What Happens When the Goods Receipt Never Arrived?

Why the gap must stay visible

Three-way matching exists because invoices lie politely: they arrive formatted, approved-looking, and wrong. The receiving record is the only document in the trio that comes from the warehouse floor rather than from whoever wants to be paid. Remove it and the whole control reduces to comparing two documents produced by the same counterparty.

That is why a missing receipt is its own exception class with its own hold reason, separate from a quantity variance or a price drift. Each reason routes to a different fix: a variance goes back to the supplier or the buyer; a missing receipt goes to whoever runs receiving.

What to bring

Bring the invoice and its purchase order, plus whatever evidence does exist: delivery notes, emails from the site, system screenshots with timestamps. Partial evidence narrows the search; it does not substitute for the record.

Bring the PO receipt expectations if you have them — promised dates, split deliveries. They turn the hold from a dead end into a follow-up list.

Step 1: Confirm the absence is real

Check whether the receipt exists under a different PO ID, a later date, or a second upload batch. The match rejects conflicting identifiers rather than guessing, so a misfiled receipt looks identical to a missing one until you look.

Step 2: Read the hold literally

receipt-missing means exactly that: no receiving document was supplied for this purchase order. It says nothing about whether the goods arrived — that question is open until someone checks reality.

Step 3: Route it to the receiving owner

The fix lives outside the finance stack: ask the warehouse or site to confirm delivery or produce the delivery note. Only a real record closes the hold; a manager's assurance does not become a receiving document.

Step 4: Re-run the match with the complete set

Once the receipt arrives, re-run the match with all documents together. Quantities are re-summed per SKU, and the invoice either clears against them or picks up its remaining exceptions — quantity or price findings may still surface.

Step 5: Record the outcome either way

Whether the invoice clears or is rejected back to the supplier, the report gives you the documented trail: which documents were compared, which values matched or differed, and who resolved the gap. MatchHold never approves, schedules, or records a payment — the trail serves whoever is authorized to act.

Verification

The closed case shows three things: the originally missing document now exists, the re-run match result, and the final status with reasons. An invoice that cleared without a receipt appearing somewhere in that chain did not clear — it leaked.

Limits that stay in this failure mode

Missing receipts stay holds; they are not inferred or filled in. No amount of surrounding context — past deliveries, supplier reputation, urgency — converts into a receiving record.

MatchHold never approves, schedules, or records a payment. Resolving the hold means producing the document or rejecting the invoice; both decisions stay with people, not the workspace.

What MatchHold does in this failure mode

MatchHold keeps the absence loud. The exceptions-only report lists receipt-missing as its own hold reason with the related purchase-order ID attached, so month-end reviews see exactly which invoices are blocked on the warehouse and which are blocked on numbers.

It also protects the recovery path: checkpointed prior findings survive a re-run, so adding the late receipt does not erase earlier exceptions.