The file from Provider C arrived on a Tuesday morning, same as every month: 140 rows, registration numbers in column A, monthly payments in column D. Somewhere in row 87, a van the business had handed back six weeks earlier appeared with the same field values as every active vehicle in the portfolio. No termination flag. No zero balance. Just a row that looked, to a spreadsheet comparison, exactly like a vehicle that belonged in the register. The analyst matched it to an open slot, created the lease record, and the FRS 102 calculations ran that evening. By Wednesday, the organisation was carrying a lease liability and a right-of-use (ROU) asset for a van sitting in a fleet provider's compound.
That's the specific operational risk that Section 20 of FRS 102 creates for fleet-heavy organisations in the UK and Republic of Ireland. The accounting treatment isn't complex, but the data management is.
Updated August 2026.
This guide is for finance teams already working through the FRS 102 transition, not a re-explanation of the standard itself. For that, see our plain-English guide to FRS 102 and the FRS 102 Lease Accounting page. What follows covers the specific mechanics that make fleet different from property: the low-value exemption trap, what each vehicle event triggers, and why the data challenge compounds month by month.
Note: LOIS Fleet Management Transform is designed for fleet data files supplied by fleet lessors. It cannot process property lease files, which use a multi-row-per-lease format that Transform is not built to handle. Property leases are managed separately within LOIS.
From accounting periods beginning on or after 1 January 2026, FRS 102 Section 20 requires UK and Irish lessees to recognise a right-of-use (ROU) asset and a corresponding lease liability for virtually every lease they hold. For a plain-English explanation of how ROU assets work under IFRS 16 and the aligned standards, our guide to right-of-use assets covers the mechanics. The old distinction between finance leases (on-balance sheet) and operating leases (off-balance sheet) is gone. If you have a lease, it goes on the balance sheet: a right-of-use asset and a lease liability measured at the present value of future payments, discounted at your obtainable borrowing rate.
Two exemptions exist for lessees. The short-term lease exemption covers leases with an original term of 12 months or less, relevant for temporary vehicle hire but not for standard fleet contracts, which typically run 24 to 60 months. The low-value asset exemption covers assets that were low-value when new. For fleet, this second exemption doesn't apply, and understanding exactly why matters.
The short answer for most UK and Irish fleet operators is no, and not just because the vehicles cost too much. Under FRS 102 Section 20, vehicles are explicitly listed as an asset class that does not qualify for the low-value exemption. The standard names vehicles specifically as an example of assets that are not low-value, regardless of what they cost when new.
Run these three checks before assuming any fleet lease can be kept off-balance sheet:
The conclusion for fleet: every vehicle lease (vans, HGVs, company cars) must be capitalised under FRS 102 Section 20 unless it qualifies as a short-term lease (original term of 12 months or less). There is no low-value route out for vehicles.
This is one of the material differences between FRS 102 and IFRS 16. Under IFRS 16, the low-value guidance is less prescriptive: the standard offers tablets and personal computers as examples of qualifying assets and suggests vehicles of low value could in principle qualify. FRS 102 is more explicit. For a fuller comparison of how the two standards diverge, our post on FRS 102 vs IFRS 16 key differences covers the accounting mechanics side by side.
The on-balance sheet treatment isn't a one-time calculation. Every change to a vehicle lease during its life is a Section 20 event that requires an accounting response. The events that happen routinely in a well-managed fleet portfolio, and what each one requires, are:
| Fleet event | Section 20 classification | What the accounting requires |
|---|---|---|
| Vehicle return (early) | Scope reduction / termination | Derecognise lease liability and ROU asset; difference to income statement |
| Vehicle swap / replacement | Termination + new commencement | Derecognise old lease; recognise new ROU asset and lease liability from commencement date |
| Lease extension | Modification (change in scope or consideration) | Remeasure lease liability using revised payment stream; adjust ROU asset |
| Price or rental change | Remeasurement event | Recalculate present value of revised payments; adjust liability and ROU asset on effective date |
| New vehicle addition | Initial recognition | Recognise ROU asset at cost; recognise lease liability at present value of future payments |
For a detailed walkthrough of how Section 20 remeasurements work, including what triggers a modification versus a reassessment, our post on FRS 102 lease modifications under Section 20 covers the accounting mechanics in full.
A 140-vehicle fleet with typical churn generates six to ten of these events every month. At that volume, the question isn't whether your accounting model is correct in theory: it's whether your data process catches every event reliably in practice.
Property leases are relatively stable. A warehouse signed in March might not change again until a rent review in two years. The finance team adds it to the subledger, sets the amortisation schedule, and the calculations run undisturbed month to month.
Fleet doesn't work like that. Four structural differences make fleet data materially harder to control:
Those four factors combine into a data management problem that most finance teams try to solve with a VLOOKUP-style comparison in Excel: open the provider file next to the lease register, match on registration number or contract reference, look for what's changed. At 20 vehicles it works. At 140 vehicles across three providers with three different identifier conventions, you're doing manual lookups for every mismatch, and the error you're most likely to miss is the one with no match at all.
A missed fleet event doesn't sit quietly as a one-period error. Under Section 20, a termination that goes unprocessed means the lease carries on generating depreciation and interest charges in your income statement, while the liability remains on the balance sheet for a vehicle your organisation handed back months ago. Nobody flags it. The calculations run. By the time an auditor asks about the lease liability for vehicle X, you're not unwinding one month's entry; you're reconstructing several months of incorrect amortisation schedules and accounting for the cumulative difference.
The failure modes that recur in manual fleet data processes:
Any of these that get past the monthly data check become accounting errors. And FRS 102 accounting errors in fleet data are exactly the kind that accumulate silently, then surface at audit time when unwinding them is most expensive.
FRS 102 Section 20 doesn't prescribe a single presentation for fleet ROU assets. In practice, most organisations present vehicle ROU assets either as a separate line within the property, plant and equipment note ("ROU assets: vehicles") or within an existing vehicles or motor vehicles class. The key requirement is that ROU assets are presented or disclosed separately from owned assets, so readers can identify the balance sheet impact of the lease accounting model.
For the lease liability, fleet is typically combined with property lease liabilities in the maturity analysis disclosure: the split between current and non-current lease liabilities, and the undiscounted cash flow bands (under one year, one to five years, over five years). If your fleet liability is material relative to property, consider showing fleet and property lease liabilities separately in the disclosure to give readers a clearer picture of what's driving the numbers.
For background on what the full disclosure pack under Section 20 requires, the post on FRS 102 Section 20 disclosure requirements covers each disclosure in detail.
At 10 vehicles from a single provider, a monthly update takes twenty minutes. The file is short enough to read, the changes easy enough to spot, and if something looks off you can check it by eye. It works well enough.
At 100 or more vehicles across multiple providers, that model breaks down. The monthly data volume exceeds what manual comparison reliably handles. Each provider delivers data in its own format on its own schedule. Fleet events arrive not as discrete notifications but as implicit differences between this month's file and last month's, and some of those differences (a row that disappears, a payment that changes by 3%) don't announce themselves as accounting events. They have to be found.
At that scale, automation isn't a convenience. It's the only control that works at zero-error rates. The question isn't whether your team is capable of running the comparison manually; it's whether manual comparison is a reliable control for this volume and this change frequency. For most fleets over 100 vehicles, the honest answer is no.
When your fleet provider data file is uploaded to LOIS Fleet Management, it cross-checks every record against your existing lease portfolio and identifies each change by type before anything is applied:
Each change is presented to your finance team for review before any update is applied to the lease register or the FRS 102 calculations. LOIS accepts data from any fleet provider in any standard format; your team uploads the file as it arrives, without reformatting it first. CA-qualified accountants at LOIS validate the data as part of the managed service, catching discrepancies before they become audit issues.
The four-step process follows a consistent sequence regardless of how many providers you're working with:
If your monthly fleet update process is manual today, that risk compounds month by month. The returned van from the opening of this post, the one that shows up in row 87 looking like a new commencement, gets caught at step 2, before it reaches the register or the journals.
Are vehicle leases exempt from FRS 102 Section 20?
No. Under FRS 102 Section 20, vehicles are explicitly excluded from the low-value asset exemption. All vehicle leases (vans, HGVs, company cars, and other fleet assets) must be recognised on the balance sheet as ROU assets and lease liabilities, regardless of the vehicle's value. The only exemption that may apply to fleet is the short-term lease exemption for leases with an original term of 12 months or less.
How is the low-value asset threshold assessed under FRS 102?
The low-value assessment is made on the value of the underlying asset when new, not its current book value. A van purchased new for £25,000 doesn't qualify as low-value even if it's now worth £6,000. For vehicle leases, however, the assessment is moot: FRS 102 explicitly excludes vehicles from this exemption regardless of their new-when-purchased value.
What does a vehicle return trigger under Section 20?
An early vehicle return is a scope reduction under Section 20 and triggers a remeasurement. The lease liability for that vehicle must be derecognised, the ROU asset is written off, and any difference is recognised in the income statement. If the return isn't captured promptly, the lease continues generating depreciation and interest charges for a vehicle your organisation no longer holds, and the error compounds with every passing month.
How should fleet ROU assets be presented in the financial statements?
FRS 102 requires ROU assets to be presented or disclosed separately from owned assets, but doesn't mandate a separate balance sheet line for fleet specifically. In practice, most organisations show vehicle ROU assets within the property, plant and equipment note as a distinct class, separate from property ROU assets. Lease liabilities (fleet and property combined) are included in the maturity analysis disclosure, though material fleet portfolios may benefit from a separate split in the notes.
Does LOIS Fleet Management support FRS 102 Section 20?
Yes. LOIS Fleet Management accepts bulk fleet data from any lease provider in any standard format, cross-checks every record against your existing LOIS portfolio, and flags changes (new leases, price changes, rental changes, extensions, scope reductions, and terminations) for finance team review before any update is applied. Once confirmed, each change feeds directly into LOIS's FRS 102 Section 20 calculations with a full audit trail from the uploaded file through to the journal entry. For the full picture of how LOIS handles FRS 102 compliance, see the FRS 102 Lease Accounting page.
Stop catching fleet errors at the audit
LOIS Fleet Management validates incoming provider data against your existing portfolio before any change reaches your FRS 102 Section 20 calculations. If your monthly update process is manual today, that risk compounds every month.
See LOIS Fleet Management FRS 102 Lease Accounting