Most buying teams have lived through some version of this conversation:
Bookkeeper: "This invoice from Charlie's Produce — it's $284 but the PO was $267. Did we approve the change?"
You: "I think we did. Let me search my email."
[20 minutes of searching]
You: "Yeah, they substituted a couple of items, the strawberries went up $0.50 a flat. I forgot to update the PO."
Bookkeeper: "OK. I'll just enter it as billed. We need to either update the PO retroactively or just trust the invoice."
You: "Trust the invoice."
The invoice didn't match the PO because the PO never updated to reflect what actually happened. The supplier substituted items, raised a price, and partially shipped — three things the operator was told via email but never typed back into the procurement tool. By the time the invoice arrived, the PO was a fictional document.
This is a common source of AP friction in product, restaurant, retail, and manufacturing operations. It is also fixable structurally.
Quick answer
Invoices fail to match purchase orders because the PO often stops updating after it is sent, while the supplier conversation keeps changing the real order. Supplier substitutions, price changes, partial shipments, revised ETAs, freight, and credits may live in email while the original PO stays frozen. The fix is a living PO workflow: supplier replies update the order, receiving checks against the supplier-confirmed state, supplier AR context is attached before AP review, and AP pays from a cleaner record instead of reconstructing the order.
If invoice mismatch is really a PO status problem — supplier confirmations, changed quantities, ship dates, partial shipments, or receiving variance never made it back to the order — go directly to the .