Percentage-of-completion accounting
Lightbridge ERP defines percentage-of-completion accounting as a revenue recognition approach that records revenue and cost on a long-term project as work progresses, rather than waiting until delivery. It is the practical realization of recognizing revenue over time under ASC 606, and it is central to construction, engineering, and government contract accounting.
Percentage-of-completion accounting recognizes revenue as a project progresses.
The percentage-of-completion method records revenue and cost on a long-term contract incrementally, in step with the work, rather than at the end. The logic is straightforward: if a job has consumed a given share of its expected effort or cost, the contractor recognizes that same share of the contract revenue and the matching cost in the period. The aim is to match revenue to the work that earned it, so a multi-year program reports earnings that reflect reality instead of a single spike at delivery.
This stands in contrast to the completed-contract approach, which defers all revenue until a project finishes. Percentage-of-completion suits construction, engineering, professional services, and government contracts, where projects span periods and a deferred picture would distort performance. For organizations that run on contracts and projects, the government project accounting guide sets the wider context for how these numbers flow through the books.
Percentage-of-completion accounting measures progress by input or output methods.
Recognizing revenue over time requires a defensible measure of how far along a contract is. The standards group these into input methods and output methods, and the choice should depict the transfer of value to the customer as faithfully as possible. These are the building blocks of any percentage-of-completion calculation.
Cost-to-cost input method
The most common measure of progress. Recognized revenue tracks costs incurred to date against total estimated costs, so a contract that has consumed forty percent of its expected cost is treated as roughly forty percent complete. ASC 606 classifies this as an input method.
Output methods
Progress measured by results delivered: units produced, milestones reached, or surveys of work performed. Output methods can map more directly to value transferred to the customer, but they require a reliable way to quantify what has actually been delivered.
Estimate discipline
Both methods depend on credible estimates of total cost and total effort. Because revenue moves with those estimates, a change in the estimate flows through earnings, which is why estimate governance matters as much as the bookkeeping itself.
Under ASC 606, percentage-of-completion is recognition over time.
ASC 606, the revenue from contracts with customers standard, did not retire the percentage-of-completion method. It reframed it. The standard first asks whether a performance obligation is satisfied over time. When the answer is yes, the contractor measures progress toward completion and recognizes revenue accordingly, and the cost-to-cost calculation is the usual way that progress is measured. So percentage-of-completion lives on as the mechanism of over-time recognition.
Over-time recognition test
ASC 606 recognizes revenue over time when the customer receives benefit as work occurs, when the work creates an asset the customer controls, or when the asset has no alternative use and the contractor has an enforceable right to payment for work completed. Many project and government contracts meet one of these tests.
Performance obligations
Revenue attaches to distinct performance obligations identified in the contract. A single contract can hold several obligations, and progress is measured for each, which keeps recognition tied to what was actually promised.
Variable consideration
Incentive fees, award fees, penalties, and unpriced change orders are estimated and constrained so that recognized revenue does not include amounts that are likely to reverse. On government work, fee structures and modifications make this a recurring judgment.
Standard text, interpretations, and disclosure expectations evolve. Confirm current treatment with your auditor and the authoritative guidance before applying any of this to a specific contract.
Revenue recognition on government contracts adds variable consideration and compliance.
Government contracts frequently satisfy the over-time recognition tests, because the work often creates an asset the buyer controls or carries an enforceable right to payment for work already performed. Recognition then follows percent complete. What makes government work distinctive is the layering on top: award and incentive fees, penalties, and frequent contract modifications introduce variable consideration that must be estimated and constrained so recognized revenue excludes amounts likely to reverse. Cost-reimbursable, time-and-materials, and fixed-price contracts each behave differently.
Government accounting also layers cost-accounting and indirect-rate requirements on top of revenue recognition, which is where contract and rate discipline meets the books. The DCAA-compliant accounting guide covers those control expectations in depth. Specific clause references, dollar thresholds, and penalty figures change over time, so treat them as items to verify against authoritative sources such as acquisition.gov and current DCAA guidance rather than relying on a number quoted here.
ERP automates percentage-of-completion from cost capture to recognition.
Percentage-of-completion is error-prone on spreadsheets, because it depends on accurate costs to date and a consistent recognition run every period. A project ERP automates the steps that hand calculation gets wrong, producing a faster close and a defensible audit trail. These are the functions that matter most for project and government work.
Project cost capture
An ERP ties labor, materials, subcontractor costs, and overhead to a project and task structure, so costs incurred to date are an accurate number rather than a spreadsheet estimate. That number is the input that cost-to-cost recognition depends on.
Schedules and recognition runs
Configured recognition rules calculate percent complete, post the period revenue and any over or under billing, and produce the journal entries automatically, which reduces manual rework at close and creates a consistent audit trail.
Billing and reporting separation
Project ERP keeps billing milestones distinct from revenue recognition, so cash invoicing and earned revenue can differ without confusion. It also feeds the project, contract, and indirect-rate reporting that compliance-driven work requires.
Platforms such as Deltek Costpoint and Unanet are often named in this space, and other suites support project revenue too. Deltek, Costpoint, Unanet, and any other product names are trademarks of their respective owners, and Lightbridge ERP is independent and not affiliated with, nor a partner program member of, those vendors.
Lightbridge ERP scopes percentage-of-completion needs before recommending a platform.
Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. For project and government accounting, it starts with the requirements: which recognition methods the contracts call for, how billing and earned revenue must separate, what rate and indirect-cost reporting compliance demands, and how variable consideration should be governed. Only then does it assess how candidate platforms support those needs, scored against weighted criteria rather than a brand preference.
What keeps that advice honest is the commercial model. Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, so a recommendation is driven by fit. Where compliance is in play, the work is framed as readiness and advisory: helping an organization stand up the controls and documentation, not asserting any certification on its behalf. A structured ERP selection and ERP consulting are the right starting point for organizations weighing project accounting platforms.
Percentage-of-completion accounting: frequently asked questions
- What is percentage-of-completion accounting in simple terms?
- Percentage-of-completion accounting recognizes revenue and cost on a long-term project gradually, as the work is performed, instead of all at once when the project is finished. If a contractor has completed roughly forty percent of a job, it records roughly forty percent of the contract revenue and the related cost in that period. The method matches revenue to the effort that earned it, which gives a truer picture of a multi-year program than waiting for final delivery. Under current standards it is the way contracts that transfer value over time are recognized. This guide is general information and not accounting, tax, or audit advice.
- How does percentage-of-completion relate to ASC 606?
- Under ASC 606, the revenue standard, percentage-of-completion is best understood as recognition over time. ASC 606 first asks whether a performance obligation is satisfied over time. When it is, the contractor measures progress toward completion and recognizes revenue accordingly. The percentage-of-completion calculation, most often cost-to-cost, is how that progress is measured. So the method did not disappear under ASC 606: it became the mechanism for over-time recognition rather than a standalone standard. Because the standard text and interpretations evolve, confirm current treatment with your auditor and the authoritative guidance before applying it.
- How is percent complete measured?
- Progress is measured with either an input method or an output method. The most common input method is cost-to-cost, where costs incurred to date are divided by total estimated costs to derive percent complete. Output methods instead count results delivered, such as units produced, milestones met, or a survey of work performed. Input methods are easier to operate from cost data an ERP already captures, while output methods can map more directly to value delivered. The choice should reflect which measure most faithfully depicts the transfer of control to the customer, and it should be applied consistently.
- How does revenue recognition work on government contracts?
- Government contracts frequently satisfy the over-time recognition tests, because the work often creates an asset the buyer controls or carries an enforceable right to payment for work performed. Recognition then follows percent complete, while fee structures, award and incentive fees, penalties, and contract modifications introduce variable consideration that must be estimated and constrained. Cost-reimbursable, time-and-materials, and fixed-price contracts each behave differently. Government accounting also layers cost-accounting and rate requirements on top of revenue recognition. Treat specific clause and threshold questions as items to verify against authoritative sources such as acquisition.gov and current DCAA guidance.
- What is the difference between billing and revenue recognition?
- Billing is when you invoice the customer, governed by the payment schedule in the contract. Revenue recognition is when you record revenue as earned, governed by progress toward completion. The two rarely match in the same period, which produces costs and estimated earnings in excess of billings when you have earned more than you have billed, or billings in excess when you have invoiced ahead of the work. Tracking that difference is a core reason project organizations move off spreadsheets and onto an ERP that keeps billing milestones and recognition rules separate.
- Where does ERP automate percentage-of-completion?
- An ERP automates the parts that are error-prone by hand. It captures project costs from labor, materials, subcontractors, and overhead, calculates percent complete from those costs against the estimate, runs scheduled recognition to post period revenue and any over or under billing, and generates the supporting journal entries and audit trail. It also separates billing milestones from earned revenue and feeds project, contract, and rate reporting. The result is a faster close and a defensible record, which matters most on compliance-driven and government work. Lightbridge ERP advises on configuring these controls without committing to any single platform.
- Does Lightbridge ERP recommend a specific project accounting platform?
- No. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. It evaluates platforms against weighted requirements rather than steering toward one product, and it accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, so a recommendation is driven by fit. For project and government accounting it scopes recognition methods, rate structures, and reporting needs first, then assesses how candidate platforms support them. Where compliance is in play, Lightbridge frames the engagement as readiness and advisory work rather than asserting any certification on the client's behalf.
This guide is general information only and is not legal, audit, tax, or accounting advice. Revenue recognition and government contract rules change and depend on facts specific to each organization. Confirm treatment with a qualified professional and the authoritative sources before acting.
From understanding the method to running it in your ERP.
When the question shifts from how percentage-of-completion works to which platform should run it, Lightbridge ERP scopes the requirements and selects neutrally.