Cloud-Based Software Accounting Treatment 2026
Review cloud software costs for your client’s accounts. Distinguish subscriptions, implementation and assets, with evidence for the accounting entry.
- Published
- Updated
Cloud-based software accounting treatment depends on the customer’s contractual rights: recognise hosted access as a service, and assess controlled software separately for asset recognition.
Establish What the Software Contract Provides
Read the signed contract before assigning the software invoice to an expense or asset account. Identify what your client receives and who controls the software. The words “licence”, “implementation” or “cloud” on an invoice cannot settle that assessment.
The IFRS Interpretations Committee’s hosted-software decision distinguishes a right to future access from control of software. A contract giving only access to the supplier’s hosted application is a service contract.
A licence can convey software rights that need a separate asset assessment. Examine whether the client can obtain benefits from the software and restrict others’ access to those benefits. Identify any lease question separately where the agreement conveys control of use.
Collect these contract facts before choosing an entry:
- The contracting entity and the reporting framework used for its financial accounts.
- The access period, renewal terms and cancellation rights.
- Rights to the software or separately developed code, including use after the hosted agreement ends.
- Each supplier’s promised deliverables and the acceptance evidence for them.
- Amounts allocated to access, implementation work and any separate asset, with the basis for each allocation.
A separately invoiced implementation service needs its own assessment. It could configure the supplier’s application, supply training or create code controlled by the client. Keep these outputs separate even when one project manager oversees the whole job.
Classify Subscription and Implementation Costs
Classify each deliverable before deciding when to recognise its cost. Upfront payment establishes when cash moves. It does not establish when a service is received or prove that software qualifies as an intangible asset.
Hosted Access and Implementation Services
Configuration changes settings in existing software. Customisation changes or adds code. The Committee’s configuration and customisation decision requires an assessment of whether the resulting resource is controlled by the customer.
When no intangible asset arises, determine when the services are received. For work supplied by the hosted-software supplier, assess whether it is distinct from access. Apply the relevant AASB 15 principles to that judgement.
| Contract outcome | Recognition timing | Accounting logic |
|---|---|---|
| Hosted access only | Over the access period | Expense as access is supplied |
| Advance payment for future services | Until those services are received | Record a prepayment, then release it to expense |
| Distinct configuration or customisation from the software supplier | As the work is performed | Recognise the service expense |
| Supplier implementation inseparable from hosted access | Over the access term | Expense with the access service |
| Configuration supplied directly by a separate third party, with no asset created | As that supplier performs the work | Recognise the service expense |
A supplier subcontracting its work does not automatically turn the customer’s agreement into a direct third-party contract. Identify who owes the deliverable to your client and document why the services are distinct or inseparable.
The Queensland Audit Office’s explanation shows why cloud projects can contain expenses and prepayments alongside qualifying assets. Assess the outputs individually before moving the project total into one account.
Controlled Software Assets
Under AASB 138 Intangible Assets, recognition requires an identifiable controlled resource, probable future economic benefits and reliably measurable cost. Initially measure a qualifying asset at cost, including directly attributable preparation costs. Exclude staff training.
For internally generated software, expense research. Capitalise development only when all criteria are demonstrated: technical feasibility, intention and ability to complete and use it, probable benefits, adequate resources and reliable cost measurement. Start accumulating qualifying costs when those criteria are met.
For a finite-life software asset, amortisation begins when it is available for use. Estimate useful life from the asset’s expected use and contractual limits. Under the cost model, deduct accumulated amortisation and impairment from cost.
Fictional Customer Entries
These examples use invented amounts excluding recoverable GST. Each assumes payment in cash and the stated contract assessment. The figures illustrate journal logic, not software prices or a tax deduction.
| Scenario | Entry when paid or delivered | Later entry |
|---|---|---|
| Customer prepays $12,000 for 12 months of evenly supplied hosted access | Debit prepayments $12,000 and credit cash $12,000 | Each month, debit subscription expense $1,000 and credit prepayments $1,000 |
| Customer pays an independent consultant $6,000 after completing configuration that creates no controlled asset | Debit implementation expense $6,000 and credit cash $6,000 | No remaining implementation asset |
| Hosted supplier receives $9,000 for work assessed as inseparable from 36 months of evenly supplied access | Debit prepayments $9,000 and credit cash $9,000 | Over the access term, debit expense $250 monthly and credit prepayments $250 |
| Customer purchases separate controlled software for $24,000, meeting asset recognition criteria | Debit software intangible asset $24,000 and credit cash $24,000 | With an evidenced four-year useful life, zero residual value and straight-line consumption, annual amortisation is $6,000 |
In the final scenario, the annual entry debits amortisation expense and credits accumulated amortisation. Start that charge when the software is available for use. A part-year charge reflects the period available, with impairment assessed separately.
Incorrect treatment: capitalise the whole cloud project because it will help the client for several years.
Correct treatment: identify each contractual output and apply its recognition and timing requirements. Expected future benefit alone does not establish a software asset.
Retain the Judgement and Reconciliation
Retain a short accounting paper that links each conclusion to a contract clause and a ledger entry. Another practitioner must be able to see why a cost is expensed, prepaid or capitalised without repeating your interviews.
Keep the following evidence with the paper:
- Executed contracts and statements of work, including amendments.
- Invoices reconciled to deliverables and the allocation assumptions used for bundled charges.
- Evidence of service delivery, acceptance and when a controlled asset became available for use.
- The control assessment and the reasons supplier implementation is distinct or inseparable.
- Useful-life assumptions, amortisation workings and any impairment assessment for recognised software assets.
- The reviewer’s conclusion, approved journals and the financial-statement disclosure assessment.
Maintain separate roll-forwards for prepayments and intangible assets. Reconcile opening balances, additions and charges to the closing ledger. Investigate a cancelled service or abandoned project before carrying its remaining balance into the next period.
Separate Tax From Financial Accounting
A financial-accounting expense does not automatically establish an immediate tax deduction. The ATO’s digital product guidance distinguishes expenses from capital software expenditure and requires evidence of the claim. In-house software and development-pool rules can produce different timing.
Prepare a tax reconciliation beside the accounting schedule. Identify the amount charged in the accounts and the deduction allowed under the applicable tax rules. Show the adjustment between them and carry forward any remaining tax balance.
For example, assume a separate tax assessment establishes a $4,000 deduction against $6,000 accounting amortisation for the period. Add back $6,000 and deduct $4,000 in the tax reconciliation. The net adjustment increases taxable profit by $2,000.
Those tax figures are assumptions, not a depreciation rate or entitlement. Assess any deferred tax consequence under the client’s reporting framework. Finalise the entry only when the contractual conclusion, supporting schedule and tax reconciliation agree with the reviewed file.
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