A dormant corporate account may have little or no recent activity but can still carry access rights, standing instructions, fees or residual balances that create operational risk. 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
A dormant corporate account may have little or no recent activity but can still carry access rights, standing instructions, fees or residual balances that create operational risk. For a UK business, the important point is when that concept changes cash availability, lender compliance, settlement or operating authority.
Treasury should distinguish genuinely dormant accounts from seasonal or contingency accounts, identify dependencies and either close them or apply a documented retention rationale. Management should separate external permissibility from internal policy because an action can be technically available yet still fall outside delegated authority.
How the process works
The operating sequence should move from identification to validation, approval, external action and then confirmation. For this topic, the critical mechanics are: Treasury should distinguish genuinely dormant accounts from seasonal or contingency accounts, identify dependencies and either close them or apply a documented retention rationale.
Timing should be planned backwards from the required result. Notice periods, value dates, processing windows and internal approval deadlines can make a correct instruction operationally late, so the workflow needs a repair margin.
The data and evidence that matter
A defensible record includes last transaction date, balance, account purpose, legal owner, signatories, linked services, standing instructions, bank fees, dependencies and proposed closure action. This is more useful than a generic 'checked' status because it shows what was tested and against which source.
The record should distinguish internal intention from external outcome. An approved request proves what the company intended; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what actually happened.
Where the process can fail
An unused account can retain old users and payment capabilities for years because nobody wants to take responsibility for proving that it is safe to close. The problem usually becomes harder and more expensive to fix as the settlement, testing, maturity or payment date gets closer.
Automation changes the shape of the risk rather than removing it. A wrong threshold, reference or bank detail can be processed consistently at scale, which makes pre-release validation and independent exception reporting essential.
Worked example: test the mechanics
A project account has had no external transaction for 18 months but still has £32,000 and three former project staff on historical authority records. Treasury should not treat inactivity as safety; it should reconcile the balance, remove access and either close the account or document why it must remain.
The figures are illustrative rather than universal terms. In a live case the team should replace every amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or coverage as available.
Governance and control design
Review zero- and low-activity accounts at least periodically and require an owner to justify retention. The procedure should also identify an independent reviewer and fallback owner so the control does not depend on one person being available.
A practical dashboard should monitor accounts with no activity over the review period, residual balances, fees and unresolved closure dependencies. Ageing and threshold trends show where risk is building before a single high-profile failure occurs.
The procedure should also explain what happens when the normal route fails. If the primary bank channel, approver or data source is unavailable, staff need a tested fallback that still preserves the core evidence and control.
Ownership should survive absence and staff turnover. The procedure for dormant corporate bank accounts should state who acts, who reviews, where evidence is stored and how unresolved items are escalated when the normal owner is unavailable.
Documentation should be short enough to use under pressure. A one-page operating checklist can point staff directly to last transaction date, balance, account purpose, legal owner, signatories, linked services, standing instructions, bank fees, dependencies and proposed closure action while the full policy keeps the legal, technical or scheme background.
A separate control review should ask whether accounts with no activity over the review period, residual balances, fees and unresolved closure dependencies still predicts the real exposure after changes in volume, banking structure or financing terms. A dashboard can remain visually stable while risk migrates into an unmonitored field.
A strong control can also reduce unnecessary conservatism. Once last transaction date, balance, account purpose, legal owner, signatories, linked services, standing instructions, bank fees, dependencies and proposed closure action is reliable, treasury can distinguish genuine restrictions from assumptions and may release excess buffers, shorten manual review or use available funding more efficiently.
Editorial Verdict
BanksGB's editorial view is that dormant corporate bank accounts should be managed as a practical cash-and-control issue. A dormant corporate account may have little or no recent activity but can still carry access rights, standing instructions, fees or residual balances that create operational risk. The best process ties the rule to the actual amount, entity, timing and external status instead of 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 happened outside the company and what remains outstanding. If that chain is not visible, the control around dormant corporate bank accounts is weaker than it appears. For this article, the decisive record is last transaction date, balance, account purpose, legal owner, signatories, linked services, standing instructions, bank fees, dependencies and proposed closure action; the control is incomplete if those fields cannot be tied to one dated case and one accountable owner.
Sources
- Association of Corporate Treasurers, treasury resources: https://www.treasurers.org/
- NCSC, Secure your important online accounts: https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security/secure-your-important-online-accounts