The seven that did not match
Matching is the oldest control in payables: the order, the receipt, and the bill must agree. May’s 96 invoices left seven disagreements holding 23,480.00, and the difference between a control and a bottleneck is whether those seven have names.
◆ May, partitioned96 invoices, three ways to disagree.
| Match result | Invoices |
|---|---|
| Matched clean | 89 |
| Price variance | 4 |
| Quantity variance | 2 |
| No receipt on file | 1 |
| Invoices for the period | 96 |
The 96 is the same count the spend report cuts and the journal pipe carries. The seven exceptions hold 23,480.00 between them: real bills, real suppliers, waiting on a human answer to a three-document disagreement. Sample values are illustrative, never client data.
◆ The three disagreementseach one names its fix.
A price variance is procurement’s conversation: the order said one price, the bill says another. A quantity variance is the warehouse’s: billed for more than arrived. No receipt is everyone’s least favorite: the bill exists, the goods story does not, and until it does the invoice cannot responsibly be paid. The Oracle side of this catalog documents the same three-document problem where no delivered view spans it.
◆ The owned answerexceptions as rows with ages and owners.
Match results land with the invoice lines on the supplier star, so the worklist is a filter with an age column, the partition proves nothing leaks, and a variance that waits a week is visible to exactly the person whose conversation it is.
- AP
- Accounts payable, the money owed to suppliers.
- match exception
- An invoice disagreeing with its order or receipt.
- price variance
- Billed price differs from ordered price.
- quantity variance
- Billed quantity differs from received quantity.
- no receipt
- A bill with no goods story on file yet.
- hold
- Payment stopped until the disagreement resolves.