What is deferred revenue, which side of the balance sheet does it sit on, and why?

What the interviewer is actually testing

Revenue recognition questions test whether you understand accrual accounting as a system rather than a rule to memorize. Interviewers are listening for:

1. You can state the principle, not just the mechanics. The strong opener is: "Revenue is recognized when the company satisfies its performance obligation -- when it transfers control of the good or service -- regardless of when cash is collected." Reciting ASC 606's five steps without this framing sounds like memorized jargon.

2. You instinctively know which side of the balance sheet a timing mismatch lands on. Cash received before revenue earned goes to deferred revenue, a liability. Revenue earned before cash received goes to accounts receivable, an asset. Candidates who hesitate or get the direction backwards signal they don't actually understand what these accounts represent.

3. You can connect deferred revenue to cash flow and business quality. A strong candidate volunteers that rising deferred revenue is a source of operating cash flow and often a leading indicator of the sales pipeline -- this is exactly the kind of connective-tissue insight that separates a top bucket from a pass. Being able to say you'd check bookings vs. billings vs. revenue growth rates to see if deferred revenue trends are healthy or masking a slowdown signals real fluency, not textbook recall.

4. You can walk a subscription example cold. The annual-subscription-collected-upfront example is close to universal in technicals interviews for SaaS-adjacent coverage groups. Be able to state the day-one balance sheet entry and the monthly income statement recognition without hesitating.

Keep the core answer under 45 seconds: define the principle, give the one-line deferred-revenue/AR distinction, and stop -- let the interviewer pull the thread into cash flow or a numerical example if they want depth.

Common traps

Trap 1: Confusing deferred revenue with accounts receivable. Candidates frequently get the direction backwards, calling deferred revenue an asset, or saying AR is money the company owes. AR is money owed to the company (asset); deferred revenue is an obligation owed by the company (liability).

Say it out loud: Accounts receivable is an asset -- revenue we've recognized but haven't collected in cash. Deferred revenue is a liability -- cash we've collected but haven't yet earned by delivering the good or service.

Trap 2: Saying revenue is recognized when cash is received. This describes cash-basis accounting, which almost no company of interest to a bank actually uses. Under GAAP/IFRS, recognition is tied to delivery of the performance obligation.

Say it out loud: Under accrual accounting, revenue is recognized when the performance obligation is satisfied -- when control of the good or service transfers to the customer -- not when cash is received.

Trap 3: Treating deferred revenue as bad news. Some candidates, pattern-matching liability to bad, describe growing deferred revenue negatively. In reality, growing deferred revenue for a subscription business usually signals strong forward bookings and is a healthy source of operating cash flow.

Say it out loud: Rising deferred revenue isn't a red flag -- for a subscription business it typically means bookings are outpacing recognized revenue, which is a good sign and a source of operating cash flow.

Trap 4: Forgetting that recognizing deferred revenue involves no new cash. When deferred revenue converts to recognized revenue each month, candidates sometimes describe a fresh cash inflow. There isn't one -- the cash arrived upfront; the monthly event is purely an income-statement/balance-sheet reclassification.

Say it out loud: Recognizing deferred revenue each period is a non-cash event -- the cash already came in at contract signing; we're just moving the liability into revenue as we deliver.

Trap 5: Assuming all long-term contracts wait until completion to recognize anything. Candidates over-generalize recognize revenue on delivery to mean a multi-year construction contract shows zero revenue until the final year.

Say it out loud: For long-duration contracts, revenue is often recognized over time using percentage-of-completion -- in proportion to costs incurred or milestones met -- so the income statement reflects the economic work done each period, not just the final delivery.