The ROI of corporate lease accounting software under FRS 102 comes down to one sum: the yearly benefit, minus the total yearly cost of owning the software, divided by that cost. Cost covers subscription, implementation, data migration and your own team's time to run it. The tricky part is the benefit, so start by putting a price on how you work today. Count the hours you can measure as savings, and treat misstatement and control risks as exposure, not savings.
If your leases sit across several entities, you'll know the moments. Five entity workbooks updated by hand before the first close review. An auditor asking for the signed contract behind one lease, and an hour gone on a shared drive. A rent review that property agreed in March and finance hears about in June, so the lease liability has been wrong for three month-ends. Every one of them costs your team hours, and none of them shows up as a line in the budget. That's why "the process is painful" rarely survives a CFO's first question: how much?
This guide is for UK corporate finance teams reporting under FRS 102 Section 20: CFOs, financial controllers and group reporting. We'll walk through a four-part cost baseline, then a worked ROI table in pounds sterling that you can copy straight into your own paper, then the costs to set against the savings. You don't need a financial model to start. Two month-ends of timing and a spreadsheet will do. LOIS is a lease accounting and management platform, built and supported by CA-qualified specialists, and it supports portfolios from 30 to 10,000+ leases. The method works at any size, but the case gets stronger once leases span several entities.
A lease accounting cost baseline is what manual lease accounting costs you each year, as you run it today. It has four parts: hours at close, hours of audit support, the expected cost of a misstatement, and the expected cost of a control deficiency. You can measure the first two now. The last two are estimates, so keep them in a separate column where they can't quietly inflate the total.
Time two month-ends before you estimate anything. A stopwatch figure from your own team beats a rule of thumb from any vendor, including us, and it's the number a sceptical CFO will ask for first.
Start with what the people doing the work cost you in a year: salary, employer pension contributions, employer's National Insurance, leave and a share of systems and space. Divide that by productive hours, not paid hours, because leave, meetings and training take a real share of the year. Use one blended rate across the baseline and the cost side, so you're not comparing hours priced two different ways.
1. FTE hours during close
Note down how many hours your team spends at each month-end on four jobs:
Multiply those hours by 12 and by your loaded rate, and you have the annual cost. The capacity you free is whatever share of those hours the new process removes. It only turns into cash if you avoid a contractor, overtime or a hire. Otherwise it becomes time for analysis, which is worth stating, but it's a different claim to put in front of your CFO.
2. Audit fee impact
Add up the hours your team spends during the audit retrieving contracts, explaining calculations and answering evidence requests, and price them at the same loaded rate. Then find the lease testing in your engagement letter, or ask the engagement partner to estimate it.
Treat that external fee as a memo line, not a saving. Auditors set their own fees and approach, so talk to yours about what an audit trail changes in how they test before you assume a lower fee. The base case you can defend counts only your own team's hours. Our guide to the FRS 102 first period-end close covers what auditors tend to ask for.
3. Misstatement and restatement risk
Lease balances usually go wrong in three ways: missed leases, incorrect assumptions and late adjustments. A lease nobody told finance about never reaches the register. An extension option assumed unlikely years ago is never reassessed. A modification lands after the books have closed and gets booked as a late adjustment.
Start by estimating what one correction event would cost you: internal investigation hours, external advisory or audit time, and revised disclosures. Then multiply by how likely you think it is to happen in a year. That gives you your expected exposure. Validation and review controls lower the likelihood, through checks on incoming data, review of remeasurements and approval before posting. They don't remove it. And an avoided restatement is a cost that never arrived, so you can't bank it as a saving. Show it beside the ROI, not inside it.
4. The cost of a control deficiency
A control deficiency comes with its own bill: time to investigate, time and external fees to redesign the control, and remediation testing to show the fix works across a period. Price each, add them up, and apply a likelihood as you did for misstatement.
Resist listing features. Take your last audit findings, or your own control self-assessment, and match each software control to a specific gap. If you can't name the gap, the control hasn't earned its place in the ROI.
| Gap an auditor finds | Control that closes it |
|---|---|
| Leases held in side files, missing from the register | One register of record, with the contract stored against each lease |
| Changes made without review | Approval workflow with segregation of duties |
| Journals that differ from the schedules | Journals reviewed, approved and locked before posting, plus a report that agrees the subledger to the GL |
| No evidence of who changed what | An audit trail on every modification and user action |
| One person holds the model | Controlled access for several users, so the process doesn't live in one workbook |
Here's a worked example you can copy. The table below is illustrative, for a fictional UK corporate group. It isn't LOIS customer data, and every figure is an assumption for you to swap for your own. Amounts are in pounds sterling (GBP).
| Line | Calculation | Annual amount |
|---|---|---|
| Baseline: cost of manual lease accounting today | ||
| 1. Close effort | 150 hours × 12 × £70 | £126,000 |
| 2. Audit support (your team) | 200 hours × £70 | £14,000 |
| Measured time baseline | 126,000 + 14,000 | £140,000 |
| Benefit: capacity released | ||
| Hours released | 40% × £140,000 | £56,000 |
| Costs to set against it (your own time) | ||
| Ongoing administration | 10 hours a month × 12 × £70 | £8,400 |
| Implementation and migration time | 240 hours × £70 ÷ 3 years | £5,600 |
| Vendor charges (placeholder) | Software plus any separately scoped implementation and migration fees, with one-offs spread over three years. Not a LOIS price | £20,000 |
| Result: net annual saving and ROI | ||
| Net annual saving | 56,000 minus 8,400 minus 5,600 minus 20,000 | £22,000 |
| ROI | 22,000 ÷ (8,400 + 5,600 + 20,000) | About 65% |
| Memo lines: exposure, not counted in the benefit | ||
| External audit fee for lease testing | From your engagement letter | £15,000 |
| Misstatement exposure | 10% likelihood × £45,000 per correction event | £4,500 |
| Control deficiency exposure | 10% likelihood × £40,000 remediation | £4,000 |
The £45,000 correction event is 150 internal hours (£10,500) plus £34,500 of external advisory and audit time. The £40,000 remediation is 200 internal hours (£14,000) plus £26,000 of external fees, including remediation testing.
Read the £22,000 net annual saving in the table as the value of released time. It becomes cash only if you avoid a contractor, overtime or a hire.
The £20,000 of vendor charges is a placeholder, so swap in your quote. Before vendor charges, the net benefit is £42,000 (£56,000 of released time, minus £8,400 of ongoing administration, minus £5,600 of implementation and migration time). A quote below that pays back on time alone. If your quote is higher, the case rests on the memo lines at the foot of the table (the audit fee, misstatement and control deficiency rows), and your paper should say so.
For your own numbers, the sum is annual benefit minus total annual cost, divided by total annual cost. Total cost is your vendor charges plus your own administration, implementation and migration time.
Set four costs against the savings, and ask every vendor to quote each one separately so nothing hides in a bundle:
LOIS pricing is quote-based because it depends on your portfolio, reporting entities, selected solutions and starting point. You can request indicative LOIS pricing without a demo. The response separates the ongoing software cost from any separately scoped implementation or migration costs, so each line drops straight into the table above.
Your costs rise faster than your lease count when leases span several entities, because each entity adds its own workbook, reviewer and reconciliation. Price the baseline entity by entity, starting with your three largest, then add them up. The hours hiding in a subsidiary's own file are the ones most likely to be missing from the group estimate. Acquisitions make it worse: a new company can bring a lot of leases across unfamiliar offices, all needing to reach the register.
FRS 102 adds its own load. The revised Section 20 applies to periods starting on or after 1 January 2026, so with a December balance date the first lease year ends in December 2026. Nearly every lease now goes on the balance sheet. The exemptions cover only short-term leases (under 12 months) and low-value assets, and FRS 102 lists vehicles, heavy machinery and property as not low value. Every entity then needs the same judgements on term, options and discount rate, documented the same way. That's the discipline that is hardest to hold across several workbooks.
Add another entity, and nobody holds the whole picture any more. An assumption drifts in one workbook, and you find out when the auditor does.
A source-based audit trail lets you walk from any reported lease balance back to the contract, the assumptions applied and the approvals behind it. If any of the three is missing, the number is an assertion rather than evidence, and the auditor's request comes back to your team as a task.
It matters more with each entity you add, because the person who remembers why a lease was set up a certain way is rarely sitting beside the auditor. The assumptions are the part teams forget to record: the term, the options assumed reasonably certain, the discount rate (the obtainable borrowing rate under FRS 102 where the lessor's rate isn't available) and the indexation basis, such as CPI or RPI.
Capture these once, at the lease, with who approved each change and when, and the audit support hours in your baseline stop being a hunt and become a retrieval. That's what audit-ready lease accounting means in practice: the evidence exists before anyone asks for it.
Picture the month-end after the move. LOIS has calculated interest, depreciation and remeasurements and generated the period journals. Your team reviews, approves and locks them, then exports them in the layout your ERP's journal upload expects, or retrieves them through the LOIS Managed API. A periodic report agrees the lease subledger to the GL balances. When the auditor asks about one lease, you open its record and the contract, the change history and the approval are all there.
Here's how that maps to the four areas of your baseline:
For corporate groups, LOIS supports multi-entity portfolios with consolidated reporting under FRS 102 Section 20. It also supports multi-currency and multi-country portfolios, and covers IFRS 16, AASB 16, NZ IFRS 16 and ASC 842 if part of your group reports under them. Support comes from CA-qualified lease accounting specialists. If you'd rather not carry the specialist workload yourself, the LOIS Managed Service has those specialists validate your lease data, run the calculations, prepare the journals and deliver monthly audit-ready reporting packs, while your finance team keeps review and approval.
If you're writing the paper itself rather than costing the process, our guide to building the business case for IFRS 16 and AASB 16 lease accounting software covers how to structure it for your CFO.
What is the ROI of corporate lease accounting software under FRS 102?
The ROI of corporate lease accounting software is its annual benefit, less total annual cost, divided by total annual cost. Benefit is built from hours released at close and in audit support. Cost includes subscription, implementation, data migration and ongoing administration. Avoided restatements and any audit fee change are upside, not part of the base case. In this guide's illustrative example, £56,000 of released time against £34,000 of total annual cost gives a net saving of £22,000, about 65%.
How do I calculate the cost of our manual lease accounting process?
Time two month-ends, then multiply hours per close by 12 and by a fully loaded hourly rate. Add your team's hours spent supporting the audit at the same rate. Record the external lease audit fee, expected misstatement cost and expected control deficiency cost as separate memo lines, so measured time stays distinct from estimated risk.
Will lease accounting software reduce our audit fee?
Not automatically. Auditors set their own fees and testing approach, so discuss what an audit trail and controls change with your auditor before you assume a lower fee. The part you control is your own team's time retrieving contracts, explaining calculations and resolving evidence requests. Count that, and treat any fee reduction as upside.
Can we count avoided restatements as savings?
No. An avoided restatement is a cost that never arrived, and nobody can prove it would have. Validation and review controls reduce the likelihood of misstatement, so show the expected exposure beside the ROI, with its assumptions visible, rather than inside the payback calculation.
What does LOIS cost?
LOIS pricing is quote-based and reflects your lease portfolio, reporting entities, selected solutions, starting point and implementation scope. You can request indicative pricing without a demo. The response identifies the ongoing software cost separately from any separately scoped implementation or migration costs, so each fits a line in your ROI table.
Does LOIS support FRS 102 across multiple entities?
Yes. LOIS supports FRS 102 Section 20 across multi-entity portfolios, with consolidated reporting capability and the associated security controls. It also supports multi-currency and multi-country portfolios, and covers IFRS 16, AASB 16, NZ IFRS 16 and ASC 842 for groups that report under them. Multiple charts of accounts and ledgers are supported for group structures.
Put your own numbers in the table
Request indicative LOIS pricing without a demo, then drop each line into your ROI table. Or talk to a LOIS specialist about a multi-entity portfolio and test the hours-released assumption against your own month-end.
Request indicative LOIS pricing Talk to a LOIS specialist