<?xml version="1.0" encoding="UTF-8"?><?Pub UDT _bookmark _target?><manual xmlns="urn:us:gov:treasury:irs:irm-1.0" xmlns:atict="http://www.arbortext.com/namespace/atict" catno="33710V" hasouo="yes" status="active"><atict:info tracking="off" ref="896" print="" color=""/><metadata><user organization="SBSE"/><user organization="TS"/><owner organization="TS"/><author firstname="Jennifer" lastname="Russell" middleinitial="L" symbols="C:DC:TS:CAS:SP:RPB:IMF"/></metadata>
<mt><mtdate>November 17, 2025</mtdate>
<purpose>
<para>This transmits revised IRM 3.12.37 Error Resolution, IMF General Instructions. </para>
</purpose>
<changes>
<para>IRM 3.12.37.1.1 Added background section per IRM 1.11.2.</para>
<para>IRM 3.12.37.1.3 Update title to include Roles.</para>
<para>IRM 3.12.37.1.4 Changed Objectives to Management in title per IRM 1.11.2.</para>
<para>IRM 3.12.37.1.5 Updated title to Program Controls and added procedures.</para>
<para>IRM 3.12.37.1.6 Added Terms and Acronyms per IRM 1.11.2.</para>
<para>IRM 3.12.37.1.7 Moved Related Resources from IRM 3.12.37.5.2 per IRM 1.11.2.</para>
<para>IRM 3.12.37.4 Moved Timeliness of Rejects from 3.12.37.17.1 for consistency purposes.</para>
<para>IRM 3.12.37.5.1.2(5) Removed incorrect procedure to line through the DLN when voiding.</para>
<para>IRM 3.12.37.5.2 Moved Related Resources to IRM 3.12.37.1.7 per IRM 1.11.2.</para>
<para>IRM 3.12.37.5.6 Moved Sources of Rejects procedure from IRM 3.12.37.18.2 for consistency purposes.</para>
<para>IRM 3.12.37.5.6.1 Moved Code and Edit Function from IRM 3.12.37.18.2.1 for consistency purposes.</para>
<para>IRM 3.12.37.5.6.2 Moved Error Correction Function from IRM 3.12.37.18.2.2 for consistency purposes.</para>
<para>IRM 3.12.37.5.6.3 Moved Unpostables Function from IRM 3.12.37.18.2.3 for consistency purposes.</para>
<para>IRM 3.12.37.6 Changed title to Clerical guidelines for consistency purposes.</para>
<para>IRM 3.12.37.6.2.2(7) Updated instruction for routing Action Codes 491-499.</para>
<para>IRM 3.12.37.6.4 Moved Clerical Letter Input procedures from IRM 3.12.37.7 section and subsection for consistency purposes.</para>
<para>IRM 3.12.37.6.4.1.2(2) Updated incorrect link to the Letters Job Aid.</para>
<para>IRM 3.12.37.6.4.2 Moved Correspondence Suspense file procedures from IRM 3.12.37.8 for consistency purposes.</para>
<para>IRM 3.12.37.6.5 Moved Control of Error Register section and subsection from IRM 3.12.37.9 for consistency purposes.</para>
<para>IRM 3.12.37.6.6 Moved Control of Reject Registers section and subsections from IRM 3.12.37.10.</para>
<para>IRM 3.12.37.6.6.4 Moved Reject Register Summary GMF 11-45 procedure from IRM 3.12.37.10.6 for consistency purposes.</para>
<para>IRM 3.12.37.6.6.5 Moved Current Reject Listing GMF-11-46 procedure from IRM 3.12.37.19.5 for consistency purposes.</para>
<para>IRM 3.12.37.6.7 Moved Form 6826, Error/Reject Display Card section and subsections from IRM 3.12.37.11 for consistency purposes.</para>
<para>IRM 3.12.37.8 Moved section and subsections to IRM 3.12.37.6.4.2 for consistency purposes.</para>
<para>IRM 3.12.37.9 Moved section and subsections to IRM 3.12.37.6.5 for consistency purposes.</para>
<para>IRM 3.12.37.10 Moved section and subsections to IRM 3.12.37.6.6.</para>
<para>IRM 3.12.37.11 Moved Form 6826 section and subsections to IRM 3.12.37.6.7 for consistency purposes.</para>
<para>IRM 3.12.37.12 Added Reject Register, Reject Register Identification line, and Error/Reject Action Codes, due to moving the procedures to this subsection. Also moved section and subsection to IRM 3.12.37.12.7.</para>
<para>IRM 3.12.37.12.1.1 Moved Error Register Title line from IRM 3.12.37.12.2 for consistency purposes.</para>
<para>IRM 3.12.37.12.1.2 Moved Error Register Identification line from IRM 3.12.37.12.3 for consistency purposes.</para>
<para>IRM 3.12.37.12.1.3 Moved Error Register Document Sections from IRM 3.12.37.12.4 for consistency purposes.</para>
<para>IRM 3.12.37.14 Removed section and subsection as the procedures are being moved to IRM 3.12.2 and moved Error Resolution System as well as ordering of work procedures to IRM 3.12.37.5.7 and subsections for consistency. </para>
<para>IRM 3.12.37.18 Removed as subsections have been moved for consistency purposes.</para>
<para>IRM 3.12.37.18.1 Moved Timeliness of processing Rejects to IRM 3.12.37.4.</para>
<para>IRM 3.12.37.18.2 Moved to IRM 3.12.37.5.6 for consistency purposes.</para>
<para>IRM 3.12.37.18.2.1 Moved to IRM 3.12.37.5.6.2 for consistency purposes.</para>
<para>IRM 3.12.37.18.2.2 Moved to IRM 3.12.37.5.6.2 for consistency purposes.</para>
<para>IRM 3.12.37.18.2.3 Moved to IRM 3.12.37.5.6.3 for consistency purposes.</para>
<para>IRM 3.12.37.18.14 Added condition for Unpostable Code 150 RC 0. IPU 25U3388 issued 06-09-2025. </para>
<para>IRM 3.12.37.18.14.1 Added instructions for Unpostable Code 150 RC 0. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.18.14.2 Added condition for Unpostable Code 150 RC 1. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.18.14.2.1 Added instructions for Unpostable Code 150 RC 1. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.18.21.4.2 Unpostable Code 164 RC 6 moved to IRM 3.12.37.18.21.5 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.4.3 Correction Procedures UPC 164 RC 6 moved to IRM 3.12.37.18.21.5.1 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.4.4 Unpostable Code 164 RC 8 moved to IRM 3.12.37.18.21.6 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.4.5 Correction Procedures UPC 164 RC 8 moved to IRM 3.12.37.18.21.6.1 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.4.6 Unpostable Code 164 RC 9 moved to IRM 3.12.37.18.21.7 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.4.6.1 Correction Procedures UPC 164 RC 9 moved to IRM 3.12.37.18.21.7.1 for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.21.7.1 Added instructions to remove the entire amount of IRC 1341 if the amount is less than the refund amount. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.18.21.8 Deleted subsections as they have been moved to their respective subsection for consistency. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.18.22.4.1(4) Updated incorrect procedures. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.18.22.7.1(3) Added missing instruction to send TPNC 845. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.18.43.3.1(6) j) Added TY20 and TY21 for Recovery rebate credit. IPU 25U0147 issued 01-31-2025.</para>
<para>IRM 3.12.37.19 Removed duplicate procedures.</para>
<para>IRM 3.12.37.19.2.1 Removed procedure pertaining to Unpostable inventory.</para>
<para>IRM 3.12.37.19.2.4 Added procedures to utilize the GUF55-47 or Form 8749 when processing Unpostables.</para>
<para>IRM 3.12.37.19.3 Removed duplicate procedure.</para>
<para>IRM 3.12.37.19.4 Removed duplicate language.</para>
<para>IRM 3.12.37.19.6 Removed Section and subsection as this UPC no longer presents.</para>
<para>IRM 3.12.37.19.10 Removed RC from title for consistency purposes.</para>
<para>IRM 3.12.37.19.10.1(4d) Updated incorrect CII ID number per email received. </para>
<para>IRM 3.12.37.19.19.1 Changed title to Correction Procedures UPC 157 RC 0 for consistency purposes.</para>
<para>IRM 3.12.37.19.19.1.1 Moved to IRM 3.12.37.19.19.1 for consistency purposes.</para>
<para>IRM 3.12.37.19.21.1 Changed BMF Reject team to BMF Code &amp; Edit team for conversion.</para>
<para>IRM 3.12.37.19.22.2.1(6) Added procedures for missing documents. Updated incorrect procedures throughout the table.</para>
<para>IRM 3.12.37.19.22.4 Removed conditions for UPC 164 RC 6 &amp; 8 as they are addressed under their respective IRM procedure.</para>
<para>IRM 3.12.37.19.33.3.1(4) Added missing procedure to input forms when taxpayers owe a first- time home buyer payment.</para>
<para>IRM 3.12.37.19.34.2.1 Added missing instruction per clearance feedback.</para>
<para>IRM 3.12.37.19.35.1 Changed title to Correction Procedures UPC 195 RC 1 for consistency purposes.</para>
<para>IRM 3.12.37.19.35.1.1 Moved to IRM 3.12.37.19.35.1 for consistency purposes.</para>
<para>IRM 3.12.37.19.36.1 Changed title to Correction Procedures UPC 197 RC 4 for consistency purposes.</para>
<para>IRM 3.12.37.19.36.1.1 Moved to IRM 3.12.37.19.36.1 for consistency purposes.</para>
<para>IRM 3.12.37.20 Moved reports and changed title to ERS 17-44 Error File, ERS 17-45 Suspense File, IMF Interest Jeopardy Reports.</para>
<para>IRM 3.12.37.20.2 Moved Reject register to IRM 3.12.37.12.5.</para>
<para>IRM 3.12.37.20.2.1 Moved Reject register title line to IRM 3.12.37.12.5.1.</para>
<para>IRM 3.12.37.20.2.2 Moved Reject register identification line to IRM 3.12.37.12.5.2.</para>
<para>IRM 3.12.37.20.3 Moved Reject register summary GMF-11-45 to IRM 3.12.37.6.6.4.</para>
<para>IRM 3.12.37.20.4 Moved Reject inventory list GMF-11-43 to IRM 3.12.37.6.6.3.</para>
<para>IRM 3.12.37.20.5 Moved Current Reject listing GMF-11-46 to IRM 3.12.37.6.6.5.</para>
<para>IRM 3.12.37.20.6 Moved reports to IRM 3.12.37.20.</para>
<para>IRM 3.12.37.21 Removed entire section and subsections as these procedures are in other areas and/or in the manager’s job aid.</para>
<para>IRM 3.12.37.22 Changed Correspondence suspense to loose forms and schedules due to update in IRM 3.12.37.22.4. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.22.4 Changed title to loose form and schedules and removed duplicate paragraphs and obsolete instructions. IPU 25U3388 issued 06-09-2025.</para>
<para>IRM 3.12.37.22.6.2(2) Removed FLC table due to changes of rules for scanned paper. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.22.6.2 Added missing scanned paper FLC for Austin. IPU 25U0283 issued 02-27-2025.</para>
<para>IRM 3.12.37.22.6.2(6) Added Action 199 per reach in guidance from RIVO. IPU 25U0452 issued 04-17-2025.</para>
<para>IRM 3.12.37.22.6.3 Added instructions to close the case in e-gain if the taxpayer did not submit a Reply. Added instructions if the reply received warrants the return to be processed as an International and/or BMF return. IPU 25U0432 issued 04-09-2025.</para>
<para>IRM 3.12.37.22.6.3(6) Updated incorrect second correspondence instructions for secure messaging. IPU 25U0009 issued 01-03-2025.</para>
<para>IRM 3.12.37.22.6.3(6)(9) Updated incorrect instructions for when second correspondence is needed on a secure messaging reply. Added instruction when a reply is received for a different DLN than what is showing in the eGain system. IPU 25U0452 issued 04-17-2025.</para>
<para>IRM 3.12.37.23 Removed Quick notes and no reply processing instructions from listing. Updated no reply cases to no reply processing procedures for consistency.</para>
<para>IRM 3.12.37.23.3 Removed Quick notes subsection as this information is being moved to IRM 3.12.2 for consistency purposes.</para>
<para>IRM 3.12.37.23.4 Made correction to title as the procedures are for loose forms and schedules. Added explanation of classified waste. Updated title and removed treat form 4442 as classified waste. Added explanation of classified waste.</para>
<para>IRM 3.12.37.23.5 Updated correction procedures when ACA error codes present after first correspondence. </para>
<para>IRM 3.12.37.23.6 Added procedures on how to handle an incomplete reply. Removed incorrect procedures for quick note. Updated procedures for when to send TPNC 558. Added exception for Form 1310. </para>
<para>IRM 3.12.37.23.6.2(13) Removed procedure as this is not valid on a reply that warrants a TC 290 for zero input.</para>
<para>IRM 3.12.37.23.7 Updated title to no reply processing procedures and moved procedures from IRM 3.12.37.23.7.1 for consistency purposes.</para>
<para>IRM 3.12.37.23.7.1 Moved no reply processing procedures to IRM 3.12.37.23.7 for consistency purposes.</para>
<para>IRM 3.12.37.23.8(6)(7) Added explanation of classified waste.</para>
<para>IRM 3.12.37.24.2.1 Added procedures on closing missing Statute returns.</para>
<para>IRM 3.12.37.24.4(1) Added procedure for Schedule H missing an EIN.</para>
<para>IRM 3.12.37.26 Added Form 1040 that must be processed at ANMF. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.26.2(1) Updated incorrect procedures on routing a Form 1040 for conversion to Form 1041. IPU 25U3388 issued 06-09-2025 .</para>
<para>IRM 3.12.37.26.3 Moved Automated Non-Masterfile from IRM 3.12.37.30.4 for consistency purposes. Added instructions on how Austin and Ogden are to handle MeF Form 1040 to be processed at ANMF. IPU 25U0383 issued 03-17-2025. </para>
<para>IRM 3.12.37.28.1.2(2) Added missing instruction in order to locate the date of transaction. IPU25U0009 issued 01-03-2025.</para>
<para>IRM 3.12.37.28.6 Moved ANMF Subsequent and Advanced Payment Items from IRM 3.12.37.30.4.1 for consistency purposes. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.28.6 Updated title, removed and updated incorrect instructions. IPU 25U0432 issued 04-09-2025.</para>
<para>IRM 3.12.37.29 Added the exhibit to general ledger accounts for consistency. Added procedures when processing remittance made out to entities other than the IRS.</para>
<para>IRM 3.12.37.29.2 Updated instructions throughout per guidance given from accounting.</para>
<para>IRM 3.12.37.29.3 Updated procedures throughout per guidance from accounting.</para>
<para>IRM 3.12.37.29.4 Removed procedures as Rejects should not be completing this form per accounting guidance.</para>
<para>IRM 3.12.37.29.5.3(3A) Removed incorrect procedure.</para>
<para>IRM 3.12.37.30.4 Moved to IRM 3.12.37.26.3 for consistency purposes. IPU 25U0383 issued 03-17-2025. </para>
<para>IRM 3.12.37.30.4.1 Moved to IRM 3.12.37.28.6 for consistency purposes. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.31.1 Added condition for Transaction Code 840 was not keyed in the header. IPU 25U0432 issued 04-09-2025.</para>
<para>IRM 3.12.37.31.2(4) Added instructions for when a TC 840 must be keyed in the block header. IPU 25U0432 issued 04-09-2025.</para>
<para>IRM 3.12.37.35 Added missing documents.</para>
<para>IRM 3.12.37.35.1 Moved procedure from paragraph 6a to paragraph 5 and removed all duplicate information.</para>
<para>IRM 3.12.37.35.2(4)(5)(6) Updated paragraph 4 to include Files special search, removed paragraph 5 as the instructions are in paragraph 4 and updated paragraph 6 to include Files special search for consistency purposes. IPU 25U0283 issued 02-27-2025.</para>
<para>IRM 3.12.37.35.3 (3)(4)(5) Removed invalid instructions for resuspending missing documents. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.36 Removed duplicate procedures, moved missing documents to IRM 3.12.37.35.1.</para>
<para>IRM 3.12.37.36.1 Added instructions on when to contact the originator. IPU 25U0383 issued 03-17-2025.</para>
<para>IRM 3.12.37.36.1 Added missing instruction. IPU25U0009 issued 01-03-2025.</para>
<para>Exhibit 3.12.37-1 Acronyms updated to remove and only include the acronyms used throughout the IRM.</para>
<para>Editorial changes have been made throughout this IRM to include spelling, punctuation, annual updates, corrected typos, changed section to subsection where applicable, changed 02RPD to 88RPD, and cleaned up language for easier read.</para>
</changes>
<effdocs>This IRM also incorporates the following IRM Procedural Updates (IPU) 25U0009 issued 01/03/2025, IPU 25U0147 issued 01-30-2025, IPU 25U0283 issued 02-26-2025, IPU 25U0383 issued 03-13-2025, IPU 25U0432 issued 04-07-2025, IPU 25U0452 issued 04-15-2025, IPU 25U3388 issued 06-06-2025. </effdocs>
<audience> IMF Error Resolution Departments, Submission Processing</audience>
<effdate>(01-01-2026)</effdate>
<signature><br/>Scott Wallace<br/>Director, Submission Processing<br/>Taxpayer Services</signature>
</mt>
<irm>
<part partno="3">
<parttitle>Submission Processing</parttitle>
<chapter chapno="12">
<chaptertitle>Error Resolution</chaptertitle>
<section id="id337100667" sectno="37">
<sectiontitle>IMF General Instructions</sectiontitle>
<toc/>
<subsection1 id="id337101328"><date>(04-04-2022)</date>
<title>Program Scope and Objectives </title>
<para><emphasis type="b">Purpose:</emphasis> This Internal Revenue Manual (IRM) provides instructions for correcting errors in Error Resolution System (ERS). The instructions are used to correct the validity, consistency or math computations during processing. <alphalist>
<li>This IRM also provides instructions for the control clerks to receive, sort, distribute returns, control registers, and input correspondence.</li>
<li>This IRM also provides instructions for unpostable codes, payments and correspondence.</li>
</alphalist></para>
<para><emphasis type="b">Audience:</emphasis> This IRM is used by tax examiners and clerks in the Submission Processing sites.</para>
<para><emphasis type="b">Policy Owner:</emphasis> The Director of Submission Processing</para>
<para><emphasis type="b">Program Owner:</emphasis> Taxpayer Services (TS) Submission Processing (SP) Return Processing Branch is responsible for the procedures and all updates related to this IRM.</para>
<para><emphasis type="b">Primary Stakeholders: Submission Processing (SP) and Modernized E-File (MeF).</emphasis></para>
<subsection2 id="id337101740"><date>(01-01-2026)</date>
<title>Background</title>
<para>The rejects inventory system includes workable and non-workable suspense which allow for returns/documents to be held for correspondence or routed to other areas for more research and/or more action.</para>
<para>Employees use the ERS system and the return to correct these conditions and when necessary, use IDRS to research.</para>
</subsection2>
<subsection2 id="id337101397"><date>(11-17-2020)</date>
<title>Authority</title>
<para>IRC Sec 6213(b) provides the authority for resolution of mathematical and clerical errors identified during processing of tax returns.</para>
<para>Policy Statements for Submission Processing are contained in IRM 1.2.1.4, <emphasis type="b">Policy Statements for Submission Processing Activities</emphasis>.</para>
</subsection2>
<subsection2 id="id337101398"><date>(11-10-2021)</date>
<title>Roles and Responsibilities </title>
<para>The SP Director is responsible for monitoring operational performances for the Submission Processing campuses.</para>
<para>The Operational manager is responsible for monitoring operational performance for their operation.</para>
<para>The team manager/lead is responsible for performance monitoring and ensuring employees have the tools to perform their duties.</para>
<para>The team employees are responsible for following the instructions contained in this IRM and maintaining updated IRM procedures.</para>
</subsection2>
<subsection2 id="id337101399"><date>(01-01-2026)</date>
<title>Program Management and Review</title>
<para><emphasis type="b">Program Goals</emphasis>: Correct all errors that are identified by the Error Resolutions System. </para>
<para><emphasis type="b">Program Reports</emphasis>: The Monitoring Section under Submission Processing Program Management /Process Assurance monitors the ERS Reports.</para>
<para><emphasis type="b">Program Effectiveness:</emphasis> The program goals are measured by the following reviews:<alphalist>
<li>Embedded Quality Submission Processing (EQSP) individual quality review</li>
<li>Computer Assisted Review of ERS (CARE) is an on-line review of Taxpayer Notice Code (TPNC) assigned by the ERS/Rejects tax examiner during processing</li>
<li>Balanced Measures</li>
<li>Managerial Reviews</li>
</alphalist></para>
<para><emphasis type="b">Annual Review:</emphasis> This IRM is updated and reviewed annually to ensure accuracy and promote consistent tax administration. Review and concurrence are performed by affected offices according to the clearance process established in IRM 1.11.9 Internal Management Documents System-Clearing and Approving Internal Revenue Manual prior to publishing. </para>
</subsection2>
<subsection2 id="id337101400"><date>(01-01-2026)</date>
<title>Program Controls</title>
<para>Quality Review conducts a statistical valid sample size review of completed work to ensure IRM guidelines are followed.</para>
<para>Management oversight level for discarding and/or destroying records as classified waste to ensure records are not disposed of or destroyed without following the <citation type="Document">Document 12990</citation>, IRS Records Control Schedules.</para>
</subsection2>
<subsection2 id="id337101741"><date>(01-01-2026)</date>
<title>Terms and Acronyms</title>
<para> <seealso idref="id337100470">Exhibit 3.12.37-1</seealso> for a listing of all Acronyms and Abbreviations.</para>
</subsection2>
<subsection2 id="id337101742"><date>(01-01-2026)</date>
<title>Related Resources</title>
<para>This subsection references Internal Revenue Manuals (IRM), and job aids used in processing tax returns.</para>
<para> The resources below provide the IRM references and titles.<table frame="all" id="id337100859" summary="Relevant IRM for Rejects" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">RESOURCE </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b"> TITLE</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 2.3</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">IDRS Terminal Responses</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 2.4</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">IDRS Terminal Input</entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 20.2</citation></entry>
<entry valign="middle">Interest</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.10.72</citation>							</entry>
<entry colsep="1" rowsep="1" valign="middle">Receiving, Extracting, and Sorting</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.10.73</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Batching and Numbering</entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 3.11.3</citation></entry>
<entry valign="middle">Individual Income Tax Returns</entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 3.12.2</citation></entry>
<entry valign="middle">Individual Master File Error Resolution General Instructions</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.3</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Individual Income Tax Returns</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.8</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Information Returns Processing</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.10</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Revenue Receipts </entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.21</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Credit and Account Transfers (Miscellaneous Accounting) </entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.32</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">General Unpostables</entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 3.12.38</citation></entry>
<entry valign="middle">BMF General Instruction</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.179</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">IMF and PMF Unpostable Resolution</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.212</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Applications For Extension of Time to File Tax Returns</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.12.279</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">BMF/CAWR/PMF Unpostable Resolution</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.13.122</citation></entry>
<entry colsep="1" rowsep="1" valign="middle"> IMF Entity Control Unpostables</entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 3.17.10</citation></entry>
<entry valign="middle">Dishonored Check File (DCF) and Unidentified Remittance File (URF)</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.17.79</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Accounting Refund Transactions</entry>
</row>
<row>
<?PubTbl row rht="0.43in"?>
<entry align="left" valign="middle"><citation type="IRM">IRM 3.17.220</citation></entry>
<entry valign="middle">Excess Collections File</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.22.3</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">International ERS</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.24.21</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">Credit and Account Transfers (ISRP)</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="IRM">IRM 3.42.5</citation></entry>
<entry colsep="1" rowsep="1" valign="middle">IRS e-File for Individual Income Tax Returns </entry>
</row>
<row>
<entry align="left" valign="middle"><citation type="IRM">IRM 21.5.1</citation></entry>
<entry valign="middle">General Adjustments - handling classified waste</entry>
</row>
<row>
<entry align="left" colsep="1" rowsep="1" valign="middle"><citation type="Document">Document 6209</citation>												</entry>
<entry colsep="1" rowsep="1" valign="middle">IRS Processing Codes and Information</entry>
</row>
<row>
<entry valign="middle">Current Year 2532-701 Job Aid</entry>
<entry valign="middle">Correcting IMF Suspense/Rejects</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>The following are additional related resources:<bulletlist>
<li>Servicewide Electronic Research Program (SERP)</li>
<li>Integrated Automation Technologies (IAT)</li>
<li>Integrated Data Retrieval System (IDRS)</li>
<li>National Archives and Record Administration (NARA) approved Document 12990, IRS Records Control Schedules, for records retention, disposition, and destruction guidance.</li>
</bulletlist></para>
<para>The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For additional information about the TBOR, see <a external="yes" href="https://www.irs.gov/taxpayer-bill-of-rights" title="irs.gov bill of rights">https://www.irs.gov/taxpayer-bill-of-rights.</a></para>
</subsection2>
<subsection2 id="id337101401"><date>(11-17-2020)</date>
<title>Primary Stakeholder</title>
<para>Submission Processing (SP) and Modernized E-file.</para>
</subsection2>
</subsection1>
<subsection1 id="id337101355"><date>(01-01-2025)</date>
<title>Deviations from this Internal Revenue Manual (IRM)</title>
<para>Service Center Directors, Headquarter Branch Chiefs, and Headquarter Analysts do not have the authority to approve deviations from IRM procedures. Any request for an exception or deviation to an IRM procedure must be elevated through appropriate channels for executive approval. This will ensure that other functional areas are not adversely affected by the changes and that it does not result in disparate treatment of taxpayers.</para>
<para>See guidelines in IRM <emphasis type="b">1.11.2</emphasis>, Internal Management Documents System, <emphasis>Internal</emphasis><emphasis> Revenue</emphasis><emphasis> Manual </emphasis><emphasis>(IRM)</emphasis><emphasis> Process</emphasis>. Request for an IRM deviation must be submitted in writing and signed by the Field Director, following instructions from IRM <emphasis>1.11.2.2.3</emphasis></para>
<para>Any disclosure issues will be coordinated by the Program Owner. No deviations can begin until they are reviewed by the Program Owner and approved at the Executive Level. All requests must be submitted to the Submission Processing Headquarters IRM Coordinator.</para>
</subsection1>
<subsection1 id="id337101377"><date>(11-10-2021)</date>
<title>Taxpayer Advocate Service (TAS)</title>
<para>This subsection contains information on referring cases to TAS.</para>
<subsection2 id="id337101369"><date>(01-01-2025)</date>
<title>TAS Background Information </title>
<para>The Taxpayer Advocate Service (TAS) is an independent organization within the Internal Revenue Service (IRS), led by the National Taxpayer Advocate, that helps taxpayer rights. TAS offers free help to taxpayers when a tax problem is causing a financial difficulty, when they’ve tried and been unable to resolve their issue with the IRS, or when they believe an IRS system, process, or procedure just isn’t working as it should. TAS strives to ensure that every taxpayer is treated fairly and knows and understands their rights. </para>
<para>TAS criteria include economic burden, systemic burden, best interest of the taxpayer, and public policy (as determined solely by the National Taxpayer Advocate (NTA)). TAS is responsible for assisting taxpayers who have unresolved problems with the IRS. See <citation type="IRM">IRM 13.1.7.3</citation>, <emphasis>Taxpayer Advocate Service (TAS) Case Criteria</emphasis>, if additional information is required.</para>
<para>While the IRS is continually working to serve customers in a quality manner, some taxpayers still have difficulty getting solutions to their problems or getting timely and appropriate responses to their inquiries. Per IRC 7803(c), Congress established the Office of the Taxpayer Advocate and its functions within the IRS to assist these taxpayers, TAS has identified criteria that qualify taxpayers for TAS assistance. The Case Advocate will conduct an independent review of actions that have been taken or need to be taken to resolve the problems taxpayers are experiencing.</para>
<para>The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For additional information about the TBOR, see <a external="yes" href=" https://www.irs.gov/taxpayer-bill-of-rights" title="irs.gov/taxpayer bill of rights">https://www.irs.gov/taxpayer-bill-of-rights</a>.</para>
</subsection2>
<subsection2 id="id337101372"><date>(05-24-2023)</date>
<title>Processing Received TAS Cases</title>
<para>Ensure each person working TAS cases are experienced in all aspects of ERS/Rejects work.</para>
<para>Review the case to ensure the case is being worked by the correct service center and SP is the correct area. If the case is not your area or the correct service center, contact the TAS employee in Section II part 1, Section IV, and your lead. </para>
<para>Check to see if the document is in ERS. If in ERS, follow <citation type="IRM">IRM 3.12.2</citation>,<citation type="IRM">IRM 3.12.3</citation>, and <seealso idref="id337100667">IRM 3.12.37</seealso>. If not in ERS, ACTVT the return and work the following day. If the document is not in ERS, fill in all appropriate response from Section VI – RESPONSES</para>
<para>When correspondence is needed from the taxpayer to close the return, and the return is in workable suspense and not included in the e-mail or the OAR PDF, GTREC the document (do NOT clear it). GTSEC 01 and input OARXXXXXXX (the OAR number from Section I, Part 3) in the 01CCC field and LEADXXX (your team number, Ex: LEAD101) in the 94EXV field. Request the information from the TAS Case Advocate (CA) in PDF format following TAS CASE ADVOCATE EMAIL CORRESPONDENCE procedures below.</para>
<para>After processing a TAS case in which TAS is asking the tax examiner to remove the IRC 1341 credit due to taxpayer error, tax examiners will notify their local P&amp;A analyst by sending an email which includes the DLNs they have closed.</para>
<para>If the document is NOT in workable suspense, ERINV the DLN to see if it can be activated. If the DLN can be activated, ACTVT the document and work the next day GTSEC 01 and input OARXXXXXXX (the OAR number from Section I, Part 3) in the 01CCC field and LEADXXX (your team number, Ex: LEAD101) in the 94EXV field. Request the information from the TAS Case Advocate (CA) in PDF format. </para>
<para>If correspondence was requested and it is the completion date of the OAR or the OAR has expired and no correspondence has been received from the CA, e-mail the CA with the following literal: The OAR is set to expire or has already expired. Provide the requested information by close of business tomorrow or OAR will be processed as a no-reply.</para>
<para>Follow all local procedures for processing TAS cases.</para>
</subsection2>
<subsection2 id="id337101373"><date>(01-01-2023)</date>
<title>Operations Assistance Request (OAR)</title>
<para> The Taxpayer Advocate Service uses the Operation Assistance Request (OAR) process to refer cases when TAS lacks either the statutory or delegated authority to resolve a taxpayer’s problem. The TAS uses Form 12412, <emphasis>Operation Assistance Request</emphasis> to initiate the OAR process.</para>
<para>In cases requiring an OAR, TAS completes Form 12412 and forwards the case to the Operating Division Liaison via Form 3210, <emphasis>Document Transmittal</emphasis>. The Operating Division Liaison reviews the case, assigns it to the appropriate area, and monitors the case through its conclusion.</para>
<para>When TAS requests expedite processing, Operating Division or Functions Liaisons acknowledge receipt via Form 3210, secure messaging e-mail, fax, or by phone within one workday of receipt of the OAR.</para>
<para>For OARs not requiring expedite processing, the Operation Division or Functions Liaisons acknowledge receipt via Form 3210, secure messaging e-mail, fax, or by phone within three workdays of receipt or the OAR.</para>
<para>Make every effort to expedite completion of OAR cases. Form 12412 indicates time frames for OAR Case completion. Employees:<bulletlist>
<li>Work with your manager and the Taxpayer Advocate contact listed on Form 12412 to arrive at agreed upon timeframes for follow-up based on the facts and circumstances of the particular case.</li>
<li>Immediately notify your manager if you can't resolve a taxpayer’s case by the requested timeframe or by a negotiated extension date.</li>
<li>Discuss your findings and recommendation for final case disposition with your manager and the appropriate TAS contact. The TAS contact communicates the final case decision to the taxpayer. However, you and your manager can also tell the taxpayer of the decision.</li>
<li>The TAS employee elevates this disagreement to their manager who discusses it with the appropriate Operating Division manager, if you, your manager, and the TAS contact can't agree upon the resolution to the taxpayer’s problem. Elevate any disagreement up the chain to your Department Manager.</li>
<li>Upon case resolution, the tax examiner assigned the OAR completes section VI of Form 12412 and returns it to the TAS Case Advocate assigned the case. Return the Form 12412 within three (3) workdays of completing all actions and posting all transactions.</li>
</bulletlist></para>
<para>For more detailed information, refer to <citation type="IRM">IRM 13.1.19</citation>, Advocating with Operations Assistance Requests (OARS).</para>
</subsection2>
</subsection1>
<subsection1 id="id337101743"><date>(01-01-2026)</date>
<title>Timeliness of Processing Rejects</title>
<para>Corrective action for items in the workable inventory will be completed within 10 business days. Correspondence (Letter Input) will be completed within 10 business days for items requiring taxpayer contact. </para>
<para>Aged Reject cases (over 60 days) will be worked as quickly as possible and will <emphasis type="b">not exceed twenty percent</emphasis> of the inventory. All cases will be completed within 120 days.</para>
</subsection1>
<subsection1 id="id337100002"><date>(01-01-2025)</date>
<title>Introduction and General Procedures</title>
<para>This manual contains general procedures for the following: <bulletlist>
<li>Control Clerks</li>
<li>Corrections of Error Resolution System (ERS)</li>
<li>Service Center Replacement System (SCRS)</li>
<li>Corrections of Suspense/Rejects</li>
<li>Reports to monitor and control inventories in the Input Correction Operation </li>
<li>Unpostable Codes and Correction Procedures</li>
<li>Procedures for the correction of specific tax returns or documents are contained in other Sections of the Internal Revenue Manual (IRM) 3.12.3, Error Resolution, Individual Income Tax Returns.</li>
</bulletlist></para>
<para>General procedures are always overruled by the IRM for the specific form being worked, when there are differences. The purpose of Error Resolution is to ensure that the tax return posts accurately and correctly to the proper taxpayer's account, providing quality customer service to taxpayers. This IRM cannot address every possibility that may arise while correcting returns or documents. Taxpayer intent must be taken into consideration. In some cases, it may be necessary to refer the issue to your Subject Matter Expert (SME), lead and/or manager to determine the proper corrective action. Employees will exercise sound judgment when determining which Taxpayer Notice Codes (TPNCs) is the most appropriate to send, or when to correspond for clarification. </para>
<para>Procedures for specific tax returns, documents and Error Codes are contained in Internal Revenue Manual (IRM) 3.12.3, Error Resolution, Individual Income Tax Returns, IRM 3.12.2 Individual Master File Error Resolution General Instructions.</para>
<subsection2 id="id337100003"><date>(01-01-2025)</date>
<title>General Explanation</title>
<para>This manual contains instructions that apply to several different functions within the Input Correction and Document Correction Operation.</para>
<para>Subsections in this manual contain procedures applicable to several different functions. However, tax examiners and clerks are not expected to be knowledgeable regarding portions of this manual that clearly do not relate to their work functions. <alphalist>
<li>Control Clerk—Controls the inventory received into the Input Correction Operation from other areas. They also control and release inventory to other functions.</li>
<li>ERS/SCRS—Returns or source documents that have failed validity, consistency or math computation and must be corrected via ERS or SCRS.</li>
<li>Suspense/Rejects—Returns and documents are unprocessables and included as rejects.<note>Returns activated to be worked via the Error Resolution System (ERS) will be processed using IRM 3.12.2 &amp; IRM 3.12.3 Individual Income Tax Returns and/or IRM 3.22.3 International ERS.</note></li>
<li>Reports—Designed to control and monitor inventories. Some reports are designed to monitor the performance of employees.</li>
<li>Rejected Unpostable Returns - Certain unpostable returns will be forwarded to Rejects by the Unpostable function to be worked via ERS. These returns will be processed using the procedures in IRM 3.12.37, IRM 3.12.2, IRM 3.12.3, IRM 3.12.179, IRM 3.13.122 and IRM 3.22.3.</li>
</alphalist></para>
<subsection3 id="id337100004"><date>(11-17-2020)</date>
<title>Suspense/Rejects Conditions</title>
<para>Work may be included in the Suspense/Rejects inventory for any of the following reasons: <bulletlist>
<li>Correspondence with the taxpayer is required to obtain missing information or Schedules/Forms</li>
<li>The return or document has been numbered incorrectly</li>
<li>The return requires review by another function</li>
<li>The return required additional research to determine the correct entity, filing status, FYM (fiscal year month), or filing requirements</li>
<li>The return must be reentered because of an incorrect Block Header or a program cut-off</li>
<li>The return will not be processed</li>
<li>A previous examiner was unable to make the proper correction</li>
<li>The return is missing</li>
<li>The return was filed early (i.e., before the end of the tax period)</li>
<li>Nullified Unpostables</li>
</bulletlist></para>
</subsection3>
<subsection3 id="id337101357"><date>(01-01-2026)</date>
<title>Working Trail</title>
<para> It is important to leave a legible working trail and/or Action Trail for those who may work with the return later. If your Campus has written in-house agreements which vary from the instructions below, you may follow them. </para>
<para>A working trail is to be left at the point of error on the return or schedule for each correction made in the areas specified below. Place an <emphasis><emphasis>X</emphasis></emphasis> beside the incorrect data and write the correct data to the left or above the <emphasis><emphasis>X</emphasis></emphasis>. However, if the information is available on the page, use an arrow to move the information to the correct line. <note>Circle out incorrect Tax Periods, SSNs and EINs. </note></para>
<para>Leave a working trail on the return when changes are made to the following items:<bulletlist>
<li>Tax Period (Field 01TXP)</li>
<li>Name Control (01NC)</li>
<li>Primary Social Security Number (01PS)</li>
<li>Return Processing Code (01RPC)</li>
<li>Audit Code (01ACD)</li>
<li>Special Processing Code (01SPC)</li>
<li>Computer Condition Code (01CCC)</li>
</bulletlist></para>
<para>When working Rejects re-input, circle out any previous Action codes shown on the front of the return, if no longer applicable.</para>
<para>When working Rejects, write <emphasis type="q">Voided</emphasis> with the date above the DLN, when voiding a return.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100007"><date>(01-01-2025)</date>
<title>Miscellaneous Related Forms</title>
<para>This subsection of the manual contains a listing of the miscellaneous forms used in error resolution procedures. The forms below can be found on the Forms/Pubs/Products Repository and/or the Rejects Job Aid 2532-701.</para>
<para> Refer below for a listing of forms and their uses. <table frame="all" id="id337100860" summary="Miscellaneous Forms and descriptions" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">MISCELLANEOUS FORMS</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">DESCRIPTIONS </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">Form 813 - Document Register</entry>
<entry colsep="1" rowsep="1">Used to list transaction amounts for remittance or assessment documents to be processed with a new Document Locator Number (DLN).</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 1332 - Block and Selection Record</entry>
<entry colsep="1" rowsep="1">Used to process non-remittance documents with a new DLN. It is usually prepared by the Numbering Unit. </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 2275 - Records Request, Charge and Recharge </entry>
<entry colsep="1" rowsep="1">Used to request documents from Returns File Unit and Federal Record Center. It is also used to replace a document that is sent to Rejects when no Form 813 or Form 1332 is present. Use a single copy as a replacement.</entry>
</row>
<row>
<entry>Form 2424 - Account Adjustment Voucher</entry>
<entry>Used to transfer money from one account to another account.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3210 -Document Transmittal</entry>
<entry colsep="1" rowsep="1">Used to transmit documents to be worked by other Submission Processing campus functions. These documents will normally be returned to Rejects to be corrected.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3244 - Payment Posting Voucher</entry>
<entry colsep="1" rowsep="1">Used to post a remittance that cannot be processed with the document with which it was received.</entry>
</row>
<row>
<entry>Form 3245 - Posting Voucher Refund Cancellation or Repayment</entry>
<entry>Used to reverse refunds or cancel payments.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3465 - Adjustment Request Form </entry>
<entry colsep="1" rowsep="1">Used to request transfers of credits by Accounts Management or other areas.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3471 - Edit Sheet</entry>
<entry colsep="1" rowsep="1">Used by Code and Edit to edit ERS Section 02 data.</entry>
</row>
<row>
<entry>Form 3499 - Informational Transmittal</entry>
<entry>Used to transship International returns to AUSPC and BMF returns to Ogden. </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3531 - Request for missing Signature or Missing Information to Complete Return</entry>
<entry colsep="1" rowsep="1">Used when returning a tax return back to the taxpayer.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3696/3696A - Correspondence Action Sheet </entry>
<entry colsep="1" rowsep="1">Used to initiate correspondence to the taxpayer through Integrated Data Retrieval System (IDRS) or Clerical Unit.</entry>
</row>
<row>
<entry>Form 3753 - Manual Refund Posting Voucher</entry>
<entry>Used in Rejects to prepare Manual Refunds for Accounting.</entry>
</row>
<row>
<entry>Form 3809 - Miscellaneous Adjustment Voucher </entry>
<entry>Used for Non-Revenue Receipt credit transfer and will be processed immediately. </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 3893 - Re-entry Document Control</entry>
<entry colsep="1" rowsep="1">Used to reenter documents with original DLNs. </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 4028 - SCCF Adjustment Record Form</entry>
<entry colsep="1" rowsep="1">Used by Accounting to remove, establish, and adjust records or money on the Service Center Control File (SCCF). For reject documents, Form 4028 is prepared by Rejects and routed to Accounting. At the option of the Submission Processing Campus Accounting Operation, Form 4028 may be bypassed in favor of direct input of SCCF adjustments using Command Code (CC) SCFAJ.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4028-A - Service Center Control File Renumber Adjustment Record</entry>
<entry colsep="1" rowsep="1">Used to delete a DLN from the SCCF and simultaneously establish a new DLN for the same count and amount.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 4227 - Intra-SC Reject or Routing Slip</entry>
<entry colsep="1" rowsep="1">Used by Document Perfection and Input Correction Tax Examiners to identify the reason for rejection or suspension.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 4251- Return Charge-Out</entry>
<entry colsep="1" rowsep="1">Used by various functions to charge out a document from a block.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 4338 - Information or Certified Transcript Request</entry>
<entry colsep="1" rowsep="1">Used to request copies of the unit ledger card for ANMF subsequent and advance payments.</entry>
</row>
<row>
<entry>Form 5260 - Quick Note</entry>
<entry>Used when no IDRS letter is suitable or used for a less formal request for information or action.</entry>
</row>
<row>
<entry>Form 5792 - Request for IDRS Generated Refund</entry>
<entry>Used in Rejects to prepare Manual Refunds.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 6001 - Letter 12C Correspondence Action Sheet</entry>
<entry colsep="1" rowsep="1">Used to request missing information for IMF tax returns on IDRS.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 6826 - Error/Reject Display Request Card </entry>
<entry colsep="1" rowsep="1">Used to designate the print and sort requirements for SCRS error and reject registers and listings.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 6882 - IDRS/Master File Information Request </entry>
<entry colsep="1" rowsep="1">Used to alert the IDRS researcher of what research is to be conducted.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 8161 - ERS Returns Charge-Out </entry>
<entry colsep="1" rowsep="1">Used to charge out ERS returns on the New Suspense list, Rejected Records List, and Duplicate Document DLN Register. Input Correction will also use as a routing slip and history item.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 8749 - Unpostable Action and Routing Slip</entry>
<entry colsep="1" rowsep="1">Used in Unpostables and Entity to identify reason for reject.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 9856 - Attachment Alert</entry>
<entry colsep="1" rowsep="1">Used to transmit return information to the Files Storage Area.</entry>
</row>
<row>
<entry>Form 12857 - Refund Transfer Posting Voucher</entry>
<entry>Used in Rejects to process manually prepared refunds.</entry>
</row>
<row>
<entry>Form 13900 - Letter 4087C Correspondence Action Sheet</entry>
<entry>Used to request missing information for IMF tax returns on IDRS. (AUSC only)</entry>
</row>
<row>
<entry>Form 13975 - Letter 2894C/SP Correspondence Action Sheet</entry>
<entry>Used to request missing information for IMF tax returns on IDRS. (AUSC only)</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection2>
<subsection2 id="id337100009"><date>(01-01-2025)</date>
<title>IMF Forms</title>
<para> The IMF Forms chart below contains a listing of the forms corrected on the terminal via Error Resolution System (ERS).</para>
<para>Forms 1040A and 1040EZ are historical beginning in tax year 2018. Form 1040-NR-EZ are historical beginning in tax year 2020.</para>
<para> Below are the forms used and the description of each form:<table frame="all" id="id337100861" summary="IMF Forms listing and descriptions of each form" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">FORMS </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">DESCRIPTION </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">Form 1040</entry>
<entry colsep="1" rowsep="1">U.S. Individual Income Tax Return</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 1040-ES</entry>
<entry colsep="1" rowsep="1">U.S. Declaration of Estimated Income Tax for Individuals</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 1040-NR</entry>
<entry colsep="1" rowsep="1">U.S. Nonresident Alien Income Tax Return (AUSPC Only)</entry>
</row>
<row>
<entry>Form 1040-SP</entry>
<entry>U.S. Individual Tax Return in Spanish</entry>
</row>
<row>
<entry>Form 1040-SR</entry>
<entry>U.S. Income Tax Return for Seniors </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Form 1040-SS/Form 1040-SS(sp)</entry>
<entry colsep="1" rowsep="1">U.S. Self-Employment Tax Return-U.S.Virgin Islands, Guam, American Samoa,CNMI, Puerto Rico (AUSPC Only)</entry>
</row>
<row>
<entry>Form 4868</entry>
<entry>Application for Automatic Extension of Time to File U.S. Individual Income Tax Return</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection2>
<subsection2 id="id337100013"><date>(03-11-2024)</date>
<title>Related Reports</title>
<para>The table below provides a list of related Control D reports. This is not an all-inclusive list. It is intended to provide a basic point of reference. Go to Job Aid 2515–019 for more information. <table frame="all" id="id337100862" summary="ERS report numbers and descriptions" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="7.31in"?>
<colspec colname="col1" colwidth="49*"/>
<colspec colname="col2" colwidth="51*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">ERS REPORTS</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">DESCRIPTION </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>CRX-0316</entry>
<entry>LETTER INPUT DATA FROM ILITS</entry>
</row>
<row>
<entry>CRX-0340</entry>
<entry>DAILY LETTER USE REPORT</entry>
</row>
<row>
<entry>PARAGRAPH COUNTS</entry>
<entry>DAILY 12C PARAGRAPH COUNTS REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-00-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION END OF YEAR INVENTORY REPORT </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-01-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION AVAILABLE INVENTORY REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-01-41</entry>
<entry colsep="1" rowsep="1">ERROR LIST REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-01-42</entry>
<entry colsep="1" rowsep="1">PAS CHARGE-OUT FILE (Form 8161)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-01-43</entry>
<entry colsep="1" rowsep="1">PROGRAM ANALYSIS SELECTION REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-01-44</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION ELECTRONIC FILED RETURNS LIST </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-03-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION UNSELECTED RECORDS INVENTORY </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-03-41</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION SELECTION METHOD</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-05-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION REJECTED RECORDS LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-05-41</entry>
<entry colsep="1" rowsep="1">REJECTED-REC-CHARGE-OUTS</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-07-40 </entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION UNWORKABLE SUSPENSE INVENTORY </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-07-41</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION UNWORKABLE SUSPENSE INVENTORY SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-13-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION ERROR INVENTORY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-13-41</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION ERROR INVENTORY SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-13-42</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION WORKABLE SUSPENSE INVENTORY </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-13-43</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION WORKABLE SUSPENSE INVENTORY SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION NEW SUSPENSE LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-41</entry>
<entry colsep="1" rowsep="1">NEW-SUSP-CHARGE-OUT (Form 8161)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-42</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION DUPLICATE DOCUMENT DLN REGISTER </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-43</entry>
<entry colsep="1" rowsep="1">DUP-DLN-CHARGE-OUT (Form 8161)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-44</entry>
<entry colsep="1" rowsep="1">IMF INTEREST JEOPARDY REPORT – ERROR FILE </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-45</entry>
<entry colsep="1" rowsep="1">IMF INTEREST JEOPARDY REPORT – SUSPENSE FILE</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-46</entry>
<entry colsep="1" rowsep="1">IMF INTEREST JEOPARDY REPORT SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-47</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION INVENTORY CONTROL REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-17-48</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION NEW SUSPENSE LIST SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-19-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION DUPLICATE DOCUMENT DLN REPORT BY INVENTORY SOURCE</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-31-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION UNWORKABLE SUSPENSE AGED REPORT </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-31-41</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION WORKABLE SUSPENSE REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION REPORT – ERROR CORRECTION</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-41</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION SUMMARY – ERROR CORRECTION</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-42</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION REPORT – SUSPENSE CORRECTION BY PROGRAM</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-43</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION SUMMARY – SUSPENSE CORRECTION BY PROGRAM</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-44</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION REPORT – SUSPENSE CORRECTION BY STATUS</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-45</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION PRODUCTION SUMMARY – SUSPENSE CORRECTION BY STATUS</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-46</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION DAILY EMPLOYEE TIME REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-77-47</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION DAILY EMPLOYEE TIME REPORT SUMMARY </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-83-40</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION QUALITY REVIEW REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-83-41</entry>
<entry colsep="1" rowsep="1">DAILY ERS REVIEW QUALITY REVIEW CHARGE-OUT (Form 8161)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-83-42</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION QUALITY ASSURANCE HOLD REPORT </entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERS-83-44</entry>
<entry colsep="1" rowsep="1">ERROR RESOLUTION QUALITY ASSURANCE REWORKED REPORT </entry>
</row>
<row>
<entry colsep="1" rowsep="1">MER-03-40</entry>
<entry colsep="1" rowsep="1">ERROR COUNT REPORT DAILY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">MER-03-41</entry>
<entry colsep="1" rowsep="1">ERROR COUNT REPORT YEAR-TO-DATE</entry>
</row>
<row>
<entry colsep="1" rowsep="1">MER-13-40</entry>
<entry colsep="1" rowsep="1">PROGRAM ANALYSIS REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">MERDAIL</entry>
<entry colsep="1" rowsep="1">ERROR COUNT REPORT MeF DAILY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">MERYRDT</entry>
<entry colsep="1" rowsep="1">ERROR COUNT REPORT ELF YEAR-TO-DATE</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-10-40</entry>
<entry colsep="1" rowsep="1">ERROR DISPLAY RUN CONTROL REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-10-41</entry>
<entry colsep="1" rowsep="1">ERROR REGISTER RAW/LOOP</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-10-42</entry>
<entry colsep="1" rowsep="1">ERROR PULL LIST RAW/LOOP/SUMMARY</entry>
</row>
<row>
<entry>GMF-10-43</entry>
<entry>DAILY ERROR VOLUME REPORT/SUMMARY</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-40</entry>
<entry colsep="1" rowsep="1">REJECT REPORTS RUN CONTROL REPORT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-41</entry>
<entry colsep="1" rowsep="1">REJECT RE-INPUT TRANSMITTAL</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-42</entry>
<entry colsep="1" rowsep="1">REJECTED AGED LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-43</entry>
<entry colsep="1" rowsep="1">REJECT INVENTORY LIST (DLN Sequence)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-44</entry>
<entry colsep="1" rowsep="1">REJECT PULL LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-45</entry>
<entry colsep="1" rowsep="1">REJECT REGISTER RAW/LOOP</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-46</entry>
<entry colsep="1" rowsep="1">CURRENT REJECT LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-47</entry>
<entry colsep="1" rowsep="1">REJECT DISPOSITION LIST</entry>
</row>
<row>
<entry colsep="1" rowsep="1">GMF-11-48</entry>
<entry colsep="1" rowsep="1">REJECT CORRECTION VERIFICATION LIST</entry>
</row>
<row>
<entry>GUF 55-47</entry>
<entry>NULLIFIED DISTRIBUTION LIST</entry>
</row>
<row>
<entry colsep="1">SCF-11-48</entry>
<entry colsep="1">NEW DLN RECORD LIST</entry>
</row>
<row>
<entry>SCF-11-51</entry>
<entry>TAPE CONTROL RECORD LISTING</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection2>
<subsection2 id="id337101744"><date>(01-01-2026)</date>
<title>Sources of Rejects</title>
<para>Records are identified and coded for Rejects or ERS suspense from several different sources.<bulletlist>
<li>Code &amp; Edit</li>
<li>Error Correction</li>
<li>Unpostables</li>
</bulletlist></para>
<subsection3 id="id337101676"><date>(01-01-2026)</date>
<title>Code &amp; Edit Function</title>
<para>An Action Code is entered on the source document and transcribed as part of the record when a tax examiner determined that research or correspondence is required on a numbered document. A valid Action Code will place the record in the unworkable suspense inventory for a predetermined number of days or in the workable suspense inventory to be resolved immediately.</para>
</subsection3>
<subsection3 id="id337101677"><date>(01-01-2026)</date>
<title>Error Correction Function</title>
<para>When an ERS examiner has determined that additional information is needed for processing a return they will enter CC SSPND with a valid Action Code.</para>
<para>An error correction tax examiner will enter Action Code 3 on the register to move the register from ERS to Reject inventory for further research. </para>
</subsection3>
<subsection3 id="id337101678"><date>(01-01-2026)</date>
<title>Unpostables Function</title>
<para>Certain unpostable records, determined to be uncorrectable on the Generalized Unpostable File (GUF), are rejected and automatically established on an ERS workable suspense record.</para>
<para>A tax examiner nullifies an unpostable document with Unpostable Resolution Code (URC) <emphasis type="b">8</emphasis>.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101745"><date>(01-01-2026)</date>
<title>Error Resolution System Capacity</title>
<para>The real-time portion of the Error Resolution System has a capacity of approximately 1 million Form 1040 records per campus. The capacity may be set higher as individual campuses deem necessary. <alphalist>
<li>Up to 30,000 records may be retained on the Quality Review File, so the effective capacity for real-time planning is 400,000 records.</li>
<li>The ERS programs will run more efficiently with fewer records on the file. If the system approaches capacity, it may be difficult to have ERS real-time available by the beginning of the shift the next day because the nightly update may not have been completed.</li>
<li>Although the ERS database can hold several days of inventory, the campuses will strive to keep each Master File's inventory that is day 5 or older at less than five percent (5%) of that Master File's total inventory (e.g., if the sum of IMF ERS cases from the ERS-13-41 Report is 100,000 cases, that means inventory that is day 5 or older must not be 5,000 or more).</li>
</alphalist></para>
<para>An ERS inventory threshold has been established where up to 50,000 records are automatically added to the error file. This would happen only if the entire workable suspense file had been worked. <alphalist>
<li>An automatic <emphasis type="b">ORDER ALL RECORDS</emphasis> will be made if the total of the unworked/unselected records is less than 70,000 records.</li>
<li>If the total of the unworked/unselected records will exceed the threshold, only the two oldest workgroups will be added. The system will keep a count of the two oldest workgroups.</li>
<li>If the addition of the two oldest workgroups will exceed the threshold, only the oldest workgroup will be added. If the oldest workgroup will exceed the threshold, only the predetermined program (43110) will be added automatically. </li>
<li>No inventory will be automatically added to the system if the threshold will be exceeded unless a selection is made.</li>
</alphalist></para>
<para>The Input Correction Operation has the ability to select any or all of the unselected records that are available. However, if the total workable inventory (error, suspense, and quality review) is permitted to exceed capacity, the excess will be placed in overflow status. <alphalist>
<li>Because the ERS file is maintained in DLN sequence, the records with the highest DLNs, regardless of status or days in inventory, will move to the temporary <emphasis type="b">overflow</emphasis> inventory.</li>
<li>All overflow records will appear on the ERS control file with status 999. </li>
<li>During the nightly update, if the size of the workable file has been reduced, overflow records will be automatically transferred back to the workable inventory. </li>
<li>In overflow status, the record is not accessible with any command code or included on any inventory list. The record is available only for research on the ERS control file with CC ERINV.</li>
</alphalist></para>
<para>Although unselected records will be automatically added to the ERS error file, Input Correction Operation managers will monitor the inventory levels to ensure that adequate work will be available for the next day. <alphalist>
<li>After each GMF 27 and GMF 37 runs, records are loaded into the ERS01 file prior to selection for the real-time ERS system. Records are held in this file to be selected later for real-time. The Error Resolution Available Inventory Report will be received from the console printer in the Computer Operation. </li>
<li>A separate printout, Error Resolution Unselected Records Inventory (ERS–03–40) is in the same format as the Available Records Inventory and lists all ERS records being held in the unselected inventory. In addition, the Error Resolution Selection Method (ERS–03–41) lists the records selected and the identification number of the employee making the selection. </li>
</alphalist></para>
<subsection3 id="id337101734"><date>(01-01-2026)</date>
<title>Command Code ERVOL</title>
<para>Command Code ERVOL may be used to estimate, view, and select records for ERS processing.</para>
<para>Each day compare the Grand Total Error Records count to the count from ERVOL 100 to estimate the unselected records that will be automatically added to ERS during nightly processing. Remember that Workable Suspense records are always added automatically to the real-time file and must be taken into consideration due to limited system capacity.</para>
<para>If the automatic selection will exceed the established threshold, but it has been determined that all records will be added to ERS, enter CC ERVOL, space once and <emphasis type="b">ORDER ALL RECORDS.</emphasis></para>
<para>If only a limited number of records will be added, enter CC ERVOL, space once, and <emphasis type="b">INVENTORY DISPLAY</emphasis></para>
<subsection4 id="id337101735"><date>(01-01-2026)</date>
<title>Viewing and Selecting Records from the Available Records Inventory</title>
<para>There are two screens available for viewing and/or selecting. The two screens display the program number and available inventory. Each page/screen shows the program number and available workable inventory as it appears in the data base.</para>
<para>When ordering by program number from one page/screen only: <alphalist>
<li><emphasis type="b">Page</emphasis> (position cursor on line 24 position 47 and transmit) to needed page/screen.</li>
<li>Select program number(s) and enter amount(s) to order or enter <emphasis type="b">ALL</emphasis> to order all inventory of selected program(s).</li>
<li>Transmit from line 23 or below last item on page/screen.</li>
</alphalist></para>
<para>When ordering from more than one page/screen: <alphalist>
<li>Enter <emphasis type="b">ERVOL INVENTORY DISPLAY</emphasis></li>
<li>Select program number(s) and enter amount(s) to order or enter <emphasis type="b">ALL</emphasis> to order all inventory of selected program(s).</li>
<li>Transmit from line 23 or below last item on page/screen.</li>
<note>ERVOL ORDER BY PROGRAM must appear at top left corner when ordering. This is issued by the program. Do not attempt to input this command or the program will abort.</note></alphalist></para>
<para>After records have been ordered, the first page/screen of the series will display the message <emphasis type="b">REQUEST COMPLETED-ORDER AS FOLLOWS:</emphasis> This message will appear on all pages/screens. The page/screen will display all the program numbers along with the selected inventory ordered.</para>
<para>Within each program, the oldest records are automatically selected. Within an inventory day, records are selected in DLN sequence up to the end of the batch in which the requested volume has been reached.</para>
<para>Selections made using CC ERVOL can be changed at any time during the workday. If a selection is not made, the automatic selection procedures will be employed.</para>
</subsection4>
<subsection4 id="id337101736"><date>(01-01-2026)</date>
<title>Viewing and Selecting Records from the Error Resolution Unselected Records Inventory</title>
<para>Selective ordering of documents is available as well as moving from screen 1 to screen 2. <alphalist>
<li>To view the documents on the second screen, position cursor on line 24, column 47 of screen 1 and transmit.</li>
<li>To return to the first screen, position the cursor at the bottom of the screen 2 on line 24, column 47 and transmit.</li>
</alphalist></para>
<para>To order records from the first screen, enter number of documents requested in each program and transmit on line 23.</para>
<para>Ordering from the second screen requires entering <emphasis type="b">ERVOL INVENTORY DISPLAY</emphasis> going to the second page/screen and making individual selections.</para>
<para>To selectively order records on the second screen, make your selections then position the cursor on any line below the last item on this screen and transmit.</para>
<para>Within each program, the oldest records are automatically selected. Within an inventory day, records are selected in DLN sequence up to the end of the batch in which the requested volume has been reached.</para>
<para>To request all documents for a program, enter <emphasis type="b">ALL</emphasis> then transmit. <note notetype="note">Command Code ERVOL will only order programs from the first screen and not the second screen unless you go back to the <emphasis type="b">ERVOL ORDER ALL RECORDS</emphasis> and go to the second page and order <emphasis type="b">ALL</emphasis>.</note></para>
</subsection4>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337100016"><date>(01-01-2026)</date>
<title>Clerical Guidelines</title>
<para>This subsection of the manual lists control clerk procedures. Control clerk duties include: <bulletlist>
<li>Receiving, sorting and distributing work</li>
<li>Controlling documents</li>
<li>Inputting correspondence</li>
<li>Controlling registers</li>
<li>Maintaining suspense files and charge out</li>
<li>Fulfilling other clerical functions as assigned</li>
</bulletlist></para>
<subsection2 id="id337100017"><date>(01-01-2025)</date>
<title>Control of Error Documents</title>
<para>The control clerk is responsible for controlling error documents including: <bulletlist>
<li>Controlling transcription carts</li>
<li>Alpha Block Control Number (ABC) Listing or Batch Transmittals</li>
<li>Document withdrawal requests</li>
</bulletlist></para>
<subsection3 id="id337100018"><date>(11-10-2021)</date>
<title>Controlling Transcription Carts</title>
<para>All returns and documents are routed to Cycle Control Unit after transcription is completed. Prioritize cart order as follows:<alphalist>
<li>Correspondence Carts (CORR)</li>
<li>Block Out of Balance Cart(s) (BOB) - Blocks are pulled from the regular error carts and routed to the BOB resolution function. The blocks are returned and placed on separate carts after resolution; they will be identified by new work group after resolution. The information on the cart does not need to be entered in Batch Block Tracking System (BBTS), the write-up sheet is pre-written and attached to the front of the cart(s).</li>
<li>Prior Year Carts (PY)</li>
<li>Current Year Carts (CY)</li>
<li>Miscellaneous Cart (MISC) - The write-up sheet is pre-written and attached to the front of the cart(s) by the clerks.</li>
</alphalist></para>
<para>Separate carts by program code order smallest to the largest, then block order smallest to largest within Domestic, ITIN, &amp; International returns.</para>
<para>Label each cart according to local procedures for <emphasis>Control Day = Julian Date</emphasis>, indicating the day the work was received and the type of documents on the cart. Complete <emphasis>roadmap</emphasis> for carts as follows:<alphalist>
<li>Prepare a list (i.e., <emphasis>roadmap</emphasis>) that shows all of the alphas and batches on each cart. This list will be prepared using (BBTS) <citation type="IRM">IRM 3.10.5.5</citation>, Batch/Block Tracking System.</li>
<li>This <emphasis>roadmap</emphasis> may be combined with a program to verify that each block actually received in Cycle Control Unit was released from Integrated System Remittance Processing (ISRP). <note notetype="note"> Do not depend on the Batch Transmittals to list blocks actually received. Check each block against the transmittal or a separate listing prepared to verify blocks actually received.</note></li>
</alphalist></para>
<para>Retain document carts until: <alphalist>
<li>SCRS—the first loop register has been worked, or three days.</li>
<li>ERS—all items in error inventory have been worked.</li>
</alphalist></para>
<para>Identify all documents based on the Julian date to maintain effective control.</para>
<para>If a document is not removed to Files within 4-5 days, maintain all documents in a researchable order by work group so that the documents can be pulled by Files personnel. Route completed carts to Files or a designated staging area. <note notetype="exception">Route <citation type="Form">Form 1096</citation> processed on ISRP to the Data Conversion Operation Control area or SCRIPS unit for retention imaging instead of sending the carts to Files. Local Procedures designates which area will receive the documents for imaging once ERS processes are complete.</note></para>
<subsection4 id="id337100019"><date>(01-01-2023)</date>
<title>Alpha Block Control Number (ABC) Listing or Batch Transmittal</title>
<para>Check each block of documents (including single-document re-inputs) off the ABC listing or the Batch Transmittal as it is associated with the ERS-13-40, Error Resolution Error Inventory. Remove any <emphasis>left-over</emphasis> blocks that haven’t been pulled for BOBs, Data Conversion, or Accounting and containing no errors from the cart. Verify the blocks have processed using the Service Center Control File (SCCF). </para>
<para>Use any ERS terminal to input Command Code (CC) SCFTR to verify the block has been processed. Enter the following format: <bulletlist>
<li>enter <emphasis>SCFTR</emphasis></li>
<li>a blank space</li>
<li>enter the Master File Code <br/>(IMF–1, Information Returns Processing IRP–5, or<br/> Automated Non-Master File ANMF–6)</li>
<li>enter the 12,3–digit block Document Locator Number (DLN) (without hyphens),</li>
<li>transmit<note notetype="example">block 00221-056-003-8, enter SCFTR 1002210560038.</note></li>
</bulletlist></para>
<para>The response screen will indicate that the block has already been processed by showing the 0–5 (or 1–5) control record with the entire count of the block and machine Alpha Block Control Number (ABC). The error, reject, and suspense counts in the header will be blank for original blocks. For reentries, the ABC and serial number of the 0–5 or 1–5 control record will match the Form 3893.</para>
<para>Use the SCF–11–51, Tape Control Record List, as an alternative.</para>
<para>If any <emphasis>left-over</emphasis> blocks cannot be located on the SCCF, research using the following steps: <alphalist>
<li>Check for unassociated error registers, Error Inventory listings or BOB registers for two days before and after current date.</li>
<li>For ERS documents, research using CC ERINV.</li>
<li>Recheck the SCRS tape listing and ISRP mismatch listing back and forward at least two days.</li>
<li>Check the Edit Reject List.</li>
<li>Check leftover error, ERS, and BOB listings for matching alpha and batch number, indicating that the block has been input with the wrong DLN.</li>
<li>Research the Batch Transmittals to determine when the block was to be input.</li>
<li> If unsuccessful, leave the block with the Data Control Unit as a potential unprocessed block.</li>
</alphalist></para>
</subsection4>
</subsection3>
<subsection3 id="id337100020"><date>(11-10-2021)</date>
<title>Document Withdrawal Requests</title>
<para>Files processes most document requests. Control clerks process priority document requests when the blocks are located in Error Correction. </para>
<para>Form 2275 or Form 4251 will be received for each document to be pulled for other campus functions. Attach the original record request to the document being pulled. File the second copy in the block the document was removed from as a substitute for the document and document trail. </para>
<para>Every ERS suspense document has a 3-part Form 8161 attached. <alphalist>
<li>Use the original to pull or replace the document in Files.</li>
<li>Detach copy two and retain in a suspense file.</li>
<li>Keep copy three with the document to inform the receiving area that the document is controlled by ERS.<note>If the documents are hand carried to the receiving function, the second copy of the Form 8161 may be signed as a receipt. A separate routing form such as a Form 3210 may be used in the place of the Form 8161.</note></li>
</alphalist></para>
<para>Form 8161 is received as a charge-out for ERS suspense documents and deleted ERS documents.</para>
<para>Form 8161 identified as <emphasis>Program Analysis</emphasis> charge-outs must be placed on top of the appropriate cart and used to pull the documents immediately before the cart is released to Files.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101324"><date>(11-10-2021)</date>
<title>ERS Suspense Document Control</title>
<para>This subsection of the manual lists the procedures to be followed for pulling ERS suspense documents. <bulletlist>
<li>Pulling ERS Suspense Documents, ERS-17-40</li>
<li>Disposition of documents</li>
</bulletlist></para>
<subsection3 id="id337101298"><date>(01-01-2025)</date>
<title>Pulling ERS Suspense Documents, ERS-17-40</title>
<para>Receive the New Suspense List and accompanying charge-outs for each record assigned to ERS Suspense.</para>
<para>The Error Resolution New Suspense List identifies the source of each record to assist in locating the documents. </para>
<para>Pull documents listed as suspended by Code and Edit from the ISRP carts received for that day and complete the following procedures:<alphalist>
<li>Replace each document removed from its block with the original copy of its charge-out.</li>
<li>Attach the remaining copy of the charge-out to the removed document. </li>
<li>If the document is missing, indicate on both copies of the charge-out and on the New Suspense List that it is missing. Date and initial your entry on the New Suspense List and notify the work lead. The work lead will follow instructions in <citation type="IRM">IRM 3.12.2.2.5.1.3</citation> to locate a missing block of work or missing documents.</li>
</alphalist></para>
<para>Pull each document from the carts suspended by ERS shown on the New Suspense List. <alphalist>
<li>Replace each document removed from its original block with the original copy of its associated charge-out.</li>
<li>Attach one copy of the charge-out to the removed document.</li>
<li>If the document is missing, indicate on both copies of the charge-out and on the New Suspense List that it is missing. Date and initial your entry on the New Suspense List and notify the work lead. The work lead will follow instructions in <citation type="IRM">IRM 3.12.2.2.5.1.3</citation> to locate a missing block of work or missing documents.</li>
</alphalist></para>
<para>Verify receipt of all New Suspense List documents received from the Unpostable Unit.<alphalist>
<li>Associate the charge-outs with the unpostable documents.</li>
<li>Forward the original of the charge-outs to Files for all unpostable documents received from the Unpostable Unit.</li>
<li>Attach the remaining copies to the unpostable document.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101299"><date>(01-01-2026)</date>
<title>Disposition of Documents</title>
<para>This subsection refers to several different suspense files. These files may be maintained separately or combined in a single <emphasis type="b">ERS</emphasis> suspense file. The ERS automated control system will be easier to maintain by using a single ERS suspense file. </para>
<para>The Action Code printed on the charge-out indicates the disposition of the paper document or MeF Section 01 Print. </para>
<para><emphasis type="b">Action Code 21X &amp; 22X—Correspondence:</emphasis><alphalist>
<li>Place the paper document and charge-out in the Correspondence suspense basket to be batched by ACA, SSPND 224 and Non-ACA, SSPND 211.</li>
</alphalist></para>
<para><emphasis type="b">Action Code 370 — Examination Review:</emphasis><alphalist>
<li>Place the paper documents and charge-out in the folder or basket for review by Examination.</li>
<li>Examination will visit the Rejects area to work the case.</li>
</alphalist></para>
<para><emphasis type="b">Action Codes 310, 320, 333, 34X, 360 — Suspense to Other Functions:</emphasis><alphalist>
<li>Use the second copy of the charge-out as a routing slip to the designated function in the campus.</li>
<li>Detach the copy of the charge-out and place in a suspense folder for the designated function in DLN order.</li>
<li>If the document must be routed to another area, complete <citation type="Form">Form 3210</citation> to route the paper document.</li>
</alphalist></para>
<para><emphasis type="b">Action Codes 351, 6XX, 700, 900 — Workable Suspense:</emphasis><alphalist>
<li>Associate the paper document with the current Workable Suspense Inventory report. </li>
<li>If the document must be routed to another area, complete <citation type="Form">Form 3210</citation> to route the paper document.</li>
</alphalist></para>
<para><emphasis type="b">Action Codes 491 through 499 — Management Suspense:</emphasis><alphalist>
<li>Take returns to the Rejects unit for processing.</li>
<li>The file must be maintained in DLN order, unless otherwise instructed. </li>
</alphalist></para>
<para><emphasis type="b">Action Code 511 — Missing Documents:</emphasis><alphalist>
<li>If the document is not available, place the copy of the charge-out in the missing document suspense in DLN order. The first and second copies of the charge-out are used to initiate a special search.</li>
<li>If the document is attached for Action Codes 511, input CC ACTVT and route the document and charge-out for association with the Workable Suspense Inventory report on the following day.</li>
</alphalist></para>
<para>In order to prevent returns from being sent to Files in error, all completed Rejects work must be checked by using CC ERINV for a status prior to releasing the returns to Files. Only release returns to Files that are no longer in an ERS suspense status. Any returns reflecting an ERS status will be returned to the Rejects function for resolution.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101325"><date>(01-01-2020)</date>
<title>Error Resolution System (ERS) Reports</title>
<para>This subsection of the manual provides information about the ERS reports. </para>
<para>Information in this subsection includes the following: <bulletlist>
<li>Error Resolution Inventory Control Report, ERS–17–47</li>
<li>Error Resolution Error Inventory Summary, ERS–13–41</li>
<li>Error Resolution Error Inventory, ERS–13–40</li>
</bulletlist></para>
<subsection3 id="id337101301"><date>(01-01-2023)</date>
<title>Error Resolution Inventory Control Report, ERS-17-47</title>
<para>The ERS Inventory Control Report, ERS–17–47, is a one-page summary of activity for each of the ERS files. <alphalist>
<li>This daily report is used to provide an overview of the ERS inventories. </li>
<li>The report shows the number of records added and removed from each inventory daily. Items in the Quality Review File are included in the ending inventory counts for Errors and Workable Suspense.</li>
</alphalist></para>
<para>The primary purpose of this report is to provide Data Control Unit a simplified method of balancing the ERS to the SCCF.</para>
</subsection3>
<subsection3 id="id337101302"><date>(01-01-2023)</date>
<title>Error Inventory Summary, ERS-13-41</title>
<para>The ERS Error Inventory Summary Report, ERS-13-41, shows the volume of error records by ascending program number with a total for each Master File. Separate reports are produced by the number of working days the records remain unworked in the error inventory. This report is available daily. </para>
<para>The report is used for management control of the inventory and work planning and control.</para>
</subsection3>
<subsection3 id="id337101314"><date>(01-01-2023)</date>
<title>Error Inventory, ERS-13-40</title>
<para>The ERS Error Inventory Report, ERS-13-40, lists the error records by the number of days in working inventory with their Block DLN. This report is printed daily. Separate inventories are printed for:<bulletlist>
<li>Each Master File</li>
<li>Each Program number</li>
</bulletlist></para>
<para>Use this report to assign work to tax examiners, to associate documents with error records, and to release documents from previous day’s workload, retaining only those for the unworked records.</para>
<para>Separate reports are printed showing the records in inventory by the number of working days the records have been in the inventory.</para>
<para>Separate reports are printed for each Batch number showing the following information items: <bulletlist>
<li>Block Control Number</li>
<li>Block DLN</li>
<li>Error Count for each Block</li>
<li>Control date of data entry through ISRP and GMF</li>
<li>Ascending DLN order within each Batch</li>
<li>Total error count for each Batch</li>
</bulletlist></para>
<para>Separate reports are available for Blocks received from BOB Correction. </para>
</subsection3>
</subsection2>
<subsection2 id="id337101746"><date>(01-01-2026)</date>
<title>Clerical Letter Input</title>
<para>This subsection of the manual lists the procedures for:<bulletlist>
<li>Batching</li>
<li>Letter Tool Set-up</li>
<li>Input of Correspondence</li>
<li>ICO Letter Inventory Tracking System (ILITS) Tool</li>
</bulletlist></para>
<subsection3 id="id337101680"><date>(01-01-2026)</date>
<title>Batching</title>
<para>This subsection of the manual lists the Batching procedures for the suspended and Non-Pending Correspondence to be entered by Letter Input Clerical Teams.<note><emphasis type="b">All documents are batched in Suspense Date Order.</emphasis></note></para>
<para>Batch documents by Paper, area of suspense (Code &amp; Edit or ERS), 2nd Correspondence/Non-Pending, and special suspense codes.</para>
<para>Limit batches to <emphasis type="b">25 documents</emphasis> each. Assign each batch numerically in range or per local procedure based on type of correspondence. Notate batch number on each bundle and the log in order to ensure numbers are not reissued. </para>
<para>Bundle work by type and place on batch carts for letter processing by processing day. </para>
<subsection4 id="id337101681"><date>(01-01-2026)</date>
<title>Letter Tool Set-up</title>
<para>This subsection lists procedures performed to set-up the Letter tool prior to entering ICO Correspondence:<note>If inputting correspondence for another site, remember to CMODE and use the other site’s IDRS. See SERP for Command Code CMODE and Return Address codes.</note><alphalist>
<li>Open IAT on Desktop after logging into IDRS. </li>
<li>Open Letters and select Options: CAS Mode - Checked; View - Unchecked; User Settings to complete tabs.</li>
<li>Letter Tool Tab - the following listed items will be selected:</li>
<table frame="all" id="id337101728" summary="Letter Tool Tab">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Section</emphasis></entry>
<entry valign="top"><emphasis type="b">Action</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Tool Defaults</entry>
<entry>Check <emphasis type="b">Show Selected Only</emphasis></entry>
</row>
<row>
<entry>Tool Defaults</entry>
<entry>Default to DLN research</entry>
</row>
<row>
<entry>Tool Defaults</entry>
<entry>Populate form to applicable fill-ins</entry>
</row>
<row>
<entry>Tool Defaults</entry>
<entry>Populate plan numbers to IRS Control N.</entry>
</row>
<row>
<entry>Tool Defaults</entry>
<entry>Populate tax period to applicable fill-ins</entry>
</row>
<row>
<entry>Tool Defaults</entry>
<entry>Populate TIN to applicable fill-ins</entry>
</row>
<row>
<entry>F5703 Print</entry>
<entry>Manual</entry>
</row>
<row>
<entry>Letter Sent</entry>
<entry>Confirm transmit of CC LPAGE</entry>
</row>
<row>
<entry>Letter Sent</entry>
<entry>Clear fields after letters are successfully sent</entry>
</row>
<row>
<entry>Letter Sent</entry>
<entry>Close tool after letters are successfully sent</entry>
</row>
<row>
<entry>Sort Letters</entry>
<entry>Useage</entry>
</row>
<row>
<entry>Sort Scenarios</entry>
<entry>Useage</entry>
</row>
<row>
<entry>Sort Paragraphs</entry>
<entry>Useage</entry>
</row>
<row>
<entry>STAUPS</entry>
<entry>Checked (Cycles default of 03)</entry>
</row>
<row>
<entry>LPAGE Defaults</entry>
<entry>Number: 12C</entry>
</row>
<row>
<entry>LPAGE Defaults</entry>
<entry>Employee: (enter 10 IDRS Employee number)</entry>
</row>
<row>
<entry>LPAGE Defaults</entry>
<entry>Suspend: R</entry>
</row>
<row>
<entry>LPAGE Defaults</entry>
<entry>Ex-Spouse Copy: Unchecked</entry>
</row>
<row>
<entry>LPAGE Defaults</entry>
<entry>OMB, CB, &amp; PA: All Blank</entry>
</row>
<row>
<entry valign="middle">LPAGE Defaults</entry>
<entry>Return Address Code: Specific by Service Center - See <a href="https://serp.enterprise.irs.gov/databases/who-where.dr/signaturelist.dr/return-address-codes.html#Philadelphia" title="Correspondex Return Address Codes">Correspondex Return Address Codes (irs.gov)</a></entry>
</row>
</tbody>
</tgroup>
</table>
<note>Use CMODE when inputting correspondence for the primary site. </note>
<li>General Info Tab - Fill-in Name, Mailing Address, &amp; Manager’s Information fields. The following listed items will be selected:</li>
<table frame="all" id="id337101729" summary="General Info Tab">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Section</emphasis></entry>
<entry valign="top"><emphasis type="b">Action</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>IDRS</entry>
<entry>Minimize IDRS when researching: Checked</entry>
</row>
<row>
<entry>508-Compliance</entry>
<entry>Zoom Text User: Checked</entry>
</row>
</tbody>
</tgroup>
</table>
<li>Work Info Tab - Function and Program Codes &amp; Categories remain blank. The following listed items will be selected:</li>
<table frame="all" id="id337101730" summary="Work Info Tab">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Section</emphasis></entry>
<entry valign="top"><emphasis type="b">Action</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Organizational Information</entry>
<entry>BOD:TS SP</entry>
</row>
<row>
<entry>Organizational Information</entry>
<entry>Org: Input Corrections</entry>
</row>
<row>
<entry>Organizational Information</entry>
<entry>Area: Error Resolution</entry>
</row>
<row>
<entry>Organizational Information</entry>
<entry>Title: Clerk</entry>
</row>
<row>
<entry>Organizational Information</entry>
<entry>Team Number: Enter Unit 5-digit number</entry>
</row>
<row>
<entry>Organization Information</entry>
<entry>Badge Number: Varies by clerk</entry>
</row>
</tbody>
</tgroup>
</table>
<li>Letter Info Tab - the following listed items will be selected:</li>
<table frame="all" id="id337101731" summary="Letter tool setup">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Section</emphasis></entry>
<entry valign="top"><emphasis type="b">Action</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry valign="middle">Signature Code</entry>
<entry><steplist>
<li>Austin - CJ</li>
<li>Kansas City-CB</li>
<li>Ogden-AJ</li>
</steplist></entry>
</row>
<row>
<entry>Opening</entry>
<entry>None</entry>
</row>
<row>
<entry>Certified Mail Signature Code</entry>
<entry>Blank</entry>
</row>
<row>
<entry>Closing</entry>
<entry>None</entry>
</row>
<row>
<entry>800 Number</entry>
<entry>800-829-1040</entry>
</row>
<row>
<entry valign="middle">My Info</entry>
<entry><emphasis type="b">Fax: by Campus </emphasis><steplist>
<li>Austin paper -855-204-5020 </li>
<li>Austin MeF - 844-254-2836</li>
<li>Kansas City paper- 855-892-7588</li>
<li>Kansas City MeF - 844-254-2834</li>
<li>Ogden paper- 855-309-9361</li>
<li>Ogden MeF- 844-254-2835</li>
</steplist></entry>
</row>
<row>
<entry>My Info</entry>
<entry>All other fields to be complete by user.</entry>
</row>
</tbody>
</tgroup>
</table>
<li>Select Save</li>
</alphalist></para>
</subsection4>
<subsection4 id="id337101682"><date>(01-01-2026)</date>
<title>Input of Correspondence</title>
<para>Correspondence is input by tax examiners or clerical clerks following local procedures.</para>
<para>Input the letter using the IAT CAS Letter Tool. Refer to the Letter Job Aid at <a href="https://irsgov.sharepoint.com/:w:/r/sites/IAT/_layouts/15/WopiFrame.aspx?sourcedoc=%7B1494f8d3-f642-4d5d-97b0-72c0f25dff6a%7D&amp;CID=d7edc94f-9b70-4a45-a728-f7ec97183111" title="Letters Job Aid">Letters Job Aid</a>.</para>
<para>Input other Non-Pending C Letters using IAT as appropriate.</para>
<para>Correspondence must be issued as soon as possible, but <emphasis type="b">no later than 10 business days from the ERS Suspense date</emphasis>. If correspondence has <emphasis type="b">not</emphasis> been issued within 10 business days, ACTVT and resuspend return immediately and issue correspondence.</para>
</subsection4>
<subsection4 id="id337101683"><date>(01-01-2026)</date>
<title>ICO Letter Inventory Tracking System (ILITS) Tool</title>
<para>The ICO Letter Inventory Tracking System (ILITS) is an IAT tool used by the correspondence function to maintain and control the letter inventory. The tool performs three primary actions:<bulletlist>
<li>Add Case Controls</li>
<li>Close Single Case Controls, and</li>
<li>Purge Expired Case Controls</li>
</bulletlist></para>
<para>The CRX0316 Report is a daily report on Control-D, which contains the previous day’s letter input data. Use the<emphasis> <emphasis type="b">Add Case Control</emphasis></emphasis> feature daily to run the CRX0316 file through the ILITS tool. Case controls are added to display the Batch Number on CC ENMOD, which identifies where the document is located in the suspense file. This control will also show on the CCA4243 Overage Report with a list of the controls assigned to the employee who ran the tool.</para>
<para>Use the <emphasis><emphasis type="b">Generate Batch Sheets</emphasis></emphasis> feature to print all the batch sheets for that letter file. Associate each batch sheet with its related bundle and place the bundle in the suspense file in batch number order.</para>
<para>As correspondence <emphasis>replies</emphasis> are received, associate the reply with the return. Use the <emphasis><emphasis type="b">Close Single Case Control</emphasis></emphasis> feature and the SSN on the reply/return to close the case control on CC ENMOD and activate the return to Workable Suspense Inventory.<note><emphasis type="b">Do not</emphasis> perform a separate action with CC ACTVT.</note></para>
<para>Use the <emphasis><emphasis type="b">Purge Expired Case Controls</emphasis></emphasis> feature to run the weekly Overage Report through the tool to close the case controls on the No Reply documents. <emphasis>Do NOT activate No Reply documents</emphasis>. When the suspense period has expired, IDRS will automatically place the documents in the Workable Suspense Inventory.</para>
<para>Batch Sheet and Case Control Instructions to be run daily:<alphalist>
<li>Control-D filter, Report Name CRX0316</li>
<li>Verify and select correct day of work, click on Report and Select SAVE </li>
<li>Click on save and then select SAVE AS in the drop-down box and add the previous day’s date to the end of the file name</li>
<li>Select C-drive, Users, your SEID, My Documents, SBU, IAT, Save</li>
<li>Go to IAT Tool and select Generate Batch Sheets</li>
<li>Select Continue (a list will open in IAT of the CRX0316 saved in the C-drive) Select the previous day’s date, select Open - Batch sheets will print</li>
<li>After Batch sheets are complete select Add Case Control</li>
<li>Select Continue (a list will open in IAT of the CRX0316 saved in the C-drive) Select the previous day’s date and select Open</li>
<li>Once complete, close out of ILITS</li>
</alphalist></para>
</subsection4>
</subsection3>
<subsection3 id="id337101684"><date>(01-01-2026)</date>
<title>Correspondence Suspense File</title>
<para>When the correspondence letter has been prepared, place the return in a suspense file awaiting a reply from the taxpayer. <alphalist>
<li>File ERS paper documents in Batch Number order.</li>
<li>File non-pending and 2nd Correspondence in date order.</li>
</alphalist></para>
<para>Maintain each document and Correspondence Action Sheet in a suspense file for at least 20 days after the period given for the taxpayer to respond. <note>Only destroy Section 01 screen print and do not destroy taxpayer’s correspondence or taxpayer’s documentation. </note><emphasis>Do NOT activate No Reply documents</emphasis>. When the suspense period has expired, IDRS will automatically place the documents in the Workable Suspense Inventory. </para>
<para>If the taxpayer does not reply to a request and the suspense period has expired, pull the paper return from the suspense file and stamp it No Reply. MeF No Reply cases generate the ERS 13-42 Control-D report daily to work the cases and stamp it No Reply.</para>
<para>When the taxpayer's <emphasis>reply is received</emphasis>: <alphalist>
<li>Stamp letter with Rejects Unit received date, if not already date stamped. </li>
<li>For paper replies, associate the reply with document and Correspondence Action Sheet.</li>
<li>Check the envelope for remittance or additional information.</li>
<li> For paper replies, attach the envelope and Form 6001, Form 3696-A, Form 13900, or Form 13975. For MeF replies, attach the envelope to the reply.<note notetype="caution">If reply is received through Registered Letter, do not discard the envelope or contents.</note></li>
<li>Staple the letter and attachments to back of original paper document in the upper left-hand corner.</li>
<li>When correspondence replies are received, input CC ACTVT to move the returns to the Workable Suspense Inventory. See <seealso idref="id337100494">Exhibit 3.12.37-25</seealso>. If a reply to a MeF document shows <emphasis type="b">IN WORKABLE SUSPENSE</emphasis> add <emphasis type="b">reply box</emphasis> to field 94EXV or follow local procedures to leave a working trail of the reply for the MeF document.</li>
</alphalist></para>
<para>If a reply is received without the DLN or Batch number, research to obtain the correct DLN or Batch number. Use the following instructions to research:<alphalist>
<li>If the TIN is not available, use CC NAMEI or NAMES. </li>
<li>Use CC ERINV with the TIN to search for the DLN.</li>
<li>Use CC ENMOD with the TIN to search for the Batch Number.</li>
</alphalist><note>Review the document received to ensure it is a reply for ICO Correspondence. Return mis-routed documents to the originating location. See specific sections of <citation type="IRM">IRM 3.10.72</citation> Receiving, Extracting, and Sorting <citation type="IRM">IRM 3.10.72-1</citation>, Routing Guide/Local Maildex, <citation type="IRM">IRM 3.10.72-2</citation>, Correspondex <emphasis>C</emphasis> Letters - Routing Guide, or <citation type="IRM">IRM 3.10.72-3</citation> Computer Paragraph (CP) Notices - Routing Guide.</note></para>
</subsection3>
</subsection2>
<subsection2 id="id337101747"><date>(01-01-2026)</date>
<title>Control of Error Registers</title>
<para>This subsection lists the procedures to maintain control of error registers.<bulletlist>
<li>General control procedures</li>
<li>Daily Error Volume Report, GMF–10–43</li>
<li>Error Register Summary</li>
<li>Associate Error Registers with documents</li>
<li>Control of Loop Registers</li>
<li>Error Pull List, GMF–10–42</li>
<li>Disposition of Completed Registers</li>
</bulletlist></para>
<subsection3 id="id337101686"><date>(01-01-2026)</date>
<title>General Control Procedures</title>
<para>As new data enters the Submission Processing Campus (SPC) computer, the computer performs validity and consistency checks, mathematically verifies taxpayer computations, and codes the data to assure taxpayer notification of errors. <alphalist>
<li>If the data for an input document passes all required checks, it is placed on a tape for transmittal to the Enterprise Computing Center at Martinsburg (ECC-MTB). This is known as <emphasis>good tape</emphasis>.</li>
<li>If the data for an input document does not pass all validity checks, the record is placed in error status.</li>
</alphalist></para>
<para>The error sequence numbers have gaps because the same series of numbers is used for BOB registers. The last number on the right side of the Document ID line is a register counter used to count the number of errors within a batch of work. </para>
<para>The Error Display Run Control Report, GMF–10–40, is generated daily as a computer summary of the error processing for the day. <alphalist>
<li>The information on this report reflects the totals for the Error Register Summary, Pull List, and Daily Error Volume Report.</li>
<li>Three portions of this report are used in preparing Form 6826, Error/Reject Display Request Card.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101687"><date>(01-01-2026)</date>
<title>Daily Error Volume Report, GMF–10–43</title>
<para>The Daily Error Volume Report is a listing of volumes of error records in each program on the error tape. The information is provided by Master File and Error Sequence Number Julian date. This report is used to schedule the workload for Error Resolution and to prepare Error Display Requests.</para>
<para>The last line of the report contains the total volume for all programs within the Master File and Julian date specified.</para>
<para>There is a summary page for each Master File system. The summary page is in the same format as the detail page except that the word <emphasis type="b">SUMMARY</emphasis> replaces the Julian date on the second print line.</para>
<para>Review the Daily Error Volume Report when preparing the daily Error Display Card to be sure the correct error Julian dates are being requested. </para>
<para>If any items are shown with a Program Number of <emphasis type="b">00000</emphasis> determine which programs are not recognized by number and follow the procedures in <citation type="IRM">IRM 3.30.126</citation>, Control Data Analysis, for updating the Program Number Master List.</para>
</subsection3>
<subsection3 id="id337101688"><date>(01-01-2026)</date>
<title>Error Register Summary</title>
<para>The Error Register Summary (GMF–10–42) is produced when the error register is printed. <alphalist>
<li>GMF–10–42 reflects the count of all the error documents printed on the register for that day.</li>
<li>This summary is used by management to maintain a daily count of work in the Error Correction function.</li>
</alphalist></para>
<para>This summary contains totals for each type of error document by Program Number and error status (i.e., Raw, 1st Loop, and Advanced Loops). The listing also provides the total error documents in error status for all program numbers within a Master File. <note notetype="note">This is not a comprehensive total of all records on the error tape. Those figures are available on the Daily Error Volume Report.</note></para>
<para>The count by loops is based strictly on the Julian dates designated by the Error Display Card. The computer does not independently determine how many times a record has appeared on an error register.</para>
<para>Any program shown as Program Number <emphasis type="b">00000</emphasis> with no title has not been recognized by the Program Number Master List. See <citation type="IRM">IRM 3.30.126</citation>, Control Data Analysis, if any programs have not been identified or if changes are needed to identify campus subprograms.</para>
</subsection3>
<subsection3 id="id337101689"><date>(01-01-2026)</date>
<title>Associate Error Registers with Documents</title>
<para>The Error Correction Control function receives the error register from the Computer Operation normally within half a day after receiving the carts of newly transcribed documents.</para>
<para>After verifying with the Error Register Summary, the correct registers have been received, the registers are sorted by batch number for association with the documents.</para>
<para>The control clerk assigns portions of the error register with the related document cart to the various units. Follow local procedures for controlling, routing, and/or sign-out forms prepared by the Error Correction Control function.</para>
</subsection3>
<subsection3 id="id337101690"><date>(01-01-2026)</date>
<title>Control of Loop Registers</title>
<para>Each error register is corrected, transcribed, and re-validated. If the record is still unresolved, a loop error register is printed and worked in the same manner as the original register. <alphalist>
<li>In some cases, the original register has not been corrected or transcribed, and the loop will be identical to the original register.</li>
<li>The raw registers may be retained and compared to the loop to help identify program or transcription problems.</li>
</alphalist></para>
<para>In most campuses, first loop registers are worked directly from the document carts in the same manner as raw.</para>
<para><emphasis>For second loop, all documents must be pulled</emphasis> from the blocks and associated directly with the individual error registers.</para>
<para>Be sure to indicate on the Block Header, Form 1332 or Form 813, that the document is being pulled for error loop.</para>
<para>Be sure that old error records do not remain in the inventory for an extended period. Except for Information Returns Processing (IRP), all errors will be corrected or rejected within three weeks of the Error Sequence Julian date. Carefully monitor the Daily Error Volume Reports (GMF–10–43) to ensure that this procedure is being followed. <note notetype="note">Only transactions in the reject file are available for IDRS research by other functions within IRS.</note></para>
</subsection3>
<subsection3 id="id337101691"><date>(01-01-2026)</date>
<title>Error Pull List, GMF–10–42</title>
<para>The Error Pull List (GMF–10–42) may be requested as an aid to locating source documents for error register items:<alphalist>
<li>The Error Pull List may be printed for raw errors, first loop, second loop, or subsequent loop.</li>
<li>The Error Pull List is always printed in the same sequence as the error registers.</li>
<li>The Error Pull List is recommended for the loop in which the documents will be pulled from the block for association with the individual register. The listing is then used as a check list as the documents are pulled.</li>
</alphalist></para>
<para>The Error Pull List Summary may be used to assist in scheduling the resources needed to pull documents.</para>
</subsection3>
<subsection3 id="id337101692"><date>(01-01-2026)</date>
<title>Disposition of Completed Registers</title>
<para>Corrected error registers are released to the control function as the pages are completed by tax examiners and/or quality review.</para>
<para>The registers are batched and routed to ISRP throughout the workday until the daily cut-off. The last transmittal for the day's registers will be marked <emphasis type="b">final</emphasis>.</para>
<para>Each block of registers must have a correction Alpha Block Control (ABC), and each corrected register requires a serial number. <alphalist>
<li>If the ABC is generated and is to be transcribed, it must be underlined for the first record of the register block.</li>
<li>An ABC sticker must be used if the ABC is not generated or is not to be transcribed. <note notetype="note">The ABC sticker will take priority over the generated ABC. In this case, the generated serial numbers may still be used as long as they are in ascending sequence for the transcription operations. </note></li>
<li>If the Serial Number (SN) is not generated, an SN must be stamped or written above and to the right of the <emphasis type="b">@@</emphasis> signs.</li>
<li>If the SN is generated, but is not to be transcribed, an SN must be stamped (or written) above the generated number. (The generated SN will not be lined through in this case.) <note notetype="note">The stamped or written SN takes priority over the generated SN.</note></li>
<li>If a record on the error register is not to be corrected at all for that day (i.e., no corrections are to be transcribed for that record), the SN must not be stamped or written onto the register for that record. In addition, if a generated SN is present, it must be lined through. The absence of any SN—or the presence of a lined through SN—will indicate to ISRP not to transcribe any correction data for that record.</li>
</alphalist></para>
<para>The error registers are returned to Error Correction after transcription. Verify that no unusual problems have occurred on the next loop; once all issues are resolved, destroy the error register.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101748"><date>(01-01-2026)</date>
<title>Control of Reject Registers</title>
<para>This subsection lists the procedures to maintain control of error registers.<bulletlist>
<li>General reject register control procedures</li>
<li>Reject Sequence Number (RSN)</li>
<li>Reject Inventory List, GMF–11–43</li>
<li>Reject Register Summary, GMF–11–45</li>
<li>Current Reject Listing, GMF–11–46</li>
<li>Receipt of Documents and Registers</li>
<li>Documents Received without a Reject Register</li>
<li>Disposition of Reject Registers (coding and routing)</li>
<li>Reject Correction Verification List, GMF–11–48</li>
<li>Reject Disposition List, GMF–11–47</li>
</bulletlist></para>
<subsection3 id="id337101694"><date>(01-01-2026)</date>
<title>General Reject Register Control Procedures</title>
<para>Associate each reject register with the source document, per local procedures.</para>
</subsection3>
<subsection3 id="id337101695"><date>(01-01-2026)</date>
<title>Reject Sequence Number (RSN)</title>
<para>The Reject Sequence Number (RSN) is used to access each record on the file.</para>
<para>The RSN is 10 digits displayed in the format of <emphasis type="b">X–XXX–XXXXXX</emphasis>. The RSN format is described in the following table: <table frame="all" id="id337100682" orient="port" pgbrk="nobreak" summary="Rejects Sequence Number access" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" rowsep="1"><emphasis type="b">Position</emphasis></entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" rowsep="1"><emphasis type="b">Content Description</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" rowsep="1">1 XXXX</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" rowsep="1"> Year digit</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" rowsep="1"> 2 through 4</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" rowsep="1"> Julian date plus 600</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" rowsep="1"> 5 through 10</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" rowsep="1"> Consecutive serial numbers beginning with 000001 for all new rejects on the file</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
<subsection3 id="id337101696"><date>(01-01-2026)</date>
<title>Reject Inventory List, GMF–11–43</title>
<para>The Reject Inventory List (GMF–11–43) is a listing of all items in the reject inventory as of the date of the listing. </para>
<para>The listing may be produced in <emphasis>any</emphasis> of the following sequences: <bulletlist>
<li>Document Locator Number (DLN)</li>
<li>Reject Sequence Number (RSN)</li>
<li>Taxpayer Identification Number (TIN)</li>
</bulletlist></para>
<para>Produce the inventory list at least once a week as a research tool for items in Rejects. Retain this list for at least one year as outlined in the National Archives and Records Administration (NARA)-approved Document 12990, IRS Records Control Schedules, for record retention, disposition, and destruction guidance.</para>
<para>The Reject Display Card is used to request the inventory list and select the sequence(s) for the printed list.</para>
</subsection3>
<subsection3 id="id337101697"><date>(01-01-2026)</date>
<title>Reject Register Summary, GMF–11–45</title>
<para>The Reject Register Summary lists all programs and categories of reject registers printed for the day.</para>
<para>This summary will be used to ensure that all registers have been received. The summary may be used to assist in work assignment or resource allocation. </para>
</subsection3>
<subsection3 id="id337101698"><date>(01-01-2026)</date>
<title>Current Reject Listing, GMF–11–46</title>
<para>The Current Reject Listing is a daily list of all items added to reject inventory on that date. </para>
<para>Some items may be added and removed from the inventory during the same week and never appear on the Reject Inventory List. These items can only be researched on the Current listing.</para>
<para>The Current Reject Listing may be printed in DLN or RSN sequence, or both. Use the Reject Sort Card to request the sequence.</para>
</subsection3>
<subsection3 id="id337101699"><date>(01-01-2026)</date>
<title>Receipt of Documents and Registers</title>
<para>Upon receipt of the documents and registers, the Reject Control Clerk will compare document and register for correct association. <alphalist>
<li>The tax examiner/clerk will make sure that all documents are received or noted as missing.</li>
</alphalist></para>
<para>Route the work to the applicable functions within the unit. </para>
<para>Some Reject Registers will be received without documents. <alphalist>
<li>Submission Processing Campus deletes have already been pulled by Data Controls in Accounting.</li>
<li>Verify the DLN and alpha with Data Control and code the register with Action Code <emphasis type="b">2–R</emphasis>.</li>
</alphalist></para>
<para>If the document is not on the reject inventory listing, route to a Lead ERS Tax Examiner for research to determine if the transaction has posted to the Master File.</para>
</subsection3>
<subsection3 id="id337101700"><date>(01-01-2026)</date>
<title>Documents Received without a Reject Register</title>
<para>Research using CC SCFTR to determine if the DLN is in Rejects and the date of the register.</para>
<para>Check the reject DLN inventory listing to verify that the document is a reject case.</para>
<para>If items are listed on inventory and the original register cannot be located, use the reject file copy and replace it with a photocopy. If a file copy is not available, reconstruct the register: <alphalist>
<li>Use a photocopy of a reject file copy register with the same format as is applicable to the document.</li>
<li>Line through and rewrite above the RSN the document's corresponding sequence number.</li>
<li>Line through pertinent data on the register, such as the SSN, to ensure that the register will loop. Route the photocopy of the register to ISRP for input. When the reject item appears on the loop, it will have all the data applicable to the document. Associate the loop register with document and work the case as required.</li>
</alphalist></para>
<para>If the document is not on the reject inventory listing, route to your lead TE. The lead will perform research to determine if the transaction has posted to the Master File.</para>
</subsection3>
<subsection3 id="id337101701"><date>(01-01-2026)</date>
<title>Disposition of Reject Registers (Coding and Routing)</title>
<para>Batch the completed reject registers for data transcription as follows: <alphalist>
<li>Separate the documents and route to Files or other holding area as determined by campus management.</li>
<li>Sort the registers into raw and loop, by Master File.</li>
<li>Separate the corrected from the deleted register.</li>
<li>Group into blocks of 100 or fewer registers.</li>
</alphalist></para>
<para>Assign a sequential Serial Number to each register. <alphalist>
<li>Enter the serial number immediately above the Reject Sequence Number. </li>
<li>Number the registers consecutively, beginning with 00.</li>
</alphalist></para>
<para>Enter an alpha sticker on the top-left corner of the first document in each block.</para>
<para>Prepare a transmittal to ISRP according to local procedures.</para>
<para>The registers are returned after transcription and matched against the Reject Correction Verification List. Retain this list as outlined in the National Archives and Records Administration (NARA)-approved Document 12990, IRS Records Control Schedules, for records retention, disposition, and destruction guidance.<alphalist>
<li>Deleted registers are filed and retained for one year.</li>
<li>Corrected raw reject registers are retained for four months.</li>
<li>Corrected loop reject registers may be destroyed.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101702"><date>(01-01-2026)</date>
<title>Reject Correction Verification List, GMF–11–48</title>
<para>The Reject Correction Verification List (GMF–11–48) is printed in correction block and Serial Number sequence for easy association with the reject registers returned from transcription.<alphalist>
<li>This listing contains an entry for each reject correction record which either failed to match to a reject document by RSN or matched to a previously <emphasis>non-corrected</emphasis> reject. Reject loop corrections are not printed on this listing and require no verification because <emphasis>no match</emphasis> would print as a subsequent loop.</li>
<li>This listing matches the order in which the corrected registers were transcribed. </li>
<li>Compare each block of returned registers with the Verification List to ensure that all corrections were transcribed. Corrected items identified as <emphasis>Valid</emphasis> or <emphasis>Invalid</emphasis> require no additional action. If the item is still in the reject inventory, a loop register will be printed.</li>
<li>Deleted items (Code <emphasis type="b">2–D</emphasis> or <emphasis type="b">2–R</emphasis>) must be further checked against the Reject Disposition List. (See <citation type="IRM">IRM 3.12.37.9.9</citation> Reject Disposition List).</li>
</alphalist></para>
<para>Put the following from the block for re-transcription or, if necessary, to be reworked: <alphalist>
<li>Any register with a corrected RSN that was not transcribed.</li>
<li>Any register identified as <emphasis type="b">No Match</emphasis>.</li>
<li>Any register identified as <emphasis type="b">Dup RSN</emphasis>. If the two corrections are input for the same SN, both will come out as <emphasis type="b">Dup RSN</emphasis>, unless one also had an incorrect Format Code.</li>
</alphalist></para>
<para>Check the Summary and reconcile the total count with the number of registers processed.</para>
<para>Retain the Correction Verification List as an index to the corrected registers for at least one year.</para>
<para>Items identified as <emphasis>Invalid</emphasis> will always loop. Some of the reasons for <emphasis>Invalid</emphasis> corrections are as follows: <bulletlist>
<li>Invalid Action Code</li>
<li>Invalid RSN</li>
<li>Invalid Action Code for the section being corrected</li>
<li>Invalid data for the Action Code</li>
<li>Action Code <emphasis type="b">2</emphasis> not followed by a Disposition Code </li>
<li>Action Codes <emphasis type="b">2</emphasis>, <emphasis type="b">7</emphasis>, or <emphasis type="b">9</emphasis> used with other Action Codes</li>
<li>SNs transcribed in the wrong sequence</li>
</bulletlist></para>
</subsection3>
<subsection3 id="id337101703"><date>(01-01-2026)</date>
<title>Reject Disposition List, GMF–11–47</title>
<para>The Reject Disposition List (GMF–11–47) is used to research rejects that have already matched corrections input.</para>
<para>This listing is printed in RSN sequence and includes all corrected rejects for that date, both raw and loop.</para>
<para>Each entry includes a literal indicating the disposition of the document, or in the case of renumbered documents, includes the new DLN. <alphalist>
<li>Good—Valid correction sent the document to good tape.</li>
<li>Loop—The correction was invalid, or a valid correction failed to resolve all reject conditions.</li>
<li>Reinput—Action Code <emphasis type="b">2</emphasis> and Disposition Code <emphasis type="b">R</emphasis>. Check off each reentry document and mark the date as it is released to Accounting.</li>
<li>Re-Reject—Action Code <emphasis type="b">9</emphasis>.</li>
<li>Void—Action Code <emphasis type="b">2</emphasis> and Disposition Code <emphasis type="b">D</emphasis>. These items must be checked against returned reject registers to ensure that the correct code was entered.</li>
</alphalist><note notetype="caution">Retain the Disposition List as a reference for at least one year as outlined in the National Archives and Records Administration (NARA)-approved Document 12990, IRS Records Control Schedules, for records retention, disposition, and destruction guidance so that corrected reject registers can be located.</note></para>
</subsection3>
</subsection2>
<subsection2 id="id337101749"><date>(01-01-2026)</date>
<title>Form 6826, Error/Reject Display Request Card</title>
<para>This subsection lists the procedures for Form 6826, Error/Reject Display Request Card and the IRS Service Central (formerly OS GetServices) Request Fulfillment (RF) Ticket request.</para>
<para>Information in this subsection includes the following: <bulletlist>
<li>Purpose of the Form 6826</li>
<li>IRS Service Central (formerly OS GetServices) Request Fulfillment (RF) Ticket request</li>
<li>Form 6826, Section I - Beginning SC Block Number Card (ABC Card)</li>
<li>Form 6826, Section II—Error Display Card</li>
<li>Form 6826, Section III—Reject Display Card</li>
<li>Form 6826, Section IV—Error Sort Card</li>
<li>Form 6826, Section V—Reject Sort Card</li>
</bulletlist></para>
<subsection3 id="id337101705"><date>(01-01-2026)</date>
<title>Purpose of Form 6826</title>
<para>The error and reject register correction systems provide a great deal of flexibility in deciding what registers and inventory listings will be printed each day, and in what sequence.<alphalist>
<li><emphasis>Form 6826</emphasis> is prepared to select the needed printouts. It is for register processing for all Master Files. Programs that have been converted to ERS cannot be affected by this form. <citation type="Form">Form 6826</citation> is now PDF fillable and is available on the Forms and Pubs website.</li>
<li>The program provides a <emphasis type="q">default value</emphasis> that determines what will be printed when no card is input.</li>
</alphalist></para>
<para>Sections I, II, and IV of Form 6826 are used for error registers. </para>
<para>Sections III and V are for rejects. <alphalist>
<li>The error correction sections are normally prepared in the Error Correction Control Unit and are input to run the GMF-10.</li>
<li>The rejects sections may be prepared by the Control Unit, Rejects Unit Supervisor, or the lead TE and are input to run the GMF-11.</li>
</alphalist></para>
<para>Complete Form 6826 electronically and follow the steps below to input the IRS Service Central (formerly OS GetServices) RF Ticket request.<steplist>
<li>Go to IRS Service Central from the IRS Share Point homepage.</li>
<li>On the main page of IRS Service Central, click on the smart search button and type in <emphasis type="b">Batch Processing/Job Scheduling-Unisys.</emphasis><br/>Select <emphasis type="b">18370-Batch Processing/Job Scheduling-UNISYS.</emphasis></li>
<li>On the next screen, input the below information:<br/><emphasis>Application: GMF SCF Reject Display Error Cards</emphasis><br/><emphasis type="b">Type of Work: Job Run</emphasis><br/><emphasis type="b">Description: GMF SCF Reject Display Error Cards.</emphasis><note notetype="example"><emphasis type="b">GMF SCF Reject Display Error Cards for Ogden SC</emphasis></note></li>
<li>After completing the information in the above fields, click Add to Cart.</li>
<li>The next screen is where you will add your Form 6826 SCRS order card by following the steps below.<br/>Locate the SCRS order card file.<br/>Click on the file and open as this will attach the file to your ticket.<note notetype="caution"><emphasis type="b">Verify Form 6826 is added before moving forward. If the file is not there, go back and add the file.</emphasis></note></li>
<li>Once you have added Form 6826, click the save button and then Checkout.</li>
<li>On the next screen, click the clock/calendar button and select today’s date for the order.</li>
<li>In the Purpose box add the following text, <emphasis type="b">please follow the attached file for the SCRS order card for (enter your site).</emphasis></li>
</steplist></para>
<subsection4 id="id337101706"><date>(01-01-2026)</date>
<title>Form 6826, Section I-Beginning SC Block Number Card</title>
<para>Section 1 will be prepared whenever the Correction ABC and SN are preprinted on the error registers.</para>
<para>Examine the Informational Run Control Data for the Beginning ABC on the Error Display Run Control Report (GMF–10–40) of the previous day.</para>
<para>Enter the <emphasis type="b">Beginning ABC to be Input Next Day</emphasis> in Section I of Form 6826.</para>
</subsection4>
<subsection4 id="id337101707"><date>(01-01-2026)</date>
<title>Form 6826, Section II—Error Display Card</title>
<para>Section II, Error Display Card, is used to request the printing of raw and loop error records from the error tape and must be input daily. </para>
<para> Use the following chart to determine when the documents will appear on the register:<table frame="all" id="id337100690" orient="port" pgbrk="nobreak" summary="Error display card IMF BMFIRP" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If an Error Display Card is not input on a particular day</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis><br/></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> For IMF and BMF</entry>
<entry morerows="0" nameend="col2" namest="col2">Only the raw error documents will print on the error register.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> For IRP</entry>
<entry morerows="0" nameend="col2" namest="col2">Nothing will appear on the error register.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Each horizontal line on the Error Display Card represents a computer line. A separate line must be completed for each Master File. A separate line must also be completed if only certain programs within a Master File are being requested.</para>
<para>Circle the appropriate Master File Identification Code number on the Error Display Card as follows: <bulletlist>
<li><emphasis type="b">1</emphasis> for IMF</li>
<li><emphasis type="b">2</emphasis> for BMF</li>
<li><emphasis type="b">5</emphasis> for IRP</li>
</bulletlist></para>
<para>Use the Program Number field to select specific programs within a Master File to be printed on the error register. Enter the complete Program Number or enter any lead numeric followed by Xs. The program numbers may be entered as follows: <alphalist>
<li>Leave blank or enter <emphasis type="q">XXXXX</emphasis>—All programs within a Master File will print on the error register.</li>
<li><emphasis type="b">NXXXX</emphasis>—All programs with the same first digit will print (e.g., 4XXXX).</li>
<li><emphasis type="b">NNXXX</emphasis>—All programs with the same first two digits will print (e.g., 44XXX).</li>
<li><emphasis type="b">NNNXX</emphasis>—All programs with the same first three digits will print (e.g., 444XX).</li>
<li><emphasis type="b">NNNNX</emphasis>—All programs with the same first four digits will print (e.g., 4444X).</li>
<li><emphasis type="b">NNNNN</emphasis>—Only one program will print (e.g., 44700). </li>
</alphalist></para>
<para>Use the Raw field to select the raw error records to be printed on the error register. This field contains four positions as year digit and Julian date (YDDD). <note notetype="caution">If loop registers are requested, and a card is not input to request the raw register, only the loop register will print.</note><alphalist>
<li>If error records for one Error Sequence Number Julian date is requested, enter as YDDD in the <emphasis type="b">From</emphasis> column and leave the <emphasis type="b">To</emphasis> column blank.</li>
<li>If error documents from two or more Julian dates are requested, enter as <emphasis type="b">YDDDYDDD</emphasis>. All error records which have Error SN Julian dates greater than or equal to the first YDDD and less than or equal to the second YDDD will be selected for printing as raw errors.</li>
<li>Check the Daily Error Volume Report (GMF–10–43) to determine which Julian dates are on the error file.</li>
</alphalist></para>
<para>Loops, First through Fifth—The same criteria for raw errors applies to loop errors.</para>
<para>Subsequent Loop (YDDD Only)—All error records that have Error Sequence Number Julian dates less than or equal to the YDDD entered will print as <emphasis type="b">sixth loop or over</emphasis> errors.</para>
<para>Be sure that all records with old Julian dates are printed on the error register. </para>
<para>Valid Error Display Cards will appear on the listing with nothing printed in the last column of the report. The last column of the report does not have a printed title.</para>
<para>Invalid Error Display Cards will appear on the listing with <emphasis type="b">INVALID</emphasis> printed in the last column. The Error Display Cards are invalid if any of the following conditions are present:<alphalist>
<li>The Master File Identification (ID) Code is other than 1, 2, 3, 4, or 5. If the Master File ID code is invalid, the card will print on the listing for IMF.</li>
<li>The program number entered is not in a valid format.</li>
<li>A Julian date is entered for the <emphasis type="b">TO</emphasis> column and the <emphasis type="b">FROM</emphasis> column is blank.</li>
<li>The Julian date is not numeric.</li>
<li>The day portion of the Julian date is not 001-366.<note>The items listed as <emphasis type="b">invalid</emphasis> will not print on the error register.</note></li>
</alphalist></para>
<para>Prepare the Reject Display Card as follows: <alphalist>
<li>Circle the <emphasis type="b">RD</emphasis> for each Reject Display card being prepared.</li>
<li>Circle the appropriate Master File. A separate card must be prepared for each SCRS file. (<emphasis type="b">1</emphasis> = IMF, and <emphasis type="b">5</emphasis> = IRP)</li>
<li>Enter the program number only if the request applies only to a particular program or group of programs. For a group of programs, enter two succeeding X fillers. An additional request with the program number blank may be used to request all remaining items on a Master File.</li>
<li>Circle the <emphasis type="b">1</emphasis> for <emphasis type="b">Print Raw Rejects.</emphasis> If the card is prepared, this position must be circled for each Master File, or the raw rejects will not print.</li>
<li>Circle <emphasis type="b">1</emphasis> for <emphasis type="b">Print Loop</emphasis> if the loop will be printed on this day. To avoid duplicate registers, the loop is normally not requested until all of the previous loop has been input for the designated file.</li>
<li>Circle <emphasis type="b">1</emphasis> for <emphasis type="b">Reprint Raw Rejects</emphasis> if registers have been printed incorrectly and must be reprinted. <note notetype="reminder">This must be done at End of Year processing.</note></li>
<li>If the Reject Inventory List will be printed on this day, circle a number for <emphasis type="b">Reject Inventory List</emphasis>. The available sorts for the inventory list are shown in the lower-right corner of the Form 6826. Be sure to circle only one number. For instance, if the list will be printed in both DLN and RSN order, circle 3, not 1 and 2.</li>
<li>To print the Age List circle one number for <emphasis type="b">Age List</emphasis> using the same code shown on the form.</li>
</alphalist></para>
</subsection4>
<subsection4 id="id337101708"><date>(01-01-2026)</date>
<title>Form 6826, Section III—Reject Display Card</title>
<para>Input Section III, Reject Display Card, whenever a Reject Inventory or Age List is required or whenever reject loop registers will be printed. <alphalist>
<li>If no card is input, only the raw rejects will be printed.</li>
<li>If Inventory and Age Lists and loop registers are always printed on the same day of the week, the same card may be used by the Computer Operation. </li>
</alphalist></para>
<para>Prepare the Reject Display Card as follows: <alphalist>
<li>Circle the <emphasis type="b">RD</emphasis> for each Reject Display card being prepared.</li>
<li>Circle the appropriate Master File. A separate card must be prepared for each SCRS file. (<emphasis type="b">1</emphasis> = IMF, and <emphasis type="b">5</emphasis> = IRP)</li>
<li>Enter the program number only if the request applies only to a particular program or group of programs. For a group of programs, enter two succeeding X fillers. An additional request with the program number blank may be used to request all remaining items on a Master File.</li>
<li>Circle the <emphasis type="b">1</emphasis> for <emphasis type="b">Print Raw Rejects.</emphasis> If the card is prepared, this position must be circled for each Master File, or the raw rejects will not print.</li>
<li>Circle <emphasis type="b">1</emphasis> for <emphasis type="b">Print Loop</emphasis> if the loop will be printed on this day. To avoid duplicate registers, the loop is normally not requested until all of the previous loop has been input for the designated file.</li>
<li>Circle <emphasis type="b">1</emphasis> for <emphasis type="b">Reprint Raw Rejects</emphasis> if registers have been printed incorrectly and must be reprinted. <note notetype="reminder">This must be done at End of Year processing.</note></li>
<li>If the Reject Inventory List will be printed on this day, circle a number for <emphasis type="b">Reject Inventory List</emphasis>. The available sorts for the inventory list are shown in the lower-right corner of the Form 6826. Be sure to circle only one number. For instance, if the list will be printed in both DLN and RSN order, circle 3, not 1 and 2.</li>
<li>To print the Age List circle one number for <emphasis type="b">Age List</emphasis> using the same code shown on the form.</li>
</alphalist></para>
<para>Generally, the sort requests will not change from day to day. If a request is not input, the computer will default to the last request made. </para>
<para>Each horizontal line on the Error Sort Card represents a computer line. A separate line must be prepared for each Master File. Circle the appropriate Master File Code as follows:<bulletlist>
<li><emphasis type="b">1</emphasis>=IMF</li>
<li><emphasis type="b">2</emphasis>=BMF</li>
<li><emphasis type="b">5</emphasis>=IRP</li>
</bulletlist></para>
<para>The Print Sequence field determines whether the error records are printed in transcribed batch sequence or in DLN sequence. Circle the appropriate number on the card for Raw, First, Second and Subsequent Loops. A code must be circled for all four items. <alphalist>
<li>Code 1—Transcribed Document Locator Sequence. The error registers are printed in the following order: Error Sequence Julian date, Program Number, Batch Number, SC Block Control Number and DLN Serial Number. Use this code for raw and loop errors.</li>
<li>Code 2—Files DLN Sequence Within Loop. The error register will be printed in Files DLN order within each Error Sequence Julian date within each loop. Use this code for raw and loop registers.</li>
<li>Code 3—Files–DLN Sequence Without Regard for Loop. The Loop error registers will be printed in Files DLN order.</li>
</alphalist></para>
<para>Circle <emphasis type="b">1</emphasis> for each register to print an Error Pull List. <note>If the Error Pull List won’t be printed, do not circle a number.</note></para>
<para>Correction ABC/SN—This field determines whether the computer will generate correction record alpha block control numbers and correction record serial numbers for raw and first loop records. Circle the appropriate number. Leave blank if the numbering is not to be computer generated. <alphalist>
<li>Code 1—Raw errors only.</li>
<li>Code 2—Raw and first loop errors.</li>
<li>Code 3—Raw and all loops. Until the form is revised to show this option, enter the numeric <emphasis type="b">3</emphasis> on Form 6826.</li>
</alphalist></para>
<para>If the Correction ABC/SN has been computer generated, a computer card must be prepared daily to assign the beginning ABC. <bulletlist>
<li>If a Beginning SC Block Number Card is not input to update the generated ABC, the computer will default to <emphasis type="b">/22</emphasis>.</li>
<li> It is recommended that a Beginning SC Block Number Card be input so that the ABCs will not be duplicated from day to day.</li>
<li>The Beginning SC Block Number is listed on page 3 of the Error Display Run Control Report.</li>
</bulletlist></para>
</subsection4>
<subsection4 id="id337101709"><date>(01-01-2026)</date>
<title>Form 6826, Section IV—Error Sort Card</title>
<para>Use Section IV, Error Sort Card to request changes to the following conditions: <alphalist>
<li>The order the error records will print.</li>
<li>The Error Pull List-whether to print or not.</li>
<li>The computer generation of the Alpha Block Control Number and correction record Serial Numbers (ABC/SN) to generate or not.</li>
</alphalist></para>
<para>Generally, the sort requests will not change from day to day. If a request is not input, the computer will default to the last request made. </para>
<para>Each horizontal line on the Error Sort Card represents a computer line. A separate line must be prepared for each Master File. Circle the appropriate Master File Code as follows:<bulletlist>
<li><emphasis type="b">1</emphasis>=IMF</li>
<li><emphasis type="b">2</emphasis>=BMF</li>
<li><emphasis type="b">5</emphasis>=IRP</li>
</bulletlist></para>
<para>The Print Sequence field determines whether the error records are printed in transcribed batch sequence or in DLN sequence. Circle the appropriate number on the card for Raw, First, Second and Subsequent Loops. A code must be circled for all four items. <alphalist>
<li>Code 1—Transcribed Document Locator Sequence. The error registers are printed in the following order: Error Sequence Julian date, Program Number, Batch Number, SC Block Control Number and DLN Serial Number. Use this code for raw and loop errors.</li>
<li>Code 2—Files DLN Sequence Within Loop. The error register will be printed in Files DLN order within each Error Sequence Julian date within each loop. Use this code for raw and loop registers.</li>
<li>Code 3—Files–DLN Sequence Without Regard for Loop. The Loop error registers will be printed in Files DLN order.</li>
</alphalist></para>
<para>Circle <emphasis type="b">1</emphasis> for each register to print an Error Pull List. <note>If the Error Pull List won’t be printed, do not circle a number.</note></para>
<para>Correction ABC/SN—This field determines whether the computer will generate correction record alpha block control numbers and correction record serial numbers for raw and first loop records. Circle the appropriate number. Leave blank if the numbering is not to be computer generated. <alphalist>
<li>Code 1—Raw errors only.</li>
<li>Code 2—Raw and first loop errors.</li>
<li>Code 3—Raw and all loops. Until the form is revised to show this option, enter the numeric <emphasis type="b">3</emphasis> on Form 6826.</li>
</alphalist></para>
<para>If the Correction ABC/SN has been computer generated, a computer card must be prepared daily to assign the beginning ABC. <bulletlist>
<li>If a Beginning SC Block Number Card is not input to update the generated ABC, the computer will default to <emphasis type="b">/22</emphasis>.</li>
<li> It is recommended that a Beginning SC Block Number Card be input so that the ABCs will not be duplicated from day to day.</li>
<li>The Beginning SC Block Number is listed on page 3 of the Error Display Run Control Report.</li>
</bulletlist></para>
</subsection4>
<subsection4 id="id337101710"><date>(01-01-2026)</date>
<title>Error Display Run Control Report</title>
<para>Error Sort Cards are validated and printed on the Error Display Run Control Report.</para>
<para>The Error Sort Requests show the Old Error Sort Parameters, the Error Sort Requests Input, and the New Error Sort Parameters.</para>
<para>Valid Error Sort Requests Input will appear on the listing with nothing printed in the last column of the report.</para>
<para>Error Sort Requests will appear on the listing with <emphasis type="b">DUPLICATE</emphasis> printed in the last column. If the request is valid, but there already is a valid Error Sort Request, the first valid request input is used to determine the print sequence.</para>
<para>Error Sort Requests will appear on the listing with <emphasis type="b">INVALID</emphasis> printed in the last column if <emphasis type="b">any</emphasis> of the following conditions exist: <bulletlist>
<li>The Master File Code is other than a 1, 2, or 5</li>
<li>If the Master File Code is entered as an invalid character</li>
<li>If any invalid characters are entered</li>
</bulletlist></para>
<para>Error Sort Requests will also appear on the listing with <emphasis type="b">INVALID</emphasis> printed in the last column if any of the following combinations are entered: <alphalist>
<li>Print Sequence Key for First Loop is 3 and for Second and/or Advance Loops is 1 or 2.</li>
<li>Print Sequence Key for Second Loop is 3 and for Advanced Loops is 1 or 2.</li>
<li>Print Sequence Key for First Loop is 3 and the Correction ABC/SN code is 2.</li>
</alphalist></para>
<para>If a valid Error Sort Request was input, the New Error Sort Parameters will be identical to the valid Error Sort Request. Otherwise, the New Error Sort Parameters will be equal to the old Error Sort Parameters.</para>
</subsection4>
<subsection4 id="id337101711"><date>(01-01-2026)</date>
<title>Form 6826, Section V—Reject Sort Card</title>
<para>Section V, Reject Sort Card, is prepared only if the Rejects Unit wishes to change the way that registers are sorted or the way the Current Reject Listing or Pull List is printed.</para>
<para>Prepare Section V, Form 6826, to establish a standard print format for the reject register, Current Reject Listing, and Pull List. Once the desired sort is determined, the same card will be used each day by the Computer Operation. No new card is needed unless the Rejects function changes procedures. </para>
</subsection4>
<subsection4 id="id337101712"><date>(01-01-2026)</date>
<title>Preparing the Reject Sort Card</title>
<para>Circle <emphasis type="b">RS</emphasis> for each Reject Sort card being prepared. </para>
<para>Circle the desired Master File. A separate line must be used for each file.</para>
<para>Circle the sort option desired for the reject register. <alphalist>
<li>Circle <emphasis type="b">1</emphasis> to sort the register in Files DLN sequence. </li>
<li>Circle <emphasis type="b">2</emphasis> to sort first by the source of the reject. That is, all Rejects coming from errors, BOBS, raw data, or Unpostables will be printed separately. The sort within each source is by DLN for errors, BOBS, and Unpostables and by transcribed document sequence for raw data.</li>
</alphalist></para>
<para>Circle the sort desired for the Current Reject Listing. Circle <emphasis type="b">3</emphasis> if the list will be printed in both DLN and RSN sequence. </para>
<para>Indicate the desired loop print sequence. <alphalist>
<li>Circle <emphasis type="b">1</emphasis> if the loop will be printed in strict DLN sequence, without regard to loop.</li>
<li>Circle <emphasis type="b">2</emphasis> if each loop will be printed separately. </li>
<li>Circle <emphasis type="b">3</emphasis> if only the first loop will be printed separately, with all other loops combined.</li>
</alphalist></para>
<para>If one or more Reject Pull Lists is used, indicate the requested lists. If a pull list is used for all reject registers, circle the <emphasis type="b">1</emphasis> for <emphasis type="b">Raw</emphasis>, <emphasis type="b">First Loop</emphasis>, and <emphasis type="b">Other Loop</emphasis>.</para>
</subsection4>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337100068"><date>(01-01-2026)</date>
<title>Error Register Format</title>
<para>This subsection lists the procedures for the Error Register.<bulletlist>
<li>General Error Register information</li>
<li>Error Register title line</li>
<li>Error Register document sections</li>
<li>Reject Register</li>
<li>Reject Register title line</li>
<li>Reject Register Identification line</li>
<li>Types of errors</li>
<li>Error/Reject Action Codes</li>
</bulletlist></para>
<subsection2 id="id337100069"><date>(06-25-2021)</date>
<title>General Error Register Information</title>
<para>The Error Registers are listings of document records that failed the validity, consistency, or math verification tests of the service center (SC) computer.</para>
<para>The Error Register is printed in the order requested by each campus on the Error Sort Card from Form 6826. The registers may be sorted in any of five sequences. (See <citation type="IRM">IRM 3.12.37.10.5</citation> for additional information)</para>
<para>Each processing campus will select the sequence best suited for its operations. The sort sequence is not required to be the same for every Master File.</para>
<subsection3 id="id337101750"><date>(01-01-2026)</date>
<title>Error Register Title Line</title>
<para>The Error Register Title Line identifies the Run Number and Master File, type of record, type of register, and source of the error register, program, form number, Format Code, date, and page number. It will appear as the first printed line at the top of each page. </para>
<para>The Generalized Mainline Framework (GMF) processes all Master Files on one file, but the error registers will be printed separately for each Master File (see the list as follows). <bulletlist>
<li>IMF—Individual Master File</li>
<li>BMF—Business Master File</li>
<li>IRP—Information Returns Program</li>
<li>EPMF—Employee Plans Master File</li>
</bulletlist></para>
<para>The title line designates that the register is raw or loop.</para>
<para>For loop registers, the correction loop counter specifies which loop may be contained on the page. If loop errors have been sorted separately, this field will be a one-digit number (e.g., <emphasis type="b">1</emphasis>, <emphasis type="b">2</emphasis>, etc.). This field will be the range of loop registers printed (e.g., <emphasis type="b">1–6</emphasis>, <emphasis type="b">2–6</emphasis>, or <emphasis type="b">3–6</emphasis>) if some or all loop errors have been sorted separately. </para>
</subsection3>
<subsection3 id="id337101751"><date>(01-01-2026)</date>
<title>Error Register Identification (ID) Line</title>
<para>The <emphasis type="b">Error Register ID Line</emphasis> will identify each document on the error register and, sometimes, why the document is on the error register.</para>
<para>The <emphasis type="b">Error Register ID Line</emphasis> is always the first printed line for each document on the error register. If an error document is too long to fit on one page, the ID line for this split record is repeated on the next register page.</para>
<para>The <emphasis type="b">Correction ABC and SN</emphasis> are present when requested on the Error Sort Card. <alphalist>
<li>See <citation type="IRM">IRM 3.12.37.8.7 </citation>for procedures for assignment of the ABC/SN.</li>
<li>When the generated ABC/SN is not selected, each error record is preceded by <emphasis type="b">@@</emphasis>.</li>
</alphalist></para>
<para>The <emphasis type="b">Error Sequence Number (ESN)</emphasis> is assigned to each raw input document that is determined to be in error. <alphalist>
<li>This number remains the ESN of the error document until the record is corrected or rejected from the Error File Tape.</li>
<li>The ESNs will not be in sequence on the error registers. ESNs are assigned to all Error and BOB Records as they are entered on the files, whereas Error Records are sorted in various sequences prior to being printed on the Error Register.</li>
<li>The first four positions of the ESN are the year digit and Julian date. </li>
</alphalist></para>
<para>The <emphasis type="b">Service Center Block Control Number</emphasis> is a three-digit alpha-numeric assigned to a block of documents and input by ISRP for control purposes. It is used to associate error registers with blocks or documents. </para>
<para>The <emphasis type="b">Batch Number</emphasis> is a four-digit number assigned to a group of blocks which have been associated for document control purposes, and which have identical program code, tax class, document code, and other specific record criteria.</para>
<para>The <emphasis type="b">Document Locator Number (DLN)</emphasis> is a unique 14-digit number assigned to each document within a block.</para>
<para>The <emphasis type="b">Block Header MFT</emphasis> is a code which is used to further identify the types of documents in a block. The MFT is a two-position numeric code.</para>
<para>The <emphasis type="b">Invalid Correction Error Reason Code</emphasis> is a code indicating that the last error register correction attempt was invalid. This invalid correction attempt will be identified by Error Reason Code AA for all Master Files. See <seealso idref="id337101727">IRM 3.12.37.7.4.8</seealso> for a list of the various invalid correction attempt conditions. This field will be blank if an invalid condition is not identified.</para>
<para>The <emphasis type="b">Correction Loop Counter</emphasis> is a two-digit numeric field that provides the number of times a particular record has appeared on a Loop register.</para>
<para>The <emphasis type="b">Correction Match Counter</emphasis> is a two-digit numeric field that provides the number of times that a document on the error register has had a correction matched to it. This number reflects the number of correction attempts.</para>
<para>The <emphasis type="b">Last Action Code Used</emphasis> is a code identifying the correction action code applied to an error document to resolve an error condition. When more than one action code is present in the matching correction record, the first action code in the correction record is considered to be the last action code used.</para>
<para>The <emphasis type="b">Error Register Consecutive Counter</emphasis> is an ascending and consecutive count of error records as they appear on the error register. The counter is reset to 00001 with each change of Master File and each change of raw to loop register. This counter will be used to determine the number of registers in a block of work.</para>
</subsection3>
<subsection3 id="id337101752"><date>(01-01-2026)</date>
<title>Error Register Document Sections</title>
<para>Each error register document record contains one or more sections of data. <alphalist>
<li>The section number is displayed to the left of the first line of each section.</li>
<li>The first section number for each document is 01. Other sections may follow, always in ascending order but not necessarily consecutively.</li>
</alphalist></para>
<para>The fields of each section begin on the same line as the Section Number. Each field is identified on the Error Register by an Alpha Field Designation printed before the field. The sign of the field is also printed on the Error Register for variable length input fields. When required, the sign of a field is printed after the field. <alphalist>
<li>If the field in error, is one normally designated by an asterisk, the asterisk is printed in the first space immediately to the left of the field designator. </li>
<li>The fields of a section must always be in the same sequence and must be corrected in that sequence. For correction purposes, each field is referred to by its Alpha Field Designation. The first field of each section is designated as the <emphasis type="b">A</emphasis> field and letters are assigned in alphabetic sequence for the rest of the fields in the section. Corrections must be transcribed in alphabetical order.</li>
</alphalist></para>
</subsection3>
</subsection2>
<subsection2 id="id337101753"><date>(01-01-2026)</date>
<title>Reject Register</title>
<para>The Reject Register will remain in the Rejects Unit until the register is coded for transcription.</para>
<para>All reject <emphasis type="b">register corrections</emphasis> will be made with a <emphasis type="b">colored pen/pencil</emphasis> or in accordance with campus procedures. </para>
<subsection3 id="id337101717"><date>(01-01-2026)</date>
<title>Reject Register Title Line</title>
<para>The first line of the reject register is the title line.</para>
<para>Each register contains a literal in the title line which identifies the register as <emphasis type="b">raw</emphasis>, <emphasis type="b">loop</emphasis>, <emphasis type="b">re-reject</emphasis>, or <emphasis type="b"><emphasis type="b">special</emphasis></emphasis>.</para>
<para>The Entry Source Code is located on the title line. It identifies the last status of the document before it was rejected. The Entry Source Codes, and the meaning of each, are in the following list: <alphalist>
<li>D-Raw Input—If the last function handling the document was ISRP. </li>
<li>B - Corrected BOB — After ISRP, the block of document was worked by the BOB Resolution function.</li>
<li>U- Unpostables — The document was nullified to Rejects by Unpostables. The <emphasis type="b">U</emphasis> will be followed by the Unpostable Code.</li>
<li>E– Error—The error register was <emphasis type="b">3</emphasis> coded by Error Correction.</li>
</alphalist></para>
<para>The program number is printed to left of the name of the program on the title line.</para>
</subsection3>
<subsection3 id="id337101718"><date>(01-01-2026)</date>
<title>Reject Register Identification Line</title>
<para>The second line is the document ID line.</para>
<para>The batch number is printed between the ABC and DLN.</para>
<para>The correction loop and correction match counter identifies the number of times a register has printed and the number of times a correction record has attempted to post to good tape. The loop counter and match counter are reset for re-rejects.</para>
<para>The last number on the right is the last action code used.</para>
<para>Each Reject is matched with its corresponding document. Make sure the DLNs and TINs on the register and document match.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100074"><date>(01-01-2023)</date>
<title>Types of Errors</title>
<para><emphasis>Every record that appears on an Error Register has failed a specific validity, consistency, or math error check.</emphasis> When processing GMF Error Registers or Reject Registers refer to <citation type="IRM">IRM 3.12.21</citation>.</para>
<para>Every error must be corrected with an Action Code. </para>
<para>An unpostable will create a <emphasis type="b">U</emphasis> and the Unpostable Code (e.g., <emphasis type="b">U168</emphasis>) and is printed in the top middle of the register.</para>
<subsection3 id="id337100079"><date>(01-01-2023)</date>
<title>Terminus Errors</title>
<para>A <emphasis type="b">Terminus Error</emphasis> is indicated by two asterisks (**) printed to the left of the Section Number. This indicates that there is a non-numeric character in a numeric field or that the format of the section is incorrect. <alphalist>
<li>In case of a Terminus error, check that all necessary fields and sections are present. If they are not present, enter the missing section with Action Code <emphasis type="b">5</emphasis> and the fields with Action Code <emphasis type="b">6</emphasis>.</li>
<li>If the data is correct, it will be necessary to reenter a field using Action Code <emphasis type="b">6</emphasis> to send the record to good tape.</li>
</alphalist>	</para>
</subsection3>
<subsection3 id="id337100082"><date>(01-01-2023)</date>
<title>Validity Errors</title>
<para>Validity errors are identified either because a field, which must have data, is blank, or because the computer identified invalid characters within that field. Fields are validity checked to ensure data before transmittal to the master file. Each field that is found invalid is identified on the register with an asterisk (*) before the alpha-field designator.</para>
<para>Correct as follows:<alphalist>
<li>Compare the data on the register with the document.</li>
<li>If the information on the register matches what is on the document, use CC TXMODA and compare all Dates, Transaction Codes, and money amounts match what is on the document. Make any corrections needed to Dates and/or Transaction Codes. </li>
<li>Money amounts cannot be changed as it will throw the register off-balance and create a math error.</li>
<li>If the information in CC TXMODA matches the information on the document and register, reach out to the originator of the document for guidance.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337100084"><date>(01-01-2023)</date>
<title>Math Errors</title>
<para><emphasis>Math Errors</emphasis> result when the computer computation differs from the transcribed amount.</para>
<para>The Error indicator is the computer computation amount printed on the Error Register under the transcribed amount. </para>
<para>Correct as follows:<alphalist>
<li>Check for transcription errors. </li>
<li>Compare the data on the register with the document.</li>
<li>If the information on the register matches what is on the document, use CC TXMODA and compare all Dates, Transaction Codes, and money amounts match with what is on the document. Make any corrections needed to Dates and/or Transaction Codes.</li>
<li>If the information in CC TXMODA matches the information on the document and register, reach out to the originator of the document for guidance.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337100086"><date>(01-01-2020)</date>
<title>Missing Section Errors</title>
<para><emphasis>Missing Section</emphasis> errors will be indicated by a single asterisk (*) to the left of the section number. This indicates a missing required section. Use Action Code <emphasis type="b">6</emphasis> to enter the missing data.</para>
</subsection3>
<subsection3 id="id337100087"><date>(01-01-2023)</date>
<title>Extraneous Section Errors</title>
<para><emphasis>Extraneous Section</emphasis> errors are indicated by a pound sign (#) to the left of the Section Number. This indicates an invalid section. Use Action Code <emphasis type="b">4</emphasis> to delete an unnecessary section. </para>
</subsection3>
</subsection2>
<subsection2 id="id337101754"><date>(01-01-2026)</date>
<title>Error/Reject Register Action Codes</title>
<para>This subsection of the manual provides information on Error/Reject Register Action Codes.</para>
<para>Information in this subsection includes the following: <bulletlist>
<li>Action Codes <emphasis type="b">2</emphasis> through <emphasis type="b">7</emphasis> and <emphasis type="b">9</emphasis></li>
<li>Invalid correction attempts</li>
</bulletlist></para>
<subsection3 id="id337101720"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">2</emphasis></title>
<para><emphasis type="b">Action Code <emphasis>2</emphasis> is used to delete or re-enter records on Service Center Control File (SCCF).</emphasis></para>
<para>Action Code <emphasis type="b">2</emphasis> is entered to the left of Section 01 and must be accompanied by a Reject Disposition Code. The valid Reject Disposition Codes are as follows: <bulletlist>
<li><emphasis type="b">2–D—</emphasis> delete the document from the Reject inventory</li>
<note notetype="caution">Do not use 2-D to void a register that contains a transfer-in amount in paragraph I.</note>
<li><emphasis type="b">2–R—</emphasis> reenter the document with the current DLN</li>
</bulletlist></para>
<para>Be sure to maintain an audit trail of deleted documents. Notate on the register the reason for Action Code <emphasis type="b">2</emphasis>.</para>
<para>Action Code <emphasis type="b">2</emphasis> is valid for IRP and Reject Register only.</para>
<para><emphasis type="b">When Action Code <emphasis>2</emphasis> is used, no other Action Code is valid.</emphasis></para>
</subsection3>
<subsection3 id="id337101721"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">3</emphasis></title>
<para><emphasis type="b">Enter Action Code <emphasis>3</emphasis> to the left of Section 01 for any record that is unprocessable.</emphasis></para>
<para>Some of the reasons for using Action Code <emphasis type="b">3</emphasis> are: <alphalist>
<li>A document with illegible or missing necessary data, that requires additional research.</li>
<li>A document that was numbered with the wrong document code.</li>
<li>A document that has data incorrectly transcribed in a field that cannot be changed by an Error Register Correction.</li>
<li>The ERS register is on loop 5 and must be moved to Rejects inventory for correction.</li>
</alphalist></para>
<para>Action Code <emphasis type="b">3</emphasis> is valid for Error Registers only. <note notetype="exception">IRP</note></para>
<para><emphasis type="b">When Action Code <emphasis>3</emphasis> is used, no other Action Code is valid.</emphasis></para>
</subsection3>
<subsection3 id="id337101722"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">4</emphasis></title>
<para><emphasis type="b">Action Code <emphasis>4</emphasis> is used to delete a section from a register.</emphasis></para>
<para>This code is valid for any section that is considered optional by the return program. Section 01 can never be deleted.</para>
<para>This code will not be used to delete a section identified as <emphasis type="b">missing</emphasis> (a single asterisk in front of the section number). A missing section will be dropped automatically if no data is entered in it. </para>
</subsection3>
<subsection3 id="id337101723"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">5</emphasis></title>
<para><emphasis type="b">Action Code <emphasis>5</emphasis> is used to add a section to a record on the register.</emphasis></para>
<para>Action Code <emphasis type="b">5</emphasis> is followed by the number of the section being added, the alpha field designator(s), and the data for the section being added. </para>
<para>This code is invalid for a section already on the register or a section that is not valid for the type of document being processed.</para>
<para>When adding sections, be sure that all corrections are entered in the proper sequence. <alphalist>
<li>If the document also requires Action Code <emphasis type="b">6</emphasis> corrections, sections must be added in the proper sequence with respect to other corrected sections.</li>
<li>If the document requires no other corrections, sections may be added at any place on the record, provided that each new section is in the proper sequence. </li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101724"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">6</emphasis></title>
<para><emphasis type="b">Action Code <emphasis>6</emphasis> is used to change a field or fields of a section within the Error Record.</emphasis><alphalist>
<li>The computer identifies each field of a section with an Alpha Field Designation and prints the Alpha Field Designation before the field on the Error Register. </li>
<li>To correct a field, the incorrect field data must be lined out and the correct data entered above. Any number of fields may be changed during one correction cycle.</li>
<li>Enter Action Code <emphasis type="b">6</emphasis> immediately to the left of the Section Number for the section being changed. </li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101725"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">7</emphasis></title>
<para><emphasis type="b">Action Code <emphasis>7</emphasis> is used to indicate that the data on the error register is correct and that no action is necessary. </emphasis></para>
<para>Use Action Code <emphasis type="b">7</emphasis> to clear an error record that is on the register for a one time only validity condition. <note notetype="note"><emphasis type="b">Action Code <emphasis>7</emphasis> must not be used unless all other information on the register is correct.</emphasis></note></para>
<para>Action Code <emphasis type="b">7</emphasis> will not clear a math error condition. </para>
<para><emphasis type="b">When Action Code <emphasis>7</emphasis> is used, no other Action Code is valid.</emphasis>	</para>
</subsection3>
<subsection3 id="id337101726"><date>(01-01-2026)</date>
<title>Action Code <emphasis type="b">9</emphasis></title>
<para><emphasis type="b">Use Action Code <emphasis>9</emphasis> to re-reject a loop register for correspondence or other suspense action.</emphasis></para>
<para>This code is used to prevent a reject loop record from reprinting each time the loop is run, if the record is not ready for correction.</para>
<para>Action Code <emphasis type="b">9</emphasis> is to be used for reject loop only. Do not use for raw rejects or error registers.</para>
<para><emphasis type="b">When Action Code <emphasis>9</emphasis> is used, no other Action Code is valid.</emphasis></para>
</subsection3>
<subsection3 id="id337101727"><date>(01-01-2026)</date>
<title>Invalid Correction Attempts</title>
<para>Each correction attempt is subject to tests which ensure proper correction. <alphalist>
<li>If a correction attempt fails, the record will reappear on the Error Register with Error Reason Code <emphasis type="b">AA</emphasis>.</li>
<li>When Error Reason Code <emphasis type="b">AA</emphasis> is present, correct the error register as if no other correction attempt has been made.</li>
</alphalist></para>
<para>For a given record, any correction that precedes the invalid correction attempt will print out as a corrected field. <alphalist>
<li>Any other corrections made after an invalid correction will not print out, an Error Reason Code <emphasis type="b">AA</emphasis> will be present. <note notetype="example"> Fields A, B, and C are to be corrected in a section and C was transcribed <emphasis type="b">Z. </emphasis><emphasis type="b">Z</emphasis> is an invalid Alpha Field Designation for the Section.</note></li>
<li>The Error Register will have the corrected Fields A and B printed out, but Field C will still be incorrect.</li>
</alphalist></para>
<para>Action Codes <emphasis type="b">2</emphasis>, <emphasis type="b">3</emphasis>, and <emphasis type="b">7</emphasis> are considered invalid correction attempts under the following conditions: <alphalist>
<li>The Correction Record contains other than the Error Sequence Number, Section Number 01, and Error Action Code, or Reject Disposition Code (Action Code 2 only).</li>
<li>There is more than one section in the Correction Record for an Error Sequence Number.</li>
</alphalist></para>
<para>Action Code <emphasis type="b">4</emphasis> is considered an invalid correction attempt under the following conditions: <alphalist>
<li>An attempt is made to delete any section with a single asterisk (*) before the Section Number.</li>
<li>Attempts are made to delete Section Number 01 which is a required section.</li>
</alphalist></para>
<para>Action Code <emphasis type="b">5</emphasis> is considered an invalid correction attempt when: <alphalist>
<li>The Alpha Field Designators are not in alphabetic sequence.</li>
<li>An attempt is made to add a section already in the error record.</li>
<li>An attempt is made to add a section that has an invalid Section Number. </li>
<li>An attempt is made to add a section with a field that has an Alpha Field Designation not possible for that section.</li>
</alphalist></para>
<para>Action Code <emphasis type="b">6</emphasis> is considered an invalid correction attempt when: <alphalist>
<li>The Alpha Field Designators are not in alphabetic sequence.</li>
<li>An attempt is made to change a field of a section with an invalid Section Number or invalid field breaker.</li>
<li>An attempt is made to change a field of a section which is not on the Error Tape.</li>
<li>An attempt is made to change a field with an Alpha Field Designation not possible for that section.</li>
</alphalist></para>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337100127"><date>(01-01-2023)</date>
<title>Command Codes Used in the Error Resolution System/Rejects/Suspense </title>
<para>The following table lists the majority of the IDRS and ERS command codes used in the ERS, Rejects and Suspense functions. Many of these command codes can be accessed via the IAT tool.<table frame="all" id="id337101503" summary="Command Codes and descriptions">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">IDRS COMMAND CODES</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">DESCRIPTION</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry align="center">SINON</entry>
<entry>Command code is used to sign onto the computer.<bulletlist>
<li>SINON is used by all terminal users, including ERS, GUF and IDRS.</li>
<li>To ensure the accuracy of production reports, be sure to enter CC SINON if the system has been down.</li>
</bulletlist></entry>
</row>
<row>
<entry align="center">SINOF</entry>
<entry>Command code is used to sign off the computer.<bulletlist>
<li>SINOF is used by all terminal users, including ERS, GUF and IDRS.</li>
<li>You must sign off the computer when leaving the terminal or at the completion of your shift.</li>
</bulletlist></entry>
</row>
<row>
<entry align="center">ACTON</entry>
<entry>Shows the Case Control and History. It’s used to:<bulletlist>
<li>Establish control bases.</li>
<li>Update or close control bases that are open.</li>
<li>Correct a name control on dummy accounts.</li>
<li>Append history items to modules on IDRS.</li>
</bulletlist></entry>
</row>
<row>
<entry align="center">ACTVT</entry>
<entry>Command code is used to transfer Unworkable Suspense records to the Workable inventory.</entry>
</row>
<row>
<entry align="center">ADD24/DRT24</entry>
<entry>Command code is used to transfer payment/credits, except credit elects, between modules on all Master Files.</entry>
</row>
<row>
<entry align="center">ADD34/FRM34</entry>
<entry>Command code is used to transfer payment/credits, except credit elects, between modules on one Master File (IMF or BMF).</entry>
</row>
<row>
<entry align="center">ADD48/DRT48</entry>
<entry>Command code is used to transfer credit elects.</entry>
</row>
<row>
<entry align="center">ATINQ</entry>
<entry>Command code is used to research the status of the Adoption Taxpayer Identification Number (ATIN) application (Form W-7A). ATINS are in the same format as an SSN or an ITIN.<bulletlist>
<li>Taxpayers are required to list a TIN for each adoptive dependent child to claim the exemption (2017 and prior). Applicants must submit Form W-7A.</li>
<li>The Austin Submission Processing Campus will process the Form W-7A upon receiving.</li>
<li>The ATIN is a temporary number normally used as a dependent TIN only until the applicant can obtain an SSN.</li>
<li>The taxpayer may not use the ATIN to qualify for EIC.</li>
<li>The ATIN must begin with the digit “9”.</li>
<li>The fourth and fifth digit must be “93”.</li>
<li>The last four digits must be assigned in ascending sequential order.</li>
</bulletlist> See <citation type="IRM">IRM 3.12.3</citation> to process all ATIN error codes.</entry>
</row>
<row>
<entry align="center">BMFOL</entry>
<entry>Command code is used to research nationwide entity and tax data posted to the Business Master File (BMF).</entry>
</row>
<row>
<entry align="center">CFINK</entry>
<entry>Command code is used to research the Centralized Authorization File (CAF) for Power of Attorney (POA).</entry>
</row>
<row>
<entry align="center">CMODE</entry>
<entry>Command code enables users to access and update records on another campus’ database.<bulletlist>
<li>The primary site is responsible for working ERS 100 work.</li>
<li>If your site assisting the primary site, work the ERS 100 work. The assisting site is required to issue the correspondence and use the primary sites signature code. All Unpostables, Entity, Accounting Function, Review or Reject function issues are the responsibility of the primary site.</li>
<li>Do not transship returns or correspondence.</li>
</bulletlist> This command code requires a two-character location acronym as follows:<bulletlist>
<li>Andover (AN)</li>
<li>Austin (AU)</li>
<li>Fresno (FR)</li>
<li>Kansas City (KC)</li>
<li>Ogden (OG)</li>
<li>Philadelphia (PH)</li>
</bulletlist></entry>
</row>
<row>
<entry align="center">COMPA</entry>
<entry>Command code is used to manually compute interest and certain penalties (for example, Failure to Pay, estimated tax).</entry>
</row>
<row>
<entry align="center">CRECT</entry>
<entry>Command code is valid after an error has been displayed in response to the use of Command Codes GTREC and GTSEC.</entry>
</row>
<row>
<entry align="center">DLSEC</entry>
<entry>Command code is used to delete a section from the data record.</entry>
</row>
<row>
<entry align="center">DUPOL</entry>
<entry>Command code is used to access the duplicate TIN database and provides duplicate Social Security Number data.</entry>
</row>
<row>
<entry align="center">ENMOD</entry>
<entry>Command code is used to request the Entity Module for a specific EIN or SSN.</entry>
</row>
<row>
<entry align="center">ENREQ</entry>
<entry>Command code defaults to INCHG (SSN) or BNCHG (EIN) and is used to request an entity update of the Master File.</entry>
</row>
<row>
<entry align="center">ENREQR</entry>
<entry>Command code defaults to IRCHG (SSN) or BRCHG (EIN) and is used to merge two Master File accounts.</entry>
</row>
<row>
<entry align="center">ERINV</entry>
<entry>Command code is used to research a Document Locator Number (DLN) or Taxpayer Identification Number (TIN) on the ERS Control File.</entry>
</row>
<row>
<entry align="center">ERUTL</entry>
<entry>Command code is used to display several different areas in the ERS record for research purposes.</entry>
</row>
<row>
<entry align="center">ERVOL</entry>
<entry>Command code is used to obtain the actual count of records in current Workable Inventory or the status of an error record.</entry>
</row>
<row>
<entry align="center">ESTAB</entry>
<entry>Command code is used to request documents from return files.</entry>
</row>
<row>
<entry align="center">FFINQ</entry>
<entry>Command code is used to research for a DLN using the SSN.</entry>
</row>
<row>
<entry align="center">FINDE</entry>
<entry>Command code is used to research for the business’ name and address information, using the Employer Identification Number (EIN).</entry>
</row>
<row>
<entry align="center">FRM49</entry>
<entry>Command code is used to input Transaction Code (TC) and closing code to finalize or satisfy the requirements for filing a tax return (for example, TC 599 with CC 18 is used to indicate that the original return posted to the wrong module and will be reprocessed to the correct module).</entry>
</row>
<row>
<entry align="center">GTREC</entry>
<entry>Command code is used to access the following:<bulletlist>
<li>First error record in an ERS error block. </li>
<li>A specific record in the Workable Suspense Inventory. </li>
<li>Re-display the previous uncorrected error display of a record after performing IDRS operations for the error.</li>
<li>Previous uncorrected error display is desired.</li>
</bulletlist></entry>
</row>
<row>
<entry align="center">GTSEC</entry>
<entry>Command code is used to obtain or enter a specific section on an ERS record.</entry>
</row>
<row>
<entry align="center">IMFOL</entry>
<entry>Command Code is used to research accounts posted to the Individual Master File (IMF).</entry>
</row>
<row>
<entry align="center">INOLE</entry>
<entry>Command code is used to access the National Account Profile (NAP) which contains selected entity information for all Master File (MF) accounts.</entry>
</row>
<row>
<entry align="center">INTST</entry>
<entry>Command code is used to compute the correct outstanding balance including interest and failure to pay accruals to the date specified in the input.</entry>
</row>
<row>
<entry align="center">IRPTR</entry>
<entry>Command code is used to request either online or hardcopy IRP transcripts from Information Return Master File (IRMF).</entry>
</row>
<row>
<entry align="center">LETER</entry>
<entry>Command code is used to initiate taxpayer correspondence.</entry>
</row>
<row>
<entry align="center">LPAGD</entry>
<entry>Command code is used to delete a letter.</entry>
</row>
<row>
<entry align="center">MFREQ</entry>
<entry>Command code is used to request an entity module and/or a tax module from Master File when case control is not required.</entry>
</row>
<row>
<entry align="center">MFTRA</entry>
<entry>Command code is used to request transcripts from a taxpayer’s account at Master File.</entry>
</row>
<row>
<entry align="center">NAMEE and NAMEB</entry>
<entry>Command code is used to search for EINS and SSNV accounts. </entry>
</row>
<row>
<entry align="center">NAMEI and NAMES</entry>
<entry>Command code is used to search for SSNs for the primary and secondary filers.</entry>
</row>
<row>
<entry align="center">NOREF</entry>
<entry>Command code is used to intercept refunds.</entry>
</row>
<row>
<entry align="center">NWDLN</entry>
<entry>Command code is used to assign a new DLN to a record. This action deletes the original record.</entry>
</row>
<row>
<entry align="center">QRSEL</entry>
<entry>Command code is used to select a record which will remain in ERS one day for quality/CARE review and possible correction.</entry>
</row>
<row>
<entry align="center">REINF</entry>
<entry>Command code is used to research IDRS Refund Information File (RFIF).</entry>
</row>
<row>
<entry align="center">REQ54/ADJ54</entry>
<entry>Command code is used to make data processing (DP) adjustments to tax, penalty and/or interest.</entry>
</row>
<row>
<entry align="center">REQ77/FRM77</entry>
<entry>Command code is used to input miscellaneous transactions.</entry>
</row>
<row>
<entry align="center">RFUND</entry>
<entry>Command code is used to generate a manual refund to the taxpayer.</entry>
</row>
<row>
<entry align="center">RJECT</entry>
<entry>Command code is used to delete a record from ERS.</entry>
</row>
<row>
<entry align="center">RTFTP</entry>
<entry>Command code is used to sanitize version of CC RTVUE for printing and mailing to the taxpayer.</entry>
</row>
<row>
<entry align="center">RTVUE</entry>
<entry>Command code is used to display the line item transcribed from <citation type="Form">Form 1040</citation> series and their accompanying schedules and/or forms as the returns are processed at the campuses.</entry>
</row>
<row>
<entry align="center">SCFTR</entry>
<entry>Command code is used to research the Service Center Control File (SCCF) for the status of a block DLN.</entry>
</row>
<row>
<entry align="center">SFDISP</entry>
<entry>Command code is used to view a listing of the command codes in an employee’s profile.</entry>
</row>
<row>
<entry align="center">SFINQ</entry>
<entry>Command code is a security command code limited to security representatives.</entry>
</row>
<row>
<entry align="center">SSPND</entry>
<entry>Command code is used with an ERS Action Code to place a record in suspense status.</entry>
</row>
<row>
<entry align="center">STAUP</entry>
<entry>Command code is used to suppress balance due notices generated by IDRS that are normally sent to the taxpayer.</entry>
</row>
<row>
<entry align="center">SUMRY</entry>
<entry>Command code is used to request a summary for an account on IDRS for a particular TIN and File Source.</entry>
</row>
<row>
<entry align="center">TERUP</entry>
<entry>Command code is used to delete erroneous transactions (for example tax adjustments).</entry>
</row>
<row>
<entry align="center">TRDBV</entry>
<entry>Command code is used to obtain a display of edited transcribed and corrected data from electronically filed returns.</entry>
</row>
<row>
<entry align="center">TRERS</entry>
<entry>Command code is used to link the DLN entered with command code GTREC, with the TRDBV and display the electronic or transcribed posted paper return.</entry>
</row>
<row>
<entry align="center">TRPRT</entry>
<entry>Command code is used to order electronic filed tax returns.</entry>
</row>
<row>
<entry align="center">TXMOD</entry>
<entry>Command code is used to request all tax module information for a specific tax period on the TIF.</entry>
</row>
<row>
<entry align="center">UPCAS</entry>
<entry>Command code is used to add or delete history items posted on the Generalized Unpostable Framework (GUF) database.</entry>
</row>
<row>
<entry align="center">UPDIS/UPRES</entry>
<entry>Command code is used to correct unpostable cases.</entry>
</row>
<row>
<entry align="center">UPTIN</entry>
<entry>Command code is used to research open and closed cases on the GUF database.</entry>
</row>
<row>
<entry align="center">URINQ</entry>
<entry>Command code is used to research credits in the Unidentified Remittance File (URF).</entry>
</row>
<row>
<entry align="center">XSINQ</entry>
<entry>Command code is used to research credits in the Excess Collection File (XSF).</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Command Code ERUTL is a utility command code which displays several different areas within the ERS record for research purposes. It can be used to display the following:<bulletlist>
<li>Section problem indicators (Priority II Errors)</li>
<li>The error code and clear code indicators (Priority IV Math and Consistency Errors)</li>
<li>Section presence indicators</li>
<li>Selected header information<note>This code is valid for workable records or on the day the record is worked.</note></li>
</bulletlist></para>
<para>If only CC ERUTL is entered, a screen listing the available function codes and their uses will be displayed.<steplist>
<li>ERUTL DPD displays section problem indicators for Priority II section problems.</li>
<li>ERUTL DEI displays field error indicators for Priority III Errors.</li>
<li>ERUTL DEC displays Error Codes and Clear Codes for Priority IV Errors.<br/> An “*” appears where an error code is set<br/> A “C” appears where an error code is cleared</li>
<li>ERUTL DSP displays section presence indicators<br/> A “0” indicates section is not present<br/> A “1” indicates section is present</li>
<li>ERUTL DHR displays the following ERS header information:<br/> Line 1: Header information (DLN, current date, and time)<br/> Line 2: Blank<br/> Line 3: Document DLN<br/> Line 4: Document program number<br/> Line 5: Employee number (last person to update the record)<br/> Line 6: Shows a “Y” if the record has an invalid action code (Priority I Error)<br/> Line 6: Shows an “R” if document was reworked<br/> Line 7: Displays any Action Code assigned to the record<br/> Line 7: File from which the record was loaded (Error or Suspense)<br/> Line 8: ERS worked indicator (“W” for Worked or “U” for Unworked)<br/> Line 8: Disposal code listed in the following (8)<br/> Line 9: The action taken is listed in the following (7)<br/> Line 10: Any remittance amount displayed with the error<br/> Line 10: DLN of the record<br/> Lines 11-13: CAPR Code Modules<br/> Line 14: RPS indicator is listed in the following (9)<br/> Line 15: EIF Access Indicators<br/> Lines 16-23: NAP Access/Response Indicators</li>
</steplist></para>
<para>The line 9 Action taken for the parameter “DHR” are as follows:<alphalist>
<li>CORRECTED-indicates error free record</li>
<li>NEW DLN XXXXX-XXX-XXXXX-X- indicates a new DLN was assigned</li>
<li>SUSPENDED-indicates record was suspended</li>
<li>NOT WORKED-indicates record is not worked</li>
<li>REJECTED-indicates record was rejected. It listed the reason it was rejected such as: ANMF/NON-ADP, REENTRY, VOID, INTERNATIONAL, DATA CONTROL DELETE, or MISSING DOCUMENT</li>
</alphalist></para>
<para>The line 8 Disposal Code can be one of the following:<alphalist>
<li>1-error record awaiting correction</li>
<li>2-suspense record awaiting information</li>
<li>3-suspense record with expired suspense period</li>
<li>4-suspense record with information</li>
<li>5-record was deleted</li>
<li>6-record is corrected and error free</li>
</alphalist></para>
<para>The line 14 RPS indicator can be one of the following:<alphalist>
<li>Blank-for non-ISRP</li>
<li>S-for IMF ISRP</li>
<li>2-for BMF ISRP</li>
</alphalist></para>
<para>For further explanation, screen displays, and applicable definer codes, refer to <citation type="IRM">IRM 2.3</citation> IDRS Terminal Responses, <citation type="IRM">IRM 2.4</citation> IDRS Terminal Input, and the applicable training series.</para>
</subsection1>
<subsection1 id="id337101239"><date>(11-10-2021)</date>
<title>Integrated Automation Technologies (IAT)</title>
<para>IAT tools simplify research, reduce keystrokes and increase the accuracy work. They also improve efficiency, productivity and quality by performing some functions automatically. Instructions on how to use each IAT tool can be found on the IAT website.</para>
<para>Managers will ensure employees understand that the use of IAT is mandatory and will verify that employees have access to all the tools needed for their duties. Managers will ensure all employees receive training on the use of IAT Tools.</para>
<para>IAT uses IDRS to gather and submit data. If IDRS is down or not functioning properly, or a command code is down or not functioning properly, IAT will not function correctly.</para>
<para>If you are having a problem with an IAT tool, try entering the command code manually using IDRS.</para>
</subsection1>
<subsection1 id="id337100157"><date>(01-01-2023)</date>
<title>Suspense Correction</title>
<para>This subsection lists the procedures for resolving the below errors.<bulletlist>
<li>Mixed data.</li>
<li>Unrecognizable Field Error</li>
<li>Action Code 430</li>
</bulletlist></para>
<subsection2 id="id337100158"><date>(01-01-2023)</date>
<title>Mixed Data Correction Procedures</title>
<para> Mixed data occurs when information from one document is input under the wrong DLN. </para>
<para> Take mixed data documents to your work lead and/or manager to contact Accounting before processing the documents.</para>
</subsection2>
<subsection2 id="id337100171"><date>(01-01-2023)</date>
<title>Unrecognizable Field Error Correction Procedures</title>
<para>An unrecognizable field error displays when a field error cannot be displayed and/or contains invalid data.</para>
<para>To resolve this condition, enter CC GTSEC 01, go to the bottom of the screen, and transmit. If this does not resolve the Unrecognizable field error <emphasis type="b">RJECT 630</emphasis> the document and re-input the document to resolve the error.</para>
<para>All MeF unrecognizable field errors must be renumbered to a paper DLN using CC <emphasis type="b">NWDLN 610</emphasis>.<note notetype="reminder">When renumbering a MEF return be sure to print all documents from EUP and write do not correspond for signature on the signature line.</note></para>
</subsection2>
<subsection2 id="id337100172"><date>(01-01-2025)</date>
<title>Action Code 430 Correction Procedures</title>
<para> Action Code <emphasis type="b">430</emphasis> is edited by C&amp;E when a return is received with a statement or Form 8958, <emphasis type="b">Allocation of Tax Amounts Between Certain Individuals in Community Property States</emphasis> and when an amount is present on or near line 26, Form 1040 indicating the taxpayer wants the credit applied to the spouse's account. </para>
<para>Follow <citation type="IRM">IRM 3.12.3</citation> Error Code 260 for correction procedures for community property returns. </para>
<para>If the return is FSC 3 or FSC 6 and there is a statement or schedule present showing how estimated payments are to be allocated, use the following instructions:<alphalist>
<li>Research forms and schedules to determine correct taxpayer/spouse.</li>
<li>Review Form 8958 and statements to determine taxpayer’s intent.</li>
<li>Research IDRS CC TXMODA and CC IMFOLT to verify credit amount is correct to transfer.</li>
<li>Verify the amount is correct before inputting credit transfer. <note>Use the IAT Credit Transfer Tool to input the credit transfer. If IDRS is down the tool will not function properly. </note></li>
<li>Follow taxpayer's intent/request and transfer the credit as requested per Form 8958 or statements.</li>
<li>Follow <seealso idref="id337100373">IRM 3.12.37.15.6</seealso> for Credit Transfer instructions.</li>
<li>If unable to determine taxpayer's intent, <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict>.</li>
</alphalist><note notetype="caution">If the taxpayer requests a credit transfer input the credit transfer first and hold the return to allow the credit transfer to post. After the credit transfer posts work the return.</note>: </para>
</subsection2>
</subsection1>
<subsection1 id="id337100194"><date>(01-01-2026)</date>
<title>Unpostables</title>
<para>This subsection lists the procedures for receiving and correcting unpostables.<alphalist>
<li>Receiving rejected and auto voided unpostables</li>
<li>Types of rejected unpostables</li>
<li>Applicable unpostables and their various correction procedures</li>
</alphalist></para>
<para>Customer Account Data Engine (CADE) IMF will identify unpostable criteria daily, but the files will not be processed by GUF until the weekly cycle. The Unpostable cycle closes weekly on Tuesday. This may result in subsequent transactions posting in the same cycle. </para>
<subsection2 id="id337100195"><date>(01-01-2023)</date>
<title>Receiving Rejected Unpostables</title>
<para>Unpostable records are received directly from the Generalized Unpostable Framework (GUF).</para>
<para>Each reject unpostable (or batch of rejected unpostables) will include an explanation of the unpostable condition, the suggested action, and the document or return. Normally this information is shown in an Unpostable Routing Slip (Form 8749), or an attached CC UPRES print. Ensure Form 8749 is stapled and maintained with the document/return. Any document or return received without a satisfactory or with a conflicting explanation will be referred to unpostable for clarification. </para>
<para>All nullified records are listed on the Nullified Distribution Listing (GUF–55–47) by the area that is to receive the documents. The Nullified Distribution Listing provides an audit trail for all nullified closures (URC <emphasis type="b">1</emphasis>, <emphasis type="b">2</emphasis> or <emphasis type="b">8</emphasis>).</para>
<para>Items nullified with URC <emphasis type="b">8</emphasis> will appear on a listing titled <emphasis type="b">Nullified Distribution Listing—Rejects</emphasis>. When receiving 8 coded returns use the GUF-55-47 to verify.</para>
<para>The Reject function will receive a copy of the listing for all URC <emphasis type="b">8</emphasis> closures. Cases may also be referred back to the Unpostable Function for clarification. </para>
</subsection2>
<subsection2 id="id337100197"><date>(01-01-2020)</date>
<title>Types of Rejected Unpostables</title>
<para>Rejected Unpostables are divided into four categories: <bulletlist>
<li>Statute Cases</li>
<li>Batch Rejects</li>
<li>Missing Documents</li>
<li>Unpostable Resolution Code (URC) <emphasis type="b">8</emphasis></li>
</bulletlist></para>
<subsection3 id="id337100198"><date>(01-01-2026)</date>
<title>Statute Cases</title>
<para>After reviewing the documents, the Statute Unit will make corrections to the files available to them on the GUF screen. The Statute Unit will <emphasis type="b">URC 8 code</emphasis> the case to be worked by Rejects/Suspense.</para>
</subsection3>
<subsection3 id="id337100199"><date>(01-01-2020)</date>
<title>Batch Rejects</title>
<para>Certain unpostable conditions are identified and corrected for several documents at the same time. These may be received with a single Unpostable Routing Slip for the entire batch of unpostable documents.</para>
</subsection3>
<subsection3 id="id337100200"><date>(01-01-2025)</date>
<title>Missing Documents</title>
<para>Unpostables is required to conduct the initial research for missing documents and three additional follow-up searches: one after the initial search and 2 at approximately 14-day intervals. <alphalist>
<li>When a record is rejected (after the third search), all research documentation is routed to Rejects to await the outcome of the fourth search request initiated by Unpostables. An unpostable routing slip is attached to indicate the reason for the unpostable and the corrective action (when appropriate). </li>
<li>When additional information or action is needed to process the return and Unpostables is unable to locate the correct taxpayer entity information, and the record has been processed with full entity, then Rejects/Suspense will be able to correspond or request a copy of the return.</li>
</alphalist></para>
<para>If all of the procedures in the proceeding (1) a. and b. have been addressed with no resolution, make copies of all the ERS screen displays (all sections with entries) and proceed as follows: <table frame="all" id="id337100843" summary="Remittance and Non Remittance" width="4.5in">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colname="col1" colwidth="43*"/>
<colspec colname="col2" colwidth="57*"/>
<thead>
<row>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">If the return is </emphasis></entry>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="3"><emphasis type="b">A]</emphasis> A non-remittance</entry>
<entry colsep="1" rowsep="3">Enter CC RJECT with Action Code 640.</entry>
</row>
<row>
<entry colsep="1" rowsep="3"><emphasis type="b">B]</emphasis> A remittance</entry>
<entry>If transferring the money to Unidentified, enter CC NWDLN with Action Code 611 and the literal <emphasis type="b">URF</emphasis>. If transferring to Excess Collection, use the literal <emphasis type="b">EXC</emphasis>.</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
<subsection3 id="id337100201"><date>(01-01-2026)</date>
<title>URC <emphasis>8</emphasis></title>
<para>URC <emphasis type="b">8</emphasis> is used by Unpostables Tax Examiner when it is determined the document must be corrected by Rejects/Suspense. A separate unpostable routing slip will be attached with an explanation of the unpostable condition and the proposed resolution (corrective action). URC <emphasis type="b">8</emphasis> documents may originate with instructions from Unpostables, Entity, Fraud Detection Center, or Statutes. Tax examiners must utilize the GUF-55-47(Nullified Distribution Listing report) in Control-D or Form 8749 when processing cases.</para>
<para>Revalidate all returns before correcting the Unpostable record by using GTSEC 02 and entering <emphasis type="b">R</emphasis> in Field 02RI.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100203"><date>(01-01-2026)</date>
<title>Receiving Autovoid Unpostables</title>
<para>Rejects will be receiving certain unpostable returns directly from the GUF system.</para>
<para> Auto Void from GUF will need to be worked using the Error Resolution System by accessing the DLN document via CC GTREC on IDRS. Rejects tax examiners will follow the procedures in <citation type="IRM">IRM 3.12.3</citation><emphasis type="b"> Individual Income Tax Returns</emphasis> when resolving the unpostable returns.</para>
<para>The ERS Priority I screen has been changed to display the Master File unpostable and reason code on all transactions with Action Code 900.</para>
<para>For more detailed information on category codes see <citation type="IRM">IRM 3.12.32</citation> <emphasis type="b">Generalized Unpostable Framework</emphasis> (GUF).</para>
</subsection2>
<subsection2 id="id337101146"><date>(11-10-2021)</date>
<title>Unpostable Code 126 RC 0</title>
<para>This condition has been expanded to include TC 971 AC 124. Also, unposts if TC 971 AC 121 or AC 124 with a DLN in the MISC Field equal to the return DLN is input in the same cycle as the TC 150.<note>The Taxpayer Protection Program (TPP) is responsible for identifying potential identity theft cases that are scored by a set of identity theft models in the Dependent Database (DDb), selected through filters in the Return Review Program (RRP) system or manually selected by Return Integrity Verification Operations (RIVO). </note></para>
<para>Bypass the UPC 126 0 if the IP-PIN on the input return is equal to the IP-PIN posted on CC <emphasis type="b">ENMOD</emphasis>.</para>
<para>UPC 126 RC 0 GUF is worked by the Return Integrity Verification Operations (RIVO) Taxpayer Protection Program (TPP)</para>
<subsection3 id="id337101147"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 126 RC 0</title>
<para>Verify and correct all Entity in Section 01.</para>
<para>Follow instructions given by RIVO unit to process the return and assign all applicable TPNCs.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101628"><date>(01-01-2025)</date>
<title>Unpostable Code 130 RC 0</title>
<para>This unpostable occurs when an input transaction contains information that causes a halt in the posting run.</para>
<subsection3 id="id337101542"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 130 RC 0</title>
<para>Compare the tax return with all fields on the screen. </para>
<para>Verify the taxpayer's SSN, name, address and ALL money amount fields before transmitting. Ensure the AGI, total tax and withholding amounts are the same as the taxpayer's figures.</para>
<para>If the debit module is $999 million or greater, follow instructions in <seealso idref="id337100542">IRM 3.12.37.15.5.4</seealso> for cases over $999 million dollars.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100848"><date>(11-10-2021)</date>
<title>Unpostable Code 136 RC 1 </title>
<para>Occurs when TC 150 attempts to post with a Primary SSN that starts with a <emphasis type="b">9</emphasis> containing a claim for the EIC Computer and/or a personal exemption attempts to post.<note>Master File will bypass this check if the SSN is in the ITIN range (middle two digits are 50-65,70-88, 90-92, 94-99). Master File will bypass the exemption portion of the unpostable if the exemption positions verified field contains a 0 in position 1 or if the return contains RPC <emphasis type="b">O</emphasis>.</note></para>
<subsection3 id="id337100851"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 136 RC 1</title>
<para>Research for the correct TIN/ITIN and name control of the taxpayer. Research to determine the correct last name of the taxpayer. Ensure the TIN/ITIN and last name/NC were transcribed correctly.<note notetype="caution">If the TIN has been changed to an ITIN/IRSN, follow the instructions in paragraphs 3-7.</note></para>
<para>If the TIN/ITIN or name control requires correction, use <citation type="IRM">IRM 3.12.2</citation> Section 01 to correct fields as needed. Ensure all corrective action is taken before proceeding. </para>
<para>If either the primary or the secondary taxpayer has a TIN/ITIN/IRSN starting with a <emphasis type="b">9</emphasis> ensure RPC <emphasis type="b">A</emphasis> is removed from the Field 01RPC. Assign TPNC 702 when EIC is limited to zero at EC 337 or EC 338.</para>
<para>If the primary taxpayer has an IRSN, ensure RPC <emphasis type="b">O</emphasis> is present.</para>
<para>If the TIN is invalid enter RPC <emphasis type="b">O</emphasis> and if EIC is claimed enter RPC <emphasis type="b">B</emphasis>.</para>
<para>If RPC O is present, enter 0 in the first position of Field 94EXV.</para>
<para>Assign appropriate TPNCs when exemptions, EIC or other credits are disallowed.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101050"><date>(01-01-2025)</date>
<title>Unpostable Code 140 </title>
<para>UPC 140 RC 3 will unpost an RPC TC 150 if the posted RPS TC 610 or TC 610 with Doc Code 19, 70, or 76 has been reversed by a TC 612.</para>
<subsection3 id="id337101629"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 140 RC 3</title>
<para>Follow instructions from Unpostables to post TC 150 to the correct module.</para>
</subsection3>
<subsection3 id="id337101630"><date>(01-01-2025)</date>
<title>Unpostable Code 140 RC 5</title>
<para>This condition occurs when a TC 150 contains a transaction date prior to the transaction date of an unreversed TC 610 or unreversed TC 610 with Doc Code 19, 70, or 76 which is dated <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></para>
<subsection4 id="id337101627"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 140 RC 5</title>
<para>Verify the correct date of the return.</para>
<para>Consider the return filed on time and enter the received date in Field 01RCD when all of the following exist:<alphalist>
<li>The return was originally received by the due date</li>
<li>Code and Edit or ITIN corresponded with the taxpayer</li>
</alphalist></para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337100852"><date>(01-01-2026)</date>
<title>Unpostable Code 141 RC 0 </title>
<para>TC 150 does not contain RPC<emphasis type="b"> F</emphasis> and is input to a module containing an unreversed TC 971 AC 114.</para>
<para>TC 150 contains RPC <emphasis type="b">F</emphasis>, after resequencing two cycles, the input module does not contain a posted unreversed TC 971 AC 114.</para>
<para>TC 150 contains RPC<emphasis type="b"> F</emphasis>, and the Other payment CR amount is greater than the TC 971 AC 114 MISC field Total 965 amount.</para>
<para>TC 150 is input to module containing a posted TC 971 AC 115 and the other payment CR amount is equal to or less than the TC 971 AC 115 MISC field Deferred amount.</para>
<para>TC 670 DPC 64 input to MFT 29, 35, 65, 55.</para>
<para>Unpost the input return if the Total 965 tax amount is significant and RPC F is not present on the return.</para>
<para>Unpost the input return if the TC 150 contains RPC F and the Total 965 tax is equal to $0 and 965 Installment amount is significant.</para>
<para>Unpost the input return if the deferred 965 amount is greater than the Total 965 amount.</para>
<para>Unpost the Return if the Other Payment Credit Type Code is <emphasis type="b">T</emphasis> and both RPC<emphasis type="b"> F</emphasis> and TC 971 AC 114 are not present.</para>
<para>Unpost TC 150 (except Doc Code 26) input into a module containing an unreversed TC 971 AC 150.</para>
<subsection3 id="id337100855"><date>(01-01-2026)</date>
<title>Correction Procedures UPC 141 RC 0 </title>
<para>All Section 965 Conditions can only be resolved by following <citation type="IRM">IRM 3.12.3</citation> instructions and Error Code 188.</para>
<para>If the condition is TC 670 DPC 64 with MFT 29, 35, 65, 55 research IDRS CC SUMRY, IMFOLI, IMFOLT, TXMODA, and the RTR system. Determine the correct payment amount, tax period, MFT and DPC. </para>
<para>If unable to determine where to apply the payment because the taxpayer has multiple balances due and does not designate the form type or tax year on the check, apply the payment to the earliest unexpired CSED date. If multiple tax periods have the same CSED date, apply to the earliest tax period.</para>
<para>If the condition is not related to Section 965 or DPC 29 TC 670 and the document unpost due to an unreversed TC 971 AC 150 use the following instructions: <alphalist>
<li>Void the DLN, RJECT 640/651</li>
<li>Route to ICT and </li>
<li>Complete and attach Form 4227</li>
<li>Input in the Other box on Form 4227: <br/> Scan the returns into CII as IMF International, using CII ID number <emphasis type="b">0538497111</emphasis> and category code IRRQ. Reverse TC 971 AC 150 and letter issue 86c to taxpayer.</li>
</alphalist></para>
<para>If the taxpayer is only reporting IRC 965 election payment, remove RPC F as well as any money amount in Field 05TL.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100206"><date>(01-01-2020)</date>
<title>Unpostable Code 145 RC 0</title>
<para>Unpostable Code 145 is for Substitute for Returns (SFR).</para>
<para>Occurs when a TC 150 SFR (Doc Code 10, Blocking Series 000–299) attempts to post to a module with a posted TC 150.</para>
<subsection3 id="id337100207"><date>(02-09-2022)</date>
<title>Correction Procedures UPC 145 RC 0</title>
<para>Research command codes TXMODA and IMFOLT to determine the correct area to send the return. </para>
<para>Void the DLN and route the document to either -Automated Substitute for Returns (ASFR) or CORR-EXAM (Examination). </para>
<para>Cases posted with TC 150 on the account and TC 290 for $0.00 will be sent to ASFR.</para>
<para>Cases with an L freeze or TC 420 will be sent to Exam.</para>
<para>The addresses below are used to send delinquent secured returns to ASFR when it has been identified that a previous ASFR assessment has been made. <table frame="all" id="id337100873" summary="Address for deliinquent for ASFR" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="6.89in"?>
<colspec colname="col1" colwidth="34.24*"/>
<colspec colname="col2" colwidth="34.13*"/>
<colspec colname="col3" colwidth="31.63*"/>
<thead>
<row>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">TS Cases</emphasis></entry>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">SB/SE Cases Form 1040 with Schedule C, E, F or Form 2106</emphasis></entry>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">International Returns </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="3">FSC - 89</entry>
<entry colsep="1" rowsep="3">BSC - 19</entry>
<entry colsep="1" rowsep="3">BSC - 19</entry>
</row>
<row>
<entry colsep="1" rowsep="3">Fresno Campus ASFR Unit Stop 81304 3211 S. Northpointe Fresno CA 93725</entry>
<entry colsep="1" rowsep="3">Brookhaven Campus ASFR Unit Stop 654 PO Box 9013 5000 Corporate Ct. Holtsville, NY 11742 </entry>
<entry>Brookhaven Campus ASFR Unit Stop 654 PO Box 9013 5000 Corporate C. Holtsville, NY 11742 </entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
</subsection2>
<subsection2 id="id337101631"><date>(01-01-2025)</date>
<title>Unpostable Code 147 RC 0</title>
<para>This condition occurs when a return does not contain a matching IP PIN, when an IP PIN is present in the entity. The IP PIN indicator is placed on the accounts of taxpayers who have previously been identified as victims of identity theft.<alphalist>
<li>If an Identity Protection PIN has been issued to the taxpayer, then the return will unpost if the PIN is not present or is input incorrectly.</li>
<li>The IP PIN will not be visible on IDRS and will not be correctable.</li>
</alphalist></para>
<para>Returns with CRIM Control bases/Z freezes.</para>
<subsection3 id="id337101534"><date>(01-01-2025)</date>
<title>Correction Procedures 147 RC 0</title>
<para>Follow instructions from Unpostables to deny the personal exemption as well as EIC if claimed and input CCC 3 to freeze the refund.</para>
<para>Follow instructions from Unpostables to void the return.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100608"><date>(01-01-2020)</date>
<title>Unpostable Code 148</title>
<para>Unpostable Code 148 is for a missing spouse's SSN.</para>
<subsection3 id="id337100609"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 0 and RC 1</title>
<para>Unpostable Condition—UPC 148 RC 0– Occurs when a TC 150 with Section 18 (<emphasis type="b">Schedule SE</emphasis> for the spouse) is present and transaction does not contain a secondary SSN, and no secondary SSN is present to control the name line for the input period.</para>
<para>Unpostable Condition—UPC 148 RC 1– Occurs when a TC 150 with Section 18 (<emphasis type="b">Schedule SE</emphasis> for the spouse) is present and Field 18SSN does not match the secondary SSN for the controlling name line of input return contained in entity or not matching S–SSN from input return.</para>
<subsection4 id="id337100610"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 148 RC 0</title>
<para>Use the following chart to correct UPC 148, RC 0. <table frame="all" id="id337100716" orient="port" pgbrk="nobreak" summary="UPC 148 RC 0 " width="4.5in">
<tgroup align="left" cols="3" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="33*"/>
<colspec colname="col2" colnum="2" colwidth="33*"/>
<colspec colname="col3" colnum="3" colwidth="34*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If the Schedule SE is for</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> And</emphasis></entry>
<entry morerows="0" nameend="col3" namest="col3"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> The primary taxpayer,</entry>
<entry morerows="0"/>
<entry morerows="0" nameend="col3" namest="col3">Correct the SSN and change Section 18 to Section 17.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> The primary taxpayer,</entry>
<entry morerows="0" nameend="col2" namest="col2">Section 17 is blank,</entry>
<entry morerows="0" nameend="col3" namest="col3">Correct Field 18SSN and the computer will generate the data from Section 18 to Section 17 based on the SSN.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> C]</emphasis> The secondary taxpayer,</entry>
<entry morerows="0" nameend="col2" namest="col2"/>
<entry morerows="0" nameend="col3" namest="col3">Correct Fields 18SSN and 01SS. Add the spouse's name to Field 01NL1.</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection4>
<subsection4 id="id337100611"><date>(04-25-2022)</date>
<title>Correction Procedures UPC 148 RC 1</title>
<para>Use the following chart to correct UPC 148, RC 1. <table frame="all" id="id337100717" orient="port" pgbrk="nobreak" summary="Correction procedures for UPC 148 RC 1 for Schedule SE" width="4.5in">
<tgroup align="left" cols="3" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="33*"/>
<colspec colname="col2" colnum="2" colwidth="33*"/>
<colspec colname="col3" colnum="3" colwidth="34*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If the Schedule SE is for</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> And</emphasis></entry>
<entry morerows="0" nameend="col3" namest="col3"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> The primary taxpayer,</entry>
<entry morerows="0"/>
<entry morerows="0" nameend="col3" namest="col3">Verify and/or correct Fields 01PS and 18SSN.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> The primary taxpayer,</entry>
<entry morerows="0" nameend="col2" namest="col2">Section 17 is blank,</entry>
<entry morerows="0" nameend="col3" namest="col3">Correct Field 18SSN and the computer will generate the data from Section 18 to Section 17 based on the SSN.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> C]</emphasis> The secondary taxpayer,</entry>
<entry morerows="0"/>
<entry morerows="0" nameend="col3" namest="col3">Verify and/or correct Fields 01SS and 18SSN.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> D]</emphasis> The secondary taxpayer,</entry>
<entry morerows="0" nameend="col2" namest="col2">There are no transcription errors, and the correct SSN is not available from the return or attachments, </entry>
<entry morerows="0" nameend="col3" namest="col3">Research IDRS for an SSN. If an SSN is found, enter in appropriate field(s). If an SSN is not available, SSPND 211 to correspond with the taxpayer.</entry>
</row>
</tbody>
</tgroup>
</table><note notetype="note">Refer to <citation type="IRM">IRM 3.12.2</citation> Section 17/18 and <citation type="IRM">IRM 3.12.3</citation> for appropriate Error Codes.</note></para>
</subsection4>
</subsection3>
<subsection3 id="id337100612"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 2</title>
<para>Unpostable Condition-UPC 148 RC 2- Occurs when a TC 150 with Section 25 (<emphasis type="b">Form 4137</emphasis> for the spouse) is present and transaction does not contain a secondary SSN, and no secondary SSN is present to control the name line for the input period.</para>
<subsection4 id="id337100613"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 148 RC 2</title>
<para>If the Form 4137 is for the primary taxpayer, correct the SSN in Field 24SSN/25SSN. Refer to <citation type="IRM">IRM 3.12.2</citation> (Section 24/25 and appropriate Error Codes). </para>
<para>If the Form 4137 is for the spouse, correct Fields 25SSN/01SS and add the spouse's name to Field 01NL1.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100614"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 3</title>
<para>Unpostable Condition-UPC 148 RC 3- Occurs when a TC 150 with Section 25 (<emphasis type="b">Form 4137</emphasis> for the spouse) is present and Field 25SSN does not match the secondary SSN for the controlling name line of input return contained in entity or not matching S–SSN from input return.</para>
<subsection4 id="id337100615"><date>(04-25-2022)</date>
<title>Correction Procedures UPC 148 RC 3</title>
<para>Use the following chart to correct UPC 148, RC 3.<table frame="all" id="id337101012" summary="Correction of UPC 148 RC3 and SSNs" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="col3" colwidth="33*"/>
<thead>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">If the Form 4137 is for</emphasis></entry>
<entry colsep="1" rowsep="1"><emphasis type="b">And</emphasis></entry>
<entry colsep="1" rowsep="1"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">A]</emphasis> The primary taxpayer,</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Verify and/or correct Fields 01PS and 25SSN.</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">B]</emphasis> The primary taxpayer,</entry>
<entry colsep="1" rowsep="1">Section 24 is blank,</entry>
<entry colsep="1" rowsep="1">Correct Field 25SSN and the computer will generate the data from Section 25 to Section 24 based on the SSN.</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">C]</emphasis> The secondary taxpayer,</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Verify and/or correct Fields 01SS and 25SSN.</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">D]</emphasis> The secondary taxpayer,</entry>
<entry colsep="1" rowsep="1">There are no transcription errors, and the correct SSN is not available from the return or attachments,</entry>
<entry colsep="1" rowsep="1">Research IDRS for an SSN. If an SSN is found, enter in appropriate field(s). If an SSN is not available, SSPND 211 to correspond with the taxpayer.</entry>
</row>
</tbody>
</tgroup>
</table><note>Refer to <citation type="IRM">IRM 3.12.2</citation> (Section 24/25) and <citation type="IRM">IRM 3.12.3</citation> for appropriate Error Codes.</note></para>
</subsection4>
</subsection3>
<subsection3 id="id337100975"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 4</title>
<para>Unpostable Code -148 RC4 - Occurs when a TC 150 with Section 62 (<emphasis type="b">Form 8919</emphasis> for the spouse) is present and transaction does not contain a secondary SSN, and no secondary SSN is present to control the name line for the input period.</para>
<subsection4 id="id337100976"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 148 RC 4</title>
<para>Correct transcription errors and misplaced entries in Sections 61 and 62.</para>
<para>Verify the Primary and Secondary name line and SSN in Section 01.</para>
<para>Ensure the primary taxpayer's data is in Section 61 and the secondary taxpayer's data is in Section 62.</para>
<para>Ensure all data present on Form 8919 has been entered into the correct fields for Section 61/62.</para>
<para>Delete Section 61 and/or 62 if the taxpayer has not used/completed Form 8919.</para>
<para>Follow correction procedures in <citation type="IRM">IRM 3.12.2</citation> Section 61/62 and <citation type="IRM">IRM 3.12.3</citation> for appropriate Error Codes.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100977"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 5</title>
<para>Unpostable Condition -148 RC 5 - Occurs when a TC 150 with Section 62 (<emphasis type="b">Form 8919</emphasis> for the spouse) is present and Field 62SSN does not match the secondary SSN for the controlling name line of input return contained in entity or not matching S–SSN from input return.</para>
<subsection4 id="id337100978"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 148 RC 5</title>
<para>Correct transcription errors and misplaced entries in Sections 61 and 62.</para>
<para>Verify the secondary SSN in Field 01SS.</para>
<para>Ensure the secondary SSN in Field 01SS matches the secondary SSN in Field 62SSN.</para>
<para>Ensure all data present on Form 8919 has been entered into the proper fields for Section 61/62.</para>
<para>Delete Section 61 and/or 62 if the taxpayer has not used/completed Form 8919.</para>
<para>Follow correction procedures in <citation type="IRM">IRM 3.12.2</citation> Section 61/62 and <citation type="IRM">IRM 3.12.3</citation> for appropriate Error Codes.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100988"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 6</title>
<para>Unpostable Code 148 RC 6– Occurs when a TC 150 with Form 5405 (FTHBC); Section 58 contains an SSN not equal to the primary SSN in Field 01PS.</para>
<subsection4 id="id337100995"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 148 RC 6</title>
<para>CC GTREC the DLN of the document.</para>
<para>Re-validate the document by entering <emphasis type="b">R</emphasis> in field 02RI.</para>
<para>Correct transcription errors and misplaced entries in Section 58/59.</para>
<para>Verify the Primary and Secondary name line and SSN from Section 01.</para>
<para>Ensure the primary taxpayer's SSN is in Section 58, Field 58SSN and the secondary taxpayer's SSN is in Section 59, Field 59SSN. </para>
<para>If a change is made to the primary or secondary taxpayer's SSN, enter "R" in Field 02RI after the change has been made to re-validate the SSN.</para>
<para>If FSC is other than 2 and data has been entered in Section 59; DLSEC Section 59.</para>
<para>Ensure all data present on Form 5405 has been entered into the correct fields/sections. </para>
<para>Follow correction procedures in <citation type="IRM">IRM 3.12.3</citation> EC 128 and EC 328 &amp; EC 329 as appropriate.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100991"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 7</title>
<para>Unpostable Code 148 RC 7 occurs when a TC 150 with Form 5405 (FTHBC); Section 59 contains an SSN not equal to the secondary SSN in Field 01SSN.</para>
<subsection4 id="id337101003"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 148 RC 7</title>
<para>CC GTREC the DLN of the document.</para>
<para>GTSEC 02 and enter <emphasis type="b">R</emphasis> in field 02RI to re-validate the return.</para>
<para>Correct transcription errors and misplaced entries in Sections 58 and 59.</para>
<para>Verify the Primary and Secondary name line and SSN from Section 01.</para>
<para>Ensure the secondary taxpayer's SSN is in Section 59, field 59SSN and the primary's SSN is in Section 58, field 58SSN. </para>
<para>Ensure all data present on Form 5405 has been entered into the correct fields for Section 58/59.</para>
<para>Follow correction procedures in <citation type="IRM">IRM 3.12.2</citation> Section 58/59 and <citation type="IRM">IRM 3.12.3</citation> for Error code as appropriate.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101240"><date>(01-01-2020)</date>
<title>Unpostable Code 148 RC 9</title>
<para>Unpostable Code 148 RC 9 occurs when Form 8941, Section 65 contains SSN that is not equal to the primary or Section 66 contains an SSN that is not equal to the secondary SSN.</para>
<para>If 2 Forms 8941 are filed both SSNs are invalid on Form 8941.</para>
<subsection4 id="id337101228"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 148 RC 9</title>
<para>Correct transcription and misplaced entries on displayed fields.</para>
<para>If AVS is down SSPND 800 and follow local procedures until AVS is functioning properly. </para>
<para>Review Form 1040, Form 8941 and attachments to ensure the primary SSN is entered in field 65SSN correctly.</para>
<para>Review Form 1040, Form 8941 and attachments to ensure the secondary SSN is entered in field 66SSN correctly.</para>
<para>If 2 Forms 8941 are filed, review attachments to ensure the primary and secondary SSNs are entered correctly. The primary will be entered in field 65SSN, and the secondary will be entered in field 66SSN.</para>
<para>Delete Section 65/66 if taxpayer has not used Form 8941.</para>
<para>If unable to determine correct SSN assign Primary SSN in field 65SSN.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101673"><date>(06-09-2025)</date>
<title>Unpostable Code 150 </title>
<para>This condition occurs when the first return is attempting to post to a module containing a tax liability and the received date is more than 3 years before the current 23C date.</para>
<subsection3 id="id337101670"><date>(06-09-2025)</date>
<title>Correction Procedures UPC 150 RC 0</title>
<para>Follow instructions from Statute Unpostables and close the return.</para>
<para>If the remarks state 4th request, void the return.</para>
</subsection3>
<subsection3 id="id337101671"><date>(06-09-2025)</date>
<title>Unpostable Code 150 RC 1</title>
<para>This condition occurs when an amended or duplicate return contains an Assessment Statute Expiration Date or extended RDD less than 60 days after the Assessment 23C date.</para>
<subsection4 id="id337101672"><date>(06-09-2025)</date>
<title>Correction Procedures UPC 150-1</title>
<para>Follow instructions from Statute Unpostables and close the return.</para>
<para>If the remarks state 4th request, void the return.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101197"><date>(01-01-2025)</date>
<title>Unpostable Code 151 </title>
<para>Unpostable Code 151 RC 0 occurs when transactions do not create entities, and no entity is present on Master File.</para>
<subsection3 id="id337101632"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 151 RC 0</title>
<para>Correct transcription and misplaced entries in displayed fields.</para>
<para>Disallow personal exemptions claimed and disallow EIC per remarks from Unpostable unit. Apply appropriate TPNC. If no remarks are notated, return the document to Unpostables for clarification.</para>
<para>If working payments and the taxpayer is not the same as the taxpayer on the valid segment, and a correct TIN cannot be found. Input TC 000 to the invalid side.</para>
<para>If working payments and a correct TIN cannot be found. Use Command code NWDLN to send the payment to Unidentified per remarks from Unpostables.</para>
<para>If working Doc Code 58, follow instructions from Unpostables to forward to Excess Collections, 6800 account using Command code NWDLN per remarks from Unpostables.<note>Complete <citation type="Form">Form 4028</citation> after inputting CC NWDLN per the above instructions and send to accounting with document.</note></para>
</subsection3>
<subsection3 id="id337101633"><date>(01-01-2025)</date>
<title>Unpostable Code 151 RC 1</title>
<para>Unpostable Code 151 RC 1 occurs if the account is not present and the TC 670 input to MFT 29 or current year RPS TC 610s and TC 610s with Doc Codes 19, 70, or 76 input with MFT 30 to the valid segment.</para>
<para>EFTPS payments post with a TIN which contains 0000000002 or an invalid TIN.</para>
<subsection4 id="id337101544"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 151 RC 1</title>
<para>Research using IDRS CC IMFOL <emphasis type="b">Q</emphasis> on the resequencing file by the TIN or payment amounts. Additional information on CC IMFOL Q is available in <citation type="IRM">IRM 2.3.51</citation> Command Code IMFOL.</para>
<para>If you locate the TC 610 payment, input a TC 000 using the valid taxpayer's information to bring the payment off the Re-sequencing file. If necessary, request MFTRA U to establish the account. Do not establish account on the invalid side. Monitor account and once established transfer the payment to the correct taxpayer.</para>
<para>If unable to determine the correct taxpayer's TIN/payment or establish the account, forward to Unidentified.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101634"><date>(01-01-2025)</date>
<title>Unpostable Code 152 </title>
<para>This condition occurs when any other than a long entity TC 150, 430, or 140 is addressing the invalid segment of Master File. </para>
<subsection3 id="id337101553"><date>(01-01-2025)</date>
<title>Unpostable Code 152 RC 0</title>
<para>This condition occurs when any other than a long entity TC 150, 430, or 140 is addressing the invalid segment of Master File. </para>
<subsection4 id="id337101554"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 152 RC 0</title>
<para>Correct coding and transcription errors.</para>
<para>Follow instructions from Unpostables to remove personal exemption, and EIC if claimed.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101537"><date>(01-01-2025)</date>
<title>Unpostable Code 152 RC 1</title>
<para>This condition occurs for transactions that are not covered by UPC 153 addressing the invalid side and is not long Entity.</para>
<subsection4 id="id337101555"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 152 RC 1</title>
<para>Correct coding and transcription errors.</para>
<para>Follow instructions from Unpostables to remove personal exemption and EIC if claiming.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101241"><date>(01-01-2020)</date>
<title>Unpostable Code 153 RC 0</title>
<para>This condition occurs on a name control and TIN mismatch—long entity TC 150, 140, or 430 addressing invalid segment. </para>
<subsection3 id="id337101232"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 153 RC 0</title>
<para>Correct transcription and misplaced entries in displayed fields.</para>
<para>If SSN is incorrect, research return, attachments and IDRS for the correct SSN and update Entity.</para>
<para>Follow instructions provided by Unpostable Unit. If no instructions provided, take return to work lead. The work lead will reach out to the Unpostables work lead for clarification on how to close the case.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101242"><date>(01-01-2020)</date>
<title>Unpostable Code 156 RC 0</title>
<para>This condition occurs when a name control mismatches on the valid segment for TC 150 or 430 (Entity Code 2 or 3) or TC 140. Exceptions occur for TC 150, 140, or 430, Entity Code 1, 4, and 5.</para>
<subsection3 id="id337101234"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 156 RC 0</title>
<para>Correct transcription and misplaced entries in displayed fields.</para>
<para>Follow instructions provided by Entity or Unpostables Unit. Delete exemptions and EIC as documented. </para>
</subsection3>
</subsection2>
<subsection2 id="id337101635"><date>(01-01-2025)</date>
<title>Unpostable Code 157 </title>
<para>This condition occurs when a TC 150 with FSC 5 attempts to post and the controlling name line for two most current preceding tax periods before the year of the input transaction contains FSC 5. </para>
<subsection3 id="id337101557"><date>(01-01-2025)</date>
<title>Correction Procedures 157 RC 0</title>
<para> Research the <emphasis type="b">two tax periods immediately prior to the tax period of the return</emphasis>. If research determines the taxpayer has claimed FSC 5 for more than two years, take the following actions:<bulletlist>
<li>If dependents and/or qualified non-dependents are claimed, change FSC to 4 and send TPNC 104. If no dependents are claimed, change the FSC to 1 and send TPNC 101.</li>
<li>If EC 250 generates and the taxpayer is using the Standard Deduction, assign the appropriate TPNC.</li>
<li>If EC 260 generates, verify the taxpayer's computation of Tentative Tax and enter the correct amount of Tentative Tax in Tentative Tax Verified Field.</li>
<li>Take into account all previous math errors when verifying Tentative Tax. </li>
</bulletlist></para>
</subsection3>
<subsection3 id="id337101559"><date>(01-01-2025)</date>
<title>Unpostable Code 157 RC 2</title>
<para>This condition occurs when a TC 000, TC 01X containing name information, TC 140, 150, or 430 with a joint name line that:<alphalist>
<li>Contains an ampersand (&amp;) and is not followed by a minimum of a blank space, alpha, blank space, alpha.</li>
<li>The &amp; is followed or preceded by blank space, blank space. </li>
<li>The &amp; is part of the last name.</li>
<li>FSC is other than 2 or 7 and the ampersand (&amp;) is included in the name line or the " last name line" is blank.</li>
</alphalist></para>
<subsection4 id="id337101560"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 157 RC 2</title>
<para>Correct transcription and misplaced entries in displayed fields. </para>
<para>Compare the names on the return to the name line Section 01. </para>
<para>Research thoroughly using IDRS CC ENMOD &amp; INOLE to determine the correct name and/or TIN information. </para>
<para>If FSC is other than 2 or 7 and the ampersand is included follow <citation type="IRM">IRM 3.12.2.4.3.12</citation> procedures to correct FSC field. </para>
</subsection4>
</subsection3>
<subsection3 id="id337101561"><date>(01-01-2025)</date>
<title>Unpostable Code 157 RC 3 </title>
<para>Unpostable Code 157 RC 3 occurs when a return contains either an RPC E, a TC000, a TC016, a TC017 that has a temporary spouse SSN (except ITINs) or spouse SSNs with 123-45-6789 or 111-11-1111, 222-22-2222 etc.</para>
<subsection4 id="id337101562"><date>(01-01-2025)</date>
<title>Correction Procedures 157 RC 3</title>
<para>Correct transcription and misplaced entries in displayed fields.</para>
<para>When the return is received from the Unpostable Units with a valid TIN, input the correct SSN in Field 01SS. </para>
<para>When the return is received from the Unpostable Units without a valid TIN, research the documents and attachments for the correct secondary SSN. Research and update per IDRS CC ENMOD, and/or INOLES for a cross reference with the P-SSN for the secondary SSN. If unable to determine the correct secondary SSN, input the following:<bulletlist>
<li>Disallow entry in Field 01SS</li>
<li>Disallow exemption for secondary taxpayer</li>
<li>Remove RPC <emphasis type="q">E</emphasis></li>
<li>Assign TPNC as appropriate</li>
</bulletlist> </para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101200"><date>(06-02-2021)</date>
<title>Unpostable Code 159 RC 0 </title>
<para>This condition occurs when there are invalid Installment Agreement (IA) user fees or payments posted to an account or no existing tax account module.</para>
<subsection3 id="id337101189"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 159 RC 0</title>
<para>Correct transcription and misplaced entries.</para>
<para>Correct Designated Payment Codes (DPC) as directed by the Unpostable unit.</para>
<para>Follow instructions provided by Unpostable units. If no instructions are provided, take return to work lead. Work lead will reach out to the Unpostables work lead for clarification on how to close the case.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101177"><date>(01-01-2020)</date>
<title>Unpostable Code 162 RC 0 </title>
<para>Unpostable Code 162 RC 0 occurs when the displayed taxpayer's Tax Year month is different from the month of the return. </para>
<subsection3 id="id337101170"><date>(01-01-2026)</date>
<title>Correction Procedures UPC 162 RC 0</title>
<para>Correct transcription and misplaced entries in displayed fields.</para>
<para>If Form 4868 is received with incorrect FY, follow the Unpostable units request to change the FY to agree with Master File.</para>
<para>Follow taxpayer’s intent when correcting the Tax Period Ending of the transaction.</para>
<para>If payment transaction is TC 610, 640, 660 or 670 and is intended for a BMF account, renumber to a BMF account.<note>Ensure the payment is directed to correct MFT and/or taxpayer. These payments may be for a module on MFT 55.</note></para>
<para>Follow Unpostable unit request to change the month ending to agree with Master File.</para>
<para>If the date of death is before the beginning of the tax period of the return. If your site processes BMF forward the return to the BMF C&amp;E team, otherwise transship the return to a BMF site for 1041 processing. </para>
<para>If the document is a short period return and the date of death is after the return's ending period, follow Unpostable units request to change month ending on return to agree with Master File. </para>
<para>If the tax year is not a short Period return, ensure the date and form is correct. If it is not correct convert the return to a Short period return.</para>
<para>Follow instructions provided by Unpostable units. If no instructions are provided, take return to work lead. Work lead will reach out to the Unpostables work lead for clarification on how to close the case. </para>
</subsection3>
</subsection2>
<subsection2 id="id337100208"><date>(11-10-2021)</date>
<title>Unpostable Code 164</title>
<para>Unpostable Code 164 is for EITC Recertification Indicators, Killed in Terrorist Actions (KITA), Health Coverage Tax Credit (HCTC), First-Time Homebuyer Credit (FTHBC) and Estimated Payment (ES) credits.</para>
<subsection3 id="id337101178"><date>(01-01-2020)</date>
<title>Unpostable Code 164 RC 0</title>
<para>This condition occurs when an input TC 150 contains a significant withholding amount equal to the sum of ES credits posted. </para>
<subsection4 id="id337101172"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 164 RC 0</title>
<para>Taxpayers may claim both ES credits and withholding credits, verify withholding amount per Form(s) W–2 or substitutes attached. Research to verify withholding using IDRS CC IRPTR, TXMOD and IMFOL, etc. </para>
<para>Verify ES credits using IDRS CC IMFOLT or TXMOD. <note>A TC 670 posted before April 23rd of current year is considered an ES credit.</note></para>
<para>If withholding amount is not verified, or no W–2 or substitutes are attached, correspond with taxpayer using 12C letter for verification of withholding amount.</para>
<para>If No Reply to correspondence and withholding is <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict>delete withholding and follow instructions in <citation type="IRM">IRM 3.12.3.35.2</citation>. </para>
</subsection4>
</subsection3>
<subsection3 id="id337100618"><date>(11-10-2021)</date>
<title>Unpostable Code 164 RC 1</title>
<para>This condition occurs when a TC 150 with a tax period of 199812 and subsequent contains Earned Income Credit (EIC) per computer is input to an account containing the EITC Recertification Indicator in the entity section that is set to the normal or self only setting; if the 2-or-10 year settings of the EITC Recertification Indicator are significant, or if the EITC Recertification Indicator is set to 3.<note>Master File will bypass UPC 164 RC 1 if the TC 150 contains Audit Code U; or if the normal setting only (1 setting) and not the income related setting (8 setting) is significant, and the input return is tax period 200212 or subsequent and does not contain a Schedule EIC. Master File will also bypass UPC 164 RC 1 if the EITC Recertification Indicator is set to 3 and the input tax period is equal or later than the EITC Eligible Tax Period.</note></para>
<para>American Opportunity Tax Credit (AOTC)<alphalist>
<li>AOTC Recertification indicator 1. Unpost UPC 164 RC 1 a Return input to tax year 201612 or later claiming AOTC if the AOTC Recertification indicator is set to 1. Bypass if Audit code 3 is input on the return.</li>
<li>AOTC Recertification indicator 2 or 4. Unpost UPC 164 RC 1 a Return input to a tax year 201612 or later claiming AOTC if the AOTC Recertification indicator is set to 2- or 4 (2/10-year ban). Bypass if the input tax period is equal or later than the AOTC Eligible Tax Period and the return contains Audit Code 3.</li>
<li>AOTC Recertification indicator 30. Unpost UPC 164 RC 1 a Return input to a tax year 201612 or later claiming AOTC if the Recertification indicator is set to 30. Bypass if the input tax period is equal or later than the AOTC Eligible Tax Period.</li>
</alphalist></para>
<para>Additional Child Tax Credit Recertification <alphalist>
<li>ACTC Recertification indicator 1. Unpost UPC 164 RC 1 a Return input to tax year 201612 or later claiming CTC/ACTC if the CTC/ACTC Recertification indicator is set to 1. Bypass if Audit code 2 is input on the return.</li>
<li>ACTC Recertification indicator 2 or 4. Unpost UPC 164 RC 1 a Return input to a tax year 201612 or later claiming CTC/ACTC if the CTC/ACTC Recertification indicator is set to 2 or 4 (2-or-10-year ban). Bypass if the input tax period is equal to or later than the CTC/ACTC Eligible tax period and Audit code 2 is input on the return.</li>
<li>ACTC Recertification indicator 30. Unpost UPC 164 RC 1 a Return input to a tax year 201612 or later claiming CTC/ACTC if the Recertification indicator is set to 30. Bypass if the input tax period is equal or later than the CTC/ACTC Eligible Tax Period.</li>
</alphalist></para>
<subsection4 id="id337100619"><date>(01-01-2026)</date>
<title>Correction Procedures UPC 164 RC 1</title>
<para>If the Earned Income Tax Credit (EITC), Child Tax Credit (CTC), Additional Child Tax Credit (ACTC), Credit for Other Dependents (ODC) or American Opportunity Tax Credit (AOTC) is disallowed due to deficiency procedures, a CP 79 is sent to the taxpayer explaining the disallowance of the credits. The taxpayer will be required to file Form 8862<emphasis type="b"> Information to Claim Certain Credits after Disallowance</emphasis> to recertify the next time they claim the credit. A Recertification Indicator (RI) <emphasis type="b">1</emphasis> will remain on the account until the taxpayer recertifies. IDRS CC ENMOD/IMFOLE will display the recertification indicator if the credits were disallowed through deficiency procedures by Exam. Exam determines if the recertification is no longer required. Each credit is disallowed individually and displayed on IDRS CC ENMOD and CC IMFOLE.</para>
<para>In addition to a recertification requirement, Exam can apply a 2 or 10 year ban on one or more of the credits. The taxpayer is required to recertify for each banned credit to claim it after the ban period expires.</para>
<para>If the taxpayer files a subsequent year’s return claiming EITC with no qualifying child, the taxpayer will not attach Form 8862, if the only reason the EITC was reduced or disallowed in the earlier year was because it was determined that a child listed on Schedule EIC was not the taxpayer’s qualifying child. The EITC will be allowed, and the recertification indicator<emphasis type="b"> IS NOT REMOVED</emphasis>. The taxpayer will be required to recertify for the next year that the taxpayer claims the EITC with a qualifying child.</para>
<para>Review each section of Form 8862, <emphasis type="b">Information to Claim Certain Credits after Disallowance</emphasis> in its entirety before processing UPC 164 RC 1. Review Part I line 2, Part II Section A (EITC), Part III (CTC/ACTC/ODC) and/or Part IV (AOTC) to determine the refundable credit(s) the taxpayer is claiming. Ensure ALL Audit codes and RPCs are input before processing.<note notetype="example">If Audit Code <emphasis type="b">3 and U</emphasis> are required, ensure they are both input before closing the UPC 164 RC 1.</note></para>
<para>Research using IDRS CC ENMOD and CC IMFOLE to locate the EITC, AOTC, and ACTC Recertification Indicators. When the Recertification Indicators are located, use the following instructions: <table frame="all" id="id337100866" summary="Research for EIC Recertification indicators on ENMOD and INOLE" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="col3" colwidth="33*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If the recertification indicator is</emphasis></entry>
<entry valign="top"><emphasis type="b">And the</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis>. </entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"> A) Blank or 0</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="0" rowsep="1">Recertification is not required, allow credit</entry>
</row>
<row>
<entry>B) RI 1 or R1 9 for EIC</entry>
<entry>Taxpayer has a Schedule EIC with qualifying dependents, Schedule EIC with no qualifying dependents, or no Schedule EIC and Form 8862 is not attached</entry>
<entry>Disallow the credit by entering RPC B and transmitting. Assign TPNC 653 when the applicable error code displays.</entry>
</row>
<row>
<entry>C) RI 1 or RI 9 for EIC</entry>
<entry>Taxpayer is claiming EIC and Form 8862 is attached </entry>
<entry>Allow the credit by entering Audit Code U and RPC A.</entry>
</row>
<row>
<entry>D) The document is TY 2002 and later RI 1 or RI 9 for EIC</entry>
<entry>Taxpayer is claiming EIC for self only and Form 8862 is not attached </entry>
<entry>Allow the credit by entering Audit Code U and RPC A.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">E) The document is TY 2015 and later RI 1 or RI 9 for ACTC</entry>
<entry colsep="1" rowsep="1">Taxpayer is claiming CTC/ACTC/ODC with or without Sch 8812 and Form 8862 is not attached</entry>
<entry colsep="0" rowsep="1"><steplist>
<li>Disallow the credit by entering 00 in field 94CEV/DEV<note> TY21 also enter 00 in field 94CEV for children under 6</note> and transmitting. Assign TPNC 653 when the error code redisplays.</li>
<li>Form 1040-SS/SS (sp) assign TPNC 470.</li>
</steplist></entry>
</row>
<row>
<entry colsep="1" rowsep="1">F) The document is TY 2015 and later RI 1 or RI 9 for ACTC</entry>
<entry colsep="1" rowsep="1">Taxpayer is claiming CTC/ACTC and <citation type="Form">Form 8862</citation> is attached</entry>
<entry rowsep="1">Allow the credit by entering Audit Code 2.</entry>
</row>
<row>
<entry>G) The document is TY 2015 and later RI 1 or RI 9 for AOTC</entry>
<entry>Taxpayer is claiming AOTC with <citation type="Form">Form 8863</citation> and <citation type="Form">Form 8862</citation> is not attached</entry>
<entry><steplist>
<li>Disallow the credit for TY17 &amp; prior by entering .01 in field 94AOV/94EDV and transmitting. Assign TPNC 653 when the applicable error code displays.</li>
<li>TY18 and later Enter 00 in field 50ASV and transmitting. Assign TPNC 653 when the error code redisplays.</li>
</steplist></entry>
</row>
<row>
<entry>H) The document is TY 2015 and later R1 or R9 for AOTC</entry>
<entry>Taxpayer is claiming AOTC for self with Form 8863 and Form 8862 is not attached</entry>
<entry>Allow the credit by entering Audit Code 3.</entry>
</row>
<row>
<entry>I) The document is TY 2015 and later RI 1 or RI 9 for AOTC</entry>
<entry>Taxpayer is claiming AOTC with <citation type="Form">Form 8863</citation> and <citation type="Form">Form 8862</citation> is attached</entry>
<entry>Allow the credit by entering Audit Code 3.</entry>
</row>
<row>
<entry>J) RI 2 for EIC</entry>
<entry>Tax year is less than EITC-EL TXPD field and the taxpayer is claiming EIC with qualifying children regardless, of, if Sch EIC and Form 8862 is attached or is not attached </entry>
<entry>Disallow the credit by entering RPC B and transmitting. Assign TPNC 814 when the applicable error code displays.</entry>
</row>
<row>
<entry>K) RI 2 for EIC</entry>
<entry>Tax year is less than EITC-EL-TXPD field and the taxpayer is claiming EIC for self only, regardless, of, if Form 8862 is attached</entry>
<entry>Disallow the credit by entering RPC B and transmitting. Assign TPNC 814 when the applicable error code displays.</entry>
</row>
<row>
<entry>L) RI 2 for EIC</entry>
<entry>Tax year is greater than or equal to EITC-EL-TXPD field, Sch EIC and Form 8862 is attached </entry>
<entry>Allow the credit by entering Audit Code U and RPC A.</entry>
</row>
<row>
<entry>M) RI 2 for EIC</entry>
<entry>Tax year is greater than or equal to EITC-EL-TXPD field, either Sch EIC and/or Form 8862 is not attached</entry>
<entry>Disallow the credit by entering RPC B and transmitting. Assign TPNC 815 when the applicable error code displays.</entry>
</row>
<row>
<entry>N) RI 2 for EIC</entry>
<entry>Tax year is greater than or equal to EITC-EL-TXPD field, taxpayer is claiming EIC for self only and Form 8862 is attached</entry>
<entry>Allow the credit by entering Audit Code U and RPC A.</entry>
</row>
<row>
<entry>O)RI 2 for ACTC</entry>
<entry>Tax year is less than ACTC-ELG-TXPD field, and the taxpayer is claiming CTC/ACTC/ODC with qualifying dependents regardless if Sch 8812 and/or Form 8862 are attached</entry>
<entry><steplist>
<li>Disallow the credit by entering 00 in Field 94CEV/DEV and transmitting. Assign TPNC 820 when the applicable error code displays.</li>
<li>Form 1040-SS/SS(sp) assign TPNC 499. </li>
</steplist></entry>
</row>
<row>
<entry>P) RI 2 for ACTC</entry>
<entry> Tax year is greater than or equal to ACTC-ELG-TXPD field and the taxpayer is claiming CTC/ACTC/ODC with qualifying dependents and/or Sch 8812 and Form 8862 is attached </entry>
<entry>Allow the credit by entering Audit Code 2.</entry>
</row>
<row>
<entry>Q) RI 2 for ACTC</entry>
<entry>Tax year is greater than or equal to ACTC-ELG-TXPD field and the taxpayer is claiming CTC/ACTC with qualifying dependents and Sch 8812 and <citation type="Form">Form 8862</citation> is not attached</entry>
<entry><steplist>
<li>Disallow the credit by entering 00 in Field 94CEV and transmitting. Assign TPNC 819 and TPNC 653 when the applicable error code displays.</li>
<li>Form 1040-SS/SS(sp) assign TPNC 498 and TPNC 470.</li>
</steplist></entry>
</row>
<row>
<entry>R) RI 2 for AOTC</entry>
<entry>Tax year is less than AOTC-ELG-TXPD field, and the taxpayer is claiming AOTC for self or dependents regardless if <citation type="Form">Form 8863</citation> and <citation type="Form">Form 8862</citation> are attached</entry>
<entry><steplist>
<li>Disallow the credit for TY17 and prior by entering .01 in Fields 94AOV/94EDV and transmitting. Assign TPNC 823 when the applicable error code displays. </li>
<li>TY18 and later enter .00 in Field 50ASV and transmitting. Assign TPNC 823 when the applicable error code displays.</li>
</steplist></entry>
</row>
<row>
<entry>S) RI 2 for AOTC</entry>
<entry>Tax year is greater than or equal to AOTC-ELG-TXPD field, <citation type="Form">Form 8863</citation> and <citation type="Form">Form 8862</citation> are attached</entry>
<entry>Allow the credit by entering Audit Code 3.			</entry>
</row>
<row>
<entry>T) RI 2 for AOTC</entry>
<entry>Tax year is greater than or equal to AOTC-ELG-TXPD field and the taxpayer is claiming is AOTC for self/and or dependents and <citation type="Form">Form 8863</citation> and <citation type="Form">Form 8862</citation> are not attached</entry>
<entry><steplist>
<li>Disallow the credit for TY17 and prior by entering .01 in Fields 94AOV/94EDV and transmitting. Assign TPNC 822 when the applicable error code displays.</li>
<li>TY18 and later enter .00 in Field 50ASV and transmitting. Assign TPNC 823 when the applicable error code displays.</li>
</steplist></entry>
</row>
<row>
<entry>U) RI 1 or RI 2 for EIC</entry>
<entry>Tax year is the same as the EITC-ELG-TXPD field and the taxpayer is claiming EIC with qualifying dependents and <citation type="Form">Form 8862</citation> is not attached</entry>
<entry>Disallow credit by entering RPC B and transmitting. Assign TPNC 653 and 815 when the applicable error code displays.</entry>
</row>
<row>
<entry>V) RI 3 for EIC</entry>
<entry>Tax year is greater than or equal to EITC-ELG-TXPD field and Schedule EIC is attached if claimed with qualifying dependents and/or EIC is claimed for self only</entry>
<entry>Allow the credit by entering Audit Code U and RPC A.</entry>
</row>
<row>
<entry>W) RI 3 for EIC</entry>
<entry>Tax year is less than any of the following fields:<bulletlist>
<li>EITC-ELG-TXPD</li>
<li>ACTC-ELG-TXPD</li>
<li>AOTC-ELG-TXPD</li>
</bulletlist></entry>
<entry><steplist>
<li>Disallow EIC credit by entering RPC B and transmitting. Assign TPNC 815 when the applicable error code displays.</li>
<li>Disallow CTC/ACTC/ODC by entering 00 in Field 94CEV and transmitting. Assign TPNC 819 when the applicable error code displays. </li>
<li>Form 1040-SS/SS(sp) assign TPNC 498. </li>
<li>Disallow AOTC for TY17 and prior by entering .01 in Fields 94AOV/94EDV and transmitting. Assign TPNC 822 when the applicable error code displays. </li>
<li>TY18 and later enter .00 in Field 50ASV and transmitting. Assign TPNC 823 when the applicable error code displays.</li>
</steplist></entry>
</row>
<row>
<entry>X) RI 3 for AOTC</entry>
<entry>Tax year is greater than or equal to AOTC-ELG-TXPD field and <citation type="Form">Form 8863</citation> is attached for AOTC claim for self</entry>
<entry>Allow the credit by entering Audit Code 3.</entry>
</row>
<row>
<entry>Y) RI 3 for ACTC</entry>
<entry>Tax year is greater than or equal to ACTC-ELG-TXPD field regardless if Sch 8812 is attached for CTC/ACTC/ODC claim</entry>
<entry>				Allow the credit by entering Audit Code 2.					</entry>
</row>
<row>
<entry>Z) RI 4 for EIC</entry>
<entry>Tax year is less than EITC-ELG-TXPD field and the taxpayer is claiming EIC with qualifying dependents Sch EIC and <citation type="Form">Form 8862</citation> is or/is not attached</entry>
<entry>Disallow the credit by entering RPC B and transmitting. Assign TPNC 816 when the applicable error code displays.</entry>
</row>
<row>
<entry>1) RI 4 for EIC</entry>
<entry>Tax year is greater than or equal to the EITC-EL-TXPD field and taxpayer is claiming EIC with or without qualifying dependents. Recertification is required.</entry>
<entry>If Schedule EIC and Form 8862 are not attached, disallow the credit by entering RPC B and transmitting. Assign TPNC 653 when the applicable error code displays.</entry>
</row>
<row>
<entry>2) RI 4 for ACTC</entry>
<entry>Tax year is greater than or equal to the ACTC-ELG-TXPD field and the taxpayer is claiming CTC/ACTC/ODC with qualifying dependents and/or Sch 8812</entry>
<entry><steplist>
<li>Allow the credit if Form 8862 is attached by entering Audit Code 2.</li>
<li>Disallow the credit If Form 8862 is not attached, by entering 00 in Field 94CEV/DEV and transmitting. Assign TPNC 821 when the applicable error code displays.</li>
</steplist></entry>
</row>
<row>
<entry>3) RI 4 for ACTC</entry>
<entry>Tax year is less than ACTC-ELG-TXPD field, and the taxpayer is claiming CTC/ACTC/ODC with qualifying dependents regardless if Schedule 8812 and/or <citation type="Form">Form 8862</citation> is attached</entry>
<entry>				<steplist>
<li>Disallow CTC/ACTC/ODC by entering 00 in Field 94CEV/DEV and transmitting. Assign TPNC 824 when the applicable error code displays.</li>
<li>Form 1040-SS/SS(sp) assign TPNC 500. </li>
</steplist></entry>
</row>
<row>
<entry>4) RI 4 for ACTC</entry>
<entry>Tax year is greater than or equal to the ACTC-ELG-TXPD field and the taxpayer is claiming CTC/ACTC/ODC with qualifying dependents and/or Sch 8812 and <citation type="Form">Form 8862</citation> is not attached</entry>
<entry>if Schedule 8812 and Form 8862 are not attached disallow credit by entering 00 in Field 94CEV and transmitting. Assign TPNC 653 when the applicable error code displays.</entry>
</row>
<row>
<entry>5) RI 4 for AOTC</entry>
<entry>Tax year is less than the AOTC-ELG-TXPD field and are also greater than the TXPD field and the taxpayer is claiming AOTC regardless if <citation type="Form">Form 8863</citation> or <citation type="Form">Form 8862</citation> is attached</entry>
<entry><steplist>
<li>Disallow AOTC credit for TY17 and prior by entering .01 in Fields 94AOV/94EDV and transmitting. Assign TPNC 824 when the applicable error code displays.</li>
<li>Disallow AOTC credit for TY18 and later by entering .00 in Field 50ASV and transmitting. Assign TPNC 824 when the applicable error code displays.</li>
</steplist></entry>
</row>
<row>
<entry>6)RI 4 for AOTC</entry>
<entry>Tax year is greater than or equal to AOTC-ELG-TXPD field (Recertification is required)</entry>
<entry><steplist>
<li>If Form 8862 and Form 8863 are attached, allow the credit by entering Audit Code 3.</li>
<li> For TY 2017 &amp; prior, If Form 8863 and or Form 8862 are NOT attached enter .01 in Fields 94AOV/94EDV and transmitting. Assign TPNC 653 when the applicable error code displays. </li>
<li>For TY 2018 and later enter .00 in Field 50ASV and transmit. Assign TPNC 823 when the applicable error code displays. </li>
</steplist></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>If the document cannot be located by Files and there is no <emphasis type="b">U</emphasis> in Field 01ADC, close the return by using the table above to disallow the appropriate credit.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100625"><date>(01-01-2025)</date>
<title>Unpostable Code 164 RC 2</title>
<para>Unpostable Code 164 RC 2 occurs when a TC 150, TC 290, or TC 300 is input to an account containing a Killed in Terrorist Action (KITA) or Hostage Indicator (HSTG). </para>
<subsection4 id="id337100626"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 164 RC 2</title>
<para> If the remarks from Unpostable Unit states <emphasis type="b">HSTG</emphasis> or <emphasis type="b">KITA</emphasis> follow instructions below. If IDRS command codes ENMOD, SUMRY or TXMOD displays <emphasis type="b">HSTG</emphasis> or <emphasis type="b">KITA</emphasis> RJECT 640 document to void the DLN. Mail the case along with all supporting documentation (tax forms, taxpayer correspondence, etc.) after cancellation of the DLN to the following address:<alphalist>
<li>For <emphasis type="b">Hostage Indicators</emphasis> only - Internal Revenue Service Hostage Indicator, 2385 Chamblee Tucker Road STOP 74 / Team 107, Chamblee GA 30341. <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> for clarity or questions on Hostage Indicators. </li>
<li>For <emphasis type="b">KITA Indicators</emphasis> only - Internal Revenue Service KITA Indicator Accounts Management, 333 W. Pershing Road, Kansas City, MO 64108. <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> for clarity or questions on KITA Indicators.</li>
</alphalist></para>
</subsection4>
</subsection3>
<subsection3 id="id337101661"><date>(01-01-2026)</date>
<title>Unpostable Code 164 RC 5</title>
<para>Unpostable Condition 164 RC 5 occurs when a return claiming the Health Care Coverage Tax Credit (HCTC) does not have the HCTC indicator set.</para>
<subsection4 id="id337101654"><date>(06-09-2025)</date>
<title>Correction Procedures UPC 164 RC 5</title>
<para>Correct transcription errors, misplaced entries and verify the taxpayer is claiming HCTC.</para>
<para>For HCTC TY 2015 and later follow instructions in <citation type="IRM">IRM 3.12.3.31.11.6.2</citation> Error Code 358 AC 450 HCTC.</para>
<para>If correspondence has not been issued and documentation for the credit is not present, correspond following instructions in EC 358.<note>If MeF correspondence is needed for EC 358, ensure the <emphasis type="b">20-day</emphasis> suspense period has expired.</note></para>
<para>For TY 2015 and later, follow instructions in EC 358. Enter Audit Code J in Field 01ACD. Enter amount in Field 05OTH and enter H in Field 05TYP.</para>
<para>For TY 2013 and prior, follow instructions in EC 358. Enter the amount in Field 05OTH and enter H in Field 05TYP.</para>
<para>If the taxpayer is filing an International return (Form 1040-SS) and they are not eligible to claim the HCTC credit send TPNC 377 to advise the taxpayer that they are not eligible to claim the HCTC credit.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101662"><date>(01-31-2025)</date>
<title>Unpostable 164 RC 6</title>
<para>This condition will occur when the return breaks the FTHBC rule. <note>Masterfile will bypass for a corrected UPC 164 RC 6 or if the FTHBC amount is equal to zero.</note></para>
<para>This Unpostable code is valid for TY 2008 - TY 2011 only.</para>
<para>Occurs when the First-Time Home Buyer Credit (FTHBC) is present with TC 150 FTHBC computer is significant and either primary or secondary or (both) FTHBC are on the DMF file, or</para>
<para>TC 150 input at the same time as a TC 971 AC 137, taxpayer has previously claimed First-Time Home Buyer Credit, or</para>
<para>Taxpayer has owned another main home during the <emphasis type="b">3-year</emphasis> period ending on the purchase date.</para>
<subsection4 id="id337101656"><date>(01-31-2025)</date>
<title>Correction Procedures UPC 164 RC 6</title>
<para>Correct coding, transcription errors and misplaced entries in displayed fields. The Unpostable code is valid for TY 2008 - TY 2011.</para>
<para>If the taxpayer indicates they are <emphasis type="b">First time home buyer</emphasis> by checking the 1st box on line 3, Form 5405 or the amount present on line 3 Form 5405 is not equal to $6500, delete all Special Processing Codes related to First-Time Home Buyer Credit if present and assign appropriate TPNC.</para>
<para>If the taxpayer indicates they are <emphasis type="b">Long Time Resident</emphasis> by checking the 2nd box on line 3, Form 5405 or $6,500 is present on line 3, Form 5405 follow instructions in <citation type="IRM">IRM 3.12.3</citation> for First Time Home Buyer instructions. (TY 2008 - TY 2011 ONLY)</para>
</subsection4>
</subsection3>
<subsection3 id="id337101663"><date>(01-31-2025)</date>
<title>Unpostable Code 164 RC 8</title>
<para>Unpostable 164 RC 8 occurs when TC 150 with First Time Home Buyer Credit (FTHBC) per Computer (section 4) is significant and either primary or secondary or (both) taxpayers FTHBC are on the DMF file.</para>
<subsection4 id="id337101658"><date>(01-31-2025)</date>
<title>Correction Procedures UPC 164 RC 8</title>
<para>This error occurs when the taxpayer, according to our records, has already received the credit.</para>
<para>CC GTREC the DLN.</para>
<para>Re-validate the document by entering <emphasis type="b">R</emphasis> in Field 02RI.</para>
<para>Correct coding, transcription errors and misplaced entries in displayed fields.</para>
<para>Research using CC IMFOL, TXMOD, and/or RTVUE to determine if a TC 150 has posted.</para>
<para>If research determines the return is a duplicate or an amended return, follow procedures for both.</para>
<para>If FSC 3 and taxpayer is splitting FTHBC with spouse, and research shows primary taxpayer has not received credit, delete fields 01SNC and 01SS, See. EC 366.</para>
<para>If instructions in 2 through 7 (above) do not apply, GTSEC 01 and delete all FTHBC codes in field 01SPC. If EC 366 appears, assign applicable TPNC.</para>
<para>If the first box is checked on line 3 (Form 5404 TY 2011 and earlier), or the amount present on line 3 (Form 5405 TY 2011 and earlier) is $6,500, then assign <emphasis type="b">TPNC 636</emphasis>.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101664"><date>(01-31-2025)</date>
<title>Unpostable Code 164 RC 9</title>
<para>This condition occurs when IRC 1341 amount is significant and:<alphalist>
<li>The module contains a posted TC 971 AC 137 with MISC 1341C or</li>
<li>The IRC 1341C indicator is set on the tax return.</li>
</alphalist></para>
<subsection4 id="id337101660"><date>(06-09-2025)</date>
<title>Correction Procedures UPC 164 RC 9</title>
<para>If the IRC 1341 credit amount reported on Schedule 3 matches the taxpayers refund amount, remove the IRC 1341 credit and assign TPNC 845.</para>
<para>If the IRC 1341 amount reported on Schedule 3 is more than the taxpayers refund amount, remove the IRC 1341 credit amount up to the refund amount and assign TPNC 845.<note notetype="example">IRC 1341 credit amount is $14,900.00 and the taxpayers refund amount is $3,500.00, remove only $3,500.00 of the IRC 1341 credit.</note></para>
<para>If the IRC 1341 amount reported on Schedule 3 is less than the taxpayers refund amount, remove the entire amount of IRC 1341 and assign TPNC 845.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101637"><date>(01-01-2025)</date>
<title>Unpostable Code 166 RC 0</title>
<para>This condition occurs when there is a Filing Status code mismatch (TC 150, Entity code 2 or 3).</para>
<subsection3 id="id337101607"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 166 RC 0</title>
<para>Correct filing status and entity information per Unpostables instructions.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100620"><date>(01-01-2020)</date>
<title>Unpostable Code 167 RC 2</title>
<para>Unpostable Condition 167 RC 2 occurs when the pre-journalized amount is not equal to zero or a TC 270 is input as the secondary transaction to a Revenue Receipt and the module contains an unreversed TC 320.</para>
<subsection3 id="id337100621"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 167 RC 2</title>
<para>If the pre-journalized amount is not equal to zero, re-input the transaction after removing the TC 570 for zero (00), by either: <alphalist>
<li>Re-inputting the document.</li>
<li>Routing a copy of the corrected document to Service Center Collection Branch (SCCB), explaining the unpostable condition and action taken to resolve it.</li>
</alphalist><note notetype="note">Send a copy to the originator, informing them of the action taken.</note></para>
</subsection3>
</subsection2>
<subsection2 id="id337101201"><date>(01-01-2020)</date>
<title>Unpostable Code 168 RC 0 </title>
<para>Unpostable Condition 168 RC 0 occurs if TC 892 is addressing the correct module.</para>
<para>It also occurs if correct account is being addressed and a TC 896 with the correct money is posted.</para>
<subsection3 id="id337101191"><date>(11-07-2023)</date>
<title>Correction Procedures UPC 168 RC 0</title>
<para>Correct the tax period and/or SSN is of the module.</para>
<para>Correct the account being addressed and the TC 896 with the correct money. </para>
<para>If TC 892, determine if TC is addressing the correct module. Determine if tax period and/or SSN is correct. </para>
<para>Review spousal indicators and change spousal indicators to agree with Master File. <note>The valid spousal indicators are:</note><alphalist>
<li><emphasis><emphasis type="b">0</emphasis></emphasis> (<emphasis type="b">non-joint taxpayer</emphasis> systemically generated) </li>
<li><emphasis><emphasis type="b">1</emphasis></emphasis>(<emphasis type="b">joint-filer primary taxpayer</emphasis>)</li>
<li><emphasis><emphasis type="b">2</emphasis></emphasis> (<emphasis type="b">joint-filer secondary taxpayer</emphasis>)</li>
</alphalist></para>
<para>If Doc Code 51 is present change Doc Code and correct transaction code according to instructions from Unpostable Units.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101035"><date>(01-01-2020)</date>
<title>Unpostable Code 169 RC 9</title>
<para>Unpostable Code 169 RC 9 occurs when a TC 150 attempts to post to a MFT 30 with FSC 2 (including dummy IRA) containing an IRA Form 5329 (Section 29 or 30) and any of the following conditions are met:<alphalist>
<li>Does not contain a spouse indicator, contains a spouse indicator greater than 02 or contains a section 29 or 30 with spouse indicators of equal value. </li>
<li>Contains a spouse indicator of 02 and the Secondary SSN in the controlling name line is missing or invalid. </li>
</alphalist></para>
<subsection3 id="id337101034"><date>(04-25-2022)</date>
<title>Correction Procedures UPC 169 RC 9</title>
<para>Correct coding, transcription, and misplaced entries on displayed fields.</para>
<para>Ensure field 29ISI IRA Spouse Indicator is correct. If the FSC 2, Form 5329 is for the<emphasis type="b"> Primary taxpayer, the code will be 1</emphasis>. If the FSC 2 Form 5329 is for the <emphasis type="b">Secondary taxpayer, the Code will be 2</emphasis>. If the FSC is other than 2, delete the code from Field 29ISI.</para>
<para>Follow instructions from Unpostable unit. Research all documents to ensure the correct SSN is provided by the Unpostable Unit. The Secondary SSN must be corrected on the document and the screen. If unable to determine the correct Secondary SSN, SSPND 211 to obtain the correct Secondary SSN from the Primary Taxpayer. Follow No Reply procedures if no response is received.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101506"><date>(01-01-2023)</date>
<title>Unpostable Code 176 RC 0</title>
<para>Unpostable Condition 176 RC 0 occurs when TC 150 or 430 which would create an entity on the invalid segment of Master File and no account is present. This condition is bypassed by:<alphalist>
<li>Corrected UPC cases.</li>
<li>TC 150 or TC 430 with high order digit in SSN of 9 (temporary SSN).</li>
<li>TC 430 for Form 1040C (Doc. Code 61).</li>
<li>TC 150 with CCC X.</li>
<li>TC 150 or 430 with the Accretion Indicator<note>Dual, hyphenated, or alternated-dual surnames are sometimes transcribed incorrectly. Make every effort to follow taxpayer's intent. If the taxpayer's signature contains one last name, or a dual name is hyphenated, post the document to that name control. Input TC 013 or TC 000 if needed.</note></li>
</alphalist></para>
<subsection3 id="id337101436"><date>(06-12-2023)</date>
<title> Correction Procedures UPC 176 RC 0</title>
<para>Correct coding, transcription and misplaced entries on displayed fields.</para>
<para>Follow instructions given by Unpostable Unit to correct SSN on Form 1040 Schedule SE and other forms and schedules.</para>
<para>If further research is required, search the return, attachments and Form W2. Use IDRS CC NAMEI, NAMES, INOLE, to find valid SSN. If no SSN provided, return to Unpostable Unit.</para>
<para>Edit new SSN on all fields and documents to correct unpostable condition.</para>
<para>Leave a working trail if TC 013 or TC 000 is input.</para>
<para>Follow instructions given by Unpostable Unit. Disallow personal exemptions, IRSN and EIC as requested. GTSEC 01 and disallow exemptions as appropriate as well as input RPC B to disallow EIC if claimed. Assign correct TPNC as necessary for EIC and exemptions. GTSEC 17 and 18 and enter correct SSN as given by the Unpostable Unit for Schedule SE and other forms and schedules.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101507"><date>(01-01-2023)</date>
<title>Unpostable Code 177 RC 0</title>
<para>This condition occurs when a module creating transactions attempts to post to an account on the valid segment with the Scrambled SSN Indicator set to 01, 10, 12 or 20 if the MFR is set to 08. All transactions except TC 01X with a significant Scrambled SSN value or TC 020 if the Scrambled SSN Indicator is set to 13 or 23. </para>
<subsection3 id="id337101438"><date>(01-01-2023)</date>
<title>Correction Procedures 177 RC 0</title>
<para>Do not research SSNs or TINs.</para>
<para>Follow instructions provided by the Entity Unpostable Units.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101508"><date>(01-01-2023)</date>
<title>Unpostable Code 182 RC 0</title>
<para>This condition occurs when a module creating transaction except TC 140; TC 500 cc 52, 54, or 56; or TC 971 AC 100–106 input to MFT 31, attempts to post to an account with MFR 8.</para>
<subsection3 id="id337101440"><date>(01-01-2023)</date>
<title>Correction Procedures 182 RC 0</title>
<para>Follow instructions provided by Entity and the Unpostable unit.</para>
<para>Ensure IRSN has been assigned.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101509"><date>(01-01-2023)</date>
<title>Unpostable Code 183 RC 0</title>
<para>Cases are Scheme development cases from IDT unit.</para>
<subsection3 id="id337101442"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 183 RC 0</title>
<para>Follow instructions provided by Entity and the Unpostable unit. If no instructions provided return to Entity/Unpostable units for clarification.</para>
<para>Update IRSN (IRSN 9XX-XX-XXXX*) as provided in Remarks section of Form 8749 or local transfer. </para>
<para>Remove personal exemption for the primary taxpayer (TY2017 and prior), remove EIC, and input CCC <emphasis type="b">3</emphasis> to freeze any possible refund.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101510"><date>(01-01-2023)</date>
<title>Unpostable Code 186 RC 1</title>
<para>This condition occurs if module balance is credit and any TC (except TC 400), attempts to post to a tax module with a transaction section exceeding maximum programming size.<note>A TC 820 will post if, after posting of the TC 820, the module balance becomes zero or debit.</note></para>
<subsection3 id="id337101444"><date>(11-07-2023)</date>
<title>Correction Procedures UPC 186 RC 1</title>
<para>Follow instructions provided by the Unpostable unit. If no instructions provided return to the Unpostable unit for clarification.</para>
<para>If TC 400 is on module and there is a payment or payment reversal TC, research CC XSINQ, SUMRY for correct module.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101511"><date>(01-01-2023)</date>
<title>Unpostable Code 188 RC 0</title>
<para>This condition occurs when a module creating transactions not containing name line information addresses a period earlier than earliest name line on Master File, except TC 140, Entity Code 2. <note>Master File will bypass this check for the following:</note><alphalist>
<li>TC 971 AC 010</li>
<li>RPS TC 610s</li>
<li>TC 610 with Doc Code 19, 70, or 76 that are input to a module one year prior to the earliest tax module on the Master File.</li>
<li>all DOD TC 500s regardless of the name line comparison</li>
<li>any transaction input to MFT 29, 31 or 55</li>
</alphalist></para>
<subsection3 id="id337101446"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 188 RC 0</title>
<para>Verify transaction is input to correct taxpayer's account.</para>
<para>Ensure all tax data is entered correctly. Verify name, address, SSN, TXPD, AGI, Credits, Total Tax and Balance Due/Refund is entered correctly before processing return.</para>
<para>Form 3413 Doc Code 52— Renumber with Doc Code 51 following instructions from the Unpostable units.</para>
<para>Form 3413 Doc Code 52— Renumber to 200–299 Blocking series per Unpostable instructions.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101638"><date>(01-01-2025)</date>
<title>Unpostable Code 189</title>
<para>Unpostable Code 189 RC 0 occurs if Form 3552, TC amount or date, incorrect money amounts, transaction dates, and installment agreement user fees are in error.</para>
<subsection3 id="id337101564"><date>(01-01-2025)</date>
<title>Unpostable Code 189 RC 0</title>
<para>Unpostable Code 189 RC 0 occurs if Form 3552, TC amount or date, incorrect money amounts, transaction dates, and installment agreement user fees are in error.</para>
<subsection4 id="id337101565"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 189 RC 0</title>
<para><emphasis type="b"><citation type="Form">Form 3552 Prompt Assessment Billing Assembly</citation></emphasis> Research <citation type="Form">Form 3552</citation> for correct money amount. Verify correct MFT, TXPD, Assessment Date and Transaction Code (TC). If the amount is located, contact initiator of the document and explain the condition. If money amount is correct but the date and/or TC is wrong, change date and/or TC using Action Code 6 on the register.</para>
<para><emphasis type="b">TC 892</emphasis> If TC 892 with the correct money is posted, correct Spousal indicator to agree with Master File.<note>Valid Spouse Indicators are:</note><alphalist>
<li>0 (non-joint taxpayer)</li>
<li>1 (joint filer-primary taxpayer)</li>
<li>2 (joint filer-secondary taxpayer)</li>
</alphalist></para>
<para>Review IDRS CC TXMOD for the correct tax period. Ensure the Unpostable amount and the TC 896 amount match using IDRS CC TXMOD. If the amount is less than the Unpostable amount, follow instructions from Unpostables. If the amount is greater than the Unpostable amount notify the originator for correction. If no instructions are provided, take return to work lead. Work lead will reach out to the Unpostables work lead for clarification on how to close the case.<note><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></note></para>
</subsection4>
</subsection3>
<subsection3 id="id337101566"><date>(01-01-2025)</date>
<title>Unpostable Code 189 RC 7</title>
<para>Unpostable Code 189 RC 7 occurs if a TC 150 of the SSN from Section 59 (Secondary Form 5405) is not equal to the posted spouse First Time Home Buyer Credit SSN in the Entity and the spouse First Time Home Buyer Credit FSC is equal to 2.</para>
<subsection4 id="id337101567"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 189 RC 7</title>
<para>GTREC the DLN.</para>
<para>Re-validate the document by entering <emphasis type="b">R</emphasis> in Field 02RI.</para>
<para>Section 59 information is for the spouse. Research form 5405 and Section 01 field 01SS for the correct spouse SSN.</para>
<para>Ensure the correct spouse SSN is input in Field 59SSN.</para>
<para>If the taxpayer’s return is not FSC 2 and Form 5405 is not needed DLSEC 59.</para>
<para>Refer to <citation type="IRM">IRM 3.12.3.28.6</citation> EC 329 for further processing instructions.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101568"><date>(01-01-2025)</date>
<title>Unpostable Code 189 RC 9</title>
<para>This condition occurs for a TC 150 <emphasis type="b">not</emphasis> containing Form 5405 (Section 58 or 59), but the entity contains a First Time Homebuyer section with purchase year 2008.</para>
<para>A payment of the First-Time Homebuyer Credit may come back to ERS with Unpostable Code 189, Reason Code 9. Procedures for processing these Unpostable returns are shown below. Some common reasons for the unpostable payment are shown below:<alphalist>
<li>The repayment has to be divided between the primary and secondary taxpayers.</li>
<li>The taxpayer is reporting a disposition, and it has to be applied to the secondary taxpayer too.</li>
<li>The taxpayer has died and is no longer required to pay back the credit, but the programming still requires a payment.</li>
<li>The primary TIN is input into section 59 and the secondary TIN is input into section 58.</li>
</alphalist></para>
<subsection4 id="id337101569"><date>(01-01-2026)</date>
<title>Correction Procedures UPC 189 RC 9</title>
<para><citation type="Form">Form </citation>1040, underpayment or overpayment of First-Time Homebuyer Credit. The repayment on Schedule 2, line 10 is less or more than the sum of Fields PNRI&gt; and SNRI&gt;,<alphalist>
<li>Stop, do not clear the return.</li>
<li>Enter R in Field 02RI and drop to the bottom and transmit.</li>
<li>If the taxpayers are reporting a payment on Schedule 2, line 10, compare the money amounts in Fields PNRI&gt; and SNRI&gt; to the amount the taxpayer is reporting.</li>
<li>If only the primary taxpayer is required to make a payment, GTSEC 58 and verify the primary taxpayers SSN is in Field 58SSN, there is an I in Field 5803, and the payment amount on Schedule 2, line 10 is in Field 5808.</li>
<li>If only the secondary taxpayer is required to make a payment, GTSEC 59 and verify the secondary taxpayers SSN is in Field 59SSN, there is an I in Field 5903, and the payment amount reported on Schedule 2, line 10 is in Field 5908.</li>
<li>If both taxpayers are required to make a payment, GTSEC 58 and enter the primary taxpayer information, then GTSEC 59 and enter the secondary taxpayer’s information per the instructions above, then enter one-half the payment amount in Fields 5808 and 5809.</li>
</alphalist></para>
<para>IF the taxpayers are not reporting a payment on Schedule 2, line 10 and there is a money amount in either Field PNRI&gt; or SNRI&gt; follow the instructions below:<alphalist>
<li>Stop, do not clear the return.</li>
<li>Enter R in Field 02RI and drop to the bottom and transmit.</li>
<li>GTSEC 58 and enter the primary taxpayers TIN in Field 58SSN, enter an I in Field 5803, and enter the amount in Field PNRI&gt; in Field 5808 and transmit.</li>
<li>If the return is married filing joint and the secondary taxpayer owes a payment. GTSEC 59 and enter secondary SSN in Field 59SSN, enter I in Field 5903, and enter the amount in Field SNRI&gt; in Field 5908.</li>
<li>If both taxpayers are required to make a payment, ensure both Section 58 and 59 contain the correct taxpayer information, enter I in Field 58/5903, and input the money amount listed in Field PNRI&gt; and SNRI&gt; in Fields 58/5908.</li>
<li>Enter C in the clear field.</li>
</alphalist></para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101639"><date>(01-01-2025)</date>
<title>Unpostable Code 194 </title>
<para>This condition occurs when an input transaction is attempting to post to a module and the date does not match the transaction reversal. </para>
<subsection3 id="id337101571"><date>(01-01-2025)</date>
<title>Unpostable Code 194 RC 0</title>
<para>This condition occurs when an input transaction is attempting to post to a module and the date does not match the transaction reversal. </para>
<subsection4 id="id337101572"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 194 RC 0</title>
<para>Research <emphasis type="b">Form 3552, Prompt Assessment Billing Assembly</emphasis> for correct dates. Verify correct MFT, TXPD, Assessment Date and Transaction Code (TC). If the amount is located, contact initiator of document and explain the condition. If money amount is correct but date and/or TC is wrong, change date and/or TC using Action Code 6 on the register.</para>
<para>If unable to determine correct date or amount, contact originator.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101573"><date>(01-01-2025)</date>
<title>Unpostable Code 194 RC 1</title>
<para>This condition occurs when reversal transaction money amounts exceed the original transaction code money amount.</para>
<subsection4 id="id337101574"><date>(01-01-2026)</date>
<title>Correction Procedures UPC 194 RC 1</title>
<para>If Form 3552 has incorrect dates, money amounts or transaction codes, correct according to the Form 3552. If unable to determine the correct dates, money amounts or transaction codes, contact the originator.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101640"><date>(01-01-2025)</date>
<title>Unpostable Code 195</title>
<para>This condition occurs when the <emphasis type="b">FSC is other than 2</emphasis> and Section 59 is present.</para>
<subsection3 id="id337101576"><date>(01-01-2025)</date>
<title>Correction Procedures 195 RC 1</title>
<para>CC GTREC the DLN of the document.</para>
<para>To ensure programming is correct, drop to the bottom and transmit.</para>
<para>GTSEC 01 and verify the taxpayer’s primary and secondary SSN.</para>
<para>If Section 59 is entered and the filing status is not FSC 2, delete section 59. Section 59 is for the secondary taxpayer only.</para>
<para>If Form 5405 is required; GTSEC 58 and enter the correct data in the appropriate fields.</para>
<para>Verify that the taxpayer’s SSN is entered correctly in field 58SSN before transmitting.</para>
</subsection3>
<subsection3 id="id337101578"><date>(01-01-2025)</date>
<title>Unpostable Code 195 RC 2</title>
<para>Unpostable Code 195 RC 2 occurs when the Primary/Secondary NAP FTHBC amount is not equal to zeros. If Form 5405, Section 58/59 is present, and the Disposition code is equal to ‘I’ and the <emphasis type="b">repayment-per-computer is less than</emphasis> the Primary/Secondary NAP FTHBC Installment amount.</para>
<subsection4 id="id337101579"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 195 RC 2</title>
<para>GTREC the DLN of the document.</para>
<para>Verify from the return that sections 58/59 have been transcribed correctly. Correct coding and transcription errors.</para>
<para>Remove the Disposition Code <emphasis type="b">I</emphasis> in field 5803. This action will generate the correct error code.</para>
<para>If the Disposition Code is necessary, re-enter as appropriate when the correct error code generates.</para>
<para>When Error Code 329 (Form 5405 attached) or Error Code 334 (No Form 5405) generates, follow instructions in <citation type="IRM">IRM 3.12.3</citation> as appropriate.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101641"><date>(01-01-2025)</date>
<title>Unpostable Code 197</title>
<para>Unpostable Condition 197 RC 4, 5,6 and 7 will be auto closed by GUF to Rejects when the MFT is 29.</para>
<subsection3 id="id337101581"><date>(01-01-2025)</date>
<title>Correction Procedures 197 RC 4</title>
<para>To resolve this condition, change TC 150 to TC 290.</para>
<para>Re-input the document Form 3893 Re-entry document control per Unpostable Unit instructions.</para>
<para>If MFT 29, cancel DLN and route to files.</para>
</subsection3>
<subsection3 id="id337101583"><date>(01-01-2025)</date>
<title>Unpostable Code 197 RC 5</title>
<para>Unpostable Condition 197 RC 5 occurs when a TC 400 or TC 971 AC 145 is input to a credit balance module, or the module does not contain a TC 150.</para>
<subsection4 id="id337101584"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 197 RC 5</title>
<para>Research IDRS command code TXMOD to determine the originator.</para>
<para>Cancel the DLN and route the document to Accounting with remarks to input <emphasis type="b">TC 402 and input TC 972 AC 145</emphasis>.</para>
<para>Do not send document to ANMF or MF.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101585"><date>(01-01-2025)</date>
<title>Unpostable Code 197 RC 7</title>
<para>Unpostable Condition 197 RC 7 occurs for the following reasons:<alphalist>
<li>When a TC 400 (Transfer Out) amount is not equal to zero or attempts to post to a module without a TC 150 or a module is in credit balance. </li>
<li>When a TC 370 with a secondary TC 402 does not find an unreversed TC 400 for the same date and amount. </li>
<li>When a TC 370 with a secondary TC 402 attempts to post to a module that is not in Status 29. </li>
</alphalist></para>
<subsection4 id="id337101586"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 197 RC 7</title>
<para>Verify using TXMOD the correct transaction date and amount. </para>
<para>If date or amount is mismatch and unable to determine the correct date or amount, cancel the DLN and send to Accounting</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101642"><date>(01-01-2025)</date>
<title>Unpostable Code 198 </title>
<para>UPC 198 RC 2 occurs when a TC 430, 610 (Doc Codes 19, 70 or 76) 660, 670 or 760 attempts to post to a settled module.</para>
<subsection3 id="id337101588"><date>(01-01-2025)</date>
<title>Unpostable Code 198 RC 2</title>
<para>UPC 198 RC 2 occurs when a TC 430, 610 (Doc Codes 19, 70 or 76) 660, 670 or 760 attempts to post to a settled module.</para>
<subsection4 id="id337101589"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 198 RC 2</title>
<para>Correct any transcription errors or misplaced amounts.</para>
<para>Verify payment, date, Transaction code, DPC and amount using IDRS command codes IMFOLT, TXMODA, ENMOD, BMFOLI.</para>
<para>If a TC 670 contains DPC 36. Remove DPC code per Unpostables instructions.</para>
<para>If the TC is a 670 and the taxpayer has a balance due on MFT 35, and DPC 36 <emphasis type="b">is not</emphasis> present, add DPC 36.</para>
<para>If payment belongs to a different Master File (e.g., BMF) and/or different MFT, renumber payment to correct Master File and/or MFT.</para>
<para>If payment is TC 430 or 660 or module contains a TC 836, post to current processing year.</para>
<para>If the module contains an <emphasis><emphasis type="b">L</emphasis></emphasis> Freeze, change the TC 670 to TC 640.</para>
<para>If research indicates that the TC 610 or the TC 670 payment must be processed as a quarterly estimated tax payment, correct the tax period and change the Transaction Code to TC 660.</para>
<para>If TC 760 and module contains payment for like amount, follow Unpostable instructions and route to Accounting. </para>
<para>If unable to determine where payment is to post send payment to Unidentified using CC NWDLN. Send to accounting with <citation type="Form">Form 4028</citation>.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101643"><date>(01-01-2025)</date>
<title>Unpostable Code 290</title>
<para>This condition occurs when any TC is not valid for IMF processing and includes the following:<alphalist>
<li>060, 95X, 05X, 07X, 080 (campus generated), 081, 473, 41X, 422, 423, 564, 772, 940, 942, 962; or</li>
<li>If transactions input to MFT 35 including transactions that are secondary to TC 290, TC 300 and TC 370 or revenue receipt.</li>
<li>Revenue Receipt transaction with reversal digit not 0/1/2/4.</li>
</alphalist></para>
<subsection3 id="id337101593"><date>(01-01-2025)</date>
<title>Unpostable Code 290 RC 2</title>
<para>This condition occurs when any TC is not valid for IMF processing and includes the following:<alphalist>
<li>060, 95X, 05X, 07X, 080 (campus generated), 081, 473, 41X, 422, 423, 564, 772, 940, 942, 962; or</li>
<li>If transactions input to MFT 35 including transactions that are secondary to TC 290, TC 300 and TC 370 or revenue receipt.</li>
<li>Revenue Receipt transaction with reversal digit not 0/1/2/4.</li>
</alphalist></para>
<subsection4 id="id337101594"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 290 RC 2</title>
<para>Correct transcription or misplaced entries</para>
<para>Follow instructions provided by Unpostable unit for the correct transaction code</para>
<para>If unable to determine correct transaction code, cancel DLN with CC RJECT 630 and send document with <citation type="Form">Form 4028</citation> to Accounting with remarks stating unable to locate correct transaction code.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101597"><date>(01-01-2025)</date>
<title>Unpostable Code 290 RC 4</title>
<para>This condition occurs for the following:<alphalist>
<li>Tax period invalid</li>
<li>If TC 290, 300, 861/862, 901–904, 971, and 972 with a tax period more than two years later than the 23C date month and year.</li>
<li>Reference numbers 865-869/262 and PRN 692 input for tax period other than 201412.</li>
<li>If TC 740/841 contains an invalid tax period. </li>
<li>MFT 35 posted to tax period prior to 201412.</li>
</alphalist></para>
<subsection4 id="id337101598"><date>(01-01-2025)</date>
<title>Correction Procedures Unpostable Code 290 RC 4</title>
<para>Correct transcription and misplaced entries.</para>
<para>The tax period is in the format YYYYMM. The current period is never transcribed for current-year returns. It is transcribed for prior- and fiscal-year returns.</para>
<para>Review the document and attachments to determine correct tax period.</para>
<para>If TC 290, 300, 901-904, 971 and 972 with a tax period more than two years verify correct tax period and update as appropriate. Allow credit reference numbers 861/862 for tax period 201312 and later only.</para>
<para>If TC 740/841 research for better address to determine correct mailing of refund check. Update IDRS using INCHG to correct address. Correcting the address will send the refund to the correct address (TC 018).</para>
<para>Allow credit reference numbers 865-869/262 and PRN 692 for tax period 201412 and subsequent.</para>
<para>If MFT 35 post to tax period prior to 201412, research for correct MFT. If unable to determine correct MFT, RJECT 640 and send to originator.</para>
<para>If unable to determine the correct Reference number, PRN, or tax period, RJECT 640 and send return to files.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101601"><date>(01-01-2025)</date>
<title>Unpostable Code 290 RC 6</title>
<para>This condition occurs for the following reasons:<alphalist>
<li>A Form 1040 with Computer Condition Code (CCC) <emphasis type="b">S</emphasis> and there is a remittance with the return.</li>
<li>A non-Math error TC 150 (except G or Y coded) contains a zero liability and either a remittance greater than $1 or a CCC <emphasis type="b">S</emphasis> is present. <note>Master File with bypass this condition if the balance due per taxpayer is zero or a credit. </note></li>
<li>If a TC 610 has a return Doc Code in the DLN and control date is other than 401-766.</li>
</alphalist></para>
<subsection4 id="id337101602"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 290 RC 6</title>
<para>Correct all Coding and Transcription errors.</para>
<para><emphasis type="b">TY20 only</emphasis>, if there is an entry in Field 05202, delete the amount. If a subsequent math error displays because of this tax change, assign <emphasis type="b">TPNC 796</emphasis>.</para>
<para>If the payment matches an income or loss amount on the return, enter the payment amount in Section 03, Field 03BDR. </para>
<para>If the payment matches the tax before credit amounts on the return:<alphalist>
<li>Enter the payment in Section 03 (Field 03TAX), and in Section 03 (Field 03BDR) and </li>
<li>send TPNC 299 </li>
</alphalist></para>
<para>If the payment is the same as the amount the taxpayer has computed for his refund, or to be applied to estimated payments: <alphalist>
<li>Enter in Field 03BDR as a balance due and </li>
<li>Send TPNC 299</li>
</alphalist></para>
<para>If the taxpayer indicated the return filed was an extension, overlay the return with Form 4868, edit appropriately, then renumber. Renumber using TC 670 as the Primary Transaction Code and TC 460 as the Secondary Transaction Code.</para>
<para>If the taxpayer indicates that the return was filed in lieu of an estimated tax payment for a future tax period: <alphalist>
<li>input a credit transfer to move the money from the established TC 610 module to the future year using TC 660</li>
<li>Cancel the return DLN and forward to Files to be filed in its original block</li>
</alphalist></para>
<para>If the taxpayer indicates they want the IRS to figure their tax: <alphalist>
<li>Enter the payment in Section 03 (Field 03TAX) and Section 03, (Field 03BDR)</li>
<li>Send TPNC 218, if necessary</li>
</alphalist></para>
<para>If the taxpayer resides in Alaska, due to Alaska Permanent Fund Dividend (APFD), check for valid SSNs for the children listed as exemptions on the return. <alphalist>
<li>Research the children's account for outstanding balances</li>
<li>If determination can be made, initiate a credit transfer of the TC 610 payment to each account involved. Notate action taken</li>
</alphalist></para>
<para>If the entire payment is removed from the return and if Doc Codes 06, 08, 10, 12 or 22, renumber with applicable Doc Codes. For all other Doc Codes prepare Form 3893 to re-input the document without the ISRP indicator. Hold the return for a cycle before releasing to Batching. (This will prevent UPC 140 RC 2)</para>
<para>If a portion of the payment will remain with the return, ensure that all Sections have been transcribed, then enter a <emphasis type="b">C</emphasis> in the Clear field and continue processing</para>
</subsection4>
</subsection3>
<subsection3 id="id337101603"><date>(01-01-2025)</date>
<title>Unpostable Code 290 RC 9</title>
<para>This condition occurs due to invalid User Fee Data:<alphalist>
<li>Any Revenue Receipt (except 694 or 695) containing Designated Payment Code (DPC) 44-52.</li>
<li>TC 694 DPC 44-52 not containing secondary TC 360</li>
<li>TC 694 DPC 44-52 containing secondary TC 360 money amount (TC 694 and 360) do not match. Disregard the sign. </li>
<li>TC 694 or 695 with DPC 44-52 not addressed to MFT 55 </li>
<li>TC 694 input to MFT 55 tax period YYYY01 not containing DPC 44-52.</li>
</alphalist></para>
<para>The User Fee appears as TC 360 and the payment as a TC 694. The Designated Payment Codes (DPCs) for the TC 694 are shown in the table below:</para>
<table frame="all" id="id337101604" summary="User Fee Amounts">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="33*"/>
<colspec colname="col3" colwidth="34*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">DPC</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Definition</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Amount</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>44</entry>
<entry>Online Payment Agreement (OPA) Direct Debit Installment Agreement (DDIA) Origination Fee</entry>
<entry>$31.00</entry>
</row>
<row>
<entry>45</entry>
<entry>OPA Non-Direct Debit Installment Agreement Origination Fee</entry>
<entry>$149.00</entry>
</row>
<row>
<entry>46</entry>
<entry>OPA Installment Agreement Reinstatement or Restructure Fee (Reserved)</entry>
<entry>Reserved for Future Use</entry>
</row>
<row>
<entry>47</entry>
<entry>Installment Agreement Reduced Origination User Fee</entry>
<entry>$43.00</entry>
</row>
<row>
<entry>48</entry>
<entry>DDIA Reduced Origination User Fee</entry>
<entry>$43.00</entry>
</row>
<row>
<entry>49</entry>
<entry>DDIA Origination User Fee</entry>
<entry>$107.00</entry>
</row>
<row>
<entry>50</entry>
<entry>Installment Agreement Initial Original User Fee</entry>
<entry>$225.00</entry>
</row>
<row>
<entry>51</entry>
<entry>Installment Agreement Restructured User Fee Reinstated </entry>
<entry>$89.00</entry>
</row>
<row>
<entry>52</entry>
<entry>Installment Agreement Reinstated or Restructured Reduced User Fee (Low Income)</entry>
<entry>$43.00</entry>
</row>
</tbody>
</tgroup>
</table>
<para>See <citation type="IRM">IRM 3.12.10.3.3</citation>, Revenue Receipts, Installment Agreement User Fee and <citation type="IRM">IRM 5.19.1.6.4</citation>, Balance Due, Methods of Payments Installment Agreements (IA) for additional information regarding valid DPC and fee amounts.</para>
<subsection4 id="id337101605"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 290 RC 9</title>
<para>Use the following to resolve Designated Payment Code (DPC) MFT, TC, or money amount discrepancy:<alphalist>
<li>If the DPC is 44-52 and the TC is not TC 694 or TC 695, remove DPC.</li>
<li>If the TC 694 with DPC is 44-52 does not contain secondary TC 360, follow Unpostable instructions to add the TC 360. If Form 3893 is not completed, complete Form 3893 and input TC 360.</li>
<li>If the TC 694 is input to MFT 55 Tax period YYYY01 not containing DPC 44-52, enter the correct DPC 44-52.</li>
</alphalist></para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337100221"><date>(01-01-2025)</date>
<title>Unpostable Code 291 </title>
<para>Use the following instructions for resolving UPC 291 with Reason Codes 1, 2 or 9.</para>
<subsection3 id="id337101499"><date>(01-01-2020)</date>
<title>Unpostable Code 291 RC 1</title>
<para>Unpostable Condition 291 RC 1 occurs when the transaction amount is not compatible to transaction code. <alphalist>
<li>Transaction amount is not zero and the transaction code is 140/141/142/474/475/582/583 or 59X.</li>
<li>TC 370 Doc Code 51 for a credit amount.</li>
<li>TC 61X–69X with a reversal code other than zero and a Doc Code of 34 must have a zero primary amount and significant secondary amount (except TC 896 and 694).</li>
<li>TC 150 with a negative liability.</li>
<li>TC 610 with return Doc Code must be a credit.</li>
<li>TC 430 with a zero-amount field (Doc Code 61).</li>
</alphalist></para>
<subsection4 id="id337101501"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 291 RC 1</title>
<para>Renumber or cancel as appropriate.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101500"><date>(11-10-2021)</date>
<title>Unpostable Code 291 RC 2</title>
<para>Unpostable Condition 291 RC 2 occurs when Revenue Receipt transaction contains an invalid Secondary Transaction Code: <alphalist>
<li>Secondary TC is other than 170, 171, 200, 270, 280, 360, 460, 472, 570, 770 or 772.</li>
<li>Secondary TC 280 only valid for Primary TC 611, 641, 661, 671, 681, 691, or 721.</li>
<li>Secondary TC 460 valid for Primary TC 670 only.</li>
<li>Secondary TC 570 must have zero amount.</li>
<li>Secondary TC 200 or 360 must have a significant amount. </li>
<li>Secondary TC 770 only valid with Primary Transaction Code 721.</li>
<li>Secondary TC 772 only valid with Primary Transaction code 720.</li>
</alphalist></para>
<para>Unpostable Code 291 RC 2 occurs when a TC 370 has any of the following conditions: <alphalist>
<li>Secondary TC 630 or 636 with ID number other than 02.</li>
<li>Secondary TC 632 or 637 with ID number other than 03.</li>
<li>Secondary TC 63X present and Doc Code 52 has a status indicator of 1. </li>
<li>Secondary TC 63X is present and tax period is other than 197810 through 198011.</li>
<li>Secondary TC 636 or 637 with Doc Code other than 52.</li>
<li>Document contains an 870 date with no secondary TC 300 present.</li>
</alphalist></para>
<subsection4 id="id337100225"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 291 RC 2</title>
<para>If the document is an extension and Field 01STC is other than 460, change Field 01STC to 460.</para>
<para>If TC 370 with assessment code TC 290 and Doc Code 51: <alphalist>
<li>If module already contains an TC 870 agreement date, remove the agreement date and continue processing.</li>
<li>If module does not contain an TC 870 agreement date, change the TC 290 to 300 and continue processing.</li>
</alphalist></para>
<para>If TC 370 with assessment code TC 290 and Doc Code 52, delete the DLN and forward the document to Accounting.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100226"><date>(11-10-2021)</date>
<title>Unpostable Code 291 RC 9</title>
<para>Unpostable Condition 291 RC 9 occurs when TC 150 with invalid Information.</para>
<subsection4 id="id337100227"><date>(01-01-2025)</date>
<title>Correction Procedure UPC 291 RC 9</title>
<para>Review to determine correct information.</para>
<para>If unable to determine correct transactions, RJECT 640 and send to files.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337100228"><date>(01-01-2025)</date>
<title>Unpostable Code 292 </title>
<para>Use the following instructions for resolving UPC 292 with Reason Codes 0, 1, 2, 3, 4 and 5.</para>
<subsection3 id="id337100229"><date>(01-01-2023)</date>
<title>Unpostable Code 292 RC 0</title>
<para>Unpostable Condition 292 RC 0 occurs when EIC is greater than the maximum allowed for the tax period.</para>
<para>See IRM 3.12.3 Error Codes 337 and 338 and the Prior Year Job Aid, 2515–014, for the allowable amounts.</para>
<subsection4 id="id337100230"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 292 RC 0</title>
<para>Correct the EIC amount and assign appropriate TPNC. See <citation type="IRM">IRM 3.12.3</citation> Error Codes 337 and 338 and Prior Year Job Aid, 2515–014, EIC PY information.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100231"><date>(01-01-2020)</date>
<title>Unpostable Code 292 RC 1</title>
<para>Unpostable Condition 292 RC 1 occurs if section word count is present, and corresponding section is not input on the return.</para>
<subsection4 id="id337100232"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 292 RC 1</title>
<para>Enter the appropriate section with all applicable fields or delete the section that was erroneously entered.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100233"><date>(01-01-2023)</date>
<title>Unpostable Code 292 RC 2</title>
<para>Unpostable Condition 292 RC 2 occurs when TC 150 with doc code other than 05–12, 21–22, 26–27, or 72–73.</para>
<subsection4 id="id337100234"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 292 RC 2</title>
<para>Renumber the document with the appropriate doc code.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100235"><date>(11-10-2021)</date>
<title>Unpostable Code 292 RC 3 </title>
<para>Unpostable Condition 292 RC 3 occurs when a: <alphalist>
<li>Non-Math error return with IMF Total Tax Liability Computer not equal to IMF Total Tax Computer <emphasis type="b">or</emphasis></li>
<li>Math error return with IMF Total Tax Computer equal to IMF Total Tax Liability Computer and Balance Due/Refund equal to Balance Due/Overpayment Computer. </li>
</alphalist></para>
<subsection4 id="id337100236"><date>(11-10-2021)</date>
<title>Correction Procedure UPC 292 RC 3</title>
<para>Correct math error. (See <citation type="IRM">IRM 3.12.3</citation>).</para>
</subsection4>
</subsection3>
<subsection3 id="id337100237"><date>(01-01-2020)</date>
<title>Unpostable Code 292 RC 4</title>
<para>Unpostable Condition 292 RC 4 occurs when TC 150 or TC 430 has <emphasis type="b">any</emphasis> of the following invalid entity code address information present: <bulletlist>
<li>City character count +3, greater than City/State word count X5, and non-zero city character count</li>
<li>City character count or Major City Code is less than 2 characters</li>
<li>Entity Code is 1 or 3 and City/State word count is zero</li>
<li>Transaction with address data and invalid state code or major possession or blank city/state field</li>
</bulletlist></para>
<subsection4 id="id337100238"><date>(11-10-2021)</date>
<title>Correction Procedure UPC 292 RC 4</title>
<para>GTSEC 01 and enter the complete address as shown on the return. </para>
<para>Research IDRS CC INOLES and ENMOD for the address.</para>
<para>If you are unable to perfect the entity from the information on the return, CC INOLES or ENMOD take the following action:<table frame="all" id="id337101277" summary="If the address is found or not found" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If the address is</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>A] Found on INOLES or ENMOD</entry>
<entry>Enter the long entity (<citation type="IRM">IRM 3.12.2.4.2</citation>)</entry>
</row>
<row>
<entry>B] If an address is <emphasis type="b">NOT</emphasis> found</entry>
<entry><steplist>
<li>Enter IRS in Field 01ADD</li>
<li>Enter your campus city and state in Field 01C/S and the ZIP code unique to that campus in Field 01ZIP</li>
<li>Review EC 014</li>
</steplist></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>The city, state, and ZIP Code for each IMF processing center appear below: <table frame="all" id="id337101278" summary="Campus and city state and zip for each campus" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="COLSPEC0" colwidth="33*"/>
<colspec colname="col1" colwidth="34*"/>
<colspec colname="col2" colwidth="33*"/>
<thead>
<row>
<?PubTbl row rht="0.32in"?>
<entry align="center" valign="top"><emphasis type="b">Campus</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">City &amp; State</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">01ZIP</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>AUSPC</entry>
<entry>Austin/TX</entry>
<entry>73301</entry>
</row>
<row>
<entry>KCSPC</entry>
<entry>Kansas City/MO</entry>
<entry>64999</entry>
</row>
<row>
<entry>OSPC</entry>
<entry>Ogden/UT</entry>
<entry>84201</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection4>
</subsection3>
<subsection3 id="id337100239"><date>(11-10-2021)</date>
<title>Unpostable Code 292 RC 5</title>
<para>Unpostable Condition 292 RC 5 occurs when entity code is 1, 4 or 5 and <emphasis type="b">either</emphasis> of the following conditions is present: <bulletlist>
<li>Schedule SE SSN is invalid</li>
<li>Individual Retirement Accounts (IRA) section when the significant type indicator and entity code is other than 2 or a non-remittance, or FSC of 2 and IRA Spouse Indicator is zero</li>
</bulletlist></para>
<subsection4 id="id337100240"><date>(11-10-2021)</date>
<title>Correction Procedure UPC 292 RC 5</title>
<para>Verify the entity information in Section 01 is correct. Compare and correct the Name, SSN, Address, City, State and Zip code on the return and the screen.</para>
<para>Correct Schedule(s) SE. Ensure that the SSN on Schedule SE matches the Secondary SSN on the return (See <citation type="IRM">IRM 3.12.2</citation> Section 17 &amp; 18, 29/30 and Section 01).</para>
<para>Correct the IRA Spouse Indicator or filing status if Form 5329 is transcribed into Section 29/30 (the Spouse Indicator is <emphasis type="b">1</emphasis> for the Primary taxpayer and <emphasis type="b">2</emphasis> for the Secondary taxpayer). </para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337100241"><date>(01-01-2025)</date>
<title>Unpostable Code 293 </title>
<para>Use the following instructions for resolving UPC 293 with Reason Codes 2, 3, 4 and 8.</para>
<subsection3 id="id337100242"><date>(11-10-2021)</date>
<title>Unpostable Code 293 RC 2</title>
<para>Unpostable Condition 293 RC 2 occurs when SFR TC 150, Doc Code 10, blocking series 000–299 are present, the tax period is 198112 and later, and <emphasis type="b">either</emphasis> of the following conditions are present: <bulletlist>
<li>Sections other than 1–6 are present.</li>
<li>Tax data is present in Sections 4 through 6, other than exemption amount computer, standard deduction computer, Non-Taxable Earned Income, qualifying EIC Dep NUM, gross exemption amount computer.</li>
</bulletlist></para>
<subsection4 id="id337100243"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 293 RC 2</title>
<para>Check transcription in Sections 1–6.</para>
<para>If Sections other than 1–6 are present, delete the return and route back to originator.</para>
<para>If data is present in Sections 4–6, other than the information previously listed, delete the return and route back to originator.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100244"><date>(01-01-2020)</date>
<title>Unpostable Code 293 RC 3 </title>
<para>UPC 293 RC 3 occurs when TC 370 transaction amount is not equal to net money amount of all secondary transaction plus the civil penalty reference number amount.</para>
<subsection4 id="id337100245"><date>(01-01-2020)</date>
<title>Corrections Procedures UPC 293 RC 3</title>
<para>Re-input the document.</para>
</subsection4>
<subsection4 id="id337100504"><date>(11-10-2021)</date>
<title>Unpostable Code 293 RC 4</title>
<para>Unpostable Code 293 RC 4 occurs when TC 150 containing IMF Total Tax Computer, Withholding Amount, or Excess Social Security Tax greater than 10 positions (i.e., $100,000,000.00).</para>
</subsection4>
<subsection4 id="id337100506"><date>(01-01-2020)</date>
<title>Corrections Procedures UPC 293 RC 4</title>
<para>RESERVED</para>
</subsection4>
</subsection3>
<subsection3 id="id337100246"><date>(01-01-2020)</date>
<title>Unpostable Code 293 RC 8</title>
<para>Unpostable Condition 293 RC 8 occurs when TC 150 has an Entity Code 1 (Long Entity), 4 (Partial Entity), or 5 (Partial Entity) and <emphasis type="b">any</emphasis> of the following conditions are present: <bulletlist>
<li>The last name is not present</li>
<li>The first name exceeds the 35 maximum field length</li>
<li>The first name line is not present</li>
</bulletlist></para>
<subsection4 id="id337100247"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 293 RC 8</title>
<para>Review tax return and attachments for taxpayer’s first and last name.</para>
<para>If taxpayer’s first or last name exceed 35 characters, follow the instructions in <citation type="IRM">IRM 3.12.2.4.3.5(6)</citation> for abbreviation instructions.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337100865"><date>(01-01-2020)</date>
<title>Unpostable Code 294 RC 1</title>
<para>This condition occurs when a TC 150 with DLN XX211-XXX-99XXXX containing CCC G and any of the following conditions apply: <alphalist>
<li>Entity code is other than 2 or 4; or</li>
<li>Tax period is prior to 197301; or</li>
<li>CCC 5 or 6 is not present.</li>
</alphalist><note><emphasis type="b">CCC 5</emphasis> is needed when Form 1040X shows <emphasis type="b">one</emphasis> yes box checked for Presidential Election Campaign Fund (PECF). <emphasis type="b">CCC 6</emphasis> is needed when Form 1040X shows <emphasis type="b">two</emphasis> yes boxes checked for the PECF.</note><br/></para>
<subsection3 id="id337101292"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 294 RC 1</title>
<para>If Entity code is other than 2 or 4, Re-input the return using short entity.</para>
<para>If tax period is prior to 197301, before releasing, research for correct tax period. If the tax period was correctly transcribed, cancel the return DLN. Notate on routing slip <emphasis type="b">Invalid tax period prior to 197301</emphasis>. If tax period was transcribed incorrectly, re-input return with the correct tax period.</para>
<para>If the return does not contain CCC 5 or 6, determine if one of those codes are needed. If CCC 5 or 6 is needed ensure CCC G precedes the CCC 5 or 6.</para>
<para>For all other conditions, cancel DLN and route to Files.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100248"><date>(01-01-2025)</date>
<title>Unpostable Code 295 RC 3</title>
<para>Unpostable Condition 295 RC 3 occurs when TC 000 contains a fiscal month of 00 or greater than 12.</para>
<subsection3 id="id337101539"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 295 RC 3</title>
<para>If MFT 29 input Form 5329 long entity with RPC E.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100250"><date>(01-01-2025)</date>
<title>Unpostable Code 299 </title>
<para>Unpostable Code 299 is for TC 150 with invalid fields/invalid transactions. </para>
<subsection3 id="id337100928"><date>(01-01-2020)</date>
<title>Unpostable Code 299 RC 0</title>
<para>This condition occurs when an invalid received date is present.</para>
<subsection4 id="id337100929"><date>(01-01-2025)</date>
<title>Correction Procedures UPC 299 RC 0</title>
<para>Verify the received date on the return or attachments and correct any coding or transcription errors.</para>
<para>Ensure the received date is not earlier than the ending month and year of the tax period in Field 01TXP.<note notetype="example">If Field 01TXP is 202404 the received date cannot be earlier than 20240501. </note></para>
<para>If the return has multiple receive dates enter the earliest received date in Field 01RCD.</para>
<para>Verify and correct tax periods, dates, months, and year for Form 1040 on the following conditions:<alphalist>
<li>If the input return is other than a timely filed current calendar year, then date received must not be subsequent to current (23C date) processing date. </li>
<li>The month digits must be 01 through 12. </li>
<li>The day digits must be 01 through 28 when month is 02, except when leap year, then day digits must be 01 through 29.</li>
<li>The day digits must be 01 through 30 when the month is 04, 06, 09, or 11. </li>
<li>The day digits must be 01 through 31 when the month is 01, 03, 05, 07, 08, 10, or 12. <note>Remember the format of the received date is YYYYMMDD, YYYY for the year, MM for the month, and DD for the day.</note></li>
</alphalist></para>
<para>When the received date is equal or prior to the ending date of the tax period and the received date was transcribed correctly, change the received date to match the Julian date of the DLN. <note notetype="example">Field 01TXP is 202312 and the received date is 20231227.</note> </para>
<para>Be sure CCC Y is present for Short Year tax returns to change the accounting period at the Master File. See EC 260 for more information.</para>
<para>Ensure the tax period is entered correctly for Fiscal Year tax returns. See EC 260 for more information.</para>
<para>After all corrections have been made drop down to the <emphasis type="b">BOTTOM</emphasis> of the screen and transmit.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100508"><date>(11-10-2021)</date>
<title>Unpostable Code 299 RC 1</title>
<para>Unpostable Condition 299 RC 1 occurs when an invalid field or section is present on <citation type="Form">Form 1040</citation>.</para>
<para>This condition also occurs when more than 25 TC 150s are received for the same MFT/Tax Period. </para>
<subsection4 id="id337100622"><date>(01-01-2025)</date>
<title>Correction Procedure UPC 299 RC 1</title>
<para>Verify and correct tax periods, dates, months, and year for Form 1040.</para>
<para>After all corrections have been made drop down to the <emphasis type="b">BOTTOM</emphasis> of the screen and transmit.</para>
<para>If unable to determine correct dates, months, and year of Form 1040; RJECT 640 and send return to files.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100885"><date>(01-01-2025)</date>
<title>Unpostable Code 299 RC 2</title>
<para>Unpostable Condition 299 RC 2 occurs when:<alphalist>
<li>TC 150 is significant for Making Work Pay Credit or American Opportunity Tax (Hope) Credit, input to a tax period prior to 200912.</li>
<li>TC 150 contains Section 61 and 62 Form 8919, <emphasis type="b">Uncollected Social Security and Medicare Tax on Wages</emphasis> input to a tax period prior to 200712.</li>
<li>TC 150 is significant for First-Time Homebuyer Cr-Computer for Tax Period other than 200812 through 201011. </li>
<li>TC 150 is significant for Other Payment CR amount and the Other Payment Credit type is equal to R input to tax period other than 200812 through 200911.<br/>Basic RRC on Tax Liability Computer.<br/>Basic RRC on Qualifying Income Computer.<br/>Additional RRC for Eligible Children Computer.<br/>Total Recovery Rebate Credit Computer input to tax period other than 200812-200911.</li>
<li>TC 150 contains Section 71 or 72 presence indicator, input to tax period prior to 201312.</li>
<li>TC 150 is significant for Taxable Investment Income amount input to tax period prior to 201312. </li>
<li>TC 150 is significant for Additional Medicare tax on wages, Additional Medicare tax on SE Income, Tier I additional Medicare tax on Railroad Retirement Compensation amount, Additional Sch H tax for each spouse, input to tax period prior to 201312.</li>
<li>TC150 containing blanks in the Other Payment CR Type. Invalid codes are: 8, P, N, 4, X, F, 6, 1, B, Y, H, 3, 2, A, 9, 5, C.</li>
<li>TC 150 is significant for taxpayer health care responsibility penalty amount per computer or Total APTC/Total PTC/APTC Repayment/Reconciled PTC input to tax period prior to 201412.</li>
<li>Modify UPC 299 RC 2 to unpost TY 2014 through TY 2016 return with a responsibility penalty per computer is more than $13,380 for TY 2016, $12,420 for TY 2015, or $12,240 for TY 2014. </li>
<li>TC 150 is significant for Tax on Excess ABLE contribution amount for (Section 29 or 30) input to tax period prior to 201512.</li>
<li>TC 150 is significant on Form 8839 Refundable Adoption Credit computer amount input to tax period prior to 201012 through 201212.</li>
<li>TC 150 containing section 57 <citation type="Form">Form 8978</citation> input to a tax period prior to 201812.</li>
</alphalist></para>
<subsection4 id="id337101027"><date>(01-31-2025)</date>
<title>Correction Procedure UPC 299 RC 2</title>
<para>Correct coding, transcription, and misplaced entries on displayed fields.</para>
<para>Ensure all credits are input for the correct tax period.</para>
<para>Verify Sections 05, 44/45, 61/62, 71/72, 73/74 are entered correctly.</para>
<para>Review return and determine type of refundable credit being claimed by the taxpayer.</para>
<para>Ensure the amount in Field 050TH and the code in Field 05TYP are correct. Search the return for the amount of payment or credit in the Payments section of the return or for the form(s) in (6) below and enter the correct code in Field 05TYP.</para>
<para>Codes for Field O5TYP are as follows: <alphalist>
<li><emphasis type="b">A</emphasis> - Refundable Adoption Expenses (TY10 and TY11 only)</li>
<li><emphasis type="b">C</emphasis>- Refundable Child and Dependent Care Credit (TY21 only).</li>
<li><emphasis type="b">D</emphasis>-Deferred Tax from Schedule H and SE (TY20 only)</li>
<li><emphasis type="b">F</emphasis>- First Time Homebuyer’s Credit.</li>
<li><emphasis type="b">H</emphasis>- Health Coverage Tax Credit (TY02 through TY21 only).</li>
<li><emphasis type="b">K</emphasis>- Sick and Family Leave Credit after (03/31/2021 (TY21 through TY2023).</li>
<li><emphasis type="b">L</emphasis>- Sick and Family Leave Credit (TY21 through TY2023).</li>
<li><emphasis type="b">M</emphasis> - Making Work Pay Credit (TY10 and TY09 only)</li>
<li><emphasis type="b">P</emphasis> - Credit for Prior Year Minimum Tax Credit (2007 through 201311)</li>
<li><emphasis type="b">R</emphasis>-Recovery Rebate Credit (TY08, TY20, and TY21)</li>
<li><emphasis type="b">S</emphasis> - Withholding from Form 1042-S, <emphasis type="b">AUSPC only</emphasis> File Location Code is 20</li>
<li><emphasis type="b">T </emphasis>-Federal Telephone Excise Tax (TETR-TY06 only)</li>
<li><emphasis type="b">V</emphasis> - Multiple Credits/Payments Identified</li>
<li><emphasis type="b">Z</emphasis> - Other, or Unidentified Payment (TY 08 - TY 11 only)</li>
</alphalist><note>If more than one payment or credit type, use code <emphasis type="b">V</emphasis>.</note></para>
<para>If Field 05TYP is blank or the code is not listed in (10) above and Field 05OTH then correct coding and transcription errors or misplaced entries in Field 2951 or 3051 for Tax on Excess ABLE Contribution amount. Ensure field amount is from Line 51 Form 5329. </para>
</subsection4>
</subsection3>
<subsection3 id="id337100550"><date>(01-01-2020)</date>
<title>Unpostable Code 299 RC 3</title>
<para>Unpostable Condition 299 RC 3 occurs when a TC 150 contains a credit amount in an Unallowable Total field.</para>
<subsection4 id="id337100551"><date>(11-10-2021)</date>
<title>Correction Procedure UPC 299 RC 3</title>
<para>Correct coding and transcription errors or misplaced entries in displayed fields.</para>
<para>If the credit is for Form 4136 review Form 1040 field 05FUE. </para>
<para>Enter UA 85 and the amount on Form 1040 line 31 (Field 05FUE) when the credit amount claimed is <restrict>≡ ≡ ≡ ≡ ≡ ≡</restrict>or more.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100601"><date>(01-01-2020)</date>
<title>Unpostable Code 299 RC 4</title>
<para>Unpostable Condition 299 RC 4 occurs when a TC 150 is present, and the Primary SSN equals the Secondary SSN.</para>
<subsection4 id="id337100603"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 299 RC 4</title>
<para>Research IDRS and attachments for correct Primary and Secondary SSN.</para>
<para>Determine the correct Primary and Secondary SSN. </para>
<para>Correct Section 01 and all applicable fields and sections with the correct SSN.</para>
</subsection4>
</subsection3>
<subsection3 id="id337100947"><date>(01-01-2025)</date>
<title>Unpostable Code 299 RC 5 </title>
<para>RESERVED</para>
<subsection4 id="id337100959"><date>(01-01-2020)</date>
<title>Correction Procedures UPC 299 RC 5 RESERVED</title>
<para>RESERVED</para>
</subsection4>
</subsection3>
<subsection3 id="id337101005"><date>(01-01-2023)</date>
<title>Unpostable Code 299 RC 6 </title>
<para>Unpostable Condition 299 RC 6 occurs when:<alphalist>
<li>TC 150 for Tax Period 200812–201011 with significant First Time Home Buyer Credit amount in Section 58 (primary <emphasis type="b">Form 5405</emphasis>) or Section 59 (secondary Form 5405).</li>
<li>If First Time Home Buyer Credit NAP amount field for the primary is equal to zeros and check a box a, b, d, f, or g for Section 58 (primary Form 5405) is present.</li>
<li>If First Time Home Buyer Credit NAP amount field for the secondary is equal to zeros and check a box a, b, d, f, or g for Section 59 (secondary Form 5405) is present.</li>
</alphalist></para>
<subsection4 id="id337101011"><date>(11-10-2021)</date>
<title>Correction Procedures UPC 299 RC 6</title>
<para>GTREC the DLN of the document.</para>
<para>Input <emphasis type="b">R</emphasis> in Field 02RI to revalidate the document.</para>
<para>Follow instructions in <citation type="IRM">IRM 3.12.3</citation>; Error Code 329 and EC 128. </para>
</subsection4>
</subsection3>
<subsection3 id="id337101518"><date>(01-01-2023)</date>
<title>Unpostable Code 299 RC 8</title>
<para>Unpostable Condition 299 RC 8 occurs when a TC 150 claiming First-Time Home Buyer Credit Section 58 &amp; 59 are present/input before February 7, 2010.</para>
<para>The TC 150 claiming First-Time Home Buyer credit amount per computer without Section 58 and/or Section 59.</para>
<subsection4 id="id337101431"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 299 RC 8</title>
<para>GTREC the DLN of the document.</para>
<para>Input <emphasis type="b">R</emphasis> in field 02RI for validation.</para>
<para>Ensure sections 58 for the primary taxpayer &amp; 59 for the secondary taxpayer are correctly transcribed.</para>
<para>Follow the instructions in <citation type="IRM">IRM 3.12.3</citation>, Error Code 329.</para>
</subsection4>
</subsection3>
<subsection3 id="id337101519"><date>(01-01-2023)</date>
<title>Unpostable Code 299 RC 9</title>
<para>This condition occurs when TC 150 with significance in the remittance with return field input to MF 32 <emphasis type="b">or</emphasis> TC 150 older than 2 years of the current processing year attempts to post to MFT 32.</para>
<subsection4 id="id337101433"><date>(01-01-2023)</date>
<title>Correction Procedures UPC 299 RC 9</title>
<para>If the return is a current year return, post the return with CCC <emphasis type="b">3</emphasis>.</para>
<para>Follow instructions from Unpostables.</para>
</subsection4>
</subsection3>
</subsection2>
<subsection2 id="id337101102"><date>(01-01-2020)</date>
<title>Unpostable Condition 325 RC 3</title>
<para>Unpostable Code 325 RC 3 occurs when a credit reversal (TC XX2) with Doc Code 24, 47, 48,54 or 58 may have X-Ref, MFT, Tax Period 99/999999 (TIN) attempts to post and the input debit amount exceeds the module credit balance. </para>
<para>The credit reversal exceeds the Master File module credit balance.</para>
<subsection3 id="id337101103"><date>(11-10-2021)</date>
<title>Correction Procedures 325 RC 3</title>
<para>Correct coding, transcription errors and misplaced entries on displayed fields.</para>
<para>Forward to 6800 Account Excess Collections.</para>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337101411"><date>(01-01-2026)</date>
<title>ERS-17-44 Error File, ERS 17-45 Suspense File, IMF Interest Jeopardy Reports</title>
<para>These reports are generated from the error tape file and Reject Transaction File to reduce the amount of interest paid by the IRS.</para>
<para>The reports include: <bulletlist>
<li>BLOCK NUMBER</li>
<li>BATCH NUMBER</li>
<li>DLN</li>
<li>TAX PERIOD</li>
<li>STATUS</li>
<li>RECEIVED DATE</li>
<li>EXPIRATION DATE</li>
<li>OVERPAYMENT</li>
<li>CONTROL DATE</li>
</bulletlist></para>
<para>ERS–17–44 and ERS–17–45 are <emphasis type="b">daily reports,</emphasis> and they list overpayments in excess of $1,500 that may not be processed within the 45–day interest-free period. Items included are those with a Tax Class 2 an MFT 30 and the received date is 25 or more days.</para>
<para>Documents listed on ERS–17–44 or ERS–17–45 require expedited corrective actions to refund the overpayment. <alphalist>
<li>Locate the Error and Reject item listed and resolve immediately.</li>
<li>Notate the report with the date of correction and the Tax Examiner's initial to the right of the overpayment column.</li>
</alphalist></para>
</subsection1>
<subsection1 id="id337100324"><date>(11-10-2021)</date>
<title>Suspense Action Codes</title>
<para>This subsection lists the procedures for the disposition of ERS records and documents.<alphalist>
<li>Assigning Action Codes to resuspend records</li>
<li>Use of the suspense charge-out by tax examiners</li>
</alphalist></para>
<subsection2 id="id337100325"><date>(01-01-2025)</date>
<title>Assigning Action Codes to Resuspend</title>
<para>During suspense correction, the Suspense Tax Examiner may decide to resuspend a record if <emphasis type="b">either</emphasis> of the following conditions is present: <alphalist>
<li>If the document was suspended for review by another function and the tax examiner determines correspondence is needed input SSPND 211 or SSPND 224 (ACA).<note>If suspending for second correspondence input SSPND 212.</note></li>
<li>An incorrect action code was assigned in Code and Edit or Error Correction. </li>
</alphalist></para>
<para>For a complete list of ERS Action Codes, See <seealso idref="id337100471">Exhibit 3.12.37-2</seealso></para>
</subsection2>
<subsection2 id="id337100326"><date>(11-10-2021)</date>
<title>Use of Suspense Charge-Out by Tax Examiners</title>
<para>For each suspense record, a Form 8161, ERS charge-out is generated which includes:<bulletlist>
<li>Primary TIN</li>
<li>Form Number of Document</li>
<li>Tax Period</li>
<li>Current Date</li>
<li>Original DLN</li>
<li>Name Control</li>
<li>Control Day—Julian date of the GMF processed date</li>
<li>Literal <emphasis type="b">ERS</emphasis></li>
<li>Literal <emphasis type="b">Suspense</emphasis></li>
<li>Remittance Amount</li>
<li>Action Code description</li>
<li>Alpha Block Control</li>
<li>Batch Number</li>
<li>Employee Number of Error Correction or Rejects Tax Examiner</li>
</bulletlist></para>
<para>Each charge-out has an original and two copies. The two copies will be attached to the document when the Rejects TE receives a suspense case.</para>
<para>Use the charge-out to record such actions as: <alphalist>
<li>Resuspending—Enter the new Action Code and the date you resuspended the record.</li>
<li>Routing to other areas—<emphasis type="b">X</emphasis> the appropriate campus function or <emphasis type="b">other</emphasis> listed on the Form 8161.</li>
<li>Recording data received from research or history items.</li>
<li>Processing instructions for the person who may follow up on the case after you.</li>
<li>Deleting a record with CC RJECT or NWDLN; enter the Action Code assigned and the date of deletion.</li>
</alphalist></para>
</subsection2>
</subsection1>
<subsection1 id="id337100342"><date>(01-01-2026)</date>
<title>Correspondence</title>
<para>This IRM subsection contains procedures for taxpayer correspondence and must be used in conjunction with <citation type="IRM">IRM 3.12.3</citation> to avoid situations where subsequent correspondence cannot be initiated. Additionally, this subsection also provides instructions for working correspondence received from taxpayers. </para>
<para>Letters generated by Submission Processing must be approved by Headquarters when they are intended for dissemination to 10 or more persons. These letters are numbered in accordance with <citation type="IRM">IRM 1.17.1</citation> and <citation type="IRM">IRM 1.17.2</citation>, Printing and Publication. Form letters, pattern letter, and pattern paragraph are prescribed by Headquarters for use in service centers. Do NOT make changes to text format, date of issue (or revision), or physical characteristics of these letters and paragraphs without prior <emphasis type="b">Headquarters</emphasis> approval.</para>
<para>Information in this subsection includes: <bulletlist>
<li>Taxpayer correspondence</li>
<li>Signature Requirements</li>
<li>Loose Forms and Schedules</li>
<li>Streamline International Correspondence</li>
<li>Form 8288-A Credit Verification</li>
<li>Form 4442 Referrals</li>
<li>Second correspondence</li>
<li>Field 88RPD Return Processing Date (RPD)</li>
<li>Replies to Correspondence</li>
<li>MeF Responsibilities</li>
<li>MeF/Scanned Paper Replies</li>
<li>Secure Messaging Replies</li>
<li>Identity Theft - Related Replies</li>
<li>No Reply Processing Procedures</li>
<li>Undeliverable</li>
<li>Late Replies</li>
</bulletlist></para>
<subsection2 id="id337100343"><date>(01-01-2025)</date>
<title>Taxpayer Correspondence</title>
<para> Taxpayer correspondence is defined as, but not limited to: <alphalist>
<li>All written communications from a taxpayer or their representative, excluding tax returns, whether solicited or unsolicited.</li>
<li>Written communication in response to IRS requests for information or data. </li>
<li>Written communication which requests information, including requests that may accompany tax returns.</li>
<li>Written communication, including annotated notice responses, that provide additional information or dispute a notice.</li>
</alphalist></para>
<para>If taxpayer correspondence is for International IMF returns, follow the instructions in <citation type="IRM">IRM 3.22.3</citation>, International Error Resolution – Individual Income Tax Returns, Correspondence Procedures.</para>
<para> Correspondence is initiated by tax examiners in C&amp;E or ERS using Form 6001, Letter 12C Correspondence Action Sheet, or Form 3696-A, Correspondence Action Sheet. <note notetype="exception">For MeF correspondence refer to <citation type="IRM">IRM 3.12.2.2.12</citation>.</note><alphalist>
<li>These forms will be routed directly to the TE/clerk when received by the Rejects Unit. If the return or Correspondence Action Sheet indicates that the letter has already been transmitted, route the return directly to the suspense file.</li>
<li>IAT will be used for all correspondence letters, if possible. If the letter cannot be issued via IDRS, research the CAF for Power of Attorney prior to issuing the letter whenever the return was prepared by someone other than the taxpayer.</li>
</alphalist></para>
<para>Preparation of Correspondence Action Sheets on paper returns: <alphalist>
<li>Prepare Form 6001 or 3696-A (according to local procedures) for IMF correspondence.</li>
<li>Request <emphasis type="b">all</emphasis> missing information. Check for missing signature(s).</li>
<li>Enter the money amount(s) from the return in dollar and cents.</li>
<li>Attach the completed Form 6001 or Form 3696-A to the front of the return, leaving the entity portion exposed.</li>
<li>If the record was not suspended with the proper Action Code, enter CC SSPND and use the following as appropriate:<br/> <emphasis type="b">- 211</emphasis> for first correspondence<br/> <emphasis type="b">- 212</emphasis> for second correspondence<br/><emphasis type="b"> -213</emphasis> HCTC<br/><emphasis type="b">- 215</emphasis> for International correspondence<br/><emphasis type="b">-216</emphasis> for International second correspondence<br/><emphasis type="b">- 224</emphasis> for ACA correspondence</li>
</alphalist></para>
</subsection2>
<subsection2 id="id337101258"><date>(01-01-2025)</date>
<title>Signature Requirements</title>
<para>An <emphasis type="b">original signature</emphasis>, made by the taxpayer is required below the jurat (perjury statement) in the <emphasis type="b">Sign Here</emphasis> box. Without the taxpayer's signature (or the signature of both taxpayer’s if FSC 2), the return is not an official document and may not be processed. Accept a taxpayer’s signature elsewhere on the return if the taxpayer has drawn an arrow from their signature to the Sign Here/Jurat area. Before requesting the<emphasis type="b"> taxpayer’s</emphasis> original signature read all instructions below for exceptions to the original signature requirement. </para>
<para>Inspect all returns for original signatures.<alphalist>
<li>If an original signature is present in the correct location, accept the taxpayer’s signature and continue processing the return.</li>
<li>If the taxpayer has signed elsewhere but arrowed their signature to the correct location, accept the taxpayer’s signature and continue processing.</li>
<li>If the signature is faxed or scanned, see paragraph (3) below.</li>
<li>If only one signature is present on an FSC 2 return, see paragraphs (5 &amp; 6) below.</li>
<li>If the return is signed by someone other than the taxpayer or if only one signature is present on a FSC 2 return, review the return for indicators of a Power of Attorney, and see paragraphs (5 &amp; 6) below.</li>
<li>If the taxpayer is a minor child, see paragraph (7) below.</li>
<li>If you cannot determine whether the signature is original, SSPND 211 to correspond for an original signature.</li>
<li>Review the additional exceptions listed in paragraph (8) below.</li>
<li>If a return is unsigned and there are no notations the return has been sent back to the taxpayer for signature, RJECT 640 the return and send to Code and Edit to be sent back to the taxpayer.</li>
</alphalist></para>
<para>Faxed or scanned signatures: Accept as valid signatures only if:<alphalist>
<li>Signature was received as a Reject reply via Fax.</li>
<li>Received from Taxpayer Advocate Service (TAS), or </li>
<li>Received from an IRS area, Substitute for Return (SFR) return or returns marked <emphasis>59XXX</emphasis> (excluding <emphasis>59XXX</emphasis>) received from the Collections Branch, or Correspondence Imaging Inventory (CII) returns from Accounts Management.</li>
<li>Returns stamped by RIVO (including Handwritten RIVO reviewed).</li>
<li>Return edited with SPC <emphasis>B</emphasis> or <emphasis>M</emphasis>.</li>
<li>Copies with the remark Process as Original (PAO).</li>
<li>Electronic return prints with an IRSN processed as an original, even when no copy of <citation type="Form">Form 8453</citation> is attached, or when the electronically filed return was signed with a PIN.</li>
</alphalist></para>
<para> If the taxpayer used a thumbprint instead of a signature, route return to the Frivolous Filing Program (FRP), unless already seen by Frivolous, then process the return as an original and do not correspond for signature.</para>
<para><emphasis>Joint returns</emphasis> require the signature of both taxpayers: Accept the signature of one taxpayer on a FSC 2 return only if:<alphalist>
<li>One taxpayer is deceased and there is an indication that the signing taxpayer is filing as the surviving spouse.</li>
<li><emphasis type="b">POW-MIA</emphasis>(prisoner of war) or <emphasis type="b">MIA</emphasis>(missing in action) is indicated.</li>
<li>A statement is attached that one spouse is unable to sign the return due to health reasons.</li>
<li>In a combat zone/qualified hazardous duty area identified by -C freeze on IDRS cc IMFOLE for the Combat Zone (CZ) indicator.</li>
<li>If CZ indicator is <emphasis type="b">1</emphasis> then the taxpayer is still serving in a combat zone. If CZ indicator is <emphasis type="b">2</emphasis>, then the taxpayer is no longer a combat zone participant.</li>
<li>If a POA is attached granting the signing spouse signature authority for the other taxpayer. A POA is required even if the taxpayer indicates their spouse is overseas (including military if there is no notation of combat zone/hazardous duty area), or received advance permission from the IRS.</li>
</alphalist></para>
<para>Power of Attorney/Form 2848: If a Power of Attorney (POA) or <citation type="Form">Form 2848</citation> is attached, the designated individual may sign on behalf of the taxpayer. One original signature is acceptable on a joint return when the POA is valid for both taxpayers.<note>If a guardian, personal representative, executor, trustee, or fiduciary files the return, it must have an original signature. Supporting documentation that the appointee has the legal right to file on behalf of the taxpayer may also be required. See <citation type="IRM">IRM 3.12.2.3.18</citation>, Deceased Taxpayer for related information.</note></para>
<para>Minor Child: If the taxpayer is a minor child and the tax return is:<alphalist>
<li>Signed by a parent, never requires documentary evidence such as birth certificate, but the parent must sign as <emphasis type="b">Parent for Minor Child</emphasis>,<note>The notation must clearly identify the relationship to the minor.</note></li>
<li>Signed by a guardian or other fiduciary designee - <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> See <citation type="IRM">IRM 3.11.3.11.1</citation> Documentation Evidence Requirements.</li>
</alphalist></para>
<para><emphasis type="b">Exceptions:</emphasis> Do not correspond for a missing original signature in the situations below:<alphalist>
<li> Substitute for Return Prepared by IRS is noted, a signed <citation type="Form">Form 1040X</citation> is attached for the same period with an original signature, see 1040X is noted, or dummy return.</li>
<li>Section 6020(b) or prompt assessment is noted, or <citation type="Form">Form 4810</citation> Request for Prompt Assessment under IRC Code Section 6501(d), is attached.</li>
<li> Form 8879 IRS e-file Signature Authorization is attached with a valid signature, and there is any indication that an electronic filing was rejected or the return is for a prior year. </li>
<li>The return comes from Exam, Collection, or Accounts Management and <emphasis type="b">Process as Original</emphasis> (PAO) is present on the return.</li>
<li>An employee's Integrated Data Retrieval System (IDRS) number is present on the signature line.</li>
<li>Taxpayer has signed an attached CP59 or Letter 143C on the <emphasis type="b">Sign Here</emphasis> line. CSCO will notate in the <emphasis type="b">sign here</emphasis> area whether the taxpayer has signed under the jurat on the CP59 or Letter 143C.</li>
<li>Automated Substitute for Return (ASFR) is written or stamped in the top margin, a pink Form 3531 is attached, or Letter 2566 (SC/CG) or Letter 3219 (SC/CG) is attached. See IRM 3.12.2.3.2.</li>
<li>There is an indication of TRPRT (transcript of a return).</li>
<li>Computer Condition Code (CCC) <emphasis type="b">3</emphasis> is already present. </li>
<li>The return is from the Correspondence Imaging Inventory (CII). </li>
<li>Paper-printed MeF returns that are sent from TAS.</li>
<li>Efile Graphic Print (includes when the notation is circled out or lined through).</li>
</alphalist></para>
<para>If Form 8453/Form 8878/Form 8879: Electronic and digital signatures are permitted on these forms per the Temporary Deviation from Handwritten Signature Requirement for Limited List of Tax Form. Do not correspond for original signature on these forms if electronically or digitally signed and received between on or after August 28, 2020.</para>
<para>If the chart below states to send correspondence/returns to the Alpha Files, ensure the following are complete:<alphalist>
<li>Line through and/or <emphasis>X</emphasis> out any coding and editing markings for example CCC or SPC</li>
<li>Use Form 3210 to send correspondence/returns to Alpha Files</li>
<li>Ensure the <emphasis type="b">Remarks</emphasis> box of Form 3210 notates the reason the returns/correspondence will be stored in the Alpha File</li>
</alphalist></para>
<para>Use the following chart for missing signatures and no reply to missing signatures when the return does not fit any exception criteria listed in the tridocs above.<table frame="all" summary="Missing signature resolutions RJECT 640 or send to Alpha File" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="COLSPEC0" colwidth="33*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">If Signature is</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Then Rejects will</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">No Reply to missing signature</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>A) Missing signature and <emphasis type="b">NO</emphasis> previous correspondence </entry>
<entry> RJECT 640 attach Form 3531 and send return to C&amp;E to be sent back to the taxpayer. See note.</entry>
<entry>Return to the taxpayer</entry>
</row>
<row>
<entry>B) Signature is in wrong place and taxpayer did not arrow signature</entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to be sent back to the taxpayer as a second attempt. See note.</entry>
<entry>after second correspondence - RJECT 640 to Alpha Files </entry>
</row>
<row>
<entry>C) FSC 2 but only 1 taxpayer signed return</entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to be sent back to the taxpayer as second attempt. See note.</entry>
<entry>after second correspondence - RJECT 640 to Alpha Files</entry>
</row>
<row>
<entry>D) FSC 2 only one signature with Form 2848 (POA) attached </entry>
<entry>Research using CC CFINK for POA verification. Verify POA for missing TP signature, if POA is not valid, correspond SSPND 211.</entry>
<entry>CCC <emphasis>3 </emphasis>and process return</entry>
</row>
<row>
<entry>E) FSC 1 or 4 POA signed return, Form 2848 (POA) attached</entry>
<entry>Research using CC CFINK for POA verification. Verify POA is correct for taxpayer; Accept POA signature and continue processing. If POA signature is valid, continue processing. If POA is NOT valid correspond SSPND 211. </entry>
<entry>CCC <emphasis type="b">3</emphasis> and process return</entry>
</row>
<row>
<entry>F) Photocopy Signature</entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to send back to the taxpayer. See note.</entry>
<entry>RJECT 640 to Alpha Files</entry>
</row>
<row>
<entry>G) Undelivered mail return with missing signature</entry>
<entry>Research for better address if better address found SSPND 211, if better address not found, RJECT 640 and send to Alpha Files. </entry>
<entry>RJECT 640 to Alpha Files</entry>
</row>
<row>
<entry>H) Page 2 missing and No Signature</entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to send back to the taxpayer. See note.</entry>
<entry>RJECT 640 to Alpha Files</entry>
</row>
<row>
<entry>I) Taxpayer signs with an <emphasis>X</emphasis></entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to send back to the taxpayer. See note.</entry>
<entry>RJECT 640 to Alpha Files</entry>
</row>
<row>
<entry>J)Digital Signature</entry>
<entry>RJECT 640 attach Form 3531 and send return to C&amp;E to send back to the taxpayer. See note.</entry>
<entry>RJECT 640 to Alpha Files</entry>
</row>
</tbody>
</tgroup>
</table><note>When preparing a return for mail back to the taxpayer circle out or erase any received dates, editing, and coding markings. Identify all other correspondence conditions when mailing a return back for missing, photocopied or incorrectly placed signature.</note></para>
</subsection2>
<subsection2 id="id337100347"><date>(01-01-2026)</date>
<title>Loose Forms and Schedules</title>
<para>Loose forms and schedules are defined as those schedules and forms which have inadvertently been detached, or which cannot be associated with a return. When a loose schedule is found, research CC ERINV to determine if the case is in ERS/Rejects inventory.</para>
<para>If correspondence was initiated, pull the case and work with the information obtained. </para>
<para>If a loose page 2 with only a signature and no attachments or page 1 are obtained, research for more information. If no other information is received, and the document is no longer in ERS/Rejects, check for an IDRS control base. If an open control base is not found void the page 2. If loose page 2, original signature and attachments are received associate correspondence with return.</para>
<para>If the loose schedule/form does not pertain to a return in ERS/Rejects inventory, research IDRS CC TXMODA to determine if the return is controlled by another area and route the form/schedule to the controlling area with the open control base. If the return is not in ERS/Rejects inventory and no open control on IDRS send the loose form/schedule to Files to associate with the original return. If there are no DLNs on IDRS the form/schedule is considered classified waste as this documentation is not needed for audit trail purposes.</para>
<para>For International loose Forms and Schedules <emphasis type="b">Austin ONLY</emphasis> If a loose Form 8843 or 8840 are in ERS inventory associate return with original DLN. If research determines the return <emphasis type="b">is not in ERS</emphasis> inventory send the Form 8843 or 8840 to Alpha files.</para>
<para>When a loose Form 8822 is received, route Form 8822 to Entity using Form 4227, Intra0SC Reject or routing slip.</para>
<subsection3 id="id337101180"><date>(11-10-2021)</date>
<title>Streamline International Correspondence</title>
<para>When streamlined non-filers correspondence is received, ensure all returns submitted by the taxpayer are kept together. Do not separate the package. ERS will correspond if any of the following are not attached:<alphalist>
<li>The taxpayer is required to submit delinquent tax returns for the last three years for which a U.S. tax return is due. It is acceptable for the taxpayer to submit more than 3 years returns. If the taxpayer submits less than 3 years but attaches copies of returns or statements indicating the other years were already filed, <emphasis type="b">DO NOT</emphasis> correspond.</li>
<li>Completed questionnaire signed under penalty of perjury.</li>
<li>Signed and dated delinquent <emphasis type="b">Form TDF 90-22.1</emphasis> FBAR-Report of Foreign Bank &amp; Financial Accounts, for the past 6 years.</li>
<li>If a Form 8891, U.S. Information Return for Beneficiaries of Certain Canadian Registered Retirement Plans, is included with the submission, the following will be included with that form:<br/>A statement requesting an extension of time to make the election<br/>A dated statement signed under penalty of perjury describing the events that led to the failure to file Form 8891, how they discovered that failure and if they relied on a tax professional.</li>
<li>If any of the above items are missing, correspond with the taxpayer using Letter 4087C. Ensure page 1 and page 8 are always included in the correspondence to the taxpayer. </li>
</alphalist></para>
<para>If<emphasis type="b"> late replies</emphasis> or miscellaneous correspondence is received on a Streamlined return, follow the table below.<table frame="all" summary="Late replies or miscellaneous correspondence for streamline returns" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="col3" colwidth="33*"/>
<thead>
<row>
<?PubTbl row rht="0.49in"?>
<entry valign="top"><emphasis type="b">If</emphasis></entry>
<entry valign="top"><emphasis type="b">And</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<?PubTbl row rht="0.63in"?>
<entry><br/>Response is received after the return has been sent to files <emphasis type="b">OR</emphasis>							<br/>Miscellaneous Streamlined correspondence is received for a return that is not in ERS</entry>
<entry>Form 8891 is attached </entry>
<entry><bulletlist>
<li>Detach the F8891 and forward to Mail Stop 4300 AUSC</li>
<li>Send all other correspondence to Files to be associated with the original return. </li>
<li>Write <emphasis type="b">Streamlined</emphasis> at the top of the attachment alert when sending Streamlined Correspondence to Files </li>
</bulletlist></entry>
</row>
<row>
<?PubTbl row rht="0.76in"?>
<entry><br/>Response is received after the return has been sent to Files <emphasis type="b">OR</emphasis>						<br/>Miscellaneous Streamlined correspondence is received for a return that is not in ERS</entry>
<entry>FBAR (Form TDF 90–22.1) is attached </entry>
<entry><bulletlist>
<li>Detach FBAR(s) and route to Detroit per the routing guide.</li>
<li>Send all other correspondence to Files to be associated with the original return. </li>
</bulletlist><note>Write <emphasis type="b">Streamlined</emphasis> at the top of the attachment alert when sending Streamlined correspondence to Files</note></entry>
</row>
<row>
<?PubTbl row rht="0.76in"?>
<entry><br/>Response is received after the return has been sent to Files <emphasis type="b">OR </emphasis><br/>Miscellaneous Streamlined correspondence is received for a return that is not in ERS</entry>
<entry>No Form 8891 or FBAR is attached </entry>
<entry>Send to files to be associated with the original return. <note>Write <emphasis type="b">Streamlined</emphasis> at the top of the attachment alert when sending Streamlined correspondence to Files. </note></entry>
</row>
<row>
<?PubTbl row rht="0.76in"?>
<entry>If a 2012 tax return is submitted to be associated with the original Streamlined package.</entry>
<entry>We did not correspond for the 2012 tax return</entry>
<entry>Process as original non Streamlined return</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>If the taxpayer's correspondence is returned No Reply or incomplete, follow the instructions in <citation type="IRM">IRM 3.22.3-10</citation>.</para>
</subsection3>
<subsection3 id="id337100348"><date>(01-01-2026)</date>
<title>Form 4442 Referrals</title>
<para>If Form 4442 is received and research determines there is no indication the return was ever in ERS, route erroneous referrals back to the originator via the Form 4442 Erroneous Referral Coordinator found in SERP -Who/Where - Form 4442 Erroneous Referral Coordinator drop down list under Referrals from Call Sites.</para>
<para>After following the steps listed below to address the Form 4442, dispose of Form 4442 as classified waste unless it contains original documents from the taxpayer. If there is original documentation from the taxpayer, then associate the original documents with the tax return and send to files.</para>
<para>Follow the steps below to process Address Change requests.<table frame="all" id="id337101395" summary="Address Change Requests">
<tgroup align="center" cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top">IF</entry>
<entry valign="top">THEN</entry>
</row>
</thead>
<tbody>
<row>
<entry align="left">A] The return reference on Form 4442 is in Rejects awaiting a reply to taxpayer correspondence.</entry>
<entry align="left"><steplist>
<li>Input the new address information in Fields 01ADD, 01C/S, and 01ZIP.</li>
<li>SSPND the return with Action Code 211.</li>
<li>Resend the correspondence to the new address.</li>
</steplist></entry>
</row>
<row>
<entry>B] If the return is not in Rejects when Form 4442 is received.</entry>
<entry>Classify waste Form 4442.<note notetype="exception">If it can be determined the 4442 will be routed to another area then route to that area.</note></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Follow the steps below to process Responses to Reject Letters requests.<table frame="all" id="id337101390" summary="Responses to Reject Letters requests">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="51*"/>
<colspec colname="col2" colwidth="49*"/>
<thead>
<row>
<entry align="center" valign="top">IF</entry>
<entry align="center" valign="top">THEN</entry>
</row>
</thead>
<tbody>
<row>
<entry>A] The Form 4442 transmits a response to a letter issued out of Rejects, </entry>
<entry>Treat the response as if it has been received directly from the taxpayer and follow reply/no reply procedures as appropriate. </entry>
</row>
<row>
<entry>B] There are documents attached to the Form 4442 and the return is no longer in Rejects, </entry>
<entry>Treat Form 4442 reply as a late reply. Follow Late Reply procedures at <seealso idref="id337100554">IRM 3.12.37.14.8</seealso> as appropriate. </entry>
</row>
<row>
<entry>C] The return is not in Rejects when the Form 4442 is received,</entry>
<entry>Classify waste Form 4442.<note notetype="exception">If it can be determined the 4442 will be routed to another area then route to that area. </note></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Inquiries from other areas. If the Form 4442 is received from another area, research may be required to determine how to correctly close the case. Any time a case has been open in Rejects for an extended period of time, another area may be instructed to send a Form 4442 to follow up per their IRM.<table frame="all" id="id337101391" summary="4442 Inquiries from other areas">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top">IF</entry>
<entry align="center" valign="top">THEN</entry>
</row>
</thead>
<tbody>
<row>
<entry>A) Form 4442 has been received from another area and research determines that correspondence has been issued, and the suspense period has lapsed, </entry>
<entry>Follow IRM procedures to close the document. </entry>
</row>
<row>
<entry>B) Form 4442 has been received from another area and research determines that correspondence has not been issued, </entry>
<entry><steplist>
<li>SSPND the return with Action Code 211.</li>
<li>Resend the correspondence.</li>
</steplist></entry>
</row>
<row>
<entry>C) The return is not in Rejects when the Form 4442 is received, </entry>
<entry>Classify waste the Form 4442. <note>If it can be determined the 4442 will be routed to another area then route to that area. </note></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Follow the steps below for Form 4442 referrals with other issues.<table frame="all" id="id337101392" summary="Form 4442 referrals with other issues">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top">IF</entry>
<entry align="center" valign="top">THEN</entry>
</row>
</thead>
<tbody>
<row>
<entry>A) Form 4442 does not indicate why it is being sent to Rejects, </entry>
<entry>Route Form 4442 to Form 4442 Erroneous Referral Coordinator. </entry>
</row>
<row>
<entry>C) Form 4442 will be routed to another area and you can determine which one,</entry>
<entry>Route to that area, such as Entity or Exam.</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
</subsection2>
<subsection2 id="id337100355"><date>(01-01-2026)</date>
<title>Second Correspondence</title>
<para>When contact with the taxpayer has previously been made by any area of Submission Processing, including Form 3531, treat missing information on the return as a No Reply. </para>
<para>Correspond a second time when any of the following exceptions apply, if it was not requested during first correspondence and the taxpayer provided a <emphasis type="b">complete reply</emphasis>.<alphalist>
<li>Error Code 268, Alternative Minimum Tax</li>
<li>Error Code 358, Health Coverage Tax Credit (HCTC)</li>
<li><emphasis type="b">Form 4137</emphasis> when you cannot determine the liable taxpayer</li>
<li><emphasis type="b">Form 5329</emphasis> when you cannot determine the liable taxpayer</li>
<li><emphasis type="b">Form 8606</emphasis> when you cannot determine the liable taxpayer</li>
<li><emphasis type="b">Form 8919</emphasis> when you cannot determine the liable taxpayer</li>
<li><emphasis type="b">Schedule H</emphasis> when you cannot determine the liable taxpayer</li>
<li><emphasis type="b">Schedule SE</emphasis> when you cannot determine the liable taxpayer</li>
<li>If EC 028, 029 displays after Code &amp; Edit has corresponded or ERS has corresponded, for <emphasis type="b">field errors only</emphasis>. </li>
</alphalist></para>
<para>When second correspondence is issued based on the exceptions in (2) a) through i), enter SSPND 212 and prepare the applicable Form 3696-A for LTR 1263C.<note>Refer to the Forms 3696-A located under Job Aids in the SERP ERS/Rejects portal.</note></para>
<para>If ACA Error Codes 100, 101, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 270, or 352 displays after the first correspondence and the taxpayer has provided a complete reply, follow all corrections procedures for the error code displayed to determine if second correspondence is necessary. If second correspondence is necessary, SSPND 212 and follow the procedures under the error code for the appropriate paragraph(s) to send using Form 6001. Also include paragraph <emphasis type="b">g</emphasis> with fill-in #23. <?Pub _bookmark?><emphasis type="b">EXCEPTION:</emphasis> If correspondence has been issued for ACA EC 190 through 199, EC 270 or EC 352, and another ACA error code displays for the requesting additional information, do not correspond, follow No Reply procedures in <citation type="IRM">IRM 3.12.3.</citation></para>
<para>Do not correspond a second time if the information was previously requested and the taxpayer did not furnish the information or furnished an incomplete response. Treat the return as a No Reply using the procedures in <citation type="IRM">IRM 3.12.3</citation>.</para>
<para>If taxpayer second correspondence is for International IMF returns, follow the instructions in <citation type="IRM">IRM 3.22.3.287</citation>, International Error Resolution – Individual Income Tax Returns, Second Correspondence.</para>
</subsection2>
<subsection2 id="id337100358"><date>(01-01-2026)</date>
<title>Replies to Correspondence</title>
<para>When a reply is received from the taxpayer, revalidate the return, GTSEC 02 and enter <emphasis type="b">R</emphasis> in field 02RI. After revalidation use the reply to perfect the document. Resolve every issue with the taxpayer’s correspondence by updating fields, schedules and dummying in forms or schedules as required. <note>If necessary, use CC ENMOD to identify LTR 12C paragraphs issued for MeF and/or missing information for paper correspondence in the reply. See Job Aid 2515-015 for instruction on how to access LTR 12C.</note></para>
<para>When correspondence has been issued in error do not enter return processing date in Field 88RPD or CCC <emphasis type="b">U</emphasis>.<note> If correspondence was issued erroneously, refer to the correction procedures for the specific Error Code displayed. </note></para>
<para>Enter the correspondence reply received date in Field 88RPD (Return Processed Date). The format is YYYYMMDD. Y= Year, M= Month and D=Day. To correct Field 88RPD, refer to the date stamped on the reply, or the received date printed on the fax response. Do not use dates generated by the sending fax machine when the reply is received via fax. </para>
<para>When a return has been held in suspense and a complete reply has been received <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict><note>CCC U and the RPD <emphasis type="b">must not</emphasis> both be present in the same return.</note></para>
<para>The date in Field 88RPD may not be later than the current processing date or earlier than or equal to the received date in Field 01RCD. </para>
<para>The return processed date must be present when:<alphalist>
<li>a return has been held in correspondences suspense <emphasis type="b">and</emphasis>,</li>
<li>a <emphasis type="b">complete reply</emphasis> is received after the due date of the return.</li>
</alphalist><note notetype="exception">Do not enter date in Field 88RPD when correspondence was issued for Form 1310 only.</note></para>
<para>The RPD or CCC U must not be present if a complete reply is received prior to the due date of the return, including the <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></para>
<para>If the taxpayer response is a complete reply, but we failed to ask for all necessary information, enter reply date in 88RPD and follow No-Reply instructions in <citation type="IRM">IRM 3.12.3.35</citation> for missing information.</para>
<para>If the taxpayer responds<emphasis type="b"> Not My Return</emphasis> RJECT 640 and enter TC 971 AC 506. Follow <seealso idref="id337101260">IRM 3.12.37.14.5.4</seealso> ID Theft/Not My Return for further instructions. <alphalist>
<li>Send MeF reply to Alpha File.</li>
<li>If the taxpayer provides a completed return (i.e., page 1 and 2 of Form 1040); accurately reports estimated payments/credit elect, all required form and schedules are attached, and an original signature, detach the complete return from the correspondence including Form 14039. Edit correspondence received date in the center of page 1 of the tax return and edit RPC <emphasis type="b">8</emphasis>. Send document to Receipt and Control to be processed.</li>
<li>If paper return, attach response to return and send return to Files to be refiled in block.</li>
</alphalist></para>
<para>When the reply date is missing or edited incorrectly, refer to <citation type="IRM">IRM 3.12.2.5.5</citation> to determine the return processed date.</para>
<para>When a response is received on a Domestic return that meets International processing criteria per <citation type="IRM">IRM 3.12.2.3.7</citation>, the return must be renumbered to an International return. Kansas City and Ogden(only) will follow instructions in <seealso idref="id337100388">IRM 3.12.37.17</seealso> to transship the Domestic return to Austin Submission Processing for renumbering. Austin(only) will renumber the return using instructions in <seealso idref="id337100435">IRM 3.12.37.21.3</seealso>. </para>
<para>If the taxpayer submits an amended return, <emphasis type="b">Form 1040X</emphasis>, treat the amended return as the reply to the correspondence only if the ERS correspondence is attached. If it is not attached, file Form 1040X on the wall and wait for correspondence. If correspondence is not timely, correct the account using the Form 1040X and follow no reply procedures. If the <emphasis type="b">Explanation of Changes</emphasis> indicates a change or the addition of a form or schedule, in order to make that change to the original return the form or schedule must be attached to the Form 1040X. If the taxpayer’s computations on the amended return do not agree with the taxpayer’s original computation, correct/process the return with the information provided by the taxpayer. <emphasis type="b">Assign TPNC 558</emphasis> as appropriate.</para>
<para>Refer to the Error Codes contained in <citation type="IRM">IRM 3.12.3</citation> for the specific correction procedures. </para>
<para> If a 12C letter has been sent to the taxpayer and the 1040X unit forwards a Form 1040X before the reply due date, hold the Form 1040X only if the requested information isn’t provided. Combine the 1040X and the taxpayer’s 12C reply and process. Do not process the Form 1040X without the complete 12C response. If the complete reply isn’t received by the due date, work the Form 1040X and all documents. If needed, follow no reply procedures <citation type="IRM">IRM 3.12.3</citation>.</para>
<para>A return that had been issued a 12C letter for EC 190 through 199, EC 270 or EC 352 and responds with a reply, if other ACA error Codes display for the return requesting additional information (correspondence) <emphasis type="b">DO NOT CORRESPOND</emphasis>.</para>
<para>Reply instructions for the following error codes can be found in <citation type="IRM">IRM 3.12.3</citation> within; ECs 018, 028, 029, 30, 100, 101, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 270, 352, and 380. Follow the reply instructions under each error code in <citation type="IRM">IRM 3.12.3.</citation><note>CCC U is not input on EC 195, 197, 198 and 199.</note></para>
<para>Enter the reply data including any address changes. Use CC GTSEC for applicable sections.<note notetype="note">Master File addresses will not be changed unless there is oral/written verification from the taxpayer or written information from the authorized POA.</note></para>
<para>If the taxpayer's correspondence reply is a TIN, it must be validated against the <emphasis type="b">NAP/OLE</emphasis> (e.g., Primary TIN, dependent/EIC TINs, childcare credit TIN, Schedule H TIN, etc.).<alphalist>
<li>Enter CC <emphasis type="b">GTSEC 02</emphasis> and transmit. Enter <emphasis type="b">R</emphasis> in Field 02RI, Revalidation Indicator, to generate Error Code 011 for TIN validation. <note>It may be necessary to access the NAP using CC INOLE for verification of any TINs that do not display in Error Code 011.</note></li>
</alphalist></para>
<para>When correspondence issue is unknown, research CC ENMOD to identify the LTR 12C paragraph(s) number/alpha sent. Refer to LTR 12C and read the applicable paragraph(s). See Job Aid 2515-015 instructions on how to access LTR 12C.</para>
<para>If the taxpayer's response changes the balance due/refund amount, assign <emphasis type="b">TPNC 558</emphasis> and all other applicable TPNCs.</para>
<para>For replies to <emphasis type="b">multiple tax periods on the Same Return</emphasis>, follow instructions in <citation type="IRM">IRM 3.12.2.3.20</citation> .</para>
<para> Process as <emphasis type="b">No Reply</emphasis> when the taxpayer has indicated a <emphasis type="b">refusal</emphasis> to comply. </para>
<para>If the taxpayer indicates that the response must be delayed because of illness, the preparer is out of town, or other valid reason, attach the letter to the return. Resuspend the return with Action Code 212 (Action Code 216, International returns for AUSPC only) as appropriate and leave in suspense. Allow the taxpayer up to thirty days from the interim response received date. Consider the original response due date (45 days) and the 2nd correspondence date and ensure enough time has been given for the taxpayer to respond. If no response from the taxpayer after the extended 30 days, treat as No Reply.</para>
<para>If the taxpayer's response includes a question or a request for additional information, take the following action: <alphalist>
<li>If the information is not available to answer the question/request, send a copy to the appropriate area in the campus.</li>
<li>Ensure that the taxpayer's name, TIN, and the received date are on any correspondence leaving the area.<note>Process the reply and close the case prior to routing the taxpayer's request. </note></li>
</alphalist></para>
<para>If additional information is provided, make the necessary corrections based on the new information. </para>
<para>If the taxpayer addresses new/other issues that are not related to the correspondence, but the issue does relate to the original return, correctly process the return using <citation type="IRM">IRM 3.12.3.</citation> If the issue relates to another type of return (ie., Prior Year Return), route to Accounts Management.</para>
<para>Filing of original tax returns via <emphasis type="b">FAX</emphasis> will only be allowed as part of a return perfection process initiated by the IRS where contact with the taxpayer has been made and documented. If multiple fax replies are received for the same taxpayer destroy the duplicate faxes. Do not send duplicate fax replies to Files or the Alpha File.</para>
<subsection3 id="id337101387"><date>(11-07-2023)</date>
<title>MeF/Scanned Paper Responsibilities</title>
<para>Each site is responsible for the complete closure of MeF and/or Scanned paper returns in their inventory.</para>
<para>If your site is <emphasis type="b">assisting</emphasis> the primary site, it is the responsibility of the assisting site to complete the ERS 100 work. </para>
<para>If required, the assisting site will issue the correspondence and have the correspondence returned to the primary site. It is the primary sites responsibility to complete the replies.</para>
<para>All Unpostables, Entity, Accounting Function, Review or Reject function issues are the responsibility of the primary site. </para>
<para>Do not deviate from these instructions. Only deviate from these instructions if requested from Headquarters. </para>
<para>The table below provides each sites responsibility for MeF processing: <table frame="all" id="id337101384" summary="MeF campus responsibility">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis><emphasis type="b">Sites </emphasis></emphasis></entry>
<entry valign="top"><emphasis type="b">MeF Responsibility </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry><emphasis>Austin</emphasis></entry>
<entry>Austin</entry>
</row>
<row>
<entry><emphasis>Kansas City</emphasis></entry>
<entry>Kansas City, Andover <emphasis>&amp;</emphasis> Fresno</entry>
</row>
<row>
<entry><emphasis>Ogden</emphasis></entry>
<entry>Ogden <emphasis type="b">&amp;</emphasis> Philadelphia</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
<subsection3 id="id337100982"><date>(01-01-2026)</date>
<title>MeF/Scanned Paper Replies</title>
<para>Use the following procedures before sending MeF and/or Scanned Paper replies to Files. Ensure all IDRS research is performed before inputting IDRS action. <note>This process is necessary to create a DLN in Files to associate the reply. Input all REQ54 actions within 10 business days after closing the MeF and/or Scanned Paper reply in Rejects. Complete routing form and send to Files. Allow the CARE unit to review the return before sending to Files. Do Not input TC 290 for zero (.00) when a MeF and /or Scanned Paper reply has been closed after inputting SPC <emphasis type="b">T</emphasis>. </note></para>
<para>When processing Scanned Paper correspondence, the attached PDF scan of the original return, IRS <citation type="Form">Form 1040</citation> Document will be present.<note>Transcription errors may be present, and some fields may contain invalid or incorrect data if the field is blank or illegible during the scanning process. Verify and perfect the fields in IDRS using the attached <citation type="Form">Form 1040</citation> Scanned Document.</note></para>
<para>If a campus receives a MeF and/or Scanned Paper reply for another campus Do Not Transship. Any IMF processing center can process MeF and/or Scanned Paper replies using IDRS CC CMODE. IDRS CC CMODE allows the user to access other IDRS databases. To change modes, enter CC CMODE and the 2-digit code abbreviation for the other campus. Below are the 2-digit codes for each site:<table frame="all" id="id337101388" summary="CMODE campus codes">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Sites</emphasis></entry>
<entry valign="top"><emphasis type="b">2-Digit Codes</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Andover</entry>
<entry>AN</entry>
</row>
<row>
<entry>Austin</entry>
<entry>AU</entry>
</row>
<row>
<entry>Fresno</entry>
<entry>FR</entry>
</row>
<row>
<entry>Kansas City</entry>
<entry>KC</entry>
</row>
<row>
<entry>Ogden</entry>
<entry>OG</entry>
</row>
<row>
<entry>Philadelphia</entry>
<entry>PH</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Review the DLN of the MeF and/or Scanned Paper reply. Blocking Series 92X indicates Injured Spouse (Example 76211-446-929XX-X). Input TC 290 .00 using Hold Code 4 for Injured Spouse MeF replies. If the Blocking Series is other than 92X, continue to paragraph 5.</para>
<para>Research for Freeze codes using IDRS CC TXMODA and IMFOLI and IMFOLT. Freeze codes are listed next to the letters FRZ&gt; at the top of each IDRS screen. Use Document 6209, Section 8A, Master File codes to research displayed freeze codes. Leave hold code field blank if Freeze code field is blank. Use the freeze code chart below if freeze codes are listed. Research IDRS CC IMFOL, TXMOD, TRDBV, TRERS and take the following action: <steplist>
<li>Use the IAT Tools Manager, click and startup <emphasis type="b"><emphasis type="u">Quick CC</emphasis></emphasis>, <emphasis type="b"><emphasis type="u">REQ54</emphasis></emphasis>, and <emphasis type="b"><emphasis type="u">Fill Forms</emphasis></emphasis> then arrange the tools to <emphasis type="b">your</emphasis> preference. </li>
<li>Enter IDRS CC TXMODA for the Tax Period of the reply and transmit.</li>
<li>Enter CC REQ54 and transmit. This will generate an ADJ54 format. </li>
<li>Review CC TXMODA to determine if TAS has an open control. A TAS open control shows the Category (CAT) as ATAO. <emphasis type="b">Do not work TAS open control cases</emphasis>. Contact TAS for further instructions. </li>
<li>If there is an Open Control, other than TAS, place the control in B status and work as instructed and put control back in open status when complete.</li>
<li>On ADJ54 input the next sequence number (i.e., if this is your first input for the day start with 1). Then for each subsequent input change accordingly (1, 2, 3, etc.). Notate your tax examiner number on the correspondence with the sequence number used behind it (i.e., 12345XXXXX-4).</li>
<li>Enter the Blocking Series (BLK) as <emphasis><emphasis type="b">05</emphasis>.</emphasis></li>
<li>Enter the Correspondence Received Date (CORRESP-DT). This will be the received date stamped on the correspondence by Receipt and Control.<note>If the reply date stamp is missing or edited incorrectly determine the CORRESP-DT in this order <br/>a) Fax date on reply <br/>b) date stamped on the reply <br/>c) date in the postmark on the reply envelope <br/>d) current date minus 10 days</note></li>
<li>Enter the IRS Received Date (IRS-RCVD—DT) as the date of input.</li>
<li>In the ACTIVITY field, overlay 54-TAX-ADJ with MeFReply and/or SCNNDPPRREPLY. (This field will not accept a space between words).</li>
<li>Enter the Return Processing Date (RET-PROC-DT). This entry will be the same as the CORRESP-DT entry.</li>
<li>Enter the Transaction Code (TC) as <emphasis><emphasis type="b">290</emphasis>.</emphasis></li>
<li>Enter the Transaction Amount (AMT) as <emphasis><emphasis type="b">.00</emphasis>.</emphasis></li>
<li>Enter the Hold Code (HLD-CD) per the instructions in (5) below.</li>
<li>If <emphasis type="b">TC150 not posted</emphasis>, enter the Posting Delay Code (PSTNG-DLAY-CD) as “4”. If <emphasis type="b">TC150 posted</emphasis>, do not enter Posting Delay Code. (TC 150 is an indication that the taxpayer’s return has posted).<note> If CCC 3 or O is input, enter Hold Code 4.</note></li>
<li>If there is an open control, place the control in <emphasis type="b">B</emphasis> status, work as instructed, and put control back in open status when completed. </li>
<li>Enter the SOURCE-DOCUMENT-ATTACHED as <emphasis><emphasis type="b">Y</emphasis>.</emphasis></li>
<li>Enter the REMARKS as <emphasis><emphasis type="b">MeF Reply and/or Scanned Paper Reply</emphasis></emphasis></li>
<li>Transmit.</li>
<li>Put source document in Folder, (Document 6981) and attach Form 10274 to the front of the folder. Include current date (Input Date), Employee Number, Sequence numbers (ex.,103,104,105) Function and Program Code on label (Form 10274). Bundle 100 documents or less in each source document folder to send to files. </li>
<li>Send folders to files. </li>
</steplist></para>
<para>If the Freeze code <emphasis type="b">is not</emphasis> listed below enter <emphasis type="b">0</emphasis> in the Hold Code field. If screen shows CI/RIVO involvement input hold code 4. The <emphasis type="b">RIVO indicators are TC 971 AC 111, 121,122, 123, 124, 125, 134, and 199</emphasis>. Use the chart in (8) below when considering Freeze codes and Hold codes.</para>
<para>If the -G Freeze code is on CC TXMODA/IMFOLT <emphasis type="b">AND</emphasis> TPNC 558 is displayed on CC TXMOD/RTVUE/TRERS in response to the MeF reply DO NOT SEND -G Freeze code to AM. Input REQ54 TC 290 .00 in this scenario.</para>
<para>Review all freeze codes and open controls before making a final decision to input the TC 290 .00 or sending the reply to Files or AM.<note>If Action Needed for Freeze Codes state to <emphasis type="b">Route to AM, do not input REQ54 TC 290 .00</emphasis>. Route per local procedures.</note></para>
<para> Use the chart below and review the Freeze codes and Hold codes on MeF Replies. <table frame="all" id="id337101272" summary="Freeze codes and hold codes and routing to AM" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="4.78in"?>
<colspec colname="col1" colwidth="31*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="COLSPEC0" colwidth="35*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Freeze code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Use Hold Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Action Needed</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry align="center"><emphasis type="b">-A</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">E-</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-E</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-G</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-K</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-L</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">M-</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">P-</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">-Q</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-R</emphasis></entry>
<entry align="center"><bulletlist>
<li>4 if screen shows CI/RIVO indicators</li>
<li>4 if Form 8379 (BS 92X) </li>
</bulletlist></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">-S</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">-U</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">-V</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-W</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">-X</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
<row>
<entry align="center"><emphasis type="b">Y-</emphasis></entry>
<entry align="center"/>
<entry align="center"><emphasis type="b">Route to AM</emphasis></entry>
</row>
<row>
<entry align="center"><emphasis type="b">-Z -</emphasis></entry>
<entry align="center"><emphasis type="b">4</emphasis></entry>
<entry align="center"/>
</row>
</tbody>
</tgroup>
</table></para>
<para>If IDRS CC ENMOD displays name control mismatch or no account on Masterfile as an example, create a dummy module to input the TC 290 .00 using IDRS CC MFREQD. </para>
<para>For MeF returns with MFT 32, send the returns to Alpha Files. Use MFREQD to create the MFT 32 module if the MFT 32 is not established. Use CC TXMODA when the MFT 32 is established to enter a History Item using IDRS CC ACTON: H,DOC2ALPHA<note>Use Exhibit 17 as a reference/example for Acton History Procedures <seealso idref="id337100486">Exhibit 3.12.37-17.</seealso></note></para>
<para> Always contact an employee with an open control base prior to taking action on a case, except in the following instances: <alphalist>
<li>Do not initiate contact if the control is in <emphasis type="b">B</emphasis> or <emphasis type="b">M</emphasis> (monitoring status).</li>
<li>Do not initiate contact if there is a History Item but not Open Control</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101644"><date>(04-17-2025)</date>
<title>Secure Messaging Replies</title>
<para>Taxpayer Digital Communications (TDC) is an IRS program that digitizes communications with taxpayers using eGain Secure Messaging. </para>
<para>Individuals and their representatives can use Secure Messaging when invited on Letter 12C to securely submit electronic documentation in response to the correspondence.</para>
<para>After approval of BEARS entitlement requests and training (<a external="no" href="https://irsgov.sharepoint.com/sites/JQKDIURL/SitePages/Secure-Message-Training.aspx?OR=Teams-HL&amp;CT=1708441728454" title="Secure Messaging Training">Secure Messaging Training (sharepoint.com)</a>), employees can access the secure messaging website <a external="no" href="https://connect.irs.gov/" title="https://connect.irs.gov/">https://connect.irs.gov/</a>.</para>
<para>After closing the case using the taxpayer’s reply, use CC ACTON to leave a history item with the case ID.</para>
<para>If the taxpayer’s response includes information that warrants the return to be reviewed by an area outside of SP, print the reply and suspend the return with the correct action code for review.<note notetype="caution">Do not close the return in egain until a response is received from the reviewing area.</note></para>
<para>If after inputting the reply, an error code sets that warrants second correspondence, reply to the taxpayer using the appropriate knowledge base article and suspend the document with CC SSPND 212. </para>
<para>If a response is received that is not pertaining to correspondence and/or a reply is not attached, close the case in eGain.</para>
<para>If a response is received and falls under International and/or BMF processing. Follow procedures in <seealso idref="id337100388">IRM 3.12.37.17</seealso>.</para>
<para>If a response is received for a different DLN than what is showing in the eGain system, treat the reply as a new case and work per normal correspondence procedures.</para>
</subsection3>
<subsection3 id="id337101260"><date>(04-03-2024)</date>
<title>Identity Theft - Related Replies</title>
<para>The following instructions are for Identity Theft related replies. Do not issue 4310C letter or similar ID Theft letter if it was previously issued. </para>
<para>If Form 14039, <emphasis type="b">Identity Theft Affidavit</emphasis>, police statement or similar statement is received. input TC 971 AC 506 using IDRS CC REQ77. Follow instructions in paragraph (4) below for inputting a TC 971 AC 506.</para>
<para>Use the following chart to resolve taxpayer's ID Theft related replies: <table frame="all" id="id337101283" summary="Resolving ID Theft related replies" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="29*"/>
<colspec colname="col2" colwidth="26*"/>
<colspec colname="col3" colwidth="45*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">IF</emphasis></entry>
<entry valign="top"><emphasis type="b">AND</emphasis></entry>
<entry valign="top"><emphasis type="b">THEN</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry><emphasis type="b">A)</emphasis></entry>
<entry/>
<entry/>
</row>
<row>
<entry><emphasis type="b">Timely Reply</emphasis></entry>
<entry>A) Taxpayer states <emphasis type="b">Not My Return </emphasis>and/or Form 14039, police report and/or equivalent statement</entry>
<entry><steplist>
<li>RJECT 640 bad return</li>
<li>Input TC 971 AC 506. </li>
<li>If paper, send return including 12C and/or Form 14039 to Files to be refiled in the block of work.</li>
<li>If MeF, send reply to Alpha files.</li>
</steplist></entry>
</row>
<row>
<entry/>
<entry>B) <emphasis type="b">Not My Return</emphasis>, Form 14039, police report and/or equivalent statement <emphasis type="b">and</emphasis> Here's my return</entry>
<entry><steplist>
<li>RJECT 640 the bad return.</li>
<li>Input TC 971 AC 506.</li>
<li><emphasis type="b">If paper</emphasis>, route reply including 12C to Files to be refiled in the block of work </li>
<li>If MeF, send reply to Alpha files.</li>
<li>Process the good return with FPC<emphasis type="b"> 8</emphasis><alphalist>
<li>Attach Form 14039 or equivalent statement to the good return</li>
<li>Forward good return to R&amp;C for processing</li>
</alphalist></li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">B)</emphasis></entry>
<entry/>
<entry/>
</row>
<row>
<entry><emphasis type="b">No Reply/Undeliverables</emphasis></entry>
<entry>If EC 029 (Unclaimed Credits)</entry>
<entry><steplist>
<li><emphasis type="b">For current year</emphasis>, if the filer doesn’t reply to correspondence or is undeliverable, enter SPC <emphasis type="b">T</emphasis>, and CCC <emphasis type="b">3</emphasis> in the first position, when EC 029 redisplays, enter <emphasis type="b">C</emphasis> in the clear field.</li>
<li>For Prior year returns, No reply, RJECT 640.</li>
<li>Input TC 971 AC 506.</li>
<li>If paper return, send to Files to be refiled in the block of work.</li>
<li>If MeF, input CC ACTON History Item, DOC2ALPHA, and send return to Alpha Files.</li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">C)</emphasis></entry>
<entry/>
<entry/>
</row>
<row>
<entry><emphasis type="b">Late Reply</emphasis></entry>
<entry>A) <emphasis type="b">Not My Return</emphasis> and/or Form 14039 and/or equivalent statement for EC 029 </entry>
<entry><steplist>
<li><emphasis type="b">If MeF</emphasis>, route reply including 12C and Form 14039 to Alpha File</li>
<li><emphasis type="b">If paper</emphasis>, route reply including 12C and Form 14039 to Files to be refiled in the block of work</li>
<li>Input TC 971 AC 506 if not already present. </li>
</steplist></entry>
</row>
<row>
<entry/>
<entry>B) Not My Return and/or Form 14039 and/or equivalent statement for EC 029 <emphasis type="b">AND</emphasis> Here’s my return</entry>
<entry><steplist>
<li>Process the good return with FPC 8</li>
<li>Attach Form 14039 or equivalent statement to the back of the good return</li>
<li>Forward good return to R&amp;C for processing</li>
<li>Bad return: <emphasis type="b">If MeF</emphasis> return, send to Alpha File and <emphasis type="b">if paper</emphasis> return send to Files to be refiled in the block of work.</li>
<li>Input TC 971 AC 506 if not already present.</li>
</steplist></entry>
</row>
<row>
<entry/>
<entry>C) <emphasis type="b">Is MY Return</emphasis> and return was moved to MFT 32</entry>
<entry><bulletlist>
<li>Before sending correspondence to the SP IDT group, ensure the return's DLN matches the DLN of the TC 976 posted on MFT 32. Ensure the taxpayer’s ES payments are the same as on the tax return. If they are not the same send the correspondence to the Alpha Files. If the ES payments are correct do the following: </li>
</bulletlist><bulletlist>
<li>If it is determined that the ES payments are correct, forward TP return, Form 1040, 12C and other documentation to the SP IDT unit using Form 3210 to have return removed from MFT 32 to MFT 30.</li>
</bulletlist></entry>
</row>
<row>
<entry/>
<entry>D) Is <emphasis type="b">MY</emphasis>									<emphasis type="b">Return</emphasis>											<emphasis type="b">and</emphasis> return was moved to MFT 32 and TP sends Form 1040X or other documentation for additional credits deduction, or other changes</entry>
<entry><bulletlist>
<li>Before sending correspondence to the SP IDT group, ensure the return's DLN matches the DLN of the TC 976 posted on MFT 32. Ensure the taxpayer’s ES payments are the same as on the tax return. If they are not the same send the correspondence to the Alpha Files. If the ES payments are correct do the following: </li>
<li>Before sending correspondence to the SP IDT group, ensure the return's DLN matches the DLN of the TC 976 posted on MFT 32. Once determination is made forward TP return, Form 1040X/other documentation and 12C to SP IDT unit using Form 3210 to have return moved from MFT 32 to MFT 30.</li>
</bulletlist></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Enter TC 971 AC 506 Instructions: <alphalist>
<li>On CC ENMOD, enter CC REQ77 and transmit see <seealso idref="id337100489">Exhibit 3.12.37-20</seealso>. This will generate FRM77 format.</li>
<li>Enter the TC field as 971</li>
<li>Enter Secondary Date field as 123120XX, XX notates the year the ID Theft is based on return information.</li>
<li>Enter the TC971/151 field as 506.</li>
<li>Enter the MISC field as WI SP OTHER</li>
<li>Enter Remarks as IDENTITY THEFT</li>
<li>Transmit</li>
</alphalist></para>
</subsection3>
</subsection2>
<subsection2 id="id337100359"><date>(01-01-2026)</date>
<title>No Reply Processing Procedures</title>
<para>Revalidate the return by inputting GTSEC 02 and entering <emphasis type="b">R</emphasis> in Field 02RI.</para>
<para>Follow instructions in the No Reply section of <citation type="IRM">IRM 3.12.3.35</citation> . If the instructions under actions to be taken are to enter <emphasis type="b">CCC 3</emphasis>, enter it in the first position of Field 01CCC. All other CCCs must follow. CCC U is not input on EC 195, 197, 198 and 199.<note>If it was determined correspondence was issued in error, do not enter U in Field 01CCC.</note></para>
<para> If other Error Codes display on the return requesting additional information (correspondence), follow the no reply procedures for those Error Codes. <emphasis type="b">DO NOT CORRESPOND</emphasis>.</para>
<para>If correspondence is issued on an <emphasis type="b">undeliverable</emphasis> and the taxpayer does not reply, follow No Reply procedures in IRM 3.12.3.35. </para>
<para>01CCC U must not be input in if the following conditions are met:<bulletlist>
<li>Correspondence was issued in error.</li>
<li>Correspondence was sent for Form 1310, only.</li>
</bulletlist></para>
<para>When correspondence issue is unknown, research CC ENMOD to identify LTR 12C paragraph(s). See Job Aid 2515-015 for instructions on how to access LTR 12C.</para>
<para>If a return has a missing signature, follow instructions in <seealso idref="id337101258">IRM 3.12.37.14.2</seealso> before taking action.</para>
<para>For <emphasis type="b">Multiple Tax Periods</emphasis> follow instructions in <citation type="IRM">IRM 3.12.2.3.20</citation>.</para>
</subsection2>
<subsection2 id="id337100361"><date>(01-01-2026)</date>
<title>Undeliverable</title>
<para>Undeliverable mail is any letter, notice or correspondence sent to an individual or business taxpayer and returned to the IRS with an indication that the individual no longer resides or the business is no longer located at the address.</para>
<para>If undeliverable correspondence is received with an USPS <emphasis type="b">yellow label address sticker</emphasis>, this USPS address may be the last known address (LKA) for this account. However, research is necessary prior to using this USPS address.<note>Any USPS yellow label sticker undeliverable mail received with handwritten address information or comments MUST BE considered <emphasis type="b">THIRD PARTY</emphasis> information and may not be used to update the address on IDRS.</note><table frame="all" id="id337101394" summary="If/Then chart to process undeliverable mail with a Yellow label address sticker from USPS">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">If</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry><emphasis type="b">A]</emphasis> The taxpayer’s name printed in the letter and what is shown on the “yellow label” are exactly the same, <note>If the address is a correctional facility, check the return and attachments for the taxpayer’s Prisoner ID number and input in Field 01NL2. </note></entry>
<entry><steplist>
<li>Update the taxpayer’s mailing address to the <emphasis type="b">yellow label</emphasis> address.</li>
<li>Reissue the correspondence to the taxpayer’s updated mailing address.</li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">B]</emphasis><emphasis type="b"> The taxpayer’s mailing address differs </emphasis>from the <emphasis type="b">yellow label</emphasis> and the name printed on the <emphasis type="b">yellow label</emphasis> is an exact match to the correspondence,</entry>
<entry><steplist>
<li> Update the taxpayer’s mailing address to the <emphasis type="b">yellow label</emphasis> address.</li>
<li>Reissue the correspondence to the taxpayer’s updated mailing address.</li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">C]</emphasis> If the taxpayer’s first name is like the one on the <emphasis type="b">yellow label</emphasis>, but the last name is an exact match, </entry>
<entry>Confirm whether IDRS records show any other taxpayers with similar first names and the exact same last name at the same address. <steplist>
<li>If not, update the taxpayer address.</li>
<li>Otherwise, do not update the taxpayer address.</li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">D] </emphasis>If the taxpayer first and last name do not match the name on the “yellow label”, </entry>
<entry>Do not update the taxpayer address.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>If the undelivered mail is for ID Theft correspondence such as 4310C letter, attach the Form/Correspondence and destroy as classified waste. Refer to <citation type="IRM">IRM 21.5.1</citation> for guidance on handling classified waste. Do no research on undelivered ID Theft correspondence.</para>
<para>If the following is written or stamped on the undeliverable mail envelope, research is<emphasis type="b"> mandatory</emphasis> for a more current address:<bulletlist>
<li>Forward Time Expired, return to sender</li>
<li>Bad Address</li>
<li>No such street</li>
<li>No such number</li>
</bulletlist></para>
<para>Research using IDRS Command Codes ENMOD, and IMFOLE, for the most current address. Use the ITIN Real Time System (RTS) for ITIN filers, if needed. Before completing any address changes, compare and note the following researchable dates:<bulletlist>
<li>date of correspondence</li>
<li>postmark date on the envelope </li>
<li>date of pending address change</li>
<li>latest address change on IDRS (TC 152 date)</li>
</bulletlist></para>
<para>Use the following chart when undeliverable correspondence <emphasis type="b">is</emphasis> in the ERS inventory, research IDRS for a more current address. <table frame="all" id="id337100741" orient="port" pgbrk="nobreak" summary="Research for Undeliverable correspondence " width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If research shows</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry><emphasis type="b">A]</emphasis> A more current address for ACA correspondence </entry>
<entry>Notate new address and reissue correspondence to the most current address and SSPND 224</entry>
</row>
<row>
<entry><emphasis type="b">B]</emphasis> Address change is pending and matches undelivered address and the address shown on the yellow USPS label </entry>
<entry><note>Do Not update the address on IDRS</note> Send correspondence to the updated address.</entry>
</row>
<row>
<entry><emphasis type="b">C]</emphasis> Correspondence date or the postmark date is EARLIER than the address update cycle shown on ENMOD/IMFOLE <emphasis type="b">AND</emphasis> A newer address IS located,</entry>
<entry> Notate new address and reissue correspondence to new address and SSPND 211</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> D]</emphasis> The same address but a different DLN is located, for the same tax period</entry>
<entry morerows="0" nameend="col2" namest="col2"> Refer to lead tax examiner for further instructions</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b">E]</emphasis> The same address that is on your original document,</entry>
<entry morerows="0" nameend="col2" namest="col2"><steplist>
<li>For paper returns, attach undeliverable letter and envelope to the back of the return and process as a No Reply.</li>
<li>For MEF returns, process as a No Reply then Classify waste as this documentation is not needed for audit trail purposes.</li>
<note notetype="exception">When correspondence was issued for EC 028, send MEF UD correspondence to alpha files. If correspondence was for EC 029, follow instructions in <seealso idref="id337101260">IRM 3.12.37.14.5.4</seealso> to input REQ77 prior to sending MEF UD correspondence to alpha files.</note>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">F</emphasis> A new or more current address is found,</entry>
<entry><steplist>
<li>Reissue correspondence to the new or more current address and attach new 6001.</li>
<li>Notate new address and leave a working trail on the letter to be filed on the suspense wall.</li>
</steplist></entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>When undeliverable correspondence is received after the suspense time has expired and the return is <emphasis type="b">not</emphasis> in ERS inventory, research IDRS for a more current address or if the return is assigned to another area. </para>
<para> Use the chart below to research for a better address when the return is <emphasis type="b">not</emphasis> in ERS inventory:<table frame="all" id="id337100742" orient="port" pgbrk="nobreak" summary="Research for a better address using ENMOD" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If research shows</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> A new or more current address,</entry>
<entry morerows="0" nameend="col2" namest="col2"><steplist>
<li>Route undeliverable correspondence to ICT.</li>
</steplist></entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> The same address,</entry>
<entry morerows="0" nameend="col2" namest="col2">Route the undeliverable correspondence to Files for association with the return.</entry>
</row>
<row>
<entry><emphasis type="b">C]</emphasis> MeF correspondence is undelivered mail, </entry>
<entry> MeF UD correspondence is Classified Waste as this documentation is not needed for audit trail purposes. </entry>
</row>
</tbody>
</tgroup>
</table><note>If you notice issues such as frivolous filing issues, mass mail out concerns or ID theft on the account, contact your lead for guidance. </note></para>
</subsection2>
<subsection2 id="id337100554"><date>(01-01-2026)</date>
<title>Late Replies</title>
<para>Use CC ERINV or CC GTREC with the returns 14-digit DLN to determine if the reply <emphasis type="b">is</emphasis> or <emphasis type="b">is not</emphasis> in the ERS inventory. If the return is in the ERS inventory, the return is not a late reply. Follow <citation type="IRM">IRM 3.12.3</citation> for processing instructions for the Error Code displayed.</para>
<para>When a late reply is received in response to <emphasis type="b">EC 029 Unclaimed Credits</emphasis>, review <seealso idref="id337101260">IRM 3.12.37.14.5.4</seealso> Identity Theft-Related Replies before taking action. </para>
<para>When a reply is received after the suspense time has expired and the return is <emphasis type="b">not</emphasis> in ERS inventory, research IDRS using command codes IMFOL, ENMOD and TXMOD to determine if the return is assigned to another area and follow the chart below.<table frame="all" id="id337100743" orient="port" pgbrk="nobreak" summary="Research using IDRS IMFOL ENMOD for Late Replies" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If research shows</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> The return has been assigned to another area,</entry>
<entry morerows="0" nameend="col2" namest="col2">Check TXMOD to determine the IDRS number the case is assigned to. Follow local procedures to route the return to the area. <emphasis type="b">Late Replies must be routed to the proper function within five days of receipt.</emphasis> If the function/area is outside of your processing center use the Mail Routing Guide and Form 13538 to route to the appropriate processing center and mail stop.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> The return is not assigned to another area,</entry>
<entry morerows="0" nameend="col2" namest="col2">Compare the Late Reply (schedule/form/attachment) with the accompanying letter and follow procedures in the following tables.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para> Research using IDRS CC ENMOD, IMFOLT, TXMOD, RTVUE, TRDBV and TRERS to determine if any of the following conditions apply and take the appropriate actions in the chart below after it is determined that a TC 150 has posted to the account. <table frame="all" id="id337100744" orient="port" pgbrk="nobreak" summary="Late repliesto be routed to ICT or Entity" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If the Late Reply</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> Changes the total tax, balance due, or refund</entry>
<entry morerows="0" nameend="col2" namest="col2">Route to ICT.</entry>
</row>
<row>
<entry><emphasis type="b">B]</emphasis> Has Form 8962, Form 8965, or Form 1095A attached, </entry>
<entry>Route to ICT only if there are changes to total tax, balance due, or refund.</entry>
</row>
<row>
<entry><emphasis type="b">C]</emphasis> Is for SE liability and the reply indicates the SE is for the secondary taxpayer instead of the primary taxpayer, </entry>
<entry>Route to ICT.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> D]</emphasis> Changes the entity (change to primary SSN, name control, name line, or filing status),</entry>
<entry morerows="0" nameend="col2" namest="col2">Route to Entity. </entry>
</row>
<row>
<entry><emphasis type="b">E]</emphasis> Has a Form W-7 attached,</entry>
<entry>Route the reply with Form W-7 to AUSPC using Form 3210. Notate the controlling DLN and temporary SSN.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> F]</emphasis> Has an address change or minor name changes that do not affect the name control,</entry>
<entry morerows="0" nameend="col2" namest="col2">Use IDRS CC ENMOD/INCHG to make minor changes to address or minor name changes that do not impact the name control of the taxpayer. </entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> G]</emphasis> Has no change in tax or balance due/refund amount, </entry>
<entry morerows="0" nameend="col2" namest="col2">Send the Late Reply (paper) to Files using local procedures to be associated with the return using the controlling DLN. Send MeF late reply to Files using TC 290 .00 to create a source document following <seealso idref="id337100982">IRM 3.12.37.14.5.2</seealso> MeF Replies procedures.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>If the late reply has changes to ACA, total tax, balance due or refund research to see if the TC 150 has posted. Research using IDRS CC IMFOL, TRDBV, TXMOD, UPTIN, FFINQ and ENMOD to determine if a TC 150 has posted or other actions have been taken on the late reply. If the TC 150 has not posted check the cycle date of the reply to ensure enough time has lapse from the posting of the no reply. Also, follow instructions for ID Theft Related Replies. <seealso idref="id337101260">IRM 3.12.37.14.5.4</seealso><emphasis type="b"> If No TC 150 is found on late replies do the following</emphasis>:<table frame="all" summary="Route to ICT if changes are needed to tax or refund" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col3" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If No TC 150 </emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry><emphasis type="b">A]</emphasis> Research determines no open controls on paper or MeF returns, and reply has no change to ACA, total tax, balance due or refund,</entry>
<entry>Send the Late Reply (paper) to Files using local procedures to be associated with the return using the controlling DLN. Send MeF late reply to Files using TC 290 .00 to create a source document following <seealso idref="id337100982">IRM 3.12.37.14.5.2</seealso> MeF Replies procedures.</entry>
</row>
<row>
<entry><emphasis type="b">B]</emphasis> Research determines no open controls on paper or MeF returns, and reply has changes to ACA, total tax, balance due or refund,</entry>
<entry>Route to ICT.</entry>
</row>
<row>
<entry><emphasis type="b">C]</emphasis> Late reply has an Unpostable condition,</entry>
<entry>Check UPTIN to determine if assigned to a local Unpostable Unit. If assigned locally, attach UPTIN print to show the document is open and route to the Unpostable Unit for resolution. <note>If case is RIVO or UPC 126 RC 0 related, send to Alpha Files. If case is UPC 150 RC0-9 send document to Statutes.</note></entry>
</row>
<row>
<entry><emphasis type="b">D]</emphasis> Research determines late reply is GUF Voided,</entry>
<entry><steplist>
<li>If GUF voided route late reply to Alpha File.</li>
<li>If previously voided and reply establishes taxpayer’s identity, retrieve paper return from Alpha File or reconstruct electronic return with print from the RRD and process the return.</li>
</steplist></entry>
</row>
<row>
<entry><emphasis type="b">E]</emphasis> Late reply has Form 1040X attached with changes to ACA, total tax, balance due and/or refund,</entry>
<entry>Send Form 1040X to ICT. BMF sites working IMF Late replies, route to your ICT.</entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection2>
</subsection1>
<subsection1 id="id337100362"><date>(01-03-2023)</date>
<title>Documents Routed to Other Campus Functions</title>
<para>This subsection lists the procedures for routing documents to other campus functions.<bulletlist>
<li>General instructions to route documents to other campus functions </li>
<li>Statute expiration cases </li>
<li>Exam Review</li>
<li>Entity Control </li>
<li>Manual refunds </li>
<li>Credit transfers </li>
</bulletlist></para>
<subsection2 id="id337100363"><date>(01-01-2025)</date>
<title>General Instructions for Documents Routed to other Campus Functions</title>
<para>Some returns require action by other areas of the campus before being worked by Rejects or ERS including: <bulletlist>
<li>Statute Protection Unit</li>
<li>Examination</li>
<li>Entity Control Unit</li>
<li>Accounting</li>
</bulletlist></para>
<para>If a spreadsheet is needed ensure a complete DLN, SSN, Name Control, and Tax Period is listed on each spreadsheet. </para>
<para>For paper returns, prepare Form 3210 with copies. <alphalist>
<li>Complete the TO box with a complete address including the drop point or stop number.</li>
<li>Release Date with current date. </li>
<li>Transmittal Code include all special types to be identified. </li>
<li>Remarks provide any required information. </li>
<li>Quantity indicates volume of documents per batch being sent. </li>
<li>Code or Type indicate application Type.</li>
<li>Document Identification indicate the MFT, TXPD, DLN, last 4 of the SSN, EIN, Form, and Payment amount etc. If the documents are hand delivered, the person receiving the transmittal will sign in this block. Transmittals routed to Statute Control will always be signed and dated by the receiver.</li>
<li>From include your complete return address with phone number and stop number. </li>
<li>Releasing Official signature of person preparing Form 3210 with manager approval.</li>
<li>Originator Telephone Number indicate manager's phone number.</li>
<li>Ensure all information is completed on all four parts pages of form.</li>
<li>If the documents are hand delivered, the person receiving the transmittal will sign in the Received and verified box. Transmittals routed to Statute Control will always be signed and dated by the receiver. </li>
<li>Route the documents with the first copy of Form 3210 to the receiving function. </li>
<li>Retain the copy of Form 3210.<note notetype="exception">Do NOT send paper returns to Exam for review. Exam will review paper returns in the respective area the returns are being held in for review.</note></li>
</alphalist></para>
<para>Campuses that use local automated systems to control items routed to other functions must incorporate as much information as possible from these procedures to ensure control of the routed items. In addition, Rejects Unit managers must ensure that sufficient manual procedures are in place to back up the local automated system in case of a malfunction.</para>
<para>As the documents are returned, enter the date in the Disposition column of Form 3210 or at the bottom of Form 8161, or in the appropriate area on the local automated system. All documents may be returned at one time with the transmittal, or the documents may be sent back individually. <alphalist>
<li>After two weeks, contact the receiving area regarding any documents and/or list of MeF DLNs that have not been returned. Note the response on Form 3210 or 8161. Weekly follow-up is required on any delinquent items. </li>
<li>As ERS items are returned, pull copy 2 of the charge-out from the suspense file and activate Unworkable records with CC ACTVT.</li>
</alphalist></para>
<para>Representatives from other areas may come to Rejects to examine and make a determination on the disposition of the documents. In this case, Form 3210 is not required. Take the action indicated on the Form 4227. </para>
</subsection2>
<subsection2 id="id337100365"><date>(01-01-2023)</date>
<title>Statute Expiration Cases</title>
<para>The Internal Revenue Code provides that the IRS will assess and collect taxes and refund credits within a specific time limit. Rejects will review all prior year returns and all documents rejected for additional determination as statute expiration cases. <alphalist>
<li>Review involves those returns where the statute of limitations will expire within 90 days or less and those for which the statute has already expired. </li>
<li>Each campus distributes a monthly listing of statute alert tax periods. </li>
</alphalist><note notetype="note">Generally, Statute will not clear any potential statute documents without enough information (i.e., to establish a tax liability amount) or a return, and/or correspondence without an original signature agreeing to that liability. (<emphasis type="b">A photocopy of a signature is not acceptable</emphasis>.)</note></para>
<para>Potential statute expiration cases will be hand-carried to the Statute Unit. <alphalist>
<li>For ERS documents, use Form 8161 for routing control. <note notetype="note"> The Statute Stamp is good for 90 days from the date stamped. If the case has been in the inventory for longer than 90 days, hand-carry/reclear the case through the Statutes Unit.</note></li>
<li>Rejects will keep control of these cases until they are returned from Statutes. Form 4227 will indicate either that the return must be processed or voided to Statutes.</li>
</alphalist></para>
<para>Some cases will be received in Rejects which have already been identified as true statutes cases. These returns are not rerouted on Form 3210 but can be voided immediately to Statute.</para>
<para>ERS examiners will SSPND using Action Code 310 and route to Statute Control. <alphalist>
<li>If cleared by the Statute Unit, indicated by TC 59X-XX on TXMOD or tax return, enter C in Clear Code Field.</li>
<li>To process a cleared Statute, enter Return Processing Code <emphasis type="b">K</emphasis>.</li>
</alphalist></para>
<para>Exception: Do not route the following returns to Statute:<bulletlist>
<li>Coded CCC W</li>
<li>TC 599 edited in upper left margin</li>
<li>6020(b) returns</li>
<li>SFR returns</li>
</bulletlist></para>
<subsection3 id="id337101755"><date>(01-01-2026)</date>
<title>Processing Missing Statute Documents</title>
<para>If the return is a refund return, use Command Code IMFOLT to determine if the RSED date has expired. If expired, void the return.</para>
<para>If the RSED date has not expired, follow the below instructions:<alphalist>
<li>Compare the total tax and BDR (balance due/refund line) on the open return to the total tax and BDR on the posted return. If the amounts match and/or the amounts are less than the total tax and BDR of the posted return, void the return.</li>
<li>Compare the total tax and BDR on the open return to the total tax and BDR on the posted return. If the total tax and/or BDR is more, process the return.<note>Do not correspond for any missing information, process missing information as a No Reply following instructions in <citation type="IRM">IRM 3.12.3</citation>.</note></li>
</alphalist></para>
<para>If the return is a balance due return, use Command Code IMFOLT to determine if the ASED date has expired. If expired, void the return.</para>
<para>If the ASED date has not expired, follow the below instructions:<alphalist>
<li>Compare the total tax and BDR on the open return to the total tax and BDR on the posted return. If the amounts match and/or are less than the total tax and BDR of the posted return, void the return.</li>
<li>Compare the total tax and BDR on the open return to the total tax and BDR on the posted return. If the total tax and/or BDR is more, process the return.<note>Do not correspond for any missing information, process missing information as a No Reply following instructions in <citation type="IRM">IRM 3.12.3</citation>.</note></li>
</alphalist></para>
</subsection3>
</subsection2>
<subsection2 id="id337100367"><date>(11-07-2023)</date>
<title>Exam Review</title>
<para>Code and Edit and Error Correction will identify returns that suggest questionable or fraudulent refund practitioner with frivolous filer implications. The specific situations to be identified are included in other sections of <citation type="IRM">IRM 3.11.3</citation> Returns and Analysis/Individual Income Tax Return and <citation type="IRM">IRM 3.12.3</citation> Error Resolution/Individual Income Tax Return. </para>
<para>For ERS, the following Action Codes are used to route cases to Examination: <bulletlist>
<li>333 - Prompt Audit</li>
<li>334 - Joint Committee</li>
<li>335 - Frivolous Filer Case</li>
<li>360 - Other In-House Research</li>
<note>If a return was previously reviewed/stamped, do not send the return a second time to the same area. </note></bulletlist></para>
<para>Action Code 331, Frivolous Filer Review, is used for cases held in Error Resolution for review by an FRP coordinator or another designee as assigned.</para>
<para>For non-ERS, all cases will use CCC U (Code and Edit) or Action Code 3 (Error Correction).</para>
<para>When the case has been reviewed by Exam, follow the corrective action indicated on Form 4227 or other attachment. For ERS, enter <emphasis type="b">C</emphasis> in the Clear Field if instructed to process the return. <note>EXAM instructions will remain attached to the tax return. </note></para>
<para>Follow the same procedures for Action Code 370 (Examination) referrals. </para>
<para>If Form 14039 (Identity Theft Affidavit), a police report or similar statement is attached to a return ensure SPC 8 has been input. Do Not remove or detach Form 14039. Continue processing the return. If Form 14039 is loose in Rejects, research for an Active DLN in ERS and associate the return if possible. If the DLN is not in ERS, route Form 14039 to Account Management according to local procedures.</para>
<para> Follow the chart below to determine RIVO good or false wages:<table frame="all" id="id337101022" summary="Route to IVO for wage verification for EC027" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">If RIVO states wages are</emphasis></entry>
<entry colsep="1" rowsep="1" valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><emphasis><emphasis type="b">Good</emphasis></emphasis><emphasis type="b"> wages</emphasis>.</entry>
<entry colsep="1" rowsep="1"><steplist>
<li>Route return to Entity on Form 3210 for Entity to assign an IRSN. The narrative on Form 3210 will state <emphasis type="b"><emphasis>Bad-assign IRSN.</emphasis></emphasis> Provide original return or Section 1 screen print of CC TRDBV of E-file return.</li>
<li>Rejects will disallow the primary exemption and all applicable credits, input <emphasis type="b">CCC <emphasis>3</emphasis></emphasis>, and post the return to the IRSN.</li>
</steplist></entry>
</row>
<row>
<entry colsep="1"><emphasis><emphasis type="b">False wages</emphasis></emphasis></entry>
<entry colsep="1"><emphasis type="b">REJECT 640</emphasis> to void the return.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<subsection3 id="id337101520"><date>(01-01-2023)</date>
<title>EXAM Form 8839 Qualified Adoption Expenses</title>
<para>Form 8839 requires the Exam function to enter the classification code from the Exam classifiers. Rejects units are required to have 3 designated Exam boxes in the Rejects units for:<bulletlist>
<li>EXAM-Code &amp; Edit Form 8839.</li>
<li>EXAM-Form 8839 Correspondence review.</li>
<li>EXAM-Form 8839 Classified Coded.</li>
</bulletlist></para>
<para>The Exam classifiers will review the correspondence received for the Qualified Adoption Expenses in the Rejects units. No live work will leave the area. The meaning of Exam’s classifiers codes are:<bulletlist>
<li>0-zero no support is attached.</li>
<li>1-all support is attached.</li>
<li>2-support does not meet the requirements.</li>
</bulletlist>The Supporting Documentation Indicator is edited in the right margin under Part I of Form 8839. Ensure the codes has been entered in Field 38SDI for supporting documentation. Continue processing the return following <citation type="IRM">IRM 3.12.3</citation> Error Code 294 procedures. For No Replies, disallow the credit amount and assign TPNC 255.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100368"><date>(01-01-2026)</date>
<title>Entity Control</title>
<para>Documents with the following conditions will be routed to Entity Control Unit if research is unsuccessful: <alphalist>
<li>SSN is missing or mismatch.</li>
<li>SSN is invalid and the invalid segment of Master File has a different taxpayer.</li>
<li>SSN is <emphasis type="b">applied for</emphasis>. <note notetype="note">For IMF, correspondence is required unless <emphasis type="b">none</emphasis> or <emphasis type="b">applied for</emphasis> is indicated on the document.</note></li>
<li>EIN is needed in order to process the Schedule H.</li>
</alphalist></para>
<para>ERS documents are suspended with Action Code 320 when sending documents to Entity. Action Code 320 has an automatic 10 suspense period.<note>If the suspense period has expired and Rejects has not received the return back from Entity, weekly follow-up with Entity is required.</note> </para>
<para>When the document is returned from Entity, enter the new TIN and correct the name line if edited before clearing the return.</para>
<para>If research determines the return will be routed to ITIN, attach Form 4227. Check the "Reject Correction box", "Other" box under reason, and notate “Delete DLN and route to ITIN” in the Other (explain) box. </para>
</subsection2>
<subsection2 id="id337100369"><date>(05-03-2024)</date>
<title>Manual Refund</title>
<para>A manual refund is a refund that is not generated through normal Master File processing, bypassing all systemic safeguards. For this reason, caution must be used when issuing manual refunds. Manual refunds are requested on Form 5792, Request for IDRS Generated Refund, or Form 3753, Manual Refund Posting Voucher. <note><emphasis type="b">Form 3753 must be used when issuing a manual refund on a return requesting direct deposit</emphasis>.</note><bulletlist>
<li>Both Form 3753 and Form 5792 <emphasis type="b">must be accessed through IAT</emphasis> via the Manual Refund Tool. The use of IAT is <emphasis type="b">mandatory</emphasis> to prevent duplicate refunds. The Manual Refund Tool assists the TE with processing a Manual Refund case. It conducts preliminary research and will auto-fill portions of Form 5792 and Form 3753. <note>IDRS input of CC RFUND is no longer an option</note></li>
</bulletlist></para>
<para>Expedite processing prior to the end of the calendar year, in order to reduce the number of manual refunds required. <note notetype="caution"><emphasis type="b">Prior to releasing the Manual Refund, ensure all returns suspended to Entity has 10 days to review the return</emphasis>.</note><bulletlist>
<li>MFREQ C the accounts to verify any credits on an end of year Manual Refunds.</li>
</bulletlist></para>
<para><emphasis type="b">Section 965 Returns</emphasis> - Extra care must be utilized when issuing manual refunds on Section 965 returns. The only time the taxpayer will be entitled to the refund requested is when the <emphasis type="b">refund amount exceeds the deferred tax amount.</emphasis> If the refund requested exceeds the deferred tax amount, then the taxpayer is entitled to refund for difference between deferred tax and overpayment and not the entire refund amount requested. <bulletlist>
<li>Example 1: Taxpayer requests refund of $1,000. The taxpayer’s deferred Section 965 tax is $800. The refund amount must be reduced to $200.</li>
<li>Example 2: Taxpayer requests refund of $1,000. The taxpayer’s deferred Section 965 tax is $1,500. The refund amount must be reduced to zero (0).</li>
</bulletlist></para>
<para>ERS is instructed to use Suspense Code 341 to suspend all refunds of $100 million or more as manual refunds. IDRS can process returns under $100 million automatically. A manual refund will not need to be issued unless the return meets other manual refund criteria (for example: International decedent taxpayer, the 45-day interest free period is in jeopardy, the taxpayer filed Form 1040-NR and requested the refund check to be mailed to an alternate address, refund is more than $100 million, etc.). Verify all credits using IDRS CC IRPTRO, IMFOL, and TXMOD before issuing a manual refund.<alphalist>
<li>Verify estimated payments applied from last year’s return and amount(s) paid with request for extension. If IMFOL shows these totals to be greater than the amount being requested to be refunded, Exam approval is <emphasis type="b">not</emphasis> necessary. Clear Error Code 372.</li>
<li>If income and withholding can be verified per CC IRPTRO, then the returns will not be referred to Exam for approval. Refer returns to Exam if unable to verify the documents on CC IRPTRO or IRPTRO contains the statement: <restrict><emphasis type="q">≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</emphasis></restrict>. <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></li>
</alphalist></para>
<para>All Form 1040-NR with a refund supported by a Form 1042-S will have that portion of the refund systemically frozen for up to 154 days. The 154-day freeze period begins from the later of the return due date or the date the complete return was actually filed.<alphalist>
<li>Follow normal manual refund procedures but ensure that credits for Form 1042-S (or signed Competent Authority Letter), Form 8288-A and/or Form 8805 are calculated using refund interest free period of 180 days of interest computations. If the refund is supported by Form 1042-S (partially or in full), process the return normally. <note notetype="caution">If refund is more than <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> and the case is in interest jeopardy, do a manual refund</note></li>
</alphalist></para>
<para>The more common reasons to issue a manual refund are:<bulletlist>
<li>A hardship situation necessitates a faster refund (TAS cases) TAS will prepare their own manual refunds. Rejects will input CCC <emphasis type="b">O</emphasis> and process only the refund return.</li>
<li>The 45-day interest free period is in jeopardy and the refund is $25,000 or more.</li>
<li>Overpayments of less than $1.00 when requested by the taxpayer.</li>
<li>International decedent returns may have an international address that requires the second name line to be used for the address. The second name line would not be available for the surviving spouse or personal representative. See <citation type="IRM">IRM 3.22.3.197.6</citation></li>
<li>International taxpayer request check mailed to an alternate address on indicated on Form 1040-NR. See <citation type="IRM">IRM 3.22.3.196.7</citation></li>
<li>The refund is more than $100 million.<note><emphasis type="b">Do Not issue</emphasis> manual refunds on amended returns or from taxpayers who have never filed a return before and are filing a return for the first-time or No Reply returns. Do not issue manual refund on returns that are less than 20 days old, and the refund is less than $100 million. Close control on TXMOD and leave history explaining why manual refund was not issued.</note><note><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡<citation type="IRM">≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</citation>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡<citation type="IRM">≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</citation>≡</restrict></note></li>
</bulletlist></para>
<para>Do <emphasis type="b">not</emphasis> issue a Manual Refund if any of the following conditions exists:<alphalist>
<li>Unallowable conditions are present.</li>
<li>Missing or photocopy signature. SSPND 215 for original signature. When original signature received follow Manual Refund procedures.</li>
<li>Taxpayer completed the Direct Deposit Section (Section 06) of the return.</li>
<li>Substantiation of payments is missing (e.g., W-2, 100, 8288-A, 1042-S, etc.)</li>
<li>Return is balance due return or taxpayer is applying their total refund amount to the next tax year (i.e., credit election to the next tax year).</li>
<li>Taxpayer has been assigned an IRSN. (IRSN begins with 9 and the two middle digits are other than 70-88; 90-92; 94-99).</li>
<li>Never issue a manual refund on any original return marked<emphasis type="b"> Protective Claim</emphasis>. These returns will not be processed, RJECT 640 the DLN and route the return to Accounts Management.<note>Any return hand carried by a TS liaison for Taxpayer Advocate Service (TAS) as a Manual Refund will be processed by a Lead Tax Examiner or a designated Tax Examiner.</note></li>
</alphalist></para>
<para>Contact RICS if all of the following exist:<bulletlist>
<li>The Return is requesting a refund of less than $100 million.<note>If there is a TC 971 AC 711 on the account and NO TC 973, this indicates there is an unprocessable condition in SP that must be resolved prior to RICS resolution of the account.</note></li>
<li>If there is a closed IDRS control originally assigned to 1381400000 with activity of <emphasis type="b">ISSUELTR</emphasis> along with a new IDRS control originally assigned to 1481055555 with activity of either <emphasis type="b">FXMMDDYYYY</emphasis> or <emphasis type="b">CRMMDDYYYY</emphasis>.</li>
<li>If it has been 15 days past the response received date (MMDDYYYY).</li>
</bulletlist></para>
<para>If the withholding is <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> attach Form 4227 and suspend them for Exam review. Some fraudulent returns have Form 1099-OID and some have Form 1096. Other false financial instruments may be filed in the place of or in addition to the Form 1099-OID such as Form 2439, promissory notes, bonds, sight drafts etc. Any return with Form 1099-OID <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> These refunds have to be generated systemically.</para>
<para>If Form 1099-OID or Form 1099-MISC is received with a request for a Manual Refund, follow instructions in <citation type="IRM">IRM 3.17.79.3.2.1.</citation></para>
<para>ERS/Rejects will not re-issue returned or undeliverable manual refund unless the IRS caused the refund to be returned.</para>
<para>All manual refunds will be reviewed by an Authorizing Official prior to sending the return to Accounting. In addition, all manual refunds for $100 million or more will be reviewed by a lead prior to being sent to the Authorizing Official.</para>
<para>If a manual refund must be issued and the return was suspended with Action Code 341, continue processing the return. <bulletlist>
<li>The return must be complete with all required forms, schedules and information documents. Original signatures are required</li>
<li> Correspond with the taxpayer for all missing documentation.</li>
<li> If taxpayer does not respond or provide the necessary documentation, continue processing the return with CCC<emphasis type="b"> 3</emphasis> without issuing a manual refund.</li>
<li>If the return is a decedent return, ensure that the name line is edited correctly.</li>
<li>Verify that CCC <emphasis type="b">O</emphasis> has been entered and CCC <emphasis type="b">Y</emphasis> and <emphasis type="b">LW</emphasis> are removed. After all corrections have been made to Section 01, print the Section 01 screen and include this print in the Manual Refund packet to be sent to Accounting. </li>
<li>Math verify the return. Field 03BDR will be removed, print the screen showing CCC <emphasis type="b">O</emphasis> and the computer underprint of the refund amount and include this print in the Manual Refund packet for Accounting. Enter the taxpayer's amount of refund in field 03BDR and transmit. <note><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡<emphasis type="b">≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</emphasis>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></note></li>
<li>Verify all credits.</li>
<li>If credits have been transferred into the module, check the from module for other transactions, such as extensions and payments, that may also need to be transferred.</li>
<li>Research the account using IDRS before issuing manual refunds, (e.g., IMFOL, BMFOL, MFTRA, TXMOD) use Document 6209 to verify freeze conditions and Criminal Investigation or Examination codes (e.g., TC(s) 914, 916, 918, or 810). </li>
<li>Use CC IRPTR <emphasis type="b">O</emphasis> to verify all withholding, if IRPTRO does not show the credit, suspend the return for Exam review. Do not issue a manual refund. Exam will determine how to freeze the credits and if they want to select the return for an audit, prior to sending it back for completion of processing. In the case of ID theft, they may decide the return must not be processed.<note>IRPTR is updated in mid-February with the previous year's data and shows all withholding types.</note></li>
<li>Use CC IMFOL to research for any outstanding liability on another tax period.</li>
<li>If the account is controlled by another IRS employee, contact them prior to issuing a manual refund. </li>
<li>Verify that the Refund Statute Expiration date (RSED) has not expired. </li>
<li>If the return is a decedent return, ensure all CCC are included and the name line is edited correctly.</li>
<li>If the return is a MeF return, ensure all screen prints are copied. </li>
<li>Copy pages 1 and 2 of the return. Be sure that both the original return and the copy show CCC <emphasis type="b">O</emphasis> coded. Copy all Forms W-2 and other forms showing withholding, Form 1310 or a Court Certificate, and/or any notation asking that the refund be sent to another address. If the Manual Refund is for an International Minor Taxpayer, copy Form 8615 or other form showing the parent’s name. If there is a math error of $100 or more, show working trail on the copy (but NOT on the original return). <emphasis type="b">Include these prints in the Manual Refund packet for Accounting.</emphasis></li>
</bulletlist></para>
<para>Use IDRS to ensure no other site or employee has issued a duplicate refund (TC 840). Also check for TC 971 AC 664 as an indication Form 3753 (Manual Refund) has been issued or that a refund has not already generated. (TC 846). </para>
<para>When addressing a case that involves looking for a refund issuance, follow the chart below for guidelines: <table frame="all" summary="IMF accounts addressing refunds" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="col3" colwidth="33*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If</emphasis></entry>
<entry valign="top"><emphasis type="b">And</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>A] The account has TC 846 posted,</entry>
<entry/>
<entry>A NOREF or HAL request cannot be initiated on an IMF account. Erroneous Refund Procedures will be followed.</entry>
</row>
<row>
<entry>B] The account has TC 570 with blocking series <emphasis type="b">55555</emphasis></entry>
<entry>A TC 971 AC 805 is also posted on the module indicating a refund transcript has generated,</entry>
<entry><steplist>
<li>A TC 570 can be input up to 3 business days after the systemically generated TC 570 transaction date (up to 6 PM local time) to prevent the refund transaction from generating.</li>
<li>A NOREFP can be input on the third business day after 6 PM or the fourth business day before 6 PM local from the systemically generated TC 570 transaction date to request IMF reverse the refund and stop the refund information from going to BFS.</li>
</steplist></entry>
</row>
<row>
<entry>C] The account has TC 570 with blocking series <emphasis type="b">55555</emphasis></entry>
<entry>A TC 971 AC 804 is also posted on the module indicating a CP 12, or 24 has been issued,</entry>
<entry><steplist>
<li>A TC 570 can be input up through 6 PM the following Wednesday (6 calendar days after the systemically generated TC 570 transaction date to prevent the refund transaction from generating).</li>
<li>A NOREFP can be input on the Wednesday after PM or Thursday before PM local to request IMF reverse the refund and stop the refund information from going to BFS.</li>
</steplist></entry>
</row>
</tbody>
</tgroup>
</table><note>The NOREFP request will be processed by IMF. The account will reflect a TC 841 on IMFOL the next processing day after the NOREFP is processed by IMF. Weekly taxpayer accounts will reflect the TC 841 one cycle after the TC 846. Daily taxpayer accounts will reflect the TC 841 the next business processing day after the TC 846. </note></para>
<para>To determine whether the 45-day interest free period has been met on a refund of tax, consider these three dates: <bulletlist>
<li>Normal due date</li>
<li>Return received date</li>
<li>Return process date (RPD) if present</li>
</bulletlist> If the refund schedule date (when the refund is certified by Accounting) is not on or before that date, interest must be allowed on the refund. Form 3753 must be processed no later than the 43rd day. Form 5792 must be processed no later than the 42nd day when the 43rd day is a workday. Consider the normal due date, return received date and return processing date before plus 45 calendar days when issuing a manual refund.</para>
<para> If the Refund Statute Expiration Date (RSED) or Assessment Statute Expiration Date (ASED) has expired or the return is unsigned, do NOT issue a manual refund. The ASED generally expires three years from the due date of the return or when the return is filed, whichever is later. The RSED generally expires three years from the due date of the return. These dates are shown on IDRS. Remove any CCC <emphasis type="b">O</emphasis> unless a manual refund has already been issued and process the return. The Clear Code Field will only be used by Suspense TEs. If a previous TC 840 has posted to the same module, stop processing and hold document until reject sub-TC 840 posts, to prevent erroneous refund. </para>
<para>Research for pending refunds, pending payments and credits before issuing a manual refund using IDRS CC IMFOL and/or TXMOD. Also, <emphasis type="b">be sure to check the other campus's ERINV via CMODE,</emphasis> if they have the same return in inventory do not issue a manual refund without coordinating with them. <emphasis type="b">Read the TXMOD history</emphasis>. If TC 840, F5792 Prep, or F3753 Prep is part of the history, do not issue a refund. See your Lead or Manager. Also, ensure all IMF MeF work has been correctly reviewed before accessing CC CMODE for the examiner to transfer access from one IDRS database to another. </para>
<para>Review the Freeze chart below before taking action.</para>
<table frame="all" id="id337101284" summary="Review freeze codes before issuing manual refund and send to ICT or IVO" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">If TXMOD shows</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>C- Freeze</entry>
<entry>Issue refund</entry>
</row>
<row>
<entry>-H Freeze</entry>
<entry>Issue refund</entry>
</row>
<row>
<entry>-K Freeze</entry>
<entry>Issue refund only if no open Exam issues </entry>
</row>
<row>
<entry>-L Freeze</entry>
<entry>Contact Compliance if AIMS Status Code is other than 00 through 06 or 08</entry>
</row>
<row>
<entry>N- Freeze</entry>
<entry>Issue refund</entry>
</row>
<row>
<entry>-R Freeze</entry>
<entry>Issue refund unless indication of CI or RIVO involvement or if there is a TC 570 with blocking series 55555, 55514, or 55528</entry>
</row>
<row>
<entry>-S Freeze</entry>
<entry>Issue refund</entry>
</row>
<row>
<entry>T- Freeze</entry>
<entry>Issue refund</entry>
</row>
<row>
<entry>-U Freeze</entry>
<entry>Contact Erroneous Refund Team in Accounting </entry>
</row>
<row>
<entry>X- Freeze</entry>
<entry>Issue refund unless there is a TC 971 AC 664 posted on the IMFOLT or TXMOD within 6 cycles </entry>
</row>
<row>
<entry>-Z or Z- Freeze </entry>
<entry>Contact CI</entry>
</row>
</tbody>
</tgroup>
</table>
<para>For a complete listing of freeze codes see Document 6209. If any other freeze codes are present, do not issue a manual refund. Process the return normally, without the CCC <emphasis type="b">O</emphasis>.</para>
<para>Verify that the module does not contain -L or -Z freeze. If a "-L" freeze (AIMS indicator) is present on a module, research the account for the presence of a history item or activity code "MAAS (MMDDYYYY)”. This indicates that a "quick assessment" has been requested and that a new liability may be in the process of posting. If the assessment (TC 300 for other than .00) has not posted, contact Exam for the amount of the additional liability and where the refund must be applied. If other freeze codes are listed with the indication of the L freeze code, the -L takes priority over the other freeze codes. Confirm the module does not contain a Z freeze, the Z freezes the entire account. Obtain written approval to issue manual refund for audit trail purposes. An e-mail approving the manual refund with the correct DLN must be attached to the manual refund package and notated in remarks. Ensure secure e-mail is used. </para>
<para>Ensure that CCC <emphasis type="b">O</emphasis> has been entered on the return and on the record. Take whatever corrective actions are necessary and continue processing the return.<emphasis type="b"> If there is a previous TC 840 on the module, hold the return until the new manual refund (TC 840) posts, then continue processing.</emphasis></para>
<para>Obtain written approvals to issue manual refund, for audit trail purposes. An e-mail approving a manual refund on DLN XXXXX-XXX-XXXXX-XX must be attached to the manual refund package and notated in the remarks. (Use secure e-mail for all emails) If no response from the other area is received in 2 business days, telephone the unit. Do not issue the manual refund until approval is received.</para>
<para>Form 5792 and Form 3753 must be accessed through IDAP/IAT via the Manual Refund Tool. The use of IDAP/IAT is mandatory unless IDAP/IAT is down, then the refund will be hand prepared on Forms 3753 and/or 5792. The Manual Refund Tool assists the TE with processing a Manual Refund case. It conducts research and will auto-fill portions of Form 5792 and Form 3753. Start IDAP while IDRS is on the TXMOD screen, it will also input CC RFUNDR when appropriate. If the taxpayer has requested a Direct Deposit, copy the return pages showing the banking information and forward to the Accounting function along with the refund document Form 3753. <emphasis type="b">Do not </emphasis>allow a paper check to go to the taxpayer. Initiators of manual refunds are responsible for daily monitoring of accounts using command code (CC) IMFOL/REMRQ/Universal IDRS/TXMOD until the TC 840 is posted to Master File, and the account is in <emphasis type="b">0</emphasis> balance. </para>
<para>A copy of the return, ERS screens showing CCC <emphasis type="b">O</emphasis> and prints of the necessary IDRS research must accompany the request for manual refund (Form 5792 or 3753) to the Accounting Function. Accounting will input IDRS refund with CC RFUND. Check with the manual Refund Unit for their daily cut off time. <bulletlist>
<li>On the same day, the Accounting Operation will release the refund with CC REFAP.</li>
<li>On the following day, they will associate the case with Form 5147, IDRS Transaction Record.</li>
<li>When the TC 840 is pending, ensure that the CCC <emphasis type="b">O</emphasis> has been entered on the return and on the record.</li>
<li>If the manual refund will not be issued, remove CCC <emphasis type="b">O</emphasis> and continue processing return.</li>
<li> DO NOT HOLD return.</li>
</bulletlist></para>
<para><emphasis type="b">All manual refunds must have an open control base</emphasis> established by ERS/Rejects or Accounting will reject them back to the originators. Areas initiating manual refunds are responsible for monitoring the accounts, with the IAT EMT Tool until the TC 840 has posted. Follow <seealso idref="id337101032">IRM 3.12.37.15.5.2</seealso> for monitoring manual refund instructions. It may take 2–4 weeks for the TC 840 to post when issued via Form 3753, which is being processed on an expedite cycle.<bulletlist>
<li>IDRS CC IMFOL will provide the most up to date posted refund information.</li>
<li>Monitoring is essential to avoid the issuance of duplicate/erroneous refund (TC 840 or TC 846).</li>
<li>Immediately contact the campus Manual Refund function to determine whether the TC 840 can be stopped.</li>
<li>Initiators must research and intercept duplicate refunds by using the IAT NOREF Tool no later than the established cut off times.</li>
</bulletlist></para>
<para>Prepare Form 5792 to initiate a manual refund for <emphasis type="b">less than $100 million</emphasis>, input history item F5792 Prep, and open a control base using the ERS/Rejects group number. Verify and edit, if necessary, the auto-fill fields. The DLN will not auto-fill because the return hasn’t been processed yet. Type in the DLN of return. If the entity portion includes a foreign address, both the city and/or country are placed in the city field with a space placed between the city and country and a comma and period after the last letter in the city field and it will appear on the Form 5792. <emphasis type="b"><emphasis> REMINDER</emphasis></emphasis>: All refund returns for <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> are to be suspended for Exam review, prior to preparing any manual refund.</para>
<para>Prepare Form 3753 to initiate a <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict>, input history item F3753Prep, and open a control base using the ERS/Rejects group number.<note>A <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> will have to be split between a Form 3753 and either another Form 3753 or Form 5792, depending upon the total amount of the refund.</note></para>
<para>Verify and edit, if necessary, the auto-fill fields. The DLN will not auto-fill because the return hasn’t been processed yet. Type in the DLN of return. If the entity portion includes a foreign address, both the city and/or country are placed in the city field with a space placed between the city and country and a comma and period after the last letter in the city field and it will appear on the Form 3753. <note>For additional information refer to <citation type="IRM">IRM 3.17.79.3.2</citation><emphasis type="b"> Accounting and Data Control</emphasis> - Accounting Refund Transactions and <citation type="IRM">IRM 21.4.4.4</citation> <emphasis type="b">Refund inquiries - Manual Refunds. </emphasis></note></para>
<para>ITM course 30914, <emphasis type="b">Manual Refunds</emphasis> <emphasis type="b">training must be completed annually within the period of January 1 to February 1</emphasis> or prior to being assigned Integrated Data Retrieval System (IDRS) command code(s) RFUND, REFAP or a manual refund profile restriction (RSTRK (M)).</para>
<para>ITM course 42841, <emphasis type="b">Monitoring Manual Refunds</emphasis> must be taken by managers, leads and all employees required to monitor manual refunds no later than February 1st.<note>Timely completion of all training courses is a requirement. If not, the refund command codes will be removed.</note></para>
<subsection3 id="id337101275"><date>(11-10-2021)</date>
<title>Refund Credit Interest</title>
<para>Refund credit interest is the interest that we owe the taxpayer for not processing the refund timely. It increases the amount of the total refund.<note>The allowance of interest is authorized only on overpayments. There is no overpayment until the entire tax liability (including any interest, additions to the tax, or additional amount) is satisfied.</note></para>
<para>To determine whether the 45-day interest free period has been met on a refund of overpayment, consider these three dates:<bulletlist>
<li>Normal due date</li>
<li>Return received date</li>
<li>Return Processable Date (RPD), if present<br/>To the latest of these three dates, add 45 calendar days. If the refund schedule date (when the refund is certified by Accounting) is not on or before that date, interest must be allowed on the refund. Form 3753 must be processed no later than the 43rd day. Form 5792 must be processed no later than the 42nd day. Form 5792 must be processed no later than the 42nd day when the 43rd day is a workday. <br/>Accounting must transmit the authorization to pay the refund to the Bureau of Fiscal Services (BFS) and BFS actually prepares the check and mails it or processes the direct deposits or Fedwire transfers.<note>An alert is issued in January of each year issuing the Accelerated Refund Cycle Charts. The accelerated refund cycles are also in the <citation type="IRM">IRM 3.0.275.8.3(2)</citation>, <emphasis type="b">Business Results Measures for Submission Processing Functions.</emphasis></note></li>
</bulletlist></para>
<para>Interest may be computed from<emphasis type="b"> other than</emphasis> the availability date of the overpayment when the original tax return was filed late, or in unprocessible form. When information needed to make a return processible is not received, or the reply is incomplete, no interest is allowed. See <citation type="IRM">IRM 20.2.4.4</citation> <emphasis type="b">Delinquent Returns</emphasis>, and <citation type="IRM">IRM 20.2.4.5</citation>, <emphasis type="b">Unprocessible Returns</emphasis>.</para>
</subsection3>
<subsection3 id="id337101032"><date>(01-01-2023)</date>
<title>Monitoring Manual Refunds</title>
<para>After preparing <emphasis type="b">all</emphasis> manual refunds, take the following actions to prevent duplicate refunds: <bulletlist>
<li>Establish a new control on IDRS. Use the Reject's team number followed by the five digits designated for Manual Refunds. </li>
<li>Each site will designate a unique IDRS number not being used by the Reject team. <emphasis type="b">Example</emphasis>: 0345200000</li>
</bulletlist><bulletlist>
<li>Use M status, activity code WT840, category code MISC, and the current date as the received date.</li>
</bulletlist></para>
<para>Print the Manual Refund form, attach necessary documentation and forward the Manual Refund documentation to the technical lead or designated individual for review. </para>
<para>They will review the manual refund form, the attached documentation, and using the IAT Erroneous Manual Refund tool (EMT)/Case Monitoring Tool, review the information on IDRS. Utilization of the tool by the manager, lead or designated individual will create an active monitoring file for the team. This file is automatically stored in the C drive of their computer.<note>Ensure the open control has been established prior to sending the refund for review.</note></para>
<para>After completion of the review, the Manual Refund documentation will be forwarded to the authorized official in ERS/Rejects for review and signature. Refer to <citation type="IRM">IRM 3.17.79.3.5</citation>, Employees Authorized to Sign Requests for Refunds. </para>
<para>The documentation will be returned to the T/E for the input of CC RFUND.</para>
<para>Anytime a manual refund is created within Rejects, the lead, employee, or designated individual will monitor the account weekly until the TC 840 posts, using the EMT Tool. Use of the EMT Case Monitoring Tool is <emphasis type="b">mandatory</emphasis> for documenting the monitoring process. If there are no open manual refunds within the team (i.e., there are no cases within the active EMT file), the designated reviewer is not required to run the tool daily. </para>
<para>During the monitoring process the account must be reviewed thoroughly to prevent erroneous refunds:<table frame="all" id="id337101285" summary="Monitor for TC846 " width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>A TC 846 or a subsequent TC 840 appears after initiating the manual refund due to an input error and a duplicate erroneous refund situation is created, </entry>
<entry><bulletlist>
<li>Contact the area that input the adjustment and request that the adjustment be deleted (DQd through CC TERUP Input), or</li>
<li>Input CC NOREF to stop the refund (TC846 or TC 840). Refer to <citation type="IRM">IRM 21.4.1.5.10</citation>, Refund Intercept CC NOREF and <citation type="IRM">IRM 21.4.1.5.11</citation>, IRS Holds Automated Listing (HAL)</li>
</bulletlist></entry>
</row>
<row>
<entry>A pending credit transfer without a TC 570, </entry>
<entry><bulletlist>
<li>Contact the area that input the credit transfer and request that the credit transfer be deleted (DQd through CC TERUP input) or </li>
<li>Input CC NOREF to stop the refund (TC 846 or TC 840). Refer to <citation type="IRM">IRM 21.4.1.5.10</citation>, Refund Intercept CC NOREF and <citation type="IRM">IRM 21.4.1.5.11</citation>, IRS Holds Automated Listing (HAL)</li>
</bulletlist></entry>
</row>
</tbody>
</tgroup>
</table><bulletlist>
<li>When the Accounting Function processes a Form 3753, Manual Refund Posting Voucher, they input a history item, a control base, and TC 971 AC 664 on the account.<note notetype="caution"> If a TC 971 AC 664 is on the account and a TC 840 is showing as Rejected (RJ), Unpostable (UP), or Resequencing (RS) <emphasis type="b">do not prepare another refund</emphasis>. The refund has been issued. </note></li>
</bulletlist></para>
<para>When the TC 840 posts, the following actions will be taken:<alphalist>
<li>The EMT Tool will delete the module from the active monitoring screen and will place it in the archived file located on the reviewer’s C drive on their computer. The tool will notate “TC 840 Posted” and “No E/R” if no erroneous refund was issued. This file is maintained for 90 days.<note>If the TC 840 has posted but the adjustment transaction associated with the manual refund is still pending, the reviewer will notate “adj pending” and continue monitoring for the adjustment to post. The EMT tool will not move the module from the active monitoring file to the archive file until the adjustment has posted.</note><note notetype="caution">If a record doesn’t get removed from the active file and placed in the archive file, it may be due to incorrect information loaded into the tool, e.g., refund amount or refund date. Once the information is correct on the EMT tool the case record will move to the archive file.</note></li>
<li>Indicate if an erroneous refund was issued. If so, notate <emphasis type="b">E/R</emphasis> and corrective actions taken to resolve the erroneous refund, in the EMT tool. <note>If a duplicate refund was issued, a Form 14165, Erroneous TC 840 / 846 Report <emphasis type="b">MUST</emphasis> be completed and sent to Accounting, see <citation type="IRM">IRM 21.4.5.5.6</citation> <emphasis type="b">Erroneous TC 840/846 Report.</emphasis> </note></li>
<li>Once the module has been moved from the active file to the archive file, as indicated by the posting of the TC 840 and any adjustment transaction, close the control base with the control activity in IDRS to “840 Posted” or “TC840PSTD”</li>
<li>Close the control base.</li>
</alphalist></para>
<para>The lead, or designated individual, will export the EMT active case monitoring file each week after they have performed their review (only when there are manual refunds to review). The exported EMT active case file and the EMT archive case file will be sent to the manager/designated individual via encrypted secure e-mail each day. <note>Refer to the IAT Job Aid EMT Section 5.1</note>, Exporting Cases, for step-by-step instructions on exporting and emailing the file to the manager. </para>
<para> Managerial review of manual refund monitoring and documentation is required. Managers must complete ALL actions below:<note>The person conducting the managerial review cannot be the same person who documented the refund transactions above.</note><alphalist>
<li>Import the EMT active file and then the EMT archive file from the secure e-mail.<note>Refer to the IAT website EMT Job Aid Section 5.2, Loading Cases, for step-by-step instructions.</note></li>
<li>Every week, notate on the Manger's Monitoring Confirmation Log, whether the monitoring of manual refunds by the lead or designated individual was performed and sign the confirmation log. The history area for each module will indicate each day the tool was run and the SEID of the person who performed the monitoring. Check the Yes box if the review was performed. Check the “No” box if the review as not performed and provide an explanation in the note’s column. If a review was not required provide an explanation in the note’s column. <note>Managers can save Form 14696, Manager’s Monitoring Confirmation Log, by individual quarters to minimize the size of the log file. To save the log, print the pages for the quarter as an Adobe PDF file and save.</note></li>
<li>Sign the confirmation log</li>
<li>Keep the Manager's Monitoring Confirmation Log for a period of 90 days. The confirmation log must be available to review by upper management or outside auditors, e.g., TIGTA. </li>
<li>Complete a 100% review of all accounts each week, through the EMT by accessing IDRS to verify the notations are accurate. The review needs to be both the active file and the archive file.</li>
<li>Indicate managerial review in the History section of EMT for each case reviewed by clicking on the Edit button. The EMT tool will store the monitoring for a period of 90 days.</li>
</alphalist><note>For additional information refer to <citation type="IRM">IRM 3.17.79.3.2</citation>, Accounting and Data Control - Accounting Refund Transactions and <citation type="IRM">IRM 21.4.4.5</citation>, Refund Inquiries - Manual Refunds.</note></para>
</subsection3>
<subsection3 id="id337101396"><date>(01-01-2023)</date>
<title>Refunds for less than $1 when requested by taxpayer</title>
<para>Overpayments of less than $1 are systemically cleared from the module by the posting of a TC 386. If a taxpayer requests a refund of an overpayment of less than $1, use the following procedures to reverse the TC 386 and force the generation of a systemic refund:<alphalist>
<li>Input a TC 971 action code (AC) 652 using CC REQ77. Refer to <citation type="IRM">IRM 2.4.19</citation> <emphasis type="b">Command Codes REQ77, REM77, FRM7A</emphasis></li>
<li>Enter the transaction date of the TC 386 on line 3 positions 56 - 63, &lt;TRANS-DT&gt;.</li>
</alphalist></para>
<para>The above actions will post a TC 387, reversing the TC 386, and will generate a systemic refund (TC 846).</para>
</subsection3>
<subsection3 id="id337100542"><date>(04-26-2022)</date>
<title>IMF Accounts Over 999 Million Dollars</title>
<para><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> See your Work Leader before routing returns to ensure the dollar amount is correct, enter RJECT 620. <note><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></note></para>
<para><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict><bulletlist>
<li><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </li>
<li><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </li>
<li><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </li>
<li><restrict>≡ ≡ ≡ ≡ ≡</restrict> </li>
<li><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </li>
</bulletlist></para>
<para><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict></para>
<para><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </para>
<para><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </para>
<para>Overnight these returns to: <br/>Kansas City Submission Processing Campus<br/>333 W. Pershing Road Stop 6263 P6 ANMF Team<br/>Kansas City, MO 64108</para>
<para>The Accounting Function will process the returns to Non-Master File. RACS will receive these returns and input Form 813 information through the Form 813 Block Control screen.</para>
<para>Form 1040 will be numbered as follows: <bulletlist>
<li>Tax Class 6.</li>
<li>Document Code 10.</li>
<li>Blocking Series: 000–099 non-remittance, 900–919 with remittance. </li>
<li>MFT 20.</li>
<li>Abstract Number 004.</li>
</bulletlist></para>
<para>ANMF will establish an account on the Automated Non-Master File system through the Original Assessment Screen. If it is determined that the return is an amended return, void the DLN and renumber as follows: <bulletlist>
<li>Tax Class 6.</li>
<li>Document Code 54.</li>
<li>Blocking Series: 000–999.</li>
<li>MFT 20.</li>
<li>Abstract Number 004.</li>
</bulletlist></para>
<para>Refunds — All refunds of <restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> must be cleared by Examination Classification prior to routing to Accounting.</para>
<para>Balance Due —research Master File to ensure that all payments/credits have been transferred to ANMF. Standard billing will apply.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100373"><date>(01-01-2023)</date>
<title>Credit Transfers</title>
<para>A credit transfer moves a payment or credit from one account to another, or reverses credits previously applied. Credit transfer adjustments will not be input if another employee or organization has an open control base. Contact the person or organization with the open control base. DO NOT reassign or change the control base until contact has been made. </para>
<para>Credit Transfers are performed for various reasons: <bulletlist>
<li>Incorrect tax period</li>
<li>Incorrect SSN</li>
<li>Incorrect MFT</li>
<li>Incorrect payment</li>
<li>Incorrect dates</li>
</bulletlist></para>
<para>Use of IAT is <emphasis type="b">mandatory</emphasis> for all credit transfers. IAT eliminates the need to hold cases by detecting potential unpostable conditions. For additional IAT information, refer to the IAT website. This tool provides a list of transferable payments, auto-fills reversal transaction codes (TCs), performs unpostable checks, and ensures use of appropriate codes, amounts, and dates to prevent unpostable conditions. <note notetype="exception">IDRS will be used when IAT is unavailable.</note></para>
<para>Credit transfers will not be done before the TC 610 has posted to the module. On IMF Returns, if extensive research indicates that an account is not on Master File, input a TC 000 to establish the taxpayer's account. Ensure a working trail has been input showing TC 000 or TC 013 on the document.</para>
<para>Credit transfers may be routed to Accounting or completed in the Reject/Suspense function depending on local procedures.</para>
<para>A Short Period Return with credits will be routed to Accounting to verify that all credits have been transferred to the proper period. Notate on Form 4227 <emphasis type="b">Short Period with Credits</emphasis>.</para>
<para>Whenever credits are transferred by the Rejects functions, follow the procedures in <citation type="IRM">IRM 3.24.21</citation>. The following transfers can be completed by the Reject/Suspense Units: <alphalist>
<li>Multiple period returns which require the payment to be split.</li>
<li>Transfers to Unidentified.</li>
<li>Returns being posted to a different SSN, MFT, or Tax Period and the associated payment has already posted to an incorrect module.<note>If a return is received with a statement from the taxpayer indicating that the <emphasis type="b">Credit Elect Payment (line 65)</emphasis> must be applied to the spouses account, research CC TXMOD for posted payments on the account before inputting the credit transfer. </note></li>
</alphalist></para>
<para>Never do a credit transfer when a <emphasis type="b">B-</emphasis> freeze code is present or if the payment is three years or older (expired RSED).</para>
<subsection3 id="id337100374"><date>(11-10-2021)</date>
<title>IAT Tool and Credit Transfers Procedures</title>
<para>The IAT tool <emphasis type="i"><emphasis type="b">must</emphasis></emphasis> be used for credit transfers. <note notetype="exception">If IAT is not available, then IDRS will be used</note></para>
<para>If the module where the payment is posted is present on IDRS use ADD24/ADD48 to request DRT24/DRT48 format screen.</para>
<para>If the module is not present, it can be created using MFREQ or ACTON. TXMOD or ACTON must precede ADD24/ADD48 and will generate the tax module into the top half of the DRT24/DRT48 screen. <alphalist>
<li>Overlay the top line of TXMOD where the credit is being moved (this will generate into the bottom half of the DRT24/DRT48 screen) with the TIN, MFT, Tax Period, and Name Control.</li>
<li>If the bottom half of DRT24/DRT48 is not on IDRS, an indicator must be used. Enter the indicator in the first position of the second line on the ADD24/ADD48 screen. Use an <emphasis type="b">A</emphasis> when the entity for the bottom half is not present on IDRS. Use an <emphasis type="b">@</emphasis> when the entity is present, but the module is not.</li>
</alphalist></para>
<para>Use ADC24/ADC48 in place of ADD24/ADD48 when the debit module is not present, but where you are moving the money to is present.</para>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337100381"><date>(01-01-2020)</date>
<title>Form 4028 and Form 4028A</title>
<para>This subsection of the manual lists the procedures to be followed for preparing Form 4028 and Form 4028A.</para>
<para>Information in this subsection includes the following: <bulletlist>
<li>General instructions</li>
<li>Preparation of Form 4028</li>
<li>Preparation of Form 4028A</li>
</bulletlist></para>
<subsection2 id="id337100382"><date>(01-01-2023)</date>
<title>General Instructions</title>
<para>The SCCF is automatically updated by the correction made on the reject register or ERS records in most cases.</para>
<para>Prepare Form 4028, Adjustment Record, whenever the SCCF has not been properly updated by the action on the reject register or ERS record. <alphalist>
<li>A document was rejected with CC RJECT 630.</li>
<li>A register was coded with Action Code 2-R.</li>
</alphalist></para>
<para>Prepare Form 4028A, Renumber Adjustment Record, whenever the SCCF has not been properly updated for a document that is being renumbered. <alphalist>
<li>A generated renumbered record was invalid on the SCCF and is resubmitted manually.</li>
<li>A record was renumbered to the incorrect DLN.</li>
</alphalist></para>
<para>Check SCCF and ERS 05–40 (Error Resolution Rejected Records List) or SCF11–46–CRL (Renumbered Transactions) to determine the correct SCCF adjustment to be made.</para>
</subsection2>
<subsection2 id="id337100383"><date>(01-01-2023)</date>
<title>Preparing Form 4028</title>
<para>Use the instructions in this subsection of the IRM to prepare Form 4028. </para>
<para>Enter the ABC or other designated control number.</para>
<para>Enter the adjustment <emphasis type="b">From</emphasis> and <emphasis type="b">To</emphasis> Code. The most common examples for rejects are shown on the <seealso idref="id337100482">Exhibit 3.12.37-13</seealso>. Codes 0–6 have standard meanings. <alphalist>
<li>When the <emphasis type="b">From Code</emphasis> is 7 or 8, both the <emphasis type="b">From Code</emphasis> and the <emphasis type="b">To Code</emphasis> have special meanings. These codes will only be used by Rejects for exceptional adjustments.</li>
<li>SCCF adjustments with the standard codes will transfer a balance (count and/or amount) from one status to another. For instance, Code 3–4 will transfer a balance from Error to Rejects and Code 1–5 would transfer a balance from BOBs to good tape.</li>
</alphalist></para>
<para>The reentered Source Code is needed only for establishing new DLNs for documents which have previously been unpostable or reprocessable. Use the code with adjustment From–To Code 0–0 only. <alphalist>
<li>Use Code <emphasis type="b">R</emphasis> for a document identified as a reprocessable on Form 3893. Also use Code <emphasis type="b">R</emphasis> if a document was both a reprocessable and an unpostable.</li>
<li>Use Code <emphasis type="b">N</emphasis> for a document previously in Unpostables. An unpostable document can be identified by an entry source code <emphasis type="b">U</emphasis> to the right of the reject register title or by a Form 3893 prepared in Unpostables.</li>
</alphalist></para>
<para>Enter the code for the Master File being adjusted. The codes are shown in the upper center of Form 4028: <bulletlist>
<li>1 = IMF</li>
<li>2 = BMF</li>
<li>5 = IRP</li>
<li>6 = ANMF</li>
</bulletlist><note notetype="note">The Master Files may be mixed on the same form, unless the Data Controls function requests separate forms.</note></para>
<para>Enter the DLN of the document being adjusted. Be sure to enter the correct DLN year digit, even if not shown on the document.</para>
<para><emphasis type="b">Document Count:</emphasis> <alphalist>
<li>Enter the number of documents being adjusted.</li>
<li>If the adjustment does not affect document count, leave this field blank. For example, if money is being removed from a document that will still be processed with the same DLN, no count is necessary.</li>
</alphalist></para>
<para><emphasis type="b">Credit Adjustment:</emphasis> Enter the amount of credit being adjusted.</para>
<para><emphasis type="b">Debit Adjustment:</emphasis> Enter the amount of the debit adjustment. Debit adjustments are valid only for Document Codes 24, 45, 48, 51, 58 and 87.</para>
<para><emphasis type="b">Serial Number:</emphasis> Enter the DLN serial number whenever only one document is being adjusted.</para>
<para><emphasis type="b">Control Record Source Code:</emphasis> Enter <emphasis type="b">R</emphasis> for Rejects.</para>
<para><emphasis type="b">ANMF Abstract Number:</emphasis> No entry is necessary in this column.</para>
<para><emphasis type="b">Reason for Adjustment:</emphasis> Enter the reason for the SCCF adjustment and enter the reject sequence number to provide an audit trail. If more than one adjustment is being made for the same document, enter brackets around the related adjustments.</para>
</subsection2>
<subsection2 id="id337100386"><date>(01-01-2023)</date>
<title>Preparing Form 4028A</title>
<para>Use the instructions in this subsection of the IRM to prepare <citation type="Form">Form 4028-A</citation>. </para>
<para>The <emphasis type="b">To Code</emphasis> is always <emphasis type="b">2</emphasis> and is generated.</para>
<para>Enter the reentered Source Code if applicable. <bulletlist>
<li>N—Nullified or rejected unpostable</li>
<li>R—The document was already a reprocessable return</li>
</bulletlist></para>
<para>Enter the appropriate Master File System Code as shown at the top of the Form. If the Master File of the new DLN is different from the original DLN, enter the new Master File Code.</para>
<para>Enter the old block DLN and year digit. If this is a correction to a previous renumber record, be sure to enter the DLN that is on SCCF.</para>
<para>Enter the new block DLN and year digit in the designated blocks.</para>
<para>Enter the old and new DLN serial number, if only one document.</para>
<para>Enter Control Record Source Code <emphasis type="b">R</emphasis> for Rejects. </para>
</subsection2>
</subsection1>
<subsection1 id="id337100388"><date>(03-17-2025)</date>
<title>Transshipping Returns</title>
<para>Prepare a non-suspense Letter 86C to notify the taxpayer that the return is being routed to Austin, Kansas City, and/or Ogden Submission Processing Campus. Transship the return to AUSPC, KCSC, and/or OSC and notate <emphasis type="b">86C prep</emphasis> on the document.</para>
<para>When a MeF document must be processed as International, enter CC RJECT 651 and email MeF DLN’s to Austin ICO P&amp;A.</para>
<para>Remittances with Form 1042 can be processed in all campuses.</para>
<para>Except for ANMF, all remittances are applied in the campus that received the document.</para>
<para>Forms 1040-ES and 1040C may be processed as short entity, thus eliminating the need to route to either campus. Any required entity change may be input with TC 013.</para>
<para>If Form W-7 is attached, transship to Austin.</para>
<para>Form 1040 that must be processed as Form 1041.</para>
<para>For non-remittance documents, enter RJECT 651 on the terminal.</para>
<para>Prepare a replacement Form 2275 (or local substitute) to route to Files. Note in remarks transferred to Austin, Kansas City, and/or Ogden.</para>
<para>Form 1040 that must be processed at ANMF.</para>
<subsection2 id="id337100389"><date>(01-01-2025)</date>
<title>Transhipping International Returns</title>
<para> International Returns must be forwarded (transshipped) to Austin Submission Processing Campus (AUSPC) on the day that it is received for processing to the address listed in the <emphasis type="b">Note</emphasis>. <bulletlist>
<li><note notetype="exception"><emphasis type="b">Do not process</emphasis> or send to AUSPC any Form 1040 with a Virgin Islands address if <emphasis type="b">both</emphasis> of the following conditions apply:<br/>• The return has a Virgin Islands address, and<br/>• All Form(s) W-2/1099 are from US possessions. <br/> Pull these returns and transship to:<br/>Virgin Islands Bureau of Internal Revenue<br/>6115 Estate Smith Bay, Ste 225<br/>St. Thomas U.S. Virgin Islands 00802</note><br/></li>
</bulletlist><note>Austin Submission Processing Campus <br/> 3651 South IH 35<br/>Stop 6069<br/>Austin, TX. 78731</note> <note notetype="exception" restrict="norestrict"> Do not transship returns to AUSPC if the taxpayer is only converting income paid in foreign currency (e.g., Income reported in Canadian dollars instead of American dollars).</note></para>
<para>Do not transship MeF returns <seealso idref="id337100388">IRM 3.12.37.17</seealso>.</para>
<para>Send International returns to Austin Submission Processing Campus on the day that it is received for processing to the address listed in the above. See <citation type="IRM">IRM 3.12.2.3.7</citation> for a complete list of International returns.</para>
<para>If the ZIP Code is missing, enter <emphasis type="b">01</emphasis> as the last two digits.<note>APO/DPO/FPO filers are instructed to file at AUSPC; however, if received at another campus, process as normal.</note></para>
</subsection2>
<subsection2 id="id337100391"><date>(06-09-2025)</date>
<title>Transshipping Form 1040 for 1041 conversion</title>
<para> When a return is filed for a single deceased taxpayer (two deceased taxpayers on a joint return), and the return covers a tax period after the one in which the taxpayer(s) died, Code &amp; Edit (C&amp;E) will edit Action Code (AC) 640 on a replacement page and route the return to R &amp; C for transshipment to the appropriate Submission Processing Campus (SPC) for conversion to a Form 1041. If the IMF site is processing BMF returns do not transship the return. RJECT 640 the return and route the return using local procedures to BMF C&amp;E team for conversion.</para>
<para>AUSC only, when a Form 1040 is filed for a deceased taxpayer that must be processed as a Form 1041 follow the procedures in the table below.<table frame="all" id="id337101528" summary="Transhipping Form 1040 for 1041 conversion">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>A] The taxpayer’s total income is more than $600.</entry>
<entry><steplist>
<li>RJECT 640 the return. </li>
<li>Complete Form 3696 for Letter 86C (para I and n fill-in with 1-800-829-0922). Complete the 86C fill-ins as follows, Form 1040, tax period on return, received date, OSC, 45 days.</li>
<li>Route to Letter Input team for input of letter. </li>
<li>Follow local procedures for transshipping returns.</li>
</steplist></entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection2>
<subsection2 id="id337101667"><date>(03-17-2025)</date>
<title>Automated Non-Master File Items</title>
<para>The Automated Non-Master File (ANMF) is an automated system developed to replace the previous NMF accounting system.</para>
<para>All ANMF processing is centralized in the Kansas City Submission Processing Campus (KCSPC).</para>
<para>Potential <emphasis type="b">Tax Straddle</emphasis> Returns (Form 6781 attached) will be hand carried to Examination. <alphalist>
<li>Returns identified by Examination as true Tax Straddles will be sent to ANMF for processing.</li>
<li>Returns that are not Tax Straddle will be processed to Master File.</li>
<li>Kansas City<emphasis type="b">(only)</emphasis> Rejects will void the return with CC RJECT 620 and send document to Accounting to be processed at ANMF. </li>
<li>Austin and Ogden<emphasis type="b">(only)</emphasis> will void the return with CC RJECT 620 and follow procedures in paragraph 4. Austin and Ogden will void MeF returns with CC RJECT 620, print the return, and follow procedures in paragraph 4.</li>
</alphalist></para>
<para>Route all Non-Master File documents to:<br/>Kansas City Submission Processing Campus<br/>333 W. Pershing Road<br/>ANMF Team, Mailstop 6263 P-6<br/>Kansas City, MO 64108</para>
</subsection2>
</subsection1>
<subsection1 id="id337100397"><date>(11-10-2021)</date>
<title>Verification and Release of Renumbered Documents</title>
<para>This subsection lists the procedures for verifying and releasing documents.</para>
<subsection2 id="id337100398"><date>(01-01-2023)</date>
<title>Processing Instructions</title>
<para>All renumbered documents will be held until verification that the new DLN has been properly transcribed and has properly updated the SCCF. DLNs can be verified from any of three different listings or from CC SCFTR. <alphalist>
<li>The most efficient listing for DLN verification is the New DLN Record List, SCF–11–48, which lists in new DLN sequence all documents which have been renumbered. Although this listing may include items renumbered elsewhere in the campus, this is the only listing in the same sequence as the source documents which have been blocked for input. </li>
<li>The Rejected Records List, (ERS–05–40), includes only items renumbered in ERS.</li>
</alphalist></para>
<para>Compare the new DLN shown on the document with the new DLN on the listing. <alphalist>
<li>If the new DLN does not match, and the DLN shown on the document is correct, determine whether the erroneous DLN was established on the SCCF by checking the Control Record Listing (CRL) Renumbered Transaction List or research the SCCF using CC SCFTR.</li>
<li>If the erroneous DLN was established, prepare Form 4028 changing the erroneous DLN to the correct renumber DLN. Use <emphasis type="b">From Code</emphasis> 0.</li>
<li>If the erroneous DLN was not established and the original DLN was not deleted, prepare Form 4028–A for the old DLN and the correct new DLN. Use <emphasis type="b">From Code</emphasis> 4.</li>
<li>If the new DLN on the Rejected Records List is correct, change the document to agree with the listing.</li>
<li>If unable to determine the correct action, request assistance from Data Controls.</li>
</alphalist></para>
<para>When all items in a new block have been verified, route the block to Batching for input. Be sure to include the original Form 813 or 1332 as the block header document. The second copy of Form 813 is routed to Accounting. </para>
</subsection2>
</subsection1>
<subsection1 id="id337101181"><date>(01-01-2026)</date>
<title>Processing Payments and IRS Prepared Documents</title>
<para> This subsection of the manual lists the procedures to be followed for resolving payments. Follow the instructions in the IRMs listed below for processing payments, RTR payments, unidentified remittances, lockbox, and special payment perfection procedures.<alphalist>
<li><citation type="IRM">IRM 3.17.10.3</citation> Unidentified Remittance File</li>
<li><citation type="IRM"> IRM 3.12.10.6.5.2</citation> Special Procedures for Lockbox Incomplete Processing Records</li>
<li><citation type="IRM"> IRM 3.12.212</citation> Application for Extensions of Time to File Tax Returns (Denied Extensions).</li>
<li><citation type="IRM">IRM 3.8.45.5.16</citation> Manual Deposit Process (W7)</li>
<li><citation type="IRM">IRM 3.12.10.3.5</citation> Remittance Transaction Research (RTR) System</li>
<li> <citation type="IRM">IRM 3.12.10.3.7</citation> Lockbox Unprocessable Reductions (Special Payment Perfection Procedures)</li>
<li><citation type="IRM">IRM 3.12.212.6.3</citation> Application for Extension for Time to File (Error Code 004).</li>
<li> <seealso idref="id337100576">Exhibit 3.12.37-26</seealso> </li>
</alphalist></para>
<para>If processing remittance made out to entities other than the IRS, follow procedures to send the remittance to URF or EXC.</para>
<para>IRM references must be researched prior to processing payments. </para>
<subsection2 id="id337101176"><date>(03-16-2023)</date>
<title> SSPND 351 Research and Unprocessable Payments</title>
<para>The Integrated Automation Technologies IAT Tool for Payment Perfection must be used to perform IDRS research. Check the Collection Statute Expiration Date (CSED) on all payments, apply to earliest payment when applicable. Always check cross-referenced TIN to ensure proper posting. Correct all transcribed fields and leave a working trail. </para>
<para>Below is an if then table for payments and Lockbox payments: <table frame="all" id="id337101286" summary="researching for unprocessable payments using TXMOD and IMFOLT" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">If Payment is</emphasis></entry>
<entry valign="top"><emphasis type="b">Then</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Payment received with TIN, taxpayer name and/or tax period missing</entry>
<entry>Research attachments for correct tax period. Research IDRS using CC SUMRY, IMFOLT, TXMOD to determine correct tax period. If unable to determine correct tax period, apply payment to the earliest balance due. </entry>
</row>
<row>
<entry>Payment received and the only identifying information is the name and address on the check</entry>
<entry>Research attachments for correct TIN. Research IDRS CC NAMEI &amp; NAMES to determine SSN. Use IDRS CC NAMEB &amp; NAMEE to determine EIN. Research attachments for TP TIN. If unable to determine correct TP SSN/EIN send to Unidentified Remittance File (URF). </entry>
</row>
<row>
<entry>Payment received and verification of TIN, Tax period or Name of taxpayer needed </entry>
<entry>Use CC ENMOD/INOLE to determine missing information. CC INOLEX displays SSA Name controls, cross references and MFT, merge transaction information. Apply payment correctly. </entry>
</row>
<row>
<entry>Payment received and verification of TIN is needed.</entry>
<entry>Research attachments for correct TIN. If a full name and address is found, research IDRS CC NAMEI &amp; NAMES to determine correct SSN. If unable to determine correct TP SSN/EIN send payment to Unidentified Remittance File (URF).</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Envelopes from unprocessable payments/lockbox payments have been delivered to ERS clerical daily for use in payment research and may be used to locate an address for the taxpayer. If envelopes have been associated with payments sent to URF, send envelopes to URF along with Unidentified payment.</para>
<para>Below are a list IRM referenced for IDRS Command Codes. Please use references for screen display usage.<table frame="all" id="id337101287" summary="IRM references for IDRS command codes" width="4.5in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">IDRS Command Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">IRM Reference (Screen Display)</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>IMFOL</entry>
<entry><citation type="IRM">IRM 2.3.51</citation></entry>
</row>
<row>
<entry>INOLE</entry>
<entry><citation type="IRM">IRM 2.3.47</citation></entry>
</row>
<row>
<entry>NAMEE AND NAMEB</entry>
<entry><citation type="IRM">IRM 2.3.60</citation></entry>
</row>
<row>
<entry>SUMRY and TXMOD </entry>
<entry><citation type="IRM">IRM 2.3.11</citation></entry>
</row>
<row>
<entry>BMFOL</entry>
<entry><citation type="IRM">IRM 2.3.59</citation></entry>
</row>
<row>
<entry>ENMOD </entry>
<entry><citation type="IRM">IRM 2.3.15</citation></entry>
</row>
</tbody>
</tgroup>
</table></para>
<subsection3 id="id337101342"><date>(11-10-2021)</date>
<title>Internal Revenue Code 965 Payments</title>
<para>IRC 965 payments can be identified on the payment as<emphasis type="b"> IRC Section 965</emphasis>, <emphasis type="b">Section 965</emphasis> or <emphasis type="b">965</emphasis>. This indication will be located in the top margin of the tax return or payment posting vouchers or anywhere on the paper check. These payments can be received with both IMF or BMF Forms and MFTs.</para>
<para>Taxpayers may be required to pay tax resulting from Section 965 of the Code when filing their returns for tax years 2017 and subsequent. Taxpayers must initiate payment either by same day wire transfer, check, or money order. For same day wire transfers taxpayers will use a 5-digit tax type code 09650. The fifth digit of the tax type must be <emphasis type="b">0</emphasis> so the payment post with TC 670 and a secondary TC 570. </para>
<para>Electronic Federal Processing Payment System (EFPPS) will automatically add a Designated Payment Code (DPC) 64 to same day wire payments that come in with tax type 09650. If the EIN/SSN indicator is <emphasis type="b">1</emphasis> EFPPS will auto correct the tax type to 1040. These payments are identified as 23X and DPC 64</para>
<para>Below are the correction procedures for IRC 965 payments:<bulletlist>
<li>Research using IDRS CC TXMODA, IMFOLT, BMFOLT, and SUMRY to determine the correct tax form to apply the payment. </li>
<li>Payments will be applied to Forms 1040, 1120, 1065, 1041, and 990-T. When the correct form is determined input the correct tax type with <emphasis type="b">0</emphasis> as the fifth digit. </li>
<li>All IRC 965-tax payments must be posted to the tax module where the assessment was posted. For example, if the 965 tax assessment is posted on the 201712 tax modules, all tax payments will be posted to the 201712 tax module regardless of the year in which the payment is made. </li>
<li>For tax payments received in 2018 for a tax period other than 201712 the payment must be changed to 201712.</li>
</bulletlist></para>
<para>Review payment IRM references in <seealso idref="id337101181">IRM 3.12.37.19</seealso> for specific payment instructions.</para>
</subsection3>
<subsection3 id="id337101529"><date>(11-07-2023)</date>
<title>Identifying IDRS Transactions</title>
<para>IDRS transactions are identified by the inflated Julian date. In order to research an IDRS transaction, follow the below steps.</para>
<para>Go to Control-D, click on filter and input EOD1821* under Job Name. Set your filter dates to run at least a day or two prior to the SCFTR date as well as a week after the date and locate your Campus (example EOD1821G is for Kansas City).</para>
<para>Select all the reports for your campus, click on the binocular icon on the top right and input the TIN with dashes to locate the transaction. You may also search by the DLN using the following format, XX X XX - XXX - XXX XX - X.</para>
<para>When searching for the transaction be sure to look for both sides of a credit transfer.</para>
<para>You can then save the transaction page and/or pages as your document.</para>
</subsection3>
</subsection2>
<subsection2 id="id337101645"><date>(01-01-2026)</date>
<title>Transfer to Unidentified</title>
<para>The Unidentified Remittance File (URF) was established for the purpose of controlling unidentified payments that are received in the campuses. </para>
<para>Remittance documents less than one year from the transaction received date are transferred to Unidentified in the following cases:<alphalist>
<li>The document is missing and unable to be located.</li>
<li>The document does not contain enough information in order to determine the correct taxpayer or tax module in order to apply the money.</li>
<li>The document will not post due to excess collections notated in CC TXMOD.</li>
</alphalist></para>
<para>If the document is in RTR, notate 4620 account in notes and print the document to send to accounting.</para>
<para>If you are unable to locate the paper document, you must recreate the document utilizing the information in Section 01 in IDRS to send to accounting.</para>
<para>If the Julian date in the DLN is for the current fiscal year, enter <emphasis type="b">NWDLN 611</emphasis> with the literal <emphasis type="b">URF</emphasis> and send the document to accounting.</para>
<para>If the Julian date in the DLN is for a prior year but less than one year from the transaction received date, enter <emphasis type="b">NWDLN 611</emphasis> with the literal <emphasis type="b">OTHER</emphasis> and send the document to accounting.</para>
</subsection2>
<subsection2 id="id337101646"><date>(01-01-2026)</date>
<title>Excess Collection File</title>
<para>The Excess Collection File (XSF) is where URF cases are moved to once the transaction date is a year old. It is also used when the Refund Statute Date expires and there are credits still on the account. Those credits are moved to the XSF as the taxpayers are no longer entitled to a refund. The credits remain on the IDRS file for seven years after they are moved to the XSF. The credit is then viewable on Control-D report name XCESS COLL DROP LST1. XSF employees continue to research where the money belongs.</para>
<para>Remittance documents over one year from the transaction received date are transferred to excess collections in the following cases:<alphalist>
<li>The document is missing and unable to be located.</li>
<li>The document does not contain enough information in order to determine the correct taxpayer or tax module in order to apply the money.</li>
<li>The document will not post due to excess collections notated in CC TXMOD.</li>
</alphalist></para>
<para> If the document is in RTR, notate to 6800/XSF in RTR notes and print the document to send to accounting.</para>
<para>If you are unable to locate the paper document, you must recreate the document utilizing the information in section 01 in IDRS to send to accounting.</para>
<para>Apply to excess collections by entering <emphasis type="b">NWDLN 611</emphasis> with the literal <emphasis type="b">EXC</emphasis> and send the document to accounting.<note>See <seealso idref="id337100576">Exhibit 3.12.37-26</seealso> for the correct General Ledger Account Number.</note></para>
</subsection2>
<subsection2 id="id337101648"><date>(01-01-2025)</date>
<title>Renumbering Payments and IRS Prepared Documents</title>
<para>This subsection lists the procedures for renumbering payments.<alphalist>
<li>General Requirements</li>
<li>Trace ID Requirements</li>
<li>Assignment of the new DLN</li>
<li>Command Code NWDLN</li>
</alphalist></para>
<subsection3 id="id337101620"><date>(01-01-2025)</date>
<title>General Requirements</title>
<para>Payments must be renumbered if they have been input to the wrong tax class or given the incorrect document code.</para>
<para>Use the table below when recreating missing Doc Codes 24, 45, 48, 58, and 87 to determine which form to complete.<table frame="all" id="id337101621" summary="Correct form for Doc Code 24, 45, 48, 58, and 87">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Document Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Form</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>24</entry>
<entry>Complete <citation type="Form">Form 2424</citation></entry>
</row>
<row>
<entry>45</entry>
<entry>Complete <citation type="Form">Form 3245</citation></entry>
</row>
<row>
<entry>48, 58, 87</entry>
<entry>Complete <citation type="Form">Form 3809</citation></entry>
</row>
</tbody>
</tgroup>
</table></para>
</subsection3>
<subsection3 id="id337101622"><date>(01-01-2025)</date>
<title>Trace ID Requirements</title>
<para>As of January 1, 2009, all payments are assigned a Trace Identification (ID) Number for tracking purposes. Every Deposit is assigned a Trace ID which is also assigned to each payment within that deposit. This data is entered into the Custodial Detail Data Base (CDDB). The CDDB is used for balancing receipts by IRS and BFS. It is used for payment tracers.</para>
<para>Each Deposit Ticket is assigned a Trace ID number in the following format:<table frame="all" id="id337100962" summary="The format of each deposit tick and trace id number" width="4.5in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="33*"/>
<colspec colname="col2" colwidth="34*"/>
<colspec colname="col3" colwidth="33*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Parts </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Characters </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definition </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">Site ID</entry>
<entry colsep="1" rowsep="1">NN</entry>
<entry colsep="1" rowsep="1">FLC</entry>
</row>
<row>
<entry colsep="1" rowsep="1">System ID</entry>
<entry colsep="1" rowsep="1">NN</entry>
<entry colsep="0" rowsep="1">Identifies Deposit Method</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Deposit Date</entry>
<entry colsep="1" rowsep="1">YYYYDDD</entry>
<entry colsep="1" rowsep="1">Julian Date of Deposit</entry>
</row>
<row>
<entry colsep="1">Sequence Number</entry>
<entry colsep="1">NNN</entry>
<entry colsep="1">Deposit Sequence</entry>
</row>
</tbody>
</tgroup>
</table><br/><note>The last six digits are the Transaction Sequence Number for each payment.</note><br/></para>
<para>If the original document is not available, use the Remittance Transaction Research (RTR) System to locate the correct Trace ID for each payment being renumbered for re-entry.</para>
<para>Every remittance must have a Trace ID, which must be transcribed. When creating a new document (or recreating a document) containing credit money, the Trace ID must be annotated at the bottom of the new form.</para>
<para>Payments with the same first 20 digits in their Trace ID will be given a DLN. That 20-digit Trace ID will be annotated on the bottom of the Form 813 and the transaction sequence number will go to the right of each payment listed on the Form 813. </para>
</subsection3>
<subsection3 id="id337101623"><date>(01-01-2026)</date>
<title>Command Code NWDLN</title>
<para>The SCCF must be changed to remove the old DLN and establish the New DLN anytime a document is renumbered.</para>
<para> Documents can be renumbered without a manually prepared SCCF adjustment by using CC NWDLN.</para>
<para>The valid literals that can be used with CC NWDLN are as follows: <alphalist>
<li>OTHER -- miscellaneous general ledger accounts.</li>
<li>URF -- Unidentified Remittance File (use only with current fiscal year DLN).</li>
<li>DEPF -- Deposit Fund Account 4700</li>
<li>EXC -- Excess Collection Account 6800 (Use only with prior fiscal year DLN or non-revenue document codes 48 and 58).</li>
<li>SMCR -- Small Credit/Debit Write-off Account 6540 (use only if debit balances are less than $5 and credit balances are less than $1).</li>
<li>WASH -- Washout transactions with both debit and credit sides being closed (WASH can only be used when both the debit and credit documents are in Rejects and are for the same tax class and Master File Code, and will be closed on the same day) <note>For <emphasis type="b">WASH</emphasis> documents when the tax class and/or Master File Code are not the same, prepare Form 4028 RJECT 630 the document DLN, 0 to 2 and notate <emphasis type="b">WASH</emphasis> in remarks.</note> <note>Do not use the Literals <emphasis type="b">EXC</emphasis>, <emphasis type="b">DEPF</emphasis>, or <emphasis type="b">OTHER</emphasis> except for prior fiscal year DLN without prior coordination with Accounting.</note></li>
</alphalist></para>
<para>The Rejects function will assign all new DLNs for the following documents: <bulletlist>
<li>RPS payments.</li>
<li>Revenue Receipt documents (Document Codes 17, 18, 19, 20, 24, 70,87).</li>
<li>Pre-journalized non-revenue receipt documents (Document Codes 45, 48, 58). </li>
<li>Forms 3244, Payment Posting Voucher, prepared to apply remittances from other documents.</li>
</bulletlist></para>
<para>When renumbering revenue receipt documents, be sure that the TC Code, MFT, Tax Period, Name Control, received date and Trace ID are present on the document. </para>
<para>Enter the new DLN on the record as follows:<bulletlist>
<li>Input CC NWDLN. with Action Code 611 for payments. Input CC NWDLN with Action Code 620 to renumber a payment to ANMF.<note notetype="example">NWDLN 611 09217-001-00100-2</note><note notetype="example">NWDLN 620 09617-001-00100-2</note></li>
</bulletlist></para>
<para>If the new DLN is for a different Master File, enter a hyphen after the DLN in IDRS followed by the New DLN Master File Code as follows:<alphalist>
<li>If renumbering a revenue receipt from IMF to BMF, input a <emphasis>2</emphasis> following the hyphen at the end of the new DLN.</li>
<li>If renumbering a revenue receipt from BMF to IMF, input a <emphasis>1</emphasis> following the hyphen at the end of the new DLN.</li>
<li>If renumbering a revenue receipt from IMF to EPMF, input a <emphasis type="b">3</emphasis> following the hyphen at the end of the new DLN.</li>
<li>If renumbering a revenue receipt from IMF to IRAF, input a <emphasis type="b">4</emphasis> following the hyphen at the end of the new DLN.</li>
<li>If renumbering a revenue receipt from IMF to ANMF, input a <emphasis type="b">6</emphasis> following the hyphen at the end of the new DLN.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101624"><date>(01-01-2025)</date>
<title>Assignment of New DLN</title>
<para>Use BBTS offline DLN Generation to ensure that no number is assigned twice.</para>
<para>Assign separate block DLNs for payments documents.</para>
<para>The DLN is a 14-digit number assigned to every document input to the ADP system that affects a taxpayer's account. The DLN is used for controlling, identifying, and locating a document. The table below identifies the components of a DLN.<table frame="all" id="id337101521" summary="DLN Format and description">
<tgroup cols="7" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="14*"/>
<colspec colname="col2" colwidth="14*"/>
<colspec colname="col3" colwidth="14*"/>
<colspec colname="col4" colwidth="14*"/>
<colspec colname="col5" colwidth="14*"/>
<colspec colname="col6" colwidth="14*"/>
<colspec colname="col7" colwidth="16*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">00</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">2</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">21</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">073</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">550</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">02</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">X</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>File Location Code</entry>
<entry>Tax Class</entry>
<entry>Doc Code</entry>
<entry>Julian Date</entry>
<entry>Blocking Series</entry>
<entry>Serial Number</entry>
<entry>Year Digit</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Stamp or write the new DLN on each document being numbered. <note>Be sure the old DLN has been lined through in red.</note></para>
<para>Prepare <citation type="Form">Form 813</citation> for each block of renumbered payments.<alphalist>
<li>Enter the first 11 digits of the new DLN. Verify that the DLN entered on the document and register are the same and that the new DLN is accurate.</li>
<li>Enter the year digit of the new DLN.</li>
<li>Enter the current date. </li>
<li>Enter the Block Header Transaction Code, if applicable.</li>
<li>Enter the primary amount from the document. An entry of .00 for non pre-journalized documents is considered an amount.</li>
<li>Enter the secondary amount in brackets and the credit adjustment as an increase or decrease.</li>
<li>Circle the printed serial number to indicate the number of documents in the block.</li>
<li>Add the primary amounts and enter the total credit or debit.</li>
<li>Add the secondary amounts in brackets and credit adjustment amounts as increases or decreases.</li>
<li>Enter initials.</li>
<note>Each payment listed on the <citation type="Form">Form 813</citation> must have the Trace ID Number listed to the left due to the format of Form 813.</note></alphalist></para>
<para>Hold all renumber documents until the next day to verify the new DLNs were input correctly, see <seealso idref="id337101651">IRM 3.12.37.20.1.6</seealso> </para>
</subsection3>
</subsection2>
<subsection2 id="id337101668"><date>(04-09-2025)</date>
<title>ANMF Subsequent Transactions</title>
<para>To request an ANMF transcript send an email to (*TS KCSPC Non-Master File Team) </para>
<para>Upon receipt of ANMF transcript, follow normal renumbering procedures.</para>
<para>If the response is <emphasis type="b">No Record</emphasis>, follow procedures to transfer to Unidentified.</para>
</subsection2>
</subsection1>
<subsection1 id="id337100410"><date>(01-01-2025)</date>
<title>Voided Documents</title>
<para>This subsection lists the procedures for voiding documents, including.<bulletlist>
<li>Conditions for Voiding Documents</li>
<li>Numbered Documents not to be Processed</li>
<li>Accounting Data Control requests</li>
<li>Duplicate DLNs</li>
<li>Rejects records list</li>
</bulletlist></para>
<subsection2 id="id337100411"><date>(01-01-2025)</date>
<title>Conditions for Voiding Documents</title>
<para>Documents are deleted because the document will not be processed. </para>
<para>Returns without the taxpayer's signature are not official documents and may not be processed.</para>
<para>Never void a return that has had a manual refund issued.</para>
<para>Normally, no SCCF adjustment is necessary. Enter <emphasis type="b">RJECT 640</emphasis> on the terminal and the SCCF is automatically updated. </para>
<para>Below are the types of documents which will be voided: <bulletlist>
<li>Numbered documents which are never to be processed, e.g. an attachment or form without a tax return. </li>
<li>Unprocessable IRS prepared documents</li>
<li>Returns sent back to the taxpayer</li>
<li>Data Control request</li>
<li>Duplicate DLNs</li>
</bulletlist><note notetype="note">CC ESTABDT must be performed. See <seealso idref="id337100481">Exhibit 3.12.37-12</seealso> </note></para>
<subsection3 id="id337100412"><date>(05-03-2024)</date>
<title>Numbered Documents Not to Be Processed</title>
<para>Some documents are numbered that will not be processed. These would include the following: <bulletlist>
<li>Subsequent payments</li>
<li>Attachments to returns</li>
</bulletlist></para>
<para>Attachments to returns will be routed to Files for association with the proper return. Input CC RJECT 640 line through the DLN and notate <emphasis type="b">DLN voided</emphasis> with a date and route the document to Files with a note indicating the DLN of the associated returns. For <emphasis type="b">MeF</emphasis> Returns input CC RJECT 640 and send the return to Alpha files. </para>
<para>Voided documents might have to be sent back to the filer. These types of cases will need the DLN lined out completely after you have voided the document with CC RJECT 640.</para>
<para>Returns that will not be attached to a previously filed return or returned to the taxpayer will be sent to Files to be refiled in its original block. </para>
</subsection3>
<subsection3 id="id337100413"><date>(01-01-2025)</date>
<title>Unprocessable IRS Prepared Documents</title>
<para>IRS prepared documents are voided with CC RJECT 640 for non-remittance and CC RJECT 630 for remittance documents. They are then returned to the originator if not fully processable. Attach Form 4227 (or local form) to the front of the document stating the reason for deletion.</para>
<para>When processing campus-initiated documents, use CC RJECT 640, write <emphasis type="b">DLN voided</emphasis> and the date in the top margin near the DLN. If the preparer cannot be identified, line through DLN, route to Files. For documents returned to originator, prepare a Routing and Transmittal Slip or follow local routing control.</para>
<para>For area office prepared documents, use CC RJECT 640, write <emphasis type="b">DLN voided</emphasis> and the date in the top margin near the DLN, and route to the originating office.</para>
<para>Only with supervisory approval, destroy IRS prepared documents that are to be canceled and not attached behind the return or routed to the preparer. See National Archives and Record Administration (NARA) approved Document 12990, IRS Records Control Schedules, for records retention, disposition, and destruction guidance to prevent unauthorized/unlawful destruction of records.</para>
</subsection3>
<subsection3 id="id337100414"><date>(11-07-2023)</date>
<title>Returns Sent Back to the Taxpayer</title>
<para>A few returns are voided and sent back to the taxpayer. Refer to <citation type="IRM">IRM 3.11.3</citation> and Form 3531 for a description of the returns that are returned to the taxpayer.</para>
<para> If a tax return is received without the taxpayer's signature, see <seealso idref="id337101258">IRM 3.12.37.14.2</seealso> for more information.</para>
<para>If a taxpayer has filed a non-remittance return, such as a BMF-type entity on an IMF form as an example, void the document and route back to the taxpayer. Prepare a Quick Note, advise the taxpayer to see <a href="https://www.irs.gov/" title="irs.gov">www.irs.gov</a> to locate the appropriate business form.</para>
</subsection3>
<subsection3 id="id337101649"><date>(01-01-2025)</date>
<title>Data Control Delete Request</title>
<para>Data Control deletes are removed from ERS with Action Code 660. These are records that have been selected by Data Control in Accounting for deletion.<alphalist>
<li>Data Control function may access an ERS record and delete it, instead of indicating to ERS Tax Examiners which records to delete at the campus option. </li>
<li>Regardless of the method used to enter <emphasis type="b">RJECT 660</emphasis>, the documents will be pulled by Data Control.</li>
</alphalist></para>
<para>Rejects documents:<alphalist>
<li>Enter CC RJECT, Action Code 660, for each document in the Workable Suspense Inventory.</li>
<li>For documents in Unworkable Suspense, use CC ACTVT and enter CC RJECT, Action Code 660 on the following day.</li>
</alphalist></para>
<para>GMF registers:<alphalist>
<li>If the register is in ERS status, ERS will enter Action Code 3 to move the register to Rejects inventory.</li>
<li>On the following day, enter 2-R on the registers that were 3-coded the previous day.</li>
<li>If the register is in Rejects inventory, enter 2-R.</li>
</alphalist></para>
<para>Compare the DLNs with Action Code 660 on the Rejected Records List (ERS 05-40) with the list of deletes received from Data Control to ensure that the correct records were deleted. If Data Control has deleted the records by accessing the ERS file, no verification is necessary. <alphalist>
<li>If the correct documents were deleted, destroy the charge-outs and mark both lists to show that the items have been deleted.</li>
<li>If any Action Code 660 charge-out does not match the Data Control list, pull the document using local procedures and annotate the Rejected Records List and all copies of the charge-out that the record was deleted in error. Route the document and remaining copies of the charge-out (according to local procedures) for preparation of the necessary forms to adjust the SCCF and reenter the document.</li>
</alphalist></para>
</subsection3>
<subsection3 id="id337101650"><date>(01-01-2025)</date>
<title>Duplicate DLNs</title>
<para>The Document Locator Number (DLN) is used in ERS to control every record on the file. Items in the error inventory are controlled by block DLN, while suspense records are controlled by 14–digit DLN.</para>
<para>If a block DLN attempts to establish on the error inventory for a DLN that is already on the file, the record is passed to the Suspense Inventory. <alphalist>
<li>If the 14–digit DLN does not match another on the workable inventory, the record will become part of Workable suspense, with a generated Action Code 700 and Status Code 470.</li>
<li>After accessing the Suspense Record by 14–digit DLN, clear the Action Code 700 and correct as an error record.</li>
<li>If ERS 19–40 is generated work the workable document first, then activate unworkable and cancel DLN</li>
</alphalist></para>
<subsection4 id="id337101614"><date>(01-01-2025)</date>
<title>ERS Inventory</title>
<para>Identical 14–digit DLNs are not permitted in the same ERS inventory at the same time.</para>
<para>If a second record attempts to establish on either the Workable or Unworkable Suspense Inventory, one is purged from ERS. <alphalist>
<li>A record already on the Unworkable file has priority over a new record trying to establish on that file.</li>
<li>A record on the Workable file has priority over a new or Unworkable record attempting to establish on the Workable file.</li>
<li>A record being activated from the Unworkable file has priority over a new record trying to establish on the Workable file.</li>
</alphalist></para>
</subsection4>
<subsection4 id="id337101615"><date>(01-01-2025)</date>
<title>Purged ERS Inventory</title>
<para>All purged ERS records are listed on the Duplicate Document DLN Register. </para>
<para>The Action Code indicates the previous status of the record being purged. The codes are as follows: <bulletlist>
<li>711 – From Code and Edit</li>
<li>712 – From Error Correction</li>
<li>713 – From Unpostables</li>
<li>714 – From Unworkable Suspense</li>
</bulletlist></para>
<para>No SCCF control records are produced for documents purged from ERS. If not prepared by Data Control, use Form 4028 to correct the SCCF for deleted and/or renumbered documents.</para>
<para>Most duplicate DLN cases will have been identified by the Data Controls function in Accounting. </para>
<para> Use the chart below to determine Data Control and Accounting numbering procedures:<table frame="all" id="id337100734" orient="port" pgbrk="nobreak" summary="Duplicate DLNS" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="50*"/>
<colspec colname="col2" colnum="2" colwidth="50*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If Data Control</emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> A]</emphasis> Has already requested deletion of the document on the duplicate listing,</entry>
<entry morerows="0" nameend="col2" namest="col2">No further action is necessary. The document has already been deleted from ERS and Data Control will complete the required action on the SCCF.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> B]</emphasis> Has requested deletion of the other document with that DLN,</entry>
<entry morerows="0" nameend="col2" namest="col2">Enter <emphasis type="b">RJECT 660</emphasis> for the DLN on ERS. Then reenter the document erroneously deleted from ERS. Contact Data Control or research the SCCF with CC SCFTR to ensure that the SCCF will accept this reentry. It may be necessary to prepare Form 4028 with From-To Code 3–0 or 4–0 before routing the document to Batching with Form 3893.</entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> C]</emphasis> Wants both documents deleted,</entry>
<entry morerows="0" nameend="col2" namest="col2">Enter <emphasis type="b">RJECT 660</emphasis> and route to Accounting any documents not already pulled. </entry>
</row>
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> D]</emphasis> Has not identified the duplicate condition,</entry>
<entry morerows="0" nameend="col2" namest="col2">Contact Data Control for further instructions. SCCF research will be used to determine if the documents must be reentered.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>A 3-part charge-out is generated for each item on the duplicate listing. <alphalist>
<li>For Action Codes <emphasis type="b">711</emphasis> and <emphasis type="b">712</emphasis>, the documents will be located in blocks still in the Error Correction work area.</li>
<li>For Action Code <emphasis type="b">713</emphasis>, the documents have been routed by Unpostables to Error Resolution. Detach and route the original copy of the charge-out to Files for insertion into the block.</li>
<li>If the documents are already charged to ERS Suspense, route the original copy of the charge-out to Files for insertion into the block next to the previous charge-out for Action Code <emphasis type="b">714</emphasis>.</li>
<li>Regardless of Action Code, the documents may have already been charged to Data Control. Insert the original copy of the charge-out into the block where the document had been previously filed.</li>
<li>The second copy of the <emphasis type="b">Duplicate</emphasis> charge-out may be destroyed when the case is resolved, or the second copy may be attached to the back of the return to provide an audit trail.</li>
</alphalist></para>
</subsection4>
</subsection3>
<subsection3 id="id337101651"><date>(01-01-2025)</date>
<title>Rejected Records List, ERS–05–40</title>
<para>This report lists each record that is deleted from ERS. It is printed each day and contains the following: <bulletlist>
<li>Original DLN</li>
<li>Master File Code</li>
<li>Block Number</li>
<li>Batch Number</li>
<li>Primary TIN</li>
<li>Name Control</li>
<li>Employee number of tax examiner who rejected the record</li>
<li>Action Code used</li>
<li>Renumbered DLN (and MFT, if applicable)</li>
<li>New Master File Code</li>
<li>Total number of Rejected Records</li>
</bulletlist></para>
<para>For each rejected record, there is a charge-out, with the literal <emphasis type="b">REJECT</emphasis>. <alphalist>
<li>Make sure that you have a document and charge-out for each entry on the Rejected Records List.</li>
<li>Contact Data Controls if the documents are available for Action Code 600. They are probably looking for the documents.</li>
</alphalist></para>
<para>Route the documents according to the Action Code shown on the listing.<alphalist>
<li>Action Code <emphasis type="b">610</emphasis> or <emphasis type="b">611 </emphasis>—Renumber. After verifying that the same DLN is shown on the New DLN Summary as on the document, route the documents to Batching with the new Form 813 or 1332. Action Code 611 items that show a literal will be routed to Accounting.</li>
<li>For Action Code <emphasis type="b">620</emphasis>, route the documents to the ANMF function in Accounting.</li>
<li>Items with Action Code <emphasis type="b">630</emphasis> are routed to Batching for re-input after verifying that Form 3893 has been prepared for each block DLN. Occasionally, Action Code 630 is entered for non-re-input items where later manual SCCF adjustments will be prepared.</li>
<li>Action Code <emphasis type="b">640</emphasis> indicates documents that have been voided. Route campus initiated documents to the originator. Otherwise, route to Files unless other routing instructions are attached to the return.</li>
<li>Action Code <emphasis type="b">651 </emphasis>–Route International documents to the Austin Submission Processing Campus per local procedures. Prior to transshipping line through the DLN. (See <seealso idref="id337100388">IRM 3.12.37.17</seealso>) </li>
<li>Action Code <emphasis type="b">660 </emphasis>—Data Control Delete. Route to Data Controls if not already sent.</li>
</alphalist></para>
<para>Keep the Rejected Records List for one year as a reference.</para>
</subsection3>
</subsection2>
</subsection1>
<subsection1 id="id337100419"><date>(01-01-2025)</date>
<title>Renumbering Domestic and International Form 1040</title>
<para>This subsection lists the procedures for renumbering documents.<bulletlist>
<li>General requirements</li>
<li>DLN Format</li>
<li>Domestic and International Return Renumbering Procedures</li>
</bulletlist></para>
<subsection2 id="id337100420"><date>(01-01-2025)</date>
<title>General Requirements</title>
<para> Form 1040 Injured Spouse with blocking series other than 920-929 require renumbering.</para>
<para>Form 1040-NR or Form 1040-SS Injured Spouse with blocking series other than 920-925 require renumbering.</para>
<para>See <citation type="IRM">IRM 3.12.2.3.7</citation> to determine if a Domestic <citation type="Form">Form 1040</citation> must be renumbered to an International <citation type="Form">Form 1040-NR</citation> or <citation type="Form">Form 1040-SS</citation>.</para>
</subsection2>
<subsection2 id="id337101652"><date>(01-01-2025)</date>
<title>DLN Format</title>
<para>Positions 1 and 2 File Location Code.<table frame="all" id="id337101626" summary="Submission Processing Campuses with file location codes">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Submission Processing Center</emphasis></entry>
<entry valign="top"><emphasis type="b">File Location Code</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Austin</entry>
<entry>18, 20, 21, 74, 75, 76</entry>
</row>
<row>
<entry>Kansas City</entry>
<entry>09, 14, 16, 36, 43, 70, 79, 80, 89</entry>
</row>
<row>
<entry>Ogden</entry>
<entry>29, 30, 32</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para><emphasis type="b">Position 3</emphasis> —Tax Class. Identifies the type of tax. <bulletlist>
<li>2 = Individual Income Tax/Fiduciary</li>
</bulletlist></para>
<para><emphasis type="b">Positions 4 and 5</emphasis> —Document Code.<table frame="all" id="id337101609" summary="Determine form number and MFTR codes and tax class descriptions" width="4.5in">
<tgroup cols="4" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="25*"/>
<colspec colname="col3" colwidth="25*"/>
<colspec colname="col4" colwidth="25*"/>
<colspec colname="col5" colwidth="25*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Form Numbers</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">MFT Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Tax Class</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Doc. Code</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>1040</entry>
<entry>30</entry>
<entry>2</entry>
<entry>11, 12, 21, 22</entry>
</row>
<row>
<entry>1040 MeF</entry>
<entry>30</entry>
<entry>2</entry>
<entry>11, 21</entry>
</row>
<row>
<entry>1040 MeF International (AUSC Only)</entry>
<entry>30</entry>
<entry>2</entry>
<entry>05</entry>
</row>
<row>
<entry>1040NR (AUSC Only)</entry>
<entry>30</entry>
<entry>2</entry>
<entry>72, 73</entry>
</row>
<row>
<entry>1040SS(sp) (AUSC Only)</entry>
<entry>30</entry>
<entry>2</entry>
<entry>27</entry>
</row>
<row>
<entry>1040SS (AUSC Only)</entry>
<entry>30</entry>
<entry>2</entry>
<entry>26</entry>
</row>
<row>
<entry>1040X</entry>
<entry>30</entry>
<entry>2</entry>
<entry>11, 54</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para><emphasis type="b">Positions 6, 7, and 8</emphasis> —Julian Date. <alphalist>
<li>Campuses will renumber using the same Julian date and year digit as the original DLN with the appropriate blocking series designated by Receipt and Control Operation and Accounting. </li>
<li>Coordinate with Receipt and Control Operation and Accounting to determine if specific Julian dates are used in your campus.</li>
</alphalist></para>
<para> Use the following chart for renumbering <citation type="Form">Form 1040</citation>, <citation type="Form">Form 1040-NR</citation>, and <citation type="Form">Form 1040-SS</citation>:<table frame="all" id="id337100765" orient="port" pgbrk="nobreak" restrict="norestrict" summary="Renumbering and preparing form 1332" width="4.5in">
<tgroup align="left" cols="2" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="43.20*"/>
<colspec colname="col2" colnum="2" colwidth="56.80*"/>
<thead valign="bottom">
<row>
<entry morerows="0" nameend="col1" namest="col1"><emphasis type="b"> If renumbering </emphasis></entry>
<entry morerows="0" nameend="col2" namest="col2"><emphasis type="b"> Then</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry morerows="0" nameend="col1" namest="col1">Form 1040</entry>
<entry morerows="0" nameend="col2" namest="col2">Prepare Form 1332.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para><emphasis type="b">Positions 9, 10, and 11</emphasis> —Blocking Series. For more information, follow <citation type="IRM">IRM 3.10.73</citation> <emphasis type="b">Batching and Numbering</emphasis>. The blocking series will be assigned sequentially beginning with 000 for each document code and Julian date except for the following documents: <alphalist>
<li>Forms 1040X numbered as Form 1040 (Document Code 11) must contain a block number from the following table:</li>
<table frame="all" id="id337101379" summary="1040X Block numbers">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Codes</emphasis></entry>
<entry valign="top"><emphasis type="b">Definition</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>970–989</entry>
<entry>G Coded, Amended 1040X</entry>
</row>
<row>
<entry>990–999</entry>
<entry>Presidential Election</entry>
</row>
</tbody>
</tgroup>
</table>
<li>Renumbered Forms 1040 with Document Code 11 must use block numbers 000–969. </li>
</alphalist><note notetype="note">If all available blocks have been used, number with a different File Location Code and start again with the lowest block number.</note></para>
<para><emphasis type="b">Positions 12 and 13</emphasis> —Serial Number. Number sequentially beginning with 00. Up to 100 documents may be blocked together. </para>
<para><emphasis type="b">Position 14</emphasis> —Year Digit. Enter the year for all prior year DLNs.</para>
</subsection2>
<subsection2 id="id337100435"><date>(01-01-2025)</date>
<title>Domestic and International Return Renumbering Procedures</title>
<para>All Domestic and International returns that require new DLNs are renumbered by Rejects. </para>
<para>Follow instructions in <seealso idref="id337101624">IRM 3.12.37.19.4.4</seealso> for assigning the new DLN.</para>
<para>Prepare Form 1332 for blocking the renumbered documents.</para>
<para>If an electronically filed return is being renumbered, ensure <emphasis type="b">MeF Return</emphasis> is written on the signature line(s) to avoid unnecessary correspondence. </para>
</subsection2>
<subsection2 id="id337100438"><date>(11-10-2021)</date>
<title>Suppression of Erroneous Balance Due and Delinquency Notices</title>
<para>Whenever a return or payment must be renumbered/re-input because the document had been input to the wrong MFT or tax period, immediate consideration must be given to the possibility that erroneous balance due or return delinquency notices may be issued.</para>
<para>IDRS action must be input to the correct account by the first person identifying the condition whenever any of the subsequent documents must be renumbered or re-input to correct MFT, TIN, or tax period: <alphalist>
<li>Any IMF return that is more than six months past the due date also requires CC FRM49 with TC 599–18.</li>
<li>Any subsequent payment transaction (Document Code 17, 18 or 19) requires input of CC STAUP (and the appropriate status) for six cycles. <note>Command Codes FRM49 and STAUP instructions can be found in <citation type="IRM">IRM 21.5.2.4.8.2.</citation></note></li>
</alphalist></para>
<para>When the TIN, name control, MFT, and tax period are present, but the returns are determined to be unprocessable, use TC 599 with Closing Code 17 to defer the normal delinquency.</para>
<para>Annotate the document with <emphasis type="b">599–17</emphasis>, <emphasis type="b">599–18</emphasis>, or <emphasis type="b">STAUP-6</emphasis> in the upper left margin. If the document has already been annotated, no further action is required.</para>
</subsection2>
</subsection1>
<subsection1 id="id337100439"><date>(11-10-2021)</date>
<title>Re-Entry Documents</title>
<para>This subsection lists the procedures for reentry documents.<bulletlist>
<li>Conditions for reentry</li>
<li>Preparation of documents for reentry</li>
<li>Preparation of Form 3893</li>
</bulletlist></para>
<subsection2 id="id337100440"><date>(04-09-2025)</date>
<title>Conditions for Re-Entry</title>
<para>Reenter all documents in which the record cannot be corrected due to limitations in existing computer programs. These uncorrectable conditions include <emphasis type="b">any</emphasis> of the following: <alphalist>
<li>DLN transcribed wrong on record.</li>
<li>Transaction amount transcribed incorrectly or is missing.</li>
<li>Transaction Code or MFT is missing or incorrect in the block header.</li>
<li>Non-ERS documents identified by Data Control for deletion from the reject inventory.</li>
</alphalist></para>
<para>Enter CC RJECT 630.</para>
<para>Ensure that the received date is present for each document to be re-entered. <alphalist>
<li>If the date is not stamped on the face of the document refer to <citation type="IRM">IRM 3.12.2.4.3.20</citation> to determine and edit the correct received date. </li>
<li>If the document is TY 2019 and prior and has not been cleared by Statute, follow instructions in <citation type="IRM">IRM 3.12.3.3.2.3</citation> </li>
</alphalist></para>
<para>Transaction Code 840 was not keyed in the header.</para>
<para>Rejects are a separate category on the SCCF. When a reject is reentered, a control record with a From-To Code 4–0 must post to the SCCF.</para>
<para>This 4–0 Code is produced automatically whenever CC RJECT 630 is input on the ERS terminal.</para>
<para>Prepare <citation type="Form">Form 4028</citation> and send re-entry documents along with Form 4028 to Accounting.</para>
</subsection2>
<subsection2 id="id337100441"><date>(04-09-2025)</date>
<title>Preparing Documents For Re-Entry</title>
<para>When a document is re-entered, it will be processed as an original entry document and sent back through the pipeline functions. </para>
<para>Therefore, all previous edit markings must be correct for current processing. Circle out any unnecessary Action Codes. </para>
<para>When a re-input document contains a CCC <emphasis type="b">O</emphasis> indicating a manual refund has been issued, or <citation type="Form">Form 3753</citation> or <citation type="Form">Form 5792</citation> is attached, research IDRS to see if a TC 840 or pending TC 840 is posted to the tax module with the following exceptions: <alphalist>
<li>If the CCC O is not edited in red, do not reissue a manual refund or research for a TC 840 on IDRS. Look at the history for an indication that the account is to be frozen, if unsure take the return to your lead.</li>
<li>If a TC 840 has posted or the module contains a pending TC 840, allow the CCC <emphasis type="b">O</emphasis> to remain on the return. Prepare <citation type="Form">Form 3893</citation> and re-enter the document.</li>
<li>If a TC 840 has not posted or there is no pending TC 840 on the module, reissue the manual refund using the instructions contained in this IRM. Hold the document until a pending TC 840 appears on the module. Prepare <citation type="Form">Form 3893</citation> and reenter the document.</li>
<note notetype="caution">Do not issue a manual refund if the TXMOD history indicates either a systemic or manual refund has been issued, e.g., F3753PREP, F5792PREP, TC 840 or TC 846. Take the return to your lead or manager. Also, look for a TC 971 AC 664, which indicates that a <citation type="Form">Form 3753</citation> manual refund has been sent.</note>
</alphalist></para>
<para>If the Transaction Code is 840 and Field 01BH is blank, the document must be reinput. Input CC RJECT 630, complete Form 3893 and in the remarks box type input TC 840 in the header.</para>
</subsection2>
<subsection2 id="id337100442"><date>(01-01-2023)</date>
<title>Preparing Form 3893</title>
<para><citation type="Form">Form 3893</citation> is prepared for a re-entry in block or portion of a re-entry block. Attach it to the first document in the re-entry block. Do not detach the form when processing unless a previously re-entered document is being re-entered again. </para>
<para>If a single previously re-entry document is being input again, attach the new <citation type="Form">Form 3893</citation> to the front of the document and the previously processed <citation type="Form">Form 3893</citation> to the back of the document.</para>
<para>When multiple documents within the same block are being input again, attach the new <citation type="Form">Form 3893</citation> to the document with the lowest serial number.</para>
<para>On subsequent serial numbers, attach previously processed <citation type="Form">Form 3893</citation> to the back of each document.</para>
<para>Follow the instructions in (6) through (26)</para>
<para>File Type-Check appropriate box.</para>
<para><emphasis type="b">Box 1</emphasis>— Alpha/Numeric Block Control Number. <bulletlist>
<li>Leave blank if routing to Batching in the Receipt and Control Operation.</li>
</bulletlist></para>
<para><emphasis type="b">Box 2</emphasis>— Document Locator Number. <bulletlist>
<li>Enter the eleven-digit block DLN. The complete DLN may be entered, but only the first eleven digits will be transcribed into the Block Header.</li>
</bulletlist></para>
<para><emphasis type="b">Box 3</emphasis>— Batch Number. <bulletlist>
<li>The batch number will be entered by Batching in the Receipt and Control Operation.</li>
</bulletlist></para>
<para><emphasis type="b">Box 4</emphasis>— Document Count. <bulletlist>
<li>Enter the number of documents attached to <citation type="Form">Form 3893</citation>.</li>
</bulletlist>.</para>
<para><emphasis type="b">Box 5</emphasis>— Credit.<bulletlist>
<li>Enter the amount of the credit transaction. If more than one document, enter the sum of the credit amounts.</li>
<li>If present, enter the total of the Primary and Tertiary amount. Amounts may be from remittance returns, payment transactions, transfer documents, or adjustments.</li>
</bulletlist></para>
<para><emphasis type="b">Box 6</emphasis>— Debit Amount.<bulletlist>
<li>Enter the total amount of the debits. This box must be blank if a credit amount is present.</li>
<li>Debit amounts may be present only with Document Codes 24, 45, 48, 54, 58, and 87.</li>
</bulletlist></para>
<para><emphasis type="b">Box 7</emphasis> —Transaction Code.<bulletlist>
<li>Enter only when Block Header Transaction Code is required.</li>
<table frame="all" id="id337101416" orient="port" pgbrk="nobreak" summary="Document codes and transaction codes " width="4.5in">
<tgroup align="left" cols="3" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="33*"/>
<colspec colname="col2" colnum="2" colwidth="33*"/>
<colspec colname="col3" colnum="3" colwidth="34*"/>
<thead valign="bottom">
<row>
<entry align="center" colsep="1" morerows="0" rowsep="1"><emphasis type="b">Document Code</emphasis></entry>
<entry align="center" colsep="1" morerows="0" rowsep="1"><emphasis type="b">Transaction Code on Document</emphasis></entry>
<entry align="center" colsep="1" morerows="0" rowsep="1"><emphasis type="b">Transaction Code in Block Header</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">45</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">840</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">840</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">53</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">090–092</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">090</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">51, 52</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">Transfer in</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">370</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">30</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">984, 986</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">984, 986</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">80</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">000, 012, 013, 014, 016</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">000, 010</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">81</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">000, 016</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">000, 016</entry>
</row>
</tbody>
</tgroup>
</table>
</bulletlist></para>
<para>For IRP, enter the Account Type Code followed by the Record Identification Code (F or G) followed by the Payer Count.</para>
<para><emphasis type="b">Box 8</emphasis> —Transaction Date.<bulletlist>
<li>Always enter the received date for Forms 1040-ES (Document Code 20) and 1040–C (Document Code 61). Enter received date for returns received after the tax period due date.</li>
<li>For other documents, the transaction date must be edited onto the actual document for it to be transcribed.</li>
</bulletlist></para>
<para><emphasis type="b">Box 9</emphasis>— Header MFT Code.<bulletlist>
<li>Enter only when required. </li>
<table frame="all" id="id337101417" orient="port" pgbrk="nobreak" summary="Document code MFT code and Header MFT codes" width="4.5in">
<tgroup align="left" cols="3" colsep="1" restrict="norestrict" rowsep="3">
<colspec colname="col1" colnum="1" colwidth="33*"/>
<colspec colname="col2" colnum="2" colwidth="33*"/>
<colspec colname="col3" colnum="3" colwidth="34*"/>
<thead valign="bottom">
<row>
<entry align="center" colsep="1" morerows="0" nameend="col1" namest="col1" rowsep="1"><emphasis type="b">Document Code</emphasis></entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1"><emphasis type="b">Document MFT</emphasis></entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1"><emphasis type="b">Header MFT</emphasis></entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">IRAF</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">29</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">29</entry>
</row>
<row>
<entry colsep="1" morerows="0" nameend="col1" namest="col1" restrict="norestrict" rowsep="1">ISRP Payments</entry>
<entry colsep="1" morerows="0" nameend="col2" namest="col2" restrict="norestrict" rowsep="1">Various</entry>
<entry colsep="1" morerows="0" nameend="col3" namest="col3" restrict="norestrict" rowsep="1">Same as document</entry>
</row>
</tbody>
</tgroup>
</table>
</bulletlist></para>
<para><emphasis type="b">Box 10</emphasis>— Secondary Amount.<bulletlist>
<li> Enter the secondary transaction amount when required. If you fail to enter the secondary money amount on the <citation type="Form">Form 3893</citation>, but the amount is edited on the document, there will be a block out of balance condition. </li>
<li>Place DR. or CR for the Secondary Amount.</li>
</bulletlist></para>
<para><emphasis type="b">Box 11</emphasis> — Reentry Source Code. Mark one box as indicated. <bulletlist>
<li>Mark <emphasis type="b">N</emphasis> for Nullified if the re-input document was previously an unpostable. Also, complete box 18.</li>
<li>Mark <emphasis type="b">4</emphasis> for re-input if the document has not posted or unposted at the Master File. Also, complete box 18.</li>
</bulletlist></para>
<para><emphasis type="b">Box 12</emphasis>— DLN Year Digit.<bulletlist>
<li>This box must be entered. Enter the 14th digit of the DLN from the source document. If the year digit is not shown on the document, determine the correct year from the DLN or from other information on the document.</li>
</bulletlist></para>
<para><emphasis type="b">Box 14</emphasis>— Remarks.<bulletlist>
<li>Enter any additional information needed to clarify the reason for re-input or to preserve a proper audit trail. For deletes, enter the cycle of the delete action.</li>
</bulletlist></para>
<para><emphasis type="b">Box 15</emphasis>— Process as Remittance or Non-remittance. <bulletlist>
<li>Mark the remittance box if the document or block contains money. </li>
<li>Adjustment Document, Doc. Code 54, is non-remittance even though header amounts may be present in box 5, 6 or 10.</li>
<li>All payment documents, and accounting transactions with Document Codes 24, 48, 51, 58, and 87 are remittance documents. </li>
</bulletlist></para>
<para><emphasis type="b">Box 16</emphasis>— Serial Number.<bulletlist>
<li>Enter the DLN serial number(s) of the documents being re-input.</li>
<li>For an entire block or multiple documents, enter the range of serial numbers, such as 00–49.</li>
</bulletlist></para>
<para><emphasis type="b">Box 17</emphasis>— Preparer Information.<bulletlist>
<li>Enter your name and phone number and the current date. Also mark the appropriate originating organization.</li>
</bulletlist></para>
<para><emphasis type="b">Box 18</emphasis>— Reentry Document.<bulletlist>
<li>If box 11 is <emphasis type="b">N</emphasis> or <emphasis type="b">4</emphasis>, mark the appropriate box.</li>
</bulletlist></para>
</subsection2>
</subsection1>
<subsection1 id="id337100874"><date>(01-01-2023)</date>
<title>Individual Retirement Account File (IRAF)</title>
<para>The Individual Retirement Account File (IRAF) and Master File were merged into the Individual Master File (IMF) as MFT 29. IRA MFT 29 accounts will be established when Forms 5329 are received with Forms 1040. IRA transactions may be input to post to establish MFT 29 accounts. These transactions include entity change adjustments, audit transactions, etc. IRA transactions will carry a Tax Class of Zero.</para>
<para>When <citation type="Form">Form 5329</citation> is received without <citation type="Form">Form 1040</citation>, a dummy <citation type="Form">Form 1040</citation> must be prepared with the following information to process <citation type="Form">Form 5329</citation> to MFT 29.<steplist>
<li>Write across the top of Form 1040 <emphasis type="b">Dummy to process Form 5329 to MFT 29</emphasis>.</li>
<li>Original to IMF <emphasis type="b">TC 150</emphasis> DLN.</li>
<li>Tax Period.</li>
<li>Name Control of Individual subject to additional tax.</li>
<li>Primary taxpayer’s SSN.</li>
<li>Secondary SSN (if applicable).</li>
<li>Filing status of Form 1040.</li>
<li>Tax Exempt Interest of Ordinary Dividends</li>
<li>Received date.</li>
<li>RPC <emphasis>“L”</emphasis>.</li>
<li>Amount on line 8 of Schedule 2, Form 1040.</li>
<li>Employee number who prepared the dummy return.</li>
</steplist></para>
<para>If Form 1040, Schedule 2 is received with an amount on line 8 and <citation type="Form">Form 5329</citation> is not attached, prepare a dummy <citation type="Form">Form 5329</citation> with the following information:<steplist>
<li>Write across the top of Form 5329, <emphasis type="b">Photocopy for input to MFT 29</emphasis>.</li>
<li>Spouse indicator (if FSC 2) edited to the left of the form name above the entity section of Form 5329 (<emphasis type="b">1</emphasis> if primary or <emphasis type="b">2</emphasis> if secondary).</li>
<li>The taxpayer's complete name (always a single name line), with a<emphasis type="b"> [</emphasis> (bracket) immediately in front of the proper last name.</li>
<li>Taxpayer's SSN.</li>
<li>IRA indicator of <emphasis type="q"><emphasis type="b">1</emphasis></emphasis> in the margin to the right of the address line on Form 5329.</li>
<li>Penalty amount as entered on line 58 of the Form 1040.</li>
</steplist></para>
<para>Use the original <emphasis type="b">TC 150</emphasis> DLN of the IMF account except when:<alphalist>
<li>The controlling DLN on the IMF account is a re-file DLN.</li>
<li>The Assessment Statute Expiration Date (ASED) of the original Form 1040 is within six months of expiration or expired.</li>
</alphalist></para>
<para>Prepare <citation type="Form">Form 3893</citation>, check the appropriate boxes.</para>
</subsection1>
<subsection1 id="id337101219"><date>(01-01-2020)</date>
<title>Early Filed Returns</title>
<para>A return is considered an early filed return when the return is received 5 months earlier than the due date of the tax return. </para>
<para>Correct any coding or transcription errors in received date or tax period fields.</para>
<para>Verify attachments, correspondence, taxpayer's date of death and follow taxpayer's intent for determining the correct tax period.</para>
<para>If it is determined the return is an Early Filed Decedent return, RJECT 610 and renumber the document using the current year DLN.</para>
<para>Do not delete the CCC Y from the early filed returns.</para>
<para>If both the primary and secondary taxpayer died during the tax period of the early filed return, enter A in Field 01CCC. </para>
<para>Ensure all prior year markings are circled out/removed.</para>
<para>Coordinate with Receipt and Control Operation and Accounting to determine correct DLN.</para>
</subsection1>
<subsection1 id="id337100444"><date>(01-01-2026)</date>
<title>Processing Aged Inventory</title>
<para>This subsection lists the procedures for reviewing aged cases.<bulletlist>
<li> Reject aged inventory</li>
<li>Closing aged and missing documents</li>
<li>SCCF aged items</li>
<li>On-line SCCF research</li>
</bulletlist></para>
<subsection2 id="id337100445"><date>(01-01-2026)</date>
<title>Reject Aged Inventory</title>
<para>The Reject Aged list is a report in Control-D that shows all registers in the below days in inventory range categories. The Reject Aged list (GMF 11-42) is a daily report and will be used to monitor and assign inventory.</para>
<para>The Aged List is divided into four different age groupings. <alphalist>
<li>45–59 days. </li>
<li>60-89 days</li>
<li>90–119 days </li>
<li>120 days and over</li>
</alphalist></para>
<para>If the reject register is not available in Control-D, use the file copy or reconstruct a new register.</para>
<para>The following ERS reports will be used to identify aged documents.<alphalist>
<li>The weekly ERS 31-40, Error Resolution <emphasis type="b">ERS Unworkable Suspense Aged Report</emphasis>, lists all documents currently in Unworkable Suspense that have been in the ERS system for 45 or more calendar days. </li>
<li>The weekly ERS 31-41, Error Resolution <emphasis type="b">ERS Workable Suspense Report</emphasis> lists all documents in Workable Suspense for 0 or more days.</li>
</alphalist></para>
<para>Correspondence status (e.g., 321 and 421) will be reviewed to determine the actual date the correspondence was issued and, if appropriate, processed as a No Reply.<note notetype="example">If a return is in activated status and there is no reply attached, the return may have been inadvertently activated and may be processed as a No Reply.</note></para>
<subsection3 id="id337100447"><date>(01-01-2026)</date>
<title>Closing Aged and Missing Documents</title>
<para>The person working the aged list must have a knowledgeable background on the research tools/listings applicable for the control of reject records.</para>
<para>Aged inventory will be worked daily first in first out (FIFO) according to days in ERS until all aged inventory is closed.</para>
<para>Locate all Aged reject and missing cases. <steplist>
<li>Search any files held by TEs or clerks within the Reject Unit.</li>
<li>Use CC ESTAB to request missing documents from Files. If ESTAB files request are unsuccessful, request special search using <citation type="Form">Form 2275</citation>.</li>
</steplist></para>
<para>If Files search to include special search are unsuccessful, follow instructions below:<alphalist>
<li>Research IDRS to look for a posted TC 150. If there is a posted TC 150, enter CC RJECT 640 to void the missing document. </li>
<li>If there is no posted TC 150, process the return to the best of your ability and follow No Reply instructions if applicable.</li>
</alphalist></para>
<para>For Document Codes 24, 45, 48, 58, or 87 credits or debits, research IDRS and/or <citation type="Form">Form 813</citation> to determine the proper application.<alphalist>
<li>If unable to determine the correct processing of credits or debits or cannot locate the document, contact RACS for a copy of the document. If after researching the case, a determination of how to process the case cannot be determined, contact the Accounting Operation for further instructions.</li>
</alphalist></para>
</subsection3>
</subsection2>
<subsection2 id="id337100449"><date>(05-10-2023)</date>
<title>SCCF Aged Items</title>
<para>Review the error and reject inventories on a weekly basis by reviewing the SCCF Aged Reports (SCF 07–50 and SCF 07–51) using Control D. Reports are generated on the first processing day of each new cycle and are available on the first workday of the new week (usually Friday). Reports will be worked at the beginning of the week and submitted to Accounting no later than 10:00am on Monday. </para>
<para>For SCCF purposes, Rejects includes both reject registers and ERS suspense records.</para>
<para>There will be no SCCF inventories aged over 3 months without a written explanation to the Data Control Unit.</para>
<para>Annotations will be specific and include:<bulletlist>
<li>Reason it is aged, ie., NU for nullified unpostable, or early filed return.</li>
<li>Date received in Rejects Inventory.</li>
<li>What action has been taken or will be taken to resolve the aged item.</li>
</bulletlist></para>
<para>Aged error items are on the same list and will also be resolved by Rejects with assistance from Error Resolution. <alphalist>
<li>Closed items from Error Correction will be annotated on the transcript. </li>
<li>If the DLN is not in the ERS/Rejects inventory, refer to Accounting.</li>
<li>If an aged item is determined to be open after online SCCF adjustment, refer to Accounting.</li>
</alphalist></para>
<para>Another portion of the SCCF Aged Transcript will be worked jointly between Rejects and Data Control. This is the <emphasis type="b">Aged Man Er/Rej Modules</emphasis>, SCF–07–51. This transcript includes aged blocks with <emphasis type="b">either</emphasis> of the following conditions: <alphalist>
<li>Open items in both SCCF manual balance and the error or reject balance. </li>
<li>Items that were coded as reentries by Rejects (From–To Code 4–0) and have no subsequent activity.</li>
</alphalist></para>
<para>SCCF aging is based on variable criteria. The following reject and error items are considered aged: <alphalist>
<li>Any return block with an open reject balance and no activity for 13 weeks. </li>
<li>Any non-return block with an open reject balance and no activity for 8 weeks.</li>
<li>Any block with open error balance for 4 weeks (8 weeks for IRP).</li>
<li>Any block that has been open on the SCCF for 26 weeks, regardless of activity (13 weeks for Document Codes 17, 18, and 19).</li>
</alphalist></para>
<subsection3 id="id337100450"><date>(01-01-2023)</date>
<title>Researching the SCCF Aged List</title>
<para>Notify Data Controls by the 20th of each month of any open rejects that have been in Rejects inventory for 90 days and are still being worked by other campus functions. The emphasis will be to close three months or more aged items quickly.</para>
<para>The SCCF is Data Control responsibility. However, to review SCCF aged items and perform other SCCF related duties, it is necessary to read and understand SCCF transcripts.</para>
<para> Work the SCCF Aged Listings at least twice a month.</para>
<para>Work the SCCF Aged list (SCF 07-50 and SCF 07-51) in coordination with the Reject Aged List to avoid duplication of efforts. Due to the variances in the aging criteria, items listed on the SCCF Aged Reports may not be aged in the Reject Inventory. </para>
<para>Annotate the SCCF Aged Lists with detailed explanations.<bulletlist>
<li>If the case will be closed before the next report is due, notate closed by and put the expected closing date.</li>
<li>If not, what form is it, what is the problem, and what is being done to resolve the issue, for example: Form 1040, missing return, special search.</li>
<li>Use ditto marks or vertical lines for identical remarks, to save time.</li>
<li>Provide a copy of the annotated report to the Data Control Team in Accounting.</li>
</bulletlist></para>
<para>Rejects is responsible for the research of aged items on the SCCF Reports that are in ERS and Reject Inventories. They will provide the status information to Data Control, so history items can be added to the SCCF transcript.<bulletlist>
<li>If the record is in ERS, locate the document and resolve quickly.</li>
<li>If the record is no longer in Rejects or ERS, research the closed listing to see the resolution.</li>
<li>If the record is no longer in Rejects and the document has not finished processing, check the ERS 05-40.</li>
<li>If the record was closed in error, prepare any necessary SCCF adjustments or obtain the document and re-input, if needed.<note notetype="caution">There will be no SCCF inventories aged over 3 months, without providing a written explanation to the Data Control Team.</note></li>
</bulletlist></para>
</subsection3>
<subsection3 id="id337100452"><date>(01-01-2023)</date>
<title>SCCF Transcript Format</title>
<para>The transcript format described here is used for all Master Files.</para>
<para>The original count and amount is the total for the block shown in the control record with From-To Code 0–0.<bulletlist>
<li>Code 7-0 is an increase</li>
<li>Code 8-0 is a decrease</li>
</bulletlist></para>
<para>The other balances on the transcript are manual, error, reject, and file delete. The reject balance will always agree with the count and amount of items on the reject file plus ERS suspense.</para>
<para>The Record Type ID Code identifies the type of record that posted to the SCCF. <bulletlist>
<li>0 = SCCF Adjustment Record (except renumber)</li>
<li>1 = Master Control Record</li>
<li>2 = BOB Control Record</li>
<li>4 = Generated SCCF Adjustment Record</li>
<li>5 = Delete or Reenter Block Proof Record</li>
<li>6 = Renumber Block Proof Record or Renumber Adjustment Record</li>
<li>7 = Good, Error, or Reject Block Proof Record</li>
</bulletlist></para>
<para>The From and To Codes show the effect on SCCF balances. If the From Code is 0–6, the standard meanings apply. <table frame="all" id="id337101294" summary="From and to codes to show the effect on SCCF balances" width="4.5in">
<tgroup cols="4" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="25*"/>
<colspec colname="col2" colwidth="25*"/>
<colspec colname="col3" colwidth="25*"/>
<colspec colname="col4" colwidth="25*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">From Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">To Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Meaning</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">SCCF Balance Affected</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>0</entry>
<entry>0</entry>
<entry>Raw data/re-input</entry>
<entry>Manual</entry>
</row>
<row>
<entry>1</entry>
<entry>1</entry>
<entry>BOBs</entry>
<entry>Manual</entry>
</row>
<row>
<entry>2</entry>
<entry>2</entry>
<entry>Deletes</entry>
<entry>Delete</entry>
</row>
<row>
<entry>3</entry>
<entry>3</entry>
<entry>Errors</entry>
<entry>Error</entry>
</row>
<row>
<entry>4</entry>
<entry>4</entry>
<entry>Rejects and ERS Suspense</entry>
<entry>Reject</entry>
</row>
<row>
<entry>5</entry>
<entry>5</entry>
<entry>Good Tape</entry>
<entry>None</entry>
</row>
<row>
<entry>6</entry>
<entry/>
<entry>Unpostables</entry>
<entry>None</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>When the From Code is 7, 8, or 9 special meanings apply. <table frame="all" id="id337101295" summary="From to code and meaning for 7 8 9" width="4.5in">
<tgroup cols="4" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="25*"/>
<colspec colname="col2" colwidth="25*"/>
<colspec colname="col3" colwidth="25*"/>
<colspec colname="col4" colwidth="25*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">From Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">To Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Meaning</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">SCCF Balance Affected</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>7</entry>
<entry>0</entry>
<entry>Increase the original balance</entry>
<entry>Suspense</entry>
</row>
<row>
<entry>8</entry>
<entry>0</entry>
<entry>Decrease the original balance</entry>
<entry>Suspense</entry>
</row>
<row>
<entry>7</entry>
<entry>7</entry>
<entry>Turn the ADSI On</entry>
<entry>None</entry>
</row>
<row>
<entry>8</entry>
<entry>7</entry>
<entry>Turn the ADSI Off</entry>
<entry>None</entry>
</row>
<row>
<entry>8</entry>
<entry>2</entry>
<entry>Remove the block from the SCCF</entry>
<entry>All</entry>
</row>
<row>
<entry>9</entry>
<entry>9</entry>
<entry>Information only</entry>
<entry>None</entry>
</row>
</tbody>
</tgroup>
</table><note notetype="note">Normally, these special codes are not used by Rejects. No corrected error or reject document can post to the Master File if the ADSI is on.</note></para>
<para>The re-input Source Code is: <bulletlist>
<li>N for nullified (rejected) unpostables</li>
<li>R for reprocessable</li>
<li>U for applications from the Unidentified Remittance File</li>
</bulletlist></para>
<para>The next fields are the SCCF posting tax year, Julian date, posting cycle, document count, serial number, and amount.</para>
<para>The cross-reference DLN is printed for any renumber record or new DLN created by a renumber record. The cross-reference serial number will print in the second serial number field.</para>
</subsection3>
</subsection2>
<subsection2 id="id337100453"><date>(01-01-2023)</date>
<title>On-Line SCCF Research</title>
<para>To access any DLN on the SCCF, enter CC SCFTR, space, followed by the Master File System Code, the Block DLN, and transmit.</para>
<para>The Master File System Codes are: <bulletlist>
<li>1 = IMF</li>
<li>2 = BMF</li>
<li>5 = IRP</li>
<li>6 = ANMF</li>
</bulletlist></para>
<para>The DLN must be entered as 12 numerics without hyphens or spaces.</para>
<para> If the DLN has been entered correctly and is open on the SCCF, the complete transcript is displayed. </para>
<para>The online control file will be updated continually by CC SCFAJ nightly from batch processing.</para>
<para>The Control File Block Status Code, field S on the transcript, identifies the current status of the block on the SCCF. The values are: <bulletlist>
<li>A = Active</li>
<li>D = Being deleted</li>
<li>H = Historic</li>
<li>I = Inactive (no open balances)</li>
<li>S = Shelved</li>
</bulletlist></para>
<para>The Control File Age Indicator shows the number of times that a block has been selected for SCCF age review. <alphalist>
<li>Each time the block is printed on the SCCF age transcript, the indicator is increased by one.</li>
<li>The indicator is never decreased except when the block is removed to the Historic.</li>
</alphalist></para>
<para>The Historic Cycle (HC) indicates the cycle that a block had previously gone to the Historic transcript.<note>To reactivate historical records, move the cursor below the historical record message and transmit. The record will be available on SCCF the next day.</note></para>
</subsection2>
</subsection1>
<subsection1 id="id337100465"><date>(01-01-2023)</date>
<title>Erroneous Prompt, Quick and Jeopardy Assessments</title>
<para>This subsection lists the procedures for resolving erroneous Prompt, Quick, and Jeopardy assessments.</para>
<para>Prompt, Quick and Jeopardy requests are expeditious assessments when a statute is near, or collection of taxes is in jeopardy. These pre-journalized transactions are numbered with a Doc Code 51. Erroneous assessments are sometimes made, and these assessments go unpostable. </para>
<subsection2 id="id337100466"><date>(03-17-2025)</date>
<title>Processing Instructions</title>
<para>Use the instructions in this subsection to correct duplicate Doc Code 51 assessments.</para>
<para>Tax examiners will research the TIN reported on Form 3552 to determine if the assessment is a complete and/or partial duplicate assessment. In order for the assessment to post all money that is being reversed must be in TXMOD. Research using CC TXMODA to verify the money has not already been reversed in full and/or part. <alphalist>
<li>If there is a TC 767 on Form 3552 and there are two TC 766’s in TXMOD, verify the total of the TC 766’s match the amount reported as a TC 767. If the money amounts match and have not been reversed the tax examiner will add another TC 767 to the register with money amount. See example below:<note notetype="example">The reported TC 767 amount is $6,771.00. Research shows a TC 766 for $4200.00 and a TC 766 for $2571.00. Tax examiner will add a TC 767 for $2571.00 and change the original TC 767 amount from $6771.00 to $4200.00 and the case will post.</note></li>
<li>If research shows the TC 767 money amount has already been reversed in full, the tax examiner will process Form 3552 as a complete abatement. Tax examiner will code the register with 2-R, notate cancel per research on Form 3552 and reach out to the originator to complete Form 1331-B. Once paperwork is received all paperwork will be sent to Accounting Data Control.</li>
<li>If research shows the TC 767 has not been reversed in full, the tax examiner will process assessment as a partial abatement. Tax examiner will code the register with 2-R and send Form 3552 as well as Form 1331-B to Accounting Data Control in order for the assessment to be reinput with the correct money amount.</li>
</alphalist></para>
<para>If you are unable to obtain the original <citation type="Form">Form 3552</citation> from RACS, follow the instructions below to create <citation type="Form">Form 3552</citation> from the information on the IMF Reject Register.<table frame="all" id="id337101522" summary="Instructions for completing Form 3552">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Title</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Input Information</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>Top Middle</entry>
<entry>In red ink, write Cancel per Research</entry>
</row>
<row>
<entry>Document Locator Number</entry>
<entry>Enter DLN printed on register</entry>
</row>
<row>
<entry>MFT</entry>
<entry>Enter MFT from paragraph C</entry>
</row>
<row>
<entry>Tax Period</entry>
<entry>Enter tax period from paragraph D</entry>
</row>
<row>
<entry>Assessment Date</entry>
<entry>Enter date from paragraph E</entry>
</row>
<row>
<entry>IDRS Number</entry>
<entry>Enter your 10-digit IDRS number</entry>
</row>
<row>
<entry>Notice Date</entry>
<entry>Enter the date from paragraph E</entry>
</row>
<row>
<entry>Name Control</entry>
<entry>Enter name control from paragraph A</entry>
</row>
<row>
<entry>Taxpayer Identifying Number</entry>
<entry>Enter SSN/EIN from paragraph B</entry>
</row>
<row>
<entry>Form Number</entry>
<entry>Enter Form 1040</entry>
</row>
<row>
<entry>Taxpayer</entry>
<entry>Enter taxpayers name control</entry>
</row>
<row>
<entry>Tax Period Ended</entry>
<entry>Enter the last day of the tax period listed in paragraph D<note notetype="example">Tax Period is 201712 the tax period ended would be 20171231</note></entry>
</row>
<row>
<entry>Reference, Box 31</entry>
<entry>Enter all dates listed in Sections 01-19, 30, and 40</entry>
</row>
<row>
<entry>TC, Box 32</entry>
<entry>Enter all transaction codes listed in Sections 01-19, 30, and 40</entry>
</row>
<row>
<entry>Assessment, Box 33</entry>
<entry>Enter all money amounts listed in Sections 01-19, 30, and 40</entry>
</row>
<row>
<entry>Balance Due</entry>
<entry>Input the total assessment amount in the 3rd box to the right of box 37</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para><citation type="Form">Form 1331-B</citation> must be completed to abate a duplicate assessment or portion of the assessment. Contact the originator with a request to complete <citation type="Form">Form 1331-B</citation>. If the tax examiner does not receive a response from the originator inform management and/or your local P&amp;A analyst for assistance in resolving this issue. Tax examiners will verify Form 1331-B has the following information:<table frame="all" id="id337101523" summary="Completing Form 1331-B">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Title</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Input Information</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>EIN/SSN</entry>
<entry>Enter the taxpayers TIN from Form 3552.</entry>
</row>
<row>
<entry>Form/MFT/Tax Period</entry>
<entry>Enter 1040, MFT and Tax Period from Form 3552.</entry>
</row>
<row>
<entry>Name and Address of taxpayer</entry>
<entry>Only enter the taxpayers name control from Form 3552.</entry>
</row>
<row>
<entry>Section I</entry>
<entry>Computation of liability. See example below of a partial abatement.<note notetype="example">Money amount of decrease from form. Money amount of available credit. Money amount to be removed from form for reinput.</note></entry>
</row>
<row>
<entry>Prepared by</entry>
<entry>Employee name.</entry>
</row>
<row>
<entry>Date</entry>
<entry>Date Form 1331-B was completed.</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Once all paperwork is completed, a <citation type="Form">Form 4028</citation> must be filled out with the below information.<steplist>
<li>Mark the correct Master File box on the top left.</li>
<li>From;To is 0-2.</li>
<li>Master File is 1 for IMF or 2 for BMF.</li>
<li>Input DLN from the top of the register without the document code.</li>
<li>Enter money amount under either credit or debit from the information on the register.</li>
<li>Under remarks input Abate assessment to 6510 account.</li>
</steplist></para>
<para>If the above instructions do not pertain to the issue presented on the register, contact the originator for resolution.<note>If the originator does not provide instructions to resolve the issue, elevate to management. The manager must contact the originators manager for resolution.</note></para>
</subsection2>
</subsection1>
<exhibit cols="1" id="id337100470"><exhibitnumber/><date>(01-01-2026)</date>
<title>Acronyms</title>
<table frame="all" id="id337100888" summary="Acronym and definitions A thru Z" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="37*"/>
<colspec colname="col2" colwidth="63*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Acronym </emphasis></entry>
<entry align="center" rowsep="1" valign="top"><emphasis type="b">Definition</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">A</emphasis></emphasis></entry>
<entry rowsep="1"/>
</row>
<row>
<entry align="center">AC</entry>
<entry>Action Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ABC</entry>
<entry rowsep="1">Alpha Block Control Number</entry>
</row>
<row>
<entry align="center">ACA</entry>
<entry>Affordable Care Act</entry>
</row>
<row>
<entry align="center">ACTC</entry>
<entry>Additional Child Tax Credit</entry>
</row>
<row>
<entry align="center">AOTC</entry>
<entry>Additional Other Child Tax Credit</entry>
</row>
<row>
<entry align="center">ARC</entry>
<entry>Affordable Care Act Reason Codes</entry>
</row>
<row>
<entry align="center">ACD</entry>
<entry>Audit Code</entry>
</row>
<row>
<entry align="center">ACS</entry>
<entry>Automated Collection System</entry>
</row>
<row>
<entry align="center">ADJ</entry>
<entry>Adjustment</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ADP</entry>
<entry rowsep="1">Automated Data Processing</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ADSI</entry>
<entry rowsep="1">Action Delete Status Indicator</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">AGI</entry>
<entry rowsep="1">Adjusted Gross Income </entry>
</row>
<row>
<entry align="center">ANMF</entry>
<entry>Automated Non-Masterfile</entry>
</row>
<row>
<entry align="center">ASED</entry>
<entry>Assessment Statute Expiration Date</entry>
</row>
<row>
<entry align="center">ASFR</entry>
<entry>Automated Substitute for Return</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ATIN</entry>
<entry rowsep="1">Adoption Taxpayer Identification Number </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">AUSPC</entry>
<entry rowsep="1">Austin Submission Processing Center</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">B</emphasis></emphasis></entry>
<entry rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">BBTS</entry>
<entry rowsep="1">Batch/Blocking Tracking System</entry>
</row>
<row>
<entry align="center">BDR</entry>
<entry>Balance Due Refund</entry>
</row>
<row>
<entry align="center">BFS</entry>
<entry>Bureau of the Fiscal Service</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">BMF</entry>
<entry rowsep="1">Business Master File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">BOB</entry>
<entry rowsep="1">Block out of Balance </entry>
</row>
<row>
<entry align="center">BOE</entry>
<entry>Business Enterprise Object Review</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">C</emphasis></emphasis></entry>
<entry rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">CADE</entry>
<entry rowsep="1">Customer Account Data Engine </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">CAF</entry>
<entry rowsep="1">Centralized Authorization File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">CAS</entry>
<entry rowsep="1">Correspondence Action Sheet</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">CCC</entry>
<entry rowsep="1">Computer Condition Code </entry>
</row>
<row>
<entry align="center">CFOL</entry>
<entry>Corporate Files on Line</entry>
</row>
<row>
<entry align="center">CMODE</entry>
<entry>Change Mode</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">CP</entry>
<entry rowsep="1">Computer Paragraph</entry>
</row>
<row>
<entry align="center">CTC</entry>
<entry>Child Tax Credit</entry>
</row>
<row>
<entry align="center">CW</entry>
<entry>Classified Waste</entry>
</row>
<row>
<entry align="center">CY</entry>
<entry>Current Year</entry>
</row>
<row>
<entry align="center">CZ</entry>
<entry>Combat Zone</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">D</emphasis></emphasis></entry>
<entry rowsep="1"/>
</row>
<row>
<entry align="center">DCF</entry>
<entry>Dishonored Check File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">DDb</entry>
<entry rowsep="1">Dependent database</entry>
</row>
<row>
<entry align="center">DECD</entry>
<entry>Deceased </entry>
</row>
<row>
<entry align="center">DLN</entry>
<entry>Document Locator Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">DPC</entry>
<entry colsep="1" rowsep="1">Designated Payment Code </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">DSI</entry>
<entry colsep="1" rowsep="1">Dependent Status Indicator </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">E</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">EC</entry>
<entry>Error Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ECC-MTB</entry>
<entry colsep="1" rowsep="1">Enterprise Computing Center at Martinsburg Computing Center</entry>
</row>
<row>
<entry align="center">EFDS</entry>
<entry>Electronic Fraud Detection System</entry>
</row>
<row>
<entry align="center">EFTPS</entry>
<entry>Electronic Federal Tax Payment System</entry>
</row>
<row>
<entry align="center">e.g.,</entry>
<entry>For Example</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EIC</entry>
<entry colsep="1" rowsep="1">Earned Income Credit </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EIF</entry>
<entry colsep="1" rowsep="1">Entity Index File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EIN</entry>
<entry colsep="1" rowsep="1">Employer Identification Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EMT</entry>
<entry colsep="1" rowsep="1">Erroneous Manual Refund tool</entry>
</row>
<row>
<entry align="center">EPMF</entry>
<entry>Employee Plans Master File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ERS</entry>
<entry colsep="1" rowsep="1">Error Resolution System</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ES</entry>
<entry colsep="1" rowsep="1">Estimated Tax</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EQSP</entry>
<entry colsep="1" rowsep="1">Embedded Quality Submission Processing</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">EXC</entry>
<entry colsep="1" rowsep="1">Excess Collections</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">F</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FF</entry>
<entry colsep="1" rowsep="1">Frivolous Filer</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FICA</entry>
<entry colsep="1" rowsep="1">Federal Insurance Contributions Act</entry>
</row>
<row>
<entry align="center">FIRPTA</entry>
<entry>Foreign Investment in Real Property Tax Act of 1980</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FLC</entry>
<entry colsep="1" rowsep="1">File Location Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FS</entry>
<entry colsep="1" rowsep="1">Filing Status </entry>
</row>
<row>
<entry align="center">FTD</entry>
<entry>Federal Tax Deposit</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FTF</entry>
<entry colsep="1" rowsep="1">Failure to File</entry>
</row>
<row>
<entry align="center">FTHBC</entry>
<entry>First Time Homebuyer Credit</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FTP</entry>
<entry colsep="1" rowsep="1">Failure to Pay</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">FY</entry>
<entry colsep="1" rowsep="1">Fiscal Year</entry>
</row>
<row>
<entry align="center">FYM</entry>
<entry>Fiscal Year Month</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">G</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">GMF</entry>
<entry colsep="1" rowsep="1">Generalized Mainline Framework</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">GUF</entry>
<entry colsep="1" rowsep="1">Generalized Unpostable Framework</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">H</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">HCTC</entry>
<entry>Health Coverage Tax Credit</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">HSH</entry>
<entry colsep="1" rowsep="1">Household Employee</entry>
</row>
<row>
<entry align="center">HSTG</entry>
<entry>Hostage Indicator</entry>
</row>
<row>
<entry align="center">HQ</entry>
<entry>Headquarters</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">I</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">IAT</entry>
<entry>Integrated Automation Technologies</entry>
</row>
<row>
<entry align="center">ICO</entry>
<entry>Input Correction Operation </entry>
</row>
<row>
<entry align="center">ICT</entry>
<entry>Image Control Team</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IDRS</entry>
<entry colsep="1" rowsep="1">Integrated Data Retrieval System</entry>
</row>
<row>
<entry align="center">IDT</entry>
<entry>Identity Theft</entry>
</row>
<row>
<entry align="center">ILITS</entry>
<entry>Input Correction Operation Letter Inventory Tools</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IMF</entry>
<entry colsep="1" rowsep="1">Individual Master File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRA</entry>
<entry colsep="1" rowsep="1">Individual Retirement Arrangement </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRAF</entry>
<entry colsep="1" rowsep="1">Individual Retirement Account File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRC</entry>
<entry colsep="1" rowsep="1">Internal Revenue Code </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRM</entry>
<entry colsep="1" rowsep="1">Internal Revenue Manual</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRP</entry>
<entry colsep="1" rowsep="1">Information Returns Processing </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">IRS</entry>
<entry colsep="1" rowsep="1">Internal Revenue Service </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ISRP</entry>
<entry colsep="1" rowsep="1">Integrated System Remittance Processing </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ITIN</entry>
<entry colsep="1" rowsep="1">Individual Taxpayer Identification Number </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">K</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">KCSPC</entry>
<entry colsep="1" rowsep="1">Kansas City Submission Processing Campus</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">KITA</entry>
<entry colsep="1" rowsep="1">Killed in Terrorist Action </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">M</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">MeF</entry>
<entry>Modernized Electronic File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">MFA</entry>
<entry colsep="1" rowsep="1">Married Filing Alien</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">MFJ</entry>
<entry colsep="1" rowsep="1">Married Filing Joint</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">MFS</entry>
<entry colsep="1" rowsep="1"><br/>a) Married Filing Separately <br/>b) Multiple Filing Status </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">MFT</entry>
<entry colsep="1" rowsep="1">Master File Tax</entry>
</row>
<row>
<entry align="center">MISC</entry>
<entry>Miscellaneous</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">N</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">NARA</entry>
<entry>National Archives and Records Administration</entry>
</row>
<row>
<entry align="center">NAP</entry>
<entry>National Account Profile</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">NC</entry>
<entry colsep="1" rowsep="1">Name Control</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ANMF</entry>
<entry colsep="1" rowsep="1">Automated Non Master File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">NRA</entry>
<entry colsep="1" rowsep="1">Non Resident Alien</entry>
</row>
<row>
<entry align="center">NU</entry>
<entry>Nullified Unpostable</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">O</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">OAR</entry>
<entry>Operations Assistance Request</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">ODC</entry>
<entry colsep="1" rowsep="1"><br/>Credit for Other Dependents</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">OSPC</entry>
<entry colsep="1" rowsep="1">Ogden Submission Processing Campus</entry>
</row>
<row>
<entry align="center">OTN</entry>
<entry>TOP Offset Trace Number</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">P</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">PAO</entry>
<entry>Process as Original</entry>
</row>
<row>
<entry align="center">PII</entry>
<entry>Personally Identifiable Information</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">POA</entry>
<entry colsep="1" rowsep="1">Power of Attorney</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">POD</entry>
<entry colsep="1" rowsep="1">Post of Duty </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">POW/MIA</entry>
<entry colsep="1" rowsep="1">Prisoner of War/Missing in Action</entry>
</row>
<row>
<entry align="center">P-SSN</entry>
<entry>Primary Social Security Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">P-TIN</entry>
<entry colsep="1" rowsep="1">Primary Taxpayer Identification Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">PY</entry>
<entry colsep="1" rowsep="1">Prior Year</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">R</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center">RCS</entry>
<entry>Document 12990, Records Control Schedules </entry>
</row>
<row>
<entry align="center">RDD</entry>
<entry>Return Due Date</entry>
</row>
<row>
<entry align="center">RICS</entry>
<entry>Return Integrity and Compliance Services</entry>
</row>
<row>
<entry align="center">RIVO</entry>
<entry>Return Integrity Verification Operations</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">RPC</entry>
<entry colsep="1" rowsep="1">Return Processing Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">RPD</entry>
<entry colsep="1" rowsep="1">Return Processing Date</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">RPS</entry>
<entry colsep="1" rowsep="1">Remittance Processing System</entry>
</row>
<row>
<entry align="center">RRP</entry>
<entry>Return Review Program</entry>
</row>
<row>
<entry align="center">RSED</entry>
<entry>Refund Statute Expiration Date</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">RSN</entry>
<entry colsep="1" rowsep="1">Reject Sequence Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">RTR</entry>
<entry colsep="1" rowsep="1">Remittance Transaction Research System</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">S</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">SCCF</entry>
<entry colsep="1" rowsep="1">Service Center Control File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">SCRIPS</entry>
<entry colsep="1" rowsep="1">Service Center Recognition/Image Processing System</entry>
</row>
<row>
<entry align="center">SCRS</entry>
<entry>Service Center Replacement System</entry>
</row>
<row>
<entry align="center">SERP</entry>
<entry>Servicewide Electronic Research Program</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">SFR</entry>
<entry colsep="1" rowsep="1">Substitute For Return</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">SPC</entry>
<entry colsep="1" rowsep="1"><br/>a) Submission Processing Center<br/>b) Special Processing Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">SSN</entry>
<entry colsep="1" rowsep="1">Social Security Number</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">S-SSN</entry>
<entry colsep="1" rowsep="1">Secondary Social Security Number</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">T</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TAS</entry>
<entry colsep="1" rowsep="1">Taxpayer Advocate Service </entry>
</row>
<row>
<entry align="center">TBOR</entry>
<entry>Taxpayer Bill of Rights</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TC</entry>
<entry colsep="1" rowsep="1">Transaction Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TE</entry>
<entry colsep="1" rowsep="1">Tax Examiner </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TIN</entry>
<entry colsep="1" rowsep="1">Taxpayer Identification Number </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TP</entry>
<entry colsep="1" rowsep="1">Taxpayer </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TPNC</entry>
<entry colsep="1" rowsep="1">Taxpayer Notice Code</entry>
</row>
<row>
<entry align="center">TPP</entry>
<entry>Taxpayer Protection Program</entry>
</row>
<row>
<entry align="center">TS</entry>
<entry>Taxpayer Services</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TXPD</entry>
<entry colsep="1" rowsep="1">Tax Period</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">TY</entry>
<entry colsep="1" rowsep="1">Tax Year</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="q">U</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">UPC</entry>
<entry colsep="1" rowsep="1">Unpostable Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">URC</entry>
<entry colsep="1" rowsep="1">Unpostable Resolution Code</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">URF</entry>
<entry colsep="1" rowsep="1">Unidentified Remittance File</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="q"><emphasis type="b">X</emphasis></emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry align="center" colsep="1" rowsep="1">XSF</entry>
<entry colsep="1" rowsep="1">Excess Collection File</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100471"><exhibitnumber/><date>(01-01-2025)</date>
<title>ERS and Rejects Action Codes</title>
<para>The ERS and Rejects Action codes indicates that specific information is missing, suspended, or removed from processing.</para>
<para>Only one action code can be assigned at a time to a record.</para>
<table frame="all" id="id337100893" summary="Use of Action codes on ERS Records" width="6.625in">
<tgroup cols="9" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="7.37in"?>
<colspec colname="COLSPEC0" colwidth="10*"/>
<colspec colname="col1" colwidth="18*"/>
<colspec colname="col2" colwidth="15*"/>
<colspec colname="col3" colwidth="9*"/>
<colspec colname="COLSPEC2" colwidth="8*"/>
<colspec colname="COLSPEC3" colwidth="9*"/>
<colspec colname="COLSPEC4" colwidth="10*"/>
<colspec colname="col4" colwidth="10*"/>
<colspec align="center" colname="COLSPEC1" colwidth="11*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Action Code </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definition </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Suspense Period, Bus. Days</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top">Valid for C&amp;E</entry>
<entry align="center" valign="top">Valid for Error Corr.</entry>
<entry align="center" valign="top">Valid for Susp Corr.</entry>
<entry align="center" valign="top">Valid for NWDLN</entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Valid for RJECT</emphasis></entry>
<entry valign="top">Calendar Days</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">In-House to ERS </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">001</entry>
<entry colsep="1" rowsep="1">Input Document</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Taxpayer Correspondence </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">211</entry>
<entry colsep="1" rowsep="1">First Correspondence</entry>
<entry align="center" colsep="1" rowsep="1">40</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>55–58</entry>
</row>
<row>
<entry align="center">212</entry>
<entry colsep="1" rowsep="1">Second Correspondence</entry>
<entry align="center" colsep="1" rowsep="1">25</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>34–37</entry>
</row>
<row>
<entry align="center">213</entry>
<entry colsep="1" rowsep="1">Health Coverage Tax Credit (HCTC) Correspondence (EC 358)</entry>
<entry align="center" colsep="1" rowsep="1">40</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>55–58</entry>
</row>
<row>
<entry align="center">215</entry>
<entry colsep="1" rowsep="1">International Correspondence </entry>
<entry align="center" colsep="1" rowsep="1">45</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>62–65</entry>
</row>
<row>
<entry align="center">216</entry>
<entry>International Second Taxpayer Correspondence</entry>
<entry align="center">45</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>62-65</entry>
</row>
<row>
<entry align="center">217</entry>
<entry>International Correspondence </entry>
<entry align="center">45</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>62-65</entry>
</row>
<row>
<entry align="center">224</entry>
<entry colsep="1" rowsep="1">Affordable Care Act (ACA) Correspondence </entry>
<entry align="center" colsep="1" rowsep="1">40</entry>
<entry colsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1">no</entry>
<entry>55–58</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">In-House Research </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">300</entry>
<entry colsep="1" rowsep="1">IRC 965</entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center">310</entry>
<entry colsep="1" rowsep="1">Statute Control</entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center">320</entry>
<entry colsep="1" rowsep="1">Entity Control</entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center"/>
<entry><emphasis type="b">EXAM/CI/RIVO Review</emphasis></entry>
<entry align="center"/>
<entry/>
<entry/>
<entry/>
<entry/>
<entry align="center"/>
<entry/>
</row>
<row>
<entry align="center">331</entry>
<entry colsep="1" rowsep="1">Frivolous Filer Review</entry>
<entry align="center" colsep="1" rowsep="1">03</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>4–7</entry>
</row>
<row>
<entry align="center">332</entry>
<entry colsep="1" rowsep="1">CI Review</entry>
<entry align="center" colsep="1" rowsep="1">03</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>4–7</entry>
</row>
<row>
<entry align="center">335</entry>
<entry colsep="1" rowsep="1">Frivolous (FRP) Case</entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center">370 </entry>
<entry>Examination </entry>
<entry align="center">10</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>13-16</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Accounting</emphasis>					</entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">341</entry>
<entry colsep="1" rowsep="1">Manual Refund-Accounting </entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center">343</entry>
<entry colsep="1" rowsep="1">Other Accounting </entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">TIN/Entity Research</emphasis>					</entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">351</entry>
<entry colsep="1" rowsep="1">TIN Research</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">360</entry>
<entry colsep="1" rowsep="1">Other In-House Research/FIRTPA </entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13–16</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Management Suspense</emphasis> 					</entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">410</entry>
<entry align="left" colsep="1" rowsep="1">Assistance Needed</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">420</entry>
<entry align="left" colsep="1" rowsep="1">Management Suspense-A</entry>
<entry align="center" colsep="1" rowsep="1">05</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>8-11</entry>
</row>
<row>
<entry align="center">430</entry>
<entry align="left" colsep="1" rowsep="1"> Management Suspense-B/Form 8958 Community Property/Allocation</entry>
<entry align="center" colsep="1" rowsep="1">10</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>13-16</entry>
</row>
<row>
<entry align="center">440</entry>
<entry align="left" colsep="1" rowsep="1">Management Suspense-C </entry>
<entry align="center" colsep="1" rowsep="1">15</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>20-23</entry>
</row>
<row>
<entry align="center">450</entry>
<entry align="left" colsep="1" rowsep="1"> Management Suspense D, HCTC </entry>
<entry align="center" colsep="1" rowsep="1">20</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>27-30</entry>
</row>
<row>
<entry align="center">460</entry>
<entry align="left" colsep="1" rowsep="1">Management Suspense-E</entry>
<entry align="center" colsep="1" rowsep="1">25</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>34-37</entry>
</row>
<row>
<entry align="center">470</entry>
<entry align="left" colsep="1" rowsep="1">Complex Error Codes </entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">471</entry>
<entry align="left" colsep="1" rowsep="1">HQ Suspense</entry>
<entry align="center" colsep="1" rowsep="1">02</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>5-8</entry>
</row>
<row>
<entry align="center">480</entry>
<entry align="left" colsep="1" rowsep="1">Early Filed Suspense</entry>
<entry align="center" colsep="1" rowsep="1">150</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>211-218</entry>
</row>
<row>
<entry align="center">481</entry>
<entry align="left">ERS Bypass</entry>
<entry align="center">01</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>01</entry>
</row>
<row>
<entry align="center">484</entry>
<entry align="left">Bypass Reject</entry>
<entry align="center">01</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>01</entry>
</row>
<row>
<entry align="center">490</entry>
<entry align="left" colsep="1" rowsep="1">System Problem</entry>
<entry align="center" colsep="1" rowsep="1">05</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>8-11</entry>
</row>
<row>
<entry align="center"/>
<entry><emphasis type="b">HQ Requested Suspense Only</emphasis></entry>
<entry align="center"/>
<entry/>
<entry/>
<entry/>
<entry/>
<entry align="center"/>
<entry/>
</row>
<row>
<entry align="center">491</entry>
<entry>System Problems HCTC, EC 358 PY</entry>
<entry align="center">10 </entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>13-16</entry>
</row>
<row>
<entry align="center">492</entry>
<entry>Complex Systemic Issue ACA, EC 011 and EC 750</entry>
<entry align="center">15</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>20-23</entry>
</row>
<row>
<entry align="center">493 </entry>
<entry>Complex Systemic Issue ACA Systemic Issues, EC 067</entry>
<entry align="center">20</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>27-30</entry>
</row>
<row>
<entry align="center">494</entry>
<entry>Complex Systemic Issue EC 029 Credit Transfer </entry>
<entry align="center">25</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>34-37</entry>
</row>
<row>
<entry align="center">495</entry>
<entry>Complex Systemic Issue ACA BOE Research</entry>
<entry align="center">30</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>41-45</entry>
</row>
<row>
<entry align="center">496</entry>
<entry>Complex Systemic Issue</entry>
<entry align="center">35</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>48-51</entry>
</row>
<row>
<entry align="center">497</entry>
<entry>Complex Systemic Issue</entry>
<entry align="center">40</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>55-58</entry>
</row>
<row>
<entry align="center">498</entry>
<entry>Complex Systemic Issue</entry>
<entry align="center">45</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>62-65</entry>
</row>
<row>
<entry align="center">499</entry>
<entry>Complex Systemic Issue</entry>
<entry align="center">50</entry>
<entry>no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center">no</entry>
<entry>69-72</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Missing Document </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">511</entry>
<entry colsep="1" rowsep="1">Missing Document 1st Suspense</entry>
<entry align="center" colsep="1" rowsep="1">25</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>34-37</entry>
</row>
<row>
<entry align="center"/>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Rejects</emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">610</entry>
<entry align="left" colsep="1" rowsep="1"> Renumber (CC NWDLN)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>yes</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">611</entry>
<entry align="left" colsep="1" rowsep="1"> Remittance Renumber (CC NWDLN)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>yes</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">620</entry>
<entry align="left" colsep="1" rowsep="1"> ANMF/Non-ADP (CC RJECT)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry align="center" colsep="1" rowsep="1">yes</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">630</entry>
<entry align="left" colsep="1" rowsep="1"> Re-Input (CC RJECT)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">yes</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">640</entry>
<entry align="left" colsep="1" rowsep="1"> Void (CC RJECT)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry align="center" colsep="1" rowsep="1">yes</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">651</entry>
<entry align="left" colsep="1" rowsep="1"> International Document (AUSPC) (CC RJECT)</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry>yes</entry>
<entry align="center" colsep="1" rowsep="1">yes</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">660</entry>
<entry align="left"> Data Control Delete (TEP Delete) (CC RJECT)</entry>
<entry align="center">00</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center"> yes</entry>
<entry>0</entry>
</row>
<row>
<entry align="center"/>
<entry align="left" colsep="1" rowsep="1"><emphasis type="b">Duplicate DLN </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">700</entry>
<entry align="left" colsep="1" rowsep="1"> Dup. Block DLN</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center">711</entry>
<entry align="left" colsep="1" rowsep="1"> Dup. Doc. DLN from Code &amp; Edit </entry>
<entry align="center" colsep="1" rowsep="1">NA</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>NA</entry>
</row>
<row>
<entry align="center">712</entry>
<entry align="left" colsep="1" rowsep="1"> Dup. Doc. DLN from Error Resolution </entry>
<entry align="center" colsep="1" rowsep="1">NA</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>NA</entry>
</row>
<row>
<entry align="center">713</entry>
<entry align="left" colsep="1" rowsep="1"> Dup. Doc. DLN from Unpostables</entry>
<entry align="center" colsep="1" rowsep="1">NA</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>NA</entry>
</row>
<row>
<entry align="center">715</entry>
<entry align="left" colsep="1" rowsep="1"> Dup. Doc. DLN from Workable Suspense </entry>
<entry align="center" colsep="1" rowsep="1">NA</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>NA</entry>
</row>
<row>
<entry align="center"/>
<entry align="left" colsep="1" rowsep="1"/>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">800</entry>
<entry align="left" colsep="1" rowsep="1">NAP Outage </entry>
<entry align="center" colsep="1" rowsep="1">02</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>yes</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>5-8</entry>
</row>
<row>
<entry align="center"/>
<entry align="left" colsep="1" rowsep="1"><emphasis type="b">Unpostable Records </emphasis></entry>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
<row>
<entry align="center">900</entry>
<entry align="left" colsep="1" rowsep="1"> Unpostable Record</entry>
<entry align="center" colsep="1" rowsep="1">00</entry>
<entry colsep="1" rowsep="1">no</entry>
<entry>no</entry>
<entry>no</entry>
<entry>no</entry>
<entry align="center" colsep="1" rowsep="1">no</entry>
<entry>0</entry>
</row>
<row>
<entry align="center"/>
<entry align="left" colsep="1" rowsep="1"/>
<entry align="center" colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry/>
<entry/>
<entry/>
<entry align="center" colsep="1" rowsep="1"/>
<entry/>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit id="id337100846"><exhibitnumber/><date>(01-01-2020)</date>
<title>SSN Research</title>
<para>Command Code <emphasis type="b">NAMES</emphasis> is used to query the Name Search Facility (NSF) for an SSN. NAMES analyzes the input name and address to select potential matches. A primary or secondary filer's name can be used. Taxpayer names that have spelling and phonetic similarities to the requested name will also be checked. After entering CC NAMES and transmitting, the following screen displays to input information.</para>
<table frame="all" id="id337100895" summary="SSN Research using NAMES Input Format" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">NAMES </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Input Format</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">1) NAME</entry>
<entry colsep="1" rowsep="1">WINE, SIENNA</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2) ADDRESS*</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">3) CITY*</entry>
<entry colsep="1" rowsep="1">ST LOUIS</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4) STATE*</entry>
<entry colsep="1" rowsep="1">MO</entry>
</row>
<row>
<entry colsep="1" rowsep="1">5) ZIP*</entry>
<entry colsep="1" rowsep="1">63155</entry>
</row>
<row>
<entry colsep="1" rowsep="1">6) DOB*</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">7) COUNTRY*</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">* Optional entry</emphasis></entry>
<entry colsep="1" rowsep="1"/>
</row>
</tbody>
</tgroup>
</table>
<steplist>
<li>Taxpayer's name: Last, First, Middle</li>
<li>Complete street address if known. If address does not exactly match the address on Master File, you will <emphasis type="b">not</emphasis> get a match. </li>
<li>Full city name or two-digit Major City Code.</li>
<li> Two-digit State Code or blank. Blank will conduct a nationwide search. </li>
<li> Either three-digit or five-digit ZIP Code search.</li>
<li>Date of Birth: blank or MMDDYYYY format.</li>
<li>Full Country's Name: reserved for international use only.</li>
<blockpara>A response screen will display with the names, addresses, and SSNs as they were filed on the taxpayer's last return. Paging capabilities display to view multiple records. </blockpara>
</steplist>
<para>Command Code <emphasis type="b">NAMEI</emphasis> is used to query the local SKIF (SSN Key Index File) for an SSN. Definers are used only if specific master file records are to be displayed. Up to 10 characters of the last name and up to 6 characters of the first name may be entered. <table frame="all" id="id337100896" pgbrk="nobreak" summary="Command Code NAMEI Definer Codes" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definer Codes</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definer Codes </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">A</emphasis> - IRAF</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">N</emphasis> - ANMF</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">B</emphasis> - BMF</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">Q</emphasis> - INVALID SSNs</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">I </emphasis>- IMF</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">X</emphasis> - hard copy for a screen display that exceeds 30 pages </entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>Use the following chart to input the Command Code NAMEI</para>
<table frame="all" id="id337100979" summary="Command Code NAMEI input format" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="42*"/>
<colspec colname="col2" colwidth="58*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Use When</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Input Format</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">Full name and address are known</entry>
<entry colsep="1" rowsep="1">NAMEI BECKER,VIOLET,35203,4881 </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Only the first initial of the first name is known </entry>
<entry colsep="1" rowsep="1">NAMEI BECKER,V, 35203</entry>
</row>
<row>
<entry colsep="1" rowsep="1">First name is unknown</entry>
<entry colsep="1" rowsep="1">NAMEI BECKER,-,35203,4881</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Only address known is ZIP Code range</entry>
<entry colsep="1" rowsep="1">NAMEI BECKER,VIOLET,350–360</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Only address known is state</entry>
<entry colsep="1" rowsep="1">NAMEI BECKER,VIOLET,AL</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100473"><exhibitnumber/><date>(01-01-2020)</date>
<title>Refund/Filing Research</title>
<graphic id="id337100898"><file filename="33710113"/><descriptor>
<desc-para>This is an example of Command Code REINF. It shows an example of how to access the command code using a social security number. There is a box inside of the exhibit showing the fields that are completed. The Command Code SUMRY with Definer R is used to access Refund Information File. </desc-para>
</descriptor></graphic>
<graphic id="id337100796" pgbrk="nobreak" rotation="portrait"><file filename="33710114"/><descriptor>
<desc-para>This is an example of Command Code FFINQ. It displays the status codes 1-RAW, 2-BOBed, 3-Corrected BOB, 4-ERS, 5-Corrected ERS. There is a box inside of the exhibit with an arrow pointing to the status code field displaying 5. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100474"><exhibitnumber/><date>(01-01-2020)</date>
<title>Entity Research</title>
<para>Command Code <emphasis type="b">ENMOD</emphasis> provides name, address, and other entity information and serves as a preceding step to CCs <emphasis type="b">ENREQ</emphasis>, <emphasis type="b">BNCHG</emphasis>, and <emphasis type="b">INCHG</emphasis>. To access, input<emphasis type="b"> ENMOD</emphasis> 000–00–1234. Two sections of the <emphasis type="b">ENMOD</emphasis> response screen that are useful to Reject Tax Examiners are:</para>
<table frame="all" id="id337100899" summary="Command Code ENMOD use" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="49*"/>
<colspec colname="col2" colwidth="51*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">ENMOD Section</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Use </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">1) Pending Entity Transaction</entry>
<entry colsep="1" rowsep="1">1) Monitoring name and address changes</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2) Control and History Data</entry>
<entry colsep="1" rowsep="1">2) Research correspondence history and case control </entry>
</row>
</tbody>
</tgroup>
</table>
<para>Command Code <emphasis type="b">INOLE</emphasis> provides Master File entity data for a specific TIN from the National Account Profile (NAP). A definer is required. Command Code INOLE will be used before MFTRA is requested. </para>
<table frame="all" id="id337100900" summary="Command Code INOLE input format" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definer </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Input Format</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">G</emphasis> - Use when TIN type is unknown. Enter with an unedited or edited TIN.</entry>
<entry colsep="1" rowsep="1"><br/><emphasis type="b">INOLEG</emphasis>00009512<br/><emphasis type="b">INOLEG</emphasis>000– 00–5618</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">S</emphasis> - Use when the specific account is known (such as: SSN or IRAF).</entry>
<entry colsep="1" rowsep="1"><br/><emphasis type="b">INOLES</emphasis>000–00–8795 </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">T</emphasis> - Use on edited TIN and search will be done on all file types for the same SSN.</entry>
<entry colsep="1" rowsep="1"><br/><emphasis type="b">INOLET</emphasis>000–00–4592 </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">X</emphasis> - Use when researching TINs that have no Master File account.</entry>
<entry colsep="1" rowsep="1"><br/><emphasis type="b">INOLEX</emphasis>000–00–1953 </entry>
</row>
</tbody>
</tgroup>
</table>
<para>Command Code<emphasis type="b"> URINQ</emphasis> is used to research the Account 4620, Unidentified Remittance File (URF). Remittances less than one year old will be placed here when unidentifiable. Each unidentified record within the file contains the UR Control Number, DLN, amount, type of payment, status code, 3731 (C) notice indicator, name, address, TIN, and all available payments and follow up information. </para>
<para>Files can be researched in three different ways: by Name Control, amount of remittance, or DLN. If the DLN is not known, adding the File Location Code (FLC) to one of the other data elements will narrow the search. </para>
<table frame="all" id="id337100980" summary="command code URINQ research tool for Account 4620" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Use When</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Input Format</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">All elements are known</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">URINQ</emphasis><br/>SMIT<br/> 1,672.28<br/>00218-087-40019-X </entry>
</row>
<row>
<entry colsep="1" rowsep="1">To display complete URF matching the Name Control </entry>
<entry colsep="1" rowsep="1"><emphasis type="b">URINQ</emphasis><br/>SMIT<br/>00</entry>
</row>
<row>
<entry colsep="1" rowsep="1">The amount is known and the FLC</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">URINQ</emphasis><br/>2,468.30<br/>00 </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Only the DLN is known</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">URINQ</emphasis><br/>00218–079–60193–X </entry>
</row>
</tbody>
</tgroup>
</table>
<para>Command Code <emphasis type="b">XSINQ</emphasis> is used to research the Account 6800, Excess Collection File (XSF), and Account 9999, Revenue Clearance Accountability. Unidentifiable remittances more than one year old will be placed in one of these accounts. Each excess remittance record within the file contains the control number, amount and source of credit, IRS receive date, status code, other available payments and follow up information.</para>
<para>Files can be researched in three different ways: by Name Control, amount of remittance, or DLN. If the DLN is not known, adding the File Location Code (FLC) to one of the other data elements will narrow the search. </para>
<table frame="all" id="id337100981" summary="Command code XSINQ research tool for Account 6800 XSF" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Use When</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Input Format</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">All elements are known</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">XSINQ</emphasis><br/>SMIT<br/>1,672.28<br/>00218–087–40019–X </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Display complete XSF matching the Name Control </entry>
<entry colsep="1" rowsep="1"><emphasis type="b">XSINQ</emphasis><br/>SMIT</entry>
</row>
<row>
<entry colsep="1" rowsep="1">The amount is known and the FLC</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">XSINQ</emphasis><br/>2,468.30<br/>00 </entry>
</row>
<row>
<entry colsep="1" rowsep="1">Only the DLN is known</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">XSINQ</emphasis><br/>00218–087–23471-X </entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100475"><exhibitnumber/><date>(11-10-2021)</date>
<title>Entity Changes</title>
<graphic id="id337100800" pgbrk="nobreak" rotation="portrait"><file filename="33710118"/><descriptor>
<desc-para>This is an example of an Entity Screen. It displays the Input Format starting with Command Code ENMOD screen and following with ENREQ. The box at the bottom of the screen is a picture of an IDRS screen with an arrow pointing to the SSN. The displayed information gives the response CC INCHG to input for CC ENREQ with no data or dummy module info. </desc-para>
</descriptor></graphic>
<graphic id="id337100801" pgbrk="nobreak" rotation="portrait"><file filename="33710119"/><descriptor>
<desc-para>This is an example of an ENTITY change screen continued from the previous exhibit. Two boxes are displayed in the middle of the form displaying the taxpayers name with the appropriate bracket around the taxpayer's last name. The second box displays how to input an address change. At the bottom of the screen it displays how to enter the major city code in the following format; NY, 10001. </desc-para>
</descriptor></graphic>
<graphic id="id337100802" pgbrk="nobreak" rotation="portrait"><file filename="33710120"/><descriptor>
<desc-para>This is an example of how to establish an account on Master File. The reasons to input TC 000 to establish an account: No record is found on INOLE and a different SSN is not found through research. INOLE defaults to INOLEX with or without a matching name control. INOLE shows another taxpayer in on the valid Master File, but no invalid account is established. The response screen input the new name control, the primary name, address, year from the document, TC 000, filing status and remarks. The box at the bottom displays an ENTITY screen with all of the correct fields completed. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100476"><exhibitnumber/><date>(11-10-2021)</date>
<title>Researching Unpostables</title>
<graphic id="id337100803" pgbrk="nobreak" rotation="portrait"><file filename="33710121"/><descriptor>
<desc-para>This is an example of CC UPTIN. To access UPTIN enter UPTIN 000–00–4136. Example of response to CC UPTIN is showing with an IDRS screen with the correct response with all information input for UPTIN. Showing the name control, SSN/EIN, MFT&lt; TC 150, DT 20080714 and IDRS EMP. The second box is CC UPDIS. UPDIS displays all open unpostable cases for a specific unpostable sequence number. To access input the following UPDIS 200XX31006909.</desc-para>
</descriptor></graphic>
<graphic id="id337100804" pgbrk="nobreak" rotation="portrait"><file filename="33710122"/><descriptor>
<desc-para>This is an example of CC UPRES. This is the response to CC UPDIS. UPDIS is used to close a case with Unpostable Resolution Codes. The box in the middle displays and UPRES Screen for 200XX31006909. </desc-para>
</descriptor></graphic>
<graphic id="id337100805" pgbrk="nobreak" rotation="portrait"><file filename="33710123"/><descriptor>
<desc-para>This is an example of CC UPCAS. UPCAS is used to place or update unpostable case in suspense, request a document, or add information to aid in the resolution of an unpostable condition. UPCAS definers are: Z= used to input history items by Rejects for unpostable corrections. A= add history remarks, D= delete history remarks. The box displays an arrow pointing to the History Remarks field. </desc-para>
</descriptor></graphic>
<para><emphasis type="b">TERUP</emphasis> </para>
<para>Command Code <emphasis type="b">TERUP</emphasis> is used to delete previously input IDRS transactions from CCs <emphasis type="b">ADJ54, BNCHG, INCHG, DRT24, DRT48, FRM49, FRM77, FRM7A, and RFUND</emphasis>. An employee can only delete their own entries. It must be input the same day as the original transaction(s) and will not close control bases.</para>
<para>When a credit transfer is being rejected, only the Debit TIN will be input for deletion. The pending transaction code of the deleted transaction(s) will appear as DQ (deleted per Quality Review) the following day on the <emphasis type="b">TXMOD</emphasis> or <emphasis type="b">ENMOD</emphasis> display. Enter CC <emphasis type="b">TERUP</emphasis> followed by the sequence number of the transaction being deleted. A maximum of three sequence numbers may be deleted at a time.</para>
<para>To delete, input the following:<br/><emphasis type="b">TERUP</emphasis><br/>000001<br/>000002<br/>000003 </para>
<para>Example of the next day response screen:<br/>DQ 612 20XX0516 495.00 20XX22 00224–233–00001–X</para>
</exhibit>
<exhibit cols="1" id="id337100477"><exhibitnumber/><date>(01-01-2020)</date>
<title>Corporate Files On-Line Input Formats</title>
<para><emphasis type="b">CORPORATE FILES ON LINE INPUT FORMATS</emphasis> <table frame="all" id="id337100901" summary="Formats for Coporate files on line " width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="53*"/>
<colspec colname="col2" colwidth="47*"/>
<thead>
<row>
<entry valign="middle"><emphasis type="b">Corporate Files on line input formats</emphasis></entry>
<entry valign="top"><emphasis type="b">Codes</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry valign="middle"><emphasis type="b">KEY</emphasis><br/><emphasis type="b">+</emphasis> = Replace with definer as appropriate.<br/>Definer Codes are listed on the summary screens.<br/><emphasis type="b">nnn-nn-nnnn</emphasis> = SSN<br/><emphasis type="b">nnyyyymm </emphasis>= MFT Code &amp; Tax Period<br/><emphasis type="b">yyyymm</emphasis> = Tax Period<br/><emphasis type="b">yyyy</emphasis> = Tax Year<br/><emphasis type="b">x</emphasis>= TIN Type/Validity Indicator</entry>
<entry><emphasis type="b">Note:</emphasis> To specify TIN type, enter one of the following File Source Codes directly after the TIN.<br/><emphasis type="b">Blank</emphasis> = Valid SSN<br/><emphasis type="b">*</emphasis> = Invalid SSN<br/><emphasis type="b">D</emphasis> = Temporary TIN<br/><emphasis type="b">N</emphasis> = ANMF<br/><emphasis type="b">V</emphasis> = BMF valid SSN<br/><emphasis type="b">W</emphasis> = BMF invalid SSN<br/><emphasis type="b">P</emphasis> = IRAF valid SSN<br/><emphasis type="b">X</emphasis> = IRAF invalid SSN</entry>
</row>
<row>
<entry colsep="1" rowsep="1" valign="middle"><emphasis type="b">IRPTR</emphasis><br/>IRPTR+nnnnnnnnnxyyyy<br/><emphasis type="b">Definer Codes</emphasis>:<br/><emphasis type="b">E</emphasis> = Payee hardcopy transcript request<br/><emphasis type="b">H</emphasis> = Help Screen<br/><emphasis type="b"> L</emphasis> = IRPOL Summary request<br/><emphasis type="b">O</emphasis> = Payee on-line transcript request<br/><emphasis type="b">R</emphasis> = Payer hardcopy transcript request<br/><emphasis type="b">W</emphasis> = Payee on-line sanitized transcript request </entry>
<entry colsep="1" rowsep="1"><emphasis type="b">INOLE</emphasis><br/>INOLE+nnn-nn-nnnn<br/><emphasis type="b">G</emphasis> = TIN type unknown<br/><emphasis type="b">T</emphasis> = When TIN known, file source unknown.<br/><emphasis type="b">S</emphasis> = Specific account is known<br/><emphasis type="b">X</emphasis> = No MF account, cross-reference information </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">RTVUE/RTFTP</emphasis><br/>RTVUE nnn-nn-nnnn nnyyyymm ++<br/>RTFTP nnn-nn-nnnn nnyyyymm ++<br/>Refer to the <emphasis type="q">Command Code RTVUE Quick Reference Guide </emphasis>for a listing of the Definer Codes and their meanings.</entry>
<entry colsep="1" rowsep="1"><emphasis type="b">IMFOL</emphasis><br/><emphasis type="b"> H</emphasis> = Help screen<br/><emphasis type="b">?</emphasis> = Definer input formats<br/>IMFOL+nnn-nn-nnnn<br/><emphasis type="b">E</emphasis> = Entity Information<br/><emphasis type="b">I</emphasis> = All tax modules<br/><emphasis type="b">V</emphasis> = Vestigial data (retention register)<br/><emphasis type="b">Z</emphasis> = Audit history data<br/>IMFOL+nnn-nn-nnnn nnyyyymm<br/><emphasis type="b">A</emphasis> = Adjustment transaction<br/><emphasis type="b">R</emphasis> = Posted return<br/><emphasis type="b">S</emphasis> = =Status history data<br/><emphasis type="b"> T</emphasis> = Tax module information </entry>
</row>
</tbody>
</tgroup>
</table></para>
<para><emphasis type="b">COMMAND CODE RTVUE-QUICK REFERENCE GUIDE</emphasis><table frame="all" id="id337100902" summary="RTVUE quick reference guide" width="6.625in">
<tgroup cols="4" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="7.38in"?>
<colspec colname="col1" colwidth="14*"/>
<colspec colname="col2" colwidth="35*"/>
<colspec colname="col3" colwidth="15*"/>
<colspec colname="col4" colwidth="36*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b"> Definer </emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Main Return and Associated <emphasis type="u">Schedule</emphasis></emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Definer </emphasis></entry>
<entry align="center" rowsep="1" valign="top"><emphasis type="b">Associated <emphasis type="u">Form</emphasis></emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1">SM</entry>
<entry colsep="1">Summary Screen*</entry>
<entry colsep="1" rowsep="1">FT</entry>
<entry rowsep="1">Form 1116</entry>
</row>
<row>
<entry colsep="1" rowsep="0">DC</entry>
<entry colsep="1">Summary Screen, page 2</entry>
<entry colsep="1" rowsep="1">K1</entry>
<entry rowsep="1">Form 2441</entry>
</row>
<row>
<entry colsep="1" rowsep="0">R1</entry>
<entry colsep="1">Screen 1 of Return</entry>
<entry colsep="1" rowsep="1">L1</entry>
<entry rowsep="1">First Form 2555</entry>
</row>
<row>
<entry colsep="1">R2</entry>
<entry colsep="1">Screen 2 of Return</entry>
<entry colsep="1" rowsep="1">L2</entry>
<entry rowsep="1">Second Form 2555**</entry>
</row>
<row>
<entry colsep="1">R3<br/>R4</entry>
<entry colsep="1">Screen 3 of Return<br/>Screen 4 of Return</entry>
<entry colsep="1" rowsep="1">M1<br/>M2</entry>
<entry rowsep="1">Form 3800<br/>Page 2 screen</entry>
</row>
<row>
<entry colsep="1">R5<br/>R6<br/>R7</entry>
<entry colsep="1">Screen 5 of Return<br/>Screen 6 of Return<br/>Screen 7 of Return</entry>
<entry colsep="1" rowsep="1">N1<br/>N2<br/>N3 </entry>
<entry rowsep="1">Form 4136<br/>Page 2 screen<br/>Page 3 screen</entry>
</row>
<row>
<entry colsep="1" rowsep="1">R8</entry>
<entry colsep="1" rowsep="1">Screen 8 of Return</entry>
<entry colsep="1" rowsep="1">U1</entry>
<entry rowsep="1">First Form 4137</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SA <br/>A1</entry>
<entry colsep="1" rowsep="1">Schedule A, page 1 <br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">U2</entry>
<entry rowsep="1">Second Form 4137**</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SB</entry>
<entry colsep="1" rowsep="1">Schedule B</entry>
<entry colsep="1" rowsep="1">CZ</entry>
<entry colsep="1" rowsep="1">Form 4684</entry>
</row>
<row>
<entry colsep="1" rowsep="1">C1<br/>CA</entry>
<entry colsep="1" rowsep="1">First Schedule C<br/> Page 2 screen</entry>
<entry colsep="1" rowsep="1">P1</entry>
<entry colsep="1" rowsep="1">Form 4797</entry>
</row>
<row>
<entry colsep="1" rowsep="1">C2<br/>CB</entry>
<entry colsep="1" rowsep="1">Second Schedule C**<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">FR</entry>
<entry colsep="1" rowsep="1">Form 4835</entry>
</row>
<row>
<entry colsep="1" rowsep="1">C3<br/>CC</entry>
<entry colsep="1" rowsep="1">Third Schedule C***<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">ED</entry>
<entry colsep="1" rowsep="1">Form 4952</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SD<br/>D1</entry>
<entry colsep="1" rowsep="1">Schedule D<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">Q1</entry>
<entry colsep="1" rowsep="1">Form 4972</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SE<br/>E2</entry>
<entry colsep="1" rowsep="1">Schedule E<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">RY</entry>
<entry colsep="1" rowsep="1">First Form 5329</entry>
</row>
<row>
<entry colsep="1" rowsep="1">E1</entry>
<entry colsep="1" rowsep="1">Schedule EIC</entry>
<entry colsep="1" rowsep="1">RZ</entry>
<entry colsep="1" rowsep="1">Second Form 5329</entry>
</row>
<row>
<entry colsep="1" rowsep="1">F1<br/>FA</entry>
<entry colsep="1" rowsep="1">First Schedule F<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">SZ</entry>
<entry colsep="1" rowsep="1">Form 6198</entry>
</row>
<row>
<entry colsep="1" rowsep="1">F2<br/>FB</entry>
<entry colsep="1" rowsep="1">Second Schedule F**<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">T1<br/>T2</entry>
<entry colsep="1" rowsep="1">Form 6251<br/>Page 2 screen</entry>
</row>
<row>
<entry colsep="1" rowsep="1">H1<br/>HA</entry>
<entry colsep="1" rowsep="1">Schedule H<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">V2</entry>
<entry colsep="1" rowsep="1">Form 8586</entry>
</row>
<row>
<entry colsep="1" rowsep="1">H2<br/>HB</entry>
<entry colsep="1" rowsep="1">Second Schedule H**<br/>Page 2 screen</entry>
<entry colsep="1" rowsep="1">IR </entry>
<entry colsep="1" rowsep="1">Form 8606</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SJ</entry>
<entry colsep="1" rowsep="1">Schedule J</entry>
<entry colsep="1" rowsep="1">X1</entry>
<entry colsep="1" rowsep="1">Form 8615</entry>
</row>
<row>
<entry colsep="1" rowsep="1">SR</entry>
<entry colsep="1" rowsep="1">Schedule R</entry>
<entry colsep="1" rowsep="1">Z1</entry>
<entry colsep="1" rowsep="1">Form 8814</entry>
</row>
<row>
<entry colsep="1" rowsep="1">S1</entry>
<entry colsep="1" rowsep="1">First Schedule SE (Primary T/P)</entry>
<entry colsep="1" rowsep="1">AC</entry>
<entry colsep="1" rowsep="1">Form 8839</entry>
</row>
<row>
<entry colsep="1" rowsep="1">S2 </entry>
<entry colsep="1" rowsep="1">Second Schedule SE (Secondary T/P)**</entry>
<entry colsep="1" rowsep="1">W1</entry>
<entry colsep="1" rowsep="1">Form 8853</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">EC</entry>
<entry colsep="1" rowsep="1">Form 8863</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">DR</entry>
<entry colsep="1" rowsep="1">Form 8888</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Y1<br/>YA</entry>
<entry colsep="1" rowsep="1">First Form 8889<br/>Page 2 screen</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Y2<br/>YB</entry>
<entry colsep="1" rowsep="1">Second Form 8889**<br/>Page 2 screen</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">ET</entry>
<entry colsep="1" rowsep="1">Form 8913</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">TF</entry>
<entry colsep="1" rowsep="1">Form 8917</entry>
</row>
<row>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">TX</entry>
<entry colsep="1" rowsep="1">Form 8919</entry>
</row>
</tbody>
</tgroup>
</table></para>
<para>* Blank or invalid definers, or definers requesting an unavailable screen will default to the summary screen.</para>
<para>** If more than one filed</para>
<para>*** If more than two filed </para>
<table frame="all" id="id337100904" summary="Formats and definers for corporate files on line input" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<?PubTbl tgroup dispwid="7.38in"?>
<colspec colname="col1" colwidth="19*"/>
<colspec colname="col2" colwidth="81*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Code</emphasis></entry>
<entry valign="top"><emphasis type="b">Description</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry align="center"><emphasis type="b">A</emphasis></entry>
<entry>Adjustment transactions for the specified tax module</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">B</emphasis></entry>
<entry colsep="1" rowsep="1">Re-establish tax module onto Master File</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">E</emphasis></entry>
<entry colsep="1" rowsep="1">Posted entity transactions as well as various indicators and freeze codes for the specified SSN</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">H</emphasis></entry>
<entry colsep="1" rowsep="1">Help screen</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">I</emphasis></entry>
<entry colsep="1" rowsep="1">Index of all tax modules (on-line or off line) for the specified SSN</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">R</emphasis></entry>
<entry colsep="1" rowsep="1">Posted return for the tax module</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">S</emphasis></entry>
<entry colsep="1" rowsep="1">Status history data for the specified tax module </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">T</emphasis></entry>
<entry colsep="1" rowsep="1">Posted transactions and various other data for the specified tax module</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">V</emphasis></entry>
<entry colsep="1" rowsep="1">Vestigial section of the entity which indicates specified tax modules have been aged off to the retention register</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">Z</emphasis></entry>
<entry colsep="1" rowsep="1">Audit history data of the specified SSN</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">?</emphasis></entry>
<entry colsep="1" rowsep="1">Information screen containing a summary of definers and their input format</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100478"><exhibitnumber/><date>(01-01-2020)</date>
<title>Tax Account Information</title>
<graphic id="id337100810" pgbrk="nobreak" rotation="portrait"><file filename="33710128"/><descriptor>
<desc-para>This is an example of two boxes for Command Code SUMRY and TXMOD. Sumry is used to request a summary of accounts available on TIF. If only one tax module is present TXMODA will display for that module. To access, input the following: SUMRY 000-00-1033 R will default to CC REINF if no data is available. The second box shows TXMOD, with YYYYMM for the tax period the definers are A-displays most tax module information present on TIF. C displays control base data, history data, and pending transaction data, L pending transactions with DLNs present, N notice data, P posted and pending transaction data, S SC and MF status history data, X status history data and notice data.</desc-para>
</descriptor></graphic>
<graphic id="id337100811" pgbrk="nobreak" rotation="portrait"><file filename="33710129"/><descriptor>
<desc-para>This is an example of TXMOD screen with for pages 1 &amp; 2 the balance on the account is $1,769.61. The status is M showing TPRQ 54 TAX ADJ, TC150 dated 2008627 11,205.00, TC 806 dated 20080415 9,460.32– TC196 24.93 2008627, TC290 0.00 ADJ RSN CD 06.</desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100479"><exhibitnumber/><date>(01-01-2020)</date>
<title>Suppressing Erroneous Notices</title>
<table frame="all" id="id337101378" summary="FRM 49 Transaction Codes" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">FRM49</emphasis>					<emphasis type="b">Transaction Codes</emphasis></entry>
<entry valign="top"><emphasis type="b">Closing Codes</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>590, 591, 594, 599</entry>
<entry>25, 26, 27, 28, 38, 53, 75, 76, 77, 78 88 97</entry>
</row>
</tbody>
</tgroup>
</table>
<para>Command Code FRM49 is used to input a satisfying transaction on Master File for a Taxpayer Delinquency Investigation (TDI) account when a tax return is not received. TC 59X serves as an indicator that an acceptable reason was given for the non filing of a tax return for a specific tax period. It must be input if the document is being worked six months after program completion. TCs 594 and 599 require a block indicator BB to generate blocking series 74, otherwise this field must be blank. Up to 11 transactions may be input on one screen.</para>
<para>The following is a list of valid Transaction Codes and Closing Code combinations:<br/>TC590 CC 25, 26, 27, 28, 38, 53, 75, 76, 77, 78, 88 and 97 <br/>TC591 CC 25, 38, 75, 88, and 97<br/>TC594 CC 33, 34, 38, 58,59, 63, 83, 84, and 88<br/>TC599 CC 21, 31, 44, 46, 48, 50, 90, 94, 96, 97 and 98</para>
<para><emphasis type="b">FRM49</emphasis> is input as follows:<br/><emphasis type="b"> FRM49 BB</emphasis><br/>000–00–0012 GRAY 30 200612 59434<br/>000–00–4633 GOLD 30 200512 59918<br/>000–00–5678 GREE 30 200412 59944 20080415<br/></para>
<graphic id="id337100908"><file filename="33710131"/><descriptor>
<desc-para>This is an example of STAUP. STAUP is used to update IDRS status using the taxpayers SSN, MFT, TXPD and name control. This example shows STAUP 000–00–0569,30,200612,ROSE,58,05 1520.</desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100480"><exhibitnumber/><date>(01-01-2020)</date>
<title>Master File Transcript Request</title>
<para><emphasis type="b"><emphasis type="u">MFTRA</emphasis></emphasis></para>
<para>Command Code <emphasis type="b">MFTRA</emphasis> is used for hard copy requests. <table frame="all" id="id337100912" summary="IDRS Command code MFTRA is used for hard copy request" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">Example</emphasis></entry>
<entry valign="top"><emphasis type="b">Request Types</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry><br/>000–00–5657,30,20XX12<br/>000–00–3456B,C<br/>000–00–1234,A,123.00–<br/>000–00–2345V,B<br/>000–00–5678,M,30 </entry>
<entry><br/><emphasis type="b">A</emphasis> - Transaction Amount (input a minus sign - after the amount if amount is a credit.)<br/><emphasis type="b"> B</emphasis> - Open Balance<br/><emphasis type="b">C</emphasis> - Complete<br/><emphasis type="b"> D</emphasis> - Transaction Date<br/><emphasis type="b">E</emphasis> - Entity <br/><emphasis type="b">L</emphasis> - All modules for a specific MFT on the lower level<br/><emphasis type="b">M</emphasis> - MFT<br/><emphasis type="b">T</emphasis> - Transaction Code <br/><emphasis type="b">U</emphasis> - NUMIDENT transcripts obtained from SSA<br/><emphasis type="b"> X</emphasis> - Transcript for T/P or Representative (Hard copy only)<br/><emphasis type="b">Z</emphasis> - Specific module from the temporary retention file<br/><emphasis type="b">+</emphasis> - Debit account<br/><emphasis type="b">-</emphasis> - Credit account<br/><emphasis type="b">#</emphasis> - DLN<br/>If none of these request types are input, a specific tax module will automatically generate. </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b"><emphasis type="u">Spouse SSN/Indicator Request Codes</emphasis></emphasis> <br/><emphasis type="b">S</emphasis>-Secondary SSN<br/><emphasis type="b">B</emphasis>-Unable to determine if SSN is Primary or Secondary<br/><emphasis type="b">I</emphasis>-Invalid Secondary SSN</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="u"><emphasis type="b">TIN and File Source Codes</emphasis></emphasis> 								<br/> - blank<br/><emphasis type="b">*</emphasis> - IMF Invalid (SSN)<br/><emphasis type="b">P</emphasis> - IRAF (SSN)<br/><emphasis type="b">X</emphasis> - IRAF Invalid (SSN)<br/><emphasis type="b">V</emphasis> - BMF MFT 51, 52, 77 and 78 (SSN)<br/><emphasis type="b">W</emphasis> - BMF MFT 51, 52, 77 and 78 (Invalid SSN)<br/>An <emphasis type="b">R</emphasis> may be entered instead of the TIN and File Source to repeat the previous entry. </entry>
<entry colsep="1" rowsep="1"/>
</row>
</tbody>
</tgroup>
</table></para>
</exhibit>
<exhibit cols="1" id="id337100481"><exhibitnumber/><date>(01-01-2020)</date>
<title>Document Requests</title>
<graphic id="id337100815" pgbrk="nobreak" rotation="portrait"><file filename="33710133"/><descriptor>
<desc-para>This is an example of an ESTAB screen. ESTAB is used to enter request for original documents to other areas. To access ESTAB input the following ESTABDX000–00–1234. The box below it shows the screen for ESTAB lines for the tax period employee number mft and address line and service center stop. </desc-para>
</descriptor></graphic>
<graphic id="id337100911"><file filename="33710134"/><descriptor>
<desc-para>This is an example of ESTAB (continued). The valid codes are B request and entire block of documents, O request the original document, T recharges the document. The valid file sources are Blank, N, V, W, X, * P. An N cancels a request input the same day. Provide a brief explanation of request.</desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100482"><exhibitnumber/><date>(01-01-2020)</date>
<title>Researching SCCF</title>
<graphic id="id337100817" pgbrk="nobreak" rotation="portrait"><file filename="33710135"/><descriptor><?Pub Dtl?>
<desc-para>This is an example of command SCFTR. SCFTR is used for real time research of the Service Center Control File (SCCF). CC SCFTR is input using a master file ID code and block DLN. The values and meanings for Master File System ID Code are 1 IMF, 2 BMF, 4 IRAF, 5 IRP, 6 ANMF. The bottom of the box displays a print of an screen print for SCFTR. If the response screen indicates the DLN is on the SCCF Historic File, move to the end of the SCFTRH record and transmit for overnight reactivation. </desc-para>
</descriptor></graphic>
<table frame="all" id="id337100913" summary="the from to action codes for SCCF transcript" width="6.625in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="16*"/>
<colspec colname="col2" colwidth="15*"/>
<colspec colname="col3" colwidth="69*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">FROM</emphasis></entry>
<entry valign="top"><emphasis type="b">TO</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">ACTION </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1"><br/>0<br/>0<br/>0<br/>0<br/>0<br/>0</entry>
<entry colsep="1" rowsep="1"><br/>0<br/>5<br/>4<br/>3<br/>2<br/>1</entry>
<entry colsep="1" rowsep="1"><br/>DLN has been set up by Forms 813, 2345, or 4028<br/>From Data Conversion to good tape<br/>From Data Conversion to Rejects Inventory<br/>From Data Conversion to Error Correction<br/>Deleted from raw suspense<br/>Initiates BOB indicator (item in BOB inventory)<br/></entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>1<br/>1<br/>1<br/>1</entry>
<entry colsep="1" rowsep="1"><br/>5<br/>4<br/>3<br/>0</entry>
<entry colsep="1" rowsep="1"><br/>From BOB to good tape<br/>From BOB to Rejects Inventory <br/>From BOB to Error Correction <br/>Deletes BOB indicator </entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>3<br/>3<br/>3<br/>3</entry>
<entry colsep="1" rowsep="1"><br/>5<br/>4<br/>2<br/>0</entry>
<entry colsep="1" rowsep="1"><br/>From Error Correction to good tape<br/>From Error Correction to Rejects Inventory<br/>Deleted from Error Correction inventory<br/>From Error Correction to raw suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>4<br/>4<br/>4</entry>
<entry colsep="1" rowsep="1"><br/>5<br/>2<br/>0</entry>
<entry colsep="1" rowsep="1"><br/>From Rejects inventory to good tape<br/>Deleted from Rejects inventory <br/>From Rejects inventory to raw suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>5</entry>
<entry colsep="1" rowsep="1"><br/>0</entry>
<entry colsep="1" rowsep="1"><br/>From good tape to raw suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>6<br/>6</entry>
<entry colsep="1" rowsep="1"><br/>4<br/>0</entry>
<entry colsep="1" rowsep="1"><br/>From nullified Unpostables to Rejects inventory<br/>From nullified Unpostables to raw suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>7</entry>
<entry colsep="1" rowsep="1"><br/>0</entry>
<entry colsep="1" rowsep="1"><br/>Adds count or money to the SCCF</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><br/>8</entry>
<entry colsep="1" rowsep="1"><br/>0</entry>
<entry colsep="1" rowsep="1"><br/>Subtracts count or money from the SCCF</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100483"><exhibitnumber/><date>(01-01-2020)</date>
<title>IDRS Letter Input</title>
<graphic id="id337100819" pgbrk="nobreak" rotation="portrait"><file filename="33710137"/><descriptor><?Pub Dtl?>
<desc-para>This is an example of command code LETER. Command code LETER generates the LPAGE screen to input an IDRS Letter. To access, input the following LETER 000-00-4455 30 200712. The box in the center of the form displays the format of the LPAGE screen. The NOTE at the bottom states how to perfect the name and address area of the LPAGE screen. Fill in all data on the screen. The narrative fill ins are capitalized just as they will appear on the finished letter. If you use the Expert system to produce the LPAGE screen input, an E will appear on line 1 in column 38 when you toggle back to IDRS mode. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100484"><exhibitnumber/><date>(01-01-2020)</date>
<title>Credit Transfers</title>
<graphic id="id337100820" pgbrk="nobreak" rotation="portrait"><file filename="33710138"/><descriptor>
<desc-para>This is an example of Credit Transfer. Command codes are used to move credits posted to incorrect modules. These may have been posted to the wrong MFT, tax period, or taxpayer. CC TXMODA must precede CC ADD. CC ADD is a prerequisite for the generated credit transfer CC DTR. CCs ADD24 and ADD48 post in 2 cycles. CC ADD48 is used when transferring credit elect transactions. The input format overlay the TXMODA screen of the account to be debited with ADD24, the SSN, MFT, tax period, and name control of the account to be credited. ADD24 000–00–3663 MFT&gt;30 TXPRD&gt;200612 PLN-NUM&gt; NM-CCTRL&gt;PERC. The non IDRS module indicators are A secondary account not on TIF. @ indicates secondary account is on the TIF but the module is not. Blank indicates the secondary account and module are on the TIF. </desc-para>
</descriptor></graphic>
<graphic id="id337100821" pgbrk="nobreak" rotation="portrait"><file filename="33710139"/><descriptor>
<desc-para>This is a continuation of a credit transfer screen print. The example is of CC ADD24. To input a credit transfer, complete the shaded fields. The first block shows a blank DRT24 screen. The second box shows a completed DR24 screen. The trans date, TC, Amount, and remarks field NSD per original return are displayed. </desc-para>
</descriptor></graphic>
<graphic id="id337100822" pgbrk="nobreak" rotation="portrait"><file filename="33710140"/><descriptor><?Pub Dtl?>
<desc-para>This is a credit transfer screen continuation. The input format for TXMODA will be overlayed with ADD43, the SSN, MFT, tax period, and name control of the account to be credited. exhibit gives the instructions on how to transfer credits utilizing Command Codes ADD24 and ADD48. The box at the bottom displays the fields completed on the DRT48 screen</desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100485"><exhibitnumber/><date>(01-01-2020)</date>
<title>IDRS Refunds</title>
<graphic id="id337100823" pgbrk="nobreak" rotation="portrait"><file filename="33710141"/><descriptor>
<desc-para>This is an example of command code COMPA. To access COMPA use definer D to compute both credit and debit interest. The box displays the command code COMPA with the to and from date with the tax calculated. The box displays the Total Interest as $15.89. The second box shows the command code INTST. Input command code to compute the interest and penalties on outstanding balance. The date entered will be the date to which interest is figured The INTST screen displays the MFT, Tax Period, Interest date and name control. The total balance due is $737.05. </desc-para>
</descriptor></graphic>
<graphic id="id337100824" pgbrk="nobreak" rotation="portrait"><file filename="33710142"/><descriptor>
<desc-para>This is an example of command code RFUND. Use definer R to obtain the RFUND format. To access command code RFUND overlay TXMOD and the response will be RFUNDR. The box displays the social security number, MFT, tax period, and name control. The screen displays duplicate indicator and bypass indicator. </desc-para>
</descriptor></graphic>
<graphic id="id337100825" pgbrk="nobreak" rotation="portrait"><file filename="33710143"/><descriptor>
<desc-para>This is a snap shot on how to use IDRS Command Codes COMPA, INTST and RFUND. this is a description of each circled number, 1-Total refund and interest, 2-If no interest -00, if interest due - $$.$$ (dollars &amp; cents), 3-Refund minus interest, 4-Line number 01 - 1040/A/EZ PY, 02- 1040/A/EZ 5- Interest indicator N-normal, R-resticted, 0-none, 6-Universal Location Code (ULC), 7-Case sequence number - numbered sequentially each day per TE. 8-Closure control - A, B, C, M, or S. 9-Block series indicator, 10-Requesters employee number, 11-Remarks from Form 5792. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100486"><exhibitnumber/><date>(01-01-2020)</date>
<title>Case Control and History</title>
<graphic id="id337100826" pgbrk="nobreak" rotation="portrait"><file filename="33710144"/><descriptor>
<desc-para>This is an example of command code ACTON. ACTON is used to establish, update, close control bases, correct name controls on dummy accounts, and enter history items on IDRS modules. A valid input of CC ENMOD, SUMRY, TXMOD, PLAGD, ADJ54, FRM49, FRM77, STAUP, DRT24, DRT48, ACTON, or REINF must precede each ACTON input request. The following exhibits gives the Tax Examiners the Procedures on how to use IDRS Command Code ACTON. The case status codes are A=Assigned, B=Background, C=Closed, M=Monitor/Other, S=Suspense. To record a history item, input the following: ACTON 30 20712 (new line) H, letter12C. When a SUMRY request indicates that a memo account is present on the file indicating that the account has been resequenced to another TIN, use caution when establishing a new control base on any module within the account. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100487"><exhibitnumber/><date>(01-01-2020)</date>
<title>Establishing IDRS Modules</title>
<graphic id="id337100827" pgbrk="nobreak" rotation="portrait"><file filename="33710145"/><descriptor>
<desc-para>The snap shot of command code MFREQ. MFREQ is used to establish an entity or tax module when a control base is not required. MFREQ requires a definer and generates a TC 902. If the name control is not known, substitute AAAA for valid accounts and WXYZ for invalid accounts. Definer D brings a tax module and its related entity data from the Master File to IDRS for approximately two weeks after the request. Definer C brings the account from CFOL to the local IDRS while the user is waiting. If the MFREQ request is accepted, the input screen is redisplayed with the message, REQUEST COMPLETED. To access a valid SSN, input the following: MFREQC000-00-4321 (new line) 30 200612 RUST. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100488"><exhibitnumber/><date>(01-01-2020)</date>
<title>Inputting Tax Adjustments</title>
<graphic id="id337100828" pgbrk="nobreak" rotation="portrait"><file filename="33710146"/><descriptor><?Pub Dtl?>
<desc-para>This is an example of command code REQ54. REQ54 is used to adjust tax, penalty, interest, credit items, and line items. A prerequisite command code (such as ACTON, ADJ54, DRT54, DRT48 and TXMOD) must be requested to verify the tax module and control data. To access, overlay the prerequisite command code with REQ54. The box displays the ADJ54 screen with TC 290 with .00 filled in IRS RCV DT *, CORSP DT 1020200X, NM CTRL BLAC, REMARKS ELFREPLY.</desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100489"><exhibitnumber/><date>(01-01-2020)</date>
<title>Inputting Miscellaneous Transactions</title>
<graphic id="id337100829" pgbrk="nobreak" rotation="portrait"><file filename="33710147"/><descriptor>
<desc-para>This is an example of command code REQ77. REQ77 is used on either an entity module or a specific tax module. ADJ54 or ACTON can also be used as prerequisite command codes. REQ77 will generate CC FRM77. There are two boxes one is for Extension and the other is for DLN Code. Approved = 10 and Disapproved = 17. The example in the bottom of the box shows an example of command code with DLN Cd 10 Extension DT 1015200XX, TRANS DT 041520XX, Move EXT to Correct Module. </desc-para>
</descriptor></graphic>
<graphic id="id337100830" pgbrk="nobreak" rotation="portrait"><file filename="33710148"/><descriptor><?Pub Dtl?>
<desc-para>This is an example of command code REQ77. REQ77A will generate CC FRM7A which is used to input multiple transactions. A maximum of 22 transactions per screen display can be input. The two boxes display the filed and an example of input screens for multiple TCs 460. The box displays the SSN, name control, MFT, Tax Period, MMDDYYYY, XXX, C, P. </desc-para>
</descriptor></graphic>
</exhibit>
<exhibit cols="1" id="id337100490"><exhibitnumber/><date>(01-01-2023)</date>
<title>ERS Status Codes</title>
<table frame="all" id="id337100919" summary="Alisting of ERS Status codes used in ERS and Rejects" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="21*"/>
<colspec colname="col2" colwidth="79*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Number</emphasis></entry>
<entry valign="top"><emphasis type="b">ERS Status Codes</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">1XX</emphasis></entry>
<entry colsep="1" rowsep="1">The record is in the Error Inventory. Access inventory volumes with CC ERVOL</entry>
</row>
<row>
<entry colsep="1" rowsep="1">1QA</entry>
<entry colsep="1" rowsep="1">Worked error record held for review</entry>
</row>
<row>
<entry colsep="1" rowsep="1">100</entry>
<entry colsep="1" rowsep="1">Unworked error record</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">2XX</emphasis></entry>
<entry colsep="1" rowsep="1">Records are waiting for additional information to be received. These records are in the Unworkable Suspense Inventory.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">221</entry>
<entry colsep="1" rowsep="1">Taxpayer Correspondence has been sent</entry>
</row>
<row>
<entry>222</entry>
<entry>Second Correspondence/International Taxpayer Correspondence has been sent</entry>
</row>
<row>
<entry>223</entry>
<entry>Taxpayer Correspondence has been sent</entry>
</row>
<row>
<entry colsep="1" rowsep="1">224</entry>
<entry colsep="1" rowsep="1">ACA Correspondence has been sent</entry>
</row>
<row>
<entry colsep="1" rowsep="1">230</entry>
<entry colsep="1" rowsep="1">The document was referred to Examination </entry>
</row>
<row>
<entry colsep="1" rowsep="1">231</entry>
<entry colsep="1" rowsep="1">The document was referred to Statute Control </entry>
</row>
<row>
<entry colsep="1" rowsep="1">232</entry>
<entry colsep="1" rowsep="1">The document was referred to Entity Control</entry>
</row>
<row>
<entry colsep="1" rowsep="1">233</entry>
<entry colsep="1" rowsep="1">The document was referred to Fraud Detection Center</entry>
</row>
<row>
<entry colsep="1" rowsep="1">234</entry>
<entry colsep="1" rowsep="1">The document was referred to Accounting</entry>
</row>
<row>
<entry colsep="1" rowsep="1">236</entry>
<entry colsep="1" rowsep="1">The document was referred to another area</entry>
</row>
<row>
<entry colsep="1" rowsep="1">237</entry>
<entry colsep="1" rowsep="1">The document was referred to Examination</entry>
</row>
<row>
<entry colsep="1" rowsep="1">242</entry>
<entry colsep="1" rowsep="1">Management Suspense - A</entry>
</row>
<row>
<entry colsep="1" rowsep="1">243</entry>
<entry colsep="1" rowsep="1">Management Suspense - B</entry>
</row>
<row>
<entry colsep="1" rowsep="1">244</entry>
<entry colsep="1" rowsep="1">Management Suspense - C (LB&amp;I Review)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">245</entry>
<entry colsep="1" rowsep="1">Management Suspense - D</entry>
</row>
<row>
<entry colsep="1" rowsep="1">246</entry>
<entry colsep="1" rowsep="1">Management Suspense -E </entry>
</row>
<row>
<entry colsep="1" rowsep="1">247</entry>
<entry colsep="1" rowsep="1">Workable Suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">248</entry>
<entry colsep="1" rowsep="1">Early Filed Suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">249</entry>
<entry colsep="1" rowsep="1">BOE Research and/or System Problem</entry>
</row>
<row>
<entry colsep="1" rowsep="1">251</entry>
<entry colsep="1" rowsep="1">Missing Document</entry>
</row>
<row>
<entry>281</entry>
<entry>ERS Bypass</entry>
</row>
<row>
<entry>284</entry>
<entry>Bypass Reject</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">3XX</emphasis></entry>
<entry colsep="1" rowsep="1">The suspense period has expired with no response for additional information. These records have been automatically transferred from Unworkable to Workable Suspense.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">3QA</entry>
<entry colsep="1" rowsep="1">Worked suspense record held for review</entry>
</row>
<row>
<entry colsep="1" rowsep="1">321</entry>
<entry colsep="1" rowsep="1">Taxpayer Correspondence had been sent and no response received</entry>
</row>
<row>
<entry>322</entry>
<entry>Second Correspondence/International Taxpayer Correspondence has been sent and no response received</entry>
</row>
<row>
<entry>323</entry>
<entry>Taxpayer Correspondence had been sent and no response received</entry>
</row>
<row>
<entry colsep="1" rowsep="1">324</entry>
<entry colsep="1" rowsep="1">ACA Correspondence has been sent and no response received </entry>
</row>
<row>
<entry colsep="1" rowsep="1">330</entry>
<entry colsep="1" rowsep="1">The document had been referred to Examination </entry>
</row>
<row>
<entry colsep="1" rowsep="1">331</entry>
<entry colsep="1" rowsep="1">The document had been referred to Statute Control </entry>
</row>
<row>
<entry colsep="1" rowsep="1">332</entry>
<entry colsep="1" rowsep="1">The document had been referred to Entity Control </entry>
</row>
<row>
<entry colsep="1" rowsep="1">333</entry>
<entry colsep="1" rowsep="1">The document had been referred to Fraud Detection Center</entry>
</row>
<row>
<entry colsep="1" rowsep="1">334</entry>
<entry colsep="1" rowsep="1">The document had been referred to Accounting </entry>
</row>
<row>
<entry colsep="1" rowsep="1">335</entry>
<entry colsep="1" rowsep="1">Additional Research needed</entry>
</row>
<row>
<entry colsep="1" rowsep="1">336</entry>
<entry colsep="1" rowsep="1">FIRPTA Verification (International only)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">337</entry>
<entry colsep="1" rowsep="1">The document had been referred to Examination </entry>
</row>
<row>
<entry colsep="1" rowsep="1">342</entry>
<entry colsep="1" rowsep="1">Management Suspense - A</entry>
</row>
<row>
<entry colsep="1" rowsep="1">343</entry>
<entry colsep="1" rowsep="1">Management Suspense - B</entry>
</row>
<row>
<entry colsep="1" rowsep="1">344</entry>
<entry colsep="1" rowsep="1">Management Suspense - C (LB&amp;I Review)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">345</entry>
<entry colsep="1" rowsep="1">Management Suspense - D</entry>
</row>
<row>
<entry colsep="1" rowsep="1">346</entry>
<entry colsep="1" rowsep="1">Management Suspense - E </entry>
</row>
<row>
<entry colsep="1" rowsep="1">347</entry>
<entry colsep="1" rowsep="1">HQ suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">348</entry>
<entry colsep="1" rowsep="1">Early Filed Suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">349</entry>
<entry colsep="1" rowsep="1">BOE Research and/or System Problem</entry>
</row>
<row>
<entry colsep="1" rowsep="1">351</entry>
<entry colsep="1" rowsep="1">Missing Document</entry>
</row>
<row>
<entry>381</entry>
<entry>ERS Bypass</entry>
</row>
<row>
<entry>384</entry>
<entry>Bypass Reject</entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">4XX</emphasis></entry>
<entry colsep="1" rowsep="1">All information to resolve the record is available or some information has been received and additional action is to be taken. These records either came directly to the workable file or were activated with CC ACTVT.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4QA</entry>
<entry colsep="1" rowsep="1">Worked suspense record held for review</entry>
</row>
<row>
<entry colsep="1" rowsep="1">400</entry>
<entry colsep="1" rowsep="1">Input Document </entry>
</row>
<row>
<entry colsep="1" rowsep="1">421</entry>
<entry colsep="1" rowsep="1">Taxpayer Correspondence was received</entry>
</row>
<row>
<entry>422</entry>
<entry>Second Correspondence/International Taxpayer Correspondence - response was received </entry>
</row>
<row>
<entry>423</entry>
<entry>Taxpayer Correspondence was received</entry>
</row>
<row>
<entry colsep="1" rowsep="1">424</entry>
<entry colsep="1" rowsep="1">ACA Correspondence - response was received </entry>
</row>
<row>
<entry colsep="1" rowsep="1">430</entry>
<entry colsep="1" rowsep="1">The document had been referred to Examination </entry>
</row>
<row>
<entry colsep="1" rowsep="1">431</entry>
<entry colsep="1" rowsep="1">The document had been referred to Statute Control </entry>
</row>
<row>
<entry colsep="1" rowsep="1">432</entry>
<entry colsep="1" rowsep="1">The document had been referred to Entity Control </entry>
</row>
<row>
<entry colsep="1" rowsep="1">433</entry>
<entry colsep="1" rowsep="1">The document had been referred to Fraud Detection Center</entry>
</row>
<row>
<entry colsep="1" rowsep="1">434</entry>
<entry colsep="1" rowsep="1">The document had been referred to Accounting </entry>
</row>
<row>
<entry colsep="1" rowsep="1">435</entry>
<entry colsep="1" rowsep="1">Additional research needed</entry>
</row>
<row>
<entry colsep="1" rowsep="1">436</entry>
<entry colsep="1" rowsep="1">FIRPTA (International only)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">437</entry>
<entry colsep="1" rowsep="1">The document had been referred to Examination </entry>
</row>
<row>
<entry colsep="1" rowsep="1">441</entry>
<entry colsep="1" rowsep="1">Technical Assistance was needed</entry>
</row>
<row>
<entry colsep="1" rowsep="1">442</entry>
<entry colsep="1" rowsep="1">Management Suspense - A</entry>
</row>
<row>
<entry colsep="1" rowsep="1">443</entry>
<entry colsep="1" rowsep="1">Management Suspense - B</entry>
</row>
<row>
<entry colsep="1" rowsep="1">444</entry>
<entry colsep="1" rowsep="1">Management Suspense - C (LB&amp;I Review)</entry>
</row>
<row>
<entry colsep="1" rowsep="1">445</entry>
<entry colsep="1" rowsep="1">Management Suspense - D</entry>
</row>
<row>
<entry colsep="1" rowsep="1">446</entry>
<entry colsep="1" rowsep="1">Management Suspense - E </entry>
</row>
<row>
<entry colsep="1" rowsep="1">447</entry>
<entry colsep="1" rowsep="1">HQ suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">448</entry>
<entry colsep="1" rowsep="1">Early Filed Suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1">449</entry>
<entry colsep="1" rowsep="1">BOE Research and/or System Problem</entry>
</row>
<row>
<entry colsep="1" rowsep="1">451</entry>
<entry colsep="1" rowsep="1">Missing Document was found</entry>
</row>
<row>
<entry colsep="1" rowsep="1">461</entry>
<entry colsep="1" rowsep="1">Record for renumbering rejection and reentry </entry>
</row>
<row>
<entry colsep="1" rowsep="1">462</entry>
<entry colsep="1" rowsep="1">ANMF or Non-ADP Record </entry>
</row>
<row>
<entry colsep="1" rowsep="1">463</entry>
<entry colsep="1" rowsep="1">Record for Re-input</entry>
</row>
<row>
<entry colsep="1" rowsep="1">464</entry>
<entry colsep="1" rowsep="1">Record for Void</entry>
</row>
<row>
<entry colsep="1" rowsep="1">465</entry>
<entry colsep="1" rowsep="1">International Record </entry>
</row>
<row>
<entry colsep="1" rowsep="1">470</entry>
<entry colsep="1" rowsep="1">Record with duplicate Block DLN</entry>
</row>
<row>
<entry colsep="1" rowsep="1">490</entry>
<entry colsep="1" rowsep="1">Unpostable Record </entry>
</row>
<row>
<entry>491</entry>
<entry><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> 				</entry>
</row>
<row>
<entry>492</entry>
<entry><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> 										</entry>
</row>
<row>
<entry>493</entry>
<entry><restrict>≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡</restrict> </entry>
</row>
<row>
<entry align="center" colsep="1" rowsep="1"><emphasis type="b">900</emphasis></entry>
<entry colsep="1" rowsep="1">Unselected inventory waiting to be loaded from the ERS01 File prior to selection for the real time ERS System.</entry>
</row>
<row>
<entry colsep="1" rowsep="1">999</entry>
<entry colsep="1" rowsep="1">Overflow condition occurs when the total workable inventory exceeds capacity. While in this status the record is not accessible, except for research using CC ERINV. </entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100491"><exhibitnumber/><date>(01-01-2025)</date>
<title>Rejecting Records and Researching ERS Inventory</title>
<table frame="all" id="id337100921" summary="Command code REJECTS is used to delete records from ERS" width="6.625in">
<tgroup cols="4" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="25*"/>
<colspec colname="COLSPEC2" colwidth="37*"/>
<colspec colname="COLSPEC1" colwidth="19*"/>
<colspec colname="col2" colwidth="19*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">Action Code</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Definition </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Valid on non-remittance</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">Valid on Remittance</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">620</entry>
<entry colsep="1" rowsep="1">ANMF/Non-ADP</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry colsep="1" rowsep="1">no</entry>
</row>
<row>
<entry colsep="1" rowsep="1">630</entry>
<entry colsep="1" rowsep="1">Re-Entry</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry colsep="1" rowsep="1">yes</entry>
</row>
<row>
<entry colsep="1" rowsep="1">640</entry>
<entry colsep="1" rowsep="1">Void</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry colsep="1" rowsep="1">no</entry>
</row>
<row>
<entry colsep="1" rowsep="1">651</entry>
<entry colsep="1" rowsep="1">International (AUSPC)</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry colsep="1" rowsep="1">no</entry>
</row>
<row>
<entry colsep="1" rowsep="1">660</entry>
<entry colsep="1" rowsep="1">Data Control Delete (TEP Delete)</entry>
<entry colsep="1" rowsep="1">yes</entry>
<entry colsep="1" rowsep="1">yes</entry>
</row>
</tbody>
</tgroup>
</table>
<para>Follow the chart below for IDRS Command Code ERVOL</para>
<table frame="all" id="id337100922" summary="Command code ERVOL listing and descriptions" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="27*"/>
<colspec colname="col2" colwidth="73*"/>
<thead>
<row>
<entry valign="top">ERVOL</entry>
<entry valign="top"><emphasis type="b">ERVOL Descriptions</emphasis><br/>Command Code ERVOL is used to access a document or block that is present in the ERS Control File. </entry>
</row>
</thead>
<tbody>
<row>
<entry><emphasis type="b">ERVOL 421</emphasis></entry>
<entry>To research by a specific status (e.g., activated correspondence)</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">ERVOL 3XX</emphasis></entry>
<entry colsep="1" rowsep="1">To obtain the total number of records in expired suspense</entry>
</row>
<row>
<entry colsep="1" rowsep="1"><emphasis type="b">ERVOL 4XX</emphasis></entry>
<entry colsep="1" rowsep="1">To obtain the total number of records transferred to workable suspense </entry>
</row>
</tbody>
</tgroup>
</table>
<para>Use the following chart for IDRS Command Code ERINV</para>
<table frame="all" id="id337100923" summary="Command code ERINV is used to access a document in ERS" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="47*"/>
<colspec colname="col2" colwidth="53*"/>
<thead>
<row>
<entry valign="top"><emphasis type="b">ERINV</emphasis></entry>
<entry valign="top"><emphasis type="b">Explanation</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>ERINV 00212–115–00645–X </entry>
<entry>To access a specific record in ERS inventory by individual DLN</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERINV 00212–115–006XX-X</entry>
<entry colsep="1" rowsep="1">To access all documents within a block in ERS inventory</entry>
</row>
<row>
<entry colsep="1" rowsep="1">ERINV 000004656</entry>
<entry colsep="1" rowsep="1">To access all documents with a specific TIN in ERS inventory</entry>
</row>
<row>
<entry>ERINVC</entry>
<entry>To access the preparer check box indicator data</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100492"><exhibitnumber/><date>(11-17-2020)</date>
<title>Tax Class—Doc Code—MFT Code—Program Code</title>
<table frame="all" id="id337100924" summary="Listing of tax class, document codes, MFT codes and program codes" width="6.625in">
<tgroup cols="6" colsep="1" rowsep="3">
<colspec colname="COLSPEC0" colwidth="10*"/>
<colspec colname="col1" colwidth="18*"/>
<colspec colname="col2" colwidth="18*"/>
<colspec colname="col3" colwidth="18*"/>
<colspec colname="col4" colwidth="18*"/>
<colspec colname="col5" colwidth="18*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">ITEM#</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">DOCUMENT </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">TAX CLASS</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">DOC. CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">MFT CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">PROGRAM CODE</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry>1.</entry>
<entry colsep="1" rowsep="1">1040 OTFP</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">11,21</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">43110</entry>
</row>
<row>
<entry>2.</entry>
<entry colsep="1" rowsep="1">1040 FP</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">12,22</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">43210</entry>
</row>
<row>
<entry>3.</entry>
<entry colsep="1" rowsep="1">1040 PY &amp; REINPUTS</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">11</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">43113</entry>
</row>
<row>
<entry>4.</entry>
<entry colsep="1" rowsep="1">1040 MeF</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">11, 21</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">43510</entry>
</row>
<row>
<entry>5.</entry>
<entry colsep="1" rowsep="1">1040C</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">61</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">44200</entry>
</row>
<row>
<entry>6.</entry>
<entry colsep="1" rowsep="1">1040ES</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">20</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">44200</entry>
</row>
<row>
<entry>7.</entry>
<entry>1040 MeF</entry>
<entry align="center">2</entry>
<entry>07</entry>
<entry align="center">30</entry>
<entry>43530</entry>
</row>
<row>
<entry>8.</entry>
<entry>1040 -SR MeF</entry>
<entry align="center">2</entry>
<entry>05</entry>
<entry align="center">30</entry>
<entry>43540</entry>
</row>
<row>
<entry>9.</entry>
<entry>1040-SR OTFP</entry>
<entry align="center">2</entry>
<entry>05</entry>
<entry align="center">30</entry>
<entry>43120</entry>
</row>
<row>
<entry>10.</entry>
<entry>1040- SR FP</entry>
<entry align="center">2</entry>
<entry>06</entry>
<entry align="center">30</entry>
<entry>43220</entry>
</row>
<row>
<entry>11.</entry>
<entry colsep="1" rowsep="1">1040X (Amended)</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">11</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">44400</entry>
</row>
<row>
<entry>12.</entry>
<entry colsep="1" rowsep="1">CREDIT TRANS (REV. REC.)</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">24, 87</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">45500</entry>
</row>
<row>
<entry>13.</entry>
<entry colsep="1" rowsep="1">ACCOUNTING (NON-REV. REC)</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">45,48, 51, 58</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">45500</entry>
</row>
<row>
<entry>14.</entry>
<entry colsep="1" rowsep="1">PAYMENT DOCUMENTS</entry>
<entry align="center" colsep="1" rowsep="1">2</entry>
<entry colsep="1" rowsep="1">17, 18, 19, 70</entry>
<entry align="center" colsep="1" rowsep="1">30</entry>
<entry colsep="1" rowsep="1">45500</entry>
</row>
</tbody>
</tgroup>
</table>
<table frame="all" id="id337100925" summary="NMF tax class, document code, MFT code and program code" width="6.625in">
<tgroup cols="5" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="20*"/>
<colspec colname="col2" colwidth="20*"/>
<colspec colname="col3" colwidth="20*"/>
<colspec colname="col4" colwidth="20*"/>
<colspec colname="col5" colwidth="20*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">DOCUMENT </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">TAX CLASS</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">DOC. CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">MFT CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">PROGRAM </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">SUBSEQUENT PAYMENTS</entry>
<entry align="center" colsep="1" rowsep="1">6</entry>
<entry align="center" colsep="1" rowsep="1">27, 28</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">ADVANCED PAYMENTS</entry>
<entry align="center" colsep="1" rowsep="1">6</entry>
<entry align="center" colsep="1" rowsep="1">62</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">1040</entry>
<entry align="center" colsep="1" rowsep="1">6</entry>
<entry align="center" colsep="1" rowsep="1">11,12, 21, 22</entry>
<entry align="center" colsep="1" rowsep="1">20</entry>
<entry colsep="1" rowsep="1"/>
</row>
</tbody>
</tgroup>
</table>
<table frame="all" id="id337100926" summary="IRAF tax class, document code, MFT code andprogram code" width="6.625in">
<tgroup cols="5" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="20*"/>
<colspec colname="col2" colwidth="20*"/>
<colspec colname="col3" colwidth="20*"/>
<colspec colname="col4" colwidth="20*"/>
<colspec colname="col5" colwidth="20*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">DOCUMENT </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">TAX CLASS</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">DOC. CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">MFT CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">PROGRAM </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">PAYMENTS</entry>
<entry align="center" colsep="1" rowsep="1">0.2</entry>
<entry colsep="1" rowsep="1">17, 24, 48, 51, 58</entry>
<entry colsep="1" rowsep="1">29</entry>
<entry colsep="1" rowsep="1">45500</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100493"><exhibitnumber/><date>(01-01-2020)</date>
<title>Action Code/Command Code Chart for Deleting Records</title>
<table frame="all" id="id337100927" summary="Action code/command code chart for deleting records" width="6.625in">
<tgroup cols="6" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="17*"/>
<colspec colname="col2" colwidth="17*"/>
<colspec colname="col3" colwidth="16*"/>
<colspec colname="col4" colwidth="16*"/>
<colspec colname="col5" colwidth="17*"/>
<colspec colname="col6" colwidth="17*"/>
<thead>
<row>
<entry align="center" valign="top"><emphasis type="b">REASON FOR DELETING</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">ACTION CODE</emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">RJECT </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">NWDLN </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">RJECT </emphasis></entry>
<entry align="center" valign="top"><emphasis type="b">NWDLN </emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">Renumber</entry>
<entry align="center" colsep="1" rowsep="1">610</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
<entry align="center" colsep="1" rowsep="1">Valid for new DLN</entry>
</row>
<row>
<entry colsep="1" rowsep="1">Remittance Renumber </entry>
<entry align="center" colsep="1" rowsep="1">611</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Valid for new DLN or Literal*</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">ANMF Non-ADP</entry>
<entry align="center" colsep="1" rowsep="1">620</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Valid for new DLN or Literal*</entry>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">Re-Entry</entry>
<entry align="center" colsep="1" rowsep="1">630</entry>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">Void</entry>
<entry align="center" colsep="1" rowsep="1">640</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Valid for DLN or 3244 or Literal*</entry>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">International (AUSPC)</entry>
<entry align="center" colsep="1" rowsep="1">651</entry>
<entry colsep="1" rowsep="1"/>
<entry colsep="1" rowsep="1">Valid for DLN of 3244 or Literal*</entry>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
</row>
<row>
<entry colsep="1" rowsep="1">Data Control Deletes</entry>
<entry align="center" colsep="1" rowsep="1">660</entry>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
<entry align="center" colsep="1" rowsep="1">Valid</entry>
<entry colsep="1" rowsep="1"/>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100494"><exhibitnumber/><date>(01-01-2025)</date>
<title>Activating Unworkable Suspense</title>
<para>Command Code <emphasis type="b">ACTVT</emphasis> is used for overnight activation of records from unworkable to workable suspense inventory. Up to 22 records may be entered at one time on a screen. The following table shows the input screen and examples of the response screen.</para>
<table frame="all" id="id337100916" summary="ACTVT is used for overnight activation of unworkable suspense inventory" width="6.625in">
<tgroup cols="2" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="50*"/>
<colspec colname="col2" colwidth="50*"/>
<thead>
<row>
<entry valign="top">Command Code <emphasis type="b">ACTVT</emphasis> </entry>
<entry valign="top">Responses to CC <emphasis type="b">ACTVT</emphasis></entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">00222–094–12785–X</entry>
<entry colsep="1" rowsep="1">TRANSFERRED</entry>
</row>
<row>
<entry colsep="1" rowsep="1">00221–114–24312–X</entry>
<entry colsep="1" rowsep="1">IN WORKABLE SUSPENSE</entry>
</row>
<row>
<entry colsep="1" rowsep="1">00221-095-48604-X</entry>
<entry colsep="1" rowsep="1">NOT IN ERS</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
<exhibit cols="1" id="id337100576"><exhibitnumber/><date>(01-01-2020)</date>
<title>General Ledger Account Numbers</title>
<table frame="all" id="id337100918" summary="General ledger account numbers, account titles and normal balance" width="6.625in">
<tgroup cols="3" colsep="1" rowsep="3">
<colspec colname="col1" colwidth="20*"/>
<colspec colname="col2" colwidth="60*"/>
<colspec colname="col3" colwidth="20*"/>
<thead>
<row>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Account Number</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Account Title</emphasis></entry>
<entry align="center" colsep="1" rowsep="1" valign="top"><emphasis type="b">Normal Balance</emphasis> 			</entry>
</row>
</thead>
<tbody>
<row>
<entry colsep="1" rowsep="1">1510</entry>
<entry colsep="1" rowsep="1">Other Receivables, Regular</entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">1550</entry>
<entry colsep="1" rowsep="1">Injured Spouse Claims Allowed - Receivable </entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">1710</entry>
<entry colsep="1" rowsep="1">Dishonored Checks</entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2340</entry>
<entry colsep="1" rowsep="1">Photocopy Fee</entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2350</entry>
<entry colsep="1" rowsep="1">Public Debt</entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2380</entry>
<entry colsep="1" rowsep="1">Installment Agreement, Original</entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">2385</entry>
<entry colsep="1" rowsep="1">Installment Agreement, Reinstated </entry>
<entry colsep="1" rowsep="1">DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4610</entry>
<entry colsep="1" rowsep="1">Unapplied Advance Payments </entry>
<entry colsep="1" rowsep="1">CR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4620</entry>
<entry colsep="1" rowsep="1">Unidentified Remittances </entry>
<entry colsep="1" rowsep="1">CR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4710</entry>
<entry colsep="1" rowsep="1">Offers in Compromise </entry>
<entry colsep="1" rowsep="1">CR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">4720</entry>
<entry colsep="1" rowsep="1">Sales of Seized Property</entry>
<entry colsep="1" rowsep="1">CR</entry>
</row>
<row>
<entry>6400</entry>
<entry>Public Debt</entry>
<entry>DR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">6800</entry>
<entry colsep="1" rowsep="1">Excess Collection </entry>
<entry colsep="1" rowsep="1">CR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">9998</entry>
<entry colsep="1" rowsep="1">Reversal of Revenue Clearance Accountability </entry>
<entry colsep="1" rowsep="1">DR/CR</entry>
</row>
<row>
<entry colsep="1" rowsep="1">9999</entry>
<entry colsep="1" rowsep="1">Revenue Clearance Accountability </entry>
<entry colsep="1" rowsep="1">DR/CR</entry>
</row>
</tbody>
</tgroup>
</table>
</exhibit>
</section></chapter>
</part>
</irm>
</manual><?Pub Caret -2?>