Vilnius  ·  Tallinn Working language: English  ·  First reply in minutes, price within one business day
Intellectual property · Technology · Digital assets — Lithuania & Estonia

File assembly and submission: costs drivers

Assembling and submitting an authorisation file for a digital-asset business rarely takes days. The costs drivers are the number of registers to notify, the jurisdictions involved, whether a statutory clock has started, and whether a counterparty disputes ownership of the assets in the file. Rights evidence, covered in Ownership of results: code, designs and data, often sets the timeline more than the paperwork.

How the file comes together

The process runs through a fixed sequence, whatever the sector. Intake fixes the scope: which registers apply, which jurisdictions are touched, and which entity in the group is the applicant. Gap analysis lists what is missing before anyone starts drafting. Drafting produces the file itself, built from policies, disclosures and supporting evidence. A partner signs the file off before it leaves the firm. Submission lodges the file with the competent authority, which then checks it for completeness before it checks it on the merits.

StageWhat happensTypical output
IntakeCounsel maps the business against the registers and authorisations it needsScope note
Gap analysisMissing documents and unclear ownership chains are listedGap list
DraftingPolicies, disclosures and supporting evidence are drafted or collectedDraft file
Internal sign-offA partner reviews the file before submissionSign-off record
SubmissionThe file is lodged with the competent authorityAcknowledgement of receipt
Regulator reviewThe authority checks completeness and may raise questionsDeficiency letter or decision

What drives the cost

Four factors decide how much work a file needs, independent of the sector. They also decide how many people it takes and how long assembly runs.

FactorWhy it matters
Number of registersEach register has its own document set and its own reviewer
Number of jurisdictionsCross-border structures need parallel filings and certified translations
Whether a clock has startedA running deadline compresses drafting time and raises the cost of any error
Whether a counterparty disputes ownershipDisputed provenance adds an evidentiary layer the file must carry

These factors also feed each other. A file touching three registers in two jurisdictions, with a disputed ownership chain, does not simply add the costs of each element. It multiplies the review time, because the authority checks the same evidence against three different sets of requirements. If the file has to document a past security incident, the evidentiary burden grows before drafting even starts; see Incident data protection how it is proved explained for how that proof is normally built.

Provenance and rights evidence

Digital-asset files carry a provenance problem that paper files do not. A token, a collection or a platform often bundles rights that were created, licensed or bought from someone else. The file has to show who owns what, and on what basis, before the authority looks at anything else.

Where a collection uses artwork, code or a design that a third party created, the evidence chain matters more than the description of the asset itself; see When a collection uses third-party artwork. Where the same content also carries a registered mark or design, the clearance evidence follows a similar logic to Platform takedown procedure step by step, even though the two procedures serve different purposes.

Documents you need to start

A first-pass file usually needs the following, before any sector-specific annex is added.

Documents drafted in a language the authority does not use will need a certified translation. That step alone can add several working days once the file crosses more than one jurisdiction.

Who decides, and how long it takes

The competent supervisory authority decides. It reviews the file for completeness first, then for substance. A file accepted as complete starts a review clock. A file returned as incomplete does not start that clock at all; the clock only restarts once the gaps are closed and the file is resubmitted.

The point of no return

Submission is not the point of no return. The point of no return is acceptance. Before acceptance, a file can be withdrawn and corrected without a formal record of the error. After acceptance, every amendment is a formal event, and some amendments reset the review clock rather than pausing it. This is why internal sign-off exists as a separate stage: it is cheaper to find an error before submission than to have the authority find it afterwards.

What to do

  1. Ask the compliance officer to map every register and jurisdiction the business touches.
  2. Ask legal counsel to list every rights gap before drafting starts.
  3. Resolve disputed ownership as a gap, not as a note for later.
  4. Assign one partner to sign off the file before it leaves the firm.
  5. Submit only once the gap list is empty, not once the deadline is close.
  6. Keep one named person as the single point of contact with the authority after submission.

Two scenarios

If the collection includes artwork you did not create, resolve the licence question before drafting starts, not after submission. Waiting until the file is otherwise ready only means restarting the drafting stage later.

If a former partner or platform disputes ownership of the underlying code or content, treat that dispute as a gap, not as a footnote, and close it before the file is lodged. An unresolved dispute discovered by the authority takes longer to fix than the same dispute found in-house.

What this page does not cover

This page describes the organisational steps common to most authorisation files. It does not set the fee schedule of any register, and it does not replace a jurisdiction-specific checklist for a particular sector. Where the authority has already sent questions on a file that was submitted, the next steps differ from the assembly stage described here.

Verified

This overview reflects our internal procedural practice, reviewed in the first half of 2025. It is not a substitute for the current published requirements of the register concerned, and it does not state any specific deadline or fee.

FAQ

How long does file assembly and submission take in practice?
Timing depends on the same four factors that drive cost: how many registers are involved, how many jurisdictions, whether a clock is already running, and whether ownership of any asset is disputed. A single-jurisdiction file with no disputes moves fastest through gap analysis and drafting.

Which documents are needed to start?
Corporate documents, governance documents, financial documents and rights evidence, at minimum. Sector-specific annexes are added once the gap analysis is complete and translations, where needed, are in hand.

What happens if the other side does not respond?
Where the file records a dispute over ownership or use of an asset and the other side stays silent, the file should note the attempt and the silence rather than wait indefinitely. Silence does not resolve a provenance gap; it only delays the decision on how to close it before submission.

Related reading

For the stage that follows submission, once the authority has sent questions on the file, see Responding to supervisory questions step by step.

Get help with your file

If the file is missing a required document on the AML side, treat it as the priority gap rather than paperwork to finish last; see When the file is incomplete on AML.

If the issuer and the platform are related parties, the file needs an extra layer of disclosure before it can be lodged; see When the issuer and the platform are related.

A partner responds to a first message within minutes during business hours. A fee quote for the file follows within one business day.

Make an enquiry

Or email us directly: info@aurelislaw.com