Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

3.12.106  Estate Tax Returns - Paper Correction Processing

Manual Transmittal

November 04, 2011

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

Purpose

(1) This text transmits revised IRM 3.12.106, Error Resolution - Estate and Gift Tax Returns - Paper Correction Processing.

Material Changes

(1) IMPORTANT: The long-awaited legislation for Estate, Gift, and Generation-Skipping Transfer (GST) Tax was passed last year. The "Tax Relief, Unemployment Insurance Reauthorization, and Job Creation Act of 2010" (Public Law 111-312, also known as H. R. 4853) was enacted on December 17, 2010. Act Sec. 302(c) (entitled, "Modifications to estate, gift, and generation-skipping transfer taxes" ) amends IR Code section 2505(a)(1) to determine that, in the case of any generation-skipping transfer (GST) made AFTER December 31, 2009, and BEFORE January 25, 2011, the applicable GST rate determined under Code section 2641(a) shall be zero (0). Form 706-GS(D) (Generation-Skipping Transfer Tax Return for Distributions), and Form 706-GS(T) (Generation-Skipping Transfer Tax Return For Terminations), were issued concurrently for Tax Years 2010 and 2011. The tax rate for the Tax Year 2010 returns is zero percent (0%), while the tax rate for Tax Years 2011 and Tax Year 2012 Forms 706-GS(D) and 706-GS(T) is 35% percent. As a result, there is NO repeal of Estate and Generation-Skipping Transfer (GST) taxes; all Forms 706-GS(D) and 706-GS(T) submitted for Tax Years 2010 and 2011 must be processed.

(2) IRM 3.12.106.1.3 - Introduces new text, entitled, CADE 2/IMF Daily Processing, which provides information about the replacement to the Customer Account Data Engine (CADE).

(3) Removed all text references to special (repeal) procedures issued for handling of Tax Forms 2010 returns. Those procedures were previously contained under former transmittal (for January 2011) in former TRIDOC IRM 3.12.106.1.3 for Tax Year 2010 forms ONLY

(4) IRM 3.12.106.3 - Includes text information regarding two versions of the Form 706-GS(D) issued in Calendar Year 2011.

(5) IRM 3.12.106.3.1.1. Includes revised text for Due Date (Form 706-GS(D) because of weekend and holiday.

(6) IRM 3.12.106.3.1.7. Includes revised text procedures for correcting Field 01-F, Received Date (Form 706-GS(D), to conform with BMF Consistency text instructions. Includes changes to priority/criteria for determining a missing or illegible Received Date.

(7) IRM 3.12.106.3.3.8 - Includes revised instructions for Field 03-H (Line 7)—Multiply Line 5 by Line 6 (previously referred to as "Generation Skipping Transfer tax (multiply line 5 by line 6)" ).

(8) IRM 3.12.106.3.3.9 - Includes revised instructions for Field 03-I (Line 8 (Form 7004 Payment Amount)).

(9) IRM 3.12.106.3.3.10 - Includes revised instructions for Field 03-J (Line 9/Line 10 (Tax Due/Overpayment).

(10) IRM 3.12.106.4 - Includes text information regarding two versions of the Form 706-GS(T) issued in Calendar Year 2011.

(11) IRM 3.12.106.4.1.1 Includes revised text for Due Date (Form 706-GS(T) because of weekend and holiday.

(12) IRM 3.12.106.4.3.1 Includes revised text for Field 03–H—Total GST Tax (Line 10).

(13) Includes revisions to figures and exhibits throughout the text.

(14) Includes various editorial changes made throughout the text.

Effect on Other Documents

This material supersedes the IRM 3.12.106, dated January 1, 2011, based on guidance in IRM 1.11.2.5.6, Significance of the Manual Transmittal.

Audience

These instructions will be used by Input Correction Operations, ERS Department, when resolving processing errors on revenue receipt forms and documents. Wage & Investment (W&I) and Small Business/Self-Employed (SB/SE).

Effective Date

(01-01-2012)

Signed by Jerald H. Heschel
Director, Submission Processing
Wage & Investment Division

3.12.106.1  (01-01-2012)
General

  1. This sub-section provides descriptions of the purpose, scope, abbreviations, and definition of terms used in processing of certain Form 706 series returns.

3.12.106.1.1  (01-01-2012)
Purpose and Scope

  1. This Section provides instructions for correcting error and reject registers for estate, gift, and generation-skipping tax returns. Records appear on registers because of validity, consistency, math, and/or input errors.

  2. These are instructions used for correcting paper registers of the following Business Master File (BMF) returns:

    • Form 706-GS(D), Generation-Skipping Transfer Tax Return for Distributions.

    • Form 706-GS(T), Generation-Skipping Transfer Tax Return for Terminations.

  3. If general and specific instructions conflict, always follow specific instructions.

  4. It may be necessary to refer at times to instructions in the following IRMs:

    • IRM 3.11.106—Returns and Document Analysis---Estate and Gift Tax Returns

    • IRM 3.12.38—Error Resolution---BMF General Instructions

    • IRM 3.24.106—ISRP System---Estate Tax Returns

  5. Refer to IRM 3.12.263, Error Resolution - Estate and Gift Tax Returns - Error Resolution System (ERS) Corrections, for correction information regarding the following forms:

    • Forms 706, United States Estate (and Generation-Skipping Transfer) Tax Returns;

    • Forms 706NA, United States Estate (and Generation-Skipping Transfer) Tax Returns; and,

    • Forms 709, United States Gift (and Generation-Skipping Transfer) Tax Returns.

3.12.106.1.2  (01-01-2012)
General Requirements—Forms 706 series

  1. Instructions provided in the following are to be used in conjunction with the IRM:

    Form 706-GS(D) IRM 3.11.106.17
    Form 706-GS(D–1) IRM 3.11.106.18
    Form 706-GS(T) IRM 3.11.106. 19

3.12.106.1.3  (01-01-2012)
CADE 2 / IMF Daily Processing

  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 provides daily processing of taxpayer accounts.

    Note:

    The CADE Master File, as it existed from 2004 – 2011, will transition from Production and be retired at the end of 201152.

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

    Note:

    This version of the IRM will only provide information related the Transition State 1, which will be deployed in January 2012. Additional information on Transition State 2 and the Target State phases will be provided in the later revisions of the IRM when the solutions are implemented.

  3. Accelerated IMF – All Individual taxpayers account transactions being processed weekly by IMF (on Thursday) with new cycle definitions and accelerated refund and notice issuance. The new 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

      Note:

      New Cycles are not limited to IMF Sites. BMF sites will also have the new campus cycle.

  4. IMF transactions posting timeframes are outlined as follows:

    1. Daily transactions directed to a daily account are expected to post daily with daily processing. Transactions will be viewable using CFOL command codes the second day after campus input. Transactions will be viewable on IDRS command codes the third day after campus input.

    2. Weekly transactions directed to a daily account are expected to post with the weekly processing run on Thursday and may result in the account type changing to Weekly.

    3. Daily and Weekly transactions directed to a Weekly account are expected to post with the weekly processing on Thursday.

      Note:

      For items b and c, transactions will be viewable using CFOL command codes on the Saturday following the Thursday processing run. Transactions will be viewable on IDRS command codes Monday following the Thursday processing run.

  5. BMF transaction posting timeframes are outlined as follows:

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

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

      Note:

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

  6. IMF transaction posting dates will reflect a format of "YYYYCCDD" . "YYYY" will indicate the year. "CC" will indicate the posting cycle. For IMF transactions, the following values for "DD" are defined:

    1. 01 = Friday

    2. 02 = Monday

    3. 03 = Tuesday

    4. 04 = Wednesday

    5. 05 = Thursday

      Note:

      BMF transaction posting dates will continue to reflect YYYYCC. YYYY will indicate the year. CC will indicate the posting cycle.

3.12.106.1.4  (01-01-2012)
Glossary of Abbreviations

  1. Abbreviations listed below are used to process gift and generation-skipping tax returns:

    Abbreviation Definition
    AIMS Audit Information Management System
    ADP Automatic Data Processing
    BMF Business Master File
    CAF Centralized Authorization File
    DLN Document Locator Number
    DSSN Donor's Social Security Number
    DOD Date of Death
    EIF Entity Index File
    EIN Employer Identification Number
    IDRS Integrated Data Retrieval System
    IRC Internal Revenue Code
    IRM Internal Revenue Manual
    ISRP Integrated Submission and Remittance Processing
    NAP National Accounts Profile
    POA Power of Attorney
    PSPC Philadelphia Submission Processing Center
    PSSN Primary Social Security Number
    SPC Submission Processing Center
    SSN Social Security Number
    SSSN Secondary Social Security Number
    TAS Taxpayer Advocate Service
    TIA Tax Information Authorization
    TIN Taxpayer Identification Number
    TPNC Taxpayer Notice Code
    TRS Transcript Research System

3.12.106.1.5  (01-01-2012)
Definitions

  1. Error Register—When the computer finds an error (consistency, math verification or validity) in the data input for a return, it generates an error register. It is a printed document which shows sections and fields corresponding to the information entered into the computer.

  2. Section—A portion of the return. Each section is numbered with a two-digit code beginning with 01.

  3. Field—An item in a section on the return, usually a line on the return.

  4. Alpha Field Designator—The first field of each section is designated the "A" field. Subsequent fields are designated "B" , "C" , "D" , etc.

  5. Field Breakers—A symbol that shows the end of a field. By itself, it means there was no data entered into that field.

    1. Sometimes, a "+" (plus) or "−" (minus) is used for the field breaker to show that an amount is positive or negative. If it is necessary to change a field from a positive to a negative, enter a pound sign (#) at the end of the amount to tell ISRP to input the amount as negative. To change a field from negative to positive, use a comma (,) to alert ISRP.

    2. A fixed length field does not have a field breaker. All spaces must be accounted for. When correcting a fixed length field, show the number of blanks to be used by writing and circling the number above the field.

  6. Document Locator Number—A Document Locator Number (DLN) is given to each document processed in the ADP System and is used to find the document. We distinguish between different types of returns by giving them specific tax classes and document codes.

3.12.106.1.6  (01-01-2012)
Action Code (AC)

  1. An action code tells the computer what to do next. Every correction made on the error register has a corresponding Action Code edited to the left of a particular section that needs to be corrected. Action Codes 0, 1, 3 and 7 may not be used at the same time as any other action code.

  2. Enter Action Codes (ACs) 0, 1, 2, 3 and 7 on the register to the left of Section 01. See Figure 3.12.106–1.

    Figure 3.12.106-1

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

    Editing Action Code 3 to the Left of Section 01 on the Register

  3. Enter Action Codes 4, 5, and 6 to the left of the appropriate section number. See Figure 3.12.106–2.

    Figure 3.12.106-2

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

    Editing Action Code 6 to the Left of Section 01 to Correct Field 01-E

3.12.106.1.6.1  (01-01-2012)
Action Code 0

  1. Action Code (AC) 0—Accept taxpayer's or examiner's figures.

    1. Use only when data on the register is correct.

    2. Use when computer's computation is to be disregarded because the taxpayer's or examiner's figures are correct.

3.12.106.1.6.2  (01-01-2012)
Action Code 1

  1. Action Code (AC) 1—Taxpayer math error above tolerance.

    1. Correct validity errors before using this code.

    2. Use when the data in a record has been transcribed correctly, but the taxpayer made an error on the return and the computer's tax computation should be accepted.

    3. Use a two-digit numeric code when a math error is present which affects the tax liability or settlement amounts. Enter this code to the right of AC 1, preceded by a dash (-). Use a maximum of three Taxpayer Notice Codes (TPNCs) per return. The codes are covered in the specific subsections of this Section for each return being processed. See IRM 3.12.106.3.1.13 for the list of TPNCs for Form 706-GS(D) and IRM 3.12.106.4.1.13 for Form 706-GSD(T). See Figure 3.12.106–3.

      Figure 3.12.106-3

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

      Literal "1-55" (Action Code 1 followed by a Dash and TPNC 55) Indicating Math Error Affecting Tax Liability of Settlement Amount

3.12.106.1.6.3  (01-01-2012)
Action Code 2 (Information Only)

  1. Action Code (AC) 2—Delete document from campus processing (Rejects Only).

    1. Used by Rejects to delete a record from campus processing.

    2. IMPORTANT: Action Code 2 is NOT used in the Form 706-GS(D) or Form 706-GS(T) correction programs.

3.12.106.1.6.4  (01-01-2012)
Action Code 3

  1. Action Code (AC) 3—Document is unprocessable.

    1. Use to transfer record from error register to reject register so Reject function can resolve the unprocessable condition.

    2. When AC 3 is used, attach Form 3696 (Correspondence Action Sheet) or Form 4227 (Intra–SC Reject or Routing Slip) to the return, noting the reason for the action taken.

3.12.106.1.6.5  (01-01-2012)
Action Code 4

  1. Action Code (AC) 4—Delete any section except section 01.

    1. Use to delete section from record on the register.

    2. Section 01 cannot be deleted.

    3. A generated missing section (present but no entries) cannot be deleted by using AC 4. See IRM 3.12.106.1.7.4.

3.12.106.1.6.6  (01-01-2012)
Action Code 5

  1. Action Code (AC) 5—Add sections other than 01.

    1. Use to add section to record on the register or to correct a section on the record that was computer generated.

    2. Enter alpha field designator followed by field data and field breaker for all significant fields.

    3. If field is insignificant (has no data), do not enter alpha field designator, field data, or field breaker.

3.12.106.1.6.7  (01-01-2012)
Action Code 6

  1. Action Code (AC) 6—Change field(s) in any section.

    1. Use to correct any field except remittance and TPNCs. Line out incorrect data and enter correct data above.

    2. Correct any number of fields during one correction cycle.

    3. When blanking or correcting a fixed length field, always enter the encircled number of positions (characters) prescribed for the field which does not contain significant data.

      Example:

      If the prescribed number of characters for the field is 7 and only 3 significant characters will be input, encircle 4 to show number of blanks. If the entire field will be blank, encircle 7.

3.12.106.1.6.8  (01-01-2012)
Action Code 7

  1. Action Code (AC) 7—No change required.

    1. Use to clear a record which has been sent to the register for one-time review.

    2. Use to clear a record which will be revalidated as it currently exists.

3.12.106.1.7  (01-01-2012)
Error Correction Rules

  1. Error Resolution tax examiners make corrections on the returns and registers. Make certain all entries are legible.

  2. Returns Secured or Prepared by Examination Division. To audit a taxpayer who has not filed an original return, Examination Division occasionally prepares returns or secures an unsigned copy from the taxpayer. The return is submitted for computer processing as an original. It will precede an AIMS adjustment to the BMF. It is marked SUBSTITUTE or COPY SECURED BY EXAMINATION DIVISION and may have audit papers attached. Forms you may see attached are: Forms 3198, 6459, 5255, and 3232 or 3233.

    1. If there is a math error and taxpayer correspondence is required, AC 3 to Rejects for unprocessable conditions. Rejects will void the document from the system and send it to Examination Division for further processing.

    2. DO NOT correspond with the taxpayer or executor for clarification or additional information.

3.12.106.1.8  (01-01-2012)
Validity Errors

  1. There are three general types of errors that will cause a record to print on the error register:

    • Field Validity Error

    • Section Validity Error

    • Math Error

3.12.106.1.8.1  (01-01-2012)
Integrated Submission and Remittance Processing (ISRP) Error

  1. The Error Indicator prints to the left of the section number and appears on the register as follows:

    1. "#1" —Split screen transmission. Key Verifier attempted to change the check digit or four or more digits in the TIN or Original Entry Operator entered required section as "missing" .

    2. "#3" —Invalid Section ending point.

    3. "#4" —Invalid field length (e.g., too many digits entered for field).

    4. "#5" —Operator inputs the same section more than once. Computer program drops all duplicate sections and displays on the error register the first section encountered. See Figure 3.12.106–4.

    Figure 3.12.106-4

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

    ISRP Error

  2. To correct this error, perform the following steps:

    1. Compare the return data with the register fields.

    2. Line out each incorrect field and enter the correct data immediately above the lined out data.

    3. Enter Action Code (AC) 6.

  3. If no error is found, use Action Code (AC) 7 to clear the register.

3.12.106.1.8.2  (01-01-2012)
Extraneous Section

  1. A pound sign (#) indicator prints to the left of the section number if unnecessary section appears.

  2. To fix this error, delete section using AC 4.

3.12.106.1.8.3  (01-01-2012)
Terminus Error

  1. Double asterisk (**) indicator prints to the left of the section number if alpha data is entered in numeric field or vice versa.

  2. To correct this error:

    1. Look at all fields of the section.

    2. Line out each incorrect field and enter the correct data immediately above the lined out data.

    3. Enter AC 6. See Figure 3.12.106–5.

      Figure 3.12.106-5

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

      Terminus Error

3.12.106.1.8.4  (01-01-2012)
Missing Section

  1. An asterisk (*) indicator prints to the left of the section number when a required section was not transcribed.

  2. To correct this error:

    1. Enter the necessary information.

    2. Enter AC 6. See Figure 3.12.106–6.

      Figure 3.12.106-6

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

      Missing Section

    3. A generated missing section (present with no entries) cannot be deleted by using AC 4. If no corrections to the register are necessary, use Action Code 7 to clear it.

3.12.106.1.9  (01-01-2012)
Re-entry Documents

  1. This sub-section defines re-entry documents and provides instructions for their control and processing.

3.12.106.1.9.1  (01-01-2012)
Definitions of Re-entry Documents

  1. The following definitions describe re-entry documents:

    1. A document unprocessable after blocking and numbering, but which becomes processable after making corrections or additions.

      Note:

      A document discovered to be unprocessable before it was blocked and numbered but will not be considered to be a re-entry document when it is input after correction.

    2. Document did not post to Master File on input, but now is processable if re-entered.

    3. Document posted to wrong account or module on input and will post to correct account or module if re-entered.

3.12.106.1.9.2  (01-01-2012)
Identification of Re-entry Documents

  1. Re-entry documents can be identified by the presence of Computer Condition Code "U" , and/or Form 4227 on the document when it is received in Document Perfection/Correction, or by the presence of a Re-entry Document Control Slip, Form 3893. CCC "U" coded PSPC documents are routed to the Philadelphia Submission Processing Campus. Since June 2007, documents processed previously at PSPC are processed at the Cincinnati Submission Processing Campus (CSPC).

3.12.106.1.9.3  (01-01-2012)
Processing of Re-entry Documents

  1. If a re-entry return is unprocessable, use Action Code (AC) 3 and route to the originating area on Form 4227 following local campus (Submission Processing Center) procedures. See IRM 3.11.106.5.8 for unprocessable conditions.

3.12.106.1.10  (01-01-2012)
Correction of Invalid Correction Attempt

  1. Code "AA" will print to the right of the batch number on the loop register when the computer indicates an invalid correction attempt.

    1. Correct register as if no attempt has been made to correct it before. You should examine the prior correction.

    2. If all fields are correct as transcribed, use AC 7.

3.12.106.1.11  (01-01-2012)
♦Statute Control♦

  1. A statute control document is a document filed for a barred period. A barred period is a taxable period on which statutory limitations are placed for allowing refunds, credits, or for assessing additional taxes. Generally, a claim for refund must be filed or additional tax assessments must be made not later than three years from the date the original return was filed or two years from the date the tax was paid.

  2. Treat all statute control documents as unprocessable.

    1. Reject documents by using Action Code (AC) 3.

    2. Prepare Form 4227 and route return to Statute Control Group. See Figure 3.12.106–7.

    Figure 3.12.106-7

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

    Reject Return with Action Code 3 on Register and Prepare Form 4227 to Forward Return to Statute Control

  3. Enter Computer Condition Code (CCC) "W" if the return is stamped "Cleared by Statute" , so checks will not be made on returns already cleared.

  4. If it appears that a rejected document will not reach the Statute Control Unit in time for clearance, photocopy page one of the return, stamp photocopy "Photocopy—Do Not Process" , and expedite, forwarding to the Statute Control Unit using local procedures.

  5. If the document was received timely, and the return is being processed within 34 months of the due date of the original return, delete CCC "W" whether or not Statute Control has cleared the document.

3.12.106.1.11.1  (01-01-2012)
♦Non "G" Coded Returns♦

  1. If there is a return that has not cleared the Statute Control Unit with a current processing date that is two years and nine months or more after the later of the original due date or the received date, reject the return, using AC 3. Prepare Form 4227 and route the return to the Statute Control Group.

  2. The tax period (Field 01–E) will asterisk for Statute. Check if the processing date is two years and nine months after the Return Due Date or Received Date, whichever is later, and CCC "W" is not present.

3.12.106.1.11.2  (01-01-2012)
CCC "G" Coded Returns

  1. If there is a return that has not cleared the Statute Control Unit with a current processing date that is two years and nine months or more after the later of the original due date or the received date, reject the return, using AC 3. Prepare Form 4227 and route the return to the Statute Control Group.

  2. On both non-CCC "G" and CCC "G" coded returns, both the tax period (Field 01-E) and CCC field (Field 01-F) will asterisk if the processing date is less than two years after the Return Due Date and a CCC "W" is present.

3.12.106.1.11.3  (01-01-2012)
Returns Secured or Prepared by Examination Division

  1. Examination Division may prepare dummy returns or secure unsigned copies from taxpayers to use as a source document to complete an examination case. The return is submitted for computer processing as an original. It will precede an AIMS adjustment to the BMF. It is marked "SUBSTITUTE OR COPY SECURED BY EXAMINATION DIVISION" and may have audit papers attached. Forms you may see attached are: Forms 3198, 6459, 5255 (pages 1, 2, 3, and 4), and 3232 or 3233. DO NOT correspond with taxpayer or executor for clarification or additional information. Send to Examination for further instructions. If Statute Control Date has expired, do not send to Statute Control Unit. Enter CCC "W" .

3.12.106.1.12  (01-01-2012)
Accounts Receivable Guidelines

  1. To keep the amount owed the IRS down, we must minimize the number of unresolved large dollar debit and credit modules/issues in inventory. Therefore, consistent with prevailing guidelines and other processing timeliness requirements (i.e. first-in, first-out), resolve all modules/issues with balances of $25,000 or more ASAP.

  2. Each region annually identifies complex Business Master File (BMF) entities such as large dollar accounts, federal agencies, or entities which have a history of complex issues. A "Large Complex Corporation" indicator will be set on BMF to alert the Submission Processing Centers when a notice has been generated on these accounts. This replaces the previous "L" Coded Corporate Processing activity.

  3. A "Large Corp CD" indicator will appear on IDRS, and all applicable Master File transcripts, under ENMOD and TXMOD. The CD field will be overlaid by the campus (Submission Processing Center) location code (i.e., LARGE CORP 17). These notices will be routed to the Technical Unit (or designated function) for review before being sent to the taxpayer. When this indicator is identified, employees should coordinate their case with the Technical Unit (or designated function) prior to taking action. IRM 1.10.1, The Internal Revenue Service Correspondence Manual, has procedures for the research and resolution of "Large Complex Corporation" cases.

  4. The Service is also monitoring large dollar cases identified on the Accounts Receivable "Large Dollar Trend Record" (LDTR) report. Cases listed on the LDTR report may include the Large Complex Corporation code, so the region may contact the Technical Unit (or designated function) to determine the current status of the account/module.

3.12.106.1.13  (01-01-2012)
Individual Master File On-Line and Return View

  1. You can research Master File accounts and return data with Individual Master File On-Line (IMFOL) and Return View (RTVUE).

  2. Since Master File does not carry all information available on the IDRS screen displays (IDRS notice status, case control information, pending transactions, etc.), you must research IDRS before IMFOL or RTVUE. Also, if you cannot use IMFOL or RTVUE, then use IDRS input command codes that will cause a change to Master File.

  3. Use these command codes to research entity and/or tax data which may not be available on IDRS. Since you will usually get a response in five seconds or less, you may want to use these command codes rather than make MFTRA/ESTAB requests.

  4. IMFOL provides screen displays from IMF data based on an input definer code. For more information on screen displays and applicable definer codes, see IRM 2.3, IDRS Terminal Responses, and the 2545 training series.

  5. RTVUE gets data from the Return Transaction File (RTF). It will give you all edited, transcribed, and error corrected data from data entry lines of Form 1040 series returns and related forms and schedules filed in the current processing year (PY) including late filed returns and two prior years. RTVUE needs a definer to get a particular screen and has a summary screen for each return.

3.12.106.1.13.1  (01-01-2012)
CFOL (Corporate Files On-Line) Command Codes

  1. IRPTR (Information Returns Program Transcript File On Line)—provides two payee addresses if present, filing status, one payer name and address, cross reference information, and a summary of up to 36 IRP (Information Returns Program) money amounts by income type.

  2. RTVUE (Return View)—provides on-line access to the Return Transaction File. The file consists of original input return data, including schedules. This return information contains Code and Edit, Error Resolution System (ERS), and computer-generated fields.

  3. IMFOL (Individual Master File On-Line)—provides nationwide IMF entity and tax data information on-line for tax accounts that are in credit or debit status, contain freeze conditions or open IDRS control bases. It also displays a list of accounts moved to the retention register. Other accounts that are not on the retention register will be available on-line within 24 hours upon request. This command code was previously announced as CC MFVUE.

  4. BRTVU (Business Return View)—provides business return transaction information. The file consists of original input return data, including schedules. This return information includes Code and Edit, Error Resolution (ERS), and computer-generated fields.

  5. BMFOL (Business Master File On-Line)—provides nationwide Business Master File (BMF) entity and tax data information on-line for tax accounts that are in credit or debit status, contain freeze conditions or open IDRS control bases. It also displays a list of accounts moved to the retention register. Other accounts that are not on the retention register will be available on-line within 24 hours upon request. This command code was previously announced as CC MFVUE.

  6. Use NAMEI/NAMEB to research for missing or invalid SSNs (IMF) or EINs (BMF). NAMEI replaced SSNAD. NAMEB is used for missing or invalid business names and address, and replaced EINAD.

  7. PMFOL (Payer Master File On-Line)—is a research tool which provides information from the Payer Master File (PMF). The summary screen displays all dollar amounts, withholding of income tax, number of documents filed by payer and by document type (i.e. 1099 series). It contains the Annual Summary and Transmittal of information returns (Form 1096) filed, and the civil penalties associated with each document type. CC PMFOL provides access to W–3 data (unpostable data only) beginning with tax year 1990 submissions.

3.12.106.1.14  (01-01-2012)
Forms List

  1. Forms listed below are used or referred to in estate, gift, and generation-skipping tax return processing:

    Form Title
    56 Notice Concerning Fiduciary Relationship
    706-GS(T) Generation-Skipping Transfer Tax Return for Termination
    706-GS(D) Generation-Skipping Transfer Tax Return for Distribution
    706-GS(D–1) Notification of Distribution from a Generation-Skipping Trust
    706QDT Qualified Domestic Trust
    712 Life Insurance Statement
    813 Document Register
    843 Claim for a Refund and Request for Abatement
    1310 Statement of Person Claiming a Refund Due a Deceased Taxpayer
    1332 Block and Selection Record
    2350 Application for Extension of Time to File U.S. Income Tax Return
    2758 Application for Extension of Time to File Certain Excise, Income, Information and Other Returns
    2848 Power of Attorney and Declaration of Representative
    3465 Adjustment Request
    3696 Correspondence Action Sheet
    3696A IDRS Correspondence Action Sheet
    3753 Manual Refund Posting Voucher
    3893 Re-Entry Document Control
    4227 Intra-SC Reject or Routing Slip
    4868 Application for Automatic Extension of Time to File U.S. Individual Tax Return
    5495 Request for Discharge from Personal Liability under IRC Section 6905
    5792 Request for IDRS Generated Refund
    6800 Request for Missing Information or Papers to Complete Return
    6882 IDRS/Masterfile Information Request
    8821 Tax Information Authorization

3.12.106.1.15  (01-01-2012)
♦BMF Consistency♦

  1. The purpose of this initiative is to achieve consistency in the Business Master File (BMF) Error Resolution System (ERS) processing IRMs.

  2. Topics for the BMF Consistency have been identified and developed as a coordinated effort between Cincinnati, Ogden and Paper Processing Branch BMF Code & Edit/ERS Section.

  3. BMF Consistency subsections are identified by a ♦ (diamond) before and after the title.

  4. Text in normal print is the common processes for BMF returns. The text in BOLD print is form specific and applies to this IRM only.

3.12.106.2  (01-01-2012)
♦Taxpayer Advocate Service - Service Level Agreement♦

  1. The National Taxpayer Advocate and the Commissioner, Wage and Investment (W&I) Division have reached an agreement (effective February 1, 2008) outlining the procedures and responsibilities for processing Taxpayer Advocate Service (TAS) casework when either the statutory or delegated authority to complete a case transaction rests with the W & I Division. The agreement is known as a Service Level Agreement (SLA).

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

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

    2. Securing all necessary supporting documentation.

    3. Identifying cases that require expedite processing. No case will automatically receive expedite processing; requests for expedite processing will be made on a case-by-case basis.

    4. Forwarding Form 12412 and documentation with Form 3210, Document Transmittal, to the Wage and Investment Division Liaison.

  3. W&I is responsible for:

    1. Assigning a liaison in each local office or Campus where a Local Taxpayer Advocate (LTA) is located.

    2. Acknowledging receipt of the case via Form 3210 within one (1) workday for cases requesting expedite processing or within three (3) workdays for non-expedite cases.

    3. Responding to TAS within three (3) workdays in writing, via facsimile, secure messaging email, or hand delivery of resolution.

    4. Providing TAS with the name and telephone number of the W&I employee assigned the case.

    5. Negotiating with TAS a reasonable timeframe for resolution.

    6. Upon closing of the OAR, the W&I employee assigned the OAR will complete Section VI of Form 12412, Operations Assistance Request, and return it to the TAS employee assigned the case. The Form 12412 must be returned within three (3) workdays from the date that all actions have been completed and transactions input.

  4. For further information, refer to the W&I SLA online at http://tas.web.irs.gov/ under the heading "Policy/Procedures/Guidance" .

3.12.106.2.1  (01-01-2012)
Form 911, Request for Taxpayer Advocate Service Assistance (and Application for Taxpayer Assistance Order)

  1. 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. TAS criteria include economic burden, system burden, best interest of the taxpayer, and public policy (as determined solely by the National Taxpayer Advocate (NTA). TAS is responsible for assisting taxpayers who have unresolved problems with the IRS. See IRM 13.1.7, Taxpayer Advocate Service (TAS) Case Criteria, if additional information is required.

  2. Employees should not view TAS Case Criteria as a means of excluding taxpayers from TAS, but rather, as a guide to TAS case acceptance. The criteria under which TAS accepts a case should not govern whether a taxpayer is entitled to relief.

  3. If the IRS employee can resolve a taxpayer's inquiry or provide the relief requested, as outlined in IRM 13.1.7.4, Same Day Resolution by Operations , a referral to a TAS office is not necessary even if TAS case criteria are met. The definition of same day resolution is "within 24 hours." However, cases where the employee cannot completely resolve the issue within 24 hours, but has taken steps within 24 hours to resolve the taxpayer's issue, also meet the definition of same day. Do not refer these cases to TAS unless they meet TAS criteria and the taxpayer asks to be transferred to TAS.

    Note:

    It is important that all IRS employees handle potential TAS cases with the taxpayer's best interest in mind. Refer also to IRM 21.1.3.18, Taxpayer Advocate Service (TAS) Guidelines , for more information. Provide the taxpayer with the number for the NTA toll-free case intake line, 1-877-777-4778 or TTY/TDD 1-800-829-4059. The taxpayer should be advised that TAS is available if the taxpayer is not satisfied with the service he or she received.

  4. An IRS employee should make a referral to a TAS office if the employee receives a taxpayer contact, it meets TAS criteria, and cannot initiate action to resolve the inquiry or provide the relief requested. A taxpayer does not have to specifically request TAS assistance to be referred to TAS. IRS employees will advise taxpayers of the option to seek TAS assistance when appropriate. TAS will request documentation from the taxpayer if it is needed to support the requested relief, or required by the IRM.

  5. The following types of cases should NOT be referred to TAS:

    • Cases were the taxpayer's complaint or inquiry only questions the constitutionality of the tax system, or

    • Cases where the focus of the taxpayer's inquiry is solely to employ frivolous tax strategies to avoid or delay filing or paying federal taxes.

  6. TAS Case Acceptance Criteria:

    • The taxpayer is experiencing economic harm or is about to suffer economic harm.

    • The taxpayer is facing an immediate threat of adverse action.

    • The taxpayer will incur significant costs if relief is not granted (including fees for professional representation).

    • The taxpayer will suffer irreparable injury or long-term adverse impact if relief is not granted.

    • The taxpayer has experienced a delay of more than 30 days to resolve a tax account problem.

    • The taxpayer has not received a response or resolution to the problem or inquiry by the date promised.

    • A system or procedure has either failed to operate as intended, or failed to resolve the taxpayer’s problem or dispute within the IRS.

    • The manner in which the tax laws are being administered raise considerations of equity, or have impaired or will impair the taxpayer’s rights.

    • The NTA determines compelling public policy warrants assistance to an individual or group of taxpayers.

      Note:

      Case criteria are not meant to be all-inclusive; each taxpayer's situation should be evaluated based on the unique facts and circumstances of each case.

3.12.106.2.2  (01-01-2012)
Section 3705(a), IRS Employee Contacts

  1. This sub-section provides guidelines for employees to following when communicating with taxpayers and/or their representation on tax-related matters.

3.12.106.2.2.1  (01-01-2012)
Background

  1. The Restructuring and Reform Act of 1998, Section 3705, provides identification requirements for all IRS employees working tax-related matters.

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

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

    Caution:

    Before disclosing any tax information, you must be sure you are speaking with the taxpayer or authorized representative. See the Taxpayer Authentication guidelines in IRM 21.1.3 (Operational Guidelines Overview). Also, before leaving any messages on a taxpayer's answering machine, review IRM 11.3.2.6.1 (Disclosure of Persons with a Material Interest). Fax procedures contained in IRM 11.3.1.11 (Introduction to Disclosure) must be reviewed prior to faxing confidential information to the taxpayer.

3.12.106.2.2.2  (01-01-2012)
Key Points

  1. The Restructuring and Reform Act of 1998, Section 3705, provides identification requirements for all IRM 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 provides taxpayers with enough information to identify an IRS employee who has previously assisted with tax related matters.

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

    • Telephone Contact:Their title (e.g., Mr., Mrs., Ms., Miss), their last name, and their badge identification (ID Card) number.

    • Face to Face Contact:Their title (e.g., Mr., Mrs., Ms., Miss), their last name, and their ID (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 their title (e.g., Mr., Mrs., Ms., Miss), their last name, and their IDRS, letter system, or ID Card (badge) number.

  3. The IDRS number and numbers for some other letter systems are automatically generated. If it is not generated, or a handwritten note is prepared, the ID Card (badge) number must be used.

  4. Toll-Free employees may also provide their location for identification purposes. E-mail and facsimiles to taxpayers on tax-related matters are considered manually-generated correspondence and must include the required information.

    Caution:

    Email cannot be used to transmit taxpayer account information.

  5. Correspondence, whether sent directly to the taxpayer or to the taxpayer's representative, must contain the required information.

  6. When a taxpayer insists on speaking with a specific employee who previously handled their 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.

  7. 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 the taxpayer may have about the correspondence, or the employee is asking the taxpayer to provide additional case-related information.

  8. Otherwise, if the taxpayer does not need to contact a specific employee, the correspondence needs only an IRS telephone number and standard signature.

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

  10. 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 telephone or in-person) their ID Card (badge) number on the first contact.

  11. If you can not resolve the taxpayer's issue the same day, see also IRM 3.12.106.2.1 to determine if a referral to the Taxpayer Advocate Service (TAS) is appropriate.

3.12.106.3  (01-01-2012)
Processing Form 706-GS(D)

  1. This sub-section includes instructions for correcting Sections 01 through 03 of Form 706-GS(D).

    Note:

    When the Schedule D–1 is entered as a Form 706-GS(D), the document must be deleted and be associated with the 706-GS(D). Reject with Action Code 3 for deletion.

  2. Please note that two (2) revisions of the Form 706-GS(D) were issued in Calendar Year 2011:

    1. Form 706-GS(D), Generation Skipping Transfer Tax Return For 2010 Distributions (Rev. February 2011);

    2. Form 706-GS(D), Generation Skipping Transfer Tax Return For Distributions (Use for Distributions made after December 31, 2010; For Calendar Year ......... (Rev. November 2011).

3.12.106.3.1  (01-01-2012)
Section 01—Form 706-GS(D)

  1. Section 01 alpha designators, field lengths and titles are listed below. Section 01 are fixed length fields.

    Alpha
    Designator
    Line
    Numbers
    Field
    Lengths


    Title
    A Right margin of Line 12 11 Remittance Amount
           
    B Line 1a 4 Name Control
    Name Control Underprint
           
    C Line 1b or 1c 9 TIN
           
    D Right margin of Line b 1 TIN Type
           
    E Top of the return 6 Tax Period
           
    F Dotted portion of Line 6 tax computation area 8 Received Date
           
    G Upper left of the return 10 Computer Condition Code
           
    H Left OMB number on upper portion of return 1 Penalty and Interest Code
           
    I Right margin of line 2b 1 CAF Indicator
           
    J Left margin of Line 6 8 Correspondence Received Date
           
    K   1 Entity Underprint Code
           
    L Upper left margin of return 6 Taxpayer Notice Code
           
    M Refund Code 1 1 Refund Code
           
    N Bottom Portion of Part III (Tax Computation) -"Paid Preparer's Use Only" Box (to the right of preparer's signature) 9 Preparer's SSN or PTIN
           
    O Bottom Portion of Part III (Tax Computation) -"Paid Preparer's Use Only" Box (to the right of preparer firm's name and address) 9 Preparer's EIN
           
    P Bottom Portion of Part III (Tax Computation) -"Paid Preparer's Use Only" Box (to the right of preparer firm's name and address) 10 Preparer's (Telephone) Number

3.12.106.3.1.1  (01-01-2012)
Due Date

  1. Forms 706-GS(D) are due on the fifteenth day of the fourth month (April 15th) following the calendar year when the distributions were made.

    Note:

    In Calendar Year 2012, the due date is April 17 because April 15 falls on Sunday and April 16 is the legal Emancipation Day holiday in the District of Columbia (even if the taxpayer does not live in the District of Columbia). The due date of the return is the next business day following a weekend or legal holiday.

3.12.106.3.1.2  (01-01-2012)
Field 01–A—Remittance Amount

  1. You cannot change this field. If the amount is incorrect, treat the return and related error record as unprocessable. Reject with Action Code 3 and prepare Form 4227 to explain the error. The Reject function will prepare Form 3893 for re-entry.

  2. The Remittance Amount is located on the Balance Due line of a full paid return and is designated by a green rocker.

  3. If a remittance amount is shown on an apparent nontaxable return, but an examination reveals that it should be taxable, enter the missing data in the appropriate fields and sections of the register and enter Action Code 6.

  4. Field 01–A will asterisk if an amount is present in Field 01–A and there is no entry in Net GST Tax, (Field 03–H) or Net GST Tax Computer. If the return is a true nontaxable, (i.e., taxpayer shows "none" , "not liable" , tax is zero due to a math error, or just signs the return) and no other non-math errors are involved, treat return as "unprocessable" . Bring up the underprint for Field 03–H. Reject with Action Code 3. Indicate excess remittance on Form 4227. If nontax status is due to a math error, note on Form 4227, "Zero tax due to math error. Refund if no other tax due" .

3.12.106.3.1.3  (01-01-2012)
Field 01–B—Name Control

  1. This field cannot be blank. Must be the first four alpha characters of the last name in line 1a (Name Control of the Trust). First position must be alpha. Valid characters after the first position may be alpha, hyphen or blank. The name control is invalid if there are intervening blanks between significant characters.

  2. Check for transcription errors in the Name Control Field.

    1. If the Name Control on the return and Field 01–B do not agree or was transcribed incorrectly, change Field 01–B.

    2. If it is not an obvious error, research through INOLE/ENMOD for the SSN/EIN and NAMEI/NAMEB for the name line.

    3. If the correction entry is less than four characters, enter and circle the number of the remaining positions.

    4. Check Field 01–D (TIN Type) to ensure the correct TIN type was entered. Correct the field if necessary.


More Internal Revenue Manual