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

3.5.61  Files Management and Services (Cont. 1)

3.5.61.3 
Receiving And Preparing Other Documents For Filing

3.5.61.3.25  (01-01-2010)
Form 8329, Lender's Information for Mortgage Credit Certificates (MCCs)

  1. Form(s) 8329 are processed at the Ogden Submission Processing Center.

  2. File Form(s) 8329 in TIN (Reporting Authority) order by calendar year.

3.5.61.3.26  (01-01-2010)
Form 8332, Release/Revocation of Claim to Exemption for Child by Custodial Parent.

  1. Form(s) 8332 are required to be attached to the taxpayer's return.

  2. Route loose Form(s) 8332 (paper and electronically filed) to the Accounts Management Function for adjustment input that will provide for association of the form.

3.5.61.3.27  (01-01-2010)
Form 8621, Return by a Shareholder of a Passive Foreign Investment Company or Qualified Electing Fund (OSPC)

  1. If received, route to the Ogden Submission Processing Center.

  2. File loose Form(s) 8621 in alphabetical order by year of receipt.

3.5.61.3.28  (01-01-2010)
Form 8703, Annual Certification of a Residential Rental Project

  1. Form(s) 8703 are processed at the Ogden Submission Processing Center.

  2. File Form(s) 8703 in TIN (owner of project) order by calendar year.

3.5.61.3.29  (01-01-2010)
Form 8833, Treaty-Based Position Disclosure Under Section 6114 or 7701(b)

  1. Retain loose Form(s) 8833 in alphabetical order by year of receipt.

  2. Retire to the Federal Records Center beginning January 2 through March 31 following the year in which returns were numbered and processed.

  3. Destroy on or after January 16, six (6) years after the end of the processing year unless needed for the Collection Statute Expiration Date (CSED) Extract.

3.5.61.3.30  (01-01-2010)
Form 8840, Closer Connection Exception Statement for Aliens (AUSPC Only)

  1. Loose Form(s) 8840 are processed at the Austin Submission Processing Center.

  2. File and maintain loose Form(s) 8840 in alphabetical order by year of receipt.

  3. Retire to the Federal Records Center beginning January 2nd through March 31st following the year in which returns were numbered and processed.

  4. Destroy on or after January 16, six (6) years after the end of the processing year unless needed for the Collection Statute Expiration Date (CSED) Extract.

  5. For loose Form(s) 8840 that cannot be filed alphabetically due to insufficient information (e.g. information is illegible, missing, blank, etc.), designate a storage area/box with the notation "Form 8840 - Unidentified or Unable to Associate" and file by year of receipt.

  6. At the end of the calendar year, collect all the unidentified/unable to associate loose Form(s) 8840

  7. Retain the documents for one (1) year (in the event a future association can be made) and then destroy.

3.5.61.3.31  (01-01-2010)
Form 8843, Statement for Exempt Individuals and Individuals with a Medical Condition (For Use by Alien Individuals Only) (AUSPC Only)

  1. Loose Form(s) 8843 are processed at the Austin Submission Processing Center.

  2. File loose Form(s) 8843 in alphabetical order by year of receipt.

  3. Retire to the Federal Records Center beginning January 2 through March 31 following the year in which returns were numbered and processed.

  4. Destroy on or after January 16, six (6) years after the end of the processing year unless needed for the Collection Statute Expiration Date (CSED) Extract.

  5. For loose Form(s) 8843 that cannot be filed alphabetically due to insufficient information (e.g. information is illegible, missing, blank, etc.), designate a storage area/box with the notation "Form 8843 - Unidentified or Unable to Associate" and file by year of receipt.

  6. At the end of the calendar year, collect all the unidentified/unable to associate loose Form(s) 8843.

  7. Retain the documents for one (1) year (in the event a future association can be made) and then destroy.

3.5.61.3.32  (01-01-2010)
Form 8855, Election to Treat a Qualified Revocable Trust as Part of an Estate

  1. Form(s) 8855 are processed at the Cincinnati and Ogden Submission Processing Campuses.

  2. File and maintain in EIN order by year of receipt.

  3. Associate Form 8855 with Form 1041, U.S. Income Tax Return for Estates & Trusts. If Form 1041 is not present, associate with Form 706, United States Estate (and Generation-Skipping Transfer) Tax Return.

  4. Form(s) 706 are stored at the Consolidated Site (C-Site) which is a storage facility near the Kansas City Submission Processing Campus (KCSPC).

  5. The C-Site address is : Internal Revenue Service, 335 S. GeoSpace Drive, Independence, Missouri 64056.

3.5.61.3.33  (01-01-2010)
Form 8857, Request for Innocent Spouse Relief

  1. If received, route Form(s) 8857 to the Cincinnati Submission Processing Campus (CSPC).

3.5.61.3.34  (01-01-2010)
Form 8865, Return of U.S. Persons With Respect to Certain Foreign Partnerships

  1. Route loose Form(s) 8865 to the Accounts Management Function for association with the taxpayer's tax return.

3.5.61.3.35  (01-01-2010)
Form 8868, Application for Extension of Time to File an Exempt Organization Return (OSPC Only)

  1. File and maintain in EIN order by year of receipt at the Ogden Submission Processing Center.

3.5.61.3.36  (01-01-2010)
Form 8871, Political Organization Notice of Section 527 Status, Form 8872, Political Organization Report of Contributions and Expenditures and Form 8453X, Political Organization Declaration for Electronic Filing of Notice 527 Status (OSPC Only)

  1. Form 8453X is the jurat form for electronically filed Forms 8871. Generated Form(s) 5147 will have a DLN beginning with "91977" . Associate Form(s) 8453X with these Form(s) 5147.

3.5.61.3.37  (01-01-2010)
Form 8918, Material Advisor Disclosure Statement (OSPC only)

  1. File in reportable transaction number order if the reportable transaction number is present.

  2. File in alphabetical order if the reportable transaction number is not present (application denied).

  3. Form 8918 replaces Form 8264, Application for Registration of Tax Shelter.

3.5.61.3.38  (01-01-2010)
Form 8925, Report of Employer-Owned Life Insurance Contracts

  1. Form(s) 8925 is required to be attached to the policyholder's return for each year.

  2. Route loose Form(s) 8925 to the Account Management Function for adjustment input that will provide for association of the form(s).

3.5.61.3.39  (01-01-2010)
Form SS-4, Application for Employer Identification Number

  1. Form(s) SS-4 received from the Accounts Management (EIN Function) and Entity Function will have this information shown on the outside of the folder:

    • Julian Date or Calendar Date and Year

    • Employee Number

  2. File forms by employee number sequence by date.

  3. Retire to the Federal Records Center at the end of June and at the end of December those forms and related documents over six (6) months retention.

  4. Destroy five (5) years after the end of the year in which processed.

3.5.61.3.40  (01-01-2010)
Schedule K-1 (CSC & OSC only)

  1. Schedule(s) K-1 is no longer re-associated with the parent return (Form(s) 1041, 1065, or 1120s).

  2. Schedule(s) K-1 will be received on batch carts or "stat " boxes in individual gusset/blue folders in parent DLN order.

  3. The parent return DLN will be written/stamped on the individual gusset/blue folder for each set of Schedule K-1.

  4. Retain Schedule(s) K-1 under the parent return DLN.

  5. Pull/retrieve Schedule(s) K-1 whenever a request for the parent return indicates they are needed.

  6. Retain Schedule(s) K-1 with the parent return once they have been pulled and associated.

  7. Return to the originator those schedule(s) K-1 received for association with an electronically filed parent return as there is nothing in Files with which to associate the schedule(s).

3.5.61.3.41  (01-01-2010)
Oversize Administrative Files

  1. Each Submission Processing Files Function has a different capacity for storage. The major concern is the accountability of all paper under documents under DLN control whether it be at the Campus or retired to a Federal Records Center.

  2. In those instances where a taxpayer's file contains excessive documents (schedules, audit reports, etc), which precludes filing in the normal block of documents, determine/devise a consistency filing system for all oversize administrative files based on local space availability.

    Note:

    Consider an Administrative File containing documents of 4 inches or more as overly large.

  3. Stamp the upper right hand portion of the return "Administrative File" being careful to avoid stamping over any other information.

  4. Write this information on the front of any cartons/folders prepared for storage:

    • DLN

    • Taxpayer's Name

    • Taxpayer's TIN

    • Tax Period

  5. Update all administrative files to show the new controlling DLN for the taxpayer when a return is renumbered.

  6. Process/fill requests for returns having administrative files with the complete file.

3.5.61.3.42  (01-01-2010)
Citizenship Status Statements (OSPC only)

  1. Citizenship Status Statements from the Correspondence Function consists of these categories:

    • Citizen

    • Section 911

    • Other

  2. File these statements within category, by year as received for retirement as outlined in IRM 1.15.29, Records Control Schedule for Submission Processing Campus Records.

3.5.61.3.43  (01-01-2010)
Foreign Investment in Real Property Tax Act (FIRPTA) Correspondence (OSPC only)

  1. File and maintain FIRPTA correspondence in alphabetical order by year of receipt.

  2. If the taxpayer name/identifying information is not readily identifiable on the correspondence, route to the Accounts Management Function for a determination as to the taxpayer name, etc.

3.5.61.3.44  (01-01-2010)
United Mine Workers of America Benefit Claims

  1. File claims in alphabetical order by year of receipt.

3.5.61.3.45  (01-01-2010)
Unidentified Remittance and Excess Collection Paper Files

  1. Annotate folders with this information:

    • Date

    • Employee Number

    • Type of Input

  2. File folders by date, then employee number sequence by type of input.

  3. Service requests for these documents by following instructions for IDRS source document requests.

  4. These folders should not be considered as IDRS source document folders as they have a separate and unique retention period.

  5. For retention and destruction information, see IRM 1.15.29, Records Control Schedule for Submission Processing Campus Records, Item 158

3.5.61.3.46  (01-01-2010)
SCRIPS Processed Forms 940 and 941

  1. Form(s) 940 (2006 and later) and Forms 941 (2005 and later) processed via SCRIPS will not be stapled together.

  2. Forms 940 (2006 and later) and Forms 941 (2005 and later) processed via SCRIPS may have a folder within the gusset folder that contains the return attachments. Both the return and attachments will have a unique number stamped in the upper left margin of the return and on the top of the attachment(s).

  3. When a request for a return is received, look for the folder within the gusset folder. If found, search the interior folder for all pages associated with the return. Staple the return together (with attachment when appropriate) and send to the requester.

  4. When documents (returns and attachments) are received for re-filing, they will be stapled and should be re-filed together. Do not separate the attachments(s) from the return and re-file separately.

3.5.61.3.47  (01-01-2010)
Lockbox Processed Documents

  1. Lockbox processed forms are sent to the Files Function after all transactions in the block have gone to good tape (i.e. cleared Error Resolution System).

  2. Check received documents against the CPL/ACPL as appropriate.

  3. Perform a cursory review of audit trail legibility that is printed on the back of the form. This assists in identifying any checks that may have been left in the block.

  4. Associate the Optical Character Recognition (OCR) Remittance Register or Form 813, Part 2, Document Register, with the documents prior to shelving.

  5. When filing request for blocks of documents, include the document lister tape with the block.

  6. Form 4868/4868V, Application for Automatic Extension of Time to File U.S. Individual Income Tax Return, is processed through Lockbox. Form 4868V is the tear-off bottom portion of the form and is numbered by Lockbox.

  7. Form 4868V (top portion of the form) is placed in the back of the folder in the order of input.

  8. Form 4868V is numbered using the FLC and shows a Tax Class/Document Code of "217" .

  9. Service these requests by pulling the numbered Form 4868V only.

  10. Report any unusual problems to the Submission Processing Center Lockbox Coordinator.

3.5.61.3.48  (01-01-2010)
Integrated Submission and Remittance Processing System (ISRP)

  1. ISRP replaces the Remittance Processing System (RPS) for entering data from tax returns and processing remittances.

  2. ISRP documents along with Lockbox bank remittance transaction data are consolidated into the Remittance Transaction Research System (RTR) which images remittance transaction information and makes it available to authorized users who need to research remittance transactions.

  3. ISRP assigns a DLN to each payment record. This DLN posts to the Master File and does not appear on the paper source posting document when the imaged archive does not fulfill research needs.

  4. The RPSID number consists of a three digit deposit date followed by a six digit numerical control number 000000 through 999999.

  5. The RPSID number does not appear on the Cycle Proof Listing (CPL)/Automated Cycle Proof Listing (ACPL).

3.5.61.3.48.1  (01-01-2010)
ISRP Identification

  1. ISRP can be recognized by the SP center assigned FLC with a 17, 19, 20, 27, 70 and 76 document code.

  2. ISRP documents are identified by the File Location Code in the DLN.

    SPC FLC Overflow FLC
    Andover 08 01
    Atlanta 07 58
    Austin 18 74
    Brookhaven 19 N/A
    Fresno 89 95
    Kansas City 09 41, 45, 46, 47, 48
    Memphis 49 57, 61
    Ogden 29 81, 83, 84, 85, 86, 99
    Philadelphia 28 54, 55, 66, 98

3.5.61.3.49  (01-01-2010)
Adjustment Documents

  1. Route case files with erroneous data attached to the originating/responsible area. For example, a file pertaining to another taxpayer or a return with a file for adjustment in the 100 blocking series.

  2. After BMF output processing is completed, pull Form 709 and related documents and file them in alphabetical order.

  3. See IRM 3.5.61.3.50, IDRS Source Documents, for special procedures for adjustments input via IDRS.

3.5.61.3.50  (01-01-2010)
IDRS Source Documents

  1. When processing source document folders supporting transactions input through IDRS, ensure that the outside of the folder contains the following information:

    • Employee Number

    • Input Date

    • Type of Input

  2. If the information shown above is not provided, return the folders to the functional area to obtain the required information.

  3. In those instances where source documents for a transaction are too bulky to fit into a folder, they are routed to the Files Function in one or more boxes with Form 3210, Document Transmittal. Form 3210 should contain the same information that would be shown on Form 6502, Employee Source Document Folder Label.

  4. For timeliness requirements when processing source document folders, see IRM 3.5.61.1.6, Timeliness Requirements.

  5. Check each block of documents (CFs 5147) against the IDRS Block List to verify receipt of all blocks.

  6. Document Code 54 with TC 534, blocking series 199 generates for both IMF and BMF

  7. Route NMF IDRS transaction records, document codes: 28, 45, 50 and 77 to the Accounting Function.

  8. Route document code 63 (except transaction codes: 53,54,55 and 70) to the Accounting Function.

  9. Do not pursue missing blocks for NMF IDRS transaction records.

  10. If a folder of source documents or documents within a folder has no generated transactions, hold and check the following day's output. If no transaction record is received, return the folder to the originating function.

    Note:

    If systemic problems occur, it may be necessary to hold the folders for a longer period of time.

  11. If a document code 47 or 54 re-file DLN blocking series transaction record is received without a source document or the source document appears invalid, route a copy of the transaction record to the initiator's manager. Do not route copies of the document code 47 transaction records that indicate Examination disposal codes: 28, 29, 33, or 36–47 or those with blocking series: 100–199, 130–179, 190–199, 280–299 and 400–479.

  12. Do not route copies of transaction records for document code 47 indicating Examination disposal codes: 29 or 99 for Employee Plans (EP) or Exempt Organizations (EO) as these will not have source documents.

  13. Do not route document code 54 transaction records with a reference code 616 as these will not have source documents. Certain document code 54 source documents may be deliberately retained by the Accounts Management Function for further action.

  14. These items will be identified by the annotation of SDR (Source Document Retained) in the" Remarks " field. Process as follows:

    1. Photocopy" SDR" transaction records and file the copy (by DLN) as a charge-out.

    2. Route original "SDR " transaction records to specific activity annotated in the" Remarks" field for association with retained source document.

    3. Route original SDR transaction records without special notation to the initiator.

  15. If a document code 64 transaction record indicates "SD " (Source Document) and is received without a source document, return it to the originator for the source document. If received and the transaction record indicates "NSD" (Non Source Document) or that the adjustment was completed based on oral statement, file the document as this denotes no source document will be sent to Files.

  16. Transaction records indicating "CIS -NSD" in Blocking Series 00 should not be returned to the originator. Block and shelve.

  17. Mail time can delay the association of the source document with the transaction record. In lieu of waiting, consider the following:

    1. Photocopy those transaction records requiring documentation for use as suspense items

    2. Associate source document when received and route to Re-files for placement in its original block.

  18. After association of appropriate source documents with their corresponding transaction record, sort all CFs 5147 into DLN sequence except Form 709 adjustments. See IRM 3.5.61.3.49, Adjustment Documents.

  19. Prepare Form 1332 and file folder or Block Divider Card for each block of documents and file in DLN order.

  20. Prepare additional block file folders when necessary to eliminate over-stuffing of folders.

  21. Certain Tax Delinquency Investigations (TDIs) used as source documents for IDRS input by the Campus TDI Function are held temporarily for subsequent action. These documents are sent to the File Functions as re-files and are labeled with the input date and employee number. Re-file source documents in the appropriate source document folder.

  22. If source documents are still not received after allowing the appropriate amount of time and contacting the originating function, notate" No Source Document Received" and file by input date and employee number sequence.

  23. File source documents folders by input date and employee number sequence.

3.5.61.4  (01-01-2010)
Elections/Election Statements

  1. This section describes the processes for receiving and processing elections and/or election statements received in the Files area.

  2. Receive and process all types of elections and consents (includes IRC Section 83(b), Form 8023 and elections where there is no record of the return) alphabetically by type of return by year of receipt unless otherwise specified in this section.

  3. Return to the originator all Elections and Consents received without the following information shown on the documents:

    • Name Control

    • MFT

    • Tax Period

  4. Retire elections as part of the administrative file of the related return, if known. Otherwise, retain in the SPC.

3.5.61.4.1  (01-01-2010)
Section 613A(c)(10) Election Statement

  1. This election statement is filed by individual taxpayers electing the exception provided by Internal Revenue Code(IRC) Section 613A(c)(10).

  2. Time stamp the statements and file in alphabetical order by year of receipt.

3.5.61.4.2  (01-01-2010)
Form 2553, Election by a Small Business Corporation

  1. Receive and maintain Form 2553 in DLN sequence by year of receipt.

  2. Retire to the Federal Records Center one (1) year after the end of the processing year.

  3. Destroy seventy five (75) years after end of the processing year.

3.5.61.4.3  (01-01-2010)
Form 8869, Qualified Subchapter S Subsidiary Election

  1. Receive Form(s) 8869 from the Entity Control Function via Form 9856, Attachment Alert.

  2. Associate with Form 2553.

  3. Route Form(s) 8869, received without the Form 2553 DLN noted for association to the Entity Control Function.

3.5.61.4.4  (01-01-2010)
Internal Revenue Code (IRC) Section 243 Election

  1. Obtain the latest Form 1120 DLN.

  2. Attach the election document to the return and refile under the most recent controlling DLN.

3.5.61.4.5  (01-01-2010)
Internal Revenue Code (IRC) Section 103 Election

  1. Process statements filed by municipalities electing the five (5) million dollar exemption provided under this IRC section.

  2. Receive and maintain elections as received by calendar year.

3.5.61.4.6  (01-01-2010)
Net Leases of Real Property Election

  1. This election can be made by taxpayers via letter, by filing Form 843, Claim for Refund and Request for Abatement or by amended return (Form 1040X).

  2. When received in the Files area, the election document should contain the DLN, taxpayers name, address, taxpayer identification number and the tax year.

  3. Associate the election document with the individual income tax return for the taxable period indicated on the election.

  4. If the DLN or "No Record" is not annotated on the election document, return it to the originator.

3.5.61.4.7  (01-01-2010)
Internal Revenue Code (IRC) Section 6222(b) Election

  1. Attach the notice/election document to the return and re-file under the return DLN (Form 1065, U.S. Return of Partnership Income.).

  2. If the DLN information is not provided, return election document to the originator.

  3. If the originator cannot be determined, route to the Accounts Management Function and request DLN determination.

3.5.61.4.8  (01-01-2010)
Form 8875, Taxable REIT Subsidiary Election (OSC only)

  1. Form 8875 is used by an eligible corporation and Real Estate Investment Trust (REIT) to jointly elect to treat the corporation as a taxable REIT subsidiary under Section 856(1) .

3.5.61.5  (01-01-2010)
Retirement Of Returns And Documents To The Federal Records Centers (FRCs)

  1. This subsection describes the processes for retiring returns and documents to the Federal Records Centers (FRCs).

  2. These instructions include procedures for:

    • Retirement of Files

    • Retired Document File (RETF)

    • Retirement of IRS Records to the Federal Records Centers (FRCs)

    • Requests and Refiles to the FRCs

3.5.61.5.1  (01-01-2010)
Retirement of Files

  1. Submission Processing Campus (SPC) File Functions retire returns and related documents in accordance with IRM 1.15.4, Records Management - Retiring and Requesting Records. File Functions are to follow retention instructions found in IRM 1.15.29, Records Control Schedule for Submission Processing Campus Records. Unless otherwise coordinated with the FRC, File Functions are to comply with the IRS-NARA Memorandum of Understanding (MOU).

  2. Destroy documents received as Re-files if the original block has already been destroyed.

3.5.61.5.2  (01-01-2010)
Retired Document File (RETF)

  1. This computer file contains information indicating whether a return or other document is retained in the SPC or has been retired to the Federal Records Center. This enables the computer to sort IDRS terminal input requests (Forms 4251) into three groups, as follows:

    • FRC retained

    • SPC retained

    • Out-of-SPC

  2. Update the Retired Document File using IDRS Command Code ESTAB, Modifier "R" by close of business on day of shipment. Instructions for inputting CC ESTADR are contained in IRM 2.3.56, IDRS Terminal Responses.

3.5.61.5.3  (01-01-2010)
Retirement of IRS Records to the FRCs

  1. Transfer records to the FRCs according to these procedures.

  2. Arrange to ship tax returns according to IRM 1.15.29, Records Management - Records Control Schedule for Service Center Operations, or other schedules mutually agreed upon by the primary or alternate IRS Campus contact and the appropriate FRC primary or alternate contact. Tax returns/documents shall be shipped per local procedures to the loading dock of the appropriate FRC servicing the IRS Campuses as set forth below:

    IRS Campus Federal Record Centers (FRCs)
    Andover Boston, MA
    Atlanta Atlanta, GA
    Austin Fort Worth, TX
    Brookhaven Dayton (Springboro), OH
    Cincinnati Dayton (Springboro), OH
    Fresno San Bruno, CA
    Kansas City Lenexa, KS
    Memphis Dayton (Kingsridge), OH
    Ogden Lenexa, KS
    Philadelphia Philadelphia, PA
  3. Furnish the FRC with the projected volume of records to be retired by the File Location Code(s) and Tax Class/Document Code. Provide annual estimates followed by exact volumes in advance of each shipment.

  4. Coordinate timeframes for retiring records to the FRC. The timeframes must be agreed upon by the receiving FRC. If an agreement cannot be made, contact the NARA COTR immediately so that a compromise can be reached.

  5. Provide records Transmittal and Receipt (SF-135) forms as prescribed by IRM 1.15.29, Records Management - Records Control Schedule for Service Center Operations.

    Note:

    Form SF-135 must be approved by the local Area Records Manager prior to being sent to the FRC at least one week before the shipping of records.

  6. Two weeks prior to the retirement, prepare pre-printed shipping labels, with the accession number and individual box number (1, 2, 3, etc.), for each box in the shipment. At that time, affix these labels to the boxes maintaining the numbered order.

  7. Supervise loading of the tax returns to ensure that the boxes are loaded securely, and in reverse numerical sequence so that when the shipments reach the FRC, the first box off loaded will be Box #1 enabling the boxes to be moved directly onto the shelves without being rearranged.

  8. Ensure that all records transferred to the FRC are in strict DLN sequence within the boxes.

  9. At the time of shipment, provide an estimate to the FRC of the number of missing blocks or segments of tax returns that are being withheld from the shipment pending further processing. This will enable the FRC to reserve adequate shelf space for the missing blocks/returns.

3.5.61.5.4  (01-01-2010)
Requests to the Federal Record Centers (FRCs)

  1. This section covers the handling of Requests:

    • Regular

    • Expedite/Priority and

    • Special Search Requests (Form 2275)

3.5.61.5.4.1  (01-01-2010)
Regular Requests

  1. Batch all requests in strict DLN and list year order.

  2. Multiple list years can be sent in the same shipment (oldest list year first.)

  3. Batch each list year separately using a transmittal/batch sheet.

  4. The transmittal/batch sheet must contain the following information:

    • Volume/count

    • List Year

3.5.61.5.4.2  (01-01-2010)
Expedite/Priority Requests

  1. Batch expedite/priority requests in strict DLN and list year order.

  2. Place these requests on the top and clearly mark as EXPEDITE/PRIORITY.

  3. For a complete list of priority pull requests, see IRM 3.5.61.1.2.3, Priority Pull Listing.

3.5.61.5.4.3  (01-01-2010)
Special Search Requests (Form 2275)

  1. Fax requests daily to the FRC in strict DLN and list year order.

  2. Annotate on the fax cover sheet the following information:

    • Volume/count

    • Request documents to be sent back using next day delivery

    • Provide your complete Files site/location return mailing address (including stop number)

3.5.61.5.5  (01-01-2010)
Re-files to Federal Record Centers (FRCs)

  1. Inter-file all attachments and documents in strict DLN and list year order.

  2. Multiple list years can be sent in the same shipment (oldest list year first).

  3. Batch each list year separately using a transmittal/batch sheet.

  4. The transmittal/batch sheet must contain the following information:

    • Volume/count

    • List year

3.5.61.5.6  (01-01-2010)
Personally Identifiable Information (PII) - Shipping Requests and Re-files to the Federal Records Center (FRCs)

  1. When shipping re-files and requests to the FRC, utilize the following Personally Identifiable Information (PII) procedures:

    1. Double pack and double label all shipments in such a way that if the package with the external label becomes damaged during transit, the inner package will protect the contents and clearly identify it as IRS property.

    2. Prepare Form 3210 for the entire shipment. Include the following information:

    • FRC direct building address

    • Number of boxes of Re-files

    • Number of boxes of Requests

    • Number of envelopes

    • Number of boxes of CSED

    • Files site/location direct building return address

3.5.61.6  (01-01-2010)
Document Requests - Forms Used to Pull Returns/Documents

  1. Various forms/documents are used to request tax returns and related documents from the Files Functions.

  2. The primary requests forms are:

    • Form 2275, Records Request, Charge and Recharge - Manual paper request and should only be used for extreme expedite or special request needs.

    • Form 4251, Return Charge-out - Systemic request input using IDRS command code ESTAB. Form 4251 (charge-out) prints the next day in the Submission Processing Center according to the Files Location Code (FLC) and is delivered to the Files Function.

  3. See Figure 3.5.61–2 below of a completed Form 2275 and Figure 3.5.61–3 for a completed Form 4251.

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

    Form 2275, Records Request, Charge and Recharge

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

    Form 4251, Return Charge-out

3.5.61.7  (01-01-2010)
Receiving and Sorting Requests

  1. Receive requests daily.

  2. Separate requests as follows:

    • List year

    • In-house (general) requests

    • Reimbursables

    • Recharges

    • Expedites

    • FRC

    • Microfilm requests

3.5.61.8  (01-01-2010)
Servicing Requests

  1. This subsection of the IRM describes the processes for servicing requests.

  2. Requests are separated into one of two categories:

    • Serviceable Request - Contains all the necessary information to fill the request

    • Unserviceable Request - Lacks all the necessary information to fill the request.

3.5.61.8.1  (01-01-2010)
Serviceable Requests

  1. A serviceable request must have the following information:

    • Document Locator Number (DLN) - Ensure that DLN is the controlling DLN for the document requested. If it is not, the correct document may not be pulled/retrieved.

    • Social Security Number (SSN)

    • Tax Period

    • Complete address including stop number

  2. Sort serviceable requests into two groups:

    • Requests for returns, copies and information

    • Requests for re-files, recharges and association of attachments

  3. Sort both groups of serviceable requests into files sequence within the File Function location as follows:

    Note:

    This sort is optional for SPC retained documents.

    • DLN - By processing year, type of return or document (IMF, BMF, etc.) and the remainder of DLN. IDRS requests are received pre-sorted into modified DLN sequence within two principal sorts: SPC retained documents and FRC retained documents.

    • Alpha - Sort Forms 4251/2275 according to the taxpayer entity information shown and route to the Document Retention Unit.

  4. Separate requests for internal use, photocopies, reimbursables photocopies and originals for the FRCs.

  5. Merge requests from other Campuses.

  6. Merge IDRS requests with other requests.

  7. Batch requests into groups of not more than 100 requests or re-files. Batch volumes may vary by depending on the campus, season (peak, non-peak), request type, etc.

  8. Route requests to the Document Retention Unit.

  9. Route request to be serviced by a FRC that normally services another SPC through that SPC.

3.5.61.8.2  (01-01-2010)
Unserviceable Requests

  1. Upon determination that a request is unserviceable, process as follows:

    • If the information is missing, unreadable or multiple DLNs are shown, return to the requester for correction.

    • If the routing information is missing or unreadable, destroy request as classified waste.

    • If the type of action requested is missing or unreadable, note the deficiency on the request and return to the requester for correction.

    • If the request is for association with an electronically filed return, return to the requester along with Form 9856, Attachment Alert, and indicate no paper documents can be associated with an electronically filed return/DLN.

    • For any other requests where insufficient information is provided, note the deficiency and return to the requester e.g. a request for a alpha document is submitted but no taxpayer entity information is provided.

3.5.61.8.3  (01-01-2010)
Servicing Requests for Returns, Copies and Information

  1. Pull and charge-out the document or note the requested information on the requisition.

  2. If the document is already charged out or is missing Block Not In File(BNIF)/ Document Not In File (DNIF), notate this information along with any other information required to be completed by the Files Function on Form 4251, Form 2275 or other requisition.

  3. Ensure that information written on the requisition is readable and can be easily understood by the requester.

  4. If the document/block is not in the files, take the necessary action to ensure that the document/block is not misfiled or improperly shelved (i.e. notify Files management for special search).

  5. If an "A " is marked on the block control sheet, this indicates a duplicate DLN. Check the following block, marked "B" on the block control sheet to ensure pulling of the correct document.

  6. Prepare copies where requested or if the requester is not entitled to the original return.

  7. Sort all filled requests by location of the requester and route to the requester based on the address shown on Form 4251, Form 2275 or the Examination Primary Business Code/Employee Group Code (PBC/EGC) listing.

  8. Before sending Form 4251 where the return is unavailable, destroy the second copy of the Form 4251. Send the requester only the copy having the charge-out information.

  9. Perform special search on unfilled requests only if the special search criteria is met.

  10. Send requests submitted by CI, TAS, and Disclosure directly from the servicing Campus in separate envelopes to the requesters. Forms 4251/2275 will have requester IDRS numbers beginning with "60" , "63 " and "79" respectively.

  11. Form 8161, Error Resolution Charge-outs, are received in two ways:

    1. Part 1 - File in its appropriate place in the block as the Error Resolution Function already has the return.

    2. Parts 2 and 3 - Attach to the return and route to the Error Resolution Function.

3.5.61.8.4  (01-01-2010)
Types of Requests

  1. This section covers the most common requests received in the Files Function:

    • Requests related to CP notice issuances

    • All other requests

3.5.61.8.4.1  (01-01-2010)
CP Notices

  1. CP notice issuances for the following conditions:

    • Duplicate Filing - CP 36

    • SSN Verification - CP 54

    • Re-file DLN - CP 55, 155

3.5.61.8.4.2  (01-01-2010)
CP 36/36A/36B/36D/36F/36P/36S/36Z, 170/170A, 193/193A and 293 (Duplicate Filing Conditions

  1. The following CP notices are reviewed in the Files Functions:

    • CP 36, Duplicate Filing Notice

    • CP 36A/B, Requisition Form for 1st Return

    • CP 36C, Substitute for Return

    • CP 36D, Injured Spouse Claims Notice

    • CP 36F (TRNS36F), Duplicate Filing Transcript

    • CP 36P (TRNS36P), Duplicate Filing Condition (Economic Stimulus Package)

    • CP 36S, Mixed Entity or Potential Scrambled SSN

    • CP 36Z, Duplicate Filing Condition - Automated Substitute for Return

    • CP 170/170A, Duplicate Doc Code 51 Assessments - A freeze

    • CP 193/193A, Duplicate Filing Condition

    • CP 93/293, Duplicate Filing Condition on Module Under Audit Investigation

  2. Review CP 36, 193, 170 and 36S notices separately from the CP 36A, 336A, 193A, 170A and 36B notices as each group is shown in DLN order according to the return being pulled. Note the following regarding these CP notices:

    • CP 36, 36S, 93, 170, 193 and 293 is the request for the return which caused the duplicate condition.

    • CP 36A, 36B, 170A and 193A is the request for the first return posted.

    • CP 193A is generated on MFTs 03, 36, 60, 63 and 64 only.

  3. Pull the document for the DLN located in the heading on the upper right hand portion of the CP notice. If the Block Control Sheet for the DLN on the CP is marked with an "A or B" , check the following block by indicating either "A or B " to ensure the correct document is pulled/retrieved.

  4. Use Part 1 to transmit the return to the Accounts Management Function. Use Part 2 as a charge-out.

  5. If the return requested is housed in the FRC, forward the CP or return the request unfilled to the Accounts Management Function.

  6. Identify the appropriate Campus based on the File Location Code (first two digits) of the DLN of the return causing the duplicate filing condition.

  7. Send the returns with the CP notices to the Accounts Management Function.

  8. Send CP 193/193A for MFTs 04 and 05 to the Compliance Function in the Cincinnati Submission Processing Campus only.

  9. For CP 93 and 293, pull the duplicate returns only if the original return is already charged out to the Examination Function.

  10. Pull/retrieve CP 36D having an ELF FLC and 92X blocking series and route to the Accounts Management Function on Form 3210. Annotate" ELF Returns - Injured Spouse - CP 36D."

  11. When processing CP 36Z, note the following:

    • TC 150 DLN/Tax Class 2

    • Document Code 10

    • Julian Date 887

    • FLCs: Austin (18); Brookhaven (19); Fresno (89)

  12. Send CP 36Z to the appropriate Collection/ASFR Function(s) as follows:

    • Austin - 3651 South IH35, Stop 5501, Austin , TX 78741

    • Brookhaven - 1040 Waverly Avenue, Stop 654, Holtsville, NY 11742–1129

    • Fresno - 5045 E. Butler, Stop 81404, Fresno, CA 93727–5136

  13. For those CPs where specific instructions are not provided, follow the procedures shown above for CP 36.


More Internal Revenue Manual