How to Handle a PO Mismatch on an Invoice
A PO mismatch means your invoice and the customer's purchase order disagree on a field their AP system checks automatically: the PO number, the line items, unit price, quantity, currency, or the balance left on the PO. Get the exact mismatch reason from the portal or the AP contact, compare the two documents field by field, then correct whichever side is wrong: credit and reissue if the invoice is off, or ask the buyer for a written PO amendment if the PO is. At Monk we treat a mismatch as a rejection that has to come back into the AR workflow with its reason attached, because a mismatch nobody sees looks exactly like a customer who is slow to pay.
What is a PO mismatch and why does it stop payment?
Enterprise buyers validate supplier invoices against the purchase order automatically before a human ever looks at them. Where a checked field disagrees, the invoice is held or rejected, and in many portals the supplier is the last party to find out.
That silence is the operational problem. The invoice shows as sent in your ledger, the aging clock keeps running, and the account looks like a slow payer. We covered how this plays out inside portals in why AP portals reject your invoices.
What causes a PO mismatch?
Most mismatches fall into six categories, and the category tells you who owns the fix. Identify it before you touch either document.
| Mismatch type | What the AP system sees | Who can fix it | Typical fix |
|---|---|---|---|
| Wrong or missing PO number | No PO to match against, or a PO belonging to another order | You | Credit and reissue with the correct PO and line references |
| Price or quantity variance | Invoice line values outside the buyer's tolerance | Depends on which document is right | Reissue at PO price, or have the buyer amend the PO to the agreed price |
| Invoice exceeds the PO balance | Insufficient value remaining on the PO | Buyer | Request a PO increase, or split the invoice to the remaining balance |
| Closed or expired PO | A PO that can no longer accept invoices | Buyer | Ask for the PO to be reopened or a new PO issued |
| No goods receipt or service entry | Two of three documents present under three-way matching | Buyer's requisitioner | Ask the requisitioner to record receipt, then resubmit |
| Entity, currency or unit of measure mismatch | Header or line fields that fail validation | You, usually | Reissue against the correct entity, currency and unit of measure |
Three of the six sit entirely with the buyer. Recognising that early saves a cycle of corrected invoices that were never wrong.
How do you handle a PO mismatch on an invoice?
Work the steps in order. The sequence is designed so you never reissue an invoice before you know which document is at fault.
- Get the exact mismatch reason in writing. Pull the rejection text from the AP portal or ask the AP contact which field failed and what value their system expected. "PO mismatch" is a category rather than a diagnosis, and a portal rejection normally names the specific line, quantity or amount that failed validation.
- Put the invoice and the purchase order side by side. Compare PO number, entity and bill-to address, currency, line descriptions, unit price, quantity, unit of measure, tax treatment and total. Unit of measure and tax are the two fields teams skip, and a PO written in cases against an invoice written in units fails validation while both documents look correct to a human.
- Check the PO status and its remaining balance. Log into the portal or ask AP whether the PO is open, closed, fully consumed or expired, and how much value remains on it. An invoice for $40,000 against a PO with $12,000 left will fail no matter how accurate the line items are, and a closed PO cannot accept anything at all.
- Confirm the receipt, if the buyer runs three-way matching. Three-way matching compares the PO, the goods receipt or service entry, and the invoice. Where no receipt has been entered, the invoice fails against a correct PO, and the fix belongs with the buyer's requisitioner rather than with your billing team.
- Decide which document is wrong, then fix that one. If the invoice misstates the PO number, a price, a quantity or the legal entity, the correction is yours. If the PO is short, closed, expired or written against the wrong entity, only the buyer can amend it, and no amount of reissuing on your side will clear the block.
- Credit and reissue, or request the amendment in writing. Where the invoice is wrong, issue a credit note against the original and raise a corrected invoice referencing the right PO and line numbers. Where the PO is wrong, ask the named buyer for an amended PO and hold the invoice until you have the new PO number, because resubmitting against the old one produces a second rejection and a duplicate flag.
- Resubmit through the same channel and confirm the status moved. Send the corrected invoice through the portal or intake address the original used, then check that its status advances past submitted to matched, approved or scheduled. A resubmission with no status change is still a blocked invoice, and it needs the same escalation as the first attempt.
How does three-way matching block a correct invoice?
Three-way matching compares the purchase order, the receipt of goods or services, and the invoice. All three have to agree before AP releases payment, and the receipt is the document suppliers have no control over.
This is why a technically perfect invoice sits unpaid for weeks at a buyer with strong procurement controls. The requisitioner who ordered the work has to confirm it was delivered, and that task competes with their day job. When a mismatch resolves to a missing receipt, the escalation path runs through the person who raised the requisition rather than through AP.
Should you credit and reissue, or ask for an amendment?
The decision comes down to which document is wrong, and getting it wrong costs a full rejection cycle. Reissuing against a closed PO produces a second rejection and often a duplicate-invoice flag on top of the original problem.
Credit and reissue when your invoice misstates the PO number, price, quantity, unit of measure, currency or legal entity. Request an amendment when the PO is short, closed, expired, or written at a price the customer later agreed to change. Where the commercial terms themselves are contested rather than the paperwork, handle it as a dispute instead, using the process in the complete guide to dispute resolution in AR.
How do you prevent PO mismatches?
Prevention is mostly a data-capture question at the front of the process rather than a billing question at the end. Capture the PO number, line numbers, agreed prices and PO value at order entry, and keep the remaining balance visible as you invoice against it.
Then validate before submission. Check the PO is open, that the balance covers the invoice, that line descriptions and units match the PO, and that the bill-to entity is the one on the PO. For accounts running through Coupa, Ariba or similar systems, the portal exposes most of this before you file, which we go through in our guide to Coupa, Ariba and other AP payment portals.
How we handle PO mismatches at Monk
We treat a mismatch as an exception with an owner and a reason rather than an invoice that quietly stopped moving. When a portal rejects a submission, the rejection and its reason come back onto the invoice record, so the AR team sees the specific field that failed instead of an aging balance with no explanation.
Monk files invoices into 600-plus AP portals, roughly 87% of them autonomously, with Coupa and Ariba the two our customers use most. Around 39% of cash-flow slowdowns come from predictable recurring exceptions of this kind, and more than $2B in receivables run on Monk today, with customers seeing a 40% average DSO reduction. Go-live takes 1 to 3 days.
Frequently asked questions
What is a PO mismatch on an invoice?
It is a validation failure where one or more fields on the invoice disagree with the customer's purchase order, such as the PO number, a unit price, a quantity, the currency or the remaining PO balance. The buyer's AP system holds or rejects the invoice until the two documents agree.
What are the most common causes of a PO mismatch?
A missing or wrong PO number, a price or quantity that differs from the PO, an invoice that exceeds the balance remaining, a closed or expired PO, and a mismatch in unit of measure or legal entity. Missing goods receipts are the other frequent cause at buyers running three-way matching.
Should I credit and reissue, or ask for a PO amendment?
Credit and reissue when the error is on your invoice. Request an amendment when the PO itself is wrong, short or closed, because your billing system cannot fix a document the buyer owns. Guessing wrong costs a full rejection cycle.
Can I invoice more than the value on the purchase order?
Not without an amendment. AP systems block any invoice that exceeds the remaining PO balance, sometimes within a small tolerance the buyer configures. Ask for the PO to be increased before you submit rather than after the rejection.
What is three-way matching?
It is a control that compares the purchase order, the goods receipt or service entry, and the supplier invoice before payment is released. All three have to agree, so an invoice can be correct against the PO and still fail because nobody recorded the receipt.
How do I stop PO mismatches from recurring?
Capture the PO number, line numbers and remaining balance at order entry rather than at invoicing, validate the invoice against the PO before submission, and track PO consumption across the contract term. Recurring mismatches on one account usually point at a process gap on that account rather than isolated errors.
Does a PO mismatch count as a dispute?
It is a process exception rather than a commercial disagreement, and it should be logged and worked separately from genuine disputes about quality or delivery. Mixing the two hides how much of your aging is administrative.
.avif)