What it means
Normally, when a business pays salaries for coding or buys development tools, that money is recorded immediately as an expense on the profit and loss statement. However, software capitalisation allows you to pause this immediate cost recording for projects that are past the initial planning phase and heading towards creation.
This process is called capitalisation. You move the development costs onto the balance sheet as an intangible asset.
Why does this matter? For one, it prevents a massive drop in your profits during months when you are investing heavily in technology.
Secondly, it provides a truer picture of your company value, showing that you are building long-term digital property. In practice, accountants look at specific project milestones, such as proving the software is technically feasible before letting you capitalise the costs.
Once the software launches, you gradually move those asset costs into your expenses over time, a process known as amortisation. This matches the cost of building the software with the revenue it brings in over its useful life, keeping your financial statements balanced and aligned.
Building software is like buying a delivery van. You do not write off the entire cost of the van as fuel for a single day.
Instead, you treat it as an equipment asset and use it over several years.
In practice
Real-world examples
Example 1
A tech startup spends $50,000 on developer salaries to build a new customer app. Because the app will generate subscription fees for five years, they capitalise the cost instead of writing it off immediately. Each year they amortise $10,000, matching the cost to the income the app produces.
Example 2
An established logistics firm invests $30,000 in custom warehouse tracking software. They record this as an intangible asset on their balance sheet, spreading the expense over three expected years of use. This means $10,000 a year appears as amortisation in the profit and loss statement.
Example 3
A retail business pays $40,000 to upgrade its e-commerce checkout system. They capitalise these development costs to avoid wiping out their quarterly profit, amortising the amount over the software lifespan. Their auditors check that the work created a genuine new feature rather than routine maintenance.
Think of it
Building software is like buying a delivery van. You do not write off the entire cost of the van as fuel for a single day. Instead, you treat it as an equipment asset and use it over several years.
Formula
Calculation
Capitalised Cost = Direct Development Costs + Testing Costs (planning and research costs are excluded and expensed immediately)
Annual Amortisation = Capitalised Cost / Useful Life in Years
Example: Developer salaries of $40,000 plus testing fees of $5,000 equals $45,000 capitalised as an asset. If the research and planning phase cost a further $8,000, that amount is not capitalised and is recorded straight away as an expense.
Now spread the cost. If the $45,000 asset has a useful life of 5 years, the annual amortisation is 45,000 / 5 = $9,000. Without capitalisation, the full $45,000 would hit profit in the year of spending, whereas capitalising it reduces profit by only $9,000 each year for five years.Case study
Seen in the real world
GreenLogix, a fictional supply chain company, decided to build a custom route-optimisation platform to reduce fuel costs. During the initial brainstorming and research phase, they spent $20,000 on staff brainstorming sessions and general meetings. Accountants marked this portion as a normal operating expense. Once the team proved the concept was technically possible and began writing the core code, GreenLogix entered the development phase.
Over the next six months, they spent $80,000 strictly on developer salaries and specialised testing for this platform. Because this met accounting criteria for future economic benefit, GreenLogix capitalised the $80,000, placing it on the balance sheet as an intangible asset. When the software launched, they began amortising the asset at $16,000 per year over a five-year expected lifespan. This meant their profit and loss statement took a manageable, steady hit each year rather than absorbing a giant $80,000 loss upfront, giving stakeholders a clear view of how the new technology funded its own existence.
The comparison is stark. Had GreenLogix expensed everything, the first year would have carried $20,000 + $80,000 = $100,000 of cost, whereas with capitalisation it carried $20,000 + $16,000 = $36,000 in that year. The finance team documented each decision, including the date feasibility was proven, because auditors would ask for the evidence.
Watch out
Common mistakes
- Capitalising everyday maintenance and bug fixes, which must always be recorded as normal operating expenses.
- Failing to separate the early planning and research phase from the actual development phase.
- Continuing to amortise software after it has been retired or replaced by a newer system.
Questions
People also ask
Can all software development costs be capitalised?
No. Only costs incurred during the actual development phase, after technical feasibility has been proven, qualify for capitalisation. Initial research and ongoing maintenance cannot be capitalised.
What is the difference between capitalisation and amortisation?
Capitalisation turns a development cost into an asset on your balance sheet. Amortisation is the process of gradually moving that asset value into your expenses over the useful life of the software.
Does software capitalisation affect my tax bill?
Yes, because it changes the timing of when expenses appear on your financial statements. Always consult a qualified accountant to ensure your local tax authority rules are met.