How to Account for Cloud Commitments Under ASC 842 and IFRS

To account for cloud commitments under ASC 842 and IFRS, first test whether the contract conveys control of an identified asset. If it does not, and standard public cloud commitments do not, the commitment is a service contract, not a lease. You expense usage as incurred, capitalize any prepayment as a prepaid asset and amortize it over the term, and disclose the unconditional minimum as a purchase obligation in the commitments note. Cloud commitments such as an enterprise discount program, a Savings Plan, or a committed use discount almost never meet the lease definition, so they stay off the balance sheet except for prepayments. Getting the classification right keeps the audit clean and the board's view of committed spend accurate.

Last updated: June 2026. Written by Fredrik Filipsson and reviewed by Morten Andersen, mapped to our See, Cut, Lock, Run method. This article explains the accounting model in general terms and is not a substitute for advice from your own auditors.

This article is part of our CFO guide to cloud cost management, the cluster pillar this piece links up to. Accounting treatment sits inside the Run step of our method, where committed spend has to be reported as cleanly as it is governed. For the sister question of how committed spend shows up in valuation work, see what cloud gross margin is and how to improve it.

Is a cloud commitment a lease under ASC 842?

Usually no. Under both ASC 842 (FASB) and IFRS 16 (IFRS Foundation), a contract is or contains a lease only if it conveys the right to control the use of an identified asset for a period in exchange for consideration. Two conditions must both hold: there is an identified asset, and you direct how and for what purpose that asset is used while obtaining substantially all the economic benefit from it. A typical cloud commitment fails the identified asset test, because the provider runs a shared, fungible pool of capacity and decides which physical hardware serves your workload. You bought a service and a discount, not the right to control a specific machine.

The narrow exception is genuinely dedicated infrastructure. If a contract gives you a physically distinct, identified server, rack, or capacity block that the provider cannot substitute and you direct its use, an embedded lease can exist and ASC 842 or IFRS 16 then applies to that component. This is rare in standard public cloud and common only in specialized colocation or sole tenant arrangements. When in doubt, document the substitution rights, because a substantive substitution right held by the provider defeats lease treatment.

If it is not a lease, what is a cloud commitment?

A cloud commitment that is not a lease is an executory purchase obligation under a service contract. You have promised to spend a minimum amount, or to pay for a reserved quantity, in exchange for a lower rate, but you receive and consume the service over time. Accounting follows the substance of the cash flows rather than putting a right of use asset on the books. The hosting arrangement itself is governed by ASC 350-40 in US GAAP, which treats most cloud computing arrangements as service contracts, and by IAS 38 and the related IFRS Interpretations Committee agenda decisions on SaaS in IFRS. The practical effect is the same: the running cost of the service is an operating expense in the period you use it.

How do you record prepaid reserved instances and upfront commitments?

Record an upfront or partial upfront payment as a prepaid asset and amortize it to expense over the commitment term. An all upfront reserved instance or committed use discount paid on day one is not an expense on day one; it is a prepayment for capacity you will consume over one or three years. Capitalize it and release it to expense on a systematic basis, typically straight line over the term, so the cost lands in the periods that benefit. A no upfront commitment with monthly billing needs no prepaid asset, because there is no prepayment; you simply expense each monthly charge. The distinction that drives the booking is when cash leaves, not the headline size of the commitment.

The classifications above reflect the structure of ASC 842, ASC 350-40, IFRS 16, and IAS 38 as we read them in June 2026. Standards and interpretations evolve, so confirm the current text and any recent agenda decisions on the FASB and IFRS Foundation sites and with your auditors before close.

How do you disclose cloud spend commitments?

Disclose unconditional minimum spend commitments in the commitments and contingencies note, with the amounts due by year. Even when nothing sits on the balance sheet, a multi year minimum is decision useful information for investors and lenders, and disclosure is required under ASC 440 in US GAAP and IAS 1 in IFRS. Show the total contractual minimum and the maturity profile, usually for each of the next five years and thereafter. This is also the figure the board cares about most, because it is the spend the company cannot walk away from. Tie the disclosed number back to the same commitment inventory you use operationally, so finance and FinOps report one set of numbers, a discipline we cover in how to build a cloud cost forecast model for the board.

What is the difference between ASC 842 and IFRS 16 here?

The standards diverge only in the rare case where a cloud arrangement does contain a lease. ASC 842 keeps the dual model: a lessee classifies an embedded lease as finance or operating, and both go on the balance sheet but expense differently. IFRS 16 uses a single lessee model in which almost all leases produce a right of use asset and a lease liability with front loaded interest and depreciation, with exemptions only for short term and low value leases. For the executory cloud commitments that make up the vast majority of committed spend, the two frameworks reach the same place: a service contract expensed as incurred, with prepayments amortized and minimums disclosed.

A five step method to get the bookings right

1. Test for an embedded lease. Apply the control of an identified asset test. If the provider can substitute the hardware, there is no lease. Expected result: almost every commitment exits as a service contract.
2. Classify the commitment. Sort each contract into lease, prepaid asset, or executory purchase obligation. Expected result: a labeled commitment inventory.
3. Record prepayments. Capitalize upfront and partial upfront amounts and amortize over the term. Expected result: expense matched to the periods of use.
4. Disclose the obligation. Put the unconditional minimum, by year, in the commitments note. Expected result: a maturity table that ties to the FinOps commitment register.
5. Reconcile and review. Reconcile booked amounts to provider invoices each period and confirm treatment with auditors. Expected result: a close with no commitment surprises.

Frequently asked questions

Is a cloud commitment a lease under ASC 842?

Usually no. A cloud commitment is a lease only if it gives you the right to control the use of an identified asset. Standard committed spend such as an enterprise discount program, Savings Plan, or committed use discount has no identified asset you control, so it is a service contract and purchase obligation, not a lease.

How do you account for prepaid reserved instances?

Record an all-upfront or partial-upfront reserved instance payment as a prepaid asset and amortize it to expense over the reservation term, typically one or three years, so the cost matches the period of use.

What is the difference between ASC 842 and IFRS 16 for cloud?

For a genuine embedded lease, IFRS 16 uses a single on-balance-sheet model for lessees, while ASC 842 keeps a finance versus operating lease distinction. For most cloud commitments neither standard applies, because the arrangement is a service contract disclosed as a commitment.

Where do cloud spend commitments appear in the financial statements?

Unconditional minimum spend commitments appear in the commitments and contingencies note, with amounts due by year, under ASC 440 in US GAAP or IAS 1 in IFRS. Prepayments sit on the balance sheet as prepaid assets until amortized.

The short version

Cloud commitments are service contracts, not leases, unless you control an identified, non substitutable asset. Expense usage as incurred, capitalize and amortize prepayments, disclose the unconditional minimum in the commitments note, and reconcile to invoices every period. When you want every commitment inventoried, classified, and reported the same way finance and FinOps see it, that is exactly what our Managed FinOps service delivers.