How to never miss a lease expiry: Automated alerts for Australian and NZ property portfolios
Under AASB 16 and NZ IFRS 16, a missed rent review isn't just a negotiation gap - it's a late remeasurement. Here's how automated milestone alerts fix that.
In 2024, a Queensland retail chain missed a rent review on three of its Brisbane stores. The property team knew the dates were coming; the finance team didn't. By the time the discrepancy surfaced, the AASB 16 remeasurement was six months overdue and the comparative figures needed attention. No one had made an error. The data existed. The problem was that the two teams were working in different systems, and the milestone never made it from one to the other.
This is the part that catches most property portfolios off guard: missing a rent review isn't just a missed negotiation window. Under AASB 16 and NZ IFRS 16, it's a missed compliance event. The balance sheet figures for every period between the effective date and the eventual remeasurement are wrong. If a reporting date falls in that gap, the comparative may need restating.
Updated August 2026.
What "missing a lease expiry" actually means under AASB 16 and NZ IFRS 16
Most organisations think of a missed lease expiry as a commercial problem: a landlord gains leverage, a negotiation window closes, a renewal gets confirmed on worse terms than it might have been. That's real, but it's the smaller part of the risk.
Under AASB 16 and NZ IFRS 16, a lease expiry (and the events that typically precede it) carries specific accounting consequences. A lease extension or exercise of a renewal option triggers a lease modification, which in turn requires the lessee to remeasure the lease liability using revised future lease payments, discounted at a revised incremental borrowing rate, and adjust the right-of-use asset accordingly. A rent review that changes the payment amount has the same effect. These aren't optional post-event tidy-up steps. They are required as at the effective date of the change.
When a milestone is missed, the remeasurement is late. Every period between the effective date and the eventual catch-up carries an incorrect lease liability and an incorrect ROU asset on the balance sheet. For organisations managing 50 or more property leases, those individual exposures stack up. The six areas where Australian and New Zealand auditors concentrate their IFRS 16 testing include modification remeasurements as one of the most consistently flagged issues; the root cause is usually a milestone that didn't reach finance in time.
The two kinds of lease milestone that matter
Take a rent review date. The property team needs it to open negotiations with the landlord. Finance needs it to process an AASB 16 remeasurement. Both teams are tracking the same date on the calendar, and often neither knows the other has acted on it until the discrepancy appears at month-end. That's because the date carries two distinct obligations, and most organisations are only set up to handle one of them.
Operational milestones belong to the property team: expiry dates, rent review triggers, option exercise windows, break clause deadlines. Every commercial property portfolio tracks these, even if it's in a spreadsheet. Missing them costs money and negotiating leverage.
Compliance milestones belong to finance: the remeasurement when a rent review takes effect, the lease modification entries when an option is exercised, the CPI adjustment that changes the payment stream. A property team that records an expiry in a spreadsheet but doesn't route it to the AASB 16 platform on time has handled the first obligation and created a problem with the second. The event is tracked, but the compliance response isn't.
Why calendar tools and residential property management software don't close this gap
The instinctive fix for missed milestones is a reminder system: a shared calendar, a property management tool with notification features, an alert on the lease register spreadsheet. These help property teams track commercial events. They don't solve the compliance problem.
A calendar reminder tells you that a rent review date is approaching. It doesn't connect that event to the AASB 16 calculation engine. When the property team acts on the reminder (negotiates a new rent, agrees an extension) there's still a manual step required to notify finance, who then have to open the AASB 16 platform, locate the lease, and process the remeasurement. The reminder closed the operational gap. The compliance gap is still open until someone acts on it.
Residential property management software adds a more fundamental problem: it was built for a different question. These tools manage tenancy law, rent schedules, and landlord-tenant workflows. They don't carry the concept of a lease liability, an ROU asset, or a remeasurement, because their users don't need those things. A reminder that fires inside a residential PM tool and stays there hasn't reached finance at all. It's tracked the operational event and stopped, exactly where the compliance risk begins.
- Missed negotiation window. The landlord sets the agenda before your property team has formally engaged. Commercial leverage is lost when the review has already passed its trigger date.
- Overdue remeasurement. Under AASB 16 and NZ IFRS 16, the lease liability and ROU asset must be remeasured at the effective date of the rent change. Every period before catch-up carries incorrect balance sheet figures.
- Potential comparative error. If a reporting date falls between the effective date and the eventual remeasurement, the prior period figures may need restating. That's an audit finding in the making, and it documents a process gap, not a judgement call.
For a portfolio of 50 or more property leases in Australia or New Zealand, with rent reviews spread across different calendar dates and different review structures (market, CPI, fixed), the cumulative probability of at least one milestone slipping through a manual tracking system approaches certainty over a three-year period. That's not a worst-case assumption; it's what the compliance self-assessment data from Australian and New Zealand organisations consistently shows.
How automated milestone alerts work in a unified lease platform
The distinction between a reminder in a standalone property tool and an alert in a unified lease platform is where the event goes when it fires.
In LOIS, every lease record carries its operational milestones: the rent review date, the expiry date, the option exercise window, the break clause trigger. Proactive alerts can fire at milestones, routed to the property team for actioning in the workflow to the finance team within the same platform. The property team gets enough lead time to prepare for negotiations. Finance gets enough lead time to prepare for the AASB 16 consequence, before the event becomes a late remeasurement.
The critical structural difference is that the alert and the AASB 16 calculation engine share the same underlying lease record. When a rent review fires, LOIS doesn't just remind you it's happening; it connects the event directly to the lease data that drives the remeasurement. Finance can action the AASB 16 calculations to update automatically once the new terms are confirmed, without re-entering data into a separate system and without waiting for the property team to send an email. The property-finance data sharing problem that causes most late remeasurements is solved at the architecture level, not by adding another notification layer on top of a disconnected system.
What the alert workflow looks like: from milestone to resolved remeasurement
Here is the five-step sequence from milestone alert to completed AASB 16 response in a unified platform.
Proactive alert fires
LOIS surfaces the upcoming rent review, expiry, or option window for both the property team and the finance team. The property team begins landlord negotiations. Finance is already aware of the likely compliance event before it happens.
Property team records the outcome in LOIS
Once terms are agreed, the property team records the new rent, the effective date, and any change to lease term directly in LOIS. No spreadsheet, no email to finance. The information is in the shared system the moment it's confirmed.
Finance receives a workflow notification
The lease event triggers a workflow notification to the finance team within LOIS. Finance can see what changed, confirm the effective date, and proceed to the AASB 16 remeasurement step, all within the same platform and the same lease record.
Finance actions the AASB 16 remeasurement
Finance can action the AASB 16 calculations to update automatically at the confirmed effective date: revised lease liability, updated ROU asset, remeasurement journal entries. The calculation uses the data already in the system: no rekeying, no separate model to update.
A single audit trail covers the full sequence
The alert, the property team's recorded outcome, the finance review, the remeasurement calculation, and the journal output all sit in one place. An auditor tracing a rent review through to its balance sheet impact can do so entirely within LOIS: no email chains, no cross-system reconstruction.
Compare this with the equivalent sequence when property and finance work in separate systems: a reminder fires in the property tool, someone emails or calls finance, finance opens the AASB 16 platform and re-enters the new terms, a remeasurement is processed with a different timestamp from the underlying event, and the audit trail is distributed across two systems and an email chain. That sequence works until it doesn't, and with 50+ leases, each with its own review cadence, it eventually doesn't.
What "never missing" costs to implement versus what missing one costs
The honest conversation about milestone management is a cost comparison, not a software pitch. The question is what the risk of a missed milestone actually costs, weighed against what a system that prevents it costs to run.
Consider a single missed rent review on a material commercial lease: say, $450,000 per annum for a distribution centre in Brisbane. The landlord anchors to a CPI escalation before your property team has engaged, and the new rent is set without negotiation. Six months later, when the remeasurement is finally processed, every balance sheet in the intervening period has shown the wrong lease liability and the wrong ROU asset. Finance has spent time with auditors explaining why. Comparative figures may need restating. And ASIC's expectations are clear enough that a process gap of this kind reads as a management failure in the audit file. That's a harder conversation than fixing the process.
Against that, a unified lease platform that keeps property and finance in the same system is a known, bounded cost. For portfolios between 30 and 10,000 leases (the range LOIS is built for), the question isn't whether automated milestone management pays for itself. For most organisations, a single avoided missed remeasurement on a material lease covers a meaningful share of annual system cost.
There's also the time cost to factor in. Finance teams managing property leases across separate systems from their property counterparts routinely spend two to four days per quarter reconciling the two data sets. That's not strategic work; it's error-finding. Bringing both teams into a single system, with automatic milestone alerts connected to the compliance engine, redirects that time to analysis and reporting rather than reconciliation. Our guide to property and finance lease collaboration covers the operational mechanics of how that shift works in practice.
For portfolios carrying CPI-linked leases, the compounding risk of manual tracking is particularly acute. CPI adjustments under AASB 16 require remeasurement when new payments take effect: not when CPI is announced, and not when the property team updates the rent schedule. Getting the timing right across a portfolio with different review dates, different CPI calculation methods, and different effective dates is very difficult in a manual system, and straightforwardly handled in a platform where the CPI mechanics are built into the calculation engine.
Frequently asked questions
Does a missed rent review always trigger an AASB 16 remeasurement obligation?
Under AASB 16 and NZ IFRS 16, a rent review that results in a change to future lease payments requires the lessee to remeasure the lease liability at the effective date of the new payments, using a revised discount rate if appropriate, and adjust the right-of-use asset accordingly. This applies whether the review produces a market-based increase, a CPI adjustment, or a fixed-step increase. A review that results in no change to the payment amount does not require remeasurement, but the absence of a change still needs to be documented. Missed reviews are a compliance risk precisely because they delay the remeasurement that the standard requires as at the effective date.
What lease milestones should an Australian or New Zealand commercial property portfolio be tracking?
For commercial property leases under AASB 16 and NZ IFRS 16, the key milestones include: lease expiry dates (with enough lead time to negotiate renewal or prepare for termination accounting); rent review dates for market, CPI, and fixed-step reviews; option exercise windows (options that are reasonably certain to be exercised affect the lease term and lease liability); break clause trigger dates; and any scheduled CPI adjustment dates written into the lease. Each of these is either a direct AASB 16 remeasurement trigger or a precursor to one. For most commercial property portfolios in Australia and New Zealand, tracking at least 180 days out is the standard to avoid reactive remeasurements.
Why doesn't a spreadsheet-based lease register with date reminders solve the milestone problem?
A spreadsheet reminder flags that a date is approaching. It doesn't connect that date to the AASB 16 calculation engine. When the property team acts on the reminder and agrees new terms, those terms still need to reach finance manually, usually via email or a data entry into the lease accounting system. That handoff is where milestones fall through: the property team acts, the email gets lost or delayed, and finance processes the remeasurement late. At portfolio scale, the cumulative risk of at least one handoff failing over a three-year period is very high. Spreadsheet reminders are also difficult to maintain as leases are modified, renewed, or terminated; the register goes stale and the reminders become unreliable. See our assessment of the cross-team communication risks in lease management for more on how this plays out in practice.
How does LOIS connect property milestone alerts to AASB 16 compliance in one platform?
LOIS Property Management surfaces automatic reminders for rent reviews, lease expiries, option windows, and other milestones at configurable lead times, routed to both property and finance teams in the same platform. When the property team records the outcome of a milestone event in LOIS, a workflow notification routes the change to finance, who can action the AASB 16 calculations to update automatically in the same system. The alert, the property event, the remeasurement, and the journal output all sit on the same lease record with a single audit trail. There's no separate email chain, no manual rekeying into a second system, and no gap between the commercial event and the compliance response.
How many leases do you need before manual milestone tracking becomes too risky?
LOIS works with Australian and New Zealand organisations from 30 leases upward, and the inflection point where manual tracking becomes genuinely high-risk sits around 50 property leases, at which point the combination of different review dates, different review structures (market, CPI, fixed), different option windows, and different AASB 16 modification types produces a volume of milestones that's difficult to manage reliably in a spreadsheet or standalone calendar tool, particularly as leases are modified and renewed over time. Organisations with fewer than 50 leases can often manage manually with discipline, but they typically still carry the handoff risk between property and finance that a unified platform removes.
Milestone alerts connected to the compliance engine
LOIS Property Management gives your property and finance teams automatic reminders for rent reviews, expiries, and other milestones, connected directly to the AASB 16 and NZ IFRS 16 calculation engine. See how it works in practice.
See property management See the LOIS platform