Key takeaway
A paid invoice is one event. A reproducible match also needs the applicable order, allocated receipts, tolerance rule and any authorized exception.
Start with one invoice line
An accounts-payable export often contains invoice totals and a final posting status. Those fields may say little about why the invoice was accepted. The useful purchasing question is narrower: for this line, which order authorized the purchase, which receipts supported the billed quantity, and what rule or exception allowed posting? Build that evidence chain before presenting the archive as matched procurement history.
Microsoft’s Dynamics 365 example checks invoice prices against purchase-order lines and invoice quantities against matched product receipts. Its documented approval settings also allow different treatment of discrepancies. These are product-specific examples, checked 8 October 2026, rather than a universal accounting requirement. Your own configuration and historical overrides need to be identified in the source environment.
A partial receipt changes the answer
This hypothetical order P40 contains 100 units of item K at USD 25 each. Receipt R1 records 60 units; R2 records another 40. Invoice I1 bills 60 units at the agreed price and is allocated to R1. Invoice I2 also bills 60, but the remaining unallocated receipt supports only 40. The invented local rule requires exact quantity matching. It does not establish any real company policy.
The completed ledger identifies a 20-unit discrepancy on I2. It does not accuse the supplier of fraud or decide whether the missing evidence reflects an unrecorded delivery, an invoice mistake or an allocation error. Accounts payable holds that line for its responsible reviewer. It keeps the other matched line separate instead of labeling the entire order either perfect or unusable.
| Line / evidence | Completed illustrative match | Review decision |
|---|---|---|
| P40: order line | 100 units; USD 25 each; order revision 1 | Pin the authorized order version |
| I1 against R1 | 60 billed; 60 unallocated received | Quantity matches this allocation |
| I2 against R2 | 60 billed; 40 unallocated received | 20 units unsupported; hold for review |
| Price on I2 | USD 25; order price USD 25 | Price agrees; quantity still unresolved |
| Posting status | I2 not posted in this illustration | No inferred payment or receipt correction |
Allocate receipts without using them twice
Keep the receipt-line reference and quantity allocated to each invoice line. A cumulative received total can conceal double use: two invoices can each appear less than the order total while together claiming the same receipt. Test the remaining allocation after prior invoices, corrections and credit notes. A join on supplier name or item description alone is inadequate when several orders contain the same item.
In the illustration, assigning all of R1 to both I1 and I2 would hide the discrepancy. The internal reviewer starts at each invoice, follows its receipt allocations, then checks the receipt from the opposite direction. If one receipt is partly allocated, record the amounts rather than duplicating the full receipt row. Preserve the original posting evidence while storing the reconciliation findings separately.
Recover the rule in force at the time
Document matching policy, price basis, quantity unit and tolerances for the relevant period. A case-level exception should retain its approver, stated reason and approved scope. The current policy screen cannot prove what the system applied two years ago. If historical configuration is unavailable, say that the matching rule could not be reconstructed, even when the invoice remains visible.
Microsoft distinguishes unit-price and price-total matching, and its second example shows different line-level policies and warnings. Use that distinction to ask which check actually passed. An approval to post with discrepancies is not evidence that the discrepancy disappeared. Keep automatic result, human exception and subsequent correction as different records, with links to the transaction each concerns.
Microsoft’s invoice-matching overview distinguishes net unit price from a line total that includes quantity, charges and discounts. Add those field definitions to the review request rather than assuming that a column called price has one meaning. The P40 illustration assumes no added charges or discounts: its USD 25 figure is the stated unit price only. Ask the source owner to confirm price units and the actual check performed before interpreting a discrepancy. A price match and a quantity gap can therefore remain separate findings on the same invoice line, as I2 demonstrates. This review does not change the source transaction.
Describe evidence without exposing purchasing terms
For an initial inventory, describe retained order versions, receipt allocations, invoice lines, rule history and exception evidence. Exact supplier identities, bank details, confidential prices, contract documents and staff comments need their own disclosure review. Do not send a complete finance export to demonstrate that the relationships exist. A synthetic table can clarify the structure before a separately approved sample is considered.
The next internal assignment is specific: procurement confirms P40’s authorized version; receiving checks the missing quantity evidence; accounts payable reconciles allocations; the approver decides what the proposed description can include. Use inventory to record the category and due diligence to ask a prospective evaluator whether it needs automatic checks or exception reasoning. A permissioned named introduction through VOID does not approve the financial records or a license.