A bank account restriction can feel backwards.
The customer sees a legitimate payment arrive, access changes or a transaction is delayed, and only then comes a request for documents or explanation.
But there is no single universal banking sequence of “freeze first, ask later”.
The safer explanation is narrower: financial institutions conduct ongoing customer due diligence and transaction monitoring, and a change or inconsistency in activity can trigger review, requests for information and — depending on law, contract, institution and circumstances — restrictions on some activity.
A restriction does not prove money laundering.
Silence from a bank does not prove that a suspicious activity report exists.
And a compliance review is not the only reason an account or payment can be restricted.
Three key takeaways
- Onboarding is not the end of KYC. Banks and other regulated firms maintain ongoing monitoring and can revisit customer information when activity or risk changes.
- A review, information request or restriction is not proof of wrongdoing. Fraud controls, sanctions, operational issues, commercial policy and other causes can produce similar customer experiences.
- The best preparation is an accurate, current business narrative with evidence. Customer profile, ownership, expected flows, source of funds and source of wealth where relevant should evolve with the real business.
Why banks revisit customers
UK AML rules and FCA supervision are built around continuing, risk-based customer due diligence rather than a one-time identity check.
HMRC’s anti-money-laundering guidance describes ongoing monitoring as reviewing customer due-diligence information and beneficial ownership, scrutinising transactions and, where appropriate, examining source of funds.
Triggers can include changed circumstances or transactions that appear unusual or inconsistent with what is known about the customer.
The logic is simple.
A business onboarded three years ago may no longer be the same business.
Its owners may have changed.
Its markets may have changed.
Its transaction size may have changed.
Its counterparties may have changed.
The institution’s risk information may also have changed.
Ongoing review exists because a static customer file cannot describe a changing customer forever.
A practical scenario
Consider a consulting company with a low-volume account.
For two years it receives ordinary monthly payments from a small number of known clients.
Then the business wins a large project.
A customer in a new country pays an amount several times larger than the company’s normal monthly inflow.
The payment is legitimate.
But from the bank’s perspective, several facts changed at once:
- amount;
- customer;
- geography; and
- expected activity.
A review or request for explanation would not itself imply wrongdoing.
It may simply mean that the actual transaction no longer fits the profile on file.
The company is in a far better position if it already has the contract, invoice, customer information and source-of-funds narrative needed to explain the change.
Source of funds is not “which bank sent it”
For a material transaction, the immediate sending account can be only one part of the explanation.
Source of funds asks about the economic origin of the specific money.
A payment may come from a law firm’s client account, a broker, a payment processor, another group company or the customer’s treasury account.
The transfer path matters.
So does the commercial event that generated it.
The stronger file connects:
economic reason → contract or legal basis → payer → payment path → accounting treatment
This is more useful than producing a bank statement in isolation.
Source of wealth is another question
A broader private-client or ownership review may also ask how the owner accumulated overall wealth.
That is source of wealth.
It should remain separate from source of funds.
A company can explain a large customer payment perfectly and still face a separate SOW question about the beneficial owner.
Likewise, a founder can have a well-documented history of wealth and still need to explain a specific unusual transfer.
Merging both into “proof of money” weakens the file.
Why the bank may not explain everything immediately
UK law includes offences commonly described as “tipping off” in the suspicious-activity-reporting context.
That does not mean that every vague bank response proves that a SAR has been filed.
It means that, in a specific legal context, there can be limits on disclosures that might prejudice an investigation or reveal protected information.
A customer should therefore resist reading a legal conclusion into poor or limited communication.
The institution may also be constrained by fraud controls, sanctions procedures, internal investigation, legal orders, technology or ordinary service problems.
The public lesson must stay narrow:
A bank’s incomplete explanation is not reliable evidence of the hidden reason for a restriction.
The strongest objection: banks sometimes get reviews wrong
Of course.
Risk-based systems produce false positives.
Automated monitoring can identify activity that is unusual but legitimate.
Customer data can be stale because the bank failed to update it properly.
Operational errors can create unnecessary delay.
Banks also differ substantially in systems, risk appetite and service quality.
Nothing in ongoing-C DD principles means every restriction is justified.
The practical response, however, remains the same: separate what is known from what is inferred and provide accurate evidence through the institution’s legitimate review process.
What not to do
A compliance review is not a signal to change transaction behaviour to make it less visible.
Do not:
- split a legitimate payment merely to stay below a perceived monitoring threshold;
- invent a simpler business purpose than the real one;
- alter invoices after the event to fit an explanation;
- misdescribe the beneficial owner;
- move money through unnecessary accounts to disguise origin; or
- guess at what the bank “wants to hear”.
Those actions can create the very inconsistencies that a robust file is designed to avoid.
The objective is explainability, not evasion.
The before-during-after framework
Before a review
Keep the customer file aligned with the business.
Update ownership, addresses, activity descriptions and major changes when required.
Maintain evidence for material source-of-funds events.
Keep source-of-wealth evidence separately where it is relevant to the relationship.
During a review
Identify exactly what is being requested.
Separate facts from assumptions about why it is being requested.
Respond accurately and consistently with corporate, accounting and tax records.
Use the bank’s official communication or escalation channels.
After a review
Ask what changed in the business or profile.
Update internal evidence so the same transaction can be explained later to an auditor, accountant, another bank or tax authority.
If the banking relationship no longer fits the business, address that as a bankability problem rather than trying to manipulate transaction patterns.
Banking resilience starts before the alert
International businesses are especially exposed to profile drift.
A founder may move country.
The company may add a holding.
Customers may become more global.
Average transaction size may increase.
A new regulated activity may begin.
Each change can be legitimate while making the old KYC profile obsolete.
This is why the same structural sequence keeps returning:
person → residence → activity → entity → ownership/control → banking → source of funds → source of wealth → maintenance
The strongest banking file is not the one assembled after access becomes urgent.
It is the one that has been updated as the business changed.
Sources
- UK Financial Conduct Authority — Firms’ customer due diligence processes and controls: findings
- HMRC — Anti-money laundering guidance: ongoing monitoring
- HMRC — Anti-money laundering guidance: source of funds and source of wealth
- HMRC — Anti-money laundering guidance: tipping off
- FATF — The FATF Recommendations
Disclaimer
This article provides general information only and does not constitute legal, banking or anti-money-laundering advice. Account restrictions, transaction delays and information requests can arise for many reasons and differ by institution and jurisdiction. Nothing in this article implies that any restriction proves suspicious activity or that a bank is required to follow one universal review sequence.
