Part 21. Customer Account Services

Chapter 5. Account Resolution

Section 7. Payment Tracers

21.5.7  Payment Tracers

Manual Transmittal

August 17, 2012

Purpose

(1) This transmits revised IRM 21.5.7, Account Resolution, Payment Tracers.

Material Changes

(1) Miscellaneous editorial changes - web site addresses, legal references and IRM references were reviewed and updated as necessary

(2) IRM 21.5.7.3.1 Reworded so that the information is better understood.

(3) IPU 11U1814 issued 12-13-2011 IRM 21.5.7.3.5 Added information to clarify that AM employees in remote sites and TAC employees are to refer inquiries to the campus when the taxpayer indicates the check was attached to the return.

(4) IRM 21.5.7.3.5 Removed Files telephone numbers from the IRM and placed a link to the telephone numbers located on SERP.

(5) IPU 12U0865 issued 04-25-2012 IRM 21.5.7.4.2 Updated information regarding the use of Form 4446, Payment Tracer Research Record. Do not use the version found in Accounts Management Services (AMS) until it is updated in January 2013.

(6) IRM 21.5.7.4.6.5 Updated information regarding the input of CC NOREF.

(7) IRM 21.5.7.4.6.7 Added a reference to IRM 21.3.12.4, Determine the Earliest The Taxpayer Can Full Pay, for AM balance due issues.

(8) IRM 21.5.7.4.6.9 Added a reference to IRM 21.3.12.4, Determine the Earliest The Taxpayer Can Full Pay, for AM balance due issues.

(9) IRM 21.5.7.4.7.1 Added a sentence to clarify what is meant by "All Payment Tracer Procedures" .

(10) IRM 21.5.7.4.7.4(8) Removed the Lockbox fax numbers and placed a link to the Lockbox fax numbers located on SERP.

(11) IPU 12U0865 issued 04-25-2012 IRM 21.5.7.4.7.11 Removed information regarding NMF on AMS. This information is not available through AMS.

(12) IRM 5.7.4.7.17 Added a reference to IRM 21.3.12.4, Determine the Earliest The Taxpayer Can Full Pay, for AM balance due issues.

(13) IPU 11U1814 issued 12-13-2011 IRM Exhibit 21.5.7-1 Removed information regarding Atlanta Hardcore Payment Tracer Function and refer any cases to Kansas City Hardcore Payment Tracer Function

(14) IRM 21.5.7-1 Removed the Hardcore Payment Tracer Addresses and placed a link to the addresses located on SERP.

Effect on Other Documents

IRM 21.5.7 dated August 26, 2011 (effective October 1, 2011) is superseded. This IRM also incorporates the following Interim Procedural Updates (IPUs) - 11U1814 (issued 12-31-2011) and 12U0865 (issued 04-25-2012).

Audience

All employees performing account work.

Effective Date

(10-01-2012)

Ivy S. McChesney
Director, Accounts Management
Wage and Investment Division

21.5.7.1  (10-01-2009)
Payment Tracer Overview

  1. This section provides information on payment tracers. Payments not applied to the proper tax module may cause erroneous notices or refunds.

  2. Taxpayers may resolve missing/misapplied payment issues through the Integrated Customer Communications Environment (ICCE), formally known as Telephone Routing Interactive System (TRIS), written correspondence, phone contact with a Customer Service Representative (CSR), Taxpayer Resolution Representative (TRR), or a Taxpayer Assistance Center (TAC) visit.

  3. All Customer Service Representatives, including Automated Collection System (ACS), Campus Collection Operations, and TAC, are responsible for researching and resolving payment tracer inquiries.

  4. This section provides procedures for:

    • locating missing payments

    • deciding who works payment tracer cases needing various levels of research

  5. Hard Core Payment Tracer (HCPT) instructions have been removed from IRM 21.5.7 and can be found in IRM 3.17.5, Accounting and Data Control - Hardcore Payment Tracers.

21.5.7.2  (10-01-2003)
What Is a Payment Tracer

  1. A payment tracer is the process used to locate a missing or misapplied payment. A payment tracer case is not resolved until the missing or misapplied payment is correctly applied to a taxpayer's account.

21.5.7.3  (10-01-2011)
Missing Payments Research

  1. Various research tools can help find missing payments as described below and in this section. As of January 1, 2010 use of the Integrated Automation Technologies (IAT) TC Tracer tool became mandatory, see Exhibit 21.2.2-2, Mandated IAT Tools.

  2. Before disclosing any tax information:

    1. Be sure you are speaking with the taxpayer or the taxpayer's authorized representative. See IRM 21.1.3.2, General Disclosure Guidelines, for more information.

    2. Review procedures in IRM 11.3.2.6.1, Leaving Information on Answering Machines/Voice Mail, before leaving a message on the taxpayer's answering machine or voice mail.

    3. Review procedures in IRM 11.3.1.11, Facsimile Transmission of Tax Information, before faxing confidential information to the taxpayer.

  3. Before conducting research to locate the payment, determine if it has been at least two weeks since the taxpayer mailed their payment or one week since the scheduled date of an authorized electronic payment. If not, ask the taxpayer to call back at that time. Otherwise obtain the following as applicable:

    • Evidence of payment (e.g., copy of cancelled check, front and back)

    • Date payment cleared

    • Taxpayer name and address

    • Taxpayer Identification Number (TIN)

    • Date of payment

    • Amount of payment

    • Tax period payment intended for

    • Means of payment submission (e.g., check, money order, electronic/bank submission)

    • Where payment was sent

    • Type of payment

    • Encoding information (e.g., check or money order)

    • Electronic Federal Tax Payment System (EFTPS) 15 digit EFT number

    • Routing number for financial institution on which the check was drawn

    • Credit Card Payment, confirmation number

    Note:

    In order to alleviate taxpayer burden, every attempt should be made to resolve the missing payment through internal research, including using the Remittance Transaction Research (RTR) system, before requesting any documentation. If the taxpayer cannot provide a copy of the documentation (in person or by fax), advise the taxpayer to send a copy of the documentation to the appropriate campus that processes his payments.

    Note:

    Effective October 28, 2004, the "Check Clearing for the 21st Century Act" or "Check 21," is a federal law passed by the U. S. Government. A "substitute check" is the legal equivalent of the original check and must be processed as if it were the original. Background: Not all banks have the equipment needed to accept electronic payment files and "Check 21" overcomes this obstacle. The truncating bank (which may be any bank in the check collection process) electronically transmits an image of the front and back (including endorsements) of the original check and the recipient bank converts the information into a new form of paper instrument, known as a "substitute check." A substitute check is the same size as the original and is designed to be processed in a bank’s sorting equipment just as though it were the original check and may be returned to the payer with the monthly bank statements. The check’s legend states "This is a legal copy of your check. You can use it the same way you would use the original check."

  4. Additional information and research may be needed. Research criteria may be different depending on the type of payment. See specific procedures.

    Note:

    Phone or fax taxpayer for information needed to resolve the case. If unable to reach taxpayer via telephone or fax (at least two attempts), use the appropriate "C letter."

  5. All functions work the initial phase of a payment tracer case. If a transferable payment is found, follow the credit transfer procedures in IRM 21.5.8, Credit Transfers.

  6. If you cannot locate the payment, prepare Form 4446, Payment Tracer Research Record, and forward the case to the Hardcore Payment Tracer Function (HPTF) as indicated below:

    If Payment Processed At: Then Route to:
    Andover or Fresno Fresno HPTF
    Atlanta or Kansas City Kansas City HPTF
    Austin Austin HPTF
    Brookhaven, Cincinnati or Memphis Cincinnati HPTF
    Ogden or Philadelphia Ogden HPTF



    HPTF is usually located in the Accounting Control/Services Operation. See Exhibit 21.5.7-1, Hardcore Payment Tracer Addresses.
    Follow procedures in IRM 21.5.7.4.2, Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF), to refer payment tracers.

  7. The system used to process a payment determines the research method needed. Endorsement (encoder) information on the copy of the remittance will establish an audit trail. From the endorsement/encoder information, you can reconstruct the Document Locator Number (DLN) assigned to the remittance and/or Remittance Processing System Identification (RPSID) number of the electronic voucher batch number.

  8. Request a manual lien release (TC 582, lien indicator) in the following situations:

    • The lien will not systemically release

    • The action you are taking will fully satisfy all outstanding liabilities and will not post within 30 days

    • It has been more than 30 days since the account was fully satisfied

    Follow procedures in IRM 5.12.3.2.1(5), Liability is Satisfied, for manual lien releases. Employees with access to the Automated Lien System (ALS) should input the lien release. Employees without access to ALS should submit Form 13794, Request for Release, Partial Release, Withdrawal or Partial Withdrawal of Notice of Federal Tax Lien, to the Centralized Lien Unit. The fax numbers can be found by selecting ″Lien Payoff/Release Contact Numbers″ under the Who/Where tab on the SERP Home Page.

21.5.7.3.1  (10-01-2012)
Remittance Transaction Research (RTR) System

  1. The Remittance Transaction Research (RTR) system is a universal access researchable database that contains remittance processing data and images from IRS Integrated Submission and Remittance Processing (ISRP) system and Lockbox Bank processing sites. This system permits data/image storage for up to 7 years and provides immediate retrieval of images online.

  2. RTR provides access to remittance processing data and images. Images include the front and back of the cancelled check or money order and voucher, if submitted with the payment. RTR facilitates and expedites efforts to reconcile taxpayer payments, balance daily deposits, and respond to customer service inquiries. RTR users can query the RTR database to access remittance transaction data and images, print reports, and review notes to transactions.

  3. Access to RTR is currently limited. Requests for access are made via the Automated 5081 system and must be approved by local management. Future system enhancements will allow additional user access.

  4. RTR system must be researched before requesting a copy of the cancelled check or money order from the taxpayer, if both of the following apply:

    • Access to the RTR system is available

    • The payment is an ISRP or Lockbox payment

  5. When performing a query (research) for records, it is critical to enter as much information as possible in order to narrow your research request. A query initiated with minimal information could have debilitating affects to the system.

  6. All Lockbox sites were online as of Dec. 31, 2003. Only payments processed by the banks after installation and programming of the RTR equipment are available. Archive information is not available.

  7. All sites that process ISRP payments came online June 30, 2004. As payment information for the individual campuses became available, the RTR Availability page was updated.

  8. Notes can be accessed to view record changes or deletions made to either an individual record or a block of records prior to posting to Master File. For example, a payment goes unpostable after being sent through Lockbox. Notes should contain enough information to allow users to track the payment record to the point at which it posts to a taxpayer's account. Once posted, changes or movement of credits are tracked through Master File via IDRS.

21.5.7.3.2  (10-05-2010)
Integrated Data Retrieval System (IDRS) Research for Payment

  1. Search for payments on Integrated Data Retrieval System (IDRS) and Corporate Files On Line (CFOL). Refer to Document 6209 Section 8A, Master File Codes, IRM 2.3, IDRS Terminal Responses, and IRM 2.4, IDRS Terminal Input, for information on displaying and using IDRS and CFOL information.

  2. As of January 1, 2010 use of the Integrated Automation Technologies (IAT) TC Tracer tool became mandatory, see Exhibit 21.2.2-2, Mandated IAT Tools. The IAT TC Tracer tool allows research of payments by amount, date, Taxpayer Identification Number (TIN), and/or campus location. The tool is designed to assist with IDRS research and resolution.

  3. Use IDRS Command Codes NAMES/NAMEE to obtain a Social Security Number (SSN) and NAMEI/NAMEB to obtain an Employer Identification Number (EIN) information.

  4. Use the following IDRS/CFOL command codes to search for a payment:

    • SUMRY and TXMOD, for possible misapplications of the payment. They provide different master file tax (MFT) codes for Individual Master File (IMF) and Business Master File (BMF) accounts

    • MFTRA

    • IMFOL and/or BMFOL

    • IMFOL definer code "Q" displays Reason Code (RC) 24 resequencing transactions. See IRM 2.3.51.2(6), Command Code IMFOL

    • INOLET and/or INOLEX, to check all related Taxpayer Identification Numbers (TINs), valid and invalid, provided by taxpayer

    • URINQ, to research the Unidentified Remittance File

    • XSINQ, to research the Excess Collections File

    • ERINV, to research the Error Resolution System (ERS)

    • ESTAB, to order microfilm transcripts, modules on retention, and to request returns, blocks of documents or other documents

    • SCFTR, to research the Service Center Control File

    • UPTIN, to check open and closed unpostables for a specific TIN. Closed unpostable records remain on file 90 days for display

    • TXMOD, SUMRY, and ENMOD with definer "N" after the TIN for ANMF tax modules and entity information

    • INOLE, to research entity information

    • EFTPS, to display electronic payment information

    Reminder:

    Document 6209 Section 8A, Master File Codes, can be used to help read the IDRS/CFOL screens.

  5. Research CFOL command codes (CC) for payments if IDRS is not available or if "No Data" on IDRS. CFOL will also show the MFT codes (e.g. MFT 31 for IMF accounts).

  6. Payments post and can be reversed on the Master File. See Exhibit 21.5.8-1, Transaction Codes and Reversals.

    A TC 976 will post with a money amount if the taxpayer submits a payment with an amended return. This credit should be treated as a payment.

21.5.7.3.3  (12-17-2010)
IDRS Research for Federal Tax Deposits (FTDs)

  1. Beginning January 1, 2011, businesses that have a deposit requirement (such as employment tax, excise tax, and corporate income tax) are required to deposit electronically using the Electronic Federal Tax Payment System (EFTPS). Under the regulation issued December 2, 2010, Form 8109 and 8109-B, Federal Tax Deposit Coupon, cannot be used after December 31, 2010.

  2. The following four sites processed FTD payments until January 1, 2011:

    If the payment was from: Then the payment was processed by:
    Alabama, Arkansas, Florida, Kansas, Louisiana, Mississippi, New Mexico, Oklahoma, Texas, Bank of America (North Carolina) Austin Submission Processing Center (ASPC)
    Delaware, District of Columbia, Georgia, Indiana, Kentucky, Maryland, New Jersey, New York City, Long Island, Ohio, Pennsylvania, Virginia, West Virginia, AC International Cincinnati Submission Processing Center (CSPC)
    Connecticut, Illinois, Iowa, Maine, Massachusetts, Michigan (Upper and Lower Peninsula), Minnesota, Missouri, New Hampshire, New York (State), Rhode Island, South Carolina, Tennessee, Vermont, Wisconsin Kansas City Submission Processing Center (KSPC)
    Alaska, Arizona, California, Colorado, Hawaii, Idaho, Montana, Nebraska, Nevada, North Carolina, North Dakota, Oregon, South Dakota, Utah, Washington (State), Wyoming Ogden Submission Processing Center (OSPC)

  3. When researching for FTD payments made before January 1, 2011, check the module the payment was intended for to determine if the deposit was applied and then transferred to another module or account. Computer Condition Code (CCC) E on an employment tax return indicates the taxpayer requested to credit elect all or part of an overpayment. Missing FTD payments may be included in a credit elect amount located on a subsequent module. See Document 6209 Section 3.5, Tax Return Information - Computer Condition Codes, for additional information on CCCs.

  4. A "rollover" to the FTD credit module, (indicated on IDRS by the presence of MFT 01 and the tax period 000000) occurs automatically when more credits are posted than claimed on the return. A single excess FTD may be transferred, if a return has not posted for the subsequent tax period. The reverse credit will show "R" following the transaction code, with "P" following the Document Locator Number (DLN). The gaining module will show the same microfilm serial number, with "A" following the DLN. The 9th and 10th digits of the DLN will be "99" .

  5. A "rollback" happens when more credits are claimed on the return than are present in the module. If the return has not posted for the subsequent tax period, a single FTD, equaling the difference, may be transferred back to the prior module. The same identifying data, "R" and "P" , indicate a "rollback" . A rollback can occur between a Form 940, Employer's Annual Federal Unemployment (FUTA) Tax Return, and Form 941, Employer's Quarterly Federal Tax Return.

  6. Research unpostables and the unidentified remittance file (URF). An unreversed Transaction Code (TC) 971 with Action Code (AC) 296 indicates a payment was moved to either the Unidentified Remittance File (URF) or Excess Collection File (XSF).

  7. If you are staffing the AM toll-free lines, follow procedures in the first "Note" in IRM 21.5.7.3 (3), Missing Payments Research. Otherwise, follow procedures in IRM 21.5.7.4.7.14, Federal Tax Deposits (FTD), for additional FTD research guidance.

21.5.7.3.4  (10-03-2003)
Requesting Documents Through IDRS

  1. All functions working payment tracer cases are responsible for requesting tax returns, documents, records, blocks, etc. in order to resolve the case.

  2. For payments made prior to the implementation of the Residual Remittance Processing System (RRPS) in 1999, command code ESTAB can be used to request a single document or entire block using the payment document locator number (DLN). The payment DLN can be obtained from the remittance or from IDRS/CFOL next to the payment. All campuses implemented RRPS during 1999. The major change with the implementation of RRPS is the elimination of the DLN on the payment posting documents. If a payment posts as a TC 610, do not request the document. There will not be a payment posting voucher in Files. For more information on RRPS payment documents and requesting archived images of the payment document or checks, follow procedures in IRM 21.5.7.4.7.1, Integrated Submission and Remittance Processing (ISRP) and Residual Remittance Processing System (RRPS).

  3. Research the entire block for the payment document.

  4. For information on Lockbox payment documents, follow procedures in IRM 21.5.7.4.7.4, Lockbox Payments.

21.5.7.3.5  (10-01-2012)
Remittance Left Attached to the Return

  1. If the taxpayer states the remittance was submitted with the tax return, has not stopped payment, and HAS NOT issued a replacement check:

    1. Prepare and fax Form 2275, Records Request, Charge and Recharge, to the appropriate campus files area. The Remarks field should include the following, or similar statement: "Please search through the entire document for a payment. If found, submit the payment for processing using the received date of the return. Please reply by fax or telephone if a payment was, or was not attached." Remember to include your name, telephone and fax number, Document Locator Number (DLN) of the return, and payment amount. The campus fax numbers are located on the SERP home page under the Who/Where tab under the title Files Contact Listing (the former IAP). The fax number are generally located in the Special Search section for each campus.

      Exception:

      Accounts Management (AM) toll-free remote call sites and Taxpayer Assistance Center (TAC) personnel do not prepare Form 2275 for the payment. Complete Form 4442, Inquiry Referral, and route to the Campus AM paper function within your Directorate. Indicate the following on Form 4442, "Document must be searched in files to look for the remittance" . Include all information available/obtained from the taxpayer i.e., name, Taxpayer Identification Number (TIN), amount, date of payment, etc. The Form 4442 can be used in this situation because the request is staying within the Operation (AM) and it is not a referral to another area for a payment tracer or hard core payment tracer.

    2. Follow these procedures when you receive the response from files:

    If the remittance is: Then
    Found Advise the taxpayer the remittance was found and it will be processed using the received date of the return.
    NOT found Advise the taxpayer the check was not found and request payment.

  2. If the taxpayer states the remittance was submitted with the tax return, has stopped payment, and HAS NOT issued a replacement check:

    1. Advise the taxpayer to submit payment with correspondence and an explanation.

    2. When correspondence is received, ESTAB for the return. CIS sites must use Document Request Code "O" (alpha O) to request the original return.

    3. Follow steps in the If/Then chart in (3) below.

  3. If the taxpayer states the remittance was submitted with the tax return, has or has not stopped payment and HAS issued a replacement check:

    1. Use CC ESTAB to request the original return from files. CIS sites must use Document Request Code "O" (alpha O) to request the original return. Search through the entire return and envelope for the uncashed remittance.

      Exception:

      Accounts Management (AM) toll-free remote call sites and Taxpayer Assistance Center (TAC) personnel do not ESTAB for the payment. Complete Form 4442, Inquiry Referral, and route to the Campus AM paper function within your Directorate. Indicate the following on Form 4442, "Document must be obtained from files in order to search for the remittance" . Include all information available/obtained from the taxpayer i.e., name, TIN, amount, date of payment, etc. Indicate on Form 4442 whether the taxpayer has or has not issued a replacement check and whether the taxpayer has or has not stopped payment. The Form 4442 can be used in this situation because the ESTAB request is staying within the Operation (AM) and it is not a referral to another area for a payment tracer or hard core payment tracer.

    If the remittance Then
    Is found Change the date of the subsequent payment to the date of the original payment. Write "VOID" on the check and return it to the taxpayer. Send an apology letter to the taxpayer. Follow procedures in IRM 21.5.7.4.4.4, Form 8546, Claim for Reimbursement of Bank Charges .
    Is NOT found A managerial decision must be made to change the date of the subsequent payment to the date of the original payment. Send an apology letter to the taxpayer. Follow procedures in IRM 21.5.7.4.4.4, Form 8546, Claim for Reimbursement of Bank Charges.

  4. For Electronic Filing (ELF) Returns, if the taxpayer states that the check was attached to Form 8453, U.S. Individual Income Tax Declaration for Electronic Filing, follow procedures in IRM 21.6.6.3.25(5), Electronic Filing System (e-file), to request Form 8453. If you are staffing the AM toll-free telephone lines, follow the exceptions in (1) and (3) above.

  5. Request a manual lien release (TC 582, lien indicator) in the following situations:

    • The lien will not systemically release

    • The action you are taking will fully satisfy all outstanding liabilities and will not post within 30 days

    • It has been more than 30 days since the account was fully satisfied

    Follow procedures in IRM 5.12.3.2.1(5), Liability is Satisfied, for manual lien releases. Employees with access to the Automated Lien System (ALS) should input the lien release. Employees without access to ALS should submit Form 13794, Request for Release, Partial Release, Withdrawal or Partial Withdrawal of Notice of Federal Tax Lien, to the Centralized Lien Unit. The fax numbers can be found by selecting ″Lien Payoff/Release Contact Numbers″ under the Who/Where tab on the SERP Home Page.

21.5.7.3.6  (10-01-2008)
Researching Unidentified Remittances and Excess Collection File

  1. Payments less than one year old which could not be applied to specific taxpayers and/or tax periods are moved to the Unidentified Remittance File (URF). Research the URF, Account 4620, using IDRS CC URINQ. Follow procedures in IRM 3.17.10, Dishonored Check File (DCF) and Unidentified Remittance File (URF). Payments more than one year old which could not be applied can be researched in the Excess Collection File (XSF), Account 6800, using CC XSINQ. Follow procedures in IRM 3.17.220, Excess Collections File.

    Note:

    Beginning July 1, 2006, accounts with credits moved to the URF or XSF should show a TC 971 with Action Code 296 posted to IDRS on the module payment/credit posted to. This indicates all research of the primary and related Taxpayer Identification Numbers (TINs) was completed prior to the transfer into the URF or XSF.

  2. Research URF using CC URINQ or XSF using CC XSINQ by the:

    • Amount of remittance

    • Name control

    • DLN

  3. When payments are found in these accounts:

    1. Prepare Form 8765, IDRS Control File Credit Application. See IRM 21.5.7.4.4.2, Form 8765, IDRS Control File Credit Application, for additional information on Form 8765.

    2. Route the form and supporting evidence to the unidentified remittance/excess collection function in the Accounting Control/Services Operation at the campus that applied the funds to URF/XSF. The Campus can be identified by the first two digits of the Credit Reversal DLN.

    3. Notify taxpayer the payment has been found.

    4. Release TC 470, if applicable.

      Reminder:

      Credits must be cleared by the Statute function, if applicable.

21.5.7.3.7  (10-01-2007)
Researching Unpostable Payments

  1. The transactions that fail validity checks (a system of checks-and-balances applied by the computer) and can not post to master file are referred to as "unpostables" . Each unpostable is assigned a 3 digit unpostable code which identifies the reason or condition that prevented the transaction from posting. Unpostable codes will also have a 1 digit reason code. Unpostable payments appear as UPnnn on TXMOD. These cases should NOT be sent to HPTF. Research unpostable payments on IDRS using the following commands:

    • UPTIN - displays all open and closed unpostables for a specific TIN.

    • UPDIS - displays all open unpostable cases for a specific sequence number.

  2. When you locate a payment in open unpostables use CC UPCAS with Definer "Z" to input the payment information to resolve the unpostable condition. The Unpostable function will make the correction(s) based on this information.

  3. Close the case and notify the taxpayer. Follow procedures in IRM 21.5.5.3.3, Responding to Taxpayer Inquiries, for a time frame to provide the taxpayer.

  4. See IRM 21.5.5, Unpostables, and Document 6209, Section 8 Master File Codes - Unpostables and Resequence, for more information on unpostables.

21.5.7.3.8  (10-01-2007)
Researching Error Resolution Conditions

  1. When documents are rejected from normal processing because of incomplete or incorrect information, they fall out to the Error Resolution System (ERS). ERS is used to correct these documents.

  2. To determine if a return/document is in ERS, access the ERS Control File using CC ERINV. Enter ERINV followed by a space and any of the following:

    • The primary TIN (no hyphens)

    • The complete 14 digit Document Locator Number (DLN) (with hyphens)

    • The Block DLN with XX in place of the serial number (with hyphens)


    Example:


    Research ERINV by TIN − ERINV XXXXXXXXX − Enter/XMIT key (no hyphens)
    Research ERINV by DLN − ERINV XXXXX-XXX-XXXXX-X − Enter/XMIT key (hyphens)

  3. ERINV provides the ERS status code. These codes identify if the item is workable, unworkable, in suspense or if the document has been referred to another area. See Exhibit 3.12.37-21, ERS Status Codes, for IMF and Exhibit 3.12.38-4, ERS Status Codes (Inventory), for BMF.

  4. If you locate the missing payment after researching ERINV, close the case and notify the taxpayer.

21.5.7.3.9  (10-01-2003)
Researching Reject Registers

  1. A reject sequence number in the Integrated Data Retrieval System (IDRS) indicates if there is a reject transaction on the taxpayer's account. The reject transaction has no effect on the IDRS balance.

  2. An alpha reject sequence code appears on IDRS:

    • C - Closed Case

    • O - Open Case

    • S.Sgt. Line Reject - Open Case

  3. Notate the reject sequence number on Form 4446, Payment Tracer Research Record, and send to the HPTF.

21.5.7.4  (10-01-2010)
Resolving Missing Payments Procedures

  1. Payments are identified by Campus, Lockbox, Field Processing methods or Bank Endorsements. The different types of methods and systems used to make and record payments are:

    • Cashier’s Checks

    • Cash Payments

    • Criminal restitution payments made to the clerk of court office, AKA Court-ordered Restitution Payments

    • Direct Debit Installment Agreements

    • Electronic Federal Tax Payment System (EFTPS)

    • Electronic Funds Withdrawal

    • Federal Tax Deposits

    • Free Items

    • Field Office Remittances

    • Foreign Remittances

    • Integrated Submission and Remittance Processing System (ISRP)

    • Lockbox Payments

    • Justice Department Lockbox Receipts

    • Installment Agreement User Fee Lockbox Payments

    • Manual Deposits

    • Money Orders

    • Non-Master File Payments

    • Payments for Lloyds of London Taxpayer

    • Payments Made by Credit Cards

    • Remittance Transaction Research (RTR) System

    • Residual Remittance Processing System (RRPS)

    • Service Center Recognition Image Processing System (SCRIPS)

    • State Income Tax Levy Program Payments (SITLP)

    • Treasury Bonds

    • Truncated checks

  2. When a payment is received via EFTPS and the taxpayer does not have the Electronic Funds Transfer (EFT) number, follow procedures in IRM 21.5.7.4.7.15, Electronic Federal Tax Payment System (EFTPS). The taxpayer may check their own EFTPS payment history by accessing https://www.eftps.gov/eftps/.

  3. If the taxpayer indicates a payment was attached to the tax return but has not cleared the bank, follow procedures in IRM 21.5.7.3.5, Remittance Left Attached to the Return.

  4. If a payment has posted to the wrong account and must be transferred, follow procedures in IRM 21.5.8, Credit Transfers.

  5. Research all accounts completely to resolve a payment tracer inquiry. Only prepare a written referral e.g., Form 4446, Payment Tracer Research Record, after all research is complete and the payments cannot be located.

  6. Notify taxpayer when you locate the payment. Follow procedures in IRM 21.5.7.4.5, Letters and Notices.

21.5.7.4.1  (10-01-2003)
Delay Notices and Offsets

  1. Any employee working a payment tracer case is responsible for delaying notices and/or refund offsets.

  2. Use CC STAUP to update an account in IDRS notice status. This command code generates a history item and converts the module to status 48. All balance due notices will be suppressed, except the first notice. Contact the Notice Review function if a notice must be stopped.

  3. Transaction Code 470 suspends all IDRS notices for 15 weeks. Use TC 470 if taxpayer files a claim or CC STAUP cannot be used.

  4. See IRM 21.5.1, General Adjustments, for more information.

21.5.7.4.2  (04-25-2012)
Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF)

  1. If you cannot locate the missing payment after performing preliminary research (refer to 2 below for preliminary research requirements), prepare Form 4446, Payment Tracer Research Record, documenting all research and refer to HPTF at the campus that processed the payment or processed the most recent payments if unable to determine who processed the missing payment.

  2. Indicate on the Form 4446 preliminary research including:

    • Use of the Integrated Automation Technologies (IAT) TC Tracer Tool. As of January 1, 2010 use of the IAT TC Tracer Tool became mandatory. See Exhibit 21.2.2-2, Mandated IAT Tools.

    • Documentation of IDRS and CFOL research, including command codes IMFOL, BMFOL, URINQ, XSINQ, UPTIN, SCFTR, and ANMF research.

    • RTR, EFTPS, and unpostables research if applicable.

    • Documentation of telephone or fax machine usage to obtain additional information needed to resolve the case.

  3. Prepare and then print Form 4446, Payment Tracer Research Record, through the Publishing web site located under the Forms/Letters/Pubs tab on the SERP Homepage. The current version of the form found in Accounts Management Services (AMS), will be updated at the beginning of 2013. Until that time, do not use the version of the form found in AMS.

    Note:

    When completing Form 4446, you are required to enter your employee IDRS number. DO NOT ENTER YOUR IRS BADGE NUMBER.

  4. Attach any supporting documentation to the Form 4446 such as:

    • A copy of the front and back of the taxpayer's cancelled remittance

    • Taxpayer's bank statements

    • Copy of the payment posting document (Form 813) if a potential mixed/slipped block condition is discovered; this is also needed for encoding errors

  5. Print your CIS case, prepare a CIS routing slip, and attach the Form 4446. Close the control through CIS/AMS.

    Note:

    When completing the routing slip, refer to Exhibit 21.5.7-1 for addresses and mail stops of the HPTFs in each campus.

    Note:

    All EFTPS Hardcore Payment Tracers (HCPT) are processed by the Ogden Service Center. When preparing the Form 4446, be sure to include the EFTPS 15 digit tracking number that begins with a "2" , a confirmation number, or a IMaDD number. The CIS routing slip should be directed to: Internal Revenue Service, Ogden Submission Processing Center, Payment Correction Team 37302, M/S 6264, P.O. Box 9941, Ogden, UT 84409.

  6. If working a telephone inquiry:

    • Print the Form 4446 after documenting all research performed

    • Attach any faxed documentation

    • Refer to HPTF at the campus that processed the payment or processed the most recent payments if unable to determine who processed the missing payment

    • Refer to Exhibit 21.5.7-1 for addresses and mail stops of the HPTFs in each campus

  7. Ensure the Form 4446 is complete and includes the taxpayer's name, TIN, and phone number (include the phone number in the Preliminary Research section of the Form 4446). HPTF may return incomplete, or illegible Forms 4446 for additional research or information. HPTF should not reject Form 4446 if the site does not have access to the information. Managerial review should ensure that all available preliminary research was completed.

  8. Place a closed control on the IDRS module indicating "44462HPTF" using "PAYT" as the category code. HPTF will open a new control when they receive the case.

  9. When referring the case to HPTF, send the taxpayer an 86C Letter, Referring Taxpayer Inquiry/Forms to Another Office, when appropriate and delay notices. Follow procedures in IRM 21.3.3.4.2.1, Use of 86C Letter - Referring Taxpayer Inquiry/Forms to Another Office, to determine when it is necessary to notify the taxpayer of the transfer.

  10. The HPTF located in Accounting Services/Control Operation, is responsible for working complex payment tracer cases after all preliminary research has been exhausted. Use the telephone and fax machine to obtain additional information needed to resolve the case. This will expedite the resolution process. If unable to reach taxpayer via telephone (at least two attempts), use the appropriate "C letter" . HPTF will review Form 4446 to ensure the necessary research and documentation was prepared before accepting the payment tracer case. Any incomplete case will be returned through the team manager with an explanation of the corrective action required.

    Reminder:

    Every type of payment does not require the same amount of documentation to be accepted by the HPTF.

  11. HPTF cases usually involve complex conditions such as:

    • Piggyback checks, encoding errors, and deposit discrepancies that cannot be resolved during preliminary research

    • Non-Master File (NMF) cases (tax class 6 in DLN). See IRM 21.5.7.4.7.11, Automated Non-Master File (ANMF) Payments, for additional information

    • Unpostable codes 140 or 399 from the unpostable unit

    • Field office payments without a field office or RRPS endorsement

    • Closed unpostable cases

    • Slipped/Mixed entity or block conditions involving more than three taxpayer accounts. See IRM 21.5.7.4.6.2, Mixed/Slipped Blocks

    • Payments over seven years old not located in the Excess Collection Files

    • Reject transactions

    • Electronic payments not located through specified research

    • Department of Justice (DOJ) Criminal Restitution Program and DOJ Lockbox Receipts processed at the Kansas City Submission Processing Center (KCSPC). Refer to KCSPC HPTF. Follow procedures in IRM 21.5.7.4.7.6 , Justice Department Lockbox Receipts

    • Criminal restitution payments made to the clerk of court office

    • Form 809, Receipt for Payment of Taxes, or cash register receipt payments, after preliminary research

    • "Free" Items

    Caution:

    Only send dishonored checks to the HPTF if you have proof the check was cashed.

  12. HPTF may transfer cases to other campus HPTF, if applicable. In most situations the case should already be in the campus that processed the payment.

  13. If a refund should be issued, HPTF will apply the tentative substantiated credit, with received date and amount indicated on the proof of payment, within 10 work days of receipt in HPTF.

  14. HPTF is responsible for all subsequent communication with taxpayer after they accept the case.

21.5.7.4.3  (04-19-2006)
Payment Tracers with Collection Issues

  1. Payment tracer cases with collection issues should be routed per IRM 21.3.3.4.10.2, Campus Collection Function Correspondence/Inquiry/Notice.

21.5.7.4.4  (10-01-2009)
Payment Tracer Forms

  1. Special forms are prepared for payment tracer cases. These forms are:

    • Form 4446, Payment Tracer Research Record

    • Form 8646, Checklist to Identify Delays in Processing Federal Tax Deposits (FTDs)

    • Form 8765, IDRS Control File Credit Application

    • Form 3809, Miscellaneous Adjustment Voucher (HPTF only)

    • Form 9533, Lockbox Information Requests

    • Form 8546, Claim for Reimbursement of Bank Charges Incurred Due to Erroneous Service Levy or Misplaced Payment Check

    • Form 11357, Integrated Submission and Remittance Processing Image Retrieval Request

21.5.7.4.4.1  (10-01-2011)
Form 4446, Payment Tracer Research Record

  1. Form 4446, Payment Tracer Research Record, is used to refer a payment tracer case to the Hard Core Payment Tracer Functions (HPTF) after performing preliminary research and reviewing information provided by the taxpayer/bank. Refer to IRM 21.5.7.4.2(2), Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF). Do not use Form 4442, Inquiry Referral, or Form 4159, Payment Tracer Request, for payment tracer case referrals to HPTF.

  2. Refer to IRM 21.5.7.4.2, Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF), for instructions on completing Form 4446 and routing to HPTF.

  3. FTD cases must have a legible copy of the front and back of the cancelled payment attached to the Form 4446.

    Note:

    To determine which campus processed the FTD coupon, look at who processed the most current payments. The address of the taxpayer on the check can also lead you to the correct campus, although this is not true in all cases.

21.5.7.4.4.2  (11-19-2008)
Form 8765, IDRS Control File Credit Application

  1. When the missing payment is located in the Unidentified Remittance File (URF) or Excess Collection File (XSF), application of the credit cannot be made by persons outside the Unidentified/Excess Collection function. Form 8765, IDRS Control File Credit Application, is used to request Unidentified/Excess to transfer money from the URF and XSF to the taxpayer's account.

    Note:

    The Unidentified/Excess Collection function is usually located in the Accounting Control/Services Operation. Any campus Accounting Control/Services Operation can place funds in URF/XSF; however, transferring money from URF/XSF must be done by the campus that placed funds in URF/XSF. The Campus can be identified by the first two digits of the Credit Reversal DLN.


    Contact number can be found by selecting UNIDENTIFIED/ EXCESS COLLECTION CONTACTS under the Who/Where tab on the SERP Home Page.

  2. The request should identify where to apply the money and supply the documentation from the taxpayer, including:

    • TIN

    • Name Control

    • Dollar amount

    • MFT

    • Tax Period Ending

    • Control Number

    • Remarks (required entry)

    • Date, name, and employee IDRS number of preparer of Form 8765 (required entries)

    Form 8765 should have documentation attached identifying the credit as well as justifying its requested application through correspondence, research performed, etc. If Form 8765 is received without this documentation or without proper completion of all required entries, the Form 8765 will be returned to the requestor immediately. If required by another IRM, ensure all specific documentation on credits of $100,000 or more are recorded on, or attached to, the Form 8765 (i.e. research for finding phone numbers, phone call attempts, managerial approval, or RTR prints).

  3. For additional information on Form 8765 see IRM 3.17.10.3, Unidentified Remittance File (URF), and IRM 3.17.220, Excess Collections File.

  4. For statute expired/imminent periods, see IRM 25.6.1.7.3.3(4), Transferring Credits From the XSF.

21.5.7.4.4.3  (10-01-2003)
Form 3809, Miscellaneous Adjustment Voucher

  1. Only HPTF will prepare Form 3809, Miscellaneous Adjustment Voucher, for a TC 760, Substantiated Credit Payment Allowance, to:

    • Allow and reverse tentative substantiated credit from Account 6570

    • Allow a credit from Account 7650, Losses and Shortages

21.5.7.4.4.4  (12-19-2005)
Form 8546, Claim for Reimbursement of Bank Charges Incurred Due to Erroneous Service Levy or Misplaced Payment Check

  1. IRS may reimburse taxpayers for bank charges resulting from loss or misplacement of taxpayers’ checks during processing.

  2. Taxpayers file Form 8546, Claim for Reimbursement of Bank Charges Incurred Due to Erroneous Service Levy or Misplaced Payment Check, in this situation.

    If Then
    Taxpayer requests a reimbursement of bank charges Send taxpayer a Form 8546 with taxpayer's service center Accounting return address.
    Taxpayer submits Form 8546 Send Form 8546 to Accounting.

21.5.7.4.4.5  (10-01-2010)
Delays in Processing Federal Tax Deposits (FTD)

  1. Follow procedures inIRM 20.1.4.24.2, Misdated Deposits.

21.5.7.4.5  (10-01-2010)
Letters and Notices

  1. Notify taxpayer when the payment has been located using:

    • 672C Letter, Payment(s) Located and/or Applied

    • CP 62, Notice of Credit Transfer, IMF notice generated when credits are transferred

    • CP 225, Missing Payment Applied, BMF notice generated when credits are transferred

  2. To request additional information from the taxpayer, use a 167C Letter, Payment Missing; Copy of check/Money Order/Cashiers Check.

  3. To notify the taxpayer that the payment tracer case is being transferred to another office, use an 86C Letter. See IRM 21.3.3.4.2.1, Use of 86C Letter - Referring Taxpayer Inquire/Forms to another Office.

21.5.7.4.6  (10-01-2003)
Processing Complex Payment Tracers

  1. The following subsections identify complex payment tracer cases and actions to take to locate the payments.

21.5.7.4.6.1  (12-30-2010)
Encoding Errors and Piggy-Back Checks

  1. Encoding errors occur when a check is encoded for a different amount than the amount for which the check was written. Improper handling of remittances causes a discrepancy between the records of the depository bank and the campus.

  2. Piggy-back checks are two checks attached that are run through the encoding machine as one. The front check is encoded on the face only. The second check is endorsed on the back only.

  3. The taxpayer's IRS account is credited for the amount of the first check. The taxpayer's bank account is debited for the total of both checks. The checks may or may not be from the same taxpayer.

  4. Contact the taxpayer for a copy of the bank statement for two months, the month showing the amount deducted from the account, plus the following month. Follow e-4442/Form 4442, Inquiry Referral, procedures for required information if the information is not received by end of day, see IRM 21.3.5.4.2, How to Prepare a Referral. If the taxpayer submits a check for the difference, when they send a copy of the bank statement, close the case. Process the subsequent payment with the original received date.

    If Then
    Taxpayers account was not fully debited Advise taxpayer to send a payment for the difference
    Taxpayer’s account was fully debited Forward Form 4446 to HPTF. Follow procedures in IRM 21.5.7.4.2, Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF).

  5. If the encoding error is on a money order, advise the taxpayer to contact the vendor for a photocopy of the front and back of the money order.

    IF Then
    The money order was cashed and the venders account was debited for an incorrect amount (less than the amount of the money order) Advise the caller to obtain the balance from the vendor and send a payment for the difference.
    The money order was cashed, the vendors account was debited for the correct amount, but the module credited for an incorrect amount Advise the caller to fax in a copy of the front and back of the money order and prepare a Form 4446 and forward to HPTF. Follow procedures in IRM 21.5.7.4.2, Payment Tracer Referrals to Hardcore Payment Tracer Function (HPTF).

  6. A returned refund check will post as TC 841 if the deposit discrepancy or encoding error resulted in a refund.

    If And Then
    Credit did not belong to the taxpayer Payment is less than 1 year old Transfer payment to Account 4620, Unidentified Remittance File (URF) with Form 2424, Account Adjustment Voucher. See Exhibit 3.11.10-19, Form 2424, Account Adjustment Voucher, for more information.
    Credit did not belong to the taxpayer Payment is 1 year old or more Transfer payment to Account 6800, Excess Collection File (XSF) with Form 8758, Excess Collections File Addition. See IRM 3.17.220.2.1.1, Preparation of Form 8758, for more information.

  7. Research the following:

    1. Account 4620, Unidentified Remittances File (URF), using CC URINQ for payments encoded for less than the amount of the check, and the payments are less than one year old.

    2. Account 6800, Excess Collections File (XSF), using CC XSINQ for payments encoded for less than the amount of the check, and over one year old.

  8. For additional information on transferring payments to or moving payments from the URF or XSF file, see IRM 21.5.7.4.4.2, Form 8765, IDRS Control File Credit Application, IRM 3.17.10.3, Unidentified Remittance File (URF), and IRM 3.17.220, Excess Collection File.

  9. If you cannot locate the payment, refer the case to HPTF with the following documentation attached:

    • Copy of the remittance(s)

    • IDRS print of the tax module

    • Taxpayer’s bank statements

    • Any other related documents

  10. HPTF will perform research and contact the bank for the credit.

21.5.7.4.6.2  (10-01-2003)
Mixed/Slipped Blocks

  1. A mixed or slipped block condition is created if the payment documents and the Remittance Processing System (RPS) printing are out of sequence. The RPS 813 is usually correct, but the DLN and the money amount printed on the remittance and supporting documents are for the preceding taxpayer. This condition can occur at any point in the block and continue through the end of the block.

  2. If the payment DLN indicates a missing payment posted to the account of an unrelated taxpayer:

    • Request the entire block

    • Research at least five accounts before and five accounts after the taxpayer's account

    Note:

    For ISRP/RRPS blocks, see IRM 21.5.7.4.7.1, ISRP/RRPS. Do not request the entire block if the payment can be researched on RTR.

21.5.7.4.6.3  (10-01-2003)
Multiple/Split Remittances

  1. Multiple remittance is two or more checks received with one return/document or received for one tax period. "M" is annotated in the upper left margin of the document and remittance. The number of checks follows the " M" (e.g., M3 = 3 checks, 1 return).

  2. Split remittances is one check received for more than one return/document or for more than one tax period. "S" is annotated in the upper left margin of each document and remittance. The number of returns and/or periods follows the "S" (e.g., S2 = 2 returns, 1 check).

    Note:

    Lockbox processing will show the serial numbers on the checks. Some checks are printed with the DLN(s) of the returns.

  3. Using the date of the payment, research:

    • CC IMFOL/BMFOL

    • CC SUMRY/TXMOD/MFTRA

      If Then
      Total payments do not equal the multiple or split remittance

      1. Request a copy of the front and back of the check from the taxpayer, if not already provided.

      2. Request the block using CC ESTAB. For ISRP/RRPS payment, see below.
      You cannot locate the payment(s) with a copy of the check or block and all preliminary research has been completed Prepare Form 4446 and send the case to HPTF at the campus that processed the payment or processed the most recent payments if unable to determine who processed the missing payment.

  4. ISRP/RRPS MULTIPLE REMITTANCES: Inputting the DLN from the back of the check using the ESTAB command code will allow you to secure the electronic voucher and all related checks of the multiple.

  5. ISRP/RRPS SPLIT REMITTANCES: If you request the DLN from the back of the check using the CC ESTAB, you will only receive the last electronic voucher input. To secure all related vouchers from the split, the Remittance Processing System Identification (RPSID) number must be searched. For more information on ISRP/RRPS payments, see IRM 21.5.7.4.7.1, ISRP/RRPS.

    Example:

    If the remittance was applied to three accounts, research two RPSID and sequence numbers before and after the one on the check.

  6. HPTF will request the encoding tapes to compare the money amounts on Document 813 and validate the amount. If the tapes are unavailable, they will request copies of the check from the depository.

21.5.7.4.6.4  (10-01-2007)
Refund Check to Be Applied as a Payment

  1. Taxpayers sometimes return refund checks to be applied as payments. A TC 841 must be on the tax module with a prior TC 840 or TC 846. These payments will be credited when the Service receives the refund check from the taxpayer.

    If And Then
    Credit was applied to incorrect module   Follow procedures in IRM 21.4.3.4.1, Checks Returned to Regional Financial Center (RFC) by the Taxpayer or U.S. Postal Service.
    Credit was applied to incorrect taxpayer's account A refund was issued Follow erroneous refund procedures in IRM 21.4.5, Erroneous Refunds.
    Credit was not applied   Refer case to the Campus Accounts Management Refund Inquiry Unit.

21.5.7.4.6.5  (10-01-2012)
Payment Located and Not Available for Transfer

  1. If the taxpayer's payments are applied to an incorrect tax period, transfer the payment to the correct module if the credit is still available (refund not issued).

    If Then
    Payment has been refunded Follow procedures in IRM 21.4.5, Erroneous Refunds.
    Payment will be refunded within 3 cycles (including "Q" freeze expirations) Input a refund deletion request (CC NOREF). Monitor the account and transfer credit after TC 841 posts.

    Note:

    For IMF accounts, refer to IRM 21.4.1.4.10, Refund Intercept CC NOREF, for instructions on intercepting refunds. For BMF accounts CC NOREF must be input by Friday morning in the same cycle as the TC 846.

  2. If the payment was applied to satisfy another tax liability take the following actions:

    If Then
    The taxpayer requests the payment be transferred

    • Inform the taxpayer that more interest and/or penalty may be due on the debited module.

      Note:

      If necessary, send the taxpayer a transcript indicating where the payment was applied to satisfy another tax liability.

    • After transferring the payment, tell the taxpayer how the payment was applied.

    • Request the taxpayer pay the additional interest and penalty due on the debited module.
    The Refund Statute Expiration Date (RSED) has expired, do not transfer or refund Follow procedures in IRM 25.6, Statute of Limitations.
    The payment posted to an account and created a credit status less than the payment Transfer the payment, and notify taxpayer of the balance due.

21.5.7.4.6.6  (10-01-2003)
Payment Applied to a Different Taxpayer’s Account/TIN

  1. If the taxpayer's payment has been applied to an incorrect account:

    • Transfer the credit to the correct account. CP 60, Credit Reversal Adjustment Notice, Individual Master File (IMF) or CP 260, Credit Reversal Adjustment, Business Master File (BMF), generates automatically notifying the incorrect taxpayer of a balance due of more than ≡ ≡ ≡ ≡ ≡

    • Follow category D Erroneous Refund procedures if misapplied payment caused an erroneous refund. See IRM 21.4.5, Erroneous Refunds

  2. When IMF payments are found under the secondary taxpayer's SSN on a joint return:

    • Input a credit transfer to the correct account(s)

    • Notify taxpayers of the correct SSN for future use

    • Review primary account and adjust any restricted penalties and/or interest

21.5.7.4.6.7  (10-01-2012)
Payment Applied, Account Not Fully Satisfied

  1. Input CC INTST to obtain the new balance due with accrued penalties and interest if the payment does not fully pay the account. See IRM 5.19.1.5.2, Can Full Pay Balance Due Now (Payoff), or IRM 21.3.12.4, Determine the Earliest The Taxpayer Can Full Pay, to compute the payoff.

    Note:

    If the taxpayer is in installment agreement status and defaulted because the payment had been misapplied, reinstate the installment if appropriate. Refer to instructions in IRM 5.19.1.5.5.21, Revise/Reinstatement of Installment Agreements.

  2. Advise taxpayer of the current balance due.

  3. Release TC 470 or enter appropriate STAUP, if applicable.


Next

More Internal Revenue Manual