Three documents, three questions
Invoice verification asks: Did we order it? (PO price and terms) Did we receive it? (GR quantity) Is the supplier asking for the right amount? (invoice). MIRO compares all three and posts the result to Finance.
Quantity: GR-based or not
With GR-based invoice verification, each invoice line refers to a specific goods receipt. That makes partial deliveries and returns traceable. Without it, the invoice is matched against the cumulative PO quantity — simpler, but much harder to analyse later.
Price: tolerances
Tolerance keys in OMR6 decide what variance is acceptable — PP for price, DQ for quantity, BD for small differences posted automatically, ST for date. Exceed a limit and the invoice is posted with payment block R.
Releasing blocked invoices
MRBR lists blocked invoices. Once the cause is fixed — the missing GR is posted, or the buyer corrects the PO price — the block can be released automatically or manually. Analyse MRBR history before raising tolerances: high block rates normally mean master-data issues.
Takeaway
A blocked invoice is not a system error — it is a control doing its job. The consultant's work is to make sure the controls block the right invoices.
A concept overview with illustrative examples. Exact steps and available functions depend on your SAP release and configuration.