Purchasing is the process of turning an approved business need into an order with a supplier, accepted goods and a reconciled supplier account. For a retail chain, the useful question is not simply “Has the buyer placed the order?” It is “Which goods can we use, which quantities are still unresolved, and which supplier charges have supporting records?”
Purchasing brings goods into the business from suppliers. Sales commits goods and service to customers. They meet when a customer order needs stock: the buyer must know what is already available, what is reserved and what has already been ordered before buying again. An ERP connects these departmental records so that each handover can be checked.
Cover: a generated editorial illustration of retail goods inspection and document reconciliation. It is not a photograph of a customer deployment or a product screen.
Why a purchase order marked “delivered” can still leave the chain short
A delivery truck arrives, the warehouse counts the cartons and purchasing reports that the supplier has delivered. The store still cannot fulfill its customer order because some goods are awaiting inspection. Meanwhile, accounting receives an invoice for the whole shipment.
If these events share one “done” status, the manager can promise unavailable goods, duplicate an urgent purchase or approve a payment without understanding the exception. Physical arrival, acceptance, invoice matching and payment need separate records and dates.
One purchase order, two checks and four useful measures
Illustrative example, not customer results. A retail business approves one purchase order (PO) for 20 units of one SKU at VND 5 million each: VND 100 million. The need has been checked against available stock, reservations and existing purchases. The agreed acceptance deadline is 17:00 on day 1, local time.
At that deadline, 18 units have physically arrived: 16 are accepted and two are held for inspection. Two units have not arrived. The supplier invoice covers the first 18 units, totaling VND 90 million. At 11:00 on day 2, inspection clears the two held units and the two missing units arrive and are accepted. Accepted quantity is now 20, but the invoice for the final two units has not arrived.
The order quantity, SKU, unit of measure and VND 5 million unit price stay unchanged. Taxes, freight, discounts and returns are outside this example. No payment has been made. These source values support an operational review; they do not determine the accounting entry or the amount payable immediately.
| Measure | Day 1, 17:00 | Day 2, 11:00 |
|---|---|---|
| Accepted quantity rate | 80% | 100% |
| On-time acceptance rate | 80% | 80% |
| Received-invoice match rate | 88.9% | 100% |
| Accepted but unbilled value | VND 0 | VND 10 million |
1. Accepted quantity rate: what part of this purchase can the operation rely on?
Formula: cumulative accepted units linked to this PO ÷ 20 ordered units × 100. The unit is percent. The numerator includes accepted quantities through each check; goods awaiting inspection are excluded. Sources are the approved PO, delivery record and dated acceptance or inspection record.
The move from 80% to 100% reflects four additional units being accepted. It does not mean every store can sell them immediately: warehouse location, reservations and any further release requirements still matter. The receiving supervisor confirms acceptance; purchasing follows the two absent units, while the inspection owner resolves the two held units.
2. On-time acceptance rate: did usable goods meet the original deadline?
Formula: units accepted by day 1 at 17:00 ÷ the same 20 ordered units × 100. This quantity-based measure remains 80% on day 2 because its cutoff is fixed. Sources are the agreed deadline on the approved PO and timestamped acceptance records.
Do not raise this result to 100% when late goods clear, or move the deadline retrospectively. It measures acceptance by the deadline, not merely the supplier’s arrival time, and it is not an order-level on-time-in-full score. Before assigning fault, the purchasing lead checks whether the delay came from the supplier, missing paperwork or an internal inspection queue.
3. Received-invoice match rate: how much of the invoiced value has support?
Formula: goods value on received invoice lines matched to both the agreed PO price and accepted quantities ÷ total goods value of invoices received for this PO × 100. Count each invoice allocation once. Both checks use the same VND 90 million invoice; quantities still under inspection cannot support a match.
At the first check, 16 × VND 5 million = VND 80 million has matching support: 80 ÷ 90 × 100 = 88.9%, rounded to one decimal. After inspection clears the original two held units, all VND 90 million matches. Accounts payable checks the PO, acceptance records, invoice lines and allocation history before closing the discrepancy.
Comparing order prices and receipt quantities with supplier invoice lines is a common three-way matching approach, as described in Microsoft Learn’s invoice matching overview. Here, acceptance is the business’s stated review condition. A matching result is not evidence that money has left the bank.
4. Accepted but unbilled value: what obligation still needs paperwork?
Formula: sum of accepted quantities with no corresponding received invoice allocation × their approved PO unit price. The unit is VND, measured through each check. Use the acceptance register, invoice register and allocation detail; exclude unaccepted goods and quantities already covered by an invoice.
At day 1 the result is zero: all 16 accepted units are covered by the first invoice. At day 2, the final two accepted units have no invoice, leaving VND 10 million to follow up. The accountant requests the missing document and reviews the appropriate recording treatment; the finance owner includes the expected supplier payment in the relevant forecast without treating it as confirmed cash spent.
A 100% match rate for invoices received does not mean every accepted unit has been invoiced. The fourth measure exposes that gap. An invoice can cover only part of a PO, which is why receipt-to-invoice links matter; see Microsoft Learn’s explanation of partial receipts and supplier invoices.
Hand over the exception with the record and a named owner
- Requester and approver: retain the reason, required date, destination and approved quantity. Check available stock and existing commitments before approving another purchase. A changed need requires a recorded decision.
- Buyer: obtain the supplier’s confirmed quantities, prices and delivery dates. Link each delivery to the original PO and tell the affected store which quantities remain uncertain.
- Receiving and inspection owners: record arrived, accepted and held quantities separately. Hand over the reason, evidence, next action and deadline for every held quantity. Only a recorded inspection decision clears it.
- Accounts payable: reconcile invoice allocations to PO and acceptance lines; hand price, quantity or duplicate-invoice exceptions to the responsible buyer or receiver.
- Finance and payment approver: check contractual terms, due dates, deposits, approvals and payment evidence. An operational match alone does not authorize a payment. Use the cash forecast to plan the timing.
On day 1, the VND 10 million unmatched part of the invoice overlaps the two held units within the VND 20 million of PO quantity not yet accepted. Adding these values to claim VND 30 million of extra liability would count part of the same purchase twice. On day 2, the VND 10 million unbilled balance is also not money already paid.
Close each part of the purchase on its own evidence
Receipt is complete when the agreed quantity has been accepted, or an authorized cancellation or short close explains the balance. A price change, excess delivery, rejection or supplier return needs its own approved resolution and linked records; do not rewrite the original order to make the measures improve.
Invoice reconciliation is complete when received invoice lines have been matched or their exceptions resolved. Keep the missing-document task open for accepted-but-unbilled quantities until the document arrives or an authorized resolution is recorded, with a named owner and due date. Payment is complete only when the approved obligation is settled and the bank or cash evidence is reconciled. For period-end recording, continue with the ERP accounting review.
What to ask for in a purchasing ERP demonstration
Blackwind’s purchase demand and purchasing and supplier sections describe connected requests, approvals, orders, allocations, receipts, costs and invoices. Bring a partial delivery example to the demonstration and ask:
- Can we trace this PO back to the approved need and the customer order or receiving location?
- Where do we distinguish physical arrival from accepted stock, and who can resolve held goods?
- How do two receipts and one partial invoice link without counting quantities twice?
- Can we retain the original deadline while reporting current completion separately?
- Which reports or configuration are needed for these four measures, and how can we open their source records?
Send Blackwind your purchasing requirements with the number of locations, receiving and approval roles, and a sample exception with sensitive details removed. A useful review should finish with the record to check, the person responsible and the condition that closes the work.
