Period-End Accruals & Close is where ERP discipline either begins or breaks.
Accrual for Unbilled Received Goods (Receipt Accrual) 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: Period-end AP balance includes all received-but-uninvoiced liabilities; accrual reversals eliminate double-counting in the following period; external auditors can trace every accrual to a GRN and PO.
The control flow a finance team actually needs.
Step 1
Receipt Accrual Run Scoped To A...
Step 2
Identify GRNs With Status RECEIVED And...
Step 3
Accrual Amount = PO Unit Price Minor ×...
Step 4
Post Accrual JE With Description...
Step 5
Auto-Reverse Accrual In The Opening Day...
The ERP surface involved.
Module
Period-End Accruals & Close
Actors
AP Accountant, Receiving System, ERP Accrual Engine
Tier
Tier 1
Finance area
Accounts Payable & Procure-to-Pay
Region lens
US and UK finance teams
Publication date
March 14, 2026
Receipt accrual run scoped to a specific period-end date and entity; identify GRNs with status RECEIVED and invoice_status = NONE or invoice age > 0 days past period close; accrual amount = PO unit_price_minor × received_qty using functional currency at period-end rate; post accrual JE with description referencing GRN ID and PO number; auto-reverse accrual in the opening day of the next period; prevent double-accrual if accrual JE already exists for the same GRN; accrual report lists all open receipts, amounts, and expected invoice dates; amounts in *_minor + currency_code; full ACID atomicity for accrual batch post.
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 | Receipt accrual run scoped to a specific period-end date and entity | Given GRNs with status RECEIVED and no matching vendor invoice exist at period end |
| Control 2 | identify GRNs with status RECEIVED and invoice_status = NONE or invoice age > 0 days past period close | when the accrual run is triggered for the entity and period |
| Control 3 | accrual amount = PO unit_price_minor × received_qty using functional currency at period-end rate | then one JE per GRN is posted atomically (debit expense/inventory, credit Accrued Payables) with auto_reverse flag set, and re-running the accrual does not create duplicate entries |
| Control 4 | post accrual JE with description referencing GRN ID and PO number | negative) when the period is already locked then accrual posting returns 422 with error code PERIOD_LOCKED. |
| Control 5 | auto-reverse accrual in the opening day of the next period | Period-end AP balance includes all received-but-uninvoiced liabilities; accrual reversals eliminate double-counting in the following period; external auditors can trace every accrual to a GRN and PO. |
| Control 6 | prevent double-accrual if accrual JE already exists for the same GRN | Period-end AP balance includes all received-but-uninvoiced liabilities; accrual reversals eliminate double-counting in the following period; external auditors can trace every accrual to a GRN and PO. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At period end, the accountant triggers an accrued-liability run. The system identifies all warehouse receipts (GRNs) that have been matched against a PO but for which no vendor invoice has yet been received. For each uninvoiced receipt, the system calculates the accrual amount using the PO unit price times received quantity. It posts a journal entry: debit the expense or inventory account, credit the Accrued Payables (receipt accrual) account. When the actual invoice arrives in the next period and is matched, the system reverses the accrual entry and records the final AP liability, eliminating any double-counting. |
| Control rules | Receipt accrual run scoped to a specific period-end date and entity; identify GRNs with status RECEIVED and invoice_status = NONE or invoice age > 0 days past period close; accrual amount = PO unit_price_minor × received_qty using functional currency at period-end rate; post accrual JE with description referencing GRN ID and PO number; auto-reverse accrual in the opening day of the next period; prevent double-accrual if accrual JE already exists for the same GRN; accrual report lists all open receipts, amounts, and expected invoice dates; amounts in *_minor + currency_code; full ACID atomicity for accrual batch post. |
| Acceptance proof | Given GRNs with status RECEIVED and no matching vendor invoice exist at period end; when the accrual run is triggered for the entity and period; then one JE per GRN is posted atomically (debit expense/inventory, credit Accrued Payables) with auto_reverse flag set, and re-running the accrual does not create duplicate entries; (negative) when the period is already locked then accrual posting returns 422 with error code PERIOD_LOCKED. |
| 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
`receipt_accruals` { id: string, grn_id: string, po_id: string, entity_id: string, period: string, accrual_amount_minor: int64, functional_currency_code: char(3), journal_entry_id: string, status: enum(POSTED|REVERSED|PENDING), auto_reverse: bool, external_id: string }; `journal_entries` { id, source_type: ACCRUAL, source_id, auto_reverse: bool, reversal_je_id }; (reference, product may differ).API and events
`POST /v1/ap-accruals/run` { entity_id, period_end_date } -> 202 { job_id, accrual_count }; `GET /v1/ap-accruals` { entity_id, period } -> 200 { accruals: [] }; `GET /v1/ap-accruals/{id}`; emits `ap.accrual.posted` and `ap.accrual.reversed` events; idempotent (re-run skips existing accruals for same grn_id + period).State transitions
`PENDING -> POSTED -> REVERSED`; guard: REVERSED accrual cannot be re-posted; POSTED accrual cannot be manually modified; reversal executes on period_open_date of next period.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.