Accruals Management is where ERP discipline either begins or breaks.
Month-End Accrual Journal Entry Creation and Reversal 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: Accrual-reversal pairs always balanced; no manual reversal entry creation required; recurring accruals reduce close preparation time by eliminating repeat manual work.
The control flow a finance team actually needs.
Step 1
Accrual JE Template With Reversal-Date...
Step 2
Auto-Generation Of Reversal Entry On...
Step 3
Reversal Entry Linked To Original With...
Step 4
Batch Auto-Posting Of Reversals On...
Step 5
For Recurring Accruals That...
The ERP surface involved.
Module
Accruals Management
Actors
Accountant, Accounting Manager, GL System
Tier
Tier 0
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
March 31, 2026
Accrual JE template with reversal-date configuration (next-period-first-day or custom date); auto-generation of reversal entry on approval of original; reversal entry linked to original with bidirectional audit trail; batch auto-posting of reversals on period open with notification; support for recurring accruals that auto-generate each period from a template; amounts support multi-currency with functional-currency equivalent recorded; approval workflow with at-least-two-eyes rule for JEs above configurable materiality threshold; reversal status visible on accrual schedule report.
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 | Accrual JE template with reversal-date configuration (next-period-first-day or custom date | Given an open period and an approved accrual journal entry with reversal_date set |
| Control 2 | auto-generation of reversal entry on approval of original | when Accounting Manager approves the accrual JE |
| Control 3 | reversal entry linked to original with bidirectional audit trail | then the system posts the JE to the current period, auto-generates a mirror reversal entry dated reversal_date in PENDING status linked bidirectionally to the original, and on period open auto-posts all PENDING reversals with notification |
| Control 4 | batch auto-posting of reversals on period open with notification | negative) when a reversal JE is manually deleted before auto-posting then the system returns 409 REVERSAL_DELETION_BLOCKED. |
| Control 5 | support for recurring accruals that auto-generate each period from a template | Accrual-reversal pairs always balanced; no manual reversal entry creation required; recurring accruals reduce close preparation time by eliminating repeat manual work. |
| Control 6 | amounts support multi-currency with functional-currency equivalent recorded | Accrual-reversal pairs always balanced; no manual reversal entry creation required; recurring accruals reduce close preparation time by eliminating repeat manual work. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Accountant opens the accruals module and creates a recurring accrual journal entry with debit and credit lines, GL accounts, amounts, a description, and a reversal flag set to the first day of the next period. On approval by Accounting Manager, the system posts the journal to the current period and simultaneously creates a mirror reversal entry dated the first day of the next period in Pending status. On period open, the system auto-posts all pending reversal entries and notifies the Accountant. Accountant confirms reversals posted correctly and the accrual cycle is complete. |
| Control rules | Accrual JE template with reversal-date configuration (next-period-first-day or custom date); auto-generation of reversal entry on approval of original; reversal entry linked to original with bidirectional audit trail; batch auto-posting of reversals on period open with notification; support for recurring accruals that auto-generate each period from a template; amounts support multi-currency with functional-currency equivalent recorded; approval workflow with at-least-two-eyes rule for JEs above configurable materiality threshold; reversal status visible on accrual schedule report. |
| Acceptance proof | Given an open period and an approved accrual journal entry with reversal_date set; when Accounting Manager approves the accrual JE; then the system posts the JE to the current period, auto-generates a mirror reversal entry dated reversal_date in PENDING status linked bidirectionally to the original, and on period open auto-posts all PENDING reversals with notification; (negative) when a reversal JE is manually deleted before auto-posting then the system returns 409 REVERSAL_DELETION_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
`journal_entry` { id: string, entity_id: string, period: string, type: enum, status: enum, reversal_of_id: string, reversal_date: date, amount_minor: int64, currency_code: char(3), external_id: string }; `journal_entry_line` { id: string, je_id: string, coa_account_id: string, debit_minor: int64, credit_minor: int64, currency_code: char(3), external_id: string }; (reference, product may differ).API and events
`POST /v1/journal-entries` { entity_id, period, type, lines[], reversal_date, external_id } -> 201 { id, status, reversal_entry_id }; `POST /v1/journal-entries/{id}/approve` -> 200 { status: POSTED }; `GET /v1/journal-entries?type=REVERSAL&status=PENDING`; emits `journal_entry.posted` and `journal_entry.reversal_auto_posted` events; idempotent via `external_id`.State transitions
`DRAFT -> PENDING_APPROVAL -> POSTED`; reversal entry `PENDING -> AUTO_POSTED`; terminal `VOID`; guard: POSTED JE cannot be edited; reversal entry auto-posts on period open trigger; deletion of a linked reversal entry blocked.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.