How Form 1099-DA, cost-basis reporting and the Cryptoasset Reporting Framework are changing the practical meaning of crypto compliance in 2026.

Research current to September 17, 2026. The tax examples and rules below are jurisdiction-specific, principally covering U.S. federal taxation and UK reporting obligations.

An exchange can report exactly how much crypto a customer sold and still be unable to tell that customer how much tax they owe.

That gap is becoming much more visible in 2026. U.S. investors are encountering the first reporting cycle for Form 1099-DA, covering transactions that occurred in 2025. UK cryptoasset service providers are collecting information for their first reports under the Cryptoasset Reporting Framework, due in 2027. The administrative machinery is moving closer to individual transactions, including transactions whose acquisition history sits somewhere else.

Securities classification remains consequential. It affects issuance, trading venues and intermediary obligations. Tax administration asks a separate set of questions that persists even when a token’s regulatory label changes. Who owned the asset? What did they pay? Did a transfer change beneficial ownership? Was a receipt income, and did a subsequent disposal create another gain or loss?

For users, these questions increasingly determine how much of a displayed return they can keep. For exchanges and wallet businesses, they determine what information the product must retain long after a trade has settled.

The IRS’s current digital-assets guidance separates two reporting milestones. Covered brokers must report gross proceeds from relevant transactions effected on or after January 1, 2025. Basis reporting begins for certain transactions effected on or after January 1, 2026. The first milestone produces statements in 2026 for the preceding calendar year. The second expands the information available for qualifying transactions, without making every historical holding fully documented overnight. [1]

The distinction between a transaction year and a filing year matters. A headline saying “new crypto reporting in 2026” may describe a form received this year, a trade executed this year, or information that will be filed next year. Those are different deadlines for different people.

Nor does a new information return establish a new tax on previously untaxed gains. The IRS already treats digital assets as property for federal income-tax purposes. Its updated transaction FAQs expressly include cryptocurrencies, stablecoins and NFTs in the discussion of digital assets. Existing rules about income, basis and dispositions do much of the substantive work. [2]

What changes is the reporting system around those rules. More of the information used in a taxpayer’s calculation can arrive independently at the tax authority.

U.S. broker gross-proceeds reporting

Relevant period: Relevant transactions from January 1, 2025

Practical consequence: The first 1099-DA reporting cycle occurs in 2026

U.S. basis reporting phase-in

Relevant period: Certain transactions from January 1, 2026

Practical consequence: More qualifying sales carry basis information, but gaps remain

UK CARF data collection

Relevant period: January 1 to December 31, 2026

Practical consequence: Providers need information during the year being reported

First UK CARF reports

Relevant period: January 1 to May 31, 2027

Practical consequence: Providers report the preceding calendar year’s data

These dates describe the regimes cited here. They should not be copied into a global calendar without checking the taxpayer’s residence and the provider’s applicable rules.

A sales figure answers how much consideration a disposal generated. Profit also depends on what the disposed asset cost, which units were disposed of, and the treatment of transaction costs.

That is why reading a gross-proceeds figure as taxable income can produce a serious error. Repeated purchases and sales can create a large cumulative proceeds number while producing a comparatively small net economic return. A taxpayer may also have losses, income receipts and different holding periods that require separate treatment.

The problem becomes harder when assets move between providers. The selling exchange may see the asset arriving and later leaving. The purchase price could be recorded at an earlier exchange, in an old wallet export, or in records held only by the customer.

The IRS addresses this directly in its broker-reporting FAQs. A custodial broker may use reasonably reliable customer-provided acquisition information to identify the order in which transferred-in units are sold. However, the FAQs say the broker may not use that customer-provided information to report the transferred-in assets’ basis on Form 1099-DA. [3]

That is an unusually useful detail. Information can be good enough for one reporting purpose and still be unusable for another. A missing basis field therefore requires investigation. It does not automatically establish that the investor acquired the asset for nothing.

A tax-software import cannot resolve this simply by assigning a price to every incoming transaction. An incoming asset might be a purchase, a reward or a movement of an existing holding. Each interpretation creates a different history.

The IRS distinguishes moving assets between wallets or accounts a person owns from disposing of those assets. Its digital-assets page notes that a transfer between a taxpayer’s own wallets, by itself, does not require a “Yes” answer to the digital-asset question. Paying a transaction fee with digital assets changes that analysis because the fee payment can itself be a digital-asset transaction. [1]

This makes wallet ownership important evidence. A blockchain explorer can establish that an address sent tokens to another address. It usually cannot establish, on its own, whether the same person controlled both, whether the transfer settled a purchase, or whether a custodial account credited an internal ledger.

Useful records connect the onchain event to its purpose. The transaction hash, sending account, receiving account, quantity and timestamp need to sit alongside the acquisition history. Exchange exports should be preserved in their original form, with any later reconciliation recorded separately.

Cross-chain activity adds another complication. The existence of a bridge transaction does not settle its tax characterization. A bridge may involve locking, burning, minting or receiving a different claim. The taxpayer needs to understand what legally and economically happened, rather than letting a portfolio tracker’s label decide the answer.

For U.S. taxpayers, the IRS’s current guidance also describes wallet-by-wallet or account-by-account basis identification and transitional guidance for allocating previously unattached basis as of January 1, 2025. Its FAQs explain the conditions around that transition. [1][2]

The operational consequence is straightforward. Reconstructing a single global pile of tokens from memory becomes less reliable as the reporting rules become more account-specific.

The U.S. property framework makes an exchange of one digital asset for another relevant even if no money reaches a bank account. The IRS lists exchanges for another digital asset, and payments for goods or services, among the transactions users need to consider. [1]

This is where the familiar instruction to “pay tax when you cash out” becomes inadequate. Moving from a volatile token into a stablecoin can crystallize a gain or loss on the volatile asset. Keeping the proceeds on an exchange does not reverse that disposal.

A stablecoin can then have its own acquisition and disposal records. A token designed to track one dollar may produce very little price movement, but that does not remove it from the property framework. Fees, execution prices and the taxpayer’s relevant currency can still matter. U.S. calculations should not be transplanted into another jurisdiction without checking that jurisdiction’s rules.

The IRS permits optional aggregate reporting for certain stablecoin and NFT sales, subject to the applicable conditions and thresholds. It also identifies a separate threshold for certain digital-asset payment processors. [1]

These are reporting provisions. A threshold determining whether or how an intermediary reports a transaction is not automatically an exemption from the customer’s substantive tax liability. Treating the two as interchangeable can leave a taxpayer with an incomplete return even when every form received from a provider looks correct.

This distinction becomes more important as stablecoins move into routine payments. A consumer sees a simple checkout. The tax record may need to preserve both the purchase and the asset disposition used to fund it.

The IRS includes staking, mining and other digital-asset income in its reporting guidance, and links to Revenue Ruling 2023-14 on staking income. The taxpayer has to establish the applicable receipt and valuation rules before calculating the consequences of a later sale. [1]

Receiving a reward and disposing of that reward are separate events. A later fall in market value does not, by itself, erase the earlier receipt. Equally, taxing a later disposal requires accounting for the asset’s basis, so the same value is not simply treated as an entirely new gain.

The practical difficulty is often evidence. A rewards dashboard may show a cumulative token quantity while omitting the information necessary to establish the timing and value of individual receipts. Assets can also be subject to restrictions, platform insolvency or arrangements that alter when the taxpayer has the relevant rights. These facts deserve specific analysis.

The IRS’s general digital-assets page identifies special guidance on frozen rewards associated with bankrupt platforms. That is a reminder to examine the actual arrangement before applying a one-line “all staking is taxed this way” rule.

An advertised staking yield therefore tells only part of the investor’s story. The spendable outcome depends on receipt timing, token prices, expenses, later disposals and the taxpayer’s circumstances. Comparing yield percentages without those variables can produce a misleading ranking.

Some of the most consequential language in the IRS guidance concerns what brokers temporarily do not have to report.

Notice 2024-57 identifies specified transactions for which broker reporting is deferred pending further guidance. The IRS summary lists wrapping and unwrapping, liquidity-provider transactions, staking transactions, certain lending and short-sale transactions, and notional principal contracts. It also states that the exception does not apply to rewards or other compensation earned by participants in those transactions. [1]

That is narrower than a declaration that every activity in those categories is tax-free. Broker reporting and substantive tax treatment are separate questions. A transaction’s characterization may remain fact-sensitive even while an intermediary benefits from a reporting exception.

The current IRS summary of the custodial-broker regulations also says those regulations do not include reporting requirements for decentralized or non-custodial brokers that do not take possession of the assets being sold or exchanged. This describes the scope of those regulations, rather than a blanket exemption for every business or user that calls itself DeFi.

For product teams, labels offer limited protection against ambiguity. A useful transaction export should show what the protocol actually did, including assets surrendered, claims received and rewards credited. It should not silently convert an uncertain legal characterization into an apparently definitive tax category.

HMRC’s guidance provides a second concrete view of the 2026 transition.

UK-based reporting cryptoasset service providers must collect user and transaction information under CARF. The provider definition can include businesses that transact on users’ behalf or provide a means for users to transact, including exchanges, brokers and dealers. HMRC sets out separate nexus rules for determining where a provider must report when it has connections to more than one country. [4]

HMRC says providers need to collect details of all users, but report information about users who are tax resident in the UK or another country signed up to CARF rules. The reports contain user details and a summary of transactions. [5]

The first reporting window runs from January 1 through May 31, 2027, covering January 1 through December 31, 2026. Subsequent reports are due by May 31 for the preceding calendar year. The guidance also requires providers to register and notify users by January 31, 2027. [4][5]

A provider consequently needs to establish reportable information before the filing window opens. Asking users about tax residence and obtaining the associated identifying information becomes part of operating the service.

CARF’s function should be understood precisely. It supplies a framework for reporting information. It does not impose one worldwide crypto capital-gains rate, make every jurisdiction’s taxable events identical, or determine a user’s final liability from transaction totals alone.

The UK guidance is also explicit about the format. Reports are submitted as XML, with technical schema requirements. This may sound remote from the crypto policy debate, but it is where broad commitments turn into implementation work. Someone must map identities and transactions into a valid report, correct exceptions, and retain enough evidence to explain the result.

A platform can complete a trade in seconds while creating an accounting problem that lasts for years.

That gives exchanges and wallet providers a practical competitive opportunity. Export quality, stable transaction identifiers, transparent fee records and correction procedures can materially affect how usable a product is for customers with complex histories. A visually attractive profit-and-loss screen is less useful if the underlying figures cannot be reconciled.

There are limits to what the platform can promise. It may lack the customer’s activity elsewhere or the facts required to establish residence. It may be permitted to use acquisition information for one purpose while being prohibited from including it in a particular reporting field. The IRS transferred-in basis FAQs illustrate precisely that limitation.

Customers therefore need a division of responsibilities that they can understand. Which information is directly observed? Which figure is customer-supplied? What has been estimated, and what remains unresolved?

For active users, the most valuable preparation is to reconcile records while accounts and transaction histories are still accessible. Preserve original exports, identify wallets under common ownership, and investigate unmatched transfers. Separate reward receipts from later disposals. Where the legal treatment is uncertain, retain the protocol documentation and record the question instead of letting software invent certainty.

The next difficult conversation with a crypto platform may concern a missing purchase date or an unexplained proceeds figure. The quality of its answer will matter long after the debate over the token’s label has moved on.

No. Securities or commodities classification and tax treatment answer different legal questions. Under the U.S. framework discussed here, taxable income or gains can arise from digital-asset transactions regardless of a claim that a token is not a security.

No. It reports specified transaction information. Gross proceeds do not equal profit, and basis information may be missing or limited. The taxpayer must reconcile the form with acquisition records and the rest of their applicable tax position.

The swap can be a taxable disposition of the crypto exchanged. Whether it produces a gain, a loss or no gain depends on basis, proceeds and applicable rules. Withdrawal to a bank is not the only relevant event.

A simple movement of the same asset between wallets under the same ownership generally does not create a sale by itself. Fees paid in digital assets can have separate consequences. Bridging or receiving a different token or legal claim needs its own analysis.

HMRC requires the first reports between January 1 and May 31, 2027, covering the 2026 calendar year. Providers collect the underlying information during that reporting year. These are provider reporting deadlines, not a replacement for an individual’s tax-return deadlines.

No. An information-reporting exception does not automatically change the underlying tax treatment. The IRS expressly distinguishes certain transaction-reporting exceptions from rewards and compensation associated with those transactions.

1. IRS, Digital assets, including the broker-reporting phase-in, transitional relief and specified reporting exceptions. Page reviewed September 17, 2026.

2. IRS, Frequently asked questions on digital asset transactions, particularly the property framework, gain calculations and basis identification.

3. IRS, Frequently asked questions about broker reporting, particularly questions 3 and 7 on transferred-in acquisition information.

4. HMRC, Check if you need to report cryptoasset data to HMRC, updated January 1, 2026.

5. HMRC, Reporting cryptoasset user and transaction data, updated June 3, 2026.