5.19.10  Collection Operations Transcript Processing

Manual Transmittal

October 4, 2012

Purpose

(1) This transmits revised IRM 5.19.10, Liability Collection, Collection Operations Transcript Processing.

Material Changes

(1) IPU 12U1225 issued 06-19-2012 IRM 5.19.10.4, Kansas City CSCO will accept TAS OARs and Form 843 Claims for CSED issues.

(2) IPU 12U1225 issued 06-19-2012, IRM 5.19.10.4.4, added additional CSED issues to be aware of when verifying CSED accuracy.

(3) IPU 12U1225 issued 06-19-2012, IRM 5.19.10.4.7, added a requirement to get HQ analyst approval on write offs of over a certain dollar criteria.

(4) IPU 12U1225 issued 06-19-2012, IRM 5.19.10.4.7.1, added a new section, "MULTICSED Transcripts and Listings" .

(5) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.5.9, added close BMF DUPREF transcripts with no action.

(6) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.6.2, added the applicable closing codes next to each war.

(7) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.6.5.5, revised IRM references throughout.

(8) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.6.5.6, revised IRM references throughout.

(9) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.7.2.3, added direction under (8) to input TC 500 entry to a prior year, when no return was filed for the year of entry. Address entry dates for first time filers. Wording changes throughout.

(10) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.10.3.1 changed criteria for SIA.

(11) IPU 12U1013 issued 05-15-2012 IRM 5.19.10.10.3.4, changed criteria for SIA.

(12) IPU 12U0807 issued 04-10-2012 IRM 5.19.10.5.2.6, added link to IRM 5.19.10.5.1, General Procedures for All Transcripts regarding transfer of payments to URF and XSF.

(13) IRM 5.19.10.5.5.1, rescinded instruction to take no action if the last CSED will expire within 90 days,

(14) IRM 5.19.10.6.2, expanded description in (11)b.

(15) IRM 5.19.10.6.5.5, expanded IRM reference for IRM 5.19.6.2. replaced (17)a and b.

(16) IRM 5.19.10–5, correct the links in the table.

(17) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.4.3(9)a - clarified referrals to the Headquarter analyst apply to WI only.

(18) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.4.5(3) - changed the IRM reference for TC 550 Definer Codes.

(19) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.5.1 - added information regarding the Erroneous Manual Refund Tool.

(20) IPU 12U0607 (superseded by IPU 12U0807 issued 04-10-2012) issued 03-16-2012 IRM 5.19.10.6.2, added a link referring to IRM 5.19.10.7.2.4 for determining correct entry/exit dates.

(21) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.6.5.4 - expanded procedures on determining dates when documentation is required.

(22) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.6.5.7 - added a link referring to IRM 5.19.10.7.2.4 for determining correct entry/exit dates.

(23) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.7.2.3 - added GII is excepted from the requirement to request documentation.

(24) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.7.2.4 - expanded procedures on determining dates when documentation is required.

(25) IPU 12U0607 issued 03-16-2012 IRM 5.19.10.9.5(2) - edded instructions to follow when bank info is missing from CC EFTAD.

(26) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.4(1) and IRM 5.19.10.4.1 were moved to IRM 5.19.10.4.8.

(27) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.4 was rewritten and new sections IRM 5.19.10.4.1 through IRM 5.19.10.4.7 were added regarding verifying and correcting Collection Statute Expiration Dates.

(28) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.5.1, rewrote section, General Procedures for All Transcript.

(29) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.5.5, rewrote section, CSED Transcripts.

(30) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.5.5.1, rewrote section, Processing CSED Transcript.

(31) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.2, added procedures for requesting documentation for combat zone participants.

(32) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.2.1, added information about requiring documentation from combat zone participants.

(33) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.5.1, added information about requiring documentation from combat zone participants.

(34) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.5.4, added information about requiring documentation and procedures for when documentation is received.

(35) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.5.5, added information about requiring documentation from combat zone participants. Removed information about telephone etiquette. Moved information about documentation to IRM 5.19.10.6.2. Changed criteria from 30 days to 60 days in (17)a, (change to (17)a was superseded by IPU 12U0807 issued 04-10-2012). Added directions to monitor the account until able to input TC 500, due to TC 150s with future dates.

(36) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.6.5.7, added information about requiring documentation and procedures for when documentation is received.

(37) IPU 12U0318 issued 02-15-2012 IRM 5.19.10.7.2.3, added information about requiring documentation from combat zone participants and procedures for when documentation is received.

(38) IPU 12U0318 issued 02-15-2012 IRM 5.19.19.7.2.4, Added instructions to allow taxpayer's dates if within 60 days of documentation.

(39) IPU 12U0318 issued 02-15-2012 Exhibit 5.19.10-5 through Exhibit 5.19.10-9 were added for verifying and correcting Collection Statute Expiration Date.

(40) IPU 12U0253 issued 01-27-2012 Exhibit 5.19.10-4 IAAL Prioritization List, change the months that the exception criteria applies under Tier 2.

(41) IPU 11U1894 issued 12-14-2011 IRM 5.19.10.8.6.1(1) under I - Freeze, add a reference to IRM 21.4.4.

(42) IPU 11U1894 issued 12-14-2011 (change superseded 09-15-2012), IRM 5.19.10.8.8.3(1) under (5), add a reference to IRM 21.4.4.

(43) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.3.11 - Added a link to SERP Who/Where for MOIC contacts.

(44) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.5.1 - Added transcripts referred to CSCO from Accounts Maintenance or the Statute function due to a levy payment should be reassigned back to the originator. Added reference to IRM 21.4.4, Manual Refunds.

(45) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.5.2.1 - Instruction to suspend the case for 45 days when sending the 672C letter was moved to 12(c).

(46) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.5.2.3(1) Note - Regarding application of barred payments.

(47) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.5.5 - Added direction to destroy CSED transcripts issued on TFRP accounts.

(48) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.5.11.1 - Revised instructions in (3) and (5) regarding true No Merge accounts and the assignment of temporary numbers.

(49) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6 - Added (2) IRC 7508 provisions.

(50) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.2 - Changed section title to "Combat Zone Qualified Individuals and Areas" , moved (1) to IRM 5.19.10.6, revised dates and areas.

(51) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.3(3) - Added new military operation names to the table.

(52) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.4 - Added IRM reference.

(53) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.5 - Moved (4) to the end of (3).

(54) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.5.5 - Made several changes throughout the section. Revised procedures on handling a balance due and other open TC 500s.

(55) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.5.6 - Revised procedures on handling a balance due.

(56) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.5.7 - Revised (1) and (6)(c), changed IRM references in (7). Paragraphs are renumbered to (8) and (9).

(57) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.6.5.8 - (1) Table, 2nd Then box, follow (7) through (11); (6) Table, last Then box, added 4th bullet, advise taxpayer to call to obtain a current balance; revised (9) regarding computation of penalty and interest.

(58) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.7.2.1 - Revised (3).

(59) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.7.2.2 - Added (3) and revised (4) and (6) Table.

(60) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.7.2.3 - Rewrote for clarity.

(61) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.7.2.4 - Added (2) and instructions for taxpayers who claim combat zone for services performed in unqualified areas.

(62) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.8.1(2) - Added information to the end of the paragraph.

(63) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.8.1(3) - Added explanations to the list of transcript types.

(64) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.8.4(1) - Listed the applicable reason codes for Type S Diag-Q transcripts.

(65) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.8.5 - Removed procedures for Types D and R. Revised the list of module statuses for Type E under (1). Removed last paragraph.

(66) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.10.3.3 - Added instructions for defaulted installment agreements with balances of $100,000 - $999,999.

(67) IPU 11U1595 issued 10-13-2011 IRM 5.19.10.10.4 - Added instructions for defaulted installment agreements with balances of $100,000 - $999,999.

(68) Various editorial changes made throughout the IRM.

(69) IRM 5.19.10.1(1), added an exception for EFT Listings. Atlanta CSCO works all EFT Listings.

(70) IRM 5.19.10.10.3.1(3), changed dollar criteria

(71) IRM 5.19.10.10.3.4(2), changed dollar criteria.

(72) IRM 5.19.10.3.11(3), added reminder to follow (1) and research AMS for TFRP history.

(73) IRM 5.19.4, clarified what accounts Kansas City CSCO will work for CSED issues.

(74) IRM 5.19.10.4.7.1(1), $10,000 criteria is for IMF only.

(75) IRM 5.19.10.4.7.1(2), information on writing off TC 360 and TC 280.

(76) IRM 5.19.10.5.1(4), added "to input TC 472"

(77) IRM 5.19.10.5.1(6) expanded instructions for the completion of Forms 2424 and 8758.

(78) IRM 5.19.10.5.2, rewrote and added information on the purpose of the PMTEXPCSED transcript.

(79) IRM 5.19.10.5.2.1, rewrote the section. Information in (6)a regarding an unreversed TC 608 was clarified.

(80) IRM 5.19.10.5.2.2, removed first paragraph regarding controlling the account.

(81) IRM 5.19.10.5.2.3, rewrote the section.

(82) IRM 5.19.10.5.2.4, re ordered information on TC 694.

(83) IRM 5.19.10.5.2.5(1), removed the statement regarding the computer's ability to issue a refund.

(84) IRM 5.19.10.5.2.6(1) box 4, removed the information regarding TC 608 and TC 609.

(85) IRM 5.19.10.5.11.1(3), changed SERP Alert reference to an IRM reference.

(86) IRM 5.19.10.6, removed (2) that explains IRC 7508. This information is already present in IRM 5.19.10.6.2.

(87) IRM 5.19.10.6.2.1(6), added a reference to IRM 5.19.10.6.5.2 regarding administrative relief for certain taxpayers.

(88) IRM 5.19.10.6.2(11)(g) was moved to IRM 5.19.10.6.1(5).

(89) IRM 5.19.10.6.3(7) and (8), moved the note up in the bullet list under Collection Statute Expiration Date. Changed IRM reference in (8).

(90) IRM 5.19.10.6.5.4(10), deleted the words "date of deployment" . Date of entry is what is required.

(91) IRM 5.19.10.6.5.5(9), update AMS with organization name and phone number.

(92) IRM 5.19.10.6.5.8(6), added the choice to use Letter 2761C.

(93) IRM 5.19.10.7.2.2(6) Note, changed wording from "campus" to "employee" and changed required AMS history narrative.

(94) IRM 5.19.10.8.2.1, Figure 5.19.10–7. Changed the statement under the Confidentiality Notice.

(95) IRM 5.19.10.8.6.1(1), under OIC, add direction to destroy Numerics 1 and 2.

(96) IRM 5.19.10.10.6(2), revised information under Partial Pay Installment Agreements (PPIAs). Centralized Case Processing now monitors PPIAs through an IAT tool.

(97) Exhibit 5.19.10–5, revised Table.

Effect on Other Documents

IRM 5.19.10 dated September 20, 2011 (effective September 30, 2011) is superseded. The following IRM Procedural Updates (IPUs), issued from October 13, 2011 through July 25, 2012, have been incorporated into this IRM: 11U1595, 11U1894, 12U0253, 12U0318, 12U0607, 12U0807, 12U1013, 12U1225, and 12U1410.

Audience

Small Business Self Employed (SB/SE) and Wage and Investment (W&I) Compliance employees who work Collection programs.

Effective Date

(10-15-2012)

Dagoberto Gonzalez
Director, Filing and Payment Compliance
Wage and Investment Division

5.19.10.1  (10-15-2012)
Compliance Services Collection Operation Transcript Overview

  1. This section contains instructions for Compliance Services Collection Operation (CSCO) transcript programs. Wage and Investment (W&I) CSCO works Individual Master File (IMF) accounts and Small Business/Self-Employed (SB/SE) works Business Master File (BMF) accounts.

    Exception:

    Atlanta works all Electronic Funds Transfer (EFT) Listings for IMF and BMF.

  2. Various transcripts generate on modules assigned to Compliance when specific account conditions exist. Research and appropriate account actions are required to resolve the account or move it back into the collection stream.

  3. The transcripts discussed in this section are as follows:

    • Credit Offsets

    • Collection Statute Expiration Date (CSED)

    • Balance Due Transcripts

    • Diagnostic-Q Transcripts

  4. Each of the transcripts which generate require research specific to that program. This requires conducting research through Integrated Data Retrieval System (IDRS) or any other systems available to resolve the transcript.

  5. While processing transcripts you may need to reference and use the following IRMs in conjunction with the instructions provided in this IRM:

    • IRM 2.3, IDRS Terminal Responses

    • IRM 2.4, IDRS Terminal Input

    • IRM 2.9, Integrated Data Retrieval System Procedures

    • IRM 3.13.62, Media Transport and Control

    • IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates

    • IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines

    • Document 6209, IRS Processing Codes and Information

  6. 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.

    1. Refer taxpayers to TAS when the contact meets the TAS criteria in IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, and you can't resolve the taxpayer's issue the same day. For a definition and procedures for "Same Day" resolutions, see IRM 13.1.7.4, Same Day Resolution by Operations.

    2. When you refer cases to TAS, use Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order), and forward to TAS.

5.19.10.2  (10-15-2012)
Acronyms/Definitions

  1. The following table lists the various acronyms (abbreviations) which may be used in the processing of transcript inventories and used throughout this IRM:

    Acronyms Definitions
    AC Action Code when used with Transaction Code (TC) 971 Miscellaneous Code. IDRS displays it as "971-CD" . Refer to Document 6209, IRS Processing Codes and Information, TC 971 Action Codes.
    ACS Automated Collection System
    ACTON Command Code used to establish control bases, to update or close control bases that are open, to correct name controls on dummy accounts, to append history items to modules on IDRS, and to generate TC 902s to secure tax modules and their related entity data from the Master File. See IRM 2.3.12, Command Code ACTON.
    ADD24/48, ADC24/48, ADD34, ADC34, FRM34, AND DRT24/48 These Command Codes are used to input two-sided credit transfers. and generate TC 902s to secure tax modules and their related entity data from the Master File. Refer to IRM 2.4.17, Command Codes ADD24/34/48, ADC24/34/48, FRM34, and DRT24/48.
    ADR Address Research
    ALP Automated Levy Program
    AM Accounts Management
    AMRH Account Maintenance Research History
    ANMF Automated Non Master File
    ASED Assessment Statute Expiration Date
    ASFR Automated Substitute For Return
    ASGNI ASGNB These Command Codes have five functions that may be used with accounts that are present on the Taxpayer Identification File (TIF). Refer to IRM 2.4.27, Command Code ASGNI/ASGNB formerly TSIGN. These functions include:
    • Controlling and updating Taxpayer Delinquent Account (TDA) and Taxpayer Delinquency Investigation (TDI) assignment numbers.

    • Posting Notice Codes for subsequent processing by weekly analysis.

    • Posting Alpha Case Codes for subsequent processing by weekly analysis.

    • Posting Determined Grade Levels for subsequent processing by weekly analysis.

    • Requesting a printed TDI assignment.

    ATFR Automated Trust Fund Recovery
    BMF Business Master File - A magnetic tape containing information on each taxpayer's business returns and related documents.
    BMFOL Business Master File On-Line Command Code furnishes read-only access to the Business Master File. See IRM 2.3.59, Command Codes BMFOL and BMFOR.
    BMFOR Command Code provides access to the BMF retention tax modules from accounts that merged to a new Taxpayer Identification Number (TIN). See IRM 2.3.59, Command Codes BMFOL and BMFOR.
    BOD Business Operating Division
    cc Closing Code when used with a transaction code
    CC Command Code for IDRS processing
    CCP Centralized Case Processing
    CDP Collection Due Process
    CLC Collection Location Code
    CNC Currently Not Collectible
    CO Contingency Operation
    COIC Centralized Offer In Compromise
    COMPA Command Code which computes the interest on a specified amount for a specified period of time. See IRM 2.3.29, Command Codes INTST, ICOMP, and COMPA.
    CP Case Processing
    CP Computer Paragraph
    CSCO Compliance Services Collection Operation
    CSED Collection Statute Expiration Date
    CZ Combat Zone
    AMS Accounts Management System
    DLN Document Locator Number
    DoD Department of Defense
    DPC Designated Payment Code
    ECC-MTB Enterprise Computing Center at Martinsburg (ECC-MTB), formerly Martinsburg Computing Center (MCC)
    ERRF Erroneous Refund
    EIN Employer Identification Number
    ENMOD Command Code which provides name, address, and other entity information from an input of the TIN. Refer to IRM 2.3.15, Command Code ENMOD.
    ENREQ Command Code with a blank definer is keyed in after a response to ENMOD indicates that the entry is on the file. Command Code with "R" definer is keyed in after response to ENMOD indicates that the entry is on the file. Refer to IRM 2.4.9, Command Codes ENREQ, INCHG, IRCHG, BNCHG and BRCHG for information.
    FMS Financial Management System
    FPLP Federal Payment Levy Program
    FS Filing Status
    FTP Failure To Pay
    GII Generalized IDRS Interface. - An application that interfaces with IDRS to do input previously done manually, such as establishing installment agreements, or to do bulk corrections.
    GUF Generalized Unpostable File
    IA Installment Agreement
    IAAL Installment Agreement Account Listing
    IADFR Command Codes are:
    • IAGRE—Used to request the format for entering IAORG, IAPND, or IAREV

    • IAORG—Used to initially enter an Installment Agreement on an account that contains balance due modules

    • IAPND—Used to initially enter, revise or nullify pre-assessed installment agreement

    • IAREV—Used to revise an established Installment Agreement or to initially establish an agreement in deferred status

    • IADFL—Used to default an existing Installment Agreement

    • IADIS—Used to display the Installment Agreement data

    • IADFR—Used to establish Status 63 modules across computing centers. Access to this command code will be from command codes IAORG and IAREV

    Refer to IADFR. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL, and IADIS.
    IADIS Refer to IADFR above. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL, and IADIS
    IAGRE Refer to IADFR above. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL and IADIS.
    IAORG Refer to IADFR above. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL and IADIS.
    IAPND Refer to IADFR above. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL and IADIS.
    IAREV Refer to IADFR above. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL and IADIS.
    ICOMP Command Code which computes payment information for an installment agreement. See IRM 2.3.29, Command Codes INTST, ICOMP and COMPA.
    IDRS Integrated Data Retrieval System - A computer system with the capability to instantaneously retrieve or update stored information which works in harmony with the Master File system of taxpayer accounts.
    IDS Inventory Delivery System
    IMF Individual Master File
    IMFOL Individual Master File On-Line Command Code which provides read-only access to the Individual Master File. Fields available include basic identifying information, amounts, dates, codes, indicators, and freezes. See IRM 2.3.51, Command Code IMFOL.
    INOLES Command Code is used as a research tool to display the entity information on the NAP. The NAP (National Account Profile in Martinsburg) contains extensive Master File entity information for all taxpayers on the Individual Master File, Business Master File (social security Number and employer identification number), and Employee Plan Master File. There is also Social Security data (DM-1) and spouse cross-reference data. See IRM 2.3.47, Command Codes INOLE, EOGEN and SPARQ.
    INTST Command Code which computes the balance, including interest and failure to pay accruals, to the date specified in the input. See IRM 2.3.29, Command Codes INTST, ICOMP and COMPA.
    IRC Internal Revenue Code
    IRM Internal Revenue Manual
    IRPTR Command Code allows users to request either online or hardcopy Information Returns Processing (IRP) transcripts from the Information Returns Master File (IRMF). Refer to IRM 2.3.35, Command Code IRPTR.
    IRS Internal Revenue Service
    IRSN Internal Revenue Service Number
    ISRP Integrated Submission and Remittance Processing System
    LEVY Command Code which allows one to research specific levy source information. See IRM 2.4.31, Command Code LEVY.
    LRA Last Return Amount
    LT Letter to taxpayer
    LP Letter to third party
    MARS Manual Accounting Replacement System
    MF Master File - A magnetic tape containing information concerning all taxpayers who file individual tax returns.
    MFT Master File Tax Account Code - A two-digit number which identifies the type of tax.
    MFREQ Command Code uses definers C or D or RECON to request an entity module or a tax module and its related entity data when case control is not required. See IRM 2.3.10, Command Codes MFREQ and RECON.
    MRS Microfilm Replacement System
    NMF Non Master File - A file containing records of accounts for which manual procedures must be maintained.
    NMFL Non Master File Liability
    NOMRG No Merge
    OIC Offer in Compromise - A proposal for settlement of tax liability for an amount less then that previously assessed (or unassessed) or a liability for specific penalties assessed (or unassessed). See IRC 7122, Compromises.
    OB Outstanding Balance
    OOB Out of Business
    P&I Penalty and Interest
    PCB Primary Code B
    QHDA Qualified Hazardous Duty Area
    RC Reason Code
    RECON Command Code will download the module data from Corporate Files On Line (CFOL) to the local IDRS while the user is waiting online. Refer to MFREQ for IRM reference.
    REQ77 Command Code used to request a format to input a transaction on Form 3177, Notice of Action for Entry on the Master Files, or a related document. See IRM 2.4.19, Command Codes REQ77, FRM77 and FRM7A.
    RO Revenue Officer
    RSED Refund Statute Expiration Date
    RTR Remittance Transaction Research System
    RTVUE Command Code that provides display of line items transcribed from Form 1040 series and their accompanying schedules and/or forms as the returns are processed at the campuses. Refer to Document 6209, IRS Processing Codes and Information.
    SBSE Small Business Self Employed Operating Division
    SC Service Center - SC is still used on IDRS, although Service Centers are now referred to as Campuses
    SERP Servicewide Electronic Research Program (http://serp.enterprise.irs.gov)
    SSA Social Security Administration
    SSN Social Security Number
    ST Status
    STAT Statute
    STAUP Command Codes including STATI and STATB are used with modules that are or have been balance due modules. See IRM 2.4.28, Command Code STAUP, STATI, and STATB.
    SUMRY Command Code which provides research for all master file accounts. See IRM 2.3.11, Command Codes TXMOD and SUMRY.
    TAS Taxpayer Advocate Service
    TC Transaction Code - A three digit numeric, which defines the precise nature of the transaction. Refer to Document 6209, IRS Processing Codes and Information, for a listing of transaction codes.
    TDA Taxpayer Delinquency Account
    TDI Taxpayer Delinquency Investigation
    TERUP Command Code which allows an employee to delete his/her erroneous IDRS entry/entries on the day of input. See IRM 2.4.13, Command Code TERUP.
    TFRP Trust Fund Recovery Penalty
    TIF Taxpayer Identification File (IDRS)
    TIN Taxpayer Identification Number - Every taxpayer has a permanent number for identification of their account. The Employer Identification Number (EIN) is used to identify taxpayers on the BMF. The Social Security Number (SSN) is used as the account number of the taxpayer on the IMF.
    TOP Treasury Offset Program
    TSf Territory Support function
    TSIGN Obsolete Command Code; refer to ASGNI/ASGNB.
    TXMOD Command Code which provides research for all master files by modules. See IRM 2.3.11, Command Codes TXMOD and SUMRY.
    TXPD Tax Period
    UD Undelivered
    UFA Unverified Forwarding Address
    UPTIN Command Code used to provide research for unpostables. See IRM 2.3.37, Command Code UPTIN for the GUF System.
    URF Unidentified Remittance File - A separate file within IDRS containing all remittances received which cannot be immediately identified or applied. Each record within the file contains the UR control number, amount of remittance, type of remittance, received date, taxpayer's name and other identifying information, if known.
    URINQ Command Code which requests the display of one or more records from the Unidentified Remittance File. See IRM 2.3.20, Command Code URINQ (URF).
    W&I Wage and Investment Operation Division
    XSF Excess Collection File - A file within the IDRS containing non-Revenue Receipts which cannot be identified or applied. Each record within the file contains the XS control number, amount of credit, type of credit, received date and other identifying information, if known. XSF reflects contents of Accounts 6800 and 9999 less than seven years and more than one year after the IRS received date except in true statute cases, where it may be under one year.
    XSINQ Command Code which displays one or more records in the Excess Collection File (XSF). See IRM 2.3.45, Command Code XSINQ.

5.19.10.3  (05-01-2007)
Credit Offsets

  1. If a determination is made that an overpayment on an account should be applied to another account or liability and a systemic offset will not happen, request the input of TC 130.

5.19.10.3.1  (10-15-2012)
Use of Credit Offset

  1. TC 130 is an entity transaction on CC ENMOD and will display the cross reference information and the campus (literal = SC>) that input the freeze.

  2. The Treasury Offset Program (TOP) allows credits to be applied against delinquent child support obligations, non-tax debts owed to other Federal agencies, State income tax obligations and unemployment compensation debt. TOP TC 130s are systemically engaged and released by the agencies requesting these freezes. Refer to IRM 21.4.6, Refund Offset.

  3. If a credit of ≡ ≡ ≡ ≡ ≡ or more becomes available, a CP 44 (IMF) or CP 188 (BMF) is generated to that campus.

  4. On CC TXMOD the presence of a TC 130 can be identified by freeze code "V—" .

5.19.10.3.2  (09-15-2009)
Request Input of TC 130

  1. Requests for input of TC 130 may be received on the following:

    • Form 3177,Notice of Action for Entry on Master File

    • Form 53,Report of Currently Not Collectible Taxes

    Note:

    The above forms, initiated by the field, should be processed through Centralized Case Processing in Philadelphia. All other functions are required to follow local guidelines for TC 130 input.

  2. Examine the request to ensure that the following information is given for each debit (balance due) account:

    • Tax form number

    • Tax period

    • Taxpayer's name (name of each taxpayer responsible for any joint liability)

    • Taxpayer identification number (including cross referenced liabilities)

  3. If the information is incorrect or incomplete, you must contact the originator to secure the correct information, or return the request for completion.

    Reminder:

    Requests for TC 130 input are only appropriate in situations where the Master File cannot offset the credit automatically.

5.19.10.3.3  (05-01-2007)
Input of TC 130 on IMF

  1. Consider input of TC 130 to the IMF when:

    • The taxpayer also has a Non-Master File account.

    • An IMF taxpayer is a partner or sole proprietor and has existing BMF liabilities.

    • An IMF taxpayer owes a single liability and is subsequently filing jointly as a secondary taxpayer.

    • An IMF taxpayer previously filed jointly with another taxpayer that had a tax liability and is now filing jointly with another primary taxpayer.

    • An IMF secondary taxpayer had an invalid SSN on a joint return with a tax liability, then subsequently files a refund return as a single taxpayer with a valid SSN.

    • An IMF taxpayer has a Trust Fund Recovery penalty or other civil penalty and usually files a secondary SSN on Form 1040,U.S. Individual Income Tax Return or equivalent Form 1040, series return filed by international taxpayers.

    • An IMF taxpayer has an MFT 31 assessment under his/her own SSN and usually files as a secondary SSN on Form 1040, U.S. Individual Income Tax Return.

    • An IMF taxpayer whose OIC has been accepted.

5.19.10.3.4  (05-01-2007)
Input of TC 130 on BMF

  1. Consider input of TC 130 to the BMF when:

    • There are IMF balance due modules owed by individuals who are active on the BMF.

    • There are Individual Retirement Account File balance due modules owed by individuals who are active on the BMF.

    • There are Non Master File balance due modules owed by taxpayers (any type of entity) who are active on the BMF.

    • There are BMF balance due modules owed by taxpayers who are liable for taxes on the BMF under more than one TIN.

5.19.10.3.5  (10-15-2012)
Input of TC 130 on IDRS

  1. To input a TC 130 on CC ENMOD, use CC REQ77 and input the following:

    1. TIN

    2. Name control

    3. Cross-reference TIN where credit should be applied

  2. If block 6b on Form 53, Report of Currently Not Collectible Taxes is checked "yes" , input the closing code of the TC 530, BMF name control, and cross-reference EIN.

  3. One of the following Document Locator Number Indicators should be input:

    • 000 — Master File Assessment

    • 001 — Offer in Compromise

    • 002 — Non-Master File

    • 004 — Taxpayer Request

    • 102 — Trust Fund Recovery Penalty

  4. If the request lists more than one partner on the BMF account, input a TC 130 to each individual entity module.

  5. After input, destroy the document. Retention of paper files is no longer required.

5.19.10.3.6  (05-01-2007)
TC 130 Requests from Non-Master File Accounting Function

  1. At the time a Non-Master File assessment is made, ANMF will not systemically post the TC 130 to Master File. Manual input of TC 130 is still a requirement.

5.19.10.3.7  (10-15-2012)
TC 130 Requests for Trust Fund Recovery Assessments

  1. The Automated Trust Fund Recovery System will generate a Form 3177, Notice of Action for Entry on Master File, to hold any refunds prior to the assessment posting on the taxpayer's account. Additional information will include the EIN of the corporation as cross-reference and the TC 130 DLN indicator will be "102" .

5.19.10.3.8  (10-15-2012)
TC 130 Requests from Underreporter and Examination Function

  1. Taxpayers may agree to assessments made by the Underreporter and Examination functions by requesting that their anticipated refund be applied to the assessment. Underreporter and Examination requests input of TC 130 on these accounts by forwarding a copy of the taxpayer's request to WI CSCO for IMF cases and SB/SE CSCO for BMF cases.

  2. DLN indicator "004" should be used. If the amount held does not fully satisfy the assessment, apply all available credit and input a TC 131. Any future refunds will automatically offset to the liability.

5.19.10.3.9  (09-15-2009)
Input of TC 131

  1. Research for any outstanding liabilities on IDRS.

    1. If there are no liabilities on IDRS, research ANMF or request a transcript from NMF.

    2. If no liabilities remain on IDRS or NMF, input the TC 131 to CC ENMOD using CC REQ77.

    3. Destroy paper document(s), if available.

5.19.10.3.10  (10-15-2012)
Generation of CP 44 and CP 188

  1. When a TC 130 is input, it will generate a V— freeze code for the account. When a refund at or above ≡ ≡ ≡ ≡ ≡ ≡ becomes available it is frozen. A notice, Delay in Processing Your Refund, is mailed to the taxpayer, and at the same time a CP 44 for IMF or a CP 188 for BMF will generate to WI CSCO and SB/SE CSCO respectively.

  2. Work the CP 44/188 as follows:

    1. If the X-REF TIN associated with the TC 130 on CC ENMOD is an EIN, or a pending TFRP assessment is indicated by a "21" in positions 9 and 10 of the DLN, DO NOT release the TC 130 until research has been conducted per IRM 5.19.10.3.11, Research Prior to Transfer of Credits.

    2. Sort out the CPs with a "1" in position 9 of the DLN, and route to the OIC team.

    3. Refer to IRM 25.15.2.4.3, TC 130 Entire Account Frozen From Refunding, for more information on innocent spouse relief TC 130s. TC 130s generated from input of TC 971 AC 065 carry a DLN beginning with "17" .

    4. If a NMF account is indicated, "2" in position 9 of the DLN, secure the ANMF transcript from AMS or ANMF, and prepare Form 2424,Account Adjustment Voucher, to transfer the credit. Forward to the appropriate centralized NMF campus via Form 3210,Document Transmittal.

    5. If research indicates that the entire balance due, including accruals, is less than ≡ ≡ ≡ , input the TC 131 and destroy any paper documents.

    6. If an unreversed TC 520 is on the account, send a request to Territory Support function, for advice on the proper disposition of the credit via Form 3210, Document Transmittal.

    7. If the available credit exceeds the balance due amount or if the balance due is zero, research cross-reference TIN modules on IDRS for any other balance due modules.

    8. If the debit balance is more than the amount of the available credit, note the cross-reference TIN on the CP 44/188 and process as in IRM 5.19.10.3.12, Transfer of Credits.

5.19.10.3.11  (10-15-2012)
Research Prior to Transfer of Credits

  1. If the X-REF TIN associated with the TC 130 on CC ENMOD is an EIN or a pending TFRP assessment is indicated, research AMS history on the TC 130 SSN and spouse SSN for the presence of history regarding Trust Fund Recovery Penalty.

    Example:

    "Trust Fund Recovery - for questions please contact IRS Revenue Officer RO NAME at ( xxx ) xxx xxxx for the responsible party, taxpayer name, 000-00-0000 of the Corporation, CORPORATION NAME, 00 - 0000000" .

    If... And... Then...
    History is present   Research both spouses, for a TFRP balance due
    History is not present   Follow normal TC 130 research procedures
    TFRP balance due is present   Input TC 131 to allow the overpayment to offset
    TFRP balance due is not present AMS history is less than 6 months old Do not input TC 131. Update AMS and close case
    AMS history is over 6 months old Make two attempts to contact the Revenue Officer listed on AMS. Allow three days for call back. Follow the Revenue Officer's instructions regarding the TC 130. Update AMS and close case.
    Unable to contact the Revenue Officer   Input TC 131 to release the overpayment

  2. Exercise caution to ensure that there is a basis for offsetting credits. A credit from an entity with an individual filing requirement cannot be offset to an entity with non-individual filing requirements.

    Example:

    Do not apply credits on Form 1040, U.S. Individual Income Tax Return to debits on Form 1120, U. S. Corporation Income Tax Return, Form 1041, U.S. Fiduciary Income Tax Return for Estates and Trusts, and Form 990, Return of Organization Exempt from Income Tax, series without written authorization from the taxpayer. The reverse is also true.

  3. If the cross-reference balance due module is a Limited Liability Corporation (LLC), do not offset the credit. Input TC 131, if no other balances are owed.

    Reminder:

    If the Trust Fund Recovery Penalty history is present in AMS, follow the research steps in IRM 5.19.10.3.11(1) to determine if TC 131 is appropriate.

  4. If the credit cannot be legally offset, input TC 131 to release it.

  5. If the cross reference TIN's module has a posted TC 608, the Collection Expiration Statute Date has expired and the balance will be ".00" .

    1. If the date of the payment is prior to the cross reference TIN's posted CSED and the last TC 608 amount is significant, (other than .00), transfer the credit.

    2. To transfer a credit to an expired CSED module, use CC ADD34 with the appropriate bypass code to avoid causing an unpostable and proceed to d) below.

    3. If the date of the payment is after the cross-reference TIN's module posted CSED, do not transfer the credit, proceed to d) below.

    4. Release the TC 130 freeze with a TC 131.

  6. Installment privileges for Form 1041, U.S. Fiduciary Income Tax Return (for Estates and Trusts), is automatically set up by the computer when the taxpayer files the tax return by the due date and pays one-fourth of the balance due. Input TC 131 if the following conditions apply:

    • Current status code is 14

    • Taxpayer is making quarterly payments, and

    • There are no other debit modules

  7. Under the authority of Internal Revenue Code (IRC) 6402 (a), the entire credit on a joint return may be tentatively applied to one spouse's balance due if no statement is received from the taxpayer on the allocation of the credits:

    1. Transfer credit per IRM 5.19.10.3.12, Transfer of Credits, below.

    2. Send Letter 678C to the non-liable spouse.

    Note:

    If the credit becomes available before the due date of the return, use the TC 150 date to move credit. Do this only if the taxpayer filed the return earlier than the return due date.

  8. The following If/Then Chart provides procedures on how to process accounts with certain freeze codes.

    If... Then...
    Freeze Code L — created by TC 971 AC 065, Innocent Spouse Claim Pending Determine which taxpayer filed the innocent spouse claim (If the TIN field is blank, the primary is the claimant). Retain the freeze, but do not transfer the credit if it is on the requesting spouse's account. Transfer the credit if it is from the non-requesting spouse's account.
    Freeze Codes —W and —V created by TC 520. Forward to TSf, using Form 3210, Document Transmittal, for determination.

    Note:

    TC 520 cc 76 (lien) or TC 520 cc 77 (levy) are Collection Due Process, CDP, cases. These cases should be referred to the appropriate CDP Coordinator.

    Freeze Code —R created by TC 570 is present as a result of a pending adjustment or credit transfer which will use the credit. Take no action.
    Freeze Code —R created by TC 570 resulting in a freeze input to hold the credit for manual offset. Resolve following IRM 5.19.10.3.12, Transfer of Credits.
    A —Y freeze created by a TC 480/780 is present on the primary TIN. Forward to the OIC monitoring unit for determination per SERP Who/Where.
    A —Z , freeze created by a TC 914 and freeze code Z— created by TC 916 and 918 are present. Forward to Criminal Investigation following campus direction.

  9. Prior to moving your credit, look for a Large/Corporation case indicator. If the indicator is present, contact the Technical Unit for instructions.

5.19.10.3.12  (05-01-2007)
Transfer of Credits

  1. When transferring credits, refer to Exhibit 21.5.8–1, Transaction Codes and Reversals.

  2. If the credit can be transferred on IDRS, use CC ADD24 or ADC24.

  3. Form 2424, Account Adjustment Voucher, must be prepared to transfer a credit to a NMF account:

    1. Input TC 270 as secondary amount, if applicable

    2. Input TC 680 as the amount for interest (TC 340) assessed and paid

    3. Manually compute the allowable interest on the credit transfer amount, if applicable

  4. The chart below provides procedures for application of credits when there are one or more debit modules.

    If... And... Then...
    There is only one debit module. The available credit amount satisfies the debt. Transfer the credit using TC 824 (debit) and TC 700 (credit). The TC 130 will be released and the remaining credit will refund.
    There is more than one debit module. The available credit does not satisfy the debt. Transfer the credit using applicable TC codes. Address the oldest CSED modules first, and maintain the TC 130 on the account.

  5. When there is more than one debit module, and the available credit will exceed the total debit:

    1. Transfer the credits using applicable transaction codes.

    2. Send taxpayer the Letter 678C

    3. Input TC 131 to CC ENMOD using CC REQ77 with a 2 cycle delay.

    4. Destroy all documents after they are returned from the reviewer. Retention of paper files is no longer required.

  6. If allowable interest is to be transferred, use TC 850 (debit) and TC 770 (credit).

    1. Use the date of input for transaction date.

    2. Input posting delay code 2 on debit and credit side to allow TC 770 to post.

  7. If a liability remains after application of the available credit, close the control base, if applicable.

  8. If the available credit is being transferred to an account with a TC 530 cc 03, change the address to the address shown on the CP 44, if different.

5.19.10.3.13  (05-01-2007)
Point of Count

  1. Count as follows:

    • Each CP 44/188 as one

    • Each primary TIN on the TC 130 listing, as one

    • Each TC 130/131 request, as one

    • Each related unpostable (no count)

    • Each undelivered CP 44/188 received (no count)

    • Take no count on any related clerical duties

5.19.10.4  (10-15-2012)
Collection Statute Expiration Date (CSED)

  1. The procedures in this section and subsections apply only to employees in Kansas City Collection, working MULTICSED Transcripts or listings, OFP 810–61260 and CSED corrections, 810–61261. This is for IMF accounts only that are NOT in Status 22.

  2. Beginning in July 2012, Kansas City Collection will accept the following referrals regarding WI CSED cases:

    • Form 843, Claim For Refund and Request for Abatement

    Note:

    Kansas City will not accept other types of statute issues, such as issues with the Assessment Statute Expiration Date (ASED), Refund Statute Expiration Date (RSED) or the Erroneous Refund Statute Expiration Date (ERSED).

  3. The Collection Statute Expiration Date (CSED) is the time period established by law to allow the IRS to collect taxes. The CSED is normally ten years from the date the tax is assessed, as provided by IRC 6502. Once this ten-year period has ended, the Government can no longer initiate collection action, unless the CSED is extended by case action, event or agreement.

    Note:

    In some instances the Service can continue collection action by serving a levy or filing suit prior to the expiration of this ten year period. See IRM 5.19.10.4.8, TC 971 AC 687, and Miscellaneous Codes for CSED, IRM 5.11.5.3, Continuous Effect of Levy on Salary and Wages and IRM 5.11.6.1, Retirement Income.


  4. Prior to November 5, 1990, the CSED was six years. Any CSED still open on November 5, 1990 was extended to ten years.

  5. If addressing a taxpayer issue, provide an explanation of how the Collection Statute Expiration Date was computed by sending the appropriate letter.

  6. There may be instances in Balance Due casework where the CSED will be in question. These instances could be identified through taxpayer correspondence/claim, telephone contact, internal account review and/or receipt of an Operations Assistance Request (OAR).

  7. There are many events that can have an effect on the CSED. Certain events suspend or extend the ten-year period for collection.

  8. See IRM 25.6.1.12, Collection Statute Expiration Date (CSED) and IRM 5.1.19, Collection Statute Expiration.

5.19.10.4.1  (10-15-2012)
Transaction Codes that Create a Collection Statute Expiration Date

  1. In addition to Transaction Code (TC) 150, Tax Assessed, there are other TC codes (with specific reference numbers) that carry their own ten year CSED. See IRM 5.1.19.2.1, Transaction Codes that Carry Their Own CSED, for a complete list.

  2. Each TC will show it's corresponding CSED to the right on CC IMFOLT/BMFOLT.

  3. There are no limits to the number of CSEDs that can appear on an account. The account will reflect the earliest CSED until that date has passed.

  4. CC TXMOD reflects the CSED that is next due to expire. CC IMFOLT indicates the FIRST CSED, NEXT CSED and LAST CSED. If there are more than three CSEDs present on the module, the NEXT CSED field shows the second CSED. When the second CSED expires, the NEXT CSED field updates with the third CSED, until all CSEDs are expired. For CC BMFOLT, the fields are LATEST CSED DATE, EARLIEST CSED DATE and IMMINENT CSED DATE.

  5. If the CSEDs are currently suspended by bankruptcy, Offer-In-Compromise or other, all CSED fields will show blank.

  6. When all CSEDs on the module are expired, a TC 608 generates to zero out the balance due. Until all CSEDs are expired, the balance due may consist of amounts associated with expired and unexpired CSEDs, unless expired balances were previously written off with TC 534.

5.19.10.4.2  (10-15-2012)
Transaction Codes and Case Actions that Suspend or Extend the Collection Statute Expiration Date

  1. There are also additional TCs that suspend or extend the CSED. See IRM 5.1.19.2.2, Integrated Data Retrieval System (IDRS) Transaction Codes (TC) That Suspend Or Extend A CSED.

  2. Refer to the following for a discussion of specific actions that, when taken on an account, may suspend or extend the CSED:

    IRM Reference Type of Action
    IRM 5.1.19.3, Case Actions That Can Suspend And/Or Extend A CSED

    Note:

    Additional information may be found in IRM 25.6.1.12.2.1, Conditions Postponing Collection or Suspending the 10 Year Collection Period, on some of the actions listed to the right.

    • Bankruptcy

    • Civil Penalty with Appeal Rights

    • Collection Due Process (CDP) Appeal

    • Combat Zone or Contingency Operation

    • Enforcement of the Two-Tier Tax Scheme

    • Estate Tax Lien

    • Installment Agreements with Form 900 Waiver

    • Judgment/Litigation

    • Military Deferral

    • Offer in Compromise

    • Relief From Joint And Several Liability On Joint Returns/Innocent Spouse

    • Taxpayer Assistance Order

    • Taxpayer Living Outside the U.S.

    • Wrongful Levy (Seizure)

    • Wrongful Lien

    In addition, see IRM 25.6.1.12.2.1, Conditions Postponing Collection or Suspending the 10 Year Collection Period.
    • Disaster Areas or Terroristic Action Postponement

    • Pending and Rejected Installment Agreements.

    • Summons Enforcement

    • Third-party summons

  3. See Exhibit 5.19.10-5, CSEDate Computation Reference Table, for a list of IRM references regarding each type of suspension/extension.

  4. A TC 550 is manually input to update or correct the CSED. The definer code will show the source/reason for the extension. See IRM 5.1.19.2.3, TC 550 Waiver Extension Definer Codes.

5.19.10.4.3  (10-15-2012)
Determining the Correct Collection Statute Expiration Date

  1. There may be various situations where the CSED comes into question.

  2. Discuss CSED related issues with other functional areas as necessary. If the case is being routed and the case is taxpayer initiated, send Letter 86C, Referring Taxpayer Inquiry/Forms to Another Office.

  3. Use Form 3210 to route accounts with CSED issues in Status 22, 26, 71 and 72 to the proper function using SERP Who/Where.

  4. For CSED issues on Estate Tax Liens (Form 706), contact the Advisory Estate Tax Group for assistance. Contact information can be found on the MySB/SE Website under "Estate Tax Liens - Collection: AI Advisory" .

  5. If an issue with the CSED date is identified, it must be reviewed and verified. If the manual CSED computation is within ≡ ≡ ≡ calendar days of the posted CSED, accept the posted CSED as correct.

  6. Calculate the correct CSED date using the guidelines outlined in this IRM and other IRMs. For assistance with CSED calculations, see:

    • Exhibit 5.19.10-5, CSED Computation Reference Table

    • Exhibit 5.19.10-6, Manual Calculations of a CSED Using the Julian Date Calendar

    • Exhibit 5.19.10-7, Manual Calculations of a CSED Using the Julian Date Calendar

    • Exhibit 5.19.10-8, CSED Calculator Worksheet

    • Exhibit 5.19.10-9, Example CSED Computation

  7. See Exhibit 3.11.10–4, Julian Date Calendar, Perpetual and Leap Year, to obtain Julian dates for your CSED computation.

  8. Accept TC 520/521, TC 480/780 and other applicable transaction code dates as correct.

  9. When the recalculated CSED date has expired and there are payments present dated after all CSEDs have expired, follow IRM 5.19.10.5.2, PMTEXPCSED Transcripts, for proper handling of the payments.

  10. If a determination is made that the CSED should be corrected,

    1. Refer the account to the Headquarters (HQ) analyst for approval. This applies to WI only HQ analyst has 5 business days to review.

    2. If correction is approved by the HQ analyst input TC 550 per IRM 5.19.10.4.5, Correcting an Existing Collection Statute Expiration Date, No TC 550 on Account or IRM 5.19.10.4.6, Correcting an Existing TC 550

    3. Control the module in "A" status and monitor until the CSED updates on CC IMFOLT/BMFOLT.

    4. Then follow with input of a TC 534, credit transfer, or other required case actions.

  11. Proceeds from levys served, or liens filed, prior to the CSED may still be applied to the expired balance. When payments are applied, Master File reverses the posted TC 608 with TC 609 in order to credit the payment and then generates another TC 608.

    Example:

    TC 608 1,232.47–  
    TC 670 150.00– DPC 05
    TC 609 1,232.47  
    TC 608 1,082.47–  

  12. When the taxpayer has questions regarding the CSED, provide an explanation of how the CSED was determined. Use Letter 672C, Payment(s) Located and/or Applied, or other appropriate letter to respond.

5.19.10.4.4  (10-15-2012)
Collection Statute Expiration Date Considerations

  1. The following information discusses certain conditions that should be kept in mind when working with CSEDs.

  2. If the CSED is incorrect on a module and a condition below applies, notify the Headquarters analyst of the social security number and tax period via Secure e-mail.

  3. MFT 31 is an IMF master file tax (MFT) account code and used for assessments against an individual taxpayer on a joint module. For additional guidance, see IRM 21.6.8.3, What is MFT 31.

  4. For some MFT 31 accounts created prior to January 1, 2005, interest from the MFT 30 module was assessed on the MFT 31 module using TC 340 doc code 51 in the 4th and 5th position of the DLN. This caused a new 10 year CSED based on the TC 340 date instead of the date of the associated tax assessment.

  5. When addressing a balance due on MFT 31 modules for tax periods ending December 31, 2004 and prior, analyze the module using CC IMFOLT to determine if there are TC 340s present with doc code 51.

    1. If present, compute the module CSED excluding the TC 340 doc code 51 dates.

    2. Verify the results with the CSED dates on page one of CC IMFOLT.

    3. If the CSED dates on CC IMFOLT are incorrect, input TC 550 to correct them.

  6. Offer-in-Compromise: If there appears to be a problem with the CSED and the module had a pending/accepted Offer dated after the correct CSED expired, contact the Offer-in- Compromise Centralized Service Center (COIC) per SERP Who/Where.

  7. Failure to File penalty: On some modules where a TC 166 posted with its own ten year CSED (the penalty posted alone and not in conjunction with a tax assessment), analyze the module to make sure the TC 166 was not assessed by the computer in error. Some stand alone TC 166s may be erroneous due to a processing error.

  8. TC 550: Verify the CSED on modules where the CSED was extended or corrected with a TC 550 and transaction codes follow that suspend the CSED further (TC 520, TC 480, etc.). In some cases. the system may not be computing the CSED correctly.

5.19.10.4.5  (10-15-2012)
Correcting an Existing Collection Statute Expiration Date, No TC 550 on Account

  1. When it is determined the current CSED on the tax module needs to be corrected, a TC 550 must be input. Use TC 550 DEFINER-CD "10" .

  2. For complete instructions for using CC FRM77 refer to IRM 2.4.19-5, Command Code FRM77 Input.

  3. Use CC REQ77 to input the TC 550 using the following fields:

    1. Transaction Code – always use TC 550.

    2. Extension date - recomputed CSED date.

    3. Transaction date – leave blank unless the current CSED date has expired. If it has passed, input date must be prior to the expired CSED date.

    4. DLN Code – leave blank.

    5. CSED Code – use appropriate code (P, B, or S).

    6. TC 550 Definer Code – use definer code 10, unless directed otherwise. Refer to IRM 5.1.19.2.3, TC 550 Waiver Extension Definer Codes.

    7. Remarks – must detail why CSED is being corrected.

5.19.10.4.6  (10-15-2012)
Correcting an Existing TC 550

  1. When it has been determined that the current TC 550 on the tax module is incorrect, an additional TC 550 must be input. Use TC 550 DEFINER-CD "10" unless otherwise directed.

  2. For complete instructions for using CC FRM77 refer to IRM 2.4.19-5, Command Code FRM77 Input.

  3. Use CC REQ77/FRM77 to correct the TC 550. Input the following fields:

    1. Transaction Code – always use TC 550.

    2. Extension date - recomputed CSED date.

    3. Transaction date – leave blank unless the current CSED date has expired. If it has passed, input date must be prior to the expired CSED date.

    4. DLN Code – always use 99.

    5. CSED Code – use appropriate code (P, B, or S).

    6. TC 550 Definer Code – use definer code 10 unless directed otherwise. Refer to IRM 5.19.10.4.2I, Transaction Codes and Case Actions that Suspend or Extend the Collection Statute Expiration Date

    7. Remarks – must detail why CSED is being corrected.

5.19.10.4.7  (10-15-2012)
Writing Off Expired Balances with TC 534

  1. Currently, Kansas City CSCO works lists of accounts where the earliest CSED is expired and a portion of the balance must be written off. Beginning in January 2013 a new MULTICSED transcript will issue in lieu of a listing. See IRM 5.19.10.4.7.1, MULTICSED Transcript and Listings.

  2. Write offs that exceed ≡ ≡ ≡ ≡ ≡ ≡ must be approved by the Headquarters analyst. Forward the SSN and tax period by e-mail using Secure Messaging. List the proposed TC 534 write off amount and the total amount of interest and FTP penalty included in the total.

  3. When a tax module has multiple CSEDs and the earliest is expired, input a TC 534 to write off any assessed balance associated with the expired statute. If no assessed balance remains from the expired CSED (accruals only), input a TC 534 with a zero amount.

  4. If any posted FTP or interest accruals contain amounts for both expired and unexpired assessments, the amounts attributable to the expired assessment must be included in the TC 534 amount. This applies only to MULTICSED transcripts or listings.

  5. If working CSED or SPC3 CSED Transcripts, follow IRM 5.19.10.5.5.1, Processing CSED Transcripts, for TC 534 procedures.

5.19.10.4.7.1  (10-15-2012)
MULTICSED Transcript and Listings

  1. Accounts are selected for the MULTICSED transcript or listing by the following criteria:

    • Tax module balance, with accruals, is over ≡ ≡ ≡ ≡ ≡ for IMF accounts.

    • More than one Collection Statute Expiration Date present and the earliest open CSED expired in the current cycle.

    • A transcript will not issue if the CSEDs are suspended by a TC 520, TC 480 or other.

    • A transcript will not issue if the next CSED to expire is within 90 days of the CSED that just expired.

      Example:

      The MFT 30 200212 tax module has three CSEDs, dated May 21, 2013, July 27, 2013 and March 31, 2020. No transcript will issue for the May 21, 2013 date because the next CSED, July 27, 2013, will expire in 67 days.

    • If the CSED that expires is for a TC 150 that was settled at posting (Status 12) a transcript will not issue.

    • A transcript will not issue for the last CSED on the module. TC 608 will generate to zero out the remaining balance.

  2. Follow procedures below and input AMS history for the action taken:

    If... Then...
    The assessment associated with the expired CSED full paid prior to the next assessment (Status 12 followed by Status 21) Input TC 534 .00 via CC REQ54. Use:
    • Blocking Series 19

    • Source Code 0

    • Reason Code 099

    • Hold Code 3

    The assessment associated with the expired CSED was NOT full paid prior to the next assessment
    1. Verify the accuracy of the CSEDs present on the module and make a correction, if needed, per instructions in IRM 5.19.10.4, Collection Statute Expiration Date (CSED).

    2. When verifying the CSED pay particular attention to those modules that meet the criteria identified in IRM 5.19.10.4.4, Collection Statute Expiration Date Considerations.

    3. Compute the amount to be written off with TC 534. If any posted FTP or interest contain amounts for both expired and unexpired assessments, the amounts attributable to the expired assessment must be included in the TC 534 amount. Use CC INTSTD or the Automated Computation Tool (ACT/DMI). This applies only to MULTICSED transcripts or listings.

    4. Associate any TC 360, Fees and Collection Costs or TC 280, Bad Check Penalty, with the tax assessment that it immediately follows.

    5. Input TC 534 to write off the expired portion of the module balance. Do not create a credit balance on the module.

5.19.10.4.8  (10-15-2012)
TC 971 AC 687, and Miscellaneous Codes for CSED

  1. The TC 971 AC 687 with 20 miscellaneous codes was established for CSED purposes effective January 2007. When inputting a TC 971 AC 687, a miscellaneous code must be input at the same time. The miscellaneous code serves as an audit trail, defines what type of levy was served, and identifies other various actions taken on the account.

  2. The following chart will provide an explanation for each miscellaneous code. SBSE should identify the "fixed and determined" from this point forward. Any module that does not have a code will be verified through the revenue officer or case processing.

    Note:

    "Fixed and determined" levy sources are instruments, such as pensions, royalties etc., that are payable for a fixed amount on a date in the future that can be determined in advance. For instance, Social Security benefits begin at age 62, and Civil Service pensions at age 55 and the approximate amount to be paid is known.

    Miscellaneous Codes Definitions
    001 Pre CSED levy identified as "fixed and determined" e.g. pension, royalties etc. excludes levy on working taxpayer's salaries.
    002 Identifies the module as a continuous wage levy on wages/salaries secured before CSED.

    Exception:

    To identify the legal basis for releasing levies see:

    • IRM 5.11.2.2.1, Legal Basis for Releasing Levies

    • IRM 5.19.4.4.10, Levy Release: General Information

    • IRM 5.19.10.10.6.1, IAAL Review of Continuous Wage Levy CSCO Processing

    003 Suit was filed before CSED expired.
    004 Field Manager completed pre CSED review of module. Allow this module CSED to expire in its current status.
    005 Unable to locate taxpayer.
    006 Module is not a levy module, payments coded incorrectly.
    007 Taxpayer's CSED rights communicated via phone/letter. Module has refundable credits and no outstanding liabilities. Levy release sent.
    008 Taxpayer's CSED rights communicated via letter only. Module has refundable credits and the account has outstanding liabilities. Levy release sent.
    009 Identifies an ≡ ≡ ≡ ≡ module (1). Only post ≡ ≡ ≡ ≡ ≡ payments to this module. Do not release the levy. Do not offset. Any excess credits will be refunded. Cases will be centralized in Anchorage.
    010 Levy release previously sent, second contact with the taxpayer initiated via correspondence/phone.
    011 Based on Restructuring and Reform Act of 1998 (RRA98), CSED computed incorrectly, due to failure on account for suspension under IRC 6331(k)(1) and (3)
    012 CSED review completed, move module to the Retention File.
    013 Communicated CSED rights via telephone. If account has outstanding liabilities - follow up with a letter.
    014 Credit(s) Refund Statute Expired, no outstanding liabilities.
    015 Reserved for CSED Processing.
    016 Reserved for CSED Processing.
    017 Reserved for CSED Processing.
    018 Reserved for CSED Processing.
    019 Reserved for CSED Processing.
    020 Reserved for CSED Processing.

5.19.10.5  (09-15-2010)
Balance Due Transcripts

  1. Balance Due Transcripts are generated in the campuses to signal an alert to certain situations that have been present for some time on an account and cause the account to remain unresolved. WI CSCO works IMF accounts and SB/SE works BMF accounts. This category of transcripts includes:

    • Collection Statute Expiration Date (CSED)

    • Payment Expired Collection Statute Expiration Date (PMTEXPCSED)

    • Accounts Maintenance Claim Pending (06W)

    • Accounts Maintenance (AM07)

    • Claim Pending Collection Statute (AM23W)

    • Credit Offset (CP 44 and CP 188)

    • Notice of Potential Manual Penalty/Interest Adjustment (CP 86 and CP 186)

    • Notice of No Merge TDA Module and NOMRG TDA Transcript (CP 206)

    For a complete listing of all the transcripts, refer to IRM 3.13.62, Media Transport and Control.

  2. ASED (Assessment Statute Expiration Date) is usually three years from the later of the unextended due date or the filing date of the return. The AM-X transcript will generate if the account is open in Collection and it doesn't consider any posted transactions.

  3. STAT, statute expiration is imminent (within 6 months). There are four types of STAT cases.

    • Category 23W, the only check here is for CSED. See IRM 5.19.10.5.6, Claim Pending Collection Statute Transcript (AM 23W).

    • Dummy Cases, which include other AM and TDI issues. It also includes civil penalty modules.

    • RSED, Refund Statute Expiration Date. This transcript is sent regardless of other posting or conditions.

    • Normal STAT, one of the freeze conditions (other than 03E, 12Y, 18H, 26H and 23W) is met. There are two types of issuances, First - Alert and Follow - up. The ASED is within 6 months of expiring. Once a normal STAT is issued, an AM case will not generate.

    Caution:

    If any module contains a posted TC 608, the module's last CSED has expired. Due to programming the TIN will generate on the Restricted Interest category on the IAAL. Headquarters will perform a special Generalized IDRS Interface (GII), run to systemically close them prior to being assigned to the CSCO operation.

5.19.10.5.1  (10-15-2012)
General Procedures For All Transcripts

  1. The following transcripts are considered a Priority Transcript:

    • CSED

    • PMTEXPCSED

    • CP 44

    • NMFL

    • AM07W

    • Any transcript with a "credit balance/TC 608"

  2. If an AMRH transcript or other transcript type, from Accounts Maintenance or the Statute function, is controlled to CSCO due to a levy payment on the module, reassign the transcript back to the originator. As of July 26, 2011, it is no longer necessary to refer these to CSCO to resolve the levy payment.

  3. Any transcript module that has a TC 520 (—V. —W or —VW) will not be routed.

  4. If there is a TC 470 on the module, follow IRM 5.19.10.5.3, Accounts Maintenance Claim Pending (AM06W) Transcripts, to input a TC 472. Close the control with a history item relating to the action.

  5. Research IDRS for any available credit(s). Your search should include CC URINQ, XSINQ, and UPTIN. Document AMS with a history item XXXXXRSHRD (Xs identifies the type of transcript).

    If... Then...
    Credits are statute barred Follow below to transfer the credit to the Unidentified Remittance File (URF) or the Excess Collection File (XSF)
    Credits are located Transfer them to the balance due (including accruals)
    If there is an expired CSED module, and the TC 608 is significant The payment:
    • Can be applied if research of the RTR system or payment source document indicates that the taxpayer designated that payment for the expired module and that payment was misapplied

    • Can be applied if payment was proceeds from levy on a "fixed and determinable" levy source served prior to the CSED. See IRM 5.19.10.5.2(3), PMTEXPCSED Transcripts.

    • If neither of the above apply, the payment CANNOT be applied to the expired CSED module regardless of the payment date or posting cycle date.

    • Use the proper bypass code to avoid generating an unpostable.

    If an expired CSED module has a credit that created a credit balance Treat as an overpayment of tax and follow IRM 5.19.10.5.2. PMTEXPCSED Transcripts.
    The transfer(s) full pay the module Document AMS and close the control
    Any amount of balance remains Follow specific transcript procedures

  6. To transfer credit(s) to the URF or XSF, follow the procedures below.

    1. If the credit is being transferred from an expired CSED module, there must be a new TC 609 and a new TC 608 that has posted after the credit or the transfer will unpost. If not present, it will be necessary to transfer the credit(s) to a satisfied module with a TC 570 or create a dummy module.

    2. If the payment is less than a year old, use Form 2424, Account Adjustment Voucher to transfer to URF. Follow IRM 3.17.10.3.2, Receiving Unidentified Remittance Cases. In the Explanation box on the form be very specific regarding the reason for transfer.

      Example:

      "No reply to TC 672C to claim refund of overpayment after CSED"

    3. For payments more than a year old, use Form 8758, Excess Collection File Addition. Follow IRM 3.17.220.2.1.1, Preparation of Form 8758. In the Explanation box on the form be very specific regarding the reason for transfer.

      Example:

      "No reply to TC 672C to claim refund of overpayment after CSED"


      In Box 4 enter "IDEN" .

    4. Attach the IDRS prints to the Form 2424, Account Adjustment Voucher, or Form 8758, Excess Collection File Addition. Input an AMS history item to indicate the actions taken (non-refundable credits, good refund, refund statute in jeopardy, etc. Credit to URF or XSF via From 2424 or 8758).

  7. To request a transfer from Excess Collection File, follow the procedures below.

    1. Prepare Form 8765, IDRS Control File Credit Application, refer toIRM 3.17.220 Exhibit 9 (3.17.220-9), CC XSINQ.

    2. Forward all Forms 8765 requiring statute clearance to the Statute function for review prior to forwarding to Excess Collection. For additional information, refer to IRM 3.17.220.2.11(5), Applying Amounts From the XSF—General

    3. Attach documentation to the request identifying the credit and indicating its proper application.

  8. To request a manual refund, use Form 5792, Request for IDRS Generated Refund (IGR). The Erroneous Manual Refund Tool (EMT) is an IAT tool that may be used to process and monitor manual refunds. You are strongly encouraged to utilize this tool when you are issuing a manual refund as it increases accuracy and saves time. Use of this tool is currently NOT mandatory.

    1. When initiating a manual refund, employees should follow procedures found in IRM 21.4.4, Manual Refunds. Approval must be obtained by a designated Certifying Officer.

    2. Inform taxpayers that they are still subject to offset by FMS through the TOP for past due child support or Federal agency debts owed. Refer to IRM 21.4.6, Refund Offset

  9. If account is full paid and levy payments are still being applied, see IRM 5.19.10.5.2.1, General Instructions for PMTEXPCSED Cases. Complete Form 668D, Release of Levy/Release of Property from Levy, if needed to stop the levy.

  10. If balance due notice or TDA processing is suspended for more than six months due to an IRS error, adjust any penalty and interest per procedures in IRM 20.1.2, Failure to File/Failure to Pay Penalties and IRM 20.2, Interest.

  11. If there is a TC 582 Federal Tax Lien on the module, verify the CSED. If the CSED is within 180 days of expiring, resolve any retention or freeze code. When the CSED expires, the lien is self-releasing.

    Note:

    IRC 6325 states that IRS shall issue a certificate of release no later than 30 days after the day on which the liability is satisfied or becomes unenforceable.

  12. Count each transcript received for each different MFT/TXPD, except where noted.

5.19.10.5.2  (10-15-2012)
PMTEXPCSED Transcripts

  1. A Payment Expired CSED (PMTEXPCSED) Transcript generates once for each TC 610, TC 640 or TC 670, without DPC 05, 06, or 14, that is applied to a module after the CSED has expired.

  2. The purpose of the transcript is to determine proper disposition of the payment, which may include one or more of the following:

    • Contact the taxpayer and advise them of their options under IRC 6511, Limitations on Credit or Refund. The taxpayer must advise the IRS of whether they want the payment refunded or applied to another tax module.

    • Transfer statute barred payments to Excess Collection.

    • Move a misapplied payment to the correct tax module.

    • Determine that a payment can remain on the expired CSED module.

    • Release continuous wage levies or other levy types.

  3. See IRM 5.19.10.5.1, General Procedures for All Transcripts, for more information regarding the Unidentified Remittance File (URF), Excess Collections File (XSF) and manual refunds.

  4. In some instances the Service can continue collection action by serving a levy or filing suit prior to the expiration of the ten year period. See IRM 5.19.10.4.8, TC 971 AC 687, and Miscellaneous Codes for CSED, IRM 5.11.5.3, Continuous Effect of Levy on Salary and Wages and IRM 5.11.6.1, Retirement Income.

  5. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.2.1  (10-15-2012)
General Instructions for PMTEXPCSED Cases

  1. Control the expired CSED module using "A" (active) status.

    1. The examiner monitoring the account will be responsible for each credit that posts to the module until the control is closed. Notate AMS with amount/cycle of each additional payment and close the new control(s). Analyze all credits that have a posted date after the expired CSED.

    2. All related transcripts will be routed to the examiner who is monitoring the account. That examiner will take the count for each transcript resolved.

    3. When another operation such as insolvency, TFRP, OIC or a revenue officer must resolve the credit, contact that area by phone and allow 21 days for their resolution. If unable to contact, allow five business days for call back. It will be necessary to re-assign the module to background "B" status when coordinating with the other area. If the credit is not resolved in 21 days or you are unable to contact, input detailed history on AMS and close your case. Forward the case with affected payments highlighted, to the appropriate function, requesting resolution or guidance for payments received after the CSED.

  2. If a manual or computer generated refund (TC 840/846) previously generated on an expired CSED module, and there are no additional liabilities, subsequent payments may be refunded. Send Letter 672C informing taxpayer that CSED has expired on the specific module and he/she is under no obligation to make future payments.

  3. A payment received after the CSED is treated as an overpayment of tax. After it is determined that the taxpayer must be contacted, send Letter 672C, Payment(s) Located and/or Applied. Inform the taxpayer of CSED rights and the time period under IRC 6511 within which to claim a refund.

  4. The IRC 6511 period runs two years from the payment received date and three years from the return due date, whichever is later.

  5. Most taxpayers will receive a maximum of two letters (refund and balance due) regarding his CSED rights for each module, unless a reply is received allowing the Service to apply the credit(s) to an expired CSED module. The applied credits will have a DPC "14" .

  6. If you become aware that the Letter 672C has not been sent and the time period under IRC 6511 might expire before the taxpayer has time to file a claim for refund, the Service should refund the payment without a claim. The amount of the refund may not exceed the amount that would be allowable under IRC 6511 if a claim had been filed on the date the refund is allowed. A refund or credit is allowed on the date on which the Secretary first authorizes the scheduling of an overpayment of the tax; i.e., when a certifying officer signs Form 2188, Voucher and Schedule of Overpayment and Overassessments. The IRC 6511 period runs two years from the date on which the Service received the post-CSED payment.

  7. Input the appropriate history item on AMS for the audit trail. Input history item(s) that reflect each action taken to advise the taxpayer of rights concerning the overpayment caused by taxpayer's payment of the tax after the expiration of IRC 6502 Collection After Assessment.

  8. If a payment with DPC 99 causes a transcript to generate, review the module for a DPC 04, 05 or 07.

    1. If the only DPC is 05, research Remittance Transaction Research System (RTR) to determine if it is a true levy payment.

    2. If it is not a levy payment, but a personal check or money order from the taxpayer, skip to (12) below.

    3. If one of these DPCs 04, 05 or 07 appear in the module, consider all payments as levy or lien payments unless the module was in ST 53 preceding ST 12.

  9. Use the necessary research tools to identify the levy or lien source. If the source cannot be identified, obtain the source document from the Remittance Transaction Research System, RTR System.

  10. Process a levy payment(s) as follows:

    1. A continuous wage/salary levy served before the expiration of the Collection Statute should be released when the Collection Statute expires. Refer to IRM 5.19.10.10.6.1, IAAL Review of Continuous Wage Levy CSCO Processing, IRM 5.19.4.4.10, Levy Release: General Information and IRM 5.11.2.2.1, Legal Basis for Releasing Levies.

    2. Check the Status History Section of CC TXMOD to determine the next step for releasing the levy. If the prior statuses are 12, 60, 22 or 12 and 22, CSCO will release the continuous wage levy.

    3. If the prior statuses are 12, 60, 26 or 12 and 26, and the document states "pension, social security or royalty" , the levy should not be released. If the source document does not state this type of income, CSCO will contact the appropriate Collection Case Processing (CCP) function to determine the source of the levy or lien. CCP will be responsible for releasing any levy or lien that was filed by the field. Document contact with CCP on AMS

    4. If TC 971 AC 687 has miscellaneous code of 009 on the module, document AMS and close the case. Do not automatically release the levy.

      Caution:

      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    5. CSCO will work the module if the statuses are 12 followed by 53.

    6. See IRM 5.19.10.5.2.5, Processing Refundable Credits, for more information on levy payments.

  11. If the taxpayer has an installment agreement, and the payment(s) posts to an expired CSED module:

    1. Transfer the credit to the next tax period having the earliest CSED.

    2. Send Letter 672C informing the taxpayer of the expired CSED for the specific tax year.

    3. Advise him to use the current account information for all future payments.

  12. If taxpayer does not have an installment agreement and there are other balance due modules, the payment that posted to the expired CSED module CANNOT be transferred to another balance due module unless it meets the exception in (12) or it was a misapplied payment. It must be treated as an overpayment of tax and Letter 672C sent per (14)

  13. If taxpayer is eligible for a refund of the payment(s) and it is not barred by statute:

    1. Send Letter 672C informing taxpayer of expired CSED and credit availability.

    2. Advise the taxpayer of the time frame for claiming the refund under IRC 6511

    3. Assign the case on IDRS in "M" status and suspend the case for 45 days on AMS. Allow 30 days for a response.

  14. If a telephone number is available, make two attempts to contact the taxpayer by telephone.

    1. If contact is made, verify disclosure.

    2. Advise taxpayer of expired statute, and the time period under IRC section 6511 within which to claim a refund.

    3. Input history on AMS items that reflect conversation with taxpayer and all actions taken.

  15. If a reply was received allowing the Service to apply the credit(s) to an expired CSED module, when subsequent payments post to the same expired module and the analysis shows the same conditions exist, do not send another Letter 672C. Continue applying the credits to the CSED module until full paid.

  16. When applying the credit to the expired module, input TC 672 to reverse the credit and reinput TC 670 with DPC14.

  17. If the taxpayer replies with a request to apply the credit to another module, transfer the credit using CC ADD24.

  18. If taxpayer responds requesting a refund of the payment(s), issue the refund on Form 5792. Use CC COMPAD to compute credit interest on all payments over 45 days old. See IRM 21.4.4.4, Preparation of Manual Refund Forms . Input TC 290 to associate the 672C letter to the return. Forward 672C letter to files.

  19. Transfer the credit to the Unidentified Remittance File or Excess Collections, (see IRM 5.19.10.5.1) if:

    • No response is received from the taxpayer or

    • Letter is returned as undeliverable, and no new address is available

5.19.10.5.2.2  (10-15-2012)
Analyzing, Payment Types and Process Order

  1. Analyze the expired CSED module to determine:

    1. If any refunds were undeliverable. If so, it will be necessary to verify the taxpayer's address before corresponding or refunding again.

      Note:

      If a refund was issued based on a claim filed by the taxpayer, secure the source document to verify the address. If different, follow the normal procedures for updating the taxpayer's account. Document your research. See IRM 5.19.10.5.6, Claim Pending Collection Statute Transcript (AM 23W).

    2. If there are any non-refundable credits (more than two years old from transcript date).

    3. If all TC 6XX - 8XX credits are refundable (payment/credit date is two years or less from the transcript date).

    4. If any refundable credits have a transaction code other than "670" , research Document 6209 for definition. Identify the source of these credits by utilizing the source document or the history section for employee contact information. Contact the source for disposition of the payment.

    5. Outstanding Balances, OBs, for the account.

  2. Processing of payments will be done in the following order:

    1. Processing Statute-Barred Credits, see IRM 5.19.10.5.2.3

    2. Processing Transaction Codes and Payments Other Than TC 670, see IRM 5.19.10.5.2.4

    3. Processing Refundable Credits, see IRM 5.19.10.5.2.5

5.19.10.5.2.3  (10-15-2012)
Processing Statute-Barred Credits

  1. Other than the exception discussed below in (2), a statute-barred credit may not be applied to offset the debit modules on an account.

  2. If the statute-barred credit relates to the same taxpayer, the same tax type and the same tax period as the debit module, the statute-barred credit may be used to offset the debit module.

    Example:

    The payment was applied to a Form 1040 MFT 30 2000 tax year. It can be transferred to a Form 1040 MFT 31 2000 tax year or a Form 1040 NMF 2000 tax year for the same taxpayer, even if it's barred.


    Example:

    Payment was misapplied.

  3. If the barred credit cannot be applied, transfer it to the Excess Collection File.

  4. To the extent that modules can be identified where a statute barred credit was applied in error, those credits are considered void and should therefore be reversed.

5.19.10.5.2.4  (10-15-2012)
Processing Transaction Codes and Payments Other Than TC 670

  1. These transaction codes may generate a freeze condition, an assessment, an offset or other types of payments. This If/Then Chart provides procedures for processing transaction codes and payments other than TC 670.

    Figure 5.19.10-1

    If... Then...
    TC 91X
    1. Contact Criminal Investigation. Explain the CSED issue (IRC 6502) and the payment date. Ask for advice before taking any action on the case.

    2. Document your conversation.

    TC 694
    • For payment of sale and/or administrative cost. Refer to IRM 5.1.2.5.1(2)k, Transaction Codes. This is a good payment with any date. Do not refund.

    • Normally, a TC 360 will already be in the module. However, both TC 694 and TC 360 can be input simultaneously.

    • If there is any excess after these costs, it will be posted as a TC 670 with a DPC code indicating the type of sale or administrative cost, such as cost of the levy or suit. Refer to Document 6209, Chapter 11 for a list of DPCs. This TC 670 is refundable.

    TC 706 and no outstanding liabilities The computer will occasionally offset to an expired CSED module if it is the oldest module and it was written off with an amount. Starting with processing year 2005, a transcript should generate to properly resolve the payment issue.
    1. If there are no other unexpired CSED balance due modules, consider this credit as refundable.

    2. Transfer the credit back to the module it originated from to generate a refund.

    TC 706 with other outstanding liabilities
    1. Transfer credit to the oldest unexpired CSED module with outstanding liability.

    2. Notify the taxpayer of the transfer.

    Other TCs
    1. Research Document 6209, IRS Processing Codes and Information, for description of code.

    2. Obtain source document or check the history section and contact the employee. Explain the CSED issue (IRC 6502), the payment date, and ask for advice on the disposition of the payment.

    TC 640 Advance Payment (this is an expired CSED module) A TC 608 generates if there is a balance due based on the last assessment in the module. The normal assessment statute period is three years from the later of the unextended due date or the filing date of the return. The exception is a fraudulent return. There is no statute of limitation for assessing the fraud penalties.
    1. Obtain the source document or check the history section to determine the source of the payment.

    2. Contact Case Processing and explain the CSED issue (IRC 6502) and the payment date. Ask for advice before taking any action on the case. See IRM 5.19.10.5.2.1(3)(b), General Instructions for PMTEXPCSED Cases, for additional information.

      Note:

      This is a refundable credit. If Case Processing or an RO states that a return will be secured for the TDI module, move the credit(s). Both modules should be documented. This action is within the tax law. If the RSED is in jeopardy, advise the contact person accordingly.

5.19.10.5.2.5  (10-15-2012)
Processing Refundable Credits

  1. The If/Then Chart below provides instructions on how to process refundable credit(s).

    Figure 5.19.10-2

    If... Then...
    A liability has posted since the refund generated.
    1. Always obtain a copy of the check from the RTR System. After information is obtained, check Status Section. If the last statuses are 12, 22, or 12, 60, 22, CSCO will stop the levy. Prepare Form 668D, Release of Levy/Release of Property from Levy, to terminate the levy.

    2. If the statuses are 12, 26, or 12, 60, 26 and the source documents states, "pension, social security or royalty" , input the appropriate history item. If the source document doesn't contain "pension, social security or royalty," contact the appropriate Case Processing operation to determine the levy/lien source. If the levy source is a continuous wage levy or lien (not in litigation), they are responsible for stopping the levy or lien. CSCO will send Letter 672C. Input the appropriate history codes, and resolve the payment(s) issue. Contact should be documented.

    3. If the source document is unavailable, you may need to contact the taxpayer for the levy source prior to sending this letter.

    4. Send Letter 672C and ask the taxpayers if they want the credit applied to the expired CSED module or to the new liability. Do not place in suspense unless all source information is obtained.

      Note:

      Do not close your control unless all issues have been resolved.

    No outstanding liabilities.
    1. If the source is a continuous wage levy or lien and there is only one credit, send Letter 672C. Ask the taxpayers to indicate if they want the credit refunded or applied to the expired CSED module.

    2. If there is more than one credit, send Letter 672C.

      Reminder:

      Disregard any assessment after the expired CSED. You will refund the whole payment(s), and move refund statute barred credits to Excess Collection.

    Note:

    SB/SE CSCO works BMF and WI CSCO works IMF.

5.19.10.5.2.6  (10-15-2012)
Processing Responses/No Response to Letter 672C

  1. The following If/And/Then Chart provides procedures for processing refund responses and no responses.

    Figure 5.19.10-3

    If... And... Then...
    The taxpayer can apply the credit to the expired CSED module, another liability or have it refunded. Taxpayer requested that the payment be applied to the module with the expired CSED. Input TC 672/670 using ADD24. Input DPC 14 on the new TC 670.
    Taxpayer requested that the payment be applied to another liability Transfer the credit using CC ADD24 and appropriate DPC code.
    Taxpayer requested a refund. Prepare the necessary forms. Interest should be added if the refund is more than 45 days old. Follow IRM 21.4.4, Manual Refunds
    Taxpayer does not respond. Prepare the necessary forms to move the credits to Unidentified Remittance File or Excess Collection File. For additional information on TC 608/609, see IRM 5.19.10.5.1(6), General Procedures for All Transcripts .
         
    The taxpayer can apply the credit to the expired CSED module, another liability or have it refunded. Letter is undeliverable
    1. Research for a new address. Use IMFOLE or BMFOLE to see the last return filed.

    2. If a return was filed, check RTVUE or IRPTRL for a different address.

    3. If a new address is located, reissue the letter.

    4. If the taxpayer replies, prior to issuing a manual refund make sure the address has updated on Master File.

    5. If the new address has not been updated to master file, follow normal procedures for updating.

    6. If unable to obtain a new address, prepare the necessary forms to move the credits to Unidentified Remittance File or Excess Collection File. Notate the form "Good Refund" when a new address is verified. Input TC 971 AC 687 005 (miscellaneous code).

    7. Input the appropriate history items.

    Reminder:

    If there is an expired module and the TC 608 amount was significant (amount other than zero), and the date of the payment is prior to that particular module's CSED date, apply the payment.

  2. The Service has an obligation to notify the taxpayer of his rights and satisfy all outstanding liabilities prior to refunding. Review the module, and account and process as follows:

    1. Verify the credits that posted with a date after the expired CSED are applicable based on tax law for the module.

    2. Verify the history items to make sure that they are adequate for audit trail and that the module is suitable to move to the retention file.

    3. Close your control.

5.19.10.5.3  (10-15-2012)
Accounts Maintenance Claim Pending (AM06W) Transcripts

  1. The 06W transcript will generate after twenty-two (22) cycles, when there is an unresolved TC 470 with no Closing Code (cc), a cc 90, cc 93 or cc 95 on IDRS. A -W freeze appears on the transcript and the tax module on IDRS. The issuance of the transcript is categorized as AMRH. If the first 06W transcript is not resolved, a follow-up transcript will issue in 15 cycles and can be identified by an "F" after the transcript type. Most of the 06W transcripts generated will not relate to Collection cases because other functions use the TC 470.

  2. If the Assessment Statute Expiration Date (ASED) has expired, an AM-X transcript will generate regardless of any posting in a module.

  3. If the return statute is imminent (within 180 days period), a STAT transcript will generate.

  4. All AM06 transcripts will be processed following procedures below. If the transcript cannot be resolved within 14 days from the computer notice date, input your control on IDRS.

  5. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.3.1  (10-15-2012)
Processing 06W Transcripts

  1. The following If/Then Chart provides procedures for resolving AM06W conditions. Research IDRS for the latest information, then continue below.

    Figure 5.19.10-4

    If... Then...
    If a prior action has resolved the TC 470 condition or the TXMOD status is 12. Document AMS with one of the following history items "NA or No Action." Verify that all related controls are closed.
    If an action will be taken on the account but has not yet occurred. Take no action. Also see (2) below. Update AMS and close transcript.
    If a pending transfer or adjustment will satisfy the balance due (including accruals) per cc INTST. Take no action. Update AMS and close transcript.
    If a pending transfer or adjustment will not satisfy the module and the account was in TDA status or notice status prior to the input of the TC 470.
    1. Input TC 472.

    2. Update AMS and close transcript.

    The module contains a TC 470 cc 95.
    1. Use AMS to generate a Form 4442, Inquiry Referral. Notate "Hold on Collection activity has expired. Please re-input or reverse TC 470"

    2. Route the form to the operation responsible for assessing the civil penalty.

    TC 470 input date is less than 5 months from the current date. Take no action. Update AMS and close transcript
    TC 470 input date is 5 months or more from the current date and the module has an open control base.

    Example:

    If the module is controlled to Erroneous Refund (ERRF), ASFR and Exam (may have RECN in the category).

    1. Input a TC 470.

    2. Update the other open control activity field with "TC470/EXPD" .

    TC 470 input date is 5 months or more from the current date and it's determined that the TC 470 is not necessary. Input TC 472.
    If the TC 470 cc 90 is present on a MFT 44 (Form 990–PF, Return of Private Foundation or Section 4947 (a) (1) Non exempt Charitable Trust Treated as a Private Foundation) module.
    1. Do Not reverse the TC 470.

    2. Input a TC 470 cc 90.

    If the TC 470 is present and the module contains a TC 971 AC 65 (Innocent Spouse). Input a TC 472.
    If there is a TC 971 AC 100 on the module.
    1. Do Not reverse the TC 470.

    2. Input another TC 470; use the same cc as the original. The account will become a MFT 31.

    If there is a TC 400 on the module, and the module balances are ".00" , the module has successfully moved to Non Master-File. Any transaction posting afterwards will go unpostable.
    1. Review the module to determine if the TC 400 posted after the generation of the transcript

    2. If the TC 400 posted after the transcript generated, use history item AM06TC400 and close the control.

    3. If the TC 400 posted before the transcript generated, all pertinent information should be routed to Headquarters for further review following campus discretion. Use history item AM06TH (transcript name, to Headquarters).

    If there is a TC 400 on the module and the module has a debit balance, (TC 370 and TC 402 posted which transfers the module back to Master File)
    1. Do Not reverse the TC 470

    2. Input a TC 470. Use the same cc as the original. The account is being transferred to Non Master-File.

  2. If TC 470 is not resolved and the module/account contains a freeze code, review the module to see if it is still necessary. Follow procedures in the If/Then Chart which provides procedures for modules containing a combination of a TC 470 and a freeze code.

    Figure 5.19.10-5

    If... Then...
    —Y Freeze Code.
    1. If the module is in ST 71, check the CSED field.

    2. If the CSED is all zeroes, input TC 472 and use AMS to generate a Form 4442, Inquiry Referral; notate CSED issue.

    3. Use the SERP Who/Where tab, select the Offer In Compromise Compliance Locations for Back-end to determine the appropriate OIC Site to route the Form 4442.

    4. Document history item, ROICCSED (Route Form 4442 to OIC CSED issue).

    5. If the module has a computed CSED, input TC 472.

    6. For all other statuses, input TC 470.

    —L Freeze Code.
    1. Reverse the TC 470.

    2. Update the other open control activity field with "TC470/EXPD"

    Unreversed TC 520 (—V, —W or —VW). See IRM 5.19.10.5.1, General Procedures For All Transcripts.

5.19.10.5.4  (09-15-2010)
Accounts Maintenance Transcripts (AM07)

  1. The AM07 transcript generates when there is a credit balance on an account that contains a TC 130 and TC 150 and the CP 44 Notice was not resolved in 16 cycles. A V— freeze appears on the transcript and the related module on IDRS. If the transcript is not resolved within 14 days from the computer notice date, a control base with category code AMRH is automatically established.

  2. The following will explain the three statute transcripts that will generate for the 07 if the module is open, regardless of any posting:

    1. If the Assessment Statute Expiration Date (ASED) has expired, an AM–X-07 transcript will generate.

    2. If the ASED will expire per the statute table or within six months, a statute transcript generates.

    3. The follow-up transcript will generate in 16 cycles.

  3. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.4.1  (09-15-2010)
Processing Accounts Maintenance Transcripts (AM07)

  1. If there is a TC 971 AC 065 on the module, refer to IRM 25.15.2.4.2, Innocent Spouse Indicator Transaction Code (TC) 971/972, for procedures to work the AM07 transcript.

  2. Research the history portion of IDRS for an open control base. If any cases are controlled to a CP 44 unit technician, close the control to the CP 44 technician to be associated with the case. Follow the If/And/Then Chart below which provides procedures for processing AM07 issues.

    Figure 5.19.10-6

    If... And... Then...
    Another function has a control base on the module, contact the technician with the open control base to determine if the credit balance on the module will be resolved by the technician’s action. If the technician’s action will resolve the credit balance. Document AMS and close the control.
    If the technician’s action will not resolve the credit balance. Process the transcript per IRM 5.19.1 , Balance Due.
    The transcript module has no open control base or an open unresolved CP 44 Notice. There is a credit balance on the module. Process the transcript per IRM 5.19.10.3, Credit Offsets.

  3. If there is no credit balance on the transcript, or if IDRS research shows no credit balance on the module, document AMS and close the control.

  4. If the transcript module has freeze conditions that prevent credit transfer or offset (e.g., R, K, etc.) on the transcript module, resolve those freezes as follows:

    1. If the freeze condition exists in the transcript module that another functional area is responsible for releasing, (e.g., —L, —V etc.), follow general procedures. The responsible area should resolve all issues.

    2. If there is an L— freeze on IMF (unreversed TC 971 AC 065), refer to IRM 25.15.2.4, Direct Receipt of Form 8857, for instructions on resolving this freeze. For BMF cases, refer to IRM 21.7.8, Excise Taxes, for Form 2290, Heavy Highway Vehicle Use Tax instructions. For credit transfer instructions, refer to IRM 21.5.8, Credit Transfers.

    3. Resolve all other freeze conditions by researching the taxpayer’s account. Refer to IRM 21.5.6, Freeze Codes, for instructions on resolving freezes.

5.19.10.5.5  (10-15-2012)
CSED Transcript

  1. A CSED Transcript generates when the earliest CSED is expired, the latest is not expired and there is no unreversed TC 534 or a TC 400 hold present. Each debit module has a total module balance of ≡ ≡ ≡ ≡ ≡ or more on the account. An A— freeze appears on the credit and debit module. It freezes the account for eight cycles or until a TC 534 is input, whichever is earlier. A CSED Transcript may generate even if the balance due is for accruals of penalty and interest only.

  2. Destroy any CSED transcripts that issue on Trust Fund Recovery Penalty (TFRP) modules. A separate transcript already generates to TFRP in the appropriate SB/SE CSCO site.

  3. There are several transaction codes or assessments that carry their own CSED. See IRM 25.6.1.12, Collection Statute Expiration Date (CSED), for a list.

  4. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.5.1  (10-15-2012)
Processing CSED Transcript

  1. Review CC IMFOLT/BMFOLT to identify the expired assessment that generated the transcript.

  2. Add any debit transactions associated with the expired assessment and minus out any credits (with a date prior to the CSED). This includes any withholding, tax credits, payments or refund offsets that were dated prior to that CSED.

  3. Any credits dated after the expired CSED will be credited towards the next assessment.

  4. If the expired assessment was full paid prior to the CSED, input TC 534 .00.

  5. If the expired assessment was not full paid prior to the CSED, process as follows:

    1. Review the credit causing the A— freeze. If it was available for offset prior to the expiration of the assessment, input a credit transfer using CC ADD34. Use the appropriate bypass code to avoid an unpostable.

    2. If there is still a balance remaining for the expired assessment, do not assess any additional P&I.

    3. Input a TC 534 for the remaining amount. If a credit transfer was done, use a posting delay code with the TC 534.

  6. When a module has more that one assessment, it is required to have a TC 534 input on the module with a zero or a significant amount. There should be only one TC 534 on the module to cover all expired CSEDs. It may be necessary to reverse a TC 534 with a TC 535 in order to include all expired CSED amounts.
    Use CC REQ54/ADJ54 to reverse a previous write off. Input the following fields:

    1. Blocking Series – 19

    2. INTCMP-DT - Enter the current date

    3. Transaction Code – TC 535

    4. Amount – Amount of previous TC 534 (do not use a minus sign)

    5. Source Code – 0

    6. Reason Code – 99

    7. Hold Code – 3

  7. Use CC REQ54/ADJ54 to write off the expired amount. Input the following fields:

    1. Blocking Series – 19

    2. Transaction Code – TC 534

    3. Amount – Balance to be written off with a minus sign or a zero amount

    4. Source Code – 0

    5. Reason Code – 099

    6. Hold Code – 3


    Note:

    For BMF accounts, leave the Source Code and Reason Code fields blank.

5.19.10.5.6  (09-15-2010)
Claim Pending Collection Statute Transcript (AM 23W)

  1. The AM 23W transcript is generated to alert the campus of the W— freeze condition created by a TC 470 cc 90, 93, or 95 and the tax module is within 180 days of the Collection Statute Expiration Date (CSED).

  2. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.6.1  (09-15-2009)
Processing AM23W Transcripts

  1. Reverse any TC 470, with the exception of TC 470 cc 95. For transcripts with TC 470 cc 95, document the AMS and close the control.

    Note:

    This is a restricted period and the only status the module will update to is status "12" (if it becomes full paid). Master File will not generate any notice during this period.

  2. See IRM 5.19.10.5.1, General Procedures For All Transcripts.

  3. Input the following history item on AMS, AM23WCSED, and close the control.

5.19.10.5.7  (10-15-2012)
Notices of Potential Manual Penalty/Interest Adjustment (CP 86 and CP 186)

  1. The CP 86/186 Notice generates when:

    1. A payment transaction posts to a module and the credit amount is greater than the assessed module balance due amount, and

    2. There is an interest or penalty computation restriction present.

    3. An account is transferred in from the Retention Register with Doc Code 51 or 52.

    4. An additional CP 86/186 Notice generates when subsequent credits post and the same situation as above is present. The Accounts Management function will work all CP 186s other than those meeting CSCO criteria.

    Note:

    The Retention Register contains all entity and tax modules removed from the Master File. Basic criteria for removal include: zero module balance, no freeze or unsettled condition(s) present, no activity to the module for 27 months.

  2. Collection Operations will only work collection related issues, all others should be routed to the appropriate operation.

    Reminder:

    For accounts containing a TC 582 Federal Tax Lien, see IRM 5.19.10.5.1(11), General Procedures For All Transcripts.

  3. Conditions which create restrictions are:

    1. Interest has previously been manually assessed (TC 340) or abated (TC 341).

    2. FTP penalty has previously been manually assessed (TC 270) or abated (TC 271).

    3. Any transferred in transaction (Doc. Code 51 or 52 posted).

    4. Assessed fraud penalty (TC 320).

    5. Fiduciary return Form 1041, U.S. Income Tax Return for Estates & Trusts, assessed as an installment account (Status Code 14).

    6. Form 706, U.S. Estate Tax Return, assessed as an installment account (Status 14).

  4. Verify the appropriate disaster declaration by accessing the Disaster Declarations/FEMA at http://www.tris.irs.gov/fema/.

  5. WI CSCO works IMF accounts and SB/SE works BMF accounts.

5.19.10.5.7.1  (10-15-2012)
Processing CP 86 and CP 186

  1. Analyze the module and recompute the interest and/or penalty using CC COMPA or COMPAF per IRM 20.2, Interest, and IRM 20.1, Penalty Handbook, and follow appropriate procedures. Determine what transaction code restricted the module.

  2. If an unreversed TC 480 or TC 780 is present on the module, document AMS and close the control. If a previous transcript has been routed without resolution, contact Headquarters, following campus directions. If the TC 780 was reversed with a TC 788 and both statuses are "12" , refer to (5) below. If the offer was withdrawn (TC 482), rejected (TC 481) or erroneously posted (TC 483) refer to (4) below.

  3. If an unreversed TC 520 is on the account, refile any returns associated with notices and close the control. If the TC 520 was reversed with a TC 521, refer to (4) below.

  4. If additional interest or penalty is due, input an adjustment transaction to assess the additional amount using CC REQ54. Caution should be taken when there is a 120% interest charge on the account. The interest TC will have a Julian date of 999.

    1. If the account was previously in Status 60, refer to IRM 5.19.10.10.2.1, Full Paid Restricted Interest and Penalty Accounts — CSCO Processing, for processing. Provide necessary feedback to the IAAL Operation.

    2. If the account has a TC 270 or 271 on the module, it is a restricted account. Verify the percentage of the FTP penalty. If the FTP penalty maximum percentage has been assessed, input a TC 971 AC 262. Refer to IRM 21.3.1.4.52, CP 86 Restricted Interest/Penalty Conditions. To remove the prior restriction and allow automatic generation of the FTP Penalty by master file, refer to IRM 20.1.2.1.5(4), Manual Penalty Assessments.

  5. If no additional interest or penalty is due, input TC 290 for a zero amount with blocking series 15 and Hold Code (HC) 3 using CC REQ54. Use blocking series 00 if you have the original return. Use the CP 186 as your source document.

    Note:

    If no additional interest or penalty is due and the credit has been resolved and the account is in ST 12, do not input a TC 290 for zero.

  6. Unless you are using blocking series 00 and have the original return, do not send any cases to file. Use NSD with comments and destroy the transcript.

5.19.10.5.8  (05-01-2007)
Non-Master File Liability (NMFL) Transcripts

  1. The Non-Master File Liability (NMFL) transcripts are generated by Enterprise Computing Center at Martinsburg (ECC-MTB) when a second credit posts to a module after issuance of a CP 44 Notice and the V— freeze created by the TC 130 remains on the taxpayer’s account. When a TC 740 posts to the transcript module and creates a credit balance, the NMFL transcript will generate.

    Note:

    Any module containing a TC 608 must be processed using PMTEXPCSED Transcript procedures.

5.19.10.5.8.1  (05-01-2007)
Processing NMFL Transcripts

  1. If the transcript cannot be resolved within 14 days from the computer notice date, control the transcript using Category Code CP 44 and enter "NMFL" in the history section of the control base.

  2. If there is an open control base with category Code CP 44/188, contact the examiner assigned for case resolution. For all others cases, see (3) below.

  3. Process the case using IRM 5.19.10.3.9, IRM 5.19.10.3.10, IRM 5.19.10.3.11, and IRM 5.19.10.3.12.

  4. Use the original NMFL transcript in lieu of a CP 44/188 when working your case.

  5. If the module contains a TC 608 process following IRM 5.19.10.5.2, PMTEXPCSED Transcripts. "Do not process following normal NMFL Transcript procedures."

5.19.10.5.9  (10-15-2012)
Duplicate Refund (DUPREF) Transcript

  1. A Duplicate Refund Transcript will generate weekly to the Operation if a TC 840 posts to an account and there is a previous TC 840 or TC 846 posted. These transcripts will be reassigned to the originator of the duplicate refund.

  2. If the case resulted in an erroneous refund, refer to IRM 21.4.5, Erroneous Refunds, for procedures.

  3. If a BMF DUPREF transcript is received in Atlanta due to a levy payment, close the transcript with no action.

5.19.10.5.9.1  (09-15-2010)
Processing Duplicate Refund (DUPREF) Transcript

  1. Review history on AMS and IDRS.

    1. If history shows a Letter 549C or Form 668D, Release of Levy/Release of Property from Levy, was previously sent, input history item, "previous action taken."

    2. If the account shows the module is now being controlled by "ACS-category code LEVY" , input history item.

    3. If there is no indication that a Letter 549C or Form 668D, has been sent, continue processing.

  2. Research to determine the source of the payment. Use Command Codes IADIS, ENMOD, IPRTRI, LEVYS, and the Remittance Transaction Research System, RTR System.

    1. If the source can be determined, prepare Form 668D; input appropriate history item on AMS.

    2. If the source cannot be determined, input Letter 549C with an open paragraph. The open paragraph should state the following: "Please take a copy of this letter to your payroll officer. This authorizes them to discontinue the payroll deduction or wage levy immediately." Input the appropriate history code on AMS.

5.19.10.5.10  (09-15-2009)
Verify Payment (VERFPYMT) Transcripts

  1. A VERFPYMT Transcript generates when a payment posts to a debit balance module, resulting in a credit balance of ≡ ≡ ≡ ≡ . Verify Payment (VERFPYMT) Transcripts. The VERFPYMT Transcripts are generated on a weekly basis. The transcripts are forwarded to the appropriate AMRH Unit. AMRH will sort and forward any transcript relating to Collections to the campus.

5.19.10.5.10.1  (05-01-2007)
Processing VERFPYMT Transcripts

  1. If the module contains a TC 130, V— freeze code, see IRM 5.19.10.3, Credit Offsets or IRM 5.19.10.5.8, Non-Master File Liability (NMFL) Transcripts.

  2. For all other conditions; refer to procedures in IRM 5.19.10.5.9, Duplicate Refund Transcripts.

5.19.10.5.11  (10-15-2012)
NOMRG-TDA Transcript NM07

  1. A NOMRG Transcript with Reason Code NM07 will generate when both accounts being merged contain the following conditions within the same tax period: both accounts are in TDA/TDI (22, 24, 26) status and the Location Codes (Primary or Secondary) do not agree.

  2. The "TO" account is in a TDI Status and the "FROM" account has TDA modules for which there are no modules for same MFT/TXPD in the taxpayer's account.

  3. In order to merge two related accounts, both BOD Codes must match.

  4. Document your actions and contacts on AMS for both TIN.

5.19.10.5.11.1  (10-15-2012)
Processing NOMRG-TDA Transcript

  1. Control the case on IDRS to category NMRG.

    1. Cases involving multiple taxpayers using the same Taxpayer Identification Number (TIN) are classified generally as mixed entity, Scrambled SSN cases, or True Scrambled SSN.

  2. Refer to IRM 21.6.2, Adjusting TIN-Related Problems, for detailed information.

  3. Reassign the control base to a specialized control number per IRM 21.5.2.3 , Adjustment Guidelines – Research.

    If... Then...
    TIN is a scrambled SSN (See IRM 21.6.2.4.2.1(6), Telephone Inquiries, on how to identify this type of account.)
    1. Do not make corrections to the account

    2. Enter history on AMS and close the case

    Account has identity theft issues, identified by the presence of TC 971 ac 501 or 506. See IRM 10.5.3.2.5, Identity Theft Incident Tracking Indicators.
    1. Do not make corrections to the account

    2. Enter history on AMS and close the case

    3. See IRM 5.19.1.9, Identity Theft – Overview.

    If it is a true No Merge (duplicate tax periods on the valid and invalid side and both carry a TC 150)
    1. Do not change the address and location code

    2. Do not attempt to merge

    3. Prepare Form 4442, Inquiry Referral, to the Inventory Control Manager (ICF)

    4. Enter the following history on AMS: "True duplicate filing condition. Case routed to ANSC Site Specialization."


    Note:

    Route True NoMerge DUPF to the site Specialization hold number 0830105044 per IRM 21.6.2.4.1.4, Reassignment of NOMRG Cases due to Site Specialization.

  4. Analyze the account to determine which IRS operation or function should be contacted to advise them of the no merge issue (ACS, Revenue Officer).

    If... Then...
    Both sides are in Status 22/22, 22/TDI or 22/24
    1. Contact the ACS Support Liaison on SERP Who/Where

    2. Advise them to release the levy until after the merge.

    Both sides are in Status 26/26, 26/TDI or 26/24 and not assigned to a Revenue Officer (the last two digits of the Collection assignment code on CC TXMOD are “00”)
    1. No contact is necessary

    2. Resume processing in (5) below

    Both sides are in Status 26/26, 26/TDI or 26/24 and are assigned to a Revenue Officer. The last two digits of the assignment number will be 01 – 99, (except 96).
    1. RO by TSIGN/ZIP/STATE. Refer to on SERP Who/Where for contact information.

    2. Contact the assigned Revenue Officer(s) by phone to notify them of the pending merge. If the RO does not answer, leave a message with a brief explanation, your name and telephone number.

    3. Continue processing the case

    Accounts are in Status 22/26 Follow the procedures in boxes 1 through 3 above
    One or both sides are in Status 72
    1. Contact Insolvency, see SERP Who/Where, Insolvency (Bankruptcy) National Field/Centralized Site Directory, to determine if the TC 520 is still open or should be closed.

    2. If Insolvency indicates the TC 520 should be closed, ask when the TC 521 will be input and monitor the account for that period.

    3. If the TC 520 is still open after monitoring or Insolvency indicates TC 520 is still open, do not attempt to merge.

    4. If unable to contact Insolvency and after leaving a message, you do not receive a response within 21 days, do not attempt to merge.

    5. Input AMs history and close the case.

    Both sides are in Status 24/24 or 24/TDI
    1. No contact is necessary

    2. Resume processing in (5) below

    One or both sides are in Status 60. Changes to the location code and merging of the account will cause the installment agreement to default
    1. To prevent a default notice from issuing, manually default the installment agreement using CC IADFL. See IRM 2.4.30, Command Codes IAGRE, IAORG, IAPND, IAREV, IADFL, and, IADIS.

    2. Use Default Category “Other” and Suppress Default Indicator “1”

    3. For Direct Debit Installment Agreements, (DDIA), check CC EFTAD per IRM 5.19.1.10.6.1, Requests to Skip a Payment, to turn off the next payment, if needed. Enter the bank information from CC EFTAD onto AMS for reinput to CC IAGRE after the merge.

    4. For Payroll Deduction Installment Agreements (PDIA), enter the payer information from the CC IAGRE onto AMS for reinput after the merge.

    5. Follow with CC STAUP 22 09

    6. Update AMS history, "IA defaulted to merge TINs. Will reinstate IA after merge."

  5. If the valid and invalid TINs are different numbers, use CC IMFOLE to research both the valid and invalid TINs. Determine which has the MOST CURRENT address and location code information. See IRM 3.13.5, Individual Master File Account Numbers.

    If... Then...
    MOST CURRENT information is on the invalid TIN Continue processing in (6) below. Make the necessary changes to the valid TIN
    MOST CURRENT information is on the valid TIN
    1. Move the invalid TIN to an IRSN

    2. IMPORTANT: Input CC IMFOLB to restore all retention modules to Master File on both sides. If retention modules are not returned to Master File prior to moving the account to the IRSN, those modules will no longer be accessible. The format for CC IMFOLB is the same as CC IMFOLT. See IRM 2.3.51.4, Restoring RRR Tax Modules to Master File.

    3. After CC IMFOLB input, monitor for the posting of TC 013 and TC 370 before proceeding

    4. Use CC TMSSNI to order a temporary number. See IRM 2.4.59, Command Code TMSSN

    5. Using CC ENREQ, input TC 041 on the invalid TIN to move it to the new IRSN.

    6. Make the following changes per (6) through (12) to the IRSN TIN before merging the account to the valid TIN.

  6. The following changes can be made with one input using CC ENREQ, with the exception of BOD code changes. BOD code changes should be done last. Document your actions and contacts on AMS for both TINs.

  7. The account addresses must match on both the invalid and valid TIN. Correct the address to match the MOST CURRENT account.

  8. Location codes must match. Verify the location codes on each account and make corrections, if needed.

  9. The name control must be valid per CC INOLES. If the name control on the invalid segment does not match the valid SSA name controls, you may need to validate the name to merge the accounts. Refer to Document 7071, Name Control Job Aid for Individual Master File (IMF) Taxpayers.

    1. Only change the name for the most recent return filed.

    2. Hyphenate the valid name with the invalid name.

    3. Put a bracket before the last name.

    4. Use the year of the return and the proper filing status from CC TXMOD or IMFOLT. This will generate a TC 013 on ENMOD.

  10. If the TIN requires correction, follow these procedures. If the invalid TIN is a different number than the valid TIN process as follows:

    1. Use CC INCHG on the invalid TIN to input the correct TIN.

    2. The above action will generate TC 011 on CC ENMOD. The name controls must match.

  11. If the four digit location code still does not match after CC ENREQ has posted, follow the procedures below. Change the CLC to match the MOST CURRENT account.

    1. Only the last two digits of the location code can be changed. Use CC ENREQ. If necessary, refer to the Universal Location Code (ULC) and Area Office (AO) in the Job Aid Book on SERP. Use CC ENREQ and Doc Code 50.

  12. In order to merge two related accounts, their BOD Codes must match. Make the necessary changes to the BOD Code on the MOST CURRENT account.

    1. Use CC REQ77 (overlaid on CC ENMOD). Input TC 971 with action code (ac) 050.

    2. Use the CURRENT date as the transaction date and input the appropriate BOD Code.

  13. If the invalid TIN and valid TIN are the same number and none of the above conditions apply, input TC 041 via CC ENREQ.

  14. On the "FROM" account, the message is "MERGE IN PROGRESS-LOSING ACCOUNT" . On the "TO" account, the message is "MERGE IN PROGRESS-GAINING ACCOUNT" . It can take several weeks before the merge is complete. Monitor the module until the merge is complete.

  15. After the merge or resequencing transaction is input,

    1. If the account was in Status 22 or 26 prior to the merge, input CC STAUP 22 00 to return the account to it’s original status.

    2. If the account was in Status 60 prior to the merge, reinput the installment agreement. Do not charge a reinstatement fee.

    3. Close your IDRS control base.

    4. On accounts dealing with ITINs, follow IRM 3.21.263.7.4, Merges Involving ITIN, to have the ITIN revoked.


More Internal Revenue Manual