IRM 25.23.4 — IDTVA Paper Process

# Part 25. Special Topics

Chapter 23. Identity Protection and Victim Assistance Section 4. IDTVA Paper Process 25.23.4 IDTVA Paper Process Manual Transmittal August 14, 2025 Purpose (1) This manual transmits revised guidance for IRM 25.23.4, IDTVA Paper Process, and provides procedures for the treatment and resolution of Individual Master File (IMF) tax-related identity theft (IDT) cases. Material Changes (1) IRM 25.23.4.1.3 Title changed to Roles and Responsibilities. (2) IRM 25.23.4.1.6 Title changed to Terms and Acronyms. (3) IRM 25.23.4.1.6(1) Removed Identity Theft Assistance Request (ITAR) from the list of acronyms used. Added Identity Theft Victim Assistance Headquarters (ITVA HQ) to the list of acronyms used. (4) IRM 25.23.4.3.1(1) Added a Caution addressing the creation of CII cases for NOIDT determinations. Revised current guidance for cases previously resolved identified through CCA for clarification. Revised the Reminder to clarify taking control of an unassigned case. (5) IRM 25.23.4.3.1(1) Revised the Exception listing to include addressing unresolved issues involving a secondary taxpayer. IPU 25U3218 issued 04-28-2025. (6) IRM 25.23.4.3.1(1) Revised 1st Note to include information on creating new case(s) on CII for issues identified through CCA. IPU 24U1106 issued 11-06-2024. (7) IRM 25.23.4.3.1(2) Revised current guidance for opening CII case controls for additional impacted years and covered relationships. Revised information for the received date on IRS identified cases for clarification. (8) IRM 25.23.4.3.1(6) Added a new paragraph for correspondence uploaded using the Document Upload Tool (DUT) and Digital and Mobile Adaptive Forms (DMAF). Subsequent paragraphs were renumbered. (9) IRM 25.23.4.3.1(6) Revised to clarify guidance when multiple IDT cases for the same taxpayer. IPU 25U3304 issued 05-19-2025. (10) IRM 25.23.4.3.1(7) Added a new paragraph with guidance for multiple IDT cases for the same taxpayer and tax module include similar documentation. Subsequent paragraphs were renumbered. IPU 25U3304 issued 05-19-2025. (11) IRM 25.23.4.3.1(7) Added a new paragraph to include information for correspondence received from the taxpayer for a previously resolved cases. Subsequent paragraphs were renumbered. IPU 25U3246 issued 05-05-2025. (12) IRM 25.23.4.3.3(1) Added a Reminder for IDTVA-A and IDTVA Specialty employees to review the applicable CII reassignment listing for reassignment of certain case types. IPU 25U3218 issued 04-28-2025. (13) IRM 25.23.4.3.5(2) Revised procedures for IDTVA-A cases with Priority Code (PC) 7. IPU 25U3246 issued 05-05-2025. (14) IRM 25.23.4.3.5(2) Updated Table Scenarios for Priority Code (PC) 3 and Priority Code (PC) 4 to clarify when not to update to another PC. IPU 25U0091 issued 01-23-2025. (15) IRM 25.23.4.3.5(2) Updated to include Priority 3 and Priority 4. IPU 24U1106 issued 11-06-2024. (16) IRM 25.23.4.3.5(3) Revised procedures for IDTVA Specialty cases with Priority Code (PC) 7. IPU 25U3246 issued 05-05-2025. (17) IRM 25.23.4.4(4) Revised Example (e) to clarify a taxpayer's claim for non-tax related IDT. IPU 24U1106 issued 11-06-2024. (18) IRM 25.23.4.5 Title changed to IRS Identified Identity Theft (Category Code IDT3). (19) IRM 25.23.4.5(1) Revised to mention the use of Category Code IDT3 for cases involving IRS identified identity theft for clarification purposes only. (20) IRM 25.23.4.5(2) Revised 2nd bullet to clarify indicators of current or prior identity theft for IDT1 case types. Revised 4th bullet to clarify indicators of current or prior identity theft for IDT8 case types. (21) IRM 25.23.4.5(3) Revised the Exception to clarify cases with RIVO involvement are not converted to IDT3. (22) IRM 25.23.4.5(3) Added a new paragraph to clarify when to send a closing letter to the taxpayer. Subsequent paragraphs were renumbered. IPU 25U3377 issued 06-05-2025 (23) IRM 25.23.4.6(2) Revised Note to remove CP 701S that was superseded by CP01S. (24) IRM 25.23.4.6(2) Revised first bullet to add a Note to clarify an acknowledgment CP 01S or CP 701S may have been issued. Removed second bullet advising employees to send an acknowledgement letter. IPU 25U0091 issued 01-23-2025. (25) IRM 25.23.4.6(4) Revised the Note to clarify current procedures for IDTVA-A employees. Added two Examples to provide to clarify current procedures. IPU 25U0368 issued 03-14-2025. (26) IRM 25.23.4.6(5) Revised time frame from 493 days to 582 days. IPU 25U3377 issued 06-05-2025 (27) IRM 25.23.4.6(5) Revised time frame from 640 days to 493 days. IPU 25U0091 issued 01-23-2025. (28) IRM 25.23.4.6(5) Revised time frame from 650 days to 640 days for consistency with current procedures in IRM 25.23.2.2.3 and IRM 25.23.4.18.1. IPU 24U1106 issued 11-06-2024. (29) IRM 25.23.4.6(6) Added a Note to Table Scenario (1) for inputting TC 971 AC 501 using MISC field "REFCCA" for cases with invalid returns reflecting a balance due. (30) IRM 25.23.4.6.1(11) Added a new 2nd bullet item for the presence of TC 971 AC 522 "EPSS DISABL" on accounts. Revised 3rd bullet to clarify indicators of current or prior identity theft for IDT1 case types and remove CP 701S that was superseded by CP01S from the Note.. Revised 4th bullet to clarify indicators of current or prior identity theft for IDT3 case types. Revised 5th bullet to clarify indicators of current or prior identity theft for IDT8 case types. (31) IRM 25.23.4.6.1(12) Revised to clarify procedures for cases with a previous identity theft indicator and duplicate filing conditions are present. (32) IRM 25.23.4.6.1(12) Revised the Note to clarify current procedures for IDTVA-A employees. IPU 25U0368 issued 03-14-2025. (33) IRM 25.23.4.6.1(18) Added a new paragraph for research on IDT claims and/or correspondence from incarcerated (prisoners) individuals. Subsequent paragraphs were renumbered. IPU 25U3218 issued 04-28-2025. (34) IRM 25.23.4.6.1(18) Added new Table Scenario (4) in the table to include a non-tax-related example. IPU 25U0368 issued 03-14-2025. (35) IRM 25.23.4.6.1.1 Created a new subsection for research on IDT claims and/or correspondence from incarcerated (prisoners) individuals. IPU 25U3218 issued 04-28-2025. (36) IRM 25.23.4.6.2(1) Revised to include required research for IDT8 transcript cases. (37) IRM 25.23.4.6.2(3) Revised to clarify research requirement for accounts with RIVO involvement and duplicate filing conditions. Removed the Example for CN determinations for cases with RIVO involvement. (38) IRM 25.23.4.6.2(4) Removed information regarding pre-determinations of CN ownership. (39) IRM 25.23.4.6.2(6) Added new Table Scenario (16) in the table to provide an IRM reference for account circumstances involving international taxpayers. Subsequent table scenarios were renumbered. IPU 24U1251 issued 12-18-2024. (40) IRM 25.23.4.6.2(8) Revised 1st Note for the use of another IAT adjustment tool when aMend cannot be used. IPU 24U1251 issued 12-18-2024. (41) IRM 25.23.4.6.2.1(9) Added a Note and Reminder in Table Scenario (2) and (3) to advise requirement for the use of the AMA2859 tool for prompt assessments. IPU 25U3218 issued 04-28-2025. (42) IRM 25.23.4.6.2.2 Created a new subsection with general information and research for on cases with RICS-RIVO involvement. (43) IRM 25.23.4.6.4(2) Added a new Table Scenario to include IP PIN as part of Complete Case Analysis (CCA). (44) IRM 25.23.4.6.4(6) Added a Note for marking an account using the CCA literal when the taxpayer does not identify the tax year(s) in their claim. IPU 25U0091 issued 01-23-2025. (45) IRM 25.23.4.6.4(7) Removed the Example due to inconsistency with current procedures IRM 25.23.4.3.1(2). IPU 25U0091 issued 01-23-2025. (46) IRM 25.23.4.6.5.2(3) Removed Note advising to make Common Number (CN) ownership prior to following statute protection procedures for Operation Assistance Requests (OARs) cases. IPU 25U0091 issued 01-23-2025. (47) IRM 25.23.4.6.5.2(8) Revised procedures for account conditions that must be addressed prior to forwarding a return for processing. Removed Table Scenario (5), (6), and (7) and moved to a table in new paragraph (10) table. IPU 25U0091 issued 01-23-2025. (48) IRM 25.23.4.6.5.2(9) Added a Note for the use of another IAT adjustment tool when aMend cannot be used. IPU 25U0116 issued 01-28-2025. (49) IRM 25.23.4.6.5.2(9) Added a new paragraph to include procedures for completing corrective actions to resolve an identity theft issue prior to forwarding an unprocessed return to post as the TC 976. Subsequent paragraphs were renumbered. IPU 25U0091 issued 01-23-2025. (50) IRM 25.23.4.6.5.2(10) Added a new paragraph with Table Scenario procedures for updating the entity. Subsequent paragraphs were renumbered. IPU 25U0091 issued 01-23-2025. (51) IRM 25.23.4.6.5.2(11) Removed instructions to ensure the account reflects appropriate IDT indicator(s). Subsequent paragraphs were renumbered. IPU 25U0091 issued 01-23-2025. (52) IRM 25.23.4.6.5.2(13) Revised information to clarify cases that meet previous action criteria. Previously paragraph (12). IPU 25U0091 issued 01-23-2025. (53) IRM 25.23.4.6.5.2.1(2) Revised Example for consistency of the revised Form 14039. IPU 25U3218 issued 04-28-2025. (54) IRM 25.23.4.6.5.2.1(4) Removed Table Scenario (2) with instructions when there is no open CII case control. Subsequent scenarios were renumbered. IPU 25U3218 issued 04-28-2025. (55) IRM 25.23.4.6.5.2.1(6) Updated Table Scenario (1) to include streamline processing and scheme criteria and removed original Table Scenario (2), (3) and (4). Subsequent scenarios were renumbered. IPU 25U3218 issued 04-28-2025. (56) IRM 25.23.4.6.5.2.1(7) Revised to clarify applicable procedures are for a valid return that needs to be processed. Revised Table Scenario (2) and (4) procedures to create a new CII case on statute imminent cases. IPU 25U3218 issued 04-28-2025. (57) IRM 25.23.4.6.5.2.1(9) Updated Table Scenario (2) and (3) to include information for corrective actions needed prior to forwarding an unprocessed return to post the TC 976 on the module(s). Added in Table Scenario (3) the requirement for the use of the AMA2859 tool for prompt assessments. IPU 25U3218 issued 04-28-2025. (58) IRM 25.23.4.6.5.2.1(11) Removed instructions on quick determinations for an unprocessed return. IPU 25U3218 issued 04-28-2025. (59) IRM 25.23.4.6.5.2.2 Title changed to Unprocessed Returns - 40 Day Monitor Time Frame Expired. IPU 25U3218 issued 04-28-2025. (60) IRM 25.23.4.6.5.2.2(1) Added a Caution in Table Scenario (2) for unpostable conditions. (61) IRM 25.23.4.6.5.2.2(1) Revised to replace "suspense" with "monitor" for consistency of IRM title. Revised Table Scenario (4) to replace "suspense" with "monitor" for consistency of IRM title. Revised Table Scenario (5) with procedures for case scenario with no indication the TC 976 is posted on the module(s). IPU 25U3218 issued 04-28-2025. (62) IRM 25.23.4.6.7(5) Revised information to clarify current procedures for review of a case for fraud referral. IPU 25U3218 issued 04-28-2025. (63) IRM 25.23.4.7(5) Added a new paragraph to include an IRM reference for procedures on making Common Number (CN) determinations for non-streamline case(s). IPU 24U1106 issued 11-06-2024. (64) IRM 25.23.4.8(8) Added a new Table Scenario to include information for taxpayer allegations of Return Preparer Misconduct (RPM). (65) IRM 25.23.4.8.1.1(4) Added two additional known fraud-schemes to the table. (66) IRM 25.23.4.8.1.1(5) Revised the conditions to clarify that at least one factor must be present to exclude a return with Form 7203 from consideration of a known fraud-scheme. IPU 25U0091 issued 01-23-2025. (67) IRM 25.23.4.8.1.3(3) Revised Table Scenario (1), (3), (5) and (7) to clarify the use of the IRS Received Date field when opening a CII case control. IPU 24U1106 issued 11-06-2024. (68) IRM 25.23.4.8.1.3.1(3) Added an Exception for cases involving NOIDT procedures for Invalid Joint Election (IJE) issues. IPU 25U0368 issued 03-14-2025. (69) IRM 25.23.4.8.2(1) Revised to clarify procedures for streamline IDT case processing for returns determined to be invalid. IPU 25U3304 issued 05-19-2025. (70) IRM 25.23.4.8.2(2) Added a new paragraph to clarify common terms for streamline case processing. Subsequent paragraphs were renumbered. IPU 25U3304 issued 05-19-2025. (71) IRM 25.23.4.8.2(3) Added a new paragraph for cases involving invalid returns reporting income earned by the valid taxpayer. Subsequent paragraphs were renumbered. IPU 25U3304 issued 05-19-2025. (72) IRM 25.23.4.8.2(4) Updated current streamline procedures for clarification. IPU 25U3304 issued 05-19-2025. (73) IRM 25.23.4.8.2(5) Removed the Married Filing Joint Scheme Involvement from the CN ownership determination listing and add Tax Preparation Software Misuse. (74) IRM 25.23.4.8.2(6) Added a new paragraph to include procedures when streamline processing criteria is not met. IPU 25U3304 issued 05-19-2025. (75) IRM 25.23.4.8.2.1(1) Revised information on following streamline procedures for cases with RIVO involvement for clarification procedures. (76) IRM 25.23.4.8.2.1(2) Removed guidance for reversed RIVO indicators and moved them to the new paragraph (5). Removed information for accounts with the TC 150 backed out by RIVO in error and moved it to the new paragraph (6). (77) IRM 25.23.4.8.2.1(3) Added a new paragraph to include information for reversed RIVO indicators. Subsequent paragraphs were renumbered. (78) IRM 25.23.4.8.2.1(4) Removed the Reminder for cases created as IDT6/IDS6. (79) IRM 25.23.4.8.2.1(7) Removed information for CP 36N and CP 36P transcripts. (80) IRM 25.23.4.8.2.2(1) Added a new paragraph to provide additional information on fraudulent account activity for decedent taxpayer. Subsequent paragraphs were renumbered. (81) IRM 25.23.4.8.2.2(3) Revised information to include fiduciary information or other legal documentation present for a decedent taxpayer. Moved information regarding Form 1310 to new paragraph (8).. (82) IRM 25.23.4.8.2.2(4) Removed requirement to use Category Code IDT8/IDS8 for decedent taxpayer cases. Added information for conducting thorough research for these case types. (83) IRM 25.23.4.8.2.2(5) Updated procedures to include information for claims submitted by a taxpayer (or surviving spouse) that is now deceased. (84) IRM 25.23.4.8.2.2(6) Added a new paragraph to include table procedures for IDT determinations for decedent taxpayer. (85) IRM 25.23.4.8.2.2(7) Added a new paragraph to include procedures for claims received on behalf of a taxpayer prior to their DOD. (86) IRM 25.23.4.8.2.2(8) Added a new paragraph to include additional considerations for decedent accounts. (87) IRM 25.23.4.8.2.5(4) Revised Table Scenario (5) to clarify procedures for tax-related and non-tax-related case type. IPU 24U1106 issued 11-06-2024. (88) IRM 25.23.4.8.2.5(5) Revised procedures for non-tax-related (IDT4) case processing. IPU 24U1106 issued 11-06-2024. (89) IRM 25.23.4.8.4 Revised paragraph (2) through (7) to reorganize and clarify details for claims involving dependent related identity theft. Added new paragraph (8) through (12) to include additional information to clarify issues for dependent related identity theft claims. IPU 25U3218 issued 04-28-2025. (90) IRM 25.23.4.8.4(3) Added Examples in the first Table Scenario for IDT claims filed by the parent/legal guardian of a dependent. (91) IRM 25.23.4.8.4(5) Added a Reminder regarding creating separate CII cases for each example in the Table. IPU 25U3304 issued 05-19-2025. (92) IRM 25.23.4.8.4(5) Revised Example (1) for clarification purposes. IPU 25U3246 issued 05-05-2025. (93) IRM 25.23.4.8.4(11) Added a Note to clarify the input a TC 971 AC 528 for Dependent related IDT cases. (94) IRM 25.23.4.8.4(12) Added a Caution in (d) and (e) to issue Letter 4674C for individuals under the age of 18. (95) IRM 25.23.4.8.4(12) Added a Note for taxpayers under the age of 18 for clarification. IPU 25U3304 issued 05-19-2025. (96) IRM 25.23.4.8.4.1 Title changed to Dependent Related Identity Theft (IDT) – Streamline Determinations. Revised paragraph (1) to indicate the application of streamline determination procedures. Revised paragraph (2) for conducting basic required research. Revised paragraph (3) to reorganize case research scenarios for streamline determination criteria, case research for non-streamline criteria has been moved to new IRM 25.23.4.8.4.2. Revised paragraph (4) to include a table with specific case research scenarios for streamline determination criteria, all previous information for consideration of claims in paragraph (5) and (6) has been moved to the new table in paragraph (4). Removed paragraph (7) to include in new IRM 25.23.4.8.4.2. Removed paragraph (8) to include in new IRM 25.23.4.8.4.3. IPU 25U3218 issued 04-28-2025. (97) IRM 25.23.4.8.4.1(2) Added a Caution addressing the possibility of a secondary TP being the potential confirmed parent/legal guardian. (98) IRM 25.23.4.8.4.1(7) Revised Table Scenario (4) to include CC TRDBV research steps from Table Scenario (3). IPU 25U0368 issued 03-14-2025. (99) IRM 25.23.4.8.4.1(7) Revised Table Scenario (3) and (4) to include use of CC TRDBV when conducting a review for Dependent IDT case types. IPU 24U1106 issued 11-06-2024. (100) IRM 25.23.4.8.4.1(8) Revised Table Scenario (1) to include the requirement to update the CII Category Code to IDT4 for non-tax related Dependent issues. IPU 24U1106 issued 11-06-2024. (101) IRM 25.23.4.8.4.2 Created a new subsection for non-streamline research for cases with dependent related identity theft. IPU 25U3218 issued 04-28-2025. (102) IRM 25.23.4.8.4.2(6) Revised current information when conducting a review of IDRS CC TRDBV. IPU 25U3377 issued 06-05-2025 (103) IRM 25.23.4.8.4.2(6) Revised information to include an IRM reference for procedures on dependent related IDT determinations. IPU 25U3304 issued 05-19-2025. (104) IRM 25.23.4.8.4.3 Created a new subsection with determinations for cases with dependent related identity theft. IPU 25U3218 issued 04-28-2025. (105) IRM 25.23.4.8.4.3(1) Removed special paragraphs from Table Scenario (3), (7), (8) and moved them to Exhibit 25.23.4-25. Revised the special paragraph for non-authorized third parties in Table Scenario (8). (106) IRM 25.23.4.8.4.3(1) Revised Table Scenario (3) to include procedures for sending a closing letter to a taxpayer under the age of 18. Revised Table Scenario (7) to include procedures for sending a closing letter to a taxpayer under the age of 18. Revised Table Scenario (8) to include procedures for sending a closing letter to a taxpayer under the age of 18. IPU 25U3304 issued 05-19-2025. (107) IRM 25.23.4.8.4.3(1) Updated procedures in Table Scenario (7) when research indicates the individual in question is the parent/legal guardian of the dependent. Revised Table Scenario (8) to reorganized current procedures. IPU 25U3246 issued 05-05-2025. (108) IRM 25.23.4.8.6 Created a new subsection for general information for incarcerated taxpayer (prisoner) cases. IPU 25U3218 issued 04-28-2025. (109) IRM 25.23.4.8.6.1 Created a new subsection with streamline determination procedures for cases with incarcerated individuals. IPU 25U3218 issued 04-28-2025. (110) IRM 25.23.4.8.6.2 Created a new subsection with non-streamline determination procedures for cases with incarcerated individuals. IPU 25U3218 issued 04-28-2025. (111) IRM 25.23.4.9.1 Moved to IRM 25.23.4.11. Subsequent IRMs renumbered. IPU 25U3377 issued 06-05-2025 (112) IRM 25.23.4.9.1.1 Moved to IRM 25.23.4.11.1. IPU 25U3377 issued 06-05-2025 (113) IRM 25.23.4.9.1.1.1 Moved to IRM 25.23.4.11.1.1. IPU 25U3377 issued 06-05-2025 (114) IRM 25.23.4.9.1.1.1 Title changed to Identity Theft Allegations on Tax Year 2015 and Prior. IPU 25U0091 issued 01-23-2025. (115) IRM 25.23.4.9.1.1.1 Title changed to Identity Theft Allegations on Tax Year 2014 and Prior. IPU 24U1106 issued 11-06-2024. (116) IRM 25.23.4.9.1.1.1(2)(d) Revised Example for consistency with current procedures when requesting additional information from the taxpayer. IPU 24U1106 issued 11-06-2024. (117) IRM 25.23.4.9.1.1.1(3) Removed information for invalid returns that do not meet streamline criteria and has been moved to a new paragraph. IPU 24U1106 issued 11-06-2024. (118) IRM 25.23.4.9.1.1.1(4) Added a new paragraph to include procedures for invalid returns that meet streamline criteria. Subsequent paragraphs were renumbered. IPU 24U1106 issued 11-06-2024. (119) IRM 25.23.4.9.1.2 Moved to IRM 25.23.4.11.2. IPU 25U3377 issued 06-05-2025 (120) IRM 25.23.4.9.1.3 Moved to IRM 25.23.4.11.3. IPU 25U3377 issued 06-05-2025 (121) IRM 25.23.4.9.1.4 Moved to IRM 25.23.4.11.4. IPU 25U3377 issued 06-05-2025 (122) IRM 25.23.4.9.1.4(5) Added a Reminder for preventing Unpostable Code 178-2 when inputting the TC 560 to extend an expired ASED. IPU 25U0368 issued 03-14-2025. (123) IRM 25.23.4.9.2(2) Added a Note and Reminder in Table Scenario (2) and (4) to advise requirement for the use of the AMA2859 tool for prompt assessments. IPU 25U3218 issued 04-28-2025. (124) IRM 25.23.4.9.2(3) Added a Note and Reminder in Table Scenario (2) to advise requirement for the use of the AMA2859 tool for prompt assessments. IPU 25U3218 issued 04-28-2025. (125) IRM 25.23.4.9.2(5) Added a Reminder for cases when the valid return has not been processed. Revised procedures in Table Scenario (1) through (6). Removed Table Scenario (7) through (11). (126) IRM 25.23.4.9.3(5) Added a Note and Reminder for preventing Unpostable Code 178-2 when inputting the TC 560 to extend an ASED. IPU 25U0368 issued 03-14-2025. (127) IRM 25.23.4.9.3(9) Updated Table Scenario (10) to include guidance on editing a "dummy" return if there are any valid payments sent by the taxpayer. IPU 25U0368 issued 03-14-2025. (128) IRM 25.23.4.10(1) Revised to provide an opening statement and remove references to titles that no longer exist. IPU 25U3377 issued 06-05-2025 (129) IRM 25.23.4.10(2) Added a Reminder for preventing Unpostable Code 178-2 when inputting the TC 560 to extend an expired ASED. IPU 25U0368 issued 03-14-2025. (130) IRM 25.23.4.10(2) Added a Caution to prevent an unpostable (UPC 178-2) when updating the ASED. IPU 24U1251 issued 12-18-2024. (131) IRM 25.23.4.10.1 Updated the title and revised to incorporate information from previous IRMs 25.23.4.10.1, 25.23.4.10.2, 25.23.4.10.3, 25.23.4.10.4, 25.23.4.10.5, 25.23.4.10.6, 25.23.4.10.7, and 25.23.4.10.8. IPU 25U3377 issued 06-05-2025 (132) IRM 25.23.4.10.2 Deleted. IPU 25U3377 issued 06-05-2025. (133) IRM 25.23.4.10.3 Deleted. Subsequent IRMs renumbered. (134) IRM 25.23.4.10.3 Deleted. IPU 25U3377 issued 06-05-2025. (135) IRM 25.23.4.10.4 Deleted. IPU 25U3377 issued 06-05-2025. (136) IRM 25.23.4.10.5 Deleted. IPU 25U3377 issued 06-05-2025. (137) IRM 25.23.4.10.6 Deleted. IPU 25U3377 issued 06-05-2025. (138) IRM 25.23.4.10.7 Deleted. IPU 25U3377 issued 06-05-2025. (139) IRM 25.23.4.10.8 Deleted. Subsequent IRMs renumbered. IPU 25U3377 issued 06-05-2025. (140) IRM 25.23.4.10.8(2) Added a Reminder for input of TC 971 AC 528. Added a Caution in Table Scenario (1) for the use of a selectable paragraph in closing Letter 4674C. (141) IRM 25.23.4.10.9(1) Revised the information to clarify current procedures for reversal of a TC 971 AC 522 when the taxpayer is not a victim of IDT. (142) IRM 25.23.4.10.9(2) Added guidance for cases that have an indication of loss of personally identifying information (PII) or potential Return Preparer Misconduct (RPM) previously in paragraph (4). Removed the required actions for cases determined to be NOIDT when taxpayer identified identity theft and moved to a new Table in paragraph (3). (143) IRM 25.23.4.10.9(3) Added a new Table listing the required account actions needed for all cases with a NOIDT determination. Revised the required actions for cases determined to be NOIDT when IRS identified identity theft and moved to a new Table. (144) IRM 25.23.4.10.9(4) Removed guidance for cases with allegations of return preparer misconduct and moved to paragraph (2). Added guidance for the issuance of a closing letter for taxpayer identified identity theft claims with a NOIDT determination. (145) IRM 25.23.4.10.9(5) Added a new paragraph to include guidance for creating a separate case when the account requires additional actions for NOIDT determinations. Subsequent paragraphs were renumbered. (146) IRM 25.23.4.10.9(6) Revised current guidance for IDTVA-Specialty Teams only. Added a new Reminder for cases with Exam involvement. (147) IRM 25.23.4.10.12.4(2) Revised guidance on creating new CII cases for clarification. Added a Caution for reassignment of an existing CII case for clarification. IPU 25U3304 issued 05-19-2025. (148) IRM 25.23.4.10.12.4(2) Added a Note for clarification. Added an Exception for cases involving NOIDT procedures for Invalid Joint Election (IJE) issues. IPU 25U0368 issued 03-14-2025. (149) IRM 25.23.4.10.13(1) Revised Table Scenario (1), (2), (3), (4), and (5) to clarify procedures for reversing a TC 971 AC 522 UNWORK. IPU 24U1106 issued 11-06-2024. (150) IRM 25.23.4.10.14(5) Revised to clarify dependent IDT procedures for cases that can be taxpayer identified or IRS identified. Revised Table Scenario (1) and (2) to input the applicable IDT closing indicator. IPU 25U3218 issued 04-28-2025. (151) IRM 25.23.4.10.15(2) (d) Revised the additional actions required on an account for clarification purposes only. IPU 25U3218 issued 04-28-2025. (152) IRM 25.23.4.10.15(2)(d) Added an Exception for cases involving NOIDT procedures for Invalid Joint Election (IJE) issues. IPU 25U0368 issued 03-14-2025. (153) IRM 25.23.4.10.15(3) (c) Revised the additional actions required on an account for clarification purposes only. IPU 25U3218 issued 04-28-2025. (154) IRM 25.23.4.11 New section for non-streamline cases. Current information includes guidance previously provided in IRM 25.23.4.9.1. Previous IRM has been moved to IRM 25.23.4.13. IPU 25U3377 issued 06-05-2025. (155) IRM 25.23.4.11.1 New subsection for non-streamline with CSED expired or imminent. Current information includes guidance previously provided in IRM 25.23.4.9.1.1. Previous IRM has been moved to IRM 25.23.4.13.1. IPU 25U3377 issued 06-05-2025. (156) IRM 25.23.4.11.1 Title changed to Identity Theft (IDT) Expedite Operations Assistance Requests (OARs) - (Cases that Meet Economic Burden Criteria 1-4 and Contain Unprocessed Original Returns; TC 976 Documents). IPU 25U0368 issued 03-14-2025. (157) IRM 25.23.4.11.1(1) Removed the Austin campus as the only IDTVA-A Adjustments TAS Liaison. Removed Caution regarding TC 977 posted on CC RTVUE and TRDBV. IPU 25U0368 issued 03-14-2025. (158) IRM 25.23.4.11.1(2) Revised Table Scenario (2) for clarification. (159) IRM 25.23.4.11.1(3) Revised 3rd bullet to include a reference for procedures when a case contains an unprocessed original return. Revised 5th bullet to remove the Austin campus. IPU 25U0368 issued 03-14-2025. (160) IRM 25.23.4.11.1(7) Removed the Austin campus as the only IDTVA-A Directorate. Revised 1st bullet to remove the Austin campus. Revised 3rd bullet to include a reference for procedures when a case contains an unprocessed original return. IPU 25U0368 issued 03-14-2025. (161) IRM 25.23.4.11.1.1 New subsection for non-streamline with Tax Year 2015 and prior. Current information includes guidance previously provided in IRM 25.23.4.9.1.1.1. IPU 25U3377 issued 06-05-2025. (162) IRM 25.23.4.11.2 New subsection for non-streamline move conditions. Current information includes guidance previously provided in IRM 25.23.4.9.1.2. Previous IRM has been moved to IRM 25.23.4.13.2. IPU 25U3377 issued 06-05-2025. (163) IRM 25.23.4.11.2(5) Revised current procedures for returning an OAR for clarification. IPU 25U0368 issued 03-14-2025. (164) IRM 25.23.4.11.3 New subsection for non-streamline not moving procedures. Current information includes guidance previously provided in IRM 25.23.4.9.1.3. IPU 25U3377 issued 06-05-2025. (165) IRM 25.23.4.11.4 New subsection for non-streamline move procedures. Current information includes guidance previously provided in IRM 25.23.4.9.1.4. IPU 25U3377 issued 06-05-2025. (166) IRM 25.23.4.11.4.1 New subsection for completing manual account transfers using Form 12810. Current information includes guidance previously provided in IRM 25.23.4.9.1.4. IPU 25U3377 issued 06-05-2025. (167) IRM 25.23.4.13 Current information was previously found in IRM 25.23.4.11. Previous IRM has been moved to IRM 25.23.10.4.7. IPU 25U3377 issued 06-05-2025. (168) IRM 25.23.4.13.1 Current information was previously found in IRM 25.23.4.11.1. Previous IRM has been moved to IRM 25.23.10.4.7.1. IPU 25U3377 issued 06-05-2025. (169) IRM 25.23.4.13.1(2) Revised Table Scenario (4) procedure when closing the CII case. IPU 24U1251 issued 12-18-2024. (170) IRM 25.23.4.13.2 Current information was previously found in IRM 25.23.4.11.2. Previous IRM has been moved to IRM 25.23.10.4.7.2. IPU 25U3377 issued 06-05-2025. (171) IRM 25.23.4.13.3 Moved to IRM 25.23.10.4.7. IPU 25U3377 issued 06-05-2025. (172) IRM 25.23.4.13.3.1 Moved to IRM 25.23.10.4.7.1. IPU 25U3377 issued 06-05-2025. (173) IRM 25.23.4.13.3.2 Moved to IRM 25.23.10.4.7.2. IPU 25U3377 issued 06-05-2025. (174) IRM 25.23.4.13.3.2(2) Revised current procedures for docketed cases received from Appeals for clarification. IPU 25U3218 issued 04-28-2025. (175) IRM 25.23.4.13.3.3 Moved to IRM 25.23.10.4.7.3. IPU 25U3377 issued 06-05-2025. (176) IRM 25.23.4.15(3) Added a Note and Reminder for preventing Unpostable Code 178-2 when inputting the TC 560 to extend an ASED. Added a new Table Scenario (4) to include procedures for returns that have posted to MFT 32 and the ASED is barred. Subsequent Table Scenarios were renumbered. IPU 25U0368 issued 03-14-2025. (177) IRM 25.23.4.17(10) Updated terminology "Revenue Officer" to "Group Manager" for rejected Form 2209 referrals. IPU 24U1251 issued 12-18-2024. (178) IRM 25.23.4.18(5) Revised Table Scenario (4) for translation services provided when determining what language to use when sending a letter. (179) IRM 25.23.4.18(5) Added a new Note for determining the language to use when sending a letter for clarification. IPU 25U3218 issued 04-28-2025. (180) IRM 25.23.4.18(6) Added a new paragraph to include information for covered relationship determinations and account actions. Subsequent paragraphs were renumbered. IPU 25U3218 issued 04-28-2025. (181) IRM 25.23.4.18(7) Added a new paragraph to include a Table to determine how to send a closing letter to additional impacted individuals. Subsequent paragraphs were renumbered. IPU 25U3218 issued 04-28-2025. (182) IRM 25.23.4.18.1(1) Revised Bullet #3 to expand on scenarios for the use of closing Letter 4674C. IPU 24U1106 issued 11-06-2024. (183) IRM 25.23.4.18.1(2) Removed the mention of specific letters when using the IAT Letters tool. IPU 24U1106 issued 11-06-2024. (184) IRM 25.23.4.18.1(4) Added a new paragraph to include information to clarify the exclusion of acknowledgement letters. Subsequent paragraphs were renumbered. IPU 24U1106 issued 11-06-2024. (185) IRM 25.23.4.18.1(5) Revised 3rd bullet to remove CP 701S that was superseded by CP01S. (186) IRM 25.23.4.18.1(5) Revised time frame from 493 days to 582 days. IPU 25U3377 issued 06-05-2025. (187) IRM 25.23.4.18.1(5) Revised time frame from 640 days to 493 days. IPU 25U0091 issued 01-23-2025. (188) IRM 25.23.4.18.1(9) Revised time frame from 493 days to 582 days. Revised time frame in the Example for consistency. IPU 25U3377 issued 06-05-2025. (189) IRM 25.23.4.18.1(9) Revised time frame from 640 days to 493 days. Revised time frame in the example for consistency. IPU 25U0091 issued 01-23-2025. (190) IRM 25.23.4.18.1(9) Revised information for clarification and updated the timeframe for consistency within the IRM. IPU 24U1106 issued 11-06-2024. (191) IRM 25.23.4.18.1(11) Added a Reminder when issuing Letter 4674C for individuals under the age of 18. (192) IRM 25.23.4.18.1(13) Removed all special paragraphs and moved to Exhibit 25.23.4-25. (193) IRM 25.23.4.18.1(13) Revised the Case Scenario special paragraph for "Taxpayer is under age 18" . IPU 25U3304 issued 05-19-2025. (194) IRM 25.23.4.18.1(13) Revised to reorganize current procedures when sending an IDT closing letter to taxpayer's regarding supplemental information for IP PINs. IPU 25U3218 issued 04-28-2025. (195) IRM 25.23.4.18.1(13) Added an Exception for taxpayers under the age of 18 under "General Information" . Revised information to clarify use of existing selectable paragraphs or special paragraphs when issuing closing Letter 4674C. Added an Exception for taxpayers under the age of 18 under "Already Enrolled" . IPU 25U0368 issued 03-14-2025. (196) IRM 25.23.4.18.1(13) Added a Note to include use of special paragraphs for certain case types when issuing Letter 4674C. Added an Exception for taxpayers under the age of 18 when issuing Letter 4674C. Revised special paragraph for "Already Enrolled" scenario. IPU 25U0091 issued 01-23-2025. (197) IRM 25.23.4.18.1(13) Updated to clarify the first special paragraph. Revised special paragraph for "Already Enrolled" . IPU 24U1251 issued 12-18-2024. (198) IRM 25.23.4.18.1(14) Revised the Reminder for directing taxpayers to Online Services. (199) IRM 25.23.4.18.1(14) Added a Reminder to not direct taxpayers under the age of 18 to Online Services. IPU 25U0091 issued 01-23-2025. (200) IRM 25.23.4.18.1(15) Revised information for clarification on establishing or updating the entity to a Service Center Address for a deceased taxpayer. IPU 24U1106 issued 11-06-2024. (201) IRM 25.23.4.18.1(18) Revised the amount of tax years that can be manually input when sending Letter 4674C. IPU 24U1106 issued 11-06-2024. (202) IRM 25.23.4.18.1(19) Added a Note to include information when addressing the taxpayer's account issues for multiple tax years with different case determinations. IPU 24U1106 issued 11-06-2024. (203) IRM 25.23.4.18.1(21) Revised Table Scenario (2) to remove CP 701S that was superseded by CP01S and add guidance to issue Letter 4674C for individuals under age 18 with the appropriate contact information. (204) IRM 25.23.4.18.1(21) Revised the Exception to include a third party when sending closing Letter 0135C. Added a Reminder for Table Scenario (1) to indicate that closing an account with a TC 971 AC 506 will not generate a systemic closing letter. IPU 25U0368 issued 03-14-2025. (205) IRM 25.23.4.18.1(23) Revised for clarification when sending a closing letter for cases filed married filing jointly. IPU 25U3327 issued 05-23-2025. (206) IRM 25.23.4.18.1(23) Revised for clarification when sending a closing letter for cases filed married filing jointly. IPU 25U3304 issued 05-19-2025. (207) IRM 25.23.4.18.5(3) Updated the Note for clarification of the use of idle codes for IDTVA employees 0962 and 0592 series. IPU 24U1106 issued 11-06-2024. (208) IRM 25.23.4.18.5(8) Removed Figure 25.23.4-1 due to change in telephone systems. IPU 24U1106 issued 11-06-2024. (209) IRM 25.23.4.19(1) Added a reference for a complete list of language translations. IPU 25U0368 issued 03-14-2025. (210) IRM 25.23.4.19(3) Revised instructions for designated individuals requesting translation services to Linguistic Policy, Tools and Services (LPTS). IPU 25U3218 issued 04-28-2025. (211) IRM 25.23.4.19(4) Added a new Note to provide instructions in the event changes are needed to the final version of an original source document. IPU 25U3218 issued 04-28-2025. (212) IRM 25.23.4.19(5) Revised existing information for consistency with IRM 25.23.4.18(5) regarding translation services that must be included as a CII note. IPU 24U1106 issued 11-06-2024. (213) IRM 25.23.4.19.1(1) Revised instructions for requesting translation services for any language other than Spanish. Subsequent paragraphs were renumbered. IPU 25U3218 issued 04-28-2025. (214) IRM 25.23.4.19.1(2) Revised instructions for designated individuals requesting translation services to Linguistic Policy, Tools and Services (LPTS). IPU 25U3218 issued 04-28-2025. (215) IRM 25.23.4.19.1(4) Added new paragraph to include instructions in the event changes are needed to the final version of an original source document. IPU 25U3218 issued 04-28-2025. (216) IRM 25.23.4.20.3(6) Added a new paragraph to include information for using reason codes. Subsequent paragraphs were renumbered. (217) IRM 25.23.4.20.3(7) Added a new paragraph to include information when inputting an adjustment to reduce EIP. Subsequent paragraphs were renumbered. (218) IRM 25.23.4.20.3.1(2) Added a new paragraph to include guidance on inputting a TC 971 AC 850. Subsequent paragraphs were renumbered. (219) IRM 25.23.4.20.3.1(3) Revised bullet listing of actions needed when EIP 1 and/or EIP 2 was computed based on a valid return. (220) IRM 25.23.4.20.3.1(5) Revised Table Scenario (1) and (2) to include procedures of actions needed when EIP 1 and/or EIP 2 was computed based on an invalid (IDT) return meeting streamline procedures. Removed Table Scenario (3). (221) IRM 25.23.4.20.3.1(6) Revised Table Scenario (1) and (2) to include procedures of actions needed when EIP 1 and/or EIP 2 was computed based on an invalid (IDT) return meeting non-streamline procedures. Removed Table Scenario (3). (222) IRM 25.23.4.20.3.1(7) Revised Table Scenario (1), (2) and (3) to include procedures of actions needed when EIP 1 and/or EIP 2 was computed based on an invalid return meeting IJE criteria. (223) IRM 25.23.4.20.3.1(8) Revised Table Scenario (1) and (2) letter requirements specific to EIP 1 and/or EIP 2 issues. (224) IRM 25.23.4.20.3.2(2) Removed all previous information related to issuance of EIP 3. Revised to include procedures to input a TC 971 AC 850 to flip future refunds to paper. (225) IRM 25.23.4.20.3.2(3) Removed all previous information related to considerations of eligibility of EIP3. Revised actions required on an account when the invalid taxpayer was issued EIP 3. (226) IRM 25.23.4.20.3.2(4) Removed all previous guidance for adjusting an account to reduce EIP 3. Revised Table Scenario (1) and (2) procedures for cases that meet streamline criteria. Removed Table Scenario (3). (227) IRM 25.23.4.20.3.2(5) Removed all previous information when a TIN-related math error was set during the original processing of a valid TY 2020. Revised Table Scenario (1) and (2) for cases that meet non-streamline criteria. Removed Table Scenario (3). (228) IRM 25.23.4.20.3.2(6) Deleted paragraph with previous procedures to determine the appropriate account actions required to address invalid direct deposit information. Subsequent paragraphs were renumbered. (229) IRM 25.23.4.20.3.2(7) Revised table procedures for letter requirements specific to EIP 3. (230) IRM 25.23.4.20.3.2(8) Added guidance when EIP 3 has been returned and the systemic reversal of the credits posted. (231) IRM 25.23.4.20.5(1) Revised to remove the mention of only EIP 1 and EIP 2 regarding Economic Impact Payment(s). (232) Exhibit 25.23.4-1(1) Added a new paragraph to clarify existing procedures for the Decision Tree. Subsequent paragraphs were renumbered. IPU 25U3246 issued 05-05-2025. (233) Exhibit 25.23.4-4(4) Added a Reminder for IDTVA-A employees reassigning transcripts to Specialty. IPU 25U0368 issued 03-14-2025. (234) Exhibit 25.23.4-4(4) Revised Table Scenario (2) to clarify systemic duplicate filing cases assigned on CC TXMOD. IPU 25U0091 issued 01-23-2025. (235) Exhibit 25.23.4-5(3) Added a Reminder for IDTVA-A and IDTVA Specialty employees to review the applicable CII reassignment listing for reassignment of certain case types. IPU 25U3218 issued 04-28-2025. (236) Exhibit 25.23.4-5(3) Revised Reminder for IDTVA-A employees for clarification. IPU 25U0368 issued 03-14-2025. (237) Exhibit 25.23.4-5(3) Added a Reminder to clarify procedures for transcripts that should not be reassigned to IDTVA Specialty Functions. IPU 24U1106 issued 11-06-2024. (238) Exhibit 25.23.4-5(11) Revised Table Scenario (1) and (9) to update the reassignment holding number for specific IDT case types. Revised Table Scenario (3) to refer cases with a -L freeze and AIMS status based on the listing in SERP. IPU 25U0091 issued 01-23-2025. (239) Exhibit 25.23.4-5(11) Added new Table Scenario (15) in the table to provide guidance for cases with AUR involvement. Subsequent table scenarios were renumbered. Revised Table Scenario (18) to clarify the presence of account conditions for open ASFR case(s). IPU 24U1251 issued 12-18-2024. (240) Exhibit 25.23.4-5(11) Updated Table Scenario (14) to clarify which Priority Code (PC) to use for cases with Statutory Notices. IPU 24U1106 issued 11-06-2024. (241) Exhibit 25.23.4-6(1) Removed table for IDTVA-I - Identity Protection Specialized Unit (IPSU) locations. Subsequent paragraphs were renumbered. (242) Exhibit 25.23.4-6(3) Revised campus locations for IDTVA Specialty Function groups in Exam and ACSS. IPU 24U1106 issued 11-06-2024. (243) Exhibit 25.23.4-7(1) Removed Category Code IDT9/IDTS9 from IDTVA-A and IDTVA-I table. (244) Exhibit 25.23.4-9(1) Revised Category Code IDT8/IDS8 with RIVO indicators and removed deceased taxpayers as a defining characteristic. (245) Exhibit 25.23.4-9(1) Revised Table to clarify Category Codes for tax-related identity theft issues. IPU 25U3218 issued 04-28-2025. (246) Exhibit 25.23.4-10(1) Revised the 5th bullet to clarify the issuance of Letter 4674C for taxpayer's that filed as married filing jointly. IPU 25U3218 issued 04-28-2025. (247) Exhibit 25.23.4-10(1) Revised the amount of tax years that can be manually input when sending Letter 4674C. IPU 24U1106 issued 11-06-2024. (248) Exhibit 25.23.4-12(1) Removed Category Code IDT9/IDTS9 from the table. (249) Exhibit 25.23.4-15(8) Removed instructions in Table Scenario (3) and (4) regarding contacting IDTVA Functional Liaison to request a copy of the case referred. Revised the Note to clarify the use of internal research utilizing images on AMS. IPU 24U1106 issued 11-06-2024. (250) Exhibit 25.23.4-15(9) Revised instructions on creating a case on CII when a referral cannot be located. IPU 24U1106 issued 11-06-2024. (251) Exhibit 25.23.4-16(2) Removed the mention of separate tabs for IMF and BMF accounts listed on the report from ITVA HQ Balance Due Receipts Listing. IPU 25U3377 issued 06-05-2025. (252) Exhibit 25.23.4-21(3) Revised Table Scenario (2) to clarify the requirement when inputting TC 971 AC 850. IPU 25U3246 issued 05-05-2025. (253) Exhibit 25.23.4-21(3) Updated Table Scenario (6) 4th Bullet to include the use the appropriate Action Code to reverse the indicator for the American Opportunity Credit (AOTC). IPU 25U0091 issued 01-23-2025. (254) Exhibit 25.23.4-21(4) Added new Table Scenario (8) to include guidance for inadvertent disclosure of sensitive information. (255) Exhibit 25.23.4-21(4) Added new Table Scenario (7) to include procedures for IDRS CC TXMOD reflects an amount in the "PTC-EXP-AMT" field. IPU 25U0368 issued 03-14-2025. (256) Exhibit 25.23.4-21(8) Revised Table Scenario (11) If statement clarified to indicate the reversal is only input when directed. IPU 25U3377 issued 06-05-2025. (257) Exhibit 25.23.4-21(8) Added a new Note in Table Scenario (4) and (5) for the Get Transcript Online (GTO) application decommissioned in December 2024. IPU 25U3218 issued 04-28-2025. (258) Exhibit 25.23.4-21(8) Revised Table Scenario (11) to clarify procedures when reversing an existing IDT indicator. IPU 25U0091 issued 01-23-2025. (259) Exhibit 25.23.4-23(1) Revised Example 1, 2, 3, and 4 to remove gender-neutral content to comply with executive order(s). (260) Exhibit 25.23.4-23(1) Added new Example 5 for Invalid Return and Income Related IDT for complex case types. Added new Example 6 for Employment Related IDT vs Income Related IDT for complex case types. IPU 25U3304 issued 05-19-2025. (261) Exhibit 25.23.4-25(4) Revised Example 1, 2, and 3 to place all special paragraph into Table Scenarios. Added a new Example to include special paragraphs for IP PIN case scenario issues. (262) Exhibit 25.23.4-25(4) Revised fourth selectable paragraph for taxpayers under age 18 that may be eligible for an Identity Protection Personal Identification Number (IP PIN). IPU 25U3377 issued 06-05-2025. (263) Exhibit 25.23.4-25(4) Updated the Exception to change as a Reminder for Example 1, 2 and 3 to provide clarification for taxpayers under the age of 18. Revised header of Example 3 to "Income Related Identity Theft (IDT)." IPU 25U3218 issued 04-28-2025. (264) Exhibit 25.23.4-25(4) Added new Exception for taxpayers under the age of 18 in Example 1, 2, and 3. IPU 25U0368 issued 03-14-2025. (265) Exhibit 25.23.4-25(4) Revised Example 1: Dependent Identity Theft (IDT) to include a list of selectable paragraphs not to be used when issuing closing Letter 4674C. Revised special paragraphs for Example 1: Dependent IDT. Added new Example 3 to include a special paragraph for non-tax related case types. IPU 25U0116 issued 01-28-2025. (266) Exhibit 25.23.4-25 Created a new exhibit for closing letter paragraph selections. IPU 25U0091 issued 01-23-2025. (267) IRM 25.23.4, Various editorial changes and IRM cross references updated throughout the entire IRM. IPU 25U3377 issued 06-05-2025. Effect on Other Documents IRM 25.23.4 dated 09-05-2024 (effective 10-01-2024) is superseded and incorporates Identity Theft Case Processing IRM Procedural Updates (IPUs): • IPU 24U1106 (issued 11-06-2024) • IPU 24U1251 (issued 12-18-2024) • IPU 25U0091 (issued 01-23-2025) • IPU 25U0116 (issued 01-28-2025) • IPU 25U0368 (issued 03-14-2025) • IPU 25U3218 (issued 04-28-2025) • IPU 25U3246 (issued 05-05-2025) • IPU 25U3304 (issued 05-19-2025) • IPU 25U3327 (issued 05-23-2025) • IPU 25U3377 (issued 06-05-2025) Audience The provisions in this manual apply to all divisions, functional units, employees, and contractors within the IRS working identity theft (IDT) cases. Effective Date (10-01-2025) LuCinda Comegys, Director Accounts Management Taxpayer Services

# Program Scope and Objectives

25.23.4.1 (10-21-2019) Program Scope and Objectives Purpose - This IRM section provides guidance for resolving identity theft (IDT) casework. Audience - The provisions in this section apply primarily to employees assigned to the Identity Theft Victim Assistance (IDTVA) directorate, but may be used by all divisions, functional units, employees and contractors within the IRS working identity theft cases. Policy Owner - The owner of the policies contained herein is the Director, Accounts Management. Program Owner - The Director of Accounts Management is the program owner. Primary Stakeholders - The primary stakeholders are organizations that Accounts Management collaborates with, such as Return Integrity and Compliance Services (RICS), Compliance and Submission Processing. Program Goals - Program goals for this type of work are included in the Accounts Management Program Letter.

# Background

25.23.4.1.1 (10-01-2017) Background Employees in the Identity Theft Victim Assistance (IDTVA) organization process identity theft (IDT) claims and respond to IDT victims' phone inquiries.

# Authority

25.23.4.1.2 (10-01-2024) Authority Refer to IRM 1.2.1.13, Policy Statements for Customer Account Services Activities, for information. The Taxpayer Advocate Service is an independent organization within the Internal Revenue Service (IRS), led by the National Taxpayer Advocate, that helps taxpayers and protects taxpayer rights. TAS offers free help to taxpayers when a tax problem is causing a financial difficulty, when they've tried and been unable to resolve their issue with the IRS, or when they believe an IRS system, process, or procedure just isn't working as it should. TAS strives to ensure that every taxpayer is treated fairly and knows and understands their rights under the Taxpayer Bill of Rights TAS has at least one taxpayer advocate office located in every state, the District of Columbia, and Puerto Rico.

# Roles and Responsibilities

25.23.4.1.3 (10-01-2025) Roles and Responsibilities The Taxpayer Services Commissioner has overall responsibility for the policy related to this IRM which is published on a yearly basis. Additional information is found in IRM 1.1.13.6.3, Accounts Management (AM), and IRM 21.1.1, Accounts Management and Compliance Services Overview.

# Program Management and Review

25.23.4.1.4 (10-01-2024) Program Management and Review Program Reports - For reports concerning quality, inventory, aged listing, refer to IRM 1.4.16, Accounts Management Guide for Managers. Aged listings can also be reviewed by accessing Control Data Analysis, Project PCD. They are located on the Control-D/Web Access server, which has a login program control. Program Effectiveness - Program Effectiveness is determined by Accounts Management's employees successfully using IRM guidelines to perform necessary account actions and duties effectively and efficiently.

# Program Controls

25.23.4.1.5 (10-01-2024) Program Controls Goals, measures and operating guidelines are provided in the yearly Program Letter. Quality data and guidelines for measurement is referenced in IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS) and Electronic Products and Services Support.

# Terms and Acronyms

25.23.4.1.6 (10-01-2025) Terms and Acronyms Refer to the table below for a list of acronyms used throughout IRM 25.23.4. Note: This list may not be all inclusive. Acronyms Definitions AC Action Code ACSS Automated Collection System Support AdvCTC Advanced Child Tax Credit AM Accounts Management AMS Accounts Management System APTC Advance Premium Tax Credit ARPA American Rescue Plan Act ASED Assessment Statute Expiration Date ASFR Automated Substitute for Return AUR Automated Underreporter BFS Bureau of Fiscal Service BMF Business Master File CARES Coronavirus Aid, Relief, and Economic Security Act CC Command Code CCA Complete Case Analysis CDS Centralized Delivery Service CEAS Correspondence Examination Automation Support CI Criminal Investigation CII Correspondence Imaging Inventory CN Common Number CSR Customer Service Representative DITA Designated Identity Theft Adjustment EGC Employee Group Code EIN Employer Identification Number EIP Economic Impact Payment ES Estimated Tax EUP Employee User Portal FRP Frivolous Return Program FTC Federal Trade Commission FTF Failure to File FTP Failure to Pay HC Hold Code HQ Headquarters IAT Integrated Automation Technologies ICCE Integrated Customer Communication Environment (System) ICT Image Control Team IDRS Integrated Data Retrieval System IDT Identity Theft IDTVA Identity Theft Victim Assistance IDTVA-A Identity Theft Victim Assistance Accounts Management IJE Invalid Joint Election IMF Individual Master File IPSU Identity Protection Specialized Unit (inventory programs) IRM Internal Revenue Manual IRSN Internal Revenue Service Number ITIN Individual Taxpayer Identification Number ITVA HQ Identity Theft Victim Assistance Headquarters MeF Modernized e-File MXEN Mixed Entity OAR Operations Assistance Request P&A Planning & Analysis PC Priority Code POC Point of Contact RGS Report Generation Software RICS Return Integrity and Compliance Services RIVO Return Integrity & Verification Operations RO Revenue Officer RPD Return Processable Date RPM Return Preparer Misconduct RPO Return Preparer Office RRC Recovery Rebate Credit RSED Refund Statute Expiration Date RTF Return Transaction File SC Source Code SCRM Scrambled SSN SDC Scheme Development Center SLA Service Level Agreement SP Submission Processing SSA Social Security Administration SSN Social Security Number TAC Taxpayer Assistance Center TAS Taxpayer Advocate Service TC Transaction Code TCIS Treasury Check Information System TIF Taxpayer Information File TIN Taxpayer Identification Number TOP Treasury Offset Program TPP Taxpayer Protection Program

# Related Resources

25.23.4.1.7 (04-09-2021) Related Resources This section provides Individual Master File (IMF) CSRs/TEs with the resources and guidance to resolve taxpayer (TP) identified and IRS identified identity theft cases, including general procedures for cases with Compliance involvement. The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For additional information about the TBOR, see Taxpayer Bill of Rights. CSRs/TEs should utilize and become familiar with the IRMs below in conjunction with IRM 25.23.4 to aid them in accurately resolving their case and/or routing cases to other functions, when applicable. IRM 3, Submission Processing IRM 4, Examination Process IRM 5, Collecting Process IRM 20.1, Penalty Handbook IRM 21, Customer Account Services IRM 25, Special Topics IRM 25.23.1, Identity Protection and Victim Assistance – Policy Guidance IRM 25.23.2, Identity Protection and Victim Assistance - General Case Processing IRM 25.23.3, IMF Non-Tax-Related IDT and Specialized Programs IRM 25.23.9, BMF Identity Theft Processing IRM 25.23.10, Compliance Identity Theft Case Processing IRM 25.23.11, Business Master File (BMF) Identity Theft Procedures for Accounts Management IRM 25.23.12, IMF Identity Theft Toll-Free Guidance IRM 25.24.1, Return Preparer Misconduct Victim Assistance - General Overview IRM 25.24.2, Return Preparer Misconduct Victim Assistance Specialized Accounts Management Processing Employees of Identity Theft Victim Assistance (IDTVA - Accounts Management and Specialty Functions) are responsible for keeping current with the following resources: Identity Theft Victim Assistance (IDTVA) Service Level Agreement (SLA) Identity Theft Memorandums of Understanding (MOUs) and Interim Guidance Memoranda (IGMs) Identity Theft Victim Assistance Hub (IDTVA Hub) ID Theft Resource Page and Technical Communication Documents (TCDs) SERP Alerts Employees of IDTVA are also responsible for keeping current with IRM provisions specific to resolving Compliance identity theft account referrals from: Automated Collection System Support (ACSS) Automated Substitute for Returns (ASFR) Automated Underreporter (AUR) Compliance Services Collection Operation (CSCO) Monitoring Offer In Compromise (MOIC) Centralized Offer in Compromise (COIC) Doubt as to Liability (DATL) Correspondence Examination (Exam) Taxpayer Advocate Service (TAS)

# Identity Theft (IDT) Paper Process Overview

25.23.4.2 (10-01-2023) Identity Theft (IDT) Paper Process Overview This section of the IRM provides guidance primarily for use by IDTVA for the research and resolution of tax-related identity theft cases. Additional information in IRM 25.23.10, Compliance Identity Theft Case Processing, provides procedures specific to cases involving compliance issues. Cases may initially be taxpayer identified identity theft claims or IRS identified. Note: Per Exhibit 25.23.1-1, Glossary of Identity Protection Terms and Definitions, an identity theft claim refers to any combination of Form 14039, Identity Theft Affidavit, or a police report or, for other than Compliance functions, a written statement from the taxpayer that they are, or may be, a victim of identity theft. Cases that are referred to IDTVA from a Compliance function must include a Form 14039 or police report to be considered an identity theft claim. Identity theft returns filed to generate a fraudulent refund may show the following characteristics: Refundable credits claimed, no Form W-2 income included Adoption credit First-time Homebuyer Credit Refundable Education Credit (Form 8863) Only Education Credits of $1,000 claimed on return Cases generally fall into one of two treatment streams: Streamline identity theft case processing - the identity theft return can be nullified Non-Streamline identity theft case processing - the identity theft return cannot be nullified and must be processed to an IRSN When possible, cases will be resolved based on information provided and/or directly available. If a determination cannot be made based on the information provided and/or directly available, guidance will be followed for communicating with the taxpayer(s). Steps for resolution of IDT cases are generally based on one of the following scenarios: Invalid return/valid return - no lost refund Invalid return/valid return - lost refund Valid return/invalid return - no lost refund Two or more invalid returns (no valid return) - no lost refund Two or more invalid returns (no valid return) - lost refund One invalid return only - no lost refund One invalid return only - lost refund The subsections that follow provide details on the assignment of work, management of inventory, and applicable research and resolution processes, etc. ITVA headquarters provides various reports to IDTVA P&A for inventory management purposes. Recommended uses for the reports are outlined individually. AUR Analytics Data Retrieval (ADR) Report - See Exhibit 25.23.4-15, ITVA HQ AUR ADR Report - For Use by IDTVA P&A and Designated Individuals Only. Balance Due Receipts Listing - See Exhibit 25.23.4-16, ITVA HQ Balance Due Receipts Listing - For Use by IDTVA P&A Only. Disaster -O Freeze Listing - See Exhibit 25.23.4-17, ITVA HQ Disaster -O Freeze Listing - For Use by IDTVA P&A Only. Freeze Code -L Listing - See Exhibit 25.23.4-18, ITVA HQ Freeze Code -L Listing - For Use by IDTVA P&A Only. Freeze Code Z Listing - See Exhibit 25.23.4-19, ITVA HQ Freeze Code Z Listing - For Use by IDTVA P&A Only. On a weekly basis, IDTVA P&A ensures site adherence to inventory management requirements outlined in IRM 1.4.16.5.6, Monitoring the Automated Age Listing (AAL), in an effort to appropriately prioritize cases while addressing old age inventory and unnecessary multiple controls.

# Case Assignment and Inventory Management - General Guidance

25.23.4.3 (03-11-2024) Case Assignment and Inventory Management - General Guidance IDTVA employees with IDT/RPM inventory are assigned a phone extension so taxpayers may contact them directly with questions about the status of their cases. Employees must be signed into their routing extension when they are not answering calls on a toll-free line. Refer to IRM 25.23.4.18.5, Taxpayer Calls on Identity Theft (IDT) Cases (IDTVA Paper Employees Only), for additional information. In general, identity theft cases will be scanned into the Correspondence Imaging System (CII) and assigned to employees through the Centralized Work Distribution (CWD) process. The Correspondence Imaging System (CII) has been updated with identity theft CII Logic to assign/associate newly scanned work to CSRs with existing controls. This is to be consistent with note/guidance under (2) of IRM 21.5.2.3, Adjustment Guidelines - Research. The Automated Age Listing (AAL) and Multiple Control Listing (MCL) are used to monitor and manage assigned inventory. On a quarterly basis, ITVA will provide a listing of statute imminent cases (based on the current ASED on the module). Statute year cases will be prioritized for statute clearing purposes. Refer to Exhibit 25.23.4-24 , IDTVA Statute Clearing. Identity theft cases are priority work per IRM 25.23.2.2.2, Priority Handling of Identity Theft Cases. When the CII case is controlled to an incorrect Category Code, update CII to reflect the correct case type and OFP. If multiple controls are present on your case, link cases following guidance in IRM 21.5.1.5.1, CII General Guidelines. Use the table in Exhibit 25.23.4-7, Identity Theft (IDT) Multiple Control Decision Document, to determine the appropriate IDT Category Code. Example: If an IDT4 was recently assigned to you because you have an open IDS3 or IDT3 for the same tax period, you would update the surviving Category Code to IDS1 or IDT1. If you have an IDI1, IDS1 or IDT1 for a different tax period, you must manually revise the IDT4 to the appropriate IDI/IDS/IDT category on CII. Certain identity theft determinations and/or resolution processes require lead/manager approval prior to moving forward with account actions. Document your research and determination or action requiring approval in a CII case note prior to suspending the case to your work leader. Generally, the lead/manager will provide a response within 3 business days, documenting their concurrence or disagreement in a CII case note. Identity theft cases will be closed with a TC 290 .00 with RC 139 when a corrective adjustment is not necessary. Exception: For refund related IDT (i.e., invalid return filed), do not create a CII control or input a TC 290 .00 with a Reason Code 139 if the following conditions exist: - There is no TC 150 present on the account. - No tax module exists. - The module is in retention (unless reversing a tax offset will create a balance due or it is necessary to resolve the taxpayer issue to make the taxpayer whole). - When an impacted module is not active on IDRS CC: TXMOD and is not yet in retention. Do not input IDRS CC: MFREQ. IDTVA Specialty Function teams utilize CII. If a case is open in one of the Compliance functions (AUR, Exam, ASFR, etc.) with an IDT allegation, do not refer the case to the Compliance function. Reassign the case to the appropriate IDTVA Specialty Function following Exhibit 25.23.4-5, IDTVA Routing Matrix. In addition to guidance found in IRM 21.5.1.4.2.6, Adjustments Case Management by Customer Service Representative (CSR), or Tax Examiners (TE), IDTVA employees will review the identity theft inventory on their Automated Age Listing (AAL) to identify and take action, when appropriate, to refer cases to IDTVA Specialty Functions and/or interrupt collection activity. Failure to make timely referrals to IDTVA Specialty Functions can result in default assessments requiring reconsideration activities and failure to interrupt collection activity results in undue burden, further victimizing the taxpayer. Reminder: If the taxpayer's account reflects a MF or SC collection status, refer to guidance in IRM 25.23.4.12, Collection Activity - Form 14394/13794, to interrupt collection activity while the case is worked.

# CII and IDRS Case Controls

25.23.4.3.1 (10-01-2025) CII and IDRS Case Controls All identity theft (IDT) cases are required to have a CII control. The Image Control Team (ICT) creates a CII case for the tax year identified via the taxpayer's correspondence. The creation of the CII case will open the initial IDRS control base. If multiple tax years are listed, ICT will create the CII case for the earliest year identified. Review the taxpayer's correspondence and perform Complete Case Analysis (CCA) to determine if there are any other IDT impacted tax years. A new CII case must be opened for all tax years identified by the taxpayer and all additional years discovered to be impacted by IDT. Do not update your existing CII case to reflect each year as they are worked. Refer to IRM 25.23.2-15, IDTVA IDRS Category Controls by Function, to determine the appropriate category code for additional impacted years. These controls should prevent other areas from adjusting an account without making contact. If there are multiple function controls on a case, use Exhibit 25.23.4-9, IDTVA-A Identity Theft (IDT) Work Types Listing, to determine where to route the case. Note: "IDT impacted tax years" includes dependent related identity theft, income related tax year(s), and invalid returns filed using the primary or secondary taxpayer's TIN identified through Complete Case Analysis (CCA). When a dependent related, income related, or primary/secondary taxpayer issue is identified through CCA, and the issue was not previously resolved or was worked incorrectly, the case will be created even if no tax module exists. TC 290 .00 with Reason Code 139 will only be input if a TC 150 is present. All related CII cases must be linked, including XREF TINs, dependent related IDT siblings/parents, cases previously resolved, and new cases created as a result of CCA. Caution: All cases determined to be NOIDT require a CII case to be created if the year was identified by the taxpayer (e.g., listed on Form 14039, police report, correspondence, etc.). Exception: For cases determined to be impacted by refund related IDT (i.e., invalid return filed), do not create a CII control or input a TC 290 .00 with a Reason Code 139 if the following conditions exist: - There is no TC 150 present on the account. - No tax module exists. - The module is in retention (unless reversing a tax offset will create a balance due or it is necessary to resolve the taxpayer issue to make the taxpayer whole). - Issues involving a secondary taxpayer previously worked by another function (e.g., RIVO, TPP, etc.) may require addressing an unresolved TC 594 CC 084. See IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement, for additional information. - When an impacted module is not active on IDRS CC: TXMOD and is not yet in retention. Do not input IDRS CC: MFREQ. Note: Use of the IAT REQ54 tool to input the TC 290 .00 with RC 139 will prevent unnecessary modules being made active with IDRS CC MFREQ. Reminder: Whenever possible, multiple cases for the same taxpayer will be processed by the same employee. These cases may be located in unassigned inventory or as a case assigned to another employee. When unassigned, take control of the case(s). When assigned to another employee, coordination of these same taxpayer, multi-year cases is necessary to ensure consistent processing. Attach the email to the CII case and/or leave a CII case note documenting the contact and coordination. Refer to paragraph (7) if you are the employee taking ownership of the case. When opening a CII case control for additional impacted years and covered relationships, the Category Code IDT1 or IDT4 will be used when the original case is taxpayer identified and IDT3 when IRS identified. The "IRS Received Date" field will be the earliest IRS received date. Refer to the list below for more specific guidance: IRS identified case: The IRS Received Date field will be the date of identification. This date should not be changed unless an earlier received date is found through research. IDT3, IDS3, IDT6, and IDS6 cases that are created from the generation of a transcript will retain the IRS received date used at case creation. Do not update the IRS received date on CII to the date of a TC 976. Reminder: To consider timeliness of filing and refund availability when inputting an adjustment, the IRS received date of the valid TC 976 should be reflected in the appropriate field on CC REQ54/ADJ54. Taxpayer identified case: The IRS Received Date field will be the date of the claim. This date should not be changed unless through research an earlier received date is found. Reminder: A case should rarely be opened from archive and should not be if the case cannot be closed the same day. If not closing the same day, create a new CII case. Use MISC as the category code, and the date of identification as the IRS received date. Link the new case to the archived case. Verify the appropriate IRS received date for any required adjustments. Allowing the IRS received date from the newly created case to be used may negatively impact the taxpayer. Caution: The IRS received date of IDT3, IDS3, IDT6, and IDS6 CII cases may not be the appropriate date for necessary adjustments and/or determinations of credit availability for refund or offset. Thorough research must be conducted to ensure the correct date is used for these actions. The control base will be in case status "A" while the IDT determination is in process. Tax related identity theft is controlled on IDRS CC TXMOD. Dependent related identity theft is controlled on IDRS CC TXMOD. Income related identity theft is controlled on IDRS CC TXMOD. Non-tax-related identity theft is controlled on IDRS CC ENMOD. If all case actions have been completed and you are monitoring the account to ensure "ALL" account actions have posted, close the CII case. Establish a monitor base on IDRS. See IRM 25.23.4.3.1.1, Monitoring Case Controls, for more information. If an IDRS control base is created to IDTVA in error, update the Activity Code to "OPNDNERR" and the Category Code to MISC prior to closing the case. For correspondence uploaded using the Document Upload Tool (DUT) and Digital and Mobile Adaptive Forms (DMAF), the IRS received date on CII is the taxpayer's submission date and will be treated as the signature date. The received and signature dates may not be present on the form when submitted through electronic options. The date of submission will be used when determining if a claim is timely received for purposes of credits. When multiple IDT cases for the same taxpayer and tax module include the same documentation and are being closed on the same day, close the case with the most recent received date as miscellaneous. Previous action procedures do not apply under these circumstances. Example: A CII case with received date January 23, 2021 includes a Form 14039, Identity Theft Affidavit, filed through the FTC website. A second CII case with received date February 1, 2021 for the same taxpayer and tax module is created. Comparison of the documents shows the second case includes a Form 14039 that is a duplicate of the submission made through the FTC website. The case with the earliest received date is worked following normal IDT procedures. The case with the later received date is closed as miscellaneous. When multiple IDT cases for the same taxpayer and tax module include similar documentation (i.e., Form 14039 and taxpayer correspondence describing the same incident) and are being closed on the same day, close the case with the most recent received date as miscellaneous. Previous action procedures do not apply under these circumstances. When correspondence is received from a taxpayer after previous identity theft cases were resolved, refer to the table below: When correspondence is: Case Assignment For a new tax year, Will remain with the assigned employee. For the same tax year, Will be reassigned to the employee who worked the previous case for that tax year, whenever possible. A response to NOIDT or NORPLY closing letter, Will be reassigned to the employee who worked the previous case for that tax year if new information is provided, whenever possible. Specific activity codes were created to easily determine the status of the IDT case. Use of these activity codes is encouraged for all functions. See Exhibit 25.23.4-11, IDRS Activity Codes and Definitions, for more information.

# Monitoring Case Controls

25.23.4.3.1.1 (10-01-2024) Monitoring Case Controls While working identity theft (IDT) cases, there may be instances when monitoring actions is necessary prior to moving forward with resolution. There are two types of case monitoring: Open CII case IDRS control base only (CII case has been closed) Monitoring an open CII case may be necessary when account actions must post before moving forward with additional actions required for case resolution. Examples are listed below: Note: This list is not all inclusive. Establishing a new account (TC 000) on CC ENMOD/IMFOLE (e.g., dependent's entity). Requesting additional information from the taxpayer (e.g., telephone and/or written). Suspending the case on CII to lead/manager (e.g., reassignment request, approvals, etc.). If monitoring on IDRS only, ALL actions must be completed prior to closing the case. Establish a monitor base on IDRS using Category Code "MISC" with the current date as the received date. Note: When establishing this monitored control base, use "*,*" to generate the current date and assign the case to you with Command Code (CC) ACTON. Note: The Julian date input should be calculated in calendar days as the follow up date. Refer to the table below for a list of account conditions that require monitoring after the CII case has been closed. Verifying applicable transactions related to these scenarios have posted ensures the taxpayer's issue is fully resolved. Note: This list is not all inclusive. Case Scenario Monitor Actions (1) Excess Collection File (XSF) Prepare Form 8758, Excess Collection File Addition, to transfer payments and/or credits TO the Excess Collection File (XSF) or Form 8765, IDRS Control File Credit Application, to transfer FROM the XSF. Use an IDRS control base to monitor the taxpayer's account to verify posting of payments and/or credits moved TO and/or FROM the XSF. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF), for more information. (2) Manual Refund When a manual refund is issued, and there are no other actions required to resolve the case, use an IDRS control base to monitor the account for the posting of TC 840. See below for an example. See IRM 25.23.4.10.10, Identity Theft (IDT) - Manual Refunds, for more information. (3) Moving Specific Year Account When Form 12810, Account Transfer Request Checklist, is prepared and sent to Accounting to request the transfer of a tax module from master file to non-master file (TC 370/400 procedures), use an IDRS control base to monitor the account for the posting. Reminder: If there is a valid return that must be addressed and an adjustment will be input after the TC 402 posts, the CII case will remain open. One IDRS control on the Common Number (CN) module may be used to monitor both sides of the move (From and To TINs). Below is a list of information to help with monitoring an account for TC 370/400: CN: A pending TC 971 AC 045 will be present and will post with TC 400. The module will be in a zero balance after posting. CN: The module will have a posted TC 400. IRSN: Once the TC 400 posts on the CN, a TC 370 will be input and pending on the invalid number (IRSN). IRSN: Once the TC 370 posts, all of the transactions you requested to be moved will post. CN: After the TC 370 posts on the IRSN, the CN will show a pending TC 370. CN: When the TC 370 on the CN posts, the REVERSAL transaction codes for all transactions requested to be moved will also post. See IRM 25.23.4.11.4 , Moving Specific Year Account Information, for more information. (4) Treasury Offset Program (TOP) When the Treasury Offset Program (TOP) offset being reversed is more than 6 years old, a manual reversal is required. Use an IDRS control base to monitor the account for posting of the reversal when no other actions are required to resolve the case. See below for an example. See IRM 25.23.4.10.3.2 , Identity Theft with TOP Offsets, for more information. (5) Reversal of Lost/Partially Lost Refund When a refund was incorrectly moved to the General Ledger (GL) 1545, prepare Form 3245, Posting Voucher - Refund Cancellation or Repayment, and Form 3809, Miscellaneous Adjustment Voucher, to move the credit back to the originating module. Use an IDRS control base to monitor for posting of the TC 841 or TC 700 when no other actions are required to resolve the case. See IRM 25.23.4.16, Form 3245/3809 Reversals, for more information. Example: Taxpayer Amy Jones contacted Taxpayer Advocate Service (TAS) for assistance because she has a financial hardship. As a result, TAS opens an Operation Assistance Request (OAR). The OAR lists resolving IDT and issuing a manual refund to the taxpayer as the necessary actions. The IDTVA employee assigned the OAR works the case to address all IDT issues and closes the case on CII. A monitor control base is opened to monitor for the posting of the TC 840. Example: While conducting CCA, the IDTVA employee determines the return meets the Married Filing Joint Scheme criteria. The employee takes all necessary actions to resolve the IDT issue, inputs a TOP offset reversal, and closes the case on CII. To ensure the TOP offset reversal (TC 766) posts and the account is resolved with a zero balance (no credit balance on IDRS), a monitor control is opened on IDRS using Category Code "MISC". For cases involving reversal of an IDT indicator with a secondary date for the tax year that is more than 7 years old, it is not necessary to keep the case open or monitor until the TC 972 AC 5XX posts on CC ENMOD/IMFOLE. See Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional information.

# Case Transfer within IDTVA

25.23.4.3.2 (10-01-2024) Case Transfer within IDTVA Generally, case transfers will occur when more than one IDTVA function has an open case control. To better assist the taxpayer and ensure end to end account resolution, one employee will take responsibility for the case. Refer to Exhibit 25.23.4-5, IDTVA Routing Matrix, to determine ownership of the case. Examiners will check IDRS for multiple IDTVA open controls on the same or other tax periods for one taxpayer. All issues should be worked by the same employee. This will prevent duplication of work, potential unpostables, and incorrect adjustments on a module. In most instances, the employee with the earliest IRS received date will work all tax years. However, if the identifying employee assigned a case with a later IRS received date for the same taxpayer, they may take ownership of all tax years to prevent unnecessary delays in resolution. Exception: Regardless of IRS received date, if an employee has started working the case, that employee will take ownership of all tax years. Reminder: When there are compliance issues involved (i.e., AUR, Exam, etc.), the case may need to be reassigned to an IDTVA Specialty Team. The IRS received date will not be considered in these instances. Refer to Exhibit 25.23.4-5, IDTVA Routing Matrix. If any control bases are in Status A, B, or M with IDT involvement, the assigned employee must be contacted to request reassignment or closure of the CII case before taking action on the account. Once contact is made with the assigned employee or their manager, allow 3 business days for a response before continuing with case actions. All referrals within IDTVA will be made using the Correspondence Imaging System (CII).

# Cases Requiring Routing/Reassignment to Other Functions

25.23.4.3.3 (04-28-2025) Cases Requiring Routing/Reassignment to Other Functions Review documentation submitted by the taxpayer to determine if your case should be retained or routed/referred to another function. Refer to the following IRM sections for additional guidance: Exhibit 25.23.4-4, Identity Theft (IDT) Functional Routing and Referral Chart Exhibit 25.23.4-5, IDTVA Routing Matrix Exhibit 25.23.4-9, IDTVA-A Identity Theft (IDT) Work Types Listing IRM 25.23.2.4.3, Tracking Individual Taxpayers Reporting to be Victims of Business-Related Identity Theft. Reminder: IDTVA-A and IDTVA Specialty employees – Review the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA Hub for additional information for reassignment of cases that involve issues with mixed entity, scrambled SSN, MFT 29 (Form 5329 Part III through VIII only), etc. Reminder: Before referring the case, review guidance in IRM 21.3.3.4.2.1, Use of 86C Letter - Referring Taxpayer Inquiry/Forms to Another Office, to determine if the 86C letter is required. Note: Letter 86C is not required if the case is being transferred within IDTVA, through CII, or to another function in the same location.

# IDTVA Specialty Functions - Case Referrals from Compliance Functions

25.23.4.3.4 (10-01-2023) IDTVA Specialty Functions - Case Referrals from Compliance Functions Identity theft (IDT) allegations received in campus Compliance functions will be referred to the appropriate IDTVA function when: A Form 14039, Identity Theft Affidavit, or police report is included in response to a letter/notice. IDRS CC ENMOD contains an unreversed TC 971 AC 522 with the literal UNWORK. IDRS CC ENMOD contains an unreversed TC 971 AC 522 with the literal PNDCLM and there is a CII Image of Form 14039 or police report available on AMS. There is an open control to an IDTVA employee (i.e., IDTX or IDIX) for the tax year in question. If the account contains one of the following TC 971 Action Codes for the tax year in question, the IDT issue may have been previously resolved. Action Code Literals 501 INCOME, MULTFL, INCMUL, NOFR, OTHER, DECD, REFCCA, ICMCCA or PRISNR 504 ACCT, NKI, EMPL, or ICMCCA 506 INCOME, MULTFL, INCMUL, NOFR, OTHER, DECD, or PRISNR Responses regarding functional Compliance issues should be kept and worked by the same function. If a referral is received and the account contains one of the TC 971 Action Codes in paragraph (2) above, a designated technical individual will review the referral and take the following action: If the new information/referral Then (1) Addresses an outstanding Compliance issue and will not impact IDTVA's previous determination, Reject the case back to the Compliance function that made the referral. (2) States the remaining issues are attributable to the previous identity theft claim or provides new information that may allow us to revise our previous determination, Accept the referral. If the account contains a TC 972 with the literals NOIDT or NORPLY, follow the table in (3) above. Ensure that all referrals received from another area meet the requirements to be worked by IDTVA. If requirements are not met, return any cases back to the referring function. Note: Use the "Reassign" option to return a case that was referred through the CII system. Exception: If a CII case was created for a case that met rejection criteria but was accepted in error, the case will not be rejected by the assigned employee. Use internal information and/or information already provided by the taxpayer to determine the CN owner. When a CN ownership determination cannot be made from available information, refer to IRM 25.23.2.3.6, When to Request Additional Information to Support an Allegation of Identity Theft. Any IDTVA-A or AM referrals must meet requirements listed in paragraph (4) of IRM 21.3.1.6.41, Status Of Individual Master File (IMF) Underreporter Cases. For any other referral, including referrals such as TAS, IPSU, etc., ensure the account includes a Compliance issue on at least one tax year.

# Priority Codes for IDTVA CII Cases

25.23.4.3.5 (05-05-2025) Priority Codes for IDTVA CII Cases All identity theft (IDT) cases should be treated as priority, however some cases require immediate attention. Certain case types and/or account conditions are identified by the priority code. This is not a designation of priority order. Refer to Exhibit 25.23.4-8 , Order of Priority Listing IDTVA-A and IDTVA Specialty Functions, for additional information. IDTVA-A Priority Codes are listed below. Priority Code Definition Priority Code 1 TAS case - Form 12412, Operations Assistance Request (OAR) Exception: TAS cases involving a statute imminent issue will be assigned PC 7. Priority Code 2 All IDT and IPSU inventory not meeting another PC definition Priority Code 3 Cases selected and identified by Headquarters (HQ) for trending casework - do not update to another PC unless PC 1, PC 6 or PC 7 applies. Priority Code 4 Cases selected and identified by Headquarters (HQ) for trending casework - do not update to another PC unless PC 1, PC 6 or PC 7 applies. Priority Code 6 Potential fraud-scheme scenarios Priority Code 7 Statute imminent issue requiring protection of the account The case will remain in Priority Code 7 through closure to ensure remaining actions are taken Priority Code 8 Cases identified for statute clearing IDTVA Specialty Functions Priority Codes are listed below. When sending a case to ICT for scanning to CII, certain cases will require a Priority Code to be noted on the batch sheet, as applicable. Priority Code Definition Priority 1 TAS case - Form 12412, Operations Assistance Request (OAR) IDTVA-ACSS expired Oscar inventories Exception: TAS cases involving a statute imminent issue will be assigned PC 7. Priority 2 For cases that have had a Statutory Notice of Deficiency issued and the taxpayer still has time to petition tax court Appeals/CDP IDT6/IDS6 transcript cases Referrals from OIC (Specialty Collection Offer in Compromise (SCOIC) only) Form 3870 Field referrals Form 14027-B, Global Review Referrals Priority 3 For open AUR or open Exam cases not meeting the criteria for PC 1 or PC 2 Priority Code 6 Potential fraud-scheme scenarios Priority Code 7 Statute imminent issue requiring protection of the account The case will remain in Priority Code 7 through closure to ensure remaining actions are taken Priority Code 8 Cases identified for statute clearing Blank All other inventory will be worked in IRS received date order It may be necessary to update the Priority Code of a case as it is processed. Example: The case was originally built/scanned with no Priority Code. During the time the case is waiting to be worked, TAS issues an OAR for the account. Using the 'Update Data' button in the Case Data section of your CII case, the Priority Code would need to be updated to Priority Code "1" . Example: The case was originally built/scanned with no Priority Code. During the time the case is waiting to be worked, the account comes within 180 days of the ASED expiring, the Priority Code would need to be updated to Priority Code "7" . See IRM 25.23.4.9.1, Statute Imminent Assessments for IDT Cases Refer to specific functional IRMs for additional cases that may require immediate attention.

# Taxpayer Inquiries Involving Identity Theft (IDT)

25.23.4.4 (11-06-2024) Taxpayer Inquiries Involving Identity Theft (IDT) Taxpayers indicate IDT by submitting Form 14039, Identity Theft Affidavit, a police report, or a similar statement. Note: If the taxpayer inquiry requires translation into English, refer to guidance in IRM 25.23.4.19, Requesting Translations of Certain Languages. After research is completed, the case will generally be identified as one of the following types: A mixed entity case A scrambled SSN case An IDT case that you can resolve An IDT case that should be routed or reassigned A non-IDT case (e.g., in some instances you may discover the case involves multiple returns filed by the SSN owner; a normal DUPF case) Refer to guidance in IRM 21.6.2, Adjusting TIN-Related Problems, for processing mixed entity and scrambled SSN cases. The following are examples of taxpayer inquiries involving IDT. Examples of tax-related IDT involving two or more returns include, but are not limited to, references to a Letter 673C, a notice of tax due, references to an attempt to e-file a return that was rejected due to a return already having been filed, a missing refund, or the amount of the refund is different than the amount claimed, etc., and the taxpayer claims they did not file more than one return. Examples of tax-related IDT involving only one posted return include, but are not limited to, references to impact to Social Security benefits, impact to low income housing benefits, no filing requirement or below filing requirement, and the taxpayer claims they did not file a return. Examples of tax-related IDT involving secondary TINs on returns include cases in which taxpayers' overpayments have been applied to accounts that show the taxpayers as secondary filers and the taxpayers claim they did not file as joint or secondary filers on the accounts. See IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement, and IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration. Examples of income related IDT involve instances where income earned by someone other than the CN owner is present on CC IRPTRL. These cases may be tax related or non-tax related but are always controlled on CC TXMOD on the affected tax period. Examples of non-tax-related IDT involve Forms 14039 filed in response to someone applying for a credit card using the taxpayer's name and/or Social Security Number (SSN).. Examples of dependent related IDT involve instances where misuse of a dependent's TIN is reported. These cases may be tax related or non-tax-related but are always controlled on TXMOD. If you determine a case assigned to a tax related category code (i.e., IDT1) is a true non-tax related case: Reminder: A No IDT determination will only result in a non-tax-related IDT determination if the taxpayer's statement indicates loss of personally identifying information. Update the existing CII case information to reflect Category Code IDT4 and all zeros for the MFT and Tax Period to open a control base on CC ENMOD. Note: If you determine the case was updated on CII to Category Code IDT4 but remains open on CC TXMOD, update the MFT and Tax Period to all zeros (0), per IRM 3.13.6-14, Appendix N - Document Types, Category Codes, Priority Codes, IDT - IMF, to establish the control on ENMOD. Use CC ACTON to manually close the TXMOD control as "MISC" . Follow the guidance in IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4 Overview, to resolve the case. If the inquiry, Form 14039, Identity Theft Affidavit, or correspondence is received alleging return preparer misconduct (RPM) rather than ID theft, do not reassign or route Form 14039 alleging RPM to IDTVA. Unless the exception below applies, send an appropriate C letter advising the taxpayer the information they provided indicates there is an RPM issue and not an ID theft issue. Advise the taxpayer to complete and mail Form 14157, Return Preparer Complaint, and Form 14157-A, Tax Return Preparer Fraud or Misconduct Affidavit, along with the required documentation as outlined in the instructions for Form 14157-A. Please refer to IRM 25.23.1.1.2, Terms/Definitions/Acronyms, and IRM 25.24.1.3, Identifying Potential RPM Issues For Telephone Assistors/Taxpayer Assistance Center (TAC) Assistors, for assistance in determining if there is a possible return preparer misconduct issue. Note: Enter CII Case Note, "NO ID theft - RPM issue." Input TC 972 AC 522 with Tax Administration Source Code "NOIDT" and the tax year associated with the alleged IDT incident, if appropriate. Refer to IRM 25.23.2.6.6, Reversing Unsupported Allegations of Identity Theft, for additional information. Exception: If a –A freeze is present or an unprocessed valid return is scanned to the CII case, and there is indication of RPM, do not release the –A freeze or send the return for processing, reassign to RPM per IRM 25.24.1.4.1, Routing Information - Paper. For cases where tax related identity theft is indicated by the taxpayer, change the doc type and update the Category Code to IDT1/IDS1 if it has not already been done. Exception: Change the Category Code when resolving an IDT4 case. Note: IDTVA Specialty Functions do not change Category Codes. All cases remain in the function's Category Code. Perform complete and careful research on each case, per IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and the related subsections to make a determination. If a determination cannot be made based on the information directly available, refer to guidance in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to initiate communications with the taxpayers.

# IRS Identified Identity Theft (Category Code IDT3)

25.23.4.5 (10-01-2025) IRS Identified Identity Theft (Category Code IDT3) IRS identified cases of IDT are generally associated with IRS programming, filters, transaction codes and/or research of filing history and assigned using Category Code IDT3. The following items may be indicators of current or prior identity theft: Previously posted TC 971 AC 501/506 or a TC 971 with AC 522. Evidence of a prior "CP 36I" transcript that generates an IDT1. These transcripts are generated when a taxpayer sends in a tax return with a Form 14039, a police report or a similar statement is attached and the return is edited with an FPC 8. The presence of a CP 36U transcript that generates an IDT1 or CP 36V transcript that generates an IDT3. These transcripts are generated based on prior identity theft indicators on IDRS; for example, a TC 971 AC 501 for taxpayer identified IDT or TC 971 AC 506 for IRS identified IDT. The presence of a CP 36N or CP 36P transcript that generates an IDT8. These transcripts are generated in a duplicate filing condition and when the module has a RIVO indicator of TC 971 AC 44/134/617 or TC 971 AC 199 with AMWEX60033 REFEFDS or AMWEX60033 OMMFEFDS in the miscellaneous field. The CP 36 N generates when the module has a credit balance, and the CP 36 P generates when the module has a zero or debit balance. The presence of a CP 36 or CP 36F transcript where return content and/or filing is inconsistent with the taxpayer's filing history. Unless a condition exists where additional information is needed (i.e., missing forms, etc.), IDTVA will send only a closing letter to the taxpayer when it has been determined they are a victim of identity theft. For cases where tax related identity theft is IRS identified, update the Category Code to IDT3/IDS3 if it has not already been done. Exception: Cases with RIVO involvement that systemically generated as a CP 36N or CP 36P transcript should be worked as an IDT8. Note: IDTVA Specialty Functions do not change Category Codes. All cases remain in the function's Category Code. Complete and careful research must be performed on each case per IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and the related subsections to determine the owner of the TIN. If a determination cannot be made based on the information directly available, refer to guidance in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to initiate communications with the taxpayer(s).

# Research, Actions and Complete Case Analysis - Overview

25.23.4.6 (10-01-2025) Research, Actions and Complete Case Analysis - Overview Complete and careful research must be performed on all cases. Employees outside of IDTVA are responsible for taking appropriate actions prior to reassigning a case to IDTVA or proceeding with scrambled SSN procedures. Upon recognition of a case as a potential IDT case, also perform the following actions: Determine if a TC 971 AC 522 is required and, if appropriate, whether the TC 971 AC 522 reflecting an appropriate Tax Administration Source Code has been input on CC ENMOD. See IRM 25.23.2.4.4, Initial Allegation or Suspicion of Tax-Related Identity Theft - IMF Identity Theft Indicators, for additional information. Note: A CP 01S may have been issued to acknowledge the receipt of Form 14039, Form 14039 (SP), a police report, or a similar statement related to identity theft. An acknowledgement letter would not have been issued for IRS identified IDT cases. See IRM 25.23.2.3, Identity Theft Claims - General Guidelines, and IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. Perform a complete statute search and leave a case note that indicates the case is related to an IDT issue. Statute expiration must be considered to prevent barred assessments. Determine the correct Category Code, Doc Type, etc. Update CII and the Statute Clearance check box, when appropriate, when reassigning to a CII user. Leave a note on CII if one is not generated. Ensure all relevant documents have been scanned to the case. Cases for tax years at or approaching 10 years (i.e., current year is 2023 and case is for tax year 2013), it is suggested IRPTR screen prints are attached to the case. Due to the nature of the work, access to the income history may be lost before an employee is able to work the case. Review the case for potential balance due issues that must be addressed. Accounts with balance due issues must be protected, which includes prevention of balance due notices, tax offsets, and/or enforcement actions. Refer to the table below to determine the appropriate action(s): If And Then (1) The year(s) on a claim reflect a balance due in notice status (SC or MF): The corrective adjustment will full pay the balance, Input TC 470 CC 90. (2) The year(s) on a claim reflect a balance due in notice status (SC or MF): The identity theft claim is pending and/or there will still be a balance owed after the case is resolved, Input TC 470 with no CC. (3) The year(s) on a claim reflect a balance due in collection status 03, 22, 24, 26, or 58 (SC or MF): Refer to IRM 25.23.4.12.1, Collection Activity Form 14394, for additional information about ensuring the taxpayer is not harmed from a levy. (4) There is a TC 582 (Lien Indicator) or TC 360 Refer to IRM 25.23.4.12.2, Collection Activity - Form 13794 Additional Actions Required - Lien, for additional actions that may be required to protect the taxpayer. (5) The valid taxpayer's return is not the TC 150 and requests a credit elect: The year the credit elect is to be applied to reflects a balance due that will be full paid once the credit elect is applied, Input TC 470 CC 94 on the module with the balance due to prevent notices, offsets, and collection activity. (6) The valid taxpayer's return is not the TC 150 and requests a credit elect: The year the credit elect is to be applied to reflects a balance due that will not be fully resolved once the credit elect is applied, Input TC 470 CC 94 on the module with the balance due to prevent notices, offsets, and collection activity. Once the case has been resolved, input TC 472 CC 94 to resume normal balance due activity. If reassigning the case, after performing the actions above, reassign the case to the IDT holding number. International cases should be reassigned to the International holding number. Both IDRS numbers can be found on the Accounts Management Site Specialization Temporary Holding Numbers located on SERP. See paragraph (13) of IRM 21.5.1.5.2, Cases Currently Assigned in CII, for additional information. Note: A case reassigned to the Centralized Distribution Site (CDS) in error may be returned to the originating site. Reassigning cases in error can result in an adverse impact to the taxpayer and delay the processing of their case. Exception: IDTVA employees will continue to resolve the case or route/reassign the case, if applicable. Before proceeding, if the case should be assigned/routed to another area (e.g., AUR, Exam, etc.) or employee, refer to IRM 25.23.4.3.2, Case Transfer Within IDTVA, and IRM 25.23.4.3.3, Cases Requiring Routing/Reassignment To Other Functions, for additional guidance. If the case does not require reassignment/routing, proceed to the next IRM sections that apply to your case. Note: IDTVA-A employees - do not reassign the following transcripts to IDTVA Specialty Functions unless there is an open and/or active identity theft (IDT) claim or a previous assessment that may require an IDT determination: TRNS 36, 36D, 36I, 36N, 36P, 36S, 36U and 36V. Example: CII case with TRNS 36 is assigned on tax year 2022. Research of the taxpayer's account shows a previous TC 922 with Process Code (PC) 87 (taxpayer agreed) and an assessment made for tax year 2018. Tax year 2018 does not have an IDT issue. Do not reassign the CII case for tax year 2022 to IDTVA Specialty. Example: CII case with TRNS 36 is assigned on tax year 2023. Research of the taxpayer's account shows a previous TC 300 with an Exam assessment for tax year 2020. An IDT claim received for tax year 2020 resulted in a determination of IDT, and all required actions were completed correctly. There is no remaining issue to address. Do not reassign the CII case for tax year 2023 to IDTVA Specialty. Policy Statement P-21-3 guidelines require timely and quality responses to taxpayer correspondence. The "IDT1/IDS1," "IDIX" , or "TPRQ" cases described in this subsection are, according to Policy Statement P-21-3, are considered correspondence. Generally, the response provided to the taxpayer who has submitted this type of correspondence is the closing Letter 4674C, Letter 5064C, if closed within 30 days, or CP 01 notice informing the taxpayer that we have made an identity theft determination. A response, as described here, is considered timely if issued within 582 days of the received date of the "notification" "IDT1/IDS1" , or "TPRQ" document. If a closing response cannot be issued by the 582nd day, an interim letter must be sent informing the taxpayer that we require additional time to complete the processing of their case. The time frame given in this interim letter may not exceed 60 days. Note: The issuance of a closing letter may or may not coincide with the complete resolution of the case. The closing letter is sent when we can share with the taxpayer the results of our processing of the case, e.g., we have made an ownership determination. Do not wait until all resolving actions, e.g., TOP offset reversal transfer procedures, have been completed before sending a closing letter. If additional interim letters are needed, the time frame given in the letter must not exceed 60 days. Every effort, however, must be made to provide a closing response within the initial 582-day time frame. Caution: A reasonable effort must be made to respond or send an interim letter within the time frame previously given. Such an effort is considered reasonable if it does not hinder the primary objective of resolving the IDT condition and issuing a quality closing response. Caution: Be sure you are sending any necessary letters to the correct address. The Correspondex letter system will default to the Address of Record which may or may not be the correct address for your correspondence. Override the Address of Record when appropriate. Cases determined not to be identity theft may require additional actions to resolve outstanding issues (i.e., amended return, duplicate return, etc.). Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, to appropriately close the identity theft issue and open a new case to fully resolve the account.

# Required Research

25.23.4.6.1 (10-01-2025) Required Research Make every effort to locate the correct TIN for each taxpayer before contacting the taxpayer(s) for additional information. Research the TIN (valid and invalid) to determine if there was an identity theft (IDT), mixed entity (MXEN), or scrambled SSN case (SCRM/SSA2) in prior and/or subsequent years. Complete research is essential to determining the necessary corrective actions. Attempt to locate any possible cross-reference TIN. You may identify a cross-reference TIN assigned to a taxpayer who filed a return under the common number (CN) that was determined to be due to identity theft. Internal Revenue Service Numbers (IRSNs) are temporary numbers issued by the IRS and are always on the invalid segment of Master File. The invalid segment is indicated by an asterisk (*) following the last digit of the TIN. Additionally, the tax return(s) in question must be reviewed to determine if the case is a mixed period instead of a TIN-related issue. For purposes of identifying the correct account issue, refer to the following definitions: Identity Theft (IDT) - the intentional misuse of a taxpayer's personal information/TIN to commit, or attempt to commit, tax-related fraud. Mixed Entity (MXEN) - the unintentional misuse of a taxpayer's TIN due to an inadvertent taxpayer error, tax return preparer error, Marketplace error, or IRS processing error. Note: A separate TIN can be identified for the taxpayer who has filed under the CN in error. Mixed Period - a return for the valid taxpayer is processed to an incorrect year, usually due to editing the tax year on the tax return or an incorrect version of the tax return being used by the taxpayer (i.e., TY 2020 income reported on a TY 2021 form). Scrambled SSN (SCRM/SSA2) - multiple individuals using the same SSN, and the true owner cannot be determined. The Social Security Administration (SSA) has issued the same SSN to more than one individual. Search returns, schedules, and forms for a different TIN, if applicable. Research spouse and dependent information, whenever available. Research the valid and invalid sides of any TINs identified for the case (i.e., primary, secondary, different TIN located on forms, etc.). A return posted to the invalid side of the CN is not sufficient evidence to identify an IDT issue. Further research must be conducted to verify the return was not processed to the invalid side of the TIN as a result of an error on the return or name changes that have not yet been provided to the IRS by the Social Security Administration (SSA): Generally, a return is posted to the invalid side of a TIN due to a Name Control mismatch issue. This may be seen more frequently with taxpayers who have multiple last names, taxpayers who are recently married, and typos on the return. CC INOLES: Determine the appropriate Name Control(s) for the taxpayer. CC IMFOLI: Determine if the taxpayer is filing jointly for the first time. CC TRDBV: Determine if the Name Control based on the spelling of the last name entered on the tax return processed to the invalid side of the TIN matches an appropriate Name Control shown on CC INOLES. When a Name Control mismatch has occurred as a result of taxpayer, preparer, or typographical error, and there is no indication the information included on the return is questionable (i.e., the income is verifiable, return information is consistent with filing history, etc.), refer to IRM 21.6.2.4.1, Resequencing Accounts, and its subsections. When ICT is unable to determine the correct TIN, the CII case is assigned to all zeros. Additional research is required to locate a TIN for the taxpayer. Using IDRS CC NAMES or NAMEI, input the taxpayer's name and address information to search for a TIN. To do a broad search, input the taxpayer's name and only the first 3 digits of their zip code. The results will include taxpayer information from areas surrounding the current address. Consider the following possibilities when conducting research using CC NAMES and NAMEI: The taxpayer may share their name with a parent or child. The taxpayer's current address may be different than the address reflected on their account. The taxpayer's name may be different as a result of a change in their marital status. The taxpayer's name may have included a hyphenated last name or variation in spelling of their name due to typographical errors by the taxpayer, a preparer, or the Service. A taxpayer may use Form 14039 to report someone has obtained an Employer Identification Number (EIN) in their name. When the EIN is not provided, make every effort to locate it through internal research. Once you have completed the necessary research, see the table below: If Then (1) An individual's TIN cannot be located and there is sufficient mailing information on the complaint, Issue Letter 5064C to the taxpayer requesting the taxpayer's TIN and any other required IDT documentation. See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written. (2) No response is received, Issue a Letter 4674C to advise the taxpayer no action can be taken, since we have no record of a response being received. (3) Correspondence cannot be issued, Leave a CII case note stating there is insufficient information to issue correspondence and close the case no action. (4) An EIN cannot be located, Follow IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. In your closing Letter 4674C, advise the taxpayer they may file Form 14039-B, Business Identity Theft Affidavit, if they have an identity theft issue related to an Employer Identification Number (EIN). When working ITIN cases, you must research under the relevant SSN used for income reporting. Use EUP/ITIN RTS to research ITIN application and assignment information. It is not necessary to request original Form W-7, Application for IRS Individual Taxpayer Identification Number, documents to conduct required research. Using IDRS CC NAMES or NAMEI, input the taxpayer's name and address information to search for a TIN. To do a broad search, input the taxpayer's name and only the first 3 digits of their zip code. The results will include taxpayer information from areas surrounding the current address. Consider the following possibilities when conducting research using CC NAMES and NAMEI: The taxpayer may share their name with a parent or child. The taxpayer's current address may be different than the address reflected on their account. When the taxpayer files as married filing joint, research of the spouse's TIN may lead to identification of valid TIN information for the taxpayer you are researching. The taxpayer's name may have included a hyphenated last name. When the taxpayer has a hyphenated last name, complete research under each last name separately in addition to the hyphenated name. Research the valid and invalid sides of the TIN. Returns may post to the invalid side of a TIN due to a name control mismatch. Note: An ITIN may have been assigned using only one last name. Through review of the information on Form W-7, you may be able to determine the taxpayer's valid TIN by matching address and/or spouse information to the application for an ITIN. Reminder: The Protecting Americans from Tax Hikes Act (PATH Act) was enacted December 18, 2015 and mandates ITIN renewal requirements. An expired ITIN is not a revoked ITIN. Once an ITIN is assigned, it belongs to that taxpayer unless revoked. Revoked ITINs are not recycled. An expired ITIN will be identified by "Inactive" displayed in the ITIN Status field on ITIN RTS, an ITIN Status of "I" on CC INOLES, and TC 971 AC 193 on CC ENMOD/IMFOLE. For additional information on TIN-related credits limited by the PATH Act, see IRM 3.11.6.4.4.1, Protecting Americans from Tax Hikes (PATH Act). Note: For ITIN cases, if the Form W-7, Application for IRS Individual Taxpayer Identification Number, clearly indicates which taxpayer was assigned the ITIN, make a notation of this for the CSR/TE who will be working the case, after reassignment from the Centralized Delivery Service (CDS). If you suspect the case is a scrambled SSN case, research IDRS CC ENMOD or IMFOLE for a Scrambled SSN Indicator (SCI) 01, 10, 12, 13, 20, or 23. Refer to IRM 21.6.2-1, Scrambled SSN Indicators. If the indicator is 01 or 20, the case can be reassigned as a scrambled SSN case without ordering the NUMIDENT or sending the questionnaire. If an SCI is not present, order a NUMIDENT. If the NUMIDENT supports a scrambled SSN case, refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), and its subsections to initiate contact with the taxpayers using the TIN, determine if the case is a scrambled SSN case, and the appropriate actions to take based on the determination made. For example, if it is necessary to initiate Letter 5064C, order NUMIDENT for use when asking supplementary questions per IRM 25.23.4.18.2.1, Telephone Contact Guidelines (Associated with the Letter 5064C Common Number Questionnaire). Caution: NUMIDENT is for internal use only; never send NUMIDENT to the taxpayer. Note: Only attach the NUMIDENT to the primary CII case when a determination has been made that the NUMIDENT is required and necessary to resolve the case. Reminder: IDTVA Specialty Functions do not work scrambled SSN cases. These cases will be reassigned using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases after resolution of all IDT impacted years. If you determine the case is a Mixed Period, the taxpayer is not a victim of identity theft. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. For additional information, see IRM 21.6.7.4.2.7.1, Mixed Periods. Reminder: IDTVA Specialty Functions do not work mixed period cases. These cases will be reassigned using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases after resolution of all IDT impacted years. If a valid TIN can be located for each taxpayer, the taxpayer is not a victim of identity theft. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. For additional guidance, see IRM 21.6.2.4.2, Mixed Entity Procedures. Reminder: IDTVA Specialty Functions do not work mixed entity cases. These cases will be reassigned using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases after resolution of all IDT impacted years. If a valid different TIN cannot be located for at least one of the taxpayers, continue processing as an IDT case. The following items may be indicators of current or prior IDT: Note: A TC 971 AC 129 identifies a return as questionable. This indicator alone does not meet IDT criteria. Other indications of identity theft must be present to refer a case to IDTVA. Previously posted TC 971 AC 501/506 or 522. Accounts with a TC 971 AC 522 "EPSS DISABL" indicate an on-line account has been disabled by Electronic Products Service and Support (EPSS). This will prevent the TIN owner from accessing an online account. EPSS will instruct these taxpayers to file Form 14039 to secure an IP PIN to protect their compromised TINs. See IRM 25.23.2.3.10, Electronic Products Service and Support (EPSS) Disabled Accounts, for additional information. Note: IDTVA employees cannot reverse an existing TC 971 AC 522 placed by EPSS. Prepare and email Form 4442 using the subject line: Reverse EPSS IDT Indicator (or similar) to ITVA HQ to request issuance of the IP PIN by mail. The presence of a "CP 36I" transcript that generates an IDT1. These transcripts are generated in a duplicate filing condition and a taxpayer sends in a return with a Form 14039, a police report, or a similar statement attached indicating identity theft, and the return is edited with an FPC 8. The FPC "8" also generates a TC 971 AC 522 on CC ENMOD and a CP 01S acknowledgement. Note: When a Form 14039(SP), a police report, or a similar statement is received in Spanish, the return is coded with "SPC S" , which generates the TC 971 AC 522 and a CP 01S acknowledgement. The presence of a CP 36U transcript that generates an IDT1 or CP 36V that generates an IDT3. These transcripts are generated in a duplicate filing condition and when the module has prior IDT indicators on IDRS. The posting of a CP 36N or CP 36P transcript that generates an IDT8. These transcripts are generated in a duplicate filing condition when the module has a RIVO indicator of TC 971 AC 44/134/617 or TC 971 AC 199 with AMWEX60033 REFEFDS or AMWEX60033 OMMFEFDS in the miscellaneous field. The CP 36 N generates when any of the indicators are present and the module is in credit balance, and the CP 36 "P" generates when any of the indicators are present and the module has a zero or debit balance. The cases have previous RIVO involvement. Refer to IRM 25.23.4.6.2.2, RICS-RIVO Involvement General Information and Research, for additional information. When a return is received from a taxpayer with a previous IDT indicator, a transcript (TRNS) 36V will generate. Normally this case work is identified as Category Code IDT3 on CII; however, in certain circumstances these have been converted to Category Code DUPF to be worked following normal procedures for duplicate filing conditions. The case should not be reassigned back to IDTVA based solely on the generation of a TRNS 36V. The return should be worked where received unless the account was not processed properly. The case should only be reassigned to IDTVA if there are outstanding IDT issues or questions on the previous account adjustments. Note: If the employee is not assigned to IDTVA, the case should be retained and worked where identified. Note: Transcripts can be identified on TXMOD by the presence of TC 971 AC 805 and a MISC code of TRNS 36, 36D, 36F, 36I, 36N, 36P, 36S, 36U, or 36V. Reminder: IDTVA-A employees - do not reassign the following transcripts to IDTVA Specialty Functions unless there is an open and/or active identity theft (IDT) claim or a previous assessment that may require an IDT determination: TRNS 36, 36D, 36I, 36N, 36P, 36S, 36U and 36V. Example: A taxpayer is selected by Exam. The return selected is deemed an IDT return and nullified. IDTVA Specialty Exam determines the SSN owner has a filing requirement. A return was requested but not received. The account was backed out and the appropriate IDT indicator was placed on the account. Six months later, the SSN owner files a return. The return is received in IDTVA-A. The return will remain in IDTVA-A to be processed. For cases originally controlled with a non-IDT category code (e.g., DUPF, C36F, etc.), determine how the case should be categorized (e.g., IDT1/IDS1, or IDT3/IDS3, etc.) per Exhibit 25.23.4-9, IDTVA-A Identity Theft (IDT) Work Types Listing. Prior to reassigning a case to an IDT category code, document all research completed, results of the research, the request for reassignment, and lead or manager approval to reassign in a CII case note. To correct tax-related IDT problems, you must be familiar with the following research elements and systems: Entity module Tax module Transaction Codes Reason Codes Posting Delay Codes Hold Codes Unpostable Codes Retention Register - Request a Retention Register transcript only if the account cannot be reactivated by using Command Code IMFOL with definer "B." Command Codes, including NAMES, INOLE, DDBKD, DUPOL, MFTRA, IMFOL, RTVUE, FFINQ, REINF, TRDBV, IRPTR, ENMOD, TXMOD, TPIIP, DFAST and FINDS with various definers and systems, such as TCIS or ACCURINT. Note: Some of the Command Codes and/or systems listed are applicable to the IDTVA Specialty Functions only (e.g., ACCURINT and DFAST). NUMIDENT transcript showing specific taxpayer data provided by Social Security Administration (SSA) records (for SSN research only) Collection status - If the taxpayer's account is in ACS status, refer to guidance in IRM 25.23.4.12, Collection Activity - Form 14394/13794, to interrupt collection activity while the case is worked. The research and tools necessary for accurately processing an IDT case includes, where applicable, and is not limited to the following: Utilizing the IAT aMend tool. The IAT aMend tool is mandated for use by all employees working all IDT cases, which includes streamline and non-streamline cases. See Exhibit 21.2.2-2, ACCOUNTS MANAGEMENT MANDATED IAT TOOLS, for a list of tools required for IDTVA. Utilizing the Correspondence Imaging System (CII) and all applicable and available internal research systems to review all related cases, whether open or closed. Utilizing the Correspondence Imaging System/Accounts Management System (CII/AMS) to review all related documents and/or attachments. Also refer to IRM 25.23.4.3, Case Assignment and Inventory Management - General Guidance, for additional guidance. Utilizing the ITIN Real Time System (RTS) to research and review data related to assigned, suspended and/or rejected Form W-7, Application for IRS Individual Taxpayer Identification Number. RTS is a tool located within the Employee User Portal (EUP). Online 5081 permission and access are required. See IRM 3.21.263.9.1.2, Accessing and Logging onto ITIN Real-Time System (RTS), and IRM 3.21.263.9, General Instructions for ITIN Navigation (ITIN RTS), for additional information. Note: The Form W-7 application's Document Locator Number (DLN) is only available on RTS. Analyzing the account history for: Number of years the TIN has been used for filing returns Filing status changes Method of filing, electronic or paper Previous adjustments Filing dates of original and duplicate returns TC 971 Transaction Codes Utilizing NAMES to identify and locate all related TINs for all tax years Utilizing RTVUE to determine items of information such as: Address for the first return(s) filed Dependents Type of income Filing Status Schedules and Forms filed Utilizing MeF to perform research of electronic filing activity (example of results could be an IDT return accepted by MeF, but subsequently deleted from processing by SP; data may not be present on TRDBV) Utilizing TRDBV to determine items of information such as: Wage information details Occupation Tax Return Preparer Requested method of disbursing overpayment, electronic or by mail Utilizing INOLE to determine items of information such as: Date of birth Previous names Spouse's TIN Other related TINs Utilizing IRPTR to perform research actions and determine items of information such as: Comparative review of reported income and payor information Previous and current employers Previous addresses State Reverse File Match Initiative (SRFMI) information Note: This information may be available for taxpayers who have filed a state tax return but have not filed a federal tax return. Refer to IRM 5.1.11.2.3.1.3, State Reverse File Matching Initiative (SRFMI), for additional information. The presence of state tax return information for a state other than the state the taxpayer lives in may be an indication of identity theft. Research must be conducted to determine if the taxpayer previously lived in that state or earned income in that state requiring them to file a state tax return for a state they do not currently live in. When the SRFMI information matches income information reported to the IRS (i.e., Form W-2, etc.), this may support the taxpayer's claim. See the example below. Example: The taxpayer submits Form 14039 with a tax return for TY 2021. The Form 14039 states the taxpayer could not file electronically, and the tax return is posted as the TC 976. Research of CC IRPTR shows SRFMI information reporting wages of $62,479.00 filed in the state the taxpayer lives in. There is a W-2 from ABC Company on CC IRPTR for the same amount, and the TC 976 return includes those wages. The TC 150 return is reporting wages of $44,916 and has an address in a different state. A W-2 from XYZ Corp. for this amount is on CC IRPTR. The W-2 from XYZ Corp. includes the taxpayer's name but an address in a different state. Research of the account did not result in the identification of another valid TIN. This information supports making a determination of refund related IDT requiring non-streamline resolution and income related IDT for the income earned by the person who filed the TC 150 tax return. Signatures (except for e-filed returns when a signature is unavailable) Note: For additional signature requirements refer to IRM 21.6.7.4.9, Signature Verification. Note: A Form 14039 received from Federal Trade Commission (FTC) should be considered valid. A signature is no longer required for the IRS to accept the receipt of the Form 14039. Do not determine the validity of a social security card based on the word "VOID" on the photocopy. Placing the word "VOID" on a photocopy of a recently issued social security card simply indicates that the document is a photocopy of the original card. The receipt of a "notification" or an "incidental" Form 14039 or some similar type of information (e.g., a police report regarding IDT) requires you to change the category of the "DUPF" or MXEN case to "IDT1/IDS1" or to "IDT3/IDS3" , if the IDT was discovered by the IRS. Caution: When reviewing cases with similar or identical income, careful and thorough research must be performed to determine the correct TIN owner. With external data breaches on the rise, a valid return could easily be identified as a duplicate and/or amended return. Review the returns or IDRS for the following indications: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: This list may not be all inclusive. Consider the taxpayer's statement. The taxpayer may not provide the specific details for their identity theft issue. A generalized statement may be used to identify the appropriate research path. Refer to the table below for examples: Note: This table is not all inclusive. Statement Research Path (1) Unable to file electronically, Refund related IDT (2) My Social Security Benefits were reduced, Income related IDT (3) The IRS is taking my Social Security, Collections activity (4) Obtained services or line of credit using my information (i.e., healthcare coverage, credit card, loan, etc.), Non-tax-related IDT If you identify a TC 971 AC 515, TC 971 AC 199 with MISC field "AMWEX60033 GAT EFDS" , or the Identity Theft (IDT) claim and/or correspondence is from an individual who is incarcerated (prisoner), refer to IRM 25.23.4.6.1.1, Researching Accounts for Incarcerated Individuals (Prisoners), for additional information. If you identify a TC 971 AC 123 with MISC "PREPARER CONTACT" , or the taxpayer provides a statement indicating they were potentially involved in a data breach incident, refer to IRM 25.23.4.8.2.4, Identity Theft (IDT) with External Business/Preparer Data Breach Involvement, for additional information. If you identify a TC 971 AC 123 with MISC "TTAX LIST" , or the taxpayer provides a statement indicating they were advised by Intuit/TurboTax that an individual attempted to use their personal information to create a new account and/or file a tax return, refer to IRM 25.23.4.8.2.5, Identity Theft (IDT) with Tax Preparation Software Misuse, for additional information. IDTVA cases that have been excluded from the systemic process for unemployment income relief provided in The American Rescue Plan Act of 2021 can be identified by a TC 971 AC 123 with MISC "IDTVACASE" (IDTVA case is open) posted on IDRS CC IMFOLE. When an IDT case that was excluded has been closed, IDRS CC IMFOLE will reflect a TC 971 AC 123 with MISC "IDTVACLSD" (IDTVA case has been resolved). These transactions are systemically placed on the account.

# Researching Accounts for Incarcerated Individuals (Prisoners)

25.23.4.6.1.1 (04-28-2025) Researching Accounts for Incarcerated Individuals (Prisoners) Identity Theft (IDT) claims and/or correspondence from a taxpayer may be received from individuals who are incarcerated (prisoners). Prior to making an identity theft determination, conduct basic research. Cases involving an incarcerated taxpayer may show the following indicators on IDRS CC TXMOD/IMFOL: TC 971 AC 515: Taxpayer is on the prisoner file. TC 971 AC 199 with MISC field "AMWEX60033 GAT EFDS" The incarcerated taxpayer is a full year prisoner, and a return was filed claiming refundable credits they may not qualify for. A review of the account(s) may reflect Automated Questionable Credit (AQC) inventory which is identified by TC 971 AC 122 with the following MISC fields: GAT11: Pre-refund prisoner returns with verified wages and withholding, with or without Sch. C or HSH income, with refundable credits that are not allowable based on income earned while an inmate at a penal institution. 7G2: Pre-refund return for a full year prisoner claiming Refundable Child Tax Credit (RCTC) – tax year 2021 only. IDRS populates Command Code (CC) FTBOL Definer P with data received and compiled once yearly from correctional institutions in the United States. Prisoner incarceration dates and release dates for the current tax year and three (3) prior tax years are maintained. See IRM 25.25.2-6, IDRS COMMAND CODE FTBOL SCREEN, for additional information, including IDRS examples of CC FTBOLP. Caution: Prior year incarceration and release dates will not be updated in the current year prison file. However, the "NOTE" field for prior years will update based on the most current information. Note: When yearly prisoner data is incomplete and cannot be perfected, incarceration and release dates are shown on IDRS as Not Applicable (N/A). This DOES NOT mean the taxpayer was released during that tax year. For these instances, use the latest incarceration and release dates to determine whether the taxpayer is a full year prisoner. Additional research for accounts involving an incarcerated taxpayer (prisoner) may include, but is not limited to, the following systems: Research Description (1) IDRS Research the account for evidence of current or previous taxpayer incarceration. CC TXMOD/IMFOL indicators described in paragraphs (2) and (3) above. CC FTBOL Definer P is available for reviewing the prisoner file. Refer to SERP IDRS Job Aid for CC FTBOLP and/or IRM 25.25.2-6, IDRS COMMAND CODE FTBOL SCREEN, for additional information. CC IRPTR: Form W-2 or other income document indicating wages earned in prison or the address indicates a prison or other correctional facility. Address on Form 1098-T identifies a prisoner or a prison or other correctional facility. CC DFAST is used as a research tool for displaying a list of compliance issues found on returns: Prisoner Entry/Release dates, state incarcerated and prisoner indicator for Primary TIN (these fields are not displayed for non-prisoners. (2) AMS Conduct a cursory review for any evidence of incarceration: Note: Prisoner indicators may not be present on AMS. History items documenting previous telephone inquiries specifying the taxpayer is/was incarcerated. History items documenting resolved/unresolved cases which may include details regarding the taxpayer's incarceration. Correspondence Imaging Inventory (CII) images which may include documents providing details of the taxpayer's incarceration. (3) Prisoner Database(s) Confirmation of incarceration, current facility, and updated mailing addresses may be found by researching government websites, such as the official Department of Corrections website for the state of the address provided by the taxpayer (i.e., Public Record Center, Public Record Center - Inmate Search). When available, use of the inmate Identification Number to conduct this research is recommended. (4) Documents Do not assume the individual filing the identity theft claim is the true owner of the Common Number (CN). Consider: All information received, Account research conducted, Marking on the envelope that indicates prisoner mail (i.e., Inmate Identification Number, etc.), and Additional information available. Note: An invalid return could include information that is consistent with the taxpayer's filing history. Refer to IRM 25.23.4.6, Research, Actions and Complete Case Analysis – Overview, for additional items to review to prevent the mishandling of an IDT case. Refer to the table below for common case scenarios and the appropriate research path: Case Scenario Research Path (1) The incarcerated taxpayer states they did not file the tax return in question, AND The tax return is Married Filing Joint (MFJ), See IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement, and its applicable subsections. (2) The incarcerated taxpayer states they did not file the tax return in question, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, AND The tax return was filed using the Non-Filers Tool. See IRM 25.23.4.8.5, Identity Theft with Non-Filer Returns. (3) The incarcerated taxpayer states someone claimed them as a dependent. See IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) – General, and its subsections. (4) All cases not meeting a case scenario above, Continue to IRM 25.23.4.8.6.1, Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Streamline Determination.

# IDTVA - Additional Research and Required Actions

25.23.4.6.2 (10-01-2025) IDTVA - Additional Research and Required Actions Identity theft cases will be either taxpayer identified or IRS identified. All taxpayer identified claims will be categorized as an IDT1 and all IRS identified cases as an IDT3 or a duplicate filing condition CP 36N or CP 36P transcript IDT8 case. Note: IDTVA Specialty Functions cases are identified or categorized by "IDIX" where X = a digit from 1 to 9 depending on the function. See Exhibit 25.23.2-15, IDTVA IDRS Category Controls by Function, for additional details. For the majority of cases, you will be able to work them without obtaining additional information from the taxpayer. If additional information is needed to resolve the case, refer to guidance in IRM 25.23.2.3, Identity Theft Claims - General Guidelines, and IRM 25.23.2.3.6, When to Request Additional Information to Support an Allegation of Identity Theft. Reminder: If you can work the case utilizing internal resources, do not request unnecessary information from the taxpayer. If the account has RIVO involvement and a duplicate filing condition exists, a CP 36N or CP 36P transcript IDT8 case is generated. RIVO involvement is not a pre-determination of identity theft. All normal identity theft research per IRM 25.23.4.6.1, Required Research, must be performed. Refer to IRM 25.23.4.6.2.2, RICS-RIVO Involvement General Information and Research, for additional information. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number Ownership and Case Processing Determinations, prior to taking any action on the account. Once a determination of CN ownership has been made, document the determination in a CII case note and follow the appropriate case resolution process to correct all affected modules. When a taxpayer is a victim of income related IDT and refund related IDT (invalid return present) for the same tax year, follow applicable procedures to resolve the invalid return and address any income not belonging to the valid taxpayer. The closing IDT indicator input will be based on the invalid return determination. The table below provides IRM references for various account circumstances that may need to be addressed. Account Circumstances IRM References and Resources (1) Address Change IRM 25.23.4.6.3, IDTVA Research, Verification, and Requests, Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, IRM 25.23.2.3.7, When to Update the Victim's Address, and IRM 3.13.5.42, Determining National change of Address (NCOA) Address Changes. (2) Adoption Credit Form 8839, Qualified Adoption Expenses, and IRM 21.6.3.4.1.25, Form 8839, Qualified Adoption Expenses. (3) Affordable Care Act For unprocessed returns or amended returns with Form 8962, Premium Tax Credit, or Form 8965, Health Coverage Exemptions, submitted by the valid SSN owner, follow procedures in IRM 21.6.3.4.2.12, Premium Tax Credit. When nullifying TC 150 returns for tax year 2014, or later years, the Shared Responsibility Payment (SRP) may be posted to the MFT 35. A separate adjustment on the MFT 35 account will be required to reverse the SRP. Use of the IAT Credit Transfer tool is required when reversing any credit applied from the MFT 30 account. This is identified by a TC 796 on the MFT 35 account and TC 896 on the MFT 30 account. Follow instructions in IRM 21.6.4.4.20.3.1, Shared Responsibility Payment Adjustments. (4) American Rescue Plan Act (ARPA) IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General (5) Combat Zone - C Freeze IRM 21.6.2.4.2.3, Valid TIN Located - Taxpayer B - Posted First IDTVA Specialty Functions, also see IRM 5.19.10.6.2, Combat Zone Qualified Individuals and Areas, and IRM 5.19.10.6.3, Combat Zone Freeze Code. (6) Decedent Returns IRM 21.6.6.2.21.1, Updating the Entity on Decedent Accounts. (7) Earned Income Tax Credit Recertification Indicator (EITC) - Reversals IRM 4.19.14.7(7), Recertification. (8) Economic Impact Payment (EIP) IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General. (9) Erroneous Refunds Reminder: An erroneous refund is defined as "the receipt of any money from the Service to which the recipient is not entitled." This definition includes all erroneous refunds regardless of taxpayer intent or whether the error that caused the erroneous refund was made by the IRS, the taxpayer, or a third party. IRM 21.4.5.5, Erroneous Refunds Categories and Procedures. (10) Excess Collections - Moving credits to or from the Excess Collection File (XSF) IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Note: If the debit/credit is not posted or pending after 8 weeks, follow local procedures to contact IDTVA P&A to follow up with the appropriate site's P&A. (11) First-time Homebuyer Credit (FTHBC) IRM 21.6.3.4.2.10, First-Time Homebuyer Credit. (12) Form 3949-A turned Form 14039 in error IRM 3.28.2.4, Initial Screening Criteria, for routing instructions. (13) Fraudulent and/or Compromised POA IRM 21.3.7.5.5.3, How to Report a Compromised or Potentially Compromised CAF Number. (14) General POA IRM 21.3.7.8.4, General Durable POA Authorizations. (15) IDT Case Requiring Corrections IRM 25.23.4.14, Identity Theft (IDT) Cases Processed Incorrectly. (16) International Taxpayers International taxpayers are those with an address that is not in the 50 states, District of Columbia, or an APO/DPO/FPO address. APO, DPO, and FPO addresses are considered domestic addresses (i.e., Form 14039 with a valid address in Puerto Rico, Form 1040-PR, etc.). See Exhibit 25.23.4-4, Identity Theft (IDT) Functional Routing and Referral Chart, for additional information. (17) Letter Procedures Job Aids Tools and Job Aids section of the IDTVA HUB. (18) Manual Refunds IRM 21.4.4.5, Preparation of Manual Refund Forms. (19) Math Error Procedures IRM 25.23.4.10.11, Identity Theft (IDT) - Setting the Math Error. (20) Moving Refunds IRM 21.5.2.4.23.10, Moving Refunds. (21) Prisoner Cases (Incarcerated Taxpayers) Confirmation of incarceration, current facility, and updated mailing addresses may be found by researching government websites, such as the official Department of Corrections website for the state of the address provided by the taxpayer. (i.e., Public Record Center) (22) Restricted Interest Accounts requiring manual restricted interest computations will be referred to the IDTVA restricted interest specialist. See "IDTVA Restricted Interest Desk Guide" in the IDTVA HUB Note: Cases that may require restricted interest calculations include disaster claims, carryback/carry forward and combat zone claims. (23) Statute Considerations IRM 25.23.4.6.2.1, Statute Research. (24) TOP Offsets IRM 25.23.4.10.3.2, Identity Theft with TOP Offsets. (25) Unfiled Returns IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions. (26) Unpostables IRM 21.5.5.4.2, Resolving Unpostables. The UPTIN Histories Tool on IAT can be used to research and resolve unpostables. The tool is designed to assist users with input of histories on CC UPTIN. Unpostables on OARs must be corrected within 3 days of identification. Note: The list above may not include all actions required to resolve your case. Research and analyze each case to ensure complete and accurate resolution. If a valid TIN is not located and the IDT return cannot be nullified, you may need to create an IRSN for the IDT (invalid) return(s). Refer to IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, for additional information. For all non-streamline case processing, the TIN-Related Problem Research Sheet is required. This research sheet is found on SERP under the IRM Supplements tab. The research sheet can also be completed using the aMend tool. Per Exhibit 21.2.2-2, ACCOUNTS MANAGEMENT MANDATED IAT TOOLS, use of the aMend tool is mandatory when working IDT cases. Include a CII case note when a determination is made. Record all significant research actions and information. The information retained/recorded must be sufficient to support the actions taken on the case. Note: In situations where the aMend tool will not perform the necessary account adjustment, another IAT adjustment tool must be used. For streamline cases, include a CII case note when a determination is made (e.g., CP 05A, DECD Taxpayer (TP), invalid/valid per IRP data etc.). Note: If you are preparing the case for reassignment to another CSR/TE or to the IDT holding number, you may notate your research in the "Notes" section of the CII case in lieu of using the research sheets. The IDT holding number can be found on the Accounts Management Site Specialization Temporary Holding Numbers located on SERP. Note: If you are preparing the case to reroute to another function using CII, any linked cases, IDRS screen captures, and attached files do not print. If any of these items must be attached to the case, print the items using your local printer and manually associate the printed documents. See IRM 21.5.1.5.2(7), Cases Currently Assigned in CII, for additional information. If the IDT claim cannot be supported based on the information received and your research, refer to IRM 25.23.2.6.6.3, Identity Theft Claims Submitted by Individuals Who Do Not Appear to be the Victim, for additional guidance.

# Statute Research

25.23.4.6.2.1 (04-28-2025) Statute Research A statute of limitation is a time period established by law to review, analyze, and resolve taxpayer and/or IRS tax related issues. The Internal Revenue Code (IRC) requires that the Internal Revenue Service (IRS) will assess, refund, credit, and collect taxes within specific time limits. These limits are known as the Statutes of Limitations. When they expire, the IRS can no longer assess additional tax, allow a claim for refund by the taxpayer, or take collection action. The determination of statute expiration differs for assessment, refund, and collection. Assessment Statute Expiration Date (ASED): The general rule is that an assessment of tax must be made within three years from the date a return is received. This includes increases to tax requested by the taxpayer and any additional tax increase identified by the IRS (i.e., AUR or Exam assessment). Additionally, the ASED must be considered when decreasing a posted credit. IDRS Command Codes (CCs) IMFOLT/IMFOBT and TXMODA will show ASED fields for IMF accounts. A case is considered imminent when a tax increase is required and it is within 180 days of the valid TC 150, TC 976/TC 977 or unprocessed return. To prevent a barred statute assessment follow procedures in IRM 25.23.2.5, Statute Protection. Note: Invalid returns meeting streamline processing criteria do not require statute protection; however, other returns on the account may. Each return must be considered separately. When following non-streamline procedures or reprocessing a valid return, the ASED must be considered when determining the appropriate actions. Refer to IRM 25.23.4.9, Statute Processing Considerations, and its subsections. Refund Statute Expiration Date (RSED): The RSED is generally three years from the Return Due Date (RDD) for prepaid credits if a return was filed. Timely requesting an extension to file will extend the RSED. Payments are refundable after the RSED has expired when the claim was received within two years from the payment posted date. CCs IMFOLT/IMFOBT and TXMODA will show RSED fields for IMF accounts. Care must be taken to ensure the RSED has not expired before refunding an overpayment. Generally, the amount refunded is limited to the tax paid during the three years immediately preceding the filing of a return, plus any extension of time to file. If payments are being considered, a two year look back from the claim (i.e., Form 14039) received date must be conducted to identify which payments are available for refund or offset. See IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim, and its subsections for additional information. See IRM 25.6.1.10.3.5, Claims for Credit or Refund – Taxpayers in Special Situations, and its subsections for procedures regarding claims for credit or refund from taxpayers that meet special situations such as financial disability, federally declared disaster area or significant fire, identity theft, etc. Note: The period of RSED limitations is not suspended due to identity theft. Reminder: Do not allow any overpayment of prepaid credits or subsequent payments to refund or offset if the RSED has expired. Review IRM 25.6.1, Statute of Limitations Processes and Procedures, for more information. Note: Refunds allowed outside of the statute of limitations are erroneous and require correction. For additional guidance on erroneous refunds refer to paragraph (9) below. Collection Statute Expiration Date (CSED): The CSED is a time period established by law to collect taxes. The CSED is normally ten years from the date of assessment. CCs SUMRY, IMFOLT/IMFOBT, and TXMODA will show CSED fields for IMF accounts. Each tax assessment has its own CSED. The CSED dates will always reflect in chronological order. However, you must always look for additional Transaction Codes (TCs) or other conditions that may further extend the CSED. Listed below are examples of liability assessments and their transaction codes (TCs) that may further extend the CSED: Transaction Code (TC) 150, Tax Assessed TC 160, Manually Computed Delinquency Penalty TC 166, Delinquency Penalty TC 170, Computer Generated or Manually Assessed Estimated Tax Penalty TC 176, Estimated Tax Penalty TC 180, Deposit Penalty Review IRM 25.6.1.12, Collection Statute Expiration Date (CSED), for a more detailed list of assessment Transaction Codes. For a listing of conditions that may postpone or suspend the collection period see IRM 25.6.1.12.2.1, Conditions Postponing Collection or Suspending the 10 Year Collection Period. You must consider all items in the statutes case processing charts below that apply to your case scenario. Utilizing the tables below will assist you in addressing all issues to make the taxpayer whole. Reminder: Each return on the module (valid and invalid) must be considered separately. Note: Stolen identity cases are exempt from normal statute processing. To that end, IDT cases do not truly have a CSED when it was established as the result of processing an invalid return on the module. For ASED statute related issues and instructions, see the table below: If And Then (1) Tax increase for a TC 976/977 return is imminent, More than 90 days remain before the valid return ASED expires, A normal adjustment may be input on IDRS. (2) Tax increase for a TC 976/977 return is imminent, The valid return ASED on the CN account will expire in 90 days or less, Complete Form 2859, Request for Quick or Prompt Assessment. Refer to IRM 25.23.4.9.1 IRM 25.23.4.9.2, Statute Imminent Assessments for IDT Cases, for additional information. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. (3) The invalid return will be moved to an IRSN, The ASED on the IRSN return will expire in 180 days or less, Complete Form 2859, Request for Quick or Prompt Assessment. Refer to IRM 25.23.4.9.1, Statute Imminent Assessments for IDT Cases, for additional information. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. (4) The invalid return will be moved to an IRSN, The ASED has expired, Refer to IRM 25.23.4.11, Non-Streamline - Determining When Specific Year Account Information Must Be Moved, and its subsections for additional information (5) The ASED has expired, The assessment was not timely OR tax was erroneously abated, The assessment is barred. See IRM 25.23.4.9.2, Addressing Barred Assessments on Identity Theft (IDT) Cases, for account correction and reporting procedures. (6) Recovery of an erroneous refund before the ASED expires, Note: You may identify an erroneous refund created by someone else. The refund was issued to the valid taxpayer, See IRM 25.6.1.10.2.3, Remedies for Recovering an Erroneous Refund. (7) An erroneous abatement occurred after the ASED expired, The credit is still on the account for the valid taxpayer, Send the credit to the Excess Collection File (XSF) per IRM 25.6.1.10.2.3.1, Recovery of Assessable Erroneous Refunds. (8) Recovery of an erroneous refund, The refund was issued to the invalid taxpayer, Lost refunds on an IDT return should be moved to general ledger (GL) 1545 account. For additional guidance refer to IRM 25.25.4.7, Reversing Identity Theft Lost Refunds. For RSED statute related issues and instructions, see the table below: If And Then (1) Identity theft case includes tax offsets, Follow procedures in IRM 25.23.4.10.3.1, Identity Theft with Tax Offsets. (2) Identity theft case includes TOP offsets, Follow procedures in IRM 25.23.4.10.3.2, Identity Theft with TOP Offsets. (3) When following Category D erroneous refund procedures, The Erroneous Refund Statute Expiration Date (ERSED) is considered, Refer to IRM 21.4.5.15.1.1, Statute of Limitations Category D Erroneous Refunds IRC 6532 (b) ERSED. For CSED statute related issues and instructions, see the table below: If And Then (1) Offset reversal needed to address the taxpayer's liability, Offset resulted from an overpayment of the invalid return, Follow procedures IRM 25.23.4.10.3, Identity Theft with Offsets. (2) Balance due module is a Married Filing Joint (MFJ) account, Offset was applied from a module that does not reflect both spouses' names, Example: One Return IDT - MFJ Scheme determination for TY 2019. The secondary taxpayer filed Form 14039, because their refund from their TY 2022 return was offset to the MFJ balance due. Follow procedures IRM 25.23.4.10.3, Identity Theft with Offsets. (3) TAS hardship case(s), Requests for returning an offset to the originating module, Follow procedures IRM 25.23.4.10.3.1, Identity Theft with Tax Offsets.

# RICS-RIVO Involvement General Information and Research

25.23.4.6.2.2 (10-01-2025) RICS-RIVO Involvement General Information and Research Return Integrity Compliance Services (RICS) is a Business Unit within Taxpayer Services (TS) and is responsible for protecting public interest by improving the IRS's ability to detect and prevent improper refunds and helping taxpayers understand the refundable tax credits for which they are eligible. Return Integrity Verification Operations (RIVO) is a function within RICS that identifies and dispositions returns which display evidence of patterns of fraud including identity theft (IDT) as well as identify potentially false returns and verify as-reported wage and withholding accuracy. Selected returns contain characteristics considered questionable for potential identity theft or first-person fraud. The presence of RIVO indicators should not be interpreted as a pre-determination of identity theft. In most instances, your case should be worked following normal identity theft research and identity theft determination requirements. Research must be performed to make an identity theft determination. The RIVO indicators on the account may assist you with making the determination. Cases with RIVO involvement will be worked in the category in which it was created. For example: An IDT8 is only a duplicate filing condition where a CP 36N or CP 36P is generated, A Form 14039 will be assigned as an IDT1 whether there are RIVO indicators on the account or not. The extent of your research depends upon the type of case you have, whether it is a duplicate filing condition or a taxpayer initiated claim (i.e., Form 14039 claiming identity theft, etc.). Every specific scenario cannot be included. This section is meant to provide an overview of RIVO codes and their definitions to assist you in determining what is occurring on the account. Your research should take into account the presence of RIVO indicators and may take you in a particular direction. Taxpayer Protection Program (TPP) Involvement: Through the TPP process, returns are screened for characteristics of potential identity theft. A questionable return selected for potential identity theft requires the taxpayer to authenticate their identity and verify the return, if they filed the tax return in question. The presence of TPP indicators on an account does not always indicate identity theft and is based on taxpayer response or non-response. Depending upon the selection, the taxpayer will be provided the option to call the TPP telephone line, verify online, or require them to authenticate at a TAC office. If the taxpayer does not respond to the TPP letter, the return will be purged to MFT 32 by RICS through a batch process. It is important to review the return posted on MFT 32 to determine whether it may be a valid return. Once the TPP issue is resolved, returns continue through fraud filters. Refer to the table below for a listing of transactions that can be seen on an account with TPP involvement: Account Indicator(s): And Definition(s) (1) With or without a posted TC 150, AND Unreversed TC 971 AC 124 with the DLN of the questionable return listed in the MISC field, The selected return is prevented from posting and will show as unpostable UP 126 RC 0. A TPP letter is issued requiring the taxpayer to authenticate their identity. (2) TC 150 is posted, AND Unreversed TC 971 AC 129 with the DLN of the questionable return listed in the MISC field The return was identified after the initial processing. As a result, the return(s) could not unpost with UP 126 RC 0. In this case, normal TPP authentication and verification of the return(s) is still required. The module may contain an unresolved -R freeze or P- freeze, resulting in a hold on the overpayment. (3) TC 150 and/or TC 976 is posted, AND TC 972 AC 124 with a DLN match in the MISC field, TC 971 AC 123 with MISC field "TPP RP" is NOT present, In response to a TPP letter, the taxpayer authenticated their identity and verified the return filed is valid. Note: History on AMS will reflect the taxpayer resolved the TPP issue by visiting a TAC office or by calling the TPP phone line. If the taxpayer authenticated their identity online, AMS will not reflect any history information. (4) TC 150 and/or TC 976 is posted, AND TC 972 AC 124 with a DLN match in the MISC field, TC 971 AC 123 with MISC field "TPP RP" is present, RIVO Resolution - Batch Process: Information from internal or external sources resulted in the return(s) being deemed valid. RIVO generally will resolve these case types within the first two (2) weeks of the return going unpostable. (5) TC 972 AC 129 is present, AND The MISC field is populated with Last 6 DLN underscore, MISC field also contains in whole or in part the verbiage "NONIDT" , The taxpayer has authenticated their identity and verified the return filed is valid in response to the TPP letter. (6) MFT 32 is present, AND TC 972 AC 124 and TC 971 AC 111 present with matching DLN in the MISC field, TC 971 AC 111 DOES NOT contain "88888" in the DLN, The taxpayer responded to the TPP letter and claimed identity theft. Note: History on AMS will reflect the taxpayer resolved the TPP issue by visiting a TAC office or by calling the TPP phone line. If the taxpayer authenticated their identity online, AMS will not reflect any history information. (7) MFT 32 is present, AND TC 972 AC 124 and TC 971 AC 111 present with matching DLN in the MISC field, Note: Due to timing issues, reversal of the TC 972 AC 124 may not be viewable. TC 971 AC 111 contains "88888" in the DLN, RIVO Resolution - Batch Process: The suspense period expired and the taxpayer did not respond to the TPP issue. As a result, the return is deemed as identity theft. (8) No MFT 32 is present, AND there is a TC 972 AC 124 with a MISC Field DLN and no TC 150 posted with a matching DLN, AND The return on CC TRDBV may show "Archived" or "Deleted" , The taxpayer provided a response to the TPP letter and claimed identity theft, OR RIVO resolved the issue through the batch process due to no response, the suspense timeframe expired, and the return is for a prior year (more than the current year or immediate prior year). (9) TC 972 AC 129 is present, AND MISC field contains the Last 6 digits with DLN IDT, AND Last 6 digits of the DLN match the posted TC 150, The TC 150 may have been backed out by RIVO. However, timing issues may create delays preventing it to appear on IDRS, The taxpayer has responded to the TPP letter and claimed identity theft. For possible fraud selections, returns are verified against third party data to determine whether or not first-person fraud has been committed. At this point the IRS may reach out to the taxpayer in order to verify income. The tablet below provides the definition of various RIVO markers that will generate a CP 36 "N" or CP 36 "P" - IDT8 duplicate filing case. Reminder: The presence of RIVO indicators should not be interpreted as a pre-determination of identity theft. Complete research must be performed. Account Indicator(s) Definition(s) (1) TC 971 AC 044 A CP 05- We're Holding Your Refund, was issued. (2) TC 971 AC 134 Income verification: The module may contain a -R Freeze. The presence of a TC 971 AC 134 doesn't automatically generate a letter or notice. Therefore, further research is required to determine if Letter 4464C or CP 05 was issued. Specific MISC fields are listed in paragraph (9) below. (3) TC 971 AC 617 RIVO initiated Third Party Contact notification. (4) TC 971 AC 199 Returns deemed questionable or false, RIVO will input a TC 971 AC 199 to place a "hard freeze" on the module. (5) 971 199 MISC "AMWEX60033 REFEFDS" A return was determined as fraud. TC 971 AC 134 may be present on these accounts with various MISC fields. Refer to the table below for definitions. Reminder: The presence of RIVO indicators should not be interpreted as a pre-determination of identity theft. However, depending upon the indicator it may assist you in making a determination of identity theft or not. TC 971 AC 134 MISC Field: Definition(s): (1) CANT VERIFY Non identity theft process: IRP data is not available and verification of income is required. The return in question will be held and rerun against IRP data until it is available or after it is determined all data is loaded for the processing year and released if verified ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ or it moves into the next treatment phase if not verified ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. (2) CANT VERIFY IDTFP Non identity theft process: The taxpayer authenticated their identity and confirmed the return filed is valid. Identity theft is not considered in this case. However, IRP data is not available and verification of income is required. (3) FULL YR PRN Placed on the module when an incarcerated individual is identified as a prisoner for eleven (11) consecutive months. (4) RRPNONIDT The account will reflect a posted TC 971 AC 052. The return was not selected by Return Review Program (RRP) for potential ID theft. (5) BOGUS EIN Placed on the module when any income document on the return is suspected as potentially fraudulent submission. (6) POTENTEF Placed on the module if the BMF account shows characteristics of a fabricated entity. (7) BKLD OFFSET Placed on the module when a RICS account review may result in an offset reversal. (8) BKLD COMINGLED Funds (refunds) are received/returned but, the dollar amount applied cannot be determined or the account was previously adjusted (TC 29X) and TC 841 posted. These funds (refunds) are applied to the general ledger account.

# IDTVA Research, Verification, and Requests

25.23.4.6.3 (10-01-2023) IDTVA Research, Verification, and Requests For instructions related to research, verification, and requests, see the table below: If And Then (1) The TC 976/977 was not processed, Refer to IRM 25.23.4.6.5.2, Unprocessed Documents. (2) The SSN owner's return posted as TC 976, An election was made for the Presidential Election Campaign Fund (PECF), Prepare a dummy Form 1040-X. Refer to procedures in IRM 21.6.7.4.12, Presidential Election Campaign Fund (PECF). (3) The SSN owner's return posted as TC 976/977 bypassed DIF scoring, Research for DIF scoring criteria per IRM 21.5.2.4.23.6, Discriminant Index Function (DIF) SCORE or CLASSIFICATION "Send Return(s) to Examination for Review". DO NOT refer Form 1040-EZ, Income Tax Return for Single and Joint Filers With No Dependents. Caution: All adjustment actions must be input prior to referring to Exam. (4) The return is a statute year, Action is required to prevent a barred assessment/statute, Refer to IRM 25.23.2.5, Statute Protection, IRM 25.6.1.13, Barred Assessments/Barred Statute Cases, and IRM 25.6.1.5, Basic Guide for Processing Cases with Statute of Limitations Issues, for additional guidance. Reminder: A return must be considered valid for the ASED to apply. Refer to IRM 25.6.1.6.14, Criteria for Establishing a Statute of Limitations Period. (5) You discover any errors when you math verify the valid return, See IRM 25.23.4.6.5.3, Missing Information, to determine the appropriate actions to take. (6) The valid taxpayer may have a filing requirement for the impacted year, The valid taxpayer has not filed a return, See IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions. (7) If the impacted year is tax year 2018, 2019, or 2020, Any Economic Impact Payment (EIP) was issued, See IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General. (8) The CN entity reflects an incorrect (or invalid) address, Conduct research using information available on CII, AMS, and IDRS to determine an appropriate address for the CN owner. Note: The address included on the most recent return received may not be the most current even if determined to be a valid return. Thorough research is necessary to determine the appropriate address to prevent issuance of correspondence to an incorrect address. IDTVA employees are encouraged to use their best judgment in identifying the correct address and must clearly document their research and reasoning when it is determined the most appropriate address is not the address on the valid taxpayer's correspondence or most recent return. If you are unable to identify the appropriate address through internal research, follow procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to attempt to contact the taxpayer by phone. If the taxpayer confirms the correct address, document the information in a CII case note. Do not send a letter requesting confirmation of the correct address if attempts to contact the taxpayer by phone are unsuccessful. Document attempts to contact the taxpayer and proceed to step (3). If a phone number is not available, proceed to step (3). If you were unable to determine the appropriate address through internal research and were unsuccessful in your attempts to contact the taxpayer by telephone, update the CN entity using the address from the following (to be applied in the order listed): Form 14039, Police Report, or Correspondence, unless a current year tax return determined to be valid has been received more recently. If a valid current year tax return has been received more recently, use the address on the valid return. Address found on CC IRPTR for the current year associated with income determined to belong to the valid taxpayer. Address found on the most recent prior year return determined to be valid.

# Complete Case Analysis (CCA)

25.23.4.6.4 (10-01-2025) Complete Case Analysis (CCA) To ensure all identity theft issues have been identified, complete case analysis (CCA) is required on all identity theft cases potentially impacting tax administration, including: Refund related, Income related, and Dependent related CCA includes but is not limited to the following: Research Description Tax Years Conduct a cursory review for apparent evidence of unresolved IDT issues. Prior Years - A minimum of three prior years. Continue in one-year increments until no indications of identity theft are found. Subsequent Years - All years after the year identified for the case. Example: The SSN owner filed for the first time in 2020. A review of the account indicates returns were filed for tax years 2018 and 2019. While the taxpayer did not include the tax years 2018 and 2019 on the Form 14039, these years must be fully researched for potential IDT issues. Example: The SSN owner claimed identity theft for tax year 2019. A review of the account indicates there is also identity theft for tax year 2016. The look back rule applies again by reviewing tax year 2015. If tax year 2015 is not impacted, no further look back is required. Documents Do not assume the individual filing the identity theft claim is the true owner of the Common Number (CN). Consider: All information received, Account research conducted, and Additional information available Note: An invalid return could include information that is consistent with the taxpayer's filing history. Refer to IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, for additional items to review to prevent the mishandling of an IDT case. Compliance If there is Compliance involvement and a determination of IDT for the same year: Reassign all years. Do not issue a letter to request additional information. Do not perform any account adjustments, credit transfers, etc. See Exhibit 25.23.4-5, IDTVA Routing Matrix. Dependent Dependent related IDT issues may be IRS identified when: Misuse of a TIN occurs on a return determined to be invalid. Refer to IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General, for additional information. IP PIN Determine if the taxpayer is already enrolled in the IP PIN program to identify information that may need to be provided to the taxpayer, such as: Opt in methods Issuance of the IP PIN Opt out See IRM 25.23.2.9.1, Opting into the IP PIN Program through the Individual Online Account, for additional details. When resolving accounts identified through completion of required research for the look back period, work: Tax years where IRPTR data is still available, and the module is not in retention. Tax years where IRPTR data is not available, but the module is not in retention due to current account activity (i.e., balance due, etc.) Tax years impacted by income related IDT with or without a filed return, TDI, ASFR, or Exam SFR issue. Do not adjust modules in retention, including tax years listed on Form 14039, unless: Reversing a tax offset will create a balance due, or It is necessary to resolve the taxpayer's issue. Update the activity code of the active module to RTTN### when requesting a module from retention. Include a CII case note indicating CCA was performed and the results of that research. Example: Invalid/Valid per IRPTR Data, lost refund. CCA completed - No additional impacted years. Example: Invalid/Valid per MFJ Refund Scheme. No lost refund. Completed required account research - Additional years impacted - refer to linked CII case(s). Example: Invalid/Valid per IRP Data. Lost refund. Account research completed as required - No additional years impacted. Any tax year identified through the CCA process must be addressed using the appropriate indicator for the case type. Refer to the table below: Note: When the taxpayer does not list or otherwise identify the tax year(s) in their claim, impacted tax years will be marked using the CCA literal that best matches the circumstances. Case Type Indicator Details (1) Taxpayer Identified - Affecting tax administration TC 971 AC 501 Each impacted year identified by the taxpayer on the claim, police report, or correspondence will be marked with TC 971 AC 501 using an appropriate MISC field literal. Refund Related (invalid return): Additional impacted years identified through CCA will be marked with TC 971 AC 501 using MISC field: REFCCA Note: Invalid returns reflecting a balance due will also be marked with TC 971 AC 501 using MISC field: REFCCA. . Income Related: Additional impacted years identified through CCA will be marked with TC 971 AC 501 using MISC field: ICMCCA. IRM 25.23.2-2, IMF Only TC 971 AC 501 — Taxpayer Initiated Identity Theft Case Closure (Tax-Related) - TC 971 AC 501. (2) Taxpayer Identified - Not affecting tax administration TC 971 AC 504 Income Related: Each impacted year identified by the taxpayer on the claim, police report, or correspondence will be marked with TC 971 AC 504 using an appropriate MISC field literal. Income Related: Additional impacted years identified through CCA will be marked with TC 971 AC 504 using MISC field: ICMCCA. Non-Tax-Related: The account will be marked with TC 971 AC 504 using an appropriate MISC field literal. Only one indicator will be placed on the account. Refer to IRM 25.23.2.8.1.1, TC 971 AC 504 with Miscellaneous Field Codes ACCT, ACCT-M, BOTH, BOTH-M, EMPL, EMPL-M, ICMCCA, NKI or NKI-M. See IRM 25.23.2-4, IMF Only TC 971 AC 504. (3) IRS Identified TC 971 AC 506 Each impacted year will be marked with TC 971 AC 506 using an appropriate MISC field literal. See IRM 25.23.2-8, IMF Only TC 971 AC 506 — IRS Determined Tax-Related Identity Theft Case Closure. (4) Dependent Related IDT TC 971 AC 528 The account (ENMOD) will be marked with TC 971 AC 528 using MISC Field: WI IP DEPND. Use January 1st of the current year for the Secondary Date to signify the processing year. Example: Form 14039 is filed to report the taxpayer suspects someone may be using their name and SSN to work and file taxes. The taxpayer says they were unable to file their TY 2019 return, because a return is already on file. The taxpayer explains that they began working in 2019 and this is their first time filing. Completion of CCA results in the discovery of returns meeting streamline criteria filed for TY 2017 and 2018. Further research results in the identification of income earned under the taxpayer's SSN for TY 2014-2016. The taxpayer was not of age to work during those years. There are no returns on file or Compliance issues for TY 2014-2016. TY 2019 will be closed with TC 971 AC 501, because the taxpayer was determined to be a victim of identity theft affecting tax administration and listed this year on Form 14039. TY 2017 and 2018 will be closed with TC 971 AC 501 REFCCA, because the taxpayer filed Form 14039 and was determined to be a victim of identity theft impacting tax administration for these years through CCA. TY 2014-2016 will be closed with TC 971 AC 504 ICMCCA input for each year, because the income related identity theft issue does not affect tax administration, and the tax years were not provided by the taxpayer. Cases created as a result of identification through CCA are to be worked, regardless of age, to ensure the taxpayer's identity theft issue is fully resolved without unnecessary delays.

# Documentation Requests, Return Processing and Missing Information

25.23.4.6.5 (07-15-2021) Documentation Requests, Return Processing and Missing Information Before you can proceed with resolving a case, there may be instances when you will need to take the following actions: Submit unprocessed returns to SP for processing Note: Refer to guidance under IRM 25.23.4.13.1, Identity Theft (IDT) Expedite Operations Assistance Requests (OARs) - (Cases that Meet Economic Burden Criteria 1-4 and Contain Unprocessed Original Returns; TC 976 Documents) - Austin IDTVA-A ONLY, if cases meet TAS economic burden criteria 1-4. Order returns/documents only when it is necessary for case resolution Note: For IDT1 cases originally established as IDT3 cases, all internal research must be completed in an effort to make an IDT determination prior to ordering documents. To prevent delays in resolution, only order the document when it is necessary to make a determination of IDT. Request missing schedules/forms and/or signatures from the TP Refer to the following IRM sections for additional guidance: IRM 25.23.4.6.5.1, Ordering Documents IRM 25.23.4.6.5.2, Unprocessed Documents IRM 25.23.4.6.5.3, Missing Information

# Ordering Documents

25.23.4.6.5.1 (10-01-2022) Ordering Documents Requesting documents from files may result in significant delays in case resolution. To prevent unnecessary delays, verify the document you are requesting is needed to make a determination and/or correct the account. Complete all required account research prior to ordering the document. You may find the information available in CII images, AMS history items, and IDRS Command Codes (TRDBV, IRPTR, IMFOLR, NAMES, etc.) is sufficient to make a CN ownership determination, verify nullity criteria is met, or determine the case is a MXEN or IJE issue. If the return and/or other documentation is not attached to your case and is not available in another CII case, order the document only if it is necessary to resolve the case. The CSR/TE resolving the IDT case will order the document. A document may be necessary, if any of the following conditions are met, unless an exception applies: No information exists on CC TRDBV for the duplicate return and/or schedules filed No income information is available on CC IRPTR The case requires routing to Automated Underreporter (AUR) or Exam The case is a true "MXEN" case Exception: Returns meeting No Move criteria or account move conditions requiring use of Form 12810, Account Transfer Request Checklist, do not need to be ordered to resolve the account. Refer to IRM 25.23.4.11.2, Tax Year Account Move Conditions, for additional information. The case is a Default True Scrambled SSN Case A non-streamline case Exception: Returns meeting No Move criteria or account move conditions requiring use of Form 12810, Account Transfer Request Checklist, do not need to be ordered to resolve the account. Refer to IRM 25.23.4.11.2, Tax Year Account Move Conditions, for additional information. A CP 36I was generated, but the Form 14039 was not scanned to the CII case Exception: Some CP 36I cases may not have the documents scanned to the case by the time you are ready to work your case. If you have a CP 36I case that is less than 30 days old, hold the case in your inventory to allow adequate time for the return to appear on CII, unless your research determines the return and any additional information/documentation are not necessary. Also leave a case note on CII/AMS "Awaiting CP 36I scanned docs" , or similar remarks. The decision to order the documents should be made on a case by case basis depending on other research and analysis conducted that assists you in making a correct CN determination. Having the return and Form 14039 available may provide additional information pertinent to your case. Caution: Because an external data breach return could have identical or similar information, you may need to order missing documents to determine if the TP has indicated they were the victim of a breach. This information may have been included on the Form 14039. Also refer to IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview and IRM 25.23.4.8.2.4, Identity Theft (IDT) with External Business/Preparer Data Breach Involvement. The Form W-2, Wage and Tax Statement, is missing and wages and withholding needs to be verified per paragraph (11) of IRM 21.6.3.4.2.2, Withholding (W/H) Tax Credit The return is missing schedules and/or required forms The return is filed under an ITIN and reports wages The taxpayer is deceased and you need Form 1310, Statement of Person Claiming Refund Due a Deceased Taxpayer, or court documents to issue a refund You suspect that the return is for another taxpayer with a valid SSN, but cannot locate the other SSN on NAMEI/NAMES You suspect that the return is for another tax year based on your research, but cannot validate this without the return Note: CSRs performing the resolving actions on a case should determine if additional information (which includes the Form 14039) is needed to make a determination of CN ownership. If enough information has been received or is available through internal research, work to resolve the case to completion. Requesting unnecessary information will delay the processing of the case. Exception: If the case meets CAT A or Discriminant Index Function (DIF) scoring criteria, per IRM 21.5.2.4.23.6, Discriminant Index Function (DIF) SCORE or CLASSIFICATION "Send Return(s) to Examination for Review", the return must be ordered. Caution: When a refund is due, do not order the return only to verify the signature. If the information has been transcribed on TRDBV, the signature should have been validated during processing. Assume the return had a valid signature and continue processing. In addition, do not order the return if the entity information is not present on TRDBV. If it was not transcribed, the address and name matched the information on MF. If you determine through additional research the signature is needed for other purposes and/or the entity information is incorrect, order the return. Note: This list is not all inclusive If the return is required and is not already attached to the case, utilize CC ESTAB using "DQ" as the definer. In the remarks section of the ESTAB request, annotate the following: "AM-ID Theft" and Scan to open CIIXXXXXX case. These annotations will notify Files to pull the returns as priority and to send the request to the Image Control Team (ICT) team to scan. This should reduce multiple CII cases. Caution: If reprocessing a return and research indicates prior filing by the spouse, see IRM 21.6.7.4.5, Multiple Uses of Taxpayer Identification Numbers - TRNS36F (DUPTIN Filing Condition), for additional information. If you do not receive the return within 30 days of the first request, submit a second CC ESTAB request. Refer to IRM 21.6.7.4.4.1(5), CP 36 (DUPF) - Control, for information about charge outs and Special Search requests if you have not received the return within 30 days of your second request.

# Unprocessed Documents

25.23.4.6.5.2 (01-28-2025) Unprocessed Documents While working IDT cases, you may identify unprocessed returns that must be addressed. For purposes of IDT resolution, a return posted with a TC 977 that has been scanned as a CII image will be considered unprocessed. IDTVA screeners will receive unprocessed returns from Submission Processing (SP) and/or Statutes that have indications of IDT (i.e., Form 14039, similar statements or "Identity Theft" is notated on the return, etc.). See IRM 25.23.4.6.5.2.1, Unprocessed Statute Returns or Transcripts (IDTVA Screeners Only), for specific procedures. For Compliance IDT cases, an original return with no TC 976/977 posted may be received from the referring Compliance Function. Research to determine if the return has been processed. See the chart below for additional guidance. If And Then (1) There is a TC 976 present on the account, The TC 976 is for the return in the case, The return does not need to be sent to SP for processing. (2) There is a TC 976 present on the account, The TC 976 is not for the return in the case, Search CII for the return associated with the posted TC 976, and link any related cases. For any return that does not have a posted TC 976, follow the procedures throughout the remainder of this IRM, beginning with paragraph (3). (3) There is no TC 976 present on the account, The return is present on CII or is an original return from a referring Compliance Function, Follow the procedures throughout the remainder of this IRM, beginning with paragraph (3). Priority treatment must be given to Operations Assistance Requests (OARs) and statute imminent circumstances. Screen all statute year returns to determine if the ASED is expiring or imminent. See the chart below for additional guidance. If Then (1) The current account ASED and the valid return ASED are both greater than 180 days, The account does not require statute protection actions. (2) The current account ASED and the valid return ASED are both 180 days or less, Do not abate tax. Input TC 560 before you send the case to SP for processing. Note: The ASED must post before sending to SP. Refer to IRM 25.23.2.5, Statute Protection, for quick assessment procedures. Reminder: Reference IRM 3.12.179.75.3, UPC 178 Reason Code 2 Assessment Statute Expiration Date (ASED), to prevent an unpostable 178-2. (3)The ASED for a valid return is expired, Do not abate tax. See IRM 25.23.4.9.2, Addressing Barred Assessments on Identity Theft (IDT) Cases, to determine if there is a barred assessment and identify the applicable initial case actions required to correct the account. (4)The ASED for an invalid return that will be moved to an IRSN is 180 days or less but has not expired, Do not abate tax. Research to determine if an IRSN was previously assigned to the taxpayer. Assign a new IRSN if one was not located through research. For Compliance IDT cases, contact the DITA team lead to request assignment of a new IRSN if one was not located through research. Refer to IRM 25.23.2.5, Statute Protection, to complete a quick assessment on the IRSN account. A return will be considered signed if the correspondence includes any form that contains a signed Jurat (e.g., Form 14039, Letter 3219C). Reminder: Both taxpayers' signatures must be present on jointly filed returns. See IRM 21.5.3.4.4.1, Special Handling of Signature Requests, for exceptions. Unprocessed returns deemed a nullity must never be sent to SP for processing as a TC 976. Follow procedures in IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, to make a nullity determination. If And Then (1) The TC 150 return has been determined to be a nullity through the Refund Scheme Listing, IRP Data or Schedule C Case Processing, or through verification of an RIVO determination, The unprocessed return has been validated as filed by the CN owner, Edit the unprocessed return per paragraph (11) below. Note: If there is an open CII case related to the unprocessed return, leave a CII case note documenting all actions taken. (2) There is no TC 150 posted, The unprocessed return has been validated as filed by the CN owner, Edit the unprocessed return per paragraph (11) below. Do not post TC 976. Note: If there is an open CII case related to the unprocessed return, leave a CII case note documenting all actions taken. (3) If the unprocessed return has been deemed invalid but does not meet nullity criteria, The TC 150 return has been validated as filed by the CN owner, For Compliance IDT cases, see paragraph (6) below. For all other cases, edit the unprocessed return per paragraph (11) below. Note: If there is an open CII case related to the unprocessed return, leave a CII case note documenting all actions taken. (4) If the unprocessed return has been deemed invalid but does not meet nullity criteria, There is no TC 150 posted, For Compliance IDT cases, see paragraph (6) below. For all other cases, follow the procedures detailed below: Research to determine if an IRSN was previously assigned to the taxpayer. Assign a new IRSN if one was not located through research. Edit the unprocessed return per paragraph (11) below. Do not post TC 976. Replace the TIN on the return with the IRSN assigned to that taxpayer. Note: If there is an open CII case related to the unprocessed return, leave a CII case note documenting all actions taken. For Compliance IDT cases that are not currently assigned to DITA but require an IRSN, do not route the return to SP. Follow procedures in IRM 25.23.10.5, Post Function Referral Procedures, to refer the case to DITA. Valid returns not processed as an original return have bypassed DIF scoring. Valid returns must be screened for DIF score criteria after the TC 976 has posted to the account. See Exhibit 25.23.4-21(2), Input, Annotations and Action Requirements for Streamline/Non-streamline Case Processing, If/Then scenario (3) for additional information. Review the chart below to determine if an account condition exists which must be addressed prior to forwarding a return to be processed. If And Then (1) IDRS CC TXMOD reflects a Master File (MF) status of 02 or 03, Refer to IRM 25.23.2.6.5, Closing Identity Theft Cases with Tax Delinquency Inquiries (TDI). Note the appropriate TC 59X code in the left margin of the return. (2) IDRS CC TXMOD reflects an unreversed TC 971 AC 121/124/129, Input TC 972 AC 121/124/129 to reverse it. (3) The return being processed is Married Filing Jointly (MFJ), The current filing status is not MFJ, Input TC 594 CC 084 on the secondary TIN to prevent separate TDI activity. Cross reference the primary TIN. (4) The return being processed is Married Filing Jointly (MFJ), The current filing status is MFJ with someone other than the spouse on the return, Input TC 592 to reverse the TC 594 CC 084 for the invalid return previously processed. Input TC 594 CC 084 on the secondary TIN to prevent separate TDI activity. Cross reference the primary TIN. Reminder: TC 592 will reverse all TCs 59X on the module. Input of a TC 594 CC 084 cannot be post delayed. If the valid taxpayer is the secondary on a valid MFJ return, monitor the account for one week. After one week, input TC 594 CC 084 to cross reference the correct spouse. (5) The return is part of a Compliance IDT case, The case is being worked by a function that addresses unreported income, Verify all income belonging to the taxpayer(s) is included on the return to be processed. Follow your functional IRM for specific guidelines to address incomplete returns, if necessary. Corrective actions to resolve the identity theft issue will be taken prior to forwarding the unprocessed return to post the TC 976. Follow applicable streamline/non-streamline procedures to correct the account. Note: In situations where the aMend tool will not perform the necessary account adjustment, another IAT adjustment tool must be used. Note: If the case meets previous action criteria, proceed to paragraph (13) below. Create an IDRS control base to monitor for posting of the TC 976. See IRM 25.23.4.3.1.1, Monitoring Case Controls, for additional information. After completing the necessary actions to resolve the case, continue to paragraph (11) below. When updating the entity, refer to the table below for additional considerations: If And Then (1) There is a name line change from any filing status to MFJ, Update ENMOD prior to sending the return to SP for processing to prevent UPC 166. See IRM 3.12.179.68, UPC 166 Reason Code 0 Filing Status Code (FSC) Mismatch, for additional information. (2) There is a name line change from MFJ to any other filing status, The module does include Self-Employment income for the secondary taxpayer, Update ENMOD prior to sending the return to SP for processing to prevent UPC 166. See IRM 3.12.179.68, UPC 166 Reason Code 0 Filing Status Code (FSC) Mismatch, for additional information. (3) There is a name line change from MFJ to any other filing status, The module does include Self-Employment income for the secondary taxpayer, Address the invalid return. If the invalid return meets nullity criteria, input a full back out of the return figures, unless that action will cause a barred statute. If the return does not meet nullity criteria, follow procedures in, IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, and move the return to an IRSN. For Compliance IDT cases, see paragraph (6) above. Update ENMOD to remove the secondary taxpayer information after the actions taken to nullify or remove the invalid return from the account have posted. Valid unprocessed returns must be edited prior to sending for processing: To prevent the valid return from unposting, edit the return with SPC 'B' in the right margin between the secondary TIN and the Presidential Election Campaign Fund (PECF) designation per the instructions in IRM 3.12.2-4, Special Processing Codes. This allows the return to bypass UPC 126 and all UPC 147 Reason Codes, except RC 4. Notate 'ITVA' in the upper left-hand corner. Refer to IRM 21.5.2.4.23.7, Coding and Editing Procedures, for additional guidance that may be applicable. All edits must be made in 'Red' pen/pencil only. It is also acceptable to notate all edits on CII images using the annotation tools then underline the changes in 'Red'. Send unprocessed valid returns to Submission Processing. Monitor the account for the posting of TC 976. Upon posting, the resulting -A Freeze must be released. Input TC 290 .00 with the appropriate Hold Code depending on the facts and circumstances of the case. Use the table below to determine the appropriate Submission Processing Site: If Then For campuses with Submission Processing (SP), Route the return to your local SP using a Form 1725 or similar local routing slip. Include, "Post TC 976 - Do not send to ICT to be imaged", or similar instructions in the remarks field. Exception: If a paper return is received in response to a Letter 5064C, only input, "Post TC 976", as the remarks. Exception: Unprocessed Forms 1040-NR, 1040-SS, and 1040-PR will be sent to Austin Service Center. If 40 days have passed, and the TC 976 has not posted, see IRM 25.23.4.6.5.2.2, Unprocessed Returns - 40 Day Suspense Time Frame Expired. For campuses without Submission Processing (SP), Using a Form 3210, route the return to Kansas City SP at: Internal Revenue Service Stop 6052 333 W Pershing Road Kansas City, MO 64108 Include, "Post TC 976 - Do not send to ICT to be imaged", or similar instructions in the remarks field. Exception: If a paper return is received in response to a Letter 5064C, only input, "Post TC 976", as the remarks. Exception: Unprocessed Forms 1040-NR, 1040-SS, and 1040-PR will be sent to Austin Service Center. If 40 days have passed, and the TC 976 has not posted, see IRM 25.23.4.6.5.2.2, Unprocessed Returns - 40 Day Suspense Time Frame Expired. If it is determined the case meets previous action criteria per IRM 25.23.4.10.6, Identity Theft (IDT) Previous Action, refer to the table below: If Then (1) A TC 150 is present and the ASED is greater than 90 days, Send the return to ICT as an XRET using Form 13503. Refer to the Form 13503 ICT XRET Cover Sheet Sample located on the IDTVA Hub. (2) A TC 150 is present and the ASED is less than 90 days, Create a CII case. Send the return for exception scanning. Input a TC 971 AC 010 to generate TC 977. Once scanned to the case, work following applicable procedures per IRM 21.5.3.4, General Claims Procedures. (3). No TC 150 is present (i.e., IDT was on secondary TIN, IDT return was Voided/Deleted, Follow the procedures beginning at paragraph (2) above.

# Unprocessed Statute Returns or Transcripts (IDTVA Screeners Only)

25.23.4.6.5.2.1 (04-28-2025) Unprocessed Statute Returns or Transcripts (IDTVA Screeners Only) IDTVA screeners receive unprocessed returns from Submission Processing (SP) and/or statutes that have indications of IDT (i.e., Form 14039, similar statements, "identity theft" is notated on the return, etc.). It is the responsibility of the IDTVA screeners to quickly determine if IDT has occurred, if the unprocessed return is "valid" or "invalid" , and the applicable actions to take. When the Form 14039 included with a tax return does not indicate the taxpayer's information was used to file taxes, consider the claim as reporting non-tax-related IDT, and take the following actions: Detach Form 14039. Notate in the left-hand margin of the Form 1040/A/EZ/SR what is being detached. Notate on the Form 14039 the current date and what is being detached. Route Form 14039 to ICT as an IDT4 using the IDTVA-A ICT Batch Sheet located on the IDT Hub. Continue screening the tax return. Example: Form 14039 is included with the taxpayer's 2019 return filed on Form 1040. Section A Option 1, indicating the form is being submitted for the taxpayer, and Section B Option 1, indicating the taxpayer suspects their information has been used for tax purposes, are both marked. The taxpayer provides an explanation indicating their Social Security Card and ID were in their wallet when it was lost. Detach Form 14039 from the return. Notate on the Form 1040 "detached Form 14039 sent to ICT" . Notate on Form 14039 the current date and "detached from Form 1040 TY 2019" . Research the account and unprocessed return to determine if any of the returns may be considered a nullity. Note: The screening process should be completed even if it appears the return was previously screened (SPC "B" and "ITVA" are present on the unprocessed return). When the return being screened has a stamped Document Locator Number (DLN), refer to the table below to determine where the return originated and the appropriate actions to take: If And Then (1) The DLN matches the return posted to MF, There is an open IDT(X) CII case or assigned RIVO/NCAT control (not a generic number), Send the return to files per IRM 21.5.1.4.9, Re-Charging and Re-Filing Documents, or follow IRM 21.5.1.4.10, Classified Waste, as applicable. Note: Determine why the return was sent to process (i.e., AMS, CII, history, etc.) prior to taking any actions. (2) The DLN matches a return NOT posted to MF (i.e., Voided/Deleted or Identity Theft found on TRDBV), Regardless of whether or not there is an open IDT(X) CII case or assigned RIVO/NCAT control (not a generic number), Continue the screening process. See paragraph (5). If during the screening process it is determined tax-related IDT did not occur, perform the following actions: Circle out any incorrect edits (SPC "B" and "ITVA" ). Exception: If any TC 971 AC 501/506 is present on CC ENMOD/IMFOLE that is not being reversed, edit the return per paragraph (7). Reverse any incorrect IDT indicators (i.e., TC 971 AC 501/506/522). Forward the return to SP, ICT or your local statute unit, as applicable. Use IRM 25.23.4.8.1, Identity Theft (IDT) Determinations - Schemes, and IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, along with the chart below: If And Then (1) The TC 150 return has been determined to be a nullity utilizing streamline processing, The unprocessed return has been validated as filed by the CN owner utilizing IRP data for the year of the screened return. For streamline criteria and determinations see IRM 25.23.4.8.1, Identity Theft (IDT) Determinations - Schemes, and IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing. Edit the unprocessed return per paragraph (8) below and continue to paragraph (9). (2) Extended research is needed to make a determination of invalid and/or valid return (i.e., less than 3 years IRP data, more than one TC 976/977, TC 610 payment, MFT 32 issues, transcript non-streamline procedures or meets criteria in IRM 25.6.1.13, Barred Assessments/Barred Statute Cases, etc.). The current account ASED has not expired and is not within 180 days. Edit the unprocessed return per paragraph (8) and send the return to SP for processing. (3) Extended research is needed to make a determination of invalid and/or valid return (i.e., less than 3 years IRP data, more than one TC 976/977, TC 610 payment, MFT 32 issues, transcript non-streamline procedures or meets criteria in IRM 25.6.1.13, Barred Assessments/Barred Statute Cases, etc.). Current account ASED has expired or within 180 days. Refer to paragraph (9). Note: If there is an open CII case related to the return you are screening, input a case note indicating the action being taken (i.e., valid return sent to SP to post TC 976, ASED updated and return being held by IDTVA screener until TC 976 posts, etc.). If it is determined the IDT issue was previously resolved and there is a valid return that needs to be addressed, follow the chart below. If And Then (1) A TC 150 is present. The ASED is greater than 90 days. Send the return to ICT as an XRET using Form 13503. Refer to the Form 13503 ICT XRET Cover Sheet Sample located on the IDTVA HUB. (2) A TC 150 is present. The ASED is 90 days or less. Create a new CII case. Use Category Code XRET and Program Code 40051. If TC 977 is not present, input a TC 971 AC 010. Reassign the case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment for Non-IDT Cases located on the IDTVA Hub. Contact IDTVA P&A to advise there is a statute return. Provide the CII case ID. (3) No TC 150 is present (i.e., IDT was on secondary TIN, IDT return was Voided/Deleted, or moved to MFT 32). The ASED is at least 180 days. Edit the return per paragraph (5) and forward to SP. (4) No TC 150 is present (i.e., IDT was on secondary TIN, IDT return was Voided/Deleted, or moved to MFT 32). The ASED is 180 days or less. Create a new CII case. Use Category Code XRET and Program Code 40051. If TC 977 is not present, input a TC 971 AC 010. Reassign the case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment for Non-IDT Cases located on the IDTVA Hub. Contact IDTVA P&A to advise there is a statute return. Provide this CII case ID. An unprocessed return from the TIN owner must be edited before it is sent to SP for processing. Refer to IRM 21.5.2.4.23.7, Coding and Editing Procedures, and IRM 21.5.1.5.5, Processing/Reprocessing CII Tax Returns, for additional guidance that may be applicable when sending a return for processing. Perform the following actions: Notate "ITVA" in the upper left-hand corner of the return. Edit the return SPC "B" (in the right-hand margin between the secondary TIN and PECF designation). This will allow the return to bypass all the UPC 147 Reason Codes except RC 4. See IRM 3.11.3.3.7.6, Special Processing Code (SPC). If there is a name line change, update ENMOD prior to sending the return to SP for processing (e.g., single to joint).This will allow the return to bypass the UPC 166. See IRM 3.12.179.68, UPC 166 Reason Code 0 Filing Status Code (FSC) Mismatch. When the unprocessed return is Married Filing Jointly (MFJ), input TC 594 CC 084 to satisfy the secondary TIN's filing requirement, if one is not present. Make sure there is a name line for the secondary TP's TIN on the Master File (MF) for the same tax year or earlier. If not, update ENMOD with a name line for the secondary TP's TIN for the same year. If CC TXMODA reflects a MF status of "02" or "03" , see IRM 25.23.2.6.5, Closing Identity Theft Cases with Tax Delinquency Inquiries (TDI), for additional information. To ensure the unprocessed return will post as a TC 976, consideration of the current and "valid return" ASED must be made prior to sending the return to SP for processing. If Then (1) Current account ASED is greater than 180 days, Edit the return per (8). Then send the unprocessed return to SP or your local statute, as applicable. (2) Current account ASED is within 90 days or has expired and the valid return ASED will be greater than 180 days. Caution: Ensure the correct received date is being used prior to updating the ASED. Research CC TRDBV for a previously Voided/Deleted or Identity Theft return that matches the "valid return" , and/or CC TXMOD/IMFOL for a TC 610 payment. Note: Interest penalty date in TRDBV, access code IA, is equal to the received date of the return. Updating the ASED Input a TC 560 on the account to update the ASED to 3 years from the received date of the valid return. Caution: To prevent an unpostable (UPC 178-2), see IRM 3.12.179.75.3, UPC 178 Reason Code 2 Assessment Expiration Date (ASED). Input TC 971 AC 522 following IRM 25.23.2.4.4, Initial Allegation or Suspicion of Tax-Related Identity Theft - IMF Identity Theft Indicators, as applicable. Open a MISC control base to your IDRS number using Category Code "MISC," activity "PNASEDDATE" (DATE = purge date), status "B" and current date. Hold the return until the ASED has posted (2-3 weeks). Note: Per IRM 3.11.3.73.2, Statutory Protection Cases. A statute clearance stamp is not required when SPC "B" is present. After The ASED Has Updated Once the ASED has posted, complete edits on the valid return, as applicable. Update the activity to SNT2PROCES and close the MISC base. Reminder: Corrective actions to resolve the identity theft issue will be taken prior to forwarding the unprocessed return to post the TC 976. Create a new IDRS control base to monitor the posting of the TC 976. Input a TC 290 .00 with RC 139 using the appropriate hold code to release the -A freeze. See IRM 25.23.4.3.1.1, Monitoring Case Controls, for additional information. (3) Valid return ASED will be within 180 days of expiration. Note: 180-day time frame allows for the ASED and TC 976 to post. Set aside to create a CII case. Take the following actions, once the case has been created. If the ASED is within 90 days, prepare and submit Form 2859, for a quick assessment following IRM 25.23.2.5, Statute Protection, as applicable. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. If the ASED is within 91-180 days, continue remaining actions. Input a TC 560 on the account to update the ASED to 3 years from the received date of the "valid return" and suspend until posted. Caution: To prevent an unpostable (UPC 178-2), see IRM 3.12.179.75.3, UPC 178 Reason Code 2 Assessment Expiration Date (ASED). Follow applicable streamline/non-streamline procedures to correct the account. Refer to IRM 25.23.4, IDTVA Paper Process, for guidance on adjusting the account. Reminder: Corrective actions to resolve the identity theft issue will be taken prior to forwarding the unprocessed return to post the TC 976. Create an IDRS control base to monitor the posting of the TC 976. Input a TC 290 .00 with RC 139 using the appropriate hold code to release the -A freeze. See IRM 25.23.4.3.1.1, Monitoring Case Controls, for additional information. Complete "valid return" edits, per paragraph (7). Input TC 971 AC 522, per paragraph (10). Send the return to designated SP area for processing. Input TC 971 AC 522 following IRM 25.23.2.4.4, Initial Allegation or Suspicion of Tax-Related Identity Theft - IMF Identity Theft Indicators, as applicable. This includes other years of unresolved IDT that may be found during the screening process, or have been identified by the taxpayer (via Form 14039 or similar statement).

# Unprocessed Returns - 40 Day Monitor Time Frame Expired

25.23.4.6.5.2.2 (10-01-2025) Unprocessed Returns - 40 Day Monitor Time Frame Expired If an unprocessed return is sent to SP and the TC 976 has not posted after the forty (40) day monitor time frame has expired, use the following table to determine how to continue processing the case. Caution: The instructions in this table are only for the handling of a taxpayer's return as submitted. You must still review the account to determine if the submitted return resolves any outstanding Compliance issues. If Then (1) TXMOD Reflects a rejected (RJ) TC 150 with an ERS status code, ERS has corresponded with the taxpayer to obtain required information/documentation. Monitor the account until the rejected TC 150 has converted into a TC 976. (2) The ASED for the new valid return was not updated, as required, Update the ASED to the correct date based on the earliest IRS Received Date. After the new ASED has posted resubmit the valid return to SP. Caution: Failure to update the ASED prior to sending the return to be processed will result in an Unpostable Code 150-0 or 150-1. (3) Unpostable Code 126-0, See IRM 25.23.4.10.2, Identity Theft (IDT) Cases/Transcripts with RIVO and/or TPP Involvement Resolution Tables, for additional instructions. (4). The TC 976 unposted (other than UPC 126-0), Monitor the case on IDRS for an additional 40 days to allow the Unpostables unit time to resolve the unpostable. If the additional 40-day suspense time frame elapses and the TC 976 still has not posted, take the necessary actions, to correct the account using the applicable procedures, outlined in IRM 25.23.4, IDTVA Paper Process. (5) There is no indication that a TC 976 will be input (such as an unpostable, etc.), Monitor the case on IDRS for additional 40 days. If the additional 40-day time frame elapses and the TC 976 still has not posted, close the IDRS control base.

# Missing Information

25.23.4.6.5.3 (03-11-2024) Missing Information If you have made a Common Number (CN) ownership determination and the valid taxpayer's return is missing information (e.g., signatures, schedules, forms) needed to adjust the account to the return figures, determine if it is necessary to request the missing information. Use the table below to identify appropriate research for various sections of the tax return. Section Comments and References (1) TIN requirements TIN requirements vary depending on the deduction and/or credits claimed on the return. Refer to the instructions for the form (tax year specific) Find a product. See Table Scenarios (4) and (6) for credits. (2) Income Refer to the instructions for the form (tax year specific). Find a product. (3) Deductions and Tax computation See IRM 21.6.4.4, Working Tax Computation / Accounting Period Changes, and its subsections for deductions, other taxes (i.e., self-employment tax, etc.), and various methods of tax computation. (4) Non-refundable credits These credits reduce tax liability and are generally not refundable. Certain credits may become refundable after the tax liability has been brought to zero. See IRM 21.6.3.4.1, Nonrefundable Credits Procedures, and its subsections to determine if a form or schedule is required to be provided with the return to claim a specific credit. (5) Refundable credits These credits are refundable. For CARES and ARPA credits, see IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, IRM 25.23.4.21.2, ARPA - Advanced Child Tax Credit (AdvCTC) - General, and/or IRM 25.23.4.21.3, ARPA - Excess Advance Premium Tax Credit (APTC) Repayment Relief. For all other refundable credits, see IRM 21.6.3.4.2, Refundable Credits, and its subsections to determine if a form or schedule is required to be provided with the return to claim a specific credit. (6) Signature Proceed to paragraph (3) below. If the return is missing a form or schedule required to be attached or is not signed, see IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written).

# Credit Transcripts - IDT6/IDS6

25.23.4.6.6 (02-04-2020) Credit Transcripts - IDT6/IDS6 Credit Transcripts generate under the following circumstances: A credit remains on the module after the RSED has expired. A credit is held due to RIVO involvement. Credit transcripts are referred to IDTVA as IDT6/IDS6 cases. These cases may include a TC 976 return that has not been addressed (-A Freeze). IDTVA screeners determine if the referral is appropriate. Any referral that was received in error will be returned to the originating employee/function.

# Credit Transcripts - IDT6/IDS6 (IDTVA Screeners Only)

25.23.4.6.6.1 (10-01-2022) Credit Transcripts - IDT6/IDS6 (IDTVA Screeners Only) Use the following table to identify the type of transcript received: Transcript Type Identifying Factors (1) Unresolved Credit (IDTVA-A) The case was closed on IDRS with Category Code IDT1, IDS1, IDT3, IDS3, IDT4, IDT5, IDT6, IDS6, IDT8, or IDS8, but all actions were not taken to fully resolve the account. IDTX is now used by IDTVA when a Form 15227, Application for an IP PIN, is received and is also used by other functions. IDT cases previously resolved under the Category Code IDTX will be received when all actions were not taken to fully resolve the account. Note: If you cannot identify the original Category Code with which the case was closed, review CC IMFOLA to locate the identity theft adjustment. The first 5 digits of the employee's IDRS number can be used to determine if the referral was appropriate. Use the IDRS - Unit and USR Database found on SERP Who/Where to determine if the adjustment was input by an IDTVA employee. (2) Unresolved Credit (Specialty Functions) The case was closed on IDRS with Category Code IDI1, IDI2, IDI3, IDI4, IDI5, IDI6, IDI9, or IDII, but all actions were not taken to fully resolve the account. Note: If you cannot identify the original Category Code with which the case was closed, review CC IMFOLA to locate the identity theft adjustment. The first 5 digits of the employee's IDRS number can be used to determine if the referral was appropriate. Use the IDRS - Unit and USR Database found on SERP Who/Where to determine if the adjustment was input by an IDTVA employee. (3) RIVO Involvement AM01 (-R Freeze) AM17 (P- Freeze) TC 971 with AC 052, AC 121, AC 122, AC 123, AC 124, AC 129, AC 134, AC 140, AC 199, AC 617 A Computer Condition Code (CCC) "1" A CCC "3" and another RIVO marker A CC NOREF history with an IDRS control base (open or closed) containing an IDRS assignment number 148XXXXXXX TC 971 AC 128 with MISC field "AQCPTC191" or "AQCPTC195" Unreversed Taxpayer Protection Program (TPP) indicators; refer to IRM 25.25.6.1.7, Taxpayer Protection Program Overview, for a list of indicators Letter 4464C and/or CP 05 notice Letter 4415C, TC 971 with AC 044 MISC>CP05A, or Examination correspondence Caution: The presence of TC 971 AC 199 does not automatically indicate RIVO involvement. See IRM 25.25.5-2, Transaction Code (TC) 971 Action Code (AC) 199 Miscellaneous (MISC) Field Literals for RIVO, for additional information. Only certain transcripts with RIVO involvement should be received in IDTVA. Refer to the table below for descriptions of Credit Transcripts with RIVO involvement IDTVA will resolve: If the Account Reflects And (1) No open RIVO IDRS control, or an IDRS control was opened by AMRH, with subsequent adjustment action to reverse the return information by RIVO, Memphis QRP, Brookhaven Pre-Refund Team, or Exam, and An unresolved credit remains on the module from a TC 610 or TC 670 payment, and the taxpayer's valid return is not on MFT 32 or TRDBV does not show GUF Void/Deleted, and A Letter 112C requesting a return was sent. The taxpayer submits a return in response to the Letter 112C. (2) There is an open IDRS control to RIVO 148NNNNNNN or 065NNNNNNN, or There is an open IDRS control to Return Integrity & Compliance Services (RICS), Earned Income Tax Credit (EITC), Refund Tax Compliance (RTC), or Questionable Refund Program (QRPA) 1381NNNNNN. An unresolved credit remains on the module with no subsequent adjustment action or activity by RIVO, Memphis QRP, Brookhaven Pre-Refund Team, or Exam, and There is a freeze condition that involves a -A Freeze, or there is an IDT issue that was not fully resolved. (3) There is no open RIVO IDRS control and the freeze is due to an External/Bank Lead issue, identified by TC 720. Note: The TC 720 amount may be less than the TC 846 if bank fees were deducted. An unresolved credit remains on the module, and There is a freeze condition that involves a -A Freeze, or there is an IDT issue that was not fully resolved. (4) There is no open RIVO IDRS control and the module contains a TC 971 with AC 134, AC 199, or AC 617. Exception: TC 971 with AC 199 with MISC>DPC is not RIVO related. Exception: If the module contains an unreversed TC 971 with AC 124, see (6) below in this table. An unresolved credit remains on the module with no subsequent adjustment action or activity by RIVO, Memphis QRP, Brookhaven Pre-Refund Team, or Exam, and There is a freeze condition that involves a -A Freeze, or there is an IDT issue that was not fully resolved. (5) There is no open RIVO IDRS control with no subsequent adjustment action or activity by RIVO, Memphis QRP, Brookhaven Pre-Refund Team, or Exam, An unresolved credit remains on the module and CC ENMOD shows TC 971 with AC 506 with any MISC field that contains the literal RICS, RIVO, AMTAP, or PRP, and There is a freeze condition that involves a -A Freeze. (6) There is no open RIVO IDRS control and the module contains TC 971 AC 121 or AC 124. An unresolved credit remains on the module, and There is a freeze condition that involves a -A Freeze. (7) There is no open RIVO IDRS control, the module contains TC 972 AC 121, and AMS does not show that the taxpayer authenticated. An unresolved credit remains on the module, and The freeze condition does not involve a -A Freeze. (8) There is no open RIVO IDRS control and the module contains TC 971 AC 123 or AC 129. An unresolved credit remains on the module. (9) There is no open RIVO IDRS control and Memphis QRP, or Brookhaven Pre-Refund has made an adjustment, or The module is in zero or debit balance. There is a freeze condition that involves a -A Freeze, or there is an IDT issue that was not fully resolved. (10) There is no open RIVO IDRS control and the module contains TC 971 AC 152, An unresolved credit remains on the module, the freeze condition does not involve a -A Freeze, and the return includes income/withholding that is not verifiable per IRPTR data. Note: Returns with only self-employment income and returns with minimal discrepancies in income and/or withholding should not be referred. Refer to the table below for Credit Transcript assignment procedures: If Then (1) The Credit Transcript referral does not meet IDTVA criteria, Return to the originating employee/function. Include the specific reason IDTVA criteria is not met. (2) The Credit Transcript referral is the result of an unresolved credit due to an IDT issue that was not fully resolved. Assign the case to the employee who worked the original case. Include a CII case note that indicates the case is being assigned due to an unresolved credit. If the employee who worked the case is no longer in IDTVA, assign the case to the IDTVA employee assigned to work a case for the same taxpayer, when possible. Assign the case to the general holding number when the employee who worked the original case is no longer in IDTVA and there is no other existing case. Note: When assigning the case to an IDTVA Specialty Function, the Category Code will remain IDT6/IDS6. Update the CII case Priority Code to 2. (3) The Credit Transcript referral with RIVO involvement meets IDTVA criteria. If there is an open case for the same taxpayer, assign the Credit Transcript to the IDTVA employee assigned to work that case. Note: When assigning the case to an IDTVA Specialty Function, the Category code will remain IDT6/IDS6. Update the CII case Priority Code to 2. Assign the case to the general holding number if there is no other existing case.

# Credit Transcripts Resolution

25.23.4.6.6.2 (03-09-2021) Credit Transcripts Resolution Refer to Exhibit 25.23.4-8, Order of Priority Listing - IDTVA-A and IDTVA Specialty Functions, for prioritization of IDT6/IDS6 cases. When resolving IDT6/IDS6 cases, do not update the category code based on the original case category code (for unresolved credits) or to IDT8/IDS8 (for RIVO involvement). Prior to taking action to resolve a credit transcript, ensure IDTVA criteria is met. If the case does not meet IDTVA criteria, return the transcript to the originating employee/function. Refer to IRM 25.23.4.6.6.1, Credit Transcripts - IDT6/IDS6 (IDTVA Screeners Only), for additional information. For Statute Year Credit Transcripts that do not have a -A Freeze on the module: Follow normal procedures to resolve an IDT issue, if necessary. Determine if the credit(s) are available for refund or offset. Refer to IRM 25.6.1.5, Basic Guide for Processing Cases with Statute of Limitations Issues, and IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim. Apply credits available for refund or offset to outstanding liabilities, if applicable. Manually refund any allowable amount remaining. Refer to IRM 21.4.4.3(3), Why Would a Manual Refund Be Needed?, and IRM 21.4.4.5, Preparation of Manual Refund Forms, for additional information. Move any credits not available for refund or offset to the Excess Collection File. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). For transcripts received that do not include a -A Freeze on the module and are not for a statute year, research the account to determine if there are any indications of IDT. If Then (1) You determine the account is impacted by IDT, Work the case following normal procedures. (2) You determine the account is not impacted by IDT, Follow normal freeze code procedures. Refer to IRM 21.5.6.4, Freeze Code Procedures. For Credit Transcripts with a -A Freeze on the module, determine if the -A Freeze is the result of an unresolved IDT issue or if an additional return was received after the IDT case was closed. If Then (1) The -A Freeze is the result of an unresolved IDT issue, Work the case following normal procedures. (2) The module reflects a credit that was not addressed during the resolution of an IDT case, a -A Freeze from an additional return received after the IDT case was closed is present, and there is another CII case for that return. Link the cases, and contact the other control to determine ownership of the case. If the additional return is an IDT return or the IDTVA employee is trained to work the other program (i.e., DUPF, XRET), the IDTVA employee will take ownership of both cases. If the additional return is not an IDT return and the IDTVA employee is not trained to work the other program, the IDTVA employee will resolve the credit, close the IDT6/IDS6 case, and advise the other control of the actions taken. (3) The -A Freeze is the result of an additional return received after the IDT case was closed, and there is not another CII case for that return, Determine if the additional return is an IDT return. If the additional return is an IDT return, follow normal procedures to resolve the case. If the additional return is not an IDT return, resolve the credit using the procedures outlined in (2) above. Do not address the additional return. (4) If there is a -A Freeze on a module with RIVO involvement, Follow normal procedures to resolve. See IRM 25.23.4.8.2.1, Identity Theft with RIVO Involvement, for additional information.

# Fraud Procedures

25.23.4.6.7 (04-28-2025) Fraud Procedures This section provides details for processing IMF fraudulent claims that do not have an existing treatment stream. A process has been created that enables potential tax fraud or non-compliance leads to be disseminated and subsequently acted upon. The process does not replace any existing referral methods. Generally, cases meeting fraud referral criteria possess any of the following characteristics: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Example: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Example: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ When you discover a potential fraud case, complete a Form 4442 and provide the case to your lead or manager for review and approval. Document all research completed in a CII case note and/or on Form 4442. Attach the Form 4442 to your CII case. Maintain an open control base and suspend the case while waiting for a response. Update the IDRS activity to "REF2ITVA" after suspending the case to the manager or lead. The lead or manager will review the case to ensure fraud referral criteria is met as shown in paragraph (3) above and there is not an existing treatment stream.. If the lead or manager determines criteria is not met or there is an existing treatment stream, the case will be returned to the employee with a message advising why the case does not meet fraud referral criteria. If criteria is met, the lead or manager will refer the case information to the Fraud Coordinator via email using the subject line: Fraud Referral (or similar). Caution: The case will remain in suspense in the employee's inventory awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Do not take action on the case until appropriate guidance has been provided. The HQ analyst will review the case to ensure fraud referral criteria is met. If not met, the HQ analyst will send an email to the lead/manager advising why the criteria was not met. If met, the HQ analyst will provide specific instructions to resolve the IDT issue on Form 4442 and will respond to the referring lead or manager. The HQ analyst will also address the suspected fraud.

# Non-Streamline Identity Theft (IDT) Case Processing

25.23.4.7 (11-06-2024) Non-Streamline Identity Theft (IDT) Case Processing Non-streamline case processing applies when IDT has been determined and the IDT return cannot be nullified. Any lost refunds on the IDT return should be moved to the IRSN where the related IDT return will reside. Reminder: For all non-streamline case processing, the TIN-Related Problem Research Sheet is required. See paragraph (8) of IRM 25.23.4.6.2, IDTVA - Additional Research and Required Actions, for additional information. Reminder: Each return/case must be considered separately for each tax year. If one or more returns cannot be nullified, the case will be worked as a non-streamline case. If one or more of the IDT returns can be nullified, they should be worked as a streamline IDT case following guidance in IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing. Reminder: When the only income reported on an invalid return was earned by the valid taxpayer, nullify the return. Every effort will be made to determine CN ownership based on the information provided and directly available prior to contacting the taxpayer(s). Caution: The "Social Security Administration Social Security Number Verification" printout is NOT acceptable proof of ownership of the CN. CN ownership determinations previously made due to receipt of the printout are not affected by this change. If a printout is or has been received for an unresolved case, the printout will be retained with the case but it will not determine ownership. See IRM 25.25.2.11, Identity Theft Scheme Criteria, for the characteristics of common IDT schemes. If NUMIDENT or, for ITIN cases, EUP/ITIN RTS, clearly shows the owner of the SSN or ITIN, proceed to guidance in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, to determine the appropriate scenario to resolve the case. See IRM 25.23.4.8.3, Non-Streamline Identity Theft (IDT) Determinations, for additional information on making Common Number (CN) ownership determinations..

# Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations

25.23.4.8 (10-01-2025) Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations Thorough account research must be completed following procedures in IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, prior to taking any actions to resolve the identity theft case. Careful consideration of all available information is necessary to ensure the correct taxpayer is identified as the CN owner and the correct case processing procedures are followed. Reminder: Statute year returns require additional research prior to taking action on an account. Review IRM 25.23.4.9, Statute Processing Considerations, to ensure all applicable statutes are protected. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ CN ownership/IDT determinations must be documented in a CII case note prior to taking action to resolve the account. When lead/manager concurrence or approval is required, the concurrence or approval must be documented by the lead/manager prior to taking action to resolve the account. The following subsections are intended to be considered in the order in which they are listed: IRM 25.23.4.8.1, Identity Theft (IDT) Determinations - Schemes IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing IRM 25.23.4.8.3, Non-Streamline Identity Theft (IDT) Determinations IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General IRM 25.23.4.8.5 , Identity Theft with Non-Filer Returns IRM 25.23.4.8.6, Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – General Refer to IRM 25.23.13, Income Related Identity Theft, for determinations and case processing guidelines related to questionable income. Before making a No IDT determination, consider the taxpayer's statement. If the statement: Includes Then (1) Loss of personally identifying information (i.e., driver's license or Social Security Card), fraudulent activity on their credit report, etc., they are a victim of non-tax-related identity theft. Resolve the case as an IDT4 following procedures in IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4 Overview. In these cases, a manual letter must be sent to address the taxpayer's concerns. Use Letter 4674C: Include the following suggested wording (or similar): "We reviewed your correspondence dated MM/DD/YYYY and found no indication that identity theft affected your tax account for the tax periods above." Use the date of the taxpayer's correspondence in place of MM/DD/YYYY. Include the specific reason(s) for the determination and language regarding the taxpayer's right to dispute the decision (i.e., providing additional information). Advise the taxpayer we have placed an identity theft indicator on their account to monitor activity. Inform them they may be able to obtain an IP PIN through the opt in process to protect their identity in the future. Caution: If the account reflects TC 971 AC 527, the taxpayer will not be able to use online self-help methods. Options available to the taxpayer should be provided in an open paragraph. If the taxpayer has a balance due after the IDT issue is determined not to affect tax administration, include language indicating collection activities will continue. (2) A request for an IP PIN and the account reflects a TC 971 AC 527 on CC ENMOD/IMFOLE. Note: For more information about this indicator, see IRM 25.23.2.8.6, Disabled Online Accounts TC 971 AC 527. Resolve the case as an IDTX following procedures in,IRM 25.23.3.2.7 Application for an Identity Protection Personal Identification Number (IP PIN) Overview - Form 15227. Exception: Do not update the category code for IDTVA Specialty cases. (3) There are allegations of Return Preparer Misconduct (RPM), Follow procedures in IRM 25.23.4.4, Taxpayer Inquiries Involving Identity Theft (IDT), paragraph (6) to determine if the case will be reassigned to RPM or closed with instructions to file an RPM claim. Due to the complexity of some cases, there may be instances where multiple treatment streams are required to fully resolve the account. Refer to Exhibit 25.23.4-23 , Complex Case Scenarios, for examples of cases that would require resolution with more than one treatment stream. Note: For any complex case that does not have an existing treatment stream, prepare and email Form 4442 using the subject line: Complex Case (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days.

# Identity Theft (IDT) Determinations - Schemes

25.23.4.8.1 (12-19-2023) Identity Theft (IDT) Determinations - Schemes Generally, the identification of a scheme is the result of a number of returns filed with similar characteristics determined to be identity theft. Cases meeting scheme criteria require completion of Complete Case Analysis (CCA) to determine if there are additional years impacted by identity theft. An individual return may be determined invalid based on characteristics of a specific scheme. In most instances, this determination does not require identification of consistencies or inconsistencies in the filing history. Returns determined to be invalid based on a scheme are resolved following applicable streamline procedures. Reminder: Each return must be considered separately and may impact credits related to the Coronavirus Aid, Relief, and Economic Security Act (CARES Act) and American Rescue Plan Act (ARPA). Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and their subsections for additional information. The following subsections are intended to be considered in the order in which they are listed: IRM 25.23.4.8.1.1, Known Fraud-Scheme Cases IRM 25.23.4.8.1.2, Refund Schemes IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement

# Known Fraud-Scheme Cases

25.23.4.8.1.1 (10-01-2025) Known Fraud-Scheme Cases Identity theft cases resulting from a known fraud-scheme may include one or more returns received for the tax year in question. Cases for taxpayers previously identified as potentially being impacted by a known fraud-scheme will be updated to Priority Code (PC) 6. If, while working an unidentified case, it is determined the return in question meets known fraud-scheme criteria, update the Correspondence Imaging Inventory (CII) case information to PC 6. Exception: Cases in PC 7 or PC 8 will not be updated to PC 6. To be determined an invalid return per a known fraud-scheme, the return in question must meet all requirements for the specific known fraud-scheme. Refer to paragraph (4) below for a list of known fraud-schemes and characteristics of each. All return characteristics plus the applicable number of additional commonalities for the fraud-scheme must be present. Each return must be considered separately for each tax year. Refer to the table below for a listing of each known fraud-scheme and its characteristics. Fraud-Scheme Name Return Characteristics Additional Commonalities (1) $50,100 W-2 Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional commonalities must be present. ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (2) $63,500 W-2 Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of one additional commonality must be present. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (3) Form 1099-R Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional commonalities must be present. ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (4) Recovery Rebate Credit (RRC) Velocity ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional commonalities must be present. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (5) Form 7202, Credits for Sick Leave and Family Leave for Certain Self-Employed Individuals, Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Exception: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional characteristics must be present. ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Caution: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (6) Line 25c Other Withholding Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional characteristics must be present. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (7) Repeating Wages and Withholding Scheme ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ A minimum of two additional characteristics must be present. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: The schemes listed above are separate from the Fraud Refund Scheme Listing job aid on SERP. When Form 7202, Credits for Sick Leave and Family Leave for Certain Self-Employed Individuals, is present, the return in question is excluded from known fraud-scheme consideration if at least one of the following is true: History of self-employment Cross reference EIN -E freeze condition with an unreversed TC 810 (may include -L freeze) For cases excluded from known fraud-scheme consideration, refer to the table below: Scenario Actions (1) History of self-employment or cross-reference EIN: A CN ownership determination must be made following existing procedures. See IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations. Resolve the account following applicable streamline/non-streamline procedures based on the determination made. (2) -E freeze condition with an unreversed TC 810 (may include -L freeze): Refer to IRM 25.23.4.10.12, Identity Theft (IDT) Cases with -E Freeze, for additional information. Document the determination in a CII case note. Include the name of the known fraud-scheme and the determination. Example: Invalid/Valid per Form 1099-R Scheme, lost refund. Complete account research conducted - no additional impacted years. For cases determined to meet known fraud-scheme criteria, follow applicable streamline procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. Reminder: Each return must be considered separately and may impact credits related to the Coronavirus Aid, Relief, and Economic Security Act (CARES Act) and American Rescue Plan Act (ARPA). Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and their subsections for additional information. For additional account conditions that may need to be addressed, refer to IRM 25.23.4.6.2, IDTVA - Additional Research and Required Actions, and Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing.

# Refund Schemes

25.23.4.8.1.2 (12-19-2023) Refund Schemes RICS, Integrity & Verification Operation (IVO) identifies refund schemes related to identity theft. Identity theft cases involving refund schemes may include one or more returns received for the tax year in question. Refer to the Fraud Refund Scheme Listing to determine if the return in question meets refund scheme criteria. Document the determination in a CII case note. Include the name of the refund scheme and the determination. Example: Invalid/Valid per AOTC Scheme, lost refund. CCA - no additional impacted years. For cases determined to meet refund scheme criteria, follow applicable streamline procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. Reminder: Each return must be considered separately and may impact credits related to the Coronavirus Aid, Relief, and Economic Security Act (CARES Act) and American Rescue Plan Act (ARPA). Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and their subsections for additional information. For additional account conditions that may need to be addressed, refer to IRM 25.23.4.6.2, IDTVA - Additional Research and Required Actions, and Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing.

# Married Filing Joint Scheme Involvement

25.23.4.8.1.3 (11-06-2024) Married Filing Joint Scheme Involvement In the MFJ Scheme, the IDT return has a married filing joint filing status. The thief takes two victims who are not married to one another and files a joint return or files a joint return for a couple who are married to one another. Since there is more than one IDT victim, additional research and actions are necessary. Note: The thief sometimes lists the same victim as a primary taxpayer on one return and a secondary taxpayer with a different spouse on another return. This can create a chain of SSNs that need to be researched. However, it does not have to be a multiple chain of SSNs used on a return to be considered a Married Filing Joint scheme. It can be one return with two unrelated victims. Research the primary and secondary TINs on the assigned case to determine if the TINs have been used on any type of return (valid or invalid), or any type of correspondence (e.g., Form 14039) indicating IDT. Example: The primary TIN may have been used as a secondary TIN on another IDT return. Example: The secondary TIN may have been used more than once. Example: John (primary) and Mary (secondary) file a joint return. Mary has another joint return under their TIN listed (as a primary) and Nancy (as a secondary). This return with Mary and Nancy meets Married Filing Joint Scheme Criteria. You must also research Nancy's SSN to see if they are listed as a primary or secondary taxpayer on another return. Example: Mary (primary) and Lucy (secondary) are filed on the return that meets Married Filing Joint scheme criteria. Lucy has not filed yet so a TC 594 CC 084 is under their TIN but nothing else. Example: Ex girlfriend/boyfriend (not married/living together) files without TP's knowledge/consent. Example: Mary (primary) and Lucy (secondary) are filed on the return that meets Married Filing Joint scheme criteria. Lucy has filed as a secondary on a return with Matt (as a primary). Lucy has two TC 594 CC 084 transactions under their TIN and nothing else. This list of examples is not inclusive of all the Married Filing Joint schemes that you may encounter. During the course of research, if a TIN was used on any return that meets the Married Filing Joint Refund Scheme Criteria, as found on the Refund Scheme Listing, you must address the affected TINs following the procedures in the If/Then chart below. If Then (1) The primary on the assigned case is a secondary on an invalid return OR the secondary is a primary on an invalid return. Create a new case on the XREF TIN, if a case does not already exist. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information on guidance for the IRS Received Date field when opening a CII case control. Assign the new or existing case to yourself. Link the new or existing case to your assigned case, if not already linked. Update the Category Code as needed. Address the IDT impacted modules for both TINs utilizing the applicable streamline procedures. See IRM 25.23.4.10, Resolving Identity theft Cases for specific instructions. (2) The primary on the assigned case is a secondary on a valid return AND the account under the XREF SSN does not reflect an indication of further IDT (e.g., 971-151, 594-084) OR The secondary is a primary on a valid return AND the account under the XREF SSN does not reflect an indication of further IDT. Proceed to IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, to correct the account. (3) The primary on the assigned case is a secondary on a valid return AND the account under the XREF SSN does reflect an indication of further IDT (e.g., 971-151, 594-084) OR The secondary is a primary on a valid return AND the account under the XREF SSN does reflect an indication of further IDT. Create a new case on the XREF TIN if a case does not already exist. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information on guidance for the IRS Received Date field when opening a CII case control. Assign the new or existing case to yourself Link the new or existing case to your assigned case, if not already linked. Update the Category Code as needed. Address the IDT impacted modules for both TINs utilizing the applicable streamline procedures. See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, for specific instructions. Resolve the new or existing case on the XREF TIN utilizing the applicable procedures in IRM 25.23.4, IDTVA Paper Process. (4) The secondary has not filed or informed the IRS of IDT (e.g., Form 14039) and there is NO indication of further IDT. Proceed to IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, to correct the account. (5) The secondary has not filed or informed the IRS of IDT (e.g., Form 14039) and there is indication of further IDT. Create a new case on the XREF TIN if a case does not already exist. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information on guidance for the IRS Received Date field when opening a CII case control. Assign the new or existing case to yourself Link the new or existing case to your assigned case, if not already linked. Update the Category Code as needed. Address the IDT impacted modules for both TINs utilizing the applicable streamline procedures. See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, for specific instructions. (6) The secondary TIN is used on another return as a secondary taxpayer on a valid return and there is NO indication on the XREF TIN of further IDT. Proceed to IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, to correct the account. (7) The secondary TIN is used on another return as a secondary taxpayer on a valid return and there is indication on the XREF TIN of further IDT. Create a new case for the further IDT Issue on the XREF TIN. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information on guidance for the IRS Received Date field when opening a CII case control. Assign the new or existing case to yourself Link the new or existing case to your assigned case, if not already linked. Address the IDT impacted modules for both TINs utilizing the applicable streamline procedures. See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, for specific instructions. Resolve the new or existing case on the XREF TIN utilizing the applicable procedures in IRM 25.23.4, IDTVA Paper Process. Reminder: TC 592 must be input to reverse TC 594 CC 084 cross referencing the unrelated secondary taxpayer. The TC 592 will reverse all TCs 59X on the module. Input of a TC 594 CC 084 cannot be post delayed. If the valid taxpayer is the secondary on a valid MFJ return, monitor the account for one week. After one week, input TC 594 CC 084 to cross reference the correct spouse. When a MFJ tax return does not meet MFJ Scheme criteria, you must determine if the case is an Invalid Joint Election (IJE). Taxpayers must know each other for an IJE determination to be made. Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, and the example below for additional information. Example: The Form 14039 states the taxpayer's boyfriend filed a MFJ return without their knowledge or permission. They have never been married, and the reporting taxpayer could not file their return electronically. Invalid Joint Election (IJE) must be considered in this case.

# Invalid Joint Election Consideration

25.23.4.8.1.3.1 (03-14-2025) Invalid Joint Election Consideration There are three situations where a joint return is invalid: Unlawful - The taxpayers had no legal right to file jointly. Forgery - One spouse did not sign the return. Invalid election - One of the individuals on the joint return did not elect to file a joint return. Note: Tacit consent is a factor to consider for invalid elections and forgery allegations. Do not confuse MFJ Schemes with invalid joint elections. If an invalid joint election (IJE) is determined, the IDT claim would be invalid. See IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, for additional instructions. Exception: When a determination of No IDT has been made because there is an Invalid Joint Election (IJE) issue, and a 2nd return is notpresent (e.g., XRET, DUPF), do not follow procedures in IRM 25.23.4.10.5.4, Amended or Duplicate Returns and Identity Theft (IDT) - No IDT Determinations, to create a separate case. Filing a joint return is an election. A joint return must be signed under penalty of perjury by both taxpayers to be a valid election for joint filing status. Note: Substitute for Return (SFR) and Automated Substitute for Return (ASFR) filed by the Service are never a joint return; however, a joint return can be filed after the assessment (associated with the SFR or ASFR) has posted. Many returns will not have signatures since returns are now filed electronically. Tacit consent must be considered in determining the validity of the joint filing status shown on the return. See IRM 25.15.19.2.4.1, Tacit Consent Factors, for additional information. A joint return may contain an invalid joint filing status election if: An original or amended joint return was filed and processed with only one signature on a paper filed return. The return was signed; however, it is established that the signature was forged and there is no tacit consent. The return was signed under duress. One of the individuals filed a timely original return using Single, Married Filing Separate (MFS), or Head of Household (HOH) and the joint return is not a valid amended return. Reminder: Complete IDRS research on both taxpayers' TINs. To determine if the taxpayers resided in a state that recognizes common law marriage, see IRM 5.19.11.7.1.2.2, Common Law Marriage. The marriage may not be legal for Federal tax purposes (even if the claim is received after the due date) and the claim allowed if the following verification is present: Court documents showing the marriage was not valid for the tax period involved: Copy of divorce decree or separate maintenance, Documents verifying that the taxpayers did not live together during the last six months of the tax year, such as a lease agreement, utility bills, etc., or An affidavit, signed and sworn under penalty of perjury, stating the marriage does not exist. Follow IRM 21.6.1.5.7, Married Filing Joint or Married Filing Separate is Invalid or Filed with Incorrect Status. An allocation of all return income, credits, and payments is required. If the taxpayer does not provide an allocation, use internal research resources to complete the allocation. Refer to IRM 21.6.1.5.8, Allocating Married Filing Joint Cases, for additional information. Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and their subsections to determine if the IJE return affected issuance of Economic Impact Payments, advance payments of ACTC, or application of any other tax provision intended to provide taxpayers with relief during the COVID-19 pandemic. If the taxpayers involved are considered legally married, determine if a case meets the invalid joint election criteria by considering all available information. Tacit consent factors will be considered and are found in IRM 25.15.19.2.4.1, Tacit Consent Factors. Close the case as no consideration for both the IJE and IDT claim, after reviewing the account for tacit consent factors when: There is not enough information to either rule out or prove tacit consent was implied, and The taxpayer has submitted no further documentation supporting their invalid joint election or identity theft claim. Close the case as No IDT after reviewing the account for tacit consent factors when: Research supports determining the taxpayer who filed the return could logically believe they were filing an accurate return with the reporting person's consent based on the tacit consent factors considered. Close the case as IJE after reviewing the account for tacit consent factors when: Research supports determining the joint election was not appropriate after consideration of the reporting person's statement and documentation and tacit consent is not implied. Follow the instructions in IRM 21.6.1.5.7, Married Filing Joint or Married Filing Separately is Invalid or Filed with Incorrect Status. Do not remove any Compliance assessments or income associated with the taxpayer being removed from the joint return. If TC 470 CC 90 was input, TC 472 must also be input when the taxpayer will have a balance owed. Determine if the taxpayer claiming fraud has a filing requirement. See IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, for more information. If the taxpayer has not filed or submitted a valid return with their claim, take the following action: Issue a Letter 5064C advising the taxpayer to submit a completed return including the required signatures or a statement indicating they did not have a filing requirement with a copy of our letter. Suspend the case for 40 days to allow the taxpayer time to respond. Exception: Do not request a new return if the return is six years or more overdue. If the taxpayer does not respond to the request for a return or the response does not include a valid return, follow the instructions below: Prepare Form 2209, Courtesy Investigation, as instructed by IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions. Issue a Letter 4674C as a closure letter. Include paragraph (a) reminding the taxpayer of their obligation to file a federal tax return. IDTVA-Exam Only - If AIMS is open, close the claim as "NOIDT" and notify Exam to work the case as an invalid joint election.

# Streamline Identity Theft (IDT) Case Identification and Processing

25.23.4.8.2 (10-01-2025) Streamline Identity Theft (IDT) Case Identification and Processing Streamline identity theft (IDT) case processing allows for the correction of accounts without assigning an Internal Revenue Service Number (IRSN) to the individual who filed the tax return determined to be invalid. Common streamline case processing terms for removing the invalid return information from the Common Number (CN) account include: Nullify: The process of adjusting the account to fully back out the invalid return figures or correct to the valid return figures. Nullity: The invalid tax return meeting streamline criteria. When the only income reported on an invalid return was earned by the valid taxpayer, the return can be nullified. These cases usually result from an identity theft claim stating the CN owner did not file the tax return and: May include multiple returns reporting the same exact income. May include a single return reporting income the CN owner earned. May reflect different addresses, dependents, credits, preparer, and direct deposit information with no indication of a preparer data breach. Caution: Although the income may be verifiable or consistent with the CN owner's filing history, the identity theft claim will be accepted based on the taxpayer's statement, unless there is clear and convincing evidence to support a No IDT determination. Example: Form 14039 is received stating the taxpayer's W-2 was stolen from their mailbox, and their return was rejected because someone else already filed a tax return in their name. Research of the account shows the TC 150 return is reporting the same exact income as the TC 976 return but has different direct deposit and tax preparer information. The determination is invalid/valid. The invalid return can be nullified following streamline procedures. Example: Form 14039 is received stating they suspect someone else filed a tax return in their name because they didn't receive their refund. Research of the account shows the TC 150 and TC 976 returns match exactly. The address, return figures, credits, refund amount, and direct deposit information are all consistent. It appears the taxpayer filed electronically and also submitted a paper return which posted before the refund could be issued. This is not identity theft. Each return must be considered separately for each tax year. If all invalid returns on an account meet nullity criteria, follow streamline procedures to resolve the case. You must determine the case type and make a CN ownership determination based on one or more of the following: IDT with RIVO Involvement IDT with Decedent Taxpayer Involvement IDT with IRP Data, Refund Scheme or Schedule C Involvement IDT with Preparer Data Breach Involvement IDT with Tax Preparation Software Misuse Note: Bullets 1-5 above are listed in the order in which the streamline process criteria is intended to be considered. In some instances, a case may have characteristics of more than one streamline process. Review the guidance for each process to determine which method will allow you to work your case effectively and efficiently. If, after applying streamline process criteria as described above, the return in question cannot be determined invalid, assignment of an IRSN may be required. See IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, for additional information. Then continue to IRM 25.23.4.8.3, Non-Streamline Identity Theft (IDT) Determinations, to make a CN ownership determination.

# Identity Theft (IDT) with RIVO Involvement

25.23.4.8.2.1 (10-01-2025) Identity Theft (IDT) with RIVO Involvement Return Integrity & Verification Operation (RIVO) is a pre-refund revenue protection program focused on identifying and stopping fraudulent refunds primarily generated from wage and withholding type of income. Much of this activity occurs very early in the tax year prior to normal processing time frames and involves only originally filed returns. Normal research and determination procedures should be followed when deciding whether an account with RIVO involvement can be worked as a streamlined case. Accounts with RIVO involvement may show any of the following: a TC 971 with Action Codes 121, 124, 129, 134, 199 (see Exhibit 25.25.5-2, Transaction Code (TC) 971 Action Code (AC) 199 Miscellaneous (MISC) Field Literals for RIVO. Refer to IRM 25.23.4.6.2.2, RICS-RIVO Involvement General Information and Research, for additional information. If RIVO indicators are reversed, the account should be reviewed for any subsequent account actions/conditions to determine whether the RIVO issue is resolved and whether it impacts your determination. If the TC 971 AC 121/124 has been reversed by a TC 972 AC 121/124, the RIVO Taxpayer Protection Program (TPP) process has been completed. If the TC 971 AC 129 has been reversed by a TC 972 AC 129 and the MISC field is populated with Last 6 DLN_IDT, the RIVO TPP process has been completed. If the TC 971 AC 134 has been reversed with a TC 972 AC 134 and the refund from the TC 150 has been issued, then RIVO has determined it is no longer interested in the return. Cases where RIVO determined the return to be fraudulent show one of the following: The account may be completely reversed. The account will be completely reversed except for a refundable credit. The account won't be reversed but TXMOD shows that a CP 05A notice was issued. The account won't be reversed but TXMOD shows a MISC field "AMWEX60033 NOCP05A" . The account may show a TC 971 AC 199 with the MISC field "AMWEX60033 REFEFDS or other similar miscellaneous literals" per Exhibit 25.25.5-2, Transaction Code (TC) 971/Action Code (AC) 199 Miscellaneous (MISC) Field Literals for RIVO. For cases with other MISC literals, the CSR must verify the return is "invalid" . Caution: Schedule C cases with RIVO involvement cannot be nullified, unless it has been determined to be a case on the "Refund Scheme Listing" , or meets the criteria inIRM 25.23.4.8.2.3, Identity Theft (IDT) with IRP Data, Refund Scheme or Schedule C Involvement. If there is no -A freeze and the taxpayer indicates that the TC 150 was backed out in error by RIVO, refer the case for resolution: Send an e4442 to RIVO stating that the return was backed out in error as identity theft needs to be reinstated. Employees that do not have e4442 capabilities should follow guidance in paragraph (2) of IRM 21.5.6.4.35.3.1.1, -R Freeze with RIVO Involvement and the Taxpayer is Claiming Identity Theft. Place the e4442 in the "RICS RIVO Complex Issue" , Not ID Theft Queue. On cases with a P- freeze and either of the following is present on the account, only RIVO can release the overpayment with these account conditions. If the account also contains a -A Freeze, work the case using normal procedures, but also refer the case to RIVO to release the freeze. Send an e4442 to RIVO requesting release of the P- Freeze. Use Referral type IRM and select category RICS IVO – CP 53X (TC 841 DLN 77711/77712/77713/77714) from drop-down. TC 841 DLN Blocking Series 77711, 77712, 77713, or 77714 OR TC 971 AC 123 MISC>TPP RECOVERY and TC 971 AC 805 MISC>REFCANCL18 The account may have been reversed by RIVO, before all the IRP data was made available. CP 36N and CP 36P transcripts generate when specific RIVO indicators are on CC TXMOD/ENMOD. If there is an -A freeze and your research supports a different determination (e.g., DUPF, IDT1, IDT3, 1040X, etc.,), refer to IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations, for additional information. Do not attempt to contact RIVO units or route cases to the following controls. Continue to follow established IRM procedures for your case type (examples: DUPF, XRET, IDT(X)/IDS(X), TPRQ, etc.). Open Control Explanation 14875XXXXX Generic number for closed CI prior year Transcripts. Taxpayer Relations has forwarded the transcript to the generic number 14876XXXXX Generic holding number used to input CC NOREF/NOREFE. RIVO is not actively working the case 148XX Generic number, if the case is not assigned to a specific TE or under the NCAT control A return is eligible to be referred to RIVO for verification if it meets all of the following criteria: The taxpayer has an SSN, not an ITIN The return was filed by the SSN owner The case is not a CP 36F The return is a current year return IRPTR is not available or does not match the income reported on the "current" year return IRPTR is not "fully loaded" for the "current" tax year If And Then (1) The 2nd return does not match IRPTR, or IRPTR information is not available, and the 2nd return is eligible to be referred to RIVO, RIVO determined the 1st return to be fraudulent per paragraph (4) above and meets all the requirements in paragraph (7), Perform the following actions: Accept the RIVO determination that the original return is fraudulent Open a control base to RIVO 1487777777, C# AMTOVERIFY, A using Category Code MXEN (2) Unresolved credits remain on the module with no subsequent adjustment action or activity by RIVO, Memphis QRP, Brookhaven Pre-Refund Team or Exam, Freeze condition involves an -A freeze, Do not open a new control base. Close all previous erroneous open control bases for 1487500000, 1487599998, 0650199999, and 0654599998. Also update the activity to" CLSTOIDTVA" This way RIVO will know IDTVA is resolving the case. Proceed to IRM 25.23.4.10.2, Identity Theft (IDT) Cases/Transcripts with RIVO and/or TPP Involvement - Resolution Tables, for additional processing guidance.

# Identity Theft (IDT) with Decedent Taxpayer Involvement

25.23.4.8.2.2 (10-01-2025) Identity Theft (IDT) with Decedent Taxpayer Involvement Fraudulent activity on a deceased taxpayer's account usually occurs very early in the tax year, prior to normal processing time frames. It typically involves filing a tax return but is not limited to those case types. Cases with deceased indicators can be identified on the following IDRS Command Codes. INOLET or IMFOLE: With the actual date of death (DOD) displayed. TXMOD or IMFOLT: TC 540 posted on the module. For more information on this indicator, see IRM 25.23.2.8.4.2, Locking Individual Accounts - Decedent Accounts. Decedent accounts may reflect fiduciary information as provided on Form 56, Notice Concerning Fiduciary Relationship, or with other legal documentation establishing the court appointed fiduciary relationship. Caution: This documentation may also be included with the submission of the identity theft claim. If fiduciary information is available on IDRS, compare IDRS with the Form 56 in the case documents. If it does not match, determine which is the most current. When Form 56, Notice Concerning Fiduciary Relationship, is received and IDRS does not reflect matching fiduciary information, route the form to Entity for processing. Refer to IRM 21.1.7-17, Forms – Routing Guide. Thoroughly research and consider all information available in documentation submitted and/or internal systems when making an identity theft determination for a decedent account. When the taxpayer (or surviving spouse) submitted the claim and the alleged victim is now deceased, the date of death (DOD) will not be a factor in making an identity theft determination. Refer to paragraph (8) below for additional considerations specific to decedent accounts. Then proceed to IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing. When the fiduciary or another individual files the claim on behalf of a deceased taxpayer after the date of death (DOD), or the case is IRS identified IDT, refer to the table below: Note: If additional information is needed to make an IDT determination, refer to paragraph (8) below. If And Then (1) The claim indicates someone filed a tax return using the deceased individual's information OR The case is IRS identified, The return in question is not verifiable and has an IRS received date after the DOD, Consider the return in question invalid meeting streamline criteria. Document your research and determination in a CII case note. Then, follow procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, to resolve the case. (2) The claim indicates someone filed a tax return using the deceased individual's information OR The case is IRS identified, The return in question is reporting verifiable income and has an IRS received date after the DOD, Consider the return in question invalid meeting streamline criteria when at least two (2) of the following are true: IRPTR indicates the income reported is invalid. IRPTR reflects a name that is not the taxpayer's. Note: This does not include typographical errors or names that may be interchangeable (i.e., Christopher vs. Chris, etc.). IRPTR indicates the EIN may be fabricated. Income reflected on IRPTR is not consistent with the taxpayer's income history (i.e., high wages after years of only Social Security or Retirement benefits, etc.). OR A scheme is met. See IRM 25.23.4.8.1, Identity Theft (IDT) Determinations – Schemes, and its subsections for additional information. OR Significant differences when compared to prior year returns are identified and meet requirements for a determination to be made. See Exhibit 25.23.4-1, 25.23.4-1, IRPTR/IDRS Data Decision Tree. If criteria in (1) above are not met, follow non-streamline procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, to resolve the case. (3) The claim indicates someone filed a tax return using the deceased individual's information OR The case is IRS identified, A return has not been received, The taxpayer is not a victim of identity theft. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (4) The claim indicates someone filed a tax return using the deceased individual's information OR The case is IRS identified, A return was GUF VOIDED/DELETED. OR A return was moved to MFT 32 AND The MFT 30 module does not reflect a return, The identity theft issue was previously resolved. Follow procedures in IRM 25.23.4.10.6, Identity Theft (IDT) – Previous Action. (5) The claim indicates an individual opened a line of credit, applied for or received benefits, or otherwise utilized the deceased individual's information, Research shows there is no impact to tax administration and no income related issue to address, The taxpayer's Personally Identifying Information (PII) is compromised. Follow procedures in IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, paragraph (8) Table Scenario (1). (6) The claim indicates someone received or earned income using the deceased individual's information, IRPTR reflects income reported for a tax year after the taxpayer's DOD, Follow procedures in IRM 25.23.13, Income Related Identity Theft, to make a determination and resolve the case. An individual who submitted the claim on behalf of the taxpayer prior to the DOD will be treated as an unauthorized third party when it is not a covered relationship and proof of a fiduciary relationship or legal guardianship is not provided. See IRM 25.23.4.18, Communicating with Taxpayers, for more information about covered relationships. IDTVA will not request this documentation for claims, unless it is a dependent related IDT issue. See IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) – General, and its subsections for additional information. Additional considerations for decedent accounts are listed below: Decedent cases usually require the filing of a Form 1310, Statement of Person Claiming Refund Due a Deceased Taxpayer. Check for evidence that is required when processing a deceased taxpayer's return. See IRM 21.6.6.2.21.2, Processing Decedent Account Refunds, for additional information. Refer to IRM 3.13.5.120.9, Inputting Name Changes for Deceased Taxpayers, to determine if it is appropriate to update the entity to reflect DECD. If additional information is needed to make a determination, address the request to the fiduciary when the information is available, or to the Estate of the taxpayer when it is not. Refer to IRM 21.3.3.4.16.5, Corresponding on a Deceased or Legally Disabled Taxpayer's Account, and follow procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written).

# Identity Theft (IDT) with IRP Data or Schedule C Involvement

25.23.4.8.2.3 (10-01-2024) Identity Theft (IDT) with IRP Data or Schedule C Involvement When conducting research on cases, you should determine the type of case you are working, such as invalid/valid, valid/invalid, or invalid/invalid, etc. Before proceeding with case processing, complete and thorough research must be conducted. To aid you in resolving the case, you will use various IRM guidance throughout this section and other IRM sections, in addition to resources listed below. IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview IRP Data - Research CC IRPTR/TRDBV to review case for W-2's, 1099's etc. IRPTR/IDRS Data Decision Tree - The decision tree in Exhibit 25.23.4-1 was created to assist employees in reviewing cases with specific characteristics of fraud IRM 25.23.4.10.1 , Identity Theft (IDT) with Invalid Returns, an IRSN should be created as a last resort when employees are not able to make a CN determination on one or both returns IRM 25.23.2.6.6.3, Identity Theft Claims Submitted by Individuals Who Do Not Appear to be the Victims Caution: Because an external business data breach return can be identical or similar, also refer to IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, for additional items to review to prevent the mishandling of an actual IDT case. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ For returns with Schedule C income, complete research must be performed. A determination must be made whether the original return can be nullified or if it must be moved to an IRSN. This is regardless of whether the refund was lost, offset or falls under the no lost refund process. To treat a return with Schedule C income as a nullity, there must be a high probability that the Schedule C return was not filed by the TIN owner. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Example: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Example: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ In situations where it cannot be easily determined whether a return with Schedule C income should be treated as a nullity, move the return to an IRSN. Also refer to IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing. If the refund is "not lost" or only partially lost, the lead or manager must review the case and concur with the nullity determination to ensure the return is not nullified in error. Accurate and complete research must be performed, in order to avoid a potential missed assessment. CSR/TE should include a case message of Schedule C determination and suspend to the work leader/manager for approval. Prior to requesting approval, CSR/TE must input a case note with their determination. If a work leader/manager concurs with the findings and the return(s) are nullified, a CII case note will be placed on CII indicating "Manager or Lead concurs with determination" , or similar remarks. Exception: Lead or manager concurrence is not required if research indicates the valid taxpayer does not have a filing requirement and/or the invalid return meets any scheme identified in IRM 25.23.4.8.1, Identity Theft (IDT) Determination - Schemes, and its applicable subsections. In situations where a Schedule C return with a "no lost refund" was treated as a nullity and the taxpayer submits another claim or makes an inquiry about the refund, refer the case to ITVA HQ via secure email. Prepare and email Form 4442 using the subject line: "Schedule C nullity – refund inquiry" to ITVA HQ or similar remarks. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Proceed to IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, for additional processing guidance.

# Identity Theft (IDT) with External Business/Preparer Data Breach Involvement

25.23.4.8.2.4 (06-07-2024) Identity Theft (IDT) with External Business/Preparer Data Breach Involvement You can identify taxpayers known to be impacted by a preparer data breach by a TC 971 AC 123 MISC "PREPARER CONTACT" with no secondary date on CC ENMOD/IMFOLE. The indicator is placed on the accounts of taxpayers whose tax return preparer has notified the Service of compromised PII due to a data breach. Note: A taxpayer may submit a Form 14039, police report, or correspondence indicating their preparer advised them of their personal information potentially being compromised due to a data breach incident. A TC 971 AC 123 MISC "PREPARER CONTACT" may or may not be present in these instances. Conduct research as described below to determine if the taxpayer is impacted by identity theft. Taxpayers are not always aware they are impacted by a data breach. Caution must be used when speaking with the taxpayer to avoid inadvertent disclosure of this account information even after verifying the taxpayer's identity. The external business/preparer is responsible for advising the taxpayer of the incident. Identity theft returns resulting from an external business/preparer data breach may appear to be duplicate or amended returns. These fraudulent returns may include: Duplicate or similar information to previously filed returns. Income information that is consistent with filing history and/or matches IRPTR data. The same or similar tax return preparer information. Different refund/direct deposit information. If it appears the valid taxpayer received a refund related to a fraudulent return filed due to a data breach incident, refer to IRM 25.23.4.8.2.4.1, TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme. The presence of a TC 971 AC 123 MISC "PREPARER CONTACT" on a taxpayer's entity does not confirm identity theft. Complete research must be conducted to verify the taxpayer's claim. Returns determined to be invalid can be resolved following streamline procedures. Account research and the determination must be documented in a CII case note. Use the table below to assist in making Common Number (CN) ownership determinations when an external business/preparer data breach indicator is present. Note: When the taxpayer is reporting income related IDT for any tax year, the presence of a TC 971 AC 123 will not be considered when conducting research. Normal procedures will be followed to make a determination and resolve the account. If And Then (1) Form 14039, police report, or correspondence indicating identity theft is received, there is a TC 971 AC 123 MISC "PREPARER CONTACT" present, The only difference between the posted return and duplicate return is the refund/direct deposit information, Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (7) below. (2) Form 14039, police report, or correspondence indicating identity theft is received, there is a TC 971 AC 123 MISC "PREPARER CONTACT" present, There is no difference between the posted return and duplicate return; this is a true duplicate, When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and refund/direct deposit/balance due information are all consistent with the filing history of the valid taxpayer, or if after researching the account, you cannot find evidence of tax related identity theft, refer to paragraph (6) below. When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and/or refund/direct deposit/balance due information are not consistent with the filing history of the valid taxpayer, there is a high probability the valid taxpayer has not filed a return. Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (7) below. (3) Form 14039, police report, or correspondence indicating identity theft is received, there is a TC 971 AC 123 MISC "PREPARER CONTACT" present, There is only one return present, When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and refund/direct deposit/balance due information are all consistent with the filing history of the valid taxpayer, refer to paragraph (6) below. When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and/or refund/direct deposit/balance due information are not consistent with the filing history of the valid taxpayer, there is a high probability the valid taxpayer has not filed a return. Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (7) below. (4) Form 14039, police report, or correspondence indicating identity theft due to an external business/preparer data breach is received, TC 971 AC 123 MISC "PREPARER CONTACT" is not present, Document your research and determination in a CII case note. Lead/Manager concurrence with the determination must be received and documented in a CII case note prior to taking action on the account. Once concurrence is received, follow procedures in the applicable table scenario (above). Returns filed using information obtained from a preparer data breach have a higher likelihood of being processed as valid returns. When a taxpayer is known to have been affected by a preparer data breach incident but has not yet been impacted by tax related identity theft, the Service will take additional precautions to protect the taxpayer's account. Take the following actions to resolve accounts with the TC 971 AC 123 "PREPARER CONTACT" indicator when an invalid return has not been filed: Input TC 971 AC 506 with MISC "WI AM OTHER" . For the secondary date, use the current filing year or the year of breach, if known. Do Not input a TC 971 AC 504. Issue Letter 4674C. Include paragraphs I, 7, 8, w, y, and #. For international taxpayers, use / in place of #. Caution: If the TC 971 AC 506 is not input prior to cycle 47 of the processing year, an IP PIN/CP01A will not generate for the upcoming filing season. Use the following special paragraphs in addition to the paragraphs above: 9:"Because we processed your claim late in the year, we are unable to mail an IP PIN in December or January for this upcoming filing season. File your return as normal for this tax season. We will mail you an IP PIN next December or January. If your address changes before December, you will need to complete Form 8822, Change of Address. Visit www.IRS.gov." And !:"If you want an IP PIN to use for the upcoming tax year, visit our website at www.irs.gov/your-account. A new IP PIN generates each year in mid-January. You can retrieve it by logging into your account at www.irs.gov/your-account. If you chose to create an account to obtain an IP PIN, you will not receive a notice in December or January as stated above." Follow procedures in IRM 25.23.4.8.2.4.2, External Business/Preparer Data Breach Streamline Identity Theft (IDT) - One Return Present, or IRM 25.23.4.8.2.4.3, External Business/Preparer Data Breach Streamline Identity Theft (IDT) - More Than One Return Present, to correct the account.

# TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme

25.23.4.8.2.4.1 (10-01-2020) TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme The Internal Revenue Service is aware of a scheme where criminals, after stealing client data from tax professionals, file fraudulent tax returns which include the taxpayers' real bank accounts for the refund deposit. When the fraudulent return is processed, the refund is deposited into the real taxpayer's account. The criminal subsequently contacts the taxpayer requesting/demanding the funds be returned and gives instructions telling the taxpayer how to return the funds. Accounts that have been identified by IRS as being part of the scheme will show a "TC 971 AC 123 – MISC CODE: TPP RECOVERY" or will contain an open control as shown in (3) below. If you receive a call from a taxpayer who meets the scheme criteria (taxpayer can self-identify) and needs to return the fraudulent tax refund take the following actions: Identify the tax period the refund was issued (e.g., TY 2017) Review the account for the following TC 971 marker or control base. Accounts already identified as part of the scheme will have: •TC 971 AC 123 - MISC Code: TPP Recovery • Open control on TXMOD assigned to 1487388888 with the activity RECOVERY and a category MISC If the account has no marker and no open control, open a control base on CC TXMOD with the following information: •ACTON •C#, RECOVERY, M, MISC •1487388888,* Note: The open control will result in RICS creating a TC 971 AC 123 marker, via a batch process and will ensure the account is worked through the TPP process. Exception: If there is an existing "RECOVERY MISC" control or if the account already has the TC 971 AC 123 - MISC TPP RECOVERY marker, DO NOT open a control. Provide instructions to the taxpayer on how to return the refund to the IRS. If Then (1) The refund remains in the taxpayer's bank account (not transferred or withdrawn). Follow instructions in IRM 21.4.5.12(6), How to Repay an Erroneous Refund or Return an Erroneous Refund Check or Direct Deposit, to advise taxpayer how to submit an IDT claim and repay the refund. Warn the taxpayer that the criminal who filed the return may contact them by phone or email to request transfer of the refund. The criminal may claim to work at the IRS or for a collection agency hired by the IRS. (2) The refund was withdrawn from the taxpayer's account using Treasury Direct. The withdrawal can be identified on the taxpayer's statement as Treasury Direct followed by an account number that starts with a letter followed by 9 numbers (e.g., Z123456789). Explain that Treasury Direct and IRS are not the same agency. Advise the taxpayer to contact the Treasury Direct - Customer Service at 1-844-284-2676 to discuss reimbursement/recovery of funds, or ask their bank to contact Treasury Direct. Follow instructions in IRM 21.4.5.12(6), How to Repay an Erroneous Refund or Return an Erroneous Refund Check or Direct Deposit, to advise taxpayer how to submit an IDT claim and repay the refund when Treasury Direct has reimbursed or recovered the funds. (3) The taxpayer transferred the refund amount to the criminal, mistakenly believing they were repaying the refund to the IRS. Ask the taxpayer to complete Form 14039, Identity Theft Affidavit, and attach a copy of a bank statement or document showing the transfer. The Form 14039 should also include any description or documentation of the criminal's phone call/email that the taxpayer can provide. If taxpayer needs to file their tax return, advise them to follow the steps outlined in the Taxpayer Guide to Identity Theft. Taxpayers unable to file electronically should mail a paper return along with Form 14039, Identity Theft Affidavit, stating they were victims of a tax return preparer data breach. If the taxpayer transferred the refund amount to the criminal, mistakenly believing they were repaying the refund to the IRS, and provides the written documentation described in (4) above, treat the refund as a lost refund. Take the following action: If Then (1) The taxpayer did not file a return. Follow the lost refund procedures in paragraph (2) of IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, to correct the taxpayer's account. Email a copy of the taxpayer's documentation (or the CII number if the documentation is on CII) to ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. (2) The taxpayer did file a return. Follow the procedures in IRM 25.23.4.10.1 , Identity Theft (IDT) with Invalid Returns. Email a copy of the taxpayer's documentation (or CII number if the documentation is on CII) to ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If the taxpayer says they transferred the refund amount to the criminal, mistakenly believing they were repaying the refund to the IRS, but does not provide the written documentation described in (4) above, the refund will be treated as if the taxpayer had full access and use of it. Take the following action: If Then (1) The taxpayer did not file a return, Follow the "no lost" refund procedures in paragraph (2) of IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, to correct the taxpayer's account. Follow the procedures in IRM 21.4.5.6.1, Account Actions For Category D Erroneous Refunds, to request repayment of the refund. (2) The taxpayer did file a return, Follow the procedures in IRM 25.23.4.10.1 Identity Theft (IDT) with Invalid Returns, to correct the taxpayer's account. If the refund issued on the IDT return is greater that the refund on the taxpayer's return, follow the procedures in IRM 21.4.5.6.1, Account Actions For Category D Erroneous Refunds, to request repayment of the difference.

# External Business/Preparer Data Breach Streamline Identity Theft (IDT) - One Return Present

25.23.4.8.2.4.2 (10-01-2020) External Business/Preparer Data Breach Streamline Identity Theft (IDT) - One Return Present Consider the case to meet One Return IDT when any of the following account conditions exist. Take the necessary actions to resolve the account as described. Reminder: If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. If And Then (1) Only one return meeting nullity criteria has posted (TC 150): For the year in question, the taxpayer: Was not of age to work, Is deceased, Does not have a filing requirement, or Has not yet filed a return. Ensure CII case notes include your research, determination, and lead/managerial approval to nullify the invalid return. Update the taxpayer's entity information to reflect the CN owner's name, current address, and phone number, if provided. Input an adjustment to fully back out the return. Use BS 05 and RC 139. Use HC 3 if the adjustment will not result in a credit remaining on the module. Use HC 4 to prevent a refund of any remaining credits, when necessary. Input TC 971 AC 850 when the invalid return includes direct deposit information. If the valid taxpayer received the refund from the invalid return, see IRM 25.23.4.8.2.4.1, TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme. If any portion of the refund is lost, see IRM 25.25.4.7, Reversing Identity Theft Lost Refunds. Input TC 971 AC 501/506, as appropriate. Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, to determine if the taxpayer has a filing requirement, and take appropriate actions. Refer to Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional account actions that may be required. (2) Only one return filed by the valid taxpayer has posted (TC 150): A second, unprocessed return meeting nullity criteria has been received. Input TC 290 .00 with BS 05 and RC 139. Use HC 3 if the adjustment will not result in a credit remaining on the module. Use HC 4 to prevent a refund of any remaining credits, when necessary. Input TC 971 AC 501/506, as appropriate. Refer to Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional account actions that may be required.

# External Business/Preparer Data Breach Streamline Identity Theft (IDT) - More Than One Return Present

25.23.4.8.2.4.3 (10-01-2020) External Business/Preparer Data Breach Streamline Identity Theft (IDT) - More Than One Return Present Follow the procedures below when multiple returns are present. Reminder: If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. Reminder: Statute year returns require additional research prior to taking action on an account. Review IRM 25.23.4.9, Statute Processing Considerations, to ensure all applicable statutes are protected. If And Then (1) Multiple invalid returns are present, For the year in question, the taxpayer: Was not of age to work, Is deceased, Does not have a filing requirement, or Has not yet filed a return. Ensure CII case notes include your research, determination, and lead/managerial approval to nullify the invalid returns. Update the taxpayer's entity information to reflect the CN owner's name, current address, and phone number, if provided. Input TC 971 AC 850 when the invalid return includes direct deposit information. Input an adjustment to fully back out the return(s). Use BS 05 and RC 139. Use HC 3 if the adjustment will not result in a credit remaining on the module. Use HC 4 to prevent a refund of any remaining credits, when necessary. If the valid taxpayer received the refund from the invalid return, see IRM 25.23.4.8.2.4.1, TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme. If any portion of the refund is lost, see IRM 25.25.4.7, Reversing Identity Theft Lost Refunds. Input TC 971 AC 501/506, as appropriate. Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, to determine if the taxpayer has a filing requirement, and take appropriate actions. Refer to Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional account actions that may be required. (2) The valid taxpayer's return has posted as the TC 150, At least one invalid return meeting nullity criteria has been received. Ensure CII case notes include your research, determination, and lead/managerial approval to nullify the invalid return(s). Input TC 290 .00 with BS 05 and RC 139. Use HC 3 if the adjustment will not result in a credit remaining on the module. Use HC 4 to prevent a refund of any remaining credits, when necessary. Input TC 971 AC 501/506, as appropriate. Refer to Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional account actions that may be required. (3) An invalid return has posted as the TC 150, The valid taxpayer's return has been received. Note: This scenario will be followed when more than one invalid return is received, the valid taxpayer has filed a return, and the TC 150 has been determined to be invalid. Ensure CII case notes include your research, determination, and lead/managerial approval to nullify the invalid return(s). Update the taxpayer's entity information to reflect the CN owner's name, current address, and phone number, if provided. If the valid taxpayer's return does not have a posted TC 976, see IRM 25.23.4.6.5.2, Unprocessed Documents, for applicable procedures. Input TC 971 AC 850 when the invalid return includes direct deposit information. Input an adjustment to the valid return figures, as allowable. Use BS 00 and RC 139. Use HC 3 or HC 4 when a credit remaining on the module must be held. If the valid taxpayer received the refund from the invalid return, see IRM 25.23.4.8.2.4.1, TIN Owners Receiving Fraudulent Refunds in Preparer Data Breach Scheme. If any portion of the refund is lost, see IRM 25.25.4.7, Reversing Identity Theft Lost Refunds. Input TC 971 AC 501/506, as appropriate. Refer to Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing, for additional account actions that may be required.

# Identity Theft (IDT) with Tax Preparation Software Misuse

25.23.4.8.2.5 (11-06-2024) Identity Theft (IDT) with Tax Preparation Software Misuse You can identify taxpayers known to be impacted by tax preparation software misuse by a TC 971 AC 123 with specific MISC fields on CC ENMOD/IMFOLE. An indicator is placed on the accounts of taxpayers when the Service is notified of compromised PII due to tax preparation software misuse. Refer to the following list of the MISC fields for incidents that have been reported to the Service. "TTAX LIST" - Intuit/TurboTax has reported an attempt to misuse the taxpayer's PII. Caution: This indicator is only used to mark accounts that have the potential to be impacted by tax related identity theft. Thorough research must be conducted to make a determination prior to taking any actions on the account. Note: A taxpayer may submit a Form 14039, police report, or correspondence indicating their tax preparation software company advised them of their personal information being compromised. A TC 971 AC 123 with a MISC field listed above may or may not be present in these instances. Conduct research as described below to determine if the taxpayer is impacted by identity theft. Taxpayers are not always aware their PII was used to create a new account or attempt to file a tax return with the tax preparation software they have used in the past. Caution must be used when speaking with the taxpayer to avoid inadvertent disclosure of this account information even after verifying the taxpayer's identity. The tax preparation software company is responsible for advising the taxpayer of the incident. Identity theft returns resulting from tax preparation software misuse may appear to be duplicate or amended returns. These fraudulent returns may include: Duplicate or similar information to previously filed returns. Income information that is consistent with filing history and/or matches IRPTR data. The same or similar tax return preparer information. Different refund/direct deposit information. The presence of a TC 971 AC 123 with a MISC field listed in paragraph (1) above on a taxpayer's entity does not confirm identity theft. Complete research must be conducted to verify the taxpayer's claim. Returns determined to be invalid can be resolved following streamline procedures. Use the table below to assist in making Common Number (CN) ownership determinations when misuse of tax preparation software is suspected. Note: When the taxpayer is reporting income related IDT for any tax year, the presence of a TC 971 AC 123 will not be considered when conducting research. Normal procedures will be followed to make a determination and resolve the account. If And Then (1) Form 14039, police report, or correspondence reporting identity theft is received, there is a TC 971 AC 123 MISC field indicating misuse of tax preparation software present, The only difference between the posted return and duplicate return is the refund/direct deposit information, Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (6) below. (2) Form 14039, police report, or correspondence reporting identity theft is received, there is a TC 971 AC 123 MISC field indicating misuse of tax preparation software present, There is no difference between the posted return and duplicate return; this is a true duplicate, When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and refund/direct deposit/balance due information are all consistent with the filing history of the valid taxpayer, or if after researching the account, you cannot find evidence of tax related identity theft, refer to paragraph (5) below. When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and/or refund/direct deposit/balance due information are not consistent with the filing history of the valid taxpayer, there is a high probability the valid taxpayer has not filed a return. Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (6) below. (3) Form 14039, police report, or correspondence reporting identity theft is received, there is a TC 971 AC 123 MISC field indicating misuse of tax preparation software present, There is only one return present, When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and refund/direct deposit/balance due information are all consistent with the filing history of the valid taxpayer, refer to paragraph (5) below. When the name/address, dependents, income/credits, tax preparer/3rd party contact authorization, and/or refund/direct deposit/balance due information are not consistent with the filing history of the valid taxpayer, there is a high probability the valid taxpayer has not filed a return. Consider the taxpayer submitting the identity theft claim to be the valid taxpayer. Refer to paragraph (6) below. (4) Form 14039, police report, or correspondence reporting identity theft is received, there is a TC 971 AC 123 MISC field indicating misuse of tax preparation software present, The are multiple differences between the posted return and duplicate return, Follow normal procedures to make an identity theft CN ownership determination without consideration of the TC 971 AC 123 present. (5) Form 14039, police report, or correspondence indicating identity theft due to tax preparation software misuse is received, TC 971 AC 123 MISC "PREPARER CONTACT" is not present, Document your research and determination in a CII case note. Lead/Manager concurrence with the determination must be received and documented in a CII case note prior to taking action on the account. Tax related: Follow the applicable streamline procedures to resolve the case. See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. Note: If a NOIDT determination is made, see below. Non-Tax-Related: Follow the applicable procedures in IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4 Overview, to resolve the case. When a taxpayer is known to have been affected by misuse of tax preparation software but has not yet been impacted by tax related identity theft (i.e., invalid return received), the Service will take additional precautions to protect the taxpayer's account. Take the following actions to resolve accounts identified by a TC 971 AC 123 with a MISC field listed in paragraph (1) above when an invalid return has not been filed: Update the CII Category Code to IDT4. Refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4 Overview. Input TC 971 AC 504 with MISC NKI-M. Issue Letter 4402C. Include two selectable open paragraph selections. Use the following special paragraphs: "We received your identity theft claim regarding the fraudulent account and possible fraudulent filing of a tax return by your private tax program. We have processed your claim and placed an indicator on your account. We don't need any additional information from you." AND "We highly recommend obtaining an Identity Protection Personal Identification Number (IP PIN) to protect your account. Additional information can be found below." Reminder: Do not include the quotation marks when using the special paragraphs provided above. When you have determined the taxpayer is a victim of tax related identity theft (i.e., invalid return received) as a result of tax preparation software misuse, follow the applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, depending on the facts and circumstances of your case.

# Non-Streamline Identity Theft (IDT) Determinations

25.23.4.8.3 (10-12-2023) Non-Streamline Identity Theft (IDT) Determinations When refund related identity theft (IDT) is suspected, the return in question must first be reviewed to determine if it meets streamline criteria, per IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing. When the return in question does not meet streamline criteria, refer to the applicable scenario below: Form 14039 or police report was received: IRM 25.23.4.8.3.1, Taxpayer Identified Identity Theft (IDT) Determinations IRS Identified: IRS Identified Identity Theft (IDT) Determinations: IRM 25.23.4.8.3.2, IRS Identified Identity Theft (IDT) Determinations

# Taxpayer Identified Identity Theft (IDT) Determinations

25.23.4.8.3.1 (06-07-2024) Taxpayer Identified Identity Theft (IDT) Determinations Follow the procedures below when a Form 14039 or police report has been received, there is only one return on the module, and the reporting taxpayer is stating they did not file the return in question. Ensure all required research has been completed prior to making a determination of Common Number (CN) ownership. See IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and its subsections for detailed instructions. Document your research and determination in a CII case note. If And Then (1) A Form 14039, police report, or correspondence has been received, The claim and posted return contain different addresses, If supported by your research, treat the identity theft inquiry as belonging to the valid taxpayer. If your research does not support determining in favor of the taxpayer who submitted the inquiry, correspond with both taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (2) A Form 14039, police report, or correspondence has been received and the return on file also includes an IDT claim, The claim and posted return contain different addresses, Correspond with both taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (3) A Form 14039, police report, or correspondence has been received, The claim and posted return contain the same address, If supported by your research, treat the identity theft inquiry as belonging to the valid taxpayer. If your research does not support a determination of identity theft, see IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (4) A Form 14039, police report, or correspondence has been received and the return on file also includes an IDT claim, The claim and posted return contain the same address, Correspond to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. Follow the procedures below when a Form 14039 or police report has been received, there are multiple returns, and the reporting taxpayer is stating they did not file the return in question. Ensure all required research has been completed prior to making a determination of CN ownership. See IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and its subsections for detailed instructions. If And Then (1) A Form 14039, police report, or correspondence is included with only one return, The returns contain different addresses, If supported by your research, treat the identity theft inquiry as belonging to the valid taxpayer. If your research does not support determining in favor of the taxpayer who submitted the inquiry, correspond with both taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (2) A Form 14039, police report, or correspondence is included with only one return, The returns contain the same address, If supported by your research, treat the identity theft inquiry as belonging to the valid taxpayer. If your research does not support a determination of identity theft, see IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (3) A Form 14039, police report, or correspondence is included with multiple returns, The returns contain the same address, Correspond to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (4) A Form 14039, police report, or correspondence is received separate from any return, and Multiple returns have been filed under the common number, None of the returns contain the same address as the current or previous address provided on the identity theft inquiry, If supported by your research, treat the identity theft inquiry as belonging to the valid taxpayer. If your research does not support determining in favor of the taxpayer who submitted the inquiry, correspond with all taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (5) A Form 14039, police report, or correspondence is received separate from any return, and Multiple returns have been filed under the common number, At least one (but not all) of the returns contains the same address as the current or previous address provided on the identity theft inquiry, Note: If all returns contain the same address as the current or previous address provided on the identity theft inquiry, continue to table scenario (6) below. If supported by your research, treat the identity theft inquiry and return(s) containing the same address as belonging to the valid taxpayer. If your research does not support determining in favor of the taxpayer who submitted the inquiry, correspond with all taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (6) A Form 14039, police report, or correspondence is received separate from any return, and Multiple returns have been filed under the common number, All of the returns contain the same address as the current or previous address provided on the identity theft inquiry, Correspond with all taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed. (7) More than one Form 14039, police report, or correspondence indicating an identity theft issue under the same TIN have been received, The reporting taxpayers have different addresses, Research the case as a possible Scrambled SSN. See IRM 25.23.4.6.1, Required Research, for additional information. Correspond with all taxpayers to secure necessary documentation to make a determination. Refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Include the questionnaire. Refer to IRM 25.23.4.18.2.3, Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions Sent to Determine Common Number Ownership, and IRM 25.23.4.18.2.4, Final Stage Review (Associated with Letter 5064C Sent for Common Number Ownership), when the suspense timeframe has passed.

# IRS Identified Identity Theft (IDT) Determinations

25.23.4.8.3.2 (06-07-2024) IRS Identified Identity Theft (IDT) Determinations Follow the procedures below when a Form 14039 or police report has not been received and identity theft is suspected. Ensure all required research has been completed prior to making a determination of Common Number (CN) ownership. See IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and its subsections for detailed instructions. If And Then (1) Identity theft is suspected, and a claim has not been received (IRSID), All of the following conditions are met: This is the first time one of the taxpayers has used the CN AND the other taxpayer has used the CN for more than one year. The filing history is appropriate for the DOB associated with the CN. Consider the taxpayer who has used the CN for more than one year to be the valid taxpayer. Add a CII case note documenting your research and stating "1st Year Rule" to identify the scenario used to make the determination. (2) Identity theft is suspected, and a claim has not been received (IRSID), All of the following conditions are met: One of the taxpayers has used the CN for 3 or more years AND the other taxpayer has used the CN for less than 3 years. The filing history is appropriate for the DOB associated with the CN. Consider the taxpayer who has used the CN for 3 or more years to be the valid taxpayer. Add a CII case note documenting your research and stating "3 Year Rule" to identify the scenario used to make the determination. (3) Identity theft is suspected, and a claim has not been received (IRSID), All of the following conditions are met: Complete and careful research provides reasonable evidence of CN ownership. A CN ownership determination cannot be made using scenario (1) or (2). Leave a CII case note documenting all research completed, including the evidence that supports your determinations. Refer the case for managerial/lead concurrence with the determination made. A CII case note documenting concurrence with the determination must be input prior to taking action to resolve the account. (4) Identity theft is suspected, and a claim has not been received (IRSID), All of the following conditions are met: Complete and careful research does not result in reasonable evidence of CN ownership. A CN ownership determination cannot be made using scenarios (1), (2), or (3). Your research does not support a determination of identity theft. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations

# Dependent Related Identity Theft (IDT) - General

25.23.4.8.4 (10-01-2025) Dependent Related Identity Theft (IDT) - General Dependent related identity theft (IDT) claims are received when misuse of a dependent's TIN is suspected. Refer to the list below for examples of tax related dependent IDT scenarios: A taxpayer's dependent is listed as a primary taxpayer, secondary taxpayer, or dependent on an invalid return. An individual is listed as a dependent on the return of a taxpayer who is not their parent/legal guardian (whose identity may or may not be known by the reporting person). A taxpayer is not a dependent of anyone but is listed as a dependent on a return filed by an individual they do not know or an individual (who is not their parent/legal guardian) they do know who does so without their knowledge or consent. Do not reject an incomplete Form 14039. An individual may report dependent related IDT for themselves or on behalf of another individual using Form 14039, a police report, or correspondence. Refer to the table below for additional information: Who filed the Dependent IDT Claim? Overview Parent/legal guardian on behalf of their dependent. Note: Form 14039, Section F, is designated to provide information in these instances. A parent/legal guardian relationship must be researched prior to taking any action taken on an account and verified before providing information to the reporting person. Note: When a Form 14039 is signed by a parent on behalf of their dependent child (under age 18), and the parental relationship can be verified through internal research, documentary evidence is not required to be submitted. Proof of legal guardianship of an adult dependent (age 18 or older as of the signature date) is required. Proof of relationship alone is not sufficient for these cases. Follow procedures in IRM 25.23.4.8.4.2, Dependent Related Identity Theft (IDT) – Non-Streamline Research. When the parent/legal guardian relationship cannot be confirmed, the reporting person will be treated as an unauthorized third party. Reminder: If there is an identity theft issue and the parent/legal guardianship cannot be confirmed, the identity theft issue may still be resolved. Example: An unauthorized third party submitted Form 14039 on behalf of an individual listed as the primary taxpayer on a return determined to be invalid per IRPTR Data Decision Tree criteria. The identity theft issue will be resolved following streamline procedures. Example: An unauthorized third party submitted Form 14039 on behalf of an individual listed as the secondary taxpayer on a return determined to meet Married Filing Joint Scheme criteria. The identity theft issue will be resolved following streamline procedures. Individual taxpayer reporting dependent IDT for themselves. Consider these claims when the individual is self-reporting IDT and at least age 16 as of the signature date on the claim. Note: If the claim is not signed, use the postmark date on the envelope. If neither is present, use the IRS received date for purposes of considering the claimant's age at the time of filing the claim. Dependent IDT claims may mention additional account issues that need to be addressed. Read the table below for some examples: Note: This table is not all inclusive. If Then (1) Claim includes a statement regarding non-receipt of the Economic Impact Payment (EIP) or Recovery Rebate Credit (RRC): Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) – General, and the related subsections after deciding to respond to the inquiry. (2) Claim includes a statement regarding non-receipt of Advanced Child Tax Credit (AdvCTC): Refer to IRM 25.23.4.21.2, Advanced Child Tax Credit (AdvCTC) – General. Through the course of research, additional impacted individuals and/or tax years may be identified. There should be a clear path of research leading to the identification. Refer to the table below for examples: Note: This table is not all inclusive. Caution: IDTVA employees are not to research preparer information on a return to identify other tax returns they have filed on behalf of other clients to determine if there are additional potential victims of identity theft. How was the related case identified? Example (1) Complete Case Analysis (CCA) identified additional impacted tax years. A 20-year-old taxpayer self identifies as a victim of dependent related identity theft. Form 14039 includes a statement indicating they are not a dependent of anyone and have not been since they turned age 18. Tax year 2023 is the only year listed on the claim. Research of CC DDBKD indicates they were claimed by the same unknown individual for tax years 2023 and 2022. You have identified 2022 as an additional impacted tax year. Reminder: Each impacted tax year must have a separate CII case. See IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. (2) Form 14039 submitted for multiple individuals or including a general statement. A parent files Form 14039 for themselves explaining they couldn't e-file and had to mail in their tax return because someone claimed their child, but they don't know which one. Research determines the parent's valid return claims three dependents. A review of each dependent reveals the verified parent and an unknown individual are claiming all three dependents. You have now determined there are three individuals impacted by IDT. Reminder: Each impacted individual must have a separate CII case. See IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. (3) CCA identified additional victims on an invalid tax return. Form 14039 is submitted stating they are not a dependent of anyone. Research shows they were claimed as a dependent on a tax return that is determined to be invalid per IRPTR/IDRS data. All dependents on this invalid return are victims and must be addressed. Note: Additional victims may or may not have a familial relationship. Reminder: Each impacted individual must have a separate CII case. See IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. Dependent related IDT may be IRS identified when misuse of a TIN occurs on a tax return determined to be invalid. Each dependent on the invalid tax return must be addressed. When performing research for dependent related identity theft claims, employees will not determine the following: Which parent/legal guardian is entitled to claim and/or represent the dependent. Whether the person claiming the dependent is eligible for dependency or dependent-related credits included on a valid tax return. Note: It is possible for misuse of a dependent's TIN to occur on a valid tax return. Modules where this occurs will not be adjusted to remove the dependent or dependent related credits. This will not prevent resolution of the dependent's IDT issue. Case assignment for dependent related IDT will follow the below guidance: Assign dependent related IDT cases under the dependent's TIN. See IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. Create a separate case for each individual for whom a claim is received and/or any impacted individual located through research completed based on a general statement. This may be identified by multiple TINs provided on a single claim or a statement describing the identity theft issue which results in recognition of multiple impacted individuals through the course of research. Example: A mother files a Form 14039 explaining her e-file was rejected because someone else claimed her children. Account research identifies the taxpayer usually claims two dependents. Both dependents are victims of dependent related IDT. Two separate cases are created, one for each dependent. Create a separate case for each individual meeting IRS identified dependent IDT as described in paragraph (6) above. Create a separate case for each impacted tax year. Example: The confirmed custodial parent explains their e-file was rejected. The rejection code indicated their daughter's TIN was previously used on another filed tax return for the same year, 2023. Research of the dependent's TIN identifies the daughter's TIN was also used on a 2022 return that was previously confirmed as IDT and moved to MFT32. In addition to the 2023 case, a case for 2022 will be created. Dependent related IDT cases will only be referred to IDTVA Specialty Functions when the claim is also related to a Compliance assessment made. Refer to Exhibit 25.23.4-5, ITVA Routing Matrix, for additional information regarding roles and responsibilities within IDTVA. Case notes must clearly indicate the determination being made. Notes should provide sufficient details of the research path leading to identification of additional impacted individuals, when applicable. It is appropriate to notate a case ID, when available. Refer to IRM 25.23.2.3.4, Required Case and History Notes, for additional information on required case documentation. Entity establishment may be necessary for dependent related IDT claims. If parent/legal guardianship is in question, do not establish or update the dependent's entity with the reporting person's address or telephone number until acceptable documentation is provided. When establishing or updating the entity of the dependent, refer to IRM 3.13.5.117, Establishing a New Account (TC 000), and Exhibit 25.23.4-22, Establishing or Updating Entities for Dependents. In addition to the guidance provided in these references, additional actions may be necessary when establishing or updating the entity. Do not include the word "minor" unless the correspondence includes the word "minor" in the Form 14039 Section B explanation or correspondence from the taxpayer. Note: The dependent's age will not be used to identify them as a "minor" due to extenuating circumstances which may exist. Do not include the reporting person's information in the "Continuation of Primary Name" field. Include the telephone number from the case documents when establishing or updating the entity when it has been determined the correspondence was submitted by or on behalf of the dependent (not an unauthorized third party). See IRM 25.23.2.3.7, When to Update the Victim's Address, for additional information. Dependent related IDT requires the use of specific account indicators. The chart below provides further information on closing codes that may be necessary. Account Indicator Explanation TC 971 AC 528 MISC Field Code: "WI IP DEPND" Secondary Date: January 1st of the current calendar year to signify the processing year Input after a tax-related identity theft issue is identified for a dependent to enroll individuals into the IP PIN program. Note: Additional tax-related IDT indicators are necessary to protect the account (i.e., 501 or 506). Note: If a new identity theft issue occurs after a previous case was resolved, the input of an additional TC 971 AC 528 will be necessary if the new case is not being resolved in the same processing calendar year. TC 971 AC 501 Input upon resolution of a taxpayer identified IDT issue affecting tax administration. See IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501, for more information. TC 971 AC 506 Input upon resolution of an IRS identified IDT issue affecting tax administration. See IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for more information. TC 971 AC 504 Input upon resolution of an IDT issue that has no impact to tax administration. See IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, for more information. Example: The dependent's TIN was used to get a credit card or ID and there were no tax related account issues. Follow the guidance below when issuing correspondence for dependent related identity theft. Use caution to ensure you do not inadvertently provide tax account information to an unauthorized individual. All required correspondence will be issued under the dependent's TIN. This includes sending correspondence to the individual submitting an identity theft claim on behalf of their dependent. Correspondence will be addressed to the dependent and their representative if there is information in the Continuation of Primary Name (i.e., POA, etc.). Separate correspondence will be sent to everyone for whom a claim is received and for each IRS identified individual. Caution: For individuals under the age of 18, Letter 4674C must be sent. Do not include the paragraph that directs them to request an IP PIN using Online Services. See IRM 25.23.2.9.1.2, Opting into the IP PIN Program through the Individual Online Account, for additional information. Taxpayers can be directed to irs.gov.ippin and/or irs.gov.ippinfaqs to obtain general information. Example: The taxpayer files a Form 14039 for themselves explaining someone filed a tax return under their TIN. Research determines an invalid HOH return with one dependent was moved to MFT32. The dependent is the taxpayer's dependent based on a 3-year look back. All necessary actions are taken to resolve the taxpayer and dependent's account. One closing letter will be sent to the taxpayer, and one closing letter will be sent to the dependent. When a TC 971 AC 501/506 will not be input, advise the individual they may be able to obtain an IP PIN through the opt in process to protect their identity in the future. Caution: For individuals under the age of 18, Letter 4674C must be sent. Do not include the paragraph that directs them to request an IP PIN using Online Services. See IRM 25.23.2.9.1.2, Opting into the IP PIN Program through the Individual Online Account, for additional information. Taxpayers can be directed to irs.gov.ippin and/or irs.gov.ippinfaqs to obtain general information.

# Dependent Related Identity Theft (IDT) - Streamline Determinations

25.23.4.8.4.1 (10-01-2025) Dependent Related Identity Theft (IDT) - Streamline Determinations The following streamline determination procedures will apply to only the current and two (2) immediately preceding tax years. Prior to making a streamline determination, conduct basic research. IDRS CC DDBKD: Used to confirm the parent/legal guardian relationship through internal research and identify the TIN(s) claiming the dependent by tax year. Caution: CC DDBKD only lists the primary TIN on the tax return listing the dependent. When that TIN is not confirmed as the parent/legal guardian, it is appropriate to research the account information to determine if the return includes a secondary taxpayer who can be confirmed as the parent/legal guardian. ITIN RTS: Used to research the ITIN application to confirm the parent/legal guardian relationship. When the parent/legal guardian relationship cannot be easily confirmed using information provided and internal research, a streamline determination will not be made. Refer to the table below for case scenarios meeting streamline determination criteria: Note: All scenarios below, except scenario (7), assume the parent/legal guardian relationship has been confirmed for cases where the dependent is under age 18 as of the signature date. If And Then (1) The Form 14039, police report, or correspondence indicates the individual was claimed by someone else. Research shows the individual was claimed by a parent/legal guardian. The individual is not a victim of identity theft. Follow procedures in IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (7). (2) The Form 14039, police report, or correspondence indicates the individual was claimed by someone else. Research shows the individual was not claimed by anyone (including themselves). See IRM 25.23.4.8.4.2, Dependent Related Identity Theft (IDT) – Non-Streamline Research, paragraph (6) table scenario (4). (3) The Form 14039, police report, or correspondence indicates the individual was claimed by someone else. Research shows they were claimed by someone who is not a parent/legal guardian. The individual is a victim of identity theft. See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (9). (4) The Form 14039, police report, or correspondence indicates the individual was claimed by someone else. Research shows they were listed as the primary or secondary taxpayer on a Married Filing Joint (MFJ) return. Refer to IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (6). (5) The TIN is listed on a questionable return. The return is determined to be invalid. The individual is a victim of identity theft. See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (9). If a claim has not been received for this individual, this is an IRS identified dependent related IDT case. (6) The Form 14039, police report, or correspondence indicates the loss of personally identifiable information (PII) or an individual's TIN was used to obtain a credit card, identification, loan, etc. Research shows there is no impact to tax administration. This is a non-tax-related IDT issue. See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (1). (7) The Form 14039, police report, or correspondence indicates the individual was claimed by someone else. The individual is self-reporting and under age 16. The claim will not be considered. Send a closing Letter 916C to the address provided on the claim. Include paragraphs: F, T, and 1. In paragraph T, explain that a signed statement from their parent or legal guardian must be received before we can consider their identity theft claim. Cases not meeting the scenarios above or requiring significant research must be thoroughly reviewed to make an identity theft determination. Follow procedures in IRM 25.23.4.8.4.2, Dependent Related Identity Theft (IDT) – Non-Streamline Research, to conduct necessary research related to suspected dependent IDT.

# Dependent Related Identity Theft (IDT) – Non-Streamline Research

25.23.4.8.4.2 (06-05-2025) Dependent Related Identity Theft (IDT) – Non-Streamline Research When a dependent related streamline determination cannot be made, the account must be thoroughly researched to verify the relationship of the reporting person and correctly identify the account issue. Do not assume the individual is a victim of identity theft. For parent/legal guardianship considerations, refer to the table below prior to completing account research. If Then (1) If parent/legal guardianship cannot be confirmed using the information provided and internal research, third party authority is in question, Request proof of the relationship/legal guardianship (i.e., court order, adoption certificate, or other legal documentation). See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Do not establish or update the dependent's entity with the reporting person's address or telephone number until acceptable documentation is provided. (2) If the claim was submitted on behalf of an adult dependent (age 18 or older as of the signature date), verification of the relationship alone is not sufficient, Request proof of the relationship/legal guardianship (i.e., court order). See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). (3) If a response to the request is received, Refer to paragraph (3) below to determine if it is acceptable. (4) The suspense timeframe has passed and a response to the request was not received, Refer to paragraph (4) below to determine if it is acceptable. When proof of relationship and/or legal guardianship has been requested, and the taxpayer submits information in response, refer to the table below: Acceptable Documentation Unacceptable Documentation Court Order Written statement from parent (even if notarized) Birth Certificate Adoption Documentation Form 8332, Release/Revocation of Release of Claim to Exemption for Child by Custodial Parent Foster Care Placement Documentation Note: Refer questionable foster care placement documentation to ITVA HQ as described in the note below. School records Proof of medical insurance Note: For any documentation provided that is not listed in the table above, prepare and email Form 4442 using the subject line: Dependent - Proof of Guardianship (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. After determining if the documentation is acceptable or unacceptable, refer to the table below: If Then (1) The documentation received is acceptable, Make a determination, and resolve the case following applicable procedures. (2) The documentation submitted as proof of relationship/legal guardianship (under 18) received is unacceptable, OR The documentation submitted as proof of legal guardianship (adult dependent over 18) is unacceptable, OR The suspense timeframe was expired and a response was not received, Issue a closing letter to the reporting person following procedures for corresponding with a person who is not an authorized third party. Do not include a paragraph requesting a Form 2848, Power of Attorney and Declaration of Representative, or Form 8821, Tax Information Authorization. If there is enough information, make a determination and resolve the case following applicable procedures. When a valid separate address can be found for the dependent, the reporting person and dependent will each receive a separate letter. For additional letter requirements, see IRM 25.23.4.18.1, General IDTVA Letter Procedures. Dependent related IDT may lead to the discovery of additional impacted individuals. Exercise caution when determining if any individual included on the tax return (primary, secondary, or dependent) is a victim of identity theft. It is possible for identity theft and misuse of the TIN to both exist from the same filing. Refer to the table below to assist with making this determination. Scenario Description (1) Identity Theft All individuals included on the tax return in question will be considered impacted by identity theft when the tax return can be determined to be invalid (IDT). If an IDT claim has not been received, it will be an IRS identified case. The invalid tax return will be addressed as part of resolving the identity theft issue for the primary and/or secondary taxpayer(s) in this instance. (2) Misuse of a TIN When the tax return in question cannot be determined to be invalid (i.e., verifiable income, consistent with the filing history), an individual cannot be IRS identified as a victim of dependent related IDT. Only individuals an IDT claim has been received for will be considered potential victims. The account of the tax return listing the dependent(s) will not be adjusted to remove the victim(s) and/or dependent-related credits. Reminder: IDTVA employees are not making a determination regarding which parent/legal guardian is entitled to claim and/or represent the dependent. IDTVA employees are not confirming if the person claiming the dependent is eligible for dependency or dependent-related credits included on a tax return not determined to be IDT. Conduct a review of prior years (a minimum of three prior years, if available) and all subsequent years. The prior year review will continue in one-year increments until no indications of dependent TIN use are found. Refer to the table below for research paths appropriate for the facts and circumstances of the case. After completing the required research, continue to IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) - Determinations, to make a determination. Note: Use of the TIN-Related Worksheet may be beneficial for identifying any consistencies and/or inconsistencies in the filing history. Note: There are various IAT tools available to aid in completing the research described in the table below. Caution: For purposes of research only, the asserted victim of identity theft will be referred to as the "victim" in the table below, and the asserted thief will be referred to as the "individual in question" . The validity of the claim will be determined after completion of all necessary research. If Then (1) The reporting person provides the TIN of the individual they believe committed identity theft, Research the TIN of the individual in question. Use any combination of the following systems and/or IDRS Command Codes (CC) to review the filing history: MeFile ITIN RTS CII AMS TRDBV RTVUE DDBKD/DDBKDN Note: Your research is not limited to use of the systems and Command Codes listed above and may extend to other resources available, as applicable. While reviewing the filing history, consider the following: Was the victim claimed as a dependent for the tax year in question? How many years has the victim been claimed as a dependent of the individual in question? What is the relationship between the victim and individual in question? Has the victim filed tax returns as a primary or secondary taxpayer for any of the tax years included in the research period? If the victim has filed returns, did they claim the self-exemption? (2) The reporting person provides only the name and address of the individual they believe committed identity theft, OR The reporting person provides the last four (4) digits of the TIN belonging to the individual they believe committed identity theft, Use IDRS CC NAMES/NAMEI to locate the TIN of the individual in question when the name and address are provided. Use IDRS CC TPIIP to locate the TIN of the individual in question when the last name and last 4 digits of the TIN are provided. If a TIN is located, follow procedures in table scenario (1) above to conduct the necessary research. If a TIN is not located, follow procedures in table scenario (3) below. (3) The reporting person does not provide the name, address, or TIN of the individual they believe committed identity theft and the claim is for the current or two immediately preceding years, Use IDRS CC DDBKD to determine if the victim has been listed as a dependent of anyone for the current or two immediately preceding years. Use of IDRS CC TRDBV may provide the validation of the dependent's TIN on the "MEFILE MEF REJECTED" and/or MEFILE MF POSTED for the year(s) in question of the reporting person. Select the applicable access code for the "SSN-VALDN" field. The "DUP Check Priority Access Code" field will show "2" when there is a duplicate use of the TIN. It will also provide the different TIN on the "ORIG DUP CHECK" field. This different TIN will belong to the other taxpayer who claimed the dependent(s) on their return. If a TIN is located, follow procedures in table scenario (1) above to conduct the necessary research. If a TIN is not located, the dependent is not a victim of identity theft. Document your research and No IDT determination in a CII case note. See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (2). (4) After consideration of the information available, you are unable to identify a taxpayer claiming the victim as a dependent, Claim is for a year that is not available on CC DDBKD and/or CC TRDBV did not provide a different TIN: See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (1). Claim is for a year that is available on CC DDBKD and/or research of CC TRDBV did not provide a different TIN: See IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) – Determinations, paragraph (1) table scenario (2).

# Dependent Related Identity Theft (IDT) - Determinations

25.23.4.8.4.3 (10-01-2025) Dependent Related Identity Theft (IDT) - Determinations After you have identified a streamline dependent IDT case or completed the necessary research described in IRM 25.23.4.8.4.2, Dependent Related Identity Theft (IDT) Non-Streamline Research, refer to the table below to make an identity theft determination: Note: If the reporting person provides their own TIN instead of the TIN of the dependent in question, update the TIN on the CII case. Add a CII case note documenting the reason for the change (i.e., dependent's TIN included in statement on Form 14039, dependent's TIN located through research of the reporting person's filing history, etc.). If Then (1) The issue is taxpayer identified and your research indicates tax administration is not affected, The CII case will remain controlled on IDRS CC TXMOD. Update the CII Category Code to IDT4. Refer to IRM 25.23.3.2.3, Self-Identified – Non-Tax-Related Identity Theft – IDT4. Note: If directed to this scenario from IRM 25.23.4.8.4.2, Dependent Related Identity Theft (IDT) – Non-Streamline Research, paragraph (6) table scenario 4, input the appropriate TC 971 AC 504 indicating a manual letter will be issued. Send Letter 96C. Use paragraph J, and include an open paragraph to provide the following information. You may use the special paragraph below or similar verbiage: "We have reviewed your account and don't see that your federal income taxes were affected." Include appropriate IP PIN information, depending on the facts and circumstances of your case. (2) Your research indicates the dependent was not claimed by anyone. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (3) Your research indicates use of the dependent's TIN is the result of a typo or finger error, Note: This generally results in a math error related to a name control mismatch on the return the TIN was inadvertently included on. The dependent is not a victim of identity theft. Document your research and No IDT determination in a CII case note. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Issue a closing Letter 4674C to the dependent to inform them of the determination. Include paragraph K when the reporting person is not an authorized third party. If the reporting person is not an authorized third party, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional letter requirements. At the time the letter is being issued, for taxpayers under the age of 18, refer to Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for use of a special paragraph when providing the taxpayer with supplemental information regarding IP PINs. In some instances, the dependent will be allowed during original processing, and the taxpayer who incorrectly used the TIN will not be made aware of the misuse through normal math error procedures. When a math error was not set and you can identify the correct address for the individual using the TIN incorrectly, send a Letter 3064C. Include paragraphs L, M, and X. Use the following special paragraphs to inform the individual of the misuse of the TIN: Paragraph L:"We reviewed your tax account for the tax periods listed above and found that your tax return includes incorrect information that did not affect the processing of your return." Paragraph M (TIN is an SSN):"Our records show you are using an incorrect Social Security Number (SSN) for your dependent(s). Please contact the Social Security Administration (SSA) to verify the correct SSN for your dependent(s)." Paragraph M (TIN is an ITIN):"Our records show you are using an incorrect Individual Taxpayer Identification Number (ITIN) for your dependent(s). Please refer to the notice you received informing you of the ITIN assigned to your dependent(s). If you do not have this notice, you may contact the IRS at 800-829-1040 to request a copy." (4) Your research indicates the case is a Mixed Entity due to the filing of a return with the common number (CN) listed as the primary or secondary taxpayer, Note: When the Mixed Entity is identified as a TIN being used for a dependent, refer to the table above scenario (3) above. These situations will be treated as a typo or finger error. The dependent is not a victim of identity theft. Document your research and NOIDT determination in a CII case note. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (5) Your research indicates the case is a Scrambled SSN issue, Add a CII case note documenting your research and determination. Order the NUMIDENT and complete all necessary actions per IRM 25.23.4.6.1, Required Research. IDTVA-A: Reassign the case using the IDTVA-A CII Reassignment Guide. IDTVA-Specialty: Reassign the case using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases. Refer to your functional IRM for additional guidance. (6) Your research indicates the case may be a Married Filing Joint Scheme or an Invalid Joint Election (IJE) issue, Add a CII case note documenting your research and determination. Refer to IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement, to determine if they are a victim of identity theft or if the case is an Invalid Joint Election. (7) Your research indicates the individual in question is the dependent's parent/legal guardian, The dependent is not a victim of identity theft. Document your research and No IDT determination in a CII case note. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Exception: If submitted on a Form 3949-A, the case will be routed to Exam. Refer to IRM 25.23.4.6.2, IDTVA – Additional Research and Required Actions. Review the case for reroute criteria prior to resolving as dependent related IDT. If it is determined it will be routed to Exam, DO NOT open additional cases on CII. • Issue a closing Letter 4674C to the dependent.. Caution: DO NOT use paragraph "I" . Selecting paragraph "I" will automatically include paragraph "u" on Letter 4674C. Paragraph "u" contains incorrect information advising the taxpayer they cannot opt out of the IP PIN program. See Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for more information on special paragraphs you may use. • When the dependent is the reporting person and they were claimed by their parent/legal guardian or the reporting person is the verified parent/legal guardian, include paragraph "N" . In paragraph "N" , use the following special paragraph: Note: In place of (TIN), use Social Security Number or Individual Taxpayer Identification Number, as appropriate. "Your (TIN) has not been used in the fraudulent filing of a federal tax return." • Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, to determine if the dependent has a filing requirement that must be addressed. • Include paragraph "L" when the reporting person is not an authorized third party. • If the reporting person is not an authorized third party, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional letter requirements. Reminder: Include information about the taxpayer's option to request an IP PIN to protect their identity in the future. • At the time the letter is being issued, for taxpayers under the age of 18, refer to Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for use of a special paragraph when providing the taxpayer with supplemental information regarding IP PINs. (8) Your research indicates the Service allowed a self-exemption in error while processing a return for the dependent, The dependent is not a victim of identity theft. Document your research and No IDT determination in a CII case note. When telephone information is available, attempt to contact the reporting person no less than two times. Document each attempt in a CII case note. Note: There must be a reasonable amount of time between the two attempts. For example, another call on a subsequent day constitutes a valid second attempt. If you are able to leave a phone message, allow the reporting person five (5) business days to return your call. The second attempt should not be made immediately after a first unsuccessful attempt. If the reporting person is an authorized third party, verify their identity by completing outgoing disclosure. See paragraphs (25) through (27) in IRM 21.1.1.4, Communication Skills, for specific guidance. Take one of the following actions: • If disclosure is passed, explain that the Service allowed the dependent's self-exemption in error. Apologize for the mistake, and advise them the individual who is entitled to claim the dependent will need to file a paper return, including all income, exemptions, dependents, tax, and any credits they are entitled to. Document your conversation in a CII case note. • If disclosure is not passed, follow procedures in step (4) below. If the reporting person is not an authorized third party and you are able to reach them by phone, advise them you are working the identity theft case. Explain that you are unable to provide information regarding the dependent in question. Inform them the dependent may authorize you to provide the information verbally after verification of their identity. If the dependent in question is available, verify their identity by completing outgoing disclosure. See paragraphs (25) through (27) in IRM 21.1.1.4, Communication Skills, for specific guidance. Refer to IRM 21.2.1.12, Third-Party Authorization, and IRM 21.3.10.3.5, Oral Disclosure Consent (ODC), for additional information. • If Oral Disclosure Consent is received, when speaking to the reporting person, explain that the Service allowed the dependent's self-exemption in error. Apologize for the mistake, and advise them the individual who is entitled to claim the dependent will need to file a paper return, including all income, exemptions, dependents, tax, and any credits they are entitled to. Document your conversation in a CII case note. • If the dependent does not give consent, do not provide information to the reporting person. While speaking with the dependent in question, explain that the Service allowed their self-exemption in error. Apologize for the mistake, and advise them the individual who is entitled to claim them as a dependent will need to file a paper return, including all income, exemptions, dependents, tax, and any credits they are entitled to. Document your conversation in a CII case note. If the dependent is not available, confirm an appropriate time to call back. Attempt contact at the agreed upon date and time. If you are unable to reach the reporting taxpayer or dependent at that time, another contact is not required. After contacting the reporting person (or making the necessary attempts), follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. • Issue a closing Letter 4674C to the dependent. Select paragraph "L" if the reporting person is not an authorized third party. Include an open paragraph with the following special paragraph: "We made a mistake when processing your return. We included the self-exemption which you did not request. If someone is entitled to claim you as a dependent, they may file a paper return or obtain an Identity Protection Personal Identification Number (IP PIN) to do so. We apologize for our error." • If the reporting person is not an authorized third party, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional letter requirements. • At the time the letter is being issued, for taxpayers under the age of 18, refer to Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for use of a special paragraph when providing the taxpayer with supplemental information regarding IP PINs (9) Your research indicates any of the following: The victim is listed as the primary or secondary taxpayer on an invalid return. The victim is a dependent of their parent/legal guardian and is listed as a dependent on the return of a taxpayer who is not their parent/legal guardian (even when there is a history of being listed as a dependent of that person, the parent/legal guardian has not filed with them for years, or the other person claiming the dependent is also a relative). The victim is a dependent of their parent/legal guardian and is listed on an invalid return. When the invalid return was filed using their parent/legal guardian's personal information, the parent/legal guardian is also a victim of IDT. (This scenario may be a TP identified or IRS identified IDT case.) The victim is not a dependent of anyone but is listed as a dependent on a return filed by an individual who is not their parent/legal guardian (including taxpayers listed as dependents by their adult children). Add a CII case note documenting your research and determination. Follow procedures in IRM 25.23.4.10.7, Dependent Related Identity Theft (IDT). Note: For any questionable dependent case received that does not meet one of the scenarios described above, prepare and email Form 4442 using the subject line: Questionable Dependent (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days.

# Identity Theft with Non-Filer Returns

25.23.4.8.5 (10-01-2022) Identity Theft with Non-Filer Returns The Coronavirus Aid, Relief, and Economic Security Act (CARES Act), H.R. 133, Consolidated Appropriations Act, 2021, and the American Rescue Plan Act of 2021 (ARPA) provided eligible individuals with recovery rebate credits (RRC) for tax years 2020 and 2021 that the IRS paid to each eligible individual as an advance payment referred to as Economic Impact Payments (EIP). The IRS issued three EIPs: EIP 1 and EIP 2 (advance payments of the RRC for TY 2020) and EIP 3 (advance payment of the RRC for TY 2021). The IRS was authorized to use certain information included on the taxpayer's recently filed tax return to determine the taxpayer's eligibility for each EIP as follows: EIP 1 - eligibility determined from TY 2019 return (2018 when there is no 2019 return), if filed EIP 2 - eligibility determined from TY 2019 return, if filed EIP 3 - eligibility determined from TY 2020 return (2019 when there is no 2020 return), if filed The IRS created a Non-Filers Tool and made it available for use on irs.gov to allow individuals who had not previously filed returns (because they did not have a filing requirement) to file a tax return to show their eligibility for the RRC and to receive EIP payments. Note: Returns filed using the Non-Filers Tool can be identified with $1 of taxable interest income, $1 total income, and $1 AGI. Although the Non-Filers Tool required verification of the individual's identity, it was not always used as intended. Examples of misuse include but are not limited to: Tax returns filed by identity thieves using a taxpayer's information without their knowledge or consent Tax returns filed by someone the individual trusted to assist them that intentionally included incorrect direct deposit information Research must be completed to determine if there is a high probability the return was not filed by the common number (CN) owner. Research may include, but is not limited to: Comparing filing history for address, filing status, dependents, and direct deposit information Reviewing IDRS CC IRPTR to confirm the taxpayer does not have a filing requirement AMS history items Refer to the table below to determine if the taxpayer is a victim of identity theft related to use of the Non-Filers Tool: If And Then (1) Form 14039, police report, or correspondence is received stating: They did not file the tax return, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, If supported by your research, accept the taxpayer's claim, Case resolution will follow streamline processes. Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, and its subsections, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and its subsections, to identify and address account issues resulting from use of the Non-Filers Tool. (2) Form 14039, police report, or correspondence is received stating: They did not file the tax return, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, Your research does not support accepting the taxpayer's claim. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (3) Form 14039, police report, or correspondence is received stating: They did not file the tax return, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, The claim does not provide enough information to make a determination. Follow procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to request clarification of the identity theft issue. (4) The case is IRS identified, If supported by your research, consider the CN owner a victim of identity theft, Case resolution will follow streamline processes. Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General, and its subsections, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) - General, and its subsections, to identify and address account issues resulting from use of the Non-Filers Tool. (5) The case is IRS identified, Your research does not support a determination of identity theft, Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations.

# Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – General

25.23.4.8.6 (04-28-2025) Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – General Incarcerated taxpayers (prisoners) may experience identity theft in any of the following ways: Note: This list is not all inclusive. A trusted individual intentionally directed a refund to themselves without the taxpayer's knowledge or consent. An invalid return was filed listing them as the primary or secondary taxpayer. They were claimed as a dependent. Their personal information was used to obtain employment, claim gambling winnings, receive unemployment benefits, or report any other type of income the TIN owner is unaware of (i.e., sale of assets, cancellation of debt, etc.). Another individual impersonated them, using their identity to open accounts or otherwise represent themselves as the TIN owner in a way that is not affecting tax administration (i.e., open a line of credit, enroll in school, etc.). Cases involving incarcerated taxpayers may present unique challenges. Refer to the table below for actions and applicable comments: Actions Comments (1) Confirming Incarceration When a history of incarceration cannot be confirmed after conducting research and reviewing case images, it may be necessary to request documentation from the taxpayer. (2) Identifying dates of incarceration When incarceration can be confirmed but the dates of incarceration are not available through research and cannot be located in case images, it may be necessary to request documentation from the taxpayer. (3) Verifying current address Additional research of public records may be required to determine the taxpayer's current address. Use caution when corresponding with the taxpayer to ensure you do not inadvertently provide tax account information to an unauthorized individual. Be aware of additional considerations for correspondence with incarcerated individuals: Generally, it can be assumed facilities housing prisoners open and review all incoming mail. Prisoners are sometimes transferred between facilities. It is necessary to verify the prisoner's current address. When the current address cannot be confirmed, an IRS Service Center address will be used, and correspondence normally sent regarding the IDT claim will not be issued. Issuing a letter to a facility the incarcerated taxpayer is no longer assigned to may result in unauthorized disclosure of personal and tax account information. If incarceration dates are available through research or provided in documentation submitted with the claim, proceed to IRM 25.23.4.8.6.1, Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Streamline Determinations. If incarceration dates are not available, proceed to IRM 25.23.4.8.6.2, Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Non-Streamline Determinations.

# Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Streamline Determinations

25.23.4.8.6.1 (04-28-2025) Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Streamline Determinations The following streamline determination procedures will apply to only the current and three (3) immediately preceding tax years. Exception: When case documentation includes evidence of incarceration (i.e., release documents from the facility, etc.), a streamline determination may be made only when acceptable dates are provided. To be accepted, the documentation must include: •Released Individuals: Month and year for the incarceration and release dates. •Current Incarceration: Month and year for the incarceration and planned release dates. Planned release dates will be future dates. •Continuous Incarceration: Month and year for the incarceration date. A release date is not required if the taxpayer is serving a life sentence. Prior to making a streamline determination, conduct basic research. See IRM 25.23.4.6.1.1, Researching Accounts for Incarcerated Individuals (Prisoners), for additional information. When incarceration cannot be easily confirmed using information provided and internal research, a streamline determination will not be made. Conduct a review of prior years (a minimum of three prior years, if available) and all subsequent years. The prior year review will continue in one-year increments until no indications of identity theft are found. Refer to the table below for case scenarios meeting streamline determination criteria: Note: It is possible for a case to meet more than one scenario in the table below. When you encounter this, refer to all applicable scenarios below to determine the appropriate case actions. Reminder: Each return must be considered separately and may impact credits related to the Coronavirus Aid, Relief, and Economic Security Act (CARES Act) and American Rescue Plan Act (ARPA). Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit, and IRM 25.23.4.21, American Rescue Plan Act (ARPA) – General. If And Then (1) The Form 14039, police report, or correspondence indicates the individual is incarcerated and reporting someone filed a tax return using their personal information without their permission, They are listed as the primary taxpayer on the tax return in question with no secondary taxpayer, AND Income included on the tax return is not verifiable, Accept the taxpayer's claim. Follow the applicable streamline procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT). (2) The Form 14039, police report, or correspondence indicates the individual is incarcerated and reporting income related IDT. The taxpayer was incarcerated for the entire year, OR It is unlikely the taxpayer could have earned the amount reported within the time they were not incarcerated, Example: The taxpayer was not incarcerated for two (2) months of the year, and the income reported is $60,000. Accept the taxpayer's claim. Follow procedures in IRM 25.23.13.3, Closing Income Related Identity Theft Accounts. (3) The Form 14039, police report, or correspondence indicates the individual is incarcerated and reporting non-receipt of their Economic Impact Payment (EIP), It has been determined the incarcerated taxpayer did not receive EIP per IRM 25.23.4.20.2, Economic Impact Payment (EIP) – Additional Research for Identity Theft (IDT) Cases, Accept the taxpayer's claim. EIP issued as direct deposit: Follow the applicable procedures in IRM 25.23.4.20.3, Economic Impact Payment (EIP) – Adjustments. EIP was mailed: The case will be worked as non-tax-related IDT. Refer to IRM 25.23.3.2.3, Self-Identified Non-Tax-Related Identity Theft – IDT4. (4) The Form 14039, police report, or correspondence indicates the individual is incarcerated and reporting non-tax-related IDT (e.g., healthcare coverage, credit card, loan, etc.), There is no indication tax administration is impacted (i.e., invalid return, etc.), The individual is not a victim of identity theft. Follow the applicable procedures in IRM 25.23.3.2.3, Self-Identified Non-Tax-Related Identity Theft – IDT4. (5) The Form 14039, police report, or correspondence indicates the individual is incarcerated and reporting: Non-receipt of EIP, OR Invalid return(s) filed, OR Income related IDT Research does not support their claim of IDT, The individual is not a victim of identity theft. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Cases not meeting the scenarios in the table above or requiring significant research must be thoroughly reviewed to make an identity theft determination. Follow procedures in IRM 25.23.4.8.6.2, Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Non-Streamline Determinations. For additional account conditions that may need to be addressed, refer to IRM 25.23.4.6.2, IDTVA – Additional Research and Required Actions, and Exhibit 25.23.4-21, Input, annotations and Action Requirements for Streamline/Non-Streamline Case Processing.

# Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Non-Streamline Determinations

25.23.4.8.6.2 (04-28-2025) Identity Theft (IDT) with Incarcerated Taxpayer (Prisoner) Involvement – Non-Streamline Determinations When a streamline determination cannot be made, further research and additional considerations will be used to make a non-streamline determination. Verify the taxpayer's current address. For claims received more than 30 days before the current date, research public inmate information to confirm the taxpayer's current address. If Then (1) If the claim includes the address of the facility and research indicates the taxpayer has been released, Attempt to contact the taxpayer by telephone if a telephone number is available. See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), paragraphs (6)-(9). If the phone number isn't available or attempts are unsuccessful, use an IRS Service Center address. (2) If there is any indication the taxpayer is moving facilities and the address of the new facility is not available, Suspend the case for 30 calendar days. If, after the suspense timeframe has passed, the address of the new facility is not available, use an IRS Service Center address. (3) If research shows the taxpayer is now deceased, If the taxpayer was included as the primary or secondary taxpayer on a valid Married Filing Joint (MFJ) return for the current tax year, use the address on the MFJ return. If the taxpayer was not included on a MFJ return for the current tax year, use an IRS Service Center address. (4) If there is no indication the taxpayer is moving facilities and the current address cannot be verified, Use an IRS Service Center address. Verify the dates of incarceration: If Then (1) IDRS CC FTBOLP does not reflect any dates, and it appears the taxpayer is not incarcerated, The taxpayer may be in a local or state facility. Review the correspondence for acceptable dates. If documentation does not include acceptable dates, follow table scenario (3). (2) IDRS CC FTBOLP does not provide complete information, and research shows the taxpayer is now deceased, Proceed to paragraph (5). (3) IDRS CC FTBOLP reflects N/A in the incarceration and release date fields, Prisoner data is incomplete and cannot be perfected. Use the latest incarceration and release dates available on CC FTBOLP. If none of the information available on CC FTBOLP is complete, follow table scenario (4). (4) IDRS CC FTBOLP does not provide enough information to verify the dates, and the taxpayer included supporting documentation, When acceptable dates are not provided, request documentation from the taxpayer. See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). After verifying the taxpayer's current address and dates of incarceration, review the taxpayer's statement. Details they provide may be pertinent to making an IDT determination. Refer to the table below to make an identity theft determination: If And Then (1) The taxpayer states someone claimed them as a dependent, Incarceration was confirmed or not confirmed, See IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) – General, and its subsections to make an IDT determination. (2) The taxpayer is reporting income related IDT, The taxpayer was incarcerated for the entire year, OR It is unlikely the taxpayer could have earned the amount reported within the time they were not incarcerated. Example: The taxpayer was not incarcerated for two (2) months of the year, and the income reported is $60,000. Accept the taxpayer's claim. Follow procedures in IRM 25.23.13.3, Closing Income Related Identity Theft Accounts. (3) The taxpayer is reporting income related IDT, Incarceration dates for the tax year in question cannot be confirmed, OR It is reasonable to believe the taxpayer could have earned the amount reported within the time they were not incarcerated. Example: The taxpayer was not incarcerated for eight (8) months of the year, and the income reported is $12,000. The taxpayer's potential incarceration will not be a factor in making an identity theft determination. Follow procedures in IRM 25.23.13, Income Related Identity Theft, and its applicable subsections to make an IDT determination and resolve the case. (4) The taxpayer states someone filed a tax return using their personal information without their permission, Incarceration was confirmed or not confirmed, AND The return was filed Married Filing Joint (MFJ), Follow procedures in IRM 25.23.4.8.1.3, Married Filing Joint Scheme Involvement, and its applicable subsections. (5) The taxpayer states someone filed a tax return using their personal information without their permission, Incarceration can be confirmed, AND The income is not verifiable (including self-employment income), AND The return was not filed Married Filing Joint (MFJ), Accept the taxpayer's claim. Follow the applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT). (6) The taxpayer states someone filed a tax return using their personal information without their permission, Incarceration can be confirmed, AND The income is verifiable (including self-employment income), AND The return was not filed Married Filing Joint (MFJ), Accept the taxpayer's claim. Follow the applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT). (7) The taxpayer states someone filed a tax return using their personal information without their permission, Incarceration dates for the tax year in question cannot be confirmed, The taxpayer's potential incarceration will not be a factor in making an identity theft determination. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, and its subsections, to make an identity theft determination. (8) The taxpayer states they did not receive their Economic Impact Payment (EIP) and it has been determined the taxpayer did not receive EIP per IRM 25.23.4.20.2, Economic Impact Payment (EIP) – Additional Research for Identity Theft (IDT) Cases, Incarceration can be confirmed, Accept the taxpayer's claim. EIP issued as direct deposit: Follow applicable procedures in IRM 25.23.4.20.3, Economic Impact Payment (EIP) – Adjustments. EIP was mailed: The case will be worked as non-tax-related IDT. Refer to IRM 25.23.3.2.3, Self-Identified Non-Tax-Related Identity Theft – IDT4. (9) The taxpayer states they did not receive their Economic Impact Payment (EIP) and it has been determined the taxpayer did not receive EIP per IRM 25.23.4.20.2, Economic Impact Payment (EIP) – Additional Research for Identity Theft (IDT) Cases Incarceration dates for the tax year in question cannot be confirmed, The taxpayer's potential incarceration will not be a factor in making an identity theft determination. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, and its subsections, to make an identity theft determination. (10) The taxpayer states they did not file the tax return in question, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, AND The tax return was filed using the Non-Filers Tool, Incarceration can be confirmed, Accept the taxpayer's claim. Case resolution will follow streamline processes. Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) – General, and its subsections, to identify and address account issues resulting from use of the Non-Filers Tool. (11) The taxpayer states they did not file the tax return in question, Someone helped them but added direct deposit information that does not belong to them, or They expected to receive the EIP in the mail and did not, AND The tax return was filed using the Non-Filers Tool, Incarceration dates for the tax year in question cannot be confirmed, The taxpayer's potential incarceration will not be a factor in making an identity theft determination. Refer to IRM 25.23.4.8.5, Identity Theft with Non-Filer Returns, to make an identity theft determination. (12) The taxpayer is reporting non-tax-related identity theft (e.g., healthcare coverage, credit card, loan, etc.), Incarceration was confirmed or not confirmed, AND There is no indication tax administration is impacted (i.e., invalid return, etc.), Accept the taxpayer's claim. Follow the applicable procedures in IRM 25.23.3.2.3, Self-Identified – Non-Tax-Related Identity Theft – IDT4. (13) The taxpayer's statement reports: Non-receipt of EIP, OR Invalid return(s) filed. AND Research does not support their claim of identity theft, Incarceration was confirmed or not confirmed, The taxpayer is not a victim of identity theft. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (14) The taxpayer indicates they were incarcerated but does not provide a statement explaining the identity theft issue, Incarceration was confirmed or not confirmed, The taxpayer's potential incarceration will not be a factor in making an identity theft determination. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, and its subsections, to make an identity theft determination.

# Statute Processing Considerations

25.23.4.9 (10-01-2019) Statute Processing Considerations The following subsections provide guidance to process identity theft cases when there are statute related issues to be considered.

# Statute Imminent Assessments for IDT Cases

25.23.4.9.1 (04-28-2025) Statute Imminent Assessments for IDT Cases This section provides instruction for protecting the account when the Assessment Statute Expiration Date (ASED) is imminent (within 180 days of expiration) for Common Number (CN) and Internal Revenue Service Number (IRSN) cases. Refer to the table below for imminent assessments on the CN module: Determination ASED Expiration Actions (1) Invalid/Valid 91 - 180 days remain The adjustment may be input following normal IDRS adjustment procedures. (2) Invalid/Valid 90 days or less remain Refer to IRM 25.23.2.5, Statute Protection, and its subsections to protect the account. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. Once the assessment is pending, complete all remaining actions to resolve the IDT issue. (3) TC 150 SFR/Valid 91 - 180 days remain The adjustment may be input following normal IDRS adjustment procedures. (4) TC 150 SFR/Valid 90 days or less remain Refer to IRM 25.23.2.5, Statute Protection, and its subsections to protect the account. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. Once the assessment is pending, complete all remaining actions to resolve the IDT issue. (5) MFT 32 in Error Regardless of ASED Follow procedures in paragraph (3) of IRM 25.23.4.15, MFT 32 Cases - Moved in Error, to determine the appropriate actions to take. (6) No IDT (with additional actions required) Regardless of ASED Follow applicable statute procedures for the program type (i.e., DUPF, XRET, MXEN, etc.). See IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, for additional information. Refer to the table below for imminent assessments on the IRSN module: Determination ASED Expiration Actions (1) Invalid return must be moved to an IRSN 180 days or more Reprocess the return. (2) Invalid return must be moved to an IRSN Less than 180 days Refer to IRM 25.23.2.5, Statute Protection, and its subsections to protect the account. Note: Use the AMA2859 tool to prepare Form 2859, Request for Quick or Prompt Assessment, when the ASED is less than 60 days. See the AMA SharePoint for additional information and User Guides. Reminder: AM IDTVA employees are required to use AMA2859 to prepare Form 2859. Once the assessment is pending, complete all remaining actions to resolve the IDT issue.

# Addressing Barred Assessments on Identity Theft (IDT) Cases

25.23.4.9.2 (10-01-2025) Addressing Barred Assessments on Identity Theft (IDT) Cases This section provides information on the identification of a barred assessment and initial case actions to be taken prior to adjusting the account when there is IDT involvement. A "barred assessment" occurs when a legal tax assessment is not made within the prescribed period for assessment. The prescribed period for assessment can be identified by calculating the Assessment Statute Expiration Date (ASED) as three years from the IRS received date of the return in question. The ASED of each return on the module must be considered separately. A barred assessment is not determined by a refund or balance due, but the inability to assess tax prior to the expiration of the ASED for the return being considered. Complete thorough research to ensure there is no alternative means of assessing the tax (e.g., extension to file, extended ASED, Form 12810) before determining the assessment is barred. Refer to IRM 25.6.1.13.2.4, Identifying Barred Statute Cases, for examples of "barred assessments" and tolerance amounts. Compare the total tax currently on the module to the amount of tax reported on the return being considered. If the total tax currently on the module is more than the tax reported on the return being considered, the assessment is not barred. Refer to the following options: Invalid/Valid Nullity Case - When the ASED for the valid return has not expired, there is no barred assessment. Follow normal streamline procedures. See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. Invalid/Valid Nullity Case - When the ASED for the valid return has expired, following normal streamline procedures will create a barred assessment if the valid return reports an amount of tax greater than zero. Continue with barred statute procedures. Invalid/Valid IRSN Case - When the ASED for the valid return has not expired and the ASED for the invalid return reporting verifiable income has expired, there is no barred assessment. Follow procedures in IRM 25.23.4.11, Non-Streamline - Determining When Specific Year Account Information Must Be Moved, to address the invalid return. Invalid/Valid IRSN Case - When the ASEDs for both returns have expired, the tax on the valid return cannot be assessed. Follow procedures in IRM 25.23.4.11, Non-Streamline - Determining When Specific Year Account Information Must Be Moved, to address the invalid return. Continue with barred statute procedures to process the valid return. One Return IRSN Case - When the ASED has expired and the tax module has not been abated, follow procedures in IRM 25.23.4.11, Non-Streamline - Determining When Specific Year Account Information Must Be Moved, to address the invalid return. If the tax has been abated, this is a barred assessment due to the erroneous abatement. Continue with barred statute procedures. The following procedures should only be used for cases identified as a barred assessment or erroneous abatement. For detailed case examples, see the IDTVA Barred Checklist Referral job aid on the IDTVA Hub. Before proceeding, perform the following actions: Scan or attach the valid return to the CII case if the return is not in the images of that case or a linked case. If in a linked case, input a CII case note identifying which case includes the valid return. Utilize the IDTVA Barred Checklist Referral located on the IDTVA Hub under "Statute" to assist in verifying all appropriate actions have been taken. Print and retain a copy of any forms and/or worksheets (e.g., Form 1040, Form 5792, Form 8765, Form 12356, penalty calculator, or COMPA) used in the account adjustment(s). The documents will be included with the packet routed to statute. Reminder: Attach any forms and/or worksheets used to the CII case. Use the chart below to identify applicable initial case actions: Note: Input a TC 560 with DLN CD of 70 or 99 to prevent Unpostable Code 178-2. Use DLN CD 70 when correcting the ASED to a later date than the posted ASED. Use DLN CD 99 when correcting the ASED to an earlier date than the posted ASED. Reminder: Ensure the ASED on the account is adjusted to reflect the appropriate date based on the new valid return. When the ASED on the impacted module is expired, a transaction date one day prior to the expiration must be used when inputting the TC 560 to prevent Unpostable Code 178-2. Reminder: If the valid return has not been processed follow procedures in IRM 25.23.4.6.5.2, Unprocessed Documents, and its applicable subsections to post the TC 976. If And Then (1) One return IDT – Erroneous Abatement (No valid return), There is a TC 610 payment, Address the payment: Follow procedures in IRM 25.6.1.11.2.2.10 , ST-12 (Credit No Return), paragraph (3) to identify misapplied payments. Misapplied: Follow procedures in IRM 25.6.1.11.2.2.10, ST-12 (Credit No Return), paragraph (5) to address misapplied payments. Not Misapplied: If made by the valid taxpayer, follow IRM 25.6.1.11.2.2.10, ST-12 (Credit No Return), paragraph (7) to convert the TC 610 to TC 670. Resolve the IDT account: Follow procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, resolve the IDT issue. Reminder: When the valid taxpayer has not filed a tax return, you must determine if they have a filing requirement that needs to be addressed. (2) The posted TC 150 return meets non-streamline criteria, The valid return has posted as TC 976, Update the ASED even though valid return ASED has expired. If a TC 610 payment is present, follow procedures in Table Scenario (1) above to research and address the payment. Continue to paragraph (6). (3) The posted TC 150 return meets non-streamline criteria, A valid return has been received, and resolution of the case requires use of Form 12810, Account Transfer Request Checklist, to move the invalid return, If a TC 610 payment is present, follow procedures in Table Scenario (1) above to research and address the payment. Follow procedures in IRM 25.23.4.11.4.1, Manual Account Transfers – Form 12810, to move the invalid return and update the ASED. At the point of adjustment, continue to paragraph (6) below. (4) The posted TC 150 return meets streamline criteria, the TC 976 return was filed by the valid taxpayer, and the module does not reflect the valid return figures, as allowable, The adjustment input went unpostable, OR The account was backed out in error, OR The adjustment input was incorrect (i.e., incorrect amount of tax, credits, etc.), Do not refer the case back to the person who previously worked the case. Update the ASED even though valid return ASED has expired. If a TC 610 payment is present, follow procedures in Table Scenario (1) above to research and address the payment. Continue to paragraph (6). (5) The is no TC 150 posted, AND/OR A GUF Voided/Deleted return meeting streamline criteria is present, GUF Voided/Deleted return (different DLN) is valid, If the valid return ASED has expired: Determine if the module reflects a Credit Elect (TC 716/TC 710), Estimated Tax (ES) payments (TC 660), and/or a payment with the return (TC 610). Prepare a dummy return with zero tax liability complete with entity and exemption information. Send to SP for processing. Note: Form 1040 must be used when processing a dummy return. Forms 1040-A and 1040-EZ will unpost. Edit the return in red:: ° Across the top of Form 1040 write "Dummy return prepared by IDTVA to post TC 150 for $.00" and "Use long entity" (or similar). ° Below the entity section write "Do NOT "G" Code" (or similar). ° Use original return received date. ° If applicable, edit the "Payments" section of Form 1040 to include the total of any Credit Elect, ES payments, and payments with the return. Suspend the case until the TC 150 has posted. Continue to paragraph (6). If the valid return ASED has not expired: There is no barred assessment. Follow procedures in IRM 25.23.4.11.4, Moving Specific Year Account Information, to determine the appropriate actions to move the valid return to the correct TIN/module as a TC 150. (6) The valid return was moved to MFT 32 in error, There is no TC 150 on MFT 30, OR The TC 150 amount on MFT 30 is less than the tax liability on the return moved to MFT 32 in error, AND A valid return moved to MFT 32 has a tax liability greater than zero, Follow procedures in IRM 25.23.4.15, Moved in Error, paragraph (3) Table Scenario (4). When the valid taxpayer's return is reporting a balance due, determine the amount of penalty and/or interest that cannot be assessed. This applies whether the return was timely filed or late, regardless of whether the balance was paid in full, partially paid, or remains unpaid. The amount of the barred assessment includes penalties and interest when determining the total amount lost to the IRS. Applicable penalties including Estimated Tax (ES) penalty, Failure to File (FTF) penalty, and Failure to Pay (FTP) penalty as well as interest are calculated to the ASED of the return being considered when determining the total amount of the barred assessment. Caution: The (IRN) 871 procedures will not be followed when the ASED has expired. FTF assessed for a maximum of 5 months FTP calculated from the return due date to the ASED Interest calculated on the unpaid balance, plus applicable penalties, to the ASED Refer to IRM 20.1.2, Failure To File/Failure To Pay Penalties, IRM 20.1.3, Estimated Tax Penalties, and IRM 20.2.5, Interest on Underpayments, for additional information. Example: A 2012 valid return was received 09262013 with a balance due. No extension or history of an extension was present, and no payments were made on the account. Penalties should be calculated as follows: • FTF assessed for 5 months (maximum) • FTP calculated from 04152013 to 09262016 • Interest computed for the balance, plus applicable penalties to 09262016 After all initial case actions have been taken, continue to IRM 25.23.4.9.2.1, Adjusting Accounts with Barred Assessments, for adjustment and closing actions. Note: Employees resolving a barred assessment with compliance involvement will refer to IRM 25.23.4.9.2.2, Resolving a Barred Assessment with Compliance Issues (IDTVA Specialty Functions Only).

# Adjusting Accounts with Barred Assessments

25.23.4.9.2.1 (03-11-2024) Adjusting Accounts with Barred Assessments All required actions from previous IRM guidance must be taken before adjusting the account. Reminder: Identity theft case actions and coding still apply when resolving a barred assessment account (e.g., RC 139, offsets, IDT indicators, secondary taxpayer, etc.). When the valid taxpayer files a return, the account must be adjusted to reflect the return information, as allowable. Follow procedures below when inputting the adjustment to the valid return figures. DO NOT back out the account. The current tax amount must remain on the account to protect that portion of the otherwise barred tax and will be accounted for when figuring the adjustment. Math verify the valid return. Follow procedures in IRM 21.5.4, General Math Error Procedures, to identify math errors and determine if the adjustment will require initial math error actions. If the return does not meet math error criteria but reflects information that is not allowable based on law or regulation, follow procedures in IRM 21.5.3.4.6, No Consideration and Disallowance of Claims and Amended Returns, to determine if the corrective action requires disallowance, partial disallowance, or no consideration actions. Recompute tax and/or credits, if necessary. Determine the amount of tax that cannot be assessed. Input the adjustment to the return figures, as allowable. Include appropriate Item Reference Numbers (IRN) and Credit Reference Numbers (CRN) to reflect the correct amount of dependents/exemptions, adjusted gross income (AGI), taxable income (TXI), self-employment tax (SE tax), Earned Income Tax Credit (EITC), Additional Child Tax Credit (ACTC), etc. Use HC 4. Include the appropriate Blocking Series (BS) if setting a math error or partially disallowing the claim. If fully disallowing the claim, input a separate TC 290.00 with the appropriate blocking series. Caution: If the invalid return(s) and subsequent adjustments to the module result in a total tax of more than .00 on the module, refer to paragraphs (3)-(4) below before adjusting the account. If the valid return is reporting a balance due and was not fully paid by the Return Due Date (RDD), IRN 871, PC 2 procedures cannot be used. As the ASED is expired, in this case you cannot assess any penalties with any amounts other than .00 (e.g., TC 160 .00, TC 270 .00, TC 170 .00, etc.). If following math error procedures, no consideration procedures, or disallowing in full or part, issue the appropriate letter to provide an explanation of the changes made. Include appeal rights, when applicable. Follow normal statute procedures for determining if payments are refundable. See IRM 25.6.1.5, Basic Guide for Processing Cases with Statute of Limitations Issues, for more information. When the valid return is reporting a refund that is allowable and tax cannot be assessed due to the ASED expiration, the result of the adjustment input will be a credit on the module that is more than what the taxpayer is entitled to receive. Issue a manual refund for the amount of the allowable refund, plus applicable credit interest, when applicable. See IRM 25.23.4.10.10, Identity Theft (IDT) - Manual Refunds, for additional information. Use Form 8758 to apply the credit remaining on the account to the Excess Collection File. The amount of refundable credits applied should equal the amount of tax that was barred from assessment. Note: Refer to IRM 25.6.1.7.3.1, Transferring Credit to XSF, for additional guidance. Refer to IRM 21.5.6.4.8, -D Freeze, for guidance on how to resolve -D freeze accounts. Procedures have been established to allow for tax posted to a module from an invalid return to be used to prevent or reduce the amount of a barred assessment under IRC 6201(a)(1). When the valid taxpayer's return is reporting tax in an amount that is more than zero and the ASED for the valid return has expired, follow the procedures below to protect the assessment, when possible. When the total tax on the module is less than the amount of tax reported on the valid return, do not input an adjustment to back out the account. Adjust the account to the figures on the valid return, as allowable. This results in a barred assessment that is less than it would be if the account was fully backed out first. See Example 1: Barred Assessment. Example: #1 The TC 150 return for TY 2012 is determined to meet streamline criteria. The valid taxpayer filed a refund return reporting tax of $5,000 and withholding of $7,500. The ASED for the valid return is expired. Based on the original return, the account shows TC 150 tax of $3,000, and withholding of $5,000. The valid taxpayer files their original return that posts as a TC 976. The return is not processed prior to the expiration of the ASED. The tax on the account is less than the amount of tax reported on the valid taxpayer's return. The result is a barred assessment for the amount that cannot be assessed "$2,000" . When the total tax on the module is more than the amount of tax reported on the valid return, do not input an adjustment to back out the account. Adjust the account to the figures on the valid return, as allowable. This will prevent a barred assessment. See Example 2: Not a Barred Assessment. Example: #2 The TC 150 return for TY 2013 is determined to meet streamline criteria. The valid taxpayer filed a refund return reporting tax of $1,000 and withholding of $1,500. The ASED for the valid return is expired. Based on the original return, the account shows TC 150 tax of $2,000, and withholding of $3,500. The valid taxpayer files their original return that posts as a TC 976. The return is not processed prior to the expiration of the ASED. The tax on the account is more than the amount of tax reported on the valid taxpayer's return. The account can be adjusted to the valid return figures to prevent a barred assessment. Follow IRM 25.23.4.6.3, IDTVA Research, Verification, and Requests, for remaining identity theft actions. After adjusting the account and resolving the identity theft issue, the barred assessment will be referred to your local statute unit per IRM 25.23.2.5.4, Barred Statutes, using the following guidelines. Open a monitoring control base per IRM 25.23.4.3.1, CII and IDRS Case Controls, until all adjustments have posted to ensure the IDT issue has been fully resolved. Do not keep the CII case open if the only remaining action is monitoring adjustments. Attach a completed copy of the IDTVA Barred Checklist Referral to Statute to the CII case. Prepare the packet for referral to statutes and complete the following actions: Print the valid return, CII case with all notes, penalty and interest computations, TXMODA (including case status history), forms used in case actions (e.g., 5792, 12356), and IDTVA Barred Checklist Referral to Statute. Prepare Form 3210, Document Transmittal, to route the entire package to your local statute unit. Include in the remarks section "ID Theft Barred Assessment amount $XX.XX" and "ID Theft issue reported" IRM 25.6.1.13.2.1, Barred Statute Report (Form 9355/3999). Leave a CII case note with the same remarks as the Form 3210, route package to your local statutes unit, and close the CII case if all issues have been addressed.

# Resolving a Barred Assessment with Compliance Issues (IDTVA Specialty Functions Only)

25.23.4.9.2.2 (03-16-2023) Resolving a Barred Assessment with Compliance Issues (IDTVA Specialty Functions Only) This section of the IRM is for employees resolving a barred assessment on an identity theft case with compliance involvement (IDTVA Specialty Functions Only). Refer to the instructions in IRM 25.23.4.9.2, Addressing Barred Assessments on Identity Theft (IDT) Cases, and IRM 25.23.4.9.2.1, Adjusting Accounts with Barred Assessments, in addition to the instructions within this IRM section. Procedures have been established to allow for tax posted to a module from a tax return meeting streamline criteria and/or additional valid assessments to be used to prevent or reduce the amount of a barred assessment. A statutory notice of deficiency may have been issued to assess and collect income tax, estate tax, gift tax, and certain excise and employment tax deficiencies, per IRM 25.6.1.9.6.2, Statutory Notice of Deficiency (90 Day Letter). The determination whether a Compliance assessment can be used to protect the account from containing a barred assessment depends upon the issuance of the notice of deficiency. Use the table below to determine if tax from a compliance assessment can be used to protect the account from being considered barred. If And Then (1) Notice of Deficiency was issued Was sent to the valid taxpayer's address of record at the time of issuance, and Meets all required criteria for notice of deficiency (e.g., tax and penalty calculations, waiver, and taxpayer rights) The valid Compliance assessment can be used to protect the account from being considered barred. Continue to paragraph (4). (2) Notice of Deficiency was issued Was sent to an address other than the valid taxpayer's address of record at the time of issuance, or Does not meet all required criteria for notice of deficiency (e.g., tax and penalty calculations, waiver, and taxpayer rights) The invalid Compliance assessment cannot be used to protect the account from being considered barred and must be abated. Continue to paragraph (4). Once you have determined if the Compliance assessment is valid or invalid, follow the table below to decide if there is a barred assessment and what actions to take. Note: Total tax equals the tax assessed from the original TC 150 return plus any additional TC 290/300 assessments minus any additional TC 291/301 abatements. Caution: To protect the account from being barred, DO NOT back out the account, if the taxpayer's valid return reports a tax amount and there is tax on the current account module. The current tax amount must remain on the account to protect that portion of the otherwise barred tax and will be accounted for when figuring the adjustment. If And Then (1) The Compliance assessment is valid and there is no barred assessment, The total tax on the module is greater than or equal to the tax on the taxpayer's valid return, Adjust the account to the figures on the valid return, as allowable, following your functional IRM guidance for IDTVA cases involving Compliance issues. See IRM 25.23.10, Compliance Identity Theft Case Processing. See Example 2 below. (2) The Compliance assessment is valid and there is a barred assessment, The total tax on the module is less than the tax on the taxpayer's valid return, Adjust the account to the figures on the valid return, as allowable, following IRM 25.23.4.9.2.1, Adjusting Accounts with Barred Assessments. The barred tax is the total amount that cannot be assessed (difference between the tax on the taxpayer's valid return and the total tax on the account). (3) The Compliance assessment is invalid and there is no barred assessment, The total tax on the module, not including the Compliance assessment, is greater than or equal to the tax on the taxpayer's valid return, Adjust the account to the figures on the valid return, as allowable. See Example 1 below. (4) The Compliance assessment is invalid and there is a barred assessment, The total tax on the module, not including the Compliance assessment, is less than the tax on the taxpayer's valid return, Adjust the account to the figures on the valid return, as allowable, following IRM 25.23.4.9.2.1, Adjusting Accounts with Barred Assessments. The barred tax is the total amount that cannot be assessed (difference between the tax on the taxpayer's valid return and the total tax on the tax account). See Example 3 below. See the IDTVA Barred Checklist Referral job aid on the IDTVA HUB. Example: # 1 - Not a Barred Assessment (Invalid Compliance Assessment) The TC 150 return for TY 2016 is determined to be a nullity. The valid taxpayer filed a return reporting tax of $2,000 and withholding of $3,000. The ASED for the valid return is expired. Based on the original (invalid) return, the account shows TC 150 tax of $5,000, withholding of $7,000, and AOTC of $2,000. A refund of $4,000 was issued to the invalid taxpayer by direct deposit. A CP 2000 was issued to an address other than the valid taxpayer's last known address proposing a tax increase of $8,000, an increase to withholding of $1,500, and removal of AOTC. No response was received, and a default assessment posted. The taxpayer files Form 14039 stating the refund from the current year return was applied to a balance owed for TY 2016. The taxpayer reports someone else is earning income under their SSN and states they mailed their return in January 2018. Research confirms the taxpayer is a victim of income and refund related identity theft. The tax assessed based on the CP 2000 cannot be considered when determining if there is a barred assessment. Because of the TC 150 tax of $5,000 is more than the tax of $2,000 reported by the valid taxpayer, the account will be adjusted to the valid taxpayer's return figures, preventing a barred assessment. Example: # 2 - Not a Barred Assessment (Valid Compliance Assessment) The TC 150 return for TY 2018 is determined to be a nullity. The valid taxpayer filed a return reporting tax of $8,000 and withholding of $2,000 which posted as a TC 976. The ASED for the valid return is expired. Based on the original (invalid) return, the account shows TC 150 tax of $1,000, ACTC of 3,000, and EIC of $5,000. Exam is holding the refund pending verification of relationship and residence for the dependents listed. A statutory notice is issued to the valid taxpayer's address. No response was received, and the account is adjusted to remove the dependents and related credits. The result is an increase in tax of $10,000. The case with the TC 976 return is routed to Exam as audit reconsideration. After contact with taxpayer, the taxpayer files Form 14039 to report someone else filed the first return received for TY 2018. The case is referred to IDTVA. The tax assessed based on the Exam audit can be considered when determining if there is a barred assessment, because the notice of deficiency was issued to the valid taxpayer's last known address. The TC 150 amount plus the TC 300 amount totaling $11,000 is more than the amount of tax reported on the valid taxpayer's return. The account will be adjusted to the valid taxpayer's return figures, preventing a barred assessment. Example: # 3 - Partially Barred Assessment - (Invalid Compliance Assessment) The TC 150 return for TY 2017 is determined to be a nullity. The valid taxpayer filed a return reporting self-employment income, total tax of $6,000, estimated tax payments of $4,000, and a balance due of $2,000 which posted as a TC 976. The ASED for the valid return is expired. Based on the original return, the account shows TC 150 tax of $3,000, and withholding of $5,000. A CP 2000 proposing a tax increase of $9,500 based on non-employee compensation is issued to an address other than the valid taxpayer's last known address. No response was received, and the assessment was made. The case with the TC 976 return is routed to AUR for audit reconsideration. After contact with the taxpayer, the taxpayer files Form 14039 to report someone else filed the first return received for TY 2017. The case is referred to IDTVA. The tax assessed based on the CP 2000 cannot be considered when determining if there is a barred assessment, because the notice of deficiency was issued to an address other than the valid taxpayer's last known address. The TC 150 amount is less than the amount reported on the valid taxpayer's return. The modules are adjusted to the taxpayer's return figures. This results in a barred assessment of $3,000 plus applicable penalties and interest. Example: # 4 - Erroneous Abatement The timely filed TC 150 return for TY 2018 is determined to be a nullity. The valid taxpayer filed a return reporting tax of $.00 and withholding of $2,500 which posted as a TC 976. Form 14039 is included with the return. The ASED for the valid return is expired. Based on the original return, the account shows TC 150 tax of $5,000, and withholding of $6,000. A CP 2000 proposing a tax increase of $2,000 based on unreported income is issued to the valid taxpayer's last known address. No response was received, and the assessment was made. An adjustment to the valid return figures is input. After being selected for quality review, it is determined the nullity procedures followed were incorrect. The case does not meet streamline criteria. The ASED for the TC 150 return is expired, and the tax originally assessed was abated in error. The invalid return cannot be processed to an IRSN due to the expired ASED creating a barred assessment due to erroneous abatement.

# Resolving Identity Theft (IDT) Cases

25.23.4.10 (06-05-2025) Resolving Identity Theft (IDT) Cases The following subsections provide guidance to address specific account conditions based on the determination made and the facts and circumstances of the module. Multiple references may be applicable for the same case. When updating the ASED based on the valid taxpayer's return, consider the following: Input a TC 560 with DLN CD of 70 or 99 to prevent Unpostable Code 178-2. Use DLN CD 70 when correcting the ASED to a later date than the posted ASED. Use DLN CD 99 when correcting the ASED to an earlier date than the posted ASED. If the valid taxpayer has filed two returns, and the second return is intended to be superseding, the ASED will be calculated using the received date of the first return. The account will be adjusted to the correct figures on the second return, as allowable. Caution: To prevent an unpostable (UPC 178-2), see IRM 3.12.179.79.3, UPC 178 Reason Code 2 Assessment Expiration Date (ASED), for additional information. Reminder: Ensure the ASED on the account is adjusted to reflect the appropriate date based on the new valid return. When the ASED on the impacted module is expired, a transaction date one day prior to the expiration must be used when inputting the TC 560 to prevent Unpostable Code 178-2. If the victim is a secondary filer on a joint return: Input TC 594 CC 084 on the secondary TIN to cross reference the primary TIN if one has not systemically generated already. Reverse the TC 971 AC 522, if one is present, with MISC Code "OTHER" on the primary TIN/joint account only when the primary taxpayer wasn't a victim. When all of the following conditions are met, the identity theft issue does not affect tax administration. The case will be closed with a TC 971 AC 504 upon completion of any actions necessary to resolve the case: The only invalid return(s) on the module are rejected attempts to file (no invalid returns accepted) Form 14039 was received Exception: If the account meets these criteria and the taxpayer is a victim of income related identity theft, see IRM 25.23.13, Income Related Identity Theft, for applicable procedures. Determine whether the account will be in a balance due status after adjustment action posts. If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. Take action to resume collection activity when appropriate. Refer to IRM 25.23.4.12.3, Collection Activity - Resume Collection Actions, for guidance. If an invalid return includes dependents, you may IRS identify the IDT issue for each dependent a claim has not been received for. Refer to IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General, for additional information.

# Identity Theft (IDT) with Invalid Returns

25.23.4.10.1 (06-05-2025) Identity Theft (IDT) with Invalid Returns Procedures in this section are intended to be followed after making a Common Number (CN) ownership determination and identifying an invalid return on the impacted module. Reminder: Each return in question must be considered and addressed separately. If the case involves an amended return, follow procedures in IRM 25.23.4.10.5 , Amended or Duplicate Returns and Identity Theft (IDT). If necessary, update the entity (i.e., current address, telephone number, filing status, etc.). If the account reflects a balance due and was not previously protected to prevent balance due notices, tax offsets, and/or enforcement actions, take the necessary action to protect the account. See IRM 25.23.4.6(3), Research, Actions and Complete Case Analysis – Overview. When the refund was issued to the invalid taxpayer: Streamline: Move the lost/partially lost refund to the General Ledger GL 1545. See IRM 25.25.4.7, Reversing Identity Theft Lost Refunds. Non-Streamline: Move the lost refund to the appropriate tax module for the Internal Revenue Service Number (IRSN) assigned. See IRM 21.5.2.4.23.10, Moving Refunds. Exception: When following No Move procedures, no transactions will be moved from the CN to the IRSN. Refer to the table below for specific account circumstances which must be considered prior to inputting an adjustment or taking any other action on the account: Account Circumstances Actions (1) Dependents When the invalid return includes dependents, dependent related identity theft must be considered for those individuals. Refer to IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) – General, and its subsections for additional information. (2) Valid return received after due date When the valid return was received after the return due date: Correct the Assessment Statute Expiration Date (ASED) – add 3 years to the valid return received date. Update the Return Processable Date (RPD) – See IRM 20.2.4.6, Unprocessible Returns, and IRM 20.2.4.6.1, Updating the RPD on Unprocessible Returns. (3) Invalid return includes Direct Deposit (DD) information When the invalid return includes DD information, input TC 971 AC 850 to prevent future refunds from being directly deposited into the account associated with the invalid taxpayer. (4) Penalties When the valid return did not post as the TC 150 and reflects a balance due: When the taxpayer did not timely file, see IRM 20.1.2.3.7, Failure to File a Tax Return – IRC 6651(a)(1). When the balance was not paid in full by the return due date, see IRM 20.1.2.2.6.3, Wrong Return Posed First. Determine if the taxpayer is subject to an Estimated Tax penalty (ES penalty). See IRM 20.1.3.2.2, Manual Penalty Adjustments. (5) Refund If the valid taxpayer is due a refund, the refund should be systemically released unless an exception applies. See IRM 25.23.4.10.10 , Identity Theft (IDT) – Manual Refunds. Note: If a manual refund is required and the return meets criteria for DIF scoring, the manual refund should be issued before the return has been DIF scored. Exception: If the CN owner (or the spouse of the CN owner) filed a Form 8379, Injured Spouse Allocation, refer to table scenario (11) for additional information. (6) Offsets When the tax module reflects tax offsets and/or TOP offsets, refer to IRM 25.23.4.10.3 , Identity Theft with Offsets. (7) Payments Determine who made the payments. Determine if the payments are available for refund or offset. See IRM 25.23.4.6.2.1, Statute Research. Streamline: If made by the invalid taxpayer, move the payment to Excess Collections. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Non-Streamline – No Move (with credit balance): If made by the invalid taxpayer OR made by the valid taxpayer and not refundable, move the payment to Excess Collections. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Non-Streamline – Move: If made by the invalid taxpayer, move the payment to the IRSN module (8) Economic Impact Payment (EIP) or Recovery Rebate Credit (RRC) When EIP and/or RRC are impacted due to the filing of an invalid return, refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) – General, and its applicable subsections. (9) American Rescue Plan Act (ARPA) Unemployment Compensation Tax Relief Advanced Child Tax Credit (AdvCTC) Excess Advance Premium Tax Credit (APTC) Repayment Relief When relief provided under ARPA provisions may be impacted, refer to IRM 25.23.4.21, American Rescue Plan Act (ARPA) – General, and its applicable subsections (10) First Time Home Buyer Credit (FTHBC) When FTHBC may be involved: When a math error was set for the recapture of FTHBC and the CN owner did not receive FTHBC, see IRM 21.6.4.4.17.4, Manually Adjusting the Recapture amount. When an invalid return claiming FTHBC was received, refer to IRM 21.6.3.4.2.10.7, First-Time Homebuyer (FTHBC) – Adjusting Accounts. (11) Affordable Care Act (ACA) When adjusting an account for TY 2014 or later: Compute the Premium Tax Credit (PTC) and all related data elements. See IRM 21.6.3.4.2.12.4, Tools for Accessing ACA-Related Taxpayer Data, and IRM 21.6.3.4.2.12.7, Adjusting the Account. Determine the taxpayer's liability for the Shared Responsibility Payment (SRP). See IRM 21.6.4.4.20.3, Shared Responsibility Payment Overview, and IRM 21.6.4.4.20.3.1, Shared Responsibility Payment Adjustments. (12) Combat Zone Combat Zone accounts are identified by a -C Freeze and indicate the taxpayer is or was in a designated combat zone. The -C Freeze remains on the account even after the taxpayer is no longer in the combat zone. When a -C Freeze is present, additional research is required to determine the taxpayer's combat zone status. Research IDRS CC IMFOLE for the Combat indicator on Line 11 to determine the correct action to take. Combat Indicator: 1 – The taxpayer is still serving in a combat zone. Any compliance activity, such as assessing or collecting tax, is prohibited. However, if the taxpayer has other issues or requests information, you may work these other issues and contact the taxpayer, if needed. Combat Indicator: 2 – The taxpayer is no longer in a combat zone. Follow normal procedures to resolve the case. (13) Discriminant Index Function (DIF) Score Determine if the TC 976/977 return meets criteria for DIF scoring. See IRM 21.5.2.4.23.6, Discriminant Index Function (D9F) SCORE or CLASSIFICATION "Send Return(s) to Examination for Review". Do not refer Form 1040-EZ.. If DIF score criteria is met, all adjustment actions must be input prior to referring the case to Exam. Use Priority Code (PC) 1 on your adjustment. (14) Injured Spouse (Form 8379) If the CN owner (or the spouse of the CN owner) filed an injured spouse claim, and: You do not have the skill set to resolve the case – Do not attempt to issue a refund. Open a new CII case with Category Code "DMFC" . Assign the case to the IDRS number located on the Accounts Management Site Specialization Temporary Holding Numbers listing located on SERP. For the required fields, input the Doc Type as "Injured Spouse Claim" , use Program and Function Code "ADJ-710-97140" , "Priority 2" , and reason "Form 8379 attached" . Reminder: If your site works both IDT case work and injured spouse case work, do not reassign the case. The case should be retained and worked within your site. You do have the skill set to resolve the case – Take all necessary actions to resolve the IDT issue following normal procedures. Use Hold Code (HC) 4 on your adjustment or TC 570 with credit transfers to hold the resulting credit. Then open a new CII case with Category Code "DMFC" , Program and Function Code "710-97140" , and "Priority 2" . Resolve the injured spouse claim (15) Presidential Election Campaign Fund (PECF) When the valid return reflects yes to PECF and the invalid return did not, see IRM 21.6.7.4.12, Presidential Election Campaign Fund. (16) Statute Year If the required adjustment includes a tax increase or credit decrease: ASED is open: See IRM 25.23.4.9.1, Statute Imminent Assessments for IDT Cases. Assessment is barred:IRM 25.23.4.9.1, Addressing Barred Assessments on Identity Theft (IDT) Cases. (17) Valid taxpayer has not filed Determine if the valid taxpayer has a filing requirement and address unfiled returns, if necessary. See IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions. (18) Non-Streamline Research CC NAMES to determine if the taxpayer was previously assigned an IRSN. If an IRSN was not assigned, follow local procedures to obtain an IRSN. Once an IRSN has been identified, establish the entity with TC 000 or update the previously established account if current information for the IRSN taxpayer is available. See IRM 3.13.5.117, Establishing a New Account (TC 000). If a valid address cannot be identified, use a Service Center (SC) address. See IRM 3.13.5.66, Campus Address Used Only When Taxpayer Address is Unavailable. Refer to the table below for adjustment considerations: Adjustment Item Details (1) Blocking Series (BS) Use BS 00, unless setting a math error or disallowing the claim. See IRM 21.5.2.4.22, Blocking Series (BS), for additional information. (2) Override Code Use an Override Code, when necessary: R – Allows the IRS Received Date to be older than a year. S – Allows the current date and Refund Statute Control Date to be later than the Refund Statute Expiration Date (RSED). (3) Refund Statute Clear Date (RFSCDT) Use the timely filed claim received date or timely post mark date if the claim received date is not available. (4) Source Code (SC) Use SC 0. (5) Reason Code (RC) RC 139 is used to identify an adjustment due to an identity theft claim or issue. (6) Hold Code (HC) Use the appropriate hold code depending on the expected outcome of the adjustment. HC 3 – Will hold only the adjustment notice. Use for adjustments resulting in a zero balance, balance due, or credit that will be offset or refunded systemically. HC 4 – Will hold the adjustment notice and resulting credit. Use for adjustments resulting in a manual refund, disallowance of a refund, or when all or some of the refund will be applied to a valid balance due or as a credit elect by inputting a credit transfer. (7) Priority Code (PC) Only use a PC, when necessary. See IRM 21.5.2.4.16, Priority Codes (PC), for additional information. (8) Posting Delay (PD) Code PD Codes are used to ensure account actions and adjustments will post in the correct order. See IRM 21.5.2.4.17, Posting Delay Code (PDC), for additional information. When inputting an entity update or TC 971 AC 850, post delay your corrective adjustment by one cycle. When inputting an entity update and TC 971 AC 850, post delay TC 971 AC 850 by one cycle and your corrective adjustment by two cycles. When transferring a credit to the module the adjustment will be input on, post delay your corrective adjustment by one cycle. (9) Source Document No Source Document (NSD) (10) Remarks Notate "Identity Theft" or similar. Refer to the table below to identify applicable tax module actions based on the determination made when streamline criteria is met: Note: Upon completion of the applicable case actions, continue to paragraph (10) to close the case. Determination Case Actions (1) Invalid/Valid Math verify the valid return. If a refund is claimed or the adjustment will result in a credit balance from payments on the module, determine if a refund is allowable. See IRM 25.23.4.6.2.1(6), Statute Research. Input an adjustment to the valid return figures, as allowable. If the resulting credit cannot be refunded, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). (2) One Invalid Return Input an adjustment to fully back out the account. If there is a resulting credit from payments on the module, determine if a refund is allowable. See IRM 25.23.4.6.2.1(6), Statute Research. If the resulting credit cannot be refunded, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). (3) Two or More Invalid Returns (No Valid Return) Reminder: Manager/Lead concurrence may be required. Input an adjustment to fully back out the account. If there is a resulting credit from payments on the module, determine if a refund is allowable. See IRM 25.23.4.6.2.1(6), Statute Research. If the resulting credit cannot be refunded, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). (4) Valid/Invalid Account has not been adjusted: Input TC 290 .00 with BS 05 and RC 139. Account has been adjusted: Input an adjustment to the original valid return figures, as allowed. If there is a resulting credit from payments on the module, determine if a refund is allowable. See IRM 25.23.4.6.2.1(6), Statute Research. If the resulting credit cannot be refunded, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Regardless of the determination made, when non-streamline criteria is met, determine if the invalid return will be moved to the IRSN module or if it meets No Move criteria. See IRM 25.23.4.11, Non-Streamline – Determining When Specific Year Account Information Must Be Moved, and its applicable subsections. After taking all required actions, including monitoring, when necessary, continue to paragraph (10) to close the case. Refer to the table below to identify and complete required actions prior to closing the case: Action Details (1) EITC Recertification Indicator If the EITC Recertification Indicator was placed on the account because of an invalid return, reverse the indicator. See IRM 4.19.14.7(6), Recertification, for additional guidance. (2) Balance Due TC 470 CC 90 Input No additional actions is required. The corrective adjustment will full pay the balance. TC 470 no CC Input A balance due remains. Input TC 472 to allow normal collection activity to continue (i.e., balance due notices, etc.). Form 14394 Completed See IRM 25.23.4.12.1, Collection Activity - Form 14394, to determine if follow up is required. Form 13794 Completed See IRM 25.23.4.12.2, Collection Activity – Form 13794 Additional Actions Required – Lien, to determine if follow up is required. (3) Closing Letter CN Owner Ensure an appropriate closure letter is issued when a valid address can be located. IRSN Owner Issue Letter 4675C from the IRSN account when a SC address was not used for the taxpayer's address. Do not include the CN in the correspondence. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. (4) Identity Theft Indicator Input the appropriate identity theft indicator: Taxpayer Identified (TC 971 AC 501) – See IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration – TC 971 AC 501 IRS Identified (TC 971 AC 506) – See IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration – TC 971 AC 506. Impacted years identified through CCA – See IRM 25.23.4.6.4, Complete Case Analysis.

# Identity Theft (IDT) Cases/Transcripts with RIVO and/or TPP Involvement - Resolution Tables

25.23.4.10.2 (12-20-2022) Identity Theft (IDT) Cases/Transcripts with RIVO and/or TPP Involvement - Resolution Tables There are instances when IDTVA receives cases with RIVO and/or TPP involvement that require additional guidance to resolve. The charts in paragraphs (2) and (3) below illustrate various case scenarios you may receive that can be resolved. Before proceeding to the resolution charts, refer to the bullet list below for instances when the current year must be resolved by RIVO/TPP. The income cannot be verified using IRM 25.23.4.8.2.1, IDT with RIVO Involvement. A UPC 147 is present on the account with RC 6/7 or 8. (All UPC RC 0 or 1 will be worked by SPIDT criteria). See IRM 21.4.1.4.1.2, Return Found/Not Processed Note: Each return for each tax year must be screened separately. Reminder: When resolving an account with identity theft involvement, the IDTVA employee must address all issues per IRM 25.23.2.3.2.1, Addressing All Taxpayer Issues, and on all active tax years IRM 25.23.4.6.4, Complete Case Analysis. For cases/transcripts with TPP involvement, see the table below. Reminder: All cases with RIVO involvement must be closed with the IDT8/IDS8 category code, unless the case is a transcript (IDT6/IDS6) or meets criteria described in IRM 25.23.4.8.2.1, Identity Theft (IDT) with RIVO Involvement. Reminder: If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. Reminder: If the invalid return includes dependents, dependent related identity theft must be considered. Refer to IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General, for additional information. Caution: IDTVA paper procedures for closing indicators and letters will continue to be followed even when directed to another IRM reference. Read the entire "Then" column for the applicable scenario prior to proceeding to the linked reference. If And Then (1) TPP issue is unresolved, The taxpayer has authenticated per AMS notes, you can validate the return per IRP data, OR the taxpayer is claiming IDT Caution: Before continuing, ensure this is not a data breach. Exception: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ You can resolve UPC 126 0 or TC 971 AC 129 following IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistance Center (TAC) Assistors, procedures. When following IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistance Center (TAC) Assistors, for returns validated per IRP data or taxpayer claiming IDT disregard Authentication Passed references and phone specific procedures within this IRM section. (2) TPP issue is unresolved, The taxpayer has not authenticated per AMS notes, the return cannot be validated per IRP data, OR There is no IDT involvement (i.e., TRUE DUP) and IDTVA cannot make a determination. Caution: Before continuing, ensure this is not a data breach. Follow IRM 21.5.6.4.9, E-Freeze, or IRM 21.5.1.4.4.1, Unresolved Taxpayer Protection Program (TPP) Issues for Correspondence and Loose Forms, as applicable. (3) TPP issue is unresolved, TP filed a potential amended return or there is no IDT involvement (i.e., TRUE DUP) and IDTVA can make a determination. Caution: Before continuing, ensure this is not a data breach. You can resolve UPC 126 0 or TC 971 AC 129 following IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistance Center (TAC) Assistors, procedures. Disregard phone specific procedures. Note: Account freeze conditions (i.e., -A Freeze, E- Freeze, etc.) resulting from actions taken must be resolved following normal procedures. (4) Valid return is a mixed entity, TP A (CN owner) posted first, You can resolve UPC 126 0 or TC 971 AC 129 following IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistant Center (TAC) Assistors. Review the TPP IRM for your case scenario. Disregard phone specific procedures. Note: These returns have already been through the TPP process. After the TPP issue has been resolved, refer to IRM 21.6.2.4.2, Mixed Entity Procedures, for remaining actions to resolve the case. (5) Valid return is a mixed entity, TP B posted first and the return must be reprocessed to a different TIN, The return must go through the normal TPP process on the correct TIN. Refer to IRM 21.6.2.4.2, Mixed Entity Procedures. Note: Previous authentication on an incorrect TIN does not apply. (6) Valid return is a mixed period, The return posted as TC 150 or TC 976 and AMS reflects the TP has already authenticated, You can resolve UPC 126 0 or TC 971 AC 129 following procedures in IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistance Center (TAC) Assistors. These returns have already been through the normal TPP process. Disregard phone specific procedures. (7) Valid return is a mixed period, The return posted as TC 977 or the TP has not authenticated, and IDTVA can make a determination, You can resolve UPC 126 0, or TC 971 AC 129 following IRM 25.25.6.5, Responding to the Taxpayer and Case Resolution for the Taxpayer Protection Program (TPP) Telephone Assistors and Taxpayer Assistance Center (TAC) Assistors, procedures. Disregard phone specific procedures. (8) Valid return is a mixed period, The return posted as TC 977 or the TP has not authenticated, and IDTVA cannot make a determination, Follow IRM 21.5.6.4.9, E-Freeze, or IRM 21.5.1.4.4.1, Unresolved Taxpayer Protection Program (TPP) Issues for Correspondence and Loose Forms, as applicable. (9) There is a TC 150 return posted, an unpostable TC 971 AC 111, and a TC 971 AC 506 with MISC "WI AM OTHER" or "WI PRP OTHER1" , The TC 150 DLN and TC 971 AC 111 MISC DLN match, and AMS notes indicate an ID Theft determination was made, and There is no TC 976/977 return (-A Freeze). Accept the determination made. Input an adjustment to back out the invalid TC 150 return. Follow the applicable procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. Do not input another IDT indicator. Exception: If a Form 14039 was submitted by the taxpayer, input a TC 971 AC 501. Issue a closing Letter 4674C, if necessary. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. (10) There is a TC 150 return posted, an unpostable TC 971 AC 111, and a TC 971 AC 506 with MISC "WI AM OTHER" or "WI PRP OTHER1" , The TC 150 DLN and TC 971 AC 111 DLN match, and AMS notes indicate an ID Theft determination was made, and There is a TC 976/977 return (-A Freeze). Accept the determination made for the TC 150 return. Determine if the TC 976/977 is a valid return. If the TC 976/977 is a valid return, follow the applicable procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. If the TC 976/977 is not a valid return, follow the applicable procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. Do not input another IDT indicator. Exception: If a Form 14039 was submitted by the taxpayer, input a TC 971 AC 501. Issue a closing Letter 4674C, if necessary. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. For cases/transcripts with RIVO Involvement, see the table below. Reminder: If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. If And Then (1) Return was erroneously abated by RIVO, There is NO IDT and the ASED is within 90 days of expiration, Obtain lead/manager approval per note below. Reverse all IDT indicators. Input remarks on CII and open control base using "PROMPT2IVO" , category code "TPRQ" , status code "A" , and IDRS number "1487755555" to RIVO. (2) Return was erroneously abated by RIVO, There is IDT involvement (e.g., MFT 32, Voided/Deleted) and the ASED is within 90 days of expiration, Obtain lead/manager approval per note below. Complete IDT procedures, as applicable. Input remarks on CII and open control base using "PROMPT2IVO" , category code "TPRQ" , status code "A" , and IDRS number "1487755555 " to RIVO. (3) Return was erroneously abated by RIVO, There is NO IDT involvement and the ASED has expired, Obtain lead/manager approval per note below. Reverse all IDT indicators, Input remarks on CII, "Account backed out as IDT in error by RIVO. Barred assessment" and open control base using" BARRED2IVO" category code "TPRQ" , status code "A" , and IDRS number "1487766666" to RIVO. (4) Return was erroneously abated by RIVO, There is IDT Involvement (e.g., MFT 32, Voided/Deleted) and the ASED has expired, Complete IDT procedures, as applicable. Input remarks on CII and open control base using "PROMPT2IVO" , category code "TPRQ" , status code "A" , and IDRS number "1487755555" to RIVO. (5) The account was erroneously abated by RIVO after the account was adjusted as an Invalid/Valid, There is IDT involvement and the ASED is within 90 days or has expired, Do not refer the case to RIVO. Follow IRM 25.23.2.5, Statute Protection, procedures. (6) The return was: Archived, Deleted, or Moved to MFT 32 in error, Follow procedures in IRM 25.23.4.15, MFT 32 Cases - Moved in Error. Note: Before opening a control base to RIVO and closing your CII case, you will need lead/manager approval. Prior to requesting approval, the CSR/TE must input a case note of their determination on CII. The lead/manager cannot concur with a determination that is not posted on the case. Note: If the lead and/or manager concur with your determination they will need to send an encrypted email to the RIVO mailbox (≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡) with the subject line "Expedite Statute Case." In the body of the email, you should include the social security number, tax period and the ASED of the case.

# Identity Theft with Offsets

25.23.4.10.3 (10-01-2020) Identity Theft with Offsets A taxpayer's overpayment is required to be applied to any outstanding Federal tax debt, Federal non-tax debt, child support, Treasury Offset Program (TOP) debt, State income tax obligation, or Unemployment Compensation prior to being refunded per IRC 6402(a), (c), (d), (e), and (f). A tax offset occurs when a refund is applied to an outstanding IMF, BMF, or NMF liability. A refund will be applied as a TOP offset after verification of no Federal tax debt when a Federal non-tax debt has been identified. When an identity theft case includes tax offsets and/or TOP offsets, refer to the following subsections for specific procedures to address the offsets while correcting the taxpayer's account: IRM 25.23.4.10.3.1, Identity Theft with Tax Offsets IRM 25.23.4.10.3.2, Identity Theft with TOP Offsets

# Identity Theft with Tax Offsets

25.23.4.10.3.1 (10-01-2023) Identity Theft with Tax Offsets Internal Revenue Code IRC 6402(a), (c), (d), (e), and (f) require a taxpayer's overpayment to be applied to any outstanding Federal tax debt, child support, Treasury Offset Program (TOP), State income tax obligation, or Unemployment Compensation prior to crediting the overpayment to a future tax or issuing a refund. This application of a tax overpayment is called a refund offset. Refund offsets to Federal tax debts are called tax offsets. Tax offsets may be the taxpayer's first indication they are a victim of Identity Theft (IDT). Example: (Income or employment related IDT): The taxpayer files their 2018 return expecting a refund. The taxpayer later receives a notice advising them of their refund being applied to a Federal tax debt for tax year 2016. The taxpayer calls for additional information and learns that income earned by someone else was reported for tax year 2016 which resulted in an AUR assessment. Example: (Refund related IDT): The taxpayer files their 2018 return expecting a refund. When the taxpayer calls to check on the status of their refund, they are informed it has been applied to a balance owed for the 2012 tax return filed. The taxpayer submits Form 14039, Identity Theft Affidavit explaining the first time they filed a return was for tax year 2017. Tax offsets must be resolved as part of the corrective actions for Identity Theft and RPM cases and will be treated as payments in most cases. For more information on credit availability for refund or offset, see IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF), for procedures related to credits that are not refundable and credits that are refundable but have been moved to XSF in error. Do not input a tax offset reversal unless criteria in (4), (5), or (6) is met. Exception: When the tax offset is from a refund determined to be created by an invalid return, that credit must be returned to the originating module as part of the IDT resolution for that impacted year. For example, the TY 2019 return is determined to meet nullity criteria, and the refund from that return was offset to pay a balance owed for TY 2015. The offset must be transferred from TY 2015 to TY 2019 as part of correcting the TY 2019 IDT issue. The Collection Statute Expiration Date (CSED) is the expiration of the time period established by law to collect taxes (generally 10 years from the 23C date). Once the CSED has expired, tax offsets cannot be applied to the balance owed. When a tax offset has been applied to a module after the CSED expired, follow the procedures in the table below: Caution: Review the posting cycle of the tax offset to verify it was applied after the expiration of the CSED before transferring the credit to the original module. If the tax offset posted before the CSED expired, the credit must not be moved. Refunds applied before the CSED expired will be addressed on the module they offset to following paragraph (3) above. Example: Form 14039 is received on May 2, 2019. Tax year 2008 is the impacted year. A determination of one return IDT was made. Through research you find the valid taxpayer's 2015 return was filed by April 18, 2016 and the refund offset to the balance owed for tax year 2008. The CSED for tax year 2008 is April 15, 2019, and the offset was applied to the balance in cycle 201617 (April 22 - April 28, 2016). Because the offset was applied to the balance before the CSED expired, it would not be returned to the tax year 2015 module. Credit availability will be determined following normal statute procedures for payments (i.e., 2 year rule). If And Then (1) The credit is available for refund or offset, The RSED is open, Transfer the credit back to the original module. On the credit side, include TC 570 followed by TC 572 with the appropriate post delay to prevent an offset back to the expired CSED module. Allow the system to refund the credit or offset it to another liability. (2) The credit is available for refund or offset, The RSED is expired, Transfer the credit back to the original module. On the credit side, include TC 570 to prevent offset to the expired CSED module. Issue a manual refund following procedures in IRM 21.4.4.5, Preparation of Manual Refund Forms. (3) The credit is not available for refund or offset, Transfer the credit back to the original module. On the credit side, include TC 570 to prevent offset back to the expired CSED module. Apply the credit to the Excess Collection File following procedures in IRM 25.6.1.7.3.1, Transferring Credit to XSF. When the balance due module is a Married Filing Joint account and the tax offset applied to the balance is from a module that does not reflect both spouses' names, follow procedures in the table below: If And Then (1) The credit is available for refund or offset, The RSED is open, Transfer the credit back to the original module. On the credit side, include TC 570 followed by TC 572 with PDC 2 to prevent offset back to the expired balance due module, if necessary. Allow the system to refund the credit or offset it to another liability, when possible. (2) The credit is available for refund or offset, The RSED is expired, Transfer the credit back to the original module. Include TC 570 to prevent offset back to the balance due module. Issue a manual refund following procedures in IRM 21.4.4.5, Preparation of Manual Refund Forms. (3) The credit is not available for refund or offset, Transfer the credit back to the original module. Include TC 570 to prevent offset back to the balance due module. Apply the credit to the Excess Collection File following procedures in IRM 25.6.1.7.3.1, Transferring Credit to XSF. TAS hardship requests for returning an offset to the originating module must be considered. The CSR/TE assigned the case is responsible for verifying offset reversal criteria is met. When an Operations Assistance Request (OAR) is received requesting reversal of a tax offset, return the offset to the originating module if the offset is the result of a TAS or IRS clerical error. A clerical error is an error resulting from a minor mistake or inadvertence, in writing or copying something on the record. A clerical error is not an error based on substance or judgment. Clerical errors include: Typing an incorrect number Transcribing a word incorrectly Misdirecting a form Sending a form to a nonworking fax machine Example: The TY 2017 module reflects a balance owed, and the taxpayer has filed Form 14039. The taxpayer meets hardship criteria and contacts Taxpayer Advocate Service (TAS) for assistance. The Case Advocate receives documentation supporting the taxpayer's economic hardship and submits an Offset Bypass Refund (OBR) request prior to the TY 2018 refund being applied to the TY 2017 balance owed. The OBR request includes transposed numbers in the taxpayer's TIN. The Case Advocate is contacted for a corrected request which is received after the TY 2018 refund was applied to the TY 2017 balance. Because the error made is clerical in nature, the offset will be returned to the TY 2018 module to be refunded to the taxpayer.

# Identity Theft with TOP Offsets

25.23.4.10.3.2 (06-07-2024) Identity Theft with TOP Offsets Service-wide guidance for addressing accounts with a TOP offset is located in IRM 21.4.6.4, Refund Offset Research. There are two types of refund offsets: Federal tax offset Treasury Offset Program offset (effective 01/11/1999) Bureau of the Fiscal Service initiates refund offsets to outstanding federal agency debts or child support, State Income tax obligations, and Unemployment Compensation debts. These offsets appear on the module as: TC 898 or TC 971 AC 598 (manual input of TOP offset record) with an Offset Trace Number (OTN), an offset amount, and a debtor-TIN field, if the offset is secondary spouse OTN - Starting with 1 indicates primary taxpayer debt OTN - Starting with 2 indicates secondary taxpayer debt Command Code (CC) INOLE contains debt liability indicators based on information received from the Bureau of the Fiscal Service. The indicators are used to identity a Federal tax debt TOP debt, or both. You must thoroughly research for any outstanding Federal tax or TOP debts. Always attach the INOLES for both spouses identifying the debt indicator at the time the case is worked. Include BMF screens when there is an X-REF EIN. The debt indicators are: (I) IRS Debt Note: The (I) indicator is not always set for all Federal tax debts. To determine if there is an outstanding Federal tax debt, you must also research Command Code (CC) IMFOL, CC BMFOL, and/or CC TXMOD as well as CC INOLES even on "N" indicator cases. (F) Bureau of the Fiscal Service TOP Debt (B) Both IRS and Bureau of the Fiscal Service TOP Debt (N) No Debt Note: The IAT Results IS screen may respond with a debt indicator "N" when an invalid Social Security Number (SSN) indicator follows the Taxpayer Identification Number (TIN). The IAT Tool is designed to research CC INOLET when the invalid indicator is present. If CC INOLET does not display a debt indicator, then the IAT Results IS screen display the "N" . Additional research is needed if the secondary TIN is invalid. The Department of the Treasury (Treasury), Bureau of the Fiscal Service (BFS), amended its regulation governing the offset of tax refund payments to collect past-due child support obligations. This change limits the time in which Treasury may reverse a tax refund offset to collect a delinquent child support debt to six months. To address this change, IRS must limit the time to reverse a child support offset to 5 months (150 days) from the refund payment date. To determine the date of offset, use the RFND-PYMT-DT associated with the TC 846/840. The 5-month limit allows for internal system processing of the offset reversal request (TC 766 with an Offset Trace Number - OTN). Before reversing any offset to Office of Child Support Enforcement (Agency Codes 1 and/or 2), see IRM 21.4.6.4.2.4, Child Support TOP Offsets. Offsets that occur during processing year 2016 and beyond will post with the Agency and Sub-Agency code. If the Agency code is "1" or "2" , the offset is for a delinquent child support debt and the 5 month limitation rule applies except for a Form 8379, Injured Spouse Allocation. See Document 6209 Section 5, Debtor Master File, for Office of Child Support Enforcement Agency and Sub-Agency codes. Offsets due to delinquent child support occurring during processing years 2012-2015 will be identified by the posting of Transaction Code (TC) 971 Action Code (AC) 126. The Agency Code, OTN, and offset amount will be identified in the MISC field. Offsets due to delinquent child support prior to 2012 will not have any indicators identifying which agency the refund offset to. Contact the TOP liaison to identify the agency code(s). For all TOP Offsets involving Identity Theft, follow the guidance in IRM 21.4.6.5.1.2.4, TOP Offsets Involving ID Theft and ID Theft with Fraudulent Returns. Input TC 470, as needed, to prevent balance due notices from generating while the case is being worked. If TC 470 is input, TC 472 must also be input when the valid taxpayer will have a balance owed after the identity theft issue is resolved. Include a post delay code with the TC 472 if input at the same time as TC 470. When resolution of the identity theft issue requires reversal of a TOP offset that is more than 6 years old, contact the TOP offset Liaison, per IRM 21.4.6.5.1.2.4(5), TOP Offsets Involving ID Theft and ID Theft with Fraudulent Returns, and input the adjustment to correct the account. Once all required IDT account actions have been completed, the IDT control can be closed on CII. It may take 180 days or longer for the TC 700 to post. A monitoring control on IDRS with the Activity "PNDMRR/###" and Category "MISC" will be opened by the assigned employee. A manual reversal is required when you have an IMF/BMF offset which was sent to Bureau of the Fiscal Service in error and cannot be reversed with a TC 766 (IRS reversal) or TC 899 (Bureau of the Fiscal Service reversal). Once the TOP/DMF Manual Reversal Request Form has been submitted and all required ID theft account resolution actions are completed, close the CII case. It may take 180 days or longer for the TC 700 to post. A monitoring control with the Activity "PNDMRR/###" and category "MISC" will be opened by the assigned employee. Refer to IRM 21.4.6.5.8.2, Manual Reversal of TOP Offset, for additional guidance. If the manual reversal is not posted or pending on IDRS after 180 days, follow up with the TOP liaison.

# Identity Theft and Restitution

25.23.4.10.4 (10-01-2020) Identity Theft and Restitution When restitution is court ordered, the taxpayer's account will include references to related modules reflecting the amount of restitution ordered. Modules with restitution references can be identified by: TC 971 AC 18X TC 766 with reference number 337 Do not assume the taxpayer is not a victim of identity theft when restitution references are present. An identity theft determination is made based on the facts and circumstances of the case without consideration of the restitution ordered. If an identity theft determination has been made, contact SB/SE Examination Technical Services (TS) via email at *SBSE TECH Svs Criminal Restitution to inform them of the identity theft claim and determination. Cc: ITVA HQ on the email. Suspend the case for 14 days to allow time for TS to provide a response. See Exhibit 25.23.4-13, Format for Emails to SB/SE Examination Technical Services, for an example of an email that includes the required information listed below: Subject: Identity Theft Claim with Restitution Taxpayer's name Taxpayer's SSN Impacted year(s) Identity theft determination Relevant documentation attached (i.e., Form 14039, Police Report, correspondence, etc.) Determinations of no identity theft (NOIDT) do not need to be provided to TS for review. TS will use the information to evaluate the potential impact on the court ordered restitution and contact Criminal Investigation (CI). TS will provide a response and make any necessary linkage adjustments. Upon receipt of a response or expiration of the 14 day suspense period, follow the procedures in the table below: If Then (1) The response from TS supports the IDT determination made, Take all necessary actions to resolve the account based on your determination. Attach the initial email request and response from TS to your CII case. (2) The response from TS provides information that indicates the taxpayer is not a victim of identity theft, Consider the additional information: If you agree with the information, update your determination to reflect NOIDT, and take all necessary actions to resolve the account. If you do not agree, lead or manager concurrence must be obtained and documented prior to adjusting the account based on your determination. Attach the initial email request and response from TS to your CII case. (3) If you do not receive a response from TS, Resubmit your request, including all required information listed in (4) above. Leave a case note indicating a response was not received from TS and a second request is being submitted. Suspend your case for 14 days. (4) If you do not receive a response to your second request, Take all necessary actions to resolve the account based on your determination. Leave a case note indicating a response was not received from TS. Attach the initial email request and follow-up email request to your CII case.

# Amended or Duplicate Returns and Identity Theft (IDT)

25.23.4.10.5 (12-20-2022) Amended or Duplicate Returns and Identity Theft (IDT) Taxpayers may file a Form 14039, Identity Theft Affidavit submit a Police Report, or send other correspondence indicating they are a victim of identity theft in instances where amended or duplicate returns are involved, including the following scenarios: The taxpayer did not file the TC 150 return and is filing an amended or duplicate return to correct the account. The taxpayer has received a notice and did not file an amended or duplicate return or authorize a preparer to file an amended or duplicate return on their behalf. The taxpayer has not filed a return for the year in question and the account reflects receipt of an original return and an amended or duplicate return. Accounts may reflect a posted or pending TC 977 or TC 976 and/or TC 971 Action Codes indicating an amended return has been received. Refer to IRM 3.11.6.7.21.2, Transaction Code (TC) 971 and Action Codes, for a list of the codes most frequently used by Code and Edit in conjunction with TC 971 to indicate the receipt of an amended return. Refer to the following subsections for procedural guidance.

# Amended or Duplicate Returns and Identity Theft (IDT) - Valid/Invalid

25.23.4.10.5.1 (12-20-2022) Amended or Duplicate Returns and Identity Theft (IDT) - Valid/Invalid There are situations when the taxpayer is claiming identity theft involving an amended or duplicate return filed on their account. Thorough research must be conducted to make an identity theft determination. Reminder: A return filed by the invalid taxpayer that includes income earned by the valid taxpayer may appear to be filed by the valid taxpayer. Return Preparer Misconduct (RPM) claims indicating the taxpayer authorized a preparer to file their original return but did not authorize a preparer to file an amended or duplicate return on their behalf (CAT 1) will be treated as taxpayer-initiated identity theft claims. Resolution of these cases will include nullification of the invalid amended or duplicate return and the input of TC 971 AC 501. Once the amended or duplicate return is determined to be invalid, identify the appropriate process to resolve the account - streamline or non-streamline. See IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, and IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, for additional information. Follow the applicable procedures in the table below based on your determination. Reminder: Do not include an Amended Claims Date (ACD) when inputting adjustments related to amended or duplicate returns for IDT cases. If Then (1) The amended or duplicate return meets nullity criteria, and the account has not been adjusted to the amended or duplicate return figures, Input TC 290 .00 with BS 05, RC 139, and HC 3. Use HC 4 when there is a credit balance on the module that should not be refunded or when issuing a manual refund. Ensure appropriate actions are taken to address all applicable account conditions as described in Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing. Reminder: Returns meeting nullity criteria must not be forwarded to SP for the posting of TC 976. If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. (2) The amended or duplicate return meets nullity criteria, and the account has been adjusted to the amended or duplicate return figures. Adjust the account to the original return figures with BS 05, RC 139, and HC 3. Use HC 4 when there is a credit balance on the module that should not be refunded or when issuing a manual refund. Include a Return Processable Date (RPD) when the previous adjustment included an ACD. Ensure appropriate actions are taken to address all applicable account conditions as described in Exhibit 25.23.4-21, Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing. Reminder: Returns meeting nullity criteria must not be forwarded to SP for the posting of TC 976. If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. (3) If the amended or duplicate return does not meet nullity criteria, The account will need to be adjusted to reflect the information reported on the original return if the module was previously adjusted to the amended or duplicate return figures. Include a Return Processable Date (RPD) when the previous adjustment included an ACD. If the amended return is filed on Form 1040-X, Amended U.S. Individual Income Tax Return create a dummy Form 1040 with the information reported. Note: Form 1040 must be used when processing a dummy return. Forms 1040-A, U.S. Individual Income Tax Return and 1040-EZ, Income Tax Return for Single and Joint Filers With No Dependents will unpost. If there is no posted TC 977 or TC 976 for a Form 1040 identified as an amended or duplicate return, follow procedures in IRM 25.23.4.6.5.2, Unprocessed Documents, to forward the return to SP for the posting of TC 976. If TC 470 CC 90 was input, TC 472 must also be input when the valid taxpayer will have a balance owed. IDTVA-A employees: Follow procedures in IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, and IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, to correct the account. IDTVA Specialty Functions employees: Follow procedures in IRM 25.23.10.5, Post Function Referral Procedures, to refer the case to DITA. Note: If the Exam review was closed based on the invalid amended return filing, see IRM 25.23.10.7.4.2.2, Exam Specialty Technical - IDT Claim Consideration. Reminder: Statute year returns require additional research prior to taking action on an account. Review IRM 25.23.4.9, Statute Processing Considerations, to ensure all applicable statutes are protected.

# Amended or Duplicate Returns and Identity Theft (IDT) - Invalid/Valid

25.23.4.10.5.2 (10-01-2023) Amended or Duplicate Returns and Identity Theft (IDT) - Invalid/Valid Determine if the invalid return meets nullity criteria. See IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, for additional information. Follow the applicable procedures in the table below based on your determination. If Then (1) The invalid return meets nullity criteria, If the valid amended return is filed on Form 1040-X, Amended U.S. Individual Income Tax Return create a dummy Form 1040, U.S. Individual Income Tax Return with the information reported. Note: Form 1040 must be used when processing a dummy return. Forms 1040-A, Individual Income Tax Return and 1040-EZ, Income Tax Return for Single and Joint Filers With No Dependents will unpost. Follow procedures in IRM 25.23.4.6.5.2, Unprocessed Documents, to forward the valid return to SP for the posting of TC 976. After the TC 976 posts, follow the instructions in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. (2) The invalid return does not meet nullity criteria, If the valid amended return is filed on Form 1040-X, create a dummy Form 1040 with the information reported. Note: Form 1040 must be used when processing a dummy return. Forms 1040-A and 1040-EZ will unpost. Follow procedures in IRM 25.23.4.6.5.2, Unprocessed Documents, to forward the valid return to SP for the posting of TC 976. IDTVA-A employees: After the TC 976 posts, refer to IRM 25.23.4.7, Non-Streamline Identity Theft (IDT) Case Processing, and IRM 25.23.4.10.1 , Identity Theft (IDT) with Invalid Returns, for information related to non-streamline case processing. Follow the instructions in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. IDTVA Specialty Functions employees: Follow procedures in IRM 25.23.10.6, Post Function Referral Procedures, to refer the case to DITA. Reminder: Statute year returns require additional research prior to taking action on an account. Review IRM 25.23.4.9, Statute Processing Considerations, to ensure all applicable statutes are protected. Determine if the valid taxpayer is due a refund. Refer to IRM 25.6.1.5, Basic Guide for Processing Cases with Statute of Limitations Issues, and IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim. Apply credits available for refund or offset to outstanding liabilities, if applicable. If necessary, manually refund any allowable amount remaining. Refer to IRM 21.4.4.3(3), Why Would a Manual Refund Be Needed?, and IRM 21.4.4.5, Preparation of Manual Refund Forms, for additional information. Move any credits not available for refund or offset to the Excess Collection File. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF).

# Amended or Duplicate Returns and Identity Theft (IDT) - No Valid Return

25.23.4.10.5.3 (12-20-2022) Amended or Duplicate Returns and Identity Theft (IDT) - No Valid Return Determine if the invalid return meets nullity criteria. See IRM 25.23.4.8.2, Streamline Identity Theft (IDT) Case Identification and Processing, for additional information. Follow the applicable procedures in the table below based on your determination. Reminder: Each return on the account must be considered separately. It is possible to follow nullity procedures for one invalid return but assign an IRSN for another invalid return posted to the same module. If Then (1) There is No Lost Refund, Follow the instructions in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. (2) There is a Lost Refund, Follow the instructions in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. Reminder: Statute year returns require additional research prior to taking action on an account. Review IRM 25.23.4.9, Statute Processing Considerations, to ensure all applicable statutes are protected. Determine if the valid taxpayer is due a refund. Refer to IRM 25.6.1.5, Basic Guide for Processing Cases with Statute of Limitations Issues, and IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim. Apply credits available for refund or offset to outstanding liabilities, if applicable. If necessary, manually refund any allowable amount remaining. Refer to IRM 21.4.4.3(3), Why Would a Manual Refund Be Needed?, and IRM 21.4.4.5, Preparation of Manual Refund Forms, for additional information. Move any credits not available for refund or offset to the Excess Collection File. See IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF).

# Amended or Duplicate Returns and Identity Theft (IDT) - NO IDT Determinations

25.23.4.10.5.4 (05-19-2025) Amended or Duplicate Returns and Identity Theft (IDT) - NO IDT Determinations When a determination of No IDT has been made for an IDT case and the account requires additional actions to fully resolve the module (i.e., DUPF, XRET, MXEN, etc.), take all necessary actions described in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. Note: In the Letter 4674C, advise the taxpayer their return will be processed separately. If an open CII case with the appropriate Category Code does not exist, create a new CII case for the additional required actions. Use the IRS received date of the IDT case. Use the appropriate Category and Program Codes: Caution: DO NOT reassign an existing CII case with the appropriate Category Code to the holding number as instructed in paragraph (4) below.. Note: The list below is not all inclusive. Case Type Category Code Program Code Amended Return XRET 40051 Duplicate Return DUPF 40050 CP36F MXEN 40054 Scrambled SCRM 40052 Exception: When a determination of No IDT has been made because there is an Invalid Joint Election (IJE) issue, and a 2nd return is not present (e.g., XRET, DUPF, etc.) do not create a new CII case. See IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Input a case note documenting the No IDT determination, and link the new case to your original case (i.e., No IDT. Case created to be worked as a duplicate return). Reassign the case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment for Non-IDT Cases located on the IDTVA Hub.

# Identity Theft (IDT) - Previous Action

25.23.4.10.6 (11-06-2024) Identity Theft (IDT) - Previous Action When it appears the identity theft issue was previously worked and the Correspondence Imaging Inventory (CII) images do not include a tax return, refer to the table below to determine the appropriate actions: Caution: Verify all required actions were taken prior to closing a case as previous action. Review CII case notes and/or IDRS to determine if an interim letter was issued to the taxpayer before the case was moved to IDT inventory. If an interim letter was issued and the case will be closed as previous action, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If And Then (1) The CII image(s) of form 14039, Identity Theft Affidavit, police report, and/or correspondence are an exact copy of the documents in the CII case previously worked, All dates (i.e., signature date, IRS received date stamp, fax date/time stamp, etc.) are the same as those on the original documents, Input a CII case note indicating the CII images are duplicates. If a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Note: If only one TC 971 AC 522 UNWORK is present from the initial claim, do not reverse. Only reverse the indicator for the new claim. If an acknowledgement letter was issued after the original CII case was closed, send an IRS apology Letter 0544C/SP. Include paragraph L and the IDT toll-free number 800-908-4490. Use the IDTVA International number for International taxpayers. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (2) The CII image(s) of Form 14039, police report, and/or correspondence are an exact copy of the documents included in the CII case previously worked, The documents include dates (i.e., signature date, IRS received date stamp, fax date/time stamp, etc.) that indicate the documents were signed or received before the date the previous case was closed, Input a CII case note indicating the CII images are duplicates. If a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Note: If only one TC 971 AC 522 UNWORK is present from the initial claim, do not reverse. Only reverse the indicator for the new claim. If an acknowledgement letter was issued after the original CII case was closed, send an IRS apology Letter 0544C/SP. Include paragraph L and the IDT toll-free number 800-908-4490. Use the IDTVA International number for International taxpayers. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (3) The CII image(s) of Form 14039, police report, and/or correspondence are an exact copy of the documents included in the CII case previously worked, The documents include dates (i.e., signature date, IRS received date stamp, fax date/time stamp, etc.) that indicate the documents were signed or received after the date the previous case was closed, Input a CII case note indicating the CII images are duplicates. If a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Note: If only one TC 971 AC 522 UNWORK is present from the initial claim, do not reverse. Only reverse the indicator for the new claim. Issue a closing Letter 4674C/SP advising the taxpayer their identity theft issue was previously resolved. Include the IDT toll-free number 800-908-4490. Use the IDTVA International number for International taxpayers. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (4) The CII image(s) of Form 14039, police report, and/or correspondence provide new/additional information that does not change the determination made, The new/additional information includes dates (i.e., signature date, IRS received date stamp, fax date/time stamp, etc.) that indicate the documents were signed or received before the date the previous case was closed, Input a CII case note indicating the CII images provide new information that does not change the previous determination made. If the previous case was closed with a TC 971 AC 501 or 504 and a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Note: If only one TC 971 AC 522 UNWORK is present from the initial claim, do not reverse. Only reverse the indicator for the new claim. If the previous case was closed with a TC 971 AC 506, input the appropriate TC 971 AC 501 or 504 to ensure the account reflects the receipt of the taxpayer's claim. If an acknowledgement letter was issued after the original CII case was closed, send an IRS apology Letter 0544C/SP. Include paragraph L and the IDT toll-free number 800-908-4490. Use the IDTVA International number for International taxpayers. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (5) The CII image(s) of Form 14039, police report, and/or correspondence provide new/additional information that does not change the determination made, The new/additional information includes dates (i.e., signature date, IRS received date stamp, fax date/time stamp, etc.) that indicate the documents were signed or received after the date the previous case was closed, Input a CII case note indicating the CII images provide new information that does not change the previous determination made. If the previous case was closed with a TC 971 AC 501 or 504 and a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Note: If only one TC 971 AC 522 UNWORK is present from the initial claim, do not reverse. Only reverse the indicator for the new claim. If the previous case was closed with a TC 971 AC 506, input the appropriate TC 971 AC 501 or 504 to ensure the account reflects the receipt of the taxpayer's claim. Input TC 290 .00 with RC 139 and HC 3. Use HC 4 if the module reflects a credit balance that should not be refunded. Issue a closing Letter 4674C/SP advising the taxpayer their identity theft issue was previously resolved. Include the IDT toll-free number 800-908-4490. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (6) The CII image(s) include a Form 14039, police report, and/or correspondence reporting identity theft, The impacted tax year only includes an invalid return moved to MFT 32 or The impacted tax year includes an invalid return moved to MFT 32 and the CN owner's valid return was previously processed, Input a CII case note indicating the invalid return was previously moved to MFT 32. Input TC 971 AC 501 or 506, if appropriate. See IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501. Update your IDRS control with the activity "PRVACTN" . (7) The CII image(s) include a Form 14039, police report, and/or correspondence reporting identity theft, CC TRDBV for the impacted tax year reflects only rejected attempts to file, Follow procedures in paragraph (4) of IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. (8) The CII image(s) of Form 14039, police report, and/or correspondence provide new/additional information, Consideration of the new/additional information supports changing the determination, The case cannot be worked as previous action. Work the case following normal IDT procedures. When it appears the identity theft issue was previously worked and the CII images include one tax return, refer to the table below to determine the appropriate actions: Note: Multiple CII images may be present for correspondence, charge outs, etc., in addition to the tax return. Caution: Verify all required actions were taken prior to closing a case as previous action. Review CII case notes and/or IDRS to determine if an interim letter was issued to the taxpayer before the case was moved to IDT inventory. If an interim letter was issued and the case will be closed as previous action, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If And Then (1) The return in your case is an exact copy of the return in the original case, The account was previously adjusted to the valid return figures, Input a CII case note indicating the account was previously adjusted. Verify all IDT indicators have been addressed. Input any necessary closing indicators, as appropriate. Verify credits remaining on the module have been addressed (i.e., will refund systemically, credit dump, offset to balance due, etc.). Verify the taxpayer will receive an appropriate closing letter based on the case actions previously taken. If an appropriate closing letter was not issued, send a closing letter providing any information the taxpayer did not previously receive. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (2) The return in your case is the result of a document request, The account was previously adjusted to the valid return figures using a different image of the same return or TRDBV information, Input a CII case note indicating the account was previously adjusted. Verify all IDT indicators have been addressed. Input any necessary closing indicators, as appropriate. Verify credits remaining on the module have been addressed (i.e., will refund systemically, credit dump, offset to balance due, etc.). Verify the taxpayer will receive an appropriate closing letter based on the case actions previously taken. If an appropriate closing letter was not issued, send a closing letter providing any information the taxpayer did not previously receive. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (3) The return in your case is an additional return received from the valid taxpayer, The returns are reporting the same figures and the account was previously adjusted to the valid return figures, Input a CII case note indicating the account was previously adjusted. Verify all IDT indicators have been addressed. Input any necessary closing indicators, as appropriate. If there is a -A Freeze, input TC 290 .00 with RC 139 and HC 3. Use HC 4 if the module reflects a credit balance that should not be refunded. Verify credits remaining on the module have been addressed (i.e., will refund systemically, credit dump, offset to balance due, etc.). Verify the taxpayer will receive an appropriate closing letter based on the case actions previously taken. If an appropriate closing letter was not issued, send a closing letter providing any information the taxpayer did not previously receive. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (4) The return in your case is an additional return received from the valid taxpayer, The returns are reporting different figures, The case cannot be closed as previous action. Work the case following normal IDT procedures. If the additional return was filed to amend the figures reported on the valid taxpayer's original return, see IRM 25.23.4.10.5, Amended or Duplicate Returns and Identity Theft (IDT). When it appears the identity theft issue was previously worked and there are no CII images OR the CII images include multiple tax returns, the case cannot be closed as previous action. Work the case following normal IDT procedures. Exception: When all returns included in the CII images are the result of document requests, follow procedures in paragraph (2) table scenario (2) above. If the account has not been adjusted to the valid return figures, the case must be worked following normal IDT procedures. When it appears the identity theft issue was previously worked and the CII image is a transcript, refer to the table below to determine the appropriate actions: Caution: Verify all required actions were taken prior to closing a case as previous action. Review CII case notes and/or IDRS to determine if an interim letter was issued to the taxpayer before the case was moved to IDT inventory. If an interim letter was issued and the case will be closed as previous action, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If And Then (1) If the transcript is the result of an unresolved credit remaining on the module, The credit is no longer on the module, Input a CII case note indicating the credit was previously resolved. If a TC 971 AC 522 UNWORK is present, reverse it with a TC 972 AC 522 IRSERR. Update your IDRS control with the activity "PRVACTN" . Link the case to the original CII case and close. (2) If the transcript is the result of an unresolved credit remaining on the module, The credit has not been addressed, The case cannot be closed as previous action. Follow procedures in IRM 25.23.4.6.6.2, Credit Transcripts Resolution, to correct the account. (3) If the transcript is related to prior RIVO involvement, The case cannot be closed as previous action. Follow procedures in IRM 25.23.4.6.6, Credit Transcripts - IDT6/IDS6, to determine the appropriate actions to take.

# Dependent Related Identity Theft (IDT)

25.23.4.10.7 (10-01-2025) Dependent Related Identity Theft (IDT) Dependent related identity theft (IDT) occurs when: The victim is listed as the primary or secondary taxpayer on an invalid return, The victim is a dependent of their parent/legal guardian and is listed as a dependent on the return of a taxpayer who is not their parent/legal guardian, The victim is not a dependent of anyone but is listed as a dependent on a return filed by an individual who is not their parent/legal guardian. The victim is listed as a dependent on a return determined to be invalid. Note: This includes invalid returns filed under a taxpayer's TIN listing their dependents on the invalid return. Reminder: Establish the entity, if necessary. Refer to IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General, and its applicable subsections for case and account actions that may be required to be taken prior to closing the identity theft issue. When the victim is listed as a primary/secondary taxpayer on an invalid return, follow the procedures in the table below: Reminder: When the individual listed as the primary or secondary taxpayer is the dependent of another taxpayer, input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. See IRM 25.23.4.8.4, Dependent Related Identity Theft (IDT) - General, for additional information. If Then (1) Your research indicates the return in question may be the result of an attempt to obtain the Economic Impact Payment (EIP) through use of the Non-Filer Tool, Review the claim and AMS history items for a statement from the reporting person regarding use of the tool and/or rejected attempts to electronically file their return. If you are unable to determine if the dependent in question used the Non-Filer Tool, attempt to contact the reporting person no less than two times when telephone information is available. Document each attempt in a CII case note. Note: There must be a reasonable amount of time between the two attempts. For example, another call on a subsequent day constitutes a valid second attempt. If you are able to leave a phone message, allow the reporting person 5 business days to return your call. The second attempt should not be made immediately after a first unsuccessful attempt. If the reporting person is an authorized third party or the dependent in question, verify their identity by completing outgoing disclosure. See paragraphs (20) through (22) in IRM 21.1.1.4, Communication Skills, for specific guidance. Then take one of the following actions: If disclosure is passed, advise them you are working the identity theft case and need additional information to complete your review. Ask the following question. Then take the appropriate action based on their response. "Did the dependent input their information in the Non-Filer Tool to receive the Economic Impact Payment (EIP)?" If the response indicates the Non-Filer Tool was used by the dependent or on behalf of the dependent, they are not a victim of identity theft. Explain that use of the tool creates a simple return that is filed electronically. The dependent must file a paper return to report their income, withholding, tax, credits, etc. They may submit a Form 1040-X or a Form 1040 with "EIP Amended" notated on the top. If the dependent does not have a filing requirement and will be listed as a dependent on another taxpayer's return, the individual who is entitled to claim the dependent will need to file a paper return, including all income, exemptions, dependents, tax, and credits they are entitled to. Document your conversation in a CII case note. Continue to step (5). If the response indicates the Non-Filer Tool was not used by the dependent or on behalf of the dependent, they are a victim of tax related identity theft. Thank them for the information, and advise them they will receive a letter informing them of the determination upon completion of your review. Document your conversation is a CII case note. Continue to step (6). If disclosure is not passed, follow procedures in step (4). If the reporting person is not an authorized third party or the dependent in question, advise them you are working the identity theft case and need additional information to complete your review. Ask the following question. Then thank them for the information, and advise them they will receive a letter upon completion of your review. Document your conversation in a CII case note. Then take the appropriate action based on their response. Reminder: You cannot provide any specific account details, but you can accept information provided by this individual. See IRM 21.3.10.3.3, Non-Authorized Third Parties, for additional information and references. "Did the dependent input their information in the Non-Filer Tool to receive the Economic Impact Payment (EIP)?" If the response indicates the Non-Filer Tool was used by the dependent or on behalf of the dependent, they are not a victim of identity theft. Continue to step (5). If the response indicates the Non-Filer Tool was not used by the dependent or on behalf of the dependent, they are a victim of tax related identity theft. Continue to step (6). If directed to this step after contacting the taxpayer, follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Issue a closing Letter 4674C to the dependent. Select paragraphs K (if the reporting person is not an authorized third party), M, t, w, and / (: for international taxpayers). Use paragraph M to include the suggested wording provided in IRM 25.23.4.8.4.3, Dependent Related Identity Theft (IDT) - Determinations. For paragraph t, include the following special paragraph: "When the Non-Filer tool was used to submit information to receive the Economic Impact Payment (EIP), a simple return was filed electronically. You may correct your tax return information by submitting a Form 1040-X or a Form 1040 with "EIP Amended" notated on the top. If you will be listed as a dependent of someone, they will need to file a paper return." Caution: DO NOT select paragraph "u" . Paragraph "u" contains incorrect information advising the taxpayer they cannot opt out of the IP PIN program. See Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for more information on special paragraphs you may use. If directed to this step after contacting the reporting taxpayer, follow normal procedures to conduct research and make a CN ownership determination. For specific instructions related to research and CN ownership determinations, refer to IRM 25.23.4.6, Research, Actions, and Complete Case Analysis - Overview, and IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations. Document your research and determination in a CII case note. After a CN ownership determination has been made, follow the appropriate case processing resolution (streamline/non-streamline) to correct the account. After you have taken the necessary actions to resolve the account, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine if a closing letter must be issued. If you are unable to contact the reporting person by telephone, see IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). If a response is received, follow the applicable procedures in step (4) above based on the information provided. (2) The account reflects RIVO involvement, Refer to IRM 25.23.4.8.2.1, Identity Theft (IDT) with RIVO Involvement. Document your research and determination in a CII case note. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine if a closing letter must be issued. (3) The return in question does not appear to be the result of misuse of the Non-Filer Tool for EIP and there is no RIVO involvement, Follow normal procedures to conduct research and make a CN ownership determination. For specific instructions related to research and CN ownership determinations, refer to IRM 25.23.4.6, Research, Actions, and Complete Case Analysis - Overview, and IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations. Document your research and determination in a CII case note. After a CN ownership determination has been made, follow the appropriate case processing resolution (streamline/non-streamline) to correct the account. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine if a closing letter must be issued. When the victim is a dependent of their parent/legal guardian and is listed as a dependent on the return of a taxpayer who is not their parent/legal guardian, follow the procedures in the table below: If Then (1) The individual(s) entitled to claim the dependent filed a return, The return included the dependent and has been processed, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. Document all account actions in a CII case note. (2) The individual(s) entitled to claim the dependent filed a return, The return did not include the dependent and has been processed, An amended return has not been received, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. If appropriate, include an open paragraph advising an amended return may be filed by the person entitled to claim the dependent to correct the account for the tax year(s) in question. Document all account actions in a CII case note. (3) The individual(s) entitled to claim the dependent filed a return, The return did not include the dependent and has been processed, An amended return has been received, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. If there is a CII case for the amended return and you are trained on the program, contact the assigned employee to reassign the case to you for resolution. If you are not trained on amended returns or there is not a CII case for the amended return, do not request reassignment of the case. Document all account actions in a CII case note. (4) The individual(s) entitled to claim the dependent filed a return, The return included the dependent and has not been processed, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. If the return is included in the CII images, send the return to SP for processing. Refer to IRM 25.23.4.6.5.2, Unprocessed Documents, for additional information. Document all account actions in a CII case note. (5) The individual(s) entitled to claim the dependent filed a return, The return did not include the dependent and has not been processed, An amended return has not been received, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. If appropriate, include an open paragraph advising an amended return may be filed by the person entitled to claim the dependent to correct the account for the tax year(s) in question. Document all account actions in a CII case note. (6) The individual(s) entitled to claim the dependent filed a return, The return did not include the dependent and has not been processed, An amended return has been received, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. If there is a CII case for the amended return and you are trained on the program, contact the assigned employee to reassign the case to you for resolution. If you are not trained on amended returns or there is not a CII case for the amended return, do not request reassignment of the amended return. Document all account actions in a CII case note. (7) The individual(s) entitled to claim the dependent did not file a return, Input TC 971 AC 501 or TC 971 AC 506 OTHER on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. Document all account actions in a CII case note. When the victim is a taxpayer who is not a dependent of anyone and has been listed as a dependent on a return filed by an individual who is not their parent/legal guardian, follow procedures in the table below: If Then (1) The victim filed a return that has been processed or states they filed a paper return that has not completed processing, Input TC 971 AC 501 or TC 971 AC 506 "OTHER" on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. If there is an active tax module for the year in question under the dependent's TIN and there is a valid TC 150 return posted, input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. Document all account actions in a CII case note. (2) The victim has not filed a return or an attempt to e-file was rejected and a paper return has not been filed, Input TC 971 AC 501 or TC 971 AC 506 "OTHER" on the dependent's entity. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501 and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, to determine if the taxpayer has a filing requirement and the appropriate actions to take. If the reporting person is someone other than the dependent or the case is closed with TC 971 AC 506, refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, to determine what closing letters must be issued and what information can be provided to the reporting person. Document all account actions in a CII case note. When the victim is listed as a dependent on a return determined to be invalid (this may be a TP identified or IRS identified case), follow the procedures in the table below: If Then (1) You can identify the victim's valid address, Input TC 971 AC 501 or TC 971 AC 506 "OTHER" on the dependent's entity. Refer to IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, to determine if the taxpayer has a filing requirement and the appropriate actions to take. Issue a closing Letter 4674C. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. Document all account actions in a CII case note. (2) You cannot identify the victim's valid address, Input TC 971 AC 501 or TC 971 AC 506 "OTHER" on the dependent's entity. Refer to and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506, for additional information. Input a TC 971 AC 528 with the MISC Field Code "WI IP DEPND" on ENMOD using CC REQ77. Use January 1st of the current year for the Secondary Date to signify the processing year. Document all account actions in a CII case note.

# No Identity Theft (NOIDT) Determinations

25.23.4.10.8 (10-01-2025) No Identity Theft (NOIDT) Determinations If, after completing all required research and reviewing all information available, you have not confirmed identity theft, refer to IRM 25.23.2.6.6.2, No Identity Theft (NOIDT) Determinations – TC 972 AC 522 NOIDT, for general information regarding unsubstantiated identity theft claims, including a list of scenarios that should not be marked as NOIDT and exceptions for reversing TC 971 AC 522 with a NOIDT literal. Prior to making a No IDT determination, review the taxpayer's statement. If there is any indication of loss of personally identifying information (PII), a request for an Identity Protection Personal Identification Number (IP PIN), or a potential Return Preparer Misconduct (RPM) assertion, refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to consider alternative treatment streams. If you find alternative treatment streams do not apply, the case will be determined No IDT. Refer to the table below for account actions that must be taken: Action Details (1) Reverse Indicator(s) Refer to IRM 25.23.2-11, IMF Only TC 972 AC 522 – Reversal of TC 971 AC 522. Use IDRS Command Code (CC) REQ77 initiated from CC ENMOD to input a TC 972 AC 522 reflecting the appropriate Tax Administration Source Code of: • NOIDT: Taxpayer Identified cases • IRSERR: IRS Initiated cases Caution: If, at the time of case closure, you find the entity has not been flagged with a TC 971 AC 522 UNWORK/PNDCLM/IRSID, you must enter a TC 971 AC 522 UNWORK/IRSID to be reversed with TC 972 AC 522. When a TC 971 AC 522 UNWORK/IRSID is input, the TC 972 AC 522 must be post delayed by one cycle to allow the TC 971 AC 522 UNWORK/IRSID to post first. If a TC 971 AC 501/506 is present and the taxpayer is not a victim of identity theft, the TC 971 AC 501/506 may need to be reversed. See IRM 25.23.2.6.2, Manually Reversing TC 971 AC 506. (2) Address Balance Due If a TC 470 was input to freeze collection notices, input a TC 472 to reverse the hold and resume the issuance of systemic balance due notices. If the module is in a collection status (03, 22, 24, 26, or 58), prepare Form 14394, Identity Theft Collection Alert, and route to IDTVA Specialty Functions (ACSS) for processing. Refer to IRM 25.23.4.12.3, Collection Activity – Resume Collection Actions. (3) Input Adjustment Input TC 290 .00 with RC 139 to indicate the account was reviewed for identity theft. Use HC 3. Use HC 4 to prevent a refund of any remaining credits, when necessary. For a list of exceptions to inputting the TC 290 .00 with RC 139, refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, paragraph (1) exception. Taxpayer Identified Cases Only: Issue a closing Letter 4674. See Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for additional information on selecting closing letter paragraphs. Notify the taxpayer of the No IDT decision. Include the following suggested wording (or similar): "We reviewed your correspondence dated MM/DD/YYYY. We found no indication that identity theft affected the tax periods above." Use the date of the taxpayer's correspondence in place of MM/DD/YYYY. Identify the specific reason(s) for the determination. Include language regarding the taxpayer's right to dispute the NOIDT decision (i.e., providing additional information). If the taxpayer is not currently enrolled in the IP PIN program, advise the taxpayer they may be able to obtain an IP PIN through the opt in process to protect their identity in the future. Caution: If the account reflects a TC 971 AC 527 on CC ENMOD/IMFOLE, do not include paragraph u. The taxpayer is unable to use online self-help options. Instead, include an open paragraph providing information about their option to obtain an IP PIN by submitting Form 15227, IP PIN Application, or scheduling an appointment at their local Taxpayer Assistance Center. For more information about this indicator, see IRM 25.23.2.8.6, Disabled Online Accounts TC 971 AC 527. If the taxpayer has a balance due after the IDT issue is determined to be invalid, include language indicating collection activities will continue. When the account requires additional actions to fully resolve the module (i.e., DUPF, XRET, MXEN, etc.), refer to IRM 25.23.4.10.5.4, Amended or Duplicate Returns and Identity Theft (IDT) – No IDT Determinations. Exception: When a determination of No IDT has been made because there is an Invalid Joint Election (IJE) issue, and a second return is not present (e.g., XRET, DUPF, etc.), do not follow procedures in IRM 25.23.4.10.5.4, Amended or Duplicate Returns and Identity Theft (IDT) – No IDT Determinations, to create a separate case. Note: When the duplicate return is a CP 36F converted in error, refer to Exhibit 25.23.4-4, Identity Theft (IDT) Functional Routing and Referral Chart. Specialty Functions Only: Cases including Compliance issue – Follow functional guidelines to determine if the case needs to be returned to the function that made the referral (i.e., Open AUR cases). Notify them of the No IDT determination. If the taxpayer provides falsified or altered documentation, when returning the case to the Compliance function, suggest the case be referred to the Campus Fraud Coordinator (CFC) as a potential fraud referral. Reminder: If you make a No IDT determination on a case that had Exam involvement, the documentation attached to the claim may be enough for a possible audit reconsideration for Exam. See IRM 25.23.10.6.4, IDTVA Specialties Exam Identity Theft Case Processing, for more information.

# No Reply

25.23.4.10.9 (10-01-2024) No Reply Before proceeding, refer to IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to determine the appropriate action to take.. Caution: When a taxpayer's statement indicates they have lost personally identifying information, the taxpayer is a victim of non-tax-related identity theft. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, for additional information. When directed to follow No Reply procedures, use the following table to resolve the case: Exception: See IRM 25.23.4.3.1, CII and IDRS Case Controls, paragraph (1) for a list of exceptions for inputting the TC 290 .00 with RC 139. If Then (1) There is not enough information in the taxpayer's previously submitted correspondence to make an IDT determination. Send a closure letter. Include the following special paragraph or similar verbiage: Note: If you copy and paste the following paragraph into the letter, do not include the quotation marks. "Since you did not respond to our request for additional information, we are unable to make an identity theft determination and have closed your case. For further consideration, please provide us with the previously requested information. Until then, no further action regarding your identity theft claim will be taken. Collection or Non-Filer actions will resume, if applicable." Use Command Code REQ77 initiated from ENMOD to input a TC 972 AC 522 reflecting a Tax Administration Source Code of NORPLY and the tax year of the identity theft incident. Exception: If, at the time of case closure you find the Entity module has not been flagged with a TC 971 AC 522 IRSID/UNWORK, you must enter a TC 971 AC 522 UNWORK so it can be reversed with a TC 972 AC 522 NORPLY. Reminder: The TC 972 must be post delayed one week to allow the TC 971 to post. See IRM 25.23.2-11, IMF Only TC 972 AC 522 - Reversal of TC 971 AC 522, for additional information. Input a TC 472 to reverse the hold and resume the collection process, if there is a TC 470 that was input to freeze collection notices. Prepare Form 14394, Identity Theft Collection Alert, and route to IDTVA ACSS to resume collection actions if there is a balance due on the alleged IDT tax year or any other year. Input TC 290 .00 with RC 139 to document the identity theft claim. Use HC 3. Use HC 4 to prevent a refund of any remaining credits, when necessary. (2) There is enough information to determine the taxpayer is a victim of identity theft AND the taxpayer did not respond to a request for a return or for information to make a return complete. The identity theft issue must be resolved. Refer to the applicable table in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to determine the next actions based on the facts and circumstances of the case. IDTVA Specialty Teams Only: IDTVA Specialty programs also require consideration of functional guidelines if the case contains compliance issues. Example: A Form 14039 is received indicating their dependent was claimed by someone else. Research shows the individual the claim was submitted for is age 19. Letter 5064C is sent to request proof of legal guardianship. The suspense timeframe has expired, and a response was not received. After consideration of all information available, you are unable to confirm there is identity theft. This case will be resolved following No Reply procedures. Example: A Taxpayer's account contains a TC 150 and a TC 976. The account also reflects a TC 922. An invalid/valid determination is made per IRPTR/IDRS data. The taxpayer's claim indicates a return was fraudulently filed for them but makes no mention of the issues proposed in the CP2000 notice. The TC 976 return doesn't include all of the underreported income. The underreported income appears to be valid, but it is unclear if the underreported income is included in the identity theft claim. A Letter 5064C is sent inquiring why the U/R income was not included on the taxpayer's return. The taxpayer never responds to the Letter 5064C. The case would not be closed as NORPLY even though the taxpayer did not respond to the Letter 5064C. There is still enough information to make determinations on the returns that were filed. The TC 150 would be nullified and the TC 976 processed. Due to the taxpayer not responding, no adjustment would be made to the AUR assessment except to abate any income that is included on the TC 976 return. A Letter 4674C would be sent informing them an AUR assessment remains on their account since they did not respond to our letter. The account would be marked with a TC 971 AC 501. Specialty Resolution only - If the taxpayer provides falsified or altered documentation, when returning the case to the Compliance function, suggest the case be referred to the Campus Fraud Coordinator (CFC) as a potential fraud referral. When reversing an existing IDT indicator and the secondary date is for a tax year that is more than 7 years old CC REQ77 will not accept the year. Prepare Form 4442 and email ITVA HQ using the subject line: Reverse IDT Indicator (or similar). Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Do not suspend your case. For more information, see IRM 25.23.2.3.8.1, Command Code REQ77 Secondary Date and Old Case Year Issue.

# Identity Theft (IDT) - Manual Refunds

25.23.4.10.10 (10-01-2024) Identity Theft (IDT) - Manual Refunds When resolving an identity theft case and the refund cannot be released systemically, it may be necessary to issue a manual refund. Do not issue a manual refund if: A generated refund will be released within two (2) cycles, except under conditions outlined in IRM 21.4.4.3, Why Would a Manual Refund Be Needed? There is a TC 971 AC 664 on the account - either AP, PN or posted. This transaction code indicates that either a direct deposit or paper manual refund has been issued. The most common reasons an identity theft case may require a manual refund are: Reason Scenarios (1) Receipt of a hardship request from the Taxpayer Advocate Service (TAS) using an Operations Assistance Request (OAR) Request for the IDTVA employee to issue a manual refund. Request approval to issue the manual refund. (2) Systemic limitations prevent a normal computer-generated refund Note: The amount of time that will pass before a systemic refund generates is no longer considered a systemic limitation. See paragraph (3) below. Refund Statute Expiration Date (RSED) expired for the module. Some payments and/or credits are refundable while others are not. A systemic limitation is any account condition that will not allow a refund to generate at any time. Procedural actions which extend the period of time that will pass prior to issuance of a systemic refund will not prevent the refund from generating and should not be considered a limitation. A manual refund will not be issued as a result of extended timeframes due to normal processing and posting cycles. Exception: There may be extenuating circumstances which would warrant issuance of a manual refund before a systemic refund generates. Examples of these instances include, but are not limited to, a Congressional request or direction received from headquarters. The input of manual refunds without consideration of systemic account issues can result in erroneous refunds. In addition, improper IDRS controls and lack of required monitoring can result in erroneous refunds. Prior to inputting a manual refund, review the table below for additional considerations: Considerations Details (1) Credit Availability Verify what credits and/or payments belong to the valid taxpayer. Verify if any part of credits and/or payments the valid taxpayer is entitled to were previously refunded or will be refunded based on pending transactions on the module. For more information about credit availability for refund or offset, see IRM 25.6.1.10.3.3.2, Limitations on the Amount of a Claim. (2) Hold Codes When HC 3 is used, the adjustment notice will not generate, and any resulting credit balance will be available for refund or offset. Note: Other account conditions may prevent the refund from being systemically issued. When HC 4 is used, the adjustment notice will not generate, and any resulting credit balance will be held from refunding or offsetting. HC 4 must be used when issuing a manual refund. (3) Post Delay Codes Use of a Post Delay Code will delay the posting of the adjustment/transaction by the number of cycles input as the post delay. Post Delay Codes are necessary to ensure transactions post in the correct order. When an adjustment is post delayed, the credit will not be systemically refunded within two (2) cycles. (4) Override Codes Override Code S may be used to allow a refund to be issued systemically when the module meets a specific set of conditions. Refer to paragraph (4) Table Scenario (1) for additional information. A complete list of Override Codes can be found in IRM 2.4.16-4, Input Screen CC ADJ54. (5) Excess Collections (XSF) Credits being moved from XSF to the module using Form 8765, IDRS Control File Credit Application, must post prior to issuing a refund.\ Credits being moved from the module to XSF using Form 8758, Excess Collection File Addition, do not need to post before issuing a refund. When monitoring for a credit to be transferred to XSF any remaining credit will not be systemically refunded within two (2) cycles. This is considered a systemic limitation. (6) Credit Transfers When transferring a credit to a module that also requires an adjustment, the adjustment must be post delayed by one (1) cycle to ensure they post at the same time. Any remaining credit will not be systemically refunded within two (2) cycles. This is considered a systemic limitation. When transferring a credit out of the module and issuing a manual refund, TC 570 must be input on the debit side to hold the credit and prevent an erroneous refund from being issued before the TC 840 posts. (7) Frivolous Return Program (FRP) Involvement When FRP is involved (-E freeze present), and a manual refund is necessary, include the following remarks: RICS-FRP Approval for manual refund - TC 810/4 Refer to the table below for scenarios you may see when resolving identity theft modules: Scenario Details (1) Override Codes All of the following conditions must be met for an RSED Override Code to be used to allow a refund to systemically generate: There is no hardship request. No payments on the module belong to the invalid taxpayer. All credits on the module are available for refund, and there are no credits that must be moved to Excess Collections (XSF). There are no credits being transferred into the module. The adjustment is not being post delayed. (2) Outstanding balance due Verify the taxpayer has no outstanding tax liabilities that must be satisfied prior to issuing a manual refund. Reminder: When the valid return is MFJ, the necessary research must be completed for both taxpayers. When an outstanding tax debt is identified, a manual refund may only be issued for the amount of overpayment in excess of the balance due. Exception: An offset Bypass Refund (OBR) indicator may be used to bypass outstanding debts when economic hardship exists or based on certain TC 520 closing codes. The availability date of an overpayment is determined by the payment(s) and or credits(s) of which it is comprised. Refer to the table below for additional considerations: Consideration Details (1) Credit interest availability date(s) The refund due to the taxpayer may need to include credit interest. Computation of the availability date of an overpayment is determined by the payment(s) and or credits(s) of which it is comprised. Prepayment credits (payments made before the due date of the return) are deemed paid as of the due date of the return (determined without regard to any extension of time to file) whether the return is timely or late filed. Interest on overpayments based on prepayment credits is generally allowed from the later of the return due date or delinquent return received date. See IRM 20.2.4.4.1, Availability Dates for Overpayments-Payment and Credit Types, for additional information. (2) Multiple refundable payments An overpayment can be made up of multiple payments and or credits and may have more than one availability date. See IRM 20.2.4.4.1, Availability Dates for Overpayments-Payment and Credit Types. Also see IRM 20.2.4.4.2, Availability Dates for Overpayments-Released Credits. Form 5792 is prepared when requesting an IDRS refund. This form cannot be used to issue refunds of $100 Million or more. Forward the manual refund form to the technical lead or designated individual for review, according to the routing instructions for your site. Attach necessary documentation. Refer to the checklist in IRM 21.4.4-3, Manual Refund Checklists. The technical lead or designated individual will: Review the manual refund for accuracy, and Forward to the approver for the final review and signature. Once approved, Form 5792 and all required documentation will be sent to Accounting. Effective June 20, 2023, responsibility for all manual refund monitoring is now performed at the Headquarters level. IDTVA employees issuing manual refunds will also monitor for posting to ensure the taxpayer's identity theft issue is fully resolved. The CII case can be closed with an IDRS control created to monitor when no further account actions are needed. Update the activity for the IDRS control to "MNREF/###" . (### represents the Julian Date). Monitor to ensure the TC 840 and TC 770 (if applicable) post correctly to IDRS.

# Identity Theft (IDT) - Setting the Math Error

25.23.4.10.11 (03-11-2024) Identity Theft (IDT) - Setting the Math Error A math error may be identified during the process of math verifying the valid return. Refer to the following IRMs for detailed explanations of what is and is not a math error: IRM 21.5.4.2, What is a Math Error? IRM 21.5.4.2.1, What is Not Considered a Math Error? A math error will be set when the result of recomputation of figures on a tax return shows more tax and/or less credits than the taxpayer expected resulting in an increased balance due or decreased refund amount. Math verify the valid tax return. Confirm the figures on forms and/or schedules attached are calculated correctly and match the entries on the applicable line of the tax return. Reminder: Various worksheets are available on AMS to assist with verification of tax return figures. When a math error is discovered, recompute the tax and/or credits on the valid return. Use the CII mark-up tools to edit the return with the correct amounts. Input an adjustment using the corrected amounts, include the following: Blocking Series (BS): Use BS 77 if the valid return was electronically filed or BS 78 when the valid return was filed as paper. Source Code (SC): Use SC 6. Hold Code (HC): Use HC 3 to hold the adjustment notice. Use HC 4 to hold the adjustment notice and resulting credit. Reason Code (RC): Use RC 139 and the RCs that best describe the adjustment. Issue an appropriate closing Letter 4674C and/or Letter 474C. Provide a detailed explanation of the changes made. In addition to the explanation, a return showing the correct figures may be included as an enclosure. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. Note: Only issue both letters when there is not sufficient space to address all issues in one letter.

# Identity Theft (IDT) Cases with -E Freeze

25.23.4.10.12 (06-07-2024) Identity Theft (IDT) Cases with -E Freeze The presence of a TC 810 RESP 4 and a -E freeze on the module indicates Frivolous Return Program (FRP) involvement ONLY when one or more of the following are also present: TC 971 AC 089 on the year in question A Civil Penalty MFT 55 with a Penalty Reference Number (PRN) 543 or 666 A TC 420 with or without a TC 300 with Project Code 310 or 313 When the above FRP criteria is met, refer to Exhibit 25.23.4-5, IDTVA Routing Matrix, for instructions to refer the case to FRP. When FRP criteria is not met, follow normal procedures to make an IDT determination. Refer to the table below for actions to be taken on the module(s): Reminder: Each module will be considered separately. Determination Action (1) TC 810 Code 4 (NOT FRP Criteria): IDT determination Resolve the IDT issue following the applicable streamline/non-streamline procedures. Note: When a manual refund is required, the remarks must include: RICS-FRP Approval for manual refund - TC 810/4. Close your CII case. Using IDRS CC ACTON, create a control base for FRP to release the freeze: C#,REQ_FRZRLS,A,FRPI 1486907202,* * will populate the current date. (2) TC 810 Code 4 (NOT FRP Criteria): No IDT determination Follow NO IDT procedures. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Close your CII case. The -E freeze will remain, and the account will continue moving through the FRP process. To advise FRP of the No IDT determination, use IDRS CC ACTON to create a control base for FRP: C#,NO-IDT,A,FRPI 1486907202,* * will populate the current date. Exception: If there is an open Exam issue with project code 1336 or 1505 and tracking numbers 4136-4139, DO NOT create an IDRS control.

# Non-Streamline – Determining When Specific Year Account Information Must Be Moved

25.23.4.11 (06-05-2025) Non-Streamline – Determining When Specific Year Account Information Must Be Moved After determining non-streamline case resolution is necessary, use the guidelines in the following subsections to determine whether posted tax account information for a particular year must be moved and the appropriate method to resolve the case. Moving posted tax account information may not be necessary to resolve the case. When account information must be moved, resolution may require: Merging the account, Following prompt assessment procedures, Reprocessing the return, or Using Form 12810, Account Transfer Request Checklist

# Collection Statute Expiration Date Expired or Imminent

25.23.4.11.1 (10-01-2025) Collection Statute Expiration Date Expired or Imminent The following guidance is applicable for all tax related identity theft categories (i.e., IDT(x), IDS(x), etc.). If all other statute expiration dates have expired and there is no indication of activity or pending activity on the tax module, do not move posted tax account information if: The Collection Statute Expiration Date (CSED) is expired, or The CSED is imminent (has less than 10 months remaining before it expires). If Then (1) All impacted years have an expired or imminent CSED, Send an appropriate closing letter to the valid taxpayer. Do not assign an IRSN to the invalid taxpayer. Do not input any cross-reference indicators or adjustments on the module. Do not issue Letter 4675C to the invalid taxpayer. (2) If there are multiple impacted tax years and some do not have an expired or imminent CSED, For impacted tax years with an expired or imminent CSED: Follow IRM 25.23.4.11.1.1, Identity Theft Allegations on Tax Year 2015 and Prior. For all other impacted tax years (streamline): Follow IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns For all other impacted tax years (non-streamline): Follow IRM 25.23.4.11.2, Tax Year Account Move Conditions.

# Identity Theft Allegations on Tax Year 2015 and Prior

25.23.4.11.1.1 (06-05-2025) Identity Theft Allegations on Tax Year 2015 and Prior Taxpayers may claim identity theft on tax years 2015 and prior in the following scenarios: First time filer and current year refund was offset to a prior year Taxpayer was a minor in the tax year(s) in question Current year refund was offset due to a prior year assessment Research the account(s) to determine whether the taxpayer is a victim of IDT. Although IRPTR data may not be available, internal research must be completed to make a determination. Examples of additional information that may be considered include, but are not limited to, RGS/CEAS RTF data or AUR data (CP 2000). IRPTR data for more current years may be used to support a determination based on consistency of income information. Example: The taxpayer claims they did not file a return for 2012; they were not required to file. In researching IRPTR for more current years, it is determined multiple people are using the SSN for employment purposes. There are IRP documents for the taxpayer which confirms the taxpayer does not have a filing requirement for any of the years. There is a high likelihood the taxpayer did not have a filing requirement for the tax year in question. Research AMS for the CP 2000 or RGS for the RTF data to determine the information filed on the return in question. Research CC IRPTR for available years to determine if the taxpayer had a filing requirement in other years. Note: If IRPTR information is unavailable and the income in question is wages, there is no requirement to completed Form 9409, IRS/SSA Wages Worksheet. Review AMS, CEAS, or the AUR system for taxpayer interaction with the Service, (i.e., telephone history). Research the age of the taxpayer and prior filing history. Ask for additional information that would assist with the determination, if necessary, following procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written). Reminder: If additional information is needed to verify the IDT allegation, you may attempt to call the taxpayer if a contact number is available. Example: The taxpayer claims they were incarcerated. If supporting documentation was not provided and no information can be obtained using CC FTBOL, a determination based on incarceration cannot be made. Request supporting documentation from the taxpayer by telephone and/or by mail to obtain the necessary information. If you are unable to obtain additional information but the identity theft allegation can be verified, allow the claim. Cases where a taxpayer is alleging IDT and the CSED has expired can be identified by the CSED expiration date and a TC 608 on the module. When the invalid return meets streamline criteria, follow normal procedures to resolve the case, unless an exception applies: If the module is in retention and the valid taxpayer has not filed a return, do not bring the module out of retention unless there are payments or offsets that need to be transferred or refunded to the valid taxpayer. Take all actions to update the taxpayer's entity and mark the account with an identity theft indicator, as appropriate. If the module is active and a TC 534 is present, an adjustment input will unpost. If the valid taxpayer did not file the return and there are no payments or offsets that need to be transferred or refunded to the valid taxpayer, follow procedures in IRM 25.23.4.11.3, Action Required If Not Moving Specific Year Account Information. Note: If a TC 534 is present and an adjustment is required because the valid taxpayer filed a return or there are credits to address, prepare and email Form 4442 using the subject line: CSED Expired with TC 534 (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. When the invalid return does not meet streamline criteria, refer to the scenarios below to determine if the invalid return needs to be moved to an IRSN. When the module is not in retention, the invalid return will be moved to an IRSN after the CSED has expired when the valid taxpayer has filed a return that must be processed. When the valid taxpayer has not filed a return, the invalid return will not be moved to an IRSN after the CSED has expired. Refer to IRM 25.23.4.11.3, Action Required if Not Moving Specific Year Account Information. When an account is in balance due status as of the CSED expiration, a TC 608 will systemically credit the account, bringing the balance to zero. In situations where there is an impact, (i.e., a current year refund was offset to a prior year, levy payments, etc.), and the IDT allegation has been confirmed, credits must be resolved following normal procedures. Addressing these credits will create a balance due. As a result, the TC 608 will reset systemically. Note: If the taxpayer is entitled to a refund resulting from payments on the account, a manual refund may be necessary. Refer to IRM 25.23.4.10.10 , Identity Theft (IDT) - Manual Refunds. When Notices of Federal Lien (NFTL) are filed on liabilities, the Service does not notify the credit bureaus. The credit bureaus research public filings and, in certain cases, may place NFTL information on taxpayer credit reports. When a CSED expires, liens are automatically released. The Service is not required to report to the credit bureaus when liens are released. A Form 1099-C, Cancellation of Debt, will not be issued to the taxpayer in this situation. Note: If the taxpayer requests the NFTL be withdrawn, see paragraph (16) of IRM 25.23.10.6.2.2, IDTVA Specialties ACSS Technical Research and Initial Handling Procedures. In situations where a taxpayer may be a victim of IDT for a year where the CSED has expired, research the account to make the determination. If IDT is confirmed, do not adjust the account unless there are payments or offsets that need to be transferred or refunded to the valid taxpayer. Input the appropriate IDT indicator. Refer to IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501, and IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506. Document actions taken in a CII case note. If the taxpayer's correspondence indicates they are impacted due to a Notice of Federal Tax Lien (NFTL), see IRM 25.23.4.12.2, Collection Activity - Form 13794 Additional Actions Required - Lien, for additional information.

# Tax Year Account Move Conditions

25.23.4.11.2 (06-05-2025) Tax Year Account Move Conditions Tax account information for a specific tax year must be moved to or cross-referenced with an Internal Revenue Service Number (IRSN) when any of the following conditions are met: Reminder: If the Assessment Statute Expiration Date (ASED) is expired or imminent on a tax return to be reprocessed, NEVER abate tax on the "from" account prior to posting on the IRSN module. Once reprocessing the return to the IRSN is complete, tax on the "from" module can be corrected. Caution: : The ASED does not apply when the invalid return is determined to be a nullity. The return must be considered valid in order for the ASED to apply. Refer to IRM 25.6.1.6.14, Criteria for Establishing a Statute of Limitations Period, paragraph (3)(b), for additional information. Caution: If there is an indication another area is considering action on the tax year account (e.g., an open control by Exam, Automated Underreporter (AUR), Collections, etc.), contact that area. The tax year may need to be moved based on the action they are taking on the account. Document your contact in a CII case note. The TIN owner has also filed a return for the same tax year, and the tax return amounts have been combined or adjusted. In this case, it is necessary to keep the Common Number (CN) owner's information on the account and move the invalid taxpayer's information to an IRSN. Note: This bullet is referring to tax years in which the valid taxpayer's information has been "mixed" with the invalid taxpayer's information. "Mixed" here means the income amounts were combined, and the tax and any credits were adjusted, if necessary. There is a -C Freeze on the account. A -C Freeze indicates the taxpayer is/was in a Combat Zone and the time period for filing a return for that tax year may have been extended. Caution: The -C Freeze remains on the account even after the taxpayer is no longer in the CZ. When working a case that contains a -C Freeze, additional research is required to determine the taxpayer's CZ status. Research CC IMFOLE for the Combat indicator on Line 11 to determine the correct action to take based on the following: Combat Indicator: 1 – Taxpayer is still serving in a Combat Zone. Any compliance activity (i.e., assessing or collecting tax, etc.) is prohibited. However, other issues or requests for information may be worked. Combat Indicator: 2 – The taxpayer is no longer in a Combat Zone. Follow normal procedures to work the case. There is a balance owed on the CN module. See IRM 25.23.4.11.1, Collection Statute Expiration Date Expired or Imminent, to determine if the module meets the exception for treatment as No Move. The tax year account has an overpayment that must be refunded. The CN owner is due a refund from the module being reviewed. Exception: If the CSED is also expired, an overpayment that must be addressed will not require the invalid return to be moved, unless the CN owner filed a return. The CN owner's return was moved to MFT 32 in error. Resolution of the case will require returning the valid return to MFT 30. If Then (1) None of the conditions in the bullet list above are met, Proceed to IRM 25.23.4.11.3, Action Required if Not Moving Specific Year Account Information. (2) One or more of the conditions in the bullet list above is/are met, Proceed to IRM 25.23.4.11.4, Moving Specific Year Account Information.

# Action Required if Not Moving Specific Year Account Information

25.23.4.11.3 (06-05-2025) Action Required if Not Moving Specific Year Account Information Take the following actions when you have determined it is not necessary to move posted tax account information. Unless specifically noted, the actions listed in this paragraph apply to identity theft cases (i.e., IDT(X) and IDS(X) cases). The bullet items listed here are related to the actions required on the "IRSN" . Input a CII case note detailing the no move determination. Example: Invalid TC 150 meets no move criteria. Establish a name line on the "to" account for the tax year not being moved. Include the name(s), filing status, and spouse's SSN (if applicable) as shown on the return. See IRM 3.13.5.117, Establishing a New Account (TC 000), for additional information. After the name line has posted on the "to" account, input a TC 971 AC 017 on the "to" account to cross-reference to the "from" account. Use the received date of the return not being moved. For MXEN, IDT(X),IDS(X), SCRM, and SSA2 cases, enter the following CII case note, filling in the applicable year: "Tax Year YYYY not filed by TP. See TC 971 AC 001 X-Ref" . Note: If reactivation requires obtaining microfilm, a note on CII is sufficient indicating the location of the cross-reference tax year. Caution: The ASED does not apply on a case that has been determined a nullity. The return must be considered valid (verifiable/non-streamline for IDT) in order for the ASED to apply. Refer to paragraph (3)(b) of IRM 25.6.1.6.14, Criteria for Establishing a Statute of Limitation Period, for additional information. If the return is determined to be valid (verifiable/non-streamline for IDT), an IRSN should be assigned for the invalid taxpayer (Taxpayer B). Take the following additional actions for the tax year(s) that will remain posted on the account. These additional actions listed in this paragraph apply ONLY to MXEN, IDT(X), IDS(X), IDI(X), SCRM, SSA2 cases. The bullet items listed here are related to the actions required on the "SSN" . For the "from" tax year(s) account(s), the tax year(s) account(s) not being moved, change the name line on the tax year(s) to: "NOT FILED] NAMC" . "NAMC" here represents the name control of the taxpayer who owns the SSN. You will type in the name control of the SSN owner instead of typing in "NAMC" . Update the address, if applicable. If the return that posted to the Common Number (CN), on the "from" account tax year has Self-Employment (SE) income, it must be addressed. Input CRN 878/CRN 895 and/or CRN 879/CRN 896 to zero out SE and Medicare income. Input CRN 892/CRN 899 to zero out tip income. If an overpayment on the tax year account not being moved is over one-year old and attributable to the invalid return or payments made by someone other than the valid taxpayer (including levy payments), move such overpayment to excess collections. Note: If the non-owner of the CN has a different valid TIN, this is a mixed entity (MXEN). When a refund should be issued, the tax year account must be moved to the correct TIN. Any overpayment attributable to the non-owner of the CN that has been offset to a Bureau of Fiscal Services debt must be reversed using HC 4. If the overpayment is over one year old, move it to excess collections. A letter must also be sent to the taxpayer who has the FMS debt, notifying them of the reversal. If the BFS offset is over 6 years old, refer to IRM 21.4.6.5.1.2.4, TOP Offsets Involving ID Theft and ID Theft with Fraudulent Returns. Reverse any IRS offsets attributable to the non-owner of the CN. If the overpayment is over one-year old, move the overpayment to excess collections. A letter should be sent to the CN owner informing them of the overpayment reversal when returning the offset to the originating module will result in a balance owed for the valid taxpayer. If the year the offset is being moved from is also impacted by identity theft, a closing letter for that tax year may be required to sufficiently describe actions taken to resolve the account. Reversal of the offset does not need to be addressed in more than one letter. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. If adjusting 2008 and FTHBC was claimed by the invalid taxpayer, see IRM 21.6.4.4.17.4, Manually Adjusting the Recapture Amount, to update the IMFOLF information. Input an appropriate cross reference transaction with the return received date on the "from" account to cross-reference the "to" account. For NMRG cases the "from" account is the tax year on the other side of the No Merge, usually the IRSN. • TC 971 AC 001 - Used when moving the TC 150 return • TC 971 AC 002 - Used when moving the TC 976 return If moving credits to or from excess collections, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Note: If the debit/credit is not posted or pending after 8 weeks, follow local procedures to contact IDTVA P&A to follow up with the appropriate site's P&A.

# Moving Specific Year Account Information

25.23.4.11.4 (06-05-2025) Moving Specific Year Account Information When all information on the CN must be moved to an IRSN, and there is no information on the CN belonging to the valid taxpayer, the account may be merged. See IRM 21.6.2.4.1, Resequencing Accounts, and its subsections for additional information. If there are 180 days or more remaining before the ASED expires, reprocess the return. Refer to the table below for CN and IRSN account actions: CN IRSN Update the ASED, if applicable. Input TC 971 AC 001 (if moving the TC 150 return) or TC 971 AC 002 (if moving a TC 976/TC 977 return). Cross reference the IRSN. Move payments made by the invalid taxpayer to the IRSN module. Adjust the account to reflect the valid return figures, as allowable, if necessary. If the resulting credit cannot be refunded, see IRM 25.6.1.7.3, Excess Collection File (XSF) and Unidentified Remittance File (URF). Establish/update the entity under the IRSN. Input TC 971 AC 017. Cross reference the CN. Reprocess the return to the IRSN. See paragraph (3) below. Create a control base to monitor for posting of the reprocessed return. Allow the math error and normal collection processes to address any balance due issues resulting from the reprocessing of the return. If the result of reprocessing the return is a credit balance and the overpayment is one year or older, transfer the overpayment to Excess Collections to prevent unnecessary AMRH transcripts. See IRM 21.2.4.3.10.1, Excess Collections File (XSF) and Unidentified Remittance File (URF) for AMRH. Reminder: Return to IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, for closing actions. To edit a return to reprocess to an IRSN: Notate "IDTVA" in the upper left corner. Circle out the CN and note the IRSN assigned. Edit with Computer Condition Code (CCC) "O" if moving a refund or "3" if not moving a refund. Refer to IRM 21.5.2.4.23.7, Coding and Editing Procedures, for additional editing requirements. If there are less than 180 days remaining before the ASED expires, refer to procedures in IRM 25.23.4.9.1 , Statute Imminent Assessments for IDT Cases. Caution: The ASED does not apply on a case that has been determined a nullity. The return must be considered verifiable/consistent with the taxpayer's filing history (non-streamline for IDT) in order for the ASED to apply. Refer to paragraph (3)(b) of IRM 25.6.1.6.14, Criteria for Establishing a Statute of Limitations Period, for additional information. Reminder: If the tax year account is within 180 days of the ASED, DO NOT abate tax on the "from" account prior to the tax being posted on the "to" account. Once the return has been reprocessed and the tax information has posted, or a prompt assessment has been made on the "to" account, the "from" account may be backed out to the correct amount. Reminder: If the ASED is expired, NEVER abate tax on the CN account or attempt to reprocess the return. If moving posted tax account information and the ASED is expired, follow procedures in IRM 25.23.4.11.4.1, Manual Account Transfers - Form 12810.

# Manual Account Transfers - Form 12810

25.23.4.11.4.1 (06-05-2025) Manual Account Transfers - Form 12810 Verify any of the account conditions are met, as applicable, in IRM 25.23.4.11.2, Tax Year Account Move Conditions. Note: For general information when the tax year account must be transferred via Form 12810, see IRM 25.6.1.9.9.3, Correct Records on Expired Statute Periods. Reminder: If all other statute expiration dates have expired and there is no indication of activity or pending activity on the tax year account, do not move an incorrectly posted tax year if the Collection Statute Expiration Date (CSED) is expired or imminent (will expire in less than 10 months). See IRM 25.23.4.11.1, Collection Statute Expiration Date Expired or Imminent. Refer to the table below for manual account transfer scenarios Reminder: When multiple invalid returns are present, each return must be considered and addressed separately. Resolution of the CN account may include any combination of streamline and/or non-streamline scenarios. : Scenario Actions (1) One Invalid Return Complete Form 12810 to move the invalid return. Attach the completed form to your CII case. See paragraphs (3)-(5) below. Open a monitor control base on the IRSN account. See paragraph (7) below. After the tax account information has posted on the IRSN module, input the applicable Item Reference Numbers (IRNs) on the IRSN account (i.e., IRN 888, 896, etc.). Input the appropriate cross reference indicators: CN: TC 971 AC 001 cross referencing the IRSN. IRSN: TC 971 AC 017 cross referencing the CN. (2) Invalid/Valid Complete Form 12810 to move the invalid return. Include TC 402. Attach the completed form to your CII case. See paragraphs (3)-(5) below. Open monitor controls for the CN and IRSN accounts. Monitor the CN account for the posting of TC 402. See paragraph (7) below. After TC 402 posts, correct the CN module. See paragraph (6) below for additional information. After the tax account information has posted on the IRSN module, input the applicable Item Reference Numbers (IRNs) on the IRSN account (i.e., IRN 888, 896, etc.). Input the appropriate cross reference indicators: CN: TC 971 AC 001 cross referencing the IRSN. IRSN: TC 971 AC 017 cross referencing the CN. (3) Valid/Invalid Complete Form 12810 to move the invalid return. Include TC 402 if the account was previously adjusted to the invalid return figures. Attach the completed form to your CII case. See paragraphs (3)-(5) below. Open monitor controls for the CN and IRSN accounts. Monitor the CN account for the posting of TC 402. See paragraph (7) below. After TC 402 posts, correct the CN module, if necessary. See paragraph (6) below for additional information. After the tax account information has posted on the IRSN module, input the applicable Item Reference Numbers (IRNs) on the IRSN account (i.e., IRN 888, 896, etc.). Input the appropriate cross reference indicators: CN: TC 971 AC 002 cross referencing the IRSN. IRSN: TC 971 AC 017 cross referencing the CN. Caution: : When multiple invalid returns are present, and they are filed by different taxpayers, they must be considered and resolved separately.This may include assignment of multiple IRSNs and completion of Multiple Forms 12810. Reminder: Return to IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, for closing actions. To prevent delays in processing, confirm the following account details prior to routing Form 12810 and attachments to Accounting: The CN and IRSN modules must be in debit or zero balance. Accounting will reject any requests where either module is showing or will show, once the Form 12810 transfer has been completed, a credit balance. Credit balances must be resolved prior to forwarding Form 12810, whether as a refund to the correct taxpayer, if allowable, or as a transfer to Excess Collections. The entity information on the IRSN must be posted. Any freeze conditions on the IRSN must be resolved prior to initiating the account transfer. Form 12810 includes the following: DLN TIN MFT Tax Period Complete Entity Information IDRS transcript of account Transaction Codes (Include TC 402 if the CN account must be adjusted after posting.) In the Remarks section, input "ID Theft Case" or similar verbiage. Route the completed Form 12810 and attachments to Accounting. Once the account transfer and TC 402 have posted: Input TC 560 on the CN account to update the ASED to 3 years from the received date of the taxpayer's original return, if necessary. Reminder: Ensure the account ASED is adjusted to reflect the appropriate date based on the valid return. When the ASED on the impacted module is expired, a transaction date one day prior to the expiration date must be used when inputting the TC 560 to prevent Unpostable Code 178-2. Note: Input a TC 560 with a DLN-CD of 70 or 99 to prevent Unpostable Code 178-2. Use DLN-CD 70 when correcting the ASED to a later date than the posted ASED. Use DLN-CD 99 when correcting the ASED to an earlier date than the posted ASED. Caution: If the valid taxpayer has filed two returns, and the second return is intended to be superseding, the ASED will be calculated using the received date of the first return. The account will be adjusted to the correct figures on the second return, as allowable. Example: For TY 2019, the timely filed TC 150 return is determined to be invalid and moved to an IRSN. The valid taxpayer files their original return (posted TC 976) on 6/1/2021 reporting income from 2 employers. The valid taxpayer files a second return (posted TC 976) on 7/15/2021 reporting income from 3 employers. This income is verifiable on CC IRPTR. The ASED will be set based on the valid taxpayer's original return on 6/1/2021. The account will be adjusted to the allowable figures on the TC 976 return dated 7/15/2021. Adjust the CN account to the correct return figures, as allowable. Note: An adjustment may not be needed on all CN accounts after the move is completed. When Form 12810 has been submitted, open a monitor control with an activity that indicates the reason for follow up using Category Code "MISC" . Close your case when the only remaining action for the CN is ensuring the account move posts. Refer to the table below for case monitoring information by scenario: Note: If the account move is not posted or pending after 12 weeks, follow local procedures to contact IDTVA P&A to follow up with the appropriate site's P&A. Scenario Monitoring (1) One invalid return After Form 12810 is forwarded to Accounting and all necessary closing actions have been taken, close your CII case. Monitor for posting of the account transfer with a control base on the IRSN account. (2) Invalid/Valid The CII case must remain open while monitoring for the account transfer and TC 402 to post. Once posted, the account may be adjusted, and all remaining closing actions can be taken. (3) Valid/Invalid TC 402 included - The CII case must remain open while monitoring for the account transfer and TC 402. Once posted, the account may be adjusted, and all remaining closing actions can be taken. TC 402 not included - The CII case may be closed with a monitor base controlled on the IRSN account. See the following IRM sections for proper processing of Form 12810: Form 12810 must be processed within a six-day timeframe per IRM 3.17.21.6(1), Master File Account Transfers-Out. Reminder: Ensure you submit Form 12810 to the appropriate Accounting function via EE-Fax or email. Any forms that need to be rejected will be sent back to the originator using an electronic format, by email or EE-Fax. This will prevent unnecessary delays, per IRM 3.17.21.6.1(1), Processing Account Transfers to the Master File (IMF/BMF). The employee assigned to complete the transfer needs to open a control base, using Category Code IRRQ, when it is determined the transfer request will be processed, per IRM 3.17.21.6.1(8), Processing Account Transfers to the Master File (IMF/BMF).

# Collection Activity - Form 14394/13794

25.23.4.12 (03-09-2021) Collection Activity - Form 14394/13794 Form 14394, Identity Theft/RPM Case Collection Alert, is used to suspend/resume collection activity. It is critical that taxpayers are not harmed while IDT claims are being considered. Form 14394 has two purposes: To suspend collection activity while IDT claims or issues are being processed, or To resume collection activity, reinstate an installment agreement, or place in Currently Not Collectible (CNC) status, if there is a balance due when all IDT claims or issues have been resolved. Note: If a Form 14394 was not sent upon receipt of the IDT claim and you will be completing the case that same day, it is not necessary to complete Form 14394 to suspend collection activity. Send only one Form 14394 if a balance remains after the account is corrected to ensure collection activity continues. Form 14394 is not required if the account is not in Master File or Service Center collection status 03, 22, 24, 26, or 58. Caution: A second Form 14394 is not required if there is no tax balance, only penalty and interest on the account. Form 13794, Request for Release or Partial Release of Notice of Federal Tax Lien, is used to release a lien on property and rights to property of a potential IDT victim. The decision to complete a Form 13794 is completely separate from the Form 14394. Input as much information as possible regarding the abatement. You may include specific details such as the date the lien was satisfied or resolved, payment information, and/or a reminder to abate the associated TC 360 lien. Note: The forms should be completed upon receipt, or at the earliest time possible. When a Form 14394 or Form 13794 is completed for an open CII case, the form must be attached as a .pdf. Input a CII case note describing the action(s) taken to address collection activity.

# Collection Activity - Form 14394

25.23.4.12.1 (06-06-2022) Collection Activity - Form 14394 To ensure the taxpayer is not being harmed from a levy, the following items require action: Either master file or service center collection status 03, 22, 24, 26, or 58 Note: Input a TC 470 CC 90 when the corrective adjustment will full pay the balance. Input TC 470 with no CC when the identity theft claim is pending and/or there will still be a balance owed. FPLP, AKPFD, MTLP, SITLP: The case has been in status 22, 24, or 26 AND there is a balance due AND has a TC 971 AC 060-FPLP (Federal Payment Levy Program) or TC 971 AC 601-AKPFD (Alaska Permanent Fund Dividend Levy Program) or TC 971 AC 602-MTLP (Municipal Tax Levy Program) or TC 971 AC 600-SITLP (State Income Tax Levy Program) or TC 670 (Subsequent Payment) DES-PYMT-CD>PC 05 (levy) or 20 (SITLP). Active Levy: Taxpayers indicate they have an active levy against them. Levy payments will have a TC 670 DPC 05 or 20. TC 971 with literals "FPLP" (Federal Payment Levy Program): Cases subject to the FPLP will have a TC 971 AC 062, and levy payments will have a TC 670 DPC 18 or DPC19. If the case did not originate from IDTVA-ACSS, verify a Form 14394, Identity Theft/RPM Case Collection Alert, was sent to IDTVA-ACSS. If IDTVA-ACSS was not notified, follow instructions for issuing Form 14394 as indicated on the form. Reminder: The Form 14394, Identity Theft/RPM Case Collection Alert, should be completed upon receipt, or at the earliest point possible. Exception: Form 14394 is not required to be completed for cases currently being worked by IDTVA-ACSS. The employee working the case will address collection activity, as needed. If the collection status is 26 and the case did not originate from the field, verify a Form 14394 was sent to the Revenue Officer (RO). If the RO was not notified, follow instructions for issuing Form 14394 as indicated on the form. The RO will stop collection activity for the years in question. Do NOT send the case. The determination should be made by the function. You can locate the RO by searching SERP, click the Who/Where tab, then click RO by TSIGN/ZIP/STATE. Enter the first six digits of the RO assignment number. Fax/EE-Fax to the number provided for the RO group. The following transactions indicate a reversal or block from the Federal Payment Levy Program. TC 972 AC 060 (module reversed out of FPLP), TC 971 AC 061 (module blocked from FPLP). If these transactions are present and the only collection action identified is FPLP, no action is necessary and Form 14394 is not required. Note: TC 971 AC 061 expires after 52 weeks. When a posted TC 971 AC 061 will expire and the case will not be resolved prior to expiration, input another TC 971 AC 061 to continue to prevent FPLP actions. Routing of the Form 14394 is required to be documented in a CII or AMS case note. The case note should include the suggested verbiage as follows: "Form 14394 sent to suspend collection activity" , or "Form 14394 sent to continue collection activity, reinstate an installment agreement, or Currently Not Collectible (CNC)" . If the case is determined not to be IDT (NOIDT), notify ACSS, via Form 14394, to resume collection activity. Check the appropriate boxes indicating that the IDT issue has been resolved.

# Collection Activity - Form 13794 Additional Actions Required - Lien

25.23.4.12.2 (07-15-2021) Collection Activity - Form 13794 Additional Actions Required - Lien If there is a TC 582 (Lien Indicator) or TC 360 (Lien Fee Assessment) posted and a full abatement will reverse the tax liability to zero, prepare Form 13794, Request for Release, Partial Release, of Notice of Federal Tax Lien. Form 13794 should be completed and forwarded to the Collection Advisory. Note: Only Collection Advisory has the authority to reverse lien fees (TC 360) on accounts impacted by IDT. Take the following actions when completing the Form 13794: Input as much information as possible regarding the abatement Include the Serial Lien Identification (SLID) Number from the Notice of Federal Tax Lien, if available Check box 9 indicating "Erroneous Lien" Include "ID Theft" in the "Reason" box Fax/EE-Fax or email Form 13794 to the Collection Advisory Unit for the state where the taxpayer currently resides Note: If you do not have access to the Automated Lien System (ALS), include a note asking Advisory to complete the SLID and TSIGN. Collection Advisory contacts can be found under the Who/Where tab on the SERP Home Page on the Advisory Units Contact List. Reminder: When adjusting an IDT account where a NFTL was filed on the account (TC 582 posted) and a tax liability remains after the account has been adjusted the NFTL will remain in place. The NFTL will be systemically released when the account balance is satisfied (zero). The Advisory Unit will review the Notices of Federal Tax Lien (NFTL) filed against the taxpayer using the Automated Lien System (ALS). If all modules on the NFTL are satisfied, Advisory will request the release of the NFTL as an erroneously filed NFTL per IRC 6326(b). The release of the NFTL will reverse the TC 582. Advisory will abate the TC 360 associated with the NFTL filing and issue Letter 544, Letter of Apology - Erroneous Filing of Federal Tax Lien, to the taxpayer. Note: Routing of the Form 13794 is required to be documented in a CII or AMS case note. If it has been more than 30 days since the lien release posted and the taxpayer has any issue with requests for the Notice of Federal Tax Lien (NFTL) to be released, refer the taxpayer to Publication 1450, Instructions for Requesting a Certificate of Release of Federal Tax Lien, to submit a written request for Certificate of release of erroneously filed Notice of Federal Tax Lien. The release date can be calculated based on the posting of the reversal of the TC 582 and TC 360.

# Collection Activity - Resume Collection Actions

25.23.4.12.3 (12-20-2022) Collection Activity - Resume Collection Actions If the case is in either master file or service center status 03, 22, 24, 26, or 58, resume collection activity upon completion of determination and/or case actions when: A "NOIDT" determination is made. Notify ACSS via Form 14394 to resume collection activity. Check the appropriate box indicating that the "NOIDT" determination has been made and there is a remaining tax balance due. Input a TC 472 if a TC 470 was previously input. The action taken will result in a tax balance due. Notify ACSS via Form 14394 to resume collection activity. Check the appropriate boxes indicating that the account has been resolved and there is a remaining balance due. Input a TC 472, if a TC 470 was previously input. Caution: A second Form 14394 is not required if there is no tax balance, only penalty and interest on the account. If Form 9409 was prepared to remove wages, check the boxes for "Levy Source(s) Deleted" and "Other" . In the field for "Other" , include a statement instructing them to see AMS history for deleted sources.

# Identity Theft (IDT) Cases Requiring Special Treatment - Operations Assistance Requests (OARs)

25.23.4.13 (06-05-2025) Identity Theft (IDT) Cases Requiring Special Treatment - Operations Assistance Requests (OARs) The Taxpayer Advocate Service (TAS) is an independent organization within the Internal Revenue Service (IRS), led by the National Taxpayer Advocate, that helps taxpayers and protects taxpayer rights. TAS offers free help to taxpayers when a tax problem is causing a financial difficulty, when they've tried and been unable to resolve their issue with the IRS, or when they believe an IRS system, process, or procedure just isn't working as it should. TAS strives to ensure that every taxpayer is treated fairly and knows and understands their rights under the Taxpayer Bill of Rights. TAS has at least one taxpayer advocate office located in every state, the District of Columbia, and Puerto Rico. Taxpayers have the right to receive assistance from TAS if they are experiencing financial hardship or if the IRS has not resolved their tax issues properly and timely through normal channels. TAS criteria include economic burden, systemic burden, best interest of the taxpayer, and public policy (as determined solely by the National Taxpayer Advocate (NTA)). TAS is responsible for assisting taxpayers who have unresolved problems with the IRS. TAS will issue an Operations Assistance Request (OAR) when a taxpayer's situation meets TAS criteria. Refer to guidance in the following subsections to process OARs, including those OARs associated with unprocessed original returns. OARs may be Economic Burden cases (Criteria 1-4) or Systemic Burden cases (Criteria 5-7). For OARs in Criteria 5-7 that are not marked "Expedite" , follow normal procedures for accepting and working the OAR. Note: OARs in Criteria 5-7 not marked as "Expedite" will not be rejected.

# Identity Theft (IDT) Expedite Operations Assistance Requests (OARs) - (Cases that Meet Economic Burden Criteria 1-4 and Contain Unprocessed Original Returns; TC 976 Documents

25.23.4.13.1 (06-05-2025) Identity Theft (IDT) Expedite Operations Assistance Requests (OARs) - (Cases that Meet Economic Burden Criteria 1-4 and Contain Unprocessed Original Returns; TC 976 Documents TAS will route Expedite Economic Burden Criteria 1-4 OARs (including Spanish) to the appropriate IDTVA-A Adjustments TAS Liaison if they meet one of these conditions: There is an unprocessed original return (no TC 976) that was sent directly to TAS. There is a return on CII but no TC 976 posted and the TC 150 was not filed by the SSN owner. There is no TC 976, but there is a TC 977 generated by a TC 971 AC 010, and the taxpayer's original return is on CII and has no valid return DLN on it. Caution: These procedures are not intended for valid returns moved to MFT 32 in error. This procedure is limited to cases requiring expedite processing due to economic burden. All other IDT cases will be routed using established procedures. TAS will continue to complete the preliminary research on these cases before they are routed and will ensure ALL the following criteria are met: The issue is ID theft The OAR is a Criteria 1-4 Economic Burden Case The case contains an unprocessed original return with the case. See IRM 25.23.4.6.5.2, Unprocessed Documents, for additional information All other preliminary research is completed The unprocessed return has an IRS received date stamp when submitting to IDTVA-A, or is received in IDTVA-A within one day of receipt in TAS. All required documentation must be attached. If there is no IRS received date stamp, the date the OAR is received by IDTVA-A will become the IRS received date for the return. If the return is already on CII, the received date will be the date the return was received in ICT Before processing the case, employees will follow normal procedures to determine CN ownership. If the case does not meet IDT criteria, per IRM 25.23.4, IDTVA Paper Process, or the OAR should have been sent to an area outside of the IDTVA Directorship, the employee will reject the OAR back to the assigned TAS caseworker per the IDTVA SLA Addendum and complete page 2 explaining why the OAR is being rejected. If the case is complete and CN ownership has been validated, employees should adjust the account per procedures in IRM 25.23.4, IDTVA Paper Process. Please update the ASED as required. The IDTVA-A Directorate will work these cases and follow specific guidance provided by SP Accounting to process the manual refund, per guidance in IRM 21.4.4.3, Why Would A Manual Refund Be Needed, and the following: If there is no IRS received date stamp, the date the OAR is received by IDTVA-A will become the IRS received date for the return. A copy of the unprocessed return, depending on your determination, will be submitted along with an IDRS print to show the credit. IDTVA-A will send the original return to SP per local procedures, to expedite the processing of the TC 976 document. See IRM 25.23.4.6.5.2, Unprocessed Documents, for additional information. IDTVA-A will monitor the case for additional closing actions needed (i.e., the posting of the TC 976 that will generate a -A freeze and the posting of the TC 841/TC 840).

# Normal Operations Assistance Request (OAR) Processing

25.23.4.13.2 (06-05-2025) Normal Operations Assistance Request (OAR) Processing IDTVA accepts OARs related to IDT Accounts, IDT Compliance, Fraudulent Return Requests (FRR), and Return Preparer Misconduct (RPM) per the IDTVA SLA Addendum. IDTVA also accepts OARs for other issues if there is an open or closed IDRS control for an IDTVA employee. IDTVA employees will follow OAR guidance in IRM 21.1.3.18.1, Operations Assistance Requests (OARs) Accounts Management Guidelines, to reject or reroute an OAR that is sent to IDTVA in error. Complete Section VI of Form 12412, Operations Assistance Request, when rejecting or returning an OAR to TAS. The IDTVA SLA Addendum also provides guidance on communication with TAS, translation of documents, and other aspects of routing OARs. TAS should submit OARs through group email boxes or fax numbers, not by sending emails to individual employees. If an OAR is emailed to an individual employee, accept the OAR, but provide feedback to the TAS employee and their manager about the proper routing of OARs. TAS should also provide a translation or summary of any documents not in English. If untranslated documents are submitted with an OAR, accept the OAR, but contact the TAS employee for a translation or summary. If necessary, ask for an extended completion date. If the OAR does not list the research completed, the findings of the research, provide enough information to support the determination of identity theft, or the action requested, return the OAR to the TAS employee for proper completion. If necessary, ask for an extended completion date. If the OAR is complete and has not been scanned as a CII image, Form 12412 and all associated documents must be scanned into CII upon receipt. If a Form 14039 is attached, update with TC 971 AC 522 UNWORK and send an acknowledgement letter to the taxpayer if those actions have not already been taken. When assigning IDTVA Specialty Function (Compliance) OARs on CII, follow the table below. If And Then (1) A paper OAR is received in IDTVA-A inadvertently, There is no case open in CII that should be routed to IDTVA Specialty Function (Compliance), Assign the OAR to the Functional TAS Coordinator on CII using Case Priority Code 1 and appropriate Category Code. Note: Be sure all supporting information is on CII before assignment. (2) A paper OAR is received in IDTVA-A inadvertently, There is a CII case previously assigned to IDTVA Specialty Function (Compliance), Link the OAR to the open Compliance case and assign the OAR to the Functional TAS Coordinator, using Case Priority Code 1. Functional TAS Coordinator IDRS numbers are posted in the IDTVA ATAO shared folder. The priority for working OARs is as follows: Criteria 1-4 marked "Expedite" Criteria 5-7 marked "Expedite" Other Criteria 1-4 Other Criteria 5-7 When completing actions required to resolve an Operations Assistance Request (OAR), IDTVA will complete any required adjustments and prepare required forms for Submission Processing functions, including Accounting, as appropriate. The forms will accompany the completed Form 12412, Operations Assistance Request, to TAS. TAS will open a new OAR to the SP function and forward the forms for processing. Accounts adjusted during the completion of an OAR will be monitored for unpostable transactions. Unpostables on OARs will be corrected within 3 days of identification. CII OAR cases must be closed with the appropriate functional category code. Paper OARs must be retained for 90 days after completion.

# Identity Theft (IDT) Cases Processed Incorrectly

25.23.4.14 (02-04-2020) Identity Theft (IDT) Cases Processed Incorrectly There may be instances when an employee incorrectly adjusted a case, or when the return was moved to MFT 32 in error. Actions should be taken immediately to resolve these issues. Follow procedures in IRM 25.23.4.15, MFT 32 Cases - Moved in Error, to correct the account. If it is necessary to reverse a TC 971 AC 501, TC 971 AC 506 or a TC 971 AC 522, refer to the applicable guidance as follows: IRM 25.23.2.6.2, Manually reversing TC 971 AC 501 IRM 25.23.2.6.4, Manually reversing TC 971 AC 506 IRM 25.23.2.6.6, Reversing Unsupported Allegations of Identity Theft

# Identity Theft (IDT) Adjustment Errors

25.23.4.14.1 (11-21-2018) Identity Theft (IDT) Adjustment Errors If you receive any type of correspondence that an SSN owner did not receive their refund, received an incorrect refund amount, or an incorrect balance due notice, because the case was worked incorrectly, (e.g., an employee failed to input a required TC 971 AC 850 causing a second direct deposit into the invalid taxpayer's account), treat the case as priority work. Telephone assistors will send a Form 4442, per IRM 25.23.12.4.1, Telephone Inquiries Regarding Identity Theft Victim Assistance (IDTVA) Tax-Related Cases, paragraph 4. Also see chart below for additional guidance. Exception: If all IDT actions have been taken on the account but you discover through your research the refund was not released due to a -R freeze, you can release the refund. If Then (1) The case meets TAS criteria. See IRM 13.1.7.2, Introduction to TAS Case Criteria, Follow IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines, to complete a referral. Prior to referring the case, review paragraph (1)(e) of IRM 13.1.7.4, Exceptions to Taxpayer Advocate Service Case Criteria. (2) The case does not meet TAS criteria, Reassign to the specific area based on the Identity Theft AM Case Referral/Reassignment Listing located on SERP. Note: The listing may not be all inclusive due to functional and/or organizational unit changes etc., Conduct the necessary research to determine the correct employee to refer case.

# MFT 32 Cases - Moved in Error

25.23.4.15 (03-14-2025) MFT 32 Cases - Moved in Error If an IDTVA employee or another function's employee made an incorrect determination to send a return to MFT 32, the employee who made the error should move the MFT 32 return to the MFT 30 if the following applies: The MFT 32 was caused by SP and no additional account adjustments are needed to resolve the case. The MFT 32 was caused by TPP/RIVO, but you do not have -A freeze on the account or an IDT claim from the TP that requires resolution. Note: To prevent additional delays to our customers, IDTVA employees will move MFT 32 cases back to MFT 30 when they are able to determine the correct CN owner and have a case in inventory that requires immediate attention. Caution: If the case was worked in an IDTVA Specialty Function, the case must be sent to the IDTVA Specialty Function employee for proper resolution. To refer the case, send a Form 4442, Inquiry Referral, to the employee that made the error based on the Form 4442 Referral Chart. The listing may not be all inclusive due to functional and/or organizational unit changes, etc. Conduct the necessary research to determine the correct employee to refer the Form 4442. Refer to the Identity Theft AM Case Referral/Reassignment Listing located on SERP. Monitor the account for posting of the return. Then refer to paragraph (4). To resolve the case, refer to the table below and the additional instructions that follow. Note: When updating the ASED based on the valid taxpayer's return, input a TC 560 with DLN CD of 70 or 99 to prevent Unpostable Code 178-2. Use DLN CD 70 when correcting the ASED to a later date than the posted ASED. Use DLN CD 99 when correcting the ASED to an earlier date than the posted ASED. Reminder: Ensure the ASED on the account is adjusted to reflect the appropriate date based on the new valid return. When the ASED on the impacted module is expired, a transaction date one day prior to the expiration must be used when inputting the TC 560 to prevent Unpostable Code 178-2. If And Then (1) The return posted to MFT 32 was filed by the valid taxpayer (current and immediately preceding year ONLY), There is no return present on MFT 30, Move the valid return to MFT 30. See IRM 25.25.6.7, MFT 32 Procedures - How to Move Identity Theft Returns to MFT 32, and IRM 25.25.6.7.1, Taxpayer Protection Program (TPP) Assistors, Taxpayer Assistance Center (TAC) Assistors, and Identity Theft Victims Assistance (IDTVA) Assistors MFT 32 Reversal Criteria & Procedures, for additional guidance. (2) The return posted to MFT 32 was filed by the valid taxpayer (current and immediately preceding year ONLY), There is a TC 150 return posted to MFT 30 that is an exact copy of the return moved to MFT 32, Move the valid return to MFT 30. See IRM 25.25.6.7, MFT 32 Procedures - How to Move Identity Theft Returns to MFT 32, and IRM 25.25.6.7.1, Taxpayer Protection Program (TPP) Assistors, Taxpayer Assistance Center (TAC) Assistors, and Identity Theft Victims Assistance (IDTVA) Assistors MFT 32 Reversal Criteria & Procedures, for additional guidance. Update the MFT 30 ASED to reflect the received date of the valid taxpayer's original return posted to MFT 32 if the received date is earlier than the received date of the return posted to MFT 30. Input a CII case note indicating the return posted to MFT 30 is a true duplicate of the return posted to MFT 32. If the ASED was updated, notate the action and the IRS received date of the valid taxpayer's original return. (3) The return posted to MFT 32 was filed by the valid taxpayer (AFTER Cycle 47 or archived deleted), There is no return present on MFT 30, Follow IRM 25.25.6.8, Valid Tax Returns That Were Archived - Deleted Returns or Failed Systemic MFT 32 Reversals That Must Be Processed Manually - RIVO and Non-RIVO Employees. (4) The return posted to MFT 32 was filed by the valid taxpayer (AFTER Cycle 47 or archived deleted), ASED is barred and the return has a tax liability greater than zero, Create a dummy return with the following information: All edits must be made in 'Red' pen/pencil only. It is also acceptable to notate all edits on CII images using the annotation tools then underline the changes in "Red." Use Form 1040 for all form types. Add "Dummy Return" at the top of the return. Complete the name, address, filing status and TIN area of the return. Use the taxpayer's most current address of record. Do not use CC IRPTR data as a valid address for the taxpayer. Input zeros on the lines for the adjusted gross income (AGI), the taxable income (TXI), and the tax. Enter "Dummy Return Prepared by IRS - Do Not Correspond for Signature" on the signature line. To prevent the valid return from unposting, edit the return with SPC B in the right margin between the secondary TIN and the Presidential Election Campaign Fund (PECF). designation per the instructions in IRM 3.12.2-4, Special Processing Codes. Edit the return received date on the return, see IRM 3.11.3.8.2.1, Types of Received Dates, for valid handwritten received dates. Use the interest penalty date in CC TRDBV, access code IA is equal to the received date of the return, see IRM 3.11.3.8.2, Determining Received Dates. Send the return to SP for processing, see IRM 3.10.73.6, Batching Unnumbered Returns and Documents. Open a new control base as follows: C#,DUMMY-MMDD,M,BARD 1485066666,* MMDD is the month and day the return is sent to processing. Exception: Submission Processing (SP) employees will work cases with SPIDT criteria, see IRM 21.4.1.4.1.2, Return Found/Not Processed. Special Processing Code (SPC) "T" is also used by SP employees only, see IRM 25.25.6.7, MFT 32 Procedures - How to Move Identity Theft Returns to MFT 32 During Cycles 1 - 46 and Cycles 47 – 52. (5) The return posted to MFT 32 was filed by the valid taxpayer (AFTER Cycle 47 or archived deleted), There is a TC 150 return posted to MFT 30 that is an exact copy of the return moved to MFT 32, Do not take action to move the return posted on MFT 32 to MFT 30. Update the MFT 30 ASED to reflect the received date of the valid taxpayer's original return posted to MFT 32 if the received date is earlier than the received date of the return posted to MFT 30. Input a CII case note indicating the return posted to MFT 30 is a true duplicate of the return posted to MFT 32. If the ASED was updated, notate the action and the IRS received date of the valid taxpayer's original return. (6) The return posted to MFT 32 was filed by the valid taxpayer, There is a TC 150 return posted to MFT 30 that is not an exact copy of the return moved to MFT 32, and through research it is determined the taxpayer is not a victim of identity theft. Consider the return posted to MFT 30 as an amended or superseding return. Update the MFT 30 ASED to reflect the received date of the valid taxpayer's original return posted to MFT 32 if the received date is earlier than the received date of the return posted to MFT 30. Input a CII case note indicating the return posted to MFT 30 is an amended or superseding return and the taxpayer's original return posted to MFT 32. If the ASED was updated notate the action and the IRS received date of the valid taxpayer's original return. (7) The return posted to MFT 32 was filed by the valid taxpayer, There is a TC 150 return posted to MFT 30 that is not an exact copy of the return moved to MFT 32, and through research it is determined the taxpayer is a victim of identity theft. Update the MFT 30 ASED to reflect the received date of the valid taxpayer's original return posted to MFT 32, if necessary. Input a CII case note indicating the taxpayer is a victim of identity theft, and their original return posted to MFT 32. If the ASED was updated, notate the action and the IRS received date of the valid taxpayer's original return in a CII case note. Follow procedures in IRM 25.23.2.5.3, Statute protection - Multiple Returns and MFT 32. Once the assessment has posted, follow procedures in IRM 25.25.6.8, Valid Tax Returns That Were Archived - Deleted Returns or Failed Systemic MFT 32 Reversals That Must Be Reprocessed Manually - RIVO and Non-RIVO Employees, to request the return to be moved from MFT 32 to MFT 30. Monitor the account for posting of the TC 976. Then continue to paragraph (4). After the return has been moved back from MFT 32, take the following actions: When completing reversals, use the correct information provided in Exhibit 25.23.2-9, IMF Only TC 972 AC 506 Tax-Related, Reversal of Identity Theft Case Closure, IRS Identified, for your BOD/Function. Correct the account on MFT 30, and monitor for the release of the -A freeze if the return being transferred from MFT 32 posts as a TC 976. Caution: Moving it back to the MFT 30 may cause the account to go unpostable 126-0 again. All unpostable conditions must be resolved before additional actions can be taken on the account. See IRM 25.23.4.10.2 , Identity Theft (IDT) Cases/Transcripts with RIVO and/or TPP Involvement Resolution Tables, for additional information. Correct the entity, as needed. Notify the SSN owner that they appear to be a victim of IDT, if the notification was sent to the wrong filer. Note: If multiple returns were not received, the TP whose return moved in error may not be a victim of ID Theft. If this is the case, notification is not necessary.

# Form 3245/3809 Reversals

25.23.4.16 (12-20-2022) Form 3245/3809 Reversals In certain circumstances, it may be necessary to reverse previous actions taken that debited the GL 1545 account with the posting of a TC 841 or TC 700 to the tax account. For example, a duplicate TC 841, actual credit has been returned to the module, etc. When it is determined by the originator or employee resolving a case that a TC 841 was initiated in error, a Form 3245, Posting Voucher - Refund Cancellation or Repayment, and Form 3809, Miscellaneous Adjustment Voucher, must be completed. The Form 3245 should be sent to Accounting to reverse the TC 841 with a TC 843 and the Form 3809 will be used to credit the GL 1545 account. Form 3245 and/or Form 3809 must include a brief explanation of the error and the DLN of the TC being reversed must be annotated on the forms. See Exhibit 25.23.4-2, Form 3245 Reversal, and/or Exhibit 25.23.4-3, Form 3809 Reversal, for proper annotations required for Form 3245/3809. In addition to this, 3 copies of Form 3809 and Form 3245 should be submitted when requesting a reversal and the originator should open a control base indicating "843 or 702 request" to prevent duplicate submissions to Accounting. Make sure the TC 841 to be reversed has posted to the taxpayer account before initiating the reversal action. Form 3245 and or/ Form 3809 should be forwarded to the Accounting function for numbering and journaling. The process of reversing the credits may take up to 8 weeks. If the credit cannot be seen as pending or posted, contact IDTVA P&A regarding the delay in processing the request. See IRM 3.17.80.2.7, Duplicate Identity Theft (IDT) TC 841 or TC 700 Posting Identified by Originators, for additional guidance. Note: Form 3245 and/or Form 3809 must be complete and legible for processing or the forms will be rejected back to the originating location. A current TXMOD print must be attached, or the Form 3245/3809 will be rejected back to the originating location. If you identify multiple TC 700s that have posted to the account, input a TC 570 on the account to avoid erroneous refund(s). Note: When multiple TC 700s result in a refund, complete research is needed to determine the recipient. If it's an ID theft account, follow ID theft procedures. If the owner of the EIN/SSN benefited from the refund then follow erroneous refund procedures in IRM 21.4.5.6.1, Account Actions for Category D Erroneous Refunds. For proper routing, refer to Identity Theft AM Case Referral/Reassignment Listing located on SERP. Note: The Form 3245/3809 should be routed to the Service Center (SC) identified by the first 2 digits of the TC 841/700 DLN. If the TC 843 or TC 702 is not posted or pending after 8 weeks, follow local procedures to contact IDTVA P&A to follow up with the appropriate site's P&A.

# Determining Tax Liability/Form 2209 Instructions

25.23.4.17 (12-18-2024) Determining Tax Liability/Form 2209 Instructions This section provides guidance on determining if the taxpayer is required to file a federal tax return, if the taxpayer should file a federal tax return to receive a refund, and when a Form 2209, Courtesy Investigation, is necessary. Note: Determining a taxpayer's filing requirement is not required for current tax year if the return due date (RDD) has not passed. The taxpayer's filing requirement will be determined by considering the following information: Gross income (Gross income includes all income received in the form of money, goods, property and services that is not exempt from tax.) Age Filing Status Caution: When the valid taxpayer is a victim of income related IDT, exclude any income reported that was earned by someone other than the taxpayer when calculating the gross income amount. Reminder: Complete Form 9409 for any wages reported that were not earned by the valid taxpayer. See IRM 25.23.13.3.1, Form 9409 Procedures - IRS/SSA Wage Worksheet, for additional information. Example: CC IRPTR has wage income from ABC Company in the amount of $41,250.00, MNO Enterprises in the amount of $26,800.00, and XYZ Manufacturing in the amount of $5,125.00. You determine the valid taxpayer was only employed by MNO Enterprises. The gross income used to determine if the taxpayer has a filing requirement is $26,800.00. Form 9409 must be completed for the income reported by ABC Company and XYZ Manufacturing. Use the data from IDRS CC IRPTR to calculate the taxpayer's net tax liability. Unless filing information is provided by the taxpayer, tax liability is only determined for the identity theft victim. If both the primary and secondary are victims, tax liability is determined separately for each taxpayer. The IAT Compliance Suite tool is available to assist in determining tax liability. The use of the tool is not mandatory. See the Determination of a Filing Requirement job aid located in the Resources section on the IDTVA Hub for assistance with the IAT Compliance Suite tool for performing the calculation. Note: When calculating tax liability, allow the taxpayer a filing status of single. Allow a self-exemption for tax years 2017 and prior. Exception: Taxpayers who were over 65 at the time the return was due, are allowed the higher standard deduction amount. If it is determined that the taxpayer is due a refund, issue a closing letter instructing the taxpayer to file a return. Advise the taxpayer of the statute of limitations for receiving a refund. See IRM 25.6.1.8, Original Delinquent Returns, for additional guidance on refunds. If the Masterfile status is 02 or 03, input a TC 590 CC 078. Exception: Do not request the return if the RSED has expired and input a TC 590 CC 076 instead. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Do not suspend the case pending receipt of the return. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If the Master file status is 02 or 03, input a TC 590 CC 077. If the valid taxpayer is the secondary taxpayer on a return for the year being reviewed, their filing requirement has been met. If the MFJ return is located and has not completed processing, input TC 594 CC 084 and XREF the primary taxpayer's TIN when it is not present or has been reversed with a TC 592. Do not request a return if the return is six years or more overdue. Example: You are working a case on November 5, 2020. The taxpayer did not file a TY 2010 return. The TY 2010 return was due April 15, 2011. The return is more than 6 years overdue. You would not request a return from the taxpayer for this year. In situations where a fraudulent return has posted to the account as the TC 150 and the SSN owner has not filed (but review of the IRPTR shows income for the SSN owner), complete Form 2209, Courtesy Investigation, per IRM 5.1.8.3, Originating Office Procedure, to alert compliance that the SSN owner has not filed a tax return. Follow normal case processing to ensure the account is flagged with the appropriate ID theft indicators. Refer to job aid on the IDTVA Hub for completing the Form 2209. Exception: Do not send the Form 2209, under any of the following conditions: It is determined the TP does not have a filing requirement. See paragraphs 1 - 4 above. The taxpayer's current address is a service center address. The missing return is for the current filing tax year. If the Group Manager rejects the Form 2209 referral, forward a copy of the rejection to: ITVA HQ. No other action is needed.

# Communicating with Taxpayers

25.23.4.18 (10-01-2025) Communicating with Taxpayers Communications with taxpayers may be associated with research of a case, the closing/resolution of a case or an interim contact to let taxpayers know that IRS needs more time and/or additional information to complete the processing of the request. Communications may be written or verbal (by telephone). Refer to IRM 21.3.3, Incoming and Outgoing Correspondence/Letters, and IRM 21.1.1.4, Communication Skills, for supporting guidance. Note: International taxpayers are those with an address that is not in the 50 states, District of Columbia, or an APO/DPO/FPO address. APO, DPO, and FPO addresses are considered domestic addresses. In support of the commissioner's Multilingual Strategy, review the taxpayer's account for a Mail Filing Requirement (MFR) code and Limited English Proficient (LEP) Indicator before issuing IMF Correspondence. Exception: This does not apply to systemic generated or automated letters. The MFR code is found in position 34 on CC INOLES and displays a 2-digit format (nn). The LEP indicator is found in position 72 on CC ENMOD and display a 3-character format (nnn). The following table provides instruction on determining what language to use when sending a letter. Note: When the letter being issued includes a spouse or is for a confirmed dependent, the language to be used will be based on the primary taxpayer's account and case documentation following the guidance below. IF AND Then (1) The LEP indicator is blank or LEP indicator is "000" The MFR code is not "07" Send correspondence in English. (2) The LEP indicator is blank The MFR code is "07" Send correspondence in Spanish if one is available. Otherwise, send the letter in English. (3) The LEP indicator is 001 Send the correspondence in Spanish if one is available. Otherwise, send the letter in English. (4) The LEP indicator is not blank and is something other than "000" or "001" . See Form 1040 Schedule LEP, Request for Alternative Language Products by Taxpayers With Limited English Proficiency (LEP), for indicators. Translation services are provided at the discretion permitted under Executive Order 14224.Follow directions to get a translation of the letter from Linguistic Policy, Tools, and Services (LPTS). See IRM 25.23.4.19, Requesting Translation of Certain Languages. Note: If Spanish language correspondence is received or the taxpayer marks the "Spanish" box in Section C of the Form 14039, a reply must be issued using the Spanish version of the appropriate C letter, if one is available, even if the LEP indicator and/or MFR Code do not indicate Spanish as the taxpayer's language. See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), if translation services are needed. If providing a response in Spanish that includes an open paragraph, translation of the open paragraph must be included as a CII note. When translation of a required special paragraph exceeds the number of characters allowed, a floating paragraph (*) may be used immediately following the open paragraph to separate the special paragraph into two parts to ensure the taxpayer received all relevant information. Exception: Do not issue the Spanish version of the C letter, if the taxpayer specifically requests to receive the letter in English, or if both the English and Spanish boxes are checked and the comments are written in English. If Spanish is indicated as a language spoken by the taxpayer on a Police Report, issue correspondence in English, unless the report clearly indicates the taxpayer does not speak English or would like to receive all communications in Spanish. When issuing correspondence, potential Married Filing Joint (MFJ) statuses must be considered. Determine if there is a covered relationship between the primary and secondary taxpayers. Covered relationships will result in correspondence addressed to both taxpayers when the impacted module is MFJ. Refer to the table below for potential case scenarios: Determination Account Conditions and Letter Issuance (1) Valid MFJ, The identity theft issue is under the primary TIN. This is a covered relationship. There is no disclosure issue. The letter will be issued under the primary entity to both taxpayers. (2) Valid MFJ, The identity theft issue is under the secondary TIN. The letter will be issued under the secondary entity to only the secondary taxpayer. (3) Invalid Joint Election (IJE). This is not a covered relationship. Address the letter to only the reporting taxpayer. (4) Married Filing Joint Scheme, This is not a covered relationship. Each taxpayer will receive a separate letter. Covered Relationships must be confirmed through internal research and consideration of documentation provided by the taxpayer. Covered relationships include; Spouses - Taxpayers who filed Married Filing Jointly (MFJ) for the impacted tax year when there is no indication of separation based on documentation available and subsequent filing history. Refer to the table below to determine how a closing letter will be issued to additional impacted individuals. Note: This table does not apply to systemic notices (i.e., CP01, etc.). If And Then (1) The taxpayer's statement indicates their spouse may also be a victim of identity theft, The covered relationship can be confirmed, and there is no indication the taxpayers have or intend to separate, Both taxpayers will be informed of the determination and provided any additional information in the closing letter issued from the primary taxpayer's account. (2) You have determined the case is a MFJ Scheme, Invalid Joint Election (IJE), or the relationship status has changed, This is not a covered relationship, Each taxpayer will be notified of the determination and provided any additional information separately. (3) The taxpayer's statement indicates their dependent may also be a victim of identity theft, The dependent is under age 18 and parent/legal guardianship can be confirmed, OR The dependent is age 18 or older and proof of legal guardianship has been received, Issue the closing letter from the dependent's account. (4) The taxpayer's statement indicates their dependent may also be a victim of identity theft, The dependent is under age 18 and parent/legal guardianship cannot be confirmed, OR The dependent is age 18 or older and proof of legal guardianship has not been received, If a closing letter will be sent, issue it from the dependent's account. (5) The taxpayer's statement does not indicate anyone else may be a victim of identity theft, A covered relationship can be confirmed for an additional impacted individual, Resolution of cases for additional impacted individuals will be considered taxpayer initiated. Refer to the table scenario above that best fits the facts and circumstances of the case. (6) The taxpayer's statement does not indicate anyone else may be a victim of identity theft, A covered relationship cannot be confirmed for an additional impacted individual, Unless the individual in question has submitted an identity theft claim, the additional impacted individual's case will be considered IRS identified. Each individual will be notified of the determination and provided any additional information separately. The reporting taxpayer's language preference and account information will not be considered. Refer to paragraph (5) above to determine the appropriate language. (7) There is no taxpayer correspondence, A covered relationship can be confirmed for an additional impacted individual, The cases will be considered IRS identified. If a spouse, both taxpayers will be informed of the determination and provided any additional information in the closing letter issued from the primary taxpayer's account. If a dependent, each individual will be notified of the determination and provided any additional information separately. Refer to paragraph (5) above to determine the appropriate language. (8) There is no taxpayer correspondence, A covered relationship cannot be confirmed for an additional impacted individual, The cases will be considered IRS identified. Each individual will be notified of the determination and provided any additional information separately. Example: A Form 14039 is received stating someone filed a tax return using the taxpayer's name and ITIN. Through research of the account, you determine: •The TC 150 return filed is invalid per IRPTR/IDRS data and lists the true taxpayer's child as a dependent on that return. •The TC 976 return filed is valid and is reporting verifiable income earned under another individual's SSN. •The account of the individual whose SSN is being used for employment purposes is not marked with TC 971 AC 525. •The original taxpayer and their child are both victims of identity theft. The dependent is a covered relationship, and their case will be considered taxpayer initiated. •The other taxpayer is an unrelated third party and is not a covered relationship. This case will be treated as IRS identified. The following subsections contain program specific guidance for communicating with taxpayers.

# General IDTVA Letter Procedures

25.23.4.18.1 (10-01-2025) General IDTVA Letter Procedures All IDTVA will use the following letters when addressing IDT issues. This list is not all inclusive: Letter 5073C, Acknowledgement Letter for Identity Theft Claim (Form 14039, Police Report, or other correspondence), to acknowledge receipt of the IDT claim when CP 01S/CP 01S (SP) is not systemically generated. Letter 5064C, ID Theft-In Process Letter, as an interim letter or to request additional information from the taxpayer. Letter 4674C, IDTVA Closing Letter, as a closing letter when a CP 01, Identity Theft Acknowledgement, will not be systemically issued, when the CP 01 by itself may not be sufficient to explain the actions taken on the account, the CP 01 does not respond to all issues raised by the taxpayer, or the taxpayer did not receive correspondence providing the contact information for the employee assigned to the case. Letter 4675C, Identity Theft - Temporary Number Assignment Letter (For use when an IRSN is assigned), to inform the invalid taxpayer they have been assigned an IRSN. Letter 4402C, ID Theft (Self Identified) - AM AC 504 Notification Letter, as a closing letter when issuing a manual letter for a non-tax-related IDT determination. Letter 474C, Math Error Explained (IMF), as a closing letter when setting a math error. Letter 105C, Claim Disallowed, as a closing letter when fully disallowing a claim. Letter 106C, Claim Partially Disallowed, as a closing letter when partially disallowing a claim. Note: The CII capture function must be used when sending a letter as part of IDT case resolution. Refer to IRM 21.5.1.5.1, CII General Guidelines, for additional information. The IAT Letters tool in the IAT Task Manager must be used to input letters issued for identity theft casework. The tool provides a simple format for selecting the required paragraphs, manually editing the address to the valid SSN owner's information and adding a history item or updating the control base on IDRS. See Exhibit 21.2.2-2, ACCOUNTS MANAGEMENT MANDATED IAT TOOLS, for more information. Note: When sending letters that include open paragraphs, IDTVA employees are encouraged to utilize the IRS Style Guide, Plain Language, to ensure their correspondence is grammatically correct. A determination of whether the case will remain in the function should be made prior to issuing any letters. Due to the possibility of disclosing taxpayer information to an unauthorized individual, acknowledgement letters will not be issued upon receipt of Form 14039, Identity Theft Affidavit, or other acceptable documentation in which the taxpayer alleges they are a victim of identity theft. To exercise caution when corresponding with the taxpayer, the case must be reviewed, and a determination made prior to providing any account information to the claimant. The closing contact will serve as both an acknowledgement of receipt of the taxpayer's documents and communication of the closing resolution. If it is necessary to request information from the taxpayer, the Letter 5064C issued will acknowledge receipt of the claim and request the additional information. A separate closing letter will be sent upon resolution of the case. Exception: If, after making a determination, the case will be suspended awaiting other case actions or will not be closed within five (5) business days Letter 5073C will be issued to acknowledge receipt of the taxpayer's claim. Note: When acknowledging the taxpayer's claim, regardless of which letter is issued, the following information will be included: • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ toll-free number or for international ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (in lieu of the identity theft toll free number), • Name and six-digit extension of the employee assigned to the case, • And the employee's tour of duty as the hours of operation. An acknowledgement letter is not required if any of the following conditions are met: It is determined the case needs to be returned to the referring function. It is determined the case needs to be routed/reassigned to another function and input of Letter 86C is required. See IRM 25.23.4.3.3, Cases Requiring Routing/Reassignment to Other Functions. A Letter 5316C or CP 01S was previously issued to acknowledge the claim. Caution: When the systemic acknowledgement letter was issued to an address that does not belong to the valid taxpayer, an acknowledgement letter must be issued to the valid taxpayer unless another exception applies. A Letter 2645C was previously issued when the case originated as an RPM claim (IDRS Category Codes RPMC and IDII). Another IDTVA function has already issued an acknowledgement letter within the last 582 days. The correspondence has a Form 14157, Return Preparer Complaint, or Form 14157-A, Tax Return Preparer Fraud or Misconduct Affidavit, attached (IDTVA Specialty Functions see paragraph (6) of IRM 25.23.10.2, Case Batching, for additional information). When a letter was issued for a tax year in error, a closing letter is required. Issue a Letter 544C, Apology for IRS Error, for the specific tax year only. If the case needs to be referred to another function, the referring function should issue the Letter 5073C or Letter 86C, whichever is appropriate, as the acknowledgement letter prior to referral. The acknowledgement letter must include the toll-free number 800-908-4490 or, for international taxpayers, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (not toll-free). Example: IDTVA ACS-Support receives a referral from ACS-Support. Through research IDTVA-ACS determines that the account has two impacted tax years. TY 2012 is an impacted tax year for ACS and the TY 2013 has an Exam assessment. Per Exhibit 25.23.4-5, IDTVA Routing Matrix, the case will be worked by IDTVA-Exam. IDTVA ACS-Support will send the acknowledgement letter to the taxpayer before preparing the case to be imaged by ICT. IDTVA-ACS-Support will input on the ICT Batch Cover Sheet as an IDI1, so that the cases will get assigned to IDTVA-Exam. When issuing a letter, use the signature date or the date written on the correspondence from the taxpayer or their authorized representative for the correspondence date. If a date cannot be determined, use the dates listed below in the following order: Postmark or transmission date Service Center Automated Mail Processing System (SCAMPS) digital dates Three days prior to the IRS received date of the case If a case cannot be completed within the number of days specified in the acknowledgement letter, an interim Letter 5064C, IDTVA In-Process Letter, must be sent. Interim letters will need to be issued no earlier than 577 days (minus 5 days from 582) after the IRS received date and should inform the taxpayer when a final response can be expected. Provide a contact name and number for additional inquiries if it was not previously provided or has changed. See IRM 21.3.3.4.2.2, Interim Responses, for additional information. Reminder: Issuing the interim letter prior to 577 days after the IRS received date will add the additional time from that date which could fall within the original timeframe provided in the acknowledgement letter. The time frame given in this interim letter may not exceed 60 days. Example: Today's date is November 16, 2024. Your case is currently 473 days old. Issuing an interim Letter 5064C requesting an additional 60 days to process the case will result in a response being required by January 15, 2025 (when the case is 533 days old). When issuing a Letter 5064C, IDTVA In-Process Letter, as an interim letter or to request additional information/documents, the letter must include the following: The number for the IDTVA Theft toll-free line ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ or, for international taxpayers, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (not toll-free) The name and six-digit extension of the employee assigned to the case Hours of operation - the employee that is issuing the letter will input their TOD as the hours of operation Exception: Employees who do not have a six-digit extension will use the extension of their work leader when issuing the letter. A closing letter must be sent to the taxpayer when all account actions have been completed on a case. Policy Statement P-21-3 guidelines require timely and quality responses to taxpayer correspondence. Exception: Do not issue a closing letter when the entity reflects a Service Center address. Caution: When a No IDT determination is made on a Compliance case, do not provide guidance to the taxpayer to resolve the Compliance issue (i.e., what documentation is needed by the Compliance function, etc.). If appropriate, provide the toll free number for the taxpayer to contact the specific function directly. Caution: When closing a case as previous action, review CII case notes and/or IDRS to determine if an interim letter was issued to the taxpayer before the case was moved to IDT inventory. If an interim letter was issued after the previous IDT case was closed and procedures in IRM 25.23.4.10.6 , Identity Theft (IDT) - Previous Action, do not instruct you to issue a closing letter when resolving your case scenario, a closing Letter 4674C is required to explain the identity theft issue was previously resolved. Reminder: For individuals under the age of 18, Letter 4674C must be sent. Do not include the paragraph that directs them to request an IP PIN using Online Services. See IRM 25.23.2.9.1.2, Opting into the IP PIN Program through the Individual Online Account, for additional information. Taxpayers can be directed to irs.gov.ippin and/or irs.gov.ippinfaqs to obtain general information. A quality response is an accurate and professional communication which, based on information provided: Resolves the taxpayer issues, Requests additional time and/or information from the taxpayer, or Notifies the taxpayer we have requested information from outside the IRS. To ensure the taxpayer receives a quality response, the employee may issue a manual closing letter when a systemic notice will generate. IDTVA employees are encouraged to provide the taxpayer with the best customer service possible by addressing relevant supplemental information the taxpayer may benefit from, including self-help options available on IRS.gov, to allow the taxpayer to make informed decisions. Example: An IDTVA employee may determine the taxpayer would benefit from being provided information about obtaining an IP PIN on IRS.gov. Example: An IDTVA employee may provide the taxpayer with information about locating the appropriate address for submitting a tax return when the taxpayer has a filing requirement and is unable to file electronically due to the presence of an invalid return. For certain case types (e.g., NOIDT, Dependent IDT, etc.) refer to Exhibit 25.23.4-25, Closing Letter Paragraph Selections, for use of special paragraphs when providing the taxpayer with supplemental information regarding IP PINs. Exception: Accounts that reflect TC 971 AC 524 on CC ENMOD/IMFOLE do not require this information to be provided. See IRM 25.23.2.8.4, Locking Individual Accounts - TC 971 AC 524, for more information about this indicator. Caution: DO NOT use paragraph "u" when issuing closing Letter 4674C for ALL case types. Paragraph "u" contains incorrect information advising the taxpayer they cannot opt out of the IP PIN program. See Exhibit 25.23.4-25 Closing Letter Paragraph Selections, for use of special paragraphs. Reminder: IP PIN issues must be addressed in ALL closing letters to the taxpayer(s). Accounts marked with an IDT indicator TC 971 AC 501 will generate a CP 01, Identity Theft Acknowledgement. Refer to IRM 25.23.2.6.1.1, Systemic Actions Taken TC 971 AC 501 Placed on Account, for additional information regarding a TC 971 AC 501 and the CP 01. Accounts marked with an IDT indicator TC 971 AC 504 will generate a CP 01C, Account Flagged for Identity Theft. Refer to IRM 25.23.2.8.1, IMF TC 971 AC 504, for additional information. Exception: CP 01/CP 01C generates only once in a three-year period. If another year was marked with a TC 971 AC 501 within the last 3 years, a Letter 4674C is required to inform the taxpayer their account was corrected. Note: Current programming for the CP 01/CP 01C will generate a copy of the notice to a POA that is on file. If sufficient documentation has been received to validate a POA, but is not yet on file, then issue the POA a closing letter. This ensures the taxpayer's right to retain representation and the POA's right to be informed. Note: If the TC 971 AC 501 is not input prior to cycle 47 of the processing year, an IP PIN/CP01A will not generate for the upcoming filing season. Between cycle 47 and January 1 of the following year, IP PIN information must be provided in a closing letter. Barring any unforeseen circumstances, this additional information will not be required in closing letters issued between January 1 and cycle 47. SERP Alerts should be monitored for information related to IP PINs that may impact this timeframe. Use the special paragraphs in paragraph (13) above in addition to the paragraphs selected for your closing Letter 4674C. Reminder: For taxpayers under age 18 do not direct IP PIN requests to Online Services. Taxpayers can be directed to irs.gov/ippin and/or irs.gov/ippinfaqs to obtain general information. Caution: For potential fraudulent and/or compromised POAs, refer to IRM 21.3.7.5.5.3, How to Report a Compromised or Potentially Compromised CAF Number. When the individual listed on the identity theft inquiry is deceased, refer to IRM 21.3.3.4.16.5, Corresponding on a Deceased or Legally Disabled Taxpayer's Account, to determine the appropriate format for the taxpayer's name and address when sending a letter. Reminder: When establishing or updating the entity is necessary, use a Service Center address when a valid address cannot be identified for the deceased taxpayer. See IRM 3.13.5.66, Campus Address Used Only When Taxpayer Address is Unavailable, for additional information. When the reporting person is not an authorized third party, a Letter 4674C must be sent to the taxpayer. Include paragraph L to inform them of the third-party contact. When the account does not reflect a current Form 2848, Power of Attorney and Declaration of Representative, or Form 8821, Tax Information Authorization, listing the reporting party as a representative or third-party contact for the individual listed as the impacted taxpayer, and you can locate a valid address for the reporting person, issue a closing Letter 0135C to the reporting party. Issue the letter from the reporting person's account. Include paragraphs E, *, and P. For paragraph *, include the following special paragraph: "We will reply directly to the taxpayer listed in your inquiry when we have completed our investigation into the identity theft claim. We won't send you any further correspondence regarding this matter, because our records show you are not authorized to receive confidential tax information for the taxpayer listed in your inquiry." For paragraph P, include the following special paragraph: "We must have a valid Form 2848, Power of Attorney and Declaration of Representative, or a valid Form 8821, Tax Information Authorization, on file to provide you with confidential tax information for this taxpayer. For more information about these forms, visit our website at www.irs.gov/forms-instructions." When issuing a letter, ensure the correct paragraphs are used to inform the taxpayer of the status of their account based upon the facts and circumstances of the case. Also see additional items below: If appropriate, include multiple tax years by manually inputting the tax year in the empty boxes. Up to eight (8) tax years can be input in a Letter 4674C and eight (8) tax years can be input in a Letter 5064C. If there is a valid Power of Attorney (POA) or third-party representative on file, verify the Centralized Authorization File (CAF) copy selection is input. Multiple tax years can be combined in one letter unless unique issues or account resolution are present requiring individual tax year letters. Caution: All of the taxpayer's issues must be addressed in the closing letter. When multiple determinations are made (i.e., Tax Year 2020 No IDT, Tax Year 2021 IDT) separate letters must be issued. Refer to Exhibit 25.23.4-10, Identity Theft (IDT) Closing Letter Decision Chart, for additional information. Review letters for misspelled words, errors in capitalization and punctuation, IRS jargon, and other fill-in errors. Actions taken on the account will determine if a Letter 4674C needs to be issued as a closing letter. A letter 4674C must be sent if any of the following conditions exist. Include the indicated telephone number provided for the applicable condition. Note: The IDT Toll-free number, 800-908-4490, does not include an employee's extension and is answered by the AM Toll-Free assistors. The hours of operation are 7:00 a.m. - 7:00 p.m. The IDTVA Toll-free number, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡, does include the employee's extension and is answered by employees. The employee issuing the letter will input their TOD as the hours of operation. The IDTVA International number, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (not toll-free), does include the employee's extension and is answered by employees. The employee issuing the letter will input their TOD as the hours of operation. Exception: A closing letter may be a letter other than Letter 4674C when procedural guidance specifies the letter must be sent to the taxpayer (i.e., Letter 105C) or third party (i.e., Letter 0135C). The closing letter must include the appropriate phone number based on the criteria below. It is not necessary to issue a Letter 4674C in addition to the closing letter required by the procedural guidance, unless additional information needs to be provided that cannot be included. When appropriate, an open paragraph may be used to address the identity theft claim when sending a letter other than Letter 4674C. The following paragraph or similar verbiage may be used: "We reviewed and accepted the identity theft claim dated (month day, year). We have verified you are a victim of identity theft for tax year(s) (YYYY, YYYY, and YYYY)." Input the claim date in place of (month day, year) and enter only the applicable tax year(s) in the format YYYY. See chart below: Criteria Number to be used (1) If the CP 01/CP 01C will not be issued, Reminder: The CP 01/CP 01C will not be issued if one has been issued in last three years. Reminder: Closing an account with a TC 971 AC 506 will not generate a systemic closing letter in most instances. IDT Toll-free number 800-908-4490 (2) If a Letter 5064C, Letter 5073C, or CP 01S was not issued previously providing the taxpayer with an IDT Toll-free number OR When corresponding with an individual under age 18 IDTVA Toll-free number ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ with employee's name, six-digit extension and TOD (3) If the taxpayer's correspondence contains questions that will not be addressed by the CP 01/CP 01C Answer taxpayer's question and include IDT toll-free number 800-908-4490 (4) The resolution was not what the taxpayer anticipated (i.e., NOIDT determination, disagreed with information TP provided) IDTVA Toll-free number ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ with employee's name, six-digit extension and TOD (5) There is an additional requirement in the corresponding functional IRM Telephone number based on the functional guidance (6) International taxpayers When issuing Letter 4674C, include paragraph (;). (7) You are closing the case as previous action and an interim letter was issued IDT Toll-free number 800-908-4490 (8) The case is for an individual under age 18 IDTVA Toll-free number ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ with employee's name, six-digit extension and TOD Note: If two criteria fit a case, use the IDTVA toll-free number with the employee's name, six-digit extension, and TOD. For international taxpayers, also include ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ with the employee's name, six-digit extension, and TOD. If there is still a compliance issue after the IDT issue is resolved, (i.e., account will result in a balance due), provide the applicable Compliance toll-free number. See paragraph (13) of IRM 25.23.4.18.5, Taxpayer Calls on Identity Theft (IDT) Cases (IDTVA Paper Employees Only) for a list of numbers. Caution: Do not provide a specific dollar amount unless the taxpayer or their authorized representative makes a request for one. Example: The taxpayer's current year refund was applied to a balance owed for a prior year. The taxpayer submits Form 14039 stating they are a victim of identity theft, because they didn't file a return for the year the refund was applied to and should not have a balance due. Through research, you determine the taxpayer is not a victim of identity theft. The balance owed is the result of an ASFR assessment made for income earned by the taxpayer. The identity theft case is closed, but the compliance issue remains. The closing letter must include the phone number the taxpayer may call for more information about the ASFR assessment. On cases filed as married filing jointly, the closing Letter 4674C should be addressed to both taxpayers when the CII case is assigned under the primary TIN. A disclosure issue does not exist when the letter is addressed to both taxpayers. If the valid return was filed MFJ and the CII case is assigned under the secondary taxpayer's TIN, the letter will be issued from the secondary account and may include both taxpayers' names. Exception: If the MFJ status is related to an invalid return meeting MFJ scheme criteria, each taxpayer must receive a separate closing letter. These taxpayers are unrelated and must both be advised of the determination and actions taken to resolve their account. Exception: If an invalid joint election (IJE) determination has been made, the closing letter will be issued to the reporting taxpayer only. Note: If you are providing additional account information that was filed on a separate return for the victim, then the Letter 4674C should be addressed to the victim only. This includes instances of non-tax-related IDT affecting only one of the taxpayers on a MFJ entity. Closing an account with a TC 971 AC 506 in most instances, will not generate a systemic closing letter. Use Letter 4674C, IDTVA Closing Letter, to inform the taxpayer of the outcome of their IDT return. Note: If a closing letter was issued by RIVO/TPP already (e.g., Letter 4310C), do not issue a duplicate closing letter unless it has been more than 30 days and/or the RIVO/TPP Letter 4310C did not provide a response to all of the actions taken on the account. Caution: If the TC 971 AC 506 is not input prior to cycle 47 of the processing year, an IP PIN/CP01A will not generate for the upcoming filing season. Between cycle 47 and January 1 of the following year, IP PIN information must be provided in a closing letter. Barring any unforeseen circumstances, this additional information will not be required in closing letters issued between January 1 and cycle 47. SERP Alerts should be monitored for information related to IP PINs that may impact this timeframe. Use the appropriate special paragraphs in paragraph (12) above in addition to the paragraphs selected for your closing Letter 4674C. Be sure any necessary letters are being sent to the correct address. The Correspondex letter system will default to the address of record (CC ENMOD) which may or may not be the correct address. Override the address of record, when appropriate. If the returns or return and inquiry on an account/case contain the same address and a telephone number was provided, attempt to obtain more information first by telephone contact. If a telephone number is not available, then send only one letter to the address. See IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written).

# Requests for Additional Information (Telephone and/or Written)

25.23.4.18.2 (10-01-2024) Requests for Additional Information (Telephone and/or Written) Employees are required to contact the taxpayer(s) by telephone and/or by mail to obtain the necessary information when: The information provided by the taxpayer is insufficient. An IDT determination cannot be made through internal research. The forms and schedules required to be included with the tax return (i.e., Sch. A, Form 8863, etc.) are not provided and cannot be located through internal research. Exception: Refer to paragraph (3) for the tax return signature requirements. To prevent unnecessary delays in case processing, the lead or manager must concur with the employee's decision to request information from the taxpayer. A CII case note documenting concurrence must be input prior to requesting the information. Refer to the table below to determine the appropriate action to take when a signature is missing: If Then (1) Form 14039 is not signed, A signature is not required to make an IDT determination or resolve the case. Process following normal procedures. (2) The valid tax return is not signed, Do not request the signature. Resolve the account based on the determination made using the applicable procedures outlined in IRM 25.23.4, IDTVA Paper Process, and the appropriate functional IRM for Compliance IDT cases. Use HC 3 to prevent the adjustment notice from being issued or HC 4 to prevent the adjustment notice and a refund from being issued. Document on CII with a case note indicating a signed copy of the valid taxpayer's return must be received before the refund can be released. Send a closing Letter 4674C. In an open paragraph, inform the taxpayer their refund cannot be issued until a signed copy of their return is received. Include the return address code for the appropriate campus. (3) Form 1310 is not signed, Request a signed Form 1310. Proceed to paragraph (6). If the Form 14039 alleges a Return Preparer Misconduct (RPM) issue, do not request additional information. Follow procedures in IRM 25.23.4.4, Taxpayer Inquiries Involving Identity Theft (IDT). Exception: If the taxpayer's statement is not clear and additional information is needed to determine if the taxpayer is reporting an IDT issue or an RPM issue, contact the taxpayer for clarification. If a posted TC 976 return is necessary for resolution of your case: Follow procedures in IRM 25.23.4.6.5.1, Ordering Documents, to request the return. Issue Letter 5064C, requesting a copy of the return from the taxpayer. Note: To prevent unnecessary delays, attempting to contact the taxpayer and the input of IDRS CC ESTAB may be completed on the same day. Reminder: You may attempt to contact the taxpayer by telephone to obtain a copy of the return. When telephone information is available, employees may elect to attempt to contact the taxpayer(s) by telephone to obtain the additional information. When making an outgoing call, document the attempt in a CII case note. Include the phone number called, who you spoke with, the taxpayer's response, and/or if a message was left for the taxpayer. If you are able to leave a phone message, allow the taxpayer 5 business days to return your call. Note: Employees may send Letter 5064C to request the information after the unsuccessful attempt by telephone. When leaving a message for a dependent related IDT case, advise the taxpayer the last four digits of the dependent's TIN should be provided when leaving you a voice mail if they are unable to reach you when they return your call. Letter 5064C must be sent no later than 7 business days after an unsuccessful attempt to reach the taxpayer by telephone is made. If contact is made with the taxpayer, advise the taxpayer you will begin by asking some questions to verify their identity. Refer to paragraphs (22) - (24) of IRM 21.1.1.4, Communication Skills, for guidance specific to outgoing calls. Because telephone contact for these cases involves undetermined ownership of the Common Number (CN), guidance in IRM 21.1.3.2.3, Required Taxpayer Authentication, must be followed to ensure you are speaking to the appropriate taxpayer and to prevent unauthorized disclosure of tax information. Do not ask questions that might inadvertently disclose information merely by asking the question. Do not provide any information to the taxpayer unless specifically authorized to do so. Note: Follow guidance in IRM 21.1.3.3, Third Party (POA/TIA/F706) Authentication, and the related subsections when communicating with third parties. Centralized Authorization File (CAF) function has discovered that certain individuals have tried to gain access to taxpayer account information by filing fraudulent authorizations. See IRM 21.3.7.5.5, Suspicious Forms Log and the "Potential Fraud" Authorization Referral Process, for more information on identifying a potential fraudulent authorization.. Note: Guidance in IRM 21.1.3.4, Other Third-Party Inquiries, authorizes you to accept information from any third-party even if the provider of the information does not have a written or oral authorization from the taxpayer. If you are able to authenticate the individual to whom you are speaking, advise them of the information needed to continue processing their case, and provide instructions for submitting the request. If a Letter 5064C was issued to make a CN ownership determination, proceed to paragraph (4) of IRM 25.23.4.18.2.1, Telephone Contact Guidelines (Associated with the Letter 5064C Common Number Questionnaire), for additional guidance. Note: If there are required forms or schedules the taxpayer must submit, provide them with a fax/EE-fax number so they can submit the needed documentation. Allow the taxpayer five (5) business days to submit the document(s). If the document(s) are not received within five (5) days, continue to paragraph (8) for guidance to send a letter. Note: IDTVA Specialty Functions - When applicable, be sure to explain to the taxpayer that if the requested information is not received within the allotted time, compliance issues or collection actions will resume, as appropriate. Employees must contact the taxpayer(s) by mail using Letter 5064C. Exception: If the employee is able to reach the taxpayer by telephone and obtains the information from the taxpayer during the call, a letter is not required. If no contact information is available, telephone attempts are unsuccessful, or a telephone attempt is not made, correspond with the taxpayer via Letter 5064 to request the needed information. Use IAT to input Letter 5064C. Ensure the correct address is used when issuing any correspondence. Reference any missing information, if applicable. Provide information to allow the taxpayer to reply either by mail, fax/EEFax, or telephone. Inform the taxpayers they have 30 days (60 days for International) from the date of the letter to respond. Capture an image of the letter on CII. Suspend the case for 40 days (70 days for International cases). Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional letter requirements. See Exhibit 25.23.4-11, IDRS Activity Codes and Definitions, for documenting the follow-up date. Caution: Do not advise the taxpayer to contact SSA for a "Social Security Administration Social Security Number Verification" printout. After the suspense timeframe has passed, search the case for newly associated documents and CII for a related case that may include the response. Note: Review of all indicators on CII is recommended prior to opening the case. CII will reflect a New Information Indicator D before the case is opened. This indicator will not show once the case is accessed. If the taxpayer's response includes a Form 2848, Power of Attorney and Declaration of Representative or Form 8821, Tax Information Authorization: Perform research to determine if the Form 2848 or Form 8821 has been processed. Refer to IRM 21.3.7.5.1, Essential Elements for Form 2848 and Form 8821. If unprocessed, accept the completed form. Forward the form to the appropriate CAF unit for processing. See SERP Who/Where CAF Unit Addresses, Fax Numbers, and State Mapping for routing information. Use the table below to determine the appropriate action(s) to take for scenarios that do not include requesting a copy of the posted TC 976 return. Caution: Return related instructions in this table are only for the handling of a taxpayer's return as submitted. You must still review the account to determine if the submitted return resolves any outstanding Compliance issues. If Then (1) The taxpayer provides the requested information, Resolve the account based on the determination made using the applicable procedures outlined in IRM 25.23.4, IDTVA Paper Process, and the appropriate functional IRM for Compliance IDT cases. (2) The information provided is not the information requested, Note: This includes documentation that is not acceptable for proof of legal guardianship Determine if the individual who submitted the claim is the taxpayer or an authorized representative. Caution: If the information requested was for the purpose of determining if the taxpayer was reporting an IDT issue or Return Preparer Misconduct (RPM) issue, do not take the actions below. Refer to Table Scenario (4). Caution: If the tax year in question is a statute year with a multiple return issue, do not take the actions below. Refer to paragraph (15) below. If there is enough information to determine the taxpayer is a victim of IDT: Math verify the tax return, if present. Follow procedures in IRM 25.23.4.10.11 , Identity Theft (IDT) - Setting the Math Error, if appropriate. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If, after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Make a determination of No IDT. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third-party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (3) The suspense timeframe has expired, and there is no new information, Determine if the individual who submitted the claim is the taxpayer or an authorized representative. Caution: If the information requested was for the purpose of determining if the taxpayer was reporting an IDT issue or Return Preparer Misconduct (RPM) issue, do not take the actions below. Refer to Table Scenario (4). Caution: If the tax year in question is a statute year with a multiple return issue, do not take the actions below. Refer to paragraph (15) below. If there is enough information to determine the taxpayer is a victim of IDT: Math verify the tax return, if present. Follow Procedures in IRM 25.23.4.10.11 , Identity Theft (IDT) - Setting the Math Error, if appropriate. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third-party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If, after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Follow procedures in IRM 25.23.4.10.9 , No Reply. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third-party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (4) The suspense timeframe has expired and the information requested was for the purpose of determining if the taxpayer was reporting an IDT issue or an RPM issue, Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If a response was received, and there is enough information to make an IDT determination: Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and identify the appropriate method of resolution. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third-party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If a response was received, and the taxpayer indicates it is an RPM issue: Follow procedures in IRM 25.23.4.4, Taxpayer Inquiries Involving Identity Theft (IDT). If a response was received, and the consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT OR No response was received: Make a determination of No IDT. Follow procedures in IRM 25.23.4.4 Taxpayer Inquiries Involving Identity Theft (IDT). If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third-party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. Example: Amanda Green submits Form 14039 on behalf of Robert Green. Form 14039 states they are Robert's aunt and was not able to file their return electronically because someone else used Robert's Social Security Number. You send a Letter 5064C requesting proof of legal guardianship. Amanda's response includes a written statement from Robert's mother indicating they have been placed in the care of Amanda Green. Because a parent's statement is unacceptable proof of legal guardianship, the case would be resolved by following Table Scenario 2. Example: Steven Stone submits Form 14039 on behalf of Erica Stone. Form 14039 states they did not receive their Economic Impact Payment because someone else claimed their granddaughter. Research of the account shows Erica has been claimed as a dependent by another taxpayer for the last five years. The relationship indicated on the return lists Erica Stone as a niece of this taxpayer. You send a Letter 5064C requesting proof of legal guardianship. Steven's response includes a court order placing Erica Stone in their custody since 2012. This case would be resolved following Table Scenario 1. Example: Lisa Rose files a Form 14039 reporting someone else working under their Social Security Number. Lisa explains they are working part time and their Social Security benefits were reduced because of the income earned by the other person. Research of CC IRPTR shows ten separate employers in the same city reporting income under Lisa's SSN. Lisa did not specify who their employers are or what income they are disputing. You send Lisa a Letter 5064C requesting additional information about the income they did not earn. Lisa's response does not provide enough information to determine what income they earned and did not earn. This case would be resolved following Table Scenario 2. Use the table below to determine the appropriate action(s) to take when a copy of the posted TC 976 return was requested, and it is not a statute year. If Then (1) The taxpayer provides a copy of the requested tax return, Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If there is enough information to determine the taxpayer is a victim of IDT: Math verify the tax return, if present. Follow Procedures in IRM 25.23.4.10.11 , Identity Theft (IDT) - Setting the Math Error, if appropriate. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If, after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB. Original Case: Make a determination of No IDT. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. Original Case: If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (2) The taxpayer responds but does not provide the requested tax return, Caution: When the return requested posted as a TC 976, procedures to obtain the return internally must be completed prior to moving forward. Refer to IRM 25.23.4.6.5.1, Ordering Documents, for additional information. Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If the taxpayer's response indicates they did not file the tax return requested: Determine the TC 976 return to be invalid meeting streamline criteria. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and identify the appropriate method of resolution. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If the taxpayer's response does not include or address the tax return requested, and after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB. Original Case: Make a determination of No IDT. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. Original Case: If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (3) The suspense timeframe has expired and the taxpayer did not respond, Caution: When the return requested posted as a TC 976, procedures to obtain the return internally must be completed prior to moving forward. Refer to IRM 25.23.4.6.5.1, Ordering Documents, for additional information. Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If there is enough information to determine the taxpayer is a victim of IDT: Determine the TC 976 return to be invalid meeting streamline criteria. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and identify the appropriate method of resolution. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. Input a CII case note detailing the document requests, the letter issued to the taxpayer, and the IDT determination. Include the date Letter 5064C was issued to the taxpayer and that no response was received. Issue a closing Letter 4674C. Include a statement indicating they did not respond to our request for a copy of the tax return on file and that it was not processed. You may use the special paragraph provided below or similar verbiage. Note: If you copy and paste the following paragraph into the letter, do not include the quotation marks. "You didn't respond to our request for a copy of the tax return received on XX/XX/XXXX. As a result, we were not able to process it." Input the IRS received date of the posted TC 976 in place of the X's. Refer to IRM 25.23.4.17, Determining Tax Liability/Form 2209 Instructions, regarding taxpayer filing requirements and additional information that may need to be included in the closing letter. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB. Original case: Follow procedures in IRM 25.23.4.10.9 , No Reply. Original case: If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. Use the table below to determine the appropriate action(s) to take when a copy of the posted TC 976 return was requested and it is a statute year. If Then (1) The taxpayer provides a copy of the requested tax return, Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If there is enough information to make an IDT determination: Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and the appropriate method of resolution. f the valid tax return ASED is imminent, refer to IRM 25.23.4.9.1 , Statute Imminent Assessment for IDT Cases, to ensure the account is protected. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If, after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB. Exception: If there is an imminent tax increase, advise your manager of the statute issue on the DUPF case. The case should be prioritized. Original Case: Make a determination of No IDT. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (2) The taxpayer responds but does not provide or address the requested tax return, Caution: When the return requested posted as a TC 976, procedures to obtain the return internally must be completed prior to moving forward. Refer to IRM 25.23.4.6.5.1, Ordering Documents, for additional information. Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If the taxpayer's response indicates they did not file the tax return requested: Determine the TC 976 return to be invalid meeting streamline criteria. Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and identify the appropriate method of resolution. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If the taxpayer's response does not include or address the tax return requested, and after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB Exception: If there is an imminent tax increase, advise your manager of the statute issue on the DUPF case. The case should be prioritized. Original Case: Make a determination of No IDT. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. (3) The suspense timeframe has expired, there is no new information, and the tax year in question is a statute year with a multiple return issue, Suspend the case for an additional 40 days (70 days for International cases). (4) The extended suspense timeframe has expired, there is no new information, and the tax year in question is a statute year with a multiple return issue, Caution: When the return requested posted as a TC 976, procedures to obtain the return internally must be completed prior to moving forward. Refer to IRM 25.23.4.6.5.1, Ordering Documents, for additional information. Determine if the individual who submitted the claim is the taxpayer or an authorized representative. If there is enough information to make an IDT determination: Refer to IRM 25.23.4.8, Identity Theft (IDT) Common Number (CN) Ownership and Case Processing Determinations, to make an IDT determination and the appropriate method of resolution. If the valid tax return ASED is imminent, refer to IRM 25.23.4.9.1 Statute Imminent Assessment for IDT Cases, to ensure the account is protected. Follow applicable procedures in IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases, based on the determination made. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If there is enough information to make an IDT determination and the valid return ASED is expired: Follow procedures in IRM 25.23.4.9.2 , Addressing Barred Assessments on Identity Theft (IDT) Cases, and its applicable subsections to determine if there is a barred statute and take the appropriate actions to resolve the case. If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. If a response was not received and after consideration of all information available, you are unable to confirm the taxpayer is a victim of IDT: Create a new CII case with Category Code DUPF and Program Code 40050. On both cases: Input a CII case note stating IDT could not be confirmed. Include details of the document requests, the letter issued to the taxpayer, the date Letter 5064C was issued to the taxpayer, and that no response was received. Link the new case to your original case. Reassign the new case using the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB Exception: If there is an imminent tax increase, advise your manager of the statute issue on the DUPF case. The case should be prioritized. Original case: Follow procedures in IRM 25.23.4.10.9 , No Reply. Original case: If the claim was submitted by an individual who is not the taxpayer or an authorized representative, correspond with the individual who submitted the claim following unauthorized third party procedures. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures. When corresponding with the taxpayer to make a common number ownership determination, select paragraphs S through W to include the questionnaire. The questionnaire process moves in progressive stages that afford the taxpayer ample opportunity to provide the requested information. If at any stage the necessary information for a CN ownership determination is received AND any applicable suspense periods for that stage have expired, it is not necessary to proceed to the next stage.

# Telephone Contact Guidelines (Associated with the Letter 5064C Common Number Questionnaire)

25.23.4.18.2.1 (10-01-2019) Telephone Contact Guidelines (Associated with the Letter 5064C Common Number Questionnaire) Allow 21 days from the input date of the Letter 5064C before IRS-initiated telephone contact is attempted (to allow the taxpayer to receive the letter). The following defines a valid attempt to contact the taxpayer by telephone: If a telephone number is available, then a call during the hours provided (if listed), followed by, if necessary, another call on a subsequent day constitutes a valid attempt. If you can leave a phone message allow the taxpayer 5 business days to return your call. Caution: If you leave a message for the taxpayer, do not provide any account information. Be especially careful when leaving a message on a number not obtained by a Letter 5064C response. Follow guidance in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), (Prior to Initiating Correspondence) to initiate the call. Reminder: Do not ask any questions that might inadvertently disclose information merely by asking the question. Do not provide any information to the taxpayer unless specifically authorized to do so. After authenticating the individual to whom you are speaking, ask the taxpayer if they recently received a letter from the IRS. If the taxpayer indicates they have not received a letter from the IRS, provide an explanation of the letter they will be receiving. Ask them if they would like to continue with the call or prefer to call back after they have received the letter. If the taxpayer would like to continue with the call, complete High-Risk disclosure to verify the identity of the person you are speaking with. Preface the asking of the questions below with the following statements to the taxpayer: Note: Modify your statements and questions appropriately to the taxpayer if you are working a True Scrambled SSN case. If you are working a True Scrambled SSN case, tell the taxpayer that it appears the Social Security Administration has assigned the SSN to more than one individual. Strongly recommend that the taxpayer contact SSA as soon as possible. Any information the taxpayer provides by answering these questions will assist SSA. Our records indicate that the Social Security Number you used on your tax return for the tax year(s) of 'YYYY' (state the tax year(s) in question) was also used by another individual on their federal tax return. Disclosure laws prevent us from providing any information regarding the other individual. We would like to ask you a few questions in order to determine which individual should be using the Social Security Number for the filing of federal tax returns. "The IRS does not issue Social Security Numbers, and the IRS does not determine who the true owner of the Social Security Number is for the purposes of Social Security benefits. The Social Security Administration is a separate government agency and is the final authority on determining the ownership of the Social Security Number. We recommend strongly that you contact your local Social Security Administration office to ensure that your Social Security records are correct. The questions we would like to ask you today, consequently, pertain only to the filing of your federal income tax return. " "The questions are based on information received from the Social Security Administration. The answers you provide will assist us in resolving this issue as quickly as possible. An incorrect answer or a response of "I don't know" will not necessarily result in the Social Security Number not being assigned to you for federal income tax purposes." "Are you willing to answer the questions?" If the taxpayer indicates they are not willing to answer the questions, simply thank the taxpayer for their time and inform the taxpayer that our determination will be made based on the information at hand. Inform the taxpayer that they will receive a letter regarding our determination within 6 to 8 weeks. If the taxpayer asks for the questions to be sent by mail, inform the taxpayer that the questions not already listed on the letter they received must be given and answered during direct telephone conversation. If necessary, you may inform the taxpayer that this method is intended to ensure that the person using the Social Security number in error does not have the opportunity to research and find the correct answers. If the taxpayer is willing to answer the questions, proceed with asking the questions in the questionnaire portion of the Letter 5064C and the questions in IRM 25.23.4.18.2.2, Supplementary Questions (Associated with Letter 5064C Common Number Questionnaire). Have a copy of the Numident print available, related to the SSN, when asking the Supplementary Questions. Caution: Do not respond in any way that might be construed as a confirmation or a rejection of the validity of the taxpayer's response. The purpose of asking the questions is to obtain information for consideration, not to provide information to the taxpayer. Indications of confirmation or rejection would constitute providing information to the taxpayer. On the TIN-Related Problem Research Sheet record the answers you receive. We can make a determination without the questionnaire and documents in our file, but if an ownership determination is not made, the taxpayer will not receive their refund unless they have met all the conditions of IRM 21.6.2.4.3.3, Determining if the Scrambled SSN Indicator (SCI) Should be Removed. A True Scrambled SSN Case requires the actual documents, completed by the taxpayer, for the file going to SSA. If you believe the number is a True Scrambled, tell the taxpayer to send the documents requested in the Letter 5064C and the questionnaire as soon as possible. After all the questions have been asked and the answers recorded, state the following to the taxpayer: "Thank you for the information you have provided. When we have completed our gathering and reviewing of information, we will notify you by mail of our determination. The expected time frame for the process of review and notification is generally 6 to 8 weeks. If possible, we will issue our determination more quickly than the expected time frame." "Please keep in mind the information we provided earlier in the conversation: The IRS does not issue Social Security Numbers, and the IRS does not determine who the true owner of the Social Security Number is for the purposes of Social Security benefits. The Social Security Administration is a separate government agency and is the final authority on determining the ownership of the Social Security Number. We recommend strongly that you contact your local Social Security Administration office to ensure that your Social Security records are correct. The questions we have asked today, consequently, pertain only to the filing of your federal income tax return." Caution: Be reminded that because this case involves an SSN of undetermined ownership, we cannot disclose any further information. Also, be careful not to indicate any pre-determinations you may have arrived at based on the answers you received. Ensure equal opportunity for each taxpayer to provide information. Refer to the If/And/Then Chart below: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

# Supplementary Questions (Associated with Letter 5064C Common Number Questionnaire)

25.23.4.18.2.2 (10-01-2020) Supplementary Questions (Associated with Letter 5064C Common Number Questionnaire) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Caution: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

# Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions sent to determine Common Number Ownership

25.23.4.18.2.3 (10-12-2023) Actions Based on No Response or Taxpayer Responses to Letter 5064C and/or Supplementary Questions sent to determine Common Number Ownership Follow the guidance below to determine the appropriate actions for your IDT case. Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: Please see IRM 25.23.2.2, Identity Theft Claim - Overview, for additional information. Note: For identity theft claims determined to be a scrambled SSN issue, follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, prior to resolving or reassigning the case. No Response If Then The follow-up date expires on a Letter 5064C sent for common number owner determination and a review of CII shows that neither taxpayer provided a response/documentation whether by mail, telephone, or fax/EEFax, See IRM 25.23.4.10.9, No Reply. Change control category to "SCRM" If you are not trained to work SCRM cases, then reassign the case to the SCRM holding number located on the Accounts Management Site Specialization Temporary Holding Numbers located on SERP. Note: If the required research has not been conducted and/or if the case does not contain all of the required documentation, the case will be rejected back to the site IDT POC. If trained to work SCRM cases, then continue to work the case. Refer to IRM 21.6.2.4.3, Scrambled SSN Case Procedures, for related guidance. Processable Responses from One Taxpayer Reminder: The taxpayer is not a victim of identity theft when a Scrambled SSN determination is made. Refer to IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations for additional information. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Consider the taxpayer who responded with the accurate questionnaire information to be the owner of the CN. Add a CII note and a note to your TIN-Related Problem Research Sheet stating 5064 Response. Refer to IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases to identify your case scenario. Follow the guidance to resolve your case. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Does NOT provide a different valid TIN ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ The information provided by both taxpayers is confirmed by comparison with Numident ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

# Final Stage Review (Associated with Letter 5064C sent for Common Number Ownership

25.23.4.18.2.4 (10-01-2019) Final Stage Review (Associated with Letter 5064C sent for Common Number Ownership If instructed to move to Final Stage Review by the If/Then scenarios in the preceding sections, follow the If/Then table below to determine the appropriate subsequent actions for the case. Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡

# Processing Taxpayer Replies to Closing Identity Theft (IDT) Letters sent for Common Number Owner Determination

25.23.4.18.3 (10-01-2019) Processing Taxpayer Replies to Closing Identity Theft (IDT) Letters sent for Common Number Owner Determination ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Caution: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Caution: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Caution: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

# Resolving Undeliverable Identity Theft (IDT) Mail

25.23.4.18.4 (10-21-2019) Resolving Undeliverable Identity Theft (IDT) Mail There may be instances when IDT correspondence and/or letters are returned as undeliverable because the taxpayer may have moved, an incorrect/incomplete address was input or the address provided was invalid. Refer to the chart below for additional guidance. Letter Action (1) Letter 239C/Letter 5064C Letter (Suspense) Route to the employee with the open control. (2) Letter 239C/Letter 4674C Letter (Closing) Compare the information on the letter with the documentation on the closed case file. Look for any potential errors or omissions in working the case that may have caused the letter to be undeliverable. If you are unable to determine the reason for the undeliverable, it may be necessary to order the CN owner's return (if one was filed) to verify the entity information on the original return. This also includes verifying other documents attached to the return (e.g., Form 14039 and/or additional correspondence). Possible errors or omissions may include: Sending the letter to the wrong address Omitting an address change or address perfection (i.e., missing apt #) Incorrectly determining a thief's return to be an SSN owner's return If the undeliverable was not caused by an error or omission, destroy the undeliverable as classified waste. If the undeliverable was caused by an error or omission, take any action needed to correct the tax account and entity information. Re-send the letter or another letter, if appropriate. If during your research you determine additional closing actions were omitted, make the appropriate changes to correct the TP's account. Send another letter to address all actions taken on the account, if appropriate. Note: Remember to update the case Category Code and post time under the correct function and program code if taking additional actions. Link your case to previous IDT case. Reminder: Undelivered mail should not be scanned into CII per IRM 21.3.3.4.11.1.1, Undelivered Mail Procedures for Accounts Management.

# Taxpayer Calls on Identity Theft (IDT) Cases (IDTVA Paper Employees Only)

25.23.4.18.5 (11-06-2024) Taxpayer Calls on Identity Theft (IDT) Cases (IDTVA Paper Employees Only) The IDTVA Toll-Free Number, ≡ ≡ ≡ ≡ ≡ ≡ ≡, is to be used "ONLY" for IDT/RPM calls and should not be provided to taxpayers unless there is an IDT/RPM issue. A NO IDT determination is considered an IDT issue when providing the taxpayer with a toll-free number. IDTVA employees have been assigned a six-digit extension code. That code must be included with toll-free number on all correspondence and/or closure letters generated on an IDT/RPM case or when leaving a phone message. Exception: Employees who do not have a six-digit extension will use the extension of their work leader when issuing the letter. IDTVA employees must be available and answer incoming calls to their assigned extensions when they are not providing assistance on a toll-free line. IDTVA employees will sign on to their IDTVA (IDT/RPM) extensions using idle code INVEN1 when they are working cases. Exception: Employees taking complex case actions at the time the call is received may allow the call to go to voice mail. Complex case actions may include inputting an adjustment, sending a letter with an open paragraph, issuing a manual refund, etc. Complex case actions do not include research. Note: IDTVA employees (Series 962 and 592) working paper inventory are assigned an extension for call routing. Employees that are in a 0962 series position are required to use idle codes at all times. Other employees (0592 series) are not covered by the Customer Service Agreement Part II involving the operation of the current phone systems. Employees should sign off the system when they are not at their desk working. Idle code "INVEN1" (or "INVEN2" when working OT) should be used when a 592 employee is working at their desk. It is critical all voice mail messages are retrieved immediately. Calls should be returned prior to working another case or at the time the taxpayer indicated when allowed to go to voice mail. All calls should be returned within five business days. If an employee is going to be unavailable for one or more days, the voice mail recording should be updated to reflect the unavailable time period and include a call back time frame. If the employee expects to be gone more than two business days, the message should reflect that someone else will return their call. The following script or similar verbiage should be used on IDT/RPM extensions: "You have reached (Title/Last Name/ID number). Thank you for calling regarding your identity theft case. I am not available at this time, but will return your call within five business days. Please leave your name, social security number, phone number, and the best time to call you. My shift is (start time) to (end time) based on an approximate time zone. Because your case is assigned to me, I will only be able to contact you during those times." The following script or similar verbiage should be used on IDT extensions if the employee is unavailable for four days or more: "You have reached (Title/Last Name/ID number). Thank you for calling regarding your identity theft case. I will not be available until (provide date of return), and I will return your call at that time. Please leave your name, phone number, social security number, and the best time to reach you. My shift is (start time) to (end time) based on an approximate time zone. Because your case is assigned to me, I will only be able to contact you during those times. If you need to be contacted prior to that time, call back and enter extension ###### and another member from the identity theft team will contact you as soon as possible" Note: The manager should identify which employee or work leader extension should be used for the employee's message. When receiving telephone inquiries or returning calls, IRM 21.1.3.2.3, Required Taxpayer Authentication, must be followed to ensure you are speaking to the appropriate taxpayer or their authorized representative and to prevent unauthorized disclosure of tax information. Do not ask any questions that might inadvertently disclose information merely by asking the question. Calls are routed to an employee based on the six-digit code input by the taxpayer and will show on the ICCE System with "459 WI IDT EXT RTG" on the display. For IUP calls, your extension should appear in the "Call Key" box on your computer screen. Upon receiving calls, the employee must attempt to answer the taxpayer's questions. If the taxpayer's case is not assigned to you and you are unable to answer all of their questions, determine if there is an open IDTVA IDRS control. If found, use the following link to locate the controlling employee's contact information via the IDTVA Employee Lookup Tool. Provide the taxpayer the toll-free number, employee's name, extension, and Tour of Duty (TOD), when available, based on an approximate time zone. Include the following information: "If you receive the employee's voice mail, the call will be returned within five business days." "If you do not receive a call back within five business days, you may call this number again. The five business days will begin the day after the message is left. When you call back, advise the IRS employee answering the call that you left a message and did not receive a call back within 5 business days. That employee will follow-up on the call back request." Note: If the TP called in on the "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" number, you cannot transfer them. They will need to hang up and call back with the extension. Document on AMS the caller was provided the extension number. Note: Inform the TP the IRS phone number may be blocked or display as "unknown" when we make contact. Also advise the caller, if they have a voice messaging system that does not identify them by name (as the taxpayer), the IRS will not be able to leave a message. After the information above has been provided to the taxpayer (or a secure email sent), use CII (if the case is assigned to you) or AMS (if the case is not assigned to you) to document the call and the information the taxpayer provided: The letter or notice (e.g., Letter 4674C, Letter 4675C, Letter 5064C or CP 01C, etc.) the taxpayer was inquiring about A telephone number(s) where the taxpayer can be reached and the best time for the IDTVA employee to contact them. The date the caller's tax return was filed and the amount of refund expected (when applicable) Other pertinent information filed on the return that will assist the IDTVA employee in resolving the case If the IDTVA controlling employee's IDRS Number is not available on the IDTVA Employee Lookup Tool, refer the taxpayer inquiry using a secure email to the employee and employee's manager using secure email link. If an email is received with notification that a taxpayer is attempting to get in contact with the employee assigned to their case, the taxpayer must be contacted by the employee or another employee designated by the manager immediately, but no later than within two business days of receipt of the email. If the call is determined not to be an IDT case, refer the taxpayer to the appropriate toll-free number based on their inquiry, using the table below. Function Telephone Number (1) Accounts Management Toll-Free lines - any account issues not pertaining to compliance issues (Including missing payments; refunds; balances due (other than status 22) IMF - 800-829-1040 BMF - 800-829-4933 (2) For AUR related issues (TC 922) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (3) For Exam related issues (TC 300; - L Open TC 420; TC 140 SFR) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (4) ACS (Balance Due) Individual Income: 800-829-7650 Business Income - 800-829-3903 (5) For ASFR (TC 140 ASFR) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (6) Refund Hold (TC 570 with Julian date 999) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Available resources should be utilized for callers who are non-English speaking or have Limited English Proficiency (LEP). If no resources are available and the taxpayer has no other alternative, then Over-the Phone Interpreter (OPI) can be utilized. Refer to IRM 21.1.1.5, Over the Phone Interpreter Service (OPI) Applications, and IRM 21.8.1.2.3.2, Over the Phone Interpreter Service (OPI) For International Non Toll-Free calls, for instructions on utilizing the OPI service.

# Requesting Translations of Certain Languages

25.23.4.19 (04-28-2025) Requesting Translations of Certain Languages During the course of reviewing taxpayer correspondence, forms, documents, etc., the translation of non-English language may be required. Translations can be obtained from Linguistics Policy, Tools and Services (LPTS), on documents written in languages such as: Spanish French Haitian/Creole German Italian Portuguese Various African Languages Arabic Iranian Farsi For a complete list of language translations see Exhibit 22.31.1-1, Languages Provided by LPTS Providers. When translation of a non-English language is required: Employees must not use internet provider translation services, such as Google Translator, Microsoft Office, digital assistants like Siri, Google Assistant and Alexa, or Apps available on personal devices. Placing sensitive information on the internet for this purpose creates risks and vulnerabilities for the Service. The information is not subject to data protections or restrictions from re-disclosure by the end recipient and may not always meet the investigate disclosure requirements. Instead employees should contact Linguistic Policy, Tools and Services (LPTS) for assistance. For translations in Spanish, refer to (3) below and IRM 22.31.1.5.1.1, Requesting Translation of Non-Vital Documents from Certain Languages into English, for additional information. For translations in any other language, refer to IRM 25.23.4.19.1, Translation Requests for Certain Languages - Other Than Spanish. If you have documents that are in a non-English language and want them translated into English or need to issue an open paragraph in Spanish, please follow your local process to send your request to the designated individual. Designated individuals will follow the steps below to submit your request: Note: When submitting a paragraph that will be sent to the taxpayer, please make sure that the source document you submit is the final version. This ensures the translated and reviewed document matches the original document. Additionally, it avoids confusion and reduces the cost of the translation from our vendors. Enterprise Case Management (ECM) will be used to submit requests to Request Translation Services. Complete all required fields to populate Form 14078, Request for Translation and/or Quality Review Services. Upload source documents, as appropriate. Attach the source document(s) sent for translation to your CII case. When a translation of correspondence into English is received back from LPTS, scan the translation and attach the image to your CII case. This will prevent the same correspondence being translated multiple times. Note: In the event changes need to be made to the final version of your source document, resubmit with the corrected documentation and include your original source document. For example, Quality Review results in an error for information provided in your letter which requires you to send a corrected letter to the taxpayer. When a taxpayer provides information in Spanish language, employees with bilingual skills must input a CII case note to document the following: What the taxpayer is reporting on Form 14039 Information provided in correspondence A translation of any open paragraph included in a letter issued to the taxpayer

# Translation Requests for Certain Languages - Other Than Spanish

25.23.4.19.1 (04-28-2025) Translation Requests for Certain Languages - Other Than Spanish If you have documents that are in a non-English language and want them translated into English or need to issue an open paragraph in a language other than Spanish, please follow your local process to send your request to the designated individual. Designated individuals will follow the steps in paragraph (2) below to submit your request to Linguistics Policy, Tools and Services (LPTS). Note: When submitting a paragraph that will be sent to the taxpayer, please make sure that the source document you submit is the final version. This ensures the translated and reviewed document matches the original document. Additionally, it avoids confusion and reduces the cost of the translation from our vendors. Once you have identified the appropriate C letter and all paragraphs you will include, submit the source document as a single file that will consist of the composed letter, as it needs to be sent to the taxpayer. Determine the appropriate signature. Request translation of the title for that person. Ensure the source document you are providing is the final version to receive a complete and accurate translation. Enterprise Case Management (ECM) will be used to submit requests to Request Translation Services. Complete all required fields to populate Form 14078, Request for Translation and/or Quality Review Services. Upload source documents, as appropriate. Attach the source document(s) sent for translation to your CII case. When a completed translation request is returned from LPTS, scan the translation and attach the image to your CII case. When submitting multiple requests for the same case (i.e., each paragraph individually), each translation completed must be attached to your CII case. This will prevent the same correspondence being translated multiple times. Once all translations have been received, take the following actions to issue the correspondence to the taxpayer: Assemble your letter in a Word doc including all paragraphs in the format of the appropriate C letter. Type the appropriate name in place of the signature for this letter. Include the translated title below their name. Convert the completed letter to a .pdf file. Attach the .pdf file to CII. Print the letter (2 copies). Note: If the taxpayer has a Power of Attorney (POA) on file or sufficient documentation has been received to validate the POA, but is not yet on file, print an additional copy of the letter. Mail both copies of the letter to the taxpayer in the same envelope. Mail the POA copy separately. Document the address(es) mailed to in a CII case note. In the event changes need to be made to the final version of your source document, resubmit with the corrected documentation and include your original source document. For example, Quality Review results in an error for information provided in your letter which requires you to send a corrected letter to the taxpayer.

# Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General

25.23.4.20 (01-31-2023) Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) - General The Coronavirus Aid, Relief, and Economic Security Act (CARES Act) was signed into law on March 27, 2020. IRC 6428 provides eligible individuals with a recovery rebate credit (RRC) for tax year 2020 that taxpayers may receive as an advance payment. Advance payments of the RRC are referred to as Economic Impact Payments (EIPs). The RRC for tax year 2020 was increased, and a second Economic Impact Payment (EIP) was included as part of H.R. 133, Consolidated Appropriations Act, 2021. The American Rescue Plan Act (ARPA) of 2021 was enacted on March 11, 2021. It provides eligible individuals with a recovery rebate credit for tax year 2021 that taxpayers may receive as an advance payment (EIP 3). EIPs do not accrue credit interest. Systemic issuance of EIP 1 began with payments made via direct deposit on April 10, 2020. Paper checks were issued beginning April 24, 2020. Pre-paid debit cards were issued beginning May 18, 2020, and are identified by a TC 971 AC 199 with MISC "BFS DEBIT" . Advance payments of EIP 1 were not allowed after December 31, 2020. EIP 1 was subject to offset for child support obligations, only. Systemic issuance of EIP 2 began with payments made via direct deposit on January 4, 2021 followed by paper checks and pre-paid debit cards issued later in the month. Refunds of these payments are issued from the tax year 2020 module (tax year 202101 - 202111 for fiscal year filers). EIP 2 was not subject to offset. If EIP 2 was not issued by January 15, 2021, the taxpayer must file a tax year 2020 return to claim the 2020 RRC, if eligible Issuance of EIP 3 began in March 2021. Refunds of these payments are issued from the tax year 2021 module (tax year 202201 – 202211 for fiscal year filers). EIP 3 is not subject to offset. If EIP 3 has not been calculated by December 31, 2021, the taxpayer must file a tax year 2021 return to claim the 2021 RRC, if eligible. The amount of the EIP 1 is based on the tax year 2019 return, if filed. If a tax year 2019 return has not been processed, tax year 2018 return information is used. EIP 2 is based on the tax year 2019 return, if filed. EIP 3 is based on the tax year 2020 return, if filed. If a tax year 2020 return has not been processed, tax year 2019 return information is used. Systemic computation of EIP 3 will take into consideration updated AGI (as adjusted) but does not consider changes to filing status or child tax credit. If the EIP 3 was based on a 2019 return, when a 2020 return is filed, an additional payment will be issued if the amount of EIP 3 is more when computed with the 2020 tax return information. The deadline for additional payments is 90 days after the return due date (September 1, 2021) for calendar year filers. Taxpayers who have not filed a tax return for either 2019 or 2018 will not receive an EIP 1, taxpayers who have not filed a tax return for 2019 will not receive an EIP 2, and taxpayers who have not filed a tax return for either 2020 or 2019 will not receive an EIP 3, unless an exception applies: Of those who are not required to file returns for 2019 or 2018, individuals who received Social Security retirement benefits, Social Security disability income (SSDI), Social Security survivor benefits, Railroad Retirement benefits (RRB), Railroad Retirement survivor benefits, Veterans Administration (VA) Compensation and Pension (C&P) benefits in 2019 received their EIPs based on Federal benefit payment information for 2019. Individuals who did not have a filing requirement for tax year 2018, 2019, and/or 2020 may have used the Non-Filers Tool available on IRS.gov to receive an EIP by providing their personal information and selecting a payment type of direct deposit or paper check. Taxpayers who have been issued an Identity Protection Personal Identification Number (IP PIN) must enter their IP PIN on the tool. Note: Returns filed using the Non-Filers Tool can be identified with $1 of taxable interest income, $1 total income, and $1 AGI. An eligible individual is any individual other than: A nonresident alien (including any filer of Form 1040-NR or Form 1040-NR-EZ) An individual who can be claimed as a dependent on another individual's tax return An estate or trust Note: When calculating EIP 1 for joint filers, if one spouse meets eligibility requirements and the other does not, the eligible spouse is legally entitled to $1,200. However, programming does not determine which spouse qualifies, so no payment is issued. Either, or both of the spouses, if eligible, can claim the recovery rebate credit on the tax year 2020 return. In addition to the eligible individual details in paragraph (5) above, the following groups are not eligible for EIPs: A filer of Form 1040-NR, Form 1040-NR-EZ, Form 1040-PR, or Form 1040-SS for 2019. An individual who is deceased as of the date of EIP 1 issuance. Note: Individuals with a date of death of 1/1/2020 or later are eligible for EIP 2. Individuals with a date of death of 1/1/2021 or later are eligible for EIP 3. Taxpayer Identification Number (TIN) requirements for EIPs are listed below. Refer to the table following for a list of Social Security Citizenship Codes and their meanings. To receive EIP 1 in 2020 or claim a recovery rebate credit for 2020, a taxpayer must provide a valid TIN for the taxpayer and a valid TIN for any qualifying child claimed. If the taxpayer files a joint return, both the primary and secondary taxpayers must have valid TINs to receive EIP 1. TIN requirements were revised to receive EIP 2 and/or EIP 3. If a joint return is filed and one of the spouses has an ITIN, the spouse with the ITIN will be excluded from computation of the EIP 2 and/or EIP 3. Exception: For purposes of recovery rebate credits claimed on tax year 2020 and 2021 returns (including EIPs), if at least one spouse is a member of the United States Armed Forces, only one spouse needs to have a valid TIN. Members of the Armed Forces can be identified with a TC 971 AC 162 on the entity (IDRS CC ENMOD/IMFOLE). For this purpose, a valid TIN is a Social Security Number (SSN) valid for employment in the United States that is issued before the due date (including any extension) of the return. In the case of a qualifying child legally placed for adoption, an Adoption Taxpayer Identification Number (ATIN) constitutes a valid TIN. Accordingly, to receive an EIP 1 based on the information from tax year 2019 or 2018, each taxpayer (and the spouse if filing a joint return) must have a proper SSN issued before July 15, 2020 (or before October 15, 2020, if an extension was filed). A taxpayer claiming the recovery rebate credit on the 2020 tax return must have a proper SSN issued before May 17, 2021 (or before October 15, 2021, if an extension will be filed for 2020). Citizenship Code Meaning A SSA confirms U.S. citizen (domestic born) B SSA does not confirm U.S. citizen (legal alien, eligible to work) C SSA does not confirm U.S. citizen (legal alien, not eligible to work) D SSA does not confirm U.S. citizen (other) E SSA does not confirm U.S. citizen (alien, student restricted, work authorized) F SSA does not confirm U.S. citizen (conditionally legalized alien) N Unable to verify citizenship due to failed match on name, date of birth, or SSN * SSA does not confirm U.S. citizen (foreign) For purposes of EIP 1 and EIP 2, qualifying children are those that have a proper SSN (or ATIN) and meet all criteria to qualify for the Child Tax Credit (CTC). For purposes of the RRC claimed on the TY 2020 return, qualifying children must: Be listed as a dependent on the return, Be under age 17 at the end of 2020, and Qualify for the CTC with the box checked on the return or have an ATIN For purposes of EIP 3, the amount of any credit for qualifying dependents will be determined using a formula for calculation (outlined in paragraph (14) below). The credit includes dependents of any age but is limited to a maximum of 15 dependents. For purposes of the RRC claimed on the TY 2021 return, qualifying dependents: Must be listed as a dependent on the return, Must have a valid SSN or ATIN (for children legally placed for adoption), and Must not have a date of death (DOD) prior to 1/1/2021. To determine the number of allowable dependents when calculating EIP 3, take the following steps: Identify the total number of dependents. Determine if any dependents have a DOD prior to 1/1/2021. Determine if any dependents have an ITIN. Add the number of dependents identified in steps b and c. Subtract the number of dependents calculated in step 4 from the total number of dependents identified in step 1. If the result is greater than 15, limit to 15 dependents. Example: The total number of dependents on the return is 5. None of the dependents has a DOD, and 2 of the dependents have an ITIN. a. 5 b. 0 c. 2 d. 2 e. 5 − 2 = 3 Calculation of EIP 3 and the tax year 2021 recovery rebate credit will include 3 dependents. The EIP 1 credit amount is up to $1,200 ($2,400 for MFJ), plus an additional $500 for each qualifying child. The EIP 2 credit amount is up to $600 ($1,200 for MFJ), plus an additional $600 for each qualifying child. The EIP 1, EIP 2, and tax year 2020 RRC credits are subject to phase out if the AGI on the return considered (2019 or 2018) exceeds the following income limitations: $150,000 for joint filers (filing status 2) $150,000 for qualifying widow(er) (filing status 5) (EIP 2 only) $112,500 for head of household filers (filing status 4 or 7) $75,000 for all other filers When EIP 1 or EIP 2 is subject to phase out, the credit is reduced by 5% of the taxpayer's AGI exceeding the income limitations. See below for examples of calculating EIP when phase out applies. Example: A taxpayer has not filed a TY 2019 return. The TY 2018 return is filed single with no dependents and an AGI of $90,000. This exceeds the $75,000 limitation, and EIP phase out applies. $90,000 − $75,000 = $15,000. $15,000 × 5% = $750. EIP 1: The taxpayer's EIP is reduced by $750. The taxpayer will receive $450 ($1,200 − $750). EIP 2: The taxpayer will not receive a payment, because the $750 reduction due to phase out is more than the $600 individual base amount. Example: A TY 2019 return is filed married filing jointly with 2 qualifying children and an AGI of $160,000. The AGI exceeds the $150,000 limitation, and EIP phase out applies. $160,000 − $150,000 = $10,000. $10,000 × 5% = $500. EIP 1: The taxpayers will receive $2,900 ($2,400 MFJ base amount + $1,000 for the qualifying children − $500 due to phase out). EIP 2: The taxpayers will receive $1,900 (1,200 MFJ base amount + $1,200 for the qualifying children − $500 due to phase out). Example: A TY 2019 return is filed head of household with 3 qualifying children and an AGI of $115,000. The AGI exceeds the $112,500 limitation, and EIP phase out applies. $115,000 − $112,500 = $2,500. $2,500 × 5% = $125. EIP 1: The taxpayer will receive $2,575 ($1,200 individual base amount + $1,500 for the qualifying children − $125 due to the phase out). EIP 2: The taxpayer will receive $2,275 ($600 individual base amount + $1,800 − $125 due to the phase out). Taxpayers will report the tax year 2020 recovery rebate credit on their tax year 2020 return. The credit will be calculated based on the 2020 tax return information using the EIP 2 criteria for phase out and will be reduced by the total amount of the advanced payment(s) (EIPs) received. Any remaining credit will be allowed on the tax year 2020 return. Taxpayers who do not have a filing requirement and those who would not normally need to file but may be eligible for RRC MUST file a 2020 tax return to receive the RRC. Note: The tax year 2020 recovery rebate credit is not subject to offset for federal tax debts but is subject to offset for TOP debts. If the Non-Filers Tool was used to claim EIP 1, a simple return was filed for that taxpayer. When filing their 2020 tax return electronically, the taxpayer will need to enter $1 for the prior year AGI verification. If the Non-Filers Tool was not used to claim EIP 1 and the taxpayer did not file a tax year 2019 return, the taxpayer will need to enter $0 for the prior year AGI verification. The EIP 3 credit amount is up to $1,400 ($2,800 for MFJ), plus an additional $1,400 for each allowable dependent. The EIP 3 and tax year 2021 RRC are subject to phase out if the AGI on the return considered (2019, 2020 or 2021) exceeds the following income limitations: $150,000 for joint filers (filing status 2) $150,000 for qualifying widow(er) (filing status 5) $112,500 for head of household filers (filing status 4 or 7) $75,000 for all other filers Total phase out of EIP 3 occurs when the taxpayer's AGI meets or exceeds the applicable amount for their filing status: $160,000 for joint filers (filing status 2) $160,000 for qualifying widow(er) (filing status 5) $120,000 for head of household filers (filing status 4 or 7) $80,000 for all other filers When EIP 3 is subject to phase out, the reduction percentage will be determined using the taxpayer's AGI and filing status. The standard amounts to be used in the formula for computation are listed below: $10,000 for joint filers (filing status 2) $10,000 for qualifying widow(er) (filing status 5) $7,500 for head of household filers (filing status 4 or 7) $5,000 for all other filers The reduction percentage will be calculated using the formula below and will be applied to the total amount of the credit. Enter the AGI. Enter the income limitation for the filing status. If the amount in step a is more than the amount in step b, subtract the amount in step b from the amount in step a. Otherwise, enter zero. Divide the amount in step c by the applicable standard amount in paragraph (20) for the filing status on the return. If more than 100% (1.0), enter only 100%. This is the amount of the reduction percentage. See below for examples of calculating EIP 3 when phase out applies. Example: A taxpayer has not filed a TY 2020 return. The TY 2019 return is filed single with no dependents and an AGI of $77,000. This exceeds the $75,000 limitation, and EIP phase out applies. EIP 3: $77,000 − $75,000 = $2,000 Calculating the reduction percentage: $2,000 ÷ $5,000 = .4 (40%) Because the reduction percentage is less than 100%, an EIP 3 will be issued. Calculating the amount of the credit: $1,400 (maximum credit) × 40% (reduction percentage) = $560 (amount of reduction) $1,400 (maximum credit) − $560 (amount of reduction) = $840 (amount of EIP 3) Example: A TY 2020 return is filed married filing jointly with 2 qualifying dependents and an AGI of $155,000. The taxpayers and their dependents all have valid SSNs. The AGI exceeds the $150,000 limitation, and EIP phase out applies. EIP 3: $155,000 − $150,000 = $5,000 Calculating the reduction percentage: $5,000 ÷ $10,000 = .5 (50%) Because the reduction percentage is less than 100%, an EIP 3 will be issued. Calculating the amount of the credit: $1,400 × 4 = $5,600 $5,600 (maximum credit) × 50% (reduction percentage) = $2,800 (amount of reduction) $5,600 (maximum credit) − $2,800 (amount of reduction) = $2,800 (amount of EIP 3) Example: A TY 2020 return is filed head of household with 3 dependents and an AGI of $117,000. The primary taxpayer and dependents all have a valid SSN. The AGI exceeds the $112,500 limitation, and EIP phase out applies. EIP 3: $117,000 − $112,500 = $4,500 Calculating the reduction percentage: $4,500 ÷ $7,500 = .6 (60%) Because the reduction percentage is less than 100%, an EIP 3 will be issued. Calculating the amount of the credit: $1,400 × 4 = $5,600 $5,600 (maximum credit) × 60% (reduction percentage) = $3,360 (amount of reduction) $5,600 (maximum credit) − $3,360 (amount of reduction) = $2,240 (amount of EIP 3) Taxpayers will report the tax year 2021 recovery rebate credit on their tax year 2021 return. The credit will be calculated based on the 2021 tax return information using the EIP 3 criteria for phase out and will be reduced by the total amount of the advanced payment(s) (EIPs) received. Any remaining credit will be allowed on the tax year 2021 return. Taxpayers who do not have a filing requirement and those who would not normally need to file but may be eligible for RRC MUST file a 2021 tax return to receive the RRC. If the Non-Filers Tool was used to claim EIP 3, a simple return was filed for that taxpayer. When filing their 2021 tax return electronically, the taxpayer will need to enter $1 for the prior year AGI verification. If the Non-Filers Tool was not used to claim EIP 3 and the taxpayer did not file a tax year 2020 return, the taxpayer will need to enter $0 for the prior year AGI verification. Repayment is not required when a taxpayer received more advanced payment of the 2020 recovery rebate credit (EIP 1 + EIP 2) or more advanced payment of the 2021 recovery rebate credit (EIP 3) than they were entitled to. Caution: When a taxpayer receives an excess amount of Recovery Rebate Credit (RRC), repayment of the amount that exceeds what they are entitled to is required. See below for a list of examples that may result in the erroneous overpayment: • Taxpayer claimed an amount of RRC that was allowed and later amended their tax return • An employee input an adjustment that resulted in the excess amount (may require erroneous refund procedures) • The valid taxpayer received a refund issued based on an invalid tax return received

# Economic Impact Payment (EIP) - Account Research

25.23.4.20.1 (06-06-2022) Economic Impact Payment (EIP) - Account Research EIPs are issued from the tax module for the tax year of the applicable recovery rebate credit. The associated adjustment will include: TC 290 .00 Unique Reason Codes (RC) in positions 1, 2, 3, and/or 4 (defined below) TC 766 with Credit Reference Number (CRN) 338 for the amount attributable to the primary and secondary taxpayers, if applicable TC 766 with CRN 257 for the amount attributable to qualifying children (EIP 1 and EIP 2) or allowable dependents (EIP 3) HC 3 Note: Although the adjustment notice is suppressed, the taxpayer is issued a vendor notice approximately 15 days from the posting of the credit. Married Filing Joint (MFJ) accounts will reflect the transactions on both the primary and secondary modules. The adjustment on the primary module will include the significant amounts, and the adjustment on the secondary module will post with .00 amounts. MFJ accounts that included an Injured Spouse claim with the original return will reflect the transactions on both the primary and secondary tax year 2020 modules. Both taxpayers will be credited with half of the total EIP. Taxpayers who are ineligible to receive an EIP can be identified by the adjustment posted to the module. The adjustment will include: TC 290 .00 TC 766 CRN 338 .00 RC 1 and 2 will be 000; RC 3 will be populated Systemic adjustments include unique Reason Codes (RC). Refer to the following table for additional information: RC Position Description First Position This RC identifies the number of children/allowable dependents for which the payment was computed. RC 000-099 Second Position This RC is associated with the children/allowable dependents in the first position. RC 206 and 213 Third Position This RC is associated with the primary and secondary taxpayer(s). RC 200 - 203, 205, 206, and 209 Fourth Position This RC indicates a deceased taxpayer. RC 207 Refer to the table below to determine how the EIP was calculated: Reason Code (RC) Credit Reference Number (CRN) Description 200 338 No payment due to AGI phase out. 201 338 No payment due to the taxpayer being claimed on another return. 202 338 No payment due to TIN issues (an invalid primary and/or secondary SSN, invalid due to assignment date, and TIN requirements not met). (For EIP 1 and EIP 2: A TC 971 AC 166 in the entity identifies SSNs used for non-work purposes.) 203 338 No payment due to the filing of Form 1040-NR, Form 1040-PR, or Form 1040-SS. 205 338 Systemic catch-all that identifies when a payment cannot be issued, such as a refund less than $1 or SSA/RRB deceased individual. Note: RC 205 is also used when the payment was previously considered (including an amount for zero) and could be reduced or eliminated. For example, a single taxpayer received EIP 1 in the amount of $1,200 based on a tax year 2018 return. That taxpayer then files a MFJ return for tax year 2019. The payment resulting from the tax year 2019 return is reduced by the amount previously paid based on the tax year 2018 return. 206 338/257 Payment reduced due to AGI phase out. 207 338 Deceased taxpayer; payment issued to surviving spouse. 209 338 Taxpayer qualifies for the maximum amount. 211 257 EIP 1/EIP 2 Dependent 17 or over as of January 1, 2020 Date of death prior to 2019 Non-qualifying relationship present Dependent has an ITIN EIP 3 One or more dependents have an invalid SSN (Includes ITIN and invalid due to assignment date.) 213 257 All claimed children/allowable dependents qualify (for EIP 1 and EIP 2, children who qualified for CTC plus any children with an ATIN shown in the first four dependents positions on the return). 214 338/257 EIP split 50/50 between both spouses. (EIP 3) 215 338/257 EIP attributable to the primary taxpayer. (EIP 1 and EIP 3) 216 338/257 EIP attributable to the secondary taxpayer. (EIP 1 and EIP 3) 217 338 EIP 2 attributable to both spouses (50/50 split). 218 338 EIP 2 attributable to the primary taxpayer. 219 338 EIP 2 attributable to the secondary taxpayer. Note: The adjustment, including Reason Codes, can be viewed on CC IMFOLA. To prevent duplicate EIPs, a TC 971 AC 199 with a MISC field including "REB" in positions 14-16 is placed on the entity (CC IMFOLE) of taxpayers who have been issued an EIP 1. The TC 971 AC 199 identifies the source used to determine the taxpayer's eligibility (tax year 2019, tax year 2018, SSA, RRB, SSI, or VA). For a list of TC 971 AC 199 MISC descriptions related to EIP, see Exhibit 25.23.4-20, TC 971 AC 199 MISC Field Descriptions for Economic Impact Payments (EIPs). Taxpayers who do not have to file a return and will not receive an EIP based on income from SSA, RRB, SSI, or VA are able to update their direct deposit information using the Get My Payment tool. Direct deposit information entered in this tool can be identified by a TC 971 AC 199 with a MISC field reflecting the account number followed by the letters "EF" . Note: Accounts with direct deposit information updated using the Get My Payment tool and the EIP issued will reflect a separate TC 971 AC 199 for both actions. Note: The TC 971 AC 199 MISC field may also provide a reason why the EIP was not allowed. A TC 971 AC 199 with a MISC field including "ADDREB" in positions 11-16 is placed on the entity (CC IMFOLE) of taxpayers who have been issued an EIP 2. A TC 971 AC 199 with a MISC field including "2021AREBXXXX" with "REB" in positions 14-16 and "XXXX" representing the source used to determine eligibility is placed on the entity (CC IMFOLE) of taxpayers who have been issued an EIP 3. A TC 971 AC 199 with a MISC field including "2021AREBADJ" will identify adjustments to EIP 3 where the net adjustment is positive. A TC 971 AC 199 with MISC field including "2021ARVREB" will identify adjustments to EIP 3 where the net adjustment is negative. Refunds of EIP 1 can be identified by the following characteristics on CC IMFOLT for tax year 2020: Refund date in 2020 TC 846 with "99" in the 12th and 13th positions of the DLN (for most cases) Refunds of EIP 2 can be identified by the following characteristics on CC IMFOLT for tax year 2020: Refund date in January 2021 TC 846 with DLN NN25499905055Y Refunds of EIP 3 can be identified by the following characteristics on CC IMFOLT for tax year 2021: Refund date in 2021 (no earlier than March) TC 846 with Julian date 999 and "11" in the 12th and 13th positions of the DLN (for most cases) Pre-paid debit cards for EIP 3 can be identified by a TC 971 AC 199 with a MISC field "BFS DEBIT III" on the entity (CC IMFOLE). EIPs that have been returned will credit the module with a TC 740 or TC 841. These transactions will result in the systemic reversal of the credits creating the payment (i.e., CRN 338, etc.). Paper checks returned as undeliverable due to the address will be reissued once a new address is available. Exception: After cycle 202114, when IDRS CC IDT48 is used to credit the module with TC 841, the EIP related CRNs will not be systemically reversed. Reminder: When repayment of EIP is received, it may post with a TC 720; however, this may not result in systemic reversal of the credit. The TC 720 must be considered when determining if any portion of EIP was credited to the module. When a returned EIP is received while an adjustment to reverse EIP is pending, the adjustment input will unpost if the TC 740/841 posts first. If CC IDT48/IDT58 was input, the credit from the returned payment may result in an erroneous credit balance. Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments, for additional information. Eligibility for EIP 1/EIP 2 and account conditions that would postpone issuing the EIPs will be determined using tax year 2019 information when a return has posted. If a return for tax year 2019 has not been processed, only information for tax year 2018 will be considered (EIP 1 only). Determinations of eligibility and consideration of account conditions will not include information from both tax years. A postponed EIP will be systemically issued after all account conditions are resolved, when possible. When EIP 1/EIP 2 cannot be issued systemically, the taxpayer must claim the amount they are entitled to as part of the Recovery Rebate Credit (RRC) on their tax year 2020 return. EIP 1/EIP 2 is postponed if the tax module being considered contains at least one of the following conditions: The module contains a duplicate return freeze (-A Freeze). The module contains a TC 971 AC 199 with a miscellaneous field of AMWEX60033. The module contains a TC 570 with DLN NN27788888888Y. The module has a TC 971 AC 011. The module contains an unreversed TC 971 AC 129. The module contains a TC 841 with blocking series 77711, 77712, 77713, or 77714 with a posted TC 290 .00. The module contains a TC 740 with blocking series 99999 or 66666. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ The module contains a duplicate TIN (an unreversed TC 971 AC 151) followed by an adjustment backing out the return (TC 291 = TC 150 amount). EIP 1/EIP 2 is postponed if the taxpayer's entity contains at least one of the following conditions: The entity contains an unreversed TC 971 AC 522 with a miscellaneous field of "WI FA ALTRD" . ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ An account merge is in process. The entity contains an Undeliverable As Addressed (UAA), Undelivered Mail (UD), or bad address (BAD ADDR) indicator (for paper checks only). These indicators can be found on CC ENMOD to the right of the address, or on CC IMFOLE in the indicator field below the address. Eligibility for EIP 3 and account conditions that would postpone issuing this EIP will be determined using tax year 2020 information when a return has posted. If a return for tax year 2020 has not been processed, only information for tax year 2019 will be considered. Determinations of eligibility and consideration of account conditions will not include information from both tax years. A postponed EIP will be systemically issued after all account conditions are resolved, when possible. When EIP 3 cannot be issued systemically, the taxpayer must claim the amount they are entitled to as part of the Recovery Rebate Credit (RRC) on their tax year 2021 return. EIP 3 is postponed if the tax module being considered contains at least one of the following conditions: The 2020 module contains a TC 971 AC 199 with a miscellaneous field of AMWEX60033 unless a subsequent refund (TC 846) posted or a TC 972 AC 199 with a miscellaneous field of AMWEX60033 is present. The 2020 module contains a TC 570 with DLN NN27788888888Y and a -R Freeze. The module contains a duplicate return freeze (-A Freeze). The module contains an unreversed TC 971 AC 129 (ID Theft TPP) unless a subsequent refund (TC 846) posted. The module contains a tax return and a returned refund TC 841 with blocking series 77711, 77712, 77713, or 77714 unless a subsequent refund (TC 846) posted and a later dated TC 971 AC 199 MISC EF is posted (CC IMFOLE). The module contains a TC 740 with blocking series 99999 or 66666 (undeliverable address on paper check) unless a subsequent refund (TC 846) posted. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ The module contains a duplicate TIN (an unreversed TC 971 AC 151) followed by an adjustment backing out the return (TC 291 = TC 150 amount). EIP 3 is postponed if the taxpayer's entity contains at least one of the following conditions: The entity contains an unreversed TC 971 AC 522 with a miscellaneous field of "WI FA ALTRD" (ID Theft). ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ An account merge is in process. The entity contains an unreversed TC 971 AC 199 with a miscellaneous field of "XYZ TERRITORY" . The entity contains an unreversed TC 971 AC 199 with a miscellaneous field of "XYZ ZERO" .

# Economic Impact Payment (EIP) - Additional Research for Identity Theft (IDT) Cases

25.23.4.20.2 (12-20-2022) Economic Impact Payment (EIP) - Additional Research for Identity Theft (IDT) Cases Taxpayers who are victims of identity theft (IDT) may experience delays in receiving their Economic Impact Payment (EIP) or may not have received an EIP due to the identity theft issue. TC 971 AC 522 with MISC "WI FA ALTRD" was created and systemically placed on accounts with IDT to prevent the issuance of an EIP. All cases assigned to an IDT inventory must be reviewed to determine if an EIP was issued. If an EIP was issued, it is necessary to identify who received the payment. Caution: Each EIP must be considered separately. Do not assume all payments went to the same person. Caution: Do not assume EIP is not impacted, because the case is assigned for a tax year earlier than 2018, 2019, or 2020. Additional impacted modules may be identified through Complete Case Analysis (CCA). Review the posted TC 971 AC 199 on CC IMFOLE to locate the source used to determine eligibility: Tax year 2020 return information Tax year 2019 return information Tax year 2018 return information Social Security Administration (SSA) Railroad Retirement Benefits (RRB) Social Security Disability (SSDI) Veterans Administration (VA) When Form 14039 is filed due to non-receipt of an EIP based on a valid return, determine if the EIP was issued as direct deposit. If the EIP was issued as direct deposit, continue to paragraph (5) below. If the EIP was mailed, the case will be worked as non-tax-related IDT. Refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, for specific procedures. Example: The taxpayer files Form 14039 reporting the Get My Payment Tool says their EIP was mailed on January 6, 2021. They believe someone else stole it from their mail. Your research indicates there is no invalid return and the EIP was mailed. This case will be resolved as an IDT4. Use the table below to determine who received the EIP when the source used to determine eligibility was the return information for tax year 2020, 2019, or 2018, the refund was issued or offset to child support, and the case is impacted by identity theft. Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments, for required case actions. Caution: When direct deposit information has been updated using the Child Tax Credit Update Portal (CTCUP) or Get My Payment (GMP), subsequent refunds released from the tax year 2021 module will be issued via direct deposit to that account, unless the indicator has been reversed with a TC 972. A TC 971 AC 850 will not flip payments to paper after the CTCUP has been used to update direct deposit information. You can identify CTCUP direct deposit information updates by a TC 971 AC 199 with the MISC field providing the bank/routing information followed by "EF" (20 positions) posted on the taxpayer's entity. The Julian Date will be 999, and the Blocking Series will be 77777. If And Then (1) The CTCUP/GMP was used to update the direct deposit information, Note: If the taxpayer states they did not update the information using the CTCUP/GMP, see scenario (3) below. EIP was issued by direct deposit after the update occurred, The valid taxpayer did receive their EIP. (2) The CTCUP/GMP was used to update the direct deposit information, EIP was issued by direct deposit or paper check before the update occurred, Use scenarios (5) - (16) below to determine who received the EIP. (3) The taxpayer states they did not use the CTCUP/GMP to update their direct deposit information or the taxpayer indicates an individual assisting them with using the tool input bank account information that does not belong to them, EIP was issued by direct deposit after the update occurred, The valid taxpayer did not receive their EIP. (4) The taxpayer states they did not use the CTCUP/GMP to update their direct deposit information, EIP was issued by direct deposit or paper check before the update occurred, Use scenarios (5) - (16) below to determine who received the EIP. (5) One return IDT determination, EIP was issued by direct deposit, The valid taxpayer did not receive their EIP. (6) One return IDT determination, EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (7) Invalid/Valid determination, EIP was issued by direct deposit, The valid taxpayer did not receive their EIP. (8) Invalid/Valid determination, EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (9) Valid/Invalid determination OR One valid return/no invalid return, EIP was issued by direct deposit, The valid taxpayer did receive their EIP. Note: Direct deposit information updated prior to the EIP being issued may be the result of IDT. Review the taxpayer's claim for any statement indicating the direct deposit information is not theirs. (10) Valid/Invalid determination, EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (11) Invalid/Invalid determination, EIP was issued by direct deposit, The valid taxpayer did not receive their EIP. (12) Invalid/Invalid determination, EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (13) Income-related IDT determination (no invalid return), EIP was issued by direct deposit, The valid taxpayer received their EIP. (14) Income-related IDT determination (no invalid return), EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (15) Dependent-related IDT determination, EIP was issued by direct deposit or paper check, The EIP amount attributable to the dependent was issued to the incorrect taxpayer, unless the payment was issued on the dependent's account after the valid taxpayer used the CTCUP to update the direct deposit information. (16) Taxpayer is not impacted by IDT (i.e., MXEN, IJE, etc.) EIP was issued. Additional research is necessary. Continue to paragraph (7) below. Note: You can determine if the EIP was issued via direct deposit or by mail by reviewing the DD indicator posted with the TC 846. The EIP was issued as direct deposit if the indicator is "9" and mailed if the indicator is "0" . Reminder: If the valid taxpayer has a child support obligation, some or all of the EIP 1 will offset to that debt. Caution: Addresses on taxpayers' accounts may have been updated multiple times throughout the pandemic. In an effort to ensure determinations of receipt are correct, it is suggested IDRS CC FINDS is used to compare address updates with the cycle date of the TC 846 for the refund in question. This CC provides a long-term history of the taxpayer's address and cycle dates for each change. If the source used to determine eligibility was SSA, RRB, SSDI, or VA, the EIP was issued as direct deposit or paper check to the valid taxpayer, depending on how the taxpayer normally receives their benefits. Certain accounts not impacted by IDT are also required to be reviewed. use the table below to determine who received the EIP when the source used to determine eligibility was the return information for tax year 2020, 2019, or 2018, the refund was issued or offset to child support, and the case is not impacted by identity theft. Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments, for required case actions. If And Then (1) MXEN determination, EIP was issued, Refer to IRM 21.6.2.4.7, Economic Impact Payment (EIP) and Multiple Taxpayers Using the Same TIN. (2) IJE determination, EIP was issued by direct deposit, The valid taxpayer did not receive their EIP, unless the payment was issued after the CTCUP was used by the reporting taxpayer to update the direct deposit information. (3) IJE determination, EIP was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. EIPs issued on accounts with non-tax-related IDT and NO IDT determinations (excluding the scenarios in paragraph (7) above) may require specific actions to address the EIP. For additional information, refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, or IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, as applicable. When the taxpayer erroneously used the Non-Filers Tool and filed an additional return to correct their account, refer to IRM 21.5.3.4.17, Amended Economic Impact Payment (EIP) Return. Refer to IRM 25.23.4.20.1, Economic Impact Payment (EIP) - Account Research, paragraph (6) for the reason codes that will be used for manual adjustments to EIP. These adjustments may also include reason code (RC) 000. Manual adjustments using the CRNs for EIP create a systemic TC 971 AC 199 posted to the entity. The MISC field will reflect the following literals: REBADJ - Additional EIP allowed REVREB - EIP reversed or reduced

# Economic Impact Payment (EIP) Referrals - Coordinator Duties

25.23.4.20.2.1 (06-06-2022) Economic Impact Payment (EIP) Referrals - Coordinator Duties IDTVA receives referrals for EIP adjustments on accounts impacted by identity theft. These referrals are submitted with Form 4442, Inquiry Referral, and received for the following account conditions: The EIP was issued to the invalid taxpayer after receipt of a fraudulent return. The EIP was issued to the valid taxpayer in an amount that is incorrect and was computed using information from a fraudulent return. (Based on the valid taxpayer's return, the EIP the taxpayer is entitled to is more than the amount of EIP received.) Note: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. Form 4442 referrals for EIP adjustments include the following information in addition to the taxpayer's TIN, name, address, and phone number: Issue: Refund Inquiry Referral Type: IRM Category: Other - Write-In; The write-in description will be "EIP Adj - Scenario 2" Reason: Other or Complex Issue/Training Specialization Notes: A detailed description of the adjustment that needs to be made on the account will be provided. Accounts with referrals for identity theft EIP adjustments have an open IDRS control base on the 2020 module reflecting: Activity Code:"EIP-SCEN2" Status: B Category Code: TPPI Assignment to IDRS Number: 0130076221 All EIP adjustment referrals are sent to Brookhaven for tracking and distribution. All EIP adjustments related to identity theft must be made by an IDTVA employee. Brookhaven will forward EIP Adj – Scenario 2 referrals to IDTVA via EE-fax and/or provide account information in a listing. EIP adjustment referrals must be reviewed for accuracy. Screening of EIP Adj – Scenario 2 referrals is required to verify appropriate assignment to IDTVA and will be completed the same day the referral is received. Complete the following research to screen the referrals: Review the Form 4442 for details about the taxpayer's specific IDT issue. Review AMS history items to confirm the referral is the result of a phone call from the taxpayer. Use AMS, CII, and/or IDRS to verify there is an identity theft issue. Search CII to determine if there is an open identity theft case. Note: When working from a listing to screen referrals, review the completed referral in AMS. A link will be available under the Alerts heading. Erroneous referrals received in IDTVA must be returned to Brookhaven within one business day of identifying the referral does not meet Scenario 2 criteria. Take the following actions to reject erroneous referrals: Exception: Referrals indicating an identity theft issue that did not result in the issuance of an EIP (i.e., no TC 846 on the module) will not be rejected. The valid taxpayer's identity theft issue must be resolved to ensure they receive any amount of EIP they are entitled to. Update the IDRS control base on the 2020 module using: • Activity Code:"REJ-SCEN2" • Status: B • Category Code: TPPI • IDRS Number: 0130076221 Add an AMS history item documenting the research completed and the results of the research (i.e., no invalid return, etc.). Under the notes section of Form 4442, leave a brief description of the results (i.e., Reject - No IDT issue, etc.). After taking each of the previous actions, return the referral to Brookhaven via EE-fax to 877-817-5268. Upon completion of the necessary research, complete all applicable actions as described in the table below to prepare correct referrals for assignment: If Then (1) There is an existing CII case, Update the category code to IDT1/IDS1 (or appropriate category code) if the case is currently assigned as IDT3/IDS3. If the case is assigned to an IDTVA Specialty Function, do not update the category code. Attach the Form 4442 to the CII case as a .pdf. Note: When working from a listing, you must print the Form 4442 located in AMS as a .pdf to attach it to the CII case. Add a CII case note to document the date the referral was received. Close the TPPI IDRS control base as MISC. (2) There is not an existing CII case, Create a CII case in category code IDT1/IDS1. Use the received date of Form 4442 as the IRS received date for the case. Attach the Form 4442 to the CII case as a .pdf. Note: When working from a listing, you must print the Form 4442 located in AMS as a .pdf to attach it to the CII case. Add a CII case note to document the date the referral was received. Close the TPPI IDRS control base as MISC. After preparing the referrals for assignment, distribute the EIP referrals inventory for resolution.

# Economic Impact Payment (EIP) - Adjustments - General

25.23.4.20.3 (10-01-2025) Economic Impact Payment (EIP) - Adjustments - General The credits and refunds of EIPs can be seen on the applicable tax module: EIP 1/EIP 2: Tax year 2020 module (tax year 202101 – 202111 for fiscal year filers). EIP 3: Tax year 2021 module (tax year 202201 – 202211 for fiscal year filers). When systemic consideration of EIP determines the taxpayer is ineligible, CC IMFOLT will reflect a TC 290 .00 only. Credits post with a TC 766 if adding/increasing the credit or TC 767 if removing/decreasing the credit. When adjusting the amount of EIP, the following Credit Reference Numbers (CRNs) will be used: 338 - The amount is attributable to the primary and secondary taxpayer, if applicable. 257 - The amount is attributable to qualifying children/allowable dependents. The CRN(s) used to adjust EIP will be determined by the facts and circumstances of the case. When inputting an adjustment to EIP using only CRN 338, the Reason Codes (RCs) used in the first and second positions must both be 000. This leaves the third position open for the RC that best describes the reason for the adjustment. When inputting an adjustment to EIP that includes CRN 257, the RC in the first position must indicate the number of dependents associated with the adjustment (i.e., RC 002 would be used when there are 2 dependents involved). The second and third positions may be used for additional RCs related to the adjustment. A separate adjustment will be input to mark the account with RC 139. Note: Adjustments for EIPs on the same module must be input separately. Use posting delays, as necessary. Note: On accounts where the taxpayer has different spouses for 2018 and 2019, the "XREF – TIN" field on CC ADJ54 can be used to ensure the adjustment is pointed to the appropriate spouse. Use the following RCs when adjusting the amount of EIP: Note: The following reason codes must be in the third position. Reason Code (RC) Credit Reference Number (CRN) Description 214 338/257 EIP split 50/50 between both spouses (EIP 1 and EIP 3) 215 338/257 EIP 1 attributable to the primary taxpayer (EIP 1 and EIP 3) Note: This RC will also be used for taxpayers with a filing status other than MFJ. 216 338/257 EIP 1 attributable to the secondary taxpayer (EIP 1 and EIP 3) 217 338 EIP 2 attributable to both spouses (50/50 split) 218 338 EIP 2 attributable to the primary taxpayer Note: This RC will also be used for taxpayers with a filing status other than MFJ. 219 338 EIP 2 attributable to the secondary taxpayer In addition to the EIP specific RCs, when a secondary TC 290 .00 is required use RC 139 to indicate this was an identity theft case. When inputting an adjustment to reduce EIP, use CRN 338. If the amount exceeds the credit posted with the TC 766 CRN 338, use CRN 257 to adjust the remainder. Example: The tax year 2021 module currently reflects an EIP 3 issued with the following credits posted: • TC 766 CRN 338 for $1,400.00 • TC 766 CRN 257 for $2,800.00 The valid taxpayer's 2020 return filing status is Head of Household with two allowable dependents and an AGI of $118,250. The taxpayer and dependents all have valid SSNs. The following actions will be taken to correct the account based on the valid taxpayer's return information: Calculate the reduction percentage: $118, 250 - $112,500 = $5,750 $5,750 ÷ $7,500 = 0.767 (76.7%) Calculate the amount of the credit: $1,400 × 3 = $4,200 $4,200 (maximum credit) × 76.7% (reduction percentage) = $3,221.40 The taxpayer is entitled to EIP 3 in the amount of $978.60 ($4,200 - $3,221.40) The adjustment input to correct the EIP 3 will include: • CRN 338 for $1,400.00- • CRN 257 for $1,821.40- When the IDT case is for TY 2019 or TY 2020 and may affect the calculation or issuance of Advanced Child Tax Credit (AdvCTC) payments, a determination of impact must be made prior to following the procedures below. Refer to the table below for exceptions to procedures based on the determination of impact: Determination of Impact Exceptions (1) There are no AdvCTC payments on the module None (2) All AdvCTC payments were issued to the valid taxpayer None (3) All AdvCTC payments were issued to the invalid taxpayer OR The valid and invalid taxpayers both received at least one AdvCTC payment The appropriate IDT closing indicator must not be input until the AdvCTC payments are resolved. These indicators cannot be input until the taxpayer is no longer harmed by the IDT issues. Refer to IRM 25.23.2.6, Closing Identity Theft Issues, for additional information. Required case closure correspondence must not be issued prior to the completion of all account actions. Refer to IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. The CII case must remain open until all necessary actions have been taken. Follow procedures in IRM 25.23.4.21.2.1, ARPA - Advanced Child Tax Credit (AdvCTC) - Identity Theft Research and Account Actions, to ensure AdvCTC payments are addressed appropriately. Reminder: One closing letter may be issued to address all additional information the taxpayer needs (i.e., how to claim RRC and details about the AdvCTC). When it is determined IDT (or IJE) affected EIP 1 and/or EIP 2, the tax year 2020 Recovery Rebate Credit (RRC) must also be addressed when the 2020 module reflects tax return information. When it is determined IDT (or IJE) affected EIP 3, the tax year 2021 RRC must also be addressed when the 2021 module reflects tax return information. Refer to IRM 25.23.4.20.4, Recovery Rebate Credit (RRC) - Identity Theft (IDT) Case Research, and IRM 25.23.4.20.5, Recovery Rebate Credit (RRC) - Adjustments, for additional information. When the affected module does not reflect tax return information, continue with the procedures in the applicable reference(s): IRM 25.23.4.20.3.1, Economic Impact Payment (EIP) - Adjustments - EIP 1/EIP 2 IRM 25.23.4.20.3.2, Economic Impact Payment (EIP) - Adjustments - EIP 3

# Economic Impact Payment (EIP) - Adjustments - EIP 1/EIP 2

25.23.4.20.3.1 (10-01-2025) Economic Impact Payment (EIP) - Adjustments - EIP 1/EIP 2 EIP 1/EIP 2 will be adjusted on the tax year 2020 module (tax year 202101 – 202111 for fiscal year filers). Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments - General, to determine appropriate Credit Reference Numbers (CRNs) and Reason Codes (RCs) to be used when adjusting EIP 1 and/or EIP 2. Refer to IRM 25.23.4.20.2, Economic Impact Payment (EIP) - Additional Research for Identity Theft (IDT) Cases, to determine who received each EIP issued. Reminder: A secondary TC 290 .00 will not be input when a TC 150 return has not been received. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. When EIP was issued to the invalid taxpayer via direct deposit, input TC 971 AC 850 to flip future refunds to paper. Post delay adjustments, as needed. When EIP 1 and/or EIP 2 was computed based on a valid return (or benefits when an exception applies) but was issued to the invalid taxpayer due to direct deposit information being updated, take the following actions: Reminder: Adjustments to EIP 1 and EIP 2 must be input separately. Note: If any amount of the EIP was offset to a child support obligation, follow procedures in paragraph (3) below. Input TC 971 AC 850. Adjust the account to remove the EIP. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. Post delay this adjustment by 1 cycle. If adjusting both EIP 1 and EIP 2, post delay the second adjustment by 2 cycles. Input a second TC 290 .00 with BS 05, SC 0, HC 3, and RC 139. Post delay the adjustment by 2 cycles. If adjusting both EIP 1 and EIP 2, post delay the third adjustment by 3 cycles. Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve EIPs issued to the invalid taxpayer. When the EIP was computed based on an invalid (IDT) return or invalid joint election (IJE) and the payment (in whole or part) was offset to a child support debt, take the following actions: Determination for the Tax Year used for EIP Eligibility Valid Taxpayer Tax Year 2020 Module and Entity Actions (1) One return IDT Invalid/Valid Invalid/Invalid OR The reporting taxpayer was listed as the primary taxpayer on an IJE return. All of the original EIP was offset to a child support obligation, or Some of the original EIP was offset to a child support obligation and only the reporting taxpayer received the portion of the original EIP in excess of the amount offset to child support. Input TC 290 .00 with BS 05, SC 0, and HC 3. Use RC 139 for IDT cases. Use RC 099 for IJE cases. Refer to paragraph (8) below for letter requirements. Reminder: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. This includes an offset to a child support debt. (2) One return IDT Invalid/Valid Invalid/Invalid OR The reporting taxpayer was listed as the primary or secondary taxpayer on an IJE return Some of the original EIP was offset to a child support obligation and only the non-owner of the CN received the portion of the original EIP in excess of the amount offset to child support. Reduce the amount of EIP on the module to reflect the exact amount of EIP applied to the child support obligation. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. For IDT cases, input a second TC 290 .00 with BS 05, SC 0, HC 3, and RC 139. Post delay the adjustment by one cycle. For IDT cases meeting streamline criteria, follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve the partially lost EIP issued to the invalid taxpayer. For IDT cases meeting non-streamline criteria, create a Dummy tax year 2020 module for the IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the IRSN. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. For IJE cases, create a Dummy tax year 2020 module for the other TIN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the other TIN. Refer to IRM 25.23.4.20.3.3 , Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. Reminder: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. This includes an offset to a child support debt. (3) Valid/Invalid determination OR One valid return/no invalid return, All of the original EIP was offset to a child support obligation, or Some of the original EIP was offset to a child support obligation and only the reporting taxpayer received the portion of the original EIP in excess of the amount offset to child support. Input TC 290 .00 with BS 05, SC 0, and HC 3. Use RC 139 for IDT cases. Use RC 099 for IJE cases. Refer to paragraph (8) below for letter requirements. Reminder: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. This includes an offset to a child support debt. (4) Valid/Invalid determination OR One valid return/no invalid return, Some of the original EIP was offset to a child support obligation and only the non-owner of the CN received the portion of the original EIP in excess of the amount offset to child support. Reduce the amount of EIP on the module to reflect the exact amount of EIP applied to the child support obligation. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. For IDT cases, input a second TC 290 .00 with BS 05, SC 0, HC 3, and RC 139. Post delay the adjustment by one cycle. For IDT cases meeting streamline criteria, follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve the partially lost EIP issued to the invalid taxpayer. For IDT cases meeting non-streamline criteria, create a Dummy tax year 2020 module for the IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the IRSN. Refer to IRM 25.23.4.20.3.3 , Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. For IJE cases, create a Dummy tax year 2020 module for the other TIN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the other TIN. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. Reminder: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. This includes an offset to a child support debt. Note: For any cases involving an EIP offset to a child support obligation (in whole or part) that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP - Child Support Offset" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. When EIP 1 and/or EIP 2 was computed based on an invalid (IDT) return meeting streamline criteria and a child support offset is not involved, take the following actions: Determination for the Tax Year used for EIP Eligibility Valid Taxpayer Tax Year 2020 Module and Entity Actions (1) One return IDT Invalid/Valid Invalid/Invalid Did receive the EIP (in whole or part), If the invalid taxpayer received a portion of the EIP, reduce the amount of EIP on the module to reflect the exact amount of EIP received by the valid taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input. Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve the EIP 3 payment issued to the invalid taxpayer. Refer to paragraph (8) below for letter requirements. (2) One return IDT Invalid/Valid Invalid/Invalid Did not receive any portion of the EIP, Adjust the account to remove the EIP. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund).. Post delay the adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve EIPs issued to the invalid taxpayer. Refer to paragraph (8) below for letter requirements. Note: For any streamline cases involving EIP 1 and/or EIP 2 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP - Streamline" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. When EIP 1 and/or EIP 2 was computed based on an invalid (IDT) return meeting non-streamline criteria and a child support offset is not involved, take the following actions: Determination for the Tax Year used for EIP Eligibility Valid Taxpayer Tax Year 2020 Module and Entity Actions (1) One return IDT Invalid/Valid Invalid/Invalid AND Did receive the EIP (in whole or part), If the invalid taxpayer received a portion of the EIP, reduce the amount of EIP on the module to reflect the exact amount of EIP received by the valid taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). If the invalid taxpayer received a portion of the EIP, create a Dummy tax year 2020 module for the assigned IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the lost EIP TC 846 to the IRSN module. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) – Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. (2) One return IDT Invalid/Valid Invalid/Invalid Did not receive any portion of the EIP, Adjust the account to remove the EIP. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Create a Dummy tax year 2020 module for the assigned IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the IRSN module. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. Note: For any non-streamline cases involving EIP 1 and/or EIP 2 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP - Non-Streamline" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. When EIP 1 and/or EIP 2 was computed based on an invalid return meeting invalid joint election (IJE) criteria and a child support offset is not involved, take the following actions Determination for the Tax Year used for EIP Eligibility CN Owner Tax Year 2020 Module and Entity Actions (1) IJE - Reporting person was listed as the primary taxpayer. Did not receive any portion of the EIP, Adjust the account to remove the EIP. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Create a Dummy tax year 2020 module for the secondary TIN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the secondary TIN. Input TC 470 CC 90 with post delay 2 on the 2020 module for the secondary taxpayer. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. (2) IJE Did receive the EIP (in whole or in part), If the reporting taxpayer received a portion of EIP, reduce the amount of EIP on the module to reflect the exact amount of EIP received by the reporting taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. If necessary, create a Dummy tax year 2020 module for the secondary TIN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP to the 2020 module for the secondary TIN. Input TC 470 CC 90 with post delay 2 on the 2020 module for the secondary taxpayer. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (8) below for letter requirements. Reminder: Repayment of any amount of EIP the taxpayer received in excess of the amount they are entitled to will not be requested. (3) IJE - Reporting person was listed as the secondary taxpayer. Did not receive any portion of EIP 3, Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Input TC 592 on the secondary account to separate the taxpayers. Refer to paragraph (8) below for letter requirements. Note: For any IJE cases involving EIP 1 and/or EIP 2 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP - IJE" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Refer to the table below for additional letter requirements specific to EIP 1 and/or EIP 2 issues: If Then (1) Corresponding with a taxpayer who did not receive EIP 1 and/or EIP 2, Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer we cannot issue EIP. You may use the paragraph below or similar verbiage: "We are unable to issue your Economic Impact Payment (EIP) at this time. All advance payments of EIP 1 and EIP 2 were issued by January 15, 2021." (2) Corresponding with a taxpayer who did receive EIP 1 and/or EIP 2, Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer they previously received EIP. You may use the paragraph below or similar verbiage: "Our records show you received a total of $X,XXX.XX from the Economic Impact Payment(s) issued to you. All advance payments of EIP 1 and EIP 2 were issued by January 15, 2021." Input the amount of the payment in place of the X's. When an EIP 1 and/or EIP 2 has been returned (in whole or part) and the systemic reversal of the credits posted, follow the applicable procedures in paragraphs (2) - (8) above. Caution: When an adjustment is unpostable due to the posting of a systemic reversal from a returned EIP, verify the systemic adjustment fully addresses the EIP issue before closing your unpostable control. Take any necessary actions when the systemic reversal does not fully resolve the EIP issue (i.e., addressing a partially lost refund, etc.).

# Economic Impact Payment (EIP) - Adjustments - EIP 3

25.23.4.20.3.2 (10-01-2025) Economic Impact Payment (EIP) - Adjustments - EIP 3 EIP 3 will be adjusted on the tax year 2021 module (tax year 202201 – 202211 for fiscal year filers). Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments - General, to determine appropriate Credit Reference Numbers (CRNs) and Reason Codes (RCs) to be used when adjusting EIP 1 and/or EIP 2. Refer to IRM 25.23.4.20.2, Economic Impact Payment (EIP) - Additional Research for Identity Theft (IDT) Cases, to determine who received the EIP 3. Reminder: A secondary TC 290 .00 will not be input when a TC 150 return has not been received. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. When EIP 3 was issued to the invalid taxpayer via direct deposit, input TC 971 AC 850 to flip future refunds to paper. Post delay adjustments, as needed. When EIP 3 was computed based on a valid return (or benefits when an exception applies) but was issued to the invalid taxpayer due to direct deposit information being updated, take the following actions: Input TC 971 AC 850. Adjust the account to remove the EIP. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. Post delay this adjustment by 1 cycle. Input a second TC 290 .00 with BS 05, SC 0, HC 3, and RC 139. Post delay this adjustment by 2 cycles. Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve EIPs issued to the invalid taxpayer. For cases that meet streamline criteria for the tax year EIP 3 was based on, follow the procedures outlined in the table below according to the determination you have made: Determination for the Tax Year used for EIP 3 Eligibility Valid Taxpayer Tax Year 2021 Module and Entity Actions (1) One return IDT Invalid/Valid Invalid/Invalid Did receive EIP 3 (in whole or part) If the invalid taxpayer received a portion of EIP 3, reduce the amount of EIP 3 on the module to reflect the exact amount of EIP 3 received by the valid taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay the adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve the EIP 3 payment issued to the invalid taxpayer. See paragraph (7) below for letter requirements. (2) One return IDT Invalid/Valid Invalid/Invalid Did not receive any portion of EIP 3 Adjust the account to remove the EIP 3. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds, to resolve the EIP 3 payment issued to the invalid taxpayer. See paragraph (7) below for letter requirements. Note: For any streamline cases involving EIP 3 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP 3 - Streamline" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. For cases that meet non-streamline criteria for the tax year EIP 3 was based on, follow the procedures outlined in the table below according to the determination you have made: Determination for the Tax Year used for EIP 3 Eligibility Valid Taxpayer Tax Year 2021 Module and Entity Actions (1) One return IDT Invalid/Valid Invalid/Invalid Did receive EIP 3 (in whole or part) If the invalid taxpayer received a portion of EIP 3, reduce the amount of EIP 3 on the module to reflect the exact amount of EIP 3 received by the valid taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay this adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Create a Dummy tax year 2021 module for the assigned IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the lost EIP 3 TC 846 to the IRSN module. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. See paragraph (7) below for letter requirements. (2) One return IDT Invalid/Valid Invalid/Invalid Did not receive any portion of EIP 3 Adjust the account to remove the EIP 3. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay the adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Create a Dummy tax year 2021 module for the assigned IRSN. Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the lost EIP 3 TC 846 to the IRSN module. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. See paragraph (7) below for letter requirements. Note: For any non-streamline cases involving EIP 3 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP 3 - Non-Streamline" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. For cases that meet invalid joint election (IJE) criteria for the tax year EIP 3 was based on, follow the procedures outlined in the table below according to the determination you have made: Determination for the Tax Year used for EIP 3 Eligibility Valid Taxpayer Tax Year 2021 Module and Entity Actions (1) IJE - Reporting person is listed as the primary taxpayer, Did not receive any portion of EIP 3 Adjust the account to remove the EIP 3. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay the adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Create a Dummy tax year 2021 module for the other taxpayer's TIN. Then follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP 3 TC 846 to the 2021 module for the other taxpayer's TIN. Input TC 470 CC 90 with post delay 2 on the 2021 module for the other taxpayer. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. See paragraph (7) below for letter requirements. (2) IJE - Reporting person is listed as the primary taxpayer. Did receive EIP 3 (in whole or part) If the reporting taxpayer received a portion of EIP, reduce the amount of EIP 3 on the module to reflect the exact amount of EIP 3 received by the reporting taxpayer. Input TC 290 .00 with BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. If TC 971 AC 850 was input, post delay the adjustment by 1 cycle. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3 (4 if issuing a manual refund). Post delay this adjustment by 1 cycle (2 cycles if TC 971 AC 850 was input). Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. If necessary, create a Dummy tax year 2021 module for the other taxpayer's TIN. Then follow procedures in IRM 21.5.2.4.23.10, Moving Refunds, to move the EIP 3 TC 846 to the 2021 module for the other taxpayer's TIN. Input TC 470 CC 90 with post delay 2 on the 2021 module for the other taxpayer. Refer to IRM 25.23.4.20.3.3, Economic Impact Payment (EIP) - Account Balancing Adjustments, to determine if additional actions are required to balance the accounts. Refer to paragraph (7) below for letter requirements. (3) IJE - Reporting person is listed as the secondary taxpayer. Did not receive any portion of EIP 3 Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Input TC 592 on the secondary account to separate the taxpayers. Refer to paragraph (7) below for letter requirements. Note: For any IJE cases involving EIP 3 that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "EIP 3 - IJE" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Refer to the table below for additional letter requirements specific to EIP 3 issues: If Then (1) Corresponding with a taxpayer who did not receive EIP 3, Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer we cannot issue EIP 3. You may use the paragraph below or similar verbiage: "We are unable to issue your Economic Impact Payment (EIP) at this time. All advance payments of EIP 3 were calculated by December 31, 2021." (2) Corresponding with a taxpayer who did receive EIP 3, Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer they previously received EIP 3. You may use the paragraph below or similar verbiage: "Our records show you received a total of $X,XXX.XX from the Economic Impact Payment issued to you. All advance payments of EIP 3 were calculated by December 31, 2021." Input the amount of the payment in place of the X's. When an EIP 3 has been returned (in whole or part) and the systemic reversal of the credits posted, follow the applicable procedures in paragraphs (2) – (7) above. Caution: When an adjustment is unpostable due to the posting of a systemic reversal from a returned EIP, verify the systemic adjustment fully addresses the EIP issue before closing your unpostable control. Take any necessary actions when the systemic reversal does not fully resolve the EIP issue (i.e., addressing a partially lost refund, etc.).

# Economic Impact Payment (EIP) - Account Balancing Adjustments

25.23.4.20.3.3 (10-01-2022) Economic Impact Payment (EIP) - Account Balancing Adjustments When manually adjusting EIP to resolve a non-streamline identity theft case or Invalid Joint Election (IJE) case, the account may need to be "balanced" by moving the EIP refund to the cross-reference account. When a refund is moved to the cross-reference account: The credit must be adjusted on both accounts. A TC 971 AC 195 must be manually updated to ensure IDRS reflects the correct amount of EIP received when a TC 971 AC 199 will not be systemically placed on the account. Manual adjustments may generate a systemic TC 971 AC 199 that can be found on IDRS CC IMFOLE. The MISC field will reflect: REBADJ - EIP allowed or increased (TY 2021 only) REVREB - EIP reversed or reduced (TY 2020 and 2021) Note: TC 971 AC 199 "REBADJ" does not generate systemically after cycle 202050. TC 971 AC 199 "REVREB" does generate systemically after cycle 202050. Note: The combined dollar amount associated with the TC 971 AC 199/195 is used to compute the Recovery Rebate Credit (RRC) on the TY 2020/2021 return. Input an adjustment to increase EIP on the "to" account. The total amount of the credit must equal the amount of EIP being moved. Include HC 4. Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) - Adjustments - General. Reminder: Adjustment to EIP 1 and EIP 2 must be input separately. When adjusting both EIP 1 and EIP 2, post delay the second adjustment by one cycle. When making a positive adjustment to EIP with HC 4, the manual input of TC 971 AC 195 entity transaction is required: Input TC 971 AC 195 on the "to" account using the "from" account TC 971 AC 199 entity information for the transaction date and MISC fields of the EIP being moved.

# Recovery Rebate Credit (RRC) - Identity Theft (IDT) Case Research

25.23.4.20.4 (06-06-2022) Recovery Rebate Credit (RRC) - Identity Theft (IDT) Case Research The credits and refunds of the Recovery Rebate Credit (RRC) can be seen on the applicable tax module. EIP 1/EIP 2: Tax year 2020 module (tax year 202101 – 202111 for fiscal year filers). EIP 3: Tax year 2021 module (tax year 202201 – 202211 for fiscal year filers). Credits post with a TC 766 if adding/increasing the credit or TC 767 if removing/decreasing the credit. When adjusting the amount of RRC, the following will be used: CRN 256 RC 096 Note: Corrections to Tax Year 2021 RRC will be made by resolving EIP 3 until tax year 2021 returns are filed. Refer to IRM 25.23.4.20.3, Economic Impact Payment (EIP) – Adjustments, for procedures to address EIP 3. Refer to IRM 21.6.3.4.2.14.2, RRC Taxpayer Notice Codes (TPNC), for information regarding letters issued to taxpayers as a result of an RRC related math error. After making a CN ownership determination, use the table below to determine who received the RRC based on the filing of a 2020/2021 tax return: Note: If the RRC (in whole or part) was applied to a tax obligation owed by the valid taxpayer (or spouse if MFJ) or offset to a TOP debt, consider that portion as received by the valid taxpayer. Use the table below to determine who received the payment when the account reflects an offset and a refund. If And Then (1) One return IDT determination, The refund was issued by direct deposit, The valid taxpayer did not receive the RRC. (2) One return IDT determination, The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (3) Invalid/Valid determination, The refund was issued by direct deposit, The valid taxpayer did not receive the RRC. (4) Invalid/Valid determination, The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (5) Valid/Invalid determination, The refund was issued by direct deposit, The valid taxpayer did receive the RRC. (6) Valid/Invalid determination, The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (7) Invalid/Invalid determination, The refund was issued by direct deposit, The valid taxpayer did not receive the RRC. (8) Invalid/Invalid determination, The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (9) Income-related IDT determination (no invalid return), The refund was issued by direct deposit, The valid taxpayer did receive the RRC. (10) Income-related IDT determination (no invalid return), The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (11) Taxpayer is not impacted by IDT (i.e., MXEN, IJE, etc.) The refund was issued, Additional research is necessary. Continue to paragraph (6) below. Note: You can determine if the refund was issued via direct deposit or by mail by reviewing the DD indicator posted with the TC 846. The refund was issued as direct deposit if the indicator is "9" and mailed if the indicator is "0" . Caution: Addresses on taxpayers' accounts may have been updated multiple times throughout the pandemic. In an effort to ensure determinations of receipt are correct, it is suggested IDRS CC FINDS is used to compare address updates with the cycle date of the TC 846 for the refund in question. This CC provides a long-term history of the taxpayer's address and cycle dates for each change. Certain accounts not impacted by IDT are also required to be reviewed. Use the table below to determine who received the refund when the case is not impacted by identity theft. If And Then (1) MXEN determination, The refund was issued, Refer to IRM 21.6.2.4, TIN-Related Problems Procedures. (2) IJE determination, The refund was issued by direct deposit, The valid taxpayer did not receive the RRC. (3) IJE determination, The refund was issued by paper check or pre-paid debit card, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. Refer to IRM 25.23.4.20.5, Recovery Rebate Credit (RRC) - Adjustments, to adjust the RRC when identity theft is involved or an IJE determination has been made.

# Recovery Rebate Credit (RRC) - Adjustments

25.23.4.20.5 (10-01-2025) Recovery Rebate Credit (RRC) - Adjustments Prior to inputting an adjustment for tax year 2020/2021 RRC: Determine if the valid taxpayer(s) received any amount from posted Economic Impact Payment(s). Consider any undelivered or returned payments, the secondary TP's account, and offsets when making this determination. Math verify the amount of RRC reported on the valid TY 2020/2021 return. Refer to IRM 25.23.4.20, Economic Impact Payment (EIP) and Recovery Rebate Credit (RRC) – General, for eligibility criteria and limitations. You may also use the Recovery Rebate Credit Worksheet in AMS for tax year 2020 or 2021 Worksheets for assistance in calculating or verifying the valid taxpayer's correct amount of RRC. Reminder: The amount of the RRC is calculated using the FS, number of qualifying children, and AGI from the tax year 2020/2021 return and is reduced by the total amount received from EIP 1 and/or EIP 2 for tax year 2020 and EIP 3 only for tax year 2021. See the tax year 2020 Form 1040 Instructions or tax year 2021 Form 1040 Instructions for additional information. Credit Reference Number (CRN) 256 and Reason Code (RC) 096 will be used when adjusting RRC. When you have determined the TC 150 return is invalid, input TC 971 AC 850 when direct deposit information was included on the return. Update the entity to reflect the valid taxpayer's correct address. Use appropriate posting delay codes to ensure TC 971 AC 850 and address updates post before account actions that will result in a refund. EIP and RRC refunds issued to the invalid taxpayer will be resolved following normal lost refund procedures applicable for the case type (i.e., streamline, non-streamline, or IJE). Refer to the list below for determinations that will require RRC to be addressed: One Valid Return - When EIP 1 and/or EIP 2 was based on TY 2018/2019 IDT (TY 2020 RRC) One Valid Return - When EIP 3 was based on TY 2019/2020 IDT (TY 2021 RRC) Valid/Invalid - When EIP 1 and/or EIP 2 was based on TY 2018/2019 IDT (TY 2020 RRC) Valid/Invalid - When EIP 3 was based on TY 2019/2020 IDT (TY 2021 RRC) One Invalid Return Invalid/Valid Invalid/Invalid When it is determined the taxpayer does not qualify for RRC, has not received any amount (including advance payments), and did not claim RRC on their valid return, input the adjustment(s) to fully back out the credit(s) for EIP. Include BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. Reduce any posted amount of RRC when adjusting the account to the valid return. If RC 139 is not included with the adjustment to the valid return figures, a separate TC 290 must be input to ensure the account reflects RC 139. Post delay the adjustments, as needed. Reminder: Each EIP credit must be adjusted separately, and lost refunds will be addressed following normal procedures for the case type. When it is determined the taxpayer has received the correct amount of RRC (including advance payments) and did not include any amount of RRC on their return, RRC must be addressed to remove any posted amount claimed on an invalid TC 150 return. When it is determined the correct amount of RRC is included on the valid return and the valid taxpayer has received less RRC than they are entitled to, including any advance payment(s), the account will be adjusted to reflect the correct amount, as allowable. If the valid return posted as the TC 150 return and reflects math errors related to RRC, refer to paragraph (10) below. Reminder: Lost refunds will be addressed following normal procedures for the case type. If Then (1) The taxpayer qualifies for RRC and has not received any amount (including advance payments), Input adjustment(s) to fully back out the credits for EIP. Include BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. Post delay the adjustment, if necessary. Reminder: TY 2020 - EIP 1 and EIP 2 must be adjusted separately if both are present. Adjust the RRC, as appropriate, to ensure the module reflects the total amount the taxpayer is entitled to. Include BS 05, SC 0, and HC 3 (HC 4 if issuing a manual refund). Post delay the adjustment, if necessary. Note: If RC 139 is not included with this adjustment, a separate TC 290 must be input to ensure the account reflects RC 139. (2) The taxpayer qualifies for RRC and has received less than they are entitled to (including advance payments), Input adjustment(s) to reduce the credits to reflect the exact amount of EIP the taxpayer received, including offsets. Use BS 05, SC 0, the appropriate CRN(s) and amount(s), RC(s), and HC 4. Post delay the adjustment, if necessary. Reminder: TY 2020 - EIP 1 and EIP 2 must be adjusted separately if both are present. When correcting the account to the valid return figures, adjust the RRC, as appropriate, to ensure the module reflects the total amount the taxpayer is entitled to. Post delay the adjustment, if necessary. Note: If RC 139 is not included with this adjustment, a separate TC 290 must be input to ensure the account reflects RC 139. Example: TP Jane Smith files Form 14039 reporting they are a victim of IDT because someone filed a return under their SSN. Jane files the TY 2020 return as the primary taxpayer with their spouse Dave Smith. They file MFJ with an AGI of $152,950 and do not have any dependents. This is the first year they are filing MFJ. After researching the account, you determine Jane Smith is a victim of refund related IDT for TY 2019 and 2020 (Invalid/Valid). Dave Smith does not have an identity theft issue. Jane Smith's TY 2020 module reflects the following: EIP 1 (based on the TY 2019 TC 150 return) in the amount of $1,200. $250 offset to a child support obligation and the remainder issued via direct deposit. EIP 2 (based on the TY 2019 TC 150 return) in the amount of $600 issued via direct deposit. RRC (based on the TY 2020 TC 150 return) in the amount of $600 issued via direct deposit. Dave Smith's TY 2020 module reflects the following: EIP 1 (based on the TY 2019 TC 150 return) in the amount of $1,200 issued via direct deposit. EIP 2 (based on the TY 2019 TC 150 return) in the amount of $600 issued via direct deposit. No RRC. Calculating the amount of tax year 2020 RRC for the valid taxpayer and spouse: $152,950 (AGI) − $150,000 (Limitation) = $2,950 $2,950 × 5% = $147.50 (Amount of reduction) EIP 1 allowable amount: $2,400 − $147.50 = $2,252.50 EIP 2 allowable amount: $1,200 − $147.50 = $1,052.50 Total allowable amount: $2,252.50 + $1,052.50 = $3,305 The valid TY 2020 return includes RRC in the amount of $1,255 The Primary account adjustments will include: • CRN 256 for $655.00 (RRC) • CRN 338 for $600.00- (EIP 2) • CRN 338 for $950.00- (EIP 1) The direct deposit of EIP 1 in the amount of $950 will be treated as a partially lost refund, and the direct deposit of EIP 2 in the amount of $600 will be treated as a lost refund. The result of the adjustment is: EIP 1 = $250 EIP 2 = zero. RRC = $1,255 Because the taxpayers are entitled to $3,305 and received a combined total of $2,050 (EIP 1 + EIP 2), they are entitled to RRC in the amount of $1,255. When it is determined the valid taxpayer has received more RRC than they are entitled to, including advance payments, the account must be adjusted to reflect the correct amount. If the amount of RRC posted to the module is based on an invalid return and is not included in the amount the taxpayer received erroneously, reduce the RRC to zero. See below for the order credits will be reduced in: RRC (Using CRN 256) EIP 2 (Using CRN 338) EIP 2 (Using CRN 257) EIP 1 (Using CRN 338) EIP 1 (Using CRN 257) Caution: Do not reduce EIP below the amount of the related refund received by the valid taxpayer. Taxpayers are not required to repay any portion of EIP received in excess of the amount they are entitled to. Reminder: Lost refunds will be addressed following normal procedures for the case type. Example: The valid taxpayer files Form 14039 claiming they have not received their stimulus payments because someone has filed returns. They filed a TY 2020 return as HOH with wages of $125,452. They have 1 qualifying dependent. The TY 2020 TC 150 return is invalid. After researching the account, you determine the taxpayer is a victim of refund related IDT for TY 2019 and 2020 (Invalid/Valid). The TY 2020 module reflects the following: EIP 1 (based on the TY 2019 TC 150 return) in the amount of $1,700 was offset to a child support obligation. EIP 2 (based on the TY 2019 TC 150 return) in the amount of $1,200 was issued via direct deposit. Tax year 2020 RRC (based on the TY 2020 TC 150 return) in the amount of $600 was issued via direct deposit. Calculating the amount of tax year 2020 RRC the valid taxpayer is entitled to: $125,452 (AGI) − $112,500 (Limitation) = $12,952 $12,952 × 5% = $647.60 (Amount of reduction) EIP 1 allowable amount: $1,700 − $647.60 = $1,052.40 EIP 2 allowable amount: $1,200 − $647.60 = $552.40 Total allowable amount: $1,052.40 + $552.40 = $1,604.80 Account adjustments will include: • CRN 256 for $600.00- • CRN 338 for $600.00- • CRN 257 for $600.00- The result of the adjustment is: EIP 1 posted with CRN 338 for $1,200 and CRN 257 for $500 will remain. EIP 2 and tax year 2020 RRC will both be zero. Because the taxpayer received $1,700 of EIP 1, they received an excess of $95.20 they will not be required to repay. When the TC 150 return is valid and a math error was set for claiming the RRC in an amount that is more than they are entitled to based on the amount of EIP reflected on the module, recalculate the RRC based on the valid taxpayer's information. Follow procedures in IRM 21.5.4.4.4, Math Error Substantiated Protest Processing, to correct the account. Caution: When the account includes other (non-RRC) math errors, only correct those that can be substantiated. If the information (i.e., form, schedule, TIN, etc.) required to correct an additional math error was not provided, issue a closing Letter 4674C. Include an explanation of the adjustment(s) input. Do not suspend the case to request the missing information needed to correct the additional math error(s). Reminder: Lost refunds will be addressed following normal procedures for the case type. When the TC 150 return is valid, the taxpayer qualifies for more RRC than they received (including advance payments), and the taxpayer did not claim any amount of the RRC (blank or zero) or claimed less than they are entitled to, recalculate the RRC based on the valid taxpayer's information. Adjust the account to add/increase the credit, as allowable. Do not set a math error. Issue a closing Letter 4674C to explain the changes made to their tax return figures. You may use the suggested paragraph below or similar verbiage when explaining the changes made: "We changed the amount you claimed as Recovery Rebate Credit (RRC) because we determined you are eligible for more of the credit than you reported. You included $XX.XX of RRC on your return. We recalculated the credit and allowed $XX.XX of RRC. The result of this action is (use appropriate fill in here)." Use numerical figures in place of the X's in the dollar amounts provided. Select an appropriate fill in from the list below: • an increased refund • a decreased balance due When the valid taxpayer filed a return and claimed more RRC than they are entitled to, recalculate the RRC based on the valid taxpayer's information. Correct the account, as allowable. When the valid taxpayer's return posted as a TC 976, follow procedures in IRM 21.5.4.4.1, Setting the Initial Math Error Action, to set the math error and issue a closing Letter 474C to provide an explanation of the correction made. When the valid taxpayer's return posted as the TC 150, the account should already reflect the math error. Send a closing Letter 4674C to provide an explanation of the correction made. Refer to the table below for additional account considerations: Condition Additional Considerations (1) Valid Bal Due for another year: RRC cannot be applied toward that balance. (2) Credit Elect: RRC can be applied as a credit elect. Issue a closing Letter 4674C to provide an explanation when the amount of credit elect is not the amount the taxpayer(s) expected. (3) Issuing a manual refund: Credit interest is allowed for RRC. (4) Lost refund includes RRC: Address the lost refund as instructed in the applicable streamline, non-streamline, or IJE procedures. (5) RRC was offset: EIP 1 is restricted to offset to child support obligations, only, and is not subject to repayment when the taxpayer received more than they were entitled to. EIP 2 is not subject to offset or repayment when the taxpayer received more than they were entitled to. EIP 3 is not subject to offset or repayment when the taxpayer received more than they were entitled to. RRC is not subject to offset for a federal tax debt and must be returned to the originating module when offset in error. RRC is subject to offset for a TOP debt.

# American Rescue Plan Act (ARPA) - General

25.23.4.21 (04-16-2021) American Rescue Plan Act (ARPA) - General The American Rescue Plan Act (ARPA) of 2021 was enacted on March 11, 2021. It includes various tax provisions to benefit qualifying taxpayers by reducing tax and increasing certain credits. Refer to the subsections listed below for additional information: IRM 25.23.4.21.1, ARPA - Unemployment Compensation Tax Relief IRM 25.23.4.21.2, ARPA - Advanced Child Tax Credit (AdvCTC) - General IRM 25.23.4.21.3, ARPA – Excess Advance Premium Tax Credit (APTC) Repayment Relief

# ARPA - Unemployment Compensation Tax Relief

25.23.4.21.1 (10-01-2022) ARPA - Unemployment Compensation Tax Relief Provision 9402 of the American Rescue Plan Act (ARPA) authorizes qualified individuals who received unemployment compensation during calendar year 2020 to exclude up to $10,200 ($20,400 if filing MFJ) from their Adjusted Gross Income (AGI). To qualify for the exclusion of unemployment income, the taxpayer(s) must: Have a valid SSN or ITIN Have received unemployment compensation during calendar year 2020 Meet the threshold of $150,000, regardless of filing status The Modified Adjusted Gross Income (MAGI) is calculated to determine if the $150,000 threshold is met by subtracting the total amount of all unemployment compensation from the Adjusted Gross Income (AGI). An Unemployment Compensation Exclusion Worksheet can be found in the tax year 2020 Form 1040 instructions. If the result is less than $150,000, the threshold is met. The taxpayer(s) may exclude up to $10,200 ($20,400 if MFJ) from their unemployment income when filing Note: Application of the exclusion for MFJ taxpayers will include consideration of community property rules. If the result is $150,000 or more, the threshold is not met. The taxpayer(s) do not qualify to exclude any portion of their unemployment income. Note: Taxpayers who file Form 1040-NR with their spouse claimed as a dependent cannot exclude any portion of unemployment compensation paid to their spouse. They are limited to excluding up to $10,200 of their unemployment compensation, because their filing status is not MFJ. Example: Tim and Tammy Thompson have the following income: • Wages of $130,000 • Gambling winnings of $15,000 • Unemployment compensation of $35,000 ($20,000 for primary and $15,000 for secondary) $130,000 + $15,000 + $35,000 = $180,000 (AGI) $180,000 − $35,000 = $145,000 (MAGI) Tim and Tammy Thompson qualify to exclude up to $20,400 of their unemployment income. They will report the following: • Wages of $130,000 • Gambling winnings of $15,000 • Unemployment compensation of $14,600 • AGI of $159,600 Example: Julie Henson has the following income: • Wages of $52,000 • Unemployment compensation of $12,000 $52,000 + $12,000 = $64,000 (AGI) $64,000 − $12,000 = $52,000 (MAGI) Julie Henson qualifies to exclude up to $10,200 of unemployment income. Julie will report the following: • Wages of $52,000 • Unemployment compensation of $1,800 • AGI of $53,800 A systemic relief process will be used to correct certain accounts for taxpayers who filed their tax year 2020 return prior to the enactment of ARPA. Open identity theft cases will be excluded from this process. Accounts excluded can be identified by a TC 971 AC 123 with MISC "IDTVACASE" (IDTVA case is open) systemically posted to IDRS CC IMFOLE. Upon resolution of an IDT case that was excluded, a TC 971 AC 123 with MISC "IDTVACLSD" (IDTVA case has been resolved) will be systemically posted to IDRS CC IMFOLE. Note: Reversal of the TC 971 AC 123 with MISC "IDTVACASE" will not result in the case being included in a systemic recovery at a later date. All IDT cases bypassed must be adjusted as part of the resolution of the case. For taxpayers who filed their tax year 2020 return prior to the enactment of ARPA, the IRS will determine if the taxpayer(s) qualified to exclude any portion of their unemployment income. Taxpayers are not required to file an amended return to receive this relief. The systemic process will be used to correct accounts that qualify. The following will be corrected and adjusted, as applicable: Caution: Some taxpayers who filed their 2020 return prior to the enactment of ARPA excluded all or some of the unemployment income reported. Generally, a taxpayer reporting unemployment income in this manner has identified a fraudulent unemployment claim in their name. Refer to paragraph (7) below for additional information. Taxable amount of unemployment compensation Adjusted Gross Income (AGI) (TC 888) Taxable Income (TXI) (TC 886) Total tax (TC 290/291) Non-refundable credits Refundable credits Note: If the application of the unemployment income exclusion results in the taxpayer qualifying for a credit not claimed on their original tax return, that credit will not be added. The taxpayer will need to file a Form 1040-X, Amended U.S. Individual Income Tax Return, to claim any additional credits. Exception: When the application of the unemployment income exclusion results in the taxpayer qualifying for self-EIC, the credit will be calculated and included in the corrective adjustment. Taxpayers will not be required to file an amended return to receive self-EIC. Accounts are identified by a TC 971 AC 123 with MISC "UCERECOVERY03112021" after being adjusted through the systemic recovery process. This indicator will be reversed with a TC 972 AC 123 when the systemic recovery process has been completed. Taxpayers will be notified of any changes made when the account has been corrected. Any resulting overpayment of tax will be offset when a tax debt or TOP debt exists. If no debt exists, the overpayment will be refunded by direct deposit or paper check. Taxpayers who file a return addressing fraudulent unemployment compensation reported under their TIN may include the full amount of unemployment income then reduce that amount by the amount they did not receive using Schedule 1, notating fraud, ID Theft, or similar verbiage. The systemic relief process is unable to determine the reason unemployment compensation is being reduced which may result in incorrect adjustments when systemically allowing the unemployment compensation exclusion. When the amount of unemployment income excluded on the original return is less than the amount allowable, the systemic process will input an adjustment based on unemployment income being reduced by the difference. As a result, identity theft claims filed to report unemployment fraud will need to be thoroughly researched. Use MeF to review the original return filed. Compare the amount of unemployment income claimed with the amount excluded on Schedule 1. Review the taxpayer's reason for excluding any amount of unemployment income. When the taxpayer excluded the income because of fraud or ID theft, the unemployment compensation exclusion must be applied only to the portion of unemployment income the valid taxpayer received. This requires math verification, recomputation of tax return figures, and consideration of the systemic adjustment when posted to the module. Example: Betty Fisher filed their tax year 2020 return as single. Betty reported $30,000 of unemployment income and excluded $10,000 notating someone else filed a fraudulent unemployment claim in their name. During the systemic relief process, an adjustment is input to further reduce the unemployment income by $200 for a total of $10,200. As a result, Betty has only benefitted from the exclusion of $200 of the unemployment income received. The amount of unemployment income used for the systemic computation of the exclusion is $19,800 ($30,000 − $10,200). The correct amount of unemployment income for Betty after application of the exclusion is $9,800 ($20,000 − $10,200). To correct the account, the unemployment income must be reduced by an additional $10,000. This will require recomputation of AGI, TXI, tax, and any applicable credits. After verification of the correct return figures, an adjustment must be input to fully resolve the case. Prior to inputting an adjustment, the valid taxpayer's tax year 2020 return must be math verified to ensure the unemployment income exclusion has been applied appropriately. Verify income, tax, and credits were computed correctly. Note: The following deductions will be computed using the full amount of the taxpayer's unemployment benefits prior to reduction by any exclusion amount: • Taxable Social Security Benefits • IRA Deduction • Student Loan Interest Deduction • Nontaxable Amount of Olympic or Paralympic Medals and USOC Prize Money • The exclusion of Interest from Series EE and I U.S. Savings Bonds issued after 1989 (Form 8815) • The exclusion of Employer-Provided Adoption Benefits (Form 8839) • Tuition and Fees Deduction (Form 8917) • The deduction of up to $25,000 for active participation in a Passive Rental Real Estate Activity (Form 8582) When it is determined the eligibility criteria has been met, the unemployment compensation will be reduced by the allowable amount for the filing status but not below zero. If the taxpayer has not applied this relief, the taxpayer's return figures must be recalculated. Recalculation will include total tax and may include non-refundable and/or refundable credits included on the return. Reminder: Self-EIC will be added for taxpayers who qualify for this credit after the application of the unemployment income exclusion. The taxpayer's dependents will not be considered when determining if a taxpayer qualifies for self-EIC and the amount of the credit they are entitled to. The taxpayer will need to file a Form 1040-X, Amended U.S. Individual Income Tax Return, to claim any other credits not included on the original return (i.e., original return does not include ACTC, but the taxpayer now qualifies for ACTC after application of the unemployment income exclusion or now qualifies for EIC with dependents). Example: Jane Hernandez files their tax year 2020 return which posts as the TC 976. You have made a determination of Invalid/Valid. Jane filed the return as single before ARPA was passed. Jane's return includes the following: • Wages - $34,000 • Unemployment Income - $8,400 • AGI - $42,400 • TXI - $30,000 • Total Tax - $3,406 • Withholding - $2,720 • Balance Due - $686 Recalculating the figures with unemployment income exclusion: • Wages - $34,000 • Unemployment Income - $0 • AGI - $34,000 • TXI - $21,600 • Total Tax - $2,398 • Withholding - $2,720 • Refund - $322 Example: Anna Welsh files their tax year 2020 return which posts as the TC 976. You have made a determination of Invalid/Valid. Anna filed the return as HOH before ARPA was passed. Anna's return includes the following: • Wages - $18,000 • Unemployment Income - $7,500 • AGI - $25,500 • TXI - $6,850 • Total Tax - $0 • Withholding - $1,200 • ACTC - $1,312 • EIC - $2,594 • Refund - $5,106 Recalculating the figures with unemployment income exclusion: • Wages - $18,000 • Unemployment Income - $0 • AGI - $18,000 • TXI - $0 • Total Tax - $0 • Withholding - $1,200 • ACTC - $1,400 • EIC - $3,584 • Refund - $6,184 When it is determined the taxpayer applied the unemployment income exclusion in an amount that is more than allowable, recalculate the tax year 2020 figures based on the valid taxpayer's information. Correct the account, as allowable. When the valid taxpayer's return posted as a TC 976, follow procedures in IRM 21.5.4.4.1, Setting the Initial Math Error Action, to set the math error and issue a closing Letter 474C to provide an explanation of the correction(s) made. Reminder: Recalculation of the figures may impact AGI, TXI, total tax, non-refundable credits, and refundable credits (including RRC). When an adjustment input includes figures using the unemployment income exclusion, Reason Code (RC) 020 must be used to indicate the exclusion has been applied. Use RC 020 when inputting adjustments for the following scenarios: Invalid/Valid Determinations Valid/Invalid Determinations ASFR/Exam SFR assessment with a valid return received (IDTVA Specialties only) RC 020 will not be included when inputting adjustments for the following scenarios: No IDT Determinations No Reply Cases Income Related IDT Determinations (no invalid return) For any scenarios not included in paragraphs (10) - (12) above, prepare and email a Form 4442 using the subject line: "UI Relief" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days.

# ARPA - Advanced Child Tax Credit (AdvCTC) - General

25.23.4.21.2 (10-01-2022) ARPA - Advanced Child Tax Credit (AdvCTC) - General Section 9611 of the American Rescue Plan Act (ARPA) increases the Child Tax Credit (CTC) for tax year 2021 and authorizes qualified individuals to receive periodic advance payments (in equal amounts) of up to 50% of the refundable portion of the Additional Child Tax Credit (ACTC). In addition, the CTC includes the following special rules for tax year 2021 only: The term "qualifying child" was broadened to include children under the age of 18 at the end of calendar year 2021. CTC was increased to $3,000 for each qualifying child aged 6-17 and $3,600 for each qualifying child under the age of 6. CTC was made fully refundable for taxpayers who resided in the United States for more than one half of the year (either spouse if MFJ) and taxpayers who are bona fide residents of Puerto Rico. Note: Children with a date of death prior to the calendar year of the tax return used to determine eligibility for the credit will not be taken into account when computing the AdvCTC payment amount. Note: Residents of Puerto Rico qualify for CTC but are not entitled to the advanced payments. They will receive any refundable amount when filing their tax year 2021 return. The increased amount of the credit ($1,000 for qualifying children aged 6-17; $1,600 for qualifying children under the age of 6) is subject to limitation when the modified adjusted gross income (MAGI) exceeds the applicable threshold amount for the filing status: $150,000 for married filing joint and surviving spouse $112,500 for head of household $75,000 for all other filing statuses When the credit limitation applies, the credit will be reduced by $50 for each $1,000 (or portion of $1,000) in excess of the threshold amount for the filing status. The amount of the reduction must not exceed the lesser of the increased amount of the credit ($1,000 for qualifying children aged 6-17; $1,600 for qualifying children under the age of 6) or 5% of the applicable phaseout threshold range (difference between AGI and threshold). Caution: This limitation only applies to the additional amount of credit allowed by ARPA. Application of these special rules must not reduce the credit below the amount the taxpayer is entitled to under the Tax Cuts and Jobs Act (TCJA). Example: The taxpayer filed HOH with an AGI of $120,000 and 1 qualifying dependent (age 10). $120,000 − $112,500 = $7,500 $7,500 ÷ $1,000 = 7.5 (round up to 8 for computation of the reduction amount) $50 × 8 = $400 $7,500 × 5% = $375 $1,000 − $375 = $625 (amount of additional credit after limitation) $2,000 (child tax credit amount) + $625 (additional credit for 2021) = $2,625 (total credit) Initially, the IRS will identify eligible taxpayers and calculate the Advanced Child Tax Credit (AdvCTC) using tax year 2020 return information (2019 if 2020 is not available). Each condition listed below must be met to potentially receive AdvCTC: The tax return must be an eligible return type to claim CTC (Forms 1040, 1040SR, 1040NR). The tax return must include an address that is U.S. domestic (non-territory), unless the account was subsequently updated to include a U.S. domestic address. APO, FPO, and DPO (military addresses) will be treated as U.S. domestic addresses. The tax year 2020 return (2019 if 2020 is not available) must contain CTC qualifying children. Exception: A TC 971 AC 199 with MISC "NF1040 WCTC xx" is placed on the entity of taxpayers who do not have a tax year 2020 return and filed a tax year 2019 return using the non-filer tool that did not capture the number of qualifying children on the return (EIP QC recovery). These taxpayers are eligible when all other conditions are met. The Primary Taxpayer (and Secondary Taxpayer, if MFJ) must have a valid SSN/Name Control combination or a valid, active, ITIN/Name Control combination. The Primary Taxpayer (and Secondary Taxpayer, if MFJ) must not have a date of death. (This is verified monthly for taxpayers receiving AdvCTC.) Taxpayers included on another return that is eligible to receive AdvCTC will have eligibility determined based on the tax year 2020 return only. Certain taxpayers will also be able to provide updated information using the Child Tax Credit Update Portal (CTCUP) on IRS.gov. Taxpayers who are unable to pass the online authentication will be able to call the IRS to make the changes. The following is a list of actions taxpayers may take related AdvCTC payments: Note: The IRS is using a phased approach in developing the CTCUP to provide these self-help methods to taxpayers. Each phase will expand the taxpayers' ability to revise relevant information. Enroll to receive payments or unenroll to stop receiving payments Update the number of qualifying children (including birth of a child) Change the marital status Report a change in income Update direct deposit information (online portal only) Update mailing address In addition to the online portal, taxpayers who do not have a filing requirement under normal circumstances may use a non-filer tool to submit a tax year 2020 return to report qualifying dependents for purposes of receiving AdvCTC payments. The amount of AdvCTC payments will be made using the most current information available, including tax year 2020 returns filed and updated information provided by the taxpayer. In the event the taxpayer has received an AdvCTC payment, the new payment amount will be computed with consideration of the total amount of advanced payment(s) the taxpayer has received. Taxpayers will receive the AdvCTC payments via direct deposit when valid direct deposit information is available. Payments will be issued as a paper check when there is no valid direct deposit information. Note: A payment will not be issued when the amount of the credit is less than $1. Note: When the CTCUP has been used to update direct deposit information, the taxpayer's entity will be marked with a TC 971 AC 199 with the MISC field providing the bank/routing information followed by "EF" (20 positions). The Julian Date will be 999, and the Blocking Series will be 77777. AdvCTC computation and payments will be postponed if the tax year 2020 module (2019 if 2020 is not available) contains at least one of the following conditions: A refund freeze due to Exam (-L Freeze) and an unreversed TC 424. (TC 420 for open and TC 421 for closed may also be present.) A TC 971 AC 199 MISC AMWEX60033 unless a subsequent refund (TC 846) posted or a TC 972 AC 199 MISC AMWEX60033 is present. A TC 570 with DLN NN27788888888Y and a -R Freeze. A duplicate return freeze (-A Freeze). An unreversed TC 971 AC 129 (ID Theft TPP) unless a subsequent refund (TC 846) posted. A tax return and returned tax refund (TC 841 with blocking series 77711, 77712, 77713, or 77714 unless a subsequent refund (TC 846) posted. A TC 740 with 99999 or 66666 (undeliverable address on paper check) unless a subsequent refund (TC 846) posted. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ An unreversed TC 971 AC 151 (duplicate TIN) followed by an adjustment backing out the return. A reversed refundable child tax credit transaction (CRN 336). A refund freeze due to AQC (-R Freeze) with an unreversed TC 971 AC 122/140 unless a subsequent refund (TC 846) posted. A posted TC 29X that completely reverses the posted TC 150 (full return reversal) and there is no subsequent TC 29X (excluding TC 290 .00 with no associated CRNs). An unreversed TC 971 AC 134 with MISC field "BKLD COMINGLED" unless a subsequent refund (TC 846) posted. A refund repayment (TC 720) unless a subsequent refund (TC 846) posted. AdvCTC computation and payments will be postponed if the taxpayer's entity contains at least one of the following conditions: A TC 971 AC 123 with MISC "IDTVACASE" that has not been reversed with a TC 971 AC 123 with MISC "IDTVACLSD" (ID Theft). ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ An account merge is in process. The address is a territory address: Commonwealth of the Northern Mariana Islands (state code MP), Guam (state code GU), United States Virgin Islands (state code VI), Puerto Rico (state code PR), American Samoa (state code AS), Micronesia (state code FM), Marshall Islands (state code MH), or Palau (state code PW). The 2-year or 10-year ban recertification indicator is present, and the eligible tax period is not zero. The account reflects a Service Center address unless there is a TC 971 AC 199 EF other than Blocking Series 99999. Other account conditions that will postpone AdvCTC computation and payments include: The primary taxpayer is incarcerated (filing status not MFJ). The primary and secondary taxpayers are both incarcerated (filing status is MFJ). The tax year 2021 module contains any EIP3 or AdvCTC TC 740 with Blocking Series 99999 or 66666 (undeliverable address on paper check) unless a subsequent address change has posted or the CTCUP has been used to provide direct deposit information. Note: For MFJ taxpayers, only one taxpayer needs to provide the subsequent update for this condition to be satisfied. Account conditions that will require separate treatment of MFJ taxpayers for purposes of computation and payment include (Split Payment): An innocent spouse issue has been identified (TC 971 AC 065/104). There is a Victim of Domestic Violence (VODV) indicator (TC 971 AC 198). When the primary or secondary taxpayer updates any feature within the CTCUP or through a CSR and the other spouse does not update their account with the exact same transaction (i.e., same bank account or address) within the same day. AdvCTC payments will be issued on a monthly basis beginning in July 2021 and will continue through December 2021. When an account condition that postpones computation and payments has been identified, the postponement will continue until the condition has been resolved. AdvCTC payments will not include credit interest (for original payments or reissued payments), are not subject to federal tax offsets or TOP offsets for non-tax debts, and will not be applied as a credit elect. The IRS will issue a notice no later than January 31, 2022 to provide taxpayers with the total amount of AdvCTC payments issued to them. Taxpayers will reconcile the amount of CTC and/or ACTC they are entitled to by reducing it by the total amount of AdvCTC payments issued to them (but not below zero). When the total amount of AdvCTC payments exceeds the amount of the credit the taxpayer is entitled to, the tax reported on the tax year 2021 return will be increased by the amount received in excess. Failure to correctly reconcile the amount of CTC and/or ACTC will be treated as a math error when processing the return. Taxpayer Notice Code (TPNC) 276 will be used to identify AdvCTC math errors. Refer to IRM 25.23.4.21.2.3, ARPA - Advanced Child Tax Credit (AdvCTC) Math Errors, for additional information. The amount of the tax increase may be limited by a repayment protection specific to receipt of AdvCTC in an amount that exceeds the credit the taxpayer is entitled to. The tax increase for taxpayers whose MAGI does not exceed the income threshold will be reduced by the full amount of the repayment protection (but not below zero). Refer to paragraphs (19) and (20) for additional information. The tax increase for taxpayers whose MAGI exceeds the income threshold will be subject to phase out by a reduction percentage. Refer to paragraphs (19) and (21) for additional information. The applicable income threshold amount for consideration of the repayment protection is based on the filing status: $60,000 for married filing joint and surviving spouse $50,000 for head of household $40,000 for all other filing statuses The repayment protection amount is determined by identifying the difference between the number of qualifying children the AdvCTC payments were based on and the number of qualifying children on the tax year 2021 return. That number is then multiplied by $2,000. Example: AdvCTC payments were based on a tax year 2020 return filed MFJ. The return includes 3 qualifying children under the age of 6. The taxpayers received a total of $5,400 in AdvCTC payments. The tax year 2021 return was filed MFJ, has a MAGI of $55,000, and 1 qualifying child (age 6). The repayment protection is not subject to phase out, because their MAGI is below the applicable income threshold. 3 (children on TY 2020 return) − 1 (child on TY 2021 return) = 2 2 × $2,000 = $4,000 (repayment protection amount) $5,400 (AdvCTC payments) − $3,000 (TY 2021 credit) = $2,400 (excess AdvCTC payments received) The taxpayer will not increase their tax, because the repayment protection amount is more than the amount of excess AdvCTC payments received. The repayment protection amount is fully phased out when the taxpayer's MAGI is 200% or more of the applicable income threshold. $120,000 for married filing joint and surviving spouse $100,000 for head of household $80,000 for all other filing statuses When the repayment protection amount is subject to phase out, calculate the correct repayment protection amount following the steps below: Subtract the applicable income threshold amount in paragraph (19) from the MAGI. Divide the difference from step a) by the applicable income threshold amount in paragraph (19) to calculate the reduction percentage. Determine the total potential repayment protection amount as described in paragraph (20) above. Multiply the total potential repayment protection amount from step c) by the reduction percentage from step b) to determine the phase out amount. Subtract the phase out amount calculated in step d) from the potential repayment protection amount calculated in step c) to determine the reduced repayment protection amount. Example: AdvCTC payments were based on a tax year 2020 return filed MFJ. The return includes 2 qualifying children, both under the age of 6. The taxpayers received a total of $3,600 in AdvCTC payments. The tax year 2021 return is filed MFJ, has a MAGI of $118,500, and 1 qualifying child over the age of 6. Determine if the MAGI exceeds the income threshold: $60,000 × 200% = $120,000 MAGI = $118,500 The repayment protection phase out applies. a) Calculate the difference between the MAGI and the income threshold: $118,500 − $60,000 = $58,500 b) Calculate the reduction percentage: $58,500 ÷ $60,000 = .975 .975 × 100 = 97.5% c) Determine the potential repayment protection amount: 2 − 1 = 1 1 × $2,000 = $2,000 d) Calculating the phase out amount: $2,000 × 97.5% = $1,950 e) Calculating the reduced safe harbor amount: $2,000 − $1,950 = $50 Application of the repayment protection amount: $3,600 (AdvCTC payments) − $3,000 (TY 2021 credit) = $600 (excess AdvCTC payments received) Result: $600 (excess AdvCTC payments received) − $50 (reduced repayment protection amount) = $550 The total tax will be increased by $550.

# ARPA - Advanced Child Tax Credit (AdvCTC) - Identity Theft Research and Account Actions

25.23.4.21.2.1 (06-06-2022) ARPA - Advanced Child Tax Credit (AdvCTC) - Identity Theft Research and Account Actions Advanced Child Tax Credit (AdvCTC) payments are issued from the tax year 2021 module. Each payment will post with an associated adjustment including the following information: TC 290 .00 Unique Reason Codes (RCs) (defined below) TC 766 with Credit Reference Number (CRN) 272 for the amount of the payment Note: This amount may be zero if the taxpayer is ineligible or the credit was completely phased out by the MAGI. Hold Code (HC) 3 Each adjustment will include a unique DLN to identify the month of the payment. Refer to the list below for the DLN sequence numbers: 31 - July 32 - August 33 - September 34 - October 35 - November 36 - December Refer to the table below for adjustment information specific to MFJ taxpayers who are eligible to receive the credit: Scenario Module 1 Module 2 (1) Neither taxpayer is deceased, Not innocent spouse, Not a victim of domestic violence (VODV), and Neither unenrolled Note: This scenario will also apply if one of the taxpayers is incarcerated. Primary Taxpayer The AdvCTC adjustment will post as described in paragraph (1) above. Secondary Taxpayer The AdvCTC adjustment will post with CRN 272 .00. (2) One taxpayer is deceased Surviving Spouse The AdvCTC adjustment will post as described in paragraph (1) above. RC 207 will be in the fourth position. Deceased Spouse The AdvCTC adjustment will post with CRN 272 .00. RC 207 will be in the third position. (3) Innocent spouse, or VODV indication Primary Taxpayer The AdvCTC adjustment will post as described in paragraph (1) above. Note: The credit amount will be half of the total computed amount. (50/50 split) Secondary Taxpayer The AdvCTC adjustment will post as described in paragraph (1) above. Note: The credit amount will be half of the total computed amount. (50/50 split) (4) One spouse unenrolls, The other spouse is not deceased, and The computed amount for the monthly payment is greater than zero Enrolled Spouse The AdvCTC adjustment will post as described in paragraph (1) above. Note: The credit amount will be half of the total computed amount. (50/50 split) Unenrolled Spouse An adjustment will not post to the module. (5) One spouse unenrolls, and The other spouse is deceased Deceased Spouse The AdvCTC adjustment will post with CRN 272 .00. Unenrolled Spouse An adjustment will not post to the module. When a taxpayer is ineligible for the credit (including MFJ returns), a TC 290 .00 will post to the module with CRN 272 .00. When the taxpayer is ineligible for multiple months, an additional TC 290 .00 with CRN 272 .00 will only post when the reason code in position 3 is different. Refer to the table below for adjustment Reason Codes (RCs) specific to AdvCTC adjustments: RC Position Description 1 If the taxpayer qualifies for AdvCTC, this field will contain the total number of CTC eligible children, regardless of age. If the taxpayer does not qualify for AdvCTC, this field will contain RC 000. 2 This field will contain a description of the month for the AdvCTC amount: 007 - July 008 - August 009 - September 010 - October 011 - November 012 - December 3 Systemic Adjustments: This field will contain a description of the larger computed AdvCTC amount. No Credit RCs: 200 - No AdvCTC due to MAGI phase out 202 - Invalid Primary or Secondary SSN (Includes invalid due to assignment date, SSN not valid for work) 205 - Catch all (For example, all CTC children deceased, AdvCTC under $1, etc.) Reduced Credit RC: 206 - AdvCTC reduced due to MAGI phase out Maximum Amount RC: 209 - AdvCTC not reduced by MAGI Manual Adjustments: This field will contain a description of the AdvCTC adjustment. 214 - AdvCTC split equally 50/50 between the primary and secondary taxpayers 215 - AdvCTC attributable to only the primary taxpayer 216 - AdvCTC attributable to only the secondary taxpayer 4 Systemic Adjustments: This field will include RC 207 when: A non-joint taxpayer is deceased A MFJ return and one or both taxpayers are deceased Manual Adjustments: This RC position will not be used for manual AdvCTC adjustments. An AdvCTC TC 971 AC XXX (other than 199) is placed on the entity (CC IMFOLE) of taxpayers to indicate specific account conditions. Refer to the table below for a list of the action codes and their descriptions: Action Code Description 065 Innocent Spouse (Form 8857) 198 Victim of Domestic Violence (VODV) 856 Unenrolled taxpayer (will include MISC "OPT-OUT" ) TC 971 AC 199 (systemic) is placed on the entity (CC IMFOLE) of taxpayers to document the amount of each AdvCTC payment issued (including zero amounts), the month of payment, number of dependents, and AdvCTC source (tax year of return). Refer to the table below for specific account scenarios: Note: See IRM 21.6.3-3, TC 971 AC 199 MISC Field Descriptions for Advance Child Tax Credit (Adv CTC) Payments, for a list of MISC fields and their descriptions. Scenario Posts With (1) Eligible taxpayers with a filing status other than MFJ The TC 971 AC 199 will post with the total monthly AdvCTC amount. (2) MFJ return: Neither taxpayer is deceased, Not innocent spouse, Not VODV, Not unenrolled, and Not incarcerated The TC 971 AC 199 AdvCTC amount is split in half (50/50) between the primary and secondary taxpayers. (3) MFJ return: Neither taxpayer is deceased, and Is innocent spouse or VODV The TC 971 AC 199 AdvCTC amount will match the amount of the credit in the adjustment posted to the tax module. (The credit was already split 50/50 between the Primary and Secondary taxpayers for the TC 290 adjustment.) (4) MFJ return: One spouse has unenrolled The TC 971 AC 199 will post for the taxpayer who is enrolled with an AdvCTC amount that matches the credit in the adjustment posted to the tax module. (The credit was already split 50/50 between the Primary and Secondary taxpayers for the TC 290 adjustment.) (5) MFJ return: One spouse is deceased The TC 971 AC 199 will post for the surviving spouse with the total monthly AdvCTC amount. The TC 971 AC 199 will post for the deceased taxpayer with an AdvCTC amount of zero. (6) Ineligible taxpayers The TC 971 AC 199 will post with an AdvCTC amount of zero. When systemic or manual adjustments to AdvCTC are input, a TC 971 AC 199 (systemic) or TC 971 AC 195 (manual) will reflect details of the credit on the taxpayer's entity. Refer to the table below for MISC Field format and descriptions: TC 971 AC 199/195 MISC Field Field Description (1) TC 971 AC 199 (systemic) only: NNNNNNN kktyCTCYYmm AdvCTC was computed and issued NNNNNNN - dollar amount, including cents kk - number of qualifying children ty - tax year of payment (00 or 21 = 2021) CTC - computed for AdvCTC YY - tax year used for computation (19 = 2019, 20 = 2020) mm - indicates month of the payment (07 = July, 08 = August, etc.) (2) TC 971 AC 199 (systemic) only: NNNNNNN kktyREVCTmm AdvCTC was reversed systemically (e.g., returned payment) NNNNNNN - dollar amount, including cents kk - number of qualifying children ty - tax year of payment (00 or 21 = 2021) REVCT- systemic reversal YY - tax year used for computation (19 = 2019, 20 = 2020) mm - indicates month of the payment (07 = July, 08 = August, etc.) (3) TC 971 AC 199 (systemic) or TC 971 AC 195 (manual): NNNNNNN kktyxxCTCADJ Systemically generated when a manual adjustment for AdvCTC is input resulting in a refund (TC 971 AC 199) OR Manually input when AdvCTC is moved from one account to another (TC 971 AC 195) NNNNNNN - dollar amount, including cents kk - number of qualifying children ty - tax year of payment (00 or 21 = 2021) xx - indicates month of the payment (07 = July, 08 = August, etc.) CTCADJ - indicates positive manual account adjustment (4) TC 971 AC 199 (systemic) only: NNNNNNN kktyxxREVCTC Systemically generated when a manual adjustment reversing AdvCTC is input (TC 971 AC 199) NNNNNNN - dollar amount, including cents kk - number of qualifying children ty - tax year of payment (00 or 21 = 2021) xx - indicates month of the payment (07 = July, 08 = August, etc.) REVCTC - indicates negative manual account adjustment When a TC 971 AC 199 with MISC "EF" is posted on the entity (CC IMFOLE): Unreversed TC 971 AC 199 "EF" with Blocking Series other than 99999 is present: The payment will be issued as a direct deposit to the latest EFT account associated with the indicator. TC 971 AC 199 "EF" with Blocking Series other than 99999 is not present: The payment will be issued as a paper check. A posted reversal TC 972 AC 199 "EF" and no subsequent TC 971 AC 199 "EF" with Blocking Series other than 99999 is present: The payment will be issued as a paper check. Innocent Spouse or VODV issue: The payment will be issued as a paper check unless the entity contains a posted TC 971 AC 199 "EF" with Blocking Series 77777. When the entity does not contain a TC 971 AC 199 with MISC "EF" (Blocking Series other than 99999), the payment will be issued as a paper check when one or more of the following conditions exist: The tax year 2021 module contains an unreversed TC 971 AC 850 (refund flipped to paper), unless the last posted unreversed TC 971 AC 199 "EF" has Blocking Series 77777. The tax year 2021 module contains a systemically reversed AdvCTC direct deposit refund issued for a previous month. The tax year 2021 module contains a TC 841 with Blocking Series 77711/77712/77713/77714 unless there is a TC 971 AC 199 "EF" with Blocking Series 77777 posted after the cycle of the TC 846. The tax year 2021 module contains a cycle date for the latest TC 846 that is later than the date of the TC 971 AC 199 "EF" with Blocking Series other than 99999 and there is a subsequent TC 841. When an AdvCTC payment is returned/rejected by the bank, the AdvCTC account transactions (tax module and entity) will be systemically reversed EXCEPT when: The payment is a returned direct deposit (Blocking Series 77777) for a taxpayer who is not deceased (both primary and secondary for MFJ) and/or there has not been a name line change from 2019 to 2020. These will be reissued as a paper check. The payment is a returned direct deposit and there is a later posted TC 971 AC 199 EF with Blocking Series other than 99999. These will be reissued as direct deposit to the new bank account. Note: Effective cycle 202150 and later, all returned/rejected AdvCTC payments will be systemically reversed. When the taxpayer returns an AdvCTC payment, the account will be credited with a TC 670 (DPC 063) on the tax year 2021 module. The earliest unreversed matching amount and transactions (on the tax module and entity) will be systemically reversed. When the returned AdvCTC repayment amount is more than the earliest unreversed matching amount, subsequent amounts and transactions (on the module and entity) will be systemically reversed until the repayment is exhausted. Taxpayers who are victims of identity theft (IDT) may experience delays in receiving AdvCTC payments. When you have determined the taxpayer is a victim of IDT for tax year 2020 or 2019, or the claim is related to non-receipt of AdvCTC payments, a determination of impact to AdvCTC payments must be made. Note: Each AdvCTC payment must be considered separately. Refer to the table below to determine if the payment being considered was issued to the valid taxpayer: If And Then (1) The CTCUP was used to update the direct deposit information, Note: If the taxpayer states they did not update the information using the CTCUP, see scenarios (3) and (4) below. The payment was issued by direct deposit after the update occurred, The valid taxpayer did receive the payment. (2) The CTCUP was used to update the direct deposit information, The payment was issued by direct deposit or paper check before the update occurred, Use scenarios (5) - (8) below to determine who received the payment. (3) The taxpayer states they did not use the CTCUP to update their direct deposit information or the taxpayer indicates an individual assisting them with using the tool input bank account information that does not belong to them, The payment was issued by direct deposit after the update occurred, The valid taxpayer did not receive the payment. (4) The taxpayer states they did not use the CTCUP to update their direct deposit information or the taxpayer indicates an individual assisting them with using the tool input bank account information that does not belong to them, The payment was issued by direct deposit or paper check before the update occurred, Use scenarios (5) - (8) below to determine who received the payment. (5) CTCUP was not used to update direct deposit information and one of the following determinations is made: One return IDT Invalid/Valid Invalid/Invalid IJE The payment was issued by direct deposit, The valid taxpayer did not receive the payment. (6) CTCUP was not used to update direct deposit information and one of the following determinations is made: One return IDT Invalid/Valid Invalid/Invalid IJE The payment was issued by paper check, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. (7) CTCUP was not used to update direct deposit information and one of the following determinations is made: Valid/Invalid One valid return/no invalid return Income-related IDT (no invalid return) The payment was issued by direct deposit, The valid taxpayer did receive the payment. (8) CTCUP was not used to update direct deposit information and one of the following determinations is made: Valid/Invalid One valid return/no invalid return Income-related IDT (no invalid return) The payment was issued by paper check, Review the address, including the cycle date of the last change, to determine who the payment was mailed to. Note: You can determine if the payment was issued via direct deposit or by mail by reviewing the DD indicator posted with the TC 846. The payment was issued as direct deposit if the indicator is "9" and mailed if the indicator is "0" . Reminder: Addresses on taxpayers' accounts may have been updated multiple times. In an effort to ensure determinations of receipt are correct, it is suggested IDRS CC FINDS is used to compare address updates with the cycle date of the TC 846 for the payment in question. This CC provides a long-term history of the taxpayer's address and cycle dates for each change.

# ARPA - Advanced Child Tax Credit (AdvCTC) - Adjustments

25.23.4.21.2.2 (10-01-2023) ARPA - Advanced Child Tax Credit (AdvCTC) - Adjustments AdvCTC will be adjusted on the TY 2021 module using Credit Reference Number (CRN) 272. Refer to IRM 25.23.4.21.2.1, ARPA - Advanced Child Tax Credit (AdvCTC) - Identity Theft Research and Account Actions, to determine the appropriate Reason Codes to be used when adjusting. Reminder: A secondary TC 290 .00 will not be input when a TC 150 return has not been received. Refer to IRM 25.23.4.3.1, CII and IDRS Case Controls, for additional information. Adjustments to AdvCTC will only remove the credits on an account received by the invalid taxpayer. The valid taxpayer will receive the correct amount through systemic recalculation for future payments. When all advance payments for the year have been issued, the taxpayer will be able to claim any amount not received when filing their tax return. Each advance payment must be considered separately to identify if any were issued to the invalid taxpayer. All payments issued to the invalid taxpayer will be addressed separately. Streamline IDT Cases: Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds. Non-Streamline IDT and Invalid Joint Election (IJE) Cases: Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds. CTCUP Updates: Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds. When adjusting the account to remove the credits associated with advance payments issued to an invalid taxpayer, a separate adjustment must be input for each. Attempting to adjust the account by using the total amount lost will result in an unpostable condition. Each must include the following fields required for adjustments to AdvCTC: DATA-REF-1>: 272 REF-CHG-1> the number of dependents used to calculate the amount of the credit (can be found on CC IMFOLE) Credit Reference Number (CRN): 272 Reason Code (RC): 000 (first position), the applicable RC for the month of the lost payment (second position), RC for the appropriate filing status scenario for manual adjustments (third position) When AdvCTC payments were issued as a paper check, review the scenarios below prior to taking further action: Note: Before issuing a closing letter when addressing either of the following scenarios, refer to paragraph (11) below for letter requirements. If CTCUP was updated by someone other than the valid taxpayer after all AdvCTC payments were issued or the taxpayer's payments were stolen from their mailbox, the case will be worked as non-tax-related identity theft. Refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, for specific procedures. If CTCUP was not updated by someone other than the valid taxpayer, payments were not stolen from the taxpayer's mailbox, there is no invalid return for TY 2021, and/or all payments issued were returned, the taxpayer is not a victim of IDT for TY 2021. Follow procedures in IRM 25.23.4.10.8 , No Identity Theft (NOIDT), to resolve the account. When the amount of AdvCTC was calculated using an invalid return and a return (either valid or invalid) has not been received for TY 2021, take the following actions: Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each payment issued to the invalid taxpayer. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). Refer to paragraph (11) below for letter requirements. Refer to the table below for AdvCTC scenarios that do include an invalid return for TY 2021: AdvCTC Payments And Then (1) Were issued only to the valid taxpayer OR Were not allowed or issued to anyone The determination made is valid/invalid Follow procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns. Refer to paragraph (11) below for letter requirements. (2) Were issued only to the valid taxpayer OR Were not allowed or issued to anyone An invalid return posted as the TC 150 Follow the applicable procedures: One Return IDT:IRM 25.23.4.10.1, Identity Theft with Invalid Return Invalid/Valid:IRM 25.23.4.10.1, Identity Theft with Invalid Returns Invalid/Invalid:IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns Refer to paragraph (11) below for letter requirements. (3) Were issued in whole or part to the invalid taxpayer The determination made is valid/invalid and a math error was not set Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each payment issued to the invalid taxpayer. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). For non-streamline cases, input a TC 971 AC 195 on the invalid taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC filed inputs. Follow procedures in IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns, to address the invalid return. Refer to paragraph (11) below for letter requirements. (4) Were issued in whole or part to the invalid taxpayer The determination made is valid/invalid and a math error was set Refer to IRM 25.23.4.21.2.3, ARPA - Advanced Child Tax Credit (AdvCTC) Math Errors, to correct the account. Refer to paragraph (11) below for letter requirements. (5) Were issued in whole or part to the invalid taxpayer An invalid return posted as the TC 150 Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each payment issued to the invalid taxpayer. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). Follow the applicable procedures to address the invalid return and adjust to the valid return (if received): One Return IDT:IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns Invalid/Valid:IRM 25.23.4.10.1, Identity Theft with Invalid Returns Invalid/Invalid:IRM 25.23.4.10.1, Identity Theft (IDT) with Invalid Returns For non-streamline cases, input a TC 971 AC 195 on the invalid taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC filed inputs. Refer to paragraph (11) below for letter requirements. Note: For any cases (with an invalid return) involving AdvCTC payments that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "AdvCTC" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Refer to the table below for scenarios that do not include an invalid return for TY 2021: AdvCTC Payments And Then (1) Were issued only to the valid taxpayer The valid taxpayer has filed a TY 2021 return If CTCUP was updated by someone other than the valid taxpayer after all AdvCTC payments were issued, the case will be worked as non-tax-related identity theft. Refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, for specific procedures. If there is no invalid return and CTCUP was not updated after all AdvCTC payments were issued, the taxpayer is not a victim of IDT. Follow procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT). Refer to paragraph (11) below for letter requirements. (2) Were issued in whole or part to the invalid taxpayer The valid taxpayer has filed a 2021 tax return and a math error was not set Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each payment issued to the invalid taxpayer. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. Post delay this adjustment to ensure it posts after all AdvCTC adjustments. For non-streamline cases, input a TC 971 AC 195 on the invalid taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC filed inputs. Refer to paragraph (11) below for letter requirements. (3) Were issued in whole or part to the invalid taxpayer The valid taxpayer has filed a TY 2021 return and a math error was set Refer to IRM 25.23.4.21.2.3, ARPA - Advanced Child Tax Credit (AdvCTC) Math Errors, to correct the account. Refer to paragraph (11) below for letter requirements. (4) Were issued in whole or part to the invalid taxpayer The valid taxpayer has not filed a TY 2021 return Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each payment issued to the invalid taxpayer. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). For non-streamline cases, input a TC 971 AC 195 on the invalid taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC filed inputs. Refer to paragraph (11) below for letter requirements. Note: For any cases (with no invalid return) involving AdvCTC payments that do not meet the scenarios described above, prepare and email a Form 4442 using the subject line: "AdvCTC" (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days. Refer to the table below for cases determined to be invalid joint election (IJE) or mixed entity (MXEN). If Then (1) Invalid Joint Election (IJE) Address lost payments as described in paragraph (4) above. Reverse AdvCTC for each lost payment. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). Input a TC 971 AC 195 on the other taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC filed inputs. Input TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. Post delay this adjustment to ensure it posts after all AdvCTC adjustments. Refer to IRM 25.23.4.8.1.3.1, Invalid Joint Election Consideration, for additional information. Refer to paragraph (11) below for applicable procedures. (2) Mixed Entity (MXEN) Refer to IRM 21.6.2.4.8, Advance Child Tax Credit (AdvCTC), for applicable procedures. Refer to the table below for additional letter requirements specific to AdvCTC issues: Note: Your closing letter must include the required information for all scenarios applicable to your case. If Then (1) The taxpayer has not filed a TY 2021 return: Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer they will need to file a 2021 tax return to claim any additional amount of ACTC they may be entitled to or reconcile the advance amount they received. (2) The taxpayer has filed a TY 2021 return that resulted in a math error set during original processing: Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer of any corrections made to their account. (3) The taxpayer requested to be unenrolled from AdvCTC payments but you are unable to take the action on their behalf: Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer we could not complete this action, as requested. (4) The taxpayer requested to have their information updated for AdvCTC (i.e., AGI, dependents, etc.): Issue a closing Letter 4674C. Include an open or floating paragraph to advise the taxpayer we could not complete this action, as requested. Reminder: When the taxpayer's EIP 3 was also affected by IDT, specific information may be required to be included in the closing letter. Refer to IRM 25.23.4.20.3, Economic Impact Payments - Adjustments, for additional information.

# ARPA - Advanced Child Tax Credit (AdvCTC) Math Errors

25.23.4.21.2.3 (10-01-2023) ARPA - Advanced Child Tax Credit (AdvCTC) Math Errors Identity theft (IDT) affecting Advanced Child Tax Credit (AdvCTC) payments will result in a math error (to increase tax or decrease credits related to AdvCTC/ACTC) when the tax year 2021 return is not reconciled correctly according to IRS records. Review the information provided by the taxpayer to identify each advance payment that must be addressed. Refer to the scenarios below: If Then (1) The taxpayer specifies what AdvCTC payments they did/did not receive (i.e., I only received payments for July and August.), Continue to paragraph (3) below. (2) The taxpayer provides a general statement (i.e., Someone changed my bank account information.), Research the account to determine impact to payments. If your research results in a clear determination, continue to paragraph (3) below. If your research does not support a clear determination, follow table scenario 3. (3) The taxpayer's statement is insufficient for determining impact to AdvCTC (i.e., Someone is using my SSN.), Follow procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to request the taxpayer specify what AdvCTC payments they did/did not receive. (4) There is no taxpayer statement (i.e., Form 14039 does not include an explanation, or the case is IRS identified.), Research the account to determine impact to payments. If your research results in a clear determination, continue to paragraph (3) below. If your research does not support a clear determination, follow table scenario 3. Prior to inputting adjustments to correct the tax year 2021 module: Determine the total amount of AdvCTC payments received by the valid taxpayer. Math verify the amount of Child Tax Credit (CTC) and/or Additional Child Tax Credit (ACTC) claimed on the valid tax year 2021 return. Refer to IRM 21.6.3.4.1.24, Child Tax Credit (CTC), and IRM 21.6.3.4.2.8, Additional Child Tax Credit (ACTC), for credit qualifications and computation. All payments issued to the invalid taxpayer will be addressed separately. Streamline IDT Cases: Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds. Non-Streamline IDT and Invalid Joint Election (IJE): Follow procedures in IRM 21.5.2.4.23.10, Moving Refunds. CTCUP Updates: Follow procedures in IRM 25.25.4.7, Reversing Identity Theft (IDT) Lost Refunds. After the payments issued to the invalid taxpayer have been addressed, refer to the steps below to correct the math error: Reverse AdvCTC for each lost payment. Include BS 05, SC 0, and HC 4. Post delay the first adjustment by 1 cycle and each adjustment following by an additional cycle (i.e., if reversing 3 lost payments, the first adjustment will have PD 1, the second will have PD 2, and the third will have PD 3). If assigning as non-streamline or invalid joint election, input a TC 971 AC 195 on the invalid/other taxpayer's entity using the from account TC 971 AC 199 entity information for the transaction date and MISC field inputs. Recalculate CTC/ACTC based on the valid taxpayer's information. Follow procedures in IRM 21.5.4.5.4, Math Error Substantiated Protest Processing, to correct the account. Reminder: CTC/ACTC will only be allowed up to the amount claimed by the taxpayer on their original return. To receive any additional amount they are entitled to, the taxpayer will need to amend their return. Caution: When the account includes other (non-AdvCTC) math errors, only correct those that can be substantiated. If the information (i.e., form, schedule, TIN, etc.) required to correct an additional math error was not provided, issue a closing Letter 4674C. Include an explanation of the adjustment(s) input. Do not suspend the case to request the missing information needed to correct the additional math error(s). Input a TC 290 .00 with BS 05, SC 0, RC 139, and HC 3. Post delay this adjustment to ensure it posts after all other adjustments on the module. Issue a closing Letter 4674C to advise the taxpayer of any corrections made to their account.

# ARPA – Excess Advance Premium Tax Credit (APTC) Repayment Relief

25.23.4.21.3 (10-01-2022) ARPA – Excess Advance Premium Tax Credit (APTC) Repayment Relief Section 9662 of the American Rescue Plan Act (ARPA), enacted on March 11, 2021, provides economic relief to taxpayers who would otherwise be required to increase their tax liability by the amount of excess Advance Premium Tax Credit (APTC) received. The rule requiring the repayment of excess APTC has been suspended for tax year 2020 only. Form 8962, Premium Tax Credit, is used to determine the correct amount of credit and compute any excess APTC the taxpayer received. Taxpayers are being instructed not to file this form when filing the tax year 2020 return. A systemic relief process will be used to correct certain accounts for taxpayers who filed their tax year 2020 return prior to the enactment of ARPA. Certain cases in IDTVA inventory were excluded from this process: Accounts with a -A Freeze on the tax year 2020 module Accounts excluded from the unemployment income tax systemic relief process Taxpayers who filed their tax year 2020 return prior to the enactment of ARPA are not required to file an amended return to receive this relief. Exception: If the reversal makes the taxpayer eligible for a credit not claimed on their original return, they must file an amended return to claim the credit. Accounts that have been corrected will reflect an adjustment with the following characteristics: Note: Excess APTC adjustments may include the recalculation of total tax and credits included on the original return. Taxpayers will receive a notice if the adjustment results in a tax or credit change. IRN 867- (negative): The amount will equal the amount of the APTC REPMT (IRN 868) located on IDRS CC IMFOLR. SC: 3 RC: 152 When you have made a determination of identity theft or invalid joint election (IJE) for TY 2020, excess APTC must be addressed, if present. When the TY 2020 valid return posted first, any excess APTC assessed must be reversed if the module was not included in the systemic relief process. Math verify the taxpayer's return. Recalculate tax and credits claimed, if necessary. Input an adjustment to reverse the excess APTC using the following: BS 05 SC 0 TC 290/291 IRN 867− (negative) for the amount posted with IRN 868 (located on IDRS CC IMFOLR) RC 152 and RC 139 HC 3 When the TY 2020 valid return is a TC 976/977, math verify the taxpayer's return. Ensure the taxpayer has not included excess APTC in the calculation of their total tax. Recalculate tax and credits claimed, if necessary. Input the adjustment following normal procedures based on the determination made. Issue a closing Letter 4674C to advise the taxpayer of any changes made related to excess APTC.

# IRPTR/IDRS Data Decision Tree

Exhibit 25.23.4-1 IRPTR/IDRS Data Decision Tree (1) This Exhibit provides supplemental information and is intended to be used when following procedures in IRM 25.23.4.8.2.3, Identity Theft (IDT) with IRP Data or Schedule C Involvement, to make an identity theft determination. (2) Use a 3 year look back period for data available on CC IRPTRL and/or IDRS to compare criteria provided in paragraph (2) below. Additionally, a look forward period must be conducted for all subsequent years. Refer to IRM 25.23.4.6.4, Complete Case Analysis (CCA), for additional information. Note: There may be instances where an IRP doc was fabricated, or may be suspicious. Review the IDOCs carefully when conducting CCA. See IRM 25.25.1.5, Business Masterfile (BMF) Entity Fabrication (EF) Procedures, for additional guidance. (3) Review and compare the following criteria. Exception: If the account history does not contain 3 years of returns to conduct the required comparison and: • There are at least 3 years of IRPTR data, proceed to paragraph (7). • There are less than 3 years of IRPTR data, proceed to paragraph (8). Caution: When conducting research for consistency, you are determining if any of the items below have changed during the look back and/or look forward periods. • If items have not changed, see paragraph (3). • If items have changed, see paragraph (4). • If you have the same number of consistencies and inconsistencies, see paragraph (5). ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (4) You must be able to confirm consistency for at least 3 items to determine a return is valid. (5) You must be able to identify inconsistency for at least 3 items to determine a return is invalid. (6) If you have the same number of consistencies and inconsistencies, refer to the table below: If Then (1) The case includes a taxpayer statement indicating they did not file the return (i.e., Form 14039 or police report). Determine the return in question is invalid. (2) The case includes a taxpayer statement that does not address the return in question. Follow procedures in IRM 25.23.4.18.2, Requests for Additional Information (Telephone and/or Written), to request the taxpayer provide a signed statement indicating which items or returns are a result of identity theft. (3) The case does not include a taxpayer statement, and there are two returns for the tax year in question (i.e., IDT3). Make a determination of No IDT. This is a duplicate or amended return scenario. See IRM 25.23.4.10.8 , No Identity Theft (NOIDT) Determinations. (4) The case does not include a taxpayer statement and was reassigned as an IDT3 in error (i.e., one return present, duplicate return, etc.). Make a determination of No IDT. An IRS employee incorrectly identified the case as an IDT issue. See IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. (5) The case includes a taxpayer statement that does not indicate identity theft and was reassigned as an IDT1 in error (i.e., taxpayer didn't receive EIP, etc.). Make a determination of No IDT. The case is not identity theft and was reassigned in error. As a result, the case will be resolved as an IRS initiated case following procedures in IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations. Reminder: A case reassigned to the Centralized Distribution Site (CDS) in error may be returned to the originating site. (7) There may be instances when you do not have 3 years of returns filed. If your research supports a determination of valid or invalid, refer the case to your lead/manager for concurrence. The CSR/TE must input a case note documenting their determination prior to requesting lead/manager concurrence. The lead and/or manager cannot concur with a determination that is not noted on the case. See the following example: Example: A taxpayer states he was incarcerated during 2019 and 2020 and provides a printout indicating incarceration for the years in question. Research of IDRS results in the identification of a 2018 tax return reporting verifiable income per IDRS CC IRPTR and a 2019 tax return reporting unverified wages and withholding. You do not have 3 years of account history to compare. Based on the information available, the 2019 return can be determined invalid. Lead/manager concurrence must be obtained. (8) If you do not have 3 years' worth of IRP data, but your research supports a determination of valid or invalid, refer the case to your lead/manager for concurrence. The CSR/TE must input a case note documenting their determination prior to requesting lead/manager concurrence. The lead and/or manager cannot concur with a determination that is not noted on the case. See the following example: Example: A taxpayer files Form 14039 stating that he is not required to file. IRPTR data shows only Social Security benefits. The address on the IRP doc matches the address provided on the Form 14039. One tax return has been received for the current year, and there is no history of filing for the 3 immediately preceding years. The return in question can be determined invalid per IRPTR data.

# Form 3245 Reversal

Exhibit 25.23.4-2 Form 3245 Reversal (1) All highlighted areas of Form 3245 and any additional areas applicable to your case must be completed and legible for processing or it will be rejected back to the originating location. Also, a current TXMOD print must be attached or the Form 3245 will be rejected. Ensure the DLN of the TC being reversed is annotated in the remarks field. See IRM 25.23.4.16, Form 3245/3809 Reversals, for additional information. Fields required to be completed for Form 3245The following fields are highlighted: SSN/TIN; Tax Period; MFT; Name; Schedule Date; TC; Amt. of Check; Remarks; Date; SPL REF; Requestor SEID; Other (box checked). Please click here for the text description of the image.

# Form 3809 Reversal

Exhibit 25.23.4-3 Form 3809 Reversal Fields required to be completed for Form 3809The following fields are highlighted: Name and address; X-ref. TIN; X-ref. MFT; X-ref. tax per.; Transaction date; 1st TC Debit amount; Transaction date; Credit amount; Explanation; Prepared by; and Date prepared. Please click here for the text description of the image. (1) All highlighted areas of Form 3809 and any additional areas applicable to your case must be completed and legible for processing or it will be rejected back to the originating location. Also, a current TXMOD print must be attached or the Form 3809 will be rejected. Ensure the DLN of the TC being reversed is annotated in the explanation field. See IRM 25.23.4.16, Form 3245/3809 Reversals, for additional information.

# Identity Theft (IDT) Functional Routing and Referral Chart

Exhibit 25.23.4-4 Identity Theft (IDT) Functional Routing and Referral Chart (1) The chart below should be used to expedite the routing or referring of cases that must be worked by another IDTVA function or an area outside AM. See IRM 21.5.1.5.1, CII General Guidelines, and Exhibit 3.13.6-1, Appendix A - Document Types, Category Codes, IMF. Reminder: Prior to referring a case to another function, the documentation submitted by the taxpayer should be reviewed to determine whether the case should be retained or routed to another function. See paragraph (2) of IRM 25.23.2.3.2, Assessing the Scope of the Taxpayer's Issue. (2) See below for Freeze Code conditions and applicable IRM references. Freeze Code Conditions IRM Reference (1) -E Freeze Refer to IRM 21.5.6.4.10, -E Freeze. There may be several conditions that require the case to be referred to Exam. Note: If TP is alleging IDT, refer to IDTVA Specialty Functions, per IDTVA Routing Matrix. (2) F- Freeze (Frivolous Filer) Refer to IRM 21.5.3.4.16.7, Identifying Frivolous Returns/Correspondence and Responding to Frivolous Arguments, for routing instructions. (3) P- Freeze Refer to IRM 21.5.6.4.31, P- Freeze, with the following conditions; Modules with TC 841 DLN Blocking Series 77711, 77712 or 77713. Only RIVO employees can release the refund. Prepare a 4442/e4442 to RIVO using category RICS RIVO – Unresolved Module Freeze Only when the modules have a TC 841 with DLN Blocking Series 77711, 77712 or 77713. If there is no "–A " currently on the account, prepare a Form 4442/e4442 to RIVO using the appropriate referral category and close your case. If there is a –A freeze, prepare a 4442/e4442 to RIVO after resolving –A freeze. Refer to IRM 21.5.6.4.31.2, P- Freezes with Return Integrity Verification Operations (RIVO) Involvement, for cases with the following condition: Module with a TC 971 AC 123 with MISC field TPP Recovery. paragraph 4 in the chart, refer to box 5 or 6 depending on whether the review time frame has passed. (4) -R Freeze Refer to IRM 21.5.6.4.35.3, -R Freeze Overview For Accounts With Return Integrity Verification Operations (RIVO) Involvement, (R Freeze with RIVO involvement and no –A Freeze). Prepare a 4442/e4442 to RIVO using category RICS RIVO – Unresolved Module Freeze Only when the modules have a TC 841 with DLN Blocking Series 77711, 77712 or 77713. All other - R freeze conditions should be worked by AM IDT employees. (5) Z- Freeze or -Z Freeze Refer to IRM 21.5.6.4.51, Z- Freeze, and IRM 21.5.6.4.52, -Z Freeze, as appropriate. Take no action unless the Z-/-Z freeze is released. Caution: Do not follow SDC instructions which deviate from established procedures. Established procedures do not permit SDC determinations of the CN owner. (3) See below for Functional Referrals conditions and applicable IRM references. Functional Referrals IRM Reference (1) Civil Penalty (MFT 55) Refer to IRM 21.2.4.3.3.2, Civil Penalty Module Processing. (2) Non-Tax Related Form 14039 with a TC 971 AC 505 with the following incident numbers: IR20160127510 IR20160127513 IR20160614508 AND No tax account issue Route the Form 14039 to IDTVA-I, per IRM 25.23.2.11, Get an Electronic Filing PIN Incident. (3) Cases withInternational Issues Case should be reassigned to the IDTVA International holding number, unless the exception below applies. Exception: Form 1116 is not required unless the taxpayer's foreign source income is passive and total creditable foreign taxes are not more than $300 ($600 if married filing a joint return). You can accept the taxpayer's figures if under these thresholds. Refer to IRM 21.8.1.2.14, International Forms Processing, and IRM 21.6.3.4.1.6.(4), Form 1116, Foreign Tax Credit, for additional guidance. The International holding number can be located on the Accounts Management Site Specialization Temporary Holding Numbers located on SERP. When the case involves both International and IDT Specialty Functions, the employee will document the request to reassign the case in a CII case note. Once the lead/manager approves the reassignment, update the case with the following: Work Type: IMF INTL Doc Type: ID Theft IDT1 Category: IDT1 Program: 40011 Function: ADJ-710 Campus: PSC Reassign the case using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases found on the IDTVA Hub. The International team will retain the case and may contact the appropriate ID Theft Liaison for assistance with case resolution. (4) Insolvency -W Freeze (TC 520 CC6X) -V Freeze (TC 520 CC81) Refer to Centralized Insolvency Operation (CIO) Team Assignment. (5) "Third-Party Checks/Returned Refund Checks" If AM receives a 3rd party bank check (physical check) refer to IRM 25.25.8.11, Centralized Check Procedures (CCP) If AM receives a photo copy of a 3rd party check or correspondence saying I received this check what should I do? Correspond with the taxpayer and tell them to return the check to the bank etc. There should be rare instances when an AM employee is in receipt of a 3rd party check. When following the above procedures, please disregard guidance intended for RIVO employees. Also see IRM 21.4.3.5.4, Returned Refund Check Procedures, for additional information. (6) Refund Inquiry:Form 3911, Taxpayer Statement Regarding Refund, Form 1310, Statement of Person Claiming Refund Due a Deceased Taxpayer, or correspondence received and the module has RIVO involvement Forward the documentation to RIVO. Open an IDRS control to RIVO IDRS # 1485099999. Forward the documentation to RIVO Stop # 6579 AUSC using the CII reroute feature. Do not send a Letter 86C. (4) See below for case types converted in error and applicable IRM references. Converted in Error IRM Reference (1) CP 36F IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview. Cases with Duplicate Filing Notice CP 36F present on CC TXMOD are worked in Accounts Management, Adjustments in Brookhaven. A CP 36F tool is used to convert cases to IDT1/3 or IDS1/3. If a CP 36F cases was converted in error, convert the case back to CP 36F and reassign the case to CP 36 holding number listed on the Accounts Management Site Specialization Temporary Holding Numbers. A case note should be left on AMS explaining why the case is being returned. (2) DUPF IRM 21.6.7.4.4 (1), Duplicate or Amended Returns - TRNS36. Cases with Duplicate Filing Notice CP 36I, 36N, 36P, 36U, 36V present on CC TXMOD are systemically assigned to IDT. Before following the IDT process on these or on any case that started as DUPF, verify DUPF criteria. If the case should be DUPF, follow procedures in IRM 25.23.4.10.5.4 , Amended or Duplicate Returns and Identity Theft (IDT) - NO IDT Determinations. Note: IDTVA Specialty Functions employees will not work these cases. Cases referred by an IDTVA employee to IDTVA Specialty Functions in error will be returned following procedures in Exhibit 25.23.4-5, IDTVA Routing Matrix. Cases referred by functions outside of IDTVA will be reassigned using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases available on the IDTVA Hub. Reminder: IDTVA-A employees - do not reassign the following transcripts to IDTVA Specialty Functions unless there is an open and/or active identity theft (IDT) claim or a previous assessment that may require an IDT determination: TRNS 36, 36D, 36I, 36N, 36P, 36S, 36U and 36V. See IRM 25.23.4.6.1, Required Research, for additional information. (3) IDT4 Non-tax-related and Full Scope trained employees will resolve the case. See IRM 25.23.4.4, Taxpayer Inquiries Involving Identity Theft (IDT). (4)IDT7 Fraudulent Return Request (FRR) Program Reassign to holding number listed on the Accounts Management Site Specialization Temporary Holding Numbers (5)IDTX Form 15227 Application for IP PIN (English) Reassign to holding number listed on the Accounts Management Site Specialization Temporary Holding Numbers Form 15227 Application for IP PIN (Spanish) Reassign to holding number 1183001929 (6) NFR - Non-Filer Reject IRM 21.5.3.4.10.1, Non-Filer Reject Returns, received in error should be sent back to the originating site. (7) Preparer Misconduct See IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, and IRM 25.24.1.4.1, Routing Information - Paper. Examples include cases where the TP did not sign or did not authorize the filing of a return, and cases where the TP did authorize the return. Cases received in error should be sent back to the originating site. (5) See below for transcript types received in error and applicable IRM references. Transcripts received in error should be returned to Accounts Maintenance at the originating site. AMRH - Transcripts IRM Reference (1) AM01 and AM17 IRM 21.2.4.3.18, Return Integrity & Verification Operation (RIVO) and Criminal Investigation (CI) Transcript Issues. IRM 21.2.4.3.19, Transcripts with Identity Theft (IDT) Involvement, cases without prior IDT controls. (2) AM05 IRM 21.2.4.3.36.1(3), AM05 Resolution. If the module is frozen due to a TOP offset reversal, identified by TC 290.00 HC 4 with TC 766 for the amount that was offset with IDRS activity FRAUDCASE and category DMFC, or a prisoner return identified by TC 290.00 HC 4 and TC 971 AC 140. This type case will be resolved by RIVO. (3) Unresolved Credit Transcripts IRM 21.2.4.3.10, Applying Unresolved Credits for AMRH. (4) IRSN Transcripts IRM 21.2.4.3.30, Transcripts with Internal Revenue Service Numbers (IRSN) and Individual Taxpayer Identification Numbers. (5) AM04 IRM 21.2.4.3.35, Duplicate Return (04-A). (6) AM16 IRM 21.2.4.3.50.1, AM16 Resolution.

# IDTVA Routing Matrix

Exhibit 25.23.4-5 IDTVA Routing Matrix (1) With identity theft (IDT), in most cases, there should be one single point of contact for a taxpayer. To identify the correct point of contact a matrix was developed to identify the area that will take ownership of the case and be the single point of contact for the taxpayer. (2) When multiple teams are involved within the same area, the employee with the oldest IRS received date will take ownership of all years. Example: There are 2 tax years, 2018 and 2019, open for the same taxpayer within the IDTVA Specialty AUR function but assigned to 2 different employees, the employee that has the oldest IRS received date will take ownership and work all impacted years unless the case was started. (3) When research indicates a taxpayer is impacted by identity theft that requires resolution by an IDTVA Specialty Function and a Mixed Entity or scrambled SSN issue exists for another year, the IDTVA Specialty Function will resolve all identity theft years following normal procedures. Upon completion of all necessary actions to address the identity theft, reassign the mixed entity or scrambled SSN issue using the IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA HUB Reminder: IDTVA-A and IDTVA Specialty employees – review the IDTVA-A CII Reassignment Guide or IDTVA Specialty CII Reassignment Guide for Non-IDT Cases located on the IDTVA Hub for additional information for reassignment of cases that involve issues with mixed entity, scrambled SSN, MFT 29 (Form 5329 Part III through VIII only), etc. Reminder: IDTVA-A employees - do not reassign the following transcripts to IDTVA Specialty Functions unless there is an open and/or active identity theft (IDT) claim or a previous assessment that may require an IDT determination: TRNS 36, 36D, 36I, 36N, 36P, 36S, 36U and 36V. See IRM 25.23.4.6.1, Required Research, for additional information. . (4) IDTVA Exam employees, refer to IRM 25.23.10.4, Identity Theft Cases with Multiple Specialty Function Involvement, for additional information when working cases with open AUR or ASFR issues. (5) IDTVA AUR employees, refer to IRM 25.23.10.4.1, Identity Theft Cases with AUR Involvement, and IRM 25.23.10.4.2, Identity Theft Cases with ASFR Involvement, for additional information when working cases with open ASFR issues. (6) Within IDTVA, there are different roles, responsibilities and authorities. To assist with routing cases to the correct area, the matrix below outlines the different authorities and types of cases that may be worked by an area. Function Authority (1) Tax Court/ Appeals Address assessments made by Appeals or cases currently in Appeals. For additional information, refer to IRM 25.23.10.4.7 , Requests for an Appeal. (2) Exam Address assessments made by Exam, AUR, ASFR and any other non-assessment cases. (i.e., non-Compliance cases where the taxpayer is claiming IDT but has non- Compliance involvement.) Example: a taxpayer is claiming IDT for tax years 2018 and 2019. The 2018 year has Exam involvement and the 2019 has no Exam involvement, refer both years to the IDTVA Specialty Exam holding number. (3) AUR Address assessments made by AUR and any other non-assessment cases. (i.e., non-Compliance cases where the taxpayer is claiming IDT but has non-Compliance involvement.) AUR can address assessments made by ASFR as well. Example: a taxpayer is claiming IDT for tax years 2018 and 2019. The 2018 year has AUR involvement and the 2019 has no AUR involvement, refer both years to the IDTVA-Specialty AUR holding number. A taxpayer is claiming IDT for tax years 2016 – 2020. The 2016 year has an ASFR assessment and the 2020 has an AUR assessment, refer all years to the IDTVA Specialty AUR holding number. (4) ASFR Address assessments made by ASFR and any other non-assessment cases. (i.e., non-Compliance cases where the taxpayer is claiming IDT but has non-Compliance involvement). (5) CSCO No assessments made; address cases with TDI status 02 issues and TDA. (6) ACSS Address cases in status 22/24 and any other non-assessment cases. (i.e., balance due situations and other years where there is non-Compliance involvement and TDI Status 03). (7) AM Compliance assessments not made (8) BMF Use of individual PII to establish fictitious businesses (EIN). For additional information, see IRM 25.23.2.4.3, Tracking Individual Taxpayers Reporting to be Victims of Business-Related Identity Theft. Exception: When a taxpayer is reporting an identity theft incident related to a Small Business Administration (SBA) Loan applied for using their name and/or TIN, do not refer the case to BMF IDT. These cases will be treated as non-tax-related identity theft. Update the category code to IDT4, and refer to IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4 Overview. (9) Frivolous Return Program (FRP) FRP is no longer part of Compliance. FRP was moved under the RICS Organization in October 2014. See IRM 25.25.10.19, Coordination with Program Stakeholders, for additional information. Cases with FRP Involvement should be referred to the FRP team under the RICS Organization. These cases can be identified with one or more of the following: A TC 971 AC 089 on the year in question A Civil Penalty MFT 55 with a penalty reference number (PRN) 543 or 666 A TC 420 with or without a TC 300 with the Project Code 310 or 313 Refer cases to the FRP team as follows: Open an IDRS control with activity IDTVARefer and category code FRPI assigned to 0586911111. Caution: The presence of a TC 810 with code "4" alone does not mean it automatically meets Frivolous Return criteria. The above criteria must be met to refer to FRP. If the account contains a TC 810 with code "4" but does not meet the criteria above, refer to IRM 25.23.4.10.12, Identity Theft (IDT) Cases with -E Freeze, for procedures. Note: For additional information, see IRM 25.25.10.8.6, (5), Identity Theft Screening. If the IDT allegation covers multiple years and at least one year meets FRP criteria listed above, resolve all years that do not have FRP indicators. Upon completion of account actions for those years, refer any years with FRP indicators to FRP for resolution. If research has been completed and you have made a determination prior to identifying the FRP issue, you may input a CII case note to provide that information. Note: When referring the MFT 55, include the MFT 30 module. Do not make adjustments to the MFT 30 module. Example: A taxpayer alleges IDT on tax year 2021, 2022 and 2023. The 2021 has a TC 810 with a code 4, the 2022 and 2023 do not contain any FRP indicators, the IDT determination and any necessary account adjustments for 2022 and 2023 must be done before routing to FRP. If all years included in the IDT allegation have FRP indicators, do not take action on the account. Instead, refer the case directly to FRP for resolution of all years. If research has been completed and you have made a determination prior to identifying the FRP issue, you may input a CII case note to provide that information. IDTVA referrals to FRP that need to be addressed by multiple functions other than IDTVA will be coordinated with Return Integrity Operation (RIO) HQ to streamline case resolution and will be elevated to ITVA-HQ. Document your research in a CII case note, and close the case. (10) Department of Justice (DOJ) Prepare and email Form 4442 using the subject line: Department of Justice (or similar) to ITVA HQ. Include all DOJ communications and documents received. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case for 15 business days. (7) Prior to referring a case to another function, the documentation submitted by the taxpayer must be reviewed to determine whether the case should be retained or routed to another function. CII case notes will be input to document the reason for routing or reassigning the case. See paragraph (2) of IRM 25.23.2.3.2, Assessing the Scope of the Taxpayer's Issue. Reminder: If you are preparing the case to reroute to another function using CII, any linked cases, IDRS screen captures, and attached files do not print. If any of these items must be attached to the case, print the items using your local printer and manually associate the printed documents. See paragraph (7) in IRM 21.5.1.5.2, Cases Currently Assigned in CII, for additional information. (8) The Tables in paragraph (11) outline case transfer guidelines; however, in some instances transfer of ownership is not necessary. If a case does not warrant transfer, the CII case notes should be documented why the case was not reassigned. Below are examples that illustrate when transferring ownership is not warranted. Example: #1 - A case has an Exam and AUR assessment on the same tax year. The Exam assessment is based upon the disallowance of a dependent and the Earned Income Credit. The AUR assessment is based upon underreported income. The taxpayer submits Form 14039 which states that they have no knowledge of the income reported under their SSN. Since the Form 14039 clearly states it is in reference to the underreported income, the case should not be transferred to IDTVA Specialty Exam since AUR assessed underreported income. Example: #2 - A taxpayer claims IDT on tax year 2017 and 2018 and was received in IDTVA-A. The 2017 tax year has an Exam assessment that was closed with a TC 300 and disposal code (DC) 13 with a technique code (TC) 6. The 2018 tax year has no Compliance involvement. Since the 2017 was closed with a DC13 and TC6, the case should not be transferred to IDTVA Specialty Exam. The DC13 indicates no response to the audit. There is a high likelihood the 2017 is IDT. (9) When accounts have been adjusted and issues remain on the account or an account was adjusted incorrectly, the case will be referred back to the person that worked the case unless otherwise stated in your functional IRM. This includes cases with Compliance involvement that were worked by an IDTVA non-specialty team, or has TAS involvement. Exception: If you discover an erroneous refund, refer to IRM 21.4.5.2, Erroneous Refunds Overview. The employee that identifies the erroneous refund is required to complete and forward the required documentation to SP. Attach a copy of the erroneous refund documentation to CII and return the case to the person who caused the erroneous refund. Also explain why the case is being referred. Example: A taxpayer claims IDT and there is an open TC 420. The account is adjusted by an IDTVA-A employee. There is a K freeze on the account; which froze the refund on the account; the case will be referred back to the IDTVA-A employee that adjusted the account. Example: An account was adjusted to an IDT claim. The case was identified that a credit transfer was not completed. The case was identified as part of the IPSU inventory global review process. In this situation, the case meets IRM 25.23.3.2.1, Simple Adjustments. The IPSU trained IDTVA employee would retain the case and make the necessary corrections. (10) The routing guidance below is for cases with IDT allegations only. If there are other, non IDT issues, do not use this routing chart. Follow normal procedures. See IRM 21.5.1.5.1, CII General Guidelines, and Exhibit 3.13.6-1, Appendix A - Document Types, Category Codes, IMF. Note: When referring a case to the IDTVA Specialty teams (Compliance) with an imminent statute date (90 days or less) follow IRM 25.23.2.5, Statute Protection and update the CII priority code 2. (11) When it is determined that another area must take ownership of a case, follow the chart below for the correct routing. Note: Do not issue any correspondence requesting additional information from the taxpayer or input any account adjustments prior to re-assigning. If And Then (1) -LW freeze and AIMS status is 80 – 89 Open in Appeals PBC 6XX Update CII data to: Doc Type: Exam Open IDT Category Code IDI1 Program Code 710-40211 Set Priority Code to 2 Reassign to ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, reassign case to that employee number. Note: For Exam: See IRM 25.23.10.4.7.1, Cases with -L or W Freeze Codes, if multiple tax years impacted by IDT but only 1 year is under Appeals jurisdiction. Exception: Cases in AUR with Appeals involvement will be retained in AUR and worked in accordance with IRM 25.23.2.5, Statute Protection. (2) -L freeze and AIMS status is 08 and below Open in LB&I - PBC 3XX IMF Resolve case where received unless there are multiple years impacted by IDT with at least one year with any other Exam involvement, and the case is in AIMS status 09 or above or there is an Exam assessment. If impacted by IDT with Exam involvement, update CII data to: Doc Type: Exam Open IDT Category Code: IDI1 Program Code: 710-40211 Set Priority Code to 3 Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: "Exam Spanish IDT" . Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, route all cases to that employee number. Note: .If the case is retained and not reassigned to IDTVA-Exam, send a secured email to the LB&I IMF liaison to inform Exam the IDT issue was resolved. The liaison can be located on SERP under Who/Where, AM Identity Theft Functional Liaisons. Use Email Subject: Resolved IDT Open in Status XX. Within the body of the email, provide the TIN, tax year, and IDT determination (i.e., XXX-XX-1234 201412 - Taxpayer is a victim of IDT, no filing requirement, account backed out). IDTVA Specialty Exam: See IRM 25.23.10.6.4.3, Returning Cases to Exam, for additional information. Exception: If an IDT allegation is received in IPSU and there are no open controls, update CII as stated above. (3) -L freeze and AIMS status is greater than 09 Open in LB&I - PBC 3XX Route to appropriate group using the listing on SERP under Who/Where tab. Then look under Exam Employee Group Code (EGC) Contacts. Exception: For PBC 315, refer to the "Disbanded-Renumbered Groups" tab in the EGC listing to obtain the new PBC number. Note: If multiple years are identified on the IDT claim, only the PBC 3XX tax years are referred to LB&I. All other years, including the CCA years, will be worked in IDTVA following normal procedures. (4) -L freeze and AIMS status is 09 and below Open in Campus Exam -(EGC 5XXX) Resolve case where received unless there are multiple years impacted by IDT with at least one year with Exam involvement and the case is in AIMS status 10 or above or there is an Exam assessment. If impacted by IDT with Exam involvement, Update CII data to: Doc Type: Exam Open IDT Category Code IDI1 Program Code 710-40211 Set Priority Code to 3 Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: "Exam Spanish IDT" . Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, route all cases to that employee number. Note: If case is retained and not reassigned to IDTVA-Exam, send a secured email to the IDTVA-Exam liaison to inform Exam the IDT issue was resolved. The liaison can be located on SERP under Who/Where, AM Identity Theft Functional Liaisons. Use Email Subject: Resolved IDT Open in Status XX. Within the body of the email, provide the TIN, tax year and IDT determination, i.e., XXX-XX-1234 201412. Indicate "Taxpayer is victim of IDT no filing requirement, account backed out" . IDTVA Specialty Exam, see IRM 25.23.10.6.4.3, Returning Cases to Exam, for additional information. Exception: If IDT allegation is received in an IPSU case and no open controls, update CII as stated above. (5) -L freeze and AIMS status is greater than 09 Open in Campus Exam - (PBC 19X or 29X and EGC 5XXX) Update CII data to: Doc Type: Exam Open IDT Category Code IDI1 Program Code 710-40211 Set priority code to 3 Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: "Exam Spanish IDT" . Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, reassign case to that employee number. (6) -L freeze and AIMS status is 10 and below Open in Field Exam - (PBC 20X and EGC 1XXX or 2XXX only) Do not route to Field Exam. All IDTVA functions will retain and resolve case. Once account is resolved, send a secured email to the Field IDT Coordinator to inform them the IDT issue was resolved. The Field IDT coordinators can be located on SERP under Who/Where, AM Identity Theft Functional Liaisons, Field Exam at: AM IDT Functional Liaisons Note: Use Email Subject Line: Resolved IDT Open in Status XX. Within the body of the email, provide the TIN, tax year and IDT determination, i.e., XXX-XX-1234 201412. Indicate "Taxpayer is victim of IDT" , no filing requirement, account backed out. Exception: If IDT allegation is received in an IPSU case and no open controls exists, route to Field Exam. (7) -L freeze and AIMS status is greater than 10 Open in Field Exam - (PBC 20X and EGC 1XXX or 2XXX only) Route to appropriate area using the Exam Employee Group Code (ECG) Contacts. listing on SERP under Who/Where tab. (8) AIMS is 90 Closed with a disposal code (DC) 12 or 37 Campus Exam - (PBC 19X or 29X and EGC 5XXX) Update CII data to: Doc Type: Exam Open IDT Category Code IDI1 Program Code 710-40211 Set Priority Code to 3 Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: "Exam Spanish IDT" . Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, re-assign case to that employee number. (9) Appeals Posted TC 30X TC 300 input by Appeals -(PBC 6XX) Update CII data to: Doc Type: Exam Closed IDT Category Code IDI1 Program Code 710-40211 Set Priority Code to 2 Reassign to ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, re-assign case to that employee number. Note: For Exam: See paragraph (7) IRM 4.13.1.3.2, Function Responsible & Routing Instructions, for case disposition and whether to retain case or return to Appeals. (10) Posted TC 30X – Exam Assessment input by Campus Exam - (PBC 19X or 29X and EGC 5XXX) Exception: If EGC is 54XX or 58 TEFRA see (12) below. Update CII data to: Doc Type: Exam Closed IDT Category Code IDI1 Program Code 710-40211 Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: "Exam Spanish IDT" . Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, reassign case to that employee number. Note: If the case was closed with a TC 300, disposal code (DC) 13, technique code 6/7. Do not reassign to Exam unless there are open controls or other unresolved years. If no open controls, cases closed with a DC 13 TC 6/7, case can be worked by function within IDTVA. Exception: If IDT allegation is received in an IPSU case and no open controls exists, route to Exam. Exam audit issues can be determined by the project code assigned the case. The project code can be identified by the SPCL-PROJ code on TXMOD under the TC 424. The project code look up table can be found on SERP. SERP/Exam Project Code Search (11) Posted TC 30X – Exam Assessment input by Field Exam - (PBC 20X and EGC 1XXX or 2XXX only) Update CII data to: Doc Type: Exam Field Closed IDT Category Code IDI1 Program Code 710-40211 Reassign to ≡ ≡ ≡ ≡ ≡ ≡ Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, route all cases to that employee number. If multiple years, link case (s) and reassign all cases to IDTVA Specialty Exam as outlined above. (12) TC 420 and no TC 300 or TC 420 and TC 300 – TEFRA – Non TEFRA PBC 295 or 398 with EGC codes 54XX or 58XX Update CII data to: Doc Type: Exam Closed Category Code IDI1 Program Code 710-40211 ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ (13) TC 420 and/or TC 300 Closed - LB&I PBC 3XX including PBC 315 Exception: Do not route PBC 398 with ECG 54XX or 58XX to LB&I, see (12) above IDT claims for closed LB&I cases are referred directly to the SBSE Reconsideration team located at 2970 Market Street, Philadelphia, PA 19106, Mail Stop 4-E08.200 Note: If multiple years are identified on the IDT claim, only the PBC 3XX tax years are referred to LB&I. All other years, including the CCA years, will be worked in IDTVA following normal procedures. (14) TC 922 - AUR involvement No TC 290 Determination to reassign or retain the case depends on the last Process Code assigned. If you are not trained to work AUR Specialty cases, reassign the case. Update CII data to: Doc Type: AUR Open IDT Category Code IDI2 Program Code 710-40222 Set Priority Code to 3; if last PC is 75 or 95, set Priority Code to 2 Note: Use Priority Code 3 for cases that have had a Statutory Notice of Deficiency issued and the taxpayer does not have time to petition the tax court. Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: Do not route cases to AUR where there is a TC 971 AC 922. These are AUR soft notices. They should be retained and worked where received. Note: Process Codes 09, 30, 55, 57, 59, 75, 95, 97, 98, 99 indicate the case is an open AUR case. Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: AUR Spanish. Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, reassign to the Specialty employee. (15) TC 922 - AUR Involvement TC 290 without an assessment to tax and/or prepaid credits Do not route to AUR, if the module has a TC 290 .00 with a TC 922 with Process Code 03, 10 - 18, 21 - 29, 44 - 48, 51, 52, 65, 70 - 74, 76, 80, or 91 - 93. Retain and resolve following normal streamline or non-streamline procedures. (16) TC 922 - AUR involvement TC 290 with assessment Determination to reassign or retain the case depends on the last Process Code assigned. If you are not trained to work AUR Specialty cases, reassign the case. Update CII data to: Doc Type: AUR IDT Recon Category Code IDI2 Program Code 710-40222 Set Priority Code to N/A Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: Do not route cases to AUR where there is a TC 971 AC 922. These are AUR soft notices. They should be retained and worked where received. These type cases do not have process codes and AUR does not have the case. Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: AUR Spanish. Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link cases. If multiple years, reassign to the Specialty employee. (17) ACSS - Status 22/24 Do not route to ACSS, if case has current or past compliance activity. Complete Form 14394, Identity Theft/RPM Case Collection Alert Instructions. Include check boxes "IDT" and "Case currently in Status 22/24/26". FAX/email the form to the applicable liaison per the instructions on the Form 14394. Complete Form 13794 as required and forward to the appropriate Collection Advisory contact Leave CII case note that Form 14394/13794 was referred to stop collection actions. Resolve case If account is in status 22/24 and there is other compliance activity that created the balance due (such as an Exam or AUR assessment) on the account then reassign to the applicable IDTVA Specialty team (AUR, ASFR or Exam) function per the guidance in this chart. Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link case, (s), and reassign to that employee number. For cases received in ACSS in status 22/24 that do not meet any of the above criteria; Update CII data to: Doc Type: ACSS Domestic IDT Category Code IDI3 Program Code 710-40231 Set Priority Code to N/A Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: ACSS Spanish. Exception: If IDT allegation is received in an IPSU case and no open controls, update CII as stated above. (18) ASFR TC 474 with TC 971 AC 143 or TC 140 OR TC 150 – SFR with a posted or pending TC 290 For open ASFR cases (TC 474 with TC 971 AC 143 or TC 140) Update CII data to: Doc Type: ASFR Open IDT Category Code IDI4 Program Code 710-40243 Set Priority Code to N/A Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB For ASFR RECON cases (TC 150 - SFR with a posted or pending TC 290 assessment) Update CII data to: Doc Type: ASFR Recon IDT Category Code IDI4 Program Code 710-40243 Set Priority Code to N/A Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: ASFR Spanish. Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link case(s) and reassign to that employee number. (19) BMF EIN account (i.e., taxpayer is reporting invalid returns, etc.) Follow guidance in IRM 25.23.2.4.3, Tracking Individual Taxpayers Reporting to Be Victims of Business-Related Identity Theft. Note: When the claim is for the taxpayer's SSN and EIN, a separate case will need to be created for the other TIN. IMF will be resolved following normal procedures, and BMF will resolve the EIN case. BMF IDT SMEs will create a CII case once it is accepted into the BMF IDT inventory. (20) Refund Hold TC 140 or TC 474 (may be present) TC 570 with 999 in the Julian date field RC "RF" displayed on IDRS for the module of the refund year -R Freeze on IDRS for the module of the refund year Do not reassign the case, all IDTVA functions will retain and resolve the case. If multiple years and there is other compliance activity (such as an Exam or AUR assessment) on the account, then reassign to the applicable AUR or Exam function per the function guidance in this chart. For cases received in CSCO and meet CSCO criteria: Update CII data to: Doc Type: Refund Hold IDT Category Code IDI4 Program Code 710-40243 Set Priority Code to N/A Reassign to the holding number using the IDTVA-A CII Reassignment Guide located on the IDTVA HUB Note: If Form 14039 or taxpayer correspondence is in Spanish, or the taxpayer marks only the "Spanish" box for their preferred language in Section C of Form 14039, update the Doc Type to: Balance Due IDT Spanish. Exception: If there is a CII case currently assigned to an IDTVA Specialty Functions employee, link case(s) and reassign to that employee number.

# IDTVA Site Locations

Exhibit 25.23.4-6 IDTVA Site Locations (1) IDTVA-A - Accounts Staff locations: Function Group Campus Location IDTVA-A (including IDT4) Accounts Management Andover Atlanta Austin Brookhaven Fresno Kansas City Memphis Philadelphia (2) IDTVA Specialty Functions locations: Function Group Campus Location IDTVA Specialty Function AUR Andover Atlanta Austin Brookhaven Fresno Philadelphia IDTVA Specialty Function Exam Andover Austin Brookhaven Fresno IDTVA Specialty Function ASFR Fresno IDTVA Specialty Function ACSS Fresno IDTVA Specialty Function DITA Philadelphia IDTVA Specialty Function TDI Fresno

# Identity Theft (IDT) Multiple Control Decision Document

Exhibit 25.23.4-7 Identity Theft (IDT) Multiple Control Decision Document (1) For additional information, see IRM 21.5.1.5.1, CII General Guidelines IDTVA-A If Multiple With Link/Close Category Control is* IDT1/IDS1 IDT3 IDT3 IDT1/IDS1 IDT3/IDS3 IDT1/IDS1 IDT1/IDS1 IDT1/IDS1 IDT8 IDT1/IDS1,IDT3 IDT1/IDS1,IDT3 IDT8 IDTVA-I If Multiple With Link/Close Category Control is* IDT4 IDT1/IDS1,IDT3 IDT4 IDT1/IDS1** IDT4 IDT8 IDT4 IDT8 * When all consolidation actions have been taken, this is the IDRS Category Code of the open identity theft case. **When the related case is an IDT3, the IDRS Category Code of the open case is updated to IDT1/IDS1. The information provided in the IDT4 case results in the case now being reclassified as IDT1/IDS1 – Taxpayer Identified. Note: Scenarios listed above are not all inclusive. Raise any additional questions related to identity theft multiple controls to your manager/lead. (2) IDTVA-I CSRs will have to coordinate to determine if the issue is actually tax related or non-tax related. (3) When the multiple control is an IDTVA Specialty Function case, all other case types will be linked and closed to allow the IDTVA Specialty employee to resolve the account issue(s). The case(s) that will remain open will be the IDTVA Specialty Function case(s) (i.e., category codes including IDIx).

# Order of Priority Listing - IDTVA-A and IDTVA Specialty Functions

Exhibit 25.23.4-8 Order of Priority Listing - IDTVA-A and IDTVA Specialty Functions (1) Identity theft cases will be resolved in a first in first out order unless a priority case or the exception below applies. For the lists below, case types are listed in the order of priority to be worked. Exception: Cases created for impacted tax years identified through Complete Case Analysis (CCA) will be worked, regardless of age, to ensure the taxpayer's identity theft issue is fully resolved without unnecessary delays. (2) The following inventory priorities have been established for IDTVA-A: Congressional cases Statute imminent TAS IDT1/IDS1 (3) IDTVA employees not trained on any of the priority programs listed above will work any IDT work (i.e., IDT4, IDT7, IDTX, etc.). (4) The following inventory priorities have been established for IDTVA-Specialty Functions: Congressional cases Statute imminent TAS Priority Code 2 cases Priority Code 3 cases

# IDTVA-A Identity Theft (IDT) Work Types Listing

Exhibit 25.23.4-9 IDTVA-A Identity Theft (IDT) Work Types Listing (1) Refer to the table below for a list of IDTVA-A (non-Specialty Functions) Category Codes and characteristics: Category Code Defining Characteristic IDT1 Taxpayer identified tax related identity theft IDS1 Spanish taxpayer identified tax related identity theft IDT3 IRS identified tax related identity theft IDS3 Spanish IRS identified tax related identity theft IDT4 Taxpayer identified non-tax related identity theft IDT6 Credit Transcripts IDS6 Credit Transcripts for Spanish cases IDT8 CP 36N or CP 36P Duplicate filing condition generated due to the presence of specific RIVO codes on the account IDS8 CP 36N or CP 36P Duplicate filing condition generated due to the presence of specific RIVO codes on the account (2) For IDTVA Specialty Functions Category Codes, refer to the second chart in IRM 25.23.2-15, IDTVA IDRS Category Controls by Function.

# Identity Theft (IDT) Closing Letter Decision Chart

Exhibit 25.23.4-10 Identity Theft (IDT) Closing Letter Decision Chart (1) When issuing a closing letter, ensure the correct paragraphs are used to inform the taxpayer of all actions taken on their account based on your specific case scenario. When issuing your letter also consider the following: If appropriate, manually input multiple tax years by inputting the tax years in the empty boxes. Up to (8) years can be input in a Letter 4674C. Reminder: If the letter includes multiple years, ensure all of the taxpayer's questions are addressed. No IDT determinations should be addressed in a separate letter when there is an IDT determination for some tax years but not all. If the language in any of the letters listed below are not appropriate for your specific case scenario, use another appropriate letter. Insert a time zone when issuing Letter 4674C. Select the appropriate paragraph to insert your time zone in the last available open field. For the appropriate abbreviation of time zones refer to IRS Style Guide - Dates and Time. If there is a valid Power of Attorney (POA) or third-party representative on file, verify the Centralized Authorization File (CAF) copy selection is input. Caution: For potential fraudulent and/or compromised POAs, refer to IRM 21.3.7.5.5.3, How To Report a Compromised or Potentially Compromised CAF Number. Note: Current programming for the CP 01 will generate a copy of the notice to a POA that is on file. If sufficient documentation has been received to validate a POA, but it is not yet on file, then issue the POA a closing letter. This ensures the taxpayer's right to retain representation and the POA's right to be informed. Address Letter 4674C to both taxpayers when issuing Letter 4674C under the primary SSN if the valid filing status for the impacted tax year(s) is Married Filing Joint (MFJ). For tax years with an Invalid Joint Election (IJE), MFJ scheme, or tax years not filed MFJ, address Letter 4674C to each impacted taxpayer individually. Note: If Spanish language correspondence is received or the taxpayer marks the "Spanish" box in Section C of the Form 14039, a reply must be issued using the Spanish version of the appropriate C letter, if one is available. See IRM 25.23.4.19, Requesting Translations of Certain Languages, if a translation of correspondence is needed. Exception: Do not issue the Spanish version of the C letter when the taxpayer specifically requests to receive the letter in English. (2) Refer to the Closing Letter Chart below: If And Then (1) TP filed a Form 14039 or similar statement There is a TC 971 AC 522 PPDS OPIP NODCRQ or EPSS DISABL (effective 1-1-17) See IRM 25.23.2.3.10, Electronic Products Service and Support (EPSS) Disabled Accounts. (2) TP A filed a Form 14039 or similar statement There is a TC 971 AC 505 with the following incident numbers: IR20160127510 IR20160127513 IR20160614508 AND There is an account issue IR20150521512 IR20150521555 IR20150521556 CR20170421067 LR20170421067 Issue a closing Letter 4674C. Include all applicable paragraphs. Note: If a closing letter was issued by RIVO already (e.g., Letter 4310C), do not issue a duplicate closing letter, unless it has been more than 30 days and/or the RIVO Letter 4310C did not provide a response to all of the actions taken on the account. (3) The case was closed with a TC 971 AC 501. A systemic CP 01 has not been issued within the three- year period per IRM 25.23.2.6.1.1, Systemic Actions Taken After TC 971 AC 501 Placed on Account Do not send the TP a closing letter. The CP 01 will systemically generate between 2 and 12 cycles after the input of the TC 971 AC 501 depending on when the taxpayer's account adjustment is completed. Exception: If additional account information needs to be relayed to the taxpayer, issue the IDT closing Letter 4674C. Reminder: CP 01/CP 01C generates only once in a three-year period. If another year was marked with a TC 971 AC 501 within the last 3 years, a Letter 4674C is required to inform the taxpayer their account was corrected. Note: If a closing letter was issued by RIVO already (e.g., Letter 4310), do not issue a duplicate closing letter, unless it has been more than 30 days and/or the RIVO Letter 4310C did not provide a response to all of the actions taken on the account. (4) Case closed with a TC 971 506 Send a closing Letter 4674C Note: Systemic letters are not issued for cases closed with a TC 971 506. You must issue a closing letter for these type cases. Note: If a closing letter was issued by RIVO already (e.g., Letter 4310), do not issue a duplicate closing letter, unless it has been more than 30 days and/or the RIVO Letter 4310C did not provide a response to all of the actions taken on the account.

# IDRS Activity Codes and Definitions

Exhibit 25.23.4-11 IDRS Activity Codes and Definitions (1) Specific activity codes were created to easily determine the status of the IDT case. Use of these activity codes is encouraged for all functions. The recommended activity codes listed below are not all inclusive. Use of activity codes is only required when specified by other IRM instructions. Note: Multiple activity codes may need to be input on the identity theft control base as the case progresses through the IDT process. Note: The Julian date input should be calculated in calendar days unless a specific case scenario below provides you with a specific date. (2) When actions are required on a case and monitoring is needed while active on CII, the recommended activity code may be used to identify the reason. Refer to the table below: Note: ### represents the Julian date for follow-up. Activity Code Definition (1) 5064/### Letter 5064C/SP to TP for additional information with the 40 day follow-up date. The Julian date input should be the purge date. (2) F/### When contacting a taxpayer by telephone, requesting information and the taxpayer will be submitting the information by fax/EEFax. Allow the taxpayer five days to submit the information. The Julian date input should be the purge date. (3) 2CATA/### When referring a case to CAT A due to meeting the by-pass DIF criteria. The Julian date input should be the purge date. (4) 9762SP### When sending a return to SP to have the TC 976 placed on the account. The Julian date input should be the purge date. (5) RTTN### When requesting a case from retention, the Julian date should be a date two cycles after the request was made using IDRS CC IMFOLB. If the two cycles have expired, monitor the case weekly until the requested modules are active. Caution: Multiple module requests could extend the time it takes for modules to come out of retention. (6) ESTENT### When establishing the entity for an account. The Julian date should be a date two cycles after input. (7) PNDMRR/### When monitoring the account for TOP Offset Reversal to post within 60 day increments, if needed. (8) DOCREQ/### When requesting a document using IDRS CC ESTAB. The Julian date should not exceed 30 days after input. (9) PNASED/### When holding a paper return until the valid return updated ASED has posted. The Julian date should be a date two cycles after input. (3) IDTVA Specialty Functions Only. When actions are required on a case that must be monitored while the case is active on CII, update the activity code to reflect the reason. Refer to the table below: Case Status Activity Code Definition (1) Before the case is closed IDTRSLVD IDT has been determined and account has been resolved. (2) Before the CII case is closed REJ(Function) When rejecting a case back to the originating function because it does not meet the criteria for IDTVA to accept the referral. (Function)-Input the function that made the referral. (e.g., AUR, Exam, CSCO or ACSS) (3) When creating a new CII case WT4CII/### When holding a paper return while waiting for a CII case to generate. (4) If monitoring on IDRS only. ALL actions must be completed prior to closing the CII case. The recommended activity codes listed below are not all inclusive. Note: By clicking the close button on CII, the case status will automatically be updated to "C". Reminder: Establish a monitor base on IDRS using Category Code "MISC" with the current date as the received date. Case Status Activity Code Definition (1) Excess Collection File (XSF) EXCSS/### Form 8758, Excess Collection File Addition, or Form 8765, IDRS Control File Credit Application, used to transfer a payment or credit to post TO and/or FROM the XSF. (2) Manual Refund MNREF/### When monitoring a manual refund to post within two cycles. (3) Moving Specific Year Account F12810/### Form 12810 used to initiate TC 370/400 procedures and monitor the posting of the moved return for the common number ("from" side) within 30 day increments. (4) Lost Refund 841/### or 700/### When crediting the account to resolve the lost refund using CC IDT48 or IDT58 and monitor the credit to post within three cycles. (5) Refund Reversal 843REQ/### or 702REQ/### When monitoring Form 3245/Form 3809 reversals for the credit to post within three cycles. (6) TOP Offset PNDMRR/### When monitoring the account for a manual TOP Offset Reversal sent to Bureau of the Fiscal Services (BFS) to post the credit within 60 day increments. (5) Listed below are activity codes to be used for case scenarios that do not include monitoring actions. Case Action Activity Code Definition (1) Before CII case is closed PRVACTN When an account was previously corrected and there are no other actions necessary. (2) Before CII case is closed OPNDNERR When a control base was created in error and will be closed.

# Tax-Related Identity Theft (IDT) Codes

Exhibit 25.23.4-12 Tax-Related Identity Theft (IDT) Codes (1) Refer to the table below for a list of tax-related IDT codes. Category Code CII Document Type CII Program Code Function and Program for Time Reporting IDT1/IDS1 ID Theft 40011 710–40011 IDT3/IDS3 ID Theft 40013 710–40013 IDT6/IDS6 ID Theft 40016 710-40016 IDT8/IDS8 ID Theft 40017 710-40017

# Format for Emails to SB/SE Examination Technical Services

Exhibit 25.23.4-13 Format for Emails to SB/SE Examination Technical Services (1) Use this email format when contacting SB/SE Examination Technical Services about a case with restitution. To: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Cc: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Subject: Identity Theft Claim with Restitution An identity theft case has been received from a taxpayer whose account reflects a restitution based assessment. Below are the pertinent case details. Taxpayer's Name: Taxpayer's SSN: Impacted year(s): Identity theft determination Reminder: Relevant documentation must be attached.

# Format for Emails to Appeals

Exhibit 25.23.4-14 Format for Emails to Appeals (1) Use this email format when sending Form 10467 electronically to Appeals. To: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Subject: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Attached is Form 10467, Appeals Division Feedback Report and Transmittal Memorandum, regarding an identity theft complaint filed by a taxpayer currently open in Appeals. Please forward this email to the Appeals employee assigned the case, or associate with the case file if unassigned. Taxpayer's Name: SSN: Tax Year(s):

# ITVA HQ AUR ADR Report - For Use by IDTVA P&A and Designated Individuals Only

Exhibit 25.23.4-15 ITVA HQ AUR ADR Report - For Use by IDTVA P&A and Designated Individuals Only (1) AUR Analytics Data Retrieval (ADR) Reports provide details of open AUR cases referred to IDTVA for resolution, including: Primary SSN Secondary SSN (if applicable) Tax Year Days in Status Assigned IDTVA Campus Assigned Date (2) The report will include separate tabs for each of the sites, the managerial queue, the P&A queue, some specialty functions, RPM, and blanks. AUR cases assigned to IDTVA-A and IDTVA Exam will be provided on separate reports. Caution: Due to the combining of some teams, inventory may not be found on the expected report/tab. For example, Fresno AUR and Exam are in one team. All cases belonging to that team are on the Fresno tab of the Exam report, not on the AUR report. (3) These reports are intended to be used to ensure AUR Identity Theft cases are resolved and returned to AUR in a timely manner - generally, within 120 days of the date the PC "SI" was input. See IRM 25.23.10.6.3.2.1, IDTVA Specialties AUR Technical Research and Initial Handling Procedures, for specific details. (4) ITVA HQ is responsible for providing IDTVA P&A with the AUR ADR report regularly. The report will be emailed to the designated contact(s) identified by IDTVA P&A. (5) IDTVA P&A designated contacts are responsible for reviewing AUR ADR reports provided by HQ to identify cases meeting the following criteria: Aged 120 days or more - require immediate resolution Aged 100-119 days - require follow-up Blanks - require follow-up (6) Cases requiring follow-up must be addressed with sufficient time to allow the assigned employee to resolve the case timely, whenever possible. Take the following actions based on the status of the case: Status Action (1) The case is aged 100-110 days. Follow-up within 3 calendar days. (2) The case is aged 111-117 days. Follow-up within 2 calendar days. (3) The case is aged 118-119 days. Follow-up within 1 calendar day. Reminder: If the case can't be closed within 120 days, contact the IDTVA Functional Liaison to request additional time from AUR. (7) P&A designated contacts are expected to address cases requiring immediate resolution the same day the case is identified. Contact the frontline manager of the assigned employee and the appropriate IDTVA Functional Liaison to take the following actions based on the status of the case: Status Action (1) The case is assigned to a category code other than IDI1, IDI2, IDI5, IDI6, IDII, or RPMC. (These cases will generally be found in the IDTVA-A ADR report identified as a queue belonging to P&A or IDTVA-CSCO/ACSS. Update the Category Code to IDI2. Reassign the case following the instructions in Exhibit 25.23.4-5, IDTVA Routing Matrix, paragraph (11) Table Scenario (14). (2) The case can be closed. Instruct the employee what action is needed to resolve the case. Verify the case has been closed on the next AUR ADR Report. (3) The case is 100 days old or greater and cannot be worked within 120 days. Contact the IDTVA Functional Liaison to request additional time from AUR. Monitor the case for timely resolution. (4) The case is 100 days old or greater and can be worked within 120 days. Monitor the case for timely resolution. (5) The case was closed with PC 26. The case should be treated as an AUR Recon and should not be sent back to AUR once it is resolved. (8) Cases listed on the Blanks tab must be researched to locate where the case is. Take the following actions based on the status of the case: Status Action (1) The case was worked, and a case note was left in the AUR system. No further action is needed. (2) The case was worked, and a case note was not left in the AUR system. Contact the frontline manager of the assigned employee to have a case note input in the AUR system. (3) The case was not worked, and there is no indication the case was received. See paragraph (9). (4) The case was received and forwarded to ICT, but a CII case was not created. See paragraph (9). Note: If case cannot be obtained in time to work within 120 days, do not attempt to obtain the case from AUR. Work the case using internal research. A copy of the taxpayer's response should be viewable on AMS. The images can be found in the "Alerts" section. Click on the "CP 2000" link to find the attached documents. Reminder: If the case cannot be closed within 120 days, contact the IDTVA Functional Liaison to request additional time from AUR. (9) When a referral cannot be located and a CII case needs to be created, take the following actions: Create a new CII case: • Use the IRS received date of the Form 14039/Police Report (can be found in the Case History screen of the AUR system). • Leave a CII note indicating, Case created from ADR report, work using images available on AMS or internal research, or similar verbiage. • Update the CII data, and assign the case following the instructions in Exhibit 25.23.4-5, IDTVA Routing Matrix, paragraph (11) Table Scenario (14). (10) For instructions on how to process the cases: Specialty Exam teams - See IRM 25.23.10.4, Identity Theft Cases with Multiple Specialty Function Involvement Specialty AUR and RPM teams - See IRM 25.23.10.6.3.2.1, IDTVA Specialties AUR Technical Research and Initial Handling Procedures

# ITVA HQ Balance Due Receipts Listing - For Use by IDTVA P&A Only

Exhibit 25.23.4-16 ITVA HQ Balance Due Receipts Listing - For Use by IDTVA P&A Only (1) The weekly Balance Due Receipts Listing provides accounts information from the CCA 4243 listing to identify receipts new to IDTVA categories and there is a debit module balance. The listings include the following CCA 4243 data columns: IDRS # - consisting of Location, Group, and Employee columns Campus Function MFMODBALAMOUNT TIN MODPER NAMECTRL IRSRCDDATE STATUS CATEGORY FREEZECODES ASSIGNDDATE ACTIVITYCODE ACTIONDATE AgeFromReceivedDate (2) The listings are in IDRS number order. (3) These reports are intended to be used to ensure action is taken to suspend collection activity on accounts while the taxpayer's identity theft claim is considered. (4) ITVA HQ is responsible for providing IDTVA P&A with the Balance Due Receipts Listing weekly. The report will be emailed to the designated contact(s) identified by IDTVA P&A. (5) IDTVA P&A designated contacts are responsible for distributing the listing to the IDTVA teams. (6) The assigned employees are required to review the accounts and complete the required action per IRM 25.23.4.12, Collection Activity - Form 13794/14394. (7) The listings are to be completed by the Friday of the week received. There is no requirement to provide completed listings to ITVA HQ.

# ITVA HQ Disaster -O Freeze Listing - For Use by IDTVA P&A Only

Exhibit 25.23.4-17 ITVA HQ Disaster -O Freeze Listing - For Use by IDTVA P&A Only (1) The Disaster -O Freeze Listing provides accounts information from the CCA 4243 listing to identify accounts containing Freeze Code -O. The listings include the following CCA 4243 data columns: IDRS # - consisting of Location, Group, and Employee columns Campus Function TIN MFT MODPER NAMECTRL IRSRCDDATE STATUS CATEGORY FREEZECODES ASSIGNDATE ACTIVITYCODE ACTIONDATE AGE MFMODBALAMOUNT Weekending (2) The report will include separate tabs for IMF and BMF accounts. The listings are in IDRS number order. (3) In addition, during a federal disaster declaration period, a weekly Disaster New Listing will be provided with the Disaster -O Freeze Listing. (4) These reports are intended to be used to identify taxpayer accounts impacted by federally declared disaster declarations. (5) ITVA HQ is responsible for providing IDTVA P&A with the Disaster -O Freeze and Disaster New Listings weekly. The report will be emailed to the designated contact(s) identified by IDTVA P&A. If there are no Freeze Code -O accounts, no listing will be issued. (6) IDTVA P&A designated contacts are responsible for distributing the listing to the IDTVA teams. (7) The assigned employees are required to review the accounts and complete the required action per IRM 21.5.6.4.30, -O Freeze, and IRM 25.16, Disaster Assistance and Emergency Relief. The Freeze Code -O accounts will be reviewed for determinations and adjustments that will provide the taxpayer relief during the disaster suspense time frame. Adjustments that create or increase debt for the taxpayer will be suspended during the disaster declared time frame. (8) The listings are to be completed by the Friday of the week received. There is no requirement to provide completed listings to ITVA HQ.

# ITVA HQ Freeze Code -L Listing - For Use by IDTVA P&A Only

Exhibit 25.23.4-18 ITVA HQ Freeze Code -L Listing - For Use by IDTVA P&A Only (1) The -L Freeze Listing provides accounts information from the CCA 4243 listing to identify accounts containing Freeze Code -L. The listings include the following CCA 4243 data columns: IDRS # - consisting of Location, Group, and Employee columns Campus Function TIN MFT MODPER IRSRCDDATE CATEGORY FREEZECODES ACTIVITYCODE ACTIONDATE MFMODBALAMOUNT ASSIGNDATE AgeFromAssignedDate (2) The report includes IMF accounts only. The listings are in IDRS number order. (3) These reports are intended to be used to identify taxpayer accounts containing Freeze -L indicating open AIMS accounts in Appeals, Campus Exam, Field Exam, or Large Business and International (LB&I) functions. Data from Command Codes (CC) AMDISA, INOLES, IMFOLA, and IMFOLT are populated to the listing. The data is filtered and the AIMS information is coded per the table at the bottom of this page. Other data in the spreadsheet is highlighted to identify accounts with AUR processing codes, prior adjustments with Reason Codes 131 and 139, IRS addresses, deceased taxpayers, and IRS/Federal employee indicators. (4) ITVA HQ is responsible for providing IDTVA P&A with the -L Freeze Listing weekly. The report will be emailed to the designated contact(s) identified by IDTVA P&A. (5) IDTVA P&A designated contacts are responsible for distributing the listing to the IDTVA teams. (6) The assigned employees are required to review the accounts and complete the required action per Exhibit 25.23.4-4, Identity Theft (IDT) Functional Routing and Referral Chart, and Exhibit 25.23.4-5, IDTVA Routing Matrix. (7) The listings are to be completed by the Friday of the week received. The AgeFromAssignedDate column will identify accounts aged greater than 14 days from the assigned date and still assigned to a non-Specialty Exam team. The IDTVA P&A contact is responsible for providing an update on cases aged greater than 14 days. (8) Refer to the table below for appropriate actions and IRM references for addressing accounts on the -L Freeze Listing. PBC Status Function Action IRM IDTVA-Exam Action 6XX 8X Appeals Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix Centralized in BSC 11779 6XX 90 Appeals Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix Centralized in BSC 11779 3XX Any LB&I Route per AIMS/ERCS Contacts Exhibit 25.23.4-5, IDTVA Routing Matrix 315 90/TC 30X LB&I Route per IRM 25.23.10.7.4.4(2) IRM 25.23.10.7.4.4, Field Exam Reconsiderations 295/398 Any TEFRA/NON-TEFRA EGC 54XX/58XX - Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix 20X 00-09 Field Exam Continue to work where assigned Exhibit 25.23.4-5, IDTVA Routing Matrix 20X 10-5X Field Exam Route per AIMS/ERCS Contacts Exhibit 25.23.4-5, IDTVA Routing Matrix 20X 60-9X/TC 30X Field Exam Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix 29X 00-08 Campus Exam Continue to work where assigned Exhibit 25.23.4-5, IDTVA Routing Matrix 29X 09-90/TC 30X Campus Exam Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix 29X 24 Campus Exam Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix <90 days in ST 24, update to Priority Code 2 and work 19X 00-09 Campus Exam Continue to work where assigned Exhibit 25.23.4-5, IDTVA Routing Matrix 19X 09-90/TC 30X Campus Exam Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix 19X 24 Campus Exam Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix <90 days in ST 24, update to Priority Code 2 and work --- --- Reassign to IDI1 Exhibit 25.23.4-5, IDTVA Routing Matrix Review TXMODA and/or IMFOLT for TC 420 information

# ITVA HQ Freeze Code Z Listing - For Use by IDTVA P&A Only

Exhibit 25.23.4-19 ITVA HQ Freeze Code Z Listing - For Use by IDTVA P&A Only (1) The Z Freeze Listing provides accounts information from the CCA 4243 listing to identify accounts containing Freeze Code Z. The listings include the following CCA 4243 data columns: IDRS # - consisting of Location, Group, and Employee columns Campus Function TIN MFT MODPER IRSRCDDATE CATEGORY FREEZE CODES ACTIVITYCODE MFMODBALAMOUNT (2) The report will include separate tabs for IMF and BMF accounts. The listings are in IDRS number order. (3) These reports are intended to be used to identify taxpayer accounts containing Z Freezes. (4) ITVA HQ is responsible for providing IDTVA P&A with the Z Freeze listing weekly. The report will be emailed to the designated contact(s) identified by IDTVA P&A. If there are no Freeze Code Z accounts, no listing will be issued. (5) IDTVA P&A designated contacts are responsible for distributing the listing to the IDTVA teams. (6) The assigned employees are required to review the accounts and complete the required action per IRM 21.5.6.4.52, -Z Freeze, and Exhibit 25.23.4-4, Identity Theft (IDT) Functional Routing and Referral Chart. Return Preparer Misconduct accounts will be reviewed and action taken per IRM 25.24.2.5.2.2, Criminal Investigation (CI) Involvement. (7) The listings are to be completed by the Friday of the week received. There is no requirement to provide completed listings to ITVA HQ.

# TC 971 AC 199 MISC Field Descriptions for Economic Impact Payments (EIPs)

Exhibit 25.23.4-20 TC 971 AC 199 MISC Field Descriptions for Economic Impact Payments (EIPs) (1) Refer to the table below for a list of TC 971 AC 199 MISC field descriptions used to identify an EIP computed amount per individual: Note: Additional miscellaneous fields and their descriptions can be found in IRM 21.6.3-2, TC 971 AC 199 MISC Field Descriptions for Economic Impact Payments (EIPs). TC 971 AC 199 MISC Field Description (1) "nnnnnnn REB2019" EIP was computed and issued based on the tax year 2019 return. Note: Currently REB2019 is also present for EIPs that were issued to SSI/VA recipients. A ticket has been submitted to correct these accounts. (2) "nnnnnnn REB2018" EIP was computed and issued based on the tax year 2018 return. (3) "nnnnnnn REB1099" EIP was computed and issued based on a Form SSA-1099 or Form RRB-1099. (4) "nnnnnnn REBSSI" EIP was computed and issued based on the taxpayer being an SSI recipient. (5) "nnnnnnn REBVA" EIP was computed and issued based on the taxpayer being a VA benefit recipient. (2) Refer to the table below for a list of TC 971 AC 199 MISC field descriptions used to identify SSA/RRB/SSI/VA benefit recipients that are potential candidates to receive an EIP as an auto-payment: Note: This list may not include all MISC field indicators used for EIP purposes. TC 971 AC 199 MISC Field Description (1) "SSA1099-DSI" Taxpayer was present on a Form SSA-1099 but was claimed as a dependent on another individual's tax year 2019 return. (2) "NONFILER-SSA1099" Taxpayer was present on a Form SSA-1099. (3) "RRB1099-DSI" Taxpayer was present on a Form RRB-1099 but was claimed as a dependent on another individual's tax year 2019 return. (4) "NONFILER-RRB1099" Taxpayer was present on a Form RRB-1099. (5) "SSI2019-DSI" Taxpayer SSN was provided from SSA as an SSI recipient but was claimed as a dependent on another individual's tax year 2019 return. (6) "NONFILER-SSI2019" Taxpayer SSN was provided from SSA as an SSI recipient. (7) "VA 2019-DSI" Taxpayer SSN was provided from VA as a VA benefit recipient but was claimed as a dependent on another individual's tax year 2019 return. (8) "NONFILER-VA 2019" Taxpayer SSN was provided from VA as a VA benefit recipient. (3) To prevent taxpayers from receiving duplicate payments, the account will be marked with a TC 971 AC 199 with MISC "XYZ TERRITORY" to identify the filing of a tax return in a territory. This indicator can be seen on the entity (IDRS CC IMFOLE).

# Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing

Exhibit 25.23.4-21 Input, Annotations and Action Requirements for Streamline/Non-Streamline Case Processing (1) You must consider all items in the Identity Theft (IDT) case processing charts below that apply to your case scenario. Utilizing the tables will assist you in addressing all issues to make the taxpayer whole. (2) For entity-related instructions, see the table below: If And Then (1) The TP is deceased, Update the entity information as applicable. See IRM 21.6.6.2.21.1, Updating the Entity on Decedent Accounts. (2) The TP's address is incorrect and/or requires updating, Account information and case documents have been reviewed to identify the appropriate address, Ensure the address on the CN is updated on CC ENMOD. For more information, refer to IRM 25.23.2.3.7, When to Update the Victim's Address, and IRM 3.13.5.42, Determining National Change of Address (NCOA) Address Changes. When changing an address to a Service Center address, refer to IRM 3.13.5.66, Campus Address Used Only when Taxpayer Address is Unavailable. Do Not use the Service Center's actual street address when you are unable to locate an address for the taxpayer. (3) The TP's filing status or name line is incorrect, Update the name line and/or filing status on CC ENMOD, as applicable. For the secondary spouse, if applicable, ensure the name line is updated on Masterfile for the same year or an earlier year. (4) The secondary spouse, Secondary spouse has filed married filing jointly, Input TC 594 CC 084 to satisfy the secondary TIN's filing requirement for the secondary spouse on a MFJ return, as applicable. Refer to IRM 25.23.2.6.5, Closing Identity Theft with Tax Delinquency Inquiries (TDI), for additional guidance. Note: This will ensure a TDI notice is not issued to the secondary taxpayer. (5) The MFJ IDT return(s) include two taxpayers who are not married, Input TC 592 to reverse TC 594 CC 084 cross referencing the secondary taxpayer. Note: TC 592 will reverse all TCs 59X on the module. Input of a TC 594 CC 084 cannot be post delayed. If the valid taxpayer is the secondary on a valid MFJ return, monitor the account for one week. After one week, input TC 594 CC 084 to cross reference the correct spouse. (6) If the account is affected by refund related and income related IDT, The IDT issues are for the same tax year, Use the appropriate identity theft indicator and MISC field for the refund related IDT issue. Do not input multiple indicators for the same tax year. Exception: When an impacted tax year is more than 7 years old, it may be necessary to input multiple indicators for the same tax year. See IRM 25.23.2.6, Closing Identity Theft Issues, and IRM 25.23.2.8, Miscellaneous Identity Theft Indicators, for additional information. (7) If the account is affected by refund related and income related IDT, The IDT issues are for different tax years, Use the appropriate identity theft indicator and MISC field for each impacted year. Do not input multiple indicators for the same tax year. Exception: When an impacted tax year is more than 7 years old, it may be necessary to input multiple indicators for the same tax year. See IRM 25.23.2.6, Closing Identity Theft Issues, and IRM 25.23.2.8, Miscellaneous Identity Theft Indicators, for additional information. (3) For adjustment-related instructions, see the table below: If And Then (1) TP A's (CN owner) return is received after the return due date, Refer to IRM 20.2.4.6, Unprocessible Returns, and IRM 20.2.4.6.1, Updating the RPD on Unprocessible Returns, for additional guidance. Note: This IRM will serve as official guidance for updating the RPD. (2) The invalid return reflects direct deposit information, Input a TC 971 AC 850. Include a Post Delay (PD) Code 2 in your adjustment. Note: Input of a TC 971 AC 850 will prevent direct deposit and result in the issuance of a paper refund check to the address shown on the taxpayer's entity module. (3) The return is determined to be the result of IDT, Input the adjustment including RC 139 on the account, as applicable. Input the appropriate Posting Delay and Hold Codes, as applicable. For additional guidance on Posting Delay Codes, see IRM 21.5.2.4.17, Posting Delay Code (PDC), and IRM 21.5.5.4.2.1, Cycling Transactions, to determine the appropriate number of cycles to delay your actions. (4) Incorrect information is recorded on CC DUPED, This is a current year return, Refer to IRM 21.6.1.7.1, Command Code (CC) DUPED, to correct the data to reflect the valid taxpayer's information, if applicable. Reminder: The incorrect taxpayer's information should be removed from CC DUPED. (5) Adjusting Premium Tax Credit (PTC) or Shared Responsibility Payment (SRP), Refer to the following IRMs: IRM 21.6.3.4.2.12.4, Tools for Accessing ACA-Related Taxpayer Data IRM 21.6.3.4.2.12.7, Adjusting the Account, to ensure the PTC is computed correctly, if applicable. IRM 21.6.4.4.20.3, Shared Responsibility Payment Overview IRM 21.6.4.4.20.3.1, Shared Responsibility Payment Adjustments, to determine the taxpayer's liability for the SRP, as applicable. Note: Use the appropriate Post Delay and Hold Codes, as applicable. (6) Recertification indicators are on the taxpayer's account (CCs ENMOD and IMFOLE): RECERT-IND - Displays the indicator used to identify what recertification is required for. CC ENMOD: TXPD> - Identifies the tax year the ban was set. EL-TXPD> - Identifies the tax year the ban will be lifted. CC IMFOLE: RECRT TXPD> - Identifies the tax year the ban was set. ELG TXPD> - Identifies the tax year the ban will be lifted. Identity theft returns that were audited by Exam can result in the placement of recertification indicators that will negatively impact the valid taxpayer if left unresolved. Review the account to determine if the credit disallowed was included on a return determined to be invalid. If the disallowance is related to an IDT return, the recertification indicator must be reversed. This includes cases where the valid taxpayer files a return claiming the same credits for different dependents. Refer to IRM 4.19.14.7, Recertification, for additional guidance. Use the appropriate Action Code below to reverse the indicator(s): •Earned Income Tax Credit (EITC) - Input TC 971 AC 056. •Child Tax Credit/Additional Child Tax Credit (CTC/ACTC) - Input TC 971 AC 161. •American Opportunity Credit (AOTC) – Input TC 971 AC 160. Caution: If the recertification indicator on the account is related to credits disallowed on a return determined to be filed by the CN owner, do not reverse the indicator. Reminder: When there are recertification indicators present as a result of a return filed by the valid taxpayer, recertification requirements must be considered prior to inputting adjustments for tax years that fall within the covered period. (4) For miscellaneous actions and annotations, see the table below: If Then (1) There are multiple CII cases, Link all related cases, including cases under the spouse's TIN. After completing all actions, close all related cases except ITAR. (2) More than one TC 976 return has posted to the module, Notate on CII "DUP (DLN) (last 6 digits of the DLN xxxxx-x) becomes the original" , or similar remarks. (3) Working a streamline case, Input a CII case note indicating which streamline method was used for processing. There may be some instances when multiple streamline processes apply (i.e., a case that has RIVO involvement but is also a MFJ Scheme case). Consider all actions required for all applicable methods. Refer to IRM 25.23.2.3.4, Required Case and History Notes, and IRM 21.5.1.5.1, CII General Guidelines, for additional requirements. (4) Both taxpayers on the valid return are affected by IDT, Ensure all actions are taken to resolve all issues on both the Primary and Secondary TIN, as applicable. Note: If the IDT return filing status is Married Filing Joint (MFJ) or Married Filing Separate (MFS), and the spousal name on CC ENMOD is not the spouse of the Primary taxpayer, correct the filing status and name line on the Primary TIN to remove the incorrect spousal information. Reminder: When the return is filed MFJ, the closing letter must be issued in the names of both taxpayers. (5) A fraudulent or compromised POA is involved, Refer to IRM 21.3.7.5.5.3, How to Report a Compromised or Potentially Compromised CAF Number. (6) The taxpayer's statement indicates someone else changed information using the Child Tax Credit Update Portal (CTCUP), EIP and/or Advanced Child Tax Credit (AdvCTC) may be impacted. Refer to IRM 25.23.4.21, American Rescue Plan Act (ARPA), and its subsections to determine impact and appropriate account actions. (7) The taxpayer's statement indicates someone else obtained healthcare coverage in their name and IDRS CC TXMOD reflects an amount in the PTC-EXP-AMT> field located in the posted return information section, Tax Related IDT: If a math error is set when a valid tax return is processed or an invalid tax return posted first, resolve the account as a tax related IDT issue. Non-Tax-Related IDT: If an invalid tax return is not present and valid tax return figures are not recomputed as a result of the "PTC-EXP-AMT>" , resolve the account as a non-tax-related IDT issue. (8) Inadvertent disclosure of sensitive information for the valid taxpayer, Avoid inadvertent disclosure of account information, even after verifying the taxpayer's identity in cases where they may be impacted by external business, preparer data breach, or tax preparation software misuse. The external business/preparer is responsible for advising the taxpayer of the incident. See IRM 25.23.4.8.2.4, Identity Theft (IDT) with External Business/Preparer Data Breach Involvement, and IRM 25.23.4.8.2.5, Identity Theft (IDT) with Tax Preparation Software Misuse, and applicable subsections for additional information. Refer to IRM 10.5.4, Incident Management Program, if unauthorized inadvertent disclosure has occurred. Example: The taxpayer called to inquire on the status of their case. While conducting account research, the assistor located a TC 971 AC 123 MISC "PREPARER CONTACT" posted on CC ENMOD. The assistor proceeded to advise the taxpayer they were a victim of identity theft due to being involved in a preparer data breach. The assistor should not have informed the taxpayer of the data breach incident as the tax preparer is responsible to do so, and the presence of a TC 971 AC 123 MISC "PREPARER CONTACT" on a taxpayer's entity does not confirm identity theft. (5) For refund-related issues, see the table below: If Then (1) An erroneous refund was issued to the SSN owner, Refer to IRM 21.4.5.6, Category D Erroneous Refund Procedures, for additional information. (2) An erroneous levy payment posted, Refer to IRM 25.23.10.7.2.6.5, Identity Theft and Disposition of Levy Proceeds, for additional guidance. (3) An FMS TOP Offset occurred, Refer to IRM 25.23.4.10.3.2, Identity Theft with TOP Offsets. (4) A refund is due, Allow the refund to be released systemically, unless an exception applies. See IRM 25.23.4.10.10, Identity Theft (IDT) - Manual Refunds, for situations that require a manual refund. When it is necessary to issue a manual refund, include Hold Code (HC) 4 in the adjustment. When the valid return meets DIF score criteria, issue the manual refund before sending the return to be DIF scored. Reminder: Adhere to the following adjustment considerations, as appropriate: HC 4 is to be used for any account condition requiring the credit to be held (e.g., a missing signature on the valid return). Include Priority Code (PC) 1 in the adjustment when sending the return for DIF scoring. See IRM 21.4.4.5, Preparation of Manual Refund Forms, for additional guidance on issuing a manual refund. After closing your CII case, open a monitor control base with the Category Code MISC to monitor for the posting of TC 840, as required. Additional general information can be found in IRM 21.5.2.4.19, Verifying Complete Adjustments. (5) There is a lost refund, Input TC 470 when the CN owner will not have a balance owed as a result of the actions taken to resolve the IDT issue. For streamline cases, see IRM 25.25.4.7, Reversing Identity Theft Lost Refunds, for specific guidance. Note: Because of the ramp down of Fresno Submission Processing, effective October 1, 2020, Kansas City now handles refund reversals for refunds that originated at Andover or Fresno. Do not input CC IDT48/IDT58 for Fresno. (6) For balance due issues, see the table below: If And Then (1) TP A (valid return) has a balance due, The return was filed and/or balance due was paid late, Refer to the following IRMs: IRM 20.1.2, Failure to File/Failure to Pay Penalties IRM 20.1.3.2.2, Manual Penalty Adjustments IRM 20.1.2.2.6.3, Wrong Return Posted First If any portion of the balance owed was paid late, the Failure to Pay penalty (FTP) can be computed systemically. If the return was filed late, manual computation of the Failure to File penalty (FTF) is required. Before assessing the FTF penalty, see the exception below. Exception: Do not assess the FTF penalty if the taxpayer filed a valid Form 4868, Application for Automatic Extension of Time to File U.S. Individual Income Tax Return, and the return was filed by the extended due date. For 2015 and earlier years, a TC 460 was deleted during the normal weekly update (which can take up to 3 cycles). If the TC 150 was already posted to the account, the valid taxpayer may be incorrectly assessed a FTF penalty if they filed a balance due return. If TC 460 is not showing on IDRS, the following may be indicators an extension was filed: There is a TC 670 payment with the April 15 date. Check Remittance Transaction Research (RTR) system to see if there is a Form 4868 that was filed with the payment. The valid taxpayer's return (generally the TC 976) is filed on or near October 15 (extension due date). The return information was transcribed on CC TRDBV. It may show the Form 4868 was filed. Reminder: When the valid return is MFJ, the necessary research to determine if an extension was filed must be completed for both taxpayers. (2) The overpayment from an invalid return was applied to a valid balance due, Reinstatement of an Installment Agreement (IA) is required, Prepare Form 4442, Inquiry Referral, and transmit the information via EEFax to the CSCO Operation within 24 hours. Refer to Service Center Addresses for Collection Operations to locate the appropriate EEFax. See paragraph (8) of IRM 5.19.1.6.4.13.1, DDIA - Form 433-D, Installment Agreement, and Form 9465, Installment Agreement Request, for additional information. When corresponding with the taxpayer, inform them the overpayment applied to their balance due was removed, and they will receive a separate notice explaining the changes and amount they owe. (3) The overpayment from an invalid return was applied to a valid balance due, Reinstatement of a Currently Not Collectable (CNC) is required, If the previous CNC determination is no more than 12 months old, and the total assessed balance due plus total liabilities related to the unassessed return is less than $25,000, the new account may be reported CNC without further investigation, see IRM 5.19.17.2.8, Cases Reported CNC Based on Prior CNC. Note: If the CNC module does not meet the criteria above, contact ITVA CSCO Headquarters Analyst for instructions on how to proceed with the case by emailing a completed Form 4442, Inquiry Referral. When corresponding with the taxpayer, inform them the overpayment applied to their balance due was removed, and they will receive a separate notice explaining the changes and amount they owe. (4) The overpayment from an invalid return was applied to a valid balance due, Reinstatement of an Offer In Compromise (OIC) is required, Prepare Form 4442, Inquiry Referral, requesting the reinstatement, and transmit the information to Offer-in-Compromise (OIC) Centralized Service Center Locations listed in SERP. When corresponding with the taxpayer, inform them the overpayment applied to their balance due was removed, and they will receive a separate notice explaining the changes and amount they owe. (5) The tax module reflects a balance owed in notice status, A CN ownership determination has not been made. Input TC 470 CC 90 to prevent balance due notices from generating while the taxpayer's case is open. (6) TC 470 CC 90 was input, The valid taxpayer will have a balance owed. Input TC 472 to reverse the TC 470 CC 90. (7) The tax module reflects a balance owed in collection status, Refer to IRM 25.23.4.12, Collection Activity - Form 14394/13794. (8) The valid taxpayer's return is not the TC 150 and requests a credit elect, The year the credit elect is to be applied to reflects a balance due that will be full paid once the credit elect is applied, Input TC 470 CC 94 to prevent balance due notices, offset to the module, and collection activity. (9) The valid taxpayer's return is not the TC 150 and requests a credit elect, The year the credit elect is to be applied to reflects a balance due that will not be fully resolved once the credit elect is applied, Input TC 470 CC 94 to prevent balance due notices, offsets to the module, and collection activity. Once the case has been resolved, input TC 472 CC 94 to resume normal balance due activity. (7) After completing the actions above, your case may need to be referred outside of your functional area. Refer to the chart below: If And Then (1) The TC 976/977 return bypassed Discriminant Index Function (DIF), Forward to Examination for DIF scoring. Also input a Priority Code 1 on the adjustment. Use local procedures to refer the case. Note: The return should only be sent if it meets any of the criteria in IRM 21.5.2.4.23.6, Discriminant Index Function (DIF) SCORE or CLASSIFICATION "Send Return(s) to Examination for Review" . DO NOT refer Form 1040EZ. Caution: All adjustment actions must be input prior to referring the case to Exam. (2) Form 8379, Injured Spouse Allocation, was attached to the case, You do not have the skill set to resolve the case, Open a new CII case with Category Code "DMFC" . Assign the case to the IDRS number located on theAccounts Management Site Specialization Temporary Holding Numbers listing located on SERP. For the required fields, input the Doc Type as "Injured Spouse Claim" , use Program and Function Code "ADJ-710-97140," "Priority 2" and reason "Form 8379 attached" . Reminder: If your site works both IDT case work and injured spouse case work, do not reassign the case. The case should be retained and worked within your site. (8) See the chart below to determine the final closing actions and letter requirements required for your case: Note: The CII capture function must be used when sending a letter as part of IDT case resolution. Refer to IRM 21.5.1.5.1, CII General Guidelines, for additional information. If And Then (1) Closing the case as IDT1/IDT8, Note: This includes IDT1 cases originally established as IDT3 cases in error (identified by PC 3) even when the Form 14039 is not in the CII images. TP identified (Form 14039 or similar statement submitted with return), Input the correct tax administration code TC 971 AC 501. See IRM 25.23.2.6.1, Closing Taxpayer Initiated Identity Theft Affecting Tax Administration - TC 971 AC 501, and IRM 25.23.2.6.1.1, Systemic Actions Taken After TC 971 AC 501 Placed on Account. Note: The indicator should be placed on all affected IDT tax years identified by the taxpayer. (2) Closing the case as IDT3/IDT8, IRS identified, Input the correct tax administration code TC 971 AC 506. See IRM 25.23.2.6.3, Closing IRS Determined Identity Theft Affecting Tax Administration - TC 971 AC 506. Note: The indicator should be placed on all affected IDT tax years not identified by the taxpayer. (3) Closing the case when TP B (invalid return not meeting nullity criteria) was assigned an IRSN, Adhere to the following: Do not input a TC 971 AC 501/506 on an IRSN. If you are resequencing an account, reestablish the SSN. Reinput the appropriate TC 971 AC 501/506 on the SSN. If TC 971 AC 501/506 are placed on an IRSN entity, the transactions must be reversed with a TC 972 AC 501/506 using "IRSERR" as part of the MISC field. See IRM 25.23.2.6.2, Manually Reversing TC 971 AC 501, and IRM 25.23.2.6.4, Manually Reversing TC 971 AC 506, for additional information. (4) Closing the case as IDT1/IDT3/IDT8, The following incident numbers are present: IR20150521512 IR20150521555 IR20150521556 IR20160127510 IR20160127513 IR20160614508 CR20170421067 LR20170421067 Determine if a tax administration code should be placed on the IDT victim's account. If a TC 971 AC 505 is present on the account, source "WI AM OTHER" must be used when inputting TC 971 AC 506 in addition to other required actions. Refer to IRM 25.23.2.10, Get Transcript Breach, IRM 25.23.2.11, Get an Electronic Filing PIN Incident, and IRM 25.23.2.13, Breach Numbers CR20170421067 and LR20170421067, for additional guidance. Note: The Get Transcript Online (GTO) application will be decommissioned in December 2024. If a TC 971 AC 527 is present, refer to IRM 25.23.2.8.6, Disabled Online Accounts TC 971 AC 527, IRM 25.23.2.8.6.1, Treatment of Disabled Accounts for IP PIN, and IRM 25.23.2.8.6.1.1, Resolving Tax-Related Accounts with TC 971 AC 527, for additional guidance. (5) Closing the case as IDT4, The following incident numbers are present: IR20150521512 IR20150521555 IR20150521556 IR20160127510 IR20160127513 IR20160614508 CR20170421067 LR20170421067 Determine if a tax administration code should be placed on the IDT victim's account. If a TC 971 AC 505 is present on the account, source "WI AM OTHER" must be used when inputting TC 971 AC 506 in addition to other required actions. Refer to IRM 25.23.2.10, Get Transcript Breach, IRM 25.23.2.11, Get an Electronic Filing PIN Incident, and IRM 25.23.2.13, Breach Numbers CR20170421067 and LR20170421067, for additional guidance. Note: The Get Transcript Online (GTO) application will be decommissioned in December 2024. If a TC 971 AC 527 is present, refer to IRM 25.23.2.8.6, Disabled Online Accounts TC 971 AC 527, IRM 25.23.2.8.6.1, Treatment of Disabled Accounts for IP PIN, and IRM 25.23.2.8.6.1.2, Resolving Non-Tax-Related Accounts with TC 971 AC 527, for additional guidance. (6) If Form 14039 was received, The account reflects at least one rejected invalid return and no invalid returns have been accepted, See IRM 25.23.4.10, Resolving Identity Theft (IDT) Cases. (7) A determination of identity theft is made (tax related or non-tax-related), The taxpayer has indicated they did not receive unemployment benefits, A closing letter must be sent. See IRM 25.23.3.2.3, Self-Identified - Non-Tax-Related Identity Theft - IDT4, for additional information. When at least one of the issues is tax related, send Letter 4674C instead of Letter 4402C. Include an open paragraph for the required narrative. (8) A No IDT determination was made, Input TC 972 AC 522 with MISC "NOIDT" when the case is taxpayer identified. Refer to IRM 25.23.2.6.6, Reversing Unsupported Allegations of Identity Theft, for specific information. Input TC 972 AC 522 with MISC "IRSERR" when the case is IRS identified. Refer to IRM 25.23.2.4.5, IRS Initiated Suspicion of Identity Theft - TC 971 AC 522 IRSID, for specific information. (9) All actions have been completed and closing codes input, Send the TP an IDT closing letter. Refer to Exhibit 25.23.4-10, Identity Theft (IDT) Closing Letter Decision Chart. (10) Closing the case as previous action, Review CII case notes and/or IDRS to determine if an interim letter was issued to the taxpayer before the case was moved to IDT inventory. Then follow procedures in IRM 25.23.4.10.6, Identity Theft (IDT) - Previous Action. (11) Directed to reverse an existing IDT indicator, The secondary date is for a tax year that is more than 7 years old, Prepare and email Form 4442 using the subject line: Reverse IDT Indicator (or similar) to ITVA HQ Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Per IRM 25.23.4.3.1.1, Monitoring Case Controls, do not suspend or keep your CII case open only to monitor the posting of the reversal. Note: Follow procedures in IRM 25.23.2.3.8.1, Command Code REQ77 Secondary Date and Old Case Year Issue, if placing a new IDT indicator for a year earlier than the oldest allowable year.

# Establishing or Updating Entities for Dependents

Exhibit 25.23.4-22 Establishing or Updating Entities for Dependents (1) Research IDRS Command Code (CC) DDBKD to identify the dependent's custodial parent. If custodial parent information is not available, determine if the name and TIN for at least one parent is present. Note: When the dependent is assigned an Individual Taxpayer Identification Number (ITIN), ITIN RTS must be researched when CC DDBKD does not reflect parent information. Note: If parent information is not available, refer to paragraph (2) Taxpayer Identified Table Scenario (9) or IRS Identified Table Scenario (7) below. (2) Research the filing history for each parent identified. Refer to the tables below for necessary research and account actions: Note: In the table below an address update refers to changes that have already been input and returns or requests that include an address update that have not yet been worked. Taxpayer Identified If And Then (1) The case is taxpayer identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) The custodial parent (or verified parent when custody is not specified) filed the claim and has filed a tax return (or amended their original return) for the current processing year claiming the dependent in question, and The address on the Form 14039, police report, or correspondence matches the address on the return, Establish or update the dependent's entity with the address provided in the case documents. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (2) The case is taxpayer identified and information is available for the: Custodial Parent OR Parent(s) (when custody is not specified) The case is being worked on October 31 or earlier, and a tax return for the current processing year has not been received, and The custodial parent (or verified parent when custody is not specified) has filed a tax return (or amended their original return) for the immediately preceding tax year claiming the dependent in question, and The address on the Form 14039, police report, or correspondence matches the address on the return, Exception: When the reporting parent has had an address update since submitting the claim, the address on the Form 14039 may not match the address on the most recent return. If the address has been updated since the claim was received, compare the address on the claim to the reporting parent's filing history to determine if there is a historical match. If there is a historical match, follow procedures in the Then column. If there is not a historical match, this scenario is not met. Establish or update the dependent's entity with the address provided in the case documents. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (3) The case is taxpayer identified and information is available for the: Custodial Parent OR Parent(s) (when custody is not specified) Table Scenarios (1) and (2) do not apply, and The custodial or verified parent's (when custody is not specified) most recent address matches the address on the Form 14039, police report, or correspondence, unless there has been an address update meeting the exception in table scenario (2) above, and An AMS history item indicates the parent has called and passed disclosure within the last year (from date the case is being worked), Exception: An AMS history item indicating disclosure was passed is not required if the most recent address can be matched with other account information available through research (i.e., income document on IRPTR, etc.). Establish or update the dependent's entity with the address provided in the case documents. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (4) The case is taxpayer identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) The dependent was claimed by both parents, and There is one reporting parent who meets requirements in Table Scenario (1), (2), or (3) above, Establish or update the dependent's entity with the address provided in the case documents. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (5) The case is taxpayer identified and information is available for the: Custodial parent The dependent was claimed by both parents, and Both parents reported the IDT and meet requirements in Table Scenario (1), (2), or (3) above, Establish or update the dependent's entity with the address provided in the case documents submitted by the custodial parent. Exception: When the other parent provided documentation showing they are now the current custodial parent, see Table Scenario (6) below. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (6) The case is taxpayer identified and information is available for the: Parent(s) (when custody is not specified) The dependent was claimed by both parents, and Both parents reported the IDT and meet requirements in Table Scenario (1), (2), or (3) above, Establish or update the dependent's entity with the address provided in the case documents of the case with the earliest IRS received date. Exception: When the other parent provided documentation showing they are now the current custodial parent, use the address for that case even if it does not have the earliest IRS received date. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (7) The case is taxpayer identified and information is available for the: Custodial parent The dependent was claimed by both parents, and Neither parent meets requirements in Table Scenarios (1), (2), or (3) above, Establish or update the dependent's entity with the address provided in the case documents submitted by the custodial parent if the address on the Form 14039, police report, or correspondence matches the parent's most recent address. Exception: When the other parent provided documentation showing they are now the current custodial parent, see Table Scenario (8) below. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (8) The case is taxpayer identified and information is available for the: Parent(s) (when custody is not specified) The dependent was claimed by both parents, and Neither parent meets requirements in Table Scenarios (1), (2), or (3) above, Establish or update the dependent's entity with the address provided in the case documents of the case with the earliest IRS received date if the address on the Form 14039, police report, or correspondence matches the parent's most recent address. Exception: When the other parent provided documentation showing they are now the current custodial parent, use the address for that case even if it does not have the earliest IRS received date. Exception: When the reporting parent has had an address update since submitting the claim, use the most current address of the reporting parent when establishing or updating the entity. (9) The case is taxpayer identified Parent information is not available, Establish or update the dependent's entity with an IRS Service Center address. (10) The case is taxpayer identified The dependent is now 18 and has filed a tax return as the primary or secondary taxpayer, and Proof of legal guardianship was not provided by the reporting parent, Do not update the dependent's address. IRS Identified If And Then (1) The case is IRS identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) One parent has filed a tax return (or amended their original return) for the current processing year claiming the dependent in question, Establish or update the dependent's entity with the address on the parent's tax return. Exception: When the parent has had an address update since filing or amending their return, use the most current address of the parent when establishing or updating the entity. (2) The case is IRS identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) The case is being worked on October 31 or earlier, and a tax return for the current processing year has not been received, and One parent has filed a tax return (or amended their original return) for the immediately preceding tax year claiming the dependent in question, Establish or update the dependent's entity with the address on the parent's tax return. Exception: When the parent has had an address update since filing or amending their return, use the most current address of the parent when establishing or updating the entity. (3) The case is IRS identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) Table Scenarios (1) and (2) do not apply, and An AMS history item indicates one parent has called and passed disclosure within the last year (from date the case is being worked), Exception: An AMS history item indicating disclosure was passed is not required if the most recent address can be matched with other account information available through research (i.e., income document on IRPTR, etc.). Establish or update the dependent's entity with the address on the parent's entity. Exception: When the parent has had an address update since filing or amending their return, use the most current address of the parent when establishing or updating the entity. (4) The case is IRS identified and information is available for the: Custodial parent Both parents meet criteria in Table Scenarios (1), (2), or (3), Establish or update the dependent's entity with the address of the custodial parent. Exception: If there is documentation showing the other parent is now the custodial parent, see Table Scenario (5) below. Exception: When the parent has had an address update since filing or amending their return, use the most current address of the parent when establishing or updating the entity. (5) The case is IRS identified and information is available for the: Parent(s) (when custody is not specified) Both parents meet criteria in Table Scenarios (1), (2), or (3), When custody cannot be determined, establish or update the dependent's entity using the current address of parent who filed the earliest tax return received for the current processing year. If the case is being worked on October 31 or earlier, and a tax return for the current processing year has not been received, use the current address of the parent who filed the earliest tax return received for the immediately preceding tax year. Exception: When the parent has had an address update since filing or amending their return, use the most current address of the parent when establishing or updating the entity. (6) The case is IRS identified and information is available for the: Custodial parent OR Parent(s) (when custody is not specified) Neither parent meets criteria in Table Scenarios (1), (2), or (3), Establish or update the dependent's entity with an IRS Service Center address. (7) The case is IRS identified Parent information is not available, Establish or update the dependent's entity with an IRS Service Center address. (3) For cases that do not meet any scenario in the tables above, prepare and email Form 4442 using the subject line: Dependent - Determining Address (or similar) to ITVA HQ. Document all research completed in a CII case note and/or on Form 4442. Attach Form 4442 to your CII case. Suspend the case awaiting a response from ITVA HQ. Upon receipt, the account will be researched. A response on how to address the account will be received within 7 business days.

# Complex Case Scenarios

Exhibit 25.23.4-23 Complex Case Scenarios (1) Refer to the scenarios below for examples of complex case scenarios requiring multiple treatment streams to fully resolve the account. Example 1: MXEN with Income Related IDT Scenario: Mary Greenwood files Form 14039 reporting she is a victim of identity theft. Mary states someone is working under her social security number at a company called A-Z Corp and that they are unable to file their 2023 tax return electronically. Mary includes a paper return which posted as the TC 976. Research: The CN is XXX-XX-ABCD. TC 150 return was timely filed on 4/18/2024 with the name Martin Greer and an address in Dallas, TX. TC 976 return was received on 10/5/2024 with the name Mary Greenwood and an address in Dallas, TX. IDRS filing history shows this is the first year Martin Greer has used the CN. CC INOLES is researched, and it is determined the CN belongs to Mary Greenwood. CC NAMES is researched, and it is determined Martin Greer's correct SSN is XXX-XX-ABDC. CC IRPTR is researched, and 1099-NEC income from A-Z Corp is found. The name associated with the income is Terry Howard. CC TXMOD is researched, and there are no additional assessments on the module. Determination: MXEN and income related IDT not affecting tax administration. Resolution: The existing CII case will be worked as income related IDT. A separate case will be created to address the MXEN. Example 2: No IDT and MXEN Scenario: Miles Brown files Form 14039 stating he believes someone may be using his Social Security Number. Miles attempted to use the non-filer tool for 2019 but learned someone else already filed a tax return in their name. Research: The CN is XXX-XX-TUVW. TC 150 return was timely filed on 7/15/2020 with the name Mike Brown and an address in San Francisco, CA. IDRS filing history shows Mike Brown has filed tax returns under the CN for tax years 2015-2019. Mike Brown's filing history is consistent with address, dependents, type of income, direct deposit information, and tax preparer. No one else has filed a tax return under the CN. CC INOLES is researched, and it is determined the CN belongs to Miles Brown. CC NAMES is researched, and it is determined Mike Brown's correct SSN is XXX-XX-TVVW. Determination: MXEN. Miles Brown is not a victim of identity theft. Mike Brown has been using the CN in error. This is likely due to a typographical error when the tax preparer filed their 2015 return. Resolution: The existing CII case will be worked as No IDT. A separate case will be created to address the MXEN and merge Mike Brown's information to the correct SSN. Example 3: IRSN and MXEN Scenario: Austin Rivers, Jr. files Form 14039 stating he could not file his 2023 tax return electronically, because someone already filed a tax return in their name. This is the first time filing a tax return. Research: The CN is XXX-XX-ABAB. TC 150 return was timely filed on 4/18/2024 with the name Austin Rivers, verifiable wages of $32,461, and an address in Miami, FL. TC 976 return was filed on 5/16/2024 with the name Austin Rivers, self-employment income of $86,427, and an address in Seattle, WA. TC 976 return was filed on 5/25/2024 with the name Austin Rivers, Jr., verifiable wages of $5,683, and an address in Seattle, WA. Researching the account shows the address is the same for both TC 976 returns. IDRS filing history shows this is the first tax year with tax returns. CC INOLES is researched, and it is determined the CN belongs to Austin Rivers, Jr. who is now 20 years old. CC DDBKD is researched, and it is found Austin Rivers, Jr. has been claimed as a dependent by Austin Rivers, Sr. for the two previous years. Research of the TIN identified for Austin Rivers, Sr. shows this is the only tax year without a tax return. The TC 976 return reporting self-employment income is consistent with Austin's filing history. Determination: Invalid TC 150. MXEN for first TC 976. Valid taxpayer's return posted as second TC 976. Resolution: The existing CII case will be worked as IDT moving the invalid TC 150 return to an IRSN and adjusting the account to the valid TC 976 return. A separate case will be created to resolve the MXEN by moving the first TC 976 return to the father's correct SSN. Example 4: IRSN and Dependent Related IDT Scenario: Bethany Marsh files Form 14039 stating she could not file her 2024 tax return electronically, because someone already filed a tax return in her name. Bethany includes a paper return which posts as a TC 976. Research: The CN is XXX-XX-JKLM. TC 150 return was timely filed on 4/18/2025 and includes verifiable wages and withholding. The return also includes 3 dependents, dependent-related credits, and direct deposit information. A math error was set during original processing. TC 976 return was timely filed and includes self-employment income, the same 3 dependents, dependent-related credits, and direct deposit information. Researching the account shows the TC 976 return is consistent with the taxpayer's filing history, and the TC 150 return is not. Determination: Invalid TC 150. Valid TC 976. Dependent related IDT for all dependents claimed on the invalid return. Resolution: The existing CII case will be worked as IDT moving the invalid TC 150 return to an IRSN and adjusting the account to the valid TC 976 return figures. A separate case will be created for each dependent to resolve the dependent related IDT. Example 5: Invalid Return and Income Related IDT Scenario: Violet Summers files Form 14039 to report a decrease in Social Security benefits due to wages. The statement indicates Social Security benefits are Violet's only source of income and someone else is working under the Social Security Number (SSN). Form 14039 lists 2020 as the last year Violet filed a tax return. Research: The CN is XXX-XX-QRST. Researching the module results in identification of a tax return filed for tax year 2023 which meets MFJ scheme criteria. There are no additional assessments. Research of IRPTR information results in the recognition of wages earned in a state Violet has no history of residing in for tax year 2023. The income located is not included on the tax return filed for this tax year. Research of entity information and IDRS CC NAMES does not result in discovery of another valid TIN or a potential scrambled SSN issue. Determination: One invalid return due to MFJ scheme and income related identity theft. Resolution: The invalid return will be backed out following streamline procedures. The wages identified as not belonging to Violet will be addressed with completion of Forms 9409. Only TC 971 AC 501 will be input upon closing. TC 971 AC 504 will not be input. Example 6: Employment Related IDT vs Income Related IDT Scenario: Daniel Fields files Form 14039 in response to receiving CP 01E. Form 14039 lists CP 01E in the letter/notice field, the box indicating fraudulent use for employment purposes is checked, there are no comments in the field for explanation, and tax year 2024 is identified as impacted. Research: The entity reflects TC 971 AC 525 for tax year 2024. IDRS CC IRPTR shows income reported from a state the taxpayer does not have a history of living in. Complete Case Analysis (CCA) shows no invalid returns filed. There is no impact to tax administration. Determination: The taxpayer is a victim of income related IDT previously IRS identified as employment related IDT. Resolution: The case will be resolved as a response to CP 01E. See IRM 25.23.3.2.3.1.1, Self-Identified – Non-Tax-Related Identity Theft – IDT4 Determination and Closing Actions.

# IDTVA Statute Clearing

Exhibit 25.23.4-24 IDTVA Statute Clearing (1) Due to the nature of identity theft cases, statutes must be prioritized throughout the year. To prevent barred assessments, IDTVA will ensure inventory is statute cleared on a quarterly basis. (2) IDTVA employees are responsible for statute clearing and addressing statute imminent cases in their assigned inventory. Refer to IRM 25.23.4.9, Statute Processing Considerations, for additional information. (3) IDTVA P&A is responsible for: Utilizing the quarterly statutes listing provided by ITVA to identify statute year cases in the unassigned inventory that must be statute cleared. Monitoring the holding number for cases previously statute cleared to identify cases that are statute imminent. Note: A case is statute imminent if the ASED expires in 180 days or less. (4) Update statute year cases to the appropriate priority code. See IRM 25.23.4.3.5, Priority Codes for IDTVA CII Cases, for additional information. (5) Statute year cases from the unassigned inventory will be statute cleared using the following process: Step Action 1 Move statute year cases from the unassigned inventory to the designated holding number. 2 IDTVA P&A: Distribute statute year cases to designated individuals for statute clearing purposes. 3 IDTVA Statute Clearing Employee: Determine if there is an assessment that is imminent (must be made within 180 days). Yes - Go to Step 4. No - Go to Step 5. 4 IDTVA Statute Clearing Employee: Retain the case to work as a priority. Update the priority code, if necessary. 5 IDTVA Statute Clearing Employee: Reassign the case to the designated holding number for statute cleared cases. Go to Step 6. 6 Update the control base activity with the valid ASED in a MMDDYYYY format. (6) IDTVA P&A: Distribute statute imminent cases in the holding number for cases previously statute cleared to be worked as a priority.

# Closing Letter Paragraph Selections

Exhibit 25.23.4-25 Closing Letter Paragraph Selections (1) To ensure the taxpayer receives a quality response by providing accurate and professional communication, you must review all paragraphs included prior to issuing a closing letter. See IRM 25.23.4.18.1, General IDTVA Letter Procedures, for additional information. (2) There may be instances when selectable paragraphs contain language that does not apply. When this occurs, select an open paragraph, to provide only the language that is appropriate. When necessary, a floating paragraph (*) may be used to ensure all information is included and communicated clearly. (3) Special paragraphs are those that are required for specific account circumstances. They are identified as special paragraphs and are included in the applicable IRM, where appropriate. You may need to include one or more special paragraphs in addition to the paragraphs selected for your closing letter. (4) Refer to the paragraphs below for recommended use of open and special paragraphs in place of selectable paragraphs which may include inaccurate information for certain case types when issuing a closing letter. You may use the special paragraphs listed in the table below for various IDT case types, as appropriate, depending on the facts and circumstances of the case. Caution: DO NOT select paragraph "u" when issuing Letter 4674C for ALL case types. Paragraph "u" contains incorrect information advising the taxpayer they cannot opt out of the IP PIN program. In lieu of paragraph "u" , include the following suggested wording (or similar). You're eligible to get a unique 6-digit Identity Protection Personal Identification Number (IP PIN), which will verify the tax return we receive is really from you. Visit irs.gov/ippin for more information. Example 1: Dependent Identity Theft (IDT): When providing a taxpayer under the age of 18 with supplemental information regarding IP PINs, do not select any paragraphs advising they must verify their identity. For example, paragraphs 8, s, or u in closing Letter 4674C. Case Scenario Special Paragraph(s) Taxpayer is a victim of IDT and under age 18 "To help prevent future identity theft issues, we'll issue you an Identity Protection Personal Identification Number (IP PIN). An IP PIN is a 6-digit number you may use to confirm your identity on any tax returns filed during the calendar year." AND "A missing or incorrect IP PIN may prevent the electronic filing of a tax return, and a paper return filed with a missing or incorrect IP PIN will be subject to additional review. You may visit irs.gov/ippin for more information." AND "A new IP PIN is generated each year. We'll mail the IP PIN to you in December or January. Therefore, be sure to file Form 8822, Change of Address, if you change your mailing address. You can find more information at irs.gov/ippinfaqs." . Reminder: At the time the letter is being issued, for taxpayers under the age of 18, do not include the paragraph that directs them to request an IP PIN using Online Services. Taxpayers can be directed to irs.gov/ippin and/or irs.gov/ippinfaqs to obtain general information. Example 2: No Identity Theft (NOIDT): When providing a taxpayer who is not a victim of identity theft with supplemental information regarding IP PINs, do not select paragraphs "I" or "J" . Selecting these paragraphs will automatically include paragraph "u" when issuing closing Letter 4674C. See IRM 25.23.4.10.8, No Identity Theft (NOIDT) Determinations, for additional information. Reminder: You must include paragraphs "a" , "c" , "e" , and "w" when sending Letter 4674C for NOIDT cases. Case Scenario Special Paragraph(s) Taxpayer is not a victim of IDT "We reviewed your correspondence dated MM/DD/YYYY. We found no indication that identity theft affected the tax periods above." Use the date of the taxpayer's correspondence in place of MM/DD/YYYY. OR "We reviewed your identity theft claim (identity theft affidavit or police report) dated [fill in] and found no indication identity theft affected the tax periods above. You may be eligible for an Identity Protection Personal ID Number (IP PIN), for more information about an IP PIN, please visit irs.gov/ippin." Taxpayer is not a victim of IDT and under age 18 Note: This paragraph is intended for use with the following IDT indicators only: TC 971 AC 504, TC 972 AC 5XX (e.g., NOIDT, NORPLY, etc.). "You may be eligible for an Identity Protection Personal Identification Number (IP PIN). If you are under 18 and want to apply for an IP PIN, your parent or legal guardian may complete a Form 15227, Identity Protection Personal Identification Number Paper Application, or visit your local Taxpayer Assistance Center. For more information, please visit irs.gov/ippin." Reminder: At the time the letter is being issued, for taxpayers under the age of 18, do not include the paragraph that directs them to request an IP PIN using Online Services. Taxpayers can be directed to irs.gov/ippin and/or irs.gov/ippinfaqs to obtain general information. Example 3: Income Related Identity Theft (IDT): When providing a taxpayer who is not a victim of tax related IDT with supplemental information regarding IP PINs, do not select paragraph "u" when issuing closing Letter 4674C. Paragraph "u" contains incorrect information advising the taxpayer they cannot opt out of the IP PIN program. The special paragraph below may be used for income related case types. In lieu of paragraph u refer to the Caution above for suggested wording. Reminder: At the time the letter is being issued, for taxpayers under the age of 18, do not include the paragraph that directs them to request an IP PIN using Online Services. Taxpayers can be directed to irs.gov/ippin and/or irs.gov/ippinfaqs to obtain general information. Example 4: IP PINs: When providing the taxpayer with supplemental information regarding IP PINs, refer to the following information and special paragraphs that may need to be included in addition to the paragraphs selected for your closing Letter 4674C . Note: Existing selectable paragraphs in Letter 4674Cor the applicable special paragraphs in the table below may be used. Note: Use only the special paragraphs under the case scenario "Already Enrolled" if the taxpayer is already enrolled in the IP PIN program. See IRM 25.23.2.9.2, Identifying If a Taxpayer has an IP PIN Requirement, to determine if a taxpayer's account reflects an existing IP PIN indicator. Reminder: IP PIN issues must be addressed in ALL closing letters to the taxpayer(s). Case Scenario Special Paragraph(s) Claims processed up to and including cycle 46 "If you want to obtain an IP PIN for immediate protection, visit our website at www.irs.gov/your-account. A new IP PIN generates each year in mid-January." AND "If you choose to create an account to opt in to the IP PIN program, you will be able to access your IP PIN online in the future. You can retrieve it by logging into your account at irs.gov/your-account. You will still receive an IP PIN notice in the mail for future tax years." Claims processed after cycle 46 Because we processed your claim late in the year, we are unable to mail an IP PIN in December or January for this upcoming filing season. File your return as normal for this tax season. We will mail you an IP PIN next December or January. If your address changes before December, you will need to complete Form 8822, Change of Address. Visit www.irs.gov. AND "If you want an IP PIN to use for the upcoming tax year, you may opt in. A new IP PIN generates each year in mid-January. If you choose to opt in to the IP PIN program, you will be able to access your IP PIN online in the future. You can retrieve it by logging into your account at irs.gov/your-account. You will still receive an IP PIN notice in the mail for future tax years." Already Enrolled "Our records indicate you are currently enrolled in the IP PIN program, and you will continue to be assigned an IP PIN to use when filing tax returns in the future. A new IP PIN is generated each year. We'll mail the IP PIN to you in December or January." AND "If you change your mailing address, file Form 8822, Change of Address. If you choose to create an account to obtain an IP PIN, you will be able to access your IP PIN online in the future. You can retrieve it by logging into your account at irs.gov/your-account. You will still receive an IP PIN notice in the mail." Already Enrolled - Taxpayer under age 18 "Our records indicate you are currently enrolled in the IP PIN program, and you will continue to be assigned an IP PIN to use when filing tax returns in the future. A new IP PIN is generated each year. We'll mail the IP PIN to you in December or January." AND "Be sure to file Form 8822, Change of Address, if you change your mailing address. You can find more information at irs.gov/ippinfaqs." Reminder: At the time the letter is being issued, for taxpayers under the age of 18, do not include the paragraph that directs them to request an IP PIN using Online Services. Taxpayers can be directed to irs.gov/ippin and/or irs.gov/ippinfaqs to obtain general information.