2.4.26. Command Codes FRM14, FRM49, and TDIRQ

(1) This IRM section provides the instructions for the use of Command Codes FRM14, FRM49 and TDIRQ.

(2) Purpose: This section contains terminal input instructions and research response displays for Command Codes (CC) FRM49, FRM14, and TDIRQ.

(3) Audience: LMSB, SB/SE, TE/GE and TS.

(4) Policy Owner: Project Director-Dean, Information Technology

(5) Primary Stakeholders: These Command Codes are used in Campuses and Area Offices to research or input data related to Delinquency Investigations during the Taxpayer Delinquent Return Notice phase of the investigation or after a TDI (Taxpayer Delinquency Investigation, Form TYD14) has been issued.

(6) Program Owner: Taxpayer Services (TS) is responsible for the administration, procedures, and updates related to the program.

(7) Program Goals: The Chart contained in See IRM 2.4.26.2 which lists the transaction codes that may be input with CC FRM14 and FRM49. TC 474 and TC 475 are not valid with CC FRM14. Closing Codes 001, 003, 004, 011, 013 and 014 can be input only on campus terminals. Closing Codes 008 and 009 can only be input by the Ogden campus.

(8) Contact Information: Applications Development, Internal Management, Im Sub Office, Account Services Branch

(1) Posts to Master File:

Transaction Code	Explanation	IMF/BMF	NMF	EPMF	Closing Codes	Satisfies IDRS Tax Module	Satisfies Subsequent IDRS-Tax Module Same MFT
590	Not liable for tax this period	yes	no	yes	001	yes	no
					003	yes	no
					004	yes	no
	6020(b) Unagreed Case	BMF ONLY			008	yes	no
	6020(b) Agreed Case	BMF ONLY			009	yes	no
					013,014	yes	no
					019–021	yes	no
					025–028	yes	no
					038,063,088	yes	no
					050,053,055	yes	no
					075,078,051	yes	no
					097,049,052	yes	no
591	No longer liable for this tax	yes	no	yes	001*	yes	yes
		BMF ONLY			008,009	yes	yes
					011*	yes	yes
					014	yes	no
					020	yes	yes
					025,050,075	yes	yes
					038,063,088	yes	yes
					097,049,055	yes	yes
592	Reversal of TC 59X	yes	no	yes	N/A	**	**
593		BMF ONLY			008,009	yes	yes
	Unable to locate	IMF ONLY			030	yes	yes
	Unable to locate	yes	no	yes	032,057,082	yes	yes
					038,063,088	yes	yes
		IMF ONLY			080	yes	yes
					097,049,055	yes	yes
	Unable to Contact	IMF ONLY			056	yes	yes
594		BMF ONLY			008,009	yes	no
	Return previously filed	yes	no	yes	022,023	yes	no
					033,058,083	yes	no
					034,059,084	yes	no
					038,063,088
					074	yes	no
					097,049,055	yes	no
595		BMF ONLY			008,009	yes	no
	Referred to examination	yes	no	yes	032,057,082	yes	yes
					038,063,088	yes	no
					097,049,055	yes	no
596		BMF ONLY			008, 009	yes	no
	Referred to Intelligence	yes	no	yes	032,057,082	yes	yes
					038,063,088	yes	no
					097,049,055	yes	no
597		BMF ONLY			008, 009	yes	no
	Surveyed	yes	no	yes	032,057,082	yes	no
					038,063,088	yes	no
					097,049,055	yes	no
598		BMF ONLY			008,009	yes	no
	Shelved	yes	no	yes	032,057,082	yes	no
					038,063,088	yes	no
		yes	yes		070	yes	no
					086	yes	no
					097,049,055	yes	no
599		BMF ONLY			008, 009	yes	no
	Return secured	yes	no	yes	013*	yes	no
					017,018	yes	no
					021	yes	no
					024
					031	yes	no
					038,063,088	yes	no
					060,061,062	yes	yes
					068, 072	yes	yes
					039,064,089	yes	no
					042,067,092	yes	no
					044,069,094	yes	no
					046,071,096	yes	no
					048,073,098
					050
					065	yes	no
					074	yes	no
					090	yes	no
					097	yes	no
					099,049,055	yes	no
474	To Establish Tax Module or to Delay TDI	yes	no	yes	N/A	no	no
475	Reverse 474 Transaction permits TDI Issuance	yes	no	yes	N/A	no	no
Note: * Closing Codes 001, 003, 004, 011 and 014 can be input only on campus terminals.
Note: Closing Codes 008 and 009 can be input at Ogden campus terminals only.
Note: Closing Codes 085 and 086 can be input by the Kansas City and Philadelphia PCA referral units only Note: If Federal indicator is set, allow TC 593 CC 30,56 and 80.
** TC 592 is used to reverse a previously input TX 59X closure. It will not post to Master File if input to reverse a TC 59X that does not post to Master File. Note: TC 592 reversals cause TDI issuance for non-IRA accounts.
** TC 599 with new Closing Codes (ICS will be using): Note: Return Secured — IRC 6020(b)-Agreed — use Closing Code: 060 Note: Return Secured — IRC 6020(b)-Unagreed — use Closing Code: 061 Note: Return Secured — Bankruptcy — use Closing Code: 062 Note: Return Secured — Taxable — use Closing Code: 068 Note: Return Secured — Non Taxable (TC 150 0.00) — use Closing Code: 072

1. Transaction Codes 59X used in IDRS postings to the TIF as pended Transactions (as well as confirmed Transactions) serves as an indicator that an acceptable reason was given for non-filing of a tax return for a specific period.

2. TC 592 is used to reverse a previously input TC 59X. If the TC 59X being reversed closed subsequent modules, those subsequent modules will be also reopened.

3. A TC 598, "Shelved", posting to the TIF remains on IDRS for a period of 65 cycles.

4. TC590 or TC591 with CC013/014 requires the input of the PARENT-EIN. Verification of the PARENT-EIN must be done prior to entry via Command Code INOLE or INOLEX.

5. TC590 or TC591 with CC13/14 with MFT-CD 02 requires the PARENT-NAME-CONTROL be entered. The PARENT-NAME-CONTROL field must be proceeded by an indicator in the ALT-FIELD-IND field of "N". The PARENT-NAME-CONTROL is used by NAP for validation of the parent name and EIN.

(2) For FRM14, and FRM49 batch input, each line 2–12 is processed as a separate input. Therefore, end of text (ENTER) indicator must be input on last data input line.

(1) General

1. This command code is used to input transactions resulting from the analysis of taxpayer responses to Master-File 1st Return Delinquency notices IMF CP59 and BMF CP259, CP 516 and 518, Spanish notices, IMF 1st notice CP759 and BMF CP959, and final notices IMF CP616 and IMF/BMF CP618. These notice responses are the source documents used as backup for the input of transaction codes 474, 475, and 590–599 to update tax modules on the TIF. If applicable, these transactions also post to the tax module on the Master File.

2. When FRM49 processes a transaction for a tax module, if the account and/or module is not present on the TIF, a dummy entity and/or tax module is built and a TC 902 is generated to request Master File data for non-NMF accounts.

3. Use a block indicator of "BB", to generate block series 74 for all TC 594 and 599 transactions on the screen.

4. If a transaction code 590, 591, or 593–599 is appended to a tax module, the TDI module status is updated to reflect the closure of the delinquent module. Also, when a transaction code 591, 593, 595 (closing codes 032, 057 or 082 only), or 596 (closing codes 032, 057 or 082 only) is appended to a tax module, the TDI module status is updated for all subsequent open delinquency modules for that account having the same MFT and plan number.

5. This command code may be used to input a single transaction code, or may be used for batch processing of up to 11 transactions.

   Note: Due to TIF (Taxpayer Information File) Centralization, effective Jan. 1, 2004, only transactions with same-type TIN's may be input on a single screen in batch processing. For example, if the first transaction is for an IMF account, then all transactions on that screen must be IMF. Likewise for BMF, NMF and EPMF transactions. Attempting to enter transactions with file sources different from that on the first line will result in the error message

   "FILE SOURCE ERROR" for all invalid transactions.

6. To batch process more than one transaction for an account, the TIN, file source, and name control for all but the first line entry for that account may be omitted. This is accomplished by inputting an "R" in position 1 of each subsequent line entry. Input of the "R" causes the TIN, file source, and name control to be repeated from the prior line entry.

7. For the last valid transaction on the screen, FRM49 stores the TIN, FILE SOURCE, TIN TYPE, MFT, PLAN NUM (for EPMF only), and TAX PERIOD for subsequent command code entries.

8. If a transaction code 597 & 598 is entered with a FERDI Indicator of 1 or 9, it is not allowed.

9. A Transaction Code of 593 is only allowed with closing codes 030, 056 or 080 when the FERDI Indicator is equal to 1 or 9

(2) Terminal Input:

1. Single Input Display: See Exhibit 2.4.26-1.

2. Batch Input Display: See Exhibit 2.4.26-2.

3. Screen Invalid Display : See Exhibit 2.4.26-3.

(3) Screen Invalid Responses: Screen error messages are displayed in inverse video beginning in position 1 of line 13. Correct the screen error and re-enter the entire screen. See Exhibit 2.4.26-4.

1. BLOCK INDICATOR INVALID —The block indicator field contains other than "BB" or blanks.

2. DATA PRESENT ON LINE13 — Data was entered on line 13.

3. LINE ERROR—An embedded blank line was entered as part of the screen data.

4. HEADER COMMAND INVALID-NOTIFY CSA — The CC in IDRS SIR is not FRM14 or FRM49 -- hardware/software error.

(4) Invalid Responses: Error messages are displayed beginning in position 32 of each line containing an input error, and the input line will be re-displayed. All valid line entries will be blanked out. Correct the invalid field for each line with an error and re-enter. Add additional entries for batch processing, up to a total of 11 entries. See Exhibit 2.4.26-4. The following messages are listed numerically for ease of use.

1. CLCD INV/INCONSIST—The closing code is invalid or inconsistent with transaction codes 590, 591, or 593–599.

2. CLCD W/TC475/592—A closing code was input with transaction codes 475 or 592.

3. FS CAN'T BE PRCSED—Accounts with the requested file source cannot be processed by FRM49.

4. FILE SOURCE ERROR—Input transaction has a different file source than that of the first transaction input on this screen.

5. INV FOR IRAF ACCTS — The TDI transaction input is invalid for IRAF accounts.

6. SPC BEFOR/AFT NCL—Data is present in a non-input field. For example, the name control was not preceded by or was not followed by a blank.

7. *NECESS FYM NOT 07 —The tax period was input with other than FYM 07 and was not preceded by an "*" (check made with MFT codes 48, 58, 60–63, or 93–96).

8. TAX MOD IS A MEMO—The tax module is a memo module and TDI transactions cannot be appended.

9. MFT INVALID—The MFT code is invalid.

10. ENT MOD NOT APPND—The MFT code was input as "00" (entity module) and TDI transactions cannot be appended.

11. MFT/TIN INCONSIST—The MFT code is inconsistent with the TIN.

12. MFT/TXPD INCONSIST—The MFT code is inconsistent with the tax period.

13. NAME CTRL INVALID—The name control is invalid.

14. CLCD NOT INPUT—The closing code was not input with transaction codes 590, 591, or 593–599.

15. TC474 NO CYC CT— The cycle count was not input with transaction code 474.

16. INP YR INCORRECT—The input year is not equal to the current year or the currect year minus one..

17. PLAN-NUM INVALID—The plan number or report number (MFT 46 modules) is invalid.

18. PLAN#/TIN INCONST—The plan number or report number (MFT 46 modules) is inconsistent with the TIN.

19. PLAN#/TXPD INCONST—The plan number or report number (MFT 46 modules) is inconsistent with the tax period.

20. INV CYC CT RANGE—The cycle count input with transaction code 474 is not in the valid range (01–20).

21. TRANS-CODE INVAL—The transaction code is invalid.

22. N/C MISMATCH-XXXX—The input name control does not match the TIF name control.

23. TIN/FS INCONSIST—The TIN is inconsistent with the file source.

24. TIN INVALID—The TIN is invalid.

25. TIN NOT ESTABLISHED ON MF — The TIN is not established on master file.

26. TAX PERIOD INVAL—The tax period is invalid.

27. AO TERM CLCD INV—Closing Codes 001, 003, 004, 011, 013, or 014 are valid only if input from a campus terminal.

    Note: For Closing-CD 014: When Closing Code 014 is input with Transaction Code 590 the input can be done from either a Campus or Area Office terminal.

28. MFT61 INVALID—MFT of 61 is invalid for TRANS-CD 474 or 475 when the TAX PERIOD is 198707 or later.

29. U INOLE-VAL SSN/NME — Account found on opposite validity - CC INOLE can be used to validate SSN/NAME.

30. CLCD VAL W/IMF —Closing codes 026, 089, 051, 076, 023, 034, 058, 084, 088, 030 and 080 are valid for an IMF account only.

31. CLCD VAL W/BMF—Closing codes 038, 039, 063, 064, 008 and 009 are valid for an BMF account only.

32. INP TRANS SINGL—The input name control does not match the NAP name control. Repeat transaction singly to obtain name control information on line 13.

33. SEE LN 13/N/C INFO—The input name control does not match the NAP name control. See line 13 for name control information.

34. DATE ENTRY INVAL—Date is not a valid date.

35. CRS/NAP NOT AVAIL—The linkage between CRS and NAP is not available.

36. NAP NOT AVAILABLE—The National Account Profile is not available.

37. EPMF USE CC97/74—EPMF Accounts require a closing code of 074 or 097.

38. EP TC594CC74 VAL—for EPMF, the only valid Transaction Code with Closing Code 074 is 594.

39. CC97 VAL W/EPMF—Use of Closing Code 097 is restricted to EPMF Accounts only.

40. ACCOUNT IS A MEMO—The requested account is a memo and TDI transactions cannot be appended.

41. IMF CC25,50,75 INV—Closing Codes 025, 050 and 075 used with Transaction Code 59X are for BMF accounts only.

    Note: The only exception to this is TC591, which may be used with IMF accounts.

42. NO TDI PROCESSED—This MFT is not involved in delinquency processing.

43. N/C MISMATCH-C/D—The TIF name control is a check digit.

44. PARENT-EIN NEEDED—The PARENT-EIN is mandatory for Transaction Code 590 or 591, Closing Code 014.

45. PARENT-EIN=SUB-EIN—The XREF-EIN (Parent EIN) cannot be the same EIN as the subsidiary EIN entered for this transaction.

46. BOTH XREF/SUB N/C INVAL — The name control for both the subsidiary and the Parent (XREF) EIN are invalid.

47. SEE LN 13-XREF INF — The name control for the Parent (XREF) EIN is invalid. See line 13 for a valid name control.

48. XREF-TIN NOT ON MF — The parent (XREF) EIN is not on the master file.

49. ACCOUNT FOUND ON OPPOSITE VALIDITY-CC INOLE CAN BE USED TO VALIDATE SSN/NAME — Use CC INOLE to validate SSN/NAME.

50. SSN NOT ON MF AS VALID OR INVALID-CC INOLE CAN BE USED TO VALIDATE DM-1 SSN/NAME — Use CC INOLE to validate SSN/NAME.

51. IRS-RECD-DATE REQ—The IRS-RECD-DATE must be entered in the COR-RECD-DATE (ccyymmdd) field for all 599 Transactions with Closing Codes of 009, 039, 064, or 089.

52. /INVALID_DATE REQ — IRS-RECD-DATE */ is invalid.

53. NAICS-CD REQUIRED—The North American Industry Classification System code must be entered for TC590 CC13/14 and TC591 with CC014.

54. NAICS-CD INVALID—The North American Industry Classification System code entered is not numeric.

55. ALT-FLD-IND MUST=A—An "A" must be input with Transaction Code of 599 with Closing Code 009, 039, 064, or 089.

56. ALT-FLD-IND MUST=N—An "N" must be input with a Transaction Code of 590 with Closing Code of 014 and MFT Code of 002.

57. ALT-FLD-IND INAPPR—ALT-FIELD-IND is input only for Transaction Code of 599 with Closing Code of 009, 039, 064, or 089 or Transaction Code of 590 with Closing Code of 014 and MFT Code of 02.

58. NEED XREF-NME-CTRL—The XREF-NAME-CONTROL must be input with the TC 590 and Closing-Code 014 with MFT CD 02.

59. XREF TIN NOT APPRO—The EIN entered is not appropriate with the input transaction and closing code. The XREF-EIN is used only with the Transaction Code 590 with Closing Code 014.

60. IBM PROGRAM ABEND — No access

61. XREF-INVAL NAP REQ— Invalid request for the NAP.

62. REQ CD NOT 1120—The filing requirement code when validated through the NAP processing did not show an 1120 Series filing requirement or a 990C Series filing requirement.

63. PROFILE IMF ONLY—The user is profiled for access to IMF accounts only. The input account is not IMF.

64. PROFILE BMF ONLY—The user is profiled for access to BMF accounts only. The input account is not BMF.

65. TIN NOT ON EP/BMF — The tin is not on the EPMF or the BMF.

66. TIN NOT EP - ON BMF — The tin is not on the EPMF but is on the BMF.

67. CC08/09 OSC ONLY -- The closing codes 008 and 009 are input only at the Ogden campus.

68. CC IS FOR TC599 ONLY — The closing codes 060, 061, 062, 068 and 072 are used for TC 599 ONLY.

69. SCRAMBLED SSN IS A 1 AND MFR IS AN 8 ON THIS ACCOUNT — Attempting to post on the valid segment.

70. RESOLVE CREDIT BAL — There is a credit balance amount. This balance must be resolved before any TC590, 591, or 593s can be posted. The exception to this is if a TC971 with AC296 exists.

71. TC INV FOR FERDI — TC 597, and 598 are not allowed for FERDI employees.

72. PCA REF UNITS ONLY — TC 599 with CC 085 or 086 is reserved for use by Kansas City and Philadelphia PCA referral units only. This is part of the Private Debt Collection initiative.

73. TAX YEAR INVALID — The FY-Entry of the TC 474 or 475 must not be equal to or greater than the current calendar year.

74. XREF-TIN REQUIRED - If TC 594 with CC 084 is entered the XREF-TIN is required.

75. MFT31 INVALID - If TC 474 is entered and the MFT-CD is 31, the transaction is invalid.

76. NO TDI PROCESSED - If MFT-CD is equal to 35 or 55 the transaction will not be processed.

77. MFT15 INVALID — If MFT-CD is equal to 15 the transaction is invalid

(5) The following error messages are generated by BMFOL and IMFOL checks. Where applicable UPC CODES are shown with the error messages. For further information on these messages see Document 6209, ADP and IDRS Information.

1. IMFOL FILE NOT AVAILABLE-TRY LATER—The IMFOL File is not available for use at this time. Try input later.

2. BMFOL FILE NOT AVAILABLE-TRY LATER—The BMFOL File is not available for use at this time. Try input later.

3. IMFOL TIN NOT FOUND—The input tin was not found on the IMFOL file.

4. BMFOL TIN NOT FND—The input tin was not found on the BMFOL file.

5. NO TXMOD - GO SING—The tax module for the input transaction was not present on the TIF. Use single input to access the BMFOL and IMFOL files.

6. THIS ACCOUNT IS ONLY VALID FOR POSTING FORM 990 GROUP RETURN TRANSACTIONS (UPC 383 RC 1).

7. TAX PERIOD MONTH DOES NOT MATCH THE CURRENT OR PRIOR FYM ON THE MASTER FILE (UPC 307 RC 1).

8. THE FRC ON THE BMF ARE 88 RESEARCH FOR ANOTHER TIN (UPC 341 RC 1).

9. THE INPUT MFT IS NOT COMPATIBLE WITH THE FRC ON THE BMF (UPC 329 RC 1). INPUT MFT NOT COMPATIBLE WITH FRC ON BMF (UPC 329 TC 1).

10. INPUT MFT NOT COMPATIBLE WITH FRC AND EO ENTITY STATUS = 41 (UPC 329 RC 2).

11. THIS MFT IS NOT VALID WITH AN EMPLOYMENT CD OF "S" (UPC 343 RC 1).

12. MFT NOT VALID WITH EMPLOYMENT CODE OR SUBSECTION OR EO STATUS (UPC 308 RC 5 OR RC 9).

13. ACCT IS A PARENT OF A GEN-ACCT CAN NOT BE CLOSED WITH THIS TRANS-CODE (UPC 365 RC 1).

14. THIS ACCOUNT DOES NOT HAVE AN EO SECTION (UPC 366 RC 1).

15. MASTER FILE DOES NOT HAVE A TAX MODULE FOR THIS TAX PERIOD (UPC 309 RC 1).

16. IMFOL DOES NOT HAVE A NAME LINE EQUAL TO OR EARLIER THAN THE TAX PERIOD YR (UPC 188).

17. MFR FOR THIS ACCOUNT IS AN 8 (UPC 182).

18. SCRAMBLED SSN IS A 1 AND MFR IS AN 8 FOR THIS ACCOUNT (UPC 177).

19. TAX PERIOD MONTH DOES NOT MATCH THE CURRENT OR PRIOR FYM ON THE MASTER FILE (UPC 162).

20. MASTER FILE DOES NOT HAVE A TAX MODULE FOR THIS TAX PERIOD (UPC 159).

    Note: NAICS Codes can be found in IRM 1.13.7.

21. TC INV for FERDI for 597 & 598 if the FERDI Indicator is 1 or 9.

(6) Invalid NAP Responses: Error messages returned from NAP processing will be displayed on line 13. These messages will be up to 80 characters long and self explanatory. If further explanation is needed see IRM 2.3.47.

(7) System Error Response: System error messages are displayed beginning in position 32 of the line containing the error. System errors reflect a problem relating to the availability of a file or an error with a common subroutine. In many cases an RPA should be notified, and a print made of screen input and response if possible, to aid in pinpointing and correcting programming or database problems. See the Miscellaneous Error Messages section of IRM 2.3.2.5 for definitions of these messages and corrective measures.

(8) Valid Response: If the screen contained fewer than 11 entries, REQUEST COMPLETED is displayed on line 13 and all input is re-displayed. If the screen contained 11 entries, the screen is blanked, "FRM49" is re-displayed, and the cursor is positioned on line 2.

(1) General

1. This command code is used to input transactions resulting from the analysis of taxpayer responses to Forms TYD14, Taxpayer Delinquency Investigations. The TYD14's are the source documents used as backup for the input of transaction codes 590–599 to update tax modules on the TIF. If applicable, these transactions also post to the tax module on the Master File.

2. In order for FRM14 to process a transaction for a tax module, there must be a corresponding tax module present on the TIF ( See IRM 2.4.26.4(1)(c) for the one exception to this rule). In addition, except for TC 592 transactions, the module must be in TDI status (TDI module status indicator other than zero). Also, the screen input transactions must satisfy all open modules (TDI module status indicators other than 2 or 8) for the account, or all inputs for that account will be rejected with the error message "MODS NOT SATISFIED". This open module check is not made, however, if there are 11 screen entries for the same account or all screen entries for the same account are Transaction Code 599 transactions.

3. If a transaction code 590, 591, or 593–599 is appended to a tax module, the TDI module status is updated to reflect the closure of the delinquent module. Also, when a transaction code 591, 593, 595 (closing codes 032, 057 or 082 only), or 596 (closing codes 032, 057 or 082 only) is appended to a tax module, the TDI module status is updated for all subsequent open delinquency modules for that account having the same MFT and plan number. For TRANS-CD of 591 only, if the module is not present on the TIF (and if there is at least one module already present on the TIF for that account), a dummy module is built and a TC 902 indicator is set in the tape record which causes a TC 902 to be generated in subsequent processing.

4. This command code may be used to input a single transaction code, or may be used for batch processing of up to 11 transaction.

   Note: Due to TIF (Taxpayer Information File) Centralization, effective Jan. 1, 2004, only transactions with same-type TIN's may be input on a single screen in batch processing. For example, if the first transaction is for an IMF account, then all transactions on that screen must be IMF. Likewise for BMF, NMF and EPMF transactions. Attempting to enter transactions with file sources different from that on the first line will result in the error message "FILE SOURCE ERROR" for all invalid transactions.

5. To batch process more than one transaction for an account, the TIN, file source, and name control for all but the first line entry for that account may be omitted. This is accomplished by inputting an "R" in position 1 of each subsequent line entry. Input of the "R" causes the TIN, file source, and name control to be repeated from the prior line entry.

6. For the last valid transaction on the screen, FRM14 stores the TIN, FILE SOURCE, TIN TYPE, MFT, PLAN NUM (for EPMF only), and TAX PERIOD for subsequent command code entries.

(2) Terminal Input:

1. Single Input Display: See Exhibit 2.4.26-4.

2. Batch Input Display : See Exhibit 2.4.26-5.

3. Screen Invalid Display: See Exhibit 2.4.26-6.

(3) Screen Invalid Responses: Screen error messages are displayed in inverse video beginning in position 1 of line 13. Correct the screen error and re-enter the entire screen. See Exhibit 2.4.26-8.

1. BLOCK IND INVALID*—The block indicator field contains other than "BB" or blanks.

2. DATA ON LINE 13—Data was entered on line 13.

3. LINE ERROR—An embedded blank line was entered as part of the screen data.

4. HEADER COMMAND INVALID-NOTIFY CSA — The CC in IDRS SIR is not FRM14 or FRM49 -- hardware/software error.

(4) Invalid Responses: Error messages are displayed beginning in position 32 of each line containing an input error, and the input line will be re-displayed. All valid line entries will be blanked out. Correct the invalid field for each line with an error and re-enter. Add additional entries for batch processing, up to a total of 11 entries. See Exhibit 2.4.26-8. The following messages are listed numerically for ease of use.

1. CLCD INV/INCONSIST—The closing code is invalid or inconsistent with transaction codes 590, 591, or 593–599.

2. CLCD W/TC 475/592—A closing code was input with Transaction Code 592.

3. FS CAN'T BE PRCSED—Accounts with the requested file source cannot be processed by FRM14.

4. FILE SOURCE ERROR—Input transaction has a different file source than that of the first transaction input on this screen.

5. INV FOR IRAF ACCTS — The TDI transaction input is invalid for IRAF accounts.

6. SPC BEFOR/AFT NCL—Data is present in a non-input field. For example, the name control was not preceded by or was not followed by a blank.

7. *NECESS FYM NOT 07—The tax period was input with other than FYM 07 and was not preceded by an "*" (check made with MFT codes 48, 58, 60–63, or 93–96).

8. TAX MOD IS A MEMO—The tax module is a memo module and TDI transactions cannot be appended.

9. MFT INVALID—The MFT code is invalid.

10. ENT MOD NOT APPND —The MFT code was input as "00" (entity module) and TDI transactions cannot be appended.

11. MFT/TIN INCONSIST—The MFT code is inconsistent with the TIN.

12. MFT/TXPD INCONSIST—The MFT code is inconsistent with the tax period.

13. NAME CTRL INVALID—The name control is invalid.

14. CLCD NOT INPUT—The closing code was not input with transaction codes 590, 591, or 593–599.

15. INP YR INCORRECT—The input year is not equal to the current year or the current year minus one.

16. REQ MOD NOT ON TIF—The requested tax module is not present on the TIF.

17. NOT IN TDI STATUS—The input transaction code is 590, 591 or 593–599 and the TDI module status indicator is zero, or, the input transaction code is 592 and the TDI module status indicator is not 2.

18. ACCOUNT NOT ON TIF—The requested account is not present on the TIF.

19. OPN MODS NOT SATIS—All modules in open TDI status for this account were not satisfied by the screen input transactions.

20. PLAN-NUM INVALID—The plan number or report number (MFT 46 modules) is invalid.

21. PLAN#/TIN INCONST—The plan number or report number (MFT 46 modules) is inconsistent with the TIN.

22. PLAN#/TXPD INCONST—The plan number or report number (MFT 46 modules) is inconsistent with the tax period.

23. TRANS-CD INVAL—The transaction code is invalid.

24. U INOLE-VAL SSN/NME — Account found on opposite validity - CC INOLE can be used to validate SSN/NAME.

25. N/C MISMATCH-XXXX —The input name control does not match the TIF name control.

26. N/C MISMATCH-CD — The input name control is not available.

27. TIN/FS INCONSIST—The TIN is inconsistent with the file source.

28. TIN INVALID—The TIN is invalid.

29. TIN NOT ESTABLISHED ON MF — The TIN is not established on MF.

30. TAX PERIOD INVAL— The tax period is invalid.

31. AO TERM CLCD INV— Closing-Cds of 001, 003, 004, 011, 013, or 014 are valid only if input from a campus terminal.

    Note: For Closing-CD 014— When the Closing-Cd of 014 is input with the Transaction-Code of 590 the input can be done from either a Campus or Area Office terminal.

32. CLCD VAL W/IMF —Closing codes 026, 089, 051, 076, 023, 034, 059, 084, 088, 030 and 080 are valid for an IMF account only.

33. CLCD VAL W/BMF —Closing codes 038, 039, 063, 064, 008 and 009 are valid for a BMF account only.

34. DUMMY ACCT U FRM49—The account is a dummy and must be input with FRM49.

35. DATE ENTRY INVAL— Date is not a valid date.

36. EPMF USE CC97/74-EPMF— Accounts require a closing code of 074 or 097.

37. EP TC594 CC74 VAL—For EPMF the only valid Transaction Code with Closing Code 074 is 594

38. CC97 VAL W/EPMF—Use of Closing Code 097 is restricted to EPMF Accounts only.

39. ACCOUNT IS A MEMO—The requested account is a memo and TDI transactions cannot be appended.

40. IMF CC25/50/75 INV—Closing Codes 025, 050, and 075 used with Transaction Code 59X are for BMF accounts only.

    Note: THE ONLY EXCEPTION TO THIS IS THE TC591. TC 591 WITH THESE CLOSING CODES MAY BE USED FOR IMF ACCOUNTS.

41. NO TDI PROCESSED—This MFT is not involved in delinquency processing.

42. IRS-RECD-DATE REQ—The IRS-RECD-DATE must be entered in the COR-RECD-DATE (ccyymmdd) field for all 599 Transactions with Closing Codes of 009, 039 or 064 or 089.

43. NAICS-CD REQUIRED—The NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM code must be entered for TC590 or TC591 with CC 014.

44. NAICS-CD INVALID—The NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM code entered is not numeric.

45. ALT-FLD-IND MUST=A—An "A" must be input with Transaction Code of 599 with Closing Code of 009, 039 or 064 or 089.

46. ALT-FLD-IND MUST=N—An "N" must be input with Transaction Code of 590 with Closing Code of 014 and MFT-Code of 02.

47. ALT-FLD-IND INAPPR—ALT-FLD-IND is input with Transaction Code of 599 with Closing Code of 009, 039 or 064 of 089 or Transaction Code of 590 with Closing Code of 014 and MFT Code of 02.

48. NEED XREF-NME-CTRL—The XREF-NAME-CONTROL must be input with the TC 590 and Closing-Code 014 with MFT-CD 02.

49. XREF TIN NOT APPRO—The EIN enter is not appropriate with the input transaction and closing code. The XREF-EIN is used only with the Trans-Cd 590 or Trans-Cd 591 with Closing Code 014.

50. REQ CD NOT 1120—The filing requirement code when validated through the NAP processing did not show an 1120 Series filing requirement or a 990C Series filing requirement.

51. PROFILE IMF ONLY—The user is profiled for access to IMF accounts only. The input account is not IMF.

52. PROFILE BMF ONLY—The user is profiled for access to BMF accounts only. The input account is not BMF.

53. CC08/09 OSC ONLY -- The closing codes 008 and 009 are input only at the Ogden campus.

54. SCRAMBLED SSN IS A 1 AND MFR IS AN 8 ON THIS ACCOUNT — Attempted to post to an account on the valid segment .

55. TIN NOT ON EP/BMF — The tin is not on the EPMF or the BMF.

56. TIN NOT EP - ON BMF — The tin is not on the EPMF but is on the BMF.

57. RESOLVE CREDIT BAL — There is a credit balance on this account. This balance must be resolved before any TC590, 591, or 593s can be posted. The exception to this is if a TC971 with AC296 exists.

58. TC INV FOR FERDI — TC 597, and 598 are not allowed for FERDI employees.

59. PCA REF UNITS ONLY — TC 599 with CC 085 or 086 is reserved for use by Kansas City and Philadelphia PCA referral units only. This is part of the Private Debt Collection initiative.

(5) System Error Response: System error messages are displayed beginning in position 32 of the line containing the error. System errors reflect a problem relating to the availability of a file or an error with a common subroutine. In many cases a CSA should be notified, and a print made of screen input and response if possible, to aid in pinpointing and correcting programming or database problems. See the Miscellaneous Error Messages section of IRM 2.3 for definitions of these messages and corrective measures.

(6) Valid Response: If the screen contained fewer than 11 entries, REQUEST COMPLETED is displayed on line 13 and all input is re-displayed. If the screen contained 11 entries, the screen is blanked, "FRM14" is re-displayed, and the cursor is positioned on line 2.

(1) This command code is used to generate screen literals indicating the input position for the data elements needed to input Command Code TDIRQ requests.

(2) Terminal Input: See Exhibit 2.4.26-7 for CC TDIRQR Input Format.

(3) Terminal Response: See Exhibit 2.4.26-8 for CC TDIRQR Terminal Response.

(1) General

1. This command code is used to add NMF entity, tax module, and TDI Compliance records to the TIF for the purpose of generating delinquency notices and/or TDI's for an account. This command code may also be used to add TDI Compliance Data to IMF accounts where no compliance data is present. Form 4864 is the source document used as backup for the input of a Request For Taxpayer Delinquency Investigation.

2. This command code may also be used to add IMF entity and TDI Compliance records to the TIF or to add a TDI Compliance record to an entity on the TIF which does not have TDI Compliance data.

3. Use Request Type Code ‘E’ for NMF requests when no account data is present on IDRS. An entity module will be built with name and address data, a TDI Compliance record will be built, and up to three tax modules can be built. See Exhibit 2.4.26-10.

   Note: Now TDIRQ will build an update record to be sent to NAME SEARCH FACILITY (NSF) when the NMF account is input using Request Type Code ‘E’.

4. If NSF or IHXFER is not available during real-time processing a separate record will be written and a new run will be used at the end of the day to provide a tape to ECC-MTB for NSF updates This processing will be invisible to real-time users of TDIRQ.

5. Use Request Type Code ‘T’ for NMF requests when entity data is present on IDRS and the account is already in Notice or TDI Status. The requested tax modules must not be present. TDI Compliance Data will not be built or updated, but up to three tax modules can be added to an active delinquency investigation. Input is not valid for Memo or Dummy accounts. See Exhibit 2.4.26-11.

6. Use Request Type Code ‘B’ for NMF requests when entity data is present on IDRS and the account is not in Notice or TDI Status. The requested tax modules must not be present. A TDI Compliance record will be built and up to three tax modules can be built. Input is not valid for Memo or Dummy accounts. See Exhibit 2.4.26-12.

7. Use Request Type Code ‘C’ for IMF requests when entity data and tax module data are present on IDRS and the account is not in Notice or TDI Status. If no data is present on IDRS, use CC FRM49 to input TC 474's for each tax module requested prior to inputting the CC TDIRQ request. CC FRM49 will establish the entity and build the tax modules. CC TDIRQ may then be used to build TDI Compliance Data. Input is not valid for Memo accounts. See Exhibit 2.4.26-13.

8. Use Request Type Code ‘S’ for IMF requests when no account data is present on IDRS. An entity module and a TDI Compliance record will be built. Request Type Code ‘S’ will build a TDI Compliance record for an existing account if a TDI Compliance record is not present. Input is not valid for Memo accounts. See Exhibit 2.4.26-14.

(2) Terminal Input:

1. TDIRQR Terminal Display: TDIRQ Response Format. See Exhibit 2.4.26-9.

2. TDIRQ Sample Input, Request Type Code ‘ E’: See Exhibit 2.4.26-10.

3. TDIRQ Sample Input, Request Type Code ‘ T’: See Exhibit 2.4.26-11.

4. TDIRQ Sample Input, Request Type Code ‘ B’: See Exhibit 2.4.26-12.

5. TDIRQ Sample Input, Request Type Code ‘ C’: See Exhibit 2.4.26-13.

6. TDIRQ Sample Input, Request Type Code ‘ S’: See Exhibit 2.4.26-14.

(3) Valid Response: If the request is accepted, the input screen is redisplayed with "REQUEST COMPLETED" on screen line 13.

(4) Invalid Responses: Error messages are displayed in inverse video beginning in position one of screen line 13. Correct the error and re-enter. The following messages are listed numerically for ease of use.

1. 1120DI TX-PRD MUST BE BEFORE 198501 n—The Form Number 1120DI must have a Tax Period earlier than 198501.

2. 1120IC TX-PRD MUST BE AFTER 198412 n—The Form Number 1120IC must have a Tax Period later than 198412.

3. ACCT MUST BE ON TIF W/REQ-TYPE B—An account must be present on the TIF with Request Type ‘B ’, which is used to build tax modules and a TDI Compliance record for an existing NMF account.

4. ACCT MUST BE ON TIF W/REQ-TYPE C—An account must be present on the TIF with Request Type ‘C ’, which is used to build a TDI Compliance record for an existing IMF account.

5. ACCT MUST BE ON TIF W/REQ-TYPE T—An account must be present on the TIF with Request Type ‘T ’, which is used to add additional tax modules to an existing NMF account in delinquency status.

6. ACCT PRESENT ON TIF W/REQ-TYPE E—An account must not be present on the TIF with Request Type ‘E ’, which is used to build an NMF account, tax modules, and TDI Compliance Data.

7. ACTION-CD/ACTION-CYC INCONSISTENT—A Last Action Code entry was made, but a Last Action Cycle entry was not; or, a Last Action Cycle entry was made, but a Last Action Code entry was not.

8. ADDRESS REQUIRED W/REQ-TYPE E—Address Data must be entered for Request Type ‘E’ requests.

9. ADDRESS VALID W/REQ-TYPE E ONLY—Address Data may not be entered with Request Types ‘B’ , ‘T’, ‘ C’ or ‘S’ .

10. BLOCKED FOR IMF PRIVATE DEBT COLLECTION (IMF—PDC) — If account Request Type ‘C’ or ‘S’, which is blocked for Private Debt Collection (PDC).

11. CASE-DELQ-YR INVALID—The Case Delinquent Year entry does not pass Standard Validity Check.

12. CASE-DELQ-YR VALID FOR IMF ONLY—A Case Delinquent Year entry is valid with IMF requests only.

13. CASE-DELQ-YR REQUIRED W/REQ-TYPE C—A Case Delinquent Year entry must be made to establish IMF TDI Compliance Data.

14. CASE-SC-CD INVALID—The Case Service Center Code entry does not pass Standard Validity Check.

15. CASE-SC-CD VALID FOR IMF ONLY—A Case Service Center Code entry is valid for IMF requests only,

16. CASE-DELQ-YR REQUIRED W/REQ-TYPE C—A Case Delinquent Year entry must be made to establish IMF TDI Compliance Data.

17. CASE-SC-CD INVALID—The Case Service Center Code entry does not pass Standard Validity Check.

18. CASE-SC-CD VALID FOR IMF ONLY—A Case Service Center Code entry is valid for IMF requests only.

19. CITY AND STATE AND ZIP FIELDS ARE INVALID-ERROR- CODE-IND IS 16, the CITY, STATE-CD and ZIP-CD fields all contain invalid characters.

20. CITY AND STATE FIELDS ARE INVALID-ERROR-CODE-IND IS 11, the CITY and STATE-CD fields all contain invalid characters.

21. CITY AND ZIP FIELDS ARE INVALID-ERROR-CODE-INDIS 12, the CITY and ZIP-CD fields contain invalid characters.

22. CITY FIELD IS BLANK, CITY FIELD REQUIRED-ERROR-CODE- IND IS 37. The STREET-ADDR, STATE-CD and ZIP-CD fields are present but the CITY field is blank.

23. CITY FIELD IS INVALID-ERROR-CODE-IND IS10, the CITY field contains an invalid character.

24. CITY REQUIRED—When address input is required, a city entry must be made.

25. COMMAND CODE DEFINER INVALID—The Command Code Definer field must be blank with TDIRQ requests.

26. COMPL. DATA INVALID W/REQ-TYPES T,S—TDI Compliance fields (Notice Code, TDI Case Code, Original TDI Cycle, Last Action Code, Last Action Cycle etc.) must not be entered on the screen with Request Types ‘T’ or ‘S ’ input.

27. COMPLIANCE DATA NOT ON TIF W/REQ-TYPE T—TDICompliance Data must be present on the TIF with Request Type ‘T ’, which is used to add additional tax modules to an existing delinquent account.

28. COMPLIANCE DATA ON TIF W/REQ-TYPE B—TDICompliance Data must not be present on the TIF with Request Type ‘B’, which is used to build tax modules and compliance data for existing accounts.

29. COMPLIANCE DATA ON TIF W/REQ-TYPE C—TDICompliance Data must not be present on the TIF with Request Type ‘C ’, which is used to build compliance data for an IMF account.

30. COMPL. DATA PRESENT, USE TSIGN D—Compliance Data must not be present on the TIP with Request Type ‘S ’, which is used to build compliance data for an IMF account.

31. DATA PRESENT ON LINE 13—Screen line 13 is reserved for operational messages.

32. DUPLICATE MODULE INPUT NOT ALLOWED—The same Form Number and Tax Period appear on the input screen more than once.

33. FILE INCONSISTENT W/REQ-TYPE-CD—Request Types ‘E’, ‘B ’, and ‘T’ are valid for NMF accounts only; Request Type ‘C ’ is valid for IMF accounts only and Request Type ‘S’ is valid for IMF accounts only.

34. FIRST NAME LINE INVALID—The First Name Line does not pass Standard Validity Check.

35. FOREIGN COUNTRY FIELD IS INVALID-ERROR—CODE-IND IS 31, the FOREIGN-CTRY field contains an invalid character.

36. FORM-NUM INVALID MOD-LINE n—The Form Number entered on module line ‘n’ is not a valid NMF Form Number.

37. FORM-NUM REQUIRED MOD-LINE n—A Form Number entry must be made for each requested tax module.

38. FOURTH NAME LINE INVALID—The Fourth Name Line entry does not pass Standard Validity Check.

39. FS/COMMAND CODE INCONSISTENT—TDIRQ input is valid for NMF and IMF accounts only.

40. LAST-ACTION-CD INVALID—The Last Action Code must be 1, 2, 3, 4, or 5.

41. LAST-ACTION-CYC INVALID—The Last Action Cycle must be a valid cycle and be less than the current cycle.

42. LAST-ACTION-CD MUST BE 1, 2, 3, 4, OR 5-LAST-ACTION-CD must be 1, 2, 3, 4, or 5.

43. LOC-CD INVALID—The Location Code entry does not pass Standard Validity Check.

44. LOC-CD REQUIRED W/REQ-TYPE E—An entry must be made in the Location Code field with Type ‘E ’ requests.

45. LOC-CD VALID W/REQ-TYPE E ONLY—An entry must not be made in the Location Code field with Request Types ‘ B’, ‘T’ , ‘C’ or ‘ S’ requests.

46. MFT GENERATED INCORRECTLY MOD-LINE n—A valid NMF MFT cannot be generated from the Form Number entered on module line ‘n’.

47. MFT INCONSISTENT WITH TIN MOD-LINE n—The MFT generated from the Form Number entered on module line ‘n ’ is inconsistent with the type of account.

48. MFT/TAX-PRD INCONSISTENT MOD-LINE n—The Tax Period entered on module line ‘n’ is not consistent with the MFT generated from the Form Number.

49. MODULE BALANCE INVALID MOD-LINEn—The Module Balance Amount entered on module line ‘n’ does not pass Standard Validity Check.

50. NAME CONTROL INVALID—The Name Control does not pass Standard Validity Check.

51. NAME CONTROL MISMATCH WITH TIF—The screen input Name Control does not match the TIF Name Control (Types ‘ B’, ‘T’ , ‘C’ or ‘ S’ only).

52. NAME CONTROL REQUIRED—The Name Control is a required input field.

53. NAME DATA VALID W/REQ-TYPE E ONLY—Name Data should not be entered with Type ‘B’, ‘T’, ‘C ’ or ‘S’ requests.

54. NAME-CTRL INCONSISTENT W/1ST NAME LINE—The screen input Name Control does not match the Name Control generated from the first Name Line (Request Type ‘E’ only).

55. NAME REQUIRED W/REW-TYPE E—Name Line Data must be entered with Type ‘E’ requests.

56. NL2/SECONDARY-SORT-CD INCONSISTENT—The Secondary Sort Code is ‘2’ and the first position of the Second Name Line is a bracket ‘] ’; or, the Secondary Sort Code is not a ‘2 ’ and the first position of the Second Name Line is not ‘]’; or, the Second Name Line is blank and the Secondary Sort Code is 2, 3, or 4.

57. NL3/SECONDARY-SORT-CD INCONSISTENT—The Secondary Sort Code is ‘3’ and the first position of the Third Name Line is a bracket ‘] ’; or, the Secondary Sort Code is not a ‘3 ’ and the first position of the Third Name Line is not ‘]’; or, the Third Name Line is blank and the Secondary Sort Code is 3, or 4.

58. NL4/SECONDARY-SORT-CD INCONSISTENT—The Secondary Sort Code is ‘4’ and the first position of the Fourth Name Line is a bracket ‘] ’; or, the Secondary Sort Code is not a ‘4 ’ and the first position of the Fourth Name Line is not ‘]’; or, the Fourth Name Line is blank and the Secondary Sort Code is 4.

59. NOTICE-CD INVALID—The Notice Code entry must be ‘A’ (accelerate TDI) or ‘T’ (issue duplicate TDI).

60. NOTICE-CD MUST BE A, T. I OR U—The NOTICE-CD entry must be ‘A’ (accelerate TDI) or ‘T’ (issue duplicate TDI) or ‘I’ (delay notice for 4 cycles) or ‘U’ (accelerate to TDI).

61. ORIGINAL-TDI-CYC REQUIRED— A duplicate TDI was requested (Notice Code ‘T’), therefore an Original TDI Cycle entry must be made.

62. ‘R ’ REQUIRED-TDIRQR -The CC-Definer ‘R ’ is required to access the TDIRQ Screens.

63. REQUEST DENIED-IMF MEMO ACCT-TDIRQ input is not valid for IMF Memo accounts.

64. REQUEST DENIED-NMF MEMO OR DUMMY ACCT-TDIRQ - input is not valid for NMF Memo or Dummy accounts.

65. REQUEST-TYPE-CD INVALID—The Request Type Code must be ‘E’, ‘ B’, ‘T’ , ‘C’ or ‘ S’.

66. SC CD NOT 07–09, 17–19, 28, 29, 49, 89 The Service Center Code is limited to the ten numbers listed in this error message; 07, 08, 09, 17, 18, 19, 28, 29, 49, 89.

67. SECONDARY-SORT-CD INVALID—The Secondary Sort Code must be entered as 1, 2, 3, or 4 input of a ‘1 ’ is optional.

68. SECOND NAME LINE INVALID—The Second Name Line does not pass Standard Validity Check; or the Second Name Line is blank and data follows on the Third or Fourth Name Line.

69. SELECTION-CD INVALID—The Selection Code entry does not pass Standard Validity Check.

70. SELECTION-CD VALID FOR IMF ONLY— A Selection Code entry is valid for IMF requests only.

71. SERV CTR CD REQUIRED W/REQ-TYPE S— A Service Center Code must be input when the Request Type Code is ‘S ’. Valid Service Center Codes are 07, 08, 09, 17, 18, 19, 28, 29, 49, 89.

72. SERV CTR CD VALID W/REQ-TYPE S ONLY— A Service Center Code must be input only with Request Type Code ‘S ’. Valid Service Center Codes are 07, 08, 09, 17, 18, 19, 28, 29, 49, 89.

73. STATE-CD INVALID—The State Code entry does not pass Standard Validity Check.

74. STATE-CD REQUIRED— When Address Data is required, a comma followed by a valid State Code or ‘. ’ must be entered.

75. STATE CODE AND ZIP CODE ARE INCONSISTANT-ERROR- CODE-IND IS 40, The STATE-CD and ZIP-CD fields are inconsistent.

76. STATE AND ZIP FIELDS ARE INVALID-ERROR-CODE-IND IS13, the STATE-CD and ZIP-CD fields all contain invalid characters.

77. STATE FIELD INVALID-ERROR-CODE-IND IS15, The STATE-CD field contains an invalid character.

78. STATE-CD REQUIRED— When Address Data is required, a comma followed by a valid State Code or ‘.’ must be entered.

79. STREET AND CITY AND STATE FIELDS ARE INVALID-ERROR- CODE-IND IS07, the STREET-ADDR, CITY and STATE-CD fields contain invalid characters.

80. STREET AND CITY ZIP FIELDS ARE INVALID-ERROR-CODE-IND IS 09, the STREET-ADDR, CITY and ZIP-CD fields all contain invalid characters.

81. STREET AND CITY FIELD ARE INVALID-ERROR-CODE-IND IS 04, the STREET-ADDR and CITY fields contain invalid characters.

82. STREET AND FOREIGN COUNTRY FIELDS ARE INVALID-ERROR-CODE-IND IS 17, the STREET-ADDR and FOREIGN-CTRY fields all contain invalid characters.

83. STREET AND STATE AND ZIP FIELDS ARE INVALID-ERROR-CODE-IND IS08, the STREET-ADDR and STATE-CD and ZIP-CD fields contain invalid characters.

84. STREET AND STATE FIELDS ARE INVALID-ERROR-CODE-IND IS 05, the STREET-ADDR and STATE-CD fields contain invalid characters.

85. STREET AND ZIP FIELDS ARE INVALID-ERROR-CODE-IND IS06, the STREET-ADDR and ZIP-CD fields contain invalid characters.

86. STREET AND CITY AND STATE AND ZIP FIELDS ARE INVALID- ERROR-CODE-IND IS 01, the STREET-ADDR, CITY, STATE-CD and ZIP-CD fields all contain invalid characters.

87. STREET FIELD IS INVALID-ERROR-CODE-IND IS03, the STREET-ADDR contains an invalid character.

88. SUPP-REQ-IND MUST BE D W/REQ-TYPE S—the supplement request indicator must be ‘D’.

89. SUPP-REQ-IND REQUIRED W/REQ-TYPE S—A supplement indicator entry is required with Request Type ‘S ’. The valid supplement request indicator is ‘ D’.

90. SUP-REQ-IND VALID W/REQ-TYPE S ONLY—an entry must not be made in the supplement indicator field for Request Types ‘E’, ‘B ’, ‘T’ or ‘C’.

91. TAX-MOD INPUT INVALID W/REQ-TYPES C, S—Tax module/modules must be present on the TIF prior to input of Type ‘C’ requests. Tax module/modules must not be input with Type ‘S’ requests.

92. TAX-MOD INPUT REQUIRED— At least one tax module entry is required for Type ‘E’, ‘B’, or ‘T ’ requests.

93. TAX-MOD ON TIF MOD-LINE n—The tax module entered on module line ‘n’ is already present on the TIF.

94. TAX-PRD INVALID MOD-LINEn—The Tax Period entry on module line ‘n’ does not pass Standard Validity Check.

95. TAX-PRD REQUIRED MOD-LINE n— A Tax Period must be entered for each requested tax module.

96. TDI-CASE-CODE INVALID—Must input a valid TDI-CASE-CD from the CASE-CD-LIST table. Refer to Doc. 6209.

97. TDI-CYC/ACTION-CD INCONSISTENT—The Last Action Code if entered must be ‘5’ when an Original TDI Cycle is entered.

98. TDI-CYC/ACTION-CYC INCONSISTENT—The Original TDI Cycle must be equal to or less than the Last Action Cycle.

99. TDI-CYC INVALID—The Original TDI Cycle does not pass Standard Validity Check or is not less than the current cycle.

100. TDIRQR MUST BE INPUT FIRST—Initialization with CC TDIRQR must be made prior to CC TDIRQ input.

101. THIRD NAME LINE INVALID—The Third Name Line does not pass Standard Validity Check; or, the Third Name Line is blank and data appears on the Fourth Name Line.

102. TIN/FS INCONSISTENT—The TIN entry is not consistent with the requested file.

103. TIN INVALID—The TIN entry does not pass Standard Validity Check.

104. ZIP-CD INCONSISTENT— The Zip Code entry is not within the allowable range for the State.

105. ZIP-CD INVALID—The Zip Code entry does not pass Standard Validity Check.

106. ZIP-CD PRESENT— A Zip Code entry must not be made when the State Code is entered as ‘. ’ .

107. ZIP-CD REQUIRED— A Zip Code entry is required unless the State Code is entered as ‘.’ .

(5) System Error Responses: System errors result from a file being unavailable, or an error with a common subroutine. Error messages are displayed in inverse video beginning in position one of screen line 13. Make a print of the screen input and response if possible and notify an RPA or a representative of SYSTEMS CONTROL POINT if requested.

1. CKSTZIP ERROR-NOTIFY CONTROL POINT— An error was encountered using ‘CKSTZIP’ Subroutine. The National Office should be notified.

2. DEPART ERROR ABORT-NOTIFY RPA— An unsuccessful attempt was made to depart from the TIF.

3. I/O ERROR–TRY AGAIN LATER—The requested account is temporarily unavailable. Retry later.

4. NO xTIFnn–AREA NOT AVAILABLE—The requested area of the file is temporarily disabled. It may be possible to access accounts with TINs having different ending digits.

5. NO xTIFnn–AREA IS DOWN—A TIF area is down, try TINs within other areas.

6. NO xTIFnn–AREA RESTRICTED— A TIF area is restricted, try TINs within other areas.

7. SYSTEM I/O ERROR-nnnnnn—An unusual input or output error encountered. Notify an RPA.

8. VALADD ERROR-NOTIFY CONTROL POINT— An error was encountered using ‘VALADD’ Subroutine. The National Office should be notified.

(1) Command Code FRM49, Single Input Format

(2) Record Element Description

(1) Command Code FRM49, Batch Input Format

(2) Record Element Description

(1) Command Code FRM49, Screen Invalid Responses

(2) Command Code FRM49, Invalid Responses

(3)

(1) Command Code FRM14, Single Input Format

(2) Record Element Description

(1) Command Code FRM14, Batch Input Format

(2) Record Element Description

(1) Command Code FRM14, Screen Invalid Responses

(2) Command Code FRM14, Invalid Responses

(3)

(1) Command Code TDIRQR, Input Format

(2) Record Element Description

(1) Command Code TDIRQR, Terminal Response

(1) Command Code TDIRQ Response Format

(1) Command Code TDIRQ, Sample Input Request Type Code ‘E’

(2) Record Element Description

(1) Command Code TDIRQ, Sample Input Request Type Code ‘T’

(1) Command Code TDIRQ, Sample Input Request Type Code ‘B’

(2) Record Element Description

(1) Command Code TDIRQ, Sample Input Request Type Code ‘C’

(2) Record Element Description

(1) Command code TDIRQ, Sample Input Request Type Code ‘S’

(2) Record Element Description