Pomegra Wiki

Completed-Contract Method

A contractor working on a three-year dam project recognizes zero revenue in years one and two, then books the entire profit in year three when the project closes. This completed-contract method is conservative and simple, deferring all judgment until uncertainty ends.

All-or-nothing timing

The completed-contract method is the inverse of percentage-of-completion. No revenue, no costs, and no profit are recorded on income statements until a project is fully finished and accepted. The contractor may spend millions and incur years of work, but the financial statements show nothing until the final invoice is paid and the job is done.

This approach is deliberately conservative. It assumes that recognizing revenue before completion introduces too much estimation risk. By waiting until the contract is finished, there is no guessing about final profitability or whether the job will succeed.

How it works

Using the same $10 million warehouse contract from the percentage-of-completion example:

Year 1: The contractor incurs $4.2 million in costs.

  • Revenue recognised: $0
  • Costs recognised: $0
  • Profit: $0

The costs are capitalized as an asset on the balance sheet under contract work-in-progress.

Year 2: The contractor incurs $3.8 million in costs, completing the project and receiving final payment of $10 million.

  • Revenue recognised: $10M (the full contract price)
  • Costs recognised: $8M (all costs from years 1 and 2)
  • Profit: $2M

The entire profit is recorded in year 2, even though half the work was done in year 1.

From an investor’s perspective, the contractor’s financial statements show zero earnings for two years, then a sudden $2M profit in year 3. No smoothing, no interim transparency—just the final result.

When and why it is used

The completed-contract method is less common than percentage-of-completion but appears in specific circumstances:

High uncertainty: If the contractor cannot reliably estimate costs or progress—perhaps the project is novel, technical risk is high, or the client is unpredictable—deferring all recognition until completion avoids false earnings.

Short-term contracts: For jobs finishing within a single reporting period, the difference between methods is moot. A contractor with a six-month contract may use completed-contract because the project ends mid-way through the fiscal year anyway.

Contractor preference for conservatism: Some contractors, especially small firms or those with volatile project outcomes, prefer the cautious approach. There is no management judgment about percentage-complete—just facts: the job is either done or not.

Regulatory or client requirements: Some government contracts or union agreements specify completed-contract accounting. Defence contractors and engineering firms in certain jurisdictions face this mandate.

Under GAAP, completed-contract is acceptable when the contractor cannot make reliable progress estimates. Under IFRS, it is less favoured but still allowed in narrow cases.

Balance-sheet accumulation

Because revenue is deferred, the balance sheet swells. Contract costs are recorded as an asset:

Balance Sheet (Year 1)Amount
Contract work-in-progress$4.2M
(Asset side)
Deferred revenue / Customer advances$0 or partial payment

If the customer makes progress payments (as is common on large projects), cash is credited against the work-in-progress asset. At completion, the asset is liquidated, revenue is recognised, and the profit or loss is booked.

If a contract requires the contractor to front significant costs before payment, this can strain working capital. The contractor may seek progress payments or customer advances to fund the work.

Risks of deferred recognition

The completed-contract method introduces its own hazards:

Loss contracts: If at any point the contractor realises the contract will lose money, the entire expected loss must be recognised immediately—a sharp reversal of the “wait and see” logic. A contractor halfway through a $10M job, with estimates now showing $12M costs, records a $2M loss in that period. This cliff-edge reversal can shock investors.

Earnings volatility: If a firm completes multiple large contracts unevenly across years, reported earnings are lumpy. Year one with no completed contracts shows zero profit; year two with two large project closures shows massive profit. Investors cannot discern underlying operational trends.

Working capital pressure: The contractor funds projects out of pocket for months or years before revenue is recognised. Small firms may lack the cash reserves to sustain this.

Customer disputes: If the job is technically complete but the customer disputes quality or changes scope, recognition may be delayed indefinitely. This ambiguity makes it hard to record final revenue.

Comparison to percentage-of-completion

The two methods aim at the same contract but tell different income-statement stories:

DimensionCompleted-ContractPercentage-of-Completion
Revenue recognitionUpon project completionAs work progresses (over time)
Estimated-profit riskHigh; all contingency in final periodSpread across multiple periods
Income smoothnessLumpySmooth
Interim transparencyLow; no earnings until doneHigh; shows progress-to-date
Working capitalAsset-heavy (deferred receivable)Steady, matched revenue and cost
Loss contractsFull loss recorded immediately upon discoveryLoss adjusted prospectively
Preferred under GAAPRarely; only if estimates unreliableYes, preferred default

Percentage-of-completion has become dominant in modern accounting because it better reflects economic reality: a contractor is earning profit as it works, not only at handoff. Completed-contract persists for niche cases.

The decline of completed-contract

In 2014, the Financial Accounting Standards Board updated revenue-recognition rules (ASC 606), emphasizing recognition “as control of goods or services transfers to the customer.” This shift tilted the standard further toward percentage-of-completion and “over time” recognition. Many contractors who once used completed-contract have since migrated to percentage-of-completion with the new framework.

Completed-contract is now viewed as the exception—appropriate for high-risk, short-term, or genuinely estimable contracts, but not the default for long-term projects.

See also

Wider context