TC 890: Manual Transfer of Overpayment Credits to BMF

What the code actually does

TC 890 moves money out of the IRS's account system for individuals (the Individual Master File, or IMF) and into its account system for businesses (the Business Master File, or BMF) or an Individual Retirement Account File (IRAF) record. IRS Document 6209, Section 8A defines TC 890 as the "manual transfer of overpayment credits from the IMF for application to the BMF or IRAF." It is the debit half of the same posting event TC 790 documents in full — Doc 6209 states directly that "the corresponding credit is TC 790."

Reading this module in isolation, without its TC 790 counterpart on the business side, only tells half the story: the overpayment left this module, but where it actually went and why requires checking the receiving module too, since the debit entry alone carries no information about the destination or the business liability it satisfied.

The same gates apply on the debit side

Doc 6209 repeats the identical TC 130 precondition documented on the TC 790 page: "will unpost unless TC 130 is present." A TC 890 attempted without a TC 130 collection hold already on the account will not post at all, regardless of how legitimate or well-documented the underlying transfer request is. Because both codes are one transaction, the TC 130 precondition is not separately enforced on each side — it is the same gate, checked once, that governs whether this cross-file mechanism can operate on a given account at all.

The exclusion list, though, is close but not identical — TC 890 does not apply "to taxpayers filing Form 990, 990C, 990PF, 990T, 1041, 1041A, 1065, 1120, 4720 or 5227," while TC 790's own exclusion list on the credit side adds two more forms, 706 and 709, that TC 890's entry does not mention. A practitioner checking whether either mechanism applies to an estate or gift-tax filer should check the specific code's own list rather than assuming the two are interchangeable.

What a client sees on the individual side

A taxpayer whose own overpayment funded a business balance due will see their individual module debited by this amount with no refund arriving — the money did not disappear or go to the wrong party, it satisfied a business liability the same taxpayer is personally responsible for, most often as a sole proprietor or a responsible individual on an employment tax matter.

Confirm the taxpayer actually consented to or was properly notified of this application before treating it as routine — a cross-file transfer moving a personal refund toward a business debt is a significant taxpayer-facing event, not a background accounting adjustment the client can be expected to already understand.

What TC 890 gets confused with

It gets confused with TC 824, which also releases a TC 130 freeze but transfers credit within the same context rather than specifically bridging IMF to BMF/IRAF.

It gets confused with a straightforward refund reduction for an unrelated reason. TC 890's specific purpose is funding a business account, not a general offset against some other individual liability.

It gets confused with TC 896, which shares TC 890's reversal code (TC 892) but represents a different offset mechanism — IRAF and Shared Responsibility Payment accounts under a computer-generated process rather than this manual IMF-to-BMF transfer.

The practitioner's actual next step

Confirm a TC 130 is present on the module before expecting a TC 890 to post — its absence is the most common reason this transfer fails.

Trace the matching TC 790 credit on the business account to confirm the transfer's destination and amount.

Check the exclusion list before assuming this mechanism applies to a given entity type.

Verify the taxpayer understood their individual overpayment was being applied to a business liability, given the significance of that outcome relative to receiving a refund.