Surrender of a permission: documents to prepare
Surrendering a permission is a formal application, not a notification. The holder submits a signed request, evidence that client accounts are closed or transferred, and confirmation that no outstanding obligations remain. The regulator reviews the file, may ask questions, and issues a decision. Until that decision arrives, the permission stays in force.
What changes once you file
The application does not end obligations on the day it is signed. Reporting, safeguarding of client assets and conduct duties continue until the regulator confirms surrender in writing. Filing early does not shorten this window; the file has to be complete first.
A weak file is the most common cause of delay. Missing wind-down evidence or an unresolved client complaint sends the file back for clarification, and the clock on the decision does not run while the regulator waits for an answer.
Documents to prepare
The list below covers what a regulator typically expects in a surrender file. Exact wording of forms varies by authority, so treat this as the substance to have ready rather than a template.
| Document | Purpose | Who prepares it |
|---|---|---|
| Signed surrender request | States the intention to give up the permission and the reason | Authorised representative of the holder |
| Client wind-down statement | Confirms all client positions are closed, transferred or returned | Compliance or operations lead |
| Outstanding obligations confirmation | Confirms no unresolved client claim or open investigation exists | Legal or compliance function |
| Client asset reconciliation | Shows the ledger balance matches what was returned to clients | Finance or custody team |
| Data retention and processing note | Confirms client and transaction records are retained under the applicable retention period | Data protection lead |
| Board or governing body resolution | Formal decision to cease the authorised activity | Governing body of the holder |
Where the holder relied on a third party for part of its infrastructure, the file should also show that data handling was properly closed out. A related question — Subprocessor data protection how it is proved explained — sets out what evidence a regulator or client expects to see for that closure.
Who decides and how long it takes
The authorisation authority that granted the permission is the same body that accepts its surrender. It reviews the file against internal checklists rather than against a fixed statutory list, which is why completeness on the first submission matters more than speed.
The authority may seek clarification before a decision is issued. Each round of clarification pauses the review; it does not restart it. A file with clear wind-down evidence moves through review faster than a file with gaps, regardless of when it was filed.
Forks: where the file changes shape
If surrender follows a merger or a change of control, the underlying corporate documents may need attention before the regulatory file is closed. Where the change also touches shared branding or trade marks with another party, the process resembles Coexistence negotiation step by step, run in parallel rather than after.
If a founder or key holder of technical assets has left before the surrender is filed, ownership of the underlying platform or prototype needs to be settled first. B2B software and SaaS — when a founder leaves covers what the corporate register does and does not show in that situation.
If client holdings include tokenised assets, the wind-down statement has to match on-chain movement, not only internal books. Discrepancies of this kind are covered in When a transfer on-chain is not recorded off-chain, which sets out what a mismatch costs to resolve before a file can close.
If the holder is surrendering because it is exiting the market entirely, rather than restructuring, the file is shorter but the wind-down evidence carries more weight, since there is no successor entity to answer follow-up questions later.
The point of no return
Once the regulator confirms surrender, reinstating the same permission is a new application, not a reversal. Treat the filing date as final for planning purposes even though the legal effect follows the confirmation, not the filing.
What this page does not cover
This page describes the file to prepare, not the underlying activity rules that continue to apply while the permission is still in force, and not the cost of preparing the file. It also does not cover surrender triggered by a regulator's own enforcement action, which follows a different, non-voluntary track.
Verified
This page reflects the procedural steps most authorisation authorities apply to a voluntary surrender request as at the review date shown on the site footer. Exact form names and internal checklists differ by authority; confirm the current version directly with the authority before filing.
Related publications
The step that precedes surrender in most files is the initial contact with the regulator: Pre-application meeting step by step sets out what that first conversation costs and covers.
FAQ
How long does surrender of a permission take in practice?
There is no fixed statutory deadline for this step. A complete file with clean wind-down evidence typically clears review faster than a file that needs clarification rounds, and each round adds to the timeline.
Which documents are needed to start?
At minimum: a signed surrender request, a client wind-down statement, confirmation that no obligations remain outstanding, and a governing body resolution. The table above sets out the fuller list most authorities expect.
What happens if the other side does not respond?
If "the other side" means the regulator, silence usually means the file is still under review, not that it has been rejected; a status enquiry is the normal next step. If it means a client or counterparty whose position has not been closed out, the wind-down statement cannot be finalised until that position is resolved, which delays the filing itself.