PO vs Invoice
PO vs Invoice is the three-way match audit engine that checks a vendor invoice against its purchase order before you pay. It compares unit prices, quantity delivered against quantity ordered, extended amounts, freight and tax, and classifies each invoice line as justified, overbilled, unsupported or duplicate.
Updated
What is PO vs Invoice?
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 should I use PO vs Invoice?
Use PO vs Invoice for the standard AP three-way match on materials or long-lead purchases, when you close a PO at the end of a project, or when you suspect a supplier of systematic overbilling.
- 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 do I upload to PO vs Invoice?
Upload the purchase order and the invoice, and optionally a packing slip or receiving record.
- Purchase order
- Invoice
- Optional: packing slip / receiving record
How do I run PO vs Invoice?
To run PO vs Invoice, open it, upload the PO and the invoice, run the analysis, read the recommended payment and review the flagged lines.
Open the engine
Sidebar → Engines → PO vs Invoice.
Upload PO + invoice
Plus receiving record if you have one.
Run
25–45 seconds.
Read the recommended payment
Sum of JUSTIFIED items + any confirmed receiving quantities.
Review flagged lines
Filter by status to focus on issues.
How do I read the PO vs Invoice results?
The result shows a recommended payment, a line-item status table, a freight and tax reconciliation and a receiving match.
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.