Your ERP records every stock movement, every purchase invoice, every production order. But what happens with assets you cannot touch? Patents filed this year, a brand portfolio inherited from an acquisition, capitalised software licences, right-of-use assets arising from cloud contracts — these intangible assets represent a growing share of your company’s value, and they are often the least well-tracked in the financial information system.
According to Ocean Tomo’s annual study on intangible asset market value (Intangible Asset Market Value Study 2025), intangible assets now account for 92% of the market capitalisation of S&P 500 companies. The stakes are no longer academic: for a growing mid-market company or one in a post-merger phase, poor tracking of intangibles in the ERP translates into an undervalued balance sheet, a failed impairment test, or errors in the presentation of financial statements.
This guide is aimed at CFOs, accounting managers, and financial controllers who want to structure the treatment of intangible assets in their ERP, from initial configuration to operational alerts.
The Four Main Families of Intangible Assets to Manage in Your ERP
Intangible assets form a heterogeneous set. Before configuring your ERP, you need to distinguish four families, each governed by distinct accounting rules.
Acquired Software and Internally Developed Software
Software acquired from a vendor under a perpetual licence is a classic intangible asset. It is recorded on the balance sheet at acquisition cost and depreciated on a straight-line basis over its probable useful life, typically 3 to 5 years.
Internally developed software follows a different logic. IAS 38 distinguishes two phases: the research phase, whose costs must be expensed, and the development phase, whose costs may be capitalised if six cumulative conditions are met: demonstrated technical feasibility, intention to complete, ability to use or sell the software, probable generation of future economic benefits, availability of resources, and ability to measure development expenditure reliably (IAS 38, §57).
The most frequent mistake: capitalising corrective maintenance costs or incremental improvements by qualifying them as “development”, when they belong to the research phase or constitute simple operating expenses.
SaaS Subscriptions and Right-of-Use Assets — The IFRS 16 / IAS 38 Boundary
This is the question every CFO must resolve before signing a multi-year cloud contract.
A standard SaaS subscription — Salesforce, Microsoft 365, SAP Business Cloud on shared infrastructure — is not an intangible asset within the meaning of IAS 38. The company does not control the underlying asset: it pays to access a service. The cost is recorded as an operating expense over the term of the contract, in the income statement, not on the balance sheet.
The nuance lies in IFRS 16. If the SaaS contract grants access rights to a dedicated and identified infrastructure (reserved physical servers, an isolated private instance), the contract may be reclassified as a lease. In that case, the company must recognise a right-of-use (ROU) asset on the balance sheet and a corresponding lease liability. The ROU is depreciated over the contract term, typically 3 to 5 years.
This distinction directly impacts your financial ratios: an IFRS 16 ROU asset weighs on the balance sheet and the leverage ratio, without the economic advantages of a capitalised investment. Before signing a dedicated hosting contract with a vendor, have the accounting treatment validated by your statutory auditor.
For a deeper dive into the CapEx/OpEx trade-off in an ERP project, see our guide CapEx or OpEx for Your ERP Project?
Intellectual Property: Patents, Trademarks and Proprietary Software
Intellectual property forms a third family, with its own valuation rules and useful life considerations.
An acquired patent constitutes a separately identifiable intangible asset, recorded at its acquisition cost and amortised over the remaining legal protection period (20 years maximum for a European patent, but often 7 to 10 years in practice depending on actual economic life).
An internally developed patent follows the IAS 38 rules described above: only the development phase is capitalisable, subject to the relevant conditions. Research costs incurred before the patent filing remain as expenses.
Trademarks are subject to a specific rule: a trademark with an indefinite useful life (indefinitely renewable) is not amortised but is subject to a mandatory annual impairment test (IAS 36). The ERP must therefore manage two types of intangible assets related to trademarks: periodic renewal costs (to be provisioned or capitalised depending on their nature) and recoverable value tests.
Goodwill — The Post-Acquisition Intangible Asset
In an acquisition, the price paid generally exceeds the fair value of the target’s identifiable net assets. This excess constitutes goodwill (or acquisition premium).
Under IFRS 3, goodwill is not amortised. It is subject to a mandatory annual impairment test (and mid-year if indicators of value loss appear), in accordance with IAS 36. The ERP must allow goodwill to be allocated to cash-generating units (CGUs) and must support documentation of impairment tests.
In some local GAAP frameworks, acquired goodwill may be amortised over its estimated useful life (e.g., up to 10 years in certain European jurisdictions). A company preparing both IFRS consolidated accounts and local statutory accounts must therefore manage two distinct treatments in its ERP simultaneously.
How to Configure Your ERP for Intangible Assets
Asset Categories to Create
The ERP chart of accounts for intangibles must distinguish at a minimum the following families, aligned with local accounting plans and IFRS standards:
| Category | Nature | Typical Depreciation Period |
|---|---|---|
| Establishment costs | Start-up and pre-incorporation costs | 5 years max |
| R&D costs | Capitalised development phase costs | 3 to 7 years |
| Acquired software and licences | Perpetual licence software | 3 to 5 years straight-line |
| Right-of-use assets (IFRS 16) | Dedicated infrastructure leases | Contract term |
| Acquired patents, licences and trademarks | IP with finite useful life | Remaining protection period |
| Distribution rights | Contractual or economic life | Contract or economic life |
| Goodwill | Acquisition premium (IFRS) | Not amortised — impairment test |
In practice, mid-market ERPs provide configurable category codes. Avoid grouping all intangibles in a single generic category: granularity is essential for producing financial statement notes and fixed asset tracking schedules.
Depreciation Periods and Recommended Methods
Depreciation periods are not standardised to the day, but market practice converges around precise ranges:
- Acquired ERP software (perpetual licence): 5 to 7 years straight-line — actual economic life of a core ERP, between two major migrations
- Acquired business software: 3 to 5 years straight-line depending on the version upgrade frequency
- Internally developed software: 3 to 7 years depending on complexity and estimated functional lifespan
- Acquired patent: remaining legal protection period, capped at the economic exploitation life
- IFRS 16 ROU asset: contract term, or useful life if shorter
- Capitalised R&D costs: 3 to 5 years maximum per accounting standards guidelines
For trademarks with indefinite useful lives and IFRS goodwill, the ERP must create a specific category with a “non-depreciable” indicator and an annual reminder date for the impairment test.
Automated Alerts to Configure in Your ERP
A well-configured intangible assets module integrates three types of alerts:
-
Patent/trademark renewal alert: trigger 90 days before the expiry of an industrial property right. Both the IP counsel and the CFO should receive this alert simultaneously — an untreated renewal leads to the lapse of the right and the immediate obsolescence of the balance sheet asset.
-
Annual impairment test reminder: automatically generate a task 30 days before the year-end closing date for all indefinite-life intangible assets (goodwill, non-amortised trademarks). Without this reminder, the test is often deferred to the last minute, with data prepared in haste.
-
End-of-contract alert for SaaS assets under depreciation: if a SaaS contract has been reclassified as an IFRS 16 ROU asset and is being depreciated, the system must alert before the contract expires to avoid continuing to depreciate an asset that no longer exists (double accounting).
The Five Most Common Errors to Avoid
1. Capitalising a Standard SaaS Subscription as an Intangible Asset
The error is understandable: an annual subscription worth €80,000 looks like an investment. It is not one. A SaaS subscription on shared infrastructure is an operating expense, full stop. Capitalising it without verification creates a fictitious asset on the balance sheet and an anomaly that will be flagged at the next audit.
2. Confusing Acquired Patents with Internally Developed Patents
An acquired patent is simply capitalised at acquisition cost. An internally developed patent follows the IAS 38 rules on research and development phases. Confusion leads either to capitalising research costs (prohibited) or to expensing capitalisable development costs (balance sheet undervaluation).
3. Forgetting to Capitalise ERP Implementation Costs
The configuration and initial setup costs of an ERP for own use may be capitalised under IAS 38, provided the development phase criteria are met. Data migration costs, training, and user acceptance testing assistance are not capitalisable. Precise breakdown by service nature, documented during the ERP project, makes it possible to maximise capitalisation and reduce the impact on the profit or loss for the year of deployment.
4. Amortising IFRS Goodwill
Under IFRS, goodwill is not amortised. Only an impairment test can lead to writing down part or all of the acquisition premium. Configuring an ERP category with an automatic amortisation schedule for goodwill produces incorrect IFRS financial statements. If your ERP does not allow creating “non-depreciable with impairment test” categories, a specific configuration or documented manual treatment is required.
5. Failing to Manage Partial Portfolio Disposals
When selling part of a brand portfolio or a set of patents, the disposed assets must be derecognised at their net book value at the date of disposal. The gain or loss on disposal (difference between the sale price and the net book value) is recognised in profit or loss. The ERP must allow partial disposals of intangible assets with complete transaction traceability.
Towards a Complete Intangible Asset Map in Your ERP
The Annual Inventory: Who Does What
The intangible asset map cannot rest solely on the ERP’s fixed assets module. It requires a cross-functional review:
- The CFO leads the inventory, verifies consistency between the intangible assets list and the balance sheet, and ensures impairment tests have been performed.
- The CIO catalogues active software and cloud subscriptions, distinguishes shared contracts from dedicated access, and provides contract end dates.
- The IP counsel (or specialist attorney) maintains the list of industrial property rights in portfolio with their expiry dates and territorial scope.
- The financial controller ensures the link with CGUs for the impairment test of goodwill and indefinite-life assets.
A formalised annual inventory, carried out 30 days before the year-end closing, resolves discrepancies before closing-period pressure makes corrections difficult.
ERP Modules Suited to the Task
The major ERP vendors take different approaches to intangibles management:
SAP S/4HANA: the FI-AA (Fixed Assets Accounting) module manages intangible assets in configurable asset classes. The depreciable/non-depreciable distinction is native. IFRS 16 is handled via the RE-FX (Real Estate Flexible) module or FI-AA with specific configuration. Granularity is maximal but requires fine-grained setup during implementation.
Microsoft Dynamics 365 Finance: the Fixed Assets module supports customisable intangible asset categories and allows configuring multiple parallel ledgers (local GAAP book, IFRS book). IFRS 16 has been natively supported since version 10.0. The initial intangible configuration is less costly than SAP for mid-market companies.
Sage X3: the Fixed Assets module supports intangibles with configurable categories. Managing indefinite-life assets with impairment testing requires specific configuration or manual supplementation.
Odoo: the Assets module covers standard depreciation cases. It is less granular than mid-market solutions for complex scenarios (impairment testing, multi-contract IFRS 16 ROU assets, partial disposals). For a company with a significant IP portfolio, a specialised tool alongside the ERP often remains necessary: IPfolio or Anaqua for patent portfolio management, integrated via API.
What IFRS 18 Changes in 2027 for Intangibles
IFRS 18 (applicable from 1 January 2027) will change the presentation of the income statement by introducing five mandatory categories. Intangibles that are poorly classified today will have a direct impact on the distinction between “Operating” and “Investing” in the new format. Internally developed software whose development-phase costs have been capitalised generates depreciation classified as operating charges. Poorly documented goodwill impairment risks being difficult to allocate to the correct IFRS 18 category.
Preparing for IFRS 18 therefore also involves revisiting the treatment of intangibles in your ERP. Our article IFRS 18 from 2027: What CFOs and CIOs Need to Prepare in Their ERP details the workstreams to launch now.
Managing intangible assets is one of the most common blind spots in mid-market ERP projects. Software is capitalised without documenting the phases, SaaS subscriptions are treated as CapEx without verifying control over the underlying asset, post-merger goodwill is forgotten in a generic account. These errors are not negligence: they reflect the genuine complexity of a topic that sits at the intersection of accounting, IP law, and the technical configuration of the ERP.
To go further, see our complete guide to fixed asset management in an ERP (asset lifecycle, declining-balance depreciation, component approach, physical inventory) and our article on ERP project financing: grants, subsidies and tax credits for companies that capitalise development costs and want to optimise their tax position.
