Three Tests of Congress's Authority Over Israel Aid

In July 2026, Congress's legal authority over Israel aid is being tested in three places at once. The first is still in court: the 2025–2026 litigation over the Trump administration's freeze of appropriated foreign-assistance funds, where the executive branch claimed broad foreign-affairs discretion against statutes that tell agencies when money must be obligated. The second is on the Hill: the unresolved FY2027 National Defense Authorization Act fight over provisions that would deepen Israel-related defense integration inside Pentagon structures. The third is less dramatic but more durable: the post-2028 move under discussion from traditional Foreign Military Financing grants toward procurement, co-production, joint research, and licensing channels.

The short legal answer is still clear. Congress's authority over Israel aid rests on Article I spending power and the statutes Congress has enacted to authorize, appropriate, condition, and oversee foreign assistance. The bilateral memoranda of understanding with Israel are politically important executive agreements, but they do not substitute for appropriations. As CRS put it in June 2026, the MOUs “do not constitute a binding obligation on the part of the United States government beyond available appropriations.”[1]

That answer does not end the 2026 fight. It only locates it. The question now is whether the legal architecture that has made congressional control meaningful—annual appropriations, Foreign Assistance Act reporting, Arms Export Control Act conditions, State Department administration, Leahy-related review, and committee oversight—will continue to govern the aid relationship if the delivery channel changes.

The Starting Point Is Article I, Not Diplomatic Custom

Foreign aid is often described in the vocabulary of alliance management, deterrence, and presidential diplomacy. Those words matter politically, but they do not appropriate a dollar. The constitutional source of spending authority is Article I. Congress may tax and spend for the general welfare, and the Supreme Court has described that spending authority as broad, including in the foreign-assistance context discussed in Agency for International Development v. Alliance for Open Society International in 2020.[2]

That is why the older practice matters. From Madison's 1812 request for Venezuela earthquake relief through the Marshall Plan, presidents sought statutory authorization for foreign assistance rather than treating aid as a freestanding Article II account. The point is not nostalgia for formalities. It is that foreign assistance has historically been built through laws that identify the object, the account, the conditions, and the officers responsible for execution.[2]

The modern statutory center is the Foreign Assistance Act of 1961, supplemented by the Arms Export Control Act, annual State and foreign operations appropriations measures, defense appropriations measures where relevant, and cross-cutting fiscal statutes. For Israel, the Foreign Military Financing model has usually placed the principal grant-assistance channel within a State Department-administered framework, even when the end-use is military and the downstream contracting involves U.S. defense firms.

The distinction is not cosmetic. A State-administered foreign-assistance account brings with it a particular set of oversight habits: foreign affairs committee jurisdiction, foreign operations appropriations review, Foreign Assistance Act reporting, Arms Export Control Act transfer rules, end-use monitoring, and human-rights conditions. Those mechanisms do not make Congress omnipotent in foreign affairs. They do make it the legal source of the money and the legal source of many conditions attached to the money.

For readers who want the domestic spending-law analogue, the same basic principle appears in grant litigation outside foreign affairs: Congress can fund programs and attach conditions, but the conditions must be rooted in statutory authority and stated with the clarity spending doctrine requires. That point is explored in this site's discussion of Judge Talwani's Spending Clause analysis.

The MOU Does Not Appropriate the Money

The United States and Israel have used multi-year memoranda of understanding to set expectations for security assistance. CRS identifies three recent MOUs: FY1999–FY2008 for $21.4 billion, FY2009–FY2018 for $30 billion, and FY2019–FY2028 for $38 billion.[1] Those figures are politically important because they organize planning on both sides. They are not, by themselves, budget authority.

That is the misconception worth killing early. A bilateral MOU can announce an executive-branch intention to request funds, describe a policy commitment, and shape expectations for defense planning. But unless Congress authorizes and appropriates the funds, agencies do not acquire independent authority to obligate Treasury money merely because the executive signed an understanding with a foreign government. CRS's June 2026 formulation is unusually useful because it states the rule without diplomatic haze: the MOUs do not bind the United States beyond available appropriations.[1]

That also means Congress can argue about the next arrangement without pretending the current one has displaced the appropriations process. House Democratic Leader Hakeem Jeffries's July 2026 statement that the next security arrangement should be “structured consistently with defense agreements that exist with our other Western allies” is legally relevant less for its party positioning than for what it signals about institutional form: the next fight may be over the account structure, committee lane, and statutory conditions of the successor arrangement, not just the headline dollar amount.[1]

The Aid-Freeze Litigation Puts the Conflict in Youngstown Terms

The 2025–2026 aid-freeze litigation is the cleanest separation-of-powers test because it asks what happens after Congress has appropriated foreign-assistance money and the president declines to spend it. The Trump administration's litigating position asserted “vast and generally unreviewable” foreign-affairs authority to pause or withhold foreign-assistance funds. The Supreme Court rejected that position per curiam in March 2025 in the AVAC v. Trump / GHC v. Trump litigation, while related disputes continued over implementation and relief.[2]

The constitutional frame is Justice Jackson's Youngstown concurrence. When the president acts with congressional authorization, executive power is at its maximum. When Congress has been silent, the analysis enters the more uncertain zone of concurrent authority. When the president acts contrary to Congress's expressed or implied will, presidential power is at its “lowest ebb.” In a foreign-aid freeze, the key question is not whether the president has foreign-affairs responsibilities. He does. The question is whether those responsibilities let him disregard statutes governing money Congress has already appropriated.[2]

That is why the Impoundment Control Act matters. Enacted in 1974, the statute gives the president a process for proposing rescissions or deferrals, but it does not let the executive permanently refuse to spend appropriated funds without congressional approval.[2] The Anti-Deficiency Act supplies the complementary fiscal boundary: federal officers may not obligate or expend in excess of, or before, an appropriation. In ordinary appropriations practice, those statutes are not atmospherics. They are the guardrails agency counsel use when policy offices ask whether a program can be paused, accelerated, reprogrammed, or rerouted.

The same discipline applies to Israel aid. If Congress appropriates funds through accounts governed by the Foreign Assistance Act and related appropriations language, the executive branch cannot dissolve those instructions by invoking alliance policy at a higher level of abstraction. Nor can opponents of the aid avoid the statutory question by treating every dispute as a generalized foreign-policy grievance. Once the money is appropriated, the legal analysis runs through the appropriations act, the authorizing statute, the Impoundment Control Act, the Anti-Deficiency Act, and any applicable transfer, notification, or reprogramming provisions.

For a related appropriations-law treatment of the Anti-Deficiency Act outside the Israel-aid context, see this site's discussion of stopgap funding bills and the legal process around shutdown risk.

Conditionality Lives in the Statutory Machinery

Human-rights conditionality is sometimes discussed as if it were an optional political garnish on top of Israel aid. Legally, it is part of the control system Congress built around foreign assistance and arms transfers. The Foreign Assistance Act's Section 502B requires human-rights reporting, and the Arms Export Control Act supplies conditions for defense articles and services. Leahy-related restrictions add another layer by barring certain assistance to units of foreign security forces where the statutory standard is met.[3]

Those mechanisms do not all operate in the same way. Some are reporting rules. Some are transfer conditions. Some attach to assistance for foreign security-force units. Some depend on what funds are used, who receives the benefit, and whether the transaction is an assistance program, a sale, a procurement, or something else. That is why the delivery channel matters. A dollar sent through Foreign Military Financing does not produce the same oversight questions as a Pentagon procurement contract, even if both support the same broad bilateral defense relationship.

The practical consequence is straightforward. Under a foreign-assistance model, the lawyer traces the money through State Department-administered accounts, annual foreign operations appropriations, Foreign Assistance Act authorities, Arms Export Control Act conditions, and committee notification requirements. Under a procurement or co-production model, the lawyer may instead be tracing obligations through Defense Department procurement accounts, research and development authorities, industrial-base arrangements, licensing decisions, and defense committee oversight.

The FY2027 NDAA Fight Is a Live Jurisdictional Flashpoint

The FY2027 NDAA fight should not be treated as a completed statutory shift. As of mid-July 2026, it remained a live legislative fight. Senate Democrats blocked the defense bill on July 14, 2026, amid objections that included provisions associated with Senator Tom Cotton's Israel technology-integration amendments and the broader Iran-war and Israel-integration debate.[4]

The legal significance is not that a pending NDAA provision has already transformed the aid relationship. It has not. The significance is that members are fighting over whether Israel-related cooperation should become more embedded in standing Pentagon structures. Once a program is written into defense authorization and funded through defense appropriations habits, it may be reviewed through a different institutional lens: capability, readiness, interoperability, industrial base, and force protection rather than foreign-assistance policy, diplomatic leverage, or human-rights conditionality.

The House supplied a separate indicator of congressional positioning one day later. On July 15, 2026, the House defeated Representative Thomas Massie's amendment to cut off Israel aid, a vote Reuters described as dividing Democrats.[5] FMEP separately tracked individual member positions on that vote.[6] The vote does not settle the constitutional question, and it does not answer how a post-2028 arrangement will be structured. It does show that Congress is not a silent bystander. Members are placing themselves on the record while the account architecture is being contested.

The Bigger Test Is the Procurement Shift

The most important 2026 issue may be the least visible one: what happens after the FY2019–FY2028 MOU expires. CRS reported in June 2026 that possible changes include a move away from the traditional Foreign Military Financing grant model and toward defense procurement, joint research and development, co-production, and related mechanisms.[1] Quincy Institute analysis similarly describes a possible transition from a visible “aid check” toward Pentagon-centered procurement and industrial arrangements.[7]

This is where formal legal authority and practical oversight can diverge. Congress would still have to authorize and appropriate money. The Pentagon cannot fund a new structure out of sentiment. But if Congress chooses to place more Israel-related support inside defense procurement or research accounts, the annual oversight environment changes. The issue becomes less whether Congress has power and more which part of Congress is exercising it, under which statutes, and with which default questions.

The point is not that defense procurement is lawless. It is heavily regulated. Procurement lawyers, contracting officers, inspectors general, and defense appropriators live in a dense world of statutes, clauses, certifications, audits, and bid-protest risk. But that world is built for a different purpose. It asks whether the government is buying what it lawfully needs, whether the acquisition method is valid, whether funds are available for the bona fide need, whether the contractor is eligible, whether domestic sourcing rules apply, and whether the delivered capability meets requirements. It is not naturally designed to ask the same foreign-assistance questions Congress asks when it conditions aid to a foreign military.

CRS flags one concrete version of that problem: under a procurement model, Leahy Law restrictions may not apply to sales financed solely with Israeli national funds.[1] That is a narrow statement and should be kept narrow. It does not mean every post-2028 procurement arrangement would escape human-rights review. It means that the applicability of particular restrictions can turn on the funding source and transaction structure. A program that looks politically like security support may not trigger the same statutory controls if, legally, it is structured as procurement, co-production, or a sale financed outside U.S. assistance funds.

That difference matters for accountability. In the FMF model, Congress can see the aid line, debate the appropriation, add conditions, require reports, and press State Department officials on compliance. In a procurement-centered model, support may appear as a weapons program, a technology-integration initiative, a co-production line, an R&D project, or a licensing arrangement. The money remains appropriated. The transaction remains legal only if it satisfies the governing statutes. But the oversight file moves, and with it the staff, committee calendar, statutory vocabulary, and institutional memory.

The shift also affects who bears the consequence of ambiguity. Under a foreign-assistance model, State and foreign operations staff can ask whether aid complies with the Foreign Assistance Act, the Arms Export Control Act, reporting requirements, and applicable human-rights restrictions. Under a defense procurement model, agency counsel and contracting officials may instead be asked whether an obligation fits a procurement account, whether the work statement supports a U.S. defense requirement, whether the partner role is properly characterized, and whether the arrangement is a sale, cooperative project, grant-like support, or some hybrid. Those are not minor labeling questions. They determine which statute opens the door and which statute supplies the locks.

What Congress Can Still Control

Congress's formal tools are not fragile. It can authorize or decline to authorize a program. It can appropriate, reduce, fence, condition, or withhold funds. It can specify accounts. It can require notifications before obligations. It can bar transfers. It can demand reports. It can attach human-rights conditions, end-use monitoring requirements, certification requirements, and reprogramming limits. It can decide whether support belongs in State Department foreign-assistance accounts, Defense Department procurement accounts, or some combination.

But each tool has to be placed in the statute that will actually govern the transaction. A condition written for one account may not reach a differently structured program. A reporting rule aimed at assistance may not cover a procurement contract unless Congress says so. A committee notification requirement may lose practical force if the relevant action migrates to a different title, office, or account. The legal authority remains Article I; the enforcement question becomes whether Congress drafted for the channel the executive branch and Defense Department are actually using.

This is the ordinary lesson of appropriations law, but Israel aid makes it unusually visible. Money does not merely move from Congress to an ally. It moves through accounts, apportionments, allotments, obligations, contracts, transfers, notifications, certifications, and audits. At each stage, legal control depends on the words Congress used and the institutional actor assigned to implement them.

The 2026 Answer

As of Q3 2026, Congress still holds the formal legal primacy over Israel aid. The president may negotiate, request, recommend, administer, and conduct diplomacy. The executive branch may sign MOUs that organize future expectations. The Defense Department may propose procurement and co-production structures. None of that supplies independent spending authority without Congress.

The harder issue is whether Congress will preserve the oversight architecture that made that primacy enforceable in practice. The aid-freeze litigation tests whether the executive can refuse to execute appropriated foreign-assistance funds. The FY2027 NDAA fight tests whether Israel cooperation will be further embedded in Pentagon structures. The post-2028 procurement shift tests whether assistance can become less visible as assistance while remaining fully dependent on appropriated money.

The legal center of gravity has not moved from Article I to Article II. But the practical center of oversight may move if future support leaves the familiar foreign-assistance lane and enters defense procurement structures where different committees, different statutes, and different accountability habits dominate.

References

1. Possible Changes in U.S. Military Aid to Israel: Considerations for Congress — Congressional Research Service, June 4, 2026.
2. Foreign Assistance Is Not an Article II Power — Lawfare.
3. Bringing Assistance to Israel in Line With Rights and U.S. Laws — Carnegie Endowment.
4. US Senate Democrats block defence bill over Iran war, Israel integration — Al Jazeera, July 14, 2026.
5. US House defeats bid to cut off Israel aid in vote dividing Democrats — Reuters, July 15, 2026.
6. Members on the Record re: Ending Aid to Israel (7/15/26 House vote on Massie Amendment) — Foundation for Middle East Peace.
7. The Disappearing Aid Check: The Future of US–Israel Defense Support — Quincy Institute.