This section contains information and procedures for the PSP Support Manager, section chiefs, project/program coordinators (revenue agents and tax compliance officers without an inventory), and clerical staff. PSP users can also be individuals designated as actors — such as revenue agents and tax compliance officers.

The actual instructions for PSP users for ERCS can be found in the ERCS PSP Handbook. The purpose of this section is to provide policy and procedure for the use of ERCS in PSP or similar operations.

In an effort to simplify matters, the use of the word "area" in this section can be assumed to also mean "industry" .

ERCS users in PSP may retrieve information and create reports for any territory or specific AAC in the area. Reports of statistical data for projects, impending statutes, and other priorities can be generated.

PSP clerical staff generally has READ and WRITE permissions on ERCS. They also have permission to access the time reporting section of ERCS to enable them to input time.

ERCS operates on the principle that PSP users should only change data on returns that are assigned to PSP. Consequently, a PSP user may change information only on returns in groups and statuses for which the user has permission. Throughout ERCS, error messages appear when a user attempts to update returns for AAC's for which the user does not have permission.

Because of the potential for 1204 violations, reports generated in PSP that contain any Record of Tax Enforcement Results (ROTER) information are to be shared only at the territory level or higher. In PSP, only the PSP Support Manager and/or project/program coordinator may have access to reports with ROTER information.

Users in PSP must be aware of the potential for UNAX violations from the use of ERCS. As with IDRS and AIMS, data from ERCS should be accessed only for IRS business purposes. No attempt should be made to access the user's SSN or the SSN of their spouse. If the user's or spouse's SSN is entered, the security officer is notified of a possible breach of security. The security officer is also notified if a user attempts to update an employee audit return that the user does not have permission to update.

As employee audits generally originate in PSP, PSP users should be aware of the potential for notification as stated above. READ and WRITE permission should be granted only to those project/program coordinators in PSP with a need to update employee audits.

The purpose for requiring approval authority is to provide an internal control to prevent examiners and managers from ordering tax returns or updating inventory outside their authority. Actions that require approval are:

Project/program coordinators have authority to transfer cases to another AAC and status code without approval. This is because of the project/program coordinators' responsibilities and because they do not have inventories. This is different than group users.

Requests, statute updates, etc., made by clerical personnel in PSP are the same as those for group secretaries, as outlined in Section 5, Group.

The next level of management in PSP approves updates on ERCS made by PSP personnel. Approval authority is delegated to section chiefs in PSP. Second-level approval is delegated to PSP Support Manager.

PSP managers must log onto ERCS frequently to approve/disapprove changes. The updates do not rollup to AIMS until they are approved.

Disapproval of updates causes the items to revert to their prior value(s). Returns with pending approval cannot be transferred or closed. ERCS does not create a "reject" list or otherwise mark disapproved updates. ERCS only lists those transactions that are pending approval and what the updated value will be when approved.

PSP is the central point for shipping returns from campuses. Prior to shipping returns to the area, the campus will update the AAC on the return. When the AIMS download tape is processed against ERCS, these returns are then established on ERCS for the area.

Upon receipt of the return, the area is responsible for controlling the return on ERCS.

PSP is, generally, the central receiving point for returns which are transferred from another area. The AIMS database is transferred from the transferring area to the receiving area. When the AIMS download is processed against ERCS, the returns are established on ERCS for the receiving area.

The PSP Support Manager and/or ERCS Functional Coordinator has the option to inform his/her campus of what AAC's are area AAC's and what AAC's are campus AAC's. This should be coordinated between the area and campus.

There are AAC's in each area that are specifically designated for PSP operations. These AAC's are standard so that returns sent by campuses, or other areas, to the area are sent in the same AAC.

Area employee group codes (EGC) universal to all PSP operations are:

Campus EGC's universal to all PSP operations are:

The PSP Support Manager and/or ERCS Functional Coordinators in the area can set up additional AAC's for incoming cases. This is at the discretion of the area.

Personnel in PSP are responsible for ensuring that the data for the return has been properly entered on ERCS. When cases are closed or forwarded to a group or other function, PSP is responsible for updating the ERCS data for the particular return.

Project/program coordinators in the area will generally have their own AAC. The number and type of AAC's in PSP and the use of the codes is at the discretion of the PSP Support Manager and the area.

Updates to returns made by project/program coordinators will be made and approved as necessary. These updates will be made as soon as possible after determination of the changes required.

Mass updates can be made by project/program coordinators on ERCS when working with large groups of cases. Instructions for mass updates are contained in the ERCS PSP Handbook.
Examples are:

Project/program coordinators should run ERCS reports on shared AAC's to ensure the returns charged to the area have been received from the campus or other areas. This is particularly true for the AAC's mentioned in section 4.7.4.4 (6 and 7) above. A validation should be done on these AAC's codes on a monthly basis.

PSP is generally responsible for the time reporting for the area. Group/function users are responsible for inputting technical time via Form 4502, Examination Technical Time Report, and/or Form 4606, Daily Activity Record, into ERCS on a regular basis for their particular group/function. The data is rolled up via SETTS to the Detroit Computing Center (DCC) and is the source of information for Tables 36 and 37. The current Headquarters deadline is that SETTS time must be input by the close of business of the last workday of the cycle. Transmission of SETTS to DCC is required by the close of business the first workday after the end of the cycle.

The ERCS program systemically generates a unique number to all technicians required to report time on forms 4502 or 4606.

PSP is generally responsible for ensuring that all groups have reported all time on ERCS. ERCS independently ensures that all employees in the area have been accounted for via unique numbers and position codes. Generally, the ERCS Functional Coordinator either corrects any input errors or requests the appropriate group/function to correct input errors prior to SETTS transmission.

The Territory Reports Menu on ERCS provides PSP users access to various reports providing summary information for all groups. Reports include campus totals; however, these totals are not included in industry or area totals.

Many of the reports can be generated in real time. Some reports are created overnight. It is up to the individual operating division, ERCS Functional Coordinator and MITS to determine when these reports will be generated. More information regarding how to prepare the reports is contained in the ERCS PSP Handbook referred to in the introduction to this section.

PSP is responsible for determining ERCS tracking codes. These four-digit codes are used to track particular cases through the examination process. These are used for items such as Compliance Initiative Projects, Program Actions, National Projects, MACS generated returns, etc. (Series 9500-9999 are reserved for Headquarters' use and 9000–9499 are reserved for area offices' use.) These tracking codes are in addition to Project Codes that are established on AIMS. Due to the limited number of project codes that are available, tracking codes can be used to further define subgroups within a group project code.

While most ERCS reports are generated for use by group managers, the areawide reports contain general information about all groups and functions. Because of the potential for 1204 violations and UNAX violations, these reports, or reports from the closed case database, should be used only by those project/program coordinators or PSP Support Manager with a business need. These could include reports by the area Compliance Initiative Project Coordinator, the Preparer/Program Action Coordinator, MACS Coordinator, Area Classifier, or others.

Section 6, Reports, contains detailed descriptions as well as recommended uses and frequency of generating reports available through ERCS.