Inaccurate lease data in an audit can result in a modified audit opinion, financial restatement, ASIC regulatory scrutiny, director liability exposure, and material misstatements on the balance sheet. Under IFRS 16 and AASB 16, auditors are specifically trained to verify lease liabilities and right-of-use assets, and errors here are rarely missed.
Most organisations don't discover they have a lease data problem until an auditor points it out. By then the options are narrow: correct the financials, accept a modified opinion, or explain to the board why the numbers need to be restated. None of those are comfortable conversations. What follows is a clear-eyed look at what auditors actually find, what the consequences are, and what genuinely audit-ready lease data looks like in practice.
The short answer is: it depends on materiality. The longer answer is that even immaterial errors create audit friction that costs time and money, while material errors can set off a chain of consequences that extends well beyond the audit room.
Modified audit opinion. If lease errors are material and the organisation does not correct them, the auditor may issue a qualified, adverse, or disclaimer opinion depending on the severity and pervasiveness of the misstatement. A qualified opinion signals that the financial statements are reliable except for the identified issue. An adverse opinion means the financials are materially misstated and should not be relied upon. Either outcome damages credibility with lenders, investors, and regulators.
Financial restatement. If errors are discovered after financial statements have been lodged or distributed, the entity may be required to restate prior-period figures and re-issue those statements. Restatements are costly, time-consuming, and highly visible. They attract attention from analysts, lenders, and regulators in ways that routine audit adjustments do not.
ASIC financial reporting surveillance. ASIC's annual financial reporting and audit surveillance programme is risk-based. It targets entities where there are indicators that financial reports may contain material misstatements, including areas where errors have been flagged or where significant judgements are involved. Lease liabilities and right-of-use assets are significant balance sheet items at many organisations, and they are within ASIC's regular focus areas for review.
Director liability exposure. Directors are responsible for the accuracy of financial statements under the Corporations Act. Where financial statements contain material misstatements that directors knew about or should have known about, personal liability can arise. Inaccurate lease data is not merely an accounting inconvenience; it can become a governance matter.
Covenant breach risk. Many debt facilities include financial covenants that reference balance sheet ratios, particularly leverage ratios and net asset values. Because IFRS 16 brought lease liabilities onto the balance sheet, incorrect lease liability figures can distort those ratios. An organisation that believes it is comfortably within covenant limits may be in technical breach once lease errors are corrected.
Reputational damage. The downstream effects of an audit qualification or restatement tend to persist. Lenders may tighten credit terms. Investors may reassess risk. For listed entities, a restatement can move the share price. For private entities seeking financing, it can delay or derail a transaction. The reputational cost of a lease accounting failure is rarely proportionate to what seemed like a minor data issue at the time.
These figures illustrate the structural problem: the tools most organisations use for lease accounting are the same tools most likely to contain errors. The consequences, as the list above makes clear, are disproportionate to the effort it takes to get the data right in the first place.
Auditors reviewing IFRS 16 and AASB 16 workings test five distinct areas. Understanding what they are looking for is the first step toward making sure the answers are already in order before they arrive.
Completeness of the lease register. Auditors will not accept your register at face value. They look for evidence of a systematic process for identifying leases across the whole organisation, including embedded leases within service contracts, IT agreements, and outsourced arrangements. They will sample contracts outside the register to test whether anything has been missed.
Incremental borrowing rate documentation. The IBR applied at each lease commencement and at each modification must be documented, not merely applied. Auditors will test whether the rate is reasonable, whether it was determined at the correct date, and whether it was updated when a modification required remeasurement. "We used our bank's base rate" is not a sufficient answer.
Modification and reassessment evidence. Every change to a lease, whether a formal modification, a lease extension, a CPI adjustment, or a partial termination, must have supporting documentation. Auditors will trace each modification from the source document through to the financial statements. If your system cannot show this chain of evidence automatically, you will be reconstructing it from emails and memory under time pressure.
Reconciliation of journals to financial statements. Auditors will reconcile the ROU asset balance and the lease liability balance to the financial statements. Every movement during the year (additions, depreciation, interest, modifications, and terminations) must be supported and tied to individual lease calculations. This reconciliation should run every month, not be assembled for the first time at year-end.
Completeness of disclosures. IFRS 16 requires a maturity analysis of lease liabilities, a rollforward of ROU assets, and disclosure of total cash outflows related to leases. Auditors test each figure back to the underlying data. Organisations that assemble disclosures manually from multiple sources late in the reporting cycle face the highest risk of error and the most audit friction.
If any of these six items requires assembly from multiple sources when the auditor asks, the process is not audit-ready. The standard is not that you can produce these things eventually: it is that they exist continuously, updated as part of normal operations.
Lease data errors are almost never the result of someone getting the accounting wrong in principle. They are almost always process failures: the kind that accumulate quietly over months and only become visible under audit scrutiny.
Spreadsheet formula errors and version drift. Research consistently finds that 88% of spreadsheets used in business contain at least one error, with approximately 50% of financial models in operational use having material defects (F1F9, citing Panko, University of Hawaii). In lease accounting, a broken formula in an amortisation schedule, a hardcoded value that should reference another cell, or a copy-paste error from one year's file to the next can silently corrupt every figure that flows from it. The error is compounding and invisible until someone traces the calculation end-to-end.
Missing modifications. When a contracted lease extension is executed but no formal modification is processed in the accounting system, the lease data is wrong from that point forward. The ROU asset and lease liability are calculated on terms that no longer reflect the contract, and the error compounds with every subsequent calculation. Lease extensions are the most common trigger. They are often agreed informally between property and landlord contacts and never make it into the lease register.
Stale discount rates. The incremental borrowing rate must be updated at modification date for remeasurements that are not treated as separate leases. Organisations that set the IBR at commencement and never revisit it are carrying incorrect calculations for every lease that has been modified since. In a period of significant interest rate movement, such as the one Australia and New Zealand experienced between 2022 and 2024, the impact can be material.
No audit trail for changes. A spreadsheet shows the current state of a calculation. It does not record what changed, when it changed, or who authorised the change. When an auditor asks why the lease liability balance moved between quarters, "we updated the spreadsheet" is not a satisfactory answer. Without a system-enforced audit trail, every change to the lease data is effectively invisible.
"When an auditor asks why the lease liability balance moved between quarters, the answer cannot be: we updated the spreadsheet."
Audit-ready is not a state you achieve in the weeks before your audit. It is a standard you maintain continuously throughout the year. An audit-ready lease accounting function has four characteristics.
Organisations that meet these four standards spend substantially less time in fieldwork. Auditors can test by exception rather than reconstructing the entire lease accounting universe from scratch. The difference in audit cost and elapsed time is significant.
LOIS is built around the premise that audit-readiness is not a reporting feature: it is a by-product of how the system manages lease data every day. Several specific capabilities are directly relevant to the risks described above.
Full audit trail for every modification. Every change processed in LOIS, whether a rent review, a lease extension, a partial termination, or a change in scope, is recorded with timestamp, user, effective date, and the resulting recalculation. Auditors can trace any balance to its source without relying on anyone's memory or manual reconstructions.
Automated reconciliation. LOIS reconciles ROU asset and lease liability movements to the general ledger as part of normal processing. Month-end outputs are already in a form auditors can work with, not a starting point for further assembly.
CA-qualified expert review. For organisations using the LOIS Managed Service, a CA-qualified leasing accountant validates lease data, reviews IFRS 16 calculations, and delivers audit-ready reporting packs every month. This is a second set of expert eyes on the numbers before the auditor arrives, not after.
Audit-ready reporting packs. LOIS generates the disclosure workings, maturity analyses, and movement schedules that auditors require under IFRS 16. These are produced from the same underlying data that drives the journals, so there is no reconciling gap between what was posted and what was disclosed.
For organisations managing complex or growing lease portfolios, the gap between audit-ready and audit-friction is increasingly a system question, not a staffing one. Spreadsheets cannot provide the controls, history, or reconciliation that auditors now expect as standard.
If you are preparing for an upcoming audit, the IFRS 16 Audit Preparation Checklist covers the specific items auditors will request and how to have them ready before fieldwork begins.
Organisations that prefer to hand the monthly calculation and reconciliation work to a team of experts can explore the LOIS Managed Service: CA-qualified accountants who validate your data, run the numbers, and deliver audit-ready packs every month.
What are the consequences of inaccurate lease data during an audit?
Inaccurate lease data can result in a modified audit opinion (qualified or adverse), financial restatement, ASIC regulatory scrutiny, director liability under the Corporations Act, covenant breach on debt facilities, and lasting reputational damage. Under IFRS 16 and AASB 16, lease liabilities and right-of-use assets are material balance sheet items and are a specific focus of auditor testing.
What is a material misstatement in lease accounting?
A material misstatement is an error large enough that it would influence the decisions of a reasonable user of the financial statements. In lease accounting, materiality is assessed at the portfolio level. A single missed modification on a large property lease may be material on its own. A pattern of small errors across a fleet portfolio may be material in aggregate.
Can a lease accounting error trigger an ASIC review?
Yes. ASIC's financial reporting surveillance programme selects entities for review based on risk indicators, including areas where material misstatements have occurred or where significant judgements are concentrated. Lease accounting involves significant judgements (IBR determination, lease term assessment, modification accounting) and has been flagged as a focus area in ASIC's annual reporting reviews.
What is the ATO penalty for false or misleading financial statements?
Under the Taxation Administration Act 1953, the ATO can impose a base penalty amount (BPA) of 25% of the shortfall for failure to take reasonable care, up to 75% of the shortfall for deliberate or reckless conduct, based on the degree of culpability. For Significant Global Entities, these rates are doubled. Penalty rates are confirmed by the ATO's published guidance on false or misleading statements.
What does audit-ready lease accounting look like?
Audit-ready lease accounting means having a complete modification history, monthly GL reconciliation, source documents attached to each lease record, and a controlled calculation workflow, all maintained continuously, not assembled under pressure before fieldwork. The test is whether auditors can verify each balance without requesting additional reconstructions from the finance team.
Why are lease extensions a common source of audit errors?
Lease extensions are frequently agreed informally between property managers and landlords without a corresponding update to the lease accounting system. Under IFRS 16, an executed extension that changes the lease term is a modification event requiring remeasurement of the ROU asset and lease liability at the modification date using a current IBR. If this step is skipped, the balance sheet figures are wrong from the date of the unrecorded extension onward.
Updated April 2026. Penalty rates sourced from ATO.gov.au. Spreadsheet error data sourced from F1F9 / Panko (1998). Excel usage data sourced from IRIS Software Group 2025 survey.