IFRS 16 month-end close: why it takes so long (and how to fix it)
IFRS 16 month-end close takes days because of manual modifications, no GL integration, and spreadsheet chaos. Here is what slows it down and how to fix it.
Lease accounting month-end close takes so long because IFRS 16 requires recalculating amortisation schedules, reconciling lease liabilities, processing any modifications since last close, and generating GL journal entries. All of which are manual, error-prone, and interdependent when managed in spreadsheets. A properly configured lease accounting platform can reduce close time from days to hours. If your team is regularly spending three days or more on leases at month-end, this guide explains exactly where the time is going and how to reclaim it.
For a broader foundation, our complete guide to IFRS 16 and AASB 16 explains the standard's requirements in full. This post focuses specifically on the month-end operational challenge that trips up so many finance teams, and what genuinely fixes it.
What month-end close actually involves for a lease portfolio
Before diagnosing why close takes too long, it helps to be clear about what it actually involves. IFRS 16 and AASB 16 create a specific sequence of tasks that must be completed each reporting period, and each step depends on the previous one being correct.
Each step is dependent on the one before it. If step 2 is incomplete because a modification arrived late from the property team, steps 3 through 6 are all affected. This interdependency is the structural reason why spreadsheet-based close processes are so fragile: one missing input at the start ripples through everything downstream.
The five things that slow it down
When LOIS's CA-qualified specialists review lease accounting processes ahead of implementation, the same bottlenecks appear consistently. They're not exotic problems. Most are structural issues that accumulate slowly until the close window becomes unmanageable.
1. Manual modification tracking. Lease modifications (extensions, CPI adjustments, rent reviews, terminations) are notified to finance in whatever form they arrive: an email from the property manager, a signed addendum attached to a calendar invite, a note from operations. There is no central log. At close, the finance team has to chase all of these down, confirm what changed, determine the correct IFRS 16 treatment, and then process the modification manually. For a portfolio of 200 leases with even a handful of monthly modifications, this alone can consume a day of close time.
2. No general ledger integration. After running the lease calculations, someone has to manually key the resulting journal entries into the ERP. Depreciation on ROU assets, interest on lease liabilities, principal repayment splits: all entered line by line for every lease that moved during the period. This is not just slow. It is a significant source of posting errors, and those errors often aren't caught until the reconciliation step reveals that the subledger and GL don't agree.
3. No reconciliation controls. Without an automated link between the lease register and the GL, reconciliation is a manual exercise performed at the end of close. When the numbers don't tie (and they often don't), the team has to work backwards through every journal posted that period to find the discrepancy. This is the most time-consuming firefight in the entire process and it happens every single month.
4. Version-control chaos. A portfolio of any meaningful size, managed in spreadsheets, tends to accumulate files. There is the master file, a backup, the version sent to the auditors last year, a copy someone modified and didn't rename, and the current working version that three people have opened simultaneously. At close, determining which version is authoritative and whether all recent changes have been incorporated into it is a process in itself. For organisations managing 50 or more leases this way, version drift is not a hypothetical risk: it is a regular source of errors and wasted time. Our post on the nine signs your lease management process is becoming a liability covers this in more detail.
5. Single-person dependency. In most organisations managing IFRS 16 compliance in spreadsheets, one person built the model and one person truly understands it. Close cannot happen without them. If they are on leave, unavailable, or have left the organisation, the process stalls. This is key-person risk embedded directly into the month-end close cycle, and it is far more common than most finance leaders acknowledge until it creates a crisis.
In spreadsheet-based environments, each of these five issues compounds the others. Manual modification tracking makes reconciliation harder. No GL integration makes reconciliation take longer. Version-control chaos makes it impossible to be confident in the outputs. Together, they turn a process that should take a morning into one that consumes three or more working days, every single month.
What a fast month-end close looks like
Organisations that have moved from spreadsheets to a purpose-built lease accounting platform typically reduce their monthly close time by 60 to 80 percent. The benchmark LOIS teams see most often is a transition from three or more days to half a day or less. Not because the process has been compressed, but because the manual steps have been eliminated.
Here is what that looks like in practice.
- Chase modification notifications from property team
- Manually update amortisation schedules
- Key journal entries into ERP line by line
- Manually reconcile subledger to GL
- Investigate discrepancies one by one
- Manually compile disclosure data from multiple files
- Modifications captured via approval workflow before close
- Amortisation schedules recalculated automatically
- Journal entries generated and exported to GL in bulk
- Automated reconciliation confirms subledger ties to GL
- Discrepancies flagged before posting, not after
- Disclosure data assembled automatically from single source
The difference is not marginal. It is the difference between close being a multi-day scramble and a predictable, controlled process that your team can complete within a defined window every month.
Is your month-end close at risk? A self-diagnosis checklist
If you're unsure how exposed your current process is, these eight questions will tell you. Answer honestly: each 'yes' represents a genuine risk to your close timeline and the integrity of your IFRS 16 reporting.
| Question | If yes, the risk is... |
|---|---|
| Do you manage IFRS 16 calculations in spreadsheets? | Every modification requires manual recalculation, which multiplies close time and error risk. |
| Does your team manually key journal entries into the ERP? | Manual posting is slow and the most common source of GL mismatches. |
| Do you reconcile the lease subledger to the GL manually? | Manual reconciliation at month-end routinely surfaces discrepancies that require hours to trace. |
| Does lease modification information arrive ad hoc (email, phone call, attached document)? | Unstructured notification means modifications are missed or processed late, reopening prior-period work. |
| Is there one person who owns the lease model and without whom close cannot proceed? | Key-person dependency: if that person is unavailable, close stalls entirely. |
| Do you have multiple versions of your lease register in circulation? | Version drift means you cannot be confident you are reporting from the correct data. |
| Has month-end close ever been delayed because of a lease accounting issue? | Past delays are the strongest predictor of future ones. The process has already reached its limit. |
| Have auditors ever raised questions about the accuracy or completeness of your IFRS 16 data? | Audit queries on lease data indicate the current process cannot demonstrate a complete and reliable audit trail. |
Three or more 'yes' answers indicates a process that is structurally at risk. Five or more indicates a process that is likely to fail at scale or under audit pressure. See our guide on lease accounting software for more on what a controlled process looks like in practice.
How LOIS specifically reduces close time
LOIS is built around the operational realities of IFRS 16 month-end. Three specific capabilities account for most of the time saving.
Automated reconciliation and GL control. LOIS maintains a continuous link between the lease register and the general ledger. Every calculation is reconciled to the GL before journals are posted, not after. This means the reconciliation step at month-end is a confirmation, not an investigation. Teams that previously spent an entire day tracing reconciling items typically complete this step in under an hour.
Bulk journal export and ERP integration. Rather than keying entries one by one, LOIS generates a complete set of journals for the period: depreciation, interest, and principal splits across every lease. These are exported directly to the ERP in the format required, eliminating the manual posting step entirely. For portfolios with 100 or more leases, this single change typically saves two to four hours of close time per month.
Modification workflow with approval trail. Instead of modifications arriving as emails and informal notifications, LOIS routes them through a structured workflow. Property teams log changes, finance reviews and approves them, and the audit trail is captured automatically. By the time close begins, all modifications for the period are already recorded, classified, and approved. There is nothing to chase.
“Before LOIS, our IFRS 16 close took the better part of three days. We'd spend the first day chasing property for modification details, the second running calculations, and the third trying to reconcile to the GL. Now we run the whole process in a morning. The biggest change isn't speed, it's confidence: we know the numbers are right before we post.”
Finance Manager, ASX-listed retail group
For organisations with complex portfolios or those operating a managed service model, LOIS's team of CA-qualified accountants can also run the entire close process on your behalf. Our managed service explainer covers how that works and who it suits. You can also explore the broader question of how to choose the right lease accounting software for your organisation's size and complexity.
Frequently asked questions
How long should IFRS 16 month-end close take?
For a well-configured lease accounting platform, month-end close for a portfolio of 50 to 500 leases should take between two and four hours. Portfolios with higher modification volumes or complex asset types may take a full day. If your current process takes longer than one business day, the process has structural inefficiencies that are worth addressing. Three days or more is a reliable indicator that the underlying approach needs to change.
What causes delays in lease accounting close?
The five most common causes are: manual modification tracking with no central log, manual journal entry into the ERP after calculations are run, manual reconciliation of the lease subledger to the GL, version-control issues across multiple spreadsheet files, and single-person dependency on whoever built the model. These causes are cumulative: organisations with all five in place routinely spend three to five days on IFRS 16 close alone.
Can a lease accounting platform really reduce close time?
Yes, materially. The time saving comes from eliminating specific manual steps: automatic amortisation recalculation replaces manual schedule updates; GL integration replaces manual journal keying; automated reconciliation replaces end-of-close manual tie-outs; and structured modification workflows replace email-based notification. Each eliminated step reduces close time independently. Together, the typical reduction is 60 to 80 percent compared to a spreadsheet-based process.
Is AASB 16 month-end close the same as IFRS 16?
Operationally, yes. AASB 16 is the Australian equivalent of IFRS 16 and is substantially identical in its requirements. The same close sequence applies: process modifications, recalculate schedules, post journals, reconcile, prepare disclosures. The same bottlenecks apply too. Australian organisations preparing under AASB 16 face exactly the same month-end challenges, and the same solutions address them.
If your current process is showing any of the warning signs above, it is worth understanding what a controlled, automated close looks like. Talk to the LOIS team or explore our managed service for organisations that want the process handled end to end.