The invoices that cannot post yet
When order, receipt, and invoice disagree, the invoice waits. May posted 214 invoices and the match held eighteen: eleven price fights, six quantity fights, one with no receipt behind it, together 66,650.00 that will not pay until someone signs.
◆ May invoices, by match resultone partition, three block kinds.
| Match result | Invoices | Held |
|---|---|---|
| Matched and released | 196 | 0.00 |
| Price block, invoice above order | 11 | 42,300.00 |
| Quantity block, billed over received | 6 | 18,750.00 |
| No receipt on file | 1 | 5,600.00 |
| Invoices, May | 214 | 66,650.00 |
Price blocks are the variance page’s invoice-stage story caught before payment; quantity blocks and the missing receipt are the clearing root causes seen from the invoice side. The reconciliation carries whatever clears late. Sample values are illustrative, never client data.
◆ The owned answerMIRO blocks, with history.
MIRO blocks the invoice; the owned layer remembers it. Landed at line grain, block rates trend by vendor, clearance carries a name and a date, and the vendor whose invoices block every month becomes a purchasing conversation instead of a recurring surprise.
- SAP
- The vendor. Systems, Applications, and Products in data processing.
- HANA
- SAP’s in-memory database, the platform S/4 runs on.
- MM
- Materials Management, the purchasing and inventory module.
- MIRO
- The delivered invoice-verification transaction.
- three-way match
- Order, receipt, and invoice agreeing before payment.
- price block
- Invoice price above the order price; held for purchasing.
- quantity block
- Billed quantity above received; held for the warehouse.