11.4.1 Governmental Liaison Operations

Manual Transmittal

October 17, 2022

Purpose

(1) This transmits revised IRM 11.4.1, Communications and Liaison, Office of Governmental Liaison, Governmental Liaison Operations.

Material Changes

(1) Various editorial changes were made throughout the IRM. Also, cross references and hyperlinks were added, removed or revised as appropriate.

IRM Changes
IRM 11.4.1.1.4 Addition of Program Management and Review subsection.
IRM 11.4.1.1.5 Addition of Program Controls subsection.
IRM 11.4.1.1.7 Addition of Related Resources subsection.
IRM 11.4.1.3.1.1(3) Moved CSS Components to a table format. Added IRM 11.4.1 references and titles of subsections within guidance, and updated description for IAD for clarity. Removed references to GLIDes.
IRM 11.4.1.3.1.2 (1) Moved remaining paragraph describing tax gap initiatives to IRM 11.4.1.3.3(1) and removed GL Role from sentence. Deleted subsection 11.4.3.1.2.
IRM 11.4.1.3.2 Moved lists describing GL Field Chiefs and GL/HQ Chief responsibilities to a table format for easier readability. Updated (1), table, additional information for “Implement the GL program by”, eighth bullet to address the GL Field Chiefs approve GL assistance in Safeguard Reviews.
IRM 11.4.1.3.3 (1) and (2) Added guidance originally included in IRM 11.4.1.3.1.2 as first paragraph of this subsection. Subsequent paragraphs renumbered. Updated (2) to include verbiage previously included in (2)(a) of prior revision for consistency.
IRM 11.4.1.3.3(3)(f) Added Head of Agency Letter information to table format for easier readability.
IRM 11.4.1.3.3 (5)(b) Updated to include the GLDEP Modification and New Extract Request Form and added note where the form is located on SharePoint.
IRM 11.4.1.3.3 (7)(d) Removed “should be sent” from sentence.
IRM 11.4.1.3.3 (7)(h) Removed sentence - addressed in above subsection.
IRM 11.4.1.7(3) Updated paragraph by adding a table to include information for basic agreement, implementing agreement and memorandum of understanding. Added guidance in the table for the location of program specific MOU templates on the GL SharePoint.
IRM 11.4.1.8 (2) Added “pursuant to IRS 6103(d)(1).
IRM 11.4.1.10 (2) Added territories in paragraph.
IRM 11.4.1.11 Updated title of subsection, updated (2) removing link to training material for external partners located on Governmental Liaison SharePoint and updated verbiage proving guidance for locating shareable training material available. Updated paragraph to remove outdated examples (a), (b), (c)(1), (3) and (4).
IRM 11.4.1.12.1 (1) Updated alpha list to bullet list per guidance in IRM Style Guide page 7. Removed Lien Centralization - replace with ISAC Participation Agreements.
IRM 11.4.1.12.1(2)(b) and (c) Clarification of guidance for inclusion of Counsel.
IRM 11.4.1.13 Updated title to Privacy, Governmental Liaison, and Disclosure (PGLD) Project Management Initiative Template (PMIT) and updated section to include background information for the PMIT process.
IRM 11.4.1.13.1 Updated subsection title to Documenting the PMIT Process and added guidance for the development of a PMIT. Removed references/guidance to the GLIDe process.
IRM 11.4.1.13.2 Updated title to “Documenting the Project Management Initiative Template (PMIT)” and removed reference to GLIDe Part 2: Plan, which is obsolete. Added guidance for completion of PMIT.
IRM 11.4.1.13.3 Deleted subsection. GLIDe Part 3: Summary has been obsoleted and guidance included in the PMIT.
IRM 11.4.1.14 Added reminder to (1) GLs must ensure the most current MOU template is utilized an shared with the business operating divisions. Updated throughout subsection for references to the PMIT process and removed references to the GLIDe process.
IRM 11.4.1.14.1(2), (3), (4), and (5) Added table in (2) for documents required for all new BAs. Removed “at a minimum” from the guidance. Clarification of guidance for inclusion of Counsel. Moved information included in (3), (4), and (5) to table added to (2) for readability.
IRM 11.4.1.14.2(2) and (3) Moved information previously included in a list to a table for readability and per guidance in the IRM Style Guide.
IRM 11.4.1.14.2.1(3), (5), and (6) Changed bullet list to alpha list per guidance in IRM Style Guide.
IRM 11.4.1.14.2.2(4) Changed bullet list to alpha list per guidance in IRM Style Guide. And updated (i) to remove bullets and moved information to be included within the paragraph, (j) added table for updated documents and naming convention, and (m) added table for field numbers and field names.
IRM 11.4.1.14.3(1) Removed reference to Exhibit 11.4.1-2 and added a note stating general MOU templates and MOU templates by program are available on the Governmental Liaison SharePoint.
IRM 11.4.1.14.3(6) and (7) Clarification of guidance for inclusion of Counsel and a reminder added stating the business operating division is responsible for routing the GL MOU Template to their Counsel.
IRM 11.4.1.14.3.1(1) Added a note stating general MOU templates and MOU templates by program are available on the Governmental Liaison SharePoint.
IRM 11.4.1.14.3.1(2)(a) and (f) Clarification of guidance for inclusion of Counsel. A reminder added to Field GLs for contact with the Associate SB/SE Area Counsel for legal advice. Removed link in (2)(f) to Associate Area SB/SE Counsel which in included in the IRM reference.
IRM 11.4.1.14.3.2 Update to title to specific guidance is for non-templated MOU and other agreements.
IRM 11.4.1.14.3.2(3) and (4) Clarification of guidance for inclusion of Counsel.
IRM 11.4.1.14.3.3 Added a new subsection providing guidance for templated MOUs.
IRM 11.4.1.14.4(2) Update to paragraph to include Division Commissioners and Chiefs.
IRM 11.4.1.14.4(6) Updated verbiage to conform with the plain language initiative.
IRM 11.4.1.14.5(1) and (6) Updated list in (1) to a table for readability and to meet plain language initiative. Updated alpha list in (6) to bullet list per the IRM Style Guide.
IRM 11.4.1.16(3) Updated (3) to include guidance for the Project Management initiative Template (PMIT). Removed references to the GLIDe process.
IRM 11.4.1.17.1(3) Clarification of guidance for inclusion of Counsel.
IRM 11.4.1.17.1.6(1) Clarification of guidance for inclusion of Counsel.
IRM 11.4.1.18 Clarification throughout subsection for GL Counsel referrals. Removed references to the GLIDe process and added PMIT references.
IRM 11.4.1.21(1) Clarification of guidance for inclusion of Counsel.
IRM 11.4.1.22(1) and (7) Changed references to GL HQ/Policy Disaster Coordinator to GL Disaster Coordinator.
IRM 11.4.1.23(3) Update to the procedures for requesting IRS speakers requested by state departments of revenue and other federal state and local agencies.
IRM 11.4.1.23(5) and (6) Moved information previously included in lists to tables for easier readability and per the Plan Language Initiative.
Exhibit 11.4.1-2 Previous exhibit deleted and provided reference stating GL MOU templates are located on the GL SharePoint. Subsequent exhibits renumbered.
Exhibit 11.4.1- 2 Added additional acronyms to list. Exhibit 11.4.1-3 moved to Exhibit 11.4.1-2 after previous Exhibit 11.4.1-2 was deleted.
Throughout the IRM Reviewed and updated website addresses, legal references, and IRM references as necessary. Editorial changes included as applicable and plain language initiative applied throughout the IRM.
Throughout the IRM Updated to Gender-Neutral Pronouns.

Effect on Other Documents

This revision supersedes IRM 11.4.1 dated December 30, 2020.

Audience

This IRM is intended for all employees of Governmental Liaison, Disclosure, and Safeguards.

Effective Date

(10-17-2022)

Related Resources

The Disclosure and Privacy Knowledge Base is available at the following web address: https://portal.ds.irsnet.gov/sites/vl003/pages/default.aspx.

Phyllis T. Grimes
Director, Governmental Liaison, Disclosure and Safeguards

Program Scope and Objectives

  1. Purpose: This IRM subsection provides instructions concerning the Governmental Liaison (GL) program that facilitates the exchange of data and fosters partnerships with federal, state, and local governmental agencies to improve tax administration, in accordance with Policy Statement 11-98, FedState Relations. See IRM 1.2.1.11.13, Policy Statement 11-98 (Formerly P-6-14).

  2. Audience: This IRM is intended for all employees of Governmental Liaison, Disclosure and Safeguards (GLDS).

  3. Policy Owner: The GL Office, under GLDS, is responsible for oversight of the GL policy.

  4. Program Owner: The GLDS Office, under Privacy, Governmental Liaison and Disclosure (PGLD) is the program office responsible for oversight of the Service-wide Governmental Liaison policy.

Background

  1. The Governmental Liaison (GL) program facilitates the exchange of data and fosters partnerships with federal, state, and local governmental agencies to improve tax administration, in accordance with Policy Statement 11-98, FedState Relations. See IRM 1.2.1.11.13, Policy Statement 11-98 (Formerly P-6-14).

  2. GL began as a limited information exchange program in the 1920s and is now a major IRS liaison program to foster and maintain joint tax administration projects to achieve tax compliance and Service objectives via partnerships with federal, state and local governmental agencies.

  3. In 1991, the Office of FedState Relations was created in the IRS National Office. From 1994 through 1996, FedState was institutionalized in the field with the creation of FedState regional, district office and service center program managers.

  4. In July 2000, the program was expanded to include new GL positions, assigned responsibility for relationships with the 50 states, the District of Columbia (D.C.) and the U.S. Territories. Field GLs reported to Governmental Liaison and Disclosure (GLD) Area Managers and a centralized structure headquartered in Washington, D.C.

  5. In October 2005, GL became a part of GLD in the Communications, Liaison and Disclosure operating unit of the Small Business/Self-Employed (SB/SE) Division.

  6. In June 2011, GLD became a part of Privacy, Governmental Liaison and Disclosure (PGLD), a new organization under the Deputy Commissioner, Operations and Support. As part of this realignment, the management structure of GL changed, establishing the Associate Director, Governmental Liaison position, a GL Headquarters/Policy (HQ/Policy) manager position, as well as Field GL East and West manager positions, retitled as Chief, GL HQ/Policy and Chief, GL East and West, respectively. The headquarters and field management staff report directly to the Associate Director, GL.

  7. Effective December 9, 2013, GLD was combined with the Office of Safeguards to form Governmental Liaison, Disclosure, and Safeguards (GLDS), reporting to the Director, GLDS.

  8. In 2016, PGLD updated the job title for various functions to Governmental Information Specialist. In the IRM below, the Government Information Specialist in GL are referred to as Governmental Liaisons.

Authority

  1. The following items govern the authority pertaining to Governmental Liaison operations:

    • IRM 1.2.1.11.13, Policy Statement 11-98 (Formerly P-6-14)

    • IRM 11.3.32.3 , Basic Agreements

    • IRM 11.3.32.4, Implementing Agreements

    • IRM 11.3.32.6, Memorandums of Understanding

Roles and Responsibilities

  1. The Office of Governmental Liaison develops and implements cooperative partnerships between the IRS and state tax agencies, as well as other federal and local governmental agencies.

Program Management and Review

  1. Governmental Liaisons (GLs) report directly to a group manager for either Headquarter or Field assignments.

    • Headquarter Governmental Liaisons (HQ GLs) serve as a liaisons between federal agencies and IRS business operating divisions.

    • Field Governmental Liaisons (Field GLs) serve as a liaisons between state/municipality agencies and IRS business operating divisions.

Program Controls

  1. The Office of Governmental Liaison reports program updates in regular Operational Reviews with the Director of Privacy, Governmental Liaison, and Disclosure (PGLD).

  2. Governmental Liaison (GL) operates and controls access to its SharePoint for use in storing and sharing documents within the function and with IRS reviewers on an as needed basis.

Acronyms

  1. See Exhibit 11.4.1-2, Acronyms, for a list of acronyms used in this IRM and their definitions.

Related Resources

  1. IRM 11.4.1, Governmental Liaison Operations.

  2. Disclosure and Privacy Knowledge Base.

  3. IRC 6103, Confidentiality and disclosure of returns and return information.

Function of the Associate Director, Governmental Liaison

  1. The Associate Director, Governmental Liaison (GL) supports IRS compliance, enforcement, and service to taxpayers by partnering with federal, state, and local governmental agencies to improve tax administration at all levels of government.

  2. The Associate Director, GL carries out their goals by:

    • Working jointly with the business operating divisions in formulating compliance, enforcement, and customer service initiatives.

    • Partnering with federal, state, and local governmental agencies to exchange tax and other information and engage in other joint activities.

Governmental Liaison Roles and Responsibilities

  1. The mission of the Associate Director, Governmental Liaison (GL) is to establish roles and responsibilities and direct overall operations for GL HQ/Policy and Field GL staff.

Governmental Liaison Headquarters Policy

  1. Assists the business operating divisions in formulating, developing, testing, and implementing new initiatives.

  2. Provides national oversight and coordination of new initiatives, including the development of memorandums of understanding (MOUs), if applicable.

  3. Serves as the point of contact for field and headquarters business operating division staff.

  4. Develops policy and provides oversight for the IRS Governmental Liaison (GL) program and facilitates the identification and resolution of legal and disclosure issues impacting initiatives.

  5. Serves as liaison between IRS headquarters and federal, state and local governmental agencies (for non-Tax Exempt and Government Entities (TE/GE)-related activities).

  6. Measures overall program effectiveness.

  7. Serves as primary liaison with the Federation of Tax Administrators (FTA) and for the Multistate Tax Commission (MTC).

  8. Supports IRS training classes and materials that are offered for state and local governmental agency personnel.

  9. Coordinates with Safeguards and assists Safeguards, as necessary, in soliciting overdue Safeguard Security Reports (SSRs), resolving serious deficiency findings and corrective actions and delivering key messages to external agency partners.

  10. Provides information annually for the Disclosures to State Agencies Spreadsheets folder on SharePoint.

  11. Refers to and/or consults with Disclosure and Data Services, as appropriate, on requests for Federal Tax Information (FTI) from other governmental agencies or for other IRS information not available to the public.

  12. The GL will update and maintain agreements on the IRS Agreement Database (IAD).

  13. Inputs all actions taken into eCase.

Customer Service Strategy
  1. The Governmental Liaison Head Quarters Policy(GL HQ/Policy)/Customer Service Strategy (CSS) ensures effective communications with internal and external stakeholders, accomplished by the following:

    • Sharing information and facilitating the implementation of programs involving Field GL staff, other Privacy, Governmental Liaison, and Disclosure components and other business operating divisions.

    • Collaborating with Governmental Liaison, Disclosure and Safeguards (GLDS) components to identify activities and develop strategies to consolidate key messages into a unified voice, as appropriate, for diverse audiences.

  2. CSS Objectives:

    • Support PGLD strategic objectives.

    • Establish a clear strategic direction with direct links to the resources and activities of PGLD and the IRS business operating divisions.

    • Develop appropriate strategies to identify and resolve emerging issues identified in the field and in the Communications and Stakeholder Outreach Issue Management Resolution System and direct workflow to the appropriate process.

    • Identify partnering opportunities with other business operating divisions.

    • Encourage suggestions by IRS employees and external stakeholders for increased collaboration between federal, state, and local governmental agencies.

    • Increase Service-wide awareness of GL activities.

    • Deliver key messages to internal and external stakeholders so they clearly understand expectations and desired outcomes.

    • Enhance and increase accessibility to GL products and documents available to internal stakeholders using the IRS Source, GL SharePoint site, GL Virtual Library (Knowledge Base) and the IRS Agreement Database (IAD), as appropriate.

  3. CSS Components:

    CSS Component: Description:
    PGLD Project Management Initiative Template (PMIT) For additional information on the PMIT process see IRM 11.4.1.13, Privacy, Governmental Liaison, and Disclosure (PGLD) Project Management Initiative Template (PMIT).
    GL HQ/Policy Communique Template
    • The GL communique is accessible by GL employees with proper access permissions on the GL SharePoint site. The communique is used by GL HQ/Policy Analysts to solicit external partner involvement in a project through the Field GLs, as well as to share information on national GL and business operating division programs.

    • The GL communique streamlines communications with the field. It is the vehicle used to provide specific instructions to the field on any requested action or project implementation. The communique will include supporting documents, such as MOUs, templates, fact sheets, and talking points.

    • A communique generally will be created whenever information or actions need to be solicited from or communicated to the field by GL HQ/Policy.

    • The communique will be updated by GL HQ/Policy, as necessary, to ensure delivery of accurate messages to the field.
      Reminder: Ensure all stakeholders are provided an opportunity to review and provide input when working on a GLDS joint communique.

    IRS Agreement Database (IAD) IAD is an Access database that GLDS owns and uses to document inventory of data exchange agreements and memorandums of understanding. For additional information see IRM 11.4.1.16, IRS Agreements Database (IAD).
    GL SharePoint site
    • GL SharePoint is a centralized repository for agreements, instructions, templates and other necessary reference information for GL staff.

    • The GL SharePoint site contains scanned agreements and MOUs, and a variety of other useful information and resources.

    • There is a "Search" box at the top right of every SharePoint site for searching files by keyword of the file name.

Governmental Liaison Chiefs

  1. Governmental Liaison (GL) Chiefs (East and West) Responsibilities:

    Responsibilities: Additional Information:
    Report to the Associate Director, GL.  
    Manage, direct and oversee the work of the Field GLs and of the management assistant.  
    Deliver GL programs through effective use of staff and resources.  
    Refer GL program issues that require technical, procedural or policy support to the Chief, GL HQ/Policy for resolution.  
    Convey key IRS messages to senior state and local officials, either directly or through field staff.  
    Implement the GL program by:
    • Administering national policies, guidelines and initiatives.

    • Partnering and networking with business operating division management officials on local and national initiatives.

    • Partnering and networking with state and local governmental agency executives responsible for operations in the GL areas.

    • Providing area resources to support GL teams and sub-teams working on headquarters or area initiatives and projects.

    • Coordinating input and feedback on national, area, and local initiatives and projects.

    • Ensuring GLs support, to the extent necessary, activities connected with the safeguarding requirements of agencies receiving federal tax information (FTI).

    • Elevating any unresolved matters requiring policy, procedural or technical guidance, or assistance to Safeguards.

    • Approving GL assistance with Safeguard Reviews.
      NOTE: GL HQ/Policy does not provide policy, procedural or technical guidance on safeguard reporting requirements under the jurisdiction of Safeguards.

    • Representing IRS and conveying key messages to high-level senior governmental officials at meetings, conferences, forums and other venues.

    • Preparing briefings for the Associate Director, GL.

  2. Chief, GL Headquarters/Policy Responsibilities:

    Responsibilities: Additional Information:
    Report to the Associate Director, GL.  
    Manage, direct, and oversee the work of the headquarters analyst staff.  
    Deliver GL programs through effective use of staff and resources.  
    Convey key IRS messages to senior federal, state and local officials, either directly or through Field GLs.  
    Implement the GL program by:
    • Developing, communicating and clarifying national policies, guidelines and initiatives.

    • Partnering and networking with business operating division management officials at the headquarters level.

    • Partnering and networking, as necessary, with officials of other federal agencies and organizations, such as the Federation of Tax Administrators (FTA).

    • Representing GL at internal conferences and meetings.

    • Allocating headquarters resources to establish and manage national teams and sub-teams for headquarters initiatives and projects.

    • Reviewing headquarters level MOUs and other agreements, and obtaining PGLD approval signatures, as necessary, prior to signing by the appropriate IRS official.

Governmental Liaisons

  1. Governmental Liaisons (GLs) will support Service-wide initiatives to obtain data from state and federal governmental partners to enforce voluntary compliance and reduce the tax gap.

  2. GLs are the primary point of contact for managing IRS relationships with federal, state, and local governmental agencies in their assigned state(s) and/or Insular Territories for IRS policy matters not related to tax reporting, information reporting and compliance issues relative to governmental entities in their role as taxpayers or employers. The TE/GE Division has jurisdiction over governmental agencies where these issues are concerned.

  3. Field GLs implement the GL program in their assigned states. To achieve goals of national, area, and local tax compliance or service projects, they perform key activities including, but not limited to, the following:

    1. GL Agreement-Related Program activities

    2. GL Data Exchange Program (GLDEP) activities

    3. Supports Disclosure Program activities

    4. Supports Safeguards Program activities

    5. GL Miscellaneous Program activities

    6. GL welcome letter for new appointees for state revenue or workforce agencies

      Letter Type: Action:
      GL Welcome Letter GLs will send the Welcome Letter as soon as possible (within 45 days) to provide the new agency head with the GL contact information.
      Governmental Liaison, Disclosure and Safeguards (GLDS) Director Welcome Letter GL will complete Head of Agency name, address, and GL contact information, and provide it along with a State Summary to the GL Technical Advisor for routing and issuance. GLDS will return the signed letter to GL. Upon receipt, GL will send the welcome letter electronically to the agency. If a phone call is deemed warranted, the executive assistant will contact the GL for assistance.
      Departing Head of Agency Letter GL has the option to send a letter to a departing Head of Agency.

      Note:

      The above letter templates are located on the GL SharePoint under the GL Toolbox|PGLD Letterhead and Sample Letters.

  4. GL Agreement-Related Program Activities:

    1. Assist in developing the basic agreement (BA), implementing agreement (IA), or memorandum of understanding (MOU) draft, as necessary, according to approved IRM templates and coordinating with other GLDS functions and business operating divisions, as appropriate.

    2. Coordinate the signing of the BAs, IAs, MOUs and other agreements by the head of external agencies.

    3. Distribute signed original agreements and copies of such agreements to external agencies and IRS officials, as appropriate.

    4. Ensure scanning and posting of GL agreements on the GL SharePoint site and updating of the IRS Agreement Database (IAD).

    5. Implement national or area projects and initiatives.

    6. Initiate periodic reviews of IAs and MOUs in collaboration and coordination with Disclosure, Safeguards, the business operating division and the agency.

    7. Consult with GL HQ/Policy and the business operating division to ensure new initiatives and projects are covered by MOUs or are added as revisions or addenda to IAs, as necessary.

  5. Governmental Liaison Data Exchange Program (GLDEP) Activities:

    1. Manage the GLDEP locally, in accordance with IRM 11.4.2, Data Exchange Program.

    2. GL first checks with Data Services to verify if enhancement requests are feasible (i.e. cost/staffing). If Data Services concurs, the state will prepare the appropriate form (GLDEP Modification and New Extract Request Form) and GL will sign and forward to Disclosure Manager for approval. Once approved, GL forwards to Data Services. See IRM 11.3.32.9(10), Release of Tax Data in Electronic Format, for Disclosure procedures.

      Note:

      The GLDEP Modification and New Extract Request Instructions and Form are located on the SharePoint for Data Services under GLDEP.

  6. Disclosure Program Activities:

    1. Consult with Disclosure when planning or implementing new GL initiatives, especially those that involve the exchange of Federal Tax Information (FTI), Personally Identifiable Information, or other sensitive but unclassified information.

    2. Refer to Disclosure all written requests for FTI received from other governmental agencies or for other information not specifically known to be available to the public.

    3. Review the Disclosure and Privacy Knowledge Base Site, which offers information on multiple topics. If there are additional Disclosure questions contact the Disclosure Help Desk.

    4. Refer external callers requesting disclosure assistance to the appropriate Disclosure office.

  7. Safeguards Program Activities:

    1. Advise Safeguards of agencies entering BAs, IAs or MOUs and facilitate Safeguards involvement, as necessary.

    2. Invite Safeguards to initial meetings with agencies to address the safeguarding procedures and requirements outlined in Publication 1075, Tax Information Security Guidelines for Federal, State, and Local Agencies.

    3. Assist state tax/revenue agencies in meeting IRS safeguard reporting requirements by referring questions concerning proper completion of outstanding Safeguard Security Reports (SSRs) to Safeguards as they arise, soliciting overdue SSRs and Corrective Action Plans, etc.

    4. Advise agencies to send all inquiries to the Safeguards Mailbox - SafeguardReports@irs.gov

    5. Arrange and facilitate meetings with federal, state, and local governmental agency personnel at the request of Safeguards to ensure timely and accurate resolution of serious deficiencies noted in Safeguard Review Reports, etc.

    6. Participate in on-site Safeguard Reviews, as requested or approved by Safeguards and the respective GL Field Chief.

    7. Provide assistance to Safeguards to facilitate agency compliance with safeguarding requirements, as necessary, if serious issues are identified during on-site Safeguard Reviews, etc.

  8. Miscellaneous Program Activities:

    1. Conduct appropriate research to resolve issues and inquiries independently and consult with Disclosure, GL HQ/Policy, Data Services (DS), Safeguards, other PGLD functions and other IRS business operating divisions, as necessary.

    2. Assist business operating divisions with meetings, outreach efforts and initiatives involving federal, state and local governmental agencies.

    3. Provide information to stakeholders about IRS training available to state and local governmental agency personnel.

    4. Communicate with federal, state and local governmental agencies about IRS business operating division strategic objectives and communicate external agency initiatives and objectives to key internal stakeholders.

    5. Represent the IRS at meetings with federal, state and local governmental agencies, as appropriate.

    6. Prepare briefings for the GL Chief and provide input and feedback from stakeholders regarding existing and potential IRS initiatives and projects.

    7. Notify GL HQ/Policy of agency name changes and requests new agency codes, as necessary.

    8. Update state changes into the GL State Summary Spreadsheet and the IRS Agreement Database (IAD).

Governmental Liaison Time Reporting

  1. This provides policies and procedures for time and activities reporting using the time reporting system eCase. Time reporting procedures include inputting time and activity data contemporaneously using eCase and TimeXpress. The data in eCase is used by the Governmental Liaison (GL) Office to prepare reports and briefings for management and Privacy, Governmental Liaison, and Disclosure executives.

    Note:

    The primary purpose of the time reporting system is to determine the resources expended by all GL HQ/Policy and Field GL employees and to utilize the data for data-driven decision making and planning purposes.

  2. The list below provides the history of the programs used for Time Reporting:

    1. In 2008, GL began tracking time using the Electronic—Disclosure Information Management System (e-DIMS). e-DIMS was a caseload management and timekeeping system used to record specific program activities and associated staff time. e-DIMS was officially retired on 09/30/2013.

    2. In 2012, as part of Modernized Business Products and Processes Strategy, GL rolled out the AFOIA/GLADIS project. AFOIA/GLADIS focused on using technology and developing national standards to improve the quality and efficiency of GL.

    3. In 2019, GL built on this strategy using the eCase platform, replacing AFOIA/GLADIS.

  3. The following definitions will be used throughout this subsection of the IRM:

    1. eCase: A web-based application for time and activity reporting in a central location for users to input, monitor, and report on time and task inventory.

    2. eCase Training Materials: The eCase GL User Manual and related materials can be viewed on the GL SharePoint site.

    3. Field GL: Governmental Liaison employees in both GL East and GL West groups.

    4. GL HQ/Policy: Analyst employees in the GL HQ/Policy group.

    5. Program/Activity/Strategy List: Listing of all GL programs, activities, strategies and overhead time.

    6. Task: eCase is a task-based system. Tasks are created, and time categorized using the Program/Activity/Strategy List.

  4. GL employees are required to input time and actions taken using the GL eCase application.

  5. Field GLs and GL HQ/Policy employees are responsible for:

    1. Accurate daily time input by the end of each business day, but no later than the next business day. If an employee is unexpectedly absent, the employee must input time upon returning to work.

    2. The accuracy of the task information in their assigned inventory.

    3. Reporting time in 30-minute increments.

    4. Closing tasks as work is completed.

  6. Group Secretaries/Management Assistants or designated personnel are responsible for:

    1. Overseeing ongoing time entry and verification for the group, generating and printing reports.

    2. Advising the Chief of the status of the time reporting process.

    3. Maintaining historical files.

  7. Governmental Liaison Chiefs or their designees are responsible for:

    1. Overseeing time reporting.

    2. Approving and ensuring completion of a timely and accurate monthly group report.

  8. The Governmental Liaison Technical Advisor periodically publishes a listing of all available programs, activities and strategies, including definitions. The list can be viewed on the GL SharePoint site.

  9. In general, detailed out time includes all hours spent by GL employees while on detail to another business operating division.

  10. eCase Problem Reporting Procedures and Technical Support and Analysis (TSA) Help Desk:

    1. Employees should contact the GL e-case team with questions.

    2. Employees should utilize the TSA ticket for e-case application issues.

    3. The TSA Help Desk is staffed by Data Services.

Record Retention

  1. All Federal employees are responsible for making and keeping records (paper or electronic format) of their work according to the National Archives and Records Administration (NARA) approved records retention and disposition outlined in Document 12990, Records Control Schedules to prevent inadvertent/unlawful destruction of records. For additional information on Records Retention, refer to the series of IRM 1.15.1, The Records and Information Management Program.

  2. Privacy, Governmental Liaison, and Disclosure (PGLD) organization's records file plan is located on PGLD SharePoint.

IRS Roles and Responsibilities in Support of Governmental Liaison

  1. Governmental Liaison (GL) programs, initiatives, and projects often involve one or more business operating divisions to maximize cooperation and leverage resources.

  2. PGLD staff provide technical assistance and/or partner with GL, as follows:

    1. Disclosure staff provide technical assistance on existing and potential agreements involving the disclosure of Federal Tax Information (FTI) to accomplish IRS and/or federal, state and local governmental agency objectives.

    2. Data Services staff manage the critical Governmental Liaison Data Exchange Program, coordinating the routine disclosure of a vast amount of FTI to qualified federal, state, and local governmental agencies.

    3. Safeguards staff work through existing GL relationships to ensure federal, state, and local governmental agencies meet their statutory requirements to protect FTI in their possession.

    4. Other PGLD organizations (Privacy Policy and Compliance (PPC) and Identity and Records Protection (IRP) provide technical expertise to GL and ongoing support, as needed, at outreach events where IRS information may be shared with federal, state, and local governmental agency stakeholders.

  3. Business operating division staff at all levels provide information, commit resources and provide technical expertise necessary to create and implement initiatives and projects involving GL partners to achieve tax compliance, accomplish Service goals, and enhance federal tax administration. Memorandums of Understanding with SB/SE and W&I provide a framework for any assistance GLs need.

Partnering with Federal, State and Local Governmental Agencies

  1. Governmental Liaison (GL) generally manages partnering relationships between the IRS and state, local and federal governmental agencies through the FedState Program, the Municipal Agency Program (MAP) and the Federal Intergovernmental Program (FIP).

  2. The GL is the primary point of contact for partnering with these agencies for matters not related to tax reporting, information reporting and compliance issues relative to governmental entities in their role as taxpayers or employers. The TE/GE division has jurisdiction over governmental agencies where these issues are concerned. The GL:

    1. Facilitates and develops relationships, as necessary, with federal, state and local governmental agency liaisons.

    2. Coordinates meetings between IRS and federal, state, and local governmental agency staff.

    3. Facilitates initiatives and joint training opportunities between federal, state, and local governmental agencies and IRS business operating divisions.

    4. Manages the Governmental Liaison Data Exchange Program (GLDEP) locally.

    5. Acts as liaison between the IRS and federal, state, and local governmental agencies for other tax administration matters by referring technical inquiries received to the appropriate business operating division.

  3. The Field GL works closely with the Disclosure Manager (DM) in Fed/State program activities where the IRS provides Federal Tax Information (FTI) to local, state and territory revenue and workforce agencies. GL HQ/Policy will work closely with Disclosure in activities where FTI is provided to federal agencies. Disclosure coordinates, reviews and approves documents with respect to the following:

    1. Basic agreements, implementing agreements, and memorandums of understanding facilitated by GL

    2. GLDEP enrollment agreements

    3. Optional Data Element Selection (ODES) forms

    4. Exchanges of FTI

    5. Need and use determinations and justifications by state revenue and workforce agencies for access to FTI under IRC 6103(d)

    6. Disclosure Authorization list(s)

  4. MAP is one of Governmental Liaison’s partnering components which expands GL’s mission of governmental partnering and data sharing by engaging municipal agencies. Governmental Liaisons maintain a relationship with municipalities within assigned states. The GL relationship with local government is to leverage the sharing of information that will provide a mutual benefit. This relationship is secondary to that of the primary local government contact which is assigned to TE/GE and focuses on compliance. There are currently 13 cities that qualify to receive Federal Tax Information under IRC 6103(d). Some examples of the relationship GLs may have with municipalities includes:

    1. Providing information, normally in the form of email distribution, which may include filing season updates, EITC Outreach and tax law changes.

    2. Serving as an inroad to the IRS for cities to direct inquiries to the appropriate IRS business operating division.

    3. Hosting quarterly meetings for the 13 Cities to provide pertinent federal tax law updates and provide the opportunity to share best practices.

  5. The FIP provides a systematic and structured approach to expanding existing relationships and establishing new relationships with other federal agencies. The FIP program helps ensure that IRS has a centralized process to appropriately coordinate new federal initiatives and provide a Service-wide inventory of these agreements and initiatives.

    1. FIP partnerships encourage IRS and federal partners to identify, gather, and share information and data, particularly where initiatives and relationships have the potential for increased tax compliance and decreased taxpayer burden. It is critical that IRS leverages resources with other federal agencies to achieve IRS strategic goals.

    2. GL HQ/Policy is the liaison between the IRS and federal agency headquarters offices. GL HQ/Policy facilitates the development of new relationships between IRS business operating divisions and other federal agencies, and ownership of existing and new federal initiatives remains with the respective business operating division. Existing IRS/federal agency relationships are not affected by the FIP, other than by the inclusion of ongoing initiatives in the FIP inventory.

    3. Field GLs are the primary points of contact with local branch or field offices of other federal agencies.

Fed/State Partnering Examples for Improving Tax Administration

  1. The Service partners with federal, state, and local governmental agencies to improve federal and state tax administration. Following are four examples that involve the sharing of federal or state tax information.

    1. Modernized e-File (MeF) Program - Most states have agreements with the IRS for joint electronic filing of tax returns. Federal and state returns are transmitted by an electronic return originator to an IRS campus. Under the MeF program, the IRS separates the returns and sends the state return to the state tax agency for processing.

    2. State Income Tax Levy Program (SITLP) and Treasury Offset Program (TOP) - Under SITLP the IRS levies on state tax refunds when the taxpayer owes federal income tax. Under TOP, a state certifies tax debts through the Bureau of Fiscal Services, federal tax refunds are levied upon, and the proceeds are sent to, the participating state agency.

    3. State Reverse File Match Initiative (SRFMI) - Under SRFMI, states match the IRS Individual and Business Master File extracts received through the GLDEP and supply up to four extracts annually back to the IRS on individual income tax, corporate income tax, sales tax, and withholding data. State data then becomes available to IRS compliance functions as an information return on masterfile.

    4. The Questionable Employment Tax Practices (QETP) - The QETP MOU allows the IRS and State Workforce Agencies to share employment tax audit results.

Stakeholder Relationship Management Overview

  1. Stakeholder Liaison Field (SLF) manages engagement of practitioner and business stakeholders and maintains the Communications Stakeholder Liaison and Online Services (CSO) Stakeholder Relationship Management (SRM) website with information on projects and outreach activities affecting practitioners and small business stakeholders. See Exhibit 11.4.1-1, GL/CSO Stakeholders Chart, for a chart that identifies GL and CSO stakeholder relationships and possible opportunities to support each other with respect to Governmental Liaison's (GLs) external agency stakeholders.

  2. Many area offices have an SRM Local Council (SRMLC) to deliver the program in the field. The purpose of the SRMLC is to work issues involving more than two IRS functions and external stakeholders. The GL may participate in an SRMLC composed of members from the business operating divisions. Cross-functional council meetings provide an opportunity to pool the efforts and resources of the members and their respective stakeholders.

    1. Council meetings are a communication forum for marketing GL and other PGLD programs/roles and to improve the GL’s awareness of other functional activities, priorities, and projects. Meetings provide an opportunity to solicit and provide input for projects.

    2. Council meetings are an opportunity to encourage business operating divisions to partner with states or other agencies and vice versa. GL support for business operating division projects promotes relationship building. Leveraging resources is a major benefit of mutual support.

Federal, State and Local Governmental Agency Relationship Management

  1. Governmental Liaison (GL) and Disclosure (sometimes in conjunction with the TE/GE Division's Federal, State, and Local Governments (FSL/ET) unit staff) will facilitate periodic meetings between the IRS and federal, state and local governmental agencies. Topics may include the status of ongoing initiatives, new initiatives, the Safeguards Program, training and others.

  2. GL will facilitate ad hoc meetings between the IRS and federal, state, and local governmental agencies on Service-wide issues or on functional issues.

  3. GL has a general understanding of the state and local tax structure in their assigned state(s) and can provide information about state and local taxes to the business operating divisions. Governmental Liaison will share information about new IRS policies, procedures and programs with federal, state, and local governmental agency staff.

  4. GL will refer inquiries that involve external agency tax filing requirements and other tax and compliance issues related to federal, state and local governmental agencies as employers or taxpayers (versus partnering, outreach, training and other non-tax related issues) to the TE/GE FSL/ET office, which has jurisdiction over governmental agencies where these issues are concerned.

Stakeholder Relationship Management Local Council

  1. The Governmental Liaison’s (GL’s) role in the Stakeholder Relationship Management Local Counsel (SRMLC) is to:

    1. Share information about external partners that may impact the business operating divisions.

    2. Identify and evaluate business operating division projects and initiatives that may affect GL stakeholders.

    3. Identify opportunities for joint initiatives or partnering and suggest projects for SRMLC members to consider.

    4. Support SRMLC projects and obtain the support of GL stakeholders.

    5. Request support from the SRMLC members for GL projects.

    6. Market the GL program on an ongoing basis to other SRMLC members.

    7. Enhance relationships critical to the success of GL objectives.

  2. GLs will identify projects, initiatives, and concerns discussed in the SRMLC in which GL stakeholders may have an interest or be able to provide support. GLs will invite GL stakeholder participation, when possible, to improve the implementation of any SRMLC or business operating division project or initiative.

  3. GLs will use information gained from SRMLC meetings in outreach activities directed to federal, state, and local governmental agencies.

  4. The SRMLC may prove valuable in coordinating cross-functional activities.

Disclosure of Tax Information to State Tax and Other Agencies

  1. The IRS is authorized by statute, IRC 6103(d), to disclose Federal Tax Information (FTI) to states (as defined by IRC 6103(b)(5)), for tax administration purposes, upon written request. Complete guidelines for making disclosures of FTI to states for tax administration purposes are located in IRM 11.3.32, Disclosure to States for Tax Administration Purposes.

  2. In each of the states with an income tax, there are at least two state tax agencies to which the IRS may disclose FTI. Generally, one or more tax agencies in each state administer such taxes as individual income, corporate, franchise, sales, excise, and property tax. A separate tax agency in each state normally administers the unemployment tax.

  3. Each state tax agency and the IRS may enter into GL exchange agreements that provide for the mutual exchange of FTI and state tax information, as described below:

    Agreement Type: Description:
    basic agreement (BA)
    1. The BAs provide the basis for coordination of Federal and State Tax Administration.

    2. BAs are signed by the Chief Privacy Officer and the head of the state tax agency.

    3. The provisions of the BA encompass required procedures and safeguards for exchanging tax information.

    4. See the most current BA template version on the GL SharePoint site under GL Toolbox Resources.

    5. See IRM 11.3.32.3, Basic Agreements, for more specifics regarding BAs.

    implementing agreement (IA)
    1. IAs are developed by the GL, in coordination with the Disclosure Manager (DM), in accordance with the provisions of the BA.

    2. IAs supplement the BA by providing for continuous or routine exchanges of information, such as examination reports.

    3. IAs are signed by the head of the state tax agency and by the Director, Governmental Liaison, Disclosure, and Safeguards (GLDS).

    4. IA exhibits will be updated for responsible party changes, adding or removing exchanges or tolerance changes, etc.

    5. IAs will be amended as the need arises.

    6. See the most current IA template on the GL SharePoint site under GL Toolbox Resources.

    7. For additional information about IAs, see IRM 11.3.32.4, Implementing Agreements.

    memorandum of understanding (MOU)
    1. MOUs may be used for new projects/initiatives of limited duration that may warrant a pilot/test before a decision is made on full implementation.

    2. MOUs may also be preferable where the initiative involves voluminous procedures or provides for disclosures or activities under an authority other than IRC 6103(d).

    3. Program specific templates can be found on the GL SharePoint under Agreements and MOUs Templates| MOU Templates by Program. Examples of MOUs include the Transcript Delivery System (TDS), which allows approved state users to request and receive certain IRS transcript products directly on-line, as well as the Modernized Internet Employer Identification Number/One Stop application, which allows any state or local agency to participate, but does not provide for the disclosure of FTI.

    4. The GL MOU Template, available on the GL SharePoint site in the Agreements and MOUs Related Guidances| Agreements and MOUs Templates, is used to develop MOUs not included in the MOU Templates by Program.

    5. See IRM 11.4.1.14.4, Officials Authorized to Sign BAs, IAs, MOUs and Similar Agreements with Other Federal, State and Local Agencies, for more specifics on the GL MOU Template.

    6. For additional information about MOUs, see IRM 11.3.32.6, Memorandums of Understanding.

    Note:

    GL HQ/Policy Analysts will assist in determining the proper IRS official(s) to sign/execute MOUs or other agreements based on available guidance.

  4. As a condition of receipt [required by IRC 6103(p)(4)] of FTI under any new agreement or MOU or of FTI not previously received by the agency, the agency must meet IRS safeguarding requirements, including the submission or updating of a Safeguard Security Report (SSR). The GL will forward a completed SSR Notice to the agency, to remind the agency of SSR requirements when the agency wishes to participate in new MOUs and agreements involving the disclosure of FTI to agencies, as well as for the annual GLDEP enrollment.

    1. If the approved MOU or agreement (including the Governmental Liaison Data Exchange Program (GLDEP)) involves the disclosure of FTI, the agency must meet IRS safeguard requirements prior to receiving FTI under the MOU.

    2. The GL will transmit the SSR Notice to the agency along with the MOU and with the annual GLDEP enrollment solicitation.

    3. The GL will post the MOU/agreement to the GL SharePoint site, and will forward the SSR Notice for GLDEP enrollments to Data Services for retention, along with the approved enrollment forms. When the initial MOU meetings are held, the SSR Notice will be discussed with the agency.

    4. Refer to IRM 11.3.36, Safeguard Review Program, for more information about safeguarding requirements for agencies receiving FTI.

  5. Employees should follow official policy for receipt and transmission of tax information. The means for transmitting federal tax returns and return information may vary according to the sensitivity of the material involved. Refer to the Transmission subsection of IRM 10.5.1, Privacy and Information Protection, Privacy Policy. In the event alternative transmission methods are considered, please ensure they are commensurate with, and adhere to, established IRM policy and/or other approved agency guidance regarding secure transmission (i.e. Publication 1075, Tax Information Security Guidelines for Federal, State and Local Agencies).

Processing Requests for Tax Information

  1. Federal Tax Information (FTI) may be requested on a case-by-case basis using Form 8796.

    • Form 8796-A, Request for Return/Information, Federal/State Tax Exchange Program- State and Local Government Use Only. The form (or a letter containing the required information from Form 8796-A) is used by state tax agencies to request FTI.

    • Form 8796, Request for Return/Information, Federal/State Tax Exchange Program - IRS use only to request information from state tax/revenue agencies.

  2. Form 8796 and Form 8796-A must be signed by an officer or employee of the requesting agency who is authorized to request and receive tax information for the agency. Refer to IRM 11.3.32.8, Authorized Disclosures pursuant to IRS 6103(d)(1).

  3. Governmental Liaison (GL) staff who receive written requests for FTI from states via Form 8796-A or other documents will refer them to Disclosure Centralized Processing Unit for processing or assistance, unless the DM agrees, in advance, to process the request locally.

  4. GLs may assist Disclosure Managers in updating the list of state personnel authorized to make written requests for FTI or the list of IRS personnel authorized to make requests to states.

Safeguard Review Program

  1. Safeguards ensures federal, state, and local governmental agencies properly protect Federal Tax Information (FTI) in their possession to IRS standards. Safeguards staff conduct oversight reviews of agencies to verify that safeguard requirements are met.

  2. Safeguards determines the frequency of Safeguard and Need and Use Reviews, which are usually conducted every three years, but may be more or less frequent if circumstances warrant it. Safeguards conducts Safeguard Reviews of the procedures and practices of agencies that receive FTI to determine compliance with the safeguard requirements of IRC 6103(p)(4). Safeguards also verifies agencies’ actual Need and Use of the FTI by state tax agencies.

  3. See IRM 11.3.36, Safeguard Review Program, and Publication 1075, Tax Information Security Guidelines for Federal, State, and Local Agencies, for more information about the Safeguard Review Program.

Coordination of Projects and Joint Initiatives

  1. One of Governmental Liaison’s (GLs) key responsibilities is to explore opportunities to partner with other governmental entities to improve tax administration and reduce burdens on taxpayers. Many opportunities are found through joint initiatives with external agencies. Opportunities also exist to partner with federal and local agencies.

  2. GL will assist in facilitating state, local, territories and federal agency support for initiatives owned by IRS business operating divisions.

  3. GLs may identify and facilitate joint initiatives involving IRS business operating divisions and other partners. However, the day-to-day management of such initiatives is the responsibility of the business operating division.

Partnership Activities

  1. Governmental Liaisons (GLs) will adhere to Section 5.3 of the Basic Agreement with their state agencies, which states, "In addition to the exchange of tax and other information, the Agency and IRS will, to the extent feasible, extend to each other assistance in other tax administration matters. This may include such activities as taxpayer assistance, training of personnel, special statistical studies and compilations of data, development and improvement of tax administration systems and procedures, and such other activities as may improve administration."

  2. An electronic file containing training classes requested frequently by state tax agencies is available for GLs use. These classes may be shared with state tax agencies, who may print copies to train their employees. Training material available for external partners is located on the GL SharePoint under GL Programs and Initiatives in Training for External Partners.

Identifying Joint Initiatives

  1. Potential joint initiatives can be identified in a number of ways: as a result of a request from a business operating division, on one's own initiative, brainstorming with internal and external stakeholders, or replicating an approved existing initiative.

  2. To identify joint initiative opportunities, Governmental Liaison (GL) must know the program goals and strategic plans and/or priorities of internal and external stakeholders. GL should have a working knowledge of IRS goals and strategic plans along with the more specific goals and objectives of the business operating divisions. In addition, GL should be familiar with the goals and strategic plans of state and local tax and non-tax agencies, federal agencies, and other potential partners.

  3. Regular meetings and networking with internal and external stakeholders are essential. Joint meetings are a good opportunity to brainstorm new initiatives, but they should be in clear support of an IRS business priority.

  4. GLs must become familiar with joint initiatives taking place in other states and areas. Successfully implemented initiatives in one state or area may be replicated in others. A nationwide listing of GL initiatives is available on the GL SharePoint site.

Implementing Joint Initiatives

  1. The role of the Governmental Liaison (GL) is to identify, initiate and facilitate partnering opportunities with external agencies. Implementation and day-to-day management of an initiative is the responsibility of the IRS business operating division program owner. Examples of joint initiatives initiated and/or facilitated by GL but owned and managed by a business operating division include:

    • Questionable Employment Tax Practices (QETP) Memorandum of Understanding (MOU)

    • ISAC Participant Agreements

    • EITC Erroneous Refund Reduction Program (ERRP)

    • Modernized e-File

  2. In the role of facilitator of a business operating division managed initiative, GL will ensure the initiative is worked jointly with IRS partners. Among other things, GL will:

    1. Identify contacts at the state or other governmental entity.

    2. Identify and include all relevant stakeholders (such as Disclosure, Safeguards, etc.), the appropriate Counsel contacts including General Legal Services (GLS), Procedure and Administration (P&A) and Associate SB/SE Counsel as needed.

      Note:

      See IRM 11.4.1.18, Coordination of Governmental Liaison Program Legal Issues with Counsel, for additional information specific to Counsel contacts.

    3. Arrange and, where appropriate, attend or conduct meetings between the business operating division and other governmental agencies.

    4. Monitor action plans and activities.

    5. Bring together the parties responsible for drafting any required MOUs, including, Disclosure, GL Counsel (GLS and P&A) other GL staff, the appropriate business operating division and the external stakeholder(s) involved. GL will provide input and assistance to the process of drafting the MOU, as necessary.

    6. Recommend an initiative for replication nationwide, when warranted.

Privacy, Governmental Liaison, and Disclosure (PGLD) Project Management Initiative Template (PMIT)

  1. Project teams and analysts collaborate with the IRS operations, business operating divisions, and other governmental stakeholders to develop and document initiatives and related activity utilizing the Project Management Initiative Template (PMIT). The PMIT establishes a uniform process across PGLD for implementing and documenting business projects and initiatives.

  2. A PMIT will result in consistent management, reporting, transparency and collaboration on joint projects and initiatives. The benefits of a PMIT are:

    • Provide a consistent approach to project development

    • Increase awareness of initiatives

    • Establish measurables for each initiative to evaluate results/productivity

    • Simplify status reporting

    • Support the transfer of knowledge

  3. The PMIT process enables Governmental Liaison and the business operating division to work together to:

    • Implement a holistic PGLD approach to initiative development

    • Ensure executive awareness and approval of PGLD partnering, projects, and initiatives

    • Document an action plan for implementation of the project or initiative

    • Ensure proper clearances of legal, privacy, disclosure, and data protection requirements

    • Develop business measures to evaluate the end results

    • Capture best practices and summarizes the outcome of PGLD partnering, projects, and initiatives, including use of resources, business measures, and future actions and administration

  4. In partnership with IRS operations, business operating divisions, and external stakeholders, PGLD will use the PMIT process when developing initiatives involving these activities:

    • Major initiatives requiring cross functional support

    • Initiatives requiring transparency and capture of information valuable for knowledge sharing

    • Initiatives requiring development, change, and implementation of significant PGLD policy

  5. In concert with information provided in (4), GL will use the PMIT process to develop the initiatives, capture key information, and secure GLDS and business operating division approval involving these activities:

    1. New data exchanges/initiatives

    2. New data matching initiatives

    3. New uses of data currently exchanged

    4. Joint compliance activities

  6. The PMIT process does not override or replace Compliance Initiative Projects (CIPs) or other campaigns.

  7. In GL, the HQ Policy Analyst leads completion of the PMIT form, with Field GL support, as appropriate, and includes the following:

    1. Initiative goals and steps to achieve them

    2. Activities and timeliness for completion

    3. Coordination with Information Technology, Counsel, Privacy, and impacted functions within GLDS

    4. Risks and potential piloting of the initiative

    5. Initiative results

    6. Lessons learned

    7. Resources used

    8. Additional recommendations

      Note:

      Once GL and the business operating division review and complete the PMIT, GL routes it for executive approvals from both the business operating division and GLDS. If the executives do no concur with the initiative, GL documents the reason and discusses it with the business operating division.

  8. The completed PMIT form is a historical record and business case of an initiative’s development. It is a resource for development of future initiatives. GL will store all PMITs in the PGLD, Privacy Policy and Knowledge Management document repository, including those not implemented.

Documenting the PMIT Process

  1. Governmental Liaison (GL) Field or HQ/Policy Analyst completes , depending upon who initiates the process.

  2. The Header must include:

    1. Initiative title

    2. Initiative owner and point of contact

    3. GLDS champion

    4. GLDS office lead

    5. Stakeholders

  3. Complete Part 2, Initiative Information.

    Line: Description:
    Initiative description and objectives Describe how the initiative came up as an opportunity for development.
    List the goals of the initiative.
    Scope Provide PGLD’s role and involvement in this initiative.
    Major tasks/milestones/deliverables Detail the actions needed to fulfill the goals and the key deliverables.
    Expected initiative completion date Select the estimated completion date for this initiative.
    Mandates Select the primary drivers for this initiative, and then list the details such as mandate title or authority.
    Strategic Plan/Priority Supported by IRS, PGLD, GLDS, and business operating division Document the IRS, PGLD, and business operating division strategic plan/priority for this initiative supports.
    Resources needed Document the types of resources needed (i.e., early cost projections) for completion of this initiative.
    Business outcomes/measures List the potential internal and external partners involved in the initiative.
    Risk level Select the associated risk level for this initiative. Find more information related to risks in the Risk Assessment Quick Reference Guide.
      Secure the electronic signatures from business operating division and GL at the manager or higher level, agreeing to continue with the plan.
      Document the receipt of approval from GL Chief.
      Document the business operating division response.

Documenting the PMIT

  1. The HQ /Policy Analyst takes the lead on completing the Project Management Initiative Template (PMIT), with Field Governmental Liaison (GL) support and input from the stakeholder for the completion of the PMIT process, planning, and development of the initiative, identification of the initiative scope and steps to achievement.

  2. The PMIT template consists of four parts for documenting project and initiatives.

    Part Section
    Part 1: Header Information
    1. Initiative title

    2. Initiative points of contact

    3. PGLD Champion

    4. PGLD function owner and office

    5. Stakeholder types and name

    Part 2: Initiative Information
    1. Initiative description and objectives

    2. Scope

    3. Major tasks/milestones/key deliverables

    4. Estimated initiative completion date

    5. Mandate type and name

    6. Strategic plan/Priority supported

    7. Resources needed - This section documents the estimated costs of the initiative

    8. Business outcomes/measures

    9. Risk level

    10. Risk type

    11. Initiative risks/mitigation actions

    Part 3: Assessment and Approvals
    1. This section documents executive awareness of the initiative. Once complete, the analyst and stakeholder will each route the PMIT through their respective management and executives for awareness and approval, as appropriate.

    2. The senior manager and business operating division partner approve and sign. Significant initiatives require executive signatures.

    3. If PGLD executives do not concur with the initiative, the analyst documents the reason and discusses with the stakeholder.

    Part 4: Disposition
    1. Initiative approval status and date

    2. Initiative status and completion date

    3. Initiative outcome - This section documents the results of the initiative.

    4. Success measures

    5. Related initiatives

    6. Additional recommendations

    7. Supporting documents, when appropriate
      Note: The PGLD Analyst leads the preparation of the summary, with stakeholder support.

  3. All PMIT documents, including those not implemented, are stored on SharePoint. They serve as a historical record and business case of an initiative’s development and are a resource for development of future initiatives.

Procedures for Routing, Approving, Signing and Terminating Basic Agreements (BAs), Implementing Agreements (IAs), Memorandums of Understanding (MOUs), and Other Agreements

  1. Government Liaison (GL) has primary responsibility for the development and coordination of agency agreements and memorandums of understanding (MOUs).

    Reminder:

    GLs must ensure the most current MOU template is utilized and shared with the business operating divisions. Updated MOU templates are found on the Governmental Liaison SharePoint: Agreements, MOUs, and GLIDes: Agreements and MOUs Templates.

  2. An agreement or MOU is utilized for specific ongoing tax administration projects/exchanges, when the disclosure is authorized with respect to taxes imposed by a chapter listed under IRC 6103(d) or other applicable code sections.

  3. GL documents agreements and MOU development using the Project Management Initiative Template (PMIT) process, see IRM 11.4.1.13, Privacy, Governmental Liaison, and Disclosure (PGLD) Project Management Initiative Template (PMIT), for additional information. The PMIT process is not used for the BA/IA.

  4. GL maintains an official copy of all agreements on the GL SharePoint site.

  5. Agreement and MOU information is maintained on the IRS Agreement Database, see IRM 11.4.1.16, IRS Agreements Database (IAD).

  6. The Chief Privacy Officer executes BAs on behalf of the IRS. The Director, Governmental Liaison, Disclosure, and Safeguards (GLDS) executes IAs on behalf of the IRS.

  7. Agreements and MOUs are signed by an official in the operating division having jurisdiction for the project/exchange and who is authorized by Delegation Order 11-2, see IRM 1.2.2.11.2, Delegation Order 11-2 (Rev. 3), Authority to Permit Disclosure of Tax Information and to Permit Testimony or the Production of Documents.

Pre-Approval Process for BAs

  1. The pre-approval process for basic agreements (BAs) ensures all procedural, technical, legal and other issues are resolved prior to formal routing to obtain the signatures of IRS and state tax agency officials. There is no specific time period for the completion of the pre-approval process. However, Governmental Liaisons (GLs) will ensure actions are taken as expeditiously as possible to minimize delays.

  2. The GL will prepare the pre-approval package to include the following documents required for all new BAs:

    Documents: Actions:
    Drafting a new BA
    1. Use the most recent template available on SharePoint.

    2. Include copies of applicable state statutes, an agency organization chart, and other relevant documentation collected in developing the draft BA.

    Form 13839-A , Note to Reviewer (For a Signature Package), that will:
    1. Provide the justification for entering into the agreement with the state tax agency.

    2. Include the approved “Need and Use” statement/justification.

    3. Address, where warranted, IRC 6103(p)(8) considerations outlined in Disclosure IRM 11.3.32.12.1, State Law Requirements pursuant to IRC 6103(p)(8).

    4. Document coordination with Disclosure, Safeguards and GL Counsel (General Legal Services (GLS) and Procedure and Administration (P&A)).

    Safeguard Security Report (SSR) Notice A statement indicating GL issued an SSR Notice to the agency to ensure the agency was aware of requirements for safeguarding Federal Tax Information.
    To initiate the pre-approval process, the GL will prepare Form 14074, Action Routing Sheet and route the BA Pre-Review package to the following:
    1. Disclosure Manager with jurisdiction over the state tax agency.

    2. Local Counsel (in accordance with IRM 37.1.3, The Counsel Governmental Liaison Coordination Program).
      Note: Local Counsel Contact per guidance in IRM 37.1.3, is defined as the Associate SB/SE Advisory Counsel contact Field GL’s utilize. The guidance included in IRM 37.1.3 does not circumvent the business operating division’s process of contacting the business operating division Counsel for review ensuring the BA is in line with their processes and procedures.

    3. Deputy Associate Director Disclosure (East/West).

    4. GL Chief (East/West).

    5. HQ Disclosure BA Coordinator.

    Routing, reviews and changes made to the pre-approval package: All actions are completed electronically, to the extent possible.
    Once the pre-approval process is completed: The HQ Disclosure BA Coordinator will return the pre-approved package to the GL to initiate formal routing, approval and signing of the BA.

Formal Routing, Approval, and Signing of BAs
  1. Upon receipt of the pre-approved basic agreement (BA) package from HQ Disclosure, the Governmental Liaison (GL) will obtain the signature of the head of the state tax agency. The head of the state tax agency is generally the official (other than the governor or mayor) responsible under state law for the functions of the particular tax agency or department.

  2. After obtaining the signature of the head of the state tax agency on the BA, the GL will prepare the formal routing and approval package for the signature of the Chief Privacy Officer.

  3. The BA signed by the head of the state tax agency will be routed expeditiously by the GL to ensure it will be submitted within 30 days of receipt for the signature of the Chief Privacy Officer. Governmental Liaison, Disclosure, and Safeguards, (GLDS) routing procedures will be followed to secure the signature of the Chief Privacy Officer.

  4. Following the signature of the Chief Privacy Officer, the signed BA will be returned to the GL. The GL will forward the signed BA to the agency.

  5. The GL will send a copy of the signed BA to the GL SharePoint site Coordinator for posting to the SharePoint agreements folder for the state. GL will use the examples below for the file naming convention:

    • New pdf BA document example: SC### BA MMDDYYYY

    • Revised/updated pdf BA document example: SC### BA MMDDYYYY Rev MMDDYYYY

    • Archive pdf BA document example: SC### BA MMDDYYYY Superseded MMDDYYYY

  6. GL will update the IRS Agreement Database (IAD) using Form 15030, IRS Agreements Database (IAD) - Update Request Agreement/Memorandum of Understanding (MOU) Information.

  7. The BA will be effective upon execution of the signature of both parties and will remain in effect indefinitely, unless terminated, in writing, by either party. A change of incumbent in the office of either party to the agreement will have no effect on the agreement.

  8. From time to time, it may be necessary to amend specific sections of a BA by means of an addendum. Any addendum to a BA will be processed in the same manner as the original agreement was processed.

Pre-Approval Process for IAs

  1. The pre-approval process for implementing agreements (IAs) ensures all procedural, technical, legal and other issues are resolved prior to formal routing to obtain the signatures of IRS and state tax agency officials.

  2. The following steps must be followed for the pre-approval process - Phase 1:

    Steps Actions
    For the pre-approval process:
    1. Governmental Liaison (GL) will ensure the agency has a basic agreement (BA) posted on the GL SharePoint site.

    2. GL will review the current IA, if one exists.

    3. GL will prepare an initial customized draft IA and share it with the state tax agency.

  3. The following steps must be followed to finalize the draft IA - Phase 2:

    Steps Actions
    GL will liaise with the primary agency point-of-contact (POC) and IRS Disclosure Manager (DM) to complete a customized draft IA, including:
    • Exhibit A: Contacts and contacts information.

    • Exhibit B: Information to be sent to the Agency from IRS. The DM will approve the need and use of Federal Tax Information requested, including tolerances and criteria.

    • Exhibit C: Information to be sent to the IRS from the Agency.

    • Exhibit D: List of Current memorandums of Understanding and Other Agreements.

    GL will liaise with the DM and agency POC: Verify the Federal Tax Information requested in Exhibit B relates to taxes imposed by the Code chapters listed in Section 3.2 of the agency’s BA. If not, the GL will amend the BA.
    Template body changes: GL will obtain approval from GL HQ/Policy.
    Peer review:
    1. GL will send the final draft IA to the IA Team for peer review.

    2. The IA Team will peer review the draft IA for content and formatting, then return the draft IA to the GL for agency signature.

Formal Routing, Approval and Signing of IAs
  1. After obtaining the signature of the head of the state tax agency, the Governmental Liaison (GL) working with GL in HQ/Policy will prepare the formal routing and approval package for the signature of the Director, Governmental Liaison, Disclosure, and Safeguards (GLDS).

  2. GL will prepare the implementing agreement (IA) signature package to include the following documents:

    • IA signed by Head of Agency (pdf document)

    • Action Routing Sheet (ARS) and

    • Form 13839-A, Notes to Reviewer (For a signature package) requesting a signature from the GLDS Director

      Note:

      Samples of the ARS and Notes to Reviewer are posted to the GL SharePoint site.

  3. GL will initiate the IRS signature process by routing the IA signature package in the following order:

    1. Disclosure Manager with jurisdiction over the state tax agency

    2. GL Chief (East/West)

    3. GL HQ/Policy Analyst

  4. GL HQ/Policy Analyst will review the package, work with the GL to resolve any issues, sign the ARS and submit to GL’s Technical Advisor to complete the GLDS routing procedures. GLDS will utilize the GLDS SharePoint Signature Package site to review the signature package for ARS review and approvals.

  5. After the Director, GLDS signs the IA, the GL Technical Advisor will return the IA signature package to the GL HQ/Policy Analyst. The GL HQ/Policy Analyst will:

    1. Post the newly signed IA to the agency’s IA folder on SharePoint and archive any superseded IAs

    2. Eliminate all the signature information lines, and type “Document with original signatures on file” and post the IA working copy to GL SharePoint site

    3. Update the Modification Log on the GL SharePoint site

    4. Update the Disclosure Spreadsheets on SharePoint and instruct the GL to review and confirm the accuracy. Notify business operating division contacts of changes, as needed

    5. Return the signed IA to the GL

  6. Once the signed IA is received, the GL will follow the steps below:

    1. Provide the signed IA to the agency via a secure method

    2. Carefully review and verify the accuracy of the Disclosure Spreadsheets on SharePoint

    3. Issue a Safeguard Security Report (SSR) Notice if any new data streams are added to the IA. The completed SSR Notice will be posted to the agency’s IA folder on SharePoint

    4. Complete the IAD update Form 15030 to add the new IA and archive the superseded IA

  7. The IA will be effective upon execution of the signatures of both parties and will remain in effect indefinitely, unless terminated, in writing, by either party. A change of incumbent in the office of either party to the agreement will have no effect on the agreement.

  8. From time to time, it may be necessary to modify the IA Exhibits. Any modifications will follow the process in IRM 11.4.1.14.2.2, IA Exhibit Modification Process: Instructions for Retaining, Modifying and Archiving.

IA Exhibit Modification Process: Instructions for Retaining, Modifying and Archiving
  1. A new implementing agreement (IA) template was developed in 2014 and approved for implementation. The lists of contacts and exchanges were moved to exhibits allowing them to be modified without new signatures. This will allow the IA to age like the basic agreement (BA); while the IA exhibits remain current.

  2. Annually, or as needed, the IRS and Agency liaison officials will determine if changes to exhibits are needed. In 2017, Governmental Liaison (GL) Counsel provided new guidance, changing the way IAs are retained and modified. GL Counsel advised archiving the original signed IA and using an unsigned IA Working Copy that references the original signatures along with a Modification Log to track modifications. To implement GL Counsel’s guidance, a separate IA folder for each state tax agency was created on SharePoint.

  3. Instructions for Retaining, Modifying and Archiving implementing agreements were developed to assist the GL’s in perfecting modifications to the IA Exhibits. The Field GL is responsible for maintaining the IA Working Copy (word version) with the latest exhibit changes.

  4. When an exhibit modification is needed, the GL will complete the following steps:

    1. Download a copy of the latest IA Working Copy and Modification Log from the agency’s IA folder on SharePoint.

    2. To update the exhibits, place the date in a text box in the upper right-hand corner of affected pages using Arial 12 font. If modifying an exhibit page that has been previously modified, change the date in the established text box.

    3. Log changes on the IA Modification Log.

    4. Notify the Disclosure Manager of any new items added to Exhibit B.

    5. Provide a completed Safeguard Security Report (SSR) Notice to the agency and ensure a copy is posted to GL SharePoint in the state’s IA folder. See IRM 11.4.1.7 (4), Disclosure of Tax Information to State Tax and Other Agencies, for additional information.

    6. Secure email the modified IA Working Copy and IA Modification Log to the GL East or GL West group peer reviewer. After the group level peer review is completed, the group peer reviewer will send the IA Working Copy and IA Modification Log to GL HQ/Policy Analyst for a second level review.

    7. GL HQ/Policy Analyst will identify any updates to the Disclosure Spreadsheets and make the updates. The business operating divisions access the Disclosure Spreadsheets to identify the state’s request for information.

    8. Send the updated IA Exhibits to the agency for concurrence. If the agency has additional changes, make changes and submit for peer review again.

    9. After the agency concurs with the changes, convert the IA Working Copy to a pdf document and rename using the following Naming Convention: SC### IA MMDDYYYY (date of original signing) Rev MMDDYYYY (date exhibit modified).

    10. Send the following documents to GL HQ/Policy for posting in the agency’s IA folder on SharePoint.

      Updated Documents: Naming Convention:
      IA Working Copy (word document) SC### IA Working Copy
      Example: NC156 IA Working Copy
      IA Modification Log SC### IA Modification Log
      Example: NC156 IA Modification Log
      New modified pdf IA document SC### IA MMDDYYYY (date of original signing) Rev MMDDYYYY (date exhibit modified)

      Example:

      NC156 IA 09012015 Rev 10262015

    11. GL HQ/Policy Analyst will rename and archive the superseded pdf version on SharePoint. The first date is the signed date of the original IA; the second date, if applicable, is the modification date; and the last date is the superseded date. The naming convention format is: SC### IA MMDDYYYY (date of original signing) Rev MMDDYYYY (date exhibit modified) Superseded (date agreement superseded).

      Example:

      NC156 IA 09012015 Rev 10262015 Superseded 09072017

    12. Securely share a copy of the modified IA exhibits with the agency.

    13. Complete and submit a single IRS Agreements Database (IAD) - Update Request Form 15030, using the following fields:

      Field Number: Field Name:
      Field 1 Agreement ID
      Field 8 Revision Date
      Field 26 Requestors Name
      Field 27 Date Submitted

      Note:

      Update any other fields as necessary. Additional instructions are on the template.

Governmental Liaison MOU Templates

  1. The Governmental Liaison (GL) Memorandum of Understanding (MOU) Templates are available on the GL SharePoint site and will normally be used for any MOUs initiated by the Service. The template contains standardized language for disclosure, safeguards, record keeping requirements, transmittal procedures, privacy, evaluation of data exchange and evaluation of agreement, which GL must include or consider for each MOU.

    Note:

    GLs must ensure the most current MOU template is utilized and shared with the business operating divisions. Governmental Liaison SharePoint houses general MOU templates and MOU templates by program.

  2. Not all initiatives require an MOU. However, any Federal Tax Information (FTI) provided to a state tax agency must be specifically addressed in the applicable IA, and/or must be covered in an MOU or other agreement or by an ad hoc (specific) written request for the information.

  3. GL coordinates with Disclosure and the business owner to determine the need for an MOU or other option necessary to establish and implement an initiative. The IRS executes Computer Matching Agreements (CMA) with federal and state agencies as required by the Privacy Act of 1974, for data exchanges designated as "matching programs" Treasury specifies the format, See IRM 11.3, Disclosure of Official Information.

  4. An MOU is appropriate for short-term or long-term projects, for initiatives with an indefinite life, for disclosures of FTI to a state or local tax agency under a provision of the tax code other than IRC 6103(d), or for activities not involving a disclosure of FTI or other protected information. An MOU may supplement an implementing agreement (IA) when the instructions and procedures of the activity are such that they would unduly lengthen or complicate the IA. An MOU is also used as an interim documentation of the authority and provisions of the activity when piloting an initiative, or amending/renegotiating the IA to include an ongoing activity or exchange of FTI.

  5. An MOU is signed/executed by the head of the state tax agency or other appropriate representative of a non-tax agency authorized to legally bind the agency involved. The authority to sign MOUs and other agreements by IRS officials is based on Service-wide and/or business operating division delegated authority. GL HQ/Policy Analysts will assist the business operating division with determining the proper IRS officials to sign MOUs and agreements on behalf of the IRS. See IRM 11.4.1.14.4, Officials Authorized to Sign IAs, MOUs and Similar Agreements with Other Federal, State and Local Agencies.

  6. When a business operating division headquarters initiates an MOU, the GL HQ/Policy Analyst will coordinate with business operating division headquarters staff, Field GL, Disclosure, and GL Counsel (General Legal Services (GLS) and Procedure and Administration (P&A)) and ensure all items in the GL MOU template are properly addressed.

  7. GL staff will refer recommended MOU or exhibits language changes to the appropriate GL HQ/Policy Analyst for coordination with Disclosure, GL Counsel, the business operating division, etc.

    Reminder:

    The business operating division is responsible for routing the GL MOU Template to their Counsel.

    .

MOU and Other Agreement Development and Routing Process
  1. Governmental Liaison (GL) will work with IRS business operating divisions to develop the Memorandum of Understanding (MOU) and other agreement draft.

    Note:

    GLs must ensure the most current MOU template is utilized and shared with the business operating divisions. Governmental Liaison SharePoint houses general MOU templates and MOU templates by program. GL MOU templates for Federal Tax Information (FTI) and non-FTI have also been added to the Governmental Liaison SharePoint.

  2. Upon completion of the MOU or other agreement draft, GL will route the MOU or other agreement draft through the following IRS Offices for review and input;

    1. GL Counsel (General Legal Services (GLS) and Procedure and Administration (P&A)

    2. Disclosure HQ

    3. Safeguards

    4. Privacy Policy

    5. Records and Information Management

    6. Data Services

      Note:

      For State MOUs, Field GLs will contact Associate SB/SE Area Counsel for legal advice on routine matters relating to GL programs. See IRM 11.4.1.18, Coordination of Governmental Liaison Program Legal Issues with Counsel, for additional information.

      Reminder:

      Field GL contact with the Associate SB/SE Area Counsel for legal advice is specific to GL programs as per guidance in IRM 37.1.3, Counsel Governmental Liaison Coordination Program. This process is not intended to circumvent the business operating division’s process to forward the MOU to their Counsel for review and feedback.

  3. GL will revise the MOU and other agreement draft based on the feedback and input provided by the IRS Offices under section (2) and then send the MOU or other agreement draft to agency for input and revision.

  4. Upon receipt of the agency’s feedback and input on the MOU or other agreement draft, GL will work with the IRS business operating divisions to finalize the MOU or other agreement.

Non-Templated MOU and Other Agreement Final Routing, Approval, and Signature Process
  1. Upon finalizing the Memorandum of Understanding (MOU) or other agreement with the IRS business operating divisions and Agency, Governmental Liaison (GL) will initiate the final routing, approval and signature process of the MOU or other agreement.

  2. Governmental Liaison, Disclosure, and Safeguards (GLDS) will utilize the Signature Package Guidance on GLDS SharePoint to review the signature package for Action Routing Sheet (ARS) review and approvals.

  3. GL will prepare a separate ARS and route the MOU and other agreement to GL Counsel (General Legal Services (GLS) and Procedure and Administration (P&A)) for final clearance.

  4. Upon receipt of GL Counsel’s approval (GLS and P&A), GL will prepare the Note to Reviewer (NTR) and ARS to route the MOU and other agreement through Privacy Governmental Liaison, and Disclosure (PGLD) for review. If GL worked with a specialist from the PGLD functions on the MOU or other agreement, GL will include the specialist’s name on the NTR.

    Note:

    If PGLD or Counsel make substantial changes to the MOU or other agreement, GL will discuss and resolve them with the business operating division and Agency prior to signature routing.

  5. The GL Technical Advisor will load the ARS, NTR, and the MOU and other agreement documents to SharePoint and route the signature package to the GL Field Chief, GL HQ Policy Chief, and GL Associate Director (AD).

  6. Upon securing concurrence within GL, the GL Technical Advisor will route the MOU and other agreement through GLDS and PGLD via SharePoint.

  7. The routing path is: Privacy and Records Technical Advisors, GLDS Associate Directors, and GLDS Technical Advisors.

  8. If the package is routing to a business operating division after PGLD review, the GL will prepare the business operating division ARS pages to include in the PGLD package. GL will work with the IRS business operating divisions to route the MOU or other agreement for Agency and IRS signatures.

Templated MOU and Other Agreement Final Routing, Approval, and Signature Process
  1. Templated agreements use subject matter expert (i.e., Governmental Liaison, Disclosure, and Safeguards (GLDS) reviewers, General Legal Service (GLS) Counsel and Procedure and Administration (P&A) Counsel) approved standardized text. Governmental Liaison (GL) documented the approval of the template using an Action Routing Sheet (ARS) package. For the process outlined in IRM 11.4.1.14.3.2, Non-Templated MOU and Other Agreement Final Routing, Approval, and Signature Process, GL will route each state signed agreement for awareness using the ARS process to request a signature to acknowledge receipt.

  2. GL will no longer utilize the ARS process when routing templated agreements for awareness to decrease the administrative burden of signing an ARS for each state template agreement routed. This new process will only apply to agreements executed using approved templates.

  3. The new process for templated agreements:

    Process... Additional Information...
    GL will execute the agreement with external agency partner and business operating division.  
    GL Technical Advisor will send an email message to all agreement reviewers. The email will:
    • Contain a link to the executed, agreement and approved template,

    • Include voting buttons for reviewers to acknowledge the awareness of the agreement (vote: Yes),

    • Consolidate on a weekly or bi-weekly basis the emails to include MOUs executed.

    If an agreement has been altered from the pre-approved template, it will be routed through GLDS with an ARS before securing agency signatures.  

Officials Authorized to Sign BAs, IAs, MOUs and Similar Agreements with Other Federal, State and Local Agencies

  1. The basic agreement (BA) will be drafted in accordance with the procedures in Disclosure, IRM 11.3.32.3, Basic Agreements. After the agreement is drafted, it will undergo a pre-approval review to ensure all aspects of the agreement are perfected prior to presenting the document for the official signatures of the appropriate IRS and state officials.

  2. Historically, the IRS Commissioner signed BAs, but Delegation Order 1-23 (formerly D.O. 193), which is found in IRM 1.2.2.2.20, Delegation Order, 1-23 (formerly DO-193, Rev. 6), Authorization to Perform Functions of the Commissioner, authorizes Assistant Deputy Commissioners, Division Commissioners, and Chiefs. Chief Counsel concluded in GLS-112255/GLS-HQ-386-11, Authority to Execute an IRC 6103(d) Basic Agreement FedState Agreement (dated June 8, 2011), that in accordance with, the SB/SE Commissioner had functional authority over the FedState program and responsibility for protecting confidential information by external parties. Further, D.O. 1-23 authorizes division commissioners to perform work the IRS Commissioner is authorized to perform if it relates to, arises out of, or concerns activities administered by their offices.

  3. The FedState, or Governmental Liaison program, is under the jurisdiction of the Chief Privacy Officer. Therefore, the Chief Privacy Officer has functional authority to execute BAs on behalf of the IRS.

  4. As discussed in IRM 11.3.32.4, Implementing Agreements, and IRM 11.3.32.6, Memorandums of Understanding, implementing agreements (IAs) and memorandums of understanding (MOUs) may be developed to supplement BAs by providing detailed procedures and working arrangements for items to be exchanged on a continuing basis and for recurring activities, whether or not they involve disclosures of Federal Tax Information (FTI).

  5. Generally, IAs, MOUs, and similar agreements are signed by the head of the partner agency or someone that has delegated authority to legally bind the agency.

  6. GL Counsel concluded that the Director, Governmental Liaison, Disclosure, and Safeguards (GLDS) will sign all new and amended IAs. A signature at a lower level will require an official written delegation of authority. Follow GLDS routing procedures to obtain the GLDS Director's signature.

  7. The authority to sign MOUs and other agreements on behalf of the IRS is based on Service-wide Delegation Order (D.O.) No.1-23, formerly D.O. 193; by business operating division functional statements, or other official business operating division delegations of authority.

    1. D.O. 1-23 limits the authority to sign MOUs and agreements to the respective Division Commissioner(s) or Chief(s) for matters under their jurisdiction, unless the authority is further delegated through a functional statement or other source of authority. MOUs authorizing the disclosure of FTI must be signed by a delegated authority to disclose in D.O 11-2. Delegation Order 11-2 specifies the officials authorized to disclose return information under IRC 6103. MOUs involving the disclosure of FTI must be signed by a delegated official.

    2. All MOUs and similar agreements that involve the expenditure of IT resources, in addition to the resources of one or more business operating divisions, will be signed by both the Deputy Commissioner for Services and Enforcement and the Deputy Commissioner for Operations and Support.

    3. All MOUs and similar agreements that involve the use of resources of three or more IRS business operating divisions, including Criminal Investigation, but excluding IT, will be signed by the Deputy Commissioner for Services and Enforcement.

Procedures for Terminating Agreements with Other Governmental Agencies

  1. When an agency or Privacy, Governmental Liaison, and Disclosure (PGLD) office, such as Disclosure, Safeguards and Data Services, or a business operating division informs Governmental Liaison (GL) staff that an agency no longer wishes to receive Federal Tax Information (FTI) or is not receiving FTI under existing agreements, GL will:

    Steps Actions
    Confirm the statement (if received from a party other than the agency liaison).  
    Review the termination clause of each agreement to be terminated and ensure the IRS follows the proper procedure.  
    Advise the agency to notify the IRS, in writing, of the requested termination in accordance with the agreement.
    • Address the communication to the GL or the GL HQ/Policy Analyst, in the case of other federal agency agreements.

    • Include the name and a copy of the agreement(s) the agency wishes to terminate.
      Example: The basic agreement (BA), the implementing agreement (IA), memorandums of understanding (MOUs), Letters of Understanding, and any other agreements that may be in place.

    • Address each specific agreement individually if the agency requests to terminate more than one agreement.

    Advise a state tax agency that termination of the BA is not required to terminate other agreements.
    • If the agency requests termination of the BA, the notification letter should specifically include the BA.

    • Advise the agency that, if the BA is terminated, it may take some time to obtain a new agreement if the agency later decides to receive FTI.

  2. GL will inform the agency that the termination will not prevent other cooperative activities, such as taxpayer assistance, outreach, training, and other activities that improve tax administration between the IRS and the agency.

  3. If the agency does not send a written notification of request for termination within 30 days of the IRS request, as outlined above, GL will send a letter to the agency (certified return receipt requested) notifying the agency that termination of the agreement will occur in accordance with the agency’s verbal request.

  4. If a function advises GL they wish to terminate an agreement, GL will coordinate with the function in communicating with the affected state(s) the intent to terminate the agreement and when necessary draft a termination letter.

  5. Officials at the same position, or higher, with delegated authority to sign agreements on behalf of the IRS, will sign the termination letter.

  6. GL will advise the following offices upon receiving written notification of termination (or upon issuing a termination letter):

    • Safeguards via SafeguardReports@irs.gov

    • Disclosure (Field or HQ, as appropriate)

    • Data Services GLDEP Enrollment Coordinator, if the termination request involves GLDEP extracts

  7. GL will review the IA and all other agreements to determine the functional areas that may be sending information to the state agency and will complete the Terminated Agreements Checklist available on GL SharePoint and identify programs/initiatives for termination.

  8. After completing the checklist, GL staff will contact the GL HQ/Policy Analyst responsible for terminating information exchanges. The GL HQ/Policy Analyst will coordinate with other GL HQ/Policy Analysts, as applicable, to advise impacted functional areas of the termination and to discontinue disclosures of additional information under the MOU/agreement.

  9. GL will send the Safeguard Security Report (SSR) Notice Regarding Federal Tax Information (FTI) received by agencies listing the FTI being terminated to the agency. GL will advise the agency to destroy all FTI on hand using procedures in Publication 1075, Tax Information Guidelines for Federal, State and Local Agencies, and to certify, in writing, that they destroyed all information on hand. If the agency can/will not destroy the information immediately, the agency will provide the reason and projected date of destruction. The GL will request that the agency provide the certification of destruction in writing.

  10. GL will submit a request to remove terminated agreements from the IRS Agreement Database (IAD).

  11. GL will submit a request to the GL SharePoint administrator to update the document file name in the SharePoint document library to add “terminated” and the date terminated at the end of the agreement's file name.

  12. GL will document all actions taken in eCase/TRACMS.

  13. GL will review federal, state and local agreements, periodically, and delete agreements required to be terminated, in accordance with records control schedule guidelines.

IRC 6103(p)(2)(B) Authorization

  1. Under the provisions of IRC 6103(p)(2)(B), an agency that receives Federal Tax Information (FTI) from the IRS can request approval to disclose the FTI to another state, local or Federal agency also authorized to receive the same FTI on behalf of the IRS.

  2. Once the 6103(p)(2)(B) authorization letter is signed by the Director, Governmental Liaison, Disclosure, and Safeguards (GLDS), the Field Governmental Liaison (GL) will forward the agency’s request and IRS authorization letter to the GL SharePoint Administrator for posting to SharePoint.

  3. Field GL will have the GL IRS Agreement Database (IAD) Administrator add the information and link to the 6103(p)(2)(B) authorization to the IAD with the expiration date.

  4. Field GL will update the State Summary Sheet on SharePoint.

  5. Field GLs follow up on state/local agencies 6103(p)(2)(B) authorizations, and GL Policy follows up on federal 6103(p)(2)(B) authorizations. The IAD allows GL to pull a report that highlights expirations in the coming year to help GLDS develop a timeline for reaching out to agencies timely. The GL assists the agencies with any decisions or concerns to ensure agencies have sufficient time to consider renewing the exchange. GL will contact HQ Disclosure as needed. For additional information on processing a request, see IRM 11.3.32.23, Re-disclosures by State Tax Agencies pursuant to IRC 6103(p)(2)(B).

IRS Agreements Database (IAD)

  1. The IRS Agreements Database (IAD) is a centralized, comprehensive Access database which includes agreements IRS has with federal, state, and local governmental agencies as well as specific non-governmental exchange partners. Governmental Liaison (GL) uses the IAD to reference, research and analyze agreement data, generate inventory reports, and access the agreement document(s) located on GL SharePoint (SP). Prior to development of the IAD in 2015, GL had no means to view, research, or analyze summary agreement data in one location. The IAD stores data about each agreement and associated external customer. GL can access agreement and customer data in the IAD through filtered searches or configured Inventory Reports.

  2. The IAD includes summary data and links to agreements that require Privacy, Governmental Liaison, and Disclosure (PGLD) oversight for privacy, disclosure, and safeguarding such as:

    • All IRS-executed data exchange agreements with United States federal, state, territory, and local governmental agencies.

    • All IRS-executed data exchange agreements with specific non-governmental exchange partners.

  3. The IAD includes the following modules, sections and reports:

    • Memorandum of Understanding (MOU)/Other Data - the MOU module provides the HQ/Policy GL and business operating division contact information and the purpose of and link to the associated agreement/MOU.

    • Project Management Initiative Template (PMIT) – the PMIT module provides the GL and contact information; the PMIT form, and link to the PMIT documents on GL SharePoint.

    • Reimbursables – this module is utilized and maintained by Data Services Data Exchange and Quality Initiatives (DEQI) office.

    • Governmental Liaison Data Exchange Program (GLDEP) – this module is utilized and maintained by Data Services.

    • Signature Packages – this module provides data on the current signature status of agreements requiring executive approval and signature.

    • Customer Data – this module provides external customer name and contact information. It also includes the Safeguard Security Report (SSR) due date information and identifies the supporting Disclosure Area Office.

    • Inventory Reports by GL – this module provides a standardized inventory report for GLs. This report excludes terminated agreements.

    • Inventory Report by Area – this module provides a standardized inventory report by Area. This report includes terminated agreements.

Data Exchange Agreements

  1. IRS Agreements Database (IAD) is an Access database that Governmental Liaison, Disclosure, and Safeguards (GLDS) owns and uses to document inventory of data exchange agreements and memorandums of understanding. Data exchange agreements include the following:

    • Memorandum of Understanding (MOU), a formal agreement which documents an intended common line of action between two parties.

    • On-Line access agreements allow IRS employees to obtain personally identifiable information (PII) from external government agency systems (federal or state). These agreements generally involve disclosure of taxpayer identities authorized by Internal Revenue Code IRC 6103(k)(6) Investigative Disclosures and should be documented by an agreement, MOU, Interagency Agreement (IAA), or similar agreement with the government agency, and should include appropriate privacy, disclosure and security clauses and/or terms of service agreement to cover the access of sensitive but unclassified (SBU) data about individuals in the systems.

      Example:

      Some examples include: Collection’s Department of Motor Vehicle (DMV) agreements and Taxpayer Identification Number (TIN) Matching.

    • Agreements involving consent-based disclosures under IRC 6103(c) with a governmental agency.

      Note:

      Privacy, Governmental Liaison, and Disclosure (PGLD) tracks these consent-based disclosures distinctly, because the Congressional authorization for the use of return information for these federal and state programs is not explicitly authorized under IRC 6103.

  2. The IAD excludes the following data exchange agreements:

    • Interconnection Security Agreements (ISAs) cover the security protocols for data transmission and are developed and maintained by Cybersecurity.

    • Tax Treaties and Mutual Legal Assistance Treaties (MLATs) are developed and maintained by Large Business & International (LB&I).

      Note:

      Tax Treaties include sensitive information and the data exchange is outside PGLD’s jurisdiction. Refer any requests for tax treaty information from Treasury Inspector General Tax Administration (TIGTA)/Government Accounting Office (GAO) or Congressional requests to LB&I for response.

      Note:

      FATCA agreements are publicly available on IRS.gov.

    • Online Access agreements involving IRC 6103(k)(6) disclosures executed with non-governmental entities (i.e. financial institutions, universities and private sector businesses).

    • Vendor contracts for tax administration services, i.e. procurement awards, task orders, etc. These agreements are maintained by Procurement. Contracts for disclosure of return information under IRC 6103(n) for tax administration purposes with non-governmental entities are not managed by PGLD.

    • Financial Crimes Task Force (FCTC) MOU and other agreements with law enforcement agencies covering rules of engagement between the agencies and CI, and do not involve a data exchange.

    • IRC 6103(c) consent-based disclosure agreements with non-governmental entities (i.e. taxpayer requests for disclosure).

    • W&I (Return and Income Verification Services (RAIVS), Taxpayer Assistance Centers, etc.).

      Note:

      These agreements are NOT tracked in the IAD because they are housed in databases established by the owning function, which is responsible for maintaining record copies, any required reporting, and keeping them up to date. Questions concerning these agreements should be directed to the appropriate function.

IRS Agreements Database (IAD) Responsibilities

  1. Access to the IRS Agreements Database (IAD) is restricted and requires approval from Data Services, Technical Support and Analysis (TSA) office.

  2. Governmental Liaison (GL) employees have access to the IAD as part of their responsibilities working on agreements with federal, state, territory and local governmental agencies. GLs have “read” permissions to the IAD information, allowing them to view and to generate inventory reports. GLs cannot make changes to the IAD data unless granted update permissions.

  3. The GL HQ/Policy Analyst assigned to the federal, state, territory, or local governmental agency is responsible for maintaining the IAD records in the Memorandum of Understanding (MOU)/other agreement and customer database modules for their assigned agency.

    • GL supports the accuracy of the IAD data by performing reviews of monthly inventory reconciliation reports, providing results to management and annual IAD data validation reviews.

    • GL must initiate a request to have the agreement data added to the IAD when a new agreement is established.

    • GL must initiate request for IAD data updates when an agreement is revised.

    • GL must initiate requests to update the IAD information if an agreement expires or is terminated.

    • GL must review the IAD data on a continual basis to maintain the most current and accurate agreement database records.

  4. Customer data fields on the IAD include:

    • Customer ID number

    • State

    • Name of agency

    • Agency code

    • Agency type (e.g., (Department of Revenue (DOR), State Workforce Agency (SWA), State Non-Tax (SNT))

    • Agency contact name, phone number, and email address

    • GL Area (e.g., HQ, E, W)

    • GL Point of Contact (POC)

    • Disclosure Area

    • Safeguard Security Report (SSR) Due Date

  5. Agreement data fields the IAD include:

    • Agreement ID number

    • Agreement control number

    • Agreement title

    • Agreement description

    • Agreement date

    • Revision date

    • Federal tax information (FTI) (Y or N)

    • Who benefits

    • Data format

    • Frequency

    • Data Flow

    • Business operating division

    • Business function

    • Primary and alternate contacts phone number(s)

    • Agreement expiration (if there is one)

    • Agreement termination date

    • Termination reason

    • Link to the agreement/folder on GL SharePoint

  6. When agreement and customer data require updating on the IAD, the GL and HQ/Policy Analyst assigned to the agreement will complete one or both of the following forms:

    • Form 15030 - IRS Agreements Database (IAD) - Update Request Agreement/Memorandum of Understanding (MOU) Information. Use this form to update agreement data elements. GL will complete all items to add agreement data to the IAD. When updating existing agreement data, GL will complete only required items that require a change. For expired or terminated agreements, the GL will complete all items, including Items 22 and 23 to reflect termination data along with the other agreement data.

    • Form 15030-A - IRS Agreements Database (IAD) Update Request Customer and GL Point of Contact (POC) Information. Use this form to update customer data elements. GL will complete all items when adding new customer data. GL will complete all required items to make updates to existing customer data.

  7. Submit completed forms to the IAD database mailbox *GLDS: Searchable Database Updates. The mailbox administrator distributes the requests for IAD updates to IAD team members, who make change(s) to IAD data and report back to the administrator when completed. IAD team members work directly with the requesting GL when there are questions or concerns about the requested actions.

  8. Business operating division data exchange program owners should notify HQ/Policy Analyst whenever a change is needed to a data exchange agreement or associated information on the IAD so the information is accurately maintained.

  9. The GL IAD team includes GLs from HQ, Areas East and West. Team members have “read and write” permissions to input or change data in the IAD. IAD team members can add, update, or correct data identified from targeted reviews or requests for update received through the IAD mailbox. This permission level allows them to add or make changes to all data elements.

IRS Agreements Database (IAD) Validation

  1. Governmental Liaison (GL) will validate the IRS Agreements Database (IAD) data annually to ensure the information is accurate and current for every agreement following established procedures:

    • The IAD team creates Excel workbooks from the IAD Inventory reports for HQ/Policy GL, Areas East and West and attach them to the task communiques.

    • Each GL has a worksheet containing information about agreements with their assigned states or federal agencies.

    • Field GL performs the validation review on agreement data for their assigned states and HQ/Policy GL for their assigned federal agencies’ agreements.

    • GLs will review all data elements for each agreement identified on the IAD inventory report for data validation review. GLs will verify the agreements location on SharePoint and the accuracy of the information to the IAD agreements, notating any changes/corrections to data on the worksheet in red font.

    • GLs will submit the validation worksheet back to the IAD team lead to confirm completion and any corrections to the IAD.

    • IAD team members make the necessary changes. GL will complete the annual validation by the end of January each year.

  2. The business operating division Point of Contacts (POCs) will conduct an annual validation for agreements they own on the IAD to confirm the accuracy of the data elements and ensure that all appropriate agreement data is included as shown below:

    • GL will provide validation instructions and an Excel workbook with an IAD inventory worksheet to each business operating division identifying agreements assigned to the business operating division.

    • The business operating division confirms the accuracy of agreement data on the inventory worksheet or notates corrections in red font on the worksheet.

    • The business operating division POC will confirm all worksheet data is accurate, make any corrections/additions to their worksheet, and provide a copy of any agreement that needs to the added to the IAD.

    • The business operating division will send corrected worksheets and new agreements to the IAD mailbox.

    • The business operating division will complete the annual validation process by the end of March of each year.

  3. Business operating division program owners are responsible for the data exchanged under memorandums of understanding (MOUs) executed with other agencies for data related to their program responsibilities. These MOUs are usually signed by a business operating division executive. The business operating division is the owner of the MOU and responsible for all data received and used for tax administration purposes under the agreement, as well as any tax data disclosed to an agency under the MOU. Privacy, Governmental Liaison, and Disclosure (PGLD) employees do not handle tax data in the administration of these agreements. GL does not maintain file or record counts on incoming or outgoing files for business operating division data exchange agreements. GL will refer questions on the use of tax data received from state agencies to the appropriate business operating division program manager for response.

  4. GL is responsible for maintenance of the basic agreements on Coordination of Tax Administration and supporting implementing agreements with state taxing authorities. These agreements are executed under the authority of IRC 6103(d), involve Service-wide data exchange activities, by the Chief Privacy Officer or Director Governmental Liaison, Disclosure, and Safeguards and therefore PGLD is the owner of the agreement.

Security Summit and Information Sharing and Analysis Center (ISAC)

  1. In recognition of the escalating challenges facing the tax ecosystem and the need to act quickly to prepare for the next tax filing season, the IRS Commissioner called on leaders in the public and private sectors to come together and work collaboratively to protect taxpayers from Identity Theft refund fraud. On March 19, 2015, the Commissioner convened an unprecedented Security Summit meeting in Washington, D.C. with IRS officials, the Chief Executive Officers of the leading tax preparation firms, software developers, payroll and tax financial product processors, and state tax administrators, to discuss common challenges and ways to leverage our collective resources and efforts. From this initial meeting, an agreement (Security Summit Memorandum of Understanding) was developed to establish how the Security Summit will work, including six working groups. From the Security Summit, an additional need developed to share information; this spin-off became the Information Sharing and Analysis Center (ISAC).

  2. The Security Summit and ISAC programs are owned by Wage & Investment (W&I) Return Integrity and Compliance Services (RICS).

  3. Privacy, Governmental Liaison, and Disclosure (PGLD) Governmental Liaison (GL) HQ’s involvement in the Security Summit and ISAC include providing guidance for Security Summit and ISAC activities and assistance when a PGLD program is affected.

ISAC Responsibilities

  1. Privacy, Governmental Liaison, and Disclosure (PGLD) Security Summit and Information Sharing and Analysis Center (ISAC) responsibilities are handled by Governmental Information Specialists, assigned to HQ/Policy Analysts.

  2. Attend all Security Summit Working groups and ISAC calls, which includes:

    • Authentication Working Group

    • Information Sharing Working Group

    • Strategic Threat Assessment and Response (STAR) Working Group

    • Financial Services Working Group

    • Tax Professionals Working Group

    • Communications and Public Awareness Working Group

    • ISAC Pilot Project Calls

      Note:

      Participate on calls whenever a PGLD program is mentioned or discussed. Also, be aware of the discussions; there may be topics that have a PGLD perspective without the working group being aware.

  3. Review any documentation sent by a Security Summit co-lead or ISAC official. These requests will involve either a general request for PGLD and Governmental Liaison Counsel (General Legal Services and Procedure and Administration) approval or can include a specific PGLD related question. If there is a specific question, review for any PGLD issues.

Security Summit MOU Membership
  1. Security Summit Memorandum of Understanding (MOU) Maintenance requires:

    • Incorporation of the new member signature page in the Masterfile copy on SharePoint.

    • Submission of IRS Agreement Database (IAD) form to add new member contact information to the IAD.

    • Compose welcome letter for the new member, complete signature package and submit for Governmental Liaison, Disclosure, and Safeguards Director signature, and mail welcome letter along with a Masterfile copy of the Security Summit MOU to the new member.

    • Compose courtesy letter for Security Summit partners to introduce the new member, complete signature package and submit for Governmental Liaison, Disclosure, and Safeguards Director signature, and mail courtesy letter along with the new member signature page for Security Summit members to add to their Masterfile copy of the MOU.

ISAC Participation Agreement
  1. Work with Field Governmental Liaisons (GLs) and the Trusted Third Party who manages the Information Sharing and Analysis Center (ISAC), to secure Participation Agreements from state agencies.

  2. Assistance may include; provide the Participation Agreement to GLs, arrange calls to discuss the ISAC, answer inquiries, etc.

ISAC Taxpayer First Act (TFA) Implementation Support
  1. Under the Taxpayer First Act, Section 2003, Information Sharing and Analysis Center (ISAC) Industry Participants who have a signed memorandum of understanding (MOU) with IRS-Return Integrity and Compliance Services (RICS) are authorized to receive specified per IRC 6103(k)(14). Privacy, Governmental Liaison, and Disclosure (PGLD) HQ/Policy is responsible for the following actions:

    • Post signed MOU into the IRS Agreement Database (IAD).

    • Post the MOU and Safeguards Annual Security Forms (SSF) to the SharePoint repository.

    • Update the ISAC Authorized Disclosure list. PGLD will post the ISAC Authorized Disclosure List to the PGLD SharePoint.

    • Provide ISAC Authorized Disclosure List to RICS.

    • As PGLD receives notification of a participant’s status change, PGLD HQ/Policy will update the ISAC Authorized Disclosure List and forward to RICS.

    • Provide Industry participant with “Security and Safeguards Awareness Briefing” document. Briefing is sent to the Industry member ISAC POC annually.

ISAC Onboarding
  1. HQ/Policy Analyst will send a welcome letter to the new member and schedule a call with the new member to discuss onboarding.

  2. Onboarding call includes:

    • Presenting Security Summit overview, and our goals for the current filing year.

    • Discuss annual Non-Disclosure Agreement and compliance monitoring.

    • Establish a Secure Data Transfer account (if one is not already in place).

    • Explanation of the conduit process, industry leads files, and Summit Misc. files.

    • Assistance in determining which workgroup calls best fit the new member.

    • Information Sharing and Analysis Center Overview and benefits (If not already a participant).

    • Provide the selected workgroups co-leads with the new members contact information to add to their call invite list.

ISAC Monitoring
  1. Coordinate with National Public Liaison (NPL) on annual compliance monitoring to ensure members are in good standing. Crosscheck that all agency/organization representatives participating in Security Summit activities have an Non-Disclosure Agreement on file.

ISAC Pilots
  1. Work cross functionally with business owners, Governmental Liaison (GL) Counsel (General Legal Services and Procedure and Administration) and disclosure subject matters experts to determine the feasibility of proposed data sharing pilots.

  2. Facilitate internal Privacy, Governmental Liaison, and Disclosure Subject Matter Expert call regarding any obstacles in sharing the data files.

Coordination of Governmental Liaison Program Legal Issues with GL Counsel

  1. Governmental Liaisons (GLs) will ensure the appropriate GL Counsel contacts are made. The following chart provides definitions of the differing GL Counsels and their responsibilities.

    Counsel Contact Definition
    General Legal Services (GLS) GLS serves as in-house counsel to the IRS and Office of Chief Counsel and provides legal services over a broad spectrum of matters, including labor and employment, ethics, fiscal, appropriations, procurement, contracts, and technology.
    Procedure and Administration (P&A) Procedure and Administration’s primary subject matter areas include Bankruptcy, Disclosure, and Privacy Law.
    .

  2. GL will ensure GL Counsel (General Legal Services (GLS) and Procedure and Administration (P&A)) involvement in accordance with guidelines in the Project Management Initiative Template (PMIT), discussed in IRM 11.4.1.13, Privacy, Governmental Liaison, and Disclosure (PGLD) Project Management Initiative Template (PMIT), to provide appropriate oversight and review of GL initiatives in the developmental stages.

  3. GL will refer agreements to GL Counsel for review and clearance (including memorandums of understanding, Letters of Understanding, contracts, and so on) unless the document is a template previously approved by the appropriate GL Counsel.

  4. IRM 37.1.3 Governmental Liaison Counsel Contacts, instructs Field Governmental Liaisons (GLs) to contact Associate SB/SE Area Counsel for legal advice on routine matters relating to GL programs. The current list of Associate Area Counsel contacts by state can be found at https://administrative.prod.irscounsel.treas.gov/SBSE_Contacts/Pages/Government%20Liaison.aspx.

    Reminder:

    Field GL contact with the Associate SB/SE Area Counsel for legal advice is specific to GL programs. This process is not intended to circumvent the business operation division’s process to forward to their Counsel for review and feedback.

    .

Effective Use of Intranet/Internet Resources

  1. The vast resources available through the Internet provide a wealth of information that is not only available to the public, but that can be useful in resolving a variety of Governmental Liaison (GL) questions and issues.

  2. The IRS Source is essential to the GL as a primary source of information. It efficiently directs employees to content and services available on the IRS Intranet, which they need to perform their duties. Through the IRS Source, GL staff should visit:

    1. The Disclosure and Privacy Knowledge Base, which contains program information and links to key information at: https://portal.ds.irsnet.gov/sites/vl003/pages/default.aspx, and

    2. The GL Intranet site, which contains GL program information, and links to news items and other key information and procedures at: https://portal.ds.irsnet.gov/sites/vl003/lists/governmentalliaison/landingview.aspx.

  3. GL SharePoint Main Page, accessible to GL employees only, is a major resource of a variety of important information about GL programs, GL HQ/Policy Analyst assignments and Governmental Liaison, Disclosure, and Safeguards communiques, and it provides other links to key information.

Environmental Scanning

  1. Environmental Scanning is the acquisition and use of information about events, trends, and relationships in an organization’s external environment. Environmental scanning includes both reviewing information and researching information. Environmental scanning enables Governmental Liaison (GL) staff to stay informed on the program priorities, interests, and needs of external stakeholders.

  2. Environmental scanning is not limited to external stakeholders. GL staff will use available sources, including Intranet sites, regularly to stay abreast of the latest procedures and developments within Privacy Governmental Liaison, and Disclosure and other internal organizations. Excellent internal sources of information and messages to internal and external audiences are available at various sites, including:

    • Communications website at the following: https://irssource.web.irs.gov/CL/Pages/Home.aspx

    • Headline News at the following: https://irssource.web.irs.gov/Lists/General%20News/IRSHeadLines.aspx

    • Outreach Initiatives at the following: http://mysbse.web.irs.gov/opsupport/cso/stakeholderliaison/stakeholderoutreach/initiativedatabase/default.aspx

    • IRS In the News, which is linked from the News Center at the top of the IRS Source Home Page under at the following: https://irssource.web.irs.gov/Pages/News%20and%20Events.aspx

  3. Most governmental agencies and other organizations have websites, such as the following:

  4. The weekly Federation of Tax Administrators (FTA) newsletter distributed electronically contains useful information about matters of interest to the states. The FTA list-serve also contains valuable IRS information.

    Note:

    The newsletter may be forwarded to other IRS personnel if there is a business need, but the newsletter may not be sent to stakeholders outside of the IRS.

  5. Electronic newsletters or list-serves for local newspapers, state agencies, and Congressional offices are excellent no-cost alternatives to keeping current with the needs and interests of external customers.

Increasing Governmental Liaison Program Visibility

  1. It is important that the Governmental Liaison program remains visible and shows the value added to the organization, while reinforcing employee roles and responsibilities through regular postings through business operating division articles on the IRS Source, at: https://irssource.web.irs.gov/Pages/Home.aspx.

Statistical Data Requests

  1. Governmental Liaisons (GLs) may receive requests for statistical data from federal, state, or local governmental agencies. GLs will refer to the procedures in Disclosure IRM 11.3.32.19 , Special Statistical Studies, Compilations, and Other Services, to advise them to make requests to the Statistics of Income (SOI) Division pursuant to IRC 6108(b).

  2. GLs may provide further guidance and assistance to requesters by referring them to SOI tax statistics web page at: https://www.irs.gov/statistics.

  3. GLs may refer to SOI IRM 1.13.1.7, Statistical Services - Out-Service Requests, for additional information about requests for statistical data.

  4. GLs will refer unresolved inquiries to the appropriate Disclosure Office for assistance.

Resolving Requests for Information and Assistance

  1. Governmental Liaison (GL) staff may receive requests for information and assistance from external stakeholders on a variety of topics, including questions about tax law provisions, IRS administrative procedures, IRS policies, legislative matters and IRS testimony. Such requests require that GL staff either respond independently or request the assistance of the IRS business operating divisions or other organizations, such as Disclosure and Counsel (General Legal Services (GLS), Procedure and Administration (P&A) or the Associate SB/SE Counsel as per guidance for Field GLs in IRM 11.4.1.18, Coordination of Governmental Liaison Program Legal Issue with GL Counsel).

  2. Upon receiving information and assistance requests from external agencies, GL staff will conduct initial research using the many research tools available, including, but not limited to, the variety of electronic resources described in IRM 11.4.1.19, Effective Use of Intranet/Internet Resources.

  3. If GL staff is unable to resolve inquiries using the available research tools, such as for technical or complex issues, they may need to request the assistance of the appropriate business operating division. GL staff will contact local business operating division staff to try to resolve the issue or question.

  4. In the event GLs are unable to resolve information and assistance requests locally, they will request the assistance of GL HQ/Policy Analysts, as discussed in IRM 11.4.1.21.1, Wage and Investment (W&I), through IRM 11.4.1.21.4, Large Business and International (LB&I), below.

  5. GLs will direct agencies to submit inquiries related to the Safeguard Program and/or requests for assistance related to compliance with IRS safeguard requirements, including safeguard report requirements, to the Safeguards mailbox, at "SafeguardReports@irs.gov" for direct response by Safeguards. GLs will not attempt to answer questions on behalf of Safeguards, unless Safeguards provides GL information with which to respond.

  6. GL may receive requests for technical and legislative assistance, including requests for IRS testimony or written advice on tax matters, from state officials. GL staff will contact Disclosure and/or refer to Disclosure IRM 11.3.35.3, Requests Requiring Special Processing, for assistance on requests and demands for testimony or for the production of IRS documents.

Wage and Investment (W&I)

  1. Governmental Liaison (GL) Responsibilities:

    1. Conduct appropriate research using available resources to respond to the requester, whether formally or informally.

    2. Coordinate, as appropriate, local requests for assistance with local Wage and Investment (W&I) staff.

    3. Elevate issues to the GL Chief if additional support or assistance is needed to resolve issues in coordination with appropriate local management officials.

    4. Forward unresolved requests to the GL Headquarter (HQ)/Policy Analyst assigned to W&I. The GL will provide their research results to the GL HQ/Policy Analyst to expedite resolving the request for assistance.

    5. Monitor requests submitted to W&I or to GL HQ/Policy to ensure that a timely response is provided to the state, federal or local governmental agency.

  2. W&I Responsibilities:

    1. Assign a liaison from each function in each local office where a GL is located.

    2. Provide timely technical guidance to enable GL to respond to state, federal and local governmental agency inquiries and will determine local points of contact.

    3. Provide formal written responses, when required.

    4. Resolve local issues with the GL Chief, as necessary

  3. GL HQ/Policy Responsibilities:

    1. Review requests from the W&I HQ office for the assistance of local GLs to ensure that all appropriate information is included to assist GLs in responding to requests.

    2. Review requests for assistance from Field GLs and respond, if possible. Request additional information, if needed.

    3. Forward unresolved requests from Field GLs to the W&I HQ contact for assistance.

    4. Monitor and follow-up on requests submitted to W&I HQ for response or resolution and communicate responses to Field GLs.

    5. If a formal written technical response is needed, coordinate with the function to provide a response to the local GL.

Tax Exempt and Government Entities (TE/GE)

  1. Governmental Liaison (GL)Responsibilities:

    1. Obtain general information and assistance to respond to state, federal, or local governmental agency inquiries relating to Tax Exempt/Government Entity (TE/GE) forms, applications, publications, exempt organizations, government entities, employer-sponsored pension plans, political organizations, tax exempt municipal bonds, and so on, through the TE/GE Customer Account Service (CAS) toll-free telephone number (1-877-829-5500).

    2. Respond to requesters' inquiries obtained from the CAS.

    3. Forward unresolved requests for assistance to the GL Headquarter (HQ)/Policy Analyst for coordination with HQ TE/GE. The GL will provide their research results to the GL HQ/Policy Analyst to expedite resolving the request for assistance.

    4. Monitor and follow-up on requests submitted to TE/GE or to HQ/GL Policy to ensure that a timely response is provided to the state, federal or local governmental agency.

  2. TE/GE Responsibilities:

    1. Provide support through the TE/GE toll-free number to address issues related to the tax exempt community, employee pension plans, Indian tribal governments, tax exempt bonds and the employment taxes of governments as employers.

    2. Document technical, non-account related questions as electronic referrals for call-back by TE/GE CAS revenue agents.

    3. Provide call-back responses on specific form and operational questions related to employee pension plans and exempt organizations.

    4. Provide HQ support and assistance when questions or technical matters cannot be resolved through the CAS.

    5. Administer the Pension Protection Act and the IRC 6104(c) MOU to provide tax information to state attorneys general and departments of revenue, as applicable.

  3. GL HQ/Policy Responsibilities:

    1. Coordinate Field GL support for HQ TE/GE initiatives and requests involving other federal, state, or local governmental agencies.

    2. Ensure all necessary information is provided to assist the GLs in supporting TE/GE requests.

    3. Act as the first point of contact for Field GLs when assistance is needed to resolve inquiries from federal, state, or local governmental agencies on non-employment tax matters.

    4. Review requests from GLs that require the assistance of TE/GE HQ to ensure adequate information is available to facilitate HQ TE/GE responses to requests.

    5. Forward unresolved requests from Field GLs to the TE/GE HQ contact for assistance.

    6. Monitor and follow-up on requests submitted to TE/GE HQ for response or resolution and communicate responses to Field GLs.

    7. If a formal written technical response is needed, coordinate with the function to provide a response to the local GL.

Small Business/Self-Employed (SB/SE)

  1. Governmental Liaison (GL) Responsibilities:

    1. Conduct appropriate research using available resources to respond to the requestor whether formally or informally.

    2. Coordinate, as appropriate, local requests for assistance with local Small Business/Self Employed (SB/SE) staff.

    3. Elevate issues to the GL Chief if additional support or assistance is needed to resolve issues in coordination with appropriate local management officials or if local relationships with agencies do not exist.

    4. Forward unresolved requests to the GL Headquarter (HQ)/Policy Analyst assigned to SB/SE. The GL will provide their research results to the GL HQ/Policy Analyst to expedite resolving the request for assistance.

    5. Monitor and follow-up on requests submitted to SB/SE or to GL HQ/Policy to ensure that a timely response is provided to the state, federal or local governmental agency.

  2. SB/SE Responsibilities:

    1. Assign a liaison from each function in each local office where a GL is located (Collection, Examination, Specialty Programs and others).

    2. Provide timely technical guidance to enable GL to respond to state, federal and local governmental agency inquiries and determine local points of contact.

    3. Provide formal written responses when required.

    4. Resolve local issues with the GL Chief, as necessary.

  3. GL HQ/Policy Responsibilities:

    1. Review requests from the SB/SE HQ office for the assistance of local GLs to ensure all appropriate information is included to assist GLs in responding to requests.

    2. Review requests for assistance from Field GLs and respond, if possible. Request additional information, if needed.

    3. Forward unresolved requests from Field GLs to the SB/SE HQ contact for assistance.

    4. Monitor and follow-up on requests submitted to SB/SE HQ for response or resolution and communicate responses to Field GLs.

    5. If a formal written technical response is needed, coordinate with the function to provide a response to the local GL.

Large Business and International (LB&I)

  1. Governmental Liaison (GL) Responsibilities:

    1. Conduct appropriate research using available resources to respond to the requester, whether formally or informally.

    2. Coordinate, as appropriate, local requests for assistance with local Large Business and International (LB&I) staff.

    3. Elevate issues to the GL Chief if additional support or assistance is needed to resolve issues in coordination with appropriate local management officials or if local relationships with agencies do not exist.

    4. Forward unresolved requests to the GL Headquarter (HQ)/Policy Analyst assigned to LB&I. The GL will provide their research results to the GL HQ/Policy Analyst to expedite resolving the request for assistance.

    5. Monitor requests submitted to LB&I or to GL HQ/Policy to ensure that a timely response is provided to the state, federal or local governmental agency.

  2. LB&I Responsibilities:

    1. Assign a liaison from each function in each local office where a GL is located.

    2. Provide timely technical guidance to enable GL to respond to state, federal and local governmental agency inquiries and determine local points of contact.

    3. Provide formal written responses, when required.

    4. Resolve local issues with the GL Chief, as necessary.

  3. GL HQ/Policy Responsibilities:

    1. Review requests from the LB&I HQ Office for the assistance of local GLs to ensure all appropriate information is included to assist GLs in responding to requests.

    2. Review requests for assistance from Field GLs and respond, if possible. Request additional information, if needed.

    3. Forward unresolved requests from Field GLs to the LB&I HQ contact for assistance.

    4. Monitor and follow-up on requests submitted to LB&I HQ for response or resolution and communicate responses to Field GLs.

    5. If a formal written technical response is needed, coordinate with the function to provide a response to the local GL.

Disaster and Emergency Situations

  1. In a federally declared disaster and emergency situation, the Governmental Liaison (GL) will support efforts to provide assistance, reduce burden, and provide relief to the impacted taxpayers. See IRM 25.16.1, Disaster Assistance and Emergency Relief, and the Disaster Assistance web site at the following: http://mysbse.web.irs.gov/opsupport/hc/facilitiesorganizationalsupport/continuityofop/disaster/default.aspx. The GL Disaster Assistance Coordinator will direct the GL Disaster Response. There are 10 GL Regional Disaster Assistance Coordinators (RDACs) that have the major role in GL Disaster Response. Field GLs will work closely with the RDAC in coordinating the disaster response.

  2. The GL will identify state taxing authorities whose states or districts are impacted by a disaster and provide information to them as to the steps being taken to assist disaster victims with their tax affairs.

  3. RDACs will contact the Federal Emergency Management Agency (FEMA) to obtain the locations of Disaster Recovery Centers and coordinate information with the State Disaster Assistance Coordinator in Communications and Stakeholder Outreach (CSO), Field.

  4. The GL will assist CSO, as necessary, in coordinating with state departments of revenue to staff the FEMA Disaster Recovery Centers.

  5. The GL will assist, as necessary, with information dissemination.

  6. The GL will use and timely update the Crisis Communication Plan.

  7. RDACs and GLs, upon direction from the GL Disaster Coordinator, will staff FEMA Joint Field Operations (JFOs), when assigned. JFOs are generally established for large-scale disasters.

Speaker Request Procedures

  1. Speaking at meetings, conferences and other forums, and participating in seminars or meetings provide excellent opportunities for IRS representatives to share information with external governmental agency partners. The IRS strategic plan and business operating division business plans and priorities will drive decisions on whether to provide speakers to external agency requesters, in accordance with IRS Policy Statement 11-93, regarding speaking, writing engagements and contacts with outside groups. See IRM 1.2.1.11.8, Policy Statement 11-93 (Formerly P-1-181), Speaking, writing engagements and contact with outside groups are encouraged subject to limitations.

  2. State departments of revenue, other federal state and local agencies may request IRS speakers for various reasons. These requests could range from IRS procedural issues to filing season updates and tax law changes. Many of the requests will be for local purposes, such as staff meetings, CPEs and other training. For example, a state revenue agency may be involved in planning a Federation of Tax Administrators meeting or conference and may want a business operating division subject matter expert or other speaker from IRS senior management or executive staff.

  3. To help achieve the best results for external agency needs, the Governmental Liaison (GL) staff will follow the procedures below to secure a speaker upon receiving a request from an external agency (other than for IRS Commissioner or Deputy Commissioners, which are covered in (5) below.

    1. The GL will complete all items on the applicable business operating division speaker request form, available on the GL SharePoint site, and obtain the approval of the appropriate GL Chief. Incomplete request forms may be returned.

    2. After approval by the GL Chief, the GL will work with the HQ GL assigned to the local business operating division management (Territory Manager (TM) or Area Manager (AM)) to attempt to secure a speaker for the agency.

    3. For other business operating division requests, if the GL is unable to obtain a local speaker using the above resources, or if a headquarters level speaker is requested, they will forward the approved speaker request form, via email, to the GL HQ/Policy External Agency Speaker Request Coordinator (SRC) for further processing assistance. If the speaker request was denied at the local level, the GL will provide the reason for the denial.

    4. The GL HQ/Policy SRC will review speaker requests approved by the GL Chief for completeness and will attempt to secure a speaker using available business operating division resources and contacts.

    5. The GL HQ/Policy SRC will forward speaker requests for business operating divisions other than TE/GE to the appropriate functional Speaker Request Coordinator, request an estimated response date, and share the information with the GL.

    6. The GL HQ/Policy SRC will advise the GL if the request is approved and the name of the speaker, if different than the speaker requested, or will provide the reason for denial of the request, if available.

    7. The GL will follow-up with the GL HQ/Policy SRC, if necessary.

    8. The GL will provide the name of the speaker to the requesting agency.

  4. Requests Received in GL HQ/Policy:

    1. GL HQ/Policy staff who receive speaker requests for headquarters-level speakers, excluding the IRS Commissioner and Deputy Commissioners, will prepare the applicable speaker request form, as above, obtain the approval of the GL HQ/Policy Chief, and forward the request via email to the GL HQ/Policy SRC for processing.

    2. If the GL HQ/Policy SRC is unable to secure the requested speaker, they will ascertain the reason for non-approval, if available, and advise the referring analyst accordingly.

  5. GL Field and HQ/Policy staff will immediately forward speaker requests for IRS Commissioner and Deputy Commissioners by completing the appropriate Form 14148 via email to the GL HQ/Policy SRC after approval by the appropriate GL Chief or the GL HQ/Policy Chief.

    Commissioner Action
    IRS Commissioner Governmental Liaison staff will complete and forward to the GL HQ/Policy SRC the approved Form 14148-C, Commissioner Internal and External Speaker Request, to request the attendance of the Commissioner of Internal Revenue for events and speaking engagements.
    Deputy Commissioner for Services and Enforcement (DCSE) Governmental Liaison will complete and forward to the GL HQ/Policy SRC the approved Form 14148-DCSE, Deputy Commissioner for Services and Enforcement - Speaking Request Form.

  6. The GL HQ/Policy SRC will review approved requests and will obtain the further approval of the Associate Director, GL, before taking further action to process the requests. After obtaining the approval of the Associate Director, GL, the GL HQ/Policy SRC will process the requests as follows:

    Commissioner Action
    IRS Commissioner Governmental Liaison staff will complete and forward to the GL HQ/Policy SRC the approved Form 14148-C, Commissioner Internal and External Speaker Request, to request the attendance of the Commissioner of Internal Revenue for events and speaking engagements. The GL HQ/Policy SRC will review and forward the request to the IRS Commissioner's office SRC for assistance.
    Deputy Commissioner for Services and Enforcement Governmental Liaison staff will complete and forward to the GL HQ/Policy SRC the approved Form 14148-DCSE, Deputy Commissioner for Services and Enforcement - Speaking Request Form, to request the attendance of the Deputy Commissioner for Services and Enforcement for events and speaking engagements. The GL HQ/Policy SRC will review and forward the request to the DCSE SRC for assistance.
    Deputy Commissioner for Operations Support (DCOS) Governmental Liaison staff will complete and forward to the GL HQ/Policy SRC the approved Form 14148-DCOS, Deputy Commissioner for Operations Support Speaker Request, to request the attendance of the DCOS for events and speaking engagements. The GL HQ/Policy SRC will review and forward the request to the DCOS SRC for assistance.

Visits by Foreign Tax Officials

  1. The International Visitors Program (IVP) provides government officials from other countries with an opportunity to receive clear and concise briefings on the U.S. Internal Revenue Service’s programs and policies. The briefings, given by IRS experts, assist the foreign country with its organization, strategic goals and plans. Only publicly available information may be provided to foreign tax officials through the International Visitors’ Program (IVP). The IRS does NOT accept applications from non-government entities, interns, fellows, or students working on degrees or research.

  2. An IVP Application requesting a visit to the IRS must be in writing and originate from the country’s taxing authority. It must come through appropriate government channels, and all participants must be national, state or local government officials involved in taxation. They must send the written request forty-five (45) days in advance to allow time for the IRS IVP Office to schedule presentations on the topics requested, identify the IRS experts who will meet with the officials, and allow the experts sufficient time to prepare the presentations.

  3. More information on the IVP is at this website:
    https://www.irs.gov/businesses/international-businesses/internal-revenue-service-international-visitors-program-ivp and IRM 4.62.1, International Visitor’s Program (IVP) Overview.

  4. The Privacy, Governmental Liaison, and Disclosure Associate Director or Governmental Liaison may support the program as a speaker or secure a speaker from a state tax office.

  5. Direct any questions to the HQ/Policy Analyst assigned the Large Business and International IVP Program.

GL/CSO Stakeholders Chart

Communications and Stakeholder Outreach (CSO) Stakeholders Governmental Liaison (GL) Stakeholders CSO-GL Joint Potential
Practitioner associations (American Payroll Association, Tax Forums, Taxpayer Inquiry)   • GL may assist with getting state agency input, as needed, for forums, etc. CSO may get a better response from the associations if associations can get one-stop information, including from federal, state, and local governmental agencies.
Small Business Associations/ Organizations (includes industries)   • CSO works with Small Business Administration/Service Corps of Retired Executives (SBA/SCORE) and related agencies to provide outreach and information to practitioners, although SBA, as a governmental agency, is a GL stakeholder.
• GL may work with CSO and SBA on a "Government Fair," one-stop outreach with practitioners, and agencies to reach mutual taxpayer customers.
Individual practitioners    
Universities    
Banking institutions and credit unions    
  All Federal agencies (SBA/SCORE, Federal Emergency Management Agency (FEMA), Social Security Administration (SSA), Department of Homeland Security) •Communications and Stakeholder Outreach is the primary IRS contact for disaster assistance. GL contacts FEMA to coordinate between IRS and FEMA. CSO ultimately provides the field support role with FEMA and taxpayers.
• CSO has an ongoing relationship with SBA to leverage resources for outreach to practitioner and small business organizations.
• CSO writes the IRS portion of the SSA Reporter. GLs receive this document so they will be aware of issues that might affect their state stakeholder and partner organizations.

Note:

GL is the local contact for any federal, state, or local agency, to initiate any project or outreach that involves IRS and the agency.

  State agencies (State Department of Revenue, State Workforce Agencies and State Agencies)  
  Local Government  
  Federation of Tax Administrators  
CSO    

Acronyms

Acronym Definition
AFOIA Automated Freedom of Information Act
BA Basic Agreement
CAS Customer Account Service (TE/GE)
CSO Communications and Stakeholder Outreach
CSS Customer Service Strategy
DCSE Deputy Commissioner for Services and Enforcement
DCOS Deputy Commissioner for Operations Support
DM Disclosure Manager
DOR Department of Revenue
DS Data Services
ERRP Erroneous Refund Reduction Program
FEMA Federal Emergency Management Agency
FIP Federal Intergovernmental Program
FSLG Federal, state and local governments
FTA Federation of Tax Administrators
FTI Federal Tax Information
GL Governmental Liaison
GLADIS Governmental Liaison and Data Services Information System
GLDEP Governmental Liaison Data Exchange Program
GLDS Governmental Liaison, Disclosure and Safeguards
GLS General Legal Services Counsel
IA Implementing Agreement
IAD IRS Agreement Database
IRP Identity and Records Protection
IVP International Visitors Program
IT Information Technology
LB&I Large Business and International
MAP Municipal Agency Program
MeF Modernized eFile
MOU Memorandum of Understanding
MTC Multistate Tax Commission
P&A Procedure and Administration Counsel
PGLD Privacy, Governmental Liaison and Disclosure
PMIT Project Management Initiative Template
POC Point of Contact
PPC Privacy Policy and Compliance
QETP Questionable Employment Tax Practices
RDAC Regional Disaster Assistance Coordinator
RICS Return Integrity and Compliance Services
SB/SE Small Business/Self Employed
SITLP State Income Tax Levy Program
SNT State Non-Tax
SOI Statistics of Income
SRFMI State Reversal File Match Initiative
SRM Stakeholder Relationship Management
SRMLC Stakeholder Relationship Management Local Council
SSR Safeguard Security Report
SWA State Workforce Agency
TDS Transcript Delivery System
TE/GE Tax Exempt/Government Entities
TOP Treasury Offset Program
W&I Wage and Investment