General Ledger / Chart of Accounts is where ERP discipline either begins or breaks.
Chart of Accounts Setup and Maintenance 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: A complete, hierarchical chart of accounts exists for the entity, every account maps to the correct financial statement section, and historical data is preserved even when accounts are archived.
The control flow a finance team actually needs.
Step 1
Account Code Uniqueness Enforced Within...
Step 2
Account Types: Asset, Liability,...
Step 3
Parent-Child Hierarchy For Roll-Up
Step 4
Normal Balance Per Type
Step 5
Soft-Archive For Accounts With Postings
The ERP surface involved.
Module
General Ledger / Chart of Accounts
Actors
Controller, System Administrator, GL System
Tier
Tier 0
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 2, 2026
account code uniqueness enforced within entity; account types: Asset, Liability, Equity, Revenue, Expense (GAAP/IFRS-aligned); parent-child hierarchy for roll-up; normal balance (Dr/Cr) per type; soft-archive for accounts with postings (no hard delete); dimension/segment tagging per account; bulk import via CSV with validation report; change audit trail; prevent type-change on accounts with historical postings without controller override
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 | account code uniqueness enforced within entity | Given an entity with no existing chart of accounts |
| Control 2 | account types: Asset, Liability, Equity, Revenue, Expense (GAAP/IFRS-aligned | when a controller creates an account with a unique code, valid type, and parent code |
| Control 3 | parent-child hierarchy for roll-up | |
| Control 4 | normal balance (Dr/Cr) per type | |
| Control 5 | soft-archive for accounts with postings (no hard delete | A complete, hierarchical chart of accounts exists for the entity, every account maps to the correct financial statement section, and historical data is preserved even when accounts are archived. |
| Control 6 | dimension/segment tagging per account | A complete, hierarchical chart of accounts exists for the entity, every account maps to the correct financial statement section, and historical data is preserved even when accounts are archived. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A controller or system administrator creates the foundational chart of accounts by defining account codes, account names, account types (Asset, Liability, Equity, Revenue, Expense), normal balance (Dr/Cr), and optional parent-child hierarchy for roll-up reporting. Each account is assigned to a segment structure (natural account, department, location, project) for dimension-based filtering. Inactive accounts are archived rather than deleted to preserve historical posting integrity. Any change to account type or normal balance after the first posting triggers a warning and requires controller sign-off. The system enforces uniqueness of account code within the entity and prevents deletion of accounts with any historical posting. |
| Control rules | account code uniqueness enforced within entity; account types: Asset, Liability, Equity, Revenue, Expense (GAAP/IFRS-aligned); parent-child hierarchy for roll-up; normal balance (Dr/Cr) per type; soft-archive for accounts with postings (no hard delete); dimension/segment tagging per account; bulk import via CSV with validation report; change audit trail; prevent type-change on accounts with historical postings without controller override |
| 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
`coa_accounts` { id: string, external_id: string, entity_id: string, account_code: string, name: string, account_type: enum(ASSET,LIABILITY,EQUITY,REVENUE,EXPENSE,STATISTICAL), normal_balance: enum(DEBIT,CREDIT), parent_id: string, status: enum(ACTIVE,ARCHIVED), dimension_requirements: object }; (reference, product may differ).API and events
`POST /v1/chart-of-accounts` { entity_id, account_code, name, account_type, normal_balance, parent_id, dimension_requirements, external_id } -> 201 { id, account_code, status }; `PATCH /v1/chart-of-accounts/{id}` { name, status }; `POST /v1/chart-of-accounts/import` { csv_data } -> 202 { import_id }; `GET /v1/chart-of-accounts/import/{import_id}` -> { status, errors:[{row, code, message}] }; idempotent via `external_id`.State transitions
`ACTIVE -> ARCHIVED`; guard: ARCHIVED accounts reject new postings; type-change on accounts with postings requires controller override; hard DELETE blocked if any journal_entry_lines reference the account.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.