3.13.2  BMF Account Numbers

Manual Transmittal

October 16, 2012

Purpose

(1) This transmits revised IRM 3.13.2, Campus Document Services, BMF Account Numbers.

Material Changes

(1) Editorial changes have been made through out this IRM.

(2) Multiple minor changes through out IRM due to feedback received from Course Development and the processing sites during clearance process..

(3) IRM 3.13.2.1.2(4) Added verbiage to Taxpayer Advocate Service subsection. IPU 12U0221 issued 01-23-2012

(4) IRM 3.13.2.1.4(1)b Revised text per SERP Feedback Control 201201047. IPU 12U0448 issued 02-17-2012

(5) IRM 3.13.2.1.4(1)c Added verbiage stating it is not necessary for Entity to correct existing errors in the Entity module. IPU 12U0345 issued 02-06-2012

(6) IRM 3.13.2.1.4(1)d Added Employer Identification Number (EIN) to parts of audit trail needed for documents that will be destroyed in the control team per SERP Feedback Control 201201312. IPU 12U0633 issued 03-12-2012

(7) IRM 3.13.2.1.4(17) Added verbiage regarding which address to use when writing the taxpayer per SERP Feedback Control 201202338. IPU 12U0890 issued 04-17-2012

(8) IRM 3.13.2.1.4(17) Revised paren for clarity.

(9) IRM 3.13.2.1.4 Added (18) stating the 6800sce/6801sce may be used in lieu of a specified letter if it contains all of the appropriate language. This change caused the remaining parens in the subsection to renumber. IPU 12U1054 issued 05-14-2012

(10) IRM 3.13.2.1.4(20) Revised text for clarity.

(11) IRM 3.13.2.1.4(21) Deleted paren as it is duplicated in IRM 3.13.2.2

(12) IRM 3.13.2.1.4(22) Revised text to include previously missing words. IPU 12U0345 issued 02-06-2012

(13) IRM 3.13.2.1.4(24) Added instructions to route questionable documents to Frivolous Return Program (FRP). IPU 12U0037 issued 01-03-2012

(14) IRM 3.13.2.1.4(24) Added instructions for routing fraudulent returns. IPU 12U0448 issued 02-17-2012

(15) IRM 3.13.2.1.4(24) Corrected IRM reference per SERP Feedback Control 201202328. IPU 12U0890 issued 04-17-2012

(16) IRM 3.13.2.1.4(24) - Corrected address for Frivolous Returns Program to M/S 4450. IPU 12U1319 issued 07-03-2012

(17) IRM 3.13.2.1.4(25) Added language regarding taxpayers with EO submodules that are not considered EO per SERP Feedback Control 201202105. IPU 12U0735 issued 03-26-2012

(18) IRM 3.13.2.1.4(26) Added verbiage stating all Exempt Organization (EO) cases are worked in Ogden. IPU 12U0152 issued 01-17-2012

(19) IRM 3.13.2.1.4(27) Added instructions to enter a description of the case being processed in the Remarks field of an IDRS change. IPU 12U1472 issued 08-06-2012

(20) IRM 3.13.2.1.5(1) Revised sequence number format. IPU 12U1472 issued 08-06-2012

(21) IRM 3.13.2.2.3(6) Added reference to IRM 3.13.2.25 per SERP Feedback 201200298. IPU 12U0221 issued 01-23-2012

(22) IRM 3.13.2.2.3(9) Removed erroneous text per SERP Feedback Control 201202194. IPU 12U0801 issued 04-02-2012

(23) IRM 3.13.2.2.4(9) Added GIFT TR to table of acceptable trust abbreviations. SERP Feedback Control 201105085 IPU 11U1575 issued 10/3/11 IPU 12U0037 issued 01-03-2012

(24) IRM 3.13.2.3(4) and (5) Added instructions to address changes for taxpayers that have a Large Corporation Indicator (LCI). Also added instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(25) IRM 3.13.2.3(17) Added verbiage stating it is not necessary for Entity to correct existing address abbreviation errors on EIN. IPU 12U0345 issued 02-06-2012

(26) IRM 3.13.2.3.2(5) Updated verbiage to reflect Form 8822-B, Change of Address - Business. IPU 12U0633 issued 03-12-2012

(27) IRM 3.13.2.3.2(5) Deleted erroneous text and link. IPU 12U1390 issued 07-19-2012

(28) IRM 3.13.2.3.2(7) Added instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(29) IRM 3.13.2.3.2(7) Updated instructions for Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(30) IRM 3.13.2.3.2(8) Added instructions when a return initiates an address change. IPU 12U1396 issued 7-23-12

(31) IRM 3.13.2.3.3(4) Added instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(32) IRM 3.13.2.3.3(4) Updated instructions for Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(33) IRM 3.13.2.3.4(13) Added instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(34) IRM 3.13.2.3.4(13) Updated instructions for Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(35) IRM 3.13.2.3.5(3) Added Document Locator Number (DLN) composition from National Change Of Address (NCOA) updates. IPU 12U0221 issued 01-23-2012

(36) IRM 3.13.2.3.5(5), (6), (7), and (9) Updated verbiage to reflect Form 8822-B, Change of Address - Business. IPU 12U0633 issued 03-12-2012

(37) IRM 3.13.2.3.5(6) Added verbiage to clarify action to be taken when third party submits address change request without authorization documents per SERP Feedback Control 201204241. IPU 12U1369 issued 07-16-2012

(38) IRM 3.13.2.3.5(10) Added instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(39) IRM 3.13.2.3.5(10) Updated instructions for Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(40) IRM 3.13.2.3.6(1) and (2) Added instructions to enter name and title of signature in Remarks field. Also deleted (2)(i) .IPU 12U0735 issued 03-26-2012

(41) IRM 3.13.2.3.6(1) and (2) Added verbiage and instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(42) IRM 3.13.2.3.6(2) Updated instructions for Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(43) IRM 3.13.2.3.6(2)c Updated instructions for a "complete" address change request. IPU 12U1442 issued 07-30-2012

(44) IRM 3.13.2.3.6(2) Revised identifiers within If/And/Then chart. IPU 12U0448 issued 02-17-2012

(45) IRM 3.13.2.3.7(1) and (4) Revised text and added instructions to enter name and title of signature in Remarks field. IPU 12U0735 issued 03-26-2012

(46) IRM 3.13.2.3.7 Updated instructions for completeness and Remarks field on address changes. IPU 12U1442 issued 07-30-2012

(47) IRM 3.13.2.3.7(2), (4), and (5) Added verbiage and instructions to enter address change requester's name, title, and phone number in Remarks field of transaction. IPU 12U0890 issued 04-17-2012

(48) IRM 3.13.2.4(4)c, IRM 3.13.2.4(4)d3, IRM 3.13.2.4.1(1)a Removed instructions to enclose Form 8822-B. IPU 12U1533 issued 08-27-2012

(49) IRM 3.13.2.4.1(1)a Added instructions to enclose a Form 8822-B to taxpayer when processing undeliverable per SERP Feedback Control 201204658. IPU 12U1505 issued 08-13-2012

(50) IRM 3.13.2.4.1(1)a Added instructions to enclose a Form 8822-B to taxpayer when processing undeliverable per SERP Feedback Control 201204658. IPU 12U1505 issued 08-13-2012

(51) IRM 3.13.2.4(6) Corrected text to reflect Form 8822-B. IPU 12U1319 issued 07-03-2012

(52) IRM 3.13.2.5 Deleted (10) and revised text in (5). IPU 12U0152 issued 01-17-2012

(53) IRM 3.13.2.6.1.11 Added (3) and (4) containing information on CC MFREQ Definer 'D' per SERP Feedback Control 201202190. IPU 12U0801 issued 04-02-2012

(54) IRM 3.13.2.6.2 Moved content of (5) to (10) for better flow. IPU 12U0448 issued 02-17-2012

(55) IRM 3.13.2.6.2 Added (9) for disposition of Form SS-4. IPU 12U0448 issued 02-17-2012

(56) IRM 3.13.2.7(3) Revised text for accuracy regarding MOD IEIN numbers not posted to Master File. IPU 12U0152 issued 01-17-2012

(57) IRM 3.13.2.7(7) Added instructions for Remarks field on return initiated address changes. IPU 12U1396 issued 7-23-12

(58) IRM 3.13.2.7(7) Updated instructions for Remarks field on address changes initiated by a return. IPU 12U1442 issued 07-30-2012

(59) IRM 3.13.2.7(9) Added (9) instructions when writing the taxpayer on returns which causes remaining parens to renumber. IPU 12U1054 issued 05-14-2012

(60) IRM 3.13.2.7(9) Deleted (9) as similar language is present in (7). IPU 12U1098 issued 05-21-2012

(61) IRM 3.13.2.7(7) Deleted instructions for Form 941-M as it is now obsolete. IPU 12U0037 issued 01-03-2012

(62) IRM 3.13.2.7- Deleted (7) as it contained duplicate information per SERP Feedback Control 201201396. IPU 12U0633 issued 03-12-2012

(63) IRM 3.13.2.7.2(7) Added verbiage per SERP Feedback Control 201202189. IPU 12U0801 issued 04-02-2012

(64) IRM 3.13.2.7.5(22) Added verbiage saying this corrective procedure only works for paper returns. IPU 12U1341 issued 07-09-2012

(65) IRM 3.13.2.7.5.1(7)d) Note Added text and corrected paren references in rows 'd' and 'k' per SERP Feedback Control 201201817. IPU 12U0684 issued 03-19-2012

(66) IRM 3.13.2.7.5.1(7) Rearranged and added verbiage to ensure TCs 971-375 and 971-376 are not input the same day. IPU 12U0933 issued 04-25-2012

(67) IRM 3.13.2.7.5.1(7)e Deleted unnecessary verbiage per SERP Feedback Control 201203321. IPU 12U1098 issued 05-21-2012

(68) IRM 3.13.2.7.5.1(7)(g) Added text per SERP Feedback Control 201202191. IPU 12U0801 issued 04-02-2012

(69) IRM 3.13.2.7.5.1(7)h(1) Added additional instructions for audit trail when Form 2553 is not attached to Form 1120S coded with Error Code 347. IPU 12U0448 issued 02-17-2012

(70) IRM 3.13.2.7.5.1(7) Added row "l" to provide instructions when an EIN must be assigned to Form 1120S filed under Rev. Proc. 2007-62. IPU 12U1140 issued 05-25-2012

(71) IRM 3.13.2.7.5.1(9)e) Added instructions to enter Audit Code 4 on return when renumbering per SERP Feedback Control 201203514. IPU 12U1194 issued 06-12-2012

(72) IRM 3.13.2.7.5.1(9)f) Added verbiage to ensure it is understood that a Reject Routing Slip is needed when converting EC347 returns to Forms 1120. IPU 12U0413 issued 02-14-2012

(73) IRM 3.13.2.7.5.1(10) Added (10) to offer guidance on statements of reasonable cause. IPU 12U1054 issued 05-14-2012

(74) IRM 3.13.2.7.6(3) and (4)Added instructions to procedures for Action Code 321. IPU 12U0037 issued 01-03-2012

(75) IRM 3.13.2.7.22(4) Revised verbiage on Form 7004 due date per SERP Feedback Control 201202193. IPU 12U0801 issued 04-02-2012

(76) IRM 3.13.2.7.22(7) Revised text to clarify the word "write" SERP Feedback Control 201105093 IPU 11U1575 issued 10/3/11. IPU 12U0037 issued 01-03-2012

(77) IRM 3.13.2.8.9 Added "OSPC Only" to title of subsection to ensure CSPC knows they will not process these documents. IPU 12U0037 issued 01-03-2012

(78) IRM 3.13.2.9(7) Added verbiage regarding which address to use when writing the taxpayer per SERP Feedback Control 201202338. IPU 12U0890 issued 04-17-2012

(79) IRM 3.13.2.9(7) Revised (7) removing reference to returns/documents. IPU 12U1054 issued 05-14-2012

(80) IRM 3.13.2.9.7(1)a and (1)b Provided additional instructions if taxpayer does not provide specific day business ceased. IPU 12U0152 issued 01-17-2012

(81) IRM 3.13.2.9.22(1) Expanded instructions for actions to be taken on Identity Theft EINs.

(82) IRM 3.13.2.9.22(2) Added all Action Codes used for Identity Theft. IPU 12U0345 issued 02-06-2012

(83) IRM 3.13.2.9.22 Added (2) to correct Command Code name per SERP Feedback Control 201200806. IPU 12U0413 issued 02-14-2012

(84) IRM 3.13.2.9.23(4) Added text stating X-REF fields should not be completed for non profit organizations. IPU 12U0037 issued 01-03-2012

(85) IRM 3.13.2.9.25 Updated all parens in subsection to supply instructions for all types of taxpayers under Section 1.482-7T per SERP Feedback Control 201202104. IPU 12U0735 issued 03-26-2012

(86) IRM 3.13.2.9.28(1)h Added text stating all Exempt Organization work is processed by Ogden Entity. IPU 12U0152 issued 01-176-2012

(87) IRM 3.13.2.9.30 Added new subsection for Correspondence requesting Address Changes. IPU 12U0890 issued 04-17-2012

(88) IRM 3.13.2.13.1(2) and (4)h Added text for clarification on EIN Consolidations per SERP Feedback Control 201202651. IPU 12U0923 issued 04-23-2012

(89) IRM 3.13.2.13.1(5) Removed reference to Form 941-M and Form 941-NMI as they are both obsolete. IPU 12U0037 issued 01-03-2012

(90) IRM 3.13.2.13.1(5) Added Form 1041-A to Filing Requirement Code (FRC) compatibility chart. IPU 12U1396 issued 7-23-12.

(91) IRM 3.13.2.16(3) Revised text for Form 2678 due to agent having authority to file FUTA returns on behalf of the Employer/Payer.IPU 12U0037 issued 01-03-2012

(92) IRM 3.13.2.16(4) Added text regarding multiple EINs for agents.

(93) IRM 3.13.2.16, IRM 3.13.2.16.1, IRM 3.13.2.16.2, and IRM 3.13.2.16.3 Minor verbiage changes regarding Form 2678 processing. IPU 12U0345 issued 02-06-2012

(94) IRM 3.13.2.16.3 Deleted (6) per SERP Feedback Control 201200815. IPU 12U0413 issued 02-14-2012

(95) IRM 3.13.2.16.3(8) Revised row (c) as it has been determined HHCSRs can have employees not covered by the agent agreement. IPU 12U0448 issued 02-17-2012

(96) IRM 3.13.2.16.5(2) Revised instructions for disposition of Forms 2678. IPU 12U0037 issued 01-03-2012

(97) IRM 3.13.2.17.1(6) Added instructions for assigning EIN to Form 2032. IPU 12U0037 issued 01-03-2012

(98) IRM 3.13.2.18.1(1)(f) Revised text to say fiduciary's name should be sorted per SERP Feedback Control 201201942. IPU 12U0735 issued 03-26-2012

(99) IRM 3.13.2.18.1(4) Added instructions to create "dummy" Form 56 if correspondence is received in lieu of Form 56. IPU 12U1442 issued 07-30-2012

(100) IRM 3.13.2.18.2(1) Revised text regarding termination of fiduciary relationship. IPU 12U1442 issued 07-30-2012

(101) IRM 3.13.2.20 Added (10) stating elected FYMs cannot adopt a 52-53 week tax year. IPU 12U0345 issued 02-06-2012

(102) IRM 3.13.2.20.3.5 Returned text to bullet list erroneously removed in a previous IPU. IPU 12U0037 issued 01-03-2012

(103) IRM 3.13.2.20.5(3) Deleted rows h and I from table as they contained duplicate text. IPU 12U0037 issued 01-03-2012

(104) IRM 3.13.2.22(1) Added instructions to use 312C when processing correspondence requesting an S election and has missing information. IPU 12U0933 issued 04-25-2012

(105) IRM 3.13.2.22(6) Deleted erroneous text relating to TC 092 per SERP Feedback Control 201201333. IPU 12U0633 issued 03-12-2012

(106) IRM 3.13.2.22.1(3) b and c Revised verbiage to say letter will be sent to address on Form 2553 rather than Master File. SERP Feedback Control 201105424 IPU 12U0037 issued 01-03-2012

(107) IRM 3.13.2.22.1(3) Several changes to Address portion of Form 2553 subsection. IPU 12U1054 issued 05-14-2012

(108) IRM 3.13.2.22.1(3)d Added instructions to send letter to address on Master File. IPU 12U0345 issued 02-06-2012

(109) IRM 3.13.2.22.1(3) Added Note with instructions to check the address last update cycle when considering updating an address on Form 2553.

(110) IRM 3.13.2.22.1(8) Added text stating the date of incorporation should always be considered for the effective date of Form 2553. IPU 12U0037 issued 01-03-2012

(111) IRM 3.13.2.22.1(22) Added instructions for TC 092 input. IPU 12U0037 issued 01-03-2012

(112) IRM 3.13.2.22.2(5) Added Single Member LLC to the list of taxpayers not eligible to make a Subchapter S election per SERP Feedback Control 201201139. IPU 12U0633 issued 03-12-2012

(113) IRM 3.13.2.22.2(5) Expanded language for SMLLC as a shareholder and added (6) which caused the remaining parens to renumber per SERP Feedback Control 201202046. IPU 12U0735 issued 03-26-2012

(114) IRM 3.13.2.22.2(7) Added the range of valid numbers for 4th and 5th digits of ITINs. IPU 12U0345 issued 02-06-2012

(115) IRM 3.13.2.22.4(7) Corrected tridoc reference. IPU 12U0933 issued 04-25-2012

(116) IRM 3.13.2.22.4 Added (8) to offer guidance for statements of reasonable cause. IPU 12U1054 issued 05-14-2012

(117) IRM 3.13.2.22(6) Added text to clarify history and use of TC 093. IPU 12U0448 issued 02-17-2012

(118) IRM 3.13.2.22.7(2) NOTE Added "/or" to language regarding Action Codes 375 and 376. . IPU 12U0037 issued 01-03-2012

(119) IRM 3.13.2.22.9(5) Revised verbiage to say photocopy the first page of Form 2553. IPU 12U0345 issued 02-06-2012

(120) IRM 3.13.2.22.17(7) Revised instructions for reversing invalid S corporation election due to entity not being incorporated at time of election. SERP Feedback Control 201105086. IPU 12U0037 issued 01-03-2012

(121) IRM 3.13.2.22.18(2) Corrected erroneous language. IPU 12U1472 issued 08-06-2012

(122) IRM 3.13.2.22.18(9) Added instructions to use 312C for missing information on an S election revocation. IPU 12U0933 issued 04-25-2012

(123) IRM 3.13.2.22.18(8) Added instructions to verify if an Limited Liability Company (LLC) is revoking the Entity Classification. Renumbered paragraphs as appropriate. SERP Feedback 201203484. IPU 12U1194 issued 06-12-2012

(124) IRM 3.13.2.22.19(7) Added instructions for the input of the TC 077 for LLC's revoking the Entity Classification. SERP Feedback 201203484. IPU 12U1194 issued 06-12-2012

(125) IRM 3.13.2.22.23(5)(e) Added instructions to use 312C for an incomplete QSST. IPU 12U0933 issued 04-25-2012

(126) IRM 3.13.2.22.23(8) and (11) Added instructions to send 385C to trust if prior QSST on IDRS. IPU 12U1396 issued 7-23-12.

(127) IRM 3.13.2.22.25(2) Added (e) stating 312C should be used when requesting additional information on an ESBT election. IPU 12U0933 issued 04-25-2012

(128) IRM 3.13.2.22.25(8) and (9) Added instructions to send 385C to trust if prior ESBT on IDRS. IPU 12U1396 issued 7-23-12.

(129) IRM 3.13.2.23(9) Added row e for scenario of parent not having valid S election. IPU 12U0933 issued 04-25-2012

(130) IRM 3.13.2.23(10) Added 326C as the letter to be sent on a QSub termination. IPU 12U0933 issued 04-25-2012

(131) IRM 3.13.2.24(1) Revised instructions for routing of Forms 966 not worked in Entity. IPU 12U0037 issued 01-03-2012

(132) IRM 3.13.2.25(2) Added description of LLC-CD on IDRS. IPU 12U0037 issued 01-03-2012

(133) IRM 3.13.2.25(2) Added verbiage regarding abbreviations LC and PLLC.

(134) IRM 3.13.2.25(11) Removed erroneous text per SERP Feedback Control 201201844. IPU 12U0684 issued 03-19-2012

(135) IRM 3.13.2.25(11) Added verbiage regarding Revenue Ruling 2004-77. The remaining parens renumbered.

(136) IRM 3.13.2.26.2(3)(c) Added text to ensure consistency with IRM 3.13.222 per SERP Feedback Control 201201845. IPU 12U0684 issued 03-19-2012

(137) IRM 3.13.2.26.5(1) Added "Line 8" to items not to be requested unless other information is missing from Form 8832.

(138) IRM 3.13.2.26.6(4) Added NOTE to use PSC - Z when processing Form 8832 with Form 2553. SERP Feedback Control 201104947. IPU 12U0037 issued 01-03-2012

(139) IRM 3.13.2.26.6(7) Revised procedures for photocopying Forms 8832 for SOI. IPU 12U0633 issued 03-12-2012

(140) IRM 3.13.2.26.6(7) Added parenthesis per SERP Feedback Control 201202087. IPU 12U0735 issued 03-26-2012

(141) IRM 3.13.2.26.10(5) Added verbiage for termination date when a new Form 8832 is not received. SERP Feedback Control 201105092. IPU 12U0037 issued 01-03-2012

(142) IRM 3.13.2.26.10(5) Revised text to ensure TEs know the S election terminates only if 8832 is withdrawn/rescinded. IPU 12U0152 issued 01-17-2012

(143) IRM 3.13.2.26.11(6) Added instructions for scenario of taxpayer stating Form 8832 was submitted requesting an incorrect effective date. IPU 12U0037 issued 01-03-2012

(144) IRM 3.13.2.28(3) If/Then Chart Added 6800sce to instructions for Form 8855. IPU 12U0037 issued 01-03-2012

(145) IRM 3.13.2.28(3)a Editorial correction: changed the word "trustee" to "trust" . IPU 12U0152 issued 01-17-2012

(146) IRM 3.13.2.28(3)(h) Revised identifiers in If/And/Then chart and added verbiage to line 3 regarding name change verification per SERP Feedback Control 201201138. IPU 12U0633 issued 03-12-2012

(147) Exhibit 3.13.2-2 Added CP 278 to table of transaction codes and notices generated. IPU 12U0152 issued 01-17-2012

Effect on Other Documents

This material supersedes IRM 3.13.2 dated January 1, 2012. This IRM also incorporates the following IRM Procedural Updates (IPU): 12U0037, 12U0221, 12U0345, 12U,0413, 12U0448, 12U0633, 12U0684, 12U0735, 12U0801, 12U0890, 12U0923, 12U0933, 12U1054, 12U1098, 12U1140, 12U1194, 12U1319, 12U1341, 12U1369, 12U1390, 12U1396, 12U1442, 12U1472, 12U1505, and 12U1533.

Audience

W & I Submission Processing Employees

Effective Date

(01-01-2013)

Paul J. Mamo
Director, Submission Processing
Wage and Investment Division

3.13.2.1  (01-01-2013)
General Information

  1. This IRM provides procedures for establishing, maintaining and updating entities on the Business Master File (BMF).

  2. The instructions for processing Form SS-4 and using CC ESIGN are located in IRM 21.7.13 , Assigning Employer Identification Numbers. Reference to this manual is necessary when processing Form SS-4 or using CC ESIGN to assign an Employer Identification Number (EIN) for a return, document, or payment.

  3. The following IRMs and publications are used in conjunction with this IRM section:

    • Document 11426, IRS Correspondence Manual

    • IRM 2.3, IDRS Terminal Responses

    • IRM 2.4, IDRS Terminal Input

    • IRM 3.0.273, Administrative Reference Guide

    • IRM 3.5.10, Remittance Transaction Research (RTR) System

    • IRM 3.5.61, Files Management and Services

    • IRM 3.10.72, Extracting and Sorting

    • IRM 3.10.73, Batching and Numbering

    • IRM 3.11.16, Returns and Documents Analysis-Corporate Income Tax Returns

    • IRM 3.12.32 , General Unpostables

    • IRM 3.12.37, General Instructions

    • IRM 3.12.166, EPMF Unpostables

    • IRM 3.12.278, Exempt Organization (EO) Unpostable Resolution

    • IRM 3.12.279, BMF/CAWR/PMF Unpostable Resolution

    • IRM 3.13.5, IMF (Individual Master File) Account Numbers

    • IRM 3.13.12, EO Account Numbers

    • IRM 3.13.36, EPMF Account Numbers

    • IRM 3.13.62, Media Transport and Control

    • IRM 3.13.222, BMF Entity Unpostable Correction Procedures

    • IRM 3.30.123, Processing Timeliness Cycles, Criteria, Critical Dates

    • IRM 10.5.3, Privacy, Information Protection and Data Security, Identity Theft and Incident Management Program

    • IRM 11.3.1, Disclosure of Official Information-Introduction to Disclosure

    • IRM 11.3.2, Disclosure of Official Information-Disclosure to Persons with a Material Interest

    • IRM 13.1.19, Taxpayer Advocate Case Procedures - TAS Operations Assistance Request (OAR) Process

    • IRM 21.7.13, Assigning Employer Identification Numbers

    • Pub 15, Circular E - Employer's Tax Guide

  4. This IRM addresses Entity actions on returns, forms, documents and payments.

    • Return - Filed by taxpayers to report income/loss. Returns post to Master File as TCs 150.

    • Form/document - Elective filings for various purposes: electing corporate status, FYM changes or elections, appointment of fiduciary or agent, etc.

    • Payment - Received in the form of Rejects and payments from Accounting Services. Remittance Transaction Research (RTR) will be utilized.

  5. The Integrated Automation Technologies - IAT:

    1. IAT provides tools to IRS employees that simplify research, reduce keystrokes and increase the accuracy of regular work processes.

    2. When IAT is used with IRS systems, it eliminates repetitive typing and making precise decisions.

    3. The use of IAT is mandatory. See the IAT web site at http://idap.web.irs.gov/IATRequest/Enhancement/default.asp for a list of available tools and User Guides.

    4. Managers will ensure that all employees receive training on the use and application of IAT tools.

    5. Appropriate research will be completed using CCs NAMEE, NAMEB, NAMES, NAMEI, FINDE and the Secretary of State offices.

3.13.2.1.1  (01-01-2013)
Section (§) 3705 (a), IRS Employee Contacts

  1. Background -

    1. The Restructuring and Reform Act of 1998, §, provides identification requirements for all IRS employees processing tax related matters.

    2. IRS employees are required to give their name and unique identification number during taxpayer telephone, face to face or written contact. In addition a telephone number is required on all taxpayer correspondence.

    3. This will provide taxpayers with enough information to identify an IRS employee who has previously assisted with tax related matters.

  2. Key Points - All IRS employees in the campus, national or area office who communicate by telephone, correspondence or face to face with taxpayers or their personal representatives on tax related matters are required to provide (at a minimum) the following information:

    1. With telephone contact, the caller must provide their title, last name and their unique identifying number.

    2. With face to face contact provide your title and last name during the conversation and your badge ID number.

    3. Never leave any taxpayer information on the taxpayer's answering machine or voice mail per IRM 11.3.2.

  3. Correspondence - All correspondence must include a telephone number the taxpayer can call to have questions answered.

  4. Office of Management and Budget (OMB) Codes are not required when issuing a letter to the taxpayer per 5 CFR 1320.3 (h) (6).

  5. The IDRS numbers are automatically generated for the Correspondex letter system. If another letter system is used, the unique IDRS number must be used.

  6. Faxes to taxpayers on tax related matters, are considered manually-generated correspondence and must include the required information. See IRM 11.3.1 for Disclosure requirements on faxing.

  7. Correspondence, whether sent directly to the taxpayer or to the taxpayer's personal representative, must contain: the nature of the taxpayer's inquiry and our actions taken.

  8. When sending a correspondex letter and Receipt and Control Operation was not required to date stamp the return, determine the received date using the following priorities:

    1. Latest postmark on the envelope or latest date from a private delivery service mark

      Note:

      When the envelope or label is not attached, use the postmark date stamped or handwritten on the return to determine the received date

    2. Latest date by the taxpayer's signature (Exception: Use the signature date for prior year returns only when it is within the current year; also, do not use the signature date to determine the received date for replies to correspondence),

    3. Julian date minus 10 days (Julian date is in the Document Locator Number (DLN), see Document 6209).

    4. Today's (current) date minus 10 days.

  9. When a taxpayer insists on speaking with a specific employee who previously processed their inquiry or request, or complains about the level of service previously provided, every attempt will be made to resolve the taxpayer's inquiry. If the issue cannot be resolved, the Entity Tax Examiner will refer the inquiry using established procedures to his or her manager.

  10. An Entity phone number must be provided in letters regarding Entity specific forms. When returning incomplete documents to the taxpayer, an Entity phone number must be used unless an Entity Check Box Letter (6800sce or 6801sce) is used. The BMF Toll Free Number (1-800-829-0115) may be provided in general BMF correspondence letters. If the 6800sce or 6801sce are used, input a history item on CC ENMOD that reflects the letter sent on the first line and the document returned on the second line. The number of characters allowed on each line of a history item are limited therefore keep each line under eight characters. For example:

    6800SCE
    W2553

    or

    6801SCE
    4UNDEL

  11. Before writing the taxpayer, examine the case completely so that all of the issues/conditions can be included in the same correspondence. If additional information is needed, the second correspondence must include a paragraph of apology for any inconvenience.

  12. Before returning a document to the taxpayer for completion, a blue "X" will be placed over all IRS received dates. This will ensure the validity of the received date if/when the taxpayer responds.

  13. If there is an election on record and the taxpayer erroneously submits another document (Form 8832, Form 2553, Form 1128, etc.), prepare the document for destruction per local procedures. Do not return the document to the taxpayer.

  14. Entity may be contacted by internal customers (other IRS employees) for assistance with Entity issues. For example, assigning EINs, correcting effective dates, updating Entity information on an account, etc. Ask them to fax you any pertinent data so you can service their request. Take an In and Out count for each EIN that received Entity action. Below are some examples of requests received from internal customers:

    • A Revenue Agent (RA) from Compliance/Exam needs EINs for taxpayers before they can open an investigation due to the taxpayer not paying their excise tax. The RA prepares the Substitute For Return (SFR) excise return and e-mails it to Cincinnati Submission Processing Center(CSPC) Entity. The receiving Tax Examiner (TE) assigns the EIN(s) and e-mails them (encrypted) back to the RA.

    • IRM 3.14.2.4.6.2.3 , Notice Review-BMF Notice Review, instructs Notice Review Tax Examiners (TEs) to send photocopies of returns and/or notices to Entity for review of any questionable names (and addresses) they discover. Entity TEs will research IDRS and make any necessary corrections to the taxpayer's account. The TE may take an In and Out count for each EIN touched. Once the correction is made, the photocopies will be prepared for destruction and placed in the TEs Quality Review folder.

  15. Letters generated by Submission Processing must be approved by Headquarters when they are intended for dissemination to 10 or more persons. These letters are numbered in accordance with IRM 1.17.1 and IRM 1.17.2, Printing and Publication. Form letters, pattern letters, and pattern paragraphs are prescribed by Headquarters for use in service centers. DO NOT make changes to text format, date of issue (or revision), or physical characteristics of these letters and paragraphs without prior Headquarters approval. In addition, Quick Notes that are computer generated must be forwarded to Headquarters for approval. Submit requests for new letters using Form 1767, Publishing Services Requisition, following procedures outlined in IRM 1.17.1 and 1.17.2. For minor changes or additions to current letters, follow procedures in IRM 3.0.275, Business Results Measures for Submission Processing Functions.

3.13.2.1.2  (01-01-2013)
Taxpayer Advocate Service (TAS) Service Level Agreements

  1. The National Taxpayer Advocate and the Commissioner, W&I Division have reached an agreement outlining the procedures and responsibilities for processing Taxpayer Advocate Service (TAS) casework when either the statutory or delegated authority to complete a case transaction rests with the W&I Division. The Service Level Agreements (SLAs) can be found under "TAS Favorites" at TAS' web site: http://tas.web.irs.gov/

  2. In preparation for a case being referred to a W&I Division function, the
    TAS employee is responsible for:

    • Preparing Form 12412 , Operations Assistance Request (OAR).

    • Securing all necessary supporting documentation,

    • Forwarding Form 12412 and documentation on Form 3210 , Document Transmittal, to the W&I Division liaison,

    • Clearly identifying an OAR requiring expeditious treatment.

  3. W&I Division is responsible for:

    • Assigning a liaison in each office or campus where a Taxpayer Advocate is located,

    • Acknowledging receipt of the case via Form 3210 within one workday for cases designated as "expedite" or within three days for cases not designated "expedite," '

    • Responding to TAS within three workdays for cases identified "expedite" in writing, via facsimile or hand delivery regarding the relief/no relief decision,

      Note:

      If utilizing fax, use blue or black ink in audit trail and on OAR.

    • Negotiate with TAS a reasonable time frame for resolution of cases not designated "expedite"

    • Providing TAS with the name and telephone number of the W&I employee assigned the case,

    • Upon resolution of the case, the W&I employee will complete Section VI of Form 12412 and return it to the TAS employee within three work days from the date all actions have been completed and/or transactions posted.

  4. BMF Entity TEs will be responsible for:

    • Researching prior modules for previous unpostable returns filed by the taxpayer, specifically TC 971 ACs 375, 376, and 377. CC TRDBV will be used to determine if the DLN of previous unpostables has been cancelled.

    • Researching IDRS for any history items identifying letters sent by Entity Unpostables and/or Entity relating to Form 2553 and/or Form 1120S. See CCs BMFOL, ENMOD, TXMOD, UPTIN, UPDIS, and TRDBV.

    • Considering completeness of previously submitted Forms 2553. Historically, Entity and Entity Unpostables were not able to approve S elections ‘for the next qualifying year.’ Therefore, there are taxpayers with denied elections that could have been approved for two years from the requested effective date. For example, T/P submitted incomplete 2553 for 2005 under a Rev. Proc. and election was denied. T/P was complete and timely for 2006, therefore election should be approved for 2006.

    • Considering T/P intent and responsiveness.
      Did T/P respond to IRS letters?
      Is there evidence the T/P re-submitted complete Form 2553?
      Is there evidence T/P contacted IRS regarding Form 2553/Form 1120S issues?
      Did T/P submit corrected return?

    • Verifying T/P took appropriate route before contacting TAS: Did T/P take appropriate route for assistance before contacting TAS? See IRM 13.1.7.2. Did T/P call MeF Help Desk? Did T/P respond to Entity/Entity Unpostable letters?

    • Having the history of processing procedures for various Entity forms (2553, 8832, 2678, etc.) and possibly consider those procedures in evaluating the TAS cases.

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  5. For additional information see IRM 13.1.19, Taxpayer Advocate Case Procedures - TAS Operations Assistance Request (OAR) Process.

3.13.2.1.3  (01-01-2013)
Disaster Relief

  1. When an official disaster is declared due to natural events, military, or terroristic action, the Federal Emergency Management Agency (FEMA) releases a memo detailing the type of assistance taxpayers will receive.

  2. The memo also lists the zip codes affected by the disaster. Disaster Code "-S" freeze will be automatically applied to the Master File accounts of taxpayers located in the IRS Designated Disaster Area for automatic filing and payment relief. The list of designated disaster areas identified for "-S" freeze action has been provided to MITS and will be posted to http://www.tris.irs.gov/fema/.

  3. This information is also posted to the SERP homepage in the grey column on the left side of the window:
    http://serp.enterprise.irs.gov/databases/irm-sup.dr/disaster.dr/disaster-toc.htm

  4. Generally, 60 additional days are granted to taxpayers affected by disasters.

  5. Affected taxpayers who reside or have businesses located outside the designated disaster area must call the IRS disaster toll free number, 1-866-562-5227, to self-identify for disaster relief.

  6. IRC Sections 7508 and 7508A govern the events that may be postponed due to the declaration of a Designated Disaster Area.

3.13.2.1.4  (01-01-2013)
General Entity Procedures

  1. The following are basic procedures for all cases processed in Submission Processing BMF Entity:

    1. Batch all documents with appropriate control form/batch sheet. BMF Entity uses Entity Batch/Block Tracking System (BBTS).

    2. All incoming documents/correspondence will be stamped with an IRS/Entity received date stamp. This includes faxes received within any Entity team. The dates stamped by fax machines or a Fax Transmission Verification Report will not be used for determining timeliness. It is not necessary for Entity to date stamp returns (documents that post as a TC 150).

    3. Perfect entity for processing: underline the name control per exception, correct the name (as needed per research of the Secretary of State's office via the internet), EIN, name control, address, Fiscal Year Month (FYM) or tax period, Filing Requirements Codes (FRCs) etc. if needed, and annotate your actions in the lower left corner of the document. All documents touched by Entity will bear the TE's IDRS number and date. It is not necessary for Entity to correct existing abbreviation errors on the Entity module unless accessing the EIN for other Entity corrections.

    4. Documents that will be destroyed in the control team (Forms 8822-B, correspondence, etc.) do not need a complete audit trail. TE IDRS number, EIN (if not on document) and date are sufficient. Place a large blue (or orange or purple) "X" on the document that will be destroyed and return it to your pack of documents. The control team will destroy the document upon their breaking down of the employee folders.

    5. When processing returns, it is not necessary to address minor name differences (for example, INC versus INCORPORATED or Co. versus Company) unless the name control is affected.

    6. Always use CCs NAMEE and NAMEB when researching for a missing or invalid EIN.

    7. If a taxpayer submits an original document (birth certificate, marriage license, passport, etc.) with their correspondence, prepare a Form 3699, Return of Documents to Taxpayer, and return the item to the taxpayer.

    8. If the IRS pre-printed label data is correct/without changes, do not underline the name control. If ANY change has been made to the label data, circle out the check digits and underline the name control.

    9. Always return an acknowledgement request back to the originator or requester.

  2. Various colors of ink are used by Entity TEs. See chart below.

    Ink Color Purpose
    Orange Used by Cincinnati for all documents, except returns processed by the Service Center Recognition/Image Processing System (SCRIPS) returns.
    Purple Used by Ogden for all documents, except SCRIPS returns.
    Blue Used by both sites to mark out IRS received dates on documents being returned to the taxpayer
    Blue, Orange, or Purple Used to place large "X" on documents to be destroyed in clerical team
    Blue or black Used on any document to be faxed back to the customer. For example, Social Security Administration (SSA) requests
    Green Used on SCRIPS returns

  3. Throughout this IRM the words expeditious treatment/treated expeditiously are used. This means the case will be processed immediately upon assignment. You will put your other cases aside and give this case expeditious treatment. Batches labeled expedite are low in volume. Once finished with the expedite work, the cases that were put aside will be processed.

  4. Providing instructions that will cover all combinations of changes that might appear on a given case is not possible. Therefore, where procedures are given for a specific situation (for example, name change) and the case also needs other actions, make all changes necessary to perfect the account. This includes perfecting effective dates and FYMs.

  5. Anytime an Entity Tax Examiner discovers a return or payment posted incorrectly, they must route a Form 3465, Adjustment Request, to AM/Adjustments to have the return/payment moved and posted correctly.

  6. Returns, forms, correspondence and direction from the taxpayer regarding their account will be accepted according to the terms of prima facie, otherwise, upon first examination the matter appears to be self-evident.

  7. It may become necessary for Entity TEs to create Dummy documents for use as source documents for the input of certain transactions: TC 053, TC 054, TC 055, TC 076, TC 090, TC 094, TC 098 etc. To create and process a Dummy document you will:

    1. Write the word Dummy across the top of a blank Form 1128, Form 8716, or Form 2553, etc.

    2. Complete the entity portion of the document with the taxpayer's name, address, and EIN.

    3. Enter the following on the document (if applicable): sequence number, effective date, FYM, Posting Delay Code, Blocking Series.

    4. When processing Dummy documents, always suppress the IDRS generated Computer Paragraph (CP) notice by inserting "Z" in the Paragraph Selection Code. (PSC) field of CC BNCHG. It may be necessary to correspond with the taxpayer.

    5. Annotate the document with the reason a Dummy document is needed, for example: "TC 057 erroneously reversed -taxpayer did not terminate 444" . An audit trail containing IDRS number and the date of actions taken will be written in the bottom, left corner of every return/document.

    6. Input transaction into IDRS and place document in source document folder.

    7. If inputting a TC 076 from a Dummy Form 8832, research IDRS and the taxpayer's correspondence or conversion/reorganization paperwork to determine the correct input for the Type of Entity (TOE) and Form of Entity (FOE).

  8. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  9. Whenever feasible, Entity Tax Examiners will initiate telephone contact with the taxpayer before returning an incomplete document to them. When returning incomplete documents to the taxpayer, all internal documents must be removed from the enclosure and the IRS received dates will be X'd out in blue ink.

  10. If a request is received requesting copies of documents via correspondence, Form 4506, Form 4506T, etc., Ogden Entity Department will forward the request to the Return And Income Verification Services (RAIVS) Team, mail stop 6734. Cincinnati Entity Department will forward the request to the RAIVS Team mail stop 2800F.

  11. If you are processing a case and the taxpayer requests a photocopy of his Entity related form (Form 2553, Form 8716, Form 1128, etc.), use CC ESTAB to retrieve the document from Files. Once received, make a photocopy and write the word "COPY" on the document. Include the photocopy in a 1275C to the taxpayer. If you are not processing a case, correspond with the taxpayer informing him of Form 4506, Request for Copy of Tax Return. Inform the taxpayer that a fee is required.

  12. Correspondence Imaging System (CIS) is an inventory system for scanning all documents received in Accounts Management (AM) and creating digital images of the documents/correspondence. AM processes their cases from these images. The original documents are not retained.

    • CIS documents are identified by the words CIS Image. Do not correspond for signature stamped below the signature line, or CIS is annotated on the front of the document. These annotations are from Accounts Management and do not apply to Submission Processing.

    • AM processes the CIS image prints in the same manner as original forms, documents, or correspondence.

    • All Entity forms must have a signature before they can be processed. Take the necessary action to secure signatures for each Entity form that has been imaged by CIS.

  13. GUF reports 55-40 and 55–47 will be monitored for the erroneous creation of unpostables by Entity TEs. This report will be processed weekly as there may be unpostable transactions awaiting an Entity correction. See IRM 3.12.32 and IRM 3.12.279 . This report is available on Control D.

  14. Report CCA 42-43 will be monitored for IDRS open control bases created by the auto closure of certain unpostables. This report must be processed weekly to ensure all accounts touched by Entity reflect correct information, including FRCs and FYMs. This report is available on Control D.

  15. To view tax returns electronically filed on Modernized e-file (MeF), users must first request access to the Employee User Portal (EUP).

  16. When corresponding with the taxpayer, use the appropriate letter that accurately addresses the taxpayer's situation and always use the selective paragraphs that are available in the correspondex letters before using open paragraphs. For example, do not use a 385C to inform the taxpayer of their valid EIN or denied/rejected election. Do not use a 147C on any election issues.

  17. When using CC LETER, you must determine the taxpayer's correct address.

    • If the address on the return/document matches Master File (mailing or location), use that address.

    • If the address on the return/document does not match Master File and the address change box is marked, update Master File and send all letters to this address.

    • If the address on the return/document does not match Master File and the address change box is not marked, use the address on Master File and request clarification on the address discrepancy, .

    • If the return/document does not have an address change box, use the address on the return/document including information about the address discrepancy.

    • When processing Form 7004, all letters will be sent to the mailing address on Master File. Extension requests are usually filed by third parties that tend to enter their own address on the Form 7004.

  18. If the 6800sce/6801sce contains all of the appropriate language for a scenario, they may be used in lieu of a letter specified in this IRM.

  19. When processing cases it may become necessary to photocopy a document. Whenever a photocopy is made, the word copy will be entered on the document by either a watermark or manual editing.

  20. Trust and Partnership EINs beginning with prefixes 20, 26, 27,45, 46 and 47, will reflect the first four characters of the primary name as the name control. Entity TEs will not alter the name control of these EINs because employees in the pipeline understand the different name control procedures for Mod IEIN. Other EIN prefixes will be name controlled by the historical method: the first four characters of the first last name if the entity is owned by individuals, Corporate trusts are name controlled as corporations. For example, do not change the name control of an EIN beginning with 27 because it does not match historical Submission Processing name control procedures. However, if you identify an EIN with prefixes 20, 26, or 27 that has previously been changed to match SP historical procedures, input TC 013 to make the name control match the procedures for these prefixes.

  21. Entity TEs are not responsible for deleting duplicate entity information (primary name and sort name and/or mailing address and location address unless they are going into the account to make another entity change. If both fields are duplicated on IDRS, Entity TEs will remove the duplicate information in both fields.

  22. Many types of entities are required to register with the Secretary of State's office in their state of origin. This is not always the physical location of the business. Entity will research the internet web sites of Secretary of State's offices as needed to learn the history of the business, owners, status with the state, etc.

  23. If the primary name line and the care of name line are identical, input of the care of name line is not required.

  24. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  25. Due to new programming in Exempt Organizations (EO), there are substantially more EINs reflecting an EO submodule. Many of these EINs are in a "bad" status. An entity is considered BMF, not EO, if it is in status 19, 22, 41, 70, 71, 72, 97, 98, or 99. Any document received for this type of taxpayer should be worked by BMF TEs.

  26. Cases involving EO taxpayers should only be processed at Ogden Submission Processing Center. An entity in status 01 or any status other than shown in (25), is considered EO and should be transhipped to Ogden Entity.

  27. When entering a non source document transaction into IDRS, the Remarks field of CC BNCHG/INCHG will contain a description of the type of case being processed. For example, if changing a name from a notice, enter the notice number in the Remarks field.

3.13.2.1.5  (01-01-2013)
Associating Documents to an E-Filed Return

  1. If a document needs to be associated with an e-filed return, a refile DLN needs to be created so documents can be attached to the electronically filed return's DLN. Attach IDRS document input tag (Form 12773 BMF ADJ54 Adjustment Format) to each E-file/MeF reply and complete with:

    • Employee IDRS number,

    • Input Date,

    • TC 290,

    • Amount ".00" ,

    • TIN,

    • Tax Period,

    • Block see (3) below,

    • Remarks "Attachment only" and,

    • Sequence Number. Sequence numbers for input should begin with "1" through "999" and remain in order.

  2. Input TC 290 on IDRS to generate a refile DLN to the Files area which is used to attach the reply.

    1. Access CC TXMOD'A', overlay with CC REQ54, X-mit. This will bring up the CC ADJ54 screen

    2. Input the sequence number from the IDRS input tag

    3. BLK> See (3) below

    4. IRS-RCVD-DT> *

    5. TC 290

    6. AMT> .00

    7. Hold-CD> 3

    8. SOURCE-DOCUMENT-ATTACHED?> SD-

    9. REMARKS> Attachment only

  3. Use the following blocking series:

    If MFT is Then Blocking Series is
    02 15
    05 17
    06 17
    10 15
    44 15
    67 10

  4. Complete routing form (for example, OSPC Form 261-A) and send to Files within 5 days of input.
    Reminder : Form 6502 must have the IDRS input date and entire employee IDRS number.

  5. See IRM 2.4.16.

3.13.2.1.6  (01-01-2013)
Processing Time Frames and Batching Requirements

  1. Incoming mail and cases are either delivered to the Entity Clerical Support area or picked up by an Entity designee from the appropriate area(s) on a daily basis.

  2. If Entity receives taxpayer replies for other functional areas, verify the IDRS number located in the "In reply refer to:" area of any IRS generated letter. If the IDRS number does not belong to an Entity employee, do not batch it. Route it to the appropriate functional area without delay.

  3. The time frames for processing BMF Entity inventory start from the IRS received date unless otherwise specified. See IRM 3.30.123.

  4. If it is discovered that documents were batched under an incorrect category, the batch may be re-batched to the correct category, but only during the week the batch was created.

  5. In some circumstances, cases need to be routed to a more experienced Tax Examiner for resolution. Batching clerks will adjust the volume of the original batch and immediately re-assign the remaining documents.

  6. In order to meet the program completion date, all BMF returns must be processed according to the required time frames.

  7. The time frame for all returns and documents that are received via transshipment, must be given an additional 5 processing days, however this additional time cannot be granted if the BMF return is in jeopardy of exceeding the program completion date.

  8. The time frame for processing Form 4442, Inquiry Referral, is 20 days. If the Form 4442 is for a government contractor, this case must be processed immediately. Do not wait 20 days. The Form 4442 for government contractors can be identified by the following: "Expedite Government Contractor " .

  9. If it is determined that an item meets the criteria of several categories, it will be sorted according to the most technical category that applies. An example is BMF correspondence other than an address change. If the correspondence clearly gives information concerning a Form 2553 problem, categorize this item for a twenty day time frame.

  10. Batch sizes are based on a theory of volume. The largest volumes received by Submission Processing Entity are Forms 2553. All entity cases are to be processed within a time frame based on IRS received date; all inventory must be batched by the end of each day (or whatever time the Campus designates as end of day). Therefore, batching documents late in the day (most likely) will not meet maximum batch size. Other circumstances may dictate that batch sizes be smaller than prescribed.

  11. It is important to be able to readily identify types of documents and the processing time frame without having to look at each individual batch. One way of achieving this is to use colored folders for the batches of documents.

  12. There are certain types of cases that are generally not delivered to Submission Processing Entity through mail. They are hand carried to the manager or a designee. It is the responsibility of the manager or designee to batch these cases with the appropriate processing time frames.

  13. BMF Entity TEs will process all IMF address changes/Forms 8822 received. However, any other IMF program should be transhipped. Ogden should fax to Fresno at 559-456-5080 and Cincinnati should fax to Kansas City at 816-292-6181.

3.13.2.1.7  (01-01-2013)
Entity Instructions for Routing Documents/Returns to Files

  1. To ensure Files Department operates as efficiently as possible, there are certain actions every Files customer should take and Entity Control Team will:

    • Send employee source document folders in date and IDRS number order. These will be sent on a batch cart, not in a box. Also, Entity TEs will release the source documents face up and in numerical order beginning with sequence number 001.

    • Do not place (or replace) rubber bands around the returns or the folders holding the returns in pipeline.

    • Detach Forms 4251 from all documents to be refiled.

    • Clearly label all documents going to Files. For example, "EMPLOYEE FOLDERS IDRS TEAMS 04232-04236 FOR 2-9-12 AND 2-10-12" or "ENTITY UNPOSTABLES REFILES" .

  2. Form 9856, Form 10023-B, or an IDRS print with pertinent data highlighted (EIN, name control, date of input/tax period, the DLN receiving the attachment) may be used to associate documents with returns/forms already stored in Files. If an IDRS print is used, type the word "Attachment" on the IDRS screen before printing. After printing, highlight the word "Attachment" in addition to other pertinent data.

  3. If any documents are received in Files and considered "unservicable" , it will be returned to originator for correction. See IRM 3.5.61.

3.13.2.1.8  (01-01-2013)
Customer Account Data Engine (CADE) 2

  1. The Customer Account Data Engine (CADE) Version 2 Program Office in Headquarters is charged with the primary goal to implement a single, modernized programming solution to IDRS which provides daily process of taxpayer accounts. The CADE Master File as it existed from 2004 - 2011 was retired in cycle 201152.

  2. The CADE 2 solution is comprised of several components to modernize the IRS to a daily processing environment with several Transition States.

  3. With CADE 2 there will be changes to campus posting cycles which will begin with cycle 201201. The new BMF campus cycles are:

    • Campus Cycle: Thursday - Wednesday

    • Master File Processing: Friday - Thursday

    • Notice Review: Saturday - Monday (8+ days)

    • Unpostables: New UPCs available Tuesday; closing Tuesday

  4. BMF transaction posting time frames are outlined as follows:

    • Transactions will be viewable using CFOL command codes on Saturday following the weekly Master Files processing run on Thursday.

    • Transactions will be viewable as posted transactions using IDRS command codes on Monday, following the weekly Master File processing run on Thursday.

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

  5. Cycle posting dates will reflect a format of YYYYCCDD.

    • YYYY will indicate the year,

    • CC will indicate the posting cycle


    For IMF transactions, the values for DD are as follows:

    • 01 - Friday

    • 02 - Monday

    • 03 - Tuesday

    • 04 - Wednesday

    • 05 - Thursday


    BMF posting cycles on CC BMFOL will continue to reflect YYYYCC.

    • YYYY will indicate the year,

    • CC will indicate the posting cycle


    BMF posting cycles in CC TXMOD will reflect a format of YYYYYCCDD. The value for DD will be 08.

3.13.2.2  (01-01-2013)
Entity Types-Name Controls and Filing Requirement Codes (FRCs)

  1. This subsection contains information and procedures for establishing many of the different types of entities. The standards for completion of Entity fields will be outlined.

  2. The most commonly filed returns of each entity type will be listed.

  3. IDRS requires:

    • Primary name/continuation of primary name field cannot be longer than 70 characters (35 characters each line). A word cannot be split between lines.

    • The special characters hyphen (-) and ampersand (&) can be in the primary and sort name fields. If the taxpayer uses any other special character, omit the character and leave a blank space. For example, "Taxpayer.com" will be entered as "Taxpayer com" .
      EXCEPTION: If the taxpayer includes an apostrophe in their name, omit the apostrophe, but do not leave a blank space.
      For example, JANE'S STORE becomes JANES STORE

  4. When a sort name is input, the BMF will identify the sort name which allows it to be used on the Name Search Facility (NSF). The NSF is accessed with CCs NAMES and NAMEE to locate and identify the taxpayer.

  5. If the sort name is an individual name, complete the sort name line field with the taxpayer's name as indicated by the taxpayer followed by their title. Prior to 11-30-08, Entity entered the Sort Name with the taxpayer's last name first, followed by their first name, middle initial and title. This was referred to as the "sort line format" .

  6. To delete a sort name, input the symbols "$$" on the Sort Name field.

3.13.2.2.1  (01-01-2013)
Corporations-Name Controls and FRCs

  1. Corporations are registered with the Secretary of State's office in the state of incorporation. The internet web sites of these offices will be used to verify corporation information such as:

    • date of incorporation,

    • name changes,

    • type of entity/annual filing requirement,

    • any changes in structure/owners,

    • status with state,

  2. Suffixes such as P.A. (Professional Association), P.C. (Professional Corporation), and INC. (Incorporated), indicate a Corporate entity.

  3. Omit the word "The" when followed by more than one word.

    • Name: The Meadowlark Company

    • Name Control: Meadowlark Company

  4. Include "The" in the name control when it is followed by only one word.

    • Name: The Flamingo

    • Name Control: TheFlamingo

  5. Do not abbreviate or change "and" to "&" unless the taxpayer requests it. The Corporation receives its' charter from the state exactly as shown by the taxpayer and this is the way the account will be established.

  6. Corporations have their business/trade name/Doing Business As (DBA), if different from true name, in the sort name field. CC ESIGN will not allow a primary name line and sort name line to be identical.

  7. The name control for a corporation is the first four significant characters of the corporation's name.

  8. Corporate name control rules apply if an individual name contains the abbreviations PC (Professional Corporation), SC (Small Corporation), PA (Professional Association), PS (Professional Service), or PSC (Personal Service Corporation).

    • Name: George Giraffe PSC

    • Name Control: George Giraffe PSC

  9. When the organization name contains the words "Fund" or "Foundation" , corporate name control rules apply. See IRM 3.13.12.
    For example, Kathryn Canary Memorial Foundation.

  10. When an individual name and a corporate name appear, the name control is the first four letters of the corporation name. This is most often seen on employment returns, Form 94X family.
    Barbara J. Zinnia
    ZZ Grain, Inc. Input name control as ZZGR

  11. The information for inputting corporation names is derived from the following:

    1. The filing of a return without an EIN (Form 1120, Form 940, Form 941, Form 943, Form 944, Form 945, Form 720, Form 730, Form 11-C, Form 2553, certain Forms 990 or Form 2290).

    2. The changing of a name on a return.

    3. Requesting a name change through correspondence.

    4. Perfecting the entity.

  12. Non Profit corporations are also registered with the Secretary of State's office in the state of incorporation. An organization is not considered non profit until they have received a formal exemption letter.

  13. Specific information for identification will be input as a sort name or continuation of the primary name. This information would be Local #, Area #, Unit #, School name, Governmental division, etc.

  14. For non profit organizations use the following rules for determining name control:

    1. The only organization which you will always abbreviate is Parent Teachers Association (PTA). The name control will be "PTA" plus the first letter of the name of the state.
      Name: Parent Teachers Asst. Congress of Georgia
      Name Control: PTAG

    2. The name control for a local or post number is the first four characters of the national title.
      Local 210, International—Input as INTE
      Post 3120, Veterans of Space Wars—Input as VETE

    3. Use the name control of the national organization name if there is a Group Exemption Number (GEN).

    4. For churches and their subordinate (for example nursing homes, hospitals), the name control will be derived from the legal name of the church, etc.
      Name: Locust Church
      Name Control: Locust Church

  15. Corporations will file Form 1120 family returns. See IRM 3.13.2.7.5.

  16. Corporations may also file Employment tax returns (Form 94X family) and Excise returns (Forms 720, 730, CT-1, 2290, etc.).

  17. See chart in IRM 3.13.2.13.1(5).

3.13.2.2.2  (01-01-2013)
Partnerships-Name Controls and FRCs

  1. A partnership is a group of taxpayers who have entered into a written business agreement and file Form 1065, U. S. Partnership Return of Income. This is an annual return.

  2. Partnerships may also file Employment tax returns (Form 94X family) and Excise returns (720, 730, 11-C, 2290, etc.).

  3. See chart in IRM 3.13.2.13.1(5).

  4. Partnership FYMs are governed by The Tax Reform Act of 1986. Partnerships are required to use the same tax year ending as their owner, usually December 31.

  5. There are other entities that are considered partnerships and are liable to file Form 1065.

    • An unincorporated business jointly owned by a married couple

    • qualified joint venture (however, Public Law 110-28) provides that a "qualified joint venture" , whose only members are a husband and a wife filing a joint return, can elect not to be treated as a partnership for Federal tax purposes.

  6. Partnership Name—The partnership primary name line will be the legal name of the partnership (for example, the list of partners or the business/trade name).

    • If a partnership name has not been provided, use the partner's name(s) followed with the abbreviation "PTR" .

    • If it is not possible to list all the partners as the primary name (up to 70 characters), list the maximum number of names and add the phrase "ET AL PTR" . If there is only one partners' name, add the phrase "ET AL PTR."

      Note:

      If the account indicates a Limited Liability Company (LLC), follow the primary name line with "LLC" .

    • If the primary name line and the care of name line are identical, input of the care of name line is not required.

  7. General Partner's name and title or partnership's trade name will be in the Sort Name field. Generally, partnerships will always have an entry in the sort name line field. See the table below for guidance in formatting a partnership's name lines.

    If... Then...
    The partnership has a true name and a trade name Enter the true name in the primary name line, trade name in the sort name line field and the general partner's name in the "Care of Name" field.
    The partnership has a trade name but does not supply their true name Enter the trade name in the sort name line field and the partner's name with "ET AL PTR" in the primary name line
    A business is the general partner Enter the partner's name followed by GEN PTR in the "Care of Name" name field
    The partnership does not have a trade name Enter the true name of the partnership in the primary name line and the general partners's name in the sort name line field

  8. The name control for a partnership will be derived in the following order of selection:

    1. The first four characters of the first partner's last name.
      Burgandy, Olive & Cobalt, Ptrs.

    2. The first four characters of the business (dba) or trade name.
      Rosies Restaurant

  9. Delete the word "The" from trade name and business name. If "The" is followed by only one word, then do not delete "The" .

  10. Partnership EINs that begin with prefixes 20, 26, 27, 45, 46 or 47 will have the first four characters of the Primary Name as the name control. For example, the partnership name "John Willow and James Oak Partnership" will be name controlled John .

  11. The information for inputting partnership names is derived from the following sources:

    1. The filing of a return without an EIN (Form 940, Form 941, Form 943, Form 944, Form 945, Form 720, Form 730, Form 11-C, or Form 2290)

    2. Perfecting the name on a return

    3. The filing of return (Form 1065) without an EIN

  12. Input the partnership name from these returns filed without an EIN (Form 941, Form 943, Form 944, Form 945, Form 720, Form 730, Form 11-C, or Form 2290) in the following priority:

    • DBA or trade name

    • Legal name

  13. Input the partnership name from a Form 1065 filed without an EIN in the following priority:

    • DBA or trade name (if the legal partners names are not on the name line)

    • Legal partner(s) names

  14. These common Spanish words may appear in business names.

    • Senor (Mr.)

    • Senora (Mrs.)

    • Hijos (Sons)

    • Hermanos (Brothers)

    • S. A. (INC)

3.13.2.2.3  (01-01-2013)
Limited Liability Companies (LLCs) - Name Controls and FRCs

  1. Limited Liability Companies (LLCs) are defined as an unincorporated business entity created under state law and owned by one or more persons known as members. State law generally allows for a “person” to be:

    • An individual,

    • a trust,

    • an estate

    • a partnership

    • an association

    • a company

    • a corporation

    • an LLC

  2. Suffixes such as LLC, LC, and PLLC indicate a limited liability company and are input with the LLC’s name.

  3. There are two types of LLCs: Single member and Multi-member

  4. Treasury Regulations 301.7702 (as amended by T.D. 9356, 2207–39 I.R.B.) eliminated disregarded entity status for the purposes of federal employment taxes and certain excise taxes. The LLC will continue to be a disregarded/ single member entity for federal income tax purpose, but is no longer disregarded for certain excise and employment taxes. The amended regulations provide that the LLC will have a tax status distinct from its owner.

    • For employment taxes on wages paid on or after January 1, 2009; and

    • For excise taxes imposed and actions first required or permitted in periods beginning on or after January 1, 2008


    therefore, single member LLCs will have their own EIN for filing purposes, however, a single member LLC does not have an annual filing requirement. The income/loss is reported on the annual return of the owner(s).

  5. Multi member LLCs default to the classification of a partnership.

  6. Either type of LLC can file Form 8832 to elect their Entity classification. See IRM 3.13.2.25 and IRM 3.13.2.26.

  7. LLCs may also file Employment returns (Form 94X family) and Excise returns (Forms 720, 730, 11-C, 2290, etc.).

  8. The Primary Name Line will be the legal name of the LLC.

  9. Delete the word "The" from the LLC or partnership name, trade name and business name. If "The" is followed by only one word, then do not delete "The" .

  10. Do not abbreviate or change "and" to "&" unless the taxpayer requests it. The LLC receives its' charter from the state exactly as shown by the taxpayer and this is the way the account will be established.

  11. The LLC's trade name or Doing Business As (DBA) name will be entered in the Sort Name Line field. If there is not a DBA, a member's name and their designation will be entered in the sort line.

3.13.2.2.4  (01-01-2013)
Trusts-Name Controls and FRCs

  1. Trust Names can be long and complicated. A trust name can be reduced or abbreviated to allow for the trust name to be entered on the first name line.

  2. Trusts will be name controlled by the first surname in the Primary Name. The trustee's name will be placed on the Sort Name line if an individual. If the trustee is a financial institution or business, input on the Care of Name line.

  3. Trust EINs that begin with prefixes 20, 26, 27, 45, 46, and 47 will have the first four characters of the Primary Name as the name control.
    For example, the trust name "John Willow TR fbo James Oak" will be name controlled John .

  4. The name control of a trust with a prefix other than 20, 26, 27, 45, 46, or 47 will be derived by the following selection:

    1. The first four characters of an individual's last name.
      Name: Michael T. Azalea Revocable Trust
      Name Control: Michael T]Azalea]Rvoc Tr

    2. For corporate taxpayers, use the first four characters of the corporate name.
      Name: Sunflower Company Employee Benefit Trust
      Name Control: Sunflower Company Employee Benefit Tr

  5. For GNMA Pools use the first four digits of the trust number, disregarding any leading zeroes and/or trailing alphas. If there are fewer than four numbers, use the letters "GNMA" to complete the name control. Disregard any other alphas following the pool numbers.

    • Name: 0001 GNMA Pool

    • Name Control: 1GNM

    • Name: GNMA Pool 0002

    • Name Control: 2GNM

    • Name: GNMA Pool 00100

    • Name Control: 100G

  6. If none of the above information is present, use the first four characters of the last name of the trustee (TTEE) or beneficiary (FBO).

  7. If needed, contact the taxpayer via telephone for above information. If contact cannot be made, correspond via Letter 45C.

  8. The information for inputting trust names are derived from.

    1. The filing of a return (Form 940, Form 941, Form 944, Form 945, Form 1041, Form 5227, Form 1041-A, and some Form 990, Form 990-PF or Form 990-T returns).

    2. Requesting a change through correspondence.

    3. Perfecting fiduciary from a Form 1041.

    4. Perfecting the entity,

    5. Form 56.

  9. Always abbreviate the primary name to 70 characters (two name lines). In addition, always abbreviate the following words or phrases. All dates in the trust name line will be entered as MMDDYYYY:

    NAME/or PHRASE ABBREVIATION
    Trust TR
    Under the will of, U/W, under will UW
    Under agreement, U/A, Under agreement with UA
    Dated Jan. 16, 2007 01162007 (do not enter date/dated or the alpha month).
    Irrevocable Trust IRRV TR
    Revocable Trust RVOC TR
    Trustee TTEE
    For the Benefit of, F/B/O, F B O FBO
    Gift Trust, Giftrust GIFT TR
    Family Trust FAM TR
    Marital Trust MRTL TR
    Funeral Trust FNER TR
    Inter-Vivos INTRVS
    Non-exempt Charitable Trust NECT
    Revocable RVOC
    Testamentary TEST
    Under Trust Agreement UTA
    Voluntary Employee Benefit Association VEBA
    Insurance INS
    Charitable Remainder Unitrust CRUT
    Charitable Remainder Annuity Trust CRAT

  10. Always make the individual trustee, personal representative, etc. a sort name.

    1. Do not sort a bank, mortgage company or corporation. Make this type of trustee will be on the "Care of Name" line.

    2. If it is not possible to list all the trustees as the sort name, list the maximum number of names and add the phrase "ET AL TTEE" .

  11. The following are examples of inputting trust names:

    Taxpayer shows Input
    Sophie Spathe Snipe irrevocable trust FBO Emil Spathe Snipe under agreement dated Oct. 13, 2007 Viceroy Bank Trustee Primary Name
     SOPHIE SPATHE SNIPE IRRV TR FBO Continuation of Primary Name
     EMIL SPATHE SNIPE UA 10132007
    Care of Name
    % VICEROY BANK TTEE
    Irrevocable Trust F/B/O William Michael Nancy Raccoon Mission National Bank Trustee under agreement with Howard Raccoon dated Jan. 15, 2007 Primary Name
     HOWARD RACCOON IRRV TR FBO WILLIAM Continuation of Primary Name
     ]MICHAEL NANCY RACCOON
     UA 01152007
     Care of Name
    % MISSION NATIONAL BANK TTEE
    Camel Trust & Savings Co TTEE for Harvey Hare Trust for the benefit of Molly Hare U/A dated Nov. 18, 2007 Primary Name
     HARVEY HARE TR FBO MOLLY HARE
    Continuation of Primary Name
     UA 11182007
    Care of Name
    % CAMEL TRUST SAVINGS CO TTEE
    Turtle Memorial Cemetery Perpetual Trust Fund William C Bear Trustee Primary Name
     TURTLE MEMORIAL CEMETERY TR
    Continuation of Primary Name
     PERPETUAL FUND
    Sort Name
     WILLIAM C BEAR TTEE

  12. Trust FYMs are governed by The Tax Reform Act of 1986 and are required to use the same tax year ending as their owner, usually December 31.

  13. Trusts will file Form 1041, Form 1041-QFT, Form 945, Form 5227, Form 1041-A, or some Forms 990, 990-PF or 990-T). See IRM 3.13.12.

  14. If a trust has employees, the FRC on IDRS will be 1041-2.

3.13.2.2.5  (01-01-2013)
Estates-Name Controls and FRCs

  1. The estate name (the name of the deceased person) must be included in the primary name line.

    1. The word "Estate" will be added to the primary name, if it can be identified as an estate.

    2. The name will be rearranged to show "Estate" after the individual's name.

  2. The name control for estates is the first four characters of the last name of the decedent.

  3. The last name of the decedent must be followed by the word "Estate" in the primary name line.

    • Name: Howard J. Smith Dec'd

    • Name Control: Howard J]Smith]Estate

  4. Always abbreviate the primary name to 70 characters (two name lines). Always abbreviate the following words or phrases:

    • Personal Representative to PER REP

    • Fiduciary to FID

    • Executor/Executrix to EX

    • Administrator to ADM

    • Successor to SUCC

  5. Estates are not required to use a particular tax year ending.

  6. Estates will file Form 1041.

  7. If an estate has employees, IDRS will show the FRC of 1041-2.

3.13.2.2.6  (01-01-2013)
Sole Proprietors and Individual Taxpayers-Name Controls and FRCs

  1. A Sole Proprietor is an individual that operates a business and reports the income/loss from that business on Form 1040, Schedule C.

  2. Sole Proprietors can file employment returns (Form 94X family) and/or excise returns (Forms 2290, 720, etc.), Sole proprietors do not file annual returns (Forms 1120, 1065, 1041, 990 series, etc.).

  3. Individual EIN and Social Security Numbers (SSN) Accounts—The primary name line will not contain numeric characters or the special character ampersand (&). Although a numeric character or ampersand (&) is a valid input for IDRS, an individual's name cannot contain a numeric character or ampersand.

    Example:

    A business name can be Jones & Smith. An individual's name cannot be Jones & Smith.

    1. To use CC BNCHG on Form 709 accounts, Master File Tax Code (MFT 51) must be present in the MFT> field and the year digit must be present YYYY format in the NM-YR/QTR> field of CC BNCHG.

    2. For Form 706 accounts (MFT 52), MFT> field must be present along with the DT-OF-DEATH> field in MMDDYYYY format.

    3. For Form 706 and Form 709, the Taxpayer Identification Number (TIN) must be an SSN and the Primary name line can only be for an individual.

    4. An SSN (IMF) account only has a Primary name (35 characters) - never use the Continuation of Primary name.

    5. Form 706GS(T) TIN may be either EIN or SSN. Name lines will be treated as trust name line inputs.

    6. Form 706GS(D) TIN may only be SSN. Name lines will be treated as trust name lines.

  4. If a sole proprietor requests a name change, compare the name on taxpayer's SSN with name on EIN. If SSN has already been updated, input TC 013 to update EIN. If SSN has not been updated, ask the taxpayer for documentation of the legal name change. This documentation can be a marriage certificate, court order, etc.

  5. The sort name will be used for the following:

    1. Sole Proprietors will have their business/trade name the Sort Name field.

    2. "Account under TEFRA" if it is a Pension Trust. "TEFRA" is an acronym for Tax Equity and Fairness Recovery Act

  6. The Sort Name will be changed if there is a direct demand or request from the taxpayer or clear indication the taxpayer's trade name (or Doing Business As-DBA) has changed.

  7. To delete the sort name, input "$$" in the first two positions of the sort name line.

  8. The Sort Name will be changed if there is a direct demand or request from the taxpayer or clear indication the taxpayer's trade name (or Doing Business As-DBA) has changed. Do not update the Sort Name line if the taxpayer's trade name is identical to the Primary Name line. The Sort Name line is used for research purposes and must be input accurately.

  9. The name control consists of four alpha and/or numeric characters.

  10. The ampersand (&) and hyphen (-) are the only special characters allowed in the name control. However, these characters cannot be in the first position of the name control.

  11. The name control can have less, but no more than four characters. Blanks may be present only as the last three positions of the name control.

  12. The name control for a sole proprietor's name is the first four significant characters of the last name.

  13. When the taxpayer has a true name and a trade name, the name control is derived from the first four characters of the individual's last name.

    • True Name: Arthur P. Aspen

    • Trade Name: Sunshine Restaurant

    • Name Control: Arthur P]Aspen

  14. When two last names are used, the name control is the first four letters of the second last name.

    • Maiden Name: Daisy Oak

    • Married Name: Daisy Oak Tree

    • Name Control: Daisy Oak]Tree

  15. When two last names connected by a hyphen are shown for one individual, the name control is the first four letters of the first last name.

    • Name: Jane Smith-Jones

    • Name Control: Jane]Smith-Jones

  16. On joint returns with different last names, the name control is the first four letters of the last name of the individual appearing first.

  17. For Spanish names, when two last names are shown for an individual, the name control is the first four letters of the first last name.

    • Name: Juan Garza Morales

    • Name Control: Juan]Garza]Morales

    • Name: Maria Lopez Moreno

    • Name Control: Maria]Lopez]Moreno

  18. For last names that have only two letters:

    • Name: Sunny Ming Lo

    • Name Control: Sunny Ming]Lo(blank)(blank)

  19. Vietnamese names will often have a middle name of Van (male) or Thi (female).

    • Name: Kim Van Nguyen

    • Name Control: Kim Van]Nguyen

  20. If the individual is newly arrived in the U.S., the last name may appear first on the name line. On the signature line, the last name will usually appear first.

  21. PREFIX on Sole Proprietor Individual.

    1. Delete prefixes from true names or surnames. Examples of prefixes to be deleted are Mr., Rev., Dr., Capt., Hon., Gov., Miss, Mrs. (DO NOT DELETE "MRS." WHEN SHOWN WITH THE FULL NAME OF THE HUSBAND (for example, Mrs. Richard Green) or a name of indeterminate gender (for example, Mrs. Chris Blue).

    2. Delete prefixes from the Sort Name. Examples of prefixes to be deleted are DBA, TA, AKA, etc.

  22. SUFFIX on Sole Proprietor Individual.

    1. Delete all suffixes from the Primary Name, such as Owner, Agent, Attorney, Proprietor, etc.

    2. Do not delete suffixes such as DDS, MD, PHD, Jr., Sr., III, etc.

  23. The information for inputting individual names is derived from the following:

    1. The filing of a return (Form 940, Form 941, Form 943, Form 944, Form 945, Form 720, Form 11-C, Form 730, or Form 2290).

    2. The changing of the name on a return.

    3. Requesting a change of name through correspondence.

    4. Perfecting an entity.

  24. When establishing the account or changing the name lines for an individual use the examples below to determine the input.

    1. The primary name line will consist of a true name.

    2. The sort name line will consist of a trade name or DBA (doing business as) name. Primary Name James P. Rain, Sort Name Sunshine Restaurant

    3. An individual name can only consist of one name. Although, a numeric character or ampersand (&) is a valid input for the primary name line, an individual's name in that field cannot contain a numeric character or ampersand.

      Example:

      A business name can be 357. An individual's name cannot be 357.

    4. Household Employers use the given name of the taxpayer, if available on the source document. First Name Line shows "Mrs. Albert Almond" and the signature shows "Gloria Almond" , place "Gloria Almond" in the Primary Name Line on the BMF.

  25. Names of Spanish Extraction—Many names will include two surnames. In these cases the mother's surname (matronymic) will be the last name and must be a part of the input.

    1. The "Y" (Spanish for "and" ) if present, between two names precedes the Matronymic (mother's surname).

    2. Delete the following Spanish titles ESP, ESP DE, ESPOSA DE (wife of VDA), VDA, DE VIUD (widow of), Senor (Mr.), Senora (Mrs.), Hijos (sons), Hermanos (brothers), and in some cases DE (of).

    3. The Spanish phrase "DEL" or "DE LA" preceding a name is part of the name.

    4. These common Spanish words may appear in business names. Senor (Mr.) Senora (Mrs.), Hijos (Sons), and Hermanos (Brothers).

  26. The Spanish phrases "de" , "De" "del" and "de la" are considered part of the name control.

    • Name: Elena de la Rosa

    • Name Control: Elena]dela]Rosa

3.13.2.2.7  (01-01-2013)
"Care of Name"

  1. An in "Care of Name" is used to direct mail to a specific person within an organization that is not the taxpayer's primary address. The abbreviation "c/o" is often used to represent "Care of Name" ' However, for IDRS purposes the percent sign "%" is used.

  2. If the "Care of Name" is input, a "%" must be in the first position and a blank space in the second position of the "Care of Name" field.

  3. Since banks are never sorted, most of the time a fiduciary is used, the fiduciary will appear in the "Care of Name" field.

  4. To delete a "Care of Name" , input "$$" in the first two positions of the "Care of Name" field.

  5. If the "Care of Name" field is present on IDRS, and not on the requested address change, it will be deleted unless the taxpayer has clearly stated the CareOf Name is the same. EXCEPTION: Do not alter the "Care of Name" if the entity is a Partnership or LLC and the "Care of Name" field contains the name of a partner or member.

3.13.2.3  (01-01-2013)
BMF Addresses

  1. BMF addresses are added to Master File upon assignment of the taxpayer's EIN. Master File maintains two address fields for BMF taxpayers: mailing address and location address.

  2. IMF taxpayers have only a mailing address field.

  3. Entity TEs are responsible for inputting correct address information with the use of CC ESIGN and CC BNCHG.

  4. Entity should not change the address of a taxpayer bearing a Large Corporation Indicator (LCI). See IDRS Command Code Job Aids for CCs ENMOD, BMFOL'E' and SUMRY for assistance in identifying an LCI. The change of address request (or Form 8822, Form 8822-B, etc.) should be routed to the Large Corporation/Technical Team in the respective sites with the message "LCI Address Change" entered on the routing slip.

    Note:

    The IAT tool for Address Changes identifies the LCI in the "Account Conditions" field. If IAT is unavailable, the address change request should be researched on IDRS manually to identify an LCI.

  5. All transactions containing an address change will have the requester's name, title, and phone number if present in the Remarks field of the transaction.

  6. According to postal regulations, mail will be delivered to the last address immediately preceding the city, state and ZIP code. A Post Office (PO) Box will always be the mailing address if present. For trusts and estates only, if the taxpayer indicates the street address is the mailing address and the PO Box is the location address, leave the PO Box as the location address.

  7. When inputting either the mailing or location street address information, follow these guidelines:

    • Do not leave a blank space between the house or building number and a suffix,
      Taxpayer submits 1234 B North Street. Input as 1234B NORTH ST,

    • If present, always input the street suffix such as street, drive, lane, terrace, etc. See chart in (15) below,

    • If present, always include the street directional such as North, South, East, West,

    • Always input the suite, apartment number, room number, etc. at the end of the street address line,

    • If the address contains a fraction, utilize the forward slash (/) between the numeric fields. For example, 1/2.

    • If the address contains a hyphen (-) such as 289–01 MAIN ST, enter the hyphen as part of the address. Do not remove the hyphen. Do not leave any additional spaces around the hyphen,

    • If the address contains the symbol "&" (ampersand), always input the word "and" in its place,

    • If the address contains a decimal point such as 1.5 MILES SOUTH OF HWY 19, convert the decimal point to a fraction. Input as 1 1/2 MILES SOUTH OF HWY 19,

    • If the address contains a pound sign such as 1532 MAIN ST #15. Input as 1532 MAIN ST 15. If the street address contains an abbreviation for "number" , omit from entry into address line on IDRS,

    • A city or town name (that is long) will only be abbreviated for lack of space in the IDRS field,

    • The Private Mail Box (PMB) must be entered at the end of the address regardless of where it is shown in the incoming address. It will always be included with the street address,
      Example: Private Mailbox 3, 102 S. 38 will be entered as 102 S. 38 PMB 3. When entering data from a document which has a Private Mailbox (PMB) number, to ensure consistency, input the PMB on the street address line according to the example above. If it is located in another area other than the street address line make the correction to move it to the correct line. (for example, PMB on the street address line).

  8. If city or state is missing or incomplete and the ZIP code is present, research the United States Postal Service (USPS) web site at http://www.usps.com to determine the city and state.

  9. Only the primary five digits of the ZIP code should be entered. IDRS and the FINALIST program automatically expand the ZIP code to 12 digits.

  10. Mail going to a domestic taxpayer will carry two name lines. The priority of these name lines is as follows.

    1. Always the primary name (legal name).

    2. Always sort name if present on the BMF or Care of Name or Foreign street address or continuation of primary name if no foreign street is present.

  11. To ensure outgoing mail contains pertinent information, primary name, care of name, sort name and address must be properly input.

  12. If the city listed is a major city, the Major City Code may be input in place of the city and state information on the mailing address and location address. Major City Codes are now universal and can be used in any processing site. If the Major City Code is used, it must be followed by a ZIP code. (Input requires that the Major City Codes be followed by two commas and then the ZIP code.) See Document 7475 .

  13. If there is any question regarding the correct mailing and/or location address (directionals, building number range, ZIP code, spelling, etc.) access the USPS web site at http://www.usps.com. Adhere to the IRS address abbreviation rules.

  14. A taxpayer's mailing address will not be updated unless clear indication of a change from the taxpayer or his representative is received. The exception would be when resolving undeliverables.

    • When processing forms/documents that have an "address change box" , Master File will be updated only if the "address change box" has been marked by the taxpayer.

    • Master File will not be updated with the address from a form that does not have an "address change box" unless the taxpayer has given clear instructions to update his address.

    .

  15. The words "East, West, North, South" will only be abbreviated when used as a directional for a street name. For example:
    Taxpayer enters: 1105 North Main Street,
    Entry onto IDRS: 1105 N MAIN ST

  16. Plurals for street, road, avenue, etc., will be entered as STS, RDS, AVES, etc. Street address for First, Second, Third, 1st, 2nd, or 3rd will be entered onto IDRS as the taxpayer entered.

  17. Always use the street address abbreviations shown below with CCs ESIGN and BNCHG. It is not necessary for Entity to correct incorrect abbreviations existing on an EIN unless accessing EIN for other Entity changes.

    Word Abbreviation Word Abbreviation
    Air Force Base AFB Northeast NE
    Apartment APT Northwest NW
    Avenue AVE one half, one fourth - all fractions 1/2, 1/4
    Boulevard BLVD Parkway PKY/PKWY
    Building BLDG Place PL
    Care of % Post Office Box PO BOX
    In care of % Road RD
    Circle CIR Room RM
    Court CT Rural Route RR
    Department DEPT Route RT
    Drive DR Rural Delivery RD
    East E South S
    Floor FL Southeast SE
    General Delivery GEN DEL Southwest SW
    Highway HWY Street ST
    Highway Contract HC Suite STE
    Lane LN Terrace TER
    North N West W

  18. The following abbreviations will only be used if needed to limit street address fields to 35 characters:

    Word Abbreviation Word Abbreviation
    Alley ALY Inlet INLT
    Annex ANX Island IS
    Arcade ARC Islands ISS
    Bayou BYU Isle ISLE
    Beach BCH Junction JCT
    Bend BND Key KY
    Bluff BLF Knolls KNLS
    Bottom BTM Lake LK
    Branch BR Lakes LKS
    Bridge BRG Landing LNDG
    Brook BRK Light LGT
    Burg BG Loaf LF
    Bypass BYP Locks LCKS
    Camp CP Lodge LDG
    Canyon CYN Manor MNR
    Cape CPE Meadows MDWS
    Causeway CSWY Mill ML
    Center CTR Mills MLS
    Cliffs CLFS Mission MSN
    Club CLB Mount MT
    Corner COR Mountain MTN
    Corners CORS Neck NCK
    Course CRSE Orchard ORCH
    Courts CTS Pines PNES
    Cove CV Plain PLN
    Creek CRK Plains PLNS
    Crescent CRES Plaza PLZ
    Crossing XING Point PT
    Dale DL Port PRT
    Dam DM Prairie PR
    Divide DV Radial RADL
    Estates EST Ranch RNCH
    Expressway EXPY Rapids RPDS
    Extension EXT Rest RST
    Ferry FRY Ridge RDG
    Field FLD River RIV
    Fields FLDS Shoal SHL
    Flats FLT Shoals SHLS
    Ford FRD Shore SHR
    Forest FRST Stream STRM
    Forge FRG Summit SMT
    Fork FRK Trace TRCE
    Forks FRKS Track TRAK
    Fort FT Trail TRL
    Freeway FWY Trailer TRLR
    Gardens GDNS Tunnel TUNL
    Gateway GTWY Turnpike TPKE
    Glen GLN Union UN
    Green GRN Valley VLY
    Grove GRV Viaduct VIA
    Harbor HBR View VW
    Haven HVN Village VLG
    Heights HTS Ville VL
    Hill HL Vista VIS
    Hills HLS Wells WLS
    Hollow HOLW    

3.13.2.3.1  (01-01-2013)
ESIGNing a BMF Address

  1. The first address shown on the document/return being processed will be the taxpayer's mailing address.

  2. If a second address is shown, it will become the taxpayer's location address. A trust/estate is the only entity authorized to have a PO Box as a location address. If the second address is a PO Box and the entity is not a trust/estate, make the PO Box the mailing address.

  3. The charts in IRM 3.13.2.3 will be used when inputting an address through CC ESIGN and/or CC BNCHG.

3.13.2.3.2  (01-01-2013)
Updating BMF Addresses

  1. Entity is the primary area responsible for updating taxpayer addresses. Forms 8822-B, Change of Address - Business, are processed in Entity. Taxpayer correspondence requesting address changes will be routed to Entity. If the correspondence involves an adjustment action, collection activity, or a TAS situation other than an Entity issue, the address will be updated by the function responding to the primary issue.

  2. The charts in IRM 3.13.2.3.1 governing address field abbreviations will also be applied to this subsection of IRM.

  3. Never change the address on Master File if the acronym FDIC, (Federal Deposit Insurance Corporation), is present in any of the name lines.

  4. If the "Care of Name" field is present on IDRS, and not on the requested address change, it will be deleted unless the taxpayer has clearly stated the In-Care-Of name is the same. EXCEPTION: Do not alter the "Care of Name" if the entity is a Partnership or LLC and the "Care of Name" field contains the name of a partner or member.

  5. Prior to 2010 it was the practice of Submission Processing to update a taxpayer's mailing address with a campus address upon learning that taxpayer's address caused undeliverable mail.

    • The campus address should only be placed on accounts of victims of identity theft. These accounts will be identified by a TC 971-501 or TC 971-506 on CC ENMOD.

    • If during the course of processing your assignments you discover an EIN with a campus address, the following actions will be taken: Research CCs ENMOD, FINDE, and FINDS for a valid Last Known Address (LKA). If found, send Letter 104C requesting completion of Form 8822/8822-B. If LKA is not found, input TC 593-82 on all open FRCs.

  6. When changing the mailing address from a street address to a Post Office (PO) Box number, retain the street address as a location address unless the taxpayer provides a new location address. The retention of the street address in the location address field is necessary as an audit trail for locating taxpayers. ZIP code - Input only the first five digits.

  7. All transactions containing an address change will have the requester's name, title, and phone number if present in the Remarks field of the transaction. If you are unable to determine the name and/or title, enter "SIGNATURE ILLEGIBLE" and the requester's phone number (if available).

  8. When making an address change from a return, the following information will be entered in the Remarks field of CC BNCHG:

    • MFT of return,

    • Tax Period of Return,

    • Name and title of signature,

    • Telephone number (if available)

3.13.2.3.3  (01-01-2013)
Domestic International Addresses (APO, FPO, MP, PR, GU, AS, FM, VI, MH, PW, AA, AE and AP)

  1. The following state codes must be used to replace the city and state in an international address. Always enter APO and FPO in the address:

    Country State Code ZIP code
    Americas APO AA 34000-34049
    Americas FPO AA 34050-34099
    Europe APO AE 090XX-094XX
    096XX-098XX
    Europe FPO AE 095XX
    Pacific APO AP 962XX–965XX
    97800-97859
    Pacific FPO AP 966XX and
    98760-98799


    The following are examples of CC BNCHG input formats:

    PVT. Daisy Flower Jean Rose, PCC (SW), USN
    Company F, PSC Box 100 USS Oak
    167 Infantry Regt. FPO AP 96667
    APO AE 09801  

  2. The territories and possessions listed below are not entered as international addresses and require a valid state code and ZIP code:

    Country State Code ZIP Code
    Virgin Islands VI 008nn
    Puerto Rico PR 006nn, 007nn, 009nn
    Guam GU 969nn
    American Samoa AS 96799
    Northern Mariana Islands MP 969nn
    Palau PW 969nn

  3. If the name of the foreign country is not present and cannot be determined, research using a geographical dictionary.

  4. All transactions containing an address change will have the requester's name, title, and phone number if present in the Remarks field of the transaction. If you are unable to determine the name and/or title, enter "SIGNATURE ILLEGIBLE" and the requester's phone number (if available).

3.13.2.3.4  (01-01-2013)
Foreign International Mailing and Location Addresses (other than APO, FPO, MP, FM, MH, PW, PR, GU, AS, and VI)

  1. The following fields will be used for international entities:

    • Primary Name

    • Continuation Primary Name

    • Sort Name

    • Care of Name

    • Foreign Street Address

    • Mailing Street or Foreign City/Postal Code

    • Mailing City or Foreign Country/State/ZIP (State Field = (,)(.) ZIP = blank)

    • Location Street Address

    • Location City/State/ZIP

  2. DO NOT abbreviate the country. The country is input in the city field of the mailing city/state/ZIP line.

  3. The state field must always be a comma (,) and period (.).

  4. The ZIP code field must always be a blank.

  5. The foreign street address and mailing street address must be present when the state code is a period:"." .

  6. To delete a foreign street address, "$$" must be input in the first two positions of the foreign street address. The mailing address (city, state and zip) must be present and state and ZIP code fields must not be blank.

  7. To input a foreign address as a location address:

    1. The location ZIP must be a period (.).

    2. The location city field must be at least 3 alpha characters, with no major city codes.

    3. The foreign country must be input in the location state field and must be at least 3 alpha characters followed by a comma (,).

    4. The location street address must be present.

  8. To delete a foreign address as a location address, input "$$" in the first two positions of the location street address. The location city, state, and ZIP will not be input.

  9. If the name of the foreign country is not present and cannot be determined, research online or in a geographic dictionary.

  10. When updating the address to a foreign country and IDRS gives an error message that the foreign country code is invalid, enter a "1" in the Foreign Country Override Indicator (FCOI) field of CC BNCHG.

  11. The following is an example of a foreign address change:

    Figure 3.13.2-1

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    Foreign Address Change

  12. See IRM 3.13.5 for an example of an IMF foreign address change.

  13. All transactions containing an address change will have the requester's name, title, and phone number if present in the Remarks field of the transaction. If the signature is illegible, enter "SIGNATURE ILLEGIBLE" in Remarks field of the transaction.

3.13.2.3.5  (01-01-2013)
Change of Address

  1. Correspondence indicating address changes may be directed to Entity for necessary action. However, if the correspondence involves an adjustment action, collection activity, or a TAS situation other than an entity issue, the address update will be acted upon by the function responding to the primary issue.

  2. A taxpayer's mailing address will not be updated unless clear indication of a change from the taxpayer or his representative is received. The exception would be when resolving undeliverables.

    • When processing forms/documents that have an "address change box" , Master File will be updated if the "address change box" has been marked by the taxpayer.

    • Master File will not be updated with the address from a form that does not have an "address change box" unless the taxpayer has given clear instructions to update his address.

    • Generally, the taxpayer's address will be updated from every return received per Rev. Proc. 2010-16. Ensure the return is not a copy of a previously filed/posted return.

  3. The National Change of Address (NCOA) program links with the United States Postal Service (USPS) change of address requests received from postal customers. The NCOA run updates Master File with the address provided by the postal customer/taxpayer. The DLNs from these changes will be:

    • BMF XX-9-63-995-777-66-Y

    • IMF XX-2-63-995-999-99-Y

  4. Never change the address if the acronym FDIC (Federal Deposit Insurance Corporation) is in any of the name lines. If no other action is needed, indicate "No Action" on document being processed.

  5. Signatures on Forms 8822/8822-B and requests for address changes will be accepted according to the terms of Prima Facie Evidence. Prima Facie means "at first appearance; at first view, before investigation " . If there is no contradicting evidence to dispute the authority of that person, the signature must be accepted. An all inclusive authorization list of authorized signatures/titles will not be provided because an inclusive list is not possible.

  6. Use the following table to process an address change:

    If... Then...
    a. The documentation is for an. address change only (including Form 8822/8822-B), Enter the entire taxpayer address into CC BNCHG. A TC 014 will generate from the input. The forms or documentation will be X'd out and destroyed by the Entity Control Team.
    b. A domestic street address is input, The mailing city, state and ZIP must be input.
    c. A foreign street address is input, The foreign city and foreign country must be input in the mailing street address and mailing city, state and ZIP lines.
    d. A foreign postal code is present and space allows, It must be input.
    e. A foreign city or postal code is input, The foreign street address must be input.
    f. A domestic mailing city, state and ZIP or major city code and ZIP code are input, The mailing street address must also be input.
    g. A major city code is input, A mailing ZIP code must be input.
    h. It is determined that the correspondence has been initiated by a third party, Research the CAF using CC CFINK. If the representative is on CC CFINK for any MFT, proceed with the address change.
    i. A proper authorization is not found, Send Letter 104C (or 6800sce) to the taxpayer's address on Master File requesting a completed Form 8822-B.
    j. A proper authorization is found, Update the address as requested.
    k. The address change is for an IMF (SSN) account, If the MFT is 08, do not make any changes as they will unpost. When making an IMF change, enter 8 in the Blocking Series field of CC INCHG unless using AMS. This denotes that Entity made the change. If an IMF address change is received at a BMF site, it will be processed as BMF MISCELLANEOUS. Do not transship IMF address changes.

  7. General requirements for making address changes on all Entity programs:

    If... Then...
    We receive a letter signed by the taxpayer or an authorized representative, and the taxpayer's full name and correct EIN are present, Make the address change.
    A return has a different address than what is on MF and the address change box is checked, Make the address change.
    Any of the required information is missing from the taxpayer's request for a change of address, Do not change the address. Correspond with the taxpayer via 104C (or 6800sce) at the new address and advise the taxpayer of the information needed.
    Correspondence, notices, or C letters sent by the Service that solicits or requires a response from the taxpayer is returned to the Service by the taxpayer with corrections marked on the taxpayer's address information, the correspondence will constitute clear and concise written notification of a change of address. The taxpayer's signature is not required on the correspondence, notice, or C letter, Make the address change.
    The address has a typographical error, misspelling, or contains additional information (suite number, apartment number, etc.), Make the address change.
    The taxpayer requests a temporary address change, Advise the taxpayer a temporary address change will replace their permanent address on IRS records and they will use a Form 8822/8822-B for permanent address changes.

  8. If a taxpayer requests an address change during telephone contact regarding an Entity issue, you may accept oral authority for the address change. Follow the Oral Statement Documentation requirements in IRM 21.1.3 . Rev. Proc. 2010–16 allows address changes over the phone effective June 1, 2010. It is no longer required that the taxpayer have "an open issue" to request an address change over the telephone. The caller must be authorized to request the address change. Put the name, title, and phone number of the caller in the Remarks field of the transaction.

  9. If communication is received from a third party (CPA, agent, etc.) indicating the taxpayer is no longer a client and their address should be removed from the account, take the following actions:

    If... And... Then...
    Third party supplies a new address, Third party has been authorized by the taxpayer, Update Master File with the address provided.
    Third Party does not supply a new address, A new address cannot be found, Input TC 593-82 on all open FRCs or MFT that was filed by the third party.
    Third party does not supply a new address, The LKA cannot be found, Input TC 593-82 on all open FRCs or MFT that was filed by the third party.
    Third party does not supply a new address, The LKA is found and is accurate, Send 104C (or 6800sce) to the taxpayer at their LKA requesting completion of Form 8822-B.

  10. All transactions containing an address change will have the requester's name, title, and phone number if present in the Remarks field of the transaction. If the name is illegible, enter "SIGNATURE ILLEGIBLE" in Remarks field of transaction.

  11. See IRM 3.13.2.1.4 (17) for address usage with CC LETER.

3.13.2.3.6  (01-01-2013)
Form 8822, Change of Address (For Individual, Gift, Estate, or Generation-Skipping Transfer Tax Returns)

  1. Form 8822, Change of Address, is filed by IMF and Estate and Gift (E&G) taxpayers to furnish written notification of a change of address to the Service.

    1. When Form 8822 is received with an Entity case or as a stand alone document, the change of address will be entered with any other required data.

    2. Before updating an address, the TIN entered on Form 8822 will be verified as the only TIN assigned to taxpayer.

    3. If Part I of Form 8822 is complete and received in a BMF site, it should be processed. See IRM 3.13.5. Process Form 8822 per chart below.

  2. The Remarks field of the transaction updating the taxpayer's address will contain the name, title, and phone number from the signature line of Form 8822. If the signature is illegible, enter "SIGNATURE ILLEGIBLE" in Remarks field of transaction.

    If... And... Then...
    (a) Form 8822 clearly indicates a primary name change (FKA, previous name, etc), 1. The Form 8822 is signed by authorized individual, Change the name
    2. The Form 8822 does not have an authorized signature, Correspond for verification with a 252C Letter
    (b) Unable to determine if the taxpayer is changing their name,   Do not update the taxpayer's name. Send the 252C letter instructing the taxpayer to verify the name change after updating address.
    (c) Any required information is missing,   Return Form 8822 to the taxpayer with 104C or 6800sce. Send the letter to the taxpayer's "new" address. Instruct the taxpayer to complete Form 8822 and return to us.
    (d) The taxpayer is affected by a Presidentially Declared Disaster Area,   Change the address(es) via telephone call or any other way the taxpayer informs us to change the address.
    (e) The taxpayer checks Box 2 in Part 1, indicating that gift, estate, or generation-skipping transfer tax will be filed (Form 706, Form 709, etc.), 1) The BMF SSN (SSN'V') is not established on the Master File, Input a TC 000 to establish the account.
    2) The SSN'V' is already established on the Master File, Update the address(es) as required. See Figure 3.13.2–26. When updating the address on an SSN'V'/'W', the MFT field of CC BNCHG must be completed. If the change is for a Form 709 account, the field NM-YR/QTR> must also be completed. If the change is for a Form 706 account, the field DT-OF-DEATH> must also be completed.
    (f) The EIN on Form 8822 is not on the Master File, IDRS research shows the EIN was assigned to the taxpayer reflected on Form 8822, Input TC 000 with no FRCs.
    (g) The EIN on Form 8822 is not on the Master File, IDRS research shows no record of the EIN being assigned, Send the taxpayer a 104C without an EIN asking for a copy of the notice assigning the EIN. When received, TC 000 the EIN with no FRCs.
    (h) Box 2 is checked, Account exists on EPMF, Take no action. Fax volumes of less than 50 documents to EP Entity at 801-620-7116. If volume is greater than 50, mail to Ogden Entity Clerical Team. EP TEs will determine the action needed on Form 8822 and perform all necessary actions.

3.13.2.3.7  (01-01-2013)
Form 8822-B, Change of Address - Business

  1. A new form has been created for businesses to use when requesting a change of address: Form 8822-B. The form became available in March 2012. All fields of Form 8822-B must be complete for Form 8822-B to be considered processable.

  2. Taxpayers that use EINs will submit Form 8822-B when a change of address is needed. Ensure the EIN on the form is the only EIN assigned to the taxpayer. Take actions to consolidate if more than one EIN is located.

  3. Taxpayers that use BMF SSNs (filers of Form 706 and 709 series) will continue to use Form 8822

  4. The Remarks field of the transaction updating the taxpayer's address will contain the name, title, and phone number if available from the signature line of Form 8822-B.

  5. Process Form 8822-B as follows:

    If... And... Then...
    (a) Form 8822-B clearly indicates a primary name change (FKA, previous name, etc), 1. The Form 8822-B is signed by authorized individual, Change the name
    2. The Form 8822-B does not have an authorized signature, Correspond for verification with a 252C Letter
    (b) Unable to determine if the taxpayer is changing their name,   Do not update the taxpayer's name. Send the 252C letter after updating address instructing the taxpayer to verify the name change .
    (c) Any required information is missing,   Return Form 8822-B to the taxpayer with 104C Send the letter to the taxpayer's "new" address. Instruct the taxpayer to complete Form 8822-B and return to us.
    (d) The taxpayer is affected by a Presidentially Declared Disaster Area,   Change the address(es) via telephone call or any other way the taxpayer informs us to change the address.
    (e) The EIN on Form 8822-B is not on the Master File, IDRS research shows the EIN was assigned to the taxpayer reflected on Form 8822-B, Input TC 000 with no FRCs.
    (f) The EIN on Form 8822-B is not on the Master File, IDRS research shows no record of the EIN being assigned, Send the taxpayer a 104C without an EIN asking for a copy of the notice assigning the EIN. When received, TC 000 the EIN with no FRCs.
    (g) Box 2 is checked, Account exists on EPMF, Take no action. Fax volumes of less than 50 documents to EP Entity at 801-620-7116. If volume is greater than 50, mail to Ogden Entity Clerical Team. EP TEs will determine the action needed on Form 8822-B and perform all necessary actions.

3.13.2.4  (01-01-2013)
Undeliverable Mail and Notices

  1. Undelivered CP 576 notices (Notices of EIN Assigned) will be returned to Entity for research and correction of entity data. If received in Entity, CPs 575 will be routed to Cincinnati Accounts Management Center, EIN Function.

  2. Undeliverable mail will often have a yellow sticker from the United States Postal Service (USPS) showing the taxpayer's new address. Research to ensure the yellow sticker address is not already posted/pending. If the address on Master File has not been updated, input TC 014 and send 2475C/6800sce to the taxpayer's new address enclosing undelivered Entity generated CP/Correspondence letter.

  3. Research CCs INOLE, IRPTR, ENMOD, BMFOL'E', and FINDE/FINDS for a better address for the taxpayer. In most cases the address on CC INOLE will be the same as the notice.

  4. CC INOLE can give you alternatives to locating the taxpayer such as

    1. BMF sole proprietor—the IMF account for this taxpayer may contain a different address.

    2. Any BMF account can be checked with CC INOLE 'P' to show an address from the EPMF and vice versa.

    3. Research for another address under the XREF TIN. If address is found, re-mail notice using 6800sce or 2475C in care of the individual found from the XREF TIN. If 6800sce is used, Input history item on CC ENMOD that says:
      6800SCE
      4UNDEL

    4. Follow the steps below for processing:

      If... And... Then...
      (1) Interim letter (2645C, 2644C, etc.) is received as undeliverable, Account issue has been resolved, Prepare undeliverable letter for destruction per local procedures.
      (2) A new address cannot be found via IDRS, All X-REF TINs have been researched without finding a better address, Contact the taxpayer via telephone.
      (3) Taxpayer can be reached via telephone, taxpayer supplies you with better address, Mail the notice/correspondence to the new address using 2475C or 6800sce.
      (4) Unable to locate a better address, Unable to reach taxpayer via telephone, Input TCs 593–82 on all active FRCs. Input TC 971 Action Code 661 which will generate the Undeliverable (UD) indicator. Prepare notice/correspondence for destruction per local procedures.
      (5) There is indication the taxpayer is deceased, There are no active FRCs on the EIN, Input TC 971 Action Code 661 on all MFTs reflecting a posted return on CC BMFOL'I' Use the tax period containing the date of death. TC 971 AC 661 generates the Undeliverable (UD) indicator. Prepare undeliverable for destruction per local procedures.
      (6) There is indication the taxpayer is deceased, There are active FRCs on the EIN, Research IDRS for an ESTATE EIN. If found, update the taxpayer's address to match the address on the estate EIN.
      If unable to locate an estate EIN, input TC 593-82 on all open FRCs. Input TC 971 Action Code 661 which will generate the Undeliverable (UD) indicator on all open modules. Prepare undeliverable for destruction per local procedures.

  5. Undelivered CPs 26X notices (Notices of Form 2553—Election by a Small Business Corporation) will be returned to Entity for research and correction of entity data. You may need to ESTAB Form 2553 to secure a shareholder's address.

  6. It is acceptable to re-mail a notice to another address. The taxpayer must provide clear and concise notification of a change of address A different address on a letterhead or return address on an envelope is not acceptable for updating Master File. Correspond with the taxpayer at the "better" address asking for a completed Form 8822-B.

  7. If an undeliverable is received and it was undeliverable previously, prepare for destruction per local procedures. Ensure a TC 593 Closing Code 82 is on all open FRCs.

3.13.2.4.1  (01-01-2013)
Undelivered Correspondence

  1. Undeliverable correspondence initiated by Entity will be returned to Entity for research and correction of entity data. CCs INOLE, IRPTR, FINDE/FINDS can be utilized to locate a different address. Use the following procedures:

    If... Then...
    a. A different address is found, Re-mail the correspondence to the new address using the 6800sce or 2475C Letter without updating the address on Master File. If 6800sce is utilized, input history item on CC ENMOD that says:
    6800SCE
    4UNDEL
    If an undeliverable is received and it was undeliverable previously, prepare for destruction per local procedures. Ensure a TC 593-82 is on all open FRCs.
    b. A new address cannot be found, Input TC 593 CC 82 on the current tax period for all active FRCs. Input TC 971 Action Code 661 to generate Undeliverable (UD) indicator. Prepare for destruction per local procedures.

3.13.2.4.2  (01-01-2013)
Undeliverable Mail Returned From a Print Site

  1. The Print Sites are identifying notices and letters that cannot be delivered by the United States Postal Service standards. This includes any notice or letter bearing a campus address.

  2. In January 2010, program 390–00800 will be used when processing these undeliverables.

  3. See IRM 3.13.2.4 for processing instructions.

3.13.2.5  (01-01-2013)
BMF Employment Codes (ECs)

  1. BMF Employment Codes (ECs) are on accounts to indicate the taxpayer is not liable for Form 940, Employer's Annual Federal Unemployment (FUTA) Tax Return. Except EC "Z" . It simply denotes a Federal Credit Union.

  2. The BMF Employment Codes (ECs) are A, C, F, G, I, M, S, T, and W.

  3. The primary programs processed by Entity TEs involving ECs are Form 941 and Form 940.

  4. Entity TEs are responsible for ensuring ECs are correct and the taxpayer is filing the correct return(s).

  5. BMF Entity is not able to add or change ECs A, F, G, or T. If an entity needs action on one of these ECs , contact Federal State Local Government at 512-499-5706.
    If no further Entity action is needed, route the case to the address below instead of calling:
    Internal Revenue Service-FSLG
    300 E. 8th St
    Stop 4098AUS
    Austin, TX 78701

  6. The ECs are applicable to certain Form 941, Form 943, and Form 944 filers. See table below for EC definitions:

    Code Entity Type
    A A government agency acting as an employer's fiscal agent under Section 3504 of the Internal Revenue Code (IRC)
    C Church or Church -controlled Organization filing Form 8274 (not subject to FICA or FUTA)
    F Federal Employer
    G State or Local Government Agency
    I Indian Tribal Government
    M Maritime Industry
    S Foreign Subsidiary
    T State or Local Government Agency covered under Section 218 Agreement
    W Section 501(c)(3) of the IRC Non-profit Organization (not subject to FUTA)
    Z Federal Credit Union - Liable for Form 940

  7. The input of a "9" in the EMPLMNT-CD> field of CC BNCHG deletes any existing EC. However, the changing of ECs has been limited to employees of TEGE/Federal State Local Government (FSLG). If a change to an EC is needed, contact FSLG at 512-499-5706. Identify yourself as an Entity TE in (your POD), provide your IDRS number, SEID, and telephone number.

  8. The Economic Opportunity Act (EOA) programs are carried out by state and local governmental entities or private non-profit organizations through grants or contracts with the Federal Government. When new entities are formed to carry out EOA projects they will be state or local government entities or non-profit organizations. Examples of EOA employers are as follows:

    • Anti-Poverty Programs

    • Community Action Programs

    • Head Start Programs

    • Neighborhood Youth Corps

    • Public Law 88–452

    • Economic Opportunity Act, Office or Program

    • Work Study or Work Training Program

    • Youth Conservation Corps (YCC)

    • Job Corps

    • Volunteers in Service to America

  9. If a Form 940 FRC is present on an EIN with an Employment Code , input TC 016 to delete the FRC. It may be necessary to contact FSLG at 512-499-5706. Research CC BMFOL'I' for MFT 10 modules. If any are present and unsatisfied for the period (and later periods) the entity became exempt from FUTA, input TCs 590-20.

3.13.2.5.1  (01-01-2013)
Employment Code (EC)"A"

  1. This EC is given to government agencies acting as employer/payer's fiscal agents under IRC Section 3504. These agents may refer to themselves as:

    • Household Employer Agents,

    • Fiscal agents,

    • Employer agents, or

    • Fiscal intermediaries

  2. The employer/payers may be disabled individuals or other welfare recipients receiving home-care services through a state or local government program.

  3. A fiscal agent may:

    • Represent many disabled individuals or other welfare recipients receiving home care services through a state or local program. These taxpayers may be referred to as "clients" by the agent.

    • Be a government entity or a non-governmental entity

    • Already have an existing EIN that is used to file employment taxes for the agent's own employees

    • Request a second EIN to be assigned to them for the specific purpose of acting as an agent for these employers under Section 3504, if they are a government entity.

      Note:

      Non-governmental agents are not encouraged to obtain a second EIN to file employment taxes on behalf of these household employers. The Household Employer Agent files aggregate employment tax returns for all of their own employees and for the employees of the household employers, including Form 940. However, if requested, non-governmental agents may also obtain a second EIN to file employment taxes on behalf of these household employers.

  4. The words Fiscal Agent will be behind the name of the governmental entity acting as a fiscal agent. If missing, add "Fiscal Agent" behind the agent's name.

  5. An entity with EC "A" will also have a Form 941 FRC 01.

3.13.2.5.2  (01-01-2013)
Employment Code (EC)"C"

  1. This code is generated from a posted TC 070 on churches or qualified church-controlled organizations which have filed Form 8274, Certification by Churches and Qualified Church-Controlled Organizations Electing Exemption from Employer Social Security and Medicare Taxes.

  2. Forms 8274 are processed exclusively at OSPC.

  3. See IRM 3.13.12.

3.13.2.5.3  (01-01-2013)
Employment Code (EC)"F"

  1. This code is assigned to agencies of the United States Government.

  2. If a new EIN needs EC "F" , or if an entity changes and becomes eligible for EC "F" :

    1. This EC may only be assigned with supervisory approval.

    2. An entity with EC "F" , will also have a Form 941 FRC of "02" .

    3. An entity will receive EC "F" whether the taxpayer currently has employees or not when processing Form SS-4, see IRM 21.7.13.

  3. The following agencies will have EC "F" :

    • Department of State

    • Department of the Treasury

    • Department of Defense

    • Department of the Army

    • Department of the Navy

    • Department of the Air Force

    • Department of Health and Human Services

    • Department of Education

    • Department of the Interior

    • Department of Commerce

    • Department of Labor

    • Department of Transportation

    • Department of Housing and Urban Development

    • Department of Justice

    • Department of Agriculture

    • Department of Homeland Security

    • National Guard

    • An executive department of the government or a component agency

  4. An agency of the U.S. Government that is not part of any executive department or its components at the National Headquarters of the agency or in the field such as the following:

    • U.S. District Court

    • U.S. Court of Appeals

    • U.S. Tax Court

    • General Services Administration

    • U.S. Atomic Energy Commission

    • Federal Trade Commission

    • Government Accountability Office

    • Office of Economic Opportunity

    • Federal Power Commission

    • U.S. Small Business Administration

    • Library of Congress

    • Interstate Commerce Commission

    • Veterans Administration

    • Smithsonian Institution

    • Securities and Exchange Commission

    • National Aeronautics and Space Administration

  5. Corporation wholly or principally owned by the U.S. Government which has been created by law and which performs a governmental function such as the following:

    • Federal Deposit Insurance Corporation

    • U.S. Postal Service

    • Tennessee Valley Authority

    • Federal Home Loan Bank (Not Individual Home Loan Banks)

    • Federal Reserve Board (Not Individual Regional Federal Reserve Banks)

  6. Federal instrumentalities such as the following:

    • Army and Air Force Post Exchange

    • Navy or Coast Guard Ship Stores

    • Army and Air Force Motion Picture Services and Navy counterpart

  7. Organizations that are closely connected to, but not an official part of the U.S. government establishment are entitled to EC "F" if they meet strict standards. These organizations conduct financial, social, morale or housekeeping activities such as the following:

    • Officer's Clubs

    • Enlisted Men's Club

    • Non Commissioned Officer's (NCO) Clubs

    • Officer's Open Messes

    • NCO's Open Mess

    • Billeting Funds, etc.

  8. Before assigning EC "F" to these organizations, a statement should be obtained from the Post, Camp, Station or Base Commander stating the following:

    1. The activity exists to promote the morale, comfort and well being of members of the Armed Forces, or authorized civilians.

    2. The activity is supported by an authorized non-appropriated fund as prescribed by the applicable regulations of the Service concerned.

    3. The activity is authorized by the Post, Camp, Station, Base or Major Command Commander, and is supervised by him/her.

    4. That the above referenced commander's supervision includes the periodic audit of the activities financial records, or that such audit is regularly performed by a higher authority, as the appropriate service regulations prescribed.

  9. Do not assign EC "F" to any of the following:

    1. Any religious, fraternal or benevolent organization

    2. Any ethnic or tribal organization for example, Indian tribe, tribal council, etc.

    3. Any private corporation or business entity that has in its name words such as "U.S., United States, Federal or Government" .

  10. If the type of entity cannot be determined or if the entity is a questionable "F" Code filer, take the following actions:

    1. Research the account as necessary.

    2. Contact the organization to clarify its status.

    3. If the organization is a true "F" Code, remove any erroneous filing requirements such as 1120, 1065, etc.

  11. If the organization is not a true "F" Code, take the following actions:

    1. Remove any erroneous filing requirements.

    2. Remove the "F" Code.

    3. Establish the entity with the correct filing requirements. Ensure that the organization does not have another EIN established for the same "F" Code entity.

    4. If the "F" Code is removed forward the information to AM/Adjustments to be assessed penalty and interest under the correct filing requirements.

3.13.2.5.4  (01-01-2013)
Employment Code (EC) "G"

  1. Assign this code to all state and local government agencies.

  2. When assigning EC "G" , also assign a Form 941 filing requirement of 01, because these taxpayers are responsible for income tax withholding even if they are not responsible for social security and Medicare taxes. However, if the taxpayer is from Guam or American Samoa, assign a filing requirement of 06, for the Form 941-SS.

  3. If you cannot determine from Form SS–4 that the entity is an agency of a state or local government or it is a privately owned organization, contact the entity to clarify the status prior to the assignment of EC "G" . If contact cannot be made using the telephone, input Letter 45C .

  4. The following organizations will be assigned EC "G" :

    • A state or commonwealth

    • An agency, bureau, or department of any such state or commonwealth

    • A county

    • An agency, bureau, board, or department of any such county

    • A municipality, town, village, ownership or any like unit of local government

    • An agency of a local government, such as a school district, Board of Education, public school, sanitation district, transit authority, welfare department, housing authority, cemetery, district soil/water conservation, water district, community service district, health department, etc.

  5. If a state or local government instrumentality requests and receives an exemption under IRC Section 501(c)(3), the EC remains a "G"

3.13.2.5.5  (01-01-2013)
Employment Code (EC)"I"

  1. Assign EC "I" to Indian Tribal Governmental (ITG) entities. Chief Counsel ITG will determine if an entity requires an EC "I" . If so, verify that the BOD Code is TE. Update the Business Operation Date (BOD) Client Code to I. Add a Form 940 FR of either 3 (compliant) or 4 (non-compliant) at the time the EC "I" is added. Chief Counsel ITG will determine whether the tribe is compliant or non-compliant.

  2. If an Indian Tribal Governmental entity also has a 501(c)(3) exemption, the EC must be "W" without a Form 940 filing requirement.

  3. If Master File research indicates the Exempt Organization (EO) Status is 41, 70-72, treat the entity as if they are a "regular" ITG entity with a BOD Code of TE, EC of I, and a Form 940 FR of 3 or 4.

  4. If the EO Status of 40 or 42, the BOD Code should be TE, but make no changes to the EC, BOD Client Code or filing requirements. If the EO Status has been in 40 for several years and the organization is continuing to file Forms 941 only and there is no "I" case on EDS, update the EO Status to 41 and treat as a "regular" ITG entity.

3.13.2.5.6  (01-01-2013)
Employment Code (EC) "M"

  1. Assign this code to those Maritime Industry entities which have made payments for employment taxes not yet reported.

  2. This situation arises when a shipping company estimates liabilities and makes payments currently; however, the actual liability is reported on a supplemental Form 941 filed at the termination of the voyage.

3.13.2.5.7  (01-01-2013)
Employment Code (EC) "S"

  1. This code is assigned to a domestic business that has applied for another EIN to extend social security coverage to certain employees of its Foreign Affiliate(s). by filing Form 2032, Contract Coverage under Title II of the Social Security Act.

  2. The filing of Form 2032 secures the election to withhold Social Security from the paychecks of American citizens working overseas.

  3. See IRM 3.13.2.17

3.13.2.5.8  (01-01-2013)
Employment Code (EC) "T"

  1. This code is to be assigned to state and local governmental agencies that have obtained social security coverage for employees under an agreement between the state and the Commissioner of the Social Security Administration. Under IRC 42 Section 218, they are to pay social security tax directly to IRS.

  2. This code will be input through CC BNCHG upon notification from Chief Counsel that a Section 218 agreement has been entered into by a state or local governmental agency.

    Note:

    This code is never assigned from Form SS–4.

  3. Updating the EC from a "G" to a "T" :

    If... Then...
    a. The account is for the same entity as indicated by SSA on the modification letter, Update the EC from "G" to "T" and update the Form 941 to FR 01 or 07 for Puerto Rico accounts.

    Note:

    Delete any erroneous Form 940 filing requirement. Do not update Form 941 FRC 9 or 10 to a 941-01.

    b. The account is not for the same entity as indicated by SSA, Research for a better EIN.
    c. No EIN can be found, Correspond with the taxpayer or state administrator.
    d. A filling requirement other than Form 941/940 (for example, Form 1120, 1065) is present, Research the account. Taxpayer contact may be necessary.
    e. The taxpayer corresponds that he is not active, Do not remove EC "T" . Correspond with the taxpayer informing them that Form 941 will still be required once a year and they should check the seasonal/intermittent box.

3.13.2.5.9  (01-01-2013)
Employment Code (EC) "W"

  1. This code is assigned to tax exempt organizations of the type described in IRC Sections 501(c)(3), 501(e), 501(f) and 501(k) .

  2. These will be organizations operated exclusively for religious, charitable, scientific, literary, educational, or humane purposes, or for the purposes of testing for public safety, and indicates that the organization is not subject to Federal Unemployment Tax Act (FUTA).

  3. The organization is accorded this exemption from FUTA tax until their application for exempt status is ruled on or it is determined that an application has not been submitted.

3.13.2.5.10  (01-01-2013)
Employment Code (EC) "Z"

  1. This code is assigned to Federal Credit Unions.

  2. This Employment Code does not behave like other Employment Codes as Federal Credit Unions are liable for Form 940. All other ECs indicate the taxpayer is not liable for FUTA, Form 940.

3.13.2.6  (01-01-2013)
Integrated Data Retrieval System (IDRS)

  1. The Integrated Data Retrieval System (IDRS) is used to access and update taxpayer information.

  2. This subsection lists many of the IDRS Command Codes (CCs) used by Entity TEs. This list is not all inclusive.

  3. One of the key elements on IDRS Entity TEs must understand is the Filing Requirement Code (FRC),

    1. The FRC is used to identify the type of return to be mailed to the taxpayer.

    2. If the taxpayer has a FRC and does not file a return, the FRC is used to perform a delinquency check.

  4. The FRCs are input with CC ESIGN, BNCHG or EOCHG or in some cases will be established when a return posts.

  5. Whenever an account is established (TC 000) on the BMF it must have an entry in one of the filing requirement fields, including not required.
    For example, a corporation will have an 1120 FRC and possibly FRCs for Forms 940 and 941. A social club may not need any FRCs, therefore, you must enter a "1" in the Not Required field at the end of the FRCs on CC BNCHG.

  6. The validity checks for filing requirements on CC ESIGN are in IRM 3.13.2.6.2.

  7. The validity checks for filing requirements on CC BNCHG are in IRM 3.13.2.6.3.2.

  8. The validity checks for filing requirements on CC EOCHG are in IRM 3.13.12 (EO Entity IRM).

  9. For a list of the MFT, Form, Type of Return, filing requirements, when to file and the Statutory date for all returns refer to Document 6209 ADP and IDRS Information.

3.13.2.6.1  (01-01-2013)
Research Command Codes (CCs)

  1. Research must be performed to determine if there is an EIN already assigned to a taxpayer before a new EIN is assigned. Be sure to research using the Entity "sort line format" and the Accounts Management Modernized Internet EIN (Mod IEIN) "enter as taxpayer did" format. See IRM 21.7.13. Many consolidation cases have been created due to the taxpayer being on IDRS with two different name controls. Be very cautious so as not to create new work. You should research both ways: historical format used in Entity and Modernized Internet EIN "enter as taxpayer did" format.

  2. There are several systems available in the campus for research as follows:

    • The Taxpayer Information File (TIF) CC ENMOD.

    • The BMF with CCs BMFOL/BRTVU/INOLE.

    • Tax Modules that are on IDRS with CC TXMOD.

    • Everything available on IDRS with CC SUMRY.

    • The Entity Control Log of Bulk EIN Assignments.

    • On-Line Entity and related CCs.

    • The Name Search Facility (NSF) CC NAMES, for SSN research, and NAMEE for EIN research, and NAMEB search for EINs for both primary and "doing- business-as" (DBA) names.

    • The Name Search Facility (NSF) CC NAMEI to research individuals.

3.13.2.6.1.1  (01-01-2013)
CCs MESSG and STATS

  1. CC STATS is the first page of IDRS that appears when the user signs on to IDRS. STATS will reflect today's date and the availability of IDRS.

  2. CC MESSG is used to report daily IDRS and miscellaneous information at each campus. CC MESSG can be accessed at a different site via Universal access.

  3. Some of the specific items shown on CC MESSG include:

    • Availability of IDRS realtime and CCs, including problems experienced by CCs

    • Correspondex status and updates

    • IDRS team numbers, phone numbers, and mail stops

    • Lockbox information

    • Campus user support information

3.13.2.6.1.2  (01-01-2013)
CC FIEMP

  1. The use of this CC enables IDRS users to identify and contact case control owners by researching the ten digit IDRS number of the employee. The user will enter CC FIEMP, one blank space, then the ten digit IDRS number of the case control owner.

  2. CC FIEMP displays the following information:

    • Case control owners name

    • Standard Employee Identification (SEID)

    • Employee's (or their manager's) telephone number

    • IDRS status of the employee (active or inactive)

  3. If CC FIEMP does not show the telephone number, the user may use the case owner's name or SEID to search the Discovery Directory on the IRS intranet or Outlook E-mail system to obtain a valid telephone number.

  4. CC FIEMP will only be used to research work related activities.

3.13.2.6.1.3  (01-01-2013)
CCs NAMEE, NAMEB, NAMES and NAMEI

  1. CCs NAMEE and NAMEB search for EINs for both primary and "doing business as" (DBA) or trade names.

  2. CCs NAMES and NAMEI search for SSNs for both the primary and the secondary filer.

  3. These CCs access the national Name Search Facility (NSF) file at Enterprise Computing Center at Martinsburg and will search for phonetic and spelling similarities. Common abbreviations like Mr., Mrs., Jr., Irrv. Tr., M.D., Corp., and Inc. will not be used as search criteria. CC NAMES can search using last name "," first name or first initial or blank. Using a first name or an initial in addition to the last name is better than using the last name alone.

  4. NAMES/NAMEE does not perform searches on partial last names or partial first names.

  5. Search time for CCs NAMEE/NAMES and NAMEI/NAMEB is directly related to the quality of the input fields. The more specific the information entered, the shorter the search time.

  6. If the CC NAMEB first initial is a plus (+), matching is done on all 15 characters of the last name instead of the first 10 characters.

  7. NAMEB with the definer of X and a first initial of plus (+) will not use the additional last name characters (more than 10) as selection criteria.

  8. The most efficient search is done when the name and Zip Code fields are entered. The Zip Code field must contain a valid 3 or 5-digit Zip Code or will be left blank. It should not contain all zeros. The more specific the information entered, the shorter the search time. For example, a Zip Code search is faster than a state search. The Zip Code has priority over the state and the city, neither of which will be used if the Zip Code has been entered. The address (or partial address), if entered, is then used to further refine the search results.

  9. When a name is the only information entered, CCs NAMES/NAMEE will search default to a national search.

  10. If ** is entered in the state code field, a national search is performed.

  11. Do not query using blanks in the state and ZIP Code fields, because an error message will generate to say "Campus search not available for this campus."

  12. If "NO DATA FOR THIS NAME" is displayed, verify the input and try again after removing input fields in the following order street address, city name, and last 2 digits of Zip Code.

  13. NAMES/NAMEE does not automatically reduce the search. NAMES/NAMEE will display taxpayer names in the sequence of their probability of matching the requested name, with the best matches being displayed first.

  14. NAMEB and NAMEI do not use a formatted input screen like NAMES and NAMEE. Also if NAMEB and NAMEI does not find an exact match, the search will default to the point of searching for matching name. See IRM 2.3.60 for additional information.

  15. CC NAMEE - You can enter up to 70 characters in the Name Line. You must enter the zip code when present. If the zip code is not present then enter the state. The state can be optional when entering the zip code. To narrow the search, a minimum of 5 characters to identify the street address will be entered.

    Example:

    112 Peachtree St will be entered as "112 P" .

  16. The cycle format has been expanded to YYYYMMDD.

  17. For examples of needed fields for these command codes, see the IDRS Command Code Job Aids on SERP.

3.13.2.6.1.4  (01-01-2013)
CC ENMOD

  1. This CC is used to provide a taxpayer's Entity account; BMF, IMF (Individual Master File), NMF (Non Master File), IRAF (Individual Retirement Account File) and EPMF (Employee Plans Master File). This CC shows all of the Entity data and transactions available on the Taxpayer Index File (TIF).

  2. The use of CC ENMOD is required prior to accessing CCs ENREQ, BNCHG, and INCHG.

  3. All Entity transactions post to CC ENMOD. Once CC ENMOD falls from the TIF, all Entity transactions are displayed on CC BMFOL'E'.

  4. There are two new indicators for IDRS that will be displayed on CC ENMOD or CC BMFOL'E.' The indicators are Undeliverable As Addressed "UAA" and Undelivered "UD" . UAA will generate from FINALIST when it's not able to expand or hygiene an address. UD is generated from the input of TC 971 Action Code 661 when mail is received back from USPS as undeliverable.

  5. See IRM 2.3.15 for more information about CC ENMOD

3.13.2.6.1.5  (01-01-2013)
CCs FINDE/FINDS

  1. There are two new CCs to query the NSF database. When an EIN or SSN is entered, every name and address reported to that EIN will appear on your screen.

  2. CC FINDE searches the NSF data base using the taxpayer’s EIN and requires either of the following definers:

    1. D – Only BMF Domestic names and addresses are displayed.

    2. I – Only BMF International names and addresses are displayed.

  3. CC FINDS searches the NSF data base using the taxpayer’s SSN and requires either of the following definers:

    1. D – Only IMF Domestic names and addresses are displayed.

    2. I – Only IMF International names and addresses are displayed.

  4. To search using CC FINDE/FINDS, input the appropriate CC plus the definer D or I and use the taxpayers EIN/SSN (without hyphens or dash).
    Example
    FINDED020278969, will display the domestic names and addresses for EIN 02-0278969.
    The domestic or international addresses/names for the appropriate EIN will display in cycle/year order. The most current taxpayer information will display first and includes any subsequent names/addresses displaying in descending order.

  5. The cycle format has been updated to YYYYMMDD.

  6. See IRM 2.3.60 , CCs NAMES, NAMEE, NAMEI, and NAMEB for additional information.

3.13.2.6.1.6  (01-01-2013)
CCs INOLE, BMFOL

  1. Command Code INOLE is designed to display Master File entity data (including SSA name controls, Cross Reference information, and Merge Transactions) for a specific Taxpayer Identification Number (TIN) residing on the NAP. The request type (via command code definer) determines the kind of data desired by the requester. Requests are researched via the input TIN. If primary TIN is unknown, a request may be input with the spouse's TIN. There are five types of INOLE inquiries that can be requested.

  2. Command Code INOLE input with the definer "G" — an unedited or edited TIN will be input. This command will be useful when the tin type is unknown. The returning screen will contain any nameline information available for any account attributable to that number, regardless of file if edited TIN is input. This request type involves multiple database accesses and should be used only when necessary.

    1. Command Code INOLE input with the definer "T" — an edited TIN (either SSN or EIN) and file source will be input. This command will be useful when research is desired on all accounts with the same SSN or EIN. Nameline and street address information will be returned to the user for each matching account.

    2. Command Code INOLE input with the definer "S" — an edited TIN and file source will be input. This request type will be most useful when the specific account is already known. Name lines (current and prior), street addresses, tax year, Social Security name controls, cross reference and other information specific to the type of account being requested will be returned to the user.

    3. Command Code INOLE input with the definer "X" — an edited TIN and file source will be input. This request type will be most useful when researching TINs that have no Master File account. DM1 name controls, Cross reference and merge transaction information will be returned to the user. Information returned to the user will be specific to the file source input. On SSN requests, both tin types (valid and invalid) will be searched for data, regardless of file source input. If a file source of IMF valid is input, the resulting display will show data for both the valid and invalid accounts if such data exists.

    4. Command Code INOLE input with the definer "P" — an edited EIN, file source (P), and EPMF Plan number. This request type will be used to display EPMF Plan information. The EPMF SPECIFIC SCREEN is capable of displaying only five plan names. The screen display for the "P" definer is able to display up to ten plan names. The list of plan names displayed will begin with the plan number that is input, or the next highest number.

  3. The Business Master file on-line , BMFOL system provides read-only access to accounts on the Business Master File in Martinsburg, WV. All entities, master file tax modules and the most recent seven years of retention data are in on-line status. See IRM 2.3.59.

    1. CC BMFOL with Definer "E" will show all Entity transactions posted to the Master File. This definer will also show
      Parent's EIN,
      X-REF TIN (owner's TIN),
      Railroad Retirement Board Number,
      Wages Paid Date/Business Operational Date and Business Close Date/Wages Last Paid Date,
      Employment Codes,
      Active FRCs,
      Entity module: Name, Address Fields.

    2. Definer "I" will show the modules that have been created on the EIN with an extension, return, or transaction code. The modules are listed in order of MFT. Entity will utilize several fields of the screen display.
      MFT
      TXPD (Tax Period
      RET PST (Return Posted, Y=yes, N=No)

    3. Definer "T" shows the specific tax module being viewed.
      Input the command code as follows:
      BMFOLTNN-NNNNNNN XXXXXXXX (X=MFT and Tax Period)

    4. Definer "R" shows the specifics of the return posted on the module. The input format is the same as Definer "T"

3.13.2.6.1.7  (01-01-2013)
CCs SUMRY/TXMOD

  1. Command Code SUMRY should normally be used as a first contact with IDRS to determine if a tax module or Control Base exists in the TIF. The SUMRY display will show sufficient data to enable operators to close many cases and associate others in process without further research.

  2. CC SUMRY is used to request for display, a summary of a taxpayer's account which includes all tax modules meeting IDRS selection criteria. The display shows entity data on lines 1 and 2. Tax Module Data, including tax period, various indicators, IDRS Status, Control Base information, Control DLN, IDRS Module Balance and Freeze Codes for a specific tax period begins on line 3 and ends on line 4. Other tax period data follows every two lines until all tax modules have been summarized.

  3. Command Code TXMOD is used to request for display all tax module information for a specific tax period on the TIF. The display consists of Entity data, posted returns, posted transactions, pending transactions, and reject data if available on IDRS TIF. The display shows the latest control DLN of the return.

  4. Command Code TXMOD stores the TIN, File Source, TIN Type, MFT, Tax Period, Case Control Indicator, Name Control and, for EPMF, Plan Number as required data elements for subsequent processing.

  5. For TXMOD a command code definer is required. Definer "A" will display most tax module information present on the TIF.

  6. For more information on CCs SUMRY and TXMOD, see IRM 2.3.11.

3.13.2.6.1.8  (01-01-2013)
CCs RTVUE/BRTVU

  1. These CCs will display return information for both BMF and IMF.

  2. See the IDRS Command Code Job Aids on SERP for additional information. http://serp.enterprise.irs.gov/databases/irm-sup.dr/job_aid.dr/command-code.dr/brtvu_input.htm


More Internal Revenue Manual