ASC 606 Revenue Presentation and Disclosure for Contract Balances

ASC 606 presentation and disclosure questions test whether the entity’s statement captions and notes explain the timing difference between performance, billing, and cash collection. The recognition answer may already be known, but FAR can still ask whether the resulting balance is a receivable, a contract asset, a contract liability, or a disclosure item.

The key distinction is conditionality. A receivable is an unconditional right to consideration. A contract asset exists when the entity has transferred goods or services but its right to payment is still conditional on something other than the passage of time. A contract liability exists when the entity has received consideration, or has an unconditional right to receive consideration, before transferring goods or services.

Contract Balance Framework

The exam often gives a billing schedule and a performance pattern. If revenue recognized exceeds the amount billed and the right to payment is still conditional, the excess is usually a contract asset. If billings or cash collections exceed revenue recognized, the excess is usually a contract liability.

Receivable Versus Contract Asset

The receivable-contract asset distinction is narrow but important. A receivable does not depend on future performance. The entity has completed the required performance for that payment, and only the passage of time or customer payment remains.

A contract asset still depends on another condition. For example, a contractor may recognize revenue as work is performed but cannot invoice until a milestone is reached. Until the milestone creates an unconditional right to consideration, the recognized but unbilled amount is a contract asset rather than accounts receivable.

    flowchart TB
	    A["Entity transfers goods or services"] --> B{"Is the right to consideration unconditional?"}
	    B -->|"Yes"| C["Present receivable"]
	    B -->|"No"| D["Present contract asset"]
	    E["Customer pays or amount becomes due before performance"] --> F["Present contract liability"]
	    D --> G{"Condition later satisfied?"}
	    G -->|"Yes"| C
	    F --> H["Recognize revenue as performance obligation is satisfied"]

Contract Liabilities

A contract liability is not a penalty or a refund estimate. It is the entity’s obligation to transfer goods or services because the customer has already paid or the amount is already due. Common examples include annual subscriptions billed in advance, prepaid service contracts, and upfront fees that do not provide a distinct good or service.

When the entity later satisfies the related performance obligation, the contract liability decreases and revenue is recognized. If the entity also expects refunds, returns, or credits, those amounts may require separate measurement and presentation. Do not automatically treat every customer-related liability as deferred revenue.

Presentation and Offsetting

Contract assets and contract liabilities are presented separately when material. They generally should not be offset across different contracts merely because management wants a net revenue position. Offsetting may be appropriate only when the balances arise from the same contract or combined contract and the entity has a valid basis to present the net position.

Contract Balance Disclosures

ASC 606 disclosures are designed to help users understand how contract balances changed during the period. A useful disclosure connects opening balances, new activity, revenue recognized, reclassifications, and closing balances.

FAR questions usually test the meaning of a rollforward line rather than requiring a full note disclosure. For example, “revenue recognized from beginning contract liabilities” means the entity satisfied performance obligations during the period that had been paid or billed before the period began.

Disaggregated Revenue

ASC 606 requires revenue information to be disaggregated into categories that show how economic factors affect the nature, amount, timing, and uncertainty of revenue and cash flows. The categories depend on the business, but common disaggregation bases include product line, service type, geography, market, contract duration, timing of transfer, and sales channel.

Disaggregation is not the same as segment reporting, although the categories may overlap. The revenue note should help users understand revenue recognition risk, not merely repeat the income statement total.

Remaining Performance Obligations

Remaining performance obligation disclosures explain the transaction price allocated to unsatisfied or partially unsatisfied performance obligations and when the entity expects to recognize that amount as revenue. This disclosure helps users understand future revenue from existing contracts, not from hoped-for future sales.

The exam trap is to confuse remaining performance obligations with backlog, forecasts, or sales pipeline. ASC 606 focuses on enforceable customer contracts and the portion of the transaction price allocated to obligations not yet satisfied, subject to practical expedients and materiality.

Significant Judgments

Revenue disclosures also explain major judgments and changes in judgments. These disclosures are important because ASC 606 often depends on estimates rather than simple invoice amounts.

For FAR, the stronger answer identifies the judgment that changes recognition or presentation. A vague statement that management “uses estimates” is usually not enough.

Exam Scenario

A software company signs a two-year service contract for $240,000. The customer pays $60,000 at signing and then $7,500 per month. The company provides the service evenly over 24 months. At the end of month one, the company has earned $10,000 of revenue but has collected $67,500 in cash.

The company does not recognize $67,500 of revenue. It recognizes $10,000 because one month of service has been provided. The excess cash collected over revenue recognized is a contract liability because the company still owes future service. The notes should explain the nature of the contract liability and, when material, show how beginning deferred revenue changed as revenue was recognized and new billings or collections occurred.

Now assume the same company performs customization work and recognizes $30,000 of revenue before it can invoice until a milestone is approved. If the milestone approval is more than a passage-of-time condition, the $30,000 is a contract asset. Once the milestone is approved and the right to consideration becomes unconditional, the balance moves to receivables.

Common Pitfalls

Key Takeaways

• A receivable is an unconditional right to consideration.
• A contract asset is a conditional right to consideration after performance.
• A contract liability arises when consideration is received or due before performance.
• ASC 606 disclosures explain contract balances, disaggregated revenue, remaining performance obligations, and significant judgments.
• Presentation questions often turn on the timing difference between performance, billing, and cash collection.

Knowledge Check