Banking / Account Master is where ERP discipline either begins or breaks.
Bank Account Master Data Management 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: Bank account master is accurate, audited, and tightly linked to the GL, eliminating unauthorized accounts and mis-posted cash transactions.
The control flow a finance team actually needs.
Step 1
Store Bank Account Number Encrypted At...
Step 2
Validate IBAN Checksum And ABA Routing...
Step 3
Enforce Mandatory GL Cash Account Link
Step 4
Require Approval For Create, Account...
Step 5
Multiple Signatories With Signatory Role
The ERP surface involved.
Module
Banking / Account Master
Actors
Finance Administrator, Bank, Approval Workflow
Tier
Tier 1
Finance area
Cash Management, Treasury & Banking
Region lens
US and UK finance teams
Publication date
March 27, 2026
Store bank account number encrypted at rest (AES-256); validate IBAN checksum (ISO 13616) and ABA routing number check digit on entry; enforce mandatory GL cash account link (coa_account_id NOT NULL per ADR-009); require approval for create, account number change, and GL remap; support multiple signatories with signatory role (primary, authorized, view-only); prevent posting to inactive accounts with descriptive error; support multi-currency accounts (one currency_code per account, NOT NULL); maintain full change history with user, timestamp, and changed fields; account list exportable for bank confirmation audit.
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 | Store bank account number encrypted at rest (AES-256 | Given a finance administrator submits a new bank account record with bank name, encrypted account number, routing/IBAN, currency_code, account type, owning entity, and coa_account_id |
| Control 2 | validate IBAN checksum (ISO 13616) and ABA routing number check digit on entry | when the approval workflow completes |
| Control 3 | enforce mandatory GL cash account link (coa_account_id NOT NULL per ADR-009 | then IBAN MOD97 and ABA check-digit are validated on entry, coa_account_id is NOT NULL enforced, the account is ACTIVE and available for posting, and any subsequent account-number or GL-remap change triggers a re-approval cycle |
| Control 4 | require approval for create, account number change, and GL remap | negative) when coa_account_id is absent then the request is rejected with 400 MISSING_MANDATORY_LINK. |
| Control 5 | support multiple signatories with signatory role (primary, authorized, view-only | Bank account master is accurate, audited, and tightly linked to the GL, eliminating unauthorized accounts and mis-posted cash transactions. |
| Control 6 | prevent posting to inactive accounts with descriptive error | Bank account master is accurate, audited, and tightly linked to the GL, eliminating unauthorized accounts and mis-posted cash transactions. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A finance administrator creates a new bank account record by entering bank name, account number (stored encrypted), routing/IBAN/SWIFT, currency, account type (checking, savings, money market), owning legal entity, GL cash account link, and signatory list. A mandatory review workflow routes the new account to the controller for approval. Upon approval the account is activated and becomes available for transaction posting and reconciliation. Changes to account number, routing, or GL link require a re-approval cycle. Deactivated accounts are archived but retained for historical reporting. |
| Control rules | Store bank account number encrypted at rest (AES-256); validate IBAN checksum (ISO 13616) and ABA routing number check digit on entry; enforce mandatory GL cash account link (coa_account_id NOT NULL per ADR-009); require approval for create, account number change, and GL remap; support multiple signatories with signatory role (primary, authorized, view-only); prevent posting to inactive accounts with descriptive error; support multi-currency accounts (one currency_code per account, NOT NULL); maintain full change history with user, timestamp, and changed fields; account list exportable for bank confirmation audit. |
| Acceptance proof | Given a finance administrator submits a new bank account record with bank name, encrypted account number, routing/IBAN, currency_code, account type, owning entity, and coa_account_id; when the approval workflow completes; then IBAN MOD97 and ABA check-digit are validated on entry, coa_account_id is NOT NULL enforced, the account is ACTIVE and available for posting, and any subsequent account-number or GL-remap change triggers a re-approval cycle; (negative) when coa_account_id is absent then the request is rejected with 400 MISSING_MANDATORY_LINK. |
| 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
`bank_account` { bank_account_id: string, entity_id: string, bank_name: string, account_number_encrypted: bytes, routing_code: string, iban: string, currency_code: char(3) NOT NULL, coa_account_id: string NOT NULL, account_type: enum(CHECKING, SAVINGS, MONEY_MARKET), status: enum(PENDING_APPROVAL, ACTIVE, INACTIVE, ARCHIVED), external_id: string }; `bank_account_signatory` { signatory_id: string, bank_account_id: string, user_id: string, role: enum(PRIMARY, AUTHORIZED, VIEW_ONLY) }; (reference, product may differ).API and events
`POST /v1/banking/accounts` { bank_name, routing_code, iban, currency_code, coa_account_id, account_type, signatories, external_id } -> 201 { bank_account_id, status: "PENDING_APPROVAL" }; `POST /v1/banking/accounts/{id}/approve` -> 200 { status: "ACTIVE" }; emits `banking.account_activated` and `banking.account_change_requested` events; idempotent via external_id.State transitions
`PENDING_APPROVAL -> ACTIVE -> INACTIVE -> ARCHIVED`; terminal `ARCHIVED`; guard: posting blocked on INACTIVE/ARCHIVED accounts; account-number or GL-remap change resets to PENDING_APPROVAL.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.