For Australian organisations with complex lease portfolios under AASB 16, purpose-built lease accounting software typically delivers better compliance outcomes and faster implementation than ERP lease modules. That said, the two approaches are not mutually exclusive. Many organisations use a dedicated lease platform that integrates directly with their ERP, getting the best of both worlds without replacing either.
The ERP-versus-specialist debate comes up constantly in conversations with finance teams across Australia. Usually it surfaces when an organisation is preparing for audit, switching ERP systems, or finally acknowledging that their current approach is not holding up to scrutiny. This guide explains how each approach actually works, where each one fits, and when a purpose-built platform is clearly the better choice.
ERP systems like SAP and Oracle were not originally built to handle lease accounting under IFRS 16 or AASB 16. The standard arrived in 2019, and ERP vendors responded by extending existing modules rather than building something from scratch. In SAP S/4HANA, for example, IFRS 16 compliance is handled through either the Flexible Real Estate module (RE-FX) for property leases or the Contract and Lease Management module (CLM) for moveable assets like vehicles and equipment.
Getting these modules to work for AASB 16 compliance requires significant configuration. Activating RE-FX involves mandatory enhancement packages, specific business function activations, and integration settings across SAP FI, CO, and AA. None of this is self-service. You will need specialist SAP consultants to implement it correctly, and you will need them again when requirements change.
The development priority problem is real. ERP vendors invest in general ledger functionality, procurement, and core financials. Lease-specific functionality, things like CPI adjustment handling, complex modification accounting, or asset-class-level discount rate management, tends to lag. The gap between what AASB 16 requires in practice and what an ERP module delivers out of the box is often wider than finance teams expect before go-live.
The result is that many organisations running lease accounting through their ERP find themselves filling the gaps with spreadsheets anyway, which defeats the purpose entirely. If your auditors are already asking questions about your lease workings, an ERP module configured four years ago and never revisited is unlikely to provide reassurance.
Purpose-built lease accounting platforms are designed from the ground up to handle IFRS 16 and AASB 16. Every feature, every workflow, and every report exists because lease accounting requires it. There is no configuration required to activate lease-specific logic because the entire platform is that logic.
LOIS is a purpose-built lease accounting and management platform developed and supported by CA-qualified lease accounting specialists. It automates right-of-use asset and lease liability calculations, processes every modification type under AASB 16, maintains a full timestamped audit trail for every change, and produces disclosure-ready reports aligned to Australian reporting requirements. It handles property, fleet, and IT leases in a single unified interface, removing the silos between finance and property teams that ERP modules typically do nothing to address.
Critically, it does not replace your ERP. LOIS connects to existing ERP systems via API or automated journal export, so lease journals flow directly into the general ledger each month without manual reconciliation or re-keying. Finance teams get specialised lease functionality and clean ERP integration in the same solution. The IT footprint is light and the implementation does not require an ERP project.
This approach also means the platform can be implemented quickly. Standardised upload templates, pre-configured AASB 16 workflows, and guided onboarding from CA-qualified accountants allow organisations to go live in weeks rather than months.
The table below reflects what organisations typically experience in practice, based on what LOIS's team of CA-qualified accountants see when working with Australian finance teams on AASB 16 compliance.
| Factor | ERP lease module (e.g. SAP RE-FX / CLM) | Purpose-built lease accounting software (e.g. LOIS) |
|---|---|---|
| Implementation time | Typically 3 to 12 months, depending on ERP version and portfolio complexity. Requires IT resources and SAP/Oracle consultants throughout. | Typically 4 to 12 weeks. Standardised templates and guided onboarding by leasing specialists reduce project risk. |
| Audit readiness | Audit trail quality depends on how well the module was configured. Manual steps and spreadsheet workarounds often introduce gaps. | Full timestamped audit trail generated automatically for every lease event. Audit-ready outputs by design, not by manual assembly. |
| Compliance depth (AASB 16 specifics) | Core calculations supported, but complex scenarios (CPI adjustments, partial terminations, mixed asset types) may require custom development or workarounds. | Built specifically for AASB 16 and IFRS 16. All modification types, discount rate strategies, and disclosure requirements handled natively. |
| Integration with ERP | Native to ERP ecosystem. Journal entries post directly, but multi-module dependencies can create reconciliation complexity. | Connects to any ERP via API or automated journal export. Journals flow automatically each month with no manual re-keying. |
| Cost to maintain | Ongoing IT and consultant costs for configuration updates, ERP version upgrades, and compliance changes. Per-seat licensing can be expensive for larger teams. | Lower IT dependency. Software updates are managed by the vendor. Typically priced per lease, not per seat, so team access is unrestricted. |
| Expert support | Support is IT-focused. Accounting standard questions typically require separate engagement with your auditors or an external accounting firm. | CA-qualified lease accounting specialists provide ongoing guidance. Support covers both system use and the accounting judgements behind it. |
| Flexibility for modifications | Modifications can require IT involvement to process correctly, especially for complex changes that require reclassification or separate lease treatment. | Modifications processed directly by the finance team within the platform. The system recalculates automatically and updates the audit trail in real time. |
ERP lease modules are a reasonable choice in specific circumstances. If your organisation is already deeply embedded in SAP or Oracle, has an active internal ERP team capable of managing ongoing configuration, and your lease portfolio is relatively straightforward with low modification frequency, the ERP route may work adequately.
Organisations that are mid-way through an SAP S/4HANA migration may also find it practical to activate the CLM or RE-FX lease module as part of that project, particularly if the migration budget already covers the required consulting hours. In these situations, the marginal cost of adding lease functionality within the existing ERP scope can be lower than implementing a separate system.
The honest limitation is that ERP lease modules serve the ERP vendor's broader roadmap, not the specific needs of Australian AASB 16 compliance. If your portfolio is growing, your modification volume is increasing, or your auditors are already raising concerns, an ERP module is unlikely to solve the problem.
For most Australian organisations, purpose-built lease accounting software delivers better outcomes across the factors that matter most: compliance depth, audit readiness, and ongoing maintainability without heavy IT involvement.
Dedicated software is clearly the better choice when:
A common concern finance teams raise is whether switching to a dedicated lease platform means disconnecting from their ERP. The answer is no. LOIS is designed to sit alongside your ERP, not replace it.
Each month, LOIS calculates all AASB 16 journal entries across your entire lease portfolio and delivers them directly into your general ledger via API or automated export. There is no manual reconciliation between the lease sub-ledger and the ERP. The journals arrive formatted to match your chart of accounts, and every entry traces back to the lease and modification that generated it. This gives your ERP a clean, complete, and auditable set of lease journals every reporting period, without requiring ERP-side configuration to produce them.
For finance teams already running SAP, Oracle, or another major ERP as their system of record, this model keeps the ERP doing what it does best, while LOIS handles every dimension of AASB 16 compliance that general-purpose ERP modules were not built for. See our related post on why lease accounting is now a data management problem for more on how these systems work together.
Can I use LOIS if my organisation already runs SAP?
Yes. LOIS integrates with SAP and other major ERP platforms via API or journal export. Many LOIS clients run SAP as their core financial system and use LOIS as their dedicated AASB 16 engine and Leasing Subledger, with journals flowing automatically into SAP each month. This avoids the complexity of configuring SAP RE-FX or CLM while still keeping the ERP as the system of record for financials.
Is ERP-based lease accounting compliant with AASB 16?
ERP lease modules can be made compliant with AASB 16, but compliance depends heavily on how well they were configured and whether they have been kept current with standard updates. The risk of gap-filling with spreadsheets or manual adjustments is higher in ERP implementations. Purpose-built platforms are designed with AASB 16 compliance as their primary function, which reduces the likelihood of configuration gaps creating audit exposure.
How long does a LOIS implementation take for an Australian organisation?
Most LOIS implementations for Australian organisations are completed within 4 to 12 weeks depending on portfolio size and data readiness. The onboarding process is guided by CA-qualified lease accounting specialists who work with your finance team to configure the system, validate your opening data, and ensure your AASB 16 calculations are correct from day one.
What does LOIS expert support include?
LOIS customers work with CA-qualified lease accounting specialists, not a generic software helpdesk. Support covers both system questions and accounting judgements: how to treat a particular modification, whether a contract contains an embedded lease, how to document IBR decisions, and how to prepare for external audit. LOIS also offers a managed service where experts run calculations, prepare journals, and deliver audit-ready monthly packs. Learn more about the LOIS managed service.
Does switching from an ERP module to LOIS require a complete data migration?
Yes, but the migration is typically less complex than organisations expect. LOIS uses standardised upload templates and provides migration support from its onboarding team. LOIS's CA-qualified team validates all data on import to ensure continuity of compliance from the transition date. For a full list of what to prepare, see the AASB 16 audit preparation checklist.
Updated April 2026. This comparison reflects AASB 16 and IFRS 16 requirements as currently in force for Australian reporting entities.