Part 25. Special Topics
Chapter 25. Revenue Protection
Section 8. Revenue Protection External Lead Procedures
25.25.8 Revenue Protection External Lead Procedures
Manual Transmittal
November 16, 2023
Purpose
(1) This transmits revised IRM 25.25.8, Revenue Protection External Lead Procedures.
Material Changes
(1) IRM 25.25.8.1.7(3) - Added instructions to re-emphasize the importance of timely providing banks with the acknowledgement script since External Lead inventory is time sensitive. IPU 23U0728 issued 06-14-2023.
(2) IRM 25.25.8.2(1) - Rewrote this subsection to emphasize the importance of mailbox personnel reviewing the emails received daily and getting them categorized so Tax Examiners and/or Analysts can work the accounts as expeditiously as possible. IPU 23U0728 issued 06-14-2023.
(3) IRM 25.25.8.2(2) Row 6 - Added instructions for follow up emails sent to mailbox so TEs can quickly respond and therefore reduce escalations. IPU 23U0860 issued 07-31-2023.
(4) IRM 25.25.8.2(2) - Created a table that incorporated the various scenarios, notes, and responses found in paragraphs 3-7 so that Tax Examiners could identify more efficiently the appropriate action to take based on the case scenario. IPU 23U0728 issued 06-14-2023.
(5) IRM 25.25.8.2(3 -7) - Removed these paragraphs and incorporated them into IRM 25.25.8.2(2) to make it easier for the mailbox employee to identify the scenario and respond accordingly. IPU 23U0728 issued 06-14-2023.
(6) IRM 25.25.8.2.1(3) - Re-wrote sentence to include the hyperlink to the script referenced as it was not previously included and will now save time when a Tax Examiner needs to send it. IPU 23U0728 issued 06-14-2023.
(7) IRM 25.25.8.2.1(5) - Added missing instructions to updating Lead Only cases to a Completed status in the Lead Management Database. IPU 23U0952 issued 09-12-2023.
(8) IRM 25.25.8.2.2 - Clarified, per feedback from an External Lead program review, what an ACH Reversal is and the importance of addressing this type of lead as a priority since delayed response could result in a loss of revenue. IPU 23U0728 issued 06-14-2023.
(9) IRM 25.25.8.2.3 - Rewrote the definition of an altered check for clarity, and clearly identified the modifications that causes a check to be considered altered. IPU 23U0728 issued 06-14-2023.
(10) IRM 25.25.8.2.4 - Revised the paragraph to categorize the other types of inquiries sent to the mailbox and how mailbox personnel should respond. Reclamation claims and indemnification requests were added since there weren’t clear directions on how these inquiries should be worked. IPU 23U0728 issued 06-14-2023.
(11) IRM 25.25.8.2.4.1 - Added a new subsection for reclamation claim inquiries since the IRM lacked sufficient guidance for working them. IPU 23U0728 issued 06-14-2023.
(12) IRM 25.25.8.2.4.2 - Added a new subsection for Indemnification requests since the IRM previously did not provide guidance on how these should be worked. IPU 23U0728 issued 06-14-2023.
(13) IRM 25.25.8.3(5) - Rewrote the instructions to emphasize the requirement to use the EL IAT tool to complete reviews as this was causing delays in making determinations on large cases. Also, a Reminder was added to make sure controls are placed on all applicable accounts so that those who need to research them are aware that the case is assigned to the External Lead program. IPU 23U0283 issued 02-21-2023.
(14) IRM 25.25.8.3(7) - Added a Reminder to make sure it is understood that all employees are not authorized to issue indemnification letters or scripts, since this resulted in a NQRS error issued. IPU 23U0728 issued 06-14-2023.
(15) IRM 25.25.8.3(7) - Added a Note for TEs to use when an indemnification letter is not required as this information was not known when accounts were reviewed. IPU 23U0283 issued 02-21-2023.
(16) IRM 25.25.8.3(7) Row 1 - Added a condition to specify the guidance should only be applied to returns determined to be questionable so valid returns will not be delayed from being released or commingled. IPU 23U0115 issued 01-17-2023.
(17) IRM 25.25.8.3(7) Table Row 9 - The name of the script that was previously issued for leads coming from CI and SBSE was revised and so the title was updated to reflect the current title. Also, the guidance was re-written to emphasize the importance of making sure CI and SBSE personnel are copied on all communications. IPU 23U0728 issued 06-14-2023.
(18) IRM 25.25.8.3(7) Table, Row 10 - Removed the procedures pertaining to the actions required when funds are recovered and need to be processed. IPU 23U0974 issued 09-25-2023.
(19) IRM 25.25.8.3(7) Table Row 11 - Removed these procedures as they no longer complied with current procedures for Frivolous Filer program referrals involving returns claiming certain social media scheme credits. IPU 23U0974 issued 09-25-2023.
(20) IPU 23U0974 issued 09-25-2023 IRM 25.25.8.3(7) Table Row 12 - Row 12 will replace the deleted row 11. Updates were also made to remove the guidance referring to the actions to take after funds are recovered. Those procedures are covered under processing a deposit.
(21) IRM 25.25.8.3(7) Row 12 - Added a row to address procedures to comply with Frivolous Filer Program guidelines implemented for referring returns claiming the FTC on returns screened regardless of the amount claimed. IPU 23U0952 issued 09-12-2023.
(22) IRM 25.25.8.3(8) - Rewrote the paragraph to make sure TEs understand the table covers actions to take once the indemnification letter is issued, as oppose to focusing solely on the actions required after 45 days. IPU 23U0860 issued 07-31-2023.
(23) IRM 25.25.8.3(8) - Added a new paragraph to incorporate procedures that align with processing an external lead versus monitoring them. IPU 23U0728 issued 06-14-2023.
(24) IRM 25.25.8.3.1 - Revised altered check procedures to streamline steps, and to incorporate changes to BMF altered check procedures. The email address to forward altered checks to TIGTA was restricted as TIGTA advised it should not be made publicly available. IPU 23U0728 issued 06-14-2023.
(25) IRM 25.25.8.3.1(1) - Added procedures to address the gap in creating a lead number for leads involving BMF altered check cases. IPU 23U0115 issued 01-17-2023.
(26) IRM 25.25.8.3.1(3) - Revised the sentence to make sure the procedures in the table only apply to IMF altered checks versus BMF altered checks. IPU 23U0728 issued 06-14-2023.
(27) IRM 25.25.8.3.1(3) Row 3 - Added a missing requirement, that potentially could have resulted in loss revenue, to request for funds to be returned on good returns where the check was altered. IPU 23U0728 issued 06-14-2023.
(28) IRM 25.25.8.3.1(3) Row 2 - Added to the current condition, procedures to address the handling of altered checks involving prior year returns and how to get them in STARS as this was not addressed previously. IPU 23U0115 issued 01-17-2023.
(29) IRM 25.25.8.3.2(1) - Due to an error issued for requesting a questionable EIP be returned, a Note was added to advised TEs that eligibility requirements will not be considered when told the EIP check was stolen or altered. IPU 23U0860 issued 07-31-2023.
(30) IRM 25.25.8.3.3 - Consolidated and transferred from the alpha list to a table, the BMF External Lead procedures so TEs could quickly identify the actions needed to resolve the case. Also, research procedures were added to reduce the response time for requesting refunds on referrals sent to Entity Fabrication. IPU 23U0860 issued 07-31-2023.
(31) IRM 25.25.8.3.3(1) d - Revised the BMF referral procedures to align with the agreement on how BMF Entity Fabrication would like to receive the referrals. IPU 23U0283 issued 02-21-2023.
(32) IRM 25.25.8.3.3(1) - Added a reference link to direct TEs to address, if received, the altered check before proceeding with procedures for working the BMF lead. IPU 23U0115 issued 01-17-2023.
(33) IRM 25.25.8.3.3(1) - Added instructions to require a TE to do some pre-screening for fabricated entity markers to reduce the suspense time while waiting for Entity Fabrication to advise if the funds should be recovered. IPU 23U0974 issued 09-25-2023.
(34) IRM 25.25.8.3.3(1) Table - Revised the table to include instructions for researching previously identified Entity Fabricated cases, and the procedures to address them. Also, additional instructions for processing BMF leads were added to the table to comply with BMF referral procedures. IPU 23U0974 issued 09-25-2023.
(35) IRM 25.25.8.3.3(2) - Removed the paragraph and table since the procedures were revised and then added to paragraph 1 of this subsection. IPU 23U0974 issued 09-25-2023.
(36) IRM 25.25.8.3.3(2) - Created a new paragraph to streamline steps involved in processing a BMF Lead. Also, a timeframe for responding to BMF leads was added since these leads are referred to another department to determine if funds should be recovered. IPU 23U0728 issued 06-14-2023.
(37) IRM 25.25.8.4(1) - Added a table to consolidate the various Reminders and Exceptions which was causing some delays when TEs had to work certain deposits. Also, additional guidance was added to remind TEs of the importance of CMODEing to the correct service center campus as mistakes were causing transaction failures when posting payments manually. IPU 23U0728 issued 06-14-2023.
(38) IRM 25.25.8.4(1) - Added an Exception to address how to process leads involving more than 6 refunds due to the limitations of the EL IAT tool. IPU 23U0115 issued 01-17-2023.
(39) IRM 25.25.8.4(1) - Changed the attribute Note and Exception as they were not applicable for the guidance TEs needed to follow when working cases. IPU 22U1185 issued 12-13-2022.
(40) IRM 25.25.8.4.2(1) - Edited the sentence to advised that the programming issue causing the TC 720 payments to go unpostable, was fixed. Also, a note was added to remind everyone the workaround will still be used because the update only impacted payments effective cycle 202326. IPU 23U0860 issued 07-31-2023.
(41) IRM 25.25.8.4(2) - The guidance was moved to the table in IRM 25.25.8.4(1) to be worked as this scenario was more appropriate to be worked as a deposit requiring special handling. IPU 23U0728 issued 06-14-2023.
(42) IRM 25.25.8.4(7) table row 8 - Corrected the guidance for FTC claims that had TEs instructed TEs to disposition prior year returns in EFDS when they should have been manually referred. Updates were also made to row 7 and 9 to correct the disposition process status for current year returns being referred to Frivolous Filer. IPU 23U1021 issued 10-19-2023.
(43) IRM 25.25.8.4(7) Row 7-10 - Procedures for working social media scheme returns (i.e., FTC and Sick Leave Credit) were updated to comply with current procedures for Frivolous filer referrals. IPU 23U0974 issued 09-25-2023.
(44) IRM 25.25.8.4(7) Row 13 - Added missing requirement to update the Deposit Information in LMS when processing the BMF deposit. IPU 23U0860 issued 07-31-2023.
(45) IRM 25.25.8.4.2 - Changed the title to make it more specific to its purpose; monitoring payments processed versus deposit. Also due to the programming issue resulting in TC 720 payments going unpostable, stakeholder escalations, as well as monitoring deficiencies discovered during a program review, instructions were added to make sure RIVO tracks their payments to reduce some of these issues. IPU 23U0728 issued 06-14-2023.
(46) IRM 25.25.8.4.2 - Clarified the guidance provided to assure TEs are aware the focus of the subsection is to monitor for unpostable transactions and to provide procedures when identified. IPU 22U1223 issued 12-19-2022.
(47) IRM 25.25.8.4.2 - Added a new IRM subsection that now requires TEs to monitor payments submitted for posting due to an increase in External Lead payments (TC 720) going unpostable. IPU 22U1185 issued 12-13-2022.
(48) IRM 25.25.8.6(1) Table - Updated throughout the table, the IRM reference for completing the Manual Referral spreadsheet. Also added, since this was not clear, the employee responsible for changing the STARS disposition. IPU 23U0860 issued 07-31-2023.
(49) IRM 25.25.8.6(1) - Deleted the paragraph since the instructions applied more to processing a lead versus monitoring one. IPU 23U0728 issued 06-14-2023.
(50) IRM 25.25.8.7(2) - Added a statement to emphasize that CSRs should not be initiating a trace for a lost or stolen refund when the account has External Lead involvement since this action can negatively impact banks and our ability to protect revenue. IPU 23U0974 issued 09-25-2023.
(51) IRM 25.25.8.7(2) - A Caution statement was added to instruct non-RIVO employees that there have been processing delays with leads received. So, to mitigate cases from being escalated, they are being reminded to follow the guidance stated. IPU 23U0384 issued 03-13-2023.
(52) IRM 25.25.8.7(2) Row 6 - Rewrote the sentence for clarity, and to specify what the bank will tell a taxpayer regarding their returned refund. IPU 23U0728 issued 06-14-2023.
(53) IRM 25.25.8.8(8) - Corrected the DFI Account number which is important for banks returning questionable tax refunds to the US Treasury through Credit Gateway program. IPU 23U1021 issued 10-19-2023.
(54) IRM 25.25.8.9(7) - Added a Reminder due to the request from OCSE to suspend reversal adjustment unless the timeframe for inputting the adjustment is less than 30 days of the 150 we are given to request for the reversal. Otherwise if the adjustment is not inputted, the IRS will lose those funds on the cases a determination was made the return was fraudulent. IPU 23U1021 issued 10-19-2023.
(55) IRM 25.25.8.9(7) - Caution statements were removed because the procedures cited, policy was implemented that no longer requires TE to perform adjustments to determine the offset amount. As a result, certain rows throughout the table that referenced adjustments were also deleted (see rows 5 and 10). Other deletions throughout the table that were removed, included updates/notes to AMS and EFDS as this procedure was not consistent with other External Lead inventory(see rows 11, 13, 14, 14a-b). IPU 23U0860 issued 07-31-2023.
(56) IRM 25.25.8.9(7) Row 2 - Added for clarification, the additional information TEs needed to consider when determining the appropriate action to take based on the case scenario. Also clarified who should be contacting the TOP Liaison as this was not clear. In addition, a statement was added to make sure LMS updates are completed, and referrals are made, if applicable. IPU 23U0860 issued 07-31-2023.
(57) IRM 25.25.8.9(7) Row 3 - A statement was added to make sure TEs enter all required LMS data as this information is needed to complete processing the offset. IPU 23U0860 issued 07-31-2023.
(58) IRM 25.25.8.9(7) Row 12 - Added a statement to the response to make sure TEs review all scenarios that may apply to the scenario to assure the appropriate action is taken to resolve the case. IPU 23U0860 issued 07-31-2023.
(59) IRM 25.25.8.9(7) Row 13 - Note was added to make TEs aware that Mass Push procedures should be followed for prior year returns being pushed to STARS. IPU 23U0860 issued 07-31-2023.
(60) IRM 25.25.8.9(8) - Documented procedures the RIVO OCSE POC will follow during the initial import and subsequent export of cases referred. Which also includes the commitment to PAS for NQRS reviews. IPU 23U0860 issued 07-31-2023.
(61) IRM 25.25.8.10 - Revised the paragraph to emphasize that only debit cards should be sent to RIVO since they were receiving other cards not associated with a questionable refund. Also added a link with procedures to address pre-paid EIP debit cards to make sure they are sent to the appropriate place to process. IPU 23U0728 issued 06-14-2023.
(62) IRM 25.25.8.12(1) - Per feedback received from a program review, the paragraph was rewritten to clearly explain the difference between reject reason code R17 and the addendum records that identifies the specific reason an ACH deposit was rejected. IPU 23U0728 issued 06-14-2023.
(63) IRM 25.25.8.12.1 - Removed the reference relating to reject reason code R23 as this type of reject is not part of the NACHA Opt-in program. IPU 23U0728 issued 06-14-2023.
(64) IRM 25.25.8.12.1(3) - Removed the reference relating to reject reason code R23 as this type of reject is not part of the NACHA Opt-in program. IPU 23U0952 issued 09-12-2023.
(65) IRM 25.25.8.12.1(5) Table Row 3 - Added procedures to require TEs to conduct additional screening after a taxpayer has authenticated to prevent refunds from be erroneously released. IPU 23U0952 issued 09-12-2023.
(66) IRM 25.25.8.12.2(2) - Added missing procedures for notating R23 cases in LMS. IPU 23U0952 issued 09-12-2023.
(67) IRM 25.25.8.12.2(3) - Added procedures for a TE to conduct additional screening for other fraud to reduce the possibility of erroneously releasing a refund if the taxpayer authenticates. IPU 23U0952 issued 09-12-2023.
(68) IRM 25.25.8.12.1(4) - Added a condition to address how to identify returns claiming either the FTC or ERC and the appropriate manner to resolve the account. IPU 23U1042 issued 10-23-2023.
(69) Editorial changes were made throughout this IRM to correct spelling, grammar, spacing, links, and punctuation. In addition, corrections were made to the title listed for the CP-53A and CP-53B notices. IPU 23U0952 issued 09-12-2023.
(70) Editorial changes were made throughout the IRM to correct grammar and punctuation. Also revised some sentences to make them clearer. IPU 23U0860 issued 07-31-2023.
(71) Editorial changes were made throughout the IRM to correct, spelling, spacing, broken links, unnecessary tags, grammar, punctuation and titles. In addition, symbols were removed that are not compatible with plain language guidance and header rows were added to tables. IPU 23U1021 issued 10-19-2023.
(72) Editorial Change was made to correct the spelling of the organization. IPU 22U1223 issued 12-19-2022.
(73) Editorial change were made to revised the numbering of rows in tables due to the deletion or revision of guidance. IPU 23U0974 issued 09-25-2023.
(74) Editorial change made to correct an email address name. IPU 23U0283 issued 02-21-2023.
Effect on Other Documents
IRM 25.25.8 dated November 28, 2022 (effective 12-12-2023) is superseded. This IRM incorporates the following IRM Procedural Updates (IPUs) - IPU 22U1185 issued 12-13-2022, IPU 22U1223 issued 12-19-2022, IPU 23U0115 issued 01-17-2023, IPU 23U0283 issued 02-21-2023, IPU 23U0384 issued 03-13-2023, IPU 23U0728 issued 06-13-2023,IPU 23U0860 issued 07-31-2023, IPU 23U0952 issued 09-12-2023, IPU 23U0974 issued 09-25-2023, IPU 23U1021 issued 10-19-2023, and IPU 23U1042 issued 10-23-2023.
Audience
Return Integrity Verification Operations employees.
Effective Date
(12-12-2023)
Related Resources
(1) The related resources listed below may be accessed for account research and issue resolution:
Electronic Fraud Detection System Database (EFDS)
Lead Management System (LMS) and Offset Reversal Lead (OSRL)
External Lead Integrated Automated Technologies (IAT) Tool
RIVO Portal External Lead RIVO
Denise D. Davis
Director, Return Integrity Verification Program Management
Wage and Investment Division
Program Scope and Objectives
(1) Purpose and Program Goals: This IRM section provides guidance for Return Integrity Verification Operations (RIVO) employees when screening Individual Master File (IMF) returns in the Electronic Fraud Detection System (EFDS) for possible identity theft and false income and withholding.
(2) Audience: RIVO employees
(3) Policy Owner: Denise D. Davis
(4) Program Owner: RIVPM program office
Background
(1) Return Integrity Verification Program Management (RIVPM) strengthens the integrity of the tax system by:
Protecting the public interest by improving IRS’s ability to detect and prevent improper refunds
Serving the public interest by taking actions fairly and appropriately to identify, evaluate and prevent the issuance of improper refunds
Helping taxpayers understand the refundable tax credits for which they are eligible
Primary stakeholders are Return Integrity Verification Operations (RIVO), Accounts Management and Taxpayer Advocate
Program Goals: Provide guidance for screening and dispositioning returns claiming questionable refunds
Program Management and Review
(1) The Return Integrity Verification Operation (RIVO) Monthly Performance Comparison Report, tracks the inventory, including receipts and closures. Additional report guidance is found in IRM 1.4.10, Return Integrity & Verification Operation Managers Guide.
(2) The Embedded Quality review program is in place to review all processes to ensure accuracy and effectiveness of the program. Goals, measures, and operating guidelines are listed in the yearly Operation Guidelines and in IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS), and Electronic Products and Services Support.
Authority
(1) The following references provide authority for RIVO:
IRM 1.2.1.5.10, Policy Statement 4-21
IRM 1.2.2, Servicewide Policies and Authorities, Servicewide Delegations of Authority
IRM 1.1.13, Wage and Investment
Various Internal Revenue Codes (IRC) including but not limited to:
IRC 6402(a), Authority to make credits or refunds
IRC 6401, Amounts treated as overpayments
IRC 6404, Abatements of tax
IRC 6213, Restrictions on assessments and math error authority
Responsibilities
(1) RIVPM has responsibility for information in this IRM. Information is published in the IRM on a yearly basis.
(2) The Director of RIVPM is responsible for the policy related to this IRM.
(3) The Chief of the RIVPM Policy & Analysis is responsible for ensuring this IRM is timely submitted to publishing each year.
(4) The Tax Analyst ensures this IRM is updated with current policies and procedures used by RIVO employees to manage their assigned inventory.
(5) RIVO employees are responsible for executing procedures per the guidance provided in this IRM.
(6) More information can be found in IRM 1.1.13.5, Return Integrity and Compliance Services.
Acronyms
(1) For a list of Acronyms used throughout RIVO see IRM 25.25.1.1.6, Acronyms
Related Resources
(1) The related resources listed below may be utilized for account research and issue resolution. These related resources may be accessed through the IRS Intranet-Servicewide Electronic Research Program (SERP) site.
Electronic Fraud Detection System (EFDS)
Lead Management System (LMS)
Offset Reversal Lead (OSRL)
External Lead Integrated Automated Technologies (IAT) tool
RIVO Portal for External Lead RIVO
(2) Integrated Data Retrieval System (IDRS) Follow IRM 21.2.1.3.2, Authorized IDRS Access.
(3) The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accordance with taxpayer rights. See IRC § 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For more information about the TBOR, see Taxpayer Bill of Rights.
External Lead Program Overview
(1) An External Lead involves a questionable federal tax refund reported by financial institutions or various other sources. A lead can be a Treasury Check, direct deposit/Automated Clearing House (ACH), refund anticipation loan check or pre-paid debit card. The IRS RICS’ External Lead Program is responsible for receiving and processing leads, and ACH credits returned by financial institutions and other sources. RIVO External Lead teams work with IRS Submission Processing to receive questionable leads, screen, and validate them and subsequently request the recovery of refunds to reconcile the accounts.
Lead Sources include:
Criminal Investigation
Refund Inquiry
Financial Institutions
Federal and State agencies
National Banks
State Banks
Savings and Loan Associations
Mutual Savings Banks
Credit Unions
Brokerage Firms
Government Agencies
Correctional Facilities
Various Other Sources
(2) Leads should be received into the general mailbox as follows:
For External Use - efleads@irs.gov
For Internal Use - *W&I-RICS External Fraud Leads
Exception: Taxpayer Advocate Service (TAS) follows the Return Integrity and Compliance Service (RICS) Service Level Agreement (SLA) addendum procedures.
(3) The Acknowledgement Verbiagescript must be sent to the financial institution the same day or next business day after a lead is received.
External Lead Mailbox Process
(1) Employees assigned to the mailbox process must review all e-mails received that day, or the next business day if it’s received after hours, a weekend, or holiday. The lead type and/or inquiry must be identified by its designated flag. Follow local procedures for flag determinations. Working the mailbox should be done as a priority since banks are advised that a response will be issued on most leads within 10 days.
Note: If the inquiry is from a new financial institution, send Publication 5033, IRS External Leads Program: Fact Sheet on Submitting Leads and the Lead Submission Spreadsheet Template. Inquiries that requires elevation to headquarters, flag the email red and then notify the RIVPM P&A POCs assigned to the External Lead program.
Lead Types
TOP Offsets
Refund Anticipation Loan (RAL)
Leads with funds available
Lead only (no funds available) - follow procedures in IRM 25.25.8.2.1, Lead Only (No Funds Available)
Automated Clearing House (ACH) Reversals - follow procedures in IRM 25.25.8.2.2, Automated Clearing House (ACH) Reversals
Altered Checks -- follow procedures in IRM 25.25.8.2.3, Altered Checks
Questionable Business Master File returns -The account number for these leads will be identified with an Employer Identification Number as the TIN. See IRM 25.25.8.3.3, BMF External Lead Procedures for more information
Centralized Check Process leads involving returned Treasury checks, third-party checks and/or miscellaneous repayments. See IRM 25.25.8.11, Centralized Check Process for more information
Economic Impact Payment (EIP) - see IRM 25.25.8.2.5, Identifying Economic Impact Payments and IRM 25.25.8.3.2, Processing Economic Impact Payment Leads for further information
(2) Employees assigned to the External Lead mailbox, use the table below to identify the action to take when an email is sent to the mailbox:
IF | AND | THEN |
1. Lead submitted includes only IMF accounts | There is an established history of submitting a lead (i.e., listed on the Financial Contact Information spreadsheet located in the Bank Working Directory file) |
|
1a. Lead submitted to the External Lead mailbox or forwarded by RIVPM P&A staff | No record found on the Financial Contact Information spreadsheet located on the Bank Working Directory. |
|
2. Lead includes BMF account(s) only |
|
|
3. Lead include IMF and BMF account leads |
|
|
4. Lead only, no funds |
| See IRM 25.25.8.2.1, Lead Only (No Funds Available) for guidance to address these leads. |
5. Leads requiring priority handling:
|
|
|
6. Follow up e-mails Reminder: Mailbox personnel must take the actions described the same day or next business day if the email is received on a weekend, holiday, or after hours. |
|
|
Lead Only (No Funds Available)
(1) Contact the financial institution to ensure there are no funds available.
(2) Do not create a lead number nor import it into the Lead Management System (LMS).
(3) Send the financial institution, the Lead Only (no funds available to be returned) feedback script.
(4) Refer all leads where no funds are available to the Industry Lead Mailbox, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ and include "lead only" in the subject line.
Reminder: Do not forward e-mails sent from the bank secured website. Create a new e-mail, include attachments and a secure password.
Reminder: This is not an encrypted mailbox. Therefore, create a password protected zip file, and then send the referral to Industry Fraud Leads. A confirmation e-mail will be received by the sender once the file is received. Refer to IRM 10.5.1.6.2, Encryption, for additional guidance when encrypting SBU data (including PII and tax information).
(5) Update the lead as "Completed" in the LMB and move the lead folder to the Completed folder.
Automated Clearing House (ACH) Reversals
(1) An ACH reversal is a lead type that involves a rejected direct deposit refund using a reason code other than 17. If notified of this type of reversal, it is important that actions be taken the same day to prevent the refund from being released. See steps 2-4.
Note: These are not common cases now, but if an ACH reversal appears in a TEs inventory, it should be made a priority to address.
(2) Open the ACH control base as C#,BKLDACHREV, A, MISC,148XX00005.
(3) Initiate refund stopping actions, and follow procedures in IRM 25.25.2.4, Stopping the Refund.
(4) Send the Notice of ACH Reversal script by e-mail and attach Pub 5033, "IRS External Leads Program: Fact Sheet on Submitting Leads" to the financial institution.
Altered Checks
(1) An altered check is one that was materially or maliciously altered to commit fraud. Usually this entails the payees name, address and/or dollar amount was changed on the check.
(2) The Treasury Inspector General for Tax Administration (TIGTA) has oversight of these types of cases.
(3) When an altered check is identified in the mailbox process send the Request for Altered Check to be Returned (Both scanned and/or Physical) script to the financial institution unless the check is in the External Lead team possession.
Reminder: If the altered check is in the possession of the External Lead team, handle it with rubber gloves, place in a plastic bag, and then secure for 90 days to allow TIGTA to follow up.
A request to create an image of the front and back of the altered check.
A request for gloves to be worn while handling the physical check.
A request to place the check in a secure place for 90 days to allow time for TIGTA to follow up.
Caution: If a lead involves both an altered and non-altered check, see IRM 25.25.8.3.1, Processing Altered Checks for information on assigning the lead number.
Other Inquiries
(1) The External Lead mailbox may receive general inquiries that may require special handling. The proceeding paragraphs capture some of the more common inquiries and responses.
(2) Legal or policy issues - Elevate to RIVPM Policy Analyst External Lead program POCs.
(3) Taxpayer inquiries - Taxpayers may contact the IRS to inquire about the status of their refund after being advised the bank returned it. Send them theTaxpayer Inquiries - IRM 25.25.8.4(3) feedback script.
(4) Reclamation Claim Request - Flag the e-mail and forward it to the site/team assigned the lead. See IRM 25.25.8.2.4.1, Reclamation Claim Requests for additional information.
(5) Third-party Check Emails - Recovery from 3rd party check e-mails will be assigned to the Centralized Check Process (CCP) POC. Do not create a lead on these referrals. Scan the third-party check and save to the CCP folder. Notate on photocopy if original check or copy of check received.
(6) Indemnification Request Involves a bank requesting the IRS return funds associated with a refund(s) recovered. See IRM 25.25.8.2.4.2, Indemnification Requests for additional information.
Reclamation Claim Requests
(1) When a taxpayer initiates a claim for a lost or stolen check, Bureau of Fiscal Service (BFS) will send a claim to the bank to recover the funds if the check was negotiated. BFS gives the bank 30 days to respond or dispute the claim. If an email is sent to the mailbox requesting assistance with the reclamation claim, send the bank the Reclamation Claim Acknowledgement script, research the account for the payment, and then follow the table below.
Note: Banks may not specifically state they received a reclamation claim. For example, the bank may state, BFS is requesting for funds to be returned, or I've been debited twice for the same payment. If it’s unclear , contact the bank POC and ask for clarification.
(2) Follow the table below for reclamation claim inquiries.
IF | AND | Then |
---|---|---|
1. The inquiry does not include the lead number |
|
|
2. Payment was recovered for the full amount of refund released Note: Inquiries may come from BFS if the bank stated the funds were returned to the IRS via the External Lead program. | Claim is less than 30 days from the date listed on the reclamation claim. Note: If more than 30 days, notify the bank to send an indemnification request and include the information needed for a manual refund. |
|
3. Payment was not found |
|
|
Indemnification Requests
(1) Financial Institutions will occasionally request for funds recovered, to be returned. The subject line may not specify this and so it is important that the TE read the email and understand what is being requested. If funds are requested to be returned, or the bank wants to know how to recover the funds, send the bank the Indemnification Request Acknowledgement script which includes the specifics on what the bank will need to provide.
(2) Once the information is received, forward it to the team responsible for preparing manual refund requests.
Identifying Economic Impact Payments
(1) The Economic Impact Payment (EIP) was authorized by the Coronavirus Aid, Relief, and Economic Security Act (CARES Act). Payments are identified as follows:
EIP 1 and 2 payments post to the 2020 tax year module
EIP 3 payments post to the 2021 tax year module
IDRS Command Code ENMOD and IMFOLE will post the transaction as a TC 971 AC 199. The source used to determine eligibility will also be posted to the module (i.e., tax year 2019 or 2018 tax return, REB, SSA, or RRB)
The amount of the payment (1/2 of the payment if filing status claimed on tax return is MFJ)
Julian date = 999
TC 766 posted with Credit Reference Number 338 (amount attributable to the primary and secondary taxpayer) and/or 257 (amount attributable to qualifying children)
If the EIP was an ACH deposit that was rejected using return reason code 17, the Control D report will display an R after the 202012 tax period
Processing External Leads
(1) The Lead Management System (LMS) is used to assign a lead to Tax Examiners (TE). Export the LMS spreadsheet and review all information provided in the lead folder.
(2) If the lead is incomplete, refer the lead to the local point of contact (POC) to contact the institution for the information missing.
Reminder: Save any additional e-mails/attachments received to the associated lead folder as a PDF.
Reminder: Update the institution’s RTN if not present on the spreadsheet. Attempt to retrieve the number from EFDS or CC IMFOBT. If the routing number is not available input a zero in the field in LMS.
Note: If the institution response contains a statement that all available information is provided, do not contact the institution.
(3) Research the account for TC 971 AC 123 with MISC field "TPP Recovery". If present, do not research further, request the financial institution return the funds.
(4) Review the account to determine if Form 4136, Credit for Federal Tax Paid on Fuels was used to claim the Fuel Tax Credit (FTC) or Form 7202, Credits for Sick Leave and Family Leave for Certain Self-Employed Individuals was used to claim the Sick Leave credit. Note, this form is currently obsolete as it was only intended for use tax years 2020 and 2021. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ See the table below to assist with identifying each credit. Paragraph 7, row 10 -12, provide the procedural guidance for working these cases.
Fuel Tax Credit | Sick Leave Credit |
---|---|
IDRS CC TXMODA will display a TC 766 with the applicable Credit Reference Number (CRN) of the fuel type paid. See Form 4136 to see the specific CRN claimed. | IDRS CC TXMODA will display a TC 766 with the applicable Credit Reference Number (CRN) 299 or 271.
|
IDRS CC TRDBV and the Employee User Portal MeF files can be used to view the Form 4136 filed. | IDRS CC TRDBV and the Employee User Portal MeF files can be used to view the Form 7202 filed. |
See IRM 4.19.15.16, Fuel Tax Credit Claimed on Form 4136 for additional information. | See IRM 4.19.14.17.4., Sick and Family Leave Credit (No current year business reported) for additional information. |
(5) The EL IAT tool must be used to decide if a return is valid, unless instructed otherwise. If the tool cannot decide, follow the research steps in paragraph 6 below. The External Lead (EL) IAT tool will be used to input a TC 971 AC 134, TC 971 AC 850, and to open a control base on IDRS, "C#,BKLD,A,MISC
148(XX)00001,*".
Reminder: A control base must be entered on all accounts except for those involving non-IRS refunds and deposit only leads.
Note: Review the detail report from the EL IAT tool ensuring actions were input to the correct tax period. Manually input action that did not populate from the tool.
Reminder: Do Not open controls on the Internal Revenue Service Number (IRSN) when the SSN is available. See IRM 3.21.263.5.5, Internal Revenue Service Number (IRSN), for other IRSN uses.
Reminder: If you determine the funds were not from the IRS, do not request them to be returned. Update LMS comments. If the refund is from a federal agency other than the IRS, respond using the Non IRS Refund Check script located at the RIVO Portal External Lead Feedback Script page.
(6) The EL IAT tool decides on whether the return is valid or not. If the tool was unable to decide, follow the research steps below to assist in a manual determination:
Review the reason for referral provided by the financial institution.
Follow IRM 25.25.2.2, Data Mining Screening, to help in deciding if the return is valid.
Identify any previous IDRS reversal adjustments on the account.
Review the account for Exam activity (TC 42X, -L freeze etc.).
Search entity modules for indications of identity theft such as a previously posted TC 971 with Action Code (AC) 5XX. See IRM 3.5.20.2.8.1, Identity Theft Indicator.
Review IDRS for any payments (TC 610, TC 670, TC 430, TC 716, etc.).
Review account for any balance due conditions (this may indicate other actions taken on the account).
Review IDRS for extension to file (TC 460).
Review EFDS notes for indication of previous RIVO involvement.
Review account for posted TC 971 action code 078, indicating forgery.
Note: Research for open issues and use Contact Employer for any previous verified good IDOCs.
Review IDRS CC TXMOD for the tax period in question and ensure there are not any open controls not in "B" status. Contact the open control, if found, before taking any action.
Exception: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Note: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ | ≡ ≡ ≡ | ≡ ≡ ≡ ≡ |
---|---|---|
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ |
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ |
Note: If Exam closed their audit and a determination was made ( i.e., TC 30X), consider the return valid as filed. Do not request for the funds to be returned. If the funds were already returned, release the funds.
(7) After making a decision, follow the table below.
Note: If instructed in the table below to issue an indemnification letter and the financial institution does not require it, the TE must enter in the Comments field located on LMS Lead Record ID page, the note "NILR" (meaning No Indemnification Letter Required). It’s not applicable to Deposit only leads as it is understood that the bank does not require an indemnification letter.
Reminder: Instructions below referencing the issuance of an indemnification letter and/or a script, should be done by the TE assigned to the lead or their designated POC (i.e., Supervisor or Lead). The TE must follow up to make sure the documentation was issued.
If | And | Then |
---|---|---|
1 Note: NO further research is required | The return is questionable |
|
2 | the return is questionable, AND no funds were received with the lead |
Note: When necessary, update Lead Template with funds to be returned/not returned for all associated accounts and save in the associated lead folder. |
3 | funds were received with the lead | See IRM 25.25.8.4, Processing External Lead Deposits. |
4 | no funds were received with the lead |
|
5 | The refund check was stolen |
|
6 | funds were received with the lead | See IRM 25.25.8.4, Processing External Lead Deposits. |
7 | no funds are available to be returned (the spreadsheet from the bank shows $0 available) |
|
8 | there is "TPP RECOVERY" in the MISC field |
Note: When necessary, update Lead Template with funds to be returned/not returned for all associated accounts and save in the associated lead folder. |
9 Note: Return is always considered bad |
|
Note: If the lead source does not provide a bank POC, check the financial Institution POC Listing for a good contact. Send the letter and script to that bank POC e-mail address. |
10 | The accounts contain either of the following markers:
|
|
11 | The account does not contain one of the markers outlined above |
|
12 | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Exception: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ |
|
(8) When an indemnification letter is issued, allow 45 days for a response. See the table below to determine the actions to take once the letter is issued.
If | Then |
1. No response |
|
2. Bank responds, payment was returned |
|
3. No response from bank nor funds received 15 days after the 45 day follow up letter is issued |
|
Processing Altered Checks
(1) The Tax Examiner (TE) will review the lead to determine if the account involves only an altered check, or a combination of accounts with altered and non-altered checks. Once the review is completed, the lead number will be assigned accordingly.
Altered Checks only - Create a new lead number that consist of the original lead number assigned, followed by the letter "A".
Combination of altered and non-altered checks - Do not change the lead number assigned. Notate in the LMS Comment field, Altered Check for the account(s) associated with the altered check.
BMF Altered Checks - Do not change the lead number assigned. Notate in the LMS Comment field BMF Altered Check. Follow the guidance in paragraph 2 below and then see IRM 25.25.8.3.3, BMF External Lead Procedures to complete processing the BMF lead.
(2) Take the following actions once the lead number is assigned:
If the physical check is received, place it in a plastic bag and store for 90 days to allow TIGTA to follow up.
Email the PDF copy of the front and back of the check and the lead number to the TIGTA Complaints Management Team (CMT) at ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ and copy Criminal Investigation mailbox at SDCLeads@ci.irs.gov.
Include the following in a secure format, when sending the PDF document:
a. State who is in possession of the physical check (i.e., RIVO - include the TE and Manager name, POD address, phone number, and e-mail address; Bank - include the bank name, POC name, phone number, and e-mail address).
b. A screenshot image of the check issued as shown on the Treasury Check Information System (TCIS).
c. If provided, state the city and state where the check was presented to the bank.Add, if provided, the TIGTA CMT reference number to the lead folder created.
Reminder: If TIGTA decides to investigate the case, a Special Agent will be deployed to retrieve the physical copy of the altered check.
(3) Used the table below to work IMF altered checks:
If | And | Then |
---|---|---|
1 | the return is good, and the check was not negotiated |
|
2 | questionable refund and the check were not negotiated |
|
3 | the return is good, and the check was negotiated |
|
4 | questionable refund and the check were negotiated |
|
Processing Economic Impact Payment Leads
(1) Upon the receipt of an Economic Impact Payment (EIP), input open Control number 148XX00001 on each account and activity code "BKLD". Leads involving questionable EIPs will require the Tax Examiner to determine an individual’s eligibility. Use the table below for this purpose.
Note: The individual’s eligibility will not be a determining factor if the referral was made because the EIP was stolen or the check was altered. The TE must request for the funds to be recovered and notate the applicable reason (i.e., stolen or altered check). Close all controls once the funds recovered are posted.
Note: Due to EIPs no longer being issued for TYs 2020 nor 2021, and the RRC/EIP issue being outside of RIVO’s scope, TEs will only update controls to closed status once a determination is made.
Reminder: Due to a court ruling on October 14, 2020, an incarcerated individual cannot be denied an Economic Impact Payment if they meet eligibility requirements. See below the EIP Eligibility Criteria.
Note: If the account contains estimated tax payments (i.e., TC 710, 716, OR 823), a manual refund will be required to release only the EIP portion.
EIP Eligibility Criteria
IF | AND | THEN |
---|---|---|
1 | A questionable EIP1, EIP2 or EIP3 lead was received |
|
2. | A questionable EIP1, EIP2 or EIP3 lead was received, and the citizenship code is A, B, C, D, or E) |
|
3. Note: If taxpayer is deceased, apply first the rules specified in the If column of either Row 1 or 2 of this table to determine the taxpayer’s eligibility for EIP 1, 2, or 3. | A questionable EIP1 lead was received, and: |
Note: If funds are returned to the IRS without our consent, the taxpayer can claim the Recovery Rebate Credit when they file their 2020 individual tax return. |
4. Note: If taxpayer is deceased, apply first the rules specified in the If column of either Row 1 or 2 of this table to determine the taxpayer’s eligibility for EIP 1, 2, or 3. | A questionable EIP1 lead was received, and: |
|
5. Exception: If the citizenship code is C and the lead involves a questionable EIP3 deposit, see Block 6 below to determine eligibility requirements. | A questionable EIP1, 2, or 3 lead was received |
|
6. | A questionable EIP3 lead was received: |
|
7. | A questionable E1P1, 2 or 3 was received: | Follow guidance in Block 3 or 4 depending on your research results to determine eligibility |
8. | The Lead Submission spreadsheet indicates in the Reason for Return field, individual already received a check from the Bank of Guam or similar verbiage |
|
BMF External Lead Procedures
(1) A BMF lead involves a questionable refund that contains an Employer Identification Number (EIN) as the TIN. When a BMF lead is received, take the following actions:
(2) The TE assigned the BMF lead will take the following actions:
1. BMF lead received Note: If the referral was submitted by CI or SBSE, or the lead source states the check was stolen or altered, open controls to BMFREQFUND 148XX00002, add history note: H,XXXXXX-XXB, and then issue the indemnification letter. Attach to the indemnification letter sent, the CI &SBSE Recovery Assistance script only when the referral comes from CI or SBSE. Proceed to step 3 once the recovered funds have posted. |
|
2. Research Command Code (CC) ENMOD and/or EFDS to determine if the EIN of the entity was marked as fabricated. Note: Indicators include on IDRS CC ENMOD, a posted TC 971 AC 524 with MISC activity EINFAB, or EFDS Contact Employer disposition, "Suspicious". |
|
3. Research confirms the entity was not fabricated or the funds from the fabricated entity posted. |
|
Processing External Lead Deposits
(1) Once notification is received that funds were returned, export the Lead Management System (LMS) spreadsheet, and review all information provided in the lead folder. Use of the EL IAT tool is mandatory when working deposits. See the table below instructions for deposits received that require specific actions.
Exception: Since the EL IAT tool will only allow a TE to override up to 6 refunds on an account, those that exceed that number will need to be applied manually using IDRS CC ELP45. When processing a payment manually, TEs must CMODE to Kansas City to prevent a transaction failure. See the table below for other requirements when working a deposit. Recovered Deposit Special Handling
If | Then |
---|---|
1. Lead source came from CI or SBSE | Notify the lead source POC, the amount recovered, if any, and the date of receipt. |
2. Rejects from the EL IAT tool | TEs must work these manually |
3. Fail to CMODE to the Kansas City sService Center location when posting a payment manually. | Input IDRS CC TERUP the same day to delete the transaction. |
4. Deposit information is inaccurate, missing or not up to date |
|
5. LMS database required fields are incomplete | Access LMS Edit field to add the following required data entries if missing:
|
6. Deposits with no x-ref lead number |
|
7. Non-IRS funds received |
|
(2) Run the EL IAT tool with the deposit information.
(3) Research the account for TC 971 AC 123 with MISC field "TPP RECOVERY." If present, do not conduct further research, post funds back to the account and suspend to 148XX00013 until TC 720 posts to the account.
Reminder: Do not release accounts containing a TC 971 AC 123. Disposition to PS 30 once the recovered funds post. See IRM 25.25.8.6, Monitoring External Leads.
(4) Research the account for TC 971 AC 078, forgery indicator. If present, do not reissue refund.
(5) Review IDRS CC TXMOD for the tax period in question and ensure all open controls are not in "B" status. If an open control is found, contact the open control before taking any actions.
(6) Use the External Lead IAT tool to input a TC 971 AC 134, TC 971 AC 850, and the history item," DONOTRFUND", if not already present on all invalid accounts. The EL IAT tool will update the control base on IDRS to, "C#,BKLDCKRECD,A,MISC
148(XX)0000X,*"(X= 4 invalid, 7 valid), input CC ELP45, and/or commingled memo.
Exception: For commingled funds, the only control base the tool will post to this account is BKLCOMNGLD.
Note: Review the detail report from the EL IAT tool and confirm actions are on the same tax period. If the actions were taken on the incorrect tax period close the control with "BKLDERROR" and open a control on the appropriate tax period. Manually input any action that did not populate from the tool.
Note: The External Lead TE has 15 working days to complete the CC ELP45 input, barring any delays or large leads.
(7) If the tool was unable to determine if the funds will be applied or remain in the commingled general ledger account, follow the table below to determine the next actions:
Reminder: Leads with multiple accounts may have multiple scenarios. For example, you may have an invalid return, a valid return, and an account with commingled funds on the same lead/deposit. Do not prepare the commingled memo until all accounts associated to the lead/deposit have been resolved.
If | And | Then |
---|---|---|
1 | the return is considered good |
Note: Balance the ELP45/ commingled amounts to reflect total of deposit. Reminder: The amount of the transfer may not exceed the TC 846 amount. Reminder: If a TC 971 AC 134 is not already on the account, do not input a new TC 971 AC 134. Input a history on CC TXMOD as "ValidNo134" |
2 | the return is considered good |
Note: Balance ELP45/commingled amounts to reflect total of deposit. Reminder: The amount of the transfer may not exceed the TC 846 amount. Reminder: If a TC 971 AC 134 is not already on the account, do not input a new TC 971 AC 134. Input a history on CC TXMOD as "ValidNo134". |
3 | the return is considered bad |
Note: If the tax year is in retention it must first be brought back to Master File using CC IMFOLB. Reminder: This will be updated en masse after the entire lead/deposit is completed. |
4 the account is dormant, in retention (refunds paid in calendar years prior to the current and prior calendar year) or the return is two years or older to the current processing year Note: DO NOT perform more research Reminder: Instructions in this row apply whether or not the Taxpayer Identification Number (TIN) owner is identified. Exception: If the account contains a TC 971 AC 123 with MISC field "TPP Recovery", post the money to the designated account. |
|
Note: If the tax year is in retention it must first be brought back to Master File using CC IMFOLB. Reminder: This will be updated en masse after the entire lead/deposit is completed. |
5 | Account does not contain TC 841 with document code 48 in the DLN or TC 700 with document code 58 in the DLN |
Note: Balance ELP45/commingled amounts to reflect total of deposit. Reminder: The amount of the transfer may not exceed the TC 846 amount. |
6 | Accounts contain TC 841 with document code 48 in the DLN or TC 700 with document code 58 in the DLN present on the account or |
Reminder: This will be updated en masse after the entire lead/deposit is completed. |
7 |
|
Note: Balance ELP45/commingled amounts to reflect total of deposit. Reminder: The amount of the transfer may not exceed the TC 846 amount. Reminder: If a TC 971 AC 134 is not already on the account, do not input a new TC 971 AC 134. Input a history on CC TXMOD as "ValidNo134". |
8 Note: Attempt to find a valid TIN. If valid TIN is found follow scenario in this if/then table. Exception: If multiple accounts on a deposit are not from an IRS refund notify your lead before proceeding | Cannot allocate the money received |
Reminder: This will be updated en masse after the entire lead/deposit is completed. |
9 Note: Attempt to find the correct tax period. If the correct tax period is found, follow scenario in this if/then table. Exception: If multiple accounts on a deposit are not from an IRS refund notify your lead before proceeding | Cannot allocate the money received |
Reminder: This will be updated en masse after the entire lead/deposit is completed. |
10 | the response from the financial institution is no funds are available for return |
|
11 | after 60 days with no response from the bank |
|
12 | the TIN is an Internal Revenue Service Number (IRSN), see IRM 3.21.263.5.5, Internal Revenue Service Number (IRSN), for more IRSN information and the module contains a TC 848 or TC 849 |
Reminder: DO NOT post anything to the IRSN, open the control and take all actions on the SSN’ Reminder: This will be updated en masse after the entire lead/deposit is completed. |
13 |
|
|
14 |
|
|
Reversal/Return of Recovered Funds
(1) Follow the table below, after researching the lead/deposit to determine if the deposit was applied to an individual account or commingled in the general ledger account.
If | And | Then |
---|---|---|
1 | Commingled funds applied to the 4971 General ledger account or funds applied to the 6801 (Excess) account Note: Funds are applied to the 6801 (Excess) account two years after the date of deposit. |
Reminder: Contact the financial institution when required information is missing. |
2 | funds applied to an individual account |
After TC 722 posts to the account: |
3 | a valid return and commingled funds applied to the 4971 General ledger account or funds were applied to the 6801 (Excess) account Note: Funds are applied to the 6801 (Excess) account two years after the date of deposit. |
|
4 | A valid return and commingled funds are applied to the 4971 General ledger account or to the 6801 (Excess) account and there is not enough available to cover the TC 846 amount. Note: Funds are applied to the 6801 (Excess) account two years after the date of deposit. |
|
5 | A valid return and funds applied to the taxpayer’s account |
|
Monitoring Posted Payments Processed
(1) Programming changes implemented in 2021 associated with Economic Impact Payments had a downstream impact on External Lead payments posted to an account as a TC 720. The impact caused these payments to go unpostable. Effective cycle 202326, programming was implemented to correct this issue. However, those unpostable that occurred prior to this cycle, will continue to follow the workaround procedures as outlined in the alpha list below, steps d-h.
Note: This workaround involves coordination between multiple departments to correct the unpostable, and therefore it may take a few weeks for the payment to post.
TEs must monitor payments in general to make sure they post. The alphalist below provides steps for monitoring to confirm a payment posted. However, due to the programming issue causing our TC 720 payments to unpost and/or get deleted, it is imperative that TEs check within two weeks to confirm the payment posted after the EL IAT tool processed it. If the payment went unpostable 138 RC 0, then the TE will need to follow the guidance in from the alphalist, d-h.Follow the steps below for monitoring payments:
Valid determinations, check the Detailed Report to confirm the payment posted.
Invalid determinations, check the Age listing for the posting of the payment.
If the P- Freeze or credit is posted to the account, this confirms the payment did not go unpostable and therefore the TE should follow procedures outlined in IRM 25.25.8.6(2) to resolve the account.
If no P- Freeze or credit is posted to the account, but an unpostable code 138 0 posted, open a control base to 1483700015 with activity code UNPOST720
Complete the Unpostable TC 720 spreadsheet located on the RIVO Portal page with the accounts found that were unpostable.
Forward the spreadsheet to the RIVPM and RIVO POCs to address the unpostables.
The RIVO POCs will notify the TE once the unpostable is corrected so the control base can be closed.
Once notified, close the control base, and take the appropriate actions to resolve the account(i.e., release refund, refer to the appropriate treatment stream, etc.)
External Lead Procedures for Automated Clearing House (ACH) Deposits
(1) Financial Institution Automated Clearing House (ACH)
Screen the return, if valid, "REFILE" and release the refund.
If questionable/suspicious, input a CC NOREFP (before return posts or same day) and send the return for verification or verify using CC IRPTR, if available for verification. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Open IDRS control base to "C#,BKLDACHREV,A,MISC 148XX00005,* ",if not already present on the module.
Close the "PRFZ" control base.
Input a TC 971 AC 134 on CC TXMOD to show RIVO activity.
If the return is not valid, add a history item to CC TXMOD, "DONOTRFUND".
Close the control as "841POSTED" when the ACH reversal post. If ACH has not posted, update the control to "148xx00004/7 "as applicable.
Monitor for credit posting, and manually add to STARS. If the return is already dispositioned and in the referral process, do not change the disposition unless the return is in a reject status and needs to be corrected (CE OR CA). See IRM 25.25.13-3, Scheme Tracking and Referral System (STARS) Disposition Definitions.
Update the 148XX00005 control to either 148XX00004 or 148XX00007, as applicable.
If prior year (PY) in STARS, input on the manual referral spreadsheet and close the IDRS control base.
Update Lead Management System.
Monitoring External Leads
(1) The local POC monitors the weekly external lead age listing. Follow the table below for appropriate actions.
Reminder: Resolve age listing in oldest received date order.
If | And | Then |
---|---|---|
1 | is 10 calendar days or older |
|
2 | is 60 calendar days or older |
If not present: If present: If good: If bad and return is current processing year: If bad and prior processing year: Reminder: If already in STARS, the National POC will update the STARS Disposition to the appropriate category and disposition. If IDT and the return is current processing year: Reminder: If completed en masse, update to "CAT 1". If completed individually, update to "CAT 7 MR". If multiple TC 846 or the posting of the TC 720 occurs after the account adjustment, refer to IRM 25.25.5-1, Triage Procedures, if the account requires adjustment. If IDT and the return is prior processing year: |
3 | is 60 calendar days or older |
|
4 | there is a credit balance and TC 720 is present |
If current processing year: Note: Manually refer to the appropriate workstream using the Manual Referral Spreadsheet if the return does not meet the auto-referral categories. If prior processing year: Reminder: If already in STARS, the National POC will update the STARS Disposition to the appropriate category and disposition. If IDT and the return is current processing year: Reminder: If completed en masse, update to "CAT 1". If completed individually, refer to IRM 25.25.5-1, Triage Procedures If IDT and the return is prior processing year: |
5 | a TC 720 is not present, and it is 10 calendar days or more from the date the CC ELP45 was input |
|
6 | there is a TC 841 present for 10 days or more |
If good: If bad and return is current processing year: If bad and prior processing year: Reminder: If already in STARS , the National POC will update the STARS Disposition to the appropriate category and disposition. If IDT and the return is current processing year: Reminder: If completed en masse, update to "CAT 1. "If completed individually, refer to IRM 25.25.5-1, Triage Procedures If IDT and the return is prior processing year: |
7 | there is no credit balance and is 60 calendar days or older | Close the control base as "Cxx,RFNDNOTHLD,C,MISC" |
8 | there is a credit balance and TC 720 is present |
Exception: Do Not Release refunds held by another function’s freeze code. When this occurs reverse RIVO marker by inputting TC 972 AC 134. |
9 | there is a credit balance and TC 720 is not present and is 10 calendar days or older from the CC ELP45 date |
|
10 | is 10 calendar days or older |
If in STARS: If not in STARS: |
11 | the TC 722 is present | Follow IRM 25.25.8.4.1, box 2 after TC 722 posts, Reversal/Return of Recovered Funds |
12 | the TC722/TC820 is not present and is 60 calendar days or older from preparation date of the accounting form |
|
13 Note: This is an account that contains a TC 971 AC 123 MISC "TPP Recovery" | the TC 720 is posted |
|
14 Note: This is an account that contains a TC 971 AC 123 MISC "TPP Recovery" | the TC 720 is not posted, and it is 10 calendar days or older from the CC ELP45 date |
|
15 | the TC 841 is posted |
|
16 | the TC 841 is not posted, and it is 60 calendar days or older from the F stop request date |
|
17 | the TC 841 is posted |
|
18 | the TC 841 is not posted, and it is 60 calendar days or older from the F stop date requested |
|
Criteria for Updating STARS Categories and Dispositions
(1) Use the table below to update STARS categories and dispositions.
If | Then |
---|---|
-A freeze is present and/or AM IDRS control base on the account such as: DUPF, IDT1, IDT3, XRET, XIVO, MXEN, IDS1, IDS3, IDT8, IDT9, IDS9, SCRM and SSA2 | Update STARS to "CAT 5 CL". |
Return meets IDT criteria:
|
|
(2) See the table in IRM 25.25.13-3, Scheme Tracking and Referral System (STARS) Disposition Definitions, for a description of the STARS disposition status codes and IRM 25.25.13-4, Scheme Tracking and Referral System (STARS) Category Definitions for each category definition.
Responding to Taxpayer Inquiries
(1) For non-RIVO employees receiving taxpayer inquiries follow the procedures outlined below.
(2) The caller states the bank returned their refund to the IRS, see Exhibit 25.25.8-2, External Lead Involvement Indicators, and follow the chart below:
Caution: Due to timing issues or delays, there may be no IDRS controls posted to the account or markers indicating the External Lead case is in progress, see box 9 below for instructions. Do not refer the taxpayer back to the financial institution unless the IRM instructs you to do so.
Note: Please contact the Point of Contact on any External Lead control before taking any actions on the account. See External Lead Point of Contact.
If | And | Then |
---|---|---|
1 | The control base activity field is one of the following:
|
|
2 | The control base activity field is one of the following:
|
Exception: Identity Theft Victim Assistance ( IDTVA) Employees may make IDRS adjustments as needed after contacting the External Leads POC to verify if the financial institution returned the funds. Exception: Do not initiate contact on "BKLCOMNGLD" , close the control base. |
3 | The control base activity field is one of the following:
AND the module shows control base assignment number is one of the following:
AND the module shows a posted TC 720 or TC 841 |
Exception: ID Theft Employees may make IDRS adjustments as needed. |
4 | The control base activity field contains the following:
|
|
5 | The control base activity field is "BKLCOMNGLD", and the control base assignment number is 148XX00004 or 148XX00007. |
|
6 | The control base activity field is "NOFNDSAVLB" or "NOFNDSRTND" and the control base assignment number is 148XX00004. |
|
7 | The closed control base activity field is "841LOST" or "ACHLOST" and the control base assignment number was 148XX00005, and there are no credits held on the account. |
|
8 | The account has a TC 720 or TC 841 credit with a TC 971 AC 134 or a TC 971 AC 199 RIVO freeze code. | Refer to the last closed RIVO control base and follow the instructions in this "If and Then "chart. |
9 | No open or closed RIVO control or indications of RIVO activity. |
|
(3) If the external lead control is over 90 days and the taxpayer did not receive their refund or notification, submit a Form e-4442, Inquiry Referral, to RIVO using the referral category, RICS RIVO - External Lead.
(4) When a return preparer who directed current year tax refunds into their account calls stating the bank informed them that they returned the deposited funds to IRS due to multiple refunds or a name mismatch, take the following action:
If | And | Then |
---|---|---|
The caller claims to be a tax return preparer who directed current year tax refunds into their account | Bank has told caller that the deposited refunds were returned to the IRS due to multiple refunds or name mismatch |
|
Bureau of Fiscal Services (BFS) Credit Gateway
(1) The External Leads Program, supported and managed by the IRS Return Integrity & Verification Operation (RIVO), works in conjunction with IRS Submission Processing (SP) to receive, screen and validate leads, and request the recovery of refunds to reconcile accounts. Financial institutions can return refunds associated with leads electronically, rather than a paper check, via Bureau of the Fiscal Service (BFS) Credit Gateway.
(2) Sources must provide a spreadsheet containing personally identifiable information (PII) that helps the IRS identify the source of the funds received as well as to ensure accurate processing of them.
(3) When working these leads, conduct complete and accurate research on them and then notify the lead source the amount to return to the IRS.
(4) RIVO will provide the source with a Credit Gateway Account Locator Number (ALC) for the submission of funds. See table in (7) below.
(5) RIVO will then receive via the efleads@irs.gov mailbox, a batch file of funds with the locked down accounts, along with an e-mail including the Lead Number(s).
(6) Any sources using the BFS Credit Gateway should be provided fund transfer instructions below for the site working the inventory. The accounting POC for the site should be included in the instructions.
(7) Update Lead Management System as required.
(8) To initiate the fund transfer, use the following account information:
Kansas City, MO |
---|
ALC: 20090900 |
Standard Entry Class (SEC) code: CCD |
Transaction Type: 22 |
Receiving ABA routing number: 051036706 |
DFI account number: 82009090001 |
Receiving Company Information: Institution Name and Lead# (limit 22 characters) (Lead# = mmddyy seq# of lead, i.e., SunTrust #101414 39) |
Tax Class: 20X0903 |
External Offset Leads (State and Federal Agencies)
(1) External Offset Leads primarily include the following:
The Office of Child Support (OCSE)
State Revenue Departments
(2) The Office of Child Support Enforcement (OCSE) receives and manages various state’s child support Treasury Offset Program (TOP) offset referrals. Questionable offsets are identified by states who run their own filters to determine if an overpayment is suspicious. In addition, an agency may also receive information from a taxpayer stating they did not work during the current year or file the tax return that generated the offset. OCSE load these leads to the Health and Human Services (HHS) website portal. Then, specific IRS personnel with access to the portal receive an e-mail from HHS that a new file was uploaded for review.
Note: Fraud Referral and Evaluation Analysts (FRE), during phase 1, retrieve the cases referred from the portal and then conduct the research using various batch tools and databases to determine if the offset should be reversed. See IRM 25.25.12.9.7, Office of Child Support Enforcement (OCSE) for more details. Those cases not meeting FRE’s criteria will be assigned to RIVO OCSE team to work in phase two of this process. The guidance, therefore, starting with paragraph 3 of this subsection, is specific to RIVO TEs assigned to work the fallout from phase 1 cases referred.
The IRS usually receives the following information:
Trace number
State referring case
Debtor first and last name
Debtor Taxpayer Identification Number (TIN)
Offset amount/date
Notes column(some states use the field to disclose the reason for referral)
(3) The IRS works directly with the OCSE to provide a response to the states on returning questionable offsets referred.
Complete accurate research on referred OCSE accounts is critical to the success of the program and to the various state’s appropriate disbursement of TOP offsets from federal tax refunds. The IRS’ response on referred cases directly guides the states on whether to release offset referred or hold pending reversal request(s) from IRS or BFS. The assigned Examiner must consider the following when reaching a determination:
All related transactions on the account
The validity of corresponding claims
Any prior actions taken by the IRS or BFS, to include full or partial reversal, and funds reissued
The offset amount available
Where to refer/treat an invalid claim
Note: The offset reversal leads process requires that the Tax Examiner review the entire corresponding module(s) for all items within RIVO scope. This includes all relevant entity research such as IDRS CC FTBOL, which is only updated once a year. Therefore, when reviewing this data, also review the FTBOL FY20XX Spreadsheet to determine if updated incarceration/release information is found when conducting research. Research should also include date of death and module transactions indicating GATT. See the following references IRM 25.25.9.4, General Agreement on Tariffs and Trade (GATT) Returns, Frivolous Claims, see IRM 25.25.10-1, Frivolous Arguments, inflated income and/or withholding, see IRM 25.25.2.3, Command Code (CC) IRPTR Return Verification During the Screening Process, identity theft, Unallowables, see IRM 4.19.15.15, Unallowable Code (UA) Program, non-eligible credits (see Form 1040 instructions) and dishonored/duplicate/erroneous payment refund issues.
Tax Examiner determinations include the following
"NO" - RIVO will not be requesting the return of funds
"YES" - The entire referred offset is no longer available for disbursement
For all "YES" responses, TEs must indicate either taxpayer Fraud, IDT, Inj Sp or Other as appropriate. Additional comments should be entered in the Remarks field as needed"PIR" - Prior actions by IRS has already reversed the offset in full and therefore is no longer available for disbursement
For all PIR accounts, TEs must indicate either taxpayer Fraud, IDT, Inj Sp, or Other as appropriate. Additional comments should be entered in the Remarks field as needed.BFS - TC 899(s) have posted to the account totaling the entire amount of the TC 898 and as a result, the offset is unavailable for disbursement
Note: Prior to IRP being considered fully loaded, if the Examiner, after lookback (see IRM 25.25.2.2.1 (2) #s 8-9, Data Mining Screening Tree) is unable to decide, the return will be submitted through the RIVO verification process. An interim response of "M" will be recorded in LMS and the IDOC(s) will be dispositioned as appropriate to “Verify” in EFDS. The return DLN will be captured in the "Remarks "field.
Reminder: Do Not suspend a case which has been determined to be Identity Theft (IDT) or where the entire referred offset is no longer available for reversal (see IRM 21.4.6.4.2.11, Netting TOP Offsets and Reversals)
(4) Use batch tools to complete the research to determine the offset tax period.
(5) Input the TC 971 AC 134 with MISC "BKLD OFFSET" on all receipts to identify RIVO External Lead involvement.
Note: The TC 971 AC 134 may be input en masse using the automated GII tools.
Reminder: Ensure the name control is accurate, mismatches will require re-submission after correction or a manual input.
(6) If the batch process is unable to verify the return against CC IRPTR due to the presence of Schedule C or other "unverifiable" data, including TIN and/or tax modules that cannot be located, the case will be referred to the External Lead team to work. Research will include any identity theft markers, including TC 971 AC 125, and EFDS notes and "Compromised IRP Data - Do Not Release Based on IRP". ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡.
The External Lead Tax Examiner (TE) will identify the corresponding TIN and tax period. Thereafter, review the corresponding tax return filing(s) and tax module(s), including netting the referred TOP offset (see IRM 21.4.6.4.2.11 , Netting TOP Offsets and Reversals).
(7) After researching and reviewing the corresponding filing(s) and module(s), follow the If and Then chart below to reach a determination, and to resolve the assigned account(s). The chart provides the most encountered scenarios. If the scenario is not covered, consult your Lead for guidance.
If | And | Then |
---|---|---|
1 | ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ |
|
2 | more than 5 years 11 months from the offset date and you determine that the return is NOT valid within RIVO scope and/or there are items of interest as discussed in the Note in paragraph 3 above. | Contact the TOP Liaison (through worklead) to determine the availability of funds
|
3 | There is a posted or pending freeze indicating Exam, Frivolous Filer Program (FRP), Criminal Investigations or Duplicate/Amended return Exception: If a -E Freeze and TC 810 with a Responsibility Code 4 is posted to the module, see IRM 25.25.8.3 Processing External Lead, Row 10-12, for the appropriate guidance. |
|
4 | There are no GATT, Frivolous Claim, Unallowable or dishonored/duplicate/erroneous payment/refund concerns as discussed in the Note in paragraph 3 above |
|
5 |
|
|
6 | 150 days or more have passed from the offset date |
Note: The TC 972 AC 134 is done en masse on a regular basis using automated GII tools |
7 |
|
Note: The TC 972 AC 134 is done en masse on a regular basis using automated GII tools. |
8 |
|
Note: The TC 972 AC 134 is done en masse on a regular basis using automated GII tools. |
9 |
|
|
10 | You determine the return is valid within RIVO scope and there are no items of interest as discussed above in #3 REMINDER. |
|
|
|
|
10a | You determine that the return is NOT valid within scope and revenue can be protected, along with funds available for recovery |
|
11 |
|
|
12 |
|
|
13 | No taxpayer filing located |
|
13a | Valid taxpayer return located, and the claimed refund is equal to or more than the offset amount |
|
13b | Valid taxpayer filing located and there is a balance due or zero return |
|
13c | Valid taxpayer return located, and the claimed refund is less than the offset amount |
|
13d | Taxpayer refund return located, but does not verify within tolerances established in IRM 25.25.2.2.1 paragraph 6 or contains GATT, Frivolous Claim, Unallowable or dishonored/duplicate erroneous payment/refund concerns as discussed in the Note of paragraph 3 above |
|
14 | All is true:
Note: Do not consider a Schedule C/F/HSH filing history as consistent when multiple returns claiming them are filed within the same processing year without additional research |
|
14a | Any of the following is true:
|
Note: The TC 972 AC 134 is done en masse on a regular basis using automated GII tools
|
14b | All conditions are true as specified in 14 above except, there are unallowables claimed on the return |
|
14c | Exam previously disallowed a similar Schedule C, F. or HSH |
|
15 | Return is verified to be the TIN owner(i.e., IRP support, see IRM 25.25.8.9(6), External Offset Leads (State and Federal Agencies) above for unverified IRP, filer verification, consistency filing, or other data on the return that confirms the TIN owner) Reminder: See note above in 14 |
|
15a | Identity theft is verified | Follow guidance in 14 through 14c above |
16 |
| See the tables in paragraph 1 and 2 of IRM 25.25.8.3.2, Processing Economic Impact Payment Leads to determine eligibility requirements. If funds should be returned, take the following action to reverse the offset:
|
(8) The designated POC will take the following actions:
Upload the response file to the OCSE/HHS portal within 30 days of the initial receipt of the submission.
Provide weekly consolidated 971/972 listings to RIVO clerical staff for GII input.
Process weekly Submission Processing Update file for LMS.
Provide Quality file to PAS staff for inclusion in NQRS review pulls.
Reminder: No information that was not originally provided by the source agency may be disclosed
Responding to Offset Phone Inquiries
(1) The IRS may receive phone calls from taxpayers who were informed their refund offset was not applied to a Federal/State debt because it was returned to the IRS.
(2) Follow the If and Then chart below, document the call in AMS and include the taxpayer’s name and contact information:
If | Then |
---|---|
1 |
|
2 |
|
3 | Advise the taxpayer the refund will offset to any outstanding debt. |
4 | If over 15 days with no indication of RIVO action, prepare Form e-4442, Inquiry Referral, to RIVO, using the referral category for RICS/RIVO External Lead. |
Debit Card Procedures
(1) Only questionable debit cards received at an IRS facility should be mailed in a sealed envelope to the Kansas City Service Center address listed below. Any other card (i.e., gift cards or credit cards, etc.) or correspondence not related to a questionable IRS refund, must be returned to the originator to resolve.
Exception: Pre-paid debit cards issued for Economic Impact payments, see IRM 3.8.45.19.1 (4), Repayment of Economic Impact Payments (EIP) for the address to return the card(s).
Internal Revenue Service
Attn: RIVO External Lead Manager
Post Office Box 219981
Kansas City, MO 64121
RIVO reviews the cards and determine the return address of the issuing bank.
Prepare and send the debit card letter in Exhibit 25.25.8-1, Letter for Intercepted Prepaid Debit Card(s). The issuing bank’s name, date the letter was sent and the volume of cards should be maintained on a spreadsheet on the Austin Shared drive in a folder labeled, Debit Cards.
(2) Reloadit cards are used by some taxpayers to add funds, to pay their balance due. Send the taxpayer letters and Reloadit cards to the Kansas City SP Payment Processing Unit. The SP payment processing unit does not accept credit/debit cards as a valid form of payment. The Payment Processing Unit returns the debit cards to the taxpayer with an explanation of how they can pay their balance due.
Centralized Check Process (CCP)
(1) The Centralized Check Process (CCP) inventory is worked by the Kansas City External Lead unit. The unit receives treasury check copies, third-party checks, and miscellaneous payments in the form of money orders, savings bonds, personal checks etc., from all service centers when potential identity theft (IDT) is involved. Refer to IRM 3.10.72.5.5, Extraction of Envelope Contents for Returns and Documents with Remittance and IRM 21.4.3.5.4, Returned Refund Check Procedures. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. The original third-party checks are mailed to:
Internal Revenue Service
Attn: RIVO External Lead Manager
Post Office Box 219981
Kansas City, MO 64121
Example: A check received in a service center made payable to an individual.
Exception: Taxpayer Advocate Service (TAS) follows the Return Integrity and Compliance (RICS) Service Level Agreement (SLA) addendum procedures.
(2) Third-party checks received expired, with Entity (name line) issues, or address changes are not worked in CCP. Return these to the originator for appropriate handling.
(3) If documentation containing a live signature is received with the check, file the document(s) per IRM 25.25.5.2.1, General Replies to Letters/Notices and Undeliverable Mail.
(4) When a CCP case is received, open a control to "C#,CCP,A,EVFY
148XX00003, *".
Note: If there is an open lead already, open a closed control for tracking purposes.
Returned Treasury Checks
(1) If a Federal Refund Treasury Check is returned to the (IRS), verify:
It is a Treasury check
Taxpayer confirmed the refund issued was not theirs and identity theft (IDT) has occurred
Note: Do not send Social Security, Federal Emergency Management Agency (FEMA), and Restitution Treasury Checks to Centralized Check Process (CCP). Return these checks to the originator for appropriate handling. If there is an open control base, close with "CXX,REJECTTORI,C,EVFY"
Reminder: The POC with access to the Treasury Check Information System (TCIS), will cancel all original treasury checks received using F-stop.
If | And | Then |
---|---|---|
1 | the check has not been negotiated and identity theft documentation is attached |
The TE will: The TCIS POC will: Note: Stamp "VOID" on all checks if not present. Once the TC 841 posts, the monitoring POC working the age list will: Note: Disposition the return to "CAT 5 CL" if resolved by another function. Disposition the return to "CAT 7 CL" if identity theft resolved by Return Integrity Verification Operations (RIVO). |
2 |
|
Note: It is possible for the treasury check to post as a TC 740. If the credit amount for the check is on the account and the check number matches the TC 740, close the base "740POSTED" Note: Add prior year processed returns (if not already in STARS) to the Mass Push Spreadsheet to be updated. When adding a return to the Mass Push Spreadsheet, open a control base on IDRS to: |
Third-Party Checks or Miscellaneous Repayments
(1) If a third-party check or miscellaneous repayment is received at an IRS facility, verify that:
Example: Financial Institution issues a check to an individual instead of Department of Treasury or IRS, a money order, etc.
It is not a Treasury check
The taxpayer indicates that the refund issued is not theirs
The taxpayer indicates the refund should not have been deposited to their account
Original third-party checks are sent to the External Lead Program at:
Internal Revenue Service
Attn: RIVO External Lead Manager
Post Office Box 219981
Kansas City, MO 64121
(2) Work third-party checks and recovered miscellaneous funds as an External Lead deposit.
(3) For third-party checks received, the RIVO POC will e-mail a copy of the original check to the issuing financial institution using the appropriate script to request that the funds be returned with a check payable to IRS or Department of the Treasury. See the RIVO Portal External Lead page for the appropriate script.
(4) Follow the If/And/Then chart for completing Centralized Check Processing (CCP) for third-party checks and/or miscellaneous repayments:
If | And | Then |
---|---|---|
1 |
|
Current processing year return or the return is already in STARS: Prior processing year return: Note: Funds returned for 3rd Party checks are worked as an ELP deposit. |
2 | If no response received after 45 days | The monitoring POC working the age list will:
|
3 | If no response received after an additional 15 days from the follow-up e-mail | The monitoring POC working the age list will:
|
4
|
|
Current processing year return or already in STARS: Prior processing year return: |
Reject Reason Code 17/18/19 Transcripts
(1) Beginning January 2013, an Opt-In Program developed by the IRS, Department of Treasury Bureau of Fiscal Services (BFS) and the National Automated Clearing House Association (NACHA) repurposed reject reason code 17 to allow the IRS a dedicated return reason code to reject ACH direct deposits associated with name mismatches, ID theft, and questionable fraud returns. All rejects are identified for this program as reject reason code 17. However, the addendum record field, when completed, provides the specific reason for the rejected direct deposit. Paragraphs 2, 3, and 4 provides details for each addendum record.
(2) Financial Institutions use Reject Reason Code 17, Addendum Record 17 (R17), to reject current year direct deposit refunds when the name/taxpayer identification number (TIN) listed on the Treasury Automated Clearing House (ACH) file for the tax refund does not match the account holder information in the bank’s records. R17 rejects post to IDRS with a TC 841 DLN ending in "77711" and a control base with an assigned number of "1487111117". Taxpayer receives a CP 53A, Attempt to Direct Deposit Your Refund, Could Not b Be Processed. A Paper Check Will Be Issued. A Reject Reason Code 17 REFC (refund cancellation) will generate when one or more of the following situations occur in banking filters:
The last name on the account (account holder) does not match the name on the return.
Multiple named federal tax refunds deposited into single accounts or multiple accounts.
Multiple tax refunds for multiple taxpayers going into a single account without any established relationship.
Full and partial name mismatches where a relationship to the account holder is not established.
TIN on account does not match return information.
There is no exact match of the entity information and efforts to reconcile joint filers is exhausted.
The IRS requests funds back as part of a recovery attempt. These funds may come back as either a paper check or a deposit. These accounts contain a TC 971 AC 123 with MISC field "TPP Recovery".
Reminder: The initial notice advises the taxpayer to wait 10 weeks prior to calling regarding their refund.
(3) Financial institutions use Reject Reason Code 17, Addendum Record 18 (R18) to reject current year direct deposit refunds when the bank determines the tax refund is identity theft. R18 rejects post with a TC 841 DLN ending in "77712" and a control base with an assigned number of "1487111118". Notice CP 53B," Direct Deposit Rejected Financial Institution - Refund Check Mailed", is mailed to the taxpayer.
Reminder: The initial notice advises the taxpayer to wait 10 weeks prior to checking on the status of their refund.
(4) Financial institutions use Reject Reason Code 17, Addendum Record 19 (R19) to reject current year direct deposit refunds when the bank determines the account holder’s tax refund is fraudulent. R19 post with a TC 841 DLN ending in "77713" and a control base with an assigned number of 1487111119. Taxpayer is mailed a CP 53C, Direct Deposit Rejected by Financial Institution -Refund Check Mailed.
Reminder: The initial notice advises the taxpayer to wait 10 weeks prior to checking on the status of their refund.
(5) Subsequently a refund cancellation R17 transcript listing generates to Return Integrity Compliance Services (RICS) External Leads for workload distribution and refund verification. The refund will be released or held upon the completion of the review. If held the return will be referred to the appropriate treatment stream.
Exception: Do not release accounts containing a TC 971 AC 123 with MISC field "TPP Recovery." Disposition to PS 30 once the recovered funds post, unless research shows the account is already adjusted to the good taxpayer’s figures.
Reject Reason Code R17 Procedures
(1) The External Lead NACHA Group pull Control D reports for the most recent date for R17, R18, and R19. The files are saved as a text file in their respective folders.
(2) Input EFDS return note BKL-RXX (XX= Reject Reason code 17/18/19) on all returns using CASE.
(3) Complete the following steps after the files are saved.
Use the Access Database and NACHA Import Template for the initial import of the new NACHA leads into LMS. Update each lead with the Lead Type, Total Amount Available for Recovery, and Site.
Assign each lead to "NACHA, NULL" in LMS.
Export the spreadsheets for all the leads imported and save in a working folder until Step e-h.
If there were R18’s received, send those returns to ACE/ADJ with the note "RIVO EL IDT BKLD" and input NACHA note "BKL - R18". Update LMS as TPP and put in Suspense.
Create an Excel file for the week’s NACHA inventory received, to send to FRE. Apart fromR18s, there should be a tab for each reject code, and within that tab include the lead number, SSN, and tax period for every account received for that reject code.
Save this file in the designated folder for FRE and then email the POCs to let them know the file is ready.
Using the file returned from FRE, fill out the LMS spreadsheets that you saved in Step c. Input all DLN’s, including the ones with no Results. Update all Good returns in LMS and move them to complete. Returns marked as FRE PS30 need to be placed into Suspense with a note stating TPP. What remains will be saved in the NACHA Fall Out folder to be assigned to the TE’s.
Based on the results provided by FRE, input the following EFDS notes:
Add R17 returns to Case and add note "BKL - R17"
Add R19 returns to Case and add note "BKL - R19"Close all controls on the PS 30 tab from FRE.
Reminder: FRE will take the actions to release the refunds from the list of returns they determined were valid.
(4) The results from FRE, saved in the NACHA Fall Out folder, must be manually screened by the TE assigned the cases. Follow IRM 25.25.2.2, Data Mining Screening, to assist in making a determination and follow the procedures in the table below to determine the appropriate EFDS process status and account resolution actions.
Reminder: ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
Review EFDS to aid in determining a pattern.
Identify any previous IDRS reversal adjustments on the account.
Review the account for Exam activity (TC 42X, -L freeze etc.)
Search entity modules for indications of identity theft such as a previously posted TC 971 with Action Code (AC) 5XX. See IRM 3.5.20.2.8.1, Identity Theft Indicator.
Review IDRS for any payments (TC 610, TC 670, TC 430, TC 716, etc.).
Review account for any balance due conditions (this may indicate other actions taken on the account).
Review IDRS for extension to file (TC 460).
Review EFDS notes for indication of previous RIVO involvement.
Note: Search for open issue or previously verified good through contact employer.
Note: Any IDOC on CC IRPTR containing the warning statement, WARNING - "POTENTIAL FRAUDULENT PAYER TIN" OR "WARNING - POTENTIAL FRAUDULENT SUBMISSION" and any IDOC with the notes in "EFDS, PATMAT-SUS IRP", "FABRICATED ENTITY", or "NO EMPLOYEES", should be considered falsified information and not used to verify wages and withholding.
Reminder: Research to establish whether the return is IDT or Non-IDT. RIVO DOES NOT AUDIT returns.
Note: If Exam closed their audit and allowed a 'no-change' determination (TC 300 .00 with no other credit reversals), consider the return valid as filed and do not request funds back from the financial institution. If the funds were already returned, release the funds.
(5) Follow the table below the determination is made:
If | And | Then |
---|---|---|
1 | filed by the TIN owner |
|
2 | the full TC 846 was returned |
|
3 |
|
|
4 | the full TC 846 is not returned Exception: If the account contains a TC 971 AC 123 with MISC field "TPP Recovery", then treat as in box 2 above |
|
5 | is an electronic filed return |
|
(6) Follow the table below for paper returns:
If | Then |
---|---|
1 |
|
2 |
|
3 | Input the IDOC information in EFDS and disposition the return as appropriate. Note: If pushed to verification , add to manual verification spreadsheet. |
4 |
|
(7) If there is a duplicate Filing Condition on CC TXMODA indicated by a –A Freeze:
Suspend the case, update control base to B status and update the activity to "SUSPNCE2AM".
When Accounts Management (AM) work is complete, they update the control activity to "DUPWKD" .
RIVO then monitors for the activity update and inputs a TC 290 .00 with PC 1 and closes the control base.
Reject Reason Code R23 Procedures
(1) Financial Institutions use reject reason code 23 (R23) when a taxpayer states the refund received, is not theirs. IDRS CC TXMODA will contain in the DLN, blocking series number, 77714. R23, generates notice CP-53B.
(2) Pull Control D files for NACHA and save as a text file in the appropriate reject folder.
Import NACHA files into LMS using the NACHA Import Template. The lead number is the date on the text file followed by the sequence received that day and the NACHA reject code, i.e., 031918 01 R23.
After file imports, update the record in LMS by notating as NACHA, input the total dollar amount on the Control D file in the "Total Amount Available for Recovery" box and assign to Cincinnati.
Add R23 returns to Case and add note BKL - R23.
(3) Send R23s received to ACE/Adjustments and input the "BKL - R23" note along with the "RIVO EL IDT BKLD" note.If previously re-filed by TPP, check to see if that was because of the lost refund and not because of authentication, they can go back through for lost refund.
Note: TPP results shows the taxpayer return was authenticated as indicated by a posted TC 972 AC 121, 124 or 129, conduct additional research to determine if other fraud exist before releasing the refund. Follow guidance inIRM 25.25.2.2, Data Mining Screening for screening.
(4) Split results into two tabs, TE & Valid. Run the DLNs through Discoverer to determine which accounts have split refunds. Load the accounts that do not contain split refunds on the TE tab in Case, and anything that has not been previously disposition will be sent to ACE/ADJ with the appropriate note "RIVO EL IDT BKLD". Leave returns with the disposition SCHEME/Verification alone, and send returns in any other process besides Re-file to ACE/ADJ. Review returns in re-file to determine:
If | And | Then |
---|---|---|
Disposition is valid | lost refund | Check validity and disposition appropriately |
Disposition is valid | the return is valid |
|
Undeliverable Refunds
(1) Undeliverable refunds involve paper checks returned as undeliverable that were prior R17, R18, R19 rejects and R23. Fraud Referral and Evaluation (FRE) team, compiles a listing of these checks for RIVO to review the account and determine if it meets IDT characteristics. Follow the chart below to determine the applicable action to take:
If | And | Then |
---|---|---|
1 | complete overpayment returned | Push through manual TPP process to PS 30 with the specific bank lead EFDS note. |
2 | complete overpayment returned | push to STARS and update as CATG "7" Disp "MR". |
3 | partial refund returned (i.e., split payment and only one TC 846 was returned as undeliverable) | push to STARS and update as CATG "7" Disp" MR". |
4 | partial refund returned | push to STARS and update as CATG "7" Disp "MR". |
5 |
| Take no action. |
6 |
| update EFDS note but take no actions. Note: FRE monitors for 60 days. If the S freeze is unresolved, push to STARS, update to Cat 7 and the applicable disposition. |
Letter for Intercepted Prepaid Debit Card(s)
Letter for Intercepted Prepaid Debit Card(s) |
---|
DEPARTMENT OF THE TREASURY |
INTERNAL REVENUE SERVICE |
ATLANTA, GA 30308 |
Financial Institution |
PO Box 12345 |
Anywhere USA |
|
By :e-mail/mail/fax |
|
Re: Intercepted Prepaid Debit Cards |
The U.S. Postal Inspection Service notified us that it suspected that prepaid debit cards you issued were used to receive fraudulent Federal tax refunds. The U.S. Postal Inspection Service intercepted these cards from the mail and provided them to our agency. We are returning these cards to you as the identified issuing institution. |
We wish to investigate whether any Federal tax refunds were deposited to the prepaid debit cards returned to you to ensure that we recover all refunds that are improper Federal payments. This letter is our request for your assistance with the investigation. |
The Federal Right to Financial Privacy Act, as amended in 2008, authorizes you to assist us by providing financial records, upon request, when we are investigating or recovering an improper Federal payment. In accordance with 12 U.S.C. § 3413(k)(2)(B), we request that you provide us with the direct deposit (routing and deposit account) numbers, Federal tax refund amounts, date of deposit or ACH transfer, and Social Security Number reported by the Treasury Financial Management Service on the ACH file for each Federal tax refund deposit that posted to the cards returned to you so that we may match this information against our records. Our request for direct deposit numbers is focused on the numbers your customer would enter on a Federal tax return to direct a refund to the card. |
We ask that you provide this response in spreadsheet format within 20 days from the date of this letter by secure email to efleads@irs.gov with a subject line following this format: Intercepted Prepaid Debit Cards, [Your Name], [Date]. Please direct any questions about this request to the same email address. |
We may later request that you return to us any refunds you identify to the extent that funds remain in the accounts you identify. We may also request your best efforts to protect the funds in any accounts by stopping the re-issuance of these cards and refusing any further withdrawals or payments requested by the cardholder. |
We appreciate your assistance in this matter. |
Sincerely, |
|
Denise D. Davis |
Director, Return Integrity Operation |
External Lead Involvement Indicators
(1) The following chart contains the Integrated Data Retrieval System (IDRS) control bases and history items indicating External Lead involvement.
1 | Description |
---|---|
2 | An External Lead was received. |
3 | IRS requested the funds (refund) from the financial institution. |
4 | Federal Refund Treasury Check received. Wait for TC 841 to post back funds. |
5 | IRS received the funds (refund), the amount returned typically is less than the TC 846 due to bank fees. |
6 | IRS received the funds (refund) but is unable to determine the dollar amount to apply to this account or the account was previously adjusted, and the refund covered up with a TC 841. These funds are placed in a general ledger account. |
7 | No funds (refund) are available to be returned to the IRS or no funds returned (no response from the bank) |
8 | Automated Clearing House (ACH) Reversal associated to an External Lead. |
9 | When TC 720 posts, refund will be released. |
10 | TC 720 or TC 841 posted, and refund should not be released without approval from RIVO. |
11 | Suspend until return has been pushed to STARS and can be referred |
12 | Suspend until offset reversal posts back to the account (TC 899) |
13 | There is a potential for an offset reversal based on account review |
14 | Third-party check received that has not posted. |
15 | Payment received to repay a refund received in error. |
16 | Waiting for the posting of the TC 720. Funds to post back to the account |
17 | Waiting for the TC 722 to post |
18 | The TC 722 posted |
19 | Waiting for the posting of the TC 841. Funds to post back to the account. |
20 | Waiting for the posting of the TC 841. Funds to post back to the account. |
21 | The refund check has been altered. i.e., money amount changed, name changed etc., |
22 | Funds have posted back to the account. |
23 | A treasury check has been canceled through TCIS and is waiting for the TC 841 to post to the account. |
24 | A miscellaneous payment was received from the taxpayer to repay the refund. Waiting for the posting of the payment. |
25 | A control was opened in error. |
26 | The refund was not held . |
27 | Reject the case back to refund inquiry. |
28 | The TC 740 posted to the account. |
29 | The TC 720 has posted to the account. |
30 | The funds were not issued by IRS and they are not being requested back from the financial institution. |
31 | A lead involving a deceased taxpayer who received an Economic Impact Payment. |
32 | A lead involving an Economic Impact Payment that has an indicator of identity theft. |
Recovery from Third Party Check Letter
Recovery from Third Party Check Letter |
DEPARTMENT OF THE TREASURY |
INTERNAL REVENUE SERVICE |
ATLANTA, GA 30308 |
Date |
Financial Institution |
Address |
City, ST Zip code |
By: mail |
Re: Recovery from Third Party Checks |
We received third party checks that we believe were issued by you in connection with the filing of federal tax returns claiming a fraudulent tax refund. We are returning these checks to you as the identified issuing institution. |
We wish to investigate whether any federal tax refunds were deposited to the accounts of the checks we have returned to you to ensure that we investigate and recover refunds that are improper federal payments. This letter is our request for your assistance with the investigation. |
The Federal Right to Financial Privacy Act, as amended in 2008, authorizes you to assist us by providing financial records, upon request, when we are investigating or recovering an improper federal payment. In accordance with 12 U.S.C. § 3413(k)(2)(B), we request that you provide us with the following information about federal tax refunds that posted to the accounts related to the checks we are returning to you:
|
Our request for direct deposit numbers is focused on the numbers your customer would enter on a federal tax return to direct a refund to your bank. We welcome additional information, such as the account or customer reference number, that will assist us in communicating with you about these refunds. |
We ask that you create an electronic spreadsheet listing only suspect refunds that posted to accounts that currently have a positive balance. If there is no chance of returning any part of a refund, please exclude the refund from your spreadsheet. We ask that you provide the spreadsheet within 30 days from the date of this letter by secure email to efleads@irs.gov with a subject line following this format: |
Recovery from Third Party checks, [Your Financial Institution Name], [Date] |
Please mention this letter in the email body and include information about a point of contact at your institution. Please describe any potential patterns or trends of improper payment revealed by federal refunds you received, even if related to accounts with a zero balance or other accounts at your institution. If you include details about these other accounts, please make clear that you are not offering to return funds from those accounts, for example by listing the current balance on each account. You do not need to provide any detail if you are already working with another IRS office to report potential refund fraud. |
We may later request that you return to us any refunds you identify to the extent that funds remain in the account. We may also request your best efforts to protect the funds in any accounts by stopping the re-issuance of these checks and refusing any further withdrawals or payments requested by the account holder. |
Please direct any questions about this request to efleads@irs.gov. |
We appreciate your assistance in this matter. |
Sincerely, |
|
Denise D. Davis |
Director, Return Integrity Operation |