Recherche vérifiée par sources: OECD CARF 2027 Crypto
Le corps de l'article est affiché dans sa version anglaise vérifiée. La traduction sera ajoutée après revue des sources.
Direct answer
The OECD Global Forum reports that 76 jurisdictions are formally committed to implement the Crypto-Asset Reporting Framework, with most planning to begin automatic exchange of crypto-asset transaction information by 2027. CARF is a reporting and information-exchange framework, not a universal transaction tax or proof that every platform, wallet and user falls within identical rules. Platforms and users should identify the implementing jurisdiction, reporting service provider, covered crypto assets and transactions, tax residence and self-certification process, data-correction route and first reporting period from current local law and official guidance.
Réduire
Verified source facts
1. The OECD Global Forum states that 76 jurisdictions are formally committed to implement CARF. 2. The Global Forum says most committed jurisdictions are set to begin automatic exchanges of crypto-asset transaction information by 2027. 3. The 2025 implementation update was approved by the CARF Group and adopted by Global Forum members in November 2025. 4. The OECD has published a CARF XML schema and continued regional implementation capacity building in 2026.
Comparison at a glance
Tableau de l’article : faites défiler horizontalement ou placez le focus sur le tableau et utilisez les flèches.
| Decision layer | What to inspect | Minimum safe action |
|---|---|---|
| Jurisdiction | which country has implemented CARF | read enacted local law |
| Start period | first reportable period and exchange date | record the local timetable |
| Reporting provider | entity with the reporting duty | match the contracting entity |
| Covered asset | crypto assets inside local scope | classify each product |
| Covered transaction | exchange, transfer or other reportable activity | map event types to guidance |
| Tax residence | jurisdictions linked to the user | maintain accurate self-certification |
| Data fields | identity and transaction information | review official notices |
| Due diligence | provider validation and reasonableness checks | respond through authenticated channels |
| Correction | route for inaccurate reported data | retain records and correction contacts |
| User boundary | reporting framework versus tax liability | seek jurisdiction-specific advice |
1. Usage and measurement test: Jurisdiction
Stablecoin adoption cannot be inferred from a single gross counter. The jurisdiction dimension concerns which country has implemented CARF. Define the economic job, unit of observation, time window and entities included before counting, then read enacted local law. Otherwise one routed transaction, exchange rebalance or contract hop may be mistaken for several independent users or payments.
Separate ledger events from economic outcomes. A transfer can be real on-chain yet still represent internal treasury movement, automated arbitrage, bridge routing, collateral management or redemption rather than a purchase. Official sources can frame the categories, but they do not resolve legislative timing. The dataset and classification method therefore belong beside every headline number.
For jurisdiction, publish the numerator, denominator and exclusions that support the claim. Make the analyst read enacted local law, and compare at least one activity metric with one outcome metric relevant to which country has implemented CARF. Because legislative timing remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
2. Usage and measurement test: Start period
The start period dimension concerns first reportable period and exchange date. Define the economic job, unit of observation, time window and entities included before counting, then record the local timetable.
Official sources can frame the categories, but they do not resolve implementation delay.
For start period, publish the numerator, denominator and exclusions that support the claim. Make the analyst record the local timetable, and compare at least one activity metric with one outcome metric relevant to first reportable period and exchange date. Because implementation delay remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
3. Usage and measurement test: Reporting provider
The reporting provider dimension concerns entity with the reporting duty. Define the economic job, unit of observation, time window and entities included before counting, then match the contracting entity.
Official sources can frame the categories, but they do not resolve cross-border allocation.
For reporting provider, publish the numerator, denominator and exclusions that support the claim. Make the analyst match the contracting entity, and compare at least one activity metric with one outcome metric relevant to entity with the reporting duty. Because cross-border allocation remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
4. Usage and measurement test: Covered asset
The covered asset dimension concerns crypto assets inside local scope. Define the economic job, unit of observation, time window and entities included before counting, then classify each product.
Official sources can frame the categories, but they do not resolve local exclusions.
For covered asset, publish the numerator, denominator and exclusions that support the claim. Make the analyst classify each product, and compare at least one activity metric with one outcome metric relevant to crypto assets inside local scope. Because local exclusions remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
5. Usage and measurement test: Covered transaction
The covered transaction dimension concerns exchange, transfer or other reportable activity. Define the economic job, unit of observation, time window and entities included before counting, then map event types to guidance.
Official sources can frame the categories, but they do not resolve de minimis treatment.
For covered transaction, publish the numerator, denominator and exclusions that support the claim. Make the analyst map event types to guidance, and compare at least one activity metric with one outcome metric relevant to exchange, transfer or other reportable activity. Because de minimis treatment remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
6. Usage and measurement test: Tax residence
The tax residence dimension concerns jurisdictions linked to the user. Define the economic job, unit of observation, time window and entities included before counting, then maintain accurate self-certification.
Official sources can frame the categories, but they do not resolve multi-residence cases.
For tax residence, publish the numerator, denominator and exclusions that support the claim. Make the analyst maintain accurate self-certification, and compare at least one activity metric with one outcome metric relevant to jurisdictions linked to the user. Because multi-residence cases remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
7. Usage and measurement test: Data fields
The data fields dimension concerns identity and transaction information. Define the economic job, unit of observation, time window and entities included before counting, then review official notices.
Official sources can frame the categories, but they do not resolve local field additions.
For data fields, publish the numerator, denominator and exclusions that support the claim. Make the analyst review official notices, and compare at least one activity metric with one outcome metric relevant to identity and transaction information. Because local field additions remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
8. Usage and measurement test: Due diligence
The due diligence dimension concerns provider validation and reasonableness checks. Define the economic job, unit of observation, time window and entities included before counting, then respond through authenticated channels.
Official sources can frame the categories, but they do not resolve review frequency.
For due diligence, publish the numerator, denominator and exclusions that support the claim. Make the analyst respond through authenticated channels, and compare at least one activity metric with one outcome metric relevant to provider validation and reasonableness checks. Because review frequency remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
9. Usage and measurement test: Correction
The correction dimension concerns route for inaccurate reported data. Define the economic job, unit of observation, time window and entities included before counting, then retain records and correction contacts.
Official sources can frame the categories, but they do not resolve resolution time.
For correction, publish the numerator, denominator and exclusions that support the claim. Make the analyst retain records and correction contacts, and compare at least one activity metric with one outcome metric relevant to route for inaccurate reported data. Because resolution time remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
10. Usage and measurement test: User boundary
The user boundary dimension concerns reporting framework versus tax liability. Define the economic job, unit of observation, time window and entities included before counting, then seek jurisdiction-specific advice.
Official sources can frame the categories, but they do not resolve individual outcome.
For user boundary, publish the numerator, denominator and exclusions that support the claim. Make the analyst seek jurisdiction-specific advice, and compare at least one activity metric with one outcome metric relevant to reporting framework versus tax liability. Because individual outcome remains unobserved, the conclusion should describe measured behavior rather than declare universal adoption.
Decision scenarios
Scenario 1: when jurisdiction becomes decisive
Consider a reader whose main constraint is which country has implemented CARF. The correct response is not to infer a universal platform or product winner. It is to read enacted local law, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.
Scenario 2: when start period becomes decisive
Consider a reader whose main constraint is first reportable period and exchange date. It is to record the local timetable, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 3: when reporting provider becomes decisive
Consider a reader whose main constraint is entity with the reporting duty. It is to match the contracting entity, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 4: when covered asset becomes decisive
Consider a reader whose main constraint is crypto assets inside local scope. It is to classify each product, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 5: when covered transaction becomes decisive
Consider a reader whose main constraint is exchange, transfer or other reportable activity. It is to map event types to guidance, retain the evidence, and define a stop condition before funds or permissions are committed.
Scenario 6: when tax residence becomes decisive
Consider a reader whose main constraint is jurisdictions linked to the user. It is to maintain accurate self-certification, retain the evidence, and define a stop condition before funds or permissions are committed.