What reports does IFRS 16 / FRS 102 lease accounting software produce?

IFRS 16 lease accounting software should generate seven core categories of output: journal entry reports, ROU asset movement schedules, lease liability movement schedules, amortisation schedules, financial statement disclosure notes, a cash flow statement split, and a timestamped audit trail. Most software vendors will show you dashboards and summary screens during a demo. What matters for a finance team is whether the system produces the specific reports that auditors will actually ask for. This guide explains exactly what those are, what each one must contain, and where spreadsheet-based approaches fall short.

Updated May 2026.

For context on the underlying standard, our complete guide to IFRS 16 and AASB 16 covers the compliance framework in full. This post focuses specifically on the reporting outputs a finance team should be able to produce every reporting period, and what to look for when evaluating software.

The seven core report types every IFRS 16 system should produce

These seven outputs represent the minimum reporting capability a compliant IFRS 16 or AASB 16 system should deliver. If a vendor cannot demonstrate all seven in a live environment, ask why before signing anything.

• Journal entry reports. The system should produce period-end journal entries ready to post to the general ledger: the initial recognition entry at commencement, the monthly depreciation charge on the ROU asset, the interest expense on the lease liability, the principal repayment split, and any remeasurement entries triggered by modifications. These should be exportable at the portfolio level and drillable to individual leases. A system that produces a calculation but requires manual rekeying into the ERP has not solved the problem.
• ROU asset movement schedule. This is the primary audit working paper for right-of-use assets. It must show, by asset class: opening carrying amount, additions from new leases, upward and downward remeasurements from modifications, depreciation charged in the period, impairment losses if any, disposals and terminations, and the closing carrying amount. The closing balance must reconcile to the asset balance in the financial statements. Auditors will ask for this by asset class (property, vehicles, equipment), not as a single lump sum.
• Lease liability movement schedule. The equivalent rollforward for the financial liability side: opening balance, new leases commenced in the period, interest accretion calculated at the effective interest rate, lease payments made, movements from modifications and reassessments, terminations, and the closing balance split between current (due within 12 months) and non-current. The interest accretion line is frequently omitted when this schedule is assembled manually, which is one of the most common disclosure deficiencies auditors flag under IFRS 16.
• Amortisation schedule. The underlying calculation engine for each individual lease: a period-by-period table showing the opening lease liability, the payment due, the interest component (at the incremental borrowing rate), the principal component, and the closing liability. This is the schedule that feeds every other output in the list. If the amortisation schedule for a lease is wrong, every report that draws from it is also wrong. Good software produces this per lease and aggregates it across the portfolio without any manual consolidation step.
• Disclosure notes. IFRS 16 paragraphs 51 to 60 specify the financial statement disclosures lessees must provide. A capable system should produce these as formatted, audit-ready outputs rather than leaving finance teams to assemble them from raw data. The key components are: the maturity analysis of undiscounted lease liabilities (in bands: under 1 year, 1 to 5 years, over 5 years), the weighted average lessee's incremental borrowing rate, the weighted average remaining lease term, total cash outflows for leases, and the breakdown of the depreciation charge and interest expense by asset class. For more detail on exactly what each paragraph requires, see the guide to IFRS 16 disclosure requirements for lessees.
• Cash flow statement split. Under IFRS 16 and IAS 7, lease-related cash flows must be classified correctly in the statement of cash flows. Principal repayments on lease liabilities are classified as financing activities. Interest paid is classified as either financing or operating activities per the entity's accounting policy (which must be applied consistently). Payments on short-term and low-value leases sit in operating activities. Software should produce a cash flow analysis report that shows each category clearly, so the person preparing the statement of cash flows can pull the figures directly rather than deriving them from the raw schedules.
• Audit trail and change log. This is not a financial report, but it is equally important at year-end. Every modification, reassessment, and user action should be timestamped and attributed to the person who made it, with a before-and-after record of the values changed. When auditors request evidence that lease data has not been altered without authorisation, this is what they are looking for. A system without a full, tamper-evident audit trail cannot provide the controls evidence that sophisticated audits require. See the IFRS 16 audit preparation checklist for a complete list of what auditors typically request.

What good reporting looks like in practice

Three specific questions separate software that produces reports from software that produces reports a finance team can rely on at month-end close and audit. Ask each of these in any vendor demo before shortlisting a system.

Can reports be exported to Excel and PDF? Auditors work in Excel. Finance directors want PDFs for the board pack. A system that can produce outputs only in its own interface forces manual re-entry or screenshot workflows, both of which introduce errors and waste time. Every report in the list above should be exportable in both formats with a single click.

Do reports reconcile back to the GL automatically? The most time-consuming part of IFRS 16 month-end close is not running the calculations: it is verifying that the outputs tie back to what was actually posted to the general ledger. 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. Manual reconciliation in spreadsheets across periods is one of the primary causes of close overruns. The full picture of why month-end takes so long is covered in the guide to IFRS 16 month-end close.

Can you drill down from a portfolio summary to a single lease? Summary-level reports are useful for disclosure, but they do not help when an auditor points to a specific line and asks where the number came from. A well-designed system lets you click through from the portfolio-level ROU asset movement schedule to the individual lease that drove a specific line item. Without that drill-down capability, investigating an anomaly means running a separate query, cross-referencing manually, and hoping the source data stays consistent, which in a spreadsheet environment it rarely does.

Reports specific to property management

Finance teams are not the only users of a lease platform. Property managers have reporting needs that are entirely distinct from the financial reporting stack above. In most organisations, these two functions run from separate systems, which creates duplicated data, missed milestones, disconnected workflows, and manual handoffs at the worst possible moments.

A platform that unifies finance and property reporting should produce three additional report types for property teams.

Reports specific to fleet management

Fleet and mobile equipment portfolios introduce a different reporting challenge: volume. An organisation with 500 vehicle leases may receive a bulk data file from its fleet provider every month. The two report types that matter most for fleet finance teams are not financial statements. They are data integrity reports that prevent errors from entering the financial reporting stack in the first place.

Bulk upload validation report. When a new data file is loaded, the system should produce a validation report showing which records were accepted, which were flagged, and why. This replaces the manual spot-checking that most fleet finance teams do after a bulk import, and surfaces data quality issues before they flow through to the financial reports.

Cross-check exception report. LOIS automatically cross-checks new data against existing portfolio records and identifies updates, new leases, price changes, CPI adjustments, extensions, scope reductions, and terminations, so the finance team reviews exceptions rather than auditing every record manually. The exception report shows the before-and-after for each identified change, making it straightforward to confirm, reject, or escalate each item before processing.

What spreadsheet-based reporting typically misses

Spreadsheets can approximate some of the reports above. Finance teams run amortisation schedules in Excel all the time. The three areas where spreadsheets consistently fall short are the maturity analysis, the cash flow split, and the audit trail.

The maturity analysis required by IFRS 16 must show undiscounted future lease payments in prescribed time bands. Assembling this from individual lease schedules across a large portfolio, particularly where leases have different payment frequencies, review mechanisms, and remaining terms, is genuinely difficult in a spreadsheet and extremely prone to error. The cash flow split requires correctly classifying principal versus interest versus short-term lease payments, which depends on accurate amortisation schedule data at the individual lease level. A single formula error in one lease propagates to the disclosure. The audit trail cannot be produced from a spreadsheet at all: there is no native mechanism to record who changed a cell, when, and what the previous value was.

The comparison below shows how each report type compares across the two approaches.

LOIS produces all seven core report types as standard outputs, with batch processing templates that allow finance teams to run a full suite of period-end reports without manual consolidation. For organisations reporting under AASB 16, the same reports apply: a system that produces compliant IFRS 16 reports will produce compliant AASB 16 reports using the same data and report formats.

Frequently asked questions

Does IFRS 16 software produce reports for AASB 16 as well?
Yes. AASB 16 is the Australian equivalent of IFRS 16 and is substantively identical in its recognition, measurement, and disclosure requirements. A system that produces compliant IFRS 16 reports will produce compliant AASB 16 reports using the same data and report formats. Finance teams in Australia should confirm that their software explicitly supports AASB 16 terminology and disclosure formats, not just the IFRS 16 equivalents.

What is the difference between an amortisation schedule and a lease liability movement schedule?
The amortisation schedule operates at the individual lease level: it is the period-by-period calculation of opening balance, payment, interest, principal, and closing balance for a single lease. The lease liability movement schedule operates at the portfolio level: it aggregates opening balances, additions, movements, and closings across all leases for a reporting period. Both are required, and one feeds the other.

How often should IFRS 16 reports be produced?
Most core financial reports (journal entries, movement schedules, amortisation schedules) are produced at each reporting period: monthly for management accounts and quarterly or annually for statutory purposes. The disclosure notes are produced at year-end. The audit trail is maintained continuously.