Goods Receipt
Goods receipt is the process by which a company takes in delivered goods, checks them against the purchase order and the delivery note, and posts them to inventory. It links procurement to inventory management and is the prerequisite for correct invoice verification.
Goods receipt is the operational process by which a company physically takes in delivered goods, checks them against the associated purchase order and delivery note, and then posts them to inventory. It is the interface between the external procurement market and internal warehouse operations: only with goods receipt does an ordered quantity become available, accounted-for stock. The term denotes the process, the responsible organizational unit (the goods-receiving zone or department), and the physical area in which the acceptance takes place, all at once.
Technically, goods receipt is more than merely accepting a delivery. It includes the inspection of quantity and quality, recording in the system, posting to stock, and putaway to the designated storage location. At the same time, it triggers downstream processes: updating open purchase orders, releasing the item for invoice verification and, in the event of discrepancies, complaint or clarification processes. In the ERP system, goods receipt is therefore not an isolated step but a central link in the process chain spanning purchasing, inventory management and accounts payable.
At a glance
- Acceptance, inspection and posting of delivered goods – the bridge between procurement and the warehouse
- Core checks: quantity and item against the purchase order, condition and quality of the goods
- Only the posted goods receipt turns the quantity into available, valued stock
- Basis for the three-way match in invoice verification (purchase order, goods receipt, invoice)
- In the ERP, interlinked with purchasing, inventory management, batch/serial numbers and financial accounting
What is goods receipt – and what does it involve?
Goods receipt bundles all tasks between the physical delivery and completed putaway. It begins with goods acceptance: the carrier or parcel service hands over the shipment, which is roughly checked for outward completeness and visible transport damage and acknowledged with a proof-of-delivery document. This is followed by the actual goods receipt inspection, in which the delivery is reconciled against the purchase order and delivery note – by item, quantity and condition. Only once this check has been passed is the goods posted to stock and put away to its storage location.
Goods receipt also covers the handling of discrepancies. Short quantities, incorrect deliveries, damaged or qualitatively defective goods are documented and trigger a complaint to the supplier. Depending on the rules, the affected goods are blocked, returned or accepted under reservation. This clean recording matters because goods receipt provides the data basis for later invoice verification and for inventory valuation.
Planned and unplanned goods receipt
The standard case is the planned goods receipt: it is based on a purchase order against which it is checked and posted. Alongside it, there is the unplanned or order-less goods receipt – for example with free samples, returns from sales, or deliveries without a prior order. Such receipts must be assigned manually in the system or recorded as a separate transaction so that stock remains correct nonetheless. Goods receipts from in-house production (completion confirmation) are also handled similarly in posting terms.
How the goods receipt process runs
The operational sequence follows a recurring chain. After acceptance, the employee identifies the delivery using the delivery note or the order number and calls up the matching open purchase order in the ERP system. The delivered quantity is then recorded per line item – increasingly by barcode or RFID scan directly at the goods-receiving station. The system compares actual and target quantities, flags over- or under-deliveries and, where needed, proposes partial quantities for remaining deliveries.
Once the inspection is complete, the goods receipt is posted. This increases the stock of the item concerned, the open order quantity decreases accordingly, and the transaction is released for invoice verification. In parallel, the system prints or issues storage-location or putaway orders so that the goods physically reach their location. For items subject to inspection, the quantity is first posted to a blocked or quality-inspection stock and only released once the inspection has been passed.
Quantity inspection and quality inspection
A distinction is made between quantitative and qualitative inspection. The quantity inspection determines whether the item and unit count correspond to the purchase order; it is mandatory for almost every goods receipt. The quality inspection examines condition, dimensions or function – depending on the goods, as a full inspection or as a sample. In many industries, recording the batch, best-before date or serial number is additionally required so that traceability and later stock withdrawal by methods such as FIFO are ensured.
Why goods receipt matters
Goods receipt determines the reliability of all inventory data. If posting here is done incorrectly, too late or not at all, the system stock and actual stock diverge – with consequences for sales, planning and stocktaking. A clean goods receipt is therefore the basic prerequisite for correct inventory management and for meaningful metrics such as stock coverage or inventory turnover.
Economically, goods receipt is also the point at which financial claims are checked. Only what was actually and faultlessly delivered may be paid. The documented goods receipt therefore, together with the purchase order and incoming invoice, forms the three-way match that prevents missing and duplicate payments. The process is legally relevant too: commercial-law duties to examine and give notice of defects require defects to be identified and reported without delay so that warranty claims are preserved.
Goods receipt in the ERP system
In the ERP system, goods receipt is a posting transaction that builds on shared master data and connects several modules. It references the purchase order from purchasing, draws on the item master for units and inspection specifications, and updates inventory management. The posted quantity increases stock, changes the cost price when valued by moving average, and provides financial accounting with the basis for the accounts-payable liability.
The advantage of this integration lies in eliminating media discontinuities: a single posting transaction updates stock, open purchase orders and invoice verification simultaneously. Modern systems support mobile capture by scanner, automatic storage-location proposals and rules for blocked stock. For connecting to suppliers – for instance advised deliveries via a despatch advice or the import of shipment data – ERP systems use interfaces, often an API or EDI. In more complex warehouses, a specialized WMS partly takes over physical control and reports the goods receipt back to the ERP.
GoBD and auditability
Because goods receipt is relevant to stock and value, its recording in the DACH region is subject to the principles of proper accounting. Under the GoBD, postings must be timely, immutable and auditable. A subsequent correction of a posted goods receipt must not overwrite the original posting without trace, but must be logged as a reversal or correction posting. An ERP system reflects this through a complete document chain and change history.
Distinction: goods receipt, goods acceptance and goods receipt inspection
The terms goods receipt, goods acceptance and goods receipt inspection are often conflated, but they refer to different sub-steps. Goods acceptance is the purely physical act of taking in and acknowledging the shipment. The goods receipt inspection (or check) is the control step in which quantity and quality are reconciled against the purchase order and delivery note. Goods receipt as the umbrella term encompasses both steps along with the subsequent stock posting and putaway.
Goods receipt is also to be distinguished from goods issue, its counterpart in shipping, and from the goods receipt ledger of earlier days, which is today replaced in the ERP by stock movements and documents. The distinction from invoice verification is important: goods receipt clarifies whether and what was delivered; invoice verification clarifies whether and at what amount payment is due. Both access the same transaction but pursue different purposes.
Example
Example: Wholesaler speeds up goods receipt with scanners
A mid-sized wholesaler long accepted deliveries on paper. An employee compared the delivery note by hand against a printout of the purchase order, noted quantities and entered them into the system later. This cost time, led to delayed postings and to differences between system and actual stock – fast movers were sometimes marked as "not available" in the shop even though the goods were already on the ramp.
After introducing an integrated goods receipt in the ERP, the employee scans the order number at the receiving station and then each line item by barcode. The system shows target and actual quantities in real time, flags over- and under-deliveries, and posts the stock immediately on completion of the inspection. Batches and best-before dates are captured directly alongside. The result: up-to-date stock levels without delay, fewer mis-postings and automatic release for invoice verification via the three-way match.
Frequently asked questions
Matching ERP systems
Related services
Questions about Goods Receipt in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.