Skip to main content
 

5.14.1 Securing Installment Agreements (Payment Plans)

Manual Transmittal

July 20, 2026

Purpose

(1) This transmits revised IRM 5.14.1, Installment Agreements, Securing Installment Agreements (Payment Plans)

Material Changes

(1) Refer to the table below for details on the list of material changes in this IRM.

IRM Subsection Description of Change
IRM 5.14.1.1.1 Added to the background statement in paragraph (1) to reference payment plans (also known as installment agreements), which are arrangements that allow taxpayers to pay their tax liabilities over time.
IRM 5.14.1.1.1 Added in paragraph (2) that taxpayers must verify both filing and payment compliance; specified requirements for individual and business taxpayers; and established that revenue officers must assess whether requests are intended to delay collection action.
IRM 5.14.1.1.3 Revised the internal control from “Responsibilities” to “Roles and Responsibilities” to align with IRM 1.11.2.2.4.1, Required Internal Control Components.
IRM 5.14.1.1.3 Revised paragraph (3) to rename second level management officials in Field Collection from “territory manager” to “field compliance manager.”
IRM 5.14.1.1.4 Restructured content into a table format to align with the IRM style guide.
IRM 5.14.1.1.4 Revised the table for program reviews to correct the second level management officials in Field Collection from “territory manager” to “field compliance manager.”
IRM 5.14.1.1.5 Revised paragraph (3) to update the reference from a non-Streamlined Installment Agreement (NSIA) to the newly defined non-Simple Installment Agreement (NSIA).
IRM 5.14.1.1.5 Added language to paragraph (3) to define ICS-DSS as the cloud-based digital storage platform within ICS and clarified that Guaranteed IA, Simple Payment Plan, and Simple Payment Plan (Business Trust Fund) case dispositions do not require managerial approval.
IRM 5.14.1.1.6 Clarified definitions of delinquent taxes, and current federal tax obligations to improve guidance and compliance procedures.
IRM 5.14.1.1.6 Added definitions for BMF non-Trust Fund and Unpaid Balance of Assessment (UBA).
IRM 5.14.1.1.7 Added acronyms.
IRM 5.14.1.2 Revised subsection title to include Payment Plans.
IRM 5.14.1.2 Revised paragraphs (2) through (4) to replace guidance and references to Streamlined IA and Express IA with the new Simple Payment Plan process.
IRM 5.14.1.2 Added VanillaDirect Pay option to paragraph (6)d, allowing taxpayers to convert cash into electronic tax payments at participating retail locations.
IRM 5.14.1.2 Revised the table in paragraph (10) to update the columns for ‘Current User Fee Rates (through July 4, 2026)’ and ‘Updated User Fee Rates (Effective July 5, 2026)’ by incorporating the two new user fee rates for online agreements.
IRM 5.14.1.3 Revised subsection title to include Payment Plan.
IRM 5.14.1.3 Revised paragraph (5) to add an If/Then table that identifies the information a taxpayer must provide for an account to qualify for pending IA status. Added a condition requiring the taxpayer to provide a completed CIS, when required, for the IA request to be considered pending.
IRM 5.14.1.3 Added paragraph (6) to include an If/Then table that identifies when an account does not qualify for pending IA status. Added a Note clarifying that an unreversed TC 971 AC 043, without account history confirming the taxpayer submitted a processable IA request, does not establish pending IA status and directing employees to attempt taxpayer contact before reversing the TC 971 AC 043.
IRM 5.14.1.3 Revised the table in paragraph (14) to incorporate examples that clarify when a request does and does not result in identification of a pending IA.
IRM 5.14.1.4 Revised the subsection title to add “Payment Plan” next to “Installment Agreement”, clarifying that the terms refer to the same thing.
IRM 5.14.1.4 Revised content throughout to replace references to Streamlined and Express IAs with the new Simpler procedural process.
IRM 5.14.1.4 Added paragraph (4)f to establish pre-IAR rejection controls, requiring verification of pending installment agreement criteria and TC 971 AC 043, documentation of the proposed payment amount and due date, preparation of Form 12233, managerial concurrence, and continued suspension of collection action until the taxpayer is notified of the decision and appeal rights.
IRM 5.14.1.4.2 Clarified paragraph (2) to state that IAT may assist with compliance checks during initial analysis, but the RO must review the case and make the final compliance determination.
IRM 5.14.1.4.5 Revised paragraphs (1) through (4) to update pre-assessed module processing by replacing paper CCP routing with digitizing and uploading case files to ICS-DSS and using secure email routing to CCP, including updated Option A and Option B procedures.
IRM 5.14.1.6 Revised paragraph (12) to update campus routing procedures by requiring IAs and Form 900 to be digitized and uploaded to ICS-DSS for retention, instead of forwarding copies to CCP.
Exhibit 5.14.1-5 Updated the IA table to replace references to Streamlined and Express IAs with Simple Payment Plan and Simple Payment Plan (Business Trust Fund), including the conditions under which the IRS generally approves these agreements.
Exhibit 5.14.1-5 Revised the exhibit by replacing asterisks with numbered footnotes and placing the exception language in separate tables to clarify the criteria for Simple Payment Plan (Business Trust Fund) and IBTF IA exception.
Exhibit 5.14.1-5 Replaced bullet format pending IA requirements with a table that lists each requirement and explains the conditions needed to identify an account as pending IA.
Throughout Removed naked links to internal web addresses to reflect the new IRS structure.
Throughout Updated hyperlinks and reference points, and clarified information to assist and support the end-user. Used Artificial Intelligence (AI) tools for editorial plain language revisions, punctuation, and grammar corrections. All content was reviewed and approved.

Effect on Other Documents

This material supersedes IRM 5.14.1 dated July 02, 2024. This IRM incorporates the following Interim Guidance Memoranda: SBSE-05-0525-0030, Interim Guidance for Field Collection on New Criteria for Processing Pending Installment Agreement (IA) Requests, issued May 21, 2025; SBSE-05-0325-0008, Interim Guidance for Field Collection on Simple Payment Plans (Formerly Streamlined Installment Agreements) for IMF Accounts with Balances Up to $50,000, issued March 3, 2025; SBSE-05-0126-0008, Revised Interim Guidance for Field Collection on new Simple Payment Plans for Business Master File (BMF) taxpayers, issued January 30, 2026; and SBSE-05-0326-0022, Interim Guidance for Revenue Officers on the Use of Integrated Collection Systems (ICS) Digital Storage Solution (DSS) and the Transition from Paper to Digital Case Files, issued March 4, 2026.

Audience

Small Business Self-Employed (SB/SE) Field, TAS and Appeals employees

Effective Date

(07-20-2026)

Thomas Kramer
Director, Collection Policy
Small Business/Self-Employed

Program Scope and Objectives

  1. Purpose: This section provides an overview of the installment agreement (IA), also referred to as a payment plan, process and the considerations for accepting or rejecting an IA request. Although a variety of topics are addressed, this section does not provide comprehensive guidance on all aspects. As you use this section, remain alert for references to related IRMs and internal resources, and consult them as needed to ensure the case action taken is procedurally correct, fully documented, and consistent with the facts of the case.

  2. By following the guidance in this IRM, you will be able to:

    1. Identify taxpayer rights with respect to IAs.

    2. Explain pending IA criteria and when to input pending status to IDRS.

    3. Discuss considerations for accepting, rejecting, or perfecting IA requests.

    4. Describe compliance requirements, financial analysis considerations, and Notice of Federal Tax Lien considerations when granting IAs.

    5. Establish processing procedures for completed IAs.

    6. Discuss restrictions on levies during the IA process.

  3. Audience: These procedures and guidelines primarily apply to IRS Field Collection revenue officers and group managers.

  4. Policy Owner: The Director, Collection Policy, is the policy owner of this IRM. Collection Policy operates within the Small Business/Self-Employed (SB/SE) Division, Collection.

  5. Program Owner: Collection Policy, Case Resolution Alternatives (CRA), is the program owner of this IRM.

  6. Primary Stakeholders:

    • Field Collection

    • Independent Administrative Review (IAR)

    • Insolvency

    • Independent Office of Appeals (Appeals)

    • Taxpayer Advocate Service (TAS)

  7. Program Goals: IAs can be a viable case resolution for many delinquent accounts. By following the guidance in this IRM section, employees can protect taxpayer rights, properly identify and process pending IA requests, and make accurate acceptance and rejection determinations based on the facts and circumstances of each case. Employees must also ensure the government’s interest is protected, use the least intrusive collection action that is appropriate, and consider whether another case resolution alternative is more appropriate when an IA will not resolve the liability.

Background

  1. IAs (also referred to as payment plans) are arrangements by which the Internal Revenue Service allows taxpayers to pay liabilities over time. Taxpayers should be encouraged to pay the liability in full to avoid the costs of an IA, which include a user fee, continued accrual of penalties and interest, and the possible filing of a Notice of Federal Tax Lien (NFTL). If full payment cannot be achieved by the Collection Statute Expiration Date (CSED) and the taxpayer has some ability to pay, a Partial Payment Installment Agreement (PPIA) may be granted. During the course of the agreement, penalties and interest continue to accrue. Generally, no levy may be made on taxpayer accounts during any of the following periods:

    • while a processable IA request is pending, (i.e., after the IRS accepts the request for processing),

    • while an IA is in effect,

    • for 30 days after rejection of an IA request,

    • for 30 days after termination of an IA, or

    • while Appeals is considering a timely appeal of a rejection, default, or termination.

  2. Before granting an agreement, taxpayers must establish filing and payment compliance. Individual taxpayers must file all required returns and must be current with payment requirements (e.g., estimated (ES) tax payments, or federal income tax withholding). Business taxpayers with employees must file all required returns and must be current with payment requirements (e.g., federal tax deposits (FTDs), estimated (ES) tax payments for C Corporations, or for other business entities when applicable.) Revenue officers must also determine whether the request is made solely to delay collection action and whether the agreement protects the government’s interest.

Authority

  1. IRC 6159, Agreements for Payment of Tax Liability in Installments.

  2. IRC 6331(k), Levy and Distraint, No levy while certain offers pending or installment agreement pending or in effect.

Roles and Responsibilities

  1. The Director, Collection Policy, is the executive responsible for establishing and maintaining IRS collection policies and procedural guidance for use by collection personnel.

  2. The program manager, Case Resolution Alternatives (CRA), is responsible for developing and delivering policies, procedures and practices within the IA program.

  3. Field collection group managers and field compliance managers are responsible for ensuring IA policies and procedures detailed in this IRM are properly implemented and consistently followed.

  4. Collection employees are responsible for evaluating, securing, and processing agreements in accordance with this IRM and related guidance. This includes timely documentation in ICS, timely IDRS input or requesting input of required transaction codes, and retention of supporting documents in the digital case file.

Program Management and Review

  1. Collection Policy oversees the IA program (also referred to as payment plans) through the following reports and reviews.:

    Program Type Description
    Program Reports:
    1. Program reports include the Monthly IA Trend Report. Case Resolution Alternatives (CRA) generates and reviews this report using Collection Activity Report (CAR) data to monitor IA inventory levels, the number of IAs initiated, default rates, full pay rates, and dollars collected, and to identify and research anomalies or adverse trends.

    Program Reviews:
    1. Program reviews include ad hoc IA program reviews to verify compliance with IRM requirements, address TIGTA/GAO findings, and evaluate trends.

    2. Case reviews are conducted by group managers to ensure compliance with this IRM.

    3. Group managers, leads, and on-the-job instructors (OJIs) also review cases through Embedded Quality Review System (EQRS) for evaluating employee performance and providing feedback. The National Quality Reviewers use the National Quality Review System (NQRS) to ensure compliance with this IRM and report official organizational business-quality results. The Data Collection Instrument (DCI) is used to capture case reviews for both EQRS and NQRS.

    4. Operational reviews are conducted by the field compliance manager and area director annually to evaluate program delivery and conformance to administrative and compliance requirements.

Program Controls

  1. Group managers must approve determinations that an IA (payment plan) request was made solely to delay collection action.

  2. Independent Administrative Review (IAR) is required before communicating the rejection of an IA request that meets pending IA criteria. Taxpayers may administratively appeal the termination, modification, or rejection of a proposed IA to the IRS Independent Office of Appeals. Revenue officers must ensure appeal rights are communicated and documented in ICS history.

  3. The Integrated Collection System (ICS) is the case management system for SBSE Field Collection and includes the digital storage solution (DSS). ICS-DSS allows revenue officers (ROs) to maintain active and closed case files in a cloud-based environment and to upload and retrieve case-related documents. Each case file must show that the chosen disposition method selected is consistent with the facts and circumstances outlined in the case, the IRM, and other official guidance. Certain actions taken by ICS users systemically generate approval requests for managers. Managerial approval is required for Non-Simple Installment Agreement (NSIA) case dispositions. Managerial approval is not required for Guaranteed IA, Simple Payment Plan, and Simple Payment Plan (Business Trust Fund) case dispositions.

  4. The Integrated Data Retrieval System (IDRS) is used to monitor most IAs for timely payments on accounts, as well as to determine whether taxpayers remain in compliance with filing and paying requirements. When inputting an agreement, all open balance due modules on IDRS in a notice or collection status must be included in the agreement. Revenue officers must verify IDRS reflects all modules before submitting the agreement for upload.

  5. Collection group managers are responsible for the quality and accuracy of work performed by the employees they supervise in accordance with IRM 5.13.1, Collection Quality Measurement, Embedded Quality Collection Field Organizations Administrative Guidelines. Managers must adhere to the programming resource guide on management procedures and controls addressed in IRM 1.4.50, Collection Group Manager, Field Compliance Manager and Area Director Operational Aid.

Terms

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

    • Delinquent Taxes: Assessed balance due (BAL DUE) accounts on IDRS, including notice status accounts, Automated Collection System (ACS) balance due accounts, and Status 26 accounts assigned to Field Collection. Delinquent taxes include assessed tax, penalties, interest, and other statutory additions.

    • Accrued Taxes: Unassessed amounts due on returns, missed estimated tax payments or undeposited FTDs as of the date of contact.

    • Current Taxes: Federal tax obligations that become due after taxpayer contact or during the term of the agreement, based on the filing, payment or deposit due date. These obligations include federal tax deposits (FTDs), estimated (ES) tax payments, and required income tax withholding.

    • BMF non-Trust Fund: Non-trust fund taxes are liabilities that do not include unpaid trust fund taxes subject to the Trust Fund Recovery Penalty (TFRP) under IRC 6672, Failure to collect and pay over tax, or attempt to evade or defeat tax. Examples include corporate income taxes, civil penalties and employment tax liabilities when the trust fund portion is paid in full, and only the employer tax, penalties or interest remains due.

    • Unpaid Balance of Assessment (UBA): The total assessed balance due on IDRS, including tax, assessed penalties, and assessed interest (the command code (CC) SUMRY balance.) UBA does not include accrued (unassessed) penalties and interest.

Acronyms

  1. This table lists commonly used acronyms and their definitions:

    Acronym Definition
    AC Action Code
    ACA Affordable Care Act
    ACS Automated Collection System
    AO Area Office
    ALE Allowable Living Expense
    ALN Agreement Locator Number
    ATM Appeals Team Manager
    BAL DUE Balance Due
    BMF Business Master File
    CAP Collection Appeals Program
    CAR Collection Activity Report
    CRA Case Resolution Alternatives
    CC Command Code
    CCP Centralized Case Processing (Collection)
    CLO Centralized Lien Operation
    CDP Collection Due Process
    CIS Collection Information Statement
    CLO Centralized Lien Operation
    CNC Currently Not Collectible
    CP Computer Paragraph
    CSED Collection Statute Expiration Date
    CSCO Compliance Service Collection Operation
    DCI Data Collection Instrument
    DDIA Direct Debit Installment Agreement
    DUT Document Upload Tool
    EIN Employer Identification Number
    EFTPS Electronic Federal Tax Payment System
    EQRS Embedded Quality Review System
    ES Estimated Tax
    FTD Federal Tax Deposit
    FTP Failure to Pay
    GAO Government Accountability Office
    IA Installment Agreement
    IAR Independent Administrative Reviewer
    IBTF In-Business Trust Fund
    IAAL Installment Agreement Accounts List
    ICS Integrated Collection System
    ICS-DSS Integrated Collection System - Digital Storage Solution
    IDRS Integrated Data Retrieval System
    IMF Individual Master File
    IOLA Individual Online Account
    IRM Internal Revenue Manual
    IRS Internal Revenue Service
    LLC Limited Liability Company
    NFTL Notice of Federal Tax Lien
    NQRS National Quality Review System
    NSIA Non-Streamlined Installment Agreement
    OIC Offer-in-Compromise
    OJI On-the-Job Instructor
    OPA Online Payment Agreement
    PPIA Partial Payment Installment Agreement
    RO Revenue Officer
    SRP Shared Responsibility Payment
    SSN Social Security Number
    TAS Taxpayer Advocate Service
    TBOR Taxpayer Bill of Rights
    TC Transaction Code
    TDI Tax Delinquent Investigation
    TIN Taxpayer Identification Number
    TIGTA Treasury Inspector General of Tax Administration
    TP Taxpayer
    TS Taxpayer Services (formerly known as Wage and Investment (W&I))

Related Resources

  1. IRM Resources:

    • Procedural guidance regarding Installment Agreements can be found throughout IRM 5.14, Installment Agreements.

    • IRM 4.20.1.4, Installment Agreements, for examination collection procedures.

    • IRM 5.19.1.2.6.3, Installment Agreements, for Accounts Management, Field Assistance, ACS, ACSS and CSCO collection procedures.

    • IRM 8.22.7.5, Installment Agreements (IA), for appeals officers and appeals team managers (ATMs) regarding collection procedures.

    • IRM 5.14.1.6, Multi-functional Installment Agreement (Payment Plan) Authority, provides guidance for other functions.

  2. Web Resources:

    • Centralized Field Support Knowledge Base Homepage: Centralized Field Support Knowledge Base Homepage

    • Integrated Collection System (ICS) User Guide:Integrated Collection System (ICS) User Guide

    • Integrated Automation Technologies Homepage: Integrated Automation Technologies Homepage

    • Installment Agreements Knowledge Base Homepage: Installment Agreements Knowledge Base Homepage

  3. The Internal Revenue Code (IRC) provides taxpayers specific rights. The Taxpayer Bill of Rights (TBOR) groups these rights into ten fundamental rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. Employees are responsible for being familiar with and following these rights. For additional information about your taxpayer rights, please see Pub 1, Your Rights as a Taxpayer or visit Taxpayer Bill of Rights.

Installment Agreements (Payment Plans) and Taxpayer Rights

  1. Request full payment or partial payment of the balance due when taxpayers have the means to pay from income or equity in assets. Encourage taxpayers to pay the tax liability as quickly as possible.

  2. If taxpayers qualify for a Guaranteed Installment Agreement, Simple Payment Plan, or Simple Payment Plan (Business Trust Fund), and request that type of agreement, the request will be granted even if the taxpayers could pay the liability in full. (See IRM 5.14.5, Simple Payment Plans, Guaranteed Installment Agreements, and Simple Payment Plans (Business Trust Fund).

  3. If taxpayers do not qualify for Guaranteed Installment Agreement, Simple Payment Plan, or Simple Payment Plan (Business Trust Fund) processing, secure a complete Collection Information Statement (CIS). See IRM 5.1.10.3.2, Initial Investigative Interview.

    Reminder:

    Case circumstances may exist where granting the IA would not be in the government’s best interest, such as when a taxpayer has defaulted on one or more prior agreements. The RO should make a determination as to whether the IA proposal is “Solely to Delay” based on the facts and circumstances of the case, including the taxpayer’s compliance history and prior defaults. Refer to IRM 5.14.3.3(3)d, Installment Agreement Requests Made to Delay Collection Action, when the request is made by a taxpayer that has defaulted on one or more prior agreements.

  4. Taxpayers with aggregate individual income tax liabilities of $10,000 or less (excluding penalties, interest, and additions) may qualify for guaranteed IAs if all requirements are met. See IRM 5.14.5.3, Guaranteed Installment Agreements, for additional information. Taxpayers with an aggregate unpaid balance of assessment (the CC SUMRY balance) equal to $50,000 or less may qualify for Simple Payment Plans. The unpaid balance of assessment includes tax, assessed interest, and penalties. It does not include accrued interest and penalty. See IRM 5.14.5.2, Simple Payment Plans, for additional information.

  5. There are various methods for making monthly payments.

    Note:

    When establishing a Direct Debit Installment Agreement (DDIA), it generally takes more than 30 days from approval before the first payment is debited. Encourage the taxpayer to make a voluntary interim payment at https://www.irs.gov/payments.

  6. Encourage taxpayers to use one of the following electronic or credit card methods of payment rather than check or money order:

    1. Electronic Federal Tax Payment System (EFTPS) – taxpayers will select the "payment-due with IRS notice" payment type for posting to Master file with a Transaction Code (TC) 670. EFTPS has the ability to schedule payments up to 12 months in advance for individual taxpayers and up to 4 months in advance for business taxpayers. The taxpayer must initiate payments by sending instructions to EFTPS. See IRM 21.7.1.4.8.1, Electronic Federal Tax Payment System (EFTPS), for complete instructions.

    2. Direct Debit installment agreements - If taxpayers maintain a checking account, you should encourage them to take advantage of the direct debit installment agreement. See IRM 5.14.10.4, Direct Debit Installment Agreements, for Direct Debit procedures.

    3. Payroll Deduction installment agreements - If taxpayers will not agree to a direct debit installment agreement, encourage them to take advantage of the payroll deduction agreement. See IRM 5.14.10.2, Payroll Deduction Agreements, for Payroll Deduction procedures.

    4. VanillaDirect Pay - Taxpayers who want to pay in cash can convert cash into electronic tax payments at participating retail locations. See Pay with cash at a retail partner for additional information. See also IRM 21.2.1.60, Paying with Cash at a Retail Partner.

    5. Credit Card installment agreement payment, see IRM 21.2.1.48.4, Payment by Credit Card, Debit Card or Digital Wallet (General), for procedures for paying by credit card.

    6. Payment by check or money order - If payments are made by check, they should be payable to: "US Treasury" . However, checks made out to "Internal Revenue Service" or "IRS" will be processed.

    7. IRS Direct Pay is a free service that allows taxpayers to make electronic payments directly to the IRS from their checking or savings accounts. See IRM 21.2.1.48.2, IRS Direct Pay, for further information.

    8. Individual Online Account (IOLA) is an online system that allows taxpayers to securely access their IMF account information through Your account. The Payment Options page provides taxpayers with options to make an online payment now. See IRM 21.2.1.62(8).

      Note:

      Cases assigned to Field Collection that are in ST 26 cannot set-up a payment plan in Online Payment Agreement (OPA) or Individual Online Account (IOLA).

      Note:

      Third-party payment processors charge a processing fee for payments made by debit or credit card or digital wallet. See IRM 21.2.1.48.4, Payment by Credit Card, Debit Card or Digital Wallet (General).

  7. Certain taxpayers who enter into IAs and file timely will have the failure to pay penalty reduced from a half to a quarter percent per month for any month in which an agreement is in effect until the 25% maximum aggregate rate is reached. (IRM 5.14.1.3 describes necessary inputs for TC 971 action codes.) Input of TC 971 AC 063 reduces failure to pay penalty from one half (0.5) to one quarter (0.25) percent per month if all of the following conditions are met:

    1. The IA was entered into on or after January 1, 2000.

    2. The balances are due from an individual (whether IMF or BMF, due on income, employment or excise tax returns).

    3. The tax return(s) was timely filed, including extensions.

    4. No CP 504, LT11, or Letter 1058 was sent (indicated by a TC 971 AC 069), increasing the failure to pay penalty from one-half (0.5) to one (1) percent.

      Note:

      If agreements are terminated, penalties increase to one-half (0.50) percent. The input of TC 971 AC 163 will increase the penalty rate from one-quarter (.25) percent to one-half (.50) percent. The penalty rate is not recalculated for the months during which the IA was active. For more information on the reduced penalty rate, refer to IRM 20.1.2.3.8.1.2, 1/4 Percent Penalty Rate - IRC 6651(h).

      Note:

      Payments on the balance are applied to the tax first, then any penalty, then interest.

  8. See IRM 5.14.7.5, Payments on Trust Fund Accounts During Approved In-Business Trust Fund Installment Agreements, paragraph (1)(a) — (d), regarding designation of payments during IAs.

  9. On February 9, 2018, the President signed into law the Bipartisan Budget Act (BBA) of 2018. The Act amended IRC 6159 to provide certain limitations to IA user fees. The Act’s amendments to IRC 6159 apply to IAs entered into on or after April 10, 2018.

    • User fees for IAs may not exceed the amount of such fee as in effect on February 9, 2018.

    • IA user fees will be waived for low-income taxpayers who agree to make electronic payments through a debit instrument.

      Note:

      At this point, the only mechanism the IRS has in place in which the taxpayer may agree to make electronic payments is through a debit instrument is a DDIA.

      Note:

      CC IAGRE has been programmed to waive the user fee on a DDIA when the taxpayer meets the low-income threshold.

    • IA user fees will be reimbursed to low-income taxpayers that are unable to make electronic payments through a debit instrument upon completion of the IA.

      Note:

      See IRC 6159(f) to review the full text.

    • For IA user fee purposes, taxpayers are low-income if their adjusted gross income (AGI) for the most recent year is at or below 250 percent of the Federal Health & Human Services Guidelines (FHHSG).

  10. The purpose of an IA user fee is for the IRS to recover the costs of administering the IA program. 31 United States Code (USC) 9701 - as interpreted by the Office of Management and Budget (OMB) Circular No. A-25 - provides the authority for the imposition of user fees. User fees are imposed for services pertaining to the entering into and the restructuring or reinstating of an installment agreement. See 26 CFR 300.1, Installment agreement fee and 26 CFR 300.2, Restructuring or reinstatement of installment agreement fee. Current User Fee Rates:

    Current User Fee Rates (through July 4, 2026) Updated User Fee Rates (Effective July 5, 2026)
    1. Origination Fee:
      Manual:

      • Low-income non-DDIA (regular IA) origination fee of $43 entered into on or before 7/4/2026 may be reimbursed if certain conditions apply

      • Low-income DDIA origination fee entered into on or before 7/4/2026-$0

      • DDIA origination $107

      • Regular IA origination - $178

    2. Online Payment Agreement (OPA):

      • OPA Low-Income Non-DDIA (regular IA) origination fee of $43 entered into on or before 7/4/2026 may be reimbursed if certain conditions apply

      • OPA Low-Income DDIA origination for DDIAs entered into on or before 7/4/2026- $0

      • OPA Regular origination - $69

      • OPA DDIA origination - $22

        Note:

        Taxpayers must establish their IA through OPA to be eligible for the OPA user fees shown above.

    3. Reinstatement/Restructuring user fee:

      • Low-income Non-DDIA (regular IA) reinstatement/restructuring fee of $43 entered into on or before 7/4/2026 may be reimbursed if certain conditions apply

      • Low-income DDIA reinstatement/restructuring for DDIAs entered into on or before 7/4/2026- $0

      • OPA Low-Income reinstatement/restructuring fee applies to regular IA and DDIA types entered into on or before 7/4/2026 - $10

      • All other reinstatement/restructuring - $89

    1. Origination Fee:
      Manual:

      • Low-income non-DDIA (regular IA) origination fee of $43 entered into on or after 7/5/2026 may be reimbursed if certain conditions apply

      • Low-income DDIA origination fee entered into on or after 7/5/2026-$0

      • DDIA origination $107

      • Regular IA origination - $178

    2. Online Payment Agreement (OPA):

      • OPA Low-Income Non-DDIA (regular IA) origination fee of $43 entered into on or after 7/5/2026 may be reimbursed if certain conditions apply

      • OPA Low-Income DDIA origination for DDIAs entered into on or after 7/5/2026- $0

      • OPA Regular origination - $69

      • OPA DDIA origination - $29

        Note:

        Taxpayers must establish their IA through OPA to be eligible for the OPA user fees shown above.

    3. Reinstatement/Restructuring user fee:

      • Low-income Non-DDIA (regular IA) reinstatement/restructuring fee of $43 entered into on or after 7/5/2026 may be reimbursed if certain conditions apply

      • Low-income DDIA reinstatement/restructuring for DDIAs entered into on or after 7/5/2026- $0

      • OPA Low-Income reinstatement/restructuring applies to regular IA and DDIA types entered into on or after 7/5/2026 - $6

      • All other reinstatement/restructuring - $89

  11. Individual taxpayers qualified as low-income (for purposes of the IA user fees) get a reduced fee of $43. This $43 low-income fee may be waived or reimbursed if certain conditions are met. The low-income fee of $43 may be charged to taxpayers based on the Reduced User Fee Indicator (RUFI) on Master File, as indicated by a RUFI>1. Advise taxpayers that if they are low-income, for IA user fee purposes, if their adjusted gross income (AGI), as reported on their most recently filed tax return, that is at or below 250 percent of the FHHSG, the user fee will be reduced. Advise taxpayers that if they feel that their AGI would qualify them for low-income status, they may apply using Form 13844, Application For Reduced User Fee For Installment Agreements, available at www.irs.gov or by phone at 1-800-829-3676. Low-income status for IA user fees applies only to individuals (not partnerships or corporations). Taxpayers will be informed of their right to apply for low-income status in the installment agreement acceptance letter. Inform taxpayers that Form 13844 must be submitted within 30 days of the date on the IA acceptance letter. The contact employee will not make the determination of whether taxpayers qualify for low-income status; that determination will be made when the Form 13844, Application For Reduced User Fee For Installment Agreements, is processed and validated. Once the IRS determines that taxpayers qualify as low-income, any amount of the fee collected in excess of $43 will be credited against taxpayers' Internal Revenue Code liabilities and thereby will reduce the amount of interest and penalties that might otherwise accrue.

    Note:

    Advise taxpayers that the IA user fee is due with the first payment in the amount of the agreed upon monthly payment or the IA fee, whichever is greater.

  12. When discussing IAs, inform taxpayers that:

    1. Penalties and interest continue to accrue on unpaid liabilities. Provide taxpayers with current percentage amounts and interest rates. If taxpayers request further information regarding penalties and interest, IRM 20.1, Penalty Handbook, provides rates for IRC 6651(a)(1), "failure to file" and IRC 6651(a)(2), "failure to pay" additions to tax. SERP website provides interest rates and tables: SERP - Interest Rates.

    2. A Notice of Federal Tax Lien (NFTL) may be filed in certain circumstances. IRM 5.14.1.4.3, Notice of Federal Tax Lien and Installment Agreements (Payment Plans), provides instructions on determining when to file a request for an NFTL.

      Note:

      The NFTL will not be filed on any individual shared responsibility payment (SRP) liabilities (MFT 35/Mirrored MFT 65) under the Affordable Care Act (ACA).

    3. There is the possibility of a levy if the agreement is terminated.

      Note:

      A levy will not be issued on any individual shared responsibility payment liabilities (MFT 35/Mirrored MFT 65) under the Affordable Care Act.

    4. Current returns for taxes must be filed and current deposits paid before an IA can be approved and the taxpayer must remain tax compliant for the entire term of the IA, or they will default on the agreement. If applicable, remind the taxpayer of the obligation to make estimated tax payments to avoid accruing new tax liabilities, that would default their agreement.

    5. Federal tax refunds will be offset to pay any overdue balances. See IRM 5.14.1.4.2 (19)e and f.

    6. Taxpayers have the right to appeal proposed terminations of IAs, terminations of IAs, proposed rejection of IAs or rejection of IAs. Refer to IRM 5.14.9, Independent Review and Appeals, when considering terminating an IA.

    7. The CSED will be suspended while the IA is pending, for 30 days following the rejection or termination of an IA, and for the period that Appeals is considering the rejection or termination of an IA.

  13. In accordance with the law, each year the IRS mails Computer Paragraph CP 89 and CP 289, "Annual Installment Agreement Statement," to every IA taxpayer. The statement provides:

    • The dollar amount of the beginning account balance(s) due

    • An itemized listing of payments

    • An itemized listing of penalties, interest and other charges

    • The dollar amount of ending account balance(s) due

  14. IRC 6502(a)(2)(A) provides that statutory periods for collection may be extended in connection with granting IAs. However, it is the policy of the IRS that CSED extensions are permitted only in conjunction with Partial Payment Installment Agreements (PPIAs) and only in certain situations. See IRM 5.14.2.2.3, Waiver Procedures for Partial Payment Installment Agreements.

Identifying Pending, Approved and Rejected Installment Agreement (Payment Plan) Proposals on IDRS

  1. Proposals to enter into IAs may result from letters, phone contacts, voicemail, email, or other communications between taxpayers and IRS personnel.

    Note:

    If a taxpayer requests an IA by email, DO NOT respond by email. Contact the taxpayer by telephone or correspondence. See IRM 10.5.1.6.8.1, Emails to Taxpayers and Representatives. If correspondence is used, advise the taxpayer to call the revenue officer who issued the correspondence to request the IA.

  2. All taxpayers have the right to request IAs. Requests for IAs, including requests involving unassessed/pre-assessed modules, must be documented in ICS case history and, when the request meets pending IA criteria, identified on IDRS within 24 hours.

    Exception:

    Do not input a pending IA (TC 971 AC 043) when the module is status 72 (litigation) or there is already a pending IA (TC 971 AC 043) present on the tax module(s) that is not followed by a reversal (TC 972 AC 043) or an established IA (TC 971 AC 063).

    Exception:

    Do not input a TC 971 AC 043 for an existing IA that has not been reversed or terminated (A TC 971 AC 063 not followed by a TC 972 AC 063 or a TC 971 AC 163).

    Note:

    IAs that include only assessments for individual shared responsibility payment liabilities under the Affordable Care Act (MFT 35/Mirrored MFT 65) do not need to be identified as pending.

  3. The following transaction codes (TC) and Action Codes (AC) will be used:

    • Pending agreements: TC 971 AC 043 — for requests not immediately approved

    • Approved agreements: TC 971 AC 063 — for immediately approved requests

  4. These inputs must be made within 24 hours of the request for, and identification of, IAs or pending agreements. These transaction codes prevent enforcement (levy) action for the duration of the pending status. See IRM 5.14.1.5, Levy Restrictions and Installment Agreements (Payment Plans). Request the appropriate inputs for the applicable periods using the ICS application by selecting the "COLLECTION ACTIVITIES" menu from the Case Summary screen; then selecting "INSTALLMENT AGREEMENT" ; and then selecting the proper code for input (either "GENERATE TC971/972 AC043" or "GENERATE TC971 AC063" ).

    Note:

    If the IA will be input immediately (i.e., a Simple Payment Plan or Simple Payment Plan (Business Trust Fund)), do not request input of the TC 971 AC 043.

    Note:

    Do not input an additional TC 971 AC 043 if there is already an unreversed TC 971 AC 043 on the tax module (A TC 971 AC 043 can be reversed by either a TC 972 AC 043 or a TC 971 AC 063.) Refer to IRM 5.14.1.3.1 (1)(f) to determine if a reversal of a prior TC 971 AC 043 is necessary before inputting another TC 971 AC 043 for a new pending IA. Also, see IRM 5.14.1.3.1 (1), Cases Received From ACS or campuses, for more information.

  5. Use the table below to determine whether an IA request qualifies for pending IA status. The account qualifies for pending IA status only when the taxpayer provides all information identified in the table below.

    Caution:

    Do not identify the account as pending IA if the taxpayer made the request to delay collection action. See IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action.

    If the taxpayer... Then...
    • Provides enough information to identify the taxpayer

    Continue processing the IA request. Generally, secure the taxpayer’s name and TIN. If the taxpayer provides a name but no TIN, treat the requirement as met only if you can otherwise identify the taxpayer.
    • Identifies the tax liability to be covered

    Continue processing the IA request.
    • Proposes a specific monthly or other periodic payment amount

    Continue processing the IA request.
    • Is compliant with filing requirements

    Continue processing the IA request. See IRM 5.14.1.4.2, Compliance and Installment Agreements (Payment Plans).
    • Provides a completed collection information statement (CIS), when required

    Continue processing the IA request. Refer to Exhibit 5.14.1-5, Installment Agreement (Payment Plan) table, for details on the types of IAs that require a CIS and IRM 5.15.1, Financial Analysis Handbook, for guidance on when a CIS is required.

    Note:

    A CIS may be completed verbally or in writing. A CIS is considered complete when sufficient information is provided for the revenue officer to make an initial collection decision (e.g., full pay, currently not collectible (CNC), etc.). An IA request remains pending even if additional supporting financial documentation is required to validate the CIS or if equity in assets must be addressed.

    Note:

    If the RO secures an unpaid return from the taxpayer and creates a balance due module (pre-assessed) on ICS and the taxpayer wants to include the created balance due return in an IA proposal and meets all of the pending IA requirements at that time to establish a pending IA, request input immediately (within 24 hours).

    Reminder:

    If the completed CIS indicates the taxpayer may qualify for an alternative case resolution (e.g., full pay, CNC, etc.), input TC 971 AC 043 to document that sufficient information was provided to make an initial collection decision. Should the taxpayer agree to a different case closure action determined to be more appropriate case resolution, they may withdraw their IA request. See IRM 5.14.4.5, Withdrawal of Installment Agreement Requests.

  6. Do not identify the account as pending IA in the situations below.

    If... Then...
    The taxpayer does not meet all pending IA requirements Do not input TC 971 AC 043.
    Delinquent returns are required Advise the taxpayer that the IA is not pending. The taxpayer must submit a new IA proposal after filing the returns. The later proposal must meet all pending IA requirements at that time before a TC 971 AC 043 is input.
    The taxpayer is pursuing another case resolution (e.g., CNC, OIC, etc.) Do not treat the IA as pending. An IA is not pending until accepted for processing. See 26 CFR 301.6159-1(b)(2). A request is not processable if the taxpayer is already pursuing another case resolution alternative (e.g., CNC, OIC, etc.).
    The proposal includes restitution based assessment (RBA) modules and payments will not fully satisfy the RBAs by the CSED Do not treat the RBA modules as qualifying for pending IA status. See IRM 5.14.4.6, Establishing Installment Agreements on Restitution Based Assessments and related Civil Assessments - Overview.

    Note:

    The IRS may not accept a non-processable pending IA request unless the request meets Guaranteed IA criteria. See IRM 5.14.5.3, Guaranteed Installment Agreements.

    Note:

    An unreversed TC 971 AC 043 posted to a taxpayer’s account with no account history confirming the taxpayer submitted a processable pending IA (AMS, ICS, IDRS history, correspondence, etc. ) is not considered a pending IA. Attempt to contact the taxpayer to confirm if the taxpayer did request a pending IA before reversing the TC 971 AC 043. See IRM 5.14.1.3.1, Cases received from ACS or Campuses.

    Reminder:

    See IRM 5.14.1.3, Identifying Pending, Approved and Rejected Installment Agreement (Payment Plan) Proposals on IDRS, to determine when an IA request is considered pending.

  7. A request for an IA on post-petition liabilities is non-processable when a taxpayer is in bankruptcy. See IRM 5.9.4.20.1, IA Requests For Post-Petition Liabilities Submitted During Bankruptcy.

    Note:

    When taxpayers are in bankruptcy, post-petition IA requests submitted by taxpayers who had a pre-petition IA are also considered non-processable. The taxpayer may not be granted a post-petition IA, and the pre-petition IA may not be reinstated while the bankruptcy is open. These cases are worked by Insolvency. Contact the field insolvency mailbox (*SBSE Field Insolvency) for the next appropriate case action.

  8. A request for an IA on liabilities contained in a pending or accepted OIC is non-processable. See IRM 5.19.1.3.5(13), For Other Account Issues Requiring Referrals or Redirect, and IRM 5.8.1, Offer in Compromise (OIC), Overview.

    Caution:

    Identify if there is a pending IA (TC 971 AC 043) already present on the tax period(s) to be covered by the IA. (A TC 971 AC 043 can be reversed by either a TC 972 AC 043 or a TC 971 AC 063). If there is a pending IA already present, determine if it is still applicable or requires a reversing transaction. Do not input an additional TC 971 AC 043 to a pending IA module (unreversed TC 971 AC 043 already present).

  9. Requests that meet the criteria in IRM 5.14.1.3 (5) are identified as pending IA even if the taxpayer is not current with:

    • Estimated (ES) payment requirements; or

    • Federal tax deposit (FTD) requirements,

    Reminder:

    No IA may be approved until current payment compliance is achieved. See IRM 5.14.1.4.2.

    Reminder:

    If the information provided in IRM 5.14.1.3 (5) indicates the agreement request was made solely to delay collection action, do not identify the account as pending IA status. Instead, follow IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action, if applicable.

  10. If a taxpayer does not provide all of the information required in IRM 5.14.1.3 (5), request the missing information. For example, if no payment amount is specified, ask how much can be paid per month. A specific monthly payment amount must be specified for the account to be marked "pending" . Advise the taxpayer that the IA will not be considered pending until the information is received to perfect the IA request, and explain the potential consequences for failing to meet the deadline for the actions necessary to perfect the IA request.

  11. Acceptance or rejection of proposed agreements is based on analysis of Collection Information Statements. See IRM 5.14.1.4, Installment Agreement (Payment Plan) Acceptance and Rejection Determinations.

    Exception:

    (1) If IA requests are made solely to delay collection action, see IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action.

    Exception:

    (2) Grant Simple Payment Plans, Guaranteed Installment Agreements and Simple Payment Plans (Business Trust Fund) based on the criteria in IRM 5.14.5, Simple Payment Plans, Guaranteed Installment Agreements, and Simple Payment Plans (Business Trust Fund).

  12. The following TCs and ACs will be input on ALL taxpayer modules containing TC 971 AC 043 to indicate acceptance or rejection of proposed agreements:

    1. For approved agreements: request that TC 971 AC 063 be input to IDRS on ALL taxpayer modules.

      Note:

      Agreements approved on ICS systemically input the TC 971 AC 063 to IDRS, so no action is necessary for those agreements.

    2. For Rejected Proposals: request reversal of TC 971 AC 043 forty-five (45) days after the rejection is communicated to taxpayers, unless a timely appeal is received. The date of the reversing transaction (TC 972 AC 043) should be thirty (30) days from the date the rejection was communicated to the taxpayer. This preserves the statutory appeal period while allowing time for notice delivery and accurate CSED computation.

    3. For Appeals: TC 971 AC 043 remains on all modules while the appeal is pending. If Appeals sustains the rejection, input TC 972 AC 043 thirty days (30) after the date that Appeals sustains the rejection. If Appeals grants an IA, follow the procedures above for approved agreements.

      Reminder:

      Request input of the TC 972 AC 043 timely and with the correct transaction date to ensure the CSED is recalculated correctly.

  13. To identify trust fund recovery penalties as pending or approved IAs, the balance due account must have an:

    • Assessed liability or liabilities

    • Executed Form 2751, Proposed Assessment of Trust Fund Recovery Penalty, from the taxpayer

    • Approved Form 4183, Recommendation re: Trust Fund Recovery Penalty Assessment, and issuance of Letter 1153, Proposed Trust Fund Recovery Penalty Notification Letter

  14. Examples of "Pending" and "No Pending (agreement)" are in IRM 5.14.1.4, Installment Agreement (Payment Plan) Acceptance and Rejection Determinations, and the two charts below.

    SITUATIONS THAT DO RESULT IN IDENTIFICATION OF PENDING INSTALLMENT AGREEMENTS

    Example:

    (1) A taxpayer calls the IRS, provides their name, social security number (SSN), and identifies the outstanding liability (or balances due). The revenue officer confirms compliance with all filing requirements and the taxpayer states they want to pay $500 per month. The proposed payment amount does not meet a simple payment plan or simple payment plan (business trust fund) criteria, therefore, a CIS is required. The taxpayer provides a completed CIS that is sufficient to make an initial collection decision. However, the revenue officer determines that bank statements are required to verify the CIS, and the taxpayer must liquidate assets to partially pay the tax owed before the IA request may be accepted. The revenue officer provides the taxpayer with a deadline and inputs a TC 971 AC 043.

    Example:

    (2) A taxpayer wants to make payments. RO completes Collection Information Statement (CIS) including the taxpayer’s name and SSN and tells the taxpayer $500 per month is appropriate. The taxpayer is in compliance with filing requirements. The taxpayer verbally agrees to the payment amount.

    SITUATIONS THAT DO NOT RESULT IN IDENTIFICATION OF PENDING INSTALLMENT AGREEMENTS

    Example:

    (1) A revenue officer evaluates a taxpayer’s CIS. The taxpayer’s name, social security number and balances due are all known and/or identified. The revenue officer informs the taxpayer that a $1500 per month installment agreement is appropriate. There is no response from the taxpayer.

    Example:

    (2) A revenue officer mails a Form 433-D, Installment Agreement, (with the taxpayer’s name, SSN and balances due listed) to a taxpayer. The Form 433-D Installment Agreement, provides a payment amount based on an analysis of the taxpayer’s CIS. No response is received by phone, FAX, Document Upload Tool (DUT), email or other means of communication from the taxpayer.

    Example:

    (3) A taxpayer who knows they owe taxes tells their employer to send $500 per month of their paycheck to the IRS. The taxpayer does not communicate with the IRS. The taxpayer’s employer sends $500 per month referencing the taxpayer’s SSN. (Note: if $500 per month is being received, contact should be attempted prior to taking collection action).

    Example:

    (4) A revenue officer begins a trust fund recovery penalty (TFRP) investigation. Meanwhile, an officer of the corporation states they want an installment agreement, identifies the trust fund portion of the corporation’s liability (as the balance due account to be paid) and provides a specific payment amount (to be paid from their own funds and applied to the corporate liability – trust fund only). However, no liability has been recommended for assessment and/or the officer has not signed Form 2751, Proposed Assessment of Trust Fund Recovery Penalty, indicating responsibility for the trust fund portion of the liability (i.e., there is no balance due account for payment application). Therefore, the potentially responsible officer is informed that there is no pending installment agreement and payments made are considered voluntary. Information about designating these payments to the trust fund portion of a liability is provided in IRM 5.7.4.4, Payments by Responsible Person on Behalf of the Employer (also see IRM 5.14.7.4.1, Trust Fund Recovery Penalties and Installment Agreements and IRM 5.14.7.5, Payments on Trust Fund Accounts During Approved In-Business Trust Fund Installment Agreements.

    Example:

    (5) A taxpayer wants to make payments on an installment agreement. The revenue officer completes a CIS including the taxpayers name and PlI/SSN. The revenue officer tells the taxpayer that $500 per month appears to be an appropriate amount for an installment agreement, but notes that the taxpayer has not been compliant with filing Forms 1040 for the last two years. The taxpayer states that their accountant is away, and that the returns, which are complicated, will take some time to prepare. The revenue officer requests that the taxpayer submit original, signed returns within 60 days, along with a $500 payment (based on the financial statement received). In addition, the revenue officer requests that a payment of $500 be received within 30 days. These requests are made in accordance with the procedures provided in IRM 5.14.3.2, Setting Deadlines and Receiving Payments, and IRM 5.1.10, Taxpayer Contacts.

    Example:

    A taxpayer requests an IA and proposes a $500 monthly payment amount that meets partial payment installment agreement criteria. A CIS is required. However, when the revenue officer attempts to complete the CIS with the taxpayer, she can only provide basic asset information, and is unable to provide complete asset, income, and expense information. The taxpayer advises she needs more time to gather verification of her monthly income and expenses and assets. The IA request is not considered pending because the CIS does not have enough information to make an initial collection decision, a TC 971 AC 043 will not be entered.

Cases Received From ACS or Campuses

  1. If cases are assigned to the field from ACS or campuses with TC 971 AC 043 present on one or more of the tax modules, employees will:

    1. Attempt to contact the taxpayer and determine if the taxpayer requested an IA.

    2. If the taxpayer requested an IA, follow the procedures in IRM 5.1.10.3.2, Initial Investigative Interview, regarding requesting payments. Include a definite request for payment, if appropriate. Consider the contact date to be the new request date and begin case action. If rejection will be recommended, independent review is required. If TC 971 AC 043 has not been input on all Balance Due periods, request input immediately (within 24 hours.)

    3. If the taxpayer requested an IA and is not current with filing requirements (TC 971 AC 043 input in error), do not reverse the TC 971 AC 043 immediately. Provide the taxpayer with a deadline for filing all required returns and any additional information necessary for an IA determination.

      Note:

      The RO must provide and document in ICS history a deadline requesting the missing tax returns. ICS documentation must include all contacts and any communication made (orally or in writing) between the RO and the taxpayer.

    4. Advise the taxpayer that if they fail to meet the established deadline, the pending IA status will be reversed with no referral to the IAR for concurrence.

    5. If the taxpayer did not meet pending IA criteria (TC 971 AC 043 input in error) and the additional information requested to consider the case as pending is not received, reverse the pending IA. The reversing transaction (TC 972 AC 043) date should be the same as the TC 971 AC 043 date. If the taxpayer files all delinquent returns but fails to comply with the request for additional information needed to make an acceptance determination, refer the proposed rejection for IAR.

    6. If the taxpayer did not request an IA, request reversal of TC 971 AC 043 using TC 972 AC 043 with the same date as the original input.

      Note:

      A TC 972 AC 043 will systemically reverse TC 971 AC 043 when a TC 480 (pending offer in compromise) posts or a module is updated to Status 12 (satisfied liability), unless a TC 608 (expired CSED) has been entered.

  2. In some situations, the criteria regarding IAs made solely to delay collection action may apply. In these cases, if the current date is within 30 days of the input date of the TC 971 AC 043, and it is clear that one of the criteria provided in IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action, is present, request input of TC 972 AC 043. Independent review is not necessary. Advise the taxpayer that there is no pending IA because of the solely to delay determination and that the taxpayer may discuss the issue with the Group Manager. Ensure case histories are documented with the basis for the solely to delay determination and managerial concurrence as provided for in IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action.

Installment Agreement (Payment Plan) Acceptance and Rejection Determinations

  1. If taxpayers cannot immediately pay the balance due in full, and an IA will satisfy the liability or otherwise meets the criteria in IRM 5.14.2.2, Overview, consider an IA.

  2. If the taxpayers do not qualify for Guaranteed Installment Agreements, Simple Payment Plans or Simple Payment Plans (Business Trust Fund), determine a plan for resolving the balance due accounts based on the Collection Information Statement (CIS) and supporting documentation provided by the taxpayer. See IRM 5.1.10.3.2, Initial Investigative Interview, and IRM 5.15.1, Financial Analysis Handbook.

    Note:

    In determining the most appropriate plan for resolving the balance due, consider collection actions that are least intrusive to the taxpayer while meeting the government’s need for efficient tax collection. Consider the viable payment options in IRM 5.14.1.2 (6) and IRM 5.14.2, Partial Payment Installment Agreements and the Collection Statute Expiration Date (CSED), and follow IRM 5.1.10.7, Taxpayer Rights, to protect taxpayer rights.

  3. There are no minimum or maximum dollar limits for the amount of a liability that may be included in an IA.

  4. Generally, IAs should reflect taxpayers’ ability to pay on a monthly basis throughout the duration of agreements. Employees must:

    1. Analyze the income and expenses to determine the amount of disposable income (gross income less all allowable expenses) available to apply to the tax liability.

    2. Justify deviations from allowable living expense (ALE) standards. Supporting documentation or verbal testimony is required and must be documented in the ICS case history.

    3. Analyze assets that may be available to resolve the balance due accounts. See IRM 5.14.1.4 (5) for more information about economic hardship situations.

    4. If taxpayers do not agree to the payment amount, or to an increase in payments, inform them that these and other issues detailed in IRM 5.14.1.4(6) through (9) may be discussed with the next level of management.

    5. Employees may choose to bring managers into discussions to assist in reaching agreements.

    6. If the agreement cannot be recommended for approval, inform the taxpayer that the request remains pending and that rejection will be recommended, for IAR. Before the case is forwarded, ensure the account meets pending IA criteria, TC 971 AC 043 was input correctly, the proposed payment amount and due date are documented, Form 12233, Request for Installment Agreement - Independent Review Prior to Rejection, is prepared, and the manager concurs with the proposed rejection. See IRM 5.14.9.2.1, Revenue Officer Responsibility. Do not communicate an actual rejection to the taxpayer before IAR is completed. Collection action remains suspended until the taxpayer is given a decision and appeal rights are issued.

  5. If taxpayers have equity in assets that could be used to fully or substantially satisfy balance due accounts, explore the possibility of liquidating or borrowing against those assets as determined in guidance found in IRM 5.15.1.3, Analyzing Financial Information, unless:

    • It would impose an economic hardship situation as defined in IRM 5.15.1.2(16), and 26 CFR 301.6343-1(b)(4), or

    • The taxpayer qualifies for a guaranteed installment agreement or requests and qualifies for a simple payment plan or simple payment plan (business trust fund), and the IA is appropriate based on the facts and circumstances of the case, see IRM 5.14.5, Simple Payment Plans, Guaranteed Installment Agreement and Simple Payment Plans (Business Trust Fund).

    Note:

    See IRM 5.15.1.2(14) and IRM 5.15.1.31(3) for additional guidance.

  6. Given the various options available for satisfying balance due accounts, consider:

    If the taxpayers have the ability to fully or partially satisfy balance due accounts by: Then
    • Using cash;

    • Withdrawing cash from the bank or other accounts;

    • Liquidating of securities or borrowing money against the value of the securities holdings;

    • Borrowing on equity in real or personal property;

    • Selling real or personal property;

    • Borrowing against the cash value of the universal life or whole life insurance policies; or

    • Surrendering the universal life or whole life insurance policies (for the cash value).

      Note:

      A life insurance policy may be worth significantly more than its cash value. Selling the life insurance policy on the secondary market may give the policyholder a higher return than the policy’s cash value. See IRM 5.8.5.9(3), Life Insurance, for determining the value of a taxpayer’s insurance policy.

    1. Request full or partial payment (specify the amount) be made on balance due accounts.

    2. Inform the taxpayer that the specific amount of payment requested is based on the conversion of assets (through borrowing or selling); or cash or other liquid assets (such as securities or money market accounts); or other analysis of the taxpayer’s financial statement.

    3. Inform the taxpayers that IAs will be recommended for rejection if there is sufficient equity or cash available to fully pay the taxes and full payment is not received by a set date, or if there is sufficient equity or cash available to make a significant partial payment of the taxes and the partial payment requested is not received by a set date. Advise the taxpayer that they will have appeal rights if their IA proposal is rejected.

      Note:

      See IRM 5.14.3.2, Setting Deadlines and Receiving Payments, about providing deadlines.

    4. Provide a specific deadline for payment. In addition, notify taxpayers of the consequences of missing the deadline. See IRM 5.14.3.2, Setting Deadlines and Receiving Payments, for additional information.

    Example:

    If a taxpayer has the ability to pay $3,000 per month on a $200,000 liability and has a home valued at $400,000 with equity of $200,000, request that they attempt to borrow on the available equity in the home prior to granting an IA. If the taxpayer does not attempt to borrow on the home they must be notified that, though the IA request is pending, it will be recommended for rejection. If the taxpayer is able to get a home equity loan and the monies are used to pay taxes, the amount of the payment on the loan will be considered an allowable expense. However, if the taxpayer applies for a loan but the loan application is denied, the taxpayer will be notified to submit an installment agreement request. It would promote voluntary compliance and be in the interest of the government.

    Exception:

    If the taxpayer is eligible for a Simple Payment Plan, Guaranteed Installment Agreement or Simple Payment Plan (Business Trust Fund), financial statements are not required. See IRM 5.14.5.2, Simple Payment Plans, IRM 5.14.5.3, Guaranteed Installment Agreements, or IRM 5.14.5.4, Simple Payment Plans (Business Trust Fund).

    Caution:

    Do not warn taxpayers of enforcement action if IAs are pending or in effect. See IRM 5.14.3.2, Setting Deadlines and Receiving Payments, for additional information. This includes issuing Letter 1058, Final Notice Reply Within 30 days which is prohibited while an IA is pending. See IRM 5.11.1.3.3.3(7)a, Issuing Notice of Intent to Levy/Notice of a Right to a Hearing in Field Collection, for additional information.

    Note:

    It is not appropriate to ask a taxpayer to liquidate or borrow against an asset if doing so would create economic hardship for the taxpayer. See IRM 5.14.1.4 (5) for related guidance and exceptions.

    Reminder:

    In appropriate circumstances, the taxpayer should be referred to TAS when the case meets TAS criteria. See IRM 13.1.7.2, Introduction to TAS Case Criteria.

  7. A Simple Payment Plan or Simple Payment Plan (Business Trust Fund) may be granted when the taxpayer makes a payment on balance due accounts that reduces the unpaid balance(s) of assessments (UBAs) to an amount that fits the for the agreement type.

    Example:

    A taxpayer owes $60,000 (UBA) in IMF taxes. Request full payment of the balance due accounts. If the taxpayer cannot full pay, request a partial payment to reduce the aggregate unpaid balance of assessments, as reflected on CC SUMRY balance, to $50,000 or less prior to granting the Simple Payment Plan. The agreement may be granted once the balance is reduced to $50,000 or less, provided the CSED is protected.

  8. If an analysis of the taxpayer’s financial condition shows the taxpayer cannot pay but:

    • They insist on wanting to make payments, consider closing the account as CNC and advise the taxpayer they are not required to make payments while in CNC.

      Note:

      The taxpayer may still choose to make voluntary payments when possible and/or submit an Offer in Compromise.

    • They may choose to proceed with an IA, and the proposed amount will fully pay the balance due account(s) within the collection statute (and waiver period if appropriate), establish the IA and prepare a backup Form 53, Report of Currently Not Collectible Taxes, in case the agreement later defaults and is terminated. See Exhibit 5.14.1-2.

    Note:

    If the amounts proposed by the taxpayer will not fully pay the balance due account(s) within the collection statute, then Partial Payment Installment Agreements (PPIA) may be considered. See IRM 5.14.2.2.1, Partial Payment Installment Agreement Requirements.

  9. If analysis of the taxpayer’s financial condition shows a liability cannot be collected in full through an IA, discuss the PPIA, Offer in Compromise (OIC), or a CNC determination with the taxpayer. See IRM 5.8, Offer in Compromise, and IRM 5.14.2.2.1, Partial Payment Installment Agreement Requirements. If the taxpayer agrees with the alternative resolution of CNC or OIC, secure the taxpayer’s consent to withdraw the IA request in writing or verbally. Document the ICS case history with the taxpayer's agreement with the alternative resolution and request input of TC 972 AC 043. Refer to IRM 5.14.4.5, Withdrawal of Installment Agreement Requests.

    Note:

    Give the taxpayer an opportunity to withdraw the IA request and, at the same time, inform the taxpayer that withdrawing the pending IA waives IAR or appeal rights. Refer to IRM 5.14.4.5, Withdrawal of Installment Agreement Requests.

  10. See IRM 5.14.9.2, Proposal to Reject Installment Agreement to Independent Administrative Review, when an IA request will be recommended for rejection, and IRM 5.14.9.2.3, Cases Returned From Independent Administrative Review, for communicating rejection and appeal rights.

  11. See IRM 5.14.9.2.3(4), Cases Returned From Independent Administrative Review, regarding consideration of revised proposals received during the rejection appeal period.

  12. See IRM 5.11.1.3.2, Required Notices, and IRM 5.10.1.5.2, Alternative Methods of Collection, if the taxpayers qualify for IAs or OIC but:

    • Do not submit or request one

    • Do not agree to an acceptable payment amount

      Note:

      Also see IRM 5.14.3.2, Setting Deadlines and Receiving Payments.

    Reminder:

    Although the intention to recommend rejection should be explained to the taxpayer, do not communicate an actual rejection before IAR, and do not take enforcement action while the IA remains pending.

  13. For agreements that require no managerial approval, see IRM 5.14.5.2, Simple Payment Plans, IRM 5.14.5.3, Guaranteed Installment Agreements , and IRM 5.14.5.4, Simple Payment Plans (Business Trust Fund). For agreements that require management approval, see IRM 5.14.7.3, Installment Agreements Involving Limited Liability Companies, IRM 5.14.7.4.2, Approval and Monitoring, and IRM 5.14.13.2, Managerial Approval.

Six-Year Rule and One-Year Rule

  1. Six-Year Rule: When a taxpayer is unable to full pay immediately and does not qualify for a simple payment plan, the taxpayer may still qualify for the six-year rule. Taxpayers are required to provide financial information in these cases, but are not required to provide substantiation of reasonable expenses. All expenses may be allowed if: the taxpayer establishes that they can stay current with all paying and filing requirements, the tax liability, including projected accruals, can be fully paid within six years and within the CSED, and the expense amounts are reasonable. Do not automatically allow agreements based on the six year maximum if expenses are unreasonable.

    Reminder:

    The Six-Year Rule is not applicable to corporations, partnerships, LLCs (where the LLC is identified as the liable taxpayer), or any business expenses. The Six-Year Rule is also not applicable for Business Master File (BMF) liabilities owed by in-business sole proprietors or LLCs, where the individual owner is identified as the liable taxpayer.

    Caution:

    An IA established under the Six-Year Rule is an NSIA (Non-Simple Installment Agreement). As such, a complete financial analysis must be done prior to establishing the IA, and equity in assets must be addressed in accordance with IRM 5.15.1.3, Analyzing Financial Information.

  2. One-Year Rule: Taxpayers who cannot full pay their accounts within six years may be given up to one year to modify or eliminate excessive necessary expenses. In some cases, by modifying or eliminating some conditional expenses, a taxpayer may be able to full pay the liability plus accruals within the six year limit. This would enable a taxpayer to retain some conditional expenses under the Six-Year Rule. The taxpayer does not have to qualify for the Six-Year Rule in order to apply the One-Year Rule.

    Reminder:

    The One-Year Rule is not applicable to corporations, partnerships, LLCs (where the LLC is identified as the liable taxpayer), or any business expenses. The One-Year Rule is also not applicable for BMF liabilities owed by in-business sole proprietors or LLCs, where the individual owner is identified as the liable taxpayer.

Compliance and Installment Agreements (Payment Plans)

  1. Filing and paying compliance must be considered prior to determining that the best manner of paying delinquent taxes is through an IA.

    Note:

    The prerequisite to any agreement: Filing compliance = all required returns are filed or on an approved extension. Payment compliance = all required federal tax deposits and/or estimated tax payments are current.

  2. Ensure all balance due modules, including cross-referenced taxpayer identification numbers, displayed on IDRS (SUMRY, which includes Status 22, 23, 24, 26, 53, and 58) are included in the agreements. Verify this by checking the applicable CFOL command codes. The Integrated Automation Technologies (IAT) tool is useful for verifying compliance during the initial analysis; however, the RO must still review the case and make the final determination based on the case information. See IRM 5.1.11.2.3 , Initial Analysis, IRM 5.14.1.4.2 (17), and IRM 5.14.2.2.1, Partial Payment Installment Agreement Requirements, for exceptions.

    1. Individuals that are in business as sole proprietors must be in compliance with both individual and business filing and payment requirements to qualify for IAs.

    2. An individual that is identified as the liable taxpayer for a single member limited liability company (LLC) must be in compliance with both individual and business filing and payment requirements to qualify for IAs.

    3. A corporation, partnership, trust, estate or other entity that is identified as the liable taxpayer for a single member LLC must be in compliance with all filing and payment requirements for both entities to qualify for IAs.

    4. If taxpayers have delinquent accounts on two or more taxpayer identification numbers (SSN and EIN, or two EINs), include all balance due accounts in one agreement. See IRM 5.14.2.2.1 , Partial Payment Installment Agreement, for exceptions, IRM 5.14.13.3, IDRS Monitoring, and IRM 5.14.13.5, Manually Monitored Installment Agreements (MMIA), for monitoring.

      Note:

      For certain single member LLCs, different entities may be liable for separate tax periods assessed under the same name and EIN. See IRM 5.1.21, Collecting from Limited Liability Companies (LLCs), and IRM 5.14.7, BMF Installment Agreements.

    5. Modules in Status 22, 23, 24, 53, or 58 on IDRS must either be TSIGNed or have ICS BAL Due modules created prior to submitting the IA for approval and input.

      Note:

      If a status 53 module(s) is to be excluded from the IA listed in IRM 5.14.7.3.2, Installment Agreements When Owner (SMO) and LLC are Liable for Assessments in LLC Name, make an ICS history notation in the Closing Narrative. This history notation will alert Centralized Case Processing (CCP) to exclude these modules from the IA.

  3. Taxpayers must include ACA SRP modules (MFT 35/Mirrored MFT 65) in new or pending IAs that include regular tax assessments (MFT 30/31, 55, etc.), subject to the following guidelines:

    • If the taxpayer has an existing/agreed IA, then a new Individual SRP module (MFT 35/Mirrored MFT 65) is considered a stand alone that can be included in the IA and will not default the IA.

    • If the taxpayer responds to a notice on a subsequent MFT 35/Mirrored MFT 65, the IRS employee can add the new period into an existing IA without additional fees.

    • If the taxpayer does not want the new Individual SRP module (MFT 35/Mirrored MFT 65) added to the existing IA, then the Individual SRP module will be moved to recess (TC 530 cc 35). This will happen systemically if no action is taken, and the case will not be assigned to ACS or Field Collection.

      Note:

      The case will continue to be subject to refund offset if the taxpayer does not request to have the MFT 35/Mirrored MFT 65 included in the IA.

      Note:

      A subsequent MFT 35/Mirrored MFT 65 will not cause an existing IA to default.

    • If the IA defaults for another reason, such as insufficient payments, it will only be reinstated if all modules, including any subsequent MFT 35/Mirrored MFT 65 modules, are included.

    Note:

    After January 1, 2016, Individual SRP penalties (MFT 35) may be mirrored in the same manner as an MFT 30. These mirrored liabilities will appear as MFT 65 assessments.

    Caution:

    Do not assume that assessments made against both a husband and wife for the same period are duplicates simply because they are for the same tax period. Before assessments are treated as duplicates, caseworkers should verify that the SRP assessments are for the same underlying liability (jointly filed Form 1040), and are not for separately filed Form 1040.

  4. Taxpayers must be in compliance with all filing and payment requirements prior to approval of IAs.

    Note:

    Ensure all Del Rets are shown as closed on IDRS and in status "D" on ICS PRIOR to selecting one of the Option A systemic upload IA types (Routine Installment Agreement, Simple Payment Plan, Simple Payment Plan (Business Trust Fund), IBTF Installment Agreement). If the Del Ret is not in a closed status on IDRS and ICS, the IA request will reject.

  5. Do not grant agreements if the taxpayers have not filed all required returns. Do not identify requests for agreements as "pending" IAs if the taxpayers have not filed all required returns. See IRM 5.14.1.3 (6).

  6. A Del Ret is present when a delinquency investigation is established by input of Transaction Code (TC) 140. In some publications and procedures the term "Taxpayer Delinquency Investigation" (TDI) is used to describe Del Rets.

  7. If Del Ret status is not indicated for a tax period then, for the purpose of granting an IA, no additional compliance check is required (except on tax returns due within the past sixteen (16) months). See IRM 5.14.1.4.2 (8).

  8. Prior to granting IAs, ensure that all tax returns due within the past sixteen (16) months were filed. If not filed, address compliance even if a Del Ret is not indicated using the procedures provided in IRM 5.14.1.4.2 (9). This ensures compliance is addressed when Del Ret case creation has not yet occurred. Del Rets are created within sixteen (16) months of due dates of returns.

  9. If Del Rets were resolved by one of the following methods, the closure is not considered evidence of compliance for the purposes of entering into an IA:

    1. Surveyed

    2. Shelved

    3. Unable to locate

    4. Referred to Exam or SFR (unless the assessment is pending or the case is assigned)

  10. If Del Rets were resolved by a closure listed in IRM 5.14.1.4.2(9)a – d, but it is determined that they could have been closed as provided in IRM 5.14.1.4.2 (12), then input (or request input of) appropriate transaction and closing codes. In these situations IAs may be granted when closing Del Rets.

  11. If an IA is the appropriate case resolution, and there is an open Del Ret on another tax module, the IA may be granted when:

    1. Tax return(s) indicated as due are filed.

    2. Del Rets are resolved using the dispositions listed in IRM 5.14.1.4.2 (12).

    3. Del Rets are resolved using the dispositions listed in IRM 5.14.1.4.2 (13).

  12. IAs may also be granted when the following closures are present:

    1. No return secured – little or no tax due, see Policy Statement P-5-133 found in IRM 1.2.1.6.18, Policy Statement 5-133, Delinquent returns - Enforcement of Filing Requirements.

    2. No return secured – taxpayer due refund.

      Note:

      If the taxpayer is due a refund, which still may be credited within the refund statute, inform the taxpayer to file the refund return before the refund statute expires to reduce the balance due on the IA.

  13. If taxpayers are not required to file returns, close those modules using the appropriate transaction and closing codes. The return closing codes that indicate filing compliance, or that filing is not required, are contained in IRM 5.1.11.8.3, No Return Secured Taxpayer Not Required To File For This Period Only, and IRM 5.1.11.8.4, No Return Secured Taxpayer No Longer Required to File (Final). Also see SERP - Document 6209 - Section 11, Collection definitions.

  14. If taxpayers are required to file returns and these returns are not filed, IAs cannot be granted or approved. See IRM 5.1.11.8, Delinquent Return Investigation Closures, for closing procedures for delinquent return accounts. Also, see SERP - Document 6209 - Section 11, Collection definitions.

  15. If Del Rets were closed with a transaction code that does not indicate filing compliance, request that returns be filed within a reasonable time frame.

  16. See IRM 5.1.11.5, Cases Requiring Special Handling, for exceptions and guidance regarding the filing of returns.

  17. Compliance checks based on case information:

    1. Except in the situations described in IRM 5.14.1.4.2 (7) and IRM 5.14.1.4.2 (8) above, further compliance investigation is neither required nor prohibited, if Del Ret status is not indicated on IDRS. In addition, unless there is a Del Ret, no CFOL review (and no IRPTR review) is required.

    2. If further research is conducted and there is an indication a return is due, then address filing compliance prior to granting the IA. Do not grant an IA if the taxpayer is liable for an unfiled Balance Due return. See IRM 1.2.1.6.18, Policy Statement 5-133, Delinquent Returns - Enforcement of Filing Requirements. If further investigation shows the taxpayer may be due a refund, apply the refund return determinations and dispositions in IRM 5.14.1.4.2 (12), when appropriate.

  18. The compliance checks described in this section are conducted to determine eligibility for IAs after they are requested by taxpayers. If the taxpayers do not file the requested returns by the provided deadlines (and the circumstances described in IRM 5.1.11.5, Cases Requiring Special Handling, do not apply) requests for agreements will not be identified as pending (rejection and independent review are inapplicable) and agreements will not be granted.

  19. Analyze the current year’s anticipated tax liability. If it appears a taxpayer will have a balance due at the end of the current year, the accrued liability may be included in an agreement, see IRM 5.14.1.4.5. Compliance with filing, paying estimated taxes, and federal tax deposits must be current from the date the IA begins. Use Agreement Locator Number (ALN) XX32 (see Exhibit 5.14.1-2).

    1. If the taxpayer’s withholding is insufficient, emphasize the importance of adjusting Form W-4, Employee’s Withholding Certificate, to avoid future balance due situations. If personal (face-to-face) contact with the taxpayer is made, calculate the current amount of withholding with the taxpayer. With the taxpayer’s concurrence, prepare a new Form W-4, Employee’s Withholding Certificate, for signature. Mail the signed Form W-4, Employee’s Withholding Certificate, to the taxpayer’s employer.

    2. Advise the taxpayers to make estimated tax payments and/or federal tax deposits (FTDs) if required.

    3. Advise the taxpayers that failure to make timely estimated tax payments and/or FTDs may result in penalties.

    4. Advise the taxpayers that future compliance with tax laws is required. Any returns and/or taxes due within the period of the agreement must be filed and paid timely.

    5. Advise the taxpayers that federal tax refunds are subject to offset to pay balance due accounts during IAs, including refunds from income taxes of individuals whose sole proprietorship or partnerships owe taxes and have IAs. In these cases, ensure TC 130 is input for the appropriate SSNs.

    6. Advise the taxpayers that if the owner of a single member LLC is identified as the liable taxpayer, any federal tax refunds payable to the owner are subject to offset to pay balance due accounts during IAs, including refunds from income taxes of an individual, corporation, or other entity where the owner owes taxes and has an IA. In these cases, ensure TC 130 is input for the appropriate SSNs or EINs.

Notice of Federal Tax Lien and Installment Agreements (Payment Plans)

  1. Prior to granting IAs, ensure the government’s interest is protected. This includes filing and refiling Notices of Federal Tax Lien (NFTL), if necessary. See IRM 5.12.2, Notice of Lien Determinations, regarding NFTL filing determinations.

    1. An NFTL determination must be made on all cases meeting the criteria of IRM 5.12.2.6, NFTL Filing Criteria. In general, accounts that do not qualify for guaranteed installment agreement, simple payment plan, or simple payment plan (business trust fund) processing require NFTL determination.

    2. When filing an NFTL, in connection with an IA, advise taxpayers in advance of the plan to file the NFTL and give them the opportunity to make full payment or modify the IA to meet the non-filing criteria in IRM 5.12.2, Notice of Lien Determinations.

    Reminder:

    If the taxpayer disagrees with the proposed NFTL filing, advise the taxpayer of the right to appeal under the Collection Appeals Program (CAP). Also, explain to the taxpayer the right to request a Collection Due Process (CDP) hearing under IRC 6320 after the notice is filed. See IRM 5.12.6, Appeals Processes Involving Liens.

    Reminder:

    If an NFTL is on file for the taxpayer and a third-party forecloses on its mortgage or lien, the IRS may authorize the Department of Justice (DOJ) to counterclaim (see 26 CFR 6159-1(f)(3)(ii), Effect of installment agreement or pending installment agreement on collection activity - Other actions by the IRS while levy is prohibited - Proceedings in court).

    Example:

    The IRS may file a claim to the surplus proceeds from 28 USC 2410 action (see IRM 5.17.5.18.11(1), Surplus Proceeds) or pursue a redemption of the property if appropriate (see IRM 5.17.5.18.12(1), The Redemption Price.)

  2. NFTLs may be filed:

    • While IAs are pending

    • In connection with granting IAs

    • During the rejection process

    • During the default/termination period

      Note:

      See IRM 5.14.11.5(1)f, Considerations after Default or Termination, Including Reinstatement, and IRM 5.14.11.6, Lien Determinations: Defaulted/Terminated Installment Agreements, regarding filing NFTL during defaulted and/or terminated IAs.

  3. Though it is not general practice to do so, NFTLs may be filed after group manager approval is received:

    • While IAs are in effect.

    • During appeals of rejections, defaults and terminations (inform Appeals of this plan).

      Note:

      NFTLs should only be filed if exigent circumstances exist (i.e., the taxpayer is liquidating or placing assets beyond the reach of the government). Group manager approval is required for NFTLs filed in accordance with (3) above. Review IRM 5.14.11.6, Lien Determinations: Defaulted/Terminated Installment Agreements, prior to filing these NFTLs.

  4. If an NFTL will be required on pre-assessed tax period(s), the request for NFTL filing must be manually submitted on Form 12636, Request for Filing or Refiling Notice of Federal Tax Lien, to the Centralized Lien Operation (CLO) once the tax period is assessed and ten days have passed. CCP will NOT hold or process any request for NFTL filing on a pre-assessed period submitted with an IA.

Increases, Decreases, Varied Payment Amounts; Completing and Processing Installment Agreements (Payment Plans)

  1. The amount of the taxpayer’s payment depends on their ability to pay. See IRM 5.14.1.4 (5).

    1. Only equal monthly IAs can be monitored on IDRS. However, inform taxpayers that extra payments or higher payments can be accepted at any time.

    2. Space is provided on Form 433-D, Installment Agreement, and Form 2159, Payroll Deduction Agreement, for scheduled increases or decreases in payment amounts. IDRS will accept two changes in payment amounts when agreements are input for systemic monitoring. Agreements with more than two scheduled payment changes must be manually monitored. Document reasons for any scheduled increases or decreases. Reasons can include expected full payment of a loan that will increase the taxpayer’s ability to pay; income is scheduled to increase or decrease; or necessary living expenses are scheduled to increase or decrease. See IRM 5.15.1.11, Other Expenses.

  2. Agreements may include an increase of one or two large payments to fully or partially pay accounts if it is documented and verified taxpayers will receive funds to make the payments. These payments may be represented as increases in the installment payment amount as discussed in IRM 5.14.1.4.4(1)(b). Situations that may call for this type of agreement include:

    • Contract sales with determined payment date(s) Judgments resulting in fixed settlement and payment dates

    • Beneficiary, distributee or payee status in trusts, estates, or profit sharing plans resulting in expected payment(s) on certain date(s)

    • Accrued equity in assets from which taxpayers plan to borrow when the monthly payment is scheduled to increase

    • Other projected receipts of funds

  3. Payment schedules may incorporate varied payments. Support varied payment schedules with documentation. Examples of reasons for varied payment schedules include, but are not limited to:

    • Anticipated fluctuations in business cycles for businesses or "commission" employees

    • Contract employment

    • Self employment

    • Seasonal employment

    • Seasonal expenses (for example, child-care costs when school is out)

    • Planned (scheduled) changes in employment status, such as plans to work part-time, or reduced schedules, especially if the changes are made in order to facilitate a parent staying home with children, even if this means making numerous changes to monthly payment amounts over a period of time

  4. For all agreements: request that the taxpayers select a day of the month, from the 1st through the 28th, for the payment due date. Advise the taxpayers:

    1. On IDRS monitored agreements, a monthly payment reminder notice (CP 521) will be mailed to taxpayers two cycles before each payment due date, except in the case of DDIAs. A pre-addressed envelope is included with the notice. In the case of payroll deduction IAs (PDIAs), inform the taxpayer that even though the payments are being sent by their employer, they will receive a monthly reminder notice for their records.

      Note:

      For PDIAs, advise the taxpayer to forward all payment reminder notices to the employer. Notice CP521 is not programmed to automatically send monthly reminder notices to the employer in relation to PDIAs.

    2. To send payments according to the terms of agreements, even if no reminder notice is received.

    3. In the absence of pre-addressed envelopes, payments can be mailed to the campus address that services the area, i.e., Internal Revenue Service, city, state, and zip code of the appropriate SB/SE or Taxpayer Services (TS) campus.

    4. To write the taxpayer’s name and SSN/EIN on the front of each check if the taxpayer did not receive a reminder notice. Write the type of tax, the tax period, and “Installment Agreement” on the check. Checks should be payable to U.S. Treasury. See IRM 5.14.1.2 (5), and note that IA payments may not be designated. See IRM 5.14.7.5(1), Payments on Trust Fund Accounts During Approved In-Business Trust Fund Installment Agreements paragraph.

  5. The first payment date on the DDIA must fall between 5 and 8 weeks into the future, regardless of the selected payment due date of the month. The expectation is that the DDIA should be input into Status 60 within 30-45 days. Refer to IRM 5.14.10.4(7)c, Direct Debit Installment Agreement, for the timeframe when the first payment is scheduled to draft.

    Note:

    Effective 01/02/2025, the first payment date on the DDIA must fall between 3 and 5 weeks into the future, regardless of the selected payment due date of the month. The expectation is that the DDIA should be input into Status 60 within 30-45 days.

  6. Assign Agreement Locator Numbers (ALNs) in accordance with Exhibit 5.14.1-2. Use a multiple condition ALN when appropriate. Also see IRM 5.14.13 , Routine and Manually Monitored Installment Agreement Dispositions.

  7. List levy source information, including complete addresses, and ZIP codes on IA forms.

  8. An IA must be in writing. A written IA may take the form of a document signed by the taxpayer and the Commissioner (Form 433-D) or a written confirmation of an agreement entered into by the taxpayer and the Commissioner that is mailed or personally delivered to the taxpayer (Letter 2849 or Letter 2850).

    Note:

    Agreements approved using the ICS application will generate the appropriate written confirmation (Letters 2849 or Letter 2850). It is the revenue officer's responsibility to mail or deliver the letters to the taxpayer and document the method of delivery in ICS. Form 433-D must be signed by the taxpayer for direct debit agreements.

  9. Taxpayer signatures must be secured on all Forms 2159, Payroll Deduction Agreement. See IRM 5.14.10.3, Preparation and Distribution of Form 2159, Payroll Deduction Agreement. Also, though taxpayer signatures are generally not required on Forms 433-D:

    • Signatures on Form 433-D are required for direct debit agreements (attach a voided check or document on Form 433-D the account number and bank routing number for processing); and

    • They may be obtained when taxpayers are available during personal contact.

  10. Approval authority for IAs is provided in IRM 5.14.13 , Routine and Manually Monitored Installment Agreements. If approval cannot be secured while taxpayers are present, advise them that proposed IAs must be approved. See IRM 5.14.1.2 (5) and IRM 5.14.3.2, Setting Deadlines and Receiving Payments, regarding requests for payments in the interim, and IRM 5.14.1.3 regarding necessary inputs to IDRS. Submit agreements for approval before any payments are due. If there are delays in the approval process, notify taxpayers.

    1. Thoroughly consider the taxpayers’ rights and interests prior to recommending rejection of an IA request. Consider the circumstances presented by the taxpayer, the information provided in support of approval, and the independent review criteria in IRM 5.14.9.2.2(3) , Independent Administrative Reviewer Responsibility. Although the taxpayer should be informed that the rejection of the agreement is being recommended, do not convey actual rejection of a proposed agreement prior to IAR except in the limited situations described in IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action. Also see IRM 5.14.9.2, Proposal to Reject Installment Agreement (IA) to Independent Administrative Review, regarding the independent review process.

    2. If additional information or action is required (for instance, an attempt to borrow is requested), then request the necessary information or action from the taxpayer and establish a reasonable action date. Explain the consequences of failure to comply with the request. If an action date is missed, refer the case to the IAR prior to conveying the rejection of the proposed agreement to the taxpayer. In general, no enforcement action may be taken as a consequence of such missed action dates, unless the situations described in IRM 5.14.1.5 (2) or in IRM 5.14.3, Deadlines, Payments, and Requests for Installment Agreements Made to Delay Collection, are present. See also IRM 5.14.9.2.1, Revenue Officer Responsibility, regarding IAR.

    3. While meeting or speaking with taxpayers, if taxpayers do not agree to payment amounts or increases in payments, advise them that a meeting with the next level of management may be requested. If the IA will be recommended for rejection, advise the taxpayer that the request remains pending, the proposed rejection is subject to IAR, and appeal rights will be provided if the request is rejected. Then forward the case to IAR. See IRM 5.14.9.2.1, Revenue Officer Responsibility.

  11. Inform taxpayers that the failure-to-pay (FTP) penalty is reduced on IAs if certain conditions are met. See IRM 5.14.1.2 (6).

Installment Agreements (Payment Plans) with Pre-assessed Modules

  1. For installment agreements with pre-assessed and prompted modules only, digitize the file and upload it to the ICS digital storage solution (DSS) platform for retention, along with Form 3210, Document Transmittal. These agreements cannot be systemically uploaded from ICS to IDRS. Pre-assessed agreements may be input to IDRS by Centralized Case Processing (CCP), before the assessment is made, via IDRS command code IAPND. Although this generally precludes the need for manual monitoring of these accounts, pre-assessed IAs may be monitored by CCP until all periods are assessed.

  2. Using Option A on ICS, IAs that include both assessed (ST. 26) and pre-assessed modules, can be systemically uploaded from ICS to IDRS. However, in order for the pre-assessed module to be included in the IA, you must complete the ICS template version of the Form 4844, Request for Terminal Action. In the "Remarks" section of this form include the following statement: "Please update ENMOD history to include pre-assessed module(s) xx-xxxxxx in installment agreement." CCP will process agreements that cannot be systemically uploaded. Attach the digitized Form 433-D, Installment Agreement, PDF file (if necessary) and send it by secure email. Respond "Yes" to having the document emailed to*SBSE PSC CCP DDIA. ICS will prompt you to complete Form 4844 prior to saving the IA request.

  3. Compliance Service Collection Operation (CSCO) is responsible for adding pre-assessed modules to agreements when they post and the accounts appear on the Installment Agreement Accounts List (IAAL).

    Note:

    ICS will automatically select the correct ALN when an agreement has more than one condition. The highest priority value will be used for the "YY" indicator. A "YY" Indicator of "32" identifies that pre-assessed modules are included in the agreement.

  4. Option B on ICS can also be used to request input of IAs that include both assessed and pre-assessed modules. Use the systemically generated Form 3210 to send the IA to CCP via secure email at *SBSE PSC CCP DDIA. Use IA Locator Number XX32 (see Exhibit 5.14.1-2). Ensure all account balances included in the agreement will be fully paid prior to the CSEDs plus allowable extensions. See IRM 5.14.2.2.3(3), Waiver Procedures for Partial Payment Installment Agreements, and IRM 5.14.2.2.1, Partial Payment Installment Agreement Requirements.

  5. If the agreement contains ONLY pre-assessed modules and the taxpayer requests a DDIA, process the IA under IRM 5.14.10.4, Direct Debit Installment Agreements, for regular DDIAs, or IRM 5.14.10.5, Direct Debit Installment Agreements for IBTF Cases, for IBTF DDIAs.

Levy Restrictions and Installment Agreements (Payment Plans)

  1. No levy may be made on taxpayer accounts:

    1. While requests for IAs are pending.

    2. While IAs are in effect.

    3. For 30 days after requests for agreements are rejected.

    4. For 30 days after agreements are terminated.

    5. While a timely appeal of a default, termination or rejection is pending or unresolved.

      Note:

      Criteria for identifying "pending" agreements are in IRM 5.14.1.3.

  2. Levies may be served during the periods described in IRM 5.14.1.5 (1) under the following circumstances:

    1. The taxpayer waives the restriction in writing (see Exhibit 5.14.1-3).

    2. Collection is determined to be in jeopardy (i.e., if a condition allowing a jeopardy assessment exists.) In these situations, CP 523, Notice of intent to levy Intent to terminate your installment agreement, (Letter 2975, Notice of Defaulted Installment Agreement Under IRC 6159(b), for MMIAs) is not required. Unless notice of the right to appeal was previously provided, the taxpayer must be notified of appeal rights after jeopardy levies. See Policy Statement 4–88 found in IRM 1.2.1.5.27, Policy Statement 4-88, Jeopardy assessments to be used sparingly and assessment to be reasonable in amount, for a list of conditions under which a jeopardy assessment will be made. See also IRM 5.11.1.4.8, Pending & Active Installment Agreements, for approval levels for jeopardy levies. The Approval level depends on whether the notices described in IRM 5.11.1.3.2, Required Notices, were sent, and if required waiting periods have passed.

    3. For balance due accounts not included in the current IA, new tax periods are not affected by the appeal period for defaulted IAs.

      Caution:

      In this context, "current" IAs include agreements in IDRS status 64 (default) because they remain in status 60 on Master File for the 13 cycles they are in status 64 on IDRS (until terminated and removed from status 60). Also, CDP notices and time frames must be provided to taxpayers on all balance due accounts before levies are served. See IRM 5.14.2.2.1 (regarding partial payment installment agreements) and IRM 5.11.1.3 (regarding pre-levy actions).

      Example:

      The taxpayer has an IA for payroll taxes for the periods ending September 30, 2023, and December 31, 2023. The period ending March 31, 2024, is not included in the IA and now has a balance due and all appropriate due process notices were mailed. The default Letter 2975 has been sent on the periods in the IA, but 90 days have not passed. In this example, although levies may not be served for those tax periods included in the agreement, levies may be sent to levy sources to collect on the balance due for the period ending March 31, 2024.

  3. If an IA is identified as pending and a levy is outstanding, it may be released, but it is not required that such levies be released. If an IA is approved, and there is a levy outstanding, it must be released unless the agreement provides otherwise. If an outstanding levy will remain in effect during an IA, document this in the "Additional Conditions" block of the agreement form. See IRM 5.11.1.4.8, Pending & Active Installment Agreements.

    Example:

    (1) A levy has attached funds in the taxpayer’s bank account, and an IA is prepared before the proceeds are received. If it is decided, with the concurrence of the taxpayer, not to release the levy, this must be written in the Additional Conditions block of Form 433-D.

    Example:

    (2) If a wage levy is to remain open while a taxpayer is making installment payments, it must be written in the "Additional Conditions" block of Form 433-D that the levy is to remain in effect until the liability is satisfied (or the levy is released). Situations where a wage or continuous levy is left in place during an IA may include, but is not limited to levies on mineral royalties or intermittent income not included in the income and expense analysis.

    Note:

    If the levy is to collect on a balance due account that is not included in an IA, then no release is required.

Multi-functional Installment Agreement (Payment Plan) Authority

  1. IRM 5.14, Installment Agreements, is primarily for use by Collection contact personnel. In addition, it is referenced by other functions for IA policy and procedures. This section provides cross-functional authority to grant IAs and references actions necessary in the IA process. Collection personnel should reference this section to learn about other functions’ IA authority and the types of assistance other functions may request.

  2. The authority to grant IAs has been extended to other contact functions within the IRS to improve one-stop service, reduce taxpayer burden, encourage voluntary compliance and utilize resources more effectively. The functions are: Appeals, Tax Exempt and Government Entities, Examination, Taxpayer Advocate Service, Submission Processing, and Field Assistance.

    Note:

    IRM 5.19 provides procedures for campuses, ACS and toll-free.

  3. Multi-functional IA authority is limited to certain types of accounts with an aggregate unpaid balance of assessments of ≡ ≡ ≡ ≡ ≡ or less.

    1. The authority is limited to individual accounts, corporate or LLC accounts in which the only open periods are Form 1120 modules, and out-of-business sole proprietor or LLC accounts in which the owner of the LLC is identified as the liable taxpayer.

      Note:

      (1) The limitation on dollar amount does not apply to agreements Appeals may consider under Collection Due Process or the Collection Appeals Program. See IRM 8.22.4, Collection Due Process Appeals Program, IRM 8.24.1, Collection Appeals Program (CAP), and IRM 8.22.7, Alternatives to Collection Action.

      Note:

      (2) Multi-functional IA authority does not extend to granting agreements in accordance with the procedures provided in IRM 5.14.2.2.1, Partial Payment Installment Agreement Requirements.

    2. See simple payment plan procedures for accounts with an aggregate unpaid balance of assessments (the CC SUMRY balance) less than or equal to $50,000 in IRM 5.14.5.2, Simple Payment Plans.

    3. See guaranteed IA procedures for accounts with income tax of $10,000 or less, in IRM 5.14.5.3, Guaranteed Installment Agreements.

      Note:

      This authority is limited to individual income tax accounts.

    4. See Simple Payment Plan (Business Trust Fund) for accounts with an unpaid balance of assessment (the CC SUMRY balance) of $25,000 or less, in IRM 5.14.5.4, Simple Payment Plans (Business Trust Fund).

      Note:

      This authority is limited to in-business BMF accounts.

  4. The authority to grant a Short Term Payment Plan Within 180 days is based on the Campus Collection function and the dollar criteria for requesting payment agreements. These Short Term Payment Plans may be granted for up to 180 days (Field Collection employees do not have authority to grant a Short Term Payment Plan Within 180 days). See IRM 5.19.1.6.3, Short Term Payment Plan Within 180 Days, regarding instructions and IRM 5.19.1.2.6, Case Processing Authority Levels, for authority levels for SB/SE campus employees.

    Note:

    Any taxpayer with an open employment tax filing requirement is considered "in-business" and is not eligible for this type of agreement.

  5. The multi-functional IA authority levels apply to assessed and pre-assessed accounts, including taxpayers who state an inability to pay when filing a return, whether on time or late.

  6. If taxpayers do not qualify for guaranteed installment agreement, simple payment plan or simple payment plan (business trust fund) processing, a CIS is required. Financial analysis may be done by the function initiating the agreement if sufficient expertise exists. See IRM 5.15.1, Financial Analysis Handbook, regarding financial analysis.

  7. Financial statements for cases that do not qualify for guaranteed installment agreement, simple payment plan, or simple payment plan (business trust fund) processing — require verification of income and expenses. Verification may be done by the function initiating the agreement if sufficient expertise exists. Research of local property records regarding real property, personal property, and motor vehicle ownership is not required.

  8. See IRM 5.14.1.4.3 regarding NFTL filing. NFTL filings will be requested from the Collection function on Form 12636, Request for Filing or Refiling Notice of Federal Tax Lien.

    Reminder:

    If an NFTL is to be filed, the taxpayer must be advised in advance.

  9. If the function initiating the agreement is unable to conduct financial analysis or verification, assistance will be sought from Collection personnel, or the taxpayer will be referred to Collection. The function initiating the agreement may assist the taxpayer in completing the CIS before referring the taxpayer to Collection.

  10. Upon identification of an IA request, document in the case file that the IA is "pending." , and ensure the criteria in IRM 5.14.1.3 are met before inputting the "pending" status.

  11. If a CSED extension is appropriate, see IRM 5.14.2.3, Collection Statute Expiration Date (CSED): Law, Policy and Procedures.

  12. IAs will be approved by the function that initiates the agreement, within that function’s authority. Completed forms will be routed as follows:

    1. All field functions initiating IAs will route completed forms to Centralized Case Processing (CCP).

    2. Appeals may input IAs secured within its function according to local guidelines (except Manually Monitored IAs). See IRM 8.20.7.20.18 , CDP/EH an Installment Agreement, and IRM 8.20.7.41, Installment Agreements (IA), for Appeals procedures.

    3. If the function initiating the agreement is not located in an area office or has made arrangements to send completed forms directly to a campus, then completed forms will be routed to CSCO for processing.

    4. If a campus secures an original IA and Form 900, Tax Collection Waiver, digitize and upload both forms to ICS-DSS for retention.

  13. If an account does not fall within the multi-functional guidelines or a function is unable to grant an IA for any reason, assistance will be sought from the Collection function or the taxpayer will be referred to Collection.

  14. If the proposed IA cannot be granted due to the taxpayer’s noncompliance with deposit or estimated tax payment requirements, failure to file required returns, or failure to provide information (within a reasonable deadline), follow IRM 5.14.9.2.1, Revenue Officer Responsibility, and IRM 5.14.9.3, Collection Appeals Program, as applicable, before referring the case to field revenue officer groups. See IRM 5.19.1.3.2.4, Revenue Officer (RO) Assignment.

  15. Local procedures should be developed by SB/SE Area Collection functions to accommodate other functions seeking assistance. Collection is responsible for the administration of IAs.

  16. Examination employees who receive an IA request from a taxpayer should follow the procedures in IRM 4.19.13.11, Taxpayer Replies, and IRM 4.20.1.4, Installment Agreements, for Examination Collectibility Procedures.

Input of Transaction Code 971 Action Codes 043 and 063 for Pending and Active Installment Agreements (Payment Plans)

These procedures apply to area offices, campuses and Automated Collection System (ACS) Call sites. Directors will designate employees responsible for specified inputs at a central location, or at the group, team, or unit level. Responsible functions must be continuously available to receive telephonic requests for input of TC 971, Action codes 043 & 063, during core business hours. Requested transaction codes must be input to IDRS immediately upon the request of contact employees.

Agreement Type Instructions
Pending Agreements
  1. Request TC 971 Action Code 043 be input to IDRS on ALL modules for which the taxpayer is liable within 24 hours. See IRM 5.14.1.3, Identifying Pending, Approved and Rejected IA Proposals on IDRS for additional guidance.

  2. If there are tax modules (accounts) that are not on IDRS (But are on Master File), request input of TC 971 AC 043 separately on these.

  3. Do not input TC 971 AC 043 for immediately approved agreements. See "Approved Agreements" below.

Approved Agreements
  1. A TC 971 Action Code 063 is systemically input to IDRS on ALL modules for which the taxpayer is liable for IA’s approved on ICS, see IRM 5.14.13.5, Manually Monitored Installment Agreements (MMIA’s), for additional guidance regarding the MMIA approval process.

  2. For the purpose of this subsection, approved agreements are only those agreements that are approved on the date the agreement is requested.

  3. If agreements are immediately approved there is no need to input TC 971 AC 043 for the period of time between the request for the agreement and the time it is approved.

For Rejected Proposals/Appeals
  1. Request reversal of TC 971 AC 043 forty-five (45) days after the rejection is communicated to taxpayers, unless during the 30 day period the rejection is appealed.

  2. During appeals, TC 971 AC 043 remains on all modules included in the proposed IA.

  3. If Appeals sustains rejections, input TC 972 AC 043 (if 30 days have passed) or 30 days after rejection is communicated to taxpayers.

  4. If Appeals grants IAs, follow the procedures above for approved agreements.

For Defaulted/Terminated Agreements
  1. IDRS:

    • Systemically reverses TC 971 AC 063 when there is a change from status 6X to any Master File status other than Status 26. This systemic reversal excludes the following types of IAs: Simple Payment Plan (Business Trust Fund), IBTF-IA, DDIA Simple Payment Plan, and DDIA IBTF-IA.

    • Generates TC 971 AC 163 to reverse TC 971 AC 063.

  2. Status 64 on IDRS remains in status 60 on the Master File for thirteen cycles. This provides taxpayers levy protection.

  3. During the first 30 days of Status 64 taxpayers may appeal proposed terminations to Appeals.

  4. Taxpayers may also appeal terminations of agreements for 30 days from the date agreements are terminated. See IRM 5.14.11.4, Defaults and Terminations: IDRS Monitored Agreements, regarding defaulted and terminated agreements.

Note:

Input of TC 971 AC 043 can be generated on ICS using the IA menu. This transaction will upload from ICS to IDRS. Any notice accounts or other accounts not in Status 26 should be created on ICS so that the transaction code can be properly generated.

The following transaction/action codes identify and reverse identification of pending and active IAs:

Transaction Code Action Code Definition
971 043 Identifies pending IA.
972 043 Reverses identification of pending IA (reverses TC 971 AC 043).
971 063 Identifies active IA.
971 163 Input to reverse identification as Active IA (reverses all TC 971 AC 063s).
972 063 Input to reverse identification as Active IA when TC 971 AC 063 was input in error.

Status 60, TC 971, IDRS, Master File (MF) interface information:

  • TC 971 AC 043 must be manually requested for input to IDRS for pending agreements

  • TC 971 AC 063 is generated by status 60, or may be manually input to IDRS

  • Any change from 6X (60, 61, 64) to any Master File status other than Status 26 generates TC 971 AC 163

  • Status 64 DOES NOT generate TC 971 AC 163. While accounts are in IDRS status 64, they remain in MF status 60. See "For Defaulted/Terminated Agreements" above)

  • When TC 971 AC 163 is input, it reverses the TC 971 AC 063.

  • If TC 971 AC 063 is not present, use TC 972 AC 043 to reverse TC 971 AC 043

  • TC 972 AC 063 reverses an erroneous input of TC 971 AC 063

Installment Agreement (Payment Plan) Locator Numbers — (ALNs)

Designate 4 digit ALNs (XXYY) to identify IAs by type and originator. The XX Position (first two digits) denotes either Initiator or Agreement Type. The XX values are:

Code Definition
00 Form 433-D initiated by AO on an ACS case
01 Customer Service Toll-Free initiated agreements
02 AO Field Territory (revenue officer) initiated agreements
03 Direct Debit agreements initiated by any function
06 Exam initiated agreements
07 Submission Processing initiated agreements
08 Agreements initiated by other functions
11 Form 2159 (Payroll Deduction Agreement) initiated by any AO, ACS or Customer Service
12 AO or ACS agreement with multiple conditions (except DDIA)
20 Status 22/24 accounts — Call Site/CSCO
30 Regular IA secured as a result of Withholding Compliance Case (WHC)
31 Simple Payment Plan secured as a result of Withholding Compliance Case (WHC)
90 CSCO initiated agreements — other than status 22 or 26
91 Form 2159 agreement initiated by CSCO
92 CSCO agreement with multiple conditions (except DDIA)
94 IA requested on Form 9465, Installment Agreement Request (except DDIAs).
99 Short Term Payment Plan (Up to 180 day extensions (NOT FOR FIELD))

The "YY" position (second two digits) denotes Agreement Conditions. "YY" values are:

Code Definition
08 Continuous Wage Levy (From ACS and RO)
09 All other conditions
12 Partial Payment Installment Agreement (PPIA) all functions
15 In-Business Trust Fund (IBTF) monitoring required for all functions
27 Restricted Interest/Penalty Condition Present
32 Unassessed modules to be included in IA
36 Simple Payment Plans $25,000 or less
37 Simple Payment plans $25,001 or greater
41 BMF In-Business Deferral Level (for CSCO USE ONLY)
53 Report Currently Not Collectible if agreement defaults (Backup 53)
63 Cross-Reference TIN (ST 63)
66 File NFTL in event of default
70 Secondary TP responsible for Joint Liability
80 Review and revise payment amount
99 Short Term Payment Plan; this is not an IA (NOT FOR FIELD)

Note:

If more than one condition exists, ICS will systemically use 12 in the "XX" position:

Exception: When any DDIA selection is made regardless of any other "YY" choices, ICS will systemically use 03 in the "XX" position.

The highest priority value will be used for the YY indicator. If multiple conditions exist, and one of the conditions below is used in the YY position, all other selected values will be systemically written in the Additional Conditions section of the Form 433-D and in the ICS history. This information will NOT be included in the additional conditions section of the taxpayer's Letter 2850 or Letter 2849. The cross-reference TIN information will be printed on the letter.

Priority Agreement Condition Value Definition
1. 63 Cross-Reference TIN (ST 63)
2. 12 Partial Payment Installment Agreement (PPIA) all functions
3. 53 Report Currently Not Collectible if agreement defaults (Backup 53)
4. 32 Unassessed modules to be included in IA
5. 15 In-Business Trust Fund (IBTF) monitoring required for all functions
6. 27 Restricted Interest/Penalty Condition Present
7. 36 Simple Payment Plans $25,000 or less
8. 37 Simple Payment Plans $25,001 or greater
9. 66 File NFTL in event of default
10. 70 Secondary TP responsible for Joint Liability
11. 80 Review and revise payment amount
12. 99 Short Term Payment Plan; this is not an installment agreement (NOT FOR FIELD)

Waiver of Restriction of Levy During a Pending or Active Installment Agreement (Payment Plan)

Form 13623, Waiver of Restriction of Levy During a Pending or Active Installment Agreement, is used to identify assets and levy sources that taxpayers request to have levied during a pending or active IA.

Installment Agreement (Payment Plan) Originator Codes

The table below is a complete list of IA originator codes:

Code Definition
20 Collection Field Function Regular Agreement
21 Collection Field Function Simple Payment Plan
30 Withholding Compliance Regular IA
31 Withholding Compliance Simple Payment Plan
50 Field Assistance Counter Regular Agreement
51 Field assistance Counter Simple Payment Plan
58 Field Assistance ICS Regular IA
59 Field Assistance ICS Simple Payment Plan
60 Examination Regular Agreement
61 Examination Simple Payment Plan
70 Toll-Free Regular Agreement
71 Toll-Free Simple Payment Plan
72 Paper Regular Agreement
73 Paper Simple Payment Plan
74 Customer Service Voice response unit (system generated)
75 Automated Collection Branch Regular
76 Automated Collection Branch Simple Payment Plan
77 Automated Collection Branch Voice Response unit regular (system generated)
78 Automated Collection Branch Voice Response unit Simple Payment Plan (system generated)
80 Other Function Regular Agreement
81 Other function Simple Payment Plan
82 Online Payment Agreement, Notice Status
83 Online Payment Agreement, ACS
90-99 Reserved For Vendors-all Simple Payment Plans
98 Special Compliance Personnel (SCP) program

Installment Agreement (Payment Plan) Table

The table below outlines the different agreements available and the conditions under which the IRS generally approves them.

This space intentionally left blank Guaranteed (IMF Only) Simple Payment Plan Simple Payment Plan (Business Trust Fund) IBTF Routine Partial Payment
Amount $10,000 or less $50,000 or less $25,000 or less Any Amount Any Amount Any Amount
Type of Tax IMF Income Tax Only IMF, Out of Business (OOB) Sole Proprietor, BMF Non-Trust Fund BMF Trust Fund BMF Trust Fund IMF, BMF Income, BMF OOB Any
Payment Terms Fully paid in 3 years, including accruals, by CSED Fully paid, including accruals, by CSED Fully paid, including accruals, by CSED Fully paid by CSED Fully Paid by CSED None (Determine if CSED extension is appropriate
CIS Required No No No(1) Yes(2) Yes Yes, Financial Review every 2 years
NFTL Determination Required No No No Yes Yes Yes
TFRP Determination NA No No(1) Yes Yes, If applicable Yes, If applicable
DDIA or PDIA Required No No No No No Yes if IA default in past 24 months
Extend CSED? No No No No No Up to 5 years plus 1 year if appropriate when an asset will come into possession of a taxpayer after the CSED expires
Must View Assets No No No Yes Yes Yes
Managerial Approval No No No Yes Yes Yes
Reference IRM 5.14.5.3 IRM 5.14.5.2 IRM 5.14.5.4 IRM 5.14.7 IRM 5.14.9 IRM 5.14.2

Simple Payment Plan (Business Trust Fund) criteria do not apply for business taxpayers when any of the following conditions apply:

Exceptions to Simple Payment Plan (Business Trust Fund) Criteria(1)
  • The payment plan request is made in conjunction with a request for levy release.

  • The case meets “Solely to Delay” criteria under IRM 5.14.3.3, Installment Agreement Requests Made to Delay Collection Action. This includes situations where there is an indication the business may be using pyramiding or successor entities to avoid tax responsibilities.


In these situations, ROs should proceed with financial analysis and TFRP determinations, as required.

For IBTF IAs, a CIS is required; however, verification is not required for agreements on accounts up to $25,000 that will full pay liabilities within 60 months.

IBTF CIS Verification Exception(2)
  • Verification of the CIS is not required for IBTF IAs up to $25,000 that will full pay within 60 months. See IRM 5.14.7.4(6).

To identify an agreement request as Pending IA, the taxpayer must:

Requirement Description
Taxpayer identification Provide information sufficient to identify the taxpayer’s name and taxpayer identification number (TIN).
Liability identification Identify the tax liability to be covered by the agreement.
Proposed payment Propose a monthly or other periodic payment in a specific amount.
Filing compliance Be in compliance with all filing requirements.
Collection Information Statement (if required) Provide a completed CIS, when required.
Bankruptcy limitation Not be in bankruptcy when requesting an agreement for post-petition liabilities, unless the request qualifies for a guaranteed IA for post-petition liabilities.
BMF pyramider/FTD compliance For BMF pyramiders, the taxpayer must be in compliance with all FTD requirements.