LOIS Leasing Blog

Building the business case for IFRS 16 and AASB 16 lease accounting software

Written by Stefan Iggo | Aug 04, 2026

The business case for IFRS 16 and AASB 16 lease accounting software rests on four quantifiable arguments: audit risk reduction, finance team time savings, the cost of a single material error in reported figures, and the risk premium that manual processes add to every audit engagement. For most organisations in Australia and New Zealand managing more than 50 leases, LOIS and comparable purpose-built platforms recover their cost within one financial year through time savings alone.

This guide is structured as a coaching resource for the finance manager preparing the paper, covering the cost of the status quo, how to quantify the benefit side, what software actually costs, and how to assemble the document. Updated June 2026.

Why the business case conversation keeps getting delayed

The business case for IFRS 16 and AASB 16 lease accounting software rarely fails on substance. It usually stalls because the person preparing it is the same person managing the spreadsheet, which creates a reluctance to surface how fragile the current process actually is. Most organisations reach the point of writing this paper after one of three triggering events: an audit where the lease working papers attracted significant testing time, a key staff member leaving (taking the model with them), or a portfolio that outgrew the spreadsheet and started generating reconciliation failures at close.

The delay is also partly structural. Compliance software doesn't generate revenue, so it competes for budget against projects that do. A CFO looking at a technology spend request needs to see a credible financial argument, not just a description of the problem. The nine warning signs covered in our lease management process liability guide are useful for establishing whether an investment case is warranted. This guide explains how to quantify it.

What a CFO wants to see in a technology business case
  1. The cost of doing nothing: expressed in hours, dollars, and risk exposure, not just "it's complicated."
  2. A credible payback period: derived from real inputs the CFO can sense-check, not optimistic assumptions.
  3. A risk-adjusted view: what is the expected cost if a material error surfaces in the next audit, and how likely is that under the current process?

The four components of the cost of your current process

LOIS's business case template structures the cost-of-status-quo analysis into four components. Each can be quantified with data your finance team already holds, and the template provides worked examples for portfolios of different sizes. The four components are:

1

Finance team hours: the largest and most recoverable cost

Manual AASB 16 and IFRS 16 processes consume 15 to 40 hours per month for portfolios of 50 to 200 leases. That range covers initial calculations, monthly remeasurements on modifications, GL reconciliations, and disclosure preparation. At a blended finance professional rate of AUD 80 per hour, the annual cost is AUD 14,400 to AUD 38,400 in staff time alone. This figure is conservative: it excludes the additional hours spent re-checking outputs before audit and responding to auditor queries. See our IFRS 16 month-end close guide for a breakdown of where time is typically lost.

2

External audit fees: manual controls cost more to test

Auditors charge more when the controls over a financial reporting area are manual. A lease accounting process built on spreadsheets requires the auditor to test the model itself, trace inputs to source documents, and reperform calculations to validate the outputs. Where purpose-built software with a full audit trail is in place, the auditor can test the system controls rather than every individual transaction. The incremental audit fee attributable to lease accounting testing can represent anywhere from AUD 5,000 to over AUD 30,000 per year depending on portfolio size and audit scope. Ask your audit engagement letter whether lease accounting is itemised in the fee breakdown, and if not, ask your auditor directly what they estimate the testing component costs.

3

Misstatement risk: a single error is not a small event

A material misstatement in AASB 16 or NZ IFRS 16 balances can require a financial restatement, trigger a qualified or modified audit opinion, and attract regulatory attention. ASIC's financial reporting surveillance programme identifies lease accounting as a recurring focus area, particularly completeness of the lease register and the accuracy of remeasurements following modifications. The direct cost of a restatement (revised financial statements, additional audit fees, and management time) rarely falls below AUD 50,000. The indirect cost, which includes damage to lender and investor relationships, is harder to put a number on but is real. Our guide to what happens when lease data is wrong in an audit covers this exposure in detail.

4

Key-person risk: if they leave, the model goes with them

Most spreadsheet-based AASB 16 models are built and maintained by one person. When that person leaves, the organisation loses not just the model but the institutional knowledge of how it was built, what assumptions it rests on, and where its known weaknesses are. Rebuilding from scratch typically takes one to three months and introduces the same calculation errors the original model was managing around. This risk is nearly impossible to mitigate with spreadsheets; it is eliminated when the process runs in a system with full documentation and team-level access.

The table below illustrates representative figures for a mid-market organisation managing 100 leases. The LOIS business case template includes this as an editable Excel version with input cells for your actual portfolio size, hours, and hourly rates.

Cost component Example assumption (100 leases) Annual cost estimate
Finance team time 25 hrs/month at AUD 80/hr AUD 24,000
Incremental audit testing cost Manual controls, estimated from auditor AUD 12,000
Misstatement risk (probability-weighted) 10% probability of material error, AUD 80,000 remediation cost AUD 8,000
Key-person risk (probability-weighted) 15% probability of staff turnover, AUD 40,000 rebuild cost AUD 6,000
Total annual cost of status quo AUD 50,000

These figures are illustrative. The LOIS business case template includes input cells calibrated to your actual portfolio size, team rate, and audit engagement structure.

Framing the benefit side of the equation

The benefit case for IFRS 16 and AASB 16 software has three components that translate directly into financial value: time returned to the finance team, risk eliminated from the reporting process, and a faster month-end close. LOIS quantifies these in its business case template against the cost of the status quo, giving the CFO a genuine comparison rather than a list of software features.

Time freed for strategic finance work. The hours recovered from manual IFRS 16 calculations and reconciliations are not marginal. For a finance manager spending two to three days per month on lease accounting administration, automation returns those days to higher-value work, whether that is financial modelling, business partnering, or simply closing the books on time. The gains compound: a faster, cleaner close means fewer late adjustments, fewer audit queries, and a more predictable reporting cycle across periods.

Elimination of restatement risk. When every AASB 16 calculation runs through a purpose-built system with a full audit trail, the risk of a material misstatement drops to near zero for process failures. The calculations are deterministic: the same inputs produce the same outputs, every time, and every change is logged. This is the argument CFOs find most compelling because the downside of a restatement is asymmetric. The cost of preventing it is a known, bounded number; the cost of experiencing it is not.

Faster month-end close. LOIS integrates directly with general ledger systems, producing journal entries ready for posting rather than requiring manual preparation. The reconciliation process between the lease subledger and the GL is automated: software with proper GL integration can produce a locked-down periodic report that agrees the lease subledger to the GL balances automatically, and thus avoiding a detailed reconciliation process. For detail on where manual processes create close overruns, see our IFRS 16 month-end close guide.

What purpose-built lease accounting software actually costs

IFRS 16 and AASB 16 lease accounting software is typically priced per portfolio or per number of leases, not per user. This pricing model matters for the business case because it means the cost scales predictably with portfolio size rather than headcount, and it is directly comparable to the per-lease-per-year cost of your current manual process.

For mid-market organisations managing 30 to 500 leases in Australia and New Zealand, annual software costs are generally less than the audit time saving in Year 1. For organisations at the higher end of that range, purpose-built software usually recovers its cost within six months when time savings and audit fee reductions are combined.

LOIS is priced for mid-market organisations, not just large enterprises. The platform scales from 30 to 10,000+ leases, includes CA-qualified expert support as part of the offering (not a paid add-on), and is designed for rapid onboarding from spreadsheets. For a comparison of what purpose-built software delivers versus an ERP module for the same cost, the lease accounting software evaluation guide covers the key criteria.

Download the LOIS business case template

The LOIS business case template is a pre-built Excel workbook that includes an editable cost-of-status-quo table covering all four components above, a payback calculator calibrated to your portfolio size and team rate, and a worked ROI output your CFO can review directly. It captures the structure described in this guide and takes about 30 minutes to complete with your own numbers.

Download the template

How to structure the business case document for your CFO

A CFO business case for compliance technology follows a standard structure. What distinguishes a paper that gets approved from one that gets deferred is the quality of the quantification in the first two sections. If the current-state cost table is populated with real numbers from your organisation, the investment decision is usually straightforward. Here is the section structure the LOIS business case template is built around:

1

Executive summary

One paragraph. State the current risk (manual process, key-person dependency, audit exposure), the proposed solution, the total investment, and the payback period. The CFO should understand the recommendation without reading further. If they need to read further to grasp the point, the summary is too long.

2

Current state cost table

The four-component table with your actual figures. This is the most important section. Use the LOIS template's pre-built table and replace the illustrative figures with your portfolio size, team rate, and audit fee data. Annotate the probability-weighted risk figures with your reasoning: an auditor who has raised modification queries in two of the last three years is not a 10% risk; they are closer to 60%.

3

Proposed investment and total cost of ownership

Annual software cost, implementation fee, and estimated internal time for onboarding. Be complete: include Year 1 and Year 2 costs so the paper is not vulnerable to a "what about next year?" question. LOIS can provide a pricing proposal for your portfolio size that feeds directly into this section.

4

Payback period and risk-adjusted NPV

The LOIS template calculates both automatically from your inputs. Payback period is straightforward: total investment divided by Year 1 savings. The risk-adjusted NPV incorporates the probability-weighted risk components, which typically strengthens the case significantly. If the payback is less than 12 months on time savings alone, state that clearly. CFOs who approve software investments frequently cite a sub-12-month payback as the threshold that makes the decision easy.

5

Recommendation

One paragraph restating the investment, the payback, and the risk being transferred. Name the vendor you are recommending and the rationale (compliance depth, expert support, fit with portfolio size). Identify the decision-maker, the implementation timeline, and the approval required. Close with a single action: approve or defer, with the consequence of deferral stated explicitly.

Frequently asked questions

What is the typical ROI of IFRS 16 and AASB 16 lease accounting software?

For organisations managing 50 to 200 leases, LOIS and comparable purpose-built platforms typically recover their cost in Year 1 through time savings alone. At 25 hours per month and AUD 80 per hour, time savings total AUD 24,000 annually. When incremental audit fee reductions of AUD 8,000 to AUD 15,000 are included, most mid-market organisations see a full payback within 6 to 12 months. Risk-adjusted NPV calculations that include the probability-weighted misstatement and key-person risk components push the return higher still.

How do I estimate the incremental audit cost attributable to lease accounting?

The most direct approach is to ask your audit engagement partner to estimate the hours spent on AASB 16 or IFRS 16 testing in the last audit, and apply the hourly rate in your engagement letter. If your auditor has raised queries about lease modifications, IBR documentation, or GL reconciliations in recent years, the testing component is likely higher than average. Some organisations negotiate a fee reduction with their auditor once a purpose-built system with controls testing is in place; this is worth raising explicitly as part of your business case conversation.

Does LOIS support both AASB 16 and NZ IFRS 16?

Yes. LOIS supports IFRS 16, AASB 16, and NZ IFRS 16, as well as FRS 102 and FASB ASC 842. The platform is used by organisations across Australia, New Zealand, and the UK. Calculations, disclosures, and journal outputs are generated for the applicable standard based on the entity's configuration, and the CA-qualified support team includes specialists in each of these standards.

What if my portfolio is relatively small: is the business case still valid?

The business case is strongest for portfolios above 50 leases, where the manual process overhead is significant. For portfolios of 30 to 50 leases, the financial case may be closer to neutral on time savings, but the risk case (audit exposure, key-person risk, restatement risk) remains fully applicable regardless of portfolio size. LOIS is designed for portfolios from 30 leases upward, and pricing at the lower end of that range reflects the scale involved.

What does ASIC say about AASB 16 compliance quality?

ASIC's financial reporting surveillance programme has identified lease accounting as a focus area in multiple reporting periods, with specific concerns around the completeness of lease registers, accuracy of modifications and remeasurements, and the quality of AASB 16 disclosures. LOIS addresses each of these areas directly: a centralised lease register, automated remeasurements on every modification, and disclosure outputs generated from the same data that drives the calculations. ASIC's findings are published on its website and provide useful external evidence for the risk section of a CFO business case, particularly for listed entities or those subject to regulatory oversight.

Build your business case with LOIS

Download the LOIS business case template to start building your own numbers, or talk to our team for a pricing proposal and worked ROI estimate specific to your portfolio size. Either way, you will have what you need for your CFO conversation.