TC 760: Substantiated Credit Payment Allowance
By Forrest Baumhover, CFP®, EA · Last verified September 9, 2026
TC 760 is the ending of a genuinely lost-payment case — a manual credit the IRS posts once a taxpayer has proven they made a payment Master File never recorded, and only one specialized unit has authority to input it.
What the code actually does
IRS Document 6209, Section 8A defines TC 760 as crediting the module "for a payment which was substantiated as having been paid, but not posted to the MF." This is not a routine payment posting — it is a manual finding that a payment genuinely happened and genuinely never made it onto Master File through any of the ordinary channels.
Reaching this code means every other explanation — a rolled-over deposit, a misapplied credit sitting on a different module, a payment still resequencing — has already been ruled out through the standard payment-tracer research this batch's other pages describe.
Only one function can input it
IRM 21.5.7.4.4.3 is explicit about the gatekeeping: "Only HPTF prepares Form 3809, Miscellaneous Adjustment Voucher, for a TC 760, Substantiated Credit Payment Allowance." HPTF is the Hardcore Payment Tracer Function — the specialized unit this batch's pages repeatedly point to as the escalation point when a payment cannot be located through ordinary research.
That restriction means a general caseworker cannot simply input a TC 760 on their own conviction that a payment was made. The case has to be formally referred to HPTF, and HPTF has to independently substantiate the payment, before this credit can post.
What "substantiated" actually requires
This is not a taxpayer's word alone. Reaching a TC 760 typically requires documentary proof — a cancelled check image, bank record, or equivalent evidence — of the kind IRM 21.5.7.3 describes gathering at the start of any payment-tracer case: "evidence of payment (e.g., copy of cancelled check, front and back)," the date it cleared, and the amount.
Practitioners should set expectations accordingly. A TC 760 is the resolution of a well-documented, thoroughly researched case, not a quick fix for a client who simply insists a payment was sent. Weak or circumstantial evidence is more likely to result in a continued search than a manual credit allowance.
What TC 760 gets confused with
It gets confused with any ordinary payment code, when it is in fact a rare, manually substantiated credit that exists specifically because the ordinary posting process failed.
It gets confused with a credit transfer like TC 700. A credit transfer moves a payment that is already on Master File somewhere; TC 760 creates a credit for a payment that was never on Master File anywhere, which is why it requires substantiation rather than simple research.
It gets confused with a rolled-over federal tax deposit or an ordinary resequencing payment. Both of those are genuinely on Master File already, just not yet visible on the module being checked — a TC 760 case only exists once that possibility has actually been ruled out.
Its dishonored-check counterpart does not exist the same way the other codes in this batch pair up — a substantiated payment, by definition, has already cleared, so there is no TC 761 bad-check reversal; the correction code is TC 762, for an erroneous TC 760, not a bounced one.
The practitioner's actual next step
Confirm the standard payment-tracer research has been exhausted before pursuing a TC 760 — CC IMFOL/BMFOL, the IAT (Integrated Automation Technologies) TC Search Tool, and RTR (Remittance Transaction Research system) imaging are IDRS (the IRS's internal Integrated Data Retrieval System) tools only an IRS employee can run, so a practitioner requests this research through a transcript pull or the assigned IRS contact rather than running it personally; a TC 760 is the last resort once that research comes up empty, not the first request.
Assemble documentary proof of payment before referring the case to HPTF; a bare assertion is unlikely to result in a substantiated credit.
Prepare Form 4446, Payment Tracer Research Record, as the referral vehicle into HPTF, consistent with the escalation path used throughout this payment-tracer batch.
Watch the refund statute of limitations under IRC §6511 while a case is pending — if resolution takes long enough that the substantiated payment would produce a refund rather than pay down an existing balance, §6511's time limits can bar relief even after the payment itself is proven.
Set client expectations that this process takes real time and real documentation, not a phone call.