Lease Accounting

How to build the business case for enterprise lease accounting software

Baseline close hours, audit effort, misstatement risk and control costs, then weigh them against software costs. A guide for enterprise finance teams.


To build the business case for enterprise lease accounting software, baseline what lease accounting costs your group today across four areas: finance hours during close, audit effort and fees, misstatement and restatement exposure, and the cost of control deficiencies. Then compare the part of that baseline you can credibly reduce with subscription, implementation, data migration and ongoing administration costs.

In a multi-entity group, the gaps rarely look dramatic. One subsidiary closes a day late because its lease schedule lives in its own workbook. A modification signed in January reaches the group schedule in March. An auditor asks for the contract behind a remeasurement on a lease in another currency, and three people spend two days finding it. None of these is a crisis. Added up across entities and periods, they're a cost your CFO hasn't seen.

This guide is for CFOs, financial controllers and group reporting teams. It shows how to build that baseline, gives you an illustrative table to copy, lists the costs to set against it, and explains where LOIS lease accounting software supports each area.

One rule runs through the whole case: baseline what you can measure, discuss what you can't with the people who control it, and count only the savings you can name.

1. How much finance time does the lease close absorb?

The close absorbs the hours your team spends updating lease schedules, reviewing modifications, reconciling balances and preparing disclosures, multiplied by what those hours cost fully loaded. Measure it per entity for one real close, then total it. Estimating the whole group from a conversation produces a number nobody trusts.

Count four tasks:

  • Updating schedules: new leases, terminations, indexation and payment changes.
  • Reviewing modifications: checking the change, the discount rate and the remeasurement.
  • Reconciling balances: lease subledger to general ledger, entity by entity, including currency differences.
  • Preparing disclosures: maturity analyses, right-of-use (ROU) asset movements and the group notes.

A fully loaded hourly cost is total annual employment cost (salary, employer on-costs, benefits and an overhead allocation) divided by productive hours rather than contracted hours. Payroll or your finance business partner will have it. Include the controller's review time as well as the preparer's, because review is the easiest cost to leave out.

If nobody tracks time today, ask two or three entities to log their hours through one close. Pick entities that differ, say one property-heavy and one fleet-heavy, then extrapolate and say that's what you did.

In the illustrative baseline below, the group spends 150 hours a month across all entities. At AUD 100 an hour fully loaded, that's AUD 180,000 a year.

Be careful what you claim from it. Automation frees capacity, and capacity isn't cash until someone uses it. Say what the hours would buy: a shorter close, no year-end contractor, or a portfolio that grows without another hire. Your CFO will discount any hour with no named use, so give each one a use.

How LOIS supports the close

LOIS calculates interest and depreciation and generates the journals. Once a modification is entered, LOIS can action the remeasurement for review rather than your team rebuilding it in a workbook. Key terms are pulled automatically from lease PDFs, and bulk uploads use standardised templates. Periods open and close in alignment with your ERP.

If you'd rather not hold specialist processing in-house, LOIS Managed Service has CA-qualified specialists validate your lease data, run the calculations and prepare the journals, while your finance team keeps review and approval.

2. What does lease accounting add to your audit effort and fees?

Lease accounting adds audit cost in two places: the hours your own team spends retrieving contracts, explaining calculations and resolving evidence requests, and the fee your auditor charges to test the area. You control the first. Your auditor controls the second, so ask before you assume.

Start with last year's auditor request list. How many requests touched leases? How many needed a contract pulled from a shared drive or an email? How long did each take to close, and who answered it? That gives you internal hours you can price at the same loaded rate.

Then put three questions to your audit partner. Which parts of lease testing would change if calculations, approvals and modifications sat in a system with a change log? Would they test controls rather than reperform calculations? What would they need to see first? Put their answer in the paper as they give it, even when it's cautious. In the first year after a change, an auditor may do extra work to understand the new process, so a fee reduction isn't a given. Our guide to the compliance areas auditors focus on shows what they tend to ask for.

The illustrative baseline carries 300 internal hours (AUD 30,000) plus AUD 40,000 of lease-related audit fees. Treat the internal hours as the bankable part and the fee as upside to confirm.

LOIS keeps a full audit trail of every change, including modifications, month-end files and chart of account changes, with audit tracking of user access. Journals are reviewed, approved and locked before they reach your ERP, and a periodic report agrees the lease subledger to your GL balances. That puts the evidence your auditor asks for in one place. Whether it changes their fee is a conversation for them.

3. What is your misstatement and restatement exposure?

Misstatement exposure is the cost of lease errors reaching reported numbers. Document what has actually happened over the last two or three reporting periods, price those events, and keep any potential restatement as a stated exposure outside the payback total.

Keep a simple log with three headings:

  • Missed leases: which entity, how the lease was found, and how long after commencement.
  • Incorrect assumptions: lease term, extension options, discount rate or indexation, and which standard applied.
  • Late adjustments: post-close journals, hours to investigate, and who approved them.

Price what has already happened: the hours spent finding, correcting and re-approving. In the illustrative baseline, six late adjustments at 25 hours each come to AUD 15,000.

Avoided restatements are different, and this is where most business cases overreach. A restatement that never happens can't be booked as a saving. A probability multiplied by an assumed cost gives a figure nobody can defend in front of an audit committee. Describe the exposure in words instead: which events in your log could have been material in a different year, and what a restatement would involve in revised statements, audit work, management time and lender communication.

Then show how controls narrow it, without putting a dollar figure on the result. Look at how the errors in your log got in: a provider file loaded as it arrived, a rent review nobody flagged, a change one person made and nobody checked. Validation catches the first, reminders the second, review the third. LOIS Fleet Management cross-checks incoming provider records against your existing portfolio and flags new leases, price changes, CPI adjustments, extensions, scope reductions and terminations before they're applied. Milestone reminders prompt rent reviews and expiries so changes aren't found late, and dual approval workflows put a second person on lifecycle actions.

4. What does a control deficiency cost?

A control deficiency costs the time to investigate it, the external fees to redesign the control, and the remediation testing to show it now works. If your group has had one, price it from actuals. If it hasn't, map the gaps in your control matrix to the specific controls software would put in their place.

In the illustrative baseline, one deficiency over two years took 200 internal hours (AUD 20,000) and AUD 20,000 of external fees. That's AUD 40,000 over two years, or AUD 20,000 a year.

Connect each proposed control to a gap you can point to. The table shows the shape. Replace the left column with your own findings.

Gap in your process Control to test in software Evidence it leaves
Lease schedules sit in entity workbooks that anyone with the file can change One lease record per lease, with user access controls and audit tracking of modifications Change history by user and date
Modifications reach finance late, or not at all Milestone reminders for rent reviews and expiries, plus workflow between property and finance Dated approval record for each change
Journals prepared by hand and posted without independent review Journals reviewed, approved and locked before ERP posting, with segregation of duties Approver, date and locked journal file
Subledger to GL reconciled by hand each month Periodic report that agrees the lease subledger to GL balances Locked report for each period
Fleet and provider files loaded without checking against existing data Incoming records cross-checked against the portfolio before they're applied List of flagged changes reviewed before applying

If you haven't had a deficiency, put zero on that line and say so. The control gaps you can name are still worth describing, and the table is how you describe them.

What does an illustrative enterprise baseline look like?

Here's a baseline to copy. It's an illustrative example for a group with six entities, three currencies and around 1,500 leases, in AUD. Every figure is a placeholder, not LOIS data, a benchmark or a prediction of your result. Replace the inputs with your own.

Area Illustrative input Annual cost (AUD)
FTE hours during close 150 hours a month x AUD 100 loaded x 12 180,000
Audit effort and fees 300 internal hours x AUD 100, plus AUD 40,000 of lease-related fees 70,000
Misstatement events that happened 6 late adjustments x 25 hours x AUD 100 15,000
Control deficiency One deficiency in two years: AUD 40,000, averaged 20,000
Illustrative annual baseline Restatement exposure stated in words, outside the total 285,000

Illustrative only. The baseline is what lease accounting costs today, not what you'll save.

The total is the ceiling on what a project can touch. Your benefit is the share you can show you'll reduce: hours with a named use, audit effort your auditor agrees to change, and rework you can trace to a control. If it helps your CFO, present three columns: what you'd claim, what you'd expect, and what you've excluded.

Which costs do you set against the baseline?

Set four cost lines against the baseline: subscription, implementation, data migration and ongoing administration. LOIS pricing is quote-based and reflects your portfolio, reporting entities, selected solutions and starting point, so request indicative LOIS pricing using your real entity and lease counts.

  • Subscription: the recurring software cost, shaped by leases, entities and the solutions in scope (lease accounting, plus property or fleet if you want them).
  • Implementation: configuration, chart of accounts mapping, user set-up and training.
  • Data migration: inventory, template loading, opening-balance reconciliation and a parallel period. It draws on your people's time rather than a vendor invoice, so estimate it with care. Our guide to moving 1,000+ leases sets out the steps.
  • Ongoing administration: who owns the system, period close, user access, bulk uploads and ERP delivery. A managed service moves part of this to LOIS specialists.

LOIS connects to SAP, Oracle, Microsoft Dynamics 365, NetSuite and other ledgers through mapped journal exports or the LOIS Managed API. The integrations page explains the two routes, and the Managed API carries a setup component plus an ongoing managed service, so cost it as its own line.

Then do the sum your CFO will do: the reductions you can defend, less annual subscription and administration, less one-off costs spread over the period you choose. If the answer is close, say so. If it only works on a saving nobody has agreed, rework it.

Move to audit-ready lease accounting with confidence

As the portfolio grows, the hard part shifts from calculating leases to keeping track of what sits behind the numbers. Every entity adds contracts, every modification adds an assumption, and every period adds an approval. Your team needs to process changes without losing the thread from a figure in the group accounts to the contract, assumption and approval behind it.

Enterprise lease accounting software should combine automation with a source-based audit trail: a record, lease by lease, of what changed, who approved it and which standard applies. That record has to hold across entities, currencies and reporting standards. LOIS supports AASB 16, NZ IFRS 16, IFRS 16 and FRS 102, and ASC 842 too, across multi-entity, multi-currency, multi-country portfolios with consolidated reporting. Every change carries an audit trail, reassessments are tracked, and CA-qualified lease accountants stand behind the platform.

Building the case for a smaller or single-entity portfolio? Our guide to building the business case for IFRS 16 and AASB 16 lease accounting software covers that starting point.

Frequently asked questions

How do you build the business case for enterprise lease accounting software?

Baseline what lease accounting costs your group today across four areas: finance hours during close, audit effort and fees, misstatement and restatement exposure, and control deficiency costs. Then set the reductions you can defend against subscription, implementation, data migration and ongoing administration costs. Count only savings with a named use or an agreement behind them.

How do you estimate audit fee savings from lease accounting software?

Ask your auditor. Separate the internal hours your team spends retrieving contracts and answering evidence requests from the external fee, and discuss with your auditor which testing would change if calculations, approvals and modifications sat in a system with an audit trail. Don't assume a fee reduction, particularly in the first year after implementation.

Can you count avoided restatements as savings in a business case?

No. An avoided restatement is a reduced exposure, not a guaranteed saving. Price the errors that have already happened, such as missed leases and late adjustments, then describe the restatement exposure in words outside the payback total and show which validation and review controls address it.

What costs should you set against the savings?

Four: subscription, implementation, data migration and ongoing administration. Data migration and administration use your own team's time as well as vendor fees, so estimate them as carefully as the subscription. LOIS pricing is quote-based, and an indicative response separates the ongoing software cost from separately scoped implementation and migration.

Does LOIS support multi-entity, multi-currency groups reporting under several standards?

Yes. LOIS supports multi-entity, multi-currency and multi-country portfolios with consolidated reporting, and automates IFRS 16, AASB 16, NZ IFRS 16, FRS 102 and ASC 842. Every change carries a full audit trail, and group structures can use multiple charts of accounts and ledgers.

How much does enterprise lease accounting software cost?

Pricing depends on your lease portfolio, reporting entities and requirements, the solutions you select and your implementation scope. LOIS doesn't publish prices or packages. You can request indicative LOIS pricing without a demo, and the response explains what each cost covers and the assumptions behind it.

Put real numbers in your business case

Tell LOIS how many leases and reporting entities you have, and you'll get an indicative price that separates software from implementation and migration. For a complex group, speak to a LOIS specialist first.

Request indicative LOIS pricing Speak to a LOIS specialist

 

Similar posts

Stay ahead with LOIS insights

Subscribe to our blog for fresh ideas and practical resources from the LOIS team.