When the business model changes mid-application: what it costs to be wrong
An authorisation file describes one business model. When the model changes before the decision — a new custody arrangement, an added service, a new counterparty flow — the file no longer matches what the supervisor is assessing. The outcome is rarely a quiet amendment. It is delay, a request for resubmission, or a restart, and the clock the applicant assumed had kept running may already have reset.
The file the supervisor assesses is fixed at submission
Authorisation as a crypto-asset service provider is granted against the scope described in the application, under Regulation (EU) 2023/1114 (MiCA). Where the service touches a transfer of crypto-assets between providers, the accompanying information duty under Regulation (EU) 2023/1113 (TFR) attaches to that same scope. Neither regulation is written for a moving target, and neither treats the application file as a draft that updates itself.
This is why a change mid-application is not a drafting update. It is a new question put to the supervisor: does the file in front of them still describe the applicant in front of them. Until that question is answered, the applicant is operating two versions of the same business — the one on file and the one being built.
Why a resubmission is not a technicality
A supplementary filing is not paperwork housekeeping. It reopens the fitness and governance test that the original file was built to satisfy. Reviewers who already formed a view of the applicant now have to decide whether the change alters that view, and applicants rarely control how much weight is given to the fact that the view had to be revisited at all.
The timing of disclosure carries its own weight, separate from the change itself. An identical change, disclosed early, is a scope question. The same change, found by the supervisor later, is read first as a governance question — whether the applicant can be trusted to keep its file accurate while under review.
What actually happens once the model has moved
The supervisor treats the change according to how far it departs from what was filed. A narrower scope, such as dropping a planned service, is usually absorbed into the review already under way. A broader or structurally different scope — adding custody, adding an asset class, changing who holds client funds — is treated as a new assessment of fitness, and sometimes as a new application in substance if not in form.
| Type of change | Typical treatment | Who assesses it |
|---|---|---|
| Service dropped, scope narrows | Noted, review continues unchanged | The case officer already assigned |
| Service added, scope widens | Supplementary filing required | Same authority, extended review period |
| Custody or fund-holding structure changes | Fitness and governance reassessed | Full review panel, not the case officer alone |
| Counterparty or transfer flow changes | Information duty under TFR reassessed | Authority, and where relevant the counterparty's own supervisor |
| Target market or client base changes | Suitability of controls reassessed | Same authority, on request for further evidence |
The undisclosed version is the costly one. An applicant who keeps operating on the old file while building the new model is not managing a timeline — they are misrepresenting the scope of an application still under review. That reading survives even where the applicant believed the change was minor.
What to do, in order
- Stop treating the change as an internal matter. Notify the case officer in writing before the new model goes live, not after it does.
- Have compliance map the new scope against the original file, line by line, and mark every point of divergence explicitly.
- Ask the case officer directly whether the divergence requires a supplementary filing or a fresh application, and get the answer in writing.
- Update the governance and fitness documentation to match the new model before submitting anything further to the file.
- Keep the obligations of the old file running until the supervisor confirms, in writing, that the new scope has replaced it.
The order matters more than the speed. An applicant who submits the update before asking the question loses the chance to shape how the change is characterised, and characterisation is most of what decides the length of the delay that follows.
Who decides, and on what
The competent authority reviewing the original application decides whether the change is material. It decides on the file as amended, on the answers given at interview, and on whether the applicant disclosed the change before or after the authority found it independently. Nothing in this decision is delegated to the applicant's own reading of the scope.
A change judged immaterial is absorbed without a formal decision recorded against the applicant. A change judged material triggers a written finding, and that finding becomes part of the file the authority relies on for as long as the authorisation, once granted, remains subject to supervision.
If your situation branches
If the change involves a new data flow into the compliance file — a new source of client records, a new vetting data set built up during the review — the ownership of that material is a separate question from the authorisation itself. See A data set was assembled by an intern ownership.
If the change means client or counterparty records are now requested more often, by users or by the supervisor itself, that is a distinct operational load with its own timetable. See When access requests arrive in volume.
If the change comes bundled with a rebrand, launched ahead of the licence rather than after it, the mark itself may carry exposure the authorisation file does not cover. See When the mark has not been used for years.
If the change moves settlement from off-chain books onto a distributed ledger, the reconciliation between the two records is a separate exposure from the authorisation question raised here. See A transfer on-chain is not recorded off-chain tokenised rights.
What this page does not cover
This page does not set out how long a review takes once a supplementary filing is accepted. That period is set by the authority handling the file, and it varies with the scale of the change, not with a fixed rule. It does not cover what happens once the change has already been discovered by the supervisor rather than disclosed by the applicant — that is a supervisory action, not an authorisation step, and it follows a different procedure entirely. It also does not set out the fee attached to a supplementary filing, since that is published in the authority's own tariff, not in the regulations cited above.
Related reading
A comparable question arises when it is an outsourced function, not the business model itself, that draws the supervisor's attention mid-review. See Outsourcing is challenged by the supervisor authorisation what it.
Verified
Checked against Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR), both in force from 30 December 2024, as published on EUR-Lex. Where the authority's own procedure is described, the description is limited to the mechanism set out in these instruments, not to national implementing detail not yet held in this practice's records.
Questions we are asked
What is the first step when the business model changes mid-application?
Tell the case officer before the new model goes live. A change disclosed by the applicant is assessed on its merits, on the scope and the reasons behind it. A change found by the supervisor is assessed as a governance failure first, and only afterwards as a question of scope.
Which deadline is already running?
The original application's review clock keeps running unless the authority confirms in writing that it has been paused. Applicants who assume a pause exists without that written confirmation lose time they believed they had, and the loss becomes visible only once the review reaches its expected end date.
Who decides, and on what evidence?
The competent authority handling the original file decides. It decides on the amended scope, on the governance record built up over the review, and on the timing of disclosure relative to when the change actually took effect. None of these three elements is weighed by the applicant, and none can be settled by argument after the fact.