7.21.8  EDS Unpostables

7.21.8.1  (01-01-2003)
Overview

  1. Instructions are provided on correcting unpostable under the Employee Plans/Exempt Organizations Determination System (EDS).

  2. EDS unpostables occur when applications are entered or closed and could not post to the Master File Pipeline Subsystem (MPS) of EDS, located in the CSPC.

    1. MPS is the "old" EACS system and serves as a conduit to the master files.

    2. Once the records successfully post to MPS, they are sent to master file on the weekly posting cycle (usually Fridays) and Detroit Computer Center on the monthly 4/4/5 MIR cycle.

  3. These procedures are for DPO Unpostable Clerks.

7.21.8.2  (01-01-2003)
Daily Batch Run

  1. EDS openings (establishments) and closings get to MPS EACS by the daily batch run. As cases are entered and the closings approved, the MF status is automatically updated to mark the records for the batch run. The changing of the MF status is explained in more detail below.

  2. When the marked records are processed through the daily batch run, application opening and closing data are checked using specific validity and consistency checks. If all checks are passed, the transaction records or case records are generated and written to a file.

  3. The validity and consistency checks used in the batch are the same as those described for each screen item in the EDS User Guide.

  4. A case can be opened and closed in the same day. The MF status will instruct the batch to create both an opening transaction and a closing transaction in the same file. (See MF status 4, below.)

    Note:

    An update after closing would not need to be done the same day. The data can be updated before the batch is run.

  5. The file described in (3) above is uploaded to the NILE in the CSPC for a tape to be made for MPS which is on the CSPC mainframe computer. An additional validity and consistency check is made on the application opening and closing data for name control and zip code, when the transaction records are added to MPS.

  6. Unpostables can occur in either the EDS daily batch run (EDS unpostables) or in the MPS run (EACS unpostables). The EDS daily batch run should find all the errors in the records before the file is transmitted to MPS.

  7. There are two checks the daily batch run can not catch:

    1. They are consistency checks on the zip code and state, and

    2. EIN and Name Controls (OLE).

    Note:

    These unpostables will occur only in MPS. If MPS unposts a case for any other reason, contact your EDS Unpostable Clerk. He or she should inform Headquarters so the daily batch program can be corrected.

7.21.8.2.1  (01-01-2003)
Reports

  1. Reports are generated both from the daily batch run and MPS (EACS).

    1. When EDS errors are found, the daily batch report lists the cases and the error(s) found.

    2. The MF status field is updated with the unpostable code and the record is NOT sent to MPS.

    3. These errors (unpostables) require an EDS correction.

  2. MPS programs are run on a daily basis and a report is generated with run controls and any errors found. The availability of this report daily is dependent on the time ISD runs the daily batch runs and transmits the EO files. The Detroit tables will be more accurate if (a) below can be achieved.

    1. lf the daily batch is run in the evenings and the files are transmitted in time for the EACS run, the report will be available the next day.

    2. If the daily batch is run in the evenings and the files are transmitted after the time for the MPS run, the report will be available in two days.

    3. If the daily batch is run in the mornings and the files are transmitted in time for the MPS run, the report will be available in two days.

  3. When the MPS reports are received back on the district’s system, a program is run against the report to update the MFstatus with unpostable codes and closings. History records are created for these updates and for opening and update of MIR data postings. The MPS unpostables also require an EDS correction.

7.21.8.3  (01-01-2003)
Specific Instructions

  1. Unpostables should be resolved by the Adjustments Unit who will research for the correct data, update the corresponding items on EDS. (The Adjustments Unit must be in the Employee Master file to access ICS).

  2. Each unpostable from the daily batch run will be listed on the batch run report with the unpostable code(s) or reason the case did not post (see Exhibit 8–1 for the list of unpostable codes).

    1. When a case unposts on EDS, the MF status in the Query/Update Master File screen is updated to the unpostable code or if there was more than one unpostable the last unpostable code found.

    2. The daily batch run report is the only report that lists all the reasons a case did not post.

  3. A report may be generated in the Management Information System to print outstanding EDS unpostable cases. See Chapter 9 for instructions in running this report.

  4. Find correct entry for each error/unpostable by looking in the case file. If the correct entry cannot be found, ask the specialist who closed the case to determine the correct entry.

  5. Make correction(s) in the Query/Update Master File Screens. These screens may be found in Option 1 of the ICS Main Menu of the EDS system. All corrections will be made by the Determinations Primary Office.

    1. When all updates are made, a "Y" should be entered in the MF item to resend the record to MPS.

    2. All items can be corrected by any login if the case is open.

    3. Once a case is closed, all items can be updated except the status and hours. The status and hours can be updated in Option 5 of the Update Master File screen and only by the Adjustments Unit. The purpose of updating these items after closing is to correct data on the Detroit Data Center tables. The MF code to send the case to MPS can only be updated by the Adjustments Unit.

7.21.8.4  (01-01-2003)
Definitions

  1. Opening Record — The opening or establishment record is sent to MPS after an application is entered in DTS. An opening record is sent to allow Cincinnati Submission Processing Center (CSPC) personnel research capability with the command codes PLINQ and PLINF. Opening data is also sent to Detroit Computing Center to be counted in the MIR tables as a receipt. These records are sometimes referred to as PAO records.

  2. Closing Record — The closing record is sent to MPS after the case is closed and approved through the Case Approval Screen. This record closes off the opening record at the CSPC. The closing data is also sent to Detroit Computing Center to be counted in the MIR tables as a closing. These records are sometimes referred to as PCO records.

  3. Update Record — Option 5 in the Query/Update Master File screen allows MIR items to be updated. An update record can be sent to MPS after the record has been closed and MIR items have been updated. MPS sends the update record to the Detroit Computing Center. These records are sometimes referred to as PUO records.

  4. EC and IC Records — A "case" is stored in a number of tables in the database of EDS. For a case to be brought up in the Update Master File screen it must have a record (with the same case number) in each of the EC and IC tables. The record contains entity information, such as name, address, form number, etc. The EC records contains case information, such as, benefit type, subsection, status, etc. The IC record contains the MF indicator and the date.

  5. PCCF — Plan Case Control File, the name of the database used for MPS system. The PCCF is the holding area until transactions can be sent to master file.

7.21.8.5  (01-01-2003)
Master File Codes

  1. Master File (MF) Codes describe where the EDS record is in relation to MPS. Below is a list of MF Codes and their meanings:

    0 (zero) — Opening record waiting to be sent
    1 — Opening record sent
    2 — Closing record waiting to be sent
    3 — Closing record sent
    4 — Both opening and closing records waiting to be sent
    11 — Letter Generation record—not sent
    12 — Update MIR data after closing waiting to be sent
    13 — Update MIR data after closing sent
    14 — Closing record bypass EIN check
    30 — Closing Record Posted to MPS

    2000–2999 — MPS Opening Unpostable (When Both Opening and Closing Records were Sent)
    3000–3999 — MPS Update MIR Closing Data Unpostable
    4000–4999 — MPS Closing Unpostable
    5000–5999 — MPS Opening Unpostable
    6001–6999 — Unpostables codes for Update MIR data after closing
    7001–7999 — Unpostable codes for Opening records when both opening and closing records were sent
    8001–8999 — Unpostable codes for Closing records
    9001–9999 — Unpostable codes for Opening records

  2. MF Unpostables Codes are 4 digits. The first digit is the following:

    9 — Opening Record Unpostable
    8 — Closing Record Unpostable
    7 — Opening Record Unpostable when Opening and Closing records were sent simultaneously (or together in the same file).
    6 — Update after Closing Record Unpostable
    5 — MPS Opening Record Unpostable
    4 — MPS Closing Record Unpostable
    3 — MPS Update after Closing Record Unpostable
    2 — MPS Opening Record Unpostable when Opening and Closing records were sent simultaneously (or together in the same file).

  3. The last three digits are the unpostable code.
    For example:

    1. If an unpostable code is displayed as 9092, the State Code is invalid on an opening record.

    2. If the code is displayed as 8092, the State Code is invalid on a closing record.


    The unpostable codes are listed in Exhibit 8–1.

  4. To change the unpostable code to a code to send the record to MPS, a "Y" must be entered in the MF field. A "Y" will change the unpostable to the following:

    9XXX will be updated to 0 (zero)
    8XXX will be updated to 2
    7XXX will be updated to 4
    6XXX will be updated to 12
    5XXX will be updated to 0 (zero)
    4XXX will be updated to 2
    3XXX will be updated to 12
    2XXX will be updated to 4

  5. The batch run will update a

    • "0" (zero) when sent to MPS as a opening record,

    • "2" when sent as a closing record,

    • "4" when sent as both opening and closing records

    • "12" when sent as a MIR update after closing

    • 0 (zero) will be updated to 1 after the batch run

    • 2 will be updated to 3 after the batch run

    • 4 will be updated to 3 after the batch run

    • 12 will be updated to 13 after the batch run

    Note:

    After the batch run is complete the MF Code will reflect the record has been sent.

7.21.8.6  (01-01-2003)
Exceptions

  1. All errors may be corrected through the Query/Update Master File Screen except the errors listed below. These cases must be corrected by your EDS Unpostable Clerk.

    1. Case Number is invalid (000)

    2. Control Date is invalid (010)

    3. Area Office Code is invalid (005)

    4. Type Request is invalid (013)

    5. No matching kd record (999)

    6. No matching ec record (998)

    7. Inconsistent Closing Cd and Proposed Closing Cd (055)

    Note:

    The errors listed in 1 (a)–(f) should not occur if the record has been entered through DTS and the data has not been altered outside of EDS. If these errors should occur see your EDS Unpostable Clerk.

  2. If the error listed is "File Folder Number is invalid" (001), the File Folder Number (FFN) may be updated unless the error is in the first two digits (D.O. Code portion of the FFN). If the error is the first two digits, the case must be corrected by your EDS Unpostable Clerk.

7.21.8.7  (01-01-2003)
MPS Run Unpostables

  1. EDS transaction records are processed through programs at the CSPC. The programs that produce MPS unpostables are labeled EDS0101 and EDS0102.

    1. The program EDS0101 screens the records to see if the tape was sent to the wrong CSPC and if there are duplicate case numbers.

    2. The program EDS0102 performs the validity and consistency checks for EO records.

  2. If the records pass through two of the programs, they will be marked to update the EO/BMF based on the weekly posting cycles (usually Fridays).

  3. The data used for management information reports will be spun off to the Detroit Computing Center to be included in the MIR tables based on the monthly 4/4/5 posting cycles.

7.21.8.7.1  (01-01-2003)
MPS Run Reports

  1. The run report is generated daily and is available for Information Systems Division (ISD) to download to the district’s EDS system.

    1. ISD should print this run report daily and give it to TE/GE.

    2. Follow-up should be made. The report lists each EDS01 and EDS02 run.

  2. Run controls are totals of records

    1. input to MPS,

    2. added (established), closed and updated (MIR data updated), and

    3. unpostable

    Note:

    Other data listed is pertinent to the records being marked for master file and Detroit Computing Center.

  3. The run report also prints out each case number that was accepted by MPS. The case numbers accepted plus those that were unpostable should equal the total records sent.

7.21.8.7.2  (01-01-2003)
Message Lines

  1. Message lines will be printed on the report with the item that is not valid or consistent with another field. These message lines are read by the nightly batch run to update the MF status with the unpostable code. These reports only need to be read to compare the run controls and work any unpostables that are not in the UNP format.

  2. Below is an example of UNP and OLE format. All UNP and OLE lines will print in the nightly batch run report in a format that can be read without a template.

    • UNP|315432000EO|PCO|100|315123456|001

    • UNP|315001000EO|PAO|100|311234567|000

    • OLE|311500101EO|319500100|ANYE|ANY EXEMPT ORGANIZATION

  3. If the nightly batch run can not update an EDS record, a message line will be printed in the batch report. See your EDS Unpostable Clerk to resolve the record problem. Once the record is fixed, the unpostable can be resolved.

  4. There are two unpostable codes that will not update the MF Code. The number of these unpostables will be printed on the nightly batch report.

    1. 993 — Opening record sent a second time.

    2. 990 — Closing record sent a second time.

7.21.8.8  (01-01-2003)
Run Controls Comparison

  1. After the nightly batch run has processed the records from the CSPC Run Report, a report is generated listing the unpostables in a more readable format and run controls of the updates to the EDS database. See Exhibit 8.2 for a sample of this report.

  2. The heading of the report lists the following:

    1. The date ISD processed the CSPC Run Report.

    2. The file name of the CSPC Run Report.

    3. The date the CSPC processed the transaction files.

    4. The date the CSPC processed the transactions files were created.

  3. Compare dates to ensure the CSPC has processed every transaction file the district has sent. EDS batches are run daily. There should be report listing dates of transaction files for every day of the week. If this does not happen, contact your Unpostable Clerk. The Unpostable Clerk will coordinate with ISD to determine why there are dates missing. The sooner problems are identified, the easier it will be for ISD to remedy the situation.

  4. The Unpostable section and OLE section will print on separate pages to facilitate the ease in assigning these errors to correct.

  5. The Totals section of this report is used to monitor the updates to the EDS database. The following lines can help in the following ways:

    1. Total Openings or Closings sent twice — If this number is high, it could signify records are being resent to the CSPC. More training may be needed.

    2. Records Not Updated Due to IC Status 30 — If this number is greater than 0, ISD has probably run the CSPC run report through the program more than once. Testing has not been able to determine the complete ramifications of this action. Cases where unpostables were resolved could be put back into an unpostable condition. If this happens, contact your Unpostable Clerk. They may need to coordinate with ISD.

  6. To compare whether all records were processed from each transaction file, use the following lines from the reports:

    1. EP and EO Nightly Batch Run: Total Transactions Generated.

    2. CSPC Run Report: Individual File Number Totals — Number EO Records Read and Number EP Records Read.

    3. EP and EO MPS Run Report: Total Records Input.

    Note:

    These items should equal the Total on the report. If they do not equal, look at the CSPC run report for any unpostables that are not in the UNP format. Add the number of these unpostables that are not in the UNP format to the Total Records Input. If they still do not equal, see your Unpostable Clerk so they may contact Headquarters.

  7. The remaining items in the TOTALS section are informational items. The total of these four lines in each of the IC and AH columns should equal the Total Records Input.

    1. Records Unmatched — Total records where the program could not find the case number in the database. These cases(s) are listed in the MPS-EDS Errors Section.

    2. Records Not Updated — Total number of records that were on the report where no update was done to the database. These are generally records openings and update after closings. These records do not update the MF status (IC table). If the same file was run more than once through the programming this number would also include the total records found where the MF status was already a 30.

    3. Records Updated/Added — Total records where the MF status (IC table) was updated because of a closing or an unpostable or when a action history (AH table) record was added. Action history records are added when the MF status was changed and for all openings and update after closings.

    4. Database Failures — Total number of records where the database could not be updated because a record was being used by another login. This would not generally happen since the batches are run when no one else is on the system.

7.21.8.9  (01-01-2003)
Instructions

  1. MPS Unpostables will also be resolved by the Adjustments Unit who will —

    1. Research INOLE for the correct data,

    2. Update the corresponding items on EDS (the Adjustments Unit must have a password to login the ICS), and

    3. Send the case to MPS.

  2. The correct entry for each unpostable should be found by looking in the case file. If the correct entry cannot be found, the case should be taken to the specialist who closed the case to determine the correct entry.

  3. The correction(s) will be made in the Query/Update Master File Screen. These screens may be found in Option 1 of the ICS Main Menu of the EDS system.

    1. When all updates are made, a "Y" or "B" should be entered in the MF item to resend the record to MPS.

    2. Use a "B" should be used when both the opening and closing record should be sent to MPS.

  4. If the nightly batch run could not update the MF could with the unpostable code, the MF Code will still be a 1, 3 or 13.

  5. When entering a "Y" or "B" a message will be displayed to verify if the record should be sent to MPS. Depress the function key that says "yes, send" . The MF code will be updated to resend the record.

    1. 1 will be updated to 0 (zero)

    2. 3 will be updated to 2

    3. 3 will be updated to 4 if a "B" is entered in the MF status

    4. 13 will be updated to 12

  6. After the nightly batch run, the MF code will be updated to a code showing the record was sent.

7.21.8.10  (01-01-2003)
MPS Most

  1. There may be times when an opening and/or closing record is sent a second time for which there is no corrective action needed. The error messages from MPS will be the following:

    1. Error 993 — This Case is Already on the PCCF — Opening record sent a second time.

    2. Error 990 — Closing Code equals the Closing Code on PCCF — Closing record sent a second time. Use Option 5 of the Update Master File screen if you are attempting to correct MIR data items.

  2. If a closing record is sent before an opening unpostable is corrected, error code 994 is generated. These records should be corrected by entering a "B" in the MF code.

    • Error 994 — Opening Record Missing on PCCF

  3. If a closing unpostable has not been corrected and sent before the Update record is sent the following message will be displayed. These records should be corrected by entering a "Y" in the MF code.

    1. Error 986 — Closing Record Missing on PCCF for this Update — Update record sent and the closing record has not posted to MPS.

  4. Zip code and OLE errors will display the following error messages. These errors should be corrected by updating the zip code and putting a bracket in the correct position to generate the correct name control. A "Y" should be entered in the MF code to resend the record.

    1. Error 100 — Zip Code not Valid for this State Code

    2. OLE ERRORS — Error 996 — Mismatch on Name Control and OLE Name Control

Exhibit 7.21.8-1  (01-01-2003)
EDS Batch Run Error Codes

(See 8.4:(2) for a explanation of the first digit of the error codes. This exhibit lists only the last 3 digits.)

Unpostable Error Codes Error Messages
000 Invalid Case Number
001 Invalid File Folder Number
002 Invalid EIN
004 Invalid Name Control
005 Invalid District Code
006 Invalid Case Number (Julian Date)
007 Invalid Case Number
008 Too many AH Event 10 Records
010 Invalid Control Date
011 Invalid Form Number
012 Invalid Form Version Code
017 Invalid Subsection Code
018 Invalid NAICS Code
019 Invalid District of Location Code
021 This Form not sent to Master File
022 Invalid Area Code
023 Inappropriate Update to Control Date Attempted
040 Correction Disposal Record, See Unpostable Clerk
050 Invalid Employee Grade
051 Missing Employee Grade
052 Invalid Closing Code
053 Case Not Approved
054 Missing Specialist Hours
055 Inconsistent Closing Cd and Proposed Closing Cd
056 Missing Specialist Number
057 Invalid Case Grade
058 Missing Case Grade
072 Invalid Case Grade Source
082 Invalid 1st line of Name of Organization
083 Invalid 2nd line of Name of Organization
084 Invalid DBA Name
085 Invalid in Care of Name
089 Inconsistent Zip Code and State Code
090 Invalid Address
091 Invalid City
092 Invalid State Code
093 Invalid Zip Code
094 Invalid Foreign Address
095 Invalid Foreign City
096 Invalid Foreign Country
100 Zip Code not Valid for this State Code
101 Invalid 941 Filing Requirement
103 Invalid 1120 Filing Requirement
105 Invalid 1041 Filing Requirement
107 Invalid 1065 Filing Requirement
109 Invalid 940 Filing Requirement
111 Invalid 990C Filing Requirement
113 Invalid 990T Filing Requirement
115 Invalid 5227 Filing Requirement
117 Invalid 990PF Filing Requirement
119 Invalid 990 Filing Requirement
120 Missing Filing Requirement
121 Invalid Employment Code
123 Invalid Classification Code
125 Invalid Pension Plan Code
127 Invalid Foundation Code
128 Invalid Affiliation Code
129 Missing Exemption Determination Code
130 Invalid Deductibility Code
131 Inconsistent Deductibility Year
132 Invalid Advance Ruling Ends
133 Invalid Exemption Determination Code
135 Invalid Ruling Date
137 Invalid Accounting Period Ends
140 Invalid Entity Type
141 Invalid Effective Date
142 Invalid Reviewer Grade
143 Invalid Taxonomy Code
144 Missing Taxonomy Code
145 Missing Reviewer Grade
146 Inconsistent Taxonomy ad Closing Code
148 Inconsistent Foundation Cd and Principal Act Cd
155 Inconsistent Foundation Cd, Subsection Cd and Determination Cd
156 Inconsistent Foundation Code and Subsection
157 Inconsistent Entity Type and Subsection
158 Inconsistent Deductibility Code and Subsection
159 Inconsistent Classification Code and Subsection
160 Inconsistent Deductibility Code and Determination Code
161 Inconsistent District of Location and State Code
162 Dummy EIN Must be Updated
163 Missing Reviewer Number
164 Missing Reviewer Hours
165 Missing Affiliation Code
166 Inconsistent Closing Code and Type Request
167 Missing Entity Type
168 Missing Deductibility Code
169 Missing Classification Code
170 Missing Case Grade Source
173 Inconsistent Advance Ruling End and Type Request
174 Inconsistent Advance Ruling End and Subsection
177 Employment Code must be Blank
178 Classification Codes must be Blank
179 Determination Code must be Blank
180 Affiliation Code must be Blank
181 Ruling Date must be Blank
182 Foundation Code must be Blank
183 Advance Ruling Date must be Blank
184 Deductibility Code/Year must be Blank
188 Pension Plan must be Blank
189 Inconsistent Employment Code, Determ Cd & Subsection
190 Missing Reviewer Number and Reviewer Total Hours
300 Inconsistent FR941 and FR940
301 Inconsistent FR941 and Employment Cd
302 Inconsistent FR941 and State Cd
303 Inconsistent FR941, FR940 and Subsection
304 May NOT Zero Out a Filing Req Unless Determination CD is 1
305 Inconsistent Filing Requirement and Determination Cd
306 Inconsistent Filing Req, Determination Cd and Subsection
307 Inconsistent Filing Req, Determ Cd, Subsection and Foundation Cd
308 Inconsistent Filing Req, Determination Cd, Foundation Cd
309 FR5227 Must Be 2 If FR1041 Is 1 For this Subsection
310 FR990PF Must Be 1 or 2 If FR1041 Is 1 For This Subsection
311 FR990PF Must Be 1 If FR1041 Is 1 For this Subsection
312 Only One Filing Req For FR1041, FR1065 or FR1120 May Be Entered
313 Inconsistent FR990T With FR990PF
314 Inconsistent Filing Requirement and Classification Cd
315 Inconsistent Filing Requirement and Subsection
316 Inconsistent Filing Requirement and Foundation Cd
322 Inconsistent Filing Req, Employment Cd, Determ Cd and Subsection
323 Inconsistent Filing Requirement, Foundation Cd and Subsection
324 Inconsistent Filing Requirement and Deductibility Cd
325 Inconsistent Filing Req, Determination Cd and Deductibility Cd
326 Employment Cd Must Be Blank For This Subsection
327 Employment Cd Must Be Blank For This 941 Filing Requirement
328 Employment Cd Must Be Blank For This Determination Cd
329 FR940 Must Be Blank If Employment Cd Is Entered
330 Inconsistent Subsection and Affiliation Cd
332 Inconsistent FR990T With FR990
334 Inconsistent Filing Req, Determination Cd and Employment Cd
984 Record Error with Foreign Address, See Function Coordinator
985 EIN Not in CSPC’s Valid Range — Verify (If Correct, enter D in the MF Code.)
986 Closing Record Missing on PCCF for this Update
987 Update After Closing Error, See Unpostable Clerk (Program Error)
988 Inconsistent Form No and Form 5309 Ind or 40K Ind
990 Closing Record sent a second time (no action necessary if closing code matches the CSPC, check PLINF)
991 Tape Error, See Unpostable Clerk for ISD to Resend Tape
992 Inconsistent Key District Office Code in FFN, Case Number and District Office Code
993 Opening Record sent a Second Time (no action necessary)
994 Opening Record missing (Enter a "B" to send both an opening and a closing record)
995 Record Error with MF Code, See Unpostable Clerk
996 Mismatch on Name Control and EIn (OLE)
997 No matching em record
998 No matching ec record
999 No matching kd record

Exhibit 7.21.8-2  (01-01-2003)
Sample of a MPS (EACS) Run Report

*********************** ***************      
Part 1 — Screening Report Date:  
*********************** ***************      
  EDS01 10-01-2002 Initial Screening Report from PSPC  
  on EO File Number EDS0101  
  Created 09-20-2002 at 31  
Any errors because an opening was sent twice will appear here  
  Number TE/GE Records Read 110
  Number EP Records Passing Screening Test 19
  Number EO Records Passing Screening Test 87
  Number Records Passing Screening Test 0
  Total Header/Trailer Records 4
*********************** ***************      
Part 2 — EO Processing  
*********************** ***************      
EDS02 10-01-2002 Report on EO Records Validated and Added  
Any opening with Zip Code or other validity or consistency errors would print here  
EDS02 10-01-2002 Report on EO Records Validated and Closed  
Any closing with Zip Code or other validity or consistency errors would print here  
  Total EO Records Read 87
  Total EO Records Added/Closed/Udated on EACS 86
  Total Invalid/Inconsistent EO Records 0
  EO Cases Closed on PCCF  
Case Numbers are listed here  
EO Cases Added/Updated to PCCF  
Case Numbers are listed here  
     

More Internal Revenue Manual