TC 820: Credit Transferred
By Forrest Baumhover, CFP®, EA · Last verified September 9, 2026
TC 820 is the debit half of a manual credit transfer — money deliberately moved off one module (the record for one tax type and period) to another module, another account, or Excess Collections — and it carries a hard availability rule: the credit must already exist on Master File (the IRS’s official repository of taxpayer data) or the whole transaction fails to post.
What the code actually does
IRS Document 6209, Section 8A (the IRS’s reference guide to its data-processing codes) defines TC 820 as manually transferring "previously posted credit amount to another tax module, another account, excess collections, or other destination as required." It is the general-purpose debit side of a manual credit transfer, with TC 700 posting as "the corresponding credit" wherever the money lands.
TC 822 reverses a TC 820 in whole or in part, with TC 702 as the corresponding debit. TC 821 reverses the computer-generated TC 826, not this code.
The hard availability rule
Doc 6209 states this in capital letters for a reason: "CREDIT MUST BE AVAILABLE ON MASTER FILE AT TIME OF POSTING OR WILL UNPOST." A TC 820 transferring more than the module actually has available does not partially post and generate a debit balance — it fails outright, flagged as Unpostable Code 175 on an individual account (IMF, the Individual Master File) or Unpostable Code 325 on a business account (BMF, the Business Master File).
That distinction matters when reconciling a module that appears to show a transfer that "should have happened" but never actually took effect — check for the unpostable condition before assuming the transfer completed as intended, since an unposted attempt leaves no partial trace on either module.
The statute-freeze side effect
Doc 6209 also notes a specific, narrower effect: TC 820 "releases Assessment Statute Expiration Freeze for Doc. Code 24 only." Not every TC 820 releases this freeze — only those input under document code 24 do. A practitioner tracking an assessment statute expiration date under IRC §6501 should confirm the specific document code on the transfer before concluding whether this freeze-release effect actually applies to the module in question.
That matters most when the freeze is what has been protecting an assessment past the ordinary limitations period. Releasing it prematurely, or assuming it released when the document code does not actually support that, can change the analysis of whether an assessment is still timely at all — a determination worth getting right before advising a client either way.
Neither Doc 6209 nor the general unpostable-resolution IRM directly states whether this freeze-release effect survives when the same TC 820 fails to post under the availability rule above. Because an unpostable transaction has, by definition, not actually posted to Master File, the freeze more likely remains in place until the transfer is corrected and successfully posts — but that specific interaction is not spelled out in a primary source, so treat it as an open question worth confirming with the IRS rather than an established rule.
What people mistake TC 820 for
People confuse it with TC 826, the Master File generated overpayment offset. TC 820 is always a manual action a caseworker initiates; TC 826 is always computer generated as part of the automated pre-refund offset process.
People confuse it with a completed transfer when it actually went unpostable for exceeding the available credit — the fix is correcting the amount and re-input, not assuming the money moved.
People confuse it with a routine payment leaving the account. TC 820 moves an already-existing credit somewhere else within the IRS's own systems; it is not a refund and not money returned to the taxpayer.
People confuse it with an ordinary module-to-module transfer when the destination is Excess Collections. Excess Collections is a separate IRS file (the Excess Collection File), not a Master File tax module.
What to do next
Confirm the credit was actually available on the module at the time of posting before assuming a TC 820 transfer completed successfully.
Check for UPC 175 (IMF) or UPC 325 (BMF) if a transfer that should have posted does not appear to have taken effect.
Verify the document code before relying on the Assessment Statute Expiration Freeze release — it applies to document code 24 transfers specifically.
Trace the matching TC 700 credit on the receiving module to confirm the transfer's destination and amount.