4.7.2 Security

Manual Transmittal

October 11, 2019

Purpose

(1) This transmits a revised IRM 4.7.2, Examination Returns Control System (ERCS), Security.

Material Changes

(1) Internal controls were added to this IRM per IRM 1.11.2, Internal Revenue Manual (IRM) Process.

(2) Content previously under IRM 4.7.2.4, System Security Responsibilities and subsections, was moved to IRM 4.7.2.1.3, Responsibilities.

(3) Content previously under IRM 4.7.2.6, Resources, was moved to IRM 4.7.2.1.6, Related Resources.

(4) Throughout the IRM administrative staff was updated to administrative support staff and Online 5081 updated to OL5081.

(5) Discoverer is no longer used by the IRS. References to Discoverer have either been deleted or replaced with Tableau where applicable.

(6) Subsections and paragraphs have been renumbered due to the addition of the internal controls and new content.

(7) Significant changes to this IRM are reflected in the table below:

Original Reference New Reference Description of Change
4.7.2.1 4.7.2.1 Title changed from "Overview" to "Program Scope" to reflect the internal controls contained in this subsection. Information was added or moved from previous subsections for background, authority, responsibilities, program controls, acronyms, and related resources.
4.7.2.2.1 (7) 4.7.2.2.1 (7) Added "Whistleblower Office" employees to the list of employees that may be granted access to ERCS.
N/A 4.7.2.2.1 (8) Added "shared administrative associates" from TE/GE and SB/SE Collections must meet the same prerequisites.
4.7.2.2.2 4.7.2-2, 4.7.2-3, 4.7.2-4, 4.7.2-5, 4.7.2-6 Updated "ERCS OL5081 Applications" table, divided by user types, CCP, TS, Specialty and IIC, SB/SE and LB&I and moved to exhibits:
Deleted rows for Area applications that no longer have Technical Services (TS) employees.
Added information for shared administrative associates.
Updated Location of User for TS employees from states to TS Areas.
Updated LB&I "315" application to LB&I "330" .
4.7.2.2.3 (b) 4.7.2.2.3 (b) First "Note" clarified that users requesting temporary write permission need to include the business reason it’s needed in the OL5081 request.
Second "Note" . Added the business reason must be included in the OL5081 request, the TM must approve, and not by proxy.
Third "Note" clarified that when a TM approves write permission for a manager or acting manager, they are agreeing to approve items input and must be an active ERCS user with second level approval.
4.7.2.2.3 (c) 4.7.2.2.3 (c) Added "Admin" and "Limited" to user types.
4.7.2.2.3 (d) 4.7.2.2.3 (d) Updated to reflect field names in the OL5081 program, Remove After (#Days).
Divided the "Note" in order to show two examples.
4.7.2.2.3 (e) 4.7.2.2.3 (e) Included the business reason for access needs to be in the Special Instructions box of the OL5081 request.
"Note" added the exception for limited access users.
N/A 4.7.2.2.4(2) Added that existing users should enter their ERCS login in the User ID field of the OL5081. The AIMS/ERCS analyst will determine the login name for a new user and enter it in the User ID field prior to approving and forwarding to the SA to be added to the ERCS system.
4.7.2.2.4 (3) 4.7.2.2.4 (4) Added clarification to contact the "Enterprise Service Desk" for locked passwords.
Updated "help desk" to "Enterprise Service Desk" .
4.7.2.2.4 (6) 4.7.2.2.4 (7) Updated the password requirement from "at least eight characters" to "at least fifteen characters" .
4.7.2.2.5 4.7.2.2.5 Changed name from "Requesting a Change in Login Name" to "Changing a Login Name" .
This subsection was completely rewritten.
OL5081s for name changes are systemic, a login name change can be requested after a name change has been processed.
It is preferable that login names not be changed since audit trails are created and researched by login name.
4.7.2.3.2 (4) 4.7.2.3.2 (4) Clarified that a manager with permanent first level approval permission can delegate temporary first level approval for acting managers. Added that a manager with permanent write permission may delegate temporary write permission to a shared administrative support employee in another group if assistance is needed.
4.7.2.3.2 (5) 4.7.2.3.2 (5) Added the need for temporary permission changes lasting over 30 days to be requested via OL5081.
N/A 4.7.2.3.2 (6) Added content to define the length of temporary permission as 180 days.
Permanent permission will be granted for longer periods of time and deleted via OL5081 when no longer needed.
4.7.2.3.2 (9) 4.7.2.3.2 (11) Updated to specify that when an ERCS user is suspended, access must be deleted via OL5081 by the manager, if not systemically deleted.
4.7.2.3.2.1 4.7.2.3.2.1 Changed number of user types to ten.
Added to the definition of users included under the "Group" user type.
Changed user type name from "Area/Industry" to "Area" and added to the definition of users.
Added user type "Limited" and definition of users.
4.7.2.3.2.1 (3) 4.7.2.3.2.1 (3) Added content to reflect LB&I administrative support staff may be granted AMSOC disposal code permission to input transfers to other practice areas.
4.7.2.3.2.1 (4) 4.7.2.3.2.1 (4) Added that a territory manager may approve write permission for a group or team manager if they are an active ERCS user with Territory second level approval permission.
4.7.2.3.2.1 (5) 4.7.2.3.2.1 (5) Added content to reflect AMSOC disposal code permission may be granted to PSP users responsible for transfers out-of-area and short closures.
N/A 4.7.2.3.2.1 (15) Added paragraph to address AIMS/ERCS manager permission.
AIMS/ERCS managers need Admin read and write for areas and practice areas they support.
PSP read and first level approval are also needed for their group AAC to approve short closures.
4.7.2.3.2.1 (15) 4.7.2.3.2.1 (16) Changed "staff" to "analysts and assistants" .
Added emergency, temporary first or second level permission should be granted and removed for AIMS/ERCS analysts for specific requests.
Added content to reflect AMSOC disposal code permission will be granted to those responsible for input of short closures.
N/A 4.7.2.3.2.1 (18) "Note" added to recommend the monthly monitoring of permission reports by the AIMS/ERCS staff.
N/A 4.7.2.3.3 (3) "Note" added content to remind users to enter as much of the taxpayer’s name as possible on a name search to reduce the risk of matching an IRS employee.
N/A 4.7.2.3.3 (4) Updated to reflect a change in business rules, users can now view returns, regardless of status code, as long as they have permission to the AAC.
N/A 4.7.2-1 "Acronyms and Definitions" exhibit added.
N/A 4.7.2-2 "ERCS OL5081 Applications for CCP" exhibit added.
N/A 4.7.2-3 "ERCS OL5081 Applications for TS" exhibit added.
N/A 4.7.2-4 "ERCS OL5081 Applications for Specialty and IIC" exhibit added.
N/A 4.7.2-5 "ERCS OL5081 Applications for SB/SE" exhibit added.
N/A 4.7.2-6 "ERCS OL5081 Applications for LB&I" exhibit added.

(8) Minor editorial changes have been made throughout this IRM. Some items were reworded for clarity. Also, website addresses and IRM references were reviewed and updated, as necessary.

Effect on Other Documents

IRM 4.7.2 dated October 14, 2015 is superseded.

Audience

Small Business/Self Employed (SB/SE), Large Business and International (LB&I), Tax Exempt & Government Entities (TE/GE) and Headquarters (HQ) employees in Return Preparer Office (RPO), Whislteblower Office (WO), and National Research Program (NRP) who use ERCS.

Effective Date

(10-11-2019)

Robin L. Kidwell
Director, Technology Solutions
Small Business/Self-Employed

Program Scope

  1. This IRM section discusses ERCS security and procedures for controlling and maintaining ERCS access.

  2. Purpose: To provide guidance needed to complete the correct Online 5081 (OL5081) ERCS application and provide recommendation for approval and granting of permissions based upon the user’s official duties.

  3. Audience: ERCS is used by employees in Small Business/Self Employed (SB/SE), Large Business and International (LB&I), Tax Exempt & Government Entities (TE/GE), and Headquarters (HQ) employees in the Return Preparer Office (RPO), Whistleblower Office (WO) and National Research Program (NRP) who monitor inventory, enter examination time, add new records or update existing records on ERCS. Employees include analysts, managers, technical employees, administrative support personnel and shared administrative support personnel.

  4. Policy Owner: Chief Information Officer.

  5. Program Owner: SB/SE Director, Technology Solutions.

  6. Primary Stakeholders: LB&I.

Background

  1. All ERCS users, their managers, and ERCS support personnel (including system administrators, database administrators and ERCS developers) should be familiar with this IRM to ensure they are aware of the system security features and the requirements for ERCS access.

  2. 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, Privacy and Information Protection.

Authority

  1. IRM 10.8.1, Information Technology (IT) Security, Policy and Guidance, establishes the security program and the policy framework for the IRS.

Responsibilities

  1. Ensuring the security of ERCS is the responsibility of every user and support personnel including the AIMS/ERCS staff, the ERCS system and database administrators, and the ERCS developers.

  2. ERCS User Responsibilities: All users are responsible for ensuring the security of the ERCS system. This includes but is not limited to the following:

    • Protecting ERCS passwords.

    • Creating strong passwords.

    • Removing Smart Cards before leaving work stations.

    • Promptly picking up ERCS prints from printers in common areas.

    • Updating and approving work timely and accurately.

    • Protecting taxpayer data from unauthorized access.

    • Reporting security incidences to the proper authorities timely.

  3. AIMS/ERCS Staff Responsibilities: In addition to user responsibilities, the AIMS/ERCS staff security responsibilities include but are not limited to the following:

    • Ensuring users have met the prerequisites before approving OL5081s for ERCS access.

    • Granting user permission based on and limited to the user’s official duties and deleting permission records when no longer needed.

    • Training and/or providing job aids to new users regarding security requirements.

    • Ensuring the continued integrity of the ERCS database. This includes reviewing and correcting data issues and participating in operational reviews based on IRM requirements and local procedures.

  4. System Administrator (SA) Responsibilities: The ERCS system administrator responsibilities include but are not limited to:

    • Ensuring all security features are installed and operating properly on the ERCS server.

    • Processing OL5081s for ERCS and SSIVL access to add or delete users from the system.

    • Resetting passwords for users with locked or forgotten passwords.

    • Working OS GetServices tickets to resolve ERCS system related user issues.

  5. Database Administrator Responsibilities: The database administrator responsibilities include but are not limited to:

    • Ensuring all Oracle security features are installed and operating properly.

    • Working OS GetServices tickets to resolve ERCS database related issues.

Program Controls

  1. 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.

  2. 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.

Acronyms

  1. See Exhibit 4.7.2-1 , Acronyms and Definitions, for acronyms used in the IRM.

Related Resources

  1. The following resource documents contain information regarding IRS security requirements and ERCS programs related to creating and reading ERCS audit trails:

    • IRM 10.8.1, Policy and Guidance

    • Security chapter of the ERCS Technical Reference Manual (TRM)

    • Read Audit Trails section of the Utility Miscellaneous Programs chapter of the ERCS TRM

  2. The AIMS/ERCS website contains helpful information to resolve problems and answer questions. The following types of information is available:

    • ERCS Manuals - this section contains the ERCS user handbooks and the ERCS TRM. The manuals describe the menu options, screens, reports and other relevant information.

    • AIMS IRM and ERCS IRM.

    • Troubleshooting - this section has information on current issues such as setting up an ERCS ICON, password issues, and adding an ERCS printer.

    • Contacts - this section contains contact information for AIMS/ERCS Staff, Area and Campus Programs, Employee Group Codes, LB&I Contacts, and other helpful contact information.

  3. For security issues concerning record of tax enforcement results (ROTER) information, see the Section 1204 Website. IRM 1.5, Managing Statistics in a Balanced Measurement System, provides further guidelines for the appropriate use of statistics by managers and employees.

ERCS Access

  1. Managers must ensure that employees are only given ERCS access if their job requires it. Managers must also ensure access is removed timely when the employee’s job no longer requires ERCS access. Permission must be restricted so the employee only has what is necessary in order to perform official duties.

  2. This section discusses the requirements for obtaining and maintaining access to ERCS programs and data. The following topics are included:

    • Meeting the prerequisites

    • Choosing the OL5081

    • Completing the OL5081

    • Setting ERCS login names and passwords

    • Maintaining ERCS passwords

    • Changing login name

    • Resolving ERCS access issues

Meeting the Prerequisites

  1. A background check must be completed on permanent IRS employees requesting ERCS access prior to approving the OL5081 request.

  2. Interns and cooperative education students may be given ERCS access, if hired for a position where ERCS access is required to accomplish their official duties. For these users a background check must be initiated, but it does not have to be completed, prior to granting the employee access to ERCS.

    Note:

    "Background Date" is marked as initiated on the OL5081 if the user's fingerprints have been received.

  3. Volunteers from the Wounded Warrior Program may be given ERCS access if it is required based on the position they have been selected to fill. These users have previously had background checks as part of their service in the military. If the user is with the IRS longer than six months, a background check must be initiated.

  4. For other special IRS initiatives where an exception to the background check may be granted, contact a HQ ERCS analyst.

  5. Employees must have completed a UNAX Briefing and UNAX Certification prior to being given access to ERCS data. The employee's manager is responsible for ensuring this has been completed prior to approving the OL5081.

  6. Employees hired into a position requiring ERCS access are granted access on the approval of their managers and the AIMS/ERCS staff. These positions include:

    • Exam group managers in SB/SE and their administrative support staff

    • Team managers in LB&I and their administrative support staff

    • Territory managers (TM)s and area directors in SB/SE and their administrative support staff

    • Territory managers, Directors of Field Operations (DFO)s, and practice area directors in LB&I and their administrative support staff

    • Planning and Special Programs (PSP) section chiefs, program coordinators, technical employees and their administrative support staff

    • Technical Services (TS) managers, selected technical employees and their administrative support staff

    • Joint Committee Review (JCR) managers and their administrative support staff

    • National Quality Review Staff (NQRS) managers and their administrative support staff

    • Quality Measures and Analysis (QMA) managers and their administrative support staff

    • LB&I Quality Measurement System (LQMS) managers and their administrative support staff

    • Centralized Case Processing (CCP) managers and selected members of their staff

    • Return Preparer Office (RPO) managers and their administrative support staff

    • AIMS/ERCS managers, analysts, assistants and their administrative support staff

    • Headquarters (HQ) ERCS analysts

      Note:

      An employee detailed into a position above or acting for an employee in a position above, may also be granted access for the duration of the detail or acting assignment.

  7. An employee may be granted access on the approval of their manager and a HQ ERCS analyst if there is justification that access is needed in order to perform the user's official duties. These employees include the following:

    • SB/SE and LB&I HQ analysts

    • RPO analysts

    • NRP analysts

    • Treasury Inspector General for Tax Administration (TIGTA) employees

    • WO employees

  8. Shared administrative associates from TE/GE and SB/SE Collections supporting SB/SE and LB&I groups are required to meet the same prerequisites.

Choosing the OL5081

  1. To obtain access to ERCS, employees must complete an OL5081. Employees may need to complete more than one OL5081 for ERCS if permission is needed in more than one area or in both LB&I and SB/SE. If the employee requires more than one OL5081 for ERCS, the first one should be submitted within the user's support area and Business Operating Division (BOD). The user should wait until given a login and password to the system before submitting additional requests to other areas. There is an exception for HQ analysts, NRP analysts, WO employees, and TIGTA employees. Refer to IRM 4.7.2.2.2 (5) for OL5081 procedures for these employees.

    Note:

    When an LB&I user needs access to multiple groups within LB&I only one OL5081 needs to be input. It should be for the area that supports the user.

  2. ERCS users are supported by the AIMS/ERCS staff located in the user's local area or CCP campus, with the exception of employees in Fraud/Bank Secrecy Act (BSA), International Individual Compliance (IIC), WO employees, and TIGTA. Fraud/BSA, IIC, and RPO users have their own AIMS/ERCS support staff. WO employees are supported by Area 206, Western. Employees in TIGTA are supported by the area or campus where their access has been granted. Refer to the AIMS-ERCS Staff by User Location for support contact information.

  3. It is important to select the correct OL5081 ERCS application because each one is routed to the local AIMS/ERCS staff for approval, creation of the user's ERCS employee record and granting permission. The ERCS OL5081 Application tables, Exhibit 4.7.2-2 through Exhibit 4.7.2-6, include all ERCS applications for requesting access. Except for HQ analysts, NRP analysts, WO employees, and TIGTA employees, the exhibit tables should be used to determine a user's initial OL5081 application selection. For the excepted employees refer to IRM 4.7.2.2.2 (5).

  4. On rare occasions if access is needed to update records for an additional area or BOD, subsequent OL5081s must be completed. Write permission across areas requires justification in the Special Instructions Box on the OL5081.

  5. HQ analysts, NRP analysts, WO employees, and TIGTA employees must have an approved OL5081 for ERCS-TCC-HQ ANALYSTS (ERCS) prior to requesting any other ERCS OL5081 application. This ERCS application is routed to the HQ ERCS analysts for approval. A HQ ERCS analyst will contact the employee to determine what level of access and permission are needed, and then will inform the employee which subsequent OL5081 ERCS application to submit. The HQ ERCS analyst will alert the AIMS/ERCS managers in the areas impacted, and let them know that ERCS access has been granted.

  6. Information for OL5081 applications for Statistical Sampling Inventory Validation (SSIVL), Tableau and AIMS/ERCS staff are discussed in IRM 4.7.10, AIMS/ERCS Staff. See AIMS, ERCS, SETTS, SSIVL, and Tableau Personnel Listing for Headquarters for contact information for the HQ analysts who support these programs.

Completing the OL5081

  1. The OL5081 for new users must contain sufficient information for the AIMS/ERCS analyst to add the employee's permission records on ERCS as this document serves as the official record of the user's approved level of access. The following information must be included in the Special Instructions Box, either by the employee, the employee's manager, or the AIMS/ERCS analyst:

    1. AIMS Assignee Code (AAC) or AACs - The Primary Business Code (PBC), Secondary Business Code (SBC), and Employee Group Code (EGC) combination the user needs permission for in order to run reports, update records, apply time, etc. These three codes make up the 12 digit AAC.

    2. Permission type - The permission types consist of read, write, first level approval, and second level approval. With read permission users can run reports and see returns in their group. Write permission gives the user the ability to generate forms, update returns, and add or update employee records in the group. First level approval permission gives managers and acting managers the capability to approve updates made by other users in the group. In general, administrative support employees are given read and write permission, managers are given read and first level approval permission and TMs are given read and second level approval permission.

      Note:

      Acting managers with inventory will not routinely be given write permission during an acting assignment and must not be given permanent write permission. Users requesting temporary write permission should include the requested permission in the Special Instructions box and the reason it’s needed, when completing (or modifying) their OL5081 so it is included when the manager approves the form.

      Note:

      Managers may be given write permission, temporary is preferable, with TM approval. The manager must include the requested permission in the Special Instructions box and the reason write permission is needed, when completing (or modifying) their OL5081 so it is included when the TM approves the form. The OL5081 request must be approved by the TM and not by proxy.

      Note:

      Territory managers must approve requisitions, statute updates, and transfers or closures to a return generating the command code AMSOC if made by a manager in their territory. Since an acting manager cannot approve work for returns in their own inventory, the TM may need to approve updates made to the acting manager's inventory. Therefore, if a TM approves write permissions for a manager or acting manager, they must be an active ERCS user with second level approval.

    3. User Type - (Group, PSP, Review (Technical Services), Sample Review, CCP, Territory, DFO, Area, Admin, Limited). The user type determines the menu options available to the user.

    4. Length of Access - If the user needs permanent access the Remove After (#Days) box should be left blank on the OL5081. If the user only needs temporary access, the number of days should be entered in the Remove After (#Days) box.

      Note:

      A login and password give the user access to the ERCS server. Permission records give the user access to run ERCS programs.

      Example:

      A user acting for the manager on an ongoing basis may need permanent access to the server, but temporary permission to approve work during each acting assignment.

      Example:

      A user acting for the manager for a specific period of time would only need temporary access to the server and to ERCS. They would notate the number of days on the OL5081. This will ensure the user’s access and permission records are deleted after the acting assignment is completed.

    5. Justification - The business reason the employee needs access should be included in the Special Instructions box. If permission is needed outside the user's group or function, a justification must be input. Any other special instructions should be included such as detail assignment or acting assignment.

      Note:

      Except for Limited Access users, examiners access to ERCS should be restricted to acting assignments.

ERCS Login Names and Passwords

  1. Every ERCS user is given an eight character login name consisting of the user's first initial, middle initial, first four characters of the last name and a two digit location code. If the user does not have a middle name, an x is substituted. If the user's last name is less than four characters, the subsequent letters of the user's first name or the letter x is used to make up the remaining characters. The location code is used to set the user's default printer group when the user is added to ERCS. The user may change the printer group via the "Change Printer Group" option from the ERCS Login Menu screen. As shown in the table below, the location code may not be the same as the number in the Printer Group name:

    ERCS Location Codes for Login Names and Printer Groups

    Location Location Code Printer Group
    Maine, Massachusetts, New Hampshire, Vermont 04 exam04
    Connecticut, Rhode Island 06 exam06
    Brooklyn, New York 11 exam11
    Manhattan, New York 13 exam13
    Upstate New York 16 exam16
    Cincinnati Campus 17 exam17
    New Jersey 22 exam22
    Pennsylvania 23 exam23
    Ohio 31 exam31
    Southern California 33 exam33
    Indiana 35 exam31
    Illinois 36 exam36
    Michigan 38 exam38
    Iowa, Nebraska, Wisconsin 39 exam39
    Minnesota, North Dakota, South Dakota 41 exam41
    Kansas, Missouri 43 exam43
    Memphis Campus 49 exam49
    Delaware, Maryland 52 exam23
    Virginia, West Virginia 54 exam23
    North Carolina, South Carolina 56 exam56
    Georgia 58 exam65
    North Florida 59 exam65
    Kentucky, Tennessee 62 exam31
    South Florida 65 exam65
    Puerto Rico 66 exam98
    Alabama, Louisiana, Mississippi 72 exam72
    Arkansas, Oklahoma 73 exam72
    South Texas 74 exam74
    North Texas 75 exam75
    Houston, Texas 76 exam76
    Central California 77 exam77
    Colorado, Idaho, Montana, Utah, Wyoming 84 exam84
    Nevada 86 exam86
    Arizona, New Mexico 86 exam90
    Alaska, Oregon, Washington 91 exam91
    Hawaii 91 exam90
    Northern California 94 exam94
    Los Angeles 95 exam95
    District of Columbia 98 exam98

     

  2. Existing users should enter their ERCS login name in the User ID field on an OL5081 request. For new users, the AIMS/ERCS analyst will determine what the login name should be, following the guidelines above, and enter it in the User ID field on an OL5081 request prior to approving and forwarding to the SA to be added to the ERCS system.

  3. The ERCS system prompts users to change their password every 90 days. Passwords can be changed prior to 90 days, but after 90 days the account is locked. Users must change their password when accessing ERCS for the first time and after their password has been unlocked or reset.

  4. Every user must log onto ERCS at least once every 45 days or their ERCS account will be locked. Once the user's ERCS account is locked, the user has an additional 15 days to get the account unlocked and log into ERCS. To have a password reset or account unlocked, the first point of contact should be the Enterprise Service Desk.

    Note:

    Putting a reminder in a calendar to log in every 30 days may help prevent passwords from getting locked.

    Note:

    When contacting the Enterprise Service Desk to unlock or change a password, users should stay on the line until the temporary password has been successfully changed and ERCS can be accessed.

  5. ERCS passwords are locked after three unsuccessful attempts to enter a password.

  6. If the user fails to take the necessary steps to get the account unlocked and log in, the account is subject to deletion. ERCS accounts are deleted after 60 days of non-use.

  7. To get a password reset or unlocked, or a deleted account re-instated, see the Password Reference Guide for ERCS in the Troubleshooting section of the AIMS/ERCS website. Passwords must be at least fifteen characters long and adhere to specific rules. These rules, along with directions on how to set a strong ERCS password are included in the Password Reference Guide for ERCS.

  8. ERCS users are responsible for protecting their password. Passwords must never be shared with anyone and are not to be written down and left where they may be seen.

Changing a Login Name

  1. When a user has a name change the OL5081 program systemically generates a Modify User Profile request. It is preferable that the login name not be changed since audit trails are created and researched by login name. The AIMS/ERCS staff will input the following:

    • In the User ID field enter the current login name.

    • In the Special Instructions box enter "name change only, don’t change login name" .

  2. A user may request to have their login name changed by submitting a Modify Profile OL5081 request for ERCS under their local Area application. The following will be input for processing:

    • In the Special Instructions box the user will enter, "This request is for a login name change" and their current ERCS login name.

    • In the User ID field the AIMS/ERCS staff will enter the new login name. It must adhere to the login rules. See IRM 4.7.2.2.4 for more information about setting login names.

  3. The OL5081 is routed to the SA to change the login name on the ERCS system. It is then routed back to the local AIMS/ERCS staff to update the user's employee record, delete old permission records and add permissions with the new login.

  4. Once the user’s ERCS employee record has been updated, they must submit Modify Profile OL5081s for any additional ERCS applications for other Areas, The newly assigned login will be entered in the User ID box. In the Special Instructions box the user will enter, "This request is for a login name change" and their current ERCS login name.

    Example:

    The user’s local area application is ERCS-TCC-SBSE-AREA 202-CENTRAL, but they also have an active application for ERCS-TCC-SBSE-AREA 203-CENTRAL. Once the Modify Profile request for their local application has been processed and their ERCS employee record has been updated, the user will submit a Modify Profile request for the second application.

  5. If the user also has one of the following ERCS applications and has requested a login name change, the user must also submit a Modify Profile OL5081 request for the subsequent application:

    • ERCS-TCC-HQ ANALYSTS (ERCS)

    • ERCS-TCC-AIMS-ERCS STAFF (ERCS)

    Note:

    A login name does not need to be changed if a user changes locations.

Security Features of ERCS

  1. In addition to numerous program validation and consistency checks to ensure data is valid, ERCS security is assured by:

    • Limited system and data access by users to ensure information is provided on a need-to-know basis.

    • Audit trail generation and review of users' activities.

    • Electronic managerial approval of certain actions.

  2. The following topics are included in this section:

    • ERCS Employee Records

    • Permissions

    • Employee Audit Security

    • Audit Trails

    • Audit Trail Review

ERCS Employee Records

  1. ERCS interfaces with the Corporate Authoritative Directory Service (CADS) to download employee information, including the employee’s Standard Employee Identifier (SEID), into the ERCS database. Only data for SB/SE, LB&I, WO, and RPO employees is downloaded. When an employee record is added to ERCS, the user enters the employee's SEID. It is validated against the downloaded employee data from CADS (Discovery Directory). If a user is unable to add a new employee to ERCS because the employee's SEID is not accepted, the user should contact the local AIMS/ERCS staff for assistance. Refer to the AIMS/ERCS Staff by User Location for contact information.

  2. Employee records are added by a user with write permission for the AAC the employee will be assigned to. This includes administrative support staff or the local AIMS/ERCS staff.

  3. The information on the ERCS employee record should be entered accurately and completely. Any changes to the record should be updated as soon as they are known. ERCS employee data is used in the following:

    • Verifying a user is authorized to access ERCS.

    • Determining if an employee is required to charge technical time.

    • Validating the employee's AAC during inventory assignment.

    • Determining if the employee should have access to the Managerial Approval menu option.

    • Determining if an employee's actions require managerial approval.

    • Protecting an employee's tax return from unauthorized access.

    • Determining who should receive employee audit security alerts.

    • Determining if the employee's tax return can be audited in the area.

    • Creating the ERCS audit trails.

  4. Employee records should be updated when an employee’s name changes. If an employee has been issued a pseudonym for security reasons, the pseudonym should be entered on the ERCS employee record followed by a space and the literal XX. This will alert the AIMS/ERCS staff that the name on the employee record is not the employee’s real name.

  5. ERCS employee records should be inactivated when the employee leaves the IRS or transfers within the IRS to a non-ERCS position. If the employee’s time is entered on ERCS, the end date on the employee record must be set to the last day the employee is required to enter time. Otherwise, the last day the employee worked should be entered for the employee’s end date. The login name should not be removed from the ERCS employee record when an employee record is inactivated. It is a link to the ERCS audit trails.

Permissions

  1. Permission records determine what menu options are available to a user within the ERCS Main Menu. They also give users the ability to run reports, update employee records and returns, input time, and approve work.

  2. The permission types are read, write, first level approval, and second level approval. Managerial approval can be restricted so the user can only approve updates by return. Permission records are based on AACs. For example, a group manager may be given read and first level approval permission for the group's AAC. A CCP user in Memphis may be given read and write permission for returns in Memphis CCP.

  3. ERCS programs use the employee's permission records with the ERCS national status code files to restrict access based on the status code on the return. For example, a group user may only update returns in a group status. CCP users may only update returns in a CCP status. See Document 6036, Examination Division Reporting System Codes Booklet, for a list of status codes used by examination.

  4. Permission records are added by the AIMS/ERCS staff. Managers with permanent first level approval permission can delegate temporary first level approval permission for their group to an acting manager as long as the employee has an active ERCS login and password. Approval permission should only be granted for the length of the acting assignment. Managers with permanent write permission may delegate temporary write permission for their group to a shared administrative support employee in another group if assistance is needed.

  5. For permanent permission changes within the same area and temporary changes lasting over 30 days, the user is required to submit a Modify Profile request via OL5081.

  6. Permission can be permanent or temporary. Temporary permission is granted for up to 180 days, if needed for a longer period of time, permanent permission should be granted. The user will request deletion of the permission via OL5081 when no longer needed.

  7. A temporary, emergency permission change within the same area may be granted by the user's local AIMS/ERCS analyst. The request should be made by management via e-mail. For emergency permission not covered in these instructions, contact a HQ ERCS analyst.

  8. If an employee acts for their manager, first level approval permission will be granted with a beginning date and an ending date covering the acting assignment. If the acting assignment ends early, and permission was delegated by the group manager, the manager will update the permission records to the correct end date, but the ERCS employee record will remain active.

  9. When an employee record is inactivated, the ERCS program updates the employee's permission records to end on the employee's inactivation date.

  10. If a user no longer needs ERCS access due to a change in position or duties, a Delete OL5081 must be input.

  11. If a user is suspended from active duty the manager must input a Delete OL5081 for the user’s ERCS access if one isn’t systemically generated.

  12. Menu Options 11 through 19 on the ERCS Login Menu are granted via special OL5081s. These OL5081s go through the HQ ERCS analysts or the HQ SSIVL analysts for approval and to add the special permissions enabling the user to access the menu options. These options are described below:

    Menu Option Number Menu Option Required Position OL5081 Application Description
    11 AIMS/ERCS Analyst Menu AIMS/ERCS staff ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu contains options to aid in the support of ERCS end-users.
    12 SSIVL Analysts from SB/SE, LB&I, TE/GE, and W&I SSIVL-### This menu contains programs associated with SSIVL including extracting data and maintaining the SSIVL AAC list.
    13 SSIVL for CCP Analysts and administrative support staff in CCP SSIVL-CCP-### This menu contains programs associated with SSIVL including extracting data and running reports.
    14 Check Mail Security officers, PSP chiefs, AIMS/ERCS staff ERCS-TCC-AIMS-ERCS STAFF (ERCS) This option allows users to read ERCS system e-mail.
    15 AIMS Download AIMS/ERCS staff ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu contains the ERCS to AIMS Uploading Programs.
    16 National Codes HQ ERCS analysts, HQ SETTS analyst ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu allows users to validate new codes and update national files.
    17 SETTS AIMS/ERCS staff ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu contains the Summary Examination Time Transmission System (SETTS) programs.
    18 User Administration HQ ERCS analysts ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu contains options for granting access to menu options included in this table.
    18 User Administration SSIVL analysts SSIVL-ADMIN This menu contains options for granting access to SSIVL.
    19 Security Security officers and AIMS/ERCS managers and analysts ERCS-TCC-AIMS-ERCS STAFF (ERCS) This menu contains options for reading ERCS audit trails.
Recommended Permissions
  1. ERCS permissions are granted to users based on user type and permission type. The ten user types include:

    User Type Users
    PSP PSP section chiefs, analysts, program coordinators, technical employees and administrative support staff
    Group SB/SE, LB&I, and RPO field group and tax compliance group managers, team managers, technical employees and administrative support staff
    Territory Territory managers and administrative support staff
    DFO Directors of field operations and administrative support staff
    Area SB/SE area directors, LB&I practice area directors, and administrative support staff
    Review TS and JCR managers, analysts, technical employees, and administrative support staff
    Sample Review NQRS, QMA, LQMS managers and administrative support staff
    CCP CCP managers, analysts, technical employees, and administrative support staff
    Admin AIMS/ERCS managers, analysts and assistants. Admin users have permission to run ERCS as any user type in order to provide support for end-users.
    Limited Technical employees within an examination group, PSP, review or sample review who only have permission to input time and print their own inventory and time reports.

    Note:

    For information about the menu options available to each user type, see the Main Menu chapter of the ERCS TRM.

  2. Read permission is granted to all ERCS users. Write and approval permission is granted based on the user’s need to accomplish assigned duties.

  3. Group administrative support staff need read and write permission as a Group user for the AAC to which they are assigned and for any other AAC in which they must assist in updating returns, running reports and inputting time. LB&I administrative support staff may also be granted AMSOC Disposal Code 30 permission in order to transfer cases to other LB&I groups in a different Practice Area.

  4. Group managers and LB&I team managers need read and first level approval permission as a Group user for the AAC to which they are assigned and for any other AAC in which the manager must assist in approving updates to returns. A group or an LB&I team manager may also be given write permission, temporary is preferable, if the territory manager is in agreement, approves the OL5081 and is an active ERCS user with Territory second level approval permission.

  5. PSP administrative support staff need read and write permission as a PSP user for the AAC to which they are assigned and for any other AAC in which the employees must assist in updating returns, running reports and inputting time. Depending on their duties the employee may be given permission for all PSP in the area. Users responsible for transfers out-of-area should be granted AMSOC disposal code 30 permission, and those responsible for short closures may also be granted permission for AMSOC Disposal Codes 20, 21, 31 and 35.

  6. In SB/SE PSP section chiefs and/or the program coordinators (depending on local procedures) need read and first level approval permission as a PSP user for the AACs in their control. The PSP program coordinators should consult with their section chief before requesting write permission since some updates input by the program coordinator require second level approval. In LB&I, PSP analysts need read and first level approval permission as a PSP user for the AACs in their control.

  7. PSP territory managers and/or the PSP section chiefs (depending on local procedures) need read and second level approval permission for PSP in the area.

  8. Non-managers in CCP may be given read and write permission for CCP AACs as needed to perform their duties. Users checking in and assigning inventory need write permission for the CCP campus in order to update unassigned returns.

  9. CCP managers may be given read, write, and first level approval permission as a CCP user for their AAC.

  10. Department managers in CCP need read permission for the CCP campus, and may be given second level approval permission, as needed.

  11. TS administrative support staff may be given read and write permission for their review AACs. Users checking in and assigning inventory need read and write permission in order to update unassigned returns. TEs in TS may be given read and write permission for their review AACs, if needed, in order to perform their official duties.

  12. TS managers may be given read and first level approval permission as a Review user for their AACs.

  13. Territory managers in TS may be given Review read, first level and second level approval permission, as needed.

  14. Sample review managers and administrative support staff need read and write for their sample review AACs.

  15. AIMS/ERCS managers need Admin read and write permission for their area and for areas and practice areas they support in Specialty and LB&I. They also need PSP read and first level approval permission for their group AAC to approve short closures.

  16. AIMS/ERCS analysts and assistants need Admin read and write permission for their Area and for Areas and Practice Areas they support in Specialty and LB&I. In an emergency, temporary first or second level approval permission may be granted to an AIMS/ERCS analyst to approve a specific request. It’s recommended that approval permission be deleted once the request is completed. AIMS/ERCS staff responsible for processing short closures will be granted permission for AMSOC Disposal Codes 28, 29, 33,36. 37, 38, 39, 40 and 41.

  17. HQ SB/SE and LB&I analysts may be granted Area read permission for multiple areas if access is required to perform their official duties. See also IRM 4.7.2.2.1 (7) for additional information.

  18. HQ ERCS analysts may be granted Admin read and write permission, as needed, in order to perform their official duties.

    Note:

    It’s recommended that permission records be reviewed by the AIMS/ERCS staff monthly to ensure permission records are deleted when no longer needed and to verify correct permission has been granted. A permission report can be run through Tableau for review.

Employee Audit Security

  1. An employee audit occurs when the tax return of an IRS employee is examined. ERCS provides special security features for employee returns under audit. When any of the following events occur an audit trail is created and an ERCS system e-mail alert is generated:

    • A user enters their own SSN or the SSN of a spouse (if a joint return was filed).

    • The source code on a return is changed to or from Source Code 46, "Employee Return" .

    • The "Employee Audit" indicator is turned on or off on a return.

    • An unauthorized user attempts to access an employee's return.

    • A user attempts to add an employee return to ERCS for an employee who should not be audited in the same area.

    • A employee's return is on AIMS and during AIMS to ERCS processing, the program attempts to add the return to ERCS in an area where the employee should not be audited.

    • The addition of a high profile employee return to ERCS (such as the Security Officer).

  2. If there is a Security Officer with ERCS access for the area, the employee audit e-mail is sent to the Security Officer. Otherwise, the ERCS system e-mail is sent to the PSP TM. See IRM 4.7.5, Planning and Special Programs (PSP), for more information about the employee audit e-mail.

    Note:

    ERCS system e-mail is sent and received on the ERCS server.

  3. Not all employee audit alerts are an indication the user is doing something inappropriate. For example, alerts may be generated when a user accesses an employee's return by taxpayer identification number (TIN), and the program finds one tax period assigned to the user's group and one tax period controlled in another group or function. An alert will be generated for the tax period that is not in the user's group. Some alerts are an indication of inappropriate access, for example, when a user enters their own SSN. See Employee Audits on the AIMS/ERCS website for more information.

    Note:

    When an employee performs a search using the taxpayer’s name and the name or name control entered matches any IRS employee, audit trails are created for each matched employee. Entering as much of the taxpayer’s name as possible reduces the risk of matching an employee.

  4. Employee returns are not included on ERCS reports and screens if the user is not authorized to see the data. In general, this means the user must have permission to the AAC of a return before the return information may be viewed, regardless of the status code. Users are not notified when an employee audit alert is generated for their access.

  5. For more information about employee audit security features refer to the Security chapter of the ERCS TRM.

Audit Trails

  1. An ERCS audit trail is a record of an event initiated by a user or program on the ERCS server. The event can be anything from execution of a program to accessing or changing data. Audit trails can be used to research when changes were made to data, and to determine who input or approved the changes. Audit trails can also detect potential unauthorized access or suspicious activities.

  2. ERCS captures audit trail information for the following events:

    • Addition or deletion of taxpayer records.

    • Modification and managerial approval for selected updates to return information.

    • Research of taxpayer records.

    • Addition of employee records.

    • Modification of selected employee information.

    • Addition, deletion or modification of ERCS permissions.

    • User access to the ERCS Main Menu.

    • Selected events regarding employee returns under audit.

  3. The event information captured in an ERCS audit trail includes, but is not limited to the following:

    • The time and date of the event.

    • The user identification.

    • The approver’s identification, if the action required approval.

    • The type of activity (add, update, research, etc.)

    • The data that was accessed or changed.

    • The program that was executed.

  4. Audit trail information may be accessed from special ERCS menus by AIMS/ERCS analysts, HQ ERCS analysts, and designated system security officers. Managers should consult their local AIMS/ERCS staff for assistance if information from an ERCS audit trail is needed. For more information about ERCS audit trails refer to the "Read Audit Trails" section of the Utility Miscellaneous Programs chapter of the ERCS TRM. For information about the responsibilities of the AIMS/ERCS staff regarding the ERCS audit trails, see IRM 4.7.10, AIMS/ERCS Staff.

Audit Trail Review

  1. All modernized IRS systems containing taxpayer data, like ERCS, are required to send their system and program audit trails to the Security Audit and Analysis System (SAAS). Audit trail repositories like SAAS aid the IRS and TIGTA in detecting potential unauthorized accesses to IRS systems and data.

  2. Security specialists from Cybersecurity are responsible for performing the review of audit trails sent to SAAS. Reports from SAAS are also sent to HQ ERCS analysts for review.

  3. Refer to IRM 10.8.2, IT Security Roles and Responsibilities, for more information including actions to take for suspected security incidents.

Getting Assistance

  1. Users experiencing ERCS or SSIVL program problems or questions are to seek assistance from their local AIMS/ERCS staff. If the local staff cannot resolve the user's issue, they will make the determination if an OS GetServices ticket needs to be input. For ERCS access or ERCS program issues the ticket must be input by the AIMS/ERCS staff.

    Note:

    Links to help users find the correct local AIMS/ERCS staff can be found on the AIMS/ERCS website under The AIMS/ERCS Staff by User Location.

  2. Users experiencing ERCS or SSIVL locked or forgotten password issues should contact the Enterprise Service Desk at 1-866-743-5748, Option 2 (Information Technology Service Desk).

  3. For information on current issues impacting ERCS refer to the Troubleshooting section on the AIMS/ERCS website. For information on current changes or updates impacting AIMS and ERCS refer to the What’s New section on the AIMS/ERCS website.

  4. For information on running the ERCS programs or on error messages received running ERCS, refer to the ERCS User Handbooks in the ERCS Manuals section of the AIMS/ERCS website.

Acronyms and Definitions

Acronym Definition
AAC AIMS Assignee Code
AIMS Audit Information Management System
BOD Business Operating Division
BSA Bank Secrecy Act
CADS Corporate Authoritative Directory Service
CCP Centralized Case Processing
DFO Directors of Field Operations
EGC Employee Group Code
ERCS Examination Returns Control System
HQ Headquarters
IIC International Individual Compliance
IT Information Technology
JCR Joint Committee Review
LB&I Large Business and International
LQMS LB&I Quality Measurement System
NQRS National Quality Review Staff
NRP National Research Program
OL5081 Online 5081
PBC Primary Business Code
PSP Planning and Special Programs
QMA Quality Measures and Analysis
ROTER Record of Tax Enforcement Results
RPO Return Preparer Office
SA System Administrator
SAAS Security Audit and Analysis System
SBC Secondary Business Code
SB/SE Small Business/Self Employed
SEID Standard Employee Identifier
SETTS Summary Examination Time Transmission System
SSIVL Statistical Sampling Inventory Validation Listing
SSN Social Security Number
TE Tax Examiner
TE/GE Tax Exempt & Government Entities
TIGTA Treasury Inspector General for Tax Administration
TIN Taxpayer Identification Number
TM Territory Manager
TRM Technical Reference Manual
TS Technical Services
UNAX Unauthorized Access of Taxpayer Accounts
WO Whistleblower Office

ERCS OL5081 Applications for CCP

OL5081 ERCS application Location of User BOD of User Access needed for returns in
ERCS-TCC-LB&I-OGDEN CCP Ogden Campus SB/SE - CCP CCP in Ogden
ERCS-TCC-SBSE-CINCY CCP Cincinnati Campus SB/SE - CCP CCP in Cincinnati
ERCS-TCC-SBSE-MEMPHIS CCP Memphis Campus SB/SE - CCP CCP in Memphis

ERCS OL5081 Applications for TS

OL5081 ERCS application Location of User BOD of User Access needed for returns in
ERCS-TCC-SBSE-AREA 202-CENTRAL TS East SB/SE - TS Area 202
ERCS-TCC-SBSE-AREA 203-SOUTH ATLANTIC TS Legacy SB/SE - TS Area 203
ERCS-TCC-SBSE-AREA 204-MIDWEST TS Midstates SB/SE - TS Area 204
ERCS-TCC-SBSE-AREA 206-WESTERN TS West SB/SE - TS Area 206

ERCS OL5081 Applications for Specialty and IIC

OL5081 ERCS application Location of User BOD of User Access needed for returns in
ERCS-TCC-SBSE-AREA 212-EMPLOYMENT Any Location SB/SE - Employment Tax Area 212
ERCS-TCC-SBSE-AREA 213-ESTATE & GIFT Any Location SB/SE - Estate & Gift Area 213
ERCS-TCC-SBSE-AREA 214-EXCISE Any Location SB/SE - Excise Area 214
ERCS-TCC-SBSE-AREA 217 BSA/FRAUD Any Location SB/SE - Fraud/BSA Area 217 (Fraud or BSA)
ERCS-TCC-SBSE-AREA 218 RPO Any Location RPO Area 218 (RPO)
ERCS-TCC-LB&I 330-INTERNATIONAL Any Location (including Puerto Rico) LB&I Area 330 (IIC)

ERCS OL5081 Applications for SBSE

OL5081 ERCS application Location of User BOD of User Access needed for returns in
ERCS-TCC-SBSE-AREA 201-NORTH ATLANTIC Connecticut, Maine, Massachusetts, New Hampshire, New Jersey, New York, Rhode Island, Vermont
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 201
ERCS-TCC-SBSE-AREA 202-CENTRAL Delaware, District of Columbia, Indiana, Kentucky, Maryland, Ohio, Pennsylvania, Tennessee, Virginia, West Virginia
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 202
ERCS-TCC-SBSE-AREA 203-SOUTH ATLANTIC Florida, Georgia, North Carolina, South Carolina
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 203
ERCS-TCC-SBSE-AREA 204-MIDWEST Illinois, Iowa, Kansas, Michigan, Minnesota, Missouri, Nebraska, North Dakota, South Dakota, Wisconsin
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 204
ERCS-TCC-SBSE-AREA 205-GULF STATES Alabama, Arkansas, Louisiana, Mississippi, Oklahoma, Texas
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 205
ERCS-TCC-SBSE-AREA 206-WESTERN Alaska, California (Northern), Colorado, Idaho, Montana, Nevada, Oregon, Utah, Washington, Wyoming
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 206
ERCS-TCC-SBSE-AREA 207-SOUTHWEST Arizona, California (Southern), Hawaii, New Mexico
  • SB/SE, excluding TS

  • SB/SE Collections, LB&I and TE/GE shared administrative associates

Area 207

ERCS OL5081 Applications for LB&I

OL5081 ERCS application Location of User BOD of User Access needed for returns in
ERCS-TCC-LB&I 201-NORTH ATLANTIC Connecticut, Maine, Massachusetts, New Hampshire, New Jersey, New York, Rhode Island, Vermont
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 202-CENTRAL Delaware, District of Columbia, Indiana, Kentucky, Maryland, Ohio, Pennsylvania, Tennessee, Virginia, West Virginia
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 203-SOUTH ATLANTIC Florida, Georgia, North Carolina, South Carolina
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 204-MIDWEST Illinois, Iowa, Kansas, Michigan, Minnesota, Missouri, Nebraska, North Dakota, South Dakota, Wisconsin
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 205-GULF STATES Alabama, Arkansas, Louisiana, Mississippi, Oklahoma, Texas
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 206-WESTERN Alaska, California (Northern), Colorado, Idaho, Montana, Nevada, Oregon, Utah, Washington, Wyoming
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I
ERCS-TCC-LB&I 207-SOUTHWEST Arizona, California (Southern), Hawaii, New Mexico
  • LB&I

  • SB/SE, SB/SE Collections and TE/GE shared administrative associates

LB&I