Reading the FY2026 US defense budget: which table answers which question?

The FY2026 US defense budget contains a $890.6 billion national-defense authorization and an appropriations measure totaling $839.2 billion for covered defense activities. Adding them would produce a meaningless spending total. They describe different legal instruments and different scopes, with substantial overlap.

The way through the documents is to keep four labels beside every number: fiscal year, scope, legal stage and units. Once those labels are fixed, the tables become much easier to compare. This worked example extends our guide to budget authority and spending by following actual FY2026 figures.

Start with the document, then the total

The Congressional Research Service's FY2026 National Defense Authorization Act (NDAA) funding summary reports $890.6 billion authorized for national defense under Public Law 119-60. Its table covers Defense Department military activities, atomic-energy defense activities and other defense-related programs.

Authorization sets policy and authorizes funding; it does not itself establish that the entire authorized amount has been paid. An appropriation supplies budget authority subject to the law's conditions. Obligations are binding commitments, while outlays are payments. These distinctions are set out in the GAO's federal budget glossary.

CRS's separate appropriations report identifies $839.2 billion in Division A of Public Law 119-75, enacted February 3, 2026. That measure does not encompass every activity in the wider national-defense authorization.

Consequently, subtracting the two headline figures does not establish a funding shortfall across identical programs either. Before making that comparison, reconcile the activities each includes. Military construction and atomic-energy defense illustrate why a broad national-defense total and one appropriations division can differ without describing contradictory accounts.

Compare account rows within the same frame

The following entries come from CRS's Table 1 for the FY2026 defense appropriations measure. Amounts are billions of nominal dollars of budget authority, not cash already spent.

Within this table's frame, procurement increased by $14.4 billion from request to enactment, RDT&E by $3.9 billion, while operation and maintenance decreased by $1.3 billion. These are comparisons between stages, not additional sums to add to the enacted budget.

The account labels describe purposes. Procurement generally concerns acquiring equipment; RDT&E supports research and development; operation and maintenance supports running and sustaining activities. They do not mean that every dollar moves sequentially through all three columns.

The NDAA summary contains a separate authorized procurement figure of $161.7 billion. Its status must remain visible beside it. A reader should not substitute that figure for the enacted appropriation simply because both rows use the word procurement. Nor does an increase in an account establish how many completed systems reached military units.

Follow one small request all the way down

The Office of the Secretary of Defense's FY2026 procurement justification includes a request for $5.322 million for Man Portable Radiation Detector Systems. This is a useful example precisely because the value is small enough to follow without confusing it with a department-wide total.

The justified requirement explains what the department wanted funding to buy. It does not prove Congress retained the exact amount, that a contract was awarded or that detectors arrived. Those later questions require the enacted schedule, the relevant procurement record and delivery evidence respectively.

Units matter at this level. The same amount is $5,322,000, or 5,322 in a table expressed in thousands. Reading a value without the table's unit can create a thousandfold error. A unit-cost calculation also requires a reliable quantity and a clear account of what the line funds; dividing a total by an assumed purchase price invents a delivery count.

The same discipline applies to contract ceilings and initial obligations. They can describe one program at different stages without either being a record of final payments.

Separate future plans from current authority

The Congressional Budget Office's analysis describes a $961 billion FY2026 request that included a $113 billion placeholder drawn from the 2025 reconciliation law. CBO treats that request as a planning document with a mixture of funding sources. The incorporated reconciliation amount is not a second pot to add again to the request total.

Future-year schedules introduce another distinction. A plan indicates expected resources; it does not enact future appropriations. CBO also notes that a FY2026 Future Years Defense Program was not released with that request, limiting the basis for projecting its enduring costs.

Multi-year contracting is a separate mechanism. Federal Acquisition Regulation subpart 17.1 allows qualifying requirements to span more than one program year and provides for funding conditions and cancellation provisions. A multi-year contract can therefore carry commitments and risks that cannot be read from a single year's headline appropriation.

For any claimed purchase, keep the sequence visible: proposed amount, enacted authority, contract obligation and payment. Then add delivery evidence when the question is what the armed forces actually received. That final step is why a procurement announcement and fielded capability belong in different columns.