How to Handle a PO Mismatch on an Invoice

A PO mismatch means the buyer's accounts payable system compared your invoice against the purchase order it holds, found a field that disagrees, and stopped the invoice before a person read it. Resolve it by getting the exact rejection reason in writing, working out which of the three matching documents is wrong, and sending the correction to whoever owns that document rather than to whoever emailed you. Monk runs invoice to cash as one system, covering invoice delivery, AP portal submission, cash application and collections, so a rejected invoice comes back onto the invoice record with its reason attached instead of ageing quietly inside a portal. Most mismatches begin as two documents that were each correct when written.

The situation is familiar. You billed against a purchase order the customer gave you, the amount agrees with the contract, and three weeks later the invoice is neither paid nor visibly rejected. Your ledger shows it as sent and the ageing clock is running.

Which of the three documents disagrees, and how do you tell?

Read the rejection as a question about one document, because a three-way match compares the purchase order, the goods receipt or service entry, and your invoice, and usually only one of the three is wrong.

Buyers run either a two-way match, comparing PO against invoice, or a three-way match, which adds proof the goods or services arrived. The message you receive names a field, such as unit price or quantity, but rarely names the document that field belongs to. Skipping that translation step produces the worst available outcome: a corrected invoice issued to fix a document you never owned.

Ownership is fixed and worth writing down per account. The purchase order belongs to the requisitioner and the procurement team who priced it. The goods receipt belongs to whoever received the delivery, or for services to the manager who signs a service entry sheet. The invoice belongs to you. Accounts payable owns none of the three: AP runs the matching engine and can release a hold inside a tolerance their policy allows, and beyond that they are as blocked as you are.

Is this a price variance, a quantity variance or a receipt variance?

Each of the three resolves through a different person inside the buyer, which is why sending all three to the AP inbox produces silence.

A price variance is a disagreement between the unit price on your invoice and the unit price on the PO line. Nobody in accounts payable can overwrite a PO price. It was set by whoever built the requisition, against a rate card or a quotation, and only an amendment raised on the buyer's side changes it. Reissuing at the PO price clears the block and concedes the difference permanently, so have someone allowed to give up revenue decide which price you are billing.

A quantity variance splits in two. Invoice against PO means you billed more units than the line authorises, and the fix is a PO increase from the requisitioner. Invoice against receipt means the buyer recorded fewer units received than you billed, and the fix sits with the receiving function, or with your own dispatch records if you shipped short.

A receipt variance means the PO and the invoice agree and the third document is missing. For goods it is a warehouse task nobody was told about. For services it is a service entry sheet or timesheet approval sitting with the manager who consumed the work. AR follow-up does not move it, because the person who can act cannot see your invoice. The request has to reach the requisitioner phrased as an action inside their system.

What tolerance did the buyer set, and why did this line breach it?

Buyers configure matching tolerances so small variances release automatically, and your line breached whichever of the percentage limit and the absolute cap is tighter.

Tolerances are set per company code and often per commodity category, as a pair: a percentage of line value and a currency ceiling, with the invoice blocked when either is exceeded. They are usually asymmetric, so under-billing passes silently while over-billing stops, and separate tolerances exist for quantity and over-receipt. None of this is published to suppliers, so ask AP what the price and quantity tolerance is on your vendor record and write the answer on the account.

Here is a worked example with illustrative figures. A PO line authorises 500 units at $12.40, a value of $6,200, and the tolerance on that category is 2% or $100, whichever is lower. Your contract carries an annual uplift that took the price to $12.85 on 1 July, so you invoice 500 units at $12.85, a value of $6,425. The variance is $225, or 3.6%, breaching both limits. Nothing on your invoice is wrong. The PO was raised in April against last year's rate card.

The clean resolution is procurement amending the PO price with an effective date, then AP rematching. If the buyer will not amend for volume already delivered, invoice the delivered units at the PO price of $6,200, take the cash, and raise the $225 as a separately priced line against an amended or new PO. Holding $6,425 hostage to a $225 argument is a common, expensive habit.

What happens when the PO is closed, fully consumed or expired?

All three produce a similar rejection, none of them can be fixed from your side, and the right move is to stop resubmitting immediately.

A closed PO has been marked complete, usually because the requisitioner believed the job was finished or the system auto-closed it after final receipt. A fully consumed PO still exists with no value left, the standard failure on blanket orders where a year of drawdowns eats the value early, sometimes because another of your business units billed against the same number. An expired PO has passed its validity end date, which bites hardest in the weeks after the buyer's financial year end.

Each has a different approval chain. Reopening a closed PO is often a quick administrative act by the requisitioner. Increasing a consumed PO needs budget, so it means fresh approval and possibly cost centre sign-off. Extending an expired PO may be impossible where policy forces a new PO in the new fiscal year, in which case you need a new number first.

In all three cases: hold the invoice, do not resubmit against the dead number, and put the request in writing to the named buyer with the PO number, the line, the value outstanding and the date you need it by. Resubmitting earns a second rejection and often a duplicate flag that then blocks the clean submission you make later. Where the disagreement turns out to be commercial rather than administrative, work it through the complete guide to dispute resolution in AR.

Why does a correct price still disagree with the purchase order?

Because the PO is a snapshot of the commercial agreement on the day it was raised, and matching engines compare fields rather than intent.

Unit of measure is the classic case. A PO line reads 40 CS at $148.80 per case, where a case holds twelve. You invoice 480 EA at $12.40. The money is identical, both documents are correct, and the match rejects because the units disagree and the engine will not convert between them. The same happens with hours against days on a services PO, and with weight against pieces on freight. Bill in the unit of measure written on the PO line, even when your system prefers another.

Part numbers do the same thing more quietly. Large buyers match on their own material or catalogue number, which may bear no relation to your SKU, so an invoice carrying only your reference produces a line-not-found rejection that reads like a data error. Capture the buyer's part number the first time you see it.

Then there is everything the contract does after the PO is raised: annual uplifts, index-linked escalators, fuel and freight surcharges, expedite fees, currency clauses, and expenses on a services engagement. Each is a legitimate charge with no matching PO line, and matching runs line by line, so a surcharge has nowhere to land even when the total sits inside tolerance. Agree at contract signature how surcharges will be represented, either as a dedicated PO line or folded into the unit price.

Who do you contact, and how do you check before you submit?

Contact the owner of the document that is wrong, and prevent the next one by validating your invoice against the live PO before submission rather than after rejection.

Accounts payable is the wrong first call for most mismatches. AP can tell you the rejection reason, the tolerance, the PO status and the balance, and can release a hold inside their delegated authority. They cannot change a price, add value to a PO, reopen a closed one or post a goods receipt. Asking anyway spends a week and returns a polite refusal.

Prevention is a pre-submission check rather than a post-rejection clean-up. Before an invoice leaves, confirm the PO is open, that its validity date covers your invoice date, that remaining value exceeds the invoice, that every line uses the buyer's part number and unit of measure, and that the bill-to entity, currency and tax treatment match the PO header. Most portals show suppliers all of this before you file, as covered in our guide to Coupa, Ariba and other AP payment portals. Submitting three or four days early gives a rejection room to be fixed while the invoice is still current, and the wider pattern of portal-side rejections is set out in why AP portals reject your invoices.

How does Monk handle this?

Monk treats a mismatch as an exception with a named reason and an owner, carried on the invoice record where the AR team can see it, rather than as an ageing balance with no explanation.

Because 92% of enterprise invoices must be submitted through a vendor portal or network rather than paid from an emailed invoice, the rejection usually happens where your ERP cannot see it. Monk files the submission and brings the portal response back, so a price variance on line 2 reads as a price variance on line 2 instead of thirty days of silence. Around 39% of cash flow slowdown is caused by edge cases of this kind.

On the cash side, AI cash application matches 80% of receipts automatically, rising to 95% with suggested matching rules, so a partial payment arising from a settled variance lands against the right invoice. Julia, Monk's AI agent for Intelligent Collections, ingests the context of the conversation and earns a 24% higher response rate than standard dunning, and 90% of collections resolve with zero human intervention. Across $2B+ in receivables under management the average reduction in DSO is 40%, teams save 26 hours a month, Monk is SOC 2 Type II compliant and integrates with QuickBooks, NetSuite, Salesforce, HubSpot and Stripe, and onboarding takes less than one week. Monk files invoices into 600-plus AP portals, roughly 87% of them autonomously, with Coupa and Ariba the two our customers use most.

Where should you start?

Take the ten oldest unpaid invoices on your ageing report and check the PO behind each one before you send another reminder.

For each, write down four things: the PO number, whether the PO is open and what value remains, whether a goods receipt exists, and the exact rejection text if there is one. The invoices will split into three piles. One is awaiting payment and needs nothing. One is blocked on a document you own and can be credited and reissued this week. One is blocked on a document the buyer owns, which means a named person, a written request and a deadline rather than another dunning email.

Then count how many buyer-owned blockages come from the same two or three accounts, since that is where a standing arrangement with procurement pays for itself. To see submission, rejection reason and follow-up in one place, book a demo.

Frequently Asked Questions

What is a PO mismatch on an invoice?

It is a validation failure where fields on your invoice disagree with the buyer's purchase order or the recorded goods receipt. The commonest are unit price, quantity, unit of measure, part number, currency and remaining PO balance. The invoice is held until the documents agree. Because matching runs before human review, the block happens whether or not the invoice is wrong.

Should I credit and reissue, or ask for a PO amendment?

Credit and reissue when the error sits on your invoice: a wrong PO number, the wrong unit of measure, your own part number, or the wrong legal entity. Ask for an amendment when the PO is priced below contract, short of value, closed or expired, because your billing system cannot change a document the buyer owns. Guessing wrong costs a full rejection cycle.

Can accounts payable fix a price variance?

Only inside the tolerance their policy delegates to them, usually a small percentage and a low currency cap. Beyond that, a PO price is changed by the buyer or category manager who set it, through a formal amendment. This is why price variances sent to the AP inbox sit unanswered. Route them to procurement with the contract clause.

What is three-way matching?

It is a control comparing the purchase order, the goods receipt or service entry sheet, and the supplier invoice before payment is released. All three must agree within tolerance. An accurate invoice can still be blocked because nobody posted the receipt, the commonest reason a correct invoice ages. Buyers often run two-way matching on services and three-way on goods.

Why does my invoice reject when the total matches the PO?

Matching runs line by line rather than on the header total. A PO written in cases against an invoice in units, a surcharge with no corresponding PO line, or your part number where the buyer expects theirs will each reject even when the money is identical. Bill in the PO's unit of measure and use the buyer's part numbers.

Can I invoice more than the value left on a purchase order?

No, other than inside whatever tolerance the buyer has configured. An invoice exceeding the remaining balance is blocked regardless of how accurate the lines are. Ask for the increase before you submit, since a resubmission usually restarts the payment clock. On blanket POs, track consumption as you bill so you can see the ceiling approaching.

Does a PO mismatch count as a dispute?

It is an administrative exception rather than a commercial disagreement, and should be logged separately from disputes about quality, scope or delivery. Mixing the two hides how much of your ageing is paperwork. If the mismatch turns out to be a real argument about what was agreed, reclassify it and route it to whoever owns the relationship.