A SaaS business that bills customers annually collects cash well before it has earned revenue. This is not a quirk of the business model — it is its defining accounting feature. Cash and revenue recognition diverge structurally, the BAS treatment depends on whether the customer is in Australia or offshore, and the chart of accounts must be set up to handle deferred revenue as a genuine liability, not a holding pen that gets cleared to income at the end of the month for convenience.
AASB 15 and the Performance Obligation Framework
AASB 15 Revenue from Contracts with Customers applies to all Australian entities with contracts with customers, including SaaS businesses. The core principle is that revenue is recognised when (or as) a performance obligation is satisfied — that is, when control of the promised service transfers to the customer. For a subscription service where access to software is provided continuously over the subscription period, the performance obligation is satisfied over time, not at a point in time.
This means an annual subscription billed on 1 July for $12,000 generates $12,000 in cash on 1 July, but only $1,000 in revenue in July. The remaining $11,000 is a deferred revenue liability — an obligation to provide software access over the following 11 months.
The journal entry on billing and receipt of a $12,000 annual subscription:
- Debit Bank (or Accounts Receivable) $12,000
- Credit Deferred Revenue $12,000
At the end of each month, $1,000 is recognised as earned:
- Debit Deferred Revenue $1,000
- Credit Subscription Revenue $1,000
After 12 months, the Deferred Revenue balance returns to zero, and $12,000 has been recognised in revenue — $1,000 per month, aligned with the service delivery period.
The failure to apply this treatment — instead recognising the full $12,000 as revenue in July — overstates July revenue, understates the liability on the balance sheet, and means that if a customer cancels in September and demands a pro-rata refund, the refund is paid out of a revenue balance that no longer exists as a cash reserve.
Annual vs Monthly Billing and BAS Timing
The BAS implications of annual versus monthly billing depend on whether the entity uses accruals or cash basis GST reporting.
Under accruals basis GST, GST on a subscription invoice is reported in the period the invoice is issued — the full $1,200 GST on a $12,000 annual invoice is reported on the BAS for the quarter in which the invoice was raised, regardless of when revenue is recognised for accounting purposes. This creates a mismatch between accounting revenue recognition (spread over 12 months) and GST reporting (all in quarter one). The GST has been collected and remitted upfront; the revenue is recognised gradually. These two things can and do diverge, and the bookkeeper must resist any temptation to reconcile them by accelerating revenue recognition.
Under cash basis GST, the GST is reported when payment is received — same outcome for an invoice paid immediately on issue, but different for credit terms. If a customer takes 60 days to pay a quarterly invoice, the cash basis reporter remits the GST only when the cash arrives.
Monthly billing simplifies the alignment considerably: each month's invoice corresponds to that month's revenue and GST liability. For a startup that wants the simplest possible accounting, monthly billing at the same price per month (with no annual discount) produces the cleanest revenue recognition.
GST on Subscriptions: Domestic vs Offshore Customers
The GST treatment of a subscription depends on where the customer is located — and this is where many Australian SaaS businesses err.
Subscriptions supplied to Australian customers are taxable supplies. The supplier charges GST at 10%, remits it on the BAS, and the customer (if registered) claims the input tax credit. This is the standard domestic B2B or B2C transaction.
Subscriptions supplied to customers outside Australia are GST-free exports, provided the supply meets the conditions under Division 38-E of the GST Act. For digital services delivered to offshore customers, the supply is GST-free if the customer is outside Australia at the time of supply and the thing supplied is not connected with Australia. This means a SaaS business with 60% Australian customers and 40% overseas customers should be applying GST to the domestic revenue only.
For offshore B2C customers (individuals, not businesses) in countries that have their own digital services taxes (the EU, UK, Singapore, and others), the Australian SaaS provider may have obligations to register and remit GST/VAT in those jurisdictions — a matter for the accountant and the client's tax adviser, but the bookkeeper needs to ensure the chart of accounts codes domestic and offshore revenue separately so the split is auditable.
The reverse also applies: an Australian SaaS business importing digital services from offshore providers (AWS, Stripe, Salesforce, Google Workspace) may be subject to the "reverse charge" rules for imported services. Under Division 84 of the GST Act, an entity acquiring a taxable importation of services for a partly creditable purpose (i.e., where it is not fully entitled to input tax credits) is liable for GST on that importation. For fully creditable businesses — those making only taxable supplies — the reverse charge effectively does not result in net GST cost, as the GST payable is offset by a corresponding credit.
Churn, Refunds, and Cancellation Accounting
When a customer cancels mid-subscription and receives a pro-rata refund, the accounting unwinds in the direction of the original recognition.
If a customer paying $12,000 annually cancels after 3 months and receives a $9,000 refund:
At the time of refund:
- Debit Deferred Revenue $9,000 (the unearned portion)
- Credit Bank $9,000
There is no additional revenue reversal because only $3,000 was recognised as revenue in the three months prior to cancellation — the $9,000 deferred balance was never recognised as income. The refund settles the liability.
If the entity uses accruals basis GST and previously remitted $1,200 GST on the original invoice, the refund generates a decreasing adjustment on the BAS for the GST component of the refund ($900 GST on a $9,000 refund). This is reported at 1B in the BAS period in which the refund is paid.
Practical Xero and MYOB Setup
In Xero, deferred revenue is best managed through a liability account (Balance Sheet, Current Liabilities) named "Deferred Revenue" or "Unearned Subscription Income." Recurring monthly journal templates can automate the monthly revenue recognition entry — Xero's repeating journal feature lets you set a monthly debit to Deferred Revenue and credit to Subscription Revenue, which runs without manual intervention.
For invoicing, Xero's invoice date determines the BAS period in which the GST is reported (for accruals basis reporters). Annual subscription invoices should be dated on the billing date, and the revenue account on the invoice line should point to the Deferred Revenue liability account — not to a revenue account. This is a non-standard setup that confuses new users of Xero, but it is the correct treatment: the invoice credit is to Deferred Revenue, and the monthly journal transfers from Deferred Revenue to Subscription Revenue.
MYOB AccountRight handles this similarly through recurring journals and a dedicated liability account. The principle is the same: the invoice does not hit revenue; only the periodic journal recognises revenue. Any setup that bypasses this — coding the invoice directly to revenue to "keep things simple" — will result in overstated income in the billing month, an understated liability balance, and a reconciliation problem when the accountant reviews the year-end file.
Tracking customer-level deferred revenue balances (useful for SaaS businesses with large customer counts) is typically handled outside the accounting system, in a revenue recognition schedule or a dedicated billing platform, with the aggregated monthly recognition journal pushed into the accounting software as a single entry.