PO Mismatch on a Manufacturing Invoice: What to Check Before Resubmitting

A PO mismatch means that an invoice and the customer’s purchase order do not agree on a detail required for processing. For a manufacturing supplier, the next step is to identify the conflicting field, confirm which source is correct, and route the correction to the person authorized to make it. Do not change an invoice merely to make it pass a portal check, and do not submit a duplicate while the original is still being investigated.

This guide is for manufacturing controllers, AR managers, and billing teams selling to business customers. It covers the supplier’s billing workflow—not the buyer’s purchase-order approval process. Customer requirements, contractual terms, and accounting policies determine the permitted correction.

Start with the rejection or hold reason

Before comparing documents, save the customer’s message and the invoice’s current status. A failed submission, a tolerance hold, a disputed invoice, and an invoice awaiting a customer receipt are different problems. An invoice can exist in your ERP without having entered the customer’s payable workflow.

Record the customer entity, invoice number, PO number, submission reference, status, and exact explanation. Then ask a specific question: is the invoice wrong, is the PO outdated, is required evidence missing, or does the customer need to take an internal action?

Compare the customer PO and invoice line by line

Use the current authorized PO and the relevant agreement, not an old email attachment. When the records conflict, identify the source and ask the appropriate owner to confirm the commercial terms.

Check	What to compare	Next action if different
PO reference and version	Customer entity, PO number, amendment, and invoice line reference	Confirm the current PO with the customer’s purchasing contact
Unit price	Approved pricing, PO price, invoice price, and currency	Ask the commercial owner to confirm the authorized price
Quantity and unit of measure	Units versus cases, quantities billed, and available supporting shipment records	Resolve the discrepancy with order management and the customer
Remaining PO quantity or value	Prior invoices, credits, and the balance available against the relevant line	Check prior activity before requesting an amendment
Invoice and address details	Legal entity, invoice number, dates, bill-to and remit-to details	Use the approved customer and supplier records
Additional charges and evidence	Freight, tax treatment, and the customer’s attachment requirements	Route tax and commercial questions to the authorized specialist

For partial shipments, reconcile what was actually authorized for billing, what has already been invoiced, and any receipt or delivery evidence the customer requires. Do not assume that shipped quantity, received quantity, and billable quantity are always identical.

Decide whether the invoice or PO needs correction

• The invoice is incorrect: follow your approved correction process. If it has already been submitted or posted, confirm whether a credit, replacement, or another authorized action is required.
• The invoice reflects agreed terms but the PO is outdated: ask the buyer to amend the PO. Do not reduce the invoice or alter contractual terms simply to satisfy a system check.
• The customer has not recorded a receipt: contact the buyer’s AP or receiving team with the relevant evidence. The supplier cannot assume authority to record the customer’s receipt.
• The records do not establish the correct answer: escalate with the conflicting documents and a clear question. Keep the invoice on a tracked exception list.

A worked manufacturing example

Illustrative example—not a customer case study. A components manufacturer has an invoice for 400 units at $25 each. The customer’s PO still lists $24 per unit, so the invoice is $400 above the PO amount. A sales email mentions new pricing, but the billing team has not yet confirmed that the change was approved.

The right first step is not to force the invoice down to $9,600. The team gathers the current PO, invoice, and pricing evidence, then asks the commercial owner to confirm the agreed price. If $25 is authorized, the buyer may need to amend the PO. If $24 is correct, the supplier follows its approved invoice correction process. Either way, the record should show who confirmed the answer and what changed.

Resubmit without creating a duplicate

Once the correction is authorized, check the original invoice’s status and the customer’s permitted correction route. Portal behavior differs by customer configuration, invoice status, and local requirements. A blanket instruction to “edit and resubmit” is not reliable.

1. Confirm the original invoice and submission reference.
2. Record the approved correction and the person authorizing it.
3. Use the correction method required by the customer and your accounting policy.
4. Preserve links between original, credit, and replacement records where applicable.
5. Save the new submission evidence and check the resulting status.
6. Keep collection messages aligned with the accurate balance and unresolved issue.

For platform-specific background, read our Coupa supplier invoicing guide. Verify current customer instructions before acting. Submitted, accepted, approved, and paid are not interchangeable statuses.

A reusable PO mismatch exception checklist

For each case, record: customer and entity; invoice and PO references; current status; conflicting field; source evidence; responsible owner; requested decision; approval; permitted correction; submission evidence; and next review date. Keep one accountable owner even when sales, billing, and the customer’s AP team all participate.

This creates a useful handoff: “Invoice 1042 is held because line 2 is priced differently from PO 780. Sales is confirming the approved price. The customer’s buyer will amend the PO if the new price is correct. Billing will check the status after that decision.” It is more actionable than “invoice rejected—please investigate.”

Prevent repeat mismatches without handing over judgment

Start with the checks that recur: missing PO numbers, outdated versions, required documents, and customer-specific submission rules. Define which actions can run routinely and which need approval. Changes to pricing, credits, tax treatment, or payment terms should remain with the authorized decision-maker.

LedgerUp’s accounts receivable automation for manufacturers focuses on the manual work around existing systems. Ari can help with PO requirements, customer portal submissions, contextual follow-ups, and exception routing within your rules. Confirm your exact systems, fields, and customer requirements before deciding what to automate.

Bring one recurring PO mismatch workflow to a LedgerUp demo. We’ll walk through the repetitive steps, the decisions that stay with your team, and where Ari could help.

Frequently asked questions

Should I change an invoice to match an incorrect customer PO?

No—not solely to pass validation. First establish the authorized commercial terms. If the PO is incorrect, ask the buyer to correct it. If the invoice is incorrect, use your approved correction process.

Who can amend the customer’s purchase order?

The customer’s authorized purchasing or procurement team controls its PO. Your team can provide supporting evidence and request an amendment, but should not assume permission to change the buyer’s record.

Can I edit an invoice after submitting it through a portal?

It depends on the portal, customer configuration, invoice status, and applicable requirements. Confirm the permitted method with the customer before editing, crediting, replacing, or resubmitting an invoice.

Does a PO mismatch always mean the customer is disputing the sale?

No. It may be an administrative mismatch, an outdated PO, or a customer approval requirement. Capture the actual reason before treating the issue as a commercial dispute.

Sources and scope

Coupa’s supplier invoice FAQ and invoice creation guidance informed the distinction between PO restrictions, holds, and customer actions. Those pages are labeled legacy; use current Coupa documentation and your customer’s instructions for operating steps. This guide is a general workflow resource, not accounting, tax, or legal advice.