Why SaaS Businesses Struggle with Revenue Recognition
Recurring revenue underpins SaaS valuation, forecasting, and investor confidence. It is also one of the most common compliance failure points for Australian technology businesses.
Under AASB15 Revenue from Contracts with Customers and ATO TR 2019/1, subscription income must be recognised as performance obligations are satisfied, not when invoices are issued or cash is received. Despite this, revenue recognition remains widely misunderstood in practice.
Salesforce’s State of Finance Report 2024 found that 63% of SaaS businesses globally report misalignment between revenue recognition policies and actual service delivery. In our Australian client work, this gap most often arises from cash-basis thinking carried into accrual environments, leading to overstated profits, unreliable KPIs, and avoidable ATO risk.
This article builds on our in-depth resource, The Ultimate Guide to Accounting for SaaS & IT Businesses in Australia, and zooms in on how to recognise recurring revenue accurately — and compliantly — under ATO and AASB 15 rules.
1. Core Rule Under AASB 15: Revenue Follows Delivery, Not Cash
The principle is clear and non-negotiable.
Revenue is recognised when control of the promised service transfers to the customer, not when payment is received.
Example:
If a customer prepays $12,000 for a 12-month subscription, revenue must be recognised progressively:
| Date | Event | Accounting Treatment |
|---|---|---|
| Jan | $12 000 received | Cash increases – no revenue recognised |
| Jan–Dec | Monthly service delivered | $1 000/month recognised |
However, Xero Small Business Insights 2025 indicates that approximately 25% of Australian tech businesses still recognise annual SaaS subscriptions upfront, materially overstating profitability in early periods.
This creates downstream issues, including:
-
Artificially inflated ARR and EBITDA
-
Distorted tax positions
-
Audit exposure where financial statements do not reflect economic reality
2. Identifying Performance Obligations in SaaS Contracts
AASB 15 requires contracts to be assessed for distinct performance obligations.
In a typical SaaS arrangement, these often include:
-
Initial onboarding or implementation
Recognised when onboarding services are completed. -
Subscription access
Recognised progressively over the access period. -
Support, training, or customisation
Recognised as services are delivered.
Where these obligations are incorrectly bundled, Monthly Recurring Revenue (MRR) and churn metrics become unreliable. This is a common red flag in investor due diligence and financial reviews.
3. Common SaaS Revenue Recognition Errors (and Their Impact)
| Issue | What Happens | Risk |
|---|---|---|
| Cash-basis treatment | Revenue recorded on payment | Overstated profits and ARR |
| Bundled obligations | Setup fees recognised upfront | AASB 15 non-compliance |
| No accrual process | Delivered services not recognised | Misleading P&L |
| No deferral journals | Prepaid income overstated | ATO exposure |
42 Advisory Case Study — Chadstone SaaS Client:
This client recorded all prepaid annual subscriptions on a cash basis. Their ARR appeared 35 % higher than reality, skewing investment decisions.
We implemented:
-
Contract-level revenue schedules
-
Automated deferral journals in Xero
-
Month-end close controls integrated with Xero and Zapier
Within one quarter:
-
Revenue reporting accuracy exceeded 95%
-
Forecasting cycle time improved by 35%
-
Investor reporting discrepancies were eliminated
4. Timing Differences, Accruals, and Deferred Revenue
Deferred Revenue
Cash received for services not yet delivered. Recognised as a liability until performance occurs.
Accrued Revenue
Services delivered but not yet invoiced. Recognised as revenue with a corresponding receivable.
Multi-period subscriptions require systematic, periodic recognition. SaaS businesses with automated revenue recognition processes consistently outperform manual operators, largely because management decisions are based on real economic performance rather than cash timing noise.
5. Staying ATO-Compliant: Practical Checklist
-
Map every contract obligation under AASB 15
-
Automate deferral entries via Xero + Automations
-
Run monthly close reviews to capture accrual and deferral adjustments
-
Document your policy with ATO and AASB references
-
Engage periodic advisory reviews to validate the application and maintain audit-readiness
6. Why Revenue Recognition Matters Strategically
Accurate revenue recognition underpins:
| Metric | Impact |
|---|---|
| MRR / ARR | True growth and churn visibility |
| CAC to LTV | Reliable unit economics |
| Cashflow forecasts | Predictable tax and reinvestment planning |
| Investor reporting | Credible, defensible numbers |
When revenue recognition aligns with AASB 15 and ATO guidance, financial data becomes a decision-making asset rather than a compliance risk.
Final Word
Revenue recognition isn’t a bookkeeping footnote — it’s a strategic foundation.
By aligning timing, contracts, and accruals correctly, SaaS leaders gain clearer visibility, stronger compliance, and investor-ready confidence.
At 42 Advisory, we help SaaS founders translate accounting complexity into data-driven clarity — through automation, fixed-fee transparency, and advisory insight.
If your revenue looks healthy on paper but not in performance, it’s time to realign.
Explore our broader insights in The Ultimate Guide to Accounting for SaaS & IT Businesses in Australia to strengthen your entire compliance and growth framework.