ASC 606 Revenue Recognition for Hardware-as-a-Service (HaaS) Companies

In a Hardware-as-a-Service model, the customer pays a single recurring fee and receives a device, embedded or cloud software, and ongoing support or replacement. Think connected sensors, point-of-sale terminals, or medical devices sold on subscription. The money arrives as one clean monthly number, but accounting cannot treat it as one thing. ASC 606 requires you to decompose the arrangement, because different components are earned at different times.

Before applying ASC 606, ask whether the hardware is a lease under ASC 842. A contract contains a lease if it conveys the right to control the use of an identified asset for a period: the customer gets substantially all the economic benefits from using the device and directs how and for what purpose it is used. If so, the lease component is accounted for under ASC 842 (as a sales-type or operating lease from your side as lessor), and the software and service components stay under ASC 606.

The test often fails for HaaS. If you have a substantive right to substitute the device throughout the term (you can swap units at will and benefit from doing so), there is no identified asset and no lease. Lessors can also elect a practical expedient under ASC 842 to combine lease and nonlease components when certain conditions are met, so check your policy elections before building two sets of schedules.

Within ASC 606, list every promise in the contract and decide which are 'distinct.' A device that works only with your proprietary platform may not be distinct from the software, in which case they combine into a single obligation. A device that has standalone value, plus separately useful software and support, may be three obligations. The number of obligations directly drives the timing of revenue, so this judgment is the most consequential step.

Once obligations are identified, allocate the total contract price to each one based on its standalone selling price (SSP), meaning the price you would charge if you sold that item separately. When you never sell components separately, estimate SSP with an adjusted market assessment or an expected cost plus margin approach. A bundle discount is generally spread across all obligations in proportion to SSP rather than assigned to one component, which keeps you from front-loading revenue onto the hardware.

Apply the timing rule to each obligation. Hardware revenue is recognized at a point in time only when control of the device passes to the customer, usually at delivery or installation, as in a sale with title transfer. Cloud software access, support and monitoring are satisfied over time, so their allocated revenue is recognized ratably across the term.

If you keep title, can reclaim or swap the device, and the customer cannot use it without your service, the device is usually an input to the service rather than something transferred. Then the whole fee is recognized over time. If the device is an operating lease, lease income is also recognized over the lease term.

The practical effect is that the same monthly fee can produce very different revenue patterns. A sold device creates a revenue spike at shipment, which surprises founders who think of their product as all subscription. A retained device produces a smooth monthly line.

A labelled example shows how one fee splits. A customer signs a 36-month contract at $250 a month, $9,000 in total, for a sensor that the customer owns on delivery plus cloud monitoring and support. Assume the device and the service are distinct, and that you estimate standalone selling prices of $2,400 for the device and $220 a month ($7,920 over 36 months) for the service.

1. Total SSP: $2,400 + $7,920 = $10,320.
2. Device allocation: $9,000 x $2,400 / $10,320 = $2,093.
3. Service allocation: $9,000 x $7,920 / $10,320 = $6,907, or about $191.86 a month.

At delivery you recognize $2,093 of hardware revenue plus the first month's $191.86 of service revenue, while you have billed only $250. The difference, about $2,035, is a contract asset that unwinds as monthly billings exceed monthly service revenue.

Because the customer pays for the device over three years, check for a significant financing component. ASC 606 offers a practical expedient only when the period between transfer and payment is one year or less, so a 36-month payment stream may require you to separate interest income from the device revenue.

If instead you keep title and can swap the sensor, the full $250 is service revenue each month, and the device sits on your balance sheet as equipment.

The accounting for the device's cost follows the revenue answer. If the device is sold, its cost moves from inventory to cost of revenue when control transfers, matching the hardware revenue recognized at delivery.

If you keep the device and it is an input to your service, capitalize it as property and equipment (often labelled "devices in service" or "rental fleet"), depreciate it over its expected useful life, and present the depreciation in cost of revenue alongside hosting and support. Refurbishment and redeployment of returned units extend that life, so track devices by serial number.

If the arrangement is a sales-type lease, you derecognize the device and record a net investment in the lease. If it is an operating lease, the device stays on your books and is depreciated, as with a retained device.

Sales commissions on multi-year HaaS contracts are a separate question under ASC 340-40, which generally requires capitalizing incremental costs of obtaining a contract when the amortization period would be longer than one year.

A HaaS company needs a few schedules that a pure software company can skip. Build them before your first audit:

• A contract-level revenue schedule showing each performance obligation, its allocated price and its recognition pattern.
• A contract asset and deferred revenue rollforward tying billings to revenue.
• An SSP memo, updated at least annually, documenting how each standalone selling price was estimated.
• A device register with serial number, location, status (in service, returned, refurbishing) and net book value.
• A lease assessment memo for each contract template, recording the identified asset and substitution analysis.

These schedules also produce the numbers investors ask for: recurring revenue, hardware margin and device payback period.

Investors evaluate HaaS companies on recurring-revenue quality. If you report the entire fee as subscription revenue, your ARR and gross margin are overstated and will not survive diligence. Correct ASC 606 treatment isolates the genuinely recurring portion, gives you defensible SaaS metrics, and prevents painful restatements during a financing. We build the revenue policy, SSP analysis and schedules so the numbers hold up when investors look closely. This is general guidance, not accounting or tax advice for your specific facts.