CapEx vs OpEx: Accounting for Software Development Costs

The short answer

OpEx (operating expenses) hit the income statement immediately and reduce profit for the current period. CapEx (capital expenditure) is recorded as an asset on the balance sheet and expensed gradually through amortization over its useful life.

For software development, the logic is:

• research, idea exploration, comparing options — usually expensed;
• building a specific product once it is clear it will be completed and deliver value — may be capitalized;
• maintenance, minor fixes, user training, SaaS subscriptions — usually expensed.

The exact criteria depend on the framework your company follows: local standards, IFRS or US GAAP. Tax rules may also differ from accounting rules.

What capitalization usually requires

Under IFRS, the intangible assets standard (IAS 38) splits a project into a research phase and a development phase. Development-phase costs are capitalized only if the company can demonstrate:

1. technical feasibility of completing the product;
2. the intention to complete it and use or sell it;
3. the ability to use or sell the result;
4. how the asset will generate economic benefits;
5. available resources to finish it;
6. the ability to measure development costs reliably.

US GAAP uses similar logic for internal-use software: the preliminary project stage is expensed, the application development stage is capitalized, and the post-implementation stage is expensed. Software sold to customers follows separate rules.

Which costs go where

The key detail is time tracking. To capitalize salaries, you need to show how many hours the team spent building new capabilities rather than maintaining existing ones. Without task-level time records, an auditor is unlikely to accept the estimate.

Effect on financial statements

Income statement. Capitalizing raises current profit because costs are spread across future periods via amortization. Expensing lowers profit now but leaves no amortization burden later.

Balance sheet. Capitalization creates an intangible asset. It must be tested for impairment: if the product is shut down or stops delivering value, the asset is written off at once.

Cash flow statement. The cash leaves either way. But capitalized costs usually appear under investing activities rather than operating ones, so operating cash flow looks stronger.

Effect on valuation

Capitalization increases EBITDA, since amortization is excluded from it. That can improve the metrics banks and investors look at. Experienced analysts know this effect, though, and often adjust by looking at total development spend and free cash flow.

So aggressive capitalization is not a way to "look more valuable". It should reflect reality: if the product genuinely creates long-term value, the accounting shows it; if not, future write-offs will damage the statements.

Common mistakes

• Capitalizing everything, including maintenance and fixes.
• No documentation: the decision to start development, benefit estimates, hours worked.
• An amortization period that is too long for a product that ages quickly.
• Forgetting impairment when a project is closed or pivoted.
• Deciding after the fact at year end instead of setting rules at the start of the project.

When to talk to an accountant

Always before a major development project, when preparing for an audit, fundraising or a loan, and when moving to IFRS. An accountant or auditor will help you set the accounting policy, the criteria for moving from research to development, and how time is recorded. This article gives a general picture and does not replace professional advice.