A rent review closes in March and nobody tells finance. The new rate turns up on an invoice in June, the lease liability has been wrong on two balance sheets, and the auditor wants to know why the lease register and the general ledger don't agree. That happens without anyone doing their job badly, because property and finance are working from two versions of the same lease.
This guide is for corporate occupiers: organisations that lease the premises, vehicles and equipment they use, and account for them under AASB 16 in Australia or NZ IFRS 16 in New Zealand. It's about bringing property's lease events and finance's lease accounting into one record. It isn't about landlord tenancy operations, rent collection or trust accounting, which is a different job for a different kind of software. If you want one system where your property team and finance team work from the same lease data (what we call a total tenant lease platform), LOIS was built for exactly that. What follows explains why the split happens, what it costs, and how to close it in six steps.
Finance and property teams end up with different lease data because each team records the same lease in its own system, on its own timetable. Property logs events when they happen; finance books them at month-end. LOIS closes that gap by giving both teams one lease record, so a rent review entered by property is the figure finance calculates from.
The divide is structural rather than a communication problem. Both teams are doing their jobs correctly, with different tools, different definitions of urgency, and different timelines.
Finance teams are organised around compliance cycles: IFRS 16 calculations, month-end close, audit deliverables. They need accurate amortisation schedules, journal entries, and disclosure reports. Their system of record is shaped by the audit calendar rather than by the lease event itself.
Property teams operate on the lease itself. A property manager tracks when the rent review window opens, whether the option notice period has been triggered, what the make-good obligations look like at a site coming up for expiry. These events are urgent the week they happen, and the end of the quarter is too late to hear about them.
The result: two teams managing the same asset from different systems, syncing via email, spreadsheet exports, and manual handoffs at month-end. Data diverges from the moment it enters two separate systems. By the time both teams realise it, a rent review has been missed, a modification has been processed in finance but not updated in property, or an auditor is asking why the numbers don't reconcile.
| What property sees | What finance sees |
|---|---|
| Upcoming rent review dates and negotiation windows | Current rental payment amounts in the amortisation schedule |
| Lease expiry and option exercise deadlines | Remaining lease term used for ROU asset depreciation |
| Negotiated rent changes and commercial terms | Remeasurement triggers requiring a new IFRS 16 calculation |
| Site cost comparisons and portfolio timelines | Right-of-use asset balances and lease liabilities on the balance sheet |
| Spreadsheet or property management system | Dedicated IFRS 16 tool or ERP module |
When these views live in separate systems, the data doesn't reconcile on its own. Someone, usually in finance, has to bridge the gap manually each month.
The cost of siloed lease data isn't abstract. It shows up in three specific places: the time lost to reconciliation, the errors that compound across manual handoffs, and the milestone misses that carry real financial consequences.
What finance teams told the 2025 market survey
In the 2025 Lease Accounting Software Market Survey, conducted by Kantar in March 2025 for Quadrent (the company behind LOIS) with 260 respondents from Australian and New Zealand businesses of 250 or more employees, 26% said they still ran IFRS 16 and AASB 16 compliance in Excel or other spreadsheets. The frustrations respondents raised included the complexity and time-consuming nature of manually tracking lease data across multiple contracts. Read the survey findings.
Data duplication is the first cost. When property enters a new lease into their system and finance enters the same lease into an IFRS 16 tool, you have two versions of truth from day one. Every modification, every extension, every rent review outcome has to travel between two systems, usually via email or a shared spreadsheet. Errors accumulate rather than cancelling out.
Missed milestones are the second cost, and the more dangerous one. Rent review windows, option exercise deadlines, and lease expiry dates are time-sensitive commercial decisions. A missed rent review at market could mean paying above-market rent for years. A missed option exercise could mean losing a critical site. A system that doesn't connect property's operational calendar to finance's compliance calendar will eventually miss something material.
Reconciliation overhead is the third cost. Finance managers who spend their month-end chasing property for aligned data aren't doing strategic work. Property managers who manually re-key data from an IFRS 16 system into their tracking sheet aren't managing the portfolio. Both teams are doing administration that one well-built system would remove.
A single source of truth for lease data is one lease record per lease that finance and property both work from, with defined roles for each team, workflow approvals at the handoff points, and an integration to the general ledger. In LOIS, property enters the event, finance reviews it, and the IFRS 16 calculation runs from that same record.
It isn't a spreadsheet that both teams can access, and it isn't a finance tool with a read-only portal bolted on for property. There's one lease record per lease, with a single point of data entry. Property inputs operational data: the lease terms, commercial events, rent review outcomes, and key dates. Finance works from that same record to run IFRS 16 calculations, generate journal entries, and produce audit-ready disclosures. When property updates a record, finance sees it immediately and can action for the IFRS 16 calculations to update. When a rent review concludes and the new rate is entered, the remeasurement is waiting for finance to review and apply instead of sitting in an email that hasn't been sent yet.
"One source of truth means property can't act without finance knowing, and finance can't calculate without property's data. That takes an architectural change, and no process fix gets you there."
The workflow layer is what makes this real. A unified platform connects property milestone notifications to finance approval workflows: a lease extension initiated in property triggers a review in finance before it's finalised. A modification can't be applied without crossing the workflow boundary between both teams. This structure enforces collaboration by design, rather than relying on teams to remember to tell each other. Our guide to how property and finance teams share lease data in Australia and New Zealand walks through those handoff points in detail.
The GL integration is the last piece. Automated synchronisation between the lease register and your general ledger means finance doesn't spend month-end manually reconciling what changed during the period. The LOIS lease accounting module prepares the journals from the current data, and the audit trail shows every change and who made it.
Centralisation is a data management project as much as a system selection project. Most organisations that fail at it select a platform before they've resolved the underlying data and workflow questions. These six steps address that in the right order.
Most centralisation projects that fail do so for one of three reasons, and all three are avoidable.
LOIS connects property and finance teams by holding every lease in one record that both teams work in. Property records rent reviews, expiries and options in the LOIS property management module; finance is notified within the same system, reviews the event, and can action for the IFRS 16 calculations to update, with every step captured in one audit trail.
LOIS is built for the tenant side of the lease. It doesn't do rent collection, tenant invoicing or trust accounting for landlords, and it isn't trying to. It manages the leases your organisation holds as an occupier, from the rent review through to the AASB 16 or NZ IFRS 16 balance sheet. The March rent review from the top of this article lands in finance's queue the day property records it, and the architecture described above is how LOIS works today.
On the property side, the LOIS property management module gives property teams automatic milestone reminders for rent reviews, expiries, and options; portfolio timelines showing the full calendar of upcoming events; cost comparisons by square metre; and workflow approvals that connect property actions to finance review before they're finalised.
On the finance side, those same property events feed the accounting workflows in the LOIS lease accounting module: finance is notified when payment amounts change and can action for the remeasurement to run, journal entries are generated from current data, and the full audit trail captures every modification with a timestamp and user record.
For organisations managing a high volume of leases, the LOIS Managed Service adds a layer of CA-qualified accountants who validate data, run the calculations, and deliver fully reconciled, audit-ready outputs each month. The system and the expertise operate from the same record, so there's no handoff between the managed service team and the platform.
LOIS handles portfolios from 30 leases to over 10,000, covering property assets valued at over AUD 50 billion. The platform scales with the portfolio, and the audit trail holds up under scrutiny because every change is captured with a timestamp and user record.
What is a single source of truth for lease management?
A single source of truth for lease management is one register where all lease data, both operational (terms, milestones, events) and financial (calculations, journals, disclosures), is stored and maintained in one system. In LOIS, finance and property teams read from and write to the same lease record, which removes reconciliation overhead and data drift between the two teams.
Is this the same as landlord property management software?
No. Landlord property management software runs tenancy operations for the owner or managing agent: rent collection, tenant invoicing, outgoings and trust accounting. LOIS is built for the corporate occupier, the organisation that holds the lease as a tenant and has to account for it under AASB 16 or NZ IFRS 16 while managing rent reviews, expiries and options across its own portfolio.
How do property and finance teams share lease data without stepping on each other?
Role-based access with workflow approvals. Property manages operational data (lease terms, rent review outcomes, expiry dates, milestones) and finance manages accounting data (IFRS 16 calculations, journal entries, disclosures). Workflow approvals define the handoff points so neither team overwrites the other's work. LOIS enforces these boundaries in the system itself rather than relying on convention.
Why doesn't an ERP work as the property team's lease register?
ERP systems are designed around the accounting workflow rather than property management. They won't send automatic milestone reminders, show portfolio timeline views, or support cost comparisons by square metre. Property teams given an ERP as their only tool will maintain a parallel spreadsheet, and the silo persists in a different form.
How long does it take to centralise lease data?
The timeline depends on data quality and the number of source systems. LOIS is designed for rapid onboarding using standardised upload templates, and most organisations can be fully operational within weeks. Running one parallel reporting period before cutover is recommended to surface any data gaps before go-live.