Argyle Systems Inc. v. Internal Revenue Service

CourtDistrict Court, District of Columbia
DecidedSeptember 25, 2022
DocketCivil Action No. 2021-0016
StatusPublished

This text of Argyle Systems Inc. v. Internal Revenue Service (Argyle Systems Inc. v. Internal Revenue Service) is published on Counsel Stack Legal Research, covering District Court, District of Columbia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Argyle Systems Inc. v. Internal Revenue Service, (D.D.C. 2022).

Opinion

UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA

ARGLYE SYSTEMS INC,

Plaintiff, v. Civ. Action No. 21-16 INTERNAL REVENUE SERVICE, (EGS) Defendant.

MEMORANDUM OPINION

This case arises out of Freedom of Information Act

(“FOIA”), 5 U.S.C. § 552, requests Plaintiff Argyle Systems,

Inc. (“Argyle”) made to the Internal Revenue Service (“IRS”).

See generally Compl., ECF No. 1.

Pending before the Court are the IRS’s Motion for Summary

Judgment and Argyle’s Cross-Motion for Summary Judgment. Upon

careful consideration of the motions, the oppositions and

replies thereto, the applicable law, the entire record, and for

the reasons stated below, the Court GRANTS the IRS’s Motion for

Summary Judgment, ECF No. 16, and DENIES Argyle’s Cross-Motion

for Summary Judgment, ECF No. 18.

I. Factual Background

The following facts are not in dispute. On or about October

9, 2020, Argyle submitted a FOIA request in which it sought

“[a]ny and all correspondence, communications, files, documents,

1 and records in any form, including hard copies and

electronically stored information, evidencing, reflecting or

pertaining to agency records” for nine categories of agency

records:

(1) Reporting Agent Authorization forms, set forth in IRS form 8655, and submitted to IRS between January, 2020 and the present.

(2) Reporting Agent’s Lists (“RAL”), as described in Internal Revenue Manual (“IRM”) Part 21, Section 21.3.9.3.1, created between January 1, 2020 and the present.

(3) RAF0940I – RAF Snapshot Reports generated between January 1, 2020 and the present.

(4) RAF41 listings, reports, and output files, as described in IRM Part 21, Section 21.3.9.10.3, generated between January 1, 2020 and the present.

(5) RAFREPT AGTFIL01 – Agent File(s), as described in IRM Part 21, Section 21.3.9.10.3, generated between January 1, 2020 and the present.

(6) RAFREPT AGTRPT01 – Agent File Report(s), as described in IRM Part 21, Section 21.3.9.10.3, generated between January 1, 2020 and the present.

(7) Any and all RAF26 output files, as described in IRM Part 21, Section 21.3.9.10.4, generated between January 1, 2020 and the present.

(8) Any and all RAF70 listings, reports, and output files, as described in IRM Part 21, Section 21.3.9.10.5, generated between January 1, 2020 and the present

(9) Any and all RAF08 output files and reports, as described in IRM Part 21, Section

2 21.3.9.10.6, generated between January 1, 2020 and the present.

Compl., ECF No. 1 ¶ 14. The request stated that it “specifically

does not include documents or information evidencing, reflecting

or pertaining to Taxpayer returns, income or payments of tax

liabilities.” Id.

In response, the IRS provided records responsive to Item 3.

Def.’s Brief in Support of the IRS’s Mot. for Summ. J. (“Def.’s

Mot.”), ECF No. 16-2 at 1. 1 The IRS contends that the records

sought in the remaining Items are categorically exempt from

disclosure pursuant to FOIA Exemption 3 in conjunction with 26

U.S.C. § 1603(a), and partially exempt based on FOIA exemption

6. See id.

The parties do not dispute that the remaining items in

Argyle’s FOIA request can be categorized as follows: (1)

Reporting Agent (“RA”) Authorization, Form 8655; and (2) Reports

generated from an IRS database—the Reporting Agents File

(“RAF”)—containing information derived from the Form 8655. Pl.’s

Counter-Statement of Disputed Facts, ECF No. 18-1 ¶ 40. Revenue

Procedure 2012-32 defines a RA as “an accounting service,

franchiser, bank, service bureau, or other entity authorized to

perform on behalf of a taxpayer one or more of the acts

1 When citing electronic filings throughout this Opinion, the Court cites to the ECF page number, not the page number of the filed document

3 described in this revenue procedure.” I.R.S. Tax Form and

Instructions, Rev. Proc. 2012-13.

II. Standard of Review

FOIA cases are typically and appropriately decided on

motions for summary judgment. Gold Anti–Trust Action Comm., Inc.

v. Bd. of Governors of Fed. Reserve Sys., 762 F. Supp. 2d 123,

130 (D.D.C 2011) (citations omitted). Summary judgment is

warranted “if the movant shows [by affidavit or other admissible

evidence] that there is no genuine dispute as to any material

fact and the movant is entitled to judgment as a matter of law.”

Fed. R. Civ. P. 56(a). A party opposing a summary judgment

motion must show that a genuine factual issue exists by “(A)

citing to particular parts of materials in the record . . . or

(B) showing that the materials cited do not establish the

absence . . . of a genuine dispute[.]” Fed. R. Civ. P. 56(c).

Any factual assertions in the moving party's affidavits will be

accepted as true unless the opposing party submits his own

affidavits or other documentary evidence contradicting the

assertion. See Neal v. Kelly, 963 F.2d 453, 456 (D.C. Cir.

1992). However, “the inferences to be drawn from the underlying

facts . . . must be viewed in the light most favorable to the

party opposing the motion.” Matsushita Elec. Indus. Co. v.

Zenith Radio Corp., 475 U.S. 574, 587 (1986) (internal quotation

marks omitted).

4 An agency has the burden of demonstrating that “each

document that falls within the class requested either has been

produced, is unidentifiable, or is wholly [or partially] exempt

from the Act's inspection requirements.” Goland v. CIA, 607 F.2d

339, 352 (D.C. Cir. 1978) (internal citation and quotation

omitted). In reviewing a summary judgment motion in the FOIA

context, the court must conduct a de novo review of the record,

see 5 U.S.C. § 552(a)(4)(B); but may rely on agency

declarations. See SafeCard Servs. v. SEC, 926 F.2d 1197, 1200

(D.C. Cir. 1991). Agency affidavits or declarations that are

“relatively detailed and non-conclusory” are accorded “a

presumption of good faith, which cannot be rebutted by purely

speculative claims about the existence and discoverability of

other documents.” Id. (internal citation and quotation omitted).

“[T]he Court may award summary judgment solely on the basis of

information provided by the department or agency in declarations

when the declarations describe the documents and the

justifications for nondisclosure with reasonably specific

detail, demonstrate that the information withheld logically

falls within the claimed exemption, and are not controverted by

either contrary evidence in the record nor by evidence of agency

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Rice v. United States
166 F.3d 1088 (Tenth Circuit, 1999)
Larson v. Department of State
565 F.3d 857 (D.C. Circuit, 2009)
Carl Stern v. Federal Bureau of Investigation
737 F.2d 84 (D.C. Circuit, 1984)
James H. Neal v. Sharon Pratt Kelly, Mayor
963 F.2d 453 (D.C. Circuit, 1992)
Judicial Watch, Inc. v. Social Security Admin.
799 F. Supp. 2d 91 (District of Columbia, 2011)
Wilderness Society v. United States Department of the Interior
344 F. Supp. 2d 1 (District of Columbia, 2004)
Bigwood v. United States Agency for International Development
484 F. Supp. 2d 68 (District of Columbia, 2007)

Cite This Page — Counsel Stack

Bluebook (online)
Argyle Systems Inc. v. Internal Revenue Service, Counsel Stack Legal Research, https://law.counselstack.com/opinion/argyle-systems-inc-v-internal-revenue-service-dcd-2022.