What is unbilled AR, and how does it differ from a contract asset?

Same symptom, different diagnosis

Both an unbilled receivable and a contract asset describe the same surface situation: revenue has been recognized, but no invoice has gone out yet. The distinction that matters is what's actually standing between the entity and getting paid. If the payment terms were already fixed by the contract's billing schedule and the only thing left is for the billing date to arrive, that's an unbilled receivable — a receivable in substance, just not invoiced yet. If payment depends on something else — completing a second milestone, passing an acceptance test — that's a contract asset.

Where teams actually get this wrong

The mistake usually runs one direction: calling something an unbilled receivable because it's habitually tracked in the same sub-ledger as AR, without checking whether the underlying right to payment is actually unconditional. A services engagement billed monthly in arrears, where the only open question is "has the invoice run yet," is a genuine unbilled receivable. The same engagement with a holdback released only after a satisfaction sign-off is a contract asset for that holdback amount, even if it sits in the same tracking spreadsheet as everything else labeled "unbilled."

Why it's worth getting right, not just a classification exercise

Because a contract asset carries genuine performance risk that a receivable doesn't — the entity hasn't yet cleared every hurdle to get paid — the two have to be presented as separate balance sheet lines, not combined into one "unbilled" bucket. A finance team that lumps them together loses the ability to see whether growth in unbilled amounts reflects healthy timing lag (receivables) or growing conditional exposure (contract assets), which is exactly the distinction an auditor or a careful investor will ask about.