- 3.12.249.1 General
- 3.12.249.2 Processing Form 8752, Required Payment or Refund Under Section 7519
-
As an Error Correction tax examiner, you develop your expertise working all types of Business Master File (BMF) programs. As your expertise increases, you are also developing your judgement decisions to a comfort level needed to resolve your cases. In this Internal Revenue Manual (IRM) we have provided instructions, procedures, and guidelines for you in order to attain that comfort level needed for correcting cases in the Error Correction Program.
-
This section contains information regarding the purpose, scope, concepts, and instructions for Service Center Replacement System (SCRS) processing of Form 8752, Required Payment or Refund Under Section 7519.
-
The Service Center Replacement System (SCRS) is a term used to refer to the processing of paper register documents. While ERS (Error Resolution System) is worked on the computer with IDRS (Integrated Data Retrieval System), SCRS documents are corrected on a paper print, by hand, with a pen. The errors appear on computer printed error registers. SCRS programs are few in number as programs continue to be moved to ERS each year; the few that remain are generally received in such small numbers that it is considered too expensive to move them to ERS. Despite the low amounts of receipts, these forms are just as important to process correctly as those on ERS.
-
IRM 3.12.249 is exempt from the BMF Consistency Guidelines (e.g., indicating diamonds) as shown in other 3.11 Series IRMs and 3.12 Series IRMs.
-
This section provides instructions for resolving errors made by Form 8752 taxpayers and errors made during campus processing. These instructions apply to the Service Center Replacement System (SCRS).
-
This section provides procedures for correcting records that are printed on the error registers. Instructions in specific sections take precedence over general section instructions in case of a conflict.
-
The Restructuring and Reform Act of 1998 (RRA 98), Section 3705 provides identification requirements for all IRS employees working tax-related matters. IRS employees are required to give their name and unique identification number during taxpayer telephone, face to face and written contact. In addition, a telephone number is required on all taxpayer correspondence. This will provide taxpayers with enough information to identify an IRS employee who has previously assisted with tax-related matters.
-
All IRS employees, in the field, Headquarters and area, who communicate, by telephone, correspondence or face to face, with taxpayers or their personal authorized representatives, on tax-related matters, are required to provide (at a minimum) the following information:
-
Their title (e.g., Mr., Mrs., Ms., Miss),
-
Their last name, and
-
Their Identification (ID) card (badge) number.
-
-
Correspondence - All correspondence must include a telephone number where the taxpayer's question can be answered. In addition, manually-generated and handwritten correspondence must include the following information:
-
Their title (e.g., Mr., Mrs., Ms., Miss),
-
Their last name, and
-
Their Integrated Data Retrieval System (IDRS) number or ID card (badge) number.
-
-
The IDRS number is automatically generated. If it is not generated, or a handwritten note is prepared, the ID card (badge) number must be used. Toll-free employees may also provide their location for identification purposes. Facsimiles (faxes) to taxpayers on tax-related matters, are considered manually-generated correspondence and must include the required information.
Caution:
E-mail cannot be used to transmit taxpayer account information.
-
Correspondence, whether sent directly to the taxpayer or to the taxpayer's personal authorized representative, must contain the required information.
-
When a taxpayer requests to speak with a specific employee who previously handled his or her inquiry or request, or complains about the level of service previously provided, every attempt should be made to resolve the taxpayer's inquiry. If the issue cannot be resolved, the employee should refer the inquiry using established procedures to his or her manager.
-
Correspondex letters will require a specific employee name and telephone number only if the employee initiating the correspondence is in the best position to respond to any questions that the taxpayer may have about the correspondence, or the employee is asking the taxpayer to provide additional case-related information.
-
Otherwise, if the taxpayer does not need to contact a specific employee, the correspondence needs only an IRS telephone number and standard signature.
-
Secretaries, receptionists or other people who answer the telephone in functional offices need to identify themselves. They should provide their ID card (badge) number only if they are answering telephones which are routinely used to provide tax account information.
-
It is not necessary to repeat the ID card (badge) 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 by telephone or in-person) his or her ID card (badge) number on the first contact.
-
Prior to faxing confidential information to the taxpayer, review fax procedures contained in IRM 11.3.1.10, Facsimile Transmission of Tax Information.
-
During taxpayer contact, if taxpayer mentions hardship or asks to be referred to Taxpayer Advocate Service (TAS), see IRM 3.12.249.1.4.
-
In compliance with a Chief Counsel opinion issued September 2, 2008, tax examiners will no longer send returns back to the taxpayer when corresponding for missing signature, missing information and supporting schedules and documentation on refund or zero balance returns (with some exceptions). These changes are effective October 5, 2009.
Exception:
A non-taxable return with no line entries with an indication of previously filing a final return may be sent back to the taxpayer.
-
The Taxpayer Advocate Service (TAS) is an independent organization within the IRS whose employees assist taxpayers who are experiencing economic harm, who are seeking help in resolving tax problems that have not been resolved through normal channels, or who believe that an IRS system or procedure is not working as it should.
-
Refer taxpayers to the Taxpayer Advocate Service (TAS) (see IRM Part 13, Taxpayer Advocate Service) when the contact meets TAS criteria (see IRM 13.1.7, TAS Case Criteria) and you can’t resolve the taxpayer’s issue the same day. The definition of "same day" is within 24 hours. "Same day" cases include cases you can completely resolve in 24 hours, as well as cases in which you have taken steps within 24 hours to begin resolving the taxpayer's issue. Do not refer these cases to TAS unless they meet TAS criteria and the taxpayer asks to be transferred to TAS. Refer to IRM 13.1.7.4, Same-Day Resolution by Operations. When referring cases to TAS, use Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order), and forward it to TAS in accordance with your local procedures.
-
The following section provides information for Taxpayer Advocate Service (TAS) - Service Level Agreement (SLA).
-
The National Taxpayer Advocate has reached agreements with the Commissioners of the Wage & Investment (W&I) Division, Small Business & Self-Employed (SB/SE) Division, Tax Exempt & Government Entities (TE/GE) Division, Criminal Investigation (CI), Appeals and Large & Mid-Size Business (LMSB) Division, that outline the procedures and responsibilities for the processing of Taxpayer Advocate Service (TAS) casework when either the statutory or delegated authority to complete case transactions rests outside of TAS. These agreements are known as Service Level Agreements (SLAs).
-
The SLAs are located at http://tas.web.irs.gov under the heading "Policy/Procedures/Guidance" .
-
The tax examiners applying these instructions must be familiar with the editing procedures in IRM 3.11.249, Processing Form 8752, and the general procedures in IRM 3.12.38, Error Resolution - BMF General Instructions. The telephone may be used to resolve questions pertaining to returns that are on the error register in lieu of rejecting those returns for subsequent correspondence action.
Note:
Any items that denote a protest should be referred immediately to the SC Criminal Investigation Branch.
-
You are not expected to review or redo the work of the Code & Edit tax examiner. However, if an error or omission made by the tax examiner is noticed 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 you to do something without telling you how, refer to IRM 3.11.249.
-
This manual is your main source of information. You may also need to research procedures in the following IRMs:
-
IRM 1.15.29, Records Control Schedule for Submission Processing Campus Records
-
IRM 2.3, Terminal Responses.
-
IRM 2.4, Terminal Input.
-
IRM 3.0.273, Administrative Reference Guide.
-
IRM 3.10.72, Extracting, Sorting and Numbering.
-
-
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.
-
Correct the error register as if no prior attempt at correction has been made.
-
Only a (10%) ten percent underpayment penalty can be charged on a Form 8752 account.
Note:
Transaction Code (TC) 240 (Miscellaneous) or TC 246 (Form 8752 or Form 1065 Penalty) penalty may be charged.
If a penalty is shown on the return, and the notation, "3465 Prepared," does not appear on the return, prepare a Form 3465, Adjustment Request, to request an assessment of the penalty.
-
Indicate on the Form 3465 the portion 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. Enter Computer Condition Code (CCC) "X" on the return and on the register to freeze the module from refunding or offsetting, note on the return, "3465 Prepared," and route the Form 3465 to Accounts Management (AM).
-
For additional information, refer to IRM 20.1.10.26.3 (Assertion/Assessment), in IRM Section 20.1.10, Excise Tax Penalties and Miscellaneous Penalties.
-
Statute of Limitations processing does not apply to Form 8752 because the form is considered a required deposit by the taxpayer and not a payment of tax due.
-
The following is a chart of Tax Class, Document Code, and MFT for Form 8752.
Form 8752 Tax Class 2 Document Code 23 MFT Code 15
-
Action Codes (ACs) are used to correct errors on the paper register. Every correction made on an error register or reject register must have an Action Code (AC). The Action Code signifies to the computer what action should be taken. Using Action Codes is similar to correcting an error screen on the computer, though the process is not as instantaneous.
-
Each Action Code (AC) has a different purpose. Only one AC may be entered at any time. If two different Action Codes are used, the record will loop with no corrections made. If incorrect data is present in addition to non-correctible 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 AC 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 AC 1 is used. Individual descriptions of the valid Action Codes for most error registers are provided below.
-
Action Code 0 is used to indicate that the data in the record is correct and that the computer's computations should be disregarded. The taxpayer's figures must be verified before using this action code. This code should never be used unless 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 MCC (Martinsburg Computing Center). Action Code " 0" is written to the left of Section 01.
-
Action Code 1 is used in conjunction 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 AC 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 document.
-
Action Code 2 is used to delete a rejected record from processing. It cannot be used on a raw register. Only Rejects will use Action Code "2" . Action Code 2 is written to the left of Section 01.
Note:
This action code is NOT used in Form 8752 processing.
-
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 appropriate routing slip, stating why the document is being rejected. Any of the following types of documents can be unprocessable.
-
A return or other document with illegible or missing necessary data.
-
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.
-
A return or other document that cannot be processed by the program under which it was blocked and which must be processed with a DLN for a different program.
-
An amended or substitute return where the original document is not available.
Note:
Never use Action Code 3 on a Reject register. See Action Code 9.
-
-
Action Code 4 is used to delete a section from a record. This AC 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 indicated on the register and will appear as the first two digits on the first line of print for each section. All sections cannot be deleted; therefore, a record with only one section cannot have an Action Code "4" correction. It cannot be used on certain sections, such as Section 01, which are required for processing. AC 4 is written to the left of the section to be deleted.
-
Action Code 5 is used to add a section to a record when the section was not transcribed. The AC is written in the space below the last printed section of the error record. Write in the section number, with AC 5 to the left of it, and write the Alpha Field Designators with their field data and field breaker in the order that they normally appear in the section. Only fields containing data need to be written in.
-
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 AFD and prints the AFD before the field on the register. The AC is written to the left of the section in which there is a field that requires correction. To correct an invalid field:
-
Draw a line through the incorrect information; do not line through the Alpha Field Designator or Field Breaker.
-
Write the correct information directly above the lined-out field. Use all capital letters and write as clearly and legibly as possible.
Any number of fields may be changed in the section at the same time. AC 6 can also be used more than once; if invalid fields appear in multiple sections, the AC should appear to the left of each section in which there is a field that requires correction. When the name control (a fixed-length field) must be left partially blank, enter the number of spaces to the right in the correct data above the field. This number must be encircled.
-
-
Action Code 7 is used to indicate that the data on the register is correct and that no action is necessary. AC 7 may not be used with any other Action Codes. All corrections requiring Action Codes 4, 5, and 6 must be done before Action Code 7 may be used. This AC may be used to clear a record which has been sent to the 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 the AC 7 to clear this item if no error exists.
Note:
Be cautious when determining whether to use AC 7. If there is another error in the register, and AC 7 is mistakenly used, the register will loop and return to ERS with the original error still requiring correction. AC 7 will not make any error condition "go away" and therefore should be used sparingly.
-
Action Code 9 is used to re-reject a reject loop register for correspondence or other suspense action. Action Code 9 is written to the left of Section 01.
-
This code is used to prevent a reject loop record from reprint each time the loop is run, if it is clear that the record is not ready for correction.
-
Action Code 9 is valid for reject loop only. It is not valid for raw rejects or for 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.
-
-
Enter Action Codes 0, 1, 2, 3, and 7 on the error register to the left of Section 01, and enter Action Codes 4, 5, and 6 to the left of the appropriate section number.
-
ISRP Error is an error that has been identified by the Integrated Submission and Remittance Processing (ISRP) edit run.
-
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:
ISRP Error Indicator Type of Error Error Explanation #1 Split screen transmission Key Verifier attempted to change Check Digit, Key Verifier changed 4 or more digits of Taxpayer Identification Number (TIN), or the Original Entry (OE) Operator (data transcriber) entered a required section as "missing" . #3 Invalid section ending point #4 Invalid field length #5 Questionable section The ISRP operator input the same section more than once. The computer program will drop all duplicate sections and display the first one encountered on the error register. -
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 insure the return data is for the taxpayer whose name is in Section 01.
-
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.
-
A Terminus Error results when:
-
A non-numeric character appears in a numeric field, or
-
The format of the section is incorrect.
-
-
When this error is present, two asterisks will appear to the immediate left of the section number.
-
Correct a Terminus Error as follows:
-
Compare the return with the error register.
-
Assure that any fields already containing data are correct. Correct or reject as applicable.
-
Enter data in any blank fields that should contain data.
-
-
If data is correct on register, re-enter a field, using Action Code 6 to send the record to good tape.
-
Field Validity Errors are the most common type of errors.
-
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 contain data, and if they are blank, they are invalid. The field will be in error if:
-
An invalid character is present in a field;
-
The field is otherwise incomplete or invalid; or
-
A math error is present.
-
-
Correct a Field Validity Error as follows:
-
Compare the return with the error register;
-
Line out the incorrect field, and enter the correct data immediately above the lined-out data; and
-
Enter Action Code 6.
-
In some cases, A Taxpayer Notice Code (TPNC) must be sent, or another action must be taken.
-
-
There are some fields which 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.
-
Taxpayers may send a blank return stating that they are not required to file or don't understand why they are receiving the Form 8752.
-
Research to ensure that the filer is still on a fiscal year basis. If a fiscal year filer, Form 8752 must be filed unless:
-
The entity or filer existed prior to August 1988 or the legislative issuance/modifications of Section 444 and 7519 (legislation was dated July 26, 1988).
-
The filer is a fiscal filer with an acceptable (e.g., Service-approved) business year purpose to file on a fiscal year basis. This is based on the owner's filing year (first month of the owner's fiscal year 1040).
-
-
If a fiscal year filer and 2(a) or (b) do not apply, initiate correspondence. Inform the taxpayer that a partnership or S Corporation must file Form 8752 if it made a Section 444 election to file their tax return on a fiscal year basis instead of the required calendar year basis.
If after correspondence Then the taxpayer replies and indicates that he is not required to file because he meets the conditions in either 2(a) or (b) above, 1. Prepare Form 4227, Intra-SC Reject or Routing Slip or appropriate routing slip. Attach a photocopy of the taxpayer's response.
2. Route to Entity Control to correct the taxpayer's filing requirement.
3. Void the blank return.the taxpayer replies and indicates that he is not required to file and does not offer an explanation, 1. Void the blank return.
2. Prepare Form 4227, or appropriate routing slip, noting on it that the taxpayer provided no explanation why he/she is not required to file a Form 8752.
3. Attach a photocopy of the reply to the 4227 and route to the Entity Control Function.the taxpayer does not reply, 1. Void the blank return.
2. Prepare Form 4227, or appropriate routing slip, noting on it that the taxpayer did not reply to (Form 8752) correspondence.
3. Route to Entity Control. -
If the taxpayer is no longer a fiscal-year filer, do not process the Form 8752. Void the blank return.
-
A frivolous argument is used for the purpose of expressing dissatisfaction with the substance, form, or administration of the tax laws by attempting to illegally avoid or reduce tax liabilities. Recognized frivolous arguments made by business include, but are not limited to, the examples in IRM 4.10.12.1.1, Frivolous Argument. Also, see Exhibit 3.12.249-3 , Potential Frivolous Arguments for Examination Review.
-
Review the return to determine whether it appears to be a frivolous return.
If Then The return meets any of the conditions identified as a frivolous return. Caution:
If the return shows Action Code "440" Ogden Submission Processing Campus (OSPC) or "331" Cincinnati Submission Processing Campus (CSPC), and has a Form 4227 attached with the remarks, "Refer to Exam FRP for audit after processing," continue to next procedure.
Remove return from the batch and place the return in the locally designated basket for Examination, Frivolous Return Processing (FRP) for review. Note:
IRM 4.10.12.1.3.3 requires Examination to expedite the return and make a determination whether it qualifies as a frivolous return within two (2) business days. If a determination is not made within the allowed time frame, the Examination tax examiner will edit Action Code "440" (OSPC) or "331" (CSPC) in the lower left margin of the return preceded with the letters "AC" .
Examination has selected the return as frivolous, e.g. indicated by an Action Code "440" (OSPC) or "331" (CSPC), and a Form 4227 with the remarks, "Refer to Exam FRP for audit after processing" , but sends the return for processing, Continue processing the return using procedures in IRM 3.12.249. However, do not circle or void the Action Code indicating a frivolous return. Note:
Returns having only zeros, no entries, are blank or indicate "None," "Not Liable" , etc. with no evidence of a frivolous argument are not to be considered as frivolous returns.
-
Correspondence Imaging System (CIS) is an inventory system for scanning all Accounts Management (AM) receipts into digital images and working the cases from those images.
-
"CIS" returns are identified with "CIS Image — Do not correspond for Signature" stamped below the signature line or "CIS" annotated on the front of the return.
-
Follow the instructions below for processing "CIS" returns.
If And Then The "CIS" return has a Form 13596, Reprocessing Returns, attached, Note:
If there is an indication on the return that correspondence has been sent (e.g., CCC "3" is edited on the return), do not route return to Accounts Management (AM). Continue processing the return.
The return is not complete (e.g., missing signature, schedules or forms), 1. Enter Action Code 3 and reject the record.
2. Attach Form 4227 or appropriate routing slip to the return and route to AM to secure missing information.Note:
Do not correspond for missing information on "CIS" reprocessable/reinput returns.
The "CIS" return does not have a Form 13596 attached The return is not complete (e.g., missing signature, schedules or forms), Follow normal correspondence procedures.
-
This section provides background information, descriptions of three sections of the error register, the individuals fields and their designations, and procedures for correcting Form 8752, Required Payment or Refund Under Section 7519.
-
The paper register is the physical representation of the tax document and any errors that have been identified. It is essentially a printed form of the data input from the document, and appears in a standardized format which is used for nearly every type of SCRS program. Data fields are designated with letters of the alphabet. Each section is designated with the section number.
-
The Error Register contains 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.
-
Errors appear much differently on paper registers than they do in ERS (error codes). Most errors can be located 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 with Command Codes can be used to correct some Entity errors.
-
Form 8752 is filed by partnerships (Form 1065, U.S. Partnership Return of Income) and S Corporations (Form 1120S, U.S. Income Tax Return for an S Corporation) who made the Section 444 election to file their income tax on a fiscal year, rather than a calendar year. Partnerships and S Corporations use Form 8752 to figure and report the payment required under IRC Section 7519 to obtain a refund of net prior-year payment(s). A partnership or S Corporation must file Form 8752 if it made a Section 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 a Section 444 election is in effect, including the first tax year the Section 444 is made, is an "applicable election year." Prior to 1991, the Section 444 payment made by these taxpayers was reported on Form 720, Quarterly Federal Excise Tax Return, under Abstract 11.
-
Taxpayers electing Section 444 are not required to remit a payment until a liability in excess of $500.00 has been incurred. However, taxpayers must file Form 8752 if the taxpayer was required to make a payment in a prior tax year, even if the current required payment is $500.00 or less. Thereafter, the taxpayer must continue to make the required payment even when the amount due is below the $500.00 threshold.
-
Due Date: For applicable election years beginning in 1990, Form 8752 must be filed and required payment made on or before May 15. See IRM 3.12.249.2.2.8 for additional information.
-
This section provides field criteria, descriptions, and specifications for correcting Form 8752.
-
Section 01 fields on the Error Register are shown below: alpha designator, title, field length, and location on the return. See Exhibit 3.12.249-1 , Form 8752, Required Payment or Refund Under Section 7519, for additional information. See Exhibit 3.12.249-2 , Error Register for Form 8752, for additional information.
Section 01 Alpha Designator Title Field Length Location on the Return A Remittance (non-correctable) 11 Green Writing B Name Control/Check Digit 4 Box Entitled Name of Partnership or S Corporation C Employer Identification Number 9 Box Entitled Identification Number D Tax Period 6 Center of Return above Name Line or edited Tax Period to the left of the OMB E Computer Condition Code 10 Upper left margin of Return F Received Date 8 Middle of return G Penalty and Interest Code 1 Right of OMB Number H Partnership/S Corporation Indicator 1 Right of Page 1, Form 8752, "Check Applicable Box to Show Type of Taxpayer" I Centralized Authorization File (CAF) 1 Right Lower Corner J First Tax Year Box 1 Box B K Terminating Event Box 1 Box C L Short Base Year Box 1 Box D M Entity Underprint Code 1 N Taxpayer Notice Code 6 Left Margin Name Area
-
The field cannot 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 appropriate routing slip, to explain the error. The Reject function will prepare Form 3893, Re-Entry Document Control, after corrective action has been taken.
-
Received Date — If a remittance amount is present, the received date must be present. See IRM 3.12.249.2.2.7.
-
The Reject unit will determine the proper application of an excess remittance through research, correspondence, or other existing procedures.
-
When the Reject tax examiner determines that the remittance should be applied to a different tax class or module, Condition Code "X" is entered on the return and on the register. This code will freeze the tax module from refunding or offsetting by generating a TC 570.
-
The tax examiner will prepare Form 3465, Adjustment Request, to indicate the amount and module in which the credit should be applied.
-
See IRM 3.12.38, Error Resolution - BMF General Instructions, if additional information is required.
-
This field must have 1 to 4 characters. If there are fewer than 4 characters, every position must be accounted for by editing the number of blanks and encircling it. The name control and check digit each have their own tests for validity.
-
A check digit will always be your first correction choice. It is invalid if:
-
The 1st and 2nd positions are not blank.
-
The 3rd and 4th positions are not letters.
-
The letters E, G, or M are present.
-
-
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, refer to the check digit on the label.
-
Correct any transcription errors by lining through the entry in Field 01-B (Name Control/Check Digit) and editing an encircled "2" , followed by the two-letter check digit from the mail label.
-
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.
-
-
A name control will be entered if the check digit is not available. It is invalid if:
-
The 1st position is other than a letter or number.
-
The 2nd, 3rd and 4th positions contain characters other than letters, numbers, ampersands (&), hyphens (-), or blanks.
-
Any character follows a blank.
-
-
To correct, line through the entry in Field 01-B (Name Control/Check Digit) and enter the correct name control above it. If the name control contains fewer than 4 characters, enter and circle the number of positions remaining.
-
To determine the correct name control, follow the guidelines in Document 7071, Name Control Job Aid.
-
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/Check Digit).
-
The name control underprint will be removed when the following occurs:
-
The name control underprint and the entry in Field 01-B agree.
-
Field 01-M (Entity Underprint Code) contains a "1" .
-
-
When the name control on the return does not match the name control on the EIF, one of the following has occurred:
-
The EIN was entered wrong, either by the taxpayer or the IRS.
-
The name control was edited or transcribed incorrectly.
-
The name control on the EIF is incorrect.
-
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).
-
The taxpayer’s name changed.
-
The taxpayer’s identity has changed (e.g., the taxpayer has changed from a partnership to a corporation).
-
-
To correct, compare the entries in Field 01-B (Name Control/Check Digit) and Field 01-C (EIN) to the name control and EIN on the return.
-
If the EIN on the return and the EIN in Field 01-C do not agree, correct Field 01-C to agree with the return.
-
If the correct name control is in Field 01-B, enter a " 1" in Field 01-M (Entity Underprint Code).
-
If the name control in Field 01-B is not correct, according to the information on the return, change Field 01-B.
-
If the correction does not agree with the name control underprint, enter a "1" in Field 01-M (Entity Underprint Code).
-
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 appropriate routing slip, notating, "Move ISRP Remittance Processing money." Rejects will research IDRS (Command Codes BMFOL or MFTRA) to determine if the payment has posted incorrectly. See IRM 3.12.38, Error Resolution - BMF General Instructions, for detailed instructions. If the money is posted incorrectly, prepare a Form 3465, Adjustment Request, or follow local service center procedures to transfer the money to the correct module. Note "3465 prepared" on the return and enter CCC "X" on the return and in Field 01-E (CCC).
-
-
If the EIN on the return agrees with the EIN in Field 01-C, 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 then:
-
Compare the name control underprint with Field 01-B 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 document, change Field 01-B to agree with the underprint.
-
If it is not an obvious error, request research per local service center procedures. (See IRM 2.3, Terminal Response, and IRM 2.4, Terminal Input.) Research, using the IDRS Command Codes.
-
-
Determine the correct EIN and name control from the research.
-
If another EIN is found for the entity on the return, change Field 01-C to the correct EIN and follow the procedures in (10) above.
-
If the EIN on the return is correct and the taxpayer just rearranged the name on the return, change Field 01-B to agree with the name control on the EIF.
-
If the EIN is changed from the one the taxpayer used, issue Letter 3875C as a non-suspense letter to the address on the return.
Note:
Do not send Letter 3875C if three or less digits of the EIN are transposed, different or missing or when INOLES indicates the account has been "merged to" or "merged from" .
-
-
If the EIN on the return is correct but the name control on the EIF is not conforming to the acceptable rules for name controlling:
-
Correct Field 01-B to agree with the name control on the BMF.
-
Copy page one of the return and notate "Copy, do not process." Attach any research, and Form 4227, Intra-SC Reject and Routing Slip, or appropriate routing slip, and forward the case to Entity Control. Entity Control will fix the name control, which should stop future unpostables and underprints.
-
If the EIN on the return and in Field 01-C agree, but the name control does not agree with the name on the EIF, attach Form 4227 to forward the case, along with any research, to Entity Control for resolution.
-
-
This field has nine positions.
-
It is invalid if any of the following conditions occur:
-
It is not nine numeric characters.
-
It is all nines or all zeros.
-
If the first two digits are: 00, 07, 08, 09, 17, 18, 19, 28, 29, 49, 78, 79, or 89.
-
-
If the EIN is invalid, take the following action:
-
Compare with the EIN on the return, and correct the error register with Action Code 6, if the number has been incorrectly transcribed.
-
Search the return and any attachments for a valid EIN if transcribed correctly. If one is found, enter the number on the return, and correct the Error Register with Action Code 6. If no valid EIN is found, research per IDRS (CC EINAD/NAMEE) or follow local service center procedures.
-
If it is transcribed correctly, and a valid EIN is not found during the search prescribed above, reject the record to Entity Control. Attach Form 4227 (or appropriate routing slip) and notate " Research for valid EIN" .
-
-
Reject Correction:
-
If Entity Control has found the correct EIN, enter it in Field 01-C (EIN).
-
If Entity Control has assigned an EIN, enter it in Field 01-C (EIN).
-
-
This field contains 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, 2009, is printed 200912 ). The Tax Period must be for a calendar year only (e.g., 200912 and 200812).
-
The field is invalid if:
-
It is not numeric.
-
The tax year ending is later than the current date.
-
The year is before 199012.
-
The month is not 12.
-
It is in a format other than YYYYMM.
-
-
Determine the Tax Period by the year (printed) on the face of the tax form (e.g., for the 2009 tax form, the tax period should be "200912" ). Taxpayers are advised to edit changes on the form to the tax year for prior tax periods.
-
The Tax Period must be a calendar year (e.g., 200X12). Editing is required only if the "applicable election year ending" is other than blank or December 31, 200X. Circle the taxpayer’s entry and enter the correct Tax Period.
-
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 as a calendar-year period, using the procedures described above.
-
If there are multiple returns from the same entity in a batch and you cannot determine the correct Tax Period, edit all of them to the current Tax Period (200X12). Accounts Management will work the "dup" returns and correct the Tax Periods.
-
Editing of the Tax Period is not required if the current year form is used (e.g., 2009 form), since Form 8752 is a calendar-year return.
Exception:
The taxpayer makes an indication on the form that the tax period is for a prior-year.
-
If any version of Form 8752 other than the current-year form is submitted, edit the current year in the "200X12" format under the title of the form (unless the taxpayer has indicated the tax period is for a prior-year).
Note:
Make sure that the taxpayer used the correct tax rate for the appropriate year on Line 9a. The tax rate for Tax Years 2003 through 2010 is 36%. (The tax rate decreases for Tax Years 2001 and subsequent were a result of H.R. 1836 ("The Economic Growth and Tax Relief Reconciliation Act of 2001" , signed into law on June 7, 2001).) The tax rate for Tax Year 2002 was 39.6%; for Tax Year 2001, 40.1%. The tax rate for 1993 through to December 31, 2000, was 40.6%. The tax rate for 1990 was 29%; for 1991 and 1992, it was 32%.
Note:
For Tax Year 2011, the tax rate for this form changes back to the original rate of 40.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 and prepare a Form 4227, Intra-SC Reject or Routing Slip, or appropriate routing slip, to request Rejects to research for postings.
If Then Current year has posted, Hold in suspense until January of year due. Current year has not posted, Process as current year return. Note:
If payments posted to the wrong tax period, follow instructions in IRM 3.12.38, Error Resolution - BMF General Instructions.
-
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 the Form 8752. Computer Condition Codes (CCCs) D, F, G, O, R, U (on ISRP (Submission Processing) input only), X, and 7 are valid for Form 8752 processing.
-
The field is invalid if CCCs other than those listed above are used. See IRM 3.12.249.2.2.6.1 through IRM 3.12.249.2.2.6.9 for descriptions of the CCCs.
-
See IRM 3.12.249.2.2.6.10 for Field 01-E (CCC) correction procedures.
Note:
Legislation (2001) extended reasonable cause criteria to Form 8752 filers. You may refer to IRM 3.12.38, Error Resolution - BMF General Instructions, for reasonable cause criteria.
-
≡ ≡ "≡ ≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If the taxpayer requests an abatement for Failing to Pay Timely when the return is submitted, Code and Edit will send Letter 1382C (Penalty Removal Request Incomplete) to inform the taxpayer of the proper procedure to follow to request abatement, if and when, a penalty is assessed.
-
Issue Letter 1382C (if Code and Edit has not done so) and continue processing the return (see exception below).
-
Exception: Secured returns, Disaster returns and Reprocessing returns.
-
For Secured returns (e.g., returns with an attached Form 13133, Expedite Processing Cycle), enter the applicable CCC as indicated on the return and/or attached form.
-
Disaster provisions may apply if the taxpayer has identified the return as being subject to reasonable cause because of a specific disaster declaration.
-
For Reprocessing returns (e.g., returns with an attached Form 13596), enter the applicable CCC as indicated on the return and/or attached form.
-
-
See IRM 3.12.249.2.2.6.9 for additional information. Also, you may refer to IRM 3.12.38, Error Resolution - BMF General Instructions, for reasonable cause criteria.
-
Enter CCC "F" when the taxpayer gives a positive indication that they are not liable for filing future returns. Notations such as (but not limited to) the following:
-
Final
-
Deceased
-
Out-of-Business
-
Liquidation
-
Exempt under IRC Section 501(c)(3)
-
Dissolved
-
IRC Section 444 was terminated.
Note:
In cases regarding Form 8752, any references to a "terminating event" may also apply in determining whether this is a final return.
-
-
Enter CCC "G" on return marked "Amended " , "Supplemental" , "Duplicate" , "Corrected" , "Additional" , or any other positive indication that the taxpayer has filed previously.
-
Enter CCC "O" if a completed Form 3753, Manual Refund Posting Voucher, or Form 5792, Request for IDRS Generated Refund, is attached to the return. These indicate that a presettlement manual refund was made.
-
≡ ≡ "≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If the taxpayer requests an abatement for Reasonable Cause for Failing to Timely File Return when the return is submitted, Code and Edit will send Letter 1382 (Penalty Removal Request Incomplete) to inform the taxpayer of the proper procedure to follow to request abatement, if and when, a penalty is assessed.
-
Issue Letter 1382C (if Code and Edit has not done so) and continue processing the return (see exception below).
-
Exception: Secured returns, Disaster returns and Reprocessing returns.
-
For Secured returns (e.g., returns with an attached Form 13133, Expedite Processing Cycle), enter the applicable CCC as indicated on the return and/or attached form.
-
Disaster provisions may apply if the taxpayer has identified the return as being subject to reasonable cause because of a specific disaster declaration.
-
For Reprocessing returns (e.g., returns with an attached Form 13596), enter the applicable CCC as indicated on the return and/or attached form.
-
-
See IRM 3.12.249.2.2.6.9 for additional information. Also, you may refer to IRM 3.12.38 for reasonable cause criteria.
-
Enter CCC "U" on all conditions which cause the documents to be unprocessable. Unprocessable (Form 8752) conditions are described as follows:
-
Name illegible, incomplete, or contradictory and is not acceptable for computer processing.
-
Information is not available on the document or attachments that is necessary for processing the document.
-
EIN is other than nine numeric digits.
-
Issuer indicates on documents or attachment that the document represents more than one tax period.
-
Blank returns where the filer states "not required to file" , or he/she does not know why they received the Form 8752 (or a similar statement).
-
-
CCC "W" is no longer edited by Code and Edit. . This does not apply to Form 8752 processing. Statute of Limitations processing does not apply to Form 8752 because the form is considered a required deposit by the taxpayer and not a payment of tax due.
-
Enter CCC "X" taxpayer indicates that excess remittance with return or overpayment be applied to another account. Enter "X" in Field 01-E with Action Code 6.
-
CCC "7" is no longer edited by Code and Edit. See IRM 3.12.249.2.2.6.1 and IRM 3.12.249.2.2.6.5 for additional information.
-
Enter CCC "7" when the taxpayer furnished unacceptable reason(s) for failing to file or pay the tax timely.
-
Do not enter CCC "7" if CCC "D" (Reasonable cause for failure to pay taxes timely) and CCC "R" (Reasonable Cause for Delinquency) are present. CCC "7" can be present with CCC "D" or with CCC "R" , but not with both.
-
The presence of CCC "7" with CCC " D" means reasonable cause for delinquency (CCC "R" ) was denied. CCC "7" with CCC "R" means reasonable cause for failure to pay taxes timely (CCC "D" ) was denied. Determine which code(s) should be present and correct Field 01-E (CCC) with Action Code 6.







