Subscription businesses often collect cash before they have fully delivered the service. That can make a SaaS business look more profitable than it really is, particularly when annual plans, implementation fees and usage charges are involved.
Getting revenue recognition right helps founders and finance teams produce reliable reports, manage GST and tax obligations, forecast cash flow, and make informed decisions as the business grows. It also reduces the risk of reporting revenue too early, overlooking liabilities to customers, or relying on figures that do not reflect the underlying performance of the business.
Revenue recognition starts with what you have promised the customer
For entities preparing financial reports under Australian Accounting Standards, AASB 15 provides the framework for recognising revenue from contracts with customers. The central principle is straightforward: revenue is recognised when, or as, the promised goods or services are transferred to the customer.
For SaaS businesses, the invoice date and payment date are not always the right revenue-recognition dates.
A customer may pay upfront for access over a future period. In that case, the cash has been received, but the service has not yet been fully provided. The portion relating to future access may need to sit on the balance sheet as a contract liability, often described in practical terms as deferred or unearned revenue, until the relevant service period passes.
The first step is to understand the actual customer promise. A SaaS arrangement can include more than the right to log into a platform. Depending on the contract and how the service is sold, it may also include:
– ongoing access to software or a hosted platform
– onboarding or implementation services
– data migration
– configuration or custom development
– training
– support services
– premium service levels
– additional user licences
– usage-based charges
– future upgrades or optional add-ons.
The accounting treatment should follow the substance of those promises, not simply the labels used on an invoice.
For example, a “set-up fee” is not automatically revenue when charged. If the set-up activity does not provide a distinct service to the customer, it may be part of the wider SaaS arrangement and recognised over the period in which the customer receives the related service. On the other hand, a separately useful implementation or consulting service may have a different recognition pattern.
Clear contracts, product descriptions and billing records make this analysis much easier. If the sales team offers concessions, bespoke onboarding or bundled features, finance needs visibility before the deal is signed, not months later at EOFY.
Recognise subscription revenue as the service is delivered
Most recurring SaaS subscriptions involve a continuing obligation to provide access to a platform over an agreed period. Where that is the promise made to the customer, revenue will commonly be recognised over that service period rather than in full when an annual invoice is issued or paid.
A straight-line pattern can be appropriate where access and service are provided evenly over time. However, it should not be adopted automatically. The recognition pattern should reflect how the customer receives the benefit of the service.
A simple monthly subscription may be relatively straightforward. More complex arrangements require closer attention. Common pressure points include:
– annual or multi-year subscriptions paid in advance
– free trials that convert automatically
– discounted first periods
– contracts that include both subscription access and professional services
– implementation work completed before the platform goes live
– contracts with variable usage charges
– refunds, credits and service-level commitments
– reseller, marketplace or channel-partner arrangements
– contract renewals, upgrades and downgrades.
A practical revenue schedule should show, for each customer contract:
– the contract start and end dates
– the services promised
– billing dates and amounts
– cash received
– revenue recognised to date
– deferred revenue remaining
– any unbilled revenue or contract asset balance
– credits, refunds and disputed amounts
– renewal and cancellation status.
This schedule should reconcile to the accounting system, subscription billing platform and bank receipts. If each system tells a different story, management reporting can quickly become unreliable.
It is also important to separate a receivable from a contract asset. A receivable generally arises when the business has an unconditional right to payment. A contract asset can arise where the business has recognised revenue for work performed but its right to bill is still conditional on something other than the passage of time. The distinction matters for financial reporting, credit control and audit readiness.
Treat variable fees, discounts and refunds with care
SaaS pricing is often designed to be flexible. That flexibility can support growth, but it can also make revenue recognition more difficult.
Usage-based charges, transaction fees, seat-based pricing, rebates, credits and performance incentives may change the amount the business expects to receive from a contract. Finance teams need a documented method for determining when those amounts are sufficiently supportable to include in revenue.
A sensible approach is to avoid recognising uncertain revenue simply because a customer might exceed a usage threshold or because a sales target appears likely to be met. Revenue reporting should remain supportable if it is reviewed later against the contract terms, product data and customer correspondence.
Discounts should also be reflected consistently. If a customer receives a reduced subscription price, free months, credits or bundled services, the transaction price may need to be allocated across the actual services promised. Recording the full list price as revenue and booking the concession elsewhere can distort key metrics.
Refund policies deserve the same attention. A generous cancellation policy, a service-level guarantee or a history of commercial credits may affect the amount of revenue that is ultimately expected to be retained. The business should have a process for identifying and reviewing these exposures rather than waiting for a large customer complaint or renewal dispute.
This is particularly important for businesses presenting monthly recurring revenue, annual recurring revenue, churn, customer lifetime value or revenue retention metrics. These can be useful management measures, but they are not substitutes for properly recognised accounting revenue. The definitions should be documented, applied consistently and reconciled to the underlying records.
Keep accounting revenue, GST and income tax clearly separated
One of the most common SaaS finance mistakes is assuming that accounting revenue, GST reporting and income tax timing must all follow the same result. They do not necessarily do so.
For financial reporting purposes, revenue recognition is driven by the contract and the transfer of promised goods or services. For income tax purposes, assessable income includes ordinary income derived during the income year. The appropriate method for determining when income is derived depends on the circumstances and should provide a substantially correct reflection of income.
For some businesses, the receipts method may be appropriate. For others, particularly where the business has ongoing contractual obligations, material receivables or more complex operations, an earnings-based approach may better reflect income. This should be considered carefully and applied consistently rather than changed merely to improve a short-term tax outcome.
GST has its own attribution rules. Whether a business accounts for GST on a cash basis or a non-cash basis can affect when GST is reported through the BAS. For businesses not accounting on a cash basis, GST may be attributed when payment is received or an invoice is issued, depending on which happens first. For supplies made progressively or periodically, there are specific rules that can apply to the periodic components.
That distinction creates a familiar cash flow issue. A SaaS provider may issue an annual invoice, become liable to report GST in an earlier BAS period, and then recognise accounting revenue gradually over the subscription term. The cash may be in the bank, but not all of it represents current-period revenue or freely available operating cash.
For Australian SaaS businesses selling internationally, GST analysis can become more complex. The GST treatment may depend on matters such as the customer’s location, whether the customer is a business or consumer, the nature of the service, and whether the supply is connected with Australia. Do not apply a single “overseas customers are GST-free” rule without reviewing the arrangement properly.
Improve cash flow without overstating performance
Good revenue recognition does not prevent a SaaS business from collecting cash upfront. In fact, annual prepayment options can improve working capital and reduce collection risk. The key is to distinguish between cash received and revenue earned.
A business that collects annual subscriptions in advance may have strong operating cash flow while still carrying a meaningful deferred revenue balance. That is not a problem. It is useful information because it shows the business has a continuing obligation to provide service in future periods.
To use this information well, consider building a regular cash and revenue review around:
– cash collected from new sales, renewals and expansions
– deferred revenue movement
– subscription revenue recognised during the period
– overdue receivables and failed payments
– customer refunds, credits and chargebacks
– expected GST and income tax obligations
– payroll, hosting, support and sales costs
– renewal concentration and churn risk.
A separate tax and GST reserve account can also be helpful. It reduces the temptation to treat all subscription receipts as available for product development, recruitment or founder drawings.
A practical scenario
A growing software business sells annual platform access and charges a separate onboarding fee. Its billing system records the full invoice as revenue immediately when payment is received.
The cash position looks healthy, but the monthly profit reports are overstated in the early months of the contract. The business also has difficulty explaining why reported revenue falls in quieter sales months even though customers continue using the platform.
After reviewing the contracts, the business sets up a revenue schedule. Subscription income is recognised across the access period, while onboarding is assessed based on whether it is a distinct service or part of the overall customer promise. The revised reports show steadier earned revenue, a clear deferred revenue balance and a more realistic view of future service obligations.
The result is not necessarily less successful. It is simply a more accurate picture of performance and cash flow.
Build systems that can scale with the subscription base
Manual spreadsheets can work in the earliest stages, but they become risky when a SaaS business has multiple plans, annual prepayments, upgrades, usage charges, credits and overseas customers.
The goal is not to create unnecessary complexity. It is to build a process that remains reliable as transaction volume increases.
Start by ensuring the core systems agree:
– the signed contract or accepted online terms
– the CRM record
– the subscription billing platform
– the accounting file
– payment processor reports
– bank transactions
– the revenue-recognition schedule
– BAS and tax workpapers.
Changes to customer terms should also flow through this process. A mid-contract upgrade, extension, downgrade or cancellation may affect billing, cash collection and revenue recognition. If the commercial team can amend arrangements without finance visibility, errors are likely.
It is also worth establishing clear ownership. Sales should own accurate deal information. Customer success should communicate changes, credits and cancellations. Finance should review the accounting, GST and reporting consequences. Management should review exceptions, unusual contract terms and key reconciliation items.
At a minimum, complete a monthly close that includes:
1. reconciling subscription billings to the general ledger
2. matching payment processor settlements to bank receipts
3. reviewing deferred revenue and unbilled amounts
4. checking credits, refunds and failed payments
5. assessing material contract changes
6. reconciling GST reporting data to BAS workpapers
7. reviewing revenue trends against operational metrics.
This discipline supports better decisions well before a lender, investor, purchaser or auditor asks questions.
Scale with confidence by making the numbers decision-ready
SaaS revenue recognition is not just a compliance exercise. It affects pricing decisions, growth forecasts, cash planning, performance reporting and the confidence stakeholders can place in the numbers.
A well-designed process helps business owners understand the difference between bookings, billings, cash received and revenue earned. It also helps prevent a strong sales month from being mistaken for sustainable profitability, or a quieter sales month from being mistaken for poor underlying performance.
The right approach depends on the business model, contract terms, GST accounting method, legal structure and reporting obligations. General information only: this article is not personal financial or tax advice. Speak with a registered tax agent or accountant, such as, about your specific circumstances.
If your SaaS business is growing, changing pricing models or preparing for investment, a review of your revenue recognition and reporting processes can provide a clearer foundation for the next stage of growth.