Platform - Master Data Management is where ERP discipline either begins or breaks.
Master Data Management - Chart of Accounts Governance 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: Zero orphaned GL entries; auditors trace every account to its governing approval; CoA standardized across all entities reduces consolidation mapping errors to zero.
The control flow a finance team actually needs.
Step 1
Account Code Uniqueness Enforced Within...
Step 2
Account Type Hierarchy Is Immutable Per...
Step 3
Deactivation Blocked If Account Has...
Step 4
Account Creation/Change Written To...
Step 5
CoA Import Standard Templates
The ERP surface involved.
Module
Platform - Master Data Management
Actors
Controller, Finance Administrator, Auditor
Tier
Tier 0
Finance area
Platform, Integration, Security, Administration & Analytics
Region lens
US and UK finance teams
Publication date
June 24, 2026
Account code uniqueness enforced within entity; account type hierarchy (asset, liability, equity, revenue, expense) is immutable per account; deactivation blocked if account has transactions in open periods; account creation/change written to audit log with approver; CoA import supports standard templates (GAAP, IFRS, industry-specific); maximum CoA depth of 7 levels; account search by code, name, and type with ≤100 ms response; XBRL taxonomy mapping stored per account for regulatory export; bulk CoA update via governed import with preview before commit.
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 a CoA with account code format N-NNNN |
| Control 2 | account type hierarchy (asset, liability, equity, revenue, expense) is immutable per account | when a Controller creates a new account with a code that duplicates an existing account within the entity, then 409 DUPLICATE_ACCOUNT_CODE is returned |
| Control 3 | deactivation blocked if account has transactions in open periods | when a Controller attempts to deactivate an account with open transactions in the current period, then 409 ACCOUNT_HAS_OPEN_TRANSACTIONS is returned |
| Control 4 | account creation/change written to audit log with approver | negative) when an account is successfully created and routed for approval, then it is PENDING_APPROVAL until approved and not available for journal entries |
| Control 5 | CoA import supports standard templates (GAAP, IFRS, industry-specific | when approved, it transitions to ACTIVE and is immediately usable. |
| Control 6 | maximum CoA depth of 7 levels | Zero orphaned GL entries; auditors trace every account to its governing approval; CoA standardized across all entities reduces consolidation mapping errors to zero. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Controller requests a new GL account via a governed workflow; the system validates the account number format against the entity's CoA numbering scheme, checks for duplicates, and routes for approval if the account type is revenue or COGS. On approval, the account is activated and available for journal entries immediately. Inactivating an account checks for open transactions and blocks deactivation if any exist. Account renaming is logged with before/after values. CoA template changes propagate to child entities with a preview diff and explicit confirmation. Export to XBRL taxonomy mapping is available for regulatory filing. |
| Control rules | Account code uniqueness enforced within entity; account type hierarchy (asset, liability, equity, revenue, expense) is immutable per account; deactivation blocked if account has transactions in open periods; account creation/change written to audit log with approver; CoA import supports standard templates (GAAP, IFRS, industry-specific); maximum CoA depth of 7 levels; account search by code, name, and type with ≤100 ms response; XBRL taxonomy mapping stored per account for regulatory export; bulk CoA update via governed import with preview before commit. |
| Acceptance proof | Given a CoA with account code format N-NNNN; when a Controller creates a new account with a code that duplicates an existing account within the entity, then 409 DUPLICATE_ACCOUNT_CODE is returned; when a Controller attempts to deactivate an account with open transactions in the current period, then 409 ACCOUNT_HAS_OPEN_TRANSACTIONS is returned; (negative) when an account is successfully created and routed for approval, then it is PENDING_APPROVAL until approved and not available for journal entries; when approved, it transitions to ACTIVE and is immediately usable. |
| 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_account` { account_id: string, entity_id: string, account_code: string, name: string, account_type: enum(ASSET,LIABILITY,EQUITY,REVENUE,EXPENSE), parent_account_id: string, status: enum(PENDING_APPROVAL,ACTIVE,INACTIVE), xbrl_mapping: string, external_id: string }; unique constraint on (entity_id, account_code); (reference, product may differ).API and events
`POST /v1/coa-accounts` { account_code, name, account_type, parent_account_id } -> 201 { account_id, status }; `GET /v1/coa-accounts/{account_id}`; `GET /v1/coa-accounts?entity_id=&type=&search=`; `PATCH /v1/coa-accounts/{account_id}` { status: INACTIVE } -> 200 or 409; `POST /v1/coa-accounts/import` { template_id, file } -> 202; emits `coa.account_created`, `coa.account_deactivated` events; idempotent via `external_id`.State transitions
`PENDING_APPROVAL -> ACTIVE`; terminal `INACTIVE`; guard: deactivation blocked if account has open-period transactions; account_type hierarchy immutable once set; code uniqueness enforced within entity.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.