Protecting the public interest by improving IRS’s ability to detect and prevent improper refunds

Serving the public interest by taking actions fairly and correctly to identify, evaluate and prevent the issuance of improper refunds

Helping taxpayers understand the refundable tax credits for which they are eligible

IRM 1.2.1.5.10, Policy Statement 4-21

IRC 6402(a), Authority to make credits or refunds

IRC 6401, Amounts treated as overpayments

IRC 6404, Abatements of tax

IRC 6213, Requirements for a statutory notice, including math error authority

IRM 2, Information Technology

IRM 3, Submission Processing

IRM 4, Examining Process

IRM 21, Customer Account Services

IRM 25.23, Identity Protection and Victim Assistance

IRM 25.25, Revenue Protection

IRM 1.1.13, Wage and Investment

IRM 25.25.1, Return Integrity and Verification Operation Business Master File Procedures

IRM 25.25.2, Revenue Protection Screening Procedures for Individual Master File Returns

IRM 25.25.3, Revenue Protection Verification Procedures for Individual Master File Returns

IRM 25.25.4, Integrity & Verification Identity Theft Return Procedures

IRM 25.25.5, General Correspondence Procedures

IRM 25.25.6, Taxpayer Protection Program

IRM 25.25.7, Automated Questionable Credit Program

IRM 25.25.8, Revenue Protection External Lead Procedures

IRM 25.25.9, Revenue Protection Prisoner Lead Procedures

IRM 25.25.10, Frivolous Return Program

IRM 25.25.11, Withholding Only Work (WOW) (Notice CP 05A) Procedures

IRM 25.25.13, Account Resolution for Return Integrity Verification Operations (RIVO)

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

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

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

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

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

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

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

≡ ≡ ≡ ≡ ≡ ≡ ≡

Load/Import all selected returns into CASE. Selected returns must be in Process Status (PS) codes 0, 3, 10, 12, 32, 47 or 60.

Push the return to PS 30.

Use Refund Amount and Load Date in SNAP to ensure pre-refund status.

Input the standardized EFDS return notes of the duplicate conditions that applied to your pattern (e.g., PATMAT-WW, PATMAT-ZIP CODE, PATMAT-IP, etc.)

Input a secondary EFDS note "RIVO FRE PATTERN" . The note must be on all returns pushed to PS 30.

Research may need to be performed to verify the return if it says "Tribal Income" before selecting the return for inclusion in a pattern. See IRM 25.25.2.6(4), Unsubstantiated Income and/or Withholding.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡

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

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

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

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

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

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

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡

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

≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

≡ ≡ ≡

≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡

Research for required Electronic Fraud Detection System (EFDS) note (RIVO FRE PATTERN, RIVO RSV IDT, etc.).

Determine if the return meets PS 30 criteria (not previously in the Taxpayer Protection Program (TPP), except for accounts containing a TC 971 AC 123 MISC field TPPRP or TPP Recovery).

Perform a BiTPP (Back in Taxpayer Protection) to check for accounts that have been placed back into the Taxpayer Protection (TPP) process. The accounts on this spreadsheet must be checked on IDRS for TC 971 AC 124 or AC 129 to see if the return went through the TPP process. If there is no indication of prior TPP, set the return to be sent through the TPP process on the following Thursday. If there is an indication of prior TPP then send the listing to management to have accounts removed from PS 30 and placed in the correct process status.

Provide feedback to managers if criteria are not met.

Research for missing note.

Perform a BiTPP to check for accounts that have been placed back into the TPP process.

Check IDRS accounts on the spreadsheet for TC 971 AC 124 or AC 129 to see if the return went through the TPP process.

Prepare batch freeze template for returns dispositioned to PS 30 after midnight the previous day up to the refund freeze cut off deadline, to generate TC 971 AC 134 and forward to Modernized Development and Delivery (MDD) contact.

EFDS return DLN is not posted - put on the Direct to Masterfile template for the TC 971 AC 124

EFDS return DLN is posted

Identifies current PS 30 inventory

Identifies all PS 49 DLNs (current and historical)

Tracks all DLNs placed into PS 30 at End of Day

Identifies TC 971 AC 129 and AC 124 returns for the year

Identifies returns after the correct suspense time expired

Tracks all TC 971 AC 123 DLNs

Run a Selections aNd Analytics Platform (SNAP) query and export applicable information related to each DLN submission (EIN, SSA run date, submission DLN, payee TIN, etc.).

Filter the query by assigned EIN using the payer TIN (pyr_tin) and export the query for further analysis.

Use IRM 25.25.1.5.2, Case Processing for Business Masterfile (BMF) Entity Fabrication (EF), for research steps to review EINs.

Run link analysis queries to find other potentially fraudulent submissions with bad submission IDs, SSNs, or EINs.

Add any submissions that are determined to be Suspicious IRP(SUS IRP) to the "IRMF_PFRD_Template" spreadsheet. Include the required information: EIN, SSN, Run Date, and Submission DLN.

Use the spreadsheet exported from SNAP to find any affected SSNs.
Sort the Action column by desired determination (SUS IRP or EF)
Copy all SSNs (pye_tin) and paste into a SNAP query to find any associated returns.

If a refund can be stopped for any affected SUS IRP or EF returns, regardless of the Process Status (i.e., PS 30 or PS 49), update the "Direct to Masterfile" template with the required information (Primary SSN, Name Control, Tax Year (YYYYMM) and DLN) for the input of the TC 971 AC 199. Do not include dashes in the SSN or DLN and remove any leading/trailing spaces. Place the template on the server DAILY by 10:00 AM ET for the Business Performance Lab (BPL) to add the markers to the Masterfile listing.

Move returns claiming suspicious IRP to PS 29 (Add to Scheme) in EFDS unless they are in PS 30 (Ace Adjustments) or PS 49 (ID Theft Hold).

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡

Do NOT send the return to PS 29 (Add to Scheme) if:
the Suspicious income document (ex: W-2) is not being claimed on the return
the return filed is a balance due return
potential refund loss is under tolerance (see IRM 25.25.2-4, Tolerance Chart)

If the refund is lost, disposition to PS 65 (Post Refund Potential Fraud)

If the associated returns have been moved to PS 31 (ACE Collections) and the IDOCs are determined valid and not suspicious, REFILE the return in EFDS.

Share any large dollar scheme with the HQ POC for possible referral. Include all link analysis research.

Move returns claiming potential fabricated income documents to PS 29 (Add to Scheme).

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡

Create an EFDS CASE to hold your Suspicious IRP and EF returns and monitor through the process.

If the return is in PS 49 (ID Theft Hold) when marked, it could get refiled by the Systemic Verification Process. Manually push these returns from PS 28 (Refile) to the correct scheme using IRM 25.25.2-1, State Mapping to Scheme Location.

Input the applicable EFDS Note on each return pushed to scheme per IRM 25.25.1-3, Entity Fabrication (EF) Standard Notes and Actions for EFDS and Account Management Service (AMS).

Update AMS and EFDS based on closing action. See IRM 25.25.1-3, EF Standard Notes and Actions for EFDS and AMS.

Update EFDS Mode of Contact (MOC) based on closing action.

Add the correlating EFDS Individual Return Note in the EFDS Permanent Instructions field. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡

Add all research and standardized notes to the EFDS employer notes.

Update/close case in the BMFIC database.

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

Add detailed BMFIC Notes to document specific research performed and used to make the final determination.

WOW - Withholding Only Work with no refundable credits

Exam - has refundable credits, and/or includes Sch C, E, F or F2106 ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

AQC - Automated Questionable Credits ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

Return does not contain an EFDS or IDRS note confirming a bad EIN

Return was pushed to scheme before a determination was completed

Push returns to STARS as CATG 7

Input EFDS Note: RIVO FRE PATTERN Multi/Limited Direct Deposit S Freeze

Monitor for the returns to hit STARS and use the STARS Mass Update Template to update the Disposition to "DD"

Identify returns in STARS CATG 7, DISP "DD" and run through the Return Integrity Compliance Services (RICS) IDT Tool to treat the return as IDT

Update STARS DISP to "CL"

Monitor returns filed for each lead for the current year

Monitor SSNs, potential suspicious Internet Protocol Addresses, and potential suspicious e-mail addresses received from Cyberfusion for the current year

Monitor prior year leads for potential IDT

Review all returns for possible IDT using the bank leads obtained from the saved SSRS Report spreadsheet. Continue reviewing the remaining lead data for fraudulent filing patterns.

Review Lead data, including some or all the following: SSN, Bank Account, IP address, e-mail address, name, and physical address.

Research SNAP, IDRS, EFDS and other systems to conduct lead research and identify fraudulent return patterns.

Address Leads differently based on the scenario. Refer to the Bank Leads Desk guide for current query processes.

Run SNAP queries daily based on identified lead fraud patterns.

Disposition all possible identity theft (IDT) returns to Process Status 30 (ACE/Adjustments) in EFDS. Input the following notes in EFDS:
Note 1: "RIVO FRE PATTERN"
Note 2: Summit (‘extlds Bank Leads-[SNAP QUERY NAME]”)

Determine if the lead needs to be imported

Import the lead into the database

Using all available research tools, determine if the case is Abusive or Not

Verify the Current Year (CY) return totals; if greater than 500 returns refer to the Lead Development Center (LDC) or if less than 500 returns refer to the Return Processing Center (RPC)

Double check database to make sure the EFIN is still active (if EFIN is inactive, review the comments to see if a referral is warranted)

Consider all EFINs associated with the firm being researched. Make a referral to the LDC/RPC for the firm, not an individual Preparer Tax Identification Number (PTIN)

Capture everything the firm filed, including Paper and Electronic Filing (ELF)

Check for open investigations in Criminal Investigations (CI) or Civil. Check everything in PS 29 for schemes

Pull Current Year (CY) and Prior Year (PY) return data using the EIN and/or PTIN and use those DLNs as the condition on the Preparer Query

Check for confirmed IDT. If there is any, send the case to EPSS for IDT instead of referring it as an abusive preparer

Fill out all required fields on the Abusive Preparer Program Template and complete a recommendation spreadsheet (LDC ONLY)

Forward your recommendation to the primary ERO Leads Management and Program Analyst for review. All documentation to support your recommendation to the LDC/RPC/RPO must be included in an Excel spreadsheet or template provided.

Forward the complete review to the program manager to forward the recommendation to the LDC, RPC, or the RPO for resolution.

Update the FRE database with all required fields accordingly.

Control File – (txt format) – this file contains company contact information pertaining to the data file

Data File – (xml file format) – this file contains the actual data records

Import the lead to the database

Process the Industry lead file

Review all returns in a workable process status (with stoppable refund stop dates) to identify possible identify theft returns (pattern matching)

Disposition all returns identified as possible ID theft returns to Process Status 30 (ACE/Adjustments) through Case in the Electronic Fraud Detection System (EFDS) with the following notes:
Note 1: "extlds Industry Leads OL"
Note 2: "RIVO FRE PATTERN"

Update LM - FRE with all required fields

Update the Lead Database Status to "Completed"

Move the lead files to the correct leads folder

Review and format the state lead file so that it can be imported into the Lead Management (LM) FRE database

Import the lead to the database

Review all returns that are not in a current IDT process status (with stoppable refund stop dates) to identify possible identify theft returns (pattern matching)

Update the LM FRE database with all required fields

Disposition all returns identified as possible ID theft returns to PS 30 (ACE/Adjustments) through CASE in the Electronic Fraud Detection System (EFDS) with the following notes:
Note 1: "extlds State Leads OL"
Note 2: "RIVO FRE PATTERN"

Update the lead status to "Completed"

Move the lead to the correct leads folder

The tax period associated with the TOP offset

The IRS determination:
Yes: All funds requested back - fraud or identity theft
No: No funds requested back - the offset is valid

Create the query

Research the accounts

Make the yes/no determination

Send the determination back to OCSE

Control File - (.txt file format) - this file contains company contact information pertaining to the data file

Data File - (.xlsx file format) - this file contains the actual data records

Review and format the lead file so that it can be imported into the Lead Management (LM) FRE database

Import the lead into the LM FRE database

Analyst assigns the lead to themselves in the LM FRE database

Analyze lead for potential revenue protection (pattern matching)

If applicable, disposition all returns identified to Process Status 30 (ACE/Adjustments) through CASE in the Electronic Fraud Detection System (EFDS) with the following notes
Note 1: "extlds ISAC leads OL"
Note 2: "RIVO FRE PATTERN"

Update LM FRE database with all required fields

Update the lead status to "Complete"

Respond to corresponding ISAC lead e-mail with results

DLN

Recovery Rebate Credit (RRC)

TPP Markers (TC 971 AC 124 or TC 971 AC 129)

TC 971 AC 123 with MISC field "TPP RECOVERY" , "FORCE TAC" , or "TAC AUTH ONLY"

TC 971 AC 123 with MISC field "TPP RP"

TC 971 AC 052 with MISC field "FULL YR PRN"

TC 971 AC 199 with MISC field "AMWEX60033 GATT EFDS"

Run Refile list through SNAP query to identify any cases meeting Social Media Scheme criteria. If any are found, mark them as "Send to FRIV" and take no further action.

Refile returns using CASE

Use IDRS to close NACHA controls and place the remaining controls in B status

Input a TC 971 AC 850 and a TC 290/.00 with priority code 1 and a post delay of 1

MFT32_REV_RL

MFT32_REV_IW

MFT32_REV_CV

EX: Excessive withholding: Pay 2 and Pay 3 are within 80% of each other

Send listing back to FIRE stating "FRP Cleared"

Input TC810 with Responsibility Code 4 to hold refund

Save the TIN list and manually monitor the list of questionable information returns using a SNAP query

Once the TC150 posts, refer to PS77 and add EFDS Note "FIRE Referral for Review"

Send a list of selected returns to the RIVPM PA POC quarterly

Refile returns as PS 28

Add EFDS Note "FRP cleared no frivolous issues identified"

Exclude returns with the following EFDS Notes and disposition to PS 31 (Refer to Ace) UNLESS they also have the EFDS Note "CONFIRMED - NOT SUSPICIOUS"
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

Move returns selected for Frivolous Return Program (FRP) treatment to PS 70 as a FRP Select

Add one of the following EFDS Notes:
"FRP Selected, Argument 1099 & RRP Filter"
"FRP Selected, Argument OTHER & RRP Filter"
"FRP Selected, Argument 2439 & RRP Filter"
"FRP Selected, SCH A Scheme"
"RIVO FRE PATTERN - Selected Frivolous Return ARG 1099"
"FF Filter"
"FRP Selected, FIRE Submission"
"FRP Selected - Social Media Scheme"

Create CCREQ via EITCRA to input TC 810 with a Responsibility Code 4 on potentially frivolous returns being referred

Open an IDRS control to 1486900000 with category code "FRP3" and activity of "INCOM/PS70"

If the return is considered identity theft, input EFDS Note "RIVO RSV IDT" and push return to ACE/ADJ

If the return contains unsubstantiated withholding, input EFDS Note "Unsubstantiated Withholding" and push return to ACE/EXAM

FRP Cleared: Input TC 811 to reverse -Q freeze and release refund

FRP Selected: Open an IDRS control to 1486900000, with category code "FRP3" and activity of "INCOM/DDB"

Open and close a control base on IDRS with the correct activity, category and received date

Create an Issue and Action History (en masse) on the FRP Master Database under Program Code 91853

Email completed workbook to FRP Clerical to address reject conditions and follow special instructions

Once FRP Clerical sends back the completed actions, add the new accounts to the FRP Master Database

Run "KDICALL" query and perform a GII INOLES run to build a PSL listing for the Data Processing Center (DPC) and email to FRP Clerical POC