Revenue Recognition for Government Contracts

Most mid-market government contractors recognize revenue in a way that is approximately correct, has never been audited, and rests on judgments nobody has written down. That works until someone with an incentive to look closely arrives — a lender, an auditor, or a buyer's quality of earnings team — at which point the accumulated judgments get re-examined all at once, and the restatement lands in the middle of a transaction.

The Framework

ASC 606 governs revenue from contracts with customers, and the government is a customer like any other. The model has five steps: identify the contract, identify the performance obligations within it, determine the transaction price, allocate that price to the performance obligations, and recognize revenue as each obligation is satisfied.

The step that consumes the most judgment in GovCon is the second — determining what the performance obligations actually are — and the step with the most financial consequence is the fifth.

Identifying the Contract, Which Is Harder Than It Sounds

An IDIQ vehicle is generally not itself a contract under ASC 606, because it creates no enforceable rights to specific goods or services. The task orders issued under it typically are. This distinction is not academic — it determines what enters the contract balance and what may be disclosed as backlog.

Funding modifications raise a related question. A contract funded incrementally may have enforceable rights only to the extent of funded value, which affects the transaction price and, on cost-type work, the interaction with limitation of funds provisions. Contractors who recognize against total contract value where only a portion is funded are recognizing against a right they may not have.

Over Time Versus at a Point in Time

Most government services work qualifies for recognition over time, generally because the customer simultaneously receives and consumes the benefit as the contractor performs, or because the contractor's performance creates an asset with no alternative use and there is an enforceable right to payment for performance completed to date. That last criterion fits government contracts unusually well, given termination for convenience provisions that entitle the contractor to costs incurred plus profit on work performed.

The measurement method then matters:

• Cost-to-cost input method. Progress measured as costs incurred over total estimated costs. The default for fixed-price development and construction-like work, and entirely dependent on the quality of the estimate at completion.
• Time elapsed. Appropriate for level-of-effort services delivered ratably.
• Direct measurement of output. Units delivered, milestones achieved, where those genuinely reflect progress.
• Right to invoice practical expedient. Where the contractor's right to consideration corresponds directly to the value transferred, revenue may be recognized in the amount invoiced. This is why most T&M and cost-reimbursable work recognizes at essentially the billing amount, and it is a legitimate simplification rather than a shortcut.

Estimates at Completion

Under the cost-to-cost method, the estimate at completion drives revenue directly. Revise the EAC upward and cumulative revenue recognized to date falls, producing a catch-up adjustment in the current period. Revise it downward and revenue is pulled forward.

This creates a well-known pressure point. EAC revisions are judgments, they are made by program managers who are also accountable for program performance, and their financial effect is immediate. The controls that matter are unremarkable and frequently absent: EACs reviewed on a defined cycle rather than when convenient, revisions documented with a stated cause, finance participating in the review rather than receiving the output, and a loss provision recognized promptly and in full when a contract is expected to lose money.

A contractor whose EAC revisions cluster suspiciously at period ends, or whose loss contracts were recognized late, will have those patterns identified in diligence. The adjustment is not the main cost — the credibility damage is.

Variable Consideration

Award fees, incentive fees, and unpriced change orders are variable consideration. ASC 606 requires estimating the amount and including it in the transaction price only to the extent it is probable that a significant reversal will not occur when the uncertainty resolves.

In practice contractors err in both directions. Some recognize award fee at target from day one, which is aggressive where the award history does not support it. Others recognize nothing until the fee determination arrives, which understates revenue and creates lumpy earnings that a buyer will normalize anyway. Neither is a disaster; both are questions that get asked.

Unpriced change orders and requests for equitable adjustment are the more dangerous version. Recognizing revenue on a claim the government has not agreed to requires genuine support for enforceability and collectibility, and claims recognized in revenue but never collected are a recurring diligence finding.

Contract Assets, Unbilled, and What Buyers Look At

A contract asset arises when revenue has been recognized but the right to payment is conditioned on something beyond the passage of time. A receivable arises when the right is unconditional. Unbilled receivables sit in this space and are the balance most likely to attract attention.

Buyers examine unbilled for a simple reason: it is where revenue recognized in excess of billing accumulates, and it ages. The specific questions are whether the balance is growing faster than revenue, how old the oldest components are, why they have not been billed, and whether the underlying amounts are actually billable and collectible.

Large aged unbilled balances have several possible explanations — retainage, milestone timing, funding delays, contract closeout lag, disputed amounts, or simple billing failure. Two of those are working capital timing and the rest are revenue quality problems. Diligence will determine which, and a contractor who cannot age its own unbilled by contract with reasons will not control that narrative.

The Preparation That Pays

The contractors who come through revenue diligence cleanly share a small set of practices. Written revenue recognition policy documenting the method selected for each contract type and why. EAC review on a defined cycle with documented revisions and stated causes. Loss provisions recognized when identified rather than when unavoidable. Unbilled aged by contract with explanations. And where the company has any realistic transaction horizon, an audit — because the difference between reviewed and audited financial statements shows up directly in how much of the buyer's diligence budget is spent questioning the revenue line.