The disclosure requirements under ASC 606 and IFRS 15 are among the most comprehensive in GAAP/IFRS. The objective is to help users understand the nature, amount, timing, and uncertainty of revenue and cash flows from contracts with customers. For SaaS companies — where upfront payments, multi-period contracts, and complex bundling are common — the presentation and disclosure decisions have real consequences for how the business is read by investors and auditors.
Balance Sheet: Three Concepts, Frequently Confused
Three distinct items arise from revenue contracts, and they are not interchangeable:
Contract Assets
A contract asset arises when you have already satisfied a performance obligation but your right to receive payment is conditional on something other than just the passage of time — typically, satisfying another performance obligation first. Example: you deliver and install software in month 1 (PO satisfied), but the contract says you invoice only after training is complete in month 3. You have a contract asset in months 1–2: you've earned the revenue but can't yet invoice.
Contract assets are not receivables — the customer hasn't accepted a payment obligation yet. They sit in a separate line item on the balance sheet.
Receivables (Trade Receivables)
A receivable arises when your right to receive payment is unconditional — the only thing left is the passage of time. You've invoiced, the customer owes you money, and nothing else needs to happen for you to collect. This is a regular accounts receivable, subject to standard impairment (allowance for doubtful accounts).
Contract Liabilities (Deferred Revenue)
A contract liability arises when the customer has paid (or you have the unconditional right to invoice) before you have satisfied the related performance obligation. In SaaS, this is the most common balance sheet item: annual subscriptions paid upfront create a contract liability (deferred revenue) that you amortize over the service period.
Key distinction: Not all deferred revenue is a contract liability. If you collect advance payments that include a refund right, the refund obligation may be a refund liability under ASC 606-10-55-23 or IFRS 15.55 — presented separately from contract liabilities.
Working Example: Annual SaaS Subscription
A customer pays $12,000 on January 1 for a 12-month subscription. Service begins immediately.
At January 1 (payment received, service beginning):
- Dr. Cash $12,000
- Cr. Contract Liability (Deferred Revenue) $12,000
At January 31 (one month of service delivered):
- Dr. Contract Liability $1,000
- Cr. Revenue $1,000
At the end of January, the balance sheet shows $11,000 of contract liabilities. By December 31, the contract liability is fully amortized. No contract assets — the right to payment was unconditional at signing.
Footnote disclosure required: The company must disclose that it had $12,000 of contract liabilities at the start of the period, $11,000 of which were recognized as revenue during the current period (or appropriate disclosure of the opening balance roll-forward).
Required Note Disclosures
Both standards require extensive footnote disclosure organized around five areas:
1. Disaggregation of revenue. Revenue must be broken down into categories that show how economic factors affect the nature, amount, timing, and uncertainty of revenue. Common disaggregation dimensions for SaaS: by product line, by geography, by contract duration (monthly vs. annual vs. multi-year), by delivery model (self-serve vs. enterprise), or by customer segment. You choose the categories — but they must be genuinely informative, not just top-line totals.
2. Contract balances. A roll-forward of contract assets and liabilities is required: opening balance, revenue recognized, amounts billed, and closing balance. For contract liabilities, you must also disclose how much of the opening balance was recognized as revenue during the current period — this is the "pull-through" number that investors use to sanity-check ARR.
3. Performance obligations. Qualitative description of when performance obligations are satisfied (over time or at a point in time), the significant payment terms, and whether there are warranties, return rights, or other obligations. For companies with long-term contracts, also disclose the aggregate amount of the transaction price allocated to unsatisfied performance obligations (the "backlog disclosure") — when you expect to recognize it. The practical expedient: you can skip the backlog disclosure for performance obligations with an original expected duration of one year or less.
4. Significant judgments. The methods and assumptions used in determining: (a) timing of satisfaction of performance obligations, (b) transaction price and constraint, (c) allocation to performance obligations. For SaaS, this typically covers how you identify distinct performance obligations in bundled arrangements, how you estimate and constrain variable consideration, and how you determine SSPs.
5. Assets recognized for costs to obtain or fulfill contracts. Opening and closing balances of capitalized contract costs (e.g., deferred commission assets), amortization for the period, and the judgments used to determine amortization periods.