General Ledger / Period Management is where ERP discipline either begins or breaks.
Period Close with Hard Lock 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 period is immutably locked, no new postings can corrupt it, the final trial balance matches reconciled sub-ledger totals, and the close audit log is complete for external auditors.
The control flow a finance team actually needs.
Step 1
Sub-Ledger Close Confirmation Gate
Step 2
Hard Period Lock Enforced
Step 3
Back-Posting To Locked Period Blocked
Step 4
Optional Auditor Override With...
Step 5
Close Status Visible Per Period Per Entity
The ERP surface involved.
Module
General Ledger / Period Management
Actors
Controller, GL System, Sub-ledger Systems (AP, AR, Payroll, Fixed Assets)
Tier
Tier 0
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 2, 2026
sub-ledger close confirmation gate (all modules must signal closed before GL close proceeds); hard period lock enforced at DB constraint level; back-posting to locked period blocked with RFC 7807 problem-detail error; optional auditor override with secondary approval + exception log entry; close status visible per period per entity; period re-open requires controller + CFO dual approval
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 | sub-ledger close confirmation gate (all modules must signal closed before GL close proceeds | Given all sub-ledger modules have signaled closed for a period |
| Control 2 | hard period lock enforced at DB constraint level | when the controller initiates period close |
| Control 3 | back-posting to locked period blocked with RFC 7807 problem-detail error | |
| Control 4 | optional auditor override with secondary approval + exception log entry | |
| Control 5 | close status visible per period per entity | The period is immutably locked, no new postings can corrupt it, the final trial balance matches reconciled sub-ledger totals, and the close audit log is complete for external auditors. |
| Control 6 | period re-open requires controller + CFO dual approval | The period is immutably locked, no new postings can corrupt it, the final trial balance matches reconciled sub-ledger totals, and the close audit log is complete for external auditors. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At month-end, the controller initiates the close checklist: all sub-ledger modules (AP, AR, payroll, fixed assets) confirm they have posted and reconciled their batches to the GL. The controller reviews the trial balance for unexplained variances, posts any remaining adjusting entries, then marks the accounting period as closed in the system. The system immediately enforces a hard lock preventing any new journal entry - manual or system-generated - from being posted into that period. Any attempt to back-post triggers a rejection with a descriptive error citing the locked period. The controller may optionally grant a temporary override window for auditor corrections, logged as an exception. |
| Control rules | sub-ledger close confirmation gate (all modules must signal closed before GL close proceeds); hard period lock enforced at DB constraint level; back-posting to locked period blocked with RFC 7807 problem-detail error; optional auditor override with secondary approval + exception log entry; close status visible per period per entity; period re-open requires controller + CFO dual approval |
| 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
`accounting_periods` { id: string, external_id: string, entity_id: string, fiscal_year: int, period_number: int, start_date: date, end_date: date, status: enum(OPEN,CLOSING,CLOSED,LOCKED), closed_by: string, closed_at: timestamptz, override_window_expires_at: timestamptz }; `period_close_checklist` { id: string, period_id: string, module: string, confirmed_by: string, confirmed_at: timestamptz, status: enum(OPEN,CONFIRMED) }; (reference, product may differ).API and events
`POST /v1/periods/{id}/close` { confirmed_by } -> 200 { status: CLOSED }; `GET /v1/periods/{id}/close-checklist`; `POST /v1/periods/{id}/override-window` { approver_ids:[controller,cfo], justification } -> 200 { override_window_expires_at }; emits `gl.period.closed` event; idempotent via period id.State transitions
`OPEN -> CLOSING -> CLOSED`; optional `CLOSED -> OPEN` via dual-approval override window then back to `CLOSED`; guard: CLOSED period rejects new journal posts; LOCKED (statutory) rejects re-open.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.