General Ledger / Journal Entries is where ERP discipline either begins or breaks.
Reversing Journal Entry 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: The reversal exactly offsets the original entry, both entries are linked in the GL, and net impact on account balances across both periods is zero.
The control flow a finance team actually needs.
Step 1
Reversal Creates New Entry With Dr/Cr...
Step 2
Reversal Date Defaults To First Day Of...
Step 3
Link Between Original And Reversal...
Step 4
Amounts On Reversal Entry Immutable
Step 5
Reversal Blocked If Original Entry...
The ERP surface involved.
Module
General Ledger / Journal Entries
Actors
Accountant, GL System
Tier
Tier 0
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 5, 2026
reversal creates new entry with Dr/Cr swapped; reversal date defaults to first day of next open period; link between original and reversal preserved (bidirectional reference); amounts on reversal entry immutable (block manual edits); reversal blocked if original entry period is closed and reversal date is also in a closed period; reversal entry labeled "REVERSAL OF {original_id}" in description; double-entry balance enforced; audit trail records who triggered the reversal
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 | reversal creates new entry with Dr/Cr swapped | Given a POSTED journal entry in an open period |
| Control 2 | reversal date defaults to first day of next open period | when the accountant triggers create-reversal |
| Control 3 | link between original and reversal preserved (bidirectional reference | then a new POSTED entry with Dr/Cr swapped is created, dated first day of next open period, and both entries display bidirectional references |
| Control 4 | amounts on reversal entry immutable (block manual edits | |
| Control 5 | reversal blocked if original entry period is closed and reversal date is also in a closed period | The reversal exactly offsets the original entry, both entries are linked in the GL, and net impact on account balances across both periods is zero. |
| Control 6 | | The reversal exactly offsets the original entry, both entries are linked in the GL, and net impact on account balances across both periods is zero. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | An accountant identifies a posted journal entry that needs to be reversed - typically an accrual or estimate recognized in one period that should be unwound at the start of the next. The accountant selects the original entry and triggers the "Create Reversal" action. The system generates a new journal entry with all debit and credit amounts swapped, dated the first day of the following period (or a user-specified date), and linked to the original entry by reference. The reversal entry is posted in a single atomic transaction, and both the original and the reversal display their mutual link in the audit trail. Manual modification of a reversing entry's amounts is blocked - only the date may be adjusted. |
| Control rules | |
| Acceptance proof | |
| 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_entries` { id: string, external_id: string, reversal_of_id: string, reversed_by_id: string, entry_type: enum(STANDARD,REVERSAL,ACCRUAL,ALLOCATION,RECLASSIFICATION,AUDIT_ADJUSTMENT,SYSTEM) }; (reference, product may differ).API and events
`POST /v1/journal-entries/{id}/reverse` { reversal_date, reversed_by } -> 201 { id: reversal_entry_id, status: POSTED, reversal_of_id }; `GET /v1/journal-entries/{id}` returns { reversal_of_id, reversed_by_id }; emits `gl.journal_entry.reversed` event; idempotent: second call returns existing reversal_entry_id.State transitions
Original entry gains `reversed_by_id` reference on reversal; reversal entry is born `POSTED`; guard: reversal blocked if original period and reversal date are both in CLOSED periods; amounts on reversal entry immutable after creation.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.