Three-way matching for spares: handle partial and held receipts

Topics: three-way matching for spares; MRO invoice matching; partial receipt exceptions; invoice acceptance evidence.

Ten spares arrive against an order for ten. The invoice also says ten, so the three-way match appears straightforward. Two of the received items are on a documented hold. If the invoice process sees only the arrival quantity, the match can succeed while the acceptance question remains open.

Three-way matching for spares should use the receipt and acceptance basis required by the approved purchasing and finance process. Arrival, stock disposition, invoice posting and payment release are related but distinct events. The configured ERP must demonstrate how those distinctions are enforced.

Reconstruct the simple case carefully

Illustrative example. A purchase order requests ten units at ₹25,000 each. All ten arrive, eight are accepted and two remain held for a document mismatch. The supplier invoices ten. Assume no earlier invoices or credits, one unit of measure and no tax or freight for this example.

The example's supported base quantity is eight. The treatment of the remaining two depends on the configured process: the invoice may be parked, posted with a block, split through a supported workflow or returned for correction. AP and the controller must choose the authorised treatment. This article does not prescribe a universal posting or tax rule.

When the held items are accepted, their disposition and reference should become available to the match. When they are returned, the return and relevant commercial adjustment must remain connected. In either case, a manual “match complete” flag without the supporting event leaves the original gap unresolved.

A three-document match can still miss a fourth fact

The familiar PO–receipt–invoice pattern often needs information from the quality or technical acceptance process. The necessary check depends on how the organisation represents inspection stock, blocked stock and acceptance in its ERP.

SAP’s ERP 6.0 EHP8 SP25 documentation describes configurable invoice-variance tolerances. This is a version-labelled example, not a claim about every current S/4HANA configuration. Check their settings separately from the receipt's acceptance status; the existence of a tolerance control does not prove that it reads the intended quality disposition. SAP tolerance documentation

Also distinguish the amount in dispute from the amount blocked for payment. SAP's invoice-blocking documentation states that a block can affect all invoice items even when only one item has a variance. The ₹50,000 unresolved portion in this example therefore does not imply that the other ₹2,00,000 will automatically be paid. Demonstrate the invoice-level outcome and any permitted partial-settlement process with finance. SAP Blocking Invoices

Demonstrate the held-receipt case in the actual configuration. Ask which field the match reads, whether a quantity can be physically received yet unavailable for the required acceptance basis, and what happens when the disposition changes after invoice entry.

For a certificate-related hold, retain the actual receipt and document-review reference. The certificate traceability guide explains how to connect that evidence to the affected lot or serial.

Partial invoices need cumulative checks

Extend the example: six accepted units were already invoiced earlier. With eight units currently accepted, only two additional accepted units remain uninvoiced under the simplified assumptions. A new invoice for eight is not valid merely because a receipt of eight exists. The match must consider prior invoicing and relevant reversals or credits.

Use stable PO and receipt-line references rather than description matching alone. Record whether a credit reverses quantity, value or another charge. A value-only credit should not necessarily reopen a quantity for invoicing. Finance defines the supported treatment and the system should expose it clearly.

Split deliveries create similar problems. An invoice may refer to one delivery or several. The relationship needs to remain visible so the same receipt cannot support duplicate claims under different invoice numbers.

Units and prices can change the apparent difference

A purchase order for ten packs and a receipt of 100 pieces may agree only if an approved conversion applies to that item and transaction. Do not infer the pack size from a similar description. Missing or conflicting conversion data belongs with the material-data or purchasing owner.

Check the pricing unit as well as the stock unit. An invoice may price per pack while stores records individual pieces. Preserve the original invoice quantity and price, the conversion used for comparison and its material-master or order reference. Converting only the quantity can create a large apparent price variance even when the supplier's charge is correct.

Likewise, a revised order price needs an effective revision and approval reference. AP should not replace the order price with the invoice price simply to clear a variance. Freight, discounts and other charges require their own agreed treatment; hiding them in the unit rate makes the comparison harder to reconstruct.

Keep the exception reasons precise. Receiving resolves missing receipt evidence. Quality or the designated technical authority resolves held disposition. Purchasing resolves price and order scope. AP checks duplicates, cumulative matching and processing status. Finance authorises accounting corrections and tolerance policy.

Automate comparison, preserve the decisions

Rules are well suited to identifiers, arithmetic, cumulative quantities and approved tolerances. Integration can supply acceptance status if it lives outside the ERP. Show freshness and source references; an unavailable feed should not silently become “accepted”.

When invoice formats vary, measure how reliably extraction supplies the fields used by the match. The invoice pilot separates that test from the checks on acceptance, cumulative quantities and exception routing.

Track exceptions by cause and age, accepted receipt references on matched lines and repeat errors from the same handover. Investigate a sample of apparently clean matches. A falling exception count is useful only if the underlying controls still catch the held and duplicate cases.

Summary and next actions

The match is defensible when the organisation can explain the quantity and value it is progressing, including prior claims and unresolved receipt conditions. Agreement between three totals is insufficient when those totals represent different business states.

1. Trace one partial delivery from order to receipt disposition, invoice and payment status.
2. Confirm which acceptance fields the configured match actually checks.
3. Rehearse held receipts, prior invoices, credits, unit conversion and price revisions.
4. Assign each exception category to the owner who can resolve its cause.