11.4.1  Governmental Liaison Operations

Manual Transmittal

May 17, 2011

Purpose

(1) This transmits a revision to IRM 11.4.1, Governmental Liaison Operations.

Material Changes

(1) Editorial changes were made throughout to update IRM/statute/organizational references and web sites to make the text easier to follow.

(2) IRM 11.4.1.2, Function of the Chief, revised to remove reference to properly protecting confidential tax records and other sensitive information addressing the public's right to access.

(3) IRM 11.4.1.3.1, Headquarters Governmental Liaison Office, updated to reflect oversight of development and implementation of new initiatives and Memorandums of Understanding.

(4) IRM 11.4.1.3.1.1, Customer Service Strategy, objectives updated to reflect communiqué procedures and the use of SharePoint as the primary repository of GL agreements and Memorandums of Understanding.

(5) IRM 11.4.1.3.1.1(3)(e), Customer Service Strategy, deleted reference to GLD SharePoint User Guide.

(6) IRM 11.4.1.3.1.2, Tax Gap Initiatives, updated web addresses and deleted reference GL tax gap and other analyst staff.

(7) IRM 11.4.1.3.2(2), Governmental Liaison and Disclosure Area Managers, revised and expanded list of responsibilities, including clarifying the role of Area Managers in reviewing and approving new or signing updated or amended Implementing Agreements and Memorandums of Understanding that do not involve the use of additional resources or change the number of ODs/FDs providing resources.

(8) IRM 11.4.1.3.3(3), Governmental Liaisons, expanded roles and responsibilities of Governmental Liaisons.

(9) IRM 11.4.1.3.3(3), Governmental Liaisons, further clarified Governmental Liaison and Local Taxpayer Advocate roles with respect to the Congressional Affairs Program.

(10) IRM 11.4.1.3.3(4), Governmental Liaisons, web site references updated.

(11) IRM 11.4.1.3.3(5), Governmental Liaisons, rewrote section.

(12) IRM 11.4.1.4 (1), IRS Roles and Responsibilities in Support of Governmental Liaison, updated Congressional Affairs Program web site and provided a web link where SB/SE and W & I Memorandums of Understanding may be viewed.

(13) IRM 11.4.1.5, Partnering with Federal, State, and Local Government Agencies, updated and revised to replace references and information about the FedFed Program with Federal Intergovernmental Partnering Program references and information.

(14) IRM 11.4.1. 5, Partnering with Federal, State, and Local Government Agencies, updated to include Disclosure Manager responsibility for reviewing and approving Need and Use determinations and justifications made by state agencies for access to federal tax information under IRC §6103(d).

(15) IRM 11.4.1.5.1, Partnering Examples for Improving Tax Administration, replaced joint audit discussion with State Reverse File Match Initiative program summary.

(16) IRM 11.4.1.6, Stakeholder Relationship Management Overview, revised title and content and renumbered to reflect Governmental Liaison's support of establishing and maintaining relationships with other Operating Divisions/Functional Divisions.

(17) IRM 11.4.1.7(3), Disclosure of Tax Information to State Tax and Other Agencies, revised to provide more information to explain and distinguish between Basic Agreements, Implementing Agreements, and Memorandums of Understanding and to highlight limited Governmental Liaison and Disclosure Area Manager authority to sign amended/updated Implementing Agreements and Memorandums of Understanding that do not involve additional resources or change other Operating Division/Functional Division involvement.

(18) IRM 11.4.1.7(3), Disclosure of Tax Information to State Tax and Other Agencies, added text regarding the use of Memorandums of Understanding in lieu of Implementing Agreements under certain circumstances and indicating the Headquarters Governmental Liaison analyst will be a resource to assist in determining the proper officials to sign Memorandums of Understanding and other agreements. Also deleted incorrect references to FISMA, NIST, and ISAs with respect to state agencies.

(19) IRM 11.4.1.7(4), Disclosure of Tax Information to State Tax and Other Agencies, revised text regarding requirements for Safeguard Procedures Reports.

(20) IRM 11.4.1.9, Safeguard Review Program, renamed from State Agency Reviews and substantially revised to update Governmental Liaison involvement and Office of Safeguards liaison roles and responsibilities.

(21) IRM 11.4.1.9(3), Safeguard Review Program, revised to discuss the Governmental Liaison's relationship management role when deficiencies are identified in "need and use" reviews.

(22) IRM 11.4.1.11(2)(c), Partnership Activities and Examples, updated training classes/list of materials, and web sites.

(23) IRM 11.4.1.12, Joint Initiatives, deleted section and renumbered remaining sections.

(24) IRM 11.4.1.13, Business Template for Joint Initiatives, deleted IRM reference and list of planned items to be included.

(25) IRM 11.4.1.13.1, revised section title to Completing the GL Business Template and GL MOU Template.

(26) IRM 11.4.1.13.1, Completing the GL Business Template and MOU Template, revised to provide additional information concerning the GL MOU Template, such as to clarify when an Memorandum of Understanding may be appropriate and to clarify guidelines for determining which IRS and external agency officials are authorized to sign Memorandums of Understanding and agreements.

(27) IRM 11.4.1.13.2(2), Approval Process for Business Template and Memorandums of Understanding, rewritten.

(28) IRM 11.4.1.14, Operating or Functional Division Initiated MOUs, updated to revise web locations for Headquarters Governmental Liaison staff program assignments.

(29) IRM 11.4.1.15, Governmental Liaison Program Legal Issues and Counsel Training, through IRM 11.4.1.18, Coordination of HQ Requests for Legal Advice with Counsel, rewritten.

(30) IRM 11.4.1.19, Effective Use of Internet/Intranet Resources, updated web site addresses.

(31) IRM 11.4.1.19.1, Environmental Scanning, updated SB/SE Communications web sites, deleted paragraph (1), and added note to paragraph (5) on sending portions of newsletters internally but not to external stakeholders.

(32) IRM 11.4.1.20, Requesting Statistical Data, renamed to “Statistical Data Requests,” and revised instructions for responding to requests.

(33) IRM 11.4.1.20.1, Statistics of Income Division, and IRM 11.4.1.20.2, Midwest Automated Compliance System, removed and subsequent sections renumbered.

(34) IRM 11.4.1.21, Internal and External Requests for Technical Advice or Assistance, revised to clarify that written inquiries may require a written response from the appropriate Operating Division/Functional Division, to provide instructions for agencies to direct inquiries to the Office of Safeguards electronic mailbox, to add a SharePoint link to Headquarters Governmental Liaison staff assignments, to discuss processing requests for technical or legislative assistance, and to delete an outdated link to reference documents.

(35) IRM 11.4.1.21.1(1), Wage and Investment, revised to provide additional instructions for processing inquiries and to update the web link to the Wage and Investment/Legislative Affairs Memorandum of Understanding.

(36) IRM 11.4.1.21.1(2), Wage and Investment , responsibilities renumbered to improve organization of the section.

(37) IRM 11.4.1.21.2, Tax Exempt and Government Entities, revised procedures and added reference to the Pension Protection Act.

(38) IRM 11.4.1.21.3, Small Business/Self-Employed Division (SB/SE), updated Legislative Affairs web address with posting location of SB/SE Memorandums of Understanding, deleted Headquarters Governmental Liaison program assignments link, and revised section for more clarity.

(39) IRM 11.4.1.21.4, Large Business and International (LB&I), changed name of section and references throughout from Large and Mid-Size Business (LMSB) to Large Business and International (LB&I).

(40) IRM 11.4.1.22, Disaster and Emergency Situations, updated the roles and responsibilities of the Governmental Liaison Regional FEMA Coordinators in coordinating disaster responses.

(41) IRM 11.4.1.22(1), Disaster and Emergency Situations, changed the term "Presidentially declared" to read "Federally declared " disasters for consistency with IRM 25.16.1, Disaster Assistance and Emergency Relief, and made updates reflecting changes to IRC §7508 A.

(42) IRM 11.4.1.23, Requests for Speakers Procedures, rewritten to clarify procedures for processing local requests received by Headquarters Governmental Liaison analysts and to clarify the role of the Headquarters Governmental Liaison Speaker Request Coordinator.

(43) IRM 11.4.1.24, Visits by Foreign Tax Officials, updated telephone contact numbers for the manager and other contacts of the IRS International Visitors Program.

(44) IRM 11.4.1.24.1, Receipt of Gifts and/or Meals from Foreign Officials, and IRM 11.4.1.25, Employee Suggestion Program, removed.

(45) Exhibit 11.4.1-1, HQ GL Communiqué, revised to include new format of the template.

(46) Exhibit 11.4.1-3, GL Shared Drive Instructions, deleted and subsequent exhibits renumbered.

(47) Exhibit 11.4.1-6, GL MOU Template, renumbered to Exhibit 11.4.1-5 and revised based on Interim Guidance Memorandum SBSE-11-0908-055, issued on September 30, 2008.

(48) Exhibit 11.4.1-7, SL/GL Speaker Request Engagement Form, renumbered to Exhibit 11.4.1-6 and revised to include the current Speaker Request Engagement Form.

(49) Exhibit 11.4.1-7, Commissioner Speaker Request Template, added.

(50) Exhibit 11.4.1-8, Instructions for Completing the Speaker Request Form, deleted.

(51) Exhibit 11.4.1-9, Safeguard Procedures Report Certification, form added.

(52) Exhibit 11.4.1-10, Receipt of Gift(s) from Foreign Official(s), and Exhibit 11.4.1-11, Employee Suggestion Program Suggestor's Checklist, deleted.

(53) Exhibit 11.4.1-12, Glossary of Governmental Liaison Terms, renumbered as Exhibit 11.4.1-10.

Effect on Other Documents

This material supersedes 11.4.1, Office of Governmental Liaison - Governmental Liaison Operations dated July 8, 2008. Interim Guidance Memorandum SBSE-11-0908-055, GL MOU Template, has been incorporated into this IRM.

Audience

This IRM is intended for employees of the Director, Governmental Liaison and Disclosure.

Effective Date

(05-17-2011)

Related Resources

The Governmental Liaison and Disclosure intranet home page can be found at the following web address: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/default.aspx.

Rob Wilkerson


Director, Communications, Liaison and Disclosure

11.4.1.1  (05-17-2011)
History of Governmental Liaison

  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.

  2. The Chief, Governmental Liaison, formerly named the Office of FedState Relations, began as a limited information exchange program in the 1920s and has become a major 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 with field GLs covering the various states reporting to Governmental Liaison and Disclosure (GLD) Area Managers (AMs) and a centralized structure headquartered in Washington, D.C. At the same time, the Congressional Affairs Program (CAP) was added to the duties of the field GLs.

  5. In October 2005, GL became a part of GLD in the Communications, Liaison and Disclosure (CLD) operating unit of the Small Business/Self-Employed (SB/SE) Division. The GL program supports all IRS operating divisions/functional divisions (ODs/FDs) to achieve IRS goals. GL has headquarters staff with field GL support under the GLD AMs.

11.4.1.2  (05-17-2011)
Function of the Chief, GL

  1. The Chief, 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 Chief, GL carries out his/her goals by:

    1. Working jointly with the ODs/FDs in formulating compliance, enforcement, and customer service initiatives.

    2. Working with Legislative Affairs (LA) and the Taxpayer Advocate Service (TAS) to deliver an effective CAP.

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

11.4.1.3  (05-17-2011)
Governmental Liaison Roles and Responsibilities

  1. To achieve the mission of the Chief, GL, roles and responsibilities are established for headquarters GL and field GL staff.

11.4.1.3.1  (05-17-2011)
Headquarters Governmental Liaison (HQ GL)

  1. Assists the ODs/FDs 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 headquarters OD/FD staff.

  4. Develops policy and provides oversight for the IRS 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-TEGE related activities).

  6. Oversees GL training.

  7. Measures overall program effectiveness.

  8. Serves as primary liaison with the Federation of Tax Administrators (FTA) and for the Multi-State Tax Commission (MTC).

  9. Coordinates IRS training classes and materials that are offered for state and local governmental agency personnel. This information is available at the following web address: http://mysbse.web.irs.gov/CLD/GLD/GL/Training/4304.aspx.

  10. Coordinates with LA staff to oversee and implement the GL portion of the CAP. Additional information is available at the following web address: http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx.

11.4.1.3.1.1  (05-17-2011)
Customer Service Strategy

  1. The HQ GL Customer Service Strategy (CSS) is the over-arching plan to ensure effective communications with internal and external stakeholders, accomplished by the following:

    1. Sharing information and facilitating the implementation of programs involving field GL staff, Stakeholder Liaison (SL), other SB/SE components, and other ODs/FDs.

    2. Collaborating with CLD components to identify activities and develop appropriate strategies to consolidate key messages into a unified voice, as appropriate, for diverse audiences.

    3. Sharing information with Congressional offices and federal, state, and local governmental agencies, the FTA, the MTC, and other external stakeholders as appropriate.

  2. CSS Objectives:

    1. Support the IRS Strategic Plan

    2. Support SB/SE CLD Program Letter objectives

    3. Establish a clear strategic direction with direct links to the resources and activities of SB/SE and the IRS ODs/FDs

    4. Develop appropriate strategies to identify and resolve emerging issues identified in the field and in the CLD Issue Management Resolution System (IMRS) and direct workflow to the appropriate process

    5. Identify partnering opportunities with SL

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

    7. Increase Service-wide awareness of GL activities

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

    9. Enhance and increase accessibility to GL products and documents available to internal stakeholders using the IRS Intranet, the GLD web site, GLD SharePoint, and the GL Inventory Database, as appropriate

    10. Maintain a working relationship/coordination between GL and TAS

  3. CSS Components:

    1. GL Business Template process. See IRM 11.4.1.13. Also see Exhibit 11.4.1-4.

    2. HQ GL Communiqué Template. See Exhibit 11.4.1-1.

      Steps for Communique
      1) The GL communiqué is accessible by GL employees with proper access permissions on the GLD SharePoint site: http://wsep.ds.irsnet.gov/sites/co/dcse/sbse/cl/GLD2/Lists/GLD%20Communiques/AllItems.aspx. The communiqué is used by HQ GL analysts to solicit external partner involvement in a project through the field GLs, as well as to share information on national GL programs.
      2) The GL Communiqué 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 communiqué will include supporting documents, e.g., MOUs, templates, fact sheets, talking points, etc.
      3) A communiqué generally will be created whenever information or actions need to be solicited from or communicated to the field by HQ GL.
      4) The communiqué will be updated by HQ GL, as necessary, to ensure delivery of accurate messages to the field.

    3. The SB/SE Communications Resource Center (CRC) contains a collection of policy guides, communication tips, and approved key messages for IRS employees to use when preparing speeches and articles about SB/SE programs and initiatives for internal and external audiences.

      Communications Resource Center
      1) The CRC can be accessed at: http://mysbse.web.irs.gov/AboutSBSE/CLD/Communications/CRC/default.aspx.
      2) This application is primarily designed for SB/SE GL and SL employees involved in conducting outreach, but may also be useful to other SB/SE employees and managers to ensure consistent messages are used regarding SB/SE programs with all external audiences.
      3) SB/SE outreach initiatives can be searched through CRC links.
      4) Procedures and a template for structuring messages are available in Exhibit 11.4.1-2.

    4. GL Inventory Database.

      GL Inventory Database
      1) The GL and Federal Intergovernmental Partnering Program (FIPP) inventories and instructions are located on the GLD SharePoint site. These inventories are GL and management tools intended to be a complete source of all GL projects and programs nationwide.

    5. GLD SharePoint.

      GLD SharePoint
      1) GLD SharePoint is a centralized repository for agreements, instructions, templates and other necessary reference information for GLs.
      2) The GLD SharePoint site contains scanned agreements and MOUs.
      3) There is a "Search" box at the top right of every SharePoint site for searching files by keyword of the file name.

    6. GL Web Page – The GL web page contains current information regarding the IRS GL Program and activities at the following web address: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/GL/default.aspx.

11.4.1.3.1.2  (05-17-2011)
Tax Gap Initiative

  1. Introduction

    1. The tax gap is the difference between what taxpayers should have paid and what they actually paid on a timely basis.

    2. The tax gap was estimated at $345 billion based on data compiled by the National Research Program (NRP) for Tax Year 2001. IRS enforcement activities and late payments recovered about $55 billion, which left a net tax gap of $290 billion for Tax Year 2001.

    3. More information on the tax gap is located on the Internet at the following: http://www.irs.gov/newsroom/article/0,,id=158619,00.html and on the Intranet at the following: http://mysbse.web.irs.gov/AboutSBSE/CLD/Communications/Special+Programs/Tax+Gap/default.aspx.

  2. GL Role - To implement the IRS strategy to reduce the tax gap by taking the following actions:

    1. Facilitating the development of compliance programs to reduce the tax gap by working with internal and external stakeholders.

    2. Changing attitudes about the tax gap through education and outreach with stakeholders.

    3. Identifying new stakeholders and resources that can be leveraged to implement a tax gap strategy.

      GLD Tax Gap Initiatives
      1) GL tax gap initiatives are posted in the GL Programs/Initiatives section of the Intranet at the following: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/GL/Programs/default.aspx.
      2) GLs should implement these initiatives with their internal and external stakeholders.

11.4.1.3.2  (05-17-2011)
Governmental Liaison and Disclosure Area Managers

  1. GLD AMs (like the Chief, GL) report to the Director, GLD. They manage, direct, and oversee the work of the following field GLD personnel:

    1. GLs

    2. Disclosure Managers (DMs) and their staff

    3. Area Technical Advisors

    4. Area administrative staff

  2. GLD AMs deliver GLD programs through effective use of staff and resources. They refer GL program issues that require technical, procedural or policy support to the Chief, GL for resolution. GLD AMs also convey key IRS messages to senior state and local officials, either directly or through field GLs.

  3. GLD AMs implement the GL program by:

    1. Communicating and clarifying national policies, guidelines, and initiatives.

    2. Partnering and networking with OD/FD management officials on local and national initiatives.

    3. Partnering and networking with federal, state, and local governmental agency executives responsible for operations in the GLD area.

    4. Representing GLD at internal conferences and meetings.

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

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

    7. Retaining ultimate responsibility for coordinating the signing of Basic Agreements (BAs) by the IRS Commissioner within established timeframes and for ensuring the transmission of a signed original agreement to the agency head.

    8. Reviewing and approving new Implementing Agreements (IAs) and Memorandums of Understanding (MOUs) prior to signing by the appropriate IRS official.

    9. Executing updated or amended IAs and MOUs that do not involve the use of additional resources or change the number of ODs/FDs providing resources.

    10. Ensuring GLs are personally involved and support activities connected with Safeguard Procedures Reports (SPRs) and/or Safeguard Activity Reports (SARs) required by agencies receiving federal tax information (FTI) and, becoming personally involved, as needed, and elevating to the Office of Safeguards (Safeguards) any SPR/SAR matters requiring policy or procedural guidance.

      Note:

      HQ GL does not issue policy or procedural guidance on safeguard report requirements since that is under the jurisdiction of Safeguards.

    11. Approving the participation of GLs in safeguard reviews and, in coordination with Safeguards, serving as a key contact with agencies on substantial safeguard issues that require high-level involvement to assist Safeguards in resolving deficiencies or data loss/protection issues.

    12. Providing oversight of training requests from governmental agencies.

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

11.4.1.3.3  (05-17-2011)
Governmental Liaisons

  1. GLs are the primary point of contact for managing IRS relationships with the following:

    1. Federal, state, and local governmental agencies in their assigned state(s) and/or Insular Territories.

    2. Congressional offices, as assigned, and Insular Territories on IRS policy issues.

  2. 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. Manage the GL Data Exchange Program (GLDEP) locally.

    2. Implement national or area projects and initiatives.

    3. Collaborate with the DM and agency points of contact to draft language for BAs.

    4. Invite Safeguards to initial meetings with agencies to explain the safeguard procedures outlined in Publication 1075, Tax Information Security Guidelines for Federal, State, and Local Agencies.

    5. Secure language approval and signatures in accordance with published procedures.

    6. Coordinate the signing of the BAs, IAs, and MOUs by the head of the tax/revenue agency.

    7. Create the BA, IA, or MOU draft according to approved IRM templates and coordinate with the DM and ODs/FDs, as appropriate.

    8. Consult with HQ GL to determine if MOUs should be incorporated into revised IAs.

    9. Secure language approval and signatures in accordance with GLD procedures and distribute signed original agreements and/or copies of such agreements to state agencies and IRS officials, as appropriate.

    10. Distribute signed original BAs, IAs, and MOUs to agencies and appropriate IRS OD/FD functions.

    11. Forward copies of GL agreements to Data Services (DS) for scanning and posting on the GLD SharePoint site and update the GL Inventory.

    12. Initiate annual reviews of IAs and MOUs in collaboration with the DM.

    13. Ensure new initiatives and projects are added as revisions or addenda to IAs and/or are covered by MOUs, as needed.

    14. Assist ODs/FDs with meetings, outreach efforts, and initiatives involving federal, state, and local governmental agencies.

    15. Consult with Disclosure when planning or implementing GL initiatives, especially those that involve the exchange of FTI, Personally Identifiable Information (PII), or other sensitive but classified (SBU) information.

    16. Refer to and/or consult with Disclosure on all requests for FTI received from other governmental agencies or for other information not specifically determined to be available to the public.

    17. Conduct appropriate research to resolve issues and inquiries independently and consult with Disclosure, HQ GL, DS, Safeguards, and other IRS ODs/FDs, as necessary.

    18. Assist state tax/revenue agencies in meeting their IRS safeguard reporting requirements by referring questions concerning proper completion of outstanding SPRs and SARs to Safeguards as they arise.

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

    20. Communicate with federal, state, and local governmental agencies about IRS OD/FD strategic objectives and communicate external agency initiatives and objectives to key internal stakeholders.

    21. Represent the IRS at meetings with federal, state, and local governmental agencies.

    22. Prepare briefings for the GLD AM and provide input and feedback from stakeholders regarding existing and potential IRS initiatives and projects.

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

    24. Identify the members of Congress whose constituents are affected by disasters and provide information to them about actions taken to assist disaster victims with their tax affairs.

  3. The GL is the primary IRS spokesperson with the state and district offices of members of Congress. This responsibility is part of the CAP. The GL will resolve Congressional Correspondence that does not involve casework or individual taxpayer information. The Local Taxpayer Advocate (LTA) is the primary CAP contact with the Congressional office for casework and taxpayer-specific issues.

  4. The GL’s CAP duties include, but are not limited to the following:

    1. Communicating at least monthly with local Congressional offices.

    2. Disseminating information and key messages from LA to Congressional offices.

    3. Responding to Congressional staff and constituent questions about IRS policy and procedures.

    4. Working with the LTA to ensure appropriate issues are assigned and controlled on the Taxpayer Advocate Management Information System (TAMIS).

    5. Representing the IRS at meetings with Congressional staff.

    6. Working with the LTA to ensure a coordinated approach to all CAP activities.

  5. The CAP web site contains several products, listed below, that are useful to the GL. These products can be found at the following link: http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx.

    1. An Overview of the IRS for Congressional Staff - This brochure may be used to provide a quick orientation to the IRS for new Congressional delegations or staff members. Copies should be ordered from Publishing Services, as this is a specialty print document.

    2. Catalogue of Congressional Update Newsletters, which contains newsletters for Congressional delegations that are issued on a quarterly basis. Current and back issues are stored at this site.

    3. Products that can help GLs with Congressional Correspondence include the following:
      1) Catalogue of Issue Letters - letters for certain issues that have been approved and may be used as a template
      2) Catalogue of CAP Communiqués - communiqués issued by LA for required action or information
      3) GL Pre-Visit Check Sheet - useful for planning visits to Congressional offices
      4) Links to Research Resources - lists many items that may be helpful

    4. Other helpful links are as follows:
      1) Writing to Congress, which is a LA Congressional Correspondence page, accessible at: http://irweb.irs.gov/AboutIRS/bu/cl/la/lawr/default.aspx.
      2) The Budget in Brief, which is an analysis of the administration’s budget proposal for the IRS, at: http://irweb.irs.gov/AboutIRS/bu/cl/la/labdg/default.aspx.

11.4.1.4  (05-17-2011)
IRS Roles and Responsibilities in Support of Governmental Liaison

  1. GL programs, initiatives, and projects often involve one or more ODs/FDs and may involve multi-agency partnerships (MAP) to maximize interagency cooperation and leverage resources.

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

    2. CLD staff provide technical assistance and/or partner with GL, as follows:
      (1) SL staff manage relationships with SB/SE taxpayers and stakeholder organizations. SL and GL staff frequently provide support at joint outreach events where IRS information is shared with small business and federal, state, and local governmental agency stakeholders. SL and GL headquarters and field staff play a critical role in disaster assistance programs, coordinating locally to help affected taxpayers.
      (2) Communications staff provide products and services that enhance delivery of SB/SE's program messages available for GLs to share with federal, state, and local governmental agencies and Congressional stakeholders.
      (3) DS staff manage the critical GLDEP, coordinating the routine disclosure of a vast amount of FTI to qualified federal, state, and local governmental agencies.
      (4) 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.

    3. LA staff provide information and key IRS messages written for Congressional audiences. GLs are the field presence for IRS communication with local Congressional staff. LA also provides assistance with responses to local "hot topics," such as workload realignment that might affect IRS operations. LA coordinates with HQ GL staff to oversee and implement the field portion of the CAP through the GLs. See the CAP web site at the following web address: http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx.

    4. TAS, via LTAs, partners with GL in implementing the CAP. In addition to working Congressional inquiries involving taxpayer account issues, the LTA partners with GL to conduct Congressional Liaison Meetings, Congressional Caseworker Briefings, and other outreach to Congressional staff.

    5. OD/FD staff at all levels provide resources and technical expertise necessary to create and implement GL initiatives and projects to achieve tax compliance, accomplish Service goals, and enhance federal tax administration. They provide the technical and procedural tax expertise needed by the field GL staff to respond to Congressional inquiries. Memorandums of Understanding with SB/SE and Wage & Investment (W&I) provide a framework for any assistance GLs need. The SB/SE and W&I MOUs are also available at CAP web site, above.

11.4.1.5  (05-17-2011)
Partnering with Federal, State, and Local Governmental Agencies

  1. GL manages partnering relationships between the IRS and federal, state, and local governmental agencies.

  2. The GL is the primary point of contact for these agencies, whose role is to facilitate partnering activities with the agencies to improve tax administration in support of IRS strategic priorities. The GL will:

    1. Develop relationships with federal, state, and local governmental agency personnel who are authorized to act as liaisons for their agency.

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

    3. Facilitate projects and initiatives between federal, state, and local governmental agencies and IRS ODs/FDs.

    4. Arrange joint training sessions.

    5. Manage the GLDEP locally.

    6. Act as liaison between the IRS and federal, state, and local governmental agencies for other tax administration matters.

  3. The Federal Intergovernmental Partnering Program (FIPP) is a program that provides a systematic and structured approach to expanding existing and establishing new relationships with other federal agencies to develop initiatives that support OD/FD priorities. The program will help ensure that IRS has a centralized process to appropriately coordinate new federal initiatives and provide a Service-wide inventory of current agreements and projects. FIPP partnerships encourage leveraging of IRS resources to identify, gather, and share information and data, particularly where initiatives and relationships have the potential for increased tax compliance and decreased taxpayer burden. To further the mission and objectives of the Service, it is critical that IRS leverages resources with other federal agencies to achieve IRS strategic goals. HQ GL will act as the liaison between the IRS and federal agency headquarters offices. HQ GL will facilitate the development of new relationships between ODs/FDs and other federal agencies, but ownership of new federal initiatives remains with the respective OD/FD. Existing IRS/federal agency relationships are not affected by the FIPP, other than by the inclusion of ongoing initiatives in the FIPP inventory. Field GLs are the primary points of contact with local branch or field offices of other federal agencies.

  4. The GL will work closely with the DM in activities where FTI is provided to state tax agencies. The DM will coordinate, review, approve, documents with respect to the following:

    1. BAs, IAs, and MOUs facilitated by the GL

    2. GLDEP enrollment agreements

    3. Tax data element selection forms

    4. Exchanges of FTI

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

11.4.1.5.1  (05-17-2011)
Partnering Examples for Improving Tax Administration

  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 (ERO) 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 Financial Management Service (FMS), 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.

  4. The Questionable Employment Tax Project (QETP) - The QETP MOU allows the IRS and State Workforce Agencies (SWAs) to share audit results and conduct side-by-side employment tax audits.

11.4.1.6  (05-17-2011)
Stakeholder Relationship Management Overview

  1. SL manages SB/SE’s Stakeholder Relationship Management (SRM) for practitioner and business stakeholders and maintains the SL SRM web site with information on projects and outreach activities affecting practitioners and small business stakeholders. See Exhibit 11.4.1-3 for a chart that identifies GL and SL stakeholder relationships and possible opportunities to support each other with respect to identified stakeholders.

  2. Many area offices have an SRM Local Council (SRMLC) to deliver SRM 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 ODs/FDs. 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 CLD 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 ODs/FDs to partner with states or other agencies and vice versa. GL support for OD/FD projects promotes relationship building. Leveraging resources is a major benefit of mutual support.

11.4.1.6.1  (05-17-2011)
Federal, State, and Local Governmental Agency Relationship Management

  1. The GL and the DM (sometimes in conjunction with the Tax Exempt and Governmental Entities (TE/GE) Division's Federal, State, and Local Governments (FSLG) 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, etc.

  2. The GL will facilitate ad hoc meetings between the IRS and federal, state, and local governmental agencies on Service-wide issues (e.g., abusive tax schemes, tax gap) or on functional issues.

  3. The GL has a general understanding of the state and local tax structure in their assigned states(s) and can provide information about state and local taxes to the ODs/FDs. The GL will share information about new IRS policies, procedures and programs with federal, state, and local governmental agency staff.

  4. GLs will refer inquiries to TE/GE that involve external agency tax filing requirements and other tax and compliance issues related to federal, state, and local governmental agencies (versus partnering, outreach, training and other non-tax related issues).

11.4.1.6.2  (05-17-2011)
Stakeholder Relationship Management Local Council

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

    1. Share information about external partners that may impact the ODs/FDs.

    2. Identify and evaluate OD/FD 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 OD/FD project or initiative.

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

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

11.4.1.7  (05-17-2011)
Disclosure of Tax Information to State Tax and Other Agencies

  1. The IRS is authorized by statute, IRC §6103(d), to disclose FTI to state tax officials and state and local law enforcement agencies 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:

    1. The Agreement on Coordination of Tax Administration is commonly referred to as the "Basic Agreement" , or BA. Basic Agreements must be signed by the Commissioner of Internal Revenue and the head of the state tax agency. The provisions of the BA encompass required procedures and safeguards for exchanging tax information. See IRM 11.3.32.5 for more specifics regarding BAs. See IRM Exhibit 11.3.32–1 for the standard language for BAs.

    2. Implementing Agreements (IAs) are developed by the GL in accordance with the provisions of the BA. The IA supplements the BA by providing for continuous or routine exchanges of information, such as examination reports, abusive scheme data, etc. New IAs must be signed by the head of the state tax agency and by the appropriate OD/FD Commissioner or other official properly delegated the authority to execute such agreements. In addition, individuals who sign IAs on behalf of an IRS function must also have appropriate disclosure authority and responsibility for any FTI provided under the agreement. Implementing Agreements may be amended when there are changes to responsible parties, new exchanges added, new or revised procedures, tolerance changes, etc.

    3. GLD AMs may sign revised or updated IAs that do not involve the use of additional resources or change the number of ODs/FDs providing resources. When an IA involves several amendments or significant changes, the GL will consider initiating a new IA.

    4. Memorandums of Understanding (MOUs) may be used in lieu of revising/amending IAs or for new projects/initiatives of limited duration that may warrant a pilot/test before a decision is made on full implementation. 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). The GL MOU Template at Exhibit 11.4.1-6 will be used for any MOUs being developed. See IRM 11.4.1.13.1(3) for more specifics regarding the GL MOU Template. Examples of programs warranting separate 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 (ModIEIN/One Stop) application, which allows any state or local agency to participate, but does not provide for the disclosure of FTI.

    5. HQ GL analysts will assist in determining the proper IRS official to sign/execute IAs, MOUs or other agreements based on available guidance. GLD AMs may sign revised or updated MOUs that do not involve the use of additional resources or change the number of ODs/FDs providing resources.

      Note:

      According to Chief Counsel, until a Service-wide delegation of authority is finalized, new agreements and MOUs with external agencies that are under the jurisdiction of one OD/FD must be signed by the appropriate OD/FD commissioner or chief. If more than one OD/FD is involved or if Modernization and Information Technology (MITS) resources are involved, follow the guidelines provided in the memorandum from the Director, Communications, Liaison and Disclosure, entitled "Signatures on Implementing Agreements and Memorandums of Understanding," dated May 5, 2004.

    6. For additional information about IAs, see IRM 11.3.32.6. See IRM Exhibit 11.3.32-3 for standard IA language.

      Exception:

      Exchanges made using the IRS Secure Data Transfer (SDT) program may require an SDT Participation Statement in addition to an MOU or other agreement.

  4. Prior to the receipt 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 preparation of a new or revised Safeguard Procedures Report (SPR).

    1. If the approved MOU or agreement involves the disclosure of FTI, the agency must meet IRS safeguard requirements prior to the receipt of the FTI under the MOU.

    2. The GL will transmit the SPR Certification document (Exhibit 11.4.1-9) to the agency along with the MOU.

    3. If initial MOU meetings are held, the SPR Certification document will be discussed with the agency.

    4. The agency will complete the SPR Certification document to certify:
      1) That the head of the agency understands that the receipt of the FTI under the MOU is subject to IRS safeguarding requirements;
      2) That if the agency does not have a current, approved SPR, the head of agency understands the agency will not receive FTI pursuant to the MOU until there is an approved SPR;
      3) That if the agency has a previously approved SPR that does not include procedures to safeguard the FTI to be exchanged pursuant to the MOU, the head of agency understands the agency will not receive FTI pursuant to the MOU until the agency has an approved addendum to the existing SPR; or
      4) That the agency has a current, approved SPR that includes procedures to safeguard the FTI authorized to be exchanged pursuant to the MOU.

    5. The signed SPR Certification document must be received from the agency along with the signed MOU.

    6. The GL will forward the signed SPR Certification to Safeguards in accordance with the instructions.

    7. The GL and/or HQ GL analyst will coordinate with the business owner to ensure the agency does not receive FTI pursuant to the MOU unless/until the agency has a current, approved SPR that includes procedures to safeguard the FTI to be exchanged pursuant to the MOU.

    8. Refer to IRM 11.3.6, Safeguard Review Program for more information about safeguarding requirements.

11.4.1.8  (05-17-2011)
Processing Requests for Tax Information

  1. FTI may be requested on a case-by-case basis using Form 8796, Request for Return/Information. Form 8796 (or a letter containing the required information from Form 8796) is used by state tax agencies to request FTI and may be used by the IRS to request information from state tax/revenue agencies.

  2. Form 8796 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.10.

  3. IRS offices, including field GLs, that receive written requests for FTI from states via Forms 8796 or other documents generally will refer them to the Disclosure Office for processing or assistance.

11.4.1.9  (05-17-2011)
Safeguard Review Program

  1. The Office of Safeguards ensures federal, state, and local governmental agencies properly protect FTI in their possession to IRS standards. Safeguards staff conduct oversight reviews of agencies to verify that safeguard requirements are met. See IRM 11.3.36, Safeguard Review Program and Publication 1075, Tax Information Security Guidelines for Federal, State, and Local Agencies and Entities.

  2. Safeguards determines the frequency of Safeguard and Need and Use Reviews, which are usually conducted every three years, but may be more frequent if circumstances dictate. Safeguards reviews the safeguard procedures of agencies that receive FTI to determine compliance with the safeguard requirements of IRC §6103(p)(4), as well as the agency’s state tax administration need and use of the information in accordance with Policy Statement P-1-35.

    1. As the primary relationship manager with state tax agencies, the GL may participate in opening or closing review conferences (either in person or via conference call), as approved by the GLD AM, at the request of the Safeguards.

    2. When serious deficiencies are identified during the on-site Safeguard Review, the GL will manage the relationship with the agency but will not act as an advocate for the agency. The GL will brief the AM about any serious deficiencies.

    3. The assigned Safeguards Disclosure Enforcement Specialist (DES) will schedule all reviews and provide all official notifications to state agency officials. The DES will also give the GL assigned to the state agency advance notice of a planned review. Upon request from the DES, the GL may be asked for a current assessment of the relationship with the agency. Specifically, the DES may inquire about any open or pending data exchange issues and any sensitive issues or agency concerns that may need to be addressed during the on-site review.

    4. During such calls, the GL will provide any other information concerning the relationship with the agency that may have a bearing on the review. GLs will also identify any changes to the list of state personnel authorized to make written requests for FTI.

    5. During the on-site review, the GL may:
      1. Serve as a resource person to clarify issues related to the GLDEP and MOUs.
      2. Review GLDEP specifications books with state agency staff and highlight any changes.
      3. Identify other potential uses for data extracts.
      4. Help to identify changes to the authorized list of agency requesters.
      5. Assess additional state needs.

    6. After the on-site review, the GL may:
      1. Follow-up on information obtained during the review to assist the agency in complying with safeguard requirements if deficiencies were noted.
      2. Ensure the agency understands the availability of FTI from the IRS from various sources for state tax administration purposes.
      3. Use information obtained during the review to propose new initiatives, suggest needed training, propose enhancements to the GLDEP, or recommend that the state make changes in future GLDEP enrollment forms or data element selection forms.

11.4.1.10  (03-01-2007)
Coordination of Projects and Joint Initiatives

  1. One of the GL’s key responsibilities is to explore opportunities to partner with other governmental entities to improve tax administration and reduce burden on taxpayers. Many opportunities are found through joint initiatives with external agencies. Opportunities also exist to partner with federal and local agencies, as well as with Congressional offices.

  2. The GL will assist in facilitating state, local, and local federal agency support for initiatives owned by the ODs/FDs.

  3. GLs will manage CAP for their state(s) and will encourage OD/FD participation in CAP activities, as appropriate.

    Example:

    An OD/FD representative may be invited to make a presentation at a meeting for Congressional staff. GLs will also share responsibility for CAP program initiatives with the LTA with program guidance from LA.

  4. GLs may identify and facilitate joint initiatives involving IRS ODs/FDs and other partners. However, the day-to-day management of such initiatives is the responsibility of the OD/FD.

11.4.1.11  (05-17-2011)
Partnership Activities and Examples

  1. GLs will adhere to Section 5.3 of the BA 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, stocking tax forms for the public, 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. Examples of partnership activities authorized by the BA include:

    1. Taxpayer Assistance
      1. Joint Walk-in assistance. The IRS may offer space in a Taxpayer Assistance Center (TAC) to state staff, especially during filing season, for state return preparation and assistance. IRS staff may also work at a state facility. In some TACs, IRS staff prepare both federal and state returns electronically.
      2. IRS and state staff can work together at commercial sites, such as stores, to prepare returns during filing season.
      3. In some states, IRS offices and state tax agency offices are co-located. They share adjoining space, either in a commercial building or in a federal or state office where the tenant agency pays rent.
      4. In many states, the IRS and the state tax agency jointly train Voluntary Income Tax Assistance (VITA) and Tax Counseling for the Elderly (TCE) volunteers. This training allows the volunteers to prepare both federal and state returns at volunteer sites.

    2. Stocking Tax Forms
      1. Taxpayer Assistance Centers. In many states, the IRS and the state tax agency provide each other commonly used forms for distribution at local offices.
      2. Kiosks. In some states, the IRS and the state provide tax information at kiosks or in commercial locations at governmental offices. Services available at kiosks include printing current and prior year state and federal forms and providing answers to frequently asked questions.

    3. Training Personnel
      1. The GL may coordinate with IRS training staff and state tax agencies to enroll state employees in IRS training classes, such as Revenue Agent Basic Training. State employee enrollment is limited to those classes where there is space available. There is generally no cost to the state for its employee's attendance in a locally held class. As an alternative, GL developed a system for distributing selected IRS training material to state tax agencies. See the GL intranet web page on this issue at the following: http://mysbse.web.irs.gov/CLD/GLD/GL/Training/4304.aspx.
      2. GL created a training database with electronic file copies of the training classes requested most frequently by state tax agencies. These class files may be shared with state tax agencies. The agencies may print copies to train their employees. The following classes/materials are currently available:
      •Tax Compliance Officer Units 1, 2, and 3
      • Revenue Officer Units 1, 2, and 3
      • Flow Through Entities
      • Revenue Agent Basic Corporations
      • Revenue Agent 1040
      3. Each GLD area has a representative who has access to the training materials database to assist with filling requests from the states.
      4. Continuing Professional Education (CPE). ODs/FDs may invite state tax agency staff to attend their CPEs, especially if there are topics relevant to state tax administration. The GL will coordinate the state’s attendance at IRS CPEs. When the state has training that is of interest to IRS employees, the state may invite the IRS to participate.
      5. Chief Counsel Video/IVT Courses. Chief Counsel invites state tax agency employees to attend many of its video courses. The course schedules and class descriptions for Chief Counsel and NYU/IRS CPE classes may be viewed at the following web address: http://counsel.web.irs.gov/eTools/training. The GL will enroll state employees if there is space available through the IRS Counsel web site.
      State staff may take the course examination and earn credits for professional certifications. State employees must coordinate CPE or Continuing Legal Education (CLE) credits with their professional society.
      In some instances, textbooks may be required for these courses. When textbooks are required for a particular course, the state agency must purchase the required textbooks.

11.4.1.12  (03-01-2007)
Identifying Joint Initiatives

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

  2. To identify joint initiative opportunities, the GL must know the program goals and strategic plans and/or priorities of internal and external stakeholders. GLs should have a working knowledge of IRS goals and strategic plans along with the more specific goals and objectives of the ODs/FDs. In addition, GLs should be familiar with the goals and strategic plans of state and local tax and non-tax agencies, federal agencies, Congressional offices, 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.

  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 GLD SharePoint site at the following web address: http://wsep.ds.irsnet.gov/sites/co/dcse/sbse/cl/GLD2/Lists/FedState%20and%20FedFed%20Inventories/AllItems.aspx

11.4.1.12.1  (05-17-2011)
Implementing Joint Initiatives

  1. The role of the GL is to identify, initiate, and facilitate GL partnering opportunities. Implementation and day-to-day management of an initiative is the responsibility of the IRS OD/FD program owner. Examples of joint initiatives initiated and/or facilitated by GL but owned and managed by an OD/FD include:

    1. Joint Abusive Tax Avoidance Transactions (ATAT) MOU

    2. Questionable Employment Tax Practices (QETP) MOU

    3. Lien Centralization Initiative

    4. Practitioner seminars taught by IRS and state tax agency employees

    5. Modernized e-File (MeF)

  2. In his/her role as facilitator of an OD/FD managed initiative, the GL will ensure the initiative is worked jointly with IRS partners. Among other things the GL will:

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

    2. Identify and include all relevant stakeholders (e.g., Disclosure, the Office of Safeguards, Counsel).

    3. Arrange and, where appropriate, attend or conduct meetings between the OD/FD and other governmental agencies.

    4. Monitor action plans and activities.

    5. Maintain initiative files, including a GL Business Template, where appropriate. The GL will also maintain correspondence and other historical initiative information in initiative files.

    6. Bring together the parties responsible for drafting any required MOUs, e.g., the Disclosure Office, the Counsel GL Coordinator, the appropriate OD/FD, the external stakeholder(s) involved, etc. The GL will provide input and assistance to the process of drafting the MOU, as necessary.

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

  3. GLs will maintain files for the GLDEP and for the CAP.

11.4.1.13  (05-17-2011)
GL Business Template for Joint Initiatives

  1. Initiatives worked jointly by IRS and other governmental entities are developed and documented using the GL Business Template. The GL Business Template is a tool used to establish a business case for proposed joint initiatives with state, local, and federal agencies. The template is a guide to ensure joint initiatives support IRS business objectives and/or key stakeholder objectives and that key issues are identified and addressed in developing proposed initiatives. In partnership with ODs/FDs, the GL will use the GL Business Template to guide the development of initiatives and document key information that must be addressed in pursuing local and national initiatives.

  2. The GL Business Template is used for all new initiatives with other governmental entities unless an exception applies. Exceptions are:

    1. Routine activities requiring only local approval. For example, joint forms availability at mutual sites; joint filing season publicity; joint committees, conferences, workshops, training, etc.

    2. Replicating a previously approved initiative without substantial changes.

    3. Exchanges of or access to information already covered by an existing IA provision or MOU.

  3. Preparation of the GL Business Template does not preclude addressing OD/FD requirements for completing the appropriate Compliance Initiative Project (CIP) or other required documentation.

11.4.1.13.1  (07-08-2008)
Completing the GL Business Template and the MOU Template

  1. Refer to the GL Business Template and the GL MOU Template, available at Exhibit 11.4.1-4 and Exhibit 11.4.1-5, while reviewing the following:

    1. The Business Template consists of three parts (Parts A, B, and C). The GL will complete Part A when developing a local initiative or making a successful local initiative available for broader implementation.

    2. Information included in Part A includes the initiative title, the originating office, IRS contacts, the business owner (OD/FD, GL, or joint), IRS strategic business objective(s) supported, participating agencies and their contacts, description of the initiative, applicable business measures, and expected benefits, savings or results.

    3. Part A serves as the historical record of an initiative’s development. It is used during operational reviews, when sharing information about an activity with other GLs, in marketing an activity to an OD/FD, and as documentation of the initiative for the GL’s records.

    4. When considering a local initiative requiring Part A of the Business Template, the GL will check with the responsible HQ GL analyst to see if a similar initiative has been pursued in another state. If a similar initiative has been pursued, the GL will secure a copy of Part A from that initiative for review and discuss the initiative with the originating GL to determine the status and outcome.

    5. GLs may provide a completed Part A to any OD/FD or external partners when marketing a new local initiative.

    6. If an OD/FD chooses to develop a Part A activity, the GL will ask the function to complete Part A of the Business Template. If an external partner approaches the GL to initiate a Part A activity, the GL will complete Part A.

    7. Upon completion by the GL or OD/FD staff, the Business Template, Part A, will be approved by the GLD AM and by the TM or above of any impacted OD/FD.

  2. In addition to Part A, Part B of the GL Business Template must be completed when a proposed initiative must be reviewed and approved at the OD/FD headquarters level and/or must be tested before implementation. Initiatives requiring the completion of Part B include:

    1. New data exchanges/initiatives

    2. New use of data currently exchanged

    3. Joint compliance activities

    4. New data matching initiatives (e.g., State Reverse File Matching Initiative (SRFMI))

    5. Any initiative requiring CIP (Compliance Initiative Projects) procedures or a Privacy Impact Statement (Refer to IRM 4.17.1, Compliance Initiative Projects, for CIP procedures, and refer to IRM 11.3.14.12, Controlling Information From Third Parties, for Privacy Impact Statement requirements).

    6. Any initiative that may require revising IRS procedures or working conditions.

    7. Information recorded in Part B includes resource requirements; information on internal or external coordination agreements (e.g., technical advice and CIPs); labor relations issues; legal, disclosure, privacy, and security issues; information systems certification; piloting and testing issues; training information; policy issues (e.g., IRM deviations or regulation changes); and a conclusion or summary.

  3. Part C is the GL MOU Template, which will be used for any MOUs initiated by the Service. The MOU template contains standardized language sections (disclosure, safeguards, record keeping requirements, transmittal procedures, privacy, evaluation of data exchange, evaluation of agreement, etc.) which should be included in each MOU. However, an MOU is not required for all initiatives. Any FTI provided to a state tax or other agency must be specifically addressed in the applicable IA or must be covered in an MOU or ad hoc (specific) written request for the information. GL will coordinate with Disclosure and the business owner to determine whether an MOU or another option will be used to establish and implement the initiative. See Exhibit 11.4.1-5.

  4. An MOU is also appropriate for short-term projects and 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 §6103(d), or for activities not involving a disclosure of FTI or other protected information. An MOU may supplement an IA when the instructions and procedures of the activity are such that they would unduly lengthen or complicate the IA. An MOU may also be used as interim documentation of the authority and provisions of the activity when an initiative is being piloted or while the IA is being amended or renegotiated to include an ongoing activity or exchange of FTI.

  5. If an MOU is drafted for a local Part A initiative, it should be routed to the following parties for review:

    1. State agency or other governmental partner(s)

    2. OD/FD partner(s)

    3. Local DM

    4. Local Counsel

    5. GLD AM


    An MOU will be signed/executed by the head of the state tax agency or other appropriate representative of a non-tax agency authorized to act for the agency involved. The authority to sign MOUs and other agreements by IRS officials will be based on Service-wide and/or OD/FD delegated authority. HQ GL analysts will assist, as necessary, in determining the proper IRS officials to sign MOUs and agreements on behalf of the IRS.

  6. If a local initiative is not recommended for replication, Part A of the GL Business Template will be maintained in the GL’s initiative file. If there is an MOU, a signed copy will also be maintained in the initiative file. If a Part A initiative is recommended for replication, the completed Part A and the MOU, if applicable, will be submitted by the GL to the GLD AM. After review, the GLD AM will send the initiative information to the HQ GL analyst contact for the OD/FD involved, who will coordinate with the Counsel GL Coordinator, if necessary. After all necessary reviews and approvals, the HQ GL analyst will have Part A and the MOU, if applicable, distributed to the field GLs and posted on the GL SharePoint site.

11.4.1.13.2  (07-08-2008)
Approval Process for GL Business Templates and MOUs

  1. The GL Business Template is also available through the GL intranet site at: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/GL/Resources/Documents/default.aspx.

  2. The following procedures apply when a GL Business Template Part B initiative must be reviewed and tested by an OD/FD headquarters office prior to approval and implementation or when making substantive revisions to a previously approved Part B initiative (i.e., replicating an initiative).

    1. GL will coordinate and facilitate the completion of the GL Business Template, Parts A, B, and, if there is an MOU, Part C. It is typical to have an MOU for a Part B initiative to provide documentation of key elements to the appropriate OD/FD executive(s) who must approve the initiative. If there is an MOU, GL will consult with Disclosure, appropriate OD/FD staff, and local or HQ Counsel to ensure all items are properly addressed. For locally-initiated projects, the GL will send the completed template to the GLD AM and to the OD/FD TM or above for review and approval. Headquarters-initiated business templates and MOU Templates will be approved by the appropriate OD/FD HQ executive before any partnering activities may begin.

    2. Once the local or national GL Business Template and GL MOU Template are approved, and the MOU has been signed by all parties, the package will be returned to the initiating field GL or HQ GL analyst.

    3. The field GL will secure the agency signature on the approved MOU and forward the signed MOU to the local OD/FD TM or above. The TM or above will secure the signature of the OD/FD Commissioner or other official properly delegated to sign MOUs and agreements.

    4. HQ GL will distribute approved MOUs to field GLs with appropriate instructions for soliciting state/agency involvement.

    5. The OD/FD will use its distribution channels to share the approved GL Business Template and GL MOU Template within the organization.

    6. GL Business Templates and GL MOU Templates approved for national use will be posted on the GLD SharePoint site.

    7. Any changes to the terms or provisions of an approved MOU must be cleared through the impacted OD/FD, HQ GL, Disclosure, and Counsel, at a minimum.

11.4.1.14  (05-17-2011)
Operating or Functional Division Initiated MOUs

  1. When an OD/FD headquarters initiates an MOU, the OD/FD HQ GL analyst will coordinate with OD/FD headquarters staff, Disclosure, and the Counsel GL Coordinator to ensure all items in the GL MOU template are properly addressed.

  2. The HQ GL analyst will coordinate with the field GLs to solicit support for the initiative from their state and local agency stakeholders.

11.4.1.15  (05-17-2011)
Governmental Liaison Program Legal Issues and Counsel

  1. In accordance with the Office of Chief Counsel Notice CC-2009-017, Coordination of Governmental Liaison Issues, dated June 5, 2009, field GLs will contact Associate SB/SE Area Counsel, SB/SE, for legal advice on routine matters relating to GL programs.

  2. HQ GL analysts will request legal advice using the guidelines in Notice CC-2009-017 if a joint initiative or project has national implications or requires advice from an Associate Chief Counsel or Division Counsel HQ office.

  3. According to Notice CC-2009-017, GL will request legal assistance from Chief Counsel whenever the following legal issues need to be addressed.

    1. Information sharing

    2. Appropriate use of government resources

    3. Legal and policy issues arising from GL activities

  4. Notice CC-2009-017 also indicates GL will refer agreements to memorialize joint initiatives or projects activities to Chief Counsel (including MOUs, Letters of Understanding, contracts, etc.) unless the document is a template previously approved by the appropriate Associate Chief Counsel or Division Counsel HQ office.

11.4.1.15.1  (03-01-2007)
Information Sharing

  1. GL initiatives and programs often involve sharing FTI with other federal, state, or local governmental agencies as authorized under the Internal Revenue Code. Many issues can be adequately addressed at the local SB/SE Area Counsel level.

  2. Issues involving interpretation of the Internal Revenue Code and Treasury Regulations and issues involving IRS policy decisions are made at the HQ level, generally involving Division Counsel and/or Chief Counsel.

11.4.1.15.2  (03-01-2007)
Use of Appropriated Funds

  1. The IRS receives appropriations from the U.S. Congress.

    1. It is unlawful to use these funds for purposes other than those for which they were appropriated.

    2. It is unlawful to augment appropriated funds from other sources without statutory authority.

  2. The IRS may not perform state functions, because such activities would be an unlawful use of appropriated funds. The IRS also may not accept funds from states for work performed under GL agreements.

11.4.1.15.3  (03-01-2007)
Inherently Governmental Functions

  1. Certain functions of the federal government may not be performed by anyone other than a federal government employee. Inherently governmental functions are so intimately related to the public interest as to mandate performance only by federal employees requiring exercise of discretion for the government. Examples include, but are not limited to:

    1. Determining correct tax liability

    2. Conducting criminal investigations

  2. State agencies may not carry out activities that are inherently federal governmental functions.

  3. The IRS can use information developed during a state audit in making determinations of federal liability. The advice of Counsel is important when developing these initiatives.

11.4.1.16  (03-01-2007)
Governmental Liaison Counsel Procedures

  1. GLs will follow Counsel procedures in Notice CC-2009-017, which are available electronically at: http://www.irs.gov/pub/irs-ccdm/cc-2009-017.pdf. Counsel Procedures provide guidelines on when and how to request Counsel advice on GL issues. Following the procedures will ensure GL requests contain all of the information required by Counsel before advice can be rendered. The procedures will also filter out requests that can be resolved locally and do not require requesting Associate Chief Counsel involvement.

  2. To provide appropriate oversight and review of GL initiatives in the developmental stages, GL will ensure Counsel involvement in accordance with guidelines in the GL Business Template. The template includes a section for documenting identified legal issues and Counsel's legal advice on any legal issues identified.

11.4.1.17  (07-08-2008)
Governmental Liaison Field Counsel Contacts

  1. The Associate Area Counsel for SB/SE will serve as the GL principal contact point for legal advice. Generally, there is one local SB/SE attorney assigned for each state. Notice CC-2009-017 includes the complete list of Associate Area Counsel contacts by state.

  2. The local attorney will establish a working relationship with the GLD AM. The GL will notify the local Counsel contact if legal advice is needed on a GL initiative, project or matter.

11.4.1.18  (03-01-2007)
Coordination of HQ GL Requests for Legal Advice with Counsel

  1. Novel or significant issues arising in the GL program require coordination within the HQ Office of Chief Counsel.

  2. The Counsel GL Coordinator (CGLC) serves primarily as the liaison between the Office of Chief Counsel and HQ GL. He/she will ensure that policy and legal issues are addressed by the appropriate Counsel field and HQ offices and are brought to the attention of the Chief, GL.

  3. The CGLC will assist in communicating with external stakeholders, coordinating GL training for and by Counsel, coordinating the Counsel response on the legal and policy implications of proposed GL initiatives, and coordinating requests for advice received from HQ GL.

  4. In accordance with Notice CC-2009-017, HQ GL analysts will submit requests to the CGLC for advice on GL matters with national implications, or requiring advice from Associate Chief Counsel or OD/FD Division Counsel, through the Technical Services Section mailbox, "TSS4510@irscounsel.treas.gov," or they may mail requests to 1111 Constitution Ave., NW, Room 5331, Washington, D.C. 20224. Requests may also be faxed to 202-622-4817. All requests will be clearly marked, "GL matter." The telephone number for the Technical Services Section is 202-622-7880.

11.4.1.19  (03-01-2007)
Effective Use of Intranet/Internet Resources

  1. Intranet and Internet access are essential for the GL as primary sources of information, as follows:

    1. The CLD Intranet site contains news items and links to key information at: http://mysbse.web.irs.gov/AboutSBSE/CLD/default.aspx

    2. To ensure awareness of the latest news, GLs should frequently visit the GL Intranet site, which contains GL news items and links to key information and procedures at: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/GL/default.aspx

    3. The SB/SE Outreach Initiatives Database (OID) contains program letters, priorities, Headliners, etc., at: http://mysbse.web.irs.gov/AboutSBSE/CLD/GLD/GL/Programs/CLD/4378.aspx

  2. The CLD Calendar of Events contains scheduled events that are viewable by all employees, but only authorized individuals will be able to add, edit, and delete events. This is a web-based system that is accessible by anyone within the IRS to view planned CLD liaison events throughout the country at: http://sbse.web.irs.gov/cl2/sl/Events_Calendar/default.asp.

  3. The "IMRS" link is to the Issue Management Resolution System main page, where one can search for identified issues and input new issues into the system. There are links to informational items, such as the IMRS Tool Kit, IMRS Decision Tree, and IMRS Guide. The IMRS Guide contains comprehensive information on using IMRS link is at the following web address: http://mysbse.web.irs.gov/AboutSBSE/CLD/SL/IssueManagementResolutionSystemIMRS/default.aspx.

11.4.1.19.1  (05-17-2011)
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 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 CLD 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: http://mysbse.web.irs.gov/AboutSBSE/CLD/Communications/default.aspx

    • Headline News at the following: http://mysbse.web.irs.gov/AboutSBSE/CLD/Communications/Products/HeadlineNews/default.aspx

    • Outreach Initiatives at the following: http://sbse.web.irs.gov/cl2/sl/outreach_initiatives/default.asp

    • SBSE Web Connection at the following: http://mysbse.web.irs.gov/AboutSBSE/CLD/Communications/Products/WebConnection/default.aspx.

    • IRS In the News, which is linked from the News Center in the middle of the IRWeb Home Page under News from the Tax Press and General Press at the following: http://irweb.irs.gov/AboutIRS/Nwsctr/ExtIRSNews/ITN/default.aspx.

  3. Most states, federal, and local agencies currently have available websites. The Federation of Tax Administrators (FTA) is located at the following:


  4. The weekly FTA newsletter distributed electronically by HQ GL contains useful information about matters of interest to the states. The FTA list-serve also contains valuable IRS information.

    Note:

    GLs may cut and paste sections of the newsletter and forward it to other IRS employees who may have an interest in the topic. The entire 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.

11.4.1.19.2  (03-01-2007)
Increasing Governmental Liaison Program Visibility

  1. It is important that the GL program remains visible and shows the value added to the organization, while reinforcing employee roles and responsibilities through regular postings on SB/SE OID and on the SB/SE CLD Calendar of Events, both discussed earlier, as well as on the IRWeb, at: http://irweb.irs.gov/

11.4.1.20  (05-17-2011)
Statistical Data Requests

  1. GLs may receive inquiries about and requests for statistical data from Congressional offices or from other federal, state, or local governmental agencies. GLs will refer to the procedures in Disclosure IRM 11.3.32.21, to advise requesters to make requests to the Statistics of Income Division (SOI) 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: http://www.irs.gov/taxstats.

  3. GLs may refer to SOI IRM 1.13.1.9.2 for additional information about requests for statistical data.

  4. GLs will refer inquiries not resolved above to the appropriate Disclosure Office for assistance.

11.4.1.21  (05-17-2011)
Internal and External Requests for Technical Advice or Assistance

  1. Technical inquiries are received from a variety of external stakeholders and often require a written response to questions regarding tax law provisions, IRS administrative procedures, or IRS policies. GLs research and resolve inquiries when they can, but some of the issues are complex, and technical guidance may be needed from the appropriate OD/FD. The GL will proceed with each OD, with the assistance of HQ GL analysts, as indicated in IRM 11.4.1.21.1 through 11.4.21.4, below.

  2. Requests for assistance are requests that may require the GL, OD/FD, state, federal or local governmental agency to take an action, compile data, gather information, partner in a project, distribute information, etc.

  3. 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 reports, to the Safeguards mailbox, at "SafeguardReports@irs.gov" for direct response by Safeguards. GLs will not attempt to answer questions on behalf of Safeguards.

  4. GL may receive requests for technical and legislative assistance, including requests for IRS testimony or written advice on tax matters, from Congressional or state officials for use in the legislative arena. The Director, LA issued guidance for handling these types of requests in a memorandum, “Providing Technical and Legislative Assistance to State Officials,” dated March 11, 2004. GLs will refer to the LA memorandum for guidance, available at: http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx and should consult with the LA CAP coordinator for further guidance. GL staff will also contact Disclosure and/or refer to Disclosure IRM11.3.35.5(1) for assistance on requests and demands for testimony or for the production of IRS documents.

11.4.1.21.1  (05-17-2011)
Wage and Investment

  1. GL Responsibilities:

    1. Coordinate, as appropriate, local requests for assistance with local W&I staff.

    2. Conduct appropriate research using available resources and respond to or secure information requested and respond to the requester.

    3. Forward unresolved requests to the HQ GL analyst assigned to W& I. The GL will provide his/her research results to the HQ GL analyst to expedite resolving the request for assistance. See the W& I MOU posted on the LA web site at the following: http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx.

  2. Wage and Investment Responsibilities:

    1. Provide subject matter expertise on W&I technical issues and programs to field GLs and HQ GL.

    2. Provide a written response to GLs or to HQ GL, upon request.

  3. HQ GL Responsibilities:

    1. Review requests from the W&I HQ office requesting 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 for appropriate information and respond, if possible.

    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.

11.4.1.21.2  (05-17-2011)
Tax Exempt and Government Entities (TEGE)

  1. GL Responsibilities:

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

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

    3. Forward unresolved requests for assistance to the HQ GL analyst for coordination with HQ TEGE.

  2. TEGE Responsibilities:

    1. Provide support through the TEGE 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 TEGE 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. HQ GL Responsibilities:

    1. Coordinate field GL support for HQ TEGE initiatives and requests involving other federal, state, or local governmental agencies.

    2. Ensure all necessary information is provided to assist the GLs in supporting TEGE 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 TEGE HQ to ensure adequate information is available to facilitate HQ TEGE responses to requests.

11.4.1.21.3  (05-17-2011)
Small Business/Self-Employed Division (SB/SE)

  1. GL Responsibilities

    1. Coordinate the need for technical guidance with the appropriate SB/SE contact from each function (Collection, Examination, Excise, etc.).

    2. Provide formal written responses, as necessary.

    3. Monitor formal written requests submitted to SB/SE to ensure that a timely response is provided to the state, federal or local governmental agency.

    4. Ensure that proper formats are used when formal responses are required.

    5. Sign formal written responses by SB/SE to any state, federal, or local governmental agency.

    6. Elevate issues to the GLD AM 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.

    7. Refer unresolved requests and technical inquiries with national implications to the assigned HQ GL analyst for assistance.

    8. Refer to the SB/SE and LA MOU posted on the LA web site for GL CAP responsibilities, at : http://irweb.irs.gov/AboutIRS/bu/cl/la/lacap/default.aspx.

  2. SB/SE Responsibilities:

    1. SB/SE will assign a liaison from each function in each local office where a GL is located. (Collection, Examination, Specialty Programs, etc.).

    2. SB/SE liaisons will 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. SB/SE will prepare final responses for GL signatures when formal written responses are required.

    4. SB/SE area management will resolve local issues with the GLD AM.

11.4.1.21.4  (03-01-2007)
Large Business and International (LB&I)

  1. GL Responsibilities:

    1. Coordinate appropriate responses to technical inquiries after first reviewing the information on:http://www.irs.gov/businesses/corporations/article/0,,id=152861,00.html.

    2. Send requests to the HQ GL analyst responsible for LB&I (formerly Large and Mid-Size Business (LMSB)) if additional support or assistance is needed or if a formal written response is needed but is not available from the web site.

  2. LB&I Responsibilities:

    1. If formal written technical response is needed, LB&I will coordinate with the HQ GL analyst to provide a response to local GL requests.

  3. HQ GL Responsibilities:

    1. Contact the LB&I to obtain written technical information in those instances where the GL cannot obtain the necessary information from the web site.

    2. Provide responses to the local GLs.

    3. Assist GLs, as necessary. If a formal written technical response is needed, LB&I will coordinate with the HQ GL analyst to provide a response to the local GL request.

11.4.1.22  (05-17-2011)
Disaster and Emergency Situations

  1. In a federally declared disaster and emergency situation the 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/AboutSBSE/CLD/Disaster+Assistance/default.aspx. The HQ 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 the Members of Congress and 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 FEMA to obtain the locations of the Disaster Recovery Centers and coordinate information with the State Disaster Assistance Coordinator (SDAC) in SL, Field.

  4. The GL will consider partnering with state departments of revenue to staff the FEMA Disaster Recovery Centers and will work closely with SL on that aspect of the disaster response.

  5. The GL will inform the Federal Executive Board to facilitate information dissemination.

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

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

11.4.1.23  (07-08-2008)
Requests for Speakers Procedures

  1. Invitations to speak and participate in seminars or meetings are excellent opportunities to inform the public about the IRS, its mission, programs and operations. We must focus our efforts to ensure we are delivering key messages to stakeholders. The IRS strategic plan and the SB/SE business plan will be used to drive decisions on whether to provide speakers.

  2. State departments of revenue, other state and local agencies, and other federal agencies may want IRS speakers for various reasons. Agency 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. On occasion, the agency may be involved in planning an FTA meeting and may need a speaker from an OD/FD HQ offices and/or from IRS senior management or executive staff.

  3. To help achieve the best results for external agency needs, the local GL will follow the procedures below to secure a local speaker upon receiving a request from an external agency: The first step in the process of securing a speaker is to prepare the SL Speaker Request Engagement Form. See Exhibit 11.4.1-6 for the Speakers Request Form, and See Exhibit 11.4.1-7 for the Commissioner Speaker Request Template form.

    1. Requests for SB/SE Speakers. SL HQ established guidelines for processing requests for SB/SE speakers for all SB/SE employees. The SB/SE Speaker Guidelines referenced in IRM 11.53.5.4, SB/SE Speakers Requests, address information gathering requirements and the approval process, as detailed at the following web address:http://mysbse.web.irs.gov/AboutSBSE/CLD/SL/Events/SBSE+Speakers+Campus+Visits+and+Intrnl+Visitors+P/1929.aspx.

    2. Local requests for SB/SE and other OD/FD speakers received by field GLs from external agencies will be processed by the GL, as follows:
      1) The GL will complete the Speaker Request Engagement Form.
      2) The GL will attempt to obtain a speaker through the SRMLC speakers cadre.
      3) If the state/area does not have an SRMLC speakers cadre, the GL will submit the speaker request form to the GLD AM for approval.
      4) After obtaining the AM's approval, the GL will contact local SB/SE management (TM or AM) to attempt to secure a speaker for the agency.
      5) The GL will follow-up until he/she receives the speaker’s name.
      6) The GL will provide the name of the speaker to the requesting agency.
      7) If the local GL is unable to secure an SB/SE speaker locally, he/she will forward the approved Speaker Request Engagement Form to the HQ GL Speaker Request Coordinator (SRC) for further processing assistance.
      8) The HQ GL SRC will review and perfect approved requests, as necessary, and will forward them to the SB/SE SRC for further processing assistance.

    3. Requests for SB/SE HQ and Executive Level Speakers. Requests received by the local GL for SB/SE HQ and executive speakers, including requests for the SB/SE Commissioner or Deputy Commissioner, other SB/SE leadership, the Office of Professional Responsibility (OPR), or the IRS Commissioner or Deputy Commissioners, will be forwarded to the HQ GL SRC upon approval by the GLD AM. The HQ GL SRC will review and perfect approved requests, as necessary, and will forward them to the SB/SE SRC for further processing assistance.

    4. Requests Received by HQ GL Analysts.
      1) HQ GL analysts who receive external requests for SB/SE speakers will forward the completed Speaker Request Engagement Form to the HQ GL SRC. The HQ GL SRC will review and perfect approved requests, as necessary, and will forward them to the SB/SE SRC for further processing assistance.
      2) HQ GL analysts who receive external requests for speakers from the ODs/FDs they support (other than SB/SE) will attempt to secure the requested speaker directly from the OD/FD and will advise the requester of the results of his/her efforts.
      3) HQ GL analysts who receive speaker requests pertaining to other ODs/FDs (other than SB/SE) will refer them to the appropriate HQ GL analyst for action.
      4) If the HQ GL analyst is unable to secure the requested speaker, he/she may request the assistance of the HQ GL SRC.

    5. The HQ GL SRC will:
      1) Review all speaker requests referred from field GLs and from HQ GL analysts for appropriate content and completeness.
      2) Coordinate further processing of appropriate speaker requests with the SB/SE HQ Speaker Request Coordinator, other HQ GL analysts, and other OD/FD contacts, as necessary.
      3) Forward the speaker information back to the requesting local GL or HQ GL analyst within 15 business days.
      4) Provide status updates every 15 days until a speaker is confirmed or the request is declined.

11.4.1.24  (05-17-2011)
Visits by Foreign Tax Officials

  1. Detailed information on the International Visitor’s Program (IVP) may be found in IRM 4.62.1.6.

  2. The IVP provides foreign officials with opportunities for discussion with IRS officials and observation of IRS operations. Depending on the content of the program, the visit may be held at the IRS headquarters office, a field office, or a campus site. The Chief, GL or the local GL may be asked to either support a program as a speaker or to secure a speaker from a state tax office.

  3. Requests are received from a variety of sources, most generally from the following:

    1. IRS Tax Attaché

    2. Foreign Government Embassies in Washington, DC

    3. Department of State

    4. The World Bank

    5. The United Nations

    6. Foreign Government Officials

    7. Private Organizations and Lobbyists on Behalf of Government Officials

    8. Department of Homeland Security

  4. All applicants must complete the International Visitors Program Application, which may be obtained at Exhibit 11.4.1-8 and at the following site:
    http://www.irs.gov/businesses/international/article/0,,id=97068,00.html
    Completed IVP applications will be sent via e-mail to the Manager, IRS International Visitors Program or by fax to (202) 283-8571. Applicants with questions regarding the program should call 202-283-8491, 8588, or 8445.

    1. General Information Briefings. Meetings will usually be informal and will consist of oral briefings and discussions on agreed-upon issues identified on the incoming request. Briefings will generally be held at the Office of the Deputy Commissioner, International, LB&I, 799 9th Street, NW, Washington, DC.

    2. Background Country Information. Background information about the visitors' country will generally be forwarded to the contact person, except for countries whose tax administration systems are similar to that of the IRS and countries with recurring visits, such as Canada, Australia, New Zealand, and the United Kingdom.

    If the presenter requires additional background/tax system information on the foreign country, the IVP office should be notified. This information is readily available on the Internet.

Exhibit 11.4.1-1 
HQ GL Communiqué Template

HQ GL Communiqué Template
  Date:
Subject:
IRS  
COMMUNICATION FOR AMS/GLS
Office of the Chief, Governmental Liaison
  Information Only
Action Required by Date
TA (Consolidated Area Response Required)
Issue:
(Insert subject here)
 
   
Background:
(Insert background details here)
 
   
Message for State Agencies (or other external customers):
(Insert message here)
 
   
Required GL Actions:
Insert GL Actions here)
 
   
HQ GL Contact:
Name __
Phone Number __
 
   
Other OD Contact (if applicable):
Name __
Phone Number __
 
   
EM2go (if needed):  
Open the EM2go envelope, insert the "To" information and your signature, select "Actions" from the top line menu, then select "Forward " . The "Send" button will come alive for you to send the message. Sample:
Subject: Message for Stakeholder  
Insert message to stakeholders created by HQ GL analyst for GLs to send to the field.
GL Name
GL Phone number
 
   
Attachments (if needed):
(Insert attachments here)
 
   
Legislative Affairs (if Needed):
(Insert Legislative Affairs message here with two statements below)
 
   
*This message was developed in coordination with Legislative Affairs*
If you have any questions, contact Eric Hall (LA) at (202) 622-4057 or Name (HQ GL) at number.
   
Perry Castellani
Chief, GL
212-719-8234
 
   

Note:

This document was written for, and addressed to, IRS personnel. This communication was not formatted for external audiences.

Exhibit 11.4.1-2 
Message Template

Message Template
Insert the write up for topic using the following format.

Address each boldfaced topic, as appropriate. See accompanying example.


Topic: (ex: Bank Secrecy Act)

Category: (Choose one from the following: General or Examination or Collection, Specialty or Campus Compliance Services or Fraud/BSA or Burden Reduction, or Communications Liaison & Disclosure)

Target Audience: (Brief Bullet Format)

Message Delivery:(ex: Filing Season, Summer, Ongoing, etc.)

Outreach Products & Supporting Documents: (Title & internet resource link)

Contact:(Your name, phone number and e-mail address)

Revised date: (Date this template is created – month, year) Key Messages: (Text – one or two line abstract is okay, and bullet the rest of the key messages. Ideally this can be condensed to a page or so, but the point is to state the executive highlights. Details can be left to the supporting documents in the Outreach Products & Supporting Documents section.

If you have any questions, call Insert Name & Telephone Number.

Note:

No need to try to format styles. Text only is fine.

Exhibit 11.4.1-3 
GL/SL Stakeholders Chart

SL Stakeholders GL Stakeholders SL-GL Joint Potential
Practitioner associations (APA, Tax Forums, TPI)   • GL may assist with getting state agency input as needed for forums, etc. SL may get 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)   • SL works with SBA/SCORE and related agencies to provide outreach and information to practitioners, though SBA as a governmental agency is a GL primary stakeholder.
• GL may work with SL and SBA on a "Government Fair" one-stop outreach with practitioners, agencies and Congressional staff to reach mutual taxpayer customers.
Individual practitioners    
Universities    
Banking institutions and credit unions    
  Congressional offices/ delegations • SL can provide information or briefing for Congressional-IRS seminars.
• GL can share SL products and messages with Congressional staff.
  All Federal agencies (SBA/Score, FEMA, SSA, Department of. Homeland Security) •CLD is the primary IRS contact for disaster assistance. GL contacts FEMA to coordinate between IRS and FEMA. SL ultimately provides the field support role with FEMA and taxpayers. GL assists when needed, and keeps Congressional staff informed of IRS relief efforts.
• SL has an ongoing relationship with SBA to leverage resources for outreach to practitioner and small business organizations.
• SL writes the IRS portion of the "SSA Reporter" . GLs receive this document to 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  
  Federal Tax Administrators  
CLD, OD/FDs    

Exhibit 11.4.1-4 
GL Business Template

GL Business Template
Use check box 0x2713 to indicate which part(s) applies
The Governmental Liaison (GL) Business Template is a tool used to establish a business case for proposed joint initiatives with state and local governments, and federal agencies. The template is a guide to ensure that joint initiatives support IRS business objectives and/or key stakeholder objectives and that key issues are identified and addressed in developing proposed initiatives


Benefits of Preparing a GL Business Template:

• Brings attention to local initiatives/new ideas
• Provides a structured approach to initiative development
• Ensures key issues will be considered
• Uses standardized procedures/consistent information
• Avoids duplication/reinvention of the wheel
• Encourages sharing of ideas
• Improves documentation for reviewers/approvers

All new local initiatives or proposed initiatives (either intended for local, area, or national implementation) should be submitted by using the GLD Business Template, unless one or more of the following exceptions apply:

Exceptions to preparing a GL Business Template:

1. Routine activities requiring only local approval, e.g. joint forms availability at mutual sites; joint filing season publicity, joint committees, conferences, workshops, training, etc.)
2. Replicating a previously approved GL initiative template without substantial changes
3. Exchanges of or access to information covered by an existing Implementing Agreement or Memorandum of Understanding (MOU).

Confer with your GLD Area Manager if you are unsure if a Template should be prepared.

To use the template, check Parts A, B or C, as appropriate, and submit the completed document to the Headquarters Office of the Chief, Governmental Liaison through your GLD Area Manager.

Part A: Complete Part A when developing a local initiative or making a successful local initiative available for broader implementation. An example of a "Part A" initiative is a special taxpayer assistance day. A special taxpayer assistance cadre of IRS employees established in partnership with practitioner organizations and the state and/or local income taxation authority would be available to provide help to victims of a flood, hurricane, tornado or other local disaster. Special taxpayer assistance events would offer free advice and assistance with tax responsibilities and/or claims when necessary. State and/or local governmental representatives would be invited to participate in the publicity and/or attend the event.

0x2713 Part B: Complete Part B in addition to Part A to address resource impact, disclosure, legal, union/labor relations, and coordination issues, as well as when a proposed initiative must be reviewed at the Operating Division level and may require testing before it is approved. Following are some situations where Part B of the template should be completed:

• To propose establishment of new data exchanges or propose new approaches to utilizing data provided through existing exchanges (Ex: State RAR exchange)
• To conduct joint compliance activities with an external agency (Ex: Joint Installment Agreements)
• To perform matches of IRS and external agency databases (Ex: Reverse Filing Match)
• To implement an initiative that requires the development of a CIP or a Privacy Impact Statement (Consult with the local DM)
• To develop an initiative that may significantly revise existing procedures or working conditions, thereby requiring consultation with NTEU

0x2713 Part C: Use Part C as the template for a Memorandum of Understanding (MOU) when an MOU is required to formalize procedures, costs, and responsibilities between participating agencies. (To determine who should sign an MOU, refer to the "Governmental Liaison/GL Initiative MOU Approval Chart" ).
PART A  
   
Complete all sections. Indicate "N/A" if not applicable; other options are "Not avail." Or "To be Determined" (TBD) if the information is not known at the time.

Note:

These italicized instructions should be deleted when you submit the template.

I. Initiative Title:
II. Date:(initial submission date and revision date if applicable)
III. Originating Office:
IV. IRS Contacts:
• GL:
• Operating/Functional Division (OD/FD):
V. Business Owner:(GL, OD, FD or joint)
VI. IRS Strategic Business Objective(s) Supported:(service to each taxpayer, service to all taxpayers, increase productivity through a quality work environment)
VII. Participating Agency(s):
VII. Background:(include reason initiative selected for development, existing circumstances needing change or improvement and objectives of initiative)
IX. Description of Initiative::(how initiative works [flowchart process as appropriate], and, as appropriate, identify audience and plans to market initiative internally and externally)
X. IRS Business Measures:(specific criteria, data and methodology to measure customer satisfaction, employee satisfaction and business results)
XI. Benefits/Savings/Expected Results:(tangible and intangible benefits and savings such as labor cost savings or cost avoidance [e.g., not having to hire additional staff] and non-labor cost savings or cost avoidance [e.g., upgrading/replacing existing facilities/equipment and interest savings])
IRS:
Partnering Agency(s):
Taxpayers:
PART B  
   
Complete all sections that apply to the extent possible. Provide all necessary available information, identify issues, and make recommendations as appropriate for each section. Attach documentation as needed. Indicate "N/A" if not applicable; other options are "Not Avail." or "To be Determined" (TBD) if the information is not known at the time.

Note:

These italicized instructions should be deleted when you submit the template.

   
XII. Resource Requirements:(programming, software development, data entry, space design, consultant fees, training, travel, hardware/equipment, furniture, publishing costs, etc. - itemize all costs, differentiate costs as applicable)
Developmental Costs:
Implementation Costs:
On-going Operational Costs:(additional programming, software maintenance and upgrades, travel, additional staff hours, telecommunications costs, rent, etc.)
XIII. Internal or external coordination/agreements:(impact on other functions; existing applicable agreement(s); are MOU, CIP, 6103(n) contract or other agreements needed?)
Technical Advice:
Memorandum of Understanding (MOU):
Compliance Initiative Project (CIP) (IRM 4.17.1):
Privacy Impact Statement (IRM 11.3.14.12.3):
XIV. NTEU/Labor Relations Issues:(change in bargaining unit working conditions, Section 7114 meetings, Labor Relations Issues, NTEU [local or National] Agreement)
XV. Legal, Disclosure, Privacy, and Security Issues:
Counsel Advice
Local Counsel:(if MOU required, must be sent to local counsel)
Headquarters Counsel:
Disclosure Advice:(IRC §6103, need and use)
Privacy Act Impact Assessment:(Office of Privacy, Information Protection, and Data Security (PIPDS))
Safeguard Issues:(Office of Safeguards)
Physical Security:(IRS Office of Physical Security and Emergency Preparedness (PSEP))
XVI. IS System Certification:(Required? – if so, was it requested or obtained?)
XVII. Pilot/Testing and/or Training Issues:
XVIII. Policy Issues:(policy issues and implications; consultation with field and HQ personnel as appropriate)
IRM Deviations:
IRM Revisions:
Regulations or Law Changes:
XIX. Conclusion:(summarize initiative results and any recommendations)

Exhibit 11.4.1-5 
GL MOU Template

MEMORANDUM OF UNDERSTANDING BETWEEN THE INTERNAL REVENUE SERVICE AND THE [ NAME OF AGENCY]
 
1. INTRODUCTION:
 
This Memorandum of Understanding (MOU) between the Internal Revenue Service (IRS) and [insert name of state or local agency] sets forth the agreement of the parties with respect to an initiative to
 
2. AUTHORITY:
 
This MOU is entered into between the IRS and the Agency pursuant to Internal Revenue Code Section This MOU is supported by [insert Basic or Implementing Agreement as appropriate.]
 
3. PURPOSE:
 
The purpose of this initiative is to
 
4. DUTIES AND RESPONSIBILITIES OF THE IRS:
 
The IRS will
 
5. DUTIES AND RESPONSIBILITIES OF THE AGENCY:
 
The Agency will
 
6. DISCLOSURE, SAFEGUARDS, AND RECORD KEEPING REQUIREMENTS: (If the MOU involves FTI, this section would be included):
 
A. The Agency will maintain Federal tax returns and return information separately from other information to the maximum extent possible to avoid inadvertent disclosures and to comply with the federal safeguards required by IRC §6103(p)(4). The agency will also abide by all other requirements of IRC §6103(p)(4).
B. All information obtained under this MOU must be safeguarded in accordance with the Basic Agreement, the Implementing Agreement, as well as the safeguard requirements of IRC §6103(p)(4), as described in IRS Publication 1075, Tax Information Security Guidelines for Federal, State, and Local Agencies and Entities.
C. The [Title of the IRS person responsible for record keeping and accounting ] will ensure that all requirements for recordkeeping and accounting for disclosures are met in accordance with IRC §6103(p)(3) and its implementing regulations.
D. List any other disclosure guidance applicable to the MOU (i.e., non-disclosure of information protected by governmental, attorney/client privilege, or attorney work product privileges consistent with applicable laws, or any other information that is prohibited from disclosure--IRM 11.3.32.17; non-disclosure of return information that would identify a confidential informant or seriously impair any civil or criminal tax investigation; etc.)
 
7. TRANSMITTAL PROCEDURES: (If the MOU involves FTI, this section would be included):
 
A. All information exchanged will include a Document Transmittal, (Form 3210 or equivalent) or other means of verifying receipt with a count of documents by type and a brief description of the information being provided.
B. The Document Transmittal and documents will be inserted in an envelope marked "TO BE OPENED BY ADDRESSEE ONLY" and inscribed with the name of the official designated to receive the information. The package will be hand delivered to the designated official or mailed via the United States Postal Service, Federal Express, United Parcel Service, or a Federally accredited expedited mail delivery service, in a second envelope inscribed with the address of the designated official.
 
8. LIABILITY:
 
A. Each party to this Agreement shall be liable for the acts and omissions of its own employees.
B. The IRS shall not be liable for any injury to another party’s personnel or damage to another party’s property unless such injury or damage is compensable under the Federal Tort Claims Act [28 U.S.C. 1346(b)], or pursuant to other Federal statutory authority. Similarly, the Agency shall not be liable for any injury to another party’s personnel or damage to another party’s property unless such injury or damage is compensable under applicable state or local law.
 
9. THIRD PARTY RIGHTS:
 
This MOU does not confer any rights or benefits on any third party.
 
10. PRIVACY:
 
The IRS and the Agency will assure the integrity and accuracy of personal and financial data. The IRS and the Agency will perform their duties in a manner that recognizes and enhances individuals’ rights of privacy and will make certain that their activities are consistent with law, regulations and good administrative practices.
 
11. EFFECTIVE DATE:
 
The effective date of this MOU is the date it has been signed by all parties to the Agreement.
 
12. AMENDMENT OF MOU:
 
This MOU may be amended by deletion or modification of any provisions, provided that such amendment is in writing and is signed by all parties to the MOU.
 
13. TERMINATION OF MOU:
 
This MOU may be cancelled upon [agreed-upon number] days written notice by either the IRS or the Agency or immediately by signed agreement of the IRS and the Agency.
 
14. LIMITATIONS:
 
The terms of this MOU are not intended to alter, amend, or rescind any current agreement or provision of federal law now in effect. Any provision of this MOU which conflicts with federal law will be null and void.
 
15. EVALUATION OF DATA EXCHANGE: (Use this wording if it is a data exchange type MOU)
 
The IRS and the Agency will review this MOU annually to evaluate the existing data exchange, examine the continuing needs for and uses of the exchanged data, and determine whether the provisions of this agreement require amendment or revision. The method of review (conference call, meeting, e-mail) will be jointly determined by the IRS Governmental Liaison, Office of Safeguards, Business Operating Division, and the Agency Liaison.
 
16. EVALUATION OF AGREEMENT: (Use this wording if it is a Customer Service type MOU)
 
The IRS and the Agency will review this MOU annually to determine whether the provisions of this Agreement require amendment or revision and whether the [Agency is/Agencies are] complying with the provisions of the Agreement. The method of review (conference call, meeting, e-mail) will be jointly determined by the IRS Governmental Liaison, Business Operating Division, and the Agency Liaison.
 
APPROVALS:
 
INTERNAL REVENUE SERVICE
 
Signature
 
Title (OD/FD) Division Commissioner or individual delegated authority to sign MOUs)
 
Date
 
STATE OF [Name of State]
Agency [Name of Agency]
 
Signature
 
Title (Head of Agency)
 
Date
 

Exhibit 11.4.1-6 
SL/GL Speaker Request Engagement Form

Stakeholder Liaison/Governmental Liaison Speaker Request Engagement Form
Please review the Speaker Request Guidelines for Stakeholder Liaison or Governmental Liaison for your function before completing this form.
 
SL HQ Speaker Request Coordinator: Sharon Medley, (202) 283-2634
GL HQ Speaker Request Coordinator: Al Adams, (410) 962-9093
 
Date:
 
Request submitted by:
Title/Position:
Contact Information:
 
Type of speaker requested (executive, subject matter expert – if specific individual requested, name the individual and their title/position):
 
*Organization requesting speaker:
(*Note: If this is an international request, please follow International Visitors Program guidelines at the following: http://www.irs.gov/businesses/international/article/0,,id=96177,00.html. If this is a state or federal agency refer request to local GL.)
 
Event name/Title:
 
Date of speaking engagement:
 
Location, with address:
 
Time of speaking engagement:
 
Length of speech (30, 60, 90 minutes):
 
Topic(s) for speech, requested by organization:
 
Format (keynote, solo presenter, panel, luncheon speaker etc.):
 
Describe the audience and provide estimated size (practitioners, business owners, etc.):
 
Purpose of the presentation (how it aligns with strategic goals/initiatives):
 
Opportunities to deliver service-wide messages (if yes, please describe):
 
What, if any, fee is paid by the participants attending the event?
If yes, is it consistent with the cost for similar events?
 
Will external media be present?
If yes, provide a list:
 
Are there any prohibitions for attending the event?
 
Agree with recommendation:
________________________________________
Area Manager
Date:
 
Approved:
___________________________________________
Director, Stakeholder Liaison HQ or Chief, Governmental Liaison
Date:
 
For HQ use only:
Speaker Approval/Assignment Status
 
HQ analyst will provide status to requesting office every 10 days.
 
Date request made to function:
 
Follow up status:
 

Exhibit 11.4.1-7 
Commissioner Speaker Request Template

REQUEST FOR COMMISSIONER SPEAKING ENGAGEMENT
 
ACTIVITY:
 
DATE/TIME:
 
LOCATION:
 
PURPOSE:
 
PARTICIPANTS:
 
CONTACT:
 
COMMENTS:
 
RECOMMENDATIONS:
 
DECISION:
 

Exhibit 11.4.1-8 
International Visitors Program Request Form

International Visitors Program Request Form
 
For further information see the IRS web site at the following:
http://www.irs.gov/businesses/international/article/0,,id=96177,00.html and IRM 4.62.1.6TAAS International Visitor’s Program (IVP)
Application Details
Please provide the following information
Name of person requesting the visit:
Requesting governmental department/organization:
Mailing address: Telephone number(include country and city codes):
Fax number:
E-mail address:
Date(s) visit requested:
Alternate date(s):
Number of visitors:
Will an interpreter accompany the participant(s)?
Yes _______ No _______
(Note: IRS cannot provide or arrange for interpreters.)
Purpose of Visit:
Give a brief explanation of how you believe the briefing will benefit your tax administration/governmental department:
LIST OF PARTICIPANTS
Head of Delegation Name:
Position/Title:
Education (i.e., specific colleges/universities):
Recent employment history(current position and last two positions held):
Language proficiency:
Other Members of Delegation
Please provide the same information listed above for other members of the delegation

Note:

Only name and title are required for any interpreter(s) or escort(s) who may accompany the delegation.

TOPICS REQUESTED
(Please limit request to 3 topics per day.)
We are better able to arrange for the appropriate technical and administrative presentations if we have a good understanding of the specific questions you would like discussed. Additionally, the IRS reorganization resulted in many functional and operational divisions being relocated outside of Washington, DC, therefore some travel may be required to receive briefings.
As you list your topics and questions, please indicate who the eventual audience will be when you return to your home country; i.e., with which group of taxpayers/customers will you share the information you learn during your visit?
TOPIC 1:
List specific questions.
TOPIC 2:
List specific questions.
TOPIC 3:
List specific questions.

Exhibit 11.4.1-9 
Safeguard Procedures Report Certification

Safeguard Procedures Report (SPR) Certification
Part 1
New IRS data requested (e.g., extract, Memorandum of Understanding(MOU), on-line access) or process change in receipt of data (e.g., Secure Data Transfer (SDT) (Provide specific description of data or process change)

• Please read Parts 2-4 below and check the box that describes your situation relative to the information in Part 1
• The agency head must sign/date this certification in Part 5 and return it to the Governmental Liaison along with the signed requesting document (e.g., MOU, GLDEP Enrollment Form), if applicable.
Part 2
My agency does not have a current, approved SPR (approved within the last six years). We agree that we will not receive Federal Tax Information (FTI) until we have an approved SPR.
Part 3
Our current, approved SPR does not include procedures to safeguard the FTI identified in Part 1. We agree that we will not receive the FTI identified in Part 1 until we have an approved addendum to our SPR.
Part 4
Our current, approved SPR includes procedures to safeguard the FTI identified in Part 1. We can receive this FTI.
Part 5 - Agency Head Certification
I acknowledge that the data identified in Part 1 and received from the IRS is FTI that must be safeguarded at all times in accordance with 26 USC 6103(p)(4) and the guidelines described in Publication 1075. I further acknowledge that FTI is to be used only in accordance with the provisions of IRC §6103(d) for the purpose of, and to the extent necessary, in state tax administration.
Signature:
Title:______ Agency Name:____
Agency Code:__
Date:__
Agency POC Information
Name:
Phone:
E-mail:
Instructions/Information
• The agency provides the signed certification to the Governmental Liaison, who will review and forward it to the Office of Safeguards either electronically to SafeguardReports@irs.gov ("Safeguard Procedures Report Certification" in the subject line) or by fax to 202-622-4274.
• The agency should follow the procedures outlined in Section 7 of Publication 1075, Tax Information Security Guidelines for Federal, State and Local Agencies, for submission of the SPR.
• The agency may secure a copy of the SPR template by e-mailing SafeguardReports@irs.gov or by downloading from the Safeguards IRS.gov web site. The template must remain as a Word document when it is completed.
• The agency must submit the SPR, along with the transmittal letter and any attachments, electronically to the SafeguardReports@irs.gov mailbox, using approved encryption techniques and the standard Safeguards password.
• If an SPR addendum is required, the agency must complete the SPR template specific to the process, procedures, and systems that will be employed to safeguard the FTI identified in Part 1. If a specific question on the SPR template does not apply, insert "N/A."
• Information is available on the Safeguards IRS.gov web site to assist you, including a sample SPR template. To access the IRS.gov Safeguards site, enter "Safeguards Program" in the search box on the top right corner of the IRS.gov web site. Click on the search result that says "Safeguards Program."
IRS Office of Safeguards Use Only

Concur
Do Not Concur
SPR Approval Date:
Comments:
Certification Review Date:

Exhibit 11.4.1-10 
Glossary of Governmental Liaison Terms

Glossary of Governmental Liaison Terms
AMs Area Managers
APA American Payroll Association
ATAT Abusive Tax Avoidance Transactions
BSA Bank Secrecy Act
CAP Congressional Affairs Program
CAS Customer Account Service
CGLC Counsel Governmental Liaison Coordinator
CIP Compliance Initiative Project
CLD Communications, Liaison, and Disclosure
CLE Continuing Legal Education
CPE Continuing Professional Education
CSS Customer Service Strategy
DMs Disclosure Managers
DHS Department of Homeland Security
ERO Electronic Return Originator
ESP Employee Suggestion Program
FEA Federal Executive Association
FISMA Federal Information Security Management Act
FMS Financial Management Service
FSLG Unit within TEGE - Federal, State, and Local Governments
FS Filing Season
FTA Federation of Tax Administrators
FTI Federal Tax Information
GL Governmental Liaisons
GLD Governmental Liaison and Disclosure
GLDEP Governmental Liaison Data Exchange Program
HQ Headquarters
HQ GL Headquarters, Governmental Liaison
IMRS Issue Management Resolution System
IRC Internal Revenue Code
IRS Internal Revenue Service
ISA Interconnection Security Agreement
IVP International Visitor’s Program
LB&I Large Business and International
LTA Local Taxpayer Advocate
MACS Midwest Automated Compliance System
MOA Memorandum of Agreement
MOU Memorandums of Understanding
MTA Multi-State Tax Commission
N/A Not Applicable
NIST National Institute of Standards & Technology
NRP National Research Program
NTEU National Treasury Employees Union
OD/FD Operating and Functional Division
PIPDS Office of Privacy, Information, Protection, and Data Security
QETP Questionable Employment Tax Project
RAR Revenue Agents Report
RITA Regional Income Tax Agency
SBA Small Business Association
SB/SE Small Business and Self-Employed
SCORE Service Corp. of Retired Executives
SDAC State Disaster Assistance Coordinator
SITLP State Income Tax Levy Program
SL Stakeholder Liaison
SOI Statistics of Income
SRFMI State Reverse File Matching Initiative
SRM Strategic Relationship Management
SRMLCs Stakeholder Relationship Management Local Councils
SSA Social Security Administration
SWAs State Workforce Agencies
TAC Taxpayer Assistance Center
TAMIS Taxpayer Advocate Management Information System
TAX Taxpayer Advocate Service
TBD To Be Determined
TDS Transcript Delivery System
TEGE Tax Exempt and Governmental Entities
TPI Tax Practitioner Institute
W&I Wage & Investment

More Internal Revenue Manual