Cloud Configuration Costs
Definition
Cloud configuration costs are the amounts a business spends setting up software it accesses as a service rather than owns — configuring a platform to its own processes, customising it, migrating data into it, and training its people. The accounting question is whether that spend creates an intangible asset for the customer. Under IFRS, the IFRS Interpretations Committee addressed the point in agenda decisions published in March 2019 and April 2021: in a typical cloud arrangement the customer receives a service across the contract term and does not control the software, so configuration and customisation costs are generally recognised as an expense, either as the service is received or across the period of access. Carrying the spend forward as an intangible asset arises in narrower circumstances — for example where the customer obtains additional code it controls, which is then assessed against the development-phase conditions in IAS 38.57. Worked example: a company pays £60,000 in its first year to a systems integrator to configure a finance platform, alongside £180,000 of annual subscription. The subscription is a service cost; the configuration spend is examined against what, if anything, the company controls once the work is done. Jurisdiction contrast: US GAAP is more permissive here, as ASC 350-40 allows a customer in a hosting arrangement that is a service contract to capitalise qualifying implementation costs and amortise them across the term. The judgement management makes is what the business controls when the configuration work finishes.
Taking a defensible position
The position
The IFRS Interpretations Committee's agenda decisions of March 2019 and April 2021 explain that in a typical cloud arrangement the customer receives a service and does not control the software, so configuration and customisation costs are generally expensed as the service is received. Capitalising them needs software the customer controls, such as additional code. ASC 350-40 permits qualifying implementation costs to be carried across the term.
A defensible posture
A management team reporting under IFRS can reasonably separate the elements of an implementation programme rather than treating it as one number: subscription, supplier configuration, code the entity builds and controls, data migration, and training. Where a distinct deliverable is controlled by the entity, it is assessed on its own terms. Where the work only makes a supplier’s software fit the business, an expense is the position most likely to hold.
Evidence to hold
- The service contract and any statement of work, showing what the supplier delivers and who holds rights over the output.
- An analysis of the implementation budget by element: subscription, configuration, bespoke code, data migration and training.
- Development records for any code the entity built and controls, where that element is being assessed separately.
- The expense-recognition or amortisation profile chosen, with the reasoning recorded at the time rather than later.
- For groups reporting under both frameworks, a note of where the IFRS and US GAAP answers diverge and why.
The challenge you may face
Expect a reviewer to start with the contract and ask what the entity controls once the programme ends. A large capitalised implementation balance sitting against a pure subscription contract is probed hard. Anticipate questions on whether training and data migration were swept into the total, whether the amortisation period matches the contract term, and how a group applying both frameworks explains the difference.
Complementary Terms
Concepts that frequently appear alongside Cloud Configuration Costs in practice.
A software distribution model in which applications are hosted by a service provider and made available to customers over the internet on a subscription basis. SaaS businesses are characterised by recurring revenue, high gross margins, and significant intangible asset value in software and customer relationships.
The International Accounting Standard governing the recognition, measurement, and disclosure of intangible assets. IAS 38 requires that an intangible asset be identifiable, controlled by the entity, and expected to generate future economic benefits.
Internal-use software is software a business acquires or develops for its own operations rather than to sell or licence. Under US GAAP, ASC 350-40 sets a stage-based model.
The accounting practice of recording an intangible expenditure as an asset on the balance sheet rather than expensing it immediately through the income statement. Under IAS 38, development costs must be capitalised once the six criteria in IAS 38.57 are met, whereas research costs must always be expensed.
The value embedded in a company's proprietary software assets, including applications, platforms, tools, and codebases. Software capital is a major intangible asset category that drives automation, scalability, and competitive differentiation in technology-enabled businesses.
Tax deductions available to businesses in the United Kingdom for qualifying expenditure on certain assets, effectively reducing the taxable profit by allowing the cost of the asset to be written off over time. Capital allowances are particularly relevant to intangible asset investment because the UK tax regime provides specific relief for expenditure on intellectual property, patents, know-how, and certain other intangible assets.
An intangible investment — R&D, brand-build, customer-acquisition with measurable payback, software development — that has been moved from operating expense to balance-sheet asset and amortised over its useful life under management accounting. Statutory accounting rarely permits the same treatment for internally-generated intangibles: IAS 38 imposes six conservatism criteria that are difficult to meet in practice; ASC 730 forces immediate expensing under US GAAP.
Intangible assets that are not captured on a company's balance sheet or in traditional accounting frameworks, including internally generated brands, proprietary data, organisational culture, and employee expertise. These often represent the largest source of hidden value in modern businesses.
Further Reading
SaaS configuration costs under IAS 38
The two IFRIC agenda decisions applied to configuration and customisation, with a worked ERP example under IFRS and US GAAP.
Read more →How operating businesses record and evidence investment in the systems they run on.
Read more →AI and IAS 38: When Can You Capitalise AI Development Costs?
IAS 38 sets six criteria for capitalising development costs, but applying them to AI projects is fraught with ambiguity. This article maps each criterion to AI development realities and provides practical guidance for CFOs and accountants navigating the recognition question.
Read more →Related FAQ
How should companies capitalise AI investments under IAS 38?
Under IAS 38, AI development costs can be capitalised once technical feasibility, intent to complete, probable future benefits, and reliable cost measurement are demonstrated — research phase costs must be expensed.
Read full answer →What are the ASC 350 rules for software capitalisation?
ASC 350-40 requires capitalisation of internal-use software development costs during the application development stage, while preliminary project and post-implementation costs must be expensed.
Read full answer →What is the difference between tangible and intangible assets?
Tangible assets have physical form: land, buildings, machinery, vehicles and stock. Intangible assets have none: they are identifiable non-monetary assets such as patents, trade marks, software and customer contracts.
Read full answer →Put this knowledge to work
Use Opagio's free tools to measure and grow the intangible assets that drive your business value.