Invoice Received Not Received

Invoice received not received is the AP state where an invoice arrives before its matching receipt is logged, blocking three-way matching until receiving.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Invoice Received Not Received

Invoice received not received describes a timing mismatch: the vendor's invoice has arrived in accounts payable, but the corresponding goods or services have not been marked as received in the ERP, so nothing exists yet for three-way matching to check the invoice against. The invoice sits unmatched, and whatever it charges goes unverified until someone forces a decision on it.

This is a control gap, not a drift type on its own. It matters because every other check depends on a receipt record existing first, and this is where that record is missing.

1. What is invoice received not received?

Invoice received not received is the state where an invoice has entered accounts payable but no matching receipt of goods or services exists in the ERP. Three-way matching, which checks a purchase order, a receipt, and an invoice against each other, cannot run because one leg is missing. The invoice is technically in the system, but functionally unverifiable until receiving catches up or someone overrides the block.

The term names a specific failure point in the AP workflow, not a type of overbilling. An invoice can be entirely correct and still get stuck here, and an invoice can be wrong and still slip through here if the block is overridden without review.

It shows up most on service categories where receipt is a judgment call rather than a scanned barcode: a maintenance visit, a staffing shift, a consulting hour. Someone has to confirm the work happened before the system will treat the invoice as matchable.

2. Why does this gap open up?

The gap opens because receiving and invoicing run on different clocks. A vendor invoices as soon as the work is billable, often same-day. Receiving confirmation depends on a person, in the warehouse or the requesting department, logging that the goods or work actually arrived. When that logging lags, the invoice reaches AP first and has nothing to match against.

Paper-based or manual sign-off steps slow receiving further, widening the window during which an invoice sits unmatched. The longer that window, the more invoices stack up needing a decision.

3. What happens if it is not resolved?

Two outcomes, both costly. AP holds the invoice past its due date, risking a late fee or a strained vendor relationship. Or AP pays on override to avoid that, which removes the one control point that would have caught an error. Either way, the invoice's accuracy against the contract goes unchecked at the moment it should have been checked.

A held invoice creates friction with the vendor over a delay that has nothing to do with the invoice itself.

  • Held invoice: Payment stalls until receipt is logged, risking late fees and vendor friction over an unrelated process delay.
  • Overridden match: AP pays without a receipt record, so quantity, rate, and scope go unverified at the point that verification mattered most.
  • Stacked backlog: Unresolved invoices accumulate faster than receiving can clear them, making each week's override decision harder to review carefully.

4. How is this different from other AP mismatches?

Other mismatches compare an invoice to a wrong reference: the wrong rate, the wrong tier, the wrong scope. This one has no reference to compare against yet. It is upstream of those checks, a receiving problem that blocks the contract check rather than a contract term that was violated. Fixing it does not require a rate card review, only a faster or better-documented receiving process.

That distinction matters for where a company puts its fix. A rate card dispute belongs with procurement or the vendor. A receiving delay belongs with the warehouse team or the department that requests services, and the fix is a process change, not a negotiation.

Categories like maintenance and repair or contract labor see this often because receipt confirmation there depends on a supervisor's sign-off rather than an automated scan, and that sign-off step is exactly where delay accumulates.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What does invoice received not received mean in AP terms?

It means an invoice has arrived in accounts payable but the ERP has no record yet that the underlying goods or services were received, so three-way matching cannot compare the invoice against a receipt.

Is this the same as a missed credit memo?

No. A missed credit memo involves a credit the vendor owes that was never applied. This is a receiving timing gap that happens before any matching or crediting question is even possible.

Does this cause margin drift on its own?

Not directly. The gap itself is procedural. It becomes a risk when the resulting delay pushes AP to override the match and pay without verifying the invoice against the contract, which is when an error can pass through unchecked.

Which teams need to fix this, AP or procurement?

Usually neither alone. The fix sits with whoever confirms receipt, which is the warehouse for goods or the requesting department for services. AP can flag the pattern, but it cannot log a receipt it never performed.

How is this different from a duplicate payment?

A duplicate payment is two payments for one invoice, an error after payment happened. This is a block before payment, caused by a missing receipt record. They occur at different points in the process.

Should AP pay an invoice with no receipt on file?

That is a policy decision for the company to set, not a rule this glossary can state. What matters is that the decision is deliberate and documented, not a default that happens because the invoice is overdue.

Where does this show up most in service spend?

It shows up in categories where receipt confirmation depends on a person's sign-off rather than an automated scan, such as contract labor and staffing or maintenance and repair.

Does a faster ERP fix this by itself?

No. The ERP only records what a person enters. The gap closes when the receiving process itself, not the software, confirms goods or services faster and more consistently.

1. What is invoice received not received?

Invoice received not received is the state where an invoice has entered accounts payable but no matching receipt of goods or services exists in the ERP. Three-way matching, which checks a purchase order, a receipt, and an invoice against each other, cannot run because one leg is missing. The invoice is technically in the system, but functionally unverifiable until receiving catches up or someone overrides the block. The term names a specific failure point in the AP workflow, not a type of overbilling. An invoice can be entirely correct and still get stuck here, and an invoice can be wrong and still slip through here if the block is overridden without review. It shows up most on service categories where receipt is a judgment call rather than a scanned barcode: a maintenance visit, a staffing shift, a consulting hour. Someone has to confirm the work happened before the system will treat the invoice as matchable.

2. Why does this gap open up?

The gap opens because receiving and invoicing run on different clocks. A vendor invoices as soon as the work is billable, often same-day. Receiving confirmation depends on a person, in the warehouse or the requesting department, logging that the goods or work actually arrived. When that logging lags, the invoice reaches AP first and has nothing to match against. Paper-based or manual sign-off steps slow receiving further, widening the window during which an invoice sits unmatched. The longer that window, the more invoices stack up needing a decision.

3. What happens if it is not resolved?

Two outcomes, both costly. AP holds the invoice past its due date, risking a late fee or a strained vendor relationship. Or AP pays on override to avoid that, which removes the one control point that would have caught an error. Either way, the invoice's accuracy against the contract goes unchecked at the moment it should have been checked. A held invoice creates friction with the vendor over a delay that has nothing to do with the invoice itself. - Held invoice: Payment stalls until receipt is logged, risking late fees and vendor friction over an unrelated process delay. - Overridden match: AP pays without a receipt record, so quantity, rate, and scope go unverified at the point that verification mattered most. - Stacked backlog: Unresolved invoices accumulate faster than receiving can clear them, making each week's override decision harder to review carefully.

4. How is this different from other AP mismatches?

Other mismatches compare an invoice to a wrong reference: the wrong rate, the wrong tier, the wrong scope. This one has no reference to compare against yet. It is upstream of those checks, a receiving problem that blocks the contract check rather than a contract term that was violated. Fixing it does not require a rate card review, only a faster or better-documented receiving process. That distinction matters for where a company puts its fix. A rate card dispute belongs with procurement or the vendor. A receiving delay belongs with the warehouse team or the department that requests services, and the fix is a process change, not a negotiation. Categories like [maintenance and repair](/glossary/maintenance-and-repair-audit) or [contract labor](/glossary/contract-labor-and-staffing-audit) see this often because receipt confirmation there depends on a supervisor's sign-off rather than an automated scan, and that sign-off step is exactly where delay accumulates. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What does invoice received not received mean in AP terms?

It means an invoice has arrived in accounts payable but the ERP has no record yet that the underlying goods or services were received, so three-way matching cannot compare the invoice against a receipt.

Is this the same as a missed credit memo?

No. A missed credit memo involves a credit the vendor owes that was never applied. This is a receiving timing gap that happens before any matching or crediting question is even possible.

Does this cause margin drift on its own?

Not directly. The gap itself is procedural. It becomes a risk when the resulting delay pushes AP to override the match and pay without verifying the invoice against the contract, which is when an error can pass through unchecked.

Which teams need to fix this, AP or procurement?

Usually neither alone. The fix sits with whoever confirms receipt, which is the warehouse for goods or the requesting department for services. AP can flag the pattern, but it cannot log a receipt it never performed.

How is this different from a duplicate payment?

A duplicate payment is two payments for one invoice, an error after payment happened. This is a block before payment, caused by a missing receipt record. They occur at different points in the process.

Margin Drift Resources