TC 732: Correction of TC 730 Processed in Error
By Forrest Baumhover, CFP®, EA · Last verified September 10, 2026
TC 732 undoes a TC 730 manual interest transfer that was entered incorrectly, in whole or in part, and it is worth recognizing on sight because it means the original transfer — not just the correction — is the thing that actually needs a second look.
What the code actually does
IRS Document 6209 is brief and specific about TC 732: it "reverses TC 730 interest credit applied in whole or in part by debiting the Tax Module," and requires that its own "transaction date must match TC 730 date." TC 732 is a debit — it removes some or all of an interest amount that a prior TC 730 credited to the module (the IRS's record for one tax period within the account), and it does so by pointing back at the exact TC 730 it is correcting rather than acting as a freestanding adjustment.
Because a TC 730 is generally the credit half of a manual transfer paired with a TC 850 debit on another module, a TC 732 correcting that credit leaves the question of the other side open. Undoing the receiving module's credit does not, on its own, say anything about whether the sending module's TC 850 also needs a matching fix.
Why this is a correction, not a full reversal
Doc 6209 frames TC 732 as fixing something "processed in error" — the transfer itself was entered wrong, whether in amount, in destination module, or in date — rather than describing a case where the underlying decision to transfer interest was later reconsidered. That distinction matters for how much digging a TC 732 actually calls for: it confirms a mistake happened on the mechanics of moving the money, not that the interest figure being moved was miscalculated in the first place.
The required date match — TC 732 must carry the same transaction date as the TC 730 it corrects — exists so the two entries tie together cleanly on the module's history rather than leaving an ambiguous, undated correction sitting apart from the transaction it fixes.
Checking the other side of the original transfer
A TC 730 correction on the receiving module is easy to read as the whole story, but the transfer it corrects had a TC 850 debit sitting on a different module at the time it was entered. If that TC 730 was wrong, there is a real possibility the paired TC 850 needs review as well — reviewing only the module where the TC 732 posted risks leaving a one-sided, half-corrected pair of interest entries elsewhere on the account.
This is the same review discipline TC 852 requires for its own manual-transfer family: a posted correction on one side of a paired transaction is not, by itself, confirmation that the other side is clean.
What TC 732 gets confused with
It gets confused with TC 731, a similarly named but functionally different correction code. TC 731 reverses a generated TC 736 credit or an erroneously posted TC 756 — both computer-generated, systemic transactions — while TC 732 reverses only a TC 730, which is always a manually entered one. The two corrections sit on opposite sides of the manual-versus-systemic line that runs through this entire code family, and mixing them up misidentifies whether a person or the computer made the original entry that needed fixing. Confirming which one a module actually carries also tells a practitioner where to look for the underlying error — a TC 731 points back to Master File's (the IRS's central account-processing system) own systemic offset logic, while a TC 732 points back to a manually keyed transfer someone entered incorrectly.
It also gets confused with TC 852, its closest sibling in mechanics. TC 852 "corrects 850 transaction by posting a credit to the tax module" — the debit side of the same pair TC 730/732 governs on the credit side. A TC 732 on one module and a TC 852 on another can both legitimately appear for the same underlying paired transfer, and finding only one of them is a reason to look for the other.
The practitioner's actual next step
Verify the transaction dates match before treating a TC 732 as clean — Doc 6209 requires the correction date to equal the original TC 730 date, and a mismatch is itself worth raising as a separate discrepancy.
Check the module the original TC 850 debit posted to for a companion correction. If the TC 730 side needed fixing, ask whether the TC 850 side does too, rather than assuming the paired entry was entered correctly.
Do not treat the corrected amount as newly verified interest math. TC 732 confirms a transfer entry was wrong; it says nothing about whether the interest figure behind the transfer was itself calculated correctly.
Note which specific TC 730 the correction addresses when more than one manual interest transfer exists on the account's history, since the module may carry several over time.