Leak Check Identify the likely profit or tax leak to validate first.See what you get

Revenue Recognition for Project-Based Service Businesses: Milestones, WIP, and Billing

Light layered-progress pattern beside the two-color title Revenue Recognition for Project-Based Service Businesses.

An invoice is a request for payment. It is not proof that revenue was earned in that month.

A project milestone is evidence that something happened. It is not automatically an accounting performance obligation. “Work in progress” may mean operational effort, a contract asset, deferred cost, or an informal project-management label depending on how the company uses the term.

Revenue recognition for a project-based service business starts with the customer contract and the transfer of promised services—not the invoice schedule, cash receipt, internal percent-complete opinion, or budget target. This article provides a management framework, not an accounting conclusion for a specific contract. A qualified CPA or technical accountant should establish and document the company's policy under applicable U.S. GAAP, tax, lender, and reporting requirements.

Keep four project clocks separate

Every material project should show four cumulative views:

  1. Delivery: What promised service has transferred to the customer?
  2. Revenue: How much consideration is recognized under the accounting policy?
  3. Billing: How much has become billable and been invoiced under the contract?
  4. Cash: How much has actually been collected?

Those amounts can differ without an error.

Suppose a firm signs a $360,000 project, collects a $90,000 deposit, bills another $60,000 at a milestone, and has recognized $126,000 of cumulative revenue under its approved policy. At that date:

  • Cash collected: $90,000.
  • Cumulative billing: $150,000.
  • Cumulative revenue: $126,000.
  • Receivable before other adjustments: $60,000.
  • Billing above recognized revenue: $24,000, generally presented as a contract liability when the relevant accounting criteria are met.

The exact balance-sheet presentation depends on the contract and accounting policy. The key is that revenue, invoice, receivable, deposit, and cash are not synonyms.

Use the five-step revenue model

The Financial Accounting Standards Board's Topic 606 core principle is to recognize revenue in a way that depicts the transfer of promised goods or services in the amount the entity expects to be entitled to receive. FASB summarizes five steps:

  1. Identify the contract with the customer.
  2. Identify the performance obligations in the contract.
  3. Determine the transaction price.
  4. Allocate that price to the performance obligations.
  5. Recognize revenue when or as each performance obligation is satisfied.

These are accounting assessments, not labels the sales team can choose after signing. A statement of work may contain several phases but one performance obligation. One invoice may cover several obligations. A milestone may be only a payment event.

The controller or CPA should maintain a revenue memo or policy record for material contract types showing the conclusion, evidence, judgments, progress method, variable consideration, modification treatment, and journal-entry logic.

Step 1: confirm there is an accounting contract

Management should collect:

  • Executed master agreement, statement of work, and approved changes.
  • Parties' rights and payment terms.
  • Commercial substance and collectibility assessment.
  • Termination, refund, acceptance, cancellation, and renewal provisions.
  • Customer credit and dispute history.

A sales opportunity or unsigned proposal is not a contract. A signed document also may require further assessment if rights, price, approval, or collectibility are unclear. Do not let the project system start recognizing revenue simply because a status changed to “won.”

Step 2: identify promises, not billing lines

Assume a digital implementation includes discovery, configuration, data migration, training, and post-launch support. The accounting team must assess which promised services are distinct and which combine into one performance obligation.

Ask:

  • Can the customer benefit from the service on its own or with readily available resources?
  • Is the promise separately identifiable in the contract context?
  • Is the firm providing one integrated outcome rather than several independent deliverables?
  • Does one task significantly modify, integrate, or depend on another?

Do not assume every project phase is separate because it has its own budget. Do not assume the entire contract is one obligation because sales quoted one total fee.

Steps 3 and 4: determine and allocate the transaction price

Start with fixed consideration, then identify potential variable amounts such as bonuses, penalties, credits, usage, volume, refunds, service levels, or disputed change orders. The accounting policy must address when and how variable consideration is included and constrained.

If a contract has multiple performance obligations, allocate the transaction price using the applicable standalone-selling-price approach. Internal labor budgets or invoice percentages do not automatically establish that allocation.

This is where a commercial change can become an accounting problem. A “free” added deliverable may change the promises or allocation even when the contract value stays fixed. The scope-creep margin model helps management price the work; the technical accountant determines the revenue effect.

Step 5: decide over-time or point-in-time recognition

FASB's implementation guidance explains that an obligation is recognized over time only when it meets an over-time criterion. Otherwise, revenue is recognized at the point in time when control transfers.

For a project recognized over time, select a method that faithfully depicts progress and apply it consistently. Depending on the service and evidence, that may use an output measure such as accepted units or an input measure such as appropriate labor hours or costs.

The CFO should not choose the method that produces the smoothest earnings. The method must describe performance.

Milestone billing can align with revenue by design, but it does not make the two equal. A 40% invoice on contract signing may fund mobilization without representing 40% delivery. A 30% invoice on final acceptance may lag substantial service already transferred.

Before committing more cash or adding another fix, book a free 20-minute Profit & Tax Leak Check to see which part of the financial model is creating the biggest leak.

Worked example: progress, revenue, billing, and margin

Assume the company's CPA concludes that a $360,000 service engagement contains one performance obligation satisfied over time. The approved input method uses eligible delivery cost because it faithfully depicts progress. Expected total eligible cost is $240,000.

At month-end, eligible cost incurred is $84,000:

$84,000 ÷ $240,000 = 35% progress

Cumulative revenue is:

$360,000 × 35% = $126,000

Cumulative gross profit before other project or company cost is:

$126,000 − $84,000 = $42,000

Now compare the separate clocks:

Project view Cumulative amount
Recognized revenue $126,000
Eligible delivery cost $84,000
Gross profit under the approved measure $42,000
Invoices issued $150,000
Cash collected $90,000

These are hypothetical inputs. The example assumes the contract, performance-obligation, transaction-price, over-time, progress-method, and cost-eligibility conclusions have already been established by a qualified accountant.

Estimates to complete can change prior-looking margin

In the next period, suppose cumulative eligible cost reaches $120,000 and the latest expected total cost rises from $240,000 to $300,000 because the original scope and delivery plan were underestimated.

Progress becomes:

$120,000 ÷ $300,000 = 40%

Cumulative revenue under the simplified example becomes:

$360,000 × 40% = $144,000

Cumulative gross profit is now only:

$144,000 − $120,000 = $24,000

The project moved forward, revenue increased by $18,000 from the prior snapshot, and cumulative gross profit fell by $18,000. That is why a stale denominator can overstate revenue and margin.

Every project forecast should maintain:

  • Original budget.
  • Approved changes.
  • Actual eligible inputs to date.
  • Current estimate to complete.
  • Latest total expected cost.
  • Current transaction price and variable consideration.
  • Revenue recognized to date.
  • Billed, unbilled, collected, and remaining amounts.
  • Forecast final contribution and cash.

The job-costing model for service businesses explains how to build dependable loaded cost and estimate-to-complete records. Accounting policy determines which inputs belong in a progress measure.

Define WIP instead of using the word as an account

Teams often call several things WIP:

  • Time and cost recorded on an open project.
  • Earned revenue that is not yet billable.
  • Work performed but not yet approved.
  • Deferred contract-fulfillment cost.
  • A contract asset.
  • A billing schedule report.

Give each measure a separate name. Under Topic 606, a receivable is generally an unconditional right to consideration except for the passage of time. A contract asset is a right conditioned on something other than only time, such as further performance. A contract liability reflects consideration received or due before the related service is transferred.

Do not book an operational WIP report directly into a contract asset account without reconciling it to the accounting policy. Keep the operational cash-gap schedule separate so this accounting-policy decision is not overloaded with billing and collection questions.

Change orders need commercial and accounting control

For each scope change, record:

  • Customer request and date.
  • New or revised promise.
  • Price and payment effect.
  • Approval status and enforceable rights.
  • Delivery cost and schedule effect.
  • Whether the accounting treatment is a separate contract, termination and replacement, or modification of the existing contract under the applicable guidance.
  • Revenue, billing, forecast-margin, and cash effect.

Operations may begin emergency work before the signed change arrives. That creates commercial, collection, margin, and revenue-recognition risk. Use an exception process with named approval; do not let finance silently assume the disputed amount will become revenue.

Reconcile the project subledger to the general ledger

At every close:

  1. Lock time, expense, procurement, and approved project data for the period.
  2. Update estimates to complete and transaction-price judgments.
  3. Calculate revenue under the documented contract policy.
  4. Reconcile cumulative revenue, billing, receivables, cash, contract assets, and contract liabilities.
  5. Post current-period entries and retain the rollforward.
  6. Tie project totals to the general ledger and financial statements.
  7. Review large margin, unbilled, deferred, change-order, and collectibility exceptions.

A good rollforward explains movement from opening to closing balances. A spreadsheet that simply overwrites last month's cumulative calculation destroys the audit trail.

What the CFO should use the numbers to decide

Revenue recognition is an accounting requirement, but the connected project record supports operating decisions:

  • Is delivery ahead of or behind billing?
  • Is a growing contract asset likely to become billable and collectible?
  • Did margin change because of scope, price, mix, productivity, or estimate-to-complete revisions?
  • Does a milestone fund the work before payroll is due?
  • Which projects need a change order, collection action, staffing change, or executive decision?
  • Can the business hire or distribute cash without treating deferred billing as available money?

The rolling thirteen-week cash-flow forecast should use expected invoice and collection dates independently from revenue recognition. Accrual profit does not pay payroll unless the billing and cash clocks follow.

Who owns what

Layer Primary owner Required contribution
Contract and scope Sales, delivery, legal Executed terms, promises, rights, changes, and evidence
Accounting conclusion Controller and qualified CPA Topic 606 policy, judgments, calculation, entries, and disclosures
Project forecast Project leader and finance Actual inputs, estimate to complete, final margin, schedule, and risk
Billing and collection Operations, billing, and A/R Invoice eligibility, support, disputes, and expected cash date
Decision model CFO and leadership Connect revenue, margin, working capital, capacity, and cash

A fractional CFO should not replace the technical accountant or auditor. The CFO should make sure the accounting conclusion, project forecast, billing schedule, and cash plan reconcile and lead to a decision.

Sources

Fractional CFO support can help a project-based firm build that operating layer around an approved revenue policy. The Profit & Tax Leak Check can identify whether stale estimates, unapproved scope, billing lag, project cost, collections, tax timing, or cash commitments are distorting the financial picture.

Frequently asked questions

When should a project-based service business recognize revenue?

Under an approved Topic 606 policy, recognize revenue when or as the business satisfies identified performance obligations and transfers promised services to the customer. The contract, transaction price, allocation, over-time or point-in-time conclusion, and progress method require documented accounting analysis; an invoice, milestone, or cash receipt does not decide revenue by itself.

Is milestone billing the same as milestone revenue recognition?

No. A milestone may establish when the company can invoice without proving that a distinct performance obligation was satisfied or that control transferred in the same amount. Maintain separate cumulative delivery, revenue, billing, receivable, and cash views, then reconcile their differences under the documented contract policy.

What is the difference between a contract asset and a receivable?

A receivable is generally an unconditional right to consideration except for the passage of time. A contract asset is conditioned on something else, such as further performance. A qualified accountant should apply the exact contract terms and accounting guidance rather than posting an operational WIP report directly to either balance.

Why should you keep four project clocks separate?

Those amounts can differ without an error. The exact balance-sheet presentation depends on the contract and accounting policy. The key is that revenue, invoice, receivable, deposit, and cash are not synonyms.

Why should you use the five-step revenue model?

These are accounting assessments, not labels the sales team can choose after signing. A statement of work may contain several phases but one performance obligation. One invoice may cover several obligations. A milestone may be only a payment event.

In step 1, how do you confirm there is an accounting contract?

A sales opportunity or unsigned proposal is not a contract. A signed document also may require further assessment if rights, price, approval, or collectibility are unclear. Do not let the project system start recognizing revenue simply because a status changed to “won.”

In step 2, how do you identify promises, not billing lines?

Assume a digital implementation includes discovery, configuration, data migration, training, and post-launch support. The accounting team must assess which promised services are distinct and which combine into one performance obligation.

In steps 3 and 4, how do you determine and allocate the transaction price?

Start with fixed consideration, then identify potential variable amounts such as bonuses, penalties, credits, usage, volume, refunds, service levels, or disputed change orders. The accounting policy must address when and how variable consideration is included and constrained.