Cryptocurrency tax preparation has moved from a niche specialty to a baseline competency. In the 2026 filing season, tax preparers are receiving Form 1099-DA from clients for the first time, facing IRS matching on digital asset transactions across thousands of returns, and fielding questions about staking rewards, NFT sales, DeFi activity, and wallet transfers that require more than a working knowledge of Schedule D. If you are handling crypto clients without a documented workflow, this is the season that gap will cost you.
This guide is written for tax preparers building or refining their crypto client workflow for the 2026 filing season. It covers the complete arc from client intake through Form 8949 preparation, including the new Form 1099-DA and its current reporting limitations, cost basis reconstruction methods, staking and mining income treatment, NFT transactions, DeFi considerations, aggregator tools, and the engagement-letter terms that protect your practice when client data is incomplete. Every regulated claim in this guide is flagged for preparer verification at IRS.gov before it is applied to a client return.
All regulatory figures, IRS positions, and guidance citations in this guide should be verified at IRS.gov before relying on them in client engagements. Tax law in the digital asset space is actively evolving and is subject to future IRS and Treasury guidance. This guide is informational and does not constitute legal or tax advice.
Why Crypto Tax Prep Is Now a Core Preparer Competency
The infrastructure shift that makes crypto tax preparation mandatory for general-practice preparers is Form 1099-DA. Beginning with tax year 2025, digital asset brokers (including centralized cryptocurrency exchanges) are required to file Form 1099-DA reporting gross proceeds from covered digital asset sales. Those forms are hitting client mailboxes, and they are being matched by IRS systems the same way Form 1099-B has been matched against stock transaction reporting for decades. A client who sold cryptocurrency on a major exchange in 2025 will almost certainly have a 1099-DA that the IRS already has a copy of. Preparing a return without accounting for those proceeds is the kind of discrepancy that generates CP2000 notices.
The mandatory digital asset question on Form 1040 Schedule 1 reinforces this. Every client must answer whether they received, sold, exchanged, or otherwise disposed of a digital asset during the year. The question is binary and signed under penalties of perjury. A preparer who checks "No" without asking the client specifically about cryptocurrency, NFTs, staking rewards, and DeFi activity is taking on liability that belongs to the client. Building a structured intake question into your standard process is not optional for the 2026 season.
Volume is the other driver. The IRS has signaled that digital asset compliance is an enforcement priority, and the combination of third-party reporting via Form 1099-DA and expanded broker definition under the Infrastructure Investment and Jobs Act means the matching data available to the IRS is broader and more complete than it has ever been. Preparers who develop a reproducible crypto workflow now are positioned for the full cost basis reporting rollout beginning with tax year 2026, when Box 1g on Form 1099-DA will also carry cost basis, making IRS matching substantially more precise. For a focused breakdown of broker reconciliation, proceeds-only reporting, and the missing cost basis workflow, see our Form 1099-DA digital asset reporting guide for tax preparers.
Digital Asset Taxonomy for Preparers: What Each Asset Type Means for Tax Treatment
Not every digital asset transaction is treated the same way. The tax result depends on what kind of asset it is, how the taxpayer acquired it, how long they held it, and what they did with it. Before you can correctly prepare a crypto return, you need to classify each transaction category your client has. Here is how each asset type maps to its federal tax treatment under current IRS guidance.
Coins and tokens (purchased on an exchange)
Cryptocurrency purchased on a centralized or decentralized exchange is treated as property under IRS Notice 2014-21 (verify current guidance at IRS.gov). Sale or exchange triggers capital gain or loss, long-term if held more than one year, short-term if held one year or less. The cost basis is the purchase price including any transaction fees paid to acquire the asset. Every taxable disposition, including trading one cryptocurrency for another, triggers a gain or loss recognition event.
Staking rewards
Under current IRS guidance (Rev. Rul. 2023-14, verify at IRS.gov), staking rewards are treated as ordinary income in the year received, at fair market value on the date of receipt. The FMV at receipt becomes the taxpayer's cost basis in the reward tokens. This treatment has been contested in litigation (Jarrett v. United States), and the IRS position on proof-of-stake rewards is subject to future guidance. Apply the revenue ruling as the operative standard for now, and flag the uncertainty to clients with material staking income.
Mining income
Cryptocurrency received from mining is ordinary income at fair market value on the date of receipt, regardless of whether the taxpayer mines as a business or as a hobby. Mining conducted as a trade or business generates self-employment income reportable on Schedule C, and the taxpayer can deduct ordinary and necessary business expenses (electricity, equipment depreciation). Hobby mining income is includable in gross income but deductions are limited. The FMV at receipt becomes the basis in the mined coins for purposes of any future sale.
NFTs
Non-fungible tokens require a two-track analysis. A collector who buys and later sells an NFT recognizes capital gain or loss on the sale. An artist or creator who mints and sells an NFT recognizes ordinary income from that sale, because the NFT is inventory or a created work product in the hands of the creator. Long-term capital gains on NFTs held by collectors carry a collectibles rate risk under IRC Section 1(h)(4), which imposes a 28 percent maximum rate on long-term gains from collectibles. Whether a given NFT qualifies as a collectible under current IRS guidance is not fully settled and is subject to future IRS clarification. Verify the current IRS position at IRS.gov before applying the 28 percent rate or advising clients that it does not apply.
DeFi transactions
Decentralized finance transactions (liquidity pool deposits and withdrawals, yield farming, token swaps on decentralized exchanges, lending protocol activity) do not have a single settled tax treatment. Under current IRS guidance, a token swap on a decentralized exchange is treated as an exchange of property and triggers gain or loss recognition the same as a sale. Liquidity pool deposits may or may not be treated as taxable exchanges depending on whether the taxpayer receives a new token in return (as is common with LP tokens). This area is subject to future IRS clarification. Frame all DeFi positions as subject to evolving guidance, document the approach taken, and ensure the client understands the uncertainty.
Airdrops
Cryptocurrency received in an airdrop is treated as ordinary income at fair market value on the date the taxpayer receives it and has dominion and control over it, per IRS Revenue Ruling 2023-14 and related guidance (verify at IRS.gov). If the taxpayer did not have the ability to access or transfer the airdropped tokens, the income recognition may be deferred to the date access was established. The FMV at the time of inclusion in income becomes the taxpayer's basis in the airdropped tokens for subsequent sale calculations.
Crypto Client Intake Checklist for the 2026 Filing Season
A complete crypto engagement starts with a complete data intake. The single most common source of errors in crypto return preparation is missing transaction data, not calculation errors. If your intake process does not surface every wallet and every exchange your client used, the return you prepare will be wrong before you begin. Use this checklist as the minimum data requirement before you accept a crypto engagement.
- Form 1099-DA received: Request all Forms 1099-DA the client received for the tax year. Verify the exchange or broker name, the reporting period, and whether Box 1g (cost basis) is populated. For TY2025 returns, Box 1g will be blank; basis must be reconstructed independently. Beginning with TY2026, brokers are required to report cost basis. Keep the original 1099-DA in the file; IRS matching runs against those figures.
- Exchange CSV transaction history: Require a full CSV export from every centralized exchange the client used during the tax year. "Full" means every transaction: purchases, sales, trades, transfers in, transfers out, staking rewards credited, and any other activity. A partial export covering only the client's perception of taxable events is not sufficient. Each exchange has its own export format; know in advance which formats your aggregator tool accepts.
- Wallet transaction history: For every self-custody wallet (hardware wallet, software wallet, or browser extension wallet) the client used, require a complete transaction history. Public blockchain explorers (Etherscan for Ethereum-based assets, blockchain.info for Bitcoin, and equivalents for other chains) can pull transaction history from the wallet address. The client needs to provide every wallet address they controlled during the year.
- List of all wallets and exchanges: Require the client to provide a written list of every exchange account and wallet they held during the year, including accounts that were closed, dormant, or only used for transfers. Missing a single wallet that holds unreported trades is the basis for a CP2000 or, in egregious cases, a fraud referral. The completeness of this list is the client's responsibility; document that you requested it.
- Prior-year cost basis records: For clients who held cryptocurrency prior to the tax year being prepared, prior-year purchase records or prior-year return Form 8949 detail are necessary to establish the correct basis. If the client has been filing correctly in prior years, the basis carried on those returns is the starting point. If prior years were not reported or were reported incorrectly, document the limitation in your engagement file and consider whether an amended return (Form 1040-X crypto corrections guide) is warranted.
- Staking and DeFi documentation: Request the client's records of staking platforms used, any DeFi protocol interactions (liquidity pools, yield farms, lending positions), and any governance token rewards received. These transactions often do not appear on standard exchange exports and require separate documentation from the protocol itself or from blockchain analysis.
Form 1099-DA Explained: What It Reports, What It Does Not, and Box Selection Logic
Form 1099-DA is the new information return for digital asset transactions, first required for tax year 2025. Understanding exactly what the form reports, and crucially what it does not report for TY2025, is essential before you can use it correctly in the preparation workflow.
TY2025: FORM 1099-DA BOX 1g (COST BASIS) IS BLANK
For returns filed for tax year 2025, brokers are required to report gross proceeds on Form 1099-DA but are NOT yet required to report cost basis. Box 1g will be blank on TY2025 Forms 1099-DA. Mandatory cost basis reporting begins with tax year 2026. This means every TY2025 return with a Form 1099-DA still requires independent cost basis reconstruction by the preparer. Do not assume a blank Box 1g means zero basis. Verify the current IRS Form 1099-DA implementation schedule at IRS.gov.
What Form 1099-DA reports for TY2025
Form 1099-DA reports gross proceeds from covered digital asset sales made through a broker. The form identifies the asset sold, the date of sale, and the gross proceeds amount. It does not currently report the date of acquisition, the cost basis, or the holding period. Those fields either remain blank or may reflect estimates the broker is not yet required to provide. The preparer must establish basis and holding period independently using the client's acquisition records and aggregator tool output.
The definition of "covered" transactions under Form 1099-DA follows the broker reporting rules. Centralized exchanges that act as brokers are covered. Transactions on decentralized protocols that do not involve a party acting as a broker in the traditional sense may not generate a Form 1099-DA, but they still generate taxable events that must be reported. The absence of a 1099-DA for a transaction is not evidence the transaction is not taxable.
Box A, B, and C checkbox selection on Form 8949
When you transfer Form 1099-DA data to Form 8949, the checkbox selection (Box A, B, or C for short-term; Box D, E, or F for long-term) depends on whether the transaction was reported to the IRS by a broker and whether cost basis was also reported:
- Box A (or D): Transactions reported to the IRS on Form 1099-DA with both proceeds AND cost basis reported. For TY2025, this box will not apply to most digital asset transactions because Box 1g is blank. If a broker did report basis, Box A or D applies.
- Box B (or E): Transactions reported to the IRS on Form 1099-DA but WITHOUT cost basis reported to the IRS. This is the correct box for most TY2025 Form 1099-DA transactions, where gross proceeds appear but Box 1g is blank.
- Box C (or F): Transactions NOT reported to the IRS on a 1099. This includes wallet-based transactions, DeFi transactions, peer-to-peer sales, and any disposition that did not flow through a reporting broker. Most self-custody wallet transactions and decentralized exchange trades will land in Box C or F.
Verify the current Form 8949 instructions at IRS.gov for the precise checkbox definitions and any updates to the digital asset reporting rules before preparing returns. The infrastructure for digital asset reporting is changing each filing season.
Form 8949 and Schedule D Workflow for High-Volume Crypto Clients
The mechanics of Form 8949 are the same for digital assets as for any other capital asset: each disposition gets a line, with date acquired, date sold, gross proceeds, cost basis, any adjustment code, and the resulting gain or loss. The challenge with crypto clients is volume. A client who actively traded cryptocurrency across multiple exchanges in 2025 may have hundreds or thousands of individual transactions. Preparing each on a separate line is impractical; the tax software import workflow is the operational answer.
Structuring high-volume transaction sets
For clients with high transaction volume, the practical workflow is to use a crypto aggregator tool to generate a Form 8949-formatted CSV export, then import that CSV into your tax software. The aggregator applies the correct cost basis method (FIFO by default, or specific identification if the taxpayer has made a valid election), classifies each transaction as short-term or long-term, and flags any transactions it could not reconcile due to missing data. The import produces the Form 8949 detail with individual transactions grouped by the applicable checkbox (Box B for reported-without-basis and Box C or F for unreported).
When the transaction count is very high and individual-line reporting would produce an unwieldy form, the IRS permits summary reporting on Form 8949 (a single line per grouping, showing the total proceeds and total basis for that grouping) with the full transaction detail attached as a statement. Check the current Form 8949 instructions at IRS.gov for the summary reporting method and attachment requirements before using this approach, as the rules for digital assets specifically are subject to update.
Short-term vs. long-term classification
Every disposition requires a holding period determination. Assets held one year or less at the time of disposition are short-term capital gains or losses, taxed at ordinary income rates. Assets held more than one year are long-term, eligible for preferential rates. The holding period begins on the date of acquisition and ends on the date of disposition. A crypto-to-crypto trade (swapping Bitcoin for Ethereum, for example) is a disposition of the Bitcoin and a new acquisition of the Ethereum; the holding period clock on the Ethereum starts on the trade date, not on the date the Bitcoin was originally purchased. Your aggregator output should classify transactions by holding period automatically, but review it for misclassifications, particularly for early-year transactions where the holding period spans the prior tax year.
Cost Basis Reconstruction: FIFO, Specific Identification, and Wallet-to-Wallet Transfers
For TY2025 returns, where Form 1099-DA does not carry cost basis, the preparer must reconstruct basis from the client's acquisition records. The method used affects the gain or loss on every sale and must be applied consistently. The IRS allows two primary cost basis methods for digital assets.
FIFO (First-In, First-Out): the default
Under FIFO, when the taxpayer sells cryptocurrency, the first units acquired are treated as the first units sold. FIFO is the default method for taxpayers who have not made a specific identification election. In a rising-price environment, FIFO tends to produce the largest taxable gain, because the oldest (and therefore lowest-basis) lots are sold first. Clients who accumulated cryptocurrency over multiple years at rising prices will generally have lower gains under specific identification than under FIFO. Most crypto aggregator tools apply FIFO by default and can switch to other methods if directed.
Specific identification: the election and its requirements
Specific identification allows the taxpayer to designate which specific lot (identified by acquisition date and purchase price) is being sold at the time of each transaction. Specific identification typically produces lower gains (or larger losses) by allowing the taxpayer to match high-basis lots to each sale. To be valid, the election must be made at the time of the sale and the records must be sufficient to identify the specific lot. For digital assets, this means the aggregator or exchange record must capture the lot designation before the sale executes, not reconstructed after the fact. If the records do not support specific identification at the transaction level, FIFO applies by default. Verify current IRS requirements for valid specific identification elections for digital assets at IRS.gov.
Wallet-to-wallet transfers: not a taxable event
A transfer of cryptocurrency between two wallets that the same taxpayer owns and controls is not a taxable event. No gain or loss is recognized, and the original cost basis and acquisition date carry over to the receiving wallet. This is one of the most common errors in crypto preparation: a client's aggregator or exchange export shows an outgoing transaction from Exchange A and an incoming transaction on Exchange B, and the preparer (or the aggregator, if wallet ownership is not mapped correctly) records both as taxable events.
Proper treatment requires the preparer to obtain a complete list of all wallets the client controlled and to map transfers between them as non-taxable movements with basis carryover. Aggregator tools handle this correctly only if all wallet addresses are entered and linked to the client's profile. A missing wallet in the aggregator produces an "unmatched" incoming transaction that the tool may classify incorrectly. Review all unmatched transactions in the aggregator output before accepting the Form 8949 export.
Staking and Mining Income: Ordinary Income Treatment and Basis Establishment
The IRS addressed the tax treatment of cryptocurrency staking rewards in Rev. Rul. 2023-14 (verify at IRS.gov). Under that ruling, staking rewards are includable in gross income as ordinary income in the taxable year in which the taxpayer receives them, valued at fair market value on the date of receipt. The ruling applies to taxpayers who participate in proof-of-stake blockchain validation and receive additional cryptocurrency as compensation for that participation.
The ruling has been challenged in litigation. In Jarrett v. United States, taxpayers argued that newly created cryptocurrency tokens should not be treated as income at creation, but rather only upon sale or exchange. The litigation landscape around proof-of-stake staking rewards remains active and the ultimate resolution is not settled. For the 2026 filing season, preparers should apply Rev. Rul. 2023-14 as the operative standard and disclose to clients with material staking income that the position may be affected by ongoing IRS guidance development. Verify the current status of this issue at IRS.gov before advising clients.
The practical preparation workflow: identify each date the client received staking rewards, determine the fair market value of the reward tokens on that date (using exchange price data from the relevant blockchain's major trading pairs), include that amount in gross income as ordinary income, and record the FMV at receipt as the basis in those reward tokens. When the client later sells or exchanges the staking reward tokens, the difference between the sale price and that established basis is a capital gain or loss, short-term or long-term depending on the holding period from the receipt date.
A common error to watch for: a client who included staking rewards in income on a prior-year return but did not establish the correct basis in those reward tokens. When those tokens are sold in the current year, the preparer must verify that the basis was correctly carried forward from the prior-year income inclusion. If the basis was recorded as zero in the prior-year preparation, the current-year sale will show an inflated gain. Check the prior-year return before establishing basis for any tokens the client received as staking rewards.
NFT Tax Treatment: Collectors, Creators, and the Collectibles Rate Risk
Non-fungible tokens require a two-part analysis: first, is the client a collector or a creator? Second, if a collector with long-term holding, does the 28 percent collectibles rate apply? Both questions require fact-specific analysis, and the second has a layer of regulatory uncertainty that preparers must flag explicitly.
NFT sales by collectors
A collector who buys an NFT and later sells it recognizes capital gain or loss on the sale. The basis is the purchase price (in dollars, or the fair market value in dollars of the cryptocurrency paid at the time of purchase). The gain is short-term if the holding period is one year or less, long-term if more than one year. NFTs purchased with cryptocurrency involve two taxable events: a disposition of the cryptocurrency used to purchase the NFT (triggering capital gain or loss on the crypto) and an acquisition of the NFT at the dollar-equivalent cost.
NFT sales by creators
An artist or creator who mints an NFT and sells it is recognizing ordinary income from the sale of a created work product. The NFT is inventory in the creator's hands, not a capital asset, and the proceeds are taxable as ordinary income. If the creator conducts NFT creation and sales as a trade or business, the income is self-employment income subject to self-employment tax, reportable on Schedule C. Creators who also receive royalties from secondary sales on smart-contract-enabled marketplaces are receiving additional ordinary income each time a royalty payment is triggered. Verify the current IRS treatment of NFT creator income, which may be subject to future IRS guidance, at IRS.gov.
The 28 percent collectibles rate risk
Under IRC Section 1(h)(4), long-term capital gains on the sale of collectibles are taxed at a maximum rate of 28 percent, rather than the standard preferential long-term capital gains rates (0, 15, or 20 percent depending on the taxpayer's income). Whether NFTs qualify as collectibles under current IRS guidance is not fully settled and is subject to future IRS clarification. The IRS has indicated interest in the question but has not issued definitive guidance that applies uniformly to all NFT types. Preparers handling clients with long-term NFT gains should apply a conservative approach, flag the rate risk in their workpapers, and advise clients that the 28 percent rate may apply pending further IRS guidance. Do not advise clients with certainty in either direction on this question without verifying the current IRS position at IRS.gov.
Crypto Tax Aggregator Tools: Evaluation Criteria and Engagement Requirements
For any client with more than a handful of cryptocurrency transactions across multiple exchanges or wallets, a crypto tax aggregator is a practical necessity. These tools pull transaction data from exchange APIs and wallet addresses, apply cost basis calculations, classify transactions by type (sale, reward, transfer, swap), and produce Form 8949-formatted export files that your tax software can import. The tools commonly used in the professional preparer market include CoinTracker, Koinly, CoinLedger, and TokenTax. Each has different exchange integration coverage, pricing structures, and output formats.
What to evaluate when a client brings aggregator output
Do not accept aggregator output as final without a review pass. The key things to check: (1) are all the client's wallets and exchange accounts connected, or are there gaps? (2) how has the tool classified wallet-to-wallet transfers -- if they show up as taxable events, the wallet ownership mapping is incomplete; (3) are there unmatched transactions flagged by the tool, meaning it received cryptocurrency from a source it could not trace to a prior acquisition? Unmatched incoming transactions may indicate a missing wallet or exchange account; (4) is the cost basis method applied consistent with the client's election and prior-year treatment? Switching from FIFO to specific identification mid-history distorts the gain/loss calculation.
The aggregator review is not a rubber stamp. It is the preparer's professional judgment applied to tool output. If the aggregator output contains obvious errors (a wallet-to-wallet transfer shown as a taxable sale, a staking reward not classified as income, a basis figure that does not match the client's purchase records), those errors carry through to the Form 8949 unless you catch and correct them. The preparer, not the tool, is responsible for the accuracy of the return.
When to require aggregator use before the engagement
For clients with high transaction volume (a common threshold is 100 or more transactions per year), build aggregator completion as a prerequisite in your engagement letter. Require the client to run their full transaction history through the tool, connect all exchanges and wallets, and deliver you the tool's reconciled output before the engagement begins. This limits your liability for errors caused by the client providing incomplete raw data, and it establishes a clear data-delivery standard. Document in your engagement letter that the accuracy of the aggregator output depends on the completeness of the data the client provides to the tool.
Common Errors and Audit Triggers in Crypto Return Preparation
The IRS matching program for digital assets is now active and Form 1099-DA proceeds figures are in the system. The errors that generate IRS notices in crypto returns are largely predictable. Here are the ones that show up most frequently and the correction for each.
Wallet-to-wallet transfers recorded as taxable proceeds
A transfer of cryptocurrency from one wallet to another that the same taxpayer controls is not a taxable event. When a client's aggregator shows an outgoing transaction from one wallet and has no corresponding entry showing where the assets went, the tool may classify the outgoing amount as a sale. Similarly, untracked incoming transfers may be classified as zero-basis acquisitions (which inflates future gains). The fix is a complete wallet inventory before running the aggregator. Every wallet the client controlled during the year must be mapped, and transfers between them must be linked to avoid phantom proceeds and phantom basis errors.
Leaving Box 1g blank or entering zero on Form 8949 without adjustment codes
For transactions reported on Form 1099-DA without cost basis (Box 1g blank), the correct treatment is to use the reconstructed cost basis in Column (e) of Form 8949 and enter the appropriate adjustment code in Column (f) if the basis differs from what was reported. Entering zero in Column (e) when the taxpayer actually has a non-zero basis produces a massively inflated gain and is incorrect. The Form 8949 instructions specify the adjustment codes to use when the basis differs from the brokerage's reporting. Verify the current instructions at IRS.gov.
Basis not reduced after staking income was already included in a prior year
A client who received staking rewards, included them in income on a prior-year return at fair market value, and later sold those tokens has a basis equal to the FMV at the time of income inclusion. If the prior-year return correctly included the income but the basis was recorded as zero (a common error), the current-year sale will produce a double-counted gain. Before reporting the current-year sale, trace back to the prior-year return and confirm that the basis in the staking reward tokens reflects the income that was already reported. If it does not, an amended return for the prior year (or a corrected basis entry with explanation in the current-year workpapers) may be needed.
Omitting the Schedule 1 digital asset question
Form 1040 Schedule 1 includes a mandatory question asking whether the taxpayer received, sold, exchanged, or otherwise disposed of any digital assets during the year. Checking "No" when any such activity occurred is a misrepresentation signed under penalties of perjury. Even clients who only received cryptocurrency as a gift, received staking rewards, or moved assets between wallets may need to answer "Yes." Walk every client through this question at intake, and document that you asked it specifically.
Misclassifying cryptocurrency received as payment for services
Cryptocurrency received as compensation for services rendered (freelance payments, contractor payments, salary in crypto) is ordinary income at fair market value on the receipt date, not a capital asset at the time of receipt. The capital gain or loss analysis begins only when the client later disposes of the cryptocurrency. Treating the initial receipt as a non-taxable or capital-gain event is an error. If the client is a business receiving crypto as payment, the treatment flows through Schedule C, not Schedule D.
Adding Crypto Prep to Your Engagement Letter: Scope, Fees, and Data Requirements
A standard tax preparation engagement letter is not sufficient to cover a client with cryptocurrency activity. The unique data requirements, the complexity of cost basis reconstruction, and the scope limitations that apply when client records are incomplete all need to be addressed explicitly. Adding a crypto-specific addendum to your engagement letter, or building crypto-specific language into your standard agreement, protects both you and the client.
Scope limitations to include
Your engagement letter should state clearly that the accuracy of the digital asset reporting is limited to the transaction data the client provides and that you are not responsible for transactions you could not identify because the client did not disclose them. Specifically address the following scope boundaries: (1) you are not independently verifying the completeness of the client's wallet and exchange list -- the client is responsible for providing a complete accounting of all digital asset activity; (2) the aggregator tool output is only as accurate as the data the client loaded into it; (3) cost basis reconstruction for prior-year acquisition records is performed using the records the client provides and may not reflect transactions that predate the records available; (4) DeFi, staking, and NFT positions may be subject to IRS guidance that is not yet settled, and the treatment applied in the return reflects current guidance as of the preparation date.
Fee structure for crypto engagements
Crypto tax preparation is materially more time-intensive than a standard return. A client with hundreds of transactions, multiple exchanges, staking rewards, and a prior-year cost basis reconstruction job requires significantly more preparer time than a W-2 client. Structure your fee accordingly. Common approaches include: a flat add-on fee per exchange or wallet connected, a tiered flat fee based on transaction count ranges (under 50, 50-200, 200-1000, over 1000), or an hourly rate for cost basis reconstruction work billed separately from the return preparation fee. Be explicit in the engagement letter that additional fees apply if the client's transaction records require reconstruction, or if the client delivers records after a specified date, requiring rush preparation. An undisclosed fee increase midway through a complex engagement is the leading cause of crypto-related client disputes.
Client data delivery requirements
Specify in the engagement letter exactly what the client must deliver and by what date: all Forms 1099-DA received; complete CSV transaction history exports from each exchange used during the year; the aggregator tool output (if you require the client to run one before the engagement); a written list of all wallets and exchange accounts; and any prior-year Form 8949 detail or acquisition records needed for basis reconstruction. State that the engagement cannot be completed within your standard timeline unless all required crypto records are received by the data delivery deadline. If records arrive late, the return may need to be extended.
Tax Software Workflows for Importing Form 8949 Data: CSV Import and Large Transaction E-File
The practical bottleneck for preparers handling crypto clients is getting hundreds or thousands of Form 8949 transactions into the tax software efficiently and accurately. Manual entry at scale is not a viable workflow. The solution is the CSV import function built into professional tax preparation platforms, including TaxWise, which allows you to import a properly formatted transaction file directly into Form 8949 rather than entering each transaction by hand.
CSV import workflow in TaxWise
TaxWise supports CSV import of capital asset transactions for Form 8949. The correct workflow is: (1) export the Form 8949-formatted CSV from your crypto aggregator tool (confirm the export format matches TaxWise's import template); (2) review the CSV for obvious errors before importing (zero-basis transactions, wallet-to-wallet transfers incorrectly classified as sales, unmatched transactions flagged by the aggregator); (3) import the file through TaxWise's Schedule D/Form 8949 import function; (4) review the imported transactions in the software to confirm the checkbox assignments (Box B for reported-without-basis, Box C for unreported) are correct; (5) verify that the total proceeds on the imported Form 8949 reconciles to the total proceeds on the client's Forms 1099-DA. A reconciliation variance between 1099-DA proceeds and Form 8949 proceeds is an IRS matching flag.
If you are not yet using TaxWise's 8949 CSV import feature, the TaxWise software trial lets you walk through the Form 8949 import workflow before the filing season begins. Getting the import format right before a client's 500-transaction file lands in your queue is a meaningful time investment. ATP is the authorized TaxWise reseller and can answer questions about the import configuration for digital asset transaction files.
E-filing large transaction sets
Returns with large numbers of Form 8949 transactions can exceed the limits of standard e-file transmission if each transaction is submitted as a separate line item in the electronic file. The IRS accommodates this through the summary line approach: the preparer reports summary totals on Form 8949 (one line per checkbox grouping, showing aggregate proceeds and aggregate basis), attaches the full transaction detail as a PDF attachment within the e-filed return, and checks the appropriate box indicating that a statement is attached. Tax software that supports attached PDF statements within the e-file submission handles this correctly, but verify the attachment functionality for your specific software version before the filing season.
For crypto amendments on previously filed returns that did not include digital asset activity, the workflow flows through Form 1040-X. See the Form 1040-X amended return guide for crypto corrections for the step-by-step process, including how to attach a corrected Form 8949 and Schedule D to an amended return and how to e-file the amendment through ATP's e-file enrollment program.
Preparers who are not yet enrolled for e-file with ATP should complete ATP's e-file enrollment before the filing season. ATP's e-file infrastructure supports both original Form 8949 e-file and crypto-related amended returns submitted via Form 1040-X. Enrollment is straightforward for preparers who already hold an active EFIN.
Preparers looking to build formal crypto competency for CE credit and AFSP compliance should review ATP's AFSP continuing education courses, which include digital asset and cryptocurrency tax topics that count toward IRS CE requirements and AFSP participation. Building documented crypto competency before the 2026 filing season (when Form 1099-DA cost basis reporting begins in full) positions your practice ahead of the compliance curve rather than behind it.
Regulated Claims and Citations: Preparer Verification Required
The following claims and citations should be independently verified before relying on them in client engagements: (1) Digital asset property treatment: IRS Notice 2014-21; verify current guidance and any superseding notices at IRS.gov. (2) Staking income as ordinary income: Rev. Rul. 2023-14; subject to ongoing litigation (Jarrett v. United States) and future IRS guidance; verify current IRS position at IRS.gov. (3) Form 1099-DA cost basis timeline: gross proceeds only for TY2025, mandatory cost basis reporting beginning TY2026; verify current implementation schedule at IRS.gov. (4) NFT collectibles rate risk: IRC Section 1(h)(4); IRS treatment of NFTs as collectibles is not fully settled and is subject to future IRS clarification; verify current guidance at IRS.gov. (5) Airdrop income treatment: Rev. Rul. 2023-14 and related guidance; verify at IRS.gov. (6) DeFi transaction treatment: current IRS guidance addresses token swaps as property exchanges; broader DeFi treatment is subject to future IRS guidance; verify current position at IRS.gov. (7) Form 8949 checkbox logic and summary reporting: verify current Form 8949 instructions at IRS.gov each filing season, as digital asset rules are updated. This guide is informational and does not constitute legal or tax advice.
Frequently Asked Questions
Does Form 1099-DA report cost basis for tax year 2025?
No. For tax year 2025, Form 1099-DA reports gross proceeds from covered digital asset sales but Box 1g (cost basis) is left blank. Mandatory cost basis reporting by brokers does not begin until tax year 2026. This means preparers handling TY2025 returns must reconstruct cost basis independently using exchange CSV exports, prior-year records, and aggregator tools. Verify the current IRS implementation schedule for Form 1099-DA cost basis reporting at IRS.gov.
Is a wallet-to-wallet transfer between the same owner's wallets a taxable event?
No. A transfer of cryptocurrency between two wallets that are both owned and controlled by the same taxpayer is not a taxable event. No gain or loss is recognized on the transfer, and the original cost basis and acquisition date carry over to the receiving wallet. Recording a wallet-to-wallet transfer as a sale and recognizing proceeds is one of the most common errors in crypto return preparation. Preparers must obtain a complete list of all wallets the client controls and map transfers accordingly.
How is staking income taxed under current IRS guidance?
Under Rev. Rul. 2023-14, the IRS takes the position that staking rewards are ordinary income in the year received, valued at fair market value on the date of receipt. That fair market value becomes the taxpayer's basis in the staking rewards. When the taxpayer later sells or exchanges those rewards, any difference between the sale price and the basis established at receipt is a capital gain or loss. The revenue ruling has been challenged in litigation (Jarrett v. United States), and the broader treatment of proof-of-stake rewards remains an evolving area of IRS guidance. Verify the current IRS position at IRS.gov before advising clients.
What is the collectibles rate risk for long-term NFT gains?
Under IRC Section 1(h)(4), long-term capital gains on collectibles are taxed at a maximum rate of 28 percent rather than the standard preferential long-term capital gains rates of 0, 15, or 20 percent. Current IRS guidance on whether NFTs qualify as collectibles subject to the 28 percent rate is not fully settled and is subject to future IRS clarification. Preparers handling clients with long-term NFT gains should flag this rate risk and apply the conservative treatment pending further IRS guidance. Verify the current IRS position on NFT collectible classification at IRS.gov.
When should a preparer require a client to use a crypto aggregator tool before starting the engagement?
A preparer should require clients with more than a small number of transactions to run their complete transaction history through a reputable crypto aggregator tool (such as CoinTracker, Koinly, CoinLedger, or TokenTax) before the engagement begins. High-volume transaction sets that span multiple exchanges and wallets are impractical to reconcile manually. Building the aggregator requirement into the engagement letter as a prerequisite for crypto work limits the preparer's liability for incomplete data and sets a clear data-delivery standard. The preparer should still review the aggregator output for missing wallets and obvious classification errors rather than accepting it without scrutiny.