IRM 5.19.12 — Centralized Lien Operation

# Part 5. Collecting Process

Chapter 19. Liability Collection Section 12. Centralized Lien Operation 5.19.12 Centralized Lien Operation Manual Transmittal April 16, 2024 Purpose (1) This transmits revised IRM 5.19.12, Liability Collection, Centralized Lien Operation. Material Changes (1) 5.19.12.1.5. Added new paragraph (6) to reference standard retention policy for input requests. (2) 5.19.12.2.1.2. Separated information about co-obligors and POAs and reorganized subsection for flow. (1)-(3) describe when co-obligor information is needed and (4)-(5) describe when POA information is needed. (7)-(8) discuss inputting co-obligors on ALS and (9) discusses inputting POAs. Note was inserted to (10) to clarify that separate co-obligor and POA information does not need input when the taxpayers reside at the same address and share the POA. (3) 5.19.12.2.1.3. (1) Added bullet for assignment numbers used for NFTL requests from Campus OIC Units. (4) 5.19.12.2.1.1. (2) Split paragraph into two paragraphs to categorize the information. Renumbered subsequent paragraphs. (5) 5.19.12.2.5.1. (3) Clarified the tax period data to show on notices of federal tax lien for MFT 52 assessments, as addressed in IPU 22U0613. (6) 5.19.12.2.5.5. (4) Described the possible formats for the Jeopardy NFTL request. (6) Clarified how the SLID may be returned to the requestor. (7) 5.19.12.2.6. (4) Clarified Reminder about acceptable amounts to show on a refile. (8) 5.19.12.2.7.1. Changed title of subsection to more accurately reflect content. (1) Clarified that there is no set format for release requests from taxpayers. (3) Reworded to emphasize that the table is for determining what data to input for a release. (9) 5.19.12.6.1. (4) Inserted Note about possible electronic transmission of certified mail listings. (7) Qualified instructions are applicable as resources are available. Updated technology terms to what is currently available. (10) 5.19.12.2.7.6. Split (5) to emphasize approval authority. Inserted new paragraph (7) to direct CLO employees to forward revocation requests to the FORT for processing. (8) Added qualifying language to indicate not all revocations can be processed through ALS and cross-referenced guidance for manual revocations. (9) Added instruction to research the taxpayer's current. (11) Added instruction to note what the address where the taxpayer's copy of the revocation was sent. (11) 5.19.12.2.7.6.1. (2) Qualified that partial revocation requests should also be forwarded to the FORT. (12) 5.19.12.2.7.6.2. (2) Inserted new paragraph that manually prepared revocations should be forwarded to the FORT. (6) Modified to state that documents will have to be manually added to the billing support voucher. (13) 5.19.12.7.5. (2) Updated statement and reference for emailing data. (14) 5.19.12.7.5.2. (1) Clarified that manual preparation of payoff letters is preferred. (5) Inserted note about working requests returned from the referred function. (7) Minimized references to ALS Payoff Utility. (8) Converted alpha list to a table and added examples. (11) Added instruction on handling MFT 35 assessments. (15) 5.19.12.7.5.3. (1) Clarified that CLO generally does not process payments. Referenced role of Campus Support in payment processing. (2) Inserted Note to clarify that the addresses shown belong to CLO and not Submission Processing. (16) 5.19.12.7.5.4. (3) Added qualifier for CLO to work release requests. (5) Added row to If/Then table for referring complex cases to the FORT or Advisory. (17) 5.19.12.12. (2) Updated table with the current status of electronic filing offices. (3) Removed example as it uses process that is currently inactive. (18) Editorial changes made throughout to update links, revise references, and correct grammatical and formatting issues. Effect on Other Documents This IRM supersedes IRM 5.19.12, dated September 9, 2021, and incorporates Interim Procedural Update (IPU) 22U0613, dated May 5, 2022. Audience SBSE Collection Centralized Lien Operation Effective Date (04-16-2024) Rocco A. Steco Director, Collection Policy Small Business/Self Employed

# Program Scope and Objectives

5.19.12.1 (09-09-2021) Program Scope and Objectives The Notice of Federal Tax Lien (NFTL), as described in IRC 6323, is a public notification of the government's claim against the taxpayer's property for a tax debt. NFTLs are controlled through the Automated Lien System (ALS). The Centralized Lien Operation (CLO) has primary responsibility for inputting NFTL-related requests to ALS, processing lien documents generated by ALS, and maintaining the inventory of NFTLs on ALS. CLO is also responsible for answering NFTL-related questions from internal and external customers. Purpose: This Internal Revenue Manual (IRM) section provides instructions for CLO in preparing lien documents, assisting customers with NFTL-related inquiries, and maintaining the accuracy of NFTLs on ALS. Audience: This IRM is primarily for CLO personnel, but is referenced by Field Collection and other IRS personnel who work with lien documents or handle inquiries involving NFTLs. Policy Owner: Director, Collection Policy, Small Business/Self-Employed Division (SBSE). Program Owner: Collection Policy, Enforcement is the program office responsible for overseeing the lien program. Campus Collection has management oversight of the Centralized Lien Operation. Primary Stakeholders: SBSE Collection and Wage & Investment (W&I). Other functions that are affected by, or have input to, the procedures include Chief Counsel, Appeals, and the Taxpayer Advocate Service (TAS). Program Goals: Provide policy and procedural instruction to IRS personnel for processing NFTLs and related lien documents through ALS.

# Background

5.19.12.1.1 (06-03-2020) Background The federal tax lien, which is sometimes called the "assessment lien" or "statutory lien" , arises when a tax liability is assessed, demand for payment is made, and the taxpayer neglects or refuses to pay. While the federal tax lien establishes the claim of the government against the taxpayer's property, a Notice of Federal Tax Lien (NFTL) is needed for the federal tax lien to compete with certain classes of creditors. The NFTL is filed in the public record to put third parties on notice of the government's outstanding lien against the taxpayer's property and rights to property. The Automated Lien System (ALS) is used to generate NFTLs and provide controls for the inventory of NFTLs. ALS is also used to generate documents related to NFTLs such as amended NFTLs, lien releases, revocations of release, and NFTL withdrawals. CLO has primary responsibility for inputting information to, and processing lien documents generated by, ALS.

# Authority

5.19.12.1.2 (06-03-2020) Authority The authority for NFTL program is found in the following code and regulation sections. Code Section Regulation Description 26 USC 6321 §301.6321-1 Lien for taxes 26 USC 6322 no regulation Period of lien 26 USC 6323 §301.6323(a)-1 through §301.6323(j)-1 Validity and priority against certain persons 26 USC 6325 §301.6325-1 Release of lien or discharge of property 26 USC 6326 §301.6326-1 Administrative appeal of liens The following Policy Statements and Delegation Orders regulate NFTL filing. IRM 1.2.1.6.2, Policy Statement 5-2, Collecting Principles IRM 1.2.1.6.13, Policy Statement 5-47, Notices of lien generally filed only after taxpayer is contacted in person, by telephone or by notice IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates

# Roles and Responsibilities

5.19.12.1.3 (06-03-2020) Roles and Responsibilities The Director, Collection Policy is responsible for overseeing policy and procedures regarding NFTLs. The Director, Campus Collection is responsible for overseeing the management of CLO. CLO has primary responsibility for inputting information to, and processing lien documents generated by, ALS. Other major duties of CLO include the following: Processing ALS generated documents, including, but not limited to, Notices of Federal Tax Lien (NFTL), Certificates of Release of Federal Tax Lien, Withdrawals of Filed Notice of Federal Tax Lien, and Revocations of Release of Federal Tax Lien Processing requests for manual lien documents Certifying payment of recording fees Reconciling systemic issues identified by ALS error listings Maintaining ALS information tables Researching taxpayer accounts Responding to verbal and written communications from taxpayers, practitioners and other third parties Assisting IRS employees regarding non-technical ALS related issues Communicating verbally and in writing with taxpayers, taxpayer designees, recording officials, and IRS employees Employees authorized to make determinations regarding specific lien actions are responsible for ensuring procedures are properly followed. Managers are responsible for ensuring employees are duly delegated to perform lien actions and that they are in accordance with policy and procedures. Other roles and responsibilities related to the lien program can be found in IRM 5.12.1.5, IRS Organizations Working Lien Issues, and its subsections. IRM 5.12.1.6, Locations of IRM 5.12 Content, identifies IRM locations associated with NFTL determinations, filing, withdrawal, maintenance, and release. It is within the specific IRM sections that lien program responsibilities, instructions, and procedures are identified.

# Program Management and Review

5.19.12.1.4 (09-09-2021) Program Management and Review ALS electronically stores data regarding NFTLs. ALS generates numerous reports to monitor NFTL filings. See the ALS User Guide (https://irsgov.sharepoint.com/sites/SbCHqCids_ALS/Lists/ALS%20User%20Guides/Tiles.aspx), Chapter 15, ALS Logs and Reports, for a complete listing. Systemic counts of lien documents are included in the monthly Collection Activity Report (CAR). To facilitate the management of workload, CLO maintains counts for various work streams under its control. CLO also monitors the age of the work to ensure compliance with the time frames as stated throughout this IRM. A work item is considered "old" or "overage" if the item is not resolved within the specified time frame. Generally, the age computation of a work item starts the day after CLO receives the item. The CLO receipt date does not count as a business day. Note: Responsibility for counting work items and monitoring aging issues is determined by CLO management based on available resources. Reviews of CLO are conducted annually by Campus Policy. NFTL activity is reviewed and documented in numerous other ways, including those shown on the following table. Type Source Occurrence Description Audit TIGTA Annual "Statutory Review of Compliance With Notice of Federal Tax Lien Due Process Procedures" Audit TIGTA Annual "Trends in Compliance Activity" Report IRS.gov Annual NFTL program numbers are published yearly in the IRS Data Book: Collections, Activities, Penalties, and Appeals (https://www.irs.gov/uac/enforcement-collections-penalties-criminal-investigation), Table 25 Report TAS Annual The National Taxpayer Advocate, Annual Report to Congress includes aspects of the lien program. Monitor CFO On-going NFTL filing fees are monitored by the Chief Financial Officer (CFO) and SBSE budget offices. Review NQRS On-going NFTL quality is monitored for Field Collection through reviews conducted using the Embedded Quality Job Aid Field Collection standards identified with Attribute 410, NFTL Determination/Filing and IRM 5.13.1, Embedded Quality Collection Field Organizations Administrative Guidelines Review NQRS On-going NFTL quality is monitored for Campus through reviews conducted using the Campus Embedded Quality Review System. See the Campus Central Case Processing (CCP) knowledge book and IRM 21.10.1, Embedded Quality (EQ) Program. Review Policy Ad Hoc "Timeliness of Lien Releases, Quality Assurance Internal Compliance Review" (IRM 5.12.3.18, Review of Lien Release Timeliness) Review Policy Ad Hoc Centralized Lien Operational Review

# Program Controls

5.19.12.1.5 (04-16-2024) Program Controls IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates, stipulates the IRS positions authorized for lien activities. NFTLs are created and maintained through ALS. CLO is primarily responsible for updating and maintaining ALS data. Access to systems used in the NFTL process is controlled following standard access guidelines through the Business Entitlement Access Request System (BEARS, formerly Online 5081). The primary systems accessed by CLO are ALS and the Integrated Data Retrieval System (IDRS). Other systems or databases that may be used depending on the nature of the situation include, but are not limited to Automated Non-Master File (ANMF) Integrated Collection System (ICS) Account Management System (AMS) Integrated Automated Technologies (IAT) Accurint Netronline Note: User Guides for most of the systems referenced are available on the IRS intranet and should be consulted for specific instructions on their usage. There are numerous reports to monitor NFTL filings and ALS activity. See the ALS User Guide, Chapter 15, ALS Logs and Reports, for a complete listing of ALS reports. Closed records associated with NFTLs are retained in accordance with Document 12990, Records Control Schedules, the Internal Revenue Service Records Control Schedule (RCS 28), Tax Administration - Collection, Item 43, Notice of Federal Tax Lien and Certificate of Release of Federal Tax Lien. Input requests (e.g., Form 12636) generally are retained for 60 days for inventory control and quality review purposes, as consistent with Document 12990, Records and Information Management Records Control Schedules, the Internal Revenue Service Records Control Schedule (RCS 28), Tax Administration - Collection, Item 41(a)(2), Closed Taxpayer Delinquent Accounts (TDAs) and Taxpayer Delinquency Investigations (TDIs–TYD–14).

# Terms/Definitions/Acronyms

5.19.12.1.6 (06-03-2020) Terms/Definitions/Acronyms The table below differentiates key terms in the lien program. Term Definition Lien The federal tax lien that arises when tax is assessed, demand is made, and the liability is not paid. This is sometimes called the "statutory lien" or "assessment lien." Notice of Federal Tax Lien (NFTL) The document filed in the public record to put third parties on notice of the existence of the federal tax lien. One notice of lien can list as many as 15 individual statutory liens. Caution: The term "lien" is often used generically by external and internal customers when referring to the NFTL. Also, ALS routinely uses "lien" in its functional titles. Generally, CLO deals with the processing of the NFTL and related documents. For information regarding the legal distinctions between the NFTL and statutory federal tax lien, see IRM 5.12.1, Lien Program Overview, and IRM 5.17.2, Federal Tax Liens. A listing of common terms and acronyms used in the lien program is shown in Exhibit 5.19.12-2, Glossary of Common Acronyms and Terms for Centralized Lien Operation. The table below shows common acronyms used specially with ALS and lien document processing. Acronym Definition ALS Automated Lien System BSV Billing Support Voucher CLO Centralized Lien Operation CPS Correspondence Production Services CRD Court Recording Date CSED Collection Statute Expiration Date EFT Electronic Fund Transfer ELF Electronic Lien [NFTL] Filing FMS Financial Management Service FORT Field Office Resource Team IFS Integrated Financial System LFI Lien [NFTL] Filed Indicator NFTL Notice of Federal Tax Lien PLL Potentially Lost Lien [NFTL] SLID Serial Lien [NFTL] Identification WDAR Withdrawal of NFTL After Lien Release In addition to the acronyms above, the table below shows generic terms frequently used by CLO in lien document processing. Generic Term Common Reference County Recording office (e.g., county recorder) Court Recording office (also an ALS command) Field Field Collection Release Certificate of Release of Federal Tax Lien Revocation Revocation of Certificate of Release of Federal Tax Lien Spool ALS print repository Voucher Billing Support Voucher (also an ALS command) Withdrawal Withdrawal of Filed Notice of Federal Tax Lien Beckley Accounts Payable Financial Operation, a unit at the Beckley Finance Center

# Related Resources

5.19.12.1.7 (09-09-2021) Related Resources The form used to provide notice of the lien is Form 668(Y) (C), Notice of Federal Tax Lien. Other forms used in the lien program are listed in IRM 5.12.1.11, NFTLs and Certificates, and cited throughout this IRM. Note: Forms with a (c) suffix, e.g., Form 668(Y)(c), denote they are computer-generated. Not all forms generated through ALS contain the suffix. The presence or absence of the suffix has no bearing on the validity of the form. IRM 5.17.2, Legal Reference Guide for Revenue Officers, Federal Tax Liens, provides additional details about lien law such as the types of property subject to the federal tax lien and the priority of the federal tax lien versus other competing encumbrances. IRM 5.12.1, Lien Program Overview, provides additional information, websites, and job aids related to the lien program. The Automated Lien System (ALS) User Guide illustrates the steps for creating and maintaining lien documents. (https://irsgov.sharepoint.com/sites/SbCHqCids_ALS/Lists/ALS%20User%20Guides/Tiles.aspx) Links to tools and references to assist IRS employees with lien processes may be found on the SBSE Collection page on IRS Source (https://irssource.web.irs.gov/SBSE/Pages/Collection.aspx). Similar information for taxpayers may be found on the Understanding a Federal Tax Lien page on IRS.gov (https://www.irs.gov/businesses/small-businesses-self-employed/understanding-a-federal-tax-lien). This IRM is for procedural use and does not provide detailed instruction on the use of any system. User Guides such as the ALS User Guide should be consulted, as needed. Taxpayer rights with regard to IRS processes are stipulated in IRC 7803(a)(3) and on the Taxpayer Bill of Rights intranet page (https://irssource.web.irs.gov/SitePages/TaxpayerBillOfRights.aspx). Taxpayers' specific rights regarding lien processes are referenced throughout this IRM. IRM 10.5.1.6.9.3, Shipping through Private Delivery Carrier, provides guidelines for handling Personally Identifiable Information (PII). In carrying out its duties, CLO routinely deals with PII and must follow these procedures. Note: The filing of NFTLs and related lien documents in the public record is not subject to PII procedures.

# Integrated Automation Technologies (IAT)

5.19.12.1.7.1 (09-09-2021) Integrated Automation Technologies (IAT) Integrated Automation Technologies (IAT) tools simplify processing by assisting the user with IDRS research and input. The tools reduce the chance of errors and improve productivity. They are desktop productivity enhancing tools. CLO employees must use the IAT tools shown below whenever applicable for use. ID Number Tool 637 Credit Transfer 672 Disclosure Tool 848 Fill Forms 1147 Compliance Suite 4636 Payment Tracer/Tracer If a required tool is not used because it was determined to be not appropriate for a specific situation, document the reason in the case file. If an IAT tool is not available and/or an employee has a problem with the IAT Task Manager, the case should be processed through IDRS following established procedures. The IAT Share Point site (https://irs.gov.sharepoint.com/sites/IAT) should be checked periodically for new tools that may assist in processing cases. Descriptions of each tool, as well as job aids can be found on the web site.

# Lien Documents

5.19.12.2 (09-09-2021) Lien Documents The form and content of lien documents are established by the Internal Revenue Service by the authority of IRC 6323. ALS is the system used to maintain lien documents. IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates, stipulates the positions delegated the authority to file an NFTL and includes the following: Revenue Officers ACS Customer Service Representatives Offer Specialists Advisors Insolvency Specialists Certain Tax Examiners Note: See IRM 1.2.2.6.4 for specific authority within the described positions and other delegated positions. NFTL filing requests are received by ALS through the following methods: Systemically through ICS Systemic extracts from ACS Manual input directly on ALS ALS allows the creation of a number of lien documents, including the following: Form 668(Y) (C), Notice of Federal Tax Lien Form 668-F, Notice of Federal Tax Lien Refile Form 668-Z, Certificate of Release of Federal Tax Lien Form 12474, Revocation of Certificate of Release of Federal Tax Lien Form 12474-A, Revocation of Certificate of Release of Federal Tax Lien (self-releasing lien) Form 10916, Withdrawal of Filed Notice of Federal Tax Lien Form 10916-A, Withdrawal of Filed Notice of Federal Tax Lien after Release Note: ALS also produces partials of all the documents listed above except the Form 668(Y)(c). Certain guidelines must be followed when inputting data to ALS. Review input requests and reject any request with items that do not follow the guidelines established in this IRM. Explain in detail why the request is being rejected and what is needed to correct the request. Rejected requests must be approved by the team manager or lead tax examiner (TE). Lien documents and request forms are periodically updated. Due to programming constraints, updates to documents and forms may not occur for some time after the revision. For instance, a form revised in 2019 may not be available on all system templates until 2020. When there is a form revision, a transition period is established for the mandatory use of the form. Unless expressly stated, the prior revision remains effective during the transition.

# Notice of Federal Tax Lien Requests

5.19.12.2.1 (09-09-2021) Notice of Federal Tax Lien Requests An NFTL can be filed for any statutory lien with a balance due, provided filing is not legally restricted. Generally, the statutory liens (assessments) shown on the NFTL are those that carry their own statutory period for collection (CSED). For list of assessments that have their own CSED, see IRM 5.1.19.2.1, Transaction Codes That Carry Their Own CSED, or IRM 25.6.1.12, Collection Statute Expiration Date (CSED). NFTLs are most often requested systemically through ICS or ACS, but may also be requested manually on Form 12636, Request for Filing or Refiling Notice of Federal Tax Lien, or, in certain emergency situations, by telephone. For systemic requests, CLO is normally not involved in the creation of the NFTLs by ALS. For manual requests, CLO is responsible for inputting data to ALS to create the NFTLs. Upon receipt of the Form 12636, review the form for completeness, including the co-obligor and POA information. See IRM 5.19.12.2.1.2. Secondary Taxpayer/Co-Obligor and Power of Attorney. There are three sections that must be completed when creating an NFTL. When a request is received, review for the information shown in the table below. Section Information Needed within the Section Entity Taxpayer Identification Number (TIN) Taxpayer's name and address, including the name of the general partner when applicable Entity type, e.g., Individual, Sole Proprietor, Corporation, Partnership Business Operation Division (BOD), e.g., SBSE, W&I Tax Module Tax form, Civil Penalty code, or MFT 31, if applicable Tax period Assessment date Dollar amount of the unpaid balance of assessment Administrative Requester's name Requester's title Requester's assignment number Recording office where the NFTL is to be filed The ALS Create screen is used to create and generate NFTLs on ALS. The screen is divided into the same input segments as listed above for the requests. While completing the entity section, first enter the TIN. ALS will check the Delinquent Inventory/Account Listing (DIAL) and the ALS database for other entities under the TIN. Reminder: Consult the ALS User Guide, Chapter 4, Create New Liens, for creating an NFTL on ALS. Select the entity on ALS that matches the request or input the entity information as shown on the request. Incorrect information could make the NFTL ineffective and necessitate an amended NFTL be filed. ALS systemically generates the name control based on the taxpayer name input. Compare the name control shown on ALS to the taxpayer name line. Confirm the name control on IDRS and update ALS as necessary. This action will prevent the NFTL filing indicator (TC 582) from going unpostable. Note: It is very important that the information input to ALS is correct. The TC 582 and other transaction codes are delivered to Master File based on the information on ALS. If certain information is incorrect (i.e., TIN, Name Control, Type of Tax, or Tax Period), the codes will not post, which could cause delays in the systemic release of the lien. After the entity information, input the tax module data. If the DIAL located the entity and brought up the entity information it will also bring up the tax periods for which no NFTL has been filed. Verify the tax period data against the request. If the DIAL brings up a tax period that is not on the request, delete the tax period from the input screen. Alternatively, you may attempt to contact the requestor to clarify whether the tax period should be included on the NFTL. For tax periods not on the DIAL, input the tax period data from the request. Reminder: Consult the ALS User Guide for creating an NFTL on ALS. When inputting the assessment date for the tax period, remember NFTL After Original CSED (NAOC) and refile rules. See IRM 5.12.7.7.2, NFTL Filed After Original CSED (NAOC), and IRM 5.19.12.2.6, Refiling a Notice of Federal Tax Lien. If the assessment date is more than 10 years and 30 days in the past, an updated CSED must be input. Contact the requester if the updated CSED was not provided with the request. Failure to update the CSED will cause ALS to mark the tax period as expired and possibly generate a lien release. If the assessment date is nearing 10 years and 30 days old, an updated CSED is not needed; however, the requester should be reminded that the NFTL must be refiled before the "Last Day for Refiling" (10 years and 30 days). Failure to timely refile the NFTL will cause the lien to self-release. Note: Except for updating the CSED and/or addressing the pending refile, NAOC requests are input, printed, and processed following standard NFTL procedures. When making data entries to ALS, if an entry is readily recognized as one that will cause an unpostable (e.g., typographical error in tax period, inconsistent tax form), make the correction and notify the requester or contact the requester to clarify the information. If the request is incomplete or indiscernible or the requester cannot be contacted, return the request stating the reason for the rejection. Note: See IRM 5.19.12.2.1.1, NFTL Input Requirements, for common situations to avoid when creating an NFTL. After all tax period data has been entered, review the data for accuracy. Enter the Administrative information as requested on the input document. Enter the requester's information. If the requester is from ACS or Accounts Management, see IRM 5.19.12.2.1.3, ALS Assigned Numbers, for the assignment number table. Caution: Do NOT use the specific employee number of the ACS employee making the request. All other requesters should supply their employee assignment number (tsign) in their request. Note: NFTLs cannot be created without an employee assignment number. The employee must be established on ALS. ALS defaults to the recording office (or "court" ) assigned to the zip code of the taxpayer's address. If no recording office is specified on the request, use this default recording office. Occasionally the recording office will not populate on ALS. If this happens, check IDRS to ensure the zip code was listed on the request correctly. If the address on the request matches the address on IDRS except that the zip code is different, use the IDRS zip code. If the address on the request matches the address on IDRS and the zip code is the same, research the ZIP Code on the U.S. Postal Service web site (https://tools.usps.com/go/ZipLookupAction!input.action). Once the correct recording office is identified, ensure the recording office is not under a disaster area freeze. Also, ensure the recording office is not one where lien documents are no longer filed. If necessary and available, research MAINTXC on ALS to confirm the status of the recording office. If changes are needed, forward the zip code and the recording office information to the ALS coordinator to update the zip code table in ALS for future use. After confirming the recording office, the NFTL is generated and a Serial Lien Identification (SLID) number is systemically assigned. Input additional filing locations for the NFTL when requested. Input the information regarding the POA when applicable. Electronically filed NFTLs must be approved before the POA information can be entered. See IRM 5.19.12.12, Electronic Lien Filings (ELF). Fees charged by recording offices are assessed against the taxpayer as a TC 360. Included in the fee assessed are the charges for both filing and releasing of the lien. This upload from ALS to Master File is done on Friday morning and covers the NFTLs that were on vouchers from the prior Friday through Thursday. The fees assessed are based on the ALS fee tables, but are updated if the amount is edited on the voucher. This fee will be assessed against the oldest assessment from the modules on the NFTL. ALS will also send an NFTL filing indicator TC 582 for all periods on the NFTL. See IRM 5.19.12.9.1, TC 360 Rejects, and IRM 5.19.12.10, GUF Unpostables, for information regarding correction of unposted TC 360 and TC 582. Note: ALS also sends TC 971 AC 252 to indicate the issuance of the CDP notice. When an NFTL is suppressed from the voucher and from printing it is considered a manual filing. The prep date will be treated as a print date and the fees will be assessed as though it was on a voucher. The fees will be based on the court fee table. Creation of NFTLs on ALS must be completed within five (5) business days after receipt of the request. For inventory purposes, each SLID generated by ALS is counted as one NFTL. If a request is for two filing locations (e.g., county recording office and Secretary of State), that is two SLIDs and would count as two NFTLs. Time spent creating NFTLs is reported under OFP code 810-69080. If the request is made using the toll free phone number, use OFP 700–69000.

# NFTL Input Requirements

5.19.12.2.1.1 (04-16-2024) NFTL Input Requirements Certain input requirements for entity, MFT, and tax period data must be followed when creating the NFTL on ALS. The following are common situations to avoid during input. This list is not all inclusive. DO NOT CREATE AN NFTL WITH MIXED MODULES OR ENTITY TYPES, such as the following: Master File (IMF or BMF) and Non-Master File (NMF) liabilities on the same NFTL Both IMF and BMF liabilities on the same NFTL Joint and individual liabilities using a joint name line Civil Penalty modules using a joint name line MFT 31 modules using a joint name line Anything other than "MFT31" as the tax type when inputting NFTL for MFT 31 modules MFT 59 modules and other MFT type on the same NFTL Also, DO NOT CREATE AN NFTL with the following conditions: The liability is an Individual Shared Responsibility Payment (SRP) assessment, shown on IDRS as MFT 35 or mirrored assessment MFT 65. Note: SRP assessments are not subject to the filing of an NFTL. Return requests showing SRP assessments to the requester. An incorrect name control is shown. Note: See Document 7071, Name Control Job Aid for Individual Master File (IMF) Taxpayers, and Document 7071-A, Name Control Job Aid - For Use Outside the Entity Area, for help in determining the correct name control. The taxpayers' names on a joint liability are split between two lines. Reminder: Both names should appear on the first name line with "and" or "&" between the names to ensure both parties are systemically sent a CDP notice. If it is not possible for both names to fit on the first line, use NOTADD to input the Co-Obligor's information for the CDP notice. The taxpayer's zip code is located in a designated disaster area, as seen by a -O freeze on the IDRS account (see IRM 5.19.12.13.2, Disaster Relief). The tax type shows the abbreviation "CVPEN" (or variations) for a civil penalty assessment instead of the IRC Section number (e.g., 6672, 6721). Note: There may be limited situations where the use of CVPEN is authorized until ALS reference tables are updated with an appropriate code. Questions about the usage should be directed to the FORT. There are more than 15 assessments on one NFTL. An ALS-generated NFTL can show a maximum of 15 assessments, so multiple NFTLs will be needed. Requests are frequently received where there are multiple assessments under the same tax period (e.g., TC 150 and TC 290/300, multiple TC 240). In some of these requests, the outstanding liability may not be due from the initial assessment, but only from the subsequent assessment(s). In those instances, the information about the initial assessment can be excluded from the NFTL; however, it is permissible for it to be included. Contact the requester if clarification is needed. If the requester affirms their request or cannot be contacted, input the request as indicated by the requester. Note: When there are multiple assessments on one tax period, ALS combines the amounts of each assessment to show a total unpaid balance of assessment (UBA) for the tax period. Only the total UBA for the tax period appears on ALS and the printed NFTL, and it shows with the tax period's last assessment. The UBA fields for the tax period's other assessments appear blank or with zero. Requests involving NMF liabilities often require special handling because of the way modules are constructed on the NMF system. Looking at how the assessments were, or would have been, made on Master File can be a key to properly creating the NFTL. The type of tax on the NFTL should match the assessed liability. The MFT codes for NMF liabilities differ from those used for IMF and BMF liabilities (e.g., Form 1040 is MFT 30/31 on IMF and MFT 20 on NMF; Form 941 is MFT 01 on BMF and MFT 17 on NMF). For some MFTs on IMF/BMF, there is no direct NMF equivalent and research may be needed to confirm the proper type of tax to show on the NFTL. Example: A Trust Fund Recovery Penalty (TFRP) based is assessed under MFT 55 on IMF or MFT 13 on BMF, but on NMF it is assessed under the MFT of the underlying liability. So, a TFRP based on outstanding Form 941 liabilities is under MFT 17 on NMF and a TFRP based on outstanding Form 720 liabilities is under MFT 45 on NMF. See IRM 3.17.46.6.15, Trust Fund Recovery Penalties. Regardless of the MFT or account type, the NFTL should show the type of tax as 6672, i.e., the IRC code for TFRP assessments. The tax period on the NFTL must reflect the liability period. An NMF module only has one tax assessment. When there are multiple tax assessments on the same IMF/BMF module (e.g., TC 150/290/300, TC 150/240, multiple TCs 240), NMF sets up a separate module for each assessment using "dummy" periods starting with 195001. The NFTL must show the actual period for the tax liability, not the dummy period. Note: ALS does not systemically upload transaction codes for NFTL filings to Non-Master File. Occasionally, an NFTL may be requested for only the person listed second on a joint assessment (e.g., the primary taxpayer is in bankruptcy and the assessment has not yet split). In this situation, the primary taxpayer's SSN must be used to create the NFTL on ALS. Even though the name line only shows the secondary taxpayer, the assessment is under the primary taxpayer's SSN and that SSN is needed to establish the link between ALS and Master File. Normally, a tax assessment and its related penalty assessments are made for the tax period on the same date. These are not differentiated on the NFTL request and can be shown as one assessment for the tax period on the NFTL. Occasionally, the tax and penalty assessments are made on different dates. Any assessment that carries its own CSED should be listed separately on the NFTL. If an ALS response such as "duplicate lien" or "lien already filed" is received during input, review the request to ensure input accuracy. Contact the requester if questions remain. Reminder: The duplicate lien message most often appears when a subsequent NFTL is being created for the same assessments in a different location. In those situations, continue input of the request. When necessary data for input is missing, indiscernible, or is inconsistent with the conditions in paragraph (2) above, or you are otherwise unable to create the NFTL, reject the request back to the requester. Provide a detailed explanation of why the NFTL could not be created, advise the requester to resubmit a corrected request, and close the request. Reminder: Rejected requests must be approved by the team manager or lead TE.

# Secondary Taxpayer/Co-Obligor and Power of Attorney

5.19.12.2.1.2 (04-16-2024) Secondary Taxpayer/Co-Obligor and Power of Attorney A co-obligor is a person who is jointly and severally responsible for the tax liability such as a secondary spouse on a joint income tax assessment or the general partners for a partnership liability. The IRS is required by law to separately notify a co-obligor when an NFTL is filed with their name. Generally, ALS systemically recognizes co-obligor situations when the co-obligor is listed on the first name line of the NFTL with the primary obligor and their names are joined by "and" or "&." If the co-obligor is not listed in this manner (e.g., co-obligor on the second name line), the co-obligor information must be manually added to ALS to generate their notification. Example: If the NFTL name line shows "John & Jane" as the taxpayers, ALS systemically identifies Jane as a co-obligor. If the NFTL shows "John" on the first name line and "Jane" on the second name line, Jane's information as a co-obligor must be manually input to ALS. Other situations where co-obligor information may need input manually include: The co-obligor has a different address from the primary taxpayer The co-obligor has a different power of attorney (POA) from the primary taxpayer A power of attorney (POA) is someone authorized to represent the taxpayer. Duly authorized POAs must also be notified of NFTL filings against their clients. For systemic NFTL requests through ICS and ACS, POA information relative to the NFTL modules usually is systemically downloaded to ALS when the NFTL request is transmitted. There will be times, however, when it is necessary for CLO to manually input a POA on ALS, such as the following situations: The NFTL requester identifies a POA but their information has not yet posted to the Centralized Authorization File (CAF). The co-obligor has a different POA than the primary taxpayer. The NFTL is manually requested outside ACS or ICS. It is the responsibility of the requester of an NFTL to inform CLO of all POAs and co-obligors that are to be noticed. Form 12636 contains fields specifically for the requester to identify co-obligors and POAs. Exception: Requests to input information for co-obligors or POAs might be received after the NFTL was created and/or mailed for filing. Requests after the NFTL creation might not be on Form 12636. Item 5 of the Form 12636 should contain co-obligor information when any of the following issues are present: The co-obligor is not clearly identified in the taxpayer name line (see (2) above) The co-obligor has a different address than the primary taxpayer The co-obligor has a different POA than the primary taxpayer. If the Form 12636 shows a co-obligor in item 5 but does not show that co-obligor's name in the taxpayer name line (item 1 of the form), contact the requester for clarification. If the requester is not available, reject the Form 12636 and explain that co-obligors are only noticed if they are included on the NFTL. Item 4 of the Form 12636 indicates if a POA is involved with the case. Verify that item 4 has been addressed and, if applicable, specific POA information has been provided in item 5. Take action as noted in the table below. If... And... Then... Item 4 has not been completed (i.e., no box is checked) There is no POA information in item 5 Return the form to the requester for completion Item 4 has not been completed (i.e., no box is checked) There is POA information in item 5 Process the form based on the POA information provided Item 4 indicates there is no POA (i.e., "no" is checked) There is POA information in item 5 Return the form to the requester for clarification Item 4 indicates there is a POA (i.e., "yes" is checked) There is no POA information in item 5 Return the form to the requester for completion Item 4 indicates there is a POA (i.e., "yes" is checked) There is POA information in item 5 Process the form based on the POA information provided There is no item 4 as an older version of the form has been submitted (i.e., revision date before 8/2013) n/a Return the form to the requester for completion of the most recent revision. Co-Obligor and POA information is input to ALS using the literal command NOTADD. See the ALS User Guide, Chapter 6, RRA Notices, for input instructions. Remember the following when inputting the information. When the POA information is for a co-obligor, it is important to load the co-obligor information before loading the POA. Highlight the appropriate co-obligor's name on the NOTADD screen before inputting the POA information so the POA will receive notification of the NFTL filing for their specific client. Note: If the taxpayers live at the same address and have the same POA, the co-obligor and POA information does not need to be re-input. For NFTLs requested through ICS, POA information cannot be input until the NFTL uploads to ALS, which generally occurs the day after the request is made on ICS. If the NFTL is for a recording office where the filing is completed electronically, the NFTL must be approved for filing before the POA or co-obligor information is input to ALS. Filing approval must only be done on Tuesday and Thursday. See IRM 5.19.12.12, Electronic Lien Filings (ELF).

# ALS Assigned Numbers

5.19.12.2.1.3 (04-16-2024) ALS Assigned Numbers ALS employee assignment numbers are known by different names by the various operations. Field Collection, Advisory, Insolvency, and Field Offer In Compromise employees use their TSIGN (e.g., their ICS assignment number) for NFTL requests. This number is employee specific. ACS and Accounts Management (AM) employees do not use a TSIGN or an employee specific assignment number. NFTL requests from ACS and AM use a more generic number based on the BOD and site. Offer in Compromise (OIC) campus employees use a generic number for a management official at their location (25490000 for Memphis; 21490000 for Brookhaven). ALS assignment numbers for ACS and AM requests are constructed as shown in the table below. Requester's BOD Assignment number SB/SE The first two digits of the number will be the same as the area location followed by 000008. Example: 21000008 is the ACS site for SBSE Area 1. The first two digits will always default to the area the input person is logged into on ALS. W&I The first two digits of the number will be the same as the area location followed by 000000. Example: 11000000 is W&I Area 1. The first two digits will always default to the area the input person is logged into on ALS.

# NFTLs Hand Carried for Filing

5.19.12.2.1.4 (09-09-2021) NFTLs Hand Carried for Filing Employees generally request NFTLs systemically through ICS or ACS. If a systemic request is not possible, employees may request CLO create the NFTL by faxing or secure emailing a completed Form 12636, Request for Filing or Refiling Notice of Federal Tax Lien. See IRM 5.19.12.2.1, Notice of Federal Tax Lien Requests, for processing NFTL requests. Sometimes there is a need for immediate filing of the NFTL and the normal printing and mailing process will not suffice. These instances require the NFTL to be manually prepared and hand carried to the recording office. The originator is responsible for manually preparing the NFTL. See IRM 5.12.7.4, Manual NFTL Preparation. Employees who have access to ICS and are assigned the Bal Dues on ICS must use ICS to secure a SLID for the manually prepared NFTL. Note: When a SLID is created on ICS for a manually prepared NFTL, the information for the NFTL is uploaded to ALS and it shows as a new NFTL. This allows for subsequent input of the court recording data (CRD). If the employee cannot secure the SLID from ICS or the assessment is posted to IDRS but is within 10 calendar days, the NFTL must be input directly to ALS. Employees will request ALS input by submitting Form 12636 or by contacting CLO by phone and providing the necessary information. When requests are received for immediate issuance of a SLID, create the NFTL on ALS following standard input procedures, except as noted below. Suppress the printing of the NFTL by selecting "Off Voucher" and "N" for Print and Store options. Reminder: If the NFTL is printed as part of regular CLO processing it could result in a duplicate filing. Suppress the CDP notice after verifying that the requester will be issuing the notice. Use the requesting employee's TSIGN when creating the NFTL. If the Form 12636 is incomplete, contact the originator for clarification. If the originator is not available, reject the Form 12636 and explain in detail why the request is being rejected and what is needed to correct the request. After generating the NFTL on ALS, give the SLID to the requesting employee for use in filing the NFTL. Remind the employee to send the recording information to CLO for updating the ALS. This will prevent the NFTL from subsequently showing as a potential lost lien, which could lead to a duplicate filing and untimely release. When the originating employee indicates there is a POA for the taxpayer, verify whether the originator will be issuing the CDP notice to the taxpayer and POA. If the employee makes the request by phone, ask the employee whether there is a POA involved. If there is a POA and the originator is not manually issuing the notices, input the information into NOTADD to generate a copy of the CDP notice to the POA. Reminder: When the NFTL is in an ELF recording office, the POA cannot be input until approval of the ELF file has been completed. When a request is received for NFTL filing that is within 10 calendar days of the assessment and the assessment has not posted to IDRS, refer the request to the FORT. See IRM 5.19.12.2.5.5, Jeopardy NFTLs. If it is within 10 days of the assessment and the assessment has posted to IDRS, input the request to ALS following the procedures noted above. If an error is made while creating the NFTL and the NFTL was placed on the BSV, complete a BSV add/delete form and give to manager or lead TE. They will notify the team responsible for printing and mailing that state's lien documents to pull the NFTL from the batch. Explain why the NFTL is being pulled. Input a history on ALS to indicate the NFTL was manually input and is being hand carried for filing. Due to the urgency that necessitates hand-carried NFTLs, requests for SLIDs for hand-carried NFTLs should be input by CLO as soon as possible, but must be input within five (5) business days after the receipt date. Report NFTL requests using: OFP 810-69080, if received by paper, fax, or email OFP 700-69000, if received by phone

# Loading Previously Recorded NFTLs to ALS (SCREATE)

5.19.12.2.2 (04-28-2015) Loading Previously Recorded NFTLs to ALS (SCREATE) Taxpayers may call in to request a lien release for an NFTL that is not on ALS. This situation may be the result of the NFTL having been purged from ALS or manually filed with the recording office without being loaded to ALS. To generate a certificate of lien release through ALS, the NFTL must first be loaded to ALS. If a request for release of lien or a request for payoff of a lien is received and there is no record of an NFTL on ALS, the person making the request should supply a copy of the recorded NFTL. This is to ensure the lien is a federal tax lien, and to obtain the recording information needed for further action on the NFTL. See IRM 5.19.12.7.5.4, Request for Release of Lien, for more information. To recreate the NFTL on ALS use the SCREATE literal command. See the ALS User Guide, Chapter 4, Create New Liens, for instructions on SCREATE. Caution: Do NOT use the ALS CREATE function when SCREATE is appropriate. Note: When the NFTL was previously created on ALS and recorded, the NFTL must be re-input to ALS using SCREATE. See exception in paragraph (5) below. When recreating the NFTL on ALS, all information must be exactly the same as on the original NFTL. Use the SLID number from the copy of the NFTL supplied with the request. Occasionally a copy of an NFTL may be received where the NFTL was recorded with no SLID (e.g., manually prepared NFTL that was hand carried and no SLID was secured prior to the recordation). Search ALS to confirm that the NFTL was not previously loaded to the system. Once confirmed, take the appropriate action. If the NFTL is still active, use CREATE to load the NFTL. Change the Prep Date on ALS to match the date shown on the NFTL, suppress the printing of the NFTL, and remove the NFTL from the voucher If the NFTL is no longer active, use SCREATE to load the NFTL. Establish a SLID for the NFTL that does not duplicate another SLID already in use. Input a history explaining why the NFTL was created and that the SLID was created. Immediately after loading the NFTL to ALS, input the court recording data (CRD). Charge time for resolving lien and request creation requests to OFP 810-69080.

# Resolving Errors on NFTLs

5.19.12.2.3 (06-03-2020) Resolving Errors on NFTLs Errors on NFTLs can affect the priority of the lien. See IRM 5.12.7.9, NFTL Corrections. Also, errors impact systemic processes related to NFTLs such as the information sharing between Master File and ALS which relies on certain information matching (i.e., TIN, MFT, tax period, and name control). Information matching allows the lien indicator information to pass to Master File and for ALS to receive information such as updated CSED and satisfaction of a tax module. The process for resolving errors differs depending on whether the NFTL has been printed and the nature of the error. Before the NFTL is printed, it can be edited/corrected. After it has been printed, an amended NFTL or "Not To Be Filed" lien record (NTBFL) is needed. Note: The terms "corrected" and "amended" are often used interchangeably by the requester, but they are two different processes in ALS.

# Correcting NFTLs

5.19.12.2.3.1 (04-28-2015) Correcting NFTLs Any information on an NFTL can be corrected or edited on ALS until it is printed from the ALS print spool (Tuesday and Thursday). Once the CDP notice is triggered, the NFTL cannot be edited. If a correction can be made prior to printing, an Amended NFTL is not necessary. When receiving notification of an error, review the ALS print spool for the SLID number of the NFTL to see if it has been printed. If the NFTL has not been printed, edit the NFTL using the CORRECT function. See the ALS User Guide, Chapter 5, Resolving Lien Errors, for instructions. If the NFTL has been printed, an amended NFTL or NTBFL is needed, depending on the error. After an NFTL has been printed from the ALS spool, CORRECT will only allow a change to the name control. If the name control is the only correction that is needed, no amended NFTL is required. For NFTLs that were created in an electronic recording office, the approval of the ELF queue is equivalent to printing and mailing other documents. Once the approval is done the status of the NFTL changes from "new" to "approved elf" and the NFTL cannot be edited. When receiving notification of an error on an ELF NFTL, review ALS to see if the filing has been approved. If the ELF filing has not been approved, disapprove the NFTL from the queue and input the correction. If the ELF filing has been approved, an amended NFTL or NTBFL is needed, depending on the error.

# Amended NFTLs

5.19.12.2.3.2 (06-03-2020) Amended NFTLs After the NFTL is printed (or approved for an ELF recording office), errors on an NFTL are fixed by amending the NFTL or creating a NTBFL on ALS. The nature of the error determines which is needed. IRM 5.12.7.9.2, Correcting the Filed NFTL, provides details on which should be requested and is summarized in the following table. Type of Error Resolution Needed Name of Taxpayer Amended NFTL Name Control Correct on ALS Taxpayer Address No change to NFTL Tax Period Amended NFTL Assessment Date Amended NFTL TIN Not To Be Filed lien record Dollar Amount Amended NFTL only if significant error Filing location New NFTL DO NOT use the amend function to add a name to an NFTL. The name line should only be amended to clarify the taxpayer's name already on the NFTL or remove the name of a non-liable person/entity. An NFTL should not be amended to show a new person/entity. A new NFTL should be requested for that new person/entity. When amending an NFTL that included multiple tax periods, do not include any tax periods that have been satisfied. The amended NFTL should only reflect the tax periods that currently have a balance due. In order to amend an NFTL, recording information is needed on the original NFTL. If no CRD has been input to ALS, use the best research method available to locate the recording information and update ALS accordingly. If unable to locate the recording information, notify the requester and ask them to obtain the information before resubmitting the request. For step by step instructions on how to generate an amended NFTL on ALS, see the ALS User Guide, Chapter 5, Resolving Lien Errors. When generating an amended NFTL, input a history on both SLIDs stating the reason the NFTL was amended, the name of the requester, and the cross-reference SLID. Amended lien documents will remain in paper format for electronic recording offices. The amend program will generate a print file for amended documents to send to these recording offices. The Court program will allow the input of recording information on these amendment SLIDs. Once CRD is input to the amended NFTL it will be converted to an electronic NFTL and the release will be electronic. In order for ALS to generate a print file, the recording office must be reassigned as a paper court. Contact the FORT for assistance. For the recording offices of USDC Boston and Secretary of State Connecticut, no paper lien documents are needed. Complete the amended NFTL on ALS and the document will show up as an amended NFTL on ALS for viewing. Amended NFTLs for Secretary of State California are completed in the same manner as non-electronically filed amended NFTLs. The ALS Amend program issues a new CDP notice based on the reason for amending. If changes are made to the tax period or assessment date, a Letter 3172 is generated unless the corrected tax module appears on another NFTL. In that situation a Letter 3171 will be generated. The CDP Notice generates when the amended document is printed. A CDP Notice does not generate for changes to the name, TIN, or name control. Amended NFTLs are worked within five (5) business days after the receipt date. OFP 810-69080 is charged for completing the amended NFTLs.

# Not To Be Filed Lien Record

5.19.12.2.3.3 (09-09-2021) Not To Be Filed Lien Record When there is an error in a field that does not impact the validity of the NFTL (i.e., error in TIN or MFT), a Not To Be Filed lien record (NTBFL) must be created to establish the link between ALS and Master File. For other errors, an amended NFTL is needed. See table in 5.19.12.2.3.2 above. NTBFLs, sometimes referred to as "dummy" liens, are created with the same information as on the original NFTL except with the corrected TIN and/or MFT. NTBFLs should only be input by CLO. Note: To reduce confusion, the NTBFL data should match the original NFTL except for the error(s) that was corrected. However, as long as the erroneous item is corrected to establish the link with Master File, it is not essential that the NTBFL contain all the other, correct tax period data that was on the NFTL. For example: An original NFTL included 15 modules and there was an MFT error on only one module. An NTBFL that shows only the one incorrect module and does not include the other 14 correct modules would be effective in establishing the link, but it could cause confusion to someone subsequently researching the NFTLs on ALS. NTBFLs are so named because they do not get filed. They are for internal use only. If a NTBFL is inadvertently printed, the history should be reviewed to determine appropriate steps. NEVER mail a NTBFL to a recording office. To create a NTBFL follow standard NFTL creation procedures in the ALS User Guide except as noted below. Suppress the NFTL from the billing support voucher (BSV). Suppress the CDP notice from printing. Select "Not To Be Filed" as the recording office (court number 721999). Input a history on the NTBFL and original SLID explaining the reason for the NTBFL and cross-referencing the SLIDs. Remember, this history needs to supply enough information so that a release for the original NFTL can be input when a release for the NTBFL is generated. Note: For other instruction on preparing NTBFLs, see the ALS User Guide, Chapter 5, Resolving Lien Errors. As the modules on the NFTL are satisfied, Master File notifies ALS, which updates the status of the modules on the NTBFL. The modules are also placed on the SATMOD report so that the module on the original NFTL can be marked as satisfied. This is to ensure no delays in the release of the original, recorded NFTL. After all the modules on the NTBFL have been satisfied a release will be systemically generated. The release will be placed into the print spool. When the release prints, the employee reviewing the lien documents pulls the release for the NTBFL and uses the ALS history information to request a release for the original NFTL. The release for the NTBFL can be discarded after use. Reminder: Not To Be Filed lien records or releases of NTBFLs must NOT be filed with any recording office. They are used to inform CLO of an action needed. OFP 810-69080 is charged for completing the creation of NTBFL.

# Duplicate Filings of NFTL

5.19.12.2.4 (04-28-2015) Duplicate Filings of NFTL A duplicate NFTL filing condition exists when: the same NFTL with the same SLID is recorded more than once at the recording office, or identical NFTLs with different SLIDs are recorded at the same recording office. Duplicate NFTLs might result from the recording office inadvertently recording both parts of the NFTL (i.e., the recording copy and the IRS copy) or from an NFTL being manually prepared and hand-carried for filing without the systemic printing of the NFTL being suppressed. They also can occur if duplicate requests are input to ALS. CLO may receive inquiries on duplicate NFTL situations from internal or external customers. Duplicate NFTLs are most often found when inputting recording data and it is discovered that recording data is already on ALS for the NFTL. Example: The NFTL (SLID 123456789) returned from the recording office shows Book 5 page 33. ALS already shows CRD for SLID 123456789 as Book 2 page 4. When conflicting information is found while inputting CRD for a SLID, double check the SLID to make sure the correct NFTL is displayed. If it is the correct NFTL, research Accurint, Netronline, or another appropriate website to determine if there is a duplicate NFTL filing. If it is determined that the recording information on ALS is incorrect, there is not a duplicate filing. Correct the recording information on ALS through "maintenance." Note: Check with your manager to find out if you are profiled for correcting CRD. If it is discovered that part one and part two of the NFTL were inadvertently recorded, input the recording data on ALS for the first part filed and take actions to address the duplicate filing (described below). Also, check other NFTLs on the voucher to ensure they were not filed in duplicate. If a duplicate NFTL filing situation is found, identify the requester of the NFTL and try to determine the basis for the duplicate situation. CLO resolves situations where the same NFTL with the same SLID was recorded in duplicate and there is no field assignment. Other situations should be referred to the assigned employee or Advisory, if appropriate, for resolution in accordance with IRM 5.12.7.10.4, Duplicate NFTL. When there is a duplicate NFTL where the SLIDs are the same and no field assignment, prepare Letter 2440, Certificate of Duplication of Federal Tax Lien, showing the recording information of the original and duplicate NFTL. Issue Letter 2440 to the recording office for association with the duplicate filing. Note: Depending on the reason for the duplicate filing, a fee may be charged for recording the letter. Send a copy of the Letter 2440 to the taxpayer and their representative, if applicable, notifying them a duplicate NFTL was filed. The taxpayer does not need to file the letter but should retain it for future reference. In certain situations, it may be appropriate to re-create the duplicate NFTL on ALS. Generally this occurs only at the direction of the employee assigned the taxpayer's case. Re-create the duplicate NFTL on ALS following the steps below. Using SCREATE, assign a new SLID and input the information as it appears on the NFTL. See IRM 5.19.12.2.2, Loading Previously Recorded NFTLs to ALS (SCREATE). Input a history stating the NFTL is a duplicate and what the "true" SLID number is. Input the recording information on the Court screen. Input a TC 582 for the duplicate filed NFTL. No TC 360 should be input. Document ALS history with actions taken regarding duplicate NFTLs. The history should sufficiently reference recording information of the duplicate NFTL, if it is not otherwise captured on ALS.

# Special Types of Notices of Lien

5.19.12.2.5 (09-09-2021) Special Types of Notices of Lien CLO receives manually prepared notices of lien from Field Collection, Advisory, and LB&I International. The documents include, but are not limited to, the following: Notices of Estate Tax Lien Special Condition NFTLs, which may have a specific property description typed on the face of the document Restitution-Based Assessment NFTLs Mutual Collections Assistance Request (MCAR) notices of lien Jeopardy NFTLs The extent of the information from these lien documents that is loaded to ALS varies. However, the documents are filed with their respective recording offices through CLO. Questions regarding other lien documents received should be directed to the team manager or lead TE or to the FORT.

# NFTLs for Estates

5.19.12.2.5.1 (05-12-2022) NFTLs for Estates The notice of an estate tax lien and the release of the estate tax lien are filed on the applicable forms listed below. Notices of estate tax lien are not created on ALS, or otherwise loaded to it. Form 668-H, Notice of Federal Estate Tax Lien Under Internal Revenue Code Section 6324B Form 668-I, Certificate of Release of Federal Estate Tax Lien Under Internal Revenue Section 6324B Form 668-J, Notice of Federal Estate Tax Lien Under Internal Revenue Code Section 6324A Form 668-K, Certificate of Release of Federal Estate Tax Lien Under Internal Revenue Section 6324A CLO receives manually prepared estate tax liens and releases from the Advisory Estate Tax Group. These documents are generally transmitted with a Form 3210. The FORT manages all estate tax lien and related documents. See IRM 5.19.12.8.2, Filing Estate Tax Lien Documents. In certain situations, a regular NFTL (Form 668(Y)(c)) can be filed against an estate. If a request is received for the creation of an NFTL against an estate, follow normal procedures to create the NFTL on ALS except as noted below. Include a "V" (or "W" for international accounts) after the SSN to indicate it's an estate. Input the taxpayer's date of death (DOD) as the tax period. Caution: ALS does not accept zeros (00/00/0000) for the tax period, which is how MFT 52 liabilities are reflected on IDRS. Note: The DOD can be obtained through cc INOLE. File a regular NFTL against the estate following standard procedures. If a call is received from an advisor regarding where to send an estate tax lien/release give them the address to the FORT.

# Special Condition NFTLs

5.19.12.2.5.2 (06-03-2020) Special Condition NFTLs A Special Condition NFTL (sometimes generically, and inappropriately, referred to as a "Nominee NFTL") is an uniquely-worded NFTL designed to protect the government's interest in an asset(s) that is in a third party's name. A Special Condition NFTL must be approved by Counsel and usually it is manually prepared by the revenue officer or Advisory. There are four main types of these NFTLs (Nominee, Alter Ego, Transferee, Successor-in-Interest), but Counsel may approve other variations on rare occasions. All Special Condition NFTLs have specialized name lines and certain ones (e.g., those for nominee or transferee situations) must contain additional wording that describes the property attached by the lien. Note: Detailed information about the types of special conditions and the preparation of the NFTLs can be found in IRM 5.12.7.6, Special Condition NFTL, and its related subsections. Special Condition NFTLs are forwarded to the CLO FORT for processing. If it has not already been done by Advisory or the RO, the FORT loads the Special Condition NFTL into ALS using the standard CREATE process with the exceptions noted below. Select nominee, alter ego, or "other special condition" as the entity type, depending on the condition. If the NFTL is manually prepared, suppress the NFTL from printing through ALS. If the NFTL will be hand-carried for filing by the RO, suppress the NFTL from the voucher. Additional actions to process the Special Condition NFTL may be necessary as shown in the following table. If the manually-prepared NFTL... Then... Does not have a SLID Insert the SLID generated through the CREATE process onto the NFTL. Is not being hand-carried for filing by the RO Add the NFTL to the BSV. Contains a property description of what the lien attaches Input an ALS history with an overview of the property description (e.g., property address, type of equipment). Once a Special Condition NFTL is ready for filing, it may be filed with the recording office via normal batch processing. Caution: Do NOT use batch processing if the RO is hand-carrying the NFTL for filing. When a recorded copy of a Special Condition NFTL is returned, input the CRD to ALS and forward the document to the FORT.

# Restitution-Based Assessment NFTLs

5.19.12.2.5.3 (06-03-2020) Restitution-Based Assessment NFTLs Restitution-Based Assessment ("Restitution") NFTLs are filed for restitution ordered by the court following the conviction of the taxpayer on a criminal tax violation or tax-related offense. These NFTLs contain special wording to indicate the nature of the assessment(s). These NFTLs can be printed through ALS or manually prepared by the revenue officer (RO). See IRM 5.1.5.18.2, Notice of Federal Tax Lien (NFTL) Filing on Restitution-Based Assessments (RBA), for additional information. Requests for Restitution NFTLs cannot be made through ICS. The requester must submit Form 12636 (or, if manually prepared, a copy of the NFTL) to CLO for input to ALS. Upon receipt of Form 12636, follow standard processes to review the request and input the information to ALS, with these exceptions: The type of tax must be the form involved in the restitution preceded by an "R" (e.g., R1040, R941). The assessments show on IDRS under MFT31, but that is not acceptable as a type of tax on the NFTL. Inclusion of the "R" is crucial for ALS to recognize the NFTL as a Restitution NFTL. Only restitution-based assessments may be included on the NFTL. Due to the special wording of these NFTLs, other types of assessments (e.g., 1040, 6672, etc.) must not be included. The number of entries in the tax form section is limited to 14 line items to allow space for the special wording. Restitution NFTLs generated by ALS should be printed and mailed following standard procedures. In situations where the NFTL will be hand-carried for filing, the requester must manually prepare the NFTL and contact CLO for a SLID. Upon receipt of a request for a SLID, use the standard CREATE process with exceptions for the following actions. Place an "R" in front of the tax form number to indicate the restitution situation (e.g., R1040, R941). Note: Inclusion of the "R" is crucial for ALS to recognize the NFTL as a Restitution NFTL. Ensure that only restitution-based assessments are included in the NFTL. Verify that the number of entries in the tax section does not exceed 14. Suppress the NFTL from printing through ALS. Suppress the NFTL from the voucher. Suppress the systemic CDP notification. Input a history to ALS about the manual preparation and filing. Provide the SLID to the requester. For Restitution NFTLs printed and filed by CLO, the CDP notice is systemically issued. For those manually prepared, the requester is responsible for issuing the CDP notice to the taxpayer and, if applicable, copying their POA.

# Mutual Collection Assistance Request NFTLs

5.19.12.2.5.4 (04-28-2015) Mutual Collection Assistance Request NFTLs MCAR notices of lien are created because certain tax treaties contain clauses under which the treaty partners can request assistance from the IRS in collecting taxes owed them by individuals residing in the United States. The mutual collection treaty partners are as follows: France Sweden Denmark Canada the Netherlands A MCAR notice of lien does not look like a regular NFTL and it is not input to ALS. It should come with a request explaining the lien document is to be filed and who needs to receive the recorded document back. The lien documents are placed in the normal batch processing. When these documents are returned from the recording office, forward them to the requester.

# Jeopardy NFTLs

5.19.12.2.5.5 (04-16-2024) Jeopardy NFTLs Occasionally, in special circumstances, a tax assessment is accelerated to expedite the normal assessment process. This generally is done when it is determined that collection of tax is at risk or the assessment statute expiration date (ASED) is imminent. There are four types of accelerated assessments: Jeopardy assessments Termination assessments Quick assessments Prompt assessments Note: See IRM 5.1.4, Jeopardy, Termination, Quick and Prompt Assessments, for details about each type. In many of these situations, it is necessary to immediately file an NFTL as soon as the assessment is made and notice is given. These are categorized as "Jeopardy NFTLs," regardless of the type of assessment. There are other situations when an accelerated assessment is not made, but it is necessary to file an NFTL before the assessment posts to IDRS. Although the situation differs, the NFTL request is also categorized as a "Jeopardy NFTL" because it is handled the same on ALS. See IRM 5.12.7.7.1, Jeopardy and Prompt Assessments. Jeopardy NFTLs must be manually prepared by the requester. NFTLs involving assessments that have not posted to IDRS will cause unpostables of the TCs 582, 360, and 971 AC 252. Jeopardy NFTLs are worked in the FORT. The requests may be in the form of a manually prepared Form 668(Y), Form 12636, or other accepted format. Any request for a Jeopardy NFTL received by a CLO team should immediately be forwarded to the FORT. Upon receipt of a Jeopardy NFTL request, the FORT creates a Not To Be Filed Lien record (NTBFL) on ALS. This allows for the generation of a SLID for the manually-prepared NFTL but prevents transaction codes from posting to IDRS. See further details in IRM 5.19.12.2.3.3, Not To Be Filed Lien Record. Reminder: Be sure to use OFF Voucher and STORE Only options. Caution: Termination assessments normally are made under Non-Master File (NMF) so the TIN must have an "N" suffix. Give the SLID to the revenue officer to affix to the manually prepared NFTL. If the Form 668(Y) was provided with the request, insert the SLID on the document before returning it to the requestor. Remind the requestor to return the recording data after the NFTL is hand-carried for filing. The requestor is responsible for issuing the CDP notice to the taxpayer and, as applicable, copying the POA. Input an ALS history identifying the NFTL as a jeopardy NFTL and monitor for the return of the CRD. When the CRD is received, take the actions below. Verify the assessment has posted to IDRS. Correct the court selection to the appropriate recording office where the NFTL was filed. Input the CRD. Advise the requestor to input the TC 360, 582, and 971 AC 252 to the module(s) as appropriate.

# NFTLs on Employee Benefit Plans

5.19.12.2.5.6 (09-09-2021) NFTLs on Employee Benefit Plans NFTLs may be requested for assessments made in relation to Form 5330, Return of Initial Excise Taxes Related to Employee Benefit Plans, and Form 5500, Annual Return/Report of Employee Benefit Plan. The process to create these NFTLs in ALS differs slightly from normal procedures. These NFTLs can be printed through ALS or manually prepared by the revenue officer (RO). Assessments made for Form 5330 appear on IDRS under MFT 76 and for Form 5500 under MFT 74. Whenever an assessment is made under either of these MFTs, a corresponding plan number is embedded in the assessment. Each plan has an associated three-digit plan number assigned by the employer/sponsor (e.g., 001, 002) and multiple MFT 74/76 assessments can exist for each tax period. Proper identification of the plan number related to the assessment is needed when creating the NFTL. Note: See IRM 5.12.7.7.6, Employee Benefit Plans, for additional information. Requests for NFTLs for MFT 74/76 assessments cannot be made through ICS. The requester must submit Form 12636 (or, if manually prepared, a copy of the NFTL) to CLO for input to ALS. Upon receipt of Form 12636, follow standard processes to review the request and input the information to ALS, with the exceptions noted below. Form 5330 / MFT 76 Assessments Form 5500 / MFT 74 Assessments The type of tax must be the plan number associated with the assessment, preceded by an "E" (e.g., E001). The type of tax must be the plan number associated with the assessment, preceded by a "P" (e.g., P001). Only MFT 76 employee benefit assessments should be included on the NFTL. Only MFT 74 employee benefit assessments should be included on the NFTL. Note: The alpha prefix is crucial for ALS to recognize the NFTL as a MFT 74/76 assessment. When printed through ALS, the NFTL will convert the plan number to show Form 5330 or Form 5500, as appropriate. The plan number also facilitates the posting of the NFTL transaction codes to IDRS. Print and mail NFTLs generated by ALS for these assessments following standard procedures. In situations where the NFTL will be hand-carried for filing, the requester must manually prepare the NFTL and contact CLO for a SLID. Upon receipt of a request for a SLID, follow the standard CREATE process with exceptions noted below. In the type of tax field for Form 5330 / MFT 76 assessments, place an "E" in front of the plan number (e.g., E001). The requester must provide the plan information with the request. For Form 5500 / MFT 74 assessments, place a "P" in front of the plan number (e.g., P001). Ensure that only MFT 74 or 76 assessments are included on the NFTL. Suppress the NFTL from printing through ALS. Suppress the NFTL from the voucher. Suppress the systemic CDP notification. Input a history to ALS about the manual preparation and filing. Provide the SLID to the requester. For NFTLs printed and filed by CLO, the taxpayer's CDP notice is systemically issued. For NFTLs manually prepared, the requester is responsible for the issuance of the CDP notice and the input of all applicable transaction codes to IDRS.

# NFTLs During Bankruptcy

5.19.12.2.5.7 (06-03-2020) NFTLs During Bankruptcy When a taxpayer files bankruptcy, the automatic stay of the bankruptcy prohibits various collection activities, including filing new NFTLs for the tax liabilities that arose before the bankruptcy ("pre-petition liabilities" ). Generally, NFTLs for these liabilities cannot be filed until the bankruptcy is dismissed or discharged. During the bankruptcy, the taxpayer can incur additional tax liabilities ("post-petition liabilities" ). Occasionally, an NFTL may be filed for the post-petition liabilities even though the bankruptcy is still open. These NFTLs must be specially annotated to clarify that they do not attach the assets under the jurisdiction of the bankruptcy court. See IRM 5.17.11.14, Collection of Post-petition Taxes. Because of the special wording needed, NFTLs for post-petition liabilities must be manually prepared. The requester should manually prepare the Form 668(Y) using an available template and include a statement in the body of the form such as "This Notice of Federal Tax Lien does not affect assets under the jurisdiction of the bankruptcy court." The manually prepared form should be emailed to CLO for SLID assignment and filing. Upon receipt of the form, CLO takes the following actions. Input the data from the form into ALS to secure the SLID. Insert the SLID on the Form 668(Y). Print the Form 668(Y) and associate it with other documents for filing. Return a copy of the Form 668(Y) to the requester. The requester is responsible for preparing and issuing the CDP notice to the taxpayer and the POA, if appropriate. After filing, CLO follows standard procedures for inputting CRD and maintaining the NFTL on ALS.

# Refiling a Notice of Federal Tax Lien

5.19.12.2.6 (04-16-2024) Refiling a Notice of Federal Tax Lien An NFTL is valid for a specific period of time. The date this time period expires is usually seen on the NFTL under column (e), "Last Day for Refiling." There are situations where the liability is still owed and the statutory period for collection (CSED) for the liability is extended beyond the time the NFTL is valid. When this occurs it is necessary to refile the NFTL to continue its effectiveness. See IRM 5.12.8, Notice of Lien Refiling, for additional details. An NFTL can contain up to 15 different statutory liens (i.e., assessments), each with its own assessment date and refile date; However, the NFTL for each different assessment can only be refiled within 1 year of the refile period expiring. Therefore, a refile document may contain some, but, not all, of the assessments on the NFTL and there may be multiple refiles associated with one NFTL. Example: An NFTL was filed for 4 tax periods. The "Last Day for Refiling" for the first tax period is in 6 months, for the second tax period in 2 years, and for the third and fourth tax periods in 4 years. The NFTL can be refiled for the first module now as it is within one year of the refile time period expiring. The NFTL cannot be refiled for the second tax period until next year. The third and fourth tax periods can be included on one refile document, but the refile cannot be done for three years. Refiles are not systemically input or requested. They must be manually input to ALS. Refer to the ALS User Guide, Chapter 9, Refile a Lien - Update a Lien, for directions on inputting refiles. A request for refile is normally submitted on Form 12636. The request must specify several things, including the following: The current address for the taxpayer The tax periods to include in the refile Note: A tax period may have multiple assessments on the NFTL. Only those assessments that still have a balance due should be included in the refile. The request should specify which assessments in the tax period to include. The new CSED Note: It is essential to have the updated CSED for each period on the refile. If the CSED is in suspense due to litigation, the CSED field of Form 12636 should show all asterisks (**/**/****) or a future date (e.g., CSED plus 20 years). The requester should not put N/A in the CSED field of the Form 12636. The current unpaid balance of assessment (UBA) for the tax period or the UBA shown on the original NFTL, whichever is smaller Reminder: The UBA for the module may be less than what it was on the original NFTL. Most often, this happens when credits have posted to the module since the original NFTL. The UBA for the module generally should not be greater than it was on the original NFTL because it might include additional tax assessments that were not covered by the original NFTL. There are occasions, though, when a higher UBA is appropriate (e.g., no payments made and additional failure to pay penalty and interest assessed). Contact the requester if any required information on Form 12636 is missing or appears incorrect. Also, Form 668-F, Notice of Federal Tax Lien Refile, only allows for six assessments to be included on a refile. If the refile request is for more than the allowed six assessments, notify the requester and explain that two refile documents will be generated. The NFTL must be refiled in the recording office where it was originally filed. There can be situations when the refiled NFTL can also be filed in a different location even though an NFTL was not previously filed in that location (e.g., taxpayer relocated from one county to another). When such a request is received, generate the refile on ALS for the original location, then follow the ALS prompts to generate another refile for the additional filing location. Note: A request for refiling the NFTL in a different recording office from where the NFTL was filed is consistent with IRC 6323(g). In these situations, the refiled NFTL effectively serves as a new NFTL filing in that "different" recording office. To reduce potential confusion, the requester may ask for a new NFTL in the "different" recording office instead of refiling the original NFTL there. When processing a refile request, ensure enough time is left in the refile time frame for the refile document to be created in ALS, printed and processed by CLO, mailed to the recording office and recorded. If the refiled NFTL reaches the recording office after the refile deadline it will be ineffective and may be rejected by the recording office. If there is insufficient time for the refile to be recorded (generally, less than 21 days), contact the requester and advise that a hand-carried refile is needed. If the lien has self released or is expired (i.e., it is after the "Last Day for Refiling" and/or "exp" shows on ALS), notify the requester of the status. Advise that refiling is not possible and they must revoke the self-released/expired lien if they determine a new NFTL is appropriate (e.g., balance due, time remaining on CSED). Refer to IRM 5.12.3.14, Revocation of Lien Release, for further details. When a refile needs to be hand-carried for filing, CLO may receive an urgent request from a Collection employee through the 800 Internal Aspect Phone System, by secure email, or by fax for a SLID. Input the refile data to ALS following standard procedures with the exceptions noted below. Suppress the printing of the document and the appearance of it on the voucher. Provide the SLID to the requester to add to their manually-prepared document. Enter a history item in ALS that the refile document was prepared outside of ALS and hand-carried for filing. After hand-carrying the document for filing, the originator should secure email CLO a copy of the refiled NFTL with the court recording data. If a CSED is updated after an NFTL is filed, ALS is systemically notified of the change and updates its records accordingly. ALS monitors the computed refile dates for all NFTLs. If a refile date is approaching and the CSED has been extended or suspended, ALS marks that NFTL for inclusion in the Potential Refile Report. The Potential Refile Report provides a list of periods on NFTLs where the CSED has been extended and there is still a balance due. The Potential Refile Report can be generated by the office working the report (usually Advisory). Refile requests must be worked within five (5) business days after the receipt date in CLO. The NFTL refile is processed the same as any lien document. No special processing is required once the refiled document is created on ALS. For refiles printed and processed by CLO, a copy of the NFTL refile will be sent to the taxpayer from CPS. For refiles manually prepared and filed, the RO sends a copy to the taxpayer.

# Refiling in Special Circumstances

5.19.12.2.6.1 (06-03-2020) Refiling in Special Circumstances Refiling an NFTL continues the lien's priority on all property or rights to property of the taxpayer. Occasionally, the NFTL should only be refiled with respect to specific property. This situation most often occurs when the CSED expires but there is property under seizure or was not included in a bankruptcy proceeding. See IRM 5.10.4.12, Refiling Notices of Federal Tax Lien - Collection After Statute Has Expired, and IRM 5.9.17.5.2, Collection from Exempt, Abandoned, or Excluded Property (EAEP). In this situation, the Form 668-F must include a statement regarding the lien's attachment such as "The refiling of the Notice of Federal Tax Lien is limited to the following described property and is not intended to affect any other property of the taxpayer named above." The statement should be followed by a description of the specific property involved. Because of the special wording, the Form 668-F must be manually prepared, normally by the requester. When a request for a manually prepared refile is received, take the following actions. Secure a SLID for the refile from ALS and provide it to the requester. Suppress the printing of the refile through ALS. Process the manually prepared Form 668-F following standard procedures.

# Lien Release

5.19.12.2.7 (06-03-2020) Lien Release One NFTL can include up to 15 different federal tax liens (assessments). Basically, each tax assessment shown on the NFTL is a separate federal tax lien. Under IRC 6325, the IRS is required to release a lien within 30 days of when it has been satisfied or is no longer enforceable (e.g., statute expiration). Liens can be satisfied by various methods, including, but not limited to the following: Full payment Abatement of tax, penalty, and/or interest Credit offset that full pays the liability Litigation settlement A release of lien can take one of two forms. A Form 668-Z, Certificate of Release of Federal Tax Lien, was issued. The lien "self-released" (i.e., the "Last Day for Refiling" on the NFTL passes and the NFTL is not re-filed). Note: If the "Last Day for Refiling" is not specified on the NFTL, the self-release provision is not in effect and a certificate of release must be issued when the CSED expires. See IRM 5.12.3.4.1.1, Self-Releasing Lien. The IRS is generally not required to issue a certificate of release until all the liabilities listed on the NFTL are satisfied or no longer enforceable. When all the liabilities on an NFTL have been satisfied, a Form 668-Z is issued. The majority of releases are generated systemically. When a tax module with an NFTL filed indicator (TC 582) on Master File is satisfied and the account goes into status 12, a satisfied module indicator is sent systemically to ALS. Through the program ModSat, ALS marks satisfied periods with a "528" in the status column of the NFTL. ALS then runs a program called Relscan, which looks for NFTLs that have all tax modules satisfied and generates a release. If all modules on the NFTL are not satisfied, the release will not generate. There are times when a release must be issued before the systemic process can be completed or will not be completed within 30 days. These situations require manual input to ALS. In certain situations, lien releases may be manually prepared and issued. Most often, manual preparation is done when a taxpayer requests an immediate release in exchange for full payment made to Field Collection or a Taxpayer Assistance Center. Note: Payments for immediate releases must be made by certified or guaranteed funds. For other types of payments, a release can only be immediately issued if it is shown that the payment has cleared the financial institution. See IRM 5.12.3.3.1.1, Liability Satisfied by Payment, and IRM 5.12.3.3.1.1.1, Electronic and Credit Card Payments. IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates, lists SBSE employees who have the authority to approve lien releases and other lien-related certificates. IRM 13.1.4.2.3.16, Notice of Federal Tax Lien (NFTL) Release, provides the Local Taxpayer Advocate with limited authority to release federal tax liens. Reminder: A certificate of lien release may be issued only when the conditions of IRC 6325(a) or IRC 6326 have been met. Employees authorized to release liens must follow standard release procedures defined in this and related IRMs. When a lien expires due to statute expiration, a Form 668-Z is generally not issued. The self-release language on the NFTL fulfills the requirements for release. See IRM 5.12.3.4.1.1, Self-Releasing Lien, for more information. At times, a recording office identifies a release document as being "questionable" or fraudulent and contacts CLO for assistance. If the release cannot be verified, ask the recording office to fax the document. If the document still cannot be verified, contact the FORT to make a determination on referring the case to TIGTA. See IRM 5.12.3.8.2, Fraudulent Lien Certificate Recorded.

# Manually Inputting Lien Release

5.19.12.2.7.1 (04-16-2024) Manually Inputting Lien Release A request for a manual input of a lien release might be received by telephone or in writing from an internal or external customer. Requests from IRS employees are generally made on Form 13794, Request for Release or Partial Release of Federal Tax Lien. Requests from external customers can take a variety of forms (e.g., letter, phone call). See IRM 5.19.12.7.5.4, Request for Release of Lien, for instructions on processing external requests. For direction on how to input the release on ALS, refer to the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. When inputting a release on ALS, it is necessary to identify and input the date of the satisfying transaction The table below explains the date to use in the most common circumstances. Caution: This table is only to determine the date to input to ALS to process the release. The dates described are not necessarily the dates that begin the 30-day period in which the IRS is required to release the lien. For that information, see IRM 5.12.3-1, Starting Points for 30-Day Release Time Frame. Module satisfied by... Satisfying action date is date when... Date to use on ALS... Payment Credit applied TC 670 or other credit TC Adjustment Adjustment posted TC 291, TC 301, or equivalent TC. Adjustment pending (shows as pending on IDRS) Adjustment is scheduled to post Posting date shown for pending TC or current date, if earlier Adjustment requested (an employee requested an adjustment that will satisfy the liability and a TC 470 AC 89/90/93, but the TCs do not show yet on IDRS) Adjustment is anticipated to post The date given by requester or current date, if earlier Bankruptcy discharge The court discharged the liability TC 521 Bankruptcy discharge pending (request by employee prior to discharge posting) The court discharged the liability Date given by requester (no TC date) Credit offset Overpayment moved from another module TC 706 Credit transfer Original credit moved TC 670 or other credit TC CSED expiration CSED expired TC 608 (see IRM 5.19.12.2.7.4, Self-Releasing Liens) Offer in Compromise (OIC) paid Payment terms of the OIC were completed TC 780 OIC payment pending (usually requested by MOIC/COIC prior to acceptance closure posting) Payment terms of the OIC were completed Date given by requester (no TC date) Tolerance Account went to status 12 Status 12 date (see IRM 5.12.3.3.1, Liability Is Satisfied-IRC 6325(a)(1)) Requests from employees should contain all the necessary data for ALS input, including the requester's assignment number. Research on these requests is generally only done on ALS to ensure all related NFTLs are addressed. Reminder: Do not use ACS employee numbers to release liens. The inputting TE should use their own number. When releases are manually input to ALS, document in the ALS history why the release is being input and include enough information to identify the requester. On occasion, it is necessary for the field to issue a certificate of release directly to the taxpayer or their representative so they can hand carry it to the recording office. For example, a taxpayer requests an immediate release in exchange for a full payment or a release is requested by the Department of Justice in relation to litigation. In this circumstance, a copy of the release that was manually prepared should be provided to CLO to update ALS. Input the release to ALS following standard procedures, with the exceptions noted below. Suppress the printing of the release. Suppress the release from appearing on the voucher. Following the ALS prompts, input the name of the employee who issued the release. Note: The employee issuing a release directly to the taxpayer is responsible for the input of the TC 583 to IDRS. When a certificate of release is issued directly to the taxpayer for filing, the taxpayer should be provided Notice 48, Instructions for the Certificate of Release of Federal Tax Lien. The notice explains the filing process and advises the taxpayer of their responsibility to pay the recording fee charged by the recording office or their option to request the IRS file the certificate following routine processing. Release requests must be worked within five (5) business days after the date of receipt. OFP 810-69080 is used for completing requests for the release of liens.

# Partial Lien Releases

5.19.12.2.7.2 (06-03-2020) Partial Lien Releases An NFTL can show multiple taxpayers (e.g., joint liability) and multiple tax periods. There are times when it is necessary to release the lien against one of the taxpayers or some of the tax periods listed on the NFTL. When this happens a partial release of lien is issued. A partial release for one of the taxpayers listed on the NFTL is done when one taxpayer is no longer liable for the assessments listed but the other taxpayer(s) is still liable. This happens most often when there is a joint income tax liability and one spouse has been granted a discharge in a bankruptcy, has completed the payment terms of an OIC, or has been granted innocent spouse relief. Most of these partial releases are generated systemically when the tax module is being split on Master File, but requests from IRS employees for manual input may also be received. Note: When an NFTL is filed for a joint assessment (e.g., MFT 30) and that liability is subsequently split into separate assessments (e.g., MFT 31), ALS recognizes the situation and generates a partial release when one of the separate assessments is satisfied and a full release when the other separate assessment is satisfied. When NFTLs are filed for the individuals AFTER the assessment is split, ALS does not link the two accounts but follows normal systemic release processes. Partial releases for certain tax periods listed on the NFTL can be issued after each assessment is satisfied or becomes unenforceable; however, the IRS is only required to do these partial releases upon the taxpayer's request. See IRM 5.12.3.6, Partial Lien Release. Note: For individual periods that have expired or self-released, follow self released lien procedures. See IRM 5.19.12.2.7.4, Self-Releasing Liens. Requests for partial release received from an IRS employee usually do not need researched. Contact the employee if there are questions or problems. The request is generally on Form 13794. The request should provide a reason for the partial release (e.g., taxpayer was determined to be an innocent spouse). The authority to request a partial release is the same as requesting a full release. See IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates. Requests for partial releases received from a taxpayer must be researched to determine if a partial release is appropriate. Caution: The liability under the joint entity may show satisfied, but the liability was split to separate liabilities. Ensure no liability exists under either MFT 30 or MFT 31 before processing the release request. To input a partial release, follow the same basic procedures for a manual release request except address the questions regarding the partial release. See IRM 5.19.12.2.7.1, Manual Release of Liens, and the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. For ALS to generate a partial release, the system establishes an ALS-only document identified as a "spec doc" in the status column on ALS. From this spec doc the partial release is prepared. The spec doc has a unique SLID on ALS, but the printed document shows the original SLID and special language to indicate it is a partial release. Partial releases are printed at CLO with other lien documents following regular print schedules. Partial releases for ELF recording offices are printed and mailed by CLO and can be found in SPOOL/ELF.mmdd. The TP copies of the partial releases are systemically generated and mailed from CPS. OFP 810-69080 is charged for working requests for the partial release of lien. Requests must be worked within five (5) business days after the receipt date.

# Partial Release with Tax Court Indicator

5.19.12.2.7.3 (09-09-2021) Partial Release with Tax Court Indicator Occasionally, ALS research may show a partial release was systemically created, but has not been issued. This generally happens when one person on a joint liability NFTL has made an innocent spouse claim that was denied and is challenging the assessment in Tax Court. In addition to the partial release, ALS research also shows: The release is not in the manager's approval queue; and When attempting to access the NFTL through the "Release," function, the user is warned that a duplicate should not be generated. IDRS research of the account(s) shows all the following: A TC 971 AC 102 or TC 971 AC 103, indicating the claim of the spouse was denied and is being appealed in Tax Court A TC 400 on the MFT 30 joint module, indicating the account has been transferred out An MFT 31 for the module for the non-petitioning spouse only The posting of the TC 971 AC 102/103 triggers a systemic partial release on ALS for the innocent spouse. However, the partial release is stored on ALS until a final decision is reached in Tax Court. When an inquiry is received regarding a partial release in this situation, advise the taxpayer the lien cannot be released until a Tax Court decision is final or the lien is full paid. Input a history item on ALS regarding the situation.

# Self-Releasing Liens

5.19.12.2.7.4 (06-03-2020) Self-Releasing Liens NFTLs filed on Form 668(Y)(c), Notice of Federal Tax Lien, show a "Last Day for Refiling" in column (e). Language on the form states that if the NFTL is not refiled by that date, the lien is considered to be released. This is known as a self-releasing lien. See IRM 5.12.3.4.1.1, Self-Releasing Lien, for further details. Each assessment shown on the NFTL has its own "Last Day for Refiling." When the respective date passes and no refile has been input, ALS will place an indicator on the assessment to show the lien has expired ("EXP" ). A certificate of release is not systemically issued for a self-releasing lien. If an NFTL contains multiple liabilities that are satisfied by different means (e.g., payment, statute, etc.), a certificate of release may or may not be issued depending on how the last open liability on the NFTL was resolved. If the last final liability on the NFTL is satisfied by.... And the "Last Day for Refiling" for all the other liabilities on the NFTL... Then a Certificate of Release... Statute expiration Has passed Is not necessary Statute expiration Has not passed Must be issued Payment or adjustment Has or has not passed Must be issued If there is no "Last Day for Refiling" specified on the NFTL or the NFTL does not have the self-release language (e.g., refiled NFTLs, Forms 668(Y) issued before 1983), the self-release provision is not in effect and a certificate of release must be issued within 30 days of when the CSED passes. Note: ALS systemically issues releases when the CSED for a refiled NFTL passes. When a request for lien release is received for a self-released lien, review IDRS to ensure the CSED has not been extended and to determine if there is still a balance due on the assessment(s). If the CSED has been extended and there is still a balance due, take the following actions. Determine the status of the account and refer it to the appropriate office. See IRM 5.19.12.7.5.2, Request for Payoff, for additional information on referrals. Status Refer to... 22 ACS 26 RO 71 Centralized Offer in Compromise 72 (TC 520 cc 60-67, 81, or 83-89) Centralized Insolvency Operation 72 (TC 520 cc 70-75 or 80) Advisory All other statuses Advisory Prepare a Correspondex Letter 3645C, Case Processing Liens / Centralized Lien Operation, to explain that the request is being referred or, if the request is by phone, tell the caller you are referring the case for an NFTL determination and to whom the case is being referred. See IRM 2.11.1, IDRS Correspondence, on creating correspondex letters. Input an ALS or AMS history of the actions that were taken. If the CSED has not been extended or there is no balance due, advise the taxpayer of the self-release and take the following actions. Advise the taxpayer that you can provide a certificate of release that they can file at the recording office. Explain that some recording offices may not accept the certificate because they recognize the lien as being self-released. Also, advise the taxpayer that they must pay the filing fee required by the recording office. Note: The taxpayer may ask that the IRS file the certificate. Generate a Form 668-Z using the ALS literal command "PRNT668." Ensure the NFTL has CRD before printing and, if needed, update the release document with the current date. Note: In situations where the NFTL is no longer on ALS, the taxpayer must provide a copy of the NFTL and the certificate of release must be manually prepared using an available template. Send the release document to the taxpayer with Notice 48, Instructions for the Certificate of Release of Federal Tax Lien. Update ALS with a history stating the actions taken. If the NFTL was filed in an ELF recording office, print and provide the taxpayer a facsimile of the self-released NFTL and explain it was filed in electronic recording office. If the taxpayer states they need a Certificate of Release, the lien should be released on ALS so that an electronic release is sent. The ELF recording office will not accept a paper document from the taxpayer for recording. If the recording office refuses to file a hand-carried release for the taxpayer and insists it come from the site, add the release to the next available voucher for that recording office. Caution: Sending the certificate of release directly to the recording office can cause the entire batch of documents to be rejected. If the certificate of release must be sent directly, check MAINTXC for any filing restrictions or contact the recording office prior to sending to resolve any filing problems. Paper requests for a release must be worked within five (5) business days after the date of receipt. Phone requests should be worked while the taxpayer is on the phone, unless unusual circumstances exist. OFP 810-69080 is charged for processing written requests for release of liens. If the request is by phone, use OFP 700–69000.

# Reversing a Lien Release

5.19.12.2.7.5 (06-03-2020) Reversing a Lien Release Occasionally a lien will be released on ALS, either by the issuance of a certificate of release or the self-release nature of the NFTL, and it is determined the lien should not have been released. An erroneous or improvident release must be addressed before additional actions can be taken regarding the lien. If the lien has been released on ALS but the Certificate of Release has not yet been printed, a user with the appropriate permissions, usually a manager, can reverse the release on ALS. Refer to the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals, for direction. Caution: When a release of lien is reversed, the individual modules must also be addressed on ALS. If all of the modules on the NFTL show satisfied in one way or another, a release will be systemically generated again when Relscan is run. See the ALS User Guide for instructions on reversing the SAT indicator for the modules. Once a certificate of release is filed or the NFTL expires, the release cannot be reversed on ALS. A certificate of revocation must be issued.

# Revoking a Lien Release

5.19.12.2.7.6 (04-16-2024) Revoking a Lien Release When a certificate of release is issued, the statutory lien(s) listed on the NFTL is extinguished. The same is true if the lien self-releases because the NFTL was not timely refiled. The tax liability is not extinguished and the IRS can continue to collect the liability(s) but administrative, as well as judicial, enforcement actions to collect may be restricted. See IRM 5.12.3.14, Revocation of Lien Release, for details. Sometimes a certificate of release is issued or the lien self-releases but there remains a balance due on the liabilities and the CSED is still open. Before a new NFTL can be filed, the release must be revoked to re-establish the statutory lien. An erroneous or improvident release is revoked by filing a Form 12474, Revocation of Certificate of Release of Federal Tax Lien, at the appropriate recording office. Note: The current revision of Form 12474 incorporates wording for self-released liens, thereby making Form 12474-A unnecessary. However, Form 12474-A may continue to be used for self-released liens until ALS programming for the revised Form 12474 is implemented. Requests for revocation are usually submitted on Form 14466, Request for Revocation of Erroneous Release of Federal Tax Lien. If the revocation request is for a recorded certificate of release, the requester of the revocation must supply the recording date of the release to complete the revocation. Release recording information is not kept on ALS. If the revocation request is for a self-released lien, no release recording date is necessary. The recording information for the document is the original NFTL recording information. See IRM 5.12.3.4.1.1, Self-Releasing Lien. Revocation requests are sent to CLO or CLO FORT via secure email by Advisory, Insolvency, Offer in Compromise (OIC) units, or directly from revenue officers. See IRM 5.12.3.14.1, Requesting Revocation of Lien Release. Revocations are often routed through Advisory for approval; however, other positions have approval authority, including GS-9 revenue officers and their managers, Insolvency group managers, the CLO program manager, and the CLO FORT manager. See IRM 1.2.2.6.4, Delegation Order 5.4 (Rev. 3), Federal Tax Lien Certificates. Due to the complexity of some revocation situations and ALS' limitations in processing certain types of revocations, revocation requests received by CLO teams generally should be forwarded to the FORT for processing As much as possible, revocations should be input and processed through ALS. See ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. Note: See IRM 5.19.12.2.7.6.2, Manual Revocation Situations, for instructions on processing manually prepared documents. Print the revocation document as part of the routine batch processing. Send one copy of the revocation document to the recording office. Research IDRS for the current address of record for the taxpayer(s). Mail the second copy of the revocation document via regular mail to the taxpayer(s) at their current address(es) of record. Note: Although CLO is tasked with mailing the taxpayer's copy, it is the requester's responsibility to ensure this is done. When the request for a new NFTL is included with the request for the revocation it is imperative that the revocation and new filing be completed in the proper sequence. The revocation must be prepared, recorded with the recording office, and mailed to the taxpayer PRIOR to the new NFTL being filed. Generally, the request for the new NFTL should be held (i.e., not input to ALS or sent to the recording office) for two weeks after the revocation is processed. This will help to ensure that the revocation is filed before the NFTL is filed. Alternatively, the NFTL may be filed as soon as the recording office verifies that the revocation is recorded. The revocation document and new NFTL may be sent to the recording office at the same time but a note should be attached to the documents advising the recording office that the revocation must be recorded before the new NFTL is recorded. The note to the recording office should also include references to the SLID number of both the revocation and the new NFTL. The following example shows how the note might be worded. Example: To comply with IRC 6325(f)(2), please record the attached Form 12474, Revocation of Release of Federal Tax Lien, serial number xxxxxxxxx, before recording the attached Form 668(Y)(c), Notice of Federal Tax Lien, serial number xxxxxxxxx. Caution: The revocation document must be both mailed to the taxpayer and recorded at the recording office to re-establish the statutory lien. The statutory lien must be re-established before a new NFTL is filed. Also, a revocation must be filed everywhere the NFTL was originally filed. Add a history item to ALS to indicate the reason for the revocation. Also, a history item should be added when the taxpayer's copy of the revocation is mailed and should specify to what address the document was mailed, if different from the NFTL address. If it is found that a revocation has been incorrectly input, the revocations can be reversed before the print date by a user with the appropriate permissions utilizing the ALS literal command "revoke." Refer to the ALS User Guide for more instructions. Requests for revocation must be worked within five (5) business days after the receipt date. OFP 810-69080 is charged for completing the reversal or revocation of release of liens.

# Partial Revocation of Lien Release

5.19.12.2.7.6.1 (04-16-2024) Partial Revocation of Lien Release There are times when a lien is erroneously or improvidently released but only with respect to some of the persons and/or assessments shown on the NFTL. In these situations, a partial revocation of the release may be needed. Common examples of when a partial revocation is appropriate include the following: The lien for a joint liability is released, but one of the parties still owes the liability. A certificate of release is issued for an NFTL that covers multiple assessments or the NFTL is not refiled timely causing a self-release, but some of the assessments are still owed. The NFTL refile period has passed (i.e., the lien self-released) for some of the assessments on an NFTL that covers multiple assessments, but some of those assessments are still owed. Note: This scenario includes a tax period with multiple assessments and the self-release affects only one of the assessments. Partial revocations are requested and processed in a similar manner to full revocations, including being forwarded to the FORT for processing. See IRM 5.19.12.2.7.6 above. However, the following exceptions apply. The request must detail who the revocation pertains to and what tax periods or assessments should be included on the revocation. "Partial" must be specified when inputting the revocation to ALS and the taxpayer and/or assessments to include on the revocation document must be selected. See ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. Because of the way ALS totals the UBA for a tax period with multiple assessments, a revocation request involving just one of the assessments may appear on ALS with a zero amount or blank field. Nevertheless, the request can still be processed. Partial revocation documents generated by ALS are annotated with wording that identifies the them as partial documents. Caution: Due to systemic issues, ALS cannot print partial revocations when the original NFTL was refiled prior to the release or a partial Certificate of Release on a joint liability was issued. In these cases, the revocation must be manually prepared. As with full revocations, the partial revocation document must be filed and issued to the taxpayer prior to a new NFTL being filed. For partial revocations, add an ALS history that provides details about the situation.

# Manual Revocation Situations

5.19.12.2.7.6.2 (04-16-2024) Manual Revocation Situations Whenever possible, ALS should be used to generate revocation documents so the lien database shows all lien activity. There are instances, however, when ALS cannot generate and/or print a revocation document and the revocation document must be manually prepared. The following are a few instances when manual preparation is needed. The original NFTL was refiled (in full or in part) prior to being released. The NFTL was filed in multiple locations but was not refiled in all those locations (i.e., the lien self-release of one of the NFTLs extinguished the statutory lien on all NFTLs). A partial certificate of release was issued. The NFTL was partially withdrawn before the release. Manually prepared revocation documents should be forwarded to the FORT for review and processing. The requester is responsible for manually preparing the revocation, but, in certain instances, CLO FORT may be asked to assist with the preparation process. Blank Forms 12474 are available through the ICS templates or publishing catalog (https://publish.no.irs.gov/catlg.html). The form should reflect the SLID from the original NFTL and the recording data from the certificate of release. (For self-released liens, use recording data from the original NFTL.) Complete the remainder of the form to match the certificate of release, with the exceptions noted below. If the revocation does not apply to all the persons or tax periods shown on the release (or NFTL if self-released), notate the Form 12474 as a Partial Revocation. If the revocation only applies to one person on a joint liability, input the name line as [Taxpayer A] only, in the matter of [Taxpayer A and Taxpayer B. List only the assessments for which the lien release is being revoked. Do not include assessments that no longer have a balance due. If the revocation is for one assessment of a tax period with multiple assessments, show the amount of the assessment on the revocation document as either the UBA for the tax period (as shown on the original NFTL) or the amount of the specific assessment. For partial revocations, insert a paragraph in the body of the form to describe the revocation situation. Example: *PARTIAL REVOCATION. The release of Federal tax lien is revoked only as it relates to [Taxpayer A], in the tax liability of [Taxpayer A and Taxpayer B]. The lien is released with respect to [Taxpayer B]. Example: *PARTIAL REVOCATION. The release of Federal tax lien is revoked only as it relates to the tax liabilities listed in this revocation. The lien is released for all other tax liabilities shown on the Certificate of Release. Example: *PARTIAL REVOCATION. The release of Federal tax lien is revoked only as it relates to [Taxpayer A], in the tax liability of [Taxpayer A and Taxpayer B], and only as it relates to the tax liabilities listed above. The lien is released with respect to [Taxpayer B] and all other tax liabilities shown on the Certificate of Release. Input a history item into ALS about the revocation. Manually prepared revocations can be included in the batch mailings to the recording office but will have to be manually added to the billing support voucher.

# NFTL Withdrawal

5.19.12.2.8 (06-03-2020) NFTL Withdrawal Once a Notice of Federal Tax Lien is filed, the lien can only be released when the liability is satisfied, the liability is no longer enforceable, or a bond has been accepted for the payment of the liability. In certain situations it may be appropriate for the IRS to withdraw the Notice of Federal Tax Lien while the taxpayer still owes the liability. See IRM 5.12.9, Withdrawal of Notice of Federal Tax Lien, for further details. Note: Information about withdrawing an NFTL after the lien has been released is found in IRM 5.19.12.2.8.3, Withdrawal of NFTL After Lien Release. A Withdrawal of the NFTL differs from a Certificate of Release of Federal Tax Lien and the two cannot be used for one another. A Withdrawal only removes the effect of the NFTL whereas the Certificate of Release invalidates the NFTL and extinguishes the statutory tax lien. Advisory and Insolvency managers have general approval authority for a withdrawal of an NFTL, but other positions also have limited authority to approve withdrawals as described in IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates. Most withdrawal requests are processed through Advisory. Insolvency primarily works withdrawals involving active bankruptcy cases. Both offices send approved withdrawal requests to CLO for processing actions or input the requests directly to ALS, if permissions allows. Withdrawal requests are generally submitted on Form 13794-W, Request for Withdrawal or Partial Withdrawal of Notice of Federal Tax Lien. Note: Requests from Appeals usually come through Advisory because Appeals does not have TSIGNs. Do not use generic TSIGNs for requests from Appeals. Upon receipt of an approved withdrawal request, check ALS to ensure the NFTL has recording information. CRD must be on the NFTL before a withdrawal can be input to ALS. If no CRD is on the NFTL, use an available research tool to locate the recording information and update ALS accordingly. If no recording information is found, follow the steps below. Notify the requester there is no CRD on ALS and none was found through research. Ask the requester to find the CRD and resubmit the request. Close case along with all documentation. Input a history in ALS about the situation. Note: During the research process, if you find there is no NFTL filed, notify the requester and follow the Potential Lost Lien procedures. See IRM 5.19.12.9.5, Potential Lost NFTLs. Once CRD is on the NFTL, input the withdrawal on ALS following the instructions found in the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. Input a history in ALS of the withdrawal request. Note: In rare situations where the NFTL is not on ALS and the lien has not been released, the NFTL must be added through the SCREATE process before the withdrawal can be input. Withdrawals input to ALS go to the manager's approval queue. The team manager daily approves the withdrawals in the queue. Generally, the TC 360 NFTL filing fee is not reversed when the NFTL is withdrawn. When it is appropriate, the office authorizing the withdrawal is responsible for reversing the TC 360. Form 10916, Withdrawal of Filed Notice of Federal Tax Lien, is printed and mailed for recording with other lien documents. The taxpayer's copy of Form 10916 is printed and mailed to the taxpayer from CPS. If the requesting office asks for a copy of the Form 10916, make a copy of the document when printed or, after the withdrawal is approved on ALS, generate a copy using PRNT668. If the recording office has electronic filing (ELF), print the facsimile after creating the withdrawal. Scan the copy of the withdrawal document and send it to the requester by secure email. On occasion, the withdrawal document may be manually prepared in the field and issued directly to the taxpayer for recordation. In these situations, a copy of the withdrawal document should be provided to CLO for input to ALS. Follow usual input procedures except as noted below. Suppress the printing of the withdrawal document. Suppress the document from appearing on the BSV. Indicate that the withdrawal was already issued and input the applicable data. NFTL withdrawal requests must be worked within five (5) business days after the date of receipt in CLO. OFP 810-69080 is charged for completing NFTL withdrawals.

# Partial NFTL Withdrawals

5.19.12.2.8.1 (06-03-2020) Partial NFTL Withdrawals Situations may arise where the NFTL lists multiple persons but it is appropriate to withdraw the NFTL only as it relates to one person. Also, but in unusual circumstances, there may be situations where the NFTL lists multiple tax periods but it is appropriate to withdraw the NFTL only as it relates to certain tax periods. In these situations a partial withdrawal may be issued. See IRM 5.12.9.7, Partial Withdrawal, for additional details. Those authorized under Delegation Order 5-4 to approve withdrawals can also approve partial withdrawals. Generally, the approved partial withdrawal requests come from Advisory or Insolvency to CLO for processing actions. Follow the instructions in IRM 5.19.12.2.8 above for processing the withdrawal request. Input the partial withdrawal on ALS following the instructions found in the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals. Input a history in ALS about the partial withdrawal request. Do not reverse the TC 360. There is no abatement of NFTL filing fees for partial withdrawals. Partial NFTL withdrawals must be worked within five (5) business days after the receipt date in CLO. OFP 810-69080 is charged for completing the partial NFTL withdrawals

# Misdirected Withdrawal Requests

5.19.12.2.8.2 (06-03-2020) Misdirected Withdrawal Requests Requests for NFTL withdrawal are submitted in writing, generally on Form 12277, Application for Withdrawal of Filed Form 668(Y), Notice of Federal Tax Lien. In the event a request for a withdrawal is received from a taxpayer for an NFTL and the lien has not been released, check IDRS to determine the status of the account. Refer the request following the table below. Status Refer to... 26 Assigned RO 72 (TC 520 cc 60-67, 81, or 83-89) Centralized Insolvency Operation All other statuses Advisory Consolidated Receipt Prepare a Correspondex Letter 3645C, Case Processing Liens / Centralized Lien Operation, for the taxpayer to explain that the request has been referred. Refer to IRM 2.11.1, IDRS Correspondence, for creating a correspondex letter. Input a history of the action taken on ALS or AMS, if not on ALS. If the request is received from an IRS employee not authorized to approve withdrawals, reject the request back to the requester and explain that the request must go through Advisory or Insolvency.

# Withdrawal of NFTL After Lien Release

5.19.12.2.8.3 (09-09-2021) Withdrawal of NFTL After Lien Release Taxpayers may request a withdrawal of the NFTL after the lien has been released. The policy regarding withdrawals after lien release (WDARs) is found in IRM 5.12.9.9, Requests for NFTL Withdrawal After Lien Release. WDAR requests are worked by Advisory and requests received in CLO should be referred to the Advisory Consolidated Receipt site. In unusual circumstances, CLO may work WDAR requests under IRC 6323(j)(1)(D), "best interest of the taxpayer and the government," if a certificate of release was issued. CLO managers have the authority to approve WDARs, except for situations where the lien self-released. See IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates. When it is necessary to work a WDAR request in CLO, follow the steps below. Review ALS to determine the status of the NFTL and whether a certificate of release was issued. Research IDRS to determine how the liability was satisfied and whether the taxpayer is in filing compliance. Request additional information from the requestor as needed. Make a determination on the WDAR request following the guidance found in IRM 5.12.9.9. If the conditions for withdrawal are met, input the withdrawal to ALS following standard input procedures. Print and process the Form 10916-A, Withdrawal of Filed Notice of Federal Tax Lien after Release, following standard procedures. Note: A copy of the Form 10916-A and Letter 3044, Withdrawal After Notice of Lien Release, will systemically generate and be sent to the taxpayer from CPS. If the conditions for withdrawal are not met, prepare and issue Letter 4711, Withdrawal Decision, to deny the request. Note: Determinations to withdraw the NFTL or deny the request must be approved by the team manager prior to generation of documents. In situations where a WDAR request is received for an NFTL no longer on ALS, manual preparation of the documents may be necessary. See IRM 5.12.9.9.2, Withdrawal Requests for NFTLs No Longer on ALS. Do not SCREATE a released NFTL on ALS for the sole purpose of withdrawing it. WDAR requests should be reviewed within thirty (30) calendar days after receipt of a complete request in CLO (e.g., Form 12277 with all information). If the request cannot be reviewed in that time frame, send an interim letter to the requestor advising of the status. Use OFP 810-69170 when working withdrawal requests.

# Certificate of Non-Attachment

5.19.12.2.9 (04-28-2015) Certificate of Non-Attachment Certificates of Non-Attachment (CNA) are not notices of lien. They are certificates created when a third party contacts the IRS for documentation that explains the NFTL does not affect their property. Most often this occurs when the third party and the taxpayer have a similar name. These certificates are generally prepared and submitted by Advisory. These documents are not loaded to ALS, but are filed with documents that are created on ALS. Upon receipt of a CNA, compute the filing fees and add it to the BSV. File the CNA with the recording office following the same procedures as filing an NFTL that is not on ALS.

# Document Printing

5.19.12.3 (06-03-2020) Document Printing Lien documents, including NFTLs, releases, withdrawals and revocations, are routinely printed on Tuesdays and Thursdays only. Note: There are times when the documents are printed outside of this parameter (e.g., a holiday falls on a print date, a disaster prevents sending NFTLs to the designated location). In these instances management provides guidance for alternative processing. NFTLs printed on days other than Tuesdays and Thursdays can cause a delay in the issuance of the CDP notice, resulting in the five (5) day time frame not being met. Printing and mailing of the lien documents starts the day after the "668Y" and "668Z" listings are completed and the billing support voucher is reviewed for additions and subtractions. All printing and mailing must be completed within three (3) business days. All documents should be printed on Tuesday or Thursday. This would also be the day all ELF liens are approved. Note: Managerial approval of the ELF liens is equivalent to printing of the liens and will trigger the CDP generation. The managerial approval must be done on Tuesday and Thursday to ensure CDP notices are timely printed and mailed. The printed documents are packaged and mailed the following day (Wednesday and Friday). The upload of the ELF files from ALS to the respective recording office should only be done on Wednesday and Friday. Ensure that all recording offices within the same voucher are mailed at the same time. This has impact to the date input to the voucher program. ALS uploads information about the lien documents to Master File. The TCs 582, 583, 360, and 971 AC 252 postings are directly related to the document creation and printing process. The TCs 582 and 583 are triggered by the Billing Support Voucher (BSV), The date of the TC 582/583 is based on the creation date of the lien document; however, the ALS extract to upload the TC 582/583 is based on the standard BSV date range. If the creation date of the document falls outside the standard BSV date range, the TC 582/583 is not automatically included in the extract to Master File. The TC 971 AC 252 is triggered by the printing of the NFTL. The date of the TC 971 is based on when the NFTL is printed. The ALS extract to upload the TC 971 captures all the NFTLs printed within a given range. The TC 971 is uploaded to Master File in the same file as the TC 582/583, but it is processed and posted separately. The TC 360 is triggered by the BSV and processed similarly to the TC 582/583; however, it uploads and processes separately. Example: An NFTL was created on March 2, included in the BSV built on March 4, and printed on March 5. The TCs related to this NFTL were delivered to Master File on March 6. If the same NFTL was not included in the print batch of March 5, but rather printed on March 12, the TC 971 AC 252 would have been transmitted to Master File but the TC 582 and TC 360 would not have been transmitted because the NFTL creation date was outside the standard BSV date range. Use OFP 790-69010 to report time spent reviewing and editing the BSV and working the 668Y and 668Z listings.

# SPOOL and SPOOL.OLD

5.19.12.3.1 (06-03-2020) SPOOL and SPOOL.OLD The print spool contains lien-related documents to be printed. There are two print spools found on ALS. On the ALS print menu they are identified as SPOOL and SPOOL.OLD. "SPOOL" is the active spool or queue and contains lien documents waiting to be printed. "SPOOL.OLD" is the back-up spool or queue and contains lien documents and reports that have already been printed. Review of the active spool queue should be completed after each printing to ensure all documents are printed that correspond to the range of dates being worked. ALS reports are located in the Reports file on the print menu. Once documents are printed, they move from the spool to the spool.old.. Documents are retrievable from spool.old for 17 days. Refer to the ALS User Guide, Chapter 12, Printing Documents, for more information.

# Billing Support Voucher

5.19.12.3.2 (06-03-2020) Billing Support Voucher A Billing Support Voucher (BSV or "voucher" ) is a document generated through ALS that identifies all the lien documents being sent to a specific recording office and the amount being paid for the filing of those documents. A BSV is used as an accounting tool and also to document when lien documents are filed. ALS assigns each new BSV a unique number consisting of a voucher number, account number and payment type identifier. The number will appear on the generated BSV and can be used to locate the BSV for editing. The BSV number is made up of three parts. The recording office (court) ID number that is assigned in the ALS Court Table. The voucher number, which is generated sequentially and used for all vouchers within the state (unless one specific recording office BSV is being built). The payment type identifier, which will usually be "E" indicating the recording office is paid by electronic funds transfer from the Integrated Financial System (IFS). Other identifiers less commonly used are "I" for recording offices that receive a paper check and "B" those operating on a billing process. Example: In the BSV number 330032-10 E, the 330032 represents the recording office id, 10 represents the voucher number, and the E shows the payment is made through IFS. With the implementation of the Financial Management Service Debt Management Services to collect delinquent debts owned to federal agencies, the Integrated Financial System (IFS) was implemented to interface with ALS for payment of recording fees. Note: Due to special circumstances, there are a few recording offices that still receive payment by paper check instead of by electronic fund transfer (EFT). These checks are processed outside of CLO. A BSV is built for the range of dates of the documents being filed. BSV built for printing on... Covers the documents generated from... Tuesday Previous Wednesday through Saturday Thursday Sunday through Tuesday The voucher that is stored in ALS should reflect the voucher as it was prepared for the recording office, less any manual additions or corrections made. Periodically, due to fee changes or rejections, adjustments to the BSV are needed to correct payment to the recording office. These adjustments will be completed by the team manager or lead TE using ALS voucher program before the documents for recording are printed. After transmitting the BSV and documents, CLO may be notified by the recording office that an overpayment or underpayment of fees has occurred. This notification may result in the rejection of the lien documents by the recording office. CLO should attempt to resolve the discrepancy (e.g., explain the Treasury Offset Program (TOP)), but may need to refer the recording office to Accounts Payable Financial Operations (a unit at the Beckley Finance Center). See IRM 5.19.12.7.4, Recording Offices. CLO will retain either a paper copy of the BSV or a scanned copy. This copy should be an accurate reflection of the original and/or adjusted BSV. To verify timeliness of release to the taxpayer, CLO will maintain the paper date-stamped BSV in a manner similar to the maintenance of the postal stamped Form 3877 and Registered Listings. Retain paper BSV's on site for one (1) year then forward to the Federal Records Center.

# ALS 668Y and 668Z Listings

5.19.12.3.3 (04-28-2015) ALS 668Y and 668Z Listings The ALS Voucher program provides two listings that are generated prior to building the BSV. These listings, called 668Y and 668Z, are used to determine the documents and/or data that need clarification before printing. The 668Y listing shows NFTLs (or refiles) created on ALS with a prepared date in the BSV date range that are not in the print queue. Documents are missing from the print queue when the "on voucher" or "store only" option was selected when the request was input in ALS. This most often occurs when the NFTL was hand-carried to the recording office or the NFTL is printed outside the date range. Reminder: Do not print an NFTL before the designated print time. See IRM 5.19.12.3, Document Printing. An NFTL that is being hand-carried for filing should be manually prepared by the requester using an available template. The 668Z listing shows documents (e.g., releases, withdrawals, revocations) targeted for placement on a BSV that are missing information such as recording data. Generate the 668Y and 668Z listings on Monday or Wednesday prior to the printing and mailing of the BSV. Once generated, the reports can be located in each area's reports print queue. Some listings are run overnight in CRON and are placed in the area's reports print queue on Monday and Wednesday, so they do not need to be generated. The largest of the CRON reports are as follows: California (CA) Connecticut (CT) Florida (FL) Illinois (IL) New Jersey (NJ) New York (NY) Pennsylvania (PA) Texas (TX) Note: See the ALS User Guide, Chapter 11, Billing Voucher, Listings and Lien Documents, for instructions on generating the listings. Use the information on the listing to research documents that need clarification or correction and determine appropriate action. Listings generated on Monday must be resolved before printing the documents on Tuesday; the listings generated on Wednesday must be resolved before printing the documents on Thursday.

# Resolving the 668Y Listing

5.19.12.3.3.1 (04-28-2015) Resolving the 668Y Listing To resolve NFTLs showing on the 668Y listing, research ALS for history information to determine what data the NFTL may be missing. Take appropriate corrective actions, as needed. Input an ALS voucher history if adding the document to the voucher.

# Resolving the 668Z Listing

5.19.12.3.3.2 (04-28-2015) Resolving the 668Z Listing In the "HOW" column, the 668Z listing indicates a reason the lien document was identified for research. The primary reasons are "No Recd" , which means there is no recording data on ALS for the original NFTL, and "Missing" , which indicates the lien document was prepared but is not in the print file. When the reason shown is "No Recd" , research for recording data using the best method of research for the recording office, including, as necessary and appropriate, contacting the recording office. Based on the research, take action as described in the following table. If... Then... Recording data is located Input the CRD on ALS. Recording data cannot be located and it has been 90 days since the NFTL was filed Follow the Potential Lost lien (PLL) procedures in IRM 5.19.12.9.5, Potential Lost NFTLs. The ALS history should reference that the NFTL was never filed and was removed. The recording office has the NFTL but has not filed it yet Explain to the recording office the importance of timely filing IRS documents and continue to monitor case until the CRD is received. The recording office did not receive the NFTL Follow the Potential Lost lien (PLL) procedures in IRM 5.19.12.9.5, Potential Lost NFTLs. DO NOT RESEND THE ORIGINAL NFTL. When the reason shown is "Missing" , research ALS history for information on the situation. If verified that the lien document was hand carried, remove the SLID from the BSV. If unable to determine whether the lien document was hand carried, take corrective action so the document can be printed and filed. Notate the paper listing with the actions taken and your name or ID Number. Also, input an ALS history indicating that the Z listing was worked and actions taken.

# BSV Review

5.19.12.3.3.3 (09-09-2021) BSV Review BSVs and related documents should not be printed outside of the normal processing on Tuesday and Thursday. BSVs should be reviewed on Mondays and Wednesdays on ALS before printing to ensure completeness and accuracy. Note: Normal processing days may occasionally be altered by holidays or other significant events. Prior to printing, review the BSV to identify the following situations and to take necessary corrective action. BSV problem Corrective action A Not To Be Filed lien record (NTBFL) printed. (These are for internal use only to alert of an action to be taken.) Take corrective action based on the ALS history. DO NOT FILE A NTBFL OR A RELEASE OF A NTBFL See IRM 5.19.12.2.3.3, Not To Be Filed Lien Record, for further instruction. An NFTL on an individual taxpayer is filed with Secretary of State inappropriately. Remove the NFTL from the BSV and notify the requester of the removal and why it was removed. Submit a request to the manager or lead TE to remove the NFTL from ALS. Paper documents generated for ELF recording offices (unless the document must be sent by paper, such as an amended NFTL). Change the recording office to reflect the ELF recording office and add to the BSV. Ensure the document is approved in the ELF approval queue. Remove from the paper court voucher as applicable. See IRM 5.19.12.12, Electronic Lien Filings (ELF), for further instruction. Property designations on NFTLs such as "Real Property" and "Personal Property." (These designations should no longer appear on NFTLs as they are no longer filed in "Personal Property" courts.) Edit the BSV and remove the NFTL from ALS. Notify the requester that NFTLs for this recording office are no longer an option for filing. (Releases for Real and Personal Property courts are filed. The release must match the NFTL as filed including the court.) Recording fees are not appropriate, according to the recording office. Verify the fees and edit the fee tables or the BSV accordingly. Lien documents that were manually prepared may need added to the BSV. Check the team's "Add/Delete Basket" for any of these documents, including: Special Condition NFTL MCAR NFTL Partial release Partial revocation Reminder: While any lien document can be manually prepared, manual preparation generally should be reserved for those documents that cannot be generated through ALS or require expedited processing. Manually prepared lien documents that are hand-carried by an RO to the recording office should not be included on the BSV. The RO is normally responsible for paying the associated recording fees. See IRM 5.12.7.10.5, Hand-Carried NFTL for Filing. Any request to add estate tax liens to a voucher should be hand carried to the FORT. Take all actions to update the BSV to reflect changes identified for the 668Y and 668Z listings and add/pull any inappropriate documents before printing the BSV. Inform your manager when complete resolution of the listings cannot be reached or when a release has been removed from the BSV. Ensure that you refer to the range of dates listed on the BSV and print all documents for each day. Refer to the ALS User Guide, Chapter 11, Billing Voucher, Listings and Lien Documents, for specific instructions.

# Editing the Billing Support Voucher

5.19.12.3.4 (04-28-2015) Editing the Billing Support Voucher BSVs can be researched by invoice number and specific recording office or by a specific SLID. Editing can be done to change a standard fee or to add or delete a particular document from the voucher. See IRM 5.19.12.5, Recording Fees. History items pertaining to any editing of a particular BSV are stored separately from NFTL history. This history becomes part of the voucher history. Review and editing of the voucher to correct fees and add or delete documents must be done before documents are printed. When adding a partial release to a voucher use the SLID of the original NFTL. DO NOT use the SLID of the Spec Doc. Note: If you input the Spec Doc SLID, this will cause the system to jam during the printing process and will delay lien processing. If there are two partial releases on the same NFTL, only the last partial release will be produced. When this occurs, manually add the second partial release to the voucher without the input of the SLID number. Input a history to ALS voucher identifying the recording office and reason for adding.

# Printing and Mailing Documents for Recordation

5.19.12.3.5 (09-09-2021) Printing and Mailing Documents for Recordation Lien documents are batched by ALS for printing. Document batches are ready for printing after all the following have occurred: The BSV is updated as needed. All additions to the print batch have been inserted. All documents identified to be removed, have been removed. Follow instructions in the ALS User Guide, Chapter 12, Printing Documents, for printing the document batch. After all documents have been printed, reviewed, and any corrective actions taken, associate the appropriate voucher and prepare for shipment to the recording office. Once packages are complete, ensure all recording offices with the same voucher number are together. Ensure the address of the recording office is visible and correct. If incorrect, update as necessary and notify the ALS coordinator so that ALS can be updated. Carry the package to the clerical team, which will take the packages to Receipt and Control for mailing. Date stamp the copy of the BSV and file in a designated area by county. This is usually done by the CLO clerical team. Note: The date stamps are in a locked, secured area and must be signed out when used.

# Input of Date Stamp and Pay Certification on ALS

5.19.12.3.5.1 (09-09-2021) Input of Date Stamp and Pay Certification on ALS Once the documents are mailed to the recorder, a date must be input to the ALS voucher program to indicate the mail out date. Also, a payment certification must be entered to generate the payment file for processing by Accounts Payable Financial Operations at the Beckley Finance Center. Enter the date stamp from the file copy of the BSV into ALS before 11:00 A.M. (EST/EDT). See the ALS User Guide, Chapter 11, Billing Voucher, Listings and Lien Documents, for instructions. When entering the date stamp, ALS prompts the user for payment certification. This must also be entered into ALS before 11:00 A.M. (EST/EDT) to ensure the electronic payment is received timely. See the ALS User Guide for instructions. Note: Due to time constraints, day shift teams input the date stamp and pay certification for the swing shift team. The team manager or lead TE reviews the date stamp report to ensure all vouchers were date stamped timely and accurately. The manager signs and dates the report, which is stored by the team. If there is a missing or late entry on the report, the FORT must be notified immediately. For electronic filing recording offices, the file transmission date is the date used for the date stamp. IRM 5.19.12.12, Electronic Lien Filings (ELF), for information on ELF. Unless unusual circumstances exist, all documents with the same voucher number within the state should be mailed the same day. Due to some recording offices requiring payment before the documents are recorded, the mailing package may be held by CLO so the payment reaches the recording office first.

# Returned Documents from Recording Offices

5.19.12.4 (04-28-2015) Returned Documents from Recording Offices Recording offices return certain lien documents after they have been recorded. Sometimes, and for a variety of reasons, they return documents without recording them. These are also known as rejects. Processing the returned documents depends on whether they were recorded prior to their return. SPECIAL NOTE: Although often used interchangeably, there is a legal distinction between "filing" and "recording" a document. This distinction becomes crucial when a recording office has not processed the lien documents and there is a dispute regarding lien priority or compliance with filing requirements. Generally speaking: The IRS files lien documents by delivering them to the recording office. (Delivery may be done by mail, in person, or electronically) The recording office records the lien documents when they are entered into the public record. Some states also require the "indexing" of the lien documents to complete the process. Note: See IRM 5.17.2.3.1, Purpose and Effect of Filing Notice, for more information.

# Recorded Documents

5.19.12.4.1 (06-03-2020) Recorded Documents The IRS requests that recording offices return NFTLs, amended NFTLs, and refiles after the documents are recorded so that recording data can be input to ALS. The IRS does not request the return of other lien documents (e.g., releases and withdrawals) after recordation, but some recording offices might return them. Recording data for these other documents is not input to ALS. Note: ALS does allow for the recording date for revocations of release following a different process. The recording date for any revocations returned from the recording office should be input to ALS. The priority of the federal tax lien is often based on the filing date of the NFTL. It is crucial that recording data is input accurately and timely. Also, incorrect data can impact the future release of the lien. When recorded documents are received back from the recording office review them to ensure all documents in the batch have recording information. Also, check the batch for the following: Duplicate NFTL filings, e.g., the recording office filed both parts 1 and 2 of the NFTL (IRM 5.19.12.2.4, Duplicate Filings of NFTL) NTBFLs that should not have been filed (IRM 5.19.12.2.3.3, Not to Be Filed Lien Record) Information to indicate rejected documents Checks for overpayment of recording fees Note: If a refund check is included, follow discovered remittance procedures in IRM 5.19.12.4.2, Unrecorded Documents. Information regarding changes in recording fees or general information from the recording office Note: Change information must be forwarded to the team manager and as an ALS Referral to the FORT for verification and input. Recording information is input to ALS through the COURT screen. See IRM 5.19.12.4.1.1 below. If the document is a MCAR NFTL or release, send the document to its originator using a Form 3210. These types of documents are not loaded or controlled on ALS. If document is for estate tax or a release, send the document to the FORT. See IRM 5.19.12.2.5.1, NFTLs for Estates, for information on processing estate tax liens. Recording information must be input into ALS within ten (10) business days after receipt of the lien document from the recording office.

# Court Recording Information

5.19.12.4.1.1 (09-09-2021) Court Recording Information The court recording data (CRD) on returned documents will vary in the data provided and the way it is provided. Most often the CRD is on the lien document, but some recording offices may list the CRD on the voucher or a separate spreadsheet. If the data returned is not understandable, use available research tools to resolve including, if needed, contacting the recording office. Some recording offices only use recording numbers, some use book and page numbers, some use serial or UCC numbers, and some use a combination of the above. The clock time when the document was filed is not used by ALS and inputting it is not necessary. The COURT input data screen on ALS can be set to go directly to the fields that are required by the specific recording office. This is referred to as the "Court Recording Window Flow." See the ALS User Guide, Chapter 7, Input Court Data, for the combinations available for set up. If a change to the required fields is identified, forward the information to the ALS Coordinator through your manager or lead TE. Provide the name of the recording office and what fields the recording office uses. If combinations not listed in the ALS User Guide are identified, explain this on the request to the ALS coordinator. The ALS coordinator may be able to arrange an additional combination with the ALS programming staff. Note: Prior to requesting an additional combination, be sure to verify the field is required information by the recording office. Input the CRD for each lien document. See the ALS User Guide for instruction. Verify the data is input to the correct SLID and is entered correctly. Note: Incorrect data can cause future documents, such as a release of lien, to be rejected by the recording office. If there is not sufficient space in ALS to enter the full recording number supplied by the recording office, drop the first two (2) digits of the year and use the rest of the data (e.g. "2019098765" would be "19098765" ). If not previously done, also take the actions below. Contact the recording office to ensure this will not cause future, related documents to be rejected. If no resolution is met, refer to FORT. Put a history on MAINTXC of the agreement. When inputting recording information and it is discovered that the lien document already has recording information, verify the SLID and the recording office on the document are the same as on ALS. Conduct additional research as needed to determine if this is a duplicate filing. If it is a duplicate, see IRM 5.19.12.2.4, Duplicate Filings of NFTL, for further instruction. Once all of the data is input to ALS, verify that all lien documents were recorded by reviewing the associated voucher on the ALS voucher program. Refer to the ALS User Guide for more information. If the documents were returned without a BSV attached, find the voucher number by researching one of the SLIDs in the batch on ALS COURT screen. Verify that all documents on the BSV have been recorded by checking the recorded document indicator on the first page of the voucher. If the voucher program does not show all lien documents as recorded, take the additional steps as needed. Check the voucher for the SLID that does not show up as recorded. Verify the lien document was sent with the voucher. Check if the document was an estate or MCAR NFTL, a non-attachment, or any other document that was added to the BSV without a SLID. When a discrepancy is discovered or not all lien documents were returned, contact the recording office to determine why the recording information was not returned. Input a history of your findings on the voucher program. Reminder: When inputting a history to the voucher program, identify the recording office impacted by the history. The voucher number is for all recording offices within the state. Recording information must be input to ALS within ten (10) days after receipt of the document. Use OFP 790-69030 for time spent inputting recording information and OFP 790-69040 for sorting and reviewing incoming documents.

# Unrecorded Documents

5.19.12.4.2 (09-09-2021) Unrecorded Documents Recording offices might return (or reject) documents that are unrecorded for various reasons including, but not limited to, the following: Incorrect fees paid, e.g., a batch of lien documents is sent to a recording office with an amount that is not consistent with the fee schedule for the recording office Overpayment of fees, e.g., the recording office receives a payment larger than is needed Release or withdrawal documents filed with missing or incorrect recording information Documents were sent to the wrong recording office Lien documents might be rejected in whole batches or individually, based on the recording office and the reason for the rejection. The ALS voucher program will be used for tracking of rejected lien batches and individual documents that are rejected. Refer to the ALS User Guide, Chapter 11, Billing Voucher, Listings and Lien Documents, for information on how to use this tool in the voucher program. When document(s) are returned as unrecorded, research the situation and take corrective action as needed. These actions may include, but are not limited to, the following: Correcting the fees and/or forwarding an updated schedule of fees to the ALS Coordinator. Processing an overpayment following IRM 5.19.12.5.1, Refund Received from Recording Offices. Researching and correcting CRD in ALS. Updating filing location information. Input a history on the voucher on ALS for the rejected documents. The history should include the recording office ID number, state the voucher was rejected, and specify the reason for the rejection. If specific documents from a batch were rejected, the history should also include the SLIDs. Return the corrected document(s) to the recording office. If rejected due to an IRS error, send apology letter with returned documents. See Exhibit 5.19.12-5, Sample Letter to Recording Office on Rejected Lien Documents. Whenever possible, use the same voucher to re-send the documents to the recording office. A written history must be placed on the file copy of the voucher. It must include name, actions taken, and date closed along with a new date stamp showing the date it was mailed. If using the same voucher is not possible, use a different voucher. If only specific documents were returned unrecorded, add the corrected documents to the next voucher that will be going to the recording office. If no voucher is going out on the next processing day, generate a new voucher for the documents. Rejected lien documents should be tracked from the time of receipt until resolution is made. All actions taken should be notated on a reject log spreadsheet. The manager or lead TE should check and initial the spreadsheet, thus verifying all information is correct and all inclusive. If the reject cannot be resolved at team level, the case should be referred to FORT for resolution. Note: If the documents returned with the rejected voucher have been recorded, these documents are not rejected and should not be counted as such. Resolution should be completed within five (5) business days after receipt in CLO, this corresponds with the number of days to process lien document batches. See IRM 5.19.12.3, Document Printing. Copies of the rejected vouchers and supporting documentation are retained for periodic review and analysis. For time spent working unrecorded documents, use OFP 810-69150.

# Recording Fees

5.19.12.5 (09-09-2021) Recording Fees Most recording offices charge a fee for recording documents. The amount charged varies by recording office and by the type of document being recorded. Periodically recording offices change their fee schedule. When notification is received from a recording office on fee changes, immediately forward the information to the manager or lead TE of the team responsible for filing with the recording office. If the notification is received through a phone call, complete a Team to Team referral and an ALS Coordinator form and forward to the appropriate team. Once the appropriate team receives the change information, the actions below should be taken. Verify the request is not a previous action. Inform the team of the fee changes immediately so any pending vouchers can be adjusted. Notify the ALS Coordinator to update the recording office fees on ALS.

# Refund Received from Recording Office

5.19.12.5.1 (06-03-2020) Refund Received from Recording Office It is important that fee schedules are kept up-to-date and that vouchers properly reflect the documents being filed so that the amount paid to the recording office in association with the filings is accurate. At times, normally because of rejected documents, the amount paid may exceed the amount due. Often this overpayment is resolved with adjustments in future vouchers, but occasionally a recording office will refund the overpaid amount to CLO. Generally a recording office refunds overpayment in the form of a check; however, it might return cash. If a recording office returns cash as a refund of fees paid to them and the cash is in excess of $1.00, obtain a money order made payable to "U. S. Treasury" . Use part of the cash returned for the money order fee. If a recording office returns cash as a refund of fees paid to them and the cash is $1.00 or less, no money order is needed. Complete a Form 3210 indicating the proper fiscal year commitment funding code and, if known, the BSV number associated with the overpayment. Include a copy of the money order receipt, if applicable. Mail the Form 3210 with the check, money order, or cash (if less than $1.00) to the Accounts Payable Financial Operations (at the Beckley Finance Center) via the Receipt and Control Section. Notate the BSV, if known, that a check was returned and update the ALS voucher history. In the notation include the following information: Your name The amount of the refund Check number or type of refunds (e.g., cash, money order, etc.) Reason for the return, if one is given The date

# Collection Due Process

5.19.12.6 (06-03-2020) Collection Due Process IRC 6320 requires the IRS to provide taxpayers with notification when an NFTL is filed. If it is the first time an NFTL has been filed for the tax period, the notice provides the taxpayer with information regarding their right to a hearing and the amount of the assessed balance. This notice is known as a Collection Due Process (CDP) notice. The CDP notice advises the taxpayer that they have 30 days to request a hearing on the filing of the NFTL. The notice also provides the taxpayer with information on how to obtain a certificate of release and contact information for questions. See IRM 5.12.6, Appeals Processes Involving Liens, for additional information on CDP notices for NFTLs. To comply with IRC 6320, Letter 3172, Notice of Federal Tax Lien Filing and Your Rights to a Hearing Under IRC 6320, is provided to the taxpayer by certified mail, registered mail, or in person. The following documents are sent with the Letter 3172: A copy of Form 668(Y) (C), Notice of Federal Tax Lien (If filing in an electronic recording office, a facsimile copy of the NFTL is sent) Publication 594, The IRS Collection Process Publication 1450, Instructions for Requesting a Certificate of Release of Federal Tax Lien Publication 1660, Collection Appeal Rights Form 12153, Request for a Collection Due Process or Equivalent Hearing Normally, the process of generating CDP notices begins when the Billing Support Vouchers (BSV) are printed from ALS to transmit the NFTLs to the recording offices (or when NFTLs for electronic filing locations are approved). The day after the NFTLs are printed, the CDP notices are generated and forwarded to Correspondence Production Services (CPS), which prints and mails the notices in accordance with legal requirements. ALS calculates the taxpayer's 30-day response due date for the CDP notice. The Letter 3172 must be mailed within five (5) business days after the NFTL is filed. For purposes of this calculation, the NFTL is considered filed on the date it should be received by the recording office. The IRS calculates an estimated filing date by adding three (3) business days to the NFTL mailing date. The taxpayer's response due date on the letter is determined by adding five (5) business days plus 30 calendar days to the estimated filing date. Example: An NFTL is mailed April 3, 2020. The CDP notice must be mailed by April 15, 2020 (i.e. April 3 plus three (3) business days plus five (5) business days). The taxpayer's response due date is May 15, 2020 (i.e. 30 days later). CPS receives a file from ALS each Wednesday and Friday night which contains data for CDP notices. These notices are printed and assembled with the appropriate publications and mailed by certified or registered mail to the taxpayers and co-obligors. The generation, printing, and mailing of the notices follows an established schedule to adhere to the five-day requirement for notification as stipulated in IRC 6320. See IRM 5.12.6.3, Collection Due Process for NFTL Filing, for further details.

# Certified and Registered U. S. Postal Listings

5.19.12.6.1 (04-16-2024) Certified and Registered U. S. Postal Listings Certified and registered mail listings are generated to show all the notices that were mailed on a specific date. The listings show a United States Postal Service (USPS) date stamp to indicate that CDP notices were mailed and provide documentation that the IRS complied with the notification requirements of IRC 6320. CDP notices mailed to an address within the United States; U.S. territories of Guam, Puerto Rico, Virgin Islands, and Saipan; and APO/FPO addresses are mailed certified. ALS produces U. S. Postal Form 3877 along with the taxpayer notice in a file sent to the CPS. The Form 3877 lists the certified mail number and the name and address of the receiving taxpayer. CDP notices mailed to foreign country addresses are mailed registered. ALS produces a Registered Mail Listing along with the CDP Notice. Once CPS prints and mails the taxpayer notices, the certified and registered mail listings are stamped by the USPS with the date of mailing and forwarded to CLO for record keeping. Note: Listings may be forwarded to CLO as hard copy documents or electronically, as determined by CLO management. Copies of the weekly certified and monthly registered listings can be found on Control D. These copies are used to monitor for receipt of the USPS date-stamped listings. If the date-stamped listing is not received within 14 calendar days from the date of the listings, contact the print site to secure the date-stamped copy. When the date-stamped listing is received, verify that each page is date-stamped with a legible USPS date stamp and no pages are missing. Contact the print site to secure missing or illegible pages. After verification that all pages are received, and as resources are available, scan the listings for electronic storage (e.g., cloud, portable hard drive). Store certified and registered listings separately. Review the scans to ensure the following: All pages have been scanned. The USPS date stamp is legible. The media is searchable. Label the records by content (Registered or Certified Form 3877), month and year. If scanning is being completed by another area, in addition to the above, verify that all paper listings and media have been returned to CLO and all pages have been scanned. Retain the records in date order for ten (10) years, then forward to the Federal Records Center. Retain scanned paper listings for three (3) years, then forward to the Federal Records Center. When a request for a Form 3877 is received, use ALS Display to research the certified mail number. Follow local procedures for pulling a copy of the Form 3877 and forwarding it to the requester.

# Other Notices

5.19.12.6.2 (06-03-2020) Other Notices Under IRC 6320, the IRS must notify taxpayers in writing of their right to a CDP hearing with the Office of Appeals the first time a tax period is included on an NFTL. If the same tax period appears on a subsequently filed NFTL, the IRS notifies the taxpayer of the filing, but the taxpayer is not entitled to CDP rights. Additionally, the IRS notifies a Power of Attorney (POA) when an NFTL is filed against their client and notifies a third party if they have been named on a special condition NFTL. The most common non-CDP notices are normally generated through ALS and printed and mailed by CPS. Some other notices require manual preparation and issuance by the requester. The table below describes the different notices and how they are generally issued. Notice Issued to... Issued by... Letter 3171, Notice of Federal Tax Lien Additional Filing Taxpayer when an NFTL is filed on a tax period included on a previous NFTL CPS Letter 3262, Notice of Federal Tax Lien Filing - Power of Attorney POA when a new NFTL is filed and the taxpayer (client) received Letter 3172 CPS Letter 3271, Notice of Federal Tax Lien Additional Filing - Power of Attorney POA when an NFTL is filed on a tax period included on a previous NFTL and the taxpayer (client) received Letter 3171 CPS Letter 3886, Special Condition Notice of Federal Tax Lien Filing - Taxpayer Taxpayer when a special condition NFTL is filed against a third party holding title to taxpayer assets Requester Letter 3177, Special Condition Notice of Federal Tax Lien Filing - Third Party Third party when a special condition NFTL is filed against them for holding title to taxpayer assets Requester Letter 3527, Notice of Federal Tax Lien Filing - Child Support Obligation Taxpayer when an NFTL is filed for outstanding child support payments Requester The above non-CDP notices are sent by regular mail. These notices are NOT sent by certified mail.

# Customer Contacts

5.19.12.7 (09-09-2021) Customer Contacts CLO receives inquiries and requests from a variety of internal customers (e.g., Field employees, Taxpayer Assistance Centers (TAC)) and external customers (e.g., taxpayers, practitioners, third parties). CLO must provide customers complete and accurate responses. It is important that all employees are familiar with the major duties and responsibilities in providing quality service to customers. See the following sections for general guidance on customer contacts: IRM 21.1.3, Operational Guidelines Overview IRM 21.1.1.4, Communication Skills IRM 21.3.3, Incoming and Outgoing Correspondence/Letters

# Internal Contacts

5.19.12.7.1 (06-03-2020) Internal Contacts IRS employees are considered internal contacts for CLO. Recording offices are also considered internal contacts for CLO relative to the methods of communication available to exchange information for the effective processing of lien documents. Specific taxpayer account information should not be disclosed to recording offices without proper authorization. Contacts can be made by mail or fax and, with an IRS employee, by secure email. When faxing confidential information, follow fax procedures contained in IRM 10.5.1.6.9.4, Faxing. Caution: When emailing Personally Identifiable Information (PII) or Sensitive But Unclassified (SBU) information messages or attachments, always use IRS approved encryption technology. See IRM 1.10.3.2.1, Secure Messaging & Encryption.

# Request to Stop a Lien Document

5.19.12.7.1.1 (06-03-2020) Request to Stop a Lien Document There will be times when an IRS employee will contact CLO to have a lien document stopped before filing. Example: The NFTL was requested and the taxpayer full paid the following day. Example: A release of lien was systemically generated, but the payment causing the release was reversed. The ability of CLO to stop a lien document before filing depends on whether the document has been printed and sent to the recording office. NFTLs can be removed (deleted) from ALS prior to printing of the NFTL. When a request to stop the NFTL has been made and the NFTL has not been printed, take the actions shown below. Do not print the NFTL. Research to see if a voucher has been built that includes the NFTL. Immediately give all research and documentation about the deletion to the team manager for review and to delete the NFTL from ALS and, if built, the BSV. If the BSV has been built but the NFTL has not yet printed, ensure the employee processing the documents is aware of the request to remove the NFTL from the voucher. After printing the NFTL but before sending it to the recording office, the NFTL must be physically pulled from the batch prepared for mailing. Once successfully pulled, take the actions shown below. Give all information immediately to the team manager for review and to delete the NFTL from ALS and the BSV. Ensure the employee processing the documents is aware of the request to remove the NFTL from the voucher. After sending the NFTL to the recording office, advise the requester the NFTL cannot be stopped by CLO. Depending on when the NFTL is stopped in the process, the CDP notice may still be generated. Advise the requester of the possibility that the CDP notice may be issued even though the NFTL is not filed. Note: The issued CDP notice is valid even if no NFTL is filed. See IRM 5.12.6.3.16, Invalid CDP Notices and Rescinding the CDP Notice. In situations where a request is received to stop the filing of other lien documents, most commonly a release or withdrawal, similar processes as described above apply. Instead of deleting the lien document from ALS though, the action generating the lien document must be reversed. A user with the appropriate permissions, usually a manager, can reverse a release or withdrawal on ALS. Refer to the ALS User Guide for direction. If the release, withdrawal, or other document has been sent to the recording office, CLO can attempt to contact the recording office to see if they could reject the document before recordation, but generally the document cannot be stopped.

# Taxpayer Assistance Center Requests

5.19.12.7.2 (06-03-2020) Taxpayer Assistance Center Requests To expedite securing a payoff letter or release of lien, taxpayers may go to a Taxpayer Assistance Center (TAC) to request assistance. If the TAC office receives a request for a payoff, the TAC office should do the computation unless the request is for a Restricted Interest (RI) or restricted penalty account. See IRM 21.3.4.13.1, Lien Payoff Requests. When there is restricted interest and/or penalties the field assistor should send a request through secure email and in the subject line state Lien Payoff Request-Restricted Interest/Penalty Account/Walk-in Taxpayer. The following information should be included in the email: Taxpayer name and address and identifying number Taxpayer's telephone number and the best time to reach them, if additional information is needed Computation date for payoff Tax module(s) to include in the payoff Requester's name and post of duty Any conditions that may impact calculation, e.g., combat zone dates All CLO team email boxes must be monitored for expedited TAC requests. If the payoff request is sent to the Walk-in Mailbox in error, forward the email to the correct team with a copy to the requester. The field assistor will advise the taxpayer the request has been submitted and when they can expect a response. The taxpayer will be supplied the toll-free number to CLO. Complete the computation using cc COMPA or COMPAF, as necessary. For cases requiring further computations, forward the request to the CLO FORT for calculation and possible referral. CLO FORT should provide a time estimate for when they will provide a response to the payoff request. Reply to all persons on the requesting email when there are questions needing clarification or acknowledging receipt of the request. Also, reply to all with the estimated time-frame for sending the payoff to the taxpayer. Prepare a payoff letter after receiving the interest computations and mail it to the taxpayer. Note: In the event the taxpayer has an urgent need, the TAC manager should contact the CLO manager to determine the time frame for completion of the request. A taxpayer visiting a TAC office might request an immediate lien release to hand carry to the recording office. In these situations, the TAC assistor will conduct initial research to determine the status of the taxpayer's account and will contact CLO, as needed. If the taxpayer is fully paying the liability by cash, certified funds, or other secured payment type described in IRM 5.12.3.3.1.1, Liability Satisfied by Payment, the field assistor will send a request for lien release through secured email to CLO. The request will include: The taxpayer's name and TIN The tax periods being satisfied How the periods are being satisfied (cash, certified funds, satisfied previously on IDRS), the amount of the payment, and a statement that the account is or will be in status 12 Date of the payment or when the modules were satisfied The Field Assistor's name and post of duty The name of an additional field assistor to cc on response As needed, ask for any additional information or clarifications by secure email. This should include any alerts to system down issues. It is the responsibility of TAC to ensure the accuracy of all requests for an immediate release of a lien. CLO does not verify the validity of the request for a lien release since TAC has the authority to release a lien under IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates. However, review the request to ensure that all the modules on the NFTL are addressed either by the payment received by TAC or by showing satisfied on ALS. If any module on the NFTL is not addressed, contact TAC for additional research or clarification. Verify the NFTL has court recording data on ALS. If there is no recording data, use available research methods to locate the recording information. Inform the TAC employee of the delay. Input the release on ALS following standard processing procedures, with the exceptions noted below. Use your TSIGN as the requesting employee. Indicate the release has already been recorded so the release does not go onto the voucher for the next printing cycle. Advise the manager that immediate approval of the release is needed on ALS. If the lien has self-released, advise the TAC employee of the situation. If the taxpayer still wants a certificate of release, prepare one following the instructions in IRM 5.19.12.2.7.4, Self-Releasing Liens. Print the release, scan it, and send it to the requester by secured email. For NFTLs filed in electronic recording offices, provide a facsimile of the NFTL showing the release status and advise the assistor of the ELF procedures. Update ALS with a history about the immediate release, specifying the requesting field assistor's name and post of duty. Notify the team responsible for processing lien documents where the release will be hand carried so the release can be removed from the voucher and print batch. The process from receipt of the TAC email to the return of the release should be completed within one (1) hour. If it will take longer than one hour, contact the TAC employee immediately. Note: Per IRM 21.3.4.13.2, Lien Release Requests, TAC must contact CLO by 3:30 p.m. (local TAC office time) to get an immediate lien release. Requests from Hawaii and Alaska are based on Pacific time. Upon receipt of the release, the TAC assistor will date stamp the certificate and provide it to the taxpayer. The taxpayer will be advised that when they hand carry the release to the recording office, they may be charged a fee to file the release. If the payment is made by personal check or non-certified funds, the field assistor will process the payment and update IDRS with the taxpayer's most recent address, if needed. TAC will inform the taxpayer that the lien will be released within 30 days and a copy of the certificate of release will be mailed to their address.

# Taxpayer Advocate Service (TAS)

5.19.12.7.3 (09-09-2021) Taxpayer Advocate Service (TAS) TAS referrals regarding NFTL actions are sent to the FORT via Form 3210. The FORT TAS liaison will acknowledge receipt of the TAS referral by telephone or email within: One (1) business day of receipt of an expedited case (Case Criteria 1-4, Economic Hardship), or Three (3) business days of receipt of a non-expedited case (Case Criteria 5-8, Systemic Hardship). The FORT forwards the TAS referral to the applicable lien team. Upon receipt, the team manager takes the following actions. Assign the case to a tax examiner. Monitor the case assignment log to ensure timely case completion. The tax examiner must complete the requested action: Within three (3) business days of receipt of expedited cases, or By the requested completion date shown in Item 3 of the Form 12412, Operations Assistance Request (OAR), for non-expedited cases. The tax examiner works with the TAS liaison in the FORT to resolve any issues that prevent case resolution. If the tax examiner working the OAR determines additional research or documentation is required on an OAR, the tax examiner contacts the assigned TAS employee within one (1) workday of the determination, or within one (1) business day of the receipt of the OAR on expedited cases. If the assigned TAS employee cannot provide the additional information within three (3) business days of the request, the tax examiner may return the OAR to TAS and the case will be closed out of inventory. If the case cannot be completed by the requested completion date, the tax examiner must contact the TAS liaison to renegotiate a completion date. If resolution of the case cannot be completed by the negotiated completion date or there is disagreement about the negotiated completion date, the tax examiner should elevate the disagreement to the team manager. After taking the necessary actions to resolve the issues of the case, complete Form 12412, Section VI, 1a & 1b and return the completed case to the team manager or lead TE for review. If requested case actions cannot be completed, return the case to the TAS liaison with an explanation of why case cannot be resolved. The manager takes the actions shown below. Reviews completed cases to ensure correct actions were taken. Completes Section VI of Form 12412. Sends the case back to the FORT TAS liaison and the TAS Case Advocate.

# Recording Offices

5.19.12.7.4 (09-09-2021) Recording Offices CLO might be contacted by recording offices via the internal toll-free line or other means regarding payment or recording issues. As much as possible, the assigned state team should attempt to provide "one-stop service" to facilitate the filing process. When a call is received on the toll-free line from a recording office, identify the recording office's information and determine the problem. If the problem can be resolved independently, take the appropriate actions. Such issues may include, but are not limited to, verification of a walk-in release, fee adjustment, and missing or incorrect recording data. If you cannot resolve the problem, place the caller on hold and contact the manager or lead TE of the team assigned the recording office's state. If contact is made, transfer the call to the manager/lead's Aspect telephone line. Otherwise, document information about the call and hand carry to the appropriate manager or lead TE. If the problem cannot be resolved while the recorder is on the line and the situation is such that a document cannot be recorded and/or the entire BSV may be rejected, promise a call back within the hour and take appropriate action to resolve the problem. When notified of a recording issue by means other than by telephone, attempt to resolve the issue by conducting research and, if necessary, contacting the recording office. In situations where the recording office raises a question about a payment, explain the payment process, including TOP offset. As needed, provide one of the following resources as a contact point for further information: Internet Payment Platform (IPP) at (866) 973-3131 or email ippgroup@bos.frb.org Accounts Payable Financial Operations (fka Beckley Finance Center) Lien Technician at (304) 254-3300 Treasury Offset Program at (800) 304-3107 If there is a payment issue that cannot be resolved through IPP or TOP offset, elevate the issue to Accounts Payable Financial Operations. They will research the issue and contact the recording office, if necessary. If Accounts Payable is able to resolve, they will notify the CLO team. If Accounts Payable is unable to resolve, refer to the FORT for resolution. For all other communications from the recording offices, determine the appropriate action to take. As needed, consult the team manager, lead TE, or FORT. Document the ALS voucher program with the steps taken to resolve an issue. For a recording issue that cannot be resolved, elevate the issue to the FORT.

# Treasury Offset Program (TOP)

5.19.12.7.4.1 (09-09-2021) Treasury Offset Program (TOP) The Treasury Offset Program (TOP) is a federal, centralized offset program administered by Financial Management Services (FMS) to collect delinquent debts. Before a vendor (i.e., recording office) is issued a federal payment (including payment of filing fees), FMS searches its database to determine whether the jurisdiction as a whole owes a federal debt. A TOP offset occurs when another department within the same government jurisdiction as the recording office owes a federal debt. The payment designated for the lien document fees is offset to apply toward the debt of the other department. The TOP offset is usually discovered by the recording office when they receive a diminished amount for the recording of the lien documents. The reduced amount may be as low as one dollar ($1.00), but will not be less than that amount. TOP offsets continue until the debt of the other department is fully paid. When a call from a recording office about a TOP offset is received, attempt to resolve the issue by explaining the offset program. Additional information can be found in Pub 1468, Guidelines for Processing Notice of Federal Tax Lien Documents, and on the TOP website (TOP website (https://fiscal.treasury.gov/top/). If unable to resolve the issue, immediately refer the matter to the FORT. If the FORT is unable to resolve the issue by providing additional information to the recording office, research is conducted for the specific state law that covers the filing responsibility of the particular recording office. The FORT prepares a letter to address the situation and demand that the lien documents be filed. As needed, Counsel may be consulted to assist with the research and the wording of the letter. See Exhibit 5.19.12-4, Sample Letter to Recording Office on Treasury Offset Program, for a sample format of a letter developed with Counsel. The letter is signed by the CLO Program Manager and mailed to the recording office. If the BSV and documents were rejected by the recording office, return them with the letter serving as a transmittal. If the recording office refuses to file the lien documents after receiving the letter from the Operations Manager, refer the issue back to the FORT. The FORT will prepare a formal referral to Counsel for legal intervention.

# External Contacts

5.19.12.7.5 (04-16-2024) External Contacts CLO is regularly contacted by taxpayers, taxpayer representatives, and other third parties including banks, title companies, and prospective purchasers. These are considered external contacts. These contacts can be by mail, fax, or on the Aspect toll free line. Disclosure rules must be followed on each and every contact. Below are only some of the disclosure rules. Before disclosing any tax information, verify that you are speaking to the taxpayer or their authorized representative. See guidelines in IRM 21.1.3.2.3, Required Taxpayer Authentication. Exercise caution when leaving information on answering machines or voice mail. See IRM 10.5.1.6.7.2, Answering Machine or Voicemail. Observe requirements before faxing confidential information to taxpayers. See IRM 10.5.1.6.9.4, Faxing. Be aware of guidelines for sending emails with taxpayer information. See IRM 10.5.1.6.8, Email and Other Electronic Communications. An individual is entitled to account information for any assessment for which they are liable, regardless if their name is on an NFTL. Conversely, an individual is NOT entitled to account information for assessment for which they are NOT liable, regardless if their name was inadvertently included on an NFTL. For the latter situation, follow procedures to amend the NFTL to remove the taxpayer's name or the taxpayer may request an NFTL withdrawal. Any correspondence being faxed or mailed to the taxpayer must have the SSN redacted to the last four digits in the SSN. When speaking to the taxpayer, verify the taxpayer's address. If the current address differs from IDRS, update the IDRS address using an appropriate command code (e.g., ENREQ). Be sure to enter your name, title, and phone number in the REMARKS field. See IRM 21.1.3.20, Oral Statement Authority, for guidelines on updating the taxpayer's address. Any correspondence returned to CLO as undeliverable should be destroyed in accordance with locally prescribed guidelines. Correspondence not requiring a follow-up action by the addressee should not need additional research.

# Third Parties

5.19.12.7.5.1 (09-09-2021) Third Parties Disclosure of information on a request from third parties requires one of the following: Valid Form 2848, Power of Attorney and Declaration of Representative Valid Form 8821, Tax Information Authorization Telephonic authorization from the taxpayer in accordance with IRM 11.3.3.3.2, Requirements for Oral Authorization A written request from a person who demonstrates that they possess, or intend to obtain, a right in the property attached by the lien. The written request should include the reasons the information is desired and properly identify the NFTL in question. A prospective purchaser should attach a copy of the sales contract or a lender loan application. See IRM 11.3.11.10, Disclosure of Amount of Outstanding Lien. Note: IRM 21.1.3.3, Third Party (POA/TIA/F706) Authentication. provides instruction on verifying and authenticating the third party representative. For payoff requests where specifics of the taxpayer's account are not discussed, the authentication of the third party's SSN, as described in IRM 21.1.3.3(3), is not required. The third party's authorization, as evidenced by the Centralized Authorization File (CAF), Form 2848, Form 8821, acceptable written documentation, or verbal statement from the taxpayer, is sufficient to provide the payoff. To authorize a person to act on their behalf to resolve tax matters, the taxpayer must complete Form 2848. To authorize a third party to inspect or receive confidential information, the taxpayer can submit a Form 8821. Verify on IDRS CAF if authorization has been received and established for the taxpayer. If not, the taxpayer or Power of Attorney (POA) needs to submit the appropriate form to receive information on the taxpayer's account. Note: If CLO receives a Form 2848 or Form 8821 that shows the third party is authorized for the tax periods, additional verification of CAF is not needed. When the authorization form is received, review the document to ensure it is valid. Review the instructions for the Form 2848. See IRM 21.3.7.5.1, Essential Elements for Form 2848 and Form 8821. For the purposes of providing a payoff to a third party, Form 8821 and Form 2848 are considered valid if the fields shown below have been properly completed. Failure of the taxpayer to complete the other checkboxes on the forms does not affect validity of the forms. The fields that must be completed are: Taxpayer information Designee/Representative information Tax information/Acts authorized Taxpayer Signature Representative signature and declaration (Form 2848 only) Note: Electronic or digital signatures on Forms 8821 and 2848 are only allowed if the form is submitted through the Taxpayer Digital Communications (TDC) platform. Review the authorization to ensure the tax modules that are listed match the modules on the NFTL(s) in question. If the authorization does not cover the tax periods on the NFTL, send the response directly to the taxpayer and advise the third party of the authorization situation (either verbally or in writing). If the authorization covers some, but not all, of the tax periods on the NFTL, the tax information shown on the NFTL (or Collection due process notice) can be given to the representative as well as a payoff for the full amount of the NFTL. If the representative wants to further discuss the non-covered periods, a revised/new authorization form must be provided. See IRM 11.3.11.10, Disclosure of Amount of Outstanding Lien. If the authorization covers the tax periods on one NFTL but not the tax periods on another NFTL, only the information from the NFTL with the covered tax periods can be given to the representative. Advise the representative that another NFTL is filed, but the information for that NFTL cannot be discussed until a revised/new authorization form is provided. When a Form 8821 or 2848 is received but the authorization is not on IDRS CFINK, input an ALS history with the contact information and years applicable. This can be used for further follow up contacts and letter issuance, and re-submission of the Form 2848 or Form 8821 will not be necessary. Forward the forms to the CAF area when appropriate. Note: Generally, third party requests related to Form 8821 must be made within 60 days of the authorization. However, when Form 8821 is submitted by a mortgage, title, or escrow company in connection with a lien payoff, the form is exempt from the 60-day rule for signature as the request is considered "resolving an issue related to a Federal tax matter." See IRM 11.3.3.2.1, General Requirements for Disclosure to Designee of Taxpayer. When the taxpayer verbally authorizes information to be given to a third party, document the ALS history that verbal authorization was given, who was authorized, the contact information of the third party, and for what tax modules the authorization was given. Note: Once documented, the verbal authorization remains valid until such time as the financial transaction is completed or the authorization is revoked, thereby eliminating the need for a second consent or Form 8821. Upon receipt of an inquiry from an authorized third party, research ALS to verify that an NFTL exists. If an NFTL is not found on ALS ask for additional information to identify why they believe there is an NFTL. Some possibilities and actions to take are in the table below. If the inquiry is for a(n).. Then.. Estate tax lien Provide contact information for the Advisory Estate Tax Group MCAR notice of lien Provide contact information for International State lien Advise the requester to call the State that issued the lien Levy Provide the contact information for the employee or function assigned the case.

# Request for Payoff

5.19.12.7.5.2 (04-16-2024) Request for Payoff Requests for lien payoffs can be received in a variety of ways (e.g., mail, fax, Aspect toll-free line) from a variety of customers (e.g., taxpayers, POAs, authorized third parties). Payoff computations are usually completed manually to generate Letter 3640, Taxpayer Lien Payoff, or Letter 3641, Third Party Lien Payoff (Escrow or Financial Institutions). Note: ALS has a Payoff Utility function that may be used to generate payoff letters. Check with management on its availability. Reminder: Disclosure guidelines must be followed when addressing payoff requests. See IRM 21.1.3.2, General Disclosure Guidelines. When a payoff request is received, research ALS and IDRS to determine the status of the NFTL and the tax periods. If a taxpayer has liabilities under an SSN and EIN, the requests can be worked simultaneously but separate payoff letters are issued. Research ALS to verify that an NFTL exists and whether the NFTL is still in effect. If an NFTL is not found on ALS ask the requester to provide information for why they believe there is an NFTL. The requester may be confusing something else for an NFTL. Some possibilities and actions to take are shown in the table below. If the request is for a(n).. Then.. Estate tax lien Refer the request to Advisory Estate Tax Group MCAR notice of lien Refer the request to International State lien Advise the requester to call the State that issued the lien Levy Refer the request to the employee or function assigned the case. If there is no NFTL but tax liabilities are owed, refer the payoff request based on the status of the tax module(s) as shown in the table in (4) below. Determine whether the request should be referred to another office based on the status of the tax module(s) on IDRS. If status is.. And.. And the inquiry is by PHONE, then.. Or the inquiry is in WRITING, then.. 26 The account is assigned to an RO (i.e., the assignment number does not end in 00) Use RO Lookup in SERP to secure contact information for the assigned RO. Provide the requester the RO contact information. Advise the requester to contact the RO to secure a payoff and/or discuss their account. Fax the request to the attention of the assigned RO. Include Form 8821 if applicable. Email the RO advising of the referral. Include the received date of the request, requester information, if Form 8821 was sent with the fax, and the fax number used. 71 The TC 780 is posted on IDRS (i.e., the OIC has been accepted) Advise the requester to contact the Monitoring Offer in Compromise unit (MOIC) and provide the hot line number as listed on SERP. Refer the request to the MOIC function as shown on SERP. 71 The TC 780 is not posted on IDRS Complete the request. Complete the request. 72 The TC 520 closing code is 60-67, 81, or 83-89 Advise the requester to contact the Centralized Insolvency Operation (CIO) and provide the toll free number listed on SERP (800-973-0424). Fax the request to CIO using the fax number listed on SERP (855-235-6787). 72 The TC 520 closing code is 70-75 or 80 Advise the requester the case is an Advisory issue and provide the phone number of the assigned Advisory Office. See Pub 4235 Fax the request to the assigned Advisory Office. See Pub 4235 72 The TC 520 closing code is none of the above Complete the request. Complete the request. Any not listed Any condition not listed Complete the request. Complete the request. Note: A referral to a centralized function may be subsequently referred, based on the function's internal guidance. For example, a referral to CIO may be referred to Field Insolvency depending on the nature and status of the bankruptcy. Reminder: CLO may complete payoff requests involving accounts assigned to a Private Collection Agency following the instruction in IRM 5.19.1.5.21.4, ACS and FA Taxpayer Contacts on Private Debt Collection Accounts. Refer the payoff request to the assigned function for completion of the request if any of the modules are in the described status as shown in the table. Whenever referring a written payoff request to another function, take the following actions. Send the requester Correspondex Letter 3645C, Case Processing Liens / Centralized Lien Operation, to advise of the referral. Input an ALS history of the request and to which office it was referred. Caution: Occasionally, a payoff request may be returned from the referred function because the case is no longer in their control (e.g., the insolvency case closed but the module status has not been updated). In these situations, and presuming there are no other restricting factors, CLO should complete the payoff request. For requests not in status 26, 71, or 72, or in a condition relative to those statuses (as shown in the table above), complete the payoff request. Use the payoff letter most appropriate for the situation. Letter 3640 (or Letter 3640-B), Taxpayer Lien Payoff Letter 3641 (or Letter 3641-B), Third Party Payoff (Escrow or Financial Institutions) Reminder: Templates of the payoff letters are available through ICS or the Publishing catalog, or locally through CLO management. The payoff letter is usually prepared manually by using data from the AMS Payoff Calculator or IDRS (e.g., command code INTST). The AMS Payoff Calculator and IDRS generate payoff amounts in real time but they do not produce a payoff letter. The data must be transferred to a payoff letter. Note: Occasionally, CLO receives a payoff request for a specific NFTL in a specific recording office. When appropriate, an NFTL-specific payoff letter may be issued but it must be manually prepared. To minimize any misunderstanding about the balance due shown, the payoff letter should show the SLID of the specific NFTL(s) and emphasize that other NFTLs may be filed in other locations. The ALS Payoff utility generates a payoff letter through an overnight process. The letter includes all tax liabilities from all NFTLs in the system. If a tax module is marked as expired on ALS but has a balance due on IDRS due to an extended CSED, how the payoff data is shown on the letters differs based on the overall status of the NFTL. NFTL status Module status Module balance. Letter 3640 Letter 3641 "Self-released" All the modules on the NFTL show as expired There remains a balance due on one or more of the modules Enter the payoff information for the modules under "Other tax debt" Do not include the modules because the NFTL is no longer effective relative to third party claims. "Open" or "Refiled" Some, but not all, of the modules on the NFTL show as expired There remains a balance due on one or more of the modules Enter the payoff information for the modules under "Notices of lien on tax debt" Enter the payoff information for the modules under "Notices of lien on tax debt" Example: The NFTL covering the 30/201012, 201112, and 201212 tax modules was not timely refiled and shows as self-released on ALS. However, there is still a balance due on 30/201112 and 201212. The payoff information for 30/201112 and 201212 should be included under "Other tax debt" on Letter 3640 but the amount should not be included on Letter 3641. Example: The NFTL for the 30/201012, 201112, and 201212 tax modules was timely refiled with respect to 30/201212 only and shows as refiled on ALS. However, there is still a balance due on 30/201112 as well as 30/201212. The payoff information for 30/201112 and 201212 should be included under "Notices of lien on tax debt" on Letter 3640 and Letter 3641. Reminder: After completing a payoff request involving an expired module that has a balance due, the case should be referred to the appropriate function for a revocation and new NFTL determination. See IRM 5.19.12.2.7.4, Self-Releasing Liens. ALS Payoff Utility will compute the payoff amount for modules on TXMOD. If a module is not on the Taxpayer Information File (TIF), use IDRS command MFREQ/RECON to retrieve the tax module and its related entity data from Master File (MF). During dead cycles, MFREQ/RECON are not available so if all NFTL modules are not on TXMOD, prepare a manual computation and letter. Compute the payoff to either the: Date given by the requester, or 30 days from the current date, if no date is given. Be alert to situations that may require special handling. If the tax module has an "I" freeze, it could mean there is additional interest due on the account and the module is not truly satisfied. Follow procedures for restricted interest and send these to the FORT for review and possible referral. If there is a COMP Hold on an account due to a pending adjustment (i.e., TC 29X/30X), an accurate payoff cannot be computed until those transactions have posted. Explain to the taxpayer there is a pending adjustment on the account, a payoff cannot be completed until that adjustment posts, and the requested payoff letter may take longer than the normal processing time. Look at the cycle date next to the pending transaction and complete the payoff at that time. If the computation date is within the grace period of a notice, IDRS or AMS replaces the computation date with the notice date. Depending on whether a specific payoff date was requested and how far the computation date is from the end of the notice period, consider replacing the computation date with the closest date outside the grace period. If the NFTL was filed for a joint liability, there could be additional liabilities under the secondary TIN (e.g., TINs were reversed on a different tax return). Research the secondary TIN to ensure all liabilities owed by the requestor are included in the payoff response. If the taxpayer owes for Shared Responsibility Payments (SRP) assessed under MFT 35, the amount owed should be placed under the "Other Tax Debt" section of Letter 3640. NFTLs are not filed for MFT 35 assessments. Note: MFT 35 assessments only show the primary taxpayer's name and TIN on IDRS. However, if the penalty relates to a jointly filed income tax return, the secondary taxpayer is also liable for the assessment. IDRS computes the payoff amount unless there is a computation hold on penalty/interest requiring a manual computation. If manual computations are needed, complete the computation and, if needed, update the ALS Payoff Utility letter. See IRM 20.1.2, Failure to File/Failure to Pay Penalties, and IRM 20.2.5, Interest on Underpayments. If interest is manually computed, send a copy of the interest computation report to the taxpayer with the payoff letter, pursuant to IRC 6631. If interest or penalty is manually computed, input the amount of the computation to IDRS using the appropriate transaction code (e.g., 190, 270, etc.). Use the "computed to" date for the posting date. Reminder: Under IRC 6651(d)(2), the Failure to Pay (FTP) penalty increases from one-half percent to one percent after final demand. When calculating FTP, add 10 days to the Letter 1058 or Status 58 date to allow for the percentage increase. ALS Payoff Utility requires identification of who has requested the payoff. "T" if the request is from the taxpayer "P" if the request is from a valid Form 2848 or the POA is on the CAF "O" if the request is from a valid Form 8821 or person showing a material interest Reminder: Do not disclose information if the request is not from the person owing the debt or an authorized third party. Before generating any letter, review the accuracy of the following: Entity Taxpayer current mailing address, as verified through request received Tax periods Manual computation of penalty and/or interest Print and send the letter to the taxpayer and/or the authorized third party. For expedited requests fax the request when a fax number has been supplied. For payoff requests processed through the ALS Utility, take note of the following: If the request is input to ALS by 1:00 P.M. EST, the letter will be available on ALS to print and send at 11:00 A.M. EST the next business day. When the payoff request is received by phone, input the letter request to ALS while the requester is on the line. Managers should review the print queue to ensure all payoff letters are printed and mailed timely. For payoff requests received by phone, take action according to the table below. Advise the requester of current processing time frames and, if applicable and appropriate, any reasons the payoff may be delayed (e.g., restricted interest, pending adjustment). If the caller... And... Then... Requests an immediate payoff amount The payoff can be readily computed Compute the amount due using INTST, AMS, or other available program and provide a verbal payoff amount. Requests an immediate payoff amount The payoff cannot be readily computed (e.g., complex calculations, restricted penalty / interest, freeze condition) Inform the customer of the situation. Compute the payoff amount after the phone call ends and, if needed, refer calculations to the FORT or other function. Fax or mail a payoff letter as soon as it is available. Requests a written or faxed payoff amount The payoff can be readily computed Compute the amount due using INTST, AMS, or other available program; manually prepare the Letter 3640/3641; and fax the payoff letter to the caller while they are on the line. If a fax number is not available, mail the letter. Requests a written or faxed payoff amount The payoff cannot be readily computed due to a significant number of modules Request the payoff letter through ALS while the customer is on the line. OR, after the phone call ends, manually compute the amount due and prepare the payoff letter. Fax or mail the Letter 3640/3641 as soon as it is available. Requests a written or faxed payoff amount The payoff cannot be readily computed due to complex calculations, restricted penalty / interest, freeze condition, or other complicating factor. Inform the customer of the situation. Manually compute the payoff after the phone call ends and, if needed, refer calculations to the FORT or other function. Fax or mail the Letter 3640/3641 as soon as the calculations are complete. Note: AMS will provide payoffs for all of the modules on the TIF that the taxpayer owes. For modules not on the TIF, MFREQC must be used to include them. Maintain payoff letters in the team until the letter expires. Input an ALS history once the payoff letter is provided, whether verbally, faxed, or mailed. Notate any special circumstances such as manual processing or need for immediate payoff. When a request for an updated payoff is received from a third party, check the history on ALS to verify that a payoff was previously provided and when. If the history indicates a previous payoff was provided within the last 14 calendar days, verify that it was provided to this same third party by checking their name and address against the payoff letter. If the same third party was previously issued a payoff letter and there have been no other material changes (e.g., no new NFTLs or liabilities to include), provide the updated payoff. A new Form 8821, Tax Information Authorization, is not needed. If there is no history of a previous payoff, it has been more than 14 calendar days, it is a different third party, or there was a material change to the liabilities or third party authorization, treat the request as a new payoff request and follow standard payoff procedures, including securing Form 8821 as needed. Payoff requests must be completed and mailed within 14 calendar days from receipt in CLO. If the request is taken by phone the request must be input directly into ALS while the caller is on hold. Exception: For payoff request being held for pending adjustments (TC 29X/30X), the 14-day time frame is not applicable. The payoff request should be completed as soon as possible after the adjustment has posted. Time spent preparing payoffs and the number of manual payoffs prepared should be reported using the appropriate OFP code. The number of payoff letters generated through ALS are counted systemically and should not be included in individual counts. OFP Code Request received... Count payoff letters if... 700-69000 By phone or by fax/eFax in conjunction with the phone call Manually prepared 810-69070 In writing (e.g., mail, fax/eFax) and not in conjunction with a phone call Manually prepared Note: CLO management provides methodology for counting payoff letters.

# Lien Payment Processing

5.19.12.7.5.3 (04-16-2024) Lien Payment Processing CLO generally does not process payments. Payments sent to CLO as a result of a lien payoff request are processed by Campus Support or a designated payment processing function. When responding to a payoff request, direct the requestor to remit the payment to one of the addresses below based on the mailing type used. Regular Mail Overnight Mail Internal Revenue Service P.O. Box 145595 Stop 8420-G Cincinnati, Ohio 45250-5595 Internal Revenue Service 7940 Kentucky Drive Stop 31-A Florence, KY 41042 Note: The addresses listed above are for CLO correspondence; they are not Submission Processing addresses. Remittances sent to the above addresses are separated by Campus Support and forwarded to Submission Processing. If a copy of Letter 3640 or Letter 3641 is received with the payment, the payment processing function will apply the funds to the open modules as shown on the letter. If the Letter 3640 or Letter 3641 is received with certified funds, the payment is routed to Submission Processing to process the funds. If CLO is notified that the payment received was certified funds, review the case to ensure all the tax periods on the NFTL will be fully satisfied after the certified funds are applied and input a release of the lien on ALS. The release must be input within five (5) business days after notification. Occasionally, a payment may be discovered in the course of sorting CLO receipts. If this occurs, research ALS to determine where the payment should be posted and complete a Form 3244, Payment Posting Voucher, indicating the following: Tax module for the payment to post Date payment received Amount of payment TC 670 with a designation payment code (DPC) of 007 Note: A separate Form 3244 must be prepared for each tax module on which money is being applied. In addition to the Form 3244, complete a Form 4287, Record of Discovered Remittances. See IRM 3.8.46, Discovered Remittance, for additional information. Forward the completed Forms 3244 and 4287 to Submission Processing, Receipt & Control for payment processing. If a tax return is included with the correspondence, forward the return to Submission Processing. Payments must be processed within one (1) business day of receipt.

# Request for Release of Lien

5.19.12.7.5.4 (04-16-2024) Request for Release of Lien An external request for a lien release can come to CLO via the Aspect Toll Free system, mail, or fax. Generally the requests are from the taxpayer or their representative, but occasionally a request is received from a third party. Reminder: Follow disclosure guidelines prior to giving any information. See IRM 21.1.3.2, General Disclosure Guidelines. Upon receipt of a release request, research ALS to determine if the lien has been released. If the lien has been released, advise the requester of the status. If the lien has not been released, research IDRS. Determine the status of the account on IDRS. For accounts in status 26, 71, or 72, follow referral instructions in IRM 5.19.12.7.5.2, Request for Payoff. Refer accounts with a "Z" freeze to Criminal Investigations (CI). Do not tell the taxpayer you are referring the case to CI. For accounts not meeting referral criteria, work the release request to the extent authorized. Review IDRS to determine if the NFTL modules are satisfied. Check status 12 modules for an "I" freeze, which could mean there is additional interest due and the module is not truly satisfied. Be alert for partial release situations. Be alert for assessments split to different MFTs or modules moved to NMF. Reminder: The same tax liability is only collected once. So, if a joint MFT 30 module is mirrored into two MFT 31 modules, the full payment of one person's MFT 31 module satisfies the same module of the other person. Based on the information available, take action according to the table below. If... Then... The NFTL modules are satisfied and the lien release has already been issued Advise the taxpayer of the release and that a copy would have been sent to the last known address at the time of release. If more than 30 days have passed since the release date, take the following steps. Verify the address for the taxpayer. As necessary, follow procedures for updating the address in IDRS. See IRM 21.1.3.20, Oral Statement Authority. Provide the taxpayer with a copy of the release or, in the case of ELF filings, send a facsimile. The NFTL modules are satisfied, but the lien release has not been issued Take the following steps: Ensure that the recording information for the NFTL is in ALS. If the recording information is missing, use the best research method available to locate the recording data. Review ALS and IDRS to determine any other reason the lien release may not have been issued (e.g., reversed payment, freeze code). Verify the taxpayer's address and update IDRS if necessary. Input the lien release on ALS and explain to the taxpayer that a copy of the release will be mailed. The payment to satisfy the NFTL modules is pending on IDRS Take the following steps: Advise the taxpayer that the lien will be released within 30 days of the payment posting. If the taxpayer requests an expedited release, ask for verification that the payment was made by a qualifying payment type (e.g., certified check) or has cleared the financial institution (e.g., canceled check). See IRM 5.12.3.3.1.1, Liability Satisfied by Payment. Upon satisfactory proof, input the lien release on ALS and explain to the taxpayer that a copy of the release will be mailed. The NFTL modules are not satisfied but there are credit balances on IDRS from other tax periods that will satisfy the NFTL modules Take the following steps: With managerial approval, transfer the credit to the appropriate module by inputting the appropriate transaction to IDRS, if authorized, or completing Form 2424. See IRM 21.5.8, Credit Transfers. Input the lien release on ALS and explain to the taxpayer that a copy of the release will be mailed. The NFTL modules are not satisfied, and there are no credit balances on IDRS Advise the taxpayer and proceed to the Payoff Letter Process. See IRM 5.19.12.7.5.2, Request for Payoff. IDRS shows the assessments for the NFTL modules were abated but an unpaid NFTL filing fee remains Advise the taxpayer of the outstanding balance to pay and the option to submit an abatement request to the Advisory Office where they reside. The lien has self-released Follow the procedures in IRM 5.19.12.2.7.4, Self-Releasing Liens. The case involves complex issues or requires a determination not delegated to the employee Consult the FORT and/or refer the request to Advisory for review and action. The lien release process is described in IRM 5.19.12.2.7, Lien Release. If the taxpayer states they need verification of the release immediately, an ALS facsimile of the NFTL showing the released status may be sent to them. Advise the taxpayer that a copy of the actual certificate of release will be systemically mailed to them later. Releases of satisfied liens must be input to ALS within five (5) business days after receipt of the request. Time spent releasing liens should be charged using: OFP 700-69000, if the request is received by phone. Do not take a closure count. OFP 810-69080, if a written request is received. Do report a closure count.

# Missing Payment Inquiries

5.19.12.7.5.4.1 (09-09-2021) Missing Payment Inquiries Occasionally, CLO receives a lien release request in which the taxpayer states the liability was fully paid but the payment is not showing on IDRS. Generally, CLO refers these inquiries for further research and resolution. Prior to making the referral, request a copy of the canceled check (front and back) or other proof of payment. Refer the inquiry to the appropriate function following the table below. Status Proof of Payment Provided Proof of Payment NOT Provided 22, 24 Complete Form 4442 and fax with missing payment information to the appropriate ACS Support Liaison listed in SERP (http://serp.enterprise.irs.gov/databases/who-where.dr/acs-support-status-22-tas-liaisons.html). Complete Form 4442 and fax to the appropriate ACS Support Liaison listed in SERP. Advise the taxpayer to send proof of payment to ACS Support Liaison. 26 Advise the taxpayer to contact the assigned revenue officer (http://serp.enterprise.irs.gov/cgi-bin/ROZIP_Lookup.cgi). Advise the taxpayer to contact the assigned revenue officer. Other Complete Form 4442 and fax with missing payment information to appropriate CSCO office listed in SERP (http://serp.enterprise.irs.gov/databases/who-where.dr/form-4442-referral-fax-numbers.html?site=All#results). Complete Form 4442 and fax to the appropriate CSCO office listed in SERP. Advise the taxpayer to send proof of payment to CSCO site. The referred office is responsible for researching the situation, inputting any IDRS command codes, and, when needed, requesting the lien release.

# Other Types of Requests

5.19.12.7.5.5 (09-09-2021) Other Types of Requests CLO responds to requests for lien payoffs, releases of lien, and other NFTL issues. CLO also handles all general lien-related inquiries before referring the more technical or legal questions to the FORT, Advisory, or other appropriate office. Inquiries can include, but are not limited to, the following topics: Certificate of Discharge - A lien can only be "released" when it is satisfied (e.g., paid in full) or it is no longer enforceable. At times, a taxpayer may need to sell or transfer a specific piece of property but cannot satisfy the lien. The taxpayer may request for the property to be "discharged" from the lien so that it may be transferred free from the effects of the lien. If the conditions for discharge are met (i.e., usually the IRS receives the value of the Government's interest in the property) a certificate of discharge may be issued. See IRM 5.12.10.3, Discharge of Property, for more details. Certificate of Non-Attachment - An NFTL identifies the taxpayer by name, address and redacted TIN. However, at times the lien may mistakenly be associated with a third party or a third party's property. Most often this occurs when the taxpayer and third party have a similar name. The IRS may, upon receipt of documented evidence, issue a certificate that the third party may use as proof that they are not the person, and theirs is not the property, that is subject to the lien. See IRM 5.12.10.13, Certificate of Non-Attachment, for more details. Certificate of Subordination - The filing of the NFTL establishes the priority of the lien against certain creditors. Subordination allows another creditor to move ahead of the IRS lien in priority in order to benefit the Government. Most often this is requested when a taxpayer is getting a second mortgage or is refinancing an existing loan. The IRS can consider subordinating its lien to the new financing if the Government receives the value of its interest or the financing will ultimately increase the collection of the tax debt. See IRM 5.12.10.6, Subordination of Lien, for more details. Withdrawal of NFTL - A lien cannot be released until the tax debt is satisfied or the CSED passes. A withdrawal removes the NFTL that was filed but the tax debt is still owed and the taxpayer is still liable for it. An NFTL may be withdrawn when certain conditions are met, including the NFTL was filed improperly or the withdrawal will facilitate collection. See IRM 5.12.9.3, Conditions for NFTL Withdrawal, for more details. An NFTL may also be withdrawn after the lien has been released. See IRM 5.19.12.2.8, NFTL Withdrawal. When handling inquiries for lien-related certificates, ensure the taxpayer understands that the submission of a request does not reflect approval of their request. The determinations for discharge, subordination, non-attachments, and withdrawals before lien release are generally made by Advisory. CLO has no impact on those determinations. The table below shows common inquiries involving liens and the most likely resolution for them. Note: Most applications for lien certificates are now handled through the Advisory Consolidated Receipt (ACR) site. See Pub 4235, Collection Advisory Offices Contact Information, for details. Inquiry Response Taxpayer wants to SELL or transfer ownership of their property; however, the proceeds from the sale will not satisfy the lien. Tell the taxpayer to contact the ACR to apply for a Certificate of Discharge of Property from a Federal Tax Lien. Refer the taxpayer to Publication 783, Instructions on how to apply for a Certificate of Discharge of Property From Federal Tax Lien. Advise the taxpayer to read this publication BEFORE contacting Advisory Taxpayer wants to REFINANCE their mortgage to lower the interest rate; however they cannot borrow enough to satisfy the lien. Tell the taxpayer to contact the ACR to apply for a Certificate of Subordination of Federal Tax Lien Refer the taxpayer to Publication 784, How to Prepare an Application for a Certificate of Subordination of Federal Tax Lien. Advise the caller to read the publication BEFORE contacting Advisory. Taxpayer wants to SELL property or REFINANCE a mortgage and should be able to satisfy the lien from the proceeds. Secure information from the taxpayer to provide a payoff for the NFTL. See IRM 5.19.12.7.5.2, Request for Payoff. Advise the taxpayer that if the proceeds will not be sufficient for the payoff, they should apply for a discharge or subordination, as applicable, and inform them of that process, as necessary. Caller says they are harmed by a Notice of Federal Tax Lien on a delinquent taxpayer with the same or similar name. Tell the caller to contact the ACR to apply for a Certificate of Nonattachment of Federal Tax Lien. Refer the caller to Publication 1024, How to Prepare an Application for a Certificate of Nonattachment of Federal Tax Lien. Instruct the caller to read the publication BEFORE contacting Advisory. Taxpayer wants to get the lien REMOVED as it is affecting their employment. Tell the taxpayer to contact the ACR to apply for a Withdrawal of Notice of Federal Tax Lien. Refer the taxpayer to Form 12277, Application for Withdrawal of Filed Form 668(Y), Notice of Federal Tax Lien. . Caller has applied for [any of the above] and has tried to contact Advisory several times, but has had no response. Apologize for the delay. Ask how long ago the application was made. Check ICS to look up the taxpayer's account. Check the history to determine the status Advise the taxpayer of the status and of any questions or additional information needed, as noted in the history. Verify the taxpayer has the correct contact information for the Advisory office assigned. If the taxpayer indicates it has been more than 60 days since the application was submitted to the correct office, refer the issue to the Taxpayer Advocate Services using Form 911, Request for Taxpayer Advocate Service Assistance (And Application for Taxpayer Assistance order). Input a history to IDRS ENMOD for the taxpayer, stating "911 to TAS." Input a history to ICS of the actions taken. Taxpayer has questions about the NFTL showing on their credit report. Inform the taxpayer that the IRS does not report NFTL filings or lien releases to any credit reporting agency/credit bureau. Advise the taxpayer to contact the credit reporting agency Generally, credit agencies have stopped including NFTLs on credit reports, but if one is shown, the length of time it appears there is determined by that agency. Taxpayer wants to know any of the following: What is the lien for? What does the lien attach to? Why were they not told that an NFTL would be filed? Advise the taxpayer that answers to common questions regarding federal tax liens can be found in Publication 594, The IRS Collection Process, or by searching "liens" on the IRS website (www.IRS.gov). Inform the taxpayer to contact their local Advisory Office if they have any additional questions regarding liens after reading the publication or reviewing the website. If the taxpayer has specific questions regarding their account, refer them to the assigned function/employee or, if not assigned, to the toll free line at 1-800-829-1040. Taxpayer requests abatement of the NFTL filing fee (TC 360) Advise the taxpayer that filing fees are generally only abated if the taxpayer did not cause the situation leading to the assessments or filing or the NFTL was filed due to an IRS error. See IRM 5.12.3.5.6, NFTL Fee Abatements, for additional information. If the taxpayer feels one of those factors was present, advise the taxpayer to send a letter to their local Advisory office providing their name, TIN, NFTL information, and reason for requesting the abatement. Caller wants to know why you cannot answer their questions. Tell the taxpayer that questions that are technical in nature are handled by the Advisory office. Advise the taxpayer to contact their local Advisory office. As needed, send Form 4442 to Advisory giving a detailed description of the taxpayer's questions. Caller has questions about the passport certification for seriously delinquent tax debt Refer the caller to the Philadelphia call site per IRM 5.19.25.12, Taxpayer Contacts. Domestic call 855-519-4965 International call 267-941-1004 CLO may receive other types of inquiries related to liens or payment issues (e.g., the taxpayer has questions about a bank foreclosure, an insurance company issued a two-party check naming both the taxpayer and the IRS, etc.). Questions about lien processes beyond CLO's responsibilities should be referred to Advisory. When referring a caller to a publication, form, or other document, ask questions to determine the best way for the caller to obtain the document and take action accordingly. The document can be downloaded by the caller from the IRS website (www.IRS.gov). The document can be mailed or faxed to the caller. If circumstances require, necessary information from the document can be provided verbally to the caller. Reminder: Instructional videos are available on www.IRS.gov to assist the caller in the completion of lien certificate applications. The caller can access these videos, and other information about liens, on the website by typing "liens" in the search box and following the links. When referring a caller to Advisory, determine the best way for the caller to obtain the contact information shown in Publication 4235, Collection Advisory Offices Contact Information, and take action accordingly. If the request is written, use the Correspondex Letter 3645C, Case Processing Liens / Centralized Lien Operation. Do not attempt to answer technical questions about processes not assigned to CLO (e.g., discharges, subordinations). Do not give any opinion on the taxpayer's chances of securing approval of their request.

# Field Office Resource Team (FORT)

5.19.12.8 (04-28-2015) Field Office Resource Team (FORT) The FORT is CLO's technical resource for lien law, ALS coordination, and elevated recording office issues. The FORT is available to answer CLO's questions as they relate to NFTLs, releases, and withdrawals. The ALS coordinator(s) maintains the ALS system and is available to answer questions and update maintenance items on ALS as well as issue secondary passwords. Different types of referrals will come into the FORT, usually from the CLO teams, but they may also come directly from the recording office, an employee in the field, the Government Liaison, or other internal and external sources. Referrals may involve, but are not limited to, the following: Recording office fee changes Zip code updates Billing issues that have not been resolved Technical questions on how to resolve a request Work stoppages due to recording office rejections Suggestions for systemic or procedural improvements The FORT works with Headquarters staff, as necessary, to address issues beyond their control. The FORT is also the central point for Taxpayer Advocate Service referrals.

# Recording Fee Issues

5.19.12.8.1 (04-28-2015) Recording Fee Issues CLO receives questions regarding recording fee issues and work stoppages due to missing payment, cover sheets, and confusion on documents. The CLO teams work with the recording offices to clarify and correct any problems that may come up. When the recording office and the teams cannot reach agreement, the issue is referred to the FORT. Referrals of recording office issues should be sent to the FORT by email or on a Technical Referral form. The referral will become the informational copy and all steps and history should be placed onto the referral. Once the FORT takes ownership of the issue, it sends an informational copy of the issue to the Government Liaison (GL), if appropriate. The FORT researches the issue and attempts to resolve. As needed, the FORT works with appropriate parties, which may include the CLO team, recording office, Finance, GL, Headquarters or Counsel. When the FORT resolves the issue, the resolution is documented and all appropriate parties are notified. If the FORT cannot resolve the issue, it must work with Finance, GL, Counsel or other appropriate parties to reach resolution. The FORT should send an informational copy of the issue to Headquarters. The FORT coordinates implementation of the resolution by working with appropriate parties. If the FORT team member contacts the recording office, a history is placed on the referral. This referral form will be updated by all individuals who take an action on the issue. If the FORT brings in Finance, Government Liaison, Headquarters or Counsel, the referral form is sent as an historical document for updating. The FORT maintains a copy of the closed referral documents for one year. These types of issues can be used for analysis and educational purposes. Issues sent to the FORT for resolution are considered a work stoppage. The FORT must make contact with the recording office within two (2) business days after receipt. Resolution may take longer. Interim guidance must be given to the referring lien team within three (3) business days. Resolution should be achieved as soon as possible. Document the ALS voucher history as well as the file copy of the BSV if a work stoppage occurs.

# Filing Estate Tax Lien Documents

5.19.12.8.2 (06-03-2020) Filing Estate Tax Lien Documents Estate tax liens are filed on Form 668-H or Form 668-J and released using Form 668-I or Form 668-K. Estate tax lien documents are not created on or otherwise loaded to ALS. They are manually prepared by the Advisory Estate Tax Group. Note: Notices of estate tax lien are different from NFTLs filed against the estate. Forms 668-H and 668-J are for unique liens for special estate tax elections provided by the IRC. The estate can still be liable for regular assessments made under IRC 6321. These would be shown on Form 668(Y)(c). Requests for regular NFTLs should be processed according to standard procedures. See IRM 5.5.7.11, Liens on Estate Tax Liabilities, for further details. Estate tax lien documents are processed through the FORT. Any Forms 668-H, 668-J, 668-I, or 668-K received by the CLO teams (through email or regular mail) must be forwarded to the FORT. Estate tax lien documents may be prepared in PDF format and should be submitted to CLO with a Form 3210. All estate tax lien documents must be tracked. The tracking includes the following information: Name of estate TIN, using a "V" ( or occasionally "W" ) definer Date received in CLO Originator (requester) of the Form 668-H or 668-J Recording office for filing Date sent to the recording office Voucher number of the billing support voucher (BSV) used to forward to the recording office Date recording information received back in CLO Date document was sent back to the originator Whether the Form 3210 included a request for a TC 360 and TC 582 input Note: All Forms 668-J should have a TC 360 and TC 582 input. Forms 668-H only have a TC 360 and TC 582 input upon request by Advisory. Acknowledge receipt of the lien document by returning the Form 3210 to the originator via e-Fax. If the lien document is received electronically, the FORT RO must sign the lien document for filing. Generate a separate voucher for the estate tax lien document using the ALS voucher program. Determine the amount of the recording fee charged by the recording office (to file and to release) by checking the ALS COURT screens. Due to changing fees and other special requirements, if there is no indication that it was done recently, verify the amount by calling the recording office. Document the voucher history with the name of the person who verified the amount. Input the recording fee for the notice of estate tax lien on the voucher program for use when filing the lien document. Note the entire recording fee for subsequent posting of the TC 360. Note the release fee for when the release of the estate tax lien is filed. There are occasions when the recording office may require special handling for estate tax lien documents. Refer to any special requirements the recording office may have and ensure these requirements are listed on the ALS MAINTXC screen. Once the voucher is built, send the estate tax lien document(s) to the recording office via regular mail. When the notice of estate tax lien has been recorded and received back from the recording office, input the TC 360 and TC 582 as applicable. Input a TC 360 and TC 582 for ALL Forms 668-J filed. Input a TC 360 and TC 582 for Forms 668-H ONLY when requested by the Advisor, usually on the Form 3210. These inputs will be on MFT 52 for module 000000. Note: The transaction date of the TC 582 should be the date the notice of lien was mailed to the recording office. The TC 360 should be the date the notice of lien was recorded. When the recorded document is returned, close out the tracking of the document by inputting the recording information and mail the recorded document to the originator using a Form 3210. Update the voucher history on ALS. Review the tracking document monthly to ensure the notices of estate tax lien submitted to the recording office more than 90 days prior have been recorded and returned. If the lien document was not recorded in this time frame, review the voucher program to determine whether the estate tax lien document was rejected by the recording office. If the recording office rejected the lien document and it was returned to CLO, update the tracking document to show the latest date the lien document was mailed to the recorder. Work the reject following standard procedures. If the lien document was never rejected, contact the recording office to determine the status of the filing. Notify the originator of the findings. Store the tracking information for one year from when the recorded document was returned to the originator. Process estate tax lien releases in a similar manner as described above. Review IDRS for a posted TC 582 and, as necessary, input a TC 583 for ALL Form 668-J releases and for Form 668-H releases as requested by the Advisor. Note: The transaction date of the TC 583 should be the date the release was mailed to the recording office. Retain Forms 3210 and applicable documents relative to estate tax liens for a minimum of 18 months. If a request for payoff or release of lien is received on an estate tax lien do not complete the request. Refer the request to Advisory's Estate Tax Group.

# ALS Inventory Listings

5.19.12.9 (04-28-2015) ALS Inventory Listings ALS produces several listings for CLO's review to ensure actions are taken on lien documents in ALS that could not be achieved systemically. Some of the listings pertain to problems in the systemic posting of information from ALS to Master File, including the following: TC 582, which indicates an NFTL was filed TC 360, which reflects the cost of filing the NFTL plus the future certificate of release TC 971 AC 252, which indicates the CDP notice was issued Note: ALS and Master File exchange information on a weekly basis to upload the transaction codes for NFTLs processed through ALS. Additionally, ALS receives information from Master File, including notification when modules are satisfied. Some of the listings pertain to issues in the interface between ALS and other systems, including the Integrated Collection System (ICS) and Automated Collection System (ACS).

# TC 360 Rejects

5.19.12.9.1 (09-09-2021) TC 360 Rejects When an NFTL is filed, the taxpayer's account is assessed a TC 360 for the amount the recording office charges for filing and releasing the lien. The TC 360 posts to the NFTL module with the oldest assessment date. Note: ALS does not send a TC 360 to Non-Master File (NMF) accounts. TC 360 must be manually entered on NFTLs for NMF modules. These NFTLs contain a TIN suffix of "N" . During the upload process if there is a mismatch between ALS and Master File of information for the module the TC 360 will be rejected. The notification of the rejection will be listed on the TC 360 reject listing. Two listings are generated to the reports section of the print queue. The listing entitled "17.360_errXX.mmdd" lists accounts on Master File. The listing entitled "NMF_360_17.mmdd" lists accounts on Non-Master File. The listings are dated and identify the cause for the rejection of the TC 360, the TIN, name control, MFT, tax period and SBSE area. Review the NFTL on ALS and match the entity and tax module information with IDRS. If the rejection was caused by a... Then... Name control mismatch Review the entity on IDRS to determine the extent of the problem. If the name was in error, request an amended NFTL. See IRM 5.19.12.2.3, Resolving Errors on NFTLs. If only the name control is incorrect, edit the name control on ALS and manually assess the TC 360. MFT mismatch Create a Not To Be Filed lien record on ALS and manually assess the TC 360. See IRM 5.19.12.2.3.3, Not To Be Filed Lien Record. Tax period mismatch Create an amended NFTL on ALS. See IRM 5.19.12.2.3, Resolving Errors on NFTLs. Note: Do not input a TC 360 on accounts that are in IDRS status 12. When resolving an unpostable TC 360, use the unpostable date for input. If the unpostable date is not available, use the date of the report. Generally, when the TC 360 is rejected the TC 582 will also be rejected. When working the TC 360 listing, address the unpostable TC 582, if present on IDRS. NMF requires coordination with the Non-Master File team in Submission Processing in order to ensure the TC 360 is posted to the account. This report should be worked within five (5) business days after the date of receipt. Report time under OFP 810–69130.

# TC 971 SIA Error Report

5.19.12.9.2 (06-03-2020) TC 971 SIA Error Report A TC 971 AC 252 is posted to Master File to indicate the CDP notice (Letter 3172) was issued for the NFTL filing. For NFTLs processed through ALS, the TC 971 AC 252 is triggered by the printing of the NFTL and the code is posted to each module on the NFTL. During the upload process if there is a mismatch between ALS and Master File of information for the module, the TC 971 will reject. The notification of the rejection will be listed on the TC 971 Standardized IDRS Access (SIA) error report. Note: See the table in IRM 5.19.12.9.1, TC 360 Rejects, for rejection causes. The listings are dated and identify the cause for the rejection. Generally, when the TC 971 AC 252 is rejected, the TC 360 will also reject and the TC 582 will go unpostable. Follow the procedures in the table in IRM 5.19.12.9.1, TC 360 Rejects, to correct the cause for the rejection. When an amended NFTL is filed to correct a tax period, a new CDP notice and TC 971 AC 252 will be systemically generated. For all other corrective actions, manually input the TC 971 AC 252 to each module on the NFTL. Note: When resolving unpostable TC 971 AC 252, use the unpostable date for input. If the unpostable date is not available, use the date of the report. This report should be worked within five (5) business days after the date of receipt. Report time under OFP 810-69130.

# MODSAT - Satisfied Module Rejection Report

5.19.12.9.3 (04-28-2015) MODSAT - Satisfied Module Rejection Report Each week, Master File downloads to ALS a data extraction of the modules that went to status 12 and had an open NFTL indicator (TC 582). Through the MODSAT program, those modules are marked as satisfied on ALS. MODSAT also generates a listing of those modules from the extract that could not systemically be marked as satisfied. Note: A mirrored report NMF SATMOD Reject Listing is produced from a match done between the automated Non-Master File (ANMF) and ALS. Both reports are worked the same way. The rejection of the satisfied indicator by ALS may be the result of not finding the corresponding module on ALS due to one or more of the following conditions: TIN does not match with ALS TIN TIN did match but MFT and/or tax period did not match A manual NFTL was filed and not loaded to ALS A module on a NTBFL was satisfied and the module on the original NFTL must be marked satisfied The rejection may also be the result of the module having a condition that limits the systemic release such as a restricted interest/penalty freeze or bad check indicator. MODSAT produces two different reports, both which generate on Tuesday and appear in the Area 27 print queue on Wednesday. SAT_REJ for normal workable rejects SAT_NF for entity not found rejects To resolve the items on the listings there are two functions that can be used. SAT is used to satisfy the module and will also close the item from the report. RSAT is used to close the module from the report when the module cannot be found on ALS. Using the tax module and TIN information from the reject listing, research ALS and IDRS, if necessary, to identify the module on an NFTL in ALS. Take appropriate action according to the table below. If... Then use... The module is found on ALS and the TIN is correct SAT to input the satisfaction indicator for the module on ALS. The module and TIN cannot be located on an NFTL on ALS RSAT with closing code "N" to indicate there no action is needed and remove the case from the report. The module is found on ALS but the TIN is incorrect SAT to input the satisfaction indicator for the module on ALS and RSAT with closing code "S" to close the module from the listing. Refer to the ALS User Guide, Chapter 10, Releases, Revocations & Withdrawals, for direction on how to input SAT and RSAT. Using SAT will cause the satisfaction indicator for the module on ALS and update the RSAT screen. When the lien module is located and the module is satisfied, DO NOT USE THE RSAT SCREEN TO CLOSE THE MODULE FROM THE LISTING. When searching RSAT by the TIN, there can be multiple modules found. Be sure to address the correct module and do not edit closed modules. Look for the module that has no closing entry. For SAT to properly generate the closing indicator on ALS, the module information entered to SAT must match that shown on the NFTL. Occasionally, differences in the tax period formats used by Master File and ALS may cause a discrepancy (see example below). When an input to SAT does not take, print a facsimile of the NFTL to verify the tax period ending date and re-input the information to SAT as needed. Note: A tax period is input to ALS showing an ending date of 12/13/2012. Because Master File uses the format "YYYYMM" for its ending dates, the TC 582 posts on Master File to the module ending 201212. When the module is satisfied, Master File information is downloaded to ALS and the period ending date is converted by ALS to its "MM/DD/YYYY" format as the 12/31/2012. Since this tax period ending date does not match the one input to ALS for the NFTL, the satisfied module indicator rejects. This report should be worked within five (5) business days after the receipt date. Time working this report is reported under OFP 810-69130.

# ACS/ICS Rejects

5.19.12.9.4 (09-09-2021) ACS/ICS Rejects The ACS Reject Report is generated each time an ACS/ICS data is loaded to ALS and shows NFTL requests that are rejected, generally due to invalid data and form type, incorrect zip code, or recording office not found in ALS. To access the report from the print spool, select "ACS.mmdd" then select and print "acs.rejects." CLO actions on these listings are limited to cases rejected for Unknown zip code or Court Not Found. Verify that the zip code shown on the listing is correct for the address using the Zip Code Look Up on the USPS web site (https://zip4.usps.com/zip4/welcome.jsp). If the zip code is correct on the request, notify the ALS coordinator to add the Zip Code/Court to ALS. If the zip code is incorrect on the request, take the necessary actions to correct the request. If the reject was for another reason, take action using the table below. If the rejected NFTL was input through... Then... ACS Notify ACS support in the Cincinnati Campus about the reject ICS Take no additional action. The requester will receive a notice systemically from ICS. Listings requiring CLO actions should be monitored until all actions are completed. Managerial review should be completed on the original listings to ensure correct closing actions are completed. Systemic rejects must be resolved by CLO within five (5) business days after the receipt date. Prompt processing allows timely filing of the NFTL. Report time under OFP 810–69130.

# ICS POA Reject

5.19.12.9.4.1 (06-03-2020) ICS POA Reject ICS POA rejects are associated with NFTLs systemically loaded to ALS through ICS. They are caused when the POA information is incomplete or contains invalid city, state, or zip code information. To access the report from the print spool select "ACS.mmdd" then select and print "poa_rejects." Research IDRS to obtain the correct information to complete the POA input. Using ALS NOTADD, access the SLID shown on the listing and input the correct POA information. Note: For NFTLs filed in ELF recording offices, POA information cannot be input on ALS until the ELF filings have been approved. See IRM 5.19.12.2.1.2, Secondary Taxpayer/Co-Obligor and Power of Attorney. Listings requiring CLO actions should be monitored until all actions are completed. The listings must be resolved within five (5) business days after the receipt date. Report time under OFP 810–69130.

# Potential Lost NFTLs

5.19.12.9.5 (06-03-2020) Potential Lost NFTLs ALS generates the Potential Lost Lien Report (PLL) on the 5th day of each month. The report lists NFTLs that have been created but no recordation date has been entered into the COURT screen on ALS. This report must be worked monthly. Recording information is used by the recording office to associate any subsequent documents with the original NFTL. ALS prevents subsequent action from being taken on an NFTL without the recording information input. Example: An NFTL is filed in XYZ county on page 435 of book 1289. The IRS subsequently wants to withdraw the NFTL. For the recording office to show the withdrawal of the appropriate NFTL, they must reference the recording information of the original NFTL. Several things can happen to cause an NFTL to appear on the PLL. Recording offices can take days, weeks and, at times, months to record the NFTL and return it to the IRS. If the recorded NFTL is not timely returned, recording information cannot be input to ALS. In certain situations, a revenue officer may manually prepare an NFTL and hand carry it to the recording office. Revenue officers are required to send the recording information to CLO so ALS can be updated with the information. Sometimes, the recording information is not sent to CLO for input to ALS. Note: A SLID beginning with 27xxxxxxx that has not appeared on a voucher may indicate that it was hand carried by a revenue officer. On occasion, recording information for an NFTL may be input incorrectly under the wrong SLID, which causes the NFTL to appear as not being recorded. The PLL shows NFTLs that were prepared at least 90 days prior to the listing. This time frame is used to allow for the recording process to be completed. NFTLs that require a subsequent action within 90 days of the preparation date must be worked immediately. Do not wait for the NFTL to show up on the PLL. Example: Advisory approves and requests a withdrawal on an NFTL that was prepared 2 weeks ago. The NFTL has not come back from the recording office. Research must be done to secure the recording information so the withdrawal request can be completed. Some issues that cause a lost condition can be prevented. When working the 668Z Listing, immediate research and corrective action must be taken. Do not wait until the NFTL has reached the PLL to complete the research. See IRM 5.19.12.3.3.2, Resolving the 668Z Listing. Take the following actions to secure recording information when working the PLL. Ensure any CRD from the recording office has been input to ALS by checking for any batches of recording data received and awaiting input. Verify whether the NFTL was rejected by the recording office and has been re-sent, causing a delay in the recordation. Review the ALS and voucher history to determine if the NFTL was pulled from the batch for some reason. Check to see if the batch was returned from the recording office for corrections and, if so, whether enough time has passed for the recording information to have been received. Note: Review of the voucher program will show if all other NFTLs on the voucher received recording information. This information should always be verified at the time recording information is entered. See IRM 5.19.12.4.1.1, Court Recording Information. Research the status of the NFTL using an available search engine such as Accurint, Netronline, or the local recording office website. If the NFTL was filed by Field Collection, contact the RO and ask if they have the recording information. When all the above actions have been completed and questions regarding the recording data remain, contact the recording office, explain the situation, and request the information. If the recording office will not give the information, refer the situation to the FORT for resolution. When the CRD is secured for the NFTL, input it to ALS. If the lien is released, print the release and add it to the next voucher for the recording office. If no voucher is generated the next print day, generate one for the recording office. For information on input of CRD for any ELF recording offices, see IRM 5.19.12.12.1, Manual Input of Recording Information to ELF Offices. When the CRD cannot be determined for the NFTL, check IDRS for the status of the account and the modules. It may be appropriate to remove the NFTL from ALS, which will place the NFTL into "lost lien" status. Take the necessary actions as shown in the table below. Caution: All available methods of research must be utilized before removing the NFTL from ALS. Once an NFTL is removed, a release of the lien will not be generated. If IDRS shows... And the modules are in Status.. Then... The NFTL modules have no balance due 12 Remove the NFTL as a lost lien All the NFTL modules have a balance due Any except 72 Print the NFTL and add to the next voucher for the recording office. If no voucher is generated on the next print day, generate one for the recording office. All the NFTL modules have a balance due 72 Remove the NFTL from ALS as lost and secure email the PLL Notification Memo (Exhibit 5.19.12-3) to the function assigned the case to determine if a replacement NFTL request is needed. Only some of the NFTL modules have a balance due Any except 26, 71, or 72 Remove the NFTL from ALS as a lost lien and create a new NFTL for the balance due modules using available information. Only some of the NFTL modules have a balance due 26, 71, or 72 Remove the NFTL from ALS as lost and secure email the PLL Notification Memo (Exhibit 5.19.12-3) to the function assigned the case to determine if a replacement NFTL request is needed. Reminder: New or replacement NFTLs should not include modules that have no balance due. Do not file a replacement NFTL if a certificate of release will immediately follow. Status Refer to... 26 RO 71 Centralized Offer in Compromise 72 TC 520 cc 60-67, 81, or 83-89 Centralized Insolvency Operation 72 TC 520 cc 70-75 or 80 Advisory office for the applicable state For any NFTLs marked as "lost" on ALS and not being re-sent, reverse the original TC 360 and input a TC 583 DC 4 on IDRS. If a new NFTL is subsequently created, a new TC 360 and 582 will be generated. If a PLL was worked and an NFTL was re-sent for recordation, due to the timing it may show up on the following month's PLL. This is considered a roll-over and will not be overage. ALWAYS input a history on the Potential Lost Lien Report and ALS, if applicable, stating "Lost Lien worked" and what action was taken. For example, a history could state: Lost lien research was completed using (Accurint, Netronline, and/or recording office web page) on (give date) closing lien from lost lien report. Receipts will be counted for each team for the daily inventory. A closure occurs when the Court Recording Data is entered or the NFTL status is changed to "lost" in ALS. The FORT is generally responsible for printing the PLL, distributing it to the applicable teams to work, and monitoring the overall counts. The CLO teams are responsible for resolving the NFTLs on the PLL, monitoring their inventory, and elevating issues of chronically-slow recording offices. Report time working PLL issues under OFP 810–69130.

# GUF Unpostables

5.19.12.10 (04-28-2015) GUF Unpostables The Generalized Unpostable Framework (GUF) provides listings of the unpostable TC 582 cases. These unpostable listings are located on Control D, GUF 5547 file. The FORT accesses the Control D GUF files weekly to print, assign and distribute to the CLO teams. The teams are responsible for resolving the unpostables. Common unpostable resolutions are found in Exhibit 5.19.12-1, Job Aid for Unpostable TC 582. The resolutions shown may not fit every situation; each case resolution is based on the individual situation. In most cases, the TC 582 should be re-input using the date of the unpostable TC 582, which should be approximately seven (7) calendar days within the creation date of the NFTL. If there is no unpostable date, use the date the NFTL was created. If the TC 582 continues to unpost (i.e., does not post after two inputs), DO NOT keep re-inputting the TC 582. See the team manager or lead TE for guidance. If requesting an amended NFTL to correct the unpostable condition review ALS to ensure court recording data is present. If CRD is not present, use the best research methods available to obtain recording information. See IRM 5.19.12.2.3, Resolving Errors on NFTLs. Be sure to close the IDRS control base after IDRS actions are completed. When research shows that an account has not been established (prompt assessments), close the IDRS control base and notify the revenue officer that the NFTL filed indicator on IDRS could not post. The revenue officer is responsible for monitoring IDRS for establishment of the account and ensuring that the TC 582 and TC 360 are posted. See IRM 5.12.7.12.2, Lien Filed Indicator (LFI). When the account is on NMF, contact the Non-Master File team in Submission Processing to ensure the TC 582 is posted. While researching, if it is identified the TC 360 and 971 AC 252 also did not post, research the unpostable code in Document 6209 and resolve the unpostable condition appropriately. Document actions taken on the Unpostable Excel sheet. Unpostables should be closed within five (5) business days after receipt of the listing. Report time closing unpostables under OFP 810-69130.

# ALS Maintenance

5.19.12.11 (04-28-2015) ALS Maintenance Maintenance of the ALS database is generally the responsibility of the ALS functional coordinator. All functions of the system must be monitored by management to ensure all NFTLs and related documents processed through ALS are produced timely and correctly. All available system logs must be monitored and steps taken to notify management if irregularities exist so that corrective actions can be taken. Logs are located in the ALS Lien Application Menu and the Print Lien Document Queue Menu under ALS LOG FILES. Note: The reports and logs generated on the Automated Lien System are specified in the ALS User Guide, Chapter 15, ALS Logs and Reports. IRM 5.19.12.11.1 through IRM 5.19.12.11.6 address common maintenance issues addressed by the ALS coordinator. For details on ALS tables, logs, and reports see the ALS User Guide.

# Menus

5.19.12.11.1 (04-28-2015) Menus A menu is a set of options used to move from place to place within an automated application. Each option will either execute a program or take the user to another menu. Generally, menus are standardized based on the position type and permission level of the employee. Menus can be developed by the ALS coordinators as needed. Refer to the ALS User Guide, Chapter 15, ALS Coordinator Guide, for information on how to create menus. Reminder: Literal commands can be entered from the menu prompt to go directly to a specific function. See the ALS User Guide for details.

# Employee Access and Maintenance

5.19.12.11.2 (09-09-2021) Employee Access and Maintenance Each employee using ALS has permissions specific to their job responsibilities. For a listing of the normal permissions allowed for each position type refer to the exhibit in IRM 5.12.1-1, ALS Permissions Chart. Employees requesting access to ALS must complete an BEARS request. Employees will not be established on ALS if they do not complete the BEARS request. See the ALS User Guide, Chapter 2, Getting Started, for details on requesting ALS access. Employees needing more than general research capabilities on ALS must request a secondary password in ALS to gain the additional functionality. This secondary password is requested with the BEARS requests, but is approved by the ALS Coordinator. The ALS Coordinator is notified by email when there are requests awaiting their approval and approves the BEARS request as the system administrator. When the requests are not complete with all necessary information, the request is rejected by the ALS Coordinator and the additional information requested. Generally, the permissions established for the employee by their position type should not be changed. If a variation is justified, modification of the existing permissions (or the deletion of permissions, as necessary) is done through the BEARS by the ALS Coordinator. Exception: CLO employees can request change to established permissions through an email to the ALS Coordinator in FORT. When an employee uses a pseudonym, the employee must identify their real name as well as the previously-approved pseudonym on the BEARS request. Request for password reset to ALS (i.e., UNIX password) is done through the BEARS or calling the Enterprise Help Desk. Request for second level password reset is completed by emailing the ALS Functional Coordinator at *SBSE CLO FORT.

# Court Tables

5.19.12.11.3 (04-28-2015) Court Tables Within ALS are tables that include all recording offices available for document filing. These recording offices ("courts" ) are assigned a five or six-digit ID number. The court table is maintained by the ALS Coordinator. Refer to MAINTXC screen on ALS for the appropriate court number. Because the court numbers are linked to all the historical documents, NEVER REMOVE A COURT ID FROM ALS. Always coordinate with the ALS programming staff if it is believed a ID number should be removed.

# Zip Code Tables

5.19.12.11.4 (09-09-2021) Zip Code Tables When an NFTL is created in ALS, the filing location defaults to the recording office corresponding with the taxpayer's zip code. These default filing offices are determined by the zip code tables. Occasionally, due to changes in zip code alignment, the use of previously unused zip codes, or restrictions regarding the zip code, the tables must be updated. The ALS Coordinator is responsible for maintaining the zip code tables. The ALS function Maintxz is used for this purpose. The Coordinator may receive referrals regarding unknown or incorrect zip codes; however, most updates are driven by the zip code report portion of the ACS/ICS rejects. See IRM 5.19.12.9.4, ACS/ICS Rejects. Change requests should include the following: Zip code, including the 4 digit extension, when necessary The recording office that has been identified as the court of record If the zip code is currently in ALS, to what recording office the zip code points and to what it should be changed If the request is for an addition of a new zip code, to which recording office the zip code should point. When requests for changes or additions are made, verify the zip code is not in a disaster area that has had enforcement activity suspended. If the zip code is in a disaster area, input the zip code and the freeze so that no new NFTLs can be filed. If in doubt whether the zip code is affected (e.g., an entire county is not impacted), contact the Disaster Coordinator for guidance. Keep a listing of all zip code changes. Submit these changes quarterly to the Headquarters Analyst for ICS, so that ICS can be updated with the changes and additional zip codes. ICS updates their system quarterly.

# POD Key Listing

5.19.12.11.5 (04-28-2015) POD Key Listing Each week, ALS receives an extract from ICS of its nationwide employee table. Based on the current employee ID, name and new employee number, badge number, area code and phone number, information in ALS will be updated to match information transmitted by ICS. ICS employee information is updated systemically in ALS, with the exception of the Post of Duty (POD) code. Use Maintro to add the POD code. Also use Maintro to add or modify information for all other ALS users in the same POD. Requests for POD code updates outside the systemic reports should be on the RO POD ALS Update Form and emailed to *SBSE CLO FORT. Revenue officers cannot file NFTLs until the POD is corrected. It is imperative the report is worked by the FORT on the day it is generated.

# Voucher Removal/Correction

5.19.12.11.6 (04-28-2015) Voucher Removal/Correction Routine corrections to vouchers (e.g., changing fee, adding/deleting lien document) can be done by the CLO teams. See IRM 5.19.12.3.4, Editing the Billing Support Voucher. Significant changes to the voucher or the removal of it are referred by the teams to the ALS coordinator by sending an email to *SBSE CLO FORT. There are occasions when it is necessary to remove a voucher from ALS. The Coordinator can remove the voucher, but it is only done when both the following have occurred: It has been verified that the voucher has not been mailed to any of the recording offices on the voucher and no mailing date has been input; and The request has been approved by the CLO Department Manager. The ALS Coordinator also corrects dates that have been entered into the date field of the voucher program. Permission to change the date may be given to CLO Department Managers; however, tracking of these changes should be maintained by the ALS Coordinator. Requests for voucher changes and the tracking of the vouchers should contain the following: Voucher number Recording offices involved Reason for removal/correction Department Manager approving the request Vouchers being removed must be tracked by the FORT to verify they have not been previously requested and for review purposes. The listing of voucher changes is maintained for 6 months.

# Electronic Lien Filings (ELF)

5.19.12.12 (04-16-2024) Electronic Lien Filings (ELF) The majority of lien documents are filed by paper and mailed through the USPS, but there are a few recording offices that receive information electronically. Non-paper filings are considered Electronic Lien Filings (ELF). The following recording offices currently have some form of an electronic filing process: Recording Location Electronic Filings Massachusetts - United States District Court (USDC) in Boston Lien documents Minnesota - all recording offices Lien documents (ELF process is currently inactive; paper documents being filed) Connecticut - Secretary of State (SOS) Historic lien documents only; changed to paper document filings in 2020 California - Secretary of State (SOS) Index only, paper documents filed New York City - five boroughs Index only, paper documents filed Information is exchanged with the ELF recording offices in various ways by ALS. Also, not all lien documents can be provided electronically (e.g., special condition NFTLs). See the ALS User Guide, Chapter 13, Electronic Lien Filing, for further details on the differences between the ELF recording offices. The FORT has general oversight responsibility for the ELF exchange process; however, the CLO teams are responsible for the normal processing of the lien documents. Coordination between the person delivering the ELF files and the team assigned the recording office is essential. NFTLs prepared for ELF recording offices must be approved from the ALS queue each Tuesday and Thursday by the applicable team manager. The NFTLs being approved should be for the same range of dates as all other lien documents in that print batch. Approval on ELF is equivalent to the print process in triggering the CDP notice. The approval of ELF filings produces a document file the day after the approval is done. This file is delivered to the recording office for the recordation of the lien documents. Reminder: NFTLs must be approved prior to the input of the POA or Co-Obligor information to ALS. Lien releases do not go through an approval process since they do not trigger a CDP notice. Each day a file is generated for the prior day. When delivery is made to the recording office there will be multiple release files and one NFTL file. Prepare vouchers prepared for the ELF recording offices using standard procedures, with certain exceptions as noted below. Ensure the voucher for the ELF recording office matches the NFTLs approved and other lien documents for filing. Identify the voucher for ELF recording offices with the payment definer of "E" . Date stamp the voucher with the date the file is delivered. Maintain a log of all files sent to, and returned from, the ELF recording offices with the number and type of errors or rejected records.

# Manual Input of Recording Information to ELF Offices

5.19.12.12.1 (09-09-2021) Manual Input of Recording Information to ELF Offices NFTLs for ELF recording offices are electronic files on ALS. Recording information cannot be manually input into an electronic file using the regular CRD process. The ALS Coordinator must add the recording information into a file for upload to ALS. If an NFTL filed through ELF does not show recording data but through research the data is located, send an email to the FORT with the SLID number and court recording data found. When recording information files are uploaded to ALS and notification is given during the upload process that some of the recording information cannot be loaded, review the information. Below are some common scenarios that could occur and how to resolve. If... Then... There is a transposition of numbers (i.e., SLID not correct) Notify the recording office of the situation. Determine what the SLID should be. correct the file, and upload the information again. The recording information was previously loaded Determine if this is a duplicate filing and take appropriate action. See IRM 5.19.12.2.4, Duplicate Filings of NFTL. The recording information is for a release of lien and not the NFTL itself No action is required.

# Special Circumstances

5.19.12.13 (04-28-2015) Special Circumstances In this section are types of special circumstances that require special handling or contact with the appropriate function and/or coordinator.

# Signature of Lien Documents

5.19.12.13.1 (04-28-2015) Signature of Lien Documents Although not required for legal sufficiency, lien documents are signed by an IRS official prior to filing to facilitate the recordation process with the recording offices. The lien documents printed in the CLO for recordation and taxpayer copies of the documents printed at CPS are imprinted with a digitized signature of a delegated official. See IRM 1.2.2.6.4, Delegation Order 5-4 (Rev. 3), Federal Tax Lien Certificates. When the person whose signature is on the lien documents changes, programming must be updated in ALS and at CPS with the new signatory's name, title, and signature. CLO management is responsible for notifying Collection Policy, the ALS programming staff, and/or other applicable when changes to the signature are needed.

# Disaster Relief

5.19.12.13.2 (09-09-2021) Disaster Relief When a disaster occurs, the President can declare a state, municipality, or other locale as a federal disaster area and invoke the Robert T. Stafford Disaster Relief and Emergency Assistance Act, which authorizes tax relief to affected taxpayers. The Disaster Assistance & Emergency Relief program provides guidance for responding to federally declared disasters. See the following for additional information: IRM 25.16.1, Disaster Assistance and Emergency Relief-Program Guidelines IRM 5.1.12.2, Collection Relief for Taxpayers Affected by a Disaster. Disaster Assistance and Emergency Relief Program page on IRS Source(https://irssource.web.irs.gov/SBSE/lists/HumanCapitalOffice/DispItemForm.aspx?ID=39&https://irssource.web.irs.gov/SBSE/Lists/HumanCapitalOffice/AllItems.aspx&SectionName=Organizational%20Support%20&%20Continuity%20of%20Operations) Federal Emergency Management Agency (FEMA) internet page (https://www.fema.gov/disaster/declarations) When federal tax relief is authorized, a disaster freeze code is placed on the affected taxpayers' accounts for a specified period of time. The type of freeze code reflects the relief that has been granted. An -O freeze provides systemic penalty, interest, and compliance relief and stops most collection actions, including NFTL filings. An -S freeze provides systemic penalty and interest relief, but does not automatically provide compliance relief nor does it stop collection actions. The FORT coordinates the impact of the disaster on lien processing with guidance from Headquarters, as needed.

# Disaster Relief - FORT Role

5.19.12.13.2.1 (06-03-2020) Disaster Relief - FORT Role The FORT (or ALS Coordinator) is responsible for updating ALS and coordinating CLO efforts to prevent the filing of new NFTLs in the disaster areas. The actions normally taken by the FORT (or ALS Coordinator) are described in this subsection. Upon receipt of an -O freeze designation, secure a list of affected zip codes from the FEMA Disasters web page. Verify all the zip codes within the county/parish/jurisdiction are included in the disaster relief. Determine if the recording office in the disaster area is conducting business so other lien documents (e.g., releases, refiles) can be mailed. If the impacted zip code relates to an ELF recording office, contact Headquarters on how to proceed. Using the ALS disaster maintenance screen (Maintdisv), input the zip codes affected by the disaster. Coordinate with the ALS programmers to verify all zip codes are properly marked. Note: ALS systemically blocks NFTL requests in zip codes marked as a disaster area. Notify CLO employees that the -O freeze is in effect and any requests for NFTL filings in impacted areas should be rejected to the requester, unless the requests are approved by management per disaster procedures. Provide guidance to CLO employees for pulling NFTLs recently generated or printed for (but not mailed to) recording offices for the designated disaster area. Give a listing of impacted SLIDs received from the ALS Programmers to the responsible team for deletion from ALS. Advises the responsible team to generate and process a voucher for lien documents for the SOS (when applicable) using the appropriate range of dates. Be sure the range of dates covers all documents that were pending in the queue. The ALS Coordinator takes the following actions. Request the ALS Programmers remove the impacted recording offices from "voucher only" for the identified voucher numbers. Note: If the state has a Secretary of State (SOS) filing requirement, ALWAYS include the SOS voucher in the request. Zip codes. When all zip codes are not impacted, request a listing from the ALS Programmers of the SLIDs, entity, zip codes, and the names of the requesters of the NFTLs for the impacted recording offices. Notify the responsible team that the ALS programmers have removed the NFTLs in the impacted recording offices from the voucher (include SOS, if applicable) and advise the team to process the voucher. Note: When the voucher is processed, only the recording offices that were not removed will be generated. The documents for the removed recording offices will remain in the queue. Match the requested listing(s) against the impacted zip codes. When the -O freeze is set, the CLO team will use this listing to delete the NFTLs from ALS and notify the requester of the removal of the NFTL. Reminder: DO NOT give this listing to the teams for deletion of the lien until the -O freeze is set. Notify the teams that the NFTL vouchers for the state can be processed. This excludes impacted States and, when applicable, SOS. Establish a control to monitor the disaster freeze period so the freeze indicator on ALS can be promptly reversed once the disaster relief time frame has passed. Reminder: It is imperative that ALS maintenance tables for recording offices (Maintxc), zip codes (Maintxz), and disaster freezes (Maintdisv) are kept current and accurate as these tables interact to ensure disaster freezes are applied to the correct filing locations.

# Disaster Relief - CLO Teams Role

5.19.12.13.2.2 (06-03-2020) Disaster Relief - CLO Teams Role As referenced in the preceding subsection, new NFTLs generally are not filed in a disaster area; however, in certain instances, a new NFTL may be filed with management approval. In these instances, the NFTL request must be manually input to ALS. CLO should process these requests as shown below. Upon receipt of the manual request, review the request for management approval and contact the requester if approval is not evident. Prepare separate BSVs for the new NFTL and the other lien documents for the recording office. Upon notification from the FORT, the CLO team takes the following actions. Returns all requests for NFTL filings in the impacted areas to the requesters with an explanation that the -O freeze is in effect and the NFTL cannot be input. Deletes the NFTLs on the ALS vouchers for the impacted areas that were held pending the disaster determination. When the entire county is not impacted, uses the listing of impacted SLIDs and zip codes provided by the ALS Coordinator to delete the NFTLs. Processes the vouchers as normal once all impacted SLIDs have been removed. Note: Only the unaffected recording offices should be shown on the voucher. Generates specific voucher(s) for the impacted recording offices. Follow standard printing and mailing procedures for recording offices not in the disaster area. Review BSVs for affected recording offices to ensure new NFTLs are not inadvertently included.

# Pending Collection Activity Suspension (-O Freeze)

5.19.12.13.2.3 (06-03-2020) Pending Collection Activity Suspension (-O Freeze) When a disaster has occurred and the decision for the suspension of collection activity has not yet been made, documents should be processed as normal. When the FORT is alerted by Headquarters that the potential exists for the -O freeze on IDRS, the FORT notifies the CLO teams of the situation and what zip codes, counties, or states are potentially impacted. The FORT notification to the CLO teams should state the following: A decision is pending on the suspension of collection activity (-O freeze). Requests for NFTL creations in the impacted areas should be held pending the -O freeze decision. The teams responsible for the impacted areas should generate two vouchers for the impacted recording office - one for new NFTL filings and one for other lien documents (e.g., releases, refiles). Immediately send the voucher numbers to the ALS Coordinator New NFTLs must not be printed for the disaster areas. Processing requests for releases. withdrawals, and other lien documents, and their vouchers, should continue. The FORT will provide additional information as soon as it becomes available. Upon notification from the FORT, the CLO team for the impacted area takes the steps below. Generate two vouchers for the impacted recording office(s)--one for new NFTL filings and one for releases and other documents. Reminder: Be aware of NFTLs against a taxpayer in a disaster area filed in other locations. Immediately relay the voucher numbers to the ALS Coordinator. Immediately notify the ALS Coordinator of the number of NFTLs in each impacted recording office. Process the vouchers for releases and other documents as normal. Following these procedures ensures the NFTLs within the ALS system are held pending the decision to freeze the accounts and enables the site to timely process the lien release filings. When the -O freeze is set, follow the procedures in IRM 5.19.12.13.2.1, Disaster Relief - FORT Role, and IRM 5.19.12.13.2.2, Disaster Relief - CLO Teams Role. If the -O freeze is not set, the CLO teams generate vouchers for the recording offices and process as normal. Regardless of whether an -O freeze is set or not, normal printing schedules should be followed (i.e., Tuesdays and Thursdays).

# Identity (ID) Theft

5.19.12.13.3 (06-03-2020) Identity (ID) Theft CLO may encounter situations or receive inquiries from internal and external customers regarding identity theft. CLO refers all cases regarding identity theft to the function assigned the case, which is then responsible to work the case per instructions in their respective IRM (e.g., IRM 5.1.28, Identity Theft for Collection Employees. If the account status is... Refer to... 26 RO 71 Appropriate OIC Unit 72 (TC 520 cc 60-67, 81, or 83-89) Centralized Insolvency Operation 72 (TC 520 cc 70–75, 80, or 82) Advisory office where the taxpayer resides 72 (TC 520 cc 76 or 77) Appeals office Any other status with a MFT 31 with a TC 971 AC 104 Innocent Spouse Unit Any other status or condition and NFTL filed Advisory office where the taxpayer resides Any other status or condition and no NFTL filed ID Theft team through the team manager or lead TE Document the referral in the ALS history, including the date the referral is made, the status, and name of the referred employee or office. If the assigned office determines that action is necessary to address an NFTL filed against a victim of identify theft, the office will submit a request to CLO following standard procedures. Generally, the request will be for the release of an erroneous NFTL, but in some instances it may be for a withdrawal of the NFTL. See IRM 5.12.3.10, Erroneous NFTL in ID Theft Situation. For any external inquiries on ID Theft cases, follow high risk disclosure rules. See IRM 21.1.3.2.4, Additional Taxpayer Authentication. Process requests for release or withdrawal following standard procedures.

# Government Shutdown

5.19.12.13.4 (06-03-2020) Government Shutdown When there is a lapse in appropriations for government spending, lien processing generally is suspended. Lien documents cannot be sent to the recording office if funds are not available to pay for the filings. Other CLO duties may continue during the shutdown as long as additional expenses are not incurred. The other duties performed are determined by management based on available staffing and may include processes such as inputting data to ALS, providing payoff letters, and generating releases for taxpayers to file (when requested by the taxpayer). Prior to an anticipated shutdown, representatives from CLO, Policy, ALS, and other impacted stakeholders should conference to coordinate a shutdown plan. Depending on the situation, the plan may address the inputting of new NFTLs and the printing of recently-created documents. Usually, immediately before the anticipated shutdown, CLO stops creating new NFTLs pending the shutdown resolution and prints all the lien documents in the print queue and processes them for filing. Upon shutdown, CLO stops inputting NFTL and most other manual requests to ALS. Exception: CLO should continue inputting requests for lien releases and refiles, as resources allow. During the shutdown, ALS systemic processes normally continue, including the systemic interface with Master File. As a result, lien releases will continue to be generated in ALS, even though the releases cannot be filed during the shutdown. The ALS systemic interface with CPS is also operational so lien notices for the pre-shutdown NFTLs will be issued by CPS, as their resources allow. The systemic generation of NFTLs through the ACS/ALS interface may or may not cease, depending on the shutdown plan. The actions taken when the government resumes operations is dependent on the length of the shutdown. Generally for brief shutdowns, CLO resumes normal processing. For longer shutdowns, CLO may need to prioritize their processes, such as immediately printing releases generated during the shutdown and reviewing accumulated mail for release requests. A conference of the stakeholders may be necessary to devise a resumption plan.

# Judicial Foreclosures

5.19.12.14 (09-09-2021) Judicial Foreclosures Advisory generally is responsible for processing foreclosure cases. However, CLO may receive requests from the Assistant United States Attorney's Office (AUSA) for NFTL information relative to judicial foreclosure cases. These requests might be received by fax, E-fax, mail, email, or telephone. Requests are worked in accordance with the procedures found in IRM 5.12.4.2, Judicial Foreclosures.

# Job Aid for Unpostable TC 582

Exhibit 5.19.12-1 Job Aid for Unpostable TC 582 This Exhibit shows the most common Master File unpostable conditions associated with the systemic upload of Transaction Code (TC) 582 from ALS. See IRM 5.19.12.10, GUF Unpostables. The conditions, broken down by IMF and BMF, are listed by their Unpostable Code (UPC), Reason Code (RC), and Summary Description. Each condition is followed by a table that describes common problems that may have caused the unpostable (as discovered through research of IDRS and ALS) and the most likely resolution for those problems. The described resolutions may not fit every situation but may vary based on the case facts. In most cases, the TC 582 should be re-input to IDRS with the date of the unpostable TC 582. Reminder: FOR ALL CASES, the IDRS control base must be closed after IDRS actions are completed. Individual Master File (IMF) 151-0 No entity present or account not on IDRS (MFT 30, 31, 55) Research Shows... IDRS Resolution ALS Resolution Name control on ALS is incorrect Input TC 582 Correct the name control TIN on the NFTL is incorrect Input TC 582 on correct module and close control base on incorrect module Create a Not To Be Filed lien record to correct the TIN MFT 55 or 31 module not established when TC tried to post Input TC 582 No action needed 152-1 Name control mismatch (Name line incorrect) Research Shows... IDRS Resolution ALS Resolution Name control on ALS is incorrect Input TC 582 Correct the name control Name on the NFTL is incorrect No action needed Request an Amended NFTL to correct the name TIN on the NFTL is incorrect Input TC 582 on correct module and close control base on incorrect module Create a Not To Be Filed lien record to correct the TIN 159-0 Attempts to create a module MFT 30, 31, 55 (Module is not on IDRS) Research Shows... IDRS Resolution ALS Resolution MFT on NFTL/ALS is incorrect Input TC 582 on correct module and close control base on incorrect module Create a Not To Be Filed lien record to correct the MFT Tax period on NFTL is incorrect Close control base on incorrect module Request an Amended NFTL to correct the tax period An MFT 13 or 55 module was created by the unpostable and the correct MFT 30 module has both a posted TC 240 and TC 582 Close control base on incorrect module No action needed An MFT 13 or 55 module was created by the unpostable and the correct MFT 30 module does NOT have a posted TC 240 and TC 582 Input TC 582 on correct module and close control base on incorrect module No action needed Module was not established when TC tried to post Input TC 582 No action needed 162-0 Period ending date is different Research Shows... IDRS Resolution ALS Resolution Ending date for the tax period on the NFTL is incorrect Close control base on incorrect module Request an Amended NFTL to correct the tax period 186-0 Account transferred out (Status 29) Research Shows... IDRS Resolution ALS Resolution TC 400 and TC 608 are on the module No action needed Mark period satisfied or release lien, if all periods on the NFTL are satisfied TC 400 but no TC 608 is on the module and module is satisfied on ANMF No action needed Mark period satisfied or release lien, if all periods on the NFTL are satisfied TC 400 but no TC 608 is on the module and module is open on ANMF No action needed No action needed 188-0 Module creating transaction not containing name information input to module earlier than the earliest name line Research Shows... IDRS Resolution ALS Resolution Tax period on NFTL is incorrect Input TC 582 on correct module and close control base on incorrect module Request an Amended NFTL to correct the tax period NFTL is correct, but the module was not established when TC tried to post Input TC 582 No action needed 197-0 Attempts to post to a module that was placed on retention register Research Shows... IDRS Resolution ALS Resolution Tax period on NFTL is incorrect and module is not satisfied MFREQ correct module onto IDRS, if necessary and close control base on incorrect module Request an Amended NFTL to correct the tax period Tax period on NFTL is correct and module is not satisfied MFREQ correct module onto IDRS, if necessary, and input TC 582 No action needed Tax period on NFTL is correct and module is satisfied MFREQ correct module onto IDRS, if necessary, and input TC 582 Mark period satisfied or release lien, if all periods on the NFTL are satisfied Business Master File (BMF) 301-1 Failed to match TIN with an account on BMF Research Shows... IDRS Resolution ALS Resolution Name control on ALS is incorrect Input TC 582 Correct the name control TIN on NFTL is incorrect Input TC 582 on correct module and close control base on incorrect module Create a Not To Be Filed lien record to correct the TIN 303-1 Failed to match the entity name control Research Shows... IDRS Resolution ALS Resolution Name control on ALS is incorrect Input TC 582 Correct the name control Name on the NFTL is incorrect No action needed Request an Amended NFTL to correct the name 309-1 Attempts to establish a tax module Research Shows... IDRS Resolution ALS Resolution Tax period on NFTL is incorrect Close control base on incorrect module Request an Amended NFTL to correct the tax period 311-1 Account transferred out (Status 29) Research Shows... IDRS Resolution ALS Resolution TC 400 and TC 608 are on the module No action needed Mark period satisfied or release lien, if all periods on the NFTL are satisfied TC 400 but no TC 608 is on the module and module is satisfied on ANMF No action needed Mark period satisfied or release lien, if all periods on the NFTL are satisfied TC 400 but no TC 608 is on the module and module is open on ANMF No action needed No action needed 390-5 Mismatch TIN with master file or no return posted to module Research Shows... IDRS Resolution ALS Resolution TIN on NFTL is incorrect Input TC 582 on correct module and close control base on incorrect module Create a Not To Be Filed lien record to correct the TIN Tax period on NFTL is incorrect Close control base on incorrect module Request an Amended NFTL to correct the tax period Module not established when TC tried to post Input TC 582 No action needed

# Glossary of Common Acronyms and Terms for Centralized Lien Operation

Exhibit 5.19.12-2 Glossary of Common Acronyms and Terms for Centralized Lien Operation Acronym Definition ACS Automated Collection Service AIS Automated Insolvency System ALS Automated Lien System AMS Accounts Management System BMF Business Master File BSV Billing Support Voucher CAF Centralized Authorization File CAP Collection Appeals Program CCP Centralized Case Processing CDP Collection Due Process CIO Centralized Insolvency Operation CLO Centralized Lien Operation COIC Centralized Offer in Compromise CPS Correspondence Production Services CRD Court Recording Date CSED Collection Statute Expiration Date DDIA Direct Debit Installment Agreement DPC Designated Payment Code EFT Electronic Fund Transfer EIN Employer Identification number ELF Electronic Lien Filing FMS Financial Management Service FORT Field Office Resource Team ICS Integrated Collection System IDRS Integrated Data Retrieval System IFS Integrated Financial System IMF Individual Master File IRC Internal Revenue Code IRM Internal Revenue Manual LFI Lien Filed Indicator LLC Limited Liability Company MCAR Mutual Collection Assistance Request MF Master File MFT Master File Transaction MOIC Monitoring Offer in Compromise NAOC NFTL After Original CSED (aka Portland Lien) NFOI Non-Field Other Investigation NFTL Notice of Federal Tax Lien NMF Non-Master File NTBFL Not To Be Filed Lien Record OIC Offer In Compromise PDF Portable Data Format PII Personally Identifiable Information PLL Potentially Lost (Notice of) Lien POA Power of Attorney POD Post of Duty POL Payoff Letter RO Revenue Officer SERP Servicewide Electronic Research Program SFR Substitute for Return SLID Serial Lien Identification Number SSN Social Security Number TAC Taxpayer Assistance Center (Walk-in) TAS Taxpayer Advocate Service TC Transaction Code TFRP Trust Fund Recovery Penalty TIN Taxpayer Identification Number TM Territory Manager USDC United States District Court USPS United States Postal Service WDAR Withdrawal of NFTL After Lien Release Generic Term Common Reference County Recording office (e.g., county recorder) Court Recording office (also an ALS command) Field Field Collection Release Certificate of Release of Federal Tax Lien Revocation Revocation of the release of the federal tax lien Spool ALS print repository Voucher Billing Support Voucher (also an ALS command) Withdrawal Withdrawal of Notice of Federal Tax Lien

# Sample Notification of Lost NFTL

Exhibit 5.19.12-3 Sample Notification of Lost NFTL This memorandum template is for use by CLO when contacting Field employees about lost NFTLs. See IRM 5.19.12.9.5, Potential Lost NFTLs. Notification of Lost Notice of Federal Tax Lien Date: From: Centralized Lien Operation, Team ------ To: Taxpayer: TIN: SLID(s): The Notice of Federal Tax Lien referenced above appeared on the Automated Lien System (ALS) Potential Lost Lien Report. This occurs when no recording information is reported for an NFTL within 90 days of its creation. In accordance with lost NFTL procedures in IRM 5.12.7.14 and 5.19.12.9.5, we researched available sources, but were unable to locate any data indicating the NFTL was recorded. As a result, the NFTL has been removed from the Potential Lost Lien Report and it is no longer an active NFTL on ALS. Also, TCs 583 and 361 have been input to IDRS to reverse the Lien Filing Indicator and filing fee for this NFTL. Since you are assigned the taxpayer's case, we are notifying you of the situation so that you can make a determination regarding a replacement for this NFTL. Please take the following actions: Make a determination whether a replacement NFTL is appropriate for the tax modules on this lost NFTL. If a replacement NFTL is appropriate, complete Form 12636 and submit it via secure email to the CLO Team shown above. If a replacement NFTL is not appropriate, no further action is required. No response to this memo is necessary. This situation is no longer controlled by CLO. A facsimile of the NFTL is attached for your convenience. If you have any questions, please call our internal line at 1-800-913-4170.

# Sample Letter to Recording Office on Treasury Offset Program

Exhibit 5.19.12-4 Sample Letter to Recording Office on Treasury Offset Program This letter template is for use by CLO when contacting recording offices about TOP offsets and their requirement to file lien documents despite the offset. See IRM 5.19.12.7.4.1, Treasury Offset Program (TOP). [Recording Official] [Recording Office] [Address] re: Billing Support Voucher [BSV number, Date of BSV] Dear [Name of Recording Official, if known] This letter concerns lien documents returned by your office without being recorded. The Internal Revenue Service Centralized Lien Operation (CLO) submitted [xxx] Notices of Federal Tax Lien, [xxx] Certificates of Release, and [xxx] Withdrawal notices to your office for filing with the Billing Support Voucher (BSV) referenced above. Your office returned the lien documents citing non-payment of the filing fees. The Internal Revenue Service did, in fact, pay the fees at issue. Simultaneously with the filings, a certified payment of $[xxxxx] was transmitted from the Department of the Treasury Financial Management Service (FMS), the agency that disburses lien filing fees. The payment, however, was subject to an administrative offset by the Treasury Offset Program to satisfy a delinquent debt owed by another agency of [insert state/ county]. To show that FMS made the post-offset payment, a payment of $1.00 (or other reduced amount) was deposited into your bank account. The Treasury Offset Program (TOP) is a federal centralized offset program administered by FMS to collect delinquent debts owed by vendors to other government agencies. Before a vendor receives a federal payment (including payment of lien filing fees), FMS searches the database to determine whether the jurisdiction as a whole owes a federal debt. If a debt is found, FMS offsets the payment to apply toward the delinquency and sends a payment of at least $1.00 to the vendor as indication of payment. Enclosed is additional information regarding TOP. You can also find information about TOP at http://www.fms.treas.gov. A notice of federal tax lien (NFTL) preserves the federal government's lien priority in a delinquent taxpayer's property by giving notice to certain competing creditors. Therefore, it is vital that recording offices timely file and record each NFTL and, once satisfied, each certificate of release to prevent harm to the taxpayer. Moreover, the Internal Revenue Code accords to taxpayers the statutory right to a release of the tax lien within 30 days of satisfaction. {Optional paragraph if applicable} [Insert State] has adopted a version of the Uniform Federal Tax Lien Registration Act or similar legislation at [insert applicable state law reference]. State law requires you to file federal lien documents regardless of payment. Moreover, as demonstrated, the federal government has paid the filing fees. The government has both a common law and a statutory right of setoff. United States v. Tafoya, 803 F.2d 140, 141-42 (5th Cir. 1986). "The government has the same right which belongs to every creditor, to apply the unappropriated moneys of his debtor, in his hands, in extinguishment of the debts due to him." United States v. Munsey Trust Co., 332 U.S. 234, 239 (1947). Your office must work with the State function that incurred the federal debt to internally account for the funds. Your office is not permitted to discontinue filing federal tax lien documents because of the offset situation. We request that your office immediately record the lien documents referenced above and any other documents you receive from the Internal Revenue Service in the future. If you have any questions on this matter, please contact me at the number shown above. Sincerely, [Name] Operations Manager Centralized Lien Operation Enclosure

# Sample Letter to Recording Office on Rejected Lien Documents

Exhibit 5.19.12-5 Sample Letter to Recording Office on Rejected Lien Documents This letter template is for use by CLO when returning lien documents to recording offices to correct an IRS filing error. The text detailing the specifics of the situation should be modified to fit the situation. See IRM 5.19.12.7.4, Recording Offices. [Recording Official] [Recording Office] [Address] Dear [Name of Recording Official, if known] Enclosed please find the lien documents and Billing Support Voucher [BSV number], originally dated [BSV date] you returned to our office citing the following error: □ Payment issue □ Duplicate filing □ Missing or incorrect recording data for related document SLIDs: [List SLID numbers] □ Other: We apologize for our error and have corrected the situation in the attached documents. We ask that you record these documents as soon as possible. We appreciate your feedback on this situation as it helps us to improve our quality. If there is a problem with recording documents that we send you in the future, the fastest way to resolve the problem is to contact us on our toll-free hot line at 1-800-913-4170. This line is always answered by a live operator and we can usually resolve the issue immediately. Delays in filing notices of lien can jeopardize the interest of the government and delays in filing releases of lien can harm taxpayers. To minimize delays, we would appreciate the opportunity to correct the error without your having to return the documents. If you have any questions or comments about our operation, please contact us. Thank you for your consideration and assistance. Sincerely, [Name] Operations Manager Centralized Lien Operation Enclosure