2.3.29. Command Codes INTST, ICOMP, and COMPA

(1) Overview : This IRM provides a resource guide on how to use IDRS programs to calculate accrued interest and penalty for IMF/BMF modules to a date specified.

(2) Purpose : This IRM contains the resource guide for using IDRS command codes to calculate accrued interest and penalties.

(3) Audience : LB&I, SB/SE, TE/GE, W&I.

(4) Policy Owner : The Chief Information Officer (CIO) is responsible for overseeing all aspects of our systems that operate the nation’s tax infrastructure.

(5) Program Owner : Account Services, which is under the Director, Customer Service.

(6) Primary Stakeholders : Wage & Investment (W&I), Large Business and International (LB&I), Small Business Self-Employed (SB/SE), Tax Exempt and Government Entities (TE/GE), and Enterprise Operations (EOPS)

(7) Program Goals : This IRM provides the fundamental knowledge and procedural guidance for employees who work penalty and interest responses on IDRS. By following the processes and procedures provided by this IRM, employees will process balance due responses in a manner that follows IRS policy and procedures while promoting the best interests of the Government.

(1) CC INTST computes the correct outstanding balance, including interest and failure to pay accruals, to the date specified in the input of the command code.

(2) The module used in the computation must be present on IDRS, and, for a complete computation, must not contain any of the restrictive conditions specified in See Exhibit 2.3.29-3 (4), (5) and (6).

(3) CC INTSTN has the same capabilities as INTST. In addition, accruals will be computed to the input date plus 30 days, input date plus 45 days, and input date plus 60 days.

(4) CC INTSTA has the same capabilities as INTST. In addition, accruals will be computed to the input date plus 10 days, 15 days and 21 days or any dates input, as long as they are less than 30 days.

(5) CC INTSTB has the same capabilities as INTST In, addition, it computes a separate total for other assessed penalties.

(6) CC INTSTV has the same capabilities as INTST. In addition, accruals will be computed to the input date, input date plus 30 days, and input date plus 60 days.

(7) CC INTSTD has the same capabilities as INTST. In addition, it will also shows the detail break down for Interest and FTP computation table.

(1) The input of CC COMPA causes IDRS to compute the interest on a specified amount for a specified period of time. Each screen display (page) can accommodate up to 21 amounts. CC COMPA computes and displays a line amount for each line of input. The line amounts are accumulated and displayed on line 23 as the page total. CC COMPA also has the capability of accumulating page totals for display on subsequent page(s). It is important that the interest periods input not overlap. COMPA computes debit interest before 1-1-1999. From 01-01-1999 and subsequent, COMPA will compute CREDIT and DEBIT interest (since the interest rate for "Non-Corporate" taxpayers will be the same for CREDIT & DEBIT).

(2) COMPAC is used to compute credit interest before 1-1-1999. From 1-1-1999 on COMPAC will compute credit interest for "Corporate" taxpayers only. Input and output formats are the same as COMPAD.

(3) COMPAE provides estimated tax from dates and to dates for a specified period ending and MFT.

(4) COMPAD can accommodate 21 lines of input (21 amounts); for each line (or amount), COMPAD displays the detail used to compute the interest. The appropriate percent(s), the to and from dates used to compute the elapsed time, the factor used and the amount computed as the result is displayed and then accumulated into a total for all screens. COMPAD computes in the same manner as COMPA and is designed to be used with one tax module. COMPAD computes DEBIT interest before 1-1-1999. 01-01-1999 and Subsequent for "Non-Corporate" taxpayers, COMPAD will compute CREDIT and DEBIT interest (since the interest rate for "Non-Corporate" taxpayers will be the same for CREDIT & DEBIT).

(5) COMPAF causes IDRS to compute failure to pay penalty on a specified amount for a specified period of time. Each screen display can accommodate up to 21 amounts. COMPAF displays a page total and FTP penalty computed for each amount input. It also has the capability of accumulating page totals for display on subsequent page(s).

(6) COMPAS, to be used for manual computation of estimated tax penalty, has the same capability as COMPA except that interest will not be compounded.

(7) COMPA4, to be used with certain estate tax modules, has the same capabilities as COMPA except that the interest rate is always 4%.

(8) COMPAR is used when several independent debit interest calculations are desired on the same page of input. For example, up to eleven computations can be checked on one input screen, provided that each input line is from a separate tax module. If more than one input line is needed for one module's interest computation, COMPA will have to be used. Overlapping dates may be used in COMPAR. Line amounts will be displayed and a page total accumulated, which may be carried over onto subsequent pages. Computes Debit interest before 01-01-1999. 01-01-1999 and subsequent Debit and Credit (for "Non-Corporate taxpayers") interest.

(9) COMPAM is used for multiple independent credit interest calculations on the same input page. It is possible to input eleven computations on one screen, provided that each input line is associated with a separate tax module. COMPAC will have to be used if the computation from one module requires more than one input line. COMPAM, like its debit interest counterpart, COMPAR, will accept overlapping dates. Line amounts will be displayed and a page total accumulated, which may be carried over onto subsequent pages. Computes Credit interest before 01-01-1999. 01-01-1999 and subsequent Credit interest for Corporate taxpayers only.

(10) COMPAP, to be used with dates after 12/31/1984, has the same capabilities as COMPA except that the interest rate is 120 percent of the regular rate.

(11) COMPA, COMPAF, COMPAS, COMPA4 and COMPAP are designed to be used for only one module per input.
For example, a module with the following transactions:

(12) COMPAG is used to compute credit interest for GATT corporations. (Tax periods 199412 and subsequent) Input is the same as COMPAC. Output is the same as COMPA.

(13) COMPA6 is used to compute interest for Military personnel based on IRM 5.1.7.12.2 where the interest can only be charged at a maximum of 6 percent.

(1) CC ICOMP will compute payment information for installment agreements, for an entire account or for up to 15 requested modules of an account. The interest and penalty accruals, total balance due, total payments, and the date and amount of the final payment, are computed for the life of the agreement.

(2) ICOMPF returns a format to be used for inputting a CC ICOMP request.

(1) Use this command code to obtain IDRS computed accruals of interest and failure to pay penalty for balance due modules (IMF/BMF).

(2) Input Display for INTST, INTSTA, INTSTB, INTSTN, INTSTV, & INTSTD

(3) Record Element Description for INTST

(4) Terminal Response for INTST

1. Error Responses: Error messages are displayed in inverse Video on line 24 beginning in position 1. The invalid elements can be corrected and re-entered.— See Exhibit 2.3.29-2.

2. Valid Response:
   Output of command code INTST: See Exhibit 2.3.29-3.
   Output of command code INTSTB: See Exhibit 2.3.29-4.
   Output of command codes INTSTA, INTSTN, and INTSTV: See Exhibit 2.3.29-5.
   Output of command codes INTSTD: There are more than one screen display. The first screen is similar to INTST. The subsequent screen show the interest computation table and FTP computation table. See Exhibit 2.3.29-6

(1) Error messages display in inverse Video on line 24 beginning in position 1. The invalid elements can be corrected and re-entered.

1. TIN INVALID — TIN other than numeric or incorrectly formatted.

2. ACCOUNT NOT ON FILE — TIN not present on the TIF.

3. BMF ACCESS DENIED — Employee not profiled to access BMF accounts.

4. IMF ACCESS DENIED — Employee not profiled to access IMF accounts.

5. NAME CONTROL MISMATCH — TIF contains match on TIN but there is a mismatch on Name Control.

6. MFT/TAX PERIOD MISMATCH — MFT/TAX Period do not match with any on TIF for this taxpayer.

7. FILE SOURCE INVALID — Other than IMF/BMF/IRAF.

8. NAME CONTROL INVALID — Name Control on screen is missing or is invalid/inconsistent with input file source.

9. TO DATE INVALID — Date is invalid.

10. MFT INVALID — MFT is invalid.

11. MFT INCONSISTENT WITH TIN — MFT inconsistent with SSN format or MFT inconsistent with EIN format.

12. TAX PERIOD INCONSISTENT WITH MFT — Tax period not valid with input MFT.

13. TAX PERIOD INVALID — Tax period is invalid.

14. INVALID DEFINER — Command code definer is other than D, N, A, V, B, or blank.

15. PLEASE CORRECT INVALID DATA — Self explanatory.

16. MFT NOT VALID FOR INTST — Self explanatory.

17. COMPUTATION HOLD ON INTEREST/FTP— Self explanatory

18. TO-DATE WITHIN GRACE OF A NOTICE. NOTICE DATE IS— Notice date is displayed after the message

19. EXCEEDS 30 ADDITIONAL DAYS— Display if INTSTA To Date plus number of days field exceeds 30

20. MFT 17 HAS MULTIPLE 150'S— Self explanatory

(1) Valid Response for INTST

(2)

(1) Valid Response for INTSTB

(2) Record Element Description — Asterisked (*) items are right justified.

(3) .

(4) Due to the complex processing requirements, processing cannot always be terminated upon the first condition encountered that prevents computation of interest or FTP penalty. Therefore, in cases with multiple conditions all non-compute conditions encountered will be reflected in the messages displayed on the screen. The messages and conditions that prevent computation of interest and/or FTP penalty are reflected in the next several paragraphs.

(5) INTST Warning Messages — The warning message will consist of a one line message on line 22 of the main INTST response screen. The conditions present will not restrict interest or FTP penalty but will warn the user of conditions on the account. These conditions and messages are shown below:

1. WARNING FTD PENALTY SUBJECT TO POSSIBLE INCREASE

   1. To Date is between 17 and 35 days after the transaction date of the latest TC 18X, and

   2. Applies only to 199106 and subsequent BMF tax modules.

2. COMBAT: ADD'L INT & FTP DEPEND ON EXIT — Occurs when there is a calculation request on active combat accounts, Interest and FTP calculated to entry date.

3. CAUTION: SELF-INDENTIFIED COMBAT ZONE

   1. Taxpayer has an unreversed or corrected TC500 without an entry date.

   2. Account is in a combat freeze

4. PN 502 - CHECK AGAIN AFTER TC POSTED

   1. Pending TC502 on module, cannot be used in INTST calculations

   2. Re-Calculate again after TC502 has posted

5. INT ACCRUALS RESTRICTED/SMALL BAL IND — Occurs when there is a small balance indicator present.

(6) Accrued interest/FTP Messages — The multiple line error message will consist of a first line message COMPUTATION HOLD ON INTEREST/FTP and then the condition(s) that prevented computation(s) of interest/FTP will be shown on the following page(s). Those conditions are shown below:

1. UNREVERSED TC 500 OR TC 780

   1. TC 500 present without a TC 502 reversal or,

   2. TC 780 present without a TC 781/782 reversal.

2. MF STATUS CODE 14 — Status Code 14 is present in the Master File Status History Record.

3. MFT 52 WITH NO DATE OF DEATH

   1. MFT Code is 52 and,

   2. There is no date of death on account

4. MF STAT 10/12 & SC MOD BAL ZERO/CREDIT

   1. Status code 10 or 12 is present in Master File Status History Record, and,

   2. The Service Center module balance amount is zero or credit balance and,

   3. Service Center status is not 60 or 64

5. 941 FILING REQ. 2 — PRIOR TO 197528.

   1. BMF module with 941 Filing Requirement of 2 and,

   2. Return posted prior to cycle 197528.

6. FEDERAL GOVERNMENT EMPLOYER — Employment code in Basic Entity Module is "F".

7. STATE OR LOCAL GOVERNMENT EMPLOYER.

   1. Employment code in Basic Entity Module is "G" and,

   2. Return posted prior to cycle 197528.

8. TODATE IS PRIOR TO RDD — To date entered is prior to return due date.

9. NO POSTED RETURN PRESENT — No Return or Form 7004 posted (TC 150, TC 620) including corporate returns for MFT 02, 33, 34 with tax period prior to 198312.

10. FOREIGN OPERATIONS DISTRICT 66 OR 98.

    1. BMF module with 941 filing requirement of 2 and,

    2. Return posted prior 197612 and,

    3. HISTORICAL DO CD is 66 or 98.

11. UNREVERSED TC 534—TC 535 for reversal is not present in the module.

12. ACCOUNT TRANSFERRED OUT/STATUS CODE 29 — Master File Status History Record contains a current status code of 29.

13. COMBAT ZONE FREEZE — Requires manual Interest and Failure to Pay penalty computation.

14. TC 370 WITH DOC-CD 52

    1. TC 370 in module and,

    2. DLN Document Code is 52

15. UNREVERSED TC 604/608 — A reversing TC 605 is not present in the module.

16. INT & FTP RESTRICTION ON MFT — Self explanatory.

17. F706 FREEZE SET BY MF — Master File set this condition.

18. INVALID CALLER NAME USED — Caller other than 'TDA ', 'INTST', 'PINEX', 'ICOMP', 'ICD07', 'SIA ', 'URP ', or 'ICS '.

19. MFT 17 HAS MULTIPLE 150S — Self explanatory.

20. INVALID RESTRICT CODE RTN FROM COM CD — Set when Master File Common Code return an invalid Interest or FTP restriction value.

(7) Accrued Interest Messages — The multiple line error message will consist of a first line message COMPUTATION HOLD ON INTEREST and then the condition(s) that prevented computation(s) of interest will be shown on the following page(s). Those conditions are shown below.

1. UNREVERSED TC 340 OR TC 341 — TC 342 not present in the module.

2. PEND ADJ WITH 870 WAIVER DATE.

   1. 870 waiver date in TC 30X is not zero or,

   2. MFT is 30, 55, or 29 and,

   3. Credit interest date (870 waiver date) in TC 29X is not zero.

3. INTEREST FREEZE SET BY MF — Interest Freeze on posted return set by Master File.

4. MODULE TOO LARGE TO COMPUTE INTEREST — There are more than 600 transactions in the interest table.

5. INT RESTRICTED BY P&I /SMALL BAL SWITCH — The assessed module balance equals zero and the Small Balance Switch in the Balance Section is significant.

6. HOLD40 FREEZE - MOD FZ SET TO M- — Restricted depending upon value in HOLD40 element.

7. F5330 FREEZE - MOD FZ SET TO F- — F5330 return and F5330 Freeze significant.

8. INT RESTRICT ON MFT — Interest is not computed.

9. F941 WITH TAX PERIOD = ZEROS — Self explanatory.

(8) Accrued FTP Messages— The multiple line error message will consist of a first line message COMPUTATION HOLD ON FTP and then the condition(s) that prevented computation(s) of FTP will be shown on the following page(s). Those conditions are shown below.

1. START DATE MISSING/FTP FROZEN BY MF — FTP penalty start date in posted return is zeros.

2. TAX LIAB LESS THAN OR EQUAL TO ZERO — Total tax liability amount in posted return plus any additional assessment(s) and/or abatements net to zero or less.

3. UNREVERSED TC 270 or TC 271 — Last TC 270 or TC 271 posted has no subsequent TC 272 reversal.

4. UNREVERSED TC 320 — TC 321 not present in module (Tax Periods 198712 and prior).

5. 6020B CASE WITH MF STATUS CODE 12

   1. 6020B-IND in the posted return is set to 1 and,

   2. Return posted prior to cycle 198417 and,

   3. MF Status Code is 12 and,

   4. MF Status Cycle is prior to 198435

6. 6020B CASE WITH RET-CYC 198417–198436

   1. 6020B-IND in the posted return is set to 1 and,

   2. Return posted between cycles 198417–198436

7. MFT 13/55/03 MODULE 08 — FTP Penalty is not computed on Civil Penalty and Branded Prescription Drug (BPD) Modules.

8. MFT 30 WITH RETURN DATE OF ZEROS — Self explanatory

9. DOC-CD 51 W/RESTRICTION BLOCK NUM

   1. DLN Document Code is 51 and

   2. IMF Blocking Series other than 100–159 800-899, 900-949 or,

   3. BMF Blocking Series other than 100–199 and,

   4. Return Posted After cycle 197302

10. FTP RESTRICT ON MFT — FTP penalty is not computed.

11. PENDING ADJUSTMENT TC 29X/30X — Self explanatory

12. TOO MANY TRANS FOR AN INTERNAL TABLE — There are more than 20 adjustments present in module.

13. MODULE TOO LARGE TO COMPUTE FTP — There are more 600 transactions in the FTP table.

14. RETURN HAS A CONDITION CODE D PRESENT

    1. Account is a BMF account

    2. Return condition code is D

15. RETURN HAS A CONDITION CODE M PRESENT

    1. Account is an IMF account

    2. Return condition code is M

16. MF PENALTY ABATE FREEZE SET — Freezes abatement of penalty and interest when refund statute expired (BMF).

17. MFT 05 WITH DOC-CD 46 — Self Explanatory.

18. MFT 58 - 64 PRIOR TO 1968 — Self Explanatory.

19. MFT 44 WITH 990PF E.O. IND SET — MFT 44 with 990PF indicator set..

(9) The following warning message will be displayed if the input "TO DATE" is within the allowable grace period for payment of the last notice preceding the "TO DATE" and that notice date will be displayed: TO DATE WITHIN GRACE OF A NOTICE DATE IS 99999999

(1) Valid Response for INTSTN, lNTSTA, and INTSTV Page 2 (For Record Element Description of page 1 see See Exhibit 2.3.29-3.

(2) Record Element Description — Asterisked Items are right justified.

(1) Valid response for INTSTD first screen.

(2) Record Element Description — Asterisked (*) items are right justified.

(3) Valid response for INTSTD - Interest Computation Table.

(4) Record Element Description — Asterisked (*) items are right justified.

(5) Notes:

(6) #1: The data appear on line 5 and subsequent lines (up to line 23) depending on volume of entries in the Interest Table.

(7) This element carry transaction code values. The following are "dummy" transaction codes that may also appear in the Interest Computation Table:

(8) Valid response for INTSTD - FTP Computation Table.

(9) Record Element Description — Asterisked (*) items are right justified.

(10) Notes:

(11) #1: Each assessment has a BEGIN TC XXX and END TC XXX. Where XXX is the assessment transaction code. It also shows the FTP penalty start date.

(12) #2: If there is one or more transaction code to assess then this line of literal will be display. If there is no transaction code to assess, then a blank line with be display instead.

(13) #3 :The data appear on line 7 and subsequent lines depending on volume of entries in the FTP Table.

(14) This element carry transaction code values. The following are "dummy" transaction codes that may also appear in the FTP Computation Table:

(15) #4: The end of the assessment. This line will also show the total penalty amount for this assessment

(1) Use this command code to obtain interest (due or allowable). The special feature of this version of the command code is that a page total is computed for each screen of data input. Up to 21 lines of data (computation requests) may be entered on the screen. If the computation is to be continued on a second screen format for the same module, the continuation indicator must be present on the subsequent input for a correct computation of interest.

(2) Input Display for COMPA

(3) Record Element Description for COMPA

(4) Terminal Response to COMPA

(5) Error Response: An asterisk will display to the right of each invalid data element. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will display in inverse video. The invalid data elements can be corrected and reentered. The letter "F" will display in character position 13 when subsequent screen inputs have invalid data elements. The letter " F" indicates a freeze on interest computation. Invalid data elements can be reentered on subsequent pages without starting from the beginning.

(6) Valid Response: Output of COMPA. See Exhibit 2.3.29-9.

(7) Terminal Response to COMPAG

(8) Error Response for invalid start date: An asterisk will display to the right of each invalid data element. On line 23, beginning in position 1, the error message "INVALID GATT START DATE — MUST BE AFTER 12311994" will display in inverse video. The invalid data elements can be corrected and reentered on subsequent pages without starting from the beginning.

(9) Error Response: An asterisk will display to the right of each invalid data element. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will display in inverse video. The invalid data elements can be corrected and reentered on subsequent pages without starting from the beginning.

(10) Valid Response: Output of COMPAG. See See Exhibit 2.3.29-9.

(1) Use this command code to obtain estimated tax penalty. The format is the same as for COMPA except that the MFT and Tax Period must be entered on the first line. The COMPAE response will give the COMPAS input screen format. Up to 21 lines of data (computation requests) may be entered on the screen.

(2) Record element Description for COMPAS

(3) Terminal Response to COMPAS

(4) Error Response: An asterisk will display to the right of an invalid element. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will be displayed. The invalid data element can be corrected and reentered.

(1) Valid Response for COMPA

(2) Record Element Description

(1) Valid Response for COMPAS

(2) Record element Description

(1) Use Command Code COMPA with definer E to secure a formatted screen display of Estimated Tax from dates and to dates for a specified period ending.

(2) Input Display for COMPAE

(3) Record Element Description for COMPAE

(4) Terminal Response to COMPAE

(5) Error Response: An asterisk will display to the right of an invalid MFT or period ending. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will be displayed. The invalid data element can be corrected and reentered. If MFT 34 is entered, the error message "UNABLE TO FORMAT DATES FOR MFT 34" will be displayed.

(6) Valid Response: Output of COMPAE See Exhibit 2.3.29-11.

(1) Valid Response for COMPAE

(2) Record element Description for COMPAE

(3) See Exhibit 2.3.29–7 for command code COMPAS input.

(1) Use the command code COMPA with definer C, D, 2, 4, 5, or 6 to secure details (percentages, factors, dates) used in the interest computation. Up to 21 sets of parameters (from date, to date, and amount) can be input.

(2) Input Display for COMPAC, COMPAD, COMPA2, COMPA4, COMPA5, or COMPA6

(3) Record Element Description for COMPAC, COMPAD, COMPA2, COMPA4, COMPA5, or COMPA6

(4) Terminal Response to COMPAC, COMPAD, COMPA2, COMPA4, COMPA5, or COMPA6

(5) Error Response: An asterisk will display to the right of each invalid data element. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will display in inverse video. The invalid data elements can be corrected and reentered.

(6) Valid Response: Output of COMPAC, COMPAD, COMPA2, COMPA4, COMPA5 or COMPA6. See Exhibit 2.3.29-13.

(1) Valid Response for COMPAC, COMPAD, COMPA2, COMPA4, COMPA5 COMPA6— output may be 1 or more pages.

(2) Record Element Description — Asterisked (*) items are right justified

(1) Use the Command Code COMPA with the definer F to compute failure to pay penalty. Beginning January 1, 1987, a 1% Start Date may be entered (See Item 3 listed below) on the screen. User can enter up to 21 lines of data on the screen. If the computation is to be continued on a second screen format for the same module, the continuation indicator must be present on the subsequent input for a correct computation of FTP penalty. Due to program complexities and limitations FTP computations involving additional assessments, such as TC290, TC298, TC300, and TC308, must be entered on a separate screen from the original Tax liability.

(2) Input Display for COMPAF

(3) Record Element Description for COMPAF

(4) Terminal Response to COMPAF

1. Error Response: An asterisk (*) will display to the right of each invalid data element. On line 23, beginning in position 1, the error message "PLEASE CORRECT INVALID DATA" will display in inverse video. The error message " INVAL START — DT/NO 1% COMPUTATION" will display in inverse video on line 23 should the operator attempt to input a 1% Start Date which is within the time period in which FTP was computed at ¹⁄₂%.
   

   Example: COMPAF       08061987
   05051987    08221987 100.00
   This input would generate the INVAL START-DT error message because the program is then actually computing to the end of the month, which in this example will always be the 5^th of the month. Because the To Date is past the 5^th of the month, the program actually will compute to 09051987, thereby charging the taxpayer with the FTP penalty at the ¹⁄₂% rate. Since 09051987 is past 08061987, there will be no computation at the 1% rate. The operator should either re-input the screen without the 1% Start Date or consult the IRM 20.1 to be certain that they have computed the correct 1% Start Date. The invalid data elements can be corrected and re-entered.

2. Valid Response: Output of COMPAF. See Exhibit 2.3.29-15.

(5) When a module involves FTP Penalty rates that change from ¹⁄₂% to 1% and then back to ¹⁄₂%, the computation request must be entered on a separate screen. COMPAF cannot compute the rates changing from 1% back to ¹⁄₂% on a single screen.

(1) Valid Response for COMPAF

(2) Record Element Description

(1) Use this CC with Command Code Definer of "F" to request the screen format for ICOMP.

(2) Screen Display.

(3) Record Element Description:

(1) ICOMP is used for entering the information necessary to compute Total Balance Due, including accruals and final payment amount.

(2) Screen Display.

(3) Record Element Description:

(4) Terminal Response:
General Error Response: If an error is present in the input format, the appropriate error message will then be displayed. The invalid elements can then be corrected and re-entered.

1. FILE SOURCE INVALID — The file source is not IMF, BMF or IRAF.

2. ACCOUNT NOT ON FILE — TIN not present or the TIF for the specified File source is not present.

3. BMF ACCESS RESTRICTED — Employee not profiled to access BMF accounts.

4. IMF ACCESS RESTRICTED — Employee not profiled to access IMF accounts.

5. MFT INCONSISTENT WITH TIN — MFT inconsistent with master file.

6. NAME CONTROL MISMATCH — TIN/File source matches with one on the TIF but Name Control does not match.

7. TIN INVALID — Taxpayer identification number other than numeric or incorrect format.

8. TAX PERIOD INCONSISTENT WITH MFT — Tax period inconsistent with master file.

9. MODULE INCOMPLETE ACCRUALS — Accrued interest and/or accrued Failure-To-Pay could not be computed.

10. MFT/TAX PERIOD MISMATCH — Requested module is not on the TIF.

11. DEFINER INVALID — Definer is not equal to "F" or space.

12. MFT INVALID — The MFT is not valid.

13. TAX PERIOD — The tax period is not valid.

14. MODULE NOT INCLUDED IN COMPUTATION —

    1. IDRS Status is 4X (other than 46 or 48), 71, 72, 9X or blanks, or

    2. 47 Hold, or

    3. "Z" Freeze, or

    4. pending TC 914 or 916, or

    5. unreversed pending TC 470, or

    6. "J" Freeze, or

    7. a TC 530 with CC 05 is present, or

    8. no INSTALLMENT DATA is present on the TIF.

    9. MFT is 40, 42, 46, 68, 74, or 76

15. TOO MANY PAYMENTS — 1000 or payments to be applied to module balance.

16. TOO MUCH MONEY — No. of payments input will create a credit balance at the end of the agreement.

17. PAYMENTS EXCEED TOTAL AMOUNT DUE — The final payment is displayed in credit balance to indicate how much total balance due is in overpayment. The user should reduce the total number of payments, the payment amount, or both. This credit balance is not to be refunded to the taxpayer.

18. PLEASE CORRECT INVALID DATA — The data preceding the asterisk is incorrect. Correct and re-enter.

(5) Conditions which prevent computation of accrued interest are:

1. Employment Code is F or G and return posted prior to cycle 197528.

2. BMF Module with 941 Filing Requirement 2 and return posted prior to cycle 197528.

3. Interest Freeze Indicator is on (unreversed TC 340, 341, 534 or 780 is present; or BMF only, Status Code 14 is present in Master File Status History Section).

4. TC 150 not present.

5. "To Date" prior to Return Due Date.

6. BMF 941 Filing Requirement is 2, DO of Primary Location Code is 66 or 98, and TC 150 posted prior to cycle 197612.

7. Employment Code is F and return posts subsequent to cycle 198226.

(6) Conditions which prevent computation of accrued FTP Penalty are:

1. TC 270/271 Manual Assessment/Abatement of FTP Penalty.

2. Entity Employment Code is F or G (BMF) and the return posted prior to cycle 197528.

3. Form 941 Filing Requirement Code is 2 (BMF) and the return posted prior to cycle 197528.

4. Form 941 Filing Requirement is 2 (BMF) and the HISTORICAL DO CD is 66 or 98 or 20.

5. Status Code 14 (Form 1041 Installment) is present in the Status History Section (BMF).

6. Unreversed TC 500 Military Deferment is present on Condition Code Z (Reasonable Cause (IMF)).

7. Unreversed TC 320 Fraud Penalty is present (Tax Periods 198712 and prior).

8. Transfer-In Doc-Code 52 Transaction.

9. Transfer-In Doc-Code 51 Transaction prior to January 1983 (BMF).

10. Transfer-In Doc-Code 51 (TC 150) with DLN Blocking Series other than 100–199 (BMF).

11. Transfer-In Doc-Code 51 Transaction other than DLN Blocking Series 100–159, which posted 1-1-1973 or later (IMF).

12. Non-Delinquent Form 1120, Form 990C, Form 990T where current 23c date earlier than the return due date plus 80 days (BMF).

13. Form 1120, Form 990C, Form 990T or Form 1041A (BMF).

14. TC 150 not posted.

15. "TC Date" is prior to return due date.

16. Unreversed TC 780 (Account Compromised) is present.

17. Unreversed TC 534 with a significant amount is present Expired Balance Write-Off.

18. TC 400 Freeze is in effect.

19. Audit/DP Tax Adjustment posted prior to 1/1/1970.

20. Condition Code D (Reasonable Cause) is present, (BMF).

21. Condition Code M (Reasonable Cause) is present, (IMF).

22. Net of TCs 150, 290, 291, 301 and 300 equals zero.

23. Period Ending Date is prior to 196912.

24. Module is credit balance.

25. Module balance consists entirely of penalty and interest.

26. Too many modules on TIF for CC ICOMP to complete.

(1) Valid Response — Screen Display

(2) Record Element Description: