Supplier Receiving Process for Small Business

Closed-loop procurement — the workflow where every step of the buying cycle feeds the next without duplicate entry — has to complete somewhere. It completes at the door. When goods arrive from a supplier, the receiving step either closes the loop or breaks it: confirming what arrived against the closed-loop procurement record, recording every variance, and updating inventory before accounting sees the bill. If receiving is informal — someone counts boxes, signs the packing slip, puts the product away — the loop stays open and the bookkeeper eventually closes it for you, by paying whatever the invoice says.

This guide covers the receiving process that closes the loop properly: what to receive against, how to handle the five most common variance types, what receiving does for inventory accuracy and AP, and how the workflow differs by vertical.

Quick answer

Supplier receiving is the verification step between physical delivery and payment. A closed-loop receiving process compares what arrived to the supplier-confirmed PO — not the original PO that was sent before the supplier responded — records every variance on the live order, and updates the PO state before the invoice reaches accounts payable. By the time AP sees the bill, the payable should reflect what was ordered, confirmed by the supplier, received, and invoiced — not require AP to reconstruct the order from inboxes and packing slips.

Why most small business receiving breaks

Small businesses have three endemic receiving failures. Each one breaks the procurement loop at a different point.

Receiving against the original PO

The original PO is what the buyer requested. The supplier-confirmed PO is what the supplier agreed to ship. These often differ. Between sending the PO and delivery, the supplier may have substituted a SKU, short-filled a line, moved the ETA, or changed a price. Receiving against the original PO produces a receipt that does not match the invoice. AP then faces a three-document mismatch — original PO, receipt, invoice — with no clean source for what the commercial agreement actually was.

Not counting at all

The practical workaround for busy operators: sign the packing slip, put the product away, move on. This works until the invoice arrives 12% higher than expected and nobody can explain whether the difference is a supplier error, an approved price change, or a partial shipment that wasn't recorded.

Industry estimates across distributor-served SMBs suggest that 15–25% of supplier deliveries contain at least one discrepancy — short quantities, substituted items, or pricing differences versus the confirmed order. Unrecorded variances are the primary source of invoice disputes that take 2–4 hours each to resolve.

Recording variances in a separate system

Some operators log receiving in a spreadsheet that does not connect to the PO. The PO says 12 cases; the spreadsheet says 10 arrived; the PO still says 12 cases. AP pays the invoice for 12 or calls the buyer to reconcile the spreadsheet against the invoice — which is operationally the same problem as not counting at all.

The six-step receiving process that closes the loop

Each step is a control point. Skipping one is what creates downstream AP friction.

Step 1: Pull the supplier-confirmed PO, not the original PDF

Before the delivery arrives — ideally when the delivery is scheduled — confirm which version of the PO to receive against. The supplier-confirmed PO includes any acknowledgements, quantity changes, substitutions, price changes, and partial-shipment notes the supplier communicated after the original order was sent.

Starting from the original PO turns every change the supplier already communicated into a new discrepancy at the dock. The receiver has to mentally reconstruct the supplier's reply while counting boxes — that is the wrong moment for commercial reconstruction.

Step 2: Count by item and unit

Count every item by SKU and unit of measure before signing anything. The packing slip the driver carries reflects what they were told to deliver, not necessarily what was loaded or what survived transit. If the supplier invoices by case, receive by case.

For perishable goods in food operations, add a quality inspection: temperature on arrival, date codes, visible damage, produce condition. A case counted but not inspected for spoilage becomes a receiving variance after the driver leaves — much harder to dispute than one caught at the dock.

Step 3: Compare the count to the confirmed PO

Compare what was counted to the supplier-confirmed PO line by line:

What you find	What it means	How to record it
Quantity matches	Clean delivery	Confirm receipt
Short shipment, backorder confirmed	Partial delivery expected	Receive what arrived; leave remainder open on the PO
Short shipment, no notice	Supplier error or transit loss	Receive what arrived; flag the shortage; contact supplier
Substitution not communicated	Requires buyer decision	Hold receiving; contact supplier; update PO before confirming
Substitution already confirmed	Supplier communicated the change	Receive under the substituted SKU
Price discrepancy on delivery note	Invoice will not match confirmed PO	Note the variance; attach to PO before AP review
Damage	Cannot be sold as received	Reject damaged units; record accepted vs. rejected counts

Step 4: Record every variance on the PO

Variances that stay in the receiver's head are invisible to accounting. The purpose of recording a variance on the live PO — not in a separate log — is so that AP sees the receipt state alongside the confirmed PO when they review the invoice. AP should not discover a receiving variance for the first time from the invoice itself.

Step 5: Let inventory update from the receipt

After receiving is confirmed, inventory should update from the receipt quantities — what actually arrived — not from the original PO quantities. A system that updates inventory from PO quantities will overstate stock on every partial shipment and misattribute inventory when a substitution was received.

Receiving also captures the FEFO rotation trigger: if lot numbers and expiration dates are recorded at receiving, the system knows which batch of a perishable item should be consumed first (First Expired First Out) before the newer arrival. For restaurants and food operators, this is the difference between managing waste on paper and managing it inside the replenishment workflow.

Step 6: Attach the receiving record to the PO before AP review

The accounts payable workflow should see the PO in its current state: original request → supplier confirmation → receiving record → supplier invoice. That four-document sequence gives AP enough context to approve, dispute, or flag each payable without going back to the buyer for information that should already be in the record.

Three-way matching is the formal name for this control. The problem with classic three-way matching is that it happens at AP, after the invoice arrives, when all three documents should already reflect the same reality. A living PO closes the matching gap earlier — at the supplier reply and at the dock — so that by the time AP does the comparison, there are fewer surprises. Read the full treatment in Three-Way Matching vs. Living POs.

The five receiving variances, and what to do

1. Short shipment with backorder

The supplier shipped 8 of 12 units confirmed. The other 4 are backordered, scheduled for a follow-up shipment. Receive 8 against the current PO state; leave the remaining 4 as open on the PO. Do not close the PO until the backorder arrives or is explicitly cancelled.

Leaving the PO open — rather than closing it and creating a new one — keeps receiving and payment history connected. AP needs to know whether a second invoice from this supplier is for the backorder shipment or a duplicate charge.

2. Short shipment with no notice

The supplier shipped fewer units than confirmed, with no backorder communication. This is either a transit loss or a supplier error. Receive what arrived, flag the shortage on the PO, and contact the supplier to determine whether a credit, replacement, or adjustment is coming.

Do not pay the full invoice amount for a short delivery on the assumption the remainder will arrive. The variance needs a resolution: credit, replacement shipment, or revised invoice.

3. Substitution discovered at the door

The supplier sent a different item than was confirmed — and did not communicate the substitution before delivery. Best practice: contact the supplier before accepting if possible. If the substitution is acceptable — equivalent product, same cost per unit — update the PO to record the substituted SKU and confirm receipt. If not acceptable, reject it and document the refusal.

An unrecorded substitution accepted at the dock produces a receipt for Item A against an invoice for Item B. That combination is one of the most common causes of the invoice-mismatch problem covered in Why Your Invoice Never Matches Your PO.

4. Damaged goods

Damage discovered during receiving should be logged before the driver leaves. Once the driver departs without a damage notation on the delivery document, the burden shifts: damage noted at the door is a supplier or carrier claim. Damage discovered after the driver leaves is a dispute that may not be covered depending on the supplier's terms and carrier policy.

Record accepted and rejected quantities separately. Accept what is usable; reject what is not. The receiving record captures only accepted quantities. The rejected units become a credit memo, replacement shipment request, or claim — not a receipt.

5. Price discrepancy

The delivery note or driver invoice shows a different price than the confirmed PO. This is especially common in produce, commodity ingredients, and any category with spot pricing. Record the discrepancy on the PO before completing receiving. The goal is to give AP a flagged item to review — not to hold the delivery, but to prevent the invoice from being paid silently at a price the buyer never approved.

Purchase price variance — the delta between what was ordered and what was invoiced — is a meaningful procurement KPI. Catching it at receiving creates the record; catching it after AP pays creates the dispute.

Vertical differences in receiving

Restaurants and food operators

Speed is the constraint. Delivery windows are often 15–30 minutes, and the driver has other stops. A restaurant that checks every line against the confirmed PO slows receiving to a crawl and frustrates the driver.

The practical approach: apply more scrutiny to high-value, high-variance items. Proteins, specialty produce, and high-cost center-of-plate ingredients get counted and quality-checked. High-volume staples with consistent pack sizes get spot-checked. The confirmed PO shows expected quantities; the receiver uses it to prioritize where to look closely.

Decay-aware PAR levels require that receiving also capture date codes on perishables. A restaurant that does not know the arrival date and expected shelf life of a case of strawberries cannot run FEFO picking or accurate waste projections from that receiving event.

Specialty retail and multi-location stores

Retail receiving skews toward SKU count. A specialty retailer may receive 50–200 distinct items from a single distributor. The confirmed PO is the checklist; the receiver moves through it line by line. For multi-location retail operations, receiving at the central warehouse also triggers the allocation decision: which branches need which quantities from the delivery.

Ecommerce brands and 3PLs

For ecommerce brands receiving at a warehouse or third-party logistics provider, the receiving record triggers the inventory availability update across sales channels. A brand receiving 500 units of a best-selling SKU should see those units available on Shopify or Amazon immediately after receiving confirms — not after a manual sync. The ecommerce inventory loop runs on receiving accuracy the same way a restaurant loop runs on perishable counts.

Dropshippers

Dropshipping is the edge case: the goods never cross the buyer's dock. The receiving event is the supplier's confirmation that the order was fulfilled and shipped to the end customer — tracking number, carrier, expected delivery date. A dropshipping procurement workflow treats the supplier's fulfillment confirmation the same way a physical receiving process treats a dock receipt: it is the signal that closes the supply-side event and opens the customer-facing follow-up.

What closing the receiving loop does for accounting

A complete receiving record on a living PO changes what AP receives. Instead of an original PO created two weeks ago, a supplier invoice, and a packing slip someone photographed, AP receives:

The original PO (what was requested)
The supplier-confirmed PO (what was agreed after supplier reply)
The receiving record (what physically arrived, with accepted and rejected quantities)
The supplier invoice (what the supplier is asking to be paid)

The comparison AP makes is precise: confirmed quantities vs. received quantities vs. invoiced quantities. Variances that exist are already documented, with the context of when they were accepted or rejected. AP approves, disputes, or flags — without calling the buyer first.

LineNow carries the living PO through each of these stages: the PO absorbs supplier confirmations, receiving updates inventory and closes the supply leg, and AP sees the full reconciled state when the invoice arrives. That is the closed-loop procurement workflow from order to payment — no duplicate entry at any transition.

Try the 90-day free trial at linenow.co to see how receiving fits into the full buying workflow.