Unbilled revenue: what it is, journal entries, and close controls

Unbilled revenue is revenue a company has earned but has not invoiced yet. The work has been delivered, the service period has passed, or the usage has been consumed, but the billing workflow has not caught up.

That timing gap matters during close. If finance waits for the invoice before recording earned revenue, revenue can be understated. If finance records the revenue but never follows the balance through to an invoice, cash gets delayed and revenue leakage hides in the unbilled account.

For SaaS and contract-based teams, unbilled revenue usually shows up when contracts, usage data, billing rules, invoice approvals, and the general ledger are not moving on the same schedule.

What is unbilled revenue?

Unbilled revenue is earned revenue that has not been billed to the customer. It is usually recorded under accrual accounting, where revenue is recognized when the company satisfies the relevant performance obligation, not only when an invoice is sent or cash is collected.

The phrase is often an operational label. In billing systems, reports, or close schedules, finance teams may call the balance unbilled revenue, unbilled receivables, or unbilled accounts receivable. In formal revenue-recognition presentation, the same operational balance may need a more precise label. Deloitte's ASC 606 guidance explains that an entity presents a contract asset when goods or services have been transferred before payment is due, excluding amounts that qualify as receivables; Deloitte also notes that this amount is commonly called an unbilled receivable.

That means these terms are related, but not always interchangeable:

• Unbilled revenue is the business-facing label for revenue earned before the billing workflow is complete.
• Contract asset is a financial-statement presentation label when the right to consideration is still conditional on something other than time.
• Receivable or accounts receivable applies when the right to consideration is unconditional, even if payment is not due yet.
• Accrued revenue is the broader earned-but-not-yet-collected concept. Unbilled revenue can be a type of accrued revenue, but accrued revenue is not always the exact operating account name.

The basic flow looks like this:

1. The company delivers the product, service, milestone, or usage.
2. Revenue is earned under the contract.
3. No invoice has been issued yet, so the amount sits in an unbilled revenue, unbilled receivable, or contract asset account based on the company's policy and contract terms.
4. When the right to consideration becomes unconditional, often at the invoice step under the contract, the balance moves to accounts receivable.
5. The customer pays, and accounts receivable clears to cash.

The core idea is simple: the accounting event and the billing event can happen on different dates. The accounting label should still follow the contract and the company's revenue policy.

A simple unbilled revenue example

Say a SaaS company has a customer contract with a fixed monthly subscription plus usage-based overages. In July, the customer receives the subscription service and uses $2,000 of overages. The usage data is rated after month-end, and the invoice is not sent until August 5.

If the usage was earned in July, the finance team may need to recognize the July revenue during the July close even though the invoice has not gone out yet. The $2,000 overage can sit in an unbilled revenue or contract asset account until the company has an unconditional right to bill and collect it under the contract.

The risk is not the existence of the balance. Some unbilled revenue is normal when contracts bill in arrears or usage data arrives after the cutoff. The risk is losing track of the balance after close and never converting it into a clean invoice.

Is unbilled revenue an asset or liability?

Unbilled revenue is generally an asset because the company has delivered goods or services and expects consideration from the customer. The exact presentation depends on whether the company has an unconditional right to that consideration.

It is not deferred revenue. Deferred revenue is a liability because the customer has paid, or has been billed, before the company has delivered the product or service. Unbilled revenue is the opposite timing pattern: the company has delivered first and bills later. Deloitte's ASC 606 guidance and Selden Fox's contract asset and liability examples treat contract assets, receivables, and contract liabilities as distinct concepts, so finance should not collapse them into one casual bucket.

There is one important presentation nuance. Deloitte's ASC 606 roadmap says some unbilled balances may be presented as contract assets when the right to payment is conditional on something other than the passage of time. For example, a company may have delivered one part of a contract, but the customer does not owe payment until another milestone is complete. When the right to payment is unconditional, the balance is a receivable even if payment is due later.

That is why the operational label in a billing system and the financial statement label are not always identical. Finance should follow the company's accounting policy, contract terms, and auditor guidance.

Unbilled revenue journal entries

The exact account names vary by company. Many teams use an account called unbilled revenue, unbilled receivables, accrued revenue, or contract asset. The account name should match the company's accounting policy and the contract facts.

A useful guardrail is the distinction between a contract asset and a receivable. Deloitte's ASC 606 roadmap says a contract asset exists when revenue has been recognized but payment is contingent on a future event and distinguishes contract assets from receivables. In plain English: do not move a balance to accounts receivable just because someone wants the invoice sent. Move it when the company has an unconditional right to consideration under the contract, which often happens when an invoice is issued but is not determined by invoice timing alone.

The simple accounting flow is usually:

For example, if a customer uses $2,000 of billable product usage in July and the invoice is sent in August, the July close entry may debit unbilled revenue or a contract asset for $2,000 and credit revenue for $2,000. When the right to bill and collect becomes unconditional under the contract, finance reclassifies that balance to accounts receivable.

The entry should be supported by evidence. For a SaaS team, that support might include the signed contract, usage report, pricing rule, delivery record, billing schedule, approval status, and the later invoice.

Unbilled revenue vs deferred revenue, AR, accrued revenue, and contract assets

These terms often get mixed together because they all sit near revenue recognition, billing, and close. The fastest way to separate them is to ask what happened first: delivery, invoice, cash, or an unconditional right to payment.

Selden Fox's ASC 606 examples describe contract assets as rights to consideration for transferred goods or services when the right is conditioned on something other than the passage of time, and contract liabilities as obligations to transfer goods or services for consideration already received. That is the key separation: asset balances start from delivered work and expected consideration; liability balances start from consideration received or due before performance is complete.

Unbilled revenue and deferred revenue can both exist in the same company, and sometimes even around the same customer relationship, if different products, periods, or performance obligations are at different points in the contract. They should not be netted together casually. They answer different accounting questions.

Why unbilled revenue appears in SaaS and contract-based businesses

Unbilled revenue is common anywhere the contract says one thing, the customer uses or receives another thing, and billing happens later. The balance is especially common in SaaS finance workflows because delivery, usage, pricing, approvals, and billing often live in different systems.

Common causes include:

• Arrears billing. The customer uses the service first and receives the invoice after the period ends.
• Usage data arrives after the billing cutoff. Product usage, API calls, seats, credits, or overages are earned in one period but rated and billed in the next.
• Milestone work is complete before invoicing is allowed. Implementation, onboarding, or professional services work may be delivered before customer approval or a billing milestone is reached.
• Custom contract terms change invoice timing. Annual commitments, ramps, minimums, true-ups, co-terming, and customer-specific payment terms can separate revenue recognition from invoicing.
• Sales amendments do not update billing rules fast enough. Renewals, expansions, and mid-contract changes can create earned revenue that the billing system does not know how to invoice yet.
• Customer portals or PO rules delay invoice submission. The invoice may be ready internally but blocked by a missing purchase order, Coupa or Ariba workflow, or customer approval step.
• Manual review queues miss the close deadline. Finance may know work was delivered, but the invoice is waiting on RevOps, legal, sales, customer success, or billing operations.

None of these automatically mean something is wrong. They do mean finance needs a clean way to see what has been earned, what has been billed, what is blocked, and who owns the next step.

What finance teams should watch during close

Unbilled revenue becomes risky when it is unsupported, old, or disconnected from the billing workflow. A useful close process does not just book the balance. It explains where the balance came from and how it will turn into an invoice.

Watch these areas during close:

• Recognized revenue vs invoices issued. Compare revenue recognized to invoices issued by customer, contract, product, and period.
• Unbilled aging. Review balances that are older than one billing cycle. A legitimate timing item should not become a forgotten invoice.
• Usage cutoffs. Reconcile usage data, pricing rules, rated charges, invoices, and revenue entries before close.
• Milestone status. Check whether implementation or services milestones have been completed but are waiting on approval or billing authorization.
• Non-standard terms. Review contracts with ramps, minimum commitments, usage true-ups, invoice holdbacks, customer PO rules, or special billing dates.
• Deferred and unbilled balances on the same relationship. Make sure the team can explain why both exist and which performance obligations each one relates to.
• Manual journal entries. Attach contract, usage, delivery, invoice, or approval evidence to entries that move revenue into or out of unbilled accounts.
• Blocked invoices. Assign owners for invoices stuck in review, waiting for purchase orders, or blocked in customer portals.

This is also where revenue recognition automation becomes valuable. The hardest part is not writing the journal entry. It is collecting the source evidence from CRM, contracts, usage systems, billing tools, approvals, and the ERP before the close deadline.

How to reduce unbilled revenue without under-recognizing earned revenue

The goal is not to force unbilled revenue to zero. Some earned-but-not-invoiced revenue is expected when the business bills in arrears or has legitimate contract timing gaps. The goal is to keep the balance accurate, supported, and moving toward invoice and cash when it should.

A better workflow usually has five parts:

1. Capture billing rules from the signed contract. Finance needs the actual billing schedule, usage terms, milestones, minimums, ramps, and approval requirements, not a simplified CRM note.
2. Pull delivery and usage data before close. For usage-based revenue recognition, usage cutoffs and rating logic are often the difference between a clean close and a surprise unbilled balance.
3. Match earned revenue to invoice readiness. Every earned amount should have a status: invoiced, ready to invoice, waiting for data, waiting for approval, blocked by customer requirement, or intentionally held.
4. Route exceptions before they age. If a contract term, PO, portal submission, or customer approval blocks invoicing, assign it before the close package is finalized.
5. Keep the audit trail together. The entry should tie back to the contract, performance evidence, usage or milestone support, invoice, and any approval history.

LedgerUp is built around that contract-to-cash handoff. Ari reads contract terms, checks billing and usage data, flags earned work that has not been invoiced, routes exceptions to the right person, and keeps support tied to the revenue workflow. That helps finance teams reduce preventable unbilled revenue without pretending every timing difference is an error.

FAQ

What is another name for unbilled revenue?

Unbilled revenue may be called unbilled receivables, unbilled accounts receivable, or an unbilled balance in operating reports. In formal accounting presentation, related balances may be contract assets or receivables depending on whether the right to consideration is conditional. Accrued revenue is a broader term for earned revenue that has not yet been collected in cash, so it is related but not always a perfect synonym.

Is unbilled revenue the same as accounts receivable?

No. Unbilled revenue is earned but not billed. Accounts receivable means the company has an unconditional right to consideration, even if payment is due later. In the normal workflow, an unbilled balance moves into accounts receivable when the contract and billing facts make that right unconditional, which often happens when the invoice is issued.

What is the difference between accrued revenue and unbilled revenue?

Accrued revenue is the broader category for revenue that has been earned but not yet collected in cash. Unbilled revenue is a more specific operating label for earned revenue that has not yet been billed. Depending on the contract, that balance may need to be presented as a contract asset or a receivable.

Can unbilled revenue and deferred revenue exist for the same customer?

Yes, but they should relate to different periods, products, or performance obligations. One part of a customer relationship may be prepaid and deferred, while another part may be delivered but not yet invoiced. Finance should track the supporting contract terms so the balances are not accidentally netted or mislabeled.

Keep the balance explainable

Unbilled revenue is a signal that delivery, billing, and close are not on the same timeline. That is normal in SaaS and contract-based businesses. It becomes a problem when finance cannot explain the balance, support the entry, or move it into billing when the invoice should go out.

The cleanest teams treat unbilled revenue as part of the contract-to-cash workflow. They know what was earned, why it was not billed yet, who owns the next step, and which evidence supports the close.