When the obliged entity status is disputed: what to do first
Short answer. When a supervisor, a bank, or a counterparty disputes whether your platform is an obliged entity, do not wait for a formal ruling. Confirm which specific service triggers the classification, freeze the relevant activity logs, keep a written internal position, and get a partner's read within hours rather than days. The dispute itself does not suspend any due-diligence duty that already applies.
What actually triggers the dispute
Most disputes of this kind start with the scope of Regulation (EU) 2023/1114 (MiCA): whether the service you run falls under one of the crypto-asset services it lists, or sits outside it. If it does fall inside that scope, Regulation (EU) 2023/1113 (TFR) attaches the information-accompanying duties for transfers of funds and crypto-assets that, in practice, make the provider an obliged entity for AML purposes. The disagreement is rarely about the AML rule itself. It is about which side of the MiCA service list your platform sits on.
This matters because the two regulations answer different questions. MiCA decides whether you are a regulated crypto-asset service provider at all. TFR decides what you must attach to a transfer once that status is settled. A dispute can sit entirely inside the first question and still force you to behave as if the second already applies.
What changes while the status is unsettled
A dispute over classification does not pause the clock. Screening obligations, record-keeping, and reporting triggers that were already running before the disagreement started keep running during it. Waiting for a formal answer before acting on a suspicious pattern is the single most common mistake at this stage.
A related issue can surface before the classification question is even settled: The business model changes mid-application authorisation covers what happens when the underlying service definition shifts while a decision is pending, and the deadline consequences run independently of the dispute described here.
Treat the disputed period as a period of heightened, not suspended, obligation. Regulators read a gap in monitoring during a dispute as a choice, not as an accident.
What to do, in order
- Isolate the service in question. Write down exactly which function is disputed — custody, exchange, transfer facilitation — and separate it from functions that are not contested.
- Preserve the record as it stands. Freeze logs, onboarding files, and transaction records for the disputed service before any system change touches them.
- Keep monitoring running. Do not switch off screening or reporting for the disputed activity while the question is open; a pause is treated as a decision.
- Draft a short internal position. One page: the service, the MiCA basis for the classification you take, and the TFR consequence that follows from it.
- Notify your compliance officer or MLRO in writing. The notification itself becomes part of the record if the dispute later escalates.
- Get external counsel to confirm or challenge the position within the same day. A shared services agreement with a foreign parent raises the same evidentiary pattern discussed in When improvements are claimed by both sides, where the paper trail decides the outcome more than the underlying claim.
Who decides, and on what basis
The forum depends on who raised the dispute. A supervisor's own classification query is resolved by the supervisor. A counterparty's refusal to deal with you as an unclassified entity is a commercial dispute first, and a regulatory one only if escalated.
| Who is deciding | What the decision is based on | What continues meanwhile |
|---|---|---|
| AML supervisor or financial intelligence unit | the service inventory against the MiCA scope, and the TFR trigger it produces | due-diligence duties apply on a provisional basis |
| Internal compliance function | the documented service inventory and the written position | escalation to the supervisor stays open |
| Counterparty or partner institution | its own risk appetite and its reading of your classification | the commercial relationship, not the regulatory status, is what is actually paused |
The evidentiary standard the supervisor applies mirrors the burden-of-proof pattern in When a licensee stops paying and keeps selling: the party with the contemporaneous record, not the party with the stronger argument on paper, tends to prevail.
Common forks
If the supervisor initiated the query, respond in writing within the timeframe the query itself sets, and do not let the internal position diverge from the answer you send out.
If a bank or payment partner raised the doubt, treat it as a commercial risk decision on their side first; a regulatory escalation from a private counterparty is rare and usually follows, not precedes, a supervisor's own view.
If a system migration is scheduled while the status is disputed, an exit clause in the vendor contract can interact with the standstill in ways covered in When a migration is blocked by an exit clause; postponing the migration is usually cheaper than unwinding it after a reclassification.
What this page does not resolve
This page covers the first hours and days after a status dispute opens. It does not resolve the classification itself, does not draft the supervisor submission, and does not size the monitoring workload that follows once the status is settled either way. Those steps depend on the specific service inventory and on the supervisor involved.
Verified
Checked against the current text of Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR) as published in the Official Journal of the European Union.
Related situations
A comparable pattern appears at group level: When a group policy conflicts with local duties: what covers what to do when a head-office policy and a local obligation point in different directions.
FAQ
What is the first step when the obliged entity status is disputed?
Isolate the disputed service, freeze its records, and keep monitoring running while a written internal position is prepared.
Which deadline is already running?
Any screening, record-keeping, or reporting deadline that applied before the dispute started keeps running during it; the dispute does not create a standstill on its own.
Who decides, and on what evidence?
The supervisor decides on the service inventory measured against the MiCA scope and the TFR trigger it produces; a counterparty decision is commercial and follows the supervisor's view rather than replacing it.