ASC 350-40 Hosting Arrangement: 2026 Practitioner Walkthrough

If your company runs on SaaS, PaaS, or IaaS, you are almost certainly accounting for cloud computing arrangements (CCAs) under ASC 350-40. Getting it wrong is expensive: SEC comment letters, restatements, and covenant breaches from balance sheet misclassification are all live risks. This guide walks through every decision point, in sequence, so a controller or technical accounting manager can apply the standard correctly and defend it under audit.

Key takeaway: ASC 350-40 hosting arrangement accounting requires four sequential decisions: (1) does the contract convey a software license or is it a pure service contract? (2) which implementation costs fall into which phase? (3) where does the capitalized asset sit on the balance sheet? (4) how long do you amortize it? Each decision has a specific rule and a common mistake attached to it.

What Is ASC 350-40 and Why Does It Govern Hosting Arrangements?

ASC 350-40 is the FASB subtopic that governs a customer's accounting for implementation costs incurred in a cloud computing arrangement that is a service contract. The standard has two layers, both of which are still relevant today.

ASU 2015-05 established the original framework: if a CCA includes a software license, the customer accounts for it under the internal-use software model. If it does not, the entire arrangement is a service contract and fees are expensed as incurred. That left a gap: what about the implementation costs in a pure service contract?

ASU 2018-15 closed that gap. It extended the three-phase internal-use software capitalization model to implementation costs in service-contract CCAs, eliminating the prior asymmetry where identical implementation work was capitalized if a license existed but expensed if it did not. As the FASB stated in the ASU's summary: "The amendments in this Update align the requirements for capitalizing implementation costs incurred in a hosting arrangement that is a service contract with the requirements for capitalizing implementation costs incurred to develop or obtain internal-use software."

ASU 2018-15 was effective for public business entities for fiscal years beginning after December 15, 2019 (calendar-year public companies adopted January 1, 2020) and for private entities for annual periods beginning after December 15, 2020. The standard is fully in effect for all entities. For a broader orientation to ASC 350-40 and what ASU 2025-06 changed for internal-use software more broadly, see our ASC 350-40 explained guide.

Step 1: Does the Hosting Arrangement Contain a Software License?

This is the most consequential question in the entire analysis, and most modern SaaS contracts fail both tests required to answer yes.

Under ASC 350-40-15-4A, a CCA contains a software license only if both of the following conditions are met:

1. The customer has the contractual right to take possession of the software at any time during the hosting period without significant penalty.
2. It is feasible for the customer to either run the software on its own hardware or contract with a third party unrelated to the vendor to host the software.

Both conditions must be satisfied. If either fails, the arrangement is a pure service contract.

Why most SaaS contracts fail this test. Standard SaaS agreements give the customer access to the vendor's hosted environment, not possession of the underlying code. There is no right to download and self-host. Even where a vendor offers an on-premise version, the SaaS contract itself typically does not grant that right. PaaS and IaaS arrangements are similarly structured. The practical result: the vast majority of cloud contracts are service contracts under ASC 350-40, and the license question is answered quickly.

Where it gets harder. Some enterprise software vendors offer both hosted and on-premise versions of the same product. If the contract is silent on whether a license is conveyed, you need to look at the substance of the arrangement. PwC's Viewpoint guidance notes that a pattern of selling software to third parties that was originally developed for internal use is a factor in determining whether an arrangement conveys a license. Document your conclusion and the evidence supporting it.

The "significant penalty" assessment. Per KPMG's Software Costs Handbook, the "no significant penalty" criterion means the customer can take possession without incurring a penalty significant relative to the total cost of the arrangement. Contractual termination fees, data migration costs, and business disruption costs are all relevant factors. This is a judgment call that needs to be documented.

IaaS and ASC 842 interaction. For IaaS arrangements involving dedicated servers or specific infrastructure, a separate question arises: is the arrangement a lease under ASC 842? If the customer controls a specific identified asset, ASC 842 applies instead of ASC 350-40. This is a real source of scope confusion. Our ASC 842 common mistakes guide covers the identified-asset analysis in detail.

Decision Tree: License or Service Contract?

Step 2: Map Implementation Costs to the Three Phases

Once you confirm a service contract, the next job is phase determination. This is where most errors occur and where SEC staff focus their comment letters.

ASC 350-40 uses the same three-phase model as the internal-use software guidance:

What triggers the application development stage. Capitalization begins when management with the relevant authority authorizes and commits to funding the project AND it is probable the project will be completed and the software will be used as intended. Both conditions must be present. The moment management approves and probability is established, you start capitalizing eligible costs.

What is capitalizable in the application development stage:

• External direct costs of materials and services consumed in developing or obtaining the software
• Payroll and payroll-related costs for employees directly associated with and devoting time to the project
• Interest costs incurred during development

What is never capitalizable, even in the application development stage:

• Overhead and general and administrative costs
• Training costs
• Data migration costs (unless directly related to the software configuration itself)

The agile methodology problem. Traditional phase determination assumes a linear, waterfall-style development process. Agile is iterative: sprints cycle through design, build, and test continuously, making it hard to say "we are in the application development stage" at any given moment. EY's Financial Reporting Developments guide advises that entities using agile should document their phase determination methodology carefully and apply it consistently. The practical approach: track costs by sprint and by activity type, not just by calendar date. A sprint that includes both requirements gathering (preliminary) and configuration (application development) requires cost allocation between phases.

ASU 2025-06 note. The FASB issued ASU 2025-06 in September 2025, which modernized the internal-use software guidance in ASC 350-40 to better accommodate nonlinear development methods. While ASU 2025-06 primarily addresses internal-use software development, its changes to the capitalization threshold and phase model are relevant context for CCA implementation cost accounting as well. See our ASC 350-40 practitioner walkthrough for a full treatment of those changes.

Audit red flag: Costs that span multiple phases are common in large ERP or CRM cloud migrations. If your time-tracking system does not capture activity type at a granular level, you cannot support your phase allocation. Auditors will ask for the evidence.

Step 3: Balance Sheet Classification (Not an Intangible)

Capitalized CCA implementation costs in a service contract are presented as a prepaid asset or other asset on the balance sheet. They are NOT intangible assets. This is one of the most common misclassifications in practice.

This distinction matters for several reasons:

• Intangible assets appear in a different line on the balance sheet and are subject to different impairment testing
• Debt covenants that reference intangible assets or total assets may be affected by the classification
• Financial ratios used by analysts and lenders (asset turnover, return on assets) will differ depending on where the asset sits
• SEC staff have specifically challenged companies that classified capitalized CCA costs as intangibles

The rule is clear in ASU 2018-15: the capitalized implementation costs are presented in the same balance sheet line as a prepaid for the associated hosting arrangement fees. In practice, this is typically "Prepaid expenses and other current assets" for the current portion and "Other noncurrent assets" for the long-term portion.

Abandonment. If a CCA implementation project is cancelled or significantly scaled back, any previously capitalized implementation costs must be written off in the period of abandonment. This is an area of audit focus for large ERP or CRM migrations that are cancelled mid-stream. The write-off goes to the same income statement line as the amortization of the related hosting costs.

Step 4: Determine the Amortization Period

The amortization period equals the term of the hosting arrangement: the noncancellable period plus any optional renewal periods that are reasonably certain to be exercised by the customer or for which exercise is controlled by the vendor.

This concept is analogous to the lease term under ASC 842, though ASC 350-40 does not explicitly cross-reference ASC 842. The practical analysis is similar:

• If the customer has a unilateral renewal option and there are significant economic incentives to renew (e.g., the software is deeply integrated into operations, switching costs are high, or the contract price is below market), the renewal period should be included in the amortization period.
• If the vendor controls the renewal (e.g., the vendor can require the customer to renew), that period is also included.
• Amortization is on a straight-line basis over the determined term.

Worked example. A company signs a three-year SaaS contract with two one-year renewal options. The software is a core ERP system with high switching costs. At contract inception, management concludes it is reasonably certain to exercise both renewal options. The amortization period is five years (three noncancellable plus two renewal years). If the company later decides not to renew, it accelerates the remaining amortization in the period that decision is made.

Income statement presentation. The amortization of capitalized implementation costs must appear in the same income statement line item as the fees for the associated hosting arrangement. If hosting fees are in cost of revenue, amortization goes there too. If they are in general and administrative expense, amortization follows. This is not optional: the standard requires line-item alignment.

Step 5: Cash Flow Classification

Capitalized CCA implementation costs are classified in the same section of the statement of cash flows as the fees for the hosting arrangement, which is typically operating activities. This differs from capitalized internal-use software, where cash outflows are typically classified as investing activities.

This is a common error, particularly for companies that previously capitalized on-premise software as investing cash flows and apply the same logic to cloud implementation costs. The rule is explicit in ASU 2018-15: follow the hosting fees. Since hosting fees are operating cash outflows, the implementation costs follow.

The practical impact: a company migrating from on-premise to cloud may see a shift in its cash flow statement presentation, with previously investing-classified software costs moving to operating activities. This can affect free cash flow metrics and should be disclosed and explained to investors.

Step 6: Disclosure Requirements Under ASC 350-40-50

ASC 350-40-50 requires specific disclosures for hosting arrangements that are service contracts. SEC staff have scrutinized these disclosures in comment letters, and vague or incomplete footnotes draw follow-up questions.

Required disclosures include:

• The nature of the hosting arrangements that are service contracts
• The amount of capitalized implementation costs and accumulated amortization
• The amortization expense for the period
• The line items in the financial statements where these amounts are presented (both balance sheet and income statement)

What SEC staff actually challenge. Based on SEC comment letter activity referencing ASC 350-40, staff have focused on four areas:

1. Whether the scoping determination (license vs. service contract) was properly made and documented
2. Whether costs were correctly allocated to phases, with specific questions about what was expensed vs. capitalized
3. Whether the balance sheet classification (prepaid vs. intangible) was correct
4. Whether disclosures were sufficient to allow a reader to understand the nature and amount of CCA costs

Technology, healthcare, and financial services companies have been most frequently targeted. If your CCA implementation costs are material, expect the question.

Disclosure best practice. Name the specific systems (e.g., "cloud-based ERP implementation"), state the capitalized amount and accumulated amortization, identify the balance sheet line, and explain the amortization period and the basis for any renewal period inclusion. A one-sentence footnote will not satisfy SEC staff.

Common Mistakes That Cause Restatements

These are the errors that show up in restatements and SEC comment letters:

• Classifying capitalized costs as intangibles. The standard is clear: prepaid or other asset, not intangible. Check your chart of accounts.
• Expensing all implementation costs in a service contract. Pre-ASU 2018-15 behavior that persists in some companies. Application development stage costs that meet the criteria are capitalizable.
• Capitalizing training and data migration costs. These are expensed even in the application development stage unless the data migration is directly related to the software configuration.
• Using the wrong amortization period. Ignoring reasonably certain renewal options understates the amortization period and overstates annual amortization expense.
• Classifying cash flows as investing. CCA implementation cash flows follow the hosting fees into operating activities.
• Inadequate phase documentation. Without contemporaneous records of when the application development stage began and ended, the capitalized amount cannot be defended under audit.
• Missing the abandonment write-off. When a project is cancelled, the write-off is immediate. Continuing to carry the asset is an error.

For a comparison of how ASC 350-40 interacts with ASC 985-20 for companies that both use and sell cloud software, see our ASC 350-40 vs ASC 985-20 guide.

Internal Controls and Documentation

The standard requires judgment at every step. Without controls, that judgment will be applied inconsistently across projects and periods. At minimum, a CCA accounting policy should establish:

• A scoping checklist for new cloud contracts (license vs. service contract determination, with sign-off)
• A project phase log that tracks when the preliminary, application development, and post-implementation stages begin and end, with management authorization documented
• A time-tracking mechanism that captures employee time by project and by activity type (not just by project)
• A capitalized cost register that ties to the balance sheet prepaid and tracks accumulated amortization
• A renewal option assessment at contract inception and at each reporting date
• An abandonment review as part of the quarterly close

For companies on agile development methodologies, the phase log needs to operate at the sprint level, not the project level.

What the FASB's Software Modernization Project Means for Hosting Arrangements

The current ASC 350-40 CCA model may change materially. The FASB's software cost modernization project (2022-005) has been actively deliberated through 2025 and 2026, and ASU 2025-06 was issued in September 2025 as a targeted improvement to the internal-use software guidance. The broader project aims to collapse the distinction between internal-use and external-use software into a unified framework and to address cloud computing costs more holistically.

As of September 2026, preparers should:

• Monitor the FASB project page for further proposed ASUs affecting CCA accounting
• Assess whether existing accounting policies will need to be updated if the phase-based model changes
• Consider whether transition elections (retrospective vs. prospective) will affect comparative periods

The Deloitte Heads Up on ASU 2025-06 provides useful context on how the targeted improvements interact with the existing CCA guidance.

FAQ

What is ASC 350-40 in plain terms? ASC 350-40 is the FASB standard that tells customers how to account for costs associated with cloud computing arrangements, including which implementation costs can be capitalized and how to present them on the financial statements.

When did ASC 350-40's hosting arrangement rules take effect? The key amendment, ASU 2018-15, was effective for public companies for fiscal years beginning after December 15, 2019 (January 1, 2020 for calendar-year companies) and for private companies for annual periods beginning after December 15, 2020.

How long do you amortize CCA implementation costs? Over the term of the hosting arrangement: the noncancellable period plus any renewal periods reasonably certain to be exercised or controlled by the vendor. Amortization is straight-line.

Is a SaaS arrangement a software license or a service contract under ASC 350-40? Almost always a service contract. Standard SaaS agreements do not give the customer the right to take possession of the software without significant penalty, and it is not feasible to self-host. Both conditions under ASC 350-40-15-4A must be met for a license to exist.

Where do capitalized CCA implementation costs go on the balance sheet? As a prepaid asset or other asset, not as an intangible asset. This is a common misclassification that SEC staff have challenged in comment letters.

How are CCA implementation cash flows classified on the cash flow statement? In the same section as the hosting fees, typically operating activities. This differs from capitalized internal-use software, which is usually classified as investing cash flows.