IFRS 16 turned lease accounting into a data problem disguised as an accounting problem. Every lease must be captured, classified, discounted, and remeasured as it unfolds, and the numbers change the moment a rent review lands, an extension option gets exercised, or a payment schedule is renegotiated. For most finance teams, the real bottleneck is not understanding the standard. It is the sheer volume of contract data that must be extracted, normalised, and fed into calculation models without errors creeping in.
Spreadsheets remain the default tool, and that is where the friction lives. A single lease modification can force a remeasurement of the liability, an adjustment to the right-of-use asset, and a revised amortisation schedule, all of which must reconcile to the general ledger. Multiply that across hundreds of leases in multiple currencies, and the close process becomes a manual reconciliation exercise that consumes days and still leaves auditors asking questions.
AI changes the economics of this work. Modern language models can read lease contracts, pull out the terms that drive the accounting, and generate the calculation logic, schedules, and disclosure inputs in a structured format. The finance professional stays in control of judgement and review, while the model handles extraction, drafting, and the repetitive arithmetic that eats up time. The result is a faster close, fewer errors, and an audit trail that is easier to defend.
Where AI Fits in the Lease Accounting Workflow
The most reliable pattern is to treat the model as a structured drafting and analysis engine, not as an oracle. You give it the contract, your accounting policy, and a clear specification of the output you need. It returns a lease data summary, a measurement schedule, and the journal entries, all in a format you can review and import.
The two prompts below follow that pattern. The first builds a complete IFRS 16 calculation pack for a single lease. The second handles the harder case: remeasurement after a modification. Both are written to be pasted into a Claude session alongside your own policy documents and lease files.
First, read these files completely before responding:
[lease_contract.md] — the full lease agreement including commencement date, term, payments, escalation clauses, renewal and purchase options, and any incentives
[ifrs16_policy.md] — our accounting policy, discount rate methodology, and materiality thresholds
[chart_of_accounts.md] — account codes and descriptions for right-of-use asset, lease liability, depreciation, and interest
Here is a reference for what I want to achieve:
[Upload reference file as markdown, or describe reference] — a prior lease working paper showing the layout, the schedule columns, and the journal entry format we use.
Here’s what makes this reference work:
It opens with a one-page lease summary, then shows the liability roll-forward month by month, then the right-of-use asset depreciation, then the journal entries. Every figure is traceable to a contract clause. Discount rate and key judgements are stated up front. Rounding is consistent and disclosed.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A structured working paper of roughly 800 to 1200 words plus tables, covering lease summary, key judgements, liability schedule, ROU asset schedule, and journal entries.
Recipient’s reaction: The controller should be able to review it in under fifteen minutes and sign off without chasing missing inputs.
Does NOT sound like: A textbook explanation of IFRS 16, or a generic template with placeholder logic.
Success means: Every number ties back to a contract clause or a stated assumption, and the schedules reconcile to the journal entries.
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
Notice how much of that prompt is about constraints rather than instructions. The model already knows IFRS 16. What it does not know is your discount rate policy, your account codes, and the layout your auditors expect. Supplying those turns a generic answer into a usable working paper.
The second prompt tackles remeasurement, which is where most spreadsheet models break. A modification changes the scope or consideration of a lease, and the accounting depends on whether it qualifies as a separate lease. Getting the model to reason through that test before it calculates anything is the key to a defensible answer.
First, read these files completely before responding:
[original_lease_working_paper.md] — the original measurement, including the liability roll-forward to the modification date and the remaining ROU asset balance
[modification_agreement.md] — the signed amendment showing what changed, the effective date, and any revised payment terms or term extension
[ifrs16_policy.md] — our policy on modification versus separate lease assessment and our revised discount rate approach
Here is a reference for what I want to achieve:
[Upload reference file as markdown, or describe reference] — a completed modification memo from a prior period showing how the separate lease test was documented and how the adjustment was presented.
Here’s what makes this reference work:
It states the separate lease test and the conclusion explicitly, shows the revised liability calculation, quantifies the ROU asset adjustment, and presents the journal entries with clear narration. Assumptions and the revised discount rate are justified in one short paragraph.
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A modification memo of roughly 600 to 900 words with supporting tables, including the separate lease assessment, revised measurement, adjustment calculation, and journal entries.
Recipient’s reaction: The auditor should accept the memo as sufficient documentation without requesting a follow-up schedule.
Does NOT sound like: A vague summary that skips the separate lease test or leaves the discount rate unexplained.
Success means: The revised liability and ROU asset reconcile to the prior working paper, and the journal entries balance.
My context file contains my standards, constraints, audience. Read it fully before starting.
DO NOT start executing yet. Ask clarifying questions first.
Give me your execution plan (5 steps max) before you begin.
The practical tip is to build a small library of these prompts, one for each recurring lease event: initial recognition, modification, index-based rent review, extension option exercise, and termination. Each one should reference the same policy and chart of accounts files so the outputs stay consistent across the portfolio.
Start with a single lease you already understand well. Run the first prompt, compare the output against your existing working paper, and refine the prompt until the model matches your standard. Once it does, you have a repeatable process that scales to the whole portfolio and gives your team back the days they currently spend on manual schedules.
Published on 13 October 2026 on growwithgpt.com