Phase 7 — Invoice Verification
🎯 In plain words
❓ Why it matters
This is the financial control gate of procurement. Without it you'd pay whatever the vendor invoices — wrong prices, wrong quantities, even duplicate bills slip through. It's the step that stops overpayment and fraud, and it's where MM hands the bill over to Finance for payment. It's also a core exam area: blocking, release and the 3-way match come up a lot.
🧠 Key concepts you must know
1. The 3-way match
The heart of invoice verification. SAP checks the invoice against two reference documents:
- Purchase Order — agreed quantity & price.
- Goods Receipt — what actually arrived.
- Invoice — what the vendor wants paid.
All invoices are posted in MIRO. With GR-based IV (a flag on the PO), you can only invoice what has actually been received — each invoice line settles against a specific goods receipt, which keeps GR and invoice perfectly in step.
2. Planned delivery costs, subsequent debit/credit
- Planned delivery costs — freight, duty and insurance that were entered on the PO; you settle them in MIRO alongside the goods.
- Subsequent debit / credit — a later adjustment to an already-invoiced item (e.g. the vendor sends an extra freight charge, or a price credit) without changing the quantity.
3. Blocking & release
If a value is outside tolerance, SAP posts the invoice but blocks it for payment. The common reasons:
| Block | Trigger |
|---|---|
| Price variance | Invoice price ≠ PO price |
| Quantity variance | Invoiced qty > received qty |
| Date variance | Delivery later than agreed |
You investigate, then release the blocked invoice for payment in MRBR.
4. Tolerances & duplicate checks
- Tolerance keys (OMR6) — define how much variance is allowed before a block kicks in.
- Duplicate-invoice check — stops the same bill being paid twice; configured via OMRG / OMR2.
5. ERS, parking, and GR/IR clearing
- Evaluated Receipt Settlement (ERS) — no invoice at all; SAP self-bills from the PO + GR. Great for trusted vendors.
- Parking / holding — save an incomplete invoice now, finish posting it later.
- GR/IR account maintenance (MR11) — clears the temporary GR/IR clearing account when a GR has no matching invoice (or vice versa) and never will.
🛠️ Do it now — practise alongside
Don't just read — go post these in your IDES. Theory sticks once you've done it:
Scenario 1 — the MIRO leg Tolerance fixesThen post an over-tolerance invoice in MIRO so it blocks, and release it via MRBR. Watch the block appear, clear it, and confirm the invoice is now ready to pay.
🔗 Connects to
- Phase 6 — Inventory Management: the goods receipt you posted there is one leg of the 3-way match.
- Phase 8 — Valuation & Account Determination: the invoice clears the GR/IR account and any price difference flows through OBYC.
- Phase 4 — Purchasing: the PO is the agreement everything is checked against.
🎓 Cert focus & quick recall
C_TS452 area ⑤. Expect questions on the 3-way match, what causes a block and how to release it, tolerance keys, and GR/IR clearing.
Which three documents make up the 3-way match?
The Purchase Order (agreed qty & price), the Goods Receipt (what arrived) and the Invoice (what the vendor charges). All three must agree for the invoice to pass cleanly.
What blocks an invoice, and how do you release it?
A variance outside tolerance — typically price, quantity or date. SAP posts the invoice but blocks it for payment. You release it in MRBR once the issue is resolved.
What does MR11 do?
GR/IR account maintenance — it clears the GR/IR clearing account for quantity differences where a goods receipt has no matching invoice (or an invoice has no matching GR) and never will.
What is GR-based invoice verification?
A PO flag meaning each invoice line must reference a specific goods receipt — you can only invoice what was actually received, keeping GR and invoice in lock-step.
✅ You're ready to move on when…
- You can name the three documents in the match and what each contributes.
- You've posted an invoice in MIRO, triggered a block, and released it in MRBR.
- You can explain GR-based IV and what MR11 is for.