TC 539: Reversal of TC 538

What the code actually does

IRS Document 6209 (the IRS's reference guide to its data-processing codes) defines TC 539 as the reversal code for TC 538: "Trust Fund Recovery Penalty Cases... Reverses TC 538 in whole or in part, multiple TCs 538 may be reversed with a TC 539 with the same date." That last detail matters — if several TC 538 credits posted on the same date, a single TC 539 can unwind all of them together, so a TC 539 amount does not always correspond to just one prior TC 538 entry.

The code has its own unposting guardrails: it will unpost if it attempts to post to a module (the record for one tax type and period) with no prior TC 538, if its date does not match the TC 538(s) it is reversing, or if the TC 539 amount exceeds the total of those prior TC 538 postings. Each condition exists to keep the reversal tightly bound to a real, matching prior credit rather than functioning as a free-standing debit.

Why the IRS reverses a TFRP cross-reference credit

Since TC 538 represents a responsible individual's IRC §6672 payment mirrored onto the business's employment-tax module from IMF (Individual Master File) to BMF (Business Master File), TC 539 follows when the IRS reverses or refunds the individual's own payment (a bounced check, a misapplied payment later corrected), as IRM 5.19.14.3.5 directs.

IRM 5.19.14.3.5 governs the reversal the same way it governs the original TC 538 posting — the cross-reference relationship it describes ("TC 241 RN 697 from BMF to IMF, TC 241 RN 699 from IMF to IMF, and TC 538 from IMF to BMF") runs in both directions, and a TC 539 is how the IMF-to-BMF leg gets unwound when the underlying payment relationship no longer holds.

What this means for the business's account

A TC 539 means a credit the business's module was previously given — because a responsible individual's own TFRP payment had been mirrored there — is being taken back. This is not the business incurring a new liability from its own conduct; it reflects a change on the responsible-person side of the relationship that the cross-reference mechanism is now correcting on the business side too.

Before assuming the business simply owes more money, find out why the underlying TC 538 was reversed. If the responsible person's payment bounced or was refunded, the trust-fund liability the credit had offset is genuinely still outstanding. If instead the reversal reflects a corrected misapplication, the business's true balance may be unaffected once the correction is fully worked through.

What people mistake TC 539 for

TC 539 should not be read as evidence the business made an error or failed to pay something it owed — the code only reverses a CROSS-REFERENCE credit that originated from someone else's payment, not from the business's own compliance history. Treating a TC 539 as a red flag on the business's own conduct misreads what the credit it reverses actually represented.

It is also not the same as a general Trust Fund Recovery Penalty abatement on a responsible individual's own MFT (Master File Tax account type) 55 account — that runs through different transaction codes on that person's module, including TC 241 when the cross-reference runs BMF-to-IMF or IMF-to-IMF rather than IMF-to-BMF. TC 539 operates specifically on the BUSINESS's module, undoing the mirrored effect of a payment relationship, not the underlying personal assessment itself — and a practitioner who conflates the two directions of the cross-reference risks describing the wrong account as having been corrected.

What to do next

Find out why the underlying TC 538 was reversed before advising the business on what it now owes — a bounced payment, a refund, or a correction each point to a different real-world outcome.

Check whether the responsible individual's own MFT 55 assessment changed at the same time, since the two accounts are meant to move together under the cross-reference mechanism.

Confirm the TC 539 date and amount match the TC 538 postings it claims to reverse — Document 6209's own unposting conditions mean a mismatch here signals a data problem worth escalating.

Review the client’s complete account history with the IRS Transcript Decoder to see the full TC 538/539 cross-reference history alongside the responsible person's own account before describing the trust-fund balance as settled either way.