Blocked invoice: how a mismatch stops payment

Glossary definition of "blocked invoice", the AP hold status that stops payment when an invoice fails a match check, with causes and how it differs from.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Blocked invoice: how a mismatch stops payment

A blocked invoice is one that an AP system has placed on payment hold because it failed an automated match check against its purchase order, goods receipt, or contract terms. The hold is a procedural stop, not a finding: it flags a mismatch for someone to look at before money moves. Most ERPs generate these blocks constantly, and clearing them is routine AP work rather than an audit finding in itself.

1. What triggers an invoice block?

A block triggers when an invoice fails a three-way match: the invoice, the purchase order, and the goods receipt do not agree on price, quantity, or both. Tolerance thresholds set in the ERP decide how large a variance is allowed before the system stops the invoice. Tax mismatches and missing PO references also trigger blocks in most configurations.

The rule lives in the ERP's match configuration, not in the invoice itself.

  • Price variance: Invoice unit price differs from the PO unit price by more than the configured tolerance.
  • Quantity variance: Invoiced quantity exceeds what was recorded as received.
  • Missing PO reference: The invoice does not cite a valid, open purchase order line.
  • Tax or currency mismatch: Calculated tax or currency code does not match the reference document.

2. How does a block get resolved?

Resolution starts with an AP processor or buyer pulling the invoice, the PO, and the receipt side by side to see where they diverge. They either correct a data entry error, ask the vendor for a corrected invoice or credit memo, update the receiving record, or override the block with an approved exception. The invoice releases for payment once one of those steps clears the mismatch.

Some ERPs route the block automatically to whoever owns the PO line for approval.

3. Why doesn't a block guarantee correct billing?

A block only tests what the match rule is configured to test, commonly PO price and received quantity. It does not evaluate whether a surcharge exceeded its contract cap, whether a rebate was applied, or whether a volume tier discount kicked in at the right threshold. An invoice can clear its block cleanly and still bill outside the terms of the contract that governs it.

That gap is why contract-level review and PO-level matching are separate disciplines.

A surcharge added after the PO was issued, for example, has nothing in the PO to compare against, so no block fires.

4. How does a blocked invoice relate to margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A blocked invoice and margin drift can overlap, but most margin drift never triggers a block at all, because the match rule that would catch a contract violation, such as a surcharge cap or a rebate clause, usually is not built into the ERP's PO matching logic.

Reviewing only blocked invoices leaves the paid, unblocked ones unchecked against the contract.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

5. Frequently Asked Questions (People Also Ask)

What is a blocked invoice?

A blocked invoice is an invoice the AP system has stopped from paying because it failed a match check against the purchase order, receipt, or contract terms. The block is a status field, not a judgment about who is right. It stays open until someone resolves the mismatch or overrides the hold.

Who removes a block on an invoice?

Typically an AP processor or buyer reviews the mismatch, contacts the vendor or requisitioner if needed, and either corrects the data, requests a credit memo, or releases the block for payment. The specific approval chain depends on the company's AP workflow configuration.

Does a blocked invoice mean the vendor overbilled?

Not necessarily. A block only means a data mismatch was detected between the invoice and its reference documents. The cause could be a vendor error, a receiving delay, a missing PO update, or a genuine overcharge. Someone has to look at it to know which.

What is the difference between a blocked invoice and margin drift?

A blocked invoice is caught before payment by an automated match rule. Margin drift is the gap between contract terms and what actually got billed, and it often shows up on invoices that pass every match check and get paid without ever being blocked.

Why do invoices get released without the underlying issue being fixed?

AP teams under time pressure sometimes override a block to avoid a late payment penalty or vendor escalation, without correcting the price or quantity discrepancy that caused it. The invoice pays, and the same discrepancy can recur on the next cycle.

Can a blocked invoice still contain margin drift?

Yes. A block checks for a match failure the system is configured to catch, usually PO price, quantity, or tax variance. It does not test a surcharge's contract cap or a rebate clause, so an invoice can clear its block and still bill outside contract terms.

What causes most blocks: quantity issues or price issues?

Both are common causes and each has a distinct source. A quantity block usually traces to a receiving record that has not been entered yet. A price block traces to the invoice unit price differing from the PO unit price, which can originate on either side.

Does every ERP handle blocked invoices the same way?

No. The match rules, tolerance thresholds, and approval routing for a block are configured separately in each ERP and often customized per company. What triggers a block in one system may not trigger one in another running the same invoice.

1. What triggers an invoice block?

A block triggers when an invoice fails a three-way match: the invoice, the purchase order, and the goods receipt do not agree on price, quantity, or both. Tolerance thresholds set in the ERP decide how large a variance is allowed before the system stops the invoice. Tax mismatches and missing PO references also trigger blocks in most configurations. The rule lives in the ERP's match configuration, not in the invoice itself. - Price variance: Invoice unit price differs from the PO unit price by more than the configured tolerance. - Quantity variance: Invoiced quantity exceeds what was recorded as received. - Missing PO reference: The invoice does not cite a valid, open purchase order line. - Tax or currency mismatch: Calculated tax or currency code does not match the reference document.

2. How does a block get resolved?

Resolution starts with an AP processor or buyer pulling the invoice, the PO, and the receipt side by side to see where they diverge. They either correct a data entry error, ask the vendor for a corrected invoice or credit memo, update the receiving record, or override the block with an approved exception. The invoice releases for payment once one of those steps clears the mismatch. Some ERPs route the block automatically to whoever owns the PO line for approval.

3. Why doesn't a block guarantee correct billing?

A block only tests what the match rule is configured to test, commonly PO price and received quantity. It does not evaluate whether a surcharge exceeded its contract cap, whether a rebate was applied, or whether a volume tier discount kicked in at the right threshold. An invoice can clear its block cleanly and still bill outside the terms of the contract that governs it. That gap is why contract-level review and PO-level matching are separate disciplines. A surcharge added after the PO was issued, for example, has nothing in the PO to compare against, so no block fires.

4. How does a blocked invoice relate to margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A blocked invoice and margin drift can overlap, but most margin drift never triggers a block at all, because the match rule that would catch a contract violation, such as a surcharge cap or a rebate clause, usually is not built into the ERP's PO matching logic. Reviewing only blocked invoices leaves the paid, unblocked ones unchecked against the contract. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

Questions & Answers

What is a blocked invoice?

A blocked invoice is an invoice the AP system has stopped from paying because it failed a match check against the purchase order, receipt, or contract terms. The block is a status field, not a judgment about who is right. It stays open until someone resolves the mismatch or overrides the hold.

Who removes a block on an invoice?

Typically an AP processor or buyer reviews the mismatch, contacts the vendor or requisitioner if needed, and either corrects the data, requests a credit memo, or releases the block for payment. The specific approval chain depends on the company's AP workflow configuration.

Does a blocked invoice mean the vendor overbilled?

Not necessarily. A block only means a data mismatch was detected between the invoice and its reference documents. The cause could be a vendor error, a receiving delay, a missing PO update, or a genuine overcharge. Someone has to look at it to know which.

What is the difference between a blocked invoice and margin drift?

A blocked invoice is caught before payment by an automated match rule. Margin drift is the gap between contract terms and what actually got billed, and it often shows up on invoices that pass every match check and get paid without ever being blocked.

Why do invoices get released without the underlying issue being fixed?

AP teams under time pressure sometimes override a block to avoid a late payment penalty or vendor escalation, without correcting the price or quantity discrepancy that caused it. The invoice pays, and the same discrepancy can recur on the next cycle.

Margin Drift Resources