My business bank account got closed. Now what?

The letter arrives, or the app simply stops working, and the first instinct is to search for what you did wrong. In the large majority of closures we see, there was no single act of wrongdoing. Banks run continuous portfolio reviews driven by their own regulatory exposure: a correspondent bank tightens its risk appetite for a sector or a corridor, an automated transaction-monitoring system flags a pattern that looks unusual against a static risk model, a periodic KYC refresh surfaces a data mismatch, or the institution simply decides an entire industry or geography no longer fits its risk tolerance and exits the whole book at once.

Account closure letters are deliberately generic — "in accordance with our terms and conditions" or "following a review of our commercial relationship" — because most banking terms and conditions reserve an unqualified right to close an account on notice, and because anti-money-laundering rules in many jurisdictions restrict what a bank can disclose about a suspicious activity report or an internal risk flag without committing a criminal offence themselves (commonly referred to as "tipping off"). That legal architecture means the bank's silence is often compliance-driven, not evasive.

This matters practically because it changes what you should spend your energy on. Chasing an explanation the bank is not permitted to give wastes the days you need for triage. It is more productive to assume the closure sits in one of a handful of buckets — sector de-risking, a corridor or country exposure the bank no longer wants, a documentation or beneficial-ownership mismatch, transaction volumes or patterns that outgrew the account's original profile, or a match against a sanctions or adverse-media screening tool that needs to be resolved — and to build your response and your next application around whichever bucket is most plausible for your business.

There is a second, less discussed driver: correspondent banking contraction. Many regional and challenger banks and EMIs rely on a handful of larger correspondent or settlement banks to move money internationally. When one of those upstream institutions narrows its own risk appetite, it can force dozens of downstream banks to exit entire client segments simultaneously, with almost no discretion left at the local relationship-manager level. If your closure arrived alongside a wave of others in your sector, this is very likely what happened, and it is a strong signal that the fix is a different type of institution, not a different pitch to the same one.

None of this is a guarantee about your specific case — only your bank's file tells the full story, and in a minority of cases there is a genuine compliance concern worth taking seriously (see section 8). But treating the closure as a portfolio event rather than a verdict on your business is the correct starting posture for almost everyone reading this in the first 24 hours.

Understanding the legal boundaries around disclosure helps you ask better questions and stop wasting calls on requests the bank is not able to fulfil. In most jurisdictions, a bank can tell you that your account is closing, the effective date, how remaining funds will be returned, and whether the closure is immediate or on notice. It can generally confirm whether the decision relates to your KYC file being incomplete or outdated, since that is an administrative fact rather than a suspicion.

What a bank typically cannot tell you — often by law, not by choice — is whether a suspicious activity report has been filed, the specific transaction or counterparty that triggered a review, or the internal risk score that led to the decision. Front-line staff at call centres frequently know nothing more than "closed per compliance review" because the decision is made by a separate team that does not communicate reasoning downstream, partly to prevent exactly this kind of disclosure happening inadvertently.

It is worth explicitly asking three things in your first written communication with the bank: (1) confirmation of the effective closure date and any grace period before the account is fully disabled, (2) the mechanism and expected timing for returning any remaining balance, and (3) whether there is a formal complaints or escalation process, since many jurisdictions require banks to have one and to respond within a set number of business days. Put the request in writing (email, secure message, or a letter sent with proof of delivery) rather than relying on a phone call, because you will want a paper trail for both fund recovery and for explaining the closure to your next bank.

Do not expect an appeal to reverse a portfolio-level exit. If the closure is part of a sector-wide de-risking exercise, no amount of additional documentation will change the bank's underlying risk appetite — that decision was made above the branch or relationship-manager level. Escalation is worth pursuing when funds are held longer than the bank's own stated timelines, when the closure appears to be a data or identity mismatch that is genuinely correctable, or when you have reason to believe the account was flagged in error (for example, a false-positive sanctions name match, which is common and usually resolvable within days once raised formally).

One caution: do not threaten legal action, regulatory complaints, or reputational damage in your first message. Banks record all communications, and an aggressive tone at this stage tends to slow fund release and gets noted in files that can be shared with other institutions through industry-wide fraud and risk databases. A calm, documented, factual approach protects both the funds and your reputation with the next bank.

The instinct is to panic-call every bank you can think of. Resist it for the first few hours and instead build a single-page status document: current balance and where it sits, every recurring payment tied to the account (payroll, tax, rent, suppliers, card processors, loan repayments), every incoming payment expected in the next 30 days and from whom, and every service (card issuing, payroll provider, accounting software, payment gateway) that authenticates against this account. This document is what you will hand to your accountant, your team, and your next bank, and building it first prevents the classic mistake of solving the loudest problem while missing a quieter, larger one.

Payroll is priority one because employment law in most jurisdictions treats missed wages as a serious and sometimes personally liable failure for directors, regardless of the reason. If payroll is due within the closure notice window, initiate a same-day conversation with an interim provider — many electronic money institutions can open a functional business account for payroll and supplier payments within days where a full bank would take weeks, precisely because their onboarding is digital-first and their risk model is built for exactly this kind of urgent, short-notice need. Treat this as a bridge, not a permanent solution; move to fuller banking once the dust settles.

Priority two is anything that triggers automatic penalties for non-payment: tax remittances, statutory filings tied to bank confirmation, loan covenants, and lease payments with default clauses. Contact each counterparty proactively rather than letting a payment silently fail — most tax authorities, landlords and lenders will grant a short administrative extension if you tell them before the due date rather than after. Silence reads as default; a phone call reads as an operational hiccup.

Priority three is your payment acceptance and card infrastructure. If your merchant acquirer, card issuer, or payment gateway settles into the closed account, incoming customer payments can start bouncing or, worse, get held in limbo by the processor while it looks for a valid settlement account. Update settlement details with every processor the moment you have an interim account live, and notify major counterparties and repeat customers of a temporary change in payment instructions through a verified channel — never over email alone, since payment-redirection fraud spikes precisely during these transitions and your own customers may be targeted by scammers impersonating you.

Priority four, and genuinely last, is anything reputational: updating your website's payment details, informing minor suppliers, or explaining the situation to investors. These matter, but they do not carry legal or contractual penalties on the same short clock as payroll, tax, and settlement, and rushing to explain before you have a plan tends to create more anxiety among stakeholders than a brief, calm update once the interim arrangement is live.

Most closed accounts do not lose the money in them — they hold it. Banks in most jurisdictions are legally required to return client funds even after closing an account, but the mechanism and timeline vary widely and are rarely explained upfront. A straightforward closure with no compliance flag typically results in a cheque or wire transfer to a nominated account within one to a few weeks of formal request. A closure connected to a compliance review can extend the hold to 30, 60, or in rarer cases 90-plus days while the bank completes its own internal reporting obligations, and it is legitimate for it to do so even though it is frustrating.

To speed this up, submit a written request for the balance immediately, specifying the exact destination account (which should ideally already be open and functioning — see the interim rails discussion in section 3), and ask explicitly for the bank's stated service-level timeline for fund returns so you have something concrete to escalate against if it slips. Some banks will only release funds via cheque to a registered business address rather than by wire, particularly where they want a physical paper trail; ask early so you are not surprised by a cheque arriving weeks later than a wire would have.

If the hold period is unusually long or the bank stops responding, escalate in writing to the bank's formal complaints department (required to exist and respond within statutory timeframes in most regulated jurisdictions), and, if that produces nothing after the stated response window, to the relevant financial ombudsman or banking regulator in that jurisdiction. Regulators generally cannot force a bank to reopen an account, but they can and do intervene on unreasonably delayed fund releases, since holding client money indefinitely without cause is itself a regulatory breach.

Where balances are meaningful — six figures or more — it is worth engaging counsel or an advisory firm experienced in exactly this kind of recovery early rather than after months of frustration, because a professionally drafted formal demand letter referencing the bank's own terms and conditions and the applicable regulatory framework materially shortens typical release timelines in our experience. This is general information rather than legal advice, and the right approach depends on the jurisdiction, the bank, and the specific facts of your file.

One structural point worth internalising for the future: funds held in a segregated safeguarding account at a well-run electronic money institution are typically easier and faster to recover in a closure scenario than funds in a traditional bank's general ledger, because safeguarding rules require the institution to keep client money identifiably separate from its own balance sheet at all times. This is one of several reasons a mixed banking architecture (covered in section 10) reduces both the likelihood and the severity of this exact problem recurring.

Every next bank you apply to will ask, directly or indirectly, why your last account closed. How well you can answer that question — calmly, specifically, with supporting paper — is one of the single biggest determinants of how quickly you get banked again. Start the documentation file the day the closure notice arrives, not weeks later when memories and message threads have gone stale.

The file should contain: the original closure notice or communication in full, any follow-up correspondence with the bank including timestamps, a written summary in your own words of the sequence of events (when the account was opened, how long it operated without incident, what if anything changed before the closure, and what the bank did or did not say), confirmation of the final balance and how and when it was returned, and — where relevant — evidence that any compliance concern raised was addressed or was a false positive (for example, a sanctions-screening false match resolved with a written clearance from the bank).

Avoid speculation in this document. Write only what you know to be fact and what is evidenced in writing. A file that says "the bank gave no reason, our transaction volumes and counterparties were unchanged from account opening, and the balance was returned in full within 21 days with no funds withheld" reads to an underwriter as a clean, explainable, low-risk closure. A file full of guesses about what the bank "must have thought" reads as uncertainty, and underwriters price uncertainty as risk.

If your industry experienced a wave of similar closures around the same time — common in crypto, gaming, forex, and other sectors subject to periodic de-risking cycles — gather public reporting or industry commentary confirming that pattern. Being able to say "this was part of [Bank]'s broader exit from [sector] in [period], evidenced by [source]" is a materially stronger position than an unsupported claim that the closure was unrelated to your specific business, because it gives the next underwriter an external anchor rather than only your word.

Keep this file even after you are successfully re-banked. A second closure years later, or a routine periodic KYC refresh at any future bank, may ask about historical account history going back further than you expect, and having the original documentation ready saves days of reconstructing events from memory under time pressure.

The instinct to leave a previous closure off a new application is understandable and almost always a mistake. Banks and EMIs share information through industry databases, correspondent references, and increasingly through automated checks against public registers and adverse-media tools. If an underwriter finds an undisclosed prior closure mid-review, the application is very likely to be declined — not necessarily because of what caused the original closure, but because omission itself is treated as a red flag about the applicant's candour, which is the single trait underwriters weigh most heavily.

The right approach is proactive, concise, factual disclosure, ideally in the application's business narrative or cover letter rather than buried in an answer to a direct question you hope is not asked. State plainly: which institution, roughly when, the stated or inferred reason if known, that funds were recovered in full (state the actual timeline), and — critically — what has changed or been reinforced in your compliance posture since. Underwriters read this kind of disclosure as evidence of a well-run business that had one difficult episode, which is a completely different signal from a business that is hiding something.

Do say: the facts, dates, and amounts; that the bank did not allege wrongdoing (if true and evidenced); that funds were returned in full; that your business model, ownership, and activity are unchanged and documented; and that you have since diversified your banking to reduce concentration risk. This last point specifically reassures an underwriter that you understand why concentration is dangerous and have taken a concrete step to address it.

Do not say: anything you cannot evidence, speculation about the bank's motives framed as fact, complaints about how unfairly you were treated (even if true, this reads as a relationship risk rather than a financial one), or language suggesting the closure was random or inexplicable when in fact a plausible driver exists and you are choosing not to name it. Underwriters have seen thousands of these narratives; vagueness reads as evasion far more often than founders expect.

Where the underlying driver was genuinely a sector-wide de-risking event rather than anything specific to your file, say so explicitly and, where possible, reference it. "[Bank] closed a substantial number of accounts in the [sector] segment during [period] as part of a broader risk-appetite change; our account was one of them, our balance was returned in full, and our operating history and ownership are unchanged" is a strong, specific, checkable statement that tends to move an application forward rather than stall it.

There is a meaningful difference between the disclosure that is prudent for approval odds (section 6) and the disclosure that is legally required. Most account application forms ask directly whether you have had a business account closed, declined, or restricted in the past, sometimes with a specific look-back period. Answering that question inaccurately is not a grey area — it can constitute a false statement on a regulated financial application, with consequences that range from an immediate account closure once discovered to, in serious or repeated cases, referral to a financial crime unit.

The safe rule is: answer every direct question on the application form completely and accurately, and use the narrative sections of the application (business description, source of funds, additional information) to provide context and mitigation rather than to soften or omit the fact itself. A direct question answered honestly, followed by a well-constructed explanation, is a fundamentally different risk profile in an underwriter's eyes than an evasive or inaccurate answer discovered later through a database check.

Directors and beneficial owners should also expect that a closure at one company can surface during due diligence on a different company they control, since KYC checks increasingly run against the individual, not just the entity. If you operate multiple companies, prepare a consistent version of the closure narrative across all of them — inconsistent explanations for the same event across related entities are one of the fastest ways to convert a manageable disclosure into a declined application across your entire group.

Where the original closure involved any suggestion of a compliance concern rather than a pure portfolio exit, it is worth having that addressed formally before reapplying — a written clearance letter from the original bank confirming no ongoing concern, a legal opinion addressing a specific regulatory question, or evidence that a flagged transaction was fully explained and closed out. Reapplying without resolving an open compliance question tends to produce a repeat decline at the next institution, because most underwriting teams will not accept an unresolved flag regardless of how the rest of the file looks.

This section describes general practice across the jurisdictions and institution types we work with; it is general information and not legal advice, and specific disclosure obligations vary by jurisdiction, licence type, and the wording of the particular application form in front of you. Where the stakes are high — a large balance, multiple entities, or a genuine compliance question in the file — a short scoping conversation before you submit anything is usually cheaper than a decline.

It would be dishonest to suggest every closure is blameless de-risking. A minority genuinely trace back to a real compliance issue: incomplete or inconsistent beneficial-ownership disclosure, transaction patterns that looked like structuring (splitting payments to stay under reporting thresholds), commingling of personal and business funds at a scale that obscured the true nature of transactions, or activity that strayed materially from what was declared at account opening without informing the bank.

If any of this describes your situation, the honest first step is an internal review, ideally with an accountant or compliance adviser, before any reapplication. Identify precisely what happened, whether it was a genuine breach or a defensible misunderstanding, and what has concretely changed to prevent recurrence. Underwriters at the next institution are far more forgiving of a specific, owned mistake with visible remediation than of a vague denial that does not match what a database check will eventually surface.

Remediation that actually moves the needle includes: engaging a bookkeeper or fractional CFO to formalise financial controls, obtaining updated beneficial-ownership documentation and keeping it current going forward, implementing basic transaction-monitoring discipline even at small scale (flagging your own unusual payments before a bank's system does), and, where a specific transaction or counterparty caused the issue, terminating that relationship and documenting why.

Be realistic about timelines and options in these cases. A business with a genuine, resolved compliance issue in its recent history should expect a narrower initial set of banking options — likely starting with an EMI or specialist high-risk-tolerant institution rather than a tier-one bank — and a period of clean operating history before broader options reopen. This is a realistic trajectory based on typical outcomes we see, not a guarantee, and every institution makes its own independent decision regardless of how the file is presented.

What does not work, in our experience, is minimising or reframing a genuine issue as an unrelated portfolio decision. Compliance teams at receiving institutions are experienced at distinguishing the two, and a mismatch between the narrative offered and what their own screening tools surface is more damaging than the original issue would have been if disclosed candidly.

The single highest-leverage change most businesses can make after a closure is to stop treating banking as a solved problem once one account is open. Concentration risk — holding all operating funds, payroll, and settlement in one relationship — is the structural cause of most banking crises, independent of the specific reason any one account closes. A resilient architecture typically separates functions across at least two, and often three, relationships from the start: an operating account for day-to-day payroll and supplier payments, a settlement or collections account for customer receipts (particularly important if you use card acquiring or a payment gateway), and a reserve or treasury relationship that is not touched day to day and therefore attracts less transaction-monitoring attention.

Diversifying by institution type, not just by institution, adds real resilience. A traditional bank, an electronic money institution, and — for businesses with international flows — a specialist cross-border payments provider each carry different risk appetites, different regulatory regimes, and different correspondent banking dependencies. A sector-wide de-risking wave at traditional banks does not usually hit EMIs the same way, and vice versa, so holding relationships across categories genuinely reduces the odds that one triggering event takes out your entire banking stack simultaneously.

Build the second and third relationships while the first is healthy, not after it closes. This sounds obvious and is nonetheless the step almost everyone skips, because opening a backup account while the primary one is working feels like unnecessary effort. In practice, the marginal cost of maintaining a second dormant-but-active relationship — a small recurring transaction to keep it live, periodic KYC refreshes kept current — is trivial compared with the cost of scrambling to open one during a payroll-week crisis with a closure already on your record.

Keep your compliance file evergreen even when nothing is wrong: current beneficial-ownership documentation, an up-to-date business description that reflects what you actually do now rather than what you did at incorporation, and a clean, explainable transaction history with documentation for anything unusual as it happens rather than reconstructed later. Businesses that treat ongoing KYC refreshes as a minor annoyance to be delayed are disproportionately represented among sudden, unexplained closures, because an outdated file is itself a common trigger for automated risk-scoring systems to flag an account for review.

Finally, review your banking architecture on a fixed schedule — annually is reasonable for most businesses, more often for those in higher-scrutiny sectors — rather than only reactively after a problem. Ask whether your current mix of institutions still matches your actual transaction volumes, corridors, and counterparties, and whether any single relationship has grown to represent an uncomfortable share of total flow. This is precisely the exercise we run with clients as part of ongoing advisory work, because the architecture that was right at account opening rarely stays right as a business grows.

We work with founders and finance teams at the exact moment described in this guide: an account has closed, funds may be held, payroll is due, and the immediate need is a working interim solution alongside a properly built plan for what comes next. Across more than ten years and over 600 accounts opened for clients, closures like this are one of the most common reasons businesses first come to us, and the response is usually the same in shape even where the details differ.

In the first days, we help identify and position an interim electronic money institution relationship suited to your transaction profile so payroll, suppliers, and settlement have somewhere to run within days rather than weeks, while the closed account's balance recovery is pursued in parallel through formal written channels. We do not treat the interim account as the end state — it is the bridge that buys time to build the right permanent architecture properly.

In parallel, we help build the documentation file described in sections 5 through 7: a clean written account of what happened, evidence the balance was recovered, and a disclosure narrative calibrated for the specific institutions we then approach on your behalf across our network of 120-plus banking and payment partners spanning 19 jurisdictions. Because we see closure patterns across many clients and sectors simultaneously, we often know within days whether a given closure was part of a broader institutional exit — which materially changes both the narrative and which institutions are realistic targets.

Where the closure touched on a genuine compliance question rather than a pure portfolio exit, we coordinate with legal and accounting specialists to get that question properly resolved before any reapplication goes out, because reapplying with an open flag tends to waste the goodwill of the next institution rather than preserve it.

We do not guarantee that any specific bank will approve any specific application — no adviser honestly can, since every institution makes an independent underwriting decision — but we do commit to positioning your file with the institutions whose current risk appetite genuinely matches your business, and to building the multi-relationship architecture that makes a repeat crisis far less likely. Engagements are scoped and quoted individually based on your situation; this guide is general information and not legal or tax advice.