TC 876: Interest on Overpayment Transferred to BMF

What the code actually does

IRS Document 6209 defines TC 876 precisely: "Posts interest generated on an IMF overpayment transferred to a BMF tax module in debit (underpaid) status. Corresponding credit is TC 756." (A tax module is the IRS’s record for one tax period within an account.) The Individual Master File (IMF) holds individual income tax accounts; the Business Master File (BMF) holds business accounts. TC 876 is the debit side of moving interest earned on an individual overpayment across that boundary to pay down a balance sitting on a business account.

The corresponding credit, TC 756, lands on the BMF module and, per Doc 6209's own entry for that code, "credits module with amount of interest or amount of underpayment whichever is less" — meaning the transfer cannot exceed either the interest available or the balance actually owed, whichever figure is smaller.

Why moving between master files needs its own code family

IRM 20.2.4.7.6 lists TC 876 directly inside its table of Master File and Systemic Offsets, alongside its within-file counterpart: "TC 856 — Transfer overpayment interest out of a module. TC 736 — Transfer overpayment interest into a module. TC 876 — Debit of overpayment interest from an IMF module to a BMF module. TC 756 — Credit of overpayment interest from an IMF module to a BMF module." The table treats these as parallel entries, not variations of one code — TC 856 handles a transfer that stays inside a single master file, while TC 876 exists specifically because IMF and BMF are separate systems that need their own dedicated posting codes to move money (and the interest on it) between them.

That separation matters procedurally: a transfer that never leaves one master file uses one code family, and a transfer that crosses from an individual's account to a business account uses a different one, even though the underlying action — taking interest earned on an overpayment and applying it to a balance due elsewhere — is conceptually identical in both cases.

Its principal counterpart

TC 876 only moves the interest. The underlying overpayment itself crosses the same IMF-to-BMF boundary using a separate code, TC 896, which Doc 6209 describes as being "used to reflect an offset to IRAF (MFT 29) and Shared Responsibility Payment (MFT 35) accounts and from IMF to BMF." The same split that exists within one master file — a principal code and a separate interest code for the same offset event — carries over to the cross-file version: TC 896 (or its own numbered family) moves the overpayment dollars, and TC 876 moves the interest those dollars earned.

TC 876 and TC 896 do not always appear together. The same "whichever is less" capping rule that governs the credit side of this transfer (see TC 756's own page) means principal and interest can each move independently, depending on how much of the BMF module's balance still needs covering by the time each piece is ready to transfer — the same way TC 856 and TC 826 can each post on their own within a single master file. Seeing TC 876 without a nearby TC 896 does not by itself signal a missing step; it can simply mean the principal side of the offset was already handled another way, or wasn't needed at all.

What TC 876 gets confused with

It gets confused with TC 856, since both codes describe overpayment interest being taken from one module to pay a balance somewhere else on the same taxpayer's account. The distinguishing fact is which master file is involved on each end: TC 856 never leaves a single master file, while TC 876 exists only for the interest half of a transfer that crosses from IMF to BMF. A practitioner who sees TC 876 and reasons about it using TC 856's rules is applying the wrong code family's logic to a cross-file transaction.

It also gets confused with TC 896, its own principal-side counterpart. TC 896 moves the overpayment itself across the IMF-to-BMF boundary; TC 876 moves only the interest that overpayment had already earned. They describe two different dollar figures tied to the same underlying event, not two names for the same transaction.

The practitioner's actual next step

Confirm which master file each module involved actually sits on before treating a TC 876 the way you would a TC 856 — the cross-file mechanics and the codes that document them are different, even though the underlying concept is the same.

Check whether a matching TC 896 also appears on the same modules — the two often travel together, but do not have to, so its absence alone does not mean the transfer is incomplete or that a step was missed.

Because TC 756 credits "the amount of interest or amount of underpayment whichever is less," verify the actual balance due on the BMF module before assuming the full interest amount transferred — the credited figure may be capped by the smaller of the two numbers.