TC 826: Overpayment Applied to Another Tax Debt
By Forrest Baumhover, CFP®, EA · Last verified August 28, 2026
TC 826 is Master File's own 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.
What the code actually does
TC 826 is a debit — it posts to the tax module the overpayment came from, in the amount the computer took away, and its own definition in IRS Document 6209 is specific about where that money goes: "An ECC [Enterprise Computing Center, the IRS's centralized data-processing site] computer generated debit for the amount of overpayment credit transferred to another tax module within this taxpayer's account." The phrase worth underlining is "within this taxpayer's account." Nothing about TC 826 sends money outside the IRS or to any other taxpayer — it moves a credit from one of this taxpayer's own modules to another one of this taxpayer's own modules that has a balance due.
The credit side of the same posting is TC 706, and Doc 6209 describes the mechanism plainly: "Before generating a refund, the computer analyzes all Tax Modules in the account and offsets the credit to any Tax Module with a balance past due." That is the whole engine — every time Master File is about to release a refund, it checks the rest of that taxpayer's account first, individual, business, or Non-Master File alike. Per IRM 21.4.6.4.1: "A refund offset to an outstanding IMF, BMF, or NMF tax debt is referred to as a tax offset. Tax offsets appear on a tax module as: Transaction Code (TC) 820, manual credit transfer; TC 826, computer-generated tax offset." TC 820 is the same outcome keyed in by an employee; TC 826 is the identical outcome the computer reaches on its own, which is why a clean, fully-paid current return can still lose part of its refund to an old balance sitting on a different tax period or a different tax type under the same taxpayer.
Where the authority comes from — and why it isn't TOP
The statutory basis for TC 826 is narrower than it might look next to its counterpart. IRM 21.4.6.2 states it directly: "Under Internal Revenue Code IRC 6402(a), the IRS may apply a taxpayer's overpayment, including interest, to any outstanding federal tax debt, and shall refund any remaining balance subject to subsections (c), (d), (e), and (f)." Subsection (a) is the whole of TC 826's authority — an IRS debt, applied by the IRS, to an IRS record.
Those other subsections the IRM cites — (c) through (f) — are what generate TC 898 instead: child support, other federal agency debt, state income tax, and unemployment compensation, all routed through Treasury's Bureau of the Fiscal Service rather than handled internally. The same IRM section confirms BFS enters the picture only for that second group: "Refund offsets to child support, TOP debts, State income tax obligations, and Unemployment Compensation debts are handled by the Treasury's Bureau of the Fiscal Service, (BFS) formerly Financial Management Service (FMS), through the Treasury Offset Program." A TC 826 never reaches that agency at all — the whole transaction stays inside the IRS's own systems from posting to resolution.
How it gets reversed
The reversal code is TC 821, and Doc 6209 ties it to TC 826 by transaction date: "Reverses the generated TC 826 overpayment credit transferred in whole or in part by crediting the tax module. Transaction date must match TC 826 date." A TC 821 posting means the internal offset is being undone, in whole or in part — the credit that moved to the other module is moving back, typically because the liability that justified taking it turned out to be wrong, already resolved, or reduced through an abatement on the module that received it.
Reversal does not by itself mean a new refund check is coming. Once the credit is back on the original module, whether it goes out as a refund or gets applied somewhere else again depends on the rest of that module's posture at the time — the same computer analysis Doc 6209 describes for TC 826 in the first place runs again before anything is actually released.
What this means for your refund
If TC 826 shows up on a transcript, the IRS has already used part or all of an overpayment to pay down a balance somewhere else on the same taxpayer's own IRS record — not a state, not a private creditor, not a federal agency outside the IRS. The dollar amount next to the code is what got moved; the code itself does not say which other year or account it went to, so confirming that takes pulling the module it actually landed on.
This is also good news in one specific sense: because the debt is internal, the dispute channel is the same agency that sent the notice. There is no separate outside creditor to track down. To see what TC 826 and the codes around it mean on an actual account, try the IRS Transcript Decoder.
The practitioner's actual next step
Confirm the other module's liability before advising the client it's correct — verify the balance TC 826 paid down is actually owed, actually still open, and actually attached to the right taxpayer identification number before treating the offset as final. An old assessment that was abated, already paid, or posted to the wrong module can still trigger a TC 826 before the error is caught.
If the return was filed jointly and the debt behind the offset belongs to only one spouse, Form 8379 reaches this fact pattern directly. Per IRM 21.4.6.5.6.5, Injured Spouse Refund - Tax Offset: "A manual refund is required on all injured spouse refunds of tax offsets to prevent the credit from offsetting back to the same tax debt," and the refund is issued "in 'one name only'" unless the taxpayer checked the box requesting both names — a materially different mechanic than the automated TC 766 reversal that unwinds a TOP offset, which is why the two injured-spouse subsections are worth reading as their own tracks rather than one shared procedure.
What TC 826 gets confused with
The easiest slip is with TC 130's own release codes — TC 824, one digit off from TC 826, and covered on TC 130's page. Doc 6209 is specific that TC 824 "transfers overpayment credits frozen by TC 130 Account Refund Freeze" and, in doing so, "releases TC 130 Account Refund Freeze." TC 824 exists only to end a freeze that already exists. TC 826 needs no freeze at all — it is the routine, always-running internal offset engine that checks every account before a refund goes out, freeze or no freeze, and a practitioner scanning a transcript for a 4 versus a 6 can land on the wrong explanation for why money moved.
The other pairing is TC 898 itself, since both codes describe a refund shrinking because of a debt. They run on different statutory subsections, different agencies, and different injured-spouse mechanics, covered on that page. CP49, the IRS notice that most often accompanies a TC 826-style offset, is explicit in its own text that it is not the notice a TOP offset generates — a client holding a CP49 has an internal IRS balance to sort out, not a Treasury Offset Program dispute.