Concept and Purpose
Leasing typically finances the use of a device on a fixed plan. The focus is on hardware; ownership remains with the lessor. Rental/DaaS focuses on ongoing provision and is conceptually designed around device plus associated services.
Flexibility
Same mathematics, different refinancing logic. In both models, calculations consider interest rate, term, acquisition cost, and end-of-term resale value. Differences in flexibility arise less from calculations than from provider risk appetite regarding resale of used assets and above all from their refinancing approach.
Leasing (typical forfaiting)
- The leasing company often sells a fixed payment stream over the term to a bank (forfaiting).
- The payment stream in such setups is typically non-recourse and fixed during the term (e.g., 36 months at €2,500).
- Bank decision: primarily based on the lessee’s creditworthiness and the ratio of payments to acquisition cost.
- Result: Limited flexibility for usage (termination, scaling, swaps), because changes disturb the payment stream.
Rental (asset- and portfolio-financed)
- Often refinanced through investors (family offices, funds, corporations); security lies in asset value over usage, resale potential, and risk distribution across tenants.
- Payment stream and usage duration are more flexible for financiers.
- Result: True flexibility is possible if contractually and operationally provided; however, it is not standard today.
Services and Partner Choice
Services can be included in both financing forms. The difference lies in the fine print:
Leasing (forfaited and invoiced separately):
Payment streams are forfaited and meant to remain constant. Service is often shown separately: hardware vs. service. Responsibility for service remains with the provider or is shared, depending on contract.
Consequence of poor service (leasing):
Service failure typically allows the customer to reduce payment only by the service share (e.g., €5 out of €25), depending on contractual rights (e.g., service credits, price reduction, set-off/retention).
Result: Lessor usually does not assume holistic usage responsibility; financing focuses on hardware.
Rental/DaaS (bundled usage responsibility if agreed):
Provider can assume full responsibility for device and services if SLA, governance, and responsibilities are contractually bundled.
Consequence: Payment can be reduced up to the full €25 in case of service failure, if contractually arranged (e.g., service credits, price reduction, retention).
Short summary:
Services exist in both worlds. Leasing separates accounting and responsibility; DaaS can bundle usage responsibility, enabling stronger contractual remedies for service failure.
Accounting / Balance Sheet
Leasing
On- or off-balance depends on framework (HGB, IFRS, US GAAP) and contract. No automatism.
HGB (Germany):
Criterion is economic ownership. Practice: 40/90 rule as a guideline, end-of-term conditions (purchase option, put option, return guarantee). If term is market-standard and rules plausible, asset stays with lessor → user usually off-balance. If the structure deviates significantly, it may become on-balance.
IFRS (international):
If lease exists (identified asset, no substantial substitution rights, non-cancellable term), record right-of-use and lease liability → on-balance. The lease liability is split into current (≤12 months) and non-current (>12 months). The current portion represents a real cash outflow in the next year relevant for liquidity and covenants. Exceptions: short-term (≤12 months, no purchase option) and low value items may run as expense.
US GAAP (ASC 842):
Operating and finance leases generally on-balance for lessee. Short-term can be treated as expense.
Practice:
Fixed contract on specific device → often capitalization (IFRS/US GAAP). Under HGB, same contract can remain off-balance if logic and end-of-term rules fit. Service inclusion does not automatically change assessment.
Rental/DaaS
Key is whether rental is factually a lease. If not, it is an expense.
IFRS / US GAAP:
If the lease meets all lease criteria (identified asset, no substantive substitution rights, non-cancellable term), a right-of-use asset and lease liability must be recognized. Short-term leases and low-value assets under IFRS may be expensed.
HGB:
Service-like rental generally remains off-balance for the lessee; economic ownership stays with the provider.
Practice:
Service-like, flexible rental models (e.g. monthly cancellable terms, device pooling, or effective substitution rights of the lessor) may be treated as an expense, depending on the applicable standard and contractual structure.
A fixed device assignment without a termination option over a defined term, however, triggers lease accounting and therefore balance-sheet recognition (unless an exemption applies).
Note: If rental behaves like a lease (fixed term, assigned device) → same accounting as leasing.
Key takeaway:
Label does not decide; standard + contract structure matters: identified asset, control, term/options, HGB/IFRS/US GAAP logic.
P&L & KPIs
What’s it about?
Leasing and rental arrangements affect the income statement (P&L) and financial ratios differently. It is also important to consider what becomes due within the next 12 months (current liabilities).
Leasing / factual lease:
- Balance sheet: You recognize a right-of-use asset and a lease liability. The liability is split into current (≤ 12 months) and non-current (> 12 months) portions.
→ Total assets and (lease) obligations increase. - P&L: Instead of rental expense, you typically recognize depreciation and interest (depending on the accounting standard and presentation).
→ EBITDA may be higher; the net result depends, among other things, on interest and the useful life. - KPIs: Net Debt/EBITDA often deteriorates, and the equity ratio may decline depending on KPI/covenant definitions and the accounting standard.
The current portion represents a real cash outflow within the next year, which is important for liquidity and covenant calculations.
100% flexible rental (no lease)
- Balance sheet: Generally no lease liability is recognized; in the short term, only typical payables from ongoing invoices or accruals arise. → The balance sheet remains leaner, with no additional (lease) debt.
- P&L: Payments are recognized as rental expense. → EBITDA tends to be lower than under a lease structure.
- KPI: Leverage and the equity ratio tend to remain more stable, depending on KPI definitions and the applicable standard. Planning is opex-based, without splitting obligations into short- and long-term debt.
Key takeaway:
Leasing can raise EBITDA but increases lease liabilities; service-like rental keeps balance leaner. Labels don’t matter: structure does.
Conclusion:
Leasing can increase EBITDA, but with a lease-like structure it also brings a right-of-use asset and a lease liability onto the balance sheet and may therefore affect leverage and the equity ratio (depending on the accounting standard and KPI definitions). Service-like rental or DaaS often keeps the balance sheet leaner and financial ratios more stable, as payments are recognized as expenses — although EBITDA tends to be lower as a result.
What ultimately matters is not the label, but the structure: whether there is an identifiable asset, control, the term and options, termination rights or substitution rights, and whether short-term obligations within the next 12 months arise. This allows you to choose the model that truly fits your cost structure, flexibility needs, and management objectives.
| Criterion | Purchase | Leasing | Rental / DaaS (service-based) |
| Brief definition | The company acquires the device (ownership) and pays the purchase price (typically CAPEX). | Use in exchange for regular payments over a defined term; ownership remains with the lessor (with purchase/extension options, if applicable). | Use as a service: Equipment plus defined lifecycle services (e.g., rollout, support, replacement, reporting) as a predictable rate (optionally with flex modules). |
| Orientation | Purchase-oriented (focus on procurement/ownership). | Purchase/financing-oriented (focus on hardware financing, liquidity, predictability). | Process-oriented (focus on lifecycle management, standardization, services, and governance). |
| Budget / cash flow | High initial investment; ongoing operating/lifecycle costs are incurred additionally (internal/external) and vary with failures/changes. | Predictable rates; overall picture depends on service scope, options, and end-of-term rules. | High predictability with clearly defined scope of services (SLA, in/out of scope) and transparent change/index rules; costs are bundled into one rate. |
| Technology & refresh | Freely configurable but often dependent on internal budgets/processes (refresh is often postponed). | Refreshes/upgrades are possible, but often linked to term/options; early changes may incur costs depending on the contract. | Refreshes based on demand can be controlled in a policy-based and standardized manner, depending on contract design (e.g., pooling, swap window, standard profiles). |
| Flexibility (termination, scaling, swap) | High at decision stage, but operationally “your issue” (procurement, rollout, return, replacement logistics, etc.). | Typically low flexibility: changes such as termination, swaps, or scaling are often restricted or associated with costs depending on contract and refinancing logic. | Potentially most flexible when termination, swap, and scaling rules are explicitly agreed upon (flexibility is a design feature, not an automatic feature). |
| Services & responsibility | Services must be provided internally or purchased and managed separately (more coordination/interfaces). | Services are possible but often separated in terms of organization/billing (device vs. service). Responsibility is distributed according to setup. | Bundled usage responsibility possible (one model, fewer interfaces, clearer responsibilities, simpler governance). |
| Leverage in case of poor performance | Dependent on warranty/service contracts; often high internal effort to compensate (replacement, escalation). | For separately selected service areas, service credits or reductions often primarily affect the service area depending on contractual rights. | In bundled service models, service credits or price reductions can affect the total service: provided metrics, escalation paths, credits, and rights (e.g., set-off) are clearly agreed. |
| Accounting (short logic) | Capitalization and depreciation at the company. Depends on accounting standards and contract structure (no automatic off-balance treatment). | For lease-like structures: right-of-use asset and lease liability are recognized on the balance sheet. Key factors include asset identifiability, control, term, termination options, substitution rights, and end-of-term conditions (purchase option, put option, residual value guarantee). | Depending on structure: service-like (expense) or lease-like (on-balance sheet). Decisive factors include asset identifiability, control, term/termination options, and substitution rights – not the label. |
| P&L / KPI trend (simplified) | Depreciation; EBITDA is not reduced by rental expenses (operating costs remain). | For lease-like structures: instead of rental expense, depreciation + interest or leasing expense per standard → EBITDA may be higher; balance sheet total and lease debt increase; KPI effects depend on KPI/covenant definitions. | For service-type rentals: expense in the income statement → EBITDA tends to be lower; however, there is generally no additional lease liability (for non-lease-like structures). KPI effects depend on standard/definition. |
| Internal IT effort | High (lifecycle, ITAM, rollout, repair, replacement, return, disposal, reporting). | High (lifecycle usually remains internal; additional contract/asset and end-of-term management and possibly multiple partners/interfaces). | Typically lower because lifecycle processes, tooling, and services can be included (governance/control remains with you). |
| Typical risks | Obsolescence, residual value/disposal, “shadow TCO” due to internal effort and process breaks. | Contract rigidity, interface risks (separate devices/services), complexity when exercising options or making changes. | Provider dependency, transition effort, service quality: manageable through clear SLAs/KPIs, exit rules, swap rules, data/security requirements, and transparency. |
| Best Fit | Very stable requirements, long-term use, strong internal processes, CAPEX leeway. | When financing and predictability of hardware are the primary concern and services are managed separately. | When standardization, predictability, lifecycle relief, and controllability are priorities (especially with growing fleets/complexity). |
| International | Possible internationally, but rollout/support/compliance and delivery/return processes must be organized internally per country, scaling across countries usually requires high internal effort with limited synergy effects. | Possible internationally, but often with country-specific contract, tax, and process variants; coordination effort increases. | Can facilitate international standardization (uniform policies, processes, reporting) if provider footprint, local logistics/service, and tax/VAT aspects are covered; for experienced providers this is usually part of the operating model. |
| Regulation & associated process costs | High internal effort to meet local/regulatory requirements (documentation, audits, evidence). | Partially supported but often fragmented across several contracts/partners (higher verification and coordination effort). | Reduced control and process effort possible if compliance processes, documentation, and reporting are centrally bundled and contractually regulated. |
| Liabilities | No lease liabilities; liquidity primarily CAPEX-driven. | For lease-like structures: right-of-use asset and lease liability, including current portion (≤12 months). | In genuine short-term service-type rentals there is generally no balance-sheet lease liability; only usual short-term liabilities from ongoing invoices arise. |
| Principal–agent logic (partners) | Not relevant (in-house operation). | Often multi-party setups (hardware and services separate) → roles and responsibilities distributed. | Can be designed as a principal model (one contract / one invoice / end-to-end responsibility) or as an agent/partner model; the principal model typically reduces coordination, reporting, and compliance effort, while the agent model increases it. |
Download Tabelle (PDF)
This table complements the Deep Dive article with a comprehensive comparison of purchase, leasing, and rental/DaaS and includes additional decision criteria that are not covered in detail in the article — including:
- Internationalization (scaling across countries, provider footprint, local logistics/service, tax/VAT)
- Regulation & process requirements (governance, documentation, audit and compliance reporting)
- Capitalization / liabilities (including short-term portions ≤ 12 months; depending on the accounting standard and contract structure)
- Principal–agent logic (partners) (operating model, responsibilities, reporting and coordination effort)
- Additional criteria such as budget/cash flow, technology & refresh cycles, internal effort, risks, and overall best fit.
Disclaimer:
Flexibility, international scaling, and regulatory relief are not automatic but depend on contract and process design (termination rights, swap rules, governance, provider footprint).
“Off-balance” or lease liability is not a product promise; it arises from accounting standard + contract structure.
P&L and KPI effects vary; this is not legal or tax advice; a binding assessment should always be made by qualified legal, tax, or accounting advisors.
