FA-301i · Module 2

Ratable Recognition

3 min read

SaaS subscription revenue is recognized ratably — evenly over the contract term — because the performance obligation is satisfied over time. A $120K annual subscription is recognized at $10K per month, regardless of when cash is collected. An annual prepayment in January creates $120K in cash and $110K in deferred revenue on January 31. By December 31, the deferred revenue is zero and all $120K has been recognized. This is the most common SaaS revenue pattern and the simplest to implement correctly.

Annual Subscription — Recognition Schedule:
──────────────────────────────────────────────────────
Contract: $120,000 annual subscription
Start: March 1, 2026 | End: February 28, 2027
Payment: Annual prepay on March 1
──────────────────────────────────────────────────────
         Cash    Revenue   Deferred   Recognized
Month    Recd    Recd      Revenue    to Date
──────────────────────────────────────────────────────
Mar     $120K    $10K      $110K       $10K
Apr       $0K    $10K      $100K       $20K
May       $0K    $10K       $90K       $30K
Jun       $0K    $10K       $80K       $40K
...      ...     ...        ...         ...
Feb       $0K    $10K        $0K      $120K
──────────────────────────────────────────────────────

Cash arrived in March.
Revenue arrives over 12 months.
The gap is deferred revenue — a liability
until the service is delivered.

Do This

  • Recognize subscription revenue ratably from the service start date, not the contract signature date
  • Prorate partial months — a contract starting March 15 recognizes 16/31 of the monthly amount in March
  • Maintain a deferred revenue schedule that reconciles to the balance sheet monthly

Avoid This

  • Recognize annual subscription revenue upon cash receipt — that is cash-basis, not ASC 606
  • Start recognition upon contract signature if service delivery has not begun
  • Round partial months to full months — the precision matters for audit and reporting accuracy