Finance Index
What is receiving in procurement, and how do I record a goods receipt?
Reference guide to receiving goods receipt basics, including request intake, purchasing controls, approval routing, vendor coordination, and finance visibility.
Receiving is the act of confirming what actually arrived against what was ordered - recording the item, quantity, date, and who confirmed it, ideally with proof of delivery attached. It's the third leg of 3-way matching and the difference between paying for what you ordered and paying for what you received. A goods receipt is that record, captured against the PO line.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Receiving in procurement | Receiving is the act of confirming what actually arrived against what was ordered - recording the item, quantity, date, and who confirmed it, ideally with proof of delivery attached. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Card control | Whoever physically takes delivery and can vouch for what arrived. | Keeps spend tied to policy, ownership, and review. |
| Set up receiving when we | Push receiving to the point of delivery: the requester who ordered the laptop confirms it arrived; the manager who took the package signs off. | Keeps spend controlled before the commitment is made. |
| Record a goods receipt | Confirm against the PO line: enter received quantity, date, and any proof of delivery, so the receipt is tied to what was ordered rather than logged loosely. | Keeps spend tied to policy, ownership, and review. |
| Related terms | ERP receiving keeps the record in the system of record but typically requires ERP access and training - a barrier for the dock worker or requester who actually takes delivery. | Keeps accounting records aligned with the ERP. |
Who should record receipts - the requester, a receiving dock, or the office manager?
Whoever physically takes delivery and can vouch for what arrived. In a warehouse, that's dock staff; in an office, the manager or admin who signs for packages; for distributed teams, the requester who receives the item directly. The anti-pattern is making AP "receive" - they never saw the goods, so their confirmation is fiction. Design receiving so the person with eyes on the delivery can confirm it in seconds, from wherever they are, without logging into the ERP. When receiving is hard, it doesn't happen, and 3-way match silently degrades into 2-way.
How do I set up receiving when we have no warehouse or receiving dock?
Push receiving to the point of delivery: the requester who ordered the laptop confirms it arrived; the manager who took the package signs off. Make confirmation possible from a phone or an email prompt - a notification that says "did your order arrive? confirm here" - rather than a system login. For low-dollar, low-risk purchases, consider auto-receiving on invoice match so you're not chasing confirmations that add no control. Receiving without a warehouse is a notification-and-mobile problem, not an org-structure problem.
How do I record a goods receipt against a purchase order?
Confirm against the PO line: enter received quantity, date, and any proof of delivery, so the receipt is tied to what was ordered rather than logged loosely. Line-level receipts are what let partial deliveries and 3-way matching work.
What is the difference between receiving in the ERP and receiving in a procurement front-end?
ERP receiving keeps the record in the system of record but typically requires ERP access and training - a barrier for the dock worker or requester who actually takes delivery. A procurement front-end lets non-ERP users confirm receipt easily (often on mobile) and feeds that into matching, with the relevant context still aligned to the ERP. Distributed receiving usually argues for the front-end.
How do I require receipt confirmation before an invoice can be paid?
Make a recorded receipt a precondition for releasing a PO-backed invoice (a no-receipt-no-pay control) for categories where delivery risk is real. Confirm whether your system enforces this as a hard block or surfaces it as exception context, and set the behavior per category rather than universally.
Nobody records receipts so 3-way match never completes - how do I get requesters to confirm receipt?
Make confirming trivial (a mobile prompt or email reply, not a login), prompt the right person automatically when an invoice is waiting on a receipt, and tie payment to it so confirmation has consequence. Receiving compliance is almost always a friction problem; remove the friction before adding policy.
Can requesters confirm receipt from email or slack instead of logging into a system?
That's the goal - a one-tap confirmation from where they already work, ideally mobile-friendly. Evaluate tools on how little login friction the receiving path carries, because every extra step is a receipt that won't get recorded.
What is the accounting entry when goods are received?
A goods receipt typically debits inventory or expense and credits a GRNI (goods-received-not-invoiced) accrual; the invoice later relieves GRNI and books the payable. Behavior depends on your ERP and whether you run perpetual inventory - confirm how yours posts receipts.
How do I handle receiving for drop-ship orders that go straight to a customer or job site?
The person at the delivery point confirms receipt remotely (photo or signed delivery doc from the site), or you rely on the customer/site acknowledgment as proof. Drop-ship receiving is a remote-confirmation workflow - the control is documented delivery, not a dock scan.
How does receiving work for inventory vs non-inventory purchases?
Inventory receipts update stock quantities and valuation in the ERP and demand quantity accuracy; non-inventory receipts confirm delivery for matching and expense without touching stock. Inventory receiving is tighter by necessity; confirm your ERP handles both paths.
Should low-dollar purchases require receiving at all, or auto-receive?
Auto-receive low-dollar, low-risk purchases (or skip receiving and run 2-way) - the control isn't worth the friction below a sensible threshold. Reserve mandatory receiving for spend where non-delivery or short-ship is a real and material risk.
Stampli perspective
Stampli builds receiving into the P2P workflow rather than leaving it in email or spreadsheets. The right receiver is prompted to confirm delivery, record full or partial quantities at the PO line level, attach proof of delivery, and handle corrections - including from mobile - without working inside the ERP. AP sees received-versus-remaining quantities and proof of delivery during invoice review, and every receiving action is captured with user, timestamp, quantity, and comment in an audit-ready history. Stampli positions receipt confirmation as matching context and exception visibility; specific payment-blocking-on-receipt behavior depends on configuration.