By: Money Navigator Research Team
Last Reviewed: 28/01/2026

FACT CHECKED
Quick Summary
When Tide marks an account as “reopened”, it usually means the review has reached an “account can continue” outcome – but it does not always mean every feature returns instantly, or that monitoring stops.
In practice, access and payment rails can resume in layers, and some controls can remain while records are refreshed and activity is revalidated.
This article is educational and not financial advice.
What Tide Means by “Routine Reviews” and Why “Reopened” Can Be a Staged Return
Tide publicly describes “routine security reviews” as checks on account activity, how a business makes money, the industries involved, and whether account-holder or business details have changed.
It also states it may pause an account during review, that a review can take time depending on complexity, and that updates may be limited “for legal reasons”.
Those statements help explain why “reopened” can be the end of one gate (the review decision) but not necessarily the end of all operational constraints. See Routine reviews | Tide Business.
A second reason “reopened” may not equal “fully normal” is that Tide offers more than one account type and relies on partner providers for different products.
Tide explains it is not a bank and that some members hold e-money accounts (with safeguarding protections under e-money rules) while others hold business bank accounts provided by a banking partner (with FSCS deposit cover subject to eligibility). See Is Tide a bank? | Tide Business.
“Reopened” vs “Unrestricted”: The Practical Difference
“Reopened” is best understood as a status decision (“the account can continue”) rather than a guarantee that every capability is immediately restored.
Common post-reopen patterns include:
Core access returns first: ability to log in, view balances, and access statements.
Payments resume in steps: one rail or feature can work while another is still re-enabled (for example, card use returning before outbound bank transfers, or vice versa).
Limits can remain: transfer caps, recipient/beneficiary friction, or certain high-risk payment types staying constrained while monitoring continues.
Follow-up questions can still arrive: “reopened” doesn’t prevent future requests for updated documents or explanations if activity changes or the risk profile shifts (this is consistent with ongoing monitoring obligations across the sector).
For the “what still works” breakdown during restriction (useful context when comparing to the post-reopen state), see Tide account locked or frozen: what usually still works.
Why Updates Can Be Limited Even After a Reopen Message
Two overlapping constraints can apply:
Legal constraints on disclosures
UK law includes “tipping off” offences in certain circumstances, which can restrict what a firm can say about suspicions or reports while an investigation may be prejudiced. See Proceeds of Crime Act 2002: Section 333A (tipping off: regulated sector).Ongoing monitoring rather than a one-off check
UK money laundering rules include ongoing monitoring expectations (transaction scrutiny and keeping customer information up to date). See Money Laundering Regulations 2017: Regulation 28 (customer due diligence and ongoing monitoring).
That’s why “reopened” can coexist with limited messaging and a “watchful” period operationally. For a Tide-specific explainer of communication limits, see Why Tide can’t explain a restriction: tipping off and communication limits.
Summary Table
| Scenario | Outcome | Practical impact |
|---|---|---|
| App shows “reopened” and balance visible | Account access restored | Admin tasks (statements, transaction history) typically become possible again |
| Card payments start working again first | Card rail re-enabled | Trading can feel “back”, but bank transfers may still be constrained |
| Outbound transfers work, but new payees fail or require extra steps | Payee controls remain | Supplier or contractor payments may be slower to restart |
| Incoming payments arrive, but some inbound types bounce | Inbound rails not uniform | Customer receipts may be inconsistent until all rails are live |
| Direct debits/standing orders resume after a delay | Mandates re-sync | A short gap can occur between “reopened” and mandate processing |
| A single high-value payment remains held | Transaction-level hold | “Reopened” may not release a flagged payment instantly |
| Limits remain lower than before | Risk limits persist | Larger settlements may require more time or additional checks |
| Requests for documents continue after reopen | Monitoring continues | The account can operate, but information requests may recur |
| “Reopened” but account later becomes restricted again | Re-review triggered | Activity changes can lead to another review cycle |
If the underlying question is “restricted vs closed”, see Tide business account: restricted vs closed.
Scenario table
| Scenario-level | Process-level | Outcome-level |
|---|---|---|
| “Reopened” after providing documents | Records refresh completed | Access returns; follow-up checks may continue if activity changes |
| “Reopened” after explaining unusual activity | Activity re-contextualised | Some limits may remain until patterns stabilise in monitoring systems |
| “Reopened” after ownership/director updates | Entity checks reconciled | Temporary constraints can persist while corporate records align |
| “Reopened” but one payment type still blocked | Rail-specific re-enable not complete | Card/transfers/DDs may return on different timelines |
| “Reopened” but settlement funds still delayed | Third-party timing (processor/rail) | Trading can resume, but payouts may lag behind account status |
| “Reopened” after international payment queries | Cross-border risk controls reviewed | Overseas transfers may remain more tightly controlled than domestic |
| “Reopened” with continuing source-of-funds questions | Ongoing monitoring focus | Periodic requests can reappear as volumes, counterparties, or geographies change |
For examples of the kinds of information frequently requested in reviews, see Tide compliance review documents: what’s requested and why it repeats and Tide source of funds checks: what businesses are asked to explain.
Payments, Refunds and “In-Flight” Activity After Reopening
Even when an account is reopened, timing issues can remain for activity that was “mid-stream” during the restriction window. A payment that was queued, flagged, or awaiting verification can behave differently from new payments initiated after reopening, because the original payment may be subject to separate checks.
This is one reason businesses sometimes experience a mismatch between “status” and “cashflow reality” for a short period. For broader operational impact when outgoing payments are paused at an e-money provider level, see E-money provider pauses outgoing payments: payroll, suppliers, tax.
Where card settlements and disputes are involved, reopening may not instantly resolve external hold dynamics (for example, dispute windows, refund timing, or settlement batching). For chargeback mechanics in an EMI settlement chain, see Chargebacks and card disputes with EMI settlements: who can withhold funds.
Safeguarding vs FSCS Deposit Cover: Why Account Type Matters When “Normal” Returns
Tide states that some members hold e-money accounts and others hold business bank accounts provided by a bank partner, and it distinguishes safeguarding from FSCS deposit cover. See Is Tide a bank? | Tide Business.
At a sector level, the FCA has emphasised that funds held by payment and e-money firms are not directly protected by FSCS, and that safeguarding is the mechanism used instead (which can involve delays if a firm fails).
See FCA press release on payment safeguarding rule changes. The underlying safeguarding requirement for e-money is set out in legislation. See Electronic Money Regulations 2011: Regulation 20 (safeguarding requirements).
For a deeper explainer in our guides, see Safeguarding vs deposit cover: EMI protections vs FSCS bank accounts and App business accounts: bank or e-money (check the FCA register).
Tide Business Bank Account
Tide describes itself as a platform rather than a bank, offering both e-money accounts (with safeguarding under e-money rules) and business bank accounts provided by a banking partner, where FSCS deposit cover may apply subject to eligibility.
The practical “reopened” experience can vary depending on which product a business holds and which rails are in use. See our Tide hub page for broader product context: Tide business bank accounts.
Frequently Asked Questions
“Reopened” usually means Tide has reached a decision to allow the account relationship to continue. It’s a meaningful milestone because it generally indicates the account is no longer in a “paused while we review” state.
It does not necessarily mean every internal check has ended. Ongoing monitoring is a normal requirement across the sector, and follow-up questions can still appear if activity changes, new counterparties appear, or volumes shift materially.
A common post-reopen pattern is that access is restored before every payment pathway is fully re-enabled. Transfers can also have rail-specific controls (for example, adding new payees, higher-value payments, or unusual destinations) that behave differently from routine payments.
Another edge case is that a payment initiated before or during the restriction window can be treated differently from payments initiated after reopening, because transaction-level checks and timing can diverge from account-level status.
Yes. A reopen outcome can restore access while maintaining conservative limits on certain activities, particularly those that present higher operational or financial-crime risk (for example, high-value transfers or rapid movement of funds).
Limits can also vary by product type and rail. For example, card-related activity, bank transfers, and direct debits are not always controlled by the same systems end-to-end, so limits can change in a way that feels inconsistent from the outside.
Limited explanation is not proof of wrongdoing. Tide explicitly states that updates can be limited “for legal reasons” during routine reviews, and the sector also operates under legal constraints that can restrict disclosures in certain circumstances.
That said, communication limits can feel indistinguishable from poor service. The practical implication is that “reopened” is the most operationally useful message, because it indicates access is returning even if the detail of the underlying trigger is not shared.
Repeated requests are often linked to ongoing monitoring, periodic refresh cycles, or changes in activity patterns that require updated context. Even where a prior evidence pack was accepted, a later change (new product line, new markets, new owners, higher volumes) can create a fresh need for information.
Edge cases include corporate record mismatches (director/PSC changes, address changes, trading name changes) where different sources update at different speeds, and a firm may wait until records align before fully removing constraints.
Not necessarily. “Reopened” indicates the account can operate again, but inbound payment behaviour can still vary by rail, counterparty bank, and timing. Some inbound streams may resume earlier than others.
Another edge case is where a payer’s bank has its own controls (for example, if prior payments were returned or flagged). In that case, the payer’s institution can add friction even after the recipient account is reopened.
Mandates and scheduled payments can require re-synchronisation after a pause. Even if the account is reopened, a short lag can occur before mandates behave exactly as they did previously, depending on processing cycles.
A further complication is that “in-flight” items can behave differently. A direct debit attempted during the restricted period may have failed and may not automatically retry unless the originator attempts again within its own schedule.
Yes. A processor’s hold or reserve is not the same thing as a Tide account restriction, and the processor can apply its own risk controls, dispute reserves, or rolling holds. That can make “reopened” feel incomplete from a cashflow perspective.
Disputes and chargebacks create additional timing complexity: even if business banking access returns, settlement flows and dispute windows can continue to influence when funds actually arrive and clear.
It can happen, typically when a new trigger appears: material changes in activity, new high-risk counterparties, sudden volume changes, or new information that requires revalidation. “Reopened” describes the current operational state, not a permanent guarantee.
If a second restriction occurs, it may follow a different pathway than the first. For example, a document-led review can later be followed by a transaction-led review, which can feel like a “repeat” even though the trigger differs.
A reopen outcome can reduce immediate harm, but it doesn’t automatically resolve the question of whether disruption was handled fairly or proportionately. Complaint handling can still focus on communication, timeliness, and the impact of the restriction window.
The Financial Ombudsman Service publishes guidance on how it approaches complaints involving frozen accounts and blocked payments (including circumstances where firms act on suspicion and customers complain about inconvenience or lack of notice). See Frozen accounts and blocked payments (business guidance) | Financial Ombudsman Service.
“Reopened” is best read as an operational permission state: the provider has decided it can continue servicing the account, but risk controls and payment-rail mechanics do not always reset to “day one normal” at the same moment.
That’s partly because modern business accounts are a chain (app layer, payment rails, partner providers, and sometimes third-party settlement flows), and each link can have its own gating and timing.
The other structural constraint is that reviews are not only about a single historic event; they are also about keeping records current and matching activity to the provider’s understanding of the customer.
That creates a world where a reopen decision can coexist with ongoing monitoring, limited messaging, and staged restoration of features.
Sources & References
Proceeds of Crime Act 2002: Section 333A (tipping off: regulated sector)
Money Laundering Regulations 2017: Regulation 28 (customer due diligence and ongoing monitoring)
Electronic Money Regulations 2011: Regulation 20 (safeguarding requirements)
Payment Services Regulations 2017: Regulation 23 (safeguarding requirements)
What is the FSCS and what is the new deposit protection limit? | Bank of England
Frozen accounts and blocked payments (business guidance) | Financial Ombudsman Service



