IRM 3.30.126. Control Data Analysis
15,622 words·~71 min read·
/irm/3.30.126A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
3.30.126 Control Data Analysis
Manual Transmittal
July 28, 2025
Purpose
(1)This transmits revised Internal Revenue Manual
(IRM)3.30.126, Work Planning and Control - Control Data Analysis.
Material Changes
(1)IRM 3.30.126.1.3, Roles and Responsibilities - Updated section title.
(2)IRM 3.30.126.1.6, Terms and Acronyms - Updated section title
(3)IRM 3.30.126.1.7, Related Resources - Modified subsection to house existing content previously found in IRM 3.30.126.
(4)IRM 3.30.126.1.8, IRM Deviation Procedures - Modified subsection to house existing content previously found in IRM 3.30.126.
(5)Exhibit 3.30.126-1, WP&C Program Codes - Updated program descriptors to include new Scanned Paper Return
(SPR)programs.
(6)Throughout: Made editorial changes to clarify, reorganize and remove duplicate content. Incorporated plain language and updated grammar, titles, website addresses and references.
Effect on Other Documents
IRM 3.30.126, dated January 3, 2025 is superseded.
Audience
Taxpayer Services
Effective Date
(07-28-2025)
Jim L. Fish
Director, Submission Processing
Taxpayer Services Division
1. Purpose: The Control Data Analysis utilizes data from the Service Center Control File
(SCCF)to provide management with period data and a recirculating file, containing inventory and cumulative data for each campus pipeline program on the number of documents that are good transactions, errors, rejects, Block Out of Balance (BOB), and Service Center
(SC)and Master File
(MF)deletes.
1. This printed information is provided by specific program codes and used as the data source for certain reports required by Headquarters (HQ). In addition, the output provides management with specific inventory volumes, as well as receipt and processing volumes. This system includes the Project Literal for Control Data Analysis, Project PCD
(PCD)run number series.
2. Audience: The primary users of the IRM are Submission Processing employees, mainly clerks, tax examiners, analysts, and managers from the Submission Processing Campus Accounting Operation Data Control and Reports units.
3. Policy Owner: The Director of Submission Processing.
4. Program Owner: Submission Processing, Program Management Process Assurance Branch, Monitoring Section.
5. Primary Stakeholders: The primary stakeholders are Management officials who rely on accurate data gathered by the Control Data Analysis program.
1. This IRM provides an overview of Project PCD Production Control Data Analysis. It provides procedures for the identification of campus site program issues based on the large volume of BOB blocks, errors, rejects, or critical inventory totals collected by the Control Data Analysis program.
1. Management within each campus environment must communicate security standards contained in IRM 1.4.6, Managers Security Handbook, to employees and establish methods to enforce them. Employees must take required precautions to provide security for the documents, information, and property they handle while performing official duties.
2. It is the responsibility of the user of information from this system to protect Personally Identifiable Information
(PII)from unauthorized use, access, disclosure or sharing IRM 10.5.1, Privacy Information Protection and Data Security Policy and Guidance.
1. Submission Processing, Program Management Process Assurance Branch, Monitoring Section is responsible for the information in the IRM. The Monitoring Section makes changes as needed.
2. The Director of Submission Processing is responsible for policy related to this IRM.
1. Program Reports: The program reports provided in the IRM are for identification and balancing purposes for the Submission Processing tax examiners and clerks.
2. Program Effectiveness: The program effectiveness is determined by Submission Processing employees being able to successfully resolve any balancing of data issues they may encounter.
1. The reports for the Control Data Analysis, Project PCD, are on the Control-D/Web Access server, which has a login program control.
2. It is the responsibility of the user of information from this system to protect Personally Identifiable Information
(PII)from unauthorized use, access, disclosure or sharing IRM 10.5.1, Privacy Information Protection and Data Security Policy and Guidance.
1. The table lists commonly used acronyms and their definitions:
| Acronym Definition |
| :-- :-- |
| ADJ Adjustment |
| ASFR Automated Substitute for Return |
| AUSPC Austin Submission Processing Center |
| BBTS Batch/Block Tracking System |
| BOB Block Out of Balance |
| BMF Business Master File |
| CAWR Combined Annual Wage Reporting |
| CRL Control Record List |
| CSPC Cincinnati Submission Processing Center |
| CTS Conversational Time Sharing |
| CUM Cumulative |
| DLN Document Locator Number |
| DPR Daily Production Report (PCC-22-40) |
| ECC Enterprise Computing Center |
| ECC MOB Enterprise Computing Center - Mainframe Operations Branch |
| ECC MTB Enterprise Computing Center - Martinsburg |
| ELF Electronic Filing |
| EPMF Employee Plan Master File |
| ERS Error Resolution System |
| ES Estimated Tax |
| FLC File Location Code |
| FSPC Fresno Submission Processing Center |
| FP Full Paid |
| GMF Generalized Mainline Framework |
| GUF Generalized Unpostable Framework |
| HQ Headquarters |
| ID Identifier |
| IDRS Integrated Data Retrieval System |
| IMF Individual Master File |
| INTL International |
| IRM Internal Revenue Manual |
| IRP Information Return Processing |
| IRS Internal Revenue Service |
| ISRP Integrated Submission and Remittance Processing |
| IT Information Technology |
| ITIN Individual Taxpayer Identification Number |
| KCSPC Kansas City Submission Processing Center |
| LPR Lockbox Scanned Paper Return |
| MCC Martinsburg Computing Center (old name; now Enterprise Computing Center - Martinsburg) |
| MCR Master Control Record |
| MeF Modernized e-File |
| MF Master File |
| MFT Master File Tax |
| MISC Miscellaneous |
| NMF Non Master File |
| NR Non Resident |
| OFP Organization Function Program |
| OSPC Ogden Submission Processing Center |
| OTFP Other Than Full Paid |
| PCC Project Literal for SC Production Control and Performance Reporting System, Project PCC
(563)|
| PCD Project Literal for Control Data Analysis, Project PCD
(565)|
| POC Point of Contact |
| QRSEL Quality Review Selection |
| RPS Remittance Processing System |
| SC Campus / Service Center |
| SCaaS Scanning as-a-Service |
| SCCF Service Center Control File |
| SCRIPS Service Center Recognition/Image Processing System |
| SP Submission Processing |
| SPR Scanned Paper Return |
| TC Transaction Code |
| TCRL Tape Control Record List |
| TEP Tape Edit Processor |
| TRANS Transactions |
| TY Tax Year |
| W/R With Remittance |
| WP&C Work Planning and Control |
1. The following IRMs contain specific requirements and instructions for each of the IMPIS component systems.
- IRM 3.30.18, Reports Teams Instructions for Work Planning and Control,
- IRM 3.30.19, Production Control and Performance Reporting,
- IRM 3.30.20, Organization, Function, and Program
(OFP)Codes,
- IRM 3.30.50, Project PCA Production Control Accounting,
- IRM 3.30.126, Control Data Analysis, and
- IRM 3.30.127, Workload Scheduling.
1. Service Center Directors, Headquarter Branch Chiefs, and Headquarter Analysts do not have the authority to approve deviations from IRM procedures. Any request for an exception or deviation to an IRM procedure must be elevated through appropriate channels for executive approval. Ensuring other functional areas are not adversely affected by the change and it does not result in disparate treatment of taxpayers.
2. Request for an IRM deviation must be submitted in writing following instructions from IRM 1.11.2.2.3, Internal Management Documents System - Internal Revenue Manual
(IRM)Process - When Procedures Deviate from the IRM. The program owner will coordinate any disclosure issues. No deviations can begin until reviewed by the program owner and elevated through the appropriate channels for executive approval.
1. This section describes in detail and provides procedures for establishing and operating the Control Data Analysis System, Project PCD (565), for those returns processed at the campus. These procedures provide background, general information, and detailed instructions for the following:
1. Analyzing the Document Locator Number
(DLN)in specific tape records from items processed through the Service Center
(SC)Data Control System, Project 709. Based on various elements in the DLN such as blocking series, control day key, and Saturday/Sunday key, a program code is established in those control records without a program code.
2. Balancing Individual Master File (IMF), Business Master File (BMF), Employee Plan Master File (EPMF), Information Return Processing (IRP), and Non-Master File(NMF) analyses and summaries by program code for SC Management. These analyses and summaries are reflected in the Block Proof Summary and Error Analysis (PCD-03-40), Reject Analysis (PCD-03-41), Block Deletion Analysis (PCD-03-42), and Block Out of Balance
(BOB)Analysis (PCD-03-43).
3. Analyzing the Invalid Listing (PCD-03-45) to identify unprocessable records with error codes resulting from DLN combinations that are not compatible with the GMF-81.
4. Preparing Form 8350, Correction to Block Proof Summary Balance Forward Records, containing adjustment data required for the next input to the production system.
5. Monitoring Production Control Records and Production Adjustments for daily input to the SC Production Control and Performance Reporting System, Project PCC (563).
6. Utilizing Reject Reinput Transmittals generated by program codes from the reinput file.
1. This system primarily utilizes specific tape control records from the Campus Data Control System (SCF01), containing period data and a recirculating disc file, containing inventory and cumulative data for each campus pipeline program.
2. The main purpose of this project is to feed computer counts to the Daily Production Report (by program) as pipeline documents are entered into the computer. This is necessary in order to compare the number of documents manually counted through pipeline with those entered and processed by the computer.
3. The ultimate goal is to ensure that all pipeline documents are batched and processed to good tape under the correct program number.
4. The objectives of PCD are accomplished through two computer programs. The main program (PCD03) loads the current Balance Forward File and adds period data for the current day. It then computes new percentages, new cumulative counts, and current inventory counts and generates updated records. The correction run (PCD01) is an update program for the Balance Forward File. It allows the campuses to insert, change and delete records on the existing file.
1. A master table of all program codes, as specified in the 5995a database located on the website Organization Function Program
(OFP)Code website has been established so that the program number will be printed on the Control Data Analysis reports and the program number and title will be printed on various other error and reject reports. The Program Number Master List contains all entries on the Program Number Master Table.
2. Whenever changes are made to the Program Number Master Table, a Form 8000 , Program Number Update Record, will be forwarded from HQ to the Information Technology
(IT)Division, Enterprise Computing Center
(ECC)- Mainframe Operations Branch (MOB). Functional areas can view and/or print copies of the Program Number Update List (GMF-81-40) and the Program Number Master List (GMF-81-41) from Control-D.
3. When updates have been completed the Campus GMF 81 Point of Contact
(POC)or Production Monitor is responsible for analysis of the changes and notification to the Campus Accounting Operation Data Control to update the Balance Forward File. Data Control is also responsible for analyzing data on the Invalid Listing.
Note:
Work Planning and Control (WP&C) program codes shown in Exhibit 3.30.126-1, WP&C Program Codes (Initialization) and the current GMF 81-41 Program Number Master List, must be used to validate programs currently established on the Balance Forward File and to add new program codes for beginning of the year processing. Program numbers must be updated to the Balance Forward File and have data posted before they will appear on Control Data Analysis Reports. This update is completed by the Data Control Unit within the Accounting Operation.
4. Subsequent changes to the Program Number Master Table will be reflected on the Program Number Update List (GMF-81-40). The Program Number Master List (GMF-81-41) reflects all updated changes and should be utilized throughout the year by the Data Control Unit in the Accounting Operation for updating the Balance Forward File and to assist in analyzing data on the Invalid Listing (PCD-03-45).
5. ECC MOB will download the Program Number Master List into the Batch/Block Tracking System (BBTS). Changes to blocking series on GMF-81-41 should be coordinated by the Campus Production Monitor with the appropriate numbering units to ensure consistency of reporting.
6. Changes to blocking series and the Saturday/Sunday key may cause items to post to the Invalid Listing, PCD-03-45. Should this happen, manual adjustments may be necessary until all work previously numbered, prior to receipt of the new Generalized Mainline Framework
(GMF)Transmittal, is worked through the system.
7. Run GMF-81 always produces a Program Number Update List and a Program Number Master List. The Program Number Update List shows each update record that was input. If the update record was found to be invalid, an error reason message is printed on the Program Number Update List under the heading "Error Reason" . See Exhibit 3.30.126-2, Program Number Update List (GMF- 81-40).. The Program Number Master List shows each entry in the Program Number Master Table (by Master File System) after the valid updates have been posted. See Exhibit 3.30.126-3, Program Number Master List (GMF-81-41).
8. Form 8000, Program Number Update Record, must be completed by the responsible HQ analysts to add, delete or bypass a program number on the Program Number Master List. See Exhibit 3.30.126-4, Form 8000, Program Number Update Record.
9. The Program Number Update Record cannot be used for generating subprograms on the Control Data Analysis Reports. PROJECT PCD
(565)DOES NOT RECOGNIZE FIFTH DIGIT PROGRAM NUMBERS OTHER THAN A ZERO.
1. Form 8000, Program Number Update Record, is utilized by Headquarters to update the GMF Program Number File, and by campus analysts to use subprograms on the error, reject and BOB registers and Error Resolution System
(ERS)reports. See Exhibit 3.30.126-4, Form 8000, Program Number Update Record.
2. When an update to the GMF-81-41 Program Number File is needed, campus personnel are to coordinate the request through their specific campus’ GMF-81-41 Point of Contact (POC). The campus GMF-81-41 POC must also coordinate with Submission Processing
(SP)Headquarters program owners in addition to appropriate SP Headquarters IRM handbook analysts. The campus GMF-81-41 POC is to coordinate the requested change through the appropriate Headquarter handbook analysts for IRM 3.8.44, Campus Deposit Activity, or IRM 3.10.73, Batching and Numbering. The appropriate Headquarters handbook analyst will contact the Headquarters GMF 81-41 analyst who will work the requested change through the IT GMF-81-41 programmer.
3. In order to complete this form, knowledge of the following IRMs is necessary:
- IRM 3.30.20, Organization, Function, and Program
(OFP)Codes
- IRM 3.30.126, Control Data Analysis
- IRM 3.10.73, Batching and Numbering
- IRM 3.8.44, Campus Deposit Activity
4. GENERALLY, THE FIRST FOUR DIGITS OF A PROGRAM CODE ARE SPECIFIED IN IRM 3.30.20 AND CANNOT BE CHANGED. However, it is possible to use sub-programs (fifth digit program codes) on the error, reject, and BOB registers and the ERS reports, by using the Program Number Bypass Key to bypass the HQ program number. Any key on the Form 8000 can be used to specify a fifth digit as long as the parameters for the campus sub-program entry specifies a set of documents identified by the parameters in the related HQ program number table entry. The following rules must be followed when sub-programs are used.
1. Every possible combination of tax class, document code, and blocking series that is covered by the bypassed program must be covered by a subprogram.
2. DO NOT USE A ZERO IN THE FIFTH DIGIT OF A SUBPROGRAM. Program codes ending in 1 through 9 are used for subprograms and the code ending in zero is used for the HQ program code.
3. DO NOT SUBPROGRAM ONE PART OF A HQ PROGRAM AND USE THE HQ CODE FOR THE REST. When a code has sub-programs, the entire HQ code is bypassed and all documents for the HQ program must use the sub-programs.
1. The Balance Forward File is maintained and updated daily through a recirculating process. This file is updated as follows:
1. Selected input from Service Center Control File
(SCCF)for each Master File (and the reports column titles where those items appear) are:
| If... Then... |
| :-- :-- |
| Good Block Proof Records Good Transaction Items |
| Error Block Proof Records Raw Errors Today |
| Reject Block Proof Records Raw Rejects Today and Unpostable Rejects, Period |
| Renumber Block Proof Records Rejects Cleared Today, Today’s Reject Deletions, Program Deletes |
| BOB Release Records BOBs Cleared Today |
| BOB Control Records Today’s New BOBs |
| Reinput Block Proof Records Today’s Block Deletion Releases, Reinput |
| Delete Block Proof Records Today’s Block Deletion Releases, Program Releases |
| Transaction Deletion Control Records Today’s new Block Deletions |
| Manual and Generated Adjustment Transactions Today's Transactions |
2. For an example of Form 8350 , Correction to Block Proof Summary Balance Forward Records see Exhibit 3.30.126-5. This form is prepared by the functional area responsible for balancing the Block Proof Summary reports. Integrated Submission and Remittance Processing
(ISRP)can be used for inputting data from Form 8350. However, the option exists for using the Conversational Time Sharing
(CTS)routine (on demand terminals) for inputting this data. This option requires coordination with the Enterprise Computing Center
(ECC)if ISRP is unavailable.
3. For an example of the Block Deletes Processed List (PCD-03-48), see . ISRP must be used for inputting data from this listing. (See Exhibit 3.30.126-17.)
1. IMF, BMF, EPMF, IRP and NMF
1. Correction Run:
| Report Title Location |
| :-- :-- :-- |
| PCD-01-40 Balance Forward Listing Exhibit 3.30.126-6 |
| PCD-01-41 Update Status Listing Exhibit 3.30.126-7 |
2. Control Data Analysis:
| Report Title Location |
| :-- :-- :-- |
| PCD-03-40 Block Proof Summary and Error Analysis Exhibit 3.30.126-8 |
| PCD-03-41 Reject Analysis Report Exhibit 3.30.126-9 |
| PCD-03-42 IMF Block Deletion Analysis Exhibit 3.30.126-10 |
| PCD-03-43 BOB Analysis Exhibit 3.30.126-11 |
| PCD-03-44 Balance Forward Listing Exhibit 3.30.126-12 |
| PCD-03-45 Invalid Listing Summary Exhibit 3.30.126-13 |
Invalid Listing Error Codes Exhibit 3.30.126-14 |
| PCD-03-46 Reject Reinput Batch Transmittal Exhibit 3.30.126-15 |
| PCD-03-47 Planning and Control Data Files Summary Exhibit 3.30.126-16 |
| PCD-03-48 Block Deletes Processed List Exhibit 3.30.126-17 |
3. Files for input to Project PCC
(563)Daily Production Report
| Report Title Location |
| :-- :-- :-- |
| PCD-03-30 Production Adjustments See IRM 3.30.126.7.2, Production Adjustments |
| PCD-03-31 Production Control Records See IRM 3.30.126.7.1, Production Control Record |
1. During the final cycles each year, campuses should make every effort to:
1. Reduce inventories in those functions reflected on the Control Data Analysis Reports.
2. Ensure final inventories are accurate for each program.
3. Review the next year’s program codes in Exhibit 3.30.126-1, WP&C Program Codes (Initialization), for any new, combined, or deleted codes.
4. Request well in advance all necessary computer listings from IT Enterprise Computing Center - Mainframe Operations Branch (ECC MOB).
1. Run PCD03 for all GMF/SCCF posting purge passes.
2. Cut over inventories should be shared with Reports Staff for inclusion in Daily Production Report
(DPR)(PCC-22-40) end-of-year cut-over. Cut-over inventories for each program may be acquired immediately after the end of year purge, using the following:
1. Errors
| Title Report |
| :-- :-- |
| Error Volume Report Summary GMF-10-43 |
| Error Resolution Error Inventory Summary ERS-13-41 or ERVOL Status 100 |
2. Rejects
| Title Report |
| :-- :-- |
| Reject Inventory List Summary GMF-11-43 |
| Workable Suspense Inventory Summary ERS-13-43 |
| Unworkable Suspense Inventory ERS-07-40 |
3. See Exhibit 3.30.126-18, Error Volume Report Summary (GMF-10-43), through Exhibit 3.30.126-22, Unworkable Suspense Inventory (ERS-07-40).
3. FOR THE BEGINNING OF EACH CALENDAR YEAR, THE COMPUTER PROGRAM WILL INITIALIZE ALL APPROPRIATE FIELDS TO ZERO ON THE BALANCE FORWARD FILE.
4. Compute new inventory totals using the counts in IRM 3.30.126.2.6.1(2)(a) and
(b)above. After these computations are completed, prepare a Form 8350, Correction to Block Proof Summary Balance Forward Records, to correct inventories and establish new programs. Input this data to PCD01 to update the Balance Forward File to begin the new year.
5. The TOTAL Error and Reject inventories for the beginning of the year may be verified by extracting data from GMF-07-40, Mainline Run Control Report. See Exhibit 3.30.126-23, Mainline Run Control Report (GMF-07-40) and Exhibit 3.30.126-24, Error Resolution Inventory Control Report (ERS-17-47). Obtain a copy of the first run of these reports from ECC MOB.
1. Errors
| Data Report |
| :-- :-- |
| Old Error File Total Documents GMF-07-40 |
| Plus Beginning Error Inventory ERS-17-47 |
| Equals Total (Beginning of Year Error Inventory)
2. Rejects
| Data Report |
| :-- :-- |
| Old Reject File Total Documents GMF-08-40 |
| Plus Workable Suspense Beginning Inventory ERS-17-47 |
| Plus Unworkable Suspense Beginning Inventory ERS-17-47 |
| Equals Total (Beginning of year Reject Inventory)
6. Refer to Exhibit 3.30.126-5, Form 8350, Correction to Block Proof Summary Balance Forward Records, for specific instructions in preparing Form 8350.
1. During the first few months of each year, it will be necessary to identify unpostable rejects by program code that have posted as good transactions in the prior year.
1. Each time new unpostable rejects (From Code 6, To Code 4) are posted to the Reject analysis research to determine the cycle and year they went to good tape.
2. This information is readily available by reviewing the on-line SCCF and Historic Transcripts.
2. The PCD03 program automatically subtracts unpostable rejects from the cumulative good transactions. Prior year posted items must be added back into the good tape for the current year.
1. Balance Forward Listing (PCD-01-40):
- The Balance Forward Listing can be used to verify that all adjustments have posted. It will also indicate the beginning Balance Forward File for the next PCD run. See Exhibit 3.30.126-6 for a sample of the Balance Forward Listing (PCD-01-40).
2. Update Status Listing (PCD-01-41)
- This listing indicates what happened to each record input from Form 8350, Correction to Block Proof Summary Balance Forward Records. See Exhibit 3.30.126-7 for a sample of the Update Status Listing (PCD-01-41). Use this report to verify all adjustments (overlays) were input correctly.
- Error messages will appear on this listing whenever an invalid condition occurs. Determine the cause of the problem and adjust accordingly.
1. The following subsections describe the PCD03 output analyses.
1. Information on this printout represents a summary by master file and program code of:
1. Period and cumulative items processed to good tape SCF 1151 prior to Tape Control Record List
(TCRL)totals less block deletions and unpostable rejects.
2. Period and cumulative raw conversion error receipts.
3. Errors processed.
4. Error inventory (the net of the processing activity through mainframe) beginning inventory plus new errors minus errors cleared.
5. Period and cumulative percentage of the errors to the total items processed through raw conversion. See Exhibit 3.30.126-8 for a sample of the Block Proof Summary and Error Analysis (PCD-03-40).
Note:
Errors processed, Error inventory, new errors, and errors cleared are from the perspective of SCCF and not from the perspective of ERS. For example, ERS considers items in Quality Review Selection (QRSEL) as worked while SCCF considers them as errors not yet cleared.
2. Some of these computations are based on the Cumulative
(Cum)Conversion Volume, which does not print on the analysis, but is present on the Balance Forward File and can be reviewed on the Balance Forward Listings (PCD-01-40 or PCD-03-44).
1. This listing provides a summary by master file and program code of reject activities, including unpostable and raw rejects, raw reject rates, and combined inventories. See Exhibit 3.30.126-9 for a sample of the Reject Analysis Report (PCD-03-41).
Note:
IRP and NMF do not have rejects.
1. This printout furnishes totals by program code on the status of documents deleted at the campus during the Tape Edit Processor
(TEP)run, or at the Enterprise Computing Center
(ECC)- Martinsburg (MTB). See Exhibit 3.30.126-10 for a sample of the Block Deletion Analysis (PCD-03-42).
1. The BOB Analysis provides information as to the processing activity of documents in blocks which fail to meet GMF validity requirements. In addition, this printout provides period and cumulative counts of the number of blocks converted to good tape and the number of blocks out of balance, with a corresponding percentage factor. See Exhibit 3.30.126-11 for a sample of the BOB Analysis (PCD-03-43).
1. The Balance Forward Listing provides a summary by program code of current inventories for errors, rejects, BOBs, and block deletions. It also provides cumulative data for good transactions, raw errors, conversion volumes, block deletes, BOBs, unpostable rejects, and raw rejects. See Exhibit 3.30.126-12 for a sample of the Balance Forward Listing (PCD-03-44).
1. This provides a listing of records which completed mainline processing but could not be accounted for in PCD because they failed to meet a specific criteria in the GMF-81. See Exhibit 3.30.126-13 for a sample of the Invalid Listing (PCD-03-45).
2. At the end of the Invalid Listing, a summary is provided for all Program Codes by Master File with the Total of Invalid Documents and Documents by Activity Code (From-To codes).
1. This is a transmittal that lists records of prior and current years’ returns and documents by program number, block DLN and block volume. See Exhibit 3.30.126-15 for a sample and description of the Reject Reinput Batch Transmittal (PCD-03-46).
1. This listing identifies by master file and DLN those items which have been deleted from the prior day’s TEP run. See Exhibit 3.30.126-17 for a sample and description of the Block Deletes Processed List (PCD-03-48).
1. The following subsections describe the balance function responsibility.
1. Verification of Good Transaction Items – Each day, upon receipt of the Block Proof Summary Reports, a designated employee in the Balancing function should do the following:
1. Annotate the printout with the cycle and/or tape numbers. Since the mainline runs in each campus are not necessarily scheduled on the comparable shifts, each campus must determine the processing cycle and tape numbers to be annotated.
2. Ensure the Period Good Transaction Items are equal to today’s good transaction items from SCF-11-51. Good tape block proof records on the Invalid Listing must be taken into consideration for balancing purposes.
3. Cumulative Good Transaction Items:
| Cumulative Good Transaction Items should equal: |
| :-- |
| The previous day’s cumulative good transaction items |
| Plus today’s good transaction items |
| Minus the sum of today’s new block deletions (SC and MCC) |
| Minus unpostable rejects, period |
2. Balancing of Error Analyses – The column totals to be verified are as follows:
1. Raw Errors Today should equal the error tape document count on the TCRL (SCF-11-51).
2. Cumulative Raw Errors Total:
| Cumulative Raw Errors total should equal: |
| :-- |
| The previous day’s cumulative total |
| Plus today’s raw errors |
3. Current Error Inventory:
| The Current Error Inventory should equal: |
| :-- |
| The previous day’s error inventory |
| Plus today’s raw errors |
| Minus errors cleared today |
4. Error items on the Invalid Listing and SCF-11-51 listing must be taken into consideration for balancing purposes.
5. Compare inventory totals from PCD-03-40 with SCCF Summary (SCF-07-42).
Note:
If the period figure is manually adjusted, the cumulative figure must also be adjusted.
3. Balancing of Reject Analyses:
1. Unpostable Rejects Period should equal the total reject Generalized Unpostable Framework
(GUF)items from the GUF-53-40 control run.
2. Cumulative Unpostable Rejects:
| The Cumulative Unpostable Rejects should equal: |
| :-- |
| The previous day’s unpostables cumulative |
| Plus today’s period total |
3. Raw Rejects Today should equal the reject tape document count on the TCRL (SCF-11-51).
4. Cumulative Raw Rejects:
| Cumulative Raw Rejects total should equal: |
| :-- |
| The previous day’s cumulative total |
| Plus today’s raw rejects |
5. Current Reject Inventory:
| The Current Reject Inventory should equal: |
| :-- |
| The previous day’s reject inventory |
| Plus unpostable rejects period |
| Plus today’s raw rejects |
| Minus rejects cleared today |
6. Reject items on the Invalid Listing and error codes on SCF-11-51 must be taken into consideration for balancing purposes.
7. Compare reject inventory totals from PCD-03-41 with SCCF Summary (SCF-07-42).
Note:
If the period figure is manually adjusted, the cumulative figure must be adjusted.
4. Resolving discrepancies – When discrepancies in balancing these reports occur, perform the following steps to locate the cause:
1. Ensure actual Control Record List
(CRL)record count totals (not adjusted totals) are used in computations.
2. Check the CRL for error coded items.
3. Check the Invalid Control Record List (SCF-01-41) for invalid items not included in CRL totals.
4. Ensure all appropriate items on the invalid listing are considered.
Note:
If cause of discrepancy cannot be identified, contact IT Enterprise Computing Center - Mainframe Operations Branch (ECC MOB) for assistance.
1. Today’s New Block Deletions – Campus Deletes. The total for this column should equal the Total TEP deletes from the previous day. This total is equal to the Block Document Count of Transaction (Trans) Deletion Control Records with From Code 5
(good)and To Code 0 (raw).
2. Today’s New Block Deletions – MCC Deletes. The count of MCC Deletes should equal the adjustments input to the SCCF with Control Records Source Code "D."
3. Today’s Block Deletion Releases should equal the number of items entered on the Block Delete Processed List (PCD-03-48) through ISRP the preceding day.
4. Calculating the Current Block Deletion Inventory:
| The Current Block Deletion Inventory equals: |
| --- |
| The previous day’s inventory |
| Plus today’s New Block Deletes |
| Minus Today’s Block Deletion Releases |
1. The Block Deletes Processed List will generate whenever there is activity in Today’s New Block Deletions. This list will be used as the source document to input Block Delete Processed Records. A Block Delete Processed Record is completed as follows:
1. Processing Code – Enter one of the following:
| Code Description |
| :-- :-- |
| Code "1" Indicates the block is being reinput under the original DLN or a corrected DLN with the original program code. |
| Code "2" Indicates the block will be reinput with the DLN which changes the original program code, or not reinput for reprocessing at all (in case of duplicate processing). |
| Code "3" (EPMF only) Indicates the original data will be input into the mainline run in lieu of reinputting the block. |
2. System ID Code:
| Code Description |
| --- --- |
| Code "1" IMF |
| Code "2" BMF |
| Code "3" EPMF |
| Code "5" IRP |
| Code "6" NMF |
3. MCC Deletes – The good tape portion of a block that was shipped to Master File but must be deleted before it posts to the taxpayer's account. The count of MCC Deletes should equal the adjustments input to the SCCF with Control Record source Code "D" .
4. Block DLN – the 12-digit DLN.
5. Block Document Count – the total number of items in the block.
6. Program Code – the five-digit program code that identifies the document(s).
2. This data will be input through ISRP and used as input to subsequent running of PCD03.
1. Today's New BOBs should equal the Total Computer Count on the BOB ID List (GMF-09-45). See Exhibit 3.30.126-26, BOB ID List (GMF-09-45).
2. BOBs Cleared Today equals:
1. The current day's Old Computer Doc Count Deleted Block DLN on the BOB Correction Control List (GMF-09-46). See Exhibit 3.30.126-25, BOB Correction Control List (GMF-09-46).
2. Plus the current day's New Computer Document Count Matched Block DLN on the BOB Correction Control List.
3. Calculating the Current BOBs Inventory:
| The Current BOBs Inventory equals: |
| --- |
| The previous day's Current BOBs Inventory |
| Plus Today's New BOBs |
| Minus BOBs Cleared Today |
| Plus New Computer Doc Count Matched Block DLN on the BOB Correction Control List |
| Minus Old Computer Doc Count Matched Block DLN on the BOB Correction Control List |
| Plus or Minus Adjustments made to the previous day's PCD-03-43 report |
4. Calculating the Cumulative BOBs:
| Cumulative BOBs equals: |
| --- |
| The previous day's cumulative total |
| Plus today's New BOBs |
5. Calculating the Blocks Converted Cum:
| Blocks Converted Cum equals: |
| --- |
| The previous day's Blocks Converted Cum |
| Plus today's Blocks Converted Period |
6. BOB Blocks Period should equal Total Today's New BOBs on the BOB ID List (GMF-09-45).
7. Calculating the BOB Blocks Cum:
| BOB Blocks Cum equals: |
| --- |
| The previous day's BOB Blocks Cum |
| Plus today's BOB Blocks Period |
8. Calculating the BOBs Volume Percent:
| BOBs Volume Percent equals: |
| --- |
| Cumulative BOBs |
| Divided by sum of Cum Conversion Volume (for the appropriate master file) from the Balance Forward Listing (PCD-03-44). (This sum value does not appear on the printed report. It must be calculated manually.) |
1. The Invalid Listing is generated whenever a record fails to meet specific criteria. When a DLN appears on this report, it does not mean that the returns or documents that carry the DLN did not process. Rather, it indicates that there is a consistency problem with report inventories or with determining the Program Number associated with the DLN.
2. A record will appear on the Invalid Listing whenever the amount to be subtracted is more than the amount present in the PCD03 inventories. A record will also appear on the Invalid Listing when the mainframe cannot decode a DLN into a specific Program Number. The entire record will be considered as being invalid in PCD and no counts will be updated in PCD.
3. The error records appear on the Invalid Listing as an image of an input tape record from the SCCF posting tape. The error codes will be printed on the right side of the Invalid Listing. See Exhibit 3.30.126-14 for detailed error code instructions.
4. All error conditions indicated by the Invalid Listing, must be resolved by analysis. Review the GMF-81 and compare the DLN components. If you are not sure of the resolution, identify the physical location of the document and review the document type to determine the necessary action.
5. Some "Error Code" conditions need not be corrected (e.g., Integrated Data Retrieval System
(IDRS)transactions). Other document counts from the Invalid List need to be added or subtracted from the appropriate columns, when balancing the Block Proof Summary and Error Analysis and Reject Analysis Reports and a correction must then be input into the next PCD-01 run.
6. PCD-03 program will accommodate only the current and five prior year dates. All invalid tape records printed on the Invalid Listing should be analyzed daily to determine the corrected printout totals. Ensure all necessary adjustments are promptly made to the Balance Forward File.
1. The From Code identifies the function which determines the current status of a block of documents (or portion thereof). The To Code identifies how a block of documents (or portion thereof) is to be processed next.
| From Code Definition |
| :-: :-: |
| 0 Raw data/Master Control Record
(MCR)|
| 1 BOB |
| 2 SCCF and File Deletes |
| 3 Error |
| 4 Reject |
| 5 Good Tape |
| 6 Unpostables |
2. The Record Type ID Code indicates the type of control record either posted to SCCF or attempting to post to SCCF. This ID Code is used with the From and To Codes.
| Record Type ID Code Definition |
| :-: :-: |
| 0 SCCF Adjustment |
| 2 BOB Control Record |
| 5 Reinput or Delete Block Proof Record or Trans Deletion Control Record |
| 6 Renumber Block Proof Record or Renumber Adjustment Record |
| 7 Good, Error, or Reject Block Proof Record |
3. Valid From and To Code combinations and Record Type ID Codes for Control Data Analysis reports are as follows:
| Description Record Type<br ID Code From and To Codes |
| :-: :-: :-: |
| ERRORS/REJECTS<br IMF/BMF/EPMF<br IMF/BMF<br IRP/NMF<br IRP/NMF 0/7<br 0/5<br 0/7<br 0/5 03/13/34/35/04/14/45/64<br 32/40/42<br 03/13/35<br 30/32 |
| BOBs<br IMF/BMF/IRP/EPMF 0/2 01 |
| BLOCK DELETES<br IMF/BMF/IRP/NMF/EPMF 0/5 50 |
| GOOD TRANS (MTB)<br IMF/BMF/EPMF<br IMF/BMF/EPMF<br IRP/NMF<br IRP/NMF 0/7<br 0/5<br 0/7<br 0/5 05/15/35/45<br 50<br 05/15/35<br 50 |
| PROGRAM DELETES<br EPMF 0/6 42 |
| REINPUTS<br IMF/BMF<br IRP/NMF<br EPMF 0/5<br 0/5<br 0/5 30/40<br 30<br 40 |
1. This section covers functional responsibilities including the following: input correction personnel; general explanation of BOB Analysis; BOB Correction Control List; BOB ID List; and Reports/Accounting.
1. This section provides necessary information for the Block Out of Balance function in maintaining a computer generated analysis, by specific program code, of BOB blocks. The information to determine the item count and DLN of new blocks going to BOB status will be found on the SCCF Posting Tape. Information contained on the SCCF consists of an image of the BOB record. During the normal computer run, PCD-03 will analyze the SCCF for certain records to produce the Block Proof Summary and Error Analysis, Reject Analysis, and Block Deletion Analysis reports. The computer will also analyze the BOB record image, to produce the BOB Analysis Report.
2. The BOB Analysis Report provides campus management with accurate information relative to the number and types of documents with out-of-balance conditions. In addition, the report provides a period and cumulative count of blocks converted to tape and the period and the cumulative counts of the number of BOB blocks to total blocks converted.
1. Run PCD-03 analyzes certain BOB records on the SCCF Posting Tape to produce the specified output. The BOB Record (identified by a 2 in column 1 for all Master File ID Systems) is used to determine the number of new BOBs received for correction each day by the Block Out of Balance function. The DLN is analyzed to determine the appropriate program code. The Block Document Count is then read and recorded by program code on the BOB Analysis Report. These items are:
1. Today’s New BOBs
2. BOBs Cleared Today
3. Current BOBs Inventory
4. Cumulative BOBs
2. BOB Release Record is computer generated by GMF during a BOB Correction Run and is input into the next PCD-03 run.
1. The BOB Correction Control List (GMF-09-46) is computer generated by GMF and is provided on a daily basis.
2. This list may be used to validate data on the BOB Analysis Report.
1. Old Computer Document Count Deleted Block DLN plus New Computer Document Count Matched Block DLN on the BOB Correction Control List (GMF-09-46) should equal the Total BOBs Cleared Today on the BOB Analysis Report (PCD-03-43).
2. Old Computer Document Count Non-Matched DLN of the BOB Correction Control List should equal Total Current BOB Inventory minus Total Today’s New BOBs on the BOB Analysis Report.
3. The "Julian Date" on the BOB Correction Control List indicates the original BOB date. BOBs appearing on the list after three days should be checked to determine the reason they have not been cleared.
4. A copy of this report may be found in Exhibit 3.30.126-25, BOB Correction Control List (GMF-09-46).
1. This is a control listing provided by GMF on a daily basis (GMF-09-45).
2. The BOB ID List may be used to validate data on the BOB Analysis Report.
1. Total BOB Blocks period on the BOB Analysis Report should equal the Total Today’s New BOBs on the BOB ID List.
2. Total of Today’s New BOBs on the BOB Analysis Report should equal the Total Computer Count on the BOB ID List.
3. A copy of this report may be found in Exhibit 3.30.126-26, BOB ID List (GMF-09-45).
1. Report any out of balance condition to the appropriate computing center if it appears to be a result of programming or scheduling errors.
2. Verify that Production Control Records and Production Adjustments, generated daily by run PCD-03 are input to Project PCC
(563)the same day.
3. Prepare Form 8350, Correction to Block Proof Summary Balance Forward Records, at the start of the MF processing year to include the data required for the initial Balance Forward File. The CTS routine (on demand terminals) may be used for inputting this data. However, the Demand Terminal input must be coordinated with the computing centers.
4. Update the Balance Forward File, as necessary, based on data provided by the Balancing and Input Correction functions.
1. Production Control Records and Production Adjustments are generated by Run PCD-03 for each program code specified in Exhibit 3.30.126-1 for input to the DPR.
2. These Control Records provide receipts and production volumes on the DPR:
| Function Title |
| :-: :-: |
| 910 Errors |
| 920 Rejects |
| 930 BOBs |
| 940 Block Deletes |
| 950 To MCC |
| 960 Program Deletes |
| 970 Reinputs |
| 180 Batching (for Reinput documents) |
3. These records are provided to ensure that the counts processed through the pipeline under batch control were correct and that they all convert to good tape. It is important that these functions be balanced and monitored for this purpose.
Note:
This 950 receipts record, in combination with the Function 610 roll down record represents the 950 period receipts figure on the DPR.
1. Each record is formatted as follows:
| Position Description |
| :-- :-- |
| 1 Record Number – Always 7 |
| 4 Type Code – Always 5 |
| 8-12 Organization Code – 31000, 43000 |
| 13-15 Function Code – 180, 910, 920, 930, 940, 950, 960, 970 |
| 16-20 Program Code – See valid codes in Exhibit 3.30.126-1, WP&C Program Codes (Initialization) |
| 41-48 Receipts Volume – See IRM 3.30.126.7.2(2) |
| 49-56 Production Volume – See IRM 3.30.126.7.2(2) |
| 57-59 Released Date – (DDD Julian) |
Note:
Positions not identified in the above table are blank.
2. Computations for Receipts and Production Volumes on PCD-03 generated records:
1. Function 910 (Pos. 13-15), Errors - Counts from the Block Proof Summary and Error Analysis Report:
| Description Data |
| :-- :-- |
| Receipts (Pos. 41-48) Raw Errors Today |
| Production (Pos. 49-56) Errors Cleared Today |
2. Function 920 (Pos. 13-15), Rejects - Counts from Reject Analysis Report:
| Description Data |
| :-- :-- |
| Receipts (Pos. 41-48) Unpostable Rejects Period<br plus Raw Rejects Today |
| Production (Pos. 49-56) Rejects Cleared Today |
3. Function 930 (Pos. 13-15), BOBs - Counts from BOB Analysis Report:
| Description Data |
| :-- :-- |
| Receipts (Pos. 41-48) Today’s New BOBs |
| Production (Pos. 49-56) BOBs Cleared Today |
4. Function 940 (Pos. 13-15), Block Deletes - Counts from Block Deletion Analysis Report:
| Description Data |
| :-- :-- |
| Receipts (Pos. 41-48) The sum of Today’s New Block<br Deletions (SC and MCC Deletes) |
| Production (Pos. 49-56) The sum of Today’s Block Deletion<br Releases (Reinput), plus Program<br Deletes and Record Rerun |
5. Function 950 (Pos. 13-15), To Enterprise Computing Center - Martinsburg (ECC-MTB) - Computations based on counts from all PCD reports as follows:
| Description Data |
| :-- :-- |
| Receipts (Pos. 41-48)<br <br Note:<brThe result of this computation may be a minus volume but, when combined with the Function 610 roll-down, should appear as the same figure on the DPR as the Function 950 production. 1. Minus Raw Errors Today<br <br 2. Plus Errors Cleared Yesterday<br <br 3. Minus Raw Rejects Today<br <br 4. Plus Rejects Cleared Today<br <br 5. Minus Today’s Reject Deletions (Reinput and Program Deletes)<br <br 6. Plus Today’s Block Deletion Releases, Record Rerun<br <br 7. Minus Today’s New BOBs<br <br 8. Plus BOBs Cleared Today |
| Production (Pos. 49-56) Period Good Transaction Items from the Block Proof Summary and Error Analysis. |
6. Function 960 (Pos. 13-15), Program Deletes – Counts are from the Reject Analysis and Block Deletion Analysis Reports:
Note:
Receipts (Pos. 41-48) and production (Pos. 49-56) are always the same and are the sum of the following.
| Description Data |
| :-- :-- |
| Today’s Reject Deletions Program Deletes |
| Plus Today’s Block Deletion Releases Program Deletions |
7. Function 970 (Pos. 13-15), Reinputs - Counts are from the Reject Analysis and Block Deletion Analysis Reports:
Note:
Receipts (Pos. 41-48) and production (Pos. 49-56) are always the same and are the sum of the following.
| Description Data |
| :-- :-- |
| Today’s Reject Deletions Reinput |
| Plus Today’s Block Deletion Releases Reinput |
8. Function 180 (Pos. 13-15), Batching:
Note:
Receipts (Pos. 41-48) and no production is generated for each program that has a Function 970 record. This computation is the following.
| Description Data |
| :-- :-- |
| Today’s Reject Deletions Reinput |
| Plus Today’s Block Deletion Releases Reinput |
1. Each record is formatted as follows:
| Position Description |
| :-- :-- |
| 1 Record Code – Always 3 |
| 2 Adjustment Code – Always 3 |
| 8-12 Organization Code – Always 43000 |
| 13-15 Function Code – Always "950" except "930" ) for BOBs. See IRM 3.30.126.7.2
(3)below. |
| 16-20 Program Codes – See Exhibit 3.30.126-1, WP&C Program Codes (Initialization), for valid program codes. |
| 34-41 Cumulative Receipts Since January 1 – See IRM 3.30.126.7.2 (2)(a) and (3)(b) below. |
| 42-48 Cumulative Production This Week – See IRM 3.30.126.7.2 (2)(c) below. |
| 49-56 Cumulative Production to End of Scheduling Period – See IRM 3.30.126.7.2 (2)(d) below.) |
| 57-64 Cumulative Production to End of Year – See IRM 3.30.126.7.2 (2)(e) below |
| 65-72 Daily Closing Inventory – Blank for all records except for Function 930. See IRM 3.30.126.7.2
(3)below. |
Note:
Positions not identified in the above table are blank.
2. Computations for Receipts and Production for Function 950:
1. Cum Receipts since January 1 (Pos. 34-41) is the sum of:
| Cum Receipts since January 1 (Pos. 34-41) is the sum of: |
| :-- |
| Minus Today’s New Block Deletions, SC Deletes |
| Minus Today’s New Block Deletions, MCC Deletes |
| Minus Unpostable Rejects Period |
| Plus BOB Block Document Counts in the records with a "7" BOB Inventory Adjustment Code |
| Minus BOB Block Document Counts in the records with an "8" BOB Inventory Adjustment Code |
Note:
The result of this computation may be a minus volume.
2. The result of this computation may be a minus volume.
3. Cum Production This Week (Pos. 42-48) is minus Today’s New Block Deletions, SC Deletes.
4. Computing Cum Production to the End of Scheduling Period:
| Cum Production to the End of Scheduling Period (Pos. 49-56) is the sum of: |
| :-- |
| Minus Today’s New Block Deletions, SC Deletes |
| Minus Today’s New Block Deletions, MCC Deletes |
| Minus Unpostable Rejects Period |
5. Cum Production to the End of Year (Pos. 57-64). This volume is identical to Pos. 49-56 above.
3. Computations for Receipts (Pos. 34-41) and Inventory (Pos. 65-72) for Function 930:
1. In order to adjust BOB receipts for those blocks where the Generated Block Document Count was in error, the following computation is made for each program code:
| Function 930 Receipts and Inventory: |
| --- |
| Minus All Generated Block Document Count for BOB Release Records with Inventory Adjustment Code "7" |
| Plus all Generated Block Document Count for BOB Release Records with Inventory Adjustment Code "8" |
2. The net Generated Block Document Count may be a minus volume.
1. The following sections cover the topics of Computation of period and cumulative percentage fall-out of Error, Reject and BOB.
1. The first step in computing the Raw Error and Raw Reject Rates on the Block Proof Summary and Error Analysis and Reject Analysis Reports is the computation of a Period Conversion Total. The Period Conversion Total equals the sum of Good Transaction Items Period plus Raw Errors Today minus Errors Cleared Today plus Raw Rejects Today minus Rejects Cleared Today plus Today’s Reject Deletions Reinputs/Program Deletes. (BOBs are not included in the conversion total because they fall out of the system before the GMF processing for ISRP occurs.)
2. The Raw Error Rate – Period equals the Raw Errors Today (Receipts) divided by the Period Conversion Total.
3. The Raw Reject Rate – Period equals the Raw Rejects Today (Receipts) divided by the Period Conversion Total.
4. To calculate cumulative error and reject rates, a Cumulative Conversion Volume is accumulated. The Cumulative Conversion Volume is the Period Conversion Total plus the Cumulative Conversion volume from the previous day taken from the previous day’s Balance Forward Listing. This new Cumulative Conversion Volume is entered on the Form 8350, Correction To Block Proof Summary Balance Forward Records.
5. The Raw Error Rate – Cumulative equals the Raw Errors Cumulative divided by the Cumulative Conversion Volume.
6. The Raw Reject Rate – Cumulative equals the Raw Rejects Cumulative divided by the Cumulative Conversion Volume.
1. The rate computations for the total lines are the same as the computation by program code. However, for the total lines the respective fields for all programs are added together and the applicable rates are computed.
1. Enter a two-digit serial number (00-99) in the left margin opposite every line entry in Item 2 of Form 8350. Each line is considered a separate document.
2. No more than 100 serial numbers may be placed in a block.
3. Place each block of forms under a Form 1332 in the manner specified in IRM 3.30.126.9.2, Prepare Form 1332, Block and Selection Record.
4. Blocks must be in ascending sequential order.
1. Enter a two-digit serial number (00-99) to the left of every line that contains data. Each line is considered a separate document.
2. No more than 100 serial numbers may be placed in a block.
3. Place each block of listings under a Form 1332, Block and Selection Record.
1. For each block of forms and listings specified in IRM 3.30.126.9 and IRM 3.30.126.9.1 above, prepare a Block and Selection Record, Form 1332. Entries are required only in the areas specified herein. For an exhibit of the form, see IRM 3.10.73.12, Block Selection Control Record - Form 1332, Block Selection Record or Form 1332-SC, Block and Selection Record - Service Center Recognition/Image Processing System (SCRIPS).
1. SC Block Control Number - Affix the appropriate label, Alpha-Numeric Campus Block Number.
2. Document Locator Number - Enter the appropriate Format Code:
| Description Format Code |
| :-- :-- |
| Form 8350 221 |
| Block Deletes Processed List 176 |
3. Date - Enter the year, month, and day in format YYYYMMDD. For example: May 11, 2018 - enter 20180511.
4. Release forms and listings for input to ISRP.
Exhibit 3.30.126-1
WP&C Program Codes (Initialization)
1 - IMF Programs
IMF Programs
| Program Form Description |
| --- --- --- |
| 38600 Assessment<br <br Note:<brProgram 38600 - Transaction "370" will determine processing of IMF Account Transfer documents.
| 42900 8453 8453 |
| 43110 1040 OTFP |
| 43120 1040SR OTFP |
| 43130 1040 TRANSSHIP 1040 TRANSSHIP |
| 43170 1040 ITIN |
| 43180 1040 SPR MeF |
| 43190 1040SR SR SPR MeF |
| 43210 1040 FP |
| 43510 1040 1040 MeF |
| 43540 1040SR 1040SR MeF |
| 43810 1040 OTFP SP |
| 43820 1040 FP SP |
| 43910 1040SR OTFP SP |
| 43920 1040SR FP SP |
| 44200 1040-ES, 1040C 1040-ES, 1040C |
| 44400 1040X 1040X |
| 44630 1040 SFR SUBSTITUTE FOR RETURN |
| 44450 1040X Scanned Paper Return |
| 44452 1040X W7 Scanned Paper Return |
| 44490 1040X 1040X MeF |
| 44700 4868 FILING EXTENSIONS |
| 44720 4868 4868 MeF |
| 44730 4868 4868 SPR MeF |
| 44740 2350 2350 SPR MeF |
| 44750 2350 2350 MeF |
| 45500 Revenue Receipts Revenue Receipts |
| 45520 IMF RETURNS W/R VOUCH IMF RETURNS |
| 47810 1040 ITIN OTFP SP |
2 - IMF International
(INTL)Programs Austin Submission Processing Center (AUSPC)
IMF International
(INTL)Programs (AUSPC)
| --- --- --- |
| Program Form Description |
| 33060 Form W-7A Form W-7A |
| 33070 PTIN PTIN |
| 46110 1040 INTL |
| 46120 1040, 1040NR, 1040SS, 1040PR OTFP |
| 46140 1040NR/1040NR-EZ 1040NR NEC/1040NR-EZ NEC |
| 46160 1040NR 1040NR EC OTFP SP |
| 46170 1040 INTL ITIN |
| 46180 1040NR 1040NR NEC OTFP SP |
| 46220 1040, 1040NR, 1040-PR, 1040SS FP |
| 46340 1040SS SPR MeF |
| 46350 1040NR EC SPR MeF |
| 46370 1040NR NEC SPR MeF |
| 46440 1040 ELF INTL |
| 46470 1040PR/SS ELF |
| 46510 1040 INTL MeF |
| 46540 1040PR/SS INTL MeF |
| 46550 1040NR 1040NR EC MeF |
| 46570 1040NR 1040NR NEC MeF |
| 46810 1040 OTFP SP |
| 46870 1040 INTL-ITIN SP |
| 46910 1040 FP SP |
3 - BMF Programs
BMF Programs
| Program Form Description |
| --- --- --- |
| 10100 940/940 INTL 940/940 INTL MeF |
| 10110 940PR 940PR MeF |
| 10130 941/941 INTL 941/941 INTL MeF |
| 10140 941 INTL 941 INTL MeF |
| 10150 941SS 941SS MeF |
| 10170 943/943 INTL 943/943 INTL MeF |
| 10180 943PR 943PR MeF |
| 10200 944/944 INTL 944/944 INTL MeF |
| 10220 945/945 INTL 945/945 INTL MeF |
| 11100 940, 940 PR/6020B 940, 940 PR/6020B |
| 11140 940 SCRIPS 940 SCRIPS |
| 11170 940 SPR MeF |
| 11200 941, 941 SCRIPS, 6020B 941, 941 SCRIPS, 6020B |
| 11210 941 INTL 941 INTL |
| 11250 945/945 INTL 945/945 INTL |
| 11280 941 941 SPR MeF |
| 11300 CT-1 CT-1 |
| 11330 8288 8288 |
| 11340 8804/8805/8813 8804/8805/8813 |
| 11500 1120, 1120-F, 1120-FSC, 1120-H, 1120-L, 1120-ND, 1120-PC, 1120-REIT, 1120-RIC, 1120-SF 1120, 1120-F, 1120-FSC, 1120-H, 1120-L, 1120-ND, 1120-PC, 1120-REIT, 1120-RIC, 1120-SF |
| 11520 1120 1120 MeF |
| 11540 1120C 1120C |
| 11550 1120F 1120F MeF |
| 11560 1120H 1120H MeF |
| 11600 943/943 INTL 943/943 INTL |
| 11610 943PR 943PR |
| 11650 944/SP/6020B 944/SP/6020B |
| 11660 944 XML 944 XML |
| 11680 944 INTL 944 INTL |
| 11700 7004 7004 |
| 11710 7004 7004 MeF |
| 11720 7004 7004 SPR MeF |
| 11800 720 720 |
| 11810 720 720 MeF |
| 11820 8849 8849 MeF |
| 11830 720 720 SPR MeF |
| 11900 1041 1041 |
| 11910 1041-QFT 1041-QFT |
| 11920 1041-ES 1041-ES |
| 11930 1041/1041 INTL 1041/1041 INTL MeF |
| 11950 1041 EFS 1041 EFS |
| 12100 1120-S 1120-S |
| 12110 1120-S 1120-S MeF |
| 12200 1065, 1066 1065, 1066 |
| 12210 1065 1065 MeF |
| 12220 1065-B 1065-B MeF |
| 12300 2290 2290 |
| 12310 3520 3520 |
| 12320 3520-A 3520-A |
| 12330 2290 2290 SPR MeF |
| 12340 2290 2290 MeF |
| 12400 706/706 INTL, 706GS(D), 706GS(T), 706QDT, 706NA 706/706 INTL, 706GS(D), 706GS(T), 706QDT, 706NA |
| 12410 709/709 INTL 709/709 INTL |
| 12470 709 709 MeF |
| 12480 709 709 INTL MeF |
| 12490 709NA 709NA MeF |
| 12500 1042 1042 |
| 12510 1042 1042 MeF |
| 12700 11-C, 730 11-C, 730 |
| 12820 8809 8809 |
| 12930 8453-F 8453-F |
| 12940 8453-P 8453-P |
| 13110 990 (TY07 and prior) 990 (TY07 and prior) |
| 13120 990-EZ (TY07 and prior) 990-EZ (TY07 and prior) |
| 13130 990-PF 990-PF |
| 13140 990-T 990-T |
| 13160 1041-A, 4720, 4720-A, 5578 1041-A, 4720, 4720-A, 5578 |
| 13170 1120-POL 1120-POL |
| 13180 990-C 990-C |
| 13190 5227 5227 |
| 13200 8038, 8038-G, 8038-GC, 8038-T, 8328, 8329, 8330 8038, 8038-G, 8038-GC, 8038-T, 8328, 8329, 8330 |
| 13210 8038-B, 8038-CP, 8038-TC 8038-B, 8038-CP, 8038-TC |
| 13220 8038-B, 8038-CP, 8038-TC 8038-B, 8038-CP, 8038-TC MeF |
| 13250 8703 8703 |
| 13290 5227 5227 MeF |
| 13310 990 (TY08-13) 990 (TY08-13) MeF |
| 13320 990-EZ 990-EZ MeF |
| 13330 990-PF 990-PF MeF |
| 13340 990-T 990-T MeF |
| 13350 990-N 990-N MeF |
| 13360 4720 4720 MeF |
| 13370 1120-POL 1120-POL MeF |
| 13380 990 990 MeF |
| 13390 990-EZR 990-EZR MeF |
| 13410 990 (TY08 -13) 990 (TY08 -13) |
| 13420 990-EZ 990-EZ |
| 13450 990 (TY14 and subsequent) 990 (TY14 and subsequent) |
| 14310 Sch K-1 w/F1065 Sch K-1 w/F1065 MeF |
| 14400 1120X 1120X |
| 15500 BMF Revenue Receipts (2424, 2688, 5466B, 5558, 5768, 8892) BMF Revenue Receipts (2424, 2688, 5466B, 5558, 5768, 8892) |
| 15520 BMF Returns W/R Vouchers BMF Returns W/R Vouchers |
| 15530 8868 8868 SPR MeF |
| 15540 8868 8868 |
| 15550 8868 8868 MeF |
| 15560 5558 for 5330 5558 for 5330 |
| 15800 FTD FTD |
| 15810 FTD FTD |
| 16000 8610 , 8609, 8693, 8823 8610 , 8609, 8693, 8823 |
| 16010 8453-X 8453-X |
| 18700 CAWR ADJ CAWR ADJ |
| 19000 8752 8752 |
| 38600 3413 3413 |
| 38620 Account Transfer-In (3413, 3552)<br <br Note:<brProgram 38620 - Transaction "370" will determine processing of BMF Account Transfer documents. Account Transfer-In (3413, 3552) |
| 44370 Sch K-1 w/F1120S Sch K-1 w/F1120S |
| 72360 5330/5330 INTL 5330/5330 INTL MeF |
| 72860 5330 5330 |
4 - EPMF Programs
EPMF Programs
| Program Form Description |
| --- --- --- |
| 72840 5500-EZ 5500-EZ |
| 72880 5558 for 5500 Series and 8955-SSA 5558 for 5500 Series and 8955-SSA |
5- IRP Programs
IRP Programs
| Program Form Description |
| --- --- --- |
| 11940 1041 Sch K-1 1041 Sch K-1 MeF |
| 14310 Sch K-1 w/F1065 Sch K-1 w/F1065 MeF |
| 14320 Sch K-1 w/F1065-B Sch K-1 w/F1065-B MeF |
| 44300 Various IRP Documents (1097 Series, 1098 Series, 1099 Series, 3921, 3922, 5498 Series, W-2G) Various IRP Documents (1097 Series, 1098 Series, 1099 Series, 3921, 3922, 5498 Series, W-2G) |
| 44310 1096, 1098-C 1096, 1098-C |
| 44320 FOREIGN IRP FOREIGN IRP |
| 44340 IRP SCRIPS IRP SCRIPS |
| 44370 8851, K-1/1120-S 8851, K-1/1120-S MeF |
| 44380 Sch K-1 (1065, 1041, 1120-S) Sch K-1 (1065, 1041, 1120-S) |
| 44390 Sch K-1 ELF
(1041)| Sch K-1 ELF
(1041)|
| 44610 8210 8210 |
| 71700 1042-T, 1042T ELF 1042-T, 1042T ELF |
| 71710 5471 5471 |
| 71720 1042-S, 1042-S ELF 1042-S, 1042-S ELF |
| 71790 5472 5472 |
| 80310 8027 8027 |
6- NMF Programs
| Program Form Description |
| --- --- --- |
| 72860 5330 5330 |
| 75700 NMF NMF |
| 75800 2758/8804/8805/8813/6069 2758/8804/8805/8813/6069 |
Exhibit 3.30.126-2
Program Number Update List (GMF- 81-40)
!This is an Image: 32161010.gif
This is an example of a Program Number Update List. Changes to the Program Number Master Table are reflected on this list. See IRM 3.30.126.2.2 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-3
Program Number Master List (GMF-81-41)
!This is an Image: 32161011.gif
This is an example of a Program Number Master List. The Program Number Master List shows each entry in the Program Number Master Table (by Master File System) after the valid updates have been posted. See IRM 3.30.126.2.2 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-4
Form 8000, Program Number Update Record
Complete a separate Form 8000 for each addition, deletion and/or change to update the Program Number Master Table, GMF 81.
When changing a record prepare two forms:
1. One form to delete an entire record.
2. A second form to add the record, including all changes.
Use the specific instructions listed in the table below to complete Form 8000.
The completed forms should be given to the responsible programmer for entering this data.
!This is an Image: 32161006.gif
This is an example of a Form 8000 used in adding new program codes or deleting and updating program codes to or from GMF. The table below the graphic explains how to complete Form 8000.
Please click here for the text description of the image.
| Title of Box Explanation and Action |
| --- --- |
| 1\. Program Number Action Code This code specifies the action to be taken to update the Program Number Master List. The codes and their meanings are as follows. Circle the appropriate code on Form 8000.<brAction code 1 \- used to delete an HQ or subprogram number table entry. Except for the action code, all fields on the Form 8000 must be identical to the entry on the Program Number Master List that is being deleted.<brAction code 2 \- turn off bypass key (item 15). This code allows the computer to assign to document the applicable HQ program code rather than the applicable subprogram code without having to delete the subprogram code entries.
This can be useful in cases where the service center wants to use its subprogram code only on a seasonal or temporary basis.<br <br1. Action code 2 can apply only to an HQ program number entry with a bypass key of "1" . Except for the action code, each field on the Form 8000 must be identical with the entry on the Program Number Master List that is being bypassed.<br <br2. If all of the subprograms relating to HQ program code is to be used, prepare Form 8000 with an action code 2 to change the bypass key to 0 for the HQ program.<br <brAction code 3 \- turn on bypass key (item 15).
This code is used to reverse an action code. Action code 3 is not needed to set the bypass key to 1 when subprograms are first added to the program number table. When subprogram codes are added to the table the bypass key in the related HQ program is automatically set to "1" by the computer.<br <br1. For an HQ program code, the set of documents specified by the parameters must be unique to the sets of documents specified by the parameters in the HQ program codes already in the table.<br <br2.
For a subprogram code, the set of documents specified by the parameters must be a logical subset of the set of documents specified by the parameters in the HQ program code that is already in the table and must have the same first four program number digits; and the set of documents specified by the parameters must be unique to the sets of documents specified by all programs that are already in the table and that have the same first four program number digits.<br <brAction code 4 \- used to add an HQ program code on the Program Number Master List.<br <br Note:<brAction code 4 is input by HQ only. |
| 2\. Master File
(ID)Code This code identifies the Master File for the program code. The codes and their meanings are as follows. Circle the appropriate code shown on the form.<br Code 1 - IMF<br Code 2 - BMF<br Code 3 - EPMF<br Code 4 - IRAF<br Code 5 - IRP<br Code 6 - NMF |
| 3\. Program Number Enter the five-digit program number that action is being taken on. |
| 4\. Tax Class Key This code, along with the document code, identifies the type of document. Enter the one-digit tax class code (0-9) specified on the Program Number Master List, GMF 81-41, for the program code being updated. Enter "X" if no particular tax class key is required for the program code being updated. If there is more than one tax class, a change must be made for each tax class. |
| 5\. Document Code Key This code preceded by the tax class code identifies the type of document. Enter the two-digit code (00-99) specified on the Program Number Master List, for the program code being updated. Enter "XX" if no particular document code is required for the program code being updated. If there is more than one document code for the program code, a separate update record must be prepared for each document code. |
| 6\. Block Reader MFT Key This code further identifies the program code of the document being processed. This two-digit code (00-99) must be entered whenever it is required to be input by ISRP in the Block Header information for miscellaneous documents. Most of the time this code will be blank (For example: Form 1096, enter MFT "69" ; Form W-2G, leave blank). Enter "XX" or leave blank when no particular MFT code is required for the program code being changed. |
| 7\. Control Day Key This one-digit code specifies the range of the control day that is applicable to particular DLNs and program codes. The codes and their meanings are as follows:<br Code X - Disregard this factor<br Code 1 - 001-366<br Code 2 - 401-766 |
| 8\. Block Number Key
(Low)| This code (000-999) specifies the lowest value of the block number in a DLN for the program number being updated. Enter the low order blocking series specified in IRM 3.10.73, Batching and Numbering, as a three-digit code. If two or more sets of blocking series, prepare a change for each set. |
| 9\. Block Number Key
(High)| This code (000-999) specifies the highest value of the block number in a DLN for the program number being updated. Enter the high order blocking series specified in IRM 3.10.73, Batching and Numbering, as a three-digit code. If two or more sets of blocking series, prepare a change for each set. |
| 10\. Saturday/Sunday Key This code specifies which days of the week are represented by the control day in the DLN for a program number. See the Program Number Master List to determine which program codes are used in conjunction with the Saturday/Sunday Control Day. Circle the applicable code as follows:<br Code X - Disregard this factor<br Code 1 - Weekday<br Code 2 - Saturday and/or Sunday only |
| 11\. Input System Source Key This code specifies the input system for the program codes being updated. Circle the applicable code or enter the code if not shown on the form.<br Code X - Disregard this factor<br Code A - ASFR<br Code B - Blank/Non RPS<br Code C - SCRIPS<br Code E - ELF (IMF, BMF, and IRP)<br Code F - XML<br Code L - MeF (IMF, BMF, and IRP)<br Code R - RPS |
| 12\. Prior Year Key This code specifies which program codes are applicable to prior year returns. Circle the appropriate code as specified below.<br Code X - Disregard this factor<br Code 0 - Current year only<br Code 3 - Prior year only |
| 13\. Foreign Type Key This code specifies whether the foreign or domestic File Location Code
(FLC)is applicable to the program number. Circle the appropriate codes as specified below.<br Code X - Disregard this factor<br Code 1 - All FLCs except 20, 60 and 98<br Code 2 - All FLCs except 20, 21, 60, 66, 78 and 98<br Code 3 - FLC 20, 60, or 98 only<br Code 4 - FLC 20, 21, 60, 66, 78 and 98 only |
| 14\. Transaction Code This three-digit code is used to identify the type of transaction being processed. Enter "XXX" if no particular TC is required. Enter TC 370 for Account Transfer-In documents. Leave Blank for Revenue Receipts (Program Code 15500 (Doc Code 51) and Program Code 45500 (Doc Codes 51 and 52). |
| 15\. Program Number Bypass Key This code specifies whether a HQ Program Number should be bypassed because it has been broken down into campus subprograms. When SC programs are used, the bypass key must always be "0" . Circle the appropriate code as specified below.<br Code 0 - Do not bypass<br Code 1 - bypass |
| 16\. Program Number Literal An eighteen position field used to describe the type of documents applicable to the characters for the title of the program code starting in the left most entry space of the first line. |
Exhibit 3.30.126-5
Form 8350, Correction to Block Proof Summary Balance Forward Records
Use the instructions in this table to complete Form 8350.
!This is an Image: 32161009.gif
This represents a completed Form 8350. This form is used when making corrections to the Balance Forward File and for initial input of data at the start of the processing year. It is also used for corrections/adjustments to the Block Proof Summary as well as the Error and Reject Analysis Reports. The table below the graphic explains how to complete Form 8350.
Please click here for the text description of the image.
| Column Number and Title Action |
| --- --- |
| Submission Processing Campus SC Edit the two-digit campus code in the top margin of Form 8350:<br ANSC = 07<br ATSC = 08<br KCSPC = 09<br CSPC = 17<br AUSPC = 18<br BSC = 19<br PSC = 28<br OSPC = 29<br MSC = 49<br FSPC = 89 |
| 2 - System ID Code Enter the numeric code which indicates which Master File system is to process the documents.<br 1 = IMF<br 2 = BMF<br 3 = EPMF<br 5 = IRP<br 6 = NMF |
| 3 - Program Number Enter the five-digit code that identifies the documents being corrected.<br <br Note:<brThe Master File System ID Code (col. 2) and the appropriate program number (col. 3) must be in ascending sequential order before entering a different system ID code and program number. |
| 4 - Cumulative Good Transaction Input data only at the beginning of each Master File period to decrease the inventory to zero. |
| 5 -16<br 5 - Error<br 6 - Reject<br 7 - Cumulative Raw Errors<br 8 - Current BOB Inventory<br 9 - Cumulative Conversion Volume<br 10 - Current Block Delete Inventory<br 11 - Block Deletion<br 12 - BOBS<br 13 - Unpostable Rejects<br 14 - Raw Rejects<br 15 - BOB Blocks Converted<br 16 - BOB Blocks Input as appropriate. |
| 17 - Action Code Enter the alpha code that indicates the type of adjustment to be made to a particular record:<br <br- I = Insert (adding a record to the file)<br <br <br <br Note:<br <br <br <brWhen I (Insert) is entered, Form 8350 must have an entry in every column. The entries in columns 5 - 16 must contain a positive number or a zero.<br <br- C = Change (change record on an existing file)<br <br <br <br Note:<br <br <br <brComplete columns 2, 3, 17 and any columns requiring a change.<br <br- D = Delete (delete record on an existing file)<br <br <br <br Note:<br <br <br <brComplete only columns 2, 3, and 17 on Form 8350 when deleting a record.<br <br Reminder:<brA row will not delete if the System ID Code / Program Number combination exists on the GMF-81-41. |
Exhibit 3.30.126-6
Balance Forward Listing (PCD-01-40)
!This is an Image: 32161012.gif
This is an example of a Balance Forward Listing. The Balance Forward Listing can be used to verify that all adjustments have posted. It also indicates the beginning Balance Forward File for the next PCD run. See IRM 3.30.126.3 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-7
Update Status Listing (PCD-01-41)
!This is an Image: 32161013.gif
This is an example of an Update Status Listing. This listing indicates what happened to each record input from Form 8350. See IRM 3.30.126.3 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-8
Block Proof Summary and Error Analysis (PCD-03-40)
!This is an Image: 32161014.gif
This is an example of a Block Proof Summary and Error Analysis.This report provides a summary by master file and program code of:Period and cumulative items processed to good tape SCF 1151 prior to Tape Control Record List
(TCRL)totals less block deletions and unpostable rejects.Errors processed.Error inventory (the net of the processing activity through mainframe) beginning inventory plus new errors minus errors cleared.Period and cumulative percentage of the errors to the total items processed through raw conversion.See IRM 3.30.126.4.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-9
Reject Analysis Report (PCD-03-41)
!This is an Image: 32161015.gif
This is an example of a Reject Analysis Report. This report provides a summary by master file and program code of reject activities, including unpostable and raw rejects, raw reject rates, and combined inventories.
Please click here for the text description of the image.
Exhibit 3.30.126-10
IMF Block Deletion Analysis (PCD-03-42)
!This is an Image: 32161016.gif
This is an example of a Reject Analysis Report. This report furnishes totals by program code on the status of documents deleted at the campus during the Tape Edit Processor
(TEP)run, or at the Enterprise Computing Center
(ECC)- Martinsburg (MTB).
Please click here for the text description of the image.
Exhibit 3.30.126-11
BOB Analysis (PCD-03-43)
!This is an Image: 32161017.gif
This is an example of a BOB Analysis. This report provides information as to the processing activity of documents in blocks which fail to meet GMF validity requirements. See IRM 3.30.126.4.4 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-12
Balance Forward Listing (PCD-03-44)
!This is an Image: 32161018.gif
This is an example of a Balance Forward Listing. This listing provides a summary by program code of current inventories for errors, rejects, BOBs, and block deletions. It also provides cumulative data for good transactions, raw errors, conversion volumes, block deletes, BOBs, unpostable rejects, and raw rejects.
Please click here for the text description of the image.
Exhibit 3.30.126-13
Invalid Listing Summary (PCD-03-45)
!This is an Image: 32161019.gif
This is an example of an Invalid Listing Summary. This summary provides a listing of records which completed mainline processing but could not be accounted for in PCD because they failed to meet a specific criteria in the GMF-81. See IRM 3.30.126.4.6 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-14
Invalid Listing Error Codes
The error records appear on the Invalid Listing (PCD-03-45) as an image of an input tape record from the SCCF posting tape. This Invalid Listing could contain one of the following error codes in Pos. 85-86.
| Error Code Description |
| --- --- |
| A The Block Document Count (Pos. 21-24) in a IMF, BMF or EPMF Adjustment Record (0 in Pos. 1), From and To Code (Pos. 5-6) of "40" or "42" is greater than the Current Reject Inventory from which it is to be subtracted. |
| B The Block Document Count in IMF, BMF or EPMF Reinput Block Proof Record (5 in Pos. 1), From and To Code (Pos. 5-6) of "40" is greater than the Current Reject Inventory from which it is to be subtracted. |
| C The Block Document Count in an Adjustment Record (0 in Pos. 1), From and To Code (Pos. 5-6) of "50" is greater than the Cumulative Good Transaction item from which it is to be subtracted. |
| D The Block Document Count in and Trans Deletion Control Record/Reinput Block Proof Record (5 in Pos. 1). From and To Code (Pos. 5-6) of "50" is greater than the Cumulative Good Transaction item from which it is to be subtracted. |
| E The Block Document Count in an IMF, BMF or EPMF Adjustment Record (0 in Pos.1), From and To Code (Pos. 5-6) of "34" is greater than the Current Error Inventory from which it is to be subtracted. |
| F The Block Document Count in an IMF, BMF or EPMF Reject Block Proof Record (7 in Pos.1), From and To Code (Pos. 5-6) of "34" is greater than the Current Error Inventory from which it is to be subtracted. |
| G The Block Document Count in an IRP or NMF Adjustment Record (0 in Pos. 1), From and To Code (Pos. 5-6) of "30" or "32" is greater than the Current Error Inventory from which it is to be subtracted. |
| H The Block Document Count in an IRP or NMF Reinput Proof Record (5 in Pos. 1), From and To Code (Pos. 5-6) of "30" or "32" is greater than the Current Error Inventory from which it is to be subtracted. |
| I The Block Document Count in an IMF, BMF or EPMF Delete Block Proof Record (5 in Pos. 1), From and To Code (Pos. 5-6) of "42" is greater than the Current Reject Inventory from which it is to be subtracted. |
| J The Block Document Count in an IMF, BMF or EPMF Delete Block Proof Record 6 in Pos. 1), From and To Code (Pos. 5-6) of "42" is greater than the Current Reject Inventory from which it is to be subtracted. |
| K The Block Document Count in an IRP or NMF Renumber Block Proof Record (6 in Pos 1), From and To Code (Pos. 5-6) of "32" is greater than the Current Error Inventory from which it is to be subtracted. |
| L Unable to establish program number from DLN and Program Number File. |
| M The Block Document Count in a Good Block Proof Record (7 in Pos. 1), From and To Code (Pos. 5-6) of "35" is greater than the Current Error Inventory from which it is subtracted. |
| N The Block Document Count in an IMF, BMF or EPMF Good Block Proof Record (7 in Pos. 1), From and To Code (Pos. 5-6) of "45" is greater than the Current Reject Inventory from which it is to be subtracted. |
| O The Block Document Count in an Adjustment Record (0 in Pos. 1), From and To Code (Pos. 5-6) of "36" is greater than the Current Error Inventory from which it is to be subtracted. |
| P The Block Document in an IMF, BMF or EPMF Adjustment Record (0 in Pos. 1), From and To Code (Pos. 5-6) is greater than the current Reject Inventory from which it is to be subtracted. |
| Q The Generated Block Document Count (Pos. 62-66) in a BOB Release Record (6 in Pos. 1) containing a BOB Inventory Adjustment Code (Pos. 68) of "7" is greater than the cumulative BOB from which it is to be subtracted. |
| R The Generated Block Document Count (Pos. 62-65) in a BOB Release Record (8 in Pos. 1) containing a BOB Inventory Adjustment Code (Pos. 63) of "7" or blanks is greater than the current BOB Inventory from which it is to be subtracted. |
| S The high order digit of the Block Number is other than 0-9. |
| T SC Block Number (Pos. 2-4) of an input tape record contains "IDR" indicating an IDRS tape record. |
| U The Control Date is other than 001 to 366 or 401 to 766. |
| V The year digit is other than for the current year or five prior years, except when blank on the BOB Release Record (6 in Pos. 1). |
| W A BOB Release Record (6 in Pos. 1) contains a BOB Inventory Adjustment Code (Pos. 68) is other than blank, 7 or 8. |
| X The Tax Class and/or Doc Code is invalid. |
| Y The Generated Block Document Count (Pos. 62-65) and the Block Document Count (Pos. 21-24) in a BOB Control Record (2 in Pos. 1) or BOB Release Record (8 in Pos. 1) are blank. |
| Z A Block Delete Processed Record has a program number that is not numeric or spaces. |
| 1 The Processing Code on the Block Delete Processed Record is not equal to a 1, 2, or 3. If the Processing Code is 3 the Master File System ID Code must be EPMF. |
| 2 The Master File System ID Code is other than 1, 2, 3, or 5 on the Block Delete Processed Record. |
| 3 The Block Deletion Inventory Count is less than the Block Document Count. |
| 4 Block Document Count is not numeric. |
| \ Program number of the record is not on the Balance Forward File. |
| ? Program number contains five zeros.<br <br Note:<brThe error condition can be determined by means of the error code on the listing. Valid Tax Class and Document Codes and the Table/List for determining IMF, BMF, IRP, NMF and EPMF program code identification are defined in Exhibit 3.30.126-1, WP&C Program Codes (Initialization), and Program Number Master Listing. Document Code 79 is bypassed except for IRP and NMF processing.<brWhenever the program number field contain zeros, determine what the program number should be (check for Master System ID, Program Number Master List, GMF 81-41 and the From and To Codes) and adjust inventories accordingly. |
Invalid Listing Error Code Adjustments
| Error Code From - To Code Adjustments |
| --- --- --- |
| A or B 40 OR 42 Add to Rejects Cleared Today; subtract from Current Reject Inventory. |
| C or D 50 Subtract from Good Transaction Items period and cumulative. |
| E or F 34 Add to Errors Cleared Today; subtract from Current Error Inventory. Add to Raw Rejects Today; Raw Rejects cumulative and to Current Reject Inventory. For campuses that are not up to date, daily adjustments should equal receipts and production in errors, rejects, BOBs and reinputs. Adjustments to good tape receipts during this time are acceptable. |
| G or H 30 or 32 Add to Errors Cleared Today; subtract from Current Error Inventory. |
| I or J 42 Add to Rejects Cleared Today; subtract from Current Reject Inventory. |
| K 32 Add to Errors Cleared Today; subtract from Current Error Inventory. |
| M 35 Add to Errors Cleared Today; subtract from Current Error Inventory and add to Good Transaction Items period and cumulative. |
| N 45 Add to Rejects Cleared Today; subtract from Current Reject Inventory and add to Good Transaction Items period and cumulative. |
| O 35 Add to Errors Cleared Today; subtract from Current Error Inventory and add to Good Transaction Items period and cumulative. |
| P 45 Add to Rejects Cleared Today; subtract from Current Reject Inventory and add to Good Transaction Items period and cumulative. |
Note:
From Code 1, 3, or 4; manually add document count to Errors, Rejects or BOBs Cleared Today under the correct program. From Code 0-6 does not require a manual adjustment.
To Code 1, 3, 4 or 5; manually add to document count to Good Transaction, Errors, Rejects or BOBs Today under the correct program. To Code 0 or 2 does not require a manual adjustment. It is possible to have a manual negative adjustment in current inventories. For this condition verify what the actual count should be with Error or Reject personnel.
Exhibit 3.30.126-15
Reject Reinput Batch Transmittal (PCD-03-46)
!This is an Image: 32161020.gif
This is an example of a Reject Reinput Batch Transmittal. The transmittal lists records of prior and current years’ returns and documents by program number, block DLN and block volume.
Please click here for the text description of the image.
Exhibit 3.30.126-16
Planning and Control Data Files Summary (PCD-03-47)
!This is an Image: 32161021.gif
This is an example of a Planning and Control Data Files Summary. See IRM 3.30.126.2.5 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-17
Block Deletes Processed List (PCD-03-48)
!This is an Image: 32161022.gif
This is an example of a Block Deletes Processed List. This listing identifies by master file and DLN those items which have been deleted from the prior day’s TEP run.
Please click here for the text description of the image.
Exhibit 3.30.126-18
Error Volume Report Summary (GMF-10-43)
!This is an Image: 32161031.gif
This is an example of an Error Volume Report Summary used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-19
Error Resolution Error Inventory Summary (ERS-13-41)
!This is an Image: 32161023.gif
This is an example of an Error Resolution Error Inventory Summary used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-20
Reject Inventory List Summary (GMF-11-43)
!This is an Image: 32161024.gif
This is an example of a Reject Inventory List Summary used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-21
Workable Suspense Inventory Summary (ERS-13-43)
!This is an Image: 32161025.gif
This is an example of a Workable Suspense Inventory Summary used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-22
Unworkable Suspense Inventory (ERS-07-40)
!This is an Image: 32161026.gif
This is an example of an Unworkable Suspense Inventory used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-23
Mainline Run Control Report (GMF-07-40)
!This is an Image: 32161027.gif
This is an example of a Mainline Run Control Report used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-24
Error Resolution Inventory Control Report (ERS-17-47)
!This is an Image: 32161028.gif
This is an example of an Error Resolution Inventory Control Report used in determining cut-over inventories. See IRM 3.30.126.2.6.1 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-25
BOB Correction Control List (GMF-09-46)
!This is an Image: 32161030.gif
This is an example of a BOB Correction Control List used in BOB analysis. See IRM 3.30.126.5.4 for more information.
Please click here for the text description of the image.
Exhibit 3.30.126-26
BOB ID List (GMF-09-45)
!This is an Image: 32161029.gif
This is an example of a BOB ID List used in BOB analysis. See IRM 3.30.126.5.4 for more information.
Please click here for the text description of the image.
More Internal Revenue Manual
Copy link
✓
Thanks for sharing!
Find any service
AddToAny
More…
A2A
Connections19 cite this · traces to 9
Cited by 19 sections · top 8
IRM
- IRM 3.12.38BMF General Instructions
- IRM 3.12.37IMF General Instructions
- IRM 1.1.13Taxpayer Services
- IRM 3.17.30SC Data Controls
- IRM 3.30.19Production Control and Performance Reporting
- IRM 3.30.126Control Data Analysis
- IRM 3.30.50Project PCA Production Control Accounting
- IRM 3.30.18Reports Teams Instructions for Work Planning and Control
Traces to 9 documents
IRM
- Control Data AnalysisIRM 3.30.126
- Privacy PolicyIRM 10.5.1
- Reports Teams Instructions for Work Planning and ControlIRM 3.30.18
- Production Control and Performance ReportingIRM 3.30.19
- Organization, Function, and Program (OFP) CodesIRM 3.30.20
- Project PCA Production Control AccountingIRM 3.30.50
- Workload SchedulingIRM 3.30.127
- Campus Deposit ActivityIRM 3.8.44
- Batching and NumberingIRM 3.10.73
21 references not yet in our index
- IRM 3.30.126.1.3
- IRM 3.30.126.1.6
- IRM 3.30.126.1.7
- IRM 3.30.126.1.8
- IRM 1.4.6
- IRM 3.30.126.1.4
- IRM 1.11.2.2.3
- IRM 3.30.126.7.2
- IRM 3.30.126.7.1
- IRM 3.30.126.2.6.1
- IRM 3.30.126.9.2
- IRM 3.30.126.9
- IRM 3.30.126.9.1
- IRM 3.10.73.12
- IRM 3.30.126.2.2
- IRM 3.30.126.3
- IRM 3.30.126.4.1
- IRM 3.30.126.4.4
- IRM 3.30.126.4.6
- IRM 3.30.126.2.5
- IRM 3.30.126.5.4
Citation graph
cites case law
IRM 3.30.126
Control Data Analysis
IRM×19
CiteIRM 3.30.126.1.3
CiteIRM 3.30.126.1.6
CiteIRM 3.30.126.1.7
Cites 30 · showing 12Cited by 19 across 1 source