4.24.18 Excise Operations Support

Manual Transmittal

April 09, 2014


(1) Updated IRM. This transmits updated IRM 4.24.18, Excise Tax, Excise Operations Support.

Material Changes

(1) Updates made to the way inventory is controlled, classified and delivered to field.

(2) Removed content relating to exam case feedback formerly at

(3) Remaining cites were renumbered and updated as needed to add clarity. Hyperlinks and IRM cites also updated. The Table below lists the 6-14-2012 IRM cites and changes made to this revision.

IRM Subsection Number Nature of Change Excise Operations Support (EOS) Overview No changes. Overview of the JOC No changes. Role of PSP WIC No changes. EOS Compliance Initiatives and Charters No changes. Coordination of Approved Compliance Initiatives No Changes. Charter Compliance Initiatives and SBSE Compliance Initiative Projects (CIPs) No Changes. Return Preparer Program Added new (1) regarding the Return Preparer Coordinator Position. The EOS Inventory System No changes. Types of Leads No changes. Initiative Leads Made minor edits to add clarity. Priority Leads Remove Project Code for Informant Leads cases. Remove 2 days turnaround requirement. Claims Leads Added new Push Code 51 procedures for paid claims where no return filed. Fed/State Agreement and State RAR Leads No changes. Specialist Referral System (SRS) Leads Minor edits for clarity. Other Leads No Changes. EOS Group Mailbox Receipt Leads Minor edits and updated titles for clarity. Added new Request for Information forms be sent to mailbox. Form 5346, Examination Information Report Added new requirements for leads to be uploaded to IMS. Added requirements for non-excise leads be routed to EOS for processing. Made edits for clarity. Headquarters (HQ) Excise Staff Requests Eliminated need for formal charter. Data and Assistance Requests Added new Request for Information (RFI) form and edited procedures for clarity. Income/Employment Tax Referrals Content modified and moved to and (10). Referrals now routed directly to EOS. Other Leads Deleted as not required. Processing New Leads from Inventory Minor edits for clarity. Updated IRM cites. Validating Entity Information Minor edits for clarity. Matching Leads to Other Data Minor edits for clarity. Prioritizing Leads Updated (3) to remove reference to electronic spreadsheet or paper leads.
NEW Reopening Previously Examined and Closed Case Added procedures and references. Overview of Workload Classification Minor edits for clarity. Classification Dispositions Updated Forward leads IMS procedures. Joint Audits with States Minor edits for clarity. State-Only Audits No changes. Research for Classification of Leads No changes. CIC No changes. ERCS Status Updated to include IMS control procedures. Audit History/Prior Classification Dispositions Clarified procedures and eliminate need to review IMS file. Related Entities Information No changes. Other Research Information No changes. Substantial Non-Compliance Factors (SNiF) Criteria Minor edit for clarity. Reopening Previously Examined and Closed Case No changes. Documenting Classification Dispositions on the Classification Checksheet Minor edits for clarity. Case Coding Procedures Update source codes above 44 and status code 99 in table. ERCS/AIMS Controls Procedures Update to incorporate IMS case control procedures. Coordination of Case Controls-Multiple Employee Assignments No changes. Managing Inventory Update to include IMS procedures and create new tables . Work Order Request Tracking System (WORTS) Update to remove E case and paper file requirement. Casebuilding Update to remove E case file requirement. Correspondence Audits No changes. Overview of Disclosures of Federal Tax Information (FTI) No changes. Guidance on Disclosures of Federal Tax Information to Non-Participating and Participating State Partners Minor edit for clarity. Disclosures of FTI to Non-Participating and Participating State Partners with Taxpayer Consent 00 No changes. Disclosures of FTI to Non-Participating State Partners No changes. Disclosures of FTI to Participating State Partner Non-JOC Employees No changes. Disclosures of FTI to Participating State Partner JOC Employees No changes. Disclosure Accounting Package No changes. Instructions for Completion of Form 5466-B No changes. Narrative Accounting for Disclosure Updated name and address to whom memo is to be forwarded. Instructions for Completion of Form 3210 No changes. Release of Information No changes. Disclosure Scenarios No changes. Unauthorized Disclosures No changes. Overview of EOS Quality Review Minor edits for clarity. Quality Review of Leads Classification Minor edits for clarity and remove requirement for completion of Form 5126. Quality Review of Data Used in EOS Initiatives No changes. Exam Case Feedback Deleted as not needed since feedback embedded into IMS. Manager/Employee Security Responsibilities for NDC Information Moved to 4.24.13. Minor edit for clarity. Data Transfers to and from the NDC Moved to JOC Partner Administrative Processes Moved to 4.24.14. New Partner Requirements Moved to Partnership Coordination with Privacy, Governmental Liaison, and Disclosure Office (PGLD) Moved to 4.24.14. Minor edits for clarity. State Partner Disclosure Requirements Moved to State Partner Safeguards Requirements Moved to EOS Shared Site Moved to 4.24.15. Edit list of items available on shared site. EOS Program Monitoring Moved to 4.24.16. Minor edits for clarity.

Effect on Other Documents

This material supersedes IRM 4.24.18, dated 6-14-2012. The following Interim Guidance memo has been incorporated into this IRM section; SBSE 04-0813-0070, dated 8-29-2013, Completion of Excise Lead Feedback Form.


This section is for SBSE Excise Managers, Examiners, and Specialists.

Effective Date


/s/ John Imhoff
Director, Specialty Programs
Small Business / Self Employed

Excise Operations Support (EOS) Overview

  1. Excise Operations Support (EOS) promotes collaboration and innovation to develop effective excise tax compliance strategies to support field compliance operations. EOS employs state-of-the-art technology to:

    1. conduct insightful analysis on internal and external data about the excise tax population and

    2. to assess the impact of trends and legislative proposals on excise program.

  2. EOS activities include:

    1. Planning, monitoring, selecting, and assigning excise tax workload for examination.

    2. Identifying new compliance initiatives and reviewing existing initiatives for continuance.

    3. Conducting data analysis to identify and develop compliance anomalies as case leads.

    4. Coordinating case building for selected leads.

    5. Developing case background information and instructions for related compliance activities.

    6. Ensuring establishment case controls and delivery workload to the field.

    7. Monitoring inventory requisitions.

    8. Supporting field compliance activities.

    9. Classifying case leads.

  3. EOS consists of two main groups:

    1. Joint Operations Center (JOC) and the National Data Center (NDC), and

    2. Planning and Special Programs Workload Identification and Classification (PSP WIC).

    Both groups collaborate to identify and deliver appropriate excise tax related compliance workload. Both groups work to address Policy Statement P-4-21 which states, "The primary objective in selecting returns for examination is to promote the highest degree of voluntary compliance on the part of taxpayers."

Overview of the JOC

  1. The JOC is a partnership between federal and state motor fuel taxing authorities. Its mission is to:

    • Enable state and federal motor fuel tax compliance activities.

    • Foster interagency and multi-national cooperation.

    • Provide strategic analyses of domestic and foreign motor fuel distribution trends and patterns.

  2. The JOC creates a technical foundation for a common excise tax data repository. It provides for the innovative use of technology to:

    • Collect, analyze, and share information to facilitate the access of real-time and historical tracking of fuel movement and fuel supply chain dynamics.

    • Develop and depicts trends and anomalies to establish situational awareness over the national fuel marketplace and supply chain.

    • Investigate anomalous behavior to identify leads for excise compliance follow-up activity.

  3. The JOC National Data Center (NDC) identifies, acquires, and integrates federal, state, and other commercial third party data sources that bear on the national fuel inventory. Compiled data is used to track and trend fuel movement for the purpose of:

    • Developing improved baselines for measuring fuel supply, distribution, and consumption.

    • Enabling the JOC to identify suspicious activities and tax evasion schemes using data mining technologies, predictive analytic technology, link analysis tools, and other forensic type tools and techniques identified as appropriate for JOC purposes.

    • Performing analysis using economic indicators.

    • Demonstrating the benefits of enhanced contributions to the Highway Trust Fund and the economic benefits to participating states.

    • Identifying additional information for distribution of Highway Trust Fund receipts to the states.

    • Identifying areas resistant to compliance that require systemic or legislative changes.

    • Using its tools and resources to identify leads for tax law compliance activities.

Role of PSP WIC

  1. PSP WIC is responsible for:

    • Identifying and developing field examination leads.

    • Classifying field leads.

    • Selecting workload for field operations based on examination potential.

    • Coordinating the case building, case control, and delivery of workload to the field.

    • Monitoring inventory requisitions.

EOS Compliance Initiatives and Charters

  1. EOS compliance activities generally begin with the development of a charter. Charters will ensure that the:

    • Appropriate offices collaborate for technical expertise and understanding of the compliance issues involved.

    • People who will do the work are included in the planning of the work.

    • Deliverables with dates are identified.

    • Objectives meet the workplan.

  2. Charters often require informal managerial approval to begin the initial brainstorming and hypotheses formation prior to expending significant resources on their creation. This may be as simple as an e-mail request seeking permission to move forward or a verbal discussion presenting the idea.

  3. Communication with appropriate Subject Matter Experts (SME) is required before an initiative charter is put forward for approval. See the contact listing on the Examining Excise Taxes web page at http://mysbse.web.irs.gov/Specialty/excise/default.aspx for a list of excise SME. Research with affected offices is required to determine viability and creation of the draft charter.

  4. Charters must be completed on the current, approved template which contains instructions for completion and approval routing.

  5. Once a charter is approved, a compliance initiative number will be assigned for inventory tracking.

  6. Whenever compliance initiatives are revised, the corresponding charter needs to be revised and forwarded for management approval.

Coordination of Approved Compliance Initiatives

  1. EOS employee must coordinate compliance initiatives with Excise Policy, SMEs, state partners with an approved JOC Memorandum of Understanding (MOU), and any affected offices. Coordination must include agreement on the:

    • charter hypotheses,

    • data analysis,

    • expected outcomes,

    • case assignment information,

    • anomaly detail data to include in case files, and

    • any non-standard, initiative-specific information required in case files such as Customs import transaction data or administrative information.

Charter Compliance Initiatives and SBSE Compliance Initiative Projects (CIPs)

  1. SBSE Compliance Initiative Projects (CIP) apply to any activities involving contact with specific taxpayers and collection of taxpayer data within a group, using either internal or external data to identify potential areas of non-compliance within the group, for the purpose of correcting the non-compliance.

  2. CIP procedures apply to gathering taxpayer specific external data, whether or not taxpayers are contacted. See IRM 4.17, Compliance Initiative Projects, for additional information.

  3. CIP procedures apply to excise tax activities and are mandatory. Approved EOS compliance initiative charters will be assessed for continuance under CIP procedural guidance rules found in IRM 4.17. EOS employees must review CIP procedures to determine if the compliance initiative charter meets any of the CIP exceptions listed in IRM, Activities Not Subject to CIP Procedures. If a compliance initiative does not meet any of the listed exceptions, a formal CIP is required.

Return Preparer Program

  1. The Excise Return Preparer Coordinator (RPC), based in the PSP group within EOS is responsible for coordinating excise tax return preparer penalty cases.

  2. EOS employee provide support to the Excise Return Preparer Coordinator in the development of preparer program action cases. A preparer program action case is a preparer penalty investigation in which clients of a questionable preparer are examined to determine whether preparer penalties and/or an injunction are warranted.

  3. See IRM, Return Preparer Penalty, for additional information relating to excise tax preparer penalty investigation procedures. EOS employees should also refer to IRM 4.1.10, Return Preparer Program, for additional procedures and information to develop preparer program action cases.

The Excise Workload Management System (WMS)

  1. The excise WMS monitors all EOS lead-related inventory and is used to facilitate the case building process. The excise WMS contains:

    • a repository for all excise leads submitted to the EOS, and

    • a record all lead classification dispositions.

  2. EOS employee will follow current procedures regarding the use of the excise WMS.

  3. Leads may be removed from the excise WMS for various reasons including, but not limited to:

    • aging,

    • feedback on accuracy of data, and

    • materiality of an issue.

  4. When a lead is removed from the excise WMS, an indicator will be input identifying the lead as purged.

Types of Leads

  1. New leads entered to the excise WMS include:

    • Initiative Leads

    • Priority Leads

    • Claims Leads

    • Fed/State Agreement and State Revenue Agent Report (RAR) Leads

    • Specialist Referral System (SRS) Leads

    • Other Leads

    • EOS Group Mailbox Receipt Leads

Initiative Leads

  1. EOS employee will identify and review initiative leads to determine which, will be entered to the excise WMS as lead related inventory. Initiative leads usually relate to entities exhibiting anomalous behavior. Selection criteria for these leads are dependent on a variety of factors including, but not limited to:

    • materiality,

    • complexity,

    • tax potential and

    • significant or emerging issues.

  2. EOS employee will review the initiative lead and take the following actions:

    • Perform additional research including but not limited to research on Information Management System (IMS), Internet, Integrated Data Retrieval System (IDRS), Office of Secretary of State, YK1 Research, Analysis and Statistics, and Accurint asset locator tool.

    • Process lead as a joint audit with state partners if warranted.

    • Prepare informational report inquiries (not an audit).

  3. EOS employee will submit initiative leads for entry into the excise WMS using the current, approved template. Use of the approved template ensures that the appropriate data fields are included and that compatible system formatting is provided. A lead is specific to a Taxpayer Identification Number (TIN), Masterfile (MFT) Code, and tax period.

  4. EOS employee will post initiative lead anomaly data files to the current, approved location within the excise WMS and inform the WMS gatekeepers that new files are available.

  5. Initiative lead anomaly data files must be saved using the naming convention Initiative Number – YYYYMMDD. For example, 105-20130625 indicates an anomaly file for Initiative 105 created on June 25, 2013:

  6. EOS employee will provide transaction-level detail data that supports each anomaly submitted as a lead to the excise WMS. For the Initiative 105 example above, the anomaly detail data would be the transaction information from the Custom's Entry import records that were matched to the Form 720 filing data to identify whether a taxpayer filed the correct amount of 720 tax liability. The EOS employee will post the anomaly detail data files to the current, approved location under the initiative number, detail data folder, tax period and data source. The naming convention to save anomaly detail data is:

    • Initiative Number

    • Anomaly Detail

    • Data Source

    • Tax Period


      For example 105- Anomaly Detail- CBP 201012.xls indicates Oil Spill Tax anomaly detail data from Custom's Entry transaction-level data for the tax period ending December 2010.

Priority Leads

  1. Priority leads include:

    1. Chief, Excise Tax, Requests.

    2. Prompt Determinations. These are received through the Chief, Excise Tax, which require a review of the taxpayer’s account to determine next action. See IRM, Procedures on Prompt Determinations, and Revenue Procedure 2010-27 for processing information.

    3. Taxpayer Advocate Service (TAS) Referrals. See IRM, Taxpayer Advocate Service (TAS) Cases.

    4. Form 211, Application for Award For Original Information, receipts. See IRM 25.2.1, Information and Informants’ Rewards, for detailed procedures. PSPWIC is responsible for the assignment of informants cases. Use Tracking Code 7648, Form 211 Informant Claims, to monitor these leads. Form 211 applications are processed at the Ogden Campus where they may then be referred to the Excise Tax Program. Cases are referred both electronically and in paper format. Cases are initially screened by Excise Policy and then referred to PSPWIC who is responsible for the assignment of informants cases if appropriate.

    5. Congressional Cases. These are received through the Chief, Excise Tax, and referred to EOS management if appropriate. See IRM, Processing Requests for Disclosure, for additional information.

    6. Expedite Form 5346, Examination Information Report. These require a two business-day turnaround if possible. Any that are selected will result in a case file sent directly to the group.

    7. All other requests including requests to research news articles and Criminal Investigation (CI) cases.

  2. EOS employee will process priority leads as follows:

    1. Secure management approval and assignment.

    2. Classify for disposition and enter any lead selected into excise WMS.

    3. Provide prompt responses to any requests not completed, indicating the reason for not completing.

Claims Leads

  1. Centralized classification of all excise tax claims and amended returns is conducted by Centralized Specialty Tax Operations (CSTO) at the Cincinnati IRS Campus. See IRM 4.24.8, Examination of Excise Claims for Refund or Abatement, for additional information. Claims related to a return assigned to a field group are not classified by CSTO but are forwarded to the field group for association with the return.


    This pertains only to claims for which an original return was filed and not to quarterly claims or third party claims.

  2. EOS employees may process both discretionary and mandatory claims as leads and will coordinate their selection criteria with CSTO.

  3. Interest-bearing fuel claims from Form 8849, Claim for Refund of Excise Taxes, Schedules 2, 3, or 8 selected for field review will be paid before shipment to the field.

  4. Paid claims selected for field examination should be controlled with AIMS Source Code 31 as follows:

    1. Select the MFT 03 period that corresponds to the claim period.

    2. If no MFT 03 module is available, Substitute for Return (SFR) procedures found in IRM will be initiated.

    3. Push Code 51 is to be used when establishing controls for SFR paid claims selected for field examination . Push Code 51 will allow input of a numeric statute date for the SFR, Excise return(s) which require a live statute.


      The use of Push Code 51 does not remove the IRM requirement for the manager to screen the return to determine the accuracy of the assessment statute information and to identify the need for establishing statute controls.

Fed/State Agreement and State RAR Leads

  1. The IRS Fed/State Program partners with state government agencies to enhance voluntary compliance with tax laws. This includes facilitating the exchange of taxpayer data, leveraging resources, and providing assistance to taxpayers to improve compliance and communications.

  2. The IRS also assists state agencies by identifying and reporting information on emerging tax administration issues. This is accomplished through the IRS entering into agreements to share information with the state agencies.

  3. The Privacy, Governmental Liaison and Disclosure Program (PGLD) is responsible for the coordination of activities between the IRS and state and local governments as well as other federal agencies.

  4. Refer to IRM 11.3.32, Disclosure to States for Tax Administration Purposes, for more information.

  5. State audit reports will be received through a Governmental Liaison shared site. Leads will flow through the EOS classification process and should be considered for joint audit processing. Any that result in classification for case building should be included in the excise WMS.

Specialist Referral System (SRS) Leads

  1. The Specialist Referral System (SRS) is an online, automated system that allows for all submissions and approvals for specialist assistance. It automates the referral request process for specialists in:

    • Large Business &International (LB&I),

    • Small Business Self Employed (SBSE),

    • Tax Exempt Government Entities (TEGE), and

    • Wage & Investment (W&I).

    See IRM, Specialist Referral System (On-line Referrals), and, Specialist Referral System (SRS) - Overview, for additional guidance.

  2. SRS is used to provide mandatory excise lead referrals on Coordinated Industry Cases (CIC) from LB&I.

Other Leads

  1. Other leads are usually derived from non-fuels data analysis that may or may not be documented with a charter. Leads should be monitored through the excise WMS but are not linked to an initiative number. Theses leads may be tracked by abstract number, tracking code, TIN, or other identifier for results monitoring.

EOS Group Mailbox Receipt Leads

  1. The EOS group mailbox located at *SBSE Excise EOS provides an avenue for excise employees to submit requests for information and/or data assistance. The mailbox is a secure Outlook mailbox that requires permission to view received messages.

  2. Submissions to the EOS group mailbox include the following:

    • Form 5346, Examination Information Report , including "Time-Sensitive" Form 5346 requests,

    • HQ staff requests,

    • Request for Information (RFI) forms

    • Data and assistance requests,

    • Income/employment tax referrals,

    • Exam feedback forms,

    • other requests such as requests for new initiatives.

  3. EOS group mailbox receipts will be monitored through the EOS Task Tracker database to ensure timely completion and accurate reporting. Receipts that result in classification for case building will also be included in the excise WMS.

  4. EOS employees will:

    1. Complete all requests within ten business days if possible.

    2. Review the EOS Task Tracker database weekly to ensure timely completion of requests and take action as needed.

    3. Provide an explanation back to the requestor for any rejected requests.

Form 5346, Examination Information Report

  1. The excise employee will complete Form 5346 whenever information is obtained of sufficient compliance value to warrant enforcement follow-up concerning a return filed or to be filed by a taxpayer. Submit completed Form 5346 to the manager for approval. Once approved, send to the EOS group mailbox for action.

  2. "Time-Sensitive" leads such as jeopardy assessments or wagering cases involving coordination with law enforcement agencies that require priority processing should be processed as follows:

    1. The group that discovered the lead should clearly mark the Form 5346 as "Time-Sensitive."

    2. Upon EOS approval, the group will establish ERCS controls and begin working the case.

    3. EOS will create an electronic file for any related data for group consideration.

  3. EOS employee will record receipts of all Form 5346 leads from the EOS group mailbox and forward for classification.

  4. All other Form 5346 requests have a 10 business-day turn-around time. EOS employee will monitor completion of leads to determine timely actions are taken and delays are documented.

  5. EOS employee should process Form 5346 as follows:

    1. Ensure all fields are completed properly, the "Other Information" section clearly indicates the reason for the referral, the tax period is for a current period, and the form is approved by the manager.


      A separate Form 5346 for each TIN, MFT and tax period involved is required.

    2. If Form 5346 does not contain sufficient information and EOS employee cannot determine the missing information or is unable to determine appropriate information, the Form 5346 will be returned via secure messaging e-mail to the originating group manager with the reason for rejection.

    3. EOS employee will complete an EOS Classification Checksheet for all selected information reports and provide a copy to excise WMS gatekeeper to record the receipt and begin the process for case controls and creation of the case file.

    4. A-case file containing any related initiative data and/or data requested by the EOS employee on the Classification Checksheet will be created and posted to the EOS shared site..

    5. EOS employee will monitor case control establishment through CSTO.

  6. The completed case resulting from the Form 5346 lead including the EOS Classification Checksheet and results of the research will be uploaded into the Information Management System (IMS).. Generally all non-filer leads have a five-week turn-around time from the time the lead is received in PSP WIC to the time the case is controlled and released to the excise field group.

  7. If third party issues are present, EOS employee will follow procedures in IRM 4.11.57, Third Party Contacts.

  8. If the Form 5346 request indicates that the case be transferred outside of the Excise Program, a collateral examination request should be completed. See IRM, Collateral Examinations for additional information.

  9. Excise group managers should send all non-excise tax referrals directly to the EOS group mailbox.

  10. EOS employees will forward the referrals to the appropriate Business Unit PSP for processing.

Headquarters (HQ) Excise Staff Requests

  1. All HQ staff requests must be approved by EOS management before assignment and tracking.

Data and Assistance Requests

  1. Excise employees may also submit data and assistance requests to the EOS group mailbox. EOS employees will respond to requests for data and assistance with data analysis.

  2. Data and assistance requests should be submitted on the Request for Information (RFI) form, following the prompts embedded in the form. The RFI is sent to the manager for approval, before being submitted to the EOS group mailbox.

  3. EOS employee will

    1. Route the data or assistance requests to the appropriate employee for completion. This may involve directing the request to management for assignment of data analysis or extraction.

    2. Create new data extract process if appropriate.

    3. Ensure that the data is provided in an acceptable format for field use.

    4. Compile all related case data and send the data directly to the requestor.

    5. Update the request as completed on the EOS Task Tracker database.

Processing New Leads from Inventory

  1. EOS employees will process new inventory leads as follows:

    1. Prioritize the lead to identify ones that will require classification.

    2. Validate entity information from the lead.

    3. Match lead data to other data to assist with the prioritization and classification processes.

  2. Leads are classified and prioritized as:

    1. Select,

    2. Forward,

    3. Reject,

    4. Suspense, or

    5. Purge.

    See IRM for more information.

  3. The EOS employee will create an electronic case file for Selects and Forwards and ensure the establishment of case controls.

  4. The EOS employee will provide case files for compliance action and update WMS on dispositions of inventory.

Validating Entity Information

  1. EOS employee will validate all new leads entered to inventory before posting to ensure:

    • Information of the correct taxpayer , and

    • Proper formatting of data.

Matching Leads to Other Data

  1. Available leads (including those in Suspense status) may be matched to other data that will provide information to assess the lead potential for cases. Other data includes information from the following:

    1. Coordinated Industry Case (CIC) Indicator which is located on the Issue Based Management Information System (IBMIS) listing of Open Cycle cases for current fiscal year.

    2. 637 Registration Information ( where available).

    3. IMS Information (where available).

  2. Data matching against the Examination Returns Control System (ERCS) should show if there is a current audit or investigation open for the taxpayer for the same or other tax periods. The match may be only for Primary Business Code (PBC) 214 for TIN, Name, Address, MFT, TXPD, EGC, Employee Name and Status.

  3. Any prior inventory dispositions which are the historical classification dispositions by TIN can be viewed using the excise WMS.

  4. Related Entities are tied to a single EIN. For example, a Form 720 filer tax contact may file for multiple terminal/facilities, each with its own TIN, indicating a relationship among the entities. Related entities may also show where there are multiple EIN’s that are related such as parent-subsidiary relationships. This will provide information on leads that require case control coordination on multiple employee assignments.

Prioritizing Leads

  1. Available leads require prioritization to assess what will move forward for classification. Examples of lead prioritization criteria may be based on:

    • geographic location,

    • initiative,

    • workload need,

    • resource availability, and

    • annual workplan.

  2. EOS management lead prioritization decisions will address the following:

    • the potential for joint compliance action with states,

    • selection of the referral for classification,

    • identification of the type of compliance activity for the selected leads,

    • compliance action addressed in the field or by correspondence,

    • consideration of the appropriate MFT for case controls, and

    • whether cases will be included in wall inventory or posted for field download.

  3. Selected leads should be made available for classification.

Reopening Previously Examined and Closed Case

  1. Examination cases that were previously closed may be reopened under certain circumstances.

  2. See IRB 2005-23 for guidance on:

    1. when an IRS examination is considered closed,

    2. when a closed examination may be reopened (to include reinspecting a taxpayer’s books of account), and

    3. who may approve a reopening.

    The procedure also describes by category certain IRS contacts with taxpayers and other actions taken that are not examinations, inspections of books of account, or reopenings. See also IRM 4.4.26, AIMS/Processing Handbook, Reopening/Reclosing/Reinputting Records, for additional information.

Overview of Workload Classification

  1. Classification is the process of determining whether a lead should be selected for examination.

  2. EOS employee should inform the PSP WIC manager of leads where the type, industry or potential issue is unfamiliar to the EOS employee. EOS employee should be alert to fraudulent refund schemes and/or potential preparer project returns.

  3. Leads prioritized by EOS management will be assigned for classification via spreadsheet listing by TIN. The listing will be used by EOS management to monitor the status of the leads in:

    • classification

    • case building

    • date of extraction from inventory.

  4. EOS employee will:

    1. Update the listings with dispositions for each lead including the reason why leads were not selected.

    2. Complete a current, approved EOS Classification Checksheet for all Selects.


      EOS Classification Checksheets are used to update excise WMS with the classification dispositions and also to request CSTO establish case controls.

    3. Conduct a quality review on the first two Select/Forward -case files built and provide prompt feedback on any needed corrections.

Classification Dispositions

  1. Lead classification results will be one of the following:

    • Leads identified as Select are in need for further compliance action. They require completion of the EOS Classification Checksheet to create case controls for all new uncontrolled tax periods. Case coordination should be conducted when multiple employees are involved.

    • Leads identified as Forward have a match to a current open ERCS control for the same TIN, MFT, and tax period. They do not require additional case controls. EOS employee will forward the lead data information for that TIN, MFT and tax period to the field group manager. When the case has a same TIN but different MFT and tax period on ERCS and IMS, ERCS controls will be established by EOS employee using an EOS Classification Checksheet. No IMS case file will be established. The data information for the new period will be secure e-mailed to the group manager/employee in charge of the existing IMS case. .

    • Leads identified as Reject have been rejected for a variety of reasons. The reason for rejection must be documented in the excise WMS database.


      Currently, all fuel cases require rejection documentation in the excise WMS.

    • Leads identified as Suspense are not selected temporarily due to various factors such as but not limited to freeze codes, CIC off-cycle, Appeals, etc. Reason for suspense must be documented in the excise WMS database so that the lead can be classified again after the suspense period expires.

    • Leads identified as Purge are to be removed from the excise WMS for future consideration. This will likely be due to invalid entity information.

  2. Leads classified as Selects and Forwards should also be reviewed for potential as joint audit cases with partner states or as state-only leads.

Joint Audits with States
  1. Leads selected for joint audit require EOS management involvement prior to any compliance action taken by the excise field group.

  2. Joint audit cases approved for a compliance action in the field require coordination between the excise group manager, state managers, and their respective excise employees and state auditors. See IRM for procedural guidance.

  3. EOS employees will process joint audit cases as follows:

    1. For Selects and Forwards, include documentation on joint audit case process and guidance on disclosures of federal tax information from EOS activities to non-participating and participating state partners. This documentation should be listed as the first workpaper in the -case file . Include state manager contact information.

    2. On the EOS Classification Checksheet, include a statement that the case is recommended for joint audit processing. If the case is currently open, recommend joint audit processing as appropriate for the status of the case.

    3. Update inventory to reflect joint audit case.

  4. Joint audits are worked as federal excise audits. Federal excise and state managers and their agents must be familiar with and understand the federal disclosure requirements which should be included in case files. The following steps should be completed for all leads selected as joint audit cases:

    1. The federal excise territory manager should ensure the excise group manager and assigned excise employee are notified that the case is being assigned for joint audit.

    2. The federal excise group manager should contact the state manager to obtain a comprehensive understanding of the case file, discuss the scope of the audit and next steps.

    3. The federal excise group manager is the lead on all joint audit cases and directs the scope of the exam unless notified otherwise by their territory manager.

  5. Federal excise and state manager coordination is required and should include the following:

    1. Discussing case strategy/audit plan.

    2. Responding to excise employee and state auditor recommendations to expand or contract cases. All federal procedures and protocols apply. States assist on the "joint" portion of the exam and make state self-disclosures at the appropriate time if applicable.

    3. Ensuring excise employees and state auditors work together to determine what records should be requested to reach a conclusion about the audit issues.

    4. Revising audit plans as appropriate pursuant to initial taxpayer meeting including mutual commitment date(s).

    5. Issue Letter 3253, Taxpayer Appointment Confirmation Letter, by either the excise employee or state auditor. Letter 3253 is modified to inform the taxpayer that a state auditor will be participating in the examination and list both the excise employee and state auditor names under the "Person to Contact" .

    6. Approval of Letter 3253 is required by the excise group manager. Letter 3253 will also contain an optional paragraph to include the following two statements, "(insert name of state auditor), (insert state audit or title) with the (insert state office title) will be assisting (inset excise employee name and title) with the examination. If the examination results in a federal excise tax liability, this may also result in a liability for the (insert state)." Immediately following this sentence should be "As we discussed, please have the items listed on the attached Form 4564, Information Document Request, available at our first appointment" .

    7. Coordinating any interviews conducted by both the federal excise tax employee and state auditors.

    8. Ensuring audit reports are completed as appropriate to the issues. Federal excise audit reports can only be issued by the excise employee. State auditors issue any state audit reports but only after the state agent has performed a self-disclosure.

State-Only Audits
  1. State audits parallel the federal excise tax issue and are determined from the same information; however, if at any time the state needs to acquire different information to make a state determination, they must conduct a state-only examination with an approved disclosure completed prior to beginning any activity. See IRM, Disclosure, and IRM, Overview of Disclosures of Federal Tax Information (FTI), for procedures.

  2. The IRS may not provide information to states that may impair federal tax information. The excise tax manager must determine there is no federal tax impairment when sharing this information, including cases with Criminal Investigation (CI) freezes or in which there is an active criminal investigation.

Research for Classification of Leads

  1. Leads have multiple data points that should be reviewed prior to determining disposition including:

    • CIC,

    • ERCS Status,

    • audit history/prior classification disposition,

    • related entities/multiple controls, and

    • other research information.

  2. Other research information includes:

    • entity validation,

    • filing requirements,

    • employment codes,

    • income tax controls,

    • filing history,

    • freeze codes,

    • industry type,

    • collectibility issues,

    • statutes,

    • grade of case,

    • IMS documentation, and

    • 637 status.

  1. Coordinated Industry Cases (CIC) are selected annually for examination by Large Business &International (LB&I). CIC cases require coordination between Excise and LB&I employees.

  2. To facilitate coordination, an MOU was signed by the Commissioners of LB&I and SBSE. The MOU is in effect from October 1, 2012, through September 30, 2015, and outlines the responsibilities of the excise employee in assisting the LB&I examiner.

  3. The MOU provides that referrals to the excise tax group are mandatory for all CIC cases. To facilitate this requirement, the Specialist Referral System (SRS) has been adapted to require an entry for an excise referral. See IRM, Specialist Referral System, and IRM, Specialist Refer System Overview, for additional information.

  4. EOS employee will process CIC inventory in accordance with current excise workplan guidance.

ERCS Status
  1. EOS employee will review ERCS match information to identify related names and/or multiple employee controls.

  2. EOS employee will review ERCS information to determine dispositions.

  3. If ERCS TIN/MFT/TXPD match and the status code is under 14, case disposition is Forward. This type of forward does not require further case controls. . EOS employee will process the Forward as follows:

    1. If the case is in status 08, update the IMS wall inventory case file with new information.

    2. If above status 08, secure e-mail controlling excise group manager with a cc to excise employee assigned to the case (if known) providing the additional case data for their open examination.

    3. Provide coordination instructions when there are multiple MFT or excise employees if applicable.

  4. If ERCS TIN/MFT/TXPD match and if the status code is higher than 13, the EOS employee will:

    1. Perform standard classification to determine disposition in conjunction with current ERCS status.

    2. Use professional judgment on materiality of issues identified.

    3. If selected and case has been closed, the EOS employee should refer to reopening procedures found at IRM

  5. If ERCS TIN matches but TXPD or MFT differ, the EOS employee will:

    1. Perform standard classification to determine disposition.

    2. All Selects require new ERCS case controls but will not have a new IMS case established.

    3. Once the ERCS controls exist on the new TXPD or MFT then EOS employee will secure e-mail controlling excise group manager with a cc to excise employee assigned to the case (if known) providing the additional case data for their open examination

  6. If no ERCS match exists, perform standard classification review to determine disposition.

Audit History/Prior Classification Dispositions
  1. Audit history and prior classification dispositions for the same entity may assist with classification dispositions. EOS employee shall review Command Code BMFOLZ to identify audit results including closing codes.

  2. The following should not prevent selection of a case for examination for the same MFT and tax period:

    • audit indicator for income tax examination,

    • audit indicator for employment tax examination,

    • audit indicator for an excise tax penalty or terminal/carrier review examination closed over a year ago,

    • audit indicator for any other non-excise tax examination control.

  3. The following could prevent selection of a case for examination if occurring in the last 18 months:

    • audit indicator for an excise tax MFT 03 or other primary excise return MFT,

    • audit indicator for current fraud case; however, consider lead information for coordination with the Excise Fraud Coordinator.

  4. If a case is not selected based on the above guidelines, consider for selection if the potential adjustment exceeds the current tolerance set by EOS management or if indications of fraud exist.

Related Entities Information
  1. Related entities require case control coordination. Information on related entities should be documented on the EOS Classification Checksheet to ensure excise employees are aware of the relationships and to allow for appropriate coordination.

  2. EOS employees will review available information to identify related entities. See IRM, Coordination on Cases with Multiple Employee Assignments, for more information.

Other Research Information
  1. EOS employee should review other research information to determine disposition of lead. Examples of other research information are listed below.

  2. Review Entity Validation, Filing Requirements and Employment Codes. This information is found using Command Code INOLES to validate current name, address and filing requirements to gauge the type of entity.


    Command Code BMFOLI may show the entity is filing forms not necessarily required to file by INOLES such as Employment Code (Non-profit, government, etc.) if unable to validate.

  3. If unable to validate:

    1. Research Command Code BMFOLE for name changes. This is usually shown on second or third page of the INOLES.

    2. Research Command Code NAMEE/ EINAD on geographic location for BMF and/or NAMEI for IMF.

    3. Consider Internet or Accurint business or people searches. The Internet can be used to develop further information about the taxpayer including alternate addresses and locations. Accurint may reflect name/address/TIN that are geographically or name-linked and may show employees at a given company or location. Research can then be conducted on those names via Command Code IRPTRO to identify W-2's, K1's and the correct TIN.

  4. If no EIN is identified but an SSN is available, verify the SSN, name, and address of the taxpayer. EOS employee will contact the Cincinnati Accounts Management Center (CAMC) Employer Identification Number (EIN) Program Entity Unit to obtain an EIN.

    1. EOS employee will send an secure e-mail to the EIN Entity Unit with the name, address and SSN (if applicable), the form for which the EIN is needed (Form 720, 730, 2290, etc.), and what filing year indicators are needed.

    2. Entity Unit will assign an EIN to the taxpayer and provide a completion message back.

    3. The new EIN will only be viewable on IDRS via Command Code ENMOD for the first two weeks. It is suggested that the account and new EIN be held for two weeks until fully established on IDRS.


      See CAMC contact listing for EIN Program Entity Unit contact.

  5. If still unable to validate, reject the lead and provide Reject disposition.

  6. Review Income Tax Controls. This information is found using Command Code AMDISA to identify current income tax controls. Note that automated ERCS information is provided through the automated match to other internal data for PBC 214 only.

    1. Research Command Code AMDISA for income tax controls for coordination on CIC and other income tax controls.

    2. If CIC control exists, check with Excise CIC SME for team manager/team leader information.

    3. If other income tax controls exist, provide information in case file on assigned group.

  7. Review Filing History. This information is found using Command Code BMFOLI to identify filing history, whether taxpayer is current with filings, if they are filing forms not required, whether non-filer/stop filer, or collectibility issues are present. The filing history information will allow the EOS employee to make a professional judgement regarding the overall assessment of the taxpayer.

  8. Review Freeze Codes. This information is found using Command Code BMFOLI. IDRS and Document 6209, IRS Processing Codes and Information, must be researched for freeze codes to determine processing. See IRM, Freeze Codes, for additional information. Certain freeze codes require coordination with other offices before selecting leads. Some may require suspending leads for a time. Common freeze codes include:

    • C, Combat Zone Suspense. Examinations are not to be conducted during the period of time a taxpayer is deployed in a Combat Zone. See IRM, Combat Zone, for procedures.

    • –O and –S, Disaster Suspense. See O Freeze information in IRM,(1)(a)(4), and IRM

    • Z -, Criminal Investigation Hold. See IRM, Z Freeze, for more information. Contact HQ Excise Tax Fraud Coordinator for instructions whether to continue processing or to transfer the case.

  9. Review for Industry Type, CIC, and Collectibility Issues . Use Command Code BMFOLE to determine:

    • North American Industry Classification System (NAICS) codes,

    • CIC or Coordinated Examination Program (CEP) indicator,

    • Collectible Hardship Closures (CNC) closing codes,

    • Form 637 indicator, and

    • previous names the entity may have used.

    For collectibility issues, see IRM 4.20, Examination Collectibility, and IRM, Pre-Audit Issues Collectibility, which contains a listing and definition of collectibility indicators and steps to take when evaluating collectibility potential.

  10. Review Statute of Limitation Periods (SOL). Use Command Code BMFOLT to determine SOL. See IRM 25.6.1, Statute of Limitations Processes and Procedures, for guidance on verifying SOL dates. Failure to protect the period of limitations can result in disciplinary action.

  11. Review Grade of Case. Use Command Code BRTVUE to identify grade of case. Grade of case is dependent upon the taxpayer's industry/occupation and size. Grade of case generally should be the same as the grade of the primary income tax return; however, see IRC, Assignment and Grade level of Form 637 Registration Initial Applications, Compliance Reviews, and Other IRC 4101 Case Work, and IRM, ExSTARS Workload Selection, and Assignment, for information on the standardization of IRC 4101 compliance case work. EOS employees will use Command Code BMFOLE to review the most recent income tax module to determine assets and gross receipts along with NAICS codes. See IRM, Grade Level of Work for Field Examiners, for additional information. If there is insufficient information to make a determination as to grade of case, it should be set as grade 11.


    Group managers may change grade of case if local knowledge warrants.

  12. Review IMS Documentation if available. IMS closed case workpapers may help determine if the issue has been addressed before, or if potential fraud exists. For example situations where the taxpayer is continuing to collect excise taxes but intentionally fails to remit them to the IRS (pyramiding) or continuing in other non-compliant behavior.

  13. Review 637 Status if registered. EOS employee will review information on the Form 637 registration status. This information enhances overall knowledge of the entity and helps in the decision-making process. For example a company who imports trucks subject to the retail excise tax and does not have a registration suggests that the imported trucks may be non-taxable due to municipal sales.

Substantial Non-Compliance Factors (SNiF) Criteria

  1. Using all the research information gathered, the EOS employee will screen leads using the SNiF criteria found in IRM before the lead is classified and case built and made available to the field groups. Key SNiF criteria is listed below:

    • Substantial civil tax potential when considering the estimated time to work the issue and anticipated adjustment based on the information provided.

    • Significant dollar amount and/or large, unusual and questionable items based on a review of reported items.

    • Significant potential tax loss and overall impact of noncompliance issue.

    • Local area compliance impact, for example a geographically unique industry.

    • Emerging non-compliance promotions.

    • Allegations of non-tax criminal activity that may have tax implications.

    • Significant potential for fraud.

    • Significant potential for litigation - consider issues with conflicting lower court decisions and/or significant gray areas of law. Always consult with the Excise HQ SME responsible for the issue before proceeding.

    • Evidence of intent to mislead. This may include missing, misleading, or incomplete schedules or incorrectly showing an item on the return.

    • Overriding excise management decision such as training needs, inventory requests, new ideas to test that change the normal professional judgment decision of the EOS employee.

Documenting Classification Dispositions on the EOS Classification Checksheet

  1. An EOS Classification Checksheet is required for all leads classified as "Selects" . The EOS Classification Checksheet is used to:

    1. Inform CSTO to establish case controls with specific coding information including the case status code. Cases should be placed in the appropriate status code for wall inventory or direct referral to the field.


      If the Work Order Request Tracking System (WORTS) shows work requested for the appropriate grade of case for each Select, it will be designated status 10.

      See IRM, Work Order Request Tracking System, for more information.

    2. Update the excise WMS database.

    3. Inform excise employees on any specific information for the case.

  2. EOS employee must indicate in the Checksheet Field Notes section of the EOS Classification Checksheet when -case file is available for group manager download.

Case Coding Procedures

  1. The use of AIMS source, project, and tracking codes for case work is the joint responsibility of Excise Policy and EOS. For a list of approved codes and when they should be applied, see the Codes and Procedures page on the Examining Taxes website at http://mysbse.web.irs.gov/exam/mis/default.aspx.

  2. EOS employees will ensure that the appropriate project and or tracking codes are included on all cases included related pick-ups.

  3. Excise source codes include, but are not limited to:

    Source Code Description
    20 Regular Classification
    24 Non-filer
    30 Claims for Refund/Abatement
    31 Paid Claims
    40 Filed prior and/or Subsequent Year Pick-up
    44 Non-filed Delinquent Return or SFR
    49 Preparer of Return
    71 Specialist Referral System
    73 OIC/Taxpayer Requests
    77 Fed/State Cooperative Agreement
    91 Non-AIMS Misc. Penalty

  4. The use of ERCS status codes is the joint responsibility of Excise Policy and EOS. They include:

    ERCS Status Code Description
    08 Selected-Not Assigned
    10 Assigned-No Time Applied
    66 Correspondence Audit Forwarded
    99 Correspondence Audit Reject

  5. EOS employee will establish case controls on Facility Control Numbers (FCN) by creating a substitute EIN with three leading zeroes and the six numerical digits from the terminal’s FCN number. See IRM, ExSTARS Examination Return Control System (ERCS) Procedures, for additional information.

ERCS/AIMS Controls Procedures

  1. Except for expedites, all cases selected for compliance activity must first be controlled on AIMS/ERCS under the appropriate TIN, MFT and tax period.

  2. If the new case information is identified for an open excise audit for the same MFT and tax period, the EOS employee will:

    1. Send a secure e-mail to the excise group manager with a cc to the assigned excise employee (if known) explaining that new information will be available for insertion into IMS and

    2. attach the information to the e-mail if space persist.

  3. If the new case information is identified for an open excise audit for the same TIN but a different MFT and/or tax period, the EOS employee will:

    1. Prepare the EOS Classification Checksheet and have the ERCS/AIMS controls established.

    2. Send a secure e-mail to the excise group manager with a cc to the assigned excise employee (if known) explaining that new information is available for insertion into IMS, and

    3. attach the information to the e-mail if space permits.

  4. EOS employee will provide to CSTO an electronic version of the EOS Classification Checksheet as well as any data items EOS want added in the IMS case. Case information that will be created at CSTO to be included as additional attachments include such items as:

    • CBRS,


    • 10K,

    • Accurint,

    • Internet research, etc.

  5. For case control procedures related to claims, see IRM, Excise Claim Classification and Control Procedures.

Coordination of Case Controls-Multiple Employee Assignments

  1. Coordination of case assignments is required when multiple employee case assignments are involved as follows:

    • One taxpayer (one TIN) with more than one excise employee assigned, for example when one excise employee is assigned to MFT 03 (Form 720), and a different excise employee assigned to MFT B1, (ExSTARS compliance).

    • More than one taxpayer (multiple TINs) for related entities, both the parent and subsidiary EINs are controlled to different employees, one terminal filer EIN files for multiple Facility Control Numbers (FCN), etc.

    • More than one taxpayer (multiple TINs) for related tax issues, such as in whipsaw cases.

  2. EOS employee will complete the EOS Classification Checksheet with primary and/or related indicator as appropriate.

  3. When only one taxpayer (TIN) is involved:

    If MFT is: And: Then MFT:
    03 any other MFT present , 03 controls coordination
    B0 (Form 637) no 03 but any other MFT present, B0 controls coordination
    B1 or P9 (ExSTARS Penalty) no other MFT present 03 or B0 created as appropriate to control coordination


    Management must ensure that the assigned excise employee grade level is commensurate with the grade level of the case.

  4. When more than one taxpayer (multiple TINs) with related entities or related tax issues are involved:

    If MFT is: And: Then MFT:
    03 on parent EIN any other MFT present, 03 controls coordination
    B0 on parent EIN any other MFT present, B0 controls coordination
    P9 on parent EIN any other MFT present, P9 controls coordination if GS13; otherwise, create MFT 03 or MFT B0 as appropriate
    Any other MFT on parent EIN, or no control on parent EIN no other MFT present 03 or B0 created on parent EIN as appropriate to control coordination

  5. EOS employee will send secure e-mail to excise group manager and excise employee (if known) of the MFT that controls coordination. The secure e-mail will inform them that, "Group managers should ensure coordination is conducted when multiple employee assignments exist for a given taxpayer (one TIN) or when related entities with multiple TINs are involved such as parent/subsidiary relationships or where one terminal operator filer files for multiple terminals."

  6. If the Form 720-TO is a CIC case, all related terminal reviews (FCN's) should be directed by the excise employee assigned to the Form 720-TO case. The receiving excise field group of the FCN review should contact the excise manager and examiner assigned to the open Form 720-TO case. The Form 720-TO excise examiner manager must determine if the related terminal review is to be conducted by them or coordinated with a excise field group manager located nearest the FCN that will conduct the review.

  7. EOS employee will send all leads to the Form 720-TO manager (whether open or not) to coordinate the reviews of FCN's related to that Form 720-TO.

  8. The EOS employee will open excise ERCS controls as appropriate. If the lead tax period is in ERCS status 90, Reject the lead, but consider reopening procedures for significant materiality.

  9. If the lead tax period is not status 90, the EOS employee will:

    1. Classify as a Select.

    2. Research IMS open and closed case data if necessary to identify whether the issue was addressed as part of the examination.

    3. Consider expedite processing if necessary.

    4. Document case coordination information on the EOS Classification Checksheet.

Managing Inventory

  1. Leads classified as Selects will be sent to CSTO for case controls and will specify the case building information to be included in the case file on the EOS Classification Checksheet. CSTO will establish Master File controls using the Examination Returns Control System (ERCS).


    Any changes to processes that affect CSTO must be coordinated with the Excise Tax CSTO Liaison.

  2. Leads will be designated as Status 08 for "Wall Inventory" or Status 10 for "Field Inventory."

  3. Inventory can fall under two categories:

    • EOS-built case files which include Expedites and Forwards where data is sent directly to the field but do not have an IMS case set up at CSTO. Filed groups are responsible for IMS controls.

    Type CSTO Create ERCS/AIMS Controls? CSTO Establish IMS Case? Action
    Expedites No No Field responsible for ERCS and IMS controls
    Forwards Yes if controls do not exist for the data TIN/MFT/TXPD No Field responsible for IMS controls

    • CSTO-built case files are created for all new case controls where there is no current (below status 14) ERCS for TIN/MFT/TXPD.

      If there are CSTO Create ERCS/AIMS Controls? CSTO Create IMS Case? Action
      No current ERCS/AIMS controls below status 14 for the TIN in Excise MFT Yes Yes unless already an existing IMS control excluding any MFT BO cases Wall or field Inventory Status
      Current ERCS/AIMS controls below status 14 for the TIN for any Excise controls other than MFT BO Create new periods as needed No EOS will treat as a Forward case and send to field any new data to be placed into existing IMS case.
      No current ERCS/AIMS controls below status 14 for the TIN for any other excise control but there are MFT BO controls Yes Yes Wall or Field Inventory Status


      EOS employee will review classification dispositions for Forwards to post files and secure e-mail excise group managers that a file is available in IMS or for download from Excise WMS.

  4. CSTO-built case files are built by CSTO for certain leads disposed as Selects and are processed as follows:

    • EOS employee will provide case requirement information to CSTO for needed case data such as IDRS prints, CBRS prints, etc.

    • CSTO-built case files for Wall Inventory will be held in CSTO inventory until needed.

    • CSTO-built case files for field group inventory will be merged with prints for full AIMS, updated to ERCS status 10 and sent to the appropriate field group via Form 3210 procedures.

Work Order Request Tracking System (WORTS)

  1. Excise group managers submit inventory order requests to their territory manager for approval. Territory managers utilize the WORTS to place orders with EOS. WORTS will enable the territory manager to monitor their field groups inventory requests as they are filled.

  2. Territory managers should review the ERCS IVL report for their field groups. The ERCS IVL provides information on available inventory to complete a WORTS request.

  3. If Wall Inventory is not available to meet the WORTS request, the EOS employee shall research other resources to identify work. If an inventory request cannot be filled due to the lack of inventory, the EOS manager will contact the territory manager to discuss methods to identify inventory to fulfill requirements.

  4. When Wall Inventory is requested for a specific excise field group, the EOS employee will:

    1. Refresh any needed additional data for the EOS or CSTO-built files.

    2. Update excise WMS database to reflect the WORTS number to generate into WORTS system that case was selected from Wall inventory to Field inventory.

    3. Request CSTO update case to ERCS status to 10 and appropriate EGC which will result in CSTO sending the file and notification to the group manager.

  5. An inventory requisition that has not been filled is considered "open/back ordered." EOS will monitor WORTS and prepare a monthly open/back ordered inventory report to the territory manager and Excise HQ.

  6. Group managers should be aware of the timeframes for inventory being shipped after submitting their requests and make every effort to timely order inventory.

  7. EOS will semi-annually evaluate aging inventory and make appropriate dispositions.

  8. During classification, EOS employee will grade cases and review WORTS orders to designate status code of 08 or 10.


  1. Case building is the process of assembling available taxpayer-specific research for excise employees to consider when conducting their audits/investigations/reviews.

  2. Cases built by CSTO will contain information specified by the EOS employee.

  3. Cases built by EOS employee will contain the following information if available:

    • EOS Classification Checksheet and/or Case Index. which contains entity data and summary of compliance initiatives that identified the entity.

    • Case Assignment Information which explains why the case was identified.

    • Anomaly Data summarized by TIN.

    • Anomaly Detail Data which is transaction-level data that resulted in the anomaly.

    • Data Dictionaries which describe fields in anomaly detail data.

    • Other Information which includes other documentation such as questionnaires, satellite images, etc.


      Joint audits will include disclosure and joint audit procedures and state manager contact information.

Correspondence Audits

  1. Correspondence audits may be worked by CSTO employees and require coordination with Campus Compliance Services, Campus Reporting Compliance, and Workload Selection and Delivery. If the work is within the CSTO workplan, EOS will forward information on the issue.

  2. Any requests that require additional coordination should include the Excise SME.

  3. EOS will monitor the case results and request CSTO provide feedback on productivity.

Overview of Disclosures of Federal Tax Information (FTI)

  1. Release of tax data to any other federal or state government entity shall be effected in accordance with the disclosure requirements in IRC 6103, Confidentiality and Disclosure of Returns and Return Information, and IRM 11.3, Disclosure of Information. Disclosure of returns and return information is permitted subject to established safeguards of the information and subject to other statutory restrictions with the authority to release found in Delegation Order 11-2.

  2. The JOC Memorandum of Understanding (MOU) Section 9D states that the Senior IRS Representative will ensure that all requirements for recordkeeping and accounting for disclosures are met in accordance with 6103(p)(3), 6103(p)(4) and all applicable IRC 6103 implementing regulations.

  3. In general, the following two items should be in place prior to sharing information with any state:

    • The Basic Agreement, which is an agreement on coordination of tax administration executed by the Commissioner of the Internal Revenue Service and the head of a state tax agency, which encompass the required procedures and safeguards. See IRM, Basic Agreements, for detailed procedures.

    • The Implementing Agreement, which is developed and negotiated with each state tax agency that wants to receive federal returns and return information on a continuing basis. This agreement supplements the basic agreement by specifying the detailed working arrangements and items to be exchanged. See IRM, Implementing Agreements, for detailed procedures.

  4. IRC 6103(d), Disclosure to state tax officials and state and local law enforcement agencies, permits the disclosure of returns and return information with respect to taxes imposed by chapters 31, 32, and subchapter D of chapter 36 to any state agency, body or commission, or its legal representative, charged under the laws of the state with the responsibility for administration of any state tax law. The state's ability to receive excise tax information will be listed in the Basic Agreement and/or the respective Implementing Agreement.

  5. The JOC participating agency employees will have access to federal tax information (FTI) as contractors to the IRS under provisions of IRC 6103(n), Certain other persons. The following codes sections apply to situations where the JOC refers federal tax information contained in leads developed by the JOC to a participating state agency employee:

    1. IRC 6103(d) will replace IRC 6103(n) as the governing disclosure opinion where the state employee is a contractor for the JOC acting on behalf of the IRS. Participating state agencies may use FTI obtained from the lead referral for their state tax administration purposes as provided for under IRC 6103(d) and their individual MOU's, Implementing Agreements, and Fed/State Basic Agreement on Coordination of Tax Administration executed with the IRS.

    2. State employees acting as IRS contractors are subject to the terms and conditions of the federal tax regulations found in Treasury Regulation 301.6103(n)-1, Disclosure of returns and return information in connection with procurement of property and services for tax administration purposes. The self disclosure for FTI accessed for lead generation is not governed by IRC 6103(d) but IRC 6103(n). As an IRS contractor, all state employees are allowed to access the entire universe of FTI. Once the lead is developed, the disclosure is governed by IRC 6103(d). The Basic and Implementing Agreements in effect govern the release of tax information to the participating states as well as the JOC MOU. Since the underlying disclosure instruments allowing the disclosure were signed by those in authority under the delegation order 11-2 (the JOC MOU and the other normal state agreements) that authority is covered.


      State personnel and agency contractors must complete necessary background investigations prior to having access to FTI.

    3. Records and documents collected, maintained, or generated by the IRS and/or disclosed to participating state agencies under the JOC MOU and any information collected as a result of joint correspondence, joint interview, or IRS administrative summonses will be subject to the confidentiality requirements of IRC 6103(a).

Guidance on Disclosures of Federal Tax Information to Non-Participating and Participating State Partners

  1. The following contains guidance on how to make disclosures of federal tax information and related joint audit activities from the JOC to state taxing agencies that are either non-participating or participating state partners.

  2. Participating state partners are states that have signed a MOU to participate in the JOC. Some participating state partners have employees who have completed background investigations for staff-like access to federal tax information (FTI) and are JOC employees.

Disclosures of FTI to Non-Participating and Participating State Partners with Taxpayer Consent
  1. Disclosures of FTI to both non-participating and participating state partners with taxpayer consent may be conducted under the JOC MOU if the taxpayer under audit agrees to execute a Form 8821, Tax Information Authorization, and consent conforms with the regulations found at 26 CFR 6103(c)-1(b) and designates the receiving state agency as the appointee to receive the federal tax information.

  2. IRS may release information to the state without having the state subject to safeguards for the data and without the need for the accountings for the disclosure. The taxpayer must do this willingly without coercion. The consent must include all state agencies that may have an interest in the information. The JOC Program Manager must review the consent for validity prior to any release of data.

Disclosures of FTI to Non-Participating State Partners
  1. Disclosures of FTI to non-participating state partners require coordination with the state’s servicing disclosure office.

  2. A non-participating state is a state that has not signed the JOC MOU.

  3. The state partner must solicit a specific request for FTI from the state disclosure office after determining if the state agency has the required written agreement in place to allow disclosures of excise tax information.

  4. If approved, the Disclosure office will make the disclosure and complete the required accountings.

  5. Disclosures will only apply to leads identified at the JOC National Data Center (NDC) and will be initiated by JOC management.

  6. EOS employee will draft a memorandum that explains the need to contact the state to solicit a specific request including a list of the data that the Disclosure office should transmit. The Disclosure office, after determining the state can obtain the information, should then solicit a specific request for the information and have the state submit that request to that office for release. The Disclosure office will then take care of the release and the Disclosure accounting requirement. Disclosure office contact information may be found at http://discl.web.irs.gov/contact.asp

Disclosures of FTI to Participating State Partner Non-JOC Employees
  1. Disclosures to participating state partner non-JOC employees are the same as disclosures of FTI to non-participating state partners above.

  2. A state partner non-JOC employee is an employee of a state who has signed the JOC MOU, but the employee has not completed an IRS background investigation and does not have IRS staff like access.

Disclosures of FTI to Participating State Partner JOC Employees
  1. Disclosures to participating state partner JOC employees are authorized under IRC 6103(d) through a combination of the state's current Basic and Implementing agreements along with permissions outlined in the JOC MOU and By-Laws, and approved via signature of the IRS, states and the IRS Commissioner.

Disclosure Accounting Package

  1. For each disclosure, the EOS employee will prepare a disclosure accounting package to be routed through the JOC Operations Manager. The disclosure accounting package will consist of:

    1. Form 5466-B, Multiple Records of Disclosure,

    2. FTI, and

    3. Form 3210, Document Transmittal.

Instructions for Completion of Form 5466-B
  1. Generally, this form is used to account for tax disclosures, although in situations where a large volume of records are disclosed at one time, a narrative accounting may be used. See IRM for narrative accounting procedures.

  2. IRS procedures for creating a record of the disclosure with Form 5466-B are found in IRM 11.3.37, Recordkeeping and Accounting for Disclosure.

Narrative Accounting for Disclosure
  1. If the disclosure is not documented with a Form 5466-B, the EOS employee will prepare a memorandum for the HQ Disclosure Tax Law Specialist from the JOC Operations Manager containing the information listed below:

    • Subject of Memo. Narrative Accounting for Disclosure.

    • Category and Number of Taxpayers. Include the number of Individual Master File or Business Master File records, the number of tax years, and the number of disclosures.

    • Date of Disclosure.

    • ADP Source Codes. Include the number of disclosures for each ADP code used. A list of these codes can be found in IRM Exhibit 11.3.37-2, Recordkeeping and Accounting for Disclosures.


      Some ADP examples are: 116 – Individual Master File Records; 188 – Partnership Returns and Files; 189 – Corporate Returns and Files; 144 – Information Returns Master File. The JOC will likely list all under code 404 - Compliance Programs and Project Files. If the disclosure is for specific tax returns, use the code for that return type.

    • Description of Documents Disclosed. Provide a general description of the information being disclosed. For example, "Lead information for excise tax purposes that includes 2 million gallons of petroleum products imported by Company A into the Port X ."

    • Purpose of Disclosure. IRC 6103(d) Purpose Code 11 to states for state tax administration.

    • Name and Address of Agency Receiving the Information.

    • Location of IRS Office Retaining a Copy of Disclosed Information.

    • Type of Documents Disclosed. Returns and return information (electronic or paper).

  2. Upon receipt and approval of the memorandum, the JOC Operations Manager will sign and forward the memo to:

    Forward memorandum to
    IRS, Attention: Jonathan K. Davis, Tax Law Specialist
    1999 Broadway MS 7001DEN
    Denver, CO 80202-3025

Instructions for Completion of Form 3210
  1. The EOS employee should sign and date the Form 3210 and deliver the completed package to the JOC Program or Operations Manager for approval. The package shall be signed electronically or on paper as needed. The information listed below shall be included on Form 3210:

    • To -a complete and correct address of the person and agency receiving the information.

    • Release Date -complete after approval signature by the JOC Program Manager or their delegate.

    • Remarks -a general description of the data being provided such as, "The data being provided to State Agency B is related to fuel imported by Company A and entering the US through the Port of X ."

    • A testament of research conducted to ensure that no active criminal investigation or federal tax impairment exists -Neither the IRS nor the participating state taxing agencies will disclose return information that would identify a confidential informant or seriously impair any civil or criminal tax investigation. In order to make this testament, the federal examiner must conduct research for any IDRS “Z” freezes.

    • Quantity- provide the number of items being transferred if using electronic media or the number of disks, CDs, pages or other media sources if FTI is being transmitted by another source such as overnight mail (FedEx, UPS, etc.).

    • Code or Type-provide a type description related to the quantity. If x number of files are provided, the Type would be files.

    • Description-describe the content of each type that is being shared, e.g., if four CDs are being provided, the description may read, "CD 1 contains information on fuel imports for 2001106. CD2 contains information on fuel imports for 201109 " .

    • From

    • Releasing Official

    • Originator Telephone Number

  2. Excise examiners assigned to joint activity cases will provide assistance as necessary, i.e., researching for "Z" freezes and completing Form 3210.

  3. The -Z and Z- freeze is set by TC 914, TC 916 or TC 918, initiated by and assigned to Criminal Investigation (CI) Fraud Detection Center (FDC) in the Campuses. TAKE NO ACCOUNT ACTION when a Z freeze is present on a module (Command Code TXMOD or ENMOD). Sensitive freeze conditions must be referred to CI FDC. DO NOT inform the taxpayer of CI involvement. EOS employee will only refer inquiries if the module contains a -Z freeze. Example: If there is a Z freeze on 2008 and 2009 and the case is for 2010 which does not have a -Z freeze, work the case and do not refer to CI. See IRM, Freeze Code Procedures, for additional information.

Release of Information

  1. After receiving approval for the entire disclosure package from the JOC Operations Manager, the EOS will send the original Form 3210 along with the disclosed information to the receiving agency.

  2. EOS employee will ensure receipt of the signed Form 3210 from the receiving agency acknowledging their receipt of the disclosed information.

  3. EOS employee will provide a copy of the Form 3210 to the receiving agency and return the signed, original receipted Form 3210 to the JOC Operations Manager.

Disclosure Scenarios

  1. The scenarios below cover the different disclosure circumstances that may be encountered when working joint federal/state compliance initiatives.

  2. Scenario #1 JOC leads that have federal-only or state-only tax consequences for both participating and non-participating state partners:

    • Federal-only leads will be processed separately through PSP WIC for classification, control and distribution to the field.

    • State-only leads to participating state partners will be disclosed to those states as per procedures found at IRM above.

    • State-only leads to nonparticipating state partners will be disclosed to those states as per procedures found at IRM above.

  3. Scenario #2 JOC leads that have both federal excise and state tax consequences that are audited by a team comprised of excise and state JOC employee examiners:

    • The audit will always begin under federal jurisdiction. The team will prepare generic workpapers that can be utilized to support both federal and state issues and that can be further documented signifying the jurisdictional agency at a later time.

    • At completion of the audit, a federal excise audit report can be issued by the federal agent only. Before a state audit report can be issued, a disclosure needs to be made to the state by the state field examiner as per procedures found at IRM above.

  4. Scenario #3 Same facts as Scenario 2 facts but before the federal audit report is delivered to the taxpayer, it is determined that the federal and state issues no longer coincide or the state examiner identifies a new or separate issue with state-only tax consequences. As a result, the state examiner wishes to obtain additional information in pursuit of a state-only tax determination

    • Before any action to pursue the state-only issue can be taken by the federal excise or state examiner, the state field examiner must perform a self-disclosure of the necessary FTI or lead information obtained in the federal examination utilizing the procedures found at IRM above.

  5. An alternative method to perform a disclosure of FTI in Scenarios 2 and 3 above is for the federal excise employee to utilize Form 8821. See procedural guidance found at IRM

Unauthorized Disclosures

  1. Disclosure is prohibited for:

    • non-tax purposes unless there are specific provisions in IRC 6103 that allow disclosure,


      coordination must take place with the HQ Disclosure point of contact.

    • information obtained pursuant to tax treaties,

    • wagering tax information,

    • Currency Transaction Report information,

    • Grand Jury information,

    • information obtained under immunity procedures, and

    • information that would identify a confidential informant or impair a criminal/civil investigation.

  2. Any state agency contractor, or federal employee who misuses FTI including state information that becomes FTI or makes an unauthorized access or disclosure of such information will be subject to the civil and criminal penalties under IRC 7213, 7213A, and 7431.

  3. Upon discovering a possible improper inspection or disclosure of FTI including breeches and security incidents by a federal employee, a state employee, or any other person, the individual making the observation or receiving information should contact the office of the appropriate Special Agent-in-Charge, Treasury Inspector General for Tax Administration (TIGTA). The TIGTA contact page on their web site is located at http://www.treasury.gov/tigta/oi_office.shtml.

  4. All unauthorized disclosures should be coordinated with the Office of Safeguards.

  5. For additional information on unauthorized disclosures, see IRM, Information Technology (IT) Security, Policy and Guidance, and IRM 11.3, Disclosure of Official Information.

Overview of EOS Quality Review

  1. EOS employee will conduct quality review on each step of EOS processing including the following:

    • Leads classification,

    • ERCS case controls, and

    • Data used in EOS initiatives.

Quality Review of Leads Classification

  1. The EOS manager is responsible for the quality of returns selected. A quality review covering the classification of leads will be conducted by the EOS manager or designee. The review will cover:

    • Performance of each EOS employee,

    • Orientation on classification objectives,

    • Instructions to EOS employee, and

    • Quality review procedures and documentation requirements.

  2. A 10 percent sample of each EOS employee's returns is recommended for review. Through classification reviews, the EOS manager or designee will determine whether:

    • Returns are selected for examination or accepted as filed in accordance with established procedures.

    • Accepted returns have little or no examination potential.

    • EOS Classification Checksheets are properly completed by including all Large, Unusual or Questionable (LUQ) issues.

    • The potential tax change is sufficient to warrant selection of returns.

    • EOS employee is maintaining a high level of technical proficiency, exercising good judgment in accepting and selecting returns, and effectively utilizing their time.

    • EOS employee needs additional training.

Quality Review of Data Used in EOS Initiatives

  1. Data quality is an important factor that directly relates to EOS initiatives. Data must be accurate to prevent unnecessary risk events especially when the data serves as evidence for agency program objectives. Inconsistent data may be disputed and crippling to the Service and all stakeholders. Validating data assures that it is consistently verifiable and reliable. Data obtained from internal, external, commercial and other government agencies sources will be reviewed for quality issues.

  2. As data quality issues are identified, excise employees should forward the following information to the EOS Data Quality Coordinator:

    • What appears to be the problem with the data?

    • What appears to have caused the problem?

    • What is required to correct the problem?

    • Does the problem put any initiative at risk for achieving its objective?

  3. The EOS Data Quality Coordinator will provide a monthly summary report of the accumulated data quality issues to EOS management. The EOS Data Quality Coordinator and management will collaborate on the following questions:

    • Are there errors in the data sources and, if so, can they be resolved?

    • Will the data problems create barriers to completing initiative objectives?

  4. The EOS Data Quality Coordinator will maintain a status report on each issue.

  5. EOS management will provide direction on which data quality problems should be addressed in a prioritized manner according to available resources.

  6. On a quarterly basis, EOS management should issue a report identifying issues with the quality of data including recommendations for corrections.

Manager/Employee Security Responsibilities for NDC Information

  1. EOS management will ensure that all their employees:

    • Receive a briefing or training annually on the responsibilities and rules of security.

    • Provide written acknowledgment that they will protect the JOC database system and all information stored therein by completing hard copy acknowledgments for the use of removal media for data transfer, rules of behavior, and On-Line 5081 access request.

    • Re-validate annually their user ID's.

Data Transfers to and from the NDC

  1. Data transfer to and from the NDC database must:

    • Not violate license or usage agreements.

    • Be labeled with the nature of the data and clearly marked SBU.

    • Be extracted to either CD, DVD, USB flash, or external disk drive using the Guardian Edge Removable Storage (GERS) encryption.

    • Be delivered by an IRS-authorized carrier with delivery only to the authorized recipient as identified in the approved removal e-mail.

    • First be approved by the EOS JOC Operations Manager via e-mail request with a copy to the JOC Information System Security Officer (ISSO). The request must include the data source(s), the need for the data, how it is to be used, and by whom.

JOC Partner Administrative Processes

  1. The JOC Steering Committee is responsible for approving membership with all new state taxing agency partners. Agencies must undergo a membership application process to join the JOC

  2. Agencies must complete a questionnaire indicating interest in learning more about joining the JOC. The questionnaire solicits information from the agency regarding:

    1. Organizational contacts,

    2. operations information, and

    3. technical structure.

  3. An agency completing the questionnaire confirms that agency executives responsible for committing resources are aware of the application submission and the potential commitment of resources in the future.

  4. Questionnaires are reviewed by the JOC Steering Committee with rejected questionnaires resulting in an oral and written notification to the agency from the JOC Steering Committee.

  5. Approved questionnaires result in the forwarding of a letter of application to the agency for membership into the JOC. Applications received must them be forwarded to the IRS HQ Governmental Liaison (HQ GL).

  6. The JOC Steering Committee will review application for membership and respond to applicants within 30 days of receipt. If membership application is approved, coordination shall take place with the HQ GL to secure MOU and Bylaws signatures.

  7. Approval of membership applications requires a two-thirds majority by the JOC Steering Committee. There are no predefined criteria against which an agency's application will be evaluated. A portfolio approach based on existing agency members along with agencies to be added will be used to evaluate applicants. Considerations will include, but not be limited to,

    • How similar or different the agency applying for membership is compared to existing member agencies,

    • point of taxation,

    • landlocked versus coastal agency,

    • neighboring agencies (with existing member agencies or other agency applicants),

    • fuel tax strategies utilized,

    • agency data available, and

    • commitment of resources.

New Partner Requirements

  1. New state taxing agency partnership requirements are to:

    1. Have a current Basic and Implementing Agreement with the IRS for sharing confidential tax information.

    2. Sign the JOC MOU and Bylaws.

    3. Provide a list of individual representatives and team members to the IRS disclosure managers and the agency disclosure officers in the affected jurisdictions. A copy of the list must be submitted to the JOC Steering Committee co-chairs and published as team rosters to be distributed to all JOC team members.

    4. Be in compliance with federal safeguards requirements including receiving confirmation from the IRS Office of Safeguards that the agency has a current, approved Safeguard Procedures Report (SPR) to cover the self-disclosure process and use of federal tax information.

Partnership Coordination with Privacy, Governmental Liaison, and Disclosure Office (PGLD)

  1. Coordination with the HQ PGLD Excise Tax Program Liaison will be initiated whenever agencies indicate a sincere interest in joining the JOC. When questionnaires or letters of application are provided by the JOC to an agency, the EOS employee will notify the PGLD office of the agency name, date, and agency employee contact. The PGLD will contact the local field PGLD to alert them that the agency has received the questionnaire/letter.

  2. If necessary, the local field PGLD can research the status of the agency's Basic and Implementing agreements, the status of the Office of Safeguard issues, any Office of Disclosure issues, and any relationship issues with the agency. If the agency does not have a Basic/Implementing Agreement or finds there are Safeguard issues, that information will be shared with the JOC as it will directly impact the agency's eligibility for joining the JOC. The JOC should contact the agency and inform them that they would be ineligible to apply for membership to the JOC without meeting the requirements as set forth in the MOU or Bylaws.

  3. If the agency contacts the field PGLD with questions they cannot answer, the field PGLD will contact the JOC. Field PGLD employees are relationship managers, facilitators, and marketers of all the initiatives stakeholders.. The field PGLD will facilitate a call with the JOC point of contact and the agency to answer questions.

  4. When the agency is notified of the JOC Steering Committee decision to accept/reject the application, the HQ and field PGLD offices should also be notified. If the agency is accepted, the field PGLD will provide copies of the IRS/Federal Highway Administration (FHWA) signed MOU and Bylaws to the state and initiate the process to secure agency signatures on the JOC MOU and Bylaws as well as the completed Safeguards Procedure Report (SPR) certification.

  5. The field PGLD will secure the list of individual state representatives and team members from the state per the Bylaws and provide the list to the IRS disclosure managers, state agency disclosure officers in the affected jurisdictions, and the JOC Operations Manager.

  6. The PGLD employee will send the signed JOC MOU and JOC Bylaws to the JOC point of contact.

State Partner Disclosure Requirements

  1. The JOC MOU Section 9A states that agencies that access federal tax information are subject to the provisions and safeguards of IRC 6103. The participating agency employees will initially have access to federal tax information as contractors to the IRS under provisions of IRC 6103(n). All participating agency personnel who are designated as IRS contractors must receive security clearances prior to having access to federal tax information.

  2. The JOC MOU constitutes a contract between the agencies and the IRS. Agency contractors are subject to the terms and conditions of the federal tax regulations at Section 301.6103(n)-1.

  3. The participating agency contractors will have access to various federal tax information using IRC 6103(n) as the basis for allowing disclosure of tax information that may go beyond their state jurisdiction. After a lead is developed and determined to be worked by a particular state tax agency, the assigned state employee will be permitted to self-disclose and use federal tax information for their agency tax administration purposes as provided for under IRC 6103(d) and in their individual MOU, Basic Agreement, and Implementing Agreement on Coordination of Tax Administration.

  4. Any agency or agency contractor who misuses federal tax information (which includes agency information that becomes IRC 6103 information), or makes an unauthorized access or disclosure of such information will be subject to the civil and criminal penalties described in IRC 7213, 7213A, and 7431. All records and documents collected, maintained, or generated by the IRS and/or disclosed to the participating agency and any information collected as a result of joint correspondence, joint interviews, or IRS administrative summonses, will be subject to the confidentiality requirements of IRC 6103(a).

  5. Federal tax returns and tax return information will not be disclosed to agency contractors without prior written approval of the IRS.

  6. Neither the IRS nor the participating agency tax agency will disclose return information that would identify a confidential informant or seriously impair any civil or criminal tax investigation.

  7. For state disclosure procedures, see IRM, Overview of Disclosure.

State Partner Safeguards Requirements

  1. All information obtained by the agencies must be safeguarded in accordance with the contract language for general services contained in exhibit 5 (or as may be renumbered and updated) of Pub 1075, Tax Information Security Guidelines for Federal, State and Local Agencies and Entities, and the agency’s current Safeguard Procedures Report (SPR). An agency’s SPR must describe their current operating procedures and safeguards measures.

  2. Agencies are required to amend or revise their SPR to include a full description of the self-disclosure process and use of the federal tax information. They must include the name, title, and phone number of the person within the agency who coordinates and logs the receipt as well as the distribution of the federal tax information self-disclosed.

  3. A copy of the signed and dated MOU must be included with the amendment or their revised SPR. The amendment or SPR must be submitted to the IRS Office of Safeguards within 30 days after the MOU becomes effective.

EOS Shared Site

  1. EOS internal process information will be posted to the EOS shared site. The site will be maintained by the Excise webmaster to whom changes must be submitted after approval from management. The EOS shared site includes, but is not limited to, the following items:

    • inventory reports,

    • compliance initiative charters,

    • abstract summary reports,

    • common EOS forms such as inventory templates, group mailbox request form, feedback sheet, excise group manager listing, zip code decoder, etc.

    • WORTS request site for managers, and

    • data source information.

EOS Program Monitoring

  1. EOS will develop an annual return delivery plan in accordance with guidelines found in IRM 1.5, Managing Statistics in a Balanced Measurement System. Plan information should be used for allocation of resources, workload selection, and assessment of program effectiveness.

  2. Non-filer workload can be estimated based on historical data. Historical data is available on the AIMS IVL by source code.

  3. EOS will provide monthly reports to Excise HQ management on the following:

    1. Delivery of leads/returns for classification,

    2. classification selection rates,

    3. survey rates before and after assignment and survey of excessive inventory,

    4. volume and timing of return orders, and

    5. accomplishment of excise examination goals.

  4. At a minimum, the EOS should monitor the following for cycle time:

    1. Average cycle time for open and closed cases, and

    2. average days in process for open and closed cases.

  5. At a minimum, each month, the EOS should monitor returns in the excise WMS by status codes 08, 10 and 12.

  6. At a minimum, the EOS should monitor the following for business results:

    1. Dollars per hour by activity code and project code,

    2. dollars per return by activity code and project code,

    3. return accomplishments,

    4. time applied, and

    5. large assessment cases.