Three numbers describe federal money flowing to a company, and they almost never agree. An obligation is the government's promise to pay. An outlay is the cash it actually pays. Revenue is what the company counts as earned in its financial statements. Each is recorded by a different party, under different rules, at a different moment.
None of these numbers is wrong. They answer different questions, and knowing which one you are looking at is the first step to reading federal contracting data.
Three numbers, three moments
| Measure | What it is | Who records it | When |
|---|---|---|---|
| Obligation | A binding commitment to pay | The federal agency | When the contract or order is signed |
| Outlay | Cash actually paid out | The Treasury | When the payment is made |
| Revenue | Income the company has earned | The company | As the company performs the work |
An obligation happens when an agency signs a contract, places an order or exercises an option. The government is then legally bound to pay for the work once it is delivered. Federal contract databases, including USAspending.gov, are built mainly on obligations.
An outlay happens when the Treasury actually pays. Payments follow invoices, deliveries or progress milestones, often months or years after the obligation. Outlays, not obligations, count toward the federal deficit.
Revenue is a company's own accounting. Under U.S. generally accepted accounting principles (GAAP), public companies follow the revenue standard known as ASC 606. Most long-term government contracts are recognized "over time": the company books revenue as it performs, often in proportion to the costs it has incurred. Revenue can come before the company bills the government, and well before it is paid.
Where the money starts: budget authority
Before an agency can obligate anything, Congress must give it budget authority, the legal power to make commitments. The most common form is an appropriation.
Appropriations do not all expire at the end of the year. Some funds stay available for obligation for several years, so an agency may obligate money well after Congress provided it. When Congress does not pass appropriations on time, agencies operate under a continuing resolution or, if funding lapses, shut down. Both can delay new obligations.
One obligation, several years of revenue
Suppose an agency signs a contract for three years of work and obligates the full amount up front. USAspending shows a large number in the year of signing. The company recognizes revenue gradually over the three years. In the first year, obligations look far larger than revenue. In the later years, the reverse is true.
Agencies often fund contracts in pieces instead, as appropriations allow. That brings obligations closer to revenue, but the timing still rarely lines up.
Modifications and de-obligations
A contract is rarely fixed after signing. A modification can add work, extend the schedule or change the price. Each one is recorded as a separate transaction with its own obligation amount.
A modification can also take money away. When work is cut, a contract ends early or funds go unused, the agency records a de-obligation, a negative amount. De-obligations can appear years after the original award. A company's net obligations in a given year can therefore be lower than the new work it won that year.
"Contract value" is usually a ceiling
Headlines about contract awards often cite a large "value". That figure is usually a ceiling, not an obligation.
- Options. Many contracts have a base period plus options that the government may exercise later. The headline value often includes every option, whether or not the government ever exercises them.
- IDIQ contracts. An indefinite-delivery, indefinite-quantity (IDIQ) contract sets a maximum the government may spend over its life. Money is obligated only when the agency places individual task or delivery orders. On a multiple-award IDIQ, several companies compete for orders under one shared ceiling.
A ceiling is the most a contract could be worth. Obligations are what the government has committed so far.
Prime contracts and subcontracts
USAspending's contract data records awards to prime contractors, the companies that sign directly with the government. The full obligation is credited to the prime, even when part of the work is passed to other companies.
Those other companies are subcontractors. Primes report their first-tier subawards separately, and that reporting is less complete than prime award data. A company that works mostly as a subcontractor can earn substantial government revenue with modest prime obligations. A prime that passes much of the work on can show obligations well above its own revenue.
Foreign military sales
Under foreign military sales (FMS), a foreign government buys defense equipment or services through the Department of Defense. The Pentagon signs the contract with the U.S. company, and the foreign buyer funds it. In federal contract data, these appear as Defense Department awards.
Companies treat this revenue differently in their 10-Ks. Some count it as U.S. government revenue because the Pentagon is the customer of record. Others count it as international because the buyer is another country. The same contract can be "federal" in one company's disclosure and "international" in another's.
Two calendars
The federal fiscal year runs from October 1 to September 30 and is named for the calendar year in which it ends. Many companies use the calendar year, and others end their year in a different month. Any comparison between federal records and company reports has to pair periods that do not fully overlap.
There is also a reporting lag. Department of Defense contract data is published on USAspending with a 90-day delay, so the latest three months of Pentagon obligations are not yet visible.
What this means for the obligation ratio
On each company page, we divide matched contract obligations by the company's reported U.S. government revenue. We call the result the obligation ratio. It is a cross-check, not a score.
A ratio near 1 suggests the two records roughly agree. A ratio well above 1 can reflect large up-front or multi-year obligations, FMS contracts that the company reports as international, or work the prime passed to subcontractors. A ratio well below 1 can reflect subcontract revenue, classified work that is not in the public record, recent Defense Department awards still inside the reporting delay, or subsidiaries our matching missed. When the ratio falls outside 0.4 to 2.0, we review the company's match before publishing.
How we use these numbers
Company-reported revenue is our primary measure of exposure, because it is what the company itself counts as earned. Contract obligations are a second, independent measure that shows where the money comes from and checks the disclosure. We never present obligations as revenue. Our methodology explains how we match contracts to companies, how we pair fiscal years and how we flag ratios that need review.