- 21.5.2 Adjustment Guidelines
- 21.5.2.1 Program Scope and Objectives
- 21.5.2.1.1 Background
- 21.5.2.1.2 Authority
- 21.5.2.1.3 Roles and Responsibilities
- 21.5.2.1.4 Program Management and Review
- 21.5.2.1.5 Program Controls
- 21.5.2.1.6 Terms & Acronyms
- 21.5.2.1.7 Related Resources
- 21.5.2.2 What Are Adjustment Guidelines?
- 21.5.2.3 Adjustment Guidelines – Research
- 21.5.2.4 Adjustment Guidelines – Procedures
- 21.5.2.4.1 Statutory Exceptions and Administrative Waivers
- 21.5.2.4.1.1 Designation of Federal Tax Deposits (FTD)
- 21.5.2.4.1.2 Service Errors (Effect on Penalty and Interest)
- 21.5.2.4.1.3 Reasonable Cause
- 21.5.2.4.2 Adjustments with Oral Statement
- 21.5.2.4.2.1 Case Files/Actions On-line with Oral Statement
- 21.5.2.4.3 Adjustments Requiring an Amended Return or Taxpayer Documentation
- 21.5.2.4.4 Document Locator Number (DLN)
- 21.5.2.4.5 Source Documents
- 21.5.2.4.6 Remarks Field
- 21.5.2.4.7 Remarks On Type of Adjustment
- 21.5.2.4.8 Notice Suppression
- 21.5.2.4.8.1 Notice Suppression Indicator
- 21.5.2.4.8.2 Suppressing Balance Due Notices
- 21.5.2.4.8.3 Clearance Tolerances
- 21.5.2.4.9 Penalty Overview
- 21.5.2.4.9.1 TC 971 Action Code 262
- 21.5.2.4.9.2 Oral Statement and Penalty Relief Request
- 21.5.2.4.9.3 Partnership Penalty
- 21.5.2.4.10 Interest Explanation
- 21.5.2.4.10.1 Ministerial/Managerial Interest Abatement
- 21.5.2.4.11 Assessments or Refunds Over ≡ ≡ ≡ ≡ ≡ ≡ ≡
- 21.5.2.4.12 Form 8485, Assessment Adjustment Case Record: Purpose and Preparation
- 21.5.2.4.13 Reinstating Retention Register Accounts
- 21.5.2.4.14 Penalty Computation for Retention Register Accounts
- 21.5.2.4.15 Rules for Hold Codes (HC)
- 21.5.2.4.16 Priority Codes (PC)
- 21.5.2.4.17 Posting Delay Code (PDC)
- 21.5.2.4.18 Credit Reference Numbers (CRN), Abstract Codes, and Item Reference Numbers (IRN)
- 21.5.2.4.18.1 CRNs and IRNs For Forms and MFTs
- 21.5.2.4.19 Verifying Complete Adjustments
- 21.5.2.4.20 CP 21/CP 22 Source Codes (SC) and Reason Codes (RC)
- 21.5.2.4.21 Individual Master File (IMF) Actions for Command Code ADJ54
- 21.5.2.4.22 Blocking Series (BS)
- 21.5.2.4.22.1 IMF Blocking Series 99 Special Consideration
- 21.5.2.4.23 Reprocessing Returns/Documents
- 21.5.2.4.23.1 Reprocessing Electronic Returns
- 21.5.2.4.23.2 Amended or Subsequent Return
- 21.5.2.4.23.3 DLNs Used for Reprocessing Documents
- 21.5.2.4.23.4 Statute Imminent Documents
- 21.5.2.4.23.5 Accounts with Audit Activity
- 21.5.2.4.23.6 Discriminant Function (DIF) SCORE or CLASSIFICATION "Send Return(s) to Examination for Review (Superseding Returns)"
- 21.5.2.4.23.7 Coding and Editing Procedures
- 21.5.2.4.23.8 IDRS Account Actions
- 21.5.2.4.23.9 Moving Assessments
- 21.5.2.4.23.10 Moving Refunds
- 21.5.2.4.23.11 Reprocessing "Dummy" Returns
- 21.5.2.4.24 Shipment of Source Documents
- 21.5.2.4.25 Request for Alternative Language Products by Taxpayers With Limited English Proficiency (LEP)
- 21.5.2.4.26 Form 9000, Alternative Media Preference
- 21.5.2.4.1 Statutory Exceptions and Administrative Waivers
- Exhibit 21.5.2-1 Preparing Form 3893, Re-Entry Document Control
- Exhibit 21.5.2-2 Preparing Form 13596, Reprocessing Returns
- 21.5.2.1 Program Scope and Objectives
Part 21. Customer Account Services
Chapter 5. Account Resolution
Section 2. Adjustment Guidelines
21.5.2 Adjustment Guidelines
Manual Transmittal
September 14, 2026
Purpose
(1) This transmits revised IRM 21.5.2, Account Resolution, Adjustments Guidelines.
Material Changes
(1) IRM 21.5.2.1.2 Added paragraph with links to Policy Statements for additional information on the cited policies (IPU 25U3701 issued 12-08-2025).
(2) IRM 21.5.2.1.3 Added paragraph with links to Accounts Management to support cited roles and responsibilities (IPU 25U3701 issued 12-08-2025).
(3) IRM 21.5.2.1.4 Corrected (2)(c) to PPI reviews. Added general statement what the reviews should include. Moved TBOR from Related Resources (IPU 25U3701 issued 12-08-2025).
(4) IRM 21.5.2.1.5 Added subsection Program Controls 21.5.2.1.5 per IMD guidance during clearance (IPU 25U3701 issued 12-08-2025).
(5) IRM 21.5.2.1.7 Moved TBOR from Related Resources (IPU 25U3701 issued 12-08-2025).
(6) IRM 21.5.2.3 Added guidance to paragraph 6b to avoid conflicting IRMs. Added reminder about linked cases (IPU 25U3701 issued 12-08-2025).
(7) IRM 21.5.2.3 Clarification of the procedures for unsettled accounts. Simplified language in paragraph 6 (IPU 26U0619 issued 06-10-2026).
(8) IRM 21.5.2.3.1 Added a reminder about notating the account prior to reassigning to IDTVA (IPU 25U3701 issued 12-08-2025).
(9) IRM 21.5.2.4.3.1 Added guidance for Form 2275 (IPU 25U3701 issued 12-08-2025).
(10) IRM 21.5.2.3.1 Added clarification for TPP indicators (IPU 26U0208 issued 02-06-2026) and (IPU 26U0390 issued 04-02-2026).
(11) IRM 21.5.2.3.1 Added note to paragraph 3 regarding IDT7 and IDTX procedures due to ICM (IPU 26U0619 issued 06-10-2026).
(12) IRM 21.5.2.3.1 Updated subsection throughout to improve readability by applying plain language standards.
(13) IRM 21.5.2.4.9.1 Added definition for FTP acronym (IPU 25U3701 issued 12-08-2025).
(14) IRM 21.5.2.4.10.1 Added missing linked IRM title. Added Form 843 guidance (IPU 25U3701 issued 12-08-2025).
(15) IRM 21.5.2.4.10.1 Updated guidance in the caution note (IPU 26U0390 issued 04-02-2026).
(16) IRM 21.5.2.4.16 Added Section number reference to Document 6209 for ease of use (IPU 25U3701 issued 12-08-2025).
(17) IRM 21.5.2.4.18 Added Section number reference to Document 6209 for ease of use (IPU 25U3701 issued 12-08-2025).
(18) IRM 21.5.2.4.18.1 Added missing linked IRM title (IPU 25U3701 issued 12-08-2025).
(19) IRM 21.5.2.4.19 Added guidance for TC 606 based off of IRM 21.5.8.4, IDRS Guidelines for Credit Transfers (IPU 26U0619 issued 06-10-2026).
(20) IRM 21.5.2.4.20 Added Section number reference to Document 6209 for ease of use (IPU 25U3701 issued 12-08-2025).
(21) IRM 21.5.2.4.22 Added Section number reference to Document 6209 for ease of use (IPU 25U3701 issued 12-08-2025).
(22) IRM 21.5.2.4.23 Added guidance on account conditions when reprocessing is involved. Updated verbiage to include statute imminent cases for clarity (IPU 25U3701 issued 12-08-2025)
(23) IRM 21.5.2.4.23 Updated the IRM back to the previous language for Form 4442. (IPU 26U0208 issued 02-06-2026).
(24) IRM 21.5.2.4.23 Updated the IRM back to the previous language for Form 4442. Split paragraphs for clarity (IPU 26U0390 issued 04-02-2026)
(25) IRM 21.5.2.4.23 Removed exception due to the update in IRM 25.6.1.8.4, Processing Original Delinquent Returns (IPU 26U0619 issued 06-10-2026).
(26) IRM 21.5.2.4.23.6 Removed contradictory LB&I superseding information per collaboration with Exam (IPU 26U0208 issued 02-06-2026) and (IPU 26U0390 issued 04-02-2026).
(27) IRM 21.5.2.4.23.6 Added a exception after a discussion with Exam. Updated verbiage for clarity. Added an example for clarity. Rearranged paragraphs for clarity (IPU 26U0619 issued 06-10-2026).
(28) IRM 21.5.2.4.23.7 Added procedures for IMF processing. Added a reminder for transferring figures from a Form 1040-X to a Form 1040 for reprocessing (IPU 25U3701 issued 12-08-2025).
(29) IRM 21.5.2.4.23.7 Switched around paragraphs for clarity (IPU 26U0208 issued 02-06-2026) and (IPU 26U0390 issued 04-02-2026).
(30) IRM 21.5.2.4.23.7 Added BMF guidance for annotating cases. Added Forms per M&P Analyst DSB reach-in (IPU 26U0619 issued 06-10-2026).
(31) IRM 21.5.2.4.23.8 Revised where to find TDI codes in Document 6209 for consistency (IPU 25U3701 issued 12-08-2025).
(32) IRM 21.5.2.4.23.9 Added IRM link to the reminder for use of TC 971 codes (IPU 25U3701 issued 12-08-2025).
(33) IRM 21.5.2.4.23.10 Added link to IAT Credit Transfer Tool job aid. Added reminder note regarding the input of TC 848 /TC 849 (IPU 25U3701 issued 12-08-2025).
(34) IRM 21.5.2.4.23.11 Reiterated Command Codes needed to attach to a dummy return per Feedback 35101 (IPU 25U3701 issued 12-08-2025).
(35) IRM 21.5.2.4.24 Revised reference to Transaction Codes in Document 6209 for consistency (IPU 25U3701 issued 12-08-2025).
(36) IRM 21.5.2.4.26 Updated the IRM to show that Form 9000 will now be available on irs.gov and not on IOLA per new guidance. Added verbiage from IRM 21.5.2.4.25, Request for Alternative Language Products by Taxpayers With Limited English Proficiency (LEP) for clarity (IPU 26U0619 issued 06-10-2026).
(37) Editorial changes were made throughout this IRM for clarity and IRM improvement. Reviewed and updated plain language, grammar, web addresses, IRM references, and legal references.
Effect on Other Documents
IRM 21.5.2, Adjustment Guidelines, dated August 21, 2025 (effective October 1, 2025) is superseded. This revision incorporates the following IRM Procedural Updates (IPU): IPU 25U3701 (issued 12-08-2025), IPU 26U0208 (issued 02-06-2026), IPU 26U0390 (issued 04-02-2026). IPU 26U0619 (issued 06-10-2026).
Audience
All IRS organizations - Small Business / Self Employed (SB/SE), Large Business & International (LB&I), Tax Exempt and Government Entities (TE / GE) and Taxpayer Services (TS), IRS Independent Office of Appeals, Employee Plans (all employees performing account work).
Effective Date
(10-01-2026)
LuCinda Comegys
Director, Accounts Management
Taxpayer Services
- Purpose: This Internal Revenue Manual (IRM) provides standard operating procedures for correcting, adjusting or resolving taxpayer accounts issues. These guidelines provide step-by-step procedures to resolve taxpayer account issues. Subsections include links to related guidance when additional information is needed.
- Audience: The primary users of the IRM are all IRS employees in Business Operating Divisions (BODs) who are in contact with taxpayers by telephone, correspondence, or in person.
- Policy Owner: The Director of Accounts Management is the policy owner of this IRM.
- Program Owner: Accounts Management Policy and Procedures IMF (PPI), is the program owner of this IRM.
- Primary Stakeholders: The primary stakeholders are organizations that Accounts Management collaborates with; for example, Return Integrity & Compliance Services (RICS), Compliance and Submission Processing.
Program Goals: Program goals for this type of work are:
- Achieving a high customer accuracy rate for phone calls and paper adjustments.
- Resolving general adjustment cases efficiently.
- Identifying program vulnerabilities and opportunities for improvement.
- Communicating effectively with taxpayers.
The FY 2025 Program Letter and Operating Guidelines provides further information about program goals.
- Employees in the Accounts Management (AM) organization respond to taxpayer inquiries by telephone in customer service centers. They also process amended returns, claims, duplicate-filed returns, loose forms, correspondence, and other internal adjustment requests.
- See IRM 1.2.1.2, Policy Statements for Organization, Finance and Management Activities, and IRM 1.2.1.13, Policy Statements for Customer Account Services Activities, for information.
The following policy statements provide authority for this IRM:
- Policy Statement 21-1, Service Commitment to Taxpayers Service Program
- Policy Statement 21-2, The public impact of clarity, consistency and impartiality in dealing with tax problems must be given high priority
- Policy Statement 21-4 (Formerly P-6-13), One-stop service defined
- Policy Statement 21-5 (Formerly P-6-40), Assistance furnished to taxpayers in the correction of accounts
- The Taxpayer Services Chief is responsible for the policies governing this IRM, which is published annually.
- The Accounts Management Director is responsible for the procedures contained in this IRM.
- Accounts Management Policy and Procedures IMF (PPI) tax analysts maintain the content of this IRM and serve as points of contact for all Accounts Management sites.
- Managers and leads ensure employees follow the guidance and procedures in this IRM.
- Employees input adjustments by following the procedures in this IRM.
- The Taxpayer Bill of Rights (TBOR) groups existing taxpayer rights into 10 fundamental rights using plain language. Employees are responsible for understanding and acting in accordance with those 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.
- See IRM 1.1.13.6.3, Accounts Management, and IRM 21.1.1, Accounts Management and Compliance Services Overview for additional information.
- Program Reports: The reports referenced in this IRM help Accounts Management Contact Representatives (CRs) and Tax Examiners (TEs) identify applicable program information. For reports concerning quality or inventory aged listing, refer to IRM 1.4.16, Accounts Management Guide for Managers. You can also access aged listings through Control Data Analysis, Project PCD, on the Control-D/Web Access server. Access requires authorized login credentials.
Program Effectiveness: Program effectiveness is measured through:
- National Quality Review System (NQRS)
- Centralized Evaluative Review (CER)
- Managerial reviews
- Program reviews conducted by Accounts Management Policy and Program IMF (PPI) Individual Adjustments (IA)
- Annual Review: Managers review the processes in this IRM annually to ensure accuracy and promote consistent tax administration.
- Goals, measures, and operating guidelines are provided in the annual Program Letter. For quality data and measurement guidelines see,IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Examination, Field Assistance, Tax / Exempt / Government Entities, Return Integrity and Compliance Services (RICS) and Electronic Products and Services Support.
The following table lists acronyms commonly used in this IRM. For a comprehensive listing of IRS acronyms, see the Acronym Database.
Acronym Definition AC Action Code AMS Account Management Services BMF Business Master File CDS Centralized Distribution Site CII Correspondence Imaging Inventory CFOL Corporate Files on Line CR Contact Representative DLN Document Locator Number EQ Embedded Quality FTF Failure To File FTP Failure To Pay IDT Identity Theft MeF Modernized e-File RCA Reasonable Cause Assistant RICS Return Integrity and Compliance Services RRD Return, Request, Display Application TE Tax Examiner
Related resources for this IRM include, but are not limited to:
- Taxpayer Services Insider- Accounts Management
- Servicewide Electronic Research Project (SERP)
- IRS.gov
- Publication 17, Your Federal Income Tax
- Applicable sections of IRM 21, Customer Account Services (refer to the table of contents for a list of available sections)
- IRM 20.1, Penalty Handbook
- Internal Revenue Code (IRC)
- Correspondex Letters
- IRM 1.2.1.13, Policy Statements for Customer Account Services Activities
- Taxpayer Advocate Service is an independent organization within the Internal Revenue Service (IRS)that helps taxpayers resolve problems with the IRS and protects taxpayer rights. TAS provides free assistance when taxpayers experience financial hardship, cannot resolve an issue through normal IRS channels, or believe an IRS process is not working as intended. See Taxpayer Advocate Service for additional information.
- Adjustment guidelines provide procedures for working account adjustments. Related IRM chapters provide detailed guidance for specific adjustment topics.
- Complete all required account research before taking any account action. You may need to reference other Internal Revenue Manuals (IRMs). See IRM 21.5.1.3, General Adjustments - Research, for a listing of IRMs that may be required for research. Depending on the case, you may also need additional IRM sections, publications, or the Internal Revenue Code (IRC) provisions.
Research IDRS for account conditions that could affect case processing. See CCJA - IDRS Command Code Job Aid for information about each command code. This IRM does not address every scenario or research path. If you need additional guidance, contact your lead or manager.
- Use CC SUMRY Use CC SUMRY first to determine whether a tax module or control base exists on the Tax Information File (TIF). CC SUMRY displays a summary of the taxpayer's account, including all tax modules that meet IDRS selection criteria.
Use CC TXMOD with definer "A" to display tax module information for the applicable tax period(s). Research for the following:
• Freeze codes, See IRM 21.5.6, Freeze Codes, for information and procedures.
• TC 971 codes, See IRM 21.5.1.4.8, Transaction Code 971, and Document 6209, Section 8C-9, TC 971 Action Codes for more information. The Integrated Automation Technologies (IAT) Code Search Index (CSI) tool may also be used.
• Previous or pending adjustments, unpostable adjustments, offsets and refunds. See IRM 21.5.5.4.1, Preventing Unpostables.
• Math Errors on the original return. See IRM 21.5.4, General Math Error Procedures.
• Open AUR - TC 922. See IRM 21.3.1.6.41, Status of Individual Master File (IMF) Underreporter Cases.
• TIN related problems. See IRM 21.6.2.2, What Are TIN-Related Problems?
• Current year balance due returns with TC 150 with "00000000s" in the Posted Date field. These accounts are "unsettled" balance due tax returns and the IAT xMend tool cannot determine what the current value is. Since these tax modules are actually "partially-posted" and NOT FULLY SETTLED, not all of the credits are posted on CC TXMOD until the module is settled (i.e., EITC). DO NOT adjust the account until the account becomes settled. The TC 150 for current year returns will post in cycle 20, after which they remain unsettled for 2 additional cycles. After the 2 cycles, the return settles and the CP 14 is issued providing the module is in balance due. Reassign CII cases received prior to the settlement cycle (cycle 20) to the IDRS number listed for "Unsettled Balance Due Accounts" on the AM Site Specialization Temporary Holding Numbers website. Do not reassign prior year accounts if the current year module is unsettled.Note:
Only current tax period accounts with a TC 150 that display "00000000" in the Posted Date are reassigned to the IDRS holding number. Unpostable or Rejected returns are not considered "unsettled" and are not reassigned to the IDRS holding number.
• If there is a Transaction Code (TC) 604 on the module, check with the proper Collection insolvency group to obtain approval to adjust the account. Ask Collections to reverse the TC 521 and TC 971 Action Code (AC) 031. This action is taken to allow your adjustment to post. If this is an International account, contact the proper Collection insolvency group at the Philadelphia Campus, who processes and adjusts these types of accounts. Refer to Bankruptcy Inquiries for the updated telephone listing.- Use CC ENMOD to research entity information and issued correspondence. See IRM 21.6.2.2, What are TIN - Related Problems?, and IRM 21.6.1.4, Filing Status Research.
- Follow disclosure guidelines for all adjustment actions. Do not discuss taxpayer accounts with unauthorized parties. See IRM 21.2.3.5.1, Disclosure Requirements.
- Access all required systems. Check Account Management Systems (AMS) for taxpayer account history, suspicious activity, and representative authorization before providing any account information. See IRM 21.2.1.8, Account Management Services.
Obtain the documents, returns, and taxpayer-provided information needed to adjust the account or respond to the inquiry.
Note:
Employees working Form 4442 must follow IRM 21.5.1.5.4(3), Viewing or Requesting Documents on CII Cases.
Exception:
If you are staffing the toll-free lines and a document is needed that is not available on Correspondence Imaging Inventory (CII), do not order any document that cannot be received by close of business on the day of the taxpayer telephone contact. Complete Form 4442 /e-4442, Inquiry Referral, and route to the campus Accounts Management (AM) paper function within your directorate except Puerto Rico who send the Form 4442 /e-4442 to the Brookhaven Campus paper function until further notice. Use "ESTABD" as the referral category. Some local procedures allow for campus employees to order the document and keep the case in their individual inventory.
- Taxpayers may electronically file amended returns for the current tax year and two prior years. The amended return documentation is reviewed via the MeF Return Request Display (RRD) application. These cases are identified on IDRS by Control Base Category Codes Category Code MEFP identify MeF Form 1040-X cases assigned to Submission Processing and Category Codes MEFA (Form 1040-X MeF), MEFC (Carryback Form 1040-X MeF), MEFI (International Form 1040-X MeF) and MEFR (International Carryback Form 1040-X MeF) identify cases assigned to Accounts Management. See IRM 21.2.1.22, Modernized e-File (MEF/TRDB), for more information.
- Campuses retain returns for a limited time before transferring them to the Federal Records Center (FRC). Returns may also be transferred between campuses for processing.
Research CII for open or closed cases that could affect your case. See IRM 21.5.1.5.2, Cases Currently Assigned in CII, for more information.
Reminder:
If the taxpayer submits multiple returns or correspondence for the same MFT and tax period, link the cases using the Link Function on the Active Case page.
Research may show an OPEN control base. Whenever possible, multiple cases from the same taxpayer are processed by the same employee. Coordination of these same taxpayer, multi-year cases is necessary to ensure consistent processing. See Case Management Guidelines for more information. Always contact the employee with an open control base prior to taking any action on a case, except in the following instances:- DO NOT initiate contact by phone or email if a Form 4442 /e-4442, Inquiry Referral, is the proper action based on Exhibit 21.3.5-1, Referral IRM Research List.
DO NOT initiate contact if the control is in "B" status unless directed by another IRM. (For Campus employees only, if the phone call resolves the correspondence issue and the CII case received date is less than 23 days old, use the "Update Case Data" button on the CII case to "turn off" the interim letter feature in CII). Regardless if the interim letter has already been issued or not, ensure the caller is aware this issue has been resolved and leave a CII case note indicating a closing letter is not needed.
Exception:
If control bases are "CII to CII" , follow the Case Management Guidelines Job Aid, Section 2, Multiple Control Bases, and refer to IRM 21.5.1.5.2, Cases Currently Assigned in CII, for more information.
- DO NOT initiate contact if the only open control is a nullified unpostable with category code NLUN.
- DO NOT initiate contact with the employee if the control is to a clerical unit. Clerical assignee numbers represent workflow designations rather than individual employees. These non-employee assignee numbers are frequently distinguished by zeros in the last five digits of the employee number; however, numerics other than zero may also be used. Lists of these numbers are provided in either campus IDRS bulletins or the IDRS MESSG file. Refer to IRM 21.5.2.4.3, Adjustments Requiring an Amended Return or Taxpayer Documentation, for more information on resolving the telephone inquiry.
- DO NOT initiate contact if the open control is assigned to the Accounts Management Centralized Distribution Site (CDS) or Site Specialization Number. See Accounts Management CDS/Site Specialization Temporary Holding Numbers. The CDS uses individual's IDRS numbers as temporary holding numbers for specialized work until the case can be reassigned or distributed. Accounts Management employees can reassign a case to the CDS temporary IDRS holding number when required by an IRM.
- DO NOT initiate contact if the open control has identity theft involvement and a multiple control is present with specialized inventory outside your scope (e.g., IDT1, IDT3, IDT8 etc. Refer to IRM 21.5.2.3.1, Adjustment Guidelines – Identity Theft Research, for guidance on multiple controls when there is an open control for an existing case with IDT category (i.e., IDT1, IDT3, IDT8), assigned to:
• IDTVA employee
• Unassigned Queue (e.g.,1042000000)
• IDTVA Accounts Management Centralized Distribution Site (CDS)
• Site Specialization number
Business Master File (BMF) Identity Theft can involve the use of business information to file fraudulent returns to support individual Master File (IMF) ID theft or to obtain refunds from BMF accounts. A person can use an individual’s stolen personal information to obtain an Employer Identification Number (EIN) to file false BMF tax returns and income documents. For BMF returns selected by RICS as potential identity theft, refer to IRM 25.23.9.4.1, BMF Returns Selected for Return Integrity and Compliance Services (RICS) Review. For additional information, please see IRM 25.23.9.2 Business Master File (BMF) Identity Theft – Overview and IRM 25.23.9.4 Business Master File (BMF) Identity Theft Research. DO NOT initiate contact if the open control is assigned to a site "generic employee number" , see IRM 21.5.1.5.1(1), CII General Guidelines.
Note:
Generic employee numbers for Submission Processing (SP) can be found in IRM 3.11.6.3, Controlling Cases on the Correspondence Imaging Inventory (CII) System, and IRM 3.11.6.10.4, MEFP and MEFS Accounts Management Rejected Queue.
Some taxpayer inquiries cannot be resolved by AM. Refer these cases to another function for review. When appropriate, cases are returned to the AM function for account action or for a letter of explanation to the taxpayer.
The office that receives the taxpayer's call or correspondence is responsible for resolving the inquiry unless another IRM instructs otherwise. Do Not refer cases to another campus or call site unless an IRM specifically instructs you to do so. If you are staffing the toll-free phone lines and are not profiled or trained to work CII cases, do not work the case or control. DO NOT give employee phone numbers to taxpayers.Exception:
Your campus may have a local agreement to send paper cases to another site or group. Those cases are worked following the rules in the local agreement and not shipped to the campus that processed the original return.
- Cases meeting Taxpayer Advocate Service (TAS) criteria are referred as outlined in IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines. Contact TAS when the case has an open TAS control prior to taking any case actions.
- Appeals – See IRM 20.1.1.4.1.2, Post-assessment Appeals, for penalty appeal information and IRM 21.5.3.4.6.2, Appeals and Responses to Letter 105C and Letter 106C.
- Under the Bipartisan Budget Act (BBA) of 2015, amended returns filed by individual partners while the partnership is under BBA examination must be reviewed by BBA Operations. These filings are marked with "BBA Partner Modification Amended Return" across the top of page 1. If the return is already in CII, AM contact representative must route the return to BBA Operations. See IRM 21.7.4.4.2.9(9), Form 1065 and Form 1065X, Amended Return, Administrative Adjustment Request (AAR) and Bipartisan Budget Act (BBA).
- Frivolous Arguments – See IRM 21.5.3.4.16.7, Identifying Frivolous Returns/Correspondence and Responding to Frivolous Arguments.
Before taking any account action, transferring a call, or reassigning a case to IDTVA, complete all required account research. The initial employee must identify the taxpayer's issue and research the account, including Account Management Services (AMS), to resolve routine account issues before determining whether to reassign the case to IDTVA for potential identity theft (IDT).
Reminder:
Before reassigning the case, document the actions taken and the reason for the reassignment in a case note.
Refer the case to IDTVA if any of the following conditions apply:
- If the CII case contains Form 14039, Identity Theft Affidavit, or the taxpayer states they are a victim of identity theft, follow IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview, for required action before reassigning the case to IDTVA.
- If a multiple control exists for an IDT category case (e.g., IDT1, IDT3, IDT8), assigned to an IDTVA employee, or assigned to an unassigned queue (e.g.,1174078935), or IDTVA Accounts Management Centralized Distribution Site (CDS) Site specialization number. Refer to Accounts Management CDS/Site Specialization Temporary Holding Numbers listing to identify the IDRS numbers. See below for specific guidance.
If a multiple control exists with specialized inventory outside your scope (e.g., IDT1, IDT3, IDT8) and:
- Assigned to an IDTVA Accounts Management Centralized Distribution Site (CDS), Site Specialization Number or Unassigned queue (e.g., 1174078935 for domestic and 1176064055 for international), link your CII case to the open IDT case and close your case as MISC. Document the following case note on the existing IDT case: multiple control with IDTVA, linking ‘state category of your case’ (e.g., "Multiple control with IDT case, linking MEFP/MEFS" ). For a listing of IDTVA codes, refer to Exhibit 25.23.2-16, IDTVA IDRS Category Controls by Function.
Assigned to an IDTVA employee not listed under IDT categories on the Accounts Management CDS/Site Specialization Temporary Holding Numbers listing, link your CII case to the open IDT case and reassign to the IDTVA employee. Document the following case note on the existing IDT case: "multiple control with IDTVA, linking XXXX" , (e.g., "Multiple control with IDT case, linking XRET" ).
Note:
Cases in categories IDT7 (Request for Fraudulent Return) and IDTX (Request for an IP PIN) do not necessarily indicate identity theft. If the multiple control is present with one of these categories and there are no other IDTVA case categories, and your case does not solely consist of a request for a fraudulent return or IP PIN, continue to the instructions below and do not update your case category to IDT7 or IDTX.
- If the criteria above are not met, continue researching the account to determine whether another treatment stream applies before considering identity theft. Complete research helps identify the correct corrective action and prevents unnecessary processing delays. The following information contains research tips and reminders to take into consideration as you research your case. The IRM sections cited below are not all inclusive. Reference other IRM sections as applicable.
Use the following definitions and referenced IRM sections to identify the correct account issue. If any of the following conditions apply, do not treat the case as identity theft. Follow the applicable IRM procedures.
Mixed Entity (MXEN) - The unintentional use of a taxpayer's TIN because of taxpayer, preparer, or IRS processing error. Refer to IRM 21.6.7.4.4.1, Duplicate Filing Control - (DUPF) and IRM 21.6.2.4.4, Mixed Entity Procedures.
- Mixed Period - a return for the correct taxpayer that posted to the wrong tax year, usually because of an editing error or use of the wrong tax-year form. (e.g., TY 2020 income reported on a TY 2021 form). Refer to IRM 21.6.7.4.2.5.1, Mixed Periods.
- 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. Refer to IRM 21.6.2.4.5, Scrambled SSN Case Reassignment/Referral Procedures.
- If applicable, search returns, schedules, and forms for another TIN. Research spouse and dependent information, when available.
- Research the TIN (valid and invalid) to determine if there is a mixed entity (MXEN), or scrambled SSN case (SCRM/SSA2) in prior and/or subsequent years. 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 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 shown by an asterisk (*) following the last digit of the TIN. Additionally, the tax return(s) in question is reviewed to determine if the case is a mixed period instead of a TIN-related issue.
Research both the valid and invalid sides of each identified TIN (for example, primary, secondary, or alternate TINs). A return posted to the invalid side of the Common Number (CN) alone does not establish identity theft. Conduct further research 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 typographical errors 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.2, Resequencing Accounts, and its subsections.If additional research is needed to locate the taxpayer’s TIN, use CC NAMES or CC NAMEI to 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 include taxpayer information from areas surrounding the current address. Consider the following possibilities when conducting research using CC NAMES or CC 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 have included a hyphenated last name or variation in spelling of their name due to typographical errors by the taxpayer, a preparer, or IRS.
Refund inquiry – The non receipt of a refund does not automatically warrant an ID theft referral. Refer to the applicable procedures in IRM 21.4, Refund Inquiries.
Example:
Taxpayer correspondence states they did not receive the EIP payment. This does not necessarily mean there is identity theft. Research the account to determine whether the EIP was issued, where it was issued, if it was offset, etc. Review the tax return that the EIP was based on for possible inconsistencies. If the refund was issued to a valid direct deposit or mailing address, normal refund inquiry procedures are followed. If there is an account related explanation, it is not identity theft.
- Review the account for freeze code conditions. Follow IRM 21.5.6, Freeze Codes, as applicable.
The presence of TPP indicators does not automatically mean the taxpayer is a victim of identity theft. TPP selects returns that require taxpayer authentication. Review the account, including AMS, to determine whether the TPP issue has been resolved.
Example:
If you have an amended return and there are TPP indicators on the account, research the account further.
- If the TPP issue was resolved and AMS shows the taxpayer authenticated and the return is posted, work your case following normal procedures.
- If the TPP issue was resolved, there is an MFT 32, and a TC 150 is posted, review the posted original return to determine whether the taxpayer filed that return. If there is no indication of Identity theft about the posted return, your case can be worked following normal procedures.
- If the TPP issue was resolved and there is a TC 971 AC 123 on the MFT 30 and/or on CC IMFOLT/TXMODA with a MISC field TPP RP, work your case following normal procedures.
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
- ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ - ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ - ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ - ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ - ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
- ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
After completing all required research and applicable procedures, determine whether another treatment stream applies. If no other treatment stream applies and account discrepancies indicate possible identity theft, refer the case to IDTVA.
- Before reassigning the case, follow IRM 25.23.4.6, Research, Actions and Complete Case Analysis - Overview to complete any required actions (e.g., TC 971 AC 522, 5073C letter). Review the account to see if a CP 01S, CP 701S was issued to acknowledge receipt of Form 14039, Form 14039 (SP), a police report, or a similar statement related to identity theft.
- For cases originally controlled with a non-IDT category code (e.g., DUPF, XRET, TPRQ, etc.), determine the appropriate category (e.g., IDT1, IDS1, or IDT3, IDS3, etc.) per Exhibit 25.23.4-9, IDTVA-A Identity Theft (IDT) Work Types Listing.
- Document the research completed, the research results, the request for reassignment, and lead or manager approval to reassign in a CII case note. Refer to IRM 21.5.1.5.2, Cases Currently Assigned in CII, for further information.
Reassign to the applicable IDTVA holding number per Accounts Management Site Specialization Temporary Holding Numbers Listing, located on SERP.
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.
- Follow the procedures in IRM 21.5.1, General Adjustments, when making account adjustments.
- For information on received dates when adjusting an account, see IRM 21.5.1.4.2.4, Received Date – Determination, and IRM 21.5.1.4.2.5, Received Date – Grace Periods.
- IRM 21.3.3.4.8, Taxpayer Inquiries and Complaints, provides information about why taxpayers contact the IRS. It also identifies the applicable IRMs, forms, letters, technical functions, referrals, and telephone numbers needed to obtain technical assistance.
- Administrative waivers and statutory exceptions help employees process adjustment requests timely and efficiently. For penalty specific guidance, see IRM 20.1.1.3.3, Statutory Exceptions and Administrative Waivers.
Adjustment requests involving tax, penalty, interest, or other issues are received in two forms:
- Written
- Verbal
Administrative waivers and statutory exceptions may be granted:
- To benefit taxpayers.
- To support tax administration.
- Or both.
- Under IRC 6656(e) and Rev. Proc. 2001-58, taxpayers may designate the tax period or periods to which the IRS applies a deposit. See IRM 21.5.2.4.9, Penalty Overview.
- Taxpayers may make the designation orally or in writing. Oral statement ceiling amounts do not apply.
- The IRS may make errors when assessing tax, penalty, or interest.
- Oral statement ceilings do not apply when correcting these errors.
For additional guidance, see:
- IRM 20.2.7, Abatement and Suspension of Debit Interest
- IRM 20.1.1.3.4, Correction of Service Error
- For reasonable cause criteria, see IRM 20.1.1.3.2, Reasonable Cause.
- ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡, see Oral Statement and Penalty Relief Request (Reasonable Cause) FTF, FTP & FTD Penalties.
- For penalty relief, see IRM 20.1.1.3, Criteria for Relief from Penalties.
IRM 21.1.3.20, Oral Statement Authority, explains oral statement authority for Accounts Management. This subsection provides the procedures Accounts Management must follow when working oral statement issues.
Note:
For Business Master File (BMF) and Non-Master File (NMF) oral statement procedures, see IRM 21.7.1.4(2), Business Master File (BMF)/Non-Masterfile (NMF) Adjustment Procedures.
- Payment / Credit Transfers – There are no oral statement ceiling amounts / dollar limits. See IRM 21.5.8.2, Credit Transfers Overview.
- Credit Elect Problems – See IRM 21.4.1.5.6, Credit Elect Problems.
- Reverse Credit Elect Payments Shown on the Return – See IRM 21.4.1.5.6.1, Credit Elect Reversals.
- Invalid SSN Refund Releases – See IRM 21.6.1.6.7, Resolving CP 54 with Math Error Involvement.
- Withholding Adjustment (to Ceiling Amount) – See IRM 21.6.3.4.2.2, Withholding (W/H) Tax Credit, or IRM 21.5.1.4.12, Tolerances.
- Math Error Substantiated Protests – See IRM 21.5.4.4.4, Math Error Substantiated Protest Processing.
- Certain Freeze Releases – See IRM 21.5.6.4, Freeze Code Procedures.
- True Duplicate Return (Except Form 1065, U.S. Return of Partnership Income) – For Individual Master File (IMF), see IRM 21.6.7.4.14, True Duplicate Return. For Business Master File (BMF), see IRM 21.7.9.4.1.3, True Duplicate.
- Math Errors, IRS Errors or Decimal Point Errors – See IRM 21.5.4, General Math Error Procedures.
- Penalty Relief Request – see IRM 21.5.2.4.9.2, Oral Statement and Penalty Relief Request.
- Name, Taxpayer Identification Number (TIN), Address, Filing Status, and Filing Requirement Changes – See IRM 3.13.5, Individual Master File (IMF) Account Numbers, and IRM 3.13.2, BMF Account Numbers, IRM 21.6.1.4, Filing Status Research. IRM 21.7.13.6.5.6, Authority for Making Primary Name Line Changes, and IRM 21.7.13.7.2.2, Cases Forwarded to Submission Processing BMF Entity.
- BMF Changes to Item Reference Code / Numbers (not tax) – See IRM 21.7.1.4, Business Master File (BMF) Non-Master File Adjustment Procedures.
- Earned Income Tax Credit – See IRM 21.6.3.4.2.7.9, EITC - Adjusting the Account.
If an address change is necessary and the taxpayer requests the address change using an oral statement, the address change may be input into IDRS based on Rev. Proc. 2010-16, Rev. Proc. 2010-19, IRB 664. Refer to IRM 21.1.3.20.1, IMF and BMF Oral Statement Address Changes for further information.
Reminder:
If the taxpayer reports a temporary address (for example, while attending college), do not update the Master File address. Document in Account Management Services (AMS) that you advised the taxpayer the temporary address would not be updated.
Exception:
If the account contains a Large Corp Indicator (LCI), do not use oral statement authority to change the address. See IRM 21.7.1.4.11.3, Routing Large Corp Cases and Inquiries.
Caution:
Do not change the address based on oral statement authority if the account contains an open Taxpayer Protection Program (TPP) issue or an unreversed TC 971 AC 124, unless otherwise directed in IRM 25.25.6, Taxpayer Protection Program.
- An oral statement adjustment made before the return due date is not superseding information and does not create a superseding return, as described in IRM 21.6.7.4.10, Superseding Returns.
- Adjustment actions completed on-line using oral statement authority do not require case files unless required in another IRM procedure requires one. Do not prepare unnecessary case files. Generally, input oral statement adjustments as Non-Source Document (NSD) adjustments. See IRM 21.5.2.4.5, Source Documents, for additional information.
- For actions that cannot be completed online, create a case file using Form 4442 /e-4442, Inquiry Referral. Describe the taxpayer's inquiry and the actions taken to resolve the account. After the review is complete, destroy the Form 4442 as authorized by Document 12990, IRS Records Control Schedule (RCS) 29, Item 191.
- Generally, adjusting an item that was not reported on the original return requires a signed amended return. Advise the taxpayer and order the required tax forms, if needed. See IRM 21.3.6, Forms and Information Requests.
A signed amended return is not required if one of the following conditions applies:
Row If Then 1 The taxpayer listed the item on the original return, but did not include the necessary schedule - A math error notice is issued.
- The item may not appear on RTVUE / BRTVU.
2 The taxpayer received a math error notice and provides substantiation in the case of a math error - Accept oral statement (up to the amount shown on the original return) even if the –G Freeze is no longer on the account.
- See IRM 21.5.4.4, Math Error Procedures Processing.
The following actions require a written request:
- Penalty abatements that exceed oral statement authority. Refer to IRM 21.5.2.4.9.2, Oral Statement and Penalty Relief Request, for additional information.
- Abatements of interest.
Use the taxpayer’s written request as the source document. See the following IRMs for additional guidance:
- IRM 4.19.3, IMF Automated Underreporter Program
- IRM 4.119.4.21.1.2, Abatement of Interest
- IRM 20.1, Penalty Handbook
- IRM 20.2.7, Abatement and Suspension of Debit Interest
- IRM 4.19.10, Examination General Overview
If a taxpayer's request requires written documentation or supporting evidence, determine whether the taxpayer can fax the documents while you are on the telephone. Use the following table.
Row If Then 1 The required documentation can be faxed while you are on the telephone with the taxpayer
- Provide the specific fax number to the taxpayer.
- Retrieve the faxed documentation.
- Adjust the account as appropriate.
- Input the adjustment as a "Source Document" adjustment if there is no CII case. If there is a CII case, attach the missing information and / or information received from the taxpayer to the case as an attachment (if CII access).
2 The required documentation cannot be faxed while you are on the telephone with the taxpayer - Advise the taxpayer to call back when able to fax the required documents.
- If the taxpayer is unable to fax or prefers not to fax the required documents, advise the taxpayer to attach the required documentation to the notice and mail it to the address shown on the notice or upload the required documents using the Document Upload Tool (DUT) if the taxpayer’s notice or letter allows it.
- Advise the taxpayer of the normal processing time frame for a response to correspondence (30 days).
- Input a STAUP, if needed, as outlined in IRM 21.5.2.4.8.2, Suppressing Balance Due Notices.
- Do not open a control base.
- Do not complete a Form 4442 /e-4442.
- For information on Form 941-X, Adjusted Employer’s QUARTERLY Federal Tax Return or Claim for Refund (including the Form 941-X(PR)), refer to IRM 21.7.2.4.5.5, Form 941 Discrepancy — Taxpayer Files Form 941-X.
Campuses may receive Form 4442/e-4442 referrals or adjustment requests involving return processing errors. These cases involve returns with partial, zero, or other identifiable transcription errors that do not involve freeze codes, Error Resolution System (ERS) processing, or math error procedures. Complete account research and the original tax return are required before adjusting the account. Use the following table to process these cases. These cases are centralized in Fresno and Philadelphia (International). Convert the CII category code to SPC 5 and reassign the case using the AM Site Specialization Temporary Holding Numbers website. For additional guidance on transcription errors, see IRM 21.4.1.4.1.2.1, Return Found-Processing Errors Identified.
- For information on Form 941-X, Adjusted Employer’s QUARTERLY Federal Tax Return or Claim for Refund (including the Form 941-X(PR)), refer to IRM 21.7.2.4.5.5, Form 941 Discrepancy - Taxpayer Files Form 941-X.
- The DLN for IMF and BMF accounts contains information used to process cases.
- The DLN is the 14-digit number assigned to each return or document processed through the Automated Data Processing (ADP) system. DLNs appear on computer documents in XXXXX-XXX-XXXXX-X format. See DLN Composition in Document 6209, IRS Processing Codes and Information, for detailed information.
Some adjustments completed using oral statement authority require source documents (SD):
- If an erroneous refund was issued, follow the procedures in IRM 21.4.5, Erroneous Refunds.
- Missing schedules.
Penalty determinations – See IRM 20.1.1.3.6.6, Attaching RCA Determination.
Note:
Source Documents are not required for credit transfers completed over the phone. See IRM 21.5.8.3.1, Determining Source Document Requirement for Credit Transfers.
- Verify disclosure requirements before providing account information. See IRM 21.1.3.2.3, Required Taxpayer Authentication, as applicable. See also IRM 21.1.3.2.4, Additional Taxpayer Authentication, and IRM 21.3.7, Processing Third Party Authorizations onto the Centralized Authorization File (CAF).
Request that taxpayers provide the documentation required for adjustments listed in paragraph (1). The taxpayers may fax the documentation. Provide your fax number, including area code. See IRM 21.5.2.4.3, Adjustments Requiring an Amended Return or Taxpayer Documentation, and also refer to IRM 21.3.5, Taxpayer Inquiry Referrals Form 4442, for further instructions.
- The "Remarks" field must include specific information for each type of IDRS input (for example, entity changes, tax adjustments, penalty adjustments, or credit transfers). Oral statement authority adjustments have different requirements. See IRM 21.1.3.20.2, Oral Statement Documentation Requirements, when inputting the remarks for an oral statement account change.
If the input is not completed with an oral statement, input the adjustment with "SD" , "NSD" , or "SDR" in the remarks field (or Y, N, or R on the Command Code (CC) ADJ54 screen).
- SD (Source Document) shows the document is being forwarded to files for attachment to the IDRS transaction record
NSD (Non Source Document) shows the documents are attached to the IDRS transaction record, such as with an image in the Correspondence Imaging Inventory (CII)
Note:
Taxpayers have the option to electronically amend the current tax year and two prior year Form 1040 and Form 1040-SR returns that were originally e-filed through the Modernized e-File Return (MeF) application. The CII cases created by Account Management Services (AMS) do not contain a digital CII image; however, the documentation remains available within the MeF Return Request Display (RRD) application. When adjusting these cases, use NSD.
- SDR (Source Document Retained) shows the document is being held for follow up case actions, but will later be attached to the IDRS transaction record
Use the remaining positions in the remarks field to briefly explain the reason for the adjustment or credit transfer.
- When completing both an adjustment and a credit transfer, input the required items on the adjustment and reference them in the "remarks" section of the credit transfer.
Briefly describe the reason for the adjustment (for example, "credit transfer" ). Also document the applicable letter or other supporting justification, as shown in the following table:
If And Then You are inputting multiple transactions (for example, TC 29X, 670/672, or TC 971) Actions are for the:
- Same taxpayer
- Same tax period,
- Same TIN,
and a TC 29X is one of the TCs used.- Record the required information in the Command Code ADJ54 Remarks field.
- In the related transactions Remarks field, enter NSD and identify where the supporting documentation is located.
Exception:
Do not apply the table instructions when making entity adjustments. Always record the required information on all entity changes, regardless of the source or the number of actions being taken.
- If the oral statement procedures in this IRM conflict with procedures in another IRM, follow the specific IRM.
Suppress notices using the method appropriate for the notice type and issue. Use one of the following methods:
- Command Code (CC) STAUP
- Hold Codes
- Notice Suppression Codes or Indicators
- Some IDRS command code input screens include a field that indicates whether a notice will be issued. Notice Suppression procedures appear throughout IRM 21, Customer Account Services, as applicable.
- If CC STAUP cannot be used because the action results in a settled module, and offset is likely (January - May for IMF, about 8 weeks after due dates for BMF), input a TC 470 without a closing code.
- If you use CC STAUP or a TC 470 to suppress a balance due notice, enter an Account Management Services (AMS) history item documenting the reason for the action (e.g., Taxpayer to file Form 1040-X or Taxpayer will send a check).
Enter the Notice Suppression Indicator (NSI) in the "CP-NTC-SUPP-IND" field on Command Code ADJ54 to suppress small balances on adjustment notices.
- For Business Master File (BMF) requirements for Notice Suppression Indicator 1, see IRM 21.7.1.4.2, Notice Suppression Indicator (NSI).
Use Command Code (CC) STAUP to suppress balance due IDRS notices. This requirement also applies to cases referred to other functions or sites.
If enough time remains before the next scheduled notice to complete the required action, do not input a STAUP. There are generally five weeks between notice statuses, except between Status 58 and Status 22, when the interval is five to ten weeks.
Note:
Input CC STAUP only if you need to delay the next notice. If it takes more than two weeks for the account to settle and it is in NOTICE status, you need to input a CC STAUP if another NOTICE is due to generate, see Exhibit 5.19.10-1, Restrictive Conditions, for exceptions.
As of April 19, 2021, Accounts Management (AM) no longer negotiates payments on balance due accounts or sets demand dates for missing or unfiled returns. Refer to IRM 21.1.1.3.1, Accounts Management (AM) Customer Service Representative (CSR) Duties Handling Accounts with Balance Due Accounts / Missing Returns, for more information. However, there may be occasions when you must input a STAUP. Refer to the If / Then chart, in paragraph c, to determine whether to input CC STAUP or transfer the call to Automated Collection System (ACS).
Note:
CC STAUP only prevents an erroneous IDRS notice if it is input by the Friday before the erroneous notice is scheduled to generate (17 days prior to the 23C date).
Use the following chart to determine the number of delay cycles to input:
Row If Then 1 Requesting documents from files Allow 15 cycles. 2 Requesting information from the taxpayer - Allow 4 cycles when requesting information by telephone.
- Allow 6 cycles when requesting information by correspondence (allow an additional 2 cycles if the taxpayer is submitting overseas mail).
3 An adjustment or other action does not fully satisfy the balance due, and the taxpayer is sending payment, and the taxpayer cannot be transferred to ACS or declines the transfer Allow 6 cycles. 4 An adjustment or other action does not fully satisfy the balance due, and the taxpayer has not promised payment, and the taxpayer cannot or does not want to be transferred to ACS Input a STAUP for 3 cycles to update the remaining cycles of any previously input STAUP.
5 The action taken creates a zero or credit balance Input STAUP for number of cycles needed for the action to post.
6 Correction of unpostable situation satisfies balance due Allow 9 cycles. 7 The taxpayer is submitting any other information to satisfy balance due or requests a hold on collection while the taxpayer’s correspondence or other request is being processed. Allow enough cycles for the information to post or for the request to be processed. If the taxpayer submits the request by overseas mail, allow an additional two cycles. If the taxpayer is filing an IMF or BMF original or amended return, see boxes 10 and 11 below. 8 The taxpayer will full pay the balance due now Allow 8 cycles. See IRM 21.1.1.3.1(10), Accounts Management (AM) Customer Service Representative (CSR) Duties Handling Accounts with Balance Due / Missing Returns. 9 Taxpayer can full pay within 11 to 59 days See IRM 5.19.1.6.3, Short Term Payment Plan Within 180 Days.
10 The taxpayer is filing an IMF / BMF Original or Amended Return that will full pay tax, penalty, and interest on the balance due account See IRM 5.19.1.6.3, Short Term Payment Plan Within 180 Days.
11 The taxpayer is filing an IMF / BMF Amended Return that does not full pay the balance due See IRM 5.19.1.6, Method of Payments.
12 Routing balance due cases to other areas Input or reduce the STAUP to 9 cycles. - If CC STAUP is input for more than nine cycles, establish a control base. Otherwise, CC STAUP is released after nine cycles.
Advise the taxpayer that another notice may still be issued because CC STAUP may have been input too late to stop the next notice. Also advise:
Row If Then 1 The action taken satisfies the balance due Advise taxpayer this notice may be ignored. 2 Taxpayer submits the payment / information as you requested Advise taxpayer this notice may be ignored. Note:
See MF and IDRS Collection Status Codes, in Document 6209, IRS Processing Codes and Information for a listing of status codes.
- When a module is in status 12, CC TXMOD does not display accruals under ≡ ≡ ≡ ≡ ≡ because of Master File tolerances. View accruals below this tolerance on CC BMFOLI or CC IMFOLI. Status 12 accounts with accruals below ≡ ≡ ≡ ≡ do not continue to accrue penalty and interest. Available overpayments do not offset to Status 12 accounts.
Status 12 accounts are considered fully paid and are excluded from balance due pay-off requests and installment agreements, unless the taxpayer is aware of the unpaid accruals as described in the 1st if / then statement in (3) below.
Exception:
Status 12 accounts with manually restricted interest or penalties (-I or G- freeze) are not considered full paid. Refer the case to an interest specialist for manual computation of the interest. See IRM 21.5.6.4.18, -I Freeze, for more information.
Status 12 procedures are as follows:
Row If And Then 1 The taxpayer requests a balance due notice no other adjustment issue is involved - Check CC BMFOLI or CC IMFOLI for accruals; and
- Input TC 290 .00 with Priority Code (PC) 5 to force the computer to post unrestricted failure to pay penalty and interest; and
- allow the issuance of a balance due notice to the taxpayer.
2 A payment posts to the account the posted module balance is under ≡ ≡ ≡ ≡ ≡ ≡ and the accruals are less than ≡ ≡ ≡ ≡ ≡ ≡ The system generates TC 606 to clear the account of the posted balance due.
- Input a TC 290 .00, PC 5, to force a reversal of the TC 606.
- Issue a correct balance due notice.
3 You advise the taxpayer his or her account is paid in full the account contains modules with accruals under ≡ ≡ ≡ ≡ Input a TC 290 .00, PC 5 and HC 3. The balance due will post and clear with a TC 606.
4 You are telling the taxpayer his or her account is paid in full
the account contains modules with accruals greater than ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Do not input a TC 290 .00 with PC 5. No action is required on the account. Programming will remove the accrual balances.
- If you input Priority Code (PC) 5 to post accruals and create or release an overpayment on the same or another module, use Posting Delay Code (PDC) 1 on the credit module to allow offsets during the following cycle.
For Status 23 accounts, inputting TC 290.00 with Priority Code (PC) 5 generates a balance due notice and updates accruals. See IRM 5.19.1.6.2, Can Full Pay Balance Due Now (Payoff), for further information.
Exception:
AM employees should follow IRM 21.1.1.3.1, Accounts Management (AM) Customer Service Representative (CSR) Duties Handling Accounts with Balance Due Accounts / Missing Returns, for further information about balance due responsibilities.
See IRM 20.1, Penalty Handbook, for detailed penalty guidance. Advise the taxpayer whenever a penalty may be assessed. Explain why the penalty was asserted or assessed. See IRM 20.1.1.4, Methods of Appealing Penalties, for penalty appeal procedures.
Reminder:
Transfer all cases that meet penalty appeals criteria to the Penalty Appeals Coordinator. See Penalty Appeals Coordinators (Campus), for your site’s routing procedures.
- Use IDRS Command Code (CC) INTST or CC PINEX to explain Failure to Pay (FTP) and Failure to File (FTF) penalties. Use CC FTDPN to explain Failure to Deposit (FTD) penalties.
- IRC 6656(e)(1), and Rev. Proc. 2001-58 provide an order for applying deposits that can provide relief from so-called cascading penalties in some situations. IRC 6656(e)(2) allows the person making such deposits to designate a different application within a limited time period. Rev. Proc. 2001-58 provides guidance on such applications. See IRM 20.1.4.26.3, Statutory Penalty Relief.
- Transaction Code (TC) 971 with Action Code (AC) 262 is generated when the Failure to Pay (FTP) penalty reaches its maximum amount.
- After the account is no longer available on IDRS, TC 971 AC 262 remains available through Command Codes (CC) IMFOL and BMFOL.
- TC 971 AC 262 applies to both Business Master File (BMF) and Individual Master File (IMF) accounts.
- When computing the Failure to Pay (FTP) penalty manually, you may also input TC 971 AC 262 manually.
The IRS may grant penalty relief for the following reasons:
- Administrative waivers
- Reasonable Cause
- Designation of Federal Tax Deposits
Administrative waivers include:
- First-Time Abatement (FTA)
- Waiver of 2018 Estimated Tax Penalty - limited to individuals whose total withholding and estimated tax payments, made by January 15, 2019, equal or exceed 80% of the tax shown on their 2018 income tax return. See Notice 2019-25, Notice 2019-15 and IRB 942 for additional information.
Administrative Waivers may be granted by phone and are not subject to an oral statement dollar limitation. If the waiver criteria are met, remove or suppress the penalty using Penalty Reason Code (PRC) 044 Reason Code (RC) 065. See IRM 20.1.1.3.3.2, Administrative Waivers. See Exhibit 20.1.1-2, Penalty Reason Code Chart, for the correct reason code and penalty reason code.
Before abating a penalty based on reasonable cause, determine the facts of the case and complete all required research to verify that the penalty was properly assessed. DO NOT use FTA or manually abate a penalty if the penalty will reverse systemically after the condition causing the penalty is corrected. Manually adjusting a penalty or applying FTA criteria in these instances could have a negative impact on the taxpayer since they would no longer be eligible for FTA on a legitimate abatement claim.
Example:
The taxpayer has been charged Failure To File (FTF) and Failure to Pay (FTP) penalties. The taxpayer says he wants the penalties abated because his accountant files an extension every year along with an estimated payment for taxes owed. Research shows there is a payment received April 12th and extensions filed under all prior years. In this case if it is determined that an extension "more likely than not" was filed per IRM 20.1.2.2.3.1.1, Extension of Time to File Not Found, the resolution to the case for the FTF would be to input the extension with the TC 460. If the taxpayer requested an abatement of the FTP also, reasonable cause or first time abate would be considered for FTP only.
After determining that the penalty was properly assessed, you MUST use the Reasonable Cause Assistant program (RCA), when applicable and available. See IRM 20.1.1.3.6, Reasonable Cause Assistant (RCA), for further information. If using RCA, use it through to determination. RCA determines the appropriate action. RCA determinations:
- Abate for FTA or below tolerance.
- Abate for reasonable cause.
- Deny reasonable cause request.
- Suspend for additional information and / or for situations where Oral Statement Authority (OSA) is exceeded and a written statement is needed. See IRM 20.1.1.3.6.10, RCA Conclusions / Determinations, for more information.
- Taxpayers and authorized representatives may request penalty abatements. The IRS also considers requests submitted by third parties, including representatives who do not have an authorized power of attorney (POA). For further guidance follow IRM 20.1.1.3(3), Criteria for Relief From Penalties, for further guidance.
Oral Statement Authority limits:
- Reasonable cause - When RCA is used the oral statement limit is ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. See IRM 20.1.1.3, Criteria for Relief From Penalties, and IRM 20.1.1.3.1, Unsigned or Oral Requests for Penalty Relief, for additional information.
- First Time Abatement (FTA) - Since FTA is considered an administrative waiver of penalty, it does not carry an oral statement authority dollar ceiling for abatement. See IRM 20.1.1.3.6.1, RCA and First Time Abate (FTA) Consideration.
- No oral statement limit applies when denying penalty relief. See IRM 20.1.1.3.6.4, Oral Statement Ceiling Exceeded.
- No oral statement limit applies to penalty relief resulting from IRS errors or the designation of federal tax deposits.
- When considering an unsigned statement or oral request for penalty relief, remember that while there is a limit for reasonable cause abatements, there are no ceiling thresholds for first time abatement or denial of penalty relief. For example, if the account shows FTF assessed for $1,500 on an IMF account, RCA must be accessed to determine if the taxpayer qualifies for FTA or the request for penalty abatement may be denied. See IRM 20.1.1.3.1, Unsigned or Oral Requests for Penalty Relief, for further information.
- Before evaluating reasonable cause, RCA determines whether the taxpayer qualifies for FTA. If the taxpayer qualifies, RCA abates the assessed penalties when the request is made. See IRM 20.1.1.3.6.1, RCA and First Time Abate (FTA) Consideration, for more information.
You may consider oral statement reasonable cause relief for the following penalties:
- Failure to Pay (FTP).
- Failure to File (FTF).
- Failure to Deposit (FTD).
- Daily Delinquency Penalty (DDP).
Note:
First-Time Abatement (FTA) does not apply to the Daily Delinquency Penalty (DDP) because it is an information return penalty.
- Do not advise the taxpayer to fully pay the account before requesting reasonable cause penalty relief. If RCA determines the taxpayer meets reasonable cause, the abatement will include the entire related penalty computed on the underlying tax liability, even if that penalty has not yet been assessed (accruals). See IRM 20.1.2.2.4.1, Penalty Abatements and Re-assessments for more information.
- If RCA determines that a written statement is required because oral statement authority is exceeded, the taxpayer's statement must include the penalties involved, the applicable tax year(s), the reason for the request, and the taxpayer’s signature. If the facts given by the taxpayer do not meet reasonable cause, do not request a written statement simply because the amount is over ceiling, continue to run RCA through to determination. See IRM 20.1.1.3.1, Unsigned or Oral Requests for Penalty Relief, for further information.
- If RCA determines supporting documentation is required, request documentation that supports the reasonable cause claim (for example, medical records or hospital documentation). Documentation supporting the claim of reasonable cause is not limited to those requests that exceed OSA. The need for supporting documentation depends on the circumstances of the Reasonable Cause request. See IRM 20.1.1.3.6.5, Documentation, for further information.
- If RCA determines that the penalty should be abated and additional documentation is required, ask whether the taxpayer can fax the information while still on the telephone. If the taxpayer cannot fax the documentation, advise the taxpayer to either call back when able to fax it or submit the request in writing.
Suspend the RCA case so the next employee can access the determination. See IRM 20.1.1.3.1, Unsigned or Oral Requests for Penalty Relief, for further oral statement information.
Note:
If RCA denies the penalty relief request, advise the taxpayer they will receive a letter of determination within a couple of weeks and the letter provides them with a written explanation of the outcome of their request.
Note:
The BMFO RCA Tool assists with the reasonable cause requests on income tax forms 1065, 1120 and 1041. The tool also addresses FTP and FTF penalties on 94X forms when no FTD penalty has been assessed. The BMFO RCA tool is mandated for phones when taxpayer is requesting abatement of FTF / FTP penalties based on reasonable cause on Form 1065, U.S. Return of Partnership Income, Form 1120, U.S. Corporation Income Tax Return, and Form 1041, U.S. Income Tax Return for Estates and Trusts.
- If the taxpayer contacts the IRS before the penalties are assessed, it may be possible to consider the request and suppress the penalties. While RCA cannot be used for accounts where there is no TC 150 on the module, it can be used if there is a TC 150, but the penalties have not posted to the account. See IRM 20.1.1.3.6.7, Reasonable Cause Penalty Relief Request Prior to Penalty Assessment, for further guidance.
Additional penalty information:
Row If Then 1 A Federal Tax Deposit was applied to a different period than the taxpayer designated Move the deposits according to the taxpayer's designation.
2 Daily Delinquency Penalty applies
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ See IRM 21.7.7.6.23.1.6, Abatement Procedures, for more information. 3 Daily Delinquency Penalty for Employee Plan (EP) Returns and Form 8955-SSA applies ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ See IRM 21.5.11.9, Abatements/Adjustments on Form 5500/ BMF 8955-SSA Accounts/Direct Filing Entity (DFE), for more information. 4 The oral statement ceiling is exceeded See IRM 20.1.1.3.6.4, Oral Statement Ceiling Exceeded. 5 Penalty was caused by IRS error Abate the penalty. Oral statement ceiling does not apply.
- When a partner requests abatement of a partnership penalty for failure to file Form 1065, U.S. Return of Partnership Income, see IRM 20.1.2.4, Failure to File a Partnership Return - IRC 6698, and also refer to IRM 20.1.2.6.3, Penalty Relief, and IRM 21.7.4.4.2.7, Partnership Penalties.
- IRM 20.2, Interest, provides detailed interest instructions. Interest is mandatory unless there is a legal exception. Read and become familiar with the IRM 20.2, and use this IRM following the general interest procedures when answering telephone calls and related interest questions.
- IDRS Command Code (CC) PICRD can be used to explain credit interest to the taxpayer. CC PICRD provides a computation display of any computer-generated interest (TC 776) allowed on the refund.
- Penalty and Interest Explanation can be provided through IDRS CC PINEX. A PINEX explains how credit and debit interest was computed on an IMF account.
- A taxpayer may request an interest abatement because of an error or delay in performing a ministerial or managerial act. See IRM 20.2.7.5, IRC 6404(e)(1), Unreasonable Error or Delay in Performing a Ministerial or Managerial Act.
Requests for interest abatement received via phone cannot be accepted. Advise the taxpayer to submit a written request by filing Form 843, Claim for Refund and Request for Abatement, which can be obtained via IRS.gov, or by submitting signed correspondence that contains the same required information (e.g., name, taxpayer identification number, interest period in question, signature under penalties of perjury, and the reason(s) for the abatement, etc.) as shown on the Form 843. Advise the taxpayer to send the request to the service center that they sent their most recent return. Refer to 4 below for items that the taxpayer must include with his claim so that it is considered a complete claim.
Note:
This subsection does not apply to questions about computing or explaining interest. See IRM 20.2, Interest, for calculation information and any necessary explanation to the taxpayer.
Note:
If the taxpayer requests interest abatement because a payment was mailed on time but posted late by the IRS as late, treat the case as a payment date adjustment rather than a ministerial or managerial act and follow the guidance in IRM 21.5.8.4.2(2), Determining Credit Transfer Format.
Caution:
If Form 843 requests penalty and interest relief based on reasonable cause, follow IRM 20.1.1.3, Criteria for Relief from Penalties. Do not allow requests to abate interest based on reasonable cause. These requests do not meet the criteria for interest abatement under IRC 6404(e)(1) and must be disallowed in full. Refer to IRM 20.2.7.14, Request for Interest Abatement. Use the appropriate correspondence to notify the taxpayer of the interest abatement determination. If the request is disallowed, issue a disallowance letter that includes appeal rights. Refer to IRM 20.2.7.5.3 , Interest Abatement Correspondence, for additional guidance.
When you receive Form 843 requesting interest abatement, or acceptable signed correspondence, complete the following actions:
If TC 971 AC 660 is not present on CC TXMOD, input TC 971 AC 660 using the Form 843 received date as the transaction date. The TC 971 AC 660 documents receipt of the interest abatement claim.
Note:
Use TC 971 AC 660 only for Form 843 request for interest abatement. Do not use it for written requests accepted in place of Form 843.
Forward the request to the Interest Abatement Coordinator (IAC) responsible for the location where the delay or error occurred, following local procedures. Contact information for the Campus IACs is provided on the IAC Coordinator List.
Example:
If the request concerns an interest assessment made with an audit (TC 30X), close the case to Examination using activity code "2EXAM-IAC" .
Example:
If the request concerns an interest assessment made with an ASFR adjustment, close the case to Collection using activity code "2COLL-IAC" .
Example:
If the request concerns additional interest assessed due to an incorrect payoff, identify the area responsible for the incorrect payoff and forward to the proper IAC. Close the case with the correct activity code (e.g., "2-AM-IAC" , "2EXAM-IAC" , or "2COLL-IAC" ).
Exception:
Forward all Form 843, Claim for Refund and Request for Abatement, pertaining to Trust Fund Recovery Penalty (TFRP) accounts (MFT 55), to the correct TFRP campus found in SERP Who / Where - Trust Fund Recovery Penalty (TFRP) for further determination.
Exception:
Cases indicating Kwong v. United States are protective claims and should be processed in accordance with Exhibit 21.5.3-2 Examination Criteria (CAT-A)- General. Do not submit these claims to the Interest Abatement Coordinator.
An Interest Abatement referral to the IAC must include the following:
- A detailed description explaining when and how the IRS delay or unreasonable error occurred, and how it increased interest.
Supporting documentation, including correspondence, payoff letters, and other date-specific information.
Note:
If Form 843 is incomplete, follow the no consideration procedures in IRM 21.5.3.4.6.3, No Consideration Procedures.
Send copies of all supporting documentation for each assessment over ≡ ≡ ≡ ≡ ≡ ≡ ≡ when the taxpayer did not fully pay the liability in advance to:
Internal Revenue Service
CFO, Revenue Transactional Analysis Section
Kansas City Campus
ATTN: Chief, Revenue Transactional Analysis Section
Stop S-2 1035
333 W. Pershing Rd.
Kansas City, MO 64108Refunds of ≡ ≡ ≡ ≡ ≡ ≡ ≡ dollars or more do not generate systemically (TC 846). Prepare a manual refund using Form 3753, Manual Refund Posting Voucher. See IRM 21.4.4.5.2, Preparation of the Form 3753, Manual Refund Posting Voucher. If the taxpayer submitted Form 8302, Electronic Deposit of Tax Refund of $1 Million or More, see IRM 3.17.79.3.10.1, Direct Deposits of Tax Refunds of $1 Million or More, or Due to Financial or International Hardships.
Note:
An X- freeze is set when the module credit is ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ or more for IMF, or ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ or more for BMF. Once the X- freeze is set, a manual refund is required even if later account actions reduce the credit balance.
- Form 8485, Assessment Adjustment Case Record, is the worksheet employees use to record actions taken on taxpayer accounts. Cases may originate from taxpayer inquiries or in-house transcripts. Employees may also use other forms, notices, or transcripts when required by specific procedures.
Prepare Form 8485 as follows. Complete fields 1 through 4,17, and 18, and the following unnumbered boxes at the top of the form:
- The name of the Tax Examiner
- Employee number
- Blocking series
Complete all other fields as applicable:
- Use Section II to record secondary transaction codes.
- Use Section III and IV to record the correct credit or item reference numbers.
Note:
If TC 340 or TC 341 is present on the account, enter the interest-to-date in the center of the bottom margin.
- To reestablish modules moved from the Master File (MF) to the Retention Register, input Command Code (CC) IMFOLB for Individual Master File (IMF) accounts or CC BMFOLB for Business Master File (BMF) accounts. See IRM 21.2.2.5, Retention Register Research, and IRM 3.17.21.7, Reestablishment of Retention Register Accounts, for additional guidance.
When a module is restored from the Retention Register, the system sets "G" and "I" freezes on the module. These freezes prevent MF from computing Failure to Pay (FTP) penalty and Interest.
Row If And Then 1 Your adjustment creates a balance due the case shows imminent assessment or collection statute expiration - Assess FTP and interest within ten years from the assessment date of the unpaid tax.
- Refer to the Statute Function
Assess penalties and interest when appropriate.
Row If And Then 1 TC 150 is posted to the restored module - Input Command Code (CC) REQ54 with TC 340 to assess the correct amount if interest.
- See IRM 20.2, Interest, for detailed information.
2 The restored module does not contain a TC 150 a return is input to generate a TC 150 - Monitor the account until the TC 150 posts.
- Request Notice Review to pull, correct, and mail the MF notice during the appropriate cycle so it reflects the assessed interest and penalties.
- Refer to IRM 20.2, Interest, and IRM 20.1, Penalty Handbook, for further procedures.
- Do not input adjusting entries to credit adjustment codes on Retention Register modules.
Use caution when entering hold codes (HC). Some rules to remember are:
- Do not hold notices for taxpayers entitled to refunds unless specifically excluded by separate IRM instructions. Write or call the taxpayer to clarify the notice, if necessary.
- Transfer any credit with an undetermined disposition to Unidentified or Excess Collections, as appropriate.
Take the required action to bring the module to a zero or balance due condition.
Note:
If using a hold code creates a freeze condition, resolve the freeze after the adjustment posts to avoid delaying resolution of the account. For example, the HC "1" sets a -K freeze. If it is not released and a credit balance remains, the refund will be frozen. Input an adjustment (290 .00 HC "0" ) to release the credit and bring the balance to zero.
- Use HC "0" if no other HC applies.
The HC field on the Command Code ADJ54 is required. If the adjustment does not otherwise require a HC, input a HC "0" . For more information, see Hold Codes, in Document 6209, Section 8C.2-3, Master File Codes.
Note:
A CP 21A, Data Processing Adjustment Notice, or CP 22A, Data Processing Adjustment Notice, is not issued if the account balance is zero and an adjustment (Command Code ADJ54) for TC 290.00 is input with ONLY item reference numbers (IRN) changing numerical data - NOT TAX (e.g., IRN 886, 887, 888, 889, 892, 895, 896. etc.). However, a CP 21A / CP 22A is issued if the account was in balance due status before the adjustment was input. If hold code 3 was used, issue correspondence to the taxpayer if a letter was required and a notice was held.
- Use Priority Codes (PC) to post adjustments (Doc Code 47 or 54) to the MF when specific account conditions exist. See Priority Codes, in Document 6209, Section 8C.2-4, Master File Codes for additional guidance.
Use Posting Delay Codes (PDCs) one through six to control the posting sequence when multiple transactions are required to adjust an account. See IRM 21.5.8, Credit Transfers, for instructions on using posting delays of one through six cycles for credit transfers.
Note:
Input transactions do not post to MF until the specified number of posting cycles has elapsed after the first transaction posts.
PDCs apply to IMF, BMF, and IRAF transactions in the following IDRS programs:
- ADJ54 (Doc. Code 54)
- INCHG, BNCHG, EOCHG (Doc. Codes 53, 63, 80, and 81)
- FRM77 (Doc. Code 77 and 78)
- The PDC is not posted with the transaction and does not appear with the IDRS pending transaction. The pending (PN) MF posting cycle shown on the IDRS status transaction is extended to reflect the PDCs.
- Use the applicable functional IRM chapter for instructions on when and how to enter Credit Reference Numbers (CRNs), Abstract Codes, and Item Reference Numbers (IRNs) for specific adjustment types. See Item Adjustment Codes and Credit Reference Numbers, in Document 6209, Section 8C.3, IRS Processing Codes and Information for a complete list.
- For Form 1120S, U.S. Income Tax Return for an S Corporation, IRN 886, Taxable Income is called "Ordinary Income / Loss Amount" .
- For definitions of the Abstract Numbers used with MFT 03, see Form 720, Quarterly Federal Excise Tax Return.
- For Form 4720, Return of Certain Excise Taxes on Charities and Other Persons Under Chapters 41 and 42 of the IRC, the sum of IRNs 151, 152, 153, 154,182, and 183 must equal the TC 29X amount.
For Form 941, Employer’s QUARTERLY Federal Tax Return, and Form 944, Employer’s ANNUAL Federal Tax Return, refer to IRM 21.7.2.4.1, Item Reference Numbers (IRNs) and Credit Reference Numbers (CRNs) — Employment Taxes. For adjusting Form 943, Employer’s Annual Tax Return for Agricultural Employees, see paragraph 2 in IRM 21.7.2.4.6.3(2), Form 943-X, Adjusted Employer's Annual Federal Tax Return for Agricultural Employees or Claim for Refund. For adjusting Form 945, Annual Return of Withheld Federal Income Tax, see IRM 21.7.2.4.8(6), Form 945, Annual Return of Withheld Federal Income Tax.
Exception:
If the TC 150 does not equal the posted IRNs on CC TXMODA, see IRM 21.7.2.4.1.3, IRNs Do Not Equal TC 150.
For Form 940, Employer’s Annual Federal Unemployment (FUTA) Tax Return, use the following IRN Codes:
Enter "W" followed by the applicable State code for wage adjustments. A State code is the official postal service state abbreviation.
- Use up to 53 different state codes with the IRN code "W" . This IRN code adjusts the taxable wage amount in the MF and generates a credit reduction if the state and tax year shows a reduction.
Enter "T" followed by the applicable state code to identify the portion of the tax increase or decrease attributable to each state.
- For IRAF (MFT 29) adjustments, the total of Abstract Codes 160,162,194, 195, 233, 235, 236, and 237 must equal the TC 29X amount.
- If an adjustment includes IRN 221 or 222 also input TC 34X.
Use IRNs 079 and 999 with a reference amount of zero. Reference amounts for IRN 887 do not represent dollars and cents and cannot exceed the value entered in "nn" format. See IRM 21.6.1.6, Exemption / Dependent Procedures, for more information.
Note:
Oral statement authority may be used for IRN adjustments when the request meets IRM 21.1.3.20, Oral Statement Authority. If the request does not meet those requirements, obtain the request in writing.
Resolve al identified l issues before closing the case. For telephone contacts involving collection issues, follow IRM 5.19.1, Balance Due, to collect any balance due. If missing returns are involved, see IRM 5.19.2, Individual Master File (IMF) Return Delinquency. For correspondence cases, follow procedures in IRM 21.3.3, Incoming and Outgoing Correspondence / Letters. Review all taxpayer correspondence to verify that all required adjustments have been completed and the taxpayer’s issue has been resolved.
Exception:
Accounts Management (AM) no longer negotiates payments on balance due accounts or sets demand dates for missing / unfiled returns. For AM telephone contacts, after all account actions have been taken, if a balance due remains on the account or an unfiled return / TDI, follow guidance in IRM 21.1.1.3.1, Accounts Management (AM) Customer Service Representative (CSR) Duties Handling Accounts with Balance Due / Missing Returns, for more details.
- Input manual adjustments to penalties and interest only when required. IDRS generates penalty and interest increases / decreases for most adjustments.
- Explain penalties or interest to the taxpayer.
- Inform the taxpayer of the date used to compute any balance due.
- Include any penalty and interest accruals when computing the balance due.
Note:
The word case pertains to the type of inquiry received. Taxpayer initiated contacts by telephone require resolution of ALL account issues. Taxpayer initiated contacts by correspondence require resolution of issues raised by taxpayers in their inquiries. If it becomes necessary to call the taxpayer in order to resolve an issue addressed in the correspondence, then the employee must address any further issue(s) raised by the taxpayer during the call.
- Do not request the original return(s) if sufficient information is available to verify the request for adjustment.
Take any of the following actions as necessary:
- Obtain further information from the taxpayer.
- Request returns from Files or order transcripts.
Research IDRS or other applicable systems (e.g., Correspondence Imaging Inventory).
Note:
Taxpayers have the option to electronically amend the current tax year and two prior year Form 1040, U.S. Individual Income Tax Return, and Form 1040-SR, U.S. Income Tax Return for Seniors. The CII cases created by Account Management Services (AMS) do not contain a digital CII image. The amended return documentation is reviewed via the MeF Return Request Display (RRD) application. These cases can be identified on IDRS by Control Base Category Codes. Category Code MEFP and identifies MeF Form 1040-X cases assigned to Submission Processing and Category Codes MEFA (Form 1040-X MeF), MEFC (Carryback Form 1040-X MeF), MEFI (International Form 1040-X MeF) and MEFR (International Carryback Form 1040-X MeF) for Form 1040-X cases assigned to Accounts Management.
- Research IRS publications.
- Research the Internal Revenue Code.
- Research other IRMs, etc.
- Get technical assistance, if needed.
- If a request for tax decrease is received and there is a TC 606 on the module, the TC 606 automatically reverses when the TC 291 is input. See IRM 21.5.8.4, IDRS Guidelines for Credit Transfers.
- Do not refer a case to another campus or call site unless an IRM specifically instructs you to do so. Generally, the site that receives the taxpayer’s contact works the case.
Close the control base when the case is resolved.
Note:
If all case actions are complete but an IRM requires monitoring to verify proper posting, close the case and establish an IDRS monitor control base using category code "MISC" and the current date as the received date.
The IRS issues an adjustment notice when it takes action on a taxpayer's account. The notice (CP 21A, Data Processing Adjustment Notice, or CP 22A, Data Processing Adjustment Notice) explains the action taken.
Note:
A CP 21A / CP 22A is not issued if the account balance is zero and an adjustment (Command Code (CC) ADJ54) for TC 290.00 is input with ONLY item reference numbers (IRNs) changing numerical data - NOT TAX (e.g., IRN 886, 887, 888, 889, 892, 895, 896, etc.,). However, a CP 21A or CP 22A is issued if the account was in balance due status before the adjustment was input. If hold code 3 was used, issue correspondence to the taxpayer if a letter was required and a notice was held.
- See IRM 21.6.7.4.1, Source and Reason Codes – CP 21A / CP 22A Notices, for additional information. Document 6209, IRS Processing Codes and Information, provides the language generated by the Source Codes, Section 8C.2-1, and Reason Codes, Section 8C.2-2.
Enter a source code (SC) and at least one reason code (RC) on Command Code (CC) ADJ54 when you input:
- TC 290 for an amount, with or without a secondary transaction or credit / item reference numbers.
- TC 290 for zero with a secondary transaction and / or credit / item reference numbers.
- TC 290 for zero to disallow a claim.
- If the Correspondence Imaging Inventory (CII) Indicator appears on the lower left-corner of the ADJ54 screen, a case is already open on CII. Before taking action, contact the employee or unit with the open control.
Use Blocking series to identify the type of adjustment being processed. See Adjustment Blocking Series, in Document 6209, IRS Processing Codes and Information, Section 4.14, for the blocking series used with account adjustments.
Note:
Blocking Series (BS) consists of three digits; however, Command Code (CC) ADJ54 accepts only the first two digits. IRM procedures show only the first two digits. After the adjustment posts, IDRS displays the complete three-digit Blocking Series in the Document Locator Number (DLN). For example, if the IRM instructs you to use BS 05 (IMF—Tax, Penalty, Interest, or Freeze Release Without Original IMF Returns), the adjustment DLN may post with a Blocking Series from 050 through 059.
The original return is not included in the case file if both of the following conditions exist:
- Reason Code 097, and
- Blocking Series 99
- Use Blocking series 99 with reason code 097 for Innocent Spouse Relief, Separation of Liability and Equitable Relief cases. This combination prevents issuance of CP 55, Notice to Refile Return, when the tax period is more than 10 years old.
Use these procedures to reprocess returns that posted to the wrong account or tax period. Before obtaining the original return, complete all applicable research and follow the required procedures for reprocessing the return to the correct account or tax period. This may include recovering an erroneous refund. See IRM 21.4.5, Erroneous Refunds. The return(s) may involve the current or a prior tax year and may be subject to statute or penalty considerations. Before requesting a copy of the return, determine whether the return can be reprocessed using the IDRS command codes described in IRM 21.5.2.4.23.11, Reprocessing "Dummy" Returns.
Note:
If a return has never been processed (e.g., has not posted to another year or TIN), attach a Form 1725, Routing Slip, or local routing slip, and forward the return as received to Submission Processing. Ensure the IRS received date is entered on the return. If a Correspondence Imaging Inventory (CII) image is used and the return is signed, use the stamp edit tool on CII and notate, "CII IMAGE - Do not correspond for signature" on the return. Refer to IRM 21.5.1.5.5, Processing / Reprocessing CII Tax Returns, for more information about CII returns.
Note:
If the return is signed in a SBSE (CSTO Centralized Specialized Tax Operation) scanned case, open the file in Adobe Acrobat Pro and add "CSTO (OR SBSE) SCANNED IMAGE- Do not correspond for signature" below the signature field and case information (taxpayer name, TIN, tax year, etc.) in the upper-left corner of the first page.
Note:
When reprocessing cases with TPP indicators or MFT 32 accounts, follow procedures in IRM 21.5.6.4.9, E- Freeze.
Exception:
Taxpayers have the option to electronically amend the current tax year and two prior year Form 1040 and Form 1040-SR returns that were originally e-filed through the Modernized e-File Return (MeF) application. The CII cases created by Account Management Services (AMS) do not contain a digital CII image. Returns that are printed / saved from the MeF Return Request Display (RRD) application and sent for processing are annotated with "MeF Return - Do not correspond for signature" below the signature line. Any annotations are made using the Adobe Acrobat Pro software and the annotated documentation must be attached to your CII case. If the Adobe Acrobat Pro software is not available to you, print the amended return documentation from the MeF / RRD application and have the document associated with your CII case via a CIS association sheet.
Exception:
Exempt Organizations (EO) are exempt from including the CII Case ID number and CII stamp - "Do not correspond for signature" as their returns are scanned for public inspection. Complete all other edits.
If you identify an IMF return that must be reprocessed while staffing the AM toll-free telephone lines, complete any required actions before preparing a Form 4442 /e-4442 Inquiry Referral. Advise the taxpayer that the IRS will contact them within 30 days. Forward the completed Form 4442 /e-4442 Inquiry Referral to the campus AM paper function within your directorate (unless IRM specific procedures apply). If your campus AM paper function no longer has Submission Processing, forward the Form 4442 /e-4442 Inquiry Referral as shown below:
- Andover – forward the form to Kansas City
- Atlanta - forward the form to Kansas City
- Brookhaven – forward the form to Austin
- Fresno - forward the form to Kansas City
- Memphis – forward the form to Kansas City
- Philadelphia – forward the form to Austin
- Puerto Rico - forward the form to Kansas City
- International - forward the form to Austin
Note:
If you identify a BMF return that must be reprocessed while staffing the AM toll-free telephone lines, refer to IRM 21.3.5.4.3(7) & (8), How to Transmit/Route Referrals to Another Office/Function.
Exception:
For mixed entities, follow the procedures in IRM 21.6.2.4.4, Mixed Entity Procedures, and for scrambled SSN cases, see IRM 21.6.2.4.5, Multiple Individuals Using the Same TIN.
Exception:
For Form 1040-PR /Form 1040-SS, route inquiries concerning Form 1040-PR and Form 1040-SS to the IMF International Department at the Philadelphia Campus via e-4442.
- Any returns involving taxes or payments of $1 billion or more requires special processing and are forwarded to the Philadelphia Campus, Attention TPR 503 - Drop Point - 3-L08.154. For more information, refer to IRM 21.7.12.6.2, Procedures for Individual Taxpayer NMF Accounts Of $1 Billion or More - Overview.
If a return unposts or posts to a incorrect account, reprocess it to the correct account. If an incorrect refund was issued from the account,see IRM 21.5.2.4.23.10, Moving Refunds, and IRM 21.4.5, Erroneous Refunds.
Reminder:
Before reprocessing the return or moving a refund, review all related accounts (e.g., secondary TINs and receiving account) prior to reprocessing the return or moving any refunds.
Correct the following conditions before reprocessing the return to prevent unprocessable conditions identified during original processing. If an unprocessable condition remains, Submission Processing returns the document to the originating employee for correction. Before forwarding the return to Submission Processing, verify the following:
- Canceled DLNs
- Posting to an incorrect TIN
- Posting to an incorrect tax period
After completing all required edits, forward the return to the Batching function for reprocessing as an original return. If the return does not post, Submission Processing returns it to the employee who submitted it for reprocessing.
Reminder:
Carefully prepare the returns for reprocessing. Verify that all required edits and edit marks have been entered before forwarding the return to the Batching function.
Note:
Clear IMF re-input and reprocessable statute imminent documents through the local Statute Unit prior to following procedures in IRM 21.3.3.3.5, Submission Processing Consolidation (Rampdown). When forwarding a statute imminent return, notate on the routing slip the received date of the case that created the need for reprocessing the document (e.g., 2005 -2012 needs reprocessing – part of Mixed Entity DUPF with received date MM/DD/YYYY).
Control each return or block of reprocessable documents entered through the Batching function by using Form 3893, Re-Entry Document Control, for IMF cases or a Form 13596, Reprocessing Returns, for BMF. Complete these forms and place them on the top of the documents being reprocessed. See Exhibit 21.5.2-1, Preparing Form 3893, Re-Entry Document Control, and Exhibit 21.5.2-2, Preparing Form 13596 – Reprocessing Returns, for complete instructions on preparing these forms.
Note:
Use one Form 3893 for multiple documents from the same block unless a document is not reprocessable.
When reprocessing previously processed documents, use the following guidance:
Row If Then 1 The module contains a TC 150 Do not reprocess a return to that module. 2 The module contains Document Codes 51 or 54 Do not reprocess a return to that module. 3 The return or document did not post. Re-enter as a Reinput document. 4 The return or document unposted. Re-enter as a Nullified Unpostable document. BMF only – Consider FTD penalties carefully before the following returns are reprocessed:
- Form 941, Employer’s QUARTERLY Federal Tax Return
- Form 943, Employer's Annual Federal Tax Return for Agricultural Employees
- Form 944, Employer's ANNUAL Federal Tax Return
- Form 945, Annual Return of Withheld Federal Income Tax
- Form 940, Employer’ s Annual Federal Unemployment (FUTA) Tax Return
Refer to IRM 20.1.4, Failure to Deposit Penalty, for more information.
- Electronic return printouts may be reprocessed to the correct account or tax period.
Request graphic printouts of Individual Master File (IMF) and Business Master File (BMF) returns filed through Modernized e-File (MeF) by using the Return Request Display (RRD) through the Employee User Portal (EUP) or Command Code (CC) TRPRT. See IRM 21.2.4.3.23, Electronic Returns, and IRM 21.6.6.2.25, Electronic Filing System (e-file), for more information on e-file. The TRPRT graphic is available regardless of where the return was filed. More information on Command Code TRPRT is located in IRM 21.2.2.4.4.6, TRDB CC TRPRT (Tax Return Print) Input.
Note:
Many BMF returns are also available through the Employee User Portal (EUP) as part of the Modernized e-File (MeF). Refer to IRM 21.2.1.22, Modernized e-file (MeF / TRDB), and to IRM 3.42.4.7.1, Modernized e-File (MeF) Programs, for more information.
- The TRPRT print is not the original return and is labeled "TRPRT PRINT DO NOT PROCESS" . Use the TRPRT print to reprocess the electronic return.
- Before forwarding the print for reprocessing, line through the "TRPRT PRINT DO NOT PROCESS" . See IRM 21.5.2.4.23.7, Coding and Editing Procedures for additional editing procedures.
- If TC 976 is a MEF partnership return (DLN begins with 93) with 100 or more parameters, see IRM 21.7.9.4.10.1, TC 976 Return Intended as Original.
- Taxpayers may electronically amend the current tax year and two prior tax years Form 1040 and Form 1040-SR. Although the CII case does not contain a digital image, the amended return remains available through the MeF Return Request Display (RRD). Before forwarding the amended return for processing, line through "e-file GRAPHIC print - DO NOT PROCESS." See IRM 21.5.2.4.23.7, Coding and Editing Procedures, for additional editing instructions.
When reprocessing an amended or subsequent return as the original return, complete the following steps:
Row If Then 1 Form 1040-X, Amended U.S. Individual Income Tax Return The return must be signed, forms and supporting schedules attached, and dependents listed. 2 Form 1040-X has the same information in column A and column C Transfer the information to the Form 1040 or Form 6114, Prior Year and Conversion Form 1040 Edit Sheet. 3 Form 1040-X has only column C completed Transfer the information to the Form 1040 or Form 6114, Prior Year and Conversion Form 1040 Edit Sheet. 4 Copy B of Form W-2, Wage and Income Tax Statement is attached The return must be signed, forms and supporting schedules attached, and dependents listed. Note:
These Form 1040-X, Amended U.S. Individual Income Tax Return, procedures apply only when the amended return is the only return filed and is being reprocessed as the taxpayer's original return. Before converting the amended return to an original return, complete a thorough search for the original return under all related or invalid TINs.
To prepare the return for transcription, transfer the following information to the current Form 1040, U.S. Individual Income Tax Return, or Form 6114, Prior Year and Conversion Form 1040 Edit Sheet, and attach all current schedules behind the Form 1040.
- If the DLN is valid, transfer it from the subsequent Form 1040. See IRM 21.5.2.4.23.3, DLNs Used for Reprocessing Documents, to determine if the DLN is valid or if a new DLN is required.
Recopy the DLNs.
Note:
Some campuses color-code DLNs. If the year is present on Form 1040, recopy the DLN using the color according to local procedures. If the year is not present on Form 1040, recopy the DLNs using the correct color. Refer to Exhibit 21.5.2-1, Preparing Form 3893, Re-Entry Document Control.
- Enter positive income not supported by a schedule or Form W-2 on the OTHER INCOME line of the prepared Form 1040.
- Do not verify withholding amounts of ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡.
- If a separate to joint return is being processed as the original, verification of the withholding previously allowed on the account being backed out is not needed. Select on the Form 3893 Remarks area: "Withholding of $XXXX allowed from separate return."
- Staple the Form 1040-X and all necessary forms to the back of the Form 1040.
- Edit the correct tax period ending at the top of Form 1040.
- For BMF returns, transfer information on returns filed on mag-tape to the correct form for processing to the correct EIN and Tax Period. Attach a photocopy or printout of mag-tape return behind the form as backup (with DLN voided).
- When reprocessing employment tax forms, see IRM 20.1, Penalty Handbook, for instruction on possible manual adjustments to deposit penalties and "J" coding of return.
When reprocessing a document, use the original document locator number (DLN) whenever possible.
Exception:
All BMF returns being reprocessed must receive a new DLN. Line through the original DLN following IRM 21.5.2.4.23.7, Coding and Editing Procedures.
- If the original DLN is canceled, and is still correct for the document being reprocessed, reuse it. Erase any line through. If the DLN remains illegible, rewrite it above the original and include the list year digit. See Document Locator Number, in Document 6209, IRS Processing Codes and Information, Section 4.2.
In certain instances, the original DLN is not valid for reprocessing.
The original DLN is incorrect for the document to be reprocessed. See IRM 3.10.73.8, Assignment of Document Locator Number (DLN), and applicable subsections for more information on when to request a new DLN. Line through the original DLN with a single stroke. If the return was filed electronically, also line through the DLN on Form 8453, U.S. Individual Income Tax Transmittal for an IRS e-file Return. Request a new DLN if any of the following apply:
Example:
You are reprocessing a Form 1040-X as an original Form 1040. Because the Form 1040-X DLN is not valid for Form 1040 processing, request a new DLN.
- The document was processed at another campus using a DLN reserved for that campus.
- The return was filed early and posted to the wrong tax year.
- The Document Code is 47, 51, or 54.
- The document was filed electronically.
- Reprocessed documents are input as non-remittance. If a payment was received with the original document, follow IRM 21.5.8, Credit Transfers.
Forward any reprocessable return for which the assessment statute expiration date (ASED) has expired or is imminent, to the Statute Unit. Do not use Form 3893, Re-Entry Document Control, to reinput returns when the statute for assessing tax expires within 6 months, or Form 13596, Reprocessing Returns, to reprocess returns when the statute for assessing tax expires within 90 days. Do not abate tax on the incorrect module before forwarding the case to the Statute Function.
Note:
For specific reprocessing conditions applicable to Mixed Entity / Scrambled cases, see IRM 21.6.2.4.8, Tax Year Account Move Conditions Applicable for MXEN, SCRM, SSA2 and NMRG Cases.
- When forwarding a statute imminent return, include the received date of the case that created the need for reprocessing the document (e.g., 2005 needs reprocessing – part of Mixed Entity DUPF with received date MM/DD/YYYY).
See IRM 25.6, Statute of Limitations, and Document 7368, Basic Guide for Processing Statute Cases. IRM 25.6, contains Assessment Statute Expiration Date (ASED), Refund Statute Expiration Date (RSED), and Collection Statute Expiration Date (CSED) procedures.
Note:
Clear BMF reinput and reprocessable statute imminent documents through the local Statute Unit prior to following transshipping procedures.
Note:
Clear IMF re-input and reprocessable statute imminent documents through the local Statute Unit prior to following procedures in IRM 21.3.3.3.5, Submission Processing Consolidation (Rampdown). When forwarding a statute imminent return, notate on the routing slip the received date of the case that created the need for reprocessing the document (e.g., 2005 needs reprocessing – part of Mixed Entity DUPF with received date MM/DD/YYYY).
When a return has a renumbered Document Code 47 and is posted to an incorrect TIN or tax period, complete the following actions:
- Secure the return and Form 5344, Examination Closing Record, from Files.
- Input the necessary adjustments to the tax module and prepare the proper reprocessing form to reprocess the return using the original DLN. Form 3893, Re-Entry Document Control, is used for reprocessing an IMF return and Form 13596, Reprocessing Returns, is used to reprocess a BMF return. Refer to Exhibit 21.5.2-1, Preparing Form 3893, Re-Entry Document Control and Exhibit 21.5.2-2, Preparing Form 13596 – Reprocessing Returns for additional information on these forms. If the return is within 6 months of the ASED, follow IRM 21.5.2.4.23.4, Statute Imminent Documents.
- Forward the Form 5344 to Examination Classification to determine if the audit adjustment is valid on the new module.
To forward the Form 5344 to Examination Classification:
- Use the Form 1725, Routing Slip, and show the correct TIN or tax period.
- State the incorrect TIN or tax period is adjusted or zeroed out, as applicable.
- The case is to remain controlled to Accounts Management until selected by Examination.
- If the case is not selected by Examination, forward the Form 5344 to the Automated Non-MF Accounting Function to correct the audit assessment and retain the 23C date.
- Exam should return the referred case to Accounts Management within five (5) business days. If the case is not returned, follow-up with Examination to secure the case.
- The Discriminant Function (DIF) score is used to identify superseding returns filed on or before the original or extended due date for possible Examination review. See (3) for CAT-A criteria. Exhibit 21.5.3-2, Examination Criteria (CAT-A)- General, provides superseding returns are considered for CAT-A. Amended returns, including superseding returns filed before the original or extended due date, are not considered for DIF score and are considered for CAT-A criteria because they bypass DIF scoring. Instead, evaluate them using the CAT-A criteria in Exhibit 21.5.3-2, Examination Criteria (CAT-A)- General, and Exhibit 21.5.3-3, Examination Criteria (CAT-A)- Credits. For BMF procedures, see IRM 21.7.9.3.3.1, Business Master File (BMF) Superseding Tax Return Processing Considerations for BMF procedures.
- A superseding return that was not processed as an original return bypasses DIF scoring if it was filed by the original or extended due date.
Forward returns that bypassed DIF scoring to Examination Classification only if one or more of the following conditions apply:
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Example:
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Exception:
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
- ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Exception:
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
- ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Adjust superseding returns that do not meet CAT-A criteria when CC AMDISA status is 09 or higher. After completing the adjustment, forward the return to the open AIMS field group. See Exhibit 21.5.3-1, Claim Processing with Examination Involvement, pertaining to AIMS status 09 or greater with -L freeze. After adjusting the account for the tax increase or decrease, or credit increase or decrease, and adjusting any previously assessed penalties, route the returns to Examination classification when the returns have bypassed DIF scoring and meet the criteria above in (3). Use priority code 1 unless Item Reference Number (IRN) 871 is required. If IRN 871 is required, use priority code 2. See IRM 20.1.2.2.6.3, Wrong Return Posted First. Do not use a hold code unless required to issue a manual refund or separate IRM instructions specifically provides guidance on input of hold code.
Exception:
All International Identity Theft (IDT) cases are referred to Exam using CAT-A referral reason "INTERNATIONAL IDT BYPASS DIF" instead of HQ Reserved 6.
Exception:
All Domestic Identity Theft (IDT) cases are referred to Exam to CAT-A referral reason "IDT DIF BYPASS" instead of HQ Reserved 6.
ASFR cases are forwarded to the Collection function.
Exception:
IRC 6020(b) returns are handled by reviewing IRM 21.5.3.4.10, Returns Prepared Under IRC 6020(b) - Substitute for Return (SFR).
A return must be complete before being sent for reprocessing. Most reprocessable returns have already completed Submission Processing and are complete. If required information is missing (for example, a signature, schedule, or form) and the IRS has not previously requested it, complete the following steps before forwarding the return for reprocessing:
Reminder:
If a Form 1040-X is submitted and needs to be reprocessed, transfer the figures to a Form 1040 before submitting the return to Submission Processing.
Contact the taxpayer by telephone or correspondence for the missing information.
Reminder:
Check the Correspondence Imaging Inventory (CII) for related cases. Any missing information, such as schedules, may be located on another CII case.
- Suspend the case for 45 days (or 70 days for overseas taxpayers).
- If the missing information is received, complete the necessary edits and forward for reprocessing.
If the missing information is not received, complete the required edits, and enter any applicable Computer Condition Codes (CCC) "horizontally in the upper-center portion of the filing status section of the return" for (tax year 2017 and prior) and to the blank area below "Spouse was born" section for (tax year 2018) prior to forwarding for reprocessing. For tax years 2019 and later, use a blank space at the end of the first page of the return. Enter "Reprocessable" on the top of the return prior to forwarding the return. Refer to Computer Condition Codes, for a listing of the different CCCs.
Note:
CCC "3" is used to freeze overpayments on IMF returns when the necessary signatures are missing. CCC "3" is also used to prevent credit interest on BMF returns. Code incomplete IMF returns with CCC "U" to prevent the generation of credit interest.
Edit all returns carefully using red for IMF and TEGE returns and dark green for BMF returns.
Note:
When reprocessing a CII return, edits may be made electronically prior to forwarding to Submission Processing. Refer to IRM 21.5.1.5.5, Processing / Reprocessing CII Tax Returns.
When reprocessing a BMF return:
Attach a completed Form 13596, Reprocessing Returns. Refer to Exhibit 21.5.2-2, Preparing Form 13596, Reprocessing Returns, for further editing information.
Note:
If a return has never been processed (e.g., has not posted to another year or TIN), attach a Form 1725 Routing Slip, or other local routing slip, with the notation "Process as Original" and forward the return as received to Submission Processing. Ensure the IRS received date is entered on the return (See paragraph 3(d) Note below for further information about the received date). If a Correspondence Imaging Inventory (CII) image is used and the return is signed, use the stamp tool or Text tool in the CII Document Viewer in CII and notate,"CII IMAGE - Do not correspond for signature" on the return and place the CII case ID in the upper left corner on the first page of the return. When reprocessing a return that was e-filed through the Modernized e-File Return (MeF) / Request Display (RRD) application, the notation of "MeF Return-Do not correspond for signature" should be used instead of "CII IMAGE - Do not correspond for signature" . Line through "e-file GRAPHIC print - DO NOT PROCESS" at the top of the first page prior to forwarding the document for reprocessing. Refer to IRM 21.5.1.5.5, Processing / Reprocessing CII Tax Returns, for further information about CII returns. When reprocessing a BMF return that was e-filed, the Correspondence Imaging Inventory (CII) image is used and the return is signed, use the stamp tool or Text tool in the CII Document Viewer in CII and annotate "CII IMAGE - Do not correspond for signature" below the signature line. If the return is signed in a SBSE (CSTO Centralized Specialized Tax Operation) scanned case, Use Adobe Acrobat Pro to add "CSTO (OR SBSE) SCANNED IMAGE - Do not correspond for signature" below the signature field and the (case info, etc.) in the upper left corner on the first page of the return.
- TIN – if applicable, circle an incorrect TIN and enter the correct information above the circle.
- If the return was "G" coded, circle out the "G" code. Circle out any other miscellaneous edits that are no longer necessary, such as annotations referencing duplicate, amended, or similar statements.
Edit the received date and X out any incorrect received dates if necessary. A received date is required on all reprocessed returns. See IRM 21.7.9.4.1.1, Transcript (TRNS) 193 Involving Reprocessing Returns, for more information about the received date.
Note:
If a stamped date is missing, handwrite the date (based on envelope stamp date, DLN, etc.,) in the middle of the return. State the IRS received date above the date written. Refer to IRM 21.5.1.4.2.4, Received Date -Determination for more guidance.
Circle out the paid preparer information on Form 1041, Form 1065, Form 1120, Form 1042, Form 709 ,Form 709-NA , and Form 1120-S if the "No" box is checked; neither box is checked; or both boxes are checked.
Note:
If the TC 976 is a MEF partnership return (DLN begins with 93) with 100 partners or more, edit the return with Computer Condition Code (CCC) 6, as described in 1(d) to ensure the Failure to File Electronically penalty is not assessed see IRM 21.7.4.4.2.8.1.1, Large Partnership Penalty for Failing to File Electronically, for more information on this penalty.
Line through the DLN.
- Tax Period – X out any incorrect tax period.
Place the tax period in the upper right‐hand corner of the first page in "YYYYMM" format.
Exception:
Current year returns do not need the tax period edited onto the return, unless the tax period is incorrect.
- No other edits are required.
- Forward to Submission Processing.
When reprocessing an IMF return:
Attach a completed Form 3893, Re-Entry Document Control, to the front of the document. Refer to Exhibit 21.5.2-1, Preparing Form 3893, Re-Entry Document Control.
Note:
Form 3893 can only be used for reprocessing a return with a valid DLN, as outlined in IRM 21.5.2.4.23.3, DLNs Used for Reprocessing Documents. If the DLN is not valid, complete all necessary edits and forward to Submission Processing using local routing slip.
Note:
If a return has never been processed (e.g., has not posted to another year or TIN), attach a Form 1725, Routing Slip, or local routing slip, with the notation "Process as Original" and forward the return as received to Submission Processing. Ensure the IRS received date is entered on the return. If a CII image is used and the return is signed, use the stamp tool or Text tool in the CII Document Viewer in CII and notate, "CII IMAGE - Do not correspond for signature" on the return and place the CII case ID in the upper left corner of the first page of the return. Refer to IRM 21.5.1.5.5, Processing / Reprocessing CII Tax Returns, for more information about CII returns.
Note:
If the return is signed in a SBSE (CSTO) scanned case, Use Adobe Acrobat Pro to add "CSTO (OR SBSE) SCANNED IMAGE - Do not correspond for signature" below the signature field and the (case info, etc.) in the upper left corner on the first page of the return. If applicable, if the DLN is not on the return, manually input the DLN and line through the TC 976/977 DLN top-right corner of page 1.
Reminder:
Notate CII Case ID in the top-left corner of the first page of the return; Line through the TC 976/977 DLN top-right corner of page 1, only if the DLN is invalid; Circle in red any references to the return being “Amended”, “Copy”, or “Duplicate”, including the “X” in the Form 1040-X title; Line through e-file GRAPHIC print – DO NOT PROCESS (if applicable); Notate the correct tax year (YYYYMM) to the right of the preprinted year (if applicable); Notate entity info, including Name, Address, & TIN as necessary.
Exception:
Exempt Organizations (EO) are excepted from including the CII Case ID number and CII stamp - "Do not correspond for signature" as their returns are scanned for public inspection. Complete all other edits.
Caution:
Taxpayers have the option to electronically amend the current tax year and two prior year Form 1040 and Form 1040-SR returns that were originally e-filed through the Modernized e-File Return (MeF) application. The CII cases created by Account Management Services (AMS) do not contain a digital CII image; however, the documentation remains available within the MeF Return Request Display (RRD) application. Make annotations using the Adobe Acrobat Pro software. If the Adobe Acrobat Pro software is not available to you, print the amended return documentation from the MeF / RRD application and have the documents associated with your CII case via a CIS association sheet. When reprocessing a return from MeF / RRD, be sure to line through "e-file GRAPHIC print - DO NOT PROCESS" prior to forwarding the document for reprocessing and annotate with "MeF Return - Do not correspond for signature" below the signature line, along with the CII Case ID in the upper left corner on the first page of the return. Refer to IRM 21.5.1.5.5, Processing/Reprocessing CII Tax Returns, for more information about CII returns.
Caution:
Form 1040-A and 1040-EZ are obsolete. If the taxpayer originally filed a Form 1040-A or 1040-EZ, convert the return to a Form 1040 for reprocessing.
- Remittance – Circle the Remittance Processing System, (RPS) money amount, green rocker, or other remittance indicator to show a non-remittance return. Transfer the payment to the correct TIN or Tax Period. See IRM 21.5.7, Payment Tracers, and IRM 21.5.8, Credit Transfers, for more information.
- Presidential Election Campaign – Circle out unless you are processing to a different tax period. See IRM 21.6.7.4.12, Presidential Election Campaign Fund (PECF).
A received date is required on all returns.
Row If And Then 1 The return is received after the due date of the tax period blank - Enter the received date in the center of page one for (tax year 2017 and prior) and in the empty space to the right of "Dependents" for tax year 2018 and later.
- See IRM 21.5.1.4.2.4, Received Date Determination, and IRM 25.6.1.6.13, Determining the Received Date, for received date determination requirements.
2 Return is timely filed blank - Do not edit the received date.
- See Note following this table.
3 A numbered return is to be reprocessed was originally a remittance return Edit the received date as the calendar date of the Julian date in the original DLN. 4 A numbered return is to be reprocessed was originally a non-remittance return Edit the received date as the calendar date of the Julian date in the original DLN minus 10 days.
NOTE: Do not allow the received date to be earlier than the date the taxpayer signed the return.Note:
When reprocessing a return prior to the due date of the tax period to which it posted, do not use the actual received date. Refer to IRM 21.5.1.4.2.4(3), Received Date-Determination. Mark the center of page one with the corrected received date. Also correct the Return Processable Date (RPD) if more information is secured from the taxpayer.
- Tax Period –X out any incorrect tax period. You must always edit the tax period on prior year returns. If the return is for the current year and the tax period is incorrect, edit the tax period. Enter the tax period using a "YYYYMM" format to the right of the preprinted tax year.
- Name, Address, and TIN – Circle any incorrect taxpayer information such as name, address, and / or TIN and enter the correct information above the circle.
Income, Tax, and Credits – Enter the tax information and any credit changes by putting an "X" to the left of the incorrect amounts. The correct amounts are put to the left of the "X" .
Note:
Consider previous adjustments to the account when editing the income, tax, and credits. Examples include previous adjustments due to an amended return or math error changes. Adjustments made by Examination are not edited and are reprocessed as outlined in IRM 21.5.2.4.23.5, Accounts With Audit Activity.
Note:
When reprocessing a return from CII, it is not necessary to edit the return for income, tax and credits.
Preparer and Third Party Designee information – Circle this information on TC 150 returns or when the return posted as a TC 976 because there is already a TC 150.
Exception:
Do not circle out Third Party Designee information if reprocessing the return to a different tax year or Taxpayer Identification Number (TIN). The Third Party Designee information may be needed to discuss tax issues at a later time.
- Miscellaneous Edits – Any previously edited items no longer desired can be edited by a circle. Circle (edit out) Computer Condition Code (CCC) "G" . Refer to Computer Condition Codes and Return Processing Codes within the Document 6209, Processing Codes and Information, for further information on Return Processing Code (RPC), Section 3.9, and Computer Condition Codes (CCC), Section 3.5. normally input by the Returns Analysis Function.
- When reprocessing a return as an original, complete the following IDRS account actions.
- To prevent unpostable code (UPC) 188, establish a name line for the year being reprocessed or an earlier year. If the necessary name line does not already exist, establish it using Command Code INCHG by inputting the taxpayer's name, filing status, and the year of the return being reprocessed.
Input a Transaction Code (TC) 971 Action Code (AC) 017 on the tax module where the return posts (receiving tax module). This transaction identifies that the return for the receiving tax module is being reprocessed from another tax period / TIN (losing tax module) and cross references that account. Refer to IRM 21.5.1.4.8, Transaction Code 971, for further information.
Note:
The transaction date for the TC 971 AC 017 is the received date of the return being reprocessed from the losing tax module. Refer to IRM 21.5.1.4.2.4, Received Date – Determination, for more information on determining received dates.
If a TC 14X is on the IMF module, or if the BMF module shows current status 02 or 03, input a TC 599 with the correct closing code for your function. Accounts Management:
- 094 Taxable return secured
- 096 Non-Taxable return secured (Return shows no tax liability before prepaid credits)
See IRM 2.4.26.3, Command Code FRM49, for format and instructions on inputting these transaction codes.
For further information see TDI Closing Codes in Document 6209, IRS Processing Codes and Information, Section 11.8-3. Only one TC 599 is required.
Check for an extension of time to file ( indicated by a TC 460). Verify that it should be removed and reinput to the correct tax module. Remove and reinput the extension using Command Code (CC) REQ77 with TC 460 / 462 on the gaining and losing modules, respectively. See IRM 2.4.19, Command Codes REQ77, FRM77 and FRM7A, for format and instructions for inputting a TC 460 / 462.
Caution:
Input of TC 460 using CC REQ77 could prevent MF from using the 90% and 100% paid checks (depending upon the DLN blocking series used) when determining the Failure To Pay (FTP) Start Date. Analyze the module for FTP penalty considerations and adjust the penalty if necessary.
- Determine whether the estimated tax penalty requires adjustment on the losing module. Refer to IRM 20.1.3, Estimated Tax Penalties, for information on calculating the estimated tax penalty.
- See IRM 21.4.6, Refund Offset Research, Reversals, and Injured Spouse Processing, when a refund offset occurred due to non-tax debt (TC 896 or TC 898 on the module).
- See IRM 21.4.6.5.3, Reasons to Reverse TOP Offset, for further information when there is a TC 896 or TC 898 on the module.
Complete Form 12810, Account Transfer Request Checklist, to request an assessment transfer from the incorrect account or period to the correct account or period. Include the following information:
- DLN
- TIN
- MFT
- Tax Period
- Complete Entity Information
- Civil Penalty Reference Number (if applicable)
- Abstract or Reference Number (if applicable)
- POA
- MF Transcript of the Account
- Transaction Codes
Caution:
Do not request a complete account transfer if the account contains a transaction code (TC) 606. See IRM 3.17.21.6.1, Processing Account Transfers to the Master File (IMF / BMF), for more information. Before requesting a transfer for a BMF account, update all penalty and interest accruals. The originator must either input a TC 290 for zero, with a priority code 5, or a TC 270 and TC 340 for the accrued amount if the account is restricted (G- or -I freeze). Allow these transactions to post before requesting the transfer. Submission Processing returns requests that do not meet these requirements. Apply the same posting requirement to IMF accounts.
Reminder:
Input the applicable TC 971 codes on the losing and receiving modules. See IRM 21.5.1.4.8, Transaction Code 971.
Forward the completed Form 12810, Account Transfer Request Checklist, to the following E-mail address (secured E-mail) or EEFax:
Campus Forward To E-mail / EEFax Andover, Atlanta, Kansas City, and Fresno Kansas City Submission Processing Campus ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Philadelphia, Cincinnati, Brookhaven, Ogden and Memphis Ogden Submission Processing Campus ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Austin Austin Submission Processing Center ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Note:
All transfers involving Non-Master File (NMF) are processed at the Kansas City Submission Processing Campus. Refer to IRM 3.17.21.6.3(1), Transfers to Non-Master File, for further instructions.
Note:
Transfers involving Form 8288, U.S. Withholding Tax Return for Certain Dispositions by Foreign Persons, are processed at the Ogden Submission Processing Campus.
Use the procedures contained in this subsection to transfer a refund.
Caution:
If you reprocess a return and transfer a previously issued refund, enter Computer Condition Code (CCC) O (red for IMF returns and green for BMF returns) in the filing status area to prevent issuance of a duplicate refund.
For IMF and NMF accounts, use a credit transfer instead of Form 12857, Refund Transfer Posting Voucher. The credit transfer systemically moves the refund. See IRM 21.5.8, Credit Transfers, for more information.
Reminder:
Accounts Management employees who have access to the Integrated Automation Technology (IAT) Credit Transfer tool are required to use the tool when inputting credit transfers. See the IAT Credit Transfer Tool for more information.
When inputting an adjustment that creates a credit and moves a refund, input Hold Code 1 to prevent an erroneous refund while waiting for the TC 848/849 to post.
Note:
To prevent unpostable code 188, a name line must be established for the year where the TC 849 posts on an earlier year. If the necessary name line does not already exist, establish the name line through Command Code INCHG by inputting the taxpayer's name, filing status, and year. See IRM 21.5.5.4.1, Preventing Unpostables.
To move the refund using CC ADD48:
- Input TC 848 to reverse the TC 846 or TC 840 on the from account. Use the TC 846 or TC 840 transaction date.
Input TC 849 to debit the to account. Use the same transaction date.
Reminder:
Verify you have the correct "from" and "to" TINs before using the IAT Credit Transfer Tool.
Caution:
If credit interest (TC 776/770) is posted on the "from" account, reverse it using CC REQ54/ADJ54 to input a TC 772 and include a TC 570, if necessary, to hold the reversed credit interest from refund or offset. Input a corresponding TC 770 on the "to" account.
- Input TC 470, if necessary, to hold balance due notices until the TC 848 posts. Monitor both sides of the credit transfer to ensure transactions post. See IRM 21.5.1.4.2.2, Integrated Data Retrieval System (IDRS) - Control Procedures, for monitor control procedures.
- When adjusting the primary module and transferring a refund from the secondary module, input a TC 470 with Closing Code 93 on the primary module to hold the balance due notice generated from the TC 849. If your adjustment included a HC 1, you must open a monitor control base and release the -K freeze with a 290.00, after the adjustment posts.
If a credit transfer cannot be used to reverse the previously issued refund from the incorrect account or when moving BMF refunds, prepare Form 12857, Refund Transfer Posting Voucher.
Note:
The use of an IAT Fill Forms tool is mandatory whenever preparing Form 12857 to reverse the previously issued refund from the incorrect account. If moving a refund as part of the erroneous refund process, you can use the fill form option available within the IAT Erroneous Refund tool.
Form 12857 contains:
- Part A- Information for the receiving account.
- Part B- Information for the account from which the refund is transferred.
- Include the split refund code (SPL-REF-CD on CC TXMOD) in box 9 of Form 12857 to prevent Unpostable code 138.
- Form 3809, Miscellaneous Adjustment Voucher or Form 3753, Manual Refund Posting Voucher may be used instead of Form 12857, however, Form 12857 is the preferred form.
Send Form 12857 to Accounting using Form 3210, Document Transmittal.
Note:
For ID Theft cases, annotate the remarks section of Form 3210 with "ID Theft - Expedite." Include IDRS prints showing the refund that is being moved and a print showing that the module for the "to" side is established.
Note:
For Manual Refund Team Contact Information (Accounting Function), please see Exhibit 21.4.4-4, Accounting Function - Manual Refund Team Contact Information.
Input TC 470 to suspend balance due notices until the TC 840 / 841 posts. After the TC 840 / 841 posts input TC 971 (action code 030) on both accounts to cross reference the TC 840 / 841 refund reversal using the transaction date of the TC 846. See IRM 21.6.1.5.3.1, Married Filing Separate, Single, or Head of Household to Married Filing Joint and Both Taxpayers Previously Filed, for further closing code guidance.
Note:
Form 12857 is processed manually. The TC 840 and TC 841 may take 6-8 weeks to post to master file.
If you cannot obtain the original return needed for reprocessing, use available IDRS command codes, such as RTVUE, BRTVU, or TRDBV, to recreate the return. If enough information is available, prepare a "dummy" return and forward to Submission Processing to post to the correct account.
Note:
Do not request the return from Files when preparing a "dummy" return. If the Modernized e-file (MeF) return is available through the Employee User Portal (EUP), print and process that return.
Note:
If you are working with the taxpayer, request a faxed copy of the return if available. You may process the faxed or correspondence copy by following the applicable procedures. Do not transfer information from a faxed return to a new form.
Prepare the "dummy" return using the following steps:
Complete the return using the available information from the applicable Command Codes.
Exception:
If the taxpayer originally filed Form 1040-A or Form 1040-EZ, prepare Form 1040 because those forms are obsolete.
Reminder:
For mixed-period cases, prepare the return using the correct tax year. See IRM 21.5.2.4.23.7, Coding and Editing Procedures, for more information on annotating any corrections needed (e.g., exemption or deduction amount difference).
Write the DLN from unavailable return across the upper right corner of the "dummy" return.
Exception:
Some returns require a new DLN. See IRM 21.5.2.4.23.3, DLNs Used for Reprocessing Documents, for further information.
- Attach the applicable command code print ( e.g; CCs RTVUE / BRTVU or TRDBV) to the back of the "dummy" return.
- On the signature line, show "Original signed – Dummy return to post information to the correct TIN / Tax Year – Do not correspond for signature" or something similar.
- Once completed, forward the return for reprocessing with the applicable form – Form 3893, Re-Entry Document Control for IMF, or Form 13596, Reprocessing Returns, for BMF. See IRM 21.5.2.4.23, Reprocessing Returns / Documents, and IRM 21.5.1.5.5, Processing/Reprocessing CII Tax Returns, for further information.
- Return any original documents (e.g., birth certificates, death certificates, driver’s license, Social Security cards, cancelled checks, etc.,) to the taxpayer when the issue is resolved, unless the taxpayer states the documents do not need to be returned.
Forward source documents in separate folders by document type to campus files within five (5) workdays of input.
Note:
If a source document was not forwarded within 10 workdays after input, complete either Form 10023-B, Attachment (To Be Associated With Return), or Form 9856, Attachment Alert, and include the form with the source document.
- Mail or route source documents immediately after Quality Review is complete. If a source document must be retained for more than seven workdays to complete certain ADJ54 transactions, input "R" in the remarks field. Notify the Files Management Unit immediately of any anticipated shipment delays.
- Route all adjustment documents to the Files Management Unit. Complete Form 4442/e-4442, Inquiry Referral, or Form 8485, Assessment Adjustment Case Record, as required. Include the IDRS sequence number in the upper-right corner before placing the documents in the employee folder.
Prepare a separate adjustment folder for each input date and document type. Label each folder with:
- Employee IDRS Number.
- Input Date.
Category of source documents. Enter a valid document code based on the transaction (TC) you entered.
Example:
A TC 290 adjustment uses "Doc Code 54/ADJ54" : "54" is the document code and "ADJ54" shows the command code used to input the adjustment. Refer to Transaction Codes in Document 6209, IRS Processing Codes and Information, Section 8A-2, for a complete list.
Sequence Number (e.g., 01 - 14). Input the IDRS adjustment sequence number and the number of pages in the packet.
Example:
"XXX-004" to shows that this was the X IDRS adjustment sequence number on REQ54/ADJ54 on the input date and 004 to advise the Campus Files Unit that there are four pages in the folder.
Quality Review Release Date (e.g., 09/30/25).
- Prepare a separate folder for ADJ54 case actions. Date and sequentially number Form 8485 or other applicable worksheets. This helps Campus Files maintain case integrity. Place other transactions, such as credit transfers, in a separate "Other Documents" folder and ship them daily.
Insert source documents into the folder immediately after completing the IDRS adjustment. If you discover a document was omitted, do not destroy it. Obtain the DLN and send the document to Campus Files so it can be associated with the case file.
Individuals use Schedule LEP, Request for Change in Language Preference, to request certain written IRS correspondence in another language. See IRM 22.30.1.8.15.4.1, Improving Access to Services for Persons with Limited English Proficiency (LEP) and Return Preparation Service, for background information on Schedule LEP. Taxpayers can request this preference change:
- Making an oral statement.
- Attaching a Schedule LEP to a Form 1040, U.S. Individual Income Tax Return, Form 1040-X, Amended U.S. Individual Income Tax Return, or duplicate return.
- Filing the Schedule LEP by itself.
- Using the Individual Online Account. Refer to IRM 21.2.1.62, Individual Online Account (IOLA), for more information.
Process the request using IDRS CC REQ77 on CC ENMOD. Input a TC 971, Action Code 192, using the correct Miscellaneous Code field based upon the taxpayer's selection in the table below.Note:
For the Miscellaneous Code field input, you must start the corresponding three-digit code in the third position of the "MISC>" field. Example:"MISC>xx001" (xx = two blank spaces).
Caution:
Verify that the SSN on Schedule LEP matches the taxpayer requesting the language preference. If the requesting taxpayer is the secondary taxpayer on a jointly filed return, input TC 971 AC 192 only on that taxpayer's account.
Caution:
If the taxpayer's name and SSN do not match, or the language selection is unclear, do not update the language preference. Send the appropriate "C" letter requesting a corrected Schedule LEP.
Reminder:
Taxpayers may request a language preference change by oral statement. Schedule LEP is not required. When processing an oral request, enter all zeroes for the MFT and tax period on CC REQ77.
Taxpayer Selection Miscellaneous Code English 000 Spanish 001 Korean 002 Vietnamese 003 Russian 004 Arabic 005 Haitian Creole 006 Tagalog 007 Portuguese 008 Polish 009 Farsi 010 French 011 Japanese 012 Gujarati 013 Punjabi 014 Khmer 015 Urdu 016 Bengali 017 Italian 018 Chinese (Traditional) 019 Chinese (Simplified) 020 Note:
Should an additional change in a language preference be required, i.e., from Spanish back to English, there is no need to input a TC 972 AC 192 reversal. The input of a subsequent TC 971 AC 192 systemically generates a TC 972 AC 192 to reverse the previous transaction.
Individuals use Form 9000, Alternative Media Preference, to request certain written IRS correspondence in accessible format, such as large print, Braille, or audio. Taxpayers can request this preference change:
- Making an oral statement.
- Attaching a Form 9000 to a Form 1040, U.S. Individual Income Tax Return, Form 1040-X, Amended U.S. Individual Income Tax Return, duplicate return.
- Filing the Form 9000 by itself.
- Form 9000 is no longer available through Individual Online Account (IOLA). Advise the taxpayer to complete and submit Form 9000, available at IRS.gov, available at IRS.gov.
Process the request using CC REQ77 on CC ENMOD. Input a TC 971, Action Code 592, using the correct Miscellaneous Code field based upon the taxpayer's selection in the table below:
For the Miscellaneous Code field input, you must enter the applicable two-digit code in the first position of the MISC> field.
Enter the received date in the Secondary Date field. If Form 9000 does not contain a received date, determine the received date using IRM 21.5.1.4.2.4, Received Date – Determination.
Caution:
Verify that the SSN on Form 9000 matches the taxpayer requesting the preference. If the requesting taxpayer is the secondary taxpayer on a jointly filed return, input TC 971 AC 592 only on that taxpayer's account.
Caution:
If the taxpayer’s name and SSN that appear on the Form 9000 do not match or if the selection is not clearly marked (i.e., illegible or multiple selections), do not update the preference. Send an applicable "C" letter to the taxpayer advising that we could not process the Form 9000 and to resubmit the corrected form.
Reminder:
If a media preference change is necessary and the taxpayer requests the change using oral statement, the preference update can be made using CC REQ77. The taxpayer is not required to submit the Form 9000.
Taxpayer Selection Miscellaneous Code Standard Print 00 Large Print 01 Braille 02 Audio (MP3) 03 Plain Text File (TXT) 04 Braille Ready File (BRF) 05 Note:
Should an additional change of preference be required, i.e., from braille back to standard print, there is no need to input a TC 972 AC 592 reversal. The input of a subsequent TC 971 AC 592 systemically generates a TC 972 AC 592 to reverse the previous transaction.
- Advise the taxpayer that only certain notices are issued in the alternative media format. If they receive a letter that is not in their requested format, provide them with instructions on how to request it that it be converted. See IRM 21.3.1.9, Request for Copy for Notice in an Alternative Media Format, for further information.
Prepare a Form 3893, Re-Entry Document Control, to reprocess the tax return. Complete all required blocks on Form 3893 as follows:
- File Type – Check the appropriate box for IMF or Other (for IRAF).
- Block 1 – Leave blank.
- Block 2 – Enter the first eleven digits of the document locator number (DLN).
- Block 3 – Leave blank.
- Block 4 – Document count not to exceed 100.
- Block 5 – Leave blank.
- Block 6 – Leave blank.
- Block 7 – Leave blank.
- Block 8 – Leave blank.
- Block 9 – Enter only if MFT 05, 06, 15, or 29; otherwise leave blank.
- Block 10 – Leave blank.
- Block 11 – Check appropriate box.
Block 12 – Enter the 14th digit of the DLN from the source document. If the year digit is not shown, determine the correct year from the DLN color or from other information on the document.
If the Color is Then the Year Digit is Green 0 or 5 Purple 1 or 6 Red 2 or 7 Black 3 or 8 Blue 4 or 9 - Block 13 – Leave blank.
- Block 14 – For all documents notate information needed to clarify the reason for processing or to preserve the audit trail. Include "Process as Original" .
- Block 15 – Always check "Non-remittance" .
- Block 16 – Enter digits 12 and 13 of the DLN.
- Block 17 – Enter your name or employee number, telephone number, and the current date. Mark the appropriate box for your organization.
- Block 18 – Leave blank.
- Block 19 – Mark the appropriate box to explain the action taken.
Prepare a Form 13596, Reprocessing Returns, to reprocess a BMF return. Complete all required blocks on Form 13596 as follows:
- Enter the employee number and date in the first two boxes.
- Correcting the TIN – Enter the correct TIN, if the TIN shown on the return is incorrect.
Correcting yearly or quarterly returns – Enter the correct period for the return being reprocessed. If correcting a yearly return, use the "YYYYMM" format. If correcting a quarterly return, use "YYYY" format and check the appropriate quarterly box.
Caution:
Some returns may have a tax period ending prior to the last day of the month. Use the following table to determine the correct tax period for the 52 - 53 week return.
If the tax period ended Then Less than 7 days before the end of the month that month is the end of the tax period Within the first 4 days of the month the previous month is the end of the tax period - CP 190, Notification that an amended return was received but an original return was not received – box is checked if reprocessing a TC 976 document as the original return.
- Reasonable cause – check the appropriate box if reasonable cause is being allowed.
- Remarks – enter any remarks, as needed to help process the return correctly. Include "Process as Original" in the remarks.