Responding to supervisory questions: documents to prepare
When a supervisory authority sends a request for information during authorisation, prepare three groups of documents: governance and ownership records, provenance evidence for funds and assets, and operational evidence backing the claims already made in the application. A well-organised file moves through review faster than a scattered one. The review cycle is set by the authority, not by a fixed calendar date in the letter. A single missing document rarely closes a file — but it does stop the clock.
Where the request comes from
A supervisory question usually arises from the authority's general power to seek information on an open file. The letter names the topic and a deadline. It rarely names the specific legal basis for asking, because the basis is procedural rather than substantive — the authority is checking a claim already on record, not opening a new line of enquiry from nothing.
Three topics recur most often: whether the governance structure matches what was described, where the funds or assets named in the file actually came from, and whether the operational description in the application matches what the business does day to day.
Practical consequence
A supervisory question splits the file in two. One thread is active — the reviewer is waiting for an answer. Everything else pauses until that thread closes. The delay is not free. Staff stay on standby, contracts wait for a licence date, and a launch plan built around a fixed authorisation date starts to slip. In a multi-jurisdiction structure, the delay multiplies: each entity in the chain waits for the same answer before its own filing can proceed.
Provenance questions carry a second risk. If the file cannot show where an asset or a sum of money came from, the reviewer does not simply repeat the question. The reviewer widens it. A narrow query about one account can turn into a broader query about the entire ownership chain. Preparing the wider answer before it is requested is cheaper than reconstructing it against a deadline.
What to do
- The compliance officer checks the new question against every document already submitted with the original application, line by line.
- The finance lead builds a provenance trail for the funds or assets named in the question, starting from the earliest point the company can document with bank statements, transfer records or prior ownership agreements.
- The governance file is refreshed: current organisational chart, shareholder register, and any change of controlling persons since the application was filed.
- Where the question touches a processor or a data-handling partner, that party's role is confirmed in writing before the answer is sent. Processor data protection explained sets out how that role is defined and evidenced.
- One named contact drafts the response, ties each claim to a supporting document, and attaches the documents as annexes rather than embedding them in the narrative.
- The draft is checked against the exact wording of the question before it leaves the building. Reviewers judge answers against the question asked, not the question the company would have preferred.
Keep a document map alongside the response — one line per claim, one column for the supporting file. It saves time if the same topic resurfaces months later in a different form.
Who decides
The reviewing officer inside the authority decides whether an answer is sufficient. There is no appeal at this stage. The file stays open until the officer is satisfied, escalates the question internally, or issues a formal deficiency notice. Some authorities publish an internal service target for turning a reviewed answer around; others work file by file with no published target. Either way, the applicant does not set the calendar once a question has been sent. The applicant controls only the completeness and clarity of the answer.
| Document group | What it shows | Typical form |
|---|---|---|
| Governance record | Who controls the applicant, and since when | Register extract, shareholder agreement, organisational chart |
| Provenance evidence | Where funds or assets originated | Bank statements, transfer records, sale agreements |
| Operational evidence | How the described process actually runs | Internal policy, system record, process log |
| Third-party confirmation | What a partner, bank or processor has agreed to do | Signed agreement, confirmation letter |
Forks
If the question concerns a natural person behind the applicant, the provenance trail has to reach that person directly. A corporate wrapper does not answer a question about an individual's source of funds. If the question concerns the applicant's own operating history instead, the trail stays internal: policies, system logs and minutes of the governance body responsible for the point raised.
If a document cannot be located because a founder or controlling person has since left the business, the gap has to be explained rather than quietly filled. A comparable problem shows up whenever a key contributor departs before records are settled, a pattern examined from a different angle in Games and interactive entertainment — when a founder leaves. The lesson carries across sectors: reconstruct what can be reconstructed, and state plainly what cannot.
If a question repeats in a slightly different form after an earlier answer, treat it as a signal, not a formality — the first answer did not fully satisfy the reviewer. Tracking a recurring review against its own deadline is a discipline shared with other periodic filings, including the kind covered in Renewal and restoration step by step.
Limit
This page does not list which specific documents a given national authority will require, because that list depends on the authority, the licence category and the facts of the file. A generic checklist would mislead more than it would help. It also does not cover what happens after a formal refusal; that is a separate procedure with its own forum and its own timing.
Related publications
The document set built for a supervisory question overlaps heavily with the file built for the original review of governance and controlling persons. See Governance and fit and proper review step by step for the baseline file most applicants already hold before the first question ever arrives.
Verified
Reviewed by Aleks Vaher. This page describes procedure and document practice only. It does not cite specific statutory provisions, because the applicable article numbers depend on the national regime of the authority handling the file.
Where this file can go next
Some questions are not about a missing document at all — they test whether the business has enough real substance to hold the licence it seeks. That situation is covered separately in When the applicant is asked to prove substance.
Other files stall not because of a document gap but because the authority itself changes mid-review: a new regulator, a new reviewer, a different set of expectations. That risk is set out in When the regulator changes during the project.
Where the underlying issue is a tokenised right with contractual gaps rather than a missing regulatory document, the starting point looks different again — see When the contract has no upgrade path.
FAQ
How long does responding to supervisory questions take in practice?
There is rarely a fixed statutory deadline attached to the question itself. In practice, timing depends on how quickly the applicant can assemble complete, verifiable evidence. A well-organised file can answer within days. A file missing provenance records can take months.
Which documents are needed to start?
Start with the original application file, current governance and ownership records, and a first pass at provenance evidence for any funds or assets the question names. Everything else is added once the exact scope of the question becomes clear.
What happens if the other side does not respond?
If the applicant does not respond within the period the authority allows, the file typically moves to a deficiency status, or is treated as withdrawn, depending on the authority's own rules. A partial response that explains a genuine gap is treated differently from silence.