Inventory / Procurement is where ERP discipline either begins or breaks.
Goods Receipt Note (GRN) Recording looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Inventory on-hand accuracy ≥ 99.5%; GRNI liability balance reconciles to outstanding GRNs at month-end; receiving discrepancies are captured at point of receipt, not discovered at invoice matching.
The control flow a finance team actually needs.
Step 1
Partial Receipt Be Supported
Step 2
Over-Receipt Be Blocked Or Require...
Step 3
Rejected Quantity Create A...
Step 4
GRNI Journal Entry Post In The Same...
Step 5
GRN Capture Lot/Serial Numbers When The...
The ERP surface involved.
Module
Inventory / Procurement
Actors
Warehouse Receiver, Procurement System, Inventory System
Tier
Tier 1
Finance area
Procurement & Supplier Management
Region lens
US and UK finance teams
Publication date
April 23, 2026
Partial receipt must be supported (received qty < ordered qty); over-receipt must be blocked or require approval above a configurable tolerance; rejected quantity must create a return-to-vendor record automatically; GRNI journal entry must post in the same transaction as inventory quantity update (ACID); GRN must capture lot/serial numbers when the item is lot-tracked; GRN timestamp must be the inventory valuation date; system must allow GRN within 2 seconds of submission for up to 200 concurrent receivers.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Partial receipt must be supported (received qty < ordered qty | Given an outstanding purchase order with open quantities |
| Control 2 | over-receipt must be blocked or require approval above a configurable tolerance | when a warehouse receiver records received quantities line by line against a GRN with supplier delivery note number |
| Control 3 | rejected quantity must create a return-to-vendor record automatically | then system posts GRN, increments on-hand inventory, creates GRNI accrual journal entry (debit Inventory/GRNI Expense, credit GRNI Liability) in one ACID transaction, and updates PO received_to_date_qty |
| Control 4 | GRNI journal entry must post in the same transaction as inventory quantity update (ACID | negative) when received qty exceeds PO ordered qty beyond tolerance then POST returns 422 with problem+json code OVER_RECEIPT_BLOCKED. |
| Control 5 | GRN must capture lot/serial numbers when the item is lot-tracked | Inventory on-hand accuracy ≥ 99.5%; GRNI liability balance reconciles to outstanding GRNs at month-end; receiving discrepancies are captured at point of receipt, not discovered at invoice matching. |
| Control 6 | GRN timestamp must be the inventory valuation date | Inventory on-hand accuracy ≥ 99.5%; GRNI liability balance reconciles to outstanding GRNs at month-end; receiving discrepancies are captured at point of receipt, not discovered at invoice matching. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Upon delivery from a supplier, a warehouse receiver selects the outstanding purchase order from a mobile or desktop interface, records received quantities line by line (which may be partial), captures the supplier delivery note number, and optionally flags damaged or rejected items with a reason code. The system posts a GRN, increases on-hand inventory for accepted quantities, creates a GRNI accrual journal entry (debit Inventory / debit GRNI Expense, credit GRNI Liability), and updates the PO received-to-date quantity. |
| Control rules | Partial receipt must be supported (received qty < ordered qty); over-receipt must be blocked or require approval above a configurable tolerance; rejected quantity must create a return-to-vendor record automatically; GRNI journal entry must post in the same transaction as inventory quantity update (ACID); GRN must capture lot/serial numbers when the item is lot-tracked; GRN timestamp must be the inventory valuation date; system must allow GRN within 2 seconds of submission for up to 200 concurrent receivers. |
| Acceptance proof | Given an outstanding purchase order with open quantities; when a warehouse receiver records received quantities line by line against a GRN with supplier delivery note number; then system posts GRN, increments on-hand inventory, creates GRNI accrual journal entry (debit Inventory/GRNI Expense, credit GRNI Liability) in one ACID transaction, and updates PO received_to_date_qty; (negative) when received qty exceeds PO ordered qty beyond tolerance then POST returns 422 with problem+json code OVER_RECEIPT_BLOCKED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`goods_receipt_note` { id: string, po_id: string, entity_id: string, supplier_delivery_note: string, received_at: timestamp, status: enum, external_id: string }; `grn_line` { id: string, grn_id: string, po_line_id: string, received_qty: int, rejected_qty: int, rejection_reason: string, lot_number: string, serial_number: string }; `grni_journal_entry` { id: string, grn_id: string, debit_account_id: string, credit_account_id: string, amount_minor: int64, currency_code: char(3), posted_at: timestamp }; (reference, product may differ).API and events
`POST /v1/goods-receipt-notes` { po_id, supplier_delivery_note, lines[{po_line_id, received_qty, rejected_qty, rejection_reason, lot_number}] } -> 201 { id, status, grni_journal_entry_id }; `GET /v1/goods-receipt-notes/{id}`; emits `inventory.grn_posted`, `procurement.grni_accrued` events; idempotent via `external_id`.State transitions
`DRAFT -> POSTED`; terminal `CANCELLED`; guard: POSTED is atomic with GRNI journal entry and inventory increment; over-receipt above tolerance blocked; partial receipt leaves PO line PARTIALLY_RECEIVED.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.