Brokers face a global layer (CARF/DAC8) and a US domestic layer (1099-DA and backup withholding). Here's how to meet both from one data layer.

A broker-dealer handling crypto for clients has two reporting jobs, and too many firms buy them separately. One is global: CARF and DAC8. The other is domestic, for US clients: Form 1099-DA and its backup withholding. Both run off the same customer and transaction data. Split them into two projects with two vendors and you pay twice, then still find gaps.
CARF and DAC8 make up the cross-border layer. You find reportable users, check their tax IDs, work out gains, and file in whatever format each authority accepts. Your reporting country tracks where the business is based, so you file once and the data flows onward. Start with the CARF and DAC8 overview, and if your obligations aren't clear yet, deadlines by country.
For US clients a second layer kicks in, a domestic one CARF doesn't touch: reporting disposals on Form 1099-DA, plus the 24% backup withholding that bites when a tax ID is missing or wrong. And the trigger, that bad tax ID, is the very data point that drives reporting. So the work behind a clean 1099-DA is the same work that keeps you clear of backup withholding.
Run both on one platform for a simple reason: they share everything underneath. The customer identity. The tax-ID check. The transaction ledger. Check a tax ID one time at onboarding and that result feeds the CARF filing, the 1099-DA filing, and the backup-withholding call. Our platform runs CARF and DAC8 and 1099-DA reporting off the same data, so a broker clears both from a single integration. Book a demo to see it on your own data.
In practice it looks like this. A client signs up once, hands over a W-9 or a self-certification, and the tax ID gets checked a single time. That one verified identity then flows into the CARF or DAC8 report on the cross-border side, into the 1099-DA on the US side, and into the backup-withholding decision if the tax ID ever fails. No second onboarding. No second reconciliation. No gap where a client gets reported one way and withheld the other. That's the gap between managing one vendor and reconciling three.
A broker with US clients usually faces both. CARF and DAC8 cover cross-border reporting; Form 1099-DA and its backup withholding are the US domestic layer. Two separate rules, one shared set of data.
Separate layers, same customer and transaction data. CARF and DAC8 handle cross-border; 1099-DA and its backup withholding handle US domestic. Check a tax ID once and that result serves the reporting and the withholding decision alike.
Yes. Put CARF and DAC8 and 1099-DA on one data layer and a single onboarding with one tax-ID check is enough. One integration then covers the global reporting, the US reporting, and backup withholding.

Advising a CASP toward CARF and DAC8 readiness? The assessment framework, the common gaps, and how to hand clients a working pipeline, not a slide deck.

Custodial providers are in scope as reporting CASPs. Here's the due-diligence and reporting obligation for a custodian, including the transfer edge cases.

Exchanges have users across dozens of jurisdictions. Here's the CARF and DAC8 obligation for a centralised venue, and why buying beats building it.
Generate an audit-ready report aligned to your jurisdiction. No credit card required.