3.12.21 Credit and Account Transfers

Manual Transmittal

November 05, 2021

Note:DO NOT REMOVE AND INSERT PAGES OR DISPOSE OF OBSOLETE TRANSMITTALS PRIOR TO JANUARY 1, 2022.

Purpose

(1) This transmits revised IRM 3.12.21, Error Resolution - Credit and Account Transfers.

Material Changes

(1) IRM 3.12.21.4.2.7 - Includes revisions to text, entitled, "Field 01-D - Tax Period (Validity Checks)" , as a result of a recent Functional Specifications Package (FSP) revision. (IPU 21U0345 issued 03-04-2021)

  • Added new tables (i.e., Consistency Check per the program’s Functional Specifications Package (FSP) process specifications) involving the following fields: CONSISTENCY CHECKS: MFT, TAX PERIOD AND TRANSACTION CODE.

(2) IRM 3.12.21.4.2.7 (Paragraph 8) - Adds a process to the Table (for Reference Number 687), entitled CONSISTENCY CHECKS: TAX PERIOD, MFT CODE, AND REFERENCE NUMBER:

  • If the Reference Number is 687, then all of the following items MUST be as follows:

  • The Tax Period is prior to 201512, AND

  • The MFT is 01, 02, 03, 04, 05, 07, 09, 10, 11, 12, 14, 15, 16, 31, 33, 34, 37, 38, 39, 40, 41, 42, 43, 44, 50, 51, 52, 60, 63, 64, 77 OR 78.

  • This item is located on Row 8 of the Table (under Paragraph 8).

  • Source: Changes made to Functional Specifications Package (FSP) 1.35.04.06: Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 11.1.1 and 11.1.1.1.

(3) IRM 3.12.21.4.2.7 (Paragraph 8) - Adds a process to the Table (for Reference Number 693), entitled CONSISTENCY CHECKS; TAX PERIOD, MFT CODE, AND REFERENCE NUMBER:

  • If the Reference Number is 693, then the following items MUST be as follows:

  • The Tax Period is prior to 201801, AND

  • The MFT is 13.

  • This item is located on Row 21 of the Table (under Paragraph 8).

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 13. and 13.1

(4) IRM 3.12.21.4.2.7 (Paragraph 8) - Adds a process to the Table (for Reference Number 694), entitled CONSISTENCY CHECKS: TAX PERIOD, MFT CODE AND REFERENCE NUMBER:

  • If the Reference Number is 694, then the following items MUST be as follows:

  • The Tax Period is prior to 201801, AND

  • The MFT is 13.

  • This item is located on Row 22 of the Table (under Paragraph 8)

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 14. and 14.1

(5) IRM 3.12.21.4.2.7 (Paragraph 9) - Adds a process to the Table (for Reference Numbers 700 and 710), entitled CONSISTENCY CHECKS: REFERENCE NUMBER, TRANSACTION CODE, MFT, AND TAX PERIOD:

  • If the Reference Number is EITHER700OR710, then all of the following items MUST be as follows:

  • The Transaction Code in Section 01 EITHER is 240 or 290AND the Transaction Code in Section 02-19 EITHER is BLANK, TC-190 or TC 240 or TC 241 and or TC-29X through 30X

  • The MFT is 55, AND

  • The tax period is prior to 201003.

  • This item is located on Row 4 of the Table (under Paragraph 9)

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 17. and 17.1

(6) IRM 3.12.21.4.2.7 (Paragraph 9) - Adds a process to the Table (for Reference Number 707, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, TRANSACTION CODE, MFT, AND TAX PERIOD:

  • If the Reference Number is 707, then all of the following items MUST be as follows:

  • The Transaction Code in Section 01 EITHER is TC-240 or TC-290AND the Transaction Code in Section 02-19 EITHER is BLANK, TC-190 or TC- 240 or TC- 241, TC-290 and or TC-291

  • The MFT is (BMF) MFT 05, AND

  • The tax period is prior to 201701.

  • This item is located on Row 5 of the Table (under Paragraph 9).

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 18. and 18.1

(7) IRM 3.12.21.4.2.7 (Paragraph 9) - Adds a process to the Table (for Reference Number 707, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, TRANSACTION CODE, MFT, AND TAX PERIOD

  • If the Reference Number is 707, then all of the following items MUST be as follows:

  • The Transaction Code in Section 01 EITHER is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANK, TC-190 or TC- 240 or TC- 241, TC-290 and or TC-291

  • The MFT is IMF MFT 30, AND

  • The tax period is prior to 201701

  • This item is located on Row 6 of the Table (under Paragraph 9).

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 18. and 18.1

(8) IRM 3.12.21.4.2.7 (Paragraph 9) - Adds a process to the Table (for Reference Number 707, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, TRANSACTION CODE, MFT, AND TAX PERIOD

  • If the Reference Number is 707, then all of the following items MUST be as follows:

  • The Transaction Code in Section 01 EITHER is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANK, TC-190 or TC- 240 or TC- 241, TC-290 and or TC-291

  • The MFT is IMF MFT 31, AND

  • The tax period is prior to 201701.

  • This item is located on Row 7 of the Table (under Paragraph 9).

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 18. and 18.1

(9) IRM 3.12.21.4.2.7 (Paragraph 10) - Adds a process to the Table (for FORM 3552 (FORMAT CODES 325 and 326); displaying TC 767 and other Transaction Codes), entitled CONSISTENCY CHECK (FORM 3552): TC-767, MFT, TAX PERIOD AND TRANSACTION CODE).

  • For Form 3552 (Format Code 325 or 326)

  • ALL of the following items MUST meet the following criteria for this Consistency Check to be valid:

  • Transaction Code in Section 02-19 is equal to 767,

  • MFT Code is 01, AND

  • The Tax Period EITHER is 202003, 202006, 202009, OR 202012, AND

  • Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308 AND the Transaction Code in Sections 02-19 EITHER is BLANK, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309

  • This item is located on Row 7 of the Table (under Paragraph 10).

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1. and 1.1

(10) IRM 3.12.21.4.2.7 (Paragraph 10) - Adds a process to the Table (for FORM 3552 (FORMAT CODES 325 and 326); displaying TC 767 and other Transaction Codes), entitled CONSISTENCY CHECK (FORM 3552): TC-767, MFT, TAX PERIOD AND TRANSACTION CODE).:

  • For Form 3552 (Format Code 325 or 326)

  • ALL of the following items MUST meet the following criteria for this Consistency Check to be valid:

  • Transaction Code in Section 02-19 is equal to 767

  • MFT Code is 09, 11, 14, AND

  • The Tax Period is 202012 AND

  • Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308, AND the Transaction Code in Sections 02-19 EITHER is BLANK, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309

  • This process located on Row 3 of table under Paragraph 10

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1. and 1.1

(11) IRM 3.12.21.4.2.7 (Paragraph 11) - Adds a process to the Table (for FORM 3413 (FORMAT CODES 025 and 026); displaying TC 766 or 767 and other Transaction Codes), entitled CONSISTENCY CHECK (FORM 3413): TC-767, MFT, TAX PERIOD AND TRANSACTION CODE).

  • For Form 3413 (Format Code 025 or 026)

  • ALL of the following items MUST meet the following criteria for this Consistency Check to be valid:

  • Transaction Code in Section 02-19 is equal to 766 or 767;

  • Tax Period is EITHER 202003, 202006, 202009, OR 202012;

  • MFT Code is 01;

  • Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308, AND Transaction Code in Section 02-19 EITHER is BLANK, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and or 309, AND

  • Reference Number equals 280, 296, or 299

  • This process located on Row 2 of table under Paragraph 11

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1.2. and 1.3.

(12) IRM 3.12.21.4.2.7 (Paragraph 11) - Adds a process to the Table (for FORM 3413 (FORMAT CODES 025 and 026); displaying TC 766 or 767 and other Transaction Codes), entitled CONSISTENCY CHECK (FORM 3413): TC-767, MFT, TAX PERIOD AND TRANSACTION CODE).

  • For Form 3413 (Format Code 025 or 026)

  • ALL of the following items MUST meet the following criteria for this Consistency Check to be valid:

  • Transaction Code in Section 02-19 is equal to 766 or 767;

  • MFT is EITHER09, 11, or 14;

  • Tax Period is 202012;

  • Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308, AND Transaction Code in Section 02-19 is BLANK, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and or 309, AND

  • Reference Number equals 280, 296, or 299

  • This process located on Row 3 of table under Paragraph 11

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made to FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1.2. and 1.3.

(13) IRM 3.12.21.4.2.7 (Paragraph 12) - Adds a process for Reference Number 722 to the Table, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT.

  • If the Reference Number is 722, then all of the following items MUST be as follows:

  • The MFT Code is MFT 02 (Corporate Returns), MFT 06 (Partnership Returns), or MFT 07 (REMIC (Form 1066));

  • Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or TC 301, AND

  • Transaction Amount for 290, 291, 300, and or 301 can only be zero.

  • Valid for all tax periods.

  • This process located on Row 2 of table under Paragraph 12 (IRM)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

(14) IRM 3.12.21.4.2.7 (Paragraph 12) - Adds a process for REFERENCE NUMBER 723 to the Table, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT. Field 01-M (Reference Number).

  • If the Reference Number is 723, then all of the following items MUST be as follows:

  • MFT Code is MFT 02 (Corporation Returns) or MFT 06 (Partnership Returns);

  • Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301, AND

  • Transaction Amount for 290, 291, 300, and or 301 can only be zero (0).

  • Valid for all tax periods.

  • This process located on Row 3 of table under Paragraph 12 (IRM)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

(15) IRM 3.12.21.4.2.7 (Paragraph 12) - Adds a process for Reference Number 724 to the Table, entitled CONSISTENCY CHECKS: REFERENCE NUMBER, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT.

  • If the Reference Number is 724, then all of the following items MUST be as follows:

  • MFT is 02 (Corporate Returns), 05 (Trust Returns), or 06 (Partnership Returns), AND

  • Transaction Code in Section 01 is 160 OR Transaction Code in Section 02-19 is 160, AND

  • Transaction Amount can be any amount.

  • This process located on Row 4 of table under Paragraph 12

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3. and 3.1.

(16) IRM 3.12.21.4.2.7 (Paragraph 13) - Adds a process for Reference Numbers 722 or 723 to the Table, entitled , CONSISTENCY CHECK: REFERENCE NUMBER, REFERENCE NUMBER AMOUNT, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT.. The following will appear invalid if EITHER of the following conditions (as displayed in the table below) are NOT correct:

  • If the Reference Number is 722 OR 723, then all of the following items MUST be as follows:

  • The Reference Number Amount is less than or equal to zero

  • Transaction Code in Section 01 is 160 OR Transaction Code in Section 02-19 is 160, AND

  • Transaction Amount can be any amount.

  • This process located on Row 2 of table under Paragraph 13

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

(17) IRM 3.12.21.4.2.7 (Paragraph 14) - Adds a process for Reference Number 724 to the Table, entitled , CONSISTENCY CHECK: REFERENCE NUMBER, MFT, TAX PERIOD, TRANSACTION CODE, TRANSACTION AMOUNT.. The following will appear invalid if EITHER of the following conditions (as displayed in the table below) are NOT correct:

  • If the Reference Number is 724, then all of the following items MUST be as follows:

  • MFT Code either is MFT 02 (Corporate Returns), MFT 05 (Trust Returns), OR MFT 06 (Partnership Returns), AND

  • Tax Period is equal to or greater than 201712, AND

  • Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301

  • The transaction amount may be any amount

  • This process located on Row 2 of table under Paragraph 14

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

(18) IRM 3.12.21.4.2.7 (Paragraph 20) – Revises process for Reference Number 700 in the Table, entitled, CONSISTENCY CHECKS: REFERENCE NUMBER, MFT, TRANSACTION CODE, AND TAX PERIOD.

  • If the Reference Number is 700, then all of the following items MUST be as follows:

  • the MFT is either 30 or 31

  • the Transaction Code in Section 01 EITHER is TC-240 or TC-290 AND Section 02-19 is BLANK, TC-190, 240 or 241 and or 29X or 30X

  • The tax period is BEFORE 201003.

  • This process located on Row 2 of table under Paragraph 20

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 16. and 16.1.

(19) IRM 3.12.21.4.2.7 (Paragraph 20) – Adds process for Reference Number 682 in the Table, entitled, CONSISTENCY CHECKS: REFERENCE NUMBER, MFT, TRANSACTION CODE, AND TAX PERIOD.

  • If the Reference Number is 682, then all of the following items MUST be as follows:

  • The MFT is EITHER 02 (Corporation Returns), 05 (Trust Returns), 06 (Partnership Returns) or 34 (Exempt Organization Business Income Tax Return))

  • The Transaction Code in Section 01 EITHER is 290, 294, 298, 300, 304, or 308 ANDTransaction Code in Section 02-19 EITHER is BLANK, 240, 241, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309

  • the Tax Period is equal to or greater than 201712

  • This process located on Row 10 of table under Paragraph 20

  • Source: Unified Work Request (UWR) 243633

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 7. and 7.1.

(20) IRM 3.12.21.4.2.19 - Includes revisions to text, entitled, "Fields 01-M and 01-N - Reference Number and Reference Number Amount" , to include the following items. (IPU 21U0485 issued 03-29-2021)

  • Added text for locating the Reference Number and Reference Number Amount of the Form 3552, Prompt Assessment Billing Assembly.

  • Expanded procedures for using MFT-REFERENCE-NUMBER Table for checking valid MFTs and Reference Numbers.

  • Added revised procedures for correcting Reference Numbers and Reference Number amounts.

  • Included various editorial changes throughout this subsection.

(21) IRM 3.12.21.4.2.19 - Includes revisions to text, entitled, "Fields 01-M and 01-N - Reference Number and Reference Number Amount" . Introduces the following new Reference Number processes implemented beginning with Calendar Year (CY) 2022 (Reference Numbers are listed in Functional Specifications Package (FSP) Process Specifications order).

(22) IRM 3.12.21.4.2.19 (Paragraph 21) - Reference Number 682:

  • MFT-CD is 02, 05, 06 or 34, AND

  • Tax Period greater than 201712, AND

  • Transaction Code of Section 01 is 290 294, 298, 300, 304, or 308), AND Transaction Code of Section 02 is BLANK, 240, 241, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and/or 309

  • If the transcribed fields do not meet the criteria as described above, the Reference Number and Tax Period fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243633

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 7. and 7.1.

(23) IRM 3.12.21.4.2.19 (Paragraph 36) - Reference Number 724:

  • MFT 02 (Corporate Returns) and MFT 06 (Partnership Returns), AND

  • Tax Period is 201712 or later, AND

  • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301, and

  • Transaction Amount for 290, 291, 300 and or 301 may be any amount.

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, Transaction Amount, and Tax Period fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 21. and 21.1.

(24) IRM 3.12.21.4.2.19 (Paragraph 44) - Penalty Reference Number (PRN) 722:

  • MFT is 02 (Corporate Returns) or 06 (Partnership Returns) or 07 (REMIC (Form 1066)), AND

  • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301, AND

  • Transaction Amount for 290, 291, 300 and or 301 must be equal to zero.

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206,

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

(25) IRM 3.12.21.4.2.19 (Paragraph 45) - Penalty Reference Number (PRN) 723:

  • MFT is 02 (Corporate Returns) or 06 (Partnership Returns), AND

  • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301, AND

  • Transaction Amount for 290, 291, 300 and or 301 can only be zero

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

(26) IRM 3.12.21.4.2.19 (Paragraph 46) - Penalty Reference Number (PRN) 724:

  • MFT is 05 (Trust Returns), AND

  • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) OR Transaction Code in Section 02-19 is 160, AND

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3. and 3.1.

(27) IRM 3.12.21.4.2.19 (Paragraph 47) - Penalty Reference Number (PRN) 722:

  • MFT is 02 (Corporate Returns), 06 (Partnership Returns), or 07 (REMIC (Form 1066)), AND

  • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) AND Transaction Code in Section 02-19 is 160, AND

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

(28) IRM 3.12.21.4.2.19 (Paragraph 48) - Penalty Reference Number (PRN) 723

  • MFT is MFT 02 (Corporate Returns) or MFT 06 (Partnership Returns), AND

  • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) AND Transaction Code in Section 02-19 is 160, AND

  • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

  • Source: Unified Work Request (UWR) 243206

  • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

(29) IRM 3.12.21.5.2.1 - Includes revisions to text, entitled, "Section 02-19 - Fields A, D, and G - Transaction Date" . Added a procedure, per Ogden campus’ request, to return the transaction to the originator for clarification. (IPU 21U0345 issued 03-04-2021)

(30) IRM 3.12.21.5.2.2- Includes revisions to text, entitled, "Section 02-19 - Fields B, E, and H - Transaction Codes" . Expanded existing procedures for clearer understanding, per Ogden campus’ request, to return the transaction to the originator for clarification. (IPU 21U0345 issued 03-04-2021)

(31) IRM 3.12.21.7.2.1 - Includes revisions to text, entitled, "Section 30 -33 - Fields A, D, and G - Status/Interest-to-Dates" . Revised procedures for clarification, per Ogden campus’ request, expanding procedures to provide specific steps to contact originator for clarification, research and correction. (IPU 21U0345 issued 03-04-2021)

(32) IRM 3.12.21.7.2.2 - Includes revisions to text, entitled, "Sections 30 Through 33 - Fields B, E, and H - Status Transaction Codes" . Revised procedures for clarification, per Ogden campus’ request, expanding procedures to provide specific steps to contact originator for clarification, research and correction. (IPU 21U0345 issued 03-04-2021)

(33) IRM 3.12.21.8.2.1 - Includes revisions to text, entitled, "Sections 36 Through 39 - Fields A, C, E, and G - Abstract/IRS Numbers" , to include the following items. (IPU 21U0485 issued 03-29-2021)

  • Expanded procedures for using the Abstract Number Table and for returning the invalid record to the originator.

  • Included editorial changes in this subsection.

(34) IRM 3.12.21.9.1 - Includes revisions to text, entitled, "Section 40 - Fields A Through X Descriptions" , based on proposed Calendar Year 2022 text changes to the Form 3413 (Transcription List (Account Transfer-In) and Form 3552 (Prompt Assessment Billing Assembly), to include the following new line items:

  • Field 40-C, Taxable Social Security Wages for qualified sick leave (Form 941, Form 943, Form 944)

  • Field 40-D, Taxable Social Security Wages for qualified family leave (Form 941, 943, 944)

  • Field 40-N, Nonrefundable portion of credit for qualified sick and family leave wages (Form 941, 943, 944, CT-1)

  • Field 40-O, Nonrefundable portion of employee retention credit due to the COVID-19 crisis (Form 941, 943, 944, CT-1)

  • Renumbered all Section 40 field designations from Field 40-A through Field 40-T to Field 40-A through Field 40-X

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made throughout Functional Specifications Package (FSP) 1.35.04.06

(35) IRM 3.12.21.9.2 - Includes revisions to text, entitled, "Correction Procedures - Section 40" . Changed MFT Table and text to include Calendar Year 2022 text changes to the Form 3413 (Transcription List (Account Transfer-In) and Form 3552 (Prompt Assessment Billing Assembly).

  • Source: Unified Work Request (UWR) 238671

(36) IRM 3.12.21.9.2.1 - Includes revisions to text, entitled, "Section 40 - Requirements Fields A Through X" . Changed MFT Table and text to include Calendar Year 2022 text changes to the Form 3413 (Transcription List (Account Transfer-In) and Form 3552 (Prompt Assessment Billing Assembly).

  • Source: Unified Work Request (UWR) 238671

  • Source: Changes made throughout Functional Specifications Package (FSP) 1.35.04.06

(37) IRM 3.12.21.10.2 - Includes revisions to text, entitled, "Correction Procedures - Section 41" , to include the following items. (IPU 21U0485 issued 03-29-2021)

  • Adds correction procedures for Credit Reduction transactions and records.

  • Expands procedures for correctly determining and validating Section 41 (Credit Reduction) criteria.

  • Provides procedures to follow when Credit Reductions criteria are not met and require originator review.

  • Places increased emphasis in subsection for using Exhibit 3.12.21-9, Credit Reduction Chart.

  • Included various editorial changes throughout this subsection.

(38) Revised Exhibit 3.12.21-8, Reference Numbers to Introduce the following Reference Numbers and related information:

  • Penalty Reference Number (PRN) 682 valid with MFT 02 (S Corporation Returns), MFT 05 (Fiduciary (Form 1041 Series)), MFT 06 (Partnership Returns) and 34 (Form 990-T Returns)

  • Tax periods 201712 and greater

  • Source: Unified Work Request (UWR) 243633

  • Penalty Reference Number (PRN) 722 valid with MFT 02 (Corporate Returns), MFT 06 (Partnership Returns) and MFT 07 (REMIC (Form 1066))

  • Valid for all tax periods

  • Source: Unified Work Request (UWR) 243206

  • Penalty Reference Number (PRN) 723 valid with MFT 02 (Corporate Returns) and MFT 06 (Partnership Returns)

  • Valid for all tax periods

  • Source: Unified Work Request (UWR) 243206

  • Penalty Reference Number (PRN) 724 valid with MFT 02 (Corporate Returns), MFT 05 (Trust Returns), and MFT 06 (Partnership Returns)

  • Tax Period must be 201712 and later

  • For Transaction Code 160 (Manually Computer Failure to File (FTF) Penalty):

  • Sources: Unified Work Requests (UWRs): 238671, 243206, and 243633

(39) Revised the Internal Revenue Manual (IRM), where necessary, for the following types of editorial changes:

  • Spelling, grammar, formatting, and plain language

  • IRM references, citations, and links

  • IRM graphics and alternative text

  • Italics, removed per IRM Style Guide

  • Expanded or modified Verbal Descriptive Narrative (VDN) descriptions

Other significant changes to IRM 3.12.21, Error Resolution - Credit and Account Transfers, are shown above.

Effect on Other Documents

IRM 3.12.21, Error Resolution - Credit and Account Transfers, dated November 20, 2020 (effective January 01, 2021), is superseded. The following IRM Procedural Updates (IPUs) issued March 04, 2021, through March 29, 2021, have been incorporated into this IRM: 21U0345 and 21U0485.

Audience

Wage and Investment (W&I) Submission Processing Employees

Effective Date

(01-01-2022)

James L. Fish
Director, Submission Processing
Wage and Investment Division

Program Scope and Objectives

  1. PURPOSE/PROGRAM OBJECTIVES: This IRM provides campus Error Resolution and Rejects personnel procedures for correcting paper registers with Credit and Account Transfer transaction record errors identified in campus operations. These records contain payment transaction data (such as for Jeopardy, Prompt and Quick assessments, account adjustments and reactivation of retention register accounts).

    • Credit and Account Transfers are payment transaction documents and forms prepared by campus Accounting and or Accounts Management employees based on information received from Examination field personnel.

    • After Accounting and or Accounts Management receives this transaction information from Examination, they prepare payment transaction forms referred to as Credit and Account Transfers documents (see Paragraph (2) below)

    • Integrated Submissions and Remittance Processing (ISRP) transcription operators perform data entry of these records.

    • The Generalized Mainline Framework (GMF) computer runs receive these transcribed records from ISRP and sends them through a series of consistency and validity checks to establish data integrity and validity.

    • Records passing GMF validation post to the correct taxpayer Master File accounts (such as, Individual Master File (IMF), the Business Master File (BMF), and or the Individual Retirement Account (IRAF).

    • Error Resolution (Function 270) receives transaction records failing the GMF validity runs and performs research and correction to perfect these records for re-entry through ISRP and the GMF.

      Note:

      ERS and Rejects examiners are the campus personnel performing the research and correction on these records.

    • Documents which are not fully correctable by ERS/Rejects examiners) are returned to the originators for research, perfection and or revision before returning them to ERS for resolution.

    • ERS and Rejects send the corrected records through ISRP for data input and through GMF validation until the records pass GMF validity checks and post this information to the appropriate Master File account.

  2. Submission Processing (SP) campus Accounting Function personnel prepare the following forms used for processing Credit and Account Transfers:

    • Form 3413, Transcription List (Account Transfer-In)

    • Form 3552, Prompt Assessment Billing Assembly

  3. AUDIENCE: Wage and Investment (W and I) Submission Processing (SP) employees. This IRM is created for Error Resolution and Rejects personnel as follows:

    • ERROR RESOLUTION:

    • Supervisory Tax Examining Technician oversees correction of the Error Resolution System (ERS) program and reports to the Campus Chief of Input Corrections.

    • Lead Tax Examining Technicians review and approve subordinate employees’ work and report to the Supervisory Tax Examining Technician.

    • Tax Examining Technicians are campus tax examiners manning program Function 270 (Error Resolution) who correct payment records and report to the Lead Tax Examining Technician.

    • REJECTS:

    • Supervisory Tax Examining Technicians manage the Rejects department and report to the Campus Chief of Input Corrections.

    • Lead Tax Examining Technicians manage, review and approve subordinate employees work and report to the Supervisory Tax Examining Technician.

    • Tax Examining Technicians are campus examiners manning the Rejects program function and report to the Lead Tax Examining Technician.

  4. POLICY OWNER: The Director, Submission Processing, Wage and Investment Division, oversees and monitors all Submission Processing (SP) Headquarters and campus functions and operations processing Wage and Investment (W&I) income (and related) documents. This includes the production and operations of those internal organizations described in Paragraph (5) below.

  5. PROGRAM OWNERS: The following Submission Processing organizations share administrative and procedural responsibility for the Credit and Account Transfers program:

    • Accounting and Tax Payments Branch oversees related Headquarters personnel and campus Accounting and Data Control personnel preparing the Form 3413 and Form 3552.

    • Paper Processing Branch oversees related Headquarters personnel and campus Integrated Submissions and Remittance Processing (ISRP), Error Resolution System (ERS) and Rejects personnel who provide payment record transcription input and corrections, respectively.

  6. Primary Stakeholders: are Headquarters areas impacted by these procedures and or those that may influence the project, impacting a change in workflow, other duties, change in established time frames, and similar issues. They are as follows:

    • Small Business/Self-Employed (SBSE), Large Business and International (LB&I); Chief Financial Officer (CFO); Custodial Detail Database (CDDB), Statistics of Income (SOI); Tax Exempt/Government Entities (TE/GE); Compliance

Background

  1. Error Resolution System (ERS) functions resolve validity errors, field errors, consistency errors, and math errors in returns and other documents for posting to the Master File. Records fall out in ERS due to the Generalized Mainline Framework (GMF). The entries from Integrated Submissions and Remittance Processing (ISRP) transcription records are transferred to ERS fields.

  2. The GMF programming causes records to fall out to the Error Resolution paper registers if they fail to meet certain criteria, including (but NOT limited to):

    • Invalid characters in a field (such as, numeric instead of alpha characters)

    • Invalid length of field (such as, EIN (or SSN) with 8 digits instead of 9)

    • Invalid codes in field (such as, AC 009)

    • Consistency errors - Any valid field used in any computation where the result is inconsistent with (or contradictory to) any other valid field

    • Math errors - computer does math computation and it differs from the taxpayer’s amount

    • Invalid tax periods and eligibility for certain credits

  3. Process Flow After Accounting Prepares Form 3413 and Form 3552:

    • The ISRP system operators transcribe this information

    • The transcribed records are validated through the GMF programming runs

    • Campus ERS examiners correct records failing GMF validation on printed paper error registers.

    • ISRP transcribers and GMF validation runs re-input corrected records.

    • Validated records post to the correct Master Files.

  4. The following Submission Processing (SP) campuses process Credit and Account Transfers:

    • Austin (AUSPC) processes domestic and international Individual Master File (IMF) documents.

    • Kansas City (KCSPC) processes IMF documents.

    • Ogden (OSPC) processes domestic and international Business Master File (BMF) documents.

      Note:

      As of September 30, 2021, the Fresno Submission Processing Center (FSPC) no longer processes these documents.

  5. Program Goals: The program goals are to process cases correctly in a timely manner.

Authority

  1. Authority for these procedures is found in sources including IRC 6302 and the United States Code Title 31, Subtitle III, Financial Management:

    • IRC 6302, Mode or time of collection (Title 26)

    • USC Section 321, General Authority of the Secretary (Title 31)

    • USC Section 3301, General Duties of the Secretary of the Treasury (Title 31)

    • USC Section 3302, Custodians of Money (Title 31)

    • USC Section 3303, Designation of Depositories (Title 31)

    • USC Section 3702, Authority to Settle Claims (Title 31)

Responsibilities

  1. The Director, Submission Processing (Wage and Investment Division), is the executive responsible for overseeing and monitoring campus operations, and processing performance, and production trends set with W&I returns and related documents. This executive is also responsible for overseeing Headquarters and Submission Processing (SP) personnel, including campus employees, and for the effectiveness and efficiency of their operations.

  2. The Operations Manager oversees and monitors operational and production performance for their operation.

  3. The team manager/lead oversees, monitors campus production performance and ensures employees have the tools to perform their duties.

  4. The team employees follow instructions contained in this IRM and maintain updated IRM procedures.

Program Management and Review

  1. Program Goals: First line managers of personnel working Credit and Account Transfer transactions will conduct reviews of cases assigned to all employees to ensure effective operational internal controls.

  2. Program Reports: Below are a list of reports used to show receipts, production and inventory for the paper return process. These reports are used to report and monitor the daily and weekly status of the program to completeness:

    • PCC 6040, SC WP&C Performance and Cost Report

    • PCC 6240, SC WP&C Program Analysis Report

  3. Program Effectiveness: is measured by the following:

    • Embedded Quality Submission Processing (EQSP)

    • Balanced Measures

    • Managerial Reviews

  4. Annual Review: Federal Manager Financial Integrity Act (FMFIA).

Program Controls

  1. Accounting reports as determined by the Accounting and Data Controls Internal Revenue Manuals (IRMs) listed below:

    • IRM 3.17.30 , SC Data Controls

    • IRM 3.17.41, Accounting and Data Control, Excise Reporting

    • IRM 3.17.41.5.1, Operating Reports

    • IRM 3.17.46, Automated Non-Master File Accounting

    • IRM 3.17.64, Accounting Control General Ledger Policies and Procedures

  2. The reports for the Control Data Analysis are on the Control-D/Web Access services, which has a login program control. The following reports are used to show receipts, production and inventory for the paper return process and monitor daily and weekly status of the program to completeness:

    • PCC 6040, SC WP&C Performance and Cost Report

    • PCC 6240, SC WP&C Program Analysis Report

Terms/Definitions/Acronyms

  1. The following table contains a list of terms, acronyms, and or abbreviations used throughout this IRM.

    Acronyms and Abbreviations

    Acronyms and Abbreviations Definition
    AC Action Code
    ADP Automated Data Processing
    AFD Alpha-Numeric Field Designator
    AM Accounts Management
    AMA Automated Manual Assessment
    APO Army Post Office
    BMF Business Master File
    C&E Code and Edit
    CC Command Code
    C/GEN Computer Generated
    CR Credit Reduction
    DLN Document Locator Number
    Doc Code Document Code
    E-File Electronically File
    e.g. For Example
    EIN Employer Identification Number
    EOCU EO Compliance Unit
    etc. Et Cetera
    ID Identification or Identity
    IDRS Integrated Data Retrieval System
    ISRP Integrated Submission and Remittance Processing
    IMF Individual Master File
    IRC Internal Revenue Code
    IRS Internal Revenue Service
    LB&I Large Business and International
    LCU Large Corporate Underpayment
    MeF Modernized Electronic Filing
    MFT Master File Tax
    MMDDYY Month Month Day Day Year Year
    NAICS North American Industry Classification System
    N/A Not Applicable
    OSPC Ogden Submission Processing Center
    P.O. Post Office
    RRA 98 Internal Revenue Service Restructuring and Reform Act of 1998
    SB/SE Small Business/Self-Employed
    SP Submission Processing
    SSN Social Security Number
    TAS Taxpayer Advocate Service
    TBOR Taxpayer Bill of Rights
    TC Transaction Code
    TE Tax Examiner
    TE/GE Tax Exempt/Government Entities
    TETR Telephone Excise Tax Refund
    TIN Taxpayer Identification Number
    TPE Tax Period Ending
    TY Tax Year
    U.S. United States
    USPS United States Postal Service
    W&I Wage and Investment
    ZIP Zone Improvement Plan
     

Related Resources

  1. Initial processing of the requests for these transfers and preparation of the input documents is described in the following Internal Revenue Manuals (IRMS):

    • IRM 3.17.243, Miscellaneous Accounting

    • IRM 3.17.244, Manual Assessments

    • IRM 3.17.10, Dishonored Check File (DCF) and Unidentified Remittance File (URF)

    • IRM 3.17.21, Credit and Account Transfers

    • IRM 3.17.46, Automated Non-Master File Accounting

    • IRM 3.17.220, Excess Collections File (XSF)

    • IRM 3.24.21, Credit and Account Transfers

    • Learning and Education materials (i.e., coursebooks and job aids)

  2. This IRM provides instructions for correcting the following input documents:

    1. Form 3413, Transcription List (Account Transfer-In); and,

    2. Form 3552, Prompt Assessment Billing Assembly.

General Error Correction Procedures

  1. This section describes the various error conditions, how they are identified on the registers, the action codes, and how they are used to resolve these conditions.

Error Register

  1. General descriptions of the contents, format and correction method of the error register are provided in IRM 3.12.37, IMF General Instructions or IRM 3.12.38, BMF General Instructions.

  2. Action Codes- every action taken on the error register requires the use of an action code. The Action Code is entered to the left of the section number being worked. The valid action codes for the error register are as follows:

    1. Action Code 3- (See Figure 3.12.21-1.)

      Note:

      Issue a Form 4227, Intra-SC Reject or Routing Slip, and notate on the form the error you need corrected.

      Figure 3.12.21-1

      This is an Image: 33670001.gif

      Please click here for the text description of the image.

    2. Action Code 4- (See Figure 3.12.21-2.)

      Note:

      Action Code 4 is not valid for Section 01.

      Figure 3.12.21-2

      This is an Image: 33670002.gif

      Please click here for the text description of the image.

    3. Action Code 5- (See Figure 3.12.21-3.)

      Figure 3.12.21-3

      This is an Image: 33670003.gif

      Please click here for the text description of the image.

    4. Action Code 6- (See Figure 3.12.21-4.)

      Figure 3.12.21-4

      This is an Image: 33670004.gif

      Please click here for the text description of the image.

    5. Action Code 7- (See Figure 3.12.21-5.)

    Figure 3.12.21-5

    This is an Image: 33670005.gif

    Please click here for the text description of the image.

Types of Error Conditions

  1. The types of error conditions you will encounter include validity, terminus, extraneous section, and missing section. This section will provide descriptions of and resolution instructions for each condition.

Validity Errors
  1. Validity errors are identified either because a field, which must have data, is blank, or because the computer identified invalid characters within that field. Fields are validity checked to ensure correct data before transmittal to the master file. Each field that is found invalid is identified on the register with an asterisk (*) before the alpha-field designator.

  2. Correct as follows:

    1. Compare the data on the register with the document being processed.

    2. Correct any transcription errors.

    3. If no corrections are necessary, use Action Code 7.

Terminus Errors
  1. A terminus error results when there is a non-numeric character in a numeric field, or when the format of the section is incorrect.

  2. Terminus errors are identified by two asterisks (**) to the left of the section number. (See Figure 3.12.21-6.)

    Figure 3.12.21-6

    This is an Image: 33670006.gif

    Please click here for the text description of the image.

  3. Correct as follows:

    1. Compare the data on the register with the document being processed.

    2. Correct any transcription errors.

    3. If no corrections are necessary, use Action Code 7.

Extraneous Sections
  1. Extraneous sections are identified by a single pound (#) sign in front of the section. (See Figure 3.12.21-7.)

    Figure 3.12.21-7

    This is an Image: 33670007.gif

    Please click here for the text description of the image.

  2. Correct as follows:

    1. Compare the data on the register with the document being processed.

    2. Correct any transcription errors.

    3. If the section is truly not needed to process the record, delete the section with Action Code 4.

    Note:

    SECTION 01 IS A REQUIRED SECTION AT ALL TIMES. DO NOT ATTEMPT TO DELETE SECTION 01 WITH ACTION CODE 4.

Missing Sections
  1. Missing sections are identified by an asterisk to the left of the section number with the alpha-field designator for the section printed on the error register. See Figure 3.12.21-8.

    Figure 3.12.21-8

    This is an Image: 33670008.gif

    Please click here for the text description of the image.

  2. Correct as follows:

    1. Compare the data on the register with the document being processed.

    2. Correct any transcription errors.

  3. If a section not identified as a missing section must be added, use Action Code 5.

    1. Enter on the register only the fields which will contain data.

    2. The fields must be entered on the register in alphabetical order by alpha-field designator.

Invalid Correction Attempt
  1. An invalid correction attempt is indicated by a "AA" printed to the right of the DLN (Document Locator Number) in the title line of the error register. For a complete description of invalid correction attempts, see IRM 3.12.37, IMF General Instructions, or IRM 3.12.38, BMF General Instructions.

  2. Correct as follows:

    1. Correct all errors identified on the error register as if no attempt had been made to correct it before. If necessary, examine the corrections on the prior error register.

    2. If all the fields are correct on the error register, enter an Action Code 7 to the left of section 01 on the error register.

Input Documents - General Explanation

  1. This section describes the concept of non-ADP as it relates to the various files’ document: Individual Master File (IMF), Business Master File (BMF), and Individual Retirement Account File (IRAF). Also described are the input documents (i.e., Form 3413, Transcription List (Account Transfer-in), and Form 3552, Prompt Assessment Billing Assembly, used to re-establish accounts to or transfer assessments to or between these files.

Non-ADP (Automated Data Processing) Document

  1. A non-ADP (Automated DATA Processing) document is a document processed for a tax period which ended before the Automated Data Processing (ADP) system was in place for a particular document.

  2. When a document is for a non-ADP period, reject, using Action Code 3. Prepare Form 4227, Intra-SC Reject or Routing Slip, and process as Non-Master File (NMF).

Form 3413 - Transcription List

  1. Form 3413, Transcription List (Account Transfer-In), with Doc Code 51 or 52 is used to transfer a list of all transaction codes, dates and amounts on a single record into the Master File. All money amounts are entered in dollars and cents.

  2. These documents are prepared for accounts which have been either on Non-Master File (NMF) or had been previously on the master file and were transferred out using Transaction Code (TC) 400 (Account Transfer-Out). (See Figure 3.12.21-9a) See IRM 3.12.37, IMF General Instructions or IRM 3.12.38, BMF General Instructions.

    Figure 3.12.21-9a

    This is an Image: 33670009.gif

    Please click here for the text description of the image.

    Figure 3.12.21-9b

    This is an Image: 33670038.gif

    Please click here for the text description of the image.

Form 3552 - Prompt Assessment Billing Assembly

  1. Form 3552, Prompt Assessment Billing Assembly, is used to transfer Quick, Prompt, and Jeopardy Assessments to the BMF, IMF, or IRAF. All money amounts are entered in dollars and cents. See Figure 3.12.21-10.

    Figure 3.12.21-10

    This is an Image: 33670010.gif

    Please click here for the text description of the image.

IRM Deviation Procedures

  1. IRM deviations must be submitted in writing following instructions from IRM 1.11.2.2, Internal Management Documents System - Internal Revenue Manual (IRM) Process, IRM Standards, and elevated through correct channels for executive approval.

Section 01

  1. This section provides descriptions of the fields and correction procedures for Section 01 of the register.

Section Fields A Through X Description

  1. The alpha-field designators, field lengths (maximum length for variable fields), and the field titles are shown below:

    Field Field Length (+/−) Field Title
    01-A 4   Name Control
    01-B 9   EIN or SSN and TIN Type

    Exception:

    The TIN Type is corrected in Field 01-K.

    01-C 2   MFT Code (Master File Tax Account Code)
    01-D 6   Tax Period
    01-E 8   Date of Transfer (or, Transfer in Date)
    01-F 8   23C Date of Assessment
    01-G 3   Original Assessment Transaction Code
    01-H 12 +/− Original Assessment Transaction Amount
    01-I 15 + Transfer-in Amount (or Balance Transferred-in)
    01-J 8   Agreement Date
    01-K 1   TIN Type is located on Form 3413 under Item B, Section 01 ("EIN or SSN and TIN Type" )
    01-L 8   Correspondence Received Date (located on Form 3413 as Item K, Section 01)
    01-M 3   Reference Number
    01-N 13 + Reference Number Amount
    01-O 8   2% Interest Date (located on Form 3413 as Item L, Section 01)
    01-P 8   Interest To Date
    01-Q 8   Interest Computation Date
    01-R 3   Plan/Report Number (MFT 46/74/76/85/86 Only)
    01-S 8   Excess Fringe Benefit Year (located on Form 3413 as Item U, Section 01)
    01-T 8   Reversion Date (located on Form 3413 as Item O, Section 01)
    01-U 6   Plan Year Ending Date (located on Form 3413 as Item S, Section 01)
    01-V 8   4980f Amendment Date (located on Form 3413 as Item V, Section 01)
    01-W 8   Form 8288 Trans Date (located on Form 3413 as Item T, Section 01)
    01-X 9   BMF TIN

    Note:

    Refer to the individual text instructions for the most current names/designations of Section 01, Fields A through X.

Correction Procedures - Section 01

  1. This section describes field validity criteria and correction procedures for Fields A through X in Section 01.

Field 01-A - Name Control (Validity Checks)
  1. The Name Control (Field 01-A) is found on the following forms as follows:

    • Form 3413, Transcription List (Account Transfer-in): "Item A" (Section 01) displays the "Name Control" .

    • Form 3552, Prompt Assessment Billing Assembly: The "Name Control" is found in the upper right corner of this form, beneath the "Notice Date" , OR it may be determined from the first line (name line) of the "Taxpayer" box on the upper left portion of the form.

  2. This field MUST always be present and can contain up to four characters.

  3. For BMF documents with a Social Security Number (SSN) (MFT 51, 52, 58, and 78), the first position must be alphabetic. The remaining characters can be alphabetic, hyphen or blank. No character may follow a blank.

  4. For BMF documents with an Employer Identification Number (EIN), the first character must be alphabetic or numeric. The remaining characters can be alphabetic, numeric, hyphen, ampersand, or blank. No character may follow a blank.

  5. For IMF and IRAF documents, the first character must be alphabetic. The remaining characters can be alphabetic, hyphen, or blank. No character may follow a blank.

Field 01-A - Name Control (Correction Procedures)
  1. Compare the document with Field 01-A. Correct any transcription errors using Action Code 6.

  2. Research Integrated Data Retrieval System (IDRS) for a valid name control, using correct Command Codes.

    1. If a valid name control is found, correct the name control on the document and on the register. See Figure 3.12.21-11.

      Figure 3.12.21-11

      This is an Image: 33670011.gif

      Please click here for the text description of the image.

    2. If a valid name control is not found, reject the document with Action Code 3.

Field 01-B - EIN (Employer Identification Number) or SSN (Social Security Number) and TIN Type (Taxpayer Identification Number Type) (Validity Checks)
  1. The Taxpayer Identification Number (TIN) MUST always be present and MUST contain 9 digits.

    Note:

    Form 3413 ONLY: The "EIN or SSN and TIN Type" information is found in Item B (Section 01). The "EIN or SSN and TIN Type" field is not contained on the Form 3552. Form 3552 Only: The Taxpayer Identification Number is located in the upper right part of the Form 3552, beneath the Name Control information.

  2. It can't be all zeroes (0) or all nines (9).

  3. IMF (Individual Master File) and IRAF (Individual Retirement Account File) documents will contain social security numbers (SSNs).

    Note:

    The IRAF (as a separate Master File) was retired in 2004. All references to "MFT 29" are what were previously referred to as IRAF.

  4. BMF documents will have a 9-digit taxpayer identification number which can be a Social Security Number (SSN) or an Employer Identification Number (EIN).

    1. SSNVs-MFTs 51 (Form 709, United States Gift (and Generation-Skipping Transfer) Tax Return), and 52 (Form 706, U.S. Estate Tax Return), will always have an SSNV.

    2. MFTs 46, 58, and 78 with a TIN Type (Field 01-K) of "0" will have an SSNV. (See Figure 3.12.21-12.) If the TIN Type is blank, the TIN is an EIN.

      Note:

      The SSNV is used to identify the TIN of a Business Master File (BMF) entity posting to the BMF with a Social Security Number (SSN) as its TIN. If given an SSN, adding the “V” to the end (i.e., XXX-SS-XXXXV) will pull up the BMF account associated with that MFT.

      Figure 3.12.21-12

      This is an Image: 33670012.gif

      Please click here for the text description of the image.

    3. EINs-must be all numeric and the first two digits may not be 00, 07 through 09, 17 through 19, 28, 29, 49, 78, 79, or 89.

Field 01-B - EIN or SSN and TIN Type - Correction Procedures
  1. Compare Field 01-B with the document. Correct any transcription errors.

    Exception:

    Only the EIN (Employer Identification Number) or SSN (Social Security Number) are corrected in Field 01-B. The TIN Type must be corrected in Field 01-K. see IRM 3.12.21.4.2.17.

  2. If the document was transcribed correctly and the taxpayer identification number contains other than 9 digits, research via IDRS, using Command Codes NAMEI and NAMES (SSNs) and NAMEB and NAMEE (EINs). If you are unable to locate a valid TIN, reject the document with Action Code 3.

  3. If the document is correct as transcribed, compare the document with the MFT code (Field 01-C) and the TIN Type (Field 01-K), i.e., SSN for IMF (Individual Master File), IRAF and MFT 51, 52, 58, and 78 and EIN for BMF. If the document has been numbered incorrectly reject with Action Code 3 for renumbering. See Figure 3.12.21-13.

    Figure 3.12.21-13

    This is an Image: 33670013.gif

    Please click here for the text description of the image.

Field 01-C - Master File Tax Account Code-MFT (Validity Checks)
  1. The Master File Tax Account (MFT) Code is found in Item C (Section 01), Page 1, Form 3413. It is also located in the MFT box on the upper left part of the Form 3552.

  2. This is a two-digit field that MUST be present.

  3. The MFT is pre-printed or manually entered during the preparation of the document.

  4. The MFT must be compatible with the tax class in the DLN.

Field 01-C - Master File Tax Account Code-MFT (Correction Procedures)
  1. Compare Field 01-C with the document. Correct any transcription errors.

  2. If the MFT is not present, determine the correct code using Exhibit 3.12.21-4, MFT and Tax Class Chart, and the criteria below. Enter the data in Field 01-C, using Action Code 6.

    1. If the document is IMF, the MFT must be 30, 31, 35, 55, 65 or 82.

    2. If the document is IRAF, the MFT code must be 29.

    3. If the document is BMF, the MFT code must be 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 33, 34, 36, 37, 40, 43, 44, 46, 47, 49, 50, 51, 52, 55, 58, 60, 61, 62, 63, 64, 67, 74, 75, 76, 77, 78, 79, 83, 85, or 86.

  3. Use the information in the table provided below to determine if the document was numbered correctly. If the MFT was transcribed correctly, compare the MFT and the tax class of the DLN (tax class is the third digit of the DLN). See Figure 3.12.21-14.

    Figure 3.12.21-14

    This is an Image: 33670014.gif

    Please click here for the text description of the image.

    MFT TAX CLASS Valid Section Presence
    01 1 01, 02-19, 30-33, 36, 40
    02 3 01, 02-19, 20-23, 30-33, 36
    03 4 01, 02-19, 30-33, 36, 37-39
    04 1 01, 02-19, 30-33
    05 2 01, 02-19, 20-23, 30-33, 36
    06 2 01, 02-19, 30-33, 36
    07 3 01, 02-19, 30-33, 36
    08 1 01, 02-19, 20-23, 30-33, 36
    09 7 01, 02-19, 30-33, 36, 40
    10 8 01, 02-19, 30-33, 36, 41, 42-46
    11 1 01, 02-19, 30-33, 36, 40
    12 1 01, 02-19, 30-33, 36, 40
    13 3 01, 02-19, 30-33, 36
    14 1 01, 02-19, 30-33, 36, 40
    15 2 01, 02-19, 30-33
    16 1 01, 02-19, 30-33, 36, 40
    17 1 01, 02-19, 20-23, 30-33, 36
    29 2 01, 02-19, 30-33, 36, 37
    30, 31 2 01, 02-19, 20-23, 30-33, 36
    33 3 01, 02-19, 20-23, 30-33, 36
    34 3 01, 02-19, 20-23, 30-33, 36
    35, 65 2 01, 02-19, 20-23, 30-33, 36
    36 4 01, 02-19, 30-33, 36
    37 4 01, 02-19, 30-33, 36
    40 4 01, 02-19, 30-33, 36
    43 4 01, 02-19, 30-33, 36
    44 4 01, 02-19, 30-33, 36
    46 3 01, 02-19, 20-23, 30-33
    47 4 01, 02-19, 30-33, 36
    49 4 01, 02-19, 30-33, 36-39
    50 4 01, 02-19, 30-33, 36-39
    51 5 01, 02-19, 30-33, 36
    52 5 01, 02-19, 30-33, 36
    55 2 01, 02-19, 30-33, 36
    58 4 01, 02-19, 30-33, 36
    60 4 01, 02-19, 30-33, 36
    61 4 01, 02-19, 30-33, 36, 37-39
    62 4 01, 02-19, 30-33, 36
    63 4 01, 02-19, 30-33, 36
    64 4 01, 02-19, 30-33, 36
    65 2 01, 02-19, 20-23, 30-33, 36
    67 4 01, 02-19, 30-33, 36
    74 4 01, 02-19, 30-33, 36, 37-39
    75 4 01, 02-19, 30-33, 36, 37-39
    76 4 01, 02-19, 30-33, 36, 37-39
    77 5 01, 02-19, 30-33, 36
    78 5 01, 02-19, 30-33, 36
    79 4 01, 02-19, 30-33, 36, 37-39
    82 2 01, 02-19, 30-33
    83 3 01, 02-19, 30-33
    85 3 01, 02-19, 20-23, 30-33
    86 3 01, 02-19, 20-23, 30-33

  4. If the document was numbered incorrectly, reject the document for renumbering, using Action Code 3.

  5. If the MFT was transcribed incorrectly and the MFT on the document is compatible with the tax class in the DLN, correct Field 01-C.

  6. IF THE MFT IS CORRECTED TO 03, 50, OR 61 ON A DOC CODE 51 RECORD, BE SURE THE ABSTRACT REQUIREMENTS OF SECTIONS 36-39 ARE MET BY ADDING SECTIONS IF NECESSARY. (See Table IRM 3.12.21.4.2.8.)

  7. IF THE ABSTRACT REQUIREMENTS ARE NOT IN THE SECTION 36-39 REJECT, USE ACTION CODE 3. (See Figure 3.12.21-15.)

    Figure 3.12.21-15

    This is an Image: 33670015.gif

    Please click here for the text description of the image.

Field 01-D - Tax Period (Validity Checks)
  1. The Tax Period is found in Item D (Section 01), Page 1, Form 3413. It is also located in the Tax Period box on the upper left part of the Form 3552 (to the right of the MFT box).

  2. This field MUST be present, contain six digits, and be all numeric.

  3. It is edited in YYYYMM format. The first four positions represent the year, and the last two positions represent the month of the tax period.

  4. The month in the tax period must be 01 through 12.

    Exception:

    MFT 52 (Form 706) is valid with a tax period of 000000.

  5. MFTs 58, 60, 61, 62, 63, and 64 use the tax period beginning date as the tax period. All other MFTs use the tax period ending date as the tax period with the exception of MFT 52 (see IRM 3.12.21.4.2.7(4) above).

  6. Field 01-D (Tax Period) and Field 01-C (Master File Tax Account Code) will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK: MFT CODE AND TAX PERIOD

    Field 01-C (MFT CODE) will appear invalid if: AND Field 01-D (TAX PERIOD):
    Field 01-D will appear invalid if MFT is 30 or 31 The tax period is before 196212.
    Field 01-D will appear invalid if MFT is 29 The tax period is before 197512.
    Field 01-D will appear invalid if MFT is 55 The tax period is before 197512.
    Field 01-D will appear invalid if MFT is 35 The tax period is before 201412 (also note the following conditions):
    • Valid for Tax Period 201812 and prior

    • Invalid for Tax Years 201912 and later

    • PRN 692 and Transaction Code TC-240 or TC-241 or TC-290 or TC-291 must be present

    Field 01-D will appear invalid if MFT is 43 The tax period is before 201512.
    Field 01-D will appear invalid if MFT is 65 The tax period is before 201412.
    Field 01-D will appear invalid if MFT is 82 The tax period is before 201712.
    Field 01-D will appear invalid if MFT is 83 The tax period is before 201712.
     

  7. Field 01-D (Tax Period) will appear invalid, along with Fields 20A-E or I (Transaction Code), if the tax period is other than 197810 through 198011 and the transaction code is 63X. 63X equals 630, 632, 636, and 637 (for MFT 02, 05, 30, 31, 33, and 34 only). (See Figure 3.12.21-16.)

    Figure 3.12.21-16

    This is an Image: 33670016.gif

    Please click here for the text description of the image.

    .

  8. Field 01-D (Tax Period), Field 01-C (Master File Tax Account Code), AND Field 01-M (Reference Number), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECKS: TAX PERIOD, MFT CODE, AND REFERENCE NUMBER

    Field 01-D (Tax Period): Field 01-C (MFT): And Field 01-M (Reference Number):
    The tax period is prior to 198909 The MFT Code is not 29 The Reference Number is 686 (See Figure 3.12.21-17).
    Confirmed 09032021
    The tax period is prior to 199012 The MFT is 13 The Reference Number is 649
    Confirmed 09032021
    The tax period is prior to 199012 The MFT is 13 The Reference Number is 678
    The tax period is prior to 199712 The MFT is 55 The Reference Number is 627
    Confirmed 09032021
    The tax period is prior to 200209 The MFT is 13 or MFT 55 The Reference Number is 708 or 709
    Confirmed 09032021
    The tax period is prior to 200705 The MFT is 30 The Reference Number is 687
    Confirmed 09032021
    The tax period is prior to 201512 The MFT is 01, 02, 03, 04, 05, 07, 09, 10, 11, 12, 14, 15, 16, 31, 33, 34, 37, 38, 39, 40, 41, 42, 43, 44, 50, 51, 52, 60, 63, 64, 77 OR 78 The Reference Number is 687
    Confirmed 09032021
    The tax period is prior to 200912 The MFT is 30 The Reference Number is 677 or 706
    Confirmed 09032021
    The tax period is prior to 201003 The MFT is 46 The Reference Number is greater than 291 and less than 296
    Confirmed 0903 and 09172021
    The tax period is prior to 201003 The MFT is either 02, 03, 05, 06, 07 30, 31, 34, 51, 52, 55 The Reference Number is 683
    Confirmed 09032021
    The tax period is prior to 201003 The MFT is either 30 or 31 The Reference Number is 700
    Confirmed 09032021
    The tax period is prior to 201003 The MFT is either 30 or 31 The Reference Number is 710
    Confirmed 09032021
    The tax period is not equal to or within 201112 through 202203 The MFT is 01 The Reference Number is 290; or,
    Confirmed 09032021
    The tax period is not equal to or within 201112 through 202212 The MFT is either11 or 14 The Reference Number is 290
    Confirmed 09032021
    The tax period is prior to 201409 The MFT is 79 The Reference Number is 290 or 298.
    Confirmed 09202021
    The tax period is prior to 201612. The MFT is 13. The Reference Number is 700 or 710.
    Confirmed 09032021
    The tax period is prior to 201701.(and month (MM) of Tax Period is not 03, 06, 09, or 12) The MFT is 13. The Reference Number is 519.
    Confirmed 09032021
    The tax period is prior to 201701 The MFT is BMF MFT 05 The Reference Number is 519
    The tax period is before 201801 The MFT is 13 The Reference Number is 693.
    Confirmed 09032021
    The tax period is before 201801 The MFT is 13 The Reference Number is 694.
    Confirmed 09032021
     
    1. Figure 3.12.21-17

      This is an Image: 33670017.gif

      Please click here for the text description of the image.

  9. Field 01-D (Tax Period), Field 01-C (Master File Tax Account Code), Field 01-G (Transaction Code), AND Field 01-M (Reference Number), will appear invalid (along with the Transaction Codes) if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECKS: REFERENCE NUMBER, TRANSACTION CODE, MFT, AND TAX PERIOD

    Field 01-M (REFERENCE NUMBER): Field 01-G (TRANSACTION CODE):

    Field 01-C (MFT):

    Field 01-D (Tax Period):
    If the Reference Number is 692AND The Transaction Code in Section 01 is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANKS, 190, 240, 241, 290 and or 291,AND The MFT is 35 AND The Tax Period is equal to or before 201812
    Confirmed 09272021
    If the Reference Number is 692 AND The Transaction Code in Section 01 is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANKS, 190, 240, 241, 290 and or 291, AND The MFT is 65 AND The Tax Period is equal to or before 201812
    Confirmed 09272021
    If the Reference Number is EITHER700OR710 The Transaction Code in Section 01 EITHER is 240 or 290AND the Transaction Code in Section 02-19 EITHER is BLANKS, TC-190 or TC 240 or TC 241 and or TC-29X through 30X The MFT is 55 The tax period is prior to 201003
    Confirmed 09032021
    If the Reference Number is 707 The Transaction Code in Section 01 EITHER is TC-240 or TC-290AND the Transaction Code in Section 02-19 EITHER is BLANKS, TC-190 or TC- 240 or TC- 241, TC-290 and or TC-291 The MFT is BMF MFT 05 The tax period is prior to 201701
    Confirmed 09032021
    If the Reference Number is 707 The Transaction Code in Section 01 EITHER is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANKS, TC-190 or TC- 240 or TC- 241, TC-290 and or TC-291 The MFT is IMF MFT 30 The tax period is prior to 201701
    Confirmed 09032021
    If the Reference Number is 707 The Transaction Code in Section 01 EITHER is TC-240 or TC-290 AND the Transaction Code in Section 02-19 EITHER is BLANKS, TC-190 or TC- 240 or TC-241, TC-290 and or TC-291 The MFT is IMF MFT 31 The tax period is prior to 201701
    (Confirmed 09032021)
     

  10. FORM 3552 ONLY (displaying TC-767 and other TCs): Field 01-C (Master File Tax Account Code), Field 01-D (Tax Period), along with the Transaction Codes will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECKS (FORM 3552): TC-767, MFT, TAX PERIOD AND TRANSACTION CODE

    FORMAT CODE (for Form 3552)
    TRANSACTION CODE:


    AND Field 01-C (MFT):


    AND Field 01-D (Tax Period):


    AND TRANSACTION CODE):
    Form 3552 (Format Code 325 or 326) IF Transaction Code in Section 02-19 is equal to 767AND MFT Code is 01, AND The Tax Period EITHER is 202003, 202006, 202009, OR 202012 AND Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308 AND the Transaction Code in Sections 02-19 EITHER is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309

    (CONFIRMED 09082021)
    Form 3552 (Format Code 325 or 326) OR, IF Transaction Code in Section 02-19 is equal to 767AND The MFT is EITHER09, 11, or 14AND The Tax Period IS 202012 AND Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308 AND the Transaction Code in Sections 02-19 EITHER is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309

    (CONFIRMED 09082021)
     

  11. FORM 3413 ONLY (displaying TC-766 or TC-767 and other TCs): Field 01-D (Tax Period),Field 01-C (Master File Tax Account Code),Field 01-M (Reference Number), along with the Transaction Codes will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECKS (FORM 3413): TC-766 OR TC-767, TAX PERIOD, MFT, TRANSACTION CODE, REFERENCE NUMBER

    FORMAT CODE (for Form 3413)
    TRANSACTION CODE:

    Field 01-D (TAX PERIOD)

    Field 01-C (MFT)

    TRANSACTION CODE
    Field 01-M (REFERENCE NUMBER)
    Form 3413 (Format Code 025 or 026) IF Transaction Code in Section 02-19 is equal to 766 or 767AND Tax Period is EITHER 202003, 202006, 202009, OR 202012 AND MFT Code is 01, AND Transaction Code in Section 01 is EITHER, 150, 290, 294, 298, 300, 304 or 308, AND Transaction Code in Section 02-19 EITHER is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and or 309 AND Reference Number equals 280, 296, or 299
    (Form 3413 (Format Code 025 or 026)) OR IF Transaction Code in Section 02-19 is equal to 766 or 767AND Tax Period is 202012 AND the MFT is EITHER09, 11, or 14AND The Transaction Code in Section 01 is EITHER, 150, 290, 294, 298, 300, 304, or 308, AND Transaction Code in Section 02-19EITHER is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309, AND Reference Number equals 280, 296, or 299
     

  12. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), Field 01-G (Transaction Code) AND Field 01-H (Transaction Amount) will appear invalid if EITHER of the following conditions (as displayed in the table below) are NOT correct:

    CONSISTENCY CHECKS: REFERENCE NUMBER, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT

    Field 01-M (REFERENCE NUMBER) Field 01-C (MFT Code) Field 01-G (Transaction Code) Field 01-H (Transaction Amount)
    If Reference Number is 722 AND The MFT Code equals 02, 06 OR 07, AND Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or TC 301 AND Transaction Amount for 290, 291, 300, and or 301 and their amounts can only be zero
    (CONFIRMED 10202021)Valid for all tax periods.
    OR IF Reference Number is 723 AND MFT Code equals 02 or 06AND Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301 AND Transaction Amount for 290, 291, 300, and or 301 can only be zero
    (CONFIRMED 10202021); Valid for all tax periods.
    IF Reference Number is 724AND MFT Code is 05 Transaction Code in Section 01 is 160 OR Transaction Code in Section 02-19 is 160, AND Transaction Amount can be any amount.
    (CONFIRMED 10202021)
     

  13. Field 01-M (Reference Number), Field 01-N (Reference Number Amount), Field 01-C (Master File Tax Account Code), Field 01-G (Transaction Code) AND Field 01-H (Transaction Amount) will appear invalid if EITHER of the following conditions (as displayed in the table below) are NOT correct:

    CONSISTENCY CHECK: REFERENCE NUMBER, REFERENCE AMOUNT, MFT CODE, TRANSACTION CODE, TRANSACTION AMOUNT

    Field 01-M (Reference Number) Field 01-N (Reference Number Amount)

    Field 01-C (MFT Code)

    Field 01-G (Transaction Code)

    Field 01-H (Transaction Amount)
    IF Reference Number is 722 OR 723 AND The Reference Number Amount is less than or equal to zero

    Note:

    No MFTs were listed in this FSP Process

    Transaction Code in Section 01 is 160 OR Transaction Code in Section 02-19 is 160, AND Transaction Amount may be any amount..
    (CONFIRMED 10202021)
     

  14. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), Field 01-D (Tax Period), Field 01-G (Transaction Code) AND Field 01-H (Transaction Code Amount) will appear invalid if EITHER of the following conditions (as displayed in the table below) are NOT correct:

    CONSISTENCY CHECK: REFERENCE NUMBER, MFT, TAX PERIOD, TRANSACTION CODE, TRANSACTION AMOUNT

    Field 01-M (Reference Number) Field 01-C (MFT Code) Field 01-D (Tax Period) Field-01 G (Transaction Code) Field 01-H (Transaction Amount)
    IF Reference Number is 724, AND MFT Code is MFT 02, MFT 05, OR MFT 06, AND Tax Period is equal to or greater than 201712, AND Transaction Code in Section 01 is TC 290 or TC 300 AND Transaction Code in Section 02-19 is BLANKS, 240, 241, 290, 291, 300 and or 301, THEN Transaction Amount may be any amount.
    (CONFIRMED 09142021)
     

  15. Field 01-D (Tax Period), will appear invalid, along with Field 01-M (Reference Number) if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK: TAX PERIOD AND REFERENCE NUMBER

    Field 01-D (Tax Period): AND Field 01-M (Reference Number):
    Prior to 201006 The Reference Number is 682
    Prior to 198709 The Reference Number is 685
    Confirmed 09032021
    Prior to 201006 The Reference Number is 780 or 781
    Confirmed 09082021
     

  16. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), AND Field 01-N (Reference Number Amount), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK: REFERENCE NUMBER, MFT, REFERENCE NUMBER AMOUNT

    Field 01-M (Reference Number): Field 01-C (MFT): AndField 01-N (Reference Number Amount):
    Reference Number is 528 MFT is 55 Reference Number Amount is greater than $10,000
    Confirmed 09082021
     

  17. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), Field 01-N (Reference Number Amount) and Field 01-D (Tax Period), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK: REFERENCE NUMBER, MFT, REFERENCE NUMBER AMOUNT, TAX PERIOD

    Field 01-M (Reference Number):

    Field 01-C (MFT):
    Field 01-N (Reference Number Amount):
    Field 01-D (Tax Period):
    When Reference Number is658 AND MFT Code is 13 Reference Number Amount can't exceed $5,000.00
    • The Tax Period can't be prior to 199812, OR

    • the Month of Tax Period can't be other than 12.

    CONFIRMED 09022021
     

  18. Field 01-M (Reference Number), Field 01-N (Reference Number Amount) and Field 01-D (Tax Period), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK - REFERENCE NUMBER, REFERENCE NUMBER AMOUNT, AND TAX PERIOD

    Field 01-M (Reference Number): Field 01-N (Reference Number Amount):
    Field 01-D (Tax Period):
    If Reference Number is 678. The dollar amount can't be greater than $50,000.00.
    • The Tax Period is earlier than 198512, OR

    • the Month of Tax Period can't be other than "12" .

    CONFIRMED 09142021.
     

  19. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), Field 01-D (Tax Period), and Field 01-N (Reference Number Amount), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECK - REFERENCE NUMBER, MFT, TAX PERIOD OR REFERENCE NUMBER AMOUNT

    Field 01-M (Reference Number):

    Field 01-C (MFT):

    Field 01-D (Tax Period):
    Field 01-N (Reference Number Amount):
    If Reference Number is 663, MFT is 13, AND the Tax Period is before 200008, OR the Reference Number Amount is greater than $50,000, ALL three fields i.e., Fields 01-M, 01-C, and 01-D OR Fields 01-M, 01-C, and 01-N will appear invalid. CONFIRMED 09022021.
     

  20. Field 01-M (Reference Number), Field 01-C (Master File Tax Account Code), and Field 01-D (Tax Period), along with the Transaction Code (TC), will appear invalid if EITHER of the following conditions (as displayed in the table below) are not correct:

    CONSISTENCY CHECKS: REFERENCE NUMBER, MFT, TRANSACTION CODE, AND TAX PERIOD

    Field 01-M (Reference Number):

    Field 01-C (MFT):

    TRANSACTION CODE (TC)

    Field 01-D (Tax Period):
    IF the Reference Number is 700 the MFT is 55 The Transaction Code in Section 01 is EITHER TC-240 or TC-290 AND Section 02-19 is BLANKS, TC-190, 240 or 241 and or 29X or 30X If the tax period is is equal to or greater than 201003
    (Confirmed 09272021)
    (Confirmed 09272021)
    IF the Reference Number is 710 the MFT is 55, The Transaction Code in Section 01 is EITHER TC-240 or TC-290 AND Section 02-19 is BLANKS, TC-190, 240 or 241 and or 29X or 30X If the tax period is is equal to or greater than 201003
    (Confirmed 09272021)
    IF the Reference Number is 682 the MFT is EITHER02, 05, 06, or 34 The Transaction Code in Section 01 is EITHER, 290, 294, 298, 300, 304, or 308, AND Transaction Code in Section 02-19EITHER is BLANKS, 240, 241, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and or 309 Tax Period is equal to or greater than 201712

    (Confirmed 09012021)
     

Field 01-D - Tax Period (Correction Procedures)
  1. Correct as follows:

    1. Compare the register with the document.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record with Action Code 3.

    4. Attach Form 4227, Intra-SC Reject or Routing Slip.

    5. Notate "invalid tax period" , and route to the Accounting function (for contact with originator for research and or correction)..

  2. The tax period can't be later than the current processing month plus one year or earlier than the beginning tax period indicated in the table found in Exhibit 3.12.21-1 (Valid Tax Periods) for the specific MFT being processed.

    MFT-CD BMFTX/PRD END TX/PD EARLIEST DATE ALLOWED MM-LIMITS
    01 196203 YYYY12 TAX-PRD minus 2 months 3, 6, 9,12
    02 196112 YYYY12 TAX-PRD minus 11 months 1-12
    03 196203 YYYY12 TAX-PRD minus 2 months 3,6,9,12
    04 196203 199412 TAX-PRD minus 2 months 3,6,9,12
    05/06 196112 YYYY12 TAX-PRD minus 11 months 1-12
    07 198712 YYYY12 TAX-PRD minus 11 months 12
    08 200412 YYYY12 TAX-PRD minus 11 months 1-12
    09 196203 197512 TAX-PRD minus 2 months 3,6,9,12
    09 197612 YYYY12 TAX-PRD minus 11 months 12
    10/11 196112 YYYY12 TAX-PRD minus 11 months 12
    12 198512 YYYY12 TAX-PRD minus 11 months 12
    #13 198012 YYYY12 TAX-PRD minus 11 months 12
    14 200612 YYYY12 TAX-PRD minus 11 months 12
    15 199012 YYYY12 TAX-PRD minus 11 months 12
    16 199412 YYYY12 TAX-PRD minus 11 months 12
    17 200512 YYYY12 TAX-PRD minus 11 months 1-12
    33 196112 200611 TAX-PRD minus 11 months 1-12
    34 196112 YYYY12 TAX-PRD minus 11 months 1-12
    35, 65 (IMF) 201412 YYYY12 TAX-PRD minus 11 months 1-12
    36 197012 YYYY12 TAX-PRD minus 11 months 1-12
    37 197001 198712 TAX-PRD minus 11 months 1-12
    37 198812 YYYY12 TAX-PRD minus 11 months 12
    40 200401 YYYY12 TAX-PRD minus 11 months 1-12
    43 201512 YYYY12 TAX-PRD minus 11 months 1-12
    44 197001 YYYY12 TAX-PRD minus 11 months 1-12
    46 198412 YYYY12 TAX-PRD minus 11 months 1-12
    47 200007 YYYY12 TAX-PRD minus 11 months 1-12
    49 200007 YYYY12 TAX-PRD minus 11 months 1-12
    50 197001 YYYY12 TAX-PRD minus 11 months 1-12
    51 196112 197012 TAX-PRD minus 11 months 12
    51 197103 198112 TAX-PRD minus 2 months 3,6,9,12
    51 198212 YYYY12 TAX-PRD minus 11 months 12
    52 000000 000000 12/01/1961  
    58 197007 198009 TAX-PRD 1-12
    *60 195607 YYYY12 TAX-PRD 1-12
    *61 196206 198706 TAX-PRD 1-12
    *62 196206 198006 TAX-PRD 1-12
    *63 196206 YYYY12 TAX-PRD 1-12
    *64 196206 YYYY12 TAX-PRD minus 1 month 1-12
    65 (IMF) 201412 YYYY12 TAX-PRD minus 11 months 1-12
    67 197012 YYYY12 TAX-PRD minus 11 months 1-12
    74 198412 YYYY12 TAX-PRD minus 11 months 1-12
    75 197412 YYYY12 TAX-PRD minus 11 months 1-12
    76 198412 YYYY12 TAX-PRD minus 11 months 1-12
    77/78 198612 YYYY12 TAX-PRD minus 11 months 12
    79 201409 YYYY12 TAX-PRD minus 11 months 1-12
    82 (IMF) 201712 YYYY12 TAX-PRD minus 11 months 1-12
    83 201712 YYYY12 TAX-PRD minus 11 months 1-12
    85/86 198412 YYYY12 TAX-PRD minus 11 months 1-12

  3. IMPORTANT: The following "bullets" provide other information on certain items displayed in the above-referenced table (i.e., note asterisked (*) and pound-signed (#) references):

    Note:

    Day in EARLIEST-DATE-ALLOWED is 01. YYYY in TAX-PRD is equal to YEAR of PROCESS-DATE plus 1 year.

    • * Bypass generating EARLIEST-DATE-ALLOWED on correction passes

    • # Month range for MFT-CD 13 with Reference Numbers 519, 565, 613, 643, 644, 648, 650, 655, 656, 657, 661, 656, 657, 661, 665, 676, 677, 693 694, 700, 701, 702, 703, 704, 705, or 710 is 01 through 12.

    • # MFT-CD 13 has to be calendar year with Reference Number 628.

  4. Correct as follows:

    1. Compare the document to the error register. Correct any transcription errors.

    2. If the tax period was transcribed correctly but the period was prior to the earliest valid tax period, reject using Action Code 3 for further research.

    3. If transcribed correctly but the tax period on the document is incorrect, reject with Action Code 3.

    4. Attach Form 4227 and notate "invalid tax period" .

    5. Route to the Accounting function (for contact with originator for research and or correction)..

    6. See IRM 3.12.21.4.2.8(2) above.

Field 01-E - Date of Transfer (also known as "Transfer-In Date" )---Validity Checks
  1. The Date of Transfer is found in Item E (Section 01), Page 1, Form 3413.

  2. This is an eight-digit field which MUST be present and must be NUMERIC.

  3. It is edited in YYYYMMDD format. The month (fifth and sixth digits) must be 01-12 and the day (seventh and eighth digits) must be 01-31).

  4. On BMF documents-the date may not be later than the current date, earlier than the tax period beginning nor earlier than 1961-12-01.

  5. On IMF documents-the date may not be later than the current date, earlier than the tax period beginning nor earlier than 1962-12-01.

  6. On IRAF documents-the date may not be later than the current date, earlier than the tax period beginning date nor earlier than 1976-01-01.

  7. For all MFTs-the transfer in date can't be earlier than the earliest date allowed for the individual MFT (see IRM 3.12.21.4.2.8 for table).

Field 01-E - Date of Transfer (also known as "Transfer-In Date" ) (Correction Procedures)
  1. Compare the document with the register. Correct any transcription errors.

  2. If correct as transcribed, determine the valid date from Form 3413 or Form 3552 and enter the result in Field 01-E.

  3. If there is no date on the document, enter the same date as in Field 01-F, 23C Date (Date of Assessment/Transaction Date).

Field 01-F - 23-C Date of Assessment (also known as "Transaction Date" )---Validity Checks
  1. The 23C Date or Date of Assessment is found in Item F (Section 01), Page 1, Form 3413. It is also located under the Reference column (Line 30) of the Form 3552.

  2. This field is the 23C date of Field 01-G, Original Assessment Transaction Code.

  3. This field is an eight-digit field which must be numeric.

  4. It is edited in YYYYMMDD format. The month (fifth and sixth digits) must be 01-12 and the day (seventh and eighth digits) must be 01-31.

  5. The transaction date may not be later than the current processing date, not earlier than the tax period beginning date and not earlier than the earliest date valid for the master file and MFT being processed. (See table in IRM 3.12.21.4.2.8 for earliest date allowed by MFT.)

    1. BMF- can't be earlier than 1961-12-01 (i.e., December 1, 1961).

    2. IMF- can't be earlier than 1962-12-01 (i.e., December 1, 1962).

    3. IRAF- can't be earlier than 1976-01-01 (i.e., January 1, 1976).

  6. For BMF only-the transaction date may be earlier than the tax period on the correction run for MFTs 51, 58, 60, 61, 62, 63 and 64. If the date is correct, enter Action Code 7 to clear the register. For other BMF MFT Codes, see correction procedures under IRM 3.12.21.4.2.12.

  7. Both the transaction code and the transaction date must be present. If one is missing, Fields 01-F, 23-C Date of Assessment (Transaction Date), 01-G, Original Assessment Transaction Code, and 01-H, Original Assessment Transaction Amount, will appear invalid. See Figure 3.12.21-18.

    Figure 3.12.21-18

    This is an Image: 33670018.gif

    Please click here for the text description of the image.

Field 01-F - 23-C--Date of Assessment (also known as "Transaction Date" ) (Correction Procedures)
  1. Compare the document with the register. Correct any transcription errors.

  2. If BMF MFT Code is other than 51, 58, 60, 61, 62, 63 or 64, reject, using Action Code 3, and notate on Form 4227, "Trans. Date is prior to tax period" .

  3. If the date is correct as transcribed and Field 01-F is in error, determine the correct date or tax period. Enter the information on the register with Action Code 6.

  4. If the correct data can't be determined, reject the register with Action Code 3. Attach Form 4227 and notate "invalid or missing Assessment date" .

Field 01-G - Original Assessment Transaction Code (or, "Transaction Code of Original Assessment" )
  1. The Original Assessment Transaction Code is found in Item G (Section 01), Page 1, Form 3413. It is also located under the TC (Transaction Code) column (Line 31) of the Form 3552.

  2. This field will appear invalid if it is not one of the codes shown in the correct chart Exhibit 3.12.21-5, Valid IMF Transaction Code Table, through Exhibit 3.12.21-7, BMF Valid Transaction Code Table.

  3. This field will appear invalid if it does not contain a Transaction Code that is valid for the doc code and MFT being processed.

    1. Compare the document with the register.

    2. Correct any transcription errors (NUMERIC)

      Note:

      The Original Assessment Transaction Code is found in Item G (Section 01), Page 1, Form 3413.

    3. If the document is correct as transcribed and a valid transaction code can't be determined, reject the document with Action Code 3.

    4. Attach Form 4227, Intra-SC Reject or Routing Slip, and notate "01-G (Original Assessment Transaction Code) invalid" .

    5. Route the Form 4227 to the Accounting function (for contact with the originator for research and or correction)..

  4. Fields 01-G and 01-H will both display asterisks (*) if there is an entry in Field 01-I and Field 01-H is blank. Enter the original transaction amount from Form 3413, in Field 01-H. If the amount can't be determined, reject the document with Action Code 3.

  5. Fields 01-G and 01-J will both display asterisks if there is an entry in Field 01-J, and Field 01-G is not 300. (Figure 3.12.21-19.) If Field 01-G is other than 300, reject the document with Action Code 3. Attach Form 4227 and notate "01-G not 300" .

    Figure 3.12.21-19

    This is an Image: 33670019.gif

    Please click here for the text description of the image.

  6. Field 01-G will asterisk if the MFT is 12, Field 40-H is present and the transaction code is other than 150. (See Figure 3.12.21-20.) Correct as follows:

    1. Compare the register with the document.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record with Action Code 3.

    4. Attach Form 4227 and notate "TC 150 missing MFT 12 with Line 8 amount present."

    Figure 3.12.21-20

    This is an Image: 33670020.gif

    Please click here for the text description of the image.

  7. Field 01-G will appear invalid along with Fields 01-H, Original Assessment Transaction Amount, Field 01-M, Reference Number and Field 01-N, Reference Amount if the information contained in those fields does not match the information contained in the table below.

    MFT is 13 or 55*

    MFT-CD 01-M REFERENCE NUMBER 01-N REFERENCE NUMBER AMT 01-G TRANS CD SECTION 01 01-H TRANS AMOUNT SECTION 01
    55 527, 528 Greater than 0 240 0
    55 Present (exclude 527, 528) Greater than 0 290 0
    13 Present Greater than 0 240 0
    13 Present (exclude 662, 663) Greater than 0 290 or 241 0
    55 Not Present 0 402 0 or positive
    13 Not Present 0 240 or 402 0 or positive
    13 Not Present 0 241 0 or negative
     

    MFT is 02, 05, 51, 52, 30, 31

    01-M REFERENCE NUMBER 01-N REFERENCE NUMBER AMT 01-G TRANS CD SECTION 01 01-H TRANS AMOUNT SECTION 01
    Present greater than 290 Positive or 0
    (not blank) 0    
    Present greater than 300 Positive or 0
    (not blank) 0    
     
    1. Compare the document with the register. Correct any transcription errors.

    2. If the document is correct as transcribed, reject the record with Action Code 3.

  8. IMPORTANT: The following "bullets" provide other information on certain items contained in the above-referenced tables:

    • * MFTs 13 or 55: If Fields 01-M and 01-N are present, there must be a TC 290 in Field 01-G and NO amount in Field 01-H.

    • ** MFTs 02, 05, 30, 31, 51, or 52: If Fields 01-M and 01-N are present, there must be either a TC 290 in Field 01-G and NO amount in Field 01-H, or a TC 300 in Field 01-G with or without an amount in Field 01-H.

  9. Fields 01-G and 01-H will appear invalid if the transaction code is 150, the transaction amount is greater than 0 (zero), and the MFT is 06, 36, 37 (with a tax period later than 198711), or 67. Reject the register with Action Code 3. Attach Form 4227, notating, "Transaction Code 150 transaction amount greater than 0" (zero).

Field 01-H - Original Assessment Transaction Amount (or, "Transaction Amount" )
  1. The Original Assessment Transaction Amount is found in Item H (Section 01), Page 1, Form 3413. It is also located under the Assessment column (Line 32) of the Form 3552.

  2. This field must be all numeric.

  3. The debit (+) or credit (-) amount that displays in this field must be compatible with Field 01-G (Transaction Code). See Exhibit 3.12.21-5, Valid IMF Transaction Code Table, through Exhibit 3.12.21-7, BMF Valid Transaction Code Table, for the valid debit and credit transaction codes.

  4. If there is an entry in Field 01-H, there must be an entry in Field 01-G.

  5. This field cannot display as a credit (-) unless Field 01-G contains TC 430. TC 430 is only valid for IMF, MFT 30, Doc Code 52.

  6. Fields 01-G and 01-H will appear invalid if the transaction code is 150, the transaction amount is greater than 0 (zero), and the MFT is 06, 36, 37 (with a tax period later than 198711), or 67. Reject the register with Action Code 3. Attach Form 4227, notating, "Transaction Code 150 transaction amount greater than 0" (zero).

Field 01-I - Transfer-in Amount (also known as "Balance Transferred-In" or "Primary-Trans-PJ (pre-journalized) - Amount" )
  1. The Transfer-In Amount is found in Item I (Section 01), Page 1, Form 3413.

  2. This field must be all numeric.

  3. This field can't be changed. If there is a transcription error in the money amount, reject the document with Action Code 3 to be reinput.

    Note:

    Attach Form 4227 , Intra-SC Reject or Routing Slip, notating, “Transfer-in amount not transcribed correctly.”

  4. If the Doc Code is 51, Field 01-I must be a debit (signed positive) or zero.

  5. If the Doc Code is 52, Field 01-I must be zero.

  6. If Field 01-I underprints, see IRM 3.12.21.12.1.

Field 01-J - Agreement Date (also known as, "870 Agreement Date" )-DOC Code 51 only
  1. The Agreement Date is found in Item J (Section 01), Page 1, Form 3413. It is located on Line 23 of the Form 3552 (it is displayed as the "870 Agreement Date" ).

  2. This field is invalid with Doc Code 52.

  3. This date is entered from Form 3552 and Form 3413 (Doc Code 51 only) to provide the master file with the correct interest computation date.

  4. This date must be in YYYYMMDD format. The month (fifth and sixth digits) must be 01-12 and the day (seventh and eighth digits) must be 01-31.

  5. The date may not be later than the current processing date or earlier than the following dates:

    1. 1970-01-01 (i.e., January 1, 1970) for IMF and BMF on initial input or 1962-01-01 (i.e., January 1, 1962) for BMF and 1962-12-01 (i.e., December 1, 1962) for IMF on error correction run.

    2. 1976-01-01 (i.e., January 1, 1976) for IRAF on both initial input and error correction run.

  6. If an invalid 870 date is present on Form 3552 and a valid date is not available from the attachments, reject the document, using Action Code 3. Attach Form 4227, notating "invalid 870 date" . Route to Accounting for correction.

  7. If an agreement date is present in Field 01-J, then Field 01-G must have a TC 300, 304 or 308. If Field 01-G is other than TC 300, 304 or 308 remove the agreement date in Field 01-J.

Field 01-K---TIN Type
  1. This field must contain a "0" (Zero) when the MFT (Field 01-C) is 58, 78, 76 and TIN (Field 01-B), is an SSN. In all other cases, leave blank.

    Note:

    If incorrect or missing, compare against the TIN Type found in Item B (Section 01), Page 1 ("EIN or SSN and TIN Type" ), Form 3413, and correct Field 01-K.

  2. If MFT is 29, 30, 31, 35, 51, 52, 55, 65, 82 then the TIN Type should be "0" (SSN).

  3. If MFT is 17, 58, 76, or 78, the TIN Type can be either "0" (for SSN) or Blank (for EIN).

    Note:

    The TIN Type will not be correctable for all MFT Codes. MFT 51, MFT 52; IMF and IMF/IRAF: use SSN versus EIN. MFTs 17, 58, 76 and 78: use both SSN and EIN.

  4. Delete entry Field 01-K if invalid.

Field 01-L - Correspondence Received Date
  1. The Correspondence Received Date is found in Item K (Section 01), Page 1, Form 3413. It is located on Line 25 of the Form 3552.

  2. The Correspondence Received Date must be in YYYYMMDD format and must be all numeric. It may not be later than the current processing date nor earlier than 1962-12-01 (December 1, 1962) for IMF, 1961-12-01 (December 1, 1961) for BMF, or 1976-01-01 (January 1, 1976) for IRAF. It can't be earlier than the earliest date allowed.

  3. If the date was transcribed incorrectly, correct using Action Code 6.

  4. If a valid correspondence received date can't be located, reject the document with Action Code 3. Attach Form 4227, notating “invalid correspondence received date”.

Fields 01-M and 01-N - Reference Number and Reference Number Amount
  1. The Reference Number must be a three-digit numeric field. This data is necessary to allow the automatic transfer of certain civil penalties, using Doc Code 51 or 52 into MFTs 02, 05, 13, 30, 31, 51, 52, and 55.

    Note:

    The Reference Number and Reference Number Amount are found under Item M and Item N (Section 01), respectively, Page 1, Form 3413 (Doc Code 52). The Reference Number and Reference Number Amount are found under Line 36 (Reference Number) and Line 37 (Reference Number Amount) respectively, Page 1, Form 3552 (Doc Code 51). On the Form 3552, the "Reference Number" is referred to as "Ref. (Reference) Code"

  2. Fields 01-M and 01-N are invalid for IRAF (MFT 29).

    1. If present, reject the document with Action Code 3.

    2. Attach Form 4227, Intra SC-Reject or Routing Slip, notating "Reference Number and amount not valid on IRAF" .

    3. Route to Accounting for contact with the originator for research and correction.

  3. Field 01-M, Reference Number, if present, must be a three-digit numeric field. See the table below for valid MFTs and Reference Numbers.

    1. Compare the document and the register and correct any transcription errors.

    2. If Field 01-C (MFT Code) and or Field 01-M (Reference Number) display asterisks (*) if they are invalid (such as, in “error”):

    3. If in "error" , do as follows:

    4. Compare the document and the register against the valid Reference Numbers and MFTs in the table below.

    5. If the Reference Number in Field 01-M is not listed in the table below:

    6. Reject the record, using Action Code 3.

    7. Prepare Form 4227, Intra-SC Reject and Routing Slip.

    8. Notate on the 4227, "Reference Number is not valid" .

    9. Attach the 4227 to the document and route them to Accounting (for contact with the originator for research and or correction).

    MFT-AND REFERENCE-NUM-TABLE

    REFERENCE-NUM MFT-CD DOC-CD
    198 12 51, 52
    253 30 51
    255 through 258 30 51
    260 30 51
    262 30 51
    280 01, 09, 11, 14 51,52
    281 through 282 12 51
    290 01, 11, 14 51, 52
    292 through 295 46 51
    296 01, 09, 11, 14 51, 52
    299 01, 09, 11, 14 51, 52
    324 40 51, 52
    330 through 333 08 51, 52
    330 through 333 02, 12 51
    331 through 332 30 51
    334 30 51
    336 30 51
    338 30 51
    346 40 51, 52
    350 40 51, 52
    352 through 357 40 51, 52
    359 through 363 40 51, 52
    369 40 51. 52
    375 through 377 40 51, 52
    391 13, 55 51, 52
    411 13, 55 51, 52
    438 03 51, 52
    500 through 510 13, 55 51
    511 13, 55 51, 52
    512 through 518 13, 55 51
    519 13 51, 52
    520 through 526 13, 55 51
    527 through 528 55 51, 52
    530 13, 55 51, 52
    531 13, 55 51, 52
    533 13, 55 51, 52
    535 13, 55 51, 52
    537 13, 55 51, 52
    547 through 548 13, 55 51
    549, 550 13, 55 51, 52
    551 13, 55 51, 52
    559 through 562 13, 55 51, 52
    581 13, 55 51, 52
    589 13, 55 51, 52
    598 13, 55 51, 52
    599 13, 55 51, 52
    600 through 657 13, 55 51
    627 55 52
    658 13 51, 52
    658 through 660 55 51
    661 13, 55 51
    662 through 663 13 51, 52
    662 through 673 55 51
    674 through 677 13, 55 51
    678 *** 13 51
    680 01 through 05, 07, 09 through 12, 14, 16, 30, 31, 33, 34, 37, 44, 50, 51, 52, 60, 63, 64, 77, 78 51, 52
    681 02, 05, 30, 31, 51, 52 51, 52
    682 02, 05, 06, 34, 51, 52 51, 52
    683 02, 03, 05, 06, 07, 30, 31, 34, 51, 52, 55 51, 52
    685 02, 30, 31 51, 52
    686 * 01 through 05, 07, 09 through 12, 14, 16, 30, 31, 33, 34, 37, 44, 50, 51, 52, 60, 63, 64, 77, 78 51, 52
    687 01 through 05, 07, 09 through 12, 14, 15, 16, 30, 31, 33, 34, 37, 44, 50 through 52, 60, 63, 64, 77, 78 51, 52
    689 ** 37, 44, 46, 67, 85, 86 51
    692 **** 35, 65 51, 52
    693 13 51, 52
    694 13 51, 52
    700 13, 30, 31, 55 51, 52
    701 13 51, 52
    702 13, 55 51, 52
    703 13, 55 51, 52
    704 13, 55 51, 52
    705 13 51, 52
    706 13, 55 51
    707 05, 30, 31 51, 52
    708, 709 13, 55 51
    710 13, 30, 31, 55 51, 52
    711 13, 55 51, 52
    722 02, 06, 07 51, 52
    723 02, 06 51, 52
    724 02, 05, 06 51, 52
    780, 781 ALL 51, 52
    786 through 792 02, 30 51
    870, 871, 872 37 51, 52

    SOURCE: FSP 1.35.04.06 ; Process 3.1.2.8.1.1.1.5.7.3.2.1: Procedures 1., 1.1, 1.1.1, 1.1.1.1, and 1.1.1.1.1.

    Reminder:

    This table matches the MFT/REF-NUM/TAX-PRD CONSISTENCY TABLE FOR DP-ADJUSTMENTS (FSP NO.: 1.05.19.01).

  4. The following Footnote Legends Table provides information on Reference Numbers contained in the above-referenced MFT-Reference Number-Doc Code Table.

    FOOTNOTE LEGENDS FOR THE ABOVE MFT REFERENCE NUMBER AND DOC CODE TABLE

    REFERENCE NUMBERS

    LEGEND/DESCRIPTIONS
    686 * DOC Code 52 will be valid for Reference Number 686 for 200101 processing.
    689 ** Reference Number 689 valid only with TC 240
    678 *** Reference Number 678 is valid for calendar year Tax Periods 198512 and subsequent. It must be Month 12. It is invalid for amounts greater than $50,000. If any of these requirements are not met, Fields 01-D (Tax Period), Field 01-M (Reference Number), and Field 01-N (Reference Number Amount) will appear invalid (for example, in "error" ).
    692 **** When Reference Number 692 is present with MFT 35: (1) it’s only valid for Tax Period 201812 and prior; (2) Invalid for Tax Years 201912 and subsequent, and (3) Transaction Codes TC-240 or TC-241 TC-290 or TC-291 must be present. If any of these requirements are not met, Fields 01-D, 01-M and 01-N will appear invalid (for example, in "error" .
     

  5. The following "bullets" provide other information on items contained in these instructions and the MFT-REFERENCE-NUMBER-DOC CODE Table.

    • IF Field 01-M (Reference Number) is 680, 681, 682, 685, 686, or 689, then Transaction Code (TC) field(s) must contain either TC-290, 294, 298, 300, 304, 308, or 402; or TC-291, 295, 299, 301, or 309 must appear in the correct TC field in Sections 02-19. (TC 291, 295, 299, 301, or 309. They may appear in Section 02-19, but are not needed. (Their associated Transaction Amounts must be negative.)

    • IF NOT, Field 01-D (Tax Period), Field 0 1-M (Reference Number), Field 01-N (Reference Number Amount) or the correct Transaction Code (TC) and Amount Fields in Sections 02-19 will display asterisks (*) and appear "invalid" (for example, in "error" ).

  6. CORRECTION PROCEDURES (Field 01-M):

    • Compare the document and the register.

    • If the Reference Number is invalid or was transcribed incorrectly, correct with Action Code 6.

    • If the document was correctly transcribed, but the Reference Number (Field 01-M) or Reference Number Amount (Field 01-N) is missing, reject the record with Action Code 3.

    • Attach Form 4227, notating (depending on the missing item), "Reference Number (or Reference Number Amount) is missing." .

    • Return to Accounting (for contact with the originator for research and or correction).

  7. Field 01-N, Reference Number Amount, is a numeric field not to exceed 13 digits. If there is a Reference Number present and no Reference Number Amount, search the document and attachments for a valid reference amount.

    1. If a Reference Number Amount one is found, enter it in Field 01-N.

    2. If a valid reference amount can't be found, reject the document with Action Code 3.

    3. Notate on Form 4227, "Reference Number Amount missing or incorrect" .

    4. Attach the 4227 to the document and route to Accounting (for contact with the originator for research and or correction).

  8. IMPORTANT: The original Field 01-N (Reference Number Amount) is a positive number. If correction is made on Field 01-N, it can be a negative number.

  9. If there is a Reference Number Amount (Field 01-N) present and no Reference Number (Field 01-M), search the document and attachments for a valid Reference Number.

    Note:

    You may also consult either the MFT-Reference-Number Table (in this subsection) or Exhibit 3.12.21-8 (Reference Numbers) to confirm the valid MFT/Reference Number information.

    1. If a Reference Number is found, enter it in Field 01-M.

    2. If one is not found, use the table above to determine the correct Reference Number and enter in Field 01-M.

    3. If you can't readily determine the correct Reference Number, use your local procedures to correct the problem.

  10. IMPORTANT: If there is a Reference Number (Field 01-M), there must be a Reference Number Amount (Field 01-N). If either is present, they must both be present.

  11. If there is a Reference Number or Reference Number Amount, there must be both.Field 01-N, Reference Number Amount, is a numeric not to exceed 13 digits. If there is a Reference Number present and no Reference Number Amount, search the document and attachments for a valid reference amount.

    1. If a Reference Number Amount is found, enter it in Field 01-N.

    2. If a valid reference amount can't be found, reject the document with Action Code 3.

    3. Notate on Form 4227, "Reference Number Amount missing or incorrect" .

    4. Attach the 4227 to the document and route to Accounting (for contact with the originator for research and or correction).

  12. If there is a Reference Number Amount (Field 01-N) present and no Reference Number, search the document and attachments for a valid Reference Number.

    Note:

    You may also consult either the MFT-Reference-Number Table (in this subsection) or Exhibit 3.12.21-8 (Reference Numbers) to confirm the valid MFT/Reference Number information.

    1. If a Reference Number is found, enter it in Field 01-M.

    2. If one is not found, use the table above to determine the correct Reference Number and enter in Field 01-M.

    3. If you can't readily determine the correct Reference Number, use your local procedures to correct the problem.

  13. We listed Reference Numbers (with their Process Specifications as used in Consistency Checks) in Paragraph (12) through Paragraph (48) of this subsection.

    • Reference Numbers appear in this subsection/text according to their Functional Specifications Package (FSP) process/procedures order.

    • Distinguish which is the one you’re looking for by their Tax Periods, MFTs, and other distinguishing information.

    • We provided each Reference Number’s Process Specifications for your information.

  14. Reference Number 290

    • If Reference Number is 290,

    • MFT-CD is 01, AND

    • Tax Period must be equal to or within 201112 through 202203

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: Functional Specifications Package (FSP) Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 1. and 1.1.

  15. Reference Number 290

    • If Reference Number is 290,

    • MFT-CD is 11 or 14, AND

    • Tax Period must be equal to or within 201112 through 202212

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 1. and 1.1, and 1.1.1.

  16. Reference Number is greater than 291 and less than 296

    • If Reference Number is greater than 291 and less than 296, AND

    • MFT-CD is 46, AND

    • Tax Period is before 201003

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 2. and 2.1.

  17. Reference Number 519

    • If Reference Number is 519,

    • MFT CD is 13, AND

    • the Tax Period is before 12/31/16 (December 31, 2016), AND

    • Month of Tax Period is not 03, 06, 09 or 12.

    • If the transcribed fields do not meet the criteria described above, the If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 3. and 3.1.

  18. Reference Number 627

    • If Reference Number is 627,

    • MFT-CD is 55. AND

    • Tax Period is before 199712,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 4. and 4.1.

  19. Reference Number 649

    • If Reference Number is 649,

    • MFT-CD is 13, AND

    • Tax Period is before 199012,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 5. and 5.1.

  20. Reference Number 677 or 706

    • If Reference Number is 677 or 706, AND

    • Tax Period is before 200912

    • If the transcribed fields do not meet the criteria described above, the Reference Number and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 6. and 6.1.

  21. Reference Number 682

    • If Reference Number is 682, AND

    • MFT-CD is either 02, 05, 06 or 34, AND

    • Tax Period is equal to or greater than 201712, AND

    • Transaction Code of Section 01 is 290, 294, 298, 300, 304, or 308, AND

    • Transaction Code of Section 02 is BLANK, 240, 241, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and or 309

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields, along with the Transaction Code(s), will appear invalid (such as, set to “error”).

    • Source: Unified Work Request (UWR) 243633.

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 7. and 7.1.

  22. Reference Number 683

    • If Reference Number is 683, AND

    • MFT-CD is 02 or 03 or 05 or 06 or 07 or 30 or 31 or 34 or 51 or 52 or 55, AND

    • Tax Period is before 201003.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 8. and 8.1.

  23. Reference Number 685

    • If the Reference Number is 685, AND

    • Tax Period is before 198709

    • If the transcribed fields do not meet the criteria described above, the Reference Number and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 9. and 9.1.

  24. Reference Number 686

    • If IMF (such as, the MASTERFILE-SYSTEM-ID-CODE = 1), AND

    • MFT-CD is not 29,

    • the Reference Number is 686, AND

    • Tax Period is before 198909

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 10. and 10.1. and 10.1.1

  25. Reference Number 687

    • If Reference Number is 687,

    • MFT CD is 30, AND

    • Tax Period is before 200705,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 11. and 11.1.

  26. Reference Number 687

    • If Reference Number is 687, AND

    • MFT CD is either 01, 02, 03, 04, 05, 07, 09, 10, 11, 12, 14, 15, 16, 31, 33, 34, 37, 38, 39, 40, 41, 42, 43, 44, 50, 51, 52, 60, 63, 64, 77 or 78, AND

    • The Tax Period is before 201512,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 11.1.1 and 11.1.1.1.

  27. Reference Number 692

    • IMF MFT 35 or IMF MFT 65 with TC 240 is only valid with Field 01-M , EXCEPT:

    • When Reference Number 692 is present with MFT 35 or MFT 65, AND

    • For Tax Period 201812 and prior, AND

    • Transaction Code in Section 01 is TC-240 or TC-290 AND Transaction Code in Section 02-19 is BLANK, 190, 240, 241, 290, and or 291

      Caution:

      IMPORTANT: Transaction Code TC-240 or TC-241 or TC-290 or TC-291 MUST be present.

      Exception:

      IMF MFT 35 or IMF MFT 65 with TC 240 is Invalid for Tax Years 201912 and later

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields, along with the Transaction Code(s), will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 12. and 12.1. and 12.2.

    .

  28. Reference Number 693

    • If Reference Number is 693,

    • MFT is 13, AND

    • The Tax Period is before 201801.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 13. and 13.1.

    .

  29. Reference Number 694

    • If Reference Number is 694,

    • MFT is 13, AND

    • If Tax Period is before 201801.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT and Tax Period fields will appear invalid (such as, set to “error”).

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 14. and 14.1.

    .

  30. Reference Numbers 700 or 710

    • If Reference Number is 700 or 710,

    • MFT is 13, AND

    • The Tax Period is before 201612,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 15. and 15.1.

    .

  31. Reference Number 700

    • If Reference Number is 700,

    • MFT is 30 or 31, AND

    • If Tax Period is before 201003.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 16. and 16.1.

    .

  32. Reference Numbers 700 or 710

    • If Reference Number is 700 or 710,

    • MFT is 55, AND

    • The Tax Period is is equal to or greater than 201003, AND

    • Transaction Code in Section 01 is 240 or 290 AND Transaction Code in Section 02-19 is BLANKS, 190, 240, 241, and or 29X through 30X.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT and Tax Period fields, along with the Transaction Code(s), will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 17. and 17.1.

    .

  33. Reference Number 707:

    • If Reference Number is 707,

    • MFT is 05, 30, or 31, AND

    • The Tax Period is equal to or greater than 201701, AND

    • Transaction Code in Section 01 is 240 (IMF only) or 290 AND Transaction Code in Section 02-19 is BLANKS, 190, 240, 241, 290 and or 291.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields, along with the Transaction Code(s), will appear invalid (such as, set to “error”)

      Caution:

      IMPORTANT: Transaction Codes TC-240 or TC-241 or TC-290 or TC-291 must be present

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 18. and 18.1.

    • See MFT-and-Reference Number-Table below.

  34. Reference Number 708 or 709:

    • If Reference Number is 708 or 709, AND

    • MFT is 13 or 55, AND

    • Tax Period is before 200209,

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 19. and 19.1.

  35. Reference Number 710:

    • If Reference Number is 710, AND

    • MFT is 30 or 31, AND

    • Tax Period is before 201003.

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 20. and 20.1.

  36. Penalty Reference Number (PRN) 724 (beginning Calendar Year 2022)

    • If Reference Number is 724, AND

    • MFT is 02 (Corporate Returns), 05 (Trust Returns), or 06 (Partnership Returns), AND

    • Tax Period is equal to or greater than 201712, AND

    • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and or 301

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, Tax Period, Transaction Code, and Transaction Amount fields, will appear invalid (such as, set to “error”).

    • Source: Unified Work Request (UWR) 243206

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 21. and 21.1.

  37. Reference Number 780 or 781:

    • If Reference Number is 780 or 781, AND

    • Tax Period is before 201006.

    • If the transcribed fields do not meet the criteria described above, the Reference Number and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.9; Procedures 22. and 22.1.

  38. Reference Number 528:

    • If Reference Number is 528,

    • MFT is 55, AND

    • The Reference Number Amount is greater than $10,000,

    • If the transcribed fields do not meet the criteria described above, the MFT, the Reference Number and the Reference Number Amount fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.10; Procedures 1. and 1.1.

  39. Reference Number 658:

    • If Reference Number is 658, AND

    • MFT is 13, AND

    • Tax Period is before 199812, OR

    • Month of Tax Period is not 12, OR

    • Reference Number Amount is greater than $5,000

    • If the transcribed fields do not meet the criteria described above, the Reference Number, MFT, Reference Number Amount, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.10; Procedures 2. and 2.1.

  40. Reference Number 663:

    • If Reference Number is 663, AND

    • MFT is 13, AND

    • Tax Period is before 200008, OR

    • Reference Number Amount is greater than $50,000,

    • If the transcribed fields are not according to the criteria described above, the Reference Number, MFT, Reference Number Amount, and Tax Period fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.10; Procedures 3. and 3.1.

  41. Reference Number 678:

    • If Reference Number is 678, AND

    • MFT is 13, AND

    • Tax Period is before 198512, OR

    • Month of Tax Period is not 12, OR

    • Reference Number Amount is greater than $50,000

    • If the transcribed fields do not meet the criteria described above, the MFT, Tax Period, Reference Number, and Reference Number Amount fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.10; Procedures 4. and 4.1.

  42. Reference Number 280, 296, or 299 (FORM 3413 ONLY) :

    • If FORMAT CODE (025 or 026) equals "Form 3413",

    • Transaction Code in Section 02-19 equals TC-766 or TC-767,

    • MFT is 01, AND

    • Tax Period is 202003, 202006, 202009 or 202012, AND

    • Transaction Code (TC) in Section 01 is 150, 290, 294, 298, 300, 304 or 308, AND Transaction Code in Section 02-19 is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308, and/or 309, AND

    • Reference Number is 280, 296, or 299

    • If the transcribed fields are not according to the criteria described above, the Tax Period, MFT, Reference Number, and Transaction Code fields will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1.2. and 1.3.

  43. Reference Number 280, 296, or 299 (FORM 3413 ONLY) :

    • If FORMAT CODE (025 or 026) equals "Form 3413", AND

    • Transaction Code in Section 02-19 equals 766 or 767, AND

    • MFT is EITHER 09, 11 or 14, AND

    • Tax Period is 202012, AND

    • Transaction Code in Section 01 is 150, 290, 294, 298, 300, 304 or 308, AND Transaction Code in Section 02-19 is BLANKS, 150, 290, 291, 294, 295, 298, 299, 300, 301, 304, 305, 308 and or 309, AND

    • Reference Number is 280, 296, or 299

    • If the transcribed fields are not according to the criteria described above, the Tax Period, MFT, Reference Number fields, along with the Transaction Codes will appear invalid (such as, set to “error”)

    • Source: FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 1.2. and 1.3.

  44. Penalty Reference Number (PRN) 722 (beginning Calendar Year 2022)

    • If Reference Number is 722, AND

    • MFT is 02 (Corporate Returns) or 06 (Partnership Returns) or 07 (REMIC (Form 1066)), AND

    • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANKS, 240, 241, 290, 291, 300 and or 301, AND

    • Transaction Amount for 290, 291, 300 and/or 301 must be zero (0)

    • Valid for all Tax Periods.

    • If the transcribed fields are not according to the criteria described above, the Reference Number, MFT, Transaction Code(s), and Transaction Amount fields will appear invalid (such as, set to “error”)

    • Sources: Unified Work Request (UWR) 243206 AND

    • FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

  45. Penalty Reference Number (PRN) 723 (beginning Calendar Year 2022)

    • If Reference Number is 723, AND

    • MFT is 02 (Corporate Returns) or 06 (Partnership Returns), AND

    • Transaction Code in Section 01 is 290 or 300 AND Transaction Code in Section 02-19 is BLANK, 240, 241, 290, 291, 300 and/or 301, AND

    • Transaction Amount for 290, 291, 300 and/or 301 can only be zero

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

    • Sources: Unified Work Request (UWR) 243206 AND

    • FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 2. and 2.1.

  46. Penalty Reference Number (PRN) 724 (beginning Calendar Year 2022)

    • If Reference Number is 724, AND

    • MFT is 02 (Corporate Returns), 05 (Trust Returns), or 06 (Partnership Returns), AND

    • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) AND Transaction Code in Section 02-19 is 160, AND

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

    • Sources: Unified Work Request (UWR) 243206 AND

    • FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3. and 3.1.

  47. Penalty Reference Number (PRN) 722 (beginning Calendar Year 2022)

    • If Reference Number is 722, AND

    • MFT is 02 (Corporate Returns), 06 (Partnership Returns), or 07 (REMIC (Forms 1066)), AND

    • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) AND Transaction Code in Section 02-19 is 160, AND

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

    • Sources: Unified Work Request (UWR) 243206 AND

    • FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

  48. Penalty Reference Number (PRN) 723 (beginning Calendar Year 2022)

    • If Reference Number is 723, AND

    • MFT is 02 (Corporate Returns) of 06 (Partnership Returns), AND

    • Transaction Code in Section 01 is 160 (Manually Computed Failure to File (FTF) Penalty) AND Transaction Code in Section 02-19 is 160, AND

    • If the transcribed fields do not meet the criteria as described above, the Reference Number, MFT, Transaction Code, and Transaction Amount fields will appear invalid (such as, set to “error”)

    • Sources: Unified Work Request (UWR) 243206 AND

    • FSP Process 3.1.2.8.1.1.1.5.7.3.2.11; Procedures 3.2. and 3.2.1.

Field 01-O - 2% Interest Date
  1. The 2% Interest Date is not valid for MFTs 29, 30, and 55.

    Note:

    The 2% Interest Date is found in Item L (Section 01), Page 1, Form 3413. It is located on Line 22 of the Form 3552.

  2. The 2% Interest Date is not a required field.

  3. If the 2% Interest Date is present on Form 3552, TC 340 (Section 02 through 16) and the Interest-To-Date (Field 01-P) must also be present. If the required fields are not present, reject the register using Action Code 3. Attach Form 4227, notating, "interest-to date missing" .

  4. The 2% Interest Date must be numeric and in YYYYMMDD format.

  5. The 2% Interest Date may not be earlier than 1991-01-01 (i.e., January 1, 1991), nor may it be later than the current processing date.

  6. TC 340/341 must be present for Sections 30 through 33.

    1. If the date was transcribed incorrectly, correct using Action Code 6.

    2. If the correct 2% Interest date can't be determined, reject, using Action Code 3. Attach Form 4227, notating, "2% interest to date can't be determined" .

  7. See IRM 3.12.21.4.2.23 for more information regarding validity checks and if Large Corporate Underpayment (LCU) interest (i.e., additional 2 percent interest) is applicable.

Field 01-P - Interest-To-Date (Form 3552 only)
  1. The Interest-to-Date is located on Line 21 of the Form 3552.

  2. Only one Interest-To-Date can be present.

  3. This field must be all numeric and in YYYYMMDD format.

  4. Month must be in the range of 1 through 12.

  5. Month/Day configuration must be valid in the Month-Day-Table.

  6. If the date is not valid or it has been transcribed incorrectly, correct with Action Code 6.

  7. If the date is not valid and it has been transcribed correctly, reject, using Action Code 3. Attach Form 4227, notating, "interest-to date is not valid" .

  8. See IRM 3.12.21.4.2.23 for more information regarding validity checks and Interest-to-Date.

Field 01-Q - Interest Computation Date (Form 3552) BMF/IMF
  1. The Interest Computation Date is located on Line 23 of the Form 3552.

  2. If an Interest Computation Date is present, one of the following Transaction Codes (TCs) 294, 295, 298, 304, 308, and or 309 must be present. Only one transaction must be present with the following exceptions:

    1. A TC 294 or TC 298 can be present with or without TC 290. If any other TC is present with TC 290, Field 01-Q will asterisk.

    2. A TC 304 or TC 308 can be present with or without TC 300. If any other TC is present with TC 300, Field 01-Q will asterisk.

  3. Transaction codes may appear in Field 01-G or in Sections 02 through 19.

  4. Invalid Conditions:

    Note:

    Not valid for IRAF (MFT 29).

    1. If the Interest Computation Date (Field 01-Q) is present, but none of these transaction codes is present, Field 01-Q will display asterisks (set to "error" ).

    2. If the Interest Computation Date (Field 01-Q) is present, and more than one of these transaction codes is present, Field 01-Q and all corresponding transaction code fields will display asterisks (*).

    3. If the Interest Computation Date is present with either a TC 294 or 298, and more than one TC 290 or any TC 300 is present in Section 01-19, Field 01-Q and all corresponding transaction codes will asterisk.

    4. If the Interest Computation Date is present with either a TC 304 or 308, and more than one TC 300 or any TC 290 is present in Section 01-19, Field 01-Q and all corresponding transaction codes will asterisk.

    5. If the Interest Computation Date (Field 01-Q) contains NO entry, and any Transaction Code (294, 295, 298, 299, 304, 308, or 309) is present in Sections 01-19, Field 01-Q and all corresponding transaction codes will asterisk.

  5. Correction Procedures:

    1. Compare the document and the register.

    2. If the date is invalid and or was transcribed incorrectly, correct with Action Code 6.

    3. If the date is transcribed correctly, verify that a valid transaction code was entered.

    4. If the document was correctly transcribed, but, the Computation Date or Transaction Code is invalid, reject the record with Action Code 3.

    5. Prepare Form 4227, notating, "Computation date or Transaction code invalid" .

    6. Attach 4227 to the document and route to the originator for research and or correction.

  6. See IRM 3.12.21.4.2.23 below for more information regarding validity checks and the Interest Computation Date. Also refer to correction procedures in IRM 3.12.21.5.2.2 (Section 02-19-Fields B, E, and H-Transaction Codes).

Field Validity - Interest Computation Date, Interest-to-Date and 2% Interest Date
  1. Each of these fields must be all numeric and in YYYYMMDD format. Except for MFT 52, the Interest Computation Dates are invalid when the Year of the Interest to Date or Interest Computation Date is earlier than the Year of the Tax Period or later than the Year of the Process Date. (For MFT 52 Only, the Interest-to-Date and Interest-Computation-Date are invalid when Date is after the Process Date, or Date is before December 1, 1961 (12/01/1961).)

  2. The MM must be 01 through 12. The DD must be 01 through 31. If the month is February, then numerics 30 and 31 are invalid. If the other 2% interest rate applies, the 2% "Interest Date" must be present with Field 01-Q.

    Note:

    The 2% "Interest Date" is entered only if Large Corporate Underpayment (LCU) interest (i.e., additional 2% interest) is applicable.

Field 01-R, Plan/Report Number (MFT 46/74/76/85/86 ONLY) (also known as "Report Number" ) (BMF Only)
  1. The Plan/Report Number can only be present with MFT Code 46, 74, 76, 85, or 86 and vice versa. This applies to BMF only. If the MFT is not 46, 74, 76, 85, or 86, Field 01-R and Field 01-C (Master File Tax Account (MFT) Code) will asterisk.

    Note:

    The Plan/Report Number is found in Item R (Section 01), Page 1, Form 3413. It is located in the upper right part of the Form 3552, beneath the Name Control, Taxpayer Identification Number, and Form Number information.

  2. If the Plan/Report Number is present, but the MFT is not 46, 74, 76, 85, or 86, Field 01-R and Field 01-C (Master File Tax Account (MFT) Code) will asterisk.

  3. The MFT 46, 85, or 86 Plan/Report Number must not be in the range of 001-199, 200-299, 400-499, 600-699, 800-899; and for the MFT Code 74 the report must not be in the range of 100-199, 300-399, 500-599, 700-799, or 900-999.

  4. The MFT 76 Plan/Report Number must not be in the range 000-999.

Field 01-S, Excess Fringe Benefit Year (also known as "Excess Fringe Benefit-Date" ) (BMF ONLY)
  1. The Excess Fringe Benefit Year is found in Item U (Section 01), Page 1, Form 3413. This is also located on Line 26 ("Excess Fringe Benefit-Date" ) of Form 3552.

  2. The following EXCESS-FRINGE-BENEFIT-Date field, if present, should be validated, using the following guidelines:

    1. Valid for BMF Only.

    2. MFT-CD must be 76.

    3. Excess-FRINGE-BENEFIT-DATE must be numeric and in the range 1 through 12.

    4. Month/Day configuration must be valid in the Month-Day-Table.

    5. If EXCESS-FRINGE-BENEFIT-DATE is before 01/01/1969 or is after the process date, it will be invalid.

  3. If the EXCESS-FRINGE-BENEFIT-Date is not present, BUT:

    1. the Abstract Number 201 is in Section 36 through 39,

    2. Transaction Code 150 is in Section 01 through 15,

    3. Master File System Code is "2" (BMF),

    4. the Format Code equals Form 3552 (i.e., "325" , "326" , or "347" ), and,

    5. MFT equals 76,

    6. If the EXCESS-FRINGE-BENEFIT-Date is not present, BUT the conditions described in (a) through (e) (above) are.

    7. Then Field 01-S will appear invalid.

      Note:

      Field 01-S will appear invalid (also) if the EXCESS-FRINGE-BENEFIT-Date is present, BUT the conditions described in (a) through (e) (above) are not.

Field 01-T, REVERSION DATE/DATE OF TRANSFER (Valid for BMF Only)
  1. The Reversion Date is found in Item O (Section 01), Page 1, Form 3413. It is located on Line 27 ("Reversion Date" ) of the Form 3552.

  2. The following Reversion Date/Date of Transfer field, if present, should be validated, using the following guidelines:

    1. Valid for BMF Only.

    2. MFT-CD must be 76 or 17 (Date of Transfer).

    3. REVERSION-DATE/DATE OF TRANSFER must be numeric.

    4. Month of REVERSION-DATE/DATE OF TRANSFER must be in the range of 1 through 12.

    5. Month/day configuration must be in the MONTH-DAY-TABLE.

      Note:

      See FSP 1.35.04.06; Page 4.3-ACTRFR-19 (Data Stores) for the MONTH-DAY-TABLE, for information regarding Normal Year and Leap Year data. Any employee familiar with the twelve months of the year and the number of days in each month (including Leap Year) knows this MONTH-DAY Table information already.

    6. MFT 76 (REVERSION-DATE) can't be before 12/31/1984 (i.e., December 31, 1984).

    7. MFT 17 (DATE OF TRANSFER) can't be before 12/31/2005 (i.e., December 31, 2005).

  3. If the Reversion Date is not present, BUT:

    1. the Abstract Number 204 is in Section 36 through 39,

    2. Transaction Code 150 is in Section 01 through 15,

    3. Master File System Code is "2" (BMF),

    4. The Format Code equals Form 3552 (i.e., "325" , "326" , or "347" ), and,

    5. MFT equals 76,

    6. Then Field 01-T will appear invalid.

      Note:

      Field 01-T will appear invalid (also) if the Reversion Date/Date of Transfer is present, BUT the conditions described in (a) through (e) (above) are not.

Field 01-U, PLAN-YEAR-ENDING DATE (Valid for BMF Only)
  1. The Plan Year Ending Date is found in Item S (Section 01), Page 1, Form 3413. It is located on Line 28 ("Plan Year Ending" ) of the Form 3552.

  2. The following PLAN-YEAR-ENDING field, if present, should be validated, using the following guidelines:

    1. Valid for BMF Only.

    2. MFT-CD must be 76 or 74.

    3. PLAN-YEAR-ENDING must be numeric.

    4. Month of PLAN-YEAR-ENDING must be in the range of 1 through 12.

    5. PLAN-YEAR-ENDING can't be before 198412 (i.e., December 1984) for MFT 76 and can't be before 199101 (i.e., January 1991) for MFT 74.

  3. If the Plan Year Ending Date is not present, BUT:

    1. the Abstract Number is (either) 163, or 226, or 205 in Section 36 through 39, and

    2. Transaction Code 150 is in Section 01 through 15, and

    3. Master File System Code is "2" (BMF), and

    4. the Format Code equals Form 3552 (i.e., "325" , "326" , or "347" ), and

    5. MFT equals 76,

    6. Then Field 01-U will appear invalid.

      Note:

      Field 01-U will appear invalid (also) if the Plan Year Ending Date is present, BUT the conditions described in (a) through (e) (above) are not.

Field 01-V, 4980 F-AMENDMENT-DT (Valid for BMF Only)
  1. The 4980F Amendment Date is found in Item V (Section 01), Page 1, Form 3413. It is located on Line 29 ("4890F Amendment Date" ) of the Form 3552.

  2. The following 4980 F-AMENDMENT-DT field, if present, should be validated, using the following guidelines:

    1. Valid for BMF - MFT-CD must be 76.

    2. 4980 F-AMENDMENT-DT must be numeric.

    3. Month of 4980 F-AMENDMENT-DT must be in the range of 1 through 12.

    4. Month/day configuration must be in the MONTH-DAY-TABLE.

    5. If 4980 F-AMENDMENT-DT can’t be before 12/31/1984 (i.e., December 31, 1984).

  3. If the 4980F Amendment Date is not present, BUT:

    1. the Abstract Number is 228 in Section 36 through 39, and

    2. Transaction Code 150 is in Section 01 through 15, and

    3. Master File System Code is "2" (BMF), and

    4. the Format Code equals Form 3552 (i.e., "325" , "326" , or "347" ), and

    5. MFT equals 76,

    6. Then Field 01-V will appear invalid.

      Note:

      Field 01-V will appear invalid (also) if the 4980F Amendment Date is present, BUT the conditions described in (a) through (e) (above) are not.

Field 01-W, F8288 Transfer Date (also referred to previously as "DATE-OF-TRANSFER" )
  1. The Form 8288 Transfer Date is found in Item T (Section 01), Page 1, Form 3413. It is located on Line 30 ("Form 8288 Date of Transfer (MFT 17 only)" of the Form 3552.

  2. The following DATE-OF-TRANSFER FIELD, if present, should be validated, using the following guidelines:

    1. MFT-CD must be 17.

    2. DATE-OF-TRANSFER must be numeric.

    3. Month must be in the range of 1 through 12.

    4. Month/ Day configuration must be in the MONTH-DAY-TABLE.

    5. Transfer Date can't be before 12/31/2005 (i.e., December 31, 2005).

Field 01-X - BMF TIN (Form 3552 Only)
  1. The BMF TIN (Taxpayer Identification Number) MUST contain 9 digits and MUST always be displayed with a Q/P/J (Quick, Prompt, Jeopardy) 240 Assessment when inputting a Form 2859 for civil penalty 240 Reference Number 618 into Automated Manual Assessments (AMAs). Correct any transcription errors.

    Note:

    Require the BMF TIN from the "Remarks" section of the Form 2859 and display the information on the Form 3552. ISRP must transcribe the BMF TIN to display on IDRS.

  2. It can't be all zeroes (0) or all nines (9).

  3. IMF (Individual Master File) and IRAF (Individual Retirement Account File) documents will contain social security numbers (SSNs).

    Note:

    The IRAF (as a separate Master File) was retired in 2004. All references to "MFT 29" are what were previously referred to as IRAF.

  4. BMF documents will have a 9-digit taxpayer identification number which can be a Social Security Number (SSN) or an Employer Identification Number (EIN).

    1. SSNs-MFT 51 (Form 709, United States Gift Tax Return), and MFT 52 (Form 706, U.S. Estate Tax Return), will always have an SSN.

    2. MFTs 46, 58, and 78 with a TIN Type (Field 01-K) of "0" will have an SSN. (See Figure 3.12.21-12.) If the TIN Type is blank, the TIN is an EIN.

    3. EINs-must be all numeric and the first two digits may not be 00, 07 through 09, 17 through 19, 28, 29, 49, 78, 79, or 89.

Section 02 Through 19

  1. This section provides descriptions of the fields and correction procedures for Sections 02 through 19 of the register.

Sections 02 Through 19 - Fields A Through I Description

  1. Listed below are the fields contained in Sections 02-19: Transaction Date, Transaction Code, and Transactions Amount.

  2. The alpha field designators, field lengths (maximum length for variable fields) and field titles are shown below.

    Field Field Length (+/−) Field Title
    02-19A/D/G 8   Transaction Date
    02-19B/E/H 3   Transaction Code
    02-19C/F/I 12 +/− Transaction Amount

  3. Each subcategory (within sections 02 through 19) consists of a group of three (3) items:

    • Each group consists of a Transaction Code, a Transaction Date and a Transaction Amount.

    • A group is considered significant when at least one (1) field in the group is present.

    • The document will appear on the error register if all 3 required fields (such as, Transaction Code, Transaction Date and Transaction Amount) in one (1) group are not present.

    • The document will appear on the error register if all the required fields in a group are not present when one field is present.

  4. When deleting a section, move the data to the smallest numbered section available and delete the highest.

    1. On the error register, edit the data from the current field to the correct corresponding field(s) in the smallest numbered section available.

    2. Enter an Action Code "6" to the left of that section to alert ISRP operators this information is being added to the section.

    3. Enter an Action Code "4" to the left of the (higher numbered) section from which the data was moved. This will inform ISRP operators to delete the section.

    (See Figure 3.12.21-21.)

    Note:

    For Form 3552ONLY Sections 02-16 are valid.

    Figure 3.12.21-21

    This is an Image: 33670021.gif

    Please click here for the text description of the image.

Correction Procedures-Sections 02-19

  1. This section describes field validity criteria and correction procedures for all fields in Section 02-19.

Section 02-19 - Fields A, D, and G - Transaction Date
  1. The Transaction Date, if present, is an eight-digit, all numeric field.

  2. The Month of the Transaction Date must be in the range of 01 through 12.

  3. The transaction date may not be later than the current processing date and not earlier than the earliest date allowed.

  4. On the correction run, a date earlier than the earliest date allowed is valid, but it can't be before the following dates.

    1. For BMF-1961-12-01 (i.e., December 1, 1961)

    2. For IMF-1962-12-01 (i.e., December 1, 1962)

    3. For IRAF-1976-01-01 (RAW PASS), 1962-12-01 (CORR)

      Note:

      The Individual Retirement Account File (as a separate Master File) was retired in 2004. All references to "MFT 29" are what were previously referred to as IRAF.

  5. If the date is blank and the Transaction Code (TC) is a penalty or additional tax, use the date from Field 01-F (23-C Date of Assessment or "Transaction Date" ).

  6. IMPORTANT: A Transaction Code (TC) 150 (i.e., "Tax Assessment Return" OR"Entity Created by a TC 150" ) and a TC 300 ("Examination Tax Assessment" ) must never be on the same assessment. If an assessment (on the paper Error Register) includes BOTH a TC 150 and a TC 300, do as follows:

    1. Reject, using Action Code 3.

    2. Attach Form 4227, notating, "includes a TC 150 and a TC 300" .

    3. Route to Accounting for correction.

  7. If, after comparing the error register against the input document, a valid transaction date can't be determined:

    1. Prepare Form 4227, "Intra SC-Reject or Routing Slip" .

    2. Notate on the 4227, "Invalid transaction date" .

    3. Reject, using Action Code 3, to the originator for correction.

      Exception:

      BMF MFTs 51, 58, 60, 61, 62, 63, and 64 have no restrictions on the earliest valid date on the correction run. Use Action Code 7 to clear the register.

  8. If all Transaction Dates were correctly input from the document and are valid for the allowable dates listed in Paragraph (4) above, use Action Code 7 to clear the register.

Section 02-19 - Fields B, E, and H - Transaction Codes
  1. These fields will be invalid if they do not contain a transaction code (TC) such as valid for the doc code, MFT, and section number being processed. See Exhibit 3.12.21-5, Valid IMF Transaction Code Table, through Exhibit 3.12.21-7, BMF Valid Transaction Code Table.

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Prepare Form 4227; notating, "two TC 150s present" .

    5. Attach 4227 to the document and route to Accounting for research and or correction.

  2. Fields B, E, or H will appear invalid if more than one TC 150 is present in the document. Correct as follows:

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "two TC 150s present" .

    5. Attach 4227 to the document and route to Accounting for research and or correction.

  3. The transaction codes and their corresponding transaction amount must be compatible.

  4. For every transaction code 402 there must be a corresponding TC 400 with the transaction date and transaction amount of the same value. Correct as follows:

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Prepare Form 4227, notating, "TC 402 without TC 400 Present" .

    5. Attach 4227 to the document and route to Accounting for research and or correction.

  5. If TCs 630, 632, 636, or 637 appear in this section, move the TCs to section 20 per the requirements for that section.

  6. If Fields A, B and C have entries, Fields D, E and F are blank, and Fields G, H, and I have entries, an asterisk will print before the blank fields. Correct by moving the data, leaving no blank intervening fields or sections. (See Figure 3.12.21-22.) Move entries from Fields G, H, and I into Fields D, E, and F, and delete Fields G, H, and I.

  7. If IMF record and TC 450 is present and tax period is 197512 or later, this is an invalid condition.

    Figure 3.12.21-22

    This is an Image: 33670022.gif

    Please click here for the text description of the image.

  8. If there is any TC 340/341 in Sections 02-19, dated 01/01/1991 (i.e., January 1, 1991) or later, there must be an equal number of TC 340/341s in Sections 30-33. If they are not present in an equal number, all TC 340/341 in Sections 02-19 and 30-33 and their related date and money amount fields will asterisk if the date is after 01/01/1991. Compare the register to the document and if you can determine the problem, correct. If not, reject to the originator for resolution, using Action Code 3. Attach Form 4227 and send to originator, notating, "please verify transaction codes" .

    Note:

    For Form 3413 only.

  9. The Interest Computation Date (Field 01-Q) is checked against Transaction Codes 290, 294, 295, 298, 299, 300, 304, 308, 309 in Sections 01 through 19.

    Note:

    This applies only to Form 3552 (Doc Code 51) and BMF and IMF. The program will bypass this check if the Interest Computation Date (Field 01-Q) is invalid.

  10. When Transaction Codes 290, 295, 298, 299, 300, 304, 308, 309 are present in Sections 01 through 19, the Interest Computation Date (Field 01-Q) must be present. If any of Transaction Codes 294, 295, 298, 299, 304, 308, and 309 are present, but Field 01-Q (Interest Computation Date) contains no entry, Fields B, E, H (Sections 01-19), and Field 01-Q will error code. To correct:

    1. Compare the document (Form 3552) and register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "Transaction Codes (TCs) are present without an Interest Computation Date" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  11. If a TC 290 or TC 300 is present with none of the Transaction Codes (TCs) 294, 295, 298, 299, 304, 308 and 309 Fields B, E, H, Field 01-Q (the Interest Computation Date) and all of the corresponding TC fields will error code. To correct:

    1. Compare the document (Form 3552) and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "Needs one of the following (TC 294, 295, 298, 299, 304, 308, or 309) present with TC 290 or TC 300" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  12. If more than one of these transaction codes (294, 295, 298, 299, 304, 308 and 309) are present, Field 01-Q and the corresponding TC fields will error code. To correct:

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "Interest Computation Date is present with more than one of the Transaction Codes (TCs 294, 295, 298, 299, 304,308, and 309)" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  13. If a TC 294 or TC 298 is present with more than one TC 290 (or any TC 300) in Section 01 through 19, Field 01-Q, and the corresponding transaction code fields will error code. To correct:

    1. Compare the document (Form 3552) and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "TC 294 or TC 298 is present with more than one TC 290 (or (any) TC 300)" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  14. If a TC 304 or TC 308 is present with more than one TC 300 (or any TC 290) in Section 01 through 19, Field 01-Q, and the corresponding transaction code fields will error code. To correct:

    1. Compare the document (Form 3552) and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "TC 294 or TC 298 is present with more than one TC 290 (or (any) TC 300)" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  15. If any Transaction Code 294, 295, 298, 299, 304, 308, OR 309 is present in Section 01 - 19, but the Interest Computation Date (Field 01-Q) is NOT present, Field 01-Q and the corresponding transaction code fields will error code. To correct:

    1. Compare the document (Form 3552) and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "Transaction Codes are present without an Interest Computation Date" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  16. The program will check Credit Transaction Codes 291, 295, 299, 301, 309 (Sections 02-19) against Debit Transaction Codes 290, 294, 295, 298, 299, 300, 304, 308, 309 in Sections 01 through 19 for valid Tax Liability/Carryback combinations.

    Note:

    This applies only to Form 3552 (Doc Code 51) and BMF and IMF. The program will bypass this check if IRAF (MFT 29), if any Transaction Code Error Indicators in Sections 01 through 19 are set, if the Interest Computation Date 01-Q is invalid, or if the Computer Date Error Indicator is set.

  17. If more than one of these (credit) transaction codes (291, 295, 299, 301, and 309) is present, the corresponding TC fields will error code. To correct:

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3,

    4. Notate on Form 4227, "More than one of the credit transaction codes (TCs) is present" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

  18. There must be one debit TC for every credit TC. If none, or more than one of these debit TCs 290, 294, 298, 300, and 308 is present, the credit TC and all corresponding (debit) TC fields will error code. To correct:

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. If none of the debit TCs is present, notate on Form 4227, "None of the debit TCs is present" .

    5. If there are more than one of the debit transaction codes present, notate on Form 4227, "More than one of the debit TCs are present" .

    6. Attach 4227 to the document and route to Accounting for research and correction.

  19. If Transaction Code 298 is present for IMF, it will error code if used with other tax and interest transaction codes. Otherwise, it is the same as a TC 290.

    1. Compare the document and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. If none of the debit transaction codes are present, notate on Form 4227, "TC 298 is present for IMF with other tax and interest TCs" .

    5. Attach 4227 to the document and route to Accounting for research and or correction.

    `

  20. If any transaction code combination is not found in the Tax Liability Carryback Transaction Code Table (see below), both the credit and debit will error code. To correct:

    1. Compare the document (Form 3552) and the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed, reject the record, using Action Code 3.

    4. Notate on Form 4227, "Combination is not found in the Tax Liability Carryback Transaction Code Table" .

    5. Attach 4227 to the document and route to Accounting for research and correction.

    Tax Liability Carryback Transaction Code Table - Debit Transaction Code with Credit Transaction Code

    (Debit) (Credit)
    290 295
    290 299
    294 291
    298 291
    300 309
    308 301
     

Section 02-19 - Fields C, F, and I - Transaction Amount
  1. These fields will be invalid if the amount is signed positive and the related transaction code is not a debit or if the amount is signed negative and the related transaction code is not a credit.

  2. Compare the document and the register. Correct any transcription errors.

  3. If the document is correct as transcribed, reject the record, using Action Code 3.

  4. Notate on Form 4227, "Transaction Amount error" .

  5. Attach 4227 to the document and route to Accounting for research and correction.

Sections 20 Through 23 - Form 3413

  1. This section provides descriptions of the fields and correction procedures for Section 20 through 23 (Form 3413).

Sections 20 Through 23 - Fields A Through L Description

  1. Listed below are the fields contained in Sections 20 through 23.

  2. The alpha-field designator, field length (maximum length for variable fields) and the field title is shown below:

    Field Field Length (+/−) Field Title
    20-23A/E/I 3   Transaction Code
    20-23B/F/J 2   Appropriation Code
    20-23C/G/K 1   Appropriation Indicator
    20-23D/H/L 12 +/− Transaction Amount

  3. Sections 20 through 23 contain transaction codes, appropriation codes, appropriation indicators and transaction amounts. The valid MFT codes for Form 3413 are 02, 05, 08, 17, 30, 31, 33, 34, 35, 46, 65, 85, and 86.

  4. For each transaction, the transaction code, appropriation code, and the transaction amount must be present.

  5. This section will appear invalid if a significant group of fields follows an insignificant (blank) group of fields or if the first group of fields is not present.

Correction Procedures - Sections 20 Through 23

  1. This section provides descriptions of the fields and correction procedures for Section 20 through 23 of the register.

Section 20 Through 23 - Fields A, E, and I - Transaction Codes
  1. The valid debit codes are TC 632 and TC 637.

  2. The valid credit codes are TC 630 and TC 636.

  3. TC 630 and TC 632 are valid only for Doc Code 51 and 52, MFT 02, 05, 08, 17, 30, 31, 33, 34, 46, 85, and 86.

  4. TC 636 and TC 637 are valid only for Doc Code 52, MFT 02, 05, 08, 30, 31, 33, 34, 46, 85, and 86.

  5. The transaction code fields will appear invalid along with the appropriation code fields if the transaction code is 630 or 636 and the appropriation code is other than 02 or the transaction code is 632 or 637 and the appropriation code are other than 03. (See Figure 3.12.21-23.)

    Figure 3.12.21-23

    This is an Image: 33670023.gif

    Please click here for the text description of the image.

    1. Compare the document with the register.

    2. Correct any transcription errors.

    3. If the transaction code is 630 or 636, change Field 20B/F/J to 02.

    4. If the transaction code is 632 or 637, change Field 20B/F/J to 03.

    5. If there is a notation on the document NOT to alter any information, reject with Action Code 3.

    6. Prepare Form 4227 and notate "Doc not to be altered (per doc notation); validate Transaction Code and Appropriate Code"

    7. Attach 4227 to the document and route to originator for research and correction.

  6. The transaction code fields will appear invalid along with the tax period field (Field 01-D) if the transaction code is TC 630 or TC 632 and MFT is 46, 85, or 86 and tax period is before 198412 (i.e., December 1984).

  7. The transaction code fields will appear invalid along with the tax period field (Field 01-D) if the transaction code is TC 630 or TC 632, the MFT is 08, and tax period is before 200412 (i.e., December 2004).

  8. The transaction code fields will appear invalid along with the tax period field (Field 01-D) if the transaction code is TC 630 or TC 632, the MFT is 17 and the tax period is before 200512 (i.e., December 2005).

  9. The transaction code fields will appear invalid along with the tax period field (Field 01-D) if the transaction code is TC 630 or TC 632, the MFT is 17 and the tax period is before 197810 (i.e., October 1978) or after 198011 (i.e., November 1980).

  10. The transaction code fields will appear invalid, along with the tax period field (Field 01-D) if the transaction code is TC 636 or 637, the tax period is before 197810 (i.e., October 1978) or after 198011 (i.e., November 1980).

  11. The transaction code fields and the Appropriations Code fields will appear invalid, if the transaction code is TC 630, TC 632, TC 636, or TC 637, the Appropriations Code is present, and the Doc Code is 52.

    1. Compare the document with the register.

    2. Correct any transcription errors.

    3. If the tax period was transcribed correctly and is invalid, reject the register with Action Code 3.

    4. Notate on Form 4227; "Tax Period invalid with Transaction Code and Appropriation Code" .

    5. Return to originator for correction.

  12. If any transaction code valid for Sections 02-19 is input in Section 20, move the transaction code to the correct section.

Sections 20 Through 23 - Fields B, F, and J - Appropriation Codes
  1. The valid appropriation codes are 02 and 03.

  2. Appropriation Code 02 or 03 must be present when the transaction code field is present.

  3. If an appropriation code is not present or is invalid, enter 02 for a credit or 03 for a debit.

Sections 20 Through 23 - Fields C, G, and K - Appropriation Indicator
  1. This field may be "1" or blank when the related fields are present.

  2. If the indicator is blank, the transaction amount will be included in the math verification for the "CGA" field.

  3. If the appropriation Indicator is "1" , the transaction amount will not be included in the math verification.

Sections 20 Through 23 - Fields D, H, and L - Transaction Amounts
  1. This field must be present for each appropriation transaction code.

  2. The amount is included for math error computation when the related Appropriation Indicator is blank and excluded when the indicator is "1" .

  3. The transaction amount must match (debit or credit) the related transaction code.

  4. If the transaction amount does not match (debit or credit) the related transaction code, do as follows:

    1. Compare the document and the register. Correct any transcription errors.

    2. If the document is correct as transcribed, reject the record, using Action Code 3.

    3. Notate on Form 4227, "Transaction Amount does not match the related transaction code" .

    4. Return to originator for research and corrections.

Sections 30 Through 33 (Valid only for Form 3413)

  1. This section provides descriptions of the fields and correction procedures for Section 30 through 33 (Fields A through I) of the register.

Sections 30 - Through 33 Procedures - Fields A Through I Description

  1. Listed below are fields contained in Sections 30 through 33.

  2. The alpha field designator, field length (maximum length for variable fields) and the field title is shown below:

    Field Field Length Field Title
    30-33A/D/G 8 Status/Interest-to-Date
    30-33B/E/H 3 Status Transaction Code
    30-33C/F/I 8 Statute Extension Date

  3. These sections are valid only for Form 3413. If present for Form 3552, the sections will be coded extraneous.

  4. Sections 30 through 33 contain Status Dates/Interest-To-Dates, Status Transaction Codes, and Statute Extension Dates.

  5. Sections 30 through 33, Fields A, D, and G, Status Date/Interest-To-Date (formerly titled, "Status Transaction Date" ) have been serving a dual purpose since January 1, 1993.

    1. If the corresponding Transaction Code (Sections 30 through 33, Fields B, E, or H) is 340 or 341, the field must contain an Interest-To-Date. Refer to IRM 3.12.21.7.2.2 for correction procedures.

    2. If the corresponding Transaction Code is other than 340 or 341, the field will contain a Status Date. Refer to IRM 3.12.21.7.2.1 for correction procedures.

Correction Procedures - Sections 30 Through 33

  1. This section provides descriptions of the fields and correction procedures for Section 30 through 33 (Fields A, D, and G (Status Transaction) of the register.

Sections 30 Through 33 - Fields A, D, and G - Status/Interest-To-Dates
  1. This field must be all numeric and in YYYYMMDD format. The month must be 01-12, and the day must be 01-31.

  2. The Interest-To-Date is a required field when Transaction Codes 340 or 341 are present in Sections 30 through 33.

  3. If a Transaction Code 340 or 341 is present with a transaction date of 1991-01-01 (i.e., January 1, 1991) or later, a corresponding transaction code entry must be present in Section 02-19. The Section 02-19 entry will include an amount. They must be in the same physical order in both sections. If any of the required fields are missing, all present fields in those sections will be error coded, so that they may be corrected.

  4. Correct as follows:

    1. Compare the document and the register.

    2. If the date was incorrectly transcribed, correct it, using Action Code 6.

    3. If the correct Interest-To-Date can't be determined, reject using Action Code 3.

    4. Prepare Form 4227, Intra-SC Reject or Routing Slip.

    5. Notate on Form 4227, "Interest-to-Date can't be determined" .

    6. Attach 4227 to document and route to originator for research and or correction.

    7. If Transaction Code (TC) 340 (Restricted Interest Assessment) or TC-341 (Restricted Interest Abatement) is present and the Interest-To-Date is missing, reject using Action Code 3.

    8. Prepare a Form 4227 and notate "invalid transaction date" .

    9. Attach 4227 to document and route to originator for research and or correction.

    10. If Transaction Code 340 or TC-341 is present in Sections 30 through 33, but the required identical entry (as stated in paragraph (3) above) is missing, reject using Action Code 3.

    11. Notate on Form 4227, "TC 340/341 present, but, required transaction fields not present" .

    12. Attach 4227 to document and route to originator for research and or correction.

Sections 30 Through 33 - Fields B, E, and H - Status Transaction Codes
  1. These fields are invalid if not one of the status transaction codes listed in Exhibit 3.12.21-5, Valid IMF Transaction Code Table, through Exhibit 3.12.21-7, BMF Valid Transaction Code Table. Certain codes are valid with certain MFT codes only as set forth in the applicable chart. If a transaction code is present, there must also be a status date.

  2. Fields E and H may be blank but must be present if their corresponding status date is present. If the transaction code in the input document is invalid, correct as follows:

    1. Reject the record with Action Code 3.

    2. Prepare Form 4227 for contact with the preparer.

    3. Notate on Form 4227: "Fields E and H are blank, but corresponding Status Date is present" .

    4. Attach 4227 to document and route to preparer for correction.

  3. TC 912 and TC 914 are valid only when both are present and only when they are present an equal number of times.

  4. TC 916 and TC 917 are valid only when both are present and only when they are present an equal number of times.

  5. TC 550, TC 560 and TC 564 are valid only once per document. If TC 550, TC 560 and TC 564 occur more than once in Sections 30 through 33, the duplicate transaction codes will appear invalid.

  6. TC 560 and TC 564 are not valid on the same record. If this occurs all the TC 560 and TC 564 will appear invalid.

  7. TC 550, TC 560, and TC 564 are not valid for IRAF (MFT 29).

  8. Correct as follows:

    1. Compare the document with the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed and the data on the input document is incorrect, reject the record with Action Code 3.

    4. Prepare Form 4227 for contact with the originator.

    5. Notate on Form 4227, "data on input document is incorrect" and route to the originator.

  9. If the Transaction Code (TC) is TC-340 (Restricted Interest Assessment) or TC-341 (Restricted Interest Abatement), a corresponding Interest-To-Date must also be present.

    1. If the Interest-To-Date is missing, reject with Action Code 3.

    2. Prepare Form 4227 for contact with the originator.

    3. Notate on Form 4227, "data on input document is incorrect" and route to originator.

  10. If the Transaction Code is 340 or 341, a TC 340 or 341 must exist in the same physical order in Sections 02 through 19.

    1. If not in the same physical order (disregarding TCs other than 340/341 in sections 02-19 and 30-33), reject using Action Code 3.

    2. Prepare Form 4227 for contact with the originator.

    3. Notate on Form 4227, "TC 340 or 341 not in same physical order in Sections 02 through 19" and route to originator.

Sections 30 Through 33 - Fields C, F, and I - Statute Extension Dates (BMF and IMF only)
  1. The format for these fields is YYYYMMDD.

  2. The date must also meet the validity checks relative to month and day presented for the Status Transaction Dates, good until year 2099.

  3. A date must be present if the corresponding Status Transaction Code is 468, 469, 550, 560, or 564. These fields must be blank for all other status transaction codes. These Transaction Codes will be valid until year 2099.

  4. The Statute Extension Date must be later than the Status Date.

  5. This information is not valid for IRAF (MFT 29).

  6. Correct as follows:

    1. Compare the document with the register.

    2. Correct any transcription errors.

    3. If the document is correct as transcribed and the data on the input document is incorrect, reject the document with Action Code 3.

    4. Prepare Form 4227 for contact with the originator.

    5. Notate on Form 4227, "data on input document is incorrect" and route to the originator.

Sections 30 Through 33 - Missing Field Groups
  1. If Fields A and B are printed, Fields D and E are blank, and Fields G and H are printed; an asterisk is printed before Fields D and E.

  2. Correct by entering the data, leaving no blank intervening fields or sections.

Sections 36 Through 39

  1. This section provides descriptions of the fields and correction procedures for Section 36 through 39 of the register.

Sections 36 Through 39 - Fields A Through F Description

  1. Listed below are the fields contained in Sections 36 through 39.

  2. The alpha-field designator, field length (maximum length for variable fields) and the field titles are shown below:

    Field Field Length (+/−) Field Title
    36-39A/C/E/G* 3   Abstract Number
    36-39B/D/F/H* 12 +/− Abstract Amount

  3. Sections 36 through 39 contain Abstract/IRS Numbers and Abstract Amounts.

  4. Section 36 is valid for all master files.

  5. Section 37 is valid for BMF, MFT 03, 50, 61, and IRAF, MFT 29, 74, 76, 49.

  6. Section 38 is valid with MFT code 03, 50, and 61,74, 76, 49.

  7. Section 39 is valid only with MFTs 03 and 61, 74, 76, 49.

    Note:

    Fields 36-39/G and 36-39/H of Section 01 are valid for Form 3552only.

Correction Procedures - Sections 36 Through 39

  1. This section contains correction procedures for Sections 36 through 39.

Sections 36 Through 39 - Fields A, C, E, and G - Abstract/IRS Numbers
  1. An Asterisk is printed before the field if the Abstract/IRS Number is invalid. The valid Abstract/IRS Numbers are listed as follows:

    MFT-CD Abstract/IRS Number
    02 330 through 333
    03 009 through 024, 026 through 098, 101 through 125, 133, 136, 140, 291, 303 through 310, 322 through 324, 326 through 329, 340 through 390, 392 through 398, 411 through 437
    12 330, 333
    29 160, 162, 194, 195, 233, 235, 236, 237
    34 330 through 333
    44 330 through 333
    49 163, 164
    50 151 through 154, 182, 183, 213, 214, 215, 216, 234, 237, 238, 240
    61 001 through 009, 013 through 035, 040
    74 165, 167, 169
    75 165
    76 159, 161, 163, 164, 165, 167, 169, 200, 201, 203 through 205, 206, 209, 224 through 228, 237, 450, 451, 452.
    77 218
    78 217
    All MFTs except 15, 46, 77, 78, 85, 86 221, 222

    Note:

    * MFT 03 - Abstract Number 125 is valid for Tax Period 200803 and after. MFT 29 - Abstract Numbers 235 or 236 are valid for Tax Periods 200012 (i.e., December 2000) and greater. Abstract 237 is valid for Tax Period 200412 (i.e., December 2004) and after. MFT 50 - Abstract Numbers 151-154 can't appear on the same record as 214, 182, 183. If this occurs, all Abstract Number fields that contain 214, 151-154, 182 or 183 will appear invalid. For Raw Processing, Abstract Numbers 182 and 183 (TC 150) may not appear on the same record. Abstract 234 is valid for Tax Period 199902 (i.e., February 1999) and greater. MFT 50 - Abstract Numbers 215 and 216 are valid for Tax Periods 201712 (December 2017) and later. (See Figure 3.12.21-24.)

    Figure 3.12.21-24

    This is an Image: 33670024.gif

    Please click here for the text description of the image.

  2. Determine the correct Abstract/IRS Number from the Form 3413 or Form 3552 and correct transcription errors.

  3. When there is no Abstract/IRS Number available on the input form, or the correct one can't be determined, from attachments or the table above, use the following Abstract/IRS numbers:

    1. For MFT Code 03, use abstract number 080.

    2. For MFT Code 29, use abstract number 160 or 162.

    3. For MFT Code 50, use abstract number 151.

    4. For MFT Code 61, use abstract number 006.

  4. When the Abstract/IRS Numbers can't be determined (for MFTs listed in the table other than the four listed in Paragraph (3), above), do as follows:

    1. Reject, using Action Code 3.

    2. Prepare Form 4227, Intra-SC Reject or Routing Slip.

    3. Notate on 4227, “Abstract amount blank/missing”, and route to the originator for research and or correction.

  5. Abstract numbers 221 and 222 may appear only once in a record and if one is present, the other must be present. If the abstract number is 221 or 222 the abstract amount must be greater than 0 or both the abstract number and the abstract amount will appear invalid.

  6. If the Abstract Number is 221 or 222 the transaction code must be 340 or 341 or the Abstract Number field will appear invalid.

  7. When there is a Net Tax Assessment associated with Transaction Codes 15X, 29X or 30X in Sections 01-19, there must be a valid abstract number other than 221 and 222.

  8. When Abstract is 227 there must a Transaction Code 290 or 300 in Section 01-19.

Sections 36 Through 39 - Fields B, D, F, and H - Abstract Amount
  1. These fields must be all numeric and have corresponding Abstract/IRS numbers.

  2. Determine the correct abstract amount from the input document and correct the error register.

  3. If the correct amount can't be determined, reject using Action Code 3. Attach Form 4227 for contact with the originator; notate, "Abstract amount blank/missing" .

Sections 36 Through 39 - Missing Field Groups
  1. Both items, abstract number and abstract amount must be present for each transaction group.

  2. An insignificant group (both items missing) indicates no further information in the section.

  3. Use Action Code 6 to fill or blank fields. Delete any unnecessary fields to the right of the last significant field.

Section 40 - Doc Code 51 Only

  1. This section contains field descriptions, correction procedures and related information for Section 40 (Document Code 51 only).

Section 40 - Fields A Through X Descriptions

  1. Listed below are the fields contained in Section 40.

  2. The alpha-field designator, field length (maximum length for variable fields) and the field title is shown below.

    Field Field Length (+/−) Field Title
    40-A 13 + Adj. total of inc. tax withheld (Form 943, Form 945, and Form 941--MFT 01- posted prior to 12/31/2004).
    40-B 13 + Taxable Social Security Wages (Form 941, Form 943, Form 944 and Form 945) (This is also referred to in the programming document as , Taxable FICA Wages Paid Amount)
    40-C 13 +/- Taxable Social Security Wages for qualified sick leave (Form 941, 943, 944)
    40-D 13 +/- Taxable Social Security Wages for qualified family leave (Form 941, 943, 944)
    40-E 13 + Taxable Social Security Tips (Form 941 and Form 944) (In the program, this is Taxable Tips Reported Amount.)
    40-F 13 + Taxable Medicare Wages and Tips (Form 941 and Form 944) (In program specifications this is Taxable Hospital Insurance Benefits Wages.)
    40-G 13 +/- Additional Taxable Medicare Wages and Tips (Form 941)
    40-H 13 +/- Exempt Wages/Tips Paid to Qualified Employees (Form 941, Form 943, and Form 944) (The program specifications calls this Qualified Employer Exempt Wage/Tip Paid Amount)
    40-I 13 +/- Section 3121Q Taxable Amount
    40-J 13 +/- Fractions of Cents (Form 941)
    40-K 13 +/- Current Quarter's Sick Pay Amount (Form 941) Form 944 Current Year's Adjustment (Programming specifications refer to this as CURR-QTR's - Sick Pay (Form 941) Form 944 Current yrs. Adj.)
    40-L 13 +/- Current Quarter's Tips and Group Term Insurance Adjustment (Program specifications refer to this as, CURR-QTR- Tips and Group Term Life Insurance Adjustment.)
    40-M 13 +/- Qualified Small Business Credit - Form 8974 (Form 941, Form 943, and 944)
    40-N 13 +/- Nonrefundable portion of credit for qualified sick and family leave wages (Form 941, 943, 944, CT-1)
    40-O 13 +/- Nonrefundable portion of employee retention credit due to the COVID-19 crisis (Form 941, 943, 944, CT-1)
    40-P 13 +/- Income Tax Withheld Adj. (Form 941 Current), Form 944 Prior Year) (Program specifications refer to this as, Income Tax Withholding - Adjustment. (Form 941 (Current Year), (Form 944 Prior Year).
    40-Q 13 +/- SS and Med. Tax - Adj. (Form 941, Form 943, Form 944 and Form 945) (Program specifications refer to this as Social Security and Medicare Tax - Adjustment (Form 941, Form 943, Form 944 and Form 945.)
    40-R 13 +/- Special Additions to Federal Income Tax (Form 941 and Form 944)
    40-S 13 +/- Special Additions to Social Security and Medicare Tax (Form 941 and Form 944)
    40-T 13 +/- Total Income Tax Withheld from wages (Form 941 and Form 944) posted after 12/31/2004
    40-U 13 + Tips Deemed Wages (Sec 3121g)
    40-V 13 +/- Total Backup Withhold Adj. (Form 945)
    40-W 13 + Gross Income Paid (Form 1042)
    40-X 13 +/- RR Retirement Tax Adj (Form CT-1)

Correction Procedures - Section 40

  1. If there is a field within Section 40 that is not valid for the MFT being processed, the individual field will asterisk. Use the following chart to validate the MFT and Section 40 field presence.

    Section 40 and MFT Code Table

    Field MFT Code
    40-A 01, 11, 16
    40-B 01, 11, 14, 16
    40-C 01, 09, 11, 14
    40-D 01, 09, 11, 14
    40-E 01, 14
    40-F 01, 14
    40-G 01, 11, 14, 16
    40-H 01, 11, 14
    40-I 01
    40-J 01
    40-K 01,14
    40-L 01
    40-M 01, 11, 14
    40-N 01, 09, 11, 14
    40-O 01, 09, 11, 14
    40-P 01,14
    40-Q 01, 11, 14,16
    40-R 01,14
    40-S 01,14
    40-T 01,14
    40-U 01,14
    40-V 16
    40-W 12
    40-X 09
     

  2. If Section 40 is present, the MFT must be 01, 09, 11, 12, 14 or 16 on the Raw Data Run. It is not required on the correction run.

  3. If the input document is a Form 3413 and the tax class is "1" , this section should be present. If the section is not present or the required elements in the section are not present, review the input document and any attachments for the missing data.

    1. If the required data is found, enter the data on the register using Action Code 6.

    2. If the data is not found, enter Action Code 7 to the left of section 01.

    Note:

    If more than an occasional Form 3413 is received without this information, refer this matter to the error correction supervisor, who will contact his/her counterpart in the correct Function, in the Accounting Branch, to ensure the correct preparation of the Form 3413 in the future.

  4. Section 40 is valid when Field 01-G, Original Assessment Transaction Code, is 150, 290, 294, 298, 300, 304, or 308.

  5. IMPORTANT: The program is set up to validate the credit transaction codes against the debit transaction codes. If any of the following combinations in the following Tax Liability Carryback table is not found, then both the credit and debit transaction codes will be set to error. To correct:

    1. Compare the input document against the correct field on the register.

    2. Correct transcription errors, if any.

    3. Using the table below, compare the correct Debit/Credit combinations.

    4. If the required data is found, enter the data on the register, using Action Code 6.

    5. If the data is not found, enter Action Code 7 to the left of the section.

    Tax Liability Carryback Table - Debit Transaction Code with Credit Transaction Code

    Debit Credit
    290 295
    290 299
    294 291
    298 291
    300 309
    308 301
     

  6. This section is not valid with doc code 52 records. An extraneous section (#) will result if any data is present in Section 40. If the doc code is 52, delete Section 40 with Action Code 4.

Section 40 - Field Requirements - Fields A Through X
  1. Field 40-A-Adjustment Total of Income Tax Withheld (Form 943, Form 945, and Form 941 - MFT 01---posted prior to 12/31/2004)

    1. This information is found under Item A (Section 40), Page 2, Form 3413; also, Line 1, Page 1, Form 3552).

    2. This field is valid for MFT 01,11, and 16.

    3. IMPORTANT:: On original input, this field, plus Field 40-B, Taxable Social Security Wages, and Field 40-T, Total Income Tax Withheld, must equal the net of all transaction codes 29X and 30X. If invalid or Math Error, Clear with Action Code 7.

  2. Field 40-B-Taxable Social Security Wages (Form 941, Form 943, Form 944 and Form 945)

    1. This information is found under Item B (Section 40), Page 2, Form 3413; also, Line 2, Page 1, Form 3552.).

    2. This field is valid for MFT 01,11,14, and 16.

    3. If the doc code is 51, MFT is 01, 11, 14, or 16 and Field 40-B equals zero, Field 40-B will appear invalid. If invalid or Math Error, Clear with Action Code 7.

  3. Field 40-C, Taxable Social Security Wages for qualified sick leave (Form 941, Form 943, Form 944)

    1. This information is found under Item C (Section 40), Page 2, Form 3413; also, Line 2a, Page 1, Form 3552.).

    2. This field is valid for MFT 01, 09, 11 and 14.

    3. If the doc code is 51, MFT is 01, 09, 11, or 14 and Field 40-C equals zero, Field 40-C will appear invalid. If invalid or Math Error, Clear with Action Code 7.

  4. Field 40-D, Taxable Social Security Wages for qualified family leave (Form 941, Form 943, Form 944)

    1. This information is found under Item D (Section 40), Page 2, Form 3413; also, Line 2b, Page 1, Form 3552.).

    2. This field is valid for MFT 01, 09, 11 and 14.

    3. If the doc code is 51, MFT is 01, 09, 11, or 14 and Field 40-D equals zero, Field 40-D will appear invalid. If invalid or Math Error, Clear with Action Code 7.

  5. Field 40-E-Taxable Social Security Tips (Form 941 and Form 944)

    1. This information is found under Item E (Section 40), Page 2, Form 3413 (also, Line 3, Page 1, Form 3552).

    2. This field is valid for MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-E.

  6. Field 40-F-Taxable Medicare Wages and Tips (Form 941 and Form 944)

    1. This information is found under Item F (Section 40), Page 2, Form 3413 (also, Line 4, Page 1, Form 3552).

    2. This field is only valid with MFT 01 and 14.

    3. If Field 40-F is different from the amount on the form, strike through the entry on the register. Edit the correct amount above it and correct with Action Code 6.

    4. If Field 40-F is correct as entered, accept with Action Code 7.

    5. If invalid on another MFT, delete Field 40-F.

  7. Field 40-G-Additional Taxable Medicare Wages and Tips (Form 941, Form 943, Form 944, and Form 1041 (This field is only valid with MFt 01 (Form 941), MFT 11 (Form 943), MFT 14 (Form 944), and MFT 16 (Form 945).)

    1. This information is found under Item G (Section 40), Page 2, Form 3413; also, Line 5, Page 1, Form 3552).

    2. This field is only valid with MFT 01 (Form 941), MFT 11 (Form 943), MFT 14 (Form 944), and MFT 16 Form 945).

    3. If Field 40-G is different from the amount on the form, strike through the entry on the register. Edit the correct amount above it and correct with Action Code 6.

    4. If Field 40-G is correct as entered, accept with Action Code 7.

    5. If invalid on another MFT, deleted Field 40-G.

  8. Field 40-H-Exempt Wages/Tips Paid to Qualified Employees (Form 941, Form 943, and Form 944)

    1. This information is found under Item H (Section 40), Page 2, Form 3413 (also, Line 6, Page 1, Form 3552).

    2. This field is only valid with MFT 01 (Form 941), MFT 11 (Form 943), and MFT 14 (Form 944).

    3. If Field 40-H is different from the amount on the form, strike through the entry on the register. Edit the correct amount above it and correct with Action Code 6.

    4. If Field 40-H is correct as entered, accept with Action Code 7.

    5. If invalid on another MFT, delete Field 40-H.

  9. Field 40-I-Section 3121Q Tax Amount

    1. This information is found on Item I (Section 40), Page 2, Form 3413 (also, Line 7 ("SECT 3121Q Tax Amt." ) of the Form 3552).

    2. This field is only valid with MFT 01 (Form 941).

    3. If invalid on another MFT, delete Field 40-I.

  10. Field 40-J-Fractions of Cents - Adjustment (Form 941)

    1. This information is found under Item J (Section 40), Page 2, Form 3413 (also, Line 8, Page 1, Form 3552).

    2. This field is only valid with MFT 01.

      Note:

      Currently, the program does not accept this item with MFT 14 (Form 944).

    3. If Field 40-J is different from the amount on the form, strike through the entry on the register. Edit the correct amount above it and correct with Action Code 6.

    4. If Field 40-J is correct as entered, accept with Action Code 7.

    5. If an amount is present in this field for MFT 11 use Action Code 7 to accept taxpayer information.

    6. If invalid on another MFT, delete Field 40-J.

    7. REMINDER: This field is not valid for MFT 14. If Field 40-J was deleted on Raw but continues to loop with an asterisk (*), reject with Action Code 3. Attach Form 4227, notating, "Fraction of Cents - Adjustment is not valid for MFT 14 (Form 944)" .

  11. Field 40-K-Current Quarter's Sick Pay (Form 941) Form 944 Current Year's Adjustment

    1. This information is found under Item K (Section 40), Page 2, Form 3413; also, Line 9, Page 1, Form 3552).

    2. This field is valid with MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-K.

      Note:

      Field 40-K is positive and negative for Form 3552 ONLY.

  12. Field 40-L-Current Quarter's Tips and Group Term Insurance Adjustment

    1. This information is found under Item L (Section 40), Page 2, Form 3413; also, Line 10, Page 1, Form 3552).

    2. This field is only valid with doc code 51, MFT 01 (01 only prior to 199412).

    3. If invalid on another MFT, delete Field 40-L.

      Note:

      Field 40-L is positive and negative for Form 3552 and Form 3413.

  13. Field 40-M-Qualified Small Business Credit - Form 8974(Form 941, Form 943 and Form 944)

    1. This information is found under Item M (Section 40), Page 2, Form 3413; also, Line 11a, Page 1, Form 3552).

    2. This field is valid for MFT 01, MFT 11, and MFT 14.

    3. Valid tax periods are 201712 and later

    4. Valid transaction codes are 29X/30X.

    5. If invalid on another MFT, delete Field 40-M.

  14. Field 40-N, Nonrefundable portion of credit for qualified sick and family leave wages (Form 941, Form 943, Form 944, Form CT-1)

    1. This information is found under Item N (Section 40), Page 2, Form 3413; also, Line 11b, Page 1, Form 3552).

    2. This field is valid for MFT 01, MFT 09, MFT 11, and MFT 14.

    3. If invalid on another MFT, delete Field 40-N.

  15. Field 40-O, Nonrefundable portion of employee retention credit due to the COVID-19 crisis (Form 941, Form 943, Form 944, Form CT-1)

    1. This information is found under Item O (Section 40), Page 2, Form 3413; also, Line 11c, Page 1, Form 3552).

    2. This field is valid for MFT 01, MFT 09, MFT 11, and MFT 14.

    3. If invalid on another MFT, delete Field 40-O.

  16. Field 40-P-Income Tax Withheld Adjustment (Form 941; Current Year), Form 944 (Prior Year)

    1. This information is found under Item P (Section 40), Page 2, Form 3413; also, Line 12, Page 1, Form 3552 ).

    2. This field is valid for MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-P.

  17. Field 40-Q-SS and Med. Tax- Adj.; (Form 941, Form 943, Form 944 and Form 945) (Social Security and Medicare Tax - Adjustment (Form 941, Form 943, Form 944 and Form 945)

    1. This information is found under Item Q (Section 40), Page 2, Form 3413; also, Line 13, Page 1, Form 3552).

    2. This field is valid for MFT 01,11,14 and 16.

    3. If invalid on another MFT, delete Field 40-Q.

      Note:

      Field 40-Q is positive and negative for Form 3552 ONLY.

  18. Field 40-R-Special Addition to Federal Income Tax (Form 941 and Form 944)

    1. This information is found under Item R (Section 40), Page 2, Form 3413; also, Line 14, Page 1, Form 3552).

    2. This field is valid for MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-R.

  19. Field 40-S---Special Additions to Soc. Sec. and Med. Tax (Form 941 and Form 944)

    1. This information is found under Item S (Section 40), Page 2, Form 3413; also, Line 15, Page 1, Form 3552).

    2. This field is valid for MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-S.

  20. Field 40-T---Total Income Tax Withheld from wages (Form 941 and Form 944) posted after 12/31/2004

    1. This information is found under Item T (Section 40), Page 2, Form 3413; also, Line 16, Page 1, Form 3552).

    2. This field is valid for MFT 01 and 14.

    3. If invalid on another MFT, delete Field 40-T.

  21. Field 40-U---Tips Deemed Wages (Sec. 3121q)

    1. This information is found under Item U (Section 40), Page 2, Form 3413; also, Line 17, Page 1, Form 3552).

    2. This field is valid for MFT 01 and 14

    3. If invalid on another MFT, delete Field 40-U.

  22. Field 40-V---Total Backup Withholding - Adjustment (Form 945)

    1. This information is found under Item V (Section 40), Page 2, Form 3413; also, Line 18, Page 1, Form 3552).

    2. This field is valid for MFT 16.

    3. If invalid on another MFT, delete Field 40-V.

  23. Field 40-W---Gross Income Paid (Form 1042)

    1. This information is found under Item W (Section 40), Page 2, Form 3413; also, Line 19, Page 1, Form 3552).

    2. This field is valid for MFT 12

    3. If invalid on another MFT, delete Field 40-W.

  24. Field 40-X---RR Retirement Tax Adjustment (Form CT-1)

    1. This information is found under Item X (Section 40), Page 2, Form 3413; also, Line 20, Page 1, Form 3552).

    2. This field is valid for MFT 09.

    3. This field must be blank for all other MFTs. If invalid on another MFT, delete Field 40-X.

Section 41 - Form 3552 only

  1. This section contains correction procedures and related information for Section 41 (Form 3552 only).

Section 41 - Fields A Through H Description

  1. Listed below are the fields contained in Section 41.

  2. The alpha-field designator, field length (maximum length for variable fields) and the field title is shown below:

    Field Field Length (+/−) Field Title
    41-A 13 + Total Taxable Form 940 Wages
    41-A 13 + Total Taxable Form 940 Wages Computer
    41-B 13 + Total Amount Credit Reduction
    41-B 13 + Total Amount Credit Reduction Computer
    41-C 2   State Code
    41-D 12 + Credit Reduction Wages
    41-E 2   State Code
    41-F 12 + Credit Reduction Wages
    41-G 2   State Code
    41-H 12 + Credit Reduction Wages

  3. Section 41 must be present for Form 3552, Doc Code 51, if the tax class is 8, the MFT is 10 and there is either a TC 150, 29X or 30X. (See Figure 3.12.21-25.)

    Figure 3.12.21-25

    This is an Image: 33670025.gif

    Please click here for the text description of the image.

  4. This section must not be present for Form 3413.

  5. If an amount is present in Field 41-A, Total Taxable 940 Wages, there must be an entry in Field 41-C, State Code. Search the document for the valid entries for these fields. If valid entries can't be located, reject the document with Action Code 3.

    Note:

    The "Taxable Total Wages" and the "State Code" information may be located in the bottom part of Form 3552.

    Note:

    If a State Code can't be found and you are rejecting the document, issue a Form 4227 (Intra-SC Reject or Routing Slip) and notate on the form "need valid entry for Field 41-C (State Code)" .

  6. A state code may not occur more than once per document.

  7. There can be no spaces between groups of state codes and wages. Missing fields will appear invalid. Move the data to fill the spaces.

Correction Procedures - Section 41

  1. Field 01-G, Transaction Code, and Field 41-C, State Code, will appear invalid if the MFT is 10 and the transaction code in section 01 is other than 150. (See Figure 3.12.21-26.)

    Figure 3.12.21-26

    This is an Image: 33670026.gif

    Please click here for the text description of the image.

  2. Compare the document with the register and correct any transcription errors.

    Note:

    The Section 41 data (i.e., "Taxable 940 Wages" , "Total Amount C. R. (Credit Reduction)" , "State Code" and "Credit Reduction" ) may be found in the bottom part of the Form 3552.

  3. If correct as transcribed, and the transaction code is other than 150, reject with Action Code 3. Notate on Form 4227, "Must have TC 150 when Credit Reduction data is present" .

  4. If the transaction code is 150, Section 41 will asterisk (*) as missing if the MFT is 10, Doc Code 51, Form 3552, Tax Class 8 and Section 41 is blank. (See Figure 3.12.21-27.)

    Figure 3.12.21-27

    This is an Image: 33670027.gif

    Please click here for the text description of the image.

    1. Compare the document with the register.

    2. If the data is present on the document for Section 41 (in addition to the other items listed in Paragraph (4) above), correct the register with Action Code 6.

      Note:

      The Section 41 data (i.e., "Taxable 940 Wages" , "Total Amount C. R. (Credit Reduction)" , "State Code" and "Credit Reduction" , may be found in the bottom part of the Form 3552.

    3. If Section 41 data is not present on the document, verify that MFT (Field 01-C), is correct. If so, reject with Action Code 3.

    4. Prepare Form 4227 with the notation, "MFT is 10, but Section 41 is blank" or "Credit Reduction Data required" .

    5. Attach 4227 to the document and route to the originator for research and or correction.

  5. Compare the data on the document and the register against Exhibit 3.12.21-9, Credit Reduction Chart. If the Credit Reduction data (either) is NOT valid OR is not valid for the correct year:

    1. Reject with Action Code 3.

    2. Prepare Form 4227 with the notation, "Credit Reduction Data is not valid" or "Credit Reduction Data is not valid for the correct year" .

    3. Attach 4227 to the document and route to originator for research and or correction.

  6. Section 41 will appear on the register as extraneous (#) if the MFT is other than 10 and there is data present in Section 41. See Figure 3.12.21-28.

    Figure 3.12.21-28

    This is an Image: 33670028.gif

    Please click here for the text description of the image.

    1. Compare the document with the register and correct any transcription errors.

      Note:

      The Section 41 data (i.e., "Taxable 940 Wages" , "Total Amount C. R. (Credit Reduction)" , "State Code" and "Credit Reduction" may be found in the bottom part of the Form 3552

      .

    2. If the MFT is other than 10, delete Section 41 with Action Code 4.

  7. If Field 01-G is 150, and there is an entry in Field 41-A and 41-B, a valid Credit Reduction State and Credit Reduction Wages must be present. If missing:

    1. Reject with Action Code 3 and enter the state code from entity in Field 41-C.

    2. Notate on Form 4227, "Must have credit reduction state and or wages amount."

    3. Attach 4227 to document and route to originator.

  8. Field 41-B, Total Credit Reduction, is computed using the sum of Credit Reduction Wages in Sections 41-46, multiplied by the percentage shown for each state in Exhibit 3.12.21-9. This field will underprint if a math error exists. See Figure 3.12.21-29.

    Figure 3.12.21-29

    This is an Image: 33670029.gif

    Please click here for the text description of the image.

    1. Compare the document with the register and correct any transcription errors.

    2. If correct as transcribed, reject with Action Code 3, and bring up underprint in Field 41-B.

    3. Prepare Form 4227 with the notation, "Credit Reduction amount incorrect" .

    4. Attach Form 4227 and document and route to the originator for research and or correction.

    5. IMPORTANT: Also read information in "Note" below.

    Note:

    If Field 41-B underprints, check to see if the amounts in Field 41-B and Field 41-D are in each other's field. Field 41-D will always be larger than Field 41-B. If they are, switch Field 41-B and Field 41-D. If Field 41-B re-underprints, either reject or send to Accounting.

  9. If Field 41-B underprints and a State Code Field has an invalid credit reduction state, see Exhibit 3.12.21-9, Credit Reduction Chart, to correct any transcription errors.

    1. If unable to determine the Credit Reduction State, reject with Action Code 3.

    2. Prepare Form 4227, notating, "Credit Reduction state invalid" .

    3. Attach 4227 to document and send to originator.

  10. The State Code field and Credit reduction Wages field will appear invalid if a valid credit reduction state is in the State Code field, a TC 150 is in Section 01, and the Credit Reduction Wages field is blank. See Figure 3.12.21-30Figure 3.12.21-30.

    Figure 3.12.21-30

    This is an Image: 33670030.gif

    Please click here for the text description of the image.

    1. Compare the document with the register and correct any transcription errors.

    2. If correct as transcribed, search the document for valid credit reduction wages.

    3. If you can't determine the valid credit reduction wages, reject the record with Action Code 3.

    4. Prepare Form 4227 with notation, "Credit Reduction info not determined" .

    5. Route 4227 to documentation to the originator for missing information.

  11. The State Code field and associated significant (greater than zero) Credit Reduction Wages field will error code if Transaction Code 150 is not present in Section 01. (See Figure 3.12.21-31.)

    Figure 3.12.21-31

    This is an Image: 33670031.gif

    Please click here for the text description of the image.

    1. Compare the document with the register and correct any transcription errors.

    2. If the document is correct as transcribed, reject the record with Action Code 3.

    3. Prepare Form 4227 with notation, "Credit Reduction wages without TC 150" .

    4. Route 4227 to documentation and send to the originator.

  12. Field 01-D, Tax Period, State Code field, and Credit Reduction Wages field (greater than zero) will appear invalid when there is no TC 150 in Section 01 and Credit Reduction Wages field is present; the State Code field is blank and Credit Reduction Wages field is present or an invalid credit reduction state for the tax period is present. See Figure 3.12.21-32.

    Figure 3.12.21-32

    This is an Image: 33670032.gif

    Please click here for the text description of the image.

    1. Compare the document with the register and correct any transcription errors.

    2. If the document is correct as transcribed, reject with Action Code 3.

    3. Prepare Form 4227either with notation, "Credit Reduction wages without TC 150 and other Credit Reduction information" . or"Invalid credit reduction state for the tax period is present without TC 150" .

    4. Attach 4227 to document and route to the originator.

Sections 42 Through 46 -Form 3552 only

  1. This section contains correction procedures and related information for use with Sections 42 through 46 (for Form 3552 only).

Sections 42 Through 46 - Fields A Through T Description

  1. Listed below are the fields contained in Sections 42 through 46.

  2. The alpha-field designators, field lengths (maximum length for variable fields) and the field titles are shown below.

    Field Field Length (+/−) Field Title
    42-46A 2   State Code
    42-46B 12 + Credit Reduction Wages
    42-46C 2   State Code
    42-46D 12 + Credit Reduction Wages
    42-46E 2   State Code
    42-46F 12 + Credit Reduction Wages
    42-46G 2   State Code
    42-46H 12 + Credit Reduction Wages
    42-46I 2   State Code
    42-46J 12 + Credit Reduction Wages
    42-46K 2   State Code
    42-46L 12 + Credit Reduction Wages
    42-46M 2   State Code
    42-46N 12 + Credit Reduction Wages
    42-46O 2   State Code
    42-46P 12 + Credit Reduction Wages
    42-46Q 2   State Code
    42-46R 12 + Credit Reduction Wages
    42-46S 2   State Code
    42-46T 12 + Credit Reduction Wages

  3. A state code may not occur more than once per document.

  4. There can be no missing fields between groups of state codes and wages. Missing fields will appear invalid. Move the data to fill the spaces.

Correction Procedures -Sections 42 Through 46

  1. This section contains validity information and procedures for use in correcting Sections 42 through 46.

Sections 42 Through 46 - State Code Fields
  1. The valid State Codes are AK, AL, AR, AZ, CA, CO, CT, DC, DE, FL, GA, HI, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NJ, NY, NM, NV, NY, OH, OK, OR, PA, PR, RI, SC, SD, TN, TX, UT, VA, VI, VT, WA, WI, WV, and WY.

  2. The State Code field and Credit Reduction Wages field will appear invalid if the State Code field (see Exhibit 3.12.21-9) is blank and the Credit Reduction Wages field is present.

    1. Compare the document with the register. Correct any transcription errors.

    2. If the document is correct as transcribed, reject the record with Action Code 3. Attach Form 4227 and send to the originator with notation, "Credit Reduction wages present; State Code blank" .

    Note:

    The Section 42 data (i.e., "State Code" and "Credit Reduction" fields are found in the bottom part of the Form 3552.

Sections 42 Through 46 - Credit Reduction Wages Fields

  1. The State Code field and Credit Reduction Wages field will appear invalid if a valid credit reduction state (see Exhibit 3.12.21-9) is in the State Code field and the Credit Reduction Wages field is blank.

  2. Compare the document with the register. Correct any transcription errors.

  3. If the document is correct as transcribed, reject the record with Action Code 3.

  4. Attach Form 4227 with notation, "State Code field present; Credit Reduction Wages blank" .

  5. Route the 4227 to the document to the originator

Math Errors

  1. This section contains information and procedures for use with correcting math errors.

    1. Balance Transferred In-Field 01-I - Underprint - See IRM 3.12.21.12.1

    2. Abstract Math Error Net Assessment-Sections 36-39 See IRM 3.12.21.12.2 and IRM 3.12.21.12.3

    3. TC 29X-30X Net CGA-Math Error See IRM 3.12.21.12.4

Balance Transferred-In - Field 01-I - Underprint Amount

  1. A math error is indicated by printing the computer-generated amount (CGA) under Field 01-I on the register.

  2. Compare all the amount fields in Sections 01-19 and Reference Amount on the register with the input document. Sections 20-23 are also included in the computation when the Appropriation Indicator is blank. This sum must equal Field 01-I.

  3. If a transcription error is found, correct the register with Action Code 6.

    Note:

    FIELD 01-I, BALANCE TRANSFERRED IN, MAY NOT BE CHANGED.

  4. If no transcription error is found in the amount fields, determine if the transaction codes agree with the sign accompanying the amount fields. Both the transaction code field and the amount field will appear invalid if the transaction code does not agree with the sign of the transaction amount field. The valid transaction codes for BMF, IMF and IRAF are listed in the Exhibits at the end of this IRM.

    1. If the sign of the transaction amount is in error, correct the register by entering a comma (,) for debit or a pound sign (#) for credit as field breakers.

    2. If the transaction code is in error, determine the correct code and correct the register.

  5. If the document has been prepared from an attached transcript, examine the transcript to determine if an error has been made in the preparation of the document.

    Note:

    IF TC 402 IS ON THE Form 3413 IN SECTION 01, MAKE THE PROPER CHANGES TO CORRECT THE PROBLEM.

  6. When any of the following transaction codes are invalid for the doc code being processed, they may be converted to the following equivalent valid transaction code.

    TC Convert To TC Convert To
    163 160 673 670
    166 160 706 700
    167 161 716 710
    176 170 736 730
    177 171 756 700
    186 180 768 764
    196 190 776 770
    197 191 777 771 (BMF)
    238 234 796 790
    239 235 806 800
    246 240 807 802
    276 270 836 830
    277 271 842 841
    286 280 846 840
    336 340 or 190 856 850
    337 341 876 850
    386, 388,389 Do not add    
    606 600 896 820
    613 610 897 822
    663 660    
    666 700    
    667 820    

  7. If no change is to be made to an amount, an amount sign, or transaction code, or if an amount is added and there is still a math error, reject the document, using Action Code 3.

    1. Prepare Form 4227 and notate as follows: "Math error continues to appear; no obvious correction found" .

    2. Attach 4227 to document and route to originator for research and or correction.

Abstract Math Error Net Assessment - Sections 36-39

  1. An Abstract Math Error will be located under the last Section present of the register.

  2. This math check is performed only if the Doc Code is 51, the MFT is 03, 29, 50, 61, 76, 77, or 78 and TC 15X, TC 29X or TC 30X is present in sections 01-19. Also refer to Exhibit 3.12.21-10 (TC 150 Abstract versus Tax Period Table) and Exhibit 3.12.21-11 (TC 290-30X Abstract versus Tax Period Table) and see Figure 3.12.21-33 for other information.

  3. The computation is the sum of all the abstract amounts contained in Sections 36 through 39 except those amounts associated with Abstract Numbers 221 and 222.

  4. An abstract amount error is indicated by printing the computer-generated net tax assessment amount, which is the sum of all TC 15X, 29X and 30X amounts in Sections 01-19, on the math error line of the register.

    Figure 3.12.21-33

    This is an Image: 33670033.gif

    Please click here for the text description of the image.

  5. If the Net Tax Assessment Computer-Generated Amount is greater than zero (0), Sections 36-39 must contain an abstract amount other than those associated with Abstract Numbers 221 and 222.

Abstract Math Error Net Assessment - Sections 36-39 (Correction Procedures)

  1. Compare the document with the register. Correct any transcription errors.

  2. This math check is performed only if the Doc Code is 51, the MFT is 03, 29, 50, 61, 76, 77 or 78 and TC 15X, TC 29X or TC 30X is present in sections 01-19. Also refer to Exhibit 3.12.21-10 (TC 150 Abstract Versus Tax Period Table), Exhibit 3.12.21-11 (TC 290-30X Abstract Versus Tax Period Table) and Figure 3.12.21-33 for more information.

  3. If the document was transcribed correctly or there are no abstract numbers and amounts present, add section 36 to the register, using the following abstract numbers, for the Net Tax Assessment Amount.

    1. Use Abstract 080 for Form 720, Quarterly Federal Excise Tax Return.

    2. Use Abstract 006 for Form 11, Special Tax Return and Application for Registry.

    3. Use Abstract 151 for Form 4720, Return of Certain Excise Taxes on Charities and Other Persons Under Chapters 41 and 42 of the IRC.

    4. Use Abstract 160 for Form 5329, Additional Taxes on Qualified Plans (Including IRAs) and Other Tax-Favored Accounts.

  4. If the abstract amounts are present in Sections 36-39 and do not equal the net tax assessment, reject, using Action Code 3. Attach Form 4227 and send to Accounting for contact with the originator. Notate as follows: "Abstract amounts do not equal net tax assessment" .

TC 29X/30X Net-CGA - Math Error

  1. A TC 29X/30X Net-CGA Math Error will be located under the last section present on the register. (See Figure 3.12.21-34.) Also refer to Exhibit 3.12.21-10 (TC 150 Abstract versus Tax Period Table) and Exhibit 3.12.21-11 (TC 290-30X Abstract versus Tax Period Table) for more information.

    Figure 3.12.21-34

    This is an Image: 33670034.gif

    Please click here for the text description of the image.

  2. The computation of TC 29X/30X Net-CGA is the sum of all Transaction Codes 29X and 30X in Sections 01 through 19. The Total Tax-CGA is the sum of Fields 40-M, Total Income Tax Withheld, 40-J, Adjusted Total Social Security Tax, and 40-O, Adjusted Total Backup Withholding.

    1. Compare the document with the register. Correct any transcription errors with Action Code 6.

    2. Raw input only: If the document is correct as transcribed, clear the register with Action Code 7.

    Note:

    If more than an occasional Form 3552 is received without this information, refer this matter to the Error Correction supervisor who will contact his/her counterpart in the Account Transfer Function, Accounting Branch, to ensure the correct preparation of Form 3552 in the future.

Valid Tax Periods

MFT-CD BMFTX/PRD END TX/PD EARLIEST DATE ALLOWED MM-LIMITS
01 196203 YYYY12 TAX-PRD minus 2 months 3, 6, 9, 12
02 196112 YYYY12 TAX-PRD minus 11 months 1-12
03 196203 YYYY12 TAX-PRD minus 2 months 3, 6, 9, 12
04 196203 199412 TAX-PRD minus 2 months 3, 6, 9, 12
05/06 196112 YYYY12 TAX-PRD minus 11 months 1-12
07 198712 YYYY12 TAX-PRD minus 11 months 12
08 200412 YYYY12 TAX-PRD minus 11 months 1-12
09 196203 197512 TAX-PRD minus 2 months 3, 6, 9, 12
09 197612 YYYY12 TAX-PRD minus 11 months 12
10/11 196112 YYYY12 TAX-PRD minus 11 months 12
12 198512 YYYY12 TAX-PRD minus 11 months 12
13 # 198012 YYYY12 TAX-PRD minus 11 months 12
14 200612 YYYY12 TAX-PRD minus 11 months 12
15 199012 YYYY12 TAX-PRD minus 11 months 12
16 199412 YYYY12 TAX-PRD minus 11 months 12
17 200512 YYYY12 TAX-PRD minus 11 months 1-12
33 196112 200611 TAX-PRD minus 11 months 1-12
34 196112 YYYY12 TAX-PRD minus 11 months 1-12
35, 65 201412 YYYY12 TAX-PRD minus 11 months 1-12
36 197012 YYYY12 TAX-PRD minus 11 months 1-12
37 197001 198712 TAX-PRD minus 11 months 1-12
37 198812 YYYY12 TAX-PRD minus 11 months 12
40 200401 YYYY12 TAX-PRD minus 11 months 1-12
43 201512 YYYY12 TAX-PRD minus 11 months 12
44 197001 YYYY12 TAX-PRD minus 11 months 1-12
46 198412 YYYY12 TAX-PRD minus 11 months 1-12
47 200007 YYYY12 TAX-PRD minus 11 months 1-12
49 200007 YYYY12 TAX-PRD minus 11 months 1-12
50 197001 YYYY12 TAX-PRD minus 11 months 1-12
51 196112 197012 TAX-PRD minus 11 months 12
51 197103 198112 TAX-PRD minus 2 months 3, 6, 9, 12
51 198212 YYYY12 TAX-PRD minus 11 months 12
52 000000 000000 12/01/1961  
58 197007 198009 TAX-PRD 1-12
60 * 195607 YYYY12 TAX-PRD 1-12
61 * 196206 198706 TAX-PRD 1-12
62 * 196206 198006 TAX-PRD 1-12
63 * 196206 YYYY12 TAX-PRD 1-12
64 * 196206 YYYY12 TAX-PRD minus 1 month 1-12
65 201412 YYYY12 TAX-PRD minus 11 months 1-12
67 197012 YYYY12 TAX-PRD minus 11 months 1-12
74 198412 YYYY12 TAX-PRD minus 11 months 1-12
75 1974 YYYY12 TAX-PRD minus 11 months 1-12
76 198412 YYYY12 TAX-PRD minus 11 months 1-12
77/78 198612 YYYY12 TAX-PRD minus 11 months 12
79 201409