Unified Enterprise Compliance Platform for Tax Information Reporting

What

Each reportable customer's residence, TIN, and crypto transaction data.

When

Live in early-adopter jurisdictions, with reports filed once a year.

What's next

Find out which of your customers and transactions are reportable.

The stakes

The hard part of CARF and DAC8 isn't the filing.

Your KYC stack doesn't cover this obligation

CARF and DAC8 require self-certifications and identification numbers that identity verification was never built to collect. These requirements sit on top of KYC, with different data, rules, and legal basis.

Gaps carry real consequences

Missing self-certifications and invalid identification numbers do more than delay a filing. In some jurisdictions, they bring penalties or a duty to restrict the account.

Eligibility is decided at the account level

Before any transaction is examined, each account needs its own answer on whether it's reportable and under which regime. That answer has to hold in every jurisdiction and under review.

A framework that keeps moving

CARF, DAC8, and CRS 2.0 each roll out on their own timelines, and more jurisdictions keep signing on. Your reporting has to keep pace without a rebuild for every new rule.

How it works

From fragmented data to defensible, regulator-ready reporting.

Data ingestion

Account data, self-certifications, transaction records, and custody data, normalized into a single reporting-ready schema.

Self-certification

A drop-in SDK collects CARF and DAC8 self-certification data at onboarding, with built-in validation and re-certification workflows.

Rules engine

Jurisdiction-specific rules determine who is reportable, under which regime, and to which authority.

Validation and filing

Automated checks flag missing identification numbers, invalid residency data, and schema errors before filing. Reports are generated in each jurisdiction's required format.

Your exposure

Explore CARF and DAC8 requirements by jurisdiction.

These obligations can vary by jurisdiction, business model, and the products you offer. Select a jurisdiction to see the current requirements and implementation status.

This tracker is updated as jurisdictions publish new guidance, implementation timelines, and reporting requirements.

Not sure where your gaps are? Take the impact assessment

Select your jurisdiction

Europe

Germany

● Live now

Framework

DAC8 (CARF in EU law)

Collection begins

1 Jan 2026

First report due

2027

Registration

RCASP registration required

If not ready

Penalties + account freeze duty

Additional details

View regulatory detail →

Speak to a CARF specialist

The brokers reporting through Taxbit.

“By automatically collecting information, remediating inaccuracies, and generating the required forms, we save companies and end-customers crucial time and significantly reduce operational costs.”

Edward Woodford · CEO & Founder, Zero Hash

CARF and DAC8 reporting for crypto exchanges, brokers, and wallet providers.

The hard part of CARF and DAC8 isn't the filing.

From fragmented data to defensible, regulator-ready reporting.

Explore CARF and DAC8 requirements by jurisdiction.

The brokers reporting through Taxbit.

Know where you stand on CARF and DAC8.