Match site invoices when receipts are partial or held

In this fictional example, the purchase order and invoice both show 100 valves of the same specification and unit. Of the 90 delivered, 80 have been accepted and ten are awaiting a required quality review. Another ten have not arrived. The 100 invoiced units therefore comprise 80 accepted, ten held and ten undelivered. Do not subtract the held quantity twice by treating it as a separate shortage outside the 90 received.

An AP reviewer can now ask three precise questions. Does the contract permit invoicing before delivery? What evidence makes an accepted quantity eligible for payment? What is the approved treatment of the held and undelivered balance? The answer might involve a partial payment, a disputed amount, a credit request or a different accounting treatment. Eighty accepted units do not automatically mean that 80 units must be paid today.

Keep the supplier's original invoice intact. A reviewer may record a proposed allocation or dispute, but should not quietly change 100 to 80 and lose the supplier's claim. If tax, freight or other charges apply, finance needs to determine their treatment separately; dividing every invoice total by quantity can produce a misleading result.

The minimum matching record needs the buying entity, supplier identity, purchase order and amendment, line identifier, specification, ordered unit, invoice reference and receipt references. Add accepted and held quantities, the quality decision reference, returns and relevant credits. A supplier name or invoice number alone is not a reliable identity across companies.

Match each receipt only once. A single invoice may cover several deliveries, and one receipt may be billed in stages. The allocation table should show how much of each receipt has already been used. Otherwise two individually reasonable matches can consume the same accepted quantity.

ERPNext documents accepted and rejected quantities in Purchase Receipts and Purchase Invoices linked to receipts. These are useful product examples. A site's temporary quality hold may need a distinct configuration; rejected stock and stock awaiting review are not necessarily the same business state. Demonstrate the actual installed workflow before relying on its labels.

A price tolerance can help route a small rounding difference. It must not erase a missing inspection or an unauthorised order amendment. Separate numerical checks from conditions that require affirmative evidence. A rule saying that an invoice is within two percent of an order tells you nothing about whether the goods were approved for use.

For a unit mismatch, preserve both values and the approved conversion. Ten boxes containing ten pieces each may reconcile with 100 pieces, but only if the packaging definition is correct for that item and purchase. Do not reuse a conversion from a similarly named material.

Make the exception reason specific: quantity not delivered, receipt not recorded, quality decision pending, price amendment absent, possible duplicate, or entity uncertain. Each reason should identify the next record needed. AP should not have to open five attachments simply to discover that the issue belongs to the stores team.

Suppose quality accepts six of the ten held valves and rejects four. The factual bridge becomes 86 accepted, four rejected and ten undelivered. The reviewer must still apply the agreed commercial treatment. The quality decision should update the acceptance record; it should not silently approve a payment or create a supplier credit.

If a credit for four units arrives later, link it to the affected invoice lines and rejection evidence. If the supplier also sends a corrected invoice, prevent the credit and replacement from reducing the obligation twice. Retain the original, reversal and replacement relationships so another reviewer can reconstruct the sequence.

A late receipt has a similar risk. When the remaining ten arrive, the system should reopen the relevant unmatched allocation, not propose paying the whole invoice again. Review the supplier account and existing payments before releasing any additional amount.

For low transaction volumes, a controlled register beside the ERP may be sufficient if it has clear line identities, access restrictions and a reconciled handoff. Native ERP matching is preferable when the system already holds reliable orders, receipts and invoices. An extraction layer becomes useful when AP spends substantial time reading varied documents, but it cannot compensate for missing receipts.

Compare these choices using the same difficult sample, including a split delivery, a hold, a return and a late credit. Measure reviewer handling time and unresolved balances as well as matching speed. A quick proposal that creates a second investigation is not necessarily an improvement.

Stores owns the physical receipt evidence. Quality owns its disposition within the project's procedure. Procurement explains order terms and amendments. Finance decides accounting and payment treatment. AP coordinates the match and documents the approved outcome. These responsibilities should survive when a person is absent; a shared queue still needs named delegates.

A useful acceptance exercise is to replay the 100-valve example from invoice arrival through quality review and final delivery. At every stage, the quantities must reconcile, prior allocations must remain visible, and the held portion must retain its reason. Test an attempted duplicate invoice and a changed unit as well.

The result worth aiming for is an explainable payable position, with no unexplained residual concealed by a tolerance. The AP exception pilot provides a bounded way to test document extraction once this underlying logic is clear.

1. Choose one supplier invoice with a partial or held receipt and reconstruct its line-level quantity bridge.
2. Have finance approve the treatment of each balance and quality confirm the hold evidence.
3. Assign exception owners and test a later receipt, credit and duplicate submission.
4. Expand matching only when another reviewer can reproduce the result from the saved records.