Introduction
ASC 606 is the U.S. GAAP framework that governs when and how much revenue a company recognizes from contracts with customers, tied to the transfer of promised goods or services. For federal government contractors, applying it is rarely simple.
This guide is written for contractors managing cost type arrangements, fixed price deliverables, variable fees, funding limitations, and multiyear programs. These features create genuine accounting judgment calls, not just paperwork.
Revenue timing shapes reported margins, financial statement accuracy, lender and owner reporting, and audit readiness. Many contractors still confuse revenue recognition with billing, funding approval, or cash collection, and that confusion can distort the numbers management relies on.
Below, we'll walk through the five step model, the government contract features that demand extra scrutiny, the mistakes we see most often, and the documentation practices that keep your books defensible.
Key Takeaways
- The five step model requires judgment about enforceable rights, deliverables, and control transfer, not mechanical rule following
- Contract type (fixed price, cost reimbursable, T&M) never determines timing on its own
- Funding status, incentive fees, modifications, and cost estimates can all shift when revenue lands
- Documented contract reviews and updated estimates at completion protect your audit trail
- Billing and funding milestones are separate questions from GAAP revenue recognition
What ASC 606 Means for Government Contractors
ASC 606 creates one consistent framework for recognizing revenue earned from contracts with customers. It generally applies to exchange transactions, meaning arrangements where the government receives goods or services from the contractor in return for payment.
In practical terms, this means you recognize revenue as you transfer promised goods or services, not simply when you invoice or when cash arrives. An invoice submitted under a billing schedule and GAAP revenue recognized under ASC 606 can land in entirely different periods.
Contracts vs. Grants
Not every arrangement with the federal government is an ASC 606 contract. A government grant or cost sharing arrangement, where funding flows without the government directly receiving your goods or services, may fall under different accounting guidance entirely. If your arrangement looks unusual, confirm the applicable guidance before drawing conclusions.
Why Federal Contracts Add Complexity
Federal work introduces judgment calls that commercial contracts rarely require:
- Long performance periods spanning multiple fiscal years
- Multiple deliverables bundled into one award
- Option years and change orders that reshape scope midstream
- Unfunded contract portions sitting alongside funded work
- Award fees, acceptance clauses, and FAR or DFARS specific terms
ASC 606 stays relevant even when you're also managing FAR compliance, Cost Accounting Standards, or DCAA expectations. These frameworks interact, but they answer different questions:
- FAR governs cost allowability
- CAS governs cost accounting consistency
- ASC 606 governs when revenue hits your financial statements
Treating them as interchangeable is where a lot of GovCon accounting goes sideways. At Assured Financial Services, we see this overlap constantly in our DCAA readiness and indirect rate work with contractors managing cost type awards.
How ASC 606 Works: The Five Step Model
The standard works as a sequential analysis. You generally complete contract identification and performance obligation analysis before landing on the timing and amount of revenue you recognize.
Step 1: Identify the Contract with the Customer
A contract exists under ASC 606 when there's approval and commitment from both parties, identifiable rights and payment terms, commercial substance, and probable collectibility. These arrangements can be written, oral, or implied, though federal work is rarely informal.
Government specific wrinkles to watch for:
- IDIQ contracts: A framework agreement alone usually doesn't establish enforceable rights; the task or delivery order typically does
- Undefinitized contract actions: Funded and unfunded portions can both meet contract existence criteria when rights are enforceable, even before final pricing
- Partially funded contracts: Don't assume funding gaps automatically disqualify the arrangement
- Proposal quantities: Notional amounts in a proposal are not the same as a committed order
When a modification adds distinct goods or services priced at standalone value, it may create a separate contract. Otherwise, it typically changes the accounting for the existing one.
Step 2: Identify the Performance Obligations
A performance obligation is a promised distinct good or service, or a series of substantially similar items transferred the same way over time. Distinctness depends on two things: can the customer benefit from the item on its own, and is it separately identifiable from other promises in the contract?
Bundled GovCon deliverables (engineering, hardware, integration, training, maintenance, and software support) require this two part test on each component.
Illustrative example only: Highly integrated systems development work, where engineering and hardware are inseparable, may be one combined performance obligation. Training or ongoing maintenance that the customer could use independently often requires separate analysis. This pattern won't hold for every contract; the facts control.
Step 3: Determine the Transaction Price
Transaction price includes fixed consideration plus any variable consideration you can reasonably estimate. Government contracts carry plenty of variable elements:
- Reimbursable costs and fixed fees
- Award and incentive fees
- Penalties and economic price adjustments
- Funding caps and unresolved change orders
The variable consideration constraint matters here: you only include an estimated amount when it's probable a significant revenue reversal won't occur once the uncertainty resolves.
Funding probability, cost allowability, program performance history, and updated contract data all feed that judgment. Don't invent probability thresholds or performance statistics to support an estimate; tie conclusions back to current contract data and authoritative guidance.
Step 4: Allocate the Transaction Price
You allocate consideration based on relative standalone selling prices. For highly customized government deliverables, directly observable prices often don't exist, so you estimate.
Three estimation approaches show up in practice:
- Adjusted market assessment: evaluate what the market would pay, adjusted for your costs and margin
- Expected cost plus margin: forecast the cost to satisfy the obligation and add appropriate margin
- Residual approach: total transaction price less observable prices of other promises, but only when pricing is highly variable or uncertain, not as a default shortcut
Whichever method applies, document the assumptions. Auditors and reviewers will ask.
Step 5: Recognize Revenue When or As Obligations Are Satisfied
This is where the real timing question gets answered: over time, or at a single point in time?
You recognize revenue over time when any one of these applies, according to Deloitte's revenue roadmap:
- The customer simultaneously receives and consumes benefits as you perform
- You're creating or enhancing an asset the customer controls as it's built
- The asset has no alternative use to you, and you hold an enforceable right to payment for work completed to date
If none of those apply, recognize revenue at the point in time control transfers, often at delivery or acceptance.
For over time recognition, cost to cost is the common progress measure, comparing costs incurred against total expected costs. That means your estimate at completion needs to stay current; stale forecasts distort progress percentages and can mask emerging losses.
An invoice based practical expedient may apply in limited situations where the billed amount directly mirrors value transferred. Confirm it fits your facts rather than assuming it applies automatically to every cost reimbursable arrangement.
How Government Contract Features Affect Revenue Recognition
Contract type sets the stage, but it doesn't decide the outcome. Every example below still runs through the five step analysis above, tied to actual contract terms.
Firm Fixed Price Contracts
Long term development or production work under a fixed price can qualify for over time recognition when the criteria are met. Other deliverables, especially discrete units, may require point in time recognition at delivery or acceptance.
When total expected costs shift, progress measurements, margins, and even loss recognition move with them. Disciplined estimate at completion reviews are essential.
Cost Reimbursable and Cost Plus Contracts
Allowable costs, fixed fees, incentive structures, and indirect rates all feed into the transaction price estimate, but billings are not GAAP revenue.
Separating allowable from unallowable costs under federal cost principles, and reconciling contract, job costing, billing, and financial reporting records, keeps these numbers accurate. This reconciliation work is a core part of what we handle for cost type contractors at Assured Financial Services, alongside Incurred Cost Submission preparation.
Time and Materials Contracts
Revenue tracks services actually performed, approved labor rates, and materials transferred. Contract terms, customer acceptance language, and rate structures still need review before assuming straightforward recognition. T&M pricing and margin visibility are areas where contractors frequently underprice risk, which is why profitability analysis matters as much as the accounting treatment itself.
IDIQ, Unfunded, and Partially Funded Arrangements
A notional quantity or anticipated option year doesn't automatically create an enforceable obligation. Initial orders or definitive funding actions can change that picture. According to RSM's federal contractor guide, unfunded portions may still require evaluation under the variable consideration constraint once contract existence is established. Collectibility and reversal risk both factor in.
Contract Modifications and Options
Change orders, supplemental agreements, option years, and follow on rights can all reshape scope, price, and performance obligations. The accounting lands in one of three buckets:
- Separate contract: when added goods or services are distinct and priced at standalone value
- Prospective treatment: when remaining goods or services are distinct from what's already delivered
- Cumulative catch up: when remaining items aren't distinct from a partially satisfied obligation
The facts of the modification determine the outcome, not a blanket policy.
FMS and DCS Arrangements
Foreign Military Sales and Direct Commercial Sales involve different customer relationships. In FMS, the U.S. government typically sits between the contractor and the foreign partner. In DCS, the contractor negotiates directly with the foreign customer. Each structure raises its own questions about customer identity, enforceability, payment terms, and export reporting, so verify these specifics rather than assuming one model fits both.
Common Issues, Misconceptions, and Control Practices
Some mistakes show up repeatedly in GovCon revenue recognition reviews. Here's what to watch for:
- "Revenue follows cash or funding." It doesn't. ASC 606 ties revenue to performance obligation satisfaction and control transfer, not invoicing or appropriation events.
- "Federal contracts automatically qualify for over time recognition." Each contract still needs the over time criteria tested; percentage of completion isn't a default.
- Treating every deliverable as one obligation. Distinct training, maintenance, software, or integration services often need separate analysis.
- Recognizing award or incentive fees too aggressively. Document your estimate, your constraint analysis, your supporting evidence, and a reassessment date.
- Using stale cost forecasts. Outdated total cost estimates distort progress measures. Build in periodic estimate at completion reviews with accounting, contracts, program management, and operations at the table.
Control practices reduce how often these errors reach the financials. A solid contract review file should include:
- Contract and modifications
- Performance obligation analysis
- Transaction price calculation and allocation rationale
- Recognition method and key judgments
- Supporting schedules and approval history
That file discipline is part of the GovCon accounting support Assured Financial Services builds for contractors, alongside DCAA readiness processes, indirect rate management, financial reporting, and fractional CFO oversight. The support complements your team's judgment and authoritative accounting guidance. It doesn't replace either one.
When ASC 606 Treatment May Require Additional Analysis
Some arrangements fall outside standard ASC 606 treatment entirely, including government grants, best efforts R&D cost sharing arrangements, financing arrangements, or insurance type transactions.
According to BDO's technical guidance, bundled deliverables and principal versus agent questions deserve particular scrutiny in contractor team arrangements and reseller structures.
Flag these situations for deeper technical review:
- Unclear enforceability of rights or payment terms
- Unusual funding provisions or significant modifications
- Principal versus agent questions in teaming arrangements
- Nonstandard acceptance clauses or foreign counterparties
- Conflicting contract language and accounting terms
Legal enforceability, tax treatment, FAR allowability, CAS consistency, and GAAP revenue recognition are related but distinct questions. A quick decision checklist helps:
- Identify the customer
- Confirm applicable literature
- Document enforceable rights
- Map deliverables
- Evaluate consideration
- Select a progress measure
- Set a reassessment cadence
Conclusion
ASC 606 hands government contractors a structured five step model. Getting it right depends on your actual contract terms, deliverables, funding status, and evidence of performance, not a generic playbook.
Reliable revenue recognition supports accurate margins, useful management reporting, audit readiness, and better program and cash flow decisions.
Review your policies and your significant contracts with qualified accounting professionals, particularly where judgment calls are involved. Assured Financial Services offers principal led GovCon accounting support and fractional CFO services for contractors looking to build stronger financial processes and a documented control environment around these decisions.
Frequently Asked Questions
What are the five revenue recognition criteria under ASC 606 for government contractors?
ASC 606 uses a five step model: identify the contract, identify performance obligations, determine the transaction price, allocate that price, and recognize revenue as obligations are satisfied. These are sequential steps, not independent eligibility tests.
Is ASC 606 still relevant for government contractors?
Yes. It remains the primary U.S. GAAP revenue framework for applicable contracts with customers. FAR, CAS, DCAA, and contract specific terms can still affect your processes and documentation alongside it.
How do government contractors recognize revenue under ASC 606?
Recognition depends on when performance obligations are satisfied, either over time or at a point in time. It doesn't depend solely on billing schedules, funding approval, or cash collection.
What is the difference between revenue recognition and billing for government contracts?
Revenue recognition reflects GAAP based timing tied to performance; billing reflects your contract's invoicing terms. The two frequently occur in different periods on the same contract.
When can a government contractor recognize revenue over time?
Over time recognition applies when specific ASC 606 criteria are met, such as an enforceable right to payment for work completed with no alternative use for the asset. You must support your progress measure, like cost to cost, with current and reliable estimates.
How do contract modifications affect ASC 606 revenue recognition?
A modification may be treated as a separate contract, a prospective change, or a cumulative catch up adjustment. The outcome depends on whether the added goods or services are distinct and how they're priced relative to the original obligations.
