Cloud computing and SaaS arrangement costs (as customer)

As SaaS companies are themselves heavy consumers of third-party cloud software (ERP, CRM), whether implementation and configuration spend is capitalized as an intangible or expensed depends on control over identifiable code, an area where the IFRIC agenda decision led many companies to reverse prior capitalization, so getting this wrong overstates assets and understates expense in the periods system implementations are rolled out.

Does the arrangement give the entity control over an identifiable software asset it can direct the use of, or is it purely a right to access the supplier's hosted application? Are configuration or customization costs distinct from the underlying access service, or do they only have value bundled with the hosting arrangement? If no controlled asset exists, are upfront implementation costs treated as a prepayment expensed over the SaaS contract term rather than capitalized as an intangible?

1. Determine whether the arrangement gives the entity control over an identifiable software asset (e.g., it can direct the use of and obtain substantially all the remaining benefits from specific code) or whether it is simply a right to receive a service (access to the supplier's cloud application) over the contract term.
2. Where the entity is only accessing the supplier's software as a service with no control over the underlying code, recognize the ongoing access fee as an operating expense as the service is received, not as an intangible asset.
3. Separately evaluate configuration and customization costs: costs that create new, separable code the entity controls may qualify as an intangible under IAS 38; costs that merely configure the supplier's existing application (without creating a separable resource the entity controls) are generally expensed as the service of configuration is received, consistent with the IFRIC agenda decision.
4. Where fees are paid upfront for implementation services delivered over time, recognize a prepayment asset and release it to expense as the related service is performed, rather than expensing on payment or capitalizing as an intangible.
5. Document the classification of each material cost component (subscription fee, configuration, data migration, customization) rather than applying one blanket treatment to the whole project.

Where a genuine intangible asset is recognized (rare for pure cloud-access arrangements), measure at cost including directly attributable costs to prepare the specific, controlled code for use. Where costs are prepayments for future service (e.g., upfront implementation fees for a multi-year SaaS agreement), measure at the amount paid and release systematically over the period the related service is received. Where costs are expensed, recognize them in the period the configuration or access service is received, not deferred without a supportable prepayment rationale.

Disclose: (1) the accounting policy for cloud computing/SaaS arrangement costs as a customer, given heightened regulatory and IFRIC attention; (2) the amount and nature of costs expensed versus any amounts recognized as prepayments or intangible assets; (3) the basis for concluding whether control over identifiable code exists for any capitalized component; (4) significant implementation projects in progress and their expected cost recognition pattern.

• Capitalizing large ERP or CRM implementation costs as an intangible asset without establishing that the entity controls identifiable, separable code rather than merely accessing the supplier'
• s hosted application
• expensing all implementation costs immediately without assessing whether a prepayment asset should be recognized for services not yet received
• failing to revisit prior-period capitalization after the IFRIC agenda decision clarified that configuration of a SaaS application is generally not an intangible asset
• not separating data migration, customization, and pure configuration costs, which can have different conclusions even within the same implementation project.