AccessibilitySkip to Top NavigationSkip to Main ContentHome  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

11.3.13  Freedom of Information Act (Cont. 2)

11.3.13.9 
Special Issues

11.3.13.9.14  (01-01-2006)
Trust Fund Recovery Penalties

  1. At any point in the Trust Fund Recovery Penalty process, employees may receive a FOIA request for access to the files. Each request must be considered based on the current status of the case.

  2. If a FOIA requester mentions other persons liable for the penalty or IRC §6103 in the request, Disclosure personnel shall consider both FOIA and IRC §6103(e)(9) provisions to determine releasability of information regarding other responsible parties. IRC §6103(e)(9) authorizes, upon written request by the responsible officer, disclosure to that officer of the names of other responsible persons, whether the IRS has attempted to collect from these other persons, the nature of the collection activities, and the amount collected. See IRM 11.3.2.4.13, Disclosures to Persons with a Material Interest, and IRM 11.3.40, Disclosures Involving Trust Fund Recovery Penalty Assessments, for detailed guidance on what information is available under IRC §6103(e)(9).

    Note:

    IRC §6103(e)(9) is not applicable until an assessment has actually been made. Disclosure personnel must not prematurely disclose information under IRC §6103(e)(9) based on a proposed assessment.

    Caution:

    It is possible for different responsible parties to be assessed different Trust Fund Recovery Penalty (TFRP) amounts for one period. For example, one officer may be responsible for willfully failing to pay an entire quarter's liability, while another officer is responsible and willful for only the last two months of the quarter. On this rare occasion, the second officer might not be assessed the amount attributable to the first month of the quarter. Disclosure personnel can identify this situation by reviewing IDRS command code UNLCER, and by reviewing Form 4183 in the TFRP administrative file.

  3. A FOIA request which does not include a statement requesting information regarding other responsible parties shall be handled under the rules governing protection of each officer's privacy as outlined in IRM 11.3.40.8, Access Considerations.

  4. A FOIA request letter meets the requirement for a written request for information under IRC §6103(e)(9) if it specifically requests information available under IRC §6103 regarding the liability of other individuals for the TFRP. The case file will be redacted and provided under the appropriate FOIA considerations, and the data available under (e)(9) will be provided at the same time but in a separate portion of the response letter. This letter must explain that the additional items of information contained in the letter are being provided pursuant to IRC §6103(e)(9) and not the FOIA. Below is suggested language for the response letter:

    "This is in response to your FOIA request for information about the Trust Fund Recovery Penalty (TFRP) pertaining to [Name of Business] for [enter tax period(s)]. Enclosed are [enter number] pages of the administrative file, [enter number] pages have been sanitized per FOIA exemption (b)(3) as they contain third party taxpayer information. Information about the TFRP as it applies to any taxpayer other than you is not available under the FOIA. However, pursuant to IRC §6103(e)(9) you are entitled to receive the following information about other persons assessed this penalty:"

    • Taxpayer Name

    • Nature of Collection Activity (for example TDA, installment agreement, whether suspended (and if suspended, reason for suspension))

    • Amount Collected

    Note:

    The name, nature of collection activity, and amount collected must be provided for all other individuals assessed the penalty, to the extent requested. Information provided about the nature of collection activity and amount collected must be limited to the tax period(s) or portion of tax period(s) for which the requester was determined to be liable. If you are processing a request that involves two or more responsible parties who are assessed different amounts for the same tax period, contact the TFRP Advisor in the Collection Technical Services (Advisory) function for assistance in determining how payments were applied.

11.3.13.9.15  (01-01-2006)
Credit Bureaus

  1. Copies of credit bureau reports obtained in the course of compliance activities may be provided to the taxpayer to whom they pertain unless there is a harm to tax administration. The Fair Credit Reporting Act (FCRA), 15 USC 1681, places no restrictions on government release of credit reports. There is nothing in the FCRA that prohibits the disclosure to the taxpayer. Consumer reporting agencies are required to provide the consumer with data. The only statutory prohibition against disclosure appears in section 1681(r). That section prohibits an officer or employee of a consumer reporting agency from revealing information to a person who is not authorized to receive it.

11.3.13.9.16  (01-01-2006)
Non-specific Requests Citing "A Citizen's Guide to FOIA"

  1. A FOIA request may be received that does not describe specific records or is too broad or nebulous and relies on "A Citizen's Guide on Using FOIA and the Privacy Act of 1974 to Request Government Records."

  2. Normally, this would be considered an imperfect request. However, if such non-specificity is predicated on the quote "…no individual is required to name a system of records…" from the Citizen's Guide to FOIA, the following language shall be incorporated in the response:

    Your reliance on "A Citizen's Guide on Using FOIA and the Privacy Act of 1974 to Request Government Records" is misplaced. Its authors intended that Guide to serve only as a general introduction, to familiarize members of the public with the two Acts. The authors acknowledged that there is a considerable body of case law under both Acts that contribute to a complete understanding of the principles underlying the FOIA and the Privacy Act. In that regard, courts have upheld strict compliance with agency regulations. Therefore, since the Department of Treasury Regulations on the Privacy Act explicitly provide that a request must "give the name of the system or subsystem or categories of records to which access is sought…" (31 CFR 1.26(d)(iii)), and the IRS Statement of Procedural Rules for FOIA (26 CFR 601.702(c)(1)) requires that a FOIA request be for reasonably described records, your request cannot be processed.

  3. The response letter shall also cite, as usual, any other missing material needed to perfect the request.

11.3.13.9.17  (01-01-2006)
Requests for Third Party Information From ChoicePoint

  1. ChoicePoint is an information service used primarily by revenue officers and revenue agents that includes information about a taxpayer's neighbors, including their addresses and social security numbers.

  2. When a taxpayer requests a copy of his or her records (such as in examination or collection files) and ChoicePoint reports and/or data are found within those records, Disclosure personnel shall apply the following guidelines in processing the request:

    1. If the request seeks "everything in my file" or seeks a specific file (such as examination or collection) in which ChoicePoint data exists, then any third party information should be redacted and the record provided in sanitized form. Exemption (b)(7)(C) will be used in this situation. Because the third party information is not "return information" of the third party, exemption (b)(3) in conjunction with IRC §6103(a) does not apply.

    2. If the request seeks all information "about me" , the third party information shall be considered "not responsive" and withheld on that basis. Exemptions will not be cited.

    Note:

    This procedure parallels the processing of other documents with information of multiple persons on one page, such as some state Department of Motor Vehicles records and some real estate records. See IRM 11.3.13.7.2.3.(2)(a).

11.3.13.9.18  (01-01-2006)
Automated Lien System

  1. If a request is received for information contained in the Automated Lien System (ALS) database for all liens in any given county or state, the requester will be contacted and informed that only BMF liens are subject to disclosure from the ALS and information pertaining to individuals is not available. If BMF data is not being sought, the requester shall be informed that the requested information is exempt from disclosure pursuant to FOIA exemptions (b)(6) and (b)(7)(C).

    Note:

    This subsection does not apply where a requester is seeking his/her own information in the ALS data base. In response to a request for a taxpayer’s own records, conduct a search and process any records located.

  2. If the request is for BMF data, it must be transferred to the Baltimore Disclosure office following the procedures in IRM 11.3.13.5.12. That office will complete processing of the request in accordance with the following procedures.

  3. A formal request for an estimate of the cost for the ALS extract for the particular state(s) or other geographical area and any other parameters of the search, will be sent to the attention of the Program Analyst for ALS, at S:C:CP:FP:TI.

  4. If the FOIA request contains a commitment to pay, regardless of the cost involved, the extract and the costs involved will be provided to the Disclosure office by the ALS Program Analyst within 1-2 weeks after receipt of the formal written request.

  5. If the FOIA request does not contain a commitment to pay, or the commitment is not sufficient to cover the estimated cost, the cost estimate only, and not the extract itself, will be provided to the Disclosure office within 1-2 weeks after receipt of the formal written request. The extract will be created and provided to the Disclosure office within two weeks of receipt of a formal commitment to pay the estimated cost.

    Note:

    Disclosure personnel shall follow guidance in IRM 11.3.5 to determine if fees must be prepaid or the requester notified of the cost estimate if it exceeds the agreed amount, prior to release of the extract data.

11.3.13.9.19  (10-26-2007)
Requests for Pocket Commissions

  1. When processing requests for a copy of the memorandum submitted by managers for issuance of pocket commissions for specific employees, the following guidelines shall be followed:

    1. A copy of the memorandum submitted by managers for issuance of a pocket commission, or other records containing similar information, will be provided to the requester except for records pertaining to employees in the sensitive positions identified by OPM and instances where the employee uses a pseudonym and the real name is identifiable.

      Note:

      In some instances there will be no records responsive to the request, since security offices may not maintain the pocket commission request memorandums submitted by managers.

    2. Requests for copies of the actual pocket commission shall be denied citing (b)(3) in conjunction with 18 USC 701.

    3. Requests for the serial number shown on the pocket commissions shall be denied citing (b)(2) and (b)(7)(E), since there is a potential that the numbering system could be compromised.

    4. Requests for the photo that would have accompanied the memorandum and the employee's real name, if using a pseudonym, shall be denied under (b)(6).

    5. Requests for information pertaining to the pocket commissions of employees in the sensitive positions identified by OPM, shall be denied under (b)(6).

  2. For requests submitted in the form of a series of questions pertaining to the pocket commissions for specific employees, Disclosure personnel shall advise the requester that the response will deal with only those portions of the request that conform to the FOIA. They shall also advise that the FOIA does not require agencies to respond to questions; however, information relevant to the pocket commission is available in IRM 1.16.6, Pocket Commissions.

  3. Any information provided pertaining to specific employees shall be limited to the type of information available in the Public Information Listing; therefore, the name and title of the employee will be provided in accordance with IRM 11.3.13.9.12.1.

11.3.13.9.20  (01-01-2006)
Undeliverable Refund Lists

  1. Undeliverable Refund Lists are available to the public under FOIA after being released by the IRS to the media under IRC §6103(m)(1). The list need not have been published by the media to otherwise be available.

  2. Requests for Undeliverable Refund Lists for the entire country shall be directed to the Baltimore Disclosure office for response.

  3. The Baltimore Disclosure office will coordinate the release of the Undeliverable Refund List with Media Relations, which maintains the information on CD-ROM.

  4. Requests directed to local Disclosure offices for information pertaining to a specific geographical area, such as for a particular state, will be processed by that Disclosure office.

11.3.13.9.21  (01-01-2006)
Electronic Return Originator Lists (EROs)

  1. All requests for the Electronic Return Originator Lists (EROs) shall be transferred to the Baltimore Disclosure office for a response.

  2. It has been determined that no applicable FOIA exemption can be applied to a request for a list of EROs who have been suspended within the past five years. The public's right to know outweighs any privacy interests of the ERO.

11.3.13.9.22  (01-01-2006)
Possible Refund Scheme Requests

  1. In some situations, a taxpayer may file a FOIA/Privacy Act request for transcript information and use the transcript along with a Statement of Lifetime Earnings obtained from Social Security to file a false claim. Disclosure offices should provide the CI function with a list of FOIA requesters who make the following or a closely similar request:

    "a statement of all taxes paid, all penalties, all fines, all interest and all credits for any seizures and all deposits that have been credited in the files of your system of records for [name] SSN [x12-01-2003] since the first date of filing with the IRS on or about the year 1953 to the present date of this Privacy Act Request."

  2. When processing these types of requests, they should be faxed to the attention of:
     
             Investigative Analyst
             Ogden Fraud Detection Center

    Note:

    The referral to the Ogden Fraud Detection Center for possible refund scheme scrutiny should not affect the normal processing of the FOIA request. The requester's tax information will be made available to him/her regardless of the possible purpose.

11.3.13.9.23  (01-01-2006)
IRC§ 6001 Requests

  1. Requests may be received that ask for a copy of the "notice from the District Director that I was required to keep books, records, and file return(s) as required by 26 USC §6001 and 26 CFR §1.6001-1(d) and §31.6001-6," or similar wording.

  2. IRC §6001 does not require issuance of such a notice, but the Secretary may require a person by notice served to make returns and keep records. However, there are Notices of Inadequate Books and Records (L978 and L979). A revenue agent can issue these letters during a field audit where actual books and records have been reviewed and determined to be insufficient to correctly record income and expenses.

  3. Notices to file returns do not, per se, exist. There are computer-generated letters sent by the campuses, which would not be retrievable in most cases. These letters, which have a notice number, request that the taxpayer file a return.

  4. If the campus sends the case to the field (for examination or collection involvement), a copy of the notice may or may not be in the file. Field employees can also issue a letter to a non-filer, e.g. L964(DO), a copy of which would be kept in the case file.

  5. Requests discussed in (1) above cannot be closed as imperfect simply because the IRS no longer has District Directors or because they do not clearly articulate the programs/procedures relating to IRC §6001.

  6. Since some IRS offices kept files of Letter 978 and Letter 979 (Inadequate Records Notice) issued, at a minimum, a search of such files and/or IDRS shall be made to establish whether there is indication of a field examination for the years covered by the request. With no indication of a field audit, there would be no records responsive. Files of notices issued may be found in the local Technical Support Unit (Examination and Return Selection PSP).

  7. If the search results in no responsive records being located, the letter to the requester shall contain the following language:

    "IRC §6001 does not require issuance of a notice by the District Director or any other IRS employee. § 6001 merely states that the Secretary (or his delegate) may require a person by notice served to make returns or keep records. If you received a notice that asks you to file a return or provide information about a tax year for which no return has been received, the notice was computer-generated. The IRS does not routinely maintain copies of such notices. At this time, we are unable to identify a document that meets the description in your letter. IRS employees sometimes issue letters that address issues related to IRC §6001. If you have not filed tax returns for certain years, you may have received such a letter of inquiry. Or, if returns you filed were audited and actual books and records were reviewed, the examiner may have issued a letter that states that your records are inadequate. If you were issued such a letter and you wish to pursue obtaining a duplicate of the file copy, please write again specifically requesting this information."

11.3.13.9.24  (01-01-2006)
Requests for the IRS EIN

  1. Governmental Liaison and Disclosure has been given authority from the Chief Financial Officer to release the IRS' Employee Identification Number upon receipt of a valid FOIA request seeking that information.

  2. The EIN, used by the IRS on Form 1099 and Form W-2 where IRS is the payer, may be secured from the GLD FOIA website.

11.3.13.9.25  (01-01-2006)
Federal Witness Security Program Information

  1. Title 28 of the Code of Federal Regulations, §0.111B implements non-disclosure provisions of the Witness Security Program statute.

  2. Although records related to this area are rare, if a request specifically requests Federal Witness Security Program information or a search for records identifies Program information as responsive, you must contact the FOIA Senior Tax Law Specialist or FOIA Policy Analyst for further information and guidance on how to respond. Coordination with appropriate Department of Justice personnel may be required.

11.3.13.9.26  (10-26-2007)
News Media Requests

  1. Disclosure offices may receive requests from individuals stating they are affiliated with news media and seeking a fee waiver or reduction on the basis of being a news media representative. The requester must establish his/her standing as a member of the media before any waiver or reduction of fees may be granted.

  2. Generally, representatives of the news media include persons on the staff of established news media outlets, such as, but not limited to, radio or television stations, wire services, or periodicals of general circulation.

  3. The Courts have addressed this area and have further defined the definition of "news media" as follows:

    1. A representative of the news media is, in essence, a person or entity that gathers information of potential interest to a segment of the public, uses its editorial skills to turn the raw materials into a distinct work, and distributes that work to an audience.

    2. Information is commonly gathered by means of FOIA requests, papers declassified by the Government, interviews with, and private records of, present and former government officials, official statements, publications, and press releases, testimony before Congress, newspaper and periodical accounts of recent events, and reports by congressional committees and the Government Accountability Office.

    3. From documents gathered, the requester or entity exercises a significant degree of editorial discretion in deciding what records to use and how to organize them, creates a record, report, or publication, and distributes the resulting work to the public.

  4. Freelance journalists may be regarded as working for the news media, even though not actually employed by the media, if they can demonstrate a solid basis for expecting publication, such as a publication contract or by demonstrating a record of past publication.

  5. Representatives of narrowly focused publications such as house journals, trade journals, or organizational newsletters, which are not designed for ordinary circulation to the general public, are generally not considered news media for this purpose.

    Note:

    A request from NTEU will not usually qualify as a media request. NTEU's focus and constituency are the IRS bargaining unit employees, not the general public.

  6. Information vendors, data brokers, and other second-hand disseminators of documents, such as private libraries, private repositories, or those who act as information vendors or as agents of others who want access to government documents, do not qualify as news media for fee waiver purposes.

  7. Generally, all fees may be waived or reduced when disclosing information is likely to contribute significantly to public understanding of the operations or activities of the government and when it is not primarily in the commercial interests of the requester. See IRM 11.3.5.6.2.

    Note:

    A requester seeking a fee waiver based on being a representative of the news media must generally explain in the waiver request both an intention and a reasonably expected ability to disseminate the information to the public.

11.3.13.9.27  (10-26-2007)
Grand Jury Information

  1. A response to a FOIA search memorandum may include a statement from the function (usually CI) in control of the responsive records that all, or a portion, of the responsive records are grand jury information.

  2. Not all records relating to a grand jury investigation are considered "grand jury information" subject to secrecy under Rule 6(e) of the Federal Rules of Criminal Procedure (FRCrP).

  3. The following are generally considered to be grand jury information:

    1. Exhibit to the Grand Jury, which fact is apparent on the face of the record;

    2. Transcript of Grand Jury testimony, or reveals the substance thereof;

    3. Identifies Grand Jury witnesses;

    4. Identifies Grand Jury jurors;

    5. Reveals the direction, scope, or strategy of the Grand Jury investigation;

    6. Grand Jury subpoena or search warrant, or reveals the substance thereof; or

    7. Reveals the deliberation or questions of Grand Jury jurors.

  4. The following are generally not considered to be grand jury information:

    1. Records obtained without use of the grand jury process and without mention of the existence of a grand jury;

    2. Records obtained prior to the existence of the grand jury (e.g. tax returns, other return information developed by CI, Exam or Collection prior to referral for a grand jury investigation);

    3. Records which exist independent of the grand jury (e.g. bank account records) the release of which would not reveal the inner workings of the grand jury.

  5. If a determination is made that providing grand jury records to the Disclosure office will harm the investigation, written attestation that the records are grand jury information 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, telephone number

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

    3. Location of records

    4. Other contact person name, title, telephone number

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

    6. The signature of the Special Agent or Supervisory Special Agent (SSA)

    7. The concurrence of the Special Agent in Charge (SAC)

    Note:

    See IRM 9.3.1, Disclosure and Publicity - Disclosure, and IRM 9.5.2, The Investigative Process - Grand Jury Investigations, for further information.

  6. The Disclosure office will advise the requester that responsive records in an approximate volume have been determined to be grand jury information and as such are being withheld pursuant to FOIA exemption (b)(3) in conjunction with grand jury secrecy provisions of Fed. R. Crim P. 6(e). The application of exemptions such as (b)(7)(A) and/or (b)(3) in conjunction with IRC §6103(e)(7) must be made where appropriate.

    Note:

    In those rare circumstances where the Special Agent Report is generated during a grand jury investigation at the direction of the Assistant United States Attorney, application of FOIA exemption (b)(5) should also be considered.

  7. The office (usually a CI office) making the determination that such records are grand jury information is responsible for flagging the case file appropriately so it can be adequately analyzed by Procedure and Administration attorneys in the event of any litigation associated with the FOIA response. The office must retain the grand jury information in a way consistent with FOIA record retention requirements. The documentation described above must state that a complete copy of the withheld documents will be kept available and that the function will re-evaluate the records if the requester files an administrative appeal or judicial complaint in the FOIA matter. IRS must be able to identify any documents withheld. Therefore, 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.

11.3.13.9.28  (01-01-2006)
Requests for Certified Copies of Records

  1. Many FOIA requests include language asking that Disclosure provide certified copies of records found responsive or asking for a certification of lack of record for those items where we have a "no records" determination.

  2. The FOIA contains no provision requiring IRS to provide certified copies of documents. In response to a request for certification of any IRS records sought under the FOIA, the requester shall be advised that the FOIA does not require documents to be certified in response to a FOIA request. The requester shall be further advised that IRC §6103(p)(2) only requires a certified copy of a return to be furnished to any person who is authorized access to the return. Notify the requester that a certified copy of the tax return can be requested by completing a Form 4506, checking the box on line 6, enclosing the required fees, and submitting the Form to the appropriate address as shown in the instructions. A blank Form 4506 must be provided with the response.

  3. Under no circumstances will Document 3050, Certification of Lack of Record be provided when no responsive records are found. It is sufficient to state that no records were located, without providing a certification to that effect. Notify the requester that verification of nonfiling may be obtained by submitting a Form 4506-T to the appropriate address as shown in the instructions. A blank Form 4506-T must be provided with the response.

11.3.13.9.29  (01-01-2006)
Trusts

  1. FOIA requests for trust information (whether legitimate or abusive) may be received from a person claiming to be a trustee or other qualified IRC §6103(e) requester. Frequently, the documentation necessary to establish trustee relationship (see IRM 11.3.2.4.8) such as copies of the trust instrument are not provided. A requester's self-serving attestation of trusteeship or other status is not sufficient. Assuming that the incoming request is not imperfect for other reasons, some internal research may be done to establish identity for entitlement to access.

  2. Ordinarily, for these types of requests, IDRS should be used to perform preliminary research.

    1. If there is open compliance activity, contact the compliance function. If the compliance function has established the requester's right of access (e.g. through the process of initiating and conducting examination activity), then Disclosure can rely on that determination.

    2. If there is open compliance activity, but compliance has made no determination or has specifically determined the requester's lack of a right of access, then the FOIA request shall be deemed imperfect on identity grounds with the requester being advised as to how to establish entitlement.

    3. If there is closed compliance activity, that function should be consulted to determine who was finally recognized as being entitled to trust information.

    4. If there is no indication of compliance activity, but IDRS specifically lists the FOIA requester as an IRC §6103(e) person (e.g. the trust entity module has the requester as "trustee" and the requester's address is the same as the trust's), disclosure of the trust tax information can be made consistent with regular FOIA processing and exemptions.

  3. Disclosure personnel need to be careful on these requests to ensure they don’t take a different position from the compliance function in allowing IRC §6103(e) access.

11.3.13.9.30  (10-26-2007)
Requests for Documents Associated with a Document Locator Number (DLN)

  1. Disclosure offices frequently receive FOIA requests seeking access to documents associated with specified DLNs. Generally, these requests come in a series of letters, each asking for one or more DLNs listed on a transcript provided in response to a previous request.

    Note:

    It is important to read and analyze each request carefully. If the request seeks documents "associated with" or "identified by" the DLN, or similar language, it is sufficient to ESTAB the DLN. However, if the wording of the request seeks "the documents that caused the DLN to be input" or uses similar language, further analysis of the transaction and possible underlying actions are necessary to locate responsive documents.

  2. Any document associated with the requested DLN is considered responsive to the request, including the Form 5147, IDRS Transaction Record. The Form 5147 is created when the underlying transaction is input, not when an ESTAB request is made.

  3. The underlying Form 2848, Power of Attorney and Declaration of Representative, and Form 8821, Tax Information Authorization, associated with Transaction Code (TC) 960 (Centralized Authorization File) are filed separately from tax returns. The actual form must always be retrieved in response to a request seeking access to either the form by name or the documents associated with the TC 960 DLN. Depending on the wording of the request, it may also be necessary to retrieve the Form 5147. To retrieve the actual Form 2848, or Form 8821, a Source Document Locator Number (SDLN) must be obtained and a Form 2275 prepared and sent to the Kansas City Consolidated Files Site (C-Site) at the following address:
         Internal Revenue Service
         1500 South Geospace Drive, #335
         Independence, MO 64056
         Attn.: IRS-C-SITE

    Note:

    Requests for fewer than 15 documents may be faxed.

    1. If the request seeks access to a Form 2848 or Form 8821 by name, or to the documents causing the transaction code to be input, the SDLN may be located by accessing the CFINK command code on IDRS under the requester’s SSN. The CFINK contains the SDLN.

    2. If the request seeks access to the documents associated with the DLN, an ESTAB request must be made to retrieve the Form 5147. The underlying Form 2848 or Form 8821 must also be requested in response to this request.

  4. The following DLNs have been identified as electronic transactions having no paper or source documents. It is unnecessary to ESTAB any DLN that meets either description.

    1. Any DLN with a Julian Date (digits six, seven and eight) of 367 through 400 or 767 and above, or

    2. Any DLN with a series of repetitive numbers in digits six through thirteen (e.g. 29210-000-00000-X, or 49210-999-99999-X).

  5. It is extremely difficult to identify those transactions that, when input, do not generate a paper document. Therefore, an ESTAB shall be requested for every DLN that does not meet the description in (4) above.

  6. When documents are received as a result of the ESTAB, they must be reviewed, edited, and released or withheld in accordance with IRM 11.3.13.7.

    Note:

    Retrieval of the Form 5147 is always required, even if access is denied. A copy of the Form 5147 must be retained in the case file for possible appeals and litigation

  7. The following changes apply to transaction codes (TC) input on or after February 23, 2005.

    Note:

    The changes are caused by the date of the input of the TC, not the date of the ESTAB.

    1. Forms 5147 generated as a result of a change to the account causing a new refile DLN or associated with source documents will continue printing, and Files will continue to pull the documents.

    2. Forms 5147 without source documents (NSD), including but not limited to document codes 17, 18, 24, 34, 48, 58, 63, 77, 87, will no longer be printed. Since there are no documents associated with these forms, Files will no longer handle these requests. These forms may be viewed through the Control-D WebAccess. These forms must be printed and considered responsive to the request.

11.3.13.9.31  (01-01-2006)
Requests for Form W-7, Application for IRS Individual Taxpayer Identification Number (ITIN)

  1. An ITIN is a nine-digit number issued by the IRS to individuals who are required to have a taxpayer identification number for tax purposes, but who do not have, and are not eligible to obtain, a social security number (SSN). The FOIA requests generally include an SSN and seek a copy of the Form W-7.

  2. Offices receiving a FOIA request for a Form W-7 or related information shall research the ITIN database using the following command codes to determine the status of an application, and/or obtain a DLN.

    1. ITDLN - to access the database using the applicant’s name and date of birth (DOB), or

    2. ISIGNT - to access the database using the ITIN number, or

    3. ITNSF - to access the database using the DLN.

      Note:

      Contact the Unit Security Representative to add these command codes to an IDRS profile.

  3. Once a DLN is located, the W-7 can be retrieved using command code ESTAB. The DLN for a W-7 is identified by a File Location Code of 98 with a tax class document code of 296 (English) or 298 (Spanish).

  4. If the requester did not provide a DOB or an ITIN, command code INOLE with a definer of S or X should be used to research the DOB. If internal research does not locate a DOB, the requester should be contacted by phone to solicit the needed information. Telephone contact should be made only if a number was provided with the request or if one is available on ENMOD. It is not necessary to do further research to locate a phone number. If we are unable to locate a DOB and no phone number is available, inform the requester that we cannot process the request until a complete name and DOB or ITIN is received. The request shall be closed off E-DIMS using an "I" disposition code. The following language can be used:

    "We have received your request for Form W-7, Application for an Individual Taxpayer Identification Number. Please be advised that a W-7 is to be used by individuals who are required to have a taxpayer identification number but who do not have, and are not eligible to obtain, a social security number (SSN). If the Social Security Administration assigned you an SSN, you are not eligible for an ITIN, and it is unlikely that there are records responsive to your request. However, we are unable to confirm this fact unless we receive either your date of birth or the ITIN number if one was issued. We will be glad to reconsider your request upon receipt of this information."

    Note:

    Requests may include such language as, "Send requester an explanation of just how an "Account" with the IRS was established in the first place as is referenced by IRS correspondence as to being in existence…" This portion of the request should be addressed by notifying the requester that the FOIA does not require agencies to conduct research or respond to interrogatories.

11.3.13.9.32  (01-01-2006)
Requests for Third Party Contact Information

  1. In response to a FOIA request for Form 12175, Third Party Contact Report Form, the requester shall be informed that we will neither confirm nor deny the existence of a form ("the glomar response" ) where:

    1. There has been a reprisal determination made with respect to the third party named in the form

    2. There is no responsive record or

    3. It has been determined that disclosure would jeopardize the collection of any tax (but only so long as the jeopardy situation continues)

  2. FOIA exemptions (b)(3) in conjunction with IRC §6103 (e)(7), (b)(7)(A) (where applicable), and (b)(7)(C) will be asserted as the exemptions underlying the glomar response.

  3. The Form 12175 can be provided where none of the above criteria are met.

    Note:

    Forms 12175 are maintained in two different Privacy Act systems of records: non-reprisal (00.333) and reprisal (00.334). System of records 00.334 is exempt from the access provisions of the Privacy Act.

11.3.13.9.33  (01-01-2006)
FedState Agreements

  1. Copies of FedState agreements are generally available to the public under the FOIA. However, those portions of implementing agreements or MOUs which contain tolerance and criteria information are to be withheld from disclosure using FOIA exemption (b)(2) and given the same protection as LEM material, as described in IRM Exhibit 1.16.8.5-2, Protectable Items, of IRM 1.16.8, Physical Security Standards.

  2. U.S. Possession Agreements (e.g. Tax Information Agreements, Tax Coordination Agreements, and MOUs) are considered Tax Conventions within the meaning of IRC §6105 and can only be disclosed consistent with that statute. Usually these agreements will be exempt under FOIA exemption (b)(3) cited in conjunction with IRC §6105. Other FOIA exemptions, such as (b)(7)(E) may also be applicable. Any FOIA request seeking copies of these Possession agreements shall be coordinated with the Baltimore Disclosure Office.

  3. Any response to a FOIA request for a copy of a report prepared by a state agency (including Safeguard Activity and Procedures Reports), by the IRS as a result of a review of a state agency in accordance with IRC §6103(p)(4), or by the IRS in accordance with IRC §6103(p)(5), shall be coordinated with the respective state agency. These reports often focus on sensitive processes and systems and may expose vulnerabilities. As such, the information can be protected at the request of state officials pursuant to FOIA exemption (b)(2).

11.3.13.9.34  (10-26-2007)
Requests for Copies of Information Provided to State Tax Agencies

  1. FOIA requests for access to documents provided by the IRS to state tax agencies may seek records that were provided pursuant to:

    1. A specific request from a state employee

    2. An implementing agreement and/or

    3. The tape extract program

  2. The requests may also seek other records associated with our exchange of information with state agencies, for example accountings for disclosure (including requests for Form 5466-B, Multiple Record of Disclosure) and any request for IRS records made by the state agency. Many of the requests go on to ask, "if said information was disclosed on computer tape, please print said information on hard copy."

  3. Prior to the release of any information to the requester, or confirmation that information was released, contact should be made with the agency liaison to ascertain whether release of any information not part of the Governmental Liaison Data Exchange Program (GLDEP) would impair any ongoing compliance activity. If the state representative indicates the release would harm state tax administration and can articulate that harm, the information should be withheld pursuant to FOIA exemptions (b)(7)(A) and (b)(3) in conjunction with IRC §6103(e)(7).

  4. The release of the following information should be considered, after consideration of any response from the state agency:

    1. If a request seeks information provided to the state pursuant to a specific request, search for any responsive documents and review them for possible release. Include a check of Disclosure inventory management system records in the search.

    2. If information responsive to a request includes documents that are routinely provided to the state pursuant to an implementing agreement (e.g. revenue agent reports (RARs)), efforts must be made to retrieve and consider those documents in response to the request. Examination Operational Automation Database (EOAD) data, if maintained by the Disclosure Office, may be downloaded and considered responsive rather than retrieving RARs from files.

    3. If the request seeks records such as the Form 5466-B or the letter from the state requesting information, the responsive documents must be retrieved and their release considered.

      Note:

      The Privacy Act specifically excludes records released to state agencies pursuant to IRC §6103(d) from the requirement to make accountings available upon request of the individual named in the record. However, consideration must be given to the release of accounting records pursuant to a request under the FOIA.

  5. In response to requests for information disclosed "on computer tape" that can be read as seeking access to information exchanged through tape extract programs, the requester must be provided with transcripts, including MFTRA, IRP documents, PATRA transcripts, and any other computerized records that include the data that would have been included on extracts covered by the request. Provide these documents using the following language:

    "A request for all records released to [name of state] through the tape extract program is overly broad. The IRS routinely participates in the exchange of information with [name of state]. The data routinely exchanged via these extracts is voluminous and the IRS does not maintain specific taxpayer records of the information. Enclosed are IRS Agency records that contain the information that would generally be responsive to your request. These documents substantially reflect the information that would have been provided to the state through the tape extract program based on the information you provided."

    Note:

    The IRS is in the process of moving from tapes to secure electronic transmission of this data. Any FOIA request for "computer tapes" must also be read to include electronic transmission.

  6. Disclosure personnel must be aware that the IRC §6103(d) extract tapes themselves (both inquiry tapes from other agencies and response tapes generated by IRS) are not IRS agency records and are therefore not subject to the FOIA. If a requester explicitly seeks the "data from the extract" (distinct from "data provided" ) the FOIA response should state that the record requested "is not an agency record and is not subject to disclosure pursuant to the FOIA." Similarly, in any program where data requests are made and/or responded to in electronic format, the electronic requests are not IRS agency records. This is true regardless of IRS retention for brief time periods for purposes of disaster recovery or tape recreation. The electronic response is an agency record only if a copy is retained for disclosure accounting purposes under IRC §6103(p)(3).

11.3.13.9.35  (10-26-2007)
Requests for Lottery Information

  1. If you receive a FOIA request for information regarding lottery winners you should use the following language:

    "You asked for copies of any and all documents related to court and administrative judgments for lottery winners who have brought suit against the IRS, and any and all documents concerning the appeal of a previous judgment pertaining to the taxation of their winnings. You also asked for copies of any and all court orders regarding judgments from lottery winners or their heirs for the period 1986 to the present.
     
    One of the FOIA’s requirements is that requesters reasonably describe the records they are seeking. The content of your request is so broadly based that we are unable to specifically identify any releasable records that can be made available to you. To the extent that your request would require us to conduct legal research on your behalf, please be advised that the FOIA does not require agencies to conduct such research. Based on the description of the records you are seeking, you might locate information in publicly available case decisions. Generally, these may be researched at public libraries or law libraries. There are also a number of commercial research services that allow users to search case law or decisions associated with specific topics. You may wish to make use of these resources.
     
    If any of the requested records exist in Internal Revenue Service taxpayer files, they are the return information of the taxpayer(s) to whom they pertain. These records are protected by the confidentiality provisions set forth in Internal Revenue Code §6103 and may be disclosed to you only with the authorization of the taxpayer(s) whose information is to be disclosed. Since you have not provided the required authorizations, we cannot disclose any responsive records that may exist, and we are closing our case file."

  2. Cases shall be closed as imperfect since the requested records are not reasonably described.

11.3.13.9.36  (01-01-2006)
Requests for Offshore Credit Card Project (OCCP) Files

  1. Requests may be received for access to the data contained in OCCP databases, either for general inspection or study of the data or to determine if the name of the requester, or a client of the requester, appears in the data. The information in the OCCP databases pertains to "live" credit cards.

  2. Requests for information from the OCCP database must be transferred to the Baltimore Disclosure office for processing.

  3. The Deputy Director, Compliance Policy, has determined that disclosure of data contained in the OCCP database would seriously impair tax administration within the meaning of IRC §6103(e)(7) and would "interfere with enforcement proceedings" within the meaning of FOIA exemption (b)(7)(A).

  4. Based on this determination, the following requests shall be denied pursuant to FOIA exemption (b)(3) in conjunction with IRC §6103(a) and/or (e)(7) and FOIA exemption (b)(7)(A) and/or (C):

    1. A request for data that does not pertain to the requester or the requester’s client,

    2. A request asking whether the subject taxpayer’s name appears in the data,

    3. A request seeking copies of any transactional credit card records pertaining to the subject taxpayer.

  5. Requests from specific taxpayers for credit card data that has been placed in their individual case files must be considered on a case-by-case basis by the individual examiners in coordination with the local Disclosure Managers. Disclosure staff must work closely with the case agent and manager to ensure that any information released will not impair tax administration or violate personal privacy.

  6. An OCCP case file may have unique considerations when processing a FOIA request.

    1. The file may contain ChoicePoint (or similar) information pertaining to more than one individual with the same name as that on the credit card. Agents doing the research often leave all such information in the file so that the case agent can see the process used to identify the taxpayer. Any ChoicePoint (or similar) information not directly pertaining to the taxpayer must be denied in accordance with the guidelines in IRM 11.3.13.9.17.

    2. ChoicePoint (or similar) information on the taxpayer involved in the case may be disclosed to that taxpayer at any time, unless the case agent has a reason for temporarily withholding it. Disclosure staff must work closely with the case agent and manager to make that determination. It is rare that disclosure of the taxpayer’s ChoicePoint (or similar) information would be harmful to the case.

11.3.13.9.37  (01-01-2006)
Requests for Centralized Authorization File (CAF) Extracts

  1. Requests from individuals representing taxpayers before the IRS seeking access to all information regarding themselves from the CAF must be transferred to the Headquarters Office for response. A sample request is available on the FOIA page at www.irs.govby clicking on the "CAF Client Listing Request" link.

11.3.13.9.38  (01-01-2006)
Preparer Tax Identification Numbers (PTINs)

  1. A PTIN is not return information as defined in IRC §6103(b). Neither is the Application for a Preparer Tax Identification Number, Form W-7P, a return within the meaning of IRC §6103.

  2. A request for information about individuals who hold PTINs shall be denied citing FOIA exemption (b)(6).

11.3.13.9.39  (10-26-2007)
Requests for Taxpayer Recordings Made in the Contact Recording Process

  1. The IRS has implemented Contact Recording (CR) in all toll-free sites. CR is an automated system that records interactions between the customer and telephone assistors. CR is being phased into the Call Centers, and there are plans to pilot a similar system in the Taxpayer Assistance Centers.

  2. The taxpayer does not have Privacy Act access to any CR recordings because any voice or data capture made under CR is not retained by taxpayer identifier. Rather, it is kept under the recorded employee's unique identifier for as long as it is needed, prior to transcription and use in the evaluation and feedback process.

  3. However, if the taxpayer makes a timely and processable FOIA request, the IRS will attempt to locate and provide the recording. The responsive document(s) will generally include the entire recording pertaining to the taxpayer’s contact with the CSR. If the recording includes an interchange between the as