Post-issue reporting: what the decision maker looks at
Once a token issuance closes, the reporting duty does not end with the offering document. A decision maker — usually the competent supervisor, or an internal compliance reviewer acting on the issuer's behalf — checks whether the file stays current: material changes, holder numbers, custody arrangements, and any event that could affect the original disclosure. The review is built around one question: does the file still match reality?
What triggers a post-issue report
A report becomes due when something changes that a holder or a supervisor would reasonably want to know about. Typical triggers include a change in the issuer's management, a shift in the custody arrangement for the underlying assets, a material change in the token's technical function, or an incident that affects holder rights. The trigger is the change itself, not a fixed calendar date.
Some updates are scheduled — periodic confirmations that nothing material has changed since the last filing. Others are event-driven and must be filed as soon as the issuer becomes aware of the event, regardless of the scheduled cycle. Treating the two as one calendar is a common source of delay, and delay is what draws attention later.
What the decision maker actually checks
Reviewers do not read the update in isolation. They compare it against the original file and against what the market has already seen. In practice, the check tends to cover the same points every time.
- Whether the change is reflected consistently across every annex it touches, not just the one that was easiest to update.
- Whether the filing date is close to the date the issuer says it became aware of the change.
- Whether holders who are directly affected were told separately, or only through a general filing.
- Whether the update matches anything already visible in trading activity, public statements, or prior correspondence.
- Whether the same person who drafted the change also approved it, without a second reviewer in between.
A gap on any of these points does not automatically mean a problem exists. It means the reviewer asks a follow-up question, and the issuer needs a straight answer ready.
What changes in risk and timing after issuance
Before issuance, the main risk sits in the offering document itself: is it complete, is it accurate, does it match the token's actual design. After issuance, the risk moves to the gap between that document and reality as it evolves. A stale annex, an outdated custodian name, or an unreported change in control creates exposure that grows the longer it stays unreported.
The clock for a corrective filing usually starts from the moment the issuer knew, or should reasonably have known, about the change — not from the moment a holder or the supervisor points it out. This distinction matters more than the length of any single deadline, because it decides whether a late filing looks like an oversight or a choice.
Steps to prepare the file
The steps below assume the offering document already exists in its approved form. If it does not, that has to come first, and it is a separate exercise with its own document list.
| Stage | What happens | Who is responsible | Typical timing |
|---|---|---|---|
| Change identified | Internal team flags a material change against the original disclosure | Compliance or legal owner | As soon as identified |
| Impact assessment | Team decides whether the change is material and which annex or notice it affects | Compliance, with legal sign-off | Within days of identification |
| Draft update | Annex or notice is drafted and cross-checked line by line against the existing file | Legal owner or external counsel | Runs in parallel with the assessment |
| Internal approval | Management or board confirms the update before anything leaves the building | Issuer's governing body | Set by internal policy |
| Filing | Update goes to the supervisor and, where relevant, to holders directly | Compliance owner | Immediately after approval |
| Supervisor review | Supervisor checks the filing against the original file and may raise follow-up questions | Competent authority | Set by the authority, case by case |
Keep the underlying file in order, not just the filing that gets sent out. If personal data belonging to holders or counterparties is processed as part of this routine, the arrangement with any processor should be documented in writing; a working example is set out in the Data processing agreement in practice.
- Log every material change the moment it is identified, with a date and a short description.
- Assess materiality against the original offering document, not against internal expectations of what matters.
- Draft the update so it reads as a continuation of the existing file, not as a new document.
- Route the draft through internal approval before it goes anywhere else.
- File with the supervisor and, where the change affects holders directly, notify them separately and on record.
- Keep proof of filing and of any acknowledgement received, including the date it was sent.
Who reviews the file and by when
The first review sits with the supervisor that authorised the original offering. It checks three things in order: whether the change was reported at all, whether it was reported within a reasonable time of the issuer becoming aware, and whether the update is consistent with the rest of the file. A supervisor that finds a gap usually asks for a written explanation before deciding whether anything further follows.
Internally, the decision maker is whoever signs off the filing — typically the same body that approved the original offering document. Larger issuers separate the drafting function from the sign-off function; smaller teams often combine the two, which raises the stakes of that single review step and leaves less room for a second pair of eyes.
Common scenarios
If the change is administrative — a registered address, a contact point — a short notice usually closes the matter without further exchange.
If the change touches custody, control, or the token's technical function, expect a fuller filing and a higher chance of follow-up questions from the supervisor before the matter is treated as closed.
If the issuer discovers the gap itself, before anyone else raises it, the filing tends to be treated as a correction. If a holder or the supervisor raises it first, the same content can be treated as a response to a finding rather than a voluntary update — the wording can be identical, the reception is not.
Limits and sources
This page describes the reporting routine in general terms. It does not set out jurisdiction-specific deadlines, fee schedules, or the exact form of any filing — those depend on the issuer's home supervisor and change independently of this text.
Where the underlying question is a specific counterparty rather than the reporting process itself, the report layer covers that separately: for a Lithuanian counterparty check, see Counterparty report lithuania.
For a document originating in Latvia, the equivalent check is described in Document in Latvia.
For a jurisdiction question involving Poland, see Jurisdiction in Poland.
This overview reflects general supervisory practice for post-issue reporting and does not cite specific legal provisions; it was checked for consistency with current market practice before publication.
Related reading
The reporting routine described here follows on from the drafting stage. If the offering document itself is still being assembled, the step-by-step guide covers what to prepare: Offering document preparation step by step.
FAQ
How long does post-issue reporting take in practice?
The internal steps — identification, assessment, drafting, approval — typically take a few working days for a routine change. The supervisor's own review has no fixed clock in most cases; it depends on the nature of the change and on whether follow-up questions are raised.
Which documents are needed to start?
At minimum: the original offering document, a written description of the change, and an internal record showing when the issuer became aware of it. Where custody or data processing arrangements are affected, the relevant agreements should be pulled as well.
What happens if the other side does not respond?
If a counterparty or processor involved in the change does not respond to a request for confirmation, the issuer should still file on the basis of what it knows, note the outstanding request within the filing itself, and follow up in writing. Silence on the other side does not suspend the reporting duty.
If token issuance is only one part of a wider footprint — for example, services are being added across borders alongside it — the next question is usually a different one, and it is addressed separately: When cross-border services are added explained.