This IRM provides an overview of the ERCS responsibilities Review and Sample Review employees should understand and apply in the performance of their duties.

Users must be aware of the potential for Unauthorized Access of Taxpayer Accounts (UNAX) violations from the use of ERCS. Data from ERCS should be accessed only for IRS business purposes. Users should promptly retrieve ERCS reports from printers or fax machines in order to prevent unintentional disclosure. Audit trails are created and subject to review for all user accesses of taxpayer data. For more information about UNAX, see IRM 10.5.5, IRS Unauthorized Access, Attempted Access or Inspection of Taxpayer Records (UNAX) Program Policy, Guidance and Requirements.

IRM 1.4.1, Management Roles and Responsibilities.

IRM 4.8.2, Case Processing.

Responsibilities of managers include but are not limited to:

Review managers have the following additional responsibilities:

Responsibilities of reviewers in Sample Review include but are not limited to the following:

Responsibilities of reviewers and tax examiners in Review include but are not limited to the following:

Responsibilities of the administrative support staff in Sample Review include but are not limited to:

Responsibilities of the administrative support staff in Review include but are not limited to:

Reports are available that allow management to monitor inventory, statutes, closures, time input, and employee records. See IRM 4.7.6, Reports for more information.

ERCS creates audit trails for selected changes to returns, employee records, and permission records. A special audit trail is also created when users enter a taxpayer identification number (TIN) or a taxpayer name on ERCS. See IRM 4.7.2, Security for more information. IRM 4.7.2.3.4, Audit Trails has a list of the changes in ERCS that produce an audit trail.

There are security checks within ERCS to ensure unauthorized users do not access programs and authorized users are kept within the boundaries of their permissions. These checks are performed automatically and silently each time a user attempts to access ERCS. The user has no ability to prevent the checks. For more information about permissions in ERCS, see IRM 4.7.2.3.2, Permissions.

See Exhibit 4.7.7-1, Acronyms and Definitions for Acronyms used in this IRM.

The following are terms and definitions specific to this IRM.

For questions regarding ERCS security and instructions for gaining access to ERCS refer to IRM 4.7.2, Security.

The instructions for Review users for navigating the ERCS programs can be found in the ERCS Review Handbook. The instructions for Sample Review users for navigating the ERCS programs can be found in the ERCS Sample Review Handbook.

Employee records are usually added by the administrative support staff in the group, but they can also be added by administrative support staff in another group if the user has write permission for the AAC. When setting up the employee record, special care must be taken when entering the standard employee identifier (SEID) to ensure the correct employee is associated with the data from Discovery Directory and the employee’s SSN.

It is essential that managers advise administrative support staff when updates are needed to employee records or new employees need to be added. The administrative support staff will timely and accurately add and input changes when advised. Values from the ERCS employee records are used for time reporting, inventory assignment, determining staffing needs, determining if managerial approval is required for updates, protecting an employee's tax return from unauthorized access and in the creation of audit trails. The following values must be kept current:

Review and Sample Review employee records are added to ERCS in the AACs according to the chart below:

The post of duty (POD) should be the POD of the employee’s official duty station. See the ZIP/POD Access Database for the POD associated with each zip code to find the employee's correct POD.

The position code is used for a number of checks including:

ERCS users must have a login name on their employee record. The login name is used to verify a user has permission to access ERCS and in the creation of the audit trails. Employees who temporarily act for their managers are given temporary ERCS access and assigned a login. The login name should not be removed from the ERCS employee record when the assignment is complete, since audit trails may have been created during the employee's assignment.

The WSP contains the employee's tour of duty (TOD) information and the number of hours the employee is scheduled to work each day. This information is used when time is input for the employee on ERCS. Each technical employee, manager, and the territory managers in LB&I must account for the number of hours they are scheduled to work each day. The WSP is also used to determine when an employee is required to charge holiday time on ERCS. When entering the WSP the user must enter their employment type, full time or part time and TOD. Part-time employees default to enter hours for the Part-Time TOD, full-time employees can be under one of five possible TODs. The following are the six choices for the TOD:

The WSP records are in two-week cycles that correspond with Single Entry Time Reporting (SETR) cycles. The employee's scheduled work days and the number of hours the employee is scheduled to work each day in the WSP should match the employee's information on the SETR system.

Since the WSP is used in validating time, changes to the WSP must be made at the beginning of the two-week pay period, before time has been applied on ERCS.

ERCS employee records should be inactivated when the employee leaves the IRS or transfers to a non-ERCS position. If an employee inputs time on ERCS the inactivation date must be entered as the last day the employee is required to charge time on ERCS. If the employee record contains a login name it should not be removed when the employee record is inactivated.

For information regarding transfers, details, and acting assignments see IRM 4.7.5.6 , Employee Records.

Additional information on adding an employee record to ERCS can be found in the Employee Records chapter of the ERCS Review Handbook for TS and JCR users and the Employee Records chapter of the ERCS Sample Review Handbook for NQRS and LQMS users. The user should enter all information accurately and completely when adding or updating employee records.

Permissions are granted by the local A/E staff. Temporary permissions may be delegated by the TM or group manager to an ERCS user. The manager must have the same permanent permission in order to grant it to another user.

There are four types of user permissions: read, write, first level approval and second level approval.

All users are given read permission. Users with read permissions can:

Generally only administrative support staff are given write permissions. Users with write permissions can perform the following tasks for any AAC they have been granted access:

Users with permanent first level approval permissions can:

Permission records should be deleted as soon as the need for them has expired. Employees should notify the manager if they have permission records that are no longer needed for business purposes.

Managers should ensure that technical employees with inventory are not routinely given write permission during a temporary acting assignment and must not be given permanent write permissions. Write permission compromises separation of duty. Permanent changes to ERCS permissions should only be granted via a Modify Access BEARS request which is routed to the manager for approval and processed by the local A/E staff.

Administrative support staff in TS are given read and write permission for their assigned AAC. If permissions are needed for additional PBCs in order to assign returns to reviewers Add Access BEARS requests must be submitted for these applications. See IRM 4.7.2, Security for additional information.

Administrative support staff in JCR, NQRS and LQMS are given read and write permission for their assigned AAC. The following are the AACs:

Review managers are given read and first level approval permission for their AAC.

Review TMs are generally given read and second level approval permissions for their territory.

Sample review managers are given read permission for their AAC. Approval permissions are not needed.

Employee permission records on ERCS are removed when the employee record is inactivated.

For technical employees the first point of contact for ERCS or AIMS questions should be the group manager. If the group manager needs assistance with ERCS or AIMS questions they should contact their local A/E analyst. The local A/E staff should be able to resolve most ERCS and AIMS issues and can coordinate with the TS A/E analyst when needed. They also can elevate issues, if necessary, to the HQ ERCS analysts.

A manager can grant temporary permission for any AAC to which they have first level approval to another user through the option Grant Temporary Permission providing the following requirements are met:

The manager should only delegate a user permission for the length of time the permission is needed, not to exceed 30 days. Technical employees should not routinely be given write permission during a temporary assignment.

The suspense type is a three digit ERCS code in the 500 - 599 range that can be associated with returns in TS statuses.

Suspense types provide a consistent approach to effectively monitor workload and provide a basis for timely completion of work.

Suspense types can be linked to a TS status code and/or a set number of days to be in suspense. When a user updates an ERCS record with a suspense type and if linked, the program automatically sets the status code and/or action date. See Exhibit 4.7.7-3 for a list of suspense types with their associated status codes and number of days.

When the action date is set by the program, it is set to a work day. So it is possible the action date could be one to two days different from the calculated date if the calculated date falls on a weekend or a holiday.

When a return is updated out of a TS status code, the suspense type and action date are removed from the record.

ERCS reports can be generated by a single suspense type or for all returns in suspense. Refer to the Inventory Reports chapter of the ERCS Review Handbook for information on Suspense Reports.

The ERCS reject reason is a three digit code in the 500 - 599 range used to identify the reason returns are sent back to the group from Review. See Exhibit 4.7.7-4 for a list of reject reasons for TS and JCR.

The reject reason must be input by a Review user when a return in a TS status code is updated to a group or PSP status code under Status Code 20.

The "Cases Returned to Group" report is available to Review users to monitor returns sent back to the group. Refer to the Inventory Reports chapter of the ERCS Review Handbook for information on this report.

When a group user closes the return back to a TS status code the reject reason is removed from the ERCS record.

The ERCS employee ID is a four or five digit number generated by the program when a new employee record is added to ERCS. The employee ID is used to assign inventory to a reviewer.

ERCS lists the employee assignment in TS or JCR in the review employee ID field and in NQRS or LQMS in the sample review employee ID field.

Inventory reports can be generated by the review or sample review employee ID.

The review type is a three digit number defining the type of return. Use of this code allows returns in Review to be classified into sub-categories for better inventory control and to aid managers in monitoring an individual reviewer's workload. ERCS does not require input of the review type. Refer to local procedures to see if it is required in your area. See Exhibit 4.7.7-5 for a list of review types.

The "Inventory Listing" report located on the Inventory Reports Menu, when run by a Review user, can be sorted by review type.

The sample review indicator is a two digit number that allows returns to be classified into sub-categories for better inventory control. ERCS does not require input of the sample review indicator. Refer to local procedures in your area. See Exhibit 4.7.7-6 for a list of sample review indicators.

The "Inventory Listing" report located on the Sample Review Reports Menu, when run by a Sample Review user, can be sorted by sample review indicator.