3.30.50. Project PCA Production Control Accounting

(1) This IRM contains the following procedures:

1. Preparing, reviewing, and monitoring the Form 3081, Employee Time Report input through the Single Entry Time Reporting (SETR).

2. Correcting invalid input data, and reviewing, correcting and adjusting output data.

3. Maintaining and updating the OFP Consistency and Project PCA Production Control Accounting Employee Master Files.

(2) Practices that are personnel-oriented are mentioned in this section only to explain the rationale and possible use of the information listings.

(1) Cumulative data is retained in three time frames:

• current quarter

• first prior quarter

• second prior quarter

(2) At the start of each new quarter,

• second prior quarter data is deleted,

• first prior quarter data is moved to second prior quarter,

• current quarter data is moved to first prior quarter, and,

• new current quarter data is collected.

(3) This system generates information reports. The reports are produced on a weekly schedule as soon as possible after completion of the reporting period.

(4) Reports and listings should be reviewed by the appropriate personnel (e.g., Managers, Operations reports function, WP&C Reports Team, etc.).

(1) Each of the Directors (Submission Processing, Accounts Management, Compliance Services, etc.) for each campus WP&C appoints a system coordinator to deal with any Project PCA systemic or procedural problems that arise.

(2) Procedural problems for Project PCA which require Headquarters assistance should be sent to SE:W:CAS:SP:PM:Q at the address below.

Internal Revenue Service
312 Elm Street
Attn: Suite 2250
Cincinnati, OH 45202

(1) Abbreviations used throughout this IRM are listed below:

(1) Measured Employees Performance System (MEPS) provides information for the evaluation of GS-08 and below employees on a measured performance plan under Numerical Performance Standards concept as mandated by the National Agreement. In addition MEPS provides Release Recall Listings for all areas of the service where employees are subject to periodic release and recall.

(2) The performance standards concept requires employees be told how well they must perform to achieve rating levels 1 through 5 before work is performed.

(3) The processing of performance data and the setting of fixed standards by management has been included in MEPS (see IRM 3.43.405).

(4) Performance data will be input weekly through TAPS or ISRP. After the completion of the weekly Project PCA runs, performance data which includes Form 3081, Employee Time Report; OFP Consistency File and the Employee Master File will be downloaded to MEPS.

(1) In Project PCA, Production and Control Accounting, the following files are input:

(2) Form 3081 Time Records are input via the Single Entry Time Reporting System (SETR). Refer to IRM 3.30.50.4.4, for the SETR System.

(3) The following files will be input via a terminal utilizing a user friendly front-end-processor:

(1) The performance and evaluation reports in the system require data that is unique to each employee. An Employee Master File and Employee Salary File are maintained and updated when appropriate. The Employee Master File is used to validate an employee's Social Security Number as it appears in the input data.

(1) The EMF (PCA-01-21) is a file maintained by WP&C Reports Teams that provides Project PCA with important information regarding each employee of Organizations that report to WP&C.

(2) Twenty data elements are maintained including Work Status, Social Security Number, Name, Grade and Step, Organization Code, Activity Code, Annual and Hourly Cost Salary data, and other codes needed to generate hours and cost data to PCA and PCC reports.

(3) When there is a change to an employee’s data element and a personnel information has been updated in SETR, the EMF will be updated by Employee Master Adjustment Records (PCA-01-32) that are downloaded from SETR. These elements are updated from SF-52 Personnel Actions processed in HR Connect and maintained in SETR history.

(4) When an across-the-board Pay Increase becomes effective the Headquarters WP&C Coordinator will work with the HR Connect staff, SETR staff and WP&C Reports Team to coordinate a complete overlay of the EMF after all pay actions have been sent to SETR.

(5) An Employee Master File Adjustment Record must be entered to:

1. add a new employee

2. change the work status or other elements for an employee, or

3. place employees in terminate status.

(6) There are four reports generated that display data pertaining to the Project PCA Master File:

• Employee Master Adjustments and Analysis Report (PCA–01–42), see Exhibit 3.30.50-2

• Employee Master Adjustments and Salary Updates Controls Listing (PCA–01–43), see Exhibit 3.30.50-3

• Employee Master List Report (PCA–01–44), see Exhibit 3.30.50-4

• Employee Status List Report (PCA–01–45), see Exhibit 3.30.50-5 (Working, Furloughed, Terminated)

(7) Each week all Operations will provide the servicing WP&C Reports Team with lists of employees that have been Returned to Duty or placed in Non-Work Status if the PAR action has not had the opportunity to be processed in HR Connect. Reports Teams will add the necessary “Change” Work Status records not listed in the SETR EMF update so weekly WP&C information post appropriately.

(1) The PCA Employee Salary File (PCA-01-22) is maintained but has not been updated since Locality Pay was adopted. Salary data in the Employee Master File used to be maintained by accessing the Salary File and populating the cost categories based upon the Grade and Step recorded in the EMF. PCA-01-31 Salary Update Records were transcribed by ISRP to update the Employee Salary File. When the Employee Salary File was updated the employee salary cost data was updated in the EMF.

(1) Each Employee Master Adjustment Record must have the following data:

1. Social Security Number—employee's SSN used as employee identification number.

2. Transaction Code—A for Add, C for Change, or D for Delete.

3. Effective Date—Date (MMDDYYYY) of employee's last personnel action.

4. Type of Last Change—3 digit alpha code assigned by the campus to identify the latest personnel action. (This entry is not necessary if the transaction code is D.)

(2) In addition to the above, adding new records will require the following data:

1. Work Status Code—identifies the status of the employee and is also used in ranking of employees for release/recall purposes. Data on terminated employees is not used for promotion or release/recall.

Code	Description
1	Working
2	Released
3	Terminated

2. Employee Name—initials of first and middle name (blank if no middle name) followed by the complete last name.

3. For General Salary employees, enter grade and step as shown below:

GS	Step	Enter As:
5	6	056
13	7	137
7	10	070

Note: When a zero appears as the third digit, it indicates step 10.

4. Wage Graded employees—enter the appropriate grade and step from the Wage Board Conversion Table (see Exhibit 3.30.50-1). Salary must be manually computed and entered.

5. Orgcode—the 5 digit code identifying the employee's permanently assigned organization.

6. Functional Area (FA)—enter the appropriate alpha/numeric code:

Functional Area	Title
66	Infrastructure Architecture & Engineering
67	IT Security Engineering
90	IT Certification & Accreditation
91	IT Disaster Recovery
1C	Taxpayer Communication & Education
1E	Media and Publications, NDC, CPS
1M	Taxpayer Advocate Case Processing
2B	Submission Processing
2C	Account Management / Electronic Correspondence Assistance
2E	Electronic Product & Services Support
2G	RTC Operations
4A	National Headquarters Management & Administration
4B	Real Estate & Facilities Management
4D	Procurement
4E	EEO Field Operations
4K	Employment Support Services
4L	Treasury Complaint Centers
4Q	Statistics of Income
4S	Physical Security / Emergency Preparedness
5U	IVO Operations
6D	Program Integration MTA Organization
7A	Compliance Services Management
7B	Payment Compliance - Correspondence Collection
7C	Automated Collection and Support
7E	Tax Reporting Compliance - Document Matching
7F	Tax Reporting Compliance - Correspondence Exam
7J	Fraud/Bank Secrecy Act
7S	Policy & Strategic Planning
9B	Production Control Monitoring
9C	Information Technology Services
9N	IT Management Services
9P	ACIO Program Management Office
9K	Cybersecurity
9Q	IT Executive Oversight
9R	IT Application Development
9S	IT Enterprise Operations
9T	IT Enterprise Network
9U	IT ACIO Enterprise Services
9X	IT End User Equipment & Services
9Z	IT Management

7. Funding Code. Enter a one position numeric to identify the employment category as follows:

0	—	Full Time Permanent
1	—	Other than Full Time Permanent (Career/Career-Conditional)
2	—	Other than Full Time Permanent (Non-Career/Career-Conditional or Non-IRS Funding)

8. Temporary Category Code—(a one position numeric or blank) is an optional code for further breakdown of the Funding Code. A zero or blank indicates no further breakdown and one through nine indicates further breakdown. Temporary Category Codes are assigned locally.

9. Class Code—assign a one position numeric code identifying the career status of the employee:

Code	Description
0	Detailed in from outside the campus
1	Permanent (Full Time)
2	Part-time Perms, Seasonals
3	Temporary and Intermittents (career/career conditional)
4	Temporary and Intermittents (non career/career conditional)
5	Term (funding code based on the campus allocation of funds for Terms)

10. Detail Status—assign a one position numeric code identifying detailed employees by the type of detail.

Code	Description
0	Not Detailed
1	Detailed within the campus
2	Detailed in from outside the campus

11. Special Employment Code—assign one of the following codes if the employee is hired under one of the special employment programs. Leave blank for non-special employment employees.

Code	Description
1	Youth Opportunity Program
2	Stay-in-School Program
3	Work Study for Vocational Students
4	Neighborhood Youth Corps
5	Work Study for College Students
6	Work Experience Program for Needy Persons
7	New Careers Program
8	Job Corps

12. Saved Rate Indicator—there must be a zero in the field for the record to post. When a record for a new employee is added to the EMF, the zero must be added to the EMF record in SETR. In the past when the PCA-01-22 Employee Salary File was used it showed whether or not an employee's salary was frozen.

0	—	Salary not frozen - must be present for all EMF records.
F	—	Salary frozen - not utilized at this time.

13. Whenever a matching record on SSN is found with transaction code A, the record will be assigned an unpostable message code on the PCA 0142 (Employee Master Adjustment and Analysis Report).

(3) If a change C is indicated, then the following four required fields must be entered:

1. Transaction Code

2. Date of Last Change

3. Type of Last Change

4. SSN

(4) Whenever a matching record is found on SSN with a transaction code of C, the following will occur:

1. All non-blank fields will be updated.

2. A slash (/) in the Special Employment Code field blanks out this field.

3. New salary data from the SETR EMF record updates the Employee Master File if it is present in the EMF record from SETR history.

4. The five salary elements must be entered manually if they are not present in the EMF record from SETR history.

5. A change action unposts if it does not match against the Employee Master File on SSN.

(5) It may be necessary to change the Work Status Code for an employee who has been released or terminated. To change the code, a new Employee Master Adjustment Record with the correct Work Status Code should be prepared and input during the cycle after the last Form 3081 was posted.

(6) If a delete D is entered, then the only elements required are:

• Transaction Code

• SSN

• Effective Date

(7) A record will delete when a matching SSN is found. When no matching record is found, an unpostable message will appear on the Employee Master Adjustment and Analysis Report (PCA 0142).

(8) All delete actions to the Employee Master Adjustment Record should be made before processing the input from Form 3081.

(9) The following items are also maintained on the Employee Master File for identification or control purposes:

• Hourly rate (Regular)—regular hourly salary rate

• Overtime—overtime hourly rate

• Night Differential—night differential

• Sunday Differential—Sunday differential

• SC Date—date (MMDDYYYY) of latest duty service computation date at the campus.

(10) The following fields in the Employee Master Adjustment Record are validity checked:

• Transaction Code

• Effective Date

• Type Change

• SSN

• Work Status

• Grade and Step

• Orgcode

• Functional Area Code

• Funding Code

• Temporary Category Code

• Class Code

• Detail Status

• Special Employment Code

• Annual Salary

• Regular Hourly Rate

• Overtime Hourly Rate

• Night Differential

• Sunday Differential

• Saved Rate Indicator

(11) Make no adjustment to the EMF when a record has invalid fields.

(12) The following salary categories will also be posted to the EMF via Employee Master Adjustment Records:

• Wage Grade

• Employees listed without grade/step

• Grade 000

(13) When an employee is terminated, data collected for that employee is not used for Individual Performance reporting purposes but may be used to gather historical information. A terminated employee's record remains on the files for nine months. After this period, it is identified on the Employee Master Adjustments and Analysis Report as a record removed from the file.

(14) WP&C Reports Teams will review the data supplied for the Employee Master File Adjustment Records for completeness and make corrections to the EMF updates as necessary.

(1) All Employee Master Adjustment Records are printed on the Employee Master Adjustments and Analysis Report, PCA–01–42 (see Exhibit 3.30.50-2).

(2) This report displays a complete list of all Employee Master Adjustment Records. The report is divided into five sections:

• Invalid Actions

• Delete Actions

• Add Actions

• Removed Actions

• Change Actions

(3) Each of these subsections displays all records associated with the specific type of action in SSN sequence.

(1) The Employee Master Adjustments & Salary Updates Control Listing, PCA–01–43 (see Exhibit 3.30.50-3) is a statistical compilation of update actions to the Employee Master File.

(1) The Employee Master List Report, PCA–01–44 (see Exhibit 3.30.50-4) is an edited report which displays all elements of Employee Master File Records. Each record is displayed on a separate line and listed in ascending SSN sequence.

(1) The Employee Status List Report, PCA–01–45 (see Exhibit 3.30.50-5) displays all elements of Employee Master File Records. The report is divided into three sections:

• working employees,

• furloughed (released) employees, and

• terminated employees.

(2) Each group's records are displayed in employee name sequence.

(1) Project PCA includes the function of updating and maintaining the OFP Consistency File. This is the OFP Consistency File that the campuses use for work plan related projects.

(2) The performance reports in this system require data which depends upon the correctness of the OFP codes input to the system. The OFP Consistency File must be correct, complete, and up-to-date at all times. It is used to validity check, match against input, and plays an important role in the monitoring of campus budget, work schedule, and work plan information.

(3) This file can be updated via adds, deletes, or changes. Campuses do not have the capability to add, change or delete parent codes. All parent OFP code adds, deletes or changes must be done via http://etd.ds.irsnet.gov/etd/ofp/index.asp. These changes will be approved by the OFP Coordinator in the Submission Processing Resource Section. The OFP Coordinator for each Campus Directorship will notify the servicing WP&C Reports Team of all updates for parent OFP combinations requested from the Headquarters OFP Coordinator.

(4) Campuses can update the third digit of the function code and/or the fifth digit of the program codes locally through ISRP. The OFP Coordinator for each Campus Directorship will provide to the servicing WP&C Reports Team a copy of the F. 5498 to update child level OFP combinations.

(1) The OFPs input to this file should be those that are valid and reportable within campus operations as prescribed in IRM 3.30.20, OFP Codes Overview, and in the Document 5995a database.

(2) The OFPs must include:

• the first two characters of the organization code at the operations level which will be part of the Standardized Master OFP Consistency File (last 3 digits of this code equal 0), and

• function and program codes

(3) Records on the OFP Consistency File, which identify a sub-function (e.g., 271), must have a parent function (e.g., 270) posted.

(1) All changes, additions, and deletions to parent codes for this file are made by the impacted campus via http://etd.ds.irsnet.gov/etd/ofp/index.asp. The request will be reviewed/approved by the OFP Coordinator in Submission Processing Resource Section.

(2) All changes, additions, and deletions to children function and program codes can be done at campus level. All OFP changes, additions, and deletions for this file should be coordinated with other work plan projects within the campus. There are four possible updates which can be input to the file:

• Deletes

• Additions

• Third digit function level change

• Fifth digit program level change

(3) Each time this file is updated, the OFP Consistency File Listing is generated reflecting all data for Organization, Function, and Program numerics and titles plus the associated Functional Area.

(4) Form 5948, http://publish.no.irs.gov/FORMS/INTERNAL/PDF/27840G88.PDF, OFP Consistency File Input is transcribed to update this file.

(5) To delete a record or records, enter a D on Form 5948. Each of the following actions can be accomplished via a delete code:

1. delete a unique OFP code,

2. delete all records with a unique Operations-Function,

3. delete all records with a unique Function-Program combination,

4. delete all records with a unique Program code, or

5. delete all records with a unique Function code.

(6) Prior to deleting/moving a program, check the WP&C Managers Report (PCC-60-40) or Program Analysis Report (PCC–62-40) to see if the program has scheduling (hours, or volume). If scheduling exists, you must first move the scheduling before deleting the program. Do not delete a record with scheduling. If a record has no scheduling, ensure that all sub-programs are deleted along with the primary OFP combinations.

(7) For the above delete actions to take place, specific input fields on Form 5948 must be transcribed.

1. For every item a, enter the 2 character Operations code, 3 digit Function code, and 5 digit Program code.

2. For every item b, enter the 2 character Operations code and 3 digit Function code only.

3. For every item c, enter the 3 digit Function code and 5 digit Program code only.

4. For every item d, enter the 5 digit Program code only.

5. For every item e, enter the 3 digit Function code only.

(8) Some OFPs, that were not used in the OFP Consistency File, are used in the Performance and Cost System. For example, Project PCA reporting for a program could include 3 digit sub-function code (e.g., 231 and 232), but not include parent function code (230) as reported on the Daymast.

1. These additional OFP combinations must be added to the OFP Consistency File before the first Service Center Replacement System (SCRS) running of the Daymast.

2. All OFP combinations that are used on Batch and Production Control Records or Unit Production Records must also be added to the OFP Consistency File.

3. If a child function/program failed to post to either SETR or BBTS, check the Missing Parent Functions and Sub-Functions Without Parents List, PCA-02-43, to ensure parents are established. If no parent code is listed, contact your campus OFP Coordinator to establish the parent code if needed. Refer to Exhibit 3.30.50-6.

(9) To Add an OFP enter an A on Form 5948. The following actions must be accomplished to add to the file:

1. Enter the 2 character Operations code, 3 digit Function code, and 5 digit Program code.

2. Enter the respective Organization, Function and Program titles.

3. Enter the appropriate Functional Area.

(10) Use an alpha O Code to make an Organization Level Change on Form 5948. To make this change, enter the 2 character Operations code, as well as any combination of the following:

1. New Operations code, to change a Operations code.

2. New Organization title, to change an Organization title .

3. New Functional Area, to change a Functional Area .

(11) Use an F code to update the file for a Function level change. The OFP Update Record must have the 3 digit Function code and Function title. This action will change the Function title on all records with this Function code.

(12) Use a P Code to update the file for a Program level change. The record must have the 5 digit Program code and Program title. This action will change the Program title for all records with that Program code.

(13) To change a specific record, use an S Code. Enter the 2 character Operations code, 3 digit Function code, 5 digit Program code and at least one of the following:

• Organization Title

• Function Title

• Program Title

• Functional Area

(14) The program posts this data to an existing record for any non-blank fields in the above categories.

(1) The OFP Consistency File Update Report, PCA–02–41, is a two part summary report.

1. Part 1 of the report (see Exhibit 3.30.50-7) displays invalid and unpostable update actions.

2. Part 2 of the report (see Exhibit 3.30.50-8) displays counts pertaining to the update actions.

(1) Two OFP Consistency Lists (see Exhibit 3.30.50-8) display the contents of all records on the updated OFP Consistency File. The lists are:

• OFP sequence (Organization, Function, Program)

• POF sequence (Program, Organization, Function)

(1) Data on Form 3081 feeds both Time and Attendance (T&A) with payroll information and WP&C Systems with basic information concerning an employee's time and production.

(2) Each employee must complete Form 3081 in accordance with the instructions. The following instructions also must be followed.

1. Volumes must be reported on all programs subject to individual Quality Review as prescribed in IRM 3.43.405. Include each line entry of each program. Example, an employee worked 8 hours regular time and 5 hours overtime on a measured program. The employee must report some volume on both line entries on Form 3081.

2. The volume field (column (g)) on Form 3081 may not contain more than 5 digits. If an employee wishes to report a volume figure of more than 5 digits for an OFP, two line entries must be made on the form. For example: if an individual wishes to report a volume figure of 100,000 and 40 hours for one OFP, two line entries should be made.

	HRS.	VOL.
1	20	50,000
2	20	50,000

3. If an employee's regular tour of duty for the reporting period is other than 40 hours, a period code must be entered in column (h) on Form 3081. SETR will automatically generate the period code for all employees when the organization code is validated, except when Period Code 0 is required. Period Code 0 is required if an employee is in furlough status for the whole week, or a Form 3081 quarterly split occurs and there are no hours to be posted for one part of the split. Check the No Hours box in SETR to generate the Period Code 0. The following period codes will be used:

   Note: Except for zero (0), system computed values will override values input by users if there is a discrepancy when the postings are validated against the tour of duty.

Period Code	Hours Covered
0	No Hrs. To WP&C
1	0.1–8.0
2	8.1–16.0
3	16.1–24.0
4	24.1–32.0
5	32.1–39.9
6	40.1–48.0
blank	40.0 exactly

4. When 40 regular hours are reported the Period Code entry is left blank.

5. When calculating the regular tour of duty, do not include overtime, compensatory time, Flexitour Credit Hours, or holiday time worked.

(3) Some examples of other than 40 regular hours are as follows:

• An employee is working a rotating shift.

• The reporting period is less than a week, as at the end of a quarter.

(4) The following table lists the Time Codes used on the Form 3081.

(5) Report time for a legal holiday as shown below:

1. All employees on a regular tour of duty, which includes a legal holiday during the reporting week, (when not actually on duty) must report the hours for the holiday as Function and Program Code 990–59503 and Time Code 1.

2. Those employees actually on duty must use:

Legal Holiday/Sunday/Night Diff (SETR)
Function/Program	Time Code
990–59503	1
Program Worked	7
Manager notifies timekeeper thru a closeout/corrected T&A that employee worked on Sunday, is eligible for night differential pay, etc.

3. In Pay Period 23 of 1996, the IRS was required to implement Section 101(f) of Public Law 104–208, of the Omnibus Consolidated Appropriations Act, 1997. This section prohibits the payment of Sunday premium pay to employees who do not actually perform work on Sunday. The subject prohibition was expanded to include night differential in Pay Period 09 of 1997.

(6) Each employee must:

• verify all entries for accuracy and completeness;

• submit a completed form to the supervisor on a timely basis as prescribed by local procedures; and

• provide the required data in the most practicable way, if away from the office.

(7) Each manager must:

• get completed forms from all assigned or detailed employees;

• review all forms for completeness and accuracy and assure that correct SSNs, organization, function, program and time codes are used;

• review volume figures on all measured employees because these figures are used in employee evaluations; and

• input data into SETR on a timely basis as prescribed by SETR procedures.

(1) Instructions in this section are for emergency purposes only in the event that Single Entry Time Reporting System becomes unavailable.

(2) The WP&C Coordinator will:

• establish cutoffs for receipt of Form 3081s by the WP&C Reports Teams

• establish the process for numbering forms as prescribed by ISRP procedures

(3) The numbering function can use the following procedures.

• Batch the documents into blocks of not more than 100.

• Attach a Alpha-Numeric Block Control Number to the upper right hand corner of the first document in each block (each Form 3081 is considered a document, i.e., when an employee requires two Form 3081s for the week, they are considered two documents);

• Number the forms in each block sequentially from 00–99 in the upper left hand corner, using a numbering machine if available; and

• Deliver the numbered blocks to the Data Conversion Operations.

(4) Data Conversion Operations must use the following instructions.

1. Process the data using ISRP (Format Code 073) and

2. Key verify all Form 3081s.

(5) WP&C Reports Teams will make corrections as normal from the Final Error Register Report(s).

(1) Post entries daily.

(2) Identify and record all time expended for each day of the calendar week (Sunday through Saturday).

(3) If the item is not applicable leave blank.

(4) Use a separate line whenever a function or program changes within the week. However, the same line may be continued across if the function and/or program remains unchanged.

(5) Below is a description of the items on Form 3081A.

(1) SETR 3081 is an on-line system that validates Employee Time Report information. The system has many built-in validity checks to reduce the amount of managerial review time. It performs the following:

• Totals all hours

• Validates Organization Function Program (OFPs)

• Checks compatibility of Org Codes, and

• Verifies employee entity data.

(2) Single Entry Time Reporting (SETR) is the result of a reengineering initiative which merged the campus' WP&C (Form 3081) time tracking system with the time and attendance system. SETR operates much like the Auto 3081 program, but there are many enhancements. Refer to the SETR Student Guide and Manager Guide for additional information.

(3) All employees must be in the Employee Database before their Form 3081 data is input. The SETR 3081 system is updated from HR-Connect:

• SF–52, Request for Personnel Action,

• TARS, Time and Attendance Reporting System, and

• Change T&A Org/AWS Code

(4) All paperwork for any personnel action (e.g., Return to Duty, Non-Work Status, Reassignments, etc.) must be submitted timely. Timely submission will help to ensure Employee Master File (EMF) updates and minimize error rates on Form 3081s.

• Information that the employee provided in the prior week for the organization code, SSN, employee name, extension, function and program code(s) is printed on the form without hours and volumes.

• The current week ending appears on the form.

(5) The WP&C Reports Teams have the overall responsibility of ensuring the entire campus' Form 3081 data has been input and validated for Week 1 processing and input, validated and signed for Week 2 prior to the scheduled mainframe runs.

(6) Numerous phone calls will be required by SETR Representatives or WP&C Reports Team members to units and/or Operations when Form 3081s are not validated timely. Untimely validation causes:

• additional work for WP&C Reports Teams and,

• error conditions on the WP&C or employee's Individual Performance Report.

(7) To ensure that all units within an operations area are validated by the local Monday cut off time:

1. Each Operations area should designate an individual to verify and ensure all of their organizations are validated timely. This individual will be that operations contact for the WP&C Reports Team.

2. Submit the name of a primary and an alternate for each operations area to the WP&C Reports Team.

3. Ensure that some type of backup plan is available for day shift personnel to obtain Form 3081 information to validate night shift organization codes.

(8) Each employee must complete Form 3081 in accordance with the instructions. The following instructions also apply.

• Record time and volume each day for OFPs on Form 3081A or facsimile.

• Transfer the total volumes for each program and grand total to the Form 3081 print-out at the end of the reporting period.

• Add additional programs that were worked but not shown on the previous week's Form 3081 print-out, and record the time and volume.

• Line through OFPs that are not currently valid or highlight the ones that are used (makes it easier for the designated employee to input the information).

• Route the information to the designated employee for input.

(9) Action required by designated employee:

1. Input the Form 3081 data into the system daily or weekly depending upon local procedures. Weekly input begins on Tuesday and ends on the cut-off time cob Friday (no data can be input during downloading process time). Corrections may be input and re-validated on Monday by the cut-off.

2. View/print Form 3081s by organization code to detect errors.

3. Initiate the Form 3081 validation process.

If	Then
errors are found	view/print a Form 3081 Error Report resolve errors

4. Revalidate the Org Code, then store the Form 3081.

5. Contact the operations coordinator if unable to validate Form 3081 by the specified cut off time.

6. Print a Time and Attendance Verification Report for the section. This report can be used to respond to an employee's questions regarding leave, credit hours, comp time, etc.

(10) Action required by operations coordinator(s):

1. View the Non-Validated Org Code List (before the cut off time and after all necessary actions are taken by the individual areas).

2. Ensure that all Org Codes within the operations have been validated by the specified dead-line on Monday.

3. Contact the WP&C Reports Team personnel and provide them with an approximate time for completion if the functional areas cannot validate timely.

(11) There is a Operations Time and Attendance Report available for management to review.

(12) Action required by Reports Teams:

1. Coordinate with management to establish cut-off times for receipt of Form 3081 from processing and non-processing functions.

2. Continually check the Non-Validated Org Code List for org codes which need validation/re-validation.

3. Contact the operations office for the areas listed on the Non-Validated Org Code List to validate all org codes by the date and time the Form 3081s are due.

4. Research questions and resolve problems that users have.

5. Print the Non-Validated Org Code List to lock out all users and validate the Form 3081 records.

6. Maintain Org Code and Org Structure data.

7. Print the Tape Input Org Code Listing.

8. Correct the errors on the Final Error Register Report(s) and forward to ISRP for reinput.

9. Provide feedback to management regarding the Form 3081 errors and untimely validations.

(13) The SETR Reports Unit menu contains options to monitor the processing of Form 3081s for all functions. Refer to the Report's Unit Form 3081 User's Guide for input instructions.

1. Non-Validated Org Code List—this option is the means of accounting for all Form 3081s within the campus. A list of all org codes that need to be validated or re-validated is displayed.

2. Validate Employee—this option is used to validate all Form 3081 records.

3. Lock/Unlock SETR Users—this option is used to lock/unlock Level 2, Level 3, Organizations.

4. Org Code Data Entry Screen—allows Reports to query, add, update, and remove current org code information. This screen should be used to input and maintain org code/org structure data.

5. OFP Data Entry Screen—allows Reports to query, add, update, and remove current OFP information. Used by the Reports Teams to resolve questions and problems that users have when inputting an OFP code (e.g., if a valid OFP does not get input to the mainframe in time, Reports Teams can add the record using this option). However, the OFP must be added to the mainframe's run by the time the Form 3081 data is validated on the mainframe to avoid an error.

6. WP&C Exclusion Report—this option is used to view/print a report of all org codes and SSNs which are excluded from the WP&C tape. The flag is in the org code screen.

7. Misc Reports—this option is used to view/print Misc Reports such as:

MISC REPORTS MENU
Option 1: Prior Week's Form 3081	Allows Reports to view and print an individual's Form 3081 from the previous week. This option can be used primarily to review a Form 3081 the day after Form 3081 processing is completed to review errors.
Option 2: WP&C Exclusion Report	Used to view/print a report of all org codes and SSNs which are excluded from the WP&C tape. The flag is in the org code screen.
Option 3: Form 3081/Personnel Org Code Diff List	Lists the SSN of the employees who have differences in their Form 3081 assigned org code and their personnel org, plus the FAs for each.
Option 4: SETR Employee Count Report	Gives the total number of employees on SETR per REG–OFC–ORG
Option 5: Print Tape Input Count	Listing of the number of Form 3081s by Operation that have been validated and will be included on the mainframe tape.
Option 6: Lock/Unlock EMF Report	Lists user, date and time when an Organization was unlocked and locked for the current period.
Option 7: Unlock Org Report for SETR	Lists manager, Level 2, Level 3, Org Code, date and time Org was unlocked for current period.
Option 8: No Hours Posted Report	Gives a list of OFP codes not used within a certain time frame.
Option 9: Pay Period 3081 Listing	Allows Reports to view and print the an individual's Form 3081 for the current week.

8. Unit's Users Guide—allows Reports to view and print the Reports Unit Form 3081 User Guide.

(1) The Quality Assurance Review Record Form 3926 is obsolete beginning October 1, 2013.

(2) Quality Assurance documents reviewed and documents in error information is input into the MEPS system through Embedded Quality Submission Processing (EQSP).

(1) The Form 3081 data file (PCA-03-11) from SETR is input into the mainframe system. These records are validity checked, and invalid records are printed on the Final Error Register Report(s), Final Time Error Register Report (PCA–03–43), IPR Adjustment Register (PCA–03–44), and Final No Time Error Register Report (PCA–03–45). The Period Data and Cum File Adjustments Control Listing (PCA-03-41) provides the input counts processed. Since SETR programming validates SSN’s and OFP’s, inconsistent data, for example, mismatch against the Employee Master File on SSN or mismatch against the OFP Consistency File on OFP, no longer appear on Error Registers.

(2) The Final Error Register Report(s) (see Exhibit 3.30.50-10) identifies all erroneous conditions detected. The Process Control File will be accessed to determine the time period covered which is associated with the Form 3081 data.

1. If the Period Ending Indicator is a W, the report will be printed for the specific weekly or period ending data.

2. If the Period Ending Indicator is a Q, the report will be printed as a Quarter Ending Report with the specific quarter ending data.

(3) Input records (Employee Time Report—Form 3081 and the Cum File Adjustment Record) appear on the Final Error Register Report(s) in OFP sequence within SSN.

(4) Each record image on the Final Error Register Report(s) has an error code(s) identifying the erroneous condition(s).

• These codes appear in the right-most portion entitled Error Indicators.

• More than one error code may appear on the Final Error Register Report(s) for any input.

• The identifying invalid conditions and error codes that appear on the error register are as follows:

(5) An additional error condition will be displayed on the Final Error Register Report (PCA-03-45). The error, Employee Master without Time Input (i.e., working employee without time) displays as a literal line entry when such a condition exists.

(6) Each report shows an Error Analysis Recap totalling each input in error. It also shows totals of the types of error codes detected as well as a summary of Employee Master without Time Input errors.

(7) The period data is applied and the Cum File Adjustment Record appears on the report (Error Code "H") if there was an attempt to delete an entire Cum Job Record and post period data to it in the same cycle.

(8) Error codes shown on the report identify the conditions which caused the report entry to be printed. All fields in the invalid record should be checked against the source documents.

(9) A or B error code conditions cause a dummy record to appear on the report.

• This dummy print line shows the SSN, Period Ending Date and total valid hours reported for the week. This line is followed by another print line for each line entry on the individual Form 3081.

• If one of the line entries on Form 3081 contains errors in addition to A or B errors, the entry appears twice on the Final Error Register Report(s).

• The report should be reviewed against the Employee Time Reports and Employee Correction Time Records prepared to correct the error.

(10) Correction records must be prepared to correct incorrect Hours or Volume on the Final Error Register Report(s).

• When entering an amount on the Correction Employee Time Record which will reduce the data in the hours field, place a minus sign above the units position of the amount.

• A negative value for hours on the Employee Time Correction Record is acceptable only if there are A or B errors detected.

• When correcting an A or B error, place an asterisk (*) above the entry in the Time Code Error column on the Final Error Register Report(s).

(11) Correction records are matched against the OFP Consistency File. Records found to contain validity errors or to mismatch on OFP are flagged with unique error codes.

(12) Cum File Adjustment Records correct cumulative data only. When these adjustment records are used, prepare the records in accordance with instructions found in IRM 3.30.50.5.2 and coordinate, when necessary, with Project 563 (PCC).

(13) Adjustment records are matched against the OFP Consistency File. Any records containing validity errors or to mismatch on OFP are flagged with unique error codes.

(14) To correct a line item on the Final Error Register Report(s), locate the source input document (Employee Time Record) and line entries on the document which correspond to the invalid record.

1. Use the appropriate record code when corrections are made.

Record Code	Source Document
3	Employee Time Record
4	Quality Assurance Record - Obsolete

2. Make corrections on the Final Error Register Report(s) by crossing out the error field and writing the correct data directly above the field. Make sure all data is copied correctly and placed in the correct columns.

3. The correction records should be transcribed in accordance with the instructions in IRM 3.24.50.

4. A correction record must be transcribed for each record line item on the Final Error Register Report(s) except for non-applicable error code A or B records. Corrections not processed in the current weekly cycle, are input as adjustments in a subsequent cycle.

(1) Cum File Adjustment Records are used to adjust or substitute values for Hours or Volume on the Current Grade Cum File or the Prior Grade Cum File. Cum File Adjustment Records may be entered in the initial or correction passes, or both in any given cycle.

(2) Determine what items in the Current Grade Cum File or Prior Grade Cum File require adjusting. If Hours or Volume are adjusted, a corresponding adjustment may have to be made to the Performance and Cost Reports as outlined in IRM 3.30.19, Production Control and Performance Reporting.

(3) Enter data required for the Cum File Adjustment Record on Form 6489, IPR Adjustments (http://publish.no.irs.gov/getpdf.cgi?catnum=28101).

1. Form 6489 is completed to adjust Project PCA data.

2. Managers complete the IPR Adjustments form.

3. The IPR Adjustments form is submitted to the Reports Team and distributed to the designated areas as follows:

One copy to Reports Team or the designated area responsible for input.

One copy to the Data Conversion area responsible for input (Project PCA adjustments only).

(4) The Reports Team, or designated area responsible for input, returns to managers any Form 6489 that contains records that could not be processed as submitted. Managers are responsible for:

• Verifying and correcting annotated records.

• Preparing a new Form 6489 for all records not processed.

• Discussing discrepancies with the designated area.

(5) Each Cum File Adjustment Record must have an Organization Code, Function Code, Program Code, SSN, Adjustment Code, Measured Code, Grade Code and Record Code. In addition to these required codes, only those fields being adjusted need to be included.

(6) Cum File Adjustment Records are used to adjust specific data criteria on performance file records. They may also be used to add or delete entire records.

(7) Use the following Adjustment Codes to adjust a record:

(8) If more than one adjustment record is input with the same OFP combination, SSN, Measured Code, Grade Code and Record Code only the following Adjustment Code combinations are valid:

1. When Hours and Volume have been reduced to zeros for the current, and first prior quarters on the Current Grade Cum Job Record or Prior Grade Cum Job Record, the entire record will be deleted.

2. If an Adjustment Record is input with Adjustment Code 9, the following fields should be blank: Hours and Volume.

(9) When adjusting programs where volume was reported, place a 1 in the PERS Measured Code field. When adjusting programs where no volume was reported, place a 2 in the PERS Measured Code field.

(10) Adjustments to Current Grade records should have a Record Code of 1. Adjustments to Prior Grade records should have a Record Code of 2. If a Prior Grade record is being adjusted, the Grade should contain the individual's appropriate prior grade. A Record code that is not 1 or 2 will be assumed to be a 1.

(11) When entering amounts which will reduce cumulative fields, place a minus sign above the units position of the amounts.

(12) Sample Adjustments—Volume has been placed on the wrong line of the Form 3081.

1. Example: Suppose that the volume has been placed after program 38300 instead of 37700 as shown in the following:

(13) This results in program 38300 being measured instead of the correct program 37700.

1. To correct this problem, subtract the volume and hours from 38300 with PERS Measured Code 1 and subtract the hours from 37700 with PERS Measured Code 2.

ORG	FUN	PROG	MC	HRS	VOL
37000	630	38300	1	−10	−50
37000	420	37700	2	−5

2. Then add the hours to 38300 with PERS Measured code 2 and add the volume and hours to 37700 with PERS Measured Code 1.

ORG	FUN	PROG	MC	HRS	VOL
37000	630	38300	2	+10
37000	420	37700	1	+5	+50

3. Subtract all of the data from the incorrect OFP and add to the correct OFP if data has been charged to the wrong OFP on the Form 3081.

(14) Adjustment Records may be processed immediately and included with records for the current period or held and processed at a later time. However, the Adjustment Records must be processed within the time frame in which the cumulative data is maintained.

(15) Adjustments input on the first week of a new quarter are processed after the cum data has been transferred. Care should be taken to ensure that the proper quarter is adjusted. For example: If it is necessary to adjust the previous week's period data on the first week of a new quarter, the adjustment should be applied to the first prior quarter data fields on the cum job record.

(1) Period Data and Cum File Adjustments Controls Listing, (PCA–03–41) (see Exhibit 3.30.50-11) is an edited report which displays statistics pertaining to processing actions, input of Employee Time Records, Cum File Adjustment Records, output of Detail Job Records, and Individual Performance Records.

(1) The Quality Assurance Error Register Report (see Exhibit 3.30.50-12) is obsolete. It did reflect those items which did not post to the Current Grade Cum Job Record because of erroneous Quality Assurance elements or other circumstances. The following messages are displayed to explain error item(s) and the reason for the error:

• Current Quarter Volume Less Than Documents Reviewed

• No Current Quarter Production Data on Cum Record

• No Matching Cum Record

• 1st Prior Volume Less Than Documents Reviewed and Current Quarter Volume Equals 0

• Attempt to Post QA Data to Non-Working Employee

• Attempt to Post QA Data to Terminated Employee

(2) The last two error messages referenced in IRM 3.30.50.6.1(1) above occur only with input of the Employee Time Record and Quality Assurance Record.

(1) The Current Grade to Prior Grade Transfer History Listing, (PCA-05-43), (see Exhibit 3.30.50-13) reflects those records which have been transferred from the Current Grade Cum File to the Prior Grade Cum File when an employee's grade is changed on the Employee Master File. This report reflects data from Current, 1st Prior, and 2nd Prior quarters amassed on file for selected Cum Job Records which are being transferred.

(1) The Period Data Posting Error Register, (PCA–05–45), (see Exhibit 3.30.50-14) displays records which did not post to the Current Grade Cum File. Accompanying each item is a specific message explaining why the record did not post. Error conditions displayed are:

• Working Employee Without SSN Matched Time Detail Job Record (DJR) and Cum Record: Master Record Bypassed

• Working Employee With SSN Matched Cum Record But Without Time DJR

• Hours Posting Would Result in Negative Amount in Current Quarter: Valid Fields Posted

• Attempt to Post Period Data to Non-working Employee

(1) The Individual Performance History Adjustment Report, (PCA–05–46), (see Exhibit 3.30.50-15) displays an audit trail of all actions taken to modify data on the Current Grade Cum File and Prior Grade Cum File.

(2) This report is in two sections: one for current grade adjustments and one for prior grade adjustments. This report displays message codes (MS CD) and also a message which identifies the disposition of the attempted adjustment:

• MS CD 1 Cum File Record Added

• MS CD 2 Cum File Record Deleted

• MS CD 3 Cum File Record Adjusted

• MS CD 4 Error—No Action Taken

(3) The report shows each adjustment that was input into the system, and whether or not it was accepted. When an adjustment is not accepted, an error code prints to identify the invalid condition. This code will appear in the column headed ERR CD on the Individual Performance History Adjustment Report.

1. Error codes and the invalid conditions which they identify on the Current Grade Cum File are as follows:

Error Code	Description
C	An adjustment record with an adjustment code of 2, or B matches an existing Cum Job Record.
G	Invalid adjustment code combination (see IRM 3.30.50.5.2(8)) or more than *two types of adjustment records (current, and 1st prior quarters) for the same SSN, OFP, Grade Code, Measured Code, and Record Code. *We do not adjust 2nd prior quarters anymore. However, the PCA program will accept adjustments (J, K, L, M) for 2nd prior quarters.
M	Attempt to delete a Cum Job Record and post period data to that same record.
N	An adjustment record with an adjustment code other than 2, or B does not match a Cum Job Record.
R	No hours present on input when attempting to create a cum record; or either Hours, Volume, Documents in Error, or Documents Reviewed are negative.
S	An SSN on the DJR does not find a matching SSN on the Employee Master File.
—	Adjustment would result in negative amount.

2. Prior Grade adjustments are printed on the Adjustment Register after the Current Grade adjustments. Error codes on the Prior Grade Cum File and the invalid conditions which they identify are as follows:

Error Code	Description
C	An adjustment record with an adjustment code of 2, or B matches an existing Prior Grade Cum Job Record.
G	Invalid adjustment code combination (see IRM 3.30.50.5.2(8)) or more than *two types of adjustment records (current, and 1st prior quarters) for the same SSN, OFP, Grade Code, Measured Code, and Record Code. *We do not adjust 2nd prior quarters anymore. However, the PCA program will accept adjustments (J, K, L, M) for 2nd prior quarters .
J	An adjustment record with an incorrect grade.
N	An adjustment record with an adjustment code other than 2, or B that does not match a Prior Grade Cum Job Record.
R	No hours present on input when attempting to create a cum record, or either Hours, Volume, Documents in Error, or Documents Reviewed are negative.
S	An SSN on the DJR does not find a matching SSN on the Employee Master File.
—	Adjustment would result in a negative amount.

(1) The Cum Files Updates Control Listing, (PCA–05–47), (see Exhibit 3.30.50-16) is a control recap summary reflecting all Adjustment Record actions attempted or taken with respect to updating the Current Grade Cum File and the Prior Grade Cum File, or both.

(1) The SSN Selection Record, (PCA–07–32), identifies a specific SSN which is used for selecting all Cumulative Job Records (CJR's) which pertain to that specific SSN from a designated cum file (current or prior grade files). Additionally, the SSN Selection Record may be used to identify individual CJR's which may need to be adjusted. The related performance data identified by the SSN Selection Record is printed on the SSN Selection Data Listing (see IRM 3.30.50.8.3).

(2) Coding the SSN Selection Record

1. The SSN Selection Record may be used only when the cum file is in SSN sequence.

2. Enter the SSN for each SSN desired on the SSN Selection Data Listing.

3. Enter C for Current Grade Cum File or P for Prior Grade Cum File in cc 80.

(1) The Cum File SSN Selection Error Register Report, PCA–07–41, (see Exhibit 3.30.50-18) identifies SSN Selection Records which are either invalid or which are mismatched on SSN. The following error messages are generated:

1. Invalid SSN And File Type

2. Invalid SSN Data

3. Invalid File Type Data

4. SSN Mismatch With Cum File

(1) The SSN Selection Data Listing, (PCA–07–42), (see Exhibit 3.30.50-19) is an edited report which displays Cumulative Job Records designated by the SSN Selection Record. The listing is divided into Current Grade Cum File and Prior Grade Cum File Sections.

(1) The Cum File Leveled Performance Report, (PCA–07–43), (see Exhibit 3.30.50-20) summarizes performance data for selected Branch (Operations), Departments, and/or Organizations. To select which organization levels to print, use the Branch Section Selection Record (IRM 3.30.50.8.5). An option to print or not print any of the three report levels is available by using the Process Control Record. (See IRM 3.30.50.7).

(2) A new column has been added to the report called"Measured Code". The report now displays the data by measured or unmeasured. The codes are "1" for Measured Data and "2" for Unmeasured Data.

(1) The Branch (Operations) Section Selection Record, (PCA–07–33), is input manually and is used to select which Operations and/or Sections will appear on the Project PCA listings.

(2) A maximum of 22 combinations are permitted per record, with a maximum of two records per run. Thus a total of 44 combinations may be entered at one time. Combinations must be entered in ascending sequence.

(3) The use of the Branch (Operations) Section Selection Record is mandatory (i.e., no default exists).

(4) Coding the Branch (Operations) Section Selection Record—The record title is BR—SEC SELECT.

1. Enter ALL if all operations are desired. The presence of ALL as the first entry suppresses any additional entries on that record.

2. Enter the first two characters of the organization followed by a blank when specific operations are desired.

3. Use the first three characters of the organization when specific departments are desired. Specific departments and specific operations may be requested on the same record.

4. Enter all individual operation and department entries in ascending sequence.

5. Enter C on the first record if a second record is being entered.

6. Leave blank on the second of the two records, or on the first if no other record is entered.