File assembly and submission: documents to prepare
A digital-assets authorisation file is a fixed set of documents assembled in a set order, verified before signature, and submitted as one package. The register works only with what arrives complete. A file returned for missing items restarts the clock, so the assembly stage decides most of the timeline that follows.
Stages of the file
| Stage | What happens | Typical outcome |
|---|---|---|
| Scoping | The applicant and the adviser agree the document list against the register's checklist | A fixed list, signed off before drafting starts |
| Collection | Corporate, ownership and personal-data documents are gathered from internal and external sources | Draft file, gaps flagged |
| Verification | Each document is checked against the checklist and against itself for internal consistency | File ready for signature |
| Submission | The complete package is filed with the register in the format it requires | Filing receipt issued |
| Acknowledgement | The register confirms receipt and opens its own review window | Review clock starts |
What to prepare
The file splits into four groups. Corporate documents establish who the applicant is: incorporation record, current register extract, articles, and a chart of the group structure where relevant. Ownership and control documents identify the people behind the applicant: shareholder register, beneficial-ownership declaration, and identity documents for each person named. Operational documents describe what the applicant does: a description of the service, the technology used, and the safeguarding arrangements for client assets. Personal-data documents accompany every filing that names an individual; the file should identify who acts as the controller for that data before submission — Controller data protection explained.
Each group has its own signatory. Corporate documents are signed by a director, ownership documents by the person named, operational documents by whoever holds the relevant function inside the applicant. Mixing signatories across groups is the most common reason a file bounces at verification.
The point of no return
Submission is the point of no return. Before the file is filed, any document can be replaced without consequence. Once the register issues a receipt, the file is fixed: withdrawing it and resubmitting a corrected version restarts the review window rather than pausing it. This is why the verification stage exists as a separate step from collection, not as a final read-through on the day of filing.
What to do
- The applicant confirms the document list with the register's current checklist before collection starts.
- The adviser assigns one owner per document group, so each signatory answers for one set only.
- Each document owner collects and cross-checks their group against the checklist, then hands it to verification.
- The verifier reads the assembled file as a whole, not group by group, and flags any inconsistency between sections.
- The applicant signs only after verification closes the file with no open items.
- The adviser files the package and confirms receipt before treating the matter as submitted.
Who decides
The register decides whether the file is complete on receipt and whether it is sufficient on review. Completeness is checked first and quickly; sufficiency is checked over the register's own review window, which the register itself sets and publishes. A request for further information during that window pauses the clock until the applicant responds.
Forks
If the file supports a licence application with no prior dispute, the five stages above run in sequence with no branching. If a document in the file depends on removed or disputed content held by a third-party platform, that dispute follows its own track and should not delay the rest of the file — Platform takedown procedure step by step.
If the evidence of ownership behind an operational document comes from a design or development agency rather than from a corporate register, the assembly principle for that piece differs and needs separate confirmation before it goes into the file — Games and interactive entertainment — when an agency keeps.
Cost factors
Effort on a file scales with four things: the number of registers the applicant must be checked against, the number of jurisdictions the group structure touches, whether the review clock has already started elsewhere, and whether any document group has an open dispute attached to it. A single-entity applicant with no disputes assembles faster than a group structure spanning several registers. We give a first read on scope within minutes during working hours, and a firm estimate of the work involved within one working day.
How the file is structured
In practice the file is built as a single indexed set: corporate documents first, ownership and control second, operational third, personal-data confirmations last. Each group carries its own signature page, and the index page cross-references every document to the checklist item it answers. This order is not fixed by the register; it reflects how verification catches inconsistencies fastest, working from entity identity outward to activity detail.
Sources and limit
This page describes the assembly procedure only. It does not set out which activities require authorisation or what a register charges for review — those questions belong to a different part of the site. It does not replace a checklist issued directly by a specific register, which should always be read alongside this sequence.
Verified
Reviewed as a procedural description of the assembly sequence used across current filings. No statutory citation applies to a procedure page; document requirements should be confirmed against the current checklist of the receiving register before a file is finalised.
FAQ
How long does file assembly and submission take in practice?
Assembly time depends on how many document groups are incomplete at the start and how many signatories are involved. A file with all groups ready moves through verification quickly; a file with gaps in ownership or personal-data documents takes longer, because those groups usually need input from people outside the applicant's immediate team.
Which documents are needed to start?
Scoping needs a current corporate extract and a first list of who holds ownership or control. Everything else — operational description, safeguarding arrangements, personal-data confirmations — is collected once that base is confirmed against the register's checklist.
What happens if the other side does not respond?
Where a document depends on a third party — a partner institution, a former counterparty, a co-founder no longer active in the business — a non-response stalls that one document group without stopping the rest of the file. The remaining groups continue through verification, and the outstanding item is filed as soon as it arrives, subject to the register's own rules on partial submissions.
Related publications
The stage that follows submission is answered separately: Responding to supervisory questions step by step.
Next step
If custody of the underlying assets sits with a platform rather than with the applicant, that changes what belongs in the file and who signs it. Start there — When custody is held by a platform.