Revenue Recognition for GPU and Compute Capacity Contracts

Revenue from GPU and compute capacity contracts is recognized under ASC 606 when the provider delivers a service – typically a stand-ready obligation recognized over time, with usage fees recognized as usage occurs if specific allocation criteria are met. If the contract gives the customer control of identified hardware, part of it is an embedded lease under ASC 842. Minimum commitments, resetting periods, and tiered rates decide whether revenue simply follows the invoice or has to be estimated and spread. IFRS 15 and IFRS 16 follow a comparable approach, with differences that matter for dual reporters.

For the broader industry context, see our page on AI & Data Infrastructure.

Step 1: Service or Lease?

The first question is whether the contract contains a lease. Under ASC 842, that requires an identified asset and the customer's right to control its use.

• Identified asset. A GPU cluster specified by the contract – or implicitly, because the provider has only one setup that meets the customer's requirements – can be an identified asset. A substantive substitution right defeats this, but only if the provider has the practical ability to substitute throughout the term and would benefit economically from doing so. Substitution for repairs or technical upgrades does not count.

• Capacity portions. A share of a shared pool that is not physically distinct is not an identified asset unless it represents substantially all of the asset's capacity. A physically distinct portion can be.

• Right to direct use. The customer must obtain substantially all economic benefits and direct how and for what purpose the asset is used. The provider operating and maintaining the hardware does not, by itself, prevent this.

In practice, on-demand access to a shared, provider-managed pool points to a service under ASC 606. Dedicated clusters for exclusive use point toward an embedded lease. The label on the contract does not decide it.

Step 2: What Is the Performance Obligation?

For the service portion, the key distinction is between a stand-ready obligation and a specified volume:

• Stand-ready obligation. If no volume is specified or a cap is not substantive, the provider stands ready over the entire term. This is generally a series of distinct service periods, measured with a time-based method.

• Specified volume. Rollover rights for unused capacity, service that ends when the volume is consumed, or a new purchase decision for additional volume indicate a promise of specified quantities. Revenue then follows the services as they are provided, and breakage may be considered if the customer is not expected to use the full volume.

Step 3: Usage Fees and Minimum Commitments

Most compute contracts mix fixed and variable consideration: a reserved-capacity fee, usage charges, or a minimum spend with overage. Fixed consideration in a stand-ready obligation is recognized ratably. For variable fees, ASC 606-10-32-40 allows allocation to the period in which the usage occurs if the fee relates specifically to that period and the allocation objective is met.

How the minimum is structured decides the outcome:

• Fixed rate per GPU-hour, no minimum: Usage revenue recognized as usage occurs

• Monthly minimum that resets, fixed-rate overage: Allocation exception typically applies

• Annual minimum that does not reset monthly: Variable consideration estimated, constrained, and recognized ratably

• Shortfalls carried into later periods: Exception may not apply

• Rates that step up or down with volume: Careful analysis – exception may fail if rate changes do not reflect value

The right-to-invoice practical expedient generally fits only solely usage-based pricing at a fixed rate. Substantive minimums, rate changes during the term, or significant upfront fees usually rule it out.

Step 4: Embedded Lease and Service in One Contract

If a lease exists, the contract usually still contains nonlease components – managed operations, networking, support, or software. The lessor allocates the consideration to lease and nonlease components using the ASC 606 allocation guidance. Separation and the ASC 842 lessor practical expedient are covered in a separate article.

Variable payments matter here as well. Usage fees that relate to the lease component and do not depend on an index or rate are excluded from the initial consideration and recognized when the usage occurs, allocated on the same basis as the initial allocation. In-substance fixed minimums, by contrast, belong in the initial consideration.

Implementing Compute Contracts in SAP

Once the accounting analysis is stable, the SAP design follows it:

• Billing and usage. High-volume usage is typically rated and invoiced in SAP BRIM, with SAP Convergent Charging and Convergent Invoicing. Convergent Invoicing transfers order, fulfillment, and invoice items to SAP RAR.

• Revenue contracts. In SAP RAR, reserved capacity, usage, and services become performance obligations in one revenue contract. Time-based fulfillment fits stand-ready capacity; event-based fulfillment fits usage.

• Allocation. Standalone selling prices drive the allocation across capacity, services, and – where applicable – the lease component.

• Lessor accounting. If a dedicated cluster is an embedded lease, SAP RAR handles the lessor side under ASC 842 and IFRS 16 alongside the ASC 606 obligations, without additional software.

• Contract changes. Capacity expansions and hardware generation upgrades are frequent. Each change needs a defined path as a contract modification – and, where a lease exists, as a lease modification.

In an Agentic Finance approach, agents can screen new contracts for exclusivity, substitution, and minimum-commitment clauses and route them to accountants for the judgment call.

The Bottom Line

GPU and compute capacity contracts look like simple pricing, but the accounting depends on three decisions: service or lease, stand-ready or specified volume, and how minimums reset. Make those decisions per offering, document them in policy, and design SAP BRIM and SAP RAR around them – not the other way round.

Related terms: Embedded Lease · Minimum Commitment · Variable Consideration

Related articles: Leases in Bundled Contracts: Separating Lease and Non-Lease Components · Subscription and Usage-Based Billing: Key Design Decisions

Structuring revenue and lease accounting for compute capacity contracts? Talk to our experts.