What gets recorded
When shipment arrives, warehouse or the requester posts a goods receipt (GRN) against the PO line: quantity accepted, date, location, batch or serial numbers if tracked, and sometimes quality inspection results. For services, a service entry or timesheet approval plays the same role.
The GRN does not pay the supplier—it updates inventory or expense recognition and tells AP how much quantity is eligible for invoicing.
Partial and over-receipts
Partial receipts are normal on large POs. AP should only pay invoiced quantity up to received quantity unless policy allows invoice-first for specific vendors. Over-receipts (receiving more than ordered) should block or warn until the PO is increased.
Returns and rejections post negative or reversal receipts so match logic does not think undelivered goods were accepted.
Timing with AP
Invoices often arrive before the warehouse scans the pallet. Exception queues fill with "receipt not found" until GRN posts. Clear SLAs between receiving and AP prevent duplicate supplier reminders.
For drop-ship, the requester may post receipt at the remote site; the process is the same for match even if central warehouse never touches the goods.
Example
PO-5502 orders 200 cartons of lubricant. Truck one delivers 120 cartons; GRN-881 records 120. Supplier invoices 120—three-way match succeeds. A second invoice for 80 before the next delivery should wait until GRN covers the remaining quantity or the PO is closed down.
Operational checklist for goods receipt posting
Set receiving SLAs in business days and measure backlog weekly; AP should see expected receipt dates on held invoices. Train decentralized receivers on partial receipts and return postings.
For services, define who can approve service entry sheets and link them to PO lines. Reconcile inventory subledger to GRN totals monthly to catch posting gaps early.
Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.
Metrics, audits, and rollout for goods receipt notes
Internal audit samples goods receipt notes by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.
Leading indicators for goods receipt notes include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.
Pilot changes to goods receipt notes on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.
Technology helps goods receipt notes only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.
Stakeholder alignment matters: publish a one-page RACI for goods receipt notes that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.
Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear goods receipt notes issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.