General Ledger / Opening Balances is where ERP discipline either begins or breaks.
Opening Balance Import for New Entity 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 new entity has a fully balanced opening GL, all accounts reflect the correct starting position, and the migration entry is permanently traceable to its source.
The control flow a finance team actually needs.
Step 1
CSV Import With Account Code, Amount...
Step 2
Balance Validation Preview
Step 3
Out-Of-Balance Blocks Import With...
Step 4
Single Atomic Journal Entry For All...
Step 5
Migration Date As Posting Date
The ERP surface involved.
Module
General Ledger / Opening Balances
Actors
Controller, Migration Specialist, GL System
Tier
Tier 0
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 8, 2026
CSV import with account code, amount_minor, currency_code, Dr/Cr flag; balance validation (Σ Dr = Σ Cr) before commit; out-of-balance blocks import with itemized summary; single atomic journal entry for all opening balance lines; migration date as posting date; system-generated entry tag; retained earnings account designation required; support multiple currencies per entity; opening balance entry is not reversible; audit trail records importer identity and source-system reference
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 | CSV import with account code, amount_minor, currency_code, Dr/Cr flag | Given a new entity with no prior postings |
| Control 2 | balance validation (Σ Dr = Σ Cr) before commit | when the controller imports opening balances via CSV with all Dr/Cr balanced |
| Control 3 | out-of-balance blocks import with itemized summary | then a single system-generated journal entry is created and posted with all opening balance lines on the migration date |
| Control 4 | single atomic journal entry for all opening balance lines | |
| Control 5 | migration date as posting date | The new entity has a fully balanced opening GL, all accounts reflect the correct starting position, and the migration entry is permanently traceable to its source. |
| Control 6 | system-generated entry tag | The new entity has a fully balanced opening GL, all accounts reflect the correct starting position, and the migration entry is permanently traceable to its source. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | When a new entity or subsidiary is onboarded, the controller uploads a CSV or enters opening balances for each GL account as of the migration date (typically the first day of the live period). The system validates that the total of all debit-balance accounts equals the total of all credit-balance accounts (the accounting equation: Assets = Liabilities + Equity). Any out-of-balance condition blocks the import and displays a reconciliation summary. Once balanced, the system posts all opening balance entries as a single system-generated journal entry dated the migration date, with a description referencing the source system and migration identifier. The prior-year retained earnings balance is posted to the designated equity account. |
| Control rules | CSV import with account code, amount_minor, currency_code, Dr/Cr flag; balance validation (Σ Dr = Σ Cr) before commit; out-of-balance blocks import with itemized summary; single atomic journal entry for all opening balance lines; migration date as posting date; system-generated entry tag; retained earnings account designation required; support multiple currencies per entity; opening balance entry is not reversible; audit trail records importer identity and source-system reference |
| 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
`opening_balance_imports` { id: string, external_id: string, entity_id: string, migration_date: date, status: enum(PENDING,VALIDATED,POSTED,FAILED), imported_by: string, je_id: string }; `opening_balance_import_lines` { id: string, import_id: string, account_code: string, amount_minor: int64, currency_code: char(3), direction: enum(DEBIT,CREDIT) }; (reference, product may differ).API and events
`POST /v1/opening-balance-imports` { entity_id, migration_date, csv_data, source_system_reference, external_id } -> 202 { id, status: PENDING }; `GET /v1/opening-balance-imports/{id}` -> { status, validation_errors, je_id }; `POST /v1/opening-balance-imports/{id}/commit` { approved_by } -> 200 { status: POSTED, je_id }; emits `gl.opening_balance.posted` event; idempotent via `external_id`.State transitions
`PENDING -> VALIDATED -> POSTED` or `PENDING -> FAILED`; guard: POSTED opening balance entry is not reversible; migration_date must be in an OPEN period; retained_earnings_account_id required in entity config.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.