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

11.3.13  Freedom of Information Act

11.3.13.1  (10-26-2007)
Background

  1. The Freedom of Information Act (FOIA) 5 USC 552, as amended by the 1974 Amendments to the Freedom of Information Act ( PL 93-502), the Freedom of Information Reform Act of 1986 (PL 99-570), and the Electronic Freedom of Information Act Amendments of 1996 (PL 104-231), provides for public access to records and information maintained by Federal agencies. The IRS Restructuring and Reform Act of 1998 (PL 105-206) also affects the FOIA request process.

  2. Prior to the enactment of FOIA, first effective July 4, 1967, there were no effective guidelines to help a person obtain information about how the government operated, and no judicial remedies for those denied access to governmental records. With the passage of FOIA, the burden shifted from the requester having to justify access to governmental records, to the government having to justify why information would not be released.

  3. The premise of the FOIA is that the public has a right to know what goes on in government without having to demonstrate a need or reason, and a right to file an administrative appeal or a suit in U.S. District Court if denied access to records.

  4. This section deals primarily with processing requests pursuant to Section (a)(3) of the Act for reasonably described records maintained by the IRS which are not required to be published or otherwise made available under Sections (a)(1) or (a)(2) of the Act.

    Note:

    See IRM 11.3.7, Freedom of Information Reading Room Operations, for the interaction of these provisions and maintenance of IRS' Freedom of Information Reading Room.

  5. Treasury Directive 25-05, dated March 1, 2000, establishes policy and procedures and assigns responsibilities for carrying out the requirements of the Act within the Department of the Treasury.

  6. In October, 2001, Attorney General John Ashcroft issued a new FOIA policy directive that the Department of Justice will defend an agency's decision on FOIA exemptions unless they lack a sound legal basis or present an unwarranted risk of adverse impact on the ability of other agencies to protect other important records. The Attorney General's new FOIA policy memorandum supersedes the FOIA memorandum issued by Attorney General Janet Reno on October 4, 1993. Attorney General Ashcroft's policy statement pertains to the DOJ's legal defense policy and does not contradict President Clinton's FOIA policy statement of October 4, 1993, in support of government openness and accountability associated with the agency's initial determinations. In this policy directive, the Attorney General advised agencies to make discretionary disclosures of information protected under the FOIA only after full and deliberate consideration of the institutional, commercial, and personal privacy interests that could be implicated by disclosure of the information.

  7. Effective April 23, 2004, the IRS issued Policy Statement 11-13, Freedom of Information Act Requests. (Formerly P-1-192). This Policy Statement affirms the commitment of the IRS to administering the FOIA in a manner consistent with "the fundamental values held by our society, including public accountability, safeguarding national security, enhancing the effectiveness of law enforcement agencies and the decision-making processes, protecting sensitive business information, and protecting personal privacy." The policy statement goes on to note that the "administrative cost and impact on operations involved in furnishing information in response to a FOIA request is not to be a material factor in deciding to deny a request unless the cost or impact would be so substantial as to seriously impair IRS operations."

    Note:

    See IRM 11.3.13.7.2.5 for further discussion of applying these guidelines when processing FOIA requests and asserting the (b)(5) exemption.

  8. All actions taken and determinations made in response to FOIA requests will be in accordance with procedural rules appearing at:

    • 31 CFR Part 1, and Appendix B; and

    • 26 CFR 601.702.

  9. Treasury is in the process of issuing guidelines to change the identification of "Official Use Only" (OUO) documents to "Sensitive But Unclassified" (SBU). References throughout this IRM to OUO material should be considered synonymous with SBU.

  10. Disclosure is in transition from the Electronic Disclosure Information Management System (E-DIMS) to a new management system, Automated Freedom of Information Act (AFOIA). During this transition, new initiatives, such as the inventory balancing system, may be implemented. All case processing must be consistent with procedures established by these new processes.


11.3.13.2  (10-26-2007)
Authority

  1. The Director, Governmental Liaison and Disclosure, and his/her delegate, have authority to make FOIA determinations concerning records under their jurisdiction.

  2. Officials who make FOIA determinations must request the recommendation of the function(s) having primary interest or issuing authority for the record(s) unless the same or substantially similar information has already been made available to the public or to the subject requester (as appropriate), or the determination is consistent with an established practice. Under these circumstances, coordination with the interested function or issuing authority will usually be unnecessary.

  3. If the deciding official disagrees with the recommendation of the affected function, discussions must be initiated with the function to resolve the disagreement or to afford the function a chance to provide further justification regarding the recommendation.

    Note:

    The recommendations may be useful in considering the application of FOIA exemptions to the records or may help to identify the harm which would result from the release of the requested records.

    Reminder:

    Recommendations are not binding upon the official who has the authority to make FOIA determinations and who must release or withhold records in accordance with his/her knowledge of the law.

  4. Requests for records written by the Office of Chief Counsel or known to involve matters in litigation where the IRS is a party, or that would otherwise be of interest to Counsel shall be coordinated with the affected Counsel office. If Disclosure personnel are uncertain as to the Counsel point of contact, contact Branch 6 or 7 of the Office of the Associate Chief Counsel, Procedure and Administration, who can assist in identifying the appropriate Counsel office.

    Note:

    In litigation not involving the IRS, coordination with Counsel is not generally required unless the responsive documents were written by Counsel or otherwise evidence Counsel interest or advice.

  5. Requests for records originating in other Federal agencies that require coordination with the appropriate agencies will be forwarded to the following address:

         IRS FOIA Request
         Disclosure Office
         SE:S:CLD:GLD:D
         1111 Constitution Avenue, NW
         Washington, DC 20224

  6. See IRM 11.3.13.5.6 for further guidance related to records originating in another agency.

  7. Requests involving the news media or subject matter believed to be of interest to the news media are to be coordinated with the Office of Communications, National Media Relations, through the local Public Affairs Specialist.

    Note:

    See IRM 11.3.13.9.26 for a definition of news media requester.

  8. FOIA requests for Treasury Inspector General for Tax Administration (TIGTA) records require special processing.

    1. FOIA requests for access to TIGTA records, (other than those publicly available as discussed below) created after January 18, 1999, are processed by TIGTA's Disclosure Officer and must be referred to:
           TIGTA
           Office of Chief Counsel
           IG:CC:Disclosure
           Room 700
           1125 15th St. NW
           Washington, DC 20005

      Note:

      The Disclosure Manager receiving the request shall inform the requester of the referral. See 26 CFR 601.702(c)(3)(i).

    2. Copies of records created prior to the move of Inspection from IRS to Treasury (January 18, 1999) may occasionally be found in an IRS file. For FOIA purposes, any determinations made regarding release of these documents must be coordinated with the Disclosure Officer, TIGTA. The IRS will make the final determination after considering TIGTA's input.

    3. Certain reports of audits given to the IRS by TIGTA, the operations manual, delegation orders, and other publicly available information, may be accessed by using the TIGTA E-FOIA website at:

      http://www.treas.gov/tigta/foia/available-documents.htm.

      Note:

      If a FOIA request seeks this information, the requester can be directed to this website.

    4. If a TIGTA Report of Investigation is part of an agency grievance file, it may be provided to the grievant in response to a FOIA request unless it is flagged. See IRM 11.3.20.12.2.


11.3.13.3  (10-26-2007)
Responsibility

  1. FOIA requests must be considered as requests for records under the jurisdiction of the receiving office unless:

    1. The request contains some indication that access to records located elsewhere is desired, or

    2. Research suggests that transfer to another office would provide better service to the requester. See IRM 11.3.13.5.12 below.

  2. Requests for Counsel records are processed by the Disclosure office in whose jurisdiction the underlying tax case originated. Requests for records of an Appeals Office are processed by the Disclosure office in whose jurisdiction the underlying tax case originated.

  3. Requests concerning investigation records will be processed by the office where the records originated. Disputes concerning the release of records will be resolved using the procedures in IRM 11.3.13.2(3).

  4. Requests may involve records pertaining to more than one office. In such a case, processing responsibility should be determined on the basis of major interest (i.e., in terms of volume of records, requester's address or location of any current activity). Hence, the response may be split among several offices or consolidated in one office. Disclosure Managers shall discuss such situations prior to making transfers. See IRM 11.3.13.5.12 for further discussion of transfers.

  5. Complex situations may require the assistance of the GLD Area or Headquarters Disclosure office. See IRM 11.3.13.5.5 regarding requests addressed or sent to multiple offices.

  6. Campuses should not be considered the responsible processing office for records which may be in their possession for computer input or retention, but which are primarily field office records.

    Note:

    Requests for transcripts should not be transferred when they can be obtained by the recipient office.

  7. Records retired to the Federal Records Centers are the responsibility of the originating office, and shall be retrieved when needed to process a request.

  8. A request for records received in the local IRS office after a case has been referred to the Department of Justice remains the responsibility of the local office.

    1. The Disclosure office will make determinations as to the records which exist at the local office.

    2. Any response must be coordinated with the assigned Division Counsel attorney and the assigned attorney in the Department of Justice.

    3. If the local office has not retained copies of any records sent to the Department of Justice, advise the requester that other records are in the custody of the Department of Justice. With the permission of the assigned Department of Justice attorney, the requester should be advised of the name, address and phone number of that attorney.

    4. Disclosure personnel will not refer a third party requester who has not established a right to access the requested information to the Department of Justice.

      Note:

      See IRM 11.3.13.5.4 regarding imperfect requests.

11.3.13.3.1  (10-26-2007)
Disclosure Managers

  1. Disclosure Managers are responsible for administering the FOIA Program. Responsibilities related to processing FOIA requests may involve:

    1. Establishing procedures to ensure uniform and consistent treatment of FOIA requests. Use of standardized language or paragraphs in communications with the requester should be encouraged as much as possible.

    2. Educating requesters on the proper procedures for filing a valid FOIA request, and educating IRS employees on the provisions of FOIA that affect them.

    3. Using the inventory management system to control FOIA inventory to ensure timely responses.

    4. Completing reviews of work in process for accuracy, completeness, and timeliness.

    5. Coordinating requests with the functions providing responsive data.

    6. Providing direction to functional coordinators on the procedures related to their responsibilities in the FOIA process.

    7. Providing assistance with respect to administrative appeals and lawsuits.

    8. Determining if records marked "official use only" or "limited official use" should be declassified and released to a FOIA requester.

      Note:

      See IRM 11.3.13.12. for further discussion regarding classification of records.

      Note:

      At the time of this IRM revision, Main Treasury is in the process of revising procedures for document classification.

  2. In addition, each Disclosure office should develop sufficient Functional Coordinators or other staff with an adequate level of disclosure experience to constitute a reliable reserve to assist Disclosure Managers in the event that unexpected increases in FOIA requests cause inventories to build up more rapidly than new staff can be developed.

  3. Disclosure Managers have been delegated the authority to make agency determinations. Delegation order 11-2, can be found in IRM 1.2.49.2.This authority includes the responsibility for deciding what is releasable and signing the response letter to the requester. Some authorities can be re-delegated to Disclosure Specialists and Assistants. The re-delegation order can be found at: http://mysbse.web.irs.gov/CLD/GLD/Disclosure/Office/Guidance/Memos/5602.aspx.

  4. Disclosure Managers are authorized to re-delegate the authority to sign partial and full denials to Senior Disclosure Specialists (GS-12) and Disclosure Specialists (GS-11). This authority is limited to only those instances where the Disclosure staff is located in a remote site away from the Disclosure Manager. This re-delegation order can be found at: http://mysbse.web.irs.gov/CLD/GLD/Disclosure/Office/Guidance/Memos/5594.aspx

    Note:

    Neither of these delegation orders affects who can authorize FOIA responses where information is withheld under IRC §6103(e)(7) impairment of Federal tax administration). This authority cannot be re-delegated below the supervisory level (see Delegation Order 11-2). Any denial or partial denial of records pursuant to FOIA exemption (b)(3) in conjunction with IRC §6103(e)(7) must be authorized by the Disclosure Manager, or an individual designated to act in that capacity in his/her absence. A brief phone call between the off-site Specialist reviewing the case and the Disclosure Manager (or his or her designated acting) to describe the circumstances and obtain concurrence would be sufficient. The Disclosure Manager shall add a history note documenting the discussion and his/her concurrence with the decision to withhold information pursuant to IRC §6103(e)(7).

11.3.13.3.2  (01-01-2006)
Functional Coordinators

  1. The role of Functional Coordinators in processing FOIA requests will depend upon local circumstances.

  2. The Functional Coordinator, as the contact point between the Disclosure Manager and the function, will serve in whatever way is necessary to facilitate the disclosure process. As such, he/she will request or secure such functional resources and cooperation as may be necessary. Functional Coordinators may, for example:

    1. Advise which records fall within the scope of the request

    2. Conduct record searches

    3. Obtain necessary copying services

    4. Analyze records

    5. Perform any necessary editing, sanitizing or segregating of records

    6. Prepare the functional recommendation, if any

    7. Assist in verifying requester identity

    8. Prepare indexes and

    9. Possibly serve as a witness in litigation regarding the scope of the search or the reasons certain exemptions were claimed.

  3. As the point of contact in that function, the Coordinator shall provide the following information with each response:

    1. Which offices were contacted and why

    2. Person(s) spoken to in each office and who conducted the search

    3. Files searched, if other than those initially recommended in the records search request

    4. Search terms used

    5. Volume and location of records found and

    6. Time spent by the function working the case (locating, reviewing, editing, and copying records)

    Caution:

    If total time is reported rather than separating search time, a requester could be overcharged. See IRM 11.3.13.6.3(10)(e) regarding the use of a search memo response questionnaire to ensure accurate reporting of time.

  4. Functional Coordinators may occasionally be called upon to assume the total responsibility (except for signing the response) for responding to selected FOIA requests, subject to Disclosure Manager control and direction. Such assignments may develop the Coordinator's expertise as an adequate backup or as a resource to reduce temporarily excessive inventories.

11.3.13.3.3  (10-26-2007)
Unique FOIA Aspects

  1. Requests involving unique FOIA aspects, those requiring multi–office coordination or those having national implications shall be brought to the attention of the Chief, Disclosure, through appropriate channels.

  2. The Chief, Disclosure, may determine that certain cases require special handling and may direct that cases be transferred accordingly. Requests involving the following will be transferred to the Baltimore Disclosure Office:

    1. Requests involving national contracts;

    2. Requests involving background records for Office of Management and Budget approval pertaining to a specific form; and

    3. Requests for written determinations and background file documents.

      Note:

      See IRM 11.3.13.9.1 for procedures related to written determinations.

  3. Information obtained from Interpol may be included in enforcement action files. Coordination with the Chief, Disclosure, is required before releasing Interpol information.


11.3.13.4  (01-01-2006)
Overview and Processing

  1. Processing a request under the FOIA consists of five basic steps:

    1. Receipt and control - classification, assignment and logging of requests;

    2. Analysis - review of the request for validity or other special features;

    3. Search - search procedures for responsive records;

    4. Review - review of responsive records and application of exemptions or exclusions;

    5. Response and closing - drafting of response to requester and closing the case.

  2. Each of the five basic steps has specific procedural and technical requirements, which will be discussed in detail in this section of the IRM.

    Note:

    Caseworkers will take substantial action that moves a case forward toward completion (e.g. ordering IDRS research or sending a search memo) within 10 calendar days of assignment of a request. All activities, including reasons for any delays, shall be documented in the inventory management system by notating the case history and updating the status code.

11.3.13.4.1  (01-01-2006)
Receipt and Control of FOIA Requests

  1. Receipt and control of requests for information under the FOIA include:

    1. Date stamping the request to show receipt date.

    2. Determining the type of request using definitions found in the FOIA and in the Electronic Disclosure Information Management System (E-DIMS) User Guide, available through the E-DIMS HELP menu.

    3. Inputting the request into the inventory management system, including the assigned caseworker, type of case and all other required information.

    4. Foldering the request based on national guidelines and forwarding it to the assigned caseworker.

  2. The date stamp shall be placed on the request to establish the date the request was received in the Disclosure office. This will allow computation of the statutory 20 day time period for a response or a request for a voluntary extension.

  3. Requests are classified as either Section (a)(1), (a)(2), or (a)(3), depending upon the nature of the information requested.

  4. Section (a)(1) requests are for agency records required to be published in the Federal Register. Requests for IRS Regulations or for Privacy Act System of Records Notices fall under this category.

  5. Section (a)(2) requests are requests for agency records required to be made publicly available for inspection and copying. Requests for Reading Room materials such as IRMs and Field Directives fall under this category.

  6. Section (a)(3) requests are for agency records that are not required to be made available to the public under Section (a)(1) or (a)(2). Requests for tax records or information protected by the Privacy Act fall under this category.

  7. The order of priority for requests seeking records that fall under more than one category is (a)(3), (a)(2), and (a)(1). The request shall be categorized and logged under the highest category of records requested, with (a)(3) being the highest.

    Example:

    A request for IRM 11.3 (under (a)(2)), combined with a request for tax records (under (a)(3)) will be logged as an (a)(3) request.

  8. The Disclosure Manager or other responsible employee should, wherever feasible, review the request after it is date stamped to designate the assigned caseworker. The request will then be provided to the employee with responsibility for input, foldering, and forwarding to the assigned caseworker.


11.3.13.5  (10-26-2007)
Initial Analysis of FOIA Request

  1. Requests must be thoroughly analyzed by the assigned caseworker to determine if a response is appropriate under the FOIA. Analysis of the correspondence may reveal:

    1. The request may be imperfect under the FOIA ( See IRM 11.3.13.5.4).

    2. The information requested may be under the jurisdiction of another agency or office ( See IRM 11.3.13.5.6 and IRM 11.3.13.5.7).

    3. The request may be directed to multiple offices requiring coordination of efforts ( See IRM 11.3.13.5.5).

    4. The request may be unclear as to the statute under which access is being sought ( See IRM 11.3.13.5.11) and

    5. Information requested may be available outside of the FOIA under other provisions of the law or under routine established agency procedures. See IRM 11.3.13.5.13).

  2. Proper analysis of the request by the assigned caseworker will result in determining how best to handle the request and will ultimately provide better customer service.

  3. The initial review of any request must include an analysis of the content of the request to determine if it complies with FOIA regulations or if not, whether the information could be provided under other provision of law or under established agency procedures, as appropriate. See IRM 11.3.13.5.4, IRM 11.3.13.5.9, IRM 11.3.13.5.10, and IRM 11.3.13.5.13.

  4. The FOIA, as implemented through regulations found at 26 CFR 601.702(c)(4), requires that a request:

    1. Be made in writing and signed by the person making the request

    2. State that it is made pursuant to the FOIA, or the regulations thereunder

    3. Be addressed to and mailed or hand delivered to the local Disclosure office or the office having control of the records, generally this is the office serving the state where the requester resides

    4. Reasonably describe the records sought

    5. In the case of records subject to IRC §6103 or the Privacy Act, establish the identity of the requester and the requester's right to receive the records

      Note:

      A stamped signature is not sufficient to establish a requester’s identity or right to obtain access to records the disclosure of which is restricted by statute or other authority. A FOIA request for such records under (a)(3) must, therefore, be physically signed by the requester. Any such request for (a)(3) records that is "signed" with a stamped signature will be rejected as imperfect.

      Note:

      IRS does not accept digital signatures for FOIA requests.

    6. Set forth the address to which the response is to be sent

    7. State whether the requester wishes to inspect the records or have copies made without prior inspection

    8. State the requester's agreement to pay for search, review, and reproduction charges as applicable (however, See IRM 11.3.13.5.4(3))

    9. Furnish an attestation under penalties of perjury as to the status of the requester (e.g. commercial use, media, noncommercial, scientific, educational, or other requester), and state how the records will be used, unless the requester is an "other" requester

  5. Upon receipt, a FOIA request must be analyzed properly to ensure that the recipient office has jurisdiction over the requested records.

  6. If it is determined that another Disclosure office has jurisdiction over the records, the request must be promptly transferred to the correct office within the 20 day response period. Further delay may unnecessarily cause an administrative exhaustion and possible litigation.

    Note:

    Treasury Regulation 601.702(c)(4)(i)(C) states that a FOIA request should generally be directed to the office serving the requester's geographic area of residence. Therefore, the calculation of the statutory response date begins on the date a valid FOIA request is received in such office. Transferring a request for internal jurisdictional or inventory management considerations does not change the received date or the statutory response date. If it is necessary to transfer the case, the receiving office must log it onto the inventory management system with the date it was received in the initial office. However, where a request is sent to an office outside of the requester’s geographic area, the statutory response time does not begin to run until the request is received in the correct office.

    Note:

    During the reorganization of GLD into CLD, a number of changes were made to the organizational structure that are not reflected in the Treasury Regulation. Requests transferred as a result of these changes shall be logged in as of the date received in the original office.

  7. No FOIA request can be deemed to be imperfect because the request was improperly addressed to a local Disclosure office. Disclosure personnel are required to respond to the request or forward the request to the appropriate IRS Disclosure office. See IRM 11.3.13.5.6 for procedures when records of another Agency or Treasury Component are requested.

    Note:

    Disclosure Managers may not respond by telling the requester that he or she sent the request to the wrong office and providing the address of the correct office or offices. Requests must be transferred by Disclosure personnel.

  8. When a request seeks tax records of a taxpayer other than the requester, it must include proof that the requester is authorized to obtain the records sought. This authority may be proven:

    1. By a properly completed Form 8821 , Tax Information Authorization, or equivalent.

      Note:

      This may be enclosed with the request or may have been separately sent to the IRS. A Form 8821 or equivalent must be received by the IRS within 60 days of the date the taxpayer signed and dated the document and must comply with all of the other requirements of 26 CFR 301.6103(c)-1.

      Note:

      To compute the 60-day limitation, day 1 is the day after the authorization was signed by the taxpayer. The authorization must be received by the IRS on or before the 60th day after the taxpayer signed the authorization.

    2. By a properly completed Form 2848, Power of Attorney and Declaration of Representative, or equivalent.

      Note:

      This may be enclosed with the request or may have been separately sent to the IRS. (A Form 2848 or equivalent need not be received within 60 days of the date the taxpayer signed it.)

      Note:

      Part II of the Form 2848 must be completed (or the information provided in an equivalent document). If this information is not provided, the document is incomplete and the FOIA request is considered imperfect.

      1. A valid Form 2848 sent to any office of the IRS should be assumed to be for representation purposes, unless there is evidence to the contrary (e.g. the Form 2848 specifically states "For FOIA request purposes" .)

      2. When processing the request, Disclosure personnel should not require that the Form 2848 be filed with the CAF Unit or that there be an open or closed tax case on the taxpayer.

        Note:

        Disclosure personnel should not forward Forms 2848 received in connection with a FOIA request to the CAF for input.

        Note:

        The filing of a FOIA request alone does not constitute practice before the IRS and is therefore, not covered by Circular 230.

      3. Generally, the receipt of a properly executed Form 2848 is sufficient to establish the representative’s identity and right to access the requested information. However, where the Disclosure Manager has reason to question the validity of the information submitted, additional proof of an individual’s identity and right to access may be requested. The caseworker must document the case history to explain why additional verification was necessary.

    3. If the taxpayer is an entity, by documentation demonstrating that the relationship between the taxpayer and the requester meets the applicable provision of IRC §6103(e). See IRM 11.3.13.5.1(9) and IRM 11.3.2, Disclosure to Persons with a Material Interest.

      Note:

      In March 2004, the Service stopped accepting Form 2848 as authority to disclose tax information to a designee if the designee was not eligible to practice before the Service. (See Instructions to Form 2848). Thus, the designee must complete Part II of the Form 2848 (or provide the Part II information in an equivalent document). If the designee is ineligible to complete Part II, the taxpayer must use Form 8821, or an equivalent, to authorize disclosure of returns or return information to that designee. Designees who cannot use a Form 2848 include organizations and individuals who are not eligible to practice before the IRS.

  9. Upon receipt of a request that has an imperfect disclosure authorization because of the 60 day rule, Disclosure personnel shall promptly contact the requester for a timely authorization. For customer service considerations, if the request is otherwise valid, and the requester states that a valid authorization will be submitted promptly, then search efforts may be initiated. However, records must not be provided until a valid disclosure authorization is received.

  10. If the request does not meet one of the other provisions of the regulations, the request should be treated as an imperfect request and the requester so advised.

11.3.13.5.1  (01-01-2006)
Identity of Requester

  1. The establishment of the identity of the requester is an important part of determining the overall validity of the FOIA request. Identity must be established prior to releasing any records which would be available to the requester only, and not to the general public. Examples are tax or personnel records.

  2. If in-person contact is made, the requester may establish his or her identity by presenting either one document bearing a photograph (such as a passport, driver's license, or identification badge) or two items of identification which do not bear a photograph, but do bear both a name and signature.

    Note:

    Expired identification documents will not be accepted.

  3. If contact is by mail, identity can be established by a signature, address, and one other identifier (such as a photocopy of a driver's license) bearing the requester's signature.

  4. An individual may also establish identity by presenting a notarized statement swearing to or affirming his or her identity.

    1. The notarized statement need not necessarily meet all the requirements of State law, so long as it appears to be adequate to establish the requester's identity.

      Note:

      See IRM 11.3.13.5.1(7) for factors to consider when determining whether to accept the notarized statement.

    2. The notarized statement need not be on the same sheet of paper as the request or bear the same date, as long as it is consistent with the request and is adequate to allow access to the records requested. The notary seal must be on the same page as the sworn statement.

      Note:

      If the notarized statement is on a page separate from the FOIA request, the requester’s signature on the notarized statement is sufficient to meet the regulation requirement that the FOIA request be signed.

    3. If the notarization does not swear to or affirm the requester's identity, then it does not meet the FOIA identification standard. The following is an example of a valid notary statement.

      Example:

      Mr. John Maple, known to me to be the person who executed the foregoing instrument and having acknowledged to me that he executed the same as his free act and deed.

    4. After consideration of all the factors, Disclosure personnel must exercise sound judgment in determining whether the requester has proven his or her identity. The notarized statement must be sufficient to reasonably assure an employee that the requester is the taxpayer whose records are being sought. If the notarization meets that standard, IRS can accept it as establishing the requester’s identity for purposes of considering the FOIA request valid. If there continues to be doubt, the request shall be deemed imperfect and additional verification of identity sought.

  5. A sworn statement as to identity, under penalty of perjury, is acceptable in lieu of a notarized statement. The sworn statement must meet the requirements of 28 USC 1746. If the declaration is sworn outside the United States, the sworn statement must include the following language: "I declare (or certify, verify, or state) under penalty of perjury under the laws of the United States of America that the foregoing is true and correct. Executed on (date)." If the declaration is sworn within the United States, its territories, possessions, or commonwealths, the sworn statement must include the following language: "I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date)."

  6. The Disclosure Manager may require additional proof of an individual's identity if it is determined to be necessary to verify the requester's right of access.

    Note:

    If additional proof of identity is requested, the case history shall be fully documented to explain why the verification submitted was not sufficient.

  7. Consideration should be given to the consistency of names, addresses, Social Security Numbers and other identifying information in the request with similar items in the records requested. Copies of notices, correspondence, and other records which the requester received from the IRS can help to establish identity, especially when the records requested are closely related to the subject matter of the record presented. See IRM 11.3.13.5.8(4).

  8. If the request is made in connection with a tax administration matter, an IRS employee (such as the examining agent) may provide verification of the requester's identity if necessary.

  9. Persons requesting records on behalf of or pertaining to another person must provide adequate proof of the legal relationship under which they assert the right to access the requested records. Such requests must meet the requirements of 26 CFR 601.702(c)(5)(iii). Requests for tax records must be consistent with the provisions of 26 CFR 301.6103(c)-1 and IRC §6103(e). A valid Form 2848, Power of Attorney and Declaration of Representative, is sufficient authorization. A Tax Information Authorization (Form 8821) meeting the standards of 26 CFR 301.6103(c)-1(b) is also sufficient authorization.

  10. In the event of multiple requests, it is unnecessary to provide separate documentation of identity for each request. Once the identity of the requester has been established at a local office, that identification should suffice for a continuing series of requests, as long as the thrust of the requests, the address, and the signature of the requester remain constant.

    Example:

    A single envelope contains six specific requests for information from the same requester. One of the requests does not establish identity when the remaining five are adequate. Do not consider the one request imperfect for this reason alone.

    Example:

    You receive requests routinely from the same requester and have been provided sufficient identifying information in the past. A recently received request does not adequately identify the requester. To the extent all other information is consistent, do not consider this request imperfect for this reason alone.

    Note:

    Disclosure offices are not required to maintain a system whereby a taxpayer's identifying information is maintained for later reference in the event a FOIA request is received. The above will apply only if it is readily apparent. However, because a Form 8821, Form 2848, or equivalent can be revoked by the taxpayer, Disclosure offices are expected to make reasonable efforts to confirm their continuing validity.

    Note:

    If the reason for accepting the requester’s identity is not readily apparent, document the case history notes to explain your determination.

11.3.13.5.2  (01-01-2006)
Definition of Agency Record

  1. The FOIA provides for the disclosure of "agency records." Not every record within the possession of an agency is an agency record subject to the FOIA. "Agency records" are records that are either created or obtained by an agency, and are under agency control at the time of the FOIA request. Courts have identified four relevant factors to consider when determining whether a record is an agency record:

    1. The intent of the record’s creator to retain or relinquish control over the record

    2. The ability of the agency to use and dispose of the record as it sees fit

    3. The extent to which agency personnel have read or relied upon the record for agency business and

    4. The degree to which the record was integrated into the agency’s record keeping system or files

  2. Records that are not agency records are not responsive to a FOIA request, regardless of whether the subject matter or type of record would otherwise appear to be responsive to the request.

  3. Whenever a request seeks records that originated outside of the IRS, Disclosure personnel will make a determination, after coordination with the record's originator, whether the records are agency records based upon the factors mentioned above.

11.3.13.5.3  (10-26-2007)
Joint Committee on Taxation

  1. The Joint Committee on Taxation is authorized to receive information, including returns and return information, from the IRS pursuant to various provisions in the Internal Revenue Code. See IRC §6103(f)(2), IRC §6405, and IRC §8023.

  2. IRC §8021 authorizes the Joint Committee to request information, including returns and return information pursuant to § 6103(f), for the purpose of carrying out its oversight authority. Whenever the Joint Committee corresponds with the IRS under this general oversight authority, it includes a legend on the incoming correspondence that restricts the dissemination and use of both the inquiry and responsive records. The Joint Committee reserves the right to adjust the legend as needed, after coordination with the Service.

    Note:

    At this time, the legend provides: This document is a record of the Joint Committee on Taxation ("Joint Committee" ) and is entrusted to the IRS for your use only in handling this matter. Additionally, any documents created by the IRS in connection with a response to this Joint Committee document, including (but not limited to) any replies to the Joint Committee, are records of the Joint Committee and shall be segregated from agency records and remain subject to the control of the Joint Committee. Accordingly, the aforementioned documents are not ‘agency records’ for purposes of the FOIA. Absent explicit Joint Committee authorization, access to this document and any responsive documents shall be limited to IRS personnel who need such access for the purposes of providing information or assistance to the Joint Committee.

  3. Whenever the Joint Committee’s inquiry letter includes a restrictive legend, the file that is created for the IRS’s reply, as well as any accompanying documents, may only be accessed by IRS personnel for the purpose of providing information to, or otherwise assisting, the Joint Committee. Copies of the inquiry letter and the IRS response are maintained by the Office of Legislative Affairs in their Executive Correspondence Management System (ECMS). Copies of records compiled by the IRS to respond to the Joint Committee inquiry are maintained in the office of the IRS component chiefly responsible for preparing the response.

  4. Whenever the Joint Committee’s inquiry letter includes a legend, that letter remains a congressional record. In addition, any records created by the IRS in connection with the agency’s response to the Joint Committee’s inquiry, including (but not limited to) the IRS reply letter, will also be treated as congressional records. Accordingly, the inquiry letter from the Joint Committee, and any records created by the IRS as a result of, or in response to, that inquiry, are not agency records responsive to a FOIA request and must not be released under the FOIA. Moreover, the IRS file(s) associated with providing records to the Joint Committee need not be searched for responsive records because the records the files contain are not agency records.

  5. FOIA requests received in the field that seek access to records involving the Joint Committee will be coordinated with the Headquarters FOIA Group. Disclosure personnel will consult with the Joint Committee, as well as any affected IRS function(s), before determining whether to release or withhold any agency records that are the subject of a Joint Committee oversight inquiry.

  6. Depending upon the wording of the FOIA request, copies of records created and maintained by the IRS in the normal course of its operations that are subsequently provided to the Joint Committee in response to a general oversight inquiry may be agency records subject to the provisions of the FOIA, or may be considered congressional records not subject to the FOIA:

    1. If the FOIA request specifically asks for records reviewed by the Joint Committee, the disclosure of any records, or even the acknowledgement that these records exist in the context of a Joint Committee inquiry, may confirm that the Joint Committee had exercised its general oversight responsibilities. These records are congressional records because the Joint Committee inquiry letter bears a legend, the records are maintained in files pertaining to the Joint Committee oversight inquiry, segregated from agency files, and accessible only by IRS personnel involved in responding or providing assistance to the Joint Committee.

      Note:

      Where a FOIA requester asks for "all requests by the Joint Committee for [a particular matter]," the IRS will issue a determination that, to the extent such records exist; they are congressional records and are not subject to the FOIA.

    2. If the FOIA request seeks a file, such as an examination file, which happens to contain records generated in the normal course of its operations that were subsequently furnished to the Joint Committee as part of its general oversight responsibilities, the records in the requested file are agency records subject to the FOIA. Because neither the acknowledgement nor the release of the records reveals the existence or the subject of a Joint Committee oversight inquiry, they remain agency records. In the absence of any applicable FOIA exemption, the records in the file will be provided to the requester. For treatment of Joint Committee records in IRC §6405 refund or credit cases, see IRM 11.3.4.6 and IRM 4.36.3.10.

      Note:

      Where a FOIA requester asks for "all records on me" and it is determined that the IRS is in possession of copies of, for example, an incoming Joint Committee general oversight inquiry letter bearing a Joint Committee legend, the IRS reply to the Joint Committee or any records prepared by the IRS as part of its response to the Joint Committee inquiry, then such records are not agency records. These records must not be identified as part of the agency’s responsive records in the FOIA determination letter. However, any other records responsive to the request that are agency records are to be processed under the normal FOIA procedures.

  7. In addition to its general oversight authority under IRC §8023, the Joint Committee may also conduct a review under IRC §6405 of the IRS’s proposed issuance of refunds or credits that meet the jurisdictional threshold. §6405 directs the IRS to delay the issuance of large refunds or credits for a thirty day period to afford the Joint Committee an opportunity to review the proposed action. Correspondence or other documentation reflecting the Joint Committee’s review of these proposed credits or refunds will be maintained separately within the administrative file of the taxpayer to whom it pertains. Joint Committee correspondence in this context does not contain a legend, and any documents or information received from the Joint Committee or prepared by the IRS in response thereto will constitute agency records subject to the FOIA. See IRM 4.36.1.2, IRM 4.36.3.10, IRM 4.36.4.6 and IRM 11.3.4.6.

  8. After consulting with the Joint Committee as to whether correspondence from the Joint Committee pertaining to its §6405 review will be withheld from the taxpayer-requester, the IRS may assert a number of FOIA exemptions to withhold the information. For example, correspondence or other information provided by the Joint Committee to the IRS for the latter’s consideration before issuing the refund or credit may be withheld on the basis of FOIA exemption 5, which encompasses the deliberative process privilege. In addition, the FOIA exemption 7 law enforcement exemptions, as well as exemption 3 in conjunction with IRC §6103(e)(7), may be available if the case is pending at the time of the request. If the requester is a third party seeking such records without the consent of the taxpayer, such records are protected by FOIA exemption 3 in conjunction with IRC §6103(a).

11.3.13.5.4  (10-26-2007)
Imperfect Requests

  1. The FOIA requires requesters to reasonably describe the records sought. While compliance with the procedural regulations is also required, Disclosure personnel must take care not to read a request so strictly that the requester is denied information the agency knows exists. However, if the request is not specific enough to process or it is too broad in scope, including language such as "I request all records concerning me," or otherwise lacks specificity, it can be determined to be imperfect and closed accordingly. See IRM 11.3.13.5.8.

  2. Letter 1526, or similar format on word processing applications, can be used to notify the requester that the request does not meet certain requirements of the FOIA and that more information is needed before the request can be processed. The specific deficient item(s) must be pointed out to the requester. The letter must advise the requester that he/she has 35 calendar days to perfect the request. Requests that do not comply with FOIA regulations are to be closed as imperfect. Every effort shall be made to close requests deemed to be imperfect as soon as possible.

    Note:

    Responses to imperfect requests must not include Notice 393 because no appeal rights are available to imperfect requests. The response must include a statement that the 20 day response time does not begin until a perfected request is received.

  3. Requests should not be determined to be imperfect because they do not state an agreement to pay fees if, based upon the information requested, it appears a fee would not be charged.

    Note:

    However, if the requester has an outstanding unpaid bill for any request(s) previously processed by the IRS, the current request will be considered imperfect, even if it appears no fees will be charged. The requester should be notified that no further requests will be processed until the balance due is paid in full. IRM 11.3.5.5.4(1).

  4. Notwithstanding any imperfection under FOIA, if records can be provided to requesters that they would be otherwise entitled to receive under the provisions of IRC §6103(e), and no FOIA fees are applicable, the records should be provided. An exception to this is when the request should be processed under an existing Agency procedure. See IRM 11.3.13.5.13, Routine Established Agency Procedures.

    Example:

    Even though the request fails to prove identity, if the request is for a transcript of account or other tax information that can be provided using authentication standards appropriate for the type of product requested under IRC §6103(e), the inclusion of this information should be made part of the response. See IRM 11.3.2 and IRM 21.1.3, Accounts Management and Compliance Services Operations - Operational Guidelines Overview, for authentication standards. If records are provided, be sure to indicate in your transmittal letter that the request is invalid under FOIA, but that records are being provided under another statute and state the governing statute that allows release. Appeal rights are not available for imperfect FOIAs.

    Note:

    These requests must be logged on the inventory management system as FOIA requests. A closing code "E" has been established on the inventory management system for cases citing the FOIA where records are released under IRC §6103(e).

  5. If providing information under (4) above would require more than a minimal amount of review and/or redaction, the request should be closed as imperfect. The closing letter should identify the specific information required to perfect the request. It is especially important to perfect the request and process it under the FOIA in situations where processing under IRC §6103(e) would provide no appeal rights and would cite no FOIA exemptions for redacted material.

    Note:

    Where the IRS has established a strong legal precedent for withholding information (e.g. a DIF score on an AMDISA print or return information of a spouse filing a separate return on a transcript), the information may be deleted and the redacted document provided under IRC §6103(e). However, the deletion shall be explained in the response letter, even though no appeal rights are offered. Systemic IRC §6103(e)(7) redactions require no additional approval by an official with IRC §6103(e)(7) withholding authority under Delegation Order 11-2.

  6. Verbal communication with the requester may be used to clarify the request or to ask for missing information necessary to process the request. Such verbal communication must be documented in the history notes.

  7. If the request cannot be processed, to assist the requester in perfecting it, the requester shall be informed, as applicable:

    1. The IRS does not maintain central administrative or compliance files

    2. Proof of identity is required if the request involves access to tax or Privacy Act covered records (e.g. personnel records)

    3. A firm commitment to pay fees must be made if the request is expected to result in a fee or

    4. Of any other items lacking in perfecting the request

  8. In some instances, it may be necessary to mention that the FOIA does not require agencies to answer questions, enter into doctrinal discussions, create records, or perform research. See IRM 11.3.13.5.10 for more information relative to responding to interrogatories.

    Note:

    Transferring data into or out of electronic format, including printing information retrieved from IDRS through input of a command code, does not constitute creating a new record.

  9. Requesters shall also be informed of the types of records maintained by the IRS, e.g. records concerning examinations of returns, collection actions, and criminal investigations. Inform the requester that perfected requests must include a specific reference to the types of records and tax years being requested.

  10. When the requester submits the information necessary to perfect a request or makes the payment necessary to eliminate an unpaid balance, the request shall be processed promptly. (See IRM 11.3.5, Fees, for related actions concerning fees.) A new case file shall be opened rather than re-opening the imperfect case. However, it may be necessary to read all newly supplied information and the previously imperfect request together, as not all requesters will repeat all the elements required to constitute a perfected request.

    Caution:

    Care should be taken not to make further demands upon the requester if reference to previous correspondence provides enough information to process the request.

11.3.13.5.5  (01-01-2006)
Requests Addressed to More Than One Disclosure office

  1. IRS offices may receive requests (other than imperfect requests, See IRM 11.3.13.5.4), which appear to be copies of requests addressed to other IRS offices. These requests may be identified as copies by their appearance.

    Example:

    The requests may have a primary address other than that of the receiving office, may be photocopies, or may not have an original signature.

  2. Offices may also receive a request where more than one office address is listed, which indicates possible duplicate FOIA requests have been submitted.

    Note:

    Where this occurs, the inventory management system must be checked for duplicate requests during the initial analysis of the case. There may be a need for this research in other circumstances, such as when multiple requests are received in a single office or the caseworker becomes aware that multiple requests may have been made while processing the request.

  3. Receiving offices must conduct adequate IDRS research to identify if the records requested exist and/or are obtainable. If the records exist, IDRS will show where they are located.

  4. Research of the inventory management system must be conducted to determine if there is a match on the name and identification number shown on the request. If a match is found, contact shall be made with other receiving office(s) to determine the appropriate action.

  5. Requests seeking the same information addressed to multiple offices should be consolidated in one office for a response to eliminate repetitive work. Generally, in these situations, the Disclosure office having jurisdiction over the taxpayer's address should be the responsible office. However, when another office has already initiated processing, or has jurisdiction over the largest collection of responsive documents, that office may be the responsible office.

  6. After it has been determined who will be the responding office, all other offices should close the case as a transfer. The office making the response will advise the requester as to which offices are included in the response and will inform him/her to submit future requests to the Disclosure office serving the requester's geographical area of residence.

11.3.13.5.6  (10-26-2007)
Requests for Records of Other Treasury Components or Other Agencies

  1. The procedures for handling requests for records which are in the possession of the IRS, but which were created by another Federal agency, are detailed in 26 CFR 601.702(c)(3). The FOIA request should be reviewed to determine if records requested are under the jurisdiction of the IRS. When a request explicitly seeks the records of another Treasury component or of a non-Treasury agency's records, the request shall be forwarded to the Baltimore Disclosure Office for transfer to the appropriate component or agency. (See IRM 11.3.2.5, Other Disclosure Authorities.) A letter should be sent to inform the requester of the forwarding.

  2. Sometimes a search for records responsive to a request locates records that originated in another Treasury component or in a non-Treasury agency. Records created by other Federal agencies or Treasury components shall be referred to the other agency, or component, for review, coordination, and concurrence. No determination will be made with respect to the record without prior consultation with the other agency or component.

    Note:

    This will also apply to records created by the IRS that include information that originated in another agency or Treasury component.

  3. However, if upon review it is determined that information is exempt from disclosure, in full or in part, based on IRS concerns, Disclosure personnel will process the records as usual and assert appropriate exemptions. Disclosure personnel shall inform the Baltimore Disclosure Office of the withholding; the Baltimore Disclosure Office will inform the relevant Treasury component or non-Treasury agency of the request and withholding. Any records that the IRS would disclose must be forwarded to the Baltimore Disclosure Office along with a copy of the request. The Baltimore Disclosure Office will transfer the request and the records for direct response to the requester. 31 CFR 1.5 and 26 CFR 601.702(c)(3).

  4. IRS field offices shall forward FOIA requests for records originating in other Federal agencies, including other Treasury components, to the Headquarters FOIA Office.

    Caution:

    IRS field offices may not seek disclosure recommendations directly from local offices of other Federal agencies.

  5. The field office may close its file on this request after informing the requester of the referral and responding with respect to all IRS records.

  6. The referral of a record to another Federal agency does not constitute a denial of access to such record. No appeal rights will be afforded the requester solely because a record has been referred to another agency.

    Note:

    When the responsible official has reason to believe that notifying the requester of the referral may cause a harm to the ability of the originating agency or Treasury component to withhold the records under 5 USC 552, then such notification will not be made. Such determination shall only be made in consultation with the originating agency or Treasury component.

11.3.13.5.7  (10-26-2007)
IRS Records Located in Other Agencies or Other Treasury Components

  1. IRS information is sometimes included in the files of other Federal agencies. When a FOIA request seeking access to those records is received by that agency, the IRS records are referred to IRS Headquarters FOIA office to consider. The Baltimore Disclosure Office will process these referrals.

  2. The Baltimore Disclosure Office will refer the records to the office having jurisdiction over the underlying activity to make a determination about whether the records can be released. This referral shall be made expeditiously.

    Note:

    Occasionally records are erroneously referred that did not originate in the IRS. When this occurs, the records shall be referred back to the originating agency through the Baltimore Disclosure Office. If the requester was notified of the transfer to the IRS, a letter shall be prepared informing the requester that an error was made and that the records are being returned for the consideration of the original agency.

  3. A referral from another Federal agency must be handled expeditiously, and a response issued to the requester directly from the office making the determination. All applicable FOIA procedures must be followed.

11.3.13.5.8  (01-01-2006)
Requests for All Records Concerning Me

  1. Usually, requests for "all records concerning me" or "all records containing my name" are not specific enough to process and must be rejected as imperfect. See IRM 11.3.13.5.4(6), IRM 11.3.13.5.8(5) and IRM 11.3.13.5.8(6).

  2. These requests must be thoroughly reviewed as they may contain minor references to records or enforcement actions that would help to identify the records requested.

  3. Requests containing enough information to permit a reasonable identification of records must be processed.

    Example:

    The information could include the function where the records may be found, the tax year or years involved, the type of tax, or the type and/or location of any investigation conducted by the IRS.

  4. Requesters sometimes attach copies of IRS notices, correspondence or other records to their requests.

    1. Attachments shall be carefully examined as they maybe helpful in processing the request.

    2. In the absence of any indication to the contrary, it may be assumed that the requester is seeking access to underlying files related to the attachment.

    3. Requesters need not provide their tax identification numbers, or specify the type of tax, tax year, or location of the records if such information can be determined from the attachments.

  5. If the request is not otherwise imperfect and does not specify tax years, then Disclosure personnel will consider the last three tax years when responding. See IRM 11.3.13.5.4 if the request is otherwise imperfect.

    Note:

    Where a response to a request is based on an analysis of the requester’s letter, any attached documents, and/or based on assumptions authorized under this section, the response letter must include an explanation of how the scope of the request was determined. For example, "Your request did not clearly indicate the type of tax or tax year for which you are seeking information. Based on the notices you submitted with your request, we are providing information regarding xxx for the years yyyy through zzzz" .

  6. If research reveals there is no open case or ongoing activity, the response shall state that a search of IRS records indicates that there is no open Examination, Collection, or Criminal Investigation case concerning the requester and consequently no records responsive to his/her request exist.

  7. If research reveals that an open case or ongoing activity exists, the response must generally state that no record maintained by the IRS appears to be specifically responsive to the descriptions in the request, but that an open case concerning the requester has been identified.

    Note:

    If IDRS research identifies either open or closed compliance activity, follow the procedures in IRM 11.3.13.5.4(7) through (9). If there is open criminal investigation activity, contact the special agent prior to notifying the requester to determine whether disclosing the fact of investigation could harm ongoing activity.

    Note:

    Depending upon the type of request, prior experience with requests from the requester, and other circumstances, the response must make available or withhold, as appropriate, the records identified, or the requester must be advised of the existence of files and how they may be requested if that is the requester's intent. Whether the availability of the case files is considered immediately or delayed until receipt of a further request will depend upon an analysis of the requester's intent, the adequacy of the request to extend to existing case files, and whether the anticipated costs would significantly exceed the requester's commitment to pay fees.

  8. When a request is received for records that do not exist because the record requested is one that is generated pursuant to a regulation or procedure that is not applicable to the requester, a general response will be provided to explain why no responsive records exist.

    Note:

    In the situations described in paragraphs (6), (7), and (8) above, Notice 393 must be enclosed. See IRM 11.3.13.8.2(2).

11.3.13.5.9  (10-26-2007)
Multiple or Repeat FOIA Requesters

  1. Disclosure offices commonly receive multiple requests for information from the same individual(s) over a short period of time or a large number of requests for information from the same requester all at the same time.

  2. These types of requests typically have one or more of the following characteristics:

    1. Begin with requests for transcript information, followed by multiple requests for tax information specific to most or all of the Document Locator Numbers (DLNs) found on those transcripts

    2. May be seeking various forms (each request seeking a different form) found in Examination, Collection, or Criminal Investigation administrative files

    3. Request multiple items (e.g. more than 30) followed by other requests seeking specific information already responded to in prior request(s), yet worded in a different manner

  3. These requests can impact on IRS resources and offer unique challenges in researching and securing requested records. As a result, Disclosure offices should plan an appropriate strategy to respond to the various requests received. The strategy should include the following:

    1. Assign, if at all possible, all requests to the same caseworker. This will allow the caseworker to review each request for duplications, to plan a strategy to address all requests as expeditiously as possible, and to build a history with the requester in the event of future requests.

    2. Complete adequate IDRS research to determine whether requested records exist and can be retrieved. Proper review of IDRS research will establish the scope of the search for responsive records. The response time and the effort expended may be lessened if, upon review of the tax situation of the requester and the records being requested, it becomes clear that records will not exist.

      Example:

      Numerous requests are received for copies of examination administrative files or for forms that would be included in those files. IDRS research indicates there has been no examination activity for the years requested. Further search need not be conducted and a no records response can be generated.

      Note:

      However, if future requests are received that seek the same or similar information, new research would have to be conducted to ensure that no examination activity has taken place in the interim.

    3. If the requester has made prior requests and those files are available, they must be reviewed to determine if a response has already been given for the records being requested.

      Example:

      You receive a new request for information related to a DLN associated with a transaction code 300, which is an examination administrative file. In reviewing prior files you note that the file for the requested year was provided in response to a previous request for "all examination administrative files." If that DLN predates the previous request, you can close your case by providing a copy of the prior response. No additional search is required. You must check all requests for possible duplications. Requests that seek the same records using different terminology, can be combined and only one search for records conducted. Example: You receive a request for "assessment records" and one for "23C or RAC006 records." These requests are for the same information and require only one response.

      Note:

      Both requests must be logged on the inventory management system. A single response letter should be prepared with reference to both requests.

  4. As with any FOIA request, Disclosure shall attempt to respond as fully and completely as possible by conducting adequate research to determine if records exist, performing a complete search for responsive records, and fully explaining the determination made.

  5. It is possible to respond to multiple FOIA requests in the same determination letter. There is no requirement that a separate letter for each request be provided, but every FOIA request must be addressed.

    Example:

    You receive 5 FOIA requests for different DLNs where it was determined that no records exist. You can draft one response letter to address all 5 requests rather than separate letters for each request.

  6. Any document associated with a DLN, including the Form 5147, is responsive to a request for "all forms associated with" a particular DLN, and must be retrieved and considered when responding to the FOIA. The DLN must be requested unless research clearly indicates that there would be no document, even the Form 5147. If the DLN is not requested, the case history shall contain a thorough explanation of how the caseworker determined no document would exist. See IRM 11.3.13.9.30.See IRM 11.3.13.9.30.

  7. If one letter is used to respond to several FOIA requests, a copy of that signed letter must be included in each FOIA case file and appropriate case history notes created in each file to document the fact that several requests were combined in one response.

11.3.13.5.10  (10-26-2007)
Pseudo Requests

  1. If the request is otherwise valid, it must be analyzed to determine whether it is merely citing the FOIA while not conforming to its intended purpose and cannot be processed by locating, analyzing, and releasing records.

  2. Some characteristics which may assist in recognizing pseudo-requests;

    • The individual tends to ask questions rather than request records.

    • Questions are frequently phrased in an accusatory or misleading manner, so that they appear to be intended to serve as harassment rather than to seek access to existing agency records.

    • The correspondence consists of, or imitates, form letters and may be part of a coordinated campaign involving similar requests from different requesters.

    • The letters may contain references to constitutional rights, or obscure matters concerning one or more of the following:

      1. Challenges to the authority of Title 26 or of the IRS -- The requester may argue that Title 26 of the United States Code is not law because it was never enacted as named. They may also argue that other laws or documents prevent the IRS from assessing and collecting tax.

      2. Constitutional arguments -- The requester may argue that income taxes are not valid because of the 5th, 13th or 16th amendments to the Constitution.

      3. IRC §861 arguments -- The requester may argue that IRC §861, or regulations thereunder (26 CFR 1.861), indicates that wages are not taxable.

      4. Arguments that the requester is not a person subject to tax within the meaning of the IRC or that taxes are voluntary.

      5. Arguments that the requester should be "untaxed" by withdrawing his/her Social Security Number and claiming sovereign immunity.

        Note:

        Any requests for records included in the correspondence are usually extremely extensive, poorly described, incorrectly addressed or otherwise written so as to make it difficult to respond. The objective may appear to be to force a denial rather than to actually obtain access to any records.

  3. Requesters may sometimes ask for all records concerning or serving as background materials for certain "Decisions" or "Determinations" concerning themselves. Some of the descriptions frequently encountered are:

    1. "…that I am a person required to file a tax return."

    2. "…that I didn't file a tax return."

    3. "…that I am a person as defined by the Internal Revenue Code."

    4. "…that my commercial activity or employment is taxable."

    5. "…that classifies my job description as a taxable activity for revenue purposes."

    6. "…that I am an employee or an employer or an individual engaged in a trade or business as a sole proprietor."

    7. "…that I received diversification of corporate profits."

    8. "…that I am required to possess a Social Security Number absent any income derived from any source."

    9. "…that discloses that I am a fiduciary of a trust or estate."

    10. "…that a "substitute for return" has been or will be prepared for me."

  4. In order to make an appropriate response to a pseudo-request, it is necessary to clearly distinguish between the portions of the correspondence which constitute valid FOIA requests and those portions which consist of hyperbole and questions.

  5. The FOIA does not require agencies to respond to questions, create records not already in existence in some format, or engage in doctrinal discussions with requesters.

    Note:

    Printing an electronic record to paper, or scanning a paper record to PDF, does not constitute creating a record not already in existence.

    Example:

    A request for a paper copy of an electronic audit trail should be processed. A request to create a list of employees who worked on an examination file need not be honored.

  6. Pseudo-requests should not be permitted to drain Disclosure resources needed to administer the FOIA and other programs. They must, however, be responded to in a fashion consistent with statutory requirements and in a tone appropriately reflecting a spirit of openness in government.

  7. Upon receipt of one of these letters, it must be carefully reviewed to determine whether it seeks information under the FOIA or other governing statute. Reference to the FOIA may be buried many pages into the document. A mere reference to the fact that the FOIA requires a response within 20 days, or inclusion of "FOIA" on the envelope, may be sufficient to consider the letter a request under the FOIA. See IRM 11.3.13.5.11(2) regarding unclear requests.

    Note:

    The request does not need to be "perfected" under FOIA to allow us to respond under IRC §6103(c) or (e) where those standards of entitlement/identification have been met. See IRM 11.3.13.5.10(8)(c).

  8. For correspondence that contains indications of any anti-tax argument, yet contains sufficient information to be considered a request for records under the FOIA or other statutory provision, the following steps must be taken:

    1. If the request is imperfect, work the case in accordance with procedures in IRM 11.3.13.5.4.

    2. If it is a valid FOIA request, secure the records being requested, process them according to FOIA procedures, and include in your response the information discussed in (9) below to address the frivolous arguments included in the correspondence.

    3. If it is not a valid FOIA request, yet information could be provided under IRC §6103(e) or IRC §6103(c), secure the information that can be released and include the information listed in (9) below to address the frivolous arguments included in the correspondence. See, however, IRM 11.3.13.5.13 for records available under routine agency procedures.

  9. In order to address frivolous arguments that are contained in a request for records, you must insert the following language in your response letters:

    ''Your letter also contains questions or indications that you are challenging the income tax system. Federal courts have consistently ruled against a number of arguments challenging the constitutionality of income taxes or the authority of the IRS to enforce the tax laws or collect taxes. To address these concerns and for your information, please find enclosed a copy of Publication 2105, Why Do I Have to Pay Taxes? In addition, there is information on the IRS website which answers various anti-tax arguments entitled: The Truth About Frivolous Tax Arguments, at: http://www.irs.gov/pub/irs-utl/friv_tax.pdf. We will not respond to future correspondence concerning these issues.''

    If the taxpayer is a frequent FOIA requester, and includes the same or similar questions in subsequent requests for records, there is no need to provide another copy of Publication 2105.

  10. If you have done IDRS research and there is evidence of open examination, collection, or criminal investigation activity, you must provide a copy of the request letter and the response to the compliance function(s). Requests may have been submitted because the requester intends to introduce the request or the response in some litigation. They may also be helpful to government counsel in establishing or illustrating the taxpayer's intent and attitudes.

  11. Correspondence that does not request records in accordance with the FOIA or other statutory provision, 26 CFR 601.702(c), or IRM 11.3.13.5, and only seeks responses to questions, shall be forwarded to the following address:
         Internal Revenue Service
         Ogden Campus Frivolous Return Program
         1973 N. Rulon White Boulevard
         Mail Stop 4450
         Ogden, UT 84404

    Note:

    The Frivolous Return Unit will generate appropriate letters to the requester in accordance with its procedures.

    Caution:

    This unit must not be used as a means of managing inventory; only those letters that are clearly not seeking records under FOIA or other statutory provision should be sent to them.

  12. Scheduling an inspection of records in response to a request for open investigatory files located in compliance functions should be coordinated with those functions. The presence of the requester in an IRS office may provide a convenient opportunity to make contact for tax administration purposes. Enforcement personnel may be present for such inspection, bearing in mind the rules and restrictions governing communications with taxpayers who have representatives before the IRS. See IRC §6304.

11.3.13.5.11  (01-01-2006)
Unclear Requests

  1. Upon analysis, it may be unclear which statute the requester is using to seek access. The following variations may be encountered.

    1. The request cites neither the FOIA nor the Privacy Act.

    2. The request cites both the FOIA and the Privacy Act.

    3. The request cites one Act, but the content of the request appears more appropriate to the other.

  2. Any lack of clarity as to which statute is applicable shall be resolved as closely as possible with the requester's stated intent, consistent with the law.

  3. When the request cites neither the FOIA nor the Privacy Act:

    1. Review the request for any other reference to the statute or accompanying regulations which may provide additional information regarding the requester's intent.

      Example:

      A request may simply state the statute such as 552 for the FOIA or 552a for the Privacy Act, or may state the request is being made under 601.702(c) or 31 USC Part 1, Subpart A or C, which are the FOIA and Privacy Act regulations issued by the IRS and Treasury, or there may be the letters "FOIA" on the envelope.

    2. Determine if records can be provided under a routine established agency procedure as set forth in 26 CFR 601.702(d), or under some other statute. The request should be classified as that type of request and records provided under those provisions ( See IRM 11.3.13.5.13).

    3. Requests for tax returns and return information may be directed to a Service employee involved in open compliance activity. If the request does not cite the FOIA or Privacy Act, it may be handled by that IRS employee, consistent with Delegation Order 11-2.

  4. When a request cites both the FOIA and the Privacy Act, and it is from:

    1. A first party individual seeking access to his or her own records, the request shall be classified under the statute that allows the greatest access. The FOIA generally provides the greatest access.

      Example:

      Requests for records contained in an Examination administrative file, which is in a system of records that is exempt from access provisions of the Privacy Act, shall be classified and processed under the FOIA.

    2. A third party or from an individual seeking records that are not maintained in a system of records, classify as a FOIA request.

      Example:

      Requests for a delegation order, IRM, or Forms 23C, which are not maintained in a system of records. These records statutorily fall outside of the Privacy Act, but access must be granted to the extent possible under the FOIA.

  5. In situations where the requester cites the Privacy Act, would get greater access under the FOIA, but insists upon processing pursuant to the Privacy Act:

    1. Control the case as a Privacy Act request, but provide the records that would be available under the FOIA as well as any records that are available under the Privacy Act. The response letter must cite Privacy Act Section (t)(2) and request any applicable search and duplication fees in accordance with FOIA fee provisions. See, IRM 11.3.5.4.3 and IRM 11.3.5.9.1 for a discussion about charging fees to first party requesters.

      Note:

      A first party requester is an individual seeking access to his or her own records that are maintained in a Privacy Act system of records. A party seeking access on behalf of an individual (e.g. as authorized by Form 2848 or Form 8821) meets the definition of first party requester.

    2. If records are to be denied, the applicable FOIA exemptions and the Privacy Act exemption for the system of records must be cited in the response letter.

      Note:

      In applying the above provision, a requester cannot be denied access to records under the Privacy Act unless there is a corresponding exemption under the FOIA that would prevent release of the requested record(s).

  6. Because the Privacy Act only applies to individuals, a request from a non-individual (e.g. a corporate officer requesting information related to Form 1120 citing only the Privacy Act shall be closed as imperfect.

    Note:

    Remember that a sole proprietorship is considered an individual under the Privacy Act.

  7. These instructions are not intended to require that matters which can be processed under the established agency procedures set forth in 26 CFR 601.702(d) be treated as FOIA requests. ( See IRM 11.3.13.5.13)

  8. In some cases, a single letter may contain some requests that are made pursuant to the FOIA and meet the procedural requirements of that Act, and other requests that are made pursuant to the Privacy Act and meet the procedural requirements of that Act. These requests must be treated as if both Acts were cited. For control purposes, they will be classified as a FOIA request.

    1. For these instances, the request must be considered a split request so each portion may be afforded proper treatment, appeal rights, and the correct application of fees.

    2. To the extent practicable, responses to such requests must distinguish the portions processed pursuant to each Act and the reasons for such treatment. For any records that are withheld, the response letter must cite both the FOIA and Privacy Act system of records exemptions that support the denial of records.

      Note:

      The instructions above are not intended to require Disclosure personnel to distinguish between FOIA and Privacy Act requests in situations where there is little or no significance to such distinction, such as when all requested records may be readily available and releasable and the differences in costs are minimal.

  9. Regardless of which Act is cited, the request must satisfy the procedural requirements of the applicable Act and the commitment to pay fees must encompass the services being requested.

    Note:

    A request which entails FOIA search fees because it seeks records that are not maintained in systems of records, but contains an agreement only to pay Privacy Act (duplication) fees, is imperfect if it is anticipated that the resulting fees may exceed the commitment to pay (i.e., more than 2 hours of search will be involved).

    Exception:

    FOIA search fees do not apply where first party requesters are seeking records about themselves that are maintained in systems of records. Only Privacy Act (duplication) fees apply (26 CFR 601.702(f)(3)(E)(iv)(C)). See IRM 11.3.5 for further information about fees.

11.3.13.5.12  (01-01-2006)
Transferring Requests

  1. Once it is controlled on the inventory management system, the FOIA request shall be analyzed for indications that the requester is seeking access to records located elsewhere. In addition, IDRS research must be reviewed to determine whether responsive records are located in another office. ( See Exhibit 11.3.13-1 for IDRS research guidelines.) If this is the case, Disclosure personnel must:

    1. Respond to requests for (a)(2) materials that are available on the internet by referring the requester to: http://www.irs.gov/foia/article/0,,id=110353,00.html

    2. Respond to requests for (a)(2) materials that are not available on the IRS.gov website but are locally available, such as local delegation orders before transferring and

    3. Transfer only those requests (or portions thereof) seeking access to (a)(2) materials that are not available locally or on the internet and (a)(3) materials, such as tax information of the requester. If the information can be provided by the initial receiving office, such as a transcript of account, the request should not be transferred

      Note:

      Where the initial office receives a request that is misdirected from a mail or other processing unit located in another geographical location (for example, FOIA requests erroneously sent to the Ogden Frivolous Filer Unit and forwarded to the Ogden Disclosure office), it shall immediately be forwarded to the Disclosure office that has jurisdiction over the requester’s address.

  2. Requests deemed to be imperfect will not be transferred; the receiving office shall respond accordingly. See IRM 11.3.13.5.4.

  3. If the request appears to seek access to the requester's own tax information, the initial receiving office will perform the necessary research to determine if open or closed case files likely to be responsive to the request exist.

  4. Research will be limited to IDRS or other readily available tools. It is not intended that time consuming inquiries to master files or retention files be undertaken.

  5. If research shows no such cases exist or the request seeks records that will not pertain to the requester's tax situation, the initial recipient shall make a final response on that basis. If the requester resides in a geographical location that is served by another Disclosure office, the receiving office will provide the address of the office that will normally process his/her request in its response letter.

  6. If the request appears to seek access to records whose disclosure is prohibited or which are known not to exist, the initial receiving office will make the final response, citing the proper exemption(s) or closing the case based upon a "no records responsive" determination. If the requester resides in a geographical location that is served by another Disclosure office, the receiving office shall provide the address of the office that will normally process his/her request in its response letter.

  7. If a request is determined to be imperfect, the initial receiving office will respond to the requester and provide information on how the request may be perfected. If the requester resides in a geographical location that is served by another Disclosure office, the receiving office shall provide the address of the office that will normally process his/her request in its response letter.

  8. If the request involves access to open or closed compliance files or other complex or technical matters outside the initial receiving office's jurisdiction, transfer to the office with control over the records shall be considered.

    Note:

    Generally, the office with control over the records will be the office in which the administrative action (an examination, collection action, criminal investigation, the assertion of a penalty, etc.) occurred, regardless of the requester's current address.

  9. Even if it is determined that the case could be transferred, the initial receiving office must respond if the information requested is readily available to any Disclosure office by use of appropriate research and search techniques and does not involve an open or closed compliance or other complex file. This will help to avoid unnecessary transfers and to provide prompt service to requesters. However, see the note in IRM 11.3.13.5.12(1) regarding misdirected correspondence.

    Example:

    In response to a request for records associated with a document locator number (DLN) assigned to the original return, provide a copy of Form 4506, Request for Copy of Tax Return, with directions to file the form with the appropriate IRS Campus to obtain a copy of the return.

    Example:

    The DLN represents an automated transaction for which no paper or electronic record exists, other than the transcript previously provided to the requester. The response shall inform the requester of this and advise there are no responsive records.

    Note:

    If a Form 5147 exists, it is a paper document associated with the DLN and must be retrieved in response to a request. See IRM 11.3.13.9.30.

    Example:

    The DLN relates to a non-complex item or processing record. The initial receiving office will secure the record(s) and respond accordingly.

  10. The Headquarters Office will transfer requests to the office of proper jurisdiction based upon the Headquarters Office Disclosure personnel's knowledge of the types of records being requested and the geographical boundaries of the various Disclosure offices. Transfers will generally be based on the office having jurisdiction for the address of the requester.

  11. Prior to transferring any request, the initial receiving office must telephone the office to which transfer is proposed to make certain the transfer is appropriate, and shall document the case file accordingly.

  12. Whenever a request is transferred, the requester shall be advised of the transfer by the initial recipient office, and both the response to the requester and the transmittal memo to the transferee office must clearly identify the portions of the request which have been resolved and the portions which remain unresolved.

    Note:

    If the initial receiving office is expected to release or has released records in sufficient number to result in the assessment of a processing fee, the office accepting the transfer will be so advised in the transmittal memo to allow for proper billing for additional records provided.

  13. If a transfer is accepted and the request is later determined to be imperfect, the transferee office will respond to the requester and coordinate the response with the initial receiving office.

  14. When a requester properly sends a FOIA request to the office having geographical jurisdiction over his/her address in accordance with instructions in 26 CFR 601.702, and the request is subsequently transferred, either for the purpose of balancing inventories between offices or because the records are under the jurisdiction of another office, the received date is the date the request was initially received in the office having geographical jurisdiction, per 26 CFR 601.702. When the request is input by the initial receiving office, the inventory management system received date must match the date of initial receipt, and all statutory time frames begin as of that date. It is imperative that inventory transfers be handled expeditiously, so that the transferee office will have time to complete all administrative processing within the statutory time frames. Where the transfer is delayed, statutorily required extension letters must be sent by the initial receiving office prior to transfer. However, see note at IRM 11.3.13.5(6).

11.3.13.5.13  (01-01-2006)
Routine Established Agency Procedures

  1. Requests for records that can be processed routinely in accordance with the established procedures identified in 26 CFR 601.702(d) are specifically excluded from the processing requirements of the FOIA. Requests shall be analyzed to determine if they should be handled according to these procedures. These types of requests will not be diverted to the FOIA or Privacy Act simply because the requester cites these Acts. Disclosure personnel will respond to the requester by explaining that the request is not diverted to the FOIA simply by mentioning that Act and will be processed under routine agency procedures. Generally, the requester should be provided instructions on how to resubmit the request under the routine procedures. The request will be closed off the inventory management system using closing code "R."

  2. Routine established agency procedures will apply to requests for:

    1. Tax returns and attachments or transcripts. Use Form 4506, or Form 4506-T, Request for Transcript of Tax Return.

      Note:

      FOIA and/or Privacy Act requests for open investigation files that are received by an IRS employee in the course of an open investigation are to be referred promptly to the Disclosure office for processing. Tax returns and attachments that are contained in the open investigation files are to be processed pursuant to FOIA. Requests for access to open case files directed to compliance personnel may be processed outside of FOIA, even if they cite to the FOIA, if doing so is in the best interests of customer service and the function with jurisdiction is agreeable to providing the requested information. Since only Disclosure employees are delegated the authority to respond to FOIA requests, the requester must withdraw the FOIA request and agree to obtain the records directly from compliance personnel. Disclosure personnel will provide assistance as necessary if the function is planning to withhold information under IRC §6103(e)(7) due to an impairment determination. The functions should not insist a requester go through the FOIA process if the information could otherwise be provided through an informal process, consistent with Delegation Order 11-2. Requests for access to closed case files are to be processed under FOIA.

      Note:

      A request for a Substitute for Return (SFR) does not fall under the routine established agency procedures discussed in this section. In accordance with IRC §6103(b), an SFR is not considered a return, but return information.

    2. Records of seizure and sale of real estate, found on Record 21, Part 2, are open to public inspection. These may be made available in the Technical Services (Advisory) Unit that maintains the record based on the location of the property. The locations of the Technical Services (Advisory) Units are contained in Publication 4235, Technical Services (Advisory) Group Addresses, which is available at http://irweb.irs.gov/fpd/. A request for copies of Record 21, Part 2, must be processed under the FOIA. See IRM 11.3.11.9.1.

    3. Information returns, notices and reports of certain tax exempt organizations and trusts, political organizations, applications by organizations granted tax exempt status, applications for certain deferred compensation plans and accounts, and their annual returns. Access is granted through IRC §6104 via Form 4506-A, Request for Public Inspection or Copy of Exempt or Political Organization IRS Form, which must be provided to the requester.

      Note:

      See IRM 11.3.9, Exempt Organizations, and IRM 11.3.10, Employee Plans Information.

    4. Publication of statistics of income. Access is granted through IRC §6108(a) and 26 CFR 301.6108-1. Many statistical products are available to the public on the irs.gov website through the "Tax Stats" link at http://www.irs.gov/taxstats/index.html. Requests under 6108(b) for the IRS to conduct statistical studies or make statistical compilations must be made in writing and submitted to the Director of the Office of Research, Analysis and Statistics at Internal Revenue Service, 1111 Constitution Avenue NW, Washington, DC 20224. Attention: Statistics of Income Division RAS:S02. See the applicable revenue procedure for further instructions. Copies of statistical studies or compilations previously made under §6108(b) may be available upon written request to the above address.

    5. Public comments in rule-making.

      Note:

      See IRM 11.3.11.7, Comments on Proposed Rules and Regulations.

    6. Accepted offers-in-compromise (OIC) less than one year old (from date of execution).

      Caution:

      Requests for copies of accepted OICs that are more than one year old or where no inspection is involved must be processed under FOIA. Routine procedures allow for inspection and copying only, not for copies to be provided independent of the inspection process.

      Note:

      See IRM 11.3.11.8, Public Inspection of Accepted Offers-in-Compromise, for OICs less than one year old.

    7. Written determinations and background file documents under IRC §6110.

      Note:

      See IRM 11.3.8, Disclosure of Written Determinations, and IRM 11.3.13.9.1, for discussions regarding requests for written determinations.

    8. The Public Information Listing. ( See IRM 11.3.13.9.12(1)) OPM has designated certain personnel information as being routinely available to the public.

  3. If Disclosure personnel elect to process the request and no fees are involved, the response to the requester shall acknowledge that the records, while requested under the FOIA or Privacy Act, are routinely available under established procedures and are being provided under those procedures. The appropriate citation, 26 CFR 601.702(d), along with any procedures and the access statute under which the records have been disclosed, must be provided.

  4. Letter forwarding requests are also processed under routine established agency procedures (Policy Statement P-1-187) and are excluded from FOIA processing. See IRM 11.3.11.11.


11.3.13.6  (04-05-2002)
Search Process

  1. Upon determining that the request is valid in terms of meeting the requirements of the Act, Disclosure personnel must decide the scope of the request and to what extent a search for responsive records will be conducted.

11.3.13.6.1  (01-01-2006)
Documentation of Search Efforts

  1. When no responsive records are located, requesters may appeal the scope and adequacy of the search for responsive records. The logic behind search efforts shall be documented clearly in the case file either by history note, check sheet, or another readily understood method.

  2. In the majority of cases, the incoming request, transcripts, search memos, and the written response sufficiently document the file as to the search effort.

    Note:

    See IRM 11.3.13.6.2 below for a description of other data that may be necessary to properly document the file.

11.3.13.6.2  (01-01-2006)
Search Efforts

  1. Disclosure personnel shall do as much as they reasonably can to ensure that they locate the documents the requester is seeking.

  2. The FOIA requires requesters to "reasonably" describe what is being sought. Disclosure personnel must be careful not to read a request so narrowly that the requester is denied information that the agency knows exists. Some requesters may have little or no knowledge of the types of records maintained by the Service where others have greater knowledge of what to request. See IRM 11.3.13.6.3(12) which addresses the interpretation of "intent" in terms of what the requester truly seeks.

  3. The amendments under the Electronic Freedom of Information Act (EFOIA) amend the definition of the term "record" to specifically include information in an electronic format. Therefore, the Service is required to make reasonable efforts to conduct searches for records in electronic formats and to provide records in any format requested if readily reproducible in that format.

  4. With respect to electronic format, records that are readily reproducible generally are those that can be printed, downloaded, or transferred intact to a floppy disk, compact disk (CD), magnetic tape, or other electronic media using equipment currently in use by the office(s) processing the request.

  5. Disclosure personnel need to understand the types of records that may exist in the various functions in order to ensure an adequate search has been completed. Disclosure personnel may rely on their organizational knowledge, computer research, search memoranda, and any other resource available to determine how best to locate records responsive to the request.

  6. When a request is submitted for records identified by DLN, to the extent the request also provides the tax form and tax period for those records, Disclosure personnel shall attempt to locate the responsive records. The tax form and tax period are needed by Disclosure personnel to perform adequate research to ensure the records are related to the requester prior to ordering the documents. The requester does not need to provide the IDRS transaction code associated with the DLN in order to respond to the request.

    Note:

    DLNs are especially vulnerable to typographical and transposition errors. Therefore, it is especially important to confirm the documents retrieved when ordering a DLN belong to the requester prior to release.

  7. If it can be readily ascertained (without additional research) that the requested record is a computer-generated record for which no paper or electronic copy is maintained, the requester shall be so advised. See IRM 11.3.13.9.30.

  8. Some requests seek records from a certain time period to the "present." The "present" must be interpreted to be the date the request is received by the responsible office. Records created after the date of the search are generally considered outside the scope of the request. See 26 CFR 601.702(c)(8).

    Note:

    For a discussion of when Disclosure personnel may elect to include data outside the scope of the request See IRM 11.3.13.6.3(13).

  9. Disclosure Managers shall endeavor to meet both the letter and spirit of the statutes governing the FOIA process by applying a liberal interpretation of the scope and intent of the requester. It may be necessary to communicate with the requester to clarify what is requested as well as with those employees conducting the search. It is inappropriate to hold frequent requesters or professionals to a higher standard of exactitude because "they should have known better" or "they know the law, so we shouldn't read anything into the request" while giving the "benefit of the doubt" to first time or infrequent requesters. The aim of the FOIA process is to provide consistent, top quality service to all requesters.

11.3.13.6.3  (10-26-2007)
Adequacy of Search

  1. The Disclosure Manager is responsible for ensuring the adequacy of search efforts. See IRM 11.3.13.3.1. and IRM 11.3.13.3.2 above outline the roles of the Disclosure Manager and the Functional Coordinator in completing the search.

  2. The following information must be either apparent or documented in the case history notes:

    1. Which offices were contacted and why

    2. Person spoken to in each office and who conducted the search

    3. Files searched

    4. Search terms used

    5. Volume and location of records found and

    6. Time spent in the search, copy, and review process

  3. In addition to the foregoing explanation of how the search was conducted, the Disclosure Manager should know, or have access to, how the records are indexed within all the operating divisions or functions.

  4. The request itself is the best source for ideas regarding where any responsive records may exist. Disclosure personnel shall carefully review the request and involve Functional Coordinators and other contacts in the various functions, if necessary, to determine the best course of action.

  5. In many instances, the request identifies the functional area or the employee that may have the responsive records. When the request involves tax records, it generally lists the tax periods covered. See IRM 11.3.13.5.11 pertaining to unclear requests when the tax periods are not provided.

  6. IDRS is the first step in the search for tax records, but may not be sufficient since certain types of investigations in the compliance divisions are not reflected on the IDRS printout.

    Example:

    Records relating to money laundering would not be identified from an IDRS search. Criminal Investigation Functional Coordinators need to search the Criminal Investigation Management Inventory System (CIMIS) in addition to IDRS for records under its jurisdiction.

    Note:

    Use of a search memorandum is recommended unless the request is very specific and the IDRS search reflects exactly what is requested. An example of such a specific request would be a request for a transcript for a specific tax return account.

  7. In the case of requests for other than tax records where the records requested indicate ongoing compliance activity, Disclosure personnel must consider doing an initial IDRS search to determine whether any open compliance case is in process. Occasionally, the requester’s purpose is to obtain a statement in a FOIA response letter that may aid the requester in litigation or enforcement activities. While the purpose of the request is irrelevant for FOIA processing purposes. See IRM 11.3.13.5.10(10) about notifying the affected functions about the request.

  8. See Exhibit 11.3.13-1. establishes guidelines for adequate research on IDRS. It should be used as a tool to establish the minimum required research on cases involving tax records. The exhibit is not all inclusive, however, and searchers must tailor the search on a case by case basis.

  9. Disclosure Managers must take steps to maintain a general awareness of other automated systems which could assist in the location of information. Such steps may include:

    1. Arranging to be kept informed by local Modernization & Information Technology Services management of new systems being developed

    2. Mentioning during disclosure awareness presentations that Disclosure has an interest in knowing how the new automated tools are being used by the functions; and/or

    3. Collecting a library of the news about the latest technological advances in the IRS so the Disclosure staff may research it when necessary

  10. When search efforts require going beyond the initial IDRS research, Disclosure personnel will make a request to appropriate offices for a records search. It should be in writing and provide guidance for conducting the search. Disclosure personnel should use a standard search request memo such as the sample shown in See Exhibit 11.3.13-2. The use of a standard search memo is a good tool to properly document the search effort. The same memo can be directed to various offices and shall include:

    1. A copy of the request that has been highlighted or otherwise marked to direct attention to the portion of the request that pertains to that function

    2. A request for suggestions of other areas that may have responsive records

    3. A reminder that the search must include electronic records

    4. A reminder that there is a requirement to provide electronic data in the format requested

    5. A response questionnaire assisting the function to document its actions and time spent on search, copy, and review (this also assists the Disclosure office in computing applicable fees and inputting necessary data to the inventory management system)

      Note:

      See Exhibit 11.3.13-3 for a sample response memo.

    6. A request for a recommendation for release of located records

    7. A response due date and

    8. A point of contact for a clarification or a request for more time to respond

    Note:

    The search memo may also, on a case by case basis, offer additional information that would assist the function in interpreting what is being sought.

  11. Search memos are a useful tool for control purposes and to ensure timeliness of responses. Search efforts shall be documented on E-DIMS, which also tracks search memo responses from the functions. Documented routine follow ups on overdue responses to search memos will prevent long periods of inactivity on FOIA cases.

  12. When determining the scope of records that may be responsive to a request, it may be necessary to evaluate a requester’s knowledge of IRS practices. Evaluating this level of knowledge will not be an exact science, and will generally be left to local procedures. A professional tax preparer who deals with the IRS on a continuing basis may request a specific record or a specific file by the proper terminology. In such a request, it is not necessary to increase the responsive data by including related data in the spirit of good customer service. On the other hand, a request from a taxpayer reflecting a limited knowledge of IRS procedures may require a broader interpretation even if the taxpayer uses a specific term. Occasionally, trends in requests which have been reported to Headquarters will trigger a national directive intended to achieve a level of consistency. The purpose of any directive issued will be to provide service that is more consistent to all requesters, not to penalize a particular type/class of requester. Examples include:

    1. An individual reflecting unfamiliarity with IRS procedures requests a transcript of his/her account on the "master file" , but he/she lists a tax period which has gone to retention. In such an instance, the microfilm data shall be considered responsive to the request, even though the records can be found on the retention register, instead of the "master file" .

    2. A CPA who is a frequent requester and is familiar with IRS procedures requests a complete transcript from system 24.030 CADE (Individual Master File) on behalf of his client. If the research shows that there is also retention data, then the response need not include the data from the Individual Microfilm Retention Register (22.032). If that same CPA, however, requests the IMF transcripts for a span of years that includes a year that has gone to retention, then he, too, must be given the microfilm data for the year removed to retention.

    3. A taxpayer representative familiar with IRS practices requests something specific like a Form X. He does not necessarily need to be provided the related Form Y or Z. See IRM 11.3.13.6.3(15) for discussion of the caution necessary in responding "no records" to certain requests which may be engineered for seeking just that kind of response.

  13. Records created after the receipt date of the FOIA request are outside the scope of the request and functions should be made aware of this fact. See 26 CFR 601.702(c)(1)(ii). In rare circumstances, a lengthy delay (e.g. 90 days) may be unavoidable before search efforts are initiated. If this occurs, the case history must be documented to explain the delay and the search period must be extended to the date of search. Also, when appropriate in terms of good customer service and/or in the spirit of openness in government, Disclosure personnel may make a determination to include records created after the receipt date of the request. This determination is to be made on a case-by-case basis.

  14. Typically, reading files need not be searched as they contain duplicates of agency records located in case or subject matter files. However, where official records are known to exist but cannot be located, reading files shall be searched for a substitute for the missing official agency record.

    Note:

    This instruction is not intended to require search of reading files if the official record should have been disposed of under routine destruction schedules (normal retention criteria). Destruction schedules may be verified with the local Area Records Manager (ARM). A directory of the local ARMs is listed on the REFM - Records Management Website located at the following website:   http://awss.web.irs.gov/facilities/RecordsMgmt/ARMListUpdate.htm

  15. When agency knowledge indicates that records responsive to the request would not exist, there is no need to perform futile search efforts. However, problems may arise when requesters are advised that no records exist in response to their requests. Examples include:

    1. Advising the requester that there are no records responsive to a request for "notice and demand" letters affords the requester the opportunity to challenge the validity of a lien or levy in the requester's substantive tax affairs. The requester must be advised that the Campus (or other office) does not routinely maintain hard copies of these notices, but an enclosed highlighted transcript of account reflects the issuance of these notices to the requester. Where these records are available (i.e., located in a collection file), they shall be made available to the requester, if within the scope of the request.

    2. Another area in which "no record exists" responses are being used by requesters in their substantive tax affairs deals with requests for the delegation order to a specifically named IRS employee that "authorizes him or her to file tax liens." Although it may be true that no delegation order to a designated employee by name exists, the more appropriate response would be: "delegation orders are usually not issued to employees by name, but rather are issued to employees by position title. The attached copy of Delegation Order _______ is the authority for _______ to file tax liens."

  16. Pursuant to 26 CFR 601.702(c)(14), Disclosure offices are required to maintain copies of all internal and external correspondence, including a copy of all signed and dated response letters, as well as the records identified as responsive to the request, or which may be deemed by a court to be responsive, in the FOIA processing case file. This case file must be preserved, notwithstanding otherwise applicable record disposition schedules, if the case is the subject of a pending FOIA request, administrative appeal, or lawsuit.

    Note:

    Search memoranda shall reference this regulation and instruct Functional Coordinators that correspondence between their offices and Disclosure offices, as well as the records deemed responsive to the FOIA request, must be preserved during the pendency of a FOIA request, administrative appeal, or lawsuit, notwithstanding record disposition schedules. Functional Coordinators should also be invited to discuss with Disclosure personnel any questions that arise concerning whether certain records are responsive, or may be deemed by a court to be responsive, to a particular FOIA request before record disposition schedules are followed. Whenever there are questions concerning the responsiveness of records, such records must be preserved, either by the Functional Coordinator or the Disclosure office, for cases that are the subject of pending FOIA requests, administrative appeals, or lawsuits. The Functional Coordinator and Disclosure Manager or Specialist will determine where such records will be maintained.


11.3.13.7  (01-01-2006)
Review and Editing

  1. Once the responsive records have been gathered, Disclosure personnel will review the material and determine what should be released or withheld in full or in part.

    Note:

    Disclosure personnel are responsible for determining what documents are responsive to each request. Disclosure personnel shall review documents provided by the functions to confirm that all responsive documents appear to be included and to set aside any non-responsive documents.

  2. The determination to grant or deny access to a specific record is made for each request on a case by case basis. It requires an understanding of:

    1. The purpose the record serves

    2. The relationship the record has to the objective of tax administration

    3. The effect disclosure of the record may have on the administration of taxes and

    4. The impact the disclosure of the information would have on the personal privacy of any individual weighed against the need for the public to have access to the information

  3. The determination also requires an understanding of the nine (9) FOIA exemptions, three (3) special law enforcement exclusions, applicable statutes, relevant court cases, precedents, and IRS-wide guidelines issued by Headquarters Governmental Liaison and Disclosure.

  4. The role of Disclosure personnel in this process is two-fold:

    1. To ensure the requester’s needs are addressed to the extent possible and

    2. To ensure confidential information or information that may harm tax administration, commercial or other institutional interests, or personal privacy is not released

  5. Generally, the advice of the function maintaining or originating the record requested weighs heavily in the determination regarding release of the information by Disclosure personnel. There are times, however, when the Disclosure Manager's interpretation of the facts of the case and the disclosure statutes may be different from the initial advice provided by the function. The ultimate responsibility for the disclosure resides with the Disclosure Manager pursuant to the disclosure authority outlined in 26 CFR 601.702 and, as appropriate, Delegation Order 11-2.

    Note:

    See IRM 11.3.13.3.2(3) for procedures involving disagreements with the affected function over the release of records.

  6. Disclosure Managers must make an independent judgment on the disclosure or withholding of records after considering the views of the affected functions and their understanding of the law. Disclosure personnel are responsible for balancing the two roles described in (4) above. They are also responsible for explaining the reasoning behind the final determination to withhold or release information. Some determinations are discretionary and some are clearly nondiscretionary by statute.

    Note:

    For a discussion of discretionary vs. nondiscretionary disclosures, See IRM 11.3.13.7.1.

11.3.13.7.1  (01-01-2006)
Approach to Exemptions

  1. The FOIA requires agencies to make the maximum possible information available to the public. In his October 12, 2001, FOIA policy directive to the heads of all Federal departments and agencies, Attorney General John Ashcroft expressed the Department of Justice's and the Administration's commitment to full compliance with the FOIA.

  2. The DOJ policy directive also expressed a commitment to protecting other fundamental values including protecting privileged communications, enhancing the effectiveness of law enforcement agencies, and preserving personal privacy.

  3. Under the FOIA, once a record is determined to be responsive, only such portion as falls within one of the nine (9) specific exemption categories or three (3) special law enforcement exclusions may be withheld. Disclosure personnel shall clearly document any decision to edit or withhold records. The decision must be made based upon the application of one of the exemptions or exclusions contained in the FOIA statute. Each of the exemptions and exclusions is listed and discussed in IRM 11.3.13.7.2.

  4. Some exemptions are mandatory in nature. Exemptions 1, 3 and 4 of the FOIA are exemptions for which discretionary disclosures are not appropriate since there are civil and/or criminal penalties for unauthorized disclosure of statutorily protected information.

  5. Consideration of whether discretionary exemptions should be asserted will usually be made on a case by case basis. See Policy Statement 11-13, Freedom of Information Act Requests, available at the following website:   http://www.irs.gov/pub/irs-utl/policystatement11-13.pdf.

  6. Decisions to withhold information protected under FOIA's discretionary exemptions shall be made only after:

    1. It is determined that the use of the exemption is on a sound basis both factually and legally and

    2. Full and deliberate consideration of "the institutional (i.e., public accountability, safeguarding national security, law enforcement effectiveness, and candid and complete deliberations), commercial, and personal privacy interests that could be implicated by disclosure of the information"

  7. When considering discretionary disclosures related to personal privacy, Disclosure personnel will weigh the public's right to the information against the privacy interests of the individual(s) affected. Case history notes shall fully document the reasons for the application of an exemption and include any discussions with the functions supporting that application.

  8. Records will not be withheld from the public simply because they may be subject to misinterpretation, because there is no apparent public benefit to their release, to avoid embarrassment, or to hide instances of errors or wrongdoing by IRS officials or employees.

  9. The designation of a record as "Official Use Only" does not preclude the release of the record pursuant to FOIA. See IRM 11.3.12.4, Guidelines for Classification, for additional information on "Official Use Only" determinations.

11.3.13.7.2  (01-01-2006)
Exemptions

  1. The decision to edit or withhold records is generally made based upon the application of nine specific exemptions. These specific exemptions are listed in 5 USC 552(b) and form the legal basis for the IRS to withhold records or portions of records from the public. Careful consideration of the exemptions is required when reviewing responsive records.

11.3.13.7.2.1  (04-05-2002)
Exemption (b)(1)

  1. This exemption applies to classified records concerning national defense and foreign policy. This exemption refers to information which has been or may be properly classified as confidential, secret, or top secret under the terms and procedures of the Executive Order establishing the classification system. It is seldom used by the IRS.

11.3.13.7.2.2  (10-26-2007)
Exemption (b)(2)

  1. This exemption covers matters that relate solely to the internal personnel rules and practices of an agency. Courts have interpreted the exemption to encompass two distinct categories:

    1. Internal matters of a relatively trivial nature (sometimes referred to as "low 2" information) and

    2. More substantial internal matters, the disclosure of which would risk circumvention of a law (sometimes referred to as "high 2" information)

  2. Under the 1986 amendments to the FOIA, law enforcement manuals and other sensitive information that could reasonably be expected to risk circumvention of the law, previously withheld under high (b)(2), will also be withheld under exemption (b)(7)(E). This includes computer security manuals and building evacuation plans.

    Note:

    Also assert FOIA exemption (b)(7)(F) in response to a request for building evacuation plans.

11.3.13.7.2.3  (01-01-2006)
Exemption (b)(3)

  1. This exemption protects information specifically exempted from disclosure by statute, provided that such statute:

    1. Requires that the matters be withheld from the public in such a manner as to leave no discretion on the issue or

    2. Establishes particular criteria for withholding or refers to particular types of matters to be withheld

  2. Some examples are:

    1. IRC §6103 (most commonly used)

      Note:

      The use of IRC §6103 as a supporting statute requires a determination that the information being denied is "a return or return information" as defined in IRC §6103(b)(2). When citing this exemption to deny the requester access to another taxpayer’s return information, a determination must be made that the information is the other taxpayer’s return information as defined in IRC §6103(b)(2). For example, information gathered in connection with the examination of Taxpayer A’s return includes DMV records of an individual with a similar name. Since the information was gathered in connection with the examination of Taxpayer A’s return, it is the return information of Taxpayer A. Since it was not obtained by the IRS with respect to determining the liability under Title 26 of the other individual named in the DMV records, it is not that individual’s return information, and thus cannot be withheld from Taxpayer A on the basis that it is the return information of another individual. FOIA exemptions (b)(3) in conjunction with 6103(e)(7), (b)(6), and (b)(7)(C) shall be cited in this situation. As another example, the taxpayer’s examination file contains records of the taxpayer’s expenditures for rent and office supplies. The identities and addresses of the landlord and the supplier(s), and the dates and amounts of payments to them, that were obtained to determine the taxpayer’s correct expenses are return information of the taxpayer. This information merely reflects a business relationship between the taxpayer and the landlord and supplier(s), and is not return information of the landlord or the supplier(s). Information about the business relationship cannot be withheld from the taxpayer as third party return information (although other exemptions may apply). Any notation in the file that explicitly refers to the tax matters of the landlord or supplier(s) must be withheld from the taxpayer as third party return information if the information is from IRS sources (including the caseworker). See IRM 11.3.13.7.5(3). See IRM 11.3.13.9.17 for a discussion of how the wording of the request may change the response.

      Example:

      A third party’s SSN provided by the taxpayer under examination would not be withheld; if the same SSN was retrieved from IRS sources it would be withheld.

    2. Rule 6(e) of the Federal Rules of Criminal Procedure exempts grand jury information

    3. 31 USC 5319 exempts currency transaction and certain other reports ( See IRM 11.3.13.7.6.

    4. 41 USC 253(b) relating to certain contract proposals ( See IRM 11.3.13.9.2)

    5. 5 USC 7114 (b)(4)(C) exempting labor management guidance (see the example in IRM 11.3.20.7.3 and

    6. IRC §6105 relating to tax convention information

  3. Generally, procedural rules are inappropriate as a basis for the (b)(3) exemption, except for those rules prescribed by law and having the effect of law such as Rules 6(e) and 16 of the Federal Rules of Criminal Procedure.

    Caution:

    Do not cite IRC §7213, IRC §7213A, IRC §7431, or the Privacy Act of 1974, as supporting statutes to the (b)(3) exemption.

11.3.13.7.2.4  (01-01-2006)
Exemption (b)(4)

  1. This exemption protects trade secrets and commercial or financial information obtained from a person that is privileged or confidential.

  2. The exemption is intended to protect the interests of both the government and submitters of information. Its existence encourages submitters to voluntarily furnish useful commercial and financial information to the government and correspondingly provides the government with an assurance that such information will be reliable and complete.

  3. The exemption also protects submitters who are required to furnish commercial and financial information to the government by safeguarding them from the competitive disadvantages that could result from disclosure.

  4. Requests for competitive bids for government contracts may fall in this category. These requests are seen more often in the Headquarters FOIA Office but to a limited degree, similar types of requests may be received by field personnel.

  5. This exemption relates to information submitted by individuals, corporations or partnerships. It does not apply to records which are generated by the government.

  6. 26 CFR 601.702(g) establishes certain notification and processing procedures for requests to which exemption (b)(4) might apply. This citation should be referenced as needed. For further information, See IRM 11.3.13.9.2.

11.3.13.7.2.5  (10-26-2007)
Exemption (b)(5)

  1. This exemption applies to inter-agency or interagency memorandums or letters that would not be available by law to a party other than an agency in litigation with the IRS: in other words, records that would be protected under discovery rules if they were part of a litigation.

  2. There are three primary privileges incorporated into exemption (b)(5):

    1. Deliberative process privilege

    2. Work product doctrine

    3. Attorney-Client privilege

    The Service’s assertion of these privileges in response to FOIA requests and any related discretionary determinations must be consistent with the application of these same privileges in the context of discovery.

  3. Deliberative process is the most commonly invoked privilege under exemption (b)(5). There are two fundamental requirements, both of which must be met, in order for the deliberative process to apply.

    1. The communication must be pre-decisional; that is, it precedes the adoption of an agency policy or other final decision and

    2. The communication must be deliberative; that is, play a direct part in the process of making recommendations or expressing opinions on legal or policy matters

    Note:

    Communications which precede a determination not to issue a decision, policy statement or published guidance, or with respect to which no final decision, policy statement, or published guidance has been issued, may be withheld under the deliberative process privilege if they meet these two requirements.

  4. The burden is on the agency to show the records meet both requirements. Records that reflect existing agency policy or reflect an interpretation of law already adopted by the agency should be disclosed because they are not pre-decisional, but discuss established policies and decisions.

  5. Generally, factual portions of internal agency records which may fall within the deliberative process privilege are not exempt from disclosure. However, if the facts are inextricably intertwined with deliberative matter, or selectively culled as part of the author's deliberations on the facts, they may be exempt.

    Example:

    Revenue Agent Form 4665 or "T-letters" transmitting information to Appeals are generally not exempt in their entirety, but must be reviewed to consider whether all, or part, of the record may be exempt.

  6. Disclosure personnel will withhold documents pertaining to published guidance (e.g. regulations, revenue rulings, revenue procedures, notices, and announcements), and those generated during the preparation of any statements of agency policy, or the preparation of interpretations adopted by the agency (e.g. Appeals Settlement Guidelines, Coordinated Issue Papers, IRM, etc.), when such documents are exempt from disclosure pursuant to discretionary discovery privileges or FOIA exemptions. The basis for this determination is twofold:

    1. To protect against public confusion that might result from the disclosure of various internal positions that do not reflect the grounds for the adoption of the guidance or policy that was published (or the decision not to publish at all)

    2. To protect against exposing the decision making processes of the Internal Revenue Service that would discourage candid discussion within these offices and undermine their ability to perform this critical tax administration function

  7. Work product privilege protects records prepared by an attorney or other Service employee during litigation or in reasonable contemplation of litigation. Generally, it does not cover records written by attorneys in the ordinary course of business (e.g. routine review of statutory notices of deficiency or summonses); it only covers those records which, under the particular facts and circumstances, were created primarily because of ongoing, or reasonably expected, litigation. A discussion with the Counsel attorney is required prior to release of any work product. Generally, discretionary FOIA exemptions for documents pertaining to these matters may be waived only by the Associate Area Counsel in consultation with the affected Service client at the supervisory level. For detailed instructions regarding who is authorized to make these determinations, see Chief Counsel Directives Manual (CCDM) 30.11.1.6, available at the following website: http://publish.no.irs.gov/IRM/P30/PDF/29184D05.PDF.

  8. Documents pertaining to litigation include not only documents prepared by Counsel Attorneys, but documents maintained in the administrative files of the Service to which the litigation pertains. The FOIA has sometimes been used as a discovery tool. Therefore, it is important that responses to FOIA requests be carefully coordinated with the Counsel employee responsible for the litigation. Good coordination will help to ensure that material which is privileged in discovery is also appropriately withheld pursuant to FOIA exemption 5, and that other material which could impair the government’s case is reviewed for withholding pursuant to applicable FOIA exemptions. Counsel employees will provide disclosure and withholding recommendations in accordance with CCDM 30.11.1.

  9. Attorney-client privilege protects confidential communications between an attorney and a client relating to a legal matter for which the client has sought professional advice. This includes communication from the client to the attorney and from the attorney to the client based on confidential information conveyed to the attorney by the client. The attorney-client privilege is not limited to communications pertaining to litigation or possible litigation. A discussion with the Counsel attorney is required prior to releasing any attorney-client communication. Discretionary FOIA exemptions for documents pertaining to these matters may be waived only by the Associate Area Counsel in consultation with the affected Service client at the supervisory level. See CCDM 30.11.1.

  10. Once it is determined that there is a sound factual and legal basis for asserting the exemption, a decision must be made about whether the IRS should exercise its discretion to not claim the exemption. Any decision to disclose information in response to FOIA requests shall be made only after a full and deliberate consideration of the institutional, commercial, and personal privacy interests that could be implicated by disclosing this information.

  11. Sometimes, Chief Counsel Advice or other written determinations are located in field compliance files. Since these documents are exclusively governed by IRC §6110, copies of these documents must be processed in accordance with that statutory scheme and not the FOIA. IRC §6110 requires the IRS to publish Chief Counsel Advice in addition to other written determinations (e.g. letter rulings, technical advice, and determination letters). Additional information can also be found at IRC §6110, IRM 11.3.8, Disclosure of Written Determinations, and at Chief Counsel Directives Manual 33.1.3, Releasing Legal Advice to the Public, and 37.1.1, Written Determinations Under Section 6110.

11.3.13.7.2.6  (01-01-2006)
Exemption (b)(6)

  1. This exemption pertains to the protection of personal privacy. It protects personnel and medical files and similar files, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. The first determination to be made is whether there is a protectible privacy interest that would be threatened by disclosure. Once it is determined that there is a privacy interest, this exemption requires a balancing between the individual’s right of privacy against the public’s right to be informed. The public interest to be considered in this balance is whether the information will shed light on government operations (the core purpose of FOIA).

  2. The phrase "similar files" as used in the (b)(6) exemption has been given a broad interpretation. The Supreme Court stated that Congress intended Exemption (b)(6) to cover detailed information on an individual which can be identified as applying to that individual, regardless of the type of file in which the information is maintained, rather than just a narrow class of files. This may include reports of reviews made of an office if the narrative portion of the review focuses on a named official or uniquely titled official whose operation is being evaluated.

  3. To accomplish the balancing of public interest and privacy interest, use the following formula:

    1. If no privacy interest exists - release the information

    2. If any protectible privacy interest exists - check for public interest

    3. If there is no public interest (or public interest is not the kind of interest that sheds light on how the government operates) - withhold the information

    4. If there is both privacy and qualifying public interest - balance the two interests with a leaning toward releasing the information

  4. Examples of items that are protected by this exemption are the real names of employees using pseudonyms, disciplinary action files, EEO complaint files, and employees' ratings of record.

  5. Exemption (b)(6) does not preclude the release of:

    1. Purely statistical information

    2. Staffing patterns

    3. Graphs of units closed or

    4. Overtime expenditures

  6. The FOIA Guide and Privacy Act Overview contains an in-depth discussion about how to apply this exemption. The information contained in this guide is available as two separate documents at the following website:  http://www.usdoj.gov/04foia/04_7.html.

11.3.13.7.2.7  (01-01-2006)
Exemption (b)(7)

  1. Exemption (b)(7) exempts from disclosure records or information compiled for law enforcement purposes, but only to the extent that the production of such records:

    1. Could reasonably be expected to interfere with enforcement proceedings

    2. Would deprive a person of a right to a fair trial or an impartial adjudication

    3. Could reasonably be expected to constitute an unwarranted invasion of personal privacy

    4. Could reasonably be expected to disclose the identity of a confidential source, including state, local, or foreign agency or authority, or any private institution, which furnished information on a confidential basis. In the case of a record compiled by a criminal law enforcement authority in the course of a criminal investigation, or by an agency conducting a lawful national security intelligence investigation, any information furnished by the confidential source is also exempt

    5. Would disclose techniques and procedures for law enforcement investigations or prosecutions or would disclose guidelines for law enforcement investigations or prosecutions if such disclosure could reasonably be expected to risk circumvention of the law or

    6. Could reasonably be expected to endanger the life or physical safety of any individual

  2. This exemption allows, but does not require, the withholding of records or information compiled for law enforcement purposes. It does not permit a blanket denial of records. Records may be edited or withheld only if the production of such records would cause one of the six specifically enumerated harms described above. The exemptions under (b)(7) apply to records generated out of civil and criminal judicial and administrative enforcement proceedings, and also apply to information that discusses investigations, such as certain Law Enforcement Manuals (LEM), guidelines and instructions to staff.

    Note:

    The first (threshold) requirement that must be met when applying any of the (b)(7) exemptions is to determine that the document or record in question was compiled for law enforcement purposes. If the record was not compiled for law enforcement purposes, the (b)(7) exemptions do not apply.

    Example:

    An agency’s general monitoring of its own employees to ensure that the procedures in effect are compliant with the agency’s statutory mandate and regulations does not satisfy the threshold requirement.

11.3.13.7.2.7.1  (01-01-2006)
Exemption (b)(7)(A)

  1. Exemption (b)(7)(A) exempts information in open or prospective law enforcement files. Information contained in records compiled for a law enforcement purpose is not exempt unless disclosure would harm a protected interest. Thus, records may be withheld if disclosure could reasonably be expected to interfere with enforcement proceedings. This will apply to any ongoing enforcement or concrete prospect of future enforcement proceedings.

  2. Records may be withheld if disclosure of information unknown to requesters might impede the investigation or harm the government's case in that particular or a related proceeding. A determination may be made to exempt a category of records in a specific case, without the necessity of completing a document by document review if the category of records meets the requirements for exemption described in (1) above. It is expected that withholding a category of records rather than doing a document by document review would be an infrequent approach based on very specific and compelling circumstances relating to individual enforcement matters. The following procedures and documentation are required if a determination is made to exempt the category of records.

  3. If a determination is made that disclosing the records to the requester will harm the investigation, written attestation must be prepared by the function having control over the records (usually CI), and provided to Disclosure. Disclosure personnel will include the attestation in the FOIA case file. The attestation must contain:

    1. Case agent name, title, and phone number

    2. Approximate volume of records (number of file cabinet drawers, boxes, etc.)

    3. Location of records

    4. Other contact name, title, telephone number

    5. Statement that disclosure of the records could reasonably be expected to interfere with enforcement proceedings and that copies of all records to be withheld from the requester are being provided at this time to the Disclosure Office or will be provided to the Disclosure Office if the requester files an administrative appeal or judicial complaint pertaining to the FOIA determination

    6. Assurance that the FOIA search request has been noted in the investigative file

    7. The signature of the Supervisory Special Agent (SSA), or Group Manager

    8. the concurrence of the Special Agent in Charge (SAC) or Territory Manager

  4. The Disclosure office will advise the requester that responsive records in an approximate volume are being withheld pursuant to FOIA exemption (b)(7)(A) and/or (b)(3) in conjunction with IRC §6103(e)(7).

  5. The function making the determination that disclosure could harm the government's case may provide a complete copy of the records being withheld to the Disclosure Office or must state in the documentation described above that a complete copy of the withheld documents will be kept available and will be provided if the requester files an administrative appeal or judicial complaint in the FOIA matter. IRS must be able to identify any documents withheld. Therefore, if the function does not provide copies of the withheld records to the Disclosure Office, it is imperative that the function clearly identify within its file which documents were withheld in response to the FOIA request, and that this identification be maintained for the life of the file. None of the withheld documents may be destroyed sooner than called for in the Records Control Schedule controlling FOIA records, and case documents developed/received subsequent to the FOIA request must be distinguishable from documents withheld.

  6. The function having control of an open and ongoing case should carefully weigh the administrative burden of providing the copies to the Disclosure Office with its response to the search request against the burden of maintaining the segregation within its file between the withheld documents and newer material added as the case continues. An issue to consider is the possibility that the requester will make additional requests for the file, which will require the function to separately identify the documents responsive to each FOIA request.

  7. Grounds for the nondisclosure of records include the harm in disclosing:

    1. Evidence

    2. The identities of witnesses and their prospective testimony

    3. The reliance placed by the government upon the evidence

    4. The transactions being investigated

    5. The nature, direction and strategy of the investigation

    6. The identities of confidential informants

    7. Information that would identify a witness or confidential informant

    8. The scope and limits of the investigation

    9. Methods of surveillance and

    10. The subjects of surveillance

  8. The Supreme Court has stated that the exemption may also apply when release of requested information would give the requester earlier and greater access to the government's case than he/she would otherwise have.

  9. This exemption is commonly applied to open Criminal Investigation, Examination, Collection, Appeals, and Counsel files. Prior to withholding any information, in conjunction with Functional Coordinators, Disclosure personnel must be able to determine the harm to the government's interest and articulate how release would interfere with enforcement proceedings. The file must be adequately documented to reflect this determination.

  10. Occasionally, exemption (b)(7)(A) can be applied to records in a closed case, where disclosure could reasonably be expected to interfere with unrelated open or future expected cases.

    Example:

    The amount of money actually spent in a sting operation may be withheld to prevent public knowledge of the agency’s resource limitations. This is distinct from exemption (b)(7)(E) because this is actual funds, not guidelines, procedures or techniques.

11.3.13.7.2.7.2  (01-01-2006)
Exemption (b)(7)(B)

  1. Exemption (b)(7)(B) protects against prejudicial pretrial publicity. This exemption provides for withholding if disclosure of the records would deprive a person of a right to a fair trial or impartial adjudication. This is primarily a protection against prejudicial publicity in civil or criminal trials. This is rarely used by IRS.

11.3.13.7.2.7.3  (01-01-2006)
Exemption (b)(7)(C)

  1. Exemption (b)(7)(C) protects personal information found in law enforcement records. This exemption protects from disclosure records or information compiled for law enforcement purposes the disclosure of which could reasonably be expected to constitute an unwarranted invasion of personal privacy.

  2. This exemption differs from exemption (b)(6) in that it requires a different standard for evaluating the invasion of personal privacy. It requires only a reasonable expectation of an invasion of personal privacy rather than a clearly unwarranted invasion of personal privacy.

  3. Prior to invoking this exemption, you must identify and evaluate the personal privacy interests implicated in the requested records. The Supreme Court held that whether disclosure is warranted within the meaning of the (b)(7)(C) turns upon the nature of the requested information and its relationship to the FOIA's central purpose of exposing to public scrutiny official information that sheds light on an agency's performance of its statutory duties. Disclosure personnel must balance competing personal privacy and public interests.

  4. This exemption only protects the personal privacy of individuals. Entities have no personal privacy. If the privacy or confidential information of a non-individual entity is at issue, Disclosure personnel must consider whether another FOIA exemption will properly apply to withhold the information.

  5. This exemption is commonly used to protect the identity of lower level Compliance employees at the Federal, state, or local level, names and other identifying information of taxpayers or other targets under investigation, and any witnesses or confidential sources interviewed. See IRM 11.3.13.9.10.

11.3.13.7.2.7.4  (01-01-2006)
Exemption (b)(7)(D)

  1. Exemption (b)(7)(D) protects the identity of confidential sources and, in criminal cases, the information the confidential source provided. This exempts from disclosure the name and any material which could reasonably be expected to disclose the identity of a confidential source. In criminal investigations, any information furnished by a confidential source, whether or not identifying, is exempt.

  2. The first part of this provision, concerning the identity of confidential sources, applies to any type of law enforcement record, civil or criminal. The term confidential source refers not only to paid informants but to any person who provides information under an express assurance of confidentiality or in circumstances from which such an assurance could be reasonably inferred. The factual basis for confidentiality, if not clear from the face of the records, shall be documented in the case file.

  3. A source can be confidential with respect to some items of information provided, even if other information is furnished on an open basis.

  4. Sources have been interpreted to include local, state, and foreign law enforcement agencies that provide information to an agency in confidence. This was codified by the 1986 amendments to the FOIA. It does not include Federal agency personnel.

  5. The second part of the provision applies to the information provided by the confidential source. Generally speaking, with respect to civil matters, such information may not be treated as exempt on the basis of exemption (D), except to the extent that its disclosure would reveal the identity of the confidential source. However, with respect to criminal investigations and lawful national security intelligence investigations, any information provided by a confidential source is, by that fact alone, exempt.

  6. Use of this exemption by itself provides an indication that a confidential source exists. It is recommended that use of this exemption be considered only where Disclosure personnel have confirmed, through consultation with the affected function(s), that the requester knows a confidential source exists and asserting the exemption is not likely to indirectly reveal the identity of the source. Where assertion of the exemption is believed to be inappropriate, (b)(3) in conjunction with IRC §6103(e)(7), (b)(7)(A), and (b)(7)(C) may be asserted.

11.3.13.7.2.7.5  (10-26-2007)
Exemption (b)(7)(E)

  1. Exemption (b)(7)(E) exempts from disclosure certain enforcement procedures. This exemption applies to records that would disclose techniques and procedures for law enforcement investigations or prosecutions, or would disclose guidelines for law enforcement investigations or prosecutions, if such disclosure could reasonably be expected to risk circumvention of law. Law enforcement manuals are clearly exempt from disclosure under this exemption.

  2. This exemption has been applied to protect Discriminant Information Function (DIF) scores, tolerances, and investigative criteria, which are also protected by FOIA exemption (b)(3) in conjunction with IRC §6103(b)(2). Settlement criteria can also be withheld pursuant to FOIA exemption (b)(7)(E).

  3. This exemption may only be used to protect investigative techniques or guidelines not generally known to the public (e.g. LEM criteria or settlement criteria).

  4. After the passage of time, tolerances, investigative and prosecutorial criteria, and settlement guidelines may become known to the public or revised. Such factors shall be considered before invoking the exemption. The determination must be made in consultation with the affected function(s), and documented in the case file.


More Internal Revenue Manual