Cloud Computing and SaaS Accounting: Hosting Arrangements, Capitalisation, and ASU 2018-15

Software Licence vs Service Arrangement

The fundamental question in cloud computing accounting is whether the arrangement conveys a software licence or is purely a service. A software licence gives the customer control over the software — the right to run it on their own infrastructure, hold it beyond the contract term, or take possession of it in the event of vendor bankruptcy. A licence produces an intangible asset on the customer's balance sheet.

A service arrangement (SaaS, cloud hosting, software-as-a-service) gives the customer access to software running on the vendor's infrastructure for the contract period, with no right to the underlying software code or the ability to run it independently. No asset is recognised for the access right itself — the periodic subscription fee is simply a service expense.

Most modern enterprise software arrangements (Salesforce, Workday, SAP S/4HANA Cloud, Microsoft 365) are service arrangements — the customer pays for access, not for a perpetual licence. This classification has a major impact on financial statements: no software asset on the balance sheet, no depreciation, but a recurring operating expense. See the software development accounting guide for how this differs from internally developed software.

ASU 2018-15: Cloud Implementation Costs

Before ASU 2018-15, there was no explicit GAAP guidance on whether implementation costs for cloud/hosted arrangements (costs to configure, customise, and test the cloud system) should be capitalised or expensed. Some companies capitalised them as service assets; others expensed them immediately. This created significant comparability problems — two companies implementing identical cloud ERP systems could report dramatically different costs depending on their accounting policy choice.

ASU 2018-15 (effective for public companies in fiscal years beginning after December 15, 2019) resolved this by applying the same three-stage framework from ASC 350-40 (internal-use software) to the implementation costs of cloud computing arrangements that are service arrangements — even though no software asset is recognised for the cloud access right itself.

Applying the Three-Stage Framework

The three stages for cloud implementation costs follow the same logic as internal-use software:

Preliminary project stage → Expense: Costs incurred during planning and evaluation (selecting the vendor, evaluating alternatives, conceptual design) are expensed as incurred. Even if the project is ultimately approved and implemented, these preliminary costs cannot be capitalised retroactively.

Application development stage → Capitalise: Once management has authorised and committed to funding the implementation and it is probable the project will be completed and used, implementation costs are capitalised. This includes: configuration of the cloud application, customisation coding, data migration (the portion directly attributable to the new system), and integration testing. External consulting costs incurred in this stage are generally capitalised along with internal labour costs (if directly attributable).

Post-implementation/operations stage → Expense: Costs incurred after the system is ready for its intended use — training, ongoing maintenance, help desk support, minor bug fixes — are expensed as incurred.

Presentation and Amortisation

Capitalised cloud implementation costs are presented on the balance sheet separately from any prepaid subscription fees — they are not netted against the hosting asset. The capitalised amount is amortised straight-line over the term of the hosting arrangement (including reasonably certain renewal periods), not over the software's useful life (since there is no software asset to depreciate separately).

Critically, the amortisation of capitalised cloud implementation costs is presented in the same income statement line as the hosting fees — typically operating expenses (SG&A or cost of revenue), not as depreciation and amortisation of intangible assets. This is an important presentation nuance that affects how analysts should interpret operating expense trends.

If the cloud arrangement is abandoned or the vendor relationship is terminated, the unamortised capitalised costs are immediately written off. Impairment testing follows the ASC 360 framework for the hosting arrangement as a whole.

SaaS Company Revenue Recognition

From the SaaS vendor's perspective, subscription revenue is recognised under ASC 606 as a single performance obligation satisfied over time. The customer simultaneously receives and consumes the benefit of cloud access as the vendor provides it — satisfying the over-time revenue recognition criteria. Revenue is typically recognised ratably (straight-line) over the subscription period.

Upfront setup fees and implementation services provided to SaaS customers may be separate performance obligations if they are distinct. If they are not distinct from the ongoing service, setup fees are deferred and recognised over the full expected customer relationship period. Contract acquisition costs (sales commissions) are capitalised under ASC 340-40 and amortised over the expected customer relationship if the amortisation period exceeds one year. For the full revenue recognition framework, see the ASC 606 guide.

SaaS Company Cost Capitalisation

SaaS companies that develop their own platforms apply ASC 350-40 to the development costs of their cloud platform. The three-stage framework applies: preliminary costs expensed, development stage capitalised, post-implementation expensed. Many SaaS companies capitalise significant engineering costs during the application development stage — creating large intangible assets on their balance sheets that represent the capitalised cost of building and enhancing their software platform.

Tax Treatment of Cloud Costs

For tax purposes under the TCJA, software development costs (including cloud platform development) incurred after December 31, 2021 must be capitalised and amortised over 5 years (domestic) or 15 years (foreign). Cloud subscription fees paid as service expenses are generally deductible when paid under the cash method or when incurred under the accrual method. Implementation costs that are capitalised for GAAP under ASU 2018-15 may or may not receive the same treatment for tax — the tax treatment depends on the nature of the expenditure and may need to be evaluated separately.