TechFlow Logo
Login/ Sign up
ETH Gas
Gwei
Fear
gas
What to Report in CARF? Interpretation of Reportable Information and Local Implementation Variances

What to Report in CARF? Interpretation of Reportable Information and Local Implementation Variances

2026.09.09
Share
This paper outlines the basic framework for reportable information under CARF, the key differences in local implementation, and the preparations RCASP can undertake at the data and system levels.

By: FinTax

Introduction

In previous articles in the CARF series, we discussed and analyzed under the CARF framework “who needs to report” and “where to report.” The former addresses the identification of the Reporting Crypto-Asset Service Provider (RCASP), while the latter determines in which jurisdictions the RCASP bears due diligence and reporting obligations through the Reporting Nexus rules. After establishing the reporting entity and reporting jurisdiction, the implementation of CARF obligations raises a more specific question—which information must the RCASP declare to the competent authority?

CARF reporting requires the RCASP to identify reportable users and relevant controlling persons based on its due diligence procedures, classify and aggregate transactions related to their crypto-assets according to prescribed methods, and ultimately generate report fields covering three categories: RCASP information, user information, and transaction information.

The OECD provides an internationally unified standard, but each jurisdiction must implement it through local laws and technical specifications. Therefore, understanding what CARF requires to be reported not only involves returning to the OECD rules themselves but also further examining how local implementation rules alter the final reporting content.

This article outlines the basic framework of CARF reportable information, the main differences in local implementation, and the preparations RCASPs can make at the data and system levels, with the aim of providing practical guidance.

I. Reportable Information Under the OECD CARF Rules

(1) What Constitutes “Relevant Crypto-Assets” Within the CARF Scope

Asset classification is the foundation of transaction reporting. According to the definitional clauses of CARF, the term “crypto-asset” refers to digitized value that relies on distributed ledger technology or similar technology for verification and security. In principle, a “Relevant Crypto-Asset” covers all assets meeting the definition of a crypto-asset, excluding:

  • Central Bank Digital Currencies (CBDCs);
  • Specified Electronic Money Products (SEMPs);
  • Crypto-assets that the Reporting Crypto-Asset Service Provider has fully determined cannot be used for payment or investment purposes.

Judging mainstream assets such as BTC and ETH is usually straightforward, while stablecoins, NFTs, tokenized securities, and certain utility tokens require further analysis.

Figure 1: Schematic Diagram of the Scope Adjustments Between CARF and CRS

(2) What Exactly Does CARF Require to Be Reported? Three Categories of Information: RCASP, Users, and Transactions

Reportable information is divided into three major categories: information about the Reporting Crypto-Asset Service Provider (RCASP information), information about reportable users or reportable persons (user information), and information about transactions involving relevant crypto-assets (transaction information), which together constitute the complete CARF reporting content.

RCASP Information

Name, address, and identification number of the Reporting Crypto-Asset Service Provider.*

* Identification numbers adopt the Taxpayer Identification Number (TIN); if no TIN exists, the company registration code or Global Legal Entity Identifier (LEI) shall be used. If the RCASP has been assigned no identification number, only its name and address need to be reported.

User Information

  • Name, address, place of residence, Taxpayer Identification Number (TIN)*, date of birth, and place of birth* of individual users;
  • Name, address, place of residence, and Taxpayer Identification Number (TIN) of entity users; for reportable entity controlling persons identified through due diligence procedures*, the information also includes the controller's name, address, place of residence, TIN, date of birth and location, and capacity as a controller.

* Place of birth information for individual users does not need to be reported unless otherwise stipulated by the law of the country where the RCASP is located.

* The Taxpayer Identification Number (TIN) refers to the identification number assigned to the taxpayer by the tax resident jurisdiction of the user or entity controller, rather than the number issued by the platform's jurisdiction, transaction location, or source of income jurisdiction.

If a single user is recognized as having multiple tax residency locations, the report must reflect each tax resident jurisdiction where the user resides, along with the corresponding TIN for each; selective reporting is not permitted.

* Due diligence and information reporting for entity users may further look through to controlling persons. CARF requires the RCASP to first identify the controllers of the entity, then determine whether the relevant controllers qualify as Reportable Persons. Entity controllers included in the reporting scope must meet dual criteria of tax residency and control, meaning they must not only be tax residents of the reportable jurisdiction but also exercise control over the entity—the core assessment standard being “controlling ownership interest.” Holding a specified proportion of shares, serving as a senior executive, or acting as the settlor, trustee, or beneficiary of a trust may all meet this standard.

Transaction Information

For each type of relevant crypto-asset defined under CARF*, the following shall be reported:

  1. The full legal name of the relevant crypto-asset type;
  2. Purchase and disposal of relevant crypto-assets for fiat currency: total amount paid/received*, total number of units, and number of relevant transactions;
  3. Purchase and disposal of relevant crypto-assets exchanged for other relevant crypto-assets: total fair market value*, total number of units, and number of relevant transactions;
  4. Reportable retail payment transactions*: total fair market value, total number of units, and number of transactions;
  5. Transfer of other relevant crypto-assets to or from reportable users: transfer transactions not falling under the above types, subdivided by transfer type (e.g., airdrops, staking rewards, loan payments, goods or services exchange), listing the total fair market value, total number of units, and number of relevant transactions;
  6. Transfers to unknown external wallets: total fair market value, total number of units.

* The total amount paid/received refers to the net amount after deducting transaction fees and must be reported in the fiat currency used at the time of the transaction. If multiple fiat currencies are involved, they shall be reported in a single fiat currency, converted consistently every time a relevant transaction occurs. For example, consistently using the spot exchange rate at the time of the transaction.

* The valuation point for total fair market value is the time of the transaction, and transaction fees shall be deducted; it must be determined and reported in a single fiat currency, valued consistently every time a transaction occurs. Regarding valuation methods, the RCASP should prioritize relying on the trading pairs it maintains itself. In the absence of applicable internal trading pair prices, alternative valuation methods may be used sequentially, such as internal accounting book value, value provided by third-party companies or websites, the RCASP’s latest valuation of the asset, or reasonable estimates.

* To qualify as a reportable retail payment transaction, the amount threshold must reach USD 50,000. However, payment transfers below this threshold are not exempt from reporting; instead, they should be aggregated under the items of “transfer of other relevant crypto-assets to or from reportable users” and “transfers to unknown external wallets.”

* If a user transfers crypto-assets to their private wallet or to an account operated by another platform, thereby making the complete transaction situation unrecognizable to the RCASP, the RCASP must also report it as a transfer to an unknown external wallet.

* The rules require categorizing and aggregating all transactions. If a relevant crypto-asset is non-fungible, and different variants of that relevant crypto-asset have different values within fixed units, each unit shall be treated as a separate relevant crypto-asset type.

II. Implementation Differences: From OECD Standards to Local Reporting Requirements

The CARF rules and commentaries published by the OECD provide a unified international standard, but they are ultimately transposed into local law for implementation by each jurisdiction. Core rules such as the definition of relevant crypto-assets, transaction category classification, and reporting fields are highly aligned with OECD standards, but local policies may exhibit significant differences in certain implementation details.

(1) Whether the Reporting Targets Include Domestic Users

The original OECD CARF framework primarily serves cross-border automatic exchange of tax information. “Reportable Jurisdiction” refers to jurisdictions that have already established a CARF information exchange arrangement and are listed in the public list of implementing jurisdictions; reporting focuses on tax residents of other reportable jurisdictions. Some jurisdictions have added local reporting requirements, meaning the RCASP must simultaneously report information on domestic tax resident users to the local tax authority.

For example, the UK established through the Finance Act 2026 the reporting obligation of UK RCASPs for UK tax resident users and relevant controllers. Current HMRC guidelines explicitly require RCASPs to collect all user information and report data on UK tax residents as well as tax residents of other CARF participating jurisdictions. The New Zealand Inland Revenue Department’s published list of CARF reportable jurisdictions includes its own country, meaning New Zealand tax residents also fall within the local reporting scope. Its official guidelines further clarify that when an RCASP holds both New Zealand resident and non-resident users, the identity information and relevant transaction data of both must be submitted to the tax authority, with resident data used for domestic tax administration and non-resident data exchanged to their home tax authority pursuant to the CARF arrangement.

Meanwhile, jurisdictions such as Japan and Singapore do not uniformly include their domestic tax residents within the CARF reporting scope, adopting handling methods closer to the original OECD framework. Nevertheless, RCASPs still need to conduct due diligence procedures for all users, including domestic users, to identify which ones fall within the reportable scope; the absence of a local reporting requirement does not exempt them from this obligation.

Therefore, the scope of due diligence does not equal the final reporting scope, and the scope of international exchange does not necessarily equal the reporting scope required by the local tax authority.

(2) Conversion to Single Fiat Currency and Valuation Methods

Transaction amounts and fair market values ultimately need to be converted into fiat currency for reporting according to CARF rules. Whether each jurisdiction further designates a reporting currency will directly impact the RCASP’s data conversion and reporting system.

For instance, South Africa’s SARS CARF regulations (Notice 6887) explicitly stipulate that transaction amounts and fair market values must be determined and reported in South African Rand (ZAR). The tax authority’s FAQ responded to the compliance burden and practical challenges potentially faced by high-volume platforms, elaborating in greater detail on the requirements for consistent conversion and valuation methods. It points out that CARF does not require RCASPs to perform real-time currency conversion, nor does it restrict specific exchange rate sources or per-transaction pricing methods, instead permitting reasonable methods such as batch processing, applying end-of-day exchange rates, or using appropriate averages. High transaction volumes, asset price volatility, and differing market data sources can be balanced through the operational flexibility of the RCASP.

(3) Whether the Amount Threshold Is Converted to a Local Currency Standard

Under OECD rules, only retail payment transactions reaching a USD 50,000 threshold are summarized as reportable retail payment transactions; otherwise, they fall under other transaction categories.

Local jurisdictions may convert this into a local currency standard during domestic implementation. For example, Japan sets the threshold for reportable retail payment transactions at JPY 5,000,000 (approximately USD 31,273), Brazil uses a BRL equivalent to USD 50,000, the EU’s DAC8 adopts a USD 50,000 or equivalent currency threshold, while some other jurisdictions retain the original USD standard.

There are several forms of localizing the reportable retail payment transaction amount threshold, including setting a fixed local currency amount or converting the USD standard into an equivalent local currency amount. This distinction will affect how RCASPs categorize and aggregate relevant crypto-asset transactions in practice. The same transaction may be classified into different CARF transaction categories depending on the applicable jurisdiction—one forming part of retail payment transactions in Jurisdiction A, but categorized as other types of transfer transactions in Jurisdiction B.

(4) Detail Differences in Specific Reporting Fields

The OECD rules uniformly stipulate core reporting fields for individual users, entity users, and their controllers, while leaving certain room for local legislation.

Place of birth for individual users does not need to be reported in principle, except where the law of the jurisdiction where the RCASP is located provides otherwise. Regarding the Taxpayer Identification Number (TIN), if the tax resident jurisdiction of the reportable user or relevant controller has not issued a TIN, or if local law does not require collection, the TIN does not need to be reported. In response to this, Singapore’s IRAS explicitly permits providing corresponding reason codes in accordance with its CARF XML rules for the aforementioned situations.

Furthermore, even where TIN submission is required, the format of the numbers varies across jurisdictions. In the UK, the National Insurance Number (NINO) for individuals or relevant entity controllers, the Company Registration Number (CRN) for UK companies, and the Unique Taxpayer Reference (UTR) for partnerships and trusts serve as their corresponding tax identification numbers.

(5) Whether Declaration Is Still Required When No Reportable Information Exists

Whether an RCASP is still required to submit a declaration to the tax authority if there is no information on any reportable users or relevant transactions within a reporting year also depends on the regulations of its jurisdiction.

The UK explicitly adopts a “no data, no filing” model. Singapore in principle requires filing a nil return, meaning only RCASP information needs to be filled out, without user and transaction data. Additionally, the Japanese National Tax Agency’s CARF FAQ clarifies the relationship between transaction amounts and reportable information. If a reportable transaction contract relationship that has not yet terminated exists, the RCASP is still required to file an annual report even if no transaction volume associated with that contract was generated in a particular year.

III. How RCASPs Should Prepare CARF Data and Systems

(1) Embedding CARF Tax Due Diligence Into User KYC Processes

Client AML/KYC materials serve as a verification mechanism for tax self-certification under CARF, thus constituting an important foundation for the RCASP to fulfill due diligence obligations. When fulfilling AML/KYC obligations, the RCASP typically already possesses natural persons’ names, addresses, identification documents, as well as entities’ registration information, ownership structures, and beneficial owners; this data does not need to be collected again. For reporting purposes, CARF also focuses on tax resident jurisdictions, TINs, whether relevant entity controllers qualify as Reportable Persons, and the validity of tax self-certifications. For ownership structure and beneficiary information already collected via KYC, the RCASP must further assess whether these individuals meet the definitions of “entity controller” and “reportable person.” Given the partial overlap between KYC materials and CARF data, the two should share underlying data while undergoing distinct assessments. Practically speaking, enterprises need to add a layer of CARF data requirements on top of their existing KYC frameworks rather than rebuilding a completely disjointed client system from scratch.

(2) Establishing a Unified Fiat Currency Conversion and Valuation Mechanism

During the integration and reporting of transaction information, the fiat currency unit adopted will affect transaction amount conversion, fair market value assessment processes, transaction category classification, and other matters. Relevant localization requirements significantly impact system design for global RCASPs. At minimum, RCASPs should retain the original transaction currency, transaction amount, exchange rate at the time of the transaction, the converted reporting amount and currency, as well as the valuation time and method, rather than solely storing the converted results. Even if a jurisdiction updates policy requirements to designate a local currency for reporting, the RCASP can still generate compliant reports from underlying transaction data.

(3) Perfecting the CARF Localization Rule Framework

Although OECD CARF can serve as a unified foundational data standard, the local implementation differences mentioned in this article demonstrate that the final reporting logic remains grounded in specific jurisdictions. RCASPs need to identify in which jurisdiction(s) they generate and fulfill CARF compliance obligations, and confirm whether the reporting scope includes domestic tax residents, which jurisdictions are publicly listed as reportable, whether optional fields such as individual user places of birth need to be submitted, and whether zero filings are required when no reportable information exists. Differences in local policies are also reflected in the formats of tax identification numbers for user information submissions. Ultimately, the report fields submitted must be assessed based on the local legislation and technical specifications of both the RCASP’s and users’ jurisdictions; such differences cannot be handled by merely relying on a single unified rule set.

Conclusion

The content of a CARF annual report is built upon a series of prior determinations, meaning RCASPs cannot wait until the day before the reporting deadline to begin preparation; instead, they must integrate CARF compliance into business operation chains such as client management, KYC processes, and trading systems. The global rollout of CARF has gradually entered a phase of local legislation and enforcement, and the unified standards constructed by the OECD will inevitably continue to fragment. For cross-border operating crypto-asset service providers, the same batch of user and transaction data must be configured separately according to the domestic rules of the involved jurisdictions in actual reporting. Whether local rules and system data can be thoroughly streamlined in advance will directly impact whether subsequent CARF reporting can be implemented accurately and stably.