IT and software firms have bookkeeping challenges that span revenue recognition, intellectual property capitalisation, government incentive programmes, and international billing — often simultaneously. A SaaS company that bills annually, conducts genuine R&D, employs offshore contractors, and has customers in the US, UK, and Australia has at least six distinct accounting questions to answer correctly in every financial year. This guide addresses the most material ones.
SaaS Revenue Recognition Under AASB 15
A subscription-based SaaS company's revenue model creates a structural mismatch between billing and revenue recognition that the bookkeeper must actively manage.
For a monthly subscription, revenue is recognised each month as the service is delivered — the performance obligation is the provision of the platform for the subscription period. This is straightforward: bill on the 1st, recognise revenue for the month.
For an annual subscription billed upfront, the full year's fee is collected at the start of the subscription term. Only 1/12 is earned in the first month. The remaining 11/12 is a contract liability (deferred revenue) that is recognised ratably over the subscription term. At any given balance date, the deferred revenue balance represents the value of subscriptions received that have not yet been earned.
Implementation fees require separate analysis. If the implementation service provides the customer with a standalone benefit (they could use the result independently of the ongoing SaaS subscription — for example, if the data migration and configuration creates an independently deployable result), the implementation is a distinct performance obligation under AASB 15.27 and is recognised when that service is substantially complete. If the implementation is not separately useful without the continuing subscription, the implementation fee is allocated across the subscription term and recognised ratably with the subscription revenue.
Onboarding fees that simply reflect the seller's internal cost of setting up a new account — rather than providing any meaningful deliverable to the customer — are generally not distinct performance obligations and should be allocated to the subscription term.
Software Development Costs: Expense vs. Capitalise
The ATO's default position is to allow an immediate deduction for software development costs incurred by a business developing internal-use software, provided those costs are not of a capital nature. For most ongoing software development (agile product iterations, bug fixes, feature additions to a live product), the costs are revenue in nature and deductible as incurred under s.8-1 ITAA 1997.
However, a company that creates software for commercial sale as a product may, and in some cases must, treat development-phase costs as an intangible asset under AASB 138 Intangible Assets. AASB 138.57 requires capitalisation of development costs when the entity can demonstrate:
- Technical feasibility of completing the intangible asset
- Intention to complete the asset and use or sell it
- Ability to use or sell the asset
- That the asset will generate probable future economic benefits
- Adequate resources to complete the development
- Ability to measure the expenditure reliably
Costs in the research phase (exploratory work, proof-of-concept testing, evaluating alternatives) are always expensed — they cannot be capitalised even if they are precursors to a specific product. Only once the project crosses from research to development (when the conditions above are demonstrably met) can costs be capitalised.
Capitalised development costs are amortised over their useful life (typically 3–7 years for software products) using the straight-line method. If the product is abandoned or becomes obsolete, the carrying value is impaired to nil under AASB 136.
R&D Tax Incentive: Cost Centre Tracking Throughout the Year
IT companies are among the largest beneficiaries of the Industry Research and Development Act 1986 (IR&D Act) R&D Tax Incentive. For companies with aggregated annual turnover below $20 million, the incentive is a 43.5% refundable tax offset on eligible R&D expenditure — meaning the offset is refundable even if the company has no taxable income. This is real cash from the ATO, not merely a reduction in a tax payable.
Eligible activities include developing novel algorithms, building machine learning models trained on proprietary data, testing architectures with genuinely uncertain technical outcomes, and conducting systematic experimentation on new methods. Routine software customisation, development following established methodologies, and testing based on known techniques are not eligible.
The critical bookkeeping requirement: eligible R&D expenditure must be tracked in a dedicated cost centre throughout the year. The costs to be captured include:
- Salary and wages of employees working on eligible R&D activities (with time sheet support)
- Contractor costs for eligible activities
- Cloud computing costs for experimental environments (not production)
- Specific equipment costs used exclusively in eligible activities
At year end, the R&D schedule is prepared by the tax adviser from the cost centre data and submitted to AusIndustry for registration (the registration deadline is 10 months after the end of the income year). Without a dedicated cost centre maintained in real time, the registration claim is based on retrospective reconstruction — which is harder to defend on review and routinely produces lower amounts than systematic tracking.
GST on Digital Products and Software Licences
Software sold as a perpetual licence is a taxable supply in Australia — GST at 10% applies. The licence fee is recognised as revenue at the point the licence is granted (assuming there are no other performance obligations tied to it).
SaaS subscriptions are also taxable supplies. As discussed above, the billing may be annual but the supply is delivered monthly — the GST obligation accrues monthly as the service is delivered (under the accruals method BAS) or when the invoice is issued (under the cash method).
Non-resident technology companies selling digital products or services to Australian consumers are subject to the Digital Economy provisions under Division 84A of the GST Act, effective from 1 July 2017. If a non-resident entity's GST turnover from Australian consumers exceeds $75,000 per year, it must register for GST, charge GST on sales to Australian consumers, and remit via the simplified registration system. Australian IT businesses reselling licences from non-resident vendors (for example, Microsoft, Salesforce) must confirm whether the non-resident vendor is already remitting GST — if not, the local reseller may have a reverse-charge obligation.
Foreign Currency Clients: FX Gains, Losses, and Rate Selection
IT consultancies with US or European clients regularly invoice in USD or EUR. The ATO's position under Tax Ruling TR 2014/6 is that foreign currency must be converted to Australian dollars for income tax and GST purposes. Acceptable conversion methods include:
- The actual exchange rate on the date of the transaction
- A monthly average exchange rate published by the RBA or a recognised financial institution
For GST purposes, the conversion must occur at the time of the taxable supply (or issue of the tax invoice, whichever is earlier). Using the monthly average is the most practical approach for high-volume foreign currency invoicing.
At year end, any outstanding debtors denominated in foreign currency must be translated at the year-end spot rate under Division 775 ITAA 1997. The resulting unrealised FX gain or loss is recognised in the profit and loss account. This is a common year-end adjustment that bookkeepers in IT firms sometimes omit, leading to a misstated debtors balance.
End-of-Period Checklist for IT and Software Firm Bookkeepers
- Review deferred revenue balance: confirm all annual and multi-year subscriptions have been apportioned correctly; deferred revenue at balance date should equal unearned subscription value
- Review implementation fee treatment for each major contract: confirm whether the fee is a distinct performance obligation (recognise on completion) or allocated to the subscription term
- Review software development costs: confirm research-phase costs are expensed; identify any development-phase costs that meet AASB 138.57 capitalisation criteria; calculate amortisation on previously capitalised development costs
- Compile R&D expenditure from the dedicated cost centre: prepare the schedule with salary, contractor, cloud, and equipment costs; flag for the tax adviser for AusIndustry registration well ahead of the 10-month deadline
- Confirm GST on all software licence and subscription invoices: verify that SaaS supplies to Australian customers are taxable; check that non-resident vendor arrangements are not creating a reverse-charge GST exposure
- Translate outstanding foreign currency debtors to AUD at the year-end spot rate under Division 775; recognise unrealised FX gains or losses in the profit and loss account
- Confirm monthly average exchange rates used for invoicing during the year are documented and consistently applied; retain RBA or bank rate records as support