Unbilled Revenue in a Service Business: WIP, Accrued Revenue, and the Cash Gap

Revenue can be earned before it can be billed. Payroll still cannot be paid with it.

That timing difference is common in project-based service businesses. A team may complete work this month while the contract permits billing only after a milestone, customer acceptance, supporting document, or later phase. The income statement can show progress while the bank account carries the cost.

Unbilled revenue in a service business therefore needs two kinds of discipline. Accounting must determine whether earned revenue qualifies as a contract asset under the company's approved policy. Operations must identify exactly what prevents invoicing, who owns the next action, and when the related cash can realistically arrive. Calling every unfinished or unbilled item “WIP” hides both questions.

Start with the four balances people confuse

These terms should not be used interchangeably:

Balance	What it means	Immediate management question
Operational WIP	Work started or completed according to the delivery system	Is the work valid, in scope, and supported?
Contract asset	Recognized revenue for which the right to payment is still conditional on something other than time	What remaining condition must be satisfied?
Receivable	An unconditional right to consideration, subject only to the passage of time	Was the invoice issued correctly, and when will it be collected?
Deferred or contract liability	Cash or a bill received before the related service is transferred	What delivery obligation remains?

An operational WIP schedule is evidence, not an accounting conclusion. A project manager's “90% complete” estimate may be useful for delivery planning but insufficient to support revenue. Conversely, a valid contract asset can exist even when an invoice cannot yet be sent.

The approved project revenue-recognition policy should decide when revenue is earned. This article begins after that conclusion: it focuses on the balance that has been earned but remains unbilled and the cash exposure it creates.

Reconcile earned, billable, billed, and collected amounts

Build one cumulative rollforward for each material contract or project:

Recognized revenue to date
– Amount billable under the contract to date
= Earned but not yet billable

Amount billable to date
– Invoices issued to date
= Billable but not yet invoiced

Invoices issued to date
– Cash collected to date
= Open receivables

The first difference is usually the core contract-asset or unbilled-revenue question. The second is an execution problem: finance could invoice but has not. The third is a collection problem. Combining all three into “unbilled” prevents the right owner from acting.

Add beginning balance, current additions, transfers to receivables, credits or reversals, write-offs, and ending balance. A rollforward exposes whether the balance is clearing or merely being replaced by new additions.

Give every unbilled item a reason code

An aging report is much more useful when every balance has one primary blocker:

• Contract milestone not yet reached.
• Customer acceptance or approval pending.
• Required deliverable, report, timesheet, receipt, or certification missing.
• Change order or scope amendment unsigned.
• Billing period not yet open.
• Customer portal, purchase order, vendor setup, or submission rule incomplete.
• Internal review or invoice preparation delayed.
• Dispute, quality issue, or rework unresolved.
• Accounting estimate or revenue conclusion under review.
• Data error, duplicate record, or unsupported balance.

Use specific reason codes rather than “timing.” Timing does not say whether the team should complete work, secure a signature, obtain a purchase order, prepare an invoice, reverse unsupported revenue, or escalate a dispute.

For each line, record the amount, project, customer, original recognition period, age, remaining condition, next action, owner, due date, expected invoice date, payment terms, and expected collection date. Preserve a link to the contract and supporting evidence.

Age unbilled revenue from the correct date

Receivable aging normally starts from an invoice or due date. Unbilled aging should start from the date the revenue was recognized or the related service was transferred.

That makes a 75-day-old unbilled balance visible even if no invoice exists. It also prevents a stale contract asset from appearing “current” on the day it finally transfers to accounts receivable.

Useful aging bands depend on the engagement cycle, but the principle is consistent:

• Expected: within the normal contract-to-billing interval.
• Watch: outside the normal interval but supported by a dated clearing event.
• Escalate: blocked by approval, documentation, scope, dispute, or internal delay.
• Accounting review: unlikely to become billable as recorded or no longer supported.

Do not use the same day thresholds for a weekly time-and-materials engagement and a six-month milestone contract. Measure actual normal clearing time by contract type, then investigate exceptions.

The next move should follow the numbers, not the loudest symptom. Use a free 20-minute Profit & Tax Leak Check to identify the financial constraint that deserves the first decision.

Calculate the cash gap separately from the accounting balance

The unbilled amount is not automatically the amount of cash at risk. The business has already funded some combination of labor, contractors, travel, materials, and overhead, while collections may still be weeks or months away.

A practical exposure view is:

Cash funded on earned unbilled work
+ Cash required before the invoice becomes eligible
+ Cash required during customer payment terms
– Customer deposits or advance funding attributable to the work
= Estimated cash gap

Suppose a firm recognizes $120,000 of revenue on an engagement. It has funded $72,000 of direct and attributable cash cost. Another $18,000 must be spent before the billing milestone, and the customer normally pays 40 days after a valid invoice. The $120,000 contract asset is an accounting balance; the operating question is whether the company can carry at least the funded and remaining cash cost through the expected collection date.

Put the expected invoice and receipt dates into the thirteen-week cash-flow forecast. Do not place unbilled revenue into a cash week simply because the revenue was recognized. The forecast should include contract conditions, invoice preparation time, customer validation, stated terms, and actual payment behavior.

Track conversion, not just the ending balance

A stable unbilled balance can still hide deteriorating performance. New additions may be offsetting equally large clearings, or old balances may be sitting untouched beneath normal current activity.

Use a small set of operating measures:

1. Unbilled revenue as a percentage of trailing revenue. A scale measure, not a verdict.
2. Days from recognition to invoice. Track median and older exceptions by contract type.
3. Conversion in period. Beginning unbilled balance transferred to receivables during the month.
4. Over-age concentration. Dollars and percentage beyond the normal billing interval.
5. Blocked amount by reason and owner. The action queue.
6. Expected cash date variance. Difference between the prior forecast and current expected receipt.
7. Reversal or write-down rate. A signal that original estimates, scope control, or support may be weak.

The cash conversion cycle becomes more informative when the pre-invoice interval is measured rather than disappearing before days sales outstanding begins.

Hold a weekly conversion review

The review should be a working session, not a presentation of totals. Sort material items by expected invoice date, age, and risk. For each exception, answer:

• What condition prevents billing today?
• Is the underlying revenue still supported?
• What evidence is missing?
• Who can remove the blocker?
• What is the next dated action?
• When should the invoice be accepted as valid by the customer?
• When should cash arrive under realistic behavior?
• What changes in the cash forecast if either date slips?

Project leadership should own delivery evidence and customer dependencies. Billing should own invoice readiness and submission. The controller should own the accounting rollforward and reconciliation. The CFO should connect material delays to liquidity, capacity, hiring, debt, and distribution decisions.

Prevent unbilled balances before they form

Some unbilled revenue is contractual and unavoidable. Much of it is designed into weak commercial or operating processes.

Before signing an engagement:

• Align billing events with measurable, controllable deliverables.
• Avoid milestones that depend entirely on a customer's undefined acceptance process.
• Price and fund long gaps between delivery and billing.
• Require clear change-control rights and response deadlines.
• Confirm purchase-order, portal, documentation, and vendor requirements.
• Use deposits or more frequent billing where risk and market practice support them.

During delivery:

• Capture time, cost, progress, acceptance, and scope evidence as work occurs.
• Resolve rejected or missing support before month-end.
• Escalate unsigned change orders before continuing material out-of-scope work.
• Prepare draft billing packages before the eligibility date.
• Reforecast invoice and collection dates whenever the project schedule changes.

The goal is not zero unbilled revenue. The goal is a supported balance with a contractual reason, a named clearing event, and enough liquidity to carry it.

Know when the balance is warning you

Escalate when old unbilled revenue grows faster than sales, invoice dates repeatedly move, the same blocker recurs, project teams cannot produce support, customers dispute whether work was authorized, or reversals increase after close.

Those patterns may indicate weak scope control, optimistic progress estimates, poor contract setup, delayed administration, customer credit risk, or revenue that should not remain recorded. They may also show that reported profit is funding work the company cannot convert to cash on acceptable terms.

A fractional CFO should not make the technical accounting decision alone. The controller and qualified CPA should approve classification, measurement, credit-loss treatment, and any adjustment. The CFO should make sure the approved balance becomes an operating queue and a realistic cash forecast.

Sources

• Financial Accounting Standards Board: Revenue Recognition Project Summary
• Financial Accounting Standards Board: Revenue Recognition Implementation Questions and Answers
• Deloitte Accounting Research Tool: Contract Assets

Fractional CFO support can connect the contract-asset rollforward, billing workflow, project economics, and cash plan. The Profit & Tax Leak Check can identify whether unbilled work, slow billing, collections, margin, tax timing, or cash commitments are creating the first strain.