3.12.179  Individual Master File (IMF) Unpostable Resolution

Manual Transmittal

December 27, 2013


(1) This transmits revised IRM 3.12.179, Error Resolution, Individual Master File (IMF) Unpostable Resolution.

Material Changes

(1) - Replaced Accounts Management Taxpayer Assurance Program (AMTAP) with Integrity and Verification Operation (IVO).

(2) - Reword section for better clarification.

(3) - Reword section for better clarification.

(4) (4) - Clarifying general unpostable procedures.

(5) (3) - Moved section to

(6) - (3) (d) (before move): Added ESTABDO.

(7) - Slipped or Mixed Blocks of Payments/Returns - Added Returns.

(8) - Added (3) – Procedure to request block to verify slipped block condition.

(9) - Moved section on CC IRPTR from IRM

(10) (3) (d) - Removed reference to REQ54.

(11) - Added section on CC UPCAS.

(12) (3) - Changed to state that primary request document will be provided.

(13) (3 ) (b) - Removed reference to resolving UP without doc.

(14) (8) (c) - Removed reference to resolving UP without doc.

(15) Emphasize Block Request before 4th Doc Req.

(16) (4) -Received date determination table – added “official postmark of foreign country.”.

(17) (4) -Removed sentence regarding intercepting refund.

(18) - Category Code L-7 - Expanded list of reasons credit transfers may be incorrect.

(19) - Replaced AMTAP with IVO.

(20) - Reworded Category Y-1 criteria.

(21) - Added instruction to cycle for transactions that change account validity.

(22) (3) - Expanded explanation of DM-1 validation processing.

(23) (4) - Expanded explanation of how proximal match is obtained.

(24) (6) - Expanded explanation of invalid posting/unposting.

(25) Deleted instruction to obtain IRSN for spouse.

(26) - Deleted instruction on changing addresses.

(27) (2) - Added note regarding how to enter joint name lines.

(28) (3) - Expanded section on IMF entity resolution procedure.

(29) (4) - Added instruction for transactions intended for BMF trying to post to IMF.

(30) (5) - Added instruction to URC 8 to correct Form 5329.

(31) - Added Form 5329.

(32) (j) - Removed TC 011 and added TC 041.

(33) - Added subsection Establishing an Account (TC 000).

(34) (1) - Note: added instruction to enter spouse for TC 013.

(35) (6) -Removed instruction to enter spouse’s SSN for TC 040/041.

(36) 3.12.179 .18 (2) - Added instruction for 1040 intended as 1041.

(37) (3) - Changed instruction for FSC 5 when spouse’s date of death is within tax period covered by return.

(38) (6) (a) - EFTPS. Added instruction to research MeF.

(39) (6) (b) - Clarified instruction regarding excess prior year credit.

(40) (7) - Changed resolution for credit not belonging to taxpayer.

(41) (2) - Expanded list of research tools, deleted Computer Fast Prints.

(42) (1) - UPC 126. Removed instruction to destroy Form 4251.

(43) (2) - UPC 126. Removed Austin IDRS assignation number for ID Theft.

(44) (2) (a) - UPC 136 RC 0. Added Note explaining second name line.

(45) (3) - UPC 136 RC 0. Added table for UPC 136 Computer Condition Codes.

(46) (1) ( c) - UPC 136 RC 0. Added reason for posting delay code.

(47) . (1) (d) - UPC 136 RC 0. Added that ES payments are computer transferred.

(48) (6) - UPC 137 RC 5. IPU 07-01-2013 added case resolution table.

(49) (3) (b) - UPC 140 RC 0-1. Added instruction to check URF for payments.

(50) (4) (b) - UPC 140 RC 2. Changed instructions for no-reply to 1687C letter.

(51) (2) (d) - UPC 140 RC 3. Clarified instruction for TC 150 tax period in error.

(52) (2) - UPC 140 RC 5. Table: Added “foreign country postmark.”

(53) (2) (b) - UPC 140 RC 5. Added Note regarding “Returned for Signature” stamp.

(54) (2) d) - UPC 140 RC 5. Added instruction to URC 8 to change to earlier date.

(55) (a) - UPC 140 RC 6. Added instructions for amended return payments.

(56) (3) a) - UPC 140 RC 6. Added Computer Condition Code “3.”

(57) (3) (d) - UPC 140 RC 6. Moved from (4).

(58) (4) - UPC 140 RC 6. Added instruction for check cashed in error.

(59) (6) (b) - UPC 140 RC 6. Clarified instructions for no-reply to 1687C letter. Added Form 2424 to transfer payment to Unidentified.

(60) (1) (b) Note-– UPC 147 RC 0. Added UPC 183.

(61) (2) - UPC 147 RC 0. Added resolution procedure.

(62) (2) - UPC 147 RC 0. Added comparison checklist to match criteria.

(63) (2) Note - UPC 147 RC 0. Added instruction if return is not received with 4251.

(64) (1) - UPC 147 RC 1. Deleted instruction not to assign repeats to original examiner.

(65) (4) - UPC 147 RC 1. Replaced “IPSU” with “SPIDT.”

(66) (5) (c) - Added procedures for forwarding cases to the SPIDT unit at each IMF Site.

(67) (7) - UPC 148 RC 0-5. Added URC 8 with remarks “Follow Rejects Instructions.”

(68) (1) - UPC 151. Added technical explanation of how UPC 151 occurs.

(69) (2) (c) - UPC 151 RC 0. Replaced “Adjustment Function” with “Headquarters IMF Unpostable Analyst.”

(70) (1) - UPC 151 RC 0. Added note for TC 000: Spouses SSN should be entered if available.

(71) (2) - UPC 151 RC 0. Added procedure to URC 6 with NC/NL if check digits are present and correct account is on invalid side.

(72) (1) - UPC 151 RC 0. Clarified name change resolution when case addresses invalid side.

(73) - deleted Definer B and added URC 0.

(74) (7) - UPC 151 – INTL. Clarified resolution when a valid SSN cannot be found.

(75) (2) (a) - UPC 151 RC 1. Added instruction to request MFTRA U if needed to establish account.

(76) (1) (a) - Added URC 2 to Originator.

(77) (1) (b) - UPC 152 RC 0. Added URC 2 to originator, or if no originator, URC D.

(78) (2) - UPC 152 RC 0. Added explanation of URC A.

(79) (3) - UPC 152 RC 0. Added instruction to correct both SSNs if reversed.

(80) (3) - UPC 152 RC 0. Replaced TC 000 with TC 013.

(81) (3) (b) - UPC 152 RC 0. Changed post delay code from 1 to 4 and changed release cycle from 4 weeks to 6.

(82) (2) (a) – UPC 152 RC 1. Replaced URC 6 with URC A for prior year payment.

(83) (2) (a) - UPC 153 RC 0. Added “If SSN is incorrect search for correct SSN.”

(84) (2) b) - UPC 153 RC 0. Added instruction to URC 8 to rejects if SE Schedule or Form 5329 is present.

(85) (2) (c) - UPC 153 RC 0. Added note: If TC 041 is input, URC 6 to enter name control and name line, and later cycle.

(86) (2) (d) - UPC 153 RC 0. Clarified procedure when both N/C and TIN are incorrect.

(87) (2) (f) - UPC 153 RC 0. Added explanation of URC 5.

(88) - UPC 153. Subsection rewritten to clarify merging of accounts when the same taxpayer is on both segments of Master File, and to clarify instructions on when and how to obtain an IRSN for the taxpayer on the invalid side.

(89) (2) - UPC 153. Replaced with instruction to input TC 040 for TP on valid w/invalid N/C.

(90) (4) (b) - UPC 153. Clarified when to use cycle delay when inputting TC 013.

(91) - UPC 157 RC 2. Added note to URC 2 for TC 000 on ITIN/IRSN.

(92) (b) - UPC 157 RC 2. Added remarks for URC D.

(93) (b) - UPC 157 RC 2. Clarified procedure when unpostable name line is correct.

(94) (c) - UPC 159 RC 0. Clarified procedure for closing related cases together.

(95) - UPC 159 RC 0. Added (f) – Procedure for Doc Code 77 TC 898/899.

(96) - UPC 164 RC 2. Clarified procedure for cases with KITA indicator.

(97) (1) - Clarified condition for UPC 166 RC 0.

(98) (2) - UPC 166 RC 0. Clarified procedure for determining if FSC is correct.

(99) - UPC 166 RC 0. Renamed section

(100) - UPC 166 RC 0. Moved from (2). Clarified resolution for filing status change. Deleted procedure for preprinted label for joint account.

(101) - UPC 166 RC 0. Moved from (2). Clarified resolution for filing status change. Deleted procedure for preprinted label for joint account.

(102) - UPC 166 RC 0. Moved from Removed instruction to input TC 540.

(103) (2) Note - UPC 166. Deleted “when adding spouse’s SSN and name line.”

(104) (2) Note - UPC 166. Deleted “use TC 014 for address changes.”

(105) (4) - UPC 169 RC 0-3. Added URC 2 if no year on document. Replaced URC 0 with URC 6 to add name control and name line. Added note to URC 0 if repeat due to timing issue.

(106) - UPC 169 RC 9. Removed subsection for resolution for return with zero amount.

(107) (4) d) - UPC 171 RC 2. Added URC D if originator is 0688888884.

(108) (5) - UPC 175. Removed instruction to initiate refund deletion request.

(109) - NOTE: #3 added tolerance of 99 cents

(110) - UPC 176 RC 0. Combined (3) through (7) into (3) and clarified resolution procedures.

(111) (6) - UPC 176 RC 0. Added URC 8.

(112) (7) - UPC 176 RC 0. Clarified procedure for invalid taxpayer claiming EIC or personal exemptions. Added note that TC 000 cannot be input for ITIN or IRSN.

(113) (1) - UPC 176. Clarified explanation of determining first time filer. Added research procedures.

(114) (2) - UPC 176. Added instruction to input TC 000 and URC 8 if EIC or personal exemption is claimed.

(115) (3) b) - UPC 176 INTL. Replaced TC 041 with TC 013.

(116) (4) - UPC 176 INTL. Added URC 8 to remove EIC or personal exemption.

(117) (2) - UPC 188 RC 0. Added procedure for TC 971 AC 134, 617, or 199.

(118) (1) - Note #13 – UPC 189 RC 0. Added TC 290 containing references.

(119) (1) - Note #14 – UPC 189 RC 0. Added reference number 259 with positive sign.

(120) (1) - UPC 189 RC 1. Added “below zero ($10 tolerance).”

(121) (1) - UPC 189 RC 2. Added “to greater than $2,000.00.”

(122) (1) - UPC 189 RC 2. Added “to greater than $2,000.00.”

(123) - UPC 194 RC 0 – TC 971. Added (4) – Procedure for TC 972 AC 506 or 522. Added (5) – If TC 844, correct to date of TC 846.

(124) - UPC 197 RC 0. Added (5) – IMFOLB if check specifies amended return.

(125) (1) - UPC 198 RC 2. Added note to verify information on check with unpostable information.

(126) (4) (b) – UPC 198 RC 2. Added instruction to URC 0 to allow offset to debit balance modules if payment specifies tax period.

(127) (4) (c) - UPC 198 RC 2. Removed URC 0 for preprinted notice. Added instruction to use ADD24 to transfer if payment is for different Master File and URC 0 with 570.

(128) (4) (d) - UPC 198 RC 2. Added TC 670.

(129) (4) (i) - UPC 198 RC 2. Removed paragraph regarding TC 760.

(130) (1) (a) - UPC 198 RC 2 – Resolution for All Other TCs. Added instruction to input TC 570 or NOREFP if payment indicates it is for and amended return.

(131) - UPC 299 RC 5. Added (11) to clarify condition for TC 150 with invalid fields.

Effect on Other Documents

IIRM 3.12.179 dated October 21, 2012 (effective January 1, 2013) is superseded. The following IPUs, issued from November 16, 2012 through August 9, 2013, have been incorporated into this IRM: 13U1205, 13U1172, 13U1152, 13U0645, 13U0623, 13U0438, 13U0454, 13U0356, 13U0211, and 13U0028


IMF Unpostable Units, Wage and Investment, Submission Processing Campuses.

Effective Date


Paul J. Mamo
Director, Submission Processing
Wage and Investment Division  (01-01-2014)
General Information and Introduction

  1. This subsection contains general information for Individual Master File (IMF) and Payer Master File (PMF) Unpostable resolution. Individual Retirement Account File (IRAF) will be processed as an Individual Master File (IMF) document, but will retain Master File Transaction (MFT) 29.  (01-01-2014)
Purpose and Scope

  1. This IRM Section provides "specific" IMF and PMF information, guidelines, and procedures for resolving unpostables using the Generalized Unpostable Framework (GUF).

  2. It also provides directions to all individuals who use the GUF to display, research, suspend, and close INDIVIDUAL or FILES type unpostable cases. See IRM General Unpostables, for a description of INDIVIDUAL and FILES unpostable cases.

  3. The following is a partial list of Internal Revenue Manuals (IRMs) that contain information for correcting Unpostable conditions:

    1. IRM 25.6, Statute of Limitations, provides guidelines for the clearing and processing of Statute imminent cases. Different methods are used to determine the Assessment (ASED), Refund (RSED), or Collection (CSED) Statute expiration dates. The Unpostable functions should familiarize themselves with the information that relates to an Unpostable condition. However, the Unpostables function must "clear" all statute-imminent cases other than Transaction Code (TC) 291/301 decreases through the Statute function. Decreases should be forwarded to the Accounts Management Correspondence section whether the statute is imminent or expired.

    2. IRM 3.12.32, General Unpostables, provides guidelines for the Generalized Unpostable Framework (GUF) for processing unpostable cases.

    3. IRM 3.13.5, Individual Master File (IMF) Account Numbers, provides guidelines for establishing, changing, maintaining, and perfecting individual taxpayer accounts on Individual Master File (IMF).

    4. IRM 3.13.122, IMF Entity Controls Unpostables, provides guidelines for processing IMF Entity Unpostable issues.

    5. IRM 3.17.79, Accounting Refund Transactions, provides guidelines for the issuance of manual refunds.  (01-01-2014)
General Unpostable Framework (GUF)

  1. IRM 3.12.32, General Unpostable Framework (GUF), provides the information on:

    1. How to input the necessary terminal requests to display, suspend, research, and close (resolve) unpostable cases.

    2. General guidelines regarding processing of all Unpostable cases.

    3. Case reassignment guidelines and procedures.

    4. MASS closure (batch and Integrated Submission and Remittance Processing (ISRP)) and certain FILES closure guidelines. However, if a case designated for "MASS" closure is reassigned (from the Campus or "unit" number) to an INDIVIDUAL, the case will be closed per instructions in this manual.

    5. Unpostable Categories, Form 4251 (Return Charge-Outs), Unpostable Listings, Command Codes, Terminal Screen formats, and general Unpostable Resolution Code (URC) corrective action(s).

  2. Tax Examiners should not reassign cases to or from themselves to another employee number or area.  (01-01-2014)
Unpostable Closures

  1. AUTO-VOID/AUTO REJECT—Cases closed automatically by the GUF system are Auto Voided (URC 2 or D) or Auto-Rejected (URC 8) without human intervention. These processes apply to all unpostable areas/functions. However, not all Unpostable Codes/Category Codes can be closed automatically.

  2. MASS—Multiple cases can be closed with one GUF input action using Command Code (CC) UPBAT. This process is called MASS (batch) closures.

  3. FILES— The Unpostable function will request the document from the Files function by sending Form 4251 on all incoming Unpostables except ELF and payment DLNs..

  4. INDIVIDUAL—Single case manual closures are completed in the Unpostable, Examination (Exam), Entity Control (ECU), Criminal Investigation, Statute functions, and Integrity & Verification Operation (IVO).  (01-01-2014)
Guidelines and Objectives of the Unpostable Function

  1. Maintain the integrity of the Master File by identifying transactions that are not compatible with existing Master File data or normal submission processing campus operating procedures.

  2. Review the unpostable records in a manner that will result in expeditious processing, proper posting, and minimize adverse taxpayer contact.

    1. For Accounts in balance due status, where the Unpostable correction involves decreasing or eliminating a balance due, STAUP's must be input. The STAUP will be based on the module status. If the case is being referred to Accounts Management or Collections, input STAUP for 15 weeks. All others input for four weeks.

    2. During conditions of backlogs, high priority should be given to processing unpostables related to refunds and payments on accounts where returns have previously posted and therefore are probably in a balance due condition.

    3. Review all unpostable systemic problems to minimize taxpayer impact, by working ALL RELATED CASES to post the same cycle. Mass receipts of unpostables due to systemic "bugs" that involve accounts in balance due status should result in mass closures to prevent erroneous notices. Mass receipts result in immediate contact by management to Notice Review to ensure erroneous notices are not mailed. Contact your manager immediately upon identifying a possible systemic problem. Keep copies of examples, sanitized if appropriate.

    4. If the issuance of the first delinquency notice is imminent or already has taken place, the unpostable resolution must include the processing of TC 599 cc 017/018 to minimize unnecessary collection activity and adverse taxpayer impact.

  3. Unpostables are loaded by the Operations Branch and divided into the Unpostable, Fraud Detection, Examination, Statute, and Entity inventories within three days after campus receipt from Enterprise Computing Center at Martinsburg (ECC-MTB) / Enterprise Computing Center at Memphis (ECC-MEM).

  4. New Unpostables are loaded Monday night and available for work Tuesday morning. Weekly GUF reports are available Wednesday morning. GUF corrections are run/transmitted on Tuesday night in order to meet the ECC-MTB/ECC-MEM weekly update. Missing this update will cause adverse effects (i.e., incorrect cycling).

  5. Each submission processing campus will run the GUF closures prior to loading the new receipts on Tuesday.

  6. The following submission processing campuses are consolidated at ECC-MTB:

    Processing Center Acronym
    Austin Submission Processing Campus AUSPC
    Ogden Submission Processing Campus OSPC

  7. The following submission processing campuses are consolidated at ECC-MEM:

    Processing Center Acronym
    Kansas City Submission Processing Campus KCSPC
    Cincinnati Submission Processing Campus CSPC
    Fresno Submission Processing Campus FSPC  (01-01-2014)
CADE2 Impact on Unpostables

  1. In January 2012 with CADE 2 implementation, the following cycle changes were made, which impacted Unpostables processing :

    1. Campus Cycle: Thursday - Wednesday

    2. Master File Processing: Friday - Thursday

    3. New unpostables are available to work on Tuesday mornings. The GUF closing runs occur on Tuesday evenings.


      This applies to both Individual Master File (IMF) and Business Master File (BMF) sites.

  2. For example, unpostable conditions identified on transactions input in the campus in any given cycle (with new cycle close of Wednesday), are processed by Master File on Thursday and become available in Unpostables to work as new inventory the immediately following Tuesday.


    This applies to both IMF and BMF sites.

  3. For example – Unpostable conditions identified on transactions input in the campus in any given cycle (with new cycle close of Wednesday), will be processed by Master File on Thursday and will be available in Unpostables to work as new inventory the immediately following Tuesday.  (01-01-2014)
CADE 2 Daily Processing

  1. IMF Master File processes and posts specific transactions daily. IMF also identifies unpostable transactions each day of the cycle. However, GUF continues to run weekly. Unpostables for all 5 days of the IMF cycle are marked for GUF to locate for opening runs to begin on Monday.

  2. IMF does not re-analyze the account at the end of the cycle to determine if the unpostable condition has been resolved. There is a potential that the transaction needed to resolve the unpostable condition may post on a subsequent day in the same cycle. In this situation, the unpostable can be closed with URC 0.

  3. GUF 07 reports should contain multiple IMF data rows for each day of the production cycle (data for Day 1 of the cycle, data for Day 2 of the cycle, etc.)


    BMF continues to process weekly and creates one unpostable file for GUF to locate for the opening run on Monday.

  4. Not all transactions or accounts post in IMF daily. Transactions or accounts marked as weekly resequence until Master File processes the end of the cycle on Thursday.


    BMF continue to process weekly.

  5. Corporate Files On Line (CFOL) and TXMOD Command Codes contain an indicator on the screen to identify whether the IMF account is a Daily account or a Weekly account.


    To prevent an erroneous refund when a credit transfer is being done on a Tuesday, input a cycle delay for 3 cycles on a TC 150.  (01-01-2014)
General Unpostable Concepts

  1. When resolving Unpostable records, follow the intent of the initiator/taxpayer as far as possible within the provisions of the Internal Revenue Code and the appropriate Master File computer program constraints (e.g. Computer Condition Codes, Freeze Codes, etc.). Ensure the correct procedures are followed in the applicable IRM 3.11, IRM 3.12. and IRM 3.24. If there is a conflict between the general and specific instructions, notify Headquarters for determination.

  2. Include priority for processing payment transactions and the use of STAUP. See IRM for Integrated Data Retrieval System (IDRS) STAUP guidelines.

  3. In order to ensure consistency in correspondence, use the guidelines in IRM

  4. Exercise precautions and do thorough research when correcting unpostable records to ensure payments are applied to the correct module. When a payment is identified for a particular tax module and has posted or unposted within another module, correct by closing related unpostables together or inputting a credit transfer. Accurate posting of these transactions should expedite processing and minimize adverse taxpayer contact.


    If an unpostable or misapplied credit/payment appears on the same tax period as a posted extension, the tax examiner should request the extension to verify that it posted correctly. If not posted correctly, the extension should be reprocessed to the correct tax period. This will allow the correct assessment of the penalty/interest when the original return (TC 150) posts.

  5. To minimize delays and costs to other campus functions:

    1. Prior to transferring payments to Unidentified, an attempt to contact taxpayers must be made. The results of the contact, if not conclusive, must be forwarded to Unidentified.

    2. When overpayments of accounts are present, the taxpayer should be contacted to determine if payment was intended for another account.

    3. Transactions that will freeze accounts such as TC 570, and/or TC 640 will not be used unless there is a reason to believe the liability is imminent.

    4. Every attempt should be made to resolve payment cases before requesting the document a second or third time. If document is not available in RTR, request using CC ESTABDO if needed to resolve case.

    5. No-reply actions should be based on a 30 day period beginning with the day the letter is mailed to the taxpayer.


      If the specific procedures are in conflict with the unpostable philosophy in this section, the specific Unpostable Code instructions will take precedence.

    6. No-reply actions should be based on a 30 day period beginning with the day the letter is mailed to the taxpayer.  (01-01-2014)
Weekly Inventory Review

  1. Unpostables should be worked in the following priority.

    1. Repeats, Aged, Potential and History items.

    2. Protection of government interest (Bankruptcy, Intelligence, Statute, Program bugs).

    3. Interest impact (Category C5).

    4. Taxpayer relations (payments, refunds, adjustment transactions).

    5. All other conditions.

  2. Review inventory weekly.

    1. Review assigned cases more than two cycles old to minimize processing delays. Determine if work is being delayed because of training issues, unanswered questions, Files issue, unavailable documents, etc.

    2. Review the Repeat Listing to determine the cause of repeated unpostables. Verify that initial case handling was proper. Close repeats as appropriate.

    3. Review cases in suspense to ensure suspense is timely and appropriate; that replies to correspondence are worked as soon as received, and that no-replies are worked expeditiously.


      See IRM for the guidelines in monitoring Unpostable receipts and inventories.  (01-01-2014)
Discovered Remittances Found While Processing Unpostables

  1. Cash and non-cash remittances found during processing after the mail opening operation are "discovered remittances" .

  2. It is the responsibility of the Unpostable Tax Examiner to review the envelope and return for the possibility of a remittance when working unpostables that involve missing payments.

  3. See IRM, Administrative Reference Guide, for the proper procedures for control of remittances found during processing operations.  (07-09-2013)
Associating Documents to an E-Filed Return

  1. If a document needs to be associated with an e-filed return, a re-file Document Locator Number (DLN) needs to be created so documents can be attached to the electronically filed return's DLN. Attach IDRS document input tag (Form 12772 IMF ADJ54 Adjustment Format) to each E-file/MeF reply and complete with:

    • Employee IDRS number

    • Input Date

    • TC 290

    • Amount ".00"

    • TIN

    • Tax Period

    • Block see (3) below

    • Remarks "Attachment only" and

    • Sequence Number. Sequence numbers for input should begin with "1" through "999" and remain in order

  2. Input TC 290 on IDRS to generate a re-file DLN to the Files area which is used to attach the reply.

    1. Access CC TXMODA, overlay with CC REQ54, Xmit. This will bring up the CC ADJ54 screen

    2. Input the sequence number from the IDRS input tag

    3. BLK>See (3) below

    4. IRS-RCVD-DT> *

    5. TC 290

    6. AMT> .00

    7. Hold-CD> 3


    9. REMARKS> Attachment only

  3. Use the following blocking series:

    If MFT is Then Blocking Series is
    30 05

    Reminder: Form 6502" must" have the IDRS input date and entire employee IDRS number.


    Follow local procedure to determine what area inputs TC 290.  (01-01-2014)
Cases Requiring Special Handling

  1. This subsection contains information on cases requiring special handling.  (01-01-2014)
Offset Bypass Refunds (OBRs)

  1. Under certain limited circumstances where "hardship" exists, the Service may issue a manual refund of excess credits without first satisfying outstanding tax liabilities. These refunds are known as "Offset Bypass Refunds" (OBRs). OBRs may not be issued to bypass a Treasury Offset Program (TOP) obligation. Credits holding on an account are not eligible for refund to the extent that they will satisfy a TOP obligation.

    1. Generally, for original returns, an OBR must be issued before the posting date (23C date) of the original return (TC 150) on which the overpayment was reported.

    2. OBR paper requests are no longer referred to the Taxpayer Advocate Service. A request for an OBR must be worked immediately upon receipt.

    3. When the Unpostable function has problems determining whether "hardship" exists, they should contact their Local Taxpayer Advocate (LTA) for assistance. In instances where it takes time to determine whether a "hardship" exists, or procedures do not result in the posting of the OBR request, actions should be taken to prevent the posting of the assessment until such determination can be made.

  2. OBRs can be requested by any functional office and must be signed by the authorized approving official as determined by your function.

  3. See IRM 21.4.6, Refund Offset, and IRM 3.17.79, Accounting Refund Transactions, for instructions as to what situations qualify for manual refunds, and how to complete the manual refund forms (Form 5792, Request for IDRS Generated Refund, and Form 3753, Manual Refund Posting Voucher).


    See IRM 21.4.6, Refund Offset, for an explanation of how OBRs will be identified for Accounting. See IRM 3.17.79, Refund Transactions, which includes instructions for Accounting to accept these manual refunds for processing, any special instructions for processing, and instructions to maintain a log of all OBRs issued.  (01-01-2014)
Issues and Considerations for OBRs

  1. The following indicators may be present on TXMOD:

    • ATAO

    • TAS

    • ITAR

    • Employee ID Number "63....."

    • PRPS

    • PRPD

    • TAC

  2. OBR requests cannot be honored if the current date is equal to or after the Friday before the Assessment Document date (23C date—always a Monday) of the original return.

  3. Overpayments are excess credits claimed on original returns (TC 150) that have not posted to Master File.

  4. Evidence of the credit condition and documentation must be provided when an OBR manual refund posting voucher is submitted to the Accounts Management Branch. Evidence may be either a copy of the return or an IDRS print showing the amount of the overpayment on the account.

  5. Processing of an OBR requires prompt treatment to avoid the occurrence of an offset during Master File processing, depending upon the way in which the return is filed, i.e., paper or electronic.

  6. A pending offset (TC 896, TC 826, etc.) must be reversed.

  7. If there is a pending refund (PN TC 840, TC 846), and the refund cannot be stopped, issue a manual refund for only the offset amount.

  8. Update IDRS with activity code "TC840OBR"

  9. If an overpayment and/or account are frozen, or if other special conditions are evident, an OBR request may require contact with the affected function. Some examples are:

    1. "-Z" or "Z-" Freeze—contact the Fraud Detection function

    2. "—V" Freeze (bankruptcy)—contact Special Procedures function

    3. The statute for refund has expired—no refund may be issued

    4. Invalid Social Security Number (SSN) conditions

    5. "-U" Freeze (Erroneous Refund—TC 844)

    6. "-Q" Freeze (Unallowable HoId—TC 576)—do not issue the refund for the TC 576 amount

    7. QRDT

    8. CI Control TC 910/912, TC916, TC918

    9. Employee ID number 06850xxxx - 06853xxxxx.

    10. PFRZ

    11. U- Freeze (Installment agreement)

  10. Initiators are responsible for monitoring the account and taking all necessary subsequent actions. Evaluation and monitoring are critical to prevent erroneous refunds.  (01-01-2014)
Slipped or Mixed Blocks of Payments/Returns

  1. Slipped or mixed block conditions originate with the input of payments/returns to the computer system. This issue can occur through the Integrated Submission and Remittance Processing (ISRP), Lockbox, and IDRS.

  2. The following are key elements in identifying a slipped or mixed block condition:

    1. The Entity of the unpostable document does not match the Form 4251.

    2. Missing payment for one taxpayer is posted to the account of an unrelated taxpayer.

    3. A payment posted to the complainant's account with the same transaction date and a sequential DLN which is unclaimed and/or excess. For example: Taxpayer A sends in a photocopy of a canceled check. In researching Taxpayer A's account it is found that there is a payment with the same transaction date but the DLN is different from that on the check, instead of 32270–105–60025–5 it reads 32270–105–60026–5.

  3. Request the block if necessary to verify that a slipped block condition exists.

    1. If the entity portion of a tax return does not match the Form 4251, but the DLN matches, request the block (CC ESTABDB) to verify whether previous and subsequent documents are correctly transcribed.

    2. When a slipped or mixed block is discovered, resolve the unpostable condition and route the block to Rejects (for returns), to verify tax return data.

    3. Route slipped blocks of payments to Accounts Management.  (01-01-2014)
Lien Release Considerations

  1. See IRM 5.12.3, Certificates Relating to Liens and Claims for Damages Under IRC § 7432; within IRM regarding the necessity of a manual lien release. Employees of functions with access to the Automated Lien System (ALS) will input lien release requests in these situations. For those functions that do not have access to ALS, determine the Centralized Lien Unit (CLU) lien release contact on the IRS intranet by going to:

    1. IRWeb Homepage

    2. SERP

    3. Who/Where

    4. Lein Payoff/Release Contact Numbers

  2. An internal use only telephone number is also provided along with the contact information provided on the CLU website. Ensure all e-mail communications regarding liens are via secure E-mail.  (01-01-2014)
Research Information, Methods, and Tools

  1. This subsection contains research information, methods and tools.

  2. General—Research is required unless there is an obvious transcription error or the resolution procedures are specifically noted with the unpostable. Proper research is essential to ensure correct closure of unpostable cases.  (01-01-2014)
IDRS Command Codes

  1. IDRS Command Codes that create a transaction for posting to the Master File will have the TIN and TIN/name control validated using the Taxpayer Index File (TIF) and the National Accounts Profile (NAP).

  2. Command Codes will not return the "Request Completed" response until the TIN and TIN/name control have been validated by the NAP as being on Master File..

  3. IDRS Command Codes affected by On-Line Entity (OLE) validation require the entering of a TIN and Name Control matching an existing Master File. The affected command codes are:

    1. FRM49 (TC 599)—Taxpayer Delinquent Return Notices and Investigations.

    2. REQ77/FRM77/FRM77A—Miscellaneous Transactions Entry.

    3. ENREQ—Entity Changes.

    4. EOREQ—Exempt Organizations Entity Changes.

    5. IMFOL—Provides research of nationwide entity and tax data posted to Individual Master File.

    6. ADD24/ADD48—Credit Transfers

    7. UPRES—Unpostable Correction

    8. IRPTR—Inquiry of the Information Returns File

    9. INOLE– file contains the IRS and Social Security Administration information  (01-01-2014)
System Messages Application to All Command Codes

  1. If the communication lines to the NAP are not available, the message will be "Collection Reports System (CRS)/National Account Profile (NAP) ACCESS NOT AVAILABLE" .

  2. If the NAP is not available, the message will be "NATIONAL ENTITY FILE NOT AVAILABLE" .  (01-01-2014)
Microfilm Replacement System (MRS)

  1. MRS is an automated research system which eliminates most microfilm research done in Campuses and Area Offices.

  2. MRS is accessed through the use of CC MFTRA, via IDRS terminal. The most common requests are:

    1. Entity ("E" )—shows the entity data only

    2. Tax Module—specific requested MFT and/or Tax Period information shown only (e.g., MFT input only)

    3. Complete—("C" )—shows the entire account information.

    4. Money Amount ("A" ) shows all modules with payments for the specific money amount either credit (-) and/or debit (+).

    5. MFTRA with definer "U" —used to request a (NUMIDENT) transcript or display showing specific taxpayer data from Social Security Administration (SSA) records.

  3. You may request a hard copy transcript for your research.  (01-01-2014)
CC IRPTR-Information Returns Master File Transcript Request

  1. IRPTR allows IDRS users to request either on-line or hardcopy Information Returns Processing (IRP) transcripts from the Information Returns Master File (IRMF).

  2. Up to six tax years can be referenced in IRPTR.

  3. IRPTR with Definer L will display a Summary screen with money summaries, date of birth, date of death, and filing status.

  4. See the following table for the IRPTRL input format:

    NNNNNNNNN TIN - Must be 9 numeric characters with or without hyphens
    V TIN Validity
    0 = Valid SSN
    1 = Invalid SSN
    2 = All SSN
    3 = EIN
    YYYY Tax Year
    DD Doc Code (optional)

  5. The amount of withholding is reported on the left hand side of the screen in field TAX Withheld.

  6. See IRM 2.3.35, Command Code IRPTR, for more information on CC IRPTR.  (01-01-2014)
Integrated Data Retrieval System (IDRS)

  1. IDRS is a computer system with the capability to retrieve and update stored information of taxpayer's accounts on Master Files. Research of IDRS is performed through the use of various command codes input via an IDRS terminal.

  2. Some of the most common Command Codes (CCs) used for research are as follows:

    1. DDBKD—displays information from the Dependent Database.

    2. DUPOL (Duplicate TIN on Line)—search for all files for a specific TIN.

    3. ENMOD—displays entity data for a specific TIN.

    4. ERINV—displays ERS inventory.

    5. FIEMP—displays IDRS employee information.

    6. FINDE—researches the national Name Search Facility (NSF) at Enterprise Computing Center at Martinsburg (ECC-MTB) for a business’ name and address information, using the Employer Identification Number (EIN).

    7. FINDS—researches the national Name Search Facility (NSF) at Enterprise Computing Center at Martinsburg (ECC-MTB) for a taxpayers’ name and address information, using the Social Security Number (SSN).

    8. IMFOL— researches the Individual Master File On-Line for entity and tax data information posted to the Master File.

    9. INOLE— researches the National Account Profile (NAP) for verification of TIN/name control and primary name combinations.

    10. IRPTR— to request on-line payee transcripts of income reported on various document types.

    11. MESSG—used to transmit information to all IDRS users. MESSG also contains a listing of the local IDRS numbers that includes the employee number, phone number, and stop number for routing purposes.

    12. NAMEB—search for an EIN

    13. NAMEE—A nationwide search will be performed to match the data entered from the information in the National Accounts Index (NAI), and return the EINs of possible matches.

    14. NAMEI—search for an SSN.

    15. NAMES—A nationwide search will be performed to match the data entered from the information in the National Account Index (NAI), and return the SSNs of possible matches.

    16. RTVUE—access data, transcribed and computer generated, from Form 1040 tax returns and accompanying schedules and forms.

    17. SCFTR—to identify a Return that has not yet been processed.

    18. SUMRY—aIl of the TXMODs for a specific TIN on IDRS.

    19. TMSSN--assigning IRSNs.

    20. TPIIP—to research taxpayer account information using last four digits of the TIN.

    21. TRDBV—provides read only access to electronically filed returns, paper returns as processed through submission pipeline, and paper returns found on the IMF Return Transaction File (RTF)

    22. TXMOD—displays tax module data for a specific TIN.

    23. UPTIN—displays all open and up to three months of closed unpostables for a specific TIN.

    24. URINQ—to identify unidentified Remittances.

    25. XSINQ—used to address the Excess Collection file. It displays one or more records on the (excess collection file) XSF, based on the data elements input. The XSF can be researched in three different ways: By amount of remittance, name control, or DLN.

  3. The following is a partial list of Command Codes used to input an action to the taxpayer's account:

    1. ADC/ADD 34, 24, 48, and 58—credit transfers.

    2. FRM49—used to input 59X transactions.

    3. LETER—used to input information to generate a C-Letter.

    4. REQ77/FRM77—used to input various transaction (i.e. TC 460/470/570).

  4. The following is a partial list of Pending Transaction Identification codes on IDRS:

    1. U (Unpostable)

    2. CU (Corrected Unpostable)

    3. DU (Deleted Unpostable)

    4. DN (IDRS batch processing delete)

    5. DJ (Deleted through normal weekly update)

    6. RJ (Reject Transaction)

    7. RS (Resequence transaction) - see Document 6209 Section 8B for a list of Reqsequence Codes

    8. NU (Nullified Unpostable to be resolved by Rejects or Accounts Management)

    9. DC (Transaction deleted by ERS or Rejects.)

    10. DQ (Transaction deleted by Quality Review)  (01-01-2014)
Remittance Transaction Research (RTR) System

  1. The Remittance Transaction Research (RTR) system is a researchable database that contains remittance processing data and images from ISRP and Lockbox Bank processing sites. RTR can be used to access images of remittances and related documents to conduct on-line research to correct processing errors.

  2. RTR provides 3 years of images online for immediate retrieval. Images more than 3 years old are stored offline. These can be retrieved through an online request, and will be made available by the next business day. Historical data and images in both the old RTR and InfoImage systems will be converted and made available. Historical data and images from the Lockbox Banks will not be made available.  (01-01-2014)
Accessing the GUF

  1. Authorized Access—GUF users are authorized to access only those accounts required to accomplish their official duties. GUF users must not access their own or spouse's account, the account of a friend, relative or coworker, or any account in which they have a personal financial interest.


    Employees engaged in the unauthorized access or browsing of tax accounts are subject to disciplinary actions. Browsing is defined as looking at a tax account to satisfy a personal curiosity or for fraudulent reasons.

  2. Protection of the GUF User Employee—It is essential that only properly authorized employees have access to command codes since the IDRS terminals can be used to change taxpayers' accounts. It is equally important that employees be protected from other personnel using their identification since the only record of the employee making the change will be computer generated from the operator's log-on information.

  3. Proper use of CCs SINON and SINOF will provide protection to the employee. However, employees must properly safeguard their password in order to obtain the benefits of the system. Also the GUF CCs should be authorized only for employees requiring access to unpostable records to assign, close, suspend, display and/or review unpostable cases.

  4. Accessing the GUF via IDRS—The GUF is accessed by the Command Codes UPDIS, UPASG, UPCAS, UPBAT, UPTIN, UPRES, and UPREV. Once signed onto IDRS, an employee may access the command codes that are authorized as determined by the employee's profile.  (01-01-2014)
Case Assignment

  1. All unpostable cases will be assigned on GUF in the following manner:

    1. Campus assigned—XX00000000

    2. Unit assigned—XXXXX00000

    3. Individual employee assigned—XXXXXXXXXX


    X represents a specific number 0 (zero) through 9 (nine).

  2. Campus assigned cases can be closed by any employee having access to the campus through their profile.

  3. Unit assigned cases can be closed by an employee carrying the same digits in the 3rd, 4th, and 5th positions of their employee number, and the 1st and 2nd position digits are within the campus through their profile.

  4. Only the specific employee to whom the case is assigned may close individual assigned cases. MASS (batch) closures are not allowed.

  5. For IDRS purposes the campus sites will have Office Identifiers. These numbers are NOT replacing the two digit File Location Codes in the DLN.

    Campus Office Identifiers File Location Codes (FLCs)
    BSPC 01 19
    CSPC 02 17
    MSPC 03 49
    OSPC 04 29
    PSPC 05 28
    AUSPC 06 18
    ATSPC 07 07
    ANSPC 08 08
    KCSPC 09 09
    FSPC 10 89

  6. The campus has connecting Area Offices (AOs) assigned to each site that represent the former District Offices.  (01-01-2014)
Aged Inventory

  1. The GUF 55–40, UP Employee Assignment/Aged List, and GUF 55-42, UP Employee Assignment/Aged Summary, are inventory lists produced from GUF for all open cases for each employee assignment number (campus, unit, or individual).

  2. The list identifies cases that have exceeded the maximum processing cycle or will become aged in the subsequent week.


    Bankruptcy cases are not reflected on this list.

  3. Management will monitor aged cases and will maintain an overage percentage of less than 10 percent per Master File.

  4. Cases will age as follows:

    B2, D3, G1, R1, V1, V3, V5, Z1 3
    C3, C5, D1, F1, F3, Y1, Y2 5
    B1, I1, I2, L3, L5, L7, P1, V7, W1, W3, W5 10
    L1 (AUSPC Only) 15
    Category Code Y1 TC 150 and Y2 TC 150 cases always age in five cycles.
    Category Code V8 cases are aged when the current cycles minus the cycle the case was added to SCUPMF is greater than 15.

  5. For additional information, see IRM 3.12.32, General Unpostables, within IRM, (GUF 55-40) UP Employee Assignment/Aged Listing and GUF (55-42) Summary  (01-01-2014)
Unpostable Resolution Codes (URCs)

  1. The valid range of Unpostable Resolution Codes is A, D, 0 (zero), 1, 2, 5, 6, and 8. These resolution codes may be used by the Unpostable, Entity Control, Examination, Statute, and Fraud Detection functions when using CC UPRES to work unpostable cases assigned to their area.

  2. Unpostable Resolution Code B is used for special closure of open cases by permission only from the Headquarters GUF Analyst.

  3. Unpostable Resolution Code 3 is used by the GUF system for Auto-Closures of With Remittances (ISRP/Remittance Processing System (RPS)) documents due to a tax period change.

  4. Entering remarks is optional when resolving unpostables conditions with URC A, 0, 5, or 6.

  5. Each GUF closure listed below is considered resolved through the GUF 51. The following table displays the differences:

    URC GUF 51
    0, 5, and 6 Corrected case sent to ECC-MTB/ECC-MEM to attempt to post
    1 Manual Re-input (usually through DIS)
    2 and D Delete (transaction dropped)
    8 Rejected and case sent to GMF (Rejects)
    B. Special Closure

  6. The following table explains the functionality of each URC:

    • Automatically corrects unpostable name control to the Master File name control.

    • Valid on UPC 152 and 156 on TC140, TC150, or TC430 with Entity Code (EC) 2 or 3.

    • Only use when the Master File name control is correct.

    • Special closure (determined by Headquarters) of open assigned cases that allows the records to be treated as original input data.

    • System will automatically generate "Special Closure" in the remarks field.

    • Refer to IRM for End of Year Closure information.

    • Deletes (voids) transaction and removes record from the Service Center Unpostable Master File (SCUPMF).

    • A control base will not be created and no follow up action is necessary.

    • Remarks (line 8 of UPRES) are required stating why the case is being voided. Null Code 01 systemically generates.

    • Documents can be destroyed, as necessary.

    • URC D cannot be used on remittance transactions.

    • Allows unpostable record to attempt to re-post with no change.

    • Use of Definer Modifier B will allow the transaction to bypass the National Account Profile (NAP) validation.

    • Allows transactions to be reinput with the same DLN. Removes the record from SCUPMF. Never reinput a TC 460 or TC 840.

    • Only used on Doc Code 45. Not valid for PMF transactions.

    • Remarks (line 8 of UPRES) are required stating why the case is being closed with URC 1.

    • Refer to IRM for additional information regarding URC 1 and Service Center Control File (SCCF).

    • Deletes (voids) transaction and removes record from the Service Center Unpostable Master File (SCUPMF).

    • A control base is created to the employee who input the original IDRS transaction or the area responsible for the next action.

    • Remarks (line 8 of UPRES) are required stating why the case is being closed with URC 2.

    • A Nullify Area Code is needed. Refer to IRM for the Nullification Table.

    • Route the document to the originator or designated area for appropriate action. Attach Form 8749 with the appropriate fields completed. Refer to IRM (Do not route documents to Data Control.)

    • The originator can be identified by the IDRS EMP field on UPDIS or UPTIN. IDRS CC MESSG, CC FIEMP or the IDRS User & USR Database (IUUD) website (http://iuud.web.irs.gov) can be used to research the employee's location.

    • If URC 2 is invalid, enter URC 1 or 8 as appropriate.

    • Used only by GUF system for certain types of unpostables (auto-closures for ISRP/RPS documents due to a tax period change).

    • Changes the IMF name control and IMF name line on Master File.

    • Changes any combination of name control, name line, TIN, TIN type (PMF), MFT, tax period, Spouse's SSN, transaction code, transaction date, TOP Offset Trace Number(OTN), memo amount, or Computer Condition Code (CCC).

    • Nullifies (removes) the record from the Service Center Unpostable Master File (SCUPMF) and places the transaction in suspense status in Rejects or Error Resolution System (ERS). Automatically updates the Submission Processing Center Control File (SCCF).

    • Used to resolve the unpostable when the record must be renumbered or deleted (incorrect/duplicate), for correcting data for specific fields and/or sections of the record, and for coordinating and/or routing of documents to other functions.

    • Do not use on Doc Code 47 (use URC 2); or Doc Code 45 when TC 720, 740, or 841 (use URC 1).

    • Remarks (line 8 of UPRES) are required and should include what action(s) need to be performed by Rejects.

    • A Nullify Area Code is needed. Null Code 01 should be used unless otherwise directed by an IRM instruction, or the correction instructions include forwarding to another area. Refer to IRM for the Nullification Table.

    • Route the document, including all background and research completed, to Rejects only. Attach Form 8749 with the appropriate fields completed and action(s) to take for correction (including forwarding to another area and originator employee number, if necessary). Do not just indicate the Unpostable Code. Refer to IRM

    • If URC 8 is invalid, URC 1 or 2 as appropriate.

  7. See IRM 3.12.32, General Unpostables for additional information.  (01-01-2014)
End of Year Closures Relating to URC B

  1. END OF YEAR—All assigned IMF unpostables from cycle 48 and prior will be closed and treated as original input data if in "A" (assigned) status. The system will automatically generate "SPECIAL CLOSURE" in the remark field.

  2. The following GUF Categories are excluded from the End-of–Year special closure process:

    A1 E2 C2
    A2 E3 C3
    Ex C1 Z1

  3. If any of these Unpostables repeat, an "S" indicator will be generated highlighting that these cases were from the special closure program. The old sequence number will be retained and assigned to the case.

  4. "CGEN" (Computer Generated) will be displayed in the employee number field on the appropriate listings.  (01-01-2014)

  1. Each unpostable record that is corrected with URC 1 is placed in "manual" status on the Service Center Control Files (SCCF).

    1. If the document is to be reinput, enter Nullify Area Code 01, prepare Form 3893 and route to Batching for input. No further action is needed on the SCCF.

    2. If the document is not to be reinput, enter the appropriate Nullify Area Code and route document and Nullified Distribution List to the function that is responsible for the next action.

  2. The other times URC 1 can be used are when there are program problems or when an IRA TC 150 needs to be input to IMF.

  3. Do not route reinput (URC 1) documents to Data Control, except at the request of that function.

  4. Remarks (Line 8 of UPRES) must always be entered when closing an unpostable with URC 1. If remarks are not entered, the system will not accept the correction and display an error message. Remarks must state why the unpostable is being closed with URC 1.  (01-01-2014)
Form 8749 Unpostable Action and Routing Slip

  1. Form 8749 (or locally developed form) must be used when case is routed to another area.

  2. All appropriate research should be performed and attached before routing the case. Ensure the appropriate boxes are completed. See Figure 3.12.179–1 and following table.

    Figure 3.12.179-1

    This image is too large to be displayed in the current screen. Please click the link to view the image.  (01-01-2014)

  1. The following provides the URC validity checks for CC UPRES, including the valid Master Files:

    A A A
    D D D
    0 0 0
    1 1
    2 2 2
    6 6 6
    8 8 (except TC 150)

    1. These Master File and URC combinations are subject to additional validity checks for each URC depending on the type of IMF or PMF record and the unpostable category criteria.

    2. CC UPRES must meet all the validity checks for input of the URC actions as cc definers and cc definer modifiers.  (01-01-2014)

  1. To use CC UPCAS, input CC UPDIS with an Unpostable cycle sequence, which brings up the UPRES screen. Overlay UPRES with CC UPCAS with the appropriate definer and definer modifier, if applicable.

    1. Use CC UPCASD2 and UPCASD3 to make second and third document requests from Files.

    2. Use CC UPCASSA to suspend a case awaiting further action. Input remarks to indicate why case is being suspended.

    3. Use CC UPCASSC to suspend a case when waiting for a reply to correspondence.

    4. Use CC UPCASZ to input a history item. This can be used to alert the Unpostables TE to whom the case is assigned of information needed to work the case. This is especially useful for related cases in other service centers.  (01-01-2014)

  1. In addition to CC UPRES for individual closings, CC UPBAT is used for multiple cases being resolved with the same URC. However, the CC UPBAT URC actions are not directly updated. They are generated into each resolved record during end-of-day (EOD) processing. Each closed batch record has the generated URC applied to the record via a definer code if all the cc validity checks are met.

    1. URC D, 0, 1, 2, or 8 are valid for CC UPBAT batch closures.

    2. CC UPBAT URC batch resolution actions will only validate cases with a campus or "unit" type employee number during End of Day processing. Cases assigned to an INDIVIDUAL employee number will be rejected and appear on the Rejected Activity Listing.

    3. If URC D, 1, 2, or 8 is used and remarks are not entered, GUF will not accept the correction and will display error messages.

    4. Always enter a Nullify Area Code with URC 1, 2 or 8 to indicate the function that will resolve the case. See IRM 3.12.32, General Unpostables, or IRM for additional information on nullification codes.


      The system will not accept previously input remarks on URC 1, D, or 8 closures. Enter a "/" (slash) at end of remarks field if previous remarks are still valid with unpostable closing. The IDRS employee number is not needed in the remarks section. The employee number will automatically print on the Nullified Listing from the URC D or 2 closure.  (01-01-2014)
Nullification Codes

  1. When closing an unpostable with URC 1, 2, or 8, a nullify area code MUST BE entered to identify the receiving area for the closed unpostables. Nullification listings will be generated for each Nullify Area Code used.

  2. Nullification listings are printed for each of these areas based on the nullification codes listed in the following tables:

    D 01 Void-No Further Action
    1 01 Reinput-No Further Action
    1 23 Dishonored Checks
    1 30 FTD Function-Accounting
    1 31 Data Controls
    1 32 RACS
    1 41 Accounting
    1 50 AM/Customer Service
    1 51 Comp Support/Other S/B

    8 01 Reject Resolution
    8 02 Accounts Management
    8 03 Collection/SCCB
    8 04 Statutes
    8 05 Examination
    8 06 IRP
    8 07 Communication and Liaison
    8 08 Taxpayer Relations
    8 09 Notice/Output Review
    8 12 Refund Inquiry-Taxpayer Advocate Service
    8 14 POA/CAF/RAF
    8 15 CAWR/FUTA
    8 16 AUR
    8 17 Criminal Investigation
    8 19 Collection A.O.
    8 21 Taxpayer Service A.O.
    8 22 SCWR-SC
    8 23 Dishonored Checks
    8 24 Technical
    8 25 Entity
    8 40 Unidentified/Excess Collection
    8 41 Accounting
    8 42 Transshipped to PSC
    8 43 TE/GE
    8 44 TAS/SC
    8 45 Electronic Filing
    8 46 Criminal Investigation
    8 47 TE/GE A.O.
    8 48 TAS/A.O.
    8 49 ERS/Rejects
    8 50 AM/Customer Service

    2   14 POA/CAF/RAF SC 306-324 324
    2   24 Technical SC 350-359 359
    2   12 Refund Inquiry-Taxpayer Advocate Service SC 360-364 364
    2   04 Statutes SC 365-369 369
    2   02 Accounts Management SC 300-499 399
    2   06 IRP SC 350-399 399
    2   03 SCCB/Local ACS SC 650-739 739
    2   33 Remote ACS SC 740-779 779
    2   05 Examination/SC SC 605-649 649
    2 79 07 Communication Liaison AO 100-899 899
    2   09 Notice/Output Review SC 121-129 129
    2   10 Unpostables SC 270-279 279
    2   11 Auto-Void/Contact National Office None None  
    2   13 Manual-Void/EMP # Problem None None  
    2   15 CAWR/FUTA SC 670-679 679
    2   16 AUR SC 830-849 849
    2   17 Criminal Investigation/SC SC 850-859 859
    2 21-36 19 Collection/AO AO 100-299 299
    2 21-36 20 Examination/AO AO 300-549 549
    2 50 20 Examination/AO-L/M AO 100-899 899
    2 66 20 Appeals/AO AO 100-899 899
    2 11-17 21 Taxpayer Service/AO AO 100-899 899
    2   22 SCWR-SC SC None None
    2   23 Dishonored Checks SC 110-119 119
    2   25 Entity SC 220-249 249
    2   40 Unidentified/Excess Collection SC 110-119 119
    2   41 Accounting SC 100-119 119
    2   42 Transship to PSC SC None None
    2 63 44 TAS/SC AC 800-899 899
    2   45 Electronic Filing SC 140-154 154
    2 60 46 Criminal Investigation/AO AO 100-799 799
    2 40 47 TE/GE AO 100-899 899
    2 63 48 TAS AC 100-799 799
    2   49 ERS/Rejects SC 250-269 269
    2   50 AM/Customer Service SC 500-597 597
    2   51 Comp Support/Other Small Business AO 550-899 899

  3. Nullify Area Codes 11 and 13 are computer-generated for the purpose of routing nullified unpostable cases for which a control base cannot be established due to a problem with the Employee Number. These codes are not to be input by an individual tax examiner.

  4. The following table provides distribution information for unpostables that are computer generated by the employee number:

    Automated Underreport(AUR) (0-10) 89000000 16 SCCB 849
    Automated Lien System (ALS) (11-17) 88500000 03 SCCB 739
    ALS (21-36) 88500000 19 SCCB 299
    IDS (1-10) 89209999 03 Collection Area Office 739
    Non-Master File (NMF) (1-10) 88700000 41 Accounting 119
    Standardized IDRS Access (SIA) (01-36) 88888888 03 SCCB 739

  5. All cases input by the Return Analysis/Code and Edit area should be given Nullify Area Code 02 - Accounts Management.

  6. The nullify area codes are entered on Line 2 in positions 6 and 7 on the CC UPRES screen.

  7. If a nullification code is not entered, an error message will be displayed.

  8. URC D does not need a nullification code.

  9. See Nullified Distribution Listing procedures in IRM 3.12.32, General Unpostables, for further information.  (01-01-2014)
Automatic Closures by GUF System

  1. The GUF system automatically closes some Unpostable conditions without any tax examiner involvement. These cases are systemically sent to the initiator. Due to systemic limitations of GUF and Master File, some cases may still need to be corrected manually. For a complete list of automatic closures, see IRM 3.12.32, General Unpostable Framework.

  2. The Unpostable unit must ensure that cases that do not auto-close are not overlooked.  (01-01-2014)
Form 4251, Return Charge-Out


    1. The GUF automatically generates Form 4251 for unpostable cases requiring the return or document (or information from these records) to resolve the unpostable condition.

    2. Form 4251 are also generated for certain auto-closed unpostable records that may require follow-up action by the originator.

    3. Form 4251 generates for the following GUF Categories:

      A1 C1 D3 F1 I2 P1 Y2
      A2 C2 E1 F3 L1 R1 Z1
      B1, B2 C3 E2 G1 L5 V1  
      B3 D1 E3 I1 L7 W3  
      Also certain GUF Category Codes W5 and Y1.

    4. A Form 4251 return charge-out does not generate with the following GUF Category Codes:

      I3 V3 V8 Y1 with TC 610
      I4 V5 W1  
      L3 V7 W5 with matching Y1 cases  

    5. See IRM 3.12.32, General Unpostables, for detailed information on Form 4251 and Files Routing Chart.

  2. See Figure 3.12.179-2 for an example of Form 4251.

    Figure 3.12.179-2

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. Primary Request— The Form 4251 will be given to the tax examiner at the time of the Individual case assignment.

    1. If needed to resolve the unpostable, the return/document will be provided, if available at the time of the original Files request.

    2. If the document has already been retired to the National Archives Records Administration (NARA), the Form 4251 will be routed to the NARA directly from Files.

  4. Statute Period Returns—If Unpostables cannot secure or locate a return or document within 10 workdays of the ASED, the following procedures should be followed:

    1. Return—prepare a "dummy" return and forward to Statutes. Statutes can assist in preparing the "dummy" return.

    2. Document—Forward a copy of TXMOD/TXDLN, UPRES, and Form 4251 to Statutes for a quick/prompt assessment.

  5. Scheme Development case—If the missing document is a Scheme Development case (Category A1/A2), Scheme Development will determine the necessary case resolution after all attempts have failed to locate the unpostable record. Category A1 records may be closed to Rejects if so determined by Scheme Development.

  6. Doc Code 47— If the unpostable record is a Doc Code 47, research IDRS.

    1. If the unpostable case still cannot be closed and document cannot be located, input a second request for the missing document.

    2. If the document (excluding Bankruptcy) is not found after second request and it is required to resolve the case, request the entire block from Files. This will determine whether the record was misfiled.

    3. If the document is still missing, research IDRS again.

  7. If a bankruptcy (GUF category Z1) case and document is unavailable, process the case per the Bankruptcy Listing guidelines as indicated below, and the Category Z1 procedures in IRM

  8. Secondary Request— If the document initially cannot be located in Files or the FRC, a second request will be made by the tax examiner.

    1. The unpostable suspense status (status code and status date) and "remarks" will be updated (CC UPCAS, with definer D and definer-modifier 2) to reflect action taken to obtain the missing document.

    2. This second request should be made after 14 days of the INDIVIDUAL case assignment.

    3. When a second request is made and the unpostable record is a return (TC 150), check for posted refiled DLN (Doc Code 47 or 54). If a refiled DLN is identified, request this DLN using CC ESTAB. The return should be attached.

  9. Input a second request only for original returns (TC 150 or 976), revenue receipts that cannot be viewed in Remittance Transaction Research System (RTR) (Doc Codes 17, 18, 19, 20, 70, or 76), Prompt Assessments (Doc Code 51), or extensions of time to file (TC 460 or 670).

  10. Doc Codes 54, 63, and 77 should be voided to the originator (CC UPRES with URC 2, with appropriate Nullification Code). Indicate in remarks "Doc not available" .  (01-01-2014)
Third Requests

  1. Third Requests—Input a third request after 14 work days from the second request.


    Always research thoroughly before initiating a third request. When a return or document still cannot be located in Files after a second request, or the document is charged-out to another area, initiate a third request.  (01-01-2014)
Block Request Before Requesting a Document for the Fourth (4th) Time

  1. Prior to initiating a fourth request,

    1. Request the block using CC ESTABDB. When received, search for missing document.

    2. If the document is not in the block, determine if the case can be corrected without the document using IDRS research..

    3. If the case cannot be corrected without the document, research for an address and correspond requesting a copy of the return with all attachments, schedules and signature(s). Input UPCAS with definer-modifier SC. This will place the case in correspondence suspense status.

    4. If Unpostables cannot obtain an address, forward case to Work leader to route all available information to Rejects.

    5. Never use a URC 1 or 2.

  2. If other than original return or extension of time to file (TC 460 or TC 620), prepare a dummy document. Input a fourth request using CC UPCAS definer code D and Definer modifier code 4. Route the "dummy" document to Rejects.  (01-01-2014)
Fourth Request

  1. Input a fourth (4th) Form 4251 document request using CC UPCAS definer code D and definer-modifier code 4. The "Remarks" area will indicate "FOURTH REQUEST-SPECIAL SEARCH " and the employee number. Attach a Form 8749, Unpostable Routing Slip or local use form to original Form 4251 (or second or third requests if the first is not available). Notate on the Unpostable Routing Slip that "This document is unlocatable" (or unavailable if potential statute or credit return interest return-expedite case). Also indicate on the Unpostable Routing Slip A fourth-special search document request for Rejects was input on (enter date). Attach all background research information (copy of UPCAS, listing highlighting case or local use research form, old charge-outs) and correction data, if possible, to the Form 4251, and Unpostable Routing Slip.

  2. GUF will automatically close the case to Rejects using URC 8.

  3. Unpostables should indicate to Rejects on the routing slip if the return is not received from the fourth request.

    1. If the return is a non-remittance return, the routing slip should tell Rejects to cancel the DLN and prepare Form 6752.

    2. If the return is a remittance return, Unpostables will instruct Rejects to route the payment to the Unidentified function using Command Code NWDLN, and prepare Form 6752 to route to Files.


    These procedures do not apply to Bankruptcy (Category Z1) returns that cannot be located.

  4. Prepare a "dummy" return or document when routing to Rejects for Doc Codes 17,18 19, 24, 34, 45, 48, 58, 70, or 76 only.  (01-01-2014)
Procedures for Missing Documents

  1. If the Doc Code is: Unpostable Unit will:
    17 (except TC 460 non-remittance), 18, 19, 70 or 76 Research for correct account where payment should be applied. If found, correct to post correctly. If payment must be renumbered, URC 8 and prepare "dummy" 3244. If unable to locate correct module, URC 8 and prepare "dummy" 3244 to be routed to Unidentified Unit.
    17 (TC 460 non-remittance) Research for corrective action. If unpostable cannot be corrected close with URC D, and route to Files.
    24, 48, or 58 Research to determine where debit or credit should post. If corrective action cannot be made, URC 6 or 8 to offset the transaction ("washout " ) prepare "dummy document" (if necessary) with corrections and notate "Process as Corrected" . If unable to determine opposite side of credit transfer and credit side is unpostable, transfer account to Unidentified. If debit side, transfer to 1510 Account.
    34 (Debit side) Research for corrective action. If unpostable cannot be corrected close with URC 2, and route to originator.
    34 (Credit side) Research for corrective action. If credit cannot be resolved, apply to the account where the debit posted and route to originator.
    45 Research to determine where debit or credit should post. If corrective action cannot be made, close with URC 8. Prepare Form 3245 for credit unpostable and transfer to Unidentified Account. Debit should be transferred to the 1510 Account.
    52 Research for corrective action. If unpostable cannot be corrected close with URC 2, and route to originator.
    87 Research to determine where debit should post. If unable to correct, close with URC 8 so Rejects can route case to Accounts Management for reinput or write-off.  (01-01-2014)
Duplicate Documents or Multiple Canceled DLN's

  1. The following procedures may be used only after supervisory approval to do so, if you identify a duplicate document.

  2. If "positive" identification cannot be made as to a "true" duplicate (especially for returns), treat it as an original. Ensure that proper research has been done to avoid erroneous postings, duplicate credits or duplicate payments with return (TC 610).

  3. When it can be determined that the unpostable document is a "true" duplicate and there are not specific instructions for handling duplicate documents, the following action should be taken—

    • If the Julian date is earlier than the posted return Julian date, URC 0 the duplicate return.

    • Otherwise, the duplicate return or extension should be attached to the posted return. Notate "DLN Canceled" with the date on the document. URC 8 to Rejects to cancel the DLN with a note indicating the DLN of the associated return.  (01-01-2014)
Unpostable Document Cancellation Procedures

  1. If the unpostable document is canceled (excluding tax returns, payments, or extensions),

    1. Attach form behind the return.

    2. Notate "Cancel" and the date and staple securely behind the return.

    3. "Remarks" should indicate the reason the action was taken.

  2. If the unpostable document (excluding tax returns, payments, or extensions) is to be canceled and is NOT attached behind the return or routed to the initiator, destroy the document.  (01-01-2014)
Document DLN Matches Unpostable DLN

  1. Before correcting, ensure the DLN on the document matches the DLN of the unpostable. If the document contains two DLN's and both appear to be "live" (not crossed through or canceled), contact your supervisor or lead to research.  (01-01-2014)
Taxpayer Advocate Service (TAS)

  1. This subsection contains information on referring cases to TAS.  (01-01-2014)
TAS background information

  1. The Taxpayer Advocate Service (TAS) is an independent organization within the IRS whose employees assist taxpayers who are experiencing economic harm, who are seeking help in resolving tax problems that have not been resolved through normal channels, or who believe that an IRS system or procedure is not working as it should.

  2. 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 IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, if additional information is required.

  3. While the Internal Revenue Service (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 National Taxpayer Advocate (NTA) 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.

  4. Employees should not view TAS Case Criteria as a means of excluding taxpayers from TAS, but rather, as a guide to TAS case acceptance. The criteria under which TAS accepts a case should not govern whether a taxpayer is entitled to relief.  (01-01-2014)
Referring Cases to TAS

  1. Refer taxpayers to the Taxpayer Advocate Service (TAS) (see IRM Part 13, Taxpayer Advocate Service) when the contact meets TAS criteria (see IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria), and you can’t resolve the taxpayer’s issue the same day. The definition of "same day" is within 24 hours. "Same day" cases include cases you can completely resolve in 24 hours, as well as cases in which you have taken steps within 24 hours to begin resolving the taxpayer's issue. Do not refer these cases to TAS unless they meet TAS criteria and the taxpayer asks to be transferred to TAS. Refer to IRM, Same-Day Resolution by Operations. When referring cases to TAS, use Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order), and forward it to TAS in accordance with your local procedures. Check the TAS box on AMS, if applicable.


    It is important that all IRS employees handle potential TAS cases with the taxpayer's best interest in mind.

    Refer also to, Taxpayer Advocate Service (TAS) Guidelines, for more information. Provide the taxpayer with the number for the NTA toll-free case intake line, 1-877-777-4778 or TTY/TDD 1-800-829-4059. The taxpayer should be advised that TAS is available if the taxpayer is not satisfied with the service he or she received.

  2. An IRS employee should make a referral to a TAS office if the employee receives a taxpayer contact, and cannot initiate action to resolve the inquiry or provide the relief requested. A taxpayer does not have to specifically request TAS assistance to be referred to TAS. IRS employees will advise taxpayers of the option to seek TAS assistance when appropriate. TAS will request documentation from the taxpayer if it is needed to support the requested relief, or required by the IRM.

  3. The following types of cases should NOT be referred to TAS:

    1. Cases where the taxpayer’s complaint or inquiry only questions the constitutionality of the tax system; or

    2. Cases where the focus of the taxpayer's inquiry is solely to employ frivolous tax strategies to avoid or delay filing or paying federal taxes

  4. TAS Case Criteria - Any taxpayer contact that meets any of the criteria listed below should be forwarded to the local Taxpayer Advocate for special handling using a Form 911, Request for Taxpayer Advocate Service Assistance (And Application for Taxpayer Assistance Order). The following is a list of situations to be referred if any of the criteria apply:

    • The taxpayer is experiencing economic harm or is about to suffer economic harm.

    • The taxpayer is facing an immediate threat of adverse action.

    • The taxpayer will incur significant costs if relief is not granted (including fees for professional representation).

    • The taxpayer will suffer irreparable injury or long-term adverse impact if relief is not granted.

    • The taxpayer has experienced a delay of more than 30 days to resolve a tax account problem.

    • The taxpayer has not received a response or resolution to their problem or inquiry by the date promised.

    • A system or procedure has either failed to operate as intended, or failed to resolve the taxpayer’s problem or dispute within the IRS.

    • The manner in which the tax laws are being administered raises considerations of equity, or has impaired or will impair the taxpayer’s rights.

    • The NTA determines compelling public policy warrants assistance to an individual or group of taxpayers. The NTA has the sole authority for determining which issues are included in this criterion and will so designate by memo.


    Case criteria are not meant to be all-inclusive. Evaluate each taxpayer situation based on the unique facts and circumstances of each case.  (01-01-2014)
Correspondence Guidelines and Unprocessable Information and Procedures

  1. This subsection contains information for Taxpayer contact, missing signatures, undeliverable mail, and processable/unprocessable returns.  (01-01-2014)
Section 3705(a), IRS Employee Contacts

  1. This subsection contains information on the Restructuring and Reform Act of 1998, Section 3705, which provides identification requirements for all IRS employees when communicating with taxpayers and/or their representatives on tax-related matters.

    1. IRS employees are required to give their name and unique identification number during taxpayer telephone, face to face, and written contact. In addition, a telephone number is required on all taxpayer correspondence.

    2. This will provide taxpayers with enough information to identify an IRS employee who they may contact regarding their tax-related matters.

  2. All IRS employees, in the field, national, or area office, who communicate by telephone, through correspondence, or face to face with taxpayers or their personal representatives on tax-related matters are required to provide (at a minimum) the following information:

    1. Telephone Contact: Provide your title (e.g., Mr., Mrs., Ms., Miss), last name, and badge identification (ID Card) number.

    2. Face to Face Contact: Provide your title and last name, and ID Card number during the conversation.

    3. Correspondence: All correspondence must contain the telephone number where the taxpayer's question(s) can be answered. In addition, manually-generated and hand written correspondence must include your title, last name, and IDRS, letter system, or ID Card number. This information must be displayed in a prominent manner.

  3. The IDRS numbers and numbers for some other letter systems are automatically generated. If it is not generated, or a handwritten note is prepared, the ID Card (badge) number must be used.

  4. Employees who have toll-free telephone numbers may also provide their location for identification purposes. Faxes to taxpayers on tax-related matters are considered manually-generated correspondence and must include the above required information. All faxes to taxpayers must follow the requirements outlined in IRM 11.3.1, Introduction to Disclosure.

  5. When a taxpayer requests to speak with a specific employee who previously handled the inquiry or request, or complains about the level of service previously provided, every attempt should be made to resolve the taxpayer's inquiry. If the issue cannot be resolved, the employee should refer the issue using established procedures to his or her manager.

  6. Correspondex letters will require a specific employee name and telephone number only if the employee initiating the correspondence is in the best position to respond to any taxpayer questions regarding the correspondence or the employee is asking for additional case-related information.


    If the taxpayer does not need to contact a specific employee, the correspondence needs only an IRS telephone number and standard signature.

  7. It is not necessary to repeat the ID Card (badge) number on a subsequent contact, when the nature of an employee's work involves multiple contacts with the same taxpayer, and the employee has given the taxpayer (either telephone or in-person) their ID Card (badge) number on the first contact.

  8. When contacting taxpayers by telephone, you must be sure you are speaking with the taxpayer or authorized representative before disclosing tax information. See the Taxpayer Authentication guidelines in IRM 21.1.3, Operational Guidelines Overview, within the Required Taxpayer Authentication portion and IRM, Additional Taxpayer Authentication. Also, before leaving a message on a taxpayer’s answering machine, review IRM 11.3.2, Disclosure to Persons with a Material Interest.

  9. When the following apply:

    • It appears that there may be a hardship situation,

    • The taxpayer requests to be referred to the Taxpayer Advocate Service (TAS), or

    • The contact meets TAS criteria,

      and you can't resolve the taxpayer's issue the same day, then prepare and forward Form 911, Request for Taxpayer Advocate Service Assistance, to the Local Taxpayer Advocate (see IRM Part 13, Taxpayer Advocate Service).


      The definition of same day is within 24 hours. There will be times you can completely resolve the issue within 24 hours. There will also be times that although you cannot completely resolve the issue within 24 hours, if you have taken steps within 24 hours to resolve the taxpayer's issue, these cases also meet the definition of same day. Do not refer these cases to TAS unless the taxpayer asks to be transferred to TAS. Refer to IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria; with IRM, Same Day Resolution by Operations.  (01-01-2014)
Taxpayer Contact

  1. Instructions for Taxpayer Contact..  (01-01-2014)
Do Not Correspond in these instances

  1. If there is an indication that previous correspondence was issued for the same item (e.g., missing signature).

  2. When the notation "Substitute for Return Prepared by IRS" appears.

  3. The return is prepared under the authority of Section 6020(b) (Prompt Assessment).

  4. The return is an Examination Adjustment case

    1. Copy secured by Examination is shown on the return

    2. Form 3198 is attached

    3. Examination work papers are attached

    4. Copy of Form 5546 is attached  (01-01-2014)
Contact to Resolve an Unpostable

  1. When contact is necessary to resolve an unpostable condition, use one of the following methods. Do not send an unpostable to the Reject function to initiate correspondence and suspend unless otherwise noted in IRM 3.12.179.  (01-01-2014)
C-Letters and Correspondence

  1. C-Letters (IDRS)—Input CC LETER and LPAGE in accordance with IRM 2.4.6, Command Codes LETER, LPAGE, LPAGD, LETUP, LETED, LLIST, and LREVW, Refer to Document 7130, Chapter 5 for more information. Servicewide Electronic Research Program (SERP) also provides a listing of letters.

    1. Maintain a suspense file in Unpostables to control subsequent responses. (Generally 30 days from the date the letter was input; 70 days for INTL).

    2. If the reply is received after the suspense period but before the case is closed, resolve the unpostable based upon the taxpayer's response.

    3. If the reply is received after the case is closed and contains information which could prevent subsequent unpostables, route replies to Entity Control Unit (ECU), Account Management, Examination, etc. Otherwise, forward for association with unpostable document in Files.  (01-01-2014)
Telephone Contact

  1. The use of the telephone is as follows:

    1. Telephone contact, per management approval, is permitted whenever the taxpayer has provided a telephone number and additional information is needed to resolve a taxpayer’s account.

    2. The need for telephone contact should be determined on a case by case basis not as an absolute rule. For certain types of cases, for example, to confirm a taxpayer's signature, you must follow up with a letter.

    3. When contacting a taxpayer by telephone, you must use authentication disclosure procedures in IRM 11.3.2, Disclosure to Persons with a Material Interest.

    4. Documentation of telephone contact must be attached to the case.


      Do not leave the specific nature or the call or any tax information on answering machines or voice mail, per IRM 11.3.2, Disclosure to Persons with a Material Interest, within, Leaving Information on Answering Machine/Voice Mail.  (01-01-2014)
Resolving Correspondence

  1. On an expedited basis, the Unpostable function should resolve any correspondence received from any other campus or Area Office.

  2. Any local letters should inform the taxpayer to include all necessary signatures, identifying numbers, schedules or attachments.  (01-01-2014)
Missing Signatures on Unpostable Returns

  1. This subsection contains information on missing signatures and W–2's.  (01-01-2014)
IMF Returns—Missing Signatures

  1. An original signature, made by the taxpayer himself or herself, is required below the jurat (perjury statement) in the “Sign Here” area of the return. If the signature is missing, then the return must be returned to the taxpayer unless the return meets one of the exceptions. Continue processing without an original signature if the return meets any of the following conditions:

    1. "Substitute for Return Prepared by IRS" is noted

    2. "1040X signed" is noted

    3. "Dummy return" is noted

    4. Section 6020(b) or prompt assessment is noted or Form 4810 is attached.

    5. Return is "amended", "corrected", "revised", "tentative", or "superseding"

    6. Form 8879 is attached with a valid signature, and there is indication of rejected electronic filing or prior year.

    7. The return can be identified as coming from Exam, Collections or Accounts Management and "Process as Original " is noted on the return.

    8. An employee's IDRS number is present on the signature line.

    9. Taxpayer has signed an attached CP 59 or Letter 143C on the "sign here" line.

    10. CCC "3U" is already present on the return

    11. There is indication of a TRPRT print.

    12. Correspondence Imaging System (CIS) return from Accounts Management

    13. A faxed or scanned signature can be considered a valid and acceptable signature if the return is received from another IRS area (i.e., Substitute for Return (SFR) returns or returns marked "59XXX" (excluding "59918") received from the Collections Branch, or CIS returns from Accounts Management. Faxed or scanned signatures received from TAS are also acceptable. These returns may have "Process as Original", "Process as Original - Faxed Return", or similar statement present at the top of the return and Form 3210 may be present.


    Accept a taxpayer's signature elsewhere on the return if the taxpayer has arrowed their signature to the "sign here" area of the return.

  2. If the return does not meet one of the exceptions, stop processing, Check for evidence that return was previously returned for the missing signature

    • "Returned for Signature" edited in bottom margin or,

    • Form 3531 attached.

  3. If there is evidence of previous correspondence for missing signature, URC 8 to Rejects to cancel the DLN.

  4. If there is no indication of previous correspondence, correspond with the taxpayer. Use Letter 12C and suspend the case 30 days.

  5. If the taxpayer responds with signature,

    • Stamp with Unpostable received date, if not already date stamped.

    • Continue processing to resolve the unpostable condition.

  6. If taxpayer's response directs a change in the Filing Status Code (FSC),

    1. Correct the return's FSC as indicated and attach reply to case document.

    2. Release using URC 8. Route to Rejects annotating "Correct FSC per taxpayer reply" on UPRES and Routing Slip.

    3. Take necessary action to avoid a "repeat" UP.

  7. If the signature is not provided by the taxpayer or response is not received within 30 days,

    1. Annotate "missing taxpayer signature" on return, UPRES and Routing Slip.

    2. Close with URC 8 to Rejects with instructions to cancel DLN .

  8. Faxed signatures are acceptable for IMF returns if you are speaking to the taxpayer or authorized representative and the following steps are taken:

    1. Validate that you are speaking to the taxpayer or authorized representative.

    2. Advise the taxpayer that his/ her faxed signature will become a permanent part of the tax return.

    3. When the taxpayer sends back the faxed signature, send to Files to be attached to the taxpayer's tax return.

  9. For all returns—When correspondence (signature) is received in the unpostable area, ensure action is taken to correct the Return Processable Date (RPD) to prevent interest payment on the refund. This may require releasing the Unpostable to Rejects by URC 8.  (01-01-2014)
Undeliverable Mail

  1. The service should make every effort to locate good addresses for those taxpayers whose Master File addresses are undeliverable.


    Even though a good address may be located, the Master File address should not be changed unless the procedures in IRM 3.13.122, IMF Entity Control Unpostables, for verification of the address are followed. If Form 8822, Change of Address, is received in the Unpostable unit, forward to Entity Control for input.

  2. Research CC ENMOD for a pending or posted address change. If found, correct and re-mail the letter.

  3. Research undeliverable letters for operational errors, incomplete or incorrect name and erroneous or extraneous data. If found, correct and re-mail the letter.

  4. Check other schedules or documents attached to the return to see if there are other addresses at which the taxpayer may be contacted. If there are, reissue correspondence.  (01-01-2014)
Private Mailboxes (PMBs)

  1. Private Mailbox (PMB) companies are being used as substitutes for the U.S. Post Office.

  2. When completing address information for Private Mailboxes, the PMB information must be entered using the correct standard format. Do not include the "#/pound sign" when entering an address or a change of address. An example of a correctly entered address is as follows:

    John Doe Company
    Mailbox Etc.
    1111 Anytown Road PMB 111
    Anytown, US 11111

More Internal Revenue Manual