Software startups in Australia have access to one of the most valuable tax incentives available to any business sector: the Research and Development Tax Incentive (RDTI). But accessing the RDTI requires meticulous bookkeeping throughout the year — the ATO and AusIndustry scrutinise R&D expenditure claims closely. Add to that the complexity of employee share schemes (ESOP), SaaS subscription revenue recognition, and the accounting treatment of internally developed software, and it becomes clear why startup bookkeeping requires specialist knowledge. This guide covers the key areas.
Research and Development Tax Incentive (RDTI)
The RDTI provides eligible companies with either a 43.5% refundable offset (for companies with aggregated turnover below $20 million) or a 33.5% non-refundable offset (for larger companies) on qualifying R&D expenditure under the Industry Research and Development Act 1986 and the ITAA 1997.
The fundamental requirement is that the R&D activities must constitute either core R&D activities (experimental activities with genuine scientific/technological uncertainty and intended to generate new knowledge) or supporting R&D activities (activities that are directly related to core R&D activities). The key word is experimental: the ATO and AusIndustry distinguish between genuine R&D (where the outcome is not known in advance) and routine software development (bug fixing, iterative improvement, straightforward feature addition using established methods).
From a bookkeeping perspective, the critical requirement is contemporaneous documentation. The ATO's guidance makes clear that time records, project management notes, and engineering documentation must exist at the time the R&D activities are conducted — they cannot be reconstructed retrospectively. The bookkeeper's role is to ensure that R&D expenditure is tracked in real time in a dedicated cost centre or sub-ledger: direct labour costs (with time-sheets linking to specific R&D projects), contractor costs, overheads allocated on a reasonable basis, and direct materials or software infrastructure costs attributable to R&D.
Registration with AusIndustry must occur within 10 months of the end of the income year. For a 30 June balancer, registration is due by 30 April of the following year — a deadline that is frequently missed by startups focused on product development rather than compliance. The bookkeeper's role in the R&D process includes: flagging eligible projects during the year, maintaining the expenditure tracking, and supporting the registration submission with correctly categorised cost data.
Internally Developed Software Capitalisation
The accounting treatment of internally developed software turns on AASB 138 (Intangible Assets) and its distinction between the research phase and the development phase of a project.
Costs incurred in the research phase — initial feasibility, concept investigation, and alternative solution assessment — must be expensed as incurred. They cannot be capitalised, even if they later prove to have contributed to a successful product.
Costs incurred in the development phase — once the technical feasibility of completing the software is established, the company intends to complete it and has the resources to do so — may be capitalised. AASB 138 para 57 sets out six criteria that must all be met for capitalisation to be permitted. In practice, most SaaS companies begin capitalising software costs from the point at which the technical design is confirmed and development sprints commence.
Capitalised software development costs (salaries of developers working on new features, SaaS hosting costs directly attributable to development rather than production, third-party API costs during development) are amortised once the software is available for use. Amortisation is over the software's useful life — typically 2-5 years for startup SaaS products, reflecting the fast-moving nature of the industry. The ATO's effective life for self-assessed software development is often 2.5 years (25% diminishing value or prime cost).
The RDTI and the capitalisation treatment interact: R&D expenditure that is capitalised cannot be claimed for the RDTI offset, because only revenue-account R&D expenditure (i.e., amounts that flow through the P&L, not the balance sheet) qualifies. This creates a tension between the accounting treatment (which may indicate capitalisation) and the tax treatment (which benefits from expensing). Where both are possible, the startup needs to make a deliberate choice with professional advice.
SaaS Revenue Recognition under AASB 15
SaaS subscription revenue is recognised over the service period, not at the time of payment. Monthly subscriptions are recognised monthly. Annual subscriptions paid upfront create a deferred revenue liability that is released to revenue on a monthly basis as the service is delivered.
The more complex question arises with multi-element arrangements: a SaaS company that bundles onboarding services, implementation support, and ongoing subscription access into a single contract must allocate the total contract consideration across each distinct performance obligation at its relative standalone selling price. Onboarding services that are distinct from the subscription are recognised at the point of delivery (or over the implementation period). The ongoing subscription access is recognised over the subscription term.
Professional services revenue (implementation consulting, data migration, custom development) is recognised over the service delivery period or at the point of delivery, depending on whether the services are point-in-time or over-time performance obligations.
Variable consideration — usage-based pricing, tiered pricing above a minimum, or volume discounts — must be estimated and constrained under AASB 15 paragraph 56. Revenue should only include the amount of variable consideration that is highly probable not to be significantly reversed.
Employee Share Schemes (ESOP)
Employee share schemes are a critical tool for early-stage startups that cannot pay market wages. The tax treatment for employees receiving ESOP options or shares has been substantially improved under the 2015 Tax Laws Amendment (Employee Share Schemes) Act and subsequent amendments.
For options issued at a discount under a qualifying ESS (Start-up ESS, available where the company has been incorporated less than 10 years, has aggregated turnover under $50M, and the options are granted at a minimum exercise price equal to market value), the tax on the discount is deferred until the options are exercised or sold — not at grant. This makes Start-up ESS options tax-efficient for the employee.
From a bookkeeping perspective, ESOP creates an obligation under AASB 2 (Share-based Payment). The fair value of options at grant date is recognised as an expense (share-based payment expense) over the vesting period, with a corresponding credit to an equity reserve. The fair value at grant date — typically calculated using a Black-Scholes or similar model — does not change after grant; subsequent share price movements do not affect the P&L.
For the company, ESOP options are not cash expenditure and do not create a PAYG withholding obligation at grant (under the Start-up ESS). PAYG withholding arises only if the employee makes a taxed-upfront election or at the point of disposal/exercise where applicable.
How Reconlink Supports Software Startups
Startups often operate with lean finance teams and high transaction volumes — card payments for cloud infrastructure, SaaS subscriptions for development tools, payroll runs, and investor transfers. Reconlink's automated coding rules classify recurring infrastructure costs (AWS, Azure, GCP, Vercel, Stripe, GitHub) to the correct expense or capitalised development accounts without manual intervention. Statements import from any bank — ANZ, CBA, the neobanks, anything that issues a CSV, Excel or PDF — by upload or the per-client email inbox. For R&D compliance, Reconlink's transaction history gives the bookkeeper a clean audit-ready record of expenditure by period that supports the annual AusIndustry R&D registration.