DAC8 requires CASPs to collect and report a comprehensive set of data fields for each reportable user and their transactions. This article provides the definitive list of all required data fields.
User Identification — Individuals
The following fields must be collected and reported for each individual user: first name, middle name (if available), last name, name prefix and suffix (if applicable), date of birth, place of birth (city and country, when available), current residential address (street, building number, apartment/suite, floor, city/town, subentity/state/province, postal code, country code), each jurisdiction of tax residence, Tax Identification Number for each jurisdiction of tax residence, the jurisdiction that issued each TIN, and self-certification status and date.
User Identification — Entities
For entity users: legal name, legal address (same structured format as individuals), jurisdiction of incorporation or organization, TIN for each jurisdiction of tax residence, entity type (corporation, partnership, trust, foundation, etc.), and for each controlling person the same individual identification fields listed above.
Transaction Data Fields
For each reportable user and each combination of transaction type and crypto-asset: the crypto-asset name, the crypto-asset identifier (distributed ledger address or similar), the crypto-asset classification (MiCA category), the transaction type (fiat-to-crypto, crypto-to-crypto, transfer, or payment), the aggregate gross amount in the reporting currency, the aggregate number of units, the aggregate fair market value in the reporting currency, and the total number of transactions during the reporting period.
Account Data Fields
For each reportable user: the unique account identifier or reference number assigned by the CASP, the account opening date, the account status (active, dormant, closed), and the account balance in crypto-assets at the end of the reporting period (when applicable).
Report Metadata Fields
For the report itself: the reporting CASP's legal name, address, TIN, and jurisdiction, the reporting period (calendar year), the message type (new, correction, deletion), a unique message reference ID, and timestamps for report generation and submission.
Conclusion
The comprehensive nature of DAC8's data requirements means that CASPs must build data collection processes that capture all required fields from the moment of user onboarding. Gaps in data collection will result in incomplete reports and potential penalties.
Preparing for DAC8?
Our team helps CASPs with gap analysis, transposition tracking, TIN validation, and XML report generation.