What counts as a parked invoice?

Definition, capsule and body copy for the glossary page defining what a parked invoice is and why it matters for margin drift detection. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
What counts as a parked invoice?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A parked invoice is a specific point in the AP workflow where that gap sometimes first becomes visible: before payment, while the invoice is still held for review.

This page defines the term precisely and explains why the parking reason, not just the parked status, is the detail worth reading before the invoice moves to payment.

1. What is a parked invoice, exactly?

A parked invoice is an invoice entered into the accounting system but held in a suspense status before it posts to the general ledger or moves to payment. Most ERPs assign it a status like "parked," "held," or "blocked." The invoice exists as a record, but AP has not certified it as correct and it cannot be paid until someone clears the reason it was held.

The parked status is a workflow control, not an accounting entry. Nothing hits the ledger and no cash moves. It exists so a mismatch can be investigated without losing the invoice or forcing a manual re-entry once resolved.

2. What causes an invoice to be parked?

An invoice is usually parked because an automated match check failed: the price does not agree with the rate card on file, the quantity exceeds what receiving logged, the purchase order reference is missing, or a tax or currency field cannot be validated. The system flags the exception and routes the invoice for manual review instead of posting it automatically.

Three-way matching checks the invoice against the purchase order and the goods receipt. It confirms quantity and reference fields. It does not test whether a surcharge, an escalation clause, or a volume tier was applied correctly, so a parked invoice can pass the match check on paper while still carrying a rate that diverges from the underlying contract.

3. How is a parked invoice different from a rejected or disputed invoice?

A parked invoice stays inside the buyer's system, waiting for internal review. A rejected invoice is sent back to the vendor and removed from the queue. A disputed invoice has already been reviewed and formally contested with the vendor, often after payment. Parking is the earliest and least conclusive of the three; it says only that something needs a second look.

The three statuses mark different stages. Parked sits inside the buyer's own AP system as an open exception. Rejected has left the buyer's queue entirely and gone back to the vendor for correction. Disputed means the buyer already reviewed the charge, often after paying it, and formally disagrees.

Treating a parked invoice as equivalent to a rejection undercounts how many exceptions are still live and unresolved inside the buyer's own system.

4. Why should AP and procurement review parked invoice reasons, not just clear the queue?

Clearing a parked invoice without reading the parking reason treats every exception as a data-entry fix. When the reason is a price mismatch against a rate card, that exception is describing a potential contract violation, not a clerical error. Reviewing the reason before clearing it is the only point in the cycle where the discrepancy can be caught before cash leaves the business.

Aged parked invoice reports show how long exceptions sit unresolved. A long queue usually means the reason codes are not being triaged by type.

Separating price mismatches from quantity or reference mismatches lets procurement route the contract-level exceptions to the category owner instead of having AP clear them by default.

  • Price mismatch: The billed rate does not match the rate on file. Route to the category owner, not straight to posting.
  • Quantity mismatch: Billed quantity exceeds the goods receipt. Usually a receiving or delivery discrepancy.
  • Missing PO reference: The invoice cannot be matched to an order at all. Typically a data entry gap.
  • Tax or currency exception: A field the system cannot validate automatically. Usually resolved without contract review.

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 parked invoice?

A parked invoice is one entered into the accounting system and held for review before posting, usually because it fails a match check against the purchase order or contract. It sits in a suspense status. It has not yet hit the general ledger and has not been approved for payment.

Why do invoices get parked instead of rejected?

Parking keeps the invoice in the system so AP does not have to re-key it once the discrepancy is resolved. Rejecting sends it back to the vendor and loses the record. Parking is the holding step between receipt and either posting or dispute.

Does a parked invoice mean the vendor overbilled?

Not necessarily. A parked invoice only means something did not match automatically: a price, a quantity, a missing receipt, or a tax code. The underlying cause could be a data entry gap on either side, not an actual contract violation.

How long can an invoice stay parked?

There is no fixed limit in most ERPs. An invoice can sit parked for weeks or months if nobody is assigned to resolve it, which is why aged parked invoice reports matter more than the parking status itself.

Is a parked invoice the same as a duplicate payment?

No. A duplicate payment is a completed error where the same charge was paid twice. A parked invoice has not been paid at all. It is held before payment, so it is a control point, not a loss.

What causes an invoice to get parked in an ERP?

Common causes are a price on the invoice that does not match the rate card, a quantity that exceeds what was received, a missing purchase order reference, or a tax or currency field the system cannot validate automatically.

Who is responsible for clearing parked invoices?

Typically AP clears data-entry issues and routes contract-level mismatches, such as a rate that does not match the agreement, to procurement or the category owner who can confirm the correct term.

Can a parked invoice reveal margin drift?

Yes, when the parking reason is a price or rate mismatch. Reviewing why invoices park, not just clearing them, surfaces cases where the vendor's billed rate diverges from the contract, which is a form of margin drift worth investigating before payment.

1. What is a parked invoice, exactly?

A parked invoice is an invoice entered into the accounting system but held in a suspense status before it posts to the general ledger or moves to payment. Most ERPs assign it a status like "parked," "held," or "blocked." The invoice exists as a record, but AP has not certified it as correct and it cannot be paid until someone clears the reason it was held. The parked status is a workflow control, not an accounting entry. Nothing hits the ledger and no cash moves. It exists so a mismatch can be investigated without losing the invoice or forcing a manual re-entry once resolved.

2. What causes an invoice to be parked?

An invoice is usually parked because an automated match check failed: the price does not agree with the rate card on file, the quantity exceeds what receiving logged, the purchase order reference is missing, or a tax or currency field cannot be validated. The system flags the exception and routes the invoice for manual review instead of posting it automatically. Three-way matching checks the invoice against the purchase order and the goods receipt. It confirms quantity and reference fields. It does not test whether a surcharge, an escalation clause, or [a volume tier](/glossary/volume-tier) was applied correctly, so a parked invoice can pass the match check on paper while still carrying a rate that diverges from the underlying contract.

3. How is a parked invoice different from a rejected or disputed invoice?

A parked invoice stays inside the buyer's system, waiting for internal review. A rejected invoice is sent back to the vendor and removed from the queue. A disputed invoice has already been reviewed and formally contested with the vendor, often after payment. Parking is the earliest and least conclusive of the three; it says only that something needs a second look. The three statuses mark different stages. Parked sits inside the buyer's own AP system as an open exception. Rejected has left the buyer's queue entirely and gone back to the vendor for correction. Disputed means the buyer already reviewed the charge, often after paying it, and formally disagrees. Treating a parked invoice as equivalent to a rejection undercounts how many exceptions are still live and unresolved inside the buyer's own system.

4. Why should AP and procurement review parked invoice reasons, not just clear the queue?

Clearing a parked invoice without reading the parking reason treats every exception as a data-entry fix. When the reason is a price mismatch against a rate card, that exception is describing a potential contract violation, not a clerical error. Reviewing the reason before clearing it is the only point in the cycle where the discrepancy can be caught before cash leaves the business. Aged parked invoice reports show how long exceptions sit unresolved. A long queue usually means the reason codes are not being triaged by type. Separating price mismatches from quantity or reference mismatches lets procurement route the contract-level exceptions to the category owner instead of having AP clear them by default. - Price mismatch: The billed rate does not match the rate on file. Route to the category owner, not straight to posting. - Quantity mismatch: Billed quantity exceeds the goods receipt. Usually a receiving or delivery discrepancy. - Missing PO reference: The invoice cannot be matched to an order at all. Typically a data entry gap. - Tax or currency exception: A field the system cannot validate automatically. Usually resolved without contract review. 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 parked invoice?

A parked invoice is one entered into the accounting system and held for review before posting, usually because it fails a match check against the purchase order or contract. It sits in a suspense status. It has not yet hit the general ledger and has not been approved for payment.

Why do invoices get parked instead of rejected?

Parking keeps the invoice in the system so AP does not have to re-key it once the discrepancy is resolved. Rejecting sends it back to the vendor and loses the record. Parking is the holding step between receipt and either posting or dispute.

Does a parked invoice mean the vendor overbilled?

Not necessarily. A parked invoice only means something did not match automatically: a price, a quantity, a missing receipt, or a tax code. The underlying cause could be a data entry gap on either side, not an actual contract violation.

How long can an invoice stay parked?

There is no fixed limit in most ERPs. An invoice can sit parked for weeks or months if nobody is assigned to resolve it, which is why aged parked invoice reports matter more than the parking status itself.

Is a parked invoice the same as a duplicate payment?

No. A duplicate payment is a completed error where the same charge was paid twice. A parked invoice has not been paid at all. It is held before payment, so it is a control point, not a loss.

Margin Drift Resources