This resolution of inquiry requests that the President, and directs the Secretaries of the Treasury and Homeland Security, to provide the House copies of any documents, records, logs, agreements, or communications that refer or relate to implementation or enforcement of the "Memorandum of Understanding for the Exchange of Information for Nontax Criminal Enforcement" between Treasury and DHS. The request explicitly covers requests by DHS for return information, disclosures or access provided to DHS, specified IRS Systems of Records, internal audit trails, and related policies or procedures, and it requires production within 14 days of adoption, with lawful redactions permitted.
The resolution matters because it pulls at the junction of three high-stakes concerns: congressional oversight of interagency law‑enforcement cooperation, statutory secrecy protections for tax returns under 26 U.S.C. §6103, and operational security for criminal investigations. Compliance will force agencies to inventory technically complex records (including audit logs and systems-of-records material), assess confidentiality obligations, and decide how much to disclose — decisions with practical, legal, and political consequences for agencies, privacy advocates, and affected taxpayers.
At a Glance
What It Does
The resolution requests/directs executive-branch production of any document referencing implementation or enforcement of the Treasury–DHS MOU on nontax criminal enforcement, including specific Systems of Records, audit trails, policies, and records of any alleged violations and remedial actions. It sets a 14-day production window and permits redaction to the extent required by federal law.
Who It Affects
The Department of the Treasury (including IRS systems and records custodians), the Department of Homeland Security, White House offices that review executive-branch document productions, and taxpayers whose return information may have been shared. It also directly engages House oversight staff and legal counsel who will receive and review the materials.
Why It Matters
The request tests how agencies balance 26 U.S.C. §6103 secrecy obligations against Congress's oversight powers, and whether the MOU’s operational practices exposed return information to non‑tax enforcement use. The production could identify compliance gaps, trigger policy changes, and influence future data‑sharing arrangements between tax and law‑enforcement agencies.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The resolution asks for any material that refers to how Treasury and DHS have implemented and enforced their memorandum of understanding about sharing tax return information for nontax criminal enforcement. That includes everyday operational artifacts — emails, memoranda, call logs, written agreements — along with audit trails and system logs that show who requested or accessed data.
By naming the specific Systems of Records, the resolution signals a desire to see the underlying data sources and technical paths by which return information might have flowed.
It also asks for internal policies, procedures, standards, or guidelines that govern handling of that information. Those documents are where agencies codify how they decide what may be shared, who may see it, what safeguards are required, and how disclosures are logged.
Access to those policies lets oversight staff assess whether the actual practices match formal rules and whether internal controls (like audit-logging and access restrictions) are adequate.Finally, the resolution seeks any records related to violations: instances where information may have been shared in a way that contravened 26 U.S.C. §6103 or agency policy, and the subsequent actions taken or considered in response. That captures both detection (audit results, internal reviews) and remedies (discipline, policy changes, referrals).
The text authorizes redactions “to the extent necessary to comply with Federal law,” but it still demands a comprehensive production within a tight 14-day window — a schedule that will require rapid legal review and technical retrieval work by agencies.
The Five Things You Need to Know
The resolution directs the Secretaries of the Treasury and Homeland Security, and requests the President, to furnish relevant documents to the House within 14 days after adoption, permitting redactions only as needed to comply with federal law.
Paragraph (1) explicitly seeks any request by or disclosure to DHS of return information as defined in 26 U.S.C. §6103(b)(2), and it identifies specific IRS Systems of Records (e.g.
Automated Non‑Master File; Information Return Master File; Customer Account Data Engine individual and business master files; Audit Trail and Security Records; Audit Information Management System).
Paragraph (2) requires production of any Treasury or DHS policy, procedure, standard, or guideline that governs handling of the listed return information under the MOU — i.e.
the operational rules that determine permitted sharing and safeguards.
Paragraph (3) seeks records concerning implementation, enforcement, or compliance with those policies, including any disclosure made in violation of §6103 or agency rules, and all subsequent actions taken or considered in response to such violations.
The request covers both substantive documents (agreements, memos) and technical artifacts (audit trails, audit logs, call logs), signaling oversight interest in both policy decisions and the operational record of who accessed or transmitted tax data.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Request and directive; production standard and deadline
The core operative clause both requests (of the President) and directs (of Treasury and DHS) production of documents. It sets a 14‑day deadline from adoption and allows agencies to redact material "to the extent necessary to comply with Federal law." Practically, that means agencies will perform legal reviews for statutory protections (for example, §6103) and privilege claims before turning over responsive records to House staff.
Scope: return information and specified Systems of Records
This paragraph defines the substantive scope by asking for any request by or disclosure to DHS of return information and then lists specific agency Systems of Records by name and Federal Register citations. That naming focuses production on core IRS data stores and logs where requests and disclosures would be traceable, and it signals oversight interest in both the data sets and the metadata that demonstrate access patterns.
Scope: internal policies, procedures, standards, and guidelines
Paragraph (2) demands internal governance documents at Treasury and DHS that pertain to handling the listed information under the MOU. These are the records that clarify authorized uses, access controls, retention rules, and review processes — the practical rules that translate the MOU into day‑to‑day operations.
Scope: violations, compliance reviews, and remedial actions
This paragraph asks for records tied to implementation and enforcement, including any instances where disclosures may have violated §6103 or agency rules, and documents showing detection, follow‑up actions, and consideration of remedies. It pulls for both factual findings (audit results) and decision records (disciplinary memos, policy revisions, or referrals).
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- House oversight staff and relevant committees (e.g., Ways and Means): they receive the documentary record needed to assess whether the MOU and agency practices comply with statutory confidentiality rules and whether policy changes or hearings are warranted.
- Privacy and civil‑liberties advocates: access to internal policies, audit trails, and violation records will inform public debate about taxpayer privacy, the scope of administrative data‑sharing, and whether stronger statutory limits or safeguards are needed.
- Journalists and watchdog organizations: documentary access to emails, logs, and audit records can enable independent investigation into whether IRS return information was used appropriately for nontax enforcement, potentially driving public accountability.
- Compliance officers and agency counsel: if agencies produce policies and logs, these stakeholders gain clarity on practical gaps and can prioritize remediation, training, or technical fixes to shore up controls.
Who Bears the Cost
- Department of the Treasury and the IRS: significant labor and legal expense to locate, extract, and review responsive documents across named systems of records and audit logs, and to perform redaction reviews under §6103 and other confidentiality rules.
- Department of Homeland Security: similar search and review burden for communications and access records, and potential operational impacts if sensitive investigative details must be withheld or redacted.
- Executive Office of the President/White House Counsel: if the President’s records are implicated, White House lawyers will likely spend resources evaluating privilege and deciding what to produce.
- Contractors and third‑party vendors: companies that host or process IRS/DHS systems may need to assist with data extractions and review, incurring technical and contractual costs.
- Law‑enforcement operations more broadly: disclosure or even the prospect of disclosure can complicate ongoing investigations or cause agencies to narrow information‑sharing practices, with operational trade‑offs for interagency cooperation.
Key Issues
The Core Tension
The central dilemma is balancing Congress’s legitimate need for oversight of interagency data‑sharing against statutory tax‑return confidentiality and legitimate law‑enforcement and national‑security concerns; increasing transparency can expose misuse but may also force down operational opacity that law enforcement argues is necessary to protect investigations.
Two practical implementation problems loom. First, the statutory secrecy around tax returns (26 U.S.C. §6103) imposes a legal gatekeeper that requires agencies to redact or withhold identifying taxpayer information; identifying what can be produced in redacted form while still being meaningful to oversight is not straightforward.
Second, the request reaches both policy materials and technical artifacts like audit trails and system logs; assembling those artifacts across legacy and siloed IT systems is technically complex and time‑consuming, especially under a 14‑day clock.
There are also legal and institutional frictions. Agencies may assert privileges or national‑security exceptions for particular records, and the President’s cooperation is framed as a request rather than a directive, creating a potential asymmetry in responses.
Moreover, production could reveal sensitive investigative techniques or ongoing enforcement actions, creating a public‑interest trade‑off between transparency and the integrity of criminal investigations. Finally, the resolution’s focus on specific Systems of Records may prompt agencies to change internal logging or sharing practices prospectively — a compliance effect that can both improve safeguards and degrade useful operational cooperation.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.