Under AASB 15, recognise SaaS subscription revenue as access is provided, not when you invoice or get paid. Income tax timing is a separate question under ITAA 1997 section 6-5, and GST attribution can fall due earlier again. Three frameworks, three answers. This guide gives you the journals, a contract checklist, and a clean Xero setup.
Recurring revenue underpins SaaS valuation, forecasting, and investor confidence. It also creates accounting complexity, because customers often pay upfront for services delivered over many months.
Under AASB 15 Revenue from Contracts with Customers, revenue is recognised when, or as, performance obligations are satisfied. For SaaS businesses, this usually means recognising subscription revenue progressively over the access period, rather than when cash is received or an invoice is issued.
The timing of assessable income is a separate question. It is considered under ITAA 1997 section 6-5 and ATO guidance on receipts versus earnings methods. GST attribution may differ again, depending on whether the business accounts for GST on a cash or non-cash basis. Blending these three frameworks is the most common error we see, and it is the one this article fixes.
In our work with SaaS and IT businesses, the gap usually comes from cash-basis thinking carried into an accrual environment. This article builds on our Ultimate Guide to Accounting for SaaS & IT Businesses in Australia and focuses on getting recurring revenue right across accounting, income tax, and GST.
How is SaaS subscription revenue recognised under AASB 15?
Under AASB 15, revenue is recognised when, or as, a performance obligation is satisfied by transferring control of the service to the customer. For most SaaS subscriptions, control transfers continuously as the customer accesses the software, so revenue is recognised evenly over the subscription period, not when payment is received.
AASB 15 paragraph 31 states that an entity recognises revenue when (or as) it satisfies a performance obligation by transferring a promised service to the customer, and a service is transferred when the customer obtains control. Paragraph 35 sets out when a performance obligation is satisfied over time, which is the typical pattern for software a customer uses continuously over a contract term.
Take a customer who prepays $12,000 (excluding GST) for a 12-month subscription, with access provided evenly across the year. On receipt, no revenue is recognised. The cash is recorded as a contract liability (deferred revenue). Each month, as access is provided, $1,000 is recognised as revenue.
| Timing | Event | Accounting treatment |
|---|---|---|
| On receipt | $12,000 received | Recognise a contract liability. No revenue yet. |
| Each month | Access provided | Recognise $1,000 revenue; reduce the contract liability. |
| End of month 12 | Contract complete | Contract liability is nil; $12,000 recognised in total. |
Illustrative, based on the worked example in this article (even monthly delivery).
What are the journal entries for prepaid SaaS subscriptions?
When an annual subscription is paid upfront, debit bank or debtors and credit a contract liability (deferred revenue) for the revenue base. Each month, debit the contract liability and credit subscription revenue for the portion earned. The liability falls to nil once all access has been provided.
Here are the entries for the $12,000 subscription, shown on an ex-GST basis so the revenue mechanics are clear.
| Transaction | Debit | Credit |
|---|---|---|
| Annual invoice paid upfront (ex GST) | Bank / Debtors $12,000 | Contract liability $12,000 |
| Monthly recognition | Contract liability $1,000 | Subscription revenue $1,000 |
In practice the invoice will usually carry GST. The same subscription invoiced at $13,200 GST-inclusive breaks down into a $12,000 revenue base and $1,200 GST. The $12,000 is deferred and released monthly for accounting purposes, while the $1,200 GST is handled separately under your GST accounting basis (covered below). Accurate bookkeeping here keeps the deferred revenue balance reliable month to month.
How are setup and onboarding fees treated?
Setup, onboarding, and implementation fees are not automatically recognised upfront. Under AASB 15, you must assess whether the activity transfers a distinct service to the customer. If the setup merely enables future subscription access, the fee is treated as an advance payment and recognised over the subscription period.
AASB 15 paragraphs B48 to B51 deal with non-refundable upfront fees, including activation and setup fees. The standard requires you to assess whether the fee relates to the transfer of a promised good or service. In many SaaS arrangements, the setup activity does not transfer a distinct service. Instead it is an advance payment for the subscription that follows, so it is recognised as the future service is provided. You can review the detail in Appendix B of AASB 15.
The practical test is whether the customer could buy the setup service on its own and benefit from it without the subscription. Genuine, distinct implementation work (for example, bespoke integration the customer controls) may be a separate performance obligation. Routine onboarding that simply switches the customer on is usually not. Getting this wrong distorts both early-period revenue and the way your contract value is reported.
Is SaaS income taxed when invoiced or when earned?
Income tax timing is assessed separately from accounting. Ordinary income is assessable when derived under ITAA 1997 section 6-5. For prepaid subscriptions, amounts received in advance are generally not derived until the service is provided, so assessable income often follows delivery rather than the invoice or cash receipt.
Section 6-5 of the ITAA 1997 brings ordinary income into assessable income when it is derived. The ATO sets out the two methods for working out derivation in Taxation Ruling TR 98/1: the receipts method (income derived when received) and the earnings method (income derived when earned, when a recoverable debt arises). For most trading companies, the earnings method gives a substantially correct reflex of business income.
Prepaid subscriptions carry an additional principle. In Arthur Murray (NSW) Pty Ltd v FCT [1965] HCA 58; (1965) 114 CLR 314, the High Court held that fees received in advance for services to be provided in future years were not derived at the moment of receipt. They became assessable as the services were rendered. For a SaaS business, this often aligns the timing of assessable income with the AASB 15 revenue pattern, but the two must still be tested separately, not assumed to match. We work through this as part of tax planning for each client.
Have questions about your SaaS revenue recognition?
We help SaaS and IT founders align accounting, income tax, and GST timing so the numbers hold up under investor and ATO scrutiny.
Contact Us Today →When is GST payable on annual SaaS subscriptions?
GST timing depends on your accounting basis. On a non-cash (accruals) basis, GST is attributed in the BAS period in which you issue a tax invoice or receive payment, whichever is earlier. So the full GST on an upfront annual subscription can be payable before any of the revenue is recognised under AASB 15.
GST attribution is governed by Division 29 of the A New Tax System (Goods and Services Tax) Act 1999. Under section 29-5, a business on a non-cash basis attributes GST to the earlier of the period in which it issues an invoice or receives any payment. A business on a cash basis attributes GST when payment is received. The ATO explains the two bases in its guidance on identifying your accounting basis.
On the $13,200 GST-inclusive example, a business on a non-cash basis that issues the invoice in January generally reports the full $1,200 GST in the January to March BAS, even though only three months of the $12,000 revenue base will be recognised by 31 March. The GST and the accounting revenue are simply on different clocks. Our BAS and IAS lodgement service is built around exactly this kind of timing.
The same separation applies to digital sales through third-party marketplaces. For how the platforms handle GST on app store and in-app sales, see our guide to GST on app store sales.
Common SaaS revenue recognition errors and their impact
Most problems trace back to cash-basis habits, bundled obligations, or a missing deferral process. Each one distorts the numbers that founders and investors rely on.
| Issue | What happens | Risk |
|---|---|---|
| Cash-basis treatment | Revenue recorded on payment | Overstated early-period profit and deferred revenue understated |
| Bundled obligations | Setup fees recognised upfront | AASB 15 non-compliance under B48 to B51 |
| No accrual process | Delivered services not recognised | Misleading profit and loss |
| No deferral journals | Prepaid income recognised too early | Distorted tax position and BAS errors |
What about ARR and MRR?
Be careful not to confuse accounting revenue with operating metrics. Annual Recurring Revenue (ARR) and Monthly Recurring Revenue (MRR) are management measures, not AASB 15 measures. They should be calculated from active recurring contract value, not from revenue recognised in the ledger.
Incorrect revenue recognition still does damage. It can distort reported revenue, EBITDA, deferred revenue, and management dashboards. ARR and MRR also become unreliable when they are derived from accounting revenue rather than contract-level subscription data. The fix is to keep the two systems clean and reconciled, which is a core part of business advisory and forecasting.
In our experience working with a Melbourne-based SaaS client, annual subscriptions were being recorded on a cash basis, which materially overstated early-period profit and made recurring-revenue metrics unreliable. We introduced contract-level revenue schedules, automated monthly deferral journals in Xero, and a month-end close review. Within a quarter, reported revenue reflected actual service delivery, deferred revenue was tracked accurately, and investor reporting discrepancies were resolved. Sound revenue policy also supports cleaner tax compliance at year end.
Your SaaS revenue recognition checklist
Start every contract review by capturing the terms that drive recognition. Run through this list when a new or renewed contract comes in:
- Contract start and end dates, and the service access period
- Billing frequency (monthly, annual, multi-year)
- Onboarding obligations and implementation milestones
- Support inclusions, training, and customisation
- Cancellation and refund terms
- Usage-based fees, discounts, and credits
- Renewal and upgrade terms, including any material rights
Setting it up in Xero
A clean ledger structure makes recognition repeatable and audit-ready:
- A deferred revenue (contract liability) account on the balance sheet
- Separate revenue accounts for subscription, implementation, support, and usage fees
- Monthly repeating journals or a revenue schedule to release deferred revenue
- A supporting workpaper that reconciles deferred revenue each month, retained for the audit trail
Source: ABS, Counts of Australian Businesses, including Entries and Exits (FY2022-23 to FY2024-25).
The sector continues to expand, with the number of Information Media and Telecommunications businesses rising 1.5% in 2024-25 according to the ABS Counts of Australian Businesses. More businesses each year means more founders meeting accrual-based recognition rules for the first time. If that is you, our startup accounting and advisory team can set this up from the outset.
The bottom line
Revenue recognition is not a bookkeeping footnote. It is the foundation that makes your reported numbers, tax position, and recurring-revenue metrics defensible. Recognise subscription revenue as access is provided under AASB 15, test income tax timing separately under ITAA 1997 section 6-5, and attribute GST under your accounting basis. Three frameworks, applied deliberately, turn financial data into a decision-making asset rather than a compliance risk.
For the full picture across accounting, tax, and growth, read our Ultimate Guide to Accounting for SaaS & IT Businesses in Australia.
Book a SaaS revenue recognition review
If your revenue looks healthy on paper but not in performance, we will help you realign accounting, tax, and GST timing with confidence.
Schedule a meeting →Disclaimer: The information provided in this article is general in nature and does not constitute specific tax, legal, or financial advice. Revenue recognition, income tax, and GST outcomes depend on your full facts. We recommend seeking professional advice tailored to your individual circumstances. 42 Advisory is a CPA firm and Registered Tax Agent.
Frequently Asked Questions
Does AASB 15 require SaaS revenue to be recognised monthly?
AASB 15 requires revenue to be recognised as the performance obligation is satisfied. For a subscription where access is provided evenly, that usually means recognising revenue evenly over the term, which is commonly done monthly. The pattern should reflect how control of the service actually transfers.
Is deferred revenue a liability or income?
Deferred revenue is a liability. It represents cash received for services not yet delivered, recorded as a contract liability under AASB 15. It is released to income progressively as the service is provided and the obligation is satisfied.
Is prepaid subscription income taxable when received?
Not necessarily. Income is assessable when derived under ITAA 1997 section 6-5. Following Arthur Murray (NSW) Pty Ltd v FCT, amounts received in advance for future services are generally not derived until the service is provided. The correct method depends on your facts, so seek advice.
When is GST payable on an upfront annual subscription?
It depends on your GST accounting basis. On a non-cash basis, GST is attributed when you issue the invoice or receive payment, whichever is earlier, so it can be payable before the revenue is recognised. On a cash basis, GST is attributed when payment is received.
Should SaaS setup fees be recognised upfront?
Usually not. Under AASB 15 paragraphs B48 to B51, you must assess whether the setup fee transfers a distinct service. If it only enables future subscription access, it is an advance payment recognised over the subscription period rather than upfront.
See how 42 Advisory’s fixed-fee accounting model helps SaaS and IT founders scale with confidence.
Sergiy Kucherenko
Sergiy Kucherenko is the founder and director of 42 Advisory and a member of CPA Australia. His professional career has been built in public practice and business advisory — working alongside business owners to simplify financial complexity, strengthen structure, and support growth at every stage. Originally trained as an engineer with a background in computer science, Sergiy brings an analytical and systems-oriented mindset to accounting and advisory — one that translates directly into the practice's emphasis on automation, process design, and technology-driven client solutions. It is the foundation behind 42 Advisory's cloud-first operating model and its ability to serve technically complex businesses with precision. Throughout his advisory career, Sergiy has served clients across medical technology, telecommunications, SaaS and technology businesses, construction and trades, and healthcare — including general practice and dental groups. That depth of sector exposure informs advice that is commercially grounded, not generic — calibrated to the specific operating realities of each industry. He has supported businesses at every stage of the growth cycle — from incorporation and early-stage structuring through to acquisition, restructure, and exit — with particular depth in service trust structures for medical practices, SaaS revenue recognition, and construction industry cash-flow management.