Software as a Service Accounting for Clients 2026
Review a SaaS client’s subscriptions, deferred revenue and development costs. Reconcile contracts, billing and cash to the records your practice needs.
- Published
- Updated
Software as a service accounting matches a supplier’s revenue to the services delivered. Reconcile subscription contracts with billing and cash, then assess development costs separately.
Map the Client’s Subscription Contracts
Start with what the software business promises each customer. A billing description such as annual subscription cannot tell you whether the contract includes hosted access, a software licence or separate implementation work.
Confirm the client’s financial reporting framework and the standards applicable to its reporting period. For accounts applying Australian Accounting Standards, AASB 15 governs revenue from customer contracts within its scope.
Build a contract register with the following fields:
- Customer and contract reference, including amendments.
- Enforceable term and cancellation rights.
- Service commencement, end and renewal terms.
- Hosted access, licence rights and any support promises.
- Setup work and evidence of what the customer receives.
- Fixed fees, usage charges, discounts and credits.
- Invoice schedule, payment terms and delivery evidence.
Identify distinct performance obligations, determine the transaction price and allocate it using relative stand-alone selling prices. Recognise revenue when or as each obligation is satisfied. Hosted access commonly involves an over-time service. A separate licence needs its own analysis.
An upfront setup fee is not automatically immediate revenue. Assess whether setup transfers a distinct service. Internal activation work can instead relate to future services. Usage charges and contract changes also need analysis under AASB 15.
Keep the two sides of the transaction separate. Your software supplier client earns revenue from customers. A business buying hosted access has a separate software accounting treatment question about its expenditure.
Reconcile Billing, Cash and Revenue
Reconcile each contract’s invoices and receipts to the revenue schedule. Match cash to the invoice it settles, then match revenue to the service delivered. Keep payment-processor fees separate from gross customer collections.
Fictional Monthly and Annual Subscriptions
Assume two invented contracts provide hosted access evenly over their service periods. There are no separate performance obligations, discounts or financing effects. All amounts exclude GST, which is recorded separately.
The monthly customer pays $100 in advance for one complete month. The annual customer pays $1,200 in advance for twelve complete months. Both pay at the start of their first service month.
| Contract | Initial receipt | Revenue after first complete month | Closing contract liability |
|---|---|---|---|
| Monthly access | $100 | $100 | $0 |
| Annual access | $1,200 | $100 | $1,100 |
For the annual contract, record a $1,200 debit to cash and credit to the contract liability when paid. After the first complete month, debit the liability and credit revenue by $100.
After three complete months, annual-contract revenue totals $300 and the remaining liability is $900. Recording all $1,200 as revenue on receipt would overstate revenue by $900 at that point.
Advance payments create a contract liability for future services. An unconditional right to payment is a receivable. A contract asset is a right still conditional on something beyond time passing. Unbilled does not itself decide the classification.
Changes That Explain a Reconciliation Difference
Assume the annual customer cancels after three complete months. The contract permits cancellation and requires the unused $900 to be refunded. Remove that $900 liability through the refund accounting, preserving the $300 earned for completed service.
For a plan upgrade, retain the approved amendment and its effective service point. Rebuild the affected schedule using the contract-modification analysis. Explain the adjustment separately so a reviewer can distinguish new billing from a change in recognition.
Trace a service credit to its reason and covered period. A credit for a future period affects a different part of the schedule from a correction of previously recognised revenue.
For usage billed after the reporting cut-off, retain the usage report and entitlement calculation. Assess recognition and whether the balance is a receivable or contract asset before posting it.
Use separate reconciliations for each balance. For receivables, bridge opening debtors through invoices, credits and collections to closing debtors. For deferred revenue, show additions for future service and reductions for earned revenue or refunds. Explain every manual adjustment.
Monthly recurring revenue and annual recurring revenue are operating metrics. Keep their definitions with management reporting and bridge them to financial-statement revenue. Their totals do not replace the contract-level accounting schedule. Tax treatment also needs a separate assessment.
Review Development Costs and the File
Separate research expenditure from development expenditure before capitalising the client’s software costs. AASB 138 requires research costs to be expensed. If the phases cannot be distinguished, treat the expenditure as research.
Development recognition requires evidence of every criterion:
- Technical feasibility of completion.
- Intention to complete and use or sell the asset.
- Ability to use or sell it.
- Probable future economic benefits.
- Adequate resources to finish and use or sell it.
- Reliable measurement of attributable expenditure.
Capitalisation starts when the recognition criteria are first met. Previously expensed costs cannot be reinstated. Record the available-for-use point, useful life and amortisation policy, and assess impairment requirements.
Keep a project cost schedule that identifies the work performed. Separate eligible development from research, maintenance, training and selling activity. Tie employee time to payroll and contractor work to invoices. A developer’s job title alone does not explain the work.
Records for the Accounts Reviewer
Retain the contract register, billing exports and receipt matches with the deferred-revenue reconciliation. Add the evidence for unbilled balances, credits, refunds and changed plans. Tie each closing balance to the trial balance.
For development, retain project approvals and evidence for each recognition criterion, alongside the cost schedule. Record who approves the capitalisation start, useful life and impairment assessment. Explain judgement changes from the previous accounts.
Give the reviewer a short list of exceptions with an owner and the proposed adjustment. Finish the file when the closing balances reconcile and the reviewer can trace each judgement to the underlying contract or project evidence.
One client form. One finished return.
Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.
Made for Australian accounting firms