How to share lease data between property and finance teams in Australia and New Zealand
Manual handoffs between property and finance teams create AASB 16 remeasurement errors, audit trail gaps, and months of reconciliation pain. Here is how a unified platform removes the handoff entirely.
Three days before every quarterly close, a finance manager at an Auckland retail group pulls up two spreadsheets: the property team's rent schedule and the AASB 16 model. They're never the same. The property team records rent increases when they negotiate them. Finance records them when the lease documents arrive, sometimes weeks later. By the time the balance sheet is signed off, both teams have been working from different figures for the same leases, and someone has spent three days reconciling a gap that shouldn't exist.
The handoff problem is structural. Under AASB 16 and NZ IFRS 16, the finance team's numbers govern the balance sheet, but the property team owns the underlying data. Until both teams are in the same system, the gap stays open.
Updated August 2026.
Why property and finance work from different versions of the same lease data
The divide isn't a communication failure. It's what happens when two teams with genuinely different jobs share responsibility for the same assets without sharing a system.
The property team's version of "current" is commercial: a rent review agreed in a phone call with the landlord last Tuesday, an option exercised before the deed of variation is drafted, a CPI clause that kicked in on the first of the month. They work lease by lease, in real time, driven by what's actually happening with each site.
The finance team's version of "current" is documentary: a signed variation, an invoice at the new rate, a formal CPI notification with a paper trail. They need entries auditors can trace, which means they can only work with what's been formally confirmed. A verbal agreement doesn't go on the balance sheet.
Both versions are correct for their purpose. The problem is that weeks can separate them, and during that gap the property system knows what's happening while the AASB 16 platform is still working from outdated terms. That gap is where month-end pain lives.
What the handoff failure looks like in practice
The specific failures follow a consistent pattern across Australian and New Zealand organisations managing property portfolios of 30 leases or more. Each one is a version of the same problem: a lease event that the property team knows about, recorded in a system or a spreadsheet that finance doesn't have access to in real time.
- Rent review recorded in the property system, not in the AASB 16 engine. The property team agrees a market rent review with the landlord. Finance finds out when the invoice arrives at the new rate, potentially one or two months later. Every AASB 16 schedule between those dates is wrong.
- Lease extension agreed verbally, notified by invoice. The property team exercises an option or agrees an informal extension. Finance doesn't know until the new-period invoice arrives. The AASB 16 lease term, liability, and ROU asset are all understated in the intervening period.
- CPI adjustment applied by the property system at the wrong date for AASB 16 purposes. Property records CPI from the effective date on the lease. Finance needs the remeasurement processed when the new payment amount first takes effect. If the systems are separate, the timing can differ, and the carrying value drifts.
- Lease termination flagged in a spreadsheet but never actioned in the AASB 16 platform. The property team records a termination or scope reduction. It doesn't make it to finance until the next reconciliation meeting. The lease liability continues to accrue on the balance sheet after it should have been derecognised.
Each of these failures has a common thread: the property team did their job correctly. The event was recorded. The problem isn't the recording; it's the handoff.
The compliance cost: late remeasurements and audit trail gaps
A rent review agreed by the property team is an AASB 16 remeasurement event under paragraph 45 of the standard, due at the effective date of the new rent, not when the invoice eventually confirms it. If finance doesn't know about the review until that invoice arrives, the remeasurement is already late. The balance sheet for the intervening period shows the wrong lease liability and the wrong ROU asset. If that period includes a reporting date, the comparative may be incorrect.
"We didn't know until the invoice arrived" is not a satisfying answer when your property team had the information weeks earlier. It describes a process gap, not a judgement call. Auditors examining AASB 16 compliance in 2026 have seen this pattern enough times to know it's a process question, not a complexity question. The six areas where Australian and New Zealand auditors focus their IFRS 16 testing include modification remeasurements as one of the most common sources of finding. Late notification from property to finance is frequently the root cause.
The audit trail problem compounds this. When property records the event in one system and finance processes it in another, the evidence file has two separate timestamps, two separate users, and no automatic link between the commercial event and the accounting entry. An auditor tracing a remeasurement back to its source has to cross two systems and rely on a manual handoff record (usually an email chain) to establish the connection. That is not an audit trail; it's a reconstruction.
The operational cost: reconciliation time, duplicate entry, and missed milestones
The compliance cost is visible in the audit. The operational cost is felt every month-end.
Finance teams managing property lease portfolios on separate systems from their property team routinely spend two to four days per quarter-end reconciling the two data sets. That's not analysis; it's error-finding. Every hour spent comparing a property spreadsheet to an AASB 16 model is an hour not spent on the financial commentary, the disclosure pack, or the things that actually require financial judgement.
There's also the missed milestones problem. Property teams managing critical dates (rent reviews, option exercise windows, lease expiries) are working in their system. Finance teams managing the same leases are working in theirs. When neither system is the authoritative source for both teams, reminders and alerts exist in two places, and the risk of a critical date slipping through increases with every lease added to the portfolio.
For a portfolio of 100 property leases in Australia or New Zealand, the cumulative operational cost of maintaining two separate systems is significant. Not just in reconciliation time, but in the management overhead of keeping both systems updated, the data quality risk of entries made in one system that aren't reflected in the other, and the ongoing risk of a material AASB 16 error from stale data. See our AASB 16 and NZ IFRS 16 compliance self-assessment guide for a practical framework to assess whether your current process has these gaps.
Integration versus unification: why connecting two systems rarely fixes the root problem
The instinctive response to the two-system problem is to integrate. Connect the property management system to the AASB 16 platform via an API or a periodic data feed, and data moves from one to the other without manual rekeying. It sounds like the fix, but the data quality problem travels with it.
Integration is only as good as the data quality in both systems. If the property team records a rent review in a field that doesn't map cleanly to the AASB 16 platform's modification logic, the data flows but the remeasurement doesn't trigger. If the integration runs nightly rather than in real time, the lag between the event and the accounting entry persists, just in automated form. If the property system records a lease extension as a note rather than a data field, it stays invisible to the integration.
More fundamentally, integration maintains two sources of truth. There is still a "property version" and a "finance version." Reconciling them is still a process you have to run, even if the automation reduces its frequency. When a discrepancy appears (and with two separate systems, discrepancies will appear), someone still has to go to both systems to find out which one is right.
CPI adjustments under AASB 16 illustrate the problem clearly. The correct timing for a CPI remeasurement is when the new payment amount first takes effect, not when CPI is announced and not when the property system updates the rent schedule. An integration that passes the new rent figure from a property system to an AASB 16 platform needs to pass it at exactly the right date, in exactly the right field, with the correct flag to trigger a remeasurement rather than a simple payment update. Getting that right across a diverse portfolio of leases with different CPI review dates requires both systems to have been designed to handle it the same way. That is a large assumption.
How a unified platform removes the handoff entirely
LOIS brings property management and AASB 16 lease accounting into a single platform. The property team records a lease event once. Finance can action the AASB 16 calculations to update automatically in the same system, without an email chain, without a data export, and without a reconciliation meeting.
The structural difference is the workflow. In a unified platform, a rent review isn't a piece of information that leaves the property system and travels to the AASB 16 engine. It's an event recorded in a shared system that both teams work in, with workflow and approval steps that route the event through the right process in the right sequence.
Property team records the event
The rent review, extension, CPI adjustment, or termination is recorded in LOIS by the property team as a lease event with the effective date and updated terms.
Finance receives an in-platform notification
The event triggers a workflow notification to the finance team within LOIS. No email, no spreadsheet export, no waiting for the invoice.
Finance reviews and actions the AASB 16 update
Finance can action the AASB 16 calculations to update automatically, generating the correct remeasurement entries, updated schedules, and journal outputs at the right effective date.
A single audit trail covers the full chain
The event recorded by the property team, the calculation actioned by finance, and the journal entry posted to the GL are all in one place. One timestamp, one system, one audit trail.
When both teams work in the same system, there is no handoff to fail. The data doesn't move between platforms; the property team's event and the finance team's AASB 16 response are connected by a workflow, not by an export file and a prayer that the field mapping holds.
LOIS also handles the operational side that keeps the portfolio running day to day: automatic reminders for rent reviews, option windows, and expiries; cost comparisons across sites; portfolio timelines. Because the property and AASB 16 lease accounting functions share the same underlying lease record, the milestones the property team tracks and the remeasurement events the finance team needs are driven from a single source. When a reminder fires, both teams see the same data, and neither has to wait for the other to send a spreadsheet.
For Australian and New Zealand organisations managing mixed portfolios of property, fleet, and equipment leases, LOIS handles all three in a single system. Property teams manage the property estate; finance teams handle the AASB 16 compliance across every asset class; fleet data can be batch-loaded from any provider. The handoff problem doesn't reappear for fleet leases or equipment leases because the architecture is the same: one system, both teams, built-in workflow. Our broader post on why property and finance teams need to collaborate on leasing covers the organisational dimension of this, including how shared KPIs and joint planning sessions support the technology change.
Frequently asked questions
Why does a rent review agreed by the property team create an AASB 16 compliance issue for finance?
Under AASB 16 and NZ IFRS 16, a change in lease payments resulting from a rent review is a remeasurement event. The lessee must recalculate the lease liability using the revised future payments and adjust the right-of-use asset accordingly. If finance doesn't know about the agreed rent review until the invoice arrives at the new rate, the remeasurement is processed late. The balance sheet for any period between the effective date and the processing date will show an incorrect lease liability and ROU asset. In a quarterly reporting context, that means a potentially incorrect comparative.
What's the difference between integrating two systems and using a unified platform?
Integration connects two separate systems so data passes between them. A unified platform is a single system that both teams work in. The practical difference is that integration maintains two sources of truth: discrepancies can still arise, the integration is only as accurate as the field mapping between the two systems, and reconciling differences still requires accessing both systems. A unified platform eliminates the handoff entirely. When property records an event, finance sees it in the same system and can action the AASB 16 response without any data movement or reconciliation step.
How does LOIS handle workflow and approvals between property and finance teams?
LOIS has workflow and approval steps built into the platform. When the property team records a lease event, the AASB 16 processing step is routed to the finance team within the same system. Finance can review the event, confirm the effective date, and action the AASB 16 calculations to update automatically. There are no email chains and no spreadsheet exports. The approval record is part of the audit trail alongside the event record and the calculation output, so the entire chain is traceable from a single system.
Does LOIS cover both property management and AASB 16 / NZ IFRS 16 compliance in one system?
Yes. LOIS is purpose-built for Australian and New Zealand organisations to manage lease accounting and property management in a single platform, backed by CA-qualified lease accounting experts. The property team uses LOIS to manage critical dates, rent reviews, cost comparisons, and portfolio timelines. The finance team uses the same platform to run AASB 16 and NZ IFRS 16 calculations, generate journal entries, reconcile the lease subledger to the GL, and produce audit-ready reporting packs. Fleet and equipment leases are also handled in LOIS, so the unified approach extends across the entire lease portfolio.
What does a single audit trail covering property and finance look like in LOIS?
In LOIS, the audit trail for a lease modification covers the full sequence in one place: the event recorded by the property team (with timestamp, effective date, and updated terms), the review and approval by the finance team, the AASB 16 remeasurement calculation (with before-and-after schedules), and the journal entry output. An auditor tracing a rent review through to its balance sheet impact can do so entirely within LOIS without needing to reconstruct the chain across email archives and two separate systems. That is the audit trail ASIC and the FMA expect to see, and it's what LOIS delivers as standard.
Put property and finance in one system
LOIS brings lease accounting, property management, and fleet in one platform for Australia and New Zealand. See how the workflow and approvals work in practice, or talk to a CA-qualified LOIS expert about your portfolio.
See property management See the LOIS platform