Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

1.4.51  Insolvency

1.4.51.1  (08-01-2007)
Insolvency Functional Roles

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

    • Advisory, Insolvency and Quality (AIQ)

    • Campus Compliance

    • Collection Policy

    • Campus Compliance Service Policy

    • SBSE Counsel

  2. AIQ. Field Insolvency, with offices throughout the country, belongs to the Advisory, Insolvency, and Quality (AIQ) function. Field Insolvency handles all aspects of Chapter 7 Asset, 11, and 12 accounts except for clerical processing and works Chapter 13 cases from initial case review through confirmation. Field Insolvency refers Chapter 9 and Chapter 15 cases to Counsel for procedural guidance after clerical processing has been completed. Field Insolvency offices respond to "complex issues" on any case regardless of chapter. (See IRM 5.9.1.3(3),Complex Issues.).

  3. Campus Compliance. The Centralized Insolvency Operation (CIO), located in Philadelphia, is part of the Campus Compliance Services Organization. The CIO performs initial clerical processing on cases for all bankruptcy chapters. The CIO works Chapter 7 No Asset cases from 341 notice to closure, and it works Chapter 13 cases from confirmation to closure. Chapter 9 and Chapter 15 cases are loaded onto AIS by the CIO and then forwarded to Field Insolvency to work any IIP reports and for referral to Counsel.

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

    1. owns IRM 5.9 and IRM 1.4.51;

    2. owns the Automated Insolvency System (AIS);

    3. makes all policy decisions affecting Insolvency as an enterprise covering both the CIO and Field;

    4. establishes Field Insolvency procedures;

    5. participates on the BLARE rules committee;

    6. submits requests for systems updates;

    7. responds to suggestions made through Form 5391,Procedures/Systems Change Request, or Form 13380,I Suggest;

    8. interacts with other National Office analysts on issues that impact bankruptcy processing;

    9. clears IRM bankruptcy sections written for other programs, such as field Collection and Examination;

    10. handles technical questions from Field Insolvency;

    11. performs operational reviews of Field Insolvency and the CIO; and

    12. when appropriate addresses CIO issues through contact with Campus Compliance policy analysts.

  5. Campus Compliance Services Policy. Tax policy for Campus Compliance:

    1. establishes procedures for CIO processing;

    2. helps in writing and formatting IRM 5.9;

    3. addresses CIO automated systems issues;

    4. owns the BLARE information system;

    5. participates on the BLARE rules committee;

    6. handles technical questions from the CIO staff;

    7. performs operational reviews of the CIO;

    8. screens Forms 5391,Procedures/Systems Change Request, and Form 13380,I Suggest, submitted by CIO employees before forwarding approved forms to Collection Policy for review; and

    9. when appropriate elevates CIO issues to Collection Policy.

  6. SBSE 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 LEM criteria, may coordinate action(s) with Area Counsel, the Assistant United States Attorney (AUSA), 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 SAUSAs,IRM 5.9.4.15.3,Referrals on Significant Bankruptcy Case Issues, and LEM 5.9.4.)

1.4.51.2  (08-01-2007)
Case Management Tools

  1. Introduction. Front line Insolvency managers are expected to use tools available to them to ensure the cases in their inventories 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. Reports as Tools. AIS and other automated systems provide reports to help manage required actions. Use of eight AIS reports (or their equivalent) is mandatory. ( See IRM 1.4.51.10.) Using the remaining reports to control case load is discretionary. Specially devised reports, prepared through MyEureka or other IRS approved software, may be substituted for standardized AIS reports. ( See IRM 1.4.51.10.)

  3. Mandatory Processing Duties. 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.

    Note:

    The titles for Exhibits 1.4.51-2 through 1.4.51-32, cross referenced below, are followed by the function(s) that will most often use that particular report.

    Field Insolvency Both CIO
    Meet bar dates. ( See Exhibit 1.4.51-2.) Resolve stay violations timely. (See IRM 5.9.3.4.) Work DDRs timely. (See IRM 5.9.17.3)
    Monitor plan filings and review plans. ( See Exhibit 1.4.51-3.See Exhibit 1.4.51-16. See IRM 5.9.5.4.1.) Monitor postpetition compliance. ( See Exhibit 1.4.51-25.See Exhibit 1.4.51-7.) Run IIP processes C and D. (See IRM 5.9.12.6.)
    Attend 341 hearings when appropriate. (See IRM 5.9.2.4.) Protect collection statutes. ( See Exhibit 1.4.51-28.See Exhibit 1.4.51-4.) Run IIP process J. (See IRM 5.9.12.6.)
    Protect assessment statutes. ( See Exhibit 1.4.51-8.See Exhibit 1.4.51-9.) Ensure timely responses to the Taxpayer Advocate. (See IRM 5.9.3.7.) Download ENS. (See Exhibit in IRM 5.9.12-1.)
    Respond to claim objections timely and follow up. ( See Exhibit 1.4.51-13.) Generate and work litigation transcripts. ( See Exhibit 1.4.51-25.) Work IIP error reports and PIT reports. (See IRM 5.9.12.6and IRM 5.9.12.6.2.)
    Submit plan objection referrals timely and follow up. ( See Exhibit 1.4.51-13.) Generate and work Aged Case Report annually. ( See Exhibit 1.4.51-22.) Work IIP status reports. ( See Exhibit 1.4.51-31.)
    Address adequate protection when appropriate. (See IRM 5.9.8.5.) Work LAMS Not Found on AIS report and LAMS Closed Case List quarterly. ( See Exhibit 1.4.51-23.See Exhibit 1.4.51-24.) Run IIP 2 (ADS). (See IRM 5.9.12.7.)
    File administrative claims. (See IRM 5.9.13.13.) Release NFTLs timely. ( See Exhibit 1.4.51-32. See IRM 5.9.17.4.2.) Work ADS process K and L errors. (See IRM 5.9.12.7.)
    Monitor plan payments. ( See Exhibit 1.4.51-3.) Load cases to AIS and ensure TC 520 input timely. (See IRM 5.9.12.4and Exhibit in IRM 5.9.12-1.) Distribute time sensitive mail timely. (See IRM 5.9.11.3.2.)
    Address delinquent plans. ( See Exhibit 1.4.51-11.) Address follow-up actions timely. ( See Exhibit 1.4.51-20.) Mirror MFT 31 accounts for all chapters. (See IRM 5.9.17.15.1.)
    When incomplete prompt determination request received, advise requester of missing documentation; when all documentation received, submit package to Exam. (See IRM 5.9.4.8.1.) Review and sign manual refund requests. (See IRM 5.9.16.4.) 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.8.1.)
    Pursue exempt, abandoned, or excluded property when appropriate. (See IRM 5.9.4.1.2.) Balance inventories among caseworkers and/or groups. ( See Exhibit 1.4.51-5.See Exhibit 1.4.51-6.) Work trustee refund turnover requests. (See Exhibit in IRM 5.9.6-2.)
    Submit fraud referrals. (See IRM 5.9.4.10.1.) Identify cases mis-assigned by CAG or left unassigned by CAG and assign them manually. ( See Exhibit 1.4.51-29.See Exhibit 1.4.51-21.) Post all payments received at the CIO regardless of chapter. (See IRM 5.9.15.)
    Secure delinquent returns. (See IRM 5.9.4.17.See Exhibit 1.4.51-17.) Verify correct case grade assignments through CAG. ( See Exhibit 1.4.51-21.)  
    Initiate referrals to Field Collection when applicable. ( See Exhibit 1.4.51-12.) Identify fraud. (See IRM 5.9.4.10.3.)  
    Request TFRP investigations from field Collection timely or begin in-house TFRP investigations timely. (See IRM 5.9.3.9.) Work NMF listing. ( See Exhibit 1.4.51-27.)  
    Post Chapter 7 Asset, 11, and 12 payments. (See IRM 5.9.15.) Resolve unpostables timely. ( See Exhibit 1.4.51-26.)  
    Address significant cases. (See IRM 5.9.4.15.3.) Initiate case closure timely. ( See Exhibit 1.4.51-15.See Exhibit 1.4.51-19.See Exhibit 1.4.51-30.)  
    Take appropriate actions on postpetition liabilities. ( See Exhibit 1.4.51-25.See Exhibit 1.4.51-7.See IRM 5.9.16.3.2.)    

1.4.51.3  (08-01-2007)
Insolvency Managers' Duties and Responsibilities

  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 workdays after identification by Insolvency caseworkers or notification from taxpayers, their representatives, other government agencies, or other IRS functions. IRM 5.9.3.4,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 workdays 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.8,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 IRS's involvement in a bankruptcy proceeding in the AIS history, also known as the "detail screen." Insolvency is the primary repository of bankruptcy-related case actions for all functions of the IRS. (See IRM 5.9.5.4.1,AIS Documentation.)

  6. Objections. When possible Insolvency administratively resolves objections to IRS's actions in bankruptcy, usually involving proofs of claim, that otherwise would be handled by the US Attorney, Department of Justice, 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 local Counsel, the US Attorney, or the Department of Justice.

  7. Damage Claims. Insolvency managers must process administrative damage claims pursuant to Treas. Reg. §§ 301.7433-1 & 301.7430-1. (See IRM 1.4.51.3.1, Payment of Damages, below.)

1.4.51.3.1  (08-01-2007)
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 Financial Management Service (FMS), and the treatment of the two categories of awards differs slightly. (See paragraphs (17) and (18) below.)

  2. Processing Office. The processing office (Field Insolvency office 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 May File a Claim. The debtor, debtor's representative, or trustee may 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. "Willful" in this context means an act that was committed intentionally or knowingly. A willful violation occurs when the Service has received notice of a voluntary bankruptcy filing or of the court's granting of a discharge, and the Service does not respond timely to stop its collection activities.

  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.

    Note:

    If the Service does not receive notice of the bankruptcy, action to collect may not be a violation of the automatic stay or the discharge injunction.

  6. Timeframes. Generally for a claim to be considered, the Service must have failed to take appropriate action within the timeframes of the Bankruptcy Code Compliance Program (BCCP). Those timeframes 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 Timeframes. Regardless of general timeframes, 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 a revenue officer he is in bankruptcy, and the revenue officer 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. To be considered complete, claim request must:

    1. be submitted in writing;

    2. contain a narrative with a full explanation of what Service action or procedure created the grounds for filing the claim;

    3. provide pertinent debtor and bankruptcy case information (debtor name(s) and docket number);

    4. include documentation demonstrating actual economic damages incurred as a result of the violation (e.g., bank statements with charges for insufficient funds, levy notices, NFTLs);

    5. include an itemization of fees related to an attorney's efforts to correct the violation along with billing statements if attorney's fees are sought;

    6. be signed and dated by the claimant;

    7. be submitted under penalty of perjury; and

    8. be limited to actual economic damages and actual attorney's fees.

    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) or the discharge injunction (11 USC § 524). 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-43.)

  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.52.4 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 the Area Managers or the CIO Program 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 Exhibits 1.4.51-44 and 45 for 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 seek civil damages as provided for in IRC § 7433.

    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.5.3,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.5.3,Reimbursement of Damages and Costs, should be followed when the claim application for litigative damages and/or attorney's fees with the exception of the forms to be used. For litigative award funding FMS Forms 194, 196, and 197A should be used.

  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 FMS Forms 196 and 197 are used for the damages award, then FMS 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 FMS 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.

1.4.51.3.2  (08-01-2007)
Managing the Work Flow

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

  2. Court Closure Report. Managers should review the number of cases on the Court Closure Follow-up Report 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.11,Release of 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.

  3. Promoting Efficiency. 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 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 GS-12 advisors and GS-12 specialists 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

1.4.51.3.3  (08-01-2007)
Case Assignment Guide

  1. Case Grading. Insolvency managers are responsible for monitoring the assignment of case work to ensure cases are assigned to the appropriate case grade. The Case Assignment Guide (CAG) was developed to promote consistency in the assignment of graded Insolvency cases.

  2. Pre-Assignment. 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. Exhibits 1.4.51-33 and 34 contain the pre-assignment factors. 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. 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


    Exhibits 1.4.51-36, 37, and 38 describe difficulty indicators for each of the post-assignment factors.

  4. Post-Assignment Checklist. 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. Exhibits 1.4.51-39, 40, and 41 contain the checklists for post-assignment factors.

  5. Case Assignment Profile Matrix. Insolvency 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-42 contains a template to be used as a guide in preparing the matrix. A template should be prepared for each court jurisdiction.

  6. CAG Reports and Audit Trails. 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-21.)

    1. Case Assignment Listing Report. After IIP Process D has been completed, this report lists all cases assigned by the Automated CAG process. It provides managers with a summary of their inventory distribution and can assist in identifying inappropriately assigned cases. Managers must be alert for higher graded cases assigned to employees below the appropriate grade level. When case grade level and employee grade level become unbalanced, the manager must correct the imbalance promptly. Because the report can be sorted and printed by court jurisdiction or employee number, managers can readily identify needed inventory adjustments.

    2. Ungraded Case Listing Report. This report identifies cases that cannot be graded or assigned systemically because of missing data such as BODs. It must be printed every time Automated CAG is run since the data will not be available on subsequent reports following the next running of IIP Process D. This report should be worked daily; otherwise, cases may remain ungraded and unassigned leading to stay violations or lost revenue.

    3. Ungraded Case Follow-up Report. This cumulative report identifies cases that remain ungraded after initially being identified on the Ungraded Case Listing Report. Because this report captures unresolved cases previously shown on the Ungraded Case Listing Report, managers must review this report frequently to ensure corrective actions are taken on ungraded cases.

    4. Case Classification Report. This report identifies case dockets with special issues, such as non-petitioning spouse or specific court cases based on the case classification code. Classification codes have been developed by Collection Policy to identify specific case issues. ( See Exhibit 1.4.51-46.) This report can be useful to managers in identifying trends, such as prior bankruptcies or MFT 31 cases. The report can also target specific types of cases for program reviews.

  7. Level 1 Users. CAG has a Manager Only menu option whose access is limited to Level 1 users. 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 & 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. Case Grade Report. 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-6.)

  9. Grade Change Report. The Grade Change Report reflects the docket number, employee name and dates of cases where grades were changed. This report is useful as it reflects historical data relative to changes made to the grade of cases.

  10. Last History Entry. The "Last History Entry" field is accessed from the Manager Only menu to identify the last AIS history update for cases. This feature can be used when conducting case reviews to identify specific date ranges for case actions.

  11. Audit Feature. The "Audit" screen identifies specific actions taken on cases including the dates for adding the case to AIS, adding a TIN, transferring a case from one employee to another or between Field Insolvency and the CIO, or adding a dismissal or discharge date to the case.

1.4.51.3.4  (08-01-2007)
APOC

  1. Manager Menu. The Automated Proof of Claim (APOC) program systemically calculates and classifies liabilities to populate AIS fields so Forms B-10 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.2,Automated Proofs of Claim. This IRM 1.4.51 subsection deals with manager reports and APOC permissions, topics not covered in IRM 5.9.14.2. To access the APOC Manager Menu, the user must select option 5, "APOC" from the AIS/IIP Menu. From there the user selects option 3, Manager Menu. The two options available on the APOC Manager Menu are "Reports" and "User Access."

  2. Manager Reports. By choosing the "Reports" option on the APOC Manager Menu, the user can generate either employee or manager reports. The employee report selection replicates the employee reports available to all technicians. (See IRM 5.9.14.2.5,APOC Report Access.) Manager reports are the following:

    1. Stray User Accounts. This provides a list of employees with unlimited access to APOC, but who are not in the manager's employee table.

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

    3. User Account Report. This lists authorized APOC users and their permission levels.

  3. Assigning Permissions. APOC permissions are defined as:

    1. "Employee Access" which is needed to work in APOC and must be assigned before any other access can be granted;

    2. "Operator Access" which is limited only to users approved to initiate APOC; and

    3. "Manager Access" which allows the user access to the Manager Menu.

      Note:

      Only users with Manager Access will be able to add or change permissions in APOC.

  4. Granting Employee Access. The steps for a manager to assign a user Employee Access follow.

    1. Choose "Employees" from the menu.

    2. Select "Grant."

    3. Press ESC or Ctrl and E keys to access employee names.

    4. Arrow down to the appropriate name.

    5. Press Enter to add an "E" to the left hand side of the name.

    6. Hit Esc to exit the screen and systemically grant the Employee Access.

  5. Granting Operator Access. The steps to assign Operator Access follow.

    1. Choose "Operators" from the menu.

    2. Select "Grant."

    3. Press ESC or Ctrl and E keys to access employee names.

    4. Arrow down to the appropriate name.

    5. Type "O" to the left hand side of the name.

    6. Hit Esc to exit the screen and systemically grant the employee Operator Access.

  6. Granting Manager Access. The steps to assign Manager Access follow.

    1. Choose "Managers" from the menu.

    2. Select "Grant."

    3. Press ESC or Ctrl and E keys to access employee names.

    4. Arrow down to the appropriate name.

    5. Type "M" to the left hand side of the name.

    6. Hit Esc to exit the screen and systemically grant the employee Manager Access.

  7. Revoking APOC Access. The steps to revoke an APOC permission follow.

    1. Choose the type of access to be revoked.

    2. Select "Revoke."

    3. Press ESC or Ctrl and E keys to access employee names.

    4. Arrow down to the appropriate name.

    5. Press Enter to remove the "M," "O," or "E" from the left hand side of the name.

    6. Hit Esc to exit the screen and systemically revoke the designated access.

      Note:

      Once an access type has been revoked, the manager must use the "Grant" option to re-establish the permission.

1.4.51.4  (08-01-2007)
Initial Case Processing

  1. Insolvency Interface Program (IIP). The CIO must run AIS 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 workdays of receiving notification of new bankruptcies. (See IRM 5.9.5.6.1 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., ACS, Customer Service, or Accounts Management.) Adding new cases to AIS is a CIO duty. However, Field Insolvency specialists and advisors 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), status 26 (field revenue officer), and status 71 (OIC). The CIO works all status reports except 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. (See IRM 5.9.12.6.1,IIP Status Reports.)

    4. TC 520 closing codes in the 60 - 67 series and 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.

1.4.51.5  (08-01-2007)
Closed Cases

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

  2. Discharge Timeframe. Insolvency 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. Liens. If no exempt, excluded or abandoned assets exist, procedures must be followed to ensure liens on discharged periods are released within 30 calendar days of the Service's receipt of notice of discharge, or in the instance of individual Chapter 11 cases filed prior to BAPCPA, 30 calendar days from plan completion.

    Note:

    If an NFTL includes both dischargeable and non-dischargeable periods, a lien release should not be requested until the lien on the non-dischargeable period(s) has been satisfied or determined to be unenforceable.

  4. Liens and Postpetition Collection. 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.4.2,Addressing Lien Issues, for specific timeframes.) Once a determination is made not to pursue such assets, managers should ensure liens on discharged periods are released within 30 calendar days of that determination. Due to the timeframes involved, this may require requesting manual lien releases. (See the note in paragraph (3) above.)

  5. Automated Discharge System (ADS). 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.1(5),Case Class Code Y, 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.3,Timeframes 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 Operations Manager. IRM 5.9.18,Automated Discharge System, outlines procedures for running ADS and resolving DDRs.

  6. Exempt, Excluded, or Abandoned Property. A specialist or advisor valuates 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. the remaining liability on the dischargeable periods exceeds 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). Excluded property in the form of ERISA-style pension plans with anti-alienation clauses does not require the Service to have an NFTL on file before pursuing collection action. Insolvency specialists work these cases themselves usually eliminating the need to issue an OI. (See IRM 5.9.17.4.3,Insolvency Levy Procedures for Excluded Retirement Plans.)

1.4.51.6  (04-01-2006)
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.

1.4.51.6.1  (04-01-2006)
Proofs of Claim Filing

  1. Timely Claims. In most cases to be timely, a POC must be filed no later than 180 days (the government bar date) from the date of the bankruptcy filing. (See 11 USC § 502.) Claims prepared through APOC processing should be filed prior to the first meeting of creditors. A full discussion of timeframes for filing claims can be found in IRM 5.9.13.8,Court Timeframes,IRM 5.9.13.8.1,Bar Date - Governmental, and IRM 5.9.6.8.1,Bar Date.

  2. Bar Date Misrepresentations on AIS. The "Proof Required" field on AIS is not protected. Anyone with update capabilities can change the field from "Y" (a claim is required) to "N" (a claim is NOT required). Caseworkers can also alter the fictitious bar date field to the actual bar date. Inappropriate alteration of the fictitious 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.

1.4.51.6.2  (08-01-2007)
Adequate Protection

  1. Secured Assets. Where valid NFTLs have been filed and LEM 5.9.4 criteria 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 . (Adequate protection primarily concerns Chapter 11 and 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.)

    Note:

    Pursuit of adequate protection is possible in Chapter 13 cases, but requesting a lift of the stay is often a more appropriate tactic.

1.4.51.6.3  (08-01-2007)
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.4,First Meeting of Creditors.)

1.4.51.6.4  (08-01-2007)
Plan Review

  1. Significant Cases. Significant cases must be referred to Counsel regardless of chapter. (See IRM 5.9.4.15.3,Referrals on Significant Bankruptcy Case Issues.) 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.1(3),Chapter 13 Plan Documentation,IRM 5.9.5.4.1(4),Chapters 11 and 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 Insolvency specialist or advisor, 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 screen updated.

1.4.51.6.5  (08-01-2007)
Compliance Monitoring

  1. Multiyear Plans. Insolvency caseworkers should monitor postpetition 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 postpetition taxes. BAPCPA added provisions to address postpetition 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 postpetition return. (See 11 USC § 521(j)). A specific provision regarding postpetition compliance was added for Chapter 11 cases. In Chapter 11 cases filed on or after October 17, 2005, failure to file a postpetition 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 postpetition compliance in Chapter 12, (e.g., no provision in the Bankruptcy Code for filing postpetition claims), Insolvency should seek guidance from Counsel when appropriate. (See IRM 5.9.8.11,Postpetition/Preconfirmation BMF Monitoring,IRM 5.9.8.11.1,Postpetition Debts - Chapter 11 Individuals,IRM 5.9.9.9,Monitoring Compliance, and IRM 5.9.10.9,Postpetition Tax Liabilities.)

1.4.51.6.6  (08-01-2007)
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 Area fraud technical advisor or to Counsel when warranted. (See IRM 5.9.4.10,Bankruptcy Fraud,and IRM 5.9.17.7.1,The Fraud or Willful Evasion Exception.)

1.4.51.6.7  (08-01-2007)
Lien Refiles

  1. Lien Refile. Procedures outlining the issues involved and the reviews required for potential lien refiles are found in 5.9.5.8.2,Refiling of Liens,5.9.8.16.2,Monitoring the Plan and Reviewing for Lien Refile, and 5.9.17.4.2(13),Lien Refiles.

1.4.51.6.8  (08-01-2007)
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 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 Plan 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. Whenever a claim is amended, the AIS plan payment 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.

1.4.51.7  (08-01-2007)
Statute Controls

  1. Overview. Insolvency must protect assessment statute expiration dates (ASEDs) and collection statute expiration dates (CSEDs) either of which can be suspended by the filing of a bankruptcy. 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.2.1,BRA 94 and BAPCPA's Effect on Assessments, and Exhibit 5.9.6-1.

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

1.4.51.7.1  (08-01-2007)
ASED Protection

  1. Examination Controls. The automatic stay prevents the IRS from assessing non-agreed proposed deficiencies on prepetition periods. 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 examination" field on the AIS entity screen indicates "Y" when an examination is pending.

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

  3. Campus Examination-Related Processes. 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 SBSE Campus group for correspondence cases and with the lead of each Campus AUR group.

  4. Campus Monitoring. 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 prepetition 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.

  5. Campus Access to AIS. 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.

  6. Tax Equity and Fiscal Responsibility Act (TEFRA) Deficiencies. TEFRA applies to partnership examinations. 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 for guidance.

  7. Insolvency Responsibilities. Insolvency caseworkers are charged with:

    1. recognizing imminent ASEDs ( See Exhibit 1.4.51-9.);

    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.10,Trust Fund Considerations in Chapter 11.);

    4. coordinating with field Collection if appropriate (See 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.

  8. Trust Fund Recovery ASEDs. A TFRP ASED is generally three years from the presumptive date of filing or actual date of filing, whichever is later, for quarterly periods involving trust fund 941s, collected excise taxes, and annual 943s and 944s with trust fund tax.

  9. Limitation of Stay. Officers of corporations or limited liability companies (LLCs), or other parties with fiduciary responsibilities are not subject to the automatic stay in effect on the corporations or LLCs under bankruptcy protection.

  10. Timely Trust Fund Liability Review. Specialists' 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.7(10),Initial Review of Business Chapter 7 Asset Cases,IRM 5.9.8.4,Initial Case Review for Chapter 11, and IRM 5.9.9.4(8),TFRP Actions for Corporate Debtors.)

  11. Responsible Parties. 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 penalty. (See IRM 5.9.5.4.1(2)(g).)

  12. Managers' Responsibility. 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.

  13. Reporting Expired ASEDs. 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 specialists and advisors.

1.4.51.7.2  (08-01-2007)
CSED Protection

  1. 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.2,ASED/CSED, provides more information on CSED computations.

  2. Inappropriate Freezes. Caseworkers must monitor imminent CSEDs to ensure the automatic stay is still in effect. ( See Exhibit 1.4.51-28.) Managers should be aware of the potential for a bankruptcy freeze code to remain on a taxpayer's account when the taxpayer is no longer in bankruptcy. Procedures should include a review to identify these cases through use of the LTS potentially unreversed TC 520 report and the quarterly LAMS closed case listing.

  3. Partnerships. Collection may proceed against the assets of general partners while a partnership itself is under bankruptcy protection unless the partner against whom collection is being pursued is in personal bankruptcy. Should collection proceed against an individual partner, a TC 520 with closing code 84 is usually placed on the liabilities owed by the partnership. Because closing code 84 does not suspend the CSED, upon case closure a TC 550 must be manually input on the partnership's non-dischargeable modules to extend the CSED to the proper date.

  4. Imminent and Expired CSEDs. The procedures outlined in IRM sections 5.1.19.8 through 5.1.19.8.5 should be followed when addressing imminent or expired CSEDs under the bankruptcy freeze, substituting the words "Insolvency caseworker(s)" for "revenue officer(s)." Should a CSED expire without prior approval, a memo should be prepared and routed as follows:
    Field Insolvency - from group manager to Territory Manager, and, if warranted, to the Area Manager.
    Centralized Insolvency - from unit manager to Department Manager, and, if warranted, to the Operation Manager.

1.4.51.8  (04-01-2006)
Customer Satisfaction

  1. Introduction. The largest number of bankruptcies filed are consumer Chapter 7 No Asset cases. Chapter 7 discharges are usually issued within six months of the bankruptcies' commencements, and debtors might meet with their attorneys only twice during that time. Phone calls and correspondence result from taxpayers' misunderstandings of which taxes are discharged in Chapter 7 bankruptcies and which tax are not. The CIO is responsible for responding to these inquiries unless the issue is determined to be "complex." (See IRM 5.9.1.3(3),Complex Issues.) Generally, Field Insolvency is responsible for responding to phone calls and correspondence regarding cases assigned to its inventory and to any issues deemed to be complex.

1.4.51.8.1  (08-01-2007)
Insolvency's Duties

  1. Service. One of Insolvency's objectives is to serve debtors and their authorized representatives, insofar as is possible, after a bankruptcy is filed. The Insolvency manager oversees the equitable treatment of taxpayers and IRS compliance with all aspects of bankruptcy law involving the automatic stay, pursuit of collection from exempt, abandoned, or excluded property, and discharge of debt.

  2. Prompt Response. All legally authorized parties affected by a bankruptcy filing are entitled to prompt and confidential responses to inquiries, faxes, phone calls, referrals and correspondence. These responses must not approach guidance that might be construed as providing legal advice. IRM 21.3.3.2, defines what is considered correspondence, and IRM 21.3.3.3.4,Quality and Timely Responses, establishes that a final response to correspondence be initiated within 30 days of the IRS received date. IRM 5.9.19.5(4) requires phone messages be returned within one workday of receipt.

  3. Protection of Taxpayer Information. Insolvency managers must enforce the protection of taxpayer and return information when caseworkers deal with third parties involved in bankruptcy litigation. Insolvency employees should be familiar with the contents of the Bankruptcy Disclosure Handbook and understand what may be disclosed to trustees, attorneys, escrow companies, IRS Counsel, Department of Justice (DOJ) Tax Division Attorneys, local Assistant US Attorneys and their staffs. The Exhibit in IRM 5.9.19-1provides a chart outlining to whom taxpayer information may be disclosed when a taxpayer is in bankruptcy.

  4. IDRS Security. Managers must know IDRS security rules and understand the command codes used by their employees. ( See IRM 1.4.51.12.)

  5. Manual Refunds. Most manual refund requests are prepared by the CIO, although Field Insolvency remains responsible for preparing manual refund requests for cases assigned to its inventory. (See IRM 5.9.16.4,Manual Refunds.)

  6. Taxpayer Advocate. Managers must ensure the Taxpayer Advocate function receives responses to their inquiries by the date requested. (See IRM 5.9.3.7,Taxpayer Advocate Service (TAS).)

1.4.51.8.2  (08-01-2007)
Outreach

  1. Education. Insolvency provides technical and educational support to other IRS functions through its internal outreach programs. This support enables all IRS caseworkers to make appropriate collection or assessment determinations when a bankruptcy is open or after Insolvency has completed its work on a case.

  2. Effective Communication. Managers can maintain an effective dialogue with Area Counsel, US/ DOJ attorneys, United States Trustees, and Chapters 7 and 13 trustees by attending forums, conferences, and workshops on bankruptcy related issues.

  3. Practitioner Community. Managers may impact tax law compliance if they, with their staff and Counsel's assistance, attend bar association meetings. These venues can be used to acquaint practitioners with Insolvency's policies and procedures, particularly issues regarding unfiled tax returns. ( See IRM 1.4.51.6.8.)

1.4.51.9  (04-01-2006)
Employee Satisfaction

  1. Employee Reviews. At the beginning of each fiscal year, first and second line managers should jointly develop a review plan for their groups based on program priorities and caseworkers' individual developmental needs. Managers are to evaluate the performance of all employees under their supervision annually and midyear with subsequent follow-ups as appropriate. Midyear reviews should occur no later than seven months after the beginning of the rating period in accordance with the terms of the IRS - NTEU National Agreement, OPM regulations, and Performance Management guidelines. All reviews should rate each employee's performance against the performance plan's critical job elements (CJEs).

    Note:

    Managers can maximize efficiency if employee reviews are conducted simultaneously with reviews of the Insolvency group processes, operational reviews, or program reviews.

1.4.51.9.1  (04-01-2006)
Review Emphasis

  1. Performance Based. Review efforts should concentrate on employees who require technical development to improve performance. Consistent review of reports, including a sampling of cases, can identify areas where additional training or direction is required. Because AIS reports or custom designed reports list cases where actions may be needed, employees who perform at a high level of efficiency or employees with low inventories may have few cases identified on these reports. The manager should focus on the number of cases each employee receives to ensure work is equitably distributed.

  2. Review Documentation. Review results must be adequately documented, highlighting good performance as well as job elements requiring improvement.

  3. Follow-up Reviews. Follow-up reviews of employees, operations, or programs should be scheduled and conducted as needed and shared with the employee according to the terms of the NTEU contract.

  4. Performance Appraisal. Managers should expand annual summary performance appraisal (Form 6850BU) discussions with employees to include performance plans for the upcoming year. This is a logical time to examine individual competencies, develop job training plans, and career management plans.

  5. Identifying Training Needs. Throughout the review process managers should be attuned to individual or group training needs concerning technical abilities, (e.g., knowledge of tax law and bankruptcy law), or skills (e.g., communication, organizational awareness, and automation).

  6. Spotting Barriers. Managers must be able to recognize procedural or automated systemic problems that create barriers to the accomplishment of work. Suggestions to resolve issues of a national scope should be elevated via Form 5391 through Insolvency management channels to Collection Policy.

1.4.51.9.2  (08-01-2007)
Inventory Levels

  1. Staffing. Because the number of bankruptcy filings varies from week to week, managers should review the size of their inventories and prioritize casework frequently depending on the staffing available. Employee vacancies and long term absences may require managers to reassign inventories manually to maintain a balanced workload.

    Note:

    To avoid claims for damages, managing inventory by setting and releasing litigation freezes timely takes precedence over making claim determinations before the first meeting of creditors.

  2. AIS and Custom Reports. Improving the caseworker's skills in managing inventory and prioritizing case work are the Insolvency manager's most significant responsibilities. Reports, whether standard AIS reports or custom reports, may be generated and worked to process Insolvency inventory efficiently and effectively. Other functions of the Service also provide reports that must be worked by Insolvency because of the specialized nature of bankruptcy processing.

    Note:

    These reports are tools for effective workload management. They are not intended to replace a caseworker's informed judgment guiding case actions.

1.4.51.10  (08-01-2007)
Business Results - Quantity

  1. Use of Reports. Reports are tools for managing inventory. Working most AIS reports is optional and up to the discretion of Territory or group management. But working the following AIS reports or their equivalents (see paragraph (2) below) is mandatory:

    • Bar date report (Field Insolvency only) ( See Exhibit 1.4.51-2.)

    • Aged case report ( See Exhibit 1.4.51-22.)

    • LAMS reports for Not Found on AIS( See Exhibit 1.4.51-23.) and Closed Case ( See Exhibit 1.4.51-24.)

    • LTS reports ( See Exhibit 1.4.51-25.)

    • Court closure follow-up report ( See Exhibit 1.4.51-19.)

    • GUF report (unpostables) ( See Exhibit 1.4.51-26.)

    • Non master file report ( See Exhibit 1.4.51-27.)

    • Potential manual lien release report (CIO only) ( See Exhibit 1.4.51-32.)

    Field Insolvency and CIO managers must establish controls to verify these reports are worked timely.

  2. Equivalent Custom Reports. With Territory Managers' or Department Managers' approval, AIS reports may be replaced with reports designed with software products, such as MyEureka, that are compatible with the AIS operating system. To be approved the new reports must serve the purposes of the AIS reports and increase efficiency.

  3. Documentation. As each case on a report is worked, the caseworker should document the AIS history if action is taken. No AIS documentation is required if no action is taken on an account. Each case on a report should be checked off when action has been completed and the history is documented (if required).

  4. Retention. 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

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

1.4.51.11  (08-01-2007)
Business Results - Quality

  1. Technical Improvement. Methods of monitoring the quality of work to foster performance improvement include:

    • random spot checks of work

    • employee evaluative reviews

    • operational reviews

    • program reviews

  2. Random Checks. Managers can check work at random as they move about the office or when reports indicate inspection of work may be warranted. Random checks of proofs of claim quality, plan review, and discharge determination reviews keep the manager apprised of the quality and timeliness of work. They may indicate when more in-depth reviews are needed.

  3. Following Manual Procedures. Managers should look for compliance with IRM 5.9, Collection, Bankruptcy, procedures by focusing on the effectiveness of actions taken by caseworkers relative to the following:

    1. Review of bankruptcy plans and documentation of specific plan provisions in the AIS history ;

    2. Classification of periods and dollar calculations on proofs of claim;

    3. Calculating unassessed periods on manually prepared claims based on accurate taxpayer information;

    4. Responding to inquiries posed by debtors or their representatives to avoid needless litigation;

    5. Determining which taxes should be adjusted as the result of a bankruptcy discharge;

    6. Monitoring compliance with the terms of a bankruptcy plan;

    7. Monitoring timely payment and filing responsibilities over the life of Chapter 11 and 12 plans;

    8. Observing the quality of verbal communication with taxpayers and their representatives on the phone, during interviews in the office, at § 341 meetings, during court testimony, while questioning a taxpayer about the collection of postpetition tax and determining the cause of failure to comply;

    9. Reviewing the quality of written communication by reading AIS histories and annotations in Chapter 11 paper case files;

    10. Reviewing referrals to Counsel or the US Attorney;

    11. Reading written responses to inquiries from Collection, Examination, customer assistance, Taxpayer Advocate, W & I, TEGE, or LMSB;

    12. Monitoring the quality of case decisions when determining the next action to be taken in matters concerning noncompliance or fraud; and

    13. Monitoring the timeliness of actions involving objections to confirmation, classification of tax on the POC, stipulations involving adequate protection, accepted offers in compromise and bankruptcy litigation, determinations involving the dismissal or conversion of a case, or identification of potential 6672 trust fund recovery penalty liabilities.

1.4.51.12  (08-01-2007)
Insolvency and IDRS

  1. The Role of IDRS in Insolvency. Examples of the tasks Insolvency performs on the Integrated Data Retrieval System (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 IRS’s master file);

    4. accessing account information to prepare adjustment requests;

    5. inputting or reversing bankruptcy freezes; and

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

  2. Security Groups. Whenever practical, Insolvency groups should not be included with IDRS data security work groups from other functions within SBSE (for example, Technical Advisory or field Collection). 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.

  3. IDRS On-line Adjustments. Insolvency management must ensure required security measures are in place regarding on-line IDRS account adjustments. Questions regarding IDRS security may be directed to the SBSE IDRS Security Issue Committee member whose name and number are shown on http://mass.web.irs.gov/IDRS/IDRSSecurityIssuesCommittee.asp.

  4. Command Code Profiles. Insolvency managers should monitor command code usage by all members of their group. Suggested profiles for Insolvency employees are listed below.

    Clerical Staff (303, 318)(used for running IIP, ADS, and resolving all correspondence reports)
    BMFOL IMFOB NAMES TXMOD BMFPG
    IMFOL REQ77 TRDBV INOLE SFDISP
    RTVUE INTST SINOF EMFOL IRPTR
    SINON ENMOD MFREQ COMPA FRM77
    MFTRA SUMRY IADIS NAMEE TERUP
    ACTON AMDIS  

    Note:

    The command codes listed for the clerical staff must be in their profiles for the corresponding programs to work properly. This is true for anyone running IIP or ADS.

    Specialists, Advisors, (GS Series 1101, 1169) and Technicians (GS Series 592)
    ACTON COMPA INTST SINON UPDIS
    SINOF INOLE ENMOD IRPTR STAUP
    UPTIN SFDISP UPCAS ESTAB MFREQ
    SUMRY BRTVU UNLCE AMDIS FRM77
    MFTRA TERUP CFINQ SUPOL BMFOL
    IADIS NAMEE TSIGN TRDBV REQ77
    IMFOB NAMES TXMOD EMFOL FRM49
    RTVUE IMFOL      
    Technicians (GS Series 592)
    ADC24 REQ54 ADD24 ENREQ INCHG
    ADJ54 DRT24 BNCHG IAREV IAORG

    Note:

    Per local practice some Field Insolvency offices may opt to include command codes that deal with account adjustments other than bankruptcy freezes in the specialists' and advisors profiles. Assigned command codes must reflect the user's duties.

  5. Sensitive Command Codes. 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 these command codes in their personal profiles.
    ADC24 DRT48 ADC34 FRM34 ADD24
    INCHG ADD34 REFAP ADD48 RFUND
    ADJ54 URAPL AMCLS URREF BNCHG
    XSAPL DRT24 XSREF  

  6. IDRS COMMAND CODES AND USAGE. 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 SUPOL
    Delete Your Transactions, Same Day Input TXMOD TERUP
    Dummy Account SUMRY MFREQ
    Entity Information and/or Changes ENMOD, INOLET ENREQ, INCHG,BNCHG
    Exam Issues AMDISA  
    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
     
    Unpostables TXMOD UPTIN, UPCAS, UPDIS
    Display Taxpayer Name, Address, Spouse Cross Reference Data, Filing Requirements, DOB, BOD, etc. INOLE  
    Request IRP Transcripts for Specific TIN and Tax Year IRPTR  
    EIN Research INOLET NAMEE
    Online Display of Tax Return Information RTVUE, BRTVU  
    Research Non-Filer Cases. Contains IRP Data for Potential TDI Cases SUPOL  
    Employee Master File Online EMFOL  
    Update the Status of Modules that Are or Have Been Bal Due Modules STAUP  
    Research for Trust Fund Recovery Penalty Assessment UNLCE  
    Enter IDRS SINON  
    Exit IDRS SINOF  
    Display All Command Codes in Your Profile SFDISP  

    Additional research sources include Document 6209, IRS Processing Codes and Information, LEM 25.10.3, IDRS Security Handbook, IRM 2.3, IDRS Terminal Responses, and IRM 2.4, IDRS Terminal Input.

1.4.51.13  (08-01-2007)
Insolvency Territory and Department Manager Duties and Responsibilities

  1. Introduction. Effective leaders use coaching to transfer leadership skills to front line managers to motivate, develop, instruct, and collaborate with individuals and teams. They maximize current performance and address the need for long term development while maintaining a supportive working environment. A coaching model focuses on collaborative and supportive coaching behaviors. More information on developing and increasing effective coaching skills can be found by accessing the Enterprise Learning Management System (ELMS), selecting the "Catalog" tab, and searching under key words "leadership" and "coaching."

1.4.51.13.1  (08-01-2007)
Employee Satisfaction

  1. Modeling Behaviors. To help managers model effective leadership behaviors, the IRS developed the "Transition to Leadership" course outlined on ELMS. The course focuses on six key front line manager competencies:

    • Teamwork

    • Adaptability

    • Communication

    • Partnering

    • Problem Solving

    • Technical Credibility

    Managers are responsible for incorporating these messages into their daily interactions with employees.

  2. Tools. The training tools provide skill-based modules and exercises for use in either one-on-one or group settings. Also included is guidance on including these messages during routine activities such as CPEs, staff meetings, and management training conferences.

1.4.51.13.2  (04-01-2006)
Customer Satisfaction

  1. Involving Customers. Field Insolvency and the CIO manage their own case inventories while delivering specialized advisory service to all operating divisions of the IRS. The Territory/Department Managers should be looking for opportunities to educate external and internal customers. Examples of activities that contribute to maintaining good relations and providing quality service are:

    1. participating in Area/Operation Manager staff meetings;

    2. networking with Collection mid-level managers to facilitate processing of courtesy investigations, advisory opinions, and other coordinated efforts;

    3. Field Insolvency's and the Centralized Insolvency Operation's working together toward common goals;

    4. attending Counsel forums dealing with Insolvency issues and workload management;

    5. making contacts with non-Insolvency Campus managers to ensure work flows smoothly and Campus employees are adequately educated about Insolvency's goals and objectives;

    6. giving presentations and fielding questions at enrolled agent forums;

    7. participating in bar association meetings;

    8. participating in trustee association meetings; and

    9. participating in panel discussions or seminars sponsored or planned by SB/SE TEC and W & I Spec.

1.4.51.13.3  (04-01-2006)
Business Results

  1. Process Improvements. Successful program management dictates a review of Insolvency's processes to determine if better ways can be found to perform the job. Both operational reviews and program reviews can be effective methods of recognizing procedural or systemic problems as well as identifying means of improvement.

  2. Mandatory Reviews. Insolvency second-level managers must perform an operational review of each subordinate manager at least once each year along with midyear and annual reviews of support staff which may include a secretary, management assistant, or analyst.

    1. Reviews must be documented by memorandums and include significant accomplishments and areas where performance can be improved.

    2. Directions for improvement must be given, with follow-up to be made after a reasonable time to see if directions have been carried out.

      Note:

      This review provides a major portion of the manager's annual performance evaluation.

    3. The subordinate manager must be provided with, at minimum, a midyear review due no later than seven months into the fiscal year. The purpose of the review is to assess the appropriateness of the current operation plan.

  3. Key Review Areas. Review activity should concentrate on three key areas:

    • employee satisfaction

    • customer satisfaction

    • business results

  4. EPFs. The Territory/Department Manager should review employee performance folders (EPFs) concentrating on the depth and scope of employee reviews, evaluations, individual development and team-building efforts to:

    1. ensure the manager has discussed the findings with the employee within a reasonable amount of time, normally within 30 days of finding or the period of time covered by the IRS - NTEU National Agreement;

    2. determine if employees have discussed and signed for all performance plans, CJEs, and position descriptions outlining their duties and responsibilities within 30 days of the beginning of the rating period;

    3. recognize any Records of Tax Enforcement Results (see IRM 1.5.2, Managing Statistics in a Balanced Measurement System); and

    4. confirm performance feedback is relevant to the employee's critical job elements and position description.

      Note:

      Balanced written evaluative feedback documents the employee's contribution to the workgroup's success, customer satisfaction, and Insolvency program business results.

  5. Management Skills. Workload management skills and quality control must be analyzed to:

    1. check for accomplishments of the Area/Operations and Territory/Department program plan goals and document the progress toward completing annual responsibilities and commitments - the what and how of the manager's contribution to Insolvency program goals and objectives;

    2. review the methods of the group's internal and external communications by reading group meeting minutes and any other records of group actions within the office and area and comment on communications within the unit and between the employees and the manager;

    3. review employee survey issues and results completed in the current year and ensure action plans are prepared and issues are handled appropriately;

    4. review the accomplishment of previous action items;

    5. sample reviews of work in major program areas; and

    6. document if mandatory reports are worked timely and any reports that have been worked are retained for the appropriate amount of time.

Exhibit 1.4.51-1  (04-01-2006)
Sample Annual/Midyear Review Schedule

Group Review Schedule
  SSN 6850 BU Employee Due Midyear
September 0 AA,BB Oct 31 EE, FF
October 1   Jan 31 GG,HH,11
November 2 CC Jan 31  
December 3 DD Jan 31 JJ,KK
January 4   Apr 30 LL,MM
February 5 EE,FF Apr 30  
March 6 GG,HH,II Apr 30  
April 7   Jul 31 AA,BB
May 8 JJ,KK Jul 31  
June 9 LL,MM Jul 31 CC
July       DD
August        

Note:

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

Exhibit 1.4.51-2  (08-01-2007)
Guide for Bar Date Follow-up (Field Insolvency)

Introduction. Use of the Bar Date Report or an equivalent custom report is mandatory for Field Insolvency specialists and advisers. This AIS 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 "Y" appears in the "Proof Required" field on the AIS entity screen and claim data have not been entered on the proof of claim screen(s).

Accessing the AIS Report:


1) On the AIS Main Menu, select 15 (Reports).
2) On the AIS Reports menu, choose 9 (Bar Date Report).
3) Enter 1 for employee, 2 for chapter, or 3 for "all cases."
4) 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.
5) Enter ending date. Generally use 90 days into future.

Format Options. The report can be sorted by individual employee, by chapter, or by "all cases." Sorting by caseworker best identifies case load management issues.

Contents of Report. The Bar Date Report provides the taxpayer name, primary TIN, secondary TIN, docket number, bar date, and the date for the first meeting of creditors.

Frequency of Use by Caseworker. This list must be generated and checked by caseworkers monthly 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 Period. 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.

Fictitious Bar Dates. Cases are listed in ascending chronological order by a "fictitious" bar date. The true bar date for governmental creditors to file a claim is 180 days after the commencement of the case. The fictitious bar date hits at midpoint in the government’s 180 day claim filing period (90 days from the petition date).

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 (the majority of cases have 90 days from petition date and other cases have 180 days from petition date).

Note:

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

Monitoring. Cases falling beyond the 90-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 90 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:


1) preparing/printing POC;
2) entering conversion to 7 No Asset data to AIS screen;
3) entering NL in the closure field with a date when a case is determined to be not liable;
4) closing a case on AIS as dismissed; or
5) manually changing "Proof Required" field from "Y" to "N."

AIS Documentation. Managers should be conservative in requiring documentation from caseworkers on an ongoing basis. Highlighting a case with a bar date beyond 90 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 "Y" indicating a claim is required, yet an admin claim (6338A) has been filed. The caseworker should change the "Y" to "N" if no taxes are due at the time the debtor filed bankruptcy. Leaving the "Y" reduces efficiency if a caseworker continues to check on a case where the determination has already been made.

Exhibit 1.4.51-3  (08-01-2007)
Guide for the Plan Monitoring Review Report (Field Insolvency)

Overview. The Plan Monitoring Review Report or equivalent custom report provides a list of delinquent payments by extracting data from the AIS Payment Monitoring Screen. The information it provides is only as accurate as the information from which it is compiled. A plan must be added into the payment monitoring screen stating the payment amount, the due date of the first payment, payment frequency, and the review date. If a plan is amended, the plan monitoring data must be amended.

Accessing the AIS Report:


1) From the AIS Main Menu, select 6 (Payment Monitoring).
2) From the Payment Monitoring menu, choose 14 (Plan Reports).
3) On Plan Monitoring Reports menu, enter 11 (Review Date Report).
4) Choose either Y (Yes) or N (No) when asked if a laser printer will be used.
5) Select a review date less than the current date in the MMDDYYYY format. Using the current date generates a list of all cases where a plan has been established with a review date prior to today.
6) The print menu will appear for printer selection.

Contents of Report. The Plan Monitoring Review Report provides a listing of delinquent payments from the review date set by the user. This date needs to be updated each month when a new payment is received to remain accurate. The report lists the following:
• Debtor
• Chapter
• Effective date
• Beginning dollar amount
• Total amount paid
• Current balance
• Payment amount
• Payment frequency
• Due date of next payment

Chapters Affected. This report may be used in all chapters except Chapter 7. But it is most effective in Chapter 11 cases where the plan payment date is established for a specific date each month.

Exhibit 1.4.51-4  (08-01-2007)
Guide for Diagnostic Q Reports - Type C or S (Field Insolvency)

Introduction. Campus (non-Insolvency) functions are charged with monitoring all assessments, and diagnostic transcripts are the tools they use to locate modules requiring attention. The SBSE Campus with responsibility for supporting end-users in Collection functions reviews all transcripts with open control bases.

Type C Transcripts. Type C transcripts generate when the CSED has passed, and the program cannot systemically resolve the module because of an open freeze. For Insolvency those are unreversed TC 520s with closing codes 60-67 and 81 or 83-89.

Type S Transcripts. Type S transcripts involve TINs with imminent CSEDs and multiple modules on one TIN with one or more expired CSEDs.

Receiving the Diagnostic Q Reports. Field Insolvency groups cannot access the report directly, but Insolvency managers should know who the Campus user support contacts are so changes in Collection group addresses or locations can be sent to the Campus for update. The Campus Collection Liaison or Bankruptcy Collection Liaison fills that role if the Campus has allotted staffing to that duty.

Campus (Non-Insolvency) Responsibilities. IRM 5.19.10.6.1,General Procedures for Diagnostic Q Transcripts, mandates the Campus review the systemically generated transcripts and route them to the appropriate Campus group or the appropriate Collection Area work group. Insolvency will only receive copies of these reports if IDRS shows an open control base for an Insolvency employee.

Format Options. This report is pre-formatted by IDRS programmers.

Contents of Report. The transcript provides the information contained in ENMOD and TXMODA. The open control is listed at the top by Area Office (AO) assignment number and universal locator code (ULC) (also noted as LC on IMFOLT or BMFOLT).

Range of Uses. The transcripts are generated for Chapters 7, 11, 12, and 13 to identify processing problems with the input of TC 521s to reverse TC 520s. In many cases the CSED is suspended by the automatic stay involved in the bankruptcy litigation. In some instances the transcripts bring to the caseworker's attention those modules where a CSED review was not conducted when the claim was prepared.

Note:

Effective use of other reports and transcripts (for example, LTS, Aged Case Report) will prevent the generation of Diagnostic Q transcripts.

Effect of Closing Codes. In Chapters 11, 12, and 13, modules involving postpetition periods are generated by the diagnostic process depending on the TC 520 closing codes used by the work group. Closing codes that freeze the entity prove to be the type of closing codes that result in the generation of a large number of Diagnostic Q transcripts.

Exhibit 1.4.51-5  (08-01-2007)
Guide for Pre-Case Assignment Guide (CAG) Reports (Field Insolvency)

Purpose of Report. The Pre-Case Assignment Report for CAG provides a listing of all chapters of bankruptcy, assignment for benefit of creditor cases, and receiverships in chapter/case type order and grade order with a grouping of total dollars owing based on the POC total. The manager can determine the number of cases by grade assigned to the work group. The report can be used to balance inventory among group members.

Grade Levels. Asset cases are graded according to the CAG pre-assignment criteria by chapter (7A, 11, 13), first line name, unpaid liability (according to POC combined liability—not LAMS or master file), grade (except for GS - 9 Chapter 13 cases since the listing would be too cumbersome) and Business Operating Division (BOD) code W, SB, LM, or TE.

Accessing the AIS Report:


1) From the AIS Main Menu, select 19 (Additional AIS Options).
2) From the Additional AIS Options menu, choose 6 (Case Assignment Guide).
3) On the Pre-CAG Reports menu, enter 7.
4) Select 1 to generate a listing of "all cases" in the group.
5) Select 2 to generate a one page listing of the CAG Distribution with a subtotal of cases by type and grade level.

Format Options. This report, which cannot be re-formatted, gives a snapshot of total inventory for the day it is run.

Contents of Report. The following two paragraphs explain data contained in each of the two options available.

Option 1, Case Assignment Guide Listing. This report provides the district number of the database, page number, processing site (state and district number, e.g. California 77, eventually your territory number plus twenty, e.g. 21 through 36). The date the report is generated is included in the title. The listing has the chapter heading. Within the chapter heading GS-09, GS-11, and GS-12 taxpayers are itemized in groupings by grade level. Within the grade level taxpayer names appear in alpha order by liability (drawn from the combined total of the POC data), caseworker assignment number, and docket number.

Option 2, Case Assignment Guide Distribution. This option displays the district number of the database and the run date. It is a one page overview in table form of all cases sorted by grade and chapter, totaling each type of case and giving total cases by grade and by chapter.

Note:

Option 2 assists the manager in determining the average inventory level of a GS-09, 11, or 12 within the group by taking the total number of GS-09 cases or GS-11 or 12 cases and dividing the category by the number of GS-09, 11, or 12 specialists or advisors within the group.

Frequency of Use by Manager. Managers should access these reports as needed to verify employee inventories are commensurate with their grade and to avoid the assignment of cases above grade level. The CAG Manager’s Only menu provides detailed information concerning the percentage of casework by grade assigned to each employee at the processing site. The report should be run by the manager, his assignee, or a group IIP or ADS coordinator.

Range of Uses. These reports are used to monitor appropriateness of case distribution by grade for all chapters.

Exhibit 1.4.51-6  (08-01-2007)
Guide for Case Assignment Guide (CAG) Case Grade Manager Report (Field Insolvency)

Purpose of Report. This report gives a synopsis of individual employee inventories and the percentage of work that is graded 7, 9, 11, and 12 as well as the percentage of ungraded work.

Accessing the AIS Report:


1) From the AIS Main Menu, choose 19 (Additional AIS Options).
2) From the Additional AIS Options menu, select 6 (Case Assignment Guide).
3) On the CAG Reports menu, enter 6 (Manager’s Only Menu).

Format Options. Option 2 (Case Grade Report) is a pre-formatted overview report. Option 3 (Grade Change Report) provides changes within a range of dates set by the manager.

Contents of Report. The Case Grade Report gives the group number, manager name, employee name and number, ungraded (UG) percentage, GS-7, GS-9, GS-11, and GS-12 percentages, and inventory allocation percentage for each employee in the group.

Note:

The Case Grade Report compiles inventory profile information to ensure employees have appropriately graded work.


The Grade Change Report shows the date range covered, docket number, action involved (e.g. ungraded to GS-7 or from GS-9 to GS-11), date manager changed grade, and employee name. It provides a record of the cases that have been re-graded.

Range of Uses. This report is for all chapters.

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.


More Internal Revenue Manual