When the offering document is questioned: what it costs to be wrong
When a regulator, an investor or a counterparty questions your offering document, the first cost is procedural, not financial. A challenged white paper triggers a review, sometimes a pause on reliance on it, and a duty to correct the disclosure. Getting the first response wrong extends every deadline that follows and widens who can rely on the record against you.
"Cost" here does not mean a fee schedule. It means time lost while the offer is on hold, a wider audience for the correction once it is published, and a weaker position if the same question comes back from a different angle later.
Basis
The offering document for a crypto-asset issuance is the disclosure instrument created by Regulation (EU) 2023/1114 (MiCA). It has applied since 30 December 2024 and sets out what an issuer must disclose before an offer to the public starts. It is also the first document tested once an issuance is questioned.
Under the regime introduced by Regulation (EU) 2023/1114 (MiCA), the white paper is not a marketing brochure. It is the legal representation of what the token is, what rights it carries, and what risks attach to it. A question about the offering document is, in substance, a question about whether that representation still holds.
Where the tokens move through a crypto-asset service provider once issued, Regulation (EU) 2023/1113 (TFR) governs the information that accompanies that transfer. A gap in that accompanying information can turn a disclosure dispute into a parallel transfer-record problem, even where the white paper itself is accurate.
Practical consequence
Once the offering document is questioned, three things change at once. The authority reviewing the offer can request further information or pause reliance on the white paper while it looks into the challenge. Any transfer of the tokens continues to sit under Regulation (EU) 2023/1113 (TFR), so a gap on that side compounds exposure on the disclosure side.
The withdrawal clock that runs in favour of investors keeps counting from the original publication date, not from the date the question was raised. Treating the challenge as the start of the clock, rather than a moment within it, is one of the more common ways issuers lose time they did not know they had already spent.
| Trigger | Immediate effect | Who acts |
|---|---|---|
| Investor complaint about misleading content | Authority opens a review of the white paper | National competent authority |
| Authority-initiated query | Reliance on the offer may be paused pending clarification | National competent authority |
| Counterparty dispute over what the token actually is | Offering document re-examined against the token's real features | Issuer and its advisers |
| Gap in transfer information | Cross-check against records required by Regulation (EU) 2023/1113 (TFR) | Crypto-asset service provider handling the transfer |
What to do
The sequence matters more than any single step. A response drafted before the file is complete tends to need a second correction later, which costs more credibility than the first one.
- Stop marketing the offer. The compliance officer suspends new subscriptions until the question is answered.
- Assemble the file. Legal counsel gathers the white paper, its amendments and the investor communications tied to the disputed passage.
- Check the mechanics. The technical lead confirms which statements in the document still match how the token actually behaves.
- Draft the response. Counsel prepares the reply to the authority's request, addressing each disputed point separately.
- Correct and notify. Where the white paper needs a correction, the issuer publishes it through the same channels used for the original offer.
- Keep the record. Every step, decision and date goes into the file; provenance matters as much as the wording of the fix.
None of these steps require a finished answer on day one. They require a file that shows, later, that the sequence was followed and not improvised.
Who decides
The national competent authority responsible for market oversight decides whether the published offering document complied with Regulation (EU) 2023/1114 (MiCA). It works from the file the issuer submits and from any complaint raised by an investor or counterparty.
A parallel question about the accompanying transfer record sits with the authority supervising the crypto-asset service provider under Regulation (EU) 2023/1113 (TFR). The two authorities can be looking at the same issuance from different sides at the same time.
Neither authority rules on how the token itself is classified. That question, where it arises separately from the disclosure dispute, runs on its own track and is addressed on its own evidence.
Forks
If the question comes from the authority itself, treat it as a formal review and respond on its terms, not on your own timeline. An authority-led query rarely accepts an informal clarification as a substitute for a written record.
If the question comes from an investor who says the document misled them, the file needs to show what was disclosed and when, not just what is true today. The comparison the authority makes is between the disclosure at the time and the facts at the time, not the current state of the project.
If the disputed point is really about classification rather than disclosure, the offering document is not where the answer sits. The token's status is a separate question, and answering it through a correction to the white paper alone will not resolve it.
Limits
This page does not set the number of days on the clock, or the outcome for a specific issuer; both depend on the file and on the authority handling it. It also does not decide how a given token is classified, and it does not cover a dispute that starts from the transfer side rather than the disclosure side.
Where any of those questions is the live one, the file needs a wider check than the offering document alone.
Sources
Where the question turns into a dispute with a specific counterparty, the underlying facts about that counterparty sit in the Counterparty report belgium.
Where the dispute is about the offering document as a file rather than about a person, the Document report belgium maps what can actually be established from it.
Where the question crosses into how the jurisdiction itself treats the offering, the Jurisdiction report belgium sets out what is established there.
The way these facts are collected, cross-checked and dated follows the method described in Methodology: collection, cross-checking and dating.
Checked against the consolidated texts of Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR), as published on EUR-Lex. Last verified: 4 March 2025.
Related publication
A related situation looks at the token side of the same file: When a token is classified differently than expected: what it costs when the dispute is about classification, not disclosure.
FAQ
What is the first step when the offering document is questioned?
Stop relying on the current version for new subscriptions and assemble the file before responding to anyone. Answering from memory, without the underlying documents in front of you, is how a small question turns into a larger one.
Which deadline is already running?
The withdrawal period that protects investors under Regulation (EU) 2023/1114 (MiCA) runs from the date the offering document was published, not from the date the question was raised. Treat that clock as already moving before you draft a single word of the response.
Who decides, and on what evidence?
The national competent authority overseeing the offer decides, working from the issuer's file and from whatever complaint or query triggered the review. It does not decide the token's classification; that question, where it is raised, runs on a separate track with its own evidence.