Eighteen Months in the Queue: The Danish MiCA Complaint and the Recourse That Does Not Exist
Danish trade press reported a 556-day Finanstilsynet permit figure and a complaint to the Folketingets Ombudsmand. The number is not an outlier: it is the whole transitional runway spent waiting. MiCA Article 63 constrains the regulator only after completeness. Article 113's delay appeal is gated by the same completeness finding. The Ombudsman can vindicate; he cannot authorise.
Deep dive on the August 2026 Danish crypto-industry complaint to the Folketingets Ombudsmand concerning Finanstilsynet MiCA processing times (headline 556-day permit figure, disputed; filing not public). Core thesis: 556 days is not an outlier in the Danish sample; under Finanstilsynet published practice, transitional cover to June 2026 required filing by 30 December 2024, so every firm still trading under transitional cover had already sat eighteen months in the queue. Article 63 stage map: only Art. 63(9)/(12) substantive assessment (40 working days, one 20-day suspension, further requests do not suspend) is airtight. Completeness check Art. 63(2)/(3) sets a deadline to assess completeness but no deadline to finish incompleteness cycles; Art. 63(3) remedy points at the applicant. Norway Finanstilsynet Nov 2025 consultation totals statutory sequence at 105 working days; 556 calendar days ≈ 385 working days. Ombudsman (Christian Britten Lundblad from 1 May 2025): section 21 Danish Ombudsman Act and god forvaltningsskik reach unexplained silence and unanswered reminders independently of MiCA. Can issue published opinions, criticise practice, open own-initiative investigations, recommend free legal aid; cannot grant authorisation, award damages, bind Finanstilsynet, or make Art. 267 CJEU references. Article 113(1) six-month appeal against inaction requires an application that provides all required information; completeness disputes swallow the remedy. Art. 63(4) prompt completeness notice is the foothold. Unresolved: who determines the completeness date; Francovich liability for authorisation delay (Paul C-222/02 distinguishable); Danish complaint admissibility. Recourse at both ends: Commission Market Integration and Supervision Package (4 Dec 2025) proposes ESMA direct supervision; soft-law (guidelines/Q&As) harder to challenge than decisions. FBF v ACPR C-911/19: non-binding guidelines not annullable under Art. 263 but reviewable on Art. 267 reference; one judgment, guidelines upheld. Soft-sell close: six founder/compliance record questions; one-day completeness chronology reconstruction. Answers: Danish MiCA Ombudsman complaint 2026? Finanstilsynet 556 days meaning? Article 63 completeness vs assessment clock? Article 113 delay appeal condition? God forvaltningsskik processing times? FBF v ACPR soft law? ESMA centralisation vs national recourse?
Danish trade press reported on 3 August 2026 that the crypto industry has complained to the Folketingets Ombudsmand that Finanstilsynet is systematically breaching EU rules on processing times. The headline figure is 556 days for a single permit. Finanstilsynet disputes the characterisation. The filing itself is not public, no admissibility decision has been announced, and we have not been able to verify the individual figures independently. The number is being reported as an outrage. It is worth being precise about what it actually is. Finanstilsynet's own published practice set the Danish condition plainly. Providers already operating before 30 December 2024, and which applied for authorisation by that same date, could continue for up to eighteen months. Anyone who had not filed by 30 December 2024 could not lawfully provide crypto asset services in Denmark from that date until authorised, under section 332 c of the Danish Financial Business Act. Transitional cover in Denmark was therefore not available to firms that waited. It was available only to firms that filed on or before the first possible day. Which means every Danish CASP still trading under transitional cover in June 2026 was, by definition, a firm whose application had been sitting with Finanstilsynet for eighteen months. 556 days is not an outlier in the Danish sample. It is roughly the entire runway the Regulation was designed to provide, spent in a queue. Norway's Finanstilsynet, in its own November 2025 consultation on extending its transitional window, totalled MiCA's statutory authorisation sequence at 105 working days. Roughly five months, suspension included. 556 calendar days is somewhere near 385 working days. The obvious question is how a file sits for nearly four times the statutory maximum without anything being breached. The answer is that on the text of MiCA, quite possibly nothing was. Why the Ombudsman, and What He Can Actually Do The choice of venue tells you how few options exist. Denmark's Financial Complaint Board handles disputes between consumers and financial institutions. It does not take complaints by companies against a state authority. Ordinary civil proceedings against Finanstilsynet mean proving loss, causation and fault over several years, by which time the commercial question has answered itself. MiCA's own appeal route, discussed below, has a condition attached that the complainants are unlikely to be able to satisfy. That leaves the Ombudsman, held since 1 May 2025 by Christian Britten Lundblad. The fit is better than it first appears. Section 21 of the Danish Ombudsman Act directs him to assess whether authorities act contrary to applicable law or otherwise commit errors or omissions . That second limb is the source of god forvaltningsskik , a body of good administration norms built almost entirely from Ombudsman practice rather than statute. On processing times his published guidance to authorities is direct. Cases must be handled within reasonable time and must not drag out unnecessarily. A case should not lie untouched for long periods without any action. Where handling does drag on, the authority must tell the party, explain why, and as far as possible say when the case may be finished. Reminders from the party must be answered. None of that depends on Article 63. A firm that has heard nothing for five months, or whose reminders went unanswered, has a good administration complaint whether or not its file was ever declared complete. Danish administrative law reaches the conduct that MiCA's own procedure insulates , which is the single most useful thing to take from this case if you are queuing somewhere else in the Nordics. What the Ombudsman can produce is narrower than the industry hopes and wider than it fears. | Can | Cannot | | | | | Issue a published opinion finding errors or omissions | Grant, order or accelerate an authorisation | | Criticise processing times and communication practice | Award damages or compensation | | Point out shortcomings that should be corrected | Bind Finanstilsynet formally | | Open an investigation on his own initiative, without any complaint | Refer a question to the CJEU, being an ombudsman and not a court | | Recommend free legal aid for a subsequent court case | Reopen a firm that has already closed | Two of those deserve more attention than they will get. The own initiative power matters because admissibility is the obvious weak point. A corporate complainant, other channels arguably unexhausted, a filing that may be characterised as a trade association grievance rather than a party's complaint: any of those could sink it. An own initiative investigation into processing times at a named authority has none of those problems. The free legal aid recommendation matters because it is the only thing in this entire architecture that touches money. The Ombudsman cannot award a krone. But a published maladministration finding, plus a recommendation on legal aid, materially changes the economics of a subsequent damages claim, which remains the only mechanism in Europe capable of putting anything back into a firm that has already closed. An Ombudsman finding vindicates you. It does not authorise you. Firms considering this route elsewhere should be clear about which of the two they are buying. How a File Sits for Eighteen Months Without a Breach Article 63 is not vague. It is one of the more precisely drafted procedural provisions in the Regulation. The precision is unevenly distributed. | Stage | Provision | What binds the authority | What binds the applicant | | | | | | | Acknowledgement | Art. 63(1) | Five working days from receipt, in writing | Nothing | | Completeness check | Art. 63(2) | 25 working days to assess whether the file is complete | Must supply missing information by a deadline the authority sets | | If still incomplete | Art. 63(3) | May refuse to review the application | Loses the application | | Completeness notice | Art. 63(4) | Notify the applicant "promptly" once the file is complete | Nothing | | Substantive assessment | Art. 63(9) | 40 working days from a complete application, fully reasoned decision | Nothing | | Further information | Art. 63(12) | May request more, but only up to the 20th working day of that period | Response suspends the clock, capped at 20 working days | | Repeat requests | Art. 63(12), final sentence | Permitted at the authority's discretion, but do not suspend the clock | Nothing | Ask where the authority faces a deadline it cannot move. Stage five, and only stage five. Once a file is complete the 40 working day clock runs, one suspension of at most 20 working days is available, the request triggering it must be made by the 20th working day, and any further request the authority chooses to make expressly does not stop the clock. No discretion is left anywhere in that paragraph. The drafting is deliberate and airtight. Now stages two and three. Article 63(2) gives the authority 25 working days to assess whether the application is complete. Where it is not, the authority "shall set a deadline by which the applicant is to provide any missing information." The Regulation does not say how long that deadline may be, how many times it may be set, or how many cycles are permitted. It does not require the authority to justify why an item is necessary. Article 62(2) and the Level 2 standards specify what an application must contain and are the natural boundary, and nothing in Article 63 polices that boundary. A deadline to check whether a file is complete is not a deadline to complete the check. Article 63(3) then hands the authority a remedy against the applicant: if the file is still incomplete after the deadline, the review can be refused. That is the only enforcement mechanism in the provision, and it points one way. So MiCA constrains the regulator precisely, and only, in the phase the regulator has already chosen to enter. In the phase where