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 an agenda decision published in March 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 concluded in March 2021 that a customer in a typical cloud arrangement receives a service and does not control the underlying software, so configuration and customisation costs are generally recognised as an expense as the service is received. Carrying the spend forward depends on the customer obtaining a resource it controls, assessed against IAS 38.57. 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.

SaaS (Software as a Service)

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.

IAS 38 (Intangible Assets)

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 (ASC 350-40)

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.

Capitalisation of Intangibles

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 may be capitalised when specific recognition criteria are met, whereas research costs must always be expensed.

Software Capital

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.