An invoice can look reasonable and still use the wrong price, packaging unit or contract period. Before approving a difference, you need to know which records were compared and which rules made them comparable.
This guide covers matching supplier invoices to purchase orders and dated contract prices. It includes a checklist and one example from our contract-price check demo. The example uses synthetic data and deterministic calculations, not a customer result or a model's judgment.
What are you reconciling?
“Invoice reconciliation” can mean several different checks. Agree on the question before choosing a tool.
| Question | Records you need |
|---|---|
| Does the invoiced price match the agreed terms? | Invoice lines, purchase orders, dated contracts, unit definitions and allocated credits |
| Has an invoice been paid? | Invoice records, payment records and the rules for matching them |
| Do CRM and billing agree about a subscription? | Subscription IDs, periods, statuses and amounts from both systems |
Our procurement example answers the first question. It does not establish that goods arrived, that a payment occurred or that an invoice satisfies tax requirements. The CRM–billing reconciliation example addresses the third question separately.
An invoice reconciliation checklist
Use this checklist to decide whether a row can be checked automatically or needs a person's decision.
- Identify the records. Keep the original invoice ID, supplier, item, invoice date and purchase-order reference. Preserve the source rows alongside every finding.
- Agree the comparison basis. Decide whether amounts are net or gross, which currency applies and how quantities are represented. Our example uses EUR net amounts in integer cents.
- Select the applicable terms. Match supplier and item, then choose the contract valid on the invoice date. A newer price does not automatically apply to an older invoice.
- Normalize units. Ten boxes of ten units and one hundred individual units describe the same quantity. Comparing their unit prices without conversion can create a false alert.
- Account for credits and cancellations. Establish which invoice each credit reduces and how it affects the remaining amount. An unclear allocation belongs in review.
- Check possible duplicates separately. Matching invoice numbers and business fields identify candidates. They do not prove that the supplier billed twice or that anyone paid twice.
- Separate differences from unknowns. Report a supported amount difference only when the inputs and rules allow one. Missing terms, unsupported currency or ambiguous identity must remain visible.
- Assign a reviewer and next action. Include the source records, rule and question to resolve. A finding is not authorization to reject an invoice, change a payment or contact a supplier.
Follow one invoice back to its contract
The demo publishes its synthetic input records and calculated results. Find invoice INV-01, purchase order PO-A and contract CON-OLD; the result row retains these source IDs.
| Comparison field | Synthetic example |
|---|---|
| Invoice quantity | 100 individual units |
| Contract price | €10.00 per box of 10 units |
| Expected net amount | €100.00, stored as 10,000 cents |
| Invoice net amount after allocated credits | €120.00, stored as 12,000 cents |
| Candidate price difference | €20.00, stored as 2,000 cents |
The calculation converts the contract's packaging unit before comparing amounts: 100 individual units are 10 boxes, so the expected amount is €100.00. Subtracting 10,000 from 12,000 gives 2,000 cents to investigate.
That is a candidate price difference, not a confirmed loss or recovered saving. A reviewer still needs to confirm the applicable terms and the completeness of the records. The demo's result comes from code; no model decides the monetary amount.
The same dataset shows why a checklist needs exceptions. INV-03 uses boxes rather than individual units but matches after conversion. INV-04 falls under the newer contract. Applying one price to all invoice dates would hide that distinction.
Do not count the same difference twice
The demo flags INV-02 as a possible duplicate of INV-01. That row also has a price deviation. Adding both alerts for the same invoice would overstate the amount being investigated.
The calculation keeps overlapping price alerts outside its exclusive candidate total. This is a declared rule for the synthetic example, not a universal accounting policy. Before using it in a pilot, agree how credits, duplicate groups and retained records should be treated.
A matching record does not prove duplicate payment. Confirm identity and payment history separately before drawing that conclusion.
What can be automated, and what stays in review?
With structured inputs and agreed rules, code can join records, convert declared units, compare integer amounts and attach source references. That makes the check reproducible; it does not make the source data complete or the business rules correct.
Keep cases unresolved when a contract is missing, a currency or tax basis is unsupported, a credit allocation is unclear, or a quantity cannot be handled under the agreed rules. Unknown amounts stay unknown rather than being filled with zero.
A model could help draft a question about a flagged case. That would be a separate capability to evaluate, not a replacement for the calculation or approval. This demo does not extract PDFs, connect to a live ERP, authorize payments or send supplier messages.
Start with one bounded workflow
Before building automatic invoice checks, prepare a sample export and the rules your team already uses. Include ordinary matches, known differences and difficult exceptions; agree an independent reference set and who can resolve each type of uncertainty.
Then measure correctness against that reference set and the investigation work left for the reviewer. Time saved, reviewer acceptance and production accuracy have not been measured by this synthetic example.
Inspect the contract-price check demo to follow the inputs and unresolved cases. If this resembles your process, see how a read-only workflow pilot is scoped: one defined question, agreed inputs and a result a person can review.