Cloud Computing Implementation Costs — ASU 2018-15 Capitalization (Customer's Accounting)
Capitalizing implementation costs incurred by a customer in a cloud computing (hosting) arrangement — applying ASC 350-40's three-stage model to costs like configuration, customization, and integration of a SaaS solution.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Prepaid Implementation Costs — Cloud Arrangement (Other Assets) | Asset (+) | 3,500,000.00 | - |
| Accounts Payable / Cash (System Integrator / Vendor Implementation Fees) | Liability (+) / Asset (-) | - | 3,500,000.00 |
💡 Accountant's Note
ASU 2018-15 (effective 2019 for public companies) extended the ASC 350-40 three-stage model to implementation costs of cloud computing arrangements where the customer does NOT control the underlying software (hosting arrangements — pure SaaS). Before ASU 2018-15: all cloud implementation costs were expensed as incurred (because the customer had no intangible asset — they licensed access, not the software itself). After ASU 2018-15: implementation costs during the application development stage are CAPITALIZED as a prepaid asset and amortized over the service period. Not capitalizable: preliminary project stage costs, training costs, data conversion costs (unless integral to the implementation), post-implementation maintenance. Applies to: Salesforce CRM implementation, SAP S/4HANA on cloud, Workday HRIS, ServiceNow implementation — all major SaaS implementations at large enterprises.
Practitioner & Systems Framework
💻 ERP Architecture
The ASU 2018-15 prepaid asset is presented in 'other assets' (non-current) or 'prepaid and other current assets' depending on the remaining service period. Amortization begins when the module/service is ready for its intended use — applying the hosting arrangement's service period as the amortization period. For multi-phase implementations (SAP S/4HANA in phases over 3 years), each phase may begin amortizing when that phase goes live. The amortization is presented in the same income statement line as the hosting arrangement fees (usually cost of revenues or operating expenses).
⚠️ Audit Flags
ASU 2018-15 is still relatively new and many companies are applying it inconsistently. Auditors test: (1) Does the arrangement give the customer the right to call the software? (If yes — intangible asset, not ASU 2018-15). (2) Are implementation costs correctly staged (preliminary = expense, application development = capitalize, post-implementation = expense)? (3) Is the amortization period the service period of the hosting arrangement (not the implementation timeline)? Common error: amortizing over the implementation period (6-18 months) instead of the hosting service period (5-10 years).
📄 Required Documentation
Cloud service agreement (confirming no right to call underlying software), implementation project timeline with stage boundary documentation, capitalizable vs. non-capitalizable cost identification by project task, system integrator invoices mapped to stages, ASU 2018-15 prepaid asset register with amortization schedule, go-live dates by module/phase, and service period determination.
Professional Excel Template
Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.
Related Journal Entries
Technology (Hardware, Software & Platforms)
Hardware + Embedded Software Bundle — Distinct vs. Not Distinct Performance Obligation Analysis
Technology (Hardware, Software & Platforms)
Hardware + Future Software Updates + Services Bundle (Apple iPhone Revenue Model)
Technology (Hardware, Software & Platforms)