- 2.4.10 Command Codes EOREQ and EOCHG
- 2.4.10.1 Program Scope and Objectives
- 2.4.10.1.1 Background
- 2.4.10.1.2 Authority
- 2.4.10.1.3 Roles and Responsibilities
- 2.4.10.1.4 Program Management and Review
- 2.4.10.1.5 Program Controls
- 2.4.10.1.6 Terms and Acronyms
- 2.4.10.1.7 Related Resources
- 2.4.10.2 Command Code EOREQ
- 2.4.10.3 Command Code EOCHG
- 2.4.10.3.1 Valid Responses
- 2.4.10.3.2 Error Processing for CC EOCHG:—
- 2.4.10.4 Error Messages and Responses
- 2.4.10.5 Command Code EOCHG Messages
- 2.4.10.6 Acceptable Address Abbreviations
- Exhibit 2.4.10-1 Command Code EOREQ
- Exhibit 2.4.10-2 Command Code EOCHG
- Exhibit 2.4.10-3 Command Code EOCHG—Consistency Checks
- Exhibit 2.4.10-4 Command Code EOCHG—Combined Consistency
- Exhibit 2.4.10-5 Command Code EOCHG—Organization Type Consistency
- Exhibit 2.4.10-6 Command Code EOCHG—Other Consistency Requirements
- Exhibit 2.4.10-7 Command Code EOCHG—Activity Codes For nnn
- Exhibit 2.4.10-8 Command Code EOCHG—Valid 1120 FR and Subsection Code
- Exhibit 2.4.10-9 Command Code EOCHG—Valid FR 990 and Subsection Code
- 2.4.10.1 Program Scope and Objectives
Part 2. Information Technology
Chapter 4. IDRS Terminal Input
Section 10. Command Codes EOREQ and EOCHG
2.4.10 Command Codes EOREQ and EOCHG
Manual Transmittal
January 16, 2025
Purpose
(1) This transmits revised IRM 2.4.10, IDRS Terminal Input, Command Codes EOREQ and EOCHG.
Material Changes
(1) Updated owner organization and Signature for Chief Information Officer.
(2) IRM 2.4.10.1 Modified Internal Controls to be compliant with new requirements.
(3) Changed Wage & Investment (W&I) to Taxpayer Services (TS).
Effect on Other Documents
IRM 2.4.10, dated November 14, 2023, is superseded.Audience
LB&I, SB/SE, TE/GE, Taxpayer Services (TS).Effective Date
(01-16-2025)
Rajiv Uppal
Chief Information Officer
-
Purpose: The primary purpose of this IRM chapter is to provide instructions in the use of IDRS Command Codes EOREQ and EOCHG for entering Exempt Organization entity changes. For procedural instructions pertaining to when an E.O. entity change is to be input and exactly what data elements are to be entered see IRM 3.13.12, EO Account Numbers.
-
Audience: LB&I, SB/SE, TE/GE, Taxpayer Services (TS).
-
Policy Owner: The Chief Information Officer (CIO) is responsible for overseeing all aspects of our systems that operate the nation’s tax infrastructure.
-
Program Owner: Customer Service
-
Primary Stakeholders: Taxpayer Services (TS), Large Business and International (LB&I), Small Business Self-Employed (SB/SE), and Tax Exempt and Government Entities (TE/GE).
-
This IRM and the contained sections provide the user the necessary information on how to use the Command Code EOREQ and EOCHG.
-
EOREQ and EOCHG were developed to input Document Code 80 and 81 Entity Changes for Exempt Organization (EO) accounts on the Business Master File (BMF).
-
The Entity Command Codes Project Lead is responsible for reviewing and implementing the Work Requests the affect EOREQ and EOCHG and for updating the contents of this IRM.
-
The Command Codes of EOREQ and EOCHG are managed by Work Requests which are submitted for changes and also by tickets which are submitted by users for corrections.
-
Acronyms Unique to IDRS.
Acronym Definition IMF Individual Masterfile BMF Business Masterfile TIF Taxpayer Information File TC Transactions Code CC Command Code
-
Valid Responses—For CC EOREQ the valid response is a generated input format for CC EOCHG. For CC EOCHG the input screen will be returned with "REQUEST COMPLETED" message. Only when this response is returned will a file update occur and an output transaction be created.
-
Error Processing for CC EOREQ—For CC EOREQ if any error check is failed the input screen is returned with a message specifying the error condition. Exception: if CC EOREQ is input for an account not on the BTIF and the Name Control or any of the Case Control data fields is invalid or missing, the screen is returned with asterisks after the field input positions and the error message will be "PLEASE CORRECT INVALID DATA" . Any data entered outside the fixed field input positions will be ignored and blanked out on the response.
-
Input Format—The input format generated as a valid response to CC EOREQ, uses various means of defining the input data field positions. For error responses the input screen is returned basically unchanged except to add Error Indicators (asterisks) for appropriate fields and to regenerate format literals in certain cases. The error response screen is then used as the input format after the offending data is corrected.
-
There are three types of variable fields: fixed length; multiple fixed length such as Classification Codes (CL) or E.O. File Folder Number (FF); and variable length such as Sort Name (SN) or Remarks (RM). The variable length fields must fall within their specified maximum and minimum length range and are the only variable fields allowed to contain a blank. The multiple fixed length fields must meet one of their specified lengths and are never "padded out" to maximum size with blanks: "CLnn[slashb][slashb] " is invalid.
-
All variable fields input must be correct as to their format before the Command Code will attempt to validity check the actual data content of the field.
-
The Remarks field is the only variable Field that must be entered for every CC EOCHG input.
-
-
For CC EOREQ the valid response is a generated input format for CC EOCHG.
-
For CC EOCHG the input screen will be returned with a " REQUEST COMPLETED" message. Only when this response is returned will a file update occur and an output transaction be created.
-
Initialization Checks:—These assure that no attempt has been made to change the tax account identification data, that the minimum required data fields have been input (for example, a valid Document Code and Transaction Code), and that all the other data entered is in the correct format. As soon as one of these checks is failed, error checking stops and the error response is generated with an error message for the specific condition.
-
Data Validity and Consistency Checks:—After the initialization checks are passed, data fields are subjected to validity and consistency checks. An error response is not generated until all the possible checks completed and the erroneous or missing fields are identified.
-
Each field input is first validity checked. Only if it passes validity (range, format, etc.) are the consistency checks, specified for that input field against other fields, performed. Example, suppose element " A" requires element "B" to be input and to be "888" . If element "A " fails its validity check, element "B" would not be error marked if not input or if input as "999" . When element "A" is corrected but not " B" , then element "B " is an error marked on the next input.
-
If an element fails a consistency check, all the elements relevant to that check will be error marked. For example, if a consistency check is required between elements "A" and "B" when Document Code is "81" and Transaction Code is " 016" , then the Doc. Code and Trans. Code will be error marked as well as element "A" if element "B" is not input.
-
The error response screen will display asterisks for all elements input which fail a validity or consistency check and for missing elements with fixed entry positions. The error message displayed will be "FIELD MISSING FROM VARIABLE AREA" if one or more required Variable Fields, except Remarks, is missing. If no Variable Fields are missing the error message will be "PLEASE CORRECT INVALID DATA" unless all fields but Remarks are correct, in which case the message will be "REMARKS INVALID OR MISSING" .
-
-
ACCOUNT IS ALREADY ON FILE—The account was created through some other source subsequent to ENMOD response and before completion of EOREQ.
-
PRIOR CMND CD MUST BE ENMOD—EOREQ was input but not preceded by ENMOD.
-
ID INFO CHANGED-RESTART—Generated data consisting of TIN and name control on line 1 of display has been altered. Restart with ENMOD and EOREQ.
-
INVALID CMND CD ROUTED TO EOREQ System error contact CSA.
-
MEMO ACCT-MODULE PRESENT—CC EOREQ has been attempted for a type of entity which will not accept entity changes.
-
NON-DUMMY NMF ACCT MUST BE ON TIF—NMF entity change processing requires that a full account be present on the TIF.
-
TIF NC INV ( )—The name control on the TIF account does not meet standard validity criteria (see IRM 2.3.8). For dummy accounts use CC ACTON to correct TIF account name control. If condition ever occurs on full account (real), the account advises System Control Point.
-
TIP FILE NOT AVAILABLE—The TIP file that is used to validate TC 000 EIN's is not available at the moment. Re-input the entry.
-
TIN EXISTS ON MF—The TIN and name control are valid on the NAP and the TC 000 INTEND IND is set indicating that a TC 000 transaction is about to be entered. These conditions are in conflict.
-
INVALID TIN TYPE ON NAP REQUEST-REC—The wrong type of TIN indicator is input (example EIN with a "R " , the valid codes are blank space or "P" ). This response indicates a program error—notify the IDRS Support Staff.
-
TIN NOT ESTABLISHED ON MF—The TIN is not on the NAP.
-
CRS/NAP ACCESS NOT AVAILABLE—The communication lines to the NAP file are not available. The transaction cannot be input. Notify your manager or the IDRS Support Staff. Retry input later.
-
SYSTEM ERROR ON ACCESS/UPDATE—The communication lines to the NAP file are not available. The transaction cannot be input. Notify your manager or the IDRS Support Staff. Retry input later.
-
NATIONAL FILE NOT AVAILABLE—The NAP file is not available.
-
SSN NOT ON MF AS VALID OR INVALID-CC INOLE CAN BE USED TO VALIDATE DM-1 SSN/NAME—The SSN entered was not found on either the valid or invalid segments of the Master File. CC INOLE can be used to research the DM 1.
-
ACCOUNT FOUND ON OPPOSITE VALIDITY-CC INOLE CAN BE USED TO VALIDATESSN/NAME—The SSN entered was not found on the segment of the MasterFile as indicated by the display File Source Code entered. However, it was found on the opposite segment. CC INOLE can be used to research the account.
-
TIN IS NOT ON THE EPMF OR THE BMF—The EPMF account's EIN cannot be found on either the EPMF or BMF Master Files.
-
TIN IS NOT ON THE EPMF, IS ON THE BMF—The EPMF account's EIN cannot be found on the EPMF but it does exist on the BMF.
-
The first 35 characters of the primary name from the NAP file are displayed on the screen—The TIN matches the TIN on the NAP file but the name controls do not match.
-
If the TIN matches the TIN on the NAP file and the name controls match, normal processing will continue.
-
FOUNDATION-CD MUST = 99—TC016 with subsection changing from 03 to other requires foundation code 99.
-
EXISTING ACCOUNT MUST HAVE A PARENT EIN—This applies to EO-STATUS 27 input.
-
SUBSECTION-CD MUST BE 04- Either input or existing SUBSECTION-CD.
-
CC EOCHG Initialization Type Error Messages:
-
"INVALID CMND CD ROUTED TO EOCHG" —Input for another Command Code systematically routed to the CC EOCHG program. This error should never occur; if it does notify SC RPA Staff
-
"PRIOR CMND CD MUST BE EOREQ" —CC EOCHG was not preceded by EOREQ.
-
"DOC CODE INVALID" —Document Code was not input as "80" or "81" .
-
"TRANS CODE INVALID" —Input Transaction Code must be input as "000" , " 012" , "013" , "014" or "016" .
-
"ID INFO CHANGED-RESTART" —TIN and/or Name Control have been changed from those displayed by CC EOREQ response.
-
"DATA IN NON-INPUT FIELD" —The generated literals at the end of a data field have been modified (other than completely blanked out).
-
"EXTRA DATA WITH DEFINER CD F" —There is unallowable extraneous data present with Transaction Definer Code F. Only the following fields should be present: Doc. Code, Transaction Code, Affiliation Code, From Group Exemption Number and Remarks.
-
"EXTRA DATA WITH STATUS CD 28" —There is unallowable extraneous data present with Status Code 28. Only the following fields should be present: Doc. Code, Transaction Definer Code B, From Group Exemption Number, Transaction Code, and Remarks.
-
"PD AF-CD6/8 AND FR-GROUP EXTRA DATA" —There is unallowable extraneous data present with AFFILIATION CD 6 or 8 and FROM GROUP EXEMPTION NUMBER. Only the following fields may be present: Doc Code, Transaction Code, Transaction Definer Code, Affiliation Code, From Group Exemption Number, Status, Deductibility Code, Foundation Code and Remarks.
-
"V85 AF-CD6/8 AND FR-GROUP EXTRA DATA" —There is unallowable extraneous data present with AFFILIATION CD 6 or 8 and FROM GROUP EXEMPTION NUMBER. Only the following fields may be present: Doc Code, Transaction Code, Transaction Definer Code, Affiliation Code, From Group Exemption Number, Status, Deductibility Code, Foundation Code and Remarks.
-
"V90 AF-CD6/8 AND FR-GROUP EXTRA DATA" —There is unallowable extraneous data present with AFFILIATION CD 6 or 8 and FROM GROUP EXEMPTION NUMBER. Only the following fields may be present: Doc Code, Transaction Code, Transaction Definer Code, Affiliation Code, From Group Exemption Number, Status, Deductibility Code, Foundation Code and Remarks.
-
FIX AF-CD6/8 AND FR-GROUP EXTRA DATA—There is unallowable extraneous data present with AFFILIATION CD 6 or 8 and FROM GROUP EXEMPTION NUMBER. Only the following fields may be present: Doc Code, Transaction Code, Transaction Definer Code, Affiliation Code, From Group Exemption Number, Status, Deductibility Code, Foundation Code and Remarks.
-
"PD DEFE AF-CD6/8 AND FR-GROUP EXTRA DATA" —There is unallowable extraneous data present with AFFILIATION CD 6 or 8, DEF-CD E and FROM GROUP EXEMPTION NUMBER. Only the following fields may be present. Doc Code, Transaction Code, Transaction Definer Code, Affiliation Code, From Group Exemption Number, Status, Deductibility Code, Foundation Code and Remarks.
-
-
CC EOCHG Consistency and Validity Type Error Messages:
-
"FIELD MISSING FROM VARIABLE AREA" —One or more Variable Field elements required by consistency check to be present have not been input. Those input elements requiring the missing field(s) will be asterisked.
-
"INCORRECT TIN FOR EOCHG-RESTART" .
-
"TC-DEF-CD B MUST BE PRESENT WITH A" .
-
"EXTRA DATA WITH STATUS CD 29" -- Exhibit 2.4.10-6.
-
"**CLSF-CD MUST = 1**" .
-
"PLEASE CORRECT INVALID DATA" —One or more input elements is (are) incorrect. An * (asterisk) will be generated to identify the invalid or inconsistent data input fields.
-
"REMARKS INVALID OR MISSING" —The Variable Field "REMARKS" was not input.
-
"TRANS CODE INVALID" .
-
"DOC CODE INVALID" .
-
"EXTRA DATA WITH STATUS CD 97" —Flagged field not allowed with STATUS-CD 97.
-
"STATUS CD 97 MUST HAVE TC-DEF B" .
-
"STATUS CD 97 MUST HAVE DOC CD 80" .
-
"STATUS CD 97 MUST HAVE TC 13, 14, 16" .
-
"STATUS CD 97 MUST HAVE FR1120/1041" .
-
"STATUS CD 97 MUST HAVE FYM" .
-
"BOTH HOSP-IND AND TRANS-DEFINER-CD H REQUIRED"
-
"ADDITIONAL FIELDS NOT ALLOWED WITH HOSP-IND"
-
"HOSP-IND, ACCOUNT IS NOT SUBSECTION 03"
-
"HOSP-IND, CURRENT STATUS IS nn"
-
"HOSP-IND 02, ACCOUNT FOUNDATION NOT 12"
-
"HOSP-IND SAME AS HOSP-IND ON ACCOUNT"
-
"HOSP-IND INPUT, USER PROFILE MUST BE 40522, 40525, 40528 OR 40775"
-
"DEFINER L MUST BE BY ITSELF" -- Definer L is the only definer allowed
-
-
Other Error Messages:
-
"xTIFn NOT AVAILABLE" —The portion of the TIF for this taxpayer's account not currently available for processing. (x = I, B or Z TIF (n = 1–5 TIF segment).
-
"ACCESS TEMPORARILY DENIED-RETRY" —The portion of the TIF for this taxpayer's account was not available for update at the moment of input. Re-input the entry.
-
"TIP FILE NOT AVAILABLE" —The TIP File that is used to validate TC000 EIN's is not available at the moment. Re-input the entry.
-
-
The following tables lists the acceptable address abbreviations.
Air Force Base AFB and & Avenue AVE Boulevard BLVD Building BLDG Care of % Drive DR East E General Driveway GEN DEL Highway HWY In Care of % North N Northeast NE Northwest NW One-Fourth 1/4 One-half 1/2 One-quarter 1/4 Partnership PTR P.O. Box No. PO BOX Road RD Route, Rt. or Rte RT RFD RR Rural Delivery RR Rural Route RR South S Southeast SE Southwest SW Street ST See IRM 3.27.68, ADP Systems Code For Standard State Abbreviations.
Use this Command Code to request a CC EOCHG.
Screen Display:

Please click here for the text description of the image.
Record Element Description:
Position | Element | Line | Element Name and Description |
---|---|---|---|
1–5 | 1 | 1 | Command Code EOREQ—required |
20 | 2 | 1 | TC 000 INTEND TO BUILD INDICATOR—Required if TC 000 is to be built. |
1–4 | 3 | 2 | Name Control—Must meet Standard criteria for an EIN Name Control per IRM 2.3.8. |
6 | 4 | 2 | Case Status Code—"A" or "C" per IRM 2.7.18. |
8–11 | 5 | 2 | Case Control—Must be a valid Case Category Code per IRM 2.7.18. |
13–18 | 6 | 2 | IRS Received Date—An * (asterisk) in the first position will generate current date. Otherwise, a date in MMDDCCYY format, which is not later than the current date less one year, must be input. * (note) * CC = Century |
1–10 | 7 | 2 | ACTIVITY CODE—All blanks, or 02-10 characters with no embedded blanks. |
NOTE: elements 2-6 must be input if the taxpayer account is not on the TIF. |
Use this Command Code to enter the EO entity change to the account on the BTIF.
Screen Display:

Please click here for the text description of the image.
Record Element Description:
Subsection Code:
CLASSIFICATION CODE | DOC. CODE | SUBSECTION CODE |
---|---|---|
81 | 01-20, 23, 26, 27, 70 , 71 or 81. | |
1 | 80 | 01-27, 29, 40, 50, 60, 70, 71, 80, 81, 82 or 90-93 |
1 | 80 | 28 |
2 | 03–06, 09 29 or 12-14 | |
3 or 4 | 03-06, 12 or 29 | |
5-8 | 03 |
Affiliation Code:
AFFILLIATION-CD | TRANSACTION-CD | DOCUMENT-CD | TRANSACTION-DEFINER-CD. | |
---|---|---|---|---|
1–3 | 000 | 80 | /// | |
• Subsection Code must not = "26" , "27" , "71" or "81" . | ||||
• STATUS-CD must = 01 or 02. | ||||
• NEW-GROUP-EXEMPTION-NUM must not be input. | ||||
1–3 | 016 | 80 | C | |
If Subsection Code not = "26" , "27" , " 71" or "81" then | ||||
If NEW-GROUP-EXEMPTION-NUM is input it must be 9999 | ||||
FRM-GROUP-EXEMPTION-NUM must = 0001-9998. | ||||
Else | ||||
Transaction-Definer-Cd must be blank. | ||||
6 or 8 | 016 | 80 | C | |
If Subsection Code not = "26" , "27" , " 71" or "81" then | ||||
Either the NEW-GROUP-EXEMPTION-NUM or the FRM-GROUP-EXEMPTION-NUM must be input. | ||||
If the NEW-GROUP-EXEMPTION-NUM is input it must be equal to 0002-9998. | ||||
Else | ||||
Transaction-Definer-Cd must be blank. | ||||
7 or 9 | 000 | 80 | //// | |
• Subsection Code must not = "26" , "27" , "71" or "81" | ||||
• STATUS-CD must = 01. | ||||
NEW-GROUP-EXEMPTION-NUM must = 0002–9998. | ||||
7 or 9 | 016 | 80 | C | |
If Subsection Code not = "26" , "27" , " 71" or "81" then | ||||
NEW-GROUP-EXEMPTION-NUM must equal 0002–9998. | ||||
Else | ||||
Transaction-Definer-Cd must be blank. | ||||
6–9 | 016 | 80 | F | |
7 or 9 | 016 | 81 | C or D | |
If Subsection Code = "26" , "27" , " 71" or "81" then | ||||
Transaction-Definer-Cd must be blank | ||||
Else | ||||
FRM-GROUP-EXEMPTION-NUM must equal 0002–9998. | ||||
3 | 016 | 81 | E | |
If Subsection Code not = "26" , "27" , " 71" or "81" then | ||||
FRM-GROUP-EXEMPTION-NUM must equal 0002-9998. | ||||
NEW-GROUP-EXEMPTION-NUM must equal 9999. | ||||
Else | ||||
Transaction-Definer-Cd must be blank. |
Organization Type:
TYPE OF ORGANIZATION | SUBSECTION CODE |
---|---|
1 | 01-16,19-20, 23, 25-27, 29, 40, 50, 60, 70, 71, 80 or 81 |
2 | 03-15 17-22, 24-27, 29 or 81 |
3 | 03, 26, 27, 50, 71, 80, or 93 |
4 | 26, 27, 40 or 71 |
5 | 01-21, 23, 26-27, 29, 40, 50, 60, 70 or 71 |
6 | 26, 27, 71, 91 or 92 |
Other Requirements:
If the Doc Code is "80" and the Trans. Code is "000" , then | ||
---|---|---|
STATUS CODE | SUBSECTION CODE | Other Requirements |
01 | 01-25, 40, 50, 60, 70 or 80 | — |
07 | Must Not Be Input | 990T FR Must Be 1 and 990 FR Must be 6 |
10 | Must Not Be Input | 990 FR Must Be 6 |
11 | Must Not Be Input | 990 FR Must Be 6 |
12 | 90 | 5227 FR Must Be 1 or 2 |
12 | 91 | 990 FR Must Be 1 or 2 |
12 | 92 | 990PF FR Must Be 1 |
34 | 82 | Primary Name must be input, Mailing Street Address must be input. Classification Code must = 1. FYM must be input. |
35 | Must Not Be Input | Valid FYM must be entered. NON-REQUIRED-FR-CD must be "1" . Primary Name must be entered. |
36 | Must Not Be Input | 990–FR-CD must be entered. Primary Name must be entered. |
40 | Must Not Be Input | Non Required FR Must Be 1 |
If the Doc Code is "80" and the Trans Code is "012 " , then |
||
STATUS CODE | SUBSECTION CODE | Other Requirements |
01, 06 | 01-23,40,50,60, 70 or 80 | — |
06, | 99 or Not Input | — |
07, 10, 11 or 40 | ||
12 | 90-93 | — |
18 | 92 | — |
19 | 03 | FOUNDATION CODE Must Be 03 or 04 |
If the Doc Code is "80 " and the Trans. Code is "016" and (Subsection Code not = "26" or "27" or "71" or "81" ), then Transaction Definer Code "B" must be input. |
||
STATUS CODE | TRANS DEFINER | FROM GROUP EX NUM | OTHER DATA |
---|---|---|---|
28 | B Must Be Input | Must Be Input | Only Remarks |
01, 06,07,10-12, 18-20, 22-26, 40 42 or 70 72 | B Must Be Input | — | — |
If the Doc. Code is "80" and the Trans Code is "016 " , then |
|||
EO STATUS CODE | SUBSECTION CODE | OTHER REQUIREMENTS | |
01 | — | RULING-DT required | |
34 | 82 | — | |
If the Doc. Code is 81, then the Transaction Code must be 016 |
|||
STATUS CODE | TRANS DEFINER | FROM GROUP EX NUM | OTHER DATA |
01, 20, or 26 | B or D Must Be Input | — | — |
29 | B Must Be Input | Must Be Input | Only Remarks |
30 | B Must Be Input | — | Only Remarks |
31 | B Must Be Input | — | Only Remarks |
32 | B Must Be Input | — | Only Remarks |
33 | B Must Be Input | — | Only Remarks |
34 | B or AB Must Be Input | — | Only Remarks |
ACnnn Values:
For nnn—see values below: | ||||
---|---|---|---|---|
001-008 | 179-181 | 296-301 | 409-543 | 931-934 |
029-047 | 199-213 | 317-328 | 559-569 | 990 |
059-065 | 229-237 | 349-356 | 572-575 | 991 |
088-094 | 249-254 | 379-382 | 600-603 | 994-995 |
119-126 | 259-269 | 398-408 | 900-928 | 998 |
149-169 | 279-288 |
The Subsection Code must be input. See the table below for valid combinations of 1120 FR and Subsection Code as well as any additional consistency checks:
FR 1120 | SUBSECTION CD | FR 990 | FR 990F | FOUNDATION CD | |
---|---|---|---|---|---|
01 | 03 | _ | 1 | 03 or 04 | |
01 | 12 | 01 | _ | _ | |
03 | 12 | 01 | _ | _ | |
04 | 15 | 01 | _ | _ | |
09 | 03 | 01, 02 or 13 | _ | 09 or 18 | |
09 | 01, 02, 04-23, 50, 60 or 70 or 82 | 01 or 02 | _ | _ |
The Subsection Code must be consistent with the 990 FR. See The following table for valid combinations, and other consistency checks that apply.
FR 990 | SUBSECTION CD | STATUS CD | FOUNDATION CD | CLASS CD |
---|---|---|---|---|
[slash0]OR 00 | 81 | _ | _ | 1 |
01 | 02, | _ | _ | _ |
04-20, 22, 23, 24, 25, 50, 60, 70 or 91 | _ | _ | ||
01 | 03 | _ | 09-18, 21-25 | _ |
01 | 71 | _ | ANY VALID | 1 |
01 | 26, 27 | _ | 1 | |
01 or 02 | 82 | 34 If TRAN-DEF-CD = 'B' or 'AB' | N/A | 1 if TRAN-DEF-CD = 'A' or 'AB' |
02 | 04-20, 22, 23, 24, 25, 50, 60, 70 or 91 | _ | _ | _ |
02 | 03 | _ | 09-18, 21-25 | _ |
02 | 26, 27 | _ | 1 | |
02 | 71 | _ | ANY VALID | 1 |
03 | 02, 04-20, 23, or 70 | _ | _ | _ |
03 | 03 | _ | 09–18, 21-25 | _ |
03 | 26, 27 | _ | 1 | |
03 | 71 | _ | ANY VALID | 1 |
04 | 21 | _ | _ | _ |
06 | 03 | _ | 10 | _ |
06 | Must be 99 or Not Input | 07, 10 or 11 | _ | _ |
07 | 01 | _ | _ | |
13 | 03 | 09–18, 21-25 | 7 | |
13 | 71 | ANY VALID | 1 | |
14 | 01, 04-20, 22-25, 50 or 60 | _ | _ | _ |
14 | 03 | _ | 09-18 | _ |
14 | 26 | _ | _ | 1 and TRAN-DEF-CD must = 'ABC' |
14 | 26, 27 | _ | _ | 1 |
14 | 71 | ANY VALID | 1 |