A pallet shows up at your dock on a Tuesday. Someone signs for it, someone else scans it into the system on Thursday, and three weeks later your accounting team is stuck trying to figure out why the invoice says 240 units and the packing slip says 220. Nobody did anything wrong, exactly. They just followed a receiving process that stops short of the step that actually matters.
Receiving inventory is the process of accepting, checking, and recording incoming goods so your stock counts, storage locations, and financial records all agree with what physically showed up. Most guides on this topic walk you through unloading, inspecting, and shelving a shipment, then wave at “update your system” as if it’s a single click. It isn’t. That step, matching what arrived against what you ordered and what you’re being billed for, is where growing manufacturers and distributors lose the most hours and catch the fewest errors. This piece covers the full process: all 7 steps from dock to ledger, the documents that actually drive the paperwork side, how to resolve the discrepancies that show up every week, and what changes when you stop doing the matching by hand.
What Is Receiving Inventory?
Receiving inventory is the process of accepting a shipment from a supplier, verifying it against your purchase order, inspecting its condition, and recording it in your inventory and accounting systems so the stock is available to use or sell.
It’s often confused with two other processes it sits next to. Purchasing happens before receiving: it’s the decision to order and the creation of the purchase order (PO). Cycle counting happens after receiving, on an ongoing basis: it’s the periodic check that your recorded stock still matches what’s physically on the shelf. Receiving is the one-time checkpoint in between, the moment a batch of goods crosses from “in transit” to “on hand.”
Get this checkpoint wrong and the errors compound downstream. A miscounted receipt throws off your reorder points. A receipt posted three days late makes your available-to-promise numbers wrong for those three days. A receipt that never gets matched against its invoice can mean you pay for units you never got.
The Receiving Inventory Process: 7 Steps
Most receiving guides describe five or six steps and spend nearly all of them on the physical handling. We’re adding a step here on purpose: matching documents is different work from inspecting a pallet, and folding it into “update your system” is exactly how it gets rushed.
1. Prepare the receiving area and documentation
Before a truck arrives, pull up the purchase order, print or open the expected packing list, and clear a staging zone that’s separate from your existing stock. If a supplier sends an advance shipment notice (ASN), use it: it tells you what’s coming and lets you flag a mismatch before the driver even leaves the dock. Have your scanner, scale, and any inspection tools ready. For temperature-sensitive goods, confirm cold storage is at the right temperature before the shipment lands.
2. Unload and do a first-pass visual check
Unload with the right equipment (pallet jack, forklift, hand truck) and glance over the shipment before you sign anything. Check the exterior for crushed boxes, torn packaging, or a broken pallet wrap. This isn’t the full inspection, it’s a fast gate that lets you note visible damage on the delivery receipt while the driver is still standing there, which matters if you need to file a carrier claim later.
3. Verify the shipment against the purchase order
Now count. Compare what arrived, line by line, against the PO: SKU, description, and quantity. This is the step where over-receipts, short-shipments, and wrong items get caught, and it needs to happen before anything moves to storage. If you’re receiving lot-controlled goods (food, supplements, pharma, cosmetics), capture lot or batch numbers and expiration dates right here. Reconstructing that traceability data after the fact is far harder than recording it at the point of receipt.
4. Match the packing slip, PO, and goods received note
This is the step most guides skip past. When the count is done, you create (or your system auto-generates) a goods received note (GRN), a receiving report confirming what actually arrived. That GRN, the original PO, and the packing slip that came with the shipment should all agree on quantity and item. If they don’t, you’ve found a discrepancy before it becomes an accounts payable problem. We cover this in more depth below because it’s the connective tissue between your warehouse and your books, and it’s worth understanding on its own.
5. Inspect for quality and flag exceptions
Beyond counting, check condition: damage, defects, expired shelf life, or specs that don’t match what you ordered. Use sampling for large shipments if 100% inspection isn’t practical. Anything that fails goes into a quarantine or hold location, not into general stock, and gets documented with notes (and photos, if you can) so you have evidence for a supplier claim.
6. Update inventory and accounting records
Post the confirmed quantities to your inventory system. This should happen the same day, ideally the same hour, you finish the count. A receipt that sits unposted for days creates a window where your system shows less stock than you actually have, which can trigger unnecessary reorders or false shortages in production planning. If the received price differs from the PO price, your system should capture that variance too, since it’s what your accounting team will need when the invoice arrives.
7. Label, put away, and communicate availability
Apply labels (SKU, lot number, storage location) and move goods to their assigned bin or shelf. Fast-moving items go somewhere easy to reach; slower movers can go farther back. Once it’s shelved and posted, notify the teams who need to know: sales can update availability, production can plan around the new stock, and accounting can start the invoice-matching process knowing the goods have actually landed.
Receiving Report, Packing Slip, and Goods Received Note: What’s the Difference?
These three documents get used almost interchangeably in conversation, which causes real confusion when you’re trying to build a process around them. Here’s what each one actually is.
| Document | Created By | When | Purpose |
|---|---|---|---|
| Purchase Order (PO) | Buyer | Before shipment | States what was ordered: items, quantities, agreed prices |
| Packing Slip | Supplier | Included with shipment | Lists what the supplier says they packed and shipped |
| Goods Received Note (GRN) / Receiving Report | Receiving team | At the point of receipt | Confirms what actually arrived, verified by count and inspection |
| Invoice | Supplier | After shipment | States what the supplier is billing you for |
The GRN is the one businesses most often skip creating formally, and it’s the most important of the four for catching problems early. Without it, you’re relying on the supplier’s packing slip as the record of truth, and a packing slip only tells you what the supplier claims they sent, not what you actually counted on your dock.
How Three-Way Matching Closes the Gap Between Receiving and Accounts Payable
Three-way matching is the process of comparing the purchase order, the goods received note, and the supplier’s invoice to confirm that what you ordered, what arrived, and what you’re being billed for all agree before the invoice gets paid. It’s standard practice in accounts payable, but it starts on the warehouse floor, at step 4 above, not in the finance department.
Here’s why that connection matters. If your receiving team confirms 220 units arrived but the supplier invoices for 240, a three-way match catches that gap immediately, because the GRN (220) won’t agree with the invoice (240). Without a documented GRN, accounts payable has nothing solid to check the invoice against except the PO, which only tells them what was ordered, not what showed up. That’s a two-way match, and it will happily approve payment for units you never received.
A workable match checks three things line by line:
- Quantity: does the GRN quantity match the invoiced quantity?
- Price: does the invoiced unit price match the PO’s agreed price?
- Item and terms: is it the same SKU, and do any freight or fees on the invoice match what was agreed?
When all three line up, the invoice clears for payment. When they don’t, the invoice gets held and routed back to whoever can resolve it, usually purchasing or the receiving team, rather than getting paid on faith. For a deeper look at how discrepancy checks get built into this matching step, see what an inventory receiving AI agent actually does and how AI-driven discrepancy checks catch mismatches automatically.
Common Receiving Discrepancies and How to Resolve Each One
Discrepancies aren’t a sign your process failed. They’re a normal part of receiving, and the goal isn’t zero discrepancies, it’s catching every one before it turns into a payment error or a stockout.
| Discrepancy | What It Means | Typical Cause | What To Do |
|---|---|---|---|
| Over-receipt | You received more units than the PO specifies | Supplier shipped extra, rounding to a full case | Document the excess, confirm with supplier before adding to stock, decide return vs. keep-and-adjust-PO |
| Short shipment | You received fewer units than ordered | Supplier out of stock, partial shipment, picking error | Record actual quantity received (not the PO quantity), flag for backorder, notify purchasing |
| Wrong item | SKU or description doesn’t match the PO | Supplier picking error, similar SKUs confused | Quarantine the item, do not put away, contact supplier for correction |
| Damaged goods | Items arrive broken, defective, or out of spec | Poor packaging, rough handling in transit | Photograph and document immediately, quarantine, file carrier or supplier claim |
| Price variance | Invoiced price doesn’t match the PO price | Supplier price change, data entry error, expired pricing agreement | Hold the invoice, do not approve payment until purchasing confirms correct price |
The common thread across all five: the fix depends on the discrepancy being documented at the moment you find it, not reconstructed later from memory or a missing packing slip. This is exactly what a goods received note exists to support, and why a defined goods received note process matters more than it looks like it should from the outside.
Best Practices That Actually Reduce Receiving Errors
Beyond the 7 steps, these practices are what separate a receiving process that holds up under volume from one that only works when things go smoothly.
- Use barcode scanning at the point of count. Scanning eliminates the manual keystroke errors that come from writing counts on paper and re-entering them later.
- Write down your SOP, don’t rely on tribal knowledge. A documented standard operating procedure means the process works the same way regardless of who’s on the dock that day.
- Create a goods received note for every shipment, not just the disputed ones. You only find out you needed one after a discrepancy shows up, and by then it’s too late to create it retroactively.
- Post receipts the same day you count them. A same-day posting habit is the single biggest lever against the “system shows less than you have” problem.
- Set a discrepancy threshold and a routing rule. Decide in advance what dollar or unit variance requires investigation versus auto-approval, so small rounding differences don’t eat staff time meant for real problems.
- Track supplier-level discrepancy rates. If one supplier consistently short-ships or sends mismatched paperwork, that’s a vendor management conversation, not a receiving problem to keep absorbing.
- Separate receiving from accounts payable ownership, but connect their data. The warehouse team shouldn’t approve payments, and AP shouldn’t be counting boxes, but the GRN they both rely on needs to be the same document. Our post on connecting receiving to AP and compliance walks through how that handoff should work.
Manual vs. Automated Receiving: What Changes When You Remove the Manual Step
Every step above can be done on paper with a clipboard, and plenty of businesses do exactly that at low volume. The friction shows up as volume grows, specifically in step 4, the matching step, which is where manual processes lose the most time.
Manually matching a packing slip, PO, and invoice commonly takes 8 to 15 minutes per document when done by hand, depending on complexity. That’s manageable at ten receipts a week. At two hundred, it’s a full-time job that exists only to catch errors, not to move product. One masonry supplier’s finance team reported cutting a 40-hour-a-week manual PO-matching workload down to about 4 hours after automating the matching step, which is a useful data point on the scale of the gap, even though results vary by business and shipment volume.
| Steps | Manual Receiving | Automated Receiving |
|---|---|---|
| Matching a packing slip to a PO | Line-by-line, by hand, per document | Automatic comparison, exceptions flagged for review |
| Data entry | Typed or handwritten, re-entered into each system | Captured once, synced across inventory and accounting |
| Discrepancy detection | Found when someone notices, often after posting | Found at the match, before the invoice is approved |
| Time per receipt | Minutes to tens of minutes, scales with volume | Seconds for clean matches, minutes only for exceptions |
| Audit trail | Depends on whether documents were filed and kept | Built in automatically, tied to each transaction |
Automation doesn’t remove the need for a human to inspect a damaged pallet or decide whether to accept an over-shipment. What it removes is the manual re-typing and cross-checking of numbers that are already sitting in a packing slip, a PO, and an invoice. For a closer comparison of barcode scanning versus AI-based document capture, see scanner vs. agent for receiving, and for what unstructured, inconsistent packing slips cost you specifically, see why packing slip data needs to be machine-readable.
When You Don’t Need a Complex Receiving Process
It’s fair to push back here: if you’re receiving three shipments a week from two suppliers, a clipboard and a shared spreadsheet might genuinely be enough. Building out formal GRNs, matching thresholds, and automated discrepancy routing for that volume is more process than the problem calls for.
The tipping point isn’t a specific revenue number, it’s whether your team can still tell you, without digging, exactly what arrived last week, what’s still outstanding, and whether every invoice this month matches what was actually received. Once that answer takes more than a few minutes to produce, or once a supplier discrepancy has already cost you a wrong payment, the paperwork side of receiving has outgrown the informal version, even if the physical side hasn’t changed at all.
Frequently Asked Questions
What is the goal of receiving inventory?
The goal is to make sure what’s recorded in your system, what’s physically in your warehouse, and what you’re being billed for all agree. Accurate receiving prevents phantom stock, wrong reorders, and paying for goods you never got.
What’s the difference between receiving inventory and cycle counting?
Receiving inventory is the one-time intake check when a shipment arrives, verifying it against a purchase order. Cycle counting is an ongoing, periodic check that your recorded stock still matches what’s physically on the shelf, done independently of any single shipment.
How do you handle a receiving discrepancy?
Document the actual quantity and condition received, not what the PO says you should have gotten. Photograph any damage, quarantine anything questionable, and route the discrepancy to purchasing or the supplier before the goods go into general stock or the invoice gets paid.
What is a three-way match in receiving?
A three-way match compares the purchase order, the goods received note, and the supplier invoice to confirm quantity, price, and item all agree before payment is approved. It’s the step that connects your receiving process to accounts payable.
Do small businesses need a formal receiving process?
Low-volume operations can often manage with a simple checklist and spreadsheet. The formal version, GRNs, matching thresholds, discrepancy routing, earns its cost once discrepancies start costing real money or your team can’t quickly answer what’s outstanding.
Getting Your Receiving Process Right
A reliable receiving process does two jobs at once: it gets goods physically checked, inspected, and shelved, and it produces a paper trail that lets accounting pay the right invoice for the right amount. Most guides on this topic only cover the first job well. The second one, matching your packing slip, PO, and goods received note, is where growing operations actually lose the hours and catch the fewest errors, right up until a mismatched invoice or a missed discrepancy forces the issue.
Three steps to take this week:
- Check whether your team is creating a documented goods received note for every shipment, or only reconstructing one after something goes wrong.
- Pick your worst discrepancy type from the table above and trace the last three times it happened back to where the process actually broke.
- Time how long your team spends matching packing slips to POs and invoices in a normal week, then decide if that number still makes sense at double your current volume.
Where is your receiving process actually losing time, on the dock or in the paperwork?
