Accounts payable
Review invoices before approval or payment release.
Procurement File Tools
Reconcile a purchase order against a supplier invoice and isolate the exceptions that need accounts-payable or buyer review before payment.
Extract PO and supplier-invoice line items from PDF, image, CSV or Excel, correct OCR results when needed, then detect commercial exceptions before payment approval.
1. Purchase order (PO)
PO document: PDF, image, CSV or Excel · drag/drop or browse
2. Supplier invoice
Supplier invoice: PDF, image, CSV or Excel · drag/drop or browse
Set units per pack and a common base unit when suppliers use cases, boxes, or packs.
| Item code | Supplier code | Barcode | Description | Document qty | Document unit | Units / pack | Base unit | Unit price | Base quantity | Action |
|---|---|---|---|---|---|---|---|---|---|---|
| Upload a file or add a row manually. | ||||||||||
Set units per pack and a common base unit when suppliers use cases, boxes, or packs.
| Item code | Supplier code | Barcode | Description | Document qty | Document unit | Units / pack | Base unit | Unit price | Base quantity | Action |
|---|---|---|---|---|---|---|---|---|---|---|
| Upload a file or add a row manually. | ||||||||||
Business context
A PO and invoice can appear to match while still containing quantity, unit-price, tax, freight or line-reference differences. This analysis creates a structured exception list so payment reviewers can concentrate on discrepancies instead of manually comparing entire files.
This guidance is designed for people who need to use po vs invoice matcher results in a real approval, planning or operational workflow.
Review invoices before approval or payment release.
Confirm invoice values against purchase orders and agreed prices.
Strengthen payment controls and investigate material exceptions.
Input guide
| Column | Purpose | Example |
|---|---|---|
| PO Number * | Purchase-order reference shared by the PO and invoice. | PO-10632 |
| Item / Line * | Item code or line reference used for matching. | RM-104 |
| PO Quantity * | Quantity authorised on the purchase order. | 500 |
| Invoice Quantity * | Quantity billed by the supplier. | 520 |
| PO Unit Price * | Authorised unit price. | 18.50 |
| Invoice Unit Price * | Price shown on the invoice. | 19.10 |
Mapping note: Use consistent dates, currencies, units and definitions. A correct calculation based on inconsistent inputs can still lead to a poor decision.
The sample contains fictional business data and is intended only to demonstrate the expected structure. Replace it with your own verified records before making a decision.
Use the analysis as a controlled decision-support step: prepare reliable data, review the exceptions, verify the cause and document the action taken.
Import PO and invoice lines with consistent references.
Confirm item, quantity, price and document identifiers.
Prioritise differences above approved tolerances.
Approve, amend, credit or hold each exception with evidence.
Decision support
These actions are practical review priorities. Apply your organisation's approval limits, tolerance rules and contractual requirements.
Immediate
Pause payment where invoiced quantity or price exceeds the approved PO and no authorised change exists.
Next
Check goods receipts, back orders, credit notes and approved amendments before classifying a mismatch.
Monitor
Track mismatch reasons by supplier and buyer to improve PO quality and supplier billing.
Practical examples
The same result can require a different response depending on product criticality, shelf life, contract terms, service impact and available alternatives.
An invoice uses a new price before the PO amendment is approved.
Expected outcome: The price variance is held and routed to the buyer.
The supplier bills a full order although one carton was not received.
Expected outcome: The quantity difference is confirmed against the receipt and payment is adjusted.
This is a commercial reconciliation workflow. It compares what was ordered with what the supplier billed, while keeping OCR/extraction uncertainty separate from genuine quantity, price, item and unit-of-measure exceptions.
Yes. Either side can use PDF, supported images, CSV or Excel. Text PDFs are read directly where possible and scanned documents can use browser OCR.
It can flag missing or extra lines, quantity differences, price differences, unit differences and low-confidence matches. Review taxes, freight and other header-level charges against the original documents when they are not represented as line items.
No. OCR confidence describes how reliably the document was read. Correct extracted values first; only then should reconciliation exceptions be treated as purchasing or invoicing discrepancies.
Yes. Use the available report exports to retain matched lines, exceptions, review decisions and financial variance for follow-up or audit.