A loss on a long-term contract is recognized the moment management concludes that total estimated costs will exceed total estimated revenue, and the full anticipated loss is booked immediately, not spread across the remaining life of the project. A contract that is 10 percent complete gets the same treatment as one that is 90 percent complete: as soon as the numbers turn negative, the entire shortfall hits the current period. This is one of the most aggressive acceleration rules in financial reporting, and misapplying it is a common path to a restatement.
Which Contracts This Rule Covers
A long-term contract for these purposes is an agreement for the construction, manufacture, or installation of an asset, or the delivery of related services, that spans more than one normal operating cycle. Construction, defense systems, aerospace, and large engineering projects are the typical examples. The performance obligation is satisfied over time rather than at a single delivery point, either because the customer benefits from the work as it progresses or because the asset has no alternative use to the contractor.
Revenue recognition on these contracts is governed by FASB ASC Topic 606. The loss-recognition rule discussed here draws from the loss contingency framework and longstanding industry practice for construction-type and production-type contracts, and it operates alongside ASC 606’s over-time revenue mechanics.
The Trigger and the Full-Amount Rule
The trigger is simple. At the close of every reporting period, management compares total estimated contract costs (costs incurred plus the best estimate of costs still needed to finish) against the total transaction price agreed with the customer. If costs exceed revenue by any amount, a loss must be recognized.
The amount recognized is the entire anticipated loss, not the portion attributable to work completed. If a $10 million contract now carries estimated total costs of $10.5 million, the full $500,000 loss is recorded in the current period even if only $1 million of work has been performed. There is no option to spread the loss across future reporting periods.
The reasoning is straightforward. Partial loss recognition would leave the contract’s carrying value overstated on the balance sheet and current earnings inflated relative to the economic reality. The immediate-recognition treatment overrides the normal over-time revenue mechanics for the unprofitable portion of the contract; the standard revenue calculation continues for any portion still expected to be profitable, but the full anticipated loss is pulled into the current period.
Recording the Loss
The journal entry has two sides. On the income statement, the entity debits a loss account, often labeled “Loss on Long-Term Contracts,” which reduces net income by the full amount of the anticipated loss.
On the balance sheet, ASC 606 replaced the older “Construction in Progress” and “Billings in Excess” presentation with a contract asset and contract liability framework. For each contract, the entity presents the net position: a contract asset when cumulative revenue recognized exceeds amounts billed, or a contract liability when billings exceed cumulative revenue recognized. When a loss provision is recorded, the credit typically reduces the contract asset or increases the contract liability, so the balance sheet no longer overstates what the contract is worth. Some entities present the provision as a separate accrued liability rather than netting it into the contract asset. Either presentation is acceptable, and the effect on the balance sheet is the same.
Contractors accustomed to the legacy presentation may still use “CIP” terminology internally, but external financial statements must follow the contract asset and contract liability model under ASC 606.
How Bonuses and Penalties Can Create the Loss
Performance bonuses for early completion and penalties for delays are treated as variable consideration under ASC 606, and they flow directly into the revenue side of the loss calculation. The transaction price must be estimated using either the expected-value method or the most-likely-amount method.
One constraint matters here. An estimated bonus can only be included in the transaction price to the extent that a significant reversal of cumulative revenue is not probable when the uncertainty resolves. In practice, entities are usually conservative about pulling bonuses into estimated revenue, but they must include estimated penalties once those become likely. A probable delay penalty reduces total estimated revenue and can push a marginally profitable contract into loss territory on its own.
This is a common failure point. Management teams sometimes leave probable penalties out of the revenue estimate, which makes the contract look healthier than it is and delays the loss that should already have been recognized. Auditors scrutinize the variable consideration estimate closely for exactly this reason.
Reassessing the Loss in Later Periods
The initial loss estimate is not a one-time event. At every subsequent reporting date, management reassesses total estimated costs and total estimated revenue. Material costs shift, labor rates move, scope changes accumulate, and schedules slip. Each reassessment can move the anticipated loss in either direction.
If the Loss Grows
Any increase in the estimated loss is recognized immediately in the period the revised estimate is made. If the earlier $500,000 estimate rises to $700,000, the additional $200,000 is expensed now. The journal entry mechanics are the same: debit to the loss account, credit to the contract asset or accrued liability.
If the Loss Shrinks or the Contract Returns to Profitability
When conditions improve, the entity reverses a portion of the previously recognized loss, but only up to the amount originally recorded. If the $500,000 loss now looks like it will be only $200,000, the $300,000 difference is reversed as a reduction of expense in the current period. There is no mechanism to reverse more than was previously recognized, so a favorable revision cannot create current-period profit out of a prior loss.
If the contract returns to expected profitability, any margin beyond the reversed loss is recognized prospectively through the normal over-time revenue calculation applied to remaining periods. The favorable swing gets folded into the progress measurement going forward rather than booked as a lump-sum gain.
Contract Modifications as a Loss Trigger
Scope changes, change orders, and renegotiated prices are common on long-term projects, and any of them can change the loss calculus. When a modification adds goods or services that are not distinct from those already delivered, the modification is folded into the original contract. The transaction price and the measure of progress are both updated, and the entity records a cumulative catch-up adjustment at the modification date to align previously recognized revenue with the revised terms.
That catch-up can go either way. If a scope increase raises total estimated costs by more than the negotiated price increase covers, the modification can push a previously profitable contract into loss territory. The full anticipated loss must then be recognized immediately, with the modification date as the trigger point.
Disclosure That Goes With the Loss
Recognizing the loss is only half the obligation. Under ASC Topic 275, if it is reasonably possible that the estimate of a contract loss will change materially in the near term, the entity must disclose the nature of the uncertainty and either the estimated range of possible loss or a statement that no estimate can be made. This disclosure applies whether the loss has already been recognized or is still only disclosed as a contingency under ASC Topic 450.
Public companies have more to do. SEC Regulation S-K, Item 303 requires Management’s Discussion and Analysis to address known trends or uncertainties reasonably likely to have a material impact on revenue or operating results. A shift in the cost-to-revenue relationship, whether from rising materials, labor pressure, or a change in schedule, has to be discussed. If the loss recognition rests on a critical accounting estimate, the entity must explain why the estimate is uncertain and how sensitive the reported amount is to the underlying assumptions.
The Tax Rules Are Different
The rules above govern books prepared under GAAP. Federal income tax follows a separate regime under IRC Section 460, and the two systems often produce different timing on the same contract.
Section 460 generally requires the percentage-of-completion method for long-term contracts, allocating income each year based on the ratio of costs incurred to total estimated costs. Because that method relies on estimates that inevitably change, Section 460 also imposes a look-back mechanism. In the year the contract is completed, or in any later year the price or costs are adjusted, the taxpayer reallocates income across all prior open years using actual figures. If taxes were underpaid in earlier years because estimates were too optimistic, the taxpayer owes interest on the shortfall; if they were overpaid, the taxpayer receives interest. The calculation is reported on IRS Form 8697.
Two exceptions narrow the look-back rule. It does not apply to contracts with a gross price at completion of $1,000,000 or less (or 1 percent of the taxpayer’s average annual gross receipts for the three preceding years, if lower) that are completed within two years. Taxpayers can also elect a de minimis exception if cumulative taxable income or loss under the contract stays within 10 percent of the cumulative look-back amount.
Smaller contractors are exempt from the mandatory percentage-of-completion method altogether. For tax years beginning in 2026, contractors whose average annual gross receipts for the three preceding tax years do not exceed $28,415,000 can use cash-basis, accrual-basis, or completed-contract-method accounting for tax purposes. The completed-contract method defers all income and costs until the contract is finished, which can produce very different loss-recognition timing than either GAAP or the tax-code percentage-of-completion method. None of this changes the GAAP obligation to recognize the full anticipated loss in the period it becomes apparent; it only changes when the same loss shows up on the tax return.