Construction revenuerecognition
The contract sets the price.
The contract tells you the price. ASC 606 tells you when it becomes revenue, and by which measure. This guide is the decision layer: the five steps applied to a contractor, the over-time test, the choice between an input and an output measure, and what sits on the balance sheet in between.
What revenue recognition is in construction
Revenue recognition is the decision about when a contract price becomes revenue, and by which measure. Under ASC 606 a contractor recognizes revenue as control of the work transfers to the customer, over time for most building and infrastructure contracts, and chooses an input or output method to measure how much has transferred so far.
That makes it a judgment layered on top of the arithmetic. The percentage-of-completion guide covers the arithmetic once the method is chosen. This page covers the choices that come first: whether the contract qualifies for over-time recognition at all, which measure of progress best depicts the transfer, and how the gap between what has been recognized and what has been billed is classified.
The Financial Accounting Standards Board issued Topic 606 to replace the construction-specific guidance in ASC 605-35, which traced back to SOP 81-1. For most private contractors it took effect for fiscal years beginning after December 15, 2018, with a one-year optional deferral added by ASU 2020-05. The AICPA Revenue Recognition guide carries a dedicated engineering and construction chapter, and CICPAC and CFMA both published implementation guidance, because the industry had more judgment calls to document than almost any other.
The ASC 606 five steps for a contractor
The five-step model asks the same questions of every contract in every industry. For a contractor, steps one through four are usually quick because a construction contract is one enforceable agreement for one integrated deliverable. Step five is where the industry-specific judgment lives: over time or at a point in time, and by which measure.
Walked through on the $36.0M job this guide follows, with a $0.9M pending claim that stays constrained out of the transaction price until it is probable.
| Step | What it asks | On the $36.0M job |
|---|---|---|
| 1. Identify the contract | Is there an enforceable agreement with commercial substance and probable collection? | Signed GMP agreement for $34.2M. Approved change orders are modifications, not new contracts. |
| 2. Identify performance obligations | Which promises are distinct? Most construction contracts are one integrated deliverable. | One performance obligation: the completed building. Site work, structure, and finishes are not separable. |
| 3. Determine the transaction price | Fixed price plus variable consideration you can estimate without a significant reversal risk. | $34.2M plus $1.8M approved COs equals $36.0M. A $0.9M pending claim is constrained out until it is probable. |
| 4. Allocate the price | Spread the price across obligations by relative standalone selling price. | Single obligation, so the full $36.0M attaches to it. No allocation judgment is needed. |
| 5. Recognize as (or when) satisfied | Over time if a transfer-of-control criterion is met, otherwise at a point in time. Then pick a measure. | Over time, on the owner-controlled site. Input measure selected; $6.0M of margin releases as progress is measured. |
Over time or at a point in time
Revenue is recognized over time when any one of three criteria in ASC 606-10-25-27 is met. Work on a site the customer controls satisfies the second criterion, so most construction contracts recognize over time. A contract that meets none of the three is recognized at the single point control transfers, usually handover.
The criteria are a test, not a presumption. Under the old guidance a contractor applied percentage of completion because it was a construction contract. Under ASC 606 the contractor documents which criterion the contract meets, and a speculative build on the contractor’s own land with no enforceable right to payment can fail all three.
The customer receives and consumes the benefit as the entity performs, as with a recurring service.
Rarely the construction path. Maintenance contracts and standing crews can qualify.
The work enhances an asset the customer already controls, such as a structure on the owner’s land.
The usual construction criterion. Work on the owner’s site passes control as it goes in.
The asset is customer-specific and the contractor can demand payment for work done to date, including margin.
Covers fabrication done off-site when termination clauses pay cost plus a reasonable margin.
Choosing the measure of progress
Once a contract recognizes over time, the contractor selects a measure of progress. An input method measures effort consumed, usually cost incurred against total expected cost. An output method measures value delivered directly, such as units installed or surveyed quantities. ASC 606 requires the method that best depicts the transfer of control, applied consistently.
The dominant construction choice because the cost ledger already exists. On the $36.0M job, every dollar of the $30.0M expected cost that goes in carries its share of the $6.0M margin with it. The standard warns the input can overstate progress when cost is incurred without a matching transfer, so uninstalled materials and wasted effort are carved out.
Measures what the customer has actually received: linear feet, units, surveyed quantities, or milestones. More faithful to control, harder to observe between surveys, and the better choice when inputs and delivered value visibly diverge, as on heavy-civil and unit-price work.
The selection is the subject of its own guide: measures of progress, input vs output, including the uninstalled-materials carve-out in ASC 606-10-55-21 and the cases where an output measure is the only honest one. This page stops at the choice.
From recognized revenue to the period increment
Whatever measure is chosen, it produces a cumulative figure: revenue recognized from contract start to the reporting date. The income statement does not want the cumulative figure. It wants the increment this period, and when the estimate behind the measure changes, the whole adjustment lands in the period of the change.
How the increment is derived, why an estimate revision hits one month so hard, and what the period gross margin trend tells you about a job are covered in current-period revenue recognition. Here it is enough to know the decision framework produces a cumulative number and the period figure is a second step.
Contract assets and contract liabilities
Recognized revenue and billed revenue rarely agree on any given date. ASC 606-10-45-1 to 45-4 classify the difference. Revenue recognized ahead of an unconditional right to bill is a contract asset; billings or cash ahead of recognized revenue are a contract liability; a billed amount due only with the passage of time is a receivable.
On the $36.0M job, suppose recognized revenue to date is $16.2M and the owner has been billed $17.0M under the pay application. The $0.8M excess of billings over recognized revenue is a contract liability, presented net for that contract. The reverse case books a contract asset. The job-by-job reporting of these positions is the WIP schedule; this page covers only the classification.
| Position | What it means | Balance sheet |
|---|---|---|
| Receivable | An unconditional right to cash. Only the passage of time stands between you and payment. | Asset. Billed and due under the pay application. |
| Contract asset | Revenue recognized before you have an unconditional right to bill it. Conditional on something other than time. | Asset. Costs and estimated earnings in excess of billings. |
| Contract liability | Cash or billings received ahead of the revenue recognized against them. | Liability. Billings in excess of costs and estimated earnings. |
The recognition decision, drawn as a flow
A contract enters at the left. The first diamond asks whether control transfers over time. The second asks which measure of progress depicts that transfer. The lit path, over time and measured by cost input, is the route most construction contracts take; the point-in-time branch below is where a contract goes when it fails all three over-time criteria.
The $36.0M transaction price is not the revenue story on its own. Recognition releases it as cost goes in, and the cost side has its own structure: subcontracts and their change orders, the general contractor’s direct work, and overhead. What is left is the $6.0M, 16.7% margin that an over-time measure releases across the life of the job. The view below shows that decomposition against billed and paid to date.
Contract Margin
PODRevenue → cost → margin
Project margin
Billing progress
A stored contract vs a read one
Every step of the recognition decision rests on inputs: the contract value, the approved changes, what has been billed, what cost has gone in. The judgment is the controller’s. The quality of the judgment depends on whether those inputs describe this period or the one before it.
- ·The contract sits in a folder; the revised value lives in a spreadsheet
- ·Approved change orders are added to the price by hand at month end
- ·Billed-to-date is copied from the last pay application that was found
- ·The recognition decision is made against inputs that are already a period old
- ·POD reads the pay applications, cost reports, and budget files a job already produces
- ·Contract value, approved change orders, billed-to-date, and cost-to-date stay current per project
- ·The picture a recognition decision is made against is this period’s
- ·The ASC 606 judgment itself stays with your controller and CPA
POD does not make the ASC 606 judgment for you. It reads the pay applications, cost reports, and budget files already moving through a job and keeps the contract value, approved changes, billings, and cost current per project, so the inputs behind the over-time test and the measure of progress are as current as the last file that landed. It pairs with the estimate at completion, the WIP schedule, and percentage of completion. The decision is yours; the inputs should be current.
The revenue recognition library
The pillar above this one: where recognition sits among cost, schedule, change, and earned value on a live job.
Choosing how progress is measured: cost-based or physical, the uninstalled-materials carve-out, and when output is required.
From cumulative recognition to the increment the income statement needs, and the catch-up an estimate change forces.
The mechanics once the input measure is chosen: cost-to-cost percent complete, earned revenue, and profit fade.
Where the contract asset and contract liability positions are reported job by job and reconciled to the ledger.
The forecast total cost that every input measure divides by, and the four methods for keeping it honest.
The full circuit: incurred cost, progress, recognized revenue, billings, and cash, and how each hands off to the next.
Revenue recognition questions
What is revenue recognition in construction?▾
Revenue recognition is the accounting decision about when the price in a construction contract becomes revenue on the income statement, and by which measure. Under ASC 606 a contractor identifies the contract and its performance obligations, sets the transaction price, and then recognizes that price either over time as control of the work transfers or at a single point in time. Most construction work qualifies for over-time recognition, which is why percent complete methods dominate the industry.
Does ASC 606 change how contractors recognize revenue?▾
For most contractors the answer is that the mechanics look familiar but the judgments are now explicit. ASC 606 replaced the construction-specific guidance in ASC 605-35 with a five-step model that applies to every industry. Over-time recognition now has to be earned by meeting one of three transfer-of-control criteria rather than assumed, variable consideration such as pending change orders is constrained until a reversal is unlikely, and uninstalled materials and wasted cost are excluded from an input measure. The outcome is often similar; the documentation and the decision trail are not.
When is revenue recognized over time vs at a point in time?▾
Revenue is recognized over time when any one of three criteria in ASC 606-10-25-27 is met: the customer simultaneously receives and consumes the benefit, the customer controls the asset as it is created or enhanced, or the asset has no alternative use to the contractor and the contractor has an enforceable right to payment for performance completed to date. Work on a site the owner controls meets the second criterion, so most building and infrastructure contracts recognize over time. Speculative or inventory-like builds that fail every criterion are recognized at the point control transfers, usually at handover.
What is the difference between the input and output method?▾
Both are measures of progress toward satisfying a performance obligation. An input method measures effort consumed, most commonly cost incurred as a share of total expected cost. An output method measures the value transferred to the customer directly, such as units installed, milestones reached, or surveyed quantities in place. ASC 606 asks for the method that best depicts the transfer of control and warns that inputs can overstate progress when cost is incurred without a matching transfer, which is why uninstalled materials are carved out. The choice is a judgment, not a default.
What is a contract asset vs a contract liability?▾
A contract asset is revenue you have recognized but do not yet have an unconditional right to bill; the right depends on something other than the passage of time, such as reaching a billing milestone. A contract liability is the opposite: cash or billings received ahead of the revenue recognized against them. On a construction balance sheet these appear as costs and estimated earnings in excess of billings and billings in excess of costs and estimated earnings. They are presented net per contract and rolled up on the WIP schedule.
How does POD relate to revenue recognition?▾
POD does not make the ASC 606 judgment for you; the timing and measure decisions stay with your controller and CPA. What POD does is keep the inputs those decisions rest on current. It reads the pay applications, cost reports, and budget files a job already produces and keeps contract value, approved change orders, billed-to-date, and cost-to-date current per project, so the picture a recognition decision is made against is this period’s, not last quarter’s.
POD keeps the recognition inputs current
Begin with the free budget tracker, then let POD read the pay applications and cost reports already flowing through your jobs, so the contract value, changes, billings, and cost behind every recognition decision are current.