IRS transaction code 766 records a credit to your account, typically for refundable credits the IRS has processed and allowed. Unlike Code 806, which captures withholding and excess FICA claimed on a return, Code 766 generally reflects generated refundable credit allowances calculated by the IRS. When the entry includes an offset trace number, it may also represent the reversal of a prior Treasury Offset Program (TOP) reduction—crediting back an amount that had been intercepted to satisfy a separate federal or state debt. The credit entry itself does not guarantee a refund will reach your bank account; it shows the IRS has posted an allowance that may later flow into Code 846, which debits the module to issue a refund of overpayment.
Understanding Code 766 means recognizing what it is not. It is not proof that a specific refundable credit—child tax credit, recovery rebate, or another program—has been approved for the amount shown. It does not confirm which line of your return generated the credit, nor does it establish a deposit date. The code marks an accounting entry; surrounding transaction codes, your filed return, and any IRS notices together explain the full picture.
What this entry establishes
Code 766 appears on your IRS account transcript alongside a dollar amount and transaction date. According to IRS Document 6209, Section 8A, the entry generally records a generated refundable credit allowance. If an offset trace number accompanies the 766, the entry may reverse a prior Code 898 TOP offset in whole or part, restoring funds previously diverted.
Transaction Code 767 reverses a 766 entry, removing the credit previously posted. A later 767 does not necessarily reverse Code 846 itself; each code operates at a different accounting layer. Code 768 is the dedicated earned income credit entry, so not every earned income credit uses 766. The presence of 766 alone does not identify which refundable credit program applies or confirm that the amount matches what you calculated on your return.
A practical reconciliation worksheet
Build a simple table that isolates observations from conclusions. Record what the transcript shows, what your records show, and any unresolved differences. Do not diagnose cause in the observation columns.
| Source | Code/Line/Document | Amount | Date | Notes / Unresolved Difference |
|---|---|---|---|---|
| Account transcript | TC 766 | $2,400 | Apr 15 | Credit entry posted |
| Filed return copy | Refundable credit total | $2,850 | Filed Feb | $450 difference from transcript |
| Account transcript | TC 846 | $2,400 | Apr 22 | Refund issued matches 766 |
| Bank statement | IRS TREAS deposit | $2,400 | Apr 29 | Received amount matches 846 |
| Notice received | CP12 adjustment notice | Adjustment | Dated Apr | Explains reduction; review calculation |
The table prevents the reflexive leap from "I see 766" to "I know exactly which credit this is and when my refund arrives." Instead, you map each piece of evidence and flag gaps.
Check the records in order
Start with the account transcript for the relevant tax period. Note every transaction code, amount, and date. Compare the 766 amount to your filed return's refundable credit total. If they match, record the numerical match as a candidate explanation, not proof of which credit was allowed. If they differ, review any IRS notices explaining adjustments.
Next, check subsequent entries. Does a Code 846 appear after the 766? If so, the system has debited the module to issue a refund. Code 846 records a refund of overpayment but does not establish the bank settlement date. Check your bank statement for whether the amount was actually received; use the IRS refund status tool for the official current refund status, which is not proof of settlement.
Look for reversal codes. If TC 767 appears, the credit was removed in whole or part. If TC 841 cancelled refund appears, the refund transaction did not complete. Mark these as unresolved differences and obtain the official notice explaining the action.
Finally, confirm the tax period. Code 150 shows the original return filed and tax liability assessed. An assessment does not prove you personally submitted the return; identity theft and processing errors occur. If you see 766 but did not file a return for that period, request a full account transcript and compare it to your records before concluding the credit is legitimate.
A hypothetical example
A taxpayer receives an account transcript showing TC 766 for a refundable credit, followed by TC 846 for a refund issued, both with matching amounts. The taxpayer's bank statement confirms receipt of that amount several days after the 846 date. The filed return copy shows the same refundable credit total, and no adjustment notice arrived. In this scenario, the 766 likely represents the credit as claimed, and the 846 confirms the overpayment was refunded.
In a different case, the credit recorded under TC 766 differs from the amount expected from the return. The taxpayer records both amounts and reviews any adjustment notice. If TC 767 also appears, its amount is tracked separately so the same reduction is not counted twice. An unexplained difference remains a question for follow-up.
A third scenario contains TC 766 with an offset trace number linked to an earlier TC 898 TOP offset. The taxpayer records the relationship and checks the relevant offset notice. That is a different explanation from a new refundable credit allowance; paying a debt elsewhere does not by itself prove a prior offset must be refunded.
Reconciliation checklist
- [ ] Locate Code 766 on the account transcript and note the amount and date
- [ ] Compare the 766 amount to the refundable credit total on your filed return
- [ ] Check for any IRS adjustment notices explaining differences
- [ ] Identify subsequent Code 846 entries that debit the module for refund issuance
- [ ] Check official refund status separately from bank or check evidence of actual receipt
- [ ] Review reversal codes (TC 767, TC 841) and obtain explanations if present
- [ ] Verify the tax period and Code 150 assessment matches your filing
- [ ] Mark unresolved differences in your worksheet rather than guessing the cause
FAQ
Does Code 766 mean I will receive that exact refund amount?
No. Code 766 records a credit allowance, not a guaranteed deposit. Check for a following Code 846 entry, which debits the module to issue a refund. The actual refund may differ if other adjustments, offsets, or payments occurred after the 766 posted.
Can I tell which refundable credit the 766 represents just from the code?
Not from the code alone. Code 766 generally reflects generated refundable credit allowances, but the specific program—recovery rebate, additional child tax credit, or another—requires comparison to your filed return and any IRS notices. A matching amount is a candidate explanation, never proof of credit identity.
What should I do if Code 766 appears but I did not file a return?
Request a full account transcript and review the Code 150 assessment entry. An assessment does not prove you personally submitted a return. Compare the transcript to your own records, including W-2 and 1099 forms. If discrepancies remain, contact the IRS to verify the filing and consider whether identity theft or processing error occurred. Do not automatically file an amended return or identity theft affidavit based on the code alone.
Does Code 767 reverse my refund?
Code 767 reverses a Code 766 credit entry, removing the allowance from your account. It does not necessarily reverse Code 846 itself, which operates at a different accounting layer. Check the amounts and dates of each code and obtain the official notice explaining why the 766 was reversed.
For tax firms
Transcript reconciliation depends on structured intake and repeatable workflows. A shared workpaper template, linked authorization records, and clear handoff protocols reduce the risk of missed reversals or misidentified credits.
Discuss your firm’s authorization, transcript and CRM workflow in a 26T1 demo.