Asset accounting under a hardware-as-a-service (HaaS)

If you have moved your laptops, desktops and smartphones from ownership to a subscription model, the next question your CFO will ask is how to book the invoices. Hardware as a Service (HaaS), also called Device as a Service (DaaS), looks like a simple operating cost on paper. In practice, the accounting treatment depends on how the contract is structured, which reporting standard you follow, and whether the arrangement contains what auditors call an embedded lease. This article explains how to account for HaaS as a customer, not as a provider, with an eye on both IFRS (the framework used across Europe and most of the world) and US GAAP. You will see the difference between OpEx treatment and lease accounting, what to document, and which questions to put to your provider before signing. The examples reference how devicenow structures Device as a Service for organizations running 1000+ IT seats across 190+ countries.

What HaaS actually is from an accounting perspective?

Hardware as a Service is a subscription arrangement where you pay a recurring fee for access to end user devices bundled with services. Under devicenow, that package includes the hardware (laptops, desktops, smartphones, tablets, workstations, monitors and peripherals) plus procurement, staging, global delivery, Autopilot enrolment, Break & Fix with next business day swap, device return, certified data erasure and remarketing.

Three things make HaaS different from a pure software subscription from a finance perspective.

• There is a physical asset involved. Unlike SaaS, HaaS gives you the right to use tangible property, which brings it into scope of lease accounting standards.
• The service component is significant. Most of the monthly fee covers services, not the device itself. Procurement, configuration, logistics, break fix and end of life are all bundled into the subscription.
• The contract terms decide the accounting. Two HaaS deals with identical pricing can end up in different accounting buckets depending on term length, renewal rights, substitution rights and who controls the asset.

The starting point for your treatment is therefore always the contract, not the invoice.

The accounting standards that apply to HaaS

When you evaluate how to account for Hardware as a Service, two frameworks cover most organizations. Which one applies depends on where you report.

Under IFRS 16, there is no separation between operating and finance leases for lessees. If the contract meets the definition of a lease, it goes on the balance sheet. ASC 842 keeps the distinction, so an operating lease for a laptop under US GAAP still produces a right of use asset and a lease liability, but the expense pattern on the income statement is different from a finance lease.

Both standards apply only to leases with a term longer than 12 months. IFRS 16 allows an exemption for low value assets, typically interpreted as items with a new value under around USD 5,000. An individual laptop or smartphone usually sits inside this threshold, but a fleet of devices under one master contract may need to be assessed as a whole.

If you report under local GAAP in a European market, your national standard is usually converged with IFRS 16 or is moving toward it. The UK and Ireland’s FRS 102, for example, is being updated to align with IFRS 16 from 2026. Always confirm the exact requirements with your local auditor.

Is your HaaS contract a lease or a service?

This is the central question. A HaaS contract is a lease if it gives you the right to control the use of an identified asset for a period of time in exchange for payment. If it does not, it is a service contract and you can expense the fees as they are incurred.

Four tests help you decide.

1. Is the asset identified? Do you receive a specific laptop (by serial number), or does the provider simply promise access to a device of a given specification? If the provider can swap devices freely without your consent, the asset is usually not identified.
2. Do you control the use? Can you decide how and by whom the device is used during the contract term?
3. Do you receive substantially all the economic benefits? In HaaS this is almost always yes, because the device sits with your employee.
4. Does the provider have a substantive substitution right? If the provider can genuinely substitute the device at any time and would benefit economically from doing so, the arrangement may not be a lease.

Under a devicenow subscription, devices are registered, staged and delivered to specific end users, with break and fix handled through next business day swap. The substitution right exists for failures, not at the provider’s convenience, which typically points toward lease treatment for the hardware component. The bundled services (procurement, staging, logistics, swap, end of life) are not leases, they are services, and IFRS 16 and ASC 842 require you to separate lease and non lease components unless you elect a practical expedient to combine them.

Your auditor is the final authority here. What this article gives you is the framework to have the conversation.

OpEx treatment when HaaS is a service contract

If your HaaS contract does not meet the definition of a lease, the accounting is straightforward.

• Monthly subscription fees are recognized as operating expenses in the period they relate to.
• There is no right of use asset and no lease liability on the balance sheet.
• The impact runs entirely through the income statement, usually in IT operating costs or cost of services.
• Prepayments are recorded as prepaid expenses and released over the service period.

This is the treatment companies often expect when they move from buying to subscribing, and it matches the CapEx to OpEx narrative that makes HaaS attractive to finance teams. Whether you can actually apply it depends on the lease tests above.

devicenow offers pay per use billing with fixed monthly pricing per device, and you are charged only for devices in active use. Cost allocation by cost center or business unit is supported through the Lifecycle Portal and API integration into your ITSM or procurement system, which simplifies the internal accounting work even if the underlying treatment is a lease rather than a pure service.

Lease treatment when HaaS falls under IFRS 16 or ASC 842

If your contract does meet the definition of a lease, the accounting looks different.

On the balance sheet

You recognize a right of use (ROU) asset and a lease liability at commencement. The ROU asset is initially measured as the present value of the lease payments plus initial direct costs and any prepayments, less any lease incentives. The liability is the present value of the remaining payments, discounted using the interest rate implicit in the lease or, if not determinable, your incremental borrowing rate.

On the income statement

• Under IFRS 16, you record depreciation of the ROU asset (typically straight line) and interest expense on the lease liability. Total expense is higher in the early years and declines over time.
• Under ASC 842 for an operating lease, you record a single straight line lease expense over the term, even though the liability unwinds using interest. Finance leases follow the IFRS 16 pattern.

On the cash flow statement

• Under IFRS 16, principal repayments of the liability go to financing activities and interest either to operating or financing depending on policy.
• Under ASC 842 operating lease, payments stay in operating cash flow.

Separation of components

Both standards require you to separate lease components (the device) from non lease components (the services). The consideration in the contract is allocated between them based on standalone selling prices. Lessees under both IFRS 16 and ASC 842 can elect a practical expedient to combine them by class of underlying asset.

For HaaS specifically, this means you may need to estimate how much of the monthly fee relates to the device versus procurement, staging, logistics, swap and end of life services. Your provider’s pricing transparency affects how easy this is.

Practical accounting checklist for HaaS contracts

Before you sign a HaaS subscription, walk your finance team through these points. It is much easier to structure the arrangement correctly at contract stage than to restate it at year end.

• Term. Is the committed term longer than 12 months? If yes, the short term lease exemption does not apply.
• Identified asset. Does the contract tie each subscription to a specific device or only to a specification? Check whether serial numbers appear in the delivery confirmation.
• Substitution rights. Does the provider have the right to swap devices freely? If substitution is only for failures or end of life, the asset is more likely identified.
• Renewal and termination. Are renewal options likely to be exercised? What are the penalties for early termination?
• Component pricing. Does the contract break down the fee between hardware and services, or is it a single bundled rate? Bundled pricing increases estimation work.
• Variable fees. Is the fee fixed per device per month, or does it vary with usage? Variable fees based on an index or rate affect lease liability measurement under IFRS 16.
• Low value exemption (IFRS 16 only). Can individual devices be treated as low value leases? This depends on the new value of each device and your policy.
• Reporting standard. Are you reporting under IFRS, US GAAP or both? Dual reporters need parallel records.

devicenow contracts include fixed monthly pricing per device, pay per use billing, a transparent service scope and a single SLA across 190+ countries. The service bundle (procurement, staging, delivery, swap, end of life) is described explicitly in the contract, which helps when you need to separate lease and non lease components.

Tax and cost allocation considerations

Tax treatment of HaaS is jurisdiction specific, so always confirm with your tax advisor. A few principles tend to hold across most markets.

• Deductibility. Subscription fees are generally deductible as operating costs in the period they are incurred, whether you apply service accounting or lease accounting. The difference is usually in timing rather than overall deductibility.
• Indirect tax. Cross border HaaS contracts raise VAT (in Europe and most of the world) or sales tax (in the US) questions, especially when one master contract covers devices shipped into many jurisdictions. Rules on place of supply and reverse charge mechanisms affect how invoices are issued and accounted for. devicenow operates in 190+ countries, so invoicing structure is usually agreed as part of onboarding.
• Withholding tax. Some jurisdictions treat equipment rental fees differently from pure services for withholding tax purposes. Relevant if you centralize billing and pay invoices across borders.
• Cost allocation. For internal reporting, most finance teams allocate HaaS costs to the cost center where the end user sits. Per seat pricing makes this clean. Real time reporting through the devicenow Lifecycle Portal supports cost center allocation and chargeback.

For ESG and sustainability reporting, HaaS usually reduces reported e-waste and extends device lifecycles. This matters particularly under the EU Corporate Sustainability Reporting Directive (CSRD), which brings more companies into mandatory ESG disclosures. devicenow runs a circular model with certified data erasure and refurbishment at end of subscription, and provides the documentation your ESG team needs for reporting.

Common mistakes when accounting for HaaS

A few errors show up repeatedly in finance reviews of HaaS contracts.

1. Treating all HaaS as OpEx by default. The attractive narrative of subscription economics does not override the lease definition. If the contract meets the criteria under IFRS 16 or ASC 842, it is a lease regardless of the sales pitch.
2. Ignoring the 12 month threshold through auto renewal. A 12 month term with auto renewing annual extensions that you are reasonably certain to exercise can pull the arrangement past the short term exemption.
3. Lumping device and service fees into one line. Even if you elect the practical expedient to combine components, you still need to document the decision. If you do not elect it, you need to allocate consideration.
4. Forgetting the global footprint. A HaaS contract signed centrally but billed into multiple countries has local tax and accounting consequences. Get local finance teams involved at contract stage.
5. Missing end of life cost treatment. Devices returned at end of subscription trigger deprovisioning and data erasure. These are usually included in the provider’s service, but any additional costs on your side (shipping from a specific site, for example) still need a home in your books.

Accounting with HaaS doesn’t have to be difficult

How you account for Hardware as a Service depends on one question: is the arrangement a lease or a service? The answer comes from the contract, not from the invoice and not from the sales material. Under IFRS 16, most HaaS contracts longer than 12 months with identified devices and limited substitution rights will end up on the balance sheet. Under ASC 842, the same contracts also capitalize, with a different expense pattern. In both cases, separating the hardware from the bundled services is part of the exercise.

Before you sign a HaaS subscription, get your finance team, your auditors and your tax advisors aligned on the treatment. devicenow’s service scope (fixed monthly pricing, pay per use billing, transparent lifecycle services and a single SLA across 190+ countries) gives you the contractual clarity you need to make that assessment well, but the final accounting call sits with your own organization.