What’s New

Letter 3219 is the Statutory Notice of Deficiency the IRS sends when an audit by mail ends without your agreement. It gives you 90 days from the mailing date (150 if the notice is addressed outside the United States) to petition the U.S. Tax Court, and the IRS cannot extend that time.

Letter 3219-B is the Statutory Notice of Deficiency the IRS sends a corporation, estate, or trust when third-party information does not match its return, often after a Letter 2030. It gives the entity 90 days from the mailing date (150 if addressed outside the United States) to petition the U.S. Tax Court.

Letter 531 is the Statutory Notice of Deficiency the IRS uses most often in income tax cases, usually at the end of a field (in-person) audit. It gives you 90 days from the mailing date (150 if the notice is addressed outside the United States) to petition the U.S. Tax Court.

Estimate the IRS failure-to-file and failure-to-pay penalties and daily-compounded interest on one individual return, with the IRC section, the rate, and the arithmetic beside every line.

Draft a First Time Abate or reasonable-cause request letter from your own facts, with each IRM test marked met, not met, or unknown and the source beside it.

Calculate the IRC §6213(b)(2)(A) 60-day deadline to request abatement of a math-error assessment (CP10, CP11, CP11A, CP12, CP13, CP16), adjusted under IRC §7503 for weekends and legal holidays.

Check whether a student brings you the American opportunity credit or the lifetime learning credit, the amount after the income phase-out, the refundable part, and who claims it, each rule cited to IRC §25A and Form 8863.

Check whether a child brings you the child tax credit or the credit for other dependents under IRC §24, including the age-17 and Social Security number rules, then see the income phase-out line by line.

Check which of the five filing statuses you can use, including the considered-unmarried rules for spouses who live apart, head of household, and qualifying surviving spouse. Each test shows its citation to the tax code or Pub. 501.

Check whether a person is your qualifying child or qualifying relative, whether an exception applies, and who may claim a child that two people could, each test cited to IRC §152 and Pub. 501.

Check whether you must file a federal return: the gross-income test by filing status and age, the separate test for dependents, and the situations that require a return at any income, each cited to IRC §6012 and Pub. 501.

What the IRS itself states about processing time for refunds, amended returns, Forms 2848 and 8821, ITINs, EINs, and offers in compromise, with the IRS source and check date for each row.

Find out whether a child’s unearned income is taxed at the parent’s rate under IRC §1(g), and how much extra tax that adds, with every line of Form 8615 shown and cited.

All five IRS balance-due notices in order — CP14, CP501, CP503, CP504, LT11/Letter 1058 — with what each one triggers, authorizes, and requires by when.

Find how much of your Social Security or Tier 1 Railroad Retirement benefits are taxable, with every line of Pub. 915 Worksheet 1 shown and cited to IRC §86.

Find your standard deduction for 2025 or 2026, with the age 65 and blindness add-ons, the dependent limit, and the cases where it is zero, every step cited to IRC §63 and Pub. 501.

What a tax research memorandum contains, a copyable template, and a complete sample memo on a fictional client, plus what counts as authority.

Current IRS quarterly interest rates with an as-of date, the quarterly rate history back to 2016, and the statutory percentages for failure-to-file, failure-to-pay, accuracy-related, and civil fraud penalties — each cited to the Revenue Ruling or Code section.

CP565 confirms your Individual Taxpayer Identification Number (ITIN). It asks for nothing back unless the name or date of birth on it is wrong, and it carries a rule worth knowing: an ITIN that goes unused on a tax return for three years expires.

Letter 3064C is the IRS's all-purpose custom reply: an employee writes the body for your specific case, so the number tells you the format but not the subject. What it means, and whether it has a deadline, depends entirely on the paragraphs inside it.

LT36 is a one-time reminder letter the IRS mailed in 2025 to current and retired federal employees with an unpaid balance or an unfiled return. It is not a levy notice and carries no appeal deadline — but it is aimed at a group whose federal pay and pension can be levied automatically.

These notices all say the same thing: the IRS has no record of a return it believes you owed. CP59, CP515, CP516 and CP518 are the individual track; CP259 and CP518B are the business track. Which response you send depends on which track your notice is on.

These four notices are one escalation, not four problems. The IRS is missing a return, has computed your tax from the income other people reported about you, and is moving toward assessing it. CP63 holds a refund. CP2566 and CP2566R propose the amount. CP3219N is the last step, and the IRS cannot extend its Tax Court petition period.

Every IRS phone line sorted by problem and by department — practitioner, individual, business, identity theft, e-Services, EFTPS, TAS, estate and gift, excise — with the number and hours IRS.gov prints.

Describe a tax situation in plain language and find the matching IRS form, with a link to its current IRS.gov page.

CP10 doesn't bill you for anything today — it quietly shrinks the estimated tax credit you were counting on for next year.

CP101 gives a business 10 days to dispute a Form 940 math-error correction — a fraction of the 60-day window the IRS gives individual taxpayers for the same kind of mistake, and the difference isn't a typo.

CP102 corrects an employment tax return — Form 941, 943, 944, or 945 — and gives a business the same tight 10-day window CP101 gives a Form 940 filer, for a mistake that's easy to assume is routine and isn't.

CP107 corrects a Form 1042 withholding return and gives a business 60 days to respond — six times CP101 or CP102's window — but it also carries a failure-to-deposit penalty most of this notice family never mentions.

CP111 is good news — a Form 940 correction that puts money back in the business's hands, and the one thing worth checking is whether the refund actually shows up within the window the notice itself promises.

CP112 corrects an employment tax return in the business's favor — no action required, and the only real task is confirming the refund actually lands within the window the IRS itself promises.

CP117 is a refund notice that still carries a 10-day deadline — the one member of this notice's overpayment family that does — and its own "it will explain why you owe" instruction is boilerplate left over from the balance-due side, not a sign something else is wrong.

CP13 is a math-error notice with nothing to pay and no refund coming — which makes it the easiest math-error notice to ignore, and the 60-day right to dispute it disappears exactly the same way the others' do.

CP268 isn't a bill and it isn't quite a refund notice either — it's the IRS holding a business's excess credit in limbo, and the 30-day response window is what keeps that limbo from becoming a much slower problem.

Browse the collections hub — the IRS collection sequence, the CSED, and every way to intervene, in one problem-shaped page.

Run the ratio percentage, 55% average benefits, and 25% owner concentration tests on a dependent care assistance program (DCAP), at the $7,500/$3,750 IRC §129(a)(2)(A) limits, per proposed REG-101355-26.

Browse the penalties hub — AEP, First-Time Abate, and reasonable cause, with the notices, transaction codes, and calculators for each.

Browse the transcripts hub — which transcript to pull, how to read a module, and the transaction codes practitioners misread most often.

Run the ratio percentage and 55% average benefits tests on Trump Account contributions, at the $2,500 (IRC §128(b)) and $5,000 (IRC §530A(c)(2)) limits, per proposed REG-101355-26.

TC 294 takes back some or all of a tentative refund the IRS already paid out under the net operating loss carryback program, and because that refund went out fast and unaudited, seeing this code means the IRS is now telling you it reviewed the claim again and found it did not hold up in full.

TC 295 is the fast, unaudited refund the IRS pays out within 90 days when a taxpayer carries a net operating loss, capital loss, or credit back to an earlier year where the Code permits the carryback, and understanding that it is tentative rather than final is the key to reading everything else that happens to the module (the IRS's record for one tax period within the account) afterward.

TC 298 is an ordinary additional tax assessment with one added feature — a mandatory interest computation date built into the transaction itself — and that single detail means the interest on the amount can predate the posting date, which changes how a transcript reader should calculate what is actually owed.

TC 304 is the examination-track version of taking back a tentative carryback refund — the same disallowance TC 294 performs at the processing level, but posted only after Examination Division actually reviewed the claim, which changes what procedural rights and next steps apply.

TC 305 is the examination-track twin of TC 295 — the same fast, provisional carryback refund, but processed by Examination Division rather than routine return processing, which can mean the claim arrived alongside or during an active audit rather than as a standalone filing.

TC 308 is TC 298's examination-track twin — an additional tax assessment carrying a mandatory interest computation date — but specifically for a deficiency that Examination or Appeals determined, which means the assessment followed an actual audit rather than a routine processing adjustment.

TC 350 assesses a negligence penalty, and Doc 6209 limits it to returns due before January 1, 1990. On later returns the IRC §6662 negligence penalty posts as TC 240, and the penalty reference number beside it identifies the legal theory: 786 for negligence on most assessments the IRS entered after 2014.

TC 351 reverses some or all of a TC 350 negligence penalty, and Doc 6209 limits TC 350 to returns due before January 1, 1990. Because Doc 6209 lets TC 351 abate the penalty in whole or in part, a partial TC 351 does not necessarily mean the underlying negligence determination was wrong — the IRS may only have recalculated the dollar amount.

TC 450 means the IRS has assessed someone for another taxpayer's liability under the transferee-liability doctrine, and because, for income, estate or gift tax, that assessment carries the same deficiency-procedure rights as an ordinary tax assessment, the first question is whether a Notice of Deficiency was issued and whether the 90-day Tax Court window has run.

TC 451 abates a transferee liability assessment in whole or in part, and — like the assessment it reverses — the size of the abatement relative to the original TC 450 tells you whether the transferee prevailed entirely, only partly, or whether the underlying transferor liability itself was simply recalculated.

TC 468 records the result of a request for an extension of time to pay estate tax, and an approved one does two things a lot of people miss at once — it stops the failure-to-pay penalty but not interest, and it suspends the collection statute for as long as the extension runs, under a specific statute most practitioners never have reason to look up.

TC 495 closes out the record of a statutory Notice of Deficiency — either because the deficiency case reached a resolution or because the original notice was issued in error — and the transcript alone does not tell you which of those two very different outcomes actually happened.

TC 510 releases a freeze on refunds that the IRS set because the Social Security Number or name control on a return did not match its records, and the release is permanent only as long as the SSN and name control stay unchanged going forward.

TC 538 on a business's Form 941 module (the IRS's record for one tax period within the account) is not a payment the business made — it is a mirrored credit created because a responsible individual paid part of their own Trust Fund Recovery Penalty, and the real reconciliation work is checking that credit against every responsible person's own account so the trust-fund portion is never collected twice.

TC 539 backs out a mirrored Trust Fund Recovery Penalty credit that TC 538 had previously posted, and because that credit represented a responsible person's payment being applied to the business's account, a TC 539 means that payment relationship is being unwound — not that the business now owes new money it did not owe before.

TC 973 is a document-receipt marker that means three different things depending on context — a corporation's Form 1139 tentative refund application, a Form 8038-series bond return, or a Form 5330 excise-tax filing — and on a carryback module (the IRS's record for one tax period within the account) it can also mean the claim is on hold for a BMF (Business Master File) identity-theft review, not simply that it has been logged in.

Browse the index of every live calculator and router for tax practitioners.

TC 720 looks like it belongs to the same family as the refund-issuance codes sitting near it on a transcript, but it runs the opposite direction — it is a credit posted when money the IRS already sent out comes back, whether from a bank flagging a deposit or a taxpayer repaying an erroneous refund on demand.

TC 722 does not mean a taxpayer repaid a refund twice or that a new liability appeared — it means the IRS's own computer system is undoing a TC 720 that posted incorrectly in the first place, and the correction, not the original entry, is what a transcript reader needs to explain.

TC 730 is the credit half of a manual transfer that moves already-computed overpayment interest between two of a taxpayer's own modules (the IRS's records for separate tax periods within one account) — a workaround that exists specifically because Master File (the IRS's central account-processing system) and its automatic offset engine cannot be trusted to compute interest correctly once a person, not the computer, already did the math.

TC 732 undoes a TC 730 manual interest transfer that was entered incorrectly, in whole or in part, and it is worth recognizing on sight because it means the original transfer — not just the correction — is the thing that actually needs a second look.

TC 736 is Master File's (the IRS's central account-processing system) own computer-generated way of moving overpayment interest onto a module (the IRS's record for one tax period within the account) that owes money elsewhere in the same account — reliable arithmetic when the computer both found the offset and computed the interest, but the same IRM subsection that describes it also warns that a manually computed interest amount can still ride through this systemic code and come out wrong.

TC 740 means a refund check came back to the IRS instead of reaching the taxpayer, but it hides two unrelated reasons behind one number — an undeliverable address and a check nobody ever cashed — and the blocking series on the transcript is the only thing that tells them apart.

TC 756 moves overpayment interest earned on an individual account across to a business tax module (the IRS's record for one tax period within the account) that owes money, a cross-Master-File version of the same interest-transfer engine that otherwise stays inside one account type, and it shows up specifically when a taxpayer carries both an individual and a business balance.

TC 770 is the code that actually pays a taxpayer interest on an overpayment the IRS held onto too long, and because it usually means a person calculated the interest by hand rather than the computer generating it automatically, it is worth checking rather than assuming it is correct on sight.

TC 771 takes back interest that had already been calculated into a refund the IRS is deleting before it ever goes out, and its presence on a business account is a strong signal that an entire refund — not just the interest portion of it — was stopped mid-process.

TC 772 covers three genuinely different situations under one transaction code — fixing a wrong interest credit, charging manually computed netting interest, and cleaning up interest Master File (the IRS’s central account-processing system) cannot automatically remove after an offset reversal — and telling which one applies changes what the code actually means for the account.

TC 776 is the computer deciding, on its own, that a tax module (the IRS’s record for one tax period within the account) has earned interest because it became overpaid — the credit that has to exist before any of that interest can be moved, refunded, or offset anywhere else on the account.

TC 777 looks like the automatic undo button for TC 776, but current procedure only generates it for a narrow pair of refund-check problems — reversing interest tied to an offset takes a different, manually-input code entirely.

TC 830 moves an overpayment forward to next year’s estimated tax by hand rather than by computer, under a narrower statutory authority than an ordinary IRS offset, and once the short reversal window in the current IRM closes, the election becomes binding whether or not the taxpayer still wants it.

TC 836 is the computer-generated half of a credit elect — the debit the IRS's own system posts automatically the moment a return shows an overpayment the taxpayer chose to carry forward, and it obeys the same binding reversal deadline as its manually-posted counterpart.

TC 840 means an IRS employee, not the computer, issued a refund by hand — and a specific blocking-series pattern the current IRM calls a "Dummy TC 840" means the code can post even when no actual check or deposit was ever sent.

TC 841 credits back a refund check that got cancelled before or after the taxpayer had it, and the one detail that actually matters — whether the taxpayer sent it back or the Postal Service could never deliver it in the first place — is a different transaction code entirely, not a note on this one.

TC 842 is the code that stops a scheduled business refund before Treasury ever cuts a check for it — a business-account-only transaction that means the money was never actually released, not that a refund went out and then came back.

TC 844 is a zero-dollar freeze that locks an entire account once the IRS has identified a refund it should never have sent, and it applies specifically to the category of erroneous refunds the government can only get back by asking, suing, or offsetting — not by an ordinary assessment.

TC 845 releases the account-wide freeze that TC 844 set for an erroneous refund, but a small number of gatekeeping restrictions and one plural detail in its own release rule mean the code alone does not tell you whether the case actually resolved in the government's favor.

TC 850 is the manual move of overpayment interest from one tax module (the IRS’s record for one tax period within the account) to another, and current procedure treats it as mandatory rather than optional whenever the interest involved started life as a hand-computed figure the computer cannot safely date on its own.

TC 851 undoes a computer-generated interest transfer, and specifically the computer-generated one — despite sitting numerically between two codes that involve the manual version of the same transaction, TC 851 has nothing to do with either of them directly.

TC 856 is Master File — the IRS’s central account-processing system — automatically moving overpayment interest from one tax module (the IRS’s record for one tax period within the account) to another to satisfy a balance due, and the one situation where the IRS has documented that this automation cannot be trusted to get the dates right on its own.

TC 876 is what an overpayment interest transfer looks like once it has to cross from an individual account to a business one — the same underlying mechanism as an ordinary interest offset, run through a separate code family built specifically for moving money between the IRS's two master files, its separate account-processing systems for individual and business taxpayers.

TC 896 is a tax offset that crosses Master Files (the IRS's separate account-processing systems for individual and business taxpayers) or lands on an IRAF or Shared Responsibility Payment account rather than staying inside one Master File the way TC 826 does. A rare older variant with an agency code is a Debtor Master File offset the IRS made from 1984 through January 11, 1999 (IRM 21.4.6.4.1).

TC 897 reverses a specific 1980s-and-90s predecessor to today's Treasury Offset Program, and because that program stopped generating new offsets in January 1999, seeing this code on a current account is a signal to check just how old the underlying history actually is before treating it like an active TOP transaction.

What the IRS Math and Taxpayer Help Act (H.R. 998, Public Law 119-39) changes about math-error notices, which notices it covers, and when it takes effect.

CP162B charges a partnership or S corporation for an incomplete return, an e-filing failure, or both — and which one is on your notice changes both the relief available and the deadline that applies.

CP162C can charge a partnership or S corporation for late filing, an incomplete return, a missing tracking report, or an e-filing failure — sometimes more than one at once — and the notice's own billing summary is the only reliable way to tell which.

TC 151 looks like a general-purpose "undo my return" code, but Document 6209 tags it EPMF — it lives on the Employee Plans Master File governing Form 5500 filings, and it will never show up on an individual or business income-tax transcript.

TC 196 is the computer charging interest on a balance without anyone deciding to — it posts at the first bill, after certain adjustments, and whenever an assessment forces the system to true up what interest is actually owed, and none of those triggers involve a person choosing the amount.

TC 299 is functionally the same abatement as TC 291, except the transaction itself must carry an interest computation date — and that date, not the tax figure, is what drives a systemic restatement of both interest and the failure-to-pay penalty.

TC 309 is the Examination-side twin of TC 299 — the same mandatory interest-computation-date mechanic, but tied to Form 2285 and a real data-integrity guardrail that blocks the abatement if the module cannot actually support it.

TC 421 closes out the open-exam marker that TC 420 or TC 424 set — but the freeze it is closing never held any money in the first place, so reading TC 421 as the code that released a refund is the wrong lesson to take from it.

TC 472 does not undo a TC 470 hold in general — Doc 6209 requires, for closing codes 94 through 99, the reversal to carry the same closing code as the freeze it is releasing, so a mismatched pair on the transcript can mean the hold a client is worried about never actually lifted.

TC 483 covers two different scenarios — an offer flagged in error, or one returned as not processable — and Doc 6209 is explicit that neither one buys the taxpayer a single extra day on the collection statute.

TC 502 restores the original collection statute date after a military deferment posted in error — but it releases only the account hold, not the interest and penalty freezes riding alongside it, which is the detail a practitioner needs before telling a client the correction is complete.

TC 522 does not mean the litigation ended — it means the freeze should never have gone on the account in the first place, and the IRM tells its own staff in capital letters not to use the code that actually means the case resolved.

TC 532 does not mean a client's finances improved or that a new liability appeared — it means the campus should never have reported Currently Not Collectible status in the first place, which is a very different conversation to have with a client than the one either of TC 530's other two reversal codes calls for.

TC 535 puts a wrongly-written-off balance back on the module — but a complete reversal turns the interest and penalty computation back on, so a partial TC 535 can bring part of the balance back while interest and failure-to-pay penalty computations may stay switched off.

TC 576 freezes only the part of a refund the return claimed that the IRS thinks tax law does not allow — the rest of the overpayment still goes out, which is the detail that separates this from a full-refund freeze and the one most explanations skip.

TC 577 restores the unallowable amount a TC 576 froze — and reading its four possible triggers tells you whether an examination cleared the item or the freeze was simply a mistake being corrected.

TC 611 means the check a taxpayer sent with their return bounced — it reverses TC 610 dollar for dollar and, on most accounts, automatically triggers a bad-check penalty the client did not know was coming.

TC 612 undoes a TC 610 that posted wrong — and because it can reverse the remittance in whole or in part, the amount it debits tells you whether the whole payment was misposted or only a piece of it.

TC 620 is the payment a filer sent with an extension request — Form 7004, 8868, or 5558. Its presence shows a remittance posted with an extension form, which helps when a client disputes a failure-to-pay penalty; a late-filing defense also looks to the TC 460.

TC 621 reverses an extension payment that bounced — the check sent with Form 7004, 2758, or 8736 — and on most BMF (Business Master File) accounts it automatically posts a bad-check penalty in addition to unwinding the credit.

TC 630 is a narrow, manually computed credit tied to a Separate Appropriations item — most often a solar or wind energy investment credit under the identification-number convention Doc 6209 spells out — and its rarity is exactly why misreading it as an ordinary payment causes confusion.

TC 636 is the twin of TC 630 that Master File (the IRS's central account-level record for a taxpayer) generates automatically — the same Separate Appropriations credit category, posted by the system rather than by a human computation, and the "Generated Transaction" label on the entry is the tell that distinguishes the two.

TC 640 credits an advance payment a taxpayer posts against an anticipated audit or underreporter assessment before the IRS assesses the tax. Interest can surprise clients: on a cash bond, the excess over the eventual deficiency draws no interest when it comes back, even if the IRS later abates the deficiency, but a returned IRC 6603 deposit earns interest on the part attributable to a disputable tax.

TC 641 unwinds a cash-bond or 6603 deposit whose check bounced, and unlike most dishonored-payment reversals, it can also release the freeze TC 640 put on the module (the account record for one tax period) — a detail that changes what a client can and cannot do with the rest of the account.

TC 650 records an employer's federal tax deposit before the return that reports it has even been filed, and its most useful quirk is that an unmatched deposit can silently roll forward, period after period, until it finds a return to attach to.

TC 651 means a federal tax deposit bounced — and because deposit timeliness is judged by the deposit schedule, not the return's due date, a client can face both a bad-check penalty and a separate Failure to Deposit penalty from a single returned check.

TC 660 usually credits a quarterly estimated tax installment, and it comes with a rule that is easy to overlook: absent a documented IRS or taxpayer error, the IRS cannot apply this year's estimated payment to last year's balance due, no matter how badly the client wants it applied that way.

TC 661 is a single reversal code doing double duty — on an individual account it always means a bounced estimated tax payment, but on a business account the same code can mean either that or a bounced federal tax deposit, and the MFT (Master File Tax account type) is what tells them apart.

TC 666 is Master File (the IRS's central account-level record for a taxpayer) automatically going looking for a spouse's estimated tax credits when a taxpayer claims more than their own module (the account record for one tax period) has — and it can post for zero dollars, which is not a system error but the documented outcome when the search comes up empty.

TC 667 is the debit a spouse's module (the IRS's record for one tax period within the account) takes when Master File (the IRS's central account-processing system) runs an automated search, finds available estimated tax credit, and pulls it across to satisfy the other spouse's return — the module losing the credit, not the one claiming it.

TC 671 reverses a bounced check sent against an existing balance — the most common payment type on a transcript — and it carries one exception worth memorizing: electronic (EFT) payments in blocking series 800-899 do not trigger the automatic bad-check penalty the way a paper check does.

TC 672 does not just reverse a misposted TC 670 — Doc 6209 says inputting one actually converts the original TC 670 into a TC 673, which is why the payment can look relabeled rather than reversed on the transcript.

TC 678 posts an estate's payment of federal estate tax using old Treasury bonds redeemed at full face value for exactly that purpose — a genuinely rare code on a modern transcript, and one worth recognizing rather than mistaking for a data-entry error.

TC 680 is a payment a taxpayer specifically directs toward interest rather than tax or penalty, and its overpayment logic has a cascading rule most practitioners never read closely: money that exceeds all interest due spills over to pay down tax and penalty automatically.

TC 681 reverses a bounced check that was specifically designated to pay interest — which means the interest-paid field TC 680 had updated unwinds along with the money, and any TC 196 the overpayment cascade generated needs to be revisited too.

TC 690 is a payment a taxpayer specifically directs at a penalty rather than tax or interest — a distinction that matters most when only one penalty on a multi-penalty module (the IRS's record for one tax period within the account) is being challenged and the client wants to pay down everything else first.

TC 691 unwinds a bounced check that was specifically designated to pay a penalty — restoring the module (the IRS's record for one tax period within the account) to the same undesignated, unpaid state it was in before the client tried to pay down that one liability on purpose.

TC 694 pays down lien and levy fees specifically — and the module (the IRS's record for one tax period within the account) caps it by design: it will not accept more in TC 694 payments than the unreversed TC 360 fees actually assessed, so a payment sized wrong simply fails to post rather than overpaying.

TC 700 is the receiving side of a manual credit transfer — money moved deliberately from one module (the IRS's record for one tax period within the account) to another by a caseworker — and one of its documented uses is quietly preventing an erroneous-refund bill from generating while the case is still being worked.

TC 706 is the receiving side of an internal refund-offset engine built into Master File (the IRS's central account-processing system) — the credit that lands on a balance-due module (the IRS's record for one tax period within the account) when the computer redirects an overpayment from elsewhere in the same account before a refund ever goes out — and where the offset drew down one spouse's overpayment against the other's separate liability, Form 8379 Injured Spouse Allocation relief reaches it directly.

TC 710 is the credit-elect a taxpayer actively chose — applying last year's overpayment to this year's estimated tax instead of taking a refund — and, for a timely, full credit-elect, its transaction date is fixed to the return's original due date rather than whenever the transfer actually posted; a late or partial credit follows a different dating rule instead.

TC 716 is an automated version, built into Master File (the IRS's central account-processing system), of a credit-elect carryforward — no separate manual input once the return elects the credit, since the computer generates it directly from an available prior-year credit across a specific, named list of business and individual return types.

TC 721 means a taxpayer's own check to repay a refund they received in error bounced — an unusual direction of money that still triggers the same automatic bad-check penalty as any other dishonored payment on the account.

TC 760 is the ending of a genuinely lost-payment case — a manual credit the IRS posts once a taxpayer has proven they made a payment that Master File (the IRS’s central account-processing system) never recorded, and only one specialized unit has authority to input it.

TC 764 posts Earned Income Credit that an adjustment added after the fact, not the original return's own EIC line — a distinction that matters when reconciling why a client's credit changed months or years after they filed.

TC 765 takes back an Earned Income Credit that already posted — but it reverses two different codes with two different origins, and the transcript alone will not tell you which one just came off.

TC 767 means two different things depending on whether it carries an Offset Trace Number — one is a routine credit correction, the other is a restricted transaction almost no one outside the IRS is authorized to input, and confusing them misreads what actually happened to the money.

TC 781 is the offer failing after acceptance — it reverses every TC 780 on the module and puts the original liability back, and the IRM directs employees to input it on every offer module, including ones that were already paid in full or past their own collection statute deadline.

TC 782 sounds like a full undo, but on IMF (Individual Master File) "correcting" an erroneous acceptance does not clear the module. It puts the account back under the same pending-offer (TC 480) freeze that accepting the offer had lifted — the opposite of what the word "correction" suggests.

TC 790 moves an individual's overpayment across to a business account they also control — but only after a specific gate posts first, since Doc 6209 says the transaction "will unpost" without a TC 130 already present on the module.

TC 796 is the automated version of TC 790's cross-file transfer, generated on its own once an individual overpays by at least $100 while the same taxpayer's business account is underpaid — no manual case action required.

TC 800 is a manually input credit for either ordinary withholding or excess FICA taxes — the human-keyed counterpart to the withholding code every W-2 filer already has on their transcript — and it exists specifically for the cases where a caseworker could not simply transcribe the credit from the return.

TC 807 takes back a withholding credit that already posted — and on a fiduciary return, Doc 6209 narrows what it can even reverse, a restriction easy to miss if you're reading the code the same way on every return type.

TC 820 is the debit half of a manual credit transfer — money deliberately moved off one module to another module, another account, or Excess Collections — and it carries a hard availability rule: the credit must already exist on Master File (the IRS’s central account-processing system) or the whole transaction fails to post.

TC 821 undoes an internal TC 826 offset — but when a module carries more than one same-day pair, the IRS's own procedure reads them in a fixed order, not however a practitioner happens to net them out.

TC 824 is the specific mechanism for moving an overpayment that TC 130's own refund freeze has been holding — and unlike an ordinary credit transfer, posting this one is itself what releases that freeze.

TC 848 moves a refund from one tax module to another, and it never travels alone — the counter-entry it requires is the single fact that tells you whether a transfer actually finished or is still hanging.

TC 849 is the destination side of a refund transfer — it debits the module receiving the refund and requires the matching TC 848 credit to take that same amount back out of the module it originally, and incorrectly, posted to.

TC 852 corrects a manual interest transfer that moved the wrong amount between modules — a narrow fix, but one worth recognizing on sight since it means the interest computation on both sides of the original transfer needs a second look, not just the correction amount itself.

TC 890 is the debit side of TC 790's cross-file transfer — it leaves an individual's module exactly as that overpayment moves over to satisfy a business account balance, and it will not post at all without a TC 130 hold already in place.

TC 899 reverses a prior refund offset, but which of its four Types posted decides whether the client is actually getting money back or watching an earlier refund get clawed back again.

TC 961 removes a representative from a module, but it can post from a simple revocation letter, from a new authorization silently superseding an old one, or — on a business account — from a payroll reporting agent losing its filing and deposit authority entirely.

TC 972 tells you a specific TC 971 marker was taken back — not that the notice or condition it recorded is resolved, and which of those two very different things actually happened depends entirely on the Action Code both transactions share.

TC 166 is the computer assessing a late-filing penalty with no human involved, which means nobody has yet considered whether the client had reasonable cause, and the IRS computes it on tax less prepayments, so a client who was owed a refund generally sees no penalty at all.

TC 186 is the deposit penalty the system assessed on its own, and it can arrive in two installments five cycles apart — so the first one a client sees is not always the whole charge, and an averaged version of it can post simply because nobody answered a notice.

TC 187 is the computer taking back a deposit penalty it assessed itself, when a payment lands in the right place or the tax behind it comes down — not because anyone granted relief, and not something a practitioner can ask for by name.

TC 190 is manually computed interest that leaves the account computing normally afterwards — the quiet alternative to restricted interest, and a code whose current use in the IRM is noticeably broader than the definition the IRS publishes for it.

TC 191 removes manually assessed interest without freezing the account, which makes it a lighter code in the interest family — and the published interest IRM never gives it a rule of its own, so you must read the chapter around it to find what governs it.

TC 197 is the computer walking back interest it had already assessed, usually because the tax underneath it came down — a bookkeeping consequence rather than a decision, and one the published IRM defines nowhere in general terms even though one narrow subsection names it.

TC 200 is a $50-per-failure penalty for not supplying a taxpayer identification number the IRS asked for — one of the few information reporting penalties Congress never indexed for inflation, and one with a real exception for errors that do not matter.

TC 201 removes the penalty for a missing taxpayer identification number, and the waiver it rests on weighs one factor heavily that has nothing to do with the failure itself — whether the same filer has been penalized before.

TC 238 is the computer charging an exempt organization for every day its return was late — and both dollar figures Document 6209 gives for it are base amounts frozen at 2015, which a practitioner quoting them today would understate by 20 to 23 percent.

TC 239 removes a computer-assessed Daily Delinquency Penalty on a late exempt-organization return — and it also appears for a reason that has nothing to do with relief, when a hand-entered penalty replaces the one the system already charged.

TC 240 has no meaning of its own — it assesses whichever penalty the three-digit reference number beside it identifies, and without that number a practitioner cannot tell an accuracy-related penalty from a late partnership return from a foreign reporting failure.

TC 241 has no fixed meaning of its own — it abates whichever penalty the reference number beside it identifies, which makes reading that number the difference between knowing what came off a client’s account and guessing.

TC 246 is a systemic penalty on a partnership or S-corporation return, and the reference number riding with it decides which penalty it is — a late return, an incomplete one, or a large partnership that filed on paper when it should have filed electronically.

TC 247 is the systemic abatement of a partnership or S-corporation return penalty, and Document 6209 ties it to something unexpected — a timely credit posting to the account, not a decision that the penalty was wrong.

TC 270 is a failure-to-pay penalty a person at the IRS computed by hand, and the act of posting it stops the computer from recomputing the penalty on that module (the IRS’s record of one return for one tax period) until a TC 272 removes the restriction — which is why a zero-dollar TC 270 is a meaningful entry rather than a clerical artifact.

TC 271 is a failure-to-pay penalty removed by a person rather than by the computer — and whether a single reason code rode along with it decides whether the module (the IRS’s record for one tax period within the account) keeps computing the penalty afterwards or stops dead, which is a bigger practical difference than the dollar amount.

TC 272 carries no money and does one thing — switches the failure-to-pay penalty computation back on after a manual entry froze it. On an account where the tax stayed unpaid, that can make the balance go up rather than down.

TC 276 is the computer charging a failure-to-pay penalty, and the rate on it is not fixed — it doubles ten days after the IRS gives a notice of intent to levy, which makes the date on the code as important as the amount beside it.

TC 277 is the computer removing a failure-to-pay penalty it assessed itself, with no caseworker involved — which means it is not evidence that anyone considered a relief request, and on 2020 and 2021 accounts it can be an automatic waiver nobody asked for.

TC 280 is the penalty for a payment that bounced, computed by hand — a charge First-Time Abate cannot reach, that oral explanations cannot remove, and whose rate structure has three tiers rather than a single percentage.

TC 281 removes a bounced-payment penalty, and the IRM assigns it a different penalty reason code depending on whose error caused the failure — naming the right one is most of the work, and it can post even on an account where no return has been filed.

TC 286 is a bounced-payment penalty the system charges automatically when a payment reversal posts — including, by the IRM’s own admission, in cases where the reversal code was used wrongly and the penalty should never have been assessed at all.

TC 287 is the system writing off a bounced-payment penalty on its own, but only when three specific account conditions line up at once — which makes it something to recognize on a transcript rather than something a practitioner can ever ask for.

TC 290 is the general-purpose adjustment assessment and one of the most common lines on any transcript — but a TC 290 for zero dollars is not a non-event, and in blocking series 96X it records a penalty relief request the IRS considered and refused (Doc 6209).

TC 291 is usually described as the reversal of a TC 290, and that description is too narrow — it can reduce the tax a taxpayer reported on their own original return, which makes it a code about what the liability now is rather than about undoing one prior adjustment.

TC 300 is the code that turns an examination or Appeals determination into an assessed liability — and unlike the ordinary adjustment code it looks like, it generally arrives through deficiency procedures or a written waiver of them under IRC 6213(d), which is what gives a client the rights they may already have used.

TC 301 removes tax an examination or Appeals put on — but it can also reach the original return and any data-processing adjustment, and the IRM sets a hard ceiling on it that tells a practitioner exactly how much relief the code was ever capable of delivering.

TC 310 is a 50 percent penalty on the Social Security and Medicare tax an employee never reported on their tips — assessed without deficiency procedures, and capable of being charged in a year the income tax statute has already closed.

TC 311 removes the tip-reporting penalty, and the IRM is unusually prescriptive about how to earn one — a written statement of every fact relied on, sworn under penalties of perjury when it answers a proposed assessment.

TC 320 is the 75 percent civil fraud penalty under IRC 6663 — not the accuracy-related penalty it is often mistaken for, and the one return-related penalty that carries no penalty reference number because it needs none.

TC 321 removes a civil fraud penalty in whole or in part. Doc 6209 also lists a second function for the code — releasing a restriction on the failure-to-pay penalty — and ties it to the fraud statute IRC 6663 replaced almost four decades ago, though Doc 6209’s own internal tables disagree on exactly which decades-old returns that covers.

TC 336 is interest the computer assessed because an examination adjustment posted — which makes it the interest code that tells you an exam, rather than a math error or a routine adjustment, is what created the balance.

TC 337 is the computer removing deficiency interest when an examination adjustment reverses — and because it reaches three different assessment codes rather than one, it routinely appears on accounts carrying no TC 336 at all.

TC 340 is interest a person at the IRS worked out by hand because the computer could not — which makes the figure beside it the one number on a transcript most worth recomputing before a client pays it, and the one the IRS itself keeps a written computation for.

TC 341 removes interest by hand, and it reaches four different assessment codes rather than just the TC 340 it is usually paired with — which means the amount that came off is only checkable by recomputing the whole module, and reasonable cause is not an argument that can produce one.

TC 342 is the zero-dollar transaction that switches automatic interest computation back on after a manual entry turned it off — and it cannot be input until someone retrieves the original workpaper and concludes the manual entry should never have been made.

TC 420 means a return has been assigned in Examination or Appeals, and it sets a freeze that — in the IRM’s own words — does not freeze the account; what it actually does is block the ordinary adjustment codes, which is why routine corrections stop working on a year under audit.

TC 424 is the earliest audit signal that appears on a transcript — a return has been requested for examination and pulled out of the selection pool — and it can post months before anyone contacts the taxpayer, or resolve without anyone contacting them at all.

TC 480 posts when an offer is deemed processable and starts the collection statute suspension that runs until the offer is decided — and the single most common error made with it is adding a year to that suspension, which the IRM tells its own employees not to do.

TC 500 suspends the collection statute for military service, but the code covers two quite different regimes and the closing code beside it decides which — and Document 6209 lists only two of the six closing codes the live IRM actually documents.

TC 520 is a single code covering two different freezes and a dozen different situations — bankruptcy, Tax Court, refund suits, collection due process — and only the two-digit closing code beside it says which, whether the collection statute stopped, and which IRS manual even applies.

TC 521 closes a litigation freeze because the underlying matter actually resolved — which is precisely what distinguishes it from the correction code the IRM tells its own staff to use instead, and why the two are not interchangeable even though both remove the same freeze.

TC 530 reports an account currently not collectible, but the code alone tells a practitioner almost nothing — the two-digit closing code beside it carries the entire meaning, and neither the code nor the status stops the collection statute or keeps a lien off the client’s record.

TC 582 records that a Notice of Federal Tax Lien was filed — but it posts days after the notice actually reached the recording office, it is not the date any deadline runs from, and on an individual account the same code carries a completely unrelated estate-tax meaning.

TC 583 removes a lien indicator, but it covers two legally different outcomes — a release, which says the lien is satisfied or unenforceable, and a withdrawal, which removes the public notice as though it had never been filed — and only the definer code says which one the client actually got.

TC 610 is the payment a taxpayer sent with their return, and its most useful property is what happens when it cannot post — it resequences invisibly for months before failing, which is why a client’s check can clear the bank and appear nowhere on their account.

TC 670 is any payment made after the return went in, and on an employment tax account the two-digit designated payment code riding with it decides whether the money reduced a responsible person’s personal exposure or did nothing for it at all.

TC 780 is the offer being accepted — the code a client has usually waited a year to see — and it brings two immediate effects worth warning them about first: interest and failure-to-pay stop computing, and every refund in the account is frozen for eight weeks.

TC 788 is the offer finished — every term met, the account released, the file closed — and despite sitting eight numbers above the acceptance code it does not reverse it; it requires the acceptance to still be standing in order to post at all.

TC 922 is the Automated Underreporter program marking a return for document matching — it is a status line carrying no money, and the process code sitting at the end of it is the only part that tells a practitioner whether a case is open, closed, or was never really a case at all.

TC 960 is the transaction that makes a power of attorney real on a tax module — it is the difference between a Form 2848 that was filed and one that actually causes copies of notices to reach the representative, and its absence is why practitioners find out about client problems late.

TC 976 records that a second return posted to a year that already had one — it is a filing event queued for a human to look at, not a decision about which return is right, and on an individual account it replaces the original return code rather than sitting beside it.

TC 977 records that an amended return posted, and nothing more — the dollar figure beside it is money the taxpayer sent, not the change to their liability, and reading it as the adjustment is the fastest way to quote a client a number that does not exist.

The federal rules for Trump Accounts (IRC §530A) — contributions, growth, and distributions — plus the state-by-state conformity library.

Browse the state-by-state library of how each state's own IRC conformity law treats Trump Account contributions, growth, and distributions.

Without a standalone 2026 bill, California would have taxed Trump Account growth annually; SB 180 conformed the state to the federal rule, with three California-specific modifications the federal statute does not have.

Side-by-side comparison of CP504 and LT11/Letter 1058/CP90/CP297 — what each one authorizes, the deadline for each, and how to tell them apart.

CP081B tells a business the IRS has payments or credits sitting on an account with no matching return filed — and the clock to actually get that money back as a refund is running out. Generally three years from the return's original due date, including extensions.

CP134R tells a business its federal tax deposits didn't match its return — in the business's favor. No response is required unless the business disagrees with the figures.

CP211A confirms the IRS approved a Form 8868 extension request — automatic for a Form 990-series filer who filed a complete request on time and paid any balance due, discretionary for a Form 5330 filer reporting excise taxes on an employee benefit plan. No response is required, but the notice does carry a new due date to file by.

CP30B tells you the IRS reduced an estimated tax penalty it had assessed, because the original amount exceeded what the law allows. If a refund is due to you, IRS.gov says you do not have to do anything at this time. If you owe a balance, pay it by the due date shown on your notice.

CP320B goes to a business already fighting an ERC disallowance under Letter 105-C or 106-C, with six months or less left on the two-year clock to sue for it. It flags a real option — Form 907, filed through the Document Upload Tool — but that option only works if the IRS signs it before the clock runs out, and the notice itself does not extend anything by just existing.

A digital CP575 is a downloadable confirmation of your EIN, available in Business Tax Account and accepted by banks the same way the original paper CP575 or a Letter 147C request has always been — except you can get it in minutes instead of waiting weeks for the IRS to mail a copy.

Letter 105-C tells a business the IRS is denying its entire Employee Retention Credit claim for a period — and starts a two-year clock, running from the date on the letter, to either appeal informally, sue in court, or lose the right to recover the credit at all.

Letter 106-C tells a business the IRS is denying part of its Employee Retention Credit claim — or all of the ERC while allowing other changes on the same return — and starts the same two-year suit clock as a full disallowance, running from this letter's own date.

Letter 6612 means the IRS is examining a return that claimed the Employee Retention Credit and is holding the credit until the audit is resolved. It asks for specific documentation, and the letter itself — not this page — states the actual response deadline.

The IRS Practitioner Priority Service phone number, hours, eligibility, and per-call limits for EAs, CPAs, and attorneys.

The Federal Tax Desk’s full practitioner resource library: downloadable cheat sheets and guides, plus every free reference tool on this site.

Route a dispute to Collection Due Process, the Equivalent Hearing, the Collection Appeals Program, an Offer in Compromise rejection appeal, or Audit Reconsideration in one pass, with the deadline and the IRC/IRM citation shown at every branch.

Route between IRC §6015 Innocent Spouse Relief (Form 8857) and IRC §6402 Injured Spouse Allocation (Form 8379) in one pass, with the IRC/Rev. Proc./IRM citation shown at every branch.

CP06 is an audit, not a matching notice — the IRS is holding part or all of your refund until you document the Premium Tax Credit you claimed. Treating it like a routine mismatch letter costs real time on a deadline that's already running.

CP11A is what CP11 becomes automatically the moment an EIC disallowance for a Social Security number, name, or date-of-birth mismatch is one of the math errors on the return — a different underlying problem than a routine recalculation, even though the letter looks nearly identical.

CP14I is CP14's IRA-specific sibling — a balance due from a missed required minimum distribution or an excess contribution, not the early-withdrawal penalty most practitioners assume. The payment deadline is identical to plain CP14; the underlying fix is not.

CP25 means the IRS recalculated your estimated tax payments and the difference was too small to bill or refund — genuinely no action required. The one thing worth knowing: disputing this kind of correction doesn't come with the formal abatement right other math-error notices carry.

CP39 means the IRS took a refund from you, your spouse, or a former spouse to pay a joint or spousal balance — not simply a refund moved to a different tax year. That distinction opens relief options a routine offset notice doesn't.

CP62 reports a payment applied to your account — but that isn't automatically good news. The same notice format covers a refund, a zero balance, and a real bill with a running deadline.

Letter 1153 proposes the Trust Fund Recovery Penalty against you personally under IRC §6672. You have 60 days (75 if mailed outside the US) to protest — miss it, and the penalty assesses.

Letter 2531 is the business-side inquiry that can precede Letter 2030 the same way CP2501 precedes CP2000 for individuals — but it runs under a different IRS program, uses its own response form, and its scope is narrower than "any business" implies.

Who publishes The Federal Tax Desk, what the CFP®/EA credentials mean, and what the site is not.

CP161 is the IRS’s business balance-due notice — and it is not always a penalty notice at all. What it actually demands, and why the penalty (if any) is never fixed in advance.

CP162 charges a partnership for filing on paper when electronic filing was required — a different penalty, under a different statute, than the late-filing penalty on CP162A.

CP162A charges a partnership or S corporation a per-owner, per-month penalty for filing late — up to 12 months of exposure, and relief that depends on which of the two entity types actually got the notice.

CP30 means the IRS charged you an estimated tax penalty larger than the one you figured yourself — and it usually shows up as a smaller refund, not a bill. What actually gets it reduced.

CP30A means the IRS already lowered or removed an estimated tax penalty you reported yourself — it is a review notice, not a bill, though a smaller balance can still be attached.

CP91 and CP298 are the same notice — one for individuals, one for businesses — warning that the IRS is about to start taking up to 15% of Social Security benefits every month. Each notice tells you about your right to appeal (CAP, or an Equivalent Hearing request if you had no earlier hearing on these periods). An earlier notice usually gave you the CDP hearing right.

Letter 2030 is CP2000's business counterpart — but only for corporations and estates/trusts, not partnerships or S corporations. Here is what actually differs from the individual notice, and what does not.

The IRS already filed a lien against your property. This letter is not the lien itself — it's the notice that starts a 30-day clock to challenge it, and that clock runs from the lien filing, not from the date on the envelope.

Letter 4883C asks you to prove a tax return filed under your name is really yours — but unlike some other IRS identity letters, it gives you no website to do that on. Verification happens by phone only, and that phone line is one of the hardest lines at the IRS to get through on.

Letter 5071C tells you the IRS is holding your tax return until you prove it's really you who filed it. It's one of the identity-verification letters that lets you finish the check online instead of only by phone or in person.

Letter 5747C will not accept a phone call or an online session as proof of who you are. It requires an in-person visit to an IRS Taxpayer Assistance Center, and it holds the return — and any refund — until that visit happens.

Letter 6330C asks you to confirm who you are and that you really filed your tax return — by phone, the same way as the related Letter 4883C. It has nothing to do with IRC §6330, a different IRS rule about seizing property to collect unpaid tax, even though the numbers match.

CP195B tells a business the IRS checked its filing and deposit history, found it clean enough to qualify for automatic penalty relief, and did not charge a penalty it otherwise would have. The IRS says AEP needs no action from the taxpayer — but it clears only three specific penalty types, and it is easy to mistake for the settlement notice that comes with it.

CP895(b) tells a business the IRS checked its filing and deposit history, found it clean enough to qualify for automatic penalty relief, and did not charge a penalty it otherwise would have. The IRS says AEP needs no action from the taxpayer — and the IRS's own source does not say what separates it from its close sibling, CP195B, which this page states plainly rather than guessing at.

CP95 is good news wearing the same envelope as every other IRS notice. It tells you the IRS checked your filing and payment history, found it clean enough to qualify for automatic penalty relief, and did not charge a penalty it otherwise would have. The IRS says AEP needs no action from you — just one thing worth reading closely about what it does not cover.

CP95(SP) is the companion notice to CP95 that the Procedural Update lists beside it. Both are automatic-penalty-relief notices, and the IRS says AEP needs no action from the taxpayer.

Route a penalty across AEP, First-Time Abate, and reasonable cause in one pass, with the IRM/IRC citation shown at every branch.

Browse the consumer hub of plain-English IRS notice and penalty guides.

The specific fix for a return that met every AEP requirement but never received the relief because of an IRS processing mistake — and how it differs from asking for First-Time Abate.

The IRS generally has ten years to collect a tax debt — how that clock works, what pauses it, and a free calculator to find your actual date.

Two questions to ask about any IRS letter — is it a bill or a request, and what does the code on it mean — plus a link to look up your exact letter.

Which penalty-relief path applies to you — Automatic Exemption from Penalty, First-Time Abate, or reasonable cause — and how to tell them apart.

Which of the IRS's phone lines is actually yours to call — general, identity verification, or practitioner-only — with realistic wait times for each.

The three most common reasons a refund stalls — an identity-verification letter, a review freeze, or an offset — and how to tell which one is yours.

The two different reasons a refund gets reduced — an IRS-internal offset or a Treasury Offset Program interception for a non-IRS debt — and who to call for each.

TC 150 is the transaction that turns a filed return into an assessed tax module (the IRS’s record of one return for one tax period) — nearly everything else on a transcript, from withholding credits to a refund, waits for this one debit to post first, and its date starts the collection-statute clock but does not set the assessment-statute date.

TC 570 holds a refund on the possibility of a liability the IRS has not yet finished pricing, and a second TC 570 posted before the first one clears is the one detail that turns an ordinary hold into a freeze that will not lift on its own.

TC 571 is the code that actually opens the door a TC 570 closed, but it only tells you the obstacle is gone — a separate transaction code, TC 846, is the one that tells you the refund is actually on its way.

TC 766 is a deliberately generic bucket code for refundable credits the IRS verified but hadn't yet posted — everything from a gasoline tax credit to a Regulated Investment Company credit can post under it, which is exactly why it should never be read as shorthand for any one specific credit.

TC 768 posts the Earned Income Credit exactly as claimed on the original return — a distinct code family from the generic TC 766, with its own reversal code and its own statutory refund-timing hold that has nothing to do with whether the credit itself is correct.

TC 806 is the credit that offsets a TC 150 assessment with whatever withholding a return claimed — the IRS allows it first and verifies it later against employer-filed data, which is exactly why a mismatch can surface as a frozen module months after the refund was supposed to arrive.

TC 810 stops a refund cold, and the reason code riding along with it — pre-filing notice, abusive shelter detection, a credit combination under review, or a frivolous-return screen — is the difference between a routine compliance check and a case the Taxpayer Advocate has flagged as running well over a year.

TC 811 reverses the -E freeze, but the field carrying the reversal amount is what actually decides whether a client gets their whole refund back or only part of it, and the public IRM never commits to a timeline for when that transaction posts.

TC 826 is the IRS's own internal engine for paying one of a taxpayer's balances with another year's refund — an entirely internal move made under IRC §6402(a) that never touches Treasury's Offset Program, and mistaking it for that program sends a dispute to the wrong agency.

TC 846 is the code most taxpayers are actually looking for when they pull a transcript, but the date sitting next to it is the day the IRS scheduled the release — not a promise about the day the money lands in a bank account.

TC 898 means the refund never made it past Treasury — the Bureau of the Fiscal Service intercepted it for a debt owed to someone other than the IRS, and disputing the wrong agency wastes the call.

TC 971 is one of the few codes on a transcript with no fixed meaning of its own — it is a generic wrapper for a companion Action Code that decides what actually happened, from a mailed notice to a frozen refund to nothing more than a stopped direct deposit.

Route a case across Guaranteed IA, Simple Payment Plan, Non-Streamlined IA, PPIA, CNC, and OIC in one pass, with the IRM/IRC citation shown at every branch.

TC 130 freezes an entire account from refunding — not just the return in front of you — because of a liability the IRS says exists somewhere else, and which of two very different release codes posts next tells you whether that money is coming back or already gone.

TC 131 reverses the TC 130 freeze and lets a held refund flow again — but only if the reversal is a true release, because the freeze's other exit, TC 824, ends the same freeze by spending the money instead of returning it.

TC 160 is a Failure to File penalty an Audit or Collection employee computed and posted by hand — distinct from the computer-generated version of the identical penalty — and which one is on the transcript determines whether TC 161 or TC 162 is the code to watch for next.

TC 161 is the code that actually reduces or removes a Failure to File penalty already on the account — and it covers four common situations that all look identical on a transcript: First-Time Abate, a reasonable-cause claim, a manual Automatic Exemption from Penalty (AEP) grant, and a penalty that should never have posted at all.

TC 162 does not reduce a Failure to File penalty by a single dollar — it removes the restriction a manual TC 160 or TC 161 leaves behind, so the system can compute the penalty on its own again the next time something on the account changes.

TC 167 removes a computer-assessed Failure to File penalty automatically when the return’s due date or the tax due at that date changes — a recalculation, not a reasonable-cause or First-Time Abate determination, and reading it as relief already granted can mean missing abatement the client is still owed.

TC 170 records an underpayment-of-estimated-tax penalty — and the fact worth knowing before anything else is what doesn't remove it: First-Time Abate does not reach this penalty, and reasonable cause alone does not remove it. Whether it was self-assessed on Form 2210, 2210-F, or 2220, or manually assessed by the IRS, decides which of the narrow grounds applies.

TC 171 is the code that means an IRS employee manually reduced or removed an estimated tax penalty — and the penalty reason code behind it reveals exactly which of a handful of narrow grounds actually worked.

TC 176 is Master File (the IRS’s central account-processing system) automatically assessing the estimated tax penalty, posted with no doc code and no human review behind it — which means the fastest way to reduce one is usually to fix the payment or withholding data feeding the computer’s math, not to argue relief the ES penalty was never eligible for.

TC 177 is Master File (the IRS’s central account-processing system) automatically reversing a TC 176 assessment, triggered by the same payment and withholding corrections that created the penalty in the first place — a systemic fix, not a relief argument, and knowing the difference keeps a practitioner from filing a waiver claim nobody needs to evaluate.

TC 180 assesses a penalty for late or short federal tax deposits on employment and excise tax accounts — and three separate, verifiable mechanisms can reduce or eliminate it, from a safe harbor that should have stopped the assessment in the first place to a First-Time Abate rule that names this exact penalty by statute.

TC 181 removes a Failure to Deposit penalty in whole or in part — which of four common routes gets there (a safe-harbor correction, First-Time Abate, reasonable cause, or a manual Automatic Exemption from Penalty grant) changes both how much comes off and how the request should actually be filed.

CP01A isn't a warning that something is wrong right now — it's an annual PIN reissuance that, entered incorrectly, is what actually gets an otherwise-clean return rejected or delayed.

CP05 puts a refund on hold and asks the taxpayer to do nothing at all — but its follow-up notice carries a real deadline, and conflating the two is where clients lose money.

CP05A isn't the vague refund hold that came before it — it's a specific document request with its own deadline, and answering it like CP05 just costs the client months.

CP11 isn't a proposal — it's a completed assessment, and the 60-day window to force the IRS to undo it runs from the notice date, not from when a client opens the mail.

CP12 reads like good news — a bigger or unexpected refund — but it starts the same 60-day math-error clock that governs a balance-due notice, and that clock doesn't pause for good news.

CP16 bundles two separate IRS actions into one notice — a math-error correction and a refund offset — and only one of them is disputable the way most practitioners assume.

CP21A says the IRS adjusted your return and the change left a balance due. The notice does not say who started the change.

CP21B reads like routine good news — a refund is coming — but confirming the amount and origin match what you actually filed is what keeps that read from being wrong.

CP22A means the IRS posted a change and a balance is now due — but the reason a taxpayer gets a CP22A instead of a CP21A has nothing to do with who asked for the change.

CP23 opens with the exact same sentence as CP24, but don't assume it carries the same rights as an ordinary math-error notice — Congress carved the automatic 60-day abatement right out of this one, and a client who assumes otherwise loses the response window instead of protecting it.

CP40 means the IRS handed your account to a private company — and that single fact makes it one of the easiest genuine IRS notices to mistake for a scam, and one of the easiest scams to mistake for the real thing.

CP49 says the IRS already took your refund and applied it to a debt you owe them — the money has moved, so the only real question left is whether the debt itself is right.

CP501 is the IRS's first reminder on an unpaid balance, not a new notice and demand — but the statutory lien it describes already exists whether or not you've noticed.

CP503 is labeled the IRS's second reminder, but it borrows its lien warning almost word-for-word from the first notice and grants no levy authority at all — the actual escalation is still one letter away.

CP521 is a routine monthly reminder, not a warning notice — but ignoring it is exactly how a client's installment agreement ends up on the CP523 termination track.

CP60 doesn't touch your return at all — it reverses a payment the IRS decides was posted to the wrong account, and there's no §6213(b)-style right forcing them to put it back.

CP71C is a balance-due notice that says it requires immediate attention. It carries a passport warning, and the IRS says it may file a Notice of Federal Tax Lien if the balance stays unpaid and no payment plan is in place.

CP75 isn't a computer-matching letter like CP2000 — it's a real audit of the specific credits on your return, and the IRS is holding your refund until you prove you qualify.

LT16 sounds like a levy notice and reads like one, but its own printed language admits the actual Notice of Intent to Levy hasn't been issued yet.

Browse the Transaction Code Library index of practitioner reference pages by TC code.

TC 234 assesses a per-day penalty for a late exempt-organization return under IRC §6652(c), and First-Time Abate cannot touch it: $25 a day, up to the lesser of $13,000 or 5% of gross receipts, for returns due in 2026 (for receipts above $1,309,500: $130 a day, up to $65,000). Reasonable cause is the only relief avenue, a fact worth knowing before defaulting to the playbook that works for most other penalties.

TC 235 abates a Daily Delinquency Penalty assessed on an exempt-organization return — and because First-Time Abate does not reach this penalty, every abatement has to be won on reasonable cause alone.

TC 360 adds the IRS’s own out-of-pocket lien and collection costs to a client’s balance — a fourth kind of charge on the account that is neither tax, penalty, nor interest, and that a discharged liability does not automatically erase.

TC 361 reverses a lien or collection-cost fee assessed under TC 360 — but only when the IRS abates the underlying tax in full and the liability wasn’t the taxpayer’s fault to begin with. A negotiated-down audit result doesn’t qualify, even at a zero balance.

TC 470 freezes collection or notices while a claim is worked, but what it actually holds — and for how long — depends entirely on a closing code most transcripts never explain.

TC 481 ends a pending Offer in Compromise, extends two statute clocks on two different rules — the collection statute resumes on the TC 481 date, which on an unappealed rejection posted on or after 2/2/2004 already includes the 30 days, and the assessment statute gets the pending time plus a full extra year — and opens a 30-day window for the taxpayer to appeal the rejection itself.

TC 482 ends a withdrawn or terminated Offer in Compromise and carries the same one-year assessment-statute extension as a rejection.

TC 488 places a business, trust, or estate module into collection status 14 — and its one IRM-documented use, an estate’s IRC 6166 payment-deferral election, actually suspends the collection statute (when all the tax is deferred) rather than leaving it running, the opposite of the ordinary Installment Agreement rule this code is easy to mistake it for.

TC 489 ends the status-14 deferral TC 488 created — for the one use IRM text actually documents, a Form 706 estate’s IRC 6166 election defaulting — and resumes the collection statute the day after its own date, ten full years when the election deferred all the tax.

TC 528 ends a collection stay at status 41 or 42 and puts the account back wherever it was before the stay began. The stay itself most likely does not suspend the collection statute — status 41 and 42 are not among the IRS’s listed statute-suspending events — even though IRM 5.19.1 does not document TC 528 or the stay itself.

TC 531 puts an account back into active collection after a Currently Not Collectible determination — and the collection statute never stopped running while it was gone.

TC 534 writes off one assessment inside an account whose collection statute expired — and it is the transcript entry most likely to be confused with a full-account statute closeout that has not actually happened.

TC 537 ends Currently Not Collectible status (the IRS paused collecting) automatically, so collection can start again with no review of ability to pay — and that automation is what separates it from a manual CNC reversal.

TC 560 records a signed Form 872 extending the assessment statute — the deadline for the IRS to bill more, not the deadline to collect what is already billed, and confusing the two is the single most consequential statute mistake a practitioner can make.

TC 860 reinstates a balance the IRS abated by clerical mistake, even after the statute has otherwise run — a narrow reversal power with a sharp legal line that determines whether it applies at all.

A CP14 is the IRS formally demanding payment of tax it has already assessed. It is the opening move of the collection sequence, and the deadline printed on it does something specific that most taxpayers miss.

A CP24 says the IRS recalculated your estimated tax payments and found money in your favor. It is the notice practitioners are least likely to read closely and the one most likely to be reporting a payment that posted somewhere it should not have.

A CP53E says the IRS owes you a refund it cannot deposit. It asks you to enter banking information, it may carry a QR code, and it looks exactly like a phishing attempt — which is why roughly 1.4 million of them drew a Taxpayer Advocate warning and Congressional attention.

LT11, Letter 1058, CP90, and CP297 are the same notice under four labels. This is the one that actually authorizes the IRS to take wages and bank accounts — and the one that opens a 30-day window for Collection Due Process rights that expire with it.

Browse the IRS Notice Library index of practitioner reference pages by notice code.

The IRS found a mismatch between what you reported and what a third party told them. Here is what the notice actually authorizes, what triggered it, and the real next step.

CP2501 is the IRS asking a question before it proposes anything. It can turn into a CP2000 if you don't answer, but responding well here can stop that from happening at all.

A CP3219A is the Statutory Notice of Deficiency. It starts a 90-day clock to petition the Tax Court that no one at the IRS can extend, that runs from the mailing date, and that ends the case if it expires.

CP504 is a real IRS notice with a real 30-day clock — a levy warning that authorizes far less than most people, including some practitioners, assume it does.

CP523 threatens to terminate your installment agreement and levy your wages or bank accounts — but the notice itself never mentions the hearing right most practitioners reach for first.

The compliance cards for FTD’s tools in one place, to record your firm’s review of each tool. Not a tool itself.

Check Hardship Currently Not Collectible eligibility per IRM 5.16.1.2.9 — income vs. allowable expenses and net asset equity.

Paste an IRS Account Transcript, Wage & Income Transcript, Return Transcript, or Record of Account Transcript and get every transaction code or income document, with the plain-English meaning and IRM citation for each.

Turn a pasted Wage & Income Transcript into a populated Form 433 disposable-income estimate under the IRS Collection Financial Standards.

The site homepage — links to every calculator, the IRS Notice Library, the TC Codes Library, and the taxpayer guides.

Calculate the Collection Statute Expiration Date on any IRS liability, with every tolling event shown.

Look up a transaction code and get its plain-English meaning, next action, and IRM citation.

Size a Simple Payment Plan, Guaranteed, or Simple Payment Plan (Business Trust Fund) installment agreement per IRM 5.14.

Run the IRS reasonable-collection-potential formula to test offer-in-compromise viability.

Check First-Time Abate and Automatic Exemption from Penalty eligibility, and rank reasonable-cause arguments.

Calculate your Section 199A qualified business income (QBI) deduction, including SSTB, W-2 wage, and UBIA limits.

Build a defensible reasonable-compensation range by profession and income.

See what reclaiming your research hours is worth to your practice.

Find the income level where an S-corp election beats sole-proprietor self-employment tax.

The Federal Tax Desk subscriber terms of service.