Resource center

Digital assets.

Crypto-asset regulation once the authorisation is done and the reporting starts: MiCA supervisory templates, whitepaper tagging, and the exchange of crypto transaction data under CARF and DAC8.

Crypto-asset firms in the European Union now carry two distinct reporting duties that arrived from different directions. The Markets in Crypto-Assets Regulation makes supervision routine: authorised service providers and token issuers submit structured returns to their national competent authority, and issuers publish a whitepaper in a machine-readable format rather than a document nobody can parse. Separately, the Crypto-Asset Reporting Framework and the directive that implements it in the European Union bring crypto transactions into the same automatic exchange of information model that already covers financial accounts.

The two regimes ask different questions of the same business. Supervisory reporting is about the firm: activity volumes, the assets it handles, its own position. Exchange reporting is about the customer: who they are, where they are resident, and what they transacted. Firms that treat them as one project usually discover the data models do not overlap as much as expected, and that customer due diligence records are the constraint on both.

This pillar collects what the REGREP Regulatory Team publishes across both — practitioner guides, the questions we are asked repeatedly, and reference material on schemas, templates and transaction mappings. Every record cites at least one official source, the regulation, technical standard or authority guidance it rests on, and carries the date it was last reviewed. Template and schema revisions are tracked as immutable versions, so a guide written against one version says so.

Nothing here is legal, tax or regulatory advice, and both the templates and the submission channels differ by national competent authority. Confirm the current version and channel with your authority before you file. When you are ready to produce the return or the exchange file rather than read about it, each obligation maps to a REGREP module.

What sits in this pillar

Frameworks
MiCA · CARF / DAC8
Filing population
Authorised crypto-asset service providers, token issuers, and crypto-asset reporting entities under the exchange framework
Resource types
Guides · Questions and answers · Datasets · Catalogues
Publishing standard
At least one official source, a link target and a review date on every record
Byline
REGREP Regulatory Team

The frameworks

Who files, what is filed, and the REGREP module that produces it.

All regulation pages

MiCA — supervisory reporting

Authorised service providers and issuers
Who files
Crypto-asset service providers authorised in the European Union, and issuers of asset-referenced and electronic money tokens, reporting to their national competent authority.
What is filed
Structured supervisory returns on the prescribed templates, covering the firm’s activity and the assets it issues or handles, on the cadence set for each report.
Where it breaks
Classification of the asset and the service, reference data that does not resolve, and internal figures that cannot be reconciled to the template definitions.

MiCA — whitepaper tagging

Machine-readable whitepapers
Who files
Issuers publishing a crypto-asset whitepaper, and the advisers preparing it on their behalf ahead of notification to the authority.
What is filed
The whitepaper marked up in inline XBRL against the applicable taxonomy, so that the required disclosures are machine-readable as well as human-readable.
Where it breaks
Tagging decisions on narrative sections, disclosures present in the text but absent from the tagged output, and late drafting changes that invalidate earlier markup.

CARF / DAC8

Exchange of crypto transaction data
Who files
Reporting crypto-asset service providers under the exchange framework, filing with the authority in their jurisdiction of registration.
What is filed
An annual submission of reportable users and their crypto-asset transactions, exchanged onward with each user’s jurisdiction of residence in the same model as financial account reporting.
Where it breaks
Self-certification and residence determination, taxpayer identification number structure, transfers with no counterparty jurisdiction, and mapping product events to the reportable transaction types.

Resources

Everything published under this pillar, newest first.

Search the full library

Filing dates for these frameworks

Reviewed submission dates, shown in each deadline’s local timezone with the official source attached. Guidance only — always confirm the current date with your national competent authority.

Deadline calendar

Reading is one thing. Filing is another.

Produce the supervisory return or the exchange file on your own data, and read the validation report before anything reaches an authority.