TC 768: Earned Income Credit

What the code actually does

TC 768 posts the Earned Income Credit as claimed on an original return. Document 6209 is brief and specific: it "posts Earned Income Credit which is generated from information received from Code and Edit" — Code and Edit is the IRS's original-return data-entry function, which is the detail that matters. TC 768 is not a generic refundable-credit posting that happens to be EIC; it is the code specifically tied to EIC information captured when the return itself was first processed.

That original-processing origin is what separates TC 768 from its own closer relative, TC 764. Doc 6209 defines TC 764 the same way, "Earned Income Credit," but sources it differently: it "posts Earned Income Credit generated from line items from Adjustments" — meaning a later correction, not the original return. TC 768 and TC 764 are the same credit reaching the module by two different roads: the original filing, or a later adjustment to it.

TC 768, TC 764, and TC 766 are three different codes — not one code with variants

This is the distinction most worth getting right. TC 768 and TC 764 share a single reversal code, and Doc 6209 states it plainly: TC 765, "Earned Income Credit Reversal," simply "Reverses TC 764 or 768." TC 766 is not part of that family at all — it is a different code entirely, carrying its own separate reversal code, TC 767, and its own separate Doc 6209 title, "Generated Refundable Credit Allowance," covering a deliberately wide range of credits verified across a long list of return types. It shares neither TC 768's and TC 764's dedicated "Earned Income Credit" title nor their TC 765 reversal code.

A transcript showing both a TC 766 and a TC 768 in the same account is not a duplicate posting of the same credit — it is almost always two different credits that happen to have posted around the same time. Reading TC 766 as "more EIC" on top of a TC 768 that already posted the credit is a common misread this page exists to correct.

The PATH Act hold on EIC refunds

A TC 768 on the account brings its own timing rule, independent of whether the credit amount is correct. That rule traces back to the PATH Act — the Protecting Americans from Tax Hikes Act of 2015 — which added this exact hold to the statute. IRC §6402(m) states it directly: "No credit or refund of an overpayment for a taxable year shall be made to a taxpayer before the 15th day of the second month following the close of such taxable year if a credit is allowed to such taxpayer under section 24 (by reason of subsection (d) thereof) or 32 for such taxable year" — section 32 being the Earned Income Credit statute itself. In plain terms, a return claiming EIC cannot generate its refund before roughly mid-February, no matter how early it was filed or how quickly TC 150 and TC 768 both posted.

That delay is a statutory rule applying to every return claiming the credit, not a sign that anything is wrong with this particular one. A client asking why a refund hasn't arrived in late January despite an early filing and a TC 768 already on the transcript is usually looking at IRC §6402(m) working exactly as written, not a processing problem.

What this means for your refund

A TC 768 confirms the Earned Income Credit posted from the original return — it does not, by itself, mean the refund is imminent. Between the PATH Act hold above and ordinary processing timing, a refund carrying EIC routinely lands later than a comparable refund without it, even when nothing about the return itself is in question. The IRS Transcript Decoder can help confirm whether a specific account's TC 768 is sitting inside the normal PATH Act window or reflects something else worth researching.

What TC 768 gets confused with

Beyond TC 766, the code most worth distinguishing from an ordinary TC 768 is a freeze that sounds like it belongs to the same subject: TC 810 with Responsibility Code 3 — what Document 6209 calls "Code 3," the same field IRM 21.5.6.4.10 calls a Responsibility Code (RC), not a "closing code." Doc 6209's one-line description of it, "Code 3 earned Income Credit Check Freezes," is narrower than what the current IRM text actually shows. Per IRM 21.5.6.4.10, "TC 810 RC 3" covers a cluster of credit-specific fact patterns, not EIC alone: an EIC freeze on its own, an EIC-and-Additional-Child-Tax-Credit combination, several Premium Tax Credit variations, and an American Opportunity Tax Credit freeze. A TC 810 with RC 3 sitting on the same module is not necessarily about the Earned Income Credit at all — it can just as easily be holding the refund over a Premium Tax Credit or American Opportunity Tax Credit question with no EIC involved. Either way, a TC 768 says the credit was allowed; a TC 810 with RC 3 says a different part of the IRS is holding the refund over a credit combination under review — which may or may not include the EIC that TC 768 already posted. The two are easy to conflate because they share a subject, and they should not be read as confirming each other. See TC 810 for the full Responsibility Code framework.

The practitioner's actual next step

Confirm which code actually posted before advising a client on refund timing: TC 768 means the credit came from the original return, TC 764 means it came from an adjustment, and a TC 766 elsewhere on the same transcript is very likely a different credit entirely, not additional EIC.

If a client with a TC 768 asks why the refund is late in late January or early February, check the calendar against IRC §6402(m) before researching a processing problem that may not exist. If the delay runs well past the PATH Act window, check specifically for a TC 810 with Responsibility Code 3 — and confirm which credit it actually concerns before assuming it is the EIC, since RC 3 also covers the Additional Child Tax Credit, the Premium Tax Credit, and the American Opportunity Tax Credit.