CARF, DAC8 and 1099-DA for crypto brokers: one compliance stack
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.
The global layer: CARF and DAC8
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.
The US domestic layer: 1099-DA and backup withholding
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.
One data layer for both
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.
One onboarding, both filings
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.
Sukesh Tedla is a serial entrepreneur who has been building in blockchain since 2017. He is the founder and CEO of Kryptos, a crypto financial data infrastructure company helping individual investors, enterprise finance teams and developers across 35+ countries. Earlier, he was a founding team member of the Telos Blockchain Network, which reached a valuation of over $300 million at its peak, where he led liquidity and financial operations. He's also the Chairman of the Swedish Blockchain Association. He began his career in technical and leadership roles at Ericsson and Volvo Cars, and holds a Master's in Telecommunications. His work is driven by one goal: bringing complex technology to the masses and building a more trustworthy digital world.
