Rule · EBA · 8 Nov 2023
Crypto-asset service providers must report holder and transaction data to issuers of asset-referenced tokens using templates S 06.00, S 07.01, and S 07.02. Template S 06.00 requires specific holder details including names, unique codes, and country of residence as of the reference date. Template S 07.01 mandates transaction-level information such as distributed ledger addresses, account numbers, values, and settlement dates to facilitate issuer reconciliation. Template S 07.02 requires providers to disclose public distributed ledger addresses used for client transfers to assist issuers in identifying non-custodial wallet transactions.
ANNEX IV
REPORTING FOR CRYPTO-ASSET SERVICE PROVIDERS - INSTRUCTIONS
Table of Contents
PART I: GENERAL INSTRUCTIONS ....................................................................... 2
I. STRUCTURE................................................................................................. 2
II. SCOPE OF REPORTING ................................................................................... 2
PART II: INFORMATION ON HOLDERS (S 06.00) ................................................. 3
III. GENERAL REMARKS ON TEMPLATE S 06.00........................................................ 3
IV. INSTRUCTIONS CONCERNING SPECIFIC POSITIONS OF TEMPLATE S 06.00 ................ 3
PART III: INFORMATION ON TRANSACTIONS (S 07.01 AND S 07.02) ................... 4
V. GENERAL REMARKS ON TEMPLATE S 07.01........................................................ 4
VI. INSTRUCTIONS CONCERNING SPECIFIC POSITIONS OF TEMPLATE S 07.01 ................ 5
VII. GENERAL REMARKS ON TEMPLATE S 07.02........................................................ 6
VIII. INSTRUCTIONS CONCERNING SPECIFIC POSITIONS OF TEMPLATE S 07.02 ................ 7
PART I: GENERAL INSTRUCTIONS
I. Structure
PART II: INFORMATION ON HOLDERS (S 06.00)
III. General remarks on Template S 06.00
7. Template S 06.00, following Article 22(3) of Regulation (EU) 2023/1114,
contains necessary information on the holders for the issuers, for them to comply with the reporting requirements set out in this Regulation.
8. This template shall contain information as at the end of the reference date, in line
with template S 01.00 ‘Number of holders – at reference date’ for issuers as presented in Annex I and II of this Regulation. The country of a holder shall be determined by the holders` location, which shall be based on:
(a) For natural persons, their habitual residence; (b) For legal persons, the registered office address.
IV. Instructions concerning specific positions of Template S 06.00
Column Legal references and instructions
0010 Name
The full name for natural persons and the official registered name for legal persons, including any references to the company type in accordance with the national company law, in accordance with the unique identifier provided of the holder in column 0020 of this template. 0020 Code The code as part of a row identifier must be unique for each reported entity. The code shall be unique and used consistently across the templates and across time. The code shall always have a value. The code of the holder, such as national identification number for natural persons or legal entity identifier (LEI) code for legal persons, or any other available applicable official identifier. If a LEI is available, this LEI shall be reported. In order to facilitate the data reconciliation process of the issuers, the following approach shall be considered when reporting the code. There are two lists consisting different types of codes, one for natural persons, and one for legal entities. Crypto-asset service providers shall report the first available type of code from the list specified in column 0030, starting from the 1st option on the list, then moving down one by one for the rest of the options, in case that type of identifier is not available of the holder. 0030 Type of code Types of codes of natural persons:
1. National identification number
2. National tax number
3. Passport number
4. Other type of identification number
Types of codes of legal persons:
1. Legal entity identifier (LEI) code
2. Official national registration number
3. Official registered tax number
4. Other type of identification number
The type of code shall always be reported.
0040 Retail/Non-retail
Include Retail or Non-retail, based on the holder in scope.
Retail shall be included in case the holder in scope qualifies as a retail holder. Non-retail shall be included otherwise. 0050 Country Include the name of the country of the holder in scope, in accordance with paragraph 8 of this annex. Row Legal references and instructions Crypto-asset service providers shall allocate one row for each specific holder in scope. z-axis Legal references and instructions Name or ID of the assetreference d token This template shall be reported separately for each asset-referenced token in scope. The official name or ID of the asset-referenced token shall be provided based on the published White paper of the asset-referenced token, in accordance with Article 6 of Regulation (EU) 2023/1114.
PART III: INFORMATION ON TRANSACTIONS (S 07.01 and S 07.02)
V. General remarks on Template S 07.01
9. Template S 07.01, following Article 22(3) of Regulation (EU) 2023/1114,
contains necessary information on the transactions for the issuers, for them to comply with the reporting requirements set out in this Regulation.
10. This template provides information for the issuers for allocating transactions to
the applicable rows in templates S 04.01 ‘Transactions per day – average’, S
04.02 ‘Transactions per day - average_EU’, and S 05.00 ‘Transactions per day
that are associated to its uses as a means of exchange within a single currency area – average’ as presented in Annex I and Annex II of this Regulation. Cryptoasset service providers shall provide all information they possess related to the transactions in scope in this template, even if that is not complete and full for some transactions, as the goal is for the issuers to receive this template from all crypto-asset service providers in scope and reconciliate all the data received with their own data sources, and be able to prepare one common dataset for the transactions with all the necessary information.
VI. Instructions concerning specific positions of Template S 07.01
Column Legal references and instructions
0010 Hash
The hash related to the transaction in scope, as applicable based on whether the transaction settled on or off-chain. 0020 Distributed ledger address - originator The distributed ledger address of the originator involved in the transaction in scope, as applicable based on whether the transaction settled on or off-chain, in accordance with Article 14 of Regulation (EU) 2023/1113. 0030 Distributed ledger address – beneficiary The distributed ledger address of the beneficiary involved in the transaction in scope, as applicable based on whether the transaction settled on or offchain, in accordance with Article 14 of Regulation (EU) 2023/1113. 0040 Crypto-asset account number - originator The crypto-asset account number, as in Article 14(1) and 14(2) of Regulation (EU) 2023/1113, of the originator involved in the transaction in scope, as applicable based on whether the transaction settled on or off-chain, in accordance with Article 14 of Regulation (EU) 2023/1113. 0050 Crypto-asset account number - beneficiary The crypto-asset account number, as in Article 14(1) and 14(2) of Regulation (EU) 2023/1113, of the beneficiary involved in the transaction in scope, as applicable based on whether the transaction settled on or off-chain, in accordance with Article 14 of Regulation (EU) 2023/1113. 0060 Value of the transaction The value of the transaction, denominated in the actual asset-referenced token in scope for the template. 0070 Date of the transaction
The exact date when the transaction got settled.
0080 Country – originator
For the originator involved in the transaction in accordance with Article 14 of Regulation (EU) 2023/1113 the name of the country in accordance with paragraph 8 of this annex. 0090 Country – beneficiary For the beneficiary involved in the transaction in accordance with Article 14 of Regulation (EU) 2023/1113 the name of the country in accordance with paragraph 8 of this annex. 0100 In scope for Article 22(1)(d) Include Yes, in case based on the Commission Delegated Regulation (EU) 2023/xx [RTS under Article 22(6) of MiCAR] specifying the methodology to estimate the number and value of transactions associated to uses of assetreferenced tokens as a means of exchange the transaction should be in scope for template S 05.00 ‘Transactions per day that are associated to its uses as a means of exchange within a single currency area – average’ as presented in
Annex I and Annex II of this Regulation.
Include No otherwise.
Row Legal references and instructions
Crypto-asset service providers shall allocate one row for each transaction in scope. z-axis Legal references and instructions Name or ID of the assetreference d token This template shall be reported separately for each asset-referenced token in scope. The z-axis determines the asset-referenced token in scope for the template. The official name or ID of the asset-referenced token shall be provided based on the published White paper of the asset-referenced token, in accordance with Article 6 of Regulation (EU) 2023/1114.
VII. General remarks on Template S 07.02
11. Crypto-asset service providers shall provide to the issuers the public distributed
ledger addresses they use for making transfers on behalf of their clients. That is to make it easier for issuers to identity which transactions registered on the distributed ledger take place between non-custodial wallets, to provide more information to the issuers for reporting their templates as specified in Annex I and II of this Regulation, especially S 04.03 ‘Transactions and transfers per day
between non-custodial wallets – average’. Template S 07.02 ‘Distributed ledger addresses for making transfers on behalf of clients’ provides this information to the issuers.
VIII. Instructions concerning specific positions of Template S 07.02
Column Legal references and instructions
0010 Distributed ledger address
The public distributed ledger addresses the crypto-asset service provider uses for making transfers on behalf of their clients. Row Legal references and instructions Crypto-asset service providers shall allocate one row for each distributed ledger address in scope. z-axis Legal references and instructions Name or ID of the assetreference d token This template shall be reported separately for each asset-referenced token in scope. The official name or ID of the asset-referenced token shall be provided based on the published White paper of the asset-referenced token, in accordance with Article 6 of Regulation (EU) 2023/1114.
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“The distributed ledger address of the originator involved in the transaction in scope, as applicable based on whether the transaction settled on or off-chain, in accordance with Article 14 of Regulation (EU) 2023/1113.”
“Crypto-asset service providers shall provide the two sets of templates in this annex to the respective issuers separately for each asset-referenced token following Article 22(3) of Regulation (EU) 2023/1114.”
More like this from EBA
EBA published 2 documents in the last 30 days. We email you each new one the day it's published.
Source: European Banking Authority — original document · Summary generated with machine assistance and reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated