Period Controls is where ERP discipline either begins or breaks.
Soft Close vs. Hard Period Lock Controls 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: Accidental postings to closed periods eliminated; audit trail proves period integrity for auditors; retroactive adjustments require deliberate override with accountability.
The control flow a finance team actually needs.
Step 1
Two-Tier Lock Model: Soft Lock And Hard...
Step 2
Role-Based Lock/Unlock Permissions
Step 3
Lock Status Visible On All Journal...
Step 4
Override Requires Documented Reason And...
Step 5
Retroactive Posting To A Hard-Locked...
The ERP surface involved.
Module
Period Controls
Actors
Controller, System Administrator, GL System
Tier
Tier 0
Finance area
Financial Close, Consolidation & Statutory Reporting
Region lens
US and UK finance teams
Publication date
March 30, 2026
Two-tier lock model: soft lock (restricts non-accounting roles) and hard lock (restricts all users including admins without explicit override); role-based lock/unlock permissions; lock status visible on all journal entry and transaction screens; override requires documented reason and supervisor approval; retroactive posting to a hard-locked period triggers alert to Controller; API endpoints respect lock status and return structured error with period and lock metadata; lock/unlock events written to immutable audit log.
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 | Two-tier lock model: soft lock (restricts non-accounting roles) and hard lock (restricts all users including admins without explicit override | Given a period with posted transactions |
| Control 2 | role-based lock/unlock permissions | when Controller initiates a soft close |
| Control 3 | lock status visible on all journal entry and transaction screens | then normal-role posting attempts to that period return 403 PERIOD_SOFT_LOCKED while accounting-role postings succeed |
| Control 4 | override requires documented reason and supervisor approval | when Controller escalates to hard lock |
| Control 5 | retroactive posting to a hard-locked period triggers alert to Controller | then all postings including accounting staff return 403 PERIOD_HARD_LOCKED with lock metadata |
| Control 6 | API endpoints respect lock status and return structured error with period and lock metadata | Accidental postings to closed periods eliminated; audit trail proves period integrity for auditors; retroactive adjustments require deliberate override with accountability. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At the end of a period, Controller initiates a soft close that restricts normal users from posting to the period while allowing accounting staff to continue with adjustments. Once all adjustments are complete and signed off, Controller escalates to a hard lock that prevents all postings including manual journal entries to that period. Any attempt to post to a locked period generates an error with the lock type, locked-by user, and lock date. System Administrator can unlock a hard-locked period with a required override reason that is recorded in the audit log. |
| Control rules | Two-tier lock model: soft lock (restricts non-accounting roles) and hard lock (restricts all users including admins without explicit override); role-based lock/unlock permissions; lock status visible on all journal entry and transaction screens; override requires documented reason and supervisor approval; retroactive posting to a hard-locked period triggers alert to Controller; API endpoints respect lock status and return structured error with period and lock metadata; lock/unlock events written to immutable audit log. |
| Acceptance proof | Given a period with posted transactions; when Controller initiates a soft close; then normal-role posting attempts to that period return 403 PERIOD_SOFT_LOCKED while accounting-role postings succeed; when Controller escalates to hard lock; then all postings including accounting staff return 403 PERIOD_HARD_LOCKED with lock metadata; when System Administrator unlocks with a documented reason; then an audit log entry records the reason, approver, and timestamp; (negative) when hard-lock override is attempted without documented reason then the system returns 422 OVERRIDE_REASON_REQUIRED. |
| 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
`period_lock` { id: string, entity_id: string, period: string, lock_type: enum(SOFT, HARD), locked_by: string, locked_at: timestamp, unlock_reason: string, external_id: string }; (reference, product may differ).API and events
`POST /v1/period-locks` { entity_id, period, lock_type, external_id } -> 201 { id, lock_type, locked_at }; `DELETE /v1/period-locks/{id}` { override_reason } -> 200; `GET /v1/period-locks?entity_id&period`; emits `period.soft_locked`, `period.hard_locked`, `period.unlocked` events; idempotent via `external_id`.State transitions
`OPEN -> SOFT_LOCKED -> HARD_LOCKED`; terminal states `HARD_LOCKED` (requires explicit unlock); guard: transition OPEN→SOFT_LOCKED requires Controller role; SOFT_LOCKED→HARD_LOCKED requires all soft-close adjustments signed off; unlock of HARD_LOCKED requires override_reason and supervisor role.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.