IRS Crypto Reporting. A Step-by-Step Compliance Guide

Your filing is only as complete as your setup. Confirm these are in place before your team runs the steps below.

• Entity classification locked. Your legal team needs to determine whether your platform qualifies as a custodial broker, a hosted wallet provider, or a PDAP (a payment processor handling digital assets) under IRC § 6045, the IRS code governing broker reporting. That classification drives every obligation downstream.

• Customer TIN data. Valid Form W-9, the IRS form U.S. persons use to certify their taxpayer ID, on file for every domestic account, and Form W-8 for non-U.S. persons, covering all reportable accounts.

• IRS e-Services access. Your team should be enrolled in the IRS TIN-matching program, a free tool that validates a customer's name against their taxpayer ID in real time before you file.

• Unified data pipeline. If your trading engine, custody layer, and KYC/onboarding system don't feed into a single reporting workflow, the gaps show up in your filings before you catch them. Siloed systems are the most common source of incomplete filings.

• FIRE system credentials. A registered account on the IRS Filing Information Returns Electronically system, the mandatory portal for submitting 1099s digitally.

• Compliance ownership assigned. Pick one person. Give them authority across compliance, engineering, and finance. Three teams sharing a deadline with no single owner is how filings get missed without anyone realizing it until Q4.

• Legal counsel or qualified reporting vendor. This matters most for platforms headquartered outside the U.S. that serve American customers. The reporting obligations apply regardless of where your company is incorporated.

The sequence below follows the IRS enforcement logic. Each item builds on the previous one, so gaps in earlier stages compound into larger exposure later.

Before building any reporting infrastructure, determine whether your platform qualifies as a broker under IRC § 6045, the IRS code governing broker reporting for digital assets. The IRS defines a broker as any person who regularly executes digital asset sales on behalf of customers in exchange for a fee.

Custodial exchanges, digital asset kiosks that let customers convert assets to cash, and Processors of Digital Asset Payments (PDAPs) that regularly settle transactions all meet that definition.

Custodial wallet providers that only hold assets and non-custodial protocols don't, a distinction the IRS confirmed in its October 2025 FAQ update.

The Taxpayer Identification Number (TIN) your customers provide is what ties every transaction to a reportable person. Its quality determines your backup withholding exposure in 2027.

The process has three layers:

1. Collect onboarding. Request Form W-9 from all U.S. persons and Form W-8 from non-U.S. persons before the account is activated. Retroactive collection at year-end is operationally expensive and legally weaker.
2. Submit to IRS TIN Matching. Run every name/TIN combination through the IRS e-Services TIN Matching Program and log the response date and result. Under Notice 2025-33, brokers who receive a confirmed match are relieved from backup withholding obligations on 2027 transactions for those accounts.
3. Document outreach for non-matches. For accounts where the TIN doesn't match, initiate a documented remediation workflow with at least two contact attempts. Log every touchpoint with timestamps.

Cost-basis reporting, mandatory for covered assets acquired on your platform on or after January 1, 2026, requires three data sources synchronized in real time.

• Trading engine. Disposition date, asset identifier, and gross proceeds per transaction.

• Custody layer. Acquisition date and original cost basis for covered assets.

• KYC/onboarding system. Customer TIN, name, address, and account classification.

A platform that can produce gross proceeds but can't match them to a validated TIN or a confirmed acquisition date will generate incomplete filings. Those carry the same penalty exposure as missing filings entirely.

Get that pipeline built before Q2 2026 ends. Teams that leave this for Q4 are essentially doing open-heart surgery while the patient is running.

The withholding timeline has three phases, and IRS Notice 2025-33 moved the goalposts on when each kicks in.

In digital asset-to-digital asset trades, backup withholding is calculated at 24% of the liquidation amount, not 24% of the asset's market value at transaction time. Compliance teams building withholding into payment engines need to account for that difference.

Despite the relief for 2025 and 2026, building that architecture now avoids a much harder retrofit under live enforcement conditions.

Two deadlines govern tax year 2026 activity, both falling in early 2027.

• January 31, 2027. Submit information returns electronically to the IRS.

• February 17, 2027. Send payee statements to your customers.

The IRS FIRE system, the current portal for submitting 1099s digitally, will shut down at the end of 2026. Starting with the 2027 filing season, the IRIS system (Information Returns Intake System) will be the only accepted intake channel.

Apply for your IRIS Transmitter Control Code now. Don't wait until Q4 2026.

For a complete breakdown of what fields to populate, covered vs. non-covered asset classification, and Stablecoin and NFT treatment, see our complete guide on Form 1099-DA: What Brokers Must Report to the IRS in 2026.

Good-faith penalty relief under Notice 2024-56 and Notice 2025-33 is performance-based. The IRS doesn't accept intent; it requires evidence. Your compliance log should include:

• Dated records of W-9/W-8 collection by account.

• TIN Matching submission logs with response codes and dates.

• Customer outreach records for non-matching TINs, with timestamps.

• Internal QA and testing milestones for your reporting pipeline.

• Filing and furnishing confirmation receipts.

Build this log as you go. Retroactive reconstruction of compliance documentation won't satisfy the standard and won't hold up under audit.

These are the execution gaps that surface most often in platforms that know the rules but misjudge the workload required to meet them.

• Waiting until year-end to collect TINs. Retroactive outreach is slow, incomplete, and harder to document. By the time a mismatch surfaces in Q4, the remediation window is already narrow.

• Treating gross proceeds and cost basis as the same problem. Gross proceeds reporting went live for tax year 2025. Cost-basis reporting starts with assets acquired on or after January 1, 2026. Platforms that conflate the two timelines build pipelines that are half-ready.

• Misclassifying your entity. Platforms that hold assets without executing sales, or that operate non-custodially, aren't brokers under IRC § 6045. Filing unnecessarily creates obligations that don't exist. Missing required filings creates unlimited penalty exposure.

• Applying a single reporting logic to all asset types. Wrapped tokens, stablecoins, and NFTs each carry specific rules under Notice 2024-57. One logic across all asset types produces over-reporting on some and under-reporting on others simultaneously.

• Ignoring the FIRE-to-IRIS migration. The IRS filing portal shuts down at the end of 2026. Platforms that haven't migrated to IRIS by then will have no accepted intake channel for tax year 2026 returns. Apply for your IRIS Transmitter Control Code now.

Execution is where most compliance programs lose time and budget. These practices reduce the work without creating new gaps.

• Automate TIN validation at account creation. Hook IRS TIN Matching into your onboarding flow so invalid TINs get flagged before the account goes live. Catching a mismatch at day one costs almost nothing. Catching it in December costs real money.

• Run quarterly reconciliation between your trading engine and custody layer. Don't save this for year-end. By the time Q4 arrives under filing pressure, a data gap between systems isn't a quick fix — it's a multi-week remediation project with a hard deadline already in view.

• Put one person in charge of IRIS enrollment before Q3 2026. Someone with a name and a calendar, not a shared inbox. It needs a timeline, sign-off from engineering and compliance, and enough time before summer. Miss this, and your platform has no filing channel for tax year 2026 returns.

• Look at the infrastructure that already has KYC and compliance built in. Platforms like Mercuryo come with identity verification, KYC pipelines, and regulatory integrations already running. For teams weighing a full internal build against time, that's worth pricing out.

IRS audits on digital asset reporting tend to start with the easiest cases. Platforms with no documentation trail, unmatched TINs, and no good-faith record are the first ones flagged. Build your compliance posture around what an auditor looks for, starting with the fundamentals this guide covers.