1.4.51 Insolvency

Manual Transmittal

November 17, 2022

Purpose

(1) This transmits a revised IRM 1.4.51 Resource Guide for Managers, Insolvency.

Material Changes

(1) IRM 1.4.51.3.2, Protecting Taxpayer Rights. Incorporates IPUs: 20U1290 and 21U0814 issued 12/08/2020 through 06/08/2021. The following table shows substantive changes within this IRM revision.

IRM Change
IPU 20U1290 issued 12-08-2020 Throughout Editorial changes have been made throughout this IRM.
IPU 20U1290 issued 12-08-2020 Throughout Update IRM references and correct broken links
IPU 20U1290 issued 12-08-2020 IRM 1.4.51.9 (2) Adds a note to explain that developmental Bankruptcy Specialist (GS-07) and trainee Bankruptcy Specialist (GS-05) will be assigned cases generally at the grade 9 level. Provide guidance to managers regarding the cases that should be assigned to trainees and the degree of monitoring that must be exercise during training period.
IPU 20U1290 issued 12-08-2020 IRM 1.4.51.9 (3) Adds paragraph three to clarify that managers will use inventory and case grade reports to monitor that employees are not working over 25% direct time above grade.
IPU 20U1290 issued 12-08-2020 IRM 1.4.51.9.2 (1) Adds a note to provide guidance to managers regarding Chapter 7A cases that should be assigned to Bankruptcy Specialist initially graded below GS-09.
IPU 21U0814 issued 06-08-2021 IRM 1.4.51.3.2(2) TBOR content updated based on guidance from the Division Counsel/Associate Chief Counsel (National Taxpayer Advocate Program) and Branch 3 of the Associate Chief Counsel (Procedure and Administration).
.

Effect on Other Documents

IRM 1.4.51 dated February 12, 2020 is superseded. The following IRM Procedural Updates (IPUs), issued from December 8, 2020 through June 8, 2021 has been incorporated into this IRM: 20U1290 and 21U0814.

Audience

Small Business/Self-Employed, Specialty Collection - Insolvency Management

Effective Date

(11-17-2022)

Kareem Williams, Director Collection Policy

Program Scope and Objectives

  1. Purpose. This Internal Revenue Manual (IRM) section discusses responsibilities of managers in Field Insolvency (FI) and Centralized Insolvency Operation (CIO). While many topics are touched upon in this chapter, comprehensive guidance about all of them cannot be included here. Remain alert for references to other resources, such as related IRMs and websites and access that guidance to ensure a thorough understanding of topics. Specifically, IRM 1.4.51:

    1. Describes general administrative responsibilities required of insolvency group managers.

    2. Describes employee performance and development procedures.

    3. Prescribes internal control requirements.

    4. Provides guidance to group managers on the assignment and approval of work.

    5. Provides guidance for operational reviews by Territory / Operation Managers and Director.

  2. Audience. This IRM section is designed for use by Small Business/Self-Employed (SB/SE), Specialty Collection - Insolvency (SCI) management.

  3. Policy Owner. Director, Collection Policy, SB/SE.

  4. Program Owner. Collection Policy, SB/SE, Insolvency is the program owner of this IRM.

  5. Primary Stakeholders. The primary stakeholder is SB/SE Collection, Specialty Collection - Insolvency (SCI).

  6. Program Goals. This guidance is provided to communicate the managerial responsibilities to Insolvency group managers including performance management, assignment of work, approval of work, promoting quality casework, and internal group controls.

Background

  1. Internal Revenue Manual (IRM) 1.4.51, Resource Guide for Managers, Insolvency, contains procedures, guidance, and information for Insolvency group managers. The content includes general administrative responsibilities, performance management, internal controls, assignment of work, approval of work, quality reviews, and program reviews.

Authority

  1. 5 USC Part III, Government Organizations and Employees

  2. IRS Restructuring & Reform Act of 1998:

    • IRC1203, Termination of employment for misconduct

    • IRC 1204, Basis for evaluation of IRS employees

  3. IRC 6304, Fair Tax Collection Practices

  4. IRC 6320, Notice and Opportunity for Hearing Upon Filing of Notice of Lien

  5. IRC 6330, Notice and Opportunity for Hearing Before Levy

  6. IRC 6331, Levy and Distraint

  7. IRC 6672, Failure to Collect and Pay Over Tax or Attempt to Evade or Defeat Tax

  8. IRC 7213A, Unauthorized Inspection of Returns or Return Information

  9. IRC 7521, Procedures Involving Taxpayer Interviews

  10. 26 CFR 601.106, Appeals Functions

  11. 31 USC 3302, Custodians of Money

  12. 31 USC Chapter 53, Monetary Transactions

  13. Equal Employment Opportunity Commission (EEOC) Management Directive 715 (MD-715)

  14. Rev. Proc. 2012-18, Ex part Communications Between Appeals and Other IRS Employees

Responsibilities

  1. The Director, Collection Policy is the executive responsible for the policies and procedures to be employed by collection personnel.

  2. The Director, Specialty Collection - Insolvency (SCI) is responsible for program oversight.

  3. Insolvency Group Managers and Territory / Operation Managers are responsible for ensuring the guidance and procedures described in this IRM are complied with.

Program Management and Review

  1. Program Reports. Group managers are required to generate and approve end of month reports. Group managers are required to submit quarterly certifications of compliance with Section 1204 of the Internal Revenue Service Restructuring and Reform Act of 1998, prohibiting the use of tax enforcement results. Reports housed on the Automated Insolvency System (AIS) are used for group controls in the following areas: imminent collection and assessment statutes, no touch/activity, higher graded duties, and Notice of Federal Tax Lien (NFTL) determinations. Reports to help Insolvency managers are discussed throughout this IRM chapter, including in the exhibits. The required AIS Business Objects reports are described in IRM 5.9.16.1.4(1), Program Reports, and in IRM 1.4.51.8.3, Case Management Tools. Group managers are responsible for establishing and maintaining each of their employees’ Employee Performance File (EPF).

  2. Program Effectiveness.

    1. Operational and Program reviews are conducted on a yearly basis. See IRM 1.4.51.17.2, Operational Review, and IRM 1.4.51.17.5, Program Reviews, for more information. Operational Reviews are conducted within Specialty Collection - Insolvency (SCI). Program Reviews are conducted within Headquarters Collection Policy in collaboration with SCI.

    2. National quality reviews are conducted on a monthly basis. Consistency reviews are conducted at least annually. See IRM 1.4.51.16.1, NQRS, and IRM 1.4.51.16.2, EQ Consistency Reviews, for more information.

Program Controls

  1. Insolvency Managers are required to follow program management procedures and controls addressed in IRM 1.4.51.5.2, Reviews (Overview), IRM 1.4.51.15, Controls, and IRM 1.4.51.16, Quality.

Terms and Acronyms

  1. Frequently used terms used in this IRM along with their definition include:

    Term Definition
    Bargaining Unit employee An employee who is covered by the current National Agreement with the National Treasury Employees Union (NTEU).
    National Agreement The contract between the IRS and the National Treasury Employees Union (NTEU) which covers bargaining unit employees.
    Pyramiding An in-business taxpayer, not current with Federal Tax Deposits (FTDs) and with two or more balance due trust fund modules assigned to Field Collection.
    Representative A person who is authorized to represent a taxpayer before the IRS.

  2. Acceptable acronyms and abbreviations are found in the ReferenceNet Acronym Database, which may be viewed at: http://rnet.web.irs.gov/Resources/Acronymdb.aspx.

  3. Acronyms used specifically in this IRM section are listed below:

    Acronym Definition
    ACS Automated Collection System
    ADS Automated Discharge System
    AIS Automated Insolvency System
    ALS Automated Lien System
    APOC Automated Proof of Claim
    ASED Assessment Statute Expiration Date
    ATFR Automated Trust Fund Recovery
    AUR Automated Underreporter
    BAPCPA Bankruptcy Abuse Prevention and Consumer Protection Act of 2005
    BCCP Bankruptcy Code Compliance Program
    BEC Bankruptcy Exam Coordinator
    BFS Bureau of the Fiscal Service
    BOD Business Operating Division
    BU Bargaining Unit
    CAG Case Assignment Guide
    CASS Collection Automation Support & Security
    CIO Centralized Insolvency Operation
    CJE Critical Job Element
    CPM Confirmed Plan Monitoring
    CSED Collection Statute Expiration Date
    DDR Discharge Determination Report
    EDF Employee Drop File
    EEO Equal Employment Opportunity
    ENS Electronic Noticing System
    EPF Employee Performance File
    EPOC Electronic Proof of Claim
    EQRS Embedded Quality Review System
    FI Field Insolvency
    FTD Federal Tax Deposit
    GM Group Manager
    GRS General Records Schedule
    HCO Human Capital Office
    ICS Integrated Collection System
    IIP Insolvency Interface Program
    IRC Internal Revenue Code
    LAMS Litigation Accounts Management System
    LR Labor Relations
    LTS Litigation Transcript System
    NFTL Notice of Federal Tax Lien
    NMF Non-Master File
    NTEU National Treasury Employees Union
    NQRS National Quality Review System
    OI Other Investigation
    POC Proof of Claim
    ROTERs Records of Tax Enforcement Results
    RRA 98 Restructuring and Reform Act of 1998
    SERP Servicewide Electronic Research Program
    SETR Single Entry Time Reporting
    TAS Taxpayer Advocate Service
    TFRP Trust Fund Recovery Penalty
    TIN Taxpayer Identification Number
    TM Territory Manager
    WGI Within Grade Increase

Related Resources

  1. Document 11678, National Agreement - Internal Revenue Service (IRS) and National Treasury Employees Union (NTEU).

  2. Document 12990, Records and Information Management Records Control Schedules.

  3. Document 12656, Field Insolvency Embedded Quality Job Aid.

  4. Document 13097, Centralized Insolvency Operations Technical Team Leader’s Procedural Guide.

  5. Document 13219, Automated Insolvency System (AIS) - User Guide.

  6. Document 13163, Automated Proof of Claim (APOC) and APOC Amends - User Guide.

  7. IRM resources:

    • IRM 1.2.1, Servicewide Policy Statements

    • IRM 1.2.2, Servicewide Delegations of Authority

    • IRM 1.4.1, Management Roles and Responsibilities

    • IRM 1.4.1.3, Administrative Responsibilities

    • IRM 1.4.6, Managers Security Handbook

    • IRM 1.5.2, Uses of Section 1204 Statistics

    • IRM 1.15, Records and Information Management

    • IRM 5.9.5, Opening a Bankruptcy Case

    • IRM 5.9.12, Insolvency Automated Processes

    • IRM 5.13.1, Embedded Quality Collection Field Organizations Administrative Guidelines

    • IRM 6.430.2, Performance Management Program for Evaluating Bargaining Unit and Non Bargaining Unit Employees Assigned to Critical Job Elements (CJEs)

    • IRM 6.751, Discipline and Disciplinary Actions

    • IRM 6.800.2, IRS Telework Program

    • IRM 10.8.34, IDRS Security Controls

    • IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS), and Electronic Products and Services Support

    • IRM 25.1.8, Fraud Handbook, Field Collection

  8. Web Resources:

    • Critical Job Elements (CJE): http://hco.web.irs.gov/apps/cje/

    • Embedded Quality: http://eqrs.enterprise.irs.gov:8543/eqrs/common/eqrsSplash.jsp

    • Embedded Quality Review System (EQRS) Master Attribute Job Aid (MAJA): https://eqrs.enterprise.irs.gov:8543/eqrs/campus/maja/majaMain.do?eqType=e

    • Human Capital Office (HCO): http://hco.web.irs.gov/

    • iManage: https://portal.ds.irsnet.gov/sites/iManage/SitePages/Home.aspx

    • Internal Management Documents (IMD) for Interim Guidance Memo (IGM): http://imdtrack.web.irs.gov/search.aspx

    • My SB/SE: http://mysbse.web.irs.gov/default.aspx

    • New Manager Orientation (NMO) Support Center: http://hco.web.irs.gov/apps/leads/nmo.html

    • Office of Professional Responsibility: https://irssource.web.irs.gov/OPR/Pages/Home.aspx

    • Section 1203 / RRA 98: http://hco.web.irs.gov/lrer/conperf/1203issues/index.html

    • Servicewide Electronic Research Program (SERP): http://serp.enterprise.irs.gov/

    • Telework: http://hco.web.irs.gov/Telework/

    • Unauthorized access (UNAX): https://portal.ds.irsnet.gov/sites/vl003/lists/unax1/landingview.aspx

  9. General Records Schedule (GRS) 2.2, Employee Management Records.

Role of the Field Insolvency Manager and Centralized Insolvency Operation Manager

  1. Fundamental responsibilities for all managers are discussed in IRM 1.4.1 , Management Roles and Responsibilities. An Insolvency manager must provide oversight and direction in a number of areas, which will result in accomplishing the mission of the Internal Revenue Service. Oversight responsibilities include, but are not limited to:

    1. Ensuring case actions are timely and in accordance with current law, policies, and procedures.

    2. Ensuring employees maintain high standards of professionalism in all correspondence and telephone contacts with the public, internal customers, external customers, and coworkers.

    3. Ensuring taxpayer rights are observed and taxpayers and/or their representatives are advised of those rights and how to exercise them.

    4. Ensuring employees are aware of the role of the Taxpayer Advocate Service and the Low Income Tax Clinics (refer to Pub 4134, Low Income Taxpayer Clinic List), and the service these functions provide is properly communicated with taxpayers and/or their representative.

    5. Ensuring employees are aware of ongoing changes to the laws, policies, and procedures that relate to their responsibilities (preferably during group meetings).

    6. Addressing system issues that impact either internal or external customer needs.

    7. Ensuring cases are assigned timely and employee workload:- Reflects current priorities.- Reflects employee experience and skill level.- Addresses Servicewide objectives.- Protects public interests.- Allows for effective case processing.

    8. Helping employees make the appropriate next case decision.

    9. Ensuring employees are accountable for the appropriateness of their actions.

    10. Providing ongoing employee feedback that is candid and meaningful and will establish a basis for determining an accurate assessment of performance and developmental needs.

    11. Issuing the Critical Job Elements (CJE) timely and evaluating employee performance against their CJEs.

    12. Creating and maintaining a work environment that will promote team work, positive working relationships, and increased employee satisfaction.

    13. Ensuring employees have necessary functioning equipment and supplies.

  2. Responsibilities also include:

    1. Developing employees.

    2. Evaluating employee performance and providing counseling.

    3. Addressing employee conduct issues.

    4. Fostering good working relationships.

    5. Defining goals and course of action.

    6. Assigning and directing work.

    7. Instructing employees in the application of procedures and guidelines.

    8. Displaying integrity in all actions.

  3. Managers are empowered to address performance deficiencies within their group. This may be accomplished through reviews and/or by requiring concurrence with performing specific actions.

    Example:

    It is found that Notice of Federal Tax Lien (NFTL) re-filing determinations are not being made in accordance with IRM 5.9.5.9.2, Refiling Notices of Federal Tax Lien (NFTLs). The manager can require the employee to notify him or her at case closure of Automated Insolvency System (AIS) history documentation of the NFTL refiling determination.

    For additional direction regarding performance issues see Exhibit 1.4.51-1, Suggested Action Steps for Unacceptable Performance.

  4. Managers oversee group remittance processing activities, including monitoring Form 5919 , Teller's Error Advice, sent to their group. See IRM 5.1.2.5.6, Responding to Form 5919.

  5. Managers are responsible for ensuring employees have access to the IDRS command codes necessary to perform their assigned tasks and required research. When an employee is expected to be away from their terminal for more than two weeks or longer the employee should lock their profile to avoid being locked out by Data Security. The CC LOKME is used to lock IDRS. Refer to IRM 10.8.34.6.2.2.4.2, Employee Self-Profile Locking (LOKME), for additional information.

  6. Managers coordinate IDRS security with their assigned Unit Security Representative (USR), otherwise known by their organizational title: Data Security Analyst (DSA). See IRM 5.1.25.2, IDRS Security Personnel, for additional information.

    Note:

    Managers are responsible for addressing the USR/DSA emails regarding IDRS related inquires within five business days.

Acting Manager Assignments and Designations

  1. You must designate with a formal delegation an acting manager during your periods of absence. Managerial tasks to be performed and those to be deferred may depend on the duration of the assignment. Refer to Document 11678, National Agreement - IRS/NTEU, for certain restrictions on performance evaluations. Assignments should be agreed on between you and the acting manager in advance. Specific expectations should be given at the beginning of each assignment. This will form the basis for your feedback on performance of the acting assignment.

  2. For the delegated acting manager you must utilize discretion to determine whether inventory level needs to be adjusted for the action. Factors to consider are:

    • length of acting assignment and

    • duties to be performed during this assignment.

  3. You may designate specific tasks even though you are not absent. This enables a manager to provide developmental assignments to employees aspiring to the next level to gain useful experience. In this situation, no "acting" assignment or delegation exists; therefore tasks reserved to managers (i.e., managerial approvals, callbacks requested by the taxpayer) cannot be delegated.

Communication of Expectations

  1. When a new group is established or a new manager is assigned to an existing group, a meeting with the employees must be held within the first 30 days. At this meeting the manager will communicate expectations to include the following topics:

    • Safety and security

    • Group procedures

    • Case work

    • Use of time in the office and telework

    • Timeliness of case activity

    • Reasonable time frames for case actions. (See IRM 5.9.5.5, Initial Processing Actions, IRM 5.9.5.4, Automated Insolvency System (AIS) Documentation, and IRM 5.9.16, Insolvency Case Monitoring, for timeliness and time frames.)

    • Case Review Schedule

    Reminder:

    These expectations should also be reviewed at the beginning of each fiscal year.

    Note:

    This meeting is considered a 7114 meeting. Local National Treasury Employees Union (NTEU) chapter(s) must be notified of the meeting in accordance with Article 8, Union Rights, of the National Agreement - IRS/NTEU.

  2. When a new employee is assigned to an existing group, the group manager must meet with the new employee to discuss managerial expectations (see (1) above) and ensure appropriate Business Entitlement Access Request System (BEARS) are completed and processed. This meeting is considered a 7114 meeting. See the Note in (1) above.

Group Meetings

  1. Regular group meetings will be held as necessary to review items such as the following:

    • Directives from the Director, Territory / Operation Manager, Department Manager, and Headquarters

    • Procedural memoranda

    • IRM changes

    • Case resolution techniques

    • Changes in condition of employment

    • Automation issues

    • Mandated topics not available on other media

    • General group (employee) concerns

    • IRS employee engagement issues

    • Annual IRS Employee Survey results

    • Complex cases to brainstorm ideas to assist in taking appropriate closing actions

    • Case resolution techniques in order to share best practices

    Note:

    Regular group meetings are not ordinarily considered 7114 meetings. The Union entitlement arises where there is a discussion of a personnel policy, practice, or other general condition of employment.

    Example:

    A discussion at a group meeting on the need to make timely TFRP determinations or how to handle a particular type of case would not ordinarily be considered 7114 issues. A group meeting addressing changes in condition of employment would ordinarily be considered a 7114 meeting.

    Managers should seek guidance and advice from their servicing Labor Relations (LR) Section if they are unsure whether an agenda item for a group meeting constitutes a 7114 issue. Article 8, Section 1, Union Rights, of the National Agreement - IRS/NTEU also provides guidance on 7114 Meetings. For regularly scheduled formal discussions and non-recurring formal discussion, provide the Union a notice and meeting agenda no less than five workdays in advance.

End of Month (EOM) Processing

  1. Managers are responsible for reviewing time reported by their employees to ensure accuracy. Using Integrated Collection System (ICS), verify time prior to End of Month (EOM) processing (i.e., no later than close of business on the last Friday of the monthly reporting period). Consider the following:

    1. Be alert for, and/or address as appropriate, issues such as: potentially excessive administrative time, discrepancies related to credit, compensatory, holiday, training time, etc.

    2. Perform weekly time verification and checks for all employees.

    3. Refer to IRM 5.2.1, Collection Time Reporting, for specific information about Group Manager (GM) responsibilities related to time reporting.

Functional Role

  1. The Insolvency function is comprised of two operations, Field Insolvency (FI) and the Centralized Insolvency Operation (CIO), which must work together to provide customer service while addressing employee satisfaction in delivering improved business results. Three separate business units are directly involved in bankruptcy processing:

    • Specialty Collection - Insolvency (FI and CIO)

    • Collection Policy, Insolvency

    • SB/SE Counsel

  2. Field Insolvency (FI). FI has many offices throughout the country. FI:

    • Works all aspects of Chapter 11, Chapter 12, Assignments, and Receiverships.

    • Completes initial case review of Chapter 7 Asset (7A) and Chapter 13 cases.

    • Works Chapter 7 No Asset (7N) Large Dollar cases referred to them from CIO.

    • Refers Chapter 9 and Chapter 15 cases to Counsel for procedural guidance after clerical processing has been completed.

    • Responds to "complex issues" on any case regardless of chapter. (See IRM 5.9.1.4(5), Complex Issues.)

  3. Centralized Insolvency Operation (CIO). The CIO is located in Philadelphia. The CIO:

    • Performs initial clerical processing on cases for all bankruptcy chapters.

    • Works Chapter 7 No Asset (7N) cases from 341 notice to closure including screening large dollar cases for exempt and abandoned property.

    • Works Chapter 7 Asset (7A) and Chapter 13 cases after initial case review until closure.

    • Forwards Chapter 9 and Chapter 15 Insolvency Interface Program (IIP) reports and Chapter 11 Status 22 reports to FI to work.

    • Completes mirroring of accounts.

    • Reinstates all installment agreements at case closure, when the case meets IA reinstatement criteria.

    • Sends complex issues to FI to work.

  4. Collection Policy. Collection Policy, Insolvency establishes and oversees policy for the entire Insolvency program. Collection Policy, Insolvency:

    • Owns IRM 5.9, IRM 5.17.8 - 5.17.11, and IRM 1.4.51.

    • Prepares IRM Procedural Updates (IPU) and Interim Guidance Memorandums (IGM).

    • Owns AIS and all associated subsystems (APOC, EPOC, ENS, ADS, and IIP).

    • Makes all policy decisions affecting Insolvency as an enterprise covering both the CIO and Field.

    • Reviews FI and CIO procedures, alerts, training materials, and job aids.

    • Owns the Bankruptcy Law Advisory Rules Engine (BLARE) information system and participates on the BLARE rules committee.

    • Submits requests for systems updates.

    • Responds to suggestions made through Form 13380, I Suggest, Servicewide Electronic Research Program (SERP) Feedback, and the Employee Suggestion Program.

    • Interacts with other National Office analysts on issues that impact bankruptcy processing.

    • Clears IRM bankruptcy sections written for other programs, such as Field Collection and Examination.

    • Handles technical questions from FI and CIO.

    • Performs program reviews of FI and CIO.

  5. SB/SE Counsel Coordination. If an issue arises jeopardizing the government's best interests that cannot be resolved by Insolvency's contacting the debtor's attorney directly, Insolvency, depending on IRM criteria, may coordinate action(s) with Area Counsel, Department of Justice (DOJ), or other legal functions. (See IRM 5.9.4.15, Referrals - Representing IRS in Bankruptcy Court, IRM 5.9.4.15.1, Direct Referrals, IRM 5.9.4.15.2, Referrals to Counsel (Non-Direct Referrals), and IRM 5.9.4.15.3, Significant Bankruptcy Case Referrals.)

General Managerial Responsibilities

  1. IRM 1.4.1.3, Administrative Responsibility, contains information about general managerial responsibilities. Place special emphasis on responsibilities shown in the following sections.

Administrative

  1. Group managers are responsible for oversight of certain administration functions for their employees including but not limited to:

    1. Overseeing the time reporting process.

    2. Maintenance of time and attendance records.

    3. Certifying overtime records.

    4. Approving scheduled and unscheduled leave.

    5. Controlling and approving travel.

    6. Maintaining safe working conditions.

    7. Holding group meetings.

    8. Keeping employees current on all applicable policies and procedures.

    Other Administrative tasks include, but are not limited to:
    • Ensuring group End of Month reports are completed correctly (verified, generated, and approved) by the due date.

    • Completing quarterly Section 1204 self certifications.

    • Oversight of supply procurement.

    • Maintaining Employee Performance File (EPF) and Drop Files for each employee.

      Caution:

      Managers may delegate certain duties to a secretary / administrative assistant; however, they retain oversight responsibility for those tasks.

  2. Items managers must update individually with each employee annually include, but are not limited to:

    • Form 6774, Receipt of Critical Job Elements and Fair and Equitable Treatment of Taxpayers Retention Standard

    • Form 11386, IRS Telework Agreement for Bargaining Unit (BU)

      Note:

      Per IRM 6.800.2.1.3.2, Manager Responsibilities, under (3)(i), while managers must review all Telework Agreements every year, if there are no changes to the existing Telework Agreement, there is no need to take any action to have the employee update it annually.

    • Form 7995, Outside Employment or Business Activity Request

    • Form 6850-BU, Bargaining Unit Performance Appraisal and Recognition Election

  3. Resources:

    • IRM 1.4.1.3, Administrative Responsibilities

    • Document 12990, Records and Information Management Record Control Schedules

    • New Manager Orientation: http://hco.web.irs.gov/apps/leads/nmo.html

    • iManage: https://portal.ds.irsnet.gov/sites/iManage/SitePages/Home.aspx

Employee Performance File (EPF)
  1. Managers are responsible for establishing and maintaining an EPF for each of their employees. The EPF is a system consisting of all performance ratings and other performance-related records maintained in accordance with 5 CFR 293, Subpart D.

  2. Managers are responsible for ensuring the effective use of the EPF by:

    1. Ensuring that the proper documents are included in each EPF.

      Note:

      See IRM 6.430.2.3.5, Employee Performance File (EPF).

    2. Ensuring that filing and purging of performance related documents and records are in compliance with requirements.

    3. Keeping all performance records and documents secured.

    4. Forwarding EPF records of employees transferring to other Treasury Bureaus or to a different post of duty or manager within the Service.

    5. The National Archives and Records Administration (NARA) approved General Records Schedule (GRS) 2.2, Employee Management Records, Item 70, Employee performance file system records, provides mandatory records retention and disposition instructions for administrative functions that are common to all government agencies to prevent inadvertent/unlawful destruction of records.

  3. Form 6774, Receipt of Critical Job Elements and Fair and Equitable Treatment of Taxpayers Retention Standard, is maintained in the EPF. Managers must update the form annually and ensure it is signed and dated. (See IRM 1.5.3.3, Retention Standard for the Fair and Equitable Treatment of Taxpayers.)

  4. Recordations are included in the EPF. A recordation is defined as a manager's written record evaluating an employee in a positive or negative manner. For BU employees, a recordation must be furnished to an employee within fifteen (15) workdays of the time the manager becomes aware, or should have been aware, of the event that it addresses. If it is not furnished within fifteen (15) workdays, it cannot become part of the EPF.

  5. Form 6850-BU, Bargaining Unit Performance Appraisal and Recognition Request, is maintained in the EPF. Electronic signatures may be used on Form 6850-BU, processed through HR Connect, however paper copies of the form must be maintained in the EPF.

  6. The EPF is maintained in addition to and separate from the Employee Drop File (EDF). The EPF is not the same as the Official Personnel File (OPF). (See IRM 1.4.1.8.4, Official Personnel File (OPF).)

  7. For additional information regarding the specific items to be placed in the EPF and the retention period, refer to:

    • Human Capital Office (HCO) website at: http://hco.web.irs.gov/

    • Document 11678 , National Agreement - IRS/NTEU, Article 12, Performance Appraisal System:

    • IRM 6.430.2.3.5, Employee Performance File (EPF)

    • The assigned Labor Relations Specialist

    • HR Connect: https://www.hrconnect.treas.gov/psp/ps/?cmd=login&languageCd=ENG&

    • General Records Schedule (GRS) 2.2, Employee Management Records, Item 70, Employee performance file system records

Employee Drop File (EDF)
  1. In addition to the EPF, a second file should be established for each employee. This is referred to as the Drop File. The Employee Drop File is for other documentation not related to performance.

  2. The Drop File should contain anything that is not performance related, such as leave counseling and copies of disciplinary actions. Questions about the use of a Drop File can be directed to the Labor Relations office.

Medical Information
  1. Employee medical information must be maintained separately from the EPF and EDF.

  2. For more information, see:

    • IRM 6.630.1.5.4, Safeguarding Medical Information

    • HCO website: http://hco.web.irs.gov/

Protecting Taxpayer Rights

  1. A primary responsibility of managers is to monitor employee practices and actions to ensure that taxpayer rights are always observed. In fact, Congress has now directed the IRS to ensure that all employees are aware of taxpayer rights. See Consolidated Appropriations Act, 2016, Public Law No. 114-113, Division Q, Title IV, Sec 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights.

  2. The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For additional information about the TBOR, see https://www.irs.gov/taxpayer-bill-of-rights. (See Pub 1, Your Rights as a Taxpayer):

    1. The Right to Be Informed: Taxpayers have the right to know what they need to do to comply with the tax laws. They are entitled to clear explanations of the laws and IRS procedures in all tax forms, instructions, publications, notices, and correspondence. They have the right to be informed of IRS decisions about their tax accounts and to receive clear explanations of the outcomes.

    2. The Right to Quality Service: Taxpayers have the right to receive prompt, courteous, and professional assistance in their dealings with the IRS, to be spoken to in a way they can easily understand, to receive clear and easily understandable communications from the IRS, and to speak to a supervisor about inadequate service.

    3. The Right to Pay No More than the Correct Amount of Tax: Taxpayers have the right to pay only the amount of tax legally due, including interest and penalties, and to have the IRS apply all tax payments properly.

    4. The Right to Challenge IRS’s Position and Be Heard: Taxpayer have the rights to raise objections and provide additional documentation in response to formal IRS actions or proposed actions, to expect that the IRS will consider their timely objection and documentation promptly and fairly, and to receive a response if the IRS does not agree with their position. .

    5. The Right to Appeal an IRS Decision in an Independent Forum: Taxpayers are entitled to a fair and impartial administrative appeal of most IRS decisions, including many penalties, and have the right to receive a written response regarding the Office of Appeals’ decision. Taxpayers generally have the right to take their cases to court.

    6. The Right to Finality: Taxpayers have the right to know the maximum amount of time they have to challenge the IRS’s position as well as the maximum amount of time the IRS has to audit a particular tax year or collect a tax debt. Taxpayers have the right to know when the IRS has finished an audit.

    7. The Right to Privacy: Taxpayers have the right to expect that any IRS inquiry, examination, or enforcement action will comply with the law and be no more intrusive than necessary, and will respect all due process rights, including search and seizure protections and will provide, where applicable, a collection due process hearing.

    8. The Right to Confidentiality: Taxpayers have the right to expect that any information they provide to the IRS will not be disclosed unless authorized by the taxpayer or by law. Taxpayers have the right to expect appropriate action will be taken against employees, return preparer, and others who wrongfully use or disclose taxpayer return information.

    9. The Right to Retain Representation: Taxpayers have the right to retain an authorized representative of their choice to represent them in their dealings with the IRS. Taxpayers have the right to seek assistance from a Low Income Taxpayer Clinic if they cannot afford representation.

    10. The Right to a Fair and Just Tax System: Taxpayers have the right to expect the tax system to consider facts and circumstances that might affect their underlying liabilities, ability to pay, or ability to provide information timely. Taxpayers have the right to receive assistance from the Taxpayer Advocate Service if they are experiencing financial difficulty or if the IRS has not resolved their tax issues properly and timely through its normal channels.

  3. Ensure that all employees are aware of the role the Taxpayer Advocate Service (TAS), and that this information is properly communicated to taxpayers and their representatives, as appropriate. TAS is an independent organization within the IRS that ensures tax problems that have not been resolved through normal channels are promptly and fairly handled. To determine if a case meets TAS criteria, see IRM 13.1.7.2, TAS Case Criteria. Access to TAS can be obtained by calling their toll-free number 877-777-4778, researching Pub 1546, Taxpayer Advocate Service - We are Here to Help You, or visiting their website https://www.irs.gov/taxpayer-advocate.

  4. IRC 1203 of the Internal Revenue Service Restructuring and Reform Act of 1998 (RRA 98) calls for the termination of any employee of the Internal Revenue Service if there is a final administrative or judicial determination that the employee willfully committed any act or omission described below:

    1. Failing to obtain required approval signatures when making a seizure.

    2. Providing a sworn false statement in a "material matter" concerning a taxpayer.

    3. Violating the constitutional rights of or discriminating against taxpayers, taxpayer's representatives or employees.

    4. Falsifying or destroying documents to cover a mistake concerning a taxpayer.

    5. Receiving a criminal conviction or civil judgment for assault or battery on a taxpayer, taxpayer's representative or employee.

    6. Violating the Internal Revenue Code (IRC), IRS regulations or policies to retaliate against or harass taxpayers, taxpayers’ representatives, or employees.

    7. Willful misuse of IRC 6103, Confidentiality and Disclosure or Returns and Return Information, to conceal information from Congressional inquiry.

    8. Failing to file a federal tax return on or before its due date, unless it is due to reasonable cause.

    9. Understating federal tax liability, unless it is due to reasonable cause.

    10. Threatening an audit for personal gain or benefit.

  5. There is an important distinction between evaluating performance under CJE 2, Taxpayer Rights, and evaluating compliance with the Retention Standard for the Fair and Equitable Treatment of Taxpayers. See the Human Capitol Office website http://hco.web.irs.gov/perfmgmt/evaluation/evalperf/nonmgrpolicy.html for more information.

  6. Resources:

    • Form 6774, Receipt of Critical Job Elements and Retention Standard

    • IRM 6.430.2.4.7, Rating Performance Against The Retention Standard for The Fair and Equitable Treatment of Taxpayers

    • IRM 6.430.2.2.5, Discussing The Retention Standard for the Fair and Equitable Treatment of Taxpayers

    • IRC1203 Issues: http://hco.web.irs.gov/lrer/conperf/1203issues/index.html

    • Retention Standard Resources: http://hco.web.irs.gov/perfmgmt/evaluation/evalperf/nonmgrpolicy.html

    • Office of Professional Responsibility website: https://irssource.web.irs.gov/OPR/Pages/Home.aspx

    • Pub 947, Practice Before the IRS and Power of Attorney

    • IRM 5.1.23, Taxpayer Representation

    • Taxpayer Bill of Rights:https://irssource.web.irs.gov/SitePages/TaxpayerBillOfRights.aspx

Direct Contact For Taxpayers With/or Requesting Representation
  1. Managers should ensure that their group is in conformance with IRC 7521, Procedures Involving Taxpayers Interview. It is also important to ensure that employees comply with guidelines about direct contact with taxpayers with representatives. Specifically, employees are required to:

    1. Stop the interview with a taxpayer (unless required by court order) whenever a taxpayer requests to consult with a representative (e.g., accountant, CPA, attorney, or enrolled agent, who is permitted to represent taxpayers before the IRS).

    2. Obtain managerial approval to contact the taxpayer instead of the representative, if the representative is responsible for unreasonably delaying or hindering the completion of a collection action. See IRM 5.1.23.6, By Passing a Taxpayer Representative

    Exception:

    Per IRM 5.1.23.6(6), By Passing a Taxpayer Representative, the IRS may work directly with a taxpayer to resolve an issue on the taxpayer's account if: 1) The taxpayer initiates the contact to resolve the issue on the account 2) The taxpayer expresses a specific desire to resolve the issue without the involvement of the representative after the IRS employee has advised the taxpayer of the current representation, and 3) The taxpayer's desire to have the IRS work directly with the taxpayer instead of the representative is properly documented in the case file.

  2. Examples of steps managers can take to ensure compliance by their employees are:

    • Group meetings

    • Case reviews

    • Workload reviews

    • Field visitations

    • Office visitations

    • Taxpayer/representative inquiries (if necessary)

Recording Taxpayer Interviews
  1. A taxpayer or representative may request to use audio or video equipment to record an in-person interview. See IRM 5.1.12.3, Taxpayer Recording of Interviews, for information on responding to such requests. The right to make an audio recording does not extend to telephone interviews.

Fair Tax Collection Practices
  1. IRC 6304, Fair Tax Collection Practice, imposes certain restrictions with respect to tax collection. During a case review or upon receiving a complaint from a taxpayer, managers may identify a potential violation of those restrictions. Potential employee violations of IRC 6304 must be reported to the assigned Labor Relations (LR) Specialist by the close of the next business day following notification of the alleged violation.

  2. To ensure collected data is complete and accurate, use the following IRC 6304 issue codes when reporting the potential violation. Labor Relations uses these codes for tracking on the Automated Labor and Employee Relations Tracking System (ALERTS).

    • 141 - Contact with TP at Unusual Time/Place: Contacting a taxpayer before 8:00 am or after 9:00 pm, or at an unusual location or time, or location known or which should be known to be inconvenient to the taxpayer.

    • 142 - Contact TP without Rep: Contacting a taxpayer directly without the consent of the taxpayer’s Power of Attorney.

    • 143 - Contact at a TP Employer, Prohibited: Contacting a taxpayer at their place of employment when it is known or should be known that the taxpayer’s employer prohibits the taxpayer from receiving such communication.

    • 144 - Taxpayer Harassment: Any allegation of taxpayer harassment should be reviewed along with the Internal Revenue Code (IRC 6304) because the provision is intended to be applied in a general manner when evaluating the alleged employee misconduct. Conduct which is intended to harass a taxpayer, or conduct which uses or threatens to use violence or harm is an absolute violation of the IRC.

    • 145 - Taxpayer Abuse: Any allegation of taxpayer abuse should be reviewed along with the Internal Revenue Code (IRC 6304) because the provision is intended to be applied in a general manner when evaluating the alleged employee misconduct. The use of obscene or profane language towards a taxpayer is an absolute violation of the IRC.

    • 146 - Continuous Phone Harassment: Causing a taxpayer’s telephone to ring continuously with harassing intent.

    • 147 - Phone Call without ID Disclosure: Contacting a taxpayer by telephone without providing a meaningful disclosure of the IRS employee’s identity.

  3. If violations are confirmed, work with a LR Specialist to determine the next appropriate action.

  4. Resources:

    • IRM 5.1.10.6, Fair Tax Collection Practices

    • IRM 1.5.3.3, Retention Standards for the Fair and Equitable Treatment of Taxpayers

    • IRM 6.430.2.4.7, Rating Performance Against The Retention Standard for the Fair and Equitable Treatment of Taxpayers

Ex Parte Communication With Appeals/Managerial Oversight
  1. An “ex parte communication” is a communication that takes place between any Appeals employee and employees of other IRS functions, without the taxpayer/representative being given an opportunity to participate in the communication. The term includes all forms of communication, oral or written. Written communications include those that are manually or electronically generated. Rev. Proc. 2012-18, Ex Parte Communications Between Appeals and Other Internal Revenue Service Employees, applies to communications that take place after May 15, 2012, and clarifies the rules regarding ex-parte communications.

    Note:

    For additional information on the ex-parte communication rules, see IRM 8.1.10 Ex-Parte Communications

    .

  2. Prior to approving Collection Due Process (CDP) cases for transmittal to Appeals, review Form 14461, Transmittal of the CDP/Equivalent Hearing Request.

    • Ensure that narrative statements are limited to a neutral list of documents and neutral statements regarding actions taken and documented in the case history without any further discussion regarding the strengths and weaknesses of the taxpayer’s appeal.

    • Ensure that no prohibited ex-parte communications are included before approving the transmittal of the case to Appeals.

  3. Managers must also ensure that no prohibited ex-parte communications are included in Trust Fund Recovery Penalty (TFRP) case files or the AIS/Automated Trust Fund Recovery Program (ATFR) case history before approving the transmittal of the case to Civil Enforcement Advice and Support Operations (CEASO).

  4. If a taxpayer submits a written appeal after a (non-TFRP) Penalty Abatement Request is denied, and Appeals consideration is necessary, employees will forward the appeal to their manager for review and concurrence. The manager ensures that the AIS history is attached to the appeal request and that no prohibited ex-parte communications are included before approving the transmittal of the case to Appeals. If the case history contains commentary that is determined to violate the ex-parte communication rules, take appropriate action, which could include sharing the information with the taxpayer, and affording the taxpayer a reasonable period of time within which to respond, or other remedy within the discretion of Appeals at the time it is sent to Appeals.

  5. If the appeal contains new information that requires additional investigation or Integrated Collection System (ICS) documentation, the caseworker must secure managerial concurrence of the decision to sustain penalty abatement denial. If the caseworker is unable to make contact with the taxpayer within a reasonable time period, the caseworker will forward the case file to the GM and the GM will take the following actions:

    • Prepare a letter to the taxpayer that identifies the new information and a brief summary of the results of the additional investigation.

    • Document issuance of the letter to the taxpayer in the case history and attach a copy of the letter to the taxpayer appeal.

    • Ensure that the case history is attached to the appeal request and that no prohibited ex parte communications are included before approving the transmittal of the case to Appeals.

  6. Fast Track Mediation (FTM) can be used for TFRP protests as well as CDP and Equivalency Hearings (EH). The prohibition against ex-parte communications between Appeals employees and originating function employees does not apply to FTM because the Appeals employees are not acting in their traditional Appeals settlement role. Ex-parte communications, such as a private caucus between the Appeals mediator and Collection employees during the course of the mediation session, are permissible under the ex-parte communication rules.

  7. Resources:

    • IRM 5.1.9.5, Communications with Appeals

    • IRM 5.1.9.3.3.2, Sending Hearing Request to Appeals

    • IRM 8.1.10.5, Opportunity to Participate

    • IRM 5.1.15.16.4, Penalty Relief Denial and Appeals

    • IRM 5.7.6, Trust Fund Penalty Assessment Action

IDRS Security

  1. Integrated Data Retrieval System (IDRS) security briefings are included in the mandatory Annual On-Line Briefings. IDRS security should also be reinforced through discussions at group/unit meetings.

  2. Employees should be reminded to complete Form 11377-E, Taxpayer Data Access, if an account is inadvertently accessed or otherwise applicable.

  3. IRM 10.8.34, IDRS Security Controls, requires managers to review periodic IDRS Security reports for their groups. In Insolvency, primary responsibility for those reviews rests with Collection Automation Support & Security (CASS). Managers may be contacted by a CASS representative if they are unable to resolve a potentially questionable access made by an employee.

  4. Generally, CASS will contact the manager via secure e-mail. If contacted, the manager should take the following steps:

    • Take appropriate action to determine whether or not there was a business reason for the access. Actions may include conversations with the employee, review of case inventory, review of IDRS case controls, use of IDRS Online Reports Services (IORS) queries, review of audit trails, determining if access was by automated process, etc.

    • Provide feedback about their findings to CASS within five business days of their request

  5. Resources:

    • IRM 10.8.34, IDRS Security Controls

    • Form 11377-E, Taxpayer Data Access

    • Unauthorized Access of Taxpayer Accounts (UNAX): https://portal.ds.irsnet.gov/sites/vl003/lists/unax1/landingview.aspx.

Employee Safety/Security

  1. Safety and security is a high priority. Managers must become familiar with their responsibilities to ensure workplace safety for everyone.

  2. See IRM 5.1.3, Safety, Security, and Control, for information about safety and security topics.

  3. Resources:

Working With NTEU

  1. Group Managers who supervise bargaining unit (BU) employees must:

    1. Notify the requisite chapter(s) regarding 7114 meetings when they plan to discuss changes in personnel policies, practices and working conditions with their employees. Generally, five workdays notice is provided. See Article 8, Union Rights, of the National Agreement - IRS/NTEU at: http://hco.web.irs.gov/lrer/negotiations/natagree/index.html

    2. Make sure employees have the opportunity to be represented at formal discussions regarding employee grievances. See IRM 6.771.1, Agency Grievance System (AGS), and Document 11678 National Agreement - IRS/NTEU, other personnel matters, and conduct issues.

  2. See Article 8 of the National Agreement - IRS/NTEU for more information about how to identify 7114 meetings. Contact a LR Specialist if assistance is needed to determine if a meeting is a 7114 meeting.

  3. Resources:

    • IRM 1.4.1.4, Agreements with NTEU, or contact the assigned Labor Relations Specialist.

    • IRM 6.771.1, Agency Grievance System (AGS)

    • National Agreement - IRS/NTEU: http://hco.web.irs.gov/lrer/negotiations/natagree/index.html.

Functional Security Reviews

  1. Insolvency managers (or their designated representative) will conduct annual security reviews per guidance in IRM 1.4.6.7.1, Functional Reviews. The review must be documented and a copy of the documentation provided to the next level of management. Insolvency managers may use a Form 12149, Functional Security Reviews for Managers, to document their review. If another form of documentation (such as a memo) is used, managers should ensure that it covers all items shown on Form 12149 and contains the printed name/title of reviewer, signature of reviewer, and date of review.

  2. Managers should refer to IRM 1.4.6, Managers Security Handbook, for Servicewide guidance about their responsibilities.

  3. If a manager's reviews reflect that an employee repeatedly fails to observe security protocols, the manager should contact the LR specialist to determine the next appropriate action.

Case Related

  1. Casework. Managers must ensure Insolvency case actions comply with the requirements of the Bankruptcy Code Compliance Program (BCCP) while protecting the government's interest and educating debtors on their payment and filing responsibilities.

  2. Stay Violations. Insolvency managers oversee resolutions of Bankruptcy Code stay violations ensuring corrective actions are initiated no later than two work days after identification by Insolvency caseworkers or notification from taxpayers, their representatives, other government agencies, or other IRS functions. IRM 5.9.3.5, Automatic Stay, gives an in depth discussion of the nature of stay violations.

  3. Discharge Violations. When violations of the discharge injunction are identified, Insolvency managers must ensure caseworkers initiate resolutions of the violations no later than two work days after identification or notification. If the IRS receives adequate notice of the bankruptcy discharge, violations may occur after Insolvency has adjusted an account through the Automated Discharge System (ADS) or has made a manual adjustment. Violations can also arise while Insolvency's adjustment requests are pending. IRM 5.9.17.9, Discharge Injunction,, provides more information on this topic.

  4. Review of Closed Cases. Referrals from other IRS functions must be reviewed by Insolvency when a taxpayer facing collection claims a liability is no longer due because of a bankruptcy discharge. Insolvency must provide guidance concerning the dischargeability of periods to all other IRS functions.

  5. AIS Documentation. Insolvency managers must direct subordinates to document all actions related to the IRS's involvement in a bankruptcy proceeding in the AIS history, also known as the History screen. Insolvency is the primary repository of bankruptcy-related case actions for all functions of the IRS. (See IRM 5.9.5.4, Automated Insolvency System (AIS) documentation.)

  6. Objections. Whenever possible Insolvency administratively resolves objections to the IRS's actions in bankruptcy, usually involving proofs of claim, that otherwise would be handled by the US Attorney, Department of Justice (DOJ), or Area Counsel. Case specific matters that cannot be resolved administratively, such as objections to plan confirmation or requests for conversion or dismissal, are referred to Area Counsel, the US Attorney, or DOJ.

  7. Damage Claims. Insolvency managers must process administrative damage claims pursuant to Treas. Reg. 301.7433-2, Civil cause of action for violation of section 362 or 524 of the Bankruptcy Code. (See IRM 1.4.51.3.7.1, Payment of Damages, below)

Payment of Damages
  1. Overview. The Commissioner of the IRS has authority to pay damages and attorney's fees from general appropriations in the settlement of the Service's liabilities on claims for violations of the automatic stay and discharge injunction. Awards are categorized as either:

    1. Litigative: an award in the form of a settlement or judgment resulting from a lawsuit; or

    2. Administrative: an award premised on an agency's claim authority.

    Payment requests are processed through the Bureau of the Fiscal Service (BFS), and the treatment of the two categories of awards differs slightly. (See paragraphs (17) and (18) below.)

  2. Processing Office. The processing office (FI or CIO) assigned to the case when the violation occurred will be responsible for processing claims for payment of damages up until a referral to Counsel is required. At that point the case becomes a complex issue and will be handled to conclusion by the assigned Field Insolvency office.

  3. Who Must File a Claim. The debtor, debtor's representative, or trustee must file a claim with the Service. The Service will directly pay the damages and/or attorney's fees if certain criteria are met.

  4. Willfulness. The Service can only be held liable for damages and attorney's fees if it commits a "willful violation" of the stay or discharge injunction. For a violation to be willful, the Service must know about the stay or discharge and initiate or continue collection activities. If the Service lacked notice of the stay or discharge injunction, the violation would not be willful. Even when the Service knows about a stay or discharge injunction, a good faith belief that it is inapplicable might be relevant. If the Service had a good faith (but erroneous) belief that the stay or discharge did not apply (e.g., the Service reasonably determined that the liability is excepted from discharge), consult Counsel regarding whether damages should apply. Compare Taggart v. Lorenzen, --- U.S.---, 139 S.Ct. 1795 (2019), holding that a bankruptcy court cannot impose contempt sanctions if there was an objectively reasonable basis for concluding that the creditor's conduct might be lawful. (Taggart did not deal with “willful” violations of the stay or discharge injunction, but a similar standard may apply in these situations.)

  5. Identifying Willfulness. To determine if a willful violation has occurred, Insolvency must verify the Service received notice of the bankruptcy or discharge order and:

    • Subsequently engaged in collection activities, or

    • Failed to halt its collection activities.

  6. Time frames. Generally for a claim to be considered, the Service must have failed to take appropriate action within the time frames of the Bankruptcy Code Compliance Program (BCCP). Those time frames are reflected in the chart below:

    Time Limits Required Actions
    Two work days Initiate corrective action on violations of the automatic stay or discharge injunction.
    Five work days Process initial bankruptcy petition information and ensure input of TC 520.
    10 work days Review damage claim applications for damages and attorney's fees for completeness and willfulness determination.
    30 calendar days Process discharge/dismissal notices and initiate closing procedures.
    60 calendar days Provide the debtor with a written response concerning the acceptance or denial of the claim application.

  7. Exceptions to Time frames. Regardless of general time frames, if an IRS employee initiates a collection action with knowledge of the stay or discharge, the action is a willful violation.

    Example:

    If a debtor tells an employee he is in bankruptcy, and the employee proceeds with a seizure, the collection action is a willful violation.

  8. Claim Applications. Because no standard IRS form for requesting payment of a claim has been published, a claim request must be submitted by letter. Field Insolvency offices must provide a claimant the nature of the information to be included in the application letter and where to send the claim. Share the following website, which provides additional information: https://www.irs.gov/businesses/small-businesses-self-employed/claims-for-relief-and-damages-for-violations-of-bankruptcy-automatic-stay-or-discharge-injunction. To be considered complete, a claim must be in writing and include the following:

    1. The name, taxpayer identification number, current address, and current home and work telephone numbers (with an identification of any convenient times to be contacted) of the taxpayer making the claim;

    2. The location of the bankruptcy court in which the underlying bankruptcy case was filed and the case number of the case in which the violation occurred;

    3. A description, in reasonable detail, of the violation (include copies of any available substantiating documentation or correspondence with the IRS;

    4. A description of the injuries incurred by the taxpayer filing the claim (include copies of any available substantiating documentation or evidence);

    5. The dollar amount of the claim, including any damages that have not yet been incurred but which are reasonably foreseeable (include copies of any available documentation or evidence); and

    6. The signature of the taxpayer or duly authorized representative.

    Note:

    Administrative costs, as defined in Treas. Reg. 301.7433-1(b)(2)(ii), Administrative costs, including attorneys’ fees, are not recoverable as actual, direct economic damages, but these costs may be recoverable under IRC 7430, Awarding of Costs and Certain Fees. See criteria in Treas. Reg. 301.7430-8, Administrative costs incurred in damage action for violations of section 362 and 524 of the Bankruptcy Code.

    Note:

    Pro se debtors may not claim attorney's fees.

  9. Evaluating Claims. The Service evaluates all claim applications for damages and attorneys' fees arising from willful violations of the automatic stay (11 USC 362, Automatic stay) or the discharge injunction (11 USC 524, Effect of discharge). Claims must be evaluated within ten work days from the date of the claim's receipt by the Service. Insolvency must review the claim to determine:

    1. The completeness of information provided;

    2. Evidence the Service's actions were willful; and

    3. Damages and attorneys' fees are reasonable and adequately substantiated. (Guidance from Counsel may be required.)

  10. Incomplete Claims. Incomplete claims must be returned to the claimant with a letter of explanation identifying the incomplete items. See Exhibit 1.4.51-2, Pattern Letter for Incomplete Claim for Damages and/or Attorney’s Fees.

  11. Non-Willful Violations. When Insolvency determines a willful violation of the automatic stay or discharge injunction did not occur, processing of the claim must halt. Insolvency must promptly forward its recommendation for rejection to Counsel.

    Note:

    Claims for violations are generally rejected when the claimant has not established actual damages or attorney's fees.

  12. Delegated Authorities. Delegation Order 25-10 found in IRM 1.2.2.14.10, Delegation Order 25-10 (formerly DO-254), Payment of Claims for Damages and Attorneys’ Fees Resulting from Violations of the Automatic Stay and Discharge Injunctions of the Bankruptcy Code, outlines approval authorities based on dollar amounts.

  13. Referral to Counsel. Any claim for more than $1,000 must be referred to Counsel for a legal opinion prior to its final disposition. A claim for any dollar amount that has been denied in part or in whole must be referred to Counsel for a legal opinion.

  14. Denied Claims. If payment of a claim is denied wholly or partially by Insolvency, the rejecting office must prepare a rejection recommendation stating the reasons for the rejection and refer the claim application to Counsel. If Counsel renders an opinion contrary to the rejection recommendation, only a Territory / Operation Manager has the authority to disregard the Counsel opinion.

  15. Written Notification. Upon receipt and evaluation of a complete application, Insolvency must send the claimant a written response within 60 calendar days of the receipt date stating the claim has been either rejected or accepted. See Exhibit 1.4.51-3, Pattern Letter for Approval of a Claim for Damages and/or Attorney’s Fees, and Exhibit 1.4.51-4, Pattern Letter for Denial of a Claim for Damages and/or Attorney’s Fees, for the applicable pattern letters.

  16. Civil Damages. If a taxpayer's administrative damage claim is disallowed by Insolvency, or six months pass without a decision by the IRS or Insolvency, the taxpayer may file a civil action for the damages as provided for in IRC 7433, Civil Damages for Certain Unauthorized Collection Actions. If the debtor is an individual, the debtor may also request damages for violations of the bankruptcy automatic stay, whether or not an administrative claim has been filed.

    1. The maximum damage award for reckless and intentional disregard of the code is $1 million.

    2. Negligent disregard carries a maximum award of $100,000.

  17. Payment of Administrative Claims. When the claim application for administrative damages and/or attorney's fees is approved in whole or in part, Insolvency must follow the procedures set forth in IRM 25.3.3.9.4, Reimbursement of Damages and Costs, with the exception of using the letters named in that citation. Pattern letters applying specifically to Insolvency must be substituted. (See paragraph 15 above.)

  18. Payment of Litigative Claims. Procedures in IRM 25.3.3.9.4, Reimbursement of Damages and Cost, should be followed when the claim application is for litigative damages and/or attorney's fees with the exception of the forms to be used. For litigative award funding refer to the Bureau of the Fiscal Service (BFS) forms, which should be used:

    Note:

    More information can be found at the BFS website: https://fiscal.treasury.gov/judgment-fund/forms.html.

  19. Separate Payment Requests for Damages and Attorney's Fees. When both payment of damages and attorney's fees have been authorized, Insolvency must request funding separately. For example if BFS FS Forms 196 and 197 are used for the damages award, then BFS FS Forms 196 and 197 must be used for payment of attorney's fees.

  20. Documentation. The AIS history must include detailed information on all aspects of claims for damages and/or attorney's fees including:

    1. The date the claim was received by the IRS;

    2. A summary of the issues cited in the claim;

    3. The dollar amount being sought broken down by damages and attorney's fees;

    4. A listing of documentation received by from the claimant;

    5. Results of the review for claim application completeness;

    6. Dates of correspondence sent to the claimant along with a summary of the correspondence's content;

    7. Names of management officials involved in approving/denying the claims along with the dates of their involvement;

    8. Date referral sent to Counsel;

    9. A summary of Counsel's opinion(s);

    10. Delegated authority's final determination to approve or deny the claim;

    11. The dollar amount(s) to be paid broken down by damages and attorney's fees if claim approved;

    12. Date appropriate forms are prepared and forwarded to BFS for funding if claim approved;

    13. Date denial letter sent to claimant if claim denied;

    14. Date check mailed to claimant if direct deposit not requested;

    15. Claimant's response if received; and

    16. Any other information relevant to the claim application and review process.

    In addition, paper or electronic files of all forms and correspondence pertaining to the claim must be retained until the possibility of litigation expires. For partially or wholly denied claims, this is two years from the date of the violation.

Employee Development / Training

  1. See IRM 1.4.1.6, Employee Development, for a full discussion of managerial responsibilities.

  2. Group Manager roles and responsibilities in the area of employee development and training include but are not limited to:

    1. Overseeing orientation of new employees

    2. Overseeing training for new employees (formal and on-the-job)

    3. Training and developing other employees including professional/technical and clerical staff

    4. Assisting and advising employees preparing a Career Learning Plan (CLP), if desired by the employee

      Note:

      Career Learning Plan website: http://hco.dstest.web.irs.gov/apps/clp2/index.asp

    5. Delegating acting managerial assignments

    6. Continuing education for employees to maintain and update knowledge and proficiency in technical areas

    7. Providing opportunities such as details to facilitate career development

    8. Ensuring employees have a working knowledge of tools to perform their duties, (e.g., AIS, ATFR, Automated Lien System (ALS), etc.)

  3. More information can be found at the Human Capital Office website: http://hco.web.irs.gov/

    • Servicewide Training and Briefing Programs

    • Policy and Procedural Guidance

    • Other related training resource sites, the IRS Learning Center, etc.

  4. For BU employees, also see Document 11678, National Agreement - IRS/NTEU, (Articles 7, Personnel Records, 12, Performance Appraisal System, 16, Details and Non-Competitive Temporary Promotions, and 30, Training) or contact a Human Resources Specialist.

  5. Resources:

    • IRM 1.4.1.6, Employee Development

    • Integrated Talent Management (ITM): https://irssource.web.irs.gov/Pages/ITM.aspx

    • HCO website: http://hco.web.irs.gov/

Performance Management

  1. The three balanced measures are: Employee Satisfaction, Customer Satisfaction, and Business Results. These three balanced measures are part of every individual and organizational performance evaluation system within the IRS.

  2. IRM 6.430.2, Performance Management Program for Evaluating Bargaining Unit and Non Bargaining Unit Employees Assigned to Critical Job Elements (CJEs), contains detailed guidance about evaluating performance. Refer to that IRM as well as the information following when evaluating performance.

Performance Evaluations

  1. Preparing performance evaluations is one of a manager’s most important responsibilities. In carrying out this task, the manager will observe how the employees are performing their duties and responsibilities to ensure that they are working efficiently and effectively to accomplish assigned tasks.

  2. Because managers are responsible for implementing the policies and directives relative to performance evaluations, they should thoroughly familiarize themselves with all facets of performance appraisal/evaluation information including, but not limited to:

    1. Performance expectations

    2. Mid-year and periodic performance reviews

    3. Annual ratings

    4. Acceptable level of competence

    5. Unacceptable/ minimally successful performance

    6. Competitive promotion appraisals

    7. Employee performance folders (EPF)

    8. Performance and recognition awards

  3. A formal performance evaluation serves:

    1. As a record of performance to support, recommend and initiate actions such as within-grade increases, promotions, award recommendations, reassignments, details, and adverse actions such as demotion or separation.

    2. To provide an employee with a basis for additional training and development.

    3. As a tool to improve the performance of individual employees.

  4. For employees new to the government, the first year of employment is a probationary period during which the employee must demonstrate successful performance and the capability to be promoted to the next grade level (if applicable). See IRM 6.430.2.4.3, Employees Serving Probationary Periods.

  5. Work closely with employees who are performing poorly, including probationary employees. Provide them with guidance/direction designed to assist them in improving performance. If performance improves, document the improvement accordingly. If performance fails to improve, refer to IRM 6.430.2, Performance Management Program for Evaluating Bargaining Unit and Non Bargaining Unit Employees Assigned to Critical Job Elements (CJEs), and seek appropriate advice to determine next steps.

  6. Documentation of performance:

    1. Providing feedback to the employee (positive and constructive) is essential to maintaining and/or improving their performance.

    2. Keep an employee's overall performance in mind when discussing work and other activities. Let them know when some aspect of performance may influence their performance rating, a promotional opportunity or other personnel action.

    3. Recordation serves as a snapshot of employee performance. Adequate documentation will be a reminder of changes in performance over the rating period.

    Reminder:

    Notify employees of decreased work performance per guidance in IRM 6.430.2.3.3, Acknowledging Decreased Work Performance.

  7. When writing review narratives be concise, but descriptive enough to provide an accurate picture of the strengths, developmental needs, and accomplishments of the employee in each CJE. (See IRM 6.430.2.4.6, Completing Appraisal Narratives.)

  8. Performance evaluations provide a uniform means for a written evaluation and rating of each employee's proficiency.

    • IRM 1.5, Managing Statistics in a Balanced Measurement System, describes how balanced measures are used to support individual as well as organizational performance. The three balanced measures are: Employee Satisfaction, Customer Satisfaction and Business Results. These three balanced measures are part of every individual and organizational performance evaluation system within the IRS.

    • IRM 1.5.2, Use of IRC 1204 Statistics, provides specific guidance for SB/SE use of measures. This IRM provides information about the prohibition on the use of records of tax enforcement results (ROTERs) to evaluate employees or to impose or suggest production quotas or goals.

  9. Formal employee evaluations represent the sum of what managers have observed in each employee's work, using feedback, reviews, field visitations, and other techniques discussed in this manual. Consider the following when evaluating performance for an annual appraisal:

    • Position description

    • Critical Job Elements (CJEs)

    • Mid-year and other progress reviews

    • Employee’s work products (management briefings, memos)

    • Employee’s self-assessment

    • Feedback from taxpayers and other customers

    • Team assignments and contributions to work group

    • Special Achievements

  10. Each employee will receive an annual performance evaluation. See information about Performance Appraisal Due Dates in the National Agreement - IRS/NTEU, Article 12, Exhibit 12-1.

    Note:

    A sample Annual/Mid-year Review Schedule has been provided in Exhibit 1.4.51-5, Sample Annual/Mid year Review Schedule. Managers can tailor this sample to the criteria for their group to ensure appraisals are completed timely.

  11. Employees may submit a self-assessment, limited to four (4) pages in length, no later than the last workday of his or her annual appraisal rating period. See IRM 6.430.2.4.5, Self-Assessment, and IRM 6.430.2.6, Conducting the Performance Appraisal Meeting.

  12. Use only the work requirements of the particular position or specific work standards established by the Service to make Acceptable Level of Competence Determinations (i.e. determination that employee is performing at a fully successful level.)

  13. For information on the suggested steps to make unacceptable performance determinations see Exhibit 1.4.51-1, Suggested Action Steps for Unacceptable Performance.

  14. Resources:

    • Human Capital Office website: http://hco.web.irs.gov. This website houses the CJE Resource Center, Manager Guide for Employee Performance Awards information, forms, etc.

    • Document 11678, National Agreement - IRS/NTEU, Articles 7, Personnel Records, 12, Performance Appraisal System, 17, Acceptable Level of Competence Determinations, 18, Awards, and 40, Unacceptable Performance

    • IRM 1.4.1, Management Roles and Responsibilities

    • IRM 6.430.2.3.3, Acknowledging Decreased Work Performance

    • IRM 6.432.1, Reduction in Grade, Band and Removal Based on Unacceptable Performance

    • IRM 6.451, Employee Performance and Utilization

    • Other portions of IRM, Part 6, Human Resources Management

    • The assigned Labor Relations specialist

Reviews (Overview)

  1. Providing ongoing employee feedback that is candid and meaningful is essential to employee satisfaction and is an integral part of the group manager’s responsibilities. Reviews of employee work should serve to:

    1. Assess the employee’s effectiveness in meeting the expectations established in their Critical Job Elements.

    2. Determine the employee’s efficiency in carrying out the laws, procedures, and policies of the Service.

    3. Identify and address performance problems.

    4. Evaluate the employee's ability to properly plan and schedule field, office, and Telework activity.

    5. Ensure the employee is taking timely and appropriate actions to bring the case to a prompt and proper resolution.

    6. Assess employee effectiveness in developmental case assignments.

    7. Determine the employee's effectiveness in meeting the IRS Retention Standard for the Fair and Equitable Treatment of Taxpayers. Careful review of cases should occur in order to provide a quality product and excellent taxpayer customer service.

    8. Ensure taxpayers’ rights are observed. See IRM 1.4.51.3.2 above.

  2. All reviews relating to an employee's case work must be in writing. Managers must use EQRS to review individual cases, but other types of performance observation lend themselves to other methods. For reviews that consider employee activity across multiple cases (e.g., time utilization, office/field observation) a summary narrative, such as a memorandum, may be substituted. The EQRS Individual Feedback Report provides a record of ratings and the narrative comments in which the employee’s performance is summarized. Become familiar with Document 12656, Field Insolvency Embedded Quality Job Aid and Campus Quality Master Attribute Job Aid (MAJA), which provides specific guidance related to Embedded Quality attributes and how to use them.

  3. At the beginning of the fiscal year, group managers will develop a review schedule for the group that includes all mandatory reviews and optional reviews. Optional reviews may include additional office or field visitations, time and workload reviews, etc. The review schedule should provide for a fair and accurate assessment of the employee's overall performance throughout the rating period.

  4. Mandatory reviews represent the minimum review requirements that must be completed for each employee. It is intended that the minimum requirements will provide managers with an opportunity to spend more time reviewing and developing employees that need additional feedback and assistance. Mandatory reviews include:

    1. One or more annual field visitations or observation at a 341 hearing, whenever applicable and possible.

    2. One or more time utilization reviews with each employee.

    3. Mid-Year appraisals/reviews. The mid-year appraisal should occur at the midpoint (six-months) of the employee's appraisal period.

    4. Annual performance case reviews. See IRM 1.4.51.5.2.2, Requirements for Annual Performance Case Reviews.

  5. When necessary, based on case reviews, other forms of review, field or office observation, etc., managers have the authority to require their employees to obtain their approval before taking subsequent case actions.

    Example:

    Employees who inappropriately extend deadlines or delay case actions can be required to obtain managerial approval of their extensions in the future so as not to delay timely case resolution.

  6. Group managers will continually review information gathering activities by their employees.

  7. For additional guidance on preparing reviews, narratives and appraisals see:

    • IRM 1.4.1.8, Evaluation Performance

    • IRM 5.1.3.7.1, Information Gathering Guidelines

    • IRM 6.430.2, Performance Management Program for Evaluation Bargaining Unit and Non Bargaining Unit Employees Assigned to Critical Job Elements (CLEs)

    Note:

    Operational review aids for Territory / Operation Managers and the Area Director are presented in, Exhibit 1.4.51-45, Operational Review Plan Guide, and Exhibit 1.4.51-46, Director Operational Aid (DOA).

Case Reviews
  1. Choose a sufficient number of cases for review to ensure a thorough evaluation of each employee’s performance. The Specialty Collection - Insolvency Director will provide guidance on the number of minimum yearly case reviews. Reviews should be tailored to individual needs. Managers should increase the number of case reviews when an employees performance declines. Scheduling of the analysis may be announced or unannounced at the option of local management. (Article 12, Section 4.L)

    Note:

    See IRM 1.4.51.5.2.2, Requirements for Annual Performance Case Reviews.

  2. Ensure case selection contains a mix of cases representative of the employees assigned inventory.

  3. Work submitted for approval or closure also provides an opportunity to evaluate individual performance as well as the overall quality of the group's product. When reviewing cases submitted for approval or closure, look for performance that reflects an employee's adherence to IRM standards as well as other established policies and procedures.

    Caution:

    Confine written reviews to work performed during the employees rating period.

  4. Use the Embedded Quality Review System (EQRS) for individual case reviews. The review items on the EQRS Individual Feedback Report correspond with the performance standards of an employee’s critical job elements. In general, deficiencies relating to a critical job element should be noted as an area of special concern if found in 25% or more of the cases reviewed. There may be instances where a single deficiency (e.g., expired statute) is critical. The attribute narrative should summarize the employee's performance for each individual case reviewed.

  5. Managers must also summarize the employee's overall performance on all cases reviewed, including the results of time utilization reviews, field/office visitations, etc., as part of the mid-year and/or annual performance assessment. Narrative feedback should address positive aspects, as well as areas for improvement, of an employee's performance. See Exhibit 1.4.51-6, Insolvency Group Manager’s EQRS Review Document, Form 6850 BU, and Narrative, General Guide.

  6. As part of the case review, prepare the EQRS Individual Feedback Report in duplicate and include all applicable case data. Both the manager and the employee must sign it. Give the original Individual Feedback Report to the employee for action on case recommendations. Retain the duplicate in the EPF for follow-up. Discuss all recommended actions entered on the Individual Feedback Report with the employee to ensure that there is a complete understanding regarding the observations and direction.

  7. If managers have directed specific case actions, a follow-up review should be scheduled 60-90 days after the initial review to ensure their instructions are being followed and the case is moving toward resolution. If the actions are time sensitive, a shorter follow-up review may be warranted. The follow-up review will generally be limited to the cases in which a follow-up review has been scheduled unless there is need to see other cases to document a performance trend. Using EQRS, prepare a narrative conveying the results of the follow-up review.

  8. Written performance feedback (Individual Feedback Report, 6067, memorandum, etc.) must be provided to the employee within 15 work days. The 15 day time frame starts from the time the supervisor becomes aware of, or should have been aware of, the event addressed in the recordation/feedback item.

  9. Although managers may suggest or request specific actions in the case history, they should avoid making numerous case decisions for the employee. Documentation of an evaluative nature should not be entered in the case history.

  10. As part of any case review, determine if the assigned grade level is still accurate. See IRM 1.4.51.9.1, Case Assignment Guide.

  11. It is important to ensure that employees comply with guidelines about direct contact with taxpayers with representatives. During case reviews ensure that taxpayer rights have been observed, particularly with respect to direct contact provisions. See IRM 5.1.23.3.2.3, Written Communication to a Taxpayer’s Representative, and IRM 5.1.23.5, By-Passing a Taxpayer's Representative.

  12. Resources:

    • Embedded Quality: http://portal.ds.irsnet.gov/sites/vl115/pages/default.aspx

    • CJE Resource Center: http://hco.web.irs.gov/apps/cje/

    • IRM 5.13.1, Embedded Quality Collection Field Organizations Administrative Guidelines

    • IRM 6.430.2.4.9, Rating CJEs

    • IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Service (RICS), and Electronic Products and Service Support

Requirements for Annual Performance Case Reviews
  1. Select a sufficient number of cases for review that meet the criteria in IRM 1.4.51.5.2.1, Case Reviews. Review at least half of the cases prior to the mid-year progress review.

  2. Review plans should be tailored to fit the needs of individual employees.

  3. Use EQRS attributes, case summary narratives, and performance summaries for all reviews conducted during the rating period to create performance feedback. Feedback must indicate to the employee how they are meeting or not meeting the EQRS attributes and aspects of the critical job elements.

  4. Provide the employee with the narrative within 15 work days and place a copy of the document in the EPF.

Field and Office Observations
  1. Observing the employee during face-to-face contacts, either at 341 hearings or office meetings, provides an excellent opportunity for the manager to assess an employee’s:

    1. Ability to conduct interviews.

    2. Ability to communicate and interact with taxpayers.

    3. Knowledge of policies and procedures, including observance of taxpayer’s rights listed in IRM 1.4.51.3.2, Protecting Taxpayer Rights, above.

    4. Ability to deliver fair and courteous treatment to all taxpayers.

  2. Conduct one or more annual field visitations, 341 observations, or office observations with each employee, whenever applicable and possible.

  3. During observations, managers will evaluate the employee for:

    1. Ability to secure material information necessary to determine appropriate case direction.

    2. Delivery of fair and courteous treatment of taxpayers.

    3. Ability to address the various rights of the taxpayer (Pub 1, Your Rights as a Taxpayer, Pub 594, The IRS Collection Process, IRC 6320, Notice and opportunity for hearing upon filing of notice of lien, IRC 6330, Notice and opportunity for hearing before levy, and Collection Appeals Program).

    4. Ability to recognize and respond to taxpayer concerns, issues and interests.

    5. Pre-contact preparation including appropriate questions at the 341 hearing.

    6. Itinerary planning.

    7. Effective use of time.

    8. Ability to manage difficult, unexpected, complex or unusual circumstances.

    9. Ability to appropriately recognize and address "Third Party Contact" situations.

    10. Observation of proper disclosure requirements.

  4. Provide feedback based on all observations using a summary narrative, such as a memorandum.

  5. Resources:

    • CJE Resource Center: http://hco.web.irs.gov/apps/cje/

    • IRM 5.1.1.12, Third Party Contacts

    • IRM 25.27.1, Third Party Contact Program

      Note:

      Refer to IRM 25.27.1, Third Party Contact Program, for general servicewide guidance on third party contacts. Refer to IRM 5.1.1.12, Third Party Contact, for third party contact information specific to Collection casework.

    • IRM 6.430.2.2.1, Retention Standard for the Fair and Equitable Treatment of Taxpayer

    • IRM 11.3.1, Introduction to Disclosure

Time Utilization Reviews
  1. Conduct one or more Time Utilization Review annually with each employee. Use the Time Utilization Review to measure the overall effectiveness of the employee's office, field, and/or Telework. Make observations regarding work quality as appropriate, but the purpose of this review is to evaluate employee performance in effective use of time and accuracy of documentation.

  2. Conduct the Time Utilization Review within fifteen (15) workdays of the day selected.

  3. Time Utilization Reviews should be unannounced. Document the review with a memorandum or Form 6067, Employee Performance Folder Record, to summarize the observations.

    1. Technique

    • Evaluate whether time spent on case actions matches the time charged as well as the nature and complexity of what is required in each case.

    • Evaluate whether the case actions taken are likely to move the case toward resolution.

    • Identify unproductive/inefficient activity and make recommendations for improvement.

  4. Documents should be shared with the employee and maintained as part of the EPF to be used in preparation of the Mid-Year/Annual Appraisal.

Work Submitted for Approval/Closure
  1. When work is submitted for approval, managers have an opportunity to evaluate an employees' performance. This also enables the manager to prevent deficiencies. Check for accuracy and level of quality before approving reports of currently not collectible taxes, installment agreements, requests for adjustment, seizure documents, TFRP investigations and recommendations, fraud referrals, and any other document prior to submission to another function. The quality of the work that leaves a manager’s group is a reflection on the group manager.

After Hours Review
  1. An after hours review allow managers to determine whether documents, property, and monies are being adequately protected when not in the custody of authorized IRS personnel. Managers can accomplish this by being the last to leave a work area and checking the area after the close of the business day. Managers could also accomplish after hours reviews by periodically arriving early to work ahead of the staff to review the work space for compliance. (See IRM 1.4.6.7.2, After Hours Review, and IRM 1.4.6, Managers Security Handbook, for servicewide guidance on the managers responsibilities.)

  2. Managers periodically must review functional areas after hours to determine if sensitive but unclassified (SBU) date, including Personally Identifiable Information (PII) and tax information, is appropriately containerized and properly disposed. This includes PII left in printing trays. Also check to see whether cabinets, safes, and other containers are appropriately secured. Limited areas, secure areas, and office doors are to be secured and verified as well. If weaknesses are identified, managers must take immediate action to safeguard information, property, or rooms/facility, counsel employees as appropriate, and/or request assistance from appropriate local Facilities Management & Security Services (FMSS) Physical Security staff in developing corrective measures.

  3. The after hours review may be completed by a designee (e.g. the Commissioner’s Representative) of the group manager in posts of duty where the manager is not in the same location with the employee.

  4. If your reviews reflect that employees repeatedly fail to observe security protocols, contact your Labor Relations specialist to determine the next appropriate action.

Use of Statistical Data / Section 1204 / ROTERs

  1. Section 1204 of the IRS Restructuring and Reform Act of 1998 (RRA 98) prohibits the use of Records of Tax Enforcement Results (ROTERs) to evaluate employees or to impose/suggest production quotas/goals for any employee.

  2. IRM 1.5.1, The IRS Balanced Performance Measurement System, provides guidance to prevent the use of statistics to:

    1. Evaluate employees, or

    2. Impose or suggest production quotas or goals with respect to such employees.

  3. ROTERs are data, statistics, compilations of information or other numerical or quantitative recordations of the tax enforcement results reached in one or more cases. Managers are prohibited from using records of tax enforcement results to evaluate any employee who exercises judgment with regard to determining tax liability or ability to pay. This prohibition includes:

    • Required or requested performance ratings (annual, mid-year, ad hoc)

    • Self-assessments

    • Award recommendations

    • Assessment of an employee's qualifications for promotion, reassignment, or other change in duties

    • Assessment of an employee's eligibility for incentives, allowances or bonuses

    • Ranking for release/recall and reduction in force

    Note:

    ROTERs do not include tax enforcement results of individual cases when used to determine whether an employee exercised appropriate judgment in pursuing enforcement of the tax laws based upon a review of the employee’s work on that individual case.

  4. Managers are also prohibited from using ROTERs to impose or suggest production goals or quotas for employees or groups of employees. Examples of prohibited ROTERs include:

    • Number of Proofs of Claim filed

    • Number of delinquent returns secured

    • Number of delinquent returns secured with full payment

    • Number of seizures made

    • Number of levies issued

  5. Resources:

    • IRM 1.5.1, The IRS Balanced Performance Measurement System

    • IRM 1.5.2, Uses of IRC 1204 Statistics

    • IRM 1.5.3.4, Section 1204 Quarterly Certification Requirements

    • Section 1204: http://irssource.web.irs.gov/SitePages/Section1204.aspx

    • Section 1204 Documentation Tool: https://irssource.web.irs.gov/LBI/Lists/QRA_PPCA/DispItemForm.aspx?ID=55

Tax Enforcement Results (TERs)
  1. A tax enforcement result (TER) is the outcome produced by an IRS employee's exercise of judgment in recommending or determining whether or how the IRS should pursue enforcement of tax laws.

  2. TERs may be discussed in employee reviews (but not employee evaluations) to determine if the employee exercised appropriate judgment, used time efficiently and applied the laws in one or more cases properly. See IRM 1.5.2.10.1, Permitted Use of TERs.

Regulation 801 / Quantity & Quality Measures
  1. Regulation 801, Balanced System for Measuring Organizational and Employee Performance with IRS, implements the provisions of Section 1204 of the IRS Restructuring and Reform Act of 1998 (RRA 98), provides rules relating to the establishment of a balanced performance measurement system and sets forth rules governing the use of ROTERs.

  2. Quantity measures consist of outcome-neutral production and resource data that do not contain information regarding the tax enforcement result (TER) reached in any case involving particular taxpayers. Examples of quantity measures include, but are not limited to:

    • Cases started

    • Cases closed

    • Time per case

  3. Performance measures based in whole or in part on quantity measures will not be used to evaluate the performance of any non-supervisory employee who is responsible for exercising judgment with respect to tax enforcement results.

  4. The quality review of the handling of collection cases focuses on such factors as whether employees devoted an appropriate amount of time to a matter, properly analyzed the facts, complied with statutory, regulatory, and IRS procedures, etc.

  5. Resources:

    • IRM 1.5.2.12, Quality Measures

    • IRM 1.5.2.13, Quality Measures

Retention Standard

  1. Regulation 801 provides that, in addition to all other criteria required to be used in the evaluation of employee performance, all employees of the IRS will be evaluated on whether they provided fair and equitable treatment to taxpayers.

  2. Form 6774, Receipt of Critical Job Elements and Fair and Equitable Treatment of Taxpayer Retention Standard, is maintained in the EPF.

  3. Resources:

    • IRM 1.5.3.3, Retention Standard for the Fair and Equitable Treatment of Taxpayer

    • IRM 6.430.2.4.7, Rating Performance Against The Retention Standard for the Fair and Equitable Treatment of Taxpayer

    • Retention Standard resources: http://hco.web.irs.gov/perfmgmt/evaluation/evalperf/nonmgrpolicy.html

Within Grade Increase

  1. An employee shall be advanced in pay to the next higher step of their grade upon meeting the following requirements:

    1. Required waiting period completed;

    2. No equivalent increase in pay received during the required waiting period; and

    3. Fully successful performance in each of the critical job elements of their position.

  2. Use only the work requirements of the particular position or specific work standards established by the Service to make Acceptable Level of Competence Determinations (i.e. determination that employee is performing at a fully successful level.).

    Reminder:

    See IRM 6.430.2.5.4, Within Grade Increase (WGI) Determination.

  3. For information on steps to follow when an employee is not meeting an acceptable level of competence, Exhibit 1.4.51-7, Action Steps for Acceptable Level of Competence Determination if an Employee Within Grade Increase (WGI) is Due.

Evaluation Due Dates

  1. Each employee will receive an annual performance evaluation. The due date of an evaluation for any particular employee is based upon the last digit of the employee’s Social Security Number (SSN). Refer to Document 11678, National Agreement - IRS/NTEU, Article 12, Exhibit 12-1, Performance Appraisal Due Dates SSNs Aligned To Monthly Periods.

Discipline/Disciplinary Actions

  1. Discipline is defined as measures taken by management that are intended to correct employee misconduct, and encourage employee conduct in compliance with the standards of conduct, policies, goals, work procedures, and office practices of the IRS and the Federal Service. Employees must adhere to all known conditions and standards of conduct established to provide for the orderly and efficient administration of the IRS.

  2. Employees who fail to comply with standards of conduct, work procedures, and office practices will be subject to disciplinary action designed to correct the violation and motivate the employee to become a productive member of the IRS.

  3. Managers are responsible for establishing and maintaining effective discipline within their work group. Managers must explain the work requirements and other standards employees are expected to meet.

  4. When disciplinary action is required, it must be fair, equitable, impartial, and as timely as possible.

  5. A guide to assist managers in determining appropriate penalties to correct improper conduct can be found in Exhibit 6.751.1-1, IRS Guide To Penalty Determinations..

  6. Ensure to discuss and coordinate all proposed disciplinary actions with a Labor Relations Specialist.

  7. Resources:

    • IRM 6.751, Discipline and Disciplinary Actions

    • IRM 6.752, Disciplinary Suspensions and Adverse Actions

    • Document 11678, National Agreement-IRS/NTEU, Articles 38, Disciplinary Actions, and 39, Adverse Actions

Telework

  1. Telework is a program that permits employees to work at home or at other approved locations other than the assigned post of duty.

  2. There are three (3) forms of Telework:

    1. Frequent

    2. Recurring

    3. Ad Hoc

  3. See Document 11678, National Agreement - IRS/NTEU, Article 50, Section 1.B, Types of Telework, for more information about the types of Telework.

Managing Telework

  1. Managing an employee participating in Telework is essentially no different than managing an employee in the office. Managers should ensure that their actions are in compliance with the National Agreement - IRS/NTEU. The employee on Telework is still held accountable for the Rules of Conduct, Critical Job Elements, Time and Attendance, Ethics, and all other regulations applicable to their position.

    Note:

    Per Article 50, Section 1.F of the National Agreement - IRS/NTEU: Telework is not a replacement for dependent/family care.

  2. Managers should ensure that employees are responsive to all customers. Employees must check voice mail (VMS) and email (when accessible) to ensure external as well as internal customers (including managers) receive responses timely. It is appropriate for an employee to check their VMS and email prior to going to lunch and some time prior to ending their day. Employees supplied with pagers and cell phones should be expected to be more responsive.

  3. Managers have the right to direct a Telework employee to report to the office when necessary. For example, when having meetings, which include group meetings, case reviews, training, etc. This should be planned so that the employee has ample time to report to the office during their regular commute time. When an employee plans or decides to make field calls during a Telework day the manager should be informed. This is referenced under Article 50, Section 5.A.2 of the National Agreement - IRS/NTEU.

  4. Article 50 of the National Agreement - IRS/NTEU addresses Telework issues. Sections pertinent to the management of employees in a Telework environment are listed below:

    1. A supervisor’s official relationship with, authority over, and accountability for an employee participating in the Service’s Telework Program is no different than his or her relationship with, authority over, and accountability for employees who are not participating in the Telework Program. Consistent with the provision of this Article, the supervisor retains the authority to review, determine, and approve participation in this program. (Article 50, Section 1.A.5).

    2. Employees may telework more than 80 hours each month if they have elected to participate in Frequent Telework. (Article 50, Section 1.B.1). Employees approved for a Frequent Telework arrangement will be provided equipment consistent with Article 50, Section 7.B.

    3. Employees approved for a Recurring Telework arrangement may work at the approved telework site for 80 hours or less per month (Article 50, Section 1.B.2).

    4. Employees may participate in an "Ad Hoc" Telework Program. This allows the employee with nonrecurring projects or work assignments to work at a Telework site, subject to approval by their supervisor. (Article 50, Section 1.B.3).

    5. Participants may be permitted to work at home or other Telework work sites full days or a portion of a day.

      Reminder:

      Unless as otherwise provided by Article 50, Section 1.C of the National Agreement - IRS/NTEU: there is no limitation on how the work schedule may be configured as long as the scheduling is not disruptive to the work that remains in the office or cause an unreasonable burden on those who choose not to work a Telework arrangement.

    6. Management has the right to meet with employees to give assignments and to review work as necessary at either the official duty station, approved Telework location, or a mutually agreed upon site. (Article 50, Section 4.C.) This does not mean that 24 hour notification or union presence is required, but 24 hour notification is suggested.

    7. Employees must provide the supervisor and/or clerk in advance with all the specific information regarding their work schedule, type of work to be performed and location of the alternate work place. This includes the obligation to inform the supervisor when they are unable to perform work due to illness or other circumstances during the Telework tour of duty (TOD) and requesting appropriate leave. (Article 50, Section 5.A.1.)

    8. Employees must call the office to report time, to retrieve messages, and to notify the supervisor and/or clerk of changes in work locations. (Article 50, Section 5.A.)

    9. In order to ensure accountability, a participating employee and his/her supervisor must communicate at least one time during each pay period to verify the employee’s time and attendance. (Article 50, Section 6.F.)

  5. If it is determined that an employee's work appears to be degrading from "Fully Successful" or is below a "Fully Successful" rating, managers should review Article 50, Section 2, Eligibility, of the National Agreement - IRS/NTEU to determine whether the employee's continuation on Telework is appropriate. This occurs when any Critical Job Element (CJE) rating equals "2" or below.

    Note:

    When considering removing an employee from Telework, ensure that the reasons for removal are well documented. This documentation may include but is not limited to EQRS Individual and/or Cumulative Feedback Reports, Form 6850-BU, or memoranda. Managers must ensure that the employee is aware of the situation and should then monitor the employees work product closely and develop a plan for improving that employee’s work, just as would be done for an employee not on Telework. There is no prohibition per the National Agreement - IRS/NTEU on any type of performance review following a period in which an employee has worked at their Telework site. Reviews may include "Time Utilization" , "Time and Activity" , or other performance based review. Ensure this also conforms with any applicable local Area agreement as well. The types and amount of time expended on Telework should be comparable to time in the office. For example, there should not be increased amounts of administrative or miscellaneous time, or increased time charged to cases with minimal actions taken.

  6. Resources:

Interaction With Employees On Telework

  1. A manager’s official relationship with, authority over, and accountability for an employee participating in the Service's Telework Program is no different than that for employees who are not participating in the program.

  2. Manager responsibilities include:

    1. Meeting with employees at least once a year for the purpose of discussing, reviewing, and updating the Telework Agreement, if needed.

    2. Directing Telework employees to report to the office due to special circumstances.

    3. Meeting with employees to give assignments and review their work as necessary at the official duty station, approved work site that includes their home, or mutually agreed upon site.

    4. Inspecting the employee's work site when appropriate. Managers may visit the Telework site, with twenty four (24) hours notice, to ensure privacy considerations are in place to safeguard SBU data, including PII and tax information within a telework environment. Refer to IRM 10.5.1.6.11 , Telework.

      Reminder:

      Work site inspections are not expected to be routinely conducted. Inspect as necessary to verify Information Systems (IS) and privacy requirements are in place.

    5. As with all employees, be proactive in identifying opportunities to rate CJE 1, Workplace Interaction/Involvement/Environment.

  3. For an employee to remain on the Telework program, they must:

    1. Remain "Fully Successful" or above.

    2. Not be subject to a conduct investigation in which management has sufficient evidence of serious wrongdoing that would impact the integrity and efficiency of the Service.

    3. Continue to stay in compliance with Article 50, Section 2, Eligibility, of the National Agreement - IRS/NTEU.

    If any of the above circumstances do not apply, the employee may be suspended from Telework pending resolution of the performance and/or conduct investigation situations. For further information, contact the assigned Labor Relations Specialist. Refer to the National Agreement - IRS/NTEU, Article 50. Coordinate proposed changes to Telework arrangements with a LR specialist.

Recognition and Awards

  1. Awards are opportunities for group managers to recognize and reinforce positive performance and behavior.

  2. Managers are responsible for maintaining a working knowledge of the awards process.

  3. Complete information regarding awards can be found on the Human Capital website at: http://hco.web.irs.gov/perfmgmt/awards/perfaward/index.html

  4. Resources:

    • IRM 6.451.1, Policies, Authorities, Categories, and Approvals

    • IRM 1.4.1.8.3, Recognition and Awards

    • Document 11678, National Agreement - IRS/NTEU, Article 18, Awards

    • The Human Resources Specialist

Insolvency Workload Management

  1. Managers are responsible for effectively managing the group's workload in order to encourage positive work flow and case movement. To accomplish this he or she must:

    1. Ensure priority cases are worked.

    2. Assign cases based on grade and priority level.

    3. Balance inventories within the group.

    4. Ensure case activity is progressing toward resolution.

    5. Initiate methods to improve production, work processes, and/or to increase the quality of the work directed.

  2. Managers must monitor key Insolvency processes to minimize the risk of damage claims by ensuring bankruptcy freeze codes are input and released on IDRS timely.

  3. Managers should review the number of cases on the Court Closure Follow-Up report needed to monitor inventories identified as "at risk" for backlogs or lack of timely processing. Closure actions on discharged and dismissed cases must be initiated within 30 days of notice. As a part of closing actions, managers must ensure liens are released timely when release is appropriate. IRM 5.9.17.18, Release of Federal Tax Liens, provides procedures for lien releases which may include requests for manual lien release.

    Note:

    When collection is being pursued on dischargeable liabilities after case closure, Notices of Federal Tax Lien (NFTL) should not be released.

  4. Adherence to the following areas can promote efficiency in the flow of Insolvency work:

    • Educating caseworkers to the range of information available in the AIS database and explanation of the screens and fields AIS Business Objects reports access to format reports

    • Eliminating unnecessary or low value tasks to streamline processing as long as the elimination does not violate IRM requirements

    • Delegating management duties to a Field Insolvency employee whose ratings exceed fully successful (Field Insolvency)

    • Delegating of management duties to team leads (Centralized Insolvency Operation)

    • Identifying potential or actual bottlenecks in workflow

    • Developing contingency plans to prioritize work during predictable seasonal increases in receipts and manual refund processing

    • Accessibility of all cases to the group

    • Respecting assignment of duties by operation established in IRM 5.9 and IRM 1.4.51

    • Elevating system change requests through the management chain up to Collection Policy

Total Inventory Management (TIM)

  1. Strive for currency of inventory by encouraging employees to take the right action at the right time on each case.

  2. Communicate to employees that it is expected that they work their inventory as a whole.

Using AIS

  1. AIS is the primary case management system for Insolvency managers. Managers should familiarize themselves with the AIS Business Objects reports.

  2. Use AIS to:

    1. Assist employees in managing their inventories.

    2. Identify cases with which the employees may need assistance such as listed in IRM 1.4.51.8.3, Case Management Tools.

  3. Assigning Roles. Roles, that relate to specific permissions, for all AIS activities must be requested using the BEARS system. When submitting the Online BEARS the user should request the appropriate level of access based on their assigned duties. Manager's should review these requests and approve/deny them as necessary. After approval, an email will be sent to the AIS Administrators for the system and if approved the user's information will be added/deleted/updated. A second level AIS Administrator will add the employees SEID into the correct Role Group. At least once per year, managers should review their employees' Role Group on the Employee Information screen on AIS to ensure the correct level of permissions. To access the Employee Information screen from the AIS Main Menu:

    1. Under "Support" tab, select "Organization" .

    2. Select "Employees" .

    3. "Search" the employee to be viewed.

    4. Select "Submit Search" .

    5. Select "Role Information" tab to assign employee roles.

    Reminder:

    It is critical that the AIS profile accounts of employees that leave Insolvency, either through separation or transfer to a new operation, be inactivated immediately. When they are not inactivated quickly, there is potential for new and old case inventory to go un-monitored and un-worked. An AIS Administrator can inactivate the employee’s profile account, when working submitted or systemic Online BEARS entitlement removal request, as soon as the employee’s manager reassigns the employee’s CAG and transfers the employee’s inventory.

Case Management Tools

  1. Managers are expected to use tools available to ensure cases in their inventory are handled with professionalism according to both the IRC and bankruptcy laws and rules and with the intent of protecting the rights of the debtor and the interests of the government.

  2. AIS Business Objects reports are used to help manage required actions. Use of certain AIS Business Objects reports are mandatory.

  3. Reports are tools for managing inventory. The Director determines which AIS Business Objects reports are required to be worked, and how often they should be worked by employees. For managers, reviewing most AIS Business Objects reports is optional and up to the discretion of the Territory / Operation Manager; however, reviewing the following AIS Business Objects reports is "Mandatory" .

    The following reports are required to be reviewed "Weekly" :
    Automated Proof of Claim (APOC) Period Detail Flag - Credits Posted After the Petition Date report. Exhibit 1.4.51-8, Guide for APOC Reports (Field Insolvency).
    APOC Period Detail Flag - Lien Recorded Date Blank or > Petition Date report. Exhibit 1.4.51-8, Guide for APOC Reports (Field Insolvency).
    The following report is required to be reviewed "Bi-weekly" :
    APOC Period Detail Flag - Secured Period report. Exhibit 1.4.51-8, Guide for APOC Reports (Field Insolvency)
    The following reports are required to be reviewed "Monthly" :
    APOC Flagged Cases report. Exhibit 1.4.51-8, Guide for APOC Reports (Field Insolvency).
    Bar Date Follow-Up report. Exhibit 1.4.51-9, Guide for Bar Date Follow-Up Report (Field Insolvency).
    Case Grade report. Exhibit 1.4.51-12, Case Grade Report - Manager only (Field Insolvency).
    Court Closure Follow-Up report. Exhibit 1.4.51-13, Guide for Court Closure Follow-Up Report (Field Insolvency and CIO).
    Litigation Transcript System (LTS) reports. Exhibit 1.4.51-11, Guide for Litigation Transcript System (LTS) Reports (Field Insolvency and CIO).
    Proofs of Claim Follow-Up report. Exhibit 1.4.51-10, Guide for Proofs of Claim Follow-Up Report (Field Insolvency).
    Unpostable reports. Exhibit 1.4.51-34, Guide for Unpostable Reports (Field Insolvency and CIO).
    The following reports are required to be reviewed "Quarterly" :
    ASED Follow-Up report. Exhibit 1.4.51-18, Guide for ASED Follow-Up Report (Field Insolvency).
    LAMS Not Found on AIS Case Listing report. Exhibit 1.4.51-23, Guide for LAMS Not Found on AIS Case Listing Report (Field Insolvency).
    LAMS Post-Petition Case Listing report. Exhibit 1.4.51-21, Guide for LAMS Post-Petition Case Listing Report (Field Insolvency).
    Lien Research report. Exhibit 1.4.51-25, Guide for Lien Research Report (Field Insolvency and CIO).
    Litigation Accounts Management System (LAMS) Closed Case Listing report. Exhibit 1.4.51-16, Guide for LAMS Closed Case Listing Report (Field Insolvency and CIO).
    Non-Master File Listing report. Exhibit 1.4.51-24, Guide for Non-Master File Listing Report (Field Insolvency and CIO).
    Pending Refunds report. Exhibit 1.4.51-17, Guide for Pending Refunds Report (Field Insolvency and CIO).
    Referral to Counsel report. Exhibit 1.4.51-22, Guide for Referral to Counsel Report (Field Insolvency).
    Tech Review Follow-Up report. Exhibit 1.4.51-14, Guide for Tech Review Follow-Up Report (Field Insolvency and CIO).
    Tech Review No Follow-Up report. Exhibit 1.4.51-15, Guide for Tech Review No Follow-Up Report (Field Insolvency).
    Unfiled Plans report (Chapter 11 only). Exhibit 1.4.51-19, Guide for Unfiled Plans Report (Field Insolvency).
    The following reports are required to be reviewed "Semi-Annually" :
    CSED Follow-Up report. Exhibit 1.4.51-26, Guide for CSED Follow-Up Report (Field Insolvency and CIO).
    The following reports are required to be reviewed "Annually" :
    Aged Cases report. Exhibit 1.4.51-27, Guide for Aged Cases Report (Field Insolvency and CIO).
    :

  4. With Territory / Operation Manager's or Department Manager's approval, AIS Business Objects reports may be updated with additional Business Objects reports. To be approved the new reports must serve the purposes of the original AIS Business Objects reports and increase efficiency.

  5. As each case on a report is worked, the caseworker should document the AIS history in accordance with IRM 5.9.5.4(2) , History Documentation. Each case on a report should be checked off when action has been completed and the history is documented.

  6. Minimum retention of completed reports be they optional or mandatory, unless specified otherwise by the Formal Retention Standards, for completed reports are as follows:

    • Weekly reports are retained for one month, except LTS reports that are retained for one cycle.

    • Monthly reports are retained for one quarter.

    • Quarterly reports are retained for six months.

    • Annual reports are retained for two years.

    Note:

    When exceptions to these retention periods apply, the exceptions appear within the report exhibits found at the end of this IRM. Field Insolvency and CIO managers must establish controls to verify these reports are worked timely.

  7. The chart below lists actions which are "Mandatory" in bankruptcy case processing. The chart separates duties overseen by managers in Field Insolvency, overseen by managers at the CIO, and duties which are supervised by managers in both functions. The links to exhibits and IRM references cited within the chart provide cross references to report tools or IRM procedures for meeting those actions.

    Field Insolvency Both CIO
    Meet bar dates.
    See Exhibit 1.4.51-9, Guide for Bar Date Follow-Up Report (Field Insolvency).
    Resolve stay violations timely.
    See IRM 5.9.3.5, Automatic Stay.
    Work DDRs timely.
    See IRM 5.9.17.4, Time Frames for Required Actions.
    Monitor plan filings and review plans.
    See Exhibit 1.4.51-20, Guide for Delinquent Case Report (Field Insolvency).
    See Exhibit 1.4.51-19, Guide for Unfiled Plans Report (Field Insolvency).
    Case monitoring.
    See Exhibit 1.4.51-11, Guide for the Litigation Transcript System (LTS) Reports (Field Insolvency and CIO).
    Run IIP processes C and D.
    See IRM 5.9.12.5, Insolvency Interface Program (IIP).
    Attend 341 hearings when appropriate.
    See IRM 5.9.2.5, First Meeting of Creditors.
    Protect collection statutes.
    See Exhibit 1.4.51-26, Guide for CSED Follow-Up Report (Field Insolvency and CIO).
    Run IIP process J.
    See IRM 5.9.12.5, Insolvency Interface Program (IIP)..
    Protect assessment statutes.
    See Exhibit 1.4.51-18, Guide for ASED Follow-Up Report (Field Insolvency).
    Ensure timely responses to the Taxpayer Advocate.
    See IRM 5.9.3.8, Taxpayer Advocate Service (TAS).
    Work trustee refund turnover requests.
    See IRM 5.9.6.2.3, Chapter 7 Tax Refunds to Trustees.
    Respond to claim objections timely and follow-up.
    See Exhibit 1.4.51-22, Guide for Referral to Counsel Report (Field Insolvency).
    Generate and work litigation transcripts and initiate case closure timely.
    See Exhibit 1.4.51-13, Guide for Court Closure Follow-Up Report (Field Insolvency and CIO).
    Work IIP error reports and PIT reports.
    See IRM 5.9.12.5.2, Potentially Invalid TIN (PIT) List.
    Submit plan objection referrals timely and follow-up.
    See Exhibit 1.4.51-22, Guide for Referral to Counsel Report (Field Insolvency).
    Generate and work Aged Case Report annually.
    See Exhibit 1.4.51-27, Guide for Aged Cases Report (Field Insolvency and CIO).
    Work IIP status reports.
    See IRM 5.9.12.5.1, IIP Status Reports.
    Address adequate protection when appropriate.
    See IRM 5.9.8.6, Adequate Protection.
    See IRM 5.9.9.4, Adequate Protection in the Chapter 12 Case.
    Work LAMS Not Found on AIS Case Listing report.
    See Exhibit 1.4.51-23, Guide for LAMS Not Found on AIS Case Listing Report (Field Insolvency and CIO).
    Work LAMS Closed Case Listing report.
    See Exhibit 1.4.51-16, Guide for LAMS Closed Case Listing Report (Field Insolvency and CIO).
    Run IIP 2 (ADS).
    See IRM 5.9.12.6, Automated Discharge System.
    File administrative claims.
    See IRM 5.9.8.13, Post-petition/Pre-confirmation BMF Monitoring
    See IRM 5.9.8.14.1, Post-petition Debts - Chapter 11 Individuals.
    See IRM 5.9.8.19.4.2, Post-Confirmation Tax Liabilities of the Individual Debtor (Post-BAPCPA).
    See IRM 5.9.13.11, Administrative Claims.
    Release liens timely.
    See Exhibit 1.4.51-25, Guide for Lien Research Report (Field Insolvency and CIO).
    See IRM 5.9.17.5.2, Collection from Exempt, Abandoned, or Excluded Property (EAEP).
    Work ADS process K and L errors.
    See IRM 5.9.12.6, Automated Discharge System.
    Monitor plan payments.
    See Exhibit 1.4.51-20, Guide for Delinquent Case Report (Field Insolvency).
    Load cases to AIS and ensure TC 520 input timely.
    See IRM 5.9.12.5, Insolvency Interface Program (IIP).
    See IRM 5.9.12.7, Electronic Noticing System.
    Distribute time sensitive mail timely.
    See IRM 5.9.11.4.2, Time Sensitive Mail.
    Address delinquent plans.
    See Exhibit 1.4.51-19, Guide for Unfiled Plans Report (Field Insolvency).
    See Exhibit 1.4.51-28, Guide for Plan Review Report (Field Insolvency).
    Address follow-up actions timely.
    See Exhibit 1.4.51-14, Guide for Tech Review Follow-Up Report (Field Insolvency and CIO).
    Mirror MFT 31 accounts for all chapters.
    See IRM 5.9.17.23, Mirrored and Non-Master File (NMF) Modules.
    When incomplete prompt determination request received, advise requester of missing documentation when all documentation received, submit package to Exam.
    See IRM 5.9.4.9.1, Processing Prompt Determination Requests.
    Review and sign manual refund requests.
    See IRM 5.9.16.3, Manual Refunds.
    Receive and review prompt determination requests for acceptable submission; send complete packages to Exam and incomplete packages to Field Insolvency.
    See IRM 5.9.4.9.1, Processing Prompt Determination Requests.
    Pursue exempt, abandoned, or excluded property when appropriate.
    See IRM 5.9.17.5, Exempt Abandoned. or Excluded Property (EAEP).
    Work Non-Master File (NMF) listing.
    See Exhibit 1.4.51-24, Guide for Non-Master File Listing Report (Field Insolvency and CIO).
    Work trustee refund turnover requests.
    See IRM 5.9.6.2.3, Chapter 7 Tax Refunds to Trustees.
    Submit fraud referrals.
    See IRM 5.9.4.12.1, Fraud Referrals.
    Identify cases mis-assigned by CAG or left unassigned by CAG and assign them manually.
    See Exhibit 1.4.51-29, Guide for Case Assignment Reports (Field Insolvency and CIO).
    See information under column named both
    Secure delinquent returns.
    See IRM 5.9.4.16, Unfiled Pre-Petition Returns.
    See IRM 5.9.4.17, Unfiled Post-Petition Returns..
    See Exhibit 1.4.51-30, Guide for Letter 1714 Follow-Up Report (Field Insolvency).
    Verify correct case grade assignments through CAG.
    See Exhibit 1.4.51-29, Guide for Case Assignment Reports (Field Insolvency and CIO).
    See information under column named both
    Initiate referrals to Field Collection when applicable.
    See Exhibit 1.4.51-31, Guide for Other Investigation (OI) Follow-Up Report (Field Insolvency).
    See Exhibit 1.4.51-32, Guide for ICS Inventory Report (Field Insolvency).
    Identify fraud.
    See IRM 5.9.4.12, Bankruptcy Fraud.
    See information under column named both
    Request TFRP investigations from Field Collection timely or begin in-house TFRP investigations timely.
    See IRM 5.9.3.10, Trust Fund Recovery Penalty.
    See Exhibit 1.4.51-31, Guide for Other Investigation (OI) Follow-Up Report (Field Insolvency).
    Address significant cases.
    See Exhibit 1.4.51-33, Guide for Large Dollar Report (Field Insolvency and CIO).
    See information under column named both
    Address significant cases.
    See IRM 5.9.4.15.3, Significant Bankruptcy Case Referrals.
    Post all payments received regardless of the Chapter.
    See IRM 5.9.15, Payments in Bankruptcy.
    See information under column named both
    Take appropriate actions on post-petition liabilities.
    See Exhibit 1.4.51-11, Guide for the Litigation Transcript System (LTS) Reports (Field Insolvency and CIO).
    See Exhibit 1.4.51-21, Guide for LAMS Post-Petition Case Listing Report (Field Insolvency).
    See IRM 5.9.16.2.2, New Assessment Reports.
    See information under column named Field Insolvency See information under column named Field Insolvency

Assigning Work

  1. Insolvency ensures fairness and integrity in case assignment through using an equitable process for all taxpayers by using an automated system, the Electronic Noticing System (ENS) to load bankruptcy cases directly from the court. See IRM 5.9.12.7, Electronic Noticing System. In addition, the Case Assignment Guide, described below in IRM 1.4.51.9.1, Case Assignment Guide, explains the automated grading and assignment of new cases received by Insolvency. These automated systems ensure no one individual can control the enforcement selection decision making process which aligns with IRM 1.2.1.2.36, Policy Statement 1-236 (Rev. 1), Fairness and Integrity in Enforcement Selection. Adherence to the principles in this policy statement ensures the Service is meeting its commitment in the IRS Mission Statement by enforcing the tax law with integrity and fairness to all. An important component of fairness and integrity in enforcement selection includes the assignment of work by the group manager. The purpose of this section is to provide a framework for the assignment of work to ensure case assignments are consistent with the goals and objectives of the Service and are free from personal bias.

  2. Managers are responsible for ensuring that cases are assigned at the proper grade, based on all indicators of case difficulty.

    Note:

    Developmental Bankruptcy Specialist (GS-07) and trainee Bankruptcy Specialist (GS-05) will be assigned cases with a case grade of GS-09 because Insolvency cases generally are not graded below Bankruptcy Specialist journey level (GS-09). See IRM 1.4.51.9.2(1), Case Grade. Managers will carefully select the cases assigned to these employees to ensure that cases are appropriate for the experience level of the employee and for development of the employee into a GS-09 Bankruptcy Specialist, capable of performing all aspects of the position independently. The manager or on the job instructor, if one is assigned, will provide closer than normal supervision and review the work of these employees frequently to ensure that the employee is developing and making progress toward the full performance level of GS-09 Bankruptcy Specialist.

  3. Managers must review inventory and case grade reports monthly to ensure employees are not working over 25% direct time above grade. If employees works higher grade cases, the manager should track the higher graded work to ensure the 25% threshold is not exceeded. Employees who exceed 25% level for a four-month period may be entitled to a temporary promotion.

Case Assignment Guide

  1. The Case Assignment Guide (CAG) was developed to promote consistency in the assignment of graded Insolvency cases.

  2. AIS automates the grading and assignment of new cases received by Insolvency. The level of difficulty or grade of a case is based on characteristics apparent upon initial receipt. The pre-assignment grade is only an initial prediction and should be adjusted when post-assignment factors justify a change. See Exhibit 1.4.51-35, CAG Pre-Assignment Factors, and Exhibit 1.4.51-36, CAG Pre-Assignment Difficulty Indicators. Automated CAG uses the following four factors in the pre-assignment process:

    • Business Operating Division (BOD)

    • File source

    • Chapter

    • Balance due information

  3. Post-assignment factors are used either to reassign a case or to assign certain issues or tasks to an appropriately graded employee. Managers should be familiar with the post-assignment factors and take steps to reassign cases to the appropriate grade level of employee when the following post-assignment factors are identified:

    • Case action

    • Communication

    • Supervisory control

    See Exhibit 1.4.51-37, Post-Assignment Difficulty Indicators Factor 5: Case Action, Exhibit 1.4.51-38, Post-Assignment Difficulty Indicators Factor 6: Communication, and Exhibit 1.4.51-39, Post Assignment Difficulty Indicators Factor 7: Supervisory Control.

  4. The post-assignment checklist, designed to perfect the post-assignment grade of an Insolvency case, is a guide for documenting final assignment. Managers are to measure cases against the three post-assignment factors before reassigning cases. While meeting all three factors is not necessary, cases will generally not be graded at a higher level unless a majority of the factors are met at the higher level or the case contains a difficulty indicator with significant impact. See Exhibit 1.4.51-40, Post-Assignment Checklist Factor 5: Case Action, Exhibit 1.4.51-41, Post-Assignment Checklist Factor 6: Communication, and Exhibit 1.4.51-42, Post-Assignment Checklist Factor 7: Supervisory Control.

  5. Managers must designate employee assignment numbers for the inventories under their responsibility. All bankruptcy court jurisdictions must have an employee number assigned for every combination of chapter, case grade and alpha assignment. Once the inventory assignments have been designated, the manager must ensure the employee assignment information is entered in AIS for Automated CAG to work effectively. The Case Assignment Profile Matrix stores employee information so Automated CAG can assign cases to the appropriate employee. Employee assignment information cannot overlap. Exhibit 1.4.51-43, Case Assignment Profile Matrix, contains a template to be used as a guide in preparing the matrix. A template should be prepared for each court jurisdiction.

  6. Automated CAG generates a suite of reports to assist Insolvency managers in monitoring the flow of newly assigned cases and in balancing inventories. These reports identify unassigned cases that may have to be manually assigned and are tools for selecting cases for review. (See Exhibit 1.4.51-29, Guide for Case Assignment Reports.)

  7. CAG has a Manager Only menu option whose access is limited to certain employee assigned roles. This option allows Insolvency managers to supervise the assignment of work and facilitates conducting case reviews. Managers, particularly those in Field Insolvency, play a pivotal role in both the pre-assignment and post-assignment processes. They must monitor inventory receipts to ensure new cases are properly graded and assigned. They must also verify previously assigned cases are reassigned and re-graded timely when appropriate. Corrective actions must be taken immediately by the manager or designated employee in the following situations:

    1. When case dockets are ungraded, managers must input the appropriate information to grade and/or assign cases.

    2. When cases are converted from one chapter to another, the cases must be manually reassigned and re-graded.

    3. Errors from IIP Processes C and D must be resolved promptly because these errors can prevent Automated CAG from grading and assigning cases. Once the errors are resolved, CAG assigns the case when IIP is next run.

  8. The Case Grade Report should be reviewed by Insolvency managers at least monthly to identify the distribution of graded case assignments. The report provides a list of employee assignment numbers and reflects the inventory distribution for each including the percentage of cases for each grade assignment. Reviewing this report will assist managers in monitoring inventories to ensure graded cases are assigned at the appropriate levels. (See Exhibit 1.4.51-12, Guide for Case Grade Report - Manager only (Field Insolvency).) Review of this report may also identify ungraded cases that require grading. In order to see the specific cases that need grading run the Ungraded Case Follow Up Report. See Exhibit 1.4.51-29, Guide for Case Assignment Reports (Field Insolvency and CIO), for more information.

Case Grade

  1. Cases are issued with a case grade of 07, 09, 11, or 12. These case grade levels reflect the anticipated level of difficulty. Exhibit 1.4.51-36, CAG Pre-Assignment Difficulty Indicators, reflects the criteria used to determine the case difficulty level.

    Note:

    For chapter 7A cases initially grade below GS-9, the Group Manager should review the case based on the post petition assignment factors described in Exhibit 1.4.51-44, CAG Post- Assignment, to determine whether the case should be regraded upon assignment to a Bankruptcy Specialist.

  2. Managers are responsible for reviewing and maintaining the correct case grade. Case grade levels can be either increased or decreased. There are systemic processes in place to predict the grade level of a case. If the predicted case grade does not appear to be accurate, the manager may re-grade the case per the Case Assignment Guide criteria in Exhibit 1.4.51-44, CAG Post-Assignment. This can be done at any time: upon receipt, upon assignment to an employee, and during case reviews. Employees should be encouraged to bring mis-graded cases to their manager’s attention.

  3. Managers will not normally change the grade of a case unless it meets factors at the lower or high level. Document in the case history the reason for changing the grade of a case.

  4. Managers should change the grade of a case if receipt of additional information or case circumstances warrant. If additional explanation is needed, the manager should write a narrative history as well.

  5. When it is determined that the difficulty level of a case has changed, the manager may adjust the grade level.

  6. Managers may need to consider a reassignment of the case if a grade level change is made.

Maintaining Inventories

  1. Group managers are responsible for monitoring inventory levels to ensure each employee has an appropriate number of cases that can be resolved most effectively and efficiently based on his/her grade level, experience, and expertise.

Inventory Adjustments
  1. An inventory adjustment is a percentage-based adjustment to the standard range. It is based on an evaluation of time spent on activities other than work on assigned cases (direct case time) and normal overhead. Examples of situations where a manager may consider an inventory adjustment are:

    1. Collateral assignments (e.g., NTEU Representative, EEO Counselor/Investigator, details out of office, instructing assignments, coaching, etc.).

    2. Customer Service assignments (e.g., Servicing walk-in taxpayers during filing season, ACS walk-in taxpayers).

    3. Automation support.

    When an adjustment to an employee’s inventory is warranted because of any of these circumstances, use the projected time expenditure by the employee to determine the appropriate adjustment.

    Example:

    A manager reviews a GS-12 employee’s time over the last six months and determine the employee appropriately spent 25% of her/his time on collateral assignments. An adjustment of 25% is indicated in this case.

    Inventory levels may be re-adjusted as warranted. Managers should perform quarterly reviews of actual time their employees spend on collateral assignments and make adjustments as needed. Adhere to these guidelines when considering any adjustments to employee inventories.

  2. When additional cases need to be assigned, managers should look to the following sources for additional work:

    • Other employees

    • Other groups (with concurrence from the Territory / Operation Manager)

Reassignment of Departing Employee Inventory

  1. Where inventory will be abandoned for periods of 90 days or more (for example an employee is reassigned, on extended leave, or long term detail) the group manager will consider performing the following actions:

    1. Holding assignment of additional work (after confirmation of the employee’s effective date for detail, reassignment, retirement, etc.).

    2. Reviewing all inventory with the departing employee (including cases on the AIS system) and identifying those which can be resolved prior to the employee leaving, or reassigned to the remaining employees in the group. The transfer of these cases should be completed within a reasonable period of time, normally within 45 days. When appropriate, re-grade cases based on the post assignment criteria.

Initial Case Processing

  1. Insolvency Interface Program (IIP). The CIO must run IIP processes C and D daily to ensure new cases are processed timely. If IIP is unavailable the manager must direct employees to input bankruptcy freeze codes (TC 520s) with appropriate closing codes manually within five work days of receiving notification of new bankruptcies. (See IRM 5.9.5.6.1, Closing Codes, for TC 520 closing codes.)

    1. Caseworkers must add bankruptcy court case information into AIS as soon as Insolvency receives electronic notice, paper notice, or referral information from other internal sources (e.g., Automated Collection System (ACS), Customer Service, or Accounts Management). Adding new cases to AIS is a CIO duty. However, Field Insolvency caseworkers are not prohibited from loading new cases that come to their attention through the identification of a stay violation.

    2. The Potentially Invalid TIN (PIT) and Cross-Reference TIN Reports must be worked daily. The court debtor name and TIN data must match the master file information to allow the TC 520 to post to the correct taxpayer's account. The CIO will work all of these reports except for those pertaining to Chapter 9 and Chapter 15 cases. Cases that cannot be resolved by the CIO must be transferred to Field Insolvency for resolution.

    3. IIP generates reports identifying cases in status 22 - ACS, status 24 - Federal Payment Levy Program (FPLP), status 60 - installment agreements (IA), status 26 - field revenue officer (RO), and status 71 - Offer in Compromise (OIC). The CIO works all status reports except those pertaining to Chapter 9 cases, Chapter 15 cases, and some Chapter 11 cases. Cases that cannot be resolved by the CIO must be transferred to Field Insolvency for resolution. (See IRM 5.9.12.5.1, IIP Status Reports.)

    4. TC 520 closing codes in the 60 - 67 series, 81, and 83 - 85 series are input taking into consideration court rules, standing orders, and the IRS's mission to increase compliance. Only the CIO is authorized to change closing code designations on IIP and may only do so with approval from Collection Policy.

    5. Managers are to analyze the impact on work processes when the TC 520 closing code used by their group changes.

Protection of the Government's Interest

  1. Receipt of Notices. Insolvency must protect the interests of the government during bankruptcy proceedings. Following the procedures listed below will increase appropriate and timely processing actions.

Proofs of Claim Filing

  1. Timely Claims. In most cases to be timely, a proof of claim (POC) must be filed before 180 days (the government bar date) from after the date of the order of relief (which is the date the bankruptcy petition was filed in voluntary cases). (See 11 USC 502, Allowance of claims or interests, and Bankruptcy Rule 3002, Filing Proof of Claim or Interest.) Claims prepared through Automated Proof of Claim (APOC) processing should be filed prior to the first meeting of creditors. A full discussion of time frames for filing claims can be found in IRM 5.9.13.7, Bar Dates.

  2. "Proof Required" and "Bar Date" fields on AIS. The "Proof Required" field on AIS is not protected. Anyone with update capabilities can change the field from "Yes" (a claim is required) to "No" (a claim is NOT required). Caseworkers can also alter the bar date field. Inappropriate alteration of the bar date may give the impression more time is available to file a POC than legally exists. The audit trail available in the CAG Manager's Only menu records information when the Proof Required or Bar Date fields are updated.

  3. Missed Bar Dates. If a bar date has expired, the person identifying the missed bar date will, within 10 days, complete Part A of Form 14167, Bar Date Expiration Report, and will enter a statement in the case history indicating that a preliminary Form 14167 has been prepared. If not prepared by the group manager, the completed Form 14167 should be forwarded to the group manager for review. Within 60 days of identification, the group manager will review the case history, and any other relevant information, determine if further administrative action is warranted, and whether disciplinary action is appropriate. The group manager will complete Part B of Form 14167 with the results of the investigation. If disciplinary action is warranted, the manager will prepare a memo that details why the Bar Date expired, and why disciplinary action is warranted. The Form 14167 and memo should be prepared and routed as follows:

    1. Field Insolvency: from group manager to Territory Manager. The Territory Manager will review the memo and determine if disciplinary action is warranted. Form 14167 will be forwarded to the Director, Specialty Collection - Insolvency for signature. After signature, the case history will be updated to indicate that the final Form 14167 has been processed and the investigation completed.

    2. Centralized Insolvency Operation: from unit manager to Department Manager. The Department Manager will review the memo and forward to the Operation Manager for concurrence of no action/potential disciplinary action. The Operation Manager will forward the Form 14167 to the Director, Specialty Collection - Insolvency for signature if disciplinary action is warranted.

    Note:

    The report will not be required for expired bar dates in cases where the Service did not receive notification of the bankruptcy prior to the last day for filing a proof of claim as defined in Bankruptcy Rule 3002(c), Time for Filing, or Bankruptcy Rule 3003(c), Filing Proof of Claim, whichever is applicable.

    Reminder:

    All Forms 14167 will be retained for 2 years.

Adequate Protection

  1. Secured Assets. Where valid NFTLs have been filed and the criteria in IRM 5.9.4.15.4, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡, are met, Insolvency should pursue adequate protection of the government's interest in assets that will lose significant value during the life of the plan.

    Note:

    Adequate protection primarily concerns Chapter 11 and Chapter 12 cases, because debtors in those cases are generally operating an ongoing business and using property subject to liens such as inventory or accounts receivable. Pursuit of adequate protection is possible in Chapter 13 cases, but requesting a lift of the stay is often a more appropriate tactic.

341 Hearings

  1. Attendance by Insolvency. Representatives from Insolvency should attend 341 first meeting of creditors when appropriate and staffing allows. (See IRM 5.9.2.5, First Meeting of Creditors.)

Plan Review

  1. Significant Cases. Significant cases must be referred to Counsel regardless of chapter. (See IRM 5.9.4.15.3, Significant Bankruptcy Case Referrals.) The AIS history must annotate if Counsel has assumed the responsibility for plan review.

  2. Review and Documentation. IRM 5.9 provides detailed text and procedures for reviewing and documenting plans. (See IRM 5.9.5.4(3), Chapter 13 Plan Documentation, IRM 5.9.5.4(4), Chapter 11 and Chapter 12 Plan Documentation, IRM 5.9.8.14.2, The Plan of Reorganization, IRM 5.9.9.5, Chapter 12 Plans, IRM 5.9.9.5.2, Plan Modification, IRM 5.9.9.6, Reasons to Object to the Plan, and IRM 5.9.10.5, The Chapter 13 Plan.)

    Note:

    If review of a plan is not documented in the AIS history, it is considered not to have been done.

  3. Confirmed and Amended Plans. If proposed plan provisions affecting the treatment of the Service are deemed inadequate by the Field Insolvency caseworker, the AIS history must include documentation of the confirmed plan or a statement that an inadequate plan has been confirmed. When a confirmed plan is amended, where the amendment affects the interests of the Service, the amended plan must be documented in the AIS History and the Confirmed Plan Monitoring (CPM) screen updated.

Compliance Monitoring

  1. Multiyear Plans. Insolvency caseworkers should monitor post-petition compliance by the debtor when long term plans are confirmed. Some debtors make high payments mandated by trustees by lowering their withholding or by failing to make federal tax deposits, leading to unpaid post-petition taxes. The Bankruptcy Abuse Prevention and Consumer Protection Act of 2005 (BAPCPA) added provisions to address post-petition tax compliance in bankruptcy cases.

    • Any case filed on or after October 17, 2005, under any chapter, is subject to dismissal or conversion if the debtor fails to file a post-petition return. (See 11 USC 521(j).)

    • In Chapter 11 cases filed on or after October 17, 2005, failure to file a post-petition return is an express ground for dismissing or converting a case. (See 11 USC 1112(b)(4)(I).)

    • Because fewer options are available to address post-petition compliance in Chapter 12, (e.g., no provision in the Bankruptcy Code for filing post-petition claims), Insolvency should seek guidance from Counsel when appropriate.

    See IRM 5.9.8.13, Post-petition/Pre-confirmation BMF Monitoring, IRM 5.9.8.14.1, Post-petition Debts - Chapter 11 Individuals, IRM 5.9.9.10, Monitoring Compliance, and IRM 5.9.10.9, Post-Petition Tax Liabilities, for more information.

Bankruptcy Fraud

  1. Fraud Detection. All caseworkers, regardless of grade or position title, should review cases with an eye for indications of bankruptcy fraud. However, Field Insolvency is responsible for referring accounts to the Fraud Technical Advisor (FTA) or to Counsel when warranted. (See IRM 5.9.4.12, Bankruptcy Fraud, and IRM 5.9.17.8.2, The Fraud or Willful Evasion Exception to Discharge.)

NFTL Refiles

  1. NFTL Refile. Procedures outlining the issues involved and the reviews required for potential NFTL refiles are found in IRM 5.9.5.9.2, Refiling Notices of Federal Tax Lien (NFTL), IRM 5.9.8.19.2, Monitoring the Plan and Reviewing for Refiling of the Notice of Federal Tax Lien (NFTL), and IRM 5.9.17.5.3(12), Notice of Federal Tax Lien (NFTL) Refiles.

Unfiled Returns

  1. Estimated Claims. Estimated claims for unfiled, unassessed tax periods impact collection of the correct amount of tax, because estimated claims prompt delinquent debtors to file tax returns. However, estimated claims filed by the Service can be the source of objections if debtors and their representatives are not aware of the unfiled returns.

  2. BAPCPA Change. The Service has addressed compliance requirements brought about by BAPCPA by including annotations on claims and sending courtesy copies of Letter 1714, Request For Missing Tax Returns, to trustees to provide information regarding unfiled returns. The Letter 1714, courtesy copy alerts the trustee that the Service may be amending its POC or filing a motion to dismiss or convert the bankruptcy. The trustee may wish to delay distributions or plan confirmation until this tax administration issue has been resolved.

  3. Correcting the AIS CPM Screen. Managers must ensure estimated claims are amended when debtors' returns are filed and assessed if the debtors' returns do not reflect the amounts shown on our estimated claim. To avoid an objection, Managers can ensure the caseworker amended the claim when a return is received. Whenever a claim is amended, the AIS CPM screen must be adjusted to reflect the amended claim period(s), so collected funds are appropriately applied to tax rather than transferred to unidentified remittance.

Automated Proof of Claim (APOC)

  1. The APOC program systemically calculates and classifies liabilities to populate AIS proofs of claim fields so Forms B410, Proof of Claim, can be produced for the bankruptcy court. A full discussion on employee instructions for generating and perfecting APOC data is found in IRM 5.9.14, Automated Proofs of Claim (APOC). This IRM 1.4.51 subsection deals with manager reports and APOC permissions, topics not covered in IRM 5.9.14.

  2. Managers can access APOC by accessing a case and selecting the "APOC" tab.

  3. Cases that were selected for APOC processing but did not make it through the process will need to be “Restored to AIS” by an Insolvency Manager. Managers should select the "Restore APOC" button located on the APOC Case Detail screen to restore these cases when necessary.

  4. APOC Reports. The following is a list of APOC reports that should be reviewed by managers:

    1. Flagged Cases report. The Flagged Cases report lists all cases that have unresolved flags. Most flags should be worked at least five calendar days before the 341 meeting.

    2. Period Detail Flag - Credits Posted After Petition Date report. The Period Detail Flag - Credits Posted After Petition Date report lists all modules with a TC designated as Pay in the Payment Designation Tables and the TC date is greater than the Petition Date. Since these credits could be in "Violation of the Automatic Stay" caseworkers should work the cases on this report within "five" calendar days of APOC identifying the flagged condition.

    3. Period Detail Flag - Lien Recorded Date Blank or After the Petition Date report. The Period Detail Flag - Lien Recorded Date Blank or After the Petition Date report lists all modules with a notice of lien date that is either not recorded on AIS, or the date recorded is greater than the Petition Date. Since these NFTLs could be in "Violation of the Automatic Stay" , the caseworker should work the cases on this report within "five" calendar days of APOC identifying the flagged condition.

    4. Period Detail Flag - Secured Period report. The Period Detail Flag - Secured Period report lists all modules classified by APOC as "Secured" based on AIS Lien records. The caseworker should work the cases on this report within "10" calendar days of APOC identifying the flagged condition for all chapters other than Chapter 7 and Chapter 13.

    5. APOC Summary report. This report provides the manager with statistical data relating to the processing of cases through APOC.

Insolvency and IDRS

  1. Group managers are responsible for ensuring that their employees have access to the Integrated Data Retrieval System (IDRS) command codes necessary to perform their assigned tasks and required research.

  2. Examples of the tasks Insolvency performs on the IDRS are:

    1. Account research for a filing compliance check

    2. Assigning a case to another area (e.g., assign a case to a revenue officer or the Automated Collection System (ACS))

    3. Resolving incompatible data (e.g., matching data from the bankruptcy petition to a taxpayer’s name and social security number on the IRS’s master file)

    4. Accessing account information to prepare adjustment requests

    5. Inputting or reversing bankruptcy freezes

    6. Inputting account adjustments other than bankruptcy freeze actions (CIO only)

  3. Whenever practical, Insolvency groups should not be included with IDRS data security work groups from other functions within SB/SE (for example, Civil Enforcement Advice and Support Operations (CEASO) or Field Collection (FC)). If the physical office accommodates two or more Insolvency groups, all of the Insolvency groups in the same office can be under the same IDRS group code. To change, consolidate, or request a new group code, the IDRS-Unit Security Representative (USR) or the Functional Security Coordinator (FSC) must be contacted. By keeping Insolvency separate from other groups, managers can identify and oversee command codes needed to perform Insolvency specific duties.

  4. Managers must ensure required security measures are in place regarding on-line IDRS account adjustments.

  5. Managers should monitor command code usage by all members of the group. Suggested profiles for Insolvency employees may include the following:

    Bankruptcy Specialists (GS-1101), Revenue Officer Advisors (GS-1169), and Tax Examining Technicians (GS-0592) command codes:
    • ACTON

    • AMDIS

    • ASGNB

    • ASGNI

    • BMFOL

    • BMFPG

    • BRTVU

    • CFINK

    • COMPA

    • EFTAD

    • EMFOL

    • ENMOD

    • ESTAB

    • FFINQ

    • FIEMP

    • FRM34

    • FRM49

    • FRM77

    • IADIS

    • IAGRE

    • IMFOB

    • IMFOL

    • INOLE

    • INTST

    • IRPTR

    • LEVYS

    • MESSG

    • MFREQ

    • MFTRA

    • NAMEE

    • NAMEI

    • NAMES

    • RECON

    • REQ77

    • RTVUE

    • STATB

    • STATI

    • STAUP

    • SUMRY

    • TERUP

    • TPIIP

    • TRDBV

    • TXMOD

    • UNLCE

    • UPCAS

    • UPDIS

    • UPTIN

    Additional CIO Bankruptcy Specialists (GS-1101) and CIO Tax Examining Technicians (GS-0592) command codes (used for account adjustments, issuing letters, inputting refunds, etc.):
    • ADD24

    • ADD34

    • ADJ54

    • BNCHG

    • DRT24

    • ENREQ

    • IAORG

    • IAREV

    • INCHG

    • LETER

    • LPAGD

    • LPAGE

    • REQ54

    • RFUND

    • TERUP

    Support Tax Examining Technicians (GS-0592) command codes:
    • ACTON

    • AMDIS

    • BMFOL

    • COMPA

    • ENMOD

    • FIEMP

    • FRM77

    • IADIS

    • IMFOB

    • IMFOL

    • INOLES

    • INTST

    • IRPTR

    • MESSG

    • MFREQ

    • MFTRA

    • NAMEE

    • NAMEI

    • NAMES

    • RECON

    • REQ77

    • RTVUE

    • SUMRY

    • TERUP

    • TRDBV

    • TXMOD

    Note:

    The command codes listed for the Support Examining Technicians must be in their profiles for the corresponding programs to work properly. This is true for anyone running IIP, ADS, or APOC.

  6. A command code is considered "sensitive" if it can be used to adjust account balances, change the status of a tax module or account, or affect the tax liability. Sensitive command code combinations give an employee the ability to perform more than one type of transaction where the intentional mishandling of a taxpayer’s account may occur (e.g., change the entity or address information of an account and transfer payments).

    Managers who sign manual refunds are restricted from having the below command codes in their personal profiles:
    • ADC24

    • ADC34

    • ADD24

    • ADD34

    • ADD48

    • ADJ54

    • AMCLS

    • BNCHG

    • DRT24

    • DRT48

    • FRM34

    • INCHG

    • REFAP

    • RFUND

    • URAPL

    • URREF

    • XSAPL

    • XSREF

  7. The following chart lists common IDRS command codes and their functions.

    Insolvency Activity Research Command Code Action Command Code
    Address Change ENMOD ENREQ, INCHG, BNCHG
    Adjustments to Tax, Penalty, Interest, and Credit Reference Changes to IDRS Accounts TXMOD REQ54 / ADJ54
    REQ77 / FRM77
    Controlling a Case TXMOD ACTON
    Credit Transfers TXMOD ADD24 / ADC24 / DRT24
    ADD34 / ADC34 / FRM34
    ADD48 / ADC48 / DRT48
    Delinquent Account Issues IMFOLI, TXMOD N/A
    Delete Transactions, Same Day Input TXMOD TERUP
    Dummy Account SUMRY MFREQ
    Entity Information and/or Changes ENMOD, INOLET ENREQ, INCHG, BNCHG
    Exam Issues AMDISA N/A
    Fact of Filing IMFOLI FFINQ
    History Items TXMOD ACTON
    Installment Agreements IADIS IAORG, IAREV
    Interest and Penalty Bal Due Computations TXMOD INTST, COMPA
    Reassigning an Account TXMOD TSIGN
    Requesting Returns, Transcripts TXMOD, IMFOLI ESTAB, MFTRA
    Social Security Number Research INOLET NAMES
    Tax Module Research TXMOD
    SUMRY
    IMFOL
    BMFOL
    RTVUE
    BRTVU
    N/A
    Unpostables TXMOD UPTIN, UPCAS, UPDIS
    Display Taxpayer Name, Address, Spouse Cross Reference Data, Filing Requirements, DOB, BOD, etc. INOLE N/A
    Request IRP Transcripts for Specific TIN and Tax Year IRPTR N/A
    EIN Research INOLET NAMEE
    Online Display of Tax Return Information RTVUE, BRTVU N/A
    Employee Master File Online EMFOL N/A
    Update the Status of Modules that Are or Have Been Balance Due Modules STAUP N/A
    Research for Trust Fund Recovery Penalty Assessment UNLCE N/A
    Enter IDRS SINON N/A
    Exit IDRS SINOF N/A
    Display All Command Codes in Your Profile SFDISP N/A

  8. Resources:

    • IDRS Command Codes Job Aid on SERP at: http://serp.enterprise.irs.gov/job-aids/command-code/command-code.html

    • Document 6209, IRS Processing Codes and Information

    • IRM 10.8.34, IDRS Security Controls

    • IRM 2.3, IDRS Terminal Responses

    • IRM 2.4, IDRS Terminal Input

Closed Cases

  1. Dismissal actions must be initiated within 30 calendar days of the Service's receiving notification of dismissal.

  2. Managers must ensure case discharge processing begins no later than 30 calendar days after receipt of the discharge notice for all cases except non-liquidating corporate Chapter 11 cases or individual Chapter 11 cases commenced prior to October 17, 2005. Discharge actions on non-liquidating corporate Chapter 11 cases or individual Chapter 11 cases commenced prior to October 17, 2005, must be initiated within 30 calendar days of plan completion.

    Note:

    Investigation into the pursuit of exempt, abandoned, or excluded property is considered to be an initiation of the discharge process.

  3. The Service will initiate closing actions required for the release of liens on discharged taxes within 30 days of receipt of notice of the discharge order. The lien will systemically release once all adjustments have posted to IDRS. Generally, manually requesting a lien release is not required. However, if a certificate of release will not be systemically issued, the release should be requested manually on the Automated Lien System (ALS). Quarterly checking of the Lien Research report will identify liens that have not been released so corrective actions can be taken. See Exhibit 1.4.51-25, Guide for Lien Research Report (Field Insolvency and CIO). In the instance of individual Chapter 11 cases filed prior to BAPCPA or non-individual Chapter 11 cases filed at any time, closing actions will be initiated within 30 calendar days from plan completion. In these Chapter 11 cases, manually requesting the lien release may be required if the adjustments will not result in a systemic release within 30 days of receipt of the final plan payment.

    Note:

    Under IRC 6325, Release of Lien or Discharge of Property, if the assessments for any periods are fully satisfied via full payment, were abated other than due to a bankruptcy discharge, or have become legally unenforceable because the Collection Statute Expiration Date (CSED) has expired, the Service must release any liens securing these periods within 30 days.

  4. If exempt, excluded, or abandoned assets are identified, Insolvency managers should ensure prompt action is taken to determine if such assets are worth pursuing, including appropriate investigation and valuation of the assets. (See IRM 5.9.17.5.3, Addressing Lien Issues, for specific time frames.) Once a determination is made not to pursue such assets, managers should ensure that caseworkers are initiating closing actions to adjust the dischargeable modules within 30 days of the determination, which will result in a systemic release of the lien. Generally, manually requesting a lien release is not required. However, if a certificate of release will not be systemically issued, the release should be requested manually on ALS. Quarterly checking of the Lien Research report will identify NFTLs that have not been released so corrective actions can be taken. See Exhibit 1.4.51-25, Guide for Lien Research Report (Field Insolvency and CIO).

  5. Chapter 7 and Chapter 13 cases discharged by the court will be run through ADS by the CIO twice a week. ADS processing allows all discharged cases in these chapters to be reviewed by the same standards. Some circumstances may warrant a case's remaining open even though the court has entered a discharge. IRM 5.9.5.4(6), Classifications and Summary Histories, explains procedures for these cases. A majority of cases are closed systemically as either non-dischargeable and a TC 521 is input, or dischargeable and a TC 971 is input followed by a TC 521 after a two-cycle delay. Discharge determination reports (DDRs) are generated for cases that cannot be fully processed without caseworker intervention. Insolvency caseworkers must begin resolving DDRs within 30 calendar days of the Service's receiving notification of discharge. (See IRM 5.9.17.4, Time Frames for Required Actions.) Those DDRs for accounts assigned to the CIO and involving complex issues should be forwarded to the appropriate Field Insolvency office for resolution. The review frequency for DDR resolutions on specific cases is set by the CIO Operation Manager. IRM 5.9.18, Automated Discharge System (ADS), outlines procedures for running ADS and resolving DDRs.

  6. A Field Insolvency caseworker evaluates the government's interest in exempt, excluded, or abandoned property if an NFTL:

    1. Was filed before the bankruptcy action began;

    2. Is valid; and

    3. Contains Unpaid Balance of Assessments (UBA) that exceed the established tolerance.

    Attempts to collect the value of the interest may be made through direct contact with the taxpayer or taxpayer's representative, or the case may be referred to Field Collection via an Other Investigation (OI).

    Reminder:

    Excluded property in the form of Employee Retirement Income Security Account (ERISA) style pension plans with anti-alienation clauses does not require the Service to have an NFTL on file before pursuing collection action. Field Insolvency caseworkers work these cases themselves usually eliminating the need to issue an OI. (See IRM 5.9.17.5.4, Insolvency Levy Procedures for Excluded Retirement Plans.)

Controls

  1. An important aspect of workload management and quality control for Insolvency managers is the establishment of group controls and reviews. Use the EQ managerial review process to conduct case reviews.

  2. Use AIS to monitor and maintain controls in these areas:

    • Pyramiding

    • Collection Statute Expiration Date (CSED)

    • Assessment Statute Expiration Date (ASED)

    • Large Dollar

    • No touch/activity for specific time period

    • Higher graded duties

    Take corrective actions when warranted. Any negative trends identified should be addressed on an employee by employee basis. Managers should also utilize the Tech Review Follow-Up report to monitor ongoing case activities.

  3. Insolvency must protect assessment statute expiration dates (ASEDs) and collection statute expiration dates (CSEDs). For information on ASEDs and CSEDs including the effect of BAPCPA on cases filed on or after October 17, 2005, see IRM 5.9.5.7, Serial Filers, IRM 5.9.4.3.1, BAPCPA and BRA 94’s Effect on Assessments, and Exhibit 5.9.6-6, TC 520 Input Guide for Trustee Turnover Requests.

    Note:

    Statutes, while usually suspended for the debtor during the pendency of a bankruptcy, are not suspended for the non-debtor spouse, with exceptions occurring in community property states. If action is warranted against a non-debtor spouse and time allows, consideration should be given to creating MFT 31 mirror modules so assessment or collection may proceed.

  4. Once established, these control reports can be utilized to identify cases needing regular review and follow-up by the manager. Reviews should address issues such as:

    1. Are timely and effective actions being taken to appropriately resolve the case?

    2. Is the accuracy of high priority cases (CSED, ASED) being verified?

    3. Are taxpayer rights being observed?

    4. Is the employee providing good customer service?

ASED Accounts

  1. A Trust Fund Recovery Penalty (TFRP) Assessment Statute Expiration Date (ASED) is generally three years from the date a return is filed or the due date of the return, whichever is later, for quarterly periods involving trust fund 941s, collected excise taxes, and annual 943s and 944s with trust fund tax. (See IRM 5.19.14.2.2, Trust Fund Recovery Penalty Statute of Limitations.)

  2. Generate the ASED Follow-Up report from AIS Business Objects at least quarterly to identify accounts where the ASED for the TFRP will expire within the next twelve months.

  3. Caseworker identification and history documentation of debtors with trust fund liabilities upon initial case review is essential because the ASED may be imminent. (See IRM 5.9.6.11.3, Initial Case Review of the 7A Business Case by FI, IRM 5.9.8.4, Initial Case Review for Chapter 11, and IRM 5.9.9.3.2(7), TFRP Actions for Debtors.)

  4. Where trust fund taxes are an issue and a TFRP investigation has not been initiated by Field Collection, Field Insolvency must identify and document potentially responsible officers for the IRC 6672, Failure to Collect and Pay Over Tax, or Attempt to Evade or Defeat Tax, penalty. (See IRM 5.9.5.4(2), History Documentation.)

  5. Managers must ensure information concerning in-business individuals and entities responsible for paying trust fund taxes are documented on AIS and tracked appropriately throughout the life of the bankruptcy.

  6. If an ASED is identified as having expired while a case is governed by the bankruptcy freeze, the procedures in IRM 5.7.3.8, Reporting Expiration of the TFRP Statute, should be followed by Insolvency caseworkers.

  7. The automatic stay indirectly prevents the IRS from assessing non-agreed proposed deficiencies on pre-petition periods because the time to file a Tax Court petition is tolled by the stay against the commencement or continuation of a Tax Court case. Examination staff monitor these unagreed proposals via a computer system called the Insolvency Noticing System (INS) generated by the Examination Returns Control System (ERCS). The Bankruptcy Exam Coordinator (BEC) in Technical Services, normally a revenue agent, coordinates with the Insolvency function to ensure the "Open Exam" field on the AIS Taxpayer screen indicates "Yes" when an examination is pending.

  8. Revenue agents and office examiners are instructed to contact the BEC when they identify TC 520s on audit transcripts or learn through the audit process a taxpayer is in bankruptcy. The information is passed on to Insolvency so the case can be added to AIS or updated and monitored until the proposed deficiency may be assessed.

    Note:

    Assessment is allowed if the debtor agrees with the proposed deficiency, the court closes the bankruptcy case thereby lifting the automatic stay, or the court establishes the liability.

  9. A process similar to that of field Examination governs Campus controlled cases. Campus exam cases are usually controlled by Campus correspondence units and the Automated Underreporter (AUR) units. Insolvency must coordinate actions with the lead of each SB/SE Campus group for correspondence cases and with the lead of each Campus AUR group.

  10. Campus Examination employees have access to AIS to monitor modules with open controls on IDRS. Campus employees contact Insolvency caseworkers with the status of underreporter proposed deficiencies if they have not received agreements to their statutory notices of deficiency. Cases pertaining to pre-petition periods receiving no response are classified as unagreed cases and are barred from assessment during the pendency of the bankruptcy if the bankruptcy petition was filed prior to the expiration of the time period for filing a petition in tax court.

  11. Some Campus Exam units have been provided with read-only access to AIS and have received sufficient training to allow them to determine the status of a case without contacting Insolvency. Other Campus Exam units without AIS access or skills may monitor the proposed assessments in suspense status and contact Insolvency periodically for an update of the bankruptcy status.

  12. Tax Equality and Fiscal Responsibility Act (TEFRA) generally applies to partnership examinations for partnership taxable years beginning prior to January 1, 2018. After a partner files a bankruptcy petition, the Service has at least one year to assess a TEFRA deficiency. While the bankruptcy rules provide the Service is to receive notice of all Chapter 11 cases, no specific requirement exists for the debtor to provide the government notice of the bankruptcy in all TEFRA cases. These cases require immediate Insolvency attention when they are identified. Insolvency should consult the Bankruptcy Exam Coordinator (BEC) for guidance.

  13. Insolvency caseworkers are charged with:

    1. Recognizing imminent ASEDs (See Exhibit 1.4.51-18, Guide for ASED Follow-Up Report (Field Insolvency));

    2. Initiating actions to ensure ASEDs are protected;

    3. Monitoring trust fund ASEDs as long as the taxpayer is complying with the terms of a Chapter 11 plan (See IRM 5.9.8.11, Trust Fund Considerations in Chapter 11);

    4. Coordinating with Field Collection if appropriate (See IRM 5.9.6.15, Trust Fund Recovery Penalty, and IRM 5.9.8.10, Trust Fund Considerations in Chapter 11); and

    5. Notifying the BEC when a bankruptcy case with a pending deficiency assessment closes allowing the BEC to proceed with the assessment before the ASED expires.

CSED Accounts

  1. Generate a report from AIS Business Objects at least semi-annually to identify accounts for which the Collection Statute Expiration Date (CSED) will expire within the next twelve months. (See Exhibit 1.4.51-26, Guide for CSED Follow-Up Report (Field Insolvency and CIO.) Review those cases to:

    1. Verify the accuracy of the CSED, and take corrective action if needed, including updating the CSED field on the AIS Taxpayer screen with the correct CSED, and/or taking actions as described in paragraph (2) below.

    2. Ensure that timely and effective action is taken.

  2. The CSED displayed may be invalid in certain cases. The CSED shown is always for the earliest assessment on the module. If that assessment is paid, the true CSED is for a later assessment (for example, an adjustment or deficiency assessment). If that is the case, request command code CSEDR to eliminate erroneous CSEDs from future monthly reports.

  3. CSED Extensions. Typically the time for which a bankruptcy stay is in effect plus six months is added to the collection statute after the stay of collection is terminated. IRM 5.9.4.3, ASED/CSED, provides more information on CSED computations.

  4. Imminent and Expired CSEDs. The procedures outlined in IRM sections 5.1.19.5 through 5.1.19.5.6 should be followed when addressing imminent (CSED will expire in 12 months or less) or expired CSEDs under the bankruptcy freeze, substituting the words "Insolvency caseworker(s)" for "revenue officer(s)" .

    • If the statute expires, see IRM 5.16.1.2.2.5, Report of Statute Expiration.

    • Should a CSED expire without prior approval, follow procedures in IRM 5.1.19.5.5, Collection Statutes That Expire Without Prior Approval. The memo should be prepared and routed as follows: a) Field Insolvency from group manager to Territory Manager, and, if warranted, to the Director. b) Centralized Insolvency Operation from unit manager to Department Manager, to Operation Manager, and, if warranted, to the Director.

Quality

  1. The IRS vision focuses on three high level goals: service to each taxpayer, service to all taxpayers, and productivity through a quality work environment. The IRS has developed a set of Balanced Measures in three major areas: Customer Satisfaction, Employee Satisfaction, and Business Results. Business Results is comprised of measures of quality and quantity. In reaching our goals we consider our impact on customer and employee satisfaction while we strive to improve quality and achieve quantifiable results. The Embedded Quality (EQ) process was developed to support Balanced Measures objectives.

    1. EQ is a tool designed to assist managers in identifying areas of strength and need in their employees’ individual performance. Employee performance is evaluated against attributes that are designed to identify actions that move cases toward closure through appropriate and timely case activity. The attributes link individual performance to organizational goals and are used by both managers and National Quality Reviewers to assess significant case actions.

    2. EQ enables the manager to measure the quality of both individual and group performance. It allows National Quality Review to assess the quality of the function to facilitate recommendations for improvement through policy changes, training, and updated procedural guidelines.

    3. The focus of EQ is on improving performance while the performance occurs. The attributes can be measured on open or closed cases. EQ is designed to identify gaps in quality case work at the earliest point in activity. It assists the manager in targeting corrective steps that positively impact performance.

    4. To conduct employee case reviews, managers use the Embedded Quality Review System (EQRS) to rate case actions against the attributes. EQRS also provides managers with tools to capture and share review feedback to show employees how they performed in relation to both the attributes and their CJEs. This should assist managers in providing employees with specific examples of how to sustain or enhance their performance.

  2. An important aspect of workload management and quality control for Insolvency managers is the establishment of group controls and reviews. Use the EQ managerial review process to conduct case reviews.

  3. Managers are responsible for the quality of all work assigned to their group and for all work which leaves their group regardless of the methods used. Managers must devise a system of quality control which works for them. Consider the following:

    1. Encourage employees to work with their manager to improve the quality of their work.

    2. Solicit suggestions from the group to address ways that can improve the quality of the work.

    3. Develop a plan to ensure a high level of quality in the group.

    4. Use Embedded Quality Review System (EQRS) and National Quality Review System (NQRS) reports available through EQ systems as diagnostic tools to focus attention on specific quality issues and identify training needs. The EQRS application used by front line managers and the NQRS application used by centralized reviewers mirror each other and feature numerous reporting capabilities that will facilitate comparison of results from both reviews at various levels of the organization.

      Example:

      If specific aspects of NQRS reports for a certain Area Office start to decline, area, territory / operation, and even group results for the same aspect measured under the managerial EQ review can be viewed to help isolate potential root causes.

  4. Ensure appropriate time is devoted to coaching and mentoring employees, as well as providing guidance that will assist in resolving their most difficult assignments.

  5. Reviews can help determine an employee’s needs for training and development. This will help decide how much time to devote to each employee.

  6. Choose from the following reviews and controls in designing a plan:

    1. Field visitations.

    2. Office observations.

    3. Spot reviews of open and closed cases.

    4. Formal inventory analysis.

    5. Time utilizations.

    6. Reviews of work submitted for approval.

    7. Initial contact reviews.

    8. TFRP cases pending determination or recommendation.

    9. Regular reviews of high priority cases (ie. pyramiding, CSED, ASED, large dollar, and in-business accounts).

NQRS

  1. National quality reviewers use a similar web-based system called the National Quality Review System (NQRS). A cornerstone of EQ is that quality reviewers and managers use the same basic set of attributes. This should minimize the concern that national reviewers are applying different criteria than managers when reviewing cases. However the national quality reviews will not be used to evaluate individual employee performance. NQRS attributes are not linked to employee CJEs; instead each attribute is mapped to one of five Quality Measurement Categories:

    1. Timeliness

    2. Professionalism

    3. Procedural Accuracy

    4. Regulatory Accuracy

    5. Customer Accuracy

EQ Consistency Reviews

  1. Consistency Reviews will be conducted to assist users in rating EQ attributes consistently by using the Attribute Job Aids, EQ website guidance, Critical Job Elements, and IRMs. Managers may participate in one or more EQ consistency reviews each year. The goal of consistency reviews is to improve the understanding and application of the EQ rating guidelines. Group managers and Territory managers within a territory will review the same case, compare attribute results, and discuss how rating guidelines can be applied to achieve consistency on attributes where significant rating inconsistencies occurred.

  2. Territory managers will schedule and conduct EQRS consistency reviews with group managers annually. The Area Director may add additional reviews when consistency among managers needs improvement. Consistency reviews require all managers within a territory to review the same case to compare attribute results and discuss how rating guidelines can be applied to achieve consistency. Refer to IRM 5.13.1.1.3, Roles and Responsibilities, and IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS), and Electronic Products and Services Support, for review procedures and guidelines.

  3. Document the review by preparing a written narrative to include the date the review was completed, observations, and actions taken to achieve consistent application of EQ attributes.

  4. Refer to IRM 5.13.1, Embedded Quality Collection Field Organizations Administrative Guidelines, and IRM 21.10.1 , Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS), and Electronic Products and Services Support, for information and guidance about EQ.

Employee Case Documentation

  1. It is extremely important that case documentation is timely, clear, accurate, and complete.

  2. Managers must direct subordinates to document all actions related to the IRS's involvement in a bankruptcy proceeding in the AIS History screen. Insolvency is the primary repository of bankruptcy-related case actions for all functions of the IRS. (See IRM 5.9.5.4, Automated Insolvency System (AIS) Documentation.)

  3. Incomplete documentation will negatively affect:

    1. Subsequent employee case actions.

    2. Ability to review and evaluate case activity.

    3. Actions by other employees.

    4. Quality Review System results.

    5. Cases presented in legal proceedings.

    Example:

    Ensure that employees clearly document the reason(s) why they have determined that the filing of a NFTL is not appropriate.

Territory / Operation Manager Operational Aid

  1. Guidance in this section is for Insolvency Territory / Operation Managers. An optional template to assist with planning operational reviews can be found in Exhibit 1.4.51-45, Operational Review Plan Guide.

Role of the Territory / Operation Manager

  1. Territory / Operation Managers have oversight responsibility for program delivery as well as administrative/compliance conformance.

    • Program Delivery focuses on group operations and ensuring appropriate guidance and direction is given to Group Managers to assist them in successfully delivering the program outlined in the Business Plan and Letters of Engagement.

    • Administrative/Compliance Conformance focuses on ensuring adherence to servicewide managerial requirements and law, regulation and policy. Such items may or may not seem directly related to program delivery. Examples include: Section 1204 certifications, hiring, travel authorizations/vouchers, remittance control reviews, etc.

Operational Review

  1. Operational reviews are used to monitor and document progress toward achieving organizational goals and objectives.

  2. Operational Reviews have two components: Program reviews and Administrative/Compliance Conformance reviews.

  3. While oversight responsibility is ongoing, Territory / Operation Managers must periodically conduct appropriate reviews and document findings with a memorandum.

  4. Conduct follow-up reviews when appropriate.

  5. These procedures apply to all Insolvency groups.

    • Program Review Purpose. The program review of individual groups is intended to evaluate the effectiveness of the manager, assess the group’s performance, and to provide guidance and direction intended to improve business results, foster effective casework, and managerial engagement. The program review will assess the group’s progress in areas such as performance efficiencies and quality. Use the review to identify trends, assess skills, training needs, and overall performance. GM communication and leadership of the group are addressed in this process. Program reviews should focus on assisting the group manager to improve performance and quality of case actions.

    • Administrative/Compliance Conformance Review Purpose: The purpose of the administrative and compliance review is to ensure conformance with service-wide managerial requirements and compliance with guidance related to law, regulation, and policy.

Frequency

  1. Program and/or administrative/compliance reviews may be conducted during the fiscal year as a single phase comprehensive review or may take the form of an on-going series of multi-phased reviews that focus on specific aspects of the group’s performance.

  2. Information from periodic GM briefings could also be incorporated in a multi-phased approach. Briefings are an optional method used to ensure periodic communication on group progress and other areas of interest.

  3. Feedback about program review findings is expected to occur continuously throughout the review cycle.

Documentation

  1. When using a comprehensive review option, one narrative will be prepared to document findings.

  2. When using the multi-phase approach, prepare a narrative to document each component at the time the review is completed.

    Example:

    Territory / Operation Managers may conduct reviews of specific program aspects, such as NFTL determinations, or providing group specific feedback.

  3. When using the multi-phase approach, Territory / Operation Managers may choose to review program aspects across the territory / operation and provide group specific feedback or review targeted aspects for a specific group.

  4. The narrative should be written with the GM as the intended audience. Attachments that provide additional detail may be used as appropriate.

  5. Share review documentation with the group manager within 60 days of completing the actual review.

Program Reviews

  1. When developing a group program review plan, consider the experience level of the GM and the Group’s overall current performance. Additionally, Territory / Operation Managers that are new to the existing groups should conduct a review that would ensure complete familiarity to the groups in the territory.

  2. Provide a framework for the group operational reviews at the beginning of each fiscal year based on the above criteria.

  3. Exhibit 1.4.51-45, Operational Review Plan Guide, may be used to develop the framework for the Operational review.

  4. Confer with the Director for concurrence on a plan that is tailored for each group’s unique circumstances.

  5. Plan the review based on analysis of territory / operation and group performance results and program trends. A variety of management information systems (MIS) reports should assist in determining areas of focus for the review.

  6. The review plan will be tailored to the needs of each group in order to assess progress on objectives and ensure employee skills are developed, customers serviced timely, and the group’s performance is enhanced in both quality and productivity.

  7. Critical items that should be addressed in each group program review include leadership, communication, case reviews, quality of case actions, and employee performance feedback.

Program Review Planning
  1. When planning the review, incorporate mandatory review items and consider including other group appropriate items.

  2. The list below reflects commonly selected review components. Items annotated "mandatory" must be addressed in the annual operational review.

    Reminder:

    Mandatory items could be added to oversight responsibility after this IRM is published. Incorporate these and any subsequent guidance issued into the reviews.

Commonly Selected Review Components
  1. Items annotated “mandatory” must be addressed in the annual operational review:

    • Case reviews. At a minimum, review 2 to 3 cases per employee in the group. The reviews should assess whether the case is moving toward a logical resolution, if the employee is using good workload management techniques, and whether there are any trends that may be adversely impacting group performance. The Territory / Operation review is a higher level review that considers if actions taken on the case are appropriate and are effectively moving the case toward a logical resolution. As part of the case review process, customer service considerations may be assessed by determining if taxpayer contacts were timely and whether the employee has been responsive to taxpayer requests. In addition, confirm that employee has appropriately observed valid POAs on file. When case reviews are conducted, it is mandatory to ensure that managers are addressing TP rights, particularly with respect to direct contact provisions. Territory / Operation Managers may also include “mirror” reviews of cases which the GM has already reviewed in order to assess the accuracy of the GM's EQ attribute review and if proper direction was given by the GM as part of the review. Territory / Operation Managers may use the EQ review reports to determine if the GM reviewed the appropriate number and mix of cases during both the mid and annual appraisal segments. This may also be accomplished at the mid-year approval if the Territory / Operation Manager has elected to approve the mid-year appraisal of each employee. (See IRM 1.4.51.5.2.2, Requirements for Annual Performance Case Reviews.) Additional considerations include annual field visit conducted, annual time utilization reviews conducted, follow-up review conducted, and whether the reviews were provided to employee timely.

    • NFTL determination accuracy (Mandatory). TMs must review an adequate sample of cases to determine if the GM and TM approval of NFTL determinations was secured when necessary and if the NFTL determination decisions were appropriate. See IRM 5.12.2, Notice of Lien Determinations, for mandatory NFTL determination guidelines.

    • Quality. Group quality should be analyzed using available EQ/NQ reports. These resources can be used to identify trends that may need further attention.

    • Entity/MIS reports analysis. On an ongoing basis, conduct analysis of Entity and MIS reports in areas such as currency of inventory, NFTL filing determinations, activity lapses, pyramiding, large dollar, multiple modules, and other performance indicators. Identify possible case trends and provide guidance designed to achieve area/territory targets/objectives. Observation and results of the analysis may be addressed during periodic briefings with the group manager and then summarized in the program review narrative.

      Note:

      A written narrative should be prepared and shared with the GM more frequently if any issues or concerns exist.

      See https://portal.ds.irsnet.gov/sites/vl073/Pages/default.aspx.

    • EPF review. Determine if the OPM guidelines for document retention and items included in EPF have been followed. Evaluate whether performance documentation supports the evaluation rating. Verify that the appropriate reviews have been conducted at the appropriate time.

    • Communication. Look for indicators that GMs are effectively communicating procedure and policy changes affecting overall quality of work. Assess the quality of GMs guidance concerning effective case resolution. Review group meeting minutes to determine if area and territory / operation information is shared as appropriate. Territory / Operation Managers may also wish to conduct focus group or individual discussions to evaluate whether key information and message are delivered in a timely appropriate fashion.

    • Employee satisfaction. These issues can be assessed by ensuring Survey or workgroup questionnaire issues are addressed and discussed on an ongoing basis. Ascertain if appropriate EEO and diversity practices are discussed, such as: Reasonable Accommodation, hardships, EEO, etc. Discussion of training, employee development, Career Learning Plan (CLP), timely feedback to employee, timely evaluations, targeted inventory levels, and inventory mix should be considered. Many of these areas are addressed during periodic briefings and can be confirmed through GM completion of online mandatory briefings.

    • Customer satisfaction. Look for indicators that customers are receiving timely actions, and are receiving fair and equitable treatment from the employee to assist in bringing their case to an appropriate resolution.

    • Group Time Reporting and Analysis. On a monthly basis review time reports to evaluate a group’s use of Direct Time, Field Time, Administrative Time, etc. These items may be addressed during periodic briefings as well.

      Note:

      Field Insolvency employees report their specific program time in the Integrated Collection System (ICS) and use the Single Entry Time Reporting (SETR) system to report their time and attendance. CIO employees report all their time in SETR, ensuring specific program times are separately out by the Organization Function Program (OFP).

    • Group Productivity and Efficiency. Conduct an analysis of the group’s efficiency in case resolution using productivity and cycle time reports provided by Area analysts. Productivity measures are a result of case work efficiencies, including simultaneous case actions, closing cases in a timely manner, and working cases with resolution in mind.

    • Annual Appraisal/Performance Document Approval. Territory / Operation Managers are responsible for ensuring timely feedback and appropriate ratings of employees. This should be an ongoing process during the year through approval of the annual rating. Ensure consistency between the Form 6850-BU critical job element rating/narrative and the performance documentation contained in the EPF. Review for potential Section 1204 violations / ROTERs during this process. Ensure that the GM has a review schedule that includes all required reviews such as mid-year, field visits, etc. A mutually agreeable review schedule should be established the beginning of each fiscal year. Ensure that GMs conduct mid-year reviews between the 5th and 7th month of the rating cycle. Annual reviews/ratings should be completed at least 60 days prior to the end of the rating period so that employees have enough time to demonstrate improvement if necessary. Discuss GM compliance with review schedules during periodic briefings and document compliance in the program review annual narrative.

Suggested Optional Components
  1. Suggested optional components that can be included in the Program review are shown below (this list is not all inclusive). These can be completed during the actual review or anytime throughout the year and included in the annual narrative:

    • Fraud program/identification and Fraud Technical Advisor (FTA) involvement

    • Inventory ranges and assignment practices/inventory delivery process

    • Above grade work

    • Span of control

    • Attend a least one group meeting per year with each group

    • Field visitations to determine the effectiveness of the GM in ensuring TP rights and timely and appropriate actions taken by the employee

Administrative / Compliance Reviews

  1. Administrative / Compliance Reviews are used to monitor and document oversight of operational items not included in program reviews. Territory / Operation Managers are required to provide oversight for Administrative / Compliance review areas. These reviews may be conducted at anytime during the fiscal year.

  2. Document results of mandatory Administrative / Compliance review items in a clearly identified subsection of the annual comprehensive program review or prepare a separate narrative review (at least annually) to summarize results.

  3. Documentation is required for those items noted as mandatory as well as items for which findings indicate non-compliance and/or a need for improvement.

Common Components
  1. Items to be reviewed during the fiscal year include, but are not limited to:

    1. EPF/Drop file reviews. Some components of the EPF maintenance are addressed under program reviews. However, for the administrative and compliance review, assess compliance with established guidance:• IRM 1.5.3.3, Retention Standard for the Fair and Equitable Treatment of Taxpayers• IRM 1.5.3.4.3, Manager's Quarterly Self-Certification Review Components• IRM 6.735.1.7, Outside Employment and Business Activity• IRM 1.15.1, The Records and Information Management Program• IRM 6.430.2.3.5, Employee Performance File (EPF)• Telework agreements • AWS request forms

    2. Controls. Determine if appropriate and sufficient controls are in place for items such as:• Statutes, IRM 5.1.19.5, Imminent CSEDs• Trust fund, IRM 5.19.8, Collection Appeal Rights• CDP, IRM 5.7.10.2, Case Processing

    3. Timekeeping / SETR. Review the GM control timekeeping process to ensure that established timekeeping guidance is being followed IRM 6.630.1, IRS Absence and Leave.

    4. Security. Responsibilities include, but are not limited to:• Verification of GM after hours security checks and subsequent remedies. (See IRM 1.4.6.7.2, After Hours Review.)• Verification that GM has reviewed BEARS accesses and need for access to all computer systems for their employees. (See IRM 10.8.1.3.1.1, AC-2 Account Management.)• Ensuring that taxpayer returns and other SBU data is protected. (See IRM 10.5.1.4.1, Employees/Personnel.)

    5. Correspondence / File Retention. Identify the GMs correspondence and file retention procedures to ensure they comply with Document 12990, Records and Information Management Record Control Schedules.

    6. Travel Vouchers / Authorizations. Ensure that the GM is approving authorizations and vouchers timely and monitoring for correct coding, receipts, and expenses that are appropriate. (See IRM 1.32.1, IRS Local Travel Guide.)

    7. Credit Bureau. Ensure the GM is approving credit bureau requests as required and has a system in place to monitor for proper documentation. (See IRM 5.1.18.19.2, Limitations on Ordering Consumer Credit Reports.)

    8. Purchase Cards / Supplies Orders. Review the groups purchase card procedures to verify they are in compliance with established guidance. (See IRM 1.35.3.3.2, Receipt Documentation.)

    9. Section 1204 / ROTERs. On an ongoing basis, screen case and performance documentation for inappropriate use of ROTERs. Quarterly, complete the Section 1204 self certification and certify the group manager’s completion of their self certification. (See IRM 1.5.3.3.4, Retention Standard Documentation.)

    10. EQ Consistency Reviews. Conduct an EQ consistency review at least annually to promote consistent application of EQ Attributes. Document the consistency review per IRM 5.13.1, Embedded Quality Collection Field Organizations Administrative Guidelines.

Director Operational Aid

  1. Guidance in this section is for the Director. See Exhibit 1.4.51-46, Director Operational Aid (DOA).

Suggested Action Steps for Unacceptable Performance

If... And... Then...
During a workload review it is noted a performance deficiency or deficiencies based on employee's Critical Job Elements (CJE) (e.g. Protection of Public Interest, issue: filing of notice of lien and/or extension of NFTL determination) N/A The manager should…
• Take informal steps to correct performance deficiencies such as: 1. While reviewing employee documentation, the manager should see if he or she can determine other factors that may have caused the identified deficiencies.
• Counsel employee as to what is considered appropriate action on cases reviewed. Indicate which CJE or CJE's are identified as not being met at this time.
• Schedule additional dates to review employee casework.
• Require employee to obtain managerial approval to extend NFTL determination date (if applicable).
• Continue to use AIS to identify lien indicator cases and perform a query of the cases on AIS. Indicators to check are:
1. When case received
2. When case assigned to an employee
3. When NFTL filed
• All discussion(s) with employee must be fully documented and a copy of the documentation is provided to employee with a copy placed their EPF.
• Continue to closely observe/monitor employee performance using managerial tools.
The manager continues to closely observe, monitor, review and correct (if necessary) the performance deficiency or deficiencies the employee's performance improves • No additional action needed
The manager continues to closely observe, monitor, review, and correct the performance deficiency or deficiencies the employee's performance does not improve • Begin formal counseling.
• Consult with Labor Relations regarding the issuance of an opportunity letter to establish a formal period to show improvement to acceptable level of performance. The opportunity letter must include:
1. Critical elements/performance standards that are not acceptable.
2. Exact nature of deficiencies.
3. Improvement expected.
4. Fact that failure to improve could result in proposal to remove employee from current grade or the Service.
5. A specific period of time to demonstrate acceptable level of performance (usually 90 days).
6. A stated commitment to work with employee.
7. If on Telework, suspension of Telework until performance improves.
• With the continued assistance of Labor Relations, follow procedures outlined in Article 40, Unacceptable Performance, of the National Agreement - IRS/NTEU for BU employees.
• Plan a review schedule. At this planning session discuss:
1. Number of reviews planned;
2. Types of reviews;
3. Types of cases to be reviewed;
4. Number of cases at each review;
5. Time frames for review schedule (one a week, twice a month etc.)
6. In summary, tailor the planned reviews to the needs of both the manager and the employee.
• May continue to use AIS to identify lien indicator cases and perform a query review of the cases on AIS. Indicators to continue to check are:
1. When case received.
2. When case assigned to an employee.
3. When NFTL is filed.
• Review, approve or disapprove (with comments) NFTL extension determination(s) made by employee (if applicable).
• Document all reviews, provide copy of documentation to employee and place in their EPF.
The manager continues to closely observe, monitor, and review employee performance based on the provisions of the opportunity letter. the employee's performance becomes minimally successful or fully successful • Consult with Labor Relations personnel and issue a letter informing employee of this fact.
• If employee's Telework was suspended during this period, consider resuming the schedule.
The manager continues to closely observe, monitor, and review employee performance based on provisions of the opportunity letter. the employee's performance does not improve • Consult with Labor Relations regarding the issuance a 30 day advance notice of reduction in grade or removal.
• Make sure all documentation is in order and copies provided to employee with copies filed in their EPF.
• Follow procedures outlined in Article 40 of the National Agreement - IRS/NTEU for BU employees with the continued assistance of Labor Relations.
• Provide a written decision to the employee within 30 days after the date the advance notice period expires. — If no written decision is made within this 30 day period, then the advance notice period may be extended for one additional 30 day period only.
• Provide a written decision to employee within extended 30 day advance notice period.
• Initiate action to reduce in grade and/or removal based on unacceptable performance once the written decision is issued.
However, when a 30 day advance notice is being considered reassignment, voluntary reduction in grade, retirement, or disability retirement is also being considered in lieu of notice • Consult with Labor Relations personnel.
• Exercise options under consideration. – All but disability retirement option may preclude or delay processing of an action to reduce in grade or remove employee. – An application for disability retirement will not preclude or delay processing of an action to reduce in grade or remove the employee.
If written decision is issued to reduce in grade and/or removal based on unacceptable performance the personnel action is effected • The employee has appeal rights to Merit Systems Protection Board.
• BU employee may alternatively choose to appeal through the negotiated grievance procedure.

Pattern Letter for Incomplete Claim for Damages and/or Attorney's Fees

Below is suggested text for a letter to a claimant asking for payment of damages from the Service because the Service has violated the automatic stay or the discharge injunction. This letter is to be used when the claimant fails to provide complete information with his claim application. Local Counsel may suggest changes in wording or content.

Begin the letter with: Dear, name of claimant
Paragraph 1 We have received your claim dated [enter date of claim] for damages and/or attorney's fees under Internal Revenue Code 7433(e), civil damages for alleged violation(s) of the Bankruptcy Code. However, we are unable to process your claim because:
Paragraph 2 [Enter the reason(s) why the claim cannot be processed at this time. Describe any missing or incomplete information and/or additional information the claimant must provide to justify the claim. Be specific.]
Paragraph 3 We are not rejecting your claim at this time. But we do require the information requested above to process it. If we receive the information, we will evaluate your claim and send our decision on this matter to you within 60 days.
End of letter Sincerely, add your name and title

Pattern Letter for Approval of a Claim for Damages and/or Attorney's Fees

Below is suggested text for a letter to a claimant asking for payment of damages from the Service because the Service has violated the automatic stay or the discharge injunction. This letter is to be used when the Service agrees to pay all or a portion of the claimant's application. Local Counsel may suggest changes in wording or content.

Begin the letter with Dear, name of claimant
Paragraph 1 This letter is to advise you of our decision concerning the claim you filed. See the explanation below following the checked box.
Paragraph 2 We have approved your claim in full for damages and/or attorney's fees under Internal Revenue Code 7433(e), civil damages for violation(s) of the Bankruptcy Code.
Paragraph 3 We have approved a portion, $ [enter portion amount], of your claim for damages and/or attorney's fees under Internal Revenue Code 7433(e) civil damages for willful violation(s) of the Bankruptcy Code. However, we are denying the remaining portion of your claim for the following reason(s):
Paragraph 4. Describe the reason (s) for which the claim was partially allowed. Insert the specific reason(s)
Paragraph 5 Please sign and date the enclosed voucher and return it to us in the enclosed envelope. We will send you a signed copy for your records. Your check will be sent to you within six to eight weeks after we receive your signed voucher.
Paragraph 6 Please sign and date the enclosed voucher and return it to us in the enclosed envelope. We will send you a signed copy for your records. Your check will be sent to you within six to eight weeks after we receive your signed voucher.
Paragraph 7 You are not entitled to make an administrative appeal of this decision. However, if you wish to take further action, you may file a civil action in the bankruptcy court for damages under Internal Revenue Code 7433(e) for the difference not agreed upon. The law allows you two years from the date of a violation to take your case to court.
End of letter Signature and title of Delegated Authority

Pattern Letter for Denial of a Claim for Damages and/or Attorney's Fees

Below is suggested text for a letter to a claimant applying for payment of damages because the Service has violated the automatic stay or the discharge injunction. This letter is to be used when the Service denies payment of all portions of the claimant's application. Local Counsel may suggest changes in wording or content.

Begin letter with Dear, Name of Claimant
Paragraph 1 We have received your claim dated [enter date of claim] for damages and/or attorney's fees under Internal Revenue Code 7433(e), civil damages for alleged violation(s) of the Bankruptcy Code.
Paragraph 2 We are denying your claim for the following reason(s). Enter the reason(s) why the claim has been denied. Be Specific
Paragraph 3 You are not entitled to make an administrative appeal of this decision. However, if you wish to take further action, you may file a civil action in the bankruptcy court for damages under Internal Revenue Code 7433(e). The law allows you two years from the date of a violation to take your case to court.
Paragraph 4 If you have any questions, please contact: insert the name and telephone number of the contact person
End of letter Signature and title of Delegated Authority

Sample Annual/Mid-year Review Schedule

Group Review Schedule

Month SSN Form 6850-BU Employee Due Mid-year
September 0 AA, BB Oct 31 EE, FF
October 1 N/A Jan 31 GG, HH, II
November 2 CC Jan 31 N/A
December 3 DD Jan 31 JJ, KK
January 4 N/A Apr 30 LL, MM
February 5 EE, FF Apr 30 N/A
March 6 GG, HH, II Apr 30 N/A
April 7 N/A Jul 31 AA, BB
May 8 JJ, KK Jul 31 N/A
June 9 LL, MM Jul 31 CC
July N/A N/A N/A DD
August N/A N/A N/A N/A
 

Note:

The letters in this chart, for example AA, BB, represent individual employees.

Insolvency Group Manager's EQRS Review Documents, Form 6850-BU, and Narrative, General Guide

EQRS, Form 6850-BU, Bargaining Unit Performance Appraisal and Recognition Request, and narratives are important in all actions regarding caseworker performance. The review documents should justify the numerical ratings and average indicated on the Form 6850-BU.

These documents will assist the manager in substantiating a decision to take any action regarding the performance of a caseworker. These actions can include awards, reduction of a rating of record, or removal from Telework. These documents should be clear and concise. They should provide the caseworker with a clear understanding of their level of performance.

EQRS review documents, narratives and other evaluative documents should provide positive feedback and specific strategies for improvement as applicable. The narrative should be specifically written to enhance performance, identify weaknesses, and explain potential consequences when warranted.

Ensure that the reviews are written and encompass a wide spectrum of cases from the caseworker's inventory.

When performing case reviews utilizing the Embedded Quality Review System:

  1. Review any hard copy case file(s). This is to ensure documents that will expedite case resolution are included, (e.g., financial statements, bank records, etc.) and that an appropriate evaluation of case direction has been made.

  2. Ensure clear comments are included for each case reviewed. If the employee is performing well, document it in the comments.

  3. If case direction is needed, ensure directions are specific. If warranted, reference specific documents reviewed in the case file.

When preparing the review documentation the manager should:

  1. Ensure the employee's actions were appropriately documented on each case.

  2. Base comments on actions pertaining to the applicable CJE and sub-element.

  3. Ensure conformity with the employees’ CJE’s by utilizing the employee’s Performance Plan.

  4. When appropriate, reference relevant IRM sections, subsections, and case file documents.

  5. Document strategies for improvement.

  6. Be realistic in expectations.

  7. Prepare a narrative of the overall findings.

Meet with the employee and engage in an open dialogue. Be sure to discuss the positive as well as the negative aspects of the employee’s performance. Discuss the comments on the EQRS Feedback Report given on each case and ensure the employee understands.

  1. Ask for their input regarding the interpretation of their actions.

  2. If warranted, discuss the documents included in the case file, and address any that are missing.

  3. If appropriate, add their proposed actions to the comments as additional action items.

  4. Ensure that time lines are realistic.

  5. Ensure that case direction is clear.

Discuss the EQRS Feedback Report narrative with the employee to ensure they understand the document and its possible impact on their annual appraisal/evaluation (positive or negative).

Managers should have the employee sign for receipt of both the Individual Feedback Report and any accompanying documents. Document and date the Individual Feedback Report and narrative if the employee refuses to sign.

Annual Appraisal Document Form 6850-BU:

Form 6850-BU is the numerical representation of the employee's performance during the course of the evaluation period. It must be consistent with the employee's casework and evaluative documents prepared during the course of the evaluative period. Managers should ensure that the preparation of Form 6850-BU is in accordance with Article 12, Performance Appraisal System, of the National Agreement - IRS/NTEU. Base the appraisal of the employee on documented materials:

  1. Evaluative documents retained in the caseworker's EPF, such as EQRS Individual Feedback and/or Cumulative Feedback Reports. Also IRM 1.4.51.5, Performance Management, and IRM 1.4.51.5.2, Reviews (Overview), for other considerations.

  2. Taxpayer correspondence.

  3. Internal customer correspondence.

  4. All awards received during the period.

Performance and Evaluative Narratives:

Narratives are an effective tool in documenting and informing a employee of their performance. They should be used to emphasize the positive as well as the negative aspects of the employee's performance. They can be used as either stand alone documentation (EQRS Individual and/or Cumulative Feedback Reports) and/or with the Form 6850-BU (when appropriate). See Article 12, Section 4.N, of the National Agreement - IRS/NTEU, regarding Form 6850-BU narratives. Effective narratives:

  1. Are clear and concise.

  2. Address each Critical Element and its accompanying sub-element (for Form 6850-BU).

  3. Reference prior reviews and other evaluative documents completed during the course of the evaluation period and the dates completed or received.

  4. Are of sufficient length for the employee to have a clear understanding of their current level of performance and what is expected from them in the future.

  5. Summarize the findings during the course of a review or the overall performance during an evaluative period. may choose to use specific examples or sanitized case references.

  6. Refer to specific Critical Job Elements and sub-elements.

  7. Describe strengths and weaknesses found within specific element(s).

  8. Describe strategies for improvement (if necessary).

  9. Identify the level of performance (overall and within a specific CJE).

  10. Describe potential consequences if performance is at an unacceptable level or regressing.

  11. Note that the manager is available for assistance.

In conjunction with the steps to address employee performance ensure that:

  • Prescribed actions are specifically documented and appropriately worded. Consult with the Territory / Operation Manager or Labor Relations Specialist as appropriate.

  • Documentation includes a description of any problems and documentation of the discussion with the employee involved. Inform the employee of possible consequences if the issue is not resolved. Managers may inform the employee verbally, but confirm the discussion via memorandum. The proposed resolution of the issue should include a specific time period for completion. The resolution may include actions the employee must take and meetings between managers and the employee to resolve the problem.

    Note:

    The employee is entitled to request representation by the Union when the employee and the supervisor or other management official meet to discuss action or potential action, based on unacceptable performance.

Note:

When taking any performance action, managers should contact their servicing Labor Relations Representative and their direct supervisor.

Action Steps for Acceptable Level of Competence Determination if an Employee Within Grade Increase (WGI) is due.

Within and the employee's last rating is... and the employee's performance is projected as... Managers must.....
90 days Fully successful or above Fully successful or above Do nothing. WGI will be automatically generated.
90 days Fully successful or above Below Fully successful 1. Refer to WGI denial procedures in Article 17, Acceptance Level of Competence Determinations, for BU employees.
2. Consult with Labor Relations personnel and issue letter of intent to deny WGI 60 days prior to WGI due date.
3. If a fully successful rating is achieved after issuing intent letter, consult with LR regarding written notification to employee that WGI will become effective on original due date.
4. If a fully successful rating is not achieved after 60 days following issuance of intent letter:
• Consult with LR regarding written notification to employee denying WGI.
• Prepare Form 6850-BU as normally would happen at the end of the rating period except: – indicate period covered from last annual rating to date WGI was due and – annotate that “WGI Denied” – submit signed form to the Transactional Processing Branch (TPB) at least 15 days prior to WGI due date to ensure that the WGI is not processed.
59 days or less Fully successful or above Below Fully Successful 1. Refer to WGI denial procedures in Article 17 for BU employees.
2. Consult with LR and issue letter of intent to deny WGI. Letter will provide for required 60 day notice period.
3. As soon as possible, prepare Form 6850-BU. Complete appropriate blocks and annotate “Postpone WGI”.
4. Submit signed form to the TPB at least 15 days prior to WGI due date to ensure the WGI does not process.
5. If a fully successful rating is achieved at the end of 60 day notice period:
• Consult with LR regarding written notification to employee that WGI will become effective retroactive to original due date.
• Prepare Form 6850-BU. Complete appropriate blocks and annotate “Release WGI.” Submit signed form to the TPB within 3 days of advising employee.
6. If a fully successful rating is not achieved at the end of the 60 day notice period:
• Consult with LR regarding written notification to employee that WGI is being denied.
• Prepare Form 6850-BU as if annual rating except: – indicate period covered from last annual rating to date of WGI due – annotate “WGI Denied” – submit completed form to the TPB within 3 days after denial letter is issued to employee; and – immediately have SF-52 the TPB within 3 days after denial letter is issued to employee; and – immediately have SF-52 prepared for denial of WGI.
59 days or less Below Fully successful and the WGI was previously denied Fully Successful or above 1. Prepare Form 6850-BU as if annual rating except:
• Indicate period covered from date WGI was last due to the date of this form being prepared, and • Annotate “WGI Released”.
2. Advise employee that the WGI will become effective the following pay period.
3. Submit completed form to the TPB within 3 days of completing form.
59 days or less Below Fully Successful and WGI was not previously denied Fully Successful or above No action necessary

Guide for APOC Reports (Field Insolvency)

Purpose of Reports. There are numerous APOC reports available on AIS Business Objects. IRM 5.9.14.2.5(3), APOC Reports, provides a list of the APOC reports. This exhibit will only cover the reports designated as "mandatory" .

  • Period Detail Flag - Credits Posted After the Petition Date report identifies cases where there is a credit that may have been received after the petition date in violation of the stay. These cases should be worked within five calendar days of APOC identifying the flagged condition.

  • Period Detail Flag - Lien Recorded Date Blank or > Petition Date report identifies cases where the date of the notice of lien is not recorded on AIS, or the date recorded is greater than the petition date. These cases should be worked within five calendar days of APOC identifying the flagged condition.

  • Period Detail Flag - Secured Period report identifies cases where the Service may have a pre-petition NFTL on file and may be entitled to an adequate protection or cash collateral agreement. These cases should be worked within ten calendar days of APOC identifying the flagged condition.

  • Flagged Cases report lists all cases that have encountered a flag which has not yet been resolved. These cases require manual intervention by the user.

    Reminder:

    Cases that have the Period Detail Flag - Credits Posted After the Petition Date, the Period Detail Flag - Lien Recorded Date Blank or > Petition Date, and the Period Detail Flag - Secured Period will also be included on this report.

Accessing the Reports. Use AIS Business Objects to access, run, and print the APOC reports.

Frequency of Use by Caseworker. Caseworkers must ensure the time frames required for processing each of the flags is met, therefore they should work the reports at least weekly.

Note:

Since cases that have the Period Detail Flag - Credits Posted After the Petition Date report, the Period Detail Flag - Lien Recorded Date Blank or > Petition Date report, and the Period Detail Flag - Secured Period report will also be included on this Flagged Cases report, the caseworker may choose to only work from this one report.

Frequency of Use by Manager. Managers should review the Period Detail Flag - Credits Posted After the Petition Date report, and the Period Detail Flag - Lien Recorded Date Blank or > Petition Date report, weekly. They should review the Period Detail Flag - Secured Period report bi-weekly and the Flagged Cases report, monthly.

Range of Uses. All chapters where claims may be processed by APOC are subject to this report.

Guide for Bar Date Follow-Up Report (Field Insolvency)

Introduction. Use of the Bar Date Follow-Up Report is "Mandatory" . This AIS Business Objects report identifies cases where a POC is presumed to be required, yet no POC has been printed. A case is included on the report when a "Yes" appears in the "Proof Required" field on the AIS Taxpayer screen and claim data has not been entered on the Proofs of Claim screen(s).

Accessing the Report. Use AIS Business Objects to access, run, and print the Bar Date Follow-Up report.

  1. Populate Parameter field(s) for specific report selected based on output desired.

  2. Enter beginning date. An old date, like 01/01/1950, should be input to capture cases previously overlooked or cases entered with an erroneous date.

  3. Enter ending date. Generally use 90 days into future.

Frequency of Use by Caseworker. This list must be generated and checked by caseworkers at least "Bi-weekly" to encourage timely preparation and filing of proofs of claim.

Frequency of Use by Manager. The Bar Date Report is reviewed by managers "Monthly" to identify inventory management concerns, systemic noticing problems, or other issues.

Retention. The retention period for this report is one month.

Range of Uses. The report provides data on all chapters where it may be appropriate for the Service to file a claim.

Presumptive Bar Dates. Cases are listed in ascending chronological order by a "presumptive" bar date. A proof of claim (POC) must be filed before 180 days (the government bar date) from after the date of the order of relief (which is the date the bankruptcy petition was filed in voluntary cases). (See 11 USC 502, Allowance of claims or interests, and Bankruptcy Rule 3002, Filing Proof of Claim or Interest.)

Managerial Review. When reviewing this report, the petition date and bar date time period should be checked to note if the time period is consistent with locally established practice.

Note:

Managers may set procedures that prohibit changing the presumptive bar date unless the court changes the actual bar date.

If a missed bar date is identified during the manager’s review, the manager may need to complete Form 14167, Bar Date Expiration Report. See IRM 1.4.51.11.1 (3), Missed Bar Dates, for specific procedures.

Monitoring. Cases falling beyond the 70 day period should be highlighted or otherwise annotated for review on a biweekly basis. When awaiting receipt of unfiled tax returns, filing a claim with estimates within 70 days is more efficient than postponing the filing thereby risking a claim's being barred. Awaiting the receipt of unfiled returns is usually the reason for delays in the claim filing process.

Deleting a Case from the Bar Date Report. A case is removed from the Bar Date Report by:

  • Preparing/printing POC;

  • Entering conversion to 7 No Asset data to AIS Taxpayer screen;

  • Entering "NL NO LIABILITY" in the Closure Method field with a date when a case is determined to be not liable;

  • Closing a case on AIS as dismissed; or

  • Manually changing "Proof Required" field from "Yes" to "No" .

AIS Documentation. Managers should be conservative in requiring documentation from caseworkers on an ongoing basis. Highlighting a case with a bar date beyond 70 days is effective. Groups may agree on one letter codes to identify cases in a certain category, e.g. "L" for -L freeze present awaiting call back from exam or the underreporter unit, "E" for complex estimated claim being calculated, or "I" for restricted interest calculation.

Administrative Claims. The report does not list administrative claims. For example, in conversions, the reviewer may note the Proof Required field shows "Yes" indicating a claim is required, yet an admin claim (Form 6338-A, Request for Payment of Internal Revenue Taxes) has been filed. The caseworker should change the "Yes" to "No" if no taxes are due at the time the debtor filed bankruptcy. Leaving the "Yes" reduces efficiency if a caseworker continues to check on a case where the determination has already been made.

Guide for Proofs of Claim Follow-Up Report (Field Insolvency)

Purpose of Report. The Proof of Claim Follow-Up report lists all cases with proofs of claim that were sent to the court, but have not yet received an acknowledgement of the filing by the court. It is important to ensure that all cases where a claim is required are filed and acknowledged by the court prior to the bar date. Generally, it takes only a day or two for the court to acknowledge filing, so the date used can be one from a few days prior to the current date.

Accessing the Report. Use AIS Business Objects to access, run, and print the Proof of Claim Follow-Up report.

Frequency of Use by Caseworker. Caseworkers must work the Proofs of Claim Follow-Up report at least bi-weekly to ensure proper claim filing.

Frequency of Use by Manager. Managers should review the report monthly to identify trends or as part of employee reviews.

Range of Uses. Although AIS does not limit the query criteria, chapters where claims are filed are the most useful for this report.

Guide for Litigation Transcript System (LTS) Reports (Field Insolvency and CIO)

Purpose of Reports. The Litigation Transcript System (LTS) matches master file data with TIN records of the AIS database. The transcripts provide new assessment data, potential manual refunds, unreversed TC 520s, delinquent federal tax deposits, and issues that may result in violations of the Bankruptcy Code automatic stay provisions.

Frequency of Use by Caseworker. Field Insolvency will work these weekly reports for cases in its inventory within five work days of receipt. The CIO will work required LTS reports for cases in its inventory. The reports must be worked in accordance with the instructions and time frames established in IRM 5.9.16.2, Litigation Transcript System.

Frequency of Use by Manager. Managers should review the reports at least monthly to ensure potential stay violations are being addressed and resolved on a timely basis.

Range of Uses. The scope of the LTS reports touches all chapters.

Retention. The retention period for this report is one cycle.

Referrals. Appropriate receiving offices should be notified of events identified through LTS reports affecting previously issued referrals.

Example:

Counsel should be advised of receipt of delinquent returns if a referral was made requesting a motion to compel filing.

AIS History. Caseworkers should document the AIS history in accordance with IRM 5.9.5.4(2), History Documentation, noting all actions taken to resolve the LTS issue.

Transaction Codes Identified. Examples of the types of transaction codes the LTS process identifies are:

  • Posting of TC 277

  • Posting of TC 430 and no TC 150 posted

  • Posting of TC 520 with xx code

  • Posting of TC 280 bad check penalty

  • Posting of TC 670 cc05/99

  • Posting of TC 820/700 (if that is the only issue)

  • Posting of TC 846

  • Posting of TC 971 ac031/033

  • Posting of a TC 582 Notice of Federal Tax Lien

  • Post-petition refunds and credits

  • Zero balance due/even returns (wholly post-petition)

Transcript Categories. LTS transcripts fall into one of six categories:

  • After Petition

  • Credit Balance

  • Other Credit Balance

  • Case Closed on AIS

  • New Assessments

  • All Other (optional for CIO)

Guide for Case Grade Report - Manager only (Field Insolvency)

Purpose of Report. This report gives a synopsis of individual employee inventories and the percentage of work that is graded 07, 09, 11, and 12 as well as the percentage of ungraded work.

Accessing the Report. Use AIS Business Objects to access, run, and print the Case Grade report.

Range of Uses. This report is for all chapters.

Note:

The Case Grade Report compiles inventory profile information to ensure employees have appropriately graded work.

Percentages of Above Grade Work. Employees with work that is 10% above their grade level should have their inventory monitored weekly to avoid the risk of being assigned additional higher graded work. Employees should not spend more than 25% of their time each month on work above their grade level.

Ungraded Cases. If an employee has a percentage of ungraded cases, managers should also run the Ungraded Case Follow Up report in order to identify the specific cases requiring a grade. See Exhibit 1.4.51-29, Guide for Case Assignment Reports (Field Insolvency and CIO).

Guide for Court Closure Follow-Up Report (Field Insolvency and CIO)

Introduction. The Court Closure Follow-Up report is mandatory for use by both Field and Centralized Insolvency. This report provides a list of open AIS cases where the court has notified the IRS of closure. It identifies cases where closing actions should be initiated immediately. The AIS generated report denotes discharges as (DC) and dismissals as (DM).

Accessing the Report. Use AIS Business Objects to access, run, and print the Court Closure Follow-Up report.

Days Threshold Parameter. When generating this report, the user must enter a days threshold parameter. Since employees are required to initiate closure actions within 30 days of notification, generally this report should be run using no more than 30 days.

Frequency of Use by Caseworker. This report must be generated and worked weekly so closure actions are initiated within 30 days of the Service being notified of the discharge or dismissal.

Frequency of Use by Manager. Managers should review the Court Closure Follow-Up report "Monthly" to determine if cases are being closed in compliance with BCCP standards.

Range of Uses. This report identifies closures for Chapters 7N, 12, and 13 as well as individual Chapter 11 cases filed on or after October 17, 2005.

Chapters 7A and 11. This report is of limited value in listing Chapter 11 discharges because the courts issue Chapter 11 discharges upon plan confirmation with one exception. (See "note" below.) "Discharge" does not always mean the same thing for Chapter 11 cases as it does for other chapters. The Court Closure Report is of little value in listing Chapter 7A discharges because the courts usually issue Chapter 7A discharges immediately.

Note:

For individual Chapter 11 cases filed on or after October 17, 2005, confirmation of the plan does not result in a discharge. Instead, the court will grant a discharge when all plan payments are completed.

Use of Aged Case Report. The Aged Case Report is more useful than the Court Closure Report for identifying overage Chapter 7A cases.

History Documentation. Managers should be conservative in requiring documentation from caseworkers on an ongoing basis. The use of accepted acronyms should be encouraged. (See Exhibit in IRM 5.9.1-2, Acronyms and Abbreviations.)

Guide for Tech Review Follow-Up Report (Field Insolvency and CIO)

Overview. The Tech Review Follow-Up report may be used by both Field Insolvency and the Centralized Insolvency Operation. This report provides a listing of open cases selected by an Insolvency caseworker to be reviewed for a particular purpose within a specified range of dates. The user can create a list of follow-up priority items with action dates. A required action statement appears on the AIS Follow-up screen. This statement identifies the action needing attention by the caseworker.

Accessing the Report. Use AIS Business Objects to access, run, and print the Tech Review Follow-Up report.

  • When entering the beginning date, an old date, such as 01/01/2000, should be input to capture cases previously overlooked or cases entered with an incorrect date.

Frequency of Use by Caseworker. This list must be generated and checked by caseworkers at least "Monthly" to ensure cases continue towards closure.

Frequency of Use by Manager. The Tech Review Follow-Up report is reviewed by managers "Quarterly" to ensure cases continue towards closure.

Range of Uses. All chapters benefit through the use of the Tech Review Follow-Up Report.

Avoiding Redundancy. The Tech Review Follow-Up report contributes to workgroup efficiencies if used in conjunction with the other AIS Business Objects reports. Scheduling a future review of the master file for receipt of delinquent returns demonstrates an effective use of this report. Actions loaded by the user to this report should not duplicate actions listed on other reports.

Example:

A follow-up action item to prepare a POC should not be loaded because the Bar Date Follow-Up report will identify those cases.

Report Uses. The purpose of the Tech Review Follow-Up report is to focus on a particular range of cases (for example, Chapter 11 cases or large dollar Chapter 13 plans). Assigning follow-ups on every case may be counterproductive. A report listing non-critical action items debases its value for prioritizing case work.

Report Misuse. The caseworker who has not completed a scheduled action timely has the ability to change the action item with a future date giving the manager or reviewer a false impression the inventory is being effectively managed.

Critical Follow-Up Categories. Case actions that may be identified for follow-up include:

  1. Refiling of a Notice of Federal Tax Lien at least six months before the refile period expires because Automated Lien System (ALS) does not generate refile reports on accounts in bankruptcy;

  2. Monitoring federal tax deposits when appropriate (weekly, monthly, quarterly) depending on the size of the deposits and the case issue (e.g., not liable compliant Chapter 11s for one quarter, in-business Chapter 13 debtors, pre-confirmation Chapter 11 FTD monitoring); and

  3. Issuing courtesy investigations to protect ASEDs or make ASED determinations.

Updating Action Items. An action item can be added to a Tech Review Follow-Up report a number of ways by any user with update permissions. The AIS Follow-Up screen displays the follow-up fields directly.

Guide for Tech Review No Follow-Up Report (Field Insolvency)

Purpose of Report. The AIS Tech Review No Follow-Up report lists cases open on AIS where the assigned Insolvency caseworker has not input a future follow-up date. Since follow-ups can be input by anyone on any case, and this report only shows cases where the assigned caseworker did not input the follow-up, this report might prove to be of little value in managing case loads.

Accessing the Report. Use AIS Business Objects to access, run, and Tech Review No Follow-Up report.

Frequency of Use by Caseworker. This list must be generated and checked by caseworkers at least "Quarterly" to ensure cases continue towards closure.

Frequency of Use by Manager. The Tech Review No Follow-Up report is reviewed by managers "Quarterly" to ensure cases continue towards closure and no cases are overlooked.

Range of Uses. All chapters are subject to this report.

Guide for LAMS Closed Case Listing Report (Field Insolvency and CIO)

Unreversed TC 520s. This report identifies cases closed on AIS but with at least one IDRS module showing an unreversed TC 520. IRM 5.9.16.4.1, LAMS Closed Case Listing, provides step instructions for printing and working this report.

Guide for Pending Refunds Report (Field Insolvency and CIO)

Purpose of Report. The Pending Refunds report lists all cases with pending refunds on the Manual Refund screen of AIS.

Accessing the Report. Use AIS Business Objects to access, run, and print the Pending Refunds report.

Frequency of Use by Caseworker. Caseworkers must work the report at least weekly to ensure credits are processed timely.

Frequency of Use by Manager. Managers should review the report quarterly to identify trends or as part of employee reviews.

Range of Uses. All chapters are subject to this report.

Guide for ASED Report (Field Insolvency)

Purpose of Report. This AIS Business Objects report lists all ASEDs expiring before the date set by the caseworker or reviewer. Once the cases are identified, the caseworker must make a determination if proceeding with a TFRP investigation is appropriate. If so, actions must be taken to prevent the expiration of ASEDs on trust fund recovery penalty cases pursuant to IRC 6672 , Failure to Collect and Pay Over Tax, or Attempt to Evade or Defeat Tax.

Accessing the Report. Use AIS Business Objects to access, run, and print the ASED report.

  1. Enter beginning date. An old date, like 01/01/2000, should be input to capture cases previously overlooked or cases entered with an erroneous date.

  2. Enter ending date. Generally use 04/15/xxxx with the year being one year from the date of running of the report.

Range of Uses. Although AIS Business Objects allows the selection of every chapter and bankruptcy type, this report is most useful in Chapters 7A, 9, 11, and 12.

Time frames. This report should be run quarterly to identify ASEDs due the following April 15, the presumptive filing date of 941 returns. This catches cases that may have been recently filed or cases where a TFRP review was overlooked.

Note:

Field Collection may reject TFRP OIs where less than six months remain on the ASED. Thus it benefits Insolvency to request TFRP field investigations as early in the bankruptcy as possible.

Updating AIS. Because AIS Business Objects bases the extraction for this report on the earliest ASED in any module, whether the MFT deals with a trust fund liability or not, the ASED date pulled by this report may be of no use to the caseworker or reviewer. Thus the ASED on the AIS Taxpayer screen should be updated to the true most imminent ASED for trust fund liabilities. Managers should ensure caseworkers update each period on the Proof of Claim (POC) tab to ensure the proper TFRP drop down is selected, when necessary.

Guide for Unfiled Plans Report (Field Insolvency)

Purpose of Report. This Unfiled Plans report identifies Chapter 11, 12, and 13 cases where the plan filed date has not been entered on the AIS Taxpayer screen. Each case should be reviewed to determine if a plan has been received and the plan date was entered into AIS. Through the bankruptcy court's electronic records, the docket can be searched to see if a plan has been recorded. If necessary, the debtor's attorney or the bankruptcy court can be asked for a copy of the plan depending upon court jurisdiction requirements. All actions completed should be updated in the case history.

Accessing the Report. Use AIS Business Objects to access, run, and print the Unfiled Plans report.

Report Date Parameter. When generating this report, the user must enter a date parameter. Selecting dockets more than six months old for Chapter 13 cases and more than 12 months old for Chapter 11 cases is recommended. The date format is MM/DD/YYYY.

Chapter 13 Plans. IRM 5.9.10.6.1, Field Insolvency (FI) Actions Prior to Case Transfer, provides instructions on required AIS actions concerning input of plan data.

Chapter 11 Plans. Chapter 11 plans are frequently not received until at least six months after the petition date. Delays in plan filing will alert the caseworker to other problems with the Chapter 11 case.

Guide for Delinquent Case Report (Field Insolvency)

Overview. The Delinquent Case report provides a list of delinquent payments by extracting data from the AIS CPM Screen. The information it provides is only as accurate as the information from which it is compiled. A plan must be added into the CPM screen stating the payment amount, the due date of the first payment frequency, and the review date. If a plan is amended, the CPM data must be amended.

Accessing the Report. Use AIS Business Objects to access, run, and print the Delinquent Case report.

Chapters Affected. This report may be used in Chapters 11, 12, and 13. But it is most effective in Chapter 11 cases where the plan payment date is established for a specific date each month.

Guide for LAMS Post-Petition Case Listing Report (Field Insolvency)

Purpose of Report. The LAMS Post-Petition Case Listing lists both IMF and BMF post-petition liabilities found on master file. Although the LTS transcripts identify pyramiding more promptly, the post-petition report gives a complete history of post-petition compliance and lists all the post-petition modules involved, be they IMF or BMF. IRM 5.9.16.4.3, LAMS Post-Petition Case Listing provides information on generating and distributing this report.

Range of Uses. This report pertains to all chapters involving plans lasting more than 180 days (Chapters 9, 11, 12, and 13).

Guide for Referral to Counsel Report (Field Insolvency)

Purpose of Report. The Referral to Counsel report lists outstanding cases referred to Counsel for various actions, such as dismissal or conversion actions, or advisory opinions where the IRM, IRC, or Bankruptcy Code require specialized interpretation.

Note:

A listing of new Chapter 11 referrals should be pulled at month-end and counted for monthly reporting purposes on ICS.

Accessing the Report. Use AIS Business Objects to access, run, and print the Referral to Counsel report.

  1. Enter beginning date. An old date, like 01/01/2000, should be input to capture cases previously overlooked or cases entered with an erroneous date.

  2. Enter finish date. Generally use 90 days into future.

Range of Uses. This report identifies cases in all chapters where referrals have been made, and the AIS Referrals screen has been completed. (See IRM 5.9.4.15, Referrals – Representing IRS in Bankruptcy Court.) For month end reporting purposes, the group secretary or designee can pull the report to count Chapter 11 referrals within the monthly reporting period.

Reliability. The report is reliable if the Field Insolvency caseworker loaded the referral information to the Referrals screen for follow-up. Some offices maintain a manual log of cases referred. The automated system must be used, because a technician or clerk closing a case receives a notification a referral is pending when they attempt to close the case. If a manual system is used, the clerk or technician receives no notification of a pending referral when closing.

Pending Referrals. If case closure occurs and Counsel continues to work on a case that is resolved, valuable Counsel resources are wasted, and relations with Counsel might suffer. If numerous referrals for non-filing or objections are worked with Counsel (usually related to Chapter 13 cases), the report is a tool for determining the age of an unresolved issue.

Guide for LAMS Not Found on AIS Case Listing Report (Field Insolvency and CIO)

Purpose of Report. Cases are listed on this report because their TINs do not match any TINs in the presumed AIS database, and the Bankruptcy/Litigation Location Code (BLLC) is for a district other than the presumed district. Under normal conditions these cases belong to taxpayers with a Primary Location Code in the home district and a bankruptcy in a foreign district. IRM 5.9.16.4.2, LAMS Not Found on AIS Case Listing Report, provides step instructions for generating and working this report.

AIS Notification. LAMS reports are updated quarterly somewhere between one week before the end of the calendar quarter and up to five weeks after the end of the calendar quarter. A message appears on AIS when LAMS is updated. In some instances a case on this list may indicate a situation involving joint returns where only one spouse has filed bankruptcy.

Guide for Non-Master File Listing Report (Field Insolvency and CIO)

Purpose of the Report. The Non-Master File (NMF) Listing report must be worked by both Field Insolvency and the Centralized Insolvency Operation. It provides a roster of status 72 NMF assessments to be matched against the AIS open database to ensure the cases should be in litigation status and the CSED is not tolling.

Reminder:

When a bankruptcy closure applies to a module in NMF, the module was subject to the automatic stay, and a balance remains on the module, the CSED must be extended manually using TC 550.

Accessing the Report. Reports are generated at the SB/SE Campus in Cincinnati.

Contents of the Report. The TC 520 NMF listing includes litigation cases primarily involving bankruptcies and non-debtor spouses or other MFTs that still require NMF processing.

Note:

No asterisk = 90 to 179 days from 520 transaction date, * = 180 - 364 days from the TC 520 transaction date, and ** = one year or older.

Frequency of Use by Caseworker. The TC 520 listing should be generated quarterly for reconciliation. Insolvency should respond to the NMF unit within 60 days of receiving the report.

Frequency of Use by Manager. Managers should review the report annually for performance feedback purposes and to determine if CSED issues or other inventory management issues are addressed appropriately.

Retention. The NMF list should be retained for use in the following quarter to verify if accounts for which closing requests were previously submitted are truly closed.

Range of Uses. This report is used for all chapters of bankruptcy.

Case Matching. Cases should be matched against AIS and electronic court records if necessary due to age (greater than one year for Chapter 7 cases and greater than three years for all others) or lack of documentation in the AIS history.

IDRS Review. Caseworkers should check the IDRS status of cross referenced TINs to ensure their current collection status is appropriate in light of the pending bankruptcy.

Note:

Reorganizations have affected the district code listing. Any NMF listing that contains TC 520 bankruptcy accounts controlled by another Insolvency group should be faxed to the appropriate office and a history item entered on AIS to document.

Guide for Lien Research Report (Field Insolvency and CIO)

Purpose of the Report. This mandatory Lien Research report identifies cases that have been discharged and for which a Notice of Federal Tax Lien has not been systemically released. Insolvency must review the cases to identify those that require a manual release of the NFTL (excepting cases where pursuit of exempt, abandoned and excluded property is being considered). Failure to work this report may result in lien releases not being initiated within 30 days of notification of discharge when the liability is fully satisfied as defined in IRC 6325 , Release of Lien or Discharge of Property.

Accessing the Report Use AIS Business Objects to access, run, and print the Lien Research report.

Report Date Parameter. When the user is generating this report, they must enter a date parameter. Managers generating the report for review should use the start date of the prior quarter and an end date of the prior quarter.

Example:

If the manager is running the report on 04/01/2019, they will use 10/01/2018 as the beginning date and 12/31/2018 as the end date.

Caseworkers generating the report for case processing should use the start date of the week two weeks prior and an end date of the week two weeks prior to the date they run the report.

Example:

If the caseworker is generating the report on 01/10/2019 they will use 12/23/2018 as the beginning date and 12/29/2018 as the end date.

Using these time frames should assist in identifying liens that have not been released so corrective actions can be taken. The date format is MM/DD/YYYY.

Range of Uses. This report is used for Chapter 7 Asset, 7 No Asset, and Chapter 13 cases that have been discharged.

Procedures for Working the Report. The employee must review each case on the report and determine any lien requiring release within the 30 day requirement (IRC 6325, Release of lien or discharge of property) will be timely released through systemic actions. If it appears the release will be delayed due to a Discharge Determination Report (DDR), mirroring, etc., and all statutory liens for periods on the NFTL are satisfied as required under IRC 6325, a manual lien release should be requested. The lien release can be input directly into ALS.

History Documentation. The employee must document the history to reflect the lien research report was reviewed and whether or not a manual lien release requested, any periods deemed non-dischargeable, etc.

Note:

Managerial approval/denial of the lien release must also be documented in the AIS history.

Frequency of Use by Caseworker. This report must be generated and worked weekly.

Frequency of Use by Manager. Managers should review the report quarterly.

Retention. The Lien Research report should be retained for one year.

Guide for CSED Follow-Up Report (Field Insolvency and CIO)

Purpose of Report. The CSED Follow-Up report lists all CSEDs expiring before the date set by the caseworker or reviewer. This report is used to identify non-debtor spouses where the collection statute will expire within two years.

Accessing the Report. Use AIS Business Objects to access, run, and print the CSED Follow-Up report.

  1. Enter beginning date. An old date, like 01/01/2000, should be input to capture cases previously overlooked or cases entered with an erroneous date.

  2. Enter finish date. Generally this is a future expiration date so cases with imminent CSEDs may be identified and reviewed. A date two years in the future is recommended.

  3. Select Chapter type.

Frequency of Use by Caseworker. Caseworkers must work the CSED Follow-Up report semi-annually.

Frequency of Use by Manager. Managers should review the report semi-annually to identify trends or as part of employee reviews.

Range of Uses. Chapters 7A, 11, 12, and 13 are subject to this report.

Non-Debtor Partners. Partnerships, joint ventures, and limited liability companies with multiple TINs may have similar issues where collection may be pursued, but release of the TC 520 could increase the risk of a stay violation if assigned for routine collection processing. Through use of this report, the caseworker can identify cases where courtesy investigations should be issued before the stay is lifted.

Guide for Aged Cases Report (Field Insolvency and CIO)

Purpose of Report. This Aged Cases report identifies cases that are older than a certain number of days (270 for 7N and 7A cases, and 2190 for Chapter 13 cases) and do not yet have a dismissal/discharge date on AIS. IRM 5.9.16.6, Aged Case Reports, gives more information on this report.

Accessing the Report. Use AIS Business Objects to access, run, and print the Aged Cases report.

Frequency of Use by Caseworker. Annual matching is required. The CIO must work Chapter 7 No Asset and Chapter 13 cases assigned to its inventory. Field Insolvency must work the report for cases assigned to its inventory.

Frequency of Use by Manager. The manager should review this report annually to determine if trends are evident in cases' not being closed timely.

Range of Uses. This report is available for Chapters 7N, 7A, and 13.

AIS Documentation. Managers should be conservative in requiring documentation from caseworkers on an ongoing basis. A short history in the case to be closed may state "DS or DC per aged."

Guide for Plan Review Report (Field Insolvency)

Purpose of Report. This Plan Review report lists all cases in the database and provides an overall review of each case.

Accessing the Report. Use AIS Business Objects to access, run, and print the Plan Review report.

  1. Enter beginning date. An old date, like 01/01/2000, should be input to capture cases previously overlooked or cases entered with an erroneous date.

  2. Enter finish date. Generally use 90 days into future.

  3. Select Chapter type.

Range of Uses. This report can be run for Chapters 11 and 13.

Note:

If the Delinquent Case Report is used regularly, this report should be limited to special projects involving large dollar plans.

Guide for Case Assignment Reports (Field Insolvency and CIO)

Purpose of Reports. There are three Case Assignment Reports:

  • Assigned Profiles identifies how cases will be systemically assigned via the CAG program using information based on the CAG matrix.

  • CAG Assignment lists cases successfully processed and assigned to a caseworker during a specific period of time.

  • Ungraded Case Follow-Up lists cases that have not passed all systemic checks and remain unassigned. Generally, cases should not remain unassigned for more than five days.

Accessing the Report. Use AIS Business Objects to access, run, and print the Case Assignment reports.

Frequency of Use by Caseworker. The CIO Automated Process Control (APC) team is responsible for working the "Ungraded Case Follow-Up report" . This listing should be printed and reviewed weekly. The majority of the cases on the report are attributed to "Potentially Invalid TINs or Process D errors" . Prompt resolution of the error condition will allow assignment of the case the next time the IIP processes are run.

Frequency of Use by Manager. CIO Managers should review the Ungraded Case Follow-Up report monthly and Assigned Profiles report as needed. Field Insolvency Managers should review the Assigned Profiles and CAG Assignment reports as needed.

Range of Uses. All chapters are subject to this report.

Procedures for Working the Ungraded Case Follow-Up report. The caseworker must review each case on the report and determine the action to be taken in accordance with local procedures to resolve the condition preventing assignment.

Retention:

  • Assigned Profiles: when no longer needed.

  • CAG Assignment: when no longer needed.

  • Ungraded Case Follow-Up: electronic or hard copies should be retained six months from date of printing.

Guide for Letter 1714 Follow-Up Report (Field Insolvency)

Purpose of Report. The Letter 1714 Follow-Up report lists all cases where a letter requesting return information has been sent. The letter explains the debtor's duties under the Bankruptcy Code to file returns and the consequences of non-compliance which may include dismissal or conversion.

Accessing the Report. Use AIS Business Objects to access, run, and print the Letter 1714 Follow-Up report.

Range of Uses. Although AIS allows the selection of every chapter and bankruptcy type, this report is most useful in Chapters 7A, 9, 11, 12, and 13.

Note:

The highest volume of cases for review comes in the Chapter 13 program.

IDRS Research. This report provides a complete listing of unassessed returns and should be cross-checked against IDRS master file to determine if the return was filed in response to the claim of unassessed tax.

Referrals. This report is a resource to determine which cases to review for referral to Counsel requesting a case be dismissed or converted for non-filing of pre-petition tax returns.

LAMS. The report is related to the LAMS Unfiled Return Case Listing report in that it identifies unfiled returns when a POC determination is made. The LAMS Unfiled Return Case Listing report provides all delinquency investigation information on all TINs in the open AIS database. This report limits the information to cases where claims have been filed.

Guide for Other Investigation (OI) Follow-Up Report (Field Insolvency)

Purpose of Report. The OI Follow-Up report lists outstanding other investigations issued by Field Insolvency to Field Collection. The actions requested are usually related to Trust Fund Recovery Penalty investigations with time sensitive ASEDs or asset valuation cases where the IRS retains a secured lien interest in property.

Note:

The value of this report may be diminished by the current practice of Field Insolvency's opening the OI screen as a systemic prevention of premature case closure by CIO technicians.

Accessing the Report. Use AIS Business Objects to access, run, and print the OI Follow-Up report.

Range of Uses. This report covers Chapters 7, 9, 11, 12, and 13 for Trust Fund Recovery investigations and Chapters 7, 11, and 13 for exempt, abandoned, and excluded property investigations.

Cooperation with Field Collection. Effective communication between Field Insolvency and Field Collection managers reduces the need for extending the deadlines on other investigations. Insolvency caseworkers should establish cases on ICS for each AIS other investigation issued to facilitate the assignment of the investigation to Field Collection. Insolvency caseworkers should provide all relevant information concerning the bankruptcy case when an investigation request is issued. In most Trust Fund Recovery cases involving large companies, this necessitates review of the Statement of Financial Affairs so responsible officers located in different areas of the country can be identified promptly.

Multiple Investigations. Multiple other investigations can be routed and coordinated more effectively through ICS than through manual controls. The majority of cases involve closely held corporations with one or two officers in one location. Reviewing the Statement of Financial Affairs of corporations, partnerships, and LLCs gives the caseworker an idea of the complexity of the issues involved and the number of potentially responsible parties. Providing Field Collection with all available bankruptcy court or trustee information with the case assignment reduces delays in investigations.

Bankruptcy Schedules. Schedules relating to property should be provided to revenue officers whenever possible. Where the government has a secured position in exempt assets, caseworkers should determine from the bankruptcy schedules if exempt assets provide sufficient interest to pursue further collection action through referral to Field Collection. Web-based sources to determine the value of the government’s interest in real property should be consulted when possible. For further information on quick sale value analyses see IRM 5.8.5.4.1, Net Realizable Equity.

Guide for ICS Inventory Report (Field Insolvency)

Purpose of Report. This report will identify all cases assigned to the manager’s employees on ICS.

Accessing the Report. This report is generated from the ICS system.

  1. On the ICS Main Menu, click on the "Reports" button.

  2. On the Reports menu, click on "Advisory Reports" .

  3. On the Advisory Reports menu, click on "Inventory" .

  4. Click "View" next to "Employee Case Type Report" .

  5. Highlight either the report for a specific employee or for the entire group, as needed.

  6. Click "Get Report" .

Range of Uses. The report identifies cases assigned to Insolvency personnel that are open on ICS and therefore encompasses all chapters.

Note:

Revenue Officers close their own portion of the OI once they've completed their required actions. Insolvency is responsible for closure of their portion of the OI once they've verified all required activities requested are completed.

OI Control. Insolvency primarily uses ICS to control OIs it sends to Field Collection for 6672 investigations, exempt and abandoned asset determinations, and other coordinated activities.

Reminder:

Insolvency personnel should have a corresponding OI screen open on AIS to prevent premature closure of the AIS case while there are joint activities on-going.

Guide for Large Dollar Report (Field Insolvency)

Purpose of Report. The Large Dollar Report lists all cases in the open AIS file with POC data meeting a dollar criterion established by the caseworker or reviewer allowing prioritization of casework by dollar amount. IRM 5.9.4.15.3, Significant Bankruptcy Case Referrals, requires all cases meeting certain criteria to be identified and reported to Counsel as significant. This report also identifies cases likely to have post-petition trust fund or income tax pyramiding, assuming a large proportion of bankruptcy filers who owe prior to bankruptcy have the likelihood of owing significant dollar amounts after bankruptcy is filed.

Accessing the Report. Use AIS Business Objects to access, run, and print the Large Dollar report.

Range of Uses. All chapters are subject to this report.

Who Prints the Report. The secretary or caseworker who processes the ICS month end inventory reports can generate this report at the end of each quarter when Chapter 11 referral information is being gathered for reporting purposes. Grade 12 Field Insolvency caseworkers should be able to generate this report to identify significant cases for referral and to improve inventory management skills.

Other Uses. During the pendency of extended bankruptcy, this report can identify debtors who fund bankruptcy plans by not paying current taxes, thus creating post-petition liabilities. Taxpayers owing significant amounts of money at the time of bankruptcy filing may not resolve their nonpayment issues during the bankruptcy. The Field Insolvency caseworker may, for example, review all taxpayers owing over $25,000 at bankruptcy filing. Similar parameters can be set for long term plans with in-business Form 941 liabilities. The LAMS Post-Petition Case Listing report is the most effective tool to use because it draws its information every quarter from true master file account information. If LAMS is unavailable, this report is an alternative for prioritizing cases for post-petition review.

Note:

The Large Dollar report pulls information from the proofs of claim amount data.

Inventory Management. The Large Dollar report, as an inventory management tool, lists priority cases by the delinquency amount established by the user in docket number order

Large Dollar Chapter 7N Report. CIO does the screening of Large Dollar Chapter 7N cases following IRM 5.9.6.10.3(2), CIO Screening. If assets are located, the CIO documents those assets in the AIS History screen and reassigned the case to FI. Upon receipt of the case from CIO, the FI caseworker follows IRM 5.9.6.10.3(3), FI Investigation.

Guide for Unpostable Reports (Field Insolvency and CIO)

Purpose of the Report. The Unpostable Report, also called the Generalized Unpostable Framework (GUF), lists cases Insolvency entered a transaction on that went unpostable. Insolvency (both FI and CIO) is responsible for resolution of the resulting unpostable condition. General guidance for identifying and resolving unpostable transactions can be found in IRM 21.5.5, Unpostables.

Accessing the Report.

  • FI receives their overage reports from SB/SE Collection IDRS Data Security Group in Collection Automation Support and Security (CASS) monthly.

    Note:

    The FI Nullified Distribution listing is available weekly from CASS. This weekly listing is processed by the CIO Unpostable 168 IAT tool. Cases from the listing that cannot be resolved by the tool will appear on the monthly overage report.

  • CIO usually pulls their overage reports via Control-D or Overage Report Compiler and Sorter (ORCAS) on a weekly basic.

Report Types. Two types of reports are produced.

  1. Overage Report is discussed in detail in IRM 5.9.16.5.1, Overage Report.

  2. Nullified Distribution List is discussed in detail in IRM 5.9.16.5.2, Nullified Distribution List (NULL DIST LST).

Frequency of Use by Caseworker. Time frame for completion of the unpostable reports:

  • CIO reports are worked weekly when the listing becomes available.

  • FI reports are worked monthly when the listing becomes available.

This report is worked when a listing becomes available.

Frequency of Use by Manager. Managers should review reports when completed by the caseworker to ensure issues are properly addressed and potential stay violations have been addressed/corrected.

Range of Uses. This report is pertinent for all chapters.

Statutes. ASEDs and CSEDs are two reasons these cases should be worked as soon as they are received. Imminent statute information must be included in the history when requesting resolution of an unpostable.

Retention. Reports should be destroyed when no longer needed in current operations.

Requisite Command Codes. Those working this report must have command code ACTON in their IDRS profile.

CAG Pre-Assignment Factors

Factor Name Description
1 Chapter • 7N
• 7A
• 09
• 11
• 12
• 13
• 15
• AS (Assignments)
• DC (Decedent/Probate)
• RC (Receiverships)
2 Unpaid Liability • Ranges vary by chapter (See Exhibit 1.4.51-36, CAG Pre-Assignment Difficulty Indicators.)
3 Entity • IMF
• BMF
4 Business Operating Division (BOD) • WI
• SB
• LM
• TE

CAG Pre-Assignment Difficulty Indicators

GS-07 Technician

Chapter Bal Due File Source BOD
7N All IMF, BMF All
7A $0 - $19,999 IMF, BMF WI, SB
9 N/A N/A N/A
11 N/A N/A N/A
12 N/A N/A N/A
13 N/A N/A N/A

GS-09 Specialist

Chapter Bal Due File Source BOD
7A $20,000-$249,999` IMF, BMF WI, SB
9 $0-$49,999 BMF TE
11 $0-$49,999 IMF, BMF WI, SB
12 $0-$49,999 IMF, BMF WI, SB
13 $0-$49,999 IMF, BMF WI, SB

GS-11 Specialist

Chapter Bal Due File Source BOD
7A $250,000+ IMF, BMF WI, SB, LM, TE
9 $50,000 - $149,999 BMF TE
11 $50,000 - $149,999 IMF, BMF WI, SB
11 $0 - $149,999 BMF LM, TE
12 $50,000 - $149,999 IMF, BMF WI, SB
12 $0 - $149,999 BMF LM
13 $50,000 - $149,999 IMF, BMF WI, SB

GS-12 Specialist

Chapter Bal Due File Source BOD
7A N/A N/A N/A
9 $150,000+ BMF TE
11 $150,000+ IMF, BMF All
12 $150,000+ IMF, BMF WI, SB, LM
13 $150,000+ IMF, BMF WI, SB

Post-Assignment Difficulty Indicators Factor 5: Case Action

GS-07 Technician GS-09 Specialist GS-11 Specialist GS-12 Specialist
Performs routine processing of POCs. Performs routine analysis and investigations. Conducts in-depth analysis, which may involve asset transfers and lien priority. In the most complex cases, uses extensive knowledge and analytical techniques to determine:
• Viability of business’ continued operation
• Government’s position in adversarial complaints
Performs routine closing actions to include discharge and dismissals. Performs routine recommendations and requests for legal assistance. Recommends and requests legal assistance on more complex issues involving:
• Application of law
• Hidden and undisclosed assets
• Large examination assessments
• Corporations
• TEFRA
• Multiple BMF entities
Recommends and requests legal assistance on the most complex issues:
• Fraud
• Lien priorities
• Property ownership
• Settlement options
• Nominee/alter ego/transferee
Prepares manual refund requests. Reviews and responds to court documents on routine issues. Reviews and responds to moderately difficult cases to make an informed judgment about a proposed plan of reorganization. Advisory opinion: researches complex case issues to determine and apply law to facts presented. Opinions may be oral or written.
Reviews and responds to schedules and disclosure statements in complex cases to make an informed judgment about a proposed plan of reorganization. Resolves potential BCCP claims.

Post-Assignment Difficulty Indicators Factor 6: Communication

GS-07 Technician GS-09 Specialist GS-11 Specialist GS-12 Specialist
Responds to routine inquiries from taxpayers, their representatives or representatives of the court relative to case or task assignment. Confers with taxpayers, their representatives, creditors, third parties, other employees, Counsel or representatives of the court to resolve issues and determine the next course of action.
Attends meetings of creditors and testifies relative to level of expertise.
Prepares technical written documents (e.g. referrals to Counsel) relative to case or task assignment.
Confers with United States Attorney’s Office, Counsel, taxpayers, corporate officials, lawyers, bankers, creditors, third parties and prominent members from the business or political fields in complex cases.
Attends meetings of creditors and testifies at hearings relative to level of expertise.
Advises and consults with Service personnel on complex aspects of bankruptcy.
Contacts involve Department of Justice, United States Attorney’s Office, Area Counsel and accountants and CPAs from firms representing the largest business accounts in highly complex cases.
• Serves as expert witness
• Acts as contact with internal and external customers relative to duties and responsibilities as a program coordinator
• Deals with high profile and sensitive cases
• Delivers agency’s perspective in outreach presentations
Negotiates:
• Settlement options
• Adequate protection
• Complex plans

Post- Assignment Difficulty Indicators Factor 7: Supervisory Controls

GS-07 Technician GS-09 Specialist GS-11 Specialist GS-12 Specialist
Moderate supervisory control is exercised in handling of typical GS-07 cases. Little or no supervisory control exercised on typical GS-09 cases. Little or no supervisory control exercised on typical GS-11 cases. Little or no supervisory control exercised on typical GS-12 cases.
Completed work is reviewed for appropriateness, soundness, and conformance with established guidelines. Completed work is reviewed for technical soundness, appropriateness, soundness and conformance with established guidelines. Completed work is reviewed on the basis of results accomplished and is normally accepted without change. Samples of completed work are reviewed to ensure fulfillment of program guidelines, procedures and objectives. Completed work is rarely changed, as incumbent is considered to be a technical expert.
Issues in bankruptcy cases which cannot be resolved by the incumbent are referred to a higher graded employee for resolution. Incumbent exercises independent judgment and initiative in determining the course of action on routine bankruptcy cases
Guidance is limited to:
• Cases where unusual or unfamiliar situations arise
• Case actions which require an interpretation of the Bankruptcy Code or IRM
• Cases which involve matters of public interest or have potential to create adverse publicity
Guidance is limited to:
• Cases in which unusually difficult problems arise
• Case actions involving matters of public interest or the potential to create adverse publicity
• Case actions / decisions which may set a precedent
Supervisory consultations limited to:
• Cases involving significant or sensitive issues
• Decisions which deviate from established policy
• Cases which significantly impact other divisions or functions within the IRS
• Cases which involve matters of public interest or have potential to create adverse publicity

Post-Assignment Checklist Factor 5: Case Action

Series/Grade Description
GS-592-07
• Performs routine processing of POCs (regardless of chapter).
• Performs routine closing actions to include discharges and dismissals (regardless of chapter).
• Prepares manual refund requests (regardless of chapter).
GS-1101-09
• Performs routine analysis and investigation.
• Performs routine recommendations and requests legal assistance.
• Reviews and responds to court documents on routine issues.
• Reviews and responds to routine plan and disclosure statements.
GS-1101-11
• Conducts in-depth analysis which may involve asset transfers and lien priority.
• Recommends and requests legal assistance on more complex issues involving application of law, hidden and undisclosed assets, large examination assessments, corporations, TEFRA and multiple BMF entities.
• Reviews and responds to moderately difficult cases to make an informed judgment about a proposed plan or reorganization.
GS-1101-12
• In the most complex cases, uses extensive knowledge and analytical techniques to determine viability of business' continued operations, government's position in adversarial complaints.
• Recommends and requests legal assistance on the most complicated issues (fraud, lien priorities, property ownership, settlement options, nominee/alter ego/transferee).
• Advisory opinion: researches complex case issues to determine and apply law and facts. Opinions may be oral or written.
• Reviews and responds to schedules and disclosure statements in complex cases to make an informed judgment about the proposed plan or reorganization.
• Resolves potential BCCP claims.

Post-Assignment Checklist Factor 6: Communication

Series/Grade Description
GS-592-07
• Responds to routine inquiries from taxpayers, their representatives, or representatives of the court relative to case or task assignments.
GS-1101-09
• Confers with taxpayers, their representatives, creditors, third parties, other employees, Counsel or representatives of the court to resolve issues and to determine next course of action.
• Prepares technical written documents (e.g. referrals to Counsel) relative to case or task assignments.
• Attends meetings of creditors and testifies relative to their level of expertise.
GS-1101-11
• Confers with United States Attorney's Office, Counsel, taxpayers, corporate officials, lawyers, bankers, creditors, third parties, and prominent members from the business or political fields in complex cases.
• Attends meetings of creditors and testifies at hearings relative to their level of expertise.
• Advises and consults with Service personnel on complex aspects of bankruptcy.
GS-1101-12
• Contacts involve Department of Justice, United States Attorney's Office, Area Counsel, and accountants and CPAs from firms representing the largest business accounts in highly complex cases.
• Negotiates settlement options, adequate protection, and complex plans.
• Serves as expert witness.
• Contacts include internal and external customers relative to duties and responsibilities as a program coordinator.
• Deals with high profile and sensitive cases.
• Delivers agency's perspective in outreach presentations.

Post-Assignment Checklist Factor 7: Supervisory Control

Series/Grade Description
GS-592-07
• Moderate supervisory control is expected.
• Completed work is reviewed for appropriateness, soundness, and conformance with established guidelines.
GS-1101-09
• Little or no supervisory control is exercised.
• Completed work is reviewed for technical soundness, appropriateness, and conformance with established guidelines.
• Incumbent exercises independent judgment and initiative in determining the course of action on routine bankruptcy cases.
• Guidance is limited to cases where unusual or unfamiliar situations arise, case actions which require an interpretation of the Bankruptcy Code or IRM, or cases which involve matters of public interest or have potential to create adverse publicity.
GS-1101-11
• Little or no supervisory control is exercised.
• Completed work is reviewed on the basis of results accomplished and is normally accepted without change.
• Guidance is limited to cases in which unusually difficult problems arise, case actions involving matters of public interest or the potential to create adverse publicity, or cases which may set a precedent.
GS-1101-12
• Little or no supervisory control is exercised.
• Samples of completed work are reviewed to ensure fulfillment of program procedures and guidelines.
• Completed work is rarely changed as incumbent is considered a technical expert.
• Supervisory consultations are limited to cases involving significant or sensitive issues, decisions which deviate from established policy, cases which significantly impact other functions with the IRS, cases which involve matters of public interest or have potential for adverse publicity.

Case Assignment Profile Matrix

FLSO1 GS-07 GS-09 GS-11 GS-12
Chapter 7N A-C SEID YUBA
D-M SEID SMITH
N-Z SEID BALL
N/A N/A N/A
Chapter 7A A-C SEID YUBA
D-Z SEID BALL
A-F SEID BENT
G-Z SEID DREW
A-F SEID CLAY
G-R SEID THOMAS
S-Z SEID MACK
N/A
Chapter 9 N/A
A-F SEID BENT
G-Z SEID ADAMS
A-D SEID DANTE
E-Z SEID PETERS
A-Z SEID NESS
Chapter 11 N/A
A-F SEID BENT
G-Z SEID ADAMS
A-D SEID DANTE
E-Z SEID PETERS
A-Z SEID NESS
Chapter 12 N/A N/A N/A A-Z SEID NESS
Chapter 13 N/A A-F SEID HILL
G-Z SEID EDDY
A-F SEID YORK
G-Z SEID POLK
A-F SEID NESS
G-Z SEID PIMA

CAG Post-Assignment

Coverage. This portion of the Insolvency Case Assignment Guide (CAG) is primarily used to provide information which assists managers in determining if a task should be referred or an entire case reassigned. The post-assignment factors identify tasks/issues that are encountered or develop during the process of working the case. Careful review of post assignment factors should be made, as the case evolves, to ensure the case is assigned to the proper grade level of employee.

Factor Case Actions Description
5 Case Action Covers tasks/issues anticipated at the corresponding grade levels.
6 Communication Includes typical individual(s) contacted and the purpose of contacts.
7 Supervisory Controls Outlines the functioning relationship between the manager and employee, the degree of independence the employee is expected to exhibit and the extent of supervisory review of work products or accomplishments.
Most issues referred from a lower to a higher graded employee will not result in the overall reassignment of the case. If the case is permanently reassigned, the manager must measure the case against the three post-assignment factors. While it is not necessary to meet all three factors, a case will generally not be graded at the higher level unless it meets a majority of the factors at the higher level or contains a difficulty indicator that has significant impact.

Note:

All Chapter 7N cases are initially assigned to CIO. Large Dollar Chapter 7N cases are screened by CIO and assigned to Field Insolvency when potential collection from assets is identified. Chapter 7N cases assigned to Field Insolvency should be re-graded by the Field Insolvency Manager according to guidelines provided by the Director, Specialty Collection - Insolvency.

Operational Review Plan Guide

Program Review Areas:

  • Case file reviews

  • NFTL determination accuracy

  • Quality – EQ/NQ analysis

  • Quality – Consistency reviews with GM

  • Alternative case resolution discussion – are we fully utilizing Counsel, FTAs, CI, and our Abusive Tax Avoidance Transaction (ATAT) and OIC resources such as the OIC Pre-Qualifier tool located on irs.gov at: http://irs.treasury.gov/oic_pre_qualifier/?

  • TFRP/ATFR process

  • ENTITY/Management Information Systems (MIS) analysis of trends in performance indicators.

  • GM controls

  • Employee Performance Folder (EPF) reviews

  • Communications

  • Employee Satisfaction

  • Customer Satisfaction

  • ATAT Program

  • Group Time Reporting and Analysis – relating to productivity and cycle time

  • Group Productivity and Efficiency

  • Annual Appraisal/Performance Document Approval

  • Fraud program/identification and FTAs involvement

  • Inventory ranges and assignment practices/ Inventory delivery process

  • Above grade work

  • Million dollar case assignments

  • Multi-module strategy

  • Trends and patterns report – teller errors

  • Span of control

  • Summons errors

  • Hold file composition and time in hold file – review for any issues with assignment and staffing

  • Group Meeting attendance

  • Field Visits

  • Other/Local

Mandatory: Administrative and Compliance Reviews / Territory / Operation Manager Oversight:

  • EPF – administrative review

  • Controls monitoring

  • SETR and timekeeping

  • Security – after hours and computer systems

  • Form 3210 transmittals review

  • Correspondence and file retention

  • Travel vouchers and authorizations

  • Credit bureau

  • Purchase cards and supplies

  • Section 1204 / ROTERs

  • EQ consistency review for territory

  • Sensitive Case Reports – timely and appropriate

  • GMs Employee review schedule at beginning of fiscal year

  • Other

Optional: One on One Briefing - Periodic scheduling:

  • GM is scheduled for periodic briefings during the months of: (fill in)

  • Topics covered will include: (fill in )

Director Operational Aid (DOA)

Operational Reviews:

Purpose - to assess Territory / Operation Manager performance in achieving Area, HQ, and territory / operation business plan goals and to improve Employee Satisfaction and Customer Satisfaction while enhancing Business Results.

Frequency - Operational Reviews are to be performed on an annual/fiscal year basis with follow-up reviews to be performed when appropriate.

Scope - all general and specialized Collection territories.

Documentation - all Operational and Follow-up Reviews are to be documented in a memorandum format. These documents should be shared with the Territory / Operation Manager within sixty (60) days of completion of the actual review. The operational review should also include a candid discussion regarding the Territory / Operation Manager’s performance.

Pre-Operational Review Actions:

Trend Analysis - to identify and evaluate trends that may require managerial involvement.

Technique - utilize cumulative data acquired during the fiscal year, identifying areas of achievement and those that require improvement. (See Trend Analysis, under Additional Reviews and Actions). A comparison to the prior year as well as the current goals may be appropriate. The Operational Review narrative should indicate what the trend analysis revealed, areas of concern or achievement, additional actions taken in the operational review as a result of the trend analysis, recommendations, etc.

Note:

Territory / Operation Managers should be submitting completed operational reviews and mid-year feedback to the Director in preparation for Operational Reviews.

Operational Reviews should include at a minimum, assessments of the following:

Territory / Operation Operational Reviews / Follow-Ups - to ensure that Territory / Operation Managers are addressing issues identified in the Territory / Operation Manager’s Operational Aid as well as the Director’s goals.

Technique - review Territory / Operation Manager operational and follow-up reviews to ensure adherence to guidelines set by the Territory / Operation Manager’s Operational Aid. Ensure that areas identified as concerns are being proactively addressed in Territory / Operation operational reviews and follow-ups and corrective actions are prescribed when applicable.

Territory / Operation Manager Performance - to ensure that:

  1. Territory / Operation Manager activities are promoting the achievement of the Director’s Collection Business plan, and

  2. Group managers are establishing proactive commitments and goals and are fulfilling the requirements of their Critical Performance Expectations.

Technique -

  1. Determine if Territory / Operation Manager is proactively contributing to the Director’s Collection Business Plan.

  2. Ensure Territory / Operation Managers are issuing operational, follow-up, and mid-year feedback in a timely manner. Ensure Territory / Operation Manager compliance with the established review schedule.

  3. Ensure Territory / Operation Manager mid-year feedback is addressing proactive actions established in the manager’s initial performance agreement. These reviews should identify areas of accomplishment as well as those in need of improvement with recommended strategies. This should also be apparent in operational reviews and final performance evaluations.

  4. Determine if Territory / Operation Managers’ evaluations of group managers align with mid-year feedback and other evaluative documents. If discrepancies are noted or concerns exist, ensure appropriate actions are taken.

Training - to ensure managers are receiving appropriate training to facilitate efficient group operations.

Technique - discuss with Territory / Operation Manager what training has been made available to group managers. For some courses budgetary ramifications must be considered.

Communication - to ensure Territory / Operation Managers are effectively communicating to group managers the goals of Headquarters and territory / operation.

Technique - review minutes of territory / operation meetings. Ensure Territory / Operation Managers are discussing special interest cases within their groups, e.g., suits, seizures, fraud referrals. Include observations from territory / operation meeting(s) attended. Consider conducting focus group interviews with group managers and/or revenue officers.

Employee Satisfaction - to ensure that employees’ and manager’s concerns are being addressed to facilitate effective and appropriate casework.

Technique -

  1. Review Territory / Operation operational reviews to ensure Territory / Operation Managers are adhering to Employee Satisfaction guidelines of the Territory / Operation Manager aid and addressing managerial adherence to established policies and procedures.

  2. Ensure Territory / Operation Manager and GMs are addressing issues raised in most recent employee survey.

Case File Reviews - to promote proactive, timely, and appropriate case actions and managerial involvement when appropriate.

Technique - based upon trend analysis results and Director’s goals, select a mix of cases representative of the inventory.

Alternative Case Resolutions - to ensure that all possible forms of case resolution are investigated.

Technique - discuss with the Territory / Operation Manager their involvement in promoting the appropriate use of the Fraud Technical Advisor, Counsel, and Criminal Investigation.

Customer Satisfaction - to ensure customers are receiving timely and appropriate actions, and receiving fair and adequate treatment to assist in resolving their delinquency issue(s).

Technique - assess Territory / Operation Manager’s involvement in addressing customer service issues. This should be evident in operational reviews and discussions with Territory / Operation Managers.

EQRS Consistency Reviews - to ensure Territory Managers are conducting EQRS Consistency Reviews annually and actions are taken to promote consistent application of the EQ attributes.

Additional Reviews and Actions to be Completed During the Fiscal Year:

Mandatory actions:

Trend Analysis - to identify possible case trends on a monthly and cumulative basis, and ensure appropriate actions are being taken to achieve Headquarters goals.

Technique - engage Collection Policy Analysts to identify trends in accordance with Director’s goals and other pertinent indicators such as time utilization (field, and administrative time), large dollar cases, ATFR controls, no touch reports, etc.

Frequency - reports and trends should be reviewed on a monthly basis

Suggested Optional Actions:

Field Reviews - to ensure employees are effectively contacting taxpayers and making optimum use of field time.

Technique -

  1. Review a sampling of field visitation reviews completed by at least two group managers in a territory.

  2. Accompany an employee during a field visit. (When budgetary guidelines allow).

Frequency - the frequency should be established by the facts and circumstances of the and group.

Documentation - provide a written narrative to the Territory Manager or discuss the findings.

Communication - to ensure expectations of performance are understood and managerial concerns are heard and addressed.

Technique -

  1. Convene meetings including Territory / Operation Managers, Collection Policy Analysts, and Senior Insolvency Specialist to ensure that trends and goals are being monitored and acted upon in an appropriate and timely manner.

  2. Hold town hall meetings to discuss goals and concerns with group managers and Territory / Operation Managers. This should also include involvement of peripherally involved divisions such as Labor Relations, Counsel, Appeals, etc.

  3. Attend at least one territory meeting between managers and Territory / Operation Manager for each territory.

  4. Attend a sample of group meetings to ensure top down messages are understood and encourage open communication lines.

Frequency - all meetings are subject to budgetary constraints as well as facts and circumstances of the Area. Preferably these meetings would be held in person, but attendance via conference call is also acceptable.

  1. Meetings should be held at least quarterly.

  2. Town Hall meetings should be held once each fiscal year if possible.