FormatForge logoFormatForge

Procurement guide

Purchase Order vs Invoice: Differences and Matching Checklist

Learn how purchase orders and invoices differ and use a field-by-field checklist to identify billing discrepancies.

By FormatForge2026-07-218 min read

Quick summary

Learn how purchase orders and invoices differ and use a field-by-field checklist to identify billing discrepancies. This guide gives you a clear, practical explanation before you use the related online tool.

1

Different purposes

A purchase order communicates an approved buying commitment. An invoice requests payment for supplied goods or services.

2

Fields that should align

Supplier identity, PO number, item identifiers, descriptions, quantities, unit prices, currency, discounts, tax treatment and payment terms should be compared.

3

Why descriptions alone are weak

Suppliers may abbreviate or translate product names. Match SKU, barcode, supplier item code or internal code first, then use normalised descriptions as a fallback.

4

Price and quantity variance

Separate price variance from quantity variance. A correct unit price can still produce an incorrect invoice when billed quantity exceeds the received quantity.

5

Additional charges

Freight, handling, insurance and surcharges may be legitimate but should be authorised by contract or purchase order.

6

Resolution workflow

Document the exception, assign an owner, request supplier correction or internal approval, and retain evidence of the final decision.

Continue with a free tool

Related FormatForge tools

Frequently asked questions

Can an invoice exist without a PO?

Some organisations allow non-PO invoices under controlled categories, but approval rules should be explicit.

Should item descriptions match exactly?

Not always. Identifiers and normalised meaning matter more than punctuation or wording.

What is price variance?

It is the difference between agreed and invoiced price, often measured per unit and in total.

Can OCR help with matching?

Yes, by extracting scanned fields before comparison, subject to verification.

Keep learning

Related guides