Under ASC 606, the relationship between performance and payment determines how revenue-related amounts appear on the balance sheet. A contract asset arises when an entity has satisfied a performance obligation but the right to payment is conditional on something other than the passage of time (ASC 606-10-45-3). A receivable arises when the right to payment is unconditional — only the passage of time is required before payment is due (ASC 606-10-45-4). Deferred revenue (contract liability) arises when the customer has paid or payment is due before the entity has satisfied its performance obligation (ASC 606-10-45-2). The classification determines impairment treatment, disclosure requirements, and the signals a balance sheet sends about revenue quality.
Key references: ASC 606-10-45-1 through 45-5 · Contract asset impairment: ASC 310-10 · Receivable impairment: ASC 326 (CECL)
The question is always the same: what is the nature of the entity’s right to receive consideration, and what is the customer’s obligation to pay it?
The Three Balance Sheet Positions
Every revenue arrangement at any point in time sits in one of three positions relative to the relationship between performance and payment:
- Contract asset: you have performed a task but have a conditional right to payment
- Receivable: you have performed a task and have an unconditional right to payment
- Deferred revenue (contract liability). the customer has paid (or payment is due) and you have not yet performed a task
The practical distinction between a contract asset and a receivable turns on conditionality. A receivable exists when the only thing standing between the entity and collection is the passage of time; the customer owes the money, and the invoice is either outstanding or the due date has arrived. A contract asset exists when the right to payment depends on the entity satisfying additional performance obligations first. The entity has done some work and earned some revenue, but it can’t yet demand payment because there’s more to deliver.
A classic example: a two-phase professional services contract where the customer pays a single amount upon completion of phase two. After phase one is done, the entity has recognized revenue for phase one (it satisfied that PO), but it cannot invoice or demand payment until phase two is also complete. That earned-but-not-yet-billable amount is a contract asset, not a receivable.
The billing schedule doesn’t determine the classification
Whether an amount is a contract asset or a receivable depends on the nature of the right to payment, not on when the invoice was sent. An invoice can be issued before performance is complete (creating deferred revenue) or after (creating a receivable). The accounting classification follows the economics of the arrangement, not the billing mechanics.
Multi-Element Arrangements: Where the Classification Gets Nuanced
In contracts with multiple performance obligations, the classification of revenue-related amounts can shift as the entity satisfies each obligation. A single contract can generate a contract asset, a receivable, and deferred revenue simultaneously, each representing a different piece of the transaction price relative to performance.
Consider a SaaS contract that bundles a software license (point-in-time recognition at delivery) with a 12-month support subscription (recognized ratably). The transaction price is allocated between the two at standalone selling prices. At contract inception:
- Receivable: the license fee is recognized when the software is delivered and the right to payment is unconditional
- Deferred revenue: the support subscription fee is collected upfront but earned over 12 months
Now add a third element: the contract also includes implementation services, with a single payment milestone triggered only after all three deliverables are complete. When the license is delivered and the implementation services are partially completed but the milestone hasn’t been reached:
- Receivable: the portion of transaction price allocated to the license: recognized, unconditional right
- Contract asset: the portion allocated to completed implementation work: recognized, but conditional on finishing the remaining work before payment is due
- Deferred revenue: the portion allocated to future support and unfinished implementation: not yet earned
Contract netting under ASC 606-10-45-5
Contract assets and contract liabilities arising from the same contract are presented net on the balance sheet. A contract with both a contract asset (earned but conditional) and deferred revenue (unearned) shows only the net position. Contracts are not offset against each other, netting applies within a single contract only.
Impairment: Why the Classification Matters Beyond Presentation
The most significant practical consequence of the contract asset vs. receivable distinction is impairment treatment. Receivables are subject to the CECL model under ASC 326 — an expected credit loss estimate based on historical loss rates, current conditions, and reasonable forecasts. Contract assets follow ASC 310-10 impairment guidance. Unlike receivables, they require assessing both performance completion risk and customer credit risk — the asset can be impaired not only by the customer’s failure to pay but by the entity’s failure to satisfy the remaining performance conditions.
If a customer cancels a contract before the entity has satisfied the remaining performance obligations, the contract asset may need to be written down even if the customer is creditworthy. The right to payment was never unconditional, so it never became a receivable — and the inability to complete performance eliminates the basis for the asset entirely.
In practice, this means contract assets require two separate assessments at each reporting period: whether the entity expects to complete the remaining performance conditions, and whether the customer is expected to pay once those conditions are met. Treating contract assets as if they were receivables and applying only credit loss estimation misses the first question.
Disclosure Requirements
ASC 606-10-50-10 requires disclosure of the opening and closing balances of contract assets and contract liabilities, along with the significant changes in those balances during the period — revenue recognized that was included in the opening contract liability balance, revenue from obligations satisfied in prior periods, cash received in advance of performance, and changes from business combinations or write-offs.
Companies that lump contract assets and trade receivables together on the face of the balance sheet or in a single footnote line without distinguishing the nature of each are underreporting the information the standard requires. The distinction matters to investors: a large contract asset balance signals revenue that has been earned but whose collection depends on future performance, while a large receivable balance signals earned revenue awaiting only payment. The credit quality and timing implications are different.
Frequently Asked Questions
What is a contract asset under ASC 606?
A contract asset is an entity’s right to consideration in exchange for goods or services that the entity has transferred to a customer, where that right is conditioned on something other than the passage of time, typically satisfying additional performance obligations. It represents earned but not-yet-unconditionally-receivable revenue (ASC 606-10-45-3).
What is the difference between a contract asset and a receivable?
A receivable exists when the right to payment is unconditional, only the passage of time is required before payment is due. A contract asset exists when the right to payment depends on the entity satisfying additional performance obligations. A contract asset becomes a receivable when all remaining conditions are satisfied and only payment timing remains.
Can a single contract have both a contract asset and deferred revenue?
Yes. When a contract includes multiple performance obligations with different patterns of recognition and payment timing, some obligations may be satisfied ahead of billing (creating a contract asset) while others have been billed or paid before performance (creating deferred revenue). The two are presented net for the same contract under ASC 606-10-45-5.
How is a contract asset different from deferred revenue?
A contract asset reflects earned revenue where payment is conditionally owed to the entity. Deferred revenue (a contract liability) reflects amounts the customer has paid or where payment is due, but where the entity has not yet satisfied its performance obligation. One is an asset the entity holds; the other is an obligation the entity owes.
What impairment model applies to contract assets?
Contract assets are subject to impairment guidance under ASC 310-10. Unlike receivables (which are assessed only for credit loss under ASC 326), contract assets must also be assessed for the entity’s ability to satisfy the remaining performance conditions. A customer cancellation before completion can impair a contract asset even if the customer is otherwise creditworthy.
The bottom line
The distinction between contract assets, receivables, and deferred revenue isn’t a presentation technicality. It reflects the state of the relationship between performance and payment at a given point in time. Getting it right requires tracking each performance obligation’s satisfaction status, billing schedule, and payment conditionality in parallel. When those data points live in separate systems, billing in one place, revenue recognition in another, so the balance sheet classifications tend to drift.
For the full revenue recognition framework, see the Enterprise Revenue Recognition Guide. To learn how billing data flows into revenue recognition, check out Billing to Revenue Recognition: The Data Flow Problem.
