Supplier Invoices Not Matching ERP POs: First-Response Checklist

You open the supplier invoice. You open the PO in your ERP. The numbers don't match.

Maybe the unit price is different. Maybe the quantity doesn't line up. Maybe there are charges on the invoice that weren't on the PO, or PO line items that don't appear on the invoice at all. Now you're sitting with two documents that should be mirrors of each other, and instead they're giving you a reconciliation problem that could take an hour to untangle — if you know where to start.

The instinct to just approve it and move on is real. In our work with omnichannel retail brands running fragmented stacks, we've seen it at every client site. The problem is that approving a mismatched invoice locks in the wrong financial record: wrong inventory cost, wrong vendor balance, and a reconciliation mess that takes far longer to undo than the five minutes you thought you were saving.

Most supplier invoice mismatches can be ruled out in the first response window — if you know what to check. Here's the checklist.

Bilal is the Co-Founder of TkTurners, where the team has worked on POS, ERP, and payments integration architectures across 50+ US omnichannel retail brands since 2024.

Why Supplier Invoices and Purchase Orders Drift Out of Alignment

Before working through the steps, it helps to understand the category of problem you're dealing with. Invoice-PO drift isn't a data quality issue in the way most operators assume. It's a translation problem.

The supplier's billing system and your ERP don't speak the same dialect natively. PO numbers, SKU formats, unit-of-measure conventions, pricing terms, and discount structures all need to be normalized at the interface between supplier portals and your ERP purchasing module. When that translation layer breaks down — or was never configured correctly — the documents drift apart.

In our implementation experience, three patterns show up most consistently:

The supplier portal to ERP handoff is a translation problem, not a data problem. The supplier submitted accurate data. Your ERP received it and interpreted it differently because the mapping between the two systems wasn't built for that specific field, format, or convention.

PO line items don't always map cleanly to supplier invoice line items. A PO might list a bundled SKU that the supplier invoices as separate line items. Or a PO price was agreed in case quantities, but the invoice is in each. Without a matching UOM convention, the unit price looks wrong even when the total is right.

Price and quantity mismatches are the most common triggers. A supplier ships a partial wave and invoices only what went out. A price was agreed verbally or via email after the PO was locked. Quantities get updated on a shipment after the PO was issued. These are fixable — but only if you catch them before the invoice gets approved.

Operators who understand the translation-layer nature of the problem troubleshoot faster. They stop asking "which system is wrong" and start asking "where did the translation break down." That shift in mental model is what the checklist below is designed to produce.

First-Response Checklist: Supplier Invoice vs. Purchase Order Reconciliation

Work through these steps in order. Each one is designed to rule out a specific cause before you move to the next.

Step 1 — Pull the original PO from your ERP, not from email or the supplier's portal

This is the most important step in the entire checklist, and it's the one most often skipped.

The authoritative record is the PO as it exists in your ERP right now — not the PDF you emailed to the supplier, not the version saved in the supplier's portal, and not the screenshot someone took when the PO was created. Any of those can be stale. Only your ERP shows the current state, including any amendments, status changes, or quantity adjustments made after issuance.

If the PO in your ERP has been modified since issuance, that modification is itself a data point. Note it.

Step 2 — Compare PO number, date, and vendor name on both documents

Before comparing line items, confirm you're comparing the right two documents.

• Does the PO number on the invoice match the PO number in your ERP?
• Does the invoice date fall within the PO's active window?
• Does the vendor name on the invoice match the vendor name on the PO exactly — including any subsidiary or DBA naming conventions?

A surprising number of mismatches trace back to invoices routed to the wrong PO entirely. This step takes thirty seconds and rules that out before you spend twenty minutes on line-item reconciliation.

Step 3 — Check line-by-line: quantity ordered vs. quantity invoiced

Go through every line item on the invoice and compare the invoiced quantity to the PO quantity.

• Is the invoiced quantity higher than the PO quantity? Flag it — you may be receiving unordered goods.
• Is it lower? Confirm whether a partial shipment is in play (see Step 7).
• Is there a line item on the invoice that doesn't exist on the PO at all? That's a high-priority flag.

Don't aggregate and compare totals. Go line by line. A match on the bottom line with errors on individual lines is still an error.

Step 4 — Check unit price against the approved PO price — watch for currency, UOM conversions, and bundled line items

Unit price mismatches are the most common cause of ERP supplier invoice mismatch scenarios, and they show up in three recurring variations:

Currency differences. If you're working with international suppliers, a PO priced in USD may be invoiced in CAD or EUR. The exchange rate applied by the supplier's billing system may differ from the rate in your ERP.

UOM conversions. The PO might be in cases; the invoice might be in each. If your ERP doesn't have a UOM conversion table configured for that supplier, the unit price will look wrong even when the extended total is correct.

Bundled vs. unbundled line items. The PO might price a kit as one line item; the supplier invoices each component separately. Unless your ERP has bundling rules set up at the supplier or SKU level, these will never match line by line.

Step 5 — Verify shipping, freight, and handling charges that may have been added post-PO

Many operators complete the line-item check, find everything matches, and then get stuck on freight charges that weren't on the PO.

• Were shipping or freight charges added after the PO was issued?
• Does the invoice show a handling fee that wasn't discussed at time of order?
• Is there a fuel surcharge or residential delivery fee that your PO didn't account for?

Freight discrepancies are common when POs are issued as estimated values and the actual shipment cost diverges from the original assumption. Check your PO terms: was it issued as an estimate or a firm order?

Step 6 — Confirm discount terms and payment milestones match the PO

If your PO includes volume discounts, early payment terms, or milestone-based pricing, verify those are reflected on the invoice.

• Is an early payment discount applied on the invoice that wasn't on the PO?
• Are volume tier discounts reflected correctly based on actual shipped quantities?
• Did the supplier apply a discount that was conditional on something your PO specified but that hasn't been fulfilled yet?

Discount terms that don't match are a common source of dispute that can be resolved quickly if you catch them — but only if you check.

Step 7 — Rule out partial shipment scenarios: multiple invoices against one PO are valid; one invoice against multiple POs is not

This is the step that catches experienced operators off guard because the rule is counterintuitive.

Multiple invoices against a single PO are normal and valid. A supplier ships in waves — you get Invoice A for Wave 1, Invoice B for Wave 2. Each invoice is correct against the portion of the PO it covers.

One invoice against multiple POs is not valid. If a single supplier invoice references two or three different PO numbers, something is wrong. Either the supplier consolidated billing incorrectly, or the invoices were routed to the wrong POs in your ERP. Do not apply this invoice to any PO until the supplier clarifies which PO each line item belongs to.

Step 8 — Document every discrepancy with a screenshot before making any ERP-side changes

This is the step that makes escalation work.

Before you adjust anything in the ERP — before you create a credit memo, before you force-match, before you reject the invoice — take screenshots of:

• The invoice as received
• The PO in your ERP with all line items visible
• Any relevant supplier portal screens showing PO status or shipment history

Screenshots taken after you make an ERP change are worthless as evidence. Capture first, then act.

Operator tip: In our experience, the operators who escalate successfully and get fast resolution are the ones who brought a screenshot package. The ones who escalate without documentation wait days for back-and-forth because nobody can reconstruct what the mismatch looked like before someone touched it.

Three Categories of ERP Supplier Invoice Mismatch — and What Each One Means for Your Next Action

Once you've worked through the checklist, the mismatch you're looking at will fall into one of three categories. The category determines your next move.

Category 1: Data entry error on the supplier side

The supplier's billing team entered the wrong SKU, wrong quantity, or wrong unit price on the invoice.

How to recognize it: The line-item data on your PO is correct and verifiable. The invoice has a specific, identifiable error on one or more lines. No systemic pattern across prior invoices from this supplier.

Next action: Contact the supplier with the specific line number, the specific dollar amount, and the PO reference. Do not speculate on the cause. State the discrepancy factually and ask them to reissue or issue a credit memo. This is an operator action — no IT ticket needed.

Category 2: System sync failure between supplier portal and your ERP

Stale PO data in the supplier portal, duplicate PO numbers, or a failed API transmission is causing the supplier's system to work from outdated or incorrect information.

How to recognize it: The mismatch affects the same PO across both the supplier portal and your ERP. You may see duplicate PO numbers circulating. The ERP import log may show a failed transmission or a record that didn't update after a PO amendment.

Next action: This is your escalation trigger. Open a ticket with IT or your ERP admin, and provide the documentation package (see next section). Do not attempt to force-match in the ERP without understanding why the sync failed — force-matching on top of a sync failure creates duplicate or phantom records.

Category 3: Process gap — PO was issued as an estimate, supplier shipped on a different wave, or terms changed after PO creation

The PO didn't reflect the actual transaction because it was issued as a forecast, the supplier shipped outside the agreed wave, or terms were modified after the PO was locked.

How to recognize it: The PO and invoice are both internally consistent — each makes sense on its own — but they represent different transactions because something changed after the PO was created and nobody updated it.

Next action: Assess whether the supplier action was authorized. If the supplier shipped extra or at a different price based on a verbal or email conversation that wasn't reflected in the PO, you need to decide whether to accept the variance and amend the PO, or push back on the supplier. This is an operator decision with financial implications — document your reasoning.

What to Capture Before You Escalate — IT, ERP Admin, or Supplier Support

Operators who escalate with complete documentation get answers in hours. Operators who escalate without it wait days. Here's what to assemble in under ten minutes.

Minimum viable documentation package

Before you call anyone, have these five things ready:

1. PO number from your ERP — the authoritative record, not the supplier's portal version
2. Supplier invoice number exactly as it appears on the document
3. Date of the PO and date of the invoice
4. Screenshot of the mismatch — both documents side by side if possible
5. Your ERP's current PO status — approved, closed, on hold, or partially received

What to include in an IT or ERP admin support ticket

If the mismatch points to a Category 2 system sync failure, your IT ticket should include:

• The PO number and supplier invoice number
• The specific lines and dollar amounts involved
• The timestamp of the suspected failed transmission
• Any error codes visible in your ERP's import or API log
• The screenshots from Step 8

Don't send a ticket that says "invoice doesn't match PO." Send a ticket that says "API log shows failed transmission for PO #12345 at 14:32 on [date]; invoice #67890 shows different unit price on line 3 — believed stale PO data in supplier portal." That's a ticket IT can act on.

What to say to the supplier before you pay or reject

Contact the supplier with the following fields filled in — nothing more, nothing less:

• The specific line number on the invoice
• The specific dollar amount in question
• Your PO number and the date it was issued
• A request for clarification or reissuance

Frame: "Invoice #___ for PO # has a discrepancy on line — the invoiced amount is $, but the PO reflects $___. Please clarify or reissue."

Do not speculate on the cause. Do not say "your system must be wrong." State the facts and ask for a correction.

When This Becomes a Pattern — and What That Signal Actually Means

One mismatched invoice from one supplier is an operational nuisance. A recurring pattern is a configuration problem, and configuration problems have structural fixes.

Recurring mismatches from the same supplier point to a problem on the supplier's billing system side — the supplier's accounts payable setup may not be configured correctly for your ERP's PO format or pricing conventions. This is fixable with a conversation and, if needed, a supplier portal reconfiguration.

Recurring mismatches across multiple suppliers point to a problem in your ERP's purchase order import or synchronization workflow. This is the signal that your PO issuance process, your ERP's supplier data setup, or your integration layer needs attention. The supplier and vendor ops cascade goes into the downstream effects of leaving this unresolved across ERP, supplier portals, and purchase ordering — worth reading if you're seeing this pattern.

A single mismatch on a high-value SKU or a large PO should be treated as a potential inventory costing error, not just a data problem. If that SKU carries a significant margin or turns frequently, a pricing error flows directly into your cost of goods sold and your inventory valuation. Escalate that one immediately, regardless of whether it's a pattern.

For teams running purchase order reconciliation processes where this handoff problem shows up repeatedly across supplier portals, the Integration Foundation Sprint is built to map the actual data flow between your ERP, your supplier portals, and your purchase ordering system — find where the translation breaks down, and fix it structurally instead of patching mismatches one at a time.

Most supplier invoice mismatches don't need a developer. They need an operator who knows what to rule out first. Run this checklist, capture what you find, and when the pattern points to a system-level problem, that's when you bring in dedicated integration support.

If mismatches keep showing up across your supplier base, it's likely a structural handoff problem — and the Integration Foundation Sprint is built to find and fix those. Talk to the team at TkTurners.

Frequently Asked Questions

Why do supplier invoices not match purchase orders in ERP systems?

The most common causes are: supplier portal data not syncing correctly with the ERP, price or quantity changes made after the PO was issued, currency or unit-of-measure discrepancies, and manual data entry errors on either side. The mismatch typically happens at the handoff point between the supplier's billing system and your ERP's purchasing module.

What should I check first when a supplier invoice doesn't match the PO?

Start with the PO number, vendor name, and date on both documents. Then compare line-by-line on quantity and unit price. Pull the original PO from your ERP directly — not from email or the supplier portal — to ensure you're working from the authoritative record.

Should I approve a mismatched invoice while I investigate?

No. Approving a mismatched invoice locks in the wrong financial record in your ERP. Instead, flag it as a hold, document the discrepancy, and contact the supplier with the specific line item, amount, and PO reference while you complete your checklist.

When should I escalate a supplier invoice mismatch to IT?

Escalate to IT when the mismatch points to a system sync failure — such as a failed API transmission, a failed data mapping, a stale PO that wasn't updated after a change, or a duplicate PO number generating duplicate invoices. Provide IT with the PO number, supplier invoice number, timestamp, and any error codes you can find.

How do I know if a recurring mismatch is an IT problem or a supplier problem?

If the same supplier keeps sending mismatched invoices despite verified correct POs, the problem is likely on the supplier's billing system side — usually a configuration issue with how their system maps to yours. If mismatches are appearing across multiple suppliers with similar error types, the problem is more likely in your ERP's purchase order import or synchronization workflow. For a deeper look at how these mismatches create downstream problems across supplier portals and purchase ordering, see the supplier and vendor ops cascade.

This operational checklist reflects patterns observed across 50+ US omnichannel retail integration environments at TkTurners. If your team is evaluating an Integration Foundation Sprint to address supplier invoice and PO reconciliation at the architecture level, schedule a systems review or explore the Integration Foundation Sprint engagement pathway.