TC 700: Credit Applied

By Forrest Baumhover, CFP®, EA · Last verified September 9, 2026

TC 700 is the receiving side of a manual credit transfer — money moved deliberately from one module (the IRS's record for one tax period within the account) to another by a caseworker — and one of its documented uses is quietly preventing an erroneous-refund bill from generating while the case is still being worked.

What the code actually does

IRS Document 6209, Section 8A defines TC 700 as crediting the module "for a manually transferred amount," with the debit side of the same transfer posting as TC 820 "if amount is from a MF [Master File, the IRS's central account-processing system] Account." This is the credit half of an ordinary manual credit transfer, the mechanism IRM 21.5.8 governs throughout this batch.

A manual transfer moves an already-posted credit from where it currently sits to where it actually belongs — the opposite of a generated offset, which the computer initiates on its own.

Its quieter use: holding an erroneous refund case together

Doc 6209 documents a second, more specific use: "accounting credit posts in erroneous refund cases to prevent bill from generating." Where the IRS is working to recover an erroneous refund, a TC 700 accounting credit can sit on the module to keep a routine balance-due bill from going out to the taxpayer while the recovery process is underway.

Doc 6209 itself describes this credit as one that "will be reversed once refund repaid," but that line is now stale. Current, more specific procedure — IRM 21.4.5.5.5, governing Category D erroneous refunds — instructs the opposite for the specific accounting credit at issue here, identifiable as a TC 700 with document code 58 and blocking series 950-999: "Do not release the -U freeze [an account-level collection hold]. Do not reverse or transfer the false credit." Rather than reversing automatically once the refund is repaid, this credit is meant to sit in place as a hold on the module while the erroneous-refund case is worked. Seeing a TC 700 in this context is not evidence the balance is resolved, and practitioners should not expect or request its automatic reversal on repayment — it is evidence a collection or repayment process is actively in progress and specifically being managed to avoid a premature notice going out while the recovery is still being worked.

Confirming which kind of TC 700 is on the module

Because the same code covers both an ordinary transferred credit and the erroneous-refund holding credit, check the module's broader context — is there an unresolved erroneous refund elsewhere on the account, or a genuinely reconciled credit transfer with a matching TC 820 debit on another module? Those two fact patterns call for different next steps, and the transaction code alone will not distinguish them.

IRM 21.5.8.4.2 describes the underlying command-code mechanics for a manual transfer. Use CC ADD24/ADC24 when the transfer needs a payment-date change, a secondary transaction code, or — directly relevant here — involves a TC 820; use CC ADD34/ADC34 for an ordinary transfer within the same Master File. That distinction is the trail to follow when verifying a manual transfer's legitimacy and completeness.

What TC 700 gets confused with

It gets confused with its own generated counterpart, TC 706 — both credit a module from a transfer, but the Master File generates 706 automatically as part of the automated pre-refund offset process, while a caseworker manually initiates 700 (with its debit-side partner, TC 820).

It gets confused with a resolved balance when it is actually the erroneous-refund holding mechanism described above — the credit exists to suppress a bill, not to reflect that the underlying amount has been repaid.

It gets confused with a permanent credit. Current IRM procedure specifically instructs examiners not to release or reverse the erroneous-refund variant of this credit while the underlying case remains open, so its presence signals an open process rather than a closed one — not (per Doc 6209's older, now-superseded description) a credit due to reverse automatically once the refund is repaid.

The practitioner's actual next step

Check for a matching TC 820 debit on another module before assuming a TC 700 reflects a resolved, standalone credit.

Look for an open erroneous-refund case elsewhere on the account when a TC 700 appears without an obvious transfer explanation.

Do not advise a client that a balance is settled based on a TC 700 alone if the surrounding facts suggest an erroneous-refund recovery is still in progress.

Confirm the transfer used the correct command code and document code combination if the credit's placement or amount looks wrong.

Sources

Free weekly federal tax analysis for practitioners

Every week, the handful of federal tax changes that actually require action — with primary-source citations, and new IRS practitioner tools the day they ship.

Subscribe free →