2.9.1. Integrated Data Retrieval System

(1) This IRM and contained sections provide the user general instructions and information for the use of the Integrated Data Retrieval System (IDRS) in the Campuses and Area Offices.

(1) All proposed changes to this document should be directed to the Integrated Data Retrieval System (IDRS) Program Director as owner of this process.

(1) IDRS Project Lead is responsible for

• Review and implementation of Work Requests that affect IDRS

• Updating the contents of this IRM

(1) Overview of Integrated Data Retrieval System.

1. The provisions of this Section apply to IDRS processing in the Campuses and Area Office

2. This Section contains general information on the system, and provides instruction on how and when to use the system in the various functional areas of the Campuses and Area Offices.

3. The instructions contained herein are to be used in conjunction with all other related ADP Handbooks and IRM Sections containing specific detailed procedures that parallel IDRS processing unless otherwise stated herein.

(1) The main purpose of this Section is to describe how IDRS impacts on the Campus and its various functions by specifying procedures to be used when operating with IDRS. Specific procedures that exist in other ADP Handbooks or IRM Sections will still apply for IDRS. Any overlapping instructions in this IRM are still governed by the other procedures. Where other ADP Handbooks or IRM Sections specify the use of manual forms, such as the requirement for preparing Forms 2275, 3870, etc., the use of the specified forms may be replaced by command codes. The applicable procedures should still be followed, using screen entry instead of the form.

(2) The IDRS Security System is designed to provide protection for both the taxpayer and the IDRS user employee. The taxpayer must be protected from unauthorized disclosure of information concerning his/her account and unauthorized changes to it. The IDRS user employee must be protected from other personnel using his/her identification to access or make changes to an account.

(3) IDRS users are authorized to access only those accounts required to accomplish their official duties. IDRS users must not access their own or spouse's account, the account of a friend, relative or co-worker, or any account in which they have a personal or financial interest. IRS prohibits employees from accessing tax account information to satisfy personal curiosity or for fraudulent purposes.

(4) It's the Law: Unauthorized browsing of tax account information is now a criminal offense. The Taxpayer Browsing Protection Act makes browsing a criminal misdemeanor punishable by automatic termination from employment and by either a fine or imprisonment, or both. Upon conviction in a court of law, a federal employee will automatically be fired and may be fined up to $1,000 and/or imprisoned for up to a year and/or assessed the costs of prosecution.

(1)

(1) The specific instructions for use of the IDRS Terminals and the various IDRS Command Codes are included in IRMs 2.3 and 2.4.

(2) Various codes and messages used in IDRS are included in IRMs 2.3, 2.4, and 2.7.

(3) There are currently a number of ADP Handbook Transmittals, Supplements and IRM Sections which contain procedures on the use of IDRS.

(4) This section will be used with the above mentioned ADP Handbooks and IRM Sections to provide the necessary information to all users of the system. Various ADP Handbooks and IRM Sections have incorporated general procedures for IDRS into the proper functional responsibility areas. If procedures contained herein are in conflict with the responsible functional procedures, the other ADP Handbooks or IRM Sections will govern.

(5) The main purpose of this Section is to describe how IDRS impacts on the Campus and its various functions by specifying procedures to be used when operating with IDRS. Specific procedures that exist in other ADP Handbooks or IRM Sections will still apply for IDRS. Any overlapping instructions in this IRM are still governed by the other procedures. Where other ADP Handbooks or IRM Sections specify the use of manual forms, such as the requirement for preparing Forms 2275, 3870, etc., the use of the specified forms may be replaced by command codes. The applicable procedures should still be followed, using screen entry instead of the form.

(6) Note: The term 53'd is used throughout this IRM. 53'd means there is a tax module on an account that contains an unreversed TC-530, which means currently not collectible.

(1) Campuses which have the entity on their IDRS data base.

(2) Campuses to which a tax module is being sent this cycle.

(3) Campuses for which an unpostable or an entity notice is issued this cycle.

(4) Campus for the Area Office of the TC 844 Area Office in the entity.

(5) Campus for the Area Office and Collection location codes.

(6) Campus for the file location code in the DLN of a TC 000–150.

(1) A tax module is being extracted.

(2) A current cycle transaction posts to the entity.

(3) An unreversed TC 914 posts to at least one tax module in the account.

(4) An entity change posts in the current cycle.

(5) The zip code changes (current cycle TC 019).

(6) A merge takes place or EIN changes.

(7) A notice is issued or a transaction unposts this cycle.

(8) TC 902 with block & serial # not 89898 is processed or TC 902 or unpostable transaction from a previous cycle that had no matching tax module then is processed.

(9) Entity CSED freeze is released.

(10) TC 824,131, 521/522 (Closing Code other than 71–74) posts.

(11) TC 520 (Closing Code 83/85/88) posts.

(12) Entity closing code 53 switch is turned off (there is no longer a 53'd tax module in the account).

(13) Deferred action 02 expires and Form 1120 filing requirement is updated.

(14) Account is marked for IDRS recovery.

(15) Filing requirement updated.

(1) Taxpayer is potentially dangerous.

(2) Refund Scheme—TC918.

(3) EIN is a temporary TIN or the TIN changes.

(4) Entity notice data or TC 011 or TC 04x (other than TC 041) posts current cycle and one of the following is true:

1. Account is already on IDRS.

2. Account is in TDI status.

(5) Transaction posts in current cycle to entity and the account is already on IDRS.

(6) TC 902 that is not blocked 898 is processed.

(7) An entity transaction unposts to an account that is at Master File and the account is not at the Campus of the Area Office in the unpostable.

(8) The account is in TDI status and the location code changes to a different Campus due to a merge.

(9) A transaction is resequencing (TC 001, TC 003 current cycle or TC 006 preceded by a TC 005 in previous cycle).

(10) An entity module is being transmitted with a reason code A2 or A3 tax module (AIMS).

(11) Entity change posts current cycle.

(12) In the first IDRS extract cycle of a year, a search is made for any transaction that may have posted in an earlier cycle of that year (dead cycles). At this time, such a transaction would be considered as "current ".

(13) Location code changes due to merge.

(14) A non-AIMS tax module is being extracted for this entity.

(15) Entity CSED freeze is released.

(16) TC 824, 131, 521/522 (Closing Code other than 71–74) is present.

(17) TC 520 (Closing Code 83/85/88) is present.

(18) Entity closing code 53 switch is turned off (there is no longer a 53'd tax module in the account).

(19) Deferred action 02 expires and Form 1120 filing requirement is updated.

(20) The account is marked for IDRS recovery and the account is on IDRS.

(21) A transaction unposts to a tax module that is not at Master File.

(22) An entity transaction posts in the current cycle with a Julian date greater than 400.

(23) Current cycle transaction posts and the account is on IDRS.

(24) There is an entity IDRS Section. The last period satisfied activity indicator is on and the Status 58 Indicator is a 1.

(25) The current month is less than 16 months from the establishment date month, account is not on IDRS and a current cycle entity transaction posts.

(1) Campuses which have the tax module on their IDRS data base.

(2) Campuses for which an unpostable or a tax module notice is issued this cycle.

(3) Campus for the Area Office of the TC 844 Area Office in the entity.

(4) Campus for the Area Office and Collection location codes.

(5) Campus indicated by the AIMS control Campus and TC 429 Campus.

(1) Current cycle transaction posts or status updates.

(2) Current entity transaction posts.

(3) Unreversed TC 914 posts.

(4) Entity change posts in current cycle.

(5) TC 019 (zip change) posts this cycle.

(6) Account is resequencing.

(7) Notice is issued or transaction unposts this cycle.

(8) TC 902 with block & serial # not 89898 is processed.

(9) TC 429 posts without tax shelter release indicator.

(10) IDRS activation switch is significant (used for recovery).

(11) CP 101, 102, 103, 104, 107 or 131 with generated notice code of 24 or 26 generated in current cycle.

(12) It is an FTD module (MFT 01 tax period 000000).

(13) Module has an FTD debit or credit freeze.

(14) Entity 918 freeze is on.

(15) Module in Status 23 with assessed module balance and accruals above tolerance and entity status 02 or 03 switch is on.

(16) Master File tax module IDRS recovery switch set.

(1) The current status history section has a status code of 29.

(2) An unreversed TC 914 is present.

(3) One of the following freezes is present: W-, K-, P-, H-, -X, -B, -R, -K, -F, -U, -Y, -W, -E, -J, -H, R-, B-, -P, Q-, -V, L-.

(4) There is a posted return (except MFT 13) and:

1. The CSED is not expired.

2. The module is not 53'd.

3. DAR code is other than 01–39.

4. The current status code is 13, 14, 18, 19, 20, 21, 22, 56, 58 or 60.

(5) Status is 02 and Notice number is 2. Has prior 02 with Status Indicator = B, is in credit balance and the entity TDI switch is not a 1.

(6) The current status code is 03.

(7) The current status code is 02 and another module is in 03 status.

(8) The current status code is 02 and the status history notice number is 4.

(9) The current status code is 02 and the status indicator is not B and there is a credit module balance.

(10) A TC 740 posts.

(11) There is a duplicate filing condition.

(12) There is an AIMS account already on IDRS, and either TC 421 posts current cycle or an unreversed TC 420/424 is posted. For an unreversed TC 420/424, at least one of the following conditions must also be present:

1. TC 429 posts.

2. The tax module activity switch is significant.

3. The cycle of the most current status history section equals the cycle of the 23C date.

4. There is an entity change.

(13) CP notice (except CP 210, 138, 145, and 173) is issued.

(14) A TC28x, 70x, 73x, 75x, 79x, 82x (except TC 826), 85x (except TC 856), 87x or 89x posts in current cycle.

(15) A TC 846 posts with refund amount over the minimum MF extraction criteria amount.

(16) TC 902 block/serial # other than 89898 is processed.

(17) TC 902 from a prior cycle for the module that did not exist at that time is processed.

(18) There is an unpostable this cycle.

(19) There is a status code of 06 or higher in current cycle immediately preceded by an 02 status.

(20) This is an FTD module (MFT 01 tax period 000000) with credit balance and there is at least 1 balance due tax module on the account.

(21) There is no posted return and there is a credit module balance.

(22) There is a posted return (except MFT 13), the CSED is not expired and at least one of the following conditions exists:

1. The module is in status 12 and either the module is 53'd, the closing code is 09 and the accruals (interest total + failure to pay total - (failure to pay assessed + interest assessed)) are over the minimum MF extraction criteria amount or the module is not 53'd and accruals are over the minimum MF extraction criteria amount.

2. The status code is 23 and assessed module balance (module Balance and assessed interest + interest paid) + accruals are over the minimum MF extraction criteria amount.

3. The module is 53'd, the closing code is 09, assessed module balance + accruals are over the minimum MF extraction criteria amount and the status code is 19, 20, 21, 22, 56, 58, or 60.

(23) There is a posted return (except MFT 13), the CSED is not expired and the status code is 12, 19, 20, 21, 22, 23, 56, 58 or 60 and either:

1. The module is 53'd and the closing code is not 09.

2. The module is not 53'd and the closing code is 01–08 or 10–39.

(24) There is a resequencing entity (current cycle TC 001, 003 or 006 preceded by 005 in previous cycle).

(25) This is an AIMS tax module and:

1. TC 421 posts in current cycle.

2. Unreversed 420/424 posts and either one TC 429 is input or the tax module activity switch is significant or the cycle of the most current status history section equals the cycle of the 23C date or there is an entity change.

(26) The tax module is on IDRS and either:

1. A transaction posts in the current cycle.

2. An entity change transaction posts in previous cycle.

3. The tax module activity switch is significant.

4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

5. The cycle of the current status is equal to the cycle of the 23C date. In the first IDRS extract cycle of a year, a search for any current status that posted in an earlier cycle (dead cycles) of that year is also made. In the first extract cycle such a module would be considered as if the current status cycle and the cycle of the 23C date were equal.

6. Master File tax module IDRS recovery switch set.

(27) The current status or a status with current cycle date is 02 and either status indicator is not B or status cycle is not more than 15 cycles old.

(28) Entity TC 918 freeze is on and the module tax period is current year or one year prior (Reason Code KK).

(29) Extract the module in the cycle a TC 971 AC 043 posts.

(1) Campus for the Area Office and/or TDI location code in the entity

(2) Campus as derived from the control DLN of a return module being extracted to IDRS.

(3) Campus as derived from the file location number of the DLN of a transaction that imposted current cycle.

(4) Campus as derived from the file location code of the DLN of a TC 902 directed either to the entity or a return module in the account current cycle.

(5) Campus specified by the EPMF IDRS indicator which was set by a TC 902 received in a prior cycle that was directed to a return module which was not present but is present now.

(6) Campus associated with the file location code of the DLN of the TC 000

(7) All three centralized (Memphis, Atlanta, and Brookhaven) Campuses

(1) A current cycle TC 902 directed to the entity is processed.

(2) An entity transaction unposts from the entity this cycle.

(3) A return module is being extracted in the current cycle.

(4) The account is marked as being on the IDRS TIF in at least one Campus and at least one of the following conditions is met:

1. The location codes (TDI or Area Office) change in the current cycle.

2. A transaction posts to the entity in the current cycle.

3. The zip code changes in the current cycle.

(5) The entity is part of an account that is being resequenced this cycle—either resequencing from another account number this cycle or another account is being merged into this account this cycle and, the account is marked as being on the TIF in at least one Campus.

(6) A TC 000 posts in the current cycle or if the entity establishment date plus 15 months is equal to or greater than the current year month and either a transaction posts to the entity in the current cycle or a TC 019 updates the zip code in the current cycle.

(1) One of the following statuses is set in the current cycle: 02, 03 or 06.

(2) A TC 902 directed to the return module is received this cycle.

(3) The IDRS indicators show that the module was requested in a prior cycle, but was not extracted and the module is now on the EPMF returns file.

(4) A transaction unposts from the module in the current cycle.

(5) The return module is part of an account that is being resequenced this cycle—either resequencing from another account number this cycle or another account is merging into this account thus cycle and, the account is marked as being on the TIF in at least one Campus.

(6) The IDRS indicators show the module is on IDRS in at least one Campus and one or more of the following conditions occur:

1. A transaction posts to the tax module in the current cycle.

2. The module status history is updated in the current cycle.

3. A TC 428 posts to the module in the current cycle.

4. The return module is part of a plan that has either had a slot-in or plan merge successfully completed current cycle.

5. A return module is extracted to AIMS in the current cycle.

(1) Campuses to which a tax module is being sent.

(2) Campuses for which an entity notice is issued.

(3) Campuses which requested the entity in a prior cycle.

(4) Campuses requesting the entity in the current cycle.

(5) Campuses which input an entity or tax module transaction which unposts in the current cycle or unposted in a prior cycle.

(6) Campus for the Area Office code of the TC 844 Area Office in the entity.

(7) Campus for the Area Office or Collection location code in the Entity.

(8) Campuses determined from the posted entity transaction DLN if the transaction is a current cycle posted IDRS generated TC 000–149.

(9) A memo entity will not be extracted to the TIF unless there is a current cycle posted transaction in the entity and either the account is marked as being on IDRS or the entity TDI switch indicates an 02 or 03 status tax module is in the account.

(10) Campus determined by the DLN File Location Code in an open TC 922 if the first process code is equal to 03 or 06 (AUR only).

(1) The zip code is being updated by a TC 019.

(2) Account registers activity.

(3) A module within the account is being requested with a TC 902 or a TC 429.

(4) A TDA information record is being issued for a module within the account.

(5) A notice is being issued.

(6) A transaction unposts this cycle.

(7) A change in a tax module status occurs.

(8) A math error freeze is being released.

(9) The 47 hold is being released.

(10) A TC 582 or TC 583 transaction is being received.

(11) The bankruptcy freeze is being released.

(12) The offset overflow freeze is being released.

(13) The offset in expired module freeze is being released.

(14) The erroneous refund hold is being released.

(15) The module contains an unreversed TC 420 or 424.

(16) The IRS litigation freeze is being released.

(17) The scrambled SSN freeze is being released.

(18) The location codes update.

(19) A TC 912–919 posts.

(20) A TC 924 with reference number 108 posts.

(21) The module contains an open TC 922 with a process code equal to 03 or 06 and DLN FLC indicates AUR SC in the first position.

(22) Entity Combat Zone indicator was set or released this cycle, or the Entry Departure Date was corrected. Check CC IMFOLE on Line 11 for the Combat indicator. Indicator "1" indicates the Combat Zone is set and -C freeze is active/turned on (restricts assessment and collection of any tax). Indicator "2" indicates the Combat Zone is released and -C freeze is inactive/turned off (the assessment and collection of any tax may resume using normal procedures).

(1) The entity contains an unreversed TC 918.

(2) The entity PDT indicator is on.

(3) The entity scrambled SSN indicator is on.

(4) An entity notice (except 050) is being issued this cycle.

(5) A TC 011 posts to the entity in the current cycle and either the account is marked as being on IDRS or the entity TDI switch indicates an 02 or 03 status tax module is in the account.

(6) A TC 902 is received this cycle.

(7) The entity was requested in a prior cycle.

(8) Module requested via ICP.

(9) An entity or tax module transaction unposts this cycle and the module is not already on IDRS.

(10) The entity TDI switch indicates an 02 or 03 status tax module is on the account and the Collection location code or Area Office changed this cycle.

(11) The account is resequenced or merged this cycle and account is on IDRS.

(12) The entity is being extracted because a tax module under AIMS control is being extracted.

(13) One of the following occurs in an account containing an unreversed TC 420 or 424: A new name (first or second), street address, city, state or zip code posts.

(14) The account is marked as being on IDRS and Collection location code or Area Office change this cycle.

(15) The scrambled SSN indicator is turned off this cycle.

(16) The entity is being extracted because of a tax module extraction.

(17) The account is marked as being on IDRS and the zip code was updated by a TC 019, 150 or 430 in the current cycle.

(18) The account is marked as being on IDRS and an entity transaction posted in the current cycle.

(19) A TC 000 thru TC 149 with a Julian date inflated by 400 posts to the entity in the current cycle. Note: TC000 with a block/serial number of 99999 will not cause extraction.

(20) The minister indicator is set or released this cycle.

(21) The OIC year field was cleared this cycle and the account is marked as being on IDRS.

(22) The Federal Employee Indicator is set this cycle and the account is marked as being on IDRS.

(23) The TC 130 freeze was released in the current cycle and the account is marked as being on IDRS.

(24) A Master File recovery occurs in the current cycle and the account is marked as being on IDRS.

(25) The Entity FMS Levy Indicator was set or released in the current cycle and the account is marked as being on IDRS. The IDRS Entity Extract Indicator will be set to 4.

(26) The Entity Extract Indicator is set and the account is marked as being on IDRS.

(27) CC6X indicators have been set this cycle. The IDRS Entity Extract Indicator will be set to 4.

(28) The Withholding Compliance Case(WHC) Indicator in the Entity has been updated in the current cycle and the account is marked as being on IDRS. The IDRS Entity Extract Indicator will be set to 2.

(1) Campus for the Area Office or Collection location code in the entity.

(2) Campus for the latest status history AO on the tax module (only if the latest status is 02 or 03).

(3) Campuses having a notice issued for this tax module in the current cycle.

(4) Campuses that input a tax module transaction which unposts from this module in the current cycle.

(5) Campuses that input a tax module transaction which unposts from this module in a prior cycle because the tax module was not on the MF.

(6) Campuses which requested the tax module in the current cycle.

(7) Campuses which requested the tax module in a prior cycle as indicated by the MF IDRS indicators.

(8) Campuses for which a TDA information record was issued this cycle.

(9) Campuses determined by the audit control number in an unreversed TC 420 or the DLN in the TC 424, whichever is later. If an unreversed TC 420 or 424 is not present in the module and a TC 421 posts in the current cycle, use the TC 421 DLN.

(10) Campus determined by the DLN file location code in a TC 300 if the posting cycle is equal to the current cycle.

(11) Campus which requests the module via a TC 429.

(12) Campus determined by the DLN file location code in an open TC 922 if the first process code is equal to 03 or 06 (AUR only).

(13) Campus determined by the DLN file location code in an unreversed TC 914.

(1) The module is in status 29.

(2) The module contains an unreversed TC 914 or TC 916 or the account contains an unreversed TC 918.

(3) The module is frozen due to a TDI Refund freeze.

(4) module contains a TDI Refund freeze that is being released in the current cycle.

(5) The module contains a current posted TC150 and the STEX Freeze is set to a 3.

(6) One of the following freeze or hold conditions exists in the module: -Y, -W, -V, H-, J-, D-, -D, X-, B-, R-, -J, W-, K-, -E, P-, -X, -B, -R, -Q, -K, -F or -U.

(7) The module contains a settled return (except on civil penalty module—MFT 55), the module is not 53'd, the module closing code is not equal to 01–39, the CSED is not expired and the module is in status 19, 20, 21, 22, 24, 26, 54, 56, 58 or 60.

(8) The module is updated in the current cycle to status 02 with a status indicator of 2 and was previously in status 02 with status indicator B and the module is in credit balance.

(9) Both the module is updated to status 02 and the FERDI indicator is set in the current cycle. (The FERDI indicator will be a 9 in the cycle that it is set.)

(10) Module meets any one of the following conditions:

1. Module is in status 03.

2. Module is in status 02 and another module in the account is in status 03.

3. Module is in status 02 with a status indicator of 4.

4. Module is in status 02 (excluding 02 with status indicator B) and the module balance is credit.

(11) The module is in credit balance with a settled return and there is an unreversed DMF TC 130 present in the entity.

(12) The module contains a duplicate return or amended return freeze.

(13) The module contains a TC 740 freeze (Undelivered Refund).

(14) A TC 150 posts to the invalid segment.

(15) An IMF reminder notice (CP/71/71A/71C/71D) is issued in the current cycle.

(16) A tax module notice (except 021, 045, 047, 049, 050, 051, 053 or 086) is being issued this cycle.

(17) A TC 70X, 82X (except TC 826), 73X, 85X (except TC 856), 75X, 87X, 28X, 79X, or 89X posts to this module in the current cycle.

(18) A TC 902 is received this cycle from a Campus for this tax module.

(19) This tax module was requested via a TC 902 in a prior cycle but the request was not honored due to the module not being on the Master File.

(20) The tax module request is via ICP.

(21) A TC 592 posts in the current cycle in this module or a previous module in the account and this module is in status 02.

(22) A transaction went unpostable from the tax module in the current cycle.

(23) The account is a resequenced/merged account and the entity TDI switch indicates an 02 or 03 status tax module is in the account and the amount is marked as being on IDRS already.

(24) The module status was updated from 02 status to 06 status or greater in the current cycle.

(25) This is a debit module balance in status 23 and the module balance plus accruals is over the minimum MF extraction criteria amount.

(26) This is a debit module balance in status 19, 20, 21, 22, 24, 26, 54, 56, 58 or 60, the module is 53'd with closing code 09 and the module balance plus accruals is over the minimum MF extraction criteria amount.

(27) The module is in status 12, the module is not 53'd with status date after 1/1/71 and accruals are over the minimum NF extraction criteria amount.

(28) The module status is 12, the module is 53'd with closing code 09 and accruals are over the minimum MF extraction criteria amount.

(29) A debit transaction or credit reversal posts to a module this cycle containing a settled return (except on a civil penalty module—MFT 55), and the resulting balance (tax plus penalty plus unpaid assessed interest) is over the minimum MF extraction criteria amount.

(30) The module contains a settled return (except on a civil penalty module—MFT 55), at least one CSED is unexpired, the module is in status 12, 19, 20, 21, 22, 23, 24, 54, 56, 58, or 60, the module has been 53'd and the closing code is 01–08 or 10–39.

(31) The account is a resequenced account (either resequenced from another account this cycle or another account number has merged into it this cycle) and account is on IDRS.

(32) A TC 420, 421, or 30X posts to this module in the current cycle.

(33) One of the following conditions occurs in a tax module containing an unreversed TC 420 or 424:

1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2. A TC 34X, 640, 470 or 480 hold goes into effect or is released.

3. A TC 17X with a significant amount posts in the current cycle.

4. An amended/duplicate return hold goes into effect or is released.

5. A new IRA indicator posts to the IMF.

6. A TC 918 or 919 posts to the entity, a TC 916 or 917 posts to the module, or a change occurs in the entity refund schemes indicator.

7. A TC 670 posts or is reversed.

8. A TC 520 (closing code 85 or 88) hold goes into effect or is released.

9. A new SSN posts.

10. The ASED is updated.

11. A TC 960, 961 or 962 posts to the tax module.

12. A TC 29X or TC 400 posts in the current cycle.

13. The Entity Combat Zone freeze was set or released in the current year. Check CC IMFOLE on Line 11 for the Combat indicator. Indicator "1" indicates the Combat Zone is set and -C freeze is active/turned on (restricts assessment and collection of any tax). Indicator "2" indicates the Combat Zone is released and -C freeze is inactive/turned off (the assessment and collection of any tax may resume using normal procedures).

14. The Status 26 indicator is updated in the current cycle.

15. The 53 Hold indicator is updated in the current cycle.

16. A TC 971 AC 72 posts this cycle.

17. Spouse's SSN is updated.

18. The Disaster indicator is updated in the current cycle.

19. The 480 Indicator has been turned off in the current cycle.

20. The OIC Acceptance Year equals FFFF.

(34) A TC 429 from a Campus posts this cycle for this module.

(35) The G freeze, 47 hold is being released this cycle and the module is already on IDRS.

(36) The 130 freeze (left V) is being released this cycle and the module is already on IDRS.

(37) A TC 582 or TC 583 transaction is being received this cycle.

(38) A transaction posts to the tax module in the current cycle and the module is already on IDRS.

(39) The bankruptcy freeze (right V) is being released this cycle and the module is already on IDRS.

(40) There is a current cycle status change in the module and the module is already on IDRS.

(41) The offset overflow freeze (left C) is being released this cycle and the module is already on IDRS.

(42) The offset in/expired module freeze (left A) is being released this cycle and the module is already on IDRS.

(43) The erroneous refund hold (TC 844) is being released this cycle and the module is already on IDRS. The IRS litigation freeze (TC 520) is being released this cycle and the module is already on IDRS.

(44) The module is in status 02 and another module is not in status 02 with a status indicator of 2 and there is not a status 02B in the module.

(45) The refund scheme freeze (Z-) is being released this cycle and the module is already on IDRS.

(46) A TC 150 posts to the tax module in the current cycle and the current cycle is 150 days past RDD.

(47) The backup withholding indicator is being updated in current cycle and the module is on IDRS.

(48) A TC 924 with reference number 180 posts in the current cycle and the module is on IDRS.

(49) The spousal offset freeze (D-) is being released this cycle and the module its on IDRS.

(50) A TC 162 posts to the tax module in the current cycle.

(51) A Filing Status Code was updated this cycle by a doc. code 63 transaction and the module is on IDRS.

(52) The TC 480 or TC 780 freeze (-Y) is released this cycle and the module is already on IDRS.

(53) The Entity Combat Zone Freeze (-C) was turned on or off in the current cycle or the Entry/Departure date was corrected and the module is on IDRS. Check CC IMFOLE on Line 11 for the Combat indicator. Indicator "1" indicates the Combat Zone is set and -C freeze is active/turned on (restricts assessment and collection of any tax). Indicator "2" indicates the Combat Zone is released and -C freeze is inactive/turned off (the assessment and collection of any tax may resume using normal procedures).

(54) Whether a module meets the TIF extraction criteria above or not, analyze for the following conditions for AUR extraction. Those that meet both TIF and AUR extraction are extracted to both files. Those only meeting the criteria below are extracted to the AUR file only. Determine which SC to extract the update for based on the DLN FLC in the TC 922.

1. A TC 922 with a process code equal to 03 or 06 in the first position and a DLN FLC for an AUR SC posts in the current cycle.

2. A TC 922 updates the process code in the current cycle and the code in the first position is equal to 03 or 06 and the DLN FLC is for an AUR SC.

Note: Do not extract AUR updates after the process code is updated to 20–29, 35–39, 40–49, 50–53, 62–69, 70–74, 80, 82–89, or 90–93.

(55) The Federal Employee Indicator is on.

(56) Open TDA shows at least one tax module status 60 and current year tax module has a credit balance.

(57) The imminent or latest CSED has been updated this cycle.

(58) EIC Indicator has been updated this cycle.

(59) The Disaster Indicator has been updated this cycle.

(60) A TC 694 or TC 695 has posted in the current cycle in a Civil Penalty Module.

(61) A Master File recovery is occurring in the account and the module is on IDRS.

(62) A TC 971 Action Code 86 or 87 posts in the current cycle and the account is on IDRS.

(63) The IDRS Tax Module Extract Indicator is set and the account is marked as being on IDRS.

(64) A TC537 posted in the current cycle and the account is marked as being on IDRS.

(65) Extract all modules if a 6X indicator has been updated this cycle. The IDRS Entity Extract indicator will be set to a 4.

(66) Extract the module if a CADE TC 001 Blocked 999 and an IDRS Tax Module TC with a DLN Control day of >400 and <767 post in the current cycle.

(67) Extract the module in the cycle a TC 971 AC 043 posts.

(1) Retention on the TIF is governed by the principle that a module should be retained as long as any one of a specified set of criteria is met. If a module is being kept on the file because of one of these reasons and a time is reached when that reason no longer applies, the module is then analyzed to see if any of the other specified criteria apply. If one of the criteria does apply, the module is retained. Whenever the module does not meet any retention criteria whatsoever, it is dropped from the file and a generated TC 901 is sent to ECC, Enterprise Computing Center to inform the Master File that the module is no longer on the TIF.

(1) A module is part of an account that is in process of resequencing or merging at the Master File. (The module will stay on until the resequence or merge is completed or until the Master File reports a no-merge condition.)

(2) One of the freeze conditions or hold conditions that cause extraction from the Master File is present in the module. (The module will stay on until the freeze or hold is released at the Master File.)

(3) A tax module is in debit balance and has no settled return. (The module will stay on until the balance is non-debit or a return settles, or for 7 cycles, whichever is shorter.) (IMF, BMF only).

(4) A tax module is in Master File status 13, 14, 19, 20, 21 and there is a Service Center status. (The module will stay on until the status changes at the Master File, or the module goes to IDRS status 23 or 53. (IMF, BMF only.)

(5) A tax module is in Master File status 22, 24, 26, 54, 56, 58 or 60. (The module will stay on until the Master file status changes.)

(6) One of the following conditions is met. These tax modules will remain on the TIF for one cycle (IMF and BMF only).

1. A tax module is in MF status 23 with debit balance including accruals over minimum balance extraction amount.

2. A tax module is 53'd with closing code 09 and debit balance including accruals over Minimum balance extraction amount.

3. A tax module is in MF status 12 with accruals over minimum balance extraction amount and there is another tax module in TDA status or to which a debit balance transaction posted this cycle that made balance plus accruals debit over minimum balance extraction amount.

(7) A tax module contains a settled return and a credit balance (IMF-Left-Hand V freeze also) or the module contains a Left-Hand S or Right-hand A freeze. (The module will stay on until the balance becomes zero or debit or for 30 cycles, whichever is shorter.) (IMF, BMF only.)

(8) A tax module was extracted because the following transaction posted: TC's 28X, 70X, 73X, 75X, 79X, 82X (except 826), certain 846, certain 85X (except 856), 87X, 89X. The module will stay on the TIF for four weeks.

(9) Extraction of the module was requested by a TC902 from TIF Daily processing or TIF Recovery program (UTL95). (The module will stay on for one week).

(10) A module was extracted because a transaction unposted. (The module will stay on for one week. If the unpostable transaction appends to the IDRS module, which it should, the module will stay on until the transaction posts or is deleted from processing.) (IMF, BMF, EPMF only.)

(11) A module was extracted because of the issuance of one of the notices specified above under Master File Extraction Criteria and the module is not in a Master File notice status. (The module will stay on three weeks (IMF) and 8 weeks (BMF)).

(12) An account is established within the last 30 cycles and the ERAS-NOTICE-CD is A, B, J, K, L, M, P or T. (BMF/EPMF)

(13) A tax module is in IDRS status 53 and there is another non-53'd tax module being retained. The tax module will be retained on IDRS until the other modules drop or its own status changes.

(14) Extraction of the module was requested by a TC 902 from IDRS terminal input. Includes, but not limited to, inputs from MFREQ(D) or downloads from CFOL with MFREQ(C) or RECON. (Early analysis possible. The module will stay on for one to three weeks.)

(15) A tax module is in credit balance with no return and another module has an unpostable 05. (The module will stay on for five weeks.) (BMF only.)

(16) A tax module at the Master File has an unreversed TC 914 or 916 appended or entity has unreversed TC 918, or taxpayer has been determined to be ‘potentially dangerous’.

(17) A CP 71 or CP 71A has been issued on the module. (The module will stay on until there is activity in the account or until 6 weeks after the notice was issued.) (IMF only)

(18) A tax module is in IDRS status 23 and a TC 670 has appended. (The module will stay on 2 weeks after the cycle the last TC 670 appended.)

(19) A tax module has changed to IDRS status 12 from an IDRS status greater than 12. (The module will stay on for 2 weeks after the change to status 12). (IMF/BMF)

(20) A tax module is in IDRS status 19, 20, 21, 22, 24, 26, 41–44, 46–51, 54, 56, 58, 60, 61, 63, 64, 71, 72, 76, 77, or 89. The module will stay on until the status changes to a status not in the list.

(21) A tax module has an open TDI, pending TDI, TDI temporarily suspended, or is in an open TDI Notice Status (The module will stay on until the TDI is closed.)

(22) A tax module is in Master File Status 23 and has an open TDI. The module has not gone to the Queue.

(23) A tax module in TDI status is closed by a TC 598. The module will stay on 64 weeks from closure cycle.)

(24) A tax module in TDI status has been transferred to another Campus less than 4 weeks ago.

(25) A TDI module has closed. (IMF modules will stay on 10 weeks from closure cycle. All other files, only three weeks.)

(26) A tax module contains a recall DI TC 590 for the secondary SSN account from an IMF TC 150 that was processed more than 150 days past the due date or that contained condition code F or T. (The module will remain 20 weeks from the transaction cycle.)

(27) A module is a dummy module. (It will stay on for three weeks after it was established.)

(28) A module is a memo module. (It will stay on for three weeks after the cycle it became a memo.)

(29) A TC904 appends to the entity or tax module in the last three cycles.

(30) The entity contains a TDA/TDI assignment that has been updated in the last week. (The entity will stay on for one week.)

(31) Entity or tax module contains a transaction in pending status.

(32) Entity or tax module contains an open control base, or a control base closed within last 3 weeks.

(33) Entity module, created by "IAPND", containing a significant PENDING-IAGRE-CD.

(34) Tax module contains an INNOCENT-SPOUSE-TRACKING-REC.

(35) Tax module contains a COLLECTION-DUE-TRACKING-REC.

(1) A module is extracted for IDRS because of a freeze condition. As long as the freeze condition exists the module will not be further analyzed on IDRS. When the freeze condition is released on the Master File, and Master File analysis determines that the module no longer meets any condition for which it is automatically extracted, the Master File will re-extract the module indicating this condition. When the module is updated on IDRS in this situation, IDRS analysis looks for other criteria such as pending transactions or open control bases. If IDRS analysis finds that there is an open control base in the module, it will retain the module until the control base is closed then re-analyze for other IDRS criteria. If none is found, the module is dropped.

(2) A module is extracted for IDRS because a transaction attempting to post to it went unpostable this cycle. IDRS will analyze this module every week until the unpostable is no longer on IDRS. When the unpostable is no longer on IDRS, analysis looks for criteria to retain the module. One criterion which it is likely to meet in this case is a corrected unpostable pending transaction. When the corrected unpostable transaction becomes a posted transaction, IDRS will reanalyze for other IDRS criteria. If none is found, the module is dropped.

(3) A module is extracted because it was requested from a Campus. The requester has three weeks to do something to hold the module, e.g. establish an open control base. After three weeks, the module will be analyzed for IDRS criteria and dropped if none is found.

(1) An entity added to the TIF by Command Code ESIGN will be retained until either the entity is established on a Master file or meets aging criteria. When an entity meets the aging criteria, it is removed from the TIF and placed on an age listing during the weekly Name Search Facility (NSF) analysis. The aging factor for ERAS-NOTICE-CD A, B, J, K, L, M, P, or T is 30 cycles.

(1) Cases may be controlled on IDRS in several ways. Under IDRS, any type of case may be controlled. Therefore a separate adjustment control file is not necessary, except for use in special projects such as Civil Service Retirement Claims.

(2) Adjustment Control Records (ACR's) are produced for certain Master File recognized adjustment cases; for example, CP 36 and CP 193 cases. The ACR control number is used as the activity code of the control base when a new control is being established.

(3) Examiners may control a case by entering the CC ACTON or DOALL into IDRS. See IRM 2.3 for specific details.

(4) A refund deletion made through IDRS always generates an open control base regardless of the presence or status of any existing control bases.

(5) A DP Adjustment, credit transfer, CHK64 (Release of Undelivered Refund Check) or IDRS generated refunds (by CC RFUND) made through IDRS generates a closed control base if none of the following conditions exists.

1. A closed base is present with today's action date and the terminal operator's assignee number.

2. Open control base(s) assigned to the terminal operator in Status S, A, B, or M; or open control base assigned to another employee in S, A, or M Status.

3. For ADJ54 and a 2 sided Credit Transfer Command Code (DRT24, DRT48, FRM34), no open base exists on the module for that employee, and a status other than C is input with the command code.

(6) Examiners may control a case by entering the control information after inputting a letter through IDRS; see the Correspondence Section in IRM 2.3.

(7) Use CC ACTON to establish an open control base in the following situations.

1. Any case where resolution action cannot be taken immediately.

2. Any case where multiple actions are to be performed such as adjustments, credit transfers, IDRS generated refunds, release of undelivered refund checks, or refund deletions. After all transactions have been entered, use CC ACTON to put the case in its proper status, if applicable. Any case which is non-workable but must be monitored, use Status Code B. This case control does not prohibit other examiners from on-line input.

(8) The concept of one taxpayer's account being worked on by one examiner should be followed in IDRS. Whenever an examiner wants to control a case and control to another employee already exists in the module or account, contact must be made with the other employee (Command code FIEMP may be used to find an employee). If CC TXMOD or SUMRY indicates ENTITY case control, the entire account is controlled. These cases would then normally be associated and controlled to one of the examiners. Cases indicating an unreversed TC 420 will be worked in accordance with IRM 21.7. The exception to this concept is case control with Status Code B which allows more than one examiner to have open case controls.

(9) An open control will cause a module to remain on IDRS indefinitely. After the control is closed, if no other criteria exists for retaining a module, it will drop off IDRS within three weeks.

(10) Reopen and work to resolution cases not passing quality review. Re-establish the case with ACTON using a "C#", activity code "CnERRCLSD", status "A", plus the original IRS received date, assignee number, and category. Also use activity code "CnERRCLSD" for any other occasion when a case control must be reactivated.

(1) Up to 1225 inventory reports and 1225 overage listings can be produced upon request each week. These requested reports may be tailored for specific needs.

1. Parameters which can be controlled on requested inventory reports are employee number range, column aging factors, combining several categories unto one, and MFT by category.

2. Parameters which can be controlled on overage listings are employee number range, category range, specific aging factor by category, and minimum age for inclusion of case on listing by category.

(2) Since many areas in the Campus can put cases under control, monitor inventory reports to assure that IDRS control capabilities are being used properly. Utilize overage listings for this purpose as necessary but be selective, especially in requesting overage listings which consume considerable print time during weekend processing.

(3) For many Campuses, reports and listings are requested through the Campus Liaison for IT. See IDRS Related COH for CCA32, for request input information.

(1) To re-assign an open control base from one assignee number using CC ACTON or CCASG (CCASG for cases opened by Master file Case Control File). Key in the 10-digit assignee number as explained in IRM 2.3. [see IDRS Related COH for CCA32].

(2) Some assignee numbers identify functional areas, units, holding files—thus representing workflow designations rather than individual employees. These non-employee assignee numbers are frequently distinguished by zeros in the last five digits of the employee number; however, numerics other than zero may also be used. Lists of such numbers appear from time to time in either Campus IDRS bulletins or the IDRS MESSG file.

(1) This section will provide information on the following items.

1. General information on IDRS Multiple Case Control Report

2. Procedures for IDRS Multiple Case Control Report

(1) This section will provide information on the following items.

1. New Category Codes

(1) Many transactions are input directly through IDRS.

(2) These include delinquency investigation transactions—DLN doc. codes 14 and 49; Area Office payments—doc. codes 18 and 28; credit transfers—doc. codes 24, 34, and 48; D.P. adjustments—doc. code 54; entity changes—doc. codes 04, 15, 50, 53, 63, 80 and 81; miscellaneous transactions—doc. codes 77 and 78; release of undelivered refund checks—doc. code 64; IDRS generated refund doc. code 45.

(3) When a transaction is input to IDRS, it appears immediately as a "pending" transaction and remains "pending" until after it posts to a Master File. It will then show as a posted transaction. The type of pending transaction is further defined by the Transaction Status Code, see IRM 2.3 and IRM 2.4 for specifics.

1. Area Office Payments, and various transactions batch uploaded from Integrated Collection System (ICS) and Inventory Delivery System (IDS) will not appear as pending transactions until the day following input. They are appended if the TIN is present on the TIF.

2. ESIGN data will be added to the Taxpayer Information File (TIF), Name Search Facility (NSF). TC 000 will be generated for BMF, and EPMF and TC 474 and 590 for BMF during the daily analysis of ESIGN input data and sent directly to the TIF.

(4) If an employee is not subject to Quality Review on IDRS transactions, the transactions will be processed, and be ready for inclusion on a tape for posting to the TIF at end of day.

(5) If an employee is subject to Quality Review on IDRS transactions, the transactions will be processed at the end of the day in which the review took place, or at the end of the second day following the day of input if no review is made.

(6) Transactions subject to quality review on IDRS are those with document codes 04, 15, 24, 34, 47, 48, 50, 53, 54, 63, 64, 77, 78, 80, 81, and IDRS Check Claims (CC CHKCL). Unidentified Remittance, Dishonored Check or IDRS Generated Refund (CC RFUND) applications are not subject to IDRS quality review, but should be reviewed as currently specified.

(7) For specifics on inputting and reviewing transactions on IDRS, see IRM 2.3 and IRM 2.4.

(8) Source Document Folders—Do not send anything to files unless it must be retained as a backup or source document. For source documents which must be preserved and which relate to IDRS-input transactions, set up daily source document folders by employee:

1. Cases, including related source documents, that result in document codes 45, 47, 53 (certain TC09X only), 54, 63 (TC070 only), 64 or 78.

2. Cases, including related source documents, that result in an application from the Unidentified Remittance File (URF) — CC URAPL.

3. Cases, including related source documents, that result in document code 78 input.

4. All others.

(9) The different types of work should be retained in separate uniform folders as prescribed for the files [see IRM 1.15.2]. The type of work, the employee number and the input date should be noted in the left margin cut-out on each folder using the appropriate color of ink for the year as described in IRM 3.10.72.

1. For document codes 45, 54 and 64 transactions, the input sequence number must be noted on each case.

2. For URAPL transactions, the UR control number, UR name and original UR amount should be noted on each case.

3. Additional information that may be desirable to note or underline on each case would be TIN, name control, MFT, module period and—for source documents in the "all other" folder—doc. code of the input transaction.

4. As it is necessary for files to know input date and employee number for all document codes 45, 47, 54, 64 and 78 transactions that are input through IDRS, it may be necessary to put that information on each case rather than just on the folder.

(10) URAPL cases should be forwarded to the Unidentified Remittance Unit through quality review. Document Code 45 cases (CC RFUND) should be retained in the functional area until the list of refunds has been certified. Once certified, send original (yellow) copy of Form 5792, Request for IGR, to Files Management for association with Form 5147, IDRS Transaction Record, and filing. NMF Document Code 45 Forms 5147 with associated case files should be forwarded for input to RACS. The source documents should be kept in sequence number order within employee number order. There is no sequence number for Document Code 78.

(11) Transactions that are input through IDRS will receive a complete DLN and be printed out after any quality review processing has taken place. Source documents will be associated with Document Codes 45, 54, 64, and 78 transactions. For other transactions they will be maintained in files in their employee input folders as provided in IRM 3.5.61.

(12) The "remarks" section of the input formats for DP adjustments, FRM77/CRMNL, entity changes and credit transfers, must be used to clearly describe the action taken. If terminal operator (e.g., RTO) is not the originator, enter the originator's employee no. Include " SD" (source document) or "NSD" (no source document) in the remarks section. ADJ54 screen now has required input. " Source Document Attached?" Valid responses are "Y", "N" or "R". The notations have two uses:

1. To aid research if a subsequent problem develops.

2. To assist Files Management in associating any source documents with doc. codes 45, 47, 54, 64 and 78 transaction records.

(1) The need for cycling of transactions may be reduced through IDRS. Most transactions post to the Master File in transaction code order. Exceptions are: all entity addressing transactions including TC's 91X post before tax module transactions; TC 150 on BMF posts last. In those instances where cycling was done solely to be sure that a lower numbered transaction code be at the Master File in the same cycle or earlier than a later numbered transaction code, the transactions may be input to IDRS at the same time.

(1) An address change (TC 014) and a reduction in tax (TC 291) need to be input.

(2) A reduction in tax (TC 291) and then a transfer of that credit, e.g., (TC 820–700) need to be input.

(3) A payment, e.g., (TC 670) or a credit, e.g., (TC 700/820) need to be applied, and then an increase in tax (TC 290) is to be made.

(4) A consolidation of accounts such as from a "no merge" situation, results in needing to zero out the "FROM" module with TC 291, transfer credits to the "TO" module, and assessing tax with TC 290 on the "TO" module. These transactions may all be input to the module(s) involved through IDRS in the same cycle. Care should be taken through analysis of the module(s) on IDRS that the transactions will indeed post to the Master File and not create an unpostable. Use of TC 570 for freeze purposes, where applicable, may be used especially when the actual module is not on IDRS. Multiple TC's may come in on a single doc code 54 transaction. These will all post to the Master File as a group in input order and they will be sorted as coming in under a TC 290 even if the input TC was not a TC 290. Where cycling is still required, or where there is some doubt whether to cycle or not, the transactions may be cycled with the posting delay code. In this way, all actions on a case may be completed by the examiner at the same time.

(1) Run TRS04W generates Diagnostic transcripts from data extracted by the Diagnostic Analysis portion of WTU29/49/69. While the capability to suppress this analysis exists, it is strongly recommended that this not be done. If local management or operations staffs intend to override this recommendation, they should contact Headquarters.

(2) Diagnostic transcripts are produced weekly for those entity or tax modules containing pre-determined criteria which might indicate incorrect processing. Their primary purpose is to identify systemic, programming or computer operations problems. Secondarily, they may disclose operational problems in other functional areas.

(3) The IDRS User Support Staff must analyze these transcripts and sort them according to problem areas revealed and by functional areas responsible for resolving the problems identified. User Support Staff analyzing these transcripts must be alert to procedural or systemic problems revealed. After appropriate review, research and documentation, these problems, or suspected problems, should be forwarded to the office responsible for their resolution (local CSA staff, operational function or Headquarters IDRS computer specialists, etc.).

(4) After analysis by the IDRS User Support Staff, referrals should be made to proper functional areas for corrective action (as described in 2.9.1.19.2). In some instances this action may be handled on a case-by-case basis whereas others may be processed as a "batch" operation. An example of the latter would be a block of TP transactions that did not follow expected procedures. Pending transactions can affect the module balance, so it is extremely critical that these transactions be corrected promptly.

(5) Diagnostic transcript controls from run TRS04W should be maintained by cycle of issuance. A record of volume and action taken should be maintained with the controls whenever new problems are detected and the volume of such problems is significant, or when the problem is of a continuing nature. As an example, 75 TP transactions in one cycle would be a sufficiently significant volume to warrant recordation. Likewise, a similar problem occurring on 10 tax modules each week would warrant recordation at the point the problem is identified as a continuing problem condition.

(6) DIAG-Q types 1-9, C, D, E, and S that meet specific TDA or TDI criteria are now routed to the WTU2923 file instead of the WTU2913 file that is processed by TRS04W. The WTU2923 file is sent to a Desktop Integration (DI) process. The DI process sends DIAG-Q types 1-9 with –Y Freeze-CD’s to Memphis and Brookhaven campuses only, for further research. If the taxpayer's state is equal to "AK, AR, AL ,AZ, CO, FL, GA, HI, ID, KY, LA, MS, MT, NC, NV, NM, OK, OR, SC, TN,TX, UT, WA, WI OR WY" route the transcripts to MSC else route the transcripts to BSC.The DI process sends also the TDA transcripts to the Atlanta campus for further research and the TDI transcripts to the Fresno campus for further research.

(1) This section will provide information on the following items.

1. General information on DIAG-P Transcripts

2. Selection criteria for DIAG-P Transcripts

3. Procedures for disposition of DIAG-P Transcripts

(1) This section will provide information on the following items.

1. General information on DIAG-Q Transcripts

2. Type definitions of DIAG-Q Transcripts

3. Procedures for disposition of DIAG-Q Transcripts