Systems and records
Invoice exception training data: what a complete mismatch case contains
By SourceX Editorial · Updated
9 sections
Short answer
A complete invoice mismatch training case links five parts: the purchase order, receipt and invoice state at the moment the hold was raised; the documents that prove each fact; the tolerance, contract term and approval authority that applied; the ordered decisions with roles; and ledger evidence that the payment, quantities and open balances ended where the decision said. Anything less teaches a model to guess.
Document stack
Invoice exception training
Key takeaways
- A complete invoice mismatch case has five linked parts: starting state, evidence, rule, decision chain and verified outcome.
- Capture the starting state at the hold timestamp, because POs, receipts and tolerances change after the fact.
- Record the tolerance, contract term and approval authority in force, or nobody can say whether the hold or the release was correct.
- Prove the outcome with ledger arithmetic and open balances, not a Paid status.
- Keep improperly resolved cases, labeled as deviations with the failed check, instead of deleting them.
What should a complete invoice mismatch training case contain?
A complete invoice mismatch training case contains five linked parts: the starting state of the purchase order, receipts and invoice; the documents that prove each fact; the rule that applied, including tolerance and approval authority; the decision chain with named roles and timestamps; and outcome evidence showing the ledger, the purchase order and the payment ended where the decision said they would. A case missing any of the five teaches a model to guess.
Most AP exception exports stop at the hold code and the release date. That tells a model that a hold existed and that it went away, not why it was placed, what the reviewer weighed, or whether the money that left the company was right. The packet below is built to answer those three questions for one case, so a reviewer or a model can reconcile the answer back to source documents.
Everything in this page's worked case is illustrative. The vendor, item, amounts, dates, people and identifiers are invented to show structure, and they are labeled as such in the packet itself. Real packets follow the same shape with approved, de-identified records.
The starting state: what the system knew before anyone acted
The starting state is a snapshot of every record the matching engine compared, frozen at the moment the exception was raised. Capture it as of the hold timestamp, not as of the export date, because purchase orders, receipts and vendor master data keep changing after the fact.
Three-way matching compares the invoice price with the purchase order and the invoice quantity with posted product receipts, as Microsoft describes for Dynamics 365 Finance. Oracle's E-Business Suite Payables reference guide describes the next rungs in data terms: quantity received is checked for three-way matching when a receipt is required, and quantity accepted is checked for four-way matching when inspection is required. Your starting state must hold every quantity and price the engine used at its level of matching, or a reader cannot reproduce the hold.
In the illustrative case, a distributor issues purchase order PO-ILL-4471 for 200 units of a valve assembly at the quarter's contract unit price, freight prepaid by the vendor. A first receipt posts 180 units; 20 are backordered. The vendor then sends invoice ILL-77812 for 200 units at a unit price 2.5 percent above the purchase order price, plus a separate freight line. The engine raises two holds the same day: billed quantity exceeds received quantity, and invoice unit price exceeds purchase order price beyond tolerance.
| Record | Field | Value at hold time (illustrative) | Why it is in the starting state |
|---|---|---|---|
| Purchase order line | Ordered quantity and unit price | 200 units at the contract unit price | Basis for the price check and the two-way quantity check |
| Purchase order header | Freight terms | Freight prepaid by vendor, not billable | Decides whether the freight line is valid |
| Product receipt GR-1 | Posted quantity and date | 180 units, day 3 | Basis for the three-way quantity check |
| Vendor invoice ILL-77812 | Billed quantity, unit price, charges | 200 units at 2.5 percent over the PO price, plus a freight line | The document under test |
| Matching result | Holds raised | Quantity received hold; price hold | The exception the case is about |
| Tolerance setup | Price tolerance in force | 2 percent over purchase order price (illustrative policy) | Without it, nobody can say the hold was correct |
The linked evidence: which documents prove each fact
Each fact in the case needs a pointer to the record that proves it, at the level of document number, line and version. A summary sentence such as 'vendor overbilled' is a conclusion; the evidence is the purchase order line, the receipt line and the invoice line that together show it.
Link documents by stable keys rather than by text matching. The BPI Challenge 2019 purchase-to-pay log, a public event log from a coatings and paints company published on 4TU.ResearchData, uses the combination of purchase document and item as the case identifier and records goods receipt and invoice receipt messages against that item. That is the right grain for an invoice mismatch packet too: one purchase order line, every receipt and invoice line that matched to it, and every message between buyer and vendor about it.
Keep a role column on every evidence reference. A vendor price notice is evidence of what the vendor claimed, not of what the buyer agreed. Mixing the two is the most common way a training case teaches the wrong lesson.
- E1, purchase order PO-ILL-4471 version 1, line 10: 200 units at the contract unit price, freight prepaid (illustrative).
- E2, product receipt GR-1: 180 units received on day 3 against line 10 (illustrative).
- E3, vendor invoice ILL-77812: 200 units at 2.5 percent over the PO unit price, plus a freight line (illustrative).
- E4, vendor email on day 5 citing a price increase notice dated after the purchase order (illustrative).
- E5, supply agreement clause fixing the unit price for the quarter in which the order was placed (illustrative).
- E6, product receipt GR-2: remaining 20 units received on day 12 (illustrative).
- E7, vendor credit memo ILL-CM-0391 covering the price difference on 200 units and the whole freight line (illustrative).
- E8, payment record and vendor subledger lines after settlement (illustrative).
The applicable rule: tolerance, contract and authority
The packet must name the rule that made each hold correct and the rule that governed the resolution, with its version. A model that sees holds and releases without the rule learns local habits, not policy.
Tolerances are configuration, so record the values that were in force. Oracle Fusion Payables, for example, lets an organization set an ordered percentage, a received percentage and a price percentage, each describing how far an invoice may exceed the purchase order schedule before validation places a hold. Microsoft documents that the legal entity default price tolerance for two-way and three-way matching is zero percent unless the organization changes it. Two companies running the same software can therefore hold the same invoice differently, and the packet has to say which policy applied.
Authority is part of the rule. The GAO Green Book, the federal internal control standard, directs management to evaluate delegations of responsibility for proper segregation of duties, separating authority, custody and accounting. In AP terms, the person who can accept a price variance should not be the person who entered the invoice, and the packet should show both roles.
| Rule element | Illustrative value | Source record | What a reviewer checks |
|---|---|---|---|
| Price tolerance | 2 percent over PO unit price | AP tolerance setup, version in force on day 3 | The invoice price is 2.5 percent over the PO price, so the price hold was correct |
| Received quantity tolerance | 0 percent | Same tolerance setup | 200 billed against 180 received, so the quantity hold was correct |
| Contract price term | Unit price fixed for the quarter | Supply agreement clause (E5) | The vendor notice postdates the order and does not override the clause |
| Freight term | Freight prepaid by vendor | Purchase order header (E1) | The freight line is not billable |
| Variance approval authority | Buyer may reject; AP lead approves releases | Delegation of authority matrix | Releasing person differs from invoice entry person |
The decision chain: who decided what, and when
The decision chain records every step that changed the case, who took it, in which role, when, and on what evidence. It is the part of the packet that teaches judgment, so it must be complete in order and specific about alternatives that were rejected.
Microsoft describes three standard ways to resolve an invoice totals discrepancy: accept the difference and post, revise the invoice amount to the expected amount and post, or request a full credit and a new corrected invoice from the vendor. It also notes that a system may require the discrepancy to be approved before posting, with an optional approval comment. Your packet should record which option was chosen and why the other two were not, because that contrast is what a model learns from.
In the illustrative case, the buyer rejects the price increase on day 6 by citing the contract clause, AP disputes the freight line the same day by citing the freight term, and the quantity hold is left in place until the backordered units arrive. Nobody overrides a hold manually. The vendor issues a credit memo on day 10 for the price difference on all 200 units and the freight line.
| Step | Actor role (illustrative) | Action | Evidence cited | Rejected alternative |
|---|---|---|---|---|
| Day 3 | Matching engine | Raises price hold and quantity received hold | E1, E2, E3 | Not applicable |
| Day 5 | AP specialist | Routes price hold to buyer; asks vendor about price | E3, E4 | Accept difference and post |
| Day 6 | Buyer | Rejects price increase under contract clause | E4, E5 | Raise the PO price to the invoice price |
| Day 6 | AP specialist | Disputes freight line with vendor | E1, E3 | Accept freight as a one-time charge |
| Day 10 | Vendor | Issues credit memo for price difference and freight | E7 | Full credit and reissued invoice |
| Day 12 | Receiving | Posts second receipt of 20 units | E6 | Not applicable |
| Day 12 | AP lead | Revalidates; both holds clear; approves payment run | E1 to E7 | Manual release of either hold |
The verified outcome: how to prove the case actually closed
Outcome evidence is proof from the ledger and the purchase order that the financial state matches the decision, not a status field that says 'resolved'. A case is closed when the money, the quantities and the open balances reconcile.
For the illustrative case, the arithmetic is the check. The invoice bills 200 units at 2.5 percent over the contract unit price, plus freight. The credit memo removes that 2.5 percent difference on all 200 units and the whole freight line, so net payable equals 200 units times the contract unit price, exactly what the purchase order allowed. Receipts total 200 units, billed quantity totals 200 units, and the purchase order line can close.
Choose the outcome window deliberately. A case that looks settled on day 12 can reopen when a vendor statement shows the credit memo was never applied, or when a duplicate invoice for the same shipment arrives a month later. Take the outcome snapshot after the next vendor statement reconciliation or period close, whichever your team already performs, and record the date so a reviewer knows how long the result was observed.
Record the outcome checks as pass or fail with the record that proves each one. If any check cannot be run because a record is missing, the packet is incomplete, and it should be labeled that way rather than filled in by inference.
Checklist · 6 items
- Paid amount equals the contract unit price times the 200 units received (pass, E8).
- Vendor subledger shows zero open balance for invoice ILL-77812 and credit memo ILL-CM-0391 after settlement (pass, E8).
- Received quantity equals billed quantity on PO line 10: 180 plus 20 equals 200 (pass, E2 and E6).
- No hold was released manually; both cleared on revalidation (pass, hold history).
- The releasing approver is a different person from the invoice entry clerk (pass, user and role log).
- The purchase order price was not edited to match the invoice (pass, PO version history shows version 1 only).
0 of 6 ticked. Tick each item as you go.
The full packet: field-level template for the illustrative case
The template below is the asset: one row per field, grouped by the five parts, with the illustrative value and the rule for filling it from real records. A team can copy it as the schema for each exported case and validate every packet against it before it leaves finance.
At a glance
The full packet: field-level template for the illustrative case
| Packet field | Part | Illustrative value | How to fill it from real records |
|---|---|---|---|
| packet_id, version, label | Header | INV-CASE-ILL-0001, v1, illustrative | Stable ID per case; label each packet real or illustrative |
| anchor_line | Starting state | PO-ILL-4471 line 10 | One purchase order line per case; split multi-line invoices |
| snapshot_at | Starting state | Day 3, at hold creation | Hold timestamp from the AP system, never the export date |
| holds_raised | Starting state | Quantity received; price | Hold codes exactly as the system named them |
| evidence_refs | Evidence | E1 to E8 with role and version | Document number, line, version and party for each record |
| rules_in_force | Rule | Tolerances, contract clause, freight term, authority | Configuration and clause versions valid on the hold date |
| decision_steps | Decision | Seven ordered steps with roles | From hold history, approval log and correspondence, in order |
| rejected_options | Decision | Accept and post; revise PO price; manual release | Alternatives considered, from notes or approval comments |
| outcome_checks | Outcome | Six checks, all pass | Each check with the ledger or PO record that proves it |
| redactions | Release | Vendor, people and bank details replaced | List of fields replaced or removed and the method used |
The counterexample: a packet that looks complete and is not
A packet that shows a hold, a release and a 'paid' status can still be wrong, and including a failing example in your documentation teaches reviewers what to reject. The common failure is a status that looks like an outcome.
Consider an illustrative variant of the same case. AP releases the price hold manually on day 4 with the comment 'vendor price increase', posts the invoice at the higher unit price, and pays the full invoice including freight. The case shows status Paid and no open hold. As a training example it teaches that a vendor email overrides a contract price and that prepaid freight is billable. The outcome checks catch it: paid amount does not equal contract price times quantity, the hold was released manually, and no buyer approval exists.
Do not delete such cases from an export. Label them as policy deviations with the check that failed. A dataset that contains correct resolutions and labeled deviations is more useful than one that contains only cases that went well, provided every label is backed by the record that proves it.
| Check | Valid packet | Failing packet | Label for the failing packet |
|---|---|---|---|
| Paid equals contract price times received quantity | 200 units at contract price, pass | Marked-up invoice plus freight, fail | Overpayment against contract |
| Holds cleared by revalidation | Yes | Price hold released manually on day 4 | Manual override without authority |
| Buyer decision recorded | Rejection citing clause E5 | None | Missing approval |
| Freight term applied | Freight disputed and credited | Freight paid | Term not applied |
| Status field | Paid | Paid | Status alone does not distinguish the two |
Before you share invoice exception cases outside the company
Invoice exception records describe vendors, prices, contract terms, people and sometimes bank details, so a packet built for internal training is not automatically ready for anyone outside the company. Access to the AP system, permission under privacy law, ownership of the records, and the contractual right to license them are four separate questions, and de-identification alone does not create a right to license.
Before external use, check supplier agreements for confidentiality terms covering prices and terms, replace vendor and employee identifiers consistently so links between records survive, remove bank and tax identifiers, and keep a redaction list in each packet. Have finance confirm that the outcome checks still pass after redaction, because a careless replacement can break the arithmetic that proves the case.
Where a finance team concludes its exception history could be licensed, SourceX offers a managed path in which rights review, contracting, preparation, delivery and payment are handled for the selected AP records. The company's eligibility is decided in a brief assessment with nothing uploaded, and no packet leaves the company until it has approved scope and terms and signed.
Frequently asked questions
What belongs in a PO, receipt, invoice and resolution packet?
It should include the purchase order line, every receipt and invoice line matched to it, the holds raised, the tolerances and contract terms in force, the ordered decision steps with roles, and outcome checks against the ledger. Each element points to a specific record and version. The page's template lists every field with the rule for filling it.
Can a reviewer reconcile the answer to documents, authority and the final financial state?
Yes, if the packet carries evidence references, the delegation of authority in force and outcome checks. A reviewer should be able to recompute the net payable from the purchase order price and received quantity and see that it matches the payment. If that arithmetic cannot be done from the packet, the packet is incomplete.
Which records prove the AP decision and the payment outcome?
The decision is proved by the approval or rejection record tied to a named role, together with the clause or term it cites. The outcome is proved by the vendor subledger and payment records after settlement, plus the purchase order showing received and billed quantities agree. A status field such as Paid is not proof on its own.
Why not just export hold codes and release dates?
Hold codes and release dates show that an exception existed and ended, but not whether it ended correctly. Without the rule, the decision and the outcome check, a model cannot tell a correct rejection from an improper manual override. Both look identical in a status column.
Should cases with wrong resolutions be removed from a training set?
Usually not. Cases where policy was not followed are useful when they are labeled as deviations with the check that failed and the record that proves it. Removing them hides the failure modes a model most needs to recognize.
Do invoice exception packets have to be real cases?
Documentation and examples can use clearly labeled illustrative cases like the one on this page. A training or evaluation set built for a model should use approved real cases, de-identified, with every packet labeled real or illustrative so the two are never mixed by accident.
Sources
- Microsoft documents that three-way matching compares the invoice price with the purchase order and the invoice quantity with posted product receipts, and that the legal entity default price tolerance for two-way and three-way matching is zero percent. Source
- Microsoft describes accounts payable invoice matching as matching vendor invoice, purchase order and product receipt information, with variances over tolerance flagged as matching discrepancies. Source
- Microsoft lists three ways to resolve an invoice totals discrepancy (accept and post, revise to the expected amount and post, or request a full credit and corrected invoice) and notes that a system may require approval of discrepancies before posting. Source
- Oracle's E-Business Suite 12.1 Payables Reference Guide says Payables checks quantity received (three-way matching) only when receipt is required and quantity accepted (four-way matching) only when inspection is required. Source
- Oracle Fusion Payables invoice tolerances include ordered, received and price percentages that set how far an invoice may exceed the purchase order schedule before a hold is placed. Source
- The GAO Green Book directs management to evaluate delegations of responsibility for proper segregation of duties, separating authority, custody and accounting. Source
- The BPI Challenge 2019 purchase-to-pay event log on 4TU.ResearchData uses purchase document and item as the case identifier and records goods receipt and invoice messages that must match the item value. Source
See if your company qualifies
A short company assessment. No data uploads are needed.