Unbilled Revenue Aging

A company has completed work and recognised revenue, but has not yet issued an invoice under the contract, and if the amount sits unbilled for months, managers need to know why. Unbilled revenue aging groups eligible balances by how long they have remained unbilled under a defined clock.

Oracle's project report describes aged unbilled receivables and Deltek documents aged unbilled revenue report columns, but their systems use particular dates and account definitions, so a general management report should state its own start date and accounting scope. Define the balance first, since revenue recognised but not invoiced can include contract assets or unbilled receivables depending on the rights and applicable accounting standard, and not every item is immediately billable.

Set the clock at revenue recognition, completion, milestone acceptance or another documented event, because those dates answer different questions. Choose buckets such as current, 30, 60 or 90-plus days, with boundaries that reflect the business's billing cycle and contract terms.

Separate not-yet-billable work, such as a contract requiring a future milestone or customer approval, which should be aged for visibility without calling it a billing error, from eligible-to-invoice work such as goods delivered, accepted milestones or completed service periods, which should move into the billing process when conditions are met. Check evidence, since delivery confirmation, timesheets and acceptance certificates can be required before the invoice may be submitted, and keep a list of missing items.

Review price and scope as well, because an unsigned change order can leave completed work difficult to bill, and the contractual issue should be escalated rather than merely pressing the billing clerk. Avoid double counting by moving an amount from unbilled to billed AR under the accounting policy once an invoice is issued, and track credits and reversals by reconciling the original balance, adjustments and invoice amount, since revenue estimates may change.

Measure value and count, because a small number of large aged balances can dominate cash risk while many tiny items point to process friction, and segment by project since a long construction contract and a recurring software service have different billing mechanics. Distinguish ageing from impairment: an old unbilled balance can signal collectability risk, but an age bucket alone does not decide an impairment amount.

Check customer restrictions, since a portal may reject an invoice lacking a purchase order or approved reference, and review cutoffs, as work recorded at month-end may not be invoiced until the next normal run, so a few days of lag can be expected under policy. Investigate very old items, because contract disputes, missing documentation, incomplete milestones and data migration errors can each create a stuck balance.

Assign owners: delivery teams provide completion evidence, contract managers resolve terms, billing issues invoices and finance reconciles the balance. Tie the report to the ledger, so the sum of aged items reconciles to the chosen unbilled account or documented management adjustment, and protect recognition integrity by not recognising revenue prematurely just to improve a receivables metric.

Pair the report with billed aging, since once an amount is invoiced it may still wait for payment and a full cash view follows unbilled, billed and collected stages, and use a forward plan recording expected billing date, blocker and next action for each old item, because repeating an age report without follow-up adds little value. For an owner, unbilled revenue aging shows where recognised work is waiting before it becomes an invoice, and the label is meaningful only when billing eligibility and accounting classification are both clear.