IRS Logo

4.19.3  IMF Automated Underreporter Program

Manual Transmittal

August 26, 2016

Purpose

(1) This transmits revised IRM 4.19.3, Liability Determination, IMF Automated Underreporter Program.

Scope

IRM 4.19.3 effective on September 30, 2016 for tax years 2015, 2014 and 2013, supersedes IRM 4.19.3, effective September 30, 2015, for tax years 2014, 2013 and 2012. All IRMs remain in effect for related cases unless otherwise noted.

Material Changes

(1) Editorial changes were made throughout this section to clarify language and/or to update references, telephone numbers, and website addresses.

(2) Other changes were made throughout the IRM, as follows:

  • Updated money amounts to include TY 2015 amounts and remove TY 2012 amounts

  • Updated form line/column numbers to include TY 2015 line numbers and remove TY 2012 line numbers

  • Updated dates to include TY 2015 and remove TY 2012 dates

(3) IRM 4.19.3.1(11) - clarified instruction to better cover over deducted issues

(4) IRM 4.19.3.1(12) f - revised instructions to go to pc looKup option and provided reference in IRM 4.19.7

(5) IRM 4.19.3.1.1.1 - changed SNOD to Stat throughout subsection

(6) IRM 4.19.3.1.3(2) - corrected listing to remove IRM 8.20 and added IRM 8.20.6 and IRM 8.20.7

(7) IRM 4.19.3.1.5(1) and (2) - corrected information on electronically filed returns

(8) IRM 4.19.3.2.2(3) b Note - added to see Lead if TRDB information is missing

(9) IRM 4.19.3.2.5(1) - deleted original (1) renumbered remaining paragraphs; corrected information, TY 2006 and subsequent are available on AUR

(10) IRM 4.19.3.2.5(2) - corrected information; TY 2005 and prior are no longer available on AUR

(11) IRM 4.19.3.3.1(4) - added Caution for personally identifiable information

(12) IRM 4.19.3.3.1(4) - added Exception that HQ directed closures, using HQ Identified Program Problem closing process codes, do not require a case note to be input

(13) IRM 4.19.3.3.3(2) Note - removed instruction to transfer to Erroneous Refund Coordinator and added reference for instructions

(14) IRM 4.19.3.3.3.2(6) table, And column, 4th and 5th rows - revised instructions for CP 2000 phase responses on cases with "-I" Freeze Code

(15) IRM 4.19.3.3.3.2(9) c - corrected location of Exam contact information; deleted table

(16) IRM 4.19.3.3.3.2(12) - added designated Disaster Type information

(17) IRM 4.19.3.3.3.2(13) - corrected P- Freeze

(18) IRM 4.19.3.3.3.2(16) - added designated Disaster Type information and IRM reference

(19) IRM 4.19.3.3.3.2(18) - removed instruction to transfer to Erroneous Refund Coordinator and added reference for instructions

(20) IRM 4.19.3.3.3.3(6) - added new bullet to order 290-0 with PTC credit reference numbers

(21) IRM 4.19.3.4.1(14) - added example for clarity

(22) IRM 4.19.3.4.2(4) a - added income excluded per Notice 2014 - 7 to list of examples

(23) IRM 4.19.3.4.4(2) - corrected to remove reference to jurisdictions that recognize same-sex marriage and jurisdictions that do not

(24) IRM 4.19.3.4.5(2) a - added clarification

(25) IRM 4.19.3.4.6(2) - added instruction for cases that may require special or manual processing

(26) IRM 4.19.3.4.8.2(4) table, Then column, second box, step 1 - corrected wording to add if there is an indication of identity theft

(27) IRM 4.19.3.4.9(7) - removed instruction to transfer to Erroneous Refund Coordinator and added reference for instructions

(28) IRM 4.19.3.4.11(1) - added AUR payment posted with TC 670/610

(29) IRM 4.19.3.4.11(2) - removed instruction to use IAT "Erroneous Manual Refund" tool

(30) IRM 4.19.3.4.11.1 - information for each category of erroneous refund AUR will work was moved to a separate sub-section and re-written.

(31) IRM 4.19.3.4.11.2(1) through (3) - new, to provide information on and instructions for erroneous refunds which have been repaid

(32) IRM 4.19.3.7(1) - added that instructions must be used in conjunction with the general analysis procedures

(33) IRM 4.19.3.7.1.1(2) c - added Note concerning Medicare waiver (IHSS) payments

(34) IRM 4.19.3.7.1.1(6) a - added clarification that all elements of the IR should be marked “D” or “N”

(35) IRM 4.19.3.7.6.1(2) d Note - added new Note for NEC identified as nontaxable Medicare waiver or difficulty of care payments or excluded per Notice 2014 - 7

(36) IRM 4.19.3.7.6.1(10) step 2 - corrected field name

(37) IRM 4.19.3.7.10.3(2) - revised to include previously updated guidance

(38) IRM 4.19.3.7.10.4(4) - added Note and Caution regarding Form 5498 IRs with RCONV literal

(39) IRM 4.19.3.7.10.6.1(3) Note - included clarification for adding one month to the Payment Start Date

(40) IRM 4.19.3.7.10.6.1(3) 1st Example - added clarification for calculation

(41) IRM 4.19.3.7.10.6.1(3) 2nd Example - corrected information in example and added clarification for calculation

(42) IRM 4.19.3.7.10.7(6) - new instruction for statements with the return which explain re-characterizations

(43) IRM 4.19.3.7.10.7(9) a - added clarification that total distribution should be reported on Form 8606 line 8 or 16

(44) IRM 4.19.3.7.10.8(1) - for clarity, revised wording for definition of a lump sum distribution

(45) IRM 4.19.3.7.10.8(4) step 2 - revised instruction to enter lump sum tax amount in new field

(46) IRM 4.19.3.7.12.1(12) a and b - clarified instructions for determining when income is U/R and when it should not be pursued

(47) IRM 4.19.3.7.17(3)d - added "14 PAY" information and removed information for tax years 2008 and 2009

(48) IRM 4.19.3.7.18.1(3) d Note - added new Note for OTINC identified as nontaxable Medicare waiver or difficulty of care payments or excluded per Notice 2014 - 7

(49) IRM 4.19.3.7.20.1(3) 2nd Exception - revised to clarify screening of Form 982, line 2 amount

(50) IRM 4.19.3.7.20.1(9) - corrected to reflect extension of exclusion

(51) IRM 4.19.3.7.20.1(13) - added Reminder to toggle off Paragraph 72 when sending the Special Paragraph to request a statement of assets and liabilities

(52) IRM 4.19.3.7.23(4) - added two new Category Codes for STOCK

(53) IRM 4.19.3.7.23.1(1) - added two new Category Codes for STOCK

(54) IRM 4.19.3.7.23.1(5) - added CUSIP number and item description to list of items reviewed when determining duplicate IRs

(55) IRM 4.19.3.7.33(3) - revised for clarity

(56) IRM 4.19.3.8.6.1(3) - corrected TY 2014 amounts

(57) IRM 4.19.3.8.7.1(3) table ,Then column, 2nd row - added instruction do not create an IR

(58) IRM 4.19.3.9(4) - added Caution to advise it is necessary to re-enter exemption corrections if Return Value is accessed after corrections were made

(59) IRM 4.19.3.9(22) - added Reminder and IRM reference for cases requiring a manual interest calculation

(60) IRM 4.19.3.10.2.1(5) c - added Note when multiple Schedules E are filed it may be necessary to consider line 23c total

(61) IRM 4.19.3.10.3(6) - deleted original (6) and renumbered remaining paragraphs

(62) IRM 4.19.3.10.3(6) table, Then column, 3rd and 5th rows, step 3 - revised to delete original MIP IR

(63) IRM 4.19.3.10.3(7) table, Then column, 1st row - added Exception for cases where the TP claims less than $600

(64) IRM 4.19.3.10.3(7) table, Then column, 2nd and 4th rows, step 3 - revised to delete original MIP IR

(65) IRM 4.19.3.10.3.1(1) - removed Private Mortgage Insurance (PMI) from list of non-deductible MIP items

(66) IRM 4.19.3.13.4(3) - added new e for requirement that a qualifying child for child tax credit can’t file a joint tax return in the AUR year

(67) IRM 4.19.3.13.4(11) - added Reminder to enter amounts in the MISC CREDIT AMOUNT field when applicable

(68) IRM 4.19.3.13.5.1(2) - new, to provide instruction for when the TP provides Form 1098-T with an amount in Box 1 or similar documentation, or a signed detailed explanation of amounts paid

(69) IRM 4.19.3.14.3(1) b - removed information on the 10 percent additional tax on qualified education programs

(70) IRM 4.19.3.14.8(5) 2nd bullet - added clarification that input/verified amounts should consider losses on Form 1040, lines 13 and 17

(71) IRM 4.19.3.14.9(6) - added b and c to provide instructions for attached paper Form W-2 and ELF Form W-2 with amounts in Box 12, coded "B" or "N"

(72) IRM 4.19.3.14.9(8) - added Caution for Form 8959, line 19 totals which include amounts from Form W-2, Box 12

(73) IRM 4.19.3.14.9(12) - added table with instructions for TY 2013 and TY 2014 for sending PARAGRAPH 143 when the AdMT change is due to an incorrectly completed Form 8959

(74) IRM 4.19.3.14.10(2) and (3) - revised for clarity

(75) IRM 4.19.3.14.10(5) - added automatic Paragraph 153 information

(76) IRM 4.19.3.14.12(6) - added Caution to explain new PER RETURN fields for SIMPLE, ARCHER MSA, HSA, 5%, and NQDC and instruction to move reported amounts of these taxes from the OTHER MISCELLANEOUS TAXES C field to the appropriate PER RETURN and/or RECOMPUTED field(s)

(77) IRM 4.19.3.15.1.1(3) - added new (3) to address W/H on wages excludable per Notice 2014 - 7

(78) IRM 4.19.3.15.1.2(2) d Note - removed instruction to transfer to Erroneous Refund Coordinator and added reference for instructions

(79) IRM 4.19.3.15.3(7) - adding information regarding income excluded per Notice 2014 - 7

(80) IRM 4.19.3.15.3(15) b - adding information regarding income excluded per Notice 2014 - 7

(81) IRM 4.19.3.15.3(17) table, TY 2014 Column, 1st row - corrected amount

(82) IRM 4.19.3.15.6(1) - added Caution for processing changes that added APTC/PTC; added Note for telephone assistors, when a recomputed notice is needed and PTC recalculation is required, the assistor may request that the TP respond in writing; added Note regarding Form 8962, Part 5

(83) IRM 4.19.3.15.6(2) - added instructions for cases with no change to AGI

(84) IRM 4.19.3.15.6(3) step 8 - added new instruction to verify and correct, if necessary, all AMS pre-populated fields; renumbered remaining steps

(85) IRM 4.19.3.15.6(3) step 9 and 1st Note - corrected instructions to change field entries to zero

(86) IRM 4.19.3.15.6(3) step 11 - added Exception to printing calculation when there is no change to APTC/PTC and included instruction for case note to document this situation

(87) IRM 4.19.3.15.6(6) - added automatic Paragraph 62 information and Note regarding Paragraph 90

(88) IRM 4.19.3.16.10(7) - revised to include IRC

(89) IRM 4.19.3.17.1.1 - deleted subsection containing procedures pertaining to auto purge process for TY 2012 Batch Type 84100 - 299 Merchant Card cases only

(90) IRM 4.19.3.19.1(1) - deleted procedures pertaining to auto purge process for TY 2012 Batch Type 84100 - 299 Merchant Card cases only

(91) IRM 4.19.3.19.1(4) - corrected table IRM references related to AC 504, 505, 506, 523 and 524

(92) IRM 4.19.3.19.1(4) table, Then column, 8th row, step 5 - corrected instructions to advise taxpayer to make a report to their local police and the three major credit bureaus

(93) IRM 4.19.3.19.1(5) - clarified instruction; only a current AUR initiated TC 971 AC 522 PNDCLM for the AUR tax year should be reversed, if requested IDT documentation is not provided

(94) IRM 4.19.3.19.1(6) - added Caution for erroneous refund conditions and applicable IRM reference

(95) IRM 4.19.3.19.1(8) table And column, 3rd and 4th rows - revised instruction for CP 2000 phase cases with manual interest conditions

(96) IRM 4.19.3.19.1(10) - added IRM reference

(97) IRM 4.19.3.20.1(2) c - added instruction for Form 433-D

(98) IRM 4.19.3.20.1(2) e - deleted Reminder

(99) IRM 4.19.3.20.1(5) - added instruction for documents scanned into AMS/CIS by IDTVA

(100) IRM 4.19.3.20.1.7(4) - revised to include previously updated guidance

(101) IRM 4.19.3.20.1.8(1) 2nd Then column, step 2 - revised instructions for researching website

(102) IRM 4.19.3.20.1.8(1) 2nd Then column, step 3 - revised to include previously updated guidance

(103) IRM 4.19.3.20.1.8.1(3) - new to provide reference for MFJ return docketed cases when only one TP filed a petition with the U.S.Tax Court

(104) IRM 4.19.3.20.1.8.1(4) - added new non-statutory items

(105) IRM 4.19.3.20.1.8.1(5) - added to use the appropriate Hold Code to assessment instructions

(106) IRM 4.19.3.20.1.8.1(6) step 2 - new to issue letter to explain partial assessment

(107) IRM 4.19.3.20.1.8.1(7) - new to provide instruction for Shared Responsibility Payment

(108) IRM 4.19.3.20.1.8.1.1 - added new subsection for docketed cases when only one TP on a jointly filed return files a petition with the U.S. Tax Court

(109) IRM 4.19.3.20.1.17(5) - added information for Form 433-D

(110) IRM 4.19.3.20.1.18 - subsection has been rewritten and now only provides instructions for divorced/separated taxpayer cases when no signed consent to the tax has been received from either taxpayer

(111) IRM 4.19.3.20.1.18.1 - new subsection to provide instructions for divorced/separated taxpayer cases where only one taxpayer signed consent to the tax or each taxpayer signed separate consents, which are dated differently

(112) IRM 4.19.3.20.1.19(7) - added instruction for when TP states they are entitled to dependent exemption after initial request was denied

(113) IRM 4.19.3.20.1.21(1) - (4) - added Form 433-D to instructions for installment agreement requests

(114) IRM 4.19.3.20.1.23(3) and b and Note- removed bartering from instruction and b and deleted Note

(115) IRM 4.19.3.20.1.25(6) - added instruction for documents scanned into AMS/CIS by IDTVA

(116) IRM 4.19.3.20.1.25(9) - revised instruction to ensure the correct OPF code is used to record time spent on identity theft duties; deleted table and Note

(117) IRM 4.19.3.20.1.25.2(1) step 3 - added to paragraph that determination of referral to IDTVA can be an AUR case indicating a case has been referred

(118) IRM 4.19.3.20.1.25.2(4) - added clarification that instruction applies to cases not already assigned or referred to IDTVA

(119) IRM 4.19.3.20.1.25.2(8) - deleted instruction, per previously updated guidance

(120) IRM 4.19.3.20.1.25.3(5) table, Then column, 2nd row, step 6 - corrected instructions to advise taxpayer to make a report to their local police and the three major credit bureaus

(121) IRM 4.19.3.20.1.25.3.1(2) step 2 - corrected Identity Theft Tax Administration Source Term to PNDCLM

(122) IRM 4.19.3.20.1.25.3.1(4) - revised to include previously updated guidance

(123) IRM 4.19.3.20.1.25.3.1(5) table, Then column, 2nd row, step 6 and 3rd row, step 6 - corrected instructions to advise taxpayer to make a report to their local police and the three major credit bureaus

(124) IRM 4.19.3.20.1.25.3.1(5) - corrected table instructions for IDT AC 524 to close N/C

(125) IRM 4.19.3.20.1.25.3.1(7) step 6 - corrected instructions to advise taxpayer to make a report to their local police and the three major credit bureaus

(126) IRM 4.19.3.20.1.25.3.1(8) - revised to include previously updated guidance and added new step 4, to reverse a current AUR initiated TC 971 AC 522 PNDNCLM for the tax year, if the TP does not provide requested IDT documentation

(127) IRM 4.19.3.20.1.25.3.1(9) - revised instruction to apply only to responses that ignore previous claims of identity theft, corrected paragraph number and corrected Reason Code to NORPLY

(128) IRM 4.19.3.20.1.25.3.1(11) - corrected paragraph number

(129) IRM 4.19.3.20.1.25.4 - added new subsection for Return Preparer Misconduct (RPM); includes definition and guidance for phone and paper responses

(130) IRM 4.19.3.20.1.25.4(3) - removed instruction that clerical will prepare Form 3210

(131) IRM 4.19.3.20.1.25.4(4) - revised to remove requirement for a signed return

(132) IRM 4.19.3.20.1.25.4(4) step 1 - added instruction to flag Statutory Notice phase cases and include last day to petition on the flag; removed Note to send case note print

(133) IRM 4.19.3.20.1.25.4(4) step 7 - added instruction to complete Form 3210 and deleted requirement to open an IDRS control base

(134) IRM 4.19.3.20.1.25.4(4) step 8 - deleted requirement to open an IDRS control base

(135) IRM 4.19.3.20.1.25.4(5) - removed instruction to include case note print with referral package

(136) IRM 4.19.3.20.1.25.4(8) - deleted instruction related to opening an IDRS control base

(137) IRM 4.19.3.20.1.25.4(9) - deleted instruction related to opening an IDRS control base

(138) IRM 4.19.3.20.1.25.4(10) - deleted instruction related to opening an IDRS control base

(139) IRM 4.19.3.20.1.25.5 - moved AUR IDT Liaison Responsibilities to subsection 5

(140) IRM 4.19.3.20.1.25.5(1) a - added RPM referrals to AUR IDT liaison duties

(141) IRM 4.19.3.20.1.25.5(1) e - revised instruction to remove IRM reference

(142) IRM 4.19.3.20.1.25.5(2) - revised number of types of cases for AUR IDT liaison action

(143) IRM 4.19.3.20.1.25.5(2) step 2 - added new (2) step 2 for cases received from clerical with Form 14157 and/or Form 14157-A

(144) IRM 4.19.3.20.1.25.5(2) step 3 - added Form 14157 and Form 14157-A to list of criteria for referral to IDTVA

(145) IRM 4.19.3.20.1.25.5(3) - added information for Form 14157 and/or Form 14157-A

(146) IRM 4.19.3.20.1.25.5(6) - new instructions for referral of RPM cases

(147) IRM 4.19.3.20.1.25.5(7) table - added instruction for RPM throughout table

(148) IRM 4.19.3.20.1.25.5(8) - added reference for RPM referral instruction

(149) IRM 4.19.3.20.1.25.5(9) - added RPM information to IDTVA referral time frames, corrected reference for cases where a Statutory Notice has been issued, added Note regarding transfer/closure to Exam of cases with a response indicating "return as intended to be filed" ; renumbered remaining paragraphs

(150) IRM 4.19.3.20.2(6) Note - revised Note to ensure correct OFP code is used to report all time spent on phone calls that involve IDT

(151) IRM 4.19.3.20.2(7) - removed information regarding $250,000 cap for accepting faxed agreement (faxed signatures) to the tax increase and added Form 433-D to the list of signed faxed documents which can be accepted

(152) IRM 4.19.3.20.2.2(3) 3rd bullet - added Note that TPs may use "apartment," "unit," "number," etc., interchangeably when providing their complete mailing address

(153) IRM 4.19.3.20.2.2(7) - revised a and b into a table for Oral Disclosure Consent

(154) IRM 4.19.3.20.2.2(7) b - moved information to new (8) and revised to a step list

(155) IRM 4.19.3.20.2.2.1(4) - revised instructions for completing the Disclosure Verification screen and converted to a step list; added a Reminder regarding address verification, a Note regarding updating account information and a Caution to verify the case is open on AUR before updating the TP’s address

(156) IRM 4.19.3.20.2.2.1(5) - moved information in (7) to (5) and deleted remaining paragraphs in the subsection

(157) IRM 4.19.3.20.2.3(1) table, Function column, last row - corrected information to reflect the difference in hours for the W&I and SBSE toll free lines

(158) IRM 4.19.3.20.2.3(3) - deleted, Tele Tax services were discontinued January 1, 2016; renumbered remaining paragraph

(159) IRM 4.19.3.20.2.3(4) - removed reference to Tele Tax

(160) IRM 4.19.3.20.2.4(6) steps 1 and 2 - revised wording of steps to explain toll free number should be provided if the TP does not have internet access

(161) IRM 4.19.3.20.2.4(12) - added option to use the IAT Tracer tool

(162) IRM 4.19.3.20.2.4(17) - removed information regarding $250,000 cap for accepting faxed agreement (faxed signatures) to the tax increase

(163) IRM 4.19.3.20.2.4(23) - New for erroneous refunds discovered during a telephone call

(164) IRM 4.19.3.20.2.4.1(3) g - added reference to Self-Employment Tax (SE Tax) vs. Employee Share of FICA

(165) IRM 4.19.3.20.2.5(2) - added Reminder that TE must release the case after all actions are completed

(166) IRM 4.19.3.20.2.5(3) table, If column, 3rd and 4th rows - corrected BT 89004 - 89006 definition from IDT batches to suspense batches for cases requiring MFT 31 processing

(167) IRM 4.19.3.20.2.5(4) table, And column - removed $250,000 cap for accepting faxed agreement (faxed signatures) to the tax increase

(168) IRM 4.19.3.20.2.5(5) step 3 - revised to include instructions to print any PTC recalculation and fax to the clerical e-Fax of the controlling site, for it to be associated with the case file

(169) IRM 4.19.3.20.2.5(5) step 4 - new, to leave a case note to document the TP information for the recomputed notice

(170) IRM 4.19.3.20.2.5(5) step 5 - moved instruction to input correct PC to separate step and renumbered remaining step

(171) IRM 4.19.3.20.2.5(7) step 2 - revised to move 30-day extension information to new step 3

(172) IRM 4.19.3.20.2.5(7) step 3 - added to clarify specific extension date to provide

(173) IRM 4.19.3.20.3.1(4) - added new (4) to address wages excluded from income as nontaxable Medicare waiver or difficulty of care payments or excluded per Notice 2014 - 7

(174) IRM 4.19.3.20.3.3 - added to (2) for responses where the TP stated ordinary dividends are reported on Schedule D

(175) IRM 4.19.3.20.3.6(4) b - removed requirement for statement of timely rollover when Form 5498 is provided and corrected IRM references

(176) IRM 4.19.3.20.3.6(4) l- removed reference to Rollovers

(177) IRM 4.19.3.20.3.6(4) s - added to include previously updated guidance

(178) IRM 4.19.3.20.3.6(8) - added Part I, for clarification

(179) IRM 4.19.3.20.3.9(1) - added new n)

(180) IRM 4.19.3.20.3.11(2) - deleted (2), which included the requirement to complete and submit Form 8796 to request unemployment compensation verification from some states; renumbered remaining paragraph in subsection

(181) IRM 4.19.3.20.3.13(3) g - added new g) for TP responses indicating NEC is nontaxable Medicare waiver or difficulty of care payments or excludable per Notice 2014 - 7

(182) IRM 4.19.3.20.3.14(3) c - added new c) for TP responses indicating OTINC is nontaxable Medicare waiver or difficulty of care payments or excludable per Notice 2014 - 7

(183) IRM 4.19.3.20.3.16(3) c - added instruction to send a Special Paragraph to request statement of assets and liabilities and provided suggested verbiage

(184) IRM 4.19.3.20.3.23(3) step 1 Exception - added 1099-MISC to examples of original payer documents

(185) IRM 4.19.3.20.3.23(5) a - revised instruction to advise TP each line of Form SS-8 must be completed or form will be rejected, to complete and re-mail form, added reference to Out Calls - Calling the Taxpayer and instruction to hold in unit suspense for 60 days to wait for completed form

(186) IRM 4.19.3.20.4(4) - added Note beginning with TY 2015 PCs 39, 69 and 89 are no longer designated as IDT closures; these PCs will be used to process jointly filed return cases which require assessment to MFT 31 accounts established for each TP

(187) IRM 4.19.3.20.4(6) a and b - added Form 433-D

(188) IRM 4.19.3.20.5(1) - added reference to new subsection 4.19.3.20.5.1

(189) IRM 4.19.3.20.5(1) b - added instruction for Form 433-D

(190) IRM 4.19.3.20.5(1) b 2nd Note - removed information regarding $250,000 cap for accepting faxed agreement (faxed signatures) to the tax increase and added Form 433-D to the list of signed documents which can be accepted

(191) IRM 4.19.3.20.5(2) - added reference to new subsections 4.19.3.20.1.18.1 and 4.19.3.20.5.1

(192) IRM 4.19.3.20.5(9) - added instruction for Form 433-D

(193) IRM 4.19.3.20.5.1 - added new subsection for cases when only one TP on a jointly filed returns signs consent or both TPs sign consent on different dates

(194) IRM 4.19.3.20.6(5) step 4 - added Form 433-D

(195) IRM 4.19.3.20.6(6) step 4 - added Form 433-D

(196) IRM 4.19.3.20.6(7) step 4 - added Form 433-D

(197) IRM 4.19.3.20.6(8) Caution - added Form 433-D

(198) IRM 4.19.3.20.6(9) Note and e - added Form 433-D

(199) IRM 4.19.3.20.6(10) a and b - added Form 433-D

(200) IRM 4.19.3.20.6(11) c- added Form 433-D

(201) IRM 4.19.3.20.6.1(8) - added Form 433-D

(202) IRM 4.19.3.20.7(1) last bullet - added Form 433-D

(203) IRM 4.19.3.20.7(3) Note - corrected to remove reference to jurisdictions that recognize same-sex marriage and jurisdictions that do not

(204) IRM 4.19.3.20.7.1(2) a through d - revised to separate instruction for when TP states U/R belongs to another person

(205) IRM 4.19.3.20.7.1(3) - revised to separate instruction for when TP states income belongs to a minor child; renumbered remaining paragraphs

(206) IRM 4.19.3.20.7.1(5)b - corrected Letter 2626C paragraph information

(207) IRM 4.19.3.20.7.1(12) - revised to include previously updated guidance

(208) IRM 4.19.3.20.7.2(4) and (5) - added option to use the IAT Tracer tool

(209) IRM 4.19.3.20.7.5(7) table, 2nd Then box - added Exception that phone assistors may provide the information during a phone call, in lieu of sending Letter 2626C

(210) RM 4.19.3.20.7.5(8) - revised wording to add that identity theft information may have been provided during a phone call, in lieu of sending Letter 2626C

(211) IRM 4.19.3.20.8(3) - added Exception for entering the IRS received date for Letter 4314C when issued by a tax examiner

(212) IRM 4.19.3.20.8(7) d Note - added Form 433-D

(213) IRM 4.19.3.20.10(4) - added Note beginning with TY 2015 PCs 39, 69 and 89 are no longer designated as IDT closures; these PCs will be used to process jointly filed return cases which require assessment to MFT 31 accounts established for each TP

(214) IRM 4.19.3.20.10(4) Reminder - added Form 433-D

(215) IRM 4.19.3.20.10.2(2) - converted information to a step list and added PTC Credit Reference Number information

(216) IRM 4.19.3.20.10.2(3) step 3 - corrected to use Hold Code 2

(217) IRM 4.19.3.20.11(2) - new, to provide the list of items not included in the tax increase on the CP 3219A or Form 5564A

(218) IRM 4.19.3.21(7) - revised wording and instruction that notice review date should be provided weekly

(219) IRM 4.19.3.22.2.1(3) - added Caution beginning with TY 2015 PCs 39, 69 and 89 are no longer designated as IDT closures; these PCs will be used to process jointly filed return cases which require assessment to MFT 31 accounts established for each TP

(220) IRM 4.19.3.23.5(3) - revised to provide the notice date when copies of the Statutory Notice of Deficiency became available through the AUR system

(221) IRM 4.19.3.24(3) - clarified instruction for when a Recon with claim of identity theft should be referred to the AUR IDT liaison

(222) IRM 4.19.3.24(4) - new to provide IRM references for working Recons with claims of identity theft that can’t be referred

(223) IRM 4.19.3.24.2(2) - revised instruction to ensure the correct OFP code is used and deleted bullet list; added Reminder to consider cases involving IDT and cases that result/do not result in an adjustment to the AUR assessment, when determining the appropriate OFP code

(224) IRM 4.19.3.24.2(9) - removed Note under RC 068 concerning BT 81500 - 81999

(225) IRM 4.19.3.24.2.1(2) - added Caution not to transfer RECON cases

(226) IRM 4.19.3.24.4(2) Note - changed instruction to transfer case to yourself and the AUR system will assign IPC 9E

(227) IRM 4.19.3.24.4(3) - removed SRP from list of non-AUR issues to be routed elsewhere

(228) IRM 4.19.3.24.4(4) - revised routing instructions and deleted bullet list; moved information in first bullet to a Caution, added Note regarding Recons that may be retained and worked by the receiving site and moved information from second bullet to a new Exception

(229) IRM 4.19.3.24.5(11) table, 4th row, Then column - revised to add actions to take if the MFT 31 account(s) has been created

(230) IRM 4.19.3.24.5(13) - revised to include previously updated guidance

(231) IRM 4.19.3.24.5.1(1) step 1 - added Caution do not use the "Full Back Out" button to reverse the AUR assessment

(232) IRM 4.19.3.24.5.3(1) step 2 - corrected information to assignment of IPC 9E, rather than input of IPC 9E

(233) IRM 4.19.3.24.6(2) step 7 - changed instruction to transfer case to yourself and the AUR system will assign IPC 9E

(234) Exhibit 4.19.3-1 - added qualification that listed abbreviations are suggestions only and are not required to be used and added multiple abbreviations

(235) Exhibit 4.19.3-1 - added NOD and SNOD to list

(236) Exhibit 4.19.3-2 Statutory Notice - corrected list of items mailed

(237) Exhibit 4.19.3-3 - redesignated IPC S3 to Statutory Notice phase for jointly filed return cases when only one TP signed consent

(238) Exhibit 4.19.3-3 - redesignated IPC S6 for CP 2000 phase jointly filed return cases when only one TP signed consent

(239) Exhibit 4.19.3-3 - redesignated IPC S8 for Statutory Notice phase jointly filed return cases when only one TP filed a petition with the U.S. Tax Court

(240) Exhibit 5.19.3-4 - revised definition of PC 23

(241) Exhibit 4.19.3-4 - redesignated PC 39 to Statutory Notice phase for jointly filed return cases when one TP agreed at a later date - account split

(242) Exhibit 4.19.3-4 - redesignated PC 62 to Statutory Notice phase for jointly filed return cases when only one TP filed a petition with the U.S. Tax Court

(243) Exhibit 4.19.3-4 - redesignated PC 69 for CP 2000 phase jointly filed return cases when the TPs agreed on different dates - account split

(244) Exhibit 4.19.3-4 - redesignated PC 82 for Statutory Notice phase non-petitioning spouse default

(245) Exhibit 4.19.3-4 - redesignated PC 89 for Statutory Notice phase jointly filed return cases when one TP agreed and the case defaulted - account split

(246) Exhibit 4.19.3-5 - redesignated BT 89004 to Statutory Notice phase only one TP signature on the consent

(247) Exhibit 4.19.3-5 - redesignated BT 89005 to CP 2000 phase only one TP signature on the consent

(248) Exhibit 4.19.3-5 - redesignated BT 89006 to Statutory Notice phase only one TP filed a petition with the U.S. Tax Court

(249) Exhibit 4.19.3-5 - set BT 97 to Reserved

(250) Exhibit 4.19.3-7 - set Paragraph 113 to Reserved

(251) Exhibit 4.19.3-7 Paragraph 143 - corrected line number in body of paragraph

(252) Exhibit 4.19.3-7 - added Paragraph 153 for Excess Advance Premium Tax Credit repayment

(253) Exhibit 4.19.3-11 Notice Review Error Codes - added error code for Net Premium Tax Credit (PTC) amount

(254) Exhibit 4.19.3-12 Forms and Schedules - added Form 433-D

(255) Exhibit 4.19.3-12 Forms and Schedules - added Form 8796

(256) Exhibit 4.19.3-12 Forms and Schedules - added Form 14157 and Form 14157-A

(257) Exhibit 4.19.3-12 Forms and Schedules - added Schedules K-1 (Form 1041), Schedule K-1 (Form 1120S) and Schedule K-1 (Form 1065)

(258) Exhibit 4.19.3-20 - removed "Erroneous Manual Refund" tool from list of mandated IAT tools

(259) Exhibit 4.19.3-21 - added "Tracer" tool to list of other IAT tools

Effect on Other Documents

IRM 4.19.3, dated 09/04/2015 (effective 09/30/2015), is superseded. The following IRM Procedural Updates are incorporated: 15U1455 (dated 10-05-2-15), 15U1588 (dated 10-30-2015), 15U1797 (dated 12-15-2015), 15U1824 (dated 12-21-2015), 16U0327 (dated 02-12-2016), 16U0891 (dated 05-09-2016) and16U0983 (dated 05-26-2016), 13U1667 (dated 11-20-2013), 13U1716 (dated 12-10-2013), 14U0301 (dated 02-11-2014), 14U0573 (dated 03-28-2014), 14U0986 (dated 06-11-2014), 14U1060 (dated 06-27-2014), 14U1322 (dated 09-04-2014), 14U1560 and 14U1561 (dated 11-04-2014), 14U1681 and 14U1682 (dated 12-12-14), 15U0098 and 15U0099 (dated 01-13-2015), 15U0191 and 15U0195 (dated 01-27-2015), 15U0306 and 15U0307 (dated 02-12-15), 15U0568 and 15U0569 (dated 03-26-15), 15U0867 and 15U0868 (dated 05-15-2015), 15U0936 and 15U0938 (dated 06-01-2015), 15U0999 and 15U1002 (dated 06-10-2015), 15U1101 and 15U1102 (dated 06-30-2015), 15U1119 and 15U1120 (dated 07-06-2015) and 15U1210 and 15U1211 (dated 07-22-2015).

Audience

AUR tax examiners at Small Business/Self-Employed sites

Effective Date

(09-30-2016)

John Caggiano
Acting Director, Examination/AUR Policy
Small Business/Self Employed

4.19.3.1  (08-26-2016)
Overview of IMF Automated Underreporter

  1. This manual provides instructions for Automated Underreporter (AUR), the automated analysis and processing of potential underreported (U/R) and/or over-deducted (O/D) issues identified through information return (IR) matching.

  2. AVOID "AUDITING" RETURNS. All returns in the AUR inventory were previously screened for unallowable items and audit potential. They were not selected for action in either event. See IRM 4.19.3.20.1 (1), Taxpayer Responses - Overview.

  3. Underreporter cases are built from two primary sources:

    • The Individual Master File (IMF) which contains information reported to IRS by TPs

    • The Information Returns Master File (IRMF)

  4. The IMF file contains information reported on:

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

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

    • Form 1040EZ, Income Tax Return for Single or Joint Filers with No Dependents

  5. The IRMF information is matched with the IMF information to verify the TP reported all income as required. An AUR case results when computer analysis detects a discrepancy between the two data sources. Information in the IRMF file includes, but is not limited to:

    • Form W-2, Wage and Tax Statement

    • Form 1099-INT, Interest Income

    • Form 1099-DIV, Dividends and Distributions

  6. The information documents in the Form W-2 series (and Form 1099 if tax was withheld) should be attached to the tax return when it is filed.

  7. Taxpayers need not attach information documents in the Form 1099 (unless tax was withheld as noted above), Schedule K-1, Form 1098, and Form 5498 series to the return when it is filed.

  8. Discrepant cases are then categorized by type (wage, dividend, interest discrepancy, etc.) and underreported range (i.e., $200-499.99 tax change). These categories provide a logical system of criteria to select cases from the available inventory.

  9. After cases are selected from the inventory, they are worked according to procedures in this IRM.

  10. AUR Operations at seven campuses compile and control selected cases.

    1. Enterprise Computing Center at Martinsburg (ECC-MTB) sends tape information from the IRMF, Return Transaction File (RTF), Taxpayer Information File (TIF), and Payer Agent file. See IRM 4.19.3.5, Payer Agent, for additional information on the Payer Agent file. This information downloads to the AUR system.

      Note:

      Data from the TIF and Payer Agent file is updated weekly.

    2. A computer tape containing Form 4251, Return Charge-Out, data prints on a Campus printer. Each Form 4251 contains a social security number (SSN), tax year, and other case identification information, represented in a bar code and numeric format.

      Note:

      A Form 4251 will not be printed for Electronically Filed Returns (ELF) or Form 1040EZ (EZ).

    3. Federal Records Center (FRC) pulls and forwards returns to the Campus Files function for routing to Underreporter.

    4. Returns are controlled into the AUR system by scanning the bar code.

    Note:

    Electronically Filed Returns/Form 1040EZ (ELF/EZ) are considered virtual cases and are systemically built into screening batches.

  11. Tax examiners perform an in-depth analysis of each case and determine if the discrepant income or deduction(s) in question are satisfactorily identified or addressed on the tax return. If so, they close the case. If reasonable doubt remains, they send the TP either:

    • An AUR Notice, CP 2000 or

    • An Initial Contact Letter, CP 2501

    Note:

    The system auto generates CP 2000 Notices for select income categories.

  12. Process codes (PC) are used to provide an audit trail for AUR case processing. Integrated Data Retrieval System (IDRS) reflects PCs as pending actions until they post to the Master File.

    1. PC 0X (except 09) is computer generated to designate how and by which organization the case has been selected. PC 09 establishes an IDRS control base and reflects CP 2000 interest as pending.

    2. PC 20 adjusts Withholding (W/H), Excess Social Security/Railroad Retirement Tax (SSTAX) and Additional Medicare Tax withheld (MCTXW) only. A Letter 2893C is sent to advise the TP, as outlined in IRM 4.19.3.15.1.2, Withholding, SSTAX and Additional Medicare Tax Withheld - Miscellaneous.

    3. PC 30 establishes an IDRS control base whenever a CP 2501 is generated.

    4. PC 55 updates an IDRS control base when a CP 2000 is generated. An amended CP 2000 Notice also updates the existing IDRS control base.

    5. PC 75 and 77 updates the IDRS control base when a Statutory Notice of Deficiency (A CP 3219A and Form 5564-A, Notice of Deficiency - Waiver) is issued/generated.

    6. Other PCs are input during AUR processing. Select pc looKup in the Analysis Menu from the Case Analysis Screen. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Process Codes (PC).

  13. Internal process codes (IPC) are codes used in AUR processing and do not post to IDRS. See Exhibit 4.19.3-3, AUR Internal Process Codes.

  14. See Exhibit 4.19.3-1, Abbreviations (also see Glossary) and Exhibit 4.19.3-2, Glossary, for a list of abbreviations and definitions used in AUR processing.

  15. See Exhibit 4.19.3-12, Titles of Forms and Schedules, for a complete list of Forms and their titles.

4.19.3.1.1  (09-01-2013)
Taxpayer Advocate Service (TAS)

  1. Even though the IRS strives to improve its systems and provide better service, some TPs still have difficulty in getting solutions to their problems or appropriate responses to their inquiries. The purpose of the Taxpayer Advocate Service (TAS) is to give TPs someone to speak for them within the Service - an Advocate. TAS is an independent organization within the IRS whose employees assist TPs who are experiencing economic harm, who are seeking help in resolving tax problems that have not been resolved through normal channels, or who believe that an IRS system or procedure is not working as it should.

  2. Refer TPs to the Taxpayer Advocate Service (TAS) (see IRM Part 13, Taxpayer Advocate Service) when the contact meets TAS criteria (see IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria) and you cannot resolve the TP's issue the same day. The definition of "same day" is within 24 hours. "Same day" cases include cases you can completely resolve within 24 hours, as well as cases in which you have taken steps within 24 hours to begin resolving the TP's issues. Do not refer these cases to TAS unless they meet TAS criteria and the TP asks to be transferred to TAS. Refer to IRM 13.1.7.4, Same Day Resolution by Operations. When referring cases to TAS, use Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order), and forward to TAS in accordance with your local procedures. In addition provide the TP with the number for the National Taxpayer Advocate (NTA) toll-free line, 1-877-777-4778 or TDY/TDD 1-800-829-4059 and advise the TP that TAS is available if they are not satisfied with the service he or she received.

    Note:

    It is important that all IRS employees handle cases with the TP's best interest in mind.

4.19.3.1.1.1  (08-26-2016)
Taxpayer Rights Background and Importance of the Statutory Notice of Deficiency

  1. Taxpayers have the right to appeal an IRS decision in an independent forum. Taxpayers generally have the right to take their cases to court. Taxpayers also have the right to be informed. That is, they are entitled to clear explanations. Because the right to petition the U.S. Tax Court is a critical entitlement for TPs, it is important that employees understand and educate TPs about the foundation and impact of this right on TPs and the IRS.

  2. A Notice of Deficiency (NOD), also called a Statutory Notice of Deficiency (Stat), SNOD or "90-Day Letter" , is the legal notice in which the Commissioner determines the TP’s tax deficiency. IRC 6212, IRC 6213, IRC 6214, and IRC 6215 require that the IRS issue a Stat before assessing additional income tax, estate tax, gift tax, and certain excise taxes unless the TP agrees to the additional assessment. The Stat is a legal determination that is presumptively correct and consists of the following:

    1. A letter explaining the purpose of the notice, the amount of the deficiency, and the TP’s options.

    2. A waiver to allow the TP to agree to the additional tax liability.

    3. A statement showing how the deficiency was computed.

    4. An explanation of the adjustments.

  3. The purpose of the Stat is to:

    1. Ensure the TP is formally notified of the IRS’ intention to assess a tax deficiency.

    2. Inform the TP of the opportunity and right to petition the U.S. Tax Court to dispute the proposed adjustments.

  4. A Stat is issued for unagreed deficiencies of income, estate, or gift tax liabilities as well as for certain excise taxes.

  5. The Stat must provide the TP with notice of the Commissioner’s basis for determining the proposed deficiency.

  6. IRC 6212 requires that the IRS issue this notice to the TP’s last known address by certified or registered mail. Once the IRS issues this notice, the TP has 90 days (150 days if the Stat is addressed to a person outside the United States) from the date the Stat is mailed to file a petition in the U.S. Tax court. This 90-day (or 150 day) period is statutory and IRS employees cannot extend it.

  7. If the TP does not petition the U.S. Tax Court within the 90 days (or 150 days), the IRS is permitted to assess the deficiency, plus any additions to tax, after the 90 days (or 150 days) have passed. Although the IRS does permit reconsideration of examination assessments in some situations, the TP loses significant administrative and judicial avenues to dispute the IRS’ decision if he/she does not file a petition. Therefore, it is critical that IRS employees understand the importance of the Stat and be able to explain its ramifications to TPs. The U. S. Tax Court website (www.ustaxcourt.gov) provides substantial information on the petition process.

  8. If the TP does petition the U. S. Tax Court within the 90 days (or 150 days), the IRS is prohibited from making the assessment until after the court enters a decision. Once the TP petitions, the IRS will usually send the case to Appeals to try to settle the case prior to the U.S. Tax Court hearing date unless the TP has already been through the IRS’ administrative appeal process.

4.19.3.1.2  (01-27-2015)
Statute Awareness Program

  1. The Statute Awareness Program was created to minimize barred assessments and erroneous abatements. Because of the time involved in the processing of AUR issues, AUR employees must be particularly watchful for conditions that may indicate statute imminent cases.

  2. If the case is Statute imminent take the appropriate actions to prevent a barred assessment. If the case is identified during a phone call and the case belongs to another site, notify the Site immediately of the imminent statute (i.e., phone call, email, fax statute referral, etc.).

  3. Although the system generates the Statute Listing on a weekly basis to alert management to statutes in danger of expiring, employees must be personally knowledgeable of the rules that govern the assessment statute expiration date (ASED). These rules are outlined in IRM 25.6, Statute of Limitations.

    Note:

    The ASED can be found in the STATUTE EXP DATE field on the Tax Account screen, but the date should be verified.

  4. Each functional area should ensure that an adequate number of "Statute Specialists" are assigned.

4.19.3.1.3  (08-26-2016)
Related IRMs and Publications

  1. Before disclosing any tax information, you must be sure you are speaking with the TP or authorized representative. See the Taxpayer Authentication guidelines in IRM 21.1.3.2.3, Required Taxpayer Authentication and IRM 21.1.3.2, General Disclosure Guidelines, for further information.

    • See IRM 11.3.2.6.1, Leaving Information on Answering Machine/Voice Mail, for proper disclosure protocols before leaving messages on a TP's answering machine.

    • See IRM 11.3.1.11, Facsimile Transmission of Tax Information, for proper disclosure protocols before faxing confidential information to the TP.

  2. The following additional IRMs and publications/documents are listed as a convenience when AUR determines that in-depth research is required to resolve unusual technical issues not covered in AUR instructions, Form 1040 instructions and various publications. When reference to one of the related IRMs is required for AUR processing, the complete IRM reference is stated in this IRM.

    Note:

    Technical issues that occur frequently should be brought to the attention of the IRM 4.19.3, IMF Automated Underreporter, author for consideration for inclusion in this IRM.

    • IRM 2.3, IDRS Terminal Responses

    • IRM 2.4, IDRS Terminal Input

    • IRM 3.13.62, Media Transport and Control

    • IRM 4.13.1, Audit Reconsiderations, Introduction

    • IRM 4.19.2, IMF Automated Underreporter (AUR) Control

    • IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures

    • IRM 5.9, Bankruptcy and Other Insolvencies

    • IRM 8.20.6, Account and Processing Support (APS). Interim Actions

    • IRM 8.20.7, Account and Processing Support (APS). Closing Procedures

    • IRM 10.5, Privacy and Information Protection

    • IRM 11.3, Disclosure of Official Information

    • IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria

    • IRM 20.1, Penalty Handbook

    • IRM 20.2, Interest

    • IRM 21.1.1, Accounts Management and Compliance Services Overview

    • IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines

    • IRM 21.3.3, Incoming and Outgoing Correspondence/Letters

    • IRM 21.4.4, Manual Refunds

    • IRM 21.5, Account Resolution

    • IRM 21.6, Individual Tax Returns

    • IRM 25.15, Relief from Joint and Several Liability

    • Publication 17, Your Federal Income Tax (For Individuals)

    • Document 6209, IRS Processing Codes and Information

4.19.3.1.4  (09-01-2003)
AUR Security

  1. The AUR system design protects both TP data and the individual AUR users. ALL users are responsible for protecting TP information. Users should access ONLY the data needed to perform their duties, and not divulge TP information to any employee who does not have an official "need to know" . Users will report infractions to their managers immediately.

4.19.3.1.5  (08-26-2016)
Electronic Filing System

  1. Returns are filed electronically by electronic transmitters or from a home computer through a third party vendor (On-Line Filing). Initally individual electronic returns were transmitted to Andover (ANSC), Atlanta (ATSC), Austin (AUSC), Brookhaven (BSC), Cincinnati (CSC), Fresno (FSC), Kansas City (KCSC), Memphis (MSC), Ogden (OSC) and Philadelphia (PSC) Submission Processing Centers and Enterprise Computing Center - Memphis (ECC-MEM). Individual electronic returns are now transmitted to ANSC, AUSC, FSC, KCSC, PSC and ECC-MEM.

  2. All electronically transmitted returns are identified by a unique document locator number (DLN). The file location codes (FLC) shown below are for the electronic filing of individual income tax returns. The second number listed is the rollover FLC used when a site exhausts the regular FLC for a given processing date.

    Note:

    FLC information for electronically filed returns for TY 2013 and prior, is located in Document 6209, Sub Section 4.3, Campus and File Location Codes.

    • ANSC - 16; 14

    • AUSC - 76; 75; 21 for U.S. Possessions; 20 for International returns

    • FSC - 80; 90

    • KCSC - 70; 79

    • PSC - 30; 32

    • ECC-MEM - 72; 64

      Note:

      The system will not allow a user to order a transaction code (TC) 150 document with the above FLC codes.

  3. The TRPRT print is not considered the original return and is labeled "TRPRT PRINT DO NOT PROCESS" .

  4. Information such as loose forms, schedules, and correspondence CANNOT be attached to an ELF return. Do not use an attachment or association form.

  5. TRDB has a new Tab option: "Dotted…" . Dotted line literals are only available, on tax returns filed via Modernized e-File (MeF). MeF returns can be identified by a DLN Julian Date greater than 400. A TRDB screen, "Dotted…" tab display, with no entries, indicates either:

    1. The return was not filed via MeF (DLN Julian Date less than 400) or

    2. The MeF filed return included no dotted line literals

    Note:

    For a complete list of dotted line literals see Exhibit 4.19.3-18, Form 1040 Dotted Line Literals.

  6. TRDB has a new Tab option: "Attach" . When the user accesses the new "Attach" tab, each statement/attachment the TP electronically filed will be listed. There is no standard list of names/titles for the TP to use so the statement/attachment will be listed by the file name the TP used.

  7. No change PCs 15,, 47, 48, 51, 52, 70, 71, 72, 73, 91, 92 and 93 automatically generate a TC 290-0 for electronically filed returns with a "Y" in the SOURCE DOCUMENT ATTACHED? field in the Assessment window.

    Caution:

    If there is no information (loose forms, schedules or correspondence) to be associated with the refile DLN, enter an "N" in the SOURCE DOC field in the Process Code window.

4.19.3.1.6  (09-04-2015)
Integrated Automation Technologies (IAT)

  1. Automated Underreporter employees are mandated to use the Integrated Automation Technologies (IAT) tools. When an action must be taken on IDRS (unable to complete the action within the AUR system) and an IAT tool is available, AUR employees with access to IAT tools are required to complete the action using the IAT tool. The IAT tools assist the tax examiner with IDRS research and input. See Exhibit 4.19.3-20, Mandated IAT Tools, for a list of mandated IAT tools.

    Note:

    See Exhibit 4.19.3-21, Additional IAT Tools Available (Use Not Mandated), for additional IAT tools.

  2. If an IAT tool is not functioning properly, the case should be worked using IDRS. For more information on each tool see http://iat.web.irs.gov/.

4.19.3.2  (09-01-2009)
Controlling Work

  1. Underreporter cases to be analyzed by AUR tax examiners are assembled into batches, which are then divided into work units. See Exhibit 4.19.3-5, Batch Types. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures for the following windows used to control cases:

    • Assign Work Unit window

    • Release Work Unit window

    • Transfer Work Unit window

    • Accept Transfer window

    • Assign Case window

    • Release Batch window

    • Transfer Case window

    • Request Case window

    • Universal Work window

4.19.3.2.1  (07-22-2015)
Viewing Cases

  1. Each user may have clearance to view any case on the system. This function is necessary for any user answering TP phone inquiries.

  2. To view any case take the following actions:

    1. Select the appropriate Tax Year from the AUR Year menu.

    2. Select reView from the AUR Main menu.

    3. Select View case from the Review menu.

    4. Input the SSN to be viewed.

    5. Click on the PHONE CONTACT field if viewing the case due to a TP phone contact. The AUR program will extract telephone contact data based on this entry.

  3. The only entries that can be updated on the cases are:

    • Telephone number and contact hours on the Tax Account screen

    • Case notes on the Case Note window

    • Update address

    • Update third party contact

    • Update power of attorney (POA)

    • Action Required (Universal case) box

      Note:

      Any other changes will not save to the database.

  4. The Print menu option may be accessed when the user selects View Case from the Review menu.

4.19.3.2.2  (08-26-2016)
Lost Cases

  1. When an SSN is assigned to a batch, and the corresponding paper case is missing, the case is considered a "lost case" .

  2. When a lost case is identified:

    1. Select the Process Code window. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Process Code Menu.

    2. Input IPC LC (Lost Case).

      Caution:

      If the work unit contains both copies of Form 4251, it is not a lost case. Input IPC "0A" (Return Request).

    3. The AUR system moves the SSN to Batch Type (BT) 98XXX (immediately).

  3. If the missing case is:

    1. A Form 1040EZ, use the Form 1040EZ information at the bottom of the Case Analysis screen to work the case.

    2. An ELF return, see IRM 4.19.3.1.5, Electronic Filing System.

      Note:

      The system will not allow a user to input IPC LC when the case is a Virtual return. If there is no TRDB information for a case, see your Lead.

  4. Some cases are found to be missing after the work unit has been released by the tax examiner and is being disassembled by the Control Function. The Control Function notates "Lost Case" on a case transfer sheet and routes the case transfer sheet to the Lead. The Lead contacts the tax examiner who released the case.

    1. If the case is found, the tax examiner accepts and reworks the case on the system.

    2. If the case is not found, the tax examiner accepts and attempts to rework the case on the system, using a substitute Form 4251. If the case file contents are necessary to work the case, input IPC LC on the Process Code window and discard the case history/transfer sheet.

      Note:

      In an effort to eliminate unnecessary paper inventory, substitute charge outs should only be printed if absolutely necessary.

4.19.3.2.3  (10-04-2010)
Wrong Pulls in Screening (WP)

  1. If the original tax return DLN and the Form 4251 DLN do not match:

    1. Leave the Form 4251 attached to the return.

    2. Input IPC "WP" and notate "WP" on the Form 4251.

    3. Leave the return in the work unit.

    The return is sent to FRC after the batch is disassembled.

  2. If the DLNs match, but the TP's name is different, close the case with PC 29.

  3. If the tax return is for the incorrect tax year (the DLNs match, but the TY is different), close the case with PC 29 and route the return to be processed to the correct tax year.

4.19.3.2.4  (09-01-2009)
Case History

  1. The Case History screen is used to determine the location or status of a particular case. If the case is:

    1. Assigned to your unit, select the Unit Case History window from the Case Analysis menu.

    2. Assigned anywhere on the AUR system, select the Case History window (Analysis) using the Review option on the Main menu.

    See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Viewing Cases.

4.19.3.2.5  (09-30-2015)
Archived Cases

  1. For TY 2006 and subsequent years, access the case data using View Case in the appropriate tax year on the system.

  2. For TY 2005 and prior, if information on the case is needed, the case must be ordered from files.

4.19.3.3  (09-01-2003)
Case Information

  1. Each AUR case contains information for one tax account.

4.19.3.3.1  (08-26-2016)
Underreporter Cases

  1. A case where a paper Form 1040 or Form 1040A was filed has an individual income tax return present in the case. If the Form 4251 is batched without an original tax return, order the TC 150 return on the Tax Account screen.

    Note:

    A Form 4251 is not generated for Virtual returns. Local management can determine whether there is a need for the report to be printed. Tax examiners may notate the applicable PC/IPC next to the corresponding SSN on the work unit listing for Virtual returns.

  2. Some cases may have an amended return, Form 1040X, Amended U.S. Individual Income Tax Return, attached to the original individual tax return.

    1. If the amended return was not processed, include it in the resolution of the case. Leave the amended return attached to the original return when the case is closed.

    2. If the amended return was processed, consider it in the AUR case resolution and refile separately when the case is closed.

  3. All cases have online data which displays in a series of screens. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures, for more information.

  4. An action trail MUST be made part of the case data whenever significant actions are taken. Use either the IR Note window or the Case Note window. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Case Notes and Information Return Notes.

    Exception:

    At times HQ may direct closure of a case or cases with one of the HQ Identified Program Problem closing process codes. Case notes are not required on these cases.

    Caution:

    Do not include personally identifiable information (PII) in IR notes or case notes.

    Note:

    IR notes and Case notes are part of the official case file and may be viewed by the TP.

  5. Form 4251 is attached to a return when it is pulled from the files at the Federal Records Center.

    Note:

    Virtual returns will have an individual work unit listing rather than a Form 4251. Local management can determine whether there is a local need for the report to be printed.

    1. Form 4251 MUST remain with the paper return when the case is closed.

    2. Notate the applicable PCs and IPCs on Form 4251.

    3. Keep the Form 4251 in the front of the case file with the bar code visible.

4.19.3.3.2  (09-01-2006)
Case Analysis Screen

  1. The Case Analysis screen is the main screen used by tax examiners for the analysis of AUR cases. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Case Analysis Overview.

  2. Certain Transaction Codes, Freeze Codes, or Indicators may require research, referral, or other specific actions. When these conditions are present, the Message window displays on the Case Analysis screen when the SSN of the case is entered. If this window displays, review the information on the Tax Account screen to determine the appropriate action to take.

  3. Within the Case Analysis screen various windows display, dependent upon the issues involved on an individual case. You must work certain windows in the proper order if two or more of them are present. The twelve windows and their proper sequence are:

    1. Misc Adjust/Sch C Exp

    2. FICA Tax

    3. SST on Tips

    4. SE Tax

    5. SEP/KEOGH/SIMPLE

      Note:

      HSA/AMSA Contribution/Deduction. Although there is no HSA/AMSA window, this income type must be worked in the proper order. See IRM 4.19.3.8.2 (10), Health Savings Account (HSA) or Archer Medical Savings Account (AMSA) Deduction.

    6. SSA/RRB

    7. IRA (CONTR)

    8. Savings Bond Exclusion

    9. EPAB

    10. Student Loan Interest Deduction (SLID)

    11. Tuition and Fees

    12. Domestic Production Activity Deduction

    Example:

    The SE Tax window has been worked. Subsequently, the SST on Tips window is worked. The system displays a warning message describing the proper sequence. You must access the SE Tax window again to complete the proper sequence before going to the Return Value screen.

4.19.3.3.3  (08-26-2016)
Tax Account Screen

  1. The Tax Account screen displays posted information from the TP's Master File account. It contains the name and address, Date of Birth (DOB) for both primary and secondary TPs, return amounts, transactions, and other current data (including Reason Codes (RC)). The data is downloaded to the AUR system from ECC-MTB. The TP's phone number and hours of contact can be entered. This screen is used to order a return if the related adjustment has posted to the account. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures, - Tax Account Screen.

  2. Compare the Adjusted Gross Income (AGI) and Taxable Income (TXI) on the return with the AGI/TXI on the Tax Account screen. A mismatch could be due to a TP and/or processing error. The AUR Function is responsible for issuing a CP 2000 to correct these types of errors.

    Note:

    If the processing error resulted in an erroneous refund, see IRM 4.19.3.4.11, Erroneous Refunds, for further information.

  3. If the AGI on the return and the AGI on the Tax Account screen do not match, the TP/processing error may be found on page 1 of the return.

    1. The system displays the AGI as determined from Master File.

    2. Verify the AGI on the Tax Account screen.

    3. If appropriate, use the MISC ADJUSTMENT/SCHEDULE C EXPENSE window to account for the discrepancy. See IRM 4.19.3.4.9 (1), Miscellaneous.

      Exception:

      If the TP(s) AGI/TXI return amounts were correct, a processing error changed the AGI/TXI, and the TP(s) did not receive a Math Error Notice because the change was below tolerance, correct the AGI (by entering the TP's original amount in the AGI window). Leave a case note explaining the action taken.

  4. If the Tax Account screen displays an asterisk in the NEW TRANS field, a new TC has been added since the case was last analyzed. When an asterisk displays:

    1. Review the TC to determine if any action is required.

    2. Click on the asterisk and press ENTER to indicate the TC has been considered while working the case.

      Note:

      The system automatically totals TC 640 payments and displays a prompt: "Should amount be entered in Return Value Screen?" .

  5. If the Tax Account screen displays the Indicator KITA (Killed in Terrorist Action) or HSTG (Hostage in Terrorist Action) in the KITA IND field, or if the system displays the message "KITA/HSTG indicator present. Close case." , use PC 18 to close the case.

    Note:

    Because TP contact has not been made, no further actions are needed.

  6. If the Tax Account screen displays the indicator PDT (Potentially Dangerous Taxpayer), see IRM 25.4.1, Potentially Dangerous Taxpayer, for additional information. If the Tax Account screen displays the indicator CAU (Caution Upon Contact), see IRM 25.4.2, Caution Upon Contact Taxpayer.

4.19.3.3.3.1  (09-01-2013)
Power of Attorney (POA)

  1. A POA is on file when an indicator is displayed in the Centralized Authorization File (CAF) Indicator field. The indicator is either alpha or numeric. See Document 6209, IRS Processing Codes and Information, for the applicable POA indicators. A TC may also be present.

    • TC 960 is a CAF Indicator (POA on file)

    • TC 961 reverses the CAF Indicator (POA revoked)

  2. Prior to the issuance of a CP 2000/CP 2501 or Recomputation Notice, the CAF is automatically researched for the valid POA's name and address.

  3. If issuing a notice, and there is a valid POA on file:

    1. A copy of the notice is automatically created for the POA. (If there are multiple POAs, the notice is only created for the first two POAs authorized to receive notices per the CAF.)

    2. PARAGRAPH 178 automatically generates on the CP 2000/CP 2501 and Recomputation Notice to inform the TP that a copy is being sent to the POA. See IRM 4.19.3-7, CP PARAGRAPHS.

  4. If an original POA is found attached to the tax return (not detached during processing), see IRM 4.19.3.20.1.22, Letters From a Third Party and Authorization From a Valid Power of Attorney (POA) and IRM 21.3.7, Processing Third Party Authorizations onto Centralized Authorization File (CAF), for instructions on determining validity.

  5. Disregard invalid POAs.

  6. Consider "valid" POAs approved.

    Note:

    CAF will only accept the Form 2848 with a revision date of October 2011 or later.

    1. Make a photocopy for the AUR case file.

    2. Forward the original to the CAF Unit for processing.

    3. Input the POA information on the Update Address window (POA). See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Updating Address Information.

      Note:

      A foreign address requires a period ("." ) in the first position of the State field.

4.19.3.3.3.2  (08-26-2016)
Freeze Codes

  1. If certain freeze codes are present on the tax module, a message window displays on the Case Analysis screen when the SSN of the case is entered. Access the Tax Account screen to determine the proper action.

  2. If there is a Freeze Code "-A" , the case is worked by AUR. See IRM 4.19.3.3.3.3 (15) and (16), Transaction Codes Reflecting Tax Liability, for further instructions.

  3. A Freeze Code "-C " on the account indicates the TP was involved in a military operation in a designated combat zone and may be entitled to special tax treatment.

    1. The -C freeze remains on the TP's account even after the TP is no longer in the combat zone. If a case has a -C freeze present additional research is necessary to determine the TP's combat zone status.

    2. During screening if you receive the message: "12/31/9999 date is present, possible combat zone - See IRM 4.19.3" , close the case using PC 15.

    Research IDRS CC IMFOLE for the Combat Indicator.

    If the Combat Indicator is Then
    1 The TP is still serving in a combat zone. Close the case using PC 15.
    2 The TP is no longer serving in a combat zone. Manual Interest computation is required in order for the notice to generate.

    Note:

    During screening, close the case with PC 27.

  4. Freeze Code "-E" (TC 810 - code "4" ) indicates the case is currently being reviewed by the Frivolous Return Program (FRP). Freeze Code "-E" is placed on all refundable years when the TP has been identified as filing a frivolous return with a Form 1099-OID, Original Issue Discount. In either situation, refer the case to the local FRP coordinator who will provide instructions to either continue processing or to transfer case. If FRP wants the case transferred, use PC 13.

  5. Freeze code "F-" (TC 971 - action code (AC) 089) freezes the entire account and most adjustments will unpost. Refer the case to the local FRP coordinator who will provide instructions to either continue processing or to transfer case. If FRP wants the case transferred, use PC 13.

    Caution:

    Identity theft cases with a F- freeze should be referred with the proper documentation after the TP has provided the Form 14039 for identity theft.

  6. If a Freeze Code "-I" is present on Tax Account screen,

    If case is in And Then
    Screening phase   Close case with PC 27.
    CP 2501 phase ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Close case with PC 51, see IRM 4.19.3.19.1, No Response BT 84.
    CP 2501 phase ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Continue processing.
    CP 2000 phase ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Continue processing, see IRM 4.19.3.19.1, No Response BT 84.
    CP 2000 phase ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Close case with PC 73, IRM 4.19.3.19.1, No Response BT 84.
    Stat phase   Continue processing.

    See IRM 4.19.3.16.10, Manually Computed Interest for the CP 2000, for additional information.

    Note:

    If a Manual Interest computation is required, and the tax examiner attempts to input Process Code (PC) 55, 57, 59, or 95 or Internal Process Code (IPC) RN or SR, the system alerts the tax examiner that IPC MI is required.

  7. If a Freeze Code "I-" is present on Tax Account screen during screening close case with PC 27. After a notice has been issued and the case results in a refund then a Manual Interest computation is required see table in (6) above. See IRM 4.19.3.16.10, Manually Computed Interest for the CP 2000, for additional information

    Note:

    If the Return Value screen reflects a refund, and there is no "I-" freeze code present, input zero (0) in the MANUAL INTEREST field and continue processing. Do not input IPC "MI" .

  8. A Freeze Code "L-" identifies that an Innocent Spouse claim (Form 8857, Request for Innocent Spouse Relief) has been filed and is set by input of TC 971 AC 065. The TC 971 AC 065 also generates a TC 130 freezing the entire account for the non-requesting spouse.

    1. During the Screening phase, close the case using PC 28.

    2. During the Response phase, refer to , IRM 4.19.3.20.1.20.1Innocent Spouse Relief Cases - Tax Examiner Instructions, for more information.

  9. Freeze Code "-L" (Audit Indicators TC 420 or 424, not reversed by TC 421) indicates the return is currently being requested or audited by Exam. During case analysis (screening phase), research IDRS CC TXMODA for a pending TC 421 that will reverse the "-L" freeze. If there is a reversal, continue normal processing.

    If there is No reversal, research IDRS CC AMDISA for the CURRENT-STATUS-CD/DATE field. The CURRENT-STATUS-CD/DATE field determines case action as follows:

    1. If the AMDISA CURRENT-STATUS-CD/DATE field is "33" or "34" the case is controlled by the Tax Equity and Fiscal Responsibility Act (TEFRA) function. Continue normal processing. Do not use the Exam transfer PCs to close TEFRA cases.

    2. If the AMDISA CURRENT-STATUS-CD/DATE field is "06" AWAITING CLASSIFICATION, the cases have not yet been screened for possible selection for examination. Do not use the Exam transfer PC’s to close the case, continue normal processing.

    3. If the AMDISA CURRENT-STATUS-CD/DATE field is "08" , use the primary business code (PBC), secondary business code (SBC) and employee group code (EGC) to locate the correct Exam contact by accessing the EXAM Employee Group Code (EGC) Contacts, under the Who/Where Tab on SERP, then select Employee Group Code (EGC) Listing Contacts.

    4. If Exam wants the case use either PC 11 or 12 as appropriate to transfer the case to Exam. If Exam does not want the case, continue with normal processing.

      Note:

      To determine if the case is a Field or Campus audit see Document 6209 (http://serp.enterprise.irs.gov/databases/irm.dr/current/6209.dr/6209ch12.5.3.htm).

    5. If the conditions in a-c above are not met, input PC 13 (Case Analysis phase) to transfer the case to Exam.

  10. If the Freeze Code "-L" open TC 420/424 is present after an AUR notice has been issued, take the following actions:

    1. Research IDRS CC AMDISA to determine the primary business code (PBC), secondary business code (SBC) and employee group code (EGC).

    2. Use the PBC, SBC and EGC information from AMDISA to locate the correct Exam contact by accessing one of the following websites: If the PBC is 301-309:
      http://mysbse.web.irs.gov/exam/mis/contacts/empgroupcode/default.aspx
      all others:
      EXAM Employee Group Code (EGC) Contacts, under the Who/Where Tab on SERP.

    3. If the case is in CP 2501 or CP 2000 phase and Exam wants the case, input PC 38 (CP 2501) or PC 64 (CP 2000). Prepare Form 3210, including the appropriate Exam contact information, and leave it with the case

    4. If the case is in Statutory Notice phase and Exam wants the case, see (11) below.

    5. If Exam does not want the case, leave a case note and continue normal processing. If an assessment is needed see IRM 4.19.3.20.10, Assessments.

  11. If Exam wants the case, take the following actions:

    1. Allow the statutory period to expire.

    2. Access the Assessment window and enter an "N" in the SOURCE DOCUMENT ATTACHED field and the appropriate priority code.

    3. Commit the Assessment window.

    4. Prepare Form 3210, including the appropriate Exam contact information, and leave it with the case

    5. Input PC 94 and release the case.

  12. A Freeze Code "-O" on the Tax Account screen, is a Disaster Indicator set by TC 971 AC 086 or 087. This would be designated a Disaster Type 4. See IRM 4.19.3.4.6, Declared Disaster Areas, for more information.

  13. Freeze Code "P-" indicates the case may be assigned in the FRP or Integrity and Verification Operation (IVO) held the refund. Research IDRS.

    If And Then
    TC 599 AC 17 or 89 is present FRP has an open control (will show AUDT in control base) Refer the case to the local FRP coordinator who will provide instructions to either continue processing or to transfer case. If FRP wants the case transferred, use PC 13.
    TC 720 and TC 971 with either AC 052, 134, 617 is present   Close the case no change using PC 28, 52, 71, or 92 as appropriate. If a notice was issued see IRM 4.19.3.20.1.25.3 (3), IDT Claims - Initial Handling
    TC 570 with TC 971 AC 199 is present   Close the case no change using PC 28, 52, 71, or 92 as appropriate. If a notice was issued see IRM 4.19.3.20.1.25.3 (3), IDT Claims - Initial Handling.

    Caution:

    Take no action to release the "P-" freeze. The IDRS history may reflect "DO NOT REFUND" .

  14. ≡ ≡ ≡ ≡ ≡ ≡ ≡ "" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  15. A Freeze Code "-R" on Tax Account screen reflects IVO or Taxpayer Protection program (TPP) involvement and is identified with TC 971 AC 052, AC 134, AC 617 or TC 570 with TC 971 AC 199 which indicates a frozen refund. Close the case no change using PC 28, 52, 71, or 92 as appropriate. If a notice was issued see IRM 4.19.3.20.1.25.3 (3), IDT Claims - Initial Handling.

  16. A Freeze Code "-S " replaces the assignment of computer condition codes to identify tax returns filed within a declared disaster area and is set with a TC 971 AC 688. The -S freeze does not suppress notices. Continue normal case processing. This would be designated as a Disaster Type 2. See IRM 4.19.3.4.6, Declared Disaster Areas, for more information.

  17. If a Freeze Code "-T" is present on Tax Account screen, there is a ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ entity freeze on the account, used for monitoring purposes only. Continue normal case processing.

  18. If there is a Freeze Code "-U" , see IRM 4.19.3.4.11, Erroneous Refunds, for further information. Freeze Code "-U" indicates the Erroneous Refund area is monitoring a case for available credits and a closure may release needed credits.

  19. If there is a Freeze Code "-V" and/or TC 520, a Bankruptcy condition is present. If identified on the Tax Account screen;

    1. During Case Analysis (i.e., pre-notice contact), close the case using PC 27.

    2. During Response phase (after the TP has been issued an AUR Notice), see IRM 4.19.3.20.1.10, Bankruptcy Procedures - Responses.

  20. If there is a Freeze Code "-W" with closing code (cc) 81, or cc 84 and/or a TC 520 (not reversed by TC 521 or 522), a Bankruptcy condition is present. If identified on the Tax Account screen;

    1. During Case Analysis (i.e., pre-notice contact), close the case using PC 27.

    2. During Response phase (after the TP has been issued an AUR Notice), see IRM 4.19.3.20.1.10, Bankruptcy Procedures - Responses.

  21. A Freeze Code "-Y " on the account indicates that the TP filed an Offer-in-Compromise with the service. See IRM 4.19.3.3.3.4 (6), (11) and (12), Other Transaction Codes and Math Error Codes, for additional information.

  22. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "≡ ≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    Note:

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

  23. If a Freeze Code other than those explained in (2) through (22) above, are indicated on the Tax Account screen, refer to Document 6209, IRS Processing Codes and Information.

4.19.3.3.3.3  (02-12-2016)
Transaction Codes Reflecting Tax Liability

  1. A TC 150 indicates a return was filed and posted to the Master File. The TC 150 amount is the tax assessed when the original return was filed.

  2. TCs 290 and 300 indicate additional tax was assessed after the original return was filed. The system adds these amounts to the TC 150 amount to determine the total tax per return. If the TC 290/300 source document is present, determine if the adjustment source document (Form 5147, Form 5344, Examination Closing Record, Form 4700, Examination Workpapers, amended or duplicate return) resolves the U/R issue(s).

    • A TC 300-0 with a corresponding TC 764, TC 768, or TC 765 indicates Exam adjusted EIC with no change to AGI or TXI. See IRM 4.19.3.15.3, Earned Income Credit, for further instructions on EIC.

    • Certain modules where an overstatement of estimated tax payments or W/H credits resulted in a refund, offset, or a credit elect may show as assessed using TC 290, RC 051, for the amount of the overstatement. These accounts will generally not contain a TC 807.

  3. TCs 291 and 301 indicate a portion or all of a previously assessed tax was abated after the original return was filed. The system subtracts these amounts from the TC 150 amount to determine the total tax per return. If the TC 291/301 source document is present, determine if the adjustment source document (Form 5147, Form 5344, Examination Closing Record, amended or duplicate return) resolves the U/R issue(s). If the AGI/TXI on the Tax Account screen:

    1. Differs from the tax return, order the TC 291/301 document without screening for income discrepancies.

    2. Matches the tax return, screen for income discrepancies and see (5) below.

  4. Order the missing TC 290/291 or TC 300/301 adjustment source document

    1. Before issuance of a notice or

    2. Prior to taking a PC 20 action.

  5. Do not order the missing TC 290/291 or TC 300/301 source document for the following situations:

    1. The difference between the AGI/TXI on the return and the AGI/TXI shown on the Tax Account screen matches the total discrepant amount within ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ . Consider the amount in question reported and close the case if there are no other related issues (i.e., Self-employment tax (SE tax)), 10 percent tax, etc.)

      Note:

      To calculate the TP's reported self-employment income, divide the amount shown in the SE INCOME fields on the Tax Account screen by .9235 (92.35 percent).

    2. The adjustment changes the amount(s) or item(s) back to the original figures on the return (changes may have resulted from a math error code or unallowable code). The AGI, TXI and Tax (TC 150 minus TC 291) should equal the amounts on the original tax return.

    3. W/H, excess SSTAX, or additional MCTXW is the only issue (PC 20 criteria) and the adjustment does not have a TC 806/807 or TC 766/767 with credit reference number (CRN) 252 present.

    4. A TC 806/807 or a TC 766/767 with CRN 252 is the only change (there is no change to the AGI or TXI) and W/H or excess SSTAX is not an issue.

      Caution:

      Certain modules where an overstatement of estimated tax payments or W/H credits resulted in a refund, offset, or a credit elect may show as assessed using TC 290, RC 051, for the amount of the overstatement. These accounts will generally not contain a TC 807. Send a Special Paragraph using the following verbiage as an example "The other taxes as shown on this notice include the previous change made to your federal income tax withheld."

    5. The adjustment is a TC 291/301 when the AGI, TXI and the tax has been reduced to zero. Close case with PC 28 (these are generally filing status changes or incorrect SSN).

  6. Order the TC 290-0 adjustment source documents when one of the following corresponding TCs is present:

    • TC 976/977

    • TC 971 AC 010, 012 through 016 or 120

    • TC 806/807 with the TC 290-0

    • TC 764/765/768

      Exception:

      Do not order the TC 290-0 adjustment source document for changes to EIC and there is no change to AGI or TXI.

    • TC 766/767 with CRN 336

    • TC 766/767 with CRN 252

    • TC 766/767 with CRN 260

    • TC 766/767 with CRN 262

    • ELF return and the blocking series of the TC 290-0 is "05" or "15" .

  7. Do not order TC 290-0 adjustment source documents for the following:

    1. TC 290-0 adjustment source document is for changes to EIC (TC 764/765/768) and there is no change to AGI or TXI.

    2. The TC 290-0 has a corresponding TC 971 AC 071. These are injured spouse claims for which the refund was released.

    3. The TC 290-0, the TC 150 and the TC 846 have the same DLN with blocking series 92X (example: 18221-046-92337-5). These are also injured spouse claims for which the refund was released.

    4. The TC 290-0 has a corresponding TC 971 AC 270. These are cases where the amended return was sent back to the TP.

    5. The TC 290-0 is in the 98 blocking series (adjustment made without the original return) and there is a RC 062 or 065. These are penalty abatement request disallowances and have no impact on our AUR case.

    6. The TC 290-0 has a corresponding TC 971 AC 142. This is a true duplicate return.

  8. The Tax Account screen indicates if the adjustment source document is a Correspondence Imaging Services (CIS) document. If it is determined the adjustment is:

    • A CIS document, view document on Account Management System (AMS).

    • Not a CIS document, follow the instructions in (9) below.

  9. Request an amended return to resolve the case, if necessary.

    1. To request an amended return, enter an "X" in the ORDER RTN field for the applicable DLN on the Tax Account screen. During the screening phase, use IPC 0A.

      Exception:

      The system will not accept an "X" for any DLN where the DLN indicates the return is Virtual or a CIS document.

    2. If the DLN of the amended return is the control DLN on the Tax Account screen, attach the original return behind the amended return and refile together under the control DLN. Otherwise, refile them separately.

  10. Review all adjustment documents to determine if the U/R amount has already been taken into consideration. If so, close the case using PC 21. If a document has been requested, refile it separately when the case is closed.

  11. Consider all previous changes to income, deductions, refundable/non-refundable credits, taxes, and penalties when a CP 2000 is to be issued.

  12. When a TC 300/301 is present on the Tax Account screen with a TC 421 and no -L freeze, a disposal code displays on the Tax Account screen. If pursuing U/R income, determine the disposal code. The disposal code is located under the column titled "DIS CD" in the transaction section of the Tax Account screen.

    1. If the disposal code is 01 - 13, review the attached audit papers to determine if the U/R amount has been addressed. If there is still a U/R amount after review, issue a notice. Consider all changes made by Exam per the TC 300/301.

    2. If the disposal code is 20 - 99, no audit was performed. Continue processing the case.

  13. If a TC 300/301 and a TC 577 with Julian Date 999 is displayed on the Tax Account screen (no -L Freeze present), the U/R income has not been addressed by the Examination Function. Review the papers to determine what changes were made and take those changes into consideration when calculating U/R income adjustments.

  14. When a TC 896 with the literal "OFF to IRA" is present, the TP has paid additional tax on excess contributions on Form 5329, Additional Taxes on Qualified Plans (Including IRAs) and Other Tax-Favored Accounts. This tax is posted to the TP’s Master File Tax (MFT) 29 account and is not included in the TC 150 amount. The system adds this amount to the TC 150 amount to arrive at total tax per return.

    Note:

    TC 892 offsets a TC 896.

  15. If a duplicate/amended return is filed (TC 976/977 or TC 971 AC 010, 012 through 016 or 120), a CP 2000, CP 2501 or PC 20 is to be issued, a TC 290/291 is present, and the duplicate or amended return is not in the case file:

    1. Order the duplicate/amended return by requesting the TC 290/291 DLN unless the conditions in (7) above apply.

    2. Close the case using PC 29 if the duplicate/amended return is not available.

  16. If a duplicate/amended return is posted (TC 976/977 or TC 971 AC 010, 012 through 016 or 120), a CP 2000, CP 2501 or PC 20 is to be issued, a TC 290/291 is NOT present, and the duplicate/amended return is not in the case file:

    1. Transfer the case to the Unit Suspense batch.

      Exception:

      If 45 days or more from the TC 976/977 or the TC 971 pending/posted date have passed, continue processing the case.

    2. Monitor the case for 45 days from the TC 976/977 or the TC 971 date for the pending/posting of the TC 290/291.

      If the TC 290/291 posts, order the adjustment document.

      If the TC 290/291 does not post, continue processing.

      Note:

      Underreporter functions that work their own Accounts Maintenance Research (AMRH) Transcripts should forward these cases to the appropriate unit after the batch has been disassembled.

  17. TC 295 indicates a tentative allowance from Form 1045, Application for Tentative Refund, was input on the TP's account by Adjustments. TC 299 indicates an abatement of the original tax. If there is a TC 295 or 299 unreversed, or only partially reversed by TC 294 or 298, and there is U/R income, issue a notice.

  18. TC 305 indicates a tentative allowance from Form 1045 was input on the TP's account by Exam. TC 309 indicates an abatement of the original tax. If there is a TC 305 or 309 unreversed, or only partially reversed by TC 304 or 308, and there is U/R income, issue a notice.

  19. If TC 599, TC 720 and/or TC 570 are present, see IRM 4.19.3.3.3.2 (13) table, Freeze Codes, for instructions on how to process.

4.19.3.3.3.4  (09-04-2015)
Other Transaction Codes and Math Error Codes

  1. Other TCs shown on the Tax Account screen may require additional action.

  2. TC 160 or 166 indicates a Delinquency/Failure to File Penalty was assessed. TC 161 or 167 means a portion or all of the penalty has been abated. When a U/R issue exists, the system computes or recomputes the Delinquency/Failure to File Penalty when required. See IRM 4.19.3.16.1, Failure to File (FTF) Penalty, for additional information.

  3. TC 170 or 176 indicates an Estimated Tax (ES) Penalty was assessed. TC 171 or 177 means a portion or all of the penalty has been abated. When a U/R issue exists, a recomputation of the ES penalty may be required. See IRM 4.19.3.16.3, Estimated Tax (ES) Penalty, for additional information.

  4. TC 270 or 276 indicates a Failure to Pay Penalty (FTP) was assessed. TC 271 or 277 means a portion or all of the penalty is abated. See IRM 4.19.3.16.2, Failure to Pay Penalty (FTP) , for additional information.

  5. TC 460 indicates a request for extension of time to file was approved. The extension date appears in the Remarks column.

  6. TC 480 (not reversed by TC 481 or 482) indicates the TP has filed an "Offer in Compromise" (OIC) with the Service. Continue normal AUR processing. A TC 29X may be input on these types of cases. Send copies of the case data to Collection OIC function upon their request.

  7. TC 540 indicates that the TP is deceased. See IRM 4.19.3.4.5, Deceased Taxpayers, for further instructions.

  8. TC 604 indicates either bankruptcy has been discharged/revoked or close-out of the MFT 30 module in preparation of mirroring to MFT 31.

    1. During screening, close the case using PC 27.

    2. During responses (AFTER the TP has been issued an AUR notice), refer to either the local Innocent Spouse (when TC 971 AC 065 is present) or Bankruptcy Coordinator (all others).

  9. TC 764 or 768 indicates earned income credit (EIC) was allowed. TC 765 indicates the credit was fully or partially reversed. If TC 764, 765, or 768 is present, EIC may need to be computed or recomputed. See IRM 4.19.3.15.3, Earned Income Credit, for instructions.

  10. TC 766 with:

    1. CRN 336 indicates Additional Child Tax Credit was allowed. TC 767 (with CRN 336) indicates the credit was fully or partially reversed. If TC 766/767 (with CRN 336) is present, Additional Child Tax Credit may need to be computed or recomputed. See IRM 4.19.3.15.4, Additional Child Tax Credit (ACTC), for instructions.

    2. CRN 252 indicates excess SSTAX has been adjusted (TY 2006 and subsequent tax years only). TC 767 (with CRN 252 indicates the credit was fully or partially reversed. If TC 766/767 (with CRN 252) is present, excess SSTAX may need to be computed or recomputed.

    3. CRN 260 indicates previously allowed American Opportunity Credit (AOC).

    4. CRN 261 indicates previously allowed Refundable Adoption Credit.

    5. CRN 262 indicates previously allowed Premium Tax Credit (PTC).

  11. If a TC 780 has been fully reversed by a TC 781 or 782, continue normal AUR processing.

  12. If an unreversed TC 780 is present on the Tax Account screen, a warning message displays to close the case. Take the following action:

    1. Close case using the appropriate PC (28, 52, 71, or 96).

    2. Leave a case note stating that this is an OIC closure.

    3. Issue a Letter 1802C, if closing the case with PC 52, 71 or 96.

  13. TC 806/800 credits the tax module for the amount of W/H claimed on a tax return. TC 807/802 reverses the TC 806/800 credit in whole or in part. W/H may need to be adjusted because of AUR processing. Before proposing a change to W/H, be certain that the adjustment has not been previously allowed. See IRM 4.19.3.15.1, Withholding - General, for instructions.

    Note:

    Certain modules where an overstatement of estimated tax payments or W/H credits resulted in a refund, offset, or a credit elect will show as assessed using TC 290, RC 051, for the amount of the overstatement. These accounts will generally not contain a TC 807.

  14. TC 971AC 151 indicates duplicate filing by secondary TP. If the message window displays "DUP TIN filing, take appropriate action." , close the case using PC 10.

  15. TC 971 with certain Action Codes (AC), indicate the TP may be a victim of identity theft. During response phase, see IRM 4.19.3.20.1.25, Identity Theft (IDT) Claims - Overview , IRM 4.19.3.20.1.25.3, IDT Claims - Initial Handling, and IRM 4.19.3.20.1.25.3.1, IDT Claims - Responses, for additional information. During screening phase:

    If there is a TC 971 AC Then
    501 Close case PC 23
    504 Close case PC 23
    505 Close case PC 23
    506 Close case PC 23
    522 Close case PC 23
    523

    Note:

    Per IRM 10.5.3.2.12, Misuse of Dependent SSN - TC 971 AC 523, TP is a potential identity thief and has been using a questionable dependent TIN.

    1. Continue normal AUR processing.

    2. Leave a case note acknowledging the TC 971 AC 523.

    3. DO NOT TRANSFER TO IDTVA.

    524

    Note:

    Per IRM 10.5.3.2.13, Locking Decedent Accounts - TC 971 AC 524, TC 971 AC 524 is used to lock the account of deceased TPs. The posted tax return for the AUR tax year 2013 is presumed to be legitimate until a response is received.

    1. If filing status (FS) 2, research IDRS CC INOLES to determine which TP is deceased.

    2. Continue AUR processing following IRM 4.19.3.4.5, Deceased Taxpayers, and IRM 4.19.3.20.1.14, Decedents.

    3. Leave a case note acknowledging the TC 971 AC 524.

    4. DO NOT TRANSFER TO IDTVA.

    525 Close case PC 23

    Note:

    For a list of AC meanings see, Exhibit 4.19.3-16, Identity Theft Action Codes.

  16. TC 972 with corresponding AC indicates identity theft has been reversed. DO NOT TRANSFER TO IDTVA, continue normal AUR processing.

  17. If a TC other than those explained in IRM 4.19.3.3.3.3, Transaction Codes Reflecting Tax Liability, or IRM 4.19.3.3.3.4, Other Transaction Codes and Math Error Codes, are indicated on the Tax Account screen, refer to Document 6209, IRS Processing Codes and Information.

  18. If there is a math error code on a case, the math error code number displays in the MATH ERROR CODE field of the Tax Account screen. If there are multiple math error codes, they display up to a maximum of five (5) codes in this field.

    Note:

    The math error code verbiage displayed on the Tax Account screen is abbreviated and paraphrased from the actual verbiage in Document 6209, IRS Processing Codes and Information.

4.19.3.3.3.5  (06-01-2015)
Correspondence Imaging Services (CIS) Documents

  1. CIS is used to manage scanned images of amended Individual Master File (IMF) returns, documents and electronic case files.

  2. When there is a duplicate/amended return on Tax Account (TC 976/977 or TC 971 AC 010, 012 through 016 or 120 and a posted TC 290/291) an indicator "1" is displayed in the Tax Account screen in the CIS column when a CIS document is available.

  3. If a CIS document is indicated, take the following actions:

    1. Access IDRS.

    2. Access AMS.

    3. From the AMS screen, click on "Cases by TIN" in the Case Management section

    4. In the Taxpayer Lookup screen, enter the TP SSN in the "Request by TIN" field and then click on <Go> or press <Enter> on the keyboard. The TP account summary screen appears.

    5. In the Alert section, click on the "View Images" link.

    6. Select the tax year to review from the CIS image list and click on "Open Image" .

      Note:

      The thumbnail view can be used to view each page

      .

    7. Compare the amended return to the U/R issues to determine if any or all issues are addressed. Continue normal processing.

    8. After processing changes, input the IRS received date located on the amended return.

  4. To exit AMS:

    1. Click on the "Exit Account" link in the upper right hand corner.

    2. In the Taxpayer Lookup window, click on the "Logoff" link to exit the system.

4.19.3.3.4  (09-01-2003)
Information Return Window

  1. The Information Return window displays the complete IR. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Information Return window.

  2. Payer address information, as shown on the Information Return window, displays on the CP 2000/CP 2501.

4.19.3.3.5  (09-01-2003)
Income Comparison Screen

  1. The Income Comparison screen displays a comparison of amounts reported by payers on IRs and the amount the TP reported on his/her tax return. Access this window when it is necessary to view RETURN and IRP amounts or to determine the discrepant income type. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Income Comparison Screen.

  2. The OFFSET field displays codes describing how matched return and IRP amounts were offset for identification of potential discrepancies.

  3. When attempting to offset income, make sure the income to which it is being offset has not already been used. However, if you can determine that offsets were applied incorrectly, analyze that issue as well.

4.19.3.4  (08-26-2016)
Analysis Procedures

  1. The following instructions are for use by AUR tax examiners. They are to be used in conjunction with training materials and the IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures.

    1. An UNDERREPORTED (U/R) condition exists when there is income shown on the IR(s) that was not reported by the TP on Form 1040, Form 1040A, or Form 1040EZ. Proposed tax adjustments are based on these U/R amounts, as well as on reported income amounts for which the TP failed to include the required additional taxes (e.g., SE tax ).

    2. An OVER-DEDUCTED (O/D) condition exists when the TP claims more of a deduction than is substantiated by IR(s) and/or allowed by law (e.g., Mortgage Interest Deduction or Individual Retirement Account (IRA) Deduction).

    3. An UNDERCLAIMED (U/C) condition exists when the TP fails to claim all the payments to which he/she is entitled (e.g., W/H).

    4. An OVERCLAIMED (O/C) condition exists when the TP reduces his/her tax liability by an amount that either exceeds the amount shown on the IR(s), and/or the amount cannot otherwise be substantiated (e.g., Education Credits).

  2. If Exam issues are discovered during AUR processing, consult with the team leader. Then, if necessary, consult with an Exam representative to decide the appropriate action(s) to take.

  3. Computer identified income/deduction discrepancies of ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ are displayed in the LIST OF DISCREPANCIES field on the Tax Account screen. If the category is a combination type, all appropriate discrepancies are displayed.

  4. The IR(s) contributing to the discrepancies are listed first on the Case Analysis screen, and the specific income type is identified with an asterisk. The AUR system alerts the user that a discrepancy exists where is no IR(s) to mark.

    Exception:

    O/D and O/C deduction(s) in question will not have a system generated IR. See (6) below.

  5. Cases involving U/R and EIC are identified in Subfile E. An EIC discrepancy can occur when there is unreported: interest, dividends, capital gain net income (including securities), rents, royalties or income from certain passive activities and the TP claims investment income less than the amounts shown in the table below. If the TP’s total investment income exceeds the amount listed in the table below (regardless of overall AGI), the EIC is disallowed.

    TY 2013 TY 2014 TY 2015
    $3,300 $3,350 $3,400
    1. Due to the investment income limitation for EIC, cases have been created with small amounts of apparent U/R investment income. These investment income discrepancies are not asterisked, (in either Case Analysis or the Income Comparison screens) to alert the tax examiner of where the discrepancy lies. The system does not display a warning message.

    2. When accessing cases in Subfile E, screen ALL IRs.

    3. If there is any U/R (regardless of amount), complete the Return Value screen.

  6. If the Case Analysis screen does not contain any asterisked items, go to the Income Comparison screen to determine the discrepancy and screen the case accordingly.

  7. Discrepant income types are identified with an asterisk on the Income Comparison screen and Information Return window.

    Note:

    Because of computerized offsets, some APPARENT W/H discrepancies are not asterisked. Follow procedures in IRM 4.19.3.15.1, Withholding - General, for these cases.

  8. The Case Analysis screen may contain IRs that HAVE NOT been identified as discrepant. These IRs were added after the case creation and must be analyzed. These IRs are listed along with the discrepant IRs and are identified with an indicator in the AMENDED INDICATOR field. IRs containing the same income types, MUST BE screened and an applicable IR Code assigned to each element of the IR. The indicators are shown as follows:

    • N - New

    • AN - Amended New

    • RN - Replace New

    • DN - Duplicate New

    • XN - Delete New

  9. Initially analyze the asterisked elements on the IR(s) related to the computer identified discrepancies. Also analyze other issues related to the income on the discrepant IR.

    Example:

    Consider adjustments to: Child Care Credit when the DCB element is asterisked; consider SE tax when NEC, MERCH, MED, FISH, etc. elements are asterisked (or when the system identifies a potential SE tax issue); consider the 10 percent tax when Form 1099-R, Distributions From Pensions, Annuities, Retirement or Profit-Sharing Plans, IRAs, Insurance Contracts, etc., element is asterisked and the IR contains a COD, "J" , "L" , "1" , "5" or "7" (with a PGR Indicator of 1), etc.

    Note:

    The AUR system identifies potential SE tax discrepancies on reported income from Form 1040, lines 12, 18 or 21 where no SE tax was paid. The system alerts the user that a discrepancy exists when there are no IRs to mark. An asterisk displays in the SELF EMPLOYMENT TAX field on the Income Comparison window. Follow IRM procedures for specific income types and see IRM 4.19.3.14.1, Self-Employment Tax, and Exhibit 4.19.3-22, Examples of Self Employment Income, to determine when SE tax needs to be considered.

    1. If the asterisked IR is discrepant and it contains W/H, always screen W/H element(s).

    2. If there are no asterisked elements for cases in Subfile E, see (4) above.

    3. If the asterisked element(s) is/are fully reported on the line(s) designated for that income on the tax return (i.e., discrepant wages are fully reported on Form 1040, line 7), then check the INCOME COMPARISON screen for a possible misplaced data entry. Screen the income type related to the misplaced data entry.

    4. If the asterisked element is identified as being included in another type of income, analyze all related IRs. (i.e., Pensions are identified as discrepant but are found reported on the wage line - analyze both pensions and wages.)

    5. If the asterisked element results in above tolerance U/R, screen the remaining non-asterisked items.

  10. If the discrepant IR(s) element(s) is/are reported and/or the system identified SE tax discrepancy is resolved, close the case using PC 21.

  11. When there is U/R income or if related tax/credit adjustment issues are involved, proceed to Return Value.

    Note:

    It is not necessary to mark non-asterisked IR(s) to access the Return Value screen.

    1. AUR multiplies the CHANGE TO AGI field amount by the highest tax rate for the tax year. If this calculation does not result in either ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      Note:

      If any of the following is an issue - Schedule A Mortgage Interest, MIP, SE tax, Federal Insurance Contributions Act (FICA), W/H, excess SSTAX, Dependant Care Benefit (DCB), Child Care Credit, Employer Provided Adoption Benefits (EPAB), Education Credits, EIC, and/or Premature Distribution Tax on retirement income, complete the Return Value screen before closing the case. Ignore the Case Analysis screen system prompt to close the case.

    2. Complete all applicable windows.

    3. If the dollar tolerance for issuing a notice is not met, the system displays a message to close the case. Use PC 22 to close below tolerance cases.

  12. Proposed adjustments on the CP 2000/CP 2501 require an explanation to the TP. There is a single set of explanation paragraphs for both the CP 2000/CP 2501. Paragraphs are either manually selected or automatically generated based on the case condition. All applicable paragraphs display in the SELECTED PARAGRAPH field(s) on the Notice Summary screen. All automatic PARAGRAPHs are automatic toggle. If a CP 2501 Notice is selected (PC 30), the system prevents any non-CP 2501 paragraphs from printing on the notice. If issuing a CP 2501do not"toggle off" apparent inappropriate CP 2501 paragraphs. Non-automatic PARAGRAPHs may be viewed, selected, deleted, and/or added.

    • There is a single Notice Summary screen. This is to facilitate automatically generating a CP 2000 from a CP 2501 no-response.

    • The programming that automatically selects paragraphs occurs in different screens (Case Analysis, Return Value or Notice Summary) depending on the conditions needed to set the paragraph. To reduce the instances of paragraphs resetting, the tax examiner should only"toggle off" or "toggle on" paragraphs from the Select Notice Paragraph window accessed in the Notice Summary screen.

    • CP 2000/CP 2501 automatic and non-automatic paragraphs are notated in this IRM as "PARAGRAPH XX" .

    • Miscellaneous Letter paragraphs are notated as "Special Paragraph" . The verbiage provided in the Special Paragraphs is for example only and can be modified as needed.

    • There are 40 numbered paragraphs for local use by AUR. In situations where the numbered paragraphs are not applicable, a Special Paragraph may be written in the Special Paragraph window.

    Note:

    Special Paragraphs MUST BE reviewed by a manager or lead tax examiner. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Selecting, Viewing and Deleting Notice Paragraphs.

  13. Twelve different income types can be marked as underreported. If there are more than twelve U/R income types, an error message displays. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  14. When issuing a notice for underreported issues, send the applicable element(s) of the IR. The entire IR will not be sent unless all elements (income types) on an IR are marked with a "S" . This includes modified and created IRs. When an IR is marked with a "U" , the system automatically enters the Send Indicator. If it is determined that the IR should not be sent, remove the Send Indicator.

    Note:

    The Send Indicator must be manually entered on any created or modified IR that the tax examiner wants to include on the Notice. In order for a created IR to be considered valid for inclusion on the notice, it must contain: a payer name, payer EIN, and an income amount greater than zero (in addition to other required entries).

  15. Close short year returns with PC 28.

4.19.3.4.1  (08-26-2016)
Information Returns - Review

  1. The initial review of IRs is accomplished from the Case Analysis screen. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures- Case Analysis Overview.

    • All IR(s) with the same document type are sorted in payer Employer Identification Number (EIN) sequence.

    • Be aware of Payer Agent information.

  2. Delete EIN IRs as invalid if any of the following apply:

    1. The payer EIN or name on Form W-2 or Form 1099 matches the payee EIN or name on the IR in question.

    2. Schedule E contains a Partnership or Small Business Corporation with the same EIN or name as the payee EIN or name on the IR(s) in question, UNLESS the payer on the IR is the partnership or small business corporation shown on Schedule E.

  3. Delete the EIN IR when the payee name line(s) is obviously not the TP. For example, the name line(s) contains any of the following groups:

    • Government agencies - federal, state, or local

    • School - private, public, colleges, universities, etc.

    • Charitable and tax-exempt organizations - hospitals, churches, medical centers, etc.

    • Pension Profit Sharing Plan name line(s) with the words "trustee for" , "trustee" , etc.

  4. Consider the EIN IR valid (as belonging to the TP) when ANY of the following conditions are present:

    1. Primary or secondary TP's name is the only payee name on the IR.

    2. Primary or secondary TP's name appear in the first or the second name lines on the IR.

    3. The payee address on the EIN IR is the same address as shown on the tax return, Form W-2 or Form 1099 attached to the tax return, or other SSN IRs.

    4. The payee name on the IR implies a sole proprietorship type business, or the TP's occupation as shown on Form 1040, Form 1040A, Form 1040EZ, or Schedule C or F is typically operated as a sole proprietorship or small business.

    5. The payee EIN on the IR matches the EIN on the Schedule C or F.

    Exception:

    If it appears the EIN listed on the Schedule C or F does not belong to the TP (i.e., the listed EIN matches a payer EIN on another IR), use IDRS CC INOLES to determine the validity of the EIN.

  5. Compare all valid EIN IRs to amounts on the tax return and related schedules. Use instructions for the particular type of income involved.

  6. Assert SE tax, as appropriate, only on the issues that are normally subject to SE tax. See IRM 4.19.3.14.1, Self-Employment Tax, for further instructions and Exhibit 4.19.3-22, Examples of Self Employment Income.

  7. EIN IRs do not display with an Income Identify Code in the INC CD field. If SE tax applies, enter the appropriate Income Identify Code. If it cannot be determined which Income Identify Code to enter, see Exhibit 4.19.3-9, Income Identify Codes, and enter the value from the "Displayed Codes" column. If the IR has a status code of "U" , it is necessary to remove the "U" before an Income Identify Code can be entered.

  8. Delete IRs when:

    1. Payer Agent Indicator "Y" is present and the Payer Agent window contains instructions to delete the IR. See IRM 4.19.3.5, Payer Agent.

      Note:

      If all U/R income is from identified Payer/Agents and the Payer Agent window contains instructions to accept or delete the IR, close the case with PC 24.

    2. The payee entity contains the words "Estate of" .

    3. The TP's name is preceded by the word "by" .

    4. The payee(s) name is obviously different from the Tax Account names and does not contain obvious business words, even though the SSN matches.

    5. EIN 99-9999999, foreign income, is present and another EIN is present for the same payer. IR dollar amounts may vary due to currency exchange rates.

      Note:

      Delete the 99-9999999 IR ONLY when both are present. Foreign Source IRs are treated the same as domestic source IRs.

    6. The literal is "DELET" .

    7. The filing status is "3" or "6" and the SSN on the IR is for the spouse.

    8. The IR contains non-select term(s) and you determine that the payee is NOT the TP. See Exhibit 4.19.3-10, Non-Select Table.

    9. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  9. Consider IRs with the following conditions valid and pursue any U/R amounts:

    1. The payer's name is garbled, missing, or incomplete. See IRM 4.19.3.4.2 (11) c, Comparison of IRP Information Returns With Return Information.

    2. The payee's first and last name are in a different order on the IR.

    3. The payee name is a foreign version of an English name (i.e., Peter listed as Pedro or Pierre).

    4. The payee name line includes the TP's title (MD, DDS, CPA, etc.).

    5. Only a name control is showing as the payee name and it matches the TP's name.

    6. The payee second name line includes "c/o" (or a variation) followed by the TP's name.

    7. The payee name line contains obvious business words and you determine that the payee is the TP.

    8. The literal is "AMEND" and the document does not match the original documents. See (11) below for further instructions.

    9. The payee name is followed by "and" or "or" without other names.

    10. The IR payee name is a maiden name. If the payee's first name or initial on the IR are the same as the Tax Account name, pursue the IR.

    11. The word "rollover" is present on either the payee or payer side. See IRM 4.19.3.7.10.4 (1), Rollovers, for further information.

  10. The payee entity name line of the IR may contain terms or variations of terms. See Exhibit 4.19.3-10, Non-Select Table.

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ for that document type unless you determine that the payee is the TP.

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ present of the same document type NOT containing a non-select term.

  11. Amended IRs are identified on the Case Analysis screen by Indicator "A" , "R" , "D" or "X" in the AMD IND field. Amended IRs are identified on the Information Return window by the literal "AMEND" , "REPLC" , "DUPLE" , or "DELET" . If the computer has pre-identified amended IRs that are used to replace the original IR, the amended IRs have the literal "REPLC" and the literal on the original is "DELET" . PARAGRAPH 47 automatically generates when Amended IRs are included on the notice. See IRM 4.19.3-7, CP PARAGRAPHS. Delete original IRs if amended IRs match an original. The amended and original IR must have:

    • The same payer name and/or EIN.

    • The same account number (if present).

    • The same type of income if the money amount changes or different income types when the money amount stays the same (i.e., amending a Form 1099-MISC, Miscellaneous Income, from NEC to OTINC).

    Pursue all IRs if the amended IR(s) does not match an original, or if the amended IR matches more than one of the other IRs.

    1. Amended IRs may reflect incomplete information; neither amount literals nor $0 (zero dollar amounts) are displayed. If such an IR is present, assume the payer/employer attempted to zero out an incorrect income amount previously reported.

    2. A blank in the amount field of an amended IR represents $0 (zero). Amended IRs with $0 amounts appear on the Case Analysis screen only if there is another IR with at least one money amount or the IR is for a Form W-2.

  12. If all elements (SSN/EIN, name, amount, account number, income type, etc.) on any two IRs are identical:

    1. Including the source, delete one of the IRs.

    2. Except the source, delete the paper source IR.

  13. If all elements on any two IRs are identical except that one does not contain an account number, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  14. If all elements (except the account numbers) of any two IRs are the same and it can be determined that the account numbers of both IRs contain the same sequence of numbers or characters, delete one of the IRs.

    Example:

    Account number 0003013826 and account number 3013826 are account numbers which contain the same sequence of numbers.

  15. Do not consider IRs as duplicates when the account numbers are obviously different, even though all other elements are identical.

  16. Do not consider duplicate any two Form 1099-B, Proceeds From Broker and Barter Exchange Transactions, or Form 1099-S, Proceeds From Real Estate Transactions, IRs unless the sales date is the same.

  17. If a 99MIS and Schedule K-1 (PTK-1, SBK-1 or TRK-1) IR are present for the same TP, from the same payer AND for an identical money amount, see IRM 4.19.3.7.12.1 (10), Conduit Income - Analysis, for further information.

4.19.3.4.2  (08-26-2016)
Comparison of IRP Information Returns With Return Information

  1. Different income types may be combined on one information document, (e.g., Form W-2 may include ordinary wages, allocated tips, W/H, etc.). On the Case Analysis screen, each income type is displayed separately and can be assigned a status code.

    Note:

    If an IR with multiple income elements is U/R, input status code "U" ONLY for the income element that is actually U/R. If necessary, enter status code "R" or "N" for any remaining income elements that are not U/R.

  2. An Income Identify Code in the INC CD field of the Case Analysis screen and the Information Return window identifies certain income types to the system so that U/R income is included in related calculations (i.e., earned income qualifying for earned income credit (EIC), income subject to SE tax, etc.). See Exhibit 4.19.3-9, Income Identify Codes. The tax examiner may change or delete this code if information on the TP's return indicates that the displayed code for U/R income types is inaccurate.

  3. The following general rules apply to the analysis of all types of IRs:

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. Consider an IR reported if the TP reports the same amount of income but under a different payer name.

    3. Allow a tolerance of $1 (rounding) for each IR. In those processes which do automatic calculations and grouping (e.g., SS/RR, IRA Deduction, etc.), the system considers the (rounding) tolerance.

      Note:

      The system does not consider a rounding tolerance during automatic calculations that apply to W/H excess SSTAX, additional MCTXW, or the 10 percent tax. Follow the TP's intent as to rounding, dropping cents, etc. when working these issues.

    4. Consider Payer Agent criteria when evaluating IRs. See IRM 4.19.3.5, Payer Agent, for further instructions regarding Payer Agent data.

  4. Misplaced entries on the tax return are frequent causes of U/R discrepancies. Taxpayers report income on their returns in a variety of places. It is important to thoroughly review the ENTIRE return before identifying income as being underreported.

    1. If there is unearned income (i.e., UNEMP, TX/A, income excluded per Notice 2014 - 7 (Medicare waiver or difficulty of care payments/IHSS), etc.) reported as wages, complete the Return Value screen adjusting the TOTAL EARNED INCOME field of the EIC window if necessary.

    2. Be sure that income identified on an attachment is carried forward and included in the adjusted gross income.

  5. When comparing IRs with entries on any line not specifically identified for that income type, the amount must match within $1 or be clearly identified as the income type in question.

    1. If the amount matches within $1, consider the IR reported.

    2. If the amount does not match within $1, but the income type has been clearly identified, consider the IR(s) reported if the entry is a larger amount, or consider the IR partially U/R if the entry is a lesser amount.

  6. When payer documents are attached (Form W-2, Form 1099-MISC, etc.) to a paper return, consider them more accurate than the IR UNLESS:

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ continue processing and consider the IR the most accurate.

    3. There is an amended IR that corresponds with the payer document. Consider the amended IR the most accurate.

    4. They appear to be for an incorrect tax year.

  7. Taxpayers recreate payer information (such as Form W-2, Form 1099-R, etc.) to include with their ELF return. Due to the increase for potential input errors of the payer information, such as transposed money amounts or missing information (ex: pension plan box on Form W-2, COD on Form 1099-R, etc.), always consider the information on the corresponding IR more accurate than the ELF payer document.

    1. When the ELF payer document indicates more income than the IR, assume the TP is reporting correctly per an amended document. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. When the TP includes ELF payer document(s) for which there is no corresponding IR, consider the income amounts reported when determining overall U/R income and AGI changes. If necessary, create an IR for the additional amount(s).

      Exception:

      Do not give credit for W/H or additional Medicare tax withheld (MCTXW) claimed on an ELF payer document for which there is no IR.

  8. For ELF returns, consider the IR more accurate than the ELF payer document when the ELF payer document shows less income than the IR. All elements of the IR are considered more accurate than the ELF payer document elements.

  9. If the return is missing supporting forms or schedules, research IDRS. If the information is not available, take the following action(s):

    1. Allow credit against IRs for wages, W/H, interest, and dividends reported on the return unless there is an indication the return amounts are not from the same payer(s) on the IR(s).

    2. For all other types of income, do not allow credit against IRs unless the return amount matches an IR within $1.

    3. Do not make any changes in the calculation windows (e.g., Child Care Credit, Schedule A, Alternative Minimum Tax), but allow the system to compute if the necessary supporting schedule or form is missing.

  10. The Create Information Return window is used to create a new IR. See IRM 4.19.7, IMF Automated Underreporter (AUR)Technical System Procedures - Creating Information Returns.

  11. Create an IR if:

    1. The TP reports income/deductions for which there is no corresponding IR, and the reported amount is needed by the system to perform related calculations. (The corresponding information document may or may not be attached to the return.)

    2. There is an attached information document with no corresponding IR, and the income is not reported. Send PARAGRAPH 139, see IRM 4.19.3-7, CP PARAGRAPHS.

    3. The payer's name is garbled, missing or incomplete. Use the EIN to research IDRS CC INOLES for the proper payer name. If the income is U/R, recreate the IR as shown on the Case Analysis screen, including the correct payer name. Include the created IR on the notice.

      Caution:

      In order for a created IR to be considered valid for inclusion on the notice, it must contain: a payer name, payer EIN, and an income amount greater than zero (in addition to other required entries). The Send Indicator must be manually entered on the IR by clicking in the SEND INDICATOR field on the Case Analysis screen.

    4. The tax examiner determines other conditions exist that require creation of an IR.

  12. The Modify Information Return window modifies an existing IR. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Modifying Information Returns.

  13. Modify an IR if:

    1. The COD/PGR Indicator is incorrect.

    2. The Payee Indicator is incorrect.

    3. One or more IR(s) belongs to both TPs and the income/deduction amount needs to be allocated (e.g., the TPs divided nonemployee compensation from one IR between two Schedules C, and SE tax is an issue).

    4. One or more IR(s) is reported on more than one schedule or form (e.g., mortgage interest on Schedule A and Schedule E), and the income must be allocated in order to reflect the correct Income Identify Code.

    5. It is determined other conditions require modification of an IR.

      Reminder:

      After an IR is modified the system marks the original amount with an "X" . To include the modified IR on the notice, click the SEND INDICATOR field next to the original amount.

  14. Use the SEARCH option to view only those IRs that fit specific criteria (e.g., payer name, income type, etc.). See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Search Function.

  15. Use the SCROLL IR option to view multiple IRs on the Information Return window, without returning to the Case Analysis screen. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - CA Tools Menu.

  16. Use the GROUP option when the TP has not provided a breakdown and it is necessary to compare a total money amount for related IRs with a single line entry on the TP's return. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Grouping Information Returns.

    Note:

    The Group function is a tool to assist the TEs in computing the correct U/R amount. It may not be necessary to use the Group function if the correct U/R can be determined without it.

    1. If the group total amount is larger than the single line entry on the return, assign status code "U" to the group.

    2. If the group total amount is smaller than the single line entry on the return, assign status code "R" to the group.

    Note:

    All IRs of the same income type are grouped together, regardless of the Income Identify Codes. After grouping, it may be necessary to remove an IR(s) from the group because of the Income Identify Code.

  17. If a 99MIS IR has two identical money amounts (e.g., NEC is $500 and MED is $500) and the TP reports one of the amounts, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  18. A photocopy of a prior year CP 2000 response may be attached to the return. Consider the information in the previous year's response. This information may result in resolving the U/R issue(s).

  19. When a U/R issue for the same type of income from the same payer was resolved per a copy of a Letter 2625C response from a prior year attached to the return, delete any current year IR.

    Note:

    If a prior year AUR closure letter (CP 2005, Letter 1802C, etc.) is attached to the return, research the prior year to see if the resolved issue(s) corresponds to the current AUR year discrepancy. If so, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  20. If all IRs are matched exactly, but there is still a U/R amount:

    1. Add the amounts reported on the return. (There has probably been a math error.)

    2. Pursue the U/R issue.

    3. Send an appropriate paragraph to advise the TP of the error.

  21. If the discrepancy is resolved, close the case using PC 2X.

  22. Foreign source income IRs are identified by:

    • A payer TIN of "99-9999999"

    • An unusual payer name (Bundesent fer Finazen, Banque de Quebec) or a payer name indicating a foreign country (French Dividends, German Securities, United Kingdom Royalties)

    • Foreign country abbreviation in the State field

    • Account Code Type "T"

      Note:

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

4.19.3.4.2.1  (09-01-2012)
Service Center Recognition/Image Processing System (SCRIPS)

  1. The following procedures apply to the analysis of Service Center Recognition/Image Processing System (SCRIPS) IRs.

  2. The system displays a warning message when STATUS CODE "U" is assigned to a SCRIPS IR(s). When this message is received, the tax examiner should screen the related IR with EXTREME care.

  3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      Example:

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

    3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      Example:

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

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  4. If a SCRIPS IR is asterisked and is deleted due to one of the conditions in (3) above and the other asterisked item(s) are reported or below tolerance, close the case. If the other asterisked item(s) are U/R, continue processing.

  5. If a SCRIPS IR is U/R and none of the conditions in (3) above are present, consider the IR correct and pursue the issue using normal procedures.

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. Do not send SCRIPS IRs with erroneous information to the TP. Create an IR to reflect the correct information and include it on the notice.

  6. Do not send information regarding erroneous SCRIPS IRs to the AUR Payer Agent Coordinator, unless some other payer agent (P/A) condition exists.

4.19.3.4.3  (09-30-2014)
Jointly Owned Income

  1. Joint ownership is indicated when there are two or more names on the IR, or one payee name is on the IR followed by "and" or "or" . This situation occurs primarily when working with interest, dividend and/or securities income.

  2. When the TP reports the appropriate percentage of ownership from a jointly owned IR, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    Exception:

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

  3. If the TP resides in a Community Property state, see IRM 4.19.3.4.4, Community Property States, for further instructions.

  4. If the filing status is 3 (Married Filing Separately), the spouse's name appears on the IR, the TP does not report ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ of the income in question or does not include a statement that ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ , research IDRS using CC INOLE, RTVUE, ENMOD, etc. for the spouse's return.

    Note:

    If the IR is solely for the spouse, delete the IR.

    1. If the spouse did not file a return, issue a CP 2000.

    2. If the spouse filed a return, it may be possible to determine if the spouse reported the jointly owned income. If the difference between the spouse’s IRPTR data and his/her reported per return amount (from CC RTVUE, or IMFOLR) for the related income type equals the U/R amount (within tolerance) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ . If not, issue a notice for the full U/R amount to the AUR TP.

  5. If the filing status is 6 (TP claiming an exemption for spouse not filing), issue a notice as appropriate to the primary TP for the U/R issue.

    Reminder:

    If the filing status is 6 and the IR is for the spouse, delete the IR.

4.19.3.4.4  (08-26-2016)
Community Property States

  1. Taxpayers who reside in a community property state and who are subject to the state’s community property laws must follow the state community property laws to report their community/separate income on a federal tax return.

  2. AUR may receive requests for filing status changes based on the June 26, 2013 Supreme Court ruling on a provision of the 1996 Defense of Marriage Act (DOMA). The effect of the Supreme Court’s opinion is that same-sex couples who are lawfully married under state law are treated as married for all federal tax purposes including income and gift and estate taxes. The ruling applies to all federal tax provisions where marriage is a factor, including filing status, claiming personal and dependency exemptions, taking the standard deduction, employee benefits, contributing to an IRA and claiming earned income tax credit (EITC) and child tax credit (CTC). If the TP submits a Form 1040X requesting a filing status change see IRM 4.19.3.20.7.4 (3), Referrals.

  3. The Community Property states are:

    • Arizona

    • California

      Note:

      A Chief Counsel Advice Memorandum issued in May of 2010 provides that in computing federal income tax California’s community property laws apply to registered domestic partners (RDP) who reside in California in computing the partner’s federal income tax.

    • Idaho

    • Louisiana

    • Nevada

      Note:

      The states community property laws apply to RDP as of October 1, 2009.

    • New Mexico

    • Texas

    • Washington

      Note:

      The states community property laws apply to RDP as of June 12, 2008.

    • Wisconsin

  4. Married TPs can elect to file either a joint return or separate returns (to get a greater tax advantage). If the TPs meet certain conditions, they may be eligible to file a non-joint return using either FS 1 (single) or FS 4 (head of household), as opposed to FS 3 (married filing separate).

  5. RDPs are not married for federal tax purposes. They can use only the single filing status, or if they qualify, the head of household filing status. RDPs treat income as jointly owned. An RDP must report half of all community income and all of his/her separate income on his/her tax return. Taxpayers attach Form 8958, Allocation of Tax Amounts Between Certain Individuals in Community Property States, (or similar statement) to show how the income has been allocated.

  6. Community income is generally income from:

    • Community property (e.g., a jointly owned savings account)

    • Salaries, wages or pay for services that either spouse performed during their marriage

    • Real estate that is treated as community property under the laws of the state where the property is located

  7. Separate income is generally income from separate property. Separate income belongs to the TP who owns the property.

    Note:

    Contribution limits on IRAs are applied without regard to community property interests.

  8. When married TPs choose to file separate tax returns, they should use Form 8958 (or similar statement), to list their income, deductions and W/H. Each TP is instructed to attach the Form 8958 (or similar statement) or a photocopy of the other spouse's payer documents (Form W-2, Form 1099, etc.) to each of their individual tax returns.

  9. On the Form 8958 (or similar statement), community income is generally equally divided between both TPs and each TP would report their separate income.

    1. Earned income (e.g., wages, nonemployee compensation, etc.) is generally considered community income and the TPs would divide their combined income equally between them.

      Note:

      The amount of W/H would also be combined and divided between both TPs.

    2. Jointly held savings accounts are treated as community property. Individual savings accounts that earn either interest or dividends are generally considered separate property.

      Exception:

      The Community Property laws for those TPs who reside in Idaho, Louisiana, Texas or Wisconsin stipulates that income from separate property is generally treated as community income. For example, interest earned on an individual savings account would be considered community income.

  10. On an individually filed tax return, if there is partially reported income/deductions and the TP resides in a community property state as listed in (3) above, determine if the AUR condition is the result of the income allocation.

    1. Consider the information return fully reported if attached statements/worksheets or Form 8958 identifies that the income was allocated between both spouses (including RDPs).

    2. If the discrepant information return is not addressed in the attached statement/worksheet or Form 8958, pursue the full amount of the income.

4.19.3.4.5  (08-26-2016)
Deceased Taxpayers

  1. On married filing joint (FS 2) returns if there is an indication that the primary or secondary TP is deceased, but the Tax Account screen (Entity section) does not reflect this, research IDRS CC INOLES to determine which TP is deceased.

  2. Follow the procedures listed below to screen the case:

    Note:

    When one of the TPs is deceased, see IRM 4.19.3.7.17.1 (4), SS/RR - Analysis, for procedures to resolve SS/RR discrepancies on jointly filed returns.

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      Caution:

      If the decedent's income is reported on the return, consider the IR reported and enter status code "R" . This allows the system to correctly calculate any changes.

      Exception:

      If the surviving spouse's U/R income causes a change in the taxable portion of a decedent's reported SS/RR, Student Loan Interest Deduction, IRA Contributions and/or Tuition and Fees, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Send PARAGRAPH 129, see IRM 4.19.3-7, CP PARAGRAPHS

    4. Issue a notice if the U/R IR(s) show ownership for the surviving spouse.

  3. If issuing a notice, input the current information in the Update Address window. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Updating Address Information.

    1. Update the first name line.

    2. For joint returns, enter DECD after the given name of the deceased TP.

    3. For other than joint returns, enter DECD after the TP's last name, including suffix.

      Note:

      The first name line is limited to 35 characters. If DECD will not fit on this, input the deceased TP's name and DECD on the second name line.

    4. Enter the second name line, if present.

    5. Enter "D" in the Split Code field.

4.19.3.4.6  (10-30-2015)
Declared Disaster Areas

  1. AUR Coordinators input Zip Codes for specific declared disaster area situations as necessary based on IRS Disaster Relief Memos. Follow system prompts to ensure proper handling of declared disaster area cases. Disaster types with case impact:

    Note:

    Use of IPC 0D and batch type 35 to process disaster cases should occur ONLY when directed by AUR HQ and ONLY for impacted sites.

    1. Type 2 - suppresses CP 2000/CP 2501 and Statutory Notices.

    2. Type 3 - prevents cases from defaulting (notices continue to be issued).

    3. Type 4 - suppresses CP 2000/CP 2501 and Statutory Notices AND prevents cases from defaulting.

  2. Cases with the following characteristics may require special and/or manual processing:

    1. Special rules for withdrawals and loans from IRAs and other qualified retirement plans, reported on Form 8930, Qualified Disaster Recovery Assistance Retirement Plan Distributions and Repayments, and taken into consideration on Form 8606, Nondeductible IRAs.

    2. Education Credits on Form 8863, Education Credits (American Opportunity and Lifetime Learning Credits).

      Note:

      Follow procedures in the income/issue specific subsections when there is an indication of the items listed above.

4.19.3.4.7  (02-12-2016)
Frivolous Return Program (FRP)

  1. A frivolous return is defined as noncompliance with filing and/or paying tax based on unfounded legal or constitutional arguments per IRM 25.25.10, Frivolous Return Program. If in doubt about whether the return is frivolous, consult with your lead or manager. If it is determined during screening that the return is frivolous, close the case with PC 13, notate the case for clerical "FRP to Ogden" .

    Note:

    See IRM 4.19.3.4.9 (6), Miscellaneous, if the TP is quoting an IRC.

  2. If the return is determined NOT to be frivolous, continue normal processing.

  3. If FRP requests an AUR case after TP contact, close the case with the appropriate PC (38, 64 or 85), notate the case for clerical "FRP to Ogden" .

4.19.3.4.8  (10-02-2012)
Fraud Referral Program

  1. The primary objective of the fraud program is to foster voluntary compliance through the recommendation of a criminal investigation/prosecution and/or civil penalties against TPs who evade the assessment and/or payment of taxes known to be due and owing.

  2. Tax fraud is often defined as an intentional wrongdoing on the part of a TP, with the specific purpose of evading a tax known or believed to be owing. Tax fraud requires both:

    1. a tax due and owing; and

    2. fraudulent intent

  3. The objective of the Campus Fraud Referral Program is to:

    1. Identify cases with potential fraud.

    2. Develop fraud guidance from the Campus Fraud Referral Specialist (FRS).

    3. Refer potential fraud cases to Field Exam for further development.

  4. Fraud Technical Advisor (FTA) - The FTA assists with the development of fraud in the Campus Examination environment.

  5. Functional Fraud Coordinator (FFC) - The FFC is a fraud liaison assigned to a specific function or operation within the Campus. The FFC is responsible for reviewing the Forms 13549, Campus Fraud Lead Sheet, and conducting research used to establish a pattern of non-compliance. See IRM 4.19.10.4.3, Responsibilities of the Functional Fraud Coordinator (FFC), for additional information.

  6. Campus Fraud Coordinator (CFC) - The CFC is a fraud liaison assigned to each SB/SE Campus. The CFC is the main point of contact with the FTA assigned to that campus.

  7. Exam Fraud Coordinator (EFC) - The EFC is a fraud liaison assigned to each W&I Exam function. The EFC is the main point of contact with the FTA assigned to that campus.

4.19.3.4.8.1  (11-07-2012)
Identifying and Developing Fraud in AUR

  1. During the course of AUR case work, situations may be encountered involving potential fraud, referred to as indicators of fraud. Although only a small percentage of cases are fraudulent, it is essential to detect and report any potential fraudulent activities. IRM 25.1.2.3, Indicators of Fraud, provides several lists of Fraud Indicators. The following list has been developed for AUR and identifies examples of indicators of fraud that are most likely to be found in a campus environment (this list is not all inclusive and may involve a promoter/return preparer):

    • Altered Documents

    • False deductions/adjustments to income

    • False/overstated Form W-2 for EIC purposes (may be preparer/promoter)

    • False Schedule C for EIC purposes

    • Identity theft (sale or purchase)

    • False basis in assets

    • False transaction date for asset disposition

    • False statements made by TP

    • False exemptions

    • Use of decedent’s SSN

    • False business, rental, or farm expenses

    • False or overstated refundable credits

    • Amended returns with any of the above

  2. Fraud is developed by trained Fraud caseworkers until it is determined that affirmative acts (deceit, subterfuge, camouflage, concealment or some attempt to color or obscure events or to make things seem other than they are) exist. The Service must prove that the TP acted deliberately and knowingly with the specific intent to violate the law. Once a suspicion or indicator of fraud is found, it is essential that the case be transferred to the designated AUR Functional Fraud Coordinator (FFC) for further development.

  3. See IRM 25.1.1.3, Indicators of Fraud vs. Affirmative Acts of Fraud.

4.19.3.4.8.2  (08-26-2016)
AUR Tax Examiners Fraud Responsibilities

  1. Identify indications of fraud that are uncovered through regular case processing. Prior to researching for fraud indicators, use the IAT "aMend" tool, research portion, to determine Scrambled SSN or Mixed Entity. If yes, prepare Form 4442 for referral to AM. If no, refer to the following:

    1. Fraud Refund Scheme listing found in the Job Aids section on SERP: http://serp.enterprise.irs.gov/databases/irm-sup.dr/job_aid.dr/RICS-IVO/FraudRefundSchemeListing.htm

    2. IRM 4.19.3.4.8.1, Identifying and Developing Fraud in AUR.

    3. IRP data versus the filed return; i.e. the only UR income is social security benefits that do not indicate a filing requirement. The posted return appears to have fraudulent income reported, such as Schedule C and wage income that cannot be verified on IRPTR. Refer to Exhibit 4.19.3-19, Filing Requirements for Most People, for additional information

  2. Discuss the indicators of fraud with the group manager or lead. If the group manager or lead concurs:

    1. Complete Sections I, II and III of Form 13549, Campus Fraud Lead Sheet (information and indicators of fraud).

    2. Secure the group managers initials and date.

    3. Assign the appropriate IPC 0D, 3F, 6F, or 8F.

    4. Forward the case and the sheet to the AUR Functional Fraud Coordinator (FFC) for consideration.

  3. Documentation is critical in the development of fraud. Maintain complete and accurate case notes that include each of the following:

    1. All case actions.

    2. All documents received.

    3. All contacts must be adequately documented (e.g. changes to entity information were recognized/updated).

    4. All conversations with the TP, representative, return preparer, and third parties must be recorded (what was discussed and the responses).

  4. If Fraud refuses the case, returns it to the tax examiner per IRM 4.19.3.4.8.3 (6), AUR Functional Fraud Coordinator Responsibilities, take the following actions:

    If Then
    The case is in the screening phase Close the case PC 28.
    The TP's response indicates they did not file a tax return (regardless of agreement to the U/R income)
    1. Research and print ENMOD. If there is an indication of identity theft see IRM 4.19.3.20.1.25.3, IDT Claims - Initial Handling.

    2. If not, issue a Letter 2626C, and advise the TP to submit a completed return including the required signatures or a signed statement that they did not have a filing requirement with a copy of our notice. Refer to Exhibit 4.19.3-19, Filing Requirements for Most People, for additional information

    3. Request IDT documentation.

    4. Leave a detailed case note outlining the TP response and actions (i.e. "TP resp didn’t file. 2626C for rtn or signed stmt" ).

4.19.3.4.8.3  (06-01-2015)
AUR Functional Fraud Coordinator Responsibilities

  1. The AUR Functional Fraud Coordinator (FFC) is responsible for developing fraud cases:

    1. Conducting preliminary screening of Form 13549, to determine if the referral should be forwarded to the CFC (all cases in IPC 0D, 3F, 6F, and 8F).

    2. Conducting research used to establish a pattern of non-compliance.

    3. Making a determination to accept (forward the case to the CFC) or decline the referral within 10 (ten) days of receipt.

    4. Leave a case note detailing actions taken (i.e. forwarded to Fraud, doesn't meet fraud criteria, etc).

  2. The AUR FFC is also responsible for monitoring and managing the Fraud Referral Program within the AUR Operation.

    1. Maintaining a copy of each Form 13549 for 3 years.

    2. Tracking all AUR fraud leads, including those declined/returned to AUR and those accepted for further fraud development. AUR will use a combination of the IPC listing and Form 13549 to track fraud referral cases.

    3. Submitting information on fraud referral/accepted/declined cases to Exam Headquarters by the fifth day of each month.

    4. Completing the Campus Fraud Monitoring report located at \\COV0010CPSHR1\Common\SBSE\Campus Compliance Services\Fraud.

  3. If the AUR FFC declines the fraud lead he/she will:

    1. Provide a written explanation for the declination in Section VI, Explanation for Declination, of Form 13549.

    2. Return a copy of the completed Form 13549, to the initiator through the initiator’s team leader/manager.

    3. Reassign the case to the initiator's User Identification Number (UID).

  4. If the AUR FFC accepts the fraud lead, he/she will:

    1. Annotate the acceptance on the Form 13549.

    2. Forward the fraud lead (case or scanned documents and Form 13549) to the CFC for a final fraud determination, following local procedures.

      Caution:

      The normal Assessment Statute Expiration Date (ASED) expires three (3) years from the due date of the return or three years from the received date of the original return; whichever is later. There must be at least 13 months remaining on the ASED, from the date the case is referred to the CFC. If less than 13 months remain and the case has good fraud potential, the FFC can contact the CFC who can consider accepting the case on a case by case basis.

    Note:

    The CFC is required to make a determination to accept or decline a lead within 21 business days of receipt.

  5. If the CFC accepts the fraud lead for further development, he/she will request the case be reassigned and ensure the case is established on AIMS. The AUR FFC will:

    1. Close the case using Fraud Closing PC 14, 44, 72 or 84, as appropriate.

    2. Annotate the Form 13549 and keep a copy for the AUR records.

      Note:

      Copies of Form 13549 must be maintained by AUR for three years.

    3. Make and send a copy of the Form 13549 to the initiator through the initiator's manager.

    4. Ensure the entire case contents are forwarded, following local procedures.

      Note:

      If the case contents are being trans-shipped to the CFC, recharge the return using IDRS CC ESTABDT or Form 2275, Records Request, Charge and Recharge.

  6. If the CFC declines the fraud lead, he/she will return the Form 13549 with a written explanation to AUR. The AUR FFC will:

    1. Return the Form 13549 to the initiator through the initiator’s manager.

    2. Transfer the case to the initiating tax examiner's UID.

4.19.3.4.9  (08-26-2016)
Miscellaneous

  1. Initial processing errors, or additions to the AGI are corrected by entering the appropriate amount(s) in the MISCELLANEOUS ADJUSTMENT fields on the MISC ADJUSTMENT/SCHEDULE C EXPENSE window. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Miscellaneous Adjustment/Schedule C Expense. When any amount is entered in this window send a Special Paragraph explaining the adjustment. The amount computed in the changed amount field is included in the AGI by the system and is considered in all calculations. This amount is included in the U/R Amount on the Return Value screen and displays on the Notice Summary as Miscellaneous Adjustment.

    Caution:

    Do not use this window for situations where a specific income/deduction type has its own window for the required adjustment. Also, the entry for the return field can be a negative or a positive amount, depending on the line entry being changed.

  2. If Form 6781, Gains and Losses from IRC 1256 Contracts and Straddles, is attached to the return, or if Form 1040, line 44, indicates that the tax is from Form 6781, continue normal processing. This is reported on Schedule D.

  3. A net operating loss (NOL) is identified by a negative entry on Form 1040, line 22 caused by negative amounts on lines 12, 14, 17 other than Schedule E Part I, line 18, or the indication of a carryover NOL on line 21.

    Note:

    A NOL is indicated by a negative amount on Form 1040, line 22. A NOL does not exist simply because there are negative entries on lines 12, 14, 17, 18, or 21.

    1. Verify that the correct amount is displayed in the NET OPERATING LOSS AMT field of the Return Value screen.

    2. If a NOL is caused by negative entries on Form 1040, lines 14 or 21, an amount does not display on the Return Value screen. Input the amount of the NOL in the NET OPERATING LOSS AMT field.

    3. The NET OPERATING LOSS AMT field displays an amount that is just a negative figure, not an actual NOL. If a displayed amount is not a NOL, delete the incorrect amount.

  4. If Form 1040 shows a net operating loss, continue normal processing.

  5. If IRC 6501(d), Request for Prompt Assessment, is noted on the tax return, or there is a statement requesting a prompt assessment, AND there is a U/R amount, the case MUST BE WORKED EXPEDITIOUSLY. Prompt Assessment cases have an 18 month statutory period for the assessment of additional tax.

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ use the following guidelines:

    3. Enter "Y" in the IRC 6501(d) field on the Tax Account screen.

    4. Enter the irregular statute of limitation date in the IRREG DATE field on the Tax Account screen.

    5. Control the case and continue processing.

  6. If an attachment indicates the income in question is nontaxable and the TP cites an IRC section, determine the validity of the TP's statement by researching the IRC. If the IRC submitted by the TP(s) is not valid, send a Special Paragraph to inform him/her that the explanation is not acceptable.

  7. Erroneous refunds caused by IRS error require special processing, see IRM 4.19.3.4.11, Erroneous Refunds, for further information.

  8. If a Form 8857, Request for Innocent Spouse Relief, or an attachment indicates a TP is claiming Innocent Spouse, see IRM 4.19.3.3.3.2 (8), Freeze Codes, and IRM 4.19.3.20.1.20.1, Innocent Spouse Relief Cases - Tax Examiner Instructions.

    • Do not confuse Innocent Spouse cases with Injured Spouse cases, which are worked in Accounts Management.

    • If the TP's claim for Innocent Spouse relief does not relate to the tax year of the open AUR case, send only the Innocent Spouse claim to CSC. Do not send the AUR case to CSC.

4.19.3.4.10  (09-01-2010)
AUR Bankruptcy Coordinator Procedures - Contact by Insolvency

  1. When contacted by an Insolvency Specialist on a case in AUR inventory that has not yet been screened:

    1. Inform the Insolvency Specialist that there will not be an AUR issue for the year in question.

    2. Leave a detailed case note documenting the contact with the Insolvency Specialist.

    3. Take the following action to close the case with PC 27:

      If Then
      The case is currently in a batch (AB, AU OR BF status) Have the case assigned to yourself and input closing PC 27.
      The case is not currently in a batch (i.e., in a future run control) On a weekly basis, provide the clerical function with a listing of SSNs and request that they assign PC 27.

      Note:

      Follow the above procedures regardless of whether or not Bankruptcy indicators are present on the AUR system.

    4. Run the AUR Bankruptcy Status listing on a weekly basis and take appropriate steps to address the cases identified on the listing. Provide clerical with the SSNs of any "pre notice" cases identified from the listing to be closed with PC 27. See IRM 4.19.3.20.1.10.2 (9) a, Bankruptcy Procedures - AUR Bankruptcy Coordinator Instructions, for additional information.

  2. When contacted by an Insolvency Specialist on a case that has been screened but the notice has not yet been issued:

    1. Inform the Insolvency Specialist that there will not be an AUR issue for the year in question.

    2. Leave a detailed case note documenting the contact with the Insolvency Specialist.

    3. Stop the notice and input PC 27. See IRM 4.19.3.17.3, Stop Notice Functionality, for additional information on stopping notices.

      Note:

      Follow the above procedures regardless of whether or not Bankruptcy indicators are present on the AUR system and/or regardless of the proposed U/R amounts.

4.19.3.4.11  (08-26-2016)
Erroneous Refunds

  1. An erroneous refund is any receipt of money from the Service to which the recipient is not entitled. It includes all erroneous payments to the TP, even if the erroneous refund involves returning the TP’s own money. An erroneous refund may occur when:

    • The statute of limitations has expired and a refund is issued

    • There are misapplied payments

    • The AUR adjustment erroneously releases a credit hold (i.e., IVO involvement TC 971 AC 134 is present)

    • The AUR payment is posted with TC 670 or TC 610.

  2. When an erroneous refund is identified and the TC 846 has not posted, use the IAT "Stop Refund" tool to stop the refund. The action to stop the refund must be input by 10:00 a.m. on the Wednesday preceding the date of the refund.

    Caution:

    Do not stop a direct deposit refund; which is identified by the number "10" in the DDRC field on IDRS CC IMFOLT.

  3. When an erroneous refund is identified and is the only issue, assign PC 28, 53, 68, or 88. If the Erroneous Refund Statute Expiration Date (ERSED) has expired, close the case with PC 28, 52, 71, or 96. Take appropriate actions to resolve the erroneous refund issue. See IRM 4.19.3.4.11.1, Recovering Erroneous Refunds, for additional information.

4.19.3.4.11.1  (08-26-2016)
Recovering Erroneous Refunds

  1. There are four categories of erroneous refunds that AUR will work; Category A1, A2, B and D. Each category has a specific method that must be used to recover the erroneous refund and different statutes of limitation apply.

  2. The Statute of Limitation used when recovering erroneous refunds are:

    1. ASED (assessment statute expiration date) which is generally three years from the date the return was filed,

    2. CSED (collection statute expiration date) which is generally ten years from the date of assessment, and

    3. ERSED (erroneous refund statute expiration date) which is generally two years from the date of the erroneous refund check or direct deposit. A five year statute applies when the IRS can show the erroneous refund was induced by fraud or a misrepresentation of a material fact. ERSED is used to recover Category D erroneous refunds.

  3. When a case is determined to be an erroneous refund, there are two steps to follow for recovering an erroneous refund:

    1. Identify the appropriate erroneous refund category.

    2. Complete the required actions within the applicable statutes to correct the error that caused the erroneous refund.

    Category IRM Reference
    A1 See IRM 4.19.3.4.11.1.1
    A2 See IRM 4.19.3.4.11.1.2
    B See IRM 4.19.3.4.11.1.3
    D See IRM 4.19.3.4.11.1.4

4.19.3.4.11.1.1  (08-26-2016)
Recovering Erroneous Refunds - Category A1

  1. Category A1 Erroneous Refunds occur when the tax liability has been understated due to an error on either a tax assessment or on an adjustment to the tax liability and the error results in a refund.

    Example:

    The IRS lowered the tax when processing the original return or an incorrect adjustment on an amended return was made.

  2. The Category A1 Erroneous Refund is generally recovered with a deficiency assessment by the Examination function. The notice of deficiency must be issued within the assessment statute period or by the ASED.

    1. Prepare Form 4442, Inquiry Referral, and include any information pertinent to the erroneous refund. Forward the Form 4442 to your local Examination function for the issuance of a deficiency notice.

      Exception:

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

    2. Use the IAT "REQ77" tool to input TC 971 AC 663; regardless of erroneous refund amount.

    3. Leave a case note and assign appropriate PC/IPC.

      Note:

      The Letter 510C is not issued on Category A1 Erroneous Refunds. Do not input a TC 470 or a TC 844 on these accounts.

4.19.3.4.11.1.2  (08-26-2016)
Recovering Erroneous Refunds - Category A2

  1. Category A2 Erroneous Refunds involve errors on non-refundable and/or refundable credits that are subject to deficiency procedures. Examples of refundable credits subject to deficiency procedures include Additional Child Tax Credit and Earned Income Tax Credit.

  2. Category A2 Erroneous Refunds are generally recovered with a deficiency assessment by the Examination function. The notice of deficiency must be made within the assessment statute period or by the ASED.

    1. Prepare Form 4442 and include any information pertinent to the erroneous refund. Forward to your local Examination function for the issuance of a deficiency notice.

      Exception:

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

    2. Use the IAT "REQ77" tool to input TC 971 AC 663; regardless of erroneous refund amount.

    3. Leave a case note and assign appropriate PC/IPC.

      Note:

      The Letter 510C is not issued on Category A2 Erroneous Refunds. Do not input a TC 470 or a TC 844 on these accounts.

4.19.3.4.11.1.3  (08-26-2016)
Recovering Erroneous Refunds - Category B

  1. Category B Erroneous Refunds occur when the TP overstates their W/H, additional MCTXW, excess SST, or estimated income tax payments on a return or a claim for refund.

    Note:

    If the IRS caused the overstatement of W/H, additional MCTXW, excess SST, or estimated tax payments, the erroneous refund becomes a Category D Erroneous Refund and can only be recovered through the Category D Erroneous Refund procedures. See IRM 4.19.3.4.11.1.4, Recovering Erroneous Refunds - Category D, for further information.

  2. Category B assessments are not subject to the deficiency procedures; however, the assessments must be made by the ASED.

  3. The Letter 510C is not issued on Category B Erroneous Refunds.

  4. Do not input a TC 470 or a TC 844 on these accounts.

  5. Do not use Hold Codes on the adjustment that will prevent the notice from being generated.

4.19.3.4.11.1.4  (08-26-2016)
Recovering Erroneous Refunds - Category D

  1. Category D Erroneous Refunds include any erroneous refund that is not included in any other erroneous refund category. The Category D Erroneous Refunds can also include any other Category of Erroneous Refunds if the ASED has expired but the ERSED is still open.

  2. The Erroneous Refund Unit in Accounting inputs a false credit (TC 700) on Category D Erroneous Refunds to remove the erroneous refund amount from Masterfile and reestablish the account in Accounting.

    1. This action prevents notices and administrative collection action (liens or levies) from occurring on the erroneous refund liability.

    2. The TC 700 credit can be identified by a Document Code 58 and a blocking series 950-999 in the DLN.

    3. These accounts will have a -U Freeze (generated by a TC 844) and it informs other employees the account is being worked and monitored in Accounting.

    4. Do not release the TC 700 credit.

  3. The IAT "Erroneous Refund" tool may be used in the processing of Category D erroneous refunds.

  4. When a Category D Erroneous Refund is identified within the ERSED statute:

    1. Issue Letter 510C using the IAT "Letters" tool. The date of the letter is considered to be the Date of Demand. Two copies of the letter are needed; one to attach to Form 12356, Erroneous Refund Worksheet, and one for the AUR case file.

      Exception:

      Do not send Letter 510C when the ERSED is expired. Refer to (10) below.

    2. Input the adjustment using the IAT "REQ54" tool for the TC 807 (W/H) and/or TC 252 (EXSST) using blocking series 55 and Hold Code (HC) 3. Use source document "Y" if including the original return with the adjustment.

      Note:

      Failure to Pay Penalty (FTP) under IRC 6651(a)(2) and (a)(3), does not apply to Category D erroneous refunds. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    3. Input any necessary credit transfers using the IAT "Credit Transfer" tool. Use TC 570 on the debit side to suppress the CP 60 Notice. The IAT "Credit Transfer" tool contains a box for Debit Freeze and Credit Freeze and will input the TC 570 when checked.

    4. Input TC 470 using the IAT "REQ77" tool. If the ERSED has expired, do not input TC 470.

    5. Input TC 971 AC 663 using the IAT "REQ77" tool.

    6. Input a TC 844 using the IAT "REQ77" tool for TP error or refunds of more than $50,000. If the ERSED has expired, do not input TC 844. Enter the date of the erroneous refund in the "TRANS-DT" field.

      Note:

      The TC 844 generates a "-U" freeze on the account and the TC 470 will stop all systemic notices and collection processes.

    7. Input a TC 844 using the IAT "REQ77" tool for IRS error and refunds of $50,000 or less. If the ERSED has expired, do not input TC 844. Enter the Date of Demand in the "EXTENSION-DT" field, the date of the erroneous refund in the "TRANS-DT" field and the erroneous refund amount in the "FREEZE-RELEASE-AMT" field.

      Note:

      The TC 844 generates a "-U" freeze on the account and the TC 470 will stop all systemic notices and collection processes.


    Once the adjustment posts on IDRS:

    1. Create a new IDRS control with Category ERRF, assign the IDRS control base to the Erroneous Refund Unit in Accounting (A/ER), change the status to "M" with activity code "ERRORREF" . The first five digits of the Erroneous Refund Units IDRS numbers are as follows:

      Site IDRS
      Austin 06113
      Cincinnati 02116
      Fresno 10117
      Kansas City 09113
      Ogden 04117
    2. Prepare Form 12356, Erroneous Refund Worksheet, and include a copy of all pertinent information (i.e., Form 3465, Adjustment Request, case history sheet, case notes, etc.), including a copy of the Letter 510C which was sent.

    3. Refer the case to the A/ER. See IRM 3.17.80-4, Erroneous Refund Coordinators, for a list of A/ER functions and their corresponding Erroneous Refund Coordinators.

    4. Close the case by assigning PC 28, 53, 68, or 88, as appropriate, or appropriate IPC on Recon cases.

      Note:

      When assigning PC 53, 68, or 88, complete the assessment window and enter an "M" in the AUTO/MANUAL IND field to indicate a manual assessment, as the adjustment was input on IDRS.

  5. If the case involves a combination of Erroneous Refund (Cat D- W/H, additional MCTXW, and/or excess SSTAX) and other AUR issues, take the following actions:

    1. Use the IAT "REQ54" tool to input the adjustment using blocking series 05 and "N" source document since the original will be kept to work other AUR issues.

    2. Monitor for the adjustment to post on both IDRS and AUR Tax Account.

    3. After the adjustment for W/H, additional MCTXW, and/or excess SSTAX posts, issue a CP 2000 for the remaining AUR issues, following normal AUR processing procedures.

      Note:

      Do not create a new IDRS control with Category ERRF.

  6. If before a Statutory Notice of Deficiency was issued, a Category D erroneous refund was due to the AUR payment refunding in error, when the account was paid in full, take the following actions:

    1. Send Letter 510C using the IAT "Letters" Tool. Two copies of the letter are needed; one to attach to Form 12356 and one for the AUR case file.

      Exception:

      If the erroneous refund is discovered during phone contact with the TP, a case history can be input on IDRS instead of issuing a Letter 510C. Advise the TP to void and return the check if it has not been cashed. Enter history "PHTPERRF" on IDRS using IDRS CC ACTON or IAT "ACTON" tool. The date you request repayment on the phone is the Date of Demand. Leave a detailed case note on AUR.
      The Philadelphia Call Site, after entering the case history on IDRS and advising the TP to void and return the refund check (if it has not been cashed), will check the action required box and leave a detailed case note for the controlling site to complete the erroneous refund procedures.

    2. Use the IAT "REQ77" tool to input TC 844 and TC 470.

    3. Work the case as an AUR agreed response, assigning PC 53, 67, or 87. If partial payment see (8) below.


    Once the adjustment posts on IDRS:

    1. Use the IAT "REQ77" tool to input TC 971 AC 663.

    2. See (4) 2nd step 1 above, to create a new IDRS control.

    3. Prepare Form 12356, Erroneous Refund Worksheet, and include a copy of all pertinent information (i.e., Form 3465, Adjustment Request, case history sheet, case notes, etc.), including a copy of the Letter 510C which was sent.

    4. Leave a detailed case note.

  7. If after a Statutory Notice of Deficiency has been issued, a Category D erroneous refund was due to the AUR payment refunding when the account was paid in full, take the following actions:

    1. Send Letter 510C using the IAT "Letters" Tool. Two copies of the letter are needed; one to attach to Form 12356 and one for the AUR case file.

      Exception:

      If the erroneous refund is discovered during phone contact with the TP, a case history can be input on IDRS instead of issuing a Letter 510C. Advise the taxpayer to void and return the check if it has not been cashed. Enter history "PHTPERRF" on IDRS using IDRS CC ACTON or IAT "ACTON" tool. The date you request repayment on the phone is the Date of Demand. Leave a detailed case note on AUR.
      If the case is controlled at a different site, check the action required box for the controlling site to complete the erroneous refund procedures.

    2. Use the IAT "REQ77" tool to input TC 844 and TC 470

    3. Request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.

    Once the adjustment posts on IDRS:

    1. Use the IAT "REQ77" tool to input TC 971 AC 663.

    2. See (4) 2nd step 1 above, to create a new IDRS control.

    3. Prepare Form 12356, Erroneous Refund Worksheet, and include a copy of all pertinent information (i.e., Form 3465, Adjustment Request, case history sheet, case notes, etc.), including a copy of the Letter 510C which was sent.

    4. Leave a detailed case note.

  8. If the Category D erroneous refund was due to the AUR payment refunding in error, when a partial payment was received, take the following actions:

    1. Send Letter 510C using the IAT "Letters" Tool. Two copies of the letter are needed; one to attach to Form 12356 and one for the AUR case file.

      Exception:

      If the erroneous refund is discovered during phone contact with the TP, a case history can be input on IDRS instead of issuing a Letter 510C. Advise the taxpayer to void and return the check if it has not been cashed. Enter history "PHTPERRF" on IDRS using IDRS CC ACTON or the IAT "ACTON" tool. The date you request repayment on the phone is the Date of Demand. Leave a detailed case note on AUR.
      If the case is controlled at a different site, check the action required box for the controlling site to complete the erroneous refund procedures.

    2. Use the IAT "REQ77" tool to input TC 844 and TC 470

    3. Assign PC 75 and release the case. Monitor the case for the PC 75 to post.


    After a Stat has been issued:

    1. Request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.

    2. Monitor IDRS for the adjustment to post. Once the adjustment posts on IDRS:

    3. Use the IAT "REQ77" tool to input TC 971 AC 663.

    4. See (4) 2nd step 1 above, to create a new IDRS control.

    5. Prepare Form 12356, Erroneous Refund Worksheet, and include a copy of all pertinent information (i.e., Form 3465, Adjustment Request, case history sheet, case notes, etc.), including a copy of the Letter 510C which was sent.

    6. Leave a detailed case note on AUR.

  9. If the case is in Reconsideration phase:

    1. Send Letter 510C using the IAT "Letters" Tool. Two copies of the letter are needed; one to attach to Form 12356 and one for the AUR case file.

      Exception:

      If the erroneous refund is discovered during phone contact with the TP, a case history can be input on IDRS instead of issuing a Letter 510C. Advise the taxpayer to void and return the check if it has not been cashed. Enter history "PHTPERRF" on IDRS using IDRS CC ACTON or IAT "ACTON" tool. The date you request repayment on the phone is the Date of Demand. Leave a detailed case note on AUR.
      The Philadelphia Call Site, after entering the case history on IDRS and advising the TP to void and return the refund check (if it has not been cashed), will check the action required box and leave a detailed case note for the controlling site to complete the erroneous refund procedures.

    2. Use the IAT "REQ77" tool to input TC 844 and TC 470

    Once the adjustment posts on IDRS:

    1. Use the IAT "REQ77" tool to input TC 971 AC 663.

    2. See (4) 2nd step 1 above, to create a new IDRS control.

    3. Prepare Form 12356, Erroneous Refund Worksheet, and include a copy of all pertinent information (i.e., Form 3465, Adjustment Request, case history sheet, case notes, etc.), including a copy of the Letter 510C which was sent.

    4. Leave a detailed case note.

  10. When the ERSED is expired, complete the following:

    1. Notate "ERSED Statute Expired" on the case.

    2. Complete Form 12356 and include a copy of all pertinent information.

    3. Use Form 12634, Correspondence Transmittal, or Form 3499, Informational Transmittal, to route case documentation to the appropriate Erroneous Refund Unit. See table in (4), 2nd step 1, above for routing information.

    4. Do not input TC 844 or TC 470.

    5. Do not send Letter 510C.

    6. Use the IAT "REQ77" tool to input a TC 971 AC 663.

    7. Leave a case note on AUR.

    8. Close case with PC 28, 52, 71, or 96, as appropriate.

4.19.3.4.11.2  (08-26-2016)
Repaid Erroneous Refunds

  1. Erroneous refunds which have been repaid may be discovered during AUR processing. Per IRC 6404(e)(2), a TP should not be charged interest if they did not cause the erroneous refund and the refund amount is under $50,000. Even though the refund was repaid, it is necessary to follow Category D erroneous refund procedures to protect the TP from interest charges.

    Note:

    Interest is not charged when a treasury check is returned (not cashed).

    Note:

    Interest is charged from the date of the refund if the erroneous refund amount is over $50,000.

  2. If the erroneous refund has been repaid take the following actions:

    Exception:

    If the TP returned the erroneous refund check (TC 841 on the account with "99999" in the DLN) see (3) below.

    1. Use the IAT "REQ77" tool to input TC 844, using the current date as the date of demand. This will reverse any systemically assessed interest.

    2. Complete Form 12356, Erroneous Refund Worksheet. In the details section include the following information, using the verbiage provided as an example: "Full paid erroneous refund. No Letter 510C sent. Please input TC 845 to reverse TC 844."

    3. Use the following table to determine the appropriate action:

      If Then
      The original payment was full payment received before a Stat was issued Work the case as an AUR agreed response, assigning PC 53, 67, or 87.
      The original payment was partial payment received before a Stat was issued
      1. Assign PC 75 and release the case.

      2. Monitor the case for the PC 75 to post and the Stat to be mailed.

      3. After the Stat has been issued, request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.

      Payment was received after a Stat was issued Request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.
      The case is in Reconsideration phase Use the IAT "xClaim" or "REQ54" tool to post the appropriate adjustment.


    Once the adjustment posts:

    1. See IRM 4.19.3.4.11.1.4(4), 2nd step 1 to create a new IDRS control.

    2. Use the IAT "REQ77" tool to input a TC 971 AC 663.

    3. Refer the case to the A/ER using Form 3210, Document Transmittal. See IRM 3.17.80-4, Erroneous Refund Coordinators, for a list of A/ER functions and their corresponding Erroneous Refund Coordinators.

    4. Leave a detailed case note on AUR.

  3. If the TP returned the erroneous refund check (TC 841 on the account with "99999" in the DLN) take the following actions:

    1. Use the IAT "REQ77" tool to input a TC 971 AC 663.

    2. Complete Form 12356, Erroneous Refund Worksheet. In the details section include the following information, using the verbiage provided as an example: "Check returned; TC 844 not needed. No Letter 510C sent."

    3. Use the following table to determine the appropriate action:

      If Then
      The original payment was full payment received before a Stat was issued Work the case as an AUR agreed response, assigning PC 53, 67, or 87.
      The original payment was partial payment received before a Stat was issued
      1. Assign PC 75 and release the case.

      2. Monitor the case for the PC 75 to post and the Stat to be mailed.

      3. After the Stat has been issued, request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.

      Payment was received after a Stat was issued Request the case and hold in unit suspense until the taxpayer responds or the suspense period has expired. If no response is received, default the case using the appropriate PC.
      The case is in Reconsideration phase Use the IAT "xClaim" or "REQ54" tool to post the appropriate adjustment.


    Once the adjustment posts:

    1. Refer the case to the A/ER using Form 3210, Document Transmittal. See IRM 3.17.80-4, Erroneous Refund Coordinators, for a list of A/ER functions and their corresponding Erroneous Refund Coordinators.

    2. Leave a detailed case note on AUR.

4.19.3.5  (09-01-2004)
Payer Agent

  1. The Payer Agent file is a compilation of Employer/Payer Information Return documents (Form W-2, Form 1099, Form 1098, etc.) which have been verified as erroneously filed or processed. The AUR Payer Agent file is tax year specific.

  2. Payer Agent (P/A) Indicator "Y" in the PA field of the Case Analysis screen indicates that the Payer Agent file contains data for the IR in question.

  3. Taxpayers and/or Employer/Payers may contact/notify AUR that a discrepancy with documents or the filing of IRs for a tax year has occurred. Tax examiners are encouraged to request that the TP and/or Employer/Payer forward the information to the site AUR Payer Agent Coordinator.

4.19.3.5.1  (05-04-2007)
Tax Examiner - Instructions

  1. Access the Payer Agent window for all IRs showing Payer Agent Indicator "Y" . The Payer Agent window lists the payer's name, EIN, document type, source, and a synopsis of the reporting problem. See IRM 4.19.7, IMF Automated Underreporter (AUR) Technical System Procedures - Viewing Payer Agent Information.

    Note:

    If all U/R income is from identified Payer/Agents and the Payer Agent window contains instructions to accept or delete the IR, close the case with PC 24. If U/R issues remain, continue normal processing (the P/A closing PC would NOT apply).

  2. During the screening phase, the tax examiner may identify questionable IRs, which appear to be erroneous but are not marked with a Payer Agent code "Y" . When IRs appear to be questionable and the tax examiner determines the IRs should be investigated, take the following steps:

    1. Print the Case Analysis screen and the Info Return screen.

    2. Forward both screen prints and any additional supporting information documents to the site AUR Payer Agent Coordinator.

    3. Continue normal processing.

  3. During the response phase, the examiner may receive information from the payer or the TP indicating the proposed U/R is the result of a payer reporting error, or a payroll processing mistake. Take the following action to forward the information to the site Payer Agent Coordinator:

    1. Photocopy the TP statement or payer letter and print the Case Analysis screen and the Info Return screen.

    2. Forward these photocopies and any additional supporting information documents to the site AUR Payer Agent Coordinator.

    3. Continue normal processing.

4.19.3.5.2  (09-01-2004)
AUR Site Payer Agent Coordinator - Instructions

  1. The AUR Site Payer Agent Coordinator will perform the following tasks.

    1. Take action on all IRs referred by tax examiners as questionable/suspicious Payer Agent data.

    2. Sort and review the screen prints received from tax examiners deemed questionable/suspicious. Begin research when four or more screen prints with the same EIN are identified. The Site P/A Coordinator should attempt to make a determination about the discrepant IRs. If payer contact is necessary to determine the impact, check IDRS for a telephone number or call XXX-555-1212 (XXX represents the area code of the city/state being called).

      Note:

      Revised Third Party procedures allow for the administrative action of verifying information received from Employers/Payers. This verification is not considered a third party contact if the purpose of the contact is to process information received from the source and/or to ensure its validity/correctness.

    3. Create a Payer Agent record when a Payer Agent record does not currently exist, and the information available leads to a determination that the Payer Agent should be added to the Payer Agent File.

    4. Update payer name and text lines, when required. There may be more than one type of income or source code for each Payer Agent EIN entered. Verify by scrolling both type and source fields; P=Paper and T=Tape (magnetic media).

    5. Input the EIN to search/query the Payer Agent File.

    6. View and/or print Payer Agent reports from the Payer Agent Coordinator menu.

    Note:

    A Payer Agent cannot be created if a Payer Agent record already exists for the EIN, document type, source code or tax year. If this condition exists, the system displays a message.

  2. At the end of the AUR program for the tax year, print a copy of the Payer Agent Listing and retain in the Payer Agent file for three years.

4.19.3.5.3  (09-04-2015)
National Designated AUR Payer Agent Coordinator - Instructions

  1. Employer/Payer identified IR filing discrepancies are submitted through the Enterprise Computing Center at Martinsburg (ECC-MTB) Management and Technology Information Returns Division. Documentation received from Employers/Payers is reviewed at ECC-MTB and copies are provided to the HQ (national) designated AUR Payer Agent Coordinator (currently located in Ogden). The HQ (national) designated AUR Payer Agent Coordinator has access to the national AUR Payer Agent File and is responsible for the input of all Employer/Agent Information Return documents received from ECC-MTB.

    Note:

    IR documents are identified as tape source or a combination paper/tape source.

  2. Query the Payer Agent File to determine if the Payer information received should be established or needs to be updated.

  3. A Payer Agent cannot be created if a Payer Agent record already exists for the EIN, document type, source code or tax year. If this condition exists, the system displays a message. To Update/Create a Payer Agent record:

    1. Enter the EIN of the identified Payer Agent.

    2. Select the appropriate document type from the list displayed.

    3. Enter the appropriate Source Code: "P" for Paper or "T" for Tape (magnetic media).

    4. Enter the payer name.

    5. Select or enter new instructions for the tax examiners.

  4. The AUR Payer Agent Program is automatically invoked during the weekly run process. The program updates the Payer Agent File for all sites during the weekly process with the new and updated records.

  5. Revised Third Party procedures allow for the administrative action of verifying information received from Employers/Payers. This verification is not considered a third party contact if the purpose of the contact is to process information received from the source and/or to ensure its validity/correctness.

4.19.3.6  (09-04-2015)
Determination of CP 2501 Issuance

  1. Issuance of a CP 2501 (assignment of PC 30) is required for the conditions listed below. In certain other situations, issuance of a CP 2501 may provide better customer service since it is an inquiry instead of a proposal of assessment. If in doubt, consult your lead or manager for guidance.

    Exception:

    Do not issue a CP 2501 when HQ issues direction to stop issuing CP 2501 at a certain point in the AUR processing year.

    1. The U/R income is $100,000 or more.

    2. Cases involving partially reported K-1 IRs when the discrepant amount is $50,000 or more per income type, per payer.

      Exception:

      Partially reported INT, DIV, LTCG, STCG, and ROYAL discrepancies do not require a CP 2501.

    3. Cases involving questionable underclaimed W/H and/or additional MCTXW that result in an overall refund. See IRM 4.19.3.15.1.2 (3), Withholding, SSTAX and Additional Medicare Tax Withheld - Miscellaneous, for further information.

      Exception:

      If the refund is due to U/C W/H from a Form 1099-SSA, and the income is reported correctly, do not issue a CP 2501.

    4. Cases resulting in an overall refund due to underreported income.

    5. Cases involving U/C excess SSTAX on ELF returns - see IRM 4.19.3.15.2 (16) c, Social Security Tax/Tier I Railroad Retirement Tax.

    6. Cases involving Form 8615, Tax for Certain Children Who Have Unearned Income, and the parent or child used the Qualified Dividends and Capital Gains Worksheet, Schedule D or Schedule J tax methods. See IRM 4.19.3.12.1, 8615 Window.

    7. Cases where the On File Date is the same for multiple IRs and none of the IRs are reported. See IRM 4.19.3.7.12.1 (10), Conduit Income - Analysis.

    8. Cases in Category 30 and EARN is being pursued.

      Note:

      If Earn is being pursued as a secondary issue (in category other than Category 30), issue a CP 2000.


More Internal Revenue Manual