Invoice verification, ERS & payment handoff

MIRO posts the supplier invoice with reference to a PO, delivery note, bill of lading or service entry sheet. SAP proposes quantity and amount from the PO and GRs, checks price, quantity and tax, and posts an FI document to the supplier account.

• Invoice document tables RBKP (header) and RSEG (items).
• Duplicate invoice check uses company code, reference, invoice date and supplier (configurable).
• Invoices can be parked (MIR7) for completion and workflow approval.

T-codes & apps

MIROMIR7MIR4MIR6MIRA

Three-way match compares PO price, GR quantity and invoice. With the GR-based IV flag, each invoice line refers to a specific goods receipt — essential for partial deliveries and returns.

• Without GR-based IV, the invoice is matched against the cumulative PO quantity.
• Flag defaults from supplier purchasing data and is set per PO item.
• Invoice-receipt indicator must be set on the PO item for an invoice to be expected.

T-codes & apps

ME23N (Invoice tab)MIRO

Tolerance keys (OMR6) define acceptable variances per company code: PP price variance, DQ quantity variance, BD small differences (automatic posting), ST date variance and others. Exceeding a tolerance sets a payment block R. Manual (M), stochastic and amount-based blocks are also possible.

• Release blocked invoices with MRBR (manually or automatically once the cause is fixed).
• Stochastic blocking samples invoices by a threshold and probability.
• Item amount check blocks high-value lines by item category and GR indicator.

T-codes & apps

OMR6MRBR

Configuration

IMG › Materials Management › Logistics Invoice Verification › Invoice Block

ERS (self-billing) settles goods receipts automatically without a supplier invoice. It requires an agreement with the supplier, the ERS flag on the supplier's purchasing data and PO item, GR-based IV and a tax code on the PO.

• MRRL runs settlement, usually as a scheduled job.
• Settlement output (ERS message) informs the supplier.
• Also used for consignment (MRKO) and pipeline settlement in a similar way.

T-codes & apps

MRRLMRER

A credit memo reduces the quantity and value invoiced (e.g. returns). A subsequent debit/credit corrects only the value when the quantity is already settled — for example a retrospective price change.

• Return deliveries with GR-based IV need a credit memo referencing the return GR (122).
• Subsequent debit/credit affects stock value only where stock still exists; otherwise price difference.
• Invoice reduction posts the supplier's invoice and a credit memo for the difference in one step.

T-codes & apps

MIRO (transaction: credit memo / subsequent debit / subsequent credit)

Posting an invoice creates an open item on the supplier account; it is not a payment. Finance pays through the payment program based on payment terms, due date and blocks. Invoices with block R are not paid until released.

• Payment terms default from the PO/supplier and can be overwritten in MIRO.
• F110 automatic payment proposal → payment run → payment medium.
• Withholding tax (TDS in India) is calculated at invoice or payment depending on configuration.

T-codes & apps

F110FBL1NMRBR