3.17.5. Hardcore Payment Tracers

(1) Purpose of Program: This IRM provides instructions to be followed by the Submission Processing Hardcore Payment Tracer Functions (HPTF) for the resolution of taxpayers’ missing or misapplied payments.

(2) Audience: All employees within the Accounting Operation areas at each of the 3 Submission Processing campuses who work Hardcore Payment Tracer cases.

(3) Policy Owner: The Accounting Services Section is part of the Accounting and Tax Payment Branch in Submission Processing under the Wage and Investment Business Operating Division Customer Account Services.

(4) Program Owner: Wage and Investment (W&I) division, Submission Processing (SP) is responsible for policy for researching hardcore payment tracers.

(5) Primary Stakeholders: The primary stakeholders are Management Officials who rely on accurate data, reports and quality information to ensure there are no gaps in efficiencies.

(6) Program Goals: To identify missing or misapplied payments using specialized Hardcore payment tracer techniques. Preliminary Payment Tracer guidance can be found in IRM 21.5.7, Account Resolution - Payment Tracers.

(1) This section provides procedures for resolving Hardcore Payment Tracer (HCPT) cases. All functions within IRS are required to work the initial phases of a payment tracer case. Cases should be referred to the Hardcore Payment Tracer Function (HPTF) for additional research only after all initial research efforts have been exhausted - See IRM 21.5.7, Payment Tracers for initial research procedures.

(2) It is important to resolve missing payment cases as expeditiously as possible because payments not applied to the proper tax module may result in erroneous notices or erroneous refunds and undue burden for taxpayers.

(3) Taxpayers may initiate steps to resolve missing/misapplied payment issues through the Integrated Customer Communications Environment (ICCE) formerly referred to as Telephone Routing Interactive System (TRIS), written correspondence, telephone contact with a Customer Service Representative (CSR), Taxpayer Resolution Representative (TRR), Taxpayer Advocate Service (TAS), or a Taxpayer Assistance Center (TAC) visit.

(4) All customer service representatives, including Automated Collection System (ACS), Campus Collection Operations, and TAC are responsible for researching and, if possible, resolving payment tracer inquiries. If resolution is still not possible following initial research procedures, the cases will be referred to HPTF.

(1) Always exercise special precautions to protect taxpayers' accounts. Per the Taxpayer Bill of Rights (TBOR), taxpayers have the right to expect that any information they provide to the IRS will not be disclosed unless authorized by the taxpayer or by law. Taxpayers have the right to expect appropriate action will be taken against employees, return preparers, and others who wrongfully use or disclose taxpayer return information and; Taxpayers have the right to expect that any IRS inquiry, examination, or enforcement action will comply with the law and be no more intrusive than necessary, and will respect all due process rights, including search and seizure protections and will provide, where applicable, a collection due process hearing. See Taxpayer Bill of Rights (sharepoint.com) for more information.

(2) Before disclosing any tax information:

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

2. Review procedures in IRM 11.3.2.7.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.14, Facsimile (FAX), Electronic Facsimile (E-FAX), and IRS Internal Enterprise Electronic Facsimile (EEFAX) Transmission of Tax Information before faxing confidential information to the taxpayer.

(3) If the caller is unable to furnish enough information for you to establish that he/she actually is the taxpayer, request the caller to find out the information and call back. If the caller states he/she does not have the information and cannot obtain it, advise the caller to provide written documentation.

(4) Do not provide information concerning the taxpayer to third parties without written authorization from the taxpayer, even though the third party requesting the information has possession of a copy of the bill or notice in question.

(1) The CADE 2 program deployed the first transition state towards the goal to implement a single modernized environment to process individual taxpayer accounts.

(2) The components of CADE 2 Transition State 1 include:

1. Daily Processing: Individual Master File (IMF) processing with the new cycle definition outlined below but processing daily (daily transactions to daily accounts) with weekly processing occurring on Thursday.

i. New Cycles:

1. SP site(s) Cycle: Thursday - Wednesday

2. Master File Processing: Friday - Thursday

   Note: New Cycles are applicable to all SP site(s) and master files. The CADE Master File, as it existed from 2004 - 2011, will be retired.

ii. Refunds for IMF accounts will be accelerated to provide refunds to taxpayers faster.

1. Direct deposit refunds will be issued 4 business days from posting.

2. Paper check refunds will be issued 6 business days from posting.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2. CADE 2 database: To establish a taxpayer account database that will house all individual taxpayer accounts. IMF will process all transactions, settle accounts, and provide data to the CADE 2 database. IMF will remain the system of record for Transition State 1. The CADE 2 database will provide data to the Integrated Data Retrieval System (IDRS) and the Integration Production Model (IPM) programs.

3. Accelerated IDRS/Taxpayer Information File (TIF) Updates: The weekend IDRS/TIF analysis and updates will occur the immediate Saturday after Master File processing completes on Thursday. This will result in a faster posting of transactions on IDRS.

(3) Individual taxpayer accounts will be analyzed three times a year to determine whether the account at that point in time meets criteria to be marked as a Daily account.

(4) Command Codes IMFOL and TXMOD will contain an indicator on the screen to identify whether the account is a Daily account or a Weekly account.

(5) Incoming weekly transactions directed to an account that is marked as Daily will result in the account changing from Daily to Weekly when the transaction posts.

(6) Individual Master File (IMF) transaction posting time frames are outlined as follows

1. Daily transactions directed to a daily account: are expected to post daily with daily processing. Transactions will be viewable using CFOL Command Codes the second day after SP site(s) input. Transactions will be viewable on IDRS Command Codes the third day after SP site(s) input.

2. Weekly transactions directed to a daily account: are expected to post with the weekly processing run on Thursday and may result in the account type changing to Weekly.

3. Daily and Weekly transactions directed to a Weekly account: are expected to post with the weekly processing on Thursday.

   Note: For items b) and c) above, with the acceleration of the IDRS weekly analysis being performed the weekend directly after the Master File processing on Thursday, transactions will be posted instead of in pending status on Monday.

4. Use of the Posting Delay Code on transactions: will result in the transaction being held until the weekly processing on Thursday. When the transaction is processed on Thursday and the Posting Delay Code contains a value other than zero, the transaction will continue to re-sequence for the number of cycles equal to the value. Example: A transaction input with a Posting Delay Code of 1 will be processed on Thursday and will re-sequence until the following weekly processing day (the following Thursday).

Note: Use of the Posting Delay Code on a daily account with daily transactions may result in delaying the posting of the transactions that would resolve the account.

(7) Business Master File (BMF) transaction posting time frames are outlined as follows:

1. Transactions will be viewable using CFOL Command Codes on Saturday following the weekly Master File processing run on Thursday.

2. Transactions will be viewable as posted transactions using IDRS Command Codes on Monday following the weekly Master File processing run on Thursday.

   Note: With the acceleration of the IDRS weekly analysis being performed the weekend directly after the Master File processing on Thursday, transactions will be posted instead of in pending status on Monday.

(1) Hardcore payment tracer research is the process used to locate taxpayers' missing or misapplied payments. A payment tracer case is not resolved until either the missing or misapplied payment is correctly applied to the taxpayer's account or the issue has been resolved (satisfied, e.g., “made whole”) following internal guidelines.

(2) All functions work the initial phases of a payment tracer case (See IRM 21.5.7, Payment Tracers for initial research procedures).

(3) To avoid rejects/delays, all areas must follow procedures in IRM 3.17.5.6, Referrals to Hardcore Payment Tracer Function (HCPT) for the correct way to prepare and submit referrals to the HPTF.

(4) Before conducting research to locate the payment, determine if it has been at least 3 days (if payment sent electronically) or 2 weeks, since the taxpayer mailed their payment. If not, ask the taxpayer to call back at that time. If it has been at least 3 days (if payment sent electronically) or 2 weeks, obtain the following information as applicable:

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

• Date the payment cleared

• Taxpayer's name and address

• Taxpayer Identification Number (TIN)

• Date of the payment

• Amount of the payment

• Tax period the payment was intended for

• How was payment made/Means of payment submission (e.g., was it submitted by check, money order, electronic/bank submission, etc.)

• Where the payment was sent

• Type of payment

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

• Electronic Federal Tax Payment System (EFTPS) 15-digit EFT number, if applicable

• Routing number for the financial institution that the payment was made from (e.g., bank the check drawn on or electronic payment made out of)

• Credit Card Payment, confirmation number

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

(6) Information and research will vary depending on the type of payment being researched.

(1) If other functions within IRS cannot locate the missing payment after researching online IDRS or reviewing information from the taxpayer/bank per IRM 21.5.7, Payment Tracers, they will prepare Form 4446, Payment Tracer Research Record documenting all research efforts and refer the case to the HPTF at the SP site that processed the payment or to the SP site that processed the most recent payments (if unable to determine for sure which SP site(s) processed the missing payment).

(2) HPTF may also transfer cases to other SP site HPTF, if applicable.

(3) Due to the various service center consolidations, the following exceptions to (1) above apply.

(4) HPTF is usually located in the Accounting Services/Control Operation and is responsible for working complex payment tracer cases after all preliminary research has been exhausted per IRM 21.5.7, Payment Tracers.

(5) Preliminary research will expedite the resolution process. Preliminary research prior to referral to HPTF includes:

• Corresponding with the taxpayer and/or obtaining source documents internally/externally

• Researching IDRS, CFOL, Non-Master File, Unidentified & Excess Collection files, Unpostables, and EFTPS

• Using the telephone to contact the taxpayer and fax machine to obtain additional information needed to resolve the case

• Sending the appropriate "C letter" if unable to reach the taxpayer via telephone (at least two attempts)

(6) Other functions referring a case to HPTF should indicate on Form 4446, Payment Tracer Research Record:

• Use of the Integrated Automation Technologies (IAT) Payment Tracer tool.

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

• RTR, EFTPS, and Unpostable research, if applicable.

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

(7) HPTF will review Form 4446 to ensure that necessary research and documentation was adhered to before accepting the payment tracer case. See revised FTD preliminary research procedures in IRM 3.17.5.20, Federal Tax Deposits (FTD).

(8) HPTF will return any incomplete case through the HPTF unit manager with a detailed explanation of the corrective action required. HPTF will also notate on the reject sheet the stop number and/or team number (if available) of the person they are sending the case back to in order to ensure that it gets back to the right person.

(9) 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)

• Treasury Bonds after IDRS research

• Unpostable codes 140 or 399

• Field office payments without a field office or Residual Remittance Processing System (RRPS) endorsement

• Closed unpostable cases

• Slipped/Mixed entity or block conditions involving more than three (3) taxpayers' accounts

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

• Reject transactions

• Electronic payments not located through specified research

• Department of Justice (DOJ) endorsed payments

  Note: Refer DOJ missing payment cases to the Kansas City HPTF:

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

• "Free" Items

Note: Dishonored checks should only be sent to the HPTF if there is proof that the check was cashed.

(10) If a refund should be issued, HPTF will apply the tentative substantiated credit, including received date and amount indicated on the proof of payment, within 10 workdays of receipt in HPTF.

(11) HPTF is responsible for all subsequent communication with the taxpayer after accepting the case.

(1) The following subsections identify complex payment tracer cases and actions to locate the missing or misapplied payments.

(1) The following section provides procedures for creating a substantiated credit in cases where documentation is not available for normal processing. This allows for case resolution even if HPTF determines that necessary documentation has been lost or destroyed.

(2) HPTF will continue searching for the payment until it is determined documentation needed to locate the missing payment was destroyed or cannot be located. If a careful determination has been made that the documentation was destroyed or cannot be located, use the following key elements to create a substantiated credit:

• absolute Proof of Payment

• authorization

• transfer of funds from Account 6570, using Form 3809 with TC 760, substantiated credit code

(3) A substantiated credit MUST be allowed if the missing payment is not located within 120 calendar days of receipt by HPTF. Cases accepted in HPTF will be controlled in "M" status on IDRS until the case is resolved.

(4) If the missing or misapplied payment is located after the substantiated credit was allowed, return the funds to Account 6570 via Form 3809, Miscellaneous Adjustment Voucher.

(1) Absolute proof of payment is conclusive evidence that IRS received a payment and this includes:

• Cash receipts (Form 809 or IRS National Cash Register (NCR) receipts)

• Cancelled checks

• Negotiated money orders

• Negotiated cashier’s checks

• Narrative descriptions of endorsements by banks, money order vendors, and IRS employees (e.g., Revenue Officers)

(2) National Cash Register (NCR) receipts must identify the register number, time, date, office location, and type and amount of tax paid.

(3) Absolute proof that a Federal Tax Deposit (FTD) was made is the verification or acknowledgment of a payment submitted to a commercial or Federal Reserve Bank. This proof can be:

1. A cancelled check for the amount of the payment made payable to and negotiated by a commercial depository or a Federal Reserve Bank. Have the bank verify that the credit was deposited into the Treasury Tax Loan Account (TT&L).

2. A commercial bank or FTD receipt for the amount of payment.

3. A photocopy of the FTD coupon received in the FTD processing SP site(s).

4. A transmittal showing the deposit in question was received and processed without adjustment. If an adjustment was made, verify that the deposit was not included.

(1) Cases prepared for substantiation must be reviewed and Form 3809 initialed by the Team Lead and Manager before submitting to the Operations Manager. They must verify the substantiation package includes:

1. All documented research

2. Form 3809 has TC 760: and

3. The correct TIN, money amount, tax period, MFT: and

4. Form 3809 numbered with document code 48.

(2) The Accounting Control/Services Operations Manager must review and approve substantiated payment credits after all research has been exhausted and the payment cannot be located.

(3) Case will remain in controlled “M” status on IDRS until the TC 760 post.

(4) Consider all research to have been exhausted seven (7) years from the receipt date by HPTF.

(1) The following systems/methods are used for submitting or processing payments:

• Automated Non-Master (ANMF) File payments,

• Cash Payments,

• Cashier's Check,

• Direct Debit Installment Agreements,

• Electronic Federal Tax Payment System (EFTPS) Payments,

• Electronic Funds Withdrawal (Direct Debit) and Credit Cards,

• Federal Tax Deposit (FTD) Payments,

• Field Office Remittances,

• Foreign Remittances,

• Free Items,

• Installment Agreement User Fee Lockbox Payments,

• Integrated Submission and Remittance Processing System/Residual Remittance Processing System (ISRP/RRPS),

• Justice Department Lockbox Receipts,

• Lloyd's of London Taxpayers,

• Lockbox Payments,

• Manual Deposits,

• Money Orders,

• State Income Tax Levy Program (SITLP),

• Treasury Bonds,

• and Truncated Checks.

(1) ISRP and the RRPS convert paper tax, information documents and remittances received by IRS into perfected electronic records of taxpayer data. When IRS receives a tax document, it is opened and sorted by form type (e.g., Form 1040, Form 1120, etc.). Remittances with their accompanying documentation are pre-sorted into groups called batches. Each batch is uniquely identified by a 12-digit RPSID number. This number always begins with "00", followed by 6 digits, followed by "0000." This system will capture, store, retrieve, archive (vouchers and check images) and route source data to downstream processing activities which subsequently post to taxpayers' accounts on Master File.

(2) Information stored in the archive system includes the following:

1. The actual front image of a paper voucher or an image created from data that an ISRP operator entered when no voucher was present.

2. Actual images of both sides of the check. The file on the back of the check contains the endorsement and encoding information.

3. Data used to research for each voucher and related check, such as the TIN, DLN and date of deposit.

4. The archive system permits the retrieval of document images and data for up to five (5) years after the information has been processed through the remittance system.

Note: Document 6209, IRS Processing Codes and Information, Section 4, provides exhibits of the RRPS Electronic Payment Voucher, endorsement data, and the IRS audit trail.

(3) When the remittances (checks, money orders, etc.) are processed through RRPS:

• te remittance amount is encoded at the bottom right front of the remittance

• Effective with the deployment of ISRP electronic check processing through OTCnet, payment application information is not displayed on the reverse of a check image on OTCnet. You must research payment application on the Remittance Transaction Register (RTR) System by the Trace ID. The Federal Reserve Bank masks personally identifiable information on OTCnet.

• the U.S. Treasury endorsement is stamped on the back of the remittance

(4) In order to resolve missing payments, you may need to research the ISRP Archival Retrieval System or RTR. Fax Form 11357, Integrated Submission and Remittance Processing Image Retrieval Request to the SP site(s) that processed the payment. See the ISRP Archive Contact List, located on SERP under the Who/Where tab, for a list of contacts for each SP site(s) (http://serp.enterprise.irs.gov/databases/who-where.dr/isrp-archive-contacts.html).

(5) This process will scan "scannable" vouchers and checks and assign a DLN. Returns with payments will no longer have a Document Locator Number (DLN) that matches the payment DLN. The inflated Julian date associated with the deposit item previously processed through RPS will no longer appear on taxpayers' accounts.

(6) The ISRP/RRPS audit trail is different from the RPS audit trail. It will reflect the following:

• The tax period and transaction date are on the second line.

• The identifying information for a payment other than Master File, such as a photocopy payment, will also be displayed on the second line. The symbols will be the last 7 to 9 digits. For example, 20X0903. See IRM 3.8.44, Campus Deposit Activity for additional information.

• If the payment is a multiple or split payment, an M or S will appear between the tax period and the transaction date.

(7) The following is a comparison of the RPS/ISRP DLN:

(8) Functions that cannot locate the payment should follow Payment Tracer procedures outlined in IRM 21.5.7, Payment Tracers for ISRP payments prior to initiating the following actions:

1. If you have a copy of the front and back of the cancelled check and cannot find the payment through preliminary research. Complete Form 4446and enter the appropriate STAUP and TC 470 to hold the notices. The case must be transferred to HPTF. Send Letter 86C, Referring Taxpayer Inquiry/Forms to Another Office, if appropriate. See 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.

2. If you have a "slipped block" request the five (5) documents before and after your payment, if RTR is not available. If more than three (3) payments have been misapplied, prepare Form 4446, Payment Tracer Research Record when appropriate send Letter 86C, Referring Taxpayer Inquiry/Forms to Another Office. Enter the appropriate STAUP and TC 470 to hold the notices. The case must be transferred to HPTF. If three (3) payments or less have been misapplied, the customer service representative (CSR) should resolve the issue and have the payments applied to the correct accounts.

(1) The Field Office Payment Processing Program involves processing paper remittances received in field offices and the issuance, tracking, and processing of Form 809, Receipt for Payment of Taxes. Form 809 processing includes field offices and SP site(s). IRS requires strict control of official receipts, taxpayer information and payments to ensure the highest integrity and public trust.

(2) Form 809 must be handled with the same care and precision as cash. Field offices are required to use overnight traceable services or other traceable approved methods for transshipping remittances and tax receipts to their designated Submission Processing SP site(s) (See IRM 3.8.47.5.1, Receiving Field Office Receipts for additional information). Cash remittances must be converted to a check or money order before sending for processing.

(3) Field office employees issue taxpayers a Form 809, Receipt for Payment of Taxes when they receive cash as payment, and a receipt when the payment is by check, money order, etc.

(4) When field office employees issue Form 809, Receipt for Payment of Taxes, it becomes a posting document.

(5) The case will be transferred or reassigned to the HPTF SP site(s) that processed the remittance via Form 4446, Payment Tracer Research Record if the payment cannot be located after all appropriate preliminary research has been completed.

(6) Field office employees will send Form 3210, Document Transmittal with documents in a separate envelope sealed by the originator within the required overnight mail package.

(7) HPTF will acknowledge receipt of Form 3210, Document Transmittal and its contents via overnight traceable services. Include pertinent data such as: the taxpayer's TIN, name control, and date of the form.

(1) The Lockbox operation involves the processing of tax payments by commercial banks. This method of processing payments accelerates the handling and depositing of funds received. The payments are forwarded to the Department of Treasury.

(2) Lockbox banks process payments for the following Individual Master File (IMF) products:

• Form 1040-ES, Estimated Tax for Individuals

• Form 1040, U.S. Income Tax Return

• Form 1040A, U.S. Income Tax Return

• Form 1040EZ, U.S. Income Tax Return for Single and Joint Filers With No Dependents

• Form 1040X, Amended U.S. Individual Income Tax Return

• Form 1040, International, will now be processed for Austin SPC

• Form 1040NR, U.S. Nonresident Alien Income Tax Return

• Form 1040-PR, Self-Employment Tax Return - Puerto Rico (In Spanish)

• Form 1040-SS, U.S. Self-Employment Tax Return (Including the Additional Child Tax Credit for Bona Fide Residents of Puerto Rico)

• Form 4868, Application for Automatic Extension of Time to File U.S. Individual Income Tax Return

• CP 521, Installment Agreement Reminder Notice

• CP 523, Installment Agreement Default Notice

• Form 2159, Payroll Deduction Agreement

• Form 433-D, Installment Agreement

• Form 8892, Application for Automatic Extension of Time to File Form 709 and/or Payment of Gift/Generation-Skipping Transfer Tax

• Form 9465, Installment Agreements Requests

• Letter 3641, Third Party Lien Payoff (Escrow or Financial Institution)

• Letter 3856, Monthly Reminder for Installment Agreement Payments

• Letter 3856-A, Monthly Reminder for Installment Agreement Payments for Joint Liabilities

(3) Lockbox banks process payments for the following Business Master File (BMF) products:

• Form 1041-ES, Estimated Income Tax for Estates and Trusts

• Form 940 and Form 940-EZ, Employer's Annual Federal Unemployment (FUTA) Tax Return

• Form 941, Employer’s Quarterly Federal Tax Return

• Form 943, Employer’s Annual Tax for Agricultural Employees Return

• Form 944, Employer’s Annual Federal Tax Return

• Form 945, Annual Return of Withheld Federal Income Tax

• Form 2290, Heavy Highway Vehicle Use Tax Return

• CP 521, Installment Agreement Reminder Notice

• CP 523, Installment Agreement Default Notice

• Form 2159, Payroll Deduction Agreement

• Form 433-D, Direct Debit Installment Agreements

• Form 9465, Installment Agreement Request

• Letter 3641, Third Party Lien Payoff (Escrow or Financial Institution)

• Letter 3856 (CG), Monthly Reminder for Installment Agreement Payments

• Letter 3856-A (CG), Monthly Reminder for Installment Agreement Payments for Joint Liabilities

(4) Taxpayers mail remittances to the IRS at designated post office boxes for each form type. These addresses can be found on the forms listed in (2) and (3) above.

(5) The bank encodes and endorses the checks. The DLN, TIN, name control, received date, and tax period are printed on the back of the check.

(6) The Lockbox system generates an Optical Character Recognition (OCR) Remittance Register, similar to the 813 Remittance Register.

(7) The DLN consists of a File Location Code (FLC) which are the first two digits in the DLN. This is unique to Lockbox processing. Use this number with the bank endorsement to determine the correct SP site(s) to research.

(8) All Lockbox banks image checks, money orders, and vouchers can be viewed via RTR.

1. If you need a copy of a check and the payment DLN has a list year of 4 (last digit of the DLN) or subsequent, research RTR to retrieve the check image.

2. If you need a copy of a check and the payment DLN has a list year of 3 (last digit of the DLN) or prior, research the DLN through the RTR application. If payment is not available on RTR, refer to IRM 3.17.5.7, Processing Complex Payment Tracer Cases.

(1) These receipts result from court actions and IRS referrals to the Department of Justice (DOJ) for collection. The Kansas City Submission Processing site receives Standard Form 1081, Voucher and Schedule of Withdrawals and Credits, as notification of tax revenue secured by the DOJ.

(2) If a taxpayer's cancelled check shows a DOJ endorsement:

1. Transfer the case to the Kansas City HCPT.

2. Issue Letter 86C to notify taxpayer the inquiry was transferred to the Kansas City Submission Processing SP.

3. Delay notices as appropriate.

(3) Prepare Form 3210, Document Transmittal to include:

(4) Internal Revenue Service, Attn: P-6 Mail Stop 6250, HCPT, 333 W. Pershing Rd., Kansas City, MO 64108

(5) Also include:

• The taxpayer's name, TIN, and tax period

• TC 470 or CC STAUP input

• The date Letter 86C was sent

(6) HPTF will coordinate the resolution with Accounting personnel in accordance with IRM 3.17.10, Dishonored Check File (DCF) and Unidentified Remittance File (URF).

(1) Field/Area Offices issue Form 809 or a cash register receipt to taxpayers for cash payments.

(2) The tax return is validated at the time of receipt showing the amount and type of tax paid.

(3) The Field/Area Office prepares Form 783, Remittance Register, or Form 795, Daily Report of Collection Activity, to list the payments. These forms are sent to the Submission Processing site. HPTF should contact their Service Center Teller Unit to get a copy of Form 795, Daily Report of Collection Activity by giving them the Form 809, Receipt for Payment of Taxes number provided by the taxpayer.

(4) Research IDRS, including URINQ, XSINQ and RTR if available for these remittances.

(5) If other functions are unable to locate the payment per IRM 21.5.7, Payment Tracers, they will prepare Form 4446, Payment Tracer Research Record to transfer the case to the HPTF at the SP site that processed the payment.

(6) HPTF will verify Form 813, Document Register for the payment. HPTF will contact internal security before allowing a substantiated credit from Account 6570 based on Form 809, Receipt for Payment of Taxes as proof of payment.

(1) All international or possession returns with remittances are deposited where received.

(2) As of July 1, 2007, due to SP site Consolidations:

• IMF International returns are sent to the Austin SP site,

• and BMF International returns are sent to the Ogden SP site.

(3) Remittances drawn on foreign banks payable in U.S. dollars through U.S. banks must have the U.S. bank’s routing symbol printed in the lower left corner of the check and have a nine (9) digit routing number. These are processed as regular deposits.

(4) Any foreign remittance including remittances that are payable in U. S. dollars, drawn on foreign banks, and received with tax returns or documents, that fail to meet any portion of (1) above will be processed using manual deposit guidelines. The deposits are then mailed to Citibank in Wilmington, Delaware and numbered and processed as a foreign remittance.

(5) Receipt and Control will process source documents with remittances that are payable in foreign currency and drawn on foreign banks as manual deposits. The deposits are mailed to Citibank for a money conversion report.

(6) When foreign currency is received, Receipt and Control will contact Bank of America to convert foreign currency to U. S. dollars. The tax return or document will be processed using manual deposit guidelines.

(7) Each SP site has specific deposit processing procedures. See IRM 3.8.45.26, Specific Campuses Processing for additional information.

(8) For additional information on foreign remittances, see IRM 3.8.45.15, Foreign Check Remittances.

(1) The tax due on Form 706, U.S. Estate Tax Return can be paid with redeemed Treasury Bonds (TC 678). The Bureau of Public Debt (BPD) or a Federal Reserve Bank (FRB) deposits the proceeds of the bonds to the credit of the Submission Processing SP site(s) designated on Form PD 1782, Application for Redemption at Par of United States Treasury Bonds Eligible for Payment of Federal Estate Tax.

(2) On a daily basis, the BPD will request the Philadelphia Regional Financial Office to issue U. S. Treasury checks payable to the "Director of the Internal Revenue Service for the Benefit of Estate" to the SP site responsible for the estate. Form PD 1782 is faxed to each SP site approximately seven (7) days before the Treasury check arrives.

(3) The faxed copy of the PD 1782 is used by Receipt and Control as a source document. TC 678 is input and the check is processed through RRPS.

(4) Form PD 1782 will contain the name of the decedent, decedent’s TIN, date of decedent’s death, tax due date, redemption date, and amounts.

(5) To locate the payment, research the following:

• Social Security Number followed by a "V (valid SSN on BMF)" or "W (invalid SSN on BMF)",

• NAMEI/NAMES for another SSN, IRSN, or ITIN, and

• NAMEE/NAMEB for an EIN and if an EIN is located, research in SSN format for valid and invalid segments.

  Note: The encoding is located on the back of the check near the bottom.

(6) If other functions are unable to locate the payment after following IRM 21.5.7, Payment Tracers, they will prepare Form 4446, Payment Tracer Research Record, and forward the case to the HPTF function at the SP site that processed the bond. HPTF function will continue to search for the payment. HPTF may need to research the file of Forms PD 1782 held in Accounting.

(1) If the taxpayer's cancelled check is stamped "FI", this is an indication that the bank is holding credits belonging to the taxpayer. These credits are referred to as "Free Items."

(2) If the case involves "Free Items", before referring the case to the HPTF that processed the payment, the function unable to locate the payment should obtain a current transcript of the account.

(3) Upon receipt of Form 4446, Payment Tracer Research Record HPTF will initiate action to obtain the credit from the bank.

(1) As of January 1, 2011, businesses that have a deposit requirement (such as employment tax, excise tax, and corporate income tax) were required to submit their deposits electronically. They will no longer be permitted to use Form 8109, Federal Tax Deposit Coupon and Form 8109-B, FTD Deposit Form (Over The Counter Version).

(2) Treasury Tax and Loan (TT&L), the former system used to process FTD payments, was replaced with PATAX (Paper Tax). The PATAX system consolidated FTDs into one Federal Reserve Bank (FRB). However, PATAX was decommissioned in 2011 and manual procedures are necessary for making subsequent adjustments when FTD errors occur. IRM 3.17.5.20.1, FTD Referrals to HPTF, IRM 3.17.5.20.2, FTD Discrepancies and How to Correct Them, and IRM 3.17.5.20.3, FTD Discrepancies and How to Correct Them for Remaining FTD Paper Coupons contain processing procedures due to the decommissioning of PATAX.

(3) As of January 1, 2011, duties formerly performed by the Interagency Coordinator (IAC) are being performed by the FTD Point of Contact (POC). There is an FTD POC located at the following Submission Processing SP site(s): Austin, Kansas City, and Ogden.

(1) Payments processed through EFTPS can be identified through the EFT number shown on IDRS. After taxpayer enters the information, EFTPS supplies an acknowledgment number to the taxpayer. Taxpayers should write down this number and keep it for future reference. If there is any problem with the payment, this number allows IRS to trace the payment quickly. Customer Service Representatives can construct the EFT number from taxpayer provided acknowledgment number using the following elements for payments made prior to January 1, 2004. Payments made after January 1, 2004, should be constructed using the chart in IRM 3.17.277.5.3, EFT Number.

(2) All Bulk Providers are under Bank of America (BOA) effective 7/1/2005.

(3) IDRS Command Code EFTPS is a research tool developed primarily for payment tracer purposes. The Command Code allows for research of the EFTPS data base for payment data and audit history.

(1) Direct Debit Installment Agreements (DDIA) is a Collection program. Taxpayers make arrangements to repay tax liabilities in installments via Electronic Funds Transfers.

(2) These payments post to Master File as TC 670, Document Code 18, Blocking Series 800-899.

(3) If other functions are unable to locate the payment, they will prepare Form 4446 and route the case to HPTF.

(4) HPTF will research the following computer runs that are maintained in Accounting:

• EFT 12, generates DDIA payments and posts TC 670 to the taxpayer’s accounts.

• EFT 16, creates the EFT Credit and Debit Register and IDRS assigned DLN.

• EFT 18, generates a notice to Compliance Services Collection Operation if payments fail to post properly, and posts TC 671 and TC 280 to the taxpayer’s accounts.

(1) These automated levy programs run a match of delinquent accounts on the Master File database who are eligible to be levied against:

1. AKPFD: a database of applicants that have applied for the current year dividend.

2. MTLP: a database of city/municipal tax refunds for each city/municipality that participates in MTLP.

3. SITLP: a database of state tax refunds for each state that participates in SITLP.

(2) Each program is required to send the taxpayer correspondence advising of the levy and refer any inquiries to the ACS toll-free telephone number.

(3) If other functions are unable to locate the payment after all preliminary research has been exhausted, they will prepare Form 4446, Payment Tracer Research Record and route the case to HPTF.

(4) HPTF will research TDA56, Payment Detail Report, which is maintained in Accounting. The listing is in TIN order and contains the transaction date and amount of the state refund used to offset the Federal tax liability.

(1) Missing payments related to Tax Exempt Bonds that are received with Form 8038–T, Arbitrage Rebate and Penalty in Lieu of Arbitrage Rebate are worked at the Ogden Accounts Management SP site(s) (OAMC) by the Exempt Organization Accounts Team.

(2) Form 8038-T, Arbitrage Rebate and Penalty in Lieu of Arbitrage Rebate is the only Tax Exempt Bond that is received with a remittance (with the exception of closing agreements). The remittance is identified as green-rockered money and processed as a TC 610 to the Master File.

(3) Any SP site(s) receiving Form 8038-T, Arbitrage Rebate and Penalty in Lieu of Arbitrage Rebate payment tracer cases should transship the case to OAMC, Exempt Organization Accounts Team using Form 3210, Document Transmittal. The Exempt Organization Accounts Team will follow procedures in IRM 21.7.7.5.4.3, TEB Payment Tracer Procedures to resolve the case.

(1) IRM 3.8.45.10.8, STAUP for Foreign Remittances requires Command Code (CC) STAUP to suspend collection activity on the taxpayer’s account during the conversion to U.S. Dollars.

(2) Per GAO 13-420R IRS Management Report dated May 13, 2013, input of CC STAUP must be a separate duty from payment processing and Remittance Perfection Technician's IDRS profiles restrict them from inputting CC STAUP.

(3) In order to process Foreign Remittances in a timely manner and for Receipt and Control (RCO) Branch employees to carry out their duties without jeopardizing taxpayer accounts, Accounting's Hard Core Payment Tracer (HCPT) team will perform the input of the STAUP using the procedures found in IRM 3.8.45.10.8, STAUP for Foreign Remittances (See IPU 14U1589 dated 11/13/2014).