Learn Everything You Need to Know About the P/E Ratio and Identify Good Investments

What does percentage of completion mean today?

POC is best understood as a measurement technique, not an automatic accounting policy for every long project. Under Topic 606, an entity first determines whether a performance obligation is satisfied over time. Only then does it measure progress toward complete satisfaction and recognize revenue on that basis. The FASB’s Topic 606 source text identifies both input and output methods as appropriate ways to measure progress, provided the selected method depicts performance.

This framing matters because the old phrase “percentage-of-completion method” can sound as though contract duration alone triggers gradual revenue. It does not. The accounting question is whether control of the promised good or service transfers over time. If the over-time criteria are not met, revenue is recognized at a point in time even when production or construction takes months.

IFRS 15 follows the same central model: for a performance obligation satisfied over time, the entity selects an appropriate measure of progress to determine revenue recognized as performance occurs. The IFRS Foundation’s IFRS 15 overview summarizes that principle. Topic 606 and IFRS 15 are substantially converged on revenue recognition, although differences remain in some areas and entity-specific analysis is still necessary.

When is POC appropriate?

POC is appropriate only after the contract and performance obligations have been analyzed and the relevant obligation qualifies for over-time recognition. Topic 606 describes three broad routes: the customer simultaneously receives and consumes the benefits as the entity performs; the entity creates or enhances an asset the customer controls as it is created; or the entity creates an asset with no alternative use and has an enforceable right to payment for performance completed to date.

A practical eligibility review should therefore answer these questions before any percentage is calculated:

• What distinct good or service is promised, and is it one performance obligation or several?
• Does control transfer continuously, or only when a final asset or deliverable is accepted?
• For a customized asset, can the entity redirect it to another customer without significant economic loss?
• Does the contract and applicable law provide an enforceable right to payment for work completed to date?
• Can progress be measured reliably enough to depict performance rather than spending or billing activity alone?

Which measure of progress should you use?

Use the method that most faithfully depicts the transfer of control to the customer, and apply one method consistently to each over-time performance obligation. Topic 606 groups methods into output methods and input methods, then requires the measure to be updated as circumstances change.

Output methods

Output methods measure results delivered to the customer. Examples in Topic 606 include surveys of performance completed, appraisals of results, milestones reached, time elapsed, and units produced or delivered. They can be persuasive when the output is observable and each unit or milestone represents comparable value. They can mislead when work in process has transferred to the customer but is omitted from the count, or when milestones are weighted for billing convenience rather than economic substance.

Input methods

Input methods measure resources consumed or effort expended relative to total expected inputs. Topic 606 lists costs incurred, labor hours, machine hours, resources consumed, and time elapsed. Cost-to-cost is common because project accounting systems already track costs, but common does not mean automatic. Abnormal waste, rework, inefficiency, or a large purchased item that does not proportionately represent performance may need to be excluded or adjusted so the percentage does not overstate progress.

How do you calculate cost-to-cost POC?

Calculate cumulative progress from eligible costs incurred to date divided by the latest estimate of total eligible costs, then multiply that percentage by the transaction price allocated to the performance obligation. Subtract amounts recognized in prior periods to obtain the current-period revenue.

The denominator is not the original budget frozen at contract signing. It is the best current estimate of the total eligible input needed to satisfy the performance obligation. The numerator and denominator must use the same cost definition. Including procurement in one and excluding it from the other creates a mathematically clean but economically false percentage.

Also separate the measure of progress from the transaction price. Progress answers “how much has been performed?” The transaction price answers “how much consideration is allocated to that performance obligation?” Approved modifications, variable consideration, claims, incentives, penalties, and constraints can affect the transaction price independently of project costs.

What does a complete POC example look like?

Assume a single fixed-price performance obligation with a $1,200,000 transaction price, estimated total eligible costs of $900,000, and eligible costs incurred to date of $360,000. This is an illustrative planning example, not a market benchmark.

The verification check is simple: cumulative revenue plus remaining revenue must equal the current transaction price; cumulative cost plus estimated cost to complete must equal estimated total cost; and cumulative gross profit must equal cumulative revenue minus cumulative recognized cost. A project schedule, cost report, and general ledger should reconcile to the same canonical amounts.

How do estimate changes affect POC?

Estimate changes alter the cumulative result, so the current period absorbs the difference between the newly calculated cumulative amount and the amount already recognized. Topic 606 requires progress to be remeasured at each reporting date, and changes in the measure of progress can produce cumulative catch-up adjustments.

Extend the example. Suppose cumulative costs rise to $450,000 and the latest estimated total cost rises from $900,000 to $1,000,000. Progress is now 45.0%, not 50.0%. Cumulative revenue becomes $540,000, while cumulative gross profit falls to $90,000. Compared with the prior cumulative position of $480,000 revenue and $360,000 cost, the current period records $60,000 of revenue, $90,000 of cost, and a $30,000 gross loss.

That result is not a flaw in the formula; it is the formula revealing margin erosion. Management should investigate the cause rather than override the percentage. Common drivers include labor productivity, material escalation, design revisions, subcontractor performance, schedule extension, unapproved change orders, and underestimated closeout work.

Use a disciplined estimate-at-completion process

A credible estimate at completion should combine actual cost history, committed purchase orders, remaining quantities, current labor productivity, approved scope, expected rework, escalation, contingencies that are appropriate under the accounting framework, and documented assumptions. Project managers should own operational inputs, finance should test accounting consistency, and senior reviewers should challenge large estimate movements and unsupported optimism.

How are revenue, billings, cash, and contract balances different?

Revenue follows performance, billings follow contractual invoicing terms, and cash follows collection. They can move in different periods, so none should be used as a shortcut for the others.

• Revenue is the amount recognized from satisfying the performance obligation.
• Billings are invoices issued under the contract’s billing schedule, which may be ahead of or behind performance.
• Cash collected depends on payment terms, retainage, disputes, and customer behavior.
• A contract asset arises when the entity has transferred goods or services but its right to consideration remains conditional on something other than the passage of time.
• A contract liability arises when consideration is received or due before the related goods or services are transferred.
• A receivable is an unconditional right to consideration, meaning only the passage of time is required before payment is due.

These definitions come from the presentation guidance in Topic 606. They explain why a simplistic “revenue minus billings” schedule can be useful operationally but may not, by itself, determine the correct financial-statement classification. Unconditional receivables are presented separately, and contract-level netting depends on the rights and obligations in the arrangement.

For cash-flow management, compare four curves: cumulative revenue, cumulative billings, cumulative collections, and cumulative cash cost. A profitable project can still consume cash when billing milestones lag performance, retainage is high, or collections are slow. Conversely, advance billings can improve cash while creating a contract liability rather than current-period revenue.

What controls make POC reliable?

Reliable POC depends more on disciplined data and review than on spreadsheet complexity. The strongest control environment creates a traceable chain from contract terms to performance obligations, transaction price, project budget, actual costs, estimate at completion, progress calculation, revenue entry, contract balances, and disclosures.

1. Approve the contract accounting memo. Document the performance obligations, over-time conclusion, measure of progress, and significant judgments.
2. Lock the cost taxonomy. Define which cost categories are eligible inputs and use the same categories in actuals and forecasts.
3. Reconcile source systems. Tie job-cost detail to the general ledger and investigate late postings, duplicate costs, transfers, credits, and unrecorded commitments.
4. Refresh estimates consistently. Require project managers to update remaining quantities, rates, productivity, procurement, subcontractors, and closeout costs on a scheduled cadence.
5. Review exceptions. Flag sharp margin changes, progress that exceeds physical evidence, large unapproved change orders, stalled projects, abnormal waste, and revenue materially ahead of billings or collections.
6. Retain evidence. Preserve contracts, modifications, legal assessments, customer certifications, cost reports, estimate approvals, and calculation versions.

Common mistakes that distort the result

The most frequent errors are inconsistent cost definitions, stale estimates, recording unapproved claims as certain consideration, treating invoices as revenue, including abnormal waste as progress, using procurement-heavy spending as proof of performance, failing to separate performance obligations, and calculating the current period directly instead of deriving it from a cumulative model. Another subtle error is mixing forecast versions: actual cost may be current while estimated cost to complete comes from an older budget.

A useful close checklist asks whether the method still depicts performance, every material estimate change is explained, the transaction price is updated for approved modifications and constrained variable consideration, the project schedule supports the reported stage, and contract assets, liabilities, receivables, billings, and cash are reconciled rather than blended.

Is tax percentage of completion the same as book POC?

No. U.S. federal tax rules and financial-reporting rules have different objectives, definitions, exceptions, and mechanics. A contract may produce one revenue pattern under Topic 606 and another taxable-income pattern under Internal Revenue Code Section 460.

The IRS explains that Section 460 generally requires the percentage-of-completion method for taxable income from qualifying long-term contracts, usually using a cost-to-cost completion factor. The tax definition of a long-term contract focuses on certain manufacturing, building, installation, or construction contracts not completed in the tax year in which they are entered into. The IRS Construction Industry Audit Technique Guide also describes exceptions and specialized methods, so tax treatment cannot be inferred from the book calculation alone.

Section 460 can also require a look-back interest computation after completion for certain contracts. The IRS provides Form 8697 information for the look-back method. Because eligibility, exemptions, cost allocation, elections, and method changes are fact-specific, tax POC should be reviewed separately by a qualified tax professional.

In the financial model, maintain separate book and tax schedules rather than forcing one percentage into both. The difference can create deferred tax effects, cash-tax timing differences, and reconciliation items that matter to liquidity forecasts and covenant planning.

How should management utilize POC?

Management should use POC as a connected operating signal, not merely a month-end revenue entry. The percentage, estimate at completion, margin movement, billing position, and cash position together reveal whether project economics are improving or deteriorating.

Forecast revenue and gross profit

A contract-level POC schedule rolls into monthly revenue, gross profit, backlog conversion, and cash-flow forecasts. Scenario analysis should test changes in total cost, approved scope, timing, productivity, and collection. The model should separate the accounting output from the operational assumptions that drive it.

Detect margin fade early

Track original margin, prior forecast margin, current forecast margin, and realized margin to date. A declining forecast should trigger root-cause analysis and an action owner. Hiding the decline by delaying estimate updates only concentrates the correction in a later period.

Manage billing and working capital

Compare performance with contractual billing milestones before a cash gap appears. When revenue and cost progress faster than billings, management may need better milestone design, faster certification, cleaner change-order documentation, or stronger collection processes. The remedy is commercial and operational; changing the accounting measure is not a cash-management solution.

Prioritize review by risk

Rank projects by forecast loss, margin decline, overdue receivables, unapproved scope, estimate volatility, schedule delay, and revenue-to-billing gap. This directs executive attention to contracts where judgment and cash exposure are greatest rather than applying the same review depth to every project.