TC 840: Manual Refund

What the code actually does

Document 6209 titles TC 840 "Manual Refund" and describes it precisely: "Designates a manual refund was issued prior to or after a return (TC 150) has posted." Unlike this batch's TC 720, which despite its numeric neighborhood is a credit for money coming back in, TC 840 is a debit — an actual refund leaving the module (the IRS's internal record of one tax period on one account), whether the underlying return has already posted or not.

Doc 6209 also describes what happens when the return has not yet posted: "If return has not posted, freeze module from refunding or offsetting out. Refer to Freeze Code -X in Section 8." A manual refund issued ahead of the return posting locks the module down from moving anything else until that freeze clears.

Manual versus systemic: the check every practitioner should run first

The current IRM states the distinction as a direct research instruction. IRM 21.4.1.4.2, Return/Refund Located, says: "Research CC IMFOLT, CC BMFOLT and CC TXMOD to determine whether a refund was issued systemically (TC 846) or manually (TC 840). A TC 846 will appear on CC IMFOLT approximately one cycle before CC TXMOD." TC 846 is the computer's own refund-issuance code; TC 840 is what appears instead when an employee had to complete the refund by hand, whether because of a freeze, a manual adjustment, or a case that could not move through the automated pipeline.

That distinction matters beyond bookkeeping. A manual refund usually means a human being made a specific determination about the account before the money went out — which is exactly why a TC 840 is worth tracing back to whatever review or adjustment triggered it, rather than treating it as functionally identical to an ordinary systemic refund.

The "Dummy TC 840" trap, and the actual refund-trace deadline

IRM 21.4.1.4.4, Refund Issued but Lost, Stolen, Destroyed or Not Received, carries a specific caution that changes what a TC 840 on a transcript can mean: "If TC 840 carries a blocking series and serial number 9XXXX series with a Julian date less than 400, it is a 'Dummy TC 840' and no actual check has been issued." In other words, the posting of TC 840 by itself is not proof money actually moved — the blocking series and serial number have to be checked before assuming a real refund went out.

The same subsection supplies the concrete window for tracing a refund that genuinely was issued but never received: "10 calendar days (30 calendar days if it's a foreign address) from the 'RFND-PAY-DATE' on CC IMFOLT or the 'RFND-PYMT-DT' on CC TXMOD" before a Form 3911 trace request makes sense. Starting a trace before that window runs, or skipping the dummy-entry check first, can send a client down the wrong path entirely.

What TC 840 gets confused with

The unavoidable mix-up is with TC 846, the systemic refund code. Both represent a refund leaving the module, and IRM 21.4.1.4.2's own guidance exists specifically because the two need to be told apart by checking IDRS command codes rather than assumed from context. A TC 846 posting roughly a cycle ahead of TXMOD, versus a TC 840 with no such lead time, is the practical tell.

It also gets confused with a genuine, completed refund when it is actually a "Dummy TC 840" per the pattern above — the code alone does not distinguish a real disbursement from a placeholder entry with no check behind it. Treating every TC 840 as proof money left the building, without checking the blocking series and Julian date, is the specific error the current IRM is warning against.

A TC 840 refund can also resurface later as a TC 720 — the credit code that posts when a refund already sent comes back, whether a bank rejects a questionable deposit or the taxpayer repays an erroneous refund on demand. Per IRM 21.5.6.4.31, that trigger applies to either kind of refund, systemic or manual, so a TC 720 appearing after this one is not automatically a second, unrelated event — it is very often the same TC 840 money reversing course, and worth checking before treating it as a new issue.

What this means for your refund

If TC 840 appears on your transcript instead of TC 846, it means an IRS employee issued your refund manually rather than letting it process automatically — often because something about your return or account needed a specific review or adjustment first. That is not inherently a bad sign; it simply means a person, not just the system, handled your refund.

If you have not received the refund shown by a TC 840, the IRS generally will not start a trace until 10 calendar days have passed from the payment date on your transcript (30 days if you have a foreign address), so checking that date first can save you a call that goes nowhere. If your transcript shows a TC 840 but you are not sure a refund was actually sent, a tax professional can check the specific entry details behind it before you assume the money is on its way.

The practitioner's actual next step

Check the blocking series and serial number before telling a client a manual refund was issued — a 9XXXX blocking series with a Julian date under 400 is a "Dummy TC 840" under the current IRM, meaning no check was ever actually cut.

Confirm the RFND-PAY-DATE or RFND-PYMT-DT before initiating a refund trace, and hold off until the 10-day (or 30-day foreign) window has run — filing Form 3911 before that window closes is treated as premature.

Once a genuine manual refund is confirmed, trace back to what triggered it — a manual refund almost always means a specific account condition or adjustment required human handling, and that underlying cause is usually the more useful thing to explain to the client than the transaction code itself.