PO vs Invoice
Match a vendor invoice back to the purchase order. Verify unit prices, quantities received, totals, and freight — before cutting the check.
What it does
PO vs Invoice is the three-way match audit tool: invoice vs PO line items, quantity delivered vs quantity ordered, extended amounts reconciled, freight and tax handling checked. Each invoice line is classified as JUSTIFIED / OVERBILLED / UNSUPPORTED / DUPLICATE.
When to use it
- Standard AP three-way match — invoice, PO, receiving — for materials or long-lead purchases.
- Closing a PO at the end of a project.
- Auditing a supplier you suspect of systematic overbilling.
What to upload
- Purchase order
- Invoice
- Optional: packing slip / receiving record
Step by step
Open the engine
Sidebar → Engines → PO vs Invoice.
Upload PO + invoice
Plus receiving record if you have one.
Run
20–45 seconds.
Read the recommended payment
Sum of JUSTIFIED items + any confirmed receiving quantities.
Review flagged lines
Filter by status to focus on issues.
Understanding the results
Computed from JUSTIFIED lines only. Invoice total minus recommended = savings/overbilling.
One row per invoice line. Columns: invoice qty + price, PO qty + price, delta, status flag, note.
Separate section — freight may be invoiced but not on PO, or tax may differ.
If a receiving record was uploaded, three-way match results per line.
Every control, explained
Run analysisOne run.
Filter by statusOverbilled / Unsupported / Duplicate / Justified / All.
Export PDFAP-ready audit with three-way match section.
Export XLSXRaw reconciliation table.
Chains
Chains into
Chained from
No upstream chains — this engine is usually a starting step.
Exports
- PDF — AP audit with three-way match.
- XLSX — reconciliation data.
- CSV — flat flags list.
Troubleshooting
Check whether the PO specifies FOB / Incoterms. Freight on the invoice without contract basis is OVERBILLED.
Upload the packing slip — engine will match quantities across all three documents.