3.12.249. Processing Form 8752

(1) Partnerships and S Corporations use Form 8752 to figure and report the payment required under Section 7519 or to obtain a refund of net prior year payments.

(2) Error Resolution tax examiners resolve validity errors, field errors, and consistency errors, on returns using paper error registers. Employees use the paper register (error register) and the return to correct these conditions and when necessary use Integrated Data Retrieval System (IDRS) to research.

(1) Authority for these procedures is found in Internal Revenue Code Section 7519 and corresponding Treasury Regulations.

(2) All Policy Statements for Submission Processing are in IRM 1.2.1, Servicewide Policies and Authorities, Servicewide Policy Statements.

(1) Submission Processing (SP), Paper Processing Branch (PPB), BMF Code and Edit (C&E) and Error Resolution System (ERS) Section follows the content in this IRM. The BMF ERS analyst makes updates as needed and revises content once a year effective January 1st of each calendar year.

(2) The BMF Code and Edit and Error Resolution System Section Manager ensures the IRM is timely sent to Publishing each year.

(3) The Campus Director monitors operational performance for the Submission Processing campus.

(4) The Operations Manager monitors operational performance for their operation.

(5) The Team Manager/Lead monitors performance and ensures employees have the tools to perform their duties.

(6) The Team Employees follow the instructions in this IRM and keep updated on the IRM procedures.

(1) Program Goals: Enter corrections on the Form 8752 paper error registers for any errors falling out through Service Center Replacement System (SCRS) in Error Resolution.

(2) Program Reports: System control reports are on the Control-D WebAccess (CTDWA) and a general listing of the reports is found in IRM 3.12.38, Error Resolution, BMF General Instructions.

(3) Program Effectiveness: The program goals are measured by using the following tools:

• Embedded Quality Submission Processing (EQSP)

• Balanced Measures

• Managerial Reviews

(4) Annual Review: The processes outlined in this IRM are reviewed annually during IRM Review and Clearance to ensure accuracy and promote consistent tax administration.

(1) Quality Review conducts a statistical valid sample size review of completed work to ensure IRM guidelines are followed.

(1) The table lists Interpretation Words and their definitions.Interpretation Words

(2) See Exhibit 3.12.249-3, Acronyms and Abbreviations, for a list of commonly used acronyms and abbreviations.

(1) The following table lists related resources.Related Resources

(1) Submit IRM deviations in writing following instructions from IRM 1.11.2.2.4, When Procedures Deviate from the IRM, and elevate through proper channels for executive approval.

(1) The Taxpayer Advocate Service (TAS) is an independent organization within the Internal Revenue Service (IRS), led by the National Taxpayer Advocate. Its job is to protect taxpayers’ rights by ensuring that every taxpayer is treated fairly and knows and understands their rights under the Taxpayer Bill of Rights (TBOR). TAS offers free help to taxpayers, including when taxpayers face financial difficulties due to an IRS problem, when they are unable to resolve tax problems they haven’t been able to resolve on their own, or when they need assistance to address an IRS system, process, or procedure that is not functioning as it should. TAS has at least one taxpayer advocate office in every state, the District of Columbia, and Puerto Rico.

(2) TAS uses Form 12412, Operations Assistance Request (OAR), to start the OAR process of referring a case to the Wage and Investment (W&I) Division, to affect the resolution of the taxpayer’s problem. For more information, refer to IRM 13.1.19, Taxpayer Advocate Service, Taxpayer Advocate Case Procedures, Advocating With Operations Assistance Requests (OARs).

(3) Refer taxpayers to TAS when the contact meets TAS criteria or when Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order), is attached and steps cannot be taken to resolve the taxpayer's issue the same day.

(4) The definition of "same day resolution" is within 24 hours. The following two situations meet the definition of "same day resolution":

• The issue can be resolved within 24 hours.

• IRS takes steps within 24 hours to resolve the taxpayer’s issue.

(5) When making a TAS referral, use Form 911, and forward to TAS following your local procedures.

(6) For more information, see IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria.

(1) BMF ID Theft is increasing. If a case is found with attachments or correspondence showing the taxpayer is a victim of "ID Theft" (IDT):

1. Enter Action Code 3 on the error register and reject the record.

2. Attach Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip with the notation "ID THEFT".

3. Give the entire case to the manager/lead.

(2) The manager/lead will expedite the case to the Planning and Analysis (P&A) staff for referral to one of the Submission Processing (SP) BMF ID Theft liaisons. The taxpayer must show that they are a victim of "ID Theft"; do not send cases that are subject to Criminal Investigation (CI), Examination (Exam), or Fraud review.

(1) Businesses use frivolous arguments to express dissatisfaction with the substance, form or administration of the tax laws by trying to avoid or reduce tax liabilities illegally. See IRM 25.25.10, Frivolous Return Program and Exhibit 3.12.249-4, Potential Frivolous Arguments for Examination Review, for a list of recognized frivolous arguments made by businesses.

(2) Review the return to decide whether it appears to be a frivolous return. Frivolous Criteria

(3) Do not consider the following returns as frivolous, unless there is other evidence of a frivolous argument:

• Returns that have only zeros, blanks, or no entries.

• Returns showing "None", "Not Liable", etc.

(1) The Internal Revenue Service (IRS) Restructuring and Reform Act of 1998 (RRA98), Section 3705(a) provides identification requirements for all IRS employees working tax-related matters.

(2) All IRS employees who communicate by telephone, face-to-face, or any other method of correspondence with taxpayers or their personal representatives, on tax-related matters must give (at minimum) the following information:

1. Telephone Contact - Their title (e.g., Mr., Mrs., Ms., Miss), last name, and badge identification (ID Card) number. Toll-free employees may also give their location for identification purposes. Treat faxes to taxpayers on tax-related matters as correspondence and include the required information.

2. Face-to-Face Contact - Their title (e.g., Mr., Mrs., Ms., Miss), give as appropriate during the conversation, their last name and badge identification (ID Card) number.

3. Correspondence (sent to the taxpayer and authorized representatives) - A telephone number that taxpayers can call for answers to questions. In addition, manually generated correspondence must have the employee's title (e.g., Mr., Mrs., Ms., Miss), last name, Integrated Data Retrieval System (IDRS) number, and letter system number, which are systemically generated by IDRS. Treat faxes to taxpayers on tax-related matters as correspondence and include the required information.

4. Correspondex letters - Specific employee name and telephone number if the employee initiating the correspondence is in the best position to respond to any questions the taxpayer may have or if the taxpayer is being asked to give more case-related information. If the taxpayer does not need to contact a specific employee, the correspondence needs only an IRS telephone number and standard signature.

(3) When a taxpayer requests to speak with a specific employee who previously worked their inquiry or request, or complains about the level of service previously given, make every attempt to resolve the taxpayer's inquiry. If unable to resolve the issue, refer the inquiry using established procedures to the manager.

(4) Secretaries, receptionists, or other people who answer the telephone in functional offices need to identify themselves. They should give their badge identification (ID Card) number only if they are answering telephones which are routinely used to give tax or account information.

(5) It is not necessary to repeat the badge identification (ID Card) number on a subsequent contact, when the nature of an employee's work involves multiple contacts with the same taxpayer and the employee has given the taxpayer (either telephone or in-person) their badge identification (ID Card) number on the first contact.

(1) Taxpayers may send tax return information via fax as part of return perfection even when submitting a signature. In circumstances where contact with the taxpayer was made and documented, faxed signatures are acceptable.

(2) Contact with the taxpayer may be by telephone or correspondence. Follow local procedures to decide which method of contact to use.

(3) Error Resolution System (ERS) tax examiners indicate the fax paragraph on the Form 3696, Correspondence Action Sheet, or other approved Correspondence Action Sheet to inform the taxpayer of the fax options.

(4) Use the following resources to ensure you are speaking with the taxpayer or authorized representative before disclosing any tax information:

• IRM 21.1.3.2.3, Required Taxpayer Authentication

• IRM 21.1.3.2.4, Additional Taxpayer Authentication

(5) Before leaving any messages on a taxpayer's answering machine, review the following:

• IRM 10.5.1.6.7.2, Answering Machine or Voicemail

• IRM 10.8.1, Information Technology (IT) Security, Policy and Guidance

(1) Correspondence Imaging Inventory (CII) is an inventory system for scanning all Accounts Management (AM) receipts into digital images and working the cases from those images.

(2) CII returns are shown with "CII Image - Do not correspond for Signature" stamped below the signature line or "CII" annotated on the front of the return.

(3) Follow the instructions below for processing CII returns. Correspondence Imaging Inventory (CII) Criteria

(1) Criminal Investigation (CI) investigates potential criminal violations of the Internal Revenue Code (IRC) and related financial crimes. Criminal violations of the IRC include willful attempts to evade or defeat the income tax. Criminal tax violations also include the willful failure to collect or pay over tax and false claims for refunds based on bogus return information.

(2) If CI has stamped the return, do not send for further CI action.

(3) For returns with refund claims ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ do the following:

(4) Because of the repetitive nature of the ERS/Rejects function, ERS/Rejects Tax Examining Technicians often recognize income tax return data that is outside of the norm for data found on similar returns for each income tax return type. If ERS finds return characteristics not meeting Audit Code or Exam referral criteria it considers suspicious, CI is available to review the referral.

(5) If a suspicious return is found, and there is no sign Code and Edit (C&E) made a copy and sent to CI Referral, then, do the following:

1. Make a copy of the first two pages of the return along with any page of the return that appears suspicious.

2. Attach Form 4227 Intra-SC Reject or Routing Slip or other proper routing slip to the copy

3. Route the copy as shown in the table below.

CI Referral Criteria Routing

Submission Processing Campus/Center	Route the Copy To:
Ogden	Mail Stop 9001, Criminal Investigation (CI)
Kansas City	Mail Stop S2 9000, Criminal Investigation (CI)

4. Edit an action trail "Copy to CI", or "CI Referral", or similar language in the lower left corner going vertically up the side of the return.

5. Continue processing the return.

(6) If the return fits other criteria (e.g., Frivolous Argument), take proper action.

(1) The primary goal in identifying tax returns for examination is to promote the highest degree of voluntary compliance. Examination gives support and helps Submission Processing (SP) with any questionable return found during processing. Exam has a many programs and tolerance criteria already found in several IRM sections. SP can refer any questionable return to Exam, unless prohibited by instructions currently found in several IRMs.

(1) The Customer Account Data Engine (CADE) 2 Program Office in Headquarters is charged with the primary goal to implement a single, modernized programming solution which gives daily processing of taxpayer accounts.

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

(3) The Business Master File (BMF) campus cycles are:

1. Campus Cycle: Thursday - Wednesday

2. Master File Processing: Friday - Thursday

3. Notice Review: Saturday: Monday (8+ days)

4. Unpostables: New available Tuesday; Closing Tuesday

(4) BMF transaction posting time frames are:

1. Transactions will be viewable using Corporate Files Online (CFOL) command codes on Saturday following the weekly Master Files processing run on Thursday.

2. Transactions will be viewable as posted transactions using Integrated Data Retrieval System (IDRS) command codes on Monday, following the weekly Master File processing run on Thursday.

Note: Implementation of CADE 2 accelerated weekly IDRS analysis. Previously, transactions such as this would have been pending on IDRS and not shown in the CFOL command code displays.

(5) Transaction posting dates show a format of YYYYCCDD. YYYY is the year. CC is the posting cycle. Individual Master File (IMF) transactions values for DD are:

• 01 = Friday

• 02 = Monday

• 03 = Tuesday

• 04 = Wednesday

• 05 = Thursday

(1) The tax examiners applying these instructions must be familiar with the editing procedures in IRM 3.11.249, Returns and Document Analysis - Processing Form 8752, and the general procedures in IRM 3.12.38, BMF General Instructions. The telephone may be used to resolve questions about returns on the error register instead of rejecting those returns for subsequent correspondence action.

(2) Tax examiners are not expected to review or redo the work of the Code and Edit tax examiner. However, if you notice an error or omission made by the tax examiner while working the error register, enter the correct information on the return and the error register. A complete review of the return is not required. If this section instructs something without how, refer to IRM 3.11.249, Returns and Document Analysis - Processing Form 8752.

(3) This manual is the main source of information. Find procedures in the following IRMs:

• IRM 3.24.249, ISRP System, Fiscal Year Required Payments/Form 8752

• IRM 3.10.72, Receiving, Extracting, and Sorting

(1) Only a ten percent (10%) underpayment penalty can be charged on Form 8752, Required Payment or Refund Under Section 7519, account.

(2) On the Form 3465, Adjustment Request, show the part of the remittance which is available for application to the penalty assessment if the return remittance includes an amount applicable to all or part of the penalty. Route the Form 3465 to Accounts Management (AM).

(3) On the error register, enter Computer Condition Code (CCC) "X" in Field 01-E (CCC) to freeze the module from refunding or offsetting.

(4) On the Form 8752:

• Enter Computer Condition Code (CCC) "X" to freeze the module from refunding or offsetting.

• Notate "3465 Prepared" (or similar language).

(5) For more information, refer to IRM 20.1.10, Penalty Handbook - Miscellaneous Penalties.

(1) Statute of Limitations processing does not apply to Form 8752, Required Payment or Refund Under Section 7519, because the form is considered a required deposit by the taxpayer and not a payment of tax due.

(1) Taxpayers may send a blank return stating they are not required to file or don't understand why they are receiving Form 8752, Required Payment or Refund Under Section 7519.

(2) Research to ensure the filer is still on a fiscal year basis. If a fiscal year filer, Form 8752 must be filed, unless:

1. The entity has a service approved tax year either by automatic consent or letter ruling from National Office (NO) and taxpayer can demonstrate that it continues to qualify.

(3) If a fiscal year filer and the criteria in 2(a) above does not apply, initiate correspondence. Inform the taxpayer that a partnership or S Corporation must file Form 8752 if it made an IRC 444 election to file their tax return on a fiscal year basis instead of the required year basis.

(4) If the taxpayer is no longer a fiscal year filer, do not process the Form 8752, Required Payment or Refund Under Section 7519. Void the blank return.

(1) It is important to leave a legible "Working Trail" (or "Action Trail") using blue ink for those who may work with the return later.

(2) Write all Taxpayer Notice Codes (TPNCs) 90 on the front of the return in the upper left corner (or use Form 12648, Error Correction 90 TPNC). See IRM 3.12.249.4.16, Field 01-N, Taxpayer Notice Code (TPNC), for more information.

(3) If corresponding with a non-suspense letter, "X" and write the corrected money amounts to the left of each original point(s) of error. Write money amounts in dollars only or dollars and cents, as applicable. Arrowing is allowed for money amounts when there are no intervening entries between the arrow and the line to which the money is to be entered.

(4) Leave a working trail on the return when changes are made to the following items:

• Employer Identification Number (EIN)

• Tax Period

• Received Date

• Computer Condition Code (CCC)

• Correspondence Received Date (CRD)

(5) When working Reject re-inputs, circle out any previous Action Codes shown on the front of the return, if no longer applicable.

(6) When working Rejects, write "Voided" with the date above the DLN in red, when voiding a return.

(1) The paper register (error register) is the physical representation of the tax return and any errors that have been identified. It is a printed form of the data input from the return, and appears in a standardized format used for nearly every type of Service Center Replacement System (SCRS) program. Data fields are designated with letters of the alphabet. Each section is designated with the section number.

(2) The first part of the error register is the title line. The error register title line identifies the run number, master file, register status, source of the register, type of register, program, form number, format code, date and page number.

(3) The error register title line uses a couple of terms "raw" and "loop". The first-time a document in error prints on a register it is called a "raw" register. When a raw register prints, make various corrections to the register, trying to correct as many errors as possible. The document is then sent back through Integrated Submission and Remittance Processing (ISRP) system to be transcribed. If the correction resolves the error, the information is transmitted to the Enterprise Computing Center-Martinsburg (ECC-MTB). If all the errors do not clear, the error register will print again showing the errors that remain. The re-printed register is called a "loop" register. The title line shows if the register is a raw register or a loop register and how any times the register has looped (correction loop counter).

(4) The Error Register has three sections (Section 01, Section 02, and Section 03 (Address Data)). The money fields (Field 01-A (Remittance), and all fields in Section 02, except Field 02-C (Deferred Ratio)), will be entered as dollars and cents.

(5) Errors appear much differently on paper registers than they do in Error Resolution System (error codes). Most errors can be found by an asterisk (*) appearing to the immediate left of the Field Designator. Some are special errors that require unique treatment. Errors can occur anywhere in every section except for the Header Section. Research IDRS using Command Codes (e.g., NAMEE, NAMEB, INOLES, ENMOD, ENREQ, etc.) can be used to correct some Entity errors.

(6) Form 8752, Required Payment or Refund Under Section 7519, is filed by partnerships (Form 1065, U.S. Partnership Return of Income) and S Corporations (Form 1120-S, U.S. Income Tax Return for an S Corporation) who made the IRC 444 election to file their income tax return on a year other than the required year. Partnerships and S Corporations use Form 8752 to figure and report the payment required under IRC 7519 or to obtain a refund of net prior year payment(s). A partnership or S Corporation must file Form 8752 if it made an IRC 444 election by filing Form 8716, Election To Have a Tax Year Other Than a Required Tax Year, and its election is still in effect for the tax year. Any tax year that an IRC 444 election is in effect, including the first tax year the IRC 444 is made, is an "applicable election year".

(7) Taxpayers electing an IRC 444 election must file Form 8752 even if the required payment is zero (0). Taxpayers must make a required payment for the applicable election year if more than $500 or the required payment for any prior tax year was more than $500.00. The required payment represents the value by the tax deferral of owners of those entities for a taxable year other than the required tax year. For an S Corporation, the tax year resulting from an IRC 444 election ends in September, October or November. A partnership's tax year may differ and depends on the tax year of the partners. The required payment is considered a deposit.

(8) Due Date: Form 8752 must be filed and required payment made on or before May 15 of the year following the calendar year in which the applicable election year begins. See IRM 3.12.249.4.9, Field 01-G, Penalty and Interest (P/I) Code, for more information.

(1) The following is a table of Tax Class, Document Code, and Master File Tax (MFT) for Form 8752, Required Payment or Refund Under Section 7519. Tax Codes

(1) Use Action Codes to correct errors on the paper register (error register). Every correction made on an error register or reject register must have an Action Code. The Action Code signifies to the computer what action should be taken. Using Action Codes are similar to correcting an error screen on the computer, though the process is not as instantaneous.

(2) Each Action Code has a different purpose. Only one Action Code may be entered at any time. If two Action Codes are used, the record will "loop" without corrections. If incorrect data is present in addition to non-correctable data, the incorrect data should be corrected first. The error register will then "loop", and further actions can be taken at that time. No other Action Code can be used with Action Codes 0, 1, 2, 3 or 7. If incorrect data is present, it must be corrected with Action Codes 4, 5 or 6, before Action Code 1 is used. Individual descriptions of the valid Action Codes for most error registers are provided below.

(3) Action Code 0 is used to show that the data in the record is correct and that the computer's computations should be disregarded. Verify the taxpayer's figures before using this Action Code. Only use this if the correct tax and data are printed in the error register. Action Code 0 will accept a record as transcribed and send the record to Enterprise Computing Center-Martinsburg (ECC-MTB). Action Code 0 is written to the left of Section 01.

(4) Action Code 1 is used with Taxpayer Notice Codes (TPNCs), to issue math error notices. When the data in the record is correct, but the taxpayer's computations are incorrect ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ a TPNC will be sent to inform the taxpayer of their error. This code may not be used if an amount field has a transcription error or if a field validity error is present in any field of a section. No other Action Code may be used in the same correction attempt. All validity errors must be corrected before Action Code 1 can be used; otherwise, the record will "loop". Action Code 1 and the correct TPNC are written to the left of Section 01, and a working trail is left in the upper left-hand corner of the return.

(5) Action Code 2 is used to delete a rejected record from processing. It can't be used on a raw register. Only Rejects will use Action Code 2. Action Code 2 is written to the left of Section 01.

(6) Action Code 3 is used to reject a record when it is unprocessable. Use of Action Code 3 will force the record to the reject register. It must never be used on a record already in reject status. When using Action Code 3, attach Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip, stating why the return is being rejected. Any of the following types of returns can be unprocessable.

1. A return or other document with illegible or missing necessary data.

2. A return or other document with required correspondence items with uncorrectable asterisks. All errors indicated by asterisks that can be corrected must be corrected before sending a return or document to Rejects for required correspondence.

3. A return or other document that can't be processed by the program under which it was blocked and must be processed with a Document Locator Number (DLN) for a different program.

4. An amended or substitute return where the original return is unavailable.

(7) Action Code 4 is used to delete a section from a record. This Action Code is used when information has been erroneously or unnecessarily entered into a section, and the entire section is not needed for processing. Each section is shown on the error register and will appear as the first two digits on the first line of print for each section. All sections can't be deleted; therefore, a record with only one section can't have an Action Code 4 correction. It can't be used on certain sections, such as Section 01, which are required for processing. Action Code 4 is written to the left of the section to be deleted.

(8) Action Code 5 is used to add a section to a record when the section was not transcribed. The Action Code is written in the space below the last printed section of the error register. Enter Action Code 5 on the error register to the left of the added section. The section number, alpha field designator(s), the data for the added field, and the applicable field breaker (use a comma (,) for a positive amount and a pound sign (#) for a negative amount) follow Action Code 5 in the order that they normally appear in the section. Enter only those fields with data present.

(9) Action Code 6 is used to change information in a field or fields of a section within the record. The computer identifies each field of a section with an Alpha Field Designator (AFD) and prints the AFD before the field on the error register. The Action Code is written to the left of the section where a field requires correction. To correct an invalid field:

1. Draw a line through the incorrect field data.

2. Write the correct information directly above the lined-out field. Use all capital letters and write as clearly and legibly as possible.

Note: Use special symbols to change the sign. A positive amount is written with a comma (,) and a negative amount is written with a pound sign (#).

(10) Action Code 7 is used to show that the data on the error register is correct and that no action is necessary. Action Code 7 may not be used with any other Action Code. All corrections requiring Action Codes 4, 5, and 6 must be done before Action Code 7 may be used. This Action Code may be used to clear a record that has been sent to the error register for one-time review. If information for a particular section was not input, the section may be generated for review with an asterisk before the section number. Use Action Code 7 to clear this item if no error exists.

(11) Action Code 9 is used to re-reject a reject "loop" register for correspondence or other suspense actions. Action Code 9 is written to the left of Section 01.

1. This code is used to prevent a reject "loop" record from reprinting each time the "loop" is run, if it is clear that the record is not ready for correction.

2. Action Code 9 is valid for reject "loop" only. It is invalid for raw rejects or error registers.

   Note: For Form 8752 processing, this action code and Action Code 3 are used similarly, except Action Code 9 is used with reject registers.

(12) Enter Action Codes 0, 1, 2, 3, and 7 on the error register to the left of Section 01.

(13) Enter Action Codes 4, 5, and 6 on the error register to the left of the correct section number.

(1) If an invalid correction is made to an error register, the error will return to be corrected again. When this happens, it is called a "loop" error register. Error Reason Code "AA" will print on the "loop" error register. The "AA" is simply for information.

(2) Correct the error register as if no prior attempt at correction has been made.

(1) ISRP Error is an error identified by the Integrated Submission and Remittance Processing (ISRP) edit run.

(2) The ISRP Error Indicator is printed to the left of the section number. This error will appear on the error register as shown in the following table: Integrated Submission and Remittance Processing (ISRP) Error

(3) All fields of a section must be examined when this condition exists. If Section 01 of a return is error coded, also examine the tax base data section for errors to ensure the return data is for the taxpayer whose name is in Section 01.

(4) Even though one or more sections of a record are error coded, the validity and consistency checks necessary for the record are made for all sections. Line out each incorrect field, and enter the correct data. Use Action Code 6. If the record is correct as it appears on the error register, enter Action Code 7 on the error register.

(1) A Terminus Error results when:

1. A non-numeric character appears in a numeric field, or

2. The format of the section is incorrect.

(2) When this error is present, two asterisks (**) will appear to the immediate left of the section number.

(3) Correct a Terminus Error as follows:

1. Compare the return with the error register.

2. Assure that any fields already having data are correct. Correct or reject as applicable.

3. Enter data in any blank fields that should have data.

(4) If data is correct on the error register, re-enter a field, using Action Code 6 to send the record to good tape.

(1) Field Validity Errors are the most common type of errors.

(2) A Field Validity Error appears with an asterisk (*) to the immediate left of the field that is in error. All fields will be printed on the error register. Some fields must have data. If they are blank, they are invalid. The field will be in error if:

1. An invalid character is present in a field;

2. The field is otherwise incomplete or invalid; or

3. A math error is present.

(3) Correct a Field Validity Error as follows:

1. Compare the return with the error register;

2. Line out the incorrect field, and enter the correct data immediately above the lined-out data; and

3. Enter Action Code 6 on the error register.

4. In some cases, a Taxpayer Notice Code (TPNC) must be sent, or another action must be taken.

(4) There are some fields that are asterisked (on the raw only) for a cursory review. These may be cleared with Action Code 7 if there are no other errors present.

(1) Field 01-A (Remittance) can't be changed in Error Resolution. If the amount is incorrect, treat the return and related error register as unprocessable. Reject with Action Code 3, and prepare Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip, to explain the error or follow local procedures. Rejects will prepare Form 3893, Re-Entry Document Control, after corrective action has been taken.

(2) If a remittance amount is present, the received date must be present. See IRM 3.12.249.4.8, Field 01-F, Received Date.

(1) Rejects will determine the proper application of an excess remittance through research, correspondence, or other existing procedures.

(2) When the Reject tax examiner determines that the excess remittance should be applied to a different tax class or module, enter Computer Condition Code (CCC) "X" on the return and the error register. This code will freeze the tax module from refunding or offsetting by generating a Transaction Code (TC) 570.

(3) The tax examiner will prepare Form 3465, Adjustment Request, to show the amount and module in which the credit should be applied.

(4) See IRM 3.12.38, BMF General Instructions, for more information.

(1) Field 01-B (Name Control) must have one to four characters. If the name control has fewer than four characters, every position must be accounted for by entering the number of blanks and encircling it. When all spaces in this fixed field are not accounted for, the record will loop. To avoid unnecessary loops, enter the name control data (when less than four characters) and account for the blanks by entering the number of blanks and circling the number. See Figure 3.12.249-1, Fixed Length Correction.

(2) The name control and check digit each have their tests for validity.

(3) A check digit will always be the first correction choice. It is invalid if:

1. The 1st and 2nd positions are not blank.

2. The 3rd and 4th positions are not letters.

3. The letters E, G, or M are present.

(4) The check digit is derived by a mathematical computation performed by the computer on the Employer Identification Number (EIN). It is present on mail labels provided by the IRS and is only used when that mail label is present. To correct this, refer to the check digit on the label.

1. Correct any transcription errors by lining through the entry in Field 01-B (Name Control) and editing an encircled "2", followed by the two-letter check digit from the mail label.

2. If the check digit is correct but is asterisked, check for transcription errors in the EIN. Correct the EIN in Field 01-C (EIN). The computer will recompute and validate the check digit.

(5) A name control will be entered if the check digit is unavailable. It is invalid if:

1. The 1st position is other than a letter or number.

2. The 2nd, 3rd and 4th positions have characters other than letters, numbers, ampersands (&), hyphens (-), or blanks.

3. Any character follows a blank.

(6) To correct this, line through the entry in Field 01-B (Name Control) and enter the correct name control above it. If the name control has fewer than four characters, every position must be accounted for by entering the number of blanks and encircling it. See Figure 3.12.249-1, Fixed Length Correction.

(7) To determine the correct name control, follow the guidelines in Document 7071-A, Name Control Job Aid - For Use Outside of the Entity Area.

(8) If the transcribed name control does not match the name control for the transcribed EIN on the Entity Index File (EIF), there will be an underprint to Field 01-B (Name Control).

(9) The name control underprint will be removed when the following occurs:

1. The name control underprint and the entry in Field 01-B (Name Control) agree.

2. Field 01-M (Entity Underprint Code) has a "1".

(10) When the name control on the return does not match the name control on the EIF, one of the following has occurred:

1. The EIN was entered wrong, either by the taxpayer or the IRS.

2. The name control was edited or transcribed incorrectly.

3. The name control on the EIF is incorrect.

4. The taxpayer altered the order of the name on the return in such a way that the name control no longer agrees with the way it appears on the Business Master File (BMF).

5. The taxpayer's name changed.

6. The taxpayer's identity has changed (e.g., the taxpayer has changed from a partnership to a corporation).

(11) To correct this, compare the entries in Field 01-B (Name Control) and Field 01-C (EIN) to the name control and EIN on the return.

(12) If the EIN on the return and the EIN in Field 01-C (EIN) do not agree, correct Field 01-C (EIN) to agree with the return.

1. If the correct name control is in Field 01-B (Name Control), enter a "1" in Field 01-M (Entity Underprint Code).

2. If the name control in Field 01-B (Name Control) is incorrect according to the information on the return, change Field 01-B (Name Control).

3. If the correction does not agree with the name control underprint, enter a "1" in Field 01-M (Entity Underprint Code).

4. If the return is an ISRP Remittance Processing return, reject with Action Code 3 and attach Form 4227, Intra-SC Reject and Routing Slip, or other proper routing slip to Rejects notating, "Move ISRP Remittance Processing Money".
   - Rejects will research Integrated Data Retrieval System (IDRS) using command codes (e.g., Command Code (CC) BMFOL) to determine if the payment has posted incorrectly. See IRM 3.12.38.5.6, BMF General Instructions, Credit Transfers, for more information.
   - If the money is posted incorrectly, prepare a Form 3465, Adjustment Request, or follow local procedures to transfer the money to the correct module.
   - On the error register, enter Computer Condition Code (CCC) "X" in Field 01-E (CCC).
   - On the Form 8752, enter Computer Condition Code (CCC) "X" and notate "3465 Prepared" (or similar language).

(13) If the EIN on the return agrees with the EIN in Field 01-C (EIN), determine why the name control underprint is present. If the name control edited on the return agrees with the name control in Field 01-B (Name Control) then:

1. Compare the name control underprint with Field 01-B (Name Control) and the name on the return. If it is obvious that the underprint is the correct name control and it was edited wrong on the return, change Field 01-B (Name Control) to agree with the underprint.

2. If it is not an obvious error, request research per local procedures. See IRM 2.3, Terminal Response, and IRM 2.4, Terminal Input, for more information on IDRS Command Codes.

(14) Determine the correct EIN and name control from the research.

1. If another EIN is found for the entity on the return, change Field 01-C (EIN) to the correct EIN and write the correct EIN on the return. Follow the procedures in (10) above.

2. If the EIN on the return is correct and the taxpayer just rearranged the name, change Field 01-B (Name Control) to agree with the name control on the Entity Index File (EIF).

3. If the EIN is changed from the one the taxpayer used, issue Letter 3875C, Missing or Incorrect EIN on Return - BMF/EPMF, or Letter 3463C, Missing Information Request to Process Business Returns, as a non-suspense letter to the address on the return.

   Exception: Letter 3463C updated to include the paragraphs from the Letter 3875C. Letter 3463C may be used when there is more than one correspondence issue (e.g., Incorrect EIN and missing signature).

   Note: Do not send Letter 3875C when:
   1. Three or less digits of the EIN are transposed, different or missing, or
   2. The EIN is consecutive numbers (e.g., 12-3456789) or repeating numbers (e.g., 11-1111111), or
   3. Command Code (CC) INOLES shows the account has been "merged to" or "merged from" or
   4. The TIN on the return is the taxpayer's SSN (check CC INOLEG).

(15) If the EIN on the return is correct but the name control on the Entity Index File (EIF) is not conforming to the acceptable rules for name controlling:

1. Correct Field 01-B (Name Control) to agree with the name control on the BMF.

2. Copy Page 1 of the return and notate "Copy - Do Not Process". Attach any research and route the case to Entity Control following local procedures (e.g., Attach Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip). Entity Control will fix the name control, which should stop future unpostables and underprints.

3. If the EIN on the return agrees with the EIN in Field 01-C (EIN), but the name control does not agree with the name on the EIF, attach any research and route the case to Entity Control following local procedures (e.g., Attach Form 4227 or other proper routing slip).

(16) For more information on Command Codes, see Integrated Data Retrieval System (IDRS) Command Code Job Aid at: http://serp.enterprise.irs.gov/job-aids/command-code/command-code.html.

(1) This field has nine positions.

(2) It is invalid if any of the following conditions are present:

1. It is not nine numeric characters.

2. It is all nines or all zeros.

3. If the first two digits are: 00, 07, 08, 09, 17, 18, 19, 28, 29, 49, 78, 79 or 89.

(3) If the EIN is invalid, take the following action:

1. Compare with the EIN on the return, and correct the error register with Action Code 6, if the number has been incorrectly transcribed.

2. Search the return and any attachments for a valid EIN if transcribed correctly. If one is found, edit the EIN on the return, and correct the error register with Action Code 6. If no valid EIN is found, research IDRS using command codes (CCs) (e.g., CC EINAD, CC NAMEE, CC INOLE, CC ENMOD, etc.) or follow local procedures.

3. If it is transcribed correctly, and a valid EIN is not found during the search prescribed above, reject the record to Entity Control following local procedures (e.g., Attach Form 4227 or other proper routing slip and notate the reason for sending it to Entity Control).

(4) Reject Correction:

1. If Entity Control has found the correct EIN, enter it in Field 01-C (EIN) and edit the EIN on the return.

2. If Entity Control has assigned an EIN, enter it in Field 01-C (EIN).

(1) This field has the ending month and year of the tax period covering the return. The tax period ending is printed, in year-month (YYYYMM) format (e.g., December 31, 2023, is printed 202312).

(2) The field is invalid if:

1. It is not numeric.

2. The tax year ending is later than the current date.

3. The year is before 199012.

4. The month is not 12.

5. It is in a format other than YYYYMM.

(3) Determine the tax period by the year (printed) on the face of the tax form (e.g., for the 2023 tax form, the tax period should be "202312"). For example, if an election year ends September 30, 2023, the tax period is 202312, not 202309. Taxpayers are advised to edit changes on the form to the tax year for prior tax periods.

(4) The tax period may be a calendar year (e.g., 20XX12). Editing is required only if the "applicable election year ending" is other than blank. Circle the taxpayer's entry and enter the correct tax period.

1. If the tax period has been changed to an earlier year and the ending period is not December 31, circle the date and edit the tax period, using the procedures described above.

2. If multiple returns from the same entity are in a batch and can't determine the correct tax period, edit all to the current tax period (20XX12). Accounts Management will work the "dup" returns and correct the tax periods.

3. Editing of the tax period is not required if the current year form is used (e.g., 2023 form).

   Exception: The taxpayer indicates on the form that the tax period is for a prior year.

4. If any version of Form 8752 other than the current year form is received, edit the current year in the "20XX12" format under the title of the form (unless the taxpayer indicated the tax period is for a prior year).

5. If the tax period is in error due to a Statute issue, correct with Action Code 0 (zero).

(5) Tax Cuts and Jobs Act of 2017, Public Law 115-97, Section 11001 changed the Section 1 tax rates. Form 8752, Required Payments or Refund Under Section 7519, Line 9a rate changed from 40.6% to 38% for tax years beginning after December 31, 2017. Refer to the Tax Years and Rates table below.

(6) If a Form 8752 is received for a future tax period (e.g., if the tax period ending is after the current processing date), enter Action Code 3 on the error register and prepare a Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip to request Rejects to research for postings.

(1) Computer Condition Codes (CCCs) are used to identify a special condition or computation to post to the Master File and are entered in the upper left margin of Form 8752, Required Payment or Refund Under Section 7519. CCCs "F", "G", "O", "U" (on ISRP (Submission Processing) input only), and "X" are valid for Form 8752 processing.

(2) The field is invalid if CCCs other than those above are used. See IRM 3.12.249.4.6.1 through IRM 3.12.249.4.6.6 for descriptions of the CCCs.

(3) See IRM 3.12.249.4.7, Field 01-E (CCC) Correction Procedures, for more information.

(1) To correct Field 01-E (CCC), compare the CCC with the code entered on Form 8752, Required Payment or Refund Under Section 7519. If it is a transcription error, correct it by lining out the code in Field 01-E (CCC) and writing the correct code above it.

(2) If Form 8752 is coded incorrectly, determine the correct code by referring to the Computer Condition Codes information. Correct the return by lining out the code in Field 01-E (CCC), writing the correct code above it, and entering Action Code 6 on the error register.

(3) The field is invalid if Field 01-E (CCC) has a "G" and:

1. There are entries past Field 01-F (Received Date), or

2. If Field 01-F (Received Date) is blank, or

3. If Field 01-E (CCC) has entries other than "G" or "U" (on raw input only).

(4) To correct this, determine if the return is an amended return.

(5) If the return is amended:

1. Delete all fields in Section 01 past Field 01-F (Received Date).

2. Delete all CCCs except "G" in Field 01-E (CCC).

3. If Field 01-F (Received Date) is blank, enter the correct received date. See IRM 3.12.249.4.8, Field 01-F, Received Date.

4. Enter Action Code 6 on the error register to the left of Section 01.

5. Delete Section 02 (except Field 02-C (Deferral Ratio)) using Action Code 6.

(6) If the return is not amended:

1. Line through the "G" code in Field 01-E (CCC) and enter Action Code 6 on the error register to the left of Section 01.

2. Verify the remaining fields for correct data, enter any missing data and correct any erroneous data.

(7) To correct this, refer to the tax period, computer condition codes, and received date on the return.

1. Correct all coding errors and transcription errors in Field 01-E (CCC).

2. Verify the return is delinquent. If the return is delinquent, enter the received date (in YYYYMMDD format) in Field 01-F (Received Date). For example, enter June 10, 2024, as "20240610".

(8) The field is invalid if CCC "U" is present on correction processing. The "U" code is used by Code and Edit when a return must be rejected. If it is necessary to reject a return in Error Correction, use Action Code 3.

(1) Field 01-F (Received Date) is invalid if any one of the following conditions are present:

1. The month (fifth and sixth digits) is other than 01 through 12; or

2. The day (seventh and eighth digits) is other than 01 through 31 for the months 01, 03, 05, 07, 08, 10 or 12; 01-30 for the months 04, 06, 09 or 11; 01-28 for the month 02; or 01-29 for month 02 during leap year.

3. The received date is later than the processing date.

4. An alpha, special character, or blank is present in the field.

5. The received date is blank with a CCC "G", "D" or "R".

6. It is blank and the processing date is greater than the year-month of the tax period by more than six months. This condition is valid on the correction run.

7. It is blank and remittance is significant.

8. It is blank and the Penalty and Interest Code is not blank.

9. The received date is in a format other than YYYYMMDD.

10. The received date is earlier than the tax period.

(2) Correct all misplaced entries, coding errors, and transcription errors.

(3) If Field 01-F (Received Date) is invalid, refer to the return to determine the correct received date. Use Action Code 6, line out the received date on the error register and enter the correct date above the lined-out date.

(4) Determine the received date using the following priority when one is needed but is not stamped on the return or a valid handwritten received date is not present:

1. The earliest legible postmark date (U.S. Postal Service, foreign or Private Delivery Service) on the envelope. Rules for using the U.S. Postal Service (USPS) postmark or foreign postmark date are as follows:

Received Date Criteria

If	Then
An envelope is not attached,	Use the postmark date stamped on the face of the return. Note: When there are multiple returns in one envelope, the envelope is attached to one return and the postmark date is stamped on the other returns.
The postmark is missing and the envelope is certified,	Look for an "USPS.com Track & Confirm" record that has been attached to the return (should be before the envelope). Use the Acceptance date on the record to determine timeliness and follow normal procedures. See Exhibit 3.12.249-8, USPS.com Track & Confirm. If the "USPS.com Track & Confirm" record is not attached, no action is required.
An envelope has both a USPS and private-metered postmark,	Use the USPS postmark.
An envelope has a foreign and private-metered postmark,	Use the foreign postmark.
An envelope has two private-metered postmarks,	Use the latest private postmark.
An envelope has only one private-metered postmark,	Use the private-metered postmark.

Note: A private-metered postmark is to be considered timely if received ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2. Service Center Automated Mail Processing System (SCAMPS) Digital Date

3. Revenue officer's or other IRS official's signature date

4. Signature Date, if within the current year (unless other information shows the signature date is invalid)

5. Julian Date of the Document Locator Number (DLN) minus 10 days

6. Current date minus 10 days

(5) If a return has been faxed to another area of the IRS and then sent to Submission for processing, do not enter the Enterprise Electronic Fax (EEFax) Date as an IRS Received Date. Enter a received date according to normal procedures.

(1) Invalid Condition - Field 01-G (Penalty and Interest (P/I) Code) is invalid if any one of the following conditions are present:

1. It is other than blank or "1",

2. It is a "1" and the received date is not present, or

3. It is a "1" and the received date ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(2) Correction Procedures - Refer to the received date and tax period on the return to determine if the received date ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

1. Blank the field if the taxpayer has not computed penalty, interest or the received date ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Form 8752 must be filed and the required payment made to the Service Center on or before May 15th (of the year following the applicable election year). Therefore, Form 8752 for applicable election years beginning in 2023 are due May 15, 2024. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2. Enter a "1" if the taxpayer has computed penalty and interest and the received date ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Enter the received date in Field 01-F (Received Date) if it is not present.

(1) ISRP transcribes a "1" (Partnership) or "2" (S Corporation) based on the box checked by the taxpayer. If one of the boxes is checked, and Field 01-H (Partnership/S Corporation Indicator) is blank, enter the correct code on the error register. If both boxes or neither box is checked, blank the field.

1. "1" = Partnership box is checked.

2. "2" =S Corporation box is checked.

(1) Field 01-I (Centralized Authorization File (CAF) Indicator) is invalid if it is not one of the following numbers: 1, 2, 3, 4, 7 or blank.

(2) If Code and Edit entered an invalid number, enter one of the following codes in the lower right corner of Form 8752, Required Payment or Refund Under Section 7519, and correct with Action Code 6: CAF Code

(3) If the POA does not authorize refunds or notices, a code is not necessary on the return.

(1) Form 8752, Box B (First Tax Year Box) is checked for the first applicable year the election under IRC 444 is in effect. No payment is due the first year. When this box is checked, there should not be any amounts in Lines 1 through 10 and a blank or zero on Line 11. Any error indicator will appear when Field 01-J (First Tax Year Box) equals "1" and there is an amount on any other line.

(2) If Field 01-J (First Tax Year Box) was erroneously coded "1", cross out the "1" and correct it with Action Code 6.

(3) If any data was erroneously keystroked into Section 02 fields, delete Section 02 with Action Code 4.

(4) If Box B (First Tax Year Box) is checked, and there are amounts in Lines 1 through 11:

1. Research IDRS (e.g., CC BMFOL or other command code) for a previously filed return.

2. If research shows a previously filed return, cross out the 1 in Field 01-J (First Tax Year Box) and correct with Action Code 6.

3. If research shows this is the first applicable election year, correspond with the taxpayer to determine if this return represents the first applicable year or not. Applicable letters include the following:
   - Letter 118C, Corporate Return Incomplete for Processing: Forms 1120, 1120 A/S
   - Letter 3463C, Missing Information Request to Process Business Returns

4. Send Letter 3463C, paragraph L or Letter 118-C (or other proper letter) with the following suggested language: "You checked Box B on your Form 8752, indicating this is the entity's first tax year. If that is the case, Lines 1 through 10 should be blank and Line 11 should a zero. Please inform us as to whether Box B was checked in error, or Lines 1 through 12 were completed in error and we will adjust your return accordingly."

   Note: Letter 3463C is updated to include the open paragraph language shown above as a selectable paragraph.

(5) Responses/No Responses to correspondence for Form 8752, Box B (First Tax Year Box):

1. If the taxpayer's response shows this is the first applicable year, delete Section 02 with Action Code 4.

2. If the taxpayer's response shows this is not the first applicable year, cross out the "1" in Field 01-J (First Tax Year Box) and correct it with Action Code 6.

3. If the taxpayer does not respond to correspondence, cross out the "1" in Field 01-J (First Tax Year Box) and correct it with Action Code 6.

(1) This box (Box C) is used the year the IRC 444 election is terminated. If checked, CCC "F" must be present.

(2) If Field 01-K (Terminating Event Box) was erroneously coded "1", cross out the "1" and correct it with Action Code 6.

(3) If Field 01-K (Terminating Event Box) was correctly coded, enter Computer Condition Code "F" in Field 01-E (CCC) and correct it with Action Code 6.

(1) Field 01-L (Short Base Year Box) currently is not used for validity or consistency checks.

(1) In all cases where there is an underprint of the name control, the record will not go to good tape until the applicable code is in Field 01-M (Entity Underprint Code), or the name control has been corrected to match the underprint.

(2) The underprint in Field 01-B (Name Control), will not clear until either an Entity Underprint Code is entered in Field 01-M or until the name control matches the underprint.

(3) Enter Entity Underprint Code "1" if the name control is underprinting and the transcribed name control is correct.

(4) If there is no name control underprint, leave the field blank.

(1) Taxpayer Notice Codes (TPNCs) can be input only as correction data, using Action Code 1. Put the correct tax to the left of the taxpayer's figures and TPNC in the upper left margin of the return (near the Name area).

(2) All invalid conditions must be corrected before Action Code 1 is used.

(3) The codes will appear in this field on the "loop" (correction run) when another error exists. When this occurs, correct any other invalid condition, but not this field. The use of another Action Code will cause this field to be blanked on the next "loop". Correct by using Action Code 1 and the proper TPNC.

(4) The valid TPNCs are as follows: Taxpayer Notice Code (TPNC)

(1) This field is transcribed from Line 1. Correct all misplaced entries, coding errors, and transcription errors in Field 02-A (Net Income Amount) and correct with Action Code 6.

(1) This field is transcribed from Line 2. Correct all misplaced entries, coding errors, and transcription errors in Field 02-B (Applicable Payment Base Year Amount) and correct with Action Code 6.

(1) This field is transcribed from Line 3. The "Deferral Ratio" is the three-digit code representing the allowable deferral percentage for the taxpayer's elected deferral period. The term "Deferral Period" means the number of months between the last day of the elected tax year and the last day of the required tax year.

(2) The "Deferral Ratio" is the three-digit code representing the allowable deferral percentage for the taxpayer's elected deferral period. The term "Deferral Period" means the number of months that occur between the last day of the elected tax year and the last day of the required tax year. There are eleven codes. These codes represent deferrals of one to eleven months and are shown in the table below.

(3) Correct all misplaced entries, coding errors, and transcription errors in Field 02-C (Deferral Ratio).

(4) Code and Edit is responsible for editing the correct number. If they did not edit the number or edited it incorrectly, follow these instructions:

1. Enter the three-digit code for the percentage in Field 02-C (Deferral Ratio). Refer to the Deferral Ratio table above. If missing or incorrect, edit the same three-digit code on the dotted part of Line 3 (to the left of the taxpayer's entry).

2. Generally, the deferral percentage will not exceed 25% (percent). However, entities existing before 1986 could make the IRC 444 elections and keep that taxable year even if the deferral period was more than three months. If the taxpayer claims an amount greater than 25%, but less than 91.7%, accept the taxpayer's amount. If the taxpayer claims more than 91.7%, allow only 91.7%.

   Note: Before lowering the rate, multiply Line 1 by the amount shown on Line 3 to ensure the taxpayer used that rate. For instance, if a taxpayer put $1,000 on Line 1 and 83 percent on Line 3, but $1,000 on Line 1 and 83 percent on Line 3, came up with an amount of $83.00, taxpayer did not multiply by 83% (percent), but rather, 8.3%. In this case, enter 083. Caution: Deferral Ratio - must have an entry as shown above. This field can't be zero, even if Lines 1 or 2 have a "0" (zero) amount.

3. The taxpayer may either round the percentage (e.g., put down 8% or 17% or 67% rather than 8.3% or 16.7%), or carry the percentage to multiple places (8.33% or 16.67% or 66.67%). In either case, enter "083" or "167" or "667".

(5) If the taxpayer enters a percentage that does not approximate the allowable percentages, enter the acceptable code that is:

1. Lower than the percentage claimed, and

2. Closest to the percentage claimed.

(6) If the taxpayer puts down an amount that is less than six percent (6%):

1. Correspond with the taxpayer using Letter 3463C, Missing Information Request to Process Business Returns, (or other proper letter) to ask what the deferral period is.

2. Enter the proper code based on the taxpayer's response.

3. If there is no response, reject with Action Code 3 and route to Entity Control following local procedures (e.g., using Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip).

(7) If the taxpayer shows a deferral ratio in the form of a decimal rather than a percentage, convert it to a percentage.

1. Example 1: If the taxpayer enters .17 as the deferral ratio, enter "167".

2. Example 2: If the taxpayer enters .08 as the deferral ratio, enter "083".

(1) This field is transcribed from Line 4. It is computed by multiplying the deferral rate (Line 3, Field 02-C) by the amount shown for the net income amount (Line 1, Field 02-A).

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-A (Net Income Amount), Field 02-C (Deferral Ratio), and Field 02-D (Line 1 - Deferred Amount) and correct with Action Code 6.

(3) If the error in Field 02-D (Line 1 - Deferred Amount) causes an underprint in that field, send TPNC 01 using Action Code 1. If this field underprints to rounding of the percent, correct it with Action Code 7.

(1) This field is transcribed from Line 5. It is computed by multiplying the deferral rate (Line 3, Field 02-C) by the amount shown for the applicable payment made during the base year (Line 2, Field 02-B).

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-B (Applicable Payment Base Year Amount), Field 02-C (Deferral Ratio), and Field 02-E (Line 2 - Deferred Amount) and correct with Action Code 6.

(3) If the error in Field 02-E (Line 2 - Deferred Amount) causes an underprint due to rounding of the percent, then correct with Action Code 7.

(4) If the error in Field 02-E (Line 2 - Deferred Amount) causes an underprint and there is no rounding of the percent, then send TPNC 02 (or other correct TPNC) using Action Code 1.

(1) This field is transcribed from Line 6.

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-F (Applicable Payment Deferral Amount) and correct with Action Code 6.

(1) This field is transcribed from Line 7.

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-G (12 Month or Short Year Amount). If a negative amount is shown, enter $0. Correct with Action Code 6.

(1) This field is transcribed from Line 8.

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-H (Net Base Year Income Amount) and correct with Action Code 6.

(1) This field is transcribed from Line 9a. It is computed by multiplying Line 8, Field 02-H (Net Base Year Income Amount) by the rate applicable for that period.

(2) The tax years and rates are as follows: Tax Years and Rates

(3) Correct all misplaced entries, coding errors, and transcription errors in Field 02-H (Net Base Year Income Amount) and Field 02-I (Net Base Year Percentage Amount) and correct with Action Code 6.

(4) If Field 02-I (Net Base Year Percentage Amount) is blank and there is an underprint, edit Line 9a with the amount of the underprint. Bring up the underprint from Field 02-I (Net Base Year Percentage Amount) and correct with Action Code 6.

(5) If Field 02-I (Net Base Year Percentage Amount) is not blank and there is an underprint, send TPNC 03 using Action Code 1.

(6) If the taxpayer filed a return for the current year on a prior year revision of Form 8752, but did not enter the correct "Net Base Year Percentage Amount" (Line 9a), Field 02-I (Net Base Year Percentage Amount) will underprint.

(1) This field is transcribed from Line 9b. Depending on the prior payment history of the organization, it should be either the amount shown on Line 9a or $0.

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-J (Required Payment Amount) and correct with Action Code 6.

(3) See Field 02-J (Required Payment Amount) procedures below: Field 02-J Procedures

(4) Form 8752, Required Payment or Refund Under Section 7519, is used to remit the required payment. The required payment is intended to represent the value of the tax deferral by the owners of those entities using a taxable year other than the required year. Generally, the tax year must be a Fiscal Year (FY) ending in September, October or November. The required payment is considered a deposit.

(1) This field is transcribed from Line 10.

(2) Correct all misplaced entries, coding errors, and transcription errors in Field 02-K (Net Required Payment Balance) and correct with Action Code 6.

(1) This field is transcribed from Line 11 (Required Payment Due) or Line 12 (Refund of Net Prior year payments). The computer will underprint with a positive amount for a balance due (Line 11) and a negative amount for an overpayment (Line 12). Field 02-L (Payment Due or Refund Amount) will asterisk if the taxpayer's figure differs from the computer figure ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(2) Line 11 (Required Payment Due) is computed by subtracting Line 10 (Field 02-K) from Line 9b (Field 02-J). Line 12 (Refund of Net Prior year payments) is computed by subtracting Line 9b (Field 02-J) from Line 10 (Field 02-K).

(3) Correct all misplaced entries, coding errors, and transcription errors in Field 02-L (Payment Due or Refund Amount) and correct with Action Code 6.

(4) See Field 02-L (Payment Due or Refund Amount) procedures below: Field 02-L Correction Procedures

(5) If the taxpayer requests a "credit elect" or in some way asks that the refund be posted to the next tax period:

1. Prepare Form 3465, requesting Accounts Management (AM) to transfer the referenced credits to the correct module and to release the "X" freeze.

2. Notate on the return "Form 3465 to AM" and make a copy of Page 1 of the return (mark as "Copy - Do Not Process").

3. On the error register, enter CCC "X" in Field 01-E (CCC) using Action Code 6 (to freeze the module from refunding or offsetting) and to correct Field 02-L (Payment Due or Refund Amount) by bringing up the underprint.

4. Route Form 3465 with a copy of the return to Accounts Management.

(6) Any penalty or interest included by the taxpayer in Field 02-L (Payment Due or Refund Amount) should be subtracted from the amount on Lines 11 or 12 and the difference entered in Field 02-L. Also, "X" Lines 11 or 12 and edit the difference to the left of the "X". If the taxpayer has made a math error, send TPNC 05 using Action Code 1.

(7) Field 02-L (Payment Due or Refund Amount) will asterisk if either of the following conditions are present: Correction Procedures

(8) Correct all misplaced entries, coding errors, and transcription errors. If TC 840 has posted or is pending (PN 840) on IDRS to Command Code (CC) BMFOL or CC TXMOD and is the same overpayment on the return or Form 3753, Manual Refund Posting Voucher, or Form 5792, Request for IDRS Generated Refund, is attached, then enter Action Code 6 or Action Code 7, as applicable, on the error register.

(9) A manual refund on a Form 8752 will only be done if the refund is for ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If a refund is ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡:

1. Correct all misplaced entries, coding errors, and transcription errors.

   Note: The 45-Day Jeopardy rules do not apply to Form 8752.

2. Form 3753 is not attached, correct with Action Code 3 and route to Rejects with Form 4227, Intra-SC Reject or Routing Slip, or other proper routing slip. Notate "Manual Refund" on Form 4227, Intra-SC Reject or Routing Slip.

   Note: If the required date, per IRC 7519(c)(3)(A), on which a refund becomes payable has not arrived, hold the return until such date. When the refund becomes payable, follow procedures in IRM 3.12.38.5.4, BMF General Instructions - Manual Refunds, for issuing manual refunds.

3. Form 8302, Application for Electronic Funds Transfer (EFT) of $1 Million or More, is attached, correct with Action Code 3 and route to Rejects with Form 4227 or other proper routing slip. Notate "Manual Refund" on Form 4227. Do not detach Form 8302.

   Note: If the required date, per IRC 7519(c)(3)(A), on which a refund becomes payable has not arrived, hold the return until such date. When the refund becomes payable, follow procedures in IRM 3.12.38.5.4, BMF General Instructions - Manual Refunds, for issuing manual refunds.

(10) In the case of overpayment, the refund shall be payable the later of April 15 of the calendar year following the calendar year in which the election year begins or 90 days after the day the claim for refund is filed. In the case of a termination, the refund shall be payable the later of April 15 of the calendar year following the calendar year in which the election year ends, or 90 days after the day the claim for refund is filed. Credit interest will not generate on any Form 8752 refund of any amount at any time. Per Treasury Regulation 1.7519-2T(a)(6)(iii), interest is not allowed with respect to any refund of a required payment claimed on Form 8752. Credit interest can't be input under any circumstance, including where IRS actions have delayed the refund issuance.

(1) Section 6695(b) imposes a penalty on paid tax preparers who fail to sign the returns they prepare. For Compliance to determine whether a penalty should be assessed, Submission Processing must capture certain paid preparer information during the initial processing of the return.

(2) The Preparer Tax Identification Number (PTIN) is to the right of the Preparer's Signature in the PTIN box at the bottom right corner of Form 8752. Data may or may not be present in Field 02-M (PTIN).

(3) Valid Condition - Field 02-M (PTIN) can be blank or numeric. If numeric, it can't be all zeros and it can't be all nines.

(4) Invalid Condition - Field 02-M (PTIN) is invalid if any of the following conditions are present:

1. All zeros, or

2. All nines, or

3. Less than nine positions

(5) Correction Procedures:

1. Correct all misplaced entries, coding errors, and transcription errors.

2. If unable to determine a valid entry, delete Field 02-M (PTIN).

(1) Section 6695(b) imposes a penalty on paid tax preparers who fail to sign the returns they prepare. For Compliance to determine whether a penalty should be assessed, Submission Processing must capture certain paid preparer information during the initial processing of the return.

(2) The Firm's EIN is below the Preparer's PTIN box at the bottom right corner of Form 8752, Required Payment or Refund Under Section 7519.

(3) Valid Condition - Field 02-N (EIN) can be blank or numeric. It can't be all zeros or all nines.

(4) Invalid Condition - Field 02-N (EIN) is invalid if any of the following conditions are present:

1. All zeros, or

2. All nines, or

3. Less than nine characters.

(5) Correction Procedures:

1. Correct all misplaced entries, coding errors, and transcription errors.

2. If unable to determine a valid entry, delete Field 02-N (EIN).

(1) Section 6695(b) imposes a penalty on paid tax preparers who fail to sign the returns they prepare. For Compliance to determine whether a penalty should be assessed, Submission Processing must capture certain paid preparer information during the initial processing of the return.

(2) The Preparer Phone Number is below the Firm's EIN at the bottom right corner of Form 8752.

(3) Valid Condition - Field 02-O (Preparer Phone Number) must be alpha or numeric or a combination of alpha, numeric or blank characters, not to exceed 10 characters.

(4) Invalid Condition - Field 02-O (Preparer Phone Number) is invalid if other than 10 alpha, numeric or blank.

(5) Correction Procedures:

1. Correct all misplaced entries, coding errors, and transcription errors.

2. If a telephone number is invalid, delete Field 02-O (Preparer Phone Number) and continue processing.

(1) Field 03-A ("In-Care-Of" Name) is in the Entity section of Form 8752.

(2) Valid Condition - Field 03-A ("In-Care-Of" Name) has 35 positions and the valid characters are alpha, numeric, ampersand (), dash (-), slash (/), or percent (%).

(3) Invalid Condition - Field 03-A ("In-Care-Of" Name) is invalid if any of the following conditions are present:

1. The first position is % (percent) and the second position is not blank.

2. The first position is blank.

3. The first position is not alpha or numeric.

4. There are two consecutive blanks between significant characters.

(4) Correction Procedures:

1. Correct all coding errors and transcription errors.

(1) Field 03-B (Foreign Address) is in the Entity section of Form 8752, Required Payment or Refund Under Section 7519.

(2) Form 8752 with a foreign address are processed at the Ogden Submission Processing Campus (OSPC).

1. Route any returns with foreign addresses to the OSPC for processing.

2. Prepare Letter 86C, Referring Taxpayer Inquiry/Forms to Another Office, to inform the taxpayer that the return has been sent to OSPC.

(3) Valid Condition - Field 03-B (Foreign Address) has 35 characters and the valid characters are alpha, numeric and special characters.

(4) Invalid Condition - Field 03-B (Foreign Address) is invalid if any of the following conditions are present:

1. The first position is blank.

2. There are two consecutive blanks followed by valid characters.

3. There are more than 35 characters present in the field.

   Note: ISRP will input a pound sign (#) as the 35th character if there are more than 35 characters present for this field on the return.

(5) Correct all coding errors and transcription errors.Correction Procedures

(6) If Form 8822, Change of Address, (or Form 8822-B, Change of Address or Responsible Party - Business), is attached to the return, compare the name and address information on the Form 8822 (or Form 8822-B) to the return.

(1) Field 03-C (Street Address) is in the Entity section of Form 8752.

(2) Valid Condition - Field 03-C (Street Address) has 35 characters, and the valid characters are alpha, numeric and special characters.

(3) Invalid Condition - Field 03-C (Street Address) is invalid if any of the following conditions are present:

1. The first position is blank.

2. Any characters are not alpha, numeric, blank, hyphen (-) or slash (/).

3. There are two consecutive blanks followed by valid characters.

(4) Correct all coding errors and transcription errors.Correction Procedures

(5) Field 03-C (Street Address) is invalid if a Major City Code (MCC) is present in Field 03-D (City) and a street address is not present.Address Criteria

(6) If Form 8822, Change of Address, (or Form 8822-B, Change of Address or Responsible Party - Business), is attached to the return, compare the name and address information on Form 8822 (or Form 8822-B) to the return.

(1) Field 03-D (City) is in the Entity section of Form 8752, Required Payment or Refund Under Section 7519.

(2) Valid Condition - Field 03-D (City) has a maximum of 22 characters.

(3) Invalid Condition - Field 03-D (City) is invalid if any of the following conditions are present:

1. The first position is blank.

2. A character follows the first two adjoining blanks.

3. Any character is not alpha or blank.

4. It is blank.

(4) Correction Procedures - Refer to the city shown on the return.

1. Correct all coding errors and transcription errors.

2. If the city on the return is illegible, refer to the envelope and attachments to determine the correct city.

3. If the city can't be perfected, delete the address section on the error register with Action Code 4.

(5) Field 03-D (City) and Field 03-E (State) are invalid if a Major City Code (MCC) is present and a state code is also present in Field 03-E (State).

(6) To correct this, refer to the return and Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, to verify the MCC.

(7) If the MCC is correct, delete the state code entered in Field 03-E (State).

(8) If the MCC is not correct:

1. Line through the MCC and enter the city’s full name in Field 03-D (City).

2. Verify that the state code entered in Field 03-E (State) is correct.

3. Enter Action Code 6 on the error register to the left of the address section.

(9) Field 03-D (City) and Field 03-F (ZIP Code) are invalid if an MCC is present and the ZIP Code is invalid for the city.

(10) To correct this, refer to the return and Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, to determine the correct MCC and ZIP Code.

1. Correct all coding errors and transcription errors.

2. If the ZIP Code and MCC were transcribed correctly and the ZIP Code is invalid for the city, refer to the envelope and attachments to locate a valid ZIP Code. If one is found, enter it in Field 03-F (ZIP Code).

3. If the correct ZIP Code is unavailable on the taxpayer's submission, research for the correct ZIP Code and enter it in Field 03-F (ZIP Code).

(11) Field 03-D (City) is invalid if the MCC is invalid.

(12) To correct this, refer to the return and Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, to verify the MCC.

1. Correct all coding errors and transcription errors.

2. Search for a valid MCC for the city on the return. If one is found, line through the entry in Field 03-D (City) and enter the correct code above it.

3. If the city on the return does not have a valid MCC, line through the code in Field 03-D (City) and enter the full name of the city.

(13) See Exhibit 3.12.249-7, U.S. Possessions/Territories and ZIP Codes, for use with address corrections.

(1) Field 03-E (State) is in the Entity section of Form 8752, Required Payment or Refund Under Section 7519.

(2) Valid Condition - Field 03-E (State) is two alpha characters.

(3) Invalid Condition - Field 03-E (State) is invalid if any of the following conditions are present:

1. It is blank and a MCC is not present in Field 03-D (City).

2. It is other than a valid state code.

(4) Refer to the return and Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, to determine the correct state code.

1. Correct all coding errors and transcription errors.

2. Determine the correct state code from Document 7475 and enter it in Field 03-E (State).

3. If the state can't be perfected, delete the address section of the error register.

(5) Field 03-E (State) and Field 03-F (ZIP Code) are invalid if the ZIP Code is invalid for the state.

(6) To correct this, refer to the return and Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, to verify the state and ZIP Code on the error register.

1. Correct all coding errors and transcription errors.

2. If the state code is incorrect, determine the correct code and enter it in Field 03-E (State).

3. If the ZIP Code is invalid for the state, refer to the envelope and attachments to obtain a valid ZIP Code.

4. If a valid ZIP Code can't be found on the taxpayer's return and attachments, research for the correct ZIP Code and enter it in Field 03-F (ZIP Code).

(7) Returns with foreign address changes and the following American possession address changes can be input via Integrated Submission and Remittance Processing (ISRP) with the return, the same as domestic address changes. U.S. Possessions/Territory and Abbreviations

(1) Field 03-F (ZIP Code) is in the Entity section of Form 8752, Required Payment or Refund Under Section 7519.

(2) Valid Condition - Field 03-F (ZIP Code) can 5, 9 or 12 numeric characters.

(3) Invalid Condition - Field 03-F (ZIP Code) is invalid if any of the following conditions are present:

1. It is not all numeric or blank.

2. There are not 5, 9 or 12 numeric characters.

(4) Correction Procedures - Refer to the return and attachments to determine the correct ZIP Code.

1. Correct all coding errors and transcription errors.

2. Compare the error register fields with the return. If incorrect, correct information.

3. Research any of the following for valid ZIP Code information: Document 7475, State and Address Abbreviations, Major City Codes (MCCs), ZIP Codes and Countries, or IDRS Command Code (CC) INOLES, CC NAMEB, CC NAMEE or CC ENMOD.

4. If only the first three digits of the ZIP Code can be determined, enter "01" in the fourth (4th) and fifth (5th) positions.

ZIP Code Criteria

If	And	Then
Unable to determine a valid ZIP Code from the return or attachments,		Enter the valid ZIP Code found through research in Field 03-F (ZIP Code).
The address is in a major city,	A Major City Code can be determined,	Enter Major City Code in Field 03-D (City).
The address is in a major city,	A Major City Code can't be determined,	Enter the name of the city in Field 03-D (City). Enter the State Code in Field 03-E (State).
The address is not in a major city,		Enter the correct state abbreviation in Field 03-E (State). Enter the ZIP Code in Field 03-F (ZIP Code).

(5) See Exhibit 3.12.249-7, U.S. Possessions/Territories and ZIP Codes, for a valid ZIP Code.

(6) The U.S. Postal Service (USPS) established new address requirements for Army Post Office (APO), Diplomatic Post Office (DPO), and Fleet Post Office (FPO) addresses. If the old address appears (e.g., APO New York, NY 091XX), convert to the new state code abbreviation based on the ZIP code (e.g., the previous example would be converted to APO AE 091XX). APO/DPO/FPO addresses are considered domestic addresses. Refer to conversion table below: AP/DPO/FPO Conversion Table