LOIS Leasing Blog

Moving 1,000+ leases to new lease accounting software

Written by Stefan Iggo | Nov 16, 2026

In July 2019, InfraBuild moved to IFRS 16 on a US-based lease accounting system that had no GL mapping. Journals came from a workaround: an Alteryx-built template, a lot of manual conversion, and seven finance business partners each running the process for their own business area before corporate pulled the results together. Month-end journals took four to five days. When the Alteryx setup hit technical problems, a finance team that isn't an IT team paid a Big 4 consultant to fix it.

After several years of that, the group, with 5,000 staff across Australia, Hong Kong, China, the USA and Poland, switched to LOIS and migrated 1,600 leases. The migration finished with very few reconciling differences and no material adjustments. Month-end now runs two to three days shorter.

If you're weighing a switch away from a system like InfraBuild's, the fear is usually the opening balances rather than the new software: day one in the new system showing numbers that don't agree to what the auditor signed off last year, with nobody able to say why. Reconciling those balances is a defined piece of work with a method. This guide sets that method out for a portfolio of roughly 1,000 to 2,000 leases under IFRS 16, AASB 16, FRS 102 or ASC 842, the four standards LOIS automates. See IFRS 16 lease accounting and FRS 102 lease accounting for how LOIS applies each one.

What does a large-portfolio lease migration involve?

Migrating 1,000 or more leases to LOIS involves five steps: extract and inventory every lease, map the data to standardised bulk upload templates, reconcile opening balances lease by lease, run one reporting period in parallel and agree the journals, then map the general ledger and go live. The reconciliation, more than the loading, decides how long the project takes.

Nobody has to trust the new system on faith. Every step ends with a number that agrees to something you already hold: a contract, last year's audited balance, the old system's journal file.

Step 1: Extract and inventory every lease

Start with a count, because everything later gets checked against it. How many leases does the old system hold, how many does the general ledger imply, and how many sit outside both? In a portfolio of 1,000-plus the third answer is rarely zero. A subsidiary keeps its own spreadsheet, a property team runs its own register, a fleet provider's portal holds the vehicles nobody loaded.

If you're switching vendors, the old system's export is the obvious starting file and also the first place data goes missing. An export contains what the old system's fields held. Anything the old model stored as free text, or in a field it used differently from the standard, comes out flattened or misplaced.

Waveconn shows why the inventory deserves its own step. The digital infrastructure business, which builds and owns cell phone towers, came out of a merger of two companies that were both exempt from IFRS 16. It was a first-time reporter, and its lease data hadn't been recorded in one place. The team reviewed files one by one and found nuances buried in text fields that couldn't be mapped automatically to LOIS fields. One was structural: advice from their Big 4 consultants was that five-year ground leases needed to mirror the 20-year master agreements on the towers above them, so the lease records had to extend beyond the contracted term. That kind of judgement lives in a file note, not in a column. Several rounds of sense-checking followed, an iterative approach agreed with the LOIS team upfront.

Find those leases in Step 1. Find them in Step 3 and they arrive as reconciling differences with no obvious cause.

What to capture for each lease
  • Identifier, counterparty and asset type
  • Commencement date, term, and any extension or break options assumed to be exercised
  • Payment amount, frequency and timing (advance or arrears)
  • Indexation basis: CPI, fixed increase or market review
  • The discount rate in use, and the date it was set
  • Modifications to date
  • Right-of-use (ROU) asset, lease liability and accumulated depreciation at the cut-over date

Carry each lease's existing discount rate across rather than re-deriving it. A new rate produces a new number, and you lose the ability to reconcile. Pick the cut-over date now as well, and make it a period end, because balances only mean something as at a date and everything you reconcile will be as at that date.

Step 2: Map the data to standardised bulk upload templates

One criticism of LOIS on Capterra is that the bulk upload templates can be fussy for complex portfolios, and the criticism is fair. The templates are strict because they have a job: a lease with a missing payment date or an ambiguous indexation basis shouldn't enter the subledger quietly. Across 1,000 mixed property, fleet and equipment leases, strictness costs time. Each rejected row is a lease to chase, and the chasing lands on whoever knows the contract rather than whoever knows the template.

Expert loading takes the friction out by splitting the work along the line of who knows what. Your team supplies the source data and answers questions about contracts. LOIS shapes the data to the template, loads the standard leases in volume, loads the complex ones directly, and reports back on what didn't reconcile.

At Waveconn, the LOIS team created the bulk upload templates and uploaded the more complex leases itself. At InfraBuild, Program Director Hayley Williams helped manipulate the data into the LOIS bulk lease upload template and then helped identify and rectify reconciling differences at the end. Neither finance team had to become template experts to get 1,200 and 1,600 leases in.

The template keeps paying back after go-live. InfraBuild uses LOIS bulk upload for new leases and modifications each month, which is one reason its month-end is shorter. Fleet provider files can take the same route through LOIS Fleet Management, which cross-checks each incoming record against the existing portfolio before anything is applied.

Step 3: Reconcile opening balances lease by lease

An opening-balance reconciliation compares, for every lease, the ROU asset, lease liability and accumulated depreciation the old system reports at the cut-over date with what the new system calculates from the same data. A reconciling difference is any lease where the two disagree by more than your agreed tolerance.

Do it lease by lease, because totals hide offsetting errors. One lease overstated by $4,000 and another understated by $4,000 give a perfect total and two wrong schedules. Differences tend to cluster around a short list of causes, so check these before anything exotic:

Source of difference What to check
Discount rate The rate carried across for each lease, and its precision. The old system may have rounded it.
Day count Whether interest accrues daily or monthly, and where each period starts.
Payment timing Advance versus arrears, and the first payment date.
Indexation Whether CPI or fixed increases were applied from the right date and at the right amount.
Modification history A modification the old system missed, or recorded as a new lease.
Term assumptions Extension and break options assumed reasonably certain, and when that was last reassessed.

Agree the tolerance with your auditor before you load anything, not after you've seen the differences. Rounding-level differences from precision and day-count conventions are expected and normally sit inside a small per-lease threshold. Anything above it gets a named owner and a written cause.

Occasionally a difference turns out to be the old system being wrong, and that's when a migration question becomes a restatement question. If a lease was miscalculated in periods you've already reported, you're dealing with a prior-period error under IAS 8 (AASB 108 in Australia, FRS 102 Section 10 in the UK and Ireland). A material error is corrected by restating comparatives; an immaterial one is normally corrected in the current period. That's a judgement for finance leadership and the auditor. It's also the reason to list every difference lease by lease with its cause beside it before anyone starts debating the treatment.

InfraBuild's 1,600 leases went through exactly this process, with LOIS's local team of chartered accountants on hand, and came out the other side with very few reconciling differences and no material adjustments.

Shirley You, Group Financial Reporting Manager, InfraBuild

"Program Director, Hayley Williams, did a great job helping us migrate 1600 leases to LOIS with minimal impact, supporting us promptly with any technical issues. Using her experience and expert lease accounting knowledge, she was also able to help us optimise our month-end process through LOIS."

Step 4: Run one period in parallel and agree the journals

A parallel run means closing the first period after cut-over in both systems from the same opening data, then comparing the journals line by line: interest, depreciation, new leases, modifications and terminations. Finance signs off when the new system's journal file agrees to the old one, or when every remaining difference has an explanation someone has accepted.

Two practical points. First, make sure the period includes at least one new lease and one modification, because those are the paths where systems tend to diverge, and a quiet month proves very little. Second, plan for it to be the hardest month-end of the project. Your team is running two processes at once, and the calendar sets the pace: nobody can close a period early. Keep the comparison output, because it's the evidence auditors will ask for when they want to know why the numbers can be trusted.

Step 5: Map the general ledger and go live

GL mapping is the capability InfraBuild's first system didn't have, and it's the step that removes the manual journal conversion that cost InfraBuild four to five days a month. LOIS holds a generic GL code for every lease event. You map those codes to your chart of accounts once, and multiple charts and ledgers are supported for group structures. Each period, journals are reviewed, approved and locked in LOIS, then exported in the layout your ERP's journal upload expects or retrieved through the LOIS Managed API. A periodic report agrees the lease subledger to the GL balances automatically. See LOIS ERP integrations for the systems covered and how the two routes differ.

Start the mapping early. It doesn't depend on the reconciliation, so it can run alongside Steps 2 and 3 and have journal exports ready when the parallel period begins. Go-live is the first period closed from LOIS alone. Archive the old system's final reports first, so auditors can trace any historical balance without needing access to a system you've retired.

How long does a 1,000+ lease migration take?

Ask any vendor for two separate figures: the time to load your data, and the time to full go-live. They're different numbers, and a quote that blends them hides the part you control. LOIS states that the platform can be set up within four weeks, and journal exports work as soon as your chart of accounts is mapped. That's a set-up figure. Loading, reconciling and parallel-running 1,000-plus leases depend on your data and your calendar. LOIS's own guidance for Australian implementations is 4 to 12 weeks, depending on portfolio size and data readiness.

The ranges below are planning figures for roughly 1,000 to 2,000 leases. They aren't a LOIS commitment, and your data readiness decides where you land inside them.

Step Indicative weeks What moves the range
1. Extract and inventory 1 to 3 How many systems and files hold leases, and how much detail sits in text fields
2. Map and load 2 to 3 Share of complex leases, and who loads them
3. Reconcile opening balances 2 to 3 Number of differences, and how quickly owners can explain them
4. Parallel run One period end (about 4) The calendar: you can't close a period early
5. Map the GL and go live 1 to 2 Number of ledgers and entities; start early, alongside Steps 2 and 3
Elapsed, with overlaps Roughly 8 to 12 The parallel run sets the floor

Last verified November 2026. The four-week set-up figure is as stated on the LOIS integrations page.

How do you migrate a decentralised lease portfolio?

Collect the data centrally, then give each business local access once the numbers reconcile. InfraBuild needed a system that could be implemented centrally but accessed on a decentralised basis across its global locations. Before the switch, seven finance business partners had each run the same journal process separately and corporate had stitched the results together.

The practical version is one owner for the template, one inventory and one chart-of-accounts mapping. Each business supplies source files by a fixed date, in a fixed form. If every subsidiary loads its own leases, you end up reconciling seven interpretations of the same template. After reconciliation, give each business access scoped to its own entities, so they can see and maintain their leases without touching anyone else's. Our guide to centralising lease data across your organisation covers that first collection step in more detail.

First-time reporter or switching vendor: what changes?

The five steps stay the same. What changes is what you reconcile against, and where the surprises hide. A team switching vendors has an answer key: the old system's audited balances. A first-time reporter has to build the answer from contracts.

Question Switching vendor First-time reporter
Where's the data? In the old system, plus side files for leases it never held In contracts, spreadsheets and property registers, often not in one place
What do you reconcile to? The old system's balances at the cut-over date The contracts and your transition calculation; there's no earlier number to agree to
Biggest risk The old system's errors carried across as fact Lease nuances buried in text fields and missed
Parallel run Old system against new, journal against journal Often nothing to run against, so reviewers recalculate a sample independently
Month-end process Exists already; you're replacing steps Built from scratch alongside the migration
Auditor conversation Why numbers moved against the old system How the starting position was established

The auditor row mattered most to Waveconn's Head of Finance, Rahat Khan: getting the starting position right in the first set of financial statements, and being able to explain it to auditors. His summary of what helped: "The ability to work super close with the team at LOIS and have direct access to their lease accounting knowledge was most beneficial. They took the time to understand how we wanted our system set up and aligned to our internal process." The ongoing load is real too. Waveconn will review 20% of its 1,200 leases every year, so the process built during migration is the one it lives with. Our guide to moving a lease register off spreadsheets covers the first-time path in more depth.

Before you sign: five migration questions to ask any vendor
  1. What are your two figures, time to load our data and time to full go-live, and what does each assume about our data?
  2. Who loads our complex leases, us or you, and is that in the scope you've quoted?
  3. How do you reconcile opening balances lease by lease, and which report shows me every difference?
  4. Can we run one full period in parallel, and what will your team do during it?
  5. How do journals map to our chart of accounts across multiple ledgers, and can subsidiaries get local access to their own leases?

For the wider evaluation, including how to test the calculations themselves, use the lease accounting software evaluation checklist.

Frequently asked questions

How long does it take to migrate 1,000+ leases to a new lease accounting system?

Plan on roughly 8 to 12 weeks elapsed for 1,000 to 2,000 leases. Data readiness and the calendar set that figure more than the software does. LOIS states the platform can be set up within four weeks; loading, reconciling and one parallel period-end take the rest, and the parallel run can't be shortened.

Can we switch lease accounting systems part-way through the financial year?

Yes. Switching systems isn't a change in accounting policy as long as the calculation approach stays the same, so there's no accounting reason to wait for year-end. Pick a period end as the cut-over date, reconcile opening balances as at that date, and run the next period in parallel. Check the timing with your auditor first.

What should we look for in an alternative to our current lease accounting software?

Look for the failures your current system causes at month-end. InfraBuild's previous system had no GL mapping, so its journals took four to five days of manual work each month. Look for GL mapping and journal export, an audit trail on every modification, a lease-by-lease reconciliation report, and a vendor team that will help migrate your data.

What happens if our old system's balances turn out to be wrong?

Treat it as a prior-period error question rather than a migration problem. Under IAS 8 and its local equivalents, such as AASB 108 in Australia, a material error is corrected by restating comparatives, while an immaterial one is normally corrected in the current period. Document each difference and its cause lease by lease, then agree the treatment with your auditor.

Will LOIS load our lease data for us?

LOIS provides standardised bulk upload templates and supports the data load. For Waveconn, a digital infrastructure business with 1,200 leases, LOIS created the templates and uploaded the more complex leases itself. For InfraBuild's 1,600 leases, a LOIS Program Director helped shape the data into the template. How much LOIS loads is agreed for each project, so ask for it to be written into the scope.

InfraBuild's month-end now runs two to three days shorter

LOIS migrated InfraBuild's 1,600 leases with very few reconciling differences and no material adjustments. The group now runs real-time IFRS 16 reporting whenever it needs it, and models future lease changes in the Sandpit add-on, which its previous system didn't offer.

Read the InfraBuild case study Book a demo