Software & SaaS Contracts Guide
How to Identify Embedded Software Leases & Analyze SaaS Contracts
Software and SaaS contracts present distinct accounting challenges separate from traditional embedded equipment leases. Under U.S. GAAP, software itself is generally outside ASC 842 scope — the standard explicitly excludes intangibles — and software arrangements that don’t transfer a license to the customer are typically treated as cloud computing arrangements (CCAs) that are service contracts. ASU 2018-15 governs the customer’s accounting for implementation costs in CCA service contracts, aligning treatment with internal-use software under ASC 350-40. However, SaaS and IT service contracts can contain embedded equipment leases when the arrangement includes dedicated, identified hardware that the customer controls. Identifying these embedded equipment leases under ASC 842 requires structured contract review. This guide covers the distinction between CCAs and software licenses, ASU 2018-15 implementation cost treatment, the criteria for identifying embedded equipment leases in technology contracts, U.S. GAAP versus IFRS differences, and the structured contract review process that supports proper accounting.
⚡ Key Takeaway
Software and SaaS contracts present distinct accounting challenges separate from traditional embedded equipment leases. Under U.S. GAAP, software itself is generally outside ASC 842 scope (ASC 842 excludes intangibles); software arrangements that don’t transfer a software license to the customer are typically treated as service contracts (cloud computing arrangements or “CCAs”). ASU 2018-15 governs the customer’s accounting for implementation costs incurred in a CCA that is a service contract — aligning the rules with internal-use software guidance under ASC 350-40, capitalizing certain application-development costs while expensing preliminary-project and post-implementation-stage costs. However, SaaS or software contracts can contain embedded equipment leases when the arrangement includes dedicated, identified hardware (servers, dedicated cloud capacity, on-premise appliances) that the customer controls. Identifying these embedded equipment leases under ASC 842 requires structured contract review. LeaseCommand supports software-and-services contract management through AI-Powered Document Extraction and structured analysis identifying embedded leases requiring ASC 842 treatment.
Software Excluded
ASC 842 excludes intangibles; software outside scope
ASU 2018-15
Governs CCA implementation cost accounting
Embedded Hardware
Dedicated hardware in software contracts may be a lease
Software and SaaS Are Different
The rise of cloud computing has fundamentally changed how organizations consume technology. Traditional on-premise software — licensed perpetually, installed on owned or leased hardware, maintained internally — has been largely replaced by Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS) arrangements where the vendor hosts the software and infrastructure and the customer accesses it remotely. The shift has changed the economics, the operational model, and the accounting treatment of technology contracts. Under U.S. GAAP, the accounting treatment of these arrangements depends critically on whether the customer obtains a software license. ASC 842 explicitly excludes intangible assets from its scope — software itself is not subject to ASC 842 lease accounting. Cloud computing arrangements that don’t transfer a software license to the customer are typically treated as service contracts: the customer is buying access to hosted software as a service rather than acquiring a software asset. Service contract treatment means the periodic fees are recognized as operating expense as the services are received, not as lease payments under ASC 842. ASU 2018-15 addressed an important question that arose with the shift: how should customers account for the implementation costs incurred to set up a cloud computing arrangement that is a service contract? Implementation costs can be substantial — configuration, data conversion, customization, integration with other systems, training. Before ASU 2018-15, customers in service-contract CCAs typically expensed implementation costs as incurred, while customers obtaining a software license (whether on-premise or hosted) capitalized them under ASC 350-40 internal-use software guidance. ASU 2018-15 aligned the two approaches: customers in CCA service contracts now apply ASC 350-40 to determine which implementation costs to capitalize. The other accounting question that frequently arises: does the cloud computing arrangement contain an embedded equipment lease? Many SaaS-style arrangements include hardware or infrastructure components — dedicated servers, on-premise appliances, dedicated cloud capacity, IoT sensors, or other equipment provided to the customer. When the arrangement gives the customer the right to control the use of identified equipment, an embedded lease may exist under ASC 842 even though the software itself is a service contract.Software vs Service
The accounting depends on whether the customer obtains a software license (potentially under ASC 350-40) or accesses hosted software as a service (CCA under ASU 2018-15).Implementation Costs
ASU 2018-15 governs capitalization of implementation costs for CCA service contracts — aligning treatment with internal-use software under ASC 350-40.Embedded Hardware
SaaS arrangements that include dedicated, identified hardware may contain embedded equipment leases requiring ASC 842 treatment.Frequent Audit Area
Technology contracts are increasingly scrutinized for embedded leases and proper accounting classification.Cloud Computing Arrangement vs. Software License
-
1
Software License Transfer
A hosting arrangement transfers a software license if the customer has the contractual right to take possession of the software during the hosting period without significant penalty and it is feasible to either run the software on the customer’s hardware or contract with another party to host the software. When a license is transferred, the customer accounts for the software as internal-use software under ASC 350-40. -
2
Service Contract (No License)
When no software license transfers, the arrangement is a CCA service contract: the customer accesses hosted software as a service. Periodic fees are recognized as operating expense as services are received, similar to other service contracts. -
3
ASU 2018-15 Implementation Costs
For CCA service contracts, ASU 2018-15 applies ASC 350-40 to implementation costs — capitalizing application-development stage costs (configuration, customization, integration, testing), while expensing preliminary-project stage costs (planning, vendor selection) and post-implementation-operation stage costs (training, data conversion when not in application-development stage). -
4
Amortization Period
Capitalized implementation costs are amortized over the term of the hosting arrangement, including reasonably certain renewal periods. The amortization period considers vendor-controlled extension options. -
5
Presentation
ASU 2018-15 specifies presentation: capitalized implementation costs are presented in the same balance sheet line as a prepayment for the associated hosting fees; amortization is presented in the same income statement line as the hosting fees; cash flows are classified the same as the hosting arrangement fees. -
6
Disclosure
Required disclosures include the nature of the hosting arrangement, information about capitalized implementation costs analogous to ASC 360-10 property, plant, and equipment disclosures, and amounts amortized during the period.
Identifying Embedded Equipment Leases
Dedicated Hardware
Look for references to dedicated, identified, or specifically-named hardware in the contract — dedicated servers, on-premise appliances, IoT devices, network equipment, specialized terminals. Generic references to provider infrastructure typically do not create embedded leases.Economic Benefits
Assess whether the customer obtains substantially all economic benefits from use of the identified equipment. If the equipment is dedicated to the customer’s data and operations, this is typically met.Direction of Use
Determine whether the customer directs how and for what purpose the equipment is used. Customer control over configuration, scheduling, and operational decisions supports embedded lease classification.Substitution Rights
Consider whether the supplier has substantive substitution rights. Rights that are practical to exercise and economically beneficial to the supplier reduce the likelihood of an embedded lease.Common Examples
IT outsourcing with dedicated infrastructure, managed services with on-premise appliances, IoT services with dedicated devices, telecommunications with dedicated equipment, and similar arrangements frequently contain embedded leases.Allocation of Consideration
When an embedded lease exists, contract consideration must be allocated between the lease component (subject to ASC 842) and the nonlease/service components (subject to other guidance) based on standalone selling prices, unless the practical expedient to combine is elected.U.S. GAAP vs. IFRS Comparison
U.S. GAAP (ASC 842)
ASC 842 excludes intangible assets including software from its scope. Software arrangements are accounted for under ASC 350-40 (internal-use software, including ASU 2018-15) or as service contracts. Only physical equipment in software arrangements may produce embedded leases.IFRS 16
IFRS 16 does not categorically exclude intangibles — some intangible-asset arrangements can be leases under IFRS 16. The treatment of software under IFRS depends on specific facts and may differ from U.S. GAAP treatment of the same arrangement.Dual Reporters
Organizations preparing both U.S. GAAP and IFRS financial statements may need separate analyses of software arrangements producing different balance sheet outcomes between the two frameworks.Configuration & Customization
IFRIC agenda decisions on configuration and customization of SaaS in IFRS environments produced specific guidance that informs treatment of related costs under IFRS — with some convergence and some divergence from ASU 2018-15.Structured Contract Review Process
Software License Assessment
For each technology contract, determine whether a software license transfers to the customer. The assessment looks at the customer’s contractual right to take possession of the software and feasibility of running it on alternative infrastructure.Hardware Component Screening
Identify whether the contract includes dedicated hardware components. References to specific equipment, dedicated capacity, on-premise installations, or named devices warrant deeper analysis.Implementation Cost Analysis
For CCA service contracts, analyze implementation activities by stage (preliminary-project, application-development, post-implementation-operation) and apply ASU 2018-15 capitalization rules.Documentation
Document the contract analysis: software license vs service determination, embedded lease conclusion (if any), implementation cost categorization, and the basis for each conclusion.Modification Tracking
When technology contracts are modified or extended, the analysis should be revisited — modifications may change embedded lease conclusions, implementation cost capitalization periods, or other accounting treatments.Cross-Functional Coordination
Technology contracts often involve IT, procurement, finance, and accounting. Cross-functional coordination ensures consistent treatment across departments and proper accounting for material contracts.How LeaseCommand Helps
LeaseCommand supports software-and-services contract management through AI-Powered Document Extraction and structured analysis identifying embedded leases requiring ASC 842 treatment.AI-Powered Document Extraction
Extract structured terms from technology contracts including dedicated hardware references, lease components, service terms, and implementation provisions.Embedded Lease Identification
Structured analysis support for identifying embedded equipment leases in SaaS, managed services, and IT contracts.ASC 842 Compliance
For identified embedded leases, automated ROU asset and lease liability calculations, classification, and journal entries.Contract Management
Centralized management of technology contracts alongside real estate and equipment leases, supporting cross-functional review.Critical Date Tracking
Renewal dates, modification deadlines, and other technology contract milestones tracked with notifications.ERP Integration
Integration with Oracle NetSuite, Sage Intacct, Restaurant365, and QuickBooks Online for journal entry sync of identified embedded leases.Analyze Technology Contracts Systematically
LeaseCommand supports identification of embedded leases in software, SaaS, and IT service contracts through structured analysis and AI-powered extraction.Frequently Asked Questions
Software itself is generally not a lease under ASC 842. ASC 842 explicitly excludes intangible assets from its scope, and software is generally an intangible asset. Software arrangements are accounted for under different guidance depending on their structure. If the arrangement transfers a software license to the customer (the customer has the contractual right to take possession of the software and it is feasible to run the software on alternative infrastructure), the customer accounts for the software as internal-use software under ASC 350-40. If the arrangement is a cloud computing arrangement that is a service contract (no software license transfers — the customer accesses hosted software as a service), periodic fees are recognized as operating expense as services are received, and implementation costs are accounted for under ASU 2018-15. Note that this is a U.S. GAAP rule — IFRS 16 does not categorically exclude intangibles from its scope, and treatment of software under IFRS may differ.
ASU 2018-15 (Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract), issued by FASB in August 2018, governs how a customer accounts for the implementation costs incurred in a cloud computing arrangement (CCA) that is a service contract. The ASU aligns the customer’s treatment with the rules for capitalizing implementation costs to develop or obtain internal-use software under ASC 350-40. Under ASU 2018-15, costs incurred during the preliminary-project stage (planning, vendor selection) and post-implementation-operation stage (training, ongoing operations) are generally expensed as incurred. Costs incurred during the application-development stage — configuration, customization, integration with other systems, testing — are generally capitalized. Capitalized implementation costs are amortized over the term of the hosting arrangement (including reasonably certain renewal periods). The ASU specifies that capitalized costs are presented in the same balance sheet line as a prepayment for the hosting fees, with amortization in the same income statement line as the hosting fees.
A SaaS or software arrangement can contain an embedded equipment lease when the arrangement gives the customer the right to control the use of identified hardware. The ASC 842 framework asks whether: (1) the contract conveys the right to use an identified asset — dedicated, specifically-identified hardware (servers, on-premise appliances, IoT devices, network equipment) rather than generic provider infrastructure; (2) the customer obtains substantially all economic benefits from use of the asset — typically met when the equipment is dedicated to the customer’s data and operations; (3) the customer directs how and for what purpose the asset is used — customer control over configuration, scheduling, and operational decisions; and (4) the supplier does not have substantive substitution rights. When all criteria are met, an embedded equipment lease exists and must be accounted for under ASC 842 with appropriate allocation of contract consideration between the lease and nonlease/service components. Common examples include IT outsourcing with dedicated infrastructure, managed services with on-premise appliances, and IoT services with dedicated devices.
U.S. GAAP and IFRS treat software arrangements differently in several respects. Under U.S. GAAP, ASC 842 explicitly excludes intangible assets including software from its scope; software is accounted for under ASC 350-40 (internal-use software) or as service contracts (CCAs). Under IFRS, IFRS 16 does not categorically exclude intangibles, and some software arrangements can be leases under IFRS 16. The result is that the same arrangement may produce balance sheet recognition under IFRS but not under U.S. GAAP. For implementation costs in service-contract cloud arrangements, ASU 2018-15 in U.S. GAAP aligns treatment with internal-use software guidance. IFRS treatment is governed by IFRIC agenda decisions on configuration and customization of SaaS, with some convergence and some divergence from U.S. GAAP. Organizations preparing financial statements under both frameworks may need separate analyses of material software arrangements, with documented reconciliation of any differences. The complexity of dual reporting in technology-intensive businesses is significant and warrants careful contract analysis.
Several contract terms suggest the possibility of an embedded lease and warrant deeper analysis. Direct references to specific equipment by name, model, or serial number indicate identified assets that may meet the ASC 842 lease definition. Provisions for dedicated capacity, dedicated infrastructure, or dedicated equipment beyond generic shared resources also suggest identified assets. On-premise installations of equipment at the customer’s facility are a common source of embedded leases. References to the customer’s right to direct operations of equipment — configuration choices, scheduling, operational decisions — support the direction-of-use criterion. Limited supplier substitution rights, particularly where substitution would not be practical or economically beneficial to the supplier, weaken the supplier’s substitution defense. Conversely, references to shared infrastructure, fungible cloud resources, generic provider technology, and unrestricted substitution rights tend to indicate service rather than embedded lease. Each contract should be analyzed on its specific facts; the contract terms are signals, not definitive answers.
LeaseCommand supports software-and-services contract management through AI-Powered Document Extraction and structured analysis. AI-powered extraction abstracts structured terms from technology contracts — dedicated hardware references, lease components, service terms, implementation provisions, renewal options, and other relevant terms. Embedded lease identification provides structured workflow analyzing technology contracts for embedded equipment leases requiring ASC 842 treatment, applying the right-to-control criteria. For identified embedded leases, automated ROU asset and lease liability calculations, classification, and journal entries follow standard ASC 842 treatment. Centralized contract management handles technology contracts alongside real estate and equipment leases, supporting cross-functional review by IT, procurement, finance, and accounting. Critical date tracking flags renewal dates, modification deadlines, and other technology contract milestones with notifications. ERP integration with Oracle NetSuite, Sage Intacct, Restaurant365, and QuickBooks Online supports journal entry sync of identified embedded leases. Software-specific accounting questions (ASC 350-40 internal-use software treatment, ASU 2018-15 implementation cost capitalization) should be addressed with accounting advisers; LeaseCommand handles the lease accounting components.
⚠️
Legal & Accounting Disclaimer
The information on this page is provided for general informational purposes only and does not constitute legal, accounting, tax, or financial reporting advice. ASC 842, IFRS 16, GASB 87, and related lease accounting standards are complex and require interpretation specific to your organization’s facts and circumstances. Always consult qualified accounting professionals, your external auditors, and legal counsel before making decisions about lease classification, discount rate selection, disclosure, or financial reporting. LeaseCommand is a software platform — not an accounting firm or law firm. All figures, examples, and interpretations referenced are illustrative only.
