MIRO — Enter a supplier invoice

MIRO is where a supplier invoice is checked against what was ordered and what was received before any money is owed. Entering the invoice with reference to the purchasing document lets the system compare quantity and value against the order and the goods receipt, which is the three-way match. Posting clears the GR/IR account created by the receipt and opens the payable in accounts payable. Because it sits on the boundary between logistics and finance, an invoice that will not post is usually explained by purchasing data, receipt data or configuration rather than by the invoice itself.

Invoice verification is the last step of procure-to-pay for purchased materials and services. In a goods-receipt-based design the invoice can only be posted for quantities already received, so timing problems in receiving become invoice problems here. Accounts payable teams work through invoices daily, often with automation handling the clean ones and users handling exceptions, which means the invoices reaching this transaction manually are disproportionately the difficult ones. Consultants also use it in every test cycle, because a posted invoice proves that purchasing, receiving, tax and account determination all agree.

You enter the invoice date, the reference from the supplier document, the amount as billed and the tax information, then the purchase order or delivery note the invoice relates to. The system proposes items from the order and the receipt, and you confirm or correct quantity and value per line. The balance indicator is the discipline of this screen: the invoice can only be posted when the entered amount and the allocated items agree. Delivery costs, unplanned costs and subsequent debits are entered as separate item types rather than by inflating a line. Before posting, review any payment or price block that the tolerance check has applied.

For a posted supplier invoice, reconcile RBKP/RSEG with the purchase-order history in EKBE and the generated accounting document in BKPF/BSEG and ACDOCA. Confirm PO quantity/value, goods receipts, tax and GR/IR clearing using the same company code, fiscal year and currency context. Parked or held documents must be distinguished from posted invoices.

MIRO remains available in S/4HANA as the advanced supplier-invoice transaction, while SAP also provides the Create Supplier Invoice Fiori app. Logistics Invoice Verification still uses RBKP/RSEG for the invoice document and integrates the resulting accounting posting with the Universal Journal.

Primary ownership is MM Logistics Invoice Verification with Accounts Payable/Finance. Purchasing and warehouse teams own PO and GR discrepancies; Tax owns tax configuration; integration or ABAP teams join only when inbound invoice mapping or custom logic is evidenced.