21.5.5 Unpostables

Manual Transmittal

September 4, 2018

Purpose

(1) This transmits a revised IRM 21.5.5, Account Resolution, Unpostables.

Material Changes

(1) Various editorial changes were made throughout this IRM and cross-references were added, removed or revised as appropriate.

(2) IPU 18U0101 issued 01-11-2018 Links corrected throughout.

(3) IRM 21.5.5.1 updated title to Program Scope and Objectives.

(4) IRM 21.5.5.2 moved research information to research section.

(5) IRM 21.5.5.3 added research information and links.

(6) IRM 21.5.5.3.1.1 clarified pending transaction codes.

(7) IRM 21.5.5.3.1.2 added link to information about GUF 55-47 Report.

(8) IRM 21.5.5.3.2 added link to TOP Offset Conditions.

(9) IRM 21.5.5.3.2 clarified how to use command codes (CC) UPTIN, UPDIS (UPRES), and UPCASZ

(10) IRM 21.5.5.3.4 added link to Centralized Lien Processing.

(11) IRM 21.5.5.4.1 added links to Adjustment Guidelines and Unpostable Resolution Procedures.

(12) IRM 21.5.5.4.1 added adhering to IRM procedures as a way to prevent unpostables.

(13) IPU 18U0101 issued 01-11-2018 IRM 21.5.5.4.2.1 added cycle information.

(14) IRM 21.5.5.4.2.2 added caution; do not reinput the same transaction unless the unpostable condition has been corrected.

(15) IPU 18U0101 issued 01-11-2018 IRM 21.5.5.4.2.2 updated Unpostables Created by Your Own Adjustment.

(16) IPU 18U0718 issued 04-26-2018 IRM 21.5.5.4.2.2 added procedures for UPC 134-3 and Nullify Area Code 41.

Effect on Other Documents

IRM 21.5.5 dated September 6, 2017 (effective October 1, 2017) is superseded. This incudes IPUs 18U0101 issued 1/11/2018 and 18U0718 issued 04-26-2018.

Audience

All employees performing account work

Effective Date

(10-01-2018)


Karen A Michaels
Director, Accounts Management
Wage and Investment Division

Program Scope and Objectives

  1. Purpose: This IRM covers identifying, resolving, and preventing unpostable transactions. This section covers Integrated Data Retrieval System (IDRS) actions not allowed to post or were not accepted by the computer after the IDRS action was systemically reviewed for accuracy.

  2. Audience: The primary users of this IRM are all employees in Business Operating Divisions (BOD) who are in contact with taxpayers by telephone, correspondence or in person.

  3. Policy Owner: The Director of Accounts Management.

  4. Program Owner: Process and Program Management, Accounts Management, Wage and Investment (WI).

  5. Primary Stakeholders: The primary stakeholders are organizations that Accounts Management collaborates with, for example; Return Integrity and Compliance Systems (RICS), Compliance and Submission Processing.

  6. Program Goals: Program goals for this type of work are included in the Accounts Management Program Letter as well as IRM 1.4.16, Accounts Management Guide for Managers.

Background

  1. Employees in the Accounts Management (AM) organization respond to taxpayer inquiries and phone calls as well as process claims and other internal adjustment or transaction requests. Sometimes these adjustments or transactions are unable to post and need to be corrected.

Authority

  1. Refer to IRM 1.2.21, Policy Statements for Customer Account Services Activities, for information. See also IRC Section 7805 and IRC Section 7801.

Responsibilities

  1. The Wage and Investment Commissioner has overall responsibility for policy related to this IRM. Information is published in this IRM on a yearly basis.

  2. Additional information is found in IRM 1.1.13.9.4, Accounts Management, and IRM 21.1.1, Accounts Management and Compliance Services Overview.

Program Controls

  1. Program Reports: The program reports provided in this IRM are for identification purposes for the Accounts Management Customer Service Representatives (CSRs) and Tax Examiners (TEs). For reports concerning quality, inventory and aged listings, please refer to IRM 1.4.16, Accounts Management Guide for Managers. Aged listings can also be viewed by accessing Control Data Analysis, Project PCD, on the Control-D/Web Access server, which has a login program control.

  2. Program Effectiveness: Program Effectiveness is determined by Accounts Management’s employees successfully using IRM guidance to perform necessary account actions and duties.

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

Acronyms

  1. For a comprehensive listing of any IRS acronyms, please refer to the Acronym Database.

  2. Some of the acronyms used in this IRM are:

    Acronym Definition
    AGI Adjusted Gross Income
    ASED Assessment Statute Expiration Date
    BMF Business Master File
    CSI Code Search Index
    CYC Cycle
    DLN Document Locator Number
    ECC-MTB Enterprise Computing Center, Martinsburg
    FTD Federal Tax Deposit
    GUF Generalized Unpostable Framework
    IAT Integrated Automation Technologies
    IDRS Integrated Data Retrieval System
    IMF Individual Master File
    MF Master File
    MFT Master File Tax
    PC Priority Code
    RC Reason Code
    REL CYC Release Cycle
    SERP Servicewide Electronic Research Program
    TC Transaction Code
    TIN Taxpayer Identification Number
    UP Unpostable
    UPC Unpostable Code
    URC Unpostable Resolution Code

Related Resources

  1. Refer to IRM 1.4.2.1.8, Related Resources, for information on related resources that impact internal controls.

  2. The IRS adopted the Taxpayer Bill of Rights in June 2014. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC Section 7803(a)(3) or Taxpayer Bill of Rights, on www.IRS.gov for additional information.

What Is An Unpostable?

  1. Unpostables are transactions that cannot post to the IDRS Master File. While we should be taking every action to prevent unpostables from occurring, it is critical that all unpostable cases are worked within seven business days of receipt.

  2. Each IDRS transaction is subjected to a series of validity checks prior to posting to the Master File. A transaction is termed unpostable when it fails to pass any of the validity checks and is then returned to the campus for follow up action(s).

  3. An IRS employee may encounter unpostables when working the weekly list from the Enterprise Computing Center, Martinsburg (ECC-MTB) returned to the campus Unpostable Unit, when answering a taxpayer inquiry, or when his/her own adjustment case is returned for resolution.

Unpostables Research

  1. Unpostables are handled through identification, research, resolution, and response.

  2. Causes of unpostable transactions include the following:

    • Dates or money amounts do not match on credit transfers

    • Adjustments are input to an account with no transaction code (TC) 150 posted

    • Priority codes (PCs) are omitted

    • Amounts are reduced below zero, except adjusted gross income (AGI)

    • Errors are made in data entry

    • Payments are input on settled accounts

    • Freeze codes are not considered

    • Pending transactions are not considered

    • Presence of certain identity theft indicators

  3. To research the Unpostable Code (UPC), use, Document 6209, Section 8B Master File Codes, and the IAT Code Search Index (CSI) Tool, for reference.

Identifying Unpostables

  1. Identify unpostables on IDRS by the pending transaction identification codes, by the Nullified Distribution Listing (GUF 55-47), or by Form 8749, Unpostable Action and Routing Slip, Form 3465, Adjustment Request, or Form 4251, Return Charge-Out, routed from the Unpostables Function.

    Note:

    Refer to Unpostable Codes/GUF, for additional unpostable information.

  2. When an unpostable condition appears on an account on IDRS, the format includes the letter U followed by a three-digit numeric code (Uxxx) called an unpostable code (UPC). The three digits indicate the cause of the unpostable. A UPC may also include a reason code (RC). The RC is a one-digit number between 0 and 9 which follows the UPC. Reason codes provide a reason why the account transaction was unable to post. Refer to the Command Code Job Aid on Servicewide Electronic Research Program (SERP) under the IRM Supplements page for examples of input and response screens.

  3. UPCs and their definitions are listed in Document 6209, Section 8b 3, IMF, Unpostable Codes - Individual Master File (IMF), Document 6209, Section 8B.4, BMF, Unpostable Codes - Business Master File (BMF) and the IAT Code Search Index (CSI) Tool.

IDRS Pending Transaction Identification Codes
  1. Unpostables are identified on IDRS by pending transaction identification codes, including:

    • UNNN (U = unpostable, NNN = the numeric unpostable code.) This is an open unpostable case.

    • CU - Corrected Unpostable - the transaction should post to the module in the cycle appearing to the right of the transaction.

    • NU - Nullified Unpostable - the transaction unposted and was nullified; sent to the Reject Function for resolution.

    • DU - Deleted Unpostable - the transaction unposted and was deleted; will not post to Master File.

    • DN - Transaction deleted by IDRS daily Taxpayer Information File (TIF) batch processing.

    • DJ - Transaction deleted through normal weekly updates.

    • RJ - Reject transaction - case referred to the Rejects Function.

    • DC - Transaction deleted by Error Resolution System (ERS) or Campus Reject Processing.

    Note:

    These codes are displayed in front of the unpostable transaction.

  2. For additional information see Document 6209, Section 14.7A, Pending Transaction Identification Codes/IDRS Merge Related Transaction Codes.

Unpostables Nullified Distribution Listing (GUF 55-47)
  1. Items nullified by the Unpostables Function with unpostable resolution code (URC) 2 or 8 will appear on the Nullified Distribution Listing (GUF 55-47).

  2. Each Nullified Distribution Listing (GUF 55-47) contains the following identifying information:

    • Unpostable Resolution Code (URC)

    • Master File (MF)

    • Document Locator Number (DLN)

    • Taxpayer Identification Number (TIN)

    • Name Control

    • Master File Tax (MFT) Code

    • Tax Period

    • Unpostable Code

    • Pre-Journalized or Refund Amount

    • Assessment Statute Expiration Date

    • Federal Tax Deposit (FTD) Microfilm Number

    • Unpostable Category Code

    • Resolution Employee Number

    • Functional Area of Resolution

    • Remarks entered by Resolution Function

    • Identity Theft indicator present

  3. When the Unpostables Function closes a case with URC 2, a control is opened on IDRS to the responsible employee or appropriate function. The attempted transaction was deleted and must be reinput correctly after determining the reason for the unpostable.

    • The case control category is NLUN. For additional information see IRM 3.12.32.20, IDRS Case Control "NLUN" .

    • The IDRS employee number is shown on the Nullified Distribution Listing (GUF 55-47). If you do not have access to the Nullified Distribution Listing, do complete research to determine if the transaction needs to be reinput and, if it does, which area should take this action.

    Note:

    If the case is routed to the incorrect function, return the case to the employee shown on the listing.

  4. Form 4251, generated on unpostable cases, shows the assessment statute expiration date (ASED). Ensure unpostable cases showing imminent statute dates (within 90 days) are sent to the Statute unit for quick assessment.

  5. For additional information see IRM 3.12.32.53, (GUF 55-47) Nullified Distribution Listing and (GUF 55-46) Nullified Distribution Summary.

Researching Unpostables on IDRS

  1. Use command codes (CC) UPTIN, UPDIS (UPRES), and UPCASZ to research/resolve unpostables. If the account is not on your local database or at your local campus, you must access these command codes at the campus the unpostable is located.

    Example:

    If the unpostable is located at Philadelphia and you are not, input CC UPTIN SSN-SS-NSSN@05.

  2. Refer to the following IRMs for complete procedures for resolving unpostables:

    • IRM 3.12.179, Individual Master File (IMF) Unpostable Resolution

    • IRM 3.12.279, BMF/CAWR/PMF Unpostable Resolution

    • IRM 3.13.122, Individual Master File (IMF) Entity Control Unpostables

    • IRM 3.13.222, BMF Entity Unpostable Correction Procedures

  3. Refer to IRM 21.4.6.5.23, TOP Unpostable Conditions, for information on unpostables related to tax offset going to Bureau of the Fiscal Service (BFS).

Unpostable IDRS Command Codes
  1. UPTIN: This CC displays all open unpostable cases for the input TIN. Refer to IRM 2.3.37, Command Code UPTIN for the GUF System, for additional information about CC UPTIN. Also refer to the Command Code Job Aid on SERP under the IRM Supplements page for examples of input and response screens. Research CC UPTIN for the following information:

    • The unpostable sequence number of an open case (identifies the assigned number used to control the UP case - 12 characters)

    • Category code (Identifies the type of UP case - 2 characters)

    • Functional area code (Identifies the functional area assigned to the UP case - 2 characters)

    • Unpostable code (UPC) (Identifies the condition which caused the transaction to go unpostable - 3 characters)

    • UP reason code (Identifies the reason a transaction went unpostable - 1 character)

    • Original UP cycle (Identifies the cycle the transaction originally unposted - 6 characters)

    • Unpostable resolution code (Identifies how the unpostable was corrected - 1 character)

    • Nullify area code (Identifies the area nullified UP cases should be routed to - 2 characters)

    • Status code identifies what action has been taken on the case (open, suspended, or closed) - 1 character

    • Status date (Identifies the date the status was last updated - 8 characters)

    • Assigned Employee number - 10 characters

    • The corrective action taken to resolve a previously closed case

    • The response time given the taxpayer on a closed case

      Note:

      Closed unpostables for the input TIN are displayed for up to three months before dropping off the GUF. For closed cases, research the UPC on CC UPTIN to determine why the account transaction was unable to post. Refer to Document 6209, Section 8B.3, IMF, Unpostable Codes - IMF, and Document 6209, Section 8B.4, BMF, Unpostable Codes - BMF, for unpostable reason code (RC) descriptions.

  2. UPDIS: This CC displays unpostable records on the UPRES screen. When CC UPDIS is input, the automatic screen display CC UPRES appears. The information displayed on CC UPDIS varies depending on the type of unpostable. CC UPDIS must be used as a prerequisite for CC UPRES and CC UPCASZ. Research CC UPDIS to display a specific closed unpostable for the input sequence number. The closed unpostable will only appear on CC UPDIS until the correcting action is posted in the Thursday night correction tape run. Refer to IRM 2.3.48, Command Code UPDIS for the GUF System, for information about CC UPDIS. Also refer to the Command Code Job Aid on SERP for examples of input and response screens.

  3. UPCAS: Use CC UPCAS with Definer "Z" to input message/history information to aid in the resolution of the unpostable condition. Briefly explain how the unpostable can be corrected. There are 80 characters available. Refer to the Command Code Job Aid on SERP under the IRM Supplements page for examples of input and response screens.

    Note:

    The IAT UP Histories Tool is designed to assist users with input of histories on command code UPTIN. See UPTIN Histories Tool.

Probing for Information From the Taxpayer
  1. To help resolve open unpostable cases, obtain information from the taxpayer. Questions depend on the nature of the unpostable.

  2. Unpostable return conditions most commonly involve validity processing and entity mismatches.

Responding to Taxpayer Inquiries on an Open Unpostable

  1. Open unpostables are usually resolved within eight cycles, however the time frame for resolution can be extended depending on the required research or complexity of resolving the unpostable.

    Note:

    Refer to IRM 21.4.1.4.1.2, Return Found/Not Processed, for information on UPC 147 and UPC 126.

  2. Research is required to determine the status of the open unpostable. CC UPTIN should be used to identify the unpostable cycle date of the open unpostable. The unpostable cycle identifies the original unposting of the transaction and does not change as the unpostable is reassigned to another area for resolution (the cycle information of the unpostable is shown next to the literal CYC on line 1 of UPTIN). The status date of an open unpostable should not be used to determine the appropriate time frame to respond to the taxpayer. The status date reflects the date the status was last updated and can change as the case is reassigned to another area.

  3. Use the following chart when advising the taxpayer of the appropriate time frame for a response on an open unpostable:

    If And Then
    Unpostable is open and it has been less than 8 cycles since the transaction went unpostable (the cycle information of the unpostable is shown next to the literal CYC on line 1 of UPTIN) Taxpayer has received and responded to correspondence
    1. Probe for information that may assist in resolving the case and update history with UPCASZ. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes.

    2. Advise the taxpayer of the impact on the account once the transaction posts.

    3. Advise the taxpayer to allow the appropriate number of weeks for processing of the unpostable, normally 6-8 weeks.

    Note:

    If the TC 150 is unpostable, explain that once the unpostable is corrected it could take another 6-8 weeks for the return to be processed. This process could take up to 16 weeks.

    Unpostable is open and it has been less than 8 cycles since the transaction went unpostable (The cycle information of the unpostable is shown next to the literal CYC on line 1 of UPTIN) Taxpayer has NOT received any correspondence
    1. Advise the taxpayer some problems have been encountered.

    2. Probe for information that may assist in resolving the case and update history using UPCASZ. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes.

    3. Advise the taxpayer of the impact on the account once the transaction posts.

    4. Advise taxpayer to allow the appropriate number of weeks for processing, normally 6-8 weeks.

    Note:

    The 6-8 week time frame starts from the unpostable cycle (original unposting of the transaction) of the active unpostable.

    Note:

    If the TC 150 is unpostable, explain that once the unpostable is corrected it could take an additional 6-8 weeks for the return to be processed. This process could take up to 16 weeks.

    Unpostable is open and it has been more than 8 cycles since the transaction went unpostable (The cycle information of the unpostable is shown next to the literal CYC on line 1 of UPTIN) You are unable to resolve
    1. Advise taxpayer you are notifying the appropriate function.

    2. Prepare Form 4442/e-4442,Inquiry Referral, and refer case to the appropriate function.

    3. Probe for information that may assist in resolving the case and include it on the Form 4442/e-4442. Refer to the SERP Who/Where Form 4442 Submission Processing Unpostable Referral Listing.

    4. Advise the taxpayer of the impact on the account once the transaction posts.

    5. Advise the taxpayer to allow 8 weeks for processing.

    Note:

    If the TC 150 is unpostable, explain that once the unpostable is corrected, it could take an additional 6-8 weeks for the return to be processed. This process could take up to 16 weeks.

  4. See IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, to determine if the case should be referred to TAS. See IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines, for additional information.

  5. See IRM 21.5.2.4.8.2, Suppressing Balance Due Notices, if there is a balance due on the account.

Responding to Taxpayer Inquiries on a Closed Unpostable

  1. Research is required to determine how the unpostable was closed using CC UPTIN. The status date identifies the date the status was closed and should be used to determine the appropriate time frame to respond to taxpayer inquiries. (The status date is shown next to the status code of the unpostable on line 2 of UPTIN.)

    Note:

    Refer to IRM 21.4.1.4.1.2, Return Found/Not Processed, for information on UPC 147 and UPC 126.

  2. If the unpostable is closed, advise the taxpayer to allow 6 weeks from the closing date of the unpostable for processing. If the unpostable is due to TC 150, advise the taxpayer to allow 9 weeks from the closing date for processing.

    Note:

    Check CC UPDIS for possible cycle delays. The cycle the transaction should post is shown next to the Literal: REL CYC on Line 9 of CC UPRES.

  3. If the account has a lien against it and correction of the unpostable will full pay the account, a manual lien release will be needed. Follow procedures in IRM 5.12.3.3, Lien Release Conditions, regarding manual lien releases. Submit a completed Form 13794, Request for Release or Partial Release of Notice of Federal Tax Lien, to the Centralized Lien Unit, lien release contact. For additional information see, Centralized Lien Processing, on SERP Who/Where.

  4. See IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, to determine if the case should be referred to TAS. See IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines, for additional information.

  5. See IRM 21.5.2.4.8.2, Suppressing Balance Due Notices, if there is a balance due on the account.

Processing Unpostables

  1. This section provides specific procedures for processing unpostables.

Preventing Unpostables

  1. Most unpostable conditions can be prevented by adhering to IRM procedures and thoroughly reviewing IDRS before making an adjustment. However, certain unpostables cannot be prevented due to the presence of specific identity theft indicators on an account to protect the taxpayer until the rightful owner of the SSN can be verified. Consider the following to prevent an unpostable:

    1. Freeze codes

    2. The effect of any transactions pending on the account

    3. Cycling transaction information, follow procedures in IRM 21.5.5.4.2.1, Cycling Transactions

  2. Implementing strategies which prevent unpostables will help you complete adjustments accurately and efficiently. For instance, make sure dates and money amounts on credit transfers match those of the credits being moved before you make the adjustment.

  3. Contact other Service employees with an open control base on IDRS to coordinate actions and prevent duplicate adjustments. See IRM 21.5.2.3 , Adjustment Guidelines - Research, for additional information.

  4. Verify that the adjustment is not a duplicate of a previous adjustment.

  5. If updating the filing status to joint and adding secondary self-employment income, the entity must be allowed to post first.

  6. Consider previous tax adjustments before inputting a subsequent adjustment, especially those within $10 of a previous adjustment. If it is still necessary, use PC 8 on the adjustment.

  7. Look for any manual adjustments of penalties and interest (TC 160, TC 161, TC 170, TC 171, TC 340, and TC 341) that need correction or recognition when inputting an adjustment.

  8. Use the correct MFT, tax period, and name control.

  9. Input the correct item adjustment codes and credit reference numbers. Consider posted amounts, and limitations for each code being input. See IRM 3.12.179.83.1, UPC 189 RC 0 Reversal TC Amount Discrepancy, for additional information.

  10. Do not reduce the following line reference numbers below zero:

    • 878 - Primary Self Employment (SE) Income

    • 879 - Secondary SE Income

    • 886 - Taxable Income

    • 887 - Number of Exemptions

    • 889 - SE Tax

    • 891 - Primary Tip Income

    • 892 - Secondary Tip Income

    • 895 - Primary Medicare Income

    • 896 - Secondary Medicare Income

    • 897 - Spousal Claim on Debtor Master File (DMF) (IMF only)

    • 898 - Primary Medicare Tip Income

    • 899 - Secondary Medicare Tip Income

      Note:

      This list is not all inclusive. Only the most common reference numbers are listed.

    For additional information see IRM 3.12.179.83.7, UPC 189 RC 1.

  11. When an adjustment is input incorrectly, the person that input the adjustment can use CC TERUP the same day to delete it. Refer to IRM 2.4.13.2, Command Code TERUP.

Resolving Unpostables

  1. Review the unpostable condition and the specific unpostable reason code (URC) to determine the cause of the unpostable.

  2. When an unpostable is closed with a URC of 1, 2, or 8, a nullification code is entered by the Unpostables function to identify the receiving area of the closed unpostables. Refer to IRM 21.5.5.3.1.2, Unpostables Nullified Distribution Listing (GUF 55-47), for more information.

  3. If the case is still open, check the transaction information to determine what must be corrected. Follow the table below to determine the appropriate action:

    If Then
    You find an error Use CC UPDIS and CC UPCASZ to enter a history item on the GUF System for the Unpostable Function. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes, above.
    The transaction should post based on the information provided Treat the transaction as "pending" and advise the taxpayer accordingly.
    An unpostable credit does not belong on the taxpayer's module and you know where it belongs Input a history item using CC UPDIS and CC UPCASZ. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes.
    You cannot determine where the credit belongs or how to resolve the unpostable condition Prepare a referral to the Unpostable Unit. Follow procedures in IRM 21.3.5, Taxpayer Inquiry Referrals Form 4442.

    Note:

    When unpostables are closed, status code "C" shows on CC UPTIN the next day. The information remains on CC UPTIN for up to 90 days. Determine if the unpostable is closed the same day by checking CC UPDIS. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes, above.

  4. If the account has a lien against it and correction of the unpostable will full pay the account, a manual lien release will be needed. Follow procedures in IRM 5.12.3.3, Lien Release Conditions, regarding manual lien releases. Submit a completed Form 13794, Request for Release or Partial Release of Notice of Federal Tax Lien, to the appropriate contact at Centralized Lien Processing.

Cycling Transactions
  1. Each week of processing is considered a cycle. All transactions (returns and adjustments) post to the MF according to the cycle they are input. Transactions pending on the accounts must also be considered.

  2. Cycles that impact processing:

    • Campus Cycle: Thursday - Wednesday

    • Master File Processing: Friday - Thursday

  3. Certain transactions require a related transaction to post first. Input the transaction(s) to the system in the desired order of posting. For instance, most transactions require the establishment of an account or tax module before subsequent transactions can post.

    Note:

    The posting sequence for MF is generally from the lowest numbered transaction code to the highest. TC 400 (transfer of account) posts last on all MFs except for BMF. In BMF, when a TC 400 and TC 150 (return) are attempting to post in the same cycle, the TC 150 will post last.

  4. Cycle delay transactions by using a posting delay code. Determine the necessary number of cycles (weeks) to delay the posting of a TC, and input that number in the appropriate field of the IDRS input screen.

  5. If the prerequisite TC with a higher number must post prior to the posting of another TC, use an appropriate cycle delay indicator.

  6. Use an appropriate cycle delay indicator when a prerequisite TC is needed to change filing requirement, balance, freeze condition, or indicator.

    Note:

    Calculate the number of cycles required by using the current cycle plus the number of cycles the adjustment action will take to post to the MF.

  7. Do not cycle delay transactions if:

    1. The posting sequence is irrelevant; or

    2. The prerequisite transaction will post first.

    Caution:

    When you enter the number of cycles to delay a transaction, consider the day of the week in relation to the day the Service Center (SC) updates to MF. If you input the transaction close to the end of the weekly posting cycle, you may need an additional cycle to allow the transaction to post.

  8. When you transfer credits using CC FRM34, the credit side re-sequences for one cycle after the debit side posts in two cycles. The CC DRT24 and CC DRT48 transfers post in two cycles.

  9. If you use CC FRM34 and CC DRT48 simultaneously, take care to force both transactions to post in the same cycle.

    1. Use a one-cycle posting delay on the credit election transfer (CC DRT48) if you move the multiple payments with CC FRM34 to avoid generating erroneous notices, offsets, and refunds.

      Note:

      Refer to, Document 6209, Section 8B.9, Resequence Codes (IMF Only), for a list of IMF Resequence Codes.

    2. For additional information regarding credit transfers, refer to IRM 21.5.8, Credit Transfers.

  10. For additional information on cycling transactions see IRM 3.12.179.15, Posting Transactions Input Timing.

Unpostables Created by Your Own Adjustments
  1. Generalized Unpostable Framework (GUF) automatically sends select unpostables back to the originator if the employee caused the condition or has information to close the case.

  2. You must resolve unpostables created by your own adjustments, credit transfers, etc..

    Reminder:

    It is critical that all unpostable cases are worked within seven business days of receipt.

  3. A control base is usually opened (Category Code NLUN) to the employee who input the transaction originally but may also be assigned to a default IDRS number. The transaction is included on the Nullified Distribution Listing (GUF 55-47) and is available on Control D.

  4. When you are notified of an unpostable transaction, research CC UPDIS and CC UPRES for the reason(s) the adjustment was nullified. Follow procedures in IRM 21.5.5.3.2.1, Unpostable IDRS Command Codes.

  5. If a correction to the adjustment is needed, re-input the transaction(s) using the corrected information and notate the NU DLN on the subsequent adjustment package. If using Correspondence Imaging System (CIS), notate the NU DLN in your CIS history remarks.

    Caution:

    Do not reinput the same transaction that unposted unless the condition causing the transaction to unpost has been corrected.

  6. After the transaction is corrected or if no action is needed, close all NLUN controls.

    Note:

    Refer to IRM 21.5.5.4.2, Resolving Unpostables, for additional information.

  7. If your merge transaction unposts with UPC 134-3 please notify the NMRG Team. See IRM 21.6.2.4.1.5, Reassignment of NMRG Cases due to Site Specialization.

  8. If your unpostable transaction is closed to Accounting, Nullify Area Code 41, contact the appropriate Accounting function for resolution. See IRM 3.12.32.15.1, URC 1 and URC D.