The two-criterion license vs. service contract test, what cloud setup costs qualify for capitalization, how amortization reduces EBITDA, operating cash flow classification, and the IFRIC 2021 gap.
Under ASC 350-40 (as amended by ASU 2018-15), eligible implementation costs of a cloud hosting service contract are capitalized in the same balance sheet line as hosting prepayments, amortized over the hosting term in the same income statement line as the SaaS fees (reducing EBITDA), and reported as operating cash outflows. On Kestrelway's $420,000 cloud ERP rollout, US GAAP capitalizes $420,000 whereas IFRS / IFRIC 2021 expenses $330,000 immediately.
Worked in full in The Software Costs Accounting Handbook by Julian R. Sterling, with every figure reproduced in live Excel workbooks.Get the DRM-free PDF, $19.99 →
Before capitalizing a single dollar of cloud ERP, CRM, or billing setup work, the controller must decide whether the hosting arrangement includes a software license or is purely a service contract. As read in November 2026 under ASC 350-40-15-4A, a cloud hosting arrangement conveys a software license only when both of the following conditions are satisfied: first, the customer has the contractual right to take possession of the software at any time during the hosting period without significant penalty; second, it is feasible for the customer to run the software on its own hardware or contract with an unrelated third party to host it.
If both criteria are met, the customer accounts for the license element as an acquired internal-use software intangible asset. If either criterion fails (the standard outcome for multi-tenant SaaS subscriptions), the arrangement is a service contract. Under ASU 2018-15 (codified inside ASC 350-40), the customer applies internal-use software capitalization criteria to determine which implementation, configuration, and integration costs are capitalized versus expensed, while following specialized presentation rules across all three financial statements.
Capitalizable cloud implementation costs mirror internal-use software direct costs: third-party systems integrator fees for configuration, interface coding, and testing, plus internal IT and engineering payroll (including benefits and allocable stock-based compensation) for hours spent directly on coding, configuring, and testing the cloud setup. Under ASU 2025-06 (effective for annual periods beginning after December 15, 2027, with early adoption permitted), entities evaluate when capitalization starts using the unified management-commitment and probable-to-complete threshold rather than sequential project stages.
Four categories remain strictly expensed as incurred: preliminary vendor evaluation and RFP work, manual legacy data cleansing and reconciliation, end-user and administrator training, and post-go-live routine support or minor configuration adjustments. Mixing training or data cleansing inside an omnibus systems-integrator invoice is one of the most frequent audit findings; controllers should require vendors to itemize configuration, training, and data migration hours on every statement of work and invoice.
In The Software Costs Accounting Handbook, Kestrelway Systems signs a three-year non-cancelable SaaS ERP contract with Draycott Cloud Services at $240,000 per year ($20,000 per month), plus one two-year renewal option that management concludes is reasonably certain of exercise because switching ERPs after three years would cause severe operational disruption. The hosting amortization term is therefore 5 years (60 months). Because Kestrelway cannot take possession of Draycott's multi-tenant code, the arrangement is a service contract.
Ahead of the July 1, 2026 go-live, Kestrelway incurs $55,000 for vendor selection, $150,000 of internal configuration payroll (including $8,000 of SBC), $270,000 of third-party integrator fees, $68,000 of manual data cleansing, $82,000 of user training, and $40,000 of H2 post-go-live support (total expensed implementation and support = $245,000). Only the $150,000 internal configuration payroll and $270,000 integrator fees qualify, creating a $420,000 capitalized cloud implementation asset.
| Draycott Cloud ERP Outlay | Amount | Accounting Treatment | Cash Flow Section |
|---|---|---|---|
| Preliminary vendor selection & scoping | $55,000 | Expensed as incurred | Operating outflow |
| Internal config & API engineering payroll | $150,000 | Capitalized (Prepaid/Other) | Operating outflow (excl. SBC) |
| Third-party ERP systems integrator | $270,000 | Capitalized (Prepaid/Other) | Operating outflow |
| Manual data cleansing & end-user training | $68,000 + $82,000 | Expensed as incurred | Operating outflow |
| Total capitalized cloud implementation asset | $420,000 | Amortized over 60 months | $412,000 cash outflow |
Controllers who treat cloud implementation costs like owned software make three immediate presentation errors. First, on the balance sheet, capitalized hosting implementation costs do not go into Property and Equipment or Intangible Assets. They belong in the same balance sheet line item as a prepayment for the hosting service (Prepaid Expenses for the current portion and Other Non-Current Assets for the long-term portion). At December 31, 2026, after six months of amortization ($7,000 per month = $42,000), Kestrelway's $378,000 ending balance splits into $84,000 current and $294,000 non-current.
Second, on the income statement, amortization of capitalized cloud implementation costs must be recorded in the same operating expense line as the underlying SaaS subscription fees, not inside Depreciation and Amortization. Kestrelway records its H2 subscription ($120,000) plus implementation amortization ($42,000) for $162,000 total in General and Administrative expense. Because that $42,000 sits inside operating expense rather than D&A, it reduces EBITDA directly.
Third, on the statement of cash flows, cash paid for capitalized cloud implementation costs follows the classification of the hosting fees: operating cash outflows, not investing cash outflows. Kestrelway's $412,000 cash outlay (excluding $8,000 of non-cash SBC) reduces operating cash flow in 2026 even though the asset sits on the balance sheet.
In the free Software Cost Capitalization Model, the Cloud Implementation tab illustrates a $300,000 SaaS rollout amortized over 60 months ($60,000 per year), stacked directly onto a $180,000 annual subscription fee so FP&A sees the true recurring operating expense load.
Dual US GAAP and IFRS reporters face a stark divergence here. Under the IFRS Interpretations Committee's March 2019 and April 2021 agenda decisions (as read in November 2026), configuration and customization performed inside a vendor's cloud environment generally do not create an intangible asset controlled by the customer under IAS 38 and must be expensed when the service is received. On Kestrelway's Draycott ERP rollout, only $90,000 of custom API bridging code hosted on Kestrelway's own servers passes IAS 38's control test, forcing the remaining $330,000 straight to IFRS profit or loss.
| Draycott ERP Metric | US GAAP (ASC 350-40) | IFRS (IAS 38 / IFRIC) | Difference |
|---|---|---|---|
| Capitalized implementation asset at go-live | $420,000 | $90,000 | $330,000 |
| H2 2026 amortization (6 months) | $42,000 | $9,000 | $33,000 lower under IFRS |
| Balance sheet line item | Prepaid / Other Assets | Intangible Asset (IAS 38) | Different line item |
| Cash flow classification | Operating activities | Investing (if controlled) | Opposite cash section |
If a cloud arrangement is terminated early or loses substantive service potential, the unamortized implementation asset is tested for impairment and abandonment under ASC 360-10; see our ASC 360 impairment test example for the recoverability and write-off mechanics.
The trap: Booking cloud ERP implementation amortization into D&A and classifying vendor setup payments as investing CapEx. Both inflate reported EBITDA and operating cash flow, triggering restatement risk during external audit.
In the same line item as a prepayment for the hosting arrangement (typically Prepaid Expenses for the next 12 months and Other Non-Current Assets for the remainder), not in PP&E or Intangible Assets.
Yes. Under ASC 350-40 / ASU 2018-15, amortization of capitalized cloud implementation costs must be presented in the same operating expense line as the SaaS subscription fees, not in D&A.
Operating cash flows. Because SaaS hosting fees are operating outflows, cash paid for capitalized implementation costs of a hosting service contract is also classified in operating activities.
US GAAP (ASC 350-40) permits capitalizing eligible configuration and customization costs of a SaaS service contract and amortizing them over the hosting term. Under IFRS (IFRIC April 2021), configuration of vendor-hosted software is typically expensed as received unless it creates a separate intangible asset controlled by the customer under IAS 38.
This guide is one chapter arc of The Software Costs Accounting Handbook. The book tracks one US GAAP company through Legacy ASC 350-40 vs. ASU 2025-06, agile sprint evidence, stock-based compensation, abandonment write-offs, cloud ERP implementation vs. IFRIC 2021, ASC 985-20 NRV testing, EBITDA covenants, transition methods and deferred taxes.
Paperback PDF edition, $19.99 Book page and companion workbooks
Free download: Software Cost Capitalization Model (Excel).
Illustrative figures computed by the book's model; every company, project and dollar figure is fictional. Rules checked as read in November 2026; education only, not accounting, audit or tax advice.