On almost every crypto tax debt I've ever unwound, the first move is to knock the penalties off before anyone talks about payment plans or offers. Penalties compound fast and they compound on themselves — failure-to-file, failure-to-pay, accuracy-related, and sometimes fraud. Get them removed and the base problem shrinks by 20-40%. This is a practical walk-through of crypto tax penalty abatement: what the statutes say, which arguments actually work, and a real example stripping $37,000 off a single crypto case.
The penalties that stack on crypto cases
A typical crypto CP2000 or audit assessment layers several penalties:
- Failure to file — IRC §6651(a)(1). 5% of unpaid tax per month up to 25%. Kicks in when you miss the filing deadline (including extensions) on a return showing a balance due.
- Failure to pay — IRC §6651(a)(2). 0.5% per month up to 25%. Stacks with FTF until month 5, then FTF stops growing and FTP continues.
- Failure to pay estimated tax — IRC §6654. Computed at short-term AFR plus the statutory addition. This is the one that catches crypto traders who had a big Q1 gain and never made an ES.
- Accuracy-related — IRC §6662. 20% of the underpayment attributable to negligence, disregard, or substantial understatement. The IRS asserts this aggressively on crypto.
- Fraud — IRC §6663. 75% of the underpayment attributable to fraud. Rare. If asserted, you're in a different universe.
Under IRC §6664(c), the accuracy-related penalty does not apply to any portion for which there was reasonable cause and the taxpayer acted in good faith. That's the statutory doorway to abatement on §6662.
First-Time Abatement (FTA): the free shot
Every crypto case starts here. Under IRM 20.1.1.3.6.1, a taxpayer is entitled to administrative waiver of failure-to-file, failure-to-pay, and failure-to-deposit penalties for a single tax period if:
- You've had no penalties for the three prior tax years (de minimis penalties don't disqualify).
- You've filed all currently required returns or filed extensions.
- You've paid, or arranged to pay, any tax due.
FTA is administrative — no reasonable cause required. The IRS will often grant it on a simple phone call to the Practitioner Priority Service. It is, truly, a free shot. Almost nobody asks for it because they don't know it exists.
Reasonable cause: the Boyle framework
If FTA doesn't apply, or if the penalties you want abated aren't FTA-eligible (§6662 accuracy-related is not FTA-eligible, for instance), you fall back on reasonable cause under §6664(c) or the general reasonable cause exceptions in §6651.
The framework comes from United States v. Boyle, 469 U.S. 241 (1985). The Supreme Court held that reliance on a tax professional to file a return is not reasonable cause — filing is a "non-delegable duty." But Boyle's own language preserved reliance on professional advice as reasonable cause for substantive positions, and the IRS recognizes reliance as a reasonable-cause factor in most accuracy-related cases. That distinction matters on crypto.
Reasonable cause arguments that work on crypto
- Reliance on a qualified tax professional on a substantive position (e.g., not reporting a bridge transaction as taxable) where the professional had full facts. Treas. Reg. §1.6664-4(c). Requires you actually gave the preparer your wallet addresses.
- Reasonable reliance on 1099 and exchange reporting that didn't capture DeFi activity. Limited but real.
- Crypto-novelty: good-faith reliance on unclear guidance before Rev Rul 2019-24 (the basis-carryover airdrop/hard-fork ruling) and Rev Rul 2023-14 (staking). For tax years before the applicable ruling, a position contrary to the later-issued guidance is often supportable if contemporaneous professional advice was obtained.
- Serious illness, death in immediate family, disaster — the traditional Form 843 grounds, applied to crypto just like anything else.
- Inability to obtain records where an exchange went bankrupt (FTX, Celsius, BlockFi). Doesn't excuse the liability, but supports reasonable cause on accuracy where basis information was genuinely unobtainable. Combined with the Cohan rule, this gets you real relief.
Worked example: stripping $37,000 off a 2021 crypto case
Facts: taxpayer sold $1.1M of ETH and SOL in Q4 2021. Filed 2021 return on extension October 15, 2022, reporting gains. Did not pay. IRS assessed the following as of the first resolution engagement in early 2026:
- Tax: $318,000
- Failure to pay (25% cap at month 50, so maxed): $79,500
- Failure to pay estimated tax (§6654): about $9,400
- Interest through date: about $94,200
- Total: about $501,100
Abatement strategy:
- FTA on 2021 §6651(a)(2). Clean prior three years (2018-2020). Granted on a single Practitioner Priority call. Penalty removed: $79,500.
- Reasonable cause on §6654 estimated tax penalty. Taxpayer had no prior-year safe harbor because 2020 income was substantially lower; crypto gains were in Q4 and a single illiquidity event meant liquidating at a loss would have been required to fund ES. Argued on Form 843. Partially granted: $4,100 removed, $5,300 remaining.
- Interest adjustment. When a penalty is abated, the interest computed on that penalty is also abated. Interest reduction from FTA and partial §6654 abatement: roughly $20,400.
Net reduction on penalties and interest: about $104,000. On the $501,100 balance, we stripped $37,000 off the penalty stack (FTA + §6654) plus another $67,000 of associated interest. New balance to resolve: $397,100. From there, we built the installment agreement. Same client, completely different case to work.
What doesn't work
- "I didn't know crypto was taxable." Notice 2014-21 has existed for a decade. Ignorance isn't reasonable cause.
- "I couldn't afford to pay." Inability to pay is not reasonable cause on §6651(a)(2) — the Supreme Court in Brown v. United States was clear. It can support Currently Not Collectible or an Offer in Compromise, but it won't abate FTP.
- "My preparer didn't tell me I needed to report it." Under Boyle, filing is non-delegable. On a substantive position, reliance works only if you gave the preparer the facts.
- Blanket reasonable cause letters with no evidence. The IRS reads thousands of these a week. Specific, documented, dated, tied to the penalty period — or don't bother.
The mechanics
FTA by phone: call the Practitioner Priority Service at 866-860-4259, reference the tax period, confirm prior three clean years. If granted, confirm in writing with a follow-up letter.
Reasonable cause: Form 843 with a reasoned argument tied to the specific penalty and period. Attach contemporaneous evidence — emails to the preparer, medical records, disaster declarations. Do not submit a generic template.
Appeals: if the IRS denies abatement at the Service Center, you have appeal rights. Most reasonable-cause denials are overturned at Appeals because the Service Center examiner isn't the right decision-maker for a facts-and-circumstances argument.
Talk to a tax attorney before the IRS picks the outcome for you
If you owe the IRS on crypto, strip the penalties off before you talk about paying anything. If the IRS already has your crypto on its radar — whether from a 1099, a John Doe summons, or a matched exchange data set — waiting is the most expensive option. I've spent 32 years cleaning up cases that started as "I'll deal with it next year." Next year is worse.
Call (813) 229-7100 for a confidential consultation, or book online at https://getirshelp.com/contact. No sales pitch. You'll get a straight read on what the IRS is likely to do, what your realistic options are, and what it costs to fix it.