TC 846: Refund Issued
By Forrest Baumhover, CFP®, EA · Last verified August 28, 2026
TC 846 is the code most taxpayers are actually looking for when they pull a transcript, but the date sitting next to it is the day the IRS scheduled the release — not a promise about the day the money lands in a bank account.
What the code actually does
TC 846 is a generated transaction — Master File posts it on its own once a tax module nets to an overpayment and no freeze is blocking the refund, without an employee keying anything in. Document 6209 describes it plainly: it "[d]ebits the tax module for the amount of overpaid tax (plus applicable interest) to be refunded to the taxpayer." The Taxpayer Advocate Service puts the same fact in plainer language: TC 846 "[r]epresents the issuance of a taxpayer's refund if the credits and withholding exceed the amount of tax due, and there are no issues with the return."
That "no issues" qualifier is the whole reason this code carries so much weight on a transcript. Seeing a TC 846 post means the return cleared every hold that could have stopped it — no unresolved freeze, no open review — and the system committed to a specific dollar amount and a specific release date. What that date actually promises, and what it does not, is where most of the confusion starts.
What the date next to TC 846 actually promises — and what it doesn’t
The date is a scheduled release date, not a receipt guarantee. Per IRM 21.4.1.4.2, the way a refund was issued — paper check or direct deposit — is marked right next to the transaction: "the indicator DD:0 (paper check) or DD:9 (direct deposit) will appear near the right margin either on the same line as the TC 846 or the next line down." Which one is showing changes what the date actually means, because the two payment methods are handled by different rules from that point forward.
Federal holidays are handled differently for each method, and in opposite directions. For a paper check, the IRM states: "If the issue date falls on a federal holiday, the refund will be issued on the day before the holiday." For direct deposit, it is the reverse: "If the issue date falls on a federal holiday, EFT refunds are dated on the holiday, but depending on the financial institution, may not be credited until the following day." A holiday sitting on the scheduled date pulls a paper check earlier and can push a direct deposit later — the same calendar event, two different effects, depending on which indicator is on the line.
IRS's own procedures go further than most practitioner shorthand acknowledges: the posted TC 846 date and the actual disbursement date are tracked as two separate fields internally, and the IRM's own worked example shows they are not guaranteed to match. IRM 21.4.1.5.7.1 documents a deposit-date field, "RFND-PAY-DATE" on CC IMFOLT and "RFND-PYMT-DT" on CC TXMOD, that sits on the line below the TC 846 entry on IRS's internal research screens — and its own example reads: "The TC 846 date for a direct deposit is 03/21/2024. The actual direct deposit date, as indicated by the RFND-PAY-DATE field below the TC 846, is 03/07/2024." That gap is the IRS's own documentation, not a hedge added for this page. It is worth being precise about where that second field lives: it is documented here as something IRS employees see on internal command codes, not confirmed to print in plain English on the account transcript a taxpayer or authorized representative actually downloads — so treat the bare TC 846 date on a downloaded transcript as the best available number, while knowing IRS's own internal records can carry a second, more specific figure a practitioner cannot see directly.
There is also a step between "scheduled" and "certified" that has nothing to do with timing at all: an offset. IRM 21.4.1.4.2 states that Treasury's "Offsets will occur after IRS has certified a refund for issuance TC 840/846, but before the check is actually sent or deposited" — so a TC 846 amount can be accurate as posted and still not be the number that actually reaches the taxpayer, if a state, federal, or child-support debt intercepts part of it first.
What this means for your refund
If a TC 846 is sitting on your transcript, the IRS has finished processing your return, cleared it of holds, and scheduled a specific amount to go out on a specific date — that part is real and it is close to final. What it does not mean is that the money will be sitting in your account or mailbox on that exact date. Direct deposits and paper checks run on different clocks: IRS gives direct deposits five or more calendar days past the scheduled date before it will even start looking for the money, and paper checks get four weeks (nine if the address is outside the United States) before the same thing happens. Neither of those windows is a sign something went wrong — they are simply how long the IRS says a normal delivery can reasonably take before it is worth escalating. Once you're past the relevant window, the IRS's own refund page is where that escalation actually happens — the refund tracker there checks status directly, and it points to Form 3911 if a paper check needs to be formally traced as lost.
A holiday landing near your scheduled date can move things a day either direction, and a debt owed to another government agency can shrink the amount without changing the date at all — both are normal, documented parts of how this code works, not evidence the refund is stuck. If you are looking at a transcript with a TC 846 and several other codes around it and are not sure what the whole picture adds up to, running it through the IRS Transcript Decoder is the fastest way to see how they fit together.
What TC 846 gets confused with
TC 840 looks like the same thing — a refund leaving the account — but it is a different process with its own, much shorter clock. Document 6209 defines it as a "Manual Refund," one "designat[ing] a manual refund was issued prior to or after a return (TC 150) has posted." Unlike TC 846's automatic release, a TC 840 means an employee certified the refund directly, outside the normal systemic path — often because the case needed to move faster than Master File's regular cycle would allow. That difference in origin shows up directly in IRM 21.4.1.4.4's own wait-time table: a TC 840 gets only "10 calendar days (30 calendar days if it's a foreign address)" before the IRS will act on a non-receipt claim, versus four weeks (nine foreign) for a TC 846 paper check — roughly a third of the wait, because a person, not a batch process, already worked the case once.
TC 841 is the one worth watching for after a TC 846 posts, because it means the money did not stay put. Document 6209 defines it as crediting "the tax module for the amount of the transaction from a refund check (TC 840 or BMF/IMF 846) which was cancelled" — in plain terms, a check that bounced back, was flagged as altered or stolen, or a direct deposit the bank returned. IRM 21.4.1.4.4 lists TC 841 on the same table as TC 846, under its own row: "TC 841 Returned/Stopped Refund." Finding a TC 841 after a TC 846 is not itself bad news — the IRM's own altered-check procedures state directly that "TC 841 and a TC 846 reissuing the refund" is resolved by advising "the taxpayer of the refund timeframe" — but it does mean the original TC 846 date is no longer the one that matters; the second TC 846, if and when it posts, is.
One more code shows up near a TC 846 without being a refund transaction at all: a TC 971 can post to stop a direct deposit before it releases — action code 850 exists for exactly that, per IRM 21.4.1.5.7 — or to record something else entirely happening on the same account around the same time. A TC 971 next to a TC 846 is worth reading on its own terms rather than assumed to be part of the refund story; see TC 971 for why that code alone never says what it is doing without more context.
The practitioner’s actual next step
Confirm the payment-method indicator before promising a timeline — DD:0 or DD:9 on the same line as the TC 846 (or the line below it) tells you which of the two very different clocks applies, per IRM 21.4.1.4.2. If the client's transcript shows an overpayment on the return but no TC 846 at all, check for an open freeze before assuming the refund is simply delayed; a V- freeze from TC 130, for instance, blocks refunding an entire account until a TC 131 or TC 824 releases it, and a TC 846 structurally cannot post while it is in place.
Once a TC 846 is present, hold the wait-time thresholds exactly, not loosely: five or more calendar days past the scheduled date for direct deposit, four weeks (nine foreign) for a paper check, before advising a trace — and when that point arrives, a self-service refund trace or Form 3911 for a paper check is the actual next action, not just "wait longer" or "call and ask." And always check for a subsequent TC 841 before telling a client their refund already arrived — a cancelled or returned refund reads almost identically to a completed one unless the practitioner looks for the reversal.
Sources
- IRS Document 6209, Section 8A (Master File Codes) — TC 846, 840, 841
- IRM 21.4.1 — Refund Research (refund issuance, direct deposit, and refund-inquiry procedures)
- Taxpayer Advocate Service — Decoding IRS Transcripts and the New Transcript Format: Part II
- IRS.gov — Refunds (refund status tracker and Form 3911 for a paper check that never arrived)