Skip to main content

Should companies capitalise development costs—or write them off immediately?

The moment a software company finishes building a new product feature and makes the first sale, the cost of creating that feature—the salaries of engineers, the cloud infrastructure, the design work—vanishes from the accounting decision point. Under GAAP, those costs are an operating expense, recorded immediately when incurred. Under IFRS, they may become an asset on the balance sheet, a deferred claim against future revenue. The same underlying cash outflow produces strikingly different reported earnings, asset bases, and profitability ratios. For investors comparing a US tech firm (GAAP) against a European competitor (IFRS), this difference alone can make one appear dramatically more profitable than the other—not because the business is stronger, but because the accounting regime is.

This article explains the rules governing development costs under each standard, the economic logic behind each approach, and the pitfalls for investors who miss the gap.

Quick definition​

Development costs are expenditures incurred in planning and executing the creation of a new product or process—distinct from research (early exploration) or pre-development. Under IFRS, qualifying development costs can be capitalised as an intangible asset and amortised over the years the product generates revenue. Under GAAP, virtually all R&D costs are expensed immediately.

Key takeaways​

  1. IFRS allows capitalisation; GAAP typically forbids it — IFRS IAS 38 permits deferring development costs as an asset if the project meets strict criteria (technical feasibility, intent to complete, probable future benefit, adequate resources). GAAP ASC 730 requires nearly all R&D to be expensed immediately.

  2. Capitalisation inflates assets and earnings — A company that capitalises development under IFRS reports higher net income (cost deferred to future periods) and a larger balance sheet than the same company expensing under GAAP, all else equal.

  3. Future amortisation creates a drag — Capitalised costs must be amortised over the product's useful life, creating a non-cash charge that returns to the income statement in future years; investors must track when that amortisation begins.

  4. GAAP reflects conservatism about R&D success — The immediate expense approach assumes R&D is inherently uncertain; only projects proven in the marketplace (like software capitalisation under ASC 985) break this rule.

  5. Software under ASC 985 is a partial exception — GAAP allows capitalisation of certain internal-use software development costs after the preliminary stage, narrowing but not eliminating the GAAP–IFRS gap.

  6. Cross-border comparisons demand restatement — Investors must strip out capitalised development costs from IFRS statements and model the expense impact to compare fairly against GAAP peers.

What counts as development—and what doesn't?​

The distinction between research and development is fundamental to both standards, and both rely on it to gate the capitalisation question.

Research consists of investigative activities aimed at discovering new knowledge, new products, or new processes. It is inherently uncertain; the outcome is unknown, and many research projects fail. Both GAAP and IFRS mandate that research costs be expensed immediately. A biotech firm investigating a promising compound, a software company prototyping a new algorithm—these are research, and the costs vanish from the income statement as incurred.

Development is the application of research findings (or existing knowledge) to create a new or improved product or process, with a reasonably clear plan and purpose. Development is less uncertain than research; the technical approach is established, and the organisation is moving toward a commercialisable asset.

This boundary is notional and contested. A company claiming that 80% of its R&D spending is "development" and thus (under IFRS) eligible for capitalisation is making a judgement that auditors will scrutinise. The more grey-market the business (biotech, early-stage software, deep learning), the blurrier the line.

IFRS sets six criteria for capitalisation of development costs. All six must be met:

  1. Technical feasibility: The development must be technically possible to complete.
  2. Intention to complete: Management intends to complete and use (or sell) the asset.
  3. Ability to use or sell: The company can demonstrate demand or internal intention to use the asset.
  4. Future economic benefits: It is probable that future revenues (or cost savings) will result.
  5. Adequate resources: Technical, financial, and other resources are available to complete the project.
  6. Reliable measurement: Development costs can be measured reliably.

These are conjunctive; failure on any one bars capitalisation. In practice, criterion 1 (technical feasibility) and criterion 4 (probable future economic benefit) are the hardest to satisfy and the most frequently disputed.

GAAP's rule is simpler and more restrictive: R&D is expensed. Full stop. The only material exception is internal-use software (ASC 985), which permits capitalisation of costs incurred after the preliminary stage and during the development and testing phase. Even there, certain costs (project management, training) are expensed, and the capitalised balance must be amortised over a useful life of 3–7 years, typical for software.

The income statement and balance sheet impact​

Imagine a software company spending $10 million over two years to build a new product platform. The product launches at the start of year 3 and generates revenue for five years.

Under GAAP:

  • Year 1: $10 million R&D expense; operating income and net income are reduced by $10 million.
  • Year 2: Same; another $10 million expense.
  • Years 3–7: No amortisation or capitalisation-related charges; R&D expense continues for ongoing work, but the platform development is fully written off.
  • Total income statement impact over the 7 years: $20 million R&D charge, $0 amortisation.

Under IFRS (assuming capitalisation is justified):

  • Year 1: $10 million capitalised as an intangible asset; no impact on operating income.
  • Year 2: Same; $10 million capitalised; balance sheet now shows $20 million in development assets.
  • Year 3: Amortisation begins. If the asset is amortised over 5 years (the product life), $4 million per year is expensed as amortisation. Operating income is reduced by $4 million.
  • Years 4–7: Amortisation continues at $4 million per year.
  • Total income statement impact over the 7 years: $20 million amortisation (same as GAAP R&D), but spread over years 3–7, not years 1–2.

The earnings distortion:

  • Year 2 net income is $10 million higher under IFRS than GAAP (the capitalised cost hasn't hit the P&L yet).
  • Year 3 net income is $4 million lower under IFRS (amortisation has begun); the gap narrows in years 4–7.
  • Over the full 7 years, cumulative net income is the same, but the timing is profoundly different.

For a growth company with multiple development cycles in flight, this timing gap can lead to systematically higher reported earnings under IFRS during periods when capitalisation is accelerating.

The balance sheet also diverges. At the end of year 2, the IFRS company reports $20 million in capitalised development assets; the GAAP company reports zero. This inflates the IFRS company's total assets and (if equity is otherwise the same) may flatten its return-on-assets ratio. A lender or regulator watching debt-to-assets ratios will perceive the IFRS balance sheet as more leveraged.

How auditors and management police the boundary​

IFRS standards are principles-based, and the capitalisation decision relies heavily on management judgement. Auditors must assess whether the six criteria are genuinely met, and they have considerable discretion in challenging a company's claim that a project is "technically feasible" or has "probable future benefit." In practice, this creates variation: a project that one auditor accepts as capitalizable may be rejected by another.

The most common auditor intervention is to exclude certain overhead or indirect costs (salaries of finance and legal staff, executive time) from the capitalised pool, even if management includes them. Auditors reason that these costs would be incurred even if the project failed, and therefore cannot be "incremental" to the development.

GAAP's bright-line rule (expense everything except specific ASC 985 software) eliminates this grey zone. However, it also creates its own distortions: a company may classify a development cost as "infrastructure" or "process improvement" rather than "R&D" to circumvent expensing rules. A company building proprietary cloud infrastructure for its SaaS platform might expense it as R&D, or capitalise it as software infrastructure—a distinction with material income statement consequences.

Companies are also aware of earnings pressure. A company falling short of guidance might look for opportunities to capitalise development costs that were previously expensed, or to lengthen the useful life of capitalised assets to reduce amortisation. These shifts are often disclosed in the accounting-policy footnote, but investors who don't read footnotes miss them entirely.

The three cases: biotech, software, and pharma​

Biotech and pharmaceutical development is perhaps the most contentious. Biotech companies spend hundreds of millions on drug discovery and clinical trials before a product is approved and marketable. Under GAAP, virtually all of this is R&D expense—a net-income drain that makes unprofitable companies appear even less profitable. Under IFRS, a company can (in theory) argue that a drug candidate that has cleared Phase II trials is "technically feasible" and likely to succeed, and thus capitalise costs from Phase III onward. In practice, IFRS auditors are conservative here; the probability of FDA approval is never certain, and many IFRS companies still expense most development costs. However, some European biotech firms do capitalise development costs, widening the gap versus their US-listed peers.

Software and SaaS offers a middle ground. ASC 985 gives GAAP companies a route to capitalise internal-use software after the preliminary design phase. This is more permissive than expensing everything, but less so than IFRS, which allows capitalisation of software developed for sale (not just internal use). A SaaS company building a new product for external customers can capitalise under IFRS but (typically) cannot under GAAP unless the software is for internal use. This is a material difference for subscription-software businesses, many of which are GAAP-filers.

Manufacturing and industrial development (e.g., a car company developing a new engine) is less contentious. Both GAAP and IFRS generally require that production tooling and equipment be capitalised, not expensed. Development of the tooling—design, prototyping, testing—may be eligible for capitalisation under IFRS but is often expensed under GAAP. However, this is a smaller dollar issue than software or biotech.

Real-world examples​

SAP and Oracle: SAP, a German software company reporting under IFRS, historically capitalised a larger share of its development costs than Oracle, a US company on GAAP. In the 2010s, when both were heavy investors in cloud infrastructure and SaaS platforms, SAP's reported operating margin was often several percentage points higher than Oracle's. Some of this gap reflected genuine business differences, but some was purely accounting: SAP's capitalised development inflated its net income relative to Oracle's expensed R&D. Astute investors built reconciliation models to restate SAP's results on a GAAP basis, revealing that the gap was smaller than headline earnings suggested.

Roche and Merck: Roche, the Swiss pharma giant on IFRS, has been more willing than Merck (US, GAAP) to capitalise drug-development costs for products in advanced trials. During years when Roche had multiple late-stage assets and Merck had fewer, Roche's net income benefited from the deferred-cost timing, even if the underlying cash R&D spend was similar or higher. After accounting adjustments, the profitability gap narrowed.

Spotify and Amazon: Spotify, a Swedish company on IFRS, capitalises a portion of software-development costs for its platform. Amazon, on GAAP, expenses almost all of its technology R&D immediately. When comparing the two as platform/subscription businesses, a superficial look at operating margins would overstate Spotify's profitability relative to Amazon. Restating Spotify's financials to expense all development costs shows a tighter margin comparison.

Common mistakes​

  1. Assuming IFRS always capitalises development costs — Many development projects fail the IFRS criteria, particularly criterion 4 (probable future economic benefit). IFRS companies that develop experimental products or pursue uncertain markets will still expense most costs. Not all IFRS reporters capitalise heavily.

  2. Ignoring future amortisation obligations — An investor sees a spike in capitalised development assets and assumes the company's asset base has genuinely improved. What the investor misses is that amortisation will begin in future periods, and that amortisation will depress earnings for years. The balance sheet benefit comes with a future income statement drag.

  3. Using headline operating margin to compare across regimes — Comparing a GAAP company's 15% operating margin to an IFRS company's 20% margin without adjusting for capitalisation policy is a beginner's error. The gap may be purely accounting.

  4. Overlooking useful-life assumptions — Two IFRS companies developing software may capitalise the same amount but assign different useful lives (one uses 5 years, another uses 7). This changes the annual amortisation and future earnings. Read the policy footnote.

  5. Forgetting that software development is an exception under GAAP, not the rule — ASC 985 allows capitalisation of internal-use software, but many companies still expense it entirely (either because they were built before ASC 985 was adopted, or for conservatism). Don't assume every GAAP software company is expensing all R&D.

FAQ​

Q: Can a company switch from expensing to capitalising development costs to boost earnings? A: Yes, but it must disclose the change in the accounting-policy footnote. Auditors must sign off on the change. This is a red flag for investors; a sudden shift from expensing to capitalising (or a lengthened useful life) should prompt scrutiny of the rationale.

Q: Why don't GAAP and IFRS converge on a single rule for development costs? A: The FASB (which sets GAAP) and IASB (IFRS) have differing philosophies. The FASB views R&D as inherently risky and prefers the conservatism of immediate expensing, even if it means earnings volatility. The IASB favours matching costs against the revenues they generate, which supports capitalisation. Converging would require one side to abandon its philosophy, which has not happened.

Q: If I'm analysing an IFRS company with large capitalised development, how do I adjust for comparability with GAAP? A: Build a model that assumes all capitalised development is expensed immediately (as it would be under GAAP). Recalculate operating income and net income with the adjustment. Note that this may make the company appear much less profitable in the near term, but it also removes future amortisation charges. The true recurring earning power is somewhere in between.

Q: Does capitalisation of development costs affect cash flow? A: No. Capitalisation is a pure balance-sheet decision; it doesn't change the cash outflow. Operating cash flow is unaffected by whether a cost is expensed or capitalised (both reduce cash). Amortisation, being non-cash, is added back in the operating cash flow section. So the cash impact is identical under both standards; only the income statement and balance sheet differ.

Q: Can a company capitalise development costs for a product that ultimately fails? A: Yes, it can capitalise the costs while the project is underway. When it becomes clear the product will not succeed, the asset is written down (impaired) or fully amortised. An impairment is a large, often non-recurring charge that can depress earnings in the period the company acknowledges failure. This is why auditors scrutinise capitalisation decisions so closely.

Q: How does development cost capitalisation interact with segment reporting? A: A company with multiple business segments may capitalise development costs by segment. Investors comparing segment profitability should check the capitalisation policy for each segment; one segment may have a lot of capitalised assets and thus lower amortisation, while another expenses aggressively. Cross-segment comparisons can be misleading without this context.

  • Intangible assets and goodwill — Capitalised development costs are recorded as intangible assets. Understand how intangible assets are tested for impairment and amortised.
  • Software capitalisation under ASC 985 — The specific GAAP rules for internal-use software capitalisation, and how they differ from IFRS.
  • Useful life and amortisation policy — How management selects the useful life of an asset, and why this choice has significant earnings impact.
  • Accounting policy changes and restatements — When a company shifts its capitalisation or useful-life policy, financial statements may be restated; understand how to spot and interpret these.
  • Impairment testing for intangible assets — Capitalised development assets can become impaired if future economic benefits don't materialise; IFRS and GAAP have different impairment models.

Summary​

Development costs sit at the intersection of measurement philosophy and earnings manipulation risk. IFRS permits capitalisation if strict criteria are met, deferring the expense to future periods when revenue is generated. GAAP nearly always requires immediate expensing (with the exception of internal-use software under ASC 985), prioritising conservatism and simplicity over theoretical matching. This accounting choice creates material differences in reported earnings and assets, especially for R&D-intensive businesses like software and biotech.

Investors comparing companies across regimes must build reconciliation models that restate IFRS financials on a GAAP basis (or vice versa) to see true operating performance. A company that appears highly profitable under IFRS due to capitalisation may show much tighter margins when restated for GAAP expensing. Future amortisation obligations must also be tracked; today's balance sheet asset becomes tomorrow's income statement drag.

The takeaway is not to distrust either standard, but to recognise that the same underlying business can produce radically different reported results depending on the accounting framework. Understanding the rules—and the gap between them—is essential for any investor comparing companies across borders or regulatory regimes.

Next​

Revaluation of fixed assets under IFRS