3.12.37  IMF General Instructions (Cont. 1)

3.12.37.7  (01-01-2015)
Error/Reject Register Action Codes

  1. This subsection of the manual provides information on Error/Reject Register Action Codes.

  2. Information in this subsection includes the following:

    • Action Codes "2" through "7" and "9"

    • Invalid correction attempts

3.12.37.7.1  (01-01-2015)
Action Code "2"

  1. Action Code "2" is used to delete, reenter or renumber records on Service Center Control File (SCCF).

  2. Action Code "2" is entered to the left of Section 01 and must be accompanied by a Reject Disposition Code. ( See Figure 3.12.37-23) The valid Reject Disposition Codes are as follows:

    • 2–D—delete the document from the Reject inventory

    • 2–R—reenter the document with the current DLN

    • 2–N—renumber the document

  3. Be sure to maintain an audit trail of deleted documents. Notate on the register the reason for Action Code "2" .

  4. Action Code "2" is valid for IRP and Reject Register only.

  5. When Action Code "2" is used, no other Action Code is valid.

    Figure 3.12.37-23

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

3.12.37.7.2  (01-01-2015)
Action Code "3"

  1. Enter Action Code "3" to the left of Section 01 for any record that is unprocessable. ( See Figure 3.12.37-24)

  2. Some of the reasons for using Action Code "3" are:

    1. A return or other document with illegible or missing necessary data, which requires additional research or taxpayer or area office contact.

    2. A return/document that cannot be processed by the program under which it was blocked and must be processed with a DLN or Block Header for a different program.

    3. A return or other document that has data incorrectly transcribed in a field that cannot be changed by an Error Register Correction.

  3. Action Code "3" is valid for Error Registers only.

    Exception:

    IRP

  4. Attach a Correspondence Action Sheet or Reject Routing Slip to the document to explain the invalid condition or intended corrective action.

  5. Immediate action may be necessary to suppress generation of erroneous balance due or delinquency notices before rejecting a payment/delinquency return to be renumbered/reentered.

  6. When Action Code "3" is used, no other Action Code is valid.

    Figure 3.12.37-24

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

3.12.37.7.3  (01-01-2015)
Action Code "4"

  1. Action Code "4" is used to delete a section from a register. (See Figure 3.12.37-25)

  2. This code is valid for any section that is considered optional by the return program. Section 01 can never be deleted.

  3. This code should not be used to delete a section identified as "missing" (a single asterisk in front of the section number). A missing section will be dropped automatically if no data is entered in it.

    Figure 3.12.37-25

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

3.12.37.7.4  (01-01-2015)
Action Code "5"

  1. Action Code "5" is used to add a section to a record on the register.

  2. Action Code "5" is followed by the number of the section being added and the alpha field designator(s) and the data for the section being added. (See Figure 3.12.37-26)

  3. This code is invalid for a section already on the register or a section that is not valid for the type of document being processed.

  4. When adding sections, be sure that all corrections are entered in the proper sequence.

    1. If the document also requires Action Code "6" corrections, sections must be added in the proper sequence with respect to other corrected sections.

    2. If the document requires no other corrections, sections may be added at any place on the record, provided that each new section is in the proper sequence.

    Figure 3.12.37-26

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

3.12.37.7.5  (01-01-2015)
Action Code "6"

  1. Action Code "6" is used to change a field or fields of a section within the Error Record.

    1. The computer identifies each field of a section with an Alpha Field Designation and prints the Alpha Field Designation before the field on the Error Register.

    2. To correct a field, the incorrect field data must be lined out and the correct data entered above. Any number of fields may be changed during one correction cycle.

    3. Enter Action Code "6" immediately to the left of the Section Number for the section being changed. (See Figure 3.12.37-27 )

  2. When a fixed-length field must be blanked out or left partially blank, special procedures are required.

    1. If the fixed field requires leading blanks, always enter the number of blanks encircled, followed by the corrected data.

    2. If the fixed field requires blanks after the data or if the entire field must be blanked, the spaces must be accounted for only if another field is being corrected later in the section.

  3. Action Code "6" cannot be used to add, delete, or change the remittance amount on an error register. If the remittance is incorrect, use Action Code "3" .

    Figure 3.12.37-27

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

3.12.37.7.6  (01-01-2015)
Action Code "7"

  1. Action Code "7" is used to indicate that the data on the error register is correct and that no action is necessary.

  2. Use Action Code "7" to clear an error record that is on the register for a one time only validity condition. ( See Figure 3.12.37-28)

    Note:

    Action Code "7" must not be used unless all other information on the register is correct.

  3. Action Code "7" will not clear a math error condition even if the taxpayer was correct. Instead, use Action Code "0" .

  4. When Action Code "7" is used, no other Action Code is valid.

    Figure 3.12.37-28

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

3.12.37.7.7  (01-01-2015)
Action Code "9"

  1. Use Action Code "9" to re-reject a loop register for correspondence or other suspense action. (See Figure 3.12.37-29)

  2. This code is used to prevent a reject loop record from reprinting each time the loop is run, if the record is not ready for correction.

  3. Action Code "9" is to be used for reject loop only. Do not use for raw rejects or error registers.

  4. When Action Code "9" is used, no other Action Code is valid. See Exhibit 3.12.37-2 for a listing of the Use of Action Codes on Error/Reject Registers.

    Figure 3.12.37-29

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

3.12.37.7.8  (01-01-2015)
Invalid Correction Attempts

  1. Each correction attempt is subject to tests which ensure proper correction.

    1. If a correction attempt fails, the record will reappear on the Error Register with Error Reason Code "AA" .

    2. When Error Reason Code "AA" is present, correct the error register as if no other correction attempt has been made.

  2. For a given record, any correction that precedes the invalid correction attempt will print out as a corrected field.

    1. Any other corrections made after an invalid correction will not printout, an Error Reason Code "AA" will be present.

      Example:

      Fields A, B, and C are to be corrected in a section and C was transcribed "Z" . "Z" is an invalid Alpha Field Designation for the Section.

    2. The Error Register will have the corrected Fields A and B printed out, but Field C will still be incorrect.

3.12.37.7.8.1  (01-01-2015)
Action Codes

  1. Action Codes "0" , "1" , "2" , "3" , and "7" are considered invalid correction attempts under the following conditions:

    1. The Correction Record contains other than the Error Sequence Number, Section Number 01, and Error Action Code, the TPNC (for Action Code 1 only) or Reject Disposition Code (Action Code 2 only).

    2. There is more than one section in the Correction Record for an Error Sequence Number.

  2. Action Code "4" is considered an invalid correction attempt under the following conditions:

    1. An attempt is made to delete any section with a single asterisk (*) before the Section Number.

    2. An attempt is made to delete a section of an Error Record when the Error Record Section is not on the Error Tape.

    3. Attempts are made to delete the only section, Section Number 01, for a record.

  3. Action Code "5" is considered an invalid correction attempt under the following conditions:

    1. The Alpha Field Designators are not in alphabetic sequence

    2. An attempt is made to add a section already in the error record

    3. An attempt is made to add a section that has an invalid Section Number

    4. An attempt is made to add a section with a field that has an Alpha Field Designation not possible for that section

  4. Action Code "6" is considered an invalid correction attempt under the following conditions:

    1. The Alpha Field Designators are not in alphabetic sequence.

    2. An attempt is made to change a field of a section with an invalid Section Number or invalid field breaker.

    3. An attempt is made to change a field of a section which is not on the Error Tape.

    4. An attempt is made to change a field with an Alpha Field Designation not possible for that section.

3.12.37.8  (01-01-2015)
Error Resolution System (ERS)

  1. This subsection of the manual provides information about the Error Resolution System (ERS).

  2. Information in this subsection includes the following:

    • General concepts

    • General correction procedures

    • Use of terminals

    • System capacity

3.12.37.8.1  (01-01-2015)
General Concepts

  1. ERS is a real—time computer system used to correct errors detected during Generalized Mainline Framework (GMF) processing.

  2. All errors for the 1040 series returns are corrected on the terminal using ERS.

  3. All other returns and documents that are processed through mainline Submission Processing Campus programs are corrected according to Service Center Replacement System (SCRS) error and reject register procedures.

  4. All ERS records are controlled by DLN.

  5. ERS records are divided into three inventories:

    1. The ERS Error Inventory consists of records that have failed specific validity, consistency, or math checks. Records are accessed by block DLN and remain in the complete block while being worked. The ERS record remains in the Error Inventory until all corrections are made. Any error record that cannot be corrected is suspended.

    2. The ERS Workable Suspense Inventory contains the Rejects inventory. These records are accessed by the complete 14-digit DLNs, as the documents have been pulled from the original block and are no longer identified with block processing.

    3. The ERS Unworkable Suspense Inventory consists of the reject items that are being held in suspense, pending a reply to correspondence or the return of a document from elsewhere in the campus. These records are not included in the on-line file and cannot be worked until they have been activated in overnight batch processing.

3.12.37.8.2  (01-01-2015)
General Correction Procedures

  1. ERS Tax Examiners (TE) access error blocks using CC GTREC with the block DLN.

    1. The first error document within the block displays. It displays with the highest priority error first.

    2. When the correction is made and transmitted for that error, the document is validity checked.

    3. Each error record must be completed before the next error record in the block can generate.

    4. When the last error in the block has been corrected, the screen message indicates that the error block is completed and the tax examiner enters another DLN.

  2. Any document that cannot be corrected is suspended with a three-digit action code, which identifies the reason the return was unprocessable. The record is then controlled on either the Workable or Unworkable Suspense Inventory, depending on the action code used.

  3. If a record needs to be reworked, it can be retrieved at any time on the same day using CC GTRECW. See Current Year Job Aid 2515–015 for details.

  4. All corrected records are transmitted to the Enterprise Computing Center at Martinsburg (ECC-MTB), also known as "good tape" .

  5. ERS listings and charge-outs should be received and associated timely. This process should be well underway each morning before the real-time ERS system is available.

  6. All ERS functions should use the system as designed by the following:

    1. Using all appropriate control listings.

    2. Working older errors and Workable Suspense cases first.

    3. Resolving or suspending all error records within three days.

    4. Resolving or suspending all Workable Suspense records within five days.

  7. In order to prevent workable inventory being sent to files in error, all 1340's should be checked for "Error Block Completed" prior to releasing block of work to files.

3.12.37.8.3  (01-01-2015)
Use of Terminals

  1. ERS uses the same terminals as IDRS and each tax examiner can easily switch from ERS to IDRS Command Codes.

  2. Each TE should learn and use the IDRS Command Codes that are provided in their operator profile. See IRMs 2.3 (IDRS TERMINAL RESPONSES) and 2.4 (IDRS TERMINAL INPUT) for further instructions.

  3. The ERS and IDRS computer systems are separate and will not necessarily be operating during the same hours. If a TE needs to research IDRS while the IDRS system is down, suspend the record so the research can be completed at a later time.

3.12.37.8.3.1  (01-01-2015)
IDRS Changes and Posting Time Frames Due to CADE2

  1. The Customer Account Data Engine (CADE) 2 Program Office in Headquarters is charged with the primary goal to implement a single, modernized programming solution which provides daily processing of taxpayer accounts.

  2. The CADE 2 solution is comprised of several components, to modernize the IRS to a daily processing environment with several Transition States.

  3. The new cycles are:

    1. Campus Cycle – Thursday – Wednesday

    2. Master File Processing – Friday – Thursday

    3. Notice Review Saturday – Monday (8+ days)

    4. Unpostables – New available Tuesday; Closing Tuesday

      Note:

      New Cycles are not limited to IMF Sites. BMF sites will also have the new campus cycle.

  4. Refunds for IMF accounts will be accelerated to provide refunds to taxpayers quicker.

    1. Direct deposit refunds will be issued in 4 business days from posting.

    2. Paper check refunds will be issued in 6 business days from posting.

  5. IMF transactions posting time frames are outlined as follows:

    1. Daily transactions directed to a daily account are expected to post daily with daily processing. Transactions will be viewable using CFOL command codes the second day after campus input. Transactions will be viewable on IDRS command codes the third day after campus input.

    2. Weekly transactions directed to a daily account are expected to post with the weekly processing run on Thursday and may result in the account type changing to Weekly.

    3. Daily and Weekly transactions directed to a Weekly account are expected to post with the weekly processing on Thursday.

    4. The following transactions will post daily on weekly accounts: Name change, Address change, Disasters designations, Combat Zone, ID Theft and certain MFT 29 and 30 payments (TCs 430, 610, 660 and 670).

  6. IMF cycle posting dates will reflect a format of YYYYCCDD. YYYY will indicate the year. CC will indicate the posting cycle. for IMF transactions, the following values for DD are defined:

    1. 01 = Friday

    2. 02 = Monday

    3. 03 = Tuesday

    4. 04 = Wednesday

    5. 05 = Thursday

      Note:

      BMF cycle posting dates on BMFOL will continue to reflect YYYYCC. YYYY will indicate the year. CC will indicate the posting cycle. BMF cycle posting dates in TXMOD will reflect a format of YYYYCCDD. The DD value will be 08.

3.12.37.8.4  (01-01-2015)
Error Resolution System Capacity

  1. The real-time portion of the Error Resolution System has a capacity of approximately 250,000 Form 1040 records per campus. The capacity may be set higher as individual campuses deem necessary.

    1. Up to 30,000 records may be retained on the Quality Review File, so the effective capacity for real-time planning is 250,000 records.

    2. The ERS programs will run more efficiently with fewer records on the file. If the system approaches capacity, it may be difficult to have ERS real-time available by the beginning of the shift the next day because the nightly update may not have been completed.

    3. Although the ERS database can hold several days of inventory, the campuses should strive to keep each Master File's inventory that is older than Day 3 at less than one percent (5%) of that Master File's total inventory (e.g., if the sum of IMF ERS cases from the ERS-13-41 Report is 100,000 cases, that means inventory older than Day 3 should not be 5,000 or more).

  2. An ERS inventory threshold has been established where up to 50,000 records are automatically added to the error file. This would happen only if the entire workable suspense file had been worked.

    1. An automatic "ORDER ALL RECORDS" will be made if the total of the unworked/unselected records is less than 70,000 records.

    2. If the total of the unworked/unselected records will exceed the threshold, only the two oldest workgroups will be added. (The system will keep a count of the two oldest workgroups.)

    3. If the addition of the two oldest workgroups will exceed the threshold, only the oldest workgroup will be added. If the oldest workgroup will exceed the threshold, only the predetermined program (43110) will be added automatically.

    4. No inventory will be automatically added to the system if the threshold will be exceeded unless a selection is made.

  3. The Input Correction Operation has the ability to select any or all the unselected records that are available. However, if the total workable inventory (error, suspense and quality review) is permitted to exceed capacity, the excess will be placed in overflow status.

    1. Because the ERS file is maintained in DLN sequence, the records with the highest DLNs, regardless of status or days in inventory, will move to the temporary "overflow" inventory.

    2. All overflow records will appear on the ERS control file with status 999.

    3. During the nightly update, if the size of the workable file has been reduced, overflow records will be automatically transferred back to the workable inventory.

    4. In overflow status, the record is not accessible with any command code or included on any inventory list. The record is available only for research on the ERS control file with CC ERINV.

  4. Although unselected records will be automatically added to the ERS error file, Input Correction Operation managers should monitor the inventory levels to ensure that adequate work will be available for the next day.

    1. After each GMF 27 and GMF 37 runs, records are loaded into the ERS01 file prior to selection for the real-time ERS system. Records are held in this file to be selected later for real-time. The Error Resolution Available Inventory Report will be received from the console printer in the Computer Operation. (See Figure 3.12.37-30)

    2. A separate printout, Error Resolution Unselected Records Inventory (ERS–03–40) is in the same format as the Available Records Inventory and lists all ERS records being held in the unselected inventory. In addition, the Error Resolution Selection Method (ERS–03–41) lists the records selected and the number of the employee making the selection. (See Figure 3.12.37-31 )

    Figure 3.12.37-30

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

    Figure 3.12.37-31

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

3.12.37.8.4.1  (01-01-2015)
Command Code ERVOL

  1. Command Code ERVOL may be used to estimate, view, and select records for ERS processing.

  2. Each day, compare the Grand Total Error Records count to the count from ERVOL 100 to estimate the unselected records that will be automatically added to ERS during nightly processing. Remember that Workable Suspense records are always added automatically to the real-time file and must be considered to the system capacity.

  3. If the automatic selection will exceed the established threshold, but it has been determined that all records should be added to ERS, enter CC ERVOL, space once and "ORDER ALL RECORDS" .

  4. If only a limited number of records should be added, enter CC ERVOL, space once, and "INVENTORY DISPLAY" .

3.12.37.8.4.1.1  (01-01-2015)
Viewing and Selecting Records From the Available Records Inventory

  1. There are two screens available for viewing and/or selecting. The two screens will display the program number and available inventory. Each page/screen will consist of the program number and available workable inventory as it appears in the data base.

  2. When ordering by program number from one page/screen only:

    1. "Page" (position cursor on line 24 position 47 and transmit) to needed page/screen.

    2. Select program number(s) and enter amount(s) to order or enter "ALL" to order all inventory of selected program(s).

    3. Transmit from line 23 or below last item on page/screen.

  3. When ordering from more than one page/screen:

    1. Enter "ERVOL INVENTORY DISPLAY" .

    2. Select program number(s) and enter amount(s) to order or enter "ALL" to order all inventory of selected program(s).

    3. Transmit from line 23 or below last item on page/screen.

    Note:

    ERVOL ORDER BY PROGRAM must appear at top left corner when ordering. This is issued by the program. Do not attempt to input this command or the program will abort.

  4. After records have been ordered, the first page/screen of the series will display the message "REQUEST COMPLETED-ORDER AS FOLLOWS:" This message will appear on all pages/screens. The page/screen will display all the program numbers along with the selected inventory ordered.

  5. Within each program, the oldest records are automatically selected. Within an inventory day, records are selected in DLN sequence up to the end of the batch in which the requested volume has been reached.

  6. Selections made using CC ERVOL can be changed at any time during the workday. If a selection is not made, the automatic selection procedures will be employed.

3.12.37.8.4.1.2  (01-01-2015)
Viewing and Selecting Records From the Error Resolution Unselected Records Inventory

  1. Selective ordering of documents is available as well as moving from screen 1 to screen 2.

    1. To view the documents on the second screen, position cursor on line 24, column 47 of screen 1 and transmit.

    2. To return to the first screen, position the cursor at the bottom of the screen 2 on line 24, column 47 and transmit.

  2. To order records from the first screen, enter number of documents requested in each program and transmit on line 23.

  3. Ordering from the second screen requires entering "ERVOL INVENTORY DISPLAY" going to the second page/screen and making individual selections.

  4. To selectively order records on the second screen, make your selections then position the cursor on any line below the last item on this screen and transmit.

  5. Within each program, the oldest records are automatically selected. Within an inventory day, records are selected in DLN sequence up to the end of the batch in which the requested volume has been reached.

  6. To request all documents for a program, enter "ALL" then transmit.

    Note:

    Command Code ERVOL will only order programs from the first screen and not the second screen unless you go back to the "ERVOL ORDER ALL RECORDS" and go to the second page and order "ALL" .

3.12.37.9  (01-01-2015)
Error Resolution System (ERS) Reports

  1. This subsection of the manual provides information about the ERS reports.

  2. Information in this subsection includes the following:

    • Error Resolution Inventory Control Report, ERS–17–47

    • Error Resolution Error Inventory Summary, ERS–13–41

    • Error Resolution Error Inventory, ERS–13–40

3.12.37.9.1  (01-01-2015)
Error Resolution Inventory Control Report, ERS–17–47

  1. The ERS Inventory Control Report, ERS–17–47, is a one-page summary of activity for each of the ERS files. (See Figure 3.12.37-32)

    1. This daily report is used to provide an overview of the ERS inventories.

    2. The report shows the number of records added and removed from each inventory daily. Items in the Quality Review File are included in the ending inventory counts for Errors and Workable Suspense.

  2. The primary purpose of this report is to provide Data Controls a simplified method of balancing the ERS to the SCCF.

    Figure 3.12.37-32

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

3.12.37.9.2  (01-01-2015)
Error Inventory Summary, ERS–13–41

  1. The ERS Error Inventory Summary Report, ERS-13-41, shows the volume of error records by ascending program number with a total for each Master File. Separate reports are produced by the number of working days the records remain unworked in the error inventory. This report is available daily. (See Figure 3.12.37-33)

    Figure 3.12.37-33

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The reports is used for management control of the inventory and work planning and control.

3.12.37.9.3  (01-01-2015)
Error Inventory, ERS–13–40

  1. The ERS Error Inventory Report, ERS-13-40, lists the error records by the number of days in working inventory with their Block DLN. This report is printed daily. Separate inventories are printed for:

    • Each Master File

    • Each Program number

  2. This report to assign work to tax examiners, to associate documents with error records, and to release documents from previous day's workload, retaining only those for the unworked records. (See Figure 3.12.37-34)

    Figure 3.12.37-34

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  3. Separate reports are printed showing the records in inventory by the number of working days the records have been in the inventory.

  4. Separate reports are printed for each Batch number, showing the following information items:

    • Block Control Number

    • Block DLN

    • Error Count for each Block

    • Control date of data entry through ISRP and GMF

    • Ascending DLN order within each Batch

    • Total error count for each Batch

  5. Separate reports are available for Blocks received from BOB Correction.

3.12.37.10  (01-01-2015)
Command Codes Used in the Error Resolution System (ERS)/Rejects/Suspense

  1. This subsection of the manual provides information about the Command Codes used in the Error Resolution (Rejects). Many of these command codes can also be accessed using the IAT tool.

  2. Information in this subsection includes the following:

    • General information

    • Command Codes SINON and SINOF

    • Command Code ACTON

    • Command Code ACTVT

    • Command Code ADD24/DRT24

    • Command Code ADD48/DRT48

    • Command Code ATINQ

    • Command Code BMFOL

    • Command Code CFINK

    • Command Code CMODE

    • Command Code COMPA

    • Command Code CRECT

    • Command Code DLSEC

    • Command Code DUPOL

    • Command Code ENMOD

    • Command Code ENREQ/INCHG

    • Command Code ENREQR/IRCHG

    • Command Code ERSSD

    • Command Code EREMP

    • Command Code ERINV

    • Command Code ERUTL

    • Command Code ERVOL

    • Command Code ESTAB

    • Command Code FFINQ

    • Command Code FINDE

    • Command Code FINDS

    • Command Code FRM49

    • Command Code GTREC

    • Command Code GTSEC

    • Command Code IMFOL

    • Command Code INOLE

    • Command Code INTST

    • Command Code IRPTR

    • Command Code LETER/LPAGE

    • Command Code LPAGD

    • Command Code MFREQ

    • Command Code MFTRA

    • Command Code NAMEE

    • Command Code NAMEI

    • Command Code NAMES

    • Command Code NOREF

    • Command Code NWDLN

    • Command Code QRSEL

    • Command Code REINF

    • Command Code REQ54/ADJ54

    • Command Code REQ77/FRM77

    • Command Code RFUND

    • Command Code RTFTP

    • Command Code RJECT

    • Command Code RTVUE

    • Command Code SCFTR

    • Command Code SFDISP

    • Command Code SSPND

    • Command Code STAUP

    • Command Code SUMRY

    • Command Code TERUP

    • Command Code TRDBV/TRDPG

    • Command Code TRPRT

    • Command Code TRERS

    • Command Code TXMOD

    • Command Code UPTIN

    • Command Code UPDIS/UPRES

    • Command Code UPCAS

    • Command Code URINQ

    • Command Code XSINQ

3.12.37.10.1  (01-01-2015)
General Information

  1. A five-character Command Code must be entered with every screen transmission. The Command Code tells the computer what action to perform. The instructions for using the following command codes are located in the Command Code section of Current Year Job Aid, 2515–015.

3.12.37.10.2  (01-01-2015)
Command Codes SINON and SINOF

  1. Command Code SINON is used to sign onto the computer. SINON will be used by all SCRS terminal users including ERS, GUF, and IDRS.

    Note:

    To ensure the accuracy of production reports, be sure to enter CC SINON if the system has been down.

  2. Command Code SINOF is used to sign off of the computer and is used by all SCRS terminal users, including ERS, GUF, and IDRS.

    Note:

    You must sign off the computer when leaving your terminal, or at the completion of your shift.

3.12.37.10.3  (01-01-2015)
Command Code ACTON

  1. Command Code ACTON is used to:

    1. Establish/update the status of an IDRS control base

    2. Establish/update a history item on ENMOD

    3. Establish/update a dummy account

    4. Change the name control on an account

3.12.37.10.4  (01-01-2015)
Command Code ACTVT

  1. Command Code ACTVT is used to transfer an Unworkable Suspense record to the Workable Suspense Inventory.

3.12.37.10.5  (01-01-2015)
Command Code ADD24/DRT24

  1. Command Code ADD24, which defaults to CC DRT24, is used to input credit transfers.

3.12.37.10.6  (01-01-2015)
Command Code ADD48/DRT48

  1. Command Code ADD48, which defaults to CC DRT48, is used to input credit transfers involving credit elects.

3.12.37.10.7  (01-01-2015)
Command Code ATINQ

  1. Command Code ATINQ is used to research the status of the Adoption Taxpayer Identification Number (ATIN) application. Use definer "T" and the Primary or Secondary SSN.

  2. Taxpayers are required to list a TIN for each adoptive dependent child to claim the exemption. These taxpayers can apply for an Adoption Taxpayer Identification Number (ATIN) for that child. Applicants must apply to the IRS using Form W–7A, Application for Taxpayer Identification Number for Pending U. S. Adoptions. A Form W-7A cannot be used if the child is not a U.S. citizen.

  3. The Austin Submission Processing Campus will process the Form W–7A application and will issue the ATIN upon receiving a complete signed application and valid documentation.

  4. The ATIN is a temporary number normally used as a dependent TIN only until the applicant obtains an SSN for their adoptive child. In only one circumstance can an ATIN be valid as a primary TIN. That is when a Form 8615 is attached.

  5. The taxpayer may not use the ATIN to qualify for EIC or ESP.

  6. ATINs are in the same format as an SSN or an ITIN. The format is 9XX-93-XXX.

    1. The ATIN must begin with the digit "9" .

    2. The fourth and fifth digit must be "93" .

    3. The last four digits must be assigned in ascending sequential order.

  7. If a dependent TIN is missing and a notation such as "ATIN applied for" is indicated in the dependent's social security number area of Form 1040/A, line 6c, then:

    1. Code & Edit will detach the Form W-7A and route it to Austin for processing. Code & Edit will leave a working trail notation, such as "Detached W-7A" in the margin.

    2. Research CC ATINQ to determine the status of the ATIN application. If ATINQ shows status "A" , enter the ATIN in the appropriate dependent TIN field. If ATINQ shows status "S" (ATIN Unit corresponding for additional info), "R" (Rejected), continue processing the return without the dependent TIN.

    3. If Error Code 010 generates, disallow the dependent exemption without a TIN.

    4. For refund returns only, input the STAT-DT on ATINQ into Field 02RPD.

  8. In addition to the dependency exemption, the ATIN also qualifies the taxpayer to claim the Adoption Credit, Child Tax Credit, and the Credit for Child and Dependent Care Expenses. However, the taxpayer is not entitled to EIC or ESP for any child using an ATIN.

  9. ATIN's status will be updated on the DM–1. When the filer notifies the IRS of the child's Social Security Number, the ATIN unit will input the Social Security Number into the database and it will delete the ATIN on the DM-1.

3.12.37.10.8  (01-01-2015)
Command Code BMFOL

  1. Command Code BMFOL is used to research nationwide entity and tax data posted to the Business Master File.

3.12.37.10.9  (01-01-2015)
Command Code CFINK

  1. Command Code CFINK is used to research the Centralized Authorization File (CAF) for Power of Attorney (POA).

3.12.37.10.10  (01-01-2015)
Command Code CMODE

  1. Command Code CMODE is used to access a database at another campus.

3.12.37.10.11  (01-01-2015)
Command Code COMPA

  1. Command Code COMPA is used to manually compute interest and certain penalties (e.g., Failure to Pay, Estimated Tax).

3.12.37.10.12  (01-01-2015)
Command Code CRECT

  1. Command Code CRECT is used to enter a correction.

  2. Command Code CRECT will be valid after an error has been displayed in response to the use of Command Codes GTREC or GTSEC.

3.12.37.10.13  (01-01-2015)
Command Code DLSEC

  1. Command Code DLSEC is used to delete a section from the data record.

    Note:

    Required sections cannot be deleted (i.e., 01, 02, 03, 04, 05).

3.12.37.10.14  (01-01-2015)
Command Code DUPOL

  1. Command Code DUPOL is used to access the duplicate TIN database and provides duplicate Social Security Number (SSN) data.

3.12.37.10.15  (01-01-2015)
Command Code ENMOD

  1. Command Code ENMOD is used to request the Entity Module for a specific SSN.

3.12.37.10.16  (01-01-2015)
Command Code ENREQ/INCHG

  1. Command Code ENREQ, which defaults to INCHG, is used in requesting an entity update of the Master File (i.e., TC 000, TC 013).

3.12.37.10.17  (01-01-2015)
Command Code ENREQR/IRCHG

  1. Command Code ENREQR, which defaults to IRCHG, is used to merge invalid and valid segments of Master File when the taxpayer has provided supporting documentation or an adequate explanation of name discrepancies (i.e., TC 016).

3.12.37.10.18  (01-01-2015)
Command Code EREMP

  1. Command Code EREMP is used to change records on the ERS Employee Name and Organization File.

3.12.37.10.19  (01-01-2015)
Command Code ERINV

  1. Command Code ERINV is used to research a DLN or TIN on the ERS Control File.

3.12.37.10.20  (01-01-2015)
Command Code ERSSD

  1. This command code is used by managers to sort ERS batches. It replaces the IAT ERS Batch Sorter Tool.

3.12.37.10.21  (01-01-2015)
Command Code ERUTL

  1. Command Code ERUTL is used to display several different areas in the ERS record for research purposes.

3.12.37.10.22  (01-01-2015)
Command Code ERVOL

  1. Command Code ERVOL is used to obtain the actual count of records in current Workable Inventory or the status of an error record.

3.12.37.10.23  (01-01-2015)
Command Code ESTAB

  1. Command Code ESTAB is used to request documents (i.e., returns) from files.

3.12.37.10.24  (01-01-2015)
Command Code FFINQ

  1. Command Code FFINQ is used to research for a Document Locator Number (DLN) using the SSN.

3.12.37.10.25  (01-01-2015)
Command Code FINDE

  1. Command Code FINDE is used to research for the business' name and address information, using the Employer Identification Number (EIN).

3.12.37.10.26  (01-01-2015)
Command Code FINDS

  1. Command Code FINDS is used to research for the taxpayer's name and address information, using the Social Security Number (SSN).

3.12.37.10.27  (01-01-2015)
Command Code FRM49

  1. Command Code FRM49 is used to input Transaction Code (TC) and Closing Code (cc) to finalize or satisfy the requirement for filing a tax return (i.e., TC 599 with CC 18 is used to indicate that the original return posted to the wrong module and will be reprocessed to the correct module).

3.12.37.10.28  (01-01-2015)
Command Code GTREC

  1. Command Code GTREC is used to access any of the following:

    1. First error record in an ERS error block.

    2. A specific record in the Workable Suspense Inventory.

    3. Re-display the previous uncorrected error display of a record after performing IDRS operations for the error.

    4. Previous uncorrected error display is desired.

3.12.37.10.29  (01-01-2015)
Command Code GTSEC

  1. Command Code GTSEC is used to obtain or enter a specific section on an ERS record.

3.12.37.10.30  (01-01-2015)
Command Code IMFOL

  1. Command Code IMFOL is used to research nationwide entity and tax data posted to the Individual Plans Master File. Command Code IMFOL is updated at least one day before Command Code TXMOD and may contain transactions that have not yet posted by IDRS to TXMOD.

3.12.37.10.31  (01-01-2015)
Command Code INOLE

  1. Command Code INOLE is used to access the National Account Profile (NAP) which contains selected entity information for all Master File (MF) accounts.

3.12.37.10.32  (01-01-2015)
Command Code INTST

  1. Command Code INTST is used to request accruals of interest and Federal Tax Deposit (FTD) penalty to a specific date.

3.12.37.10.33  (01-01-2015)
Command Code IRPTR

  1. Command Code IRPTR is used to request either online or hardcopy IRP transcripts from Information Returns Master File Processing (IRMF). This command code contains income information, entity data, cross reference information, and DOD/DOB information.

3.12.37.10.34  (01-01-2015)
Command Code LETER

  1. Command Code LETER is used to initiate taxpayer correspondence.

3.12.37.10.35  (01-01-2015)
Command Code LPAGD

  1. Command Code LPAGD is used to delete a letter.


More Internal Revenue Manual