Bank-account master data is the controlled record of the accounts a group owns and the identifiers, legal ownership and system attributes needed to use them safely. This guide explains the mechanics, evidence, failure points and controls a UK business should understand before relying on the process.
What this means in practice
Bank-account master data is the controlled record of the accounts a group owns and the identifiers, legal ownership and system attributes needed to use them safely. The practical question is whether the company can evidence the condition at the moment a payment, drawdown or hedge decision is made.
The master should be synchronised with bank confirmations, ERP and treasury-system records, but changes should follow an approval workflow rather than allowing each system to drift independently. Translating these mechanics into a short checklist helps only if the checklist still points users back to the authoritative wording and current transaction data.
How the process works
The operating sequence should move from identification to validation, approval, external submission or notice, and then confirmation. For this topic, the critical mechanics are: The master should be synchronised with bank confirmations, ERP and treasury-system records, but changes should follow an approval workflow rather than allowing each system to drift independently.
Timing should be planned backwards from the required result. Notice periods, value dates, bank cut-offs and internal approval windows can make a technically correct action late, so the process needs enough recovery time to repair data or obtain another consent. For this subject, the file should specifically reconcile legal entity, bank, branch, account number or IBAN, currency, status, opening date, closing date, routing identifiers, purpose, system mappings and evidence source. Those fields are not interchangeable with a generic approval record because they are the facts that determine whether this particular transaction remains inside the agreed rule.
The data and evidence that matter
At minimum, retain legal entity, bank, branch, account number or IBAN, currency, status, opening date, closing date, routing identifiers, purpose, system mappings and evidence source. If one of these items is uncertain, the case should remain open rather than being presented as fully resolved.
The record should distinguish internal intention from external outcome. An approved instruction proves what the company wanted to do; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what happened outside the company.
Where the process can fail
A closed or renamed account can remain active in an ERP payment template, or an account can be assigned to the wrong legal entity and distort cash or intercompany reporting. The financial cost of the problem usually increases as the payment, settlement, test date or financing event gets closer.
Fragmented ownership can hide exceptions. Legal, treasury, accounts payable and the bank may each see part of the issue, so one person should own the case until the final external status is known.
Worked example: test the mechanics
A euro account is transferred operationally from one subsidiary to another group entity during a restructuring. If the bank account itself remains legally owned by the original entity but the ERP master is changed immediately, accounting and payment authority can diverge.
The example is intentionally simplified. In a live case the business should replace every illustrative amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or hedging capacity as available.
Governance and control design
Use one governed account master, require documentary evidence for changes and reconcile it periodically to external bank records. Where technology supports it, the rule should be enforced in workflow and exceptions should require explicit approval rather than a warning that can be ignored.
Routine review should include accounts with complete verified master data, unresolved system mismatches and changes awaiting independent approval. Stable top-line activity can otherwise hide growing concentration, stale exceptions or shrinking liquidity headroom.
Change control matters as much as daily operation. When a bank changes a service, a facility is amended, an entity joins the group or a system is migrated, the company should retest the process from source data through final reconciliation. The management signal for this topic is accounts with complete verified master data, unresolved system mismatches and changes awaiting independent approval. That indicator should have an owner and escalation threshold so treasury can intervene while the exposure is still manageable rather than discovering the problem only after the external deadline.
Contingency planning should be proportionate to value and urgency. The team should know the alternate approver, funding route, bank contact or manual fallback before a live bank account master-data controls issue becomes time-critical.
Documentation should be short enough to use under pressure. A one-page operating checklist can point staff to legal entity, bank, branch, account number or IBAN, currency, status, opening date, closing date, routing identifiers, purpose, system mappings and evidence source while the fuller policy keeps the legal, technical or scheme background.
Periodic review should compare the documented procedure with what staff actually do. Where practice has drifted, management should either update the policy deliberately or restore the intended control rather than accept an undocumented compromise.
A tested fallback is part of the control. The team should know which pieces of legal entity, bank, branch, account number or IBAN, currency, status, opening date, closing date, routing identifiers, purpose, system mappings and evidence source are essential to act safely if the preferred system, approver or communication channel is unavailable.
Editorial Verdict
BanksGB's editorial view is that bank account master-data controls should be managed as a practical cash-and-control issue. Bank-account master data is the controlled record of the accounts a group owns and the identifiers, legal ownership and system attributes needed to use them safely. The best process links the rule to the amount, entity, timing and external status rather than relying on shorthand.
The final test is reproducibility. A second person should be able to explain what triggered the action, which evidence was used, who approved it, what the external party did and what remains outstanding. If that chain is not visible, the control is weaker than it appears. The control should also be tested against the article's core failure scenario: A closed or renamed account can remain active in an ERP payment template, or an account can be assigned to the wrong legal entity and distort cash or intercompany reporting. A practical review should demonstrate how the company would recognise that condition early, stop or redirect the transaction, and preserve evidence of the decision.
Sources
- Association of Corporate Treasurers, treasury resources: https://www.treasurers.org/
- Swift, ISO 20022 for corporates: https://www.swift.com/standards/iso-20022/iso-20022-faqs/corporates