IFRS 2 is one of those standards that looks manageable on the surface and turns into a maze once you are actually inside it. Share-based payment arrangements require you to pin down grant-date fair value, select a valuation model, estimate expected life and volatility, account for non-market performance conditions, handle graded vesting, and then true-up cumulative expense every reporting date as forfeiture estimates change. Add modifications, cancellations, and replacements, and the probability of a calculation or disclosure error climbs fast. Most finance teams do not have a dedicated share-based payments specialist, so the work lands on controllers and analysts who touch IFRS 2 a handful of times a year.
The friction is rarely conceptual. Teams generally understand that expense is recognized over the vesting period. The pain is in the execution: rebuilding the expected-expense schedule each period, checking that the cumulative catch-up is computed correctly, drafting the disclosure note so it ties to the ledger, and answering the auditor’s questions about why the forfeiture assumption moved. These are structured, repeatable tasks — exactly the kind of work where a well-designed AI prompt saves hours and reduces rework.
ChatGPT will not replace your valuation specialist or sign off on a Black-Scholes input, and it should not. What it can do is act as a disciplined drafting and checking partner: build the expense schedule template, walk through the modification accounting logic step by step, pressure-test your forfeiture assumptions, and produce a first-draft disclosure note that you then review against the underlying data. The key is giving it the right structure and the right context files, which is what the prompts below are designed to do.
Where AI adds real leverage in IFRS 2 work
The highest-value use cases are the ones with clear rules and repetitive arithmetic: the grant-date to vesting-date expense roll-forward, the cumulative catch-up on a change in estimated forfeitures, the reclassification between equity and liability treatment when a modification changes the settlement mechanism, and the drafting of the movement table in the notes. These tasks are rule-bound, which means an AI can be held to the standard rather than asked to exercise judgment. Reserve human judgment for the inputs — expected volatility, expected life, and whether a performance condition is a market or non-market condition — and let the model handle the mechanics and the drafting.
One caution before you start: always feed the model your own accounting policy memo and the actual arrangement terms. Generic answers about IFRS 2 are easy to find; answers that reflect your graded vesting policy, your forfeiture estimation approach, and your specific tranche structure are what save time. The two prompts below are built around that principle.
First, read these files completely before responding:
[ifrs2_policy_memo.md] — our accounting policy for share-based payments, including graded vesting treatment and forfeiture estimation approach
[plan_rules.md] — the plan rules: tranche structure, vesting conditions, grant dates, and settlement terms
[prior_period_schedule.xlsx converted to markdown] — last period’s expense schedule with opening cumulative expense by tranche
Here is a reference for what I want to achieve:
[Upload last year’s audited IFRS 2 note and the supporting schedule as markdown]
Here’s what makes this reference work:
– Every tranche is shown separately with grant date, vesting date, number of options, grant-date fair value, and expected forfeiture rate
– Cumulative expense is calculated as options expected to vest multiplied by grant-date fair value, multiplied by the proportion of the vesting period elapsed
– The current-period charge is the difference between current cumulative expense and prior cumulative expense, with the forfeiture true-up shown as a separate line
– All figures tie to the trial balance and the note cross-references the schedule
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A markdown table schedule by tranche plus a short reconciliation paragraph, roughly 400 to 600 words
Recipient’s reaction: The controller should be able to review it in ten minutes and sign off without rebuilding the math
Does NOT sound like: A textbook explanation of IFRS 2 or a generic template with placeholder formulas
Success means: Every tranche reconciles from opening to closing cumulative expense with zero unexplained differences, and the schedule is audit-ready
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.
From mechanics to disclosure: drafting the note
Once the schedule is clean, the next bottleneck is the disclosure note. IFRS 2 requires a specific set of disclosures — the nature and extent of the arrangements, the weighted average fair value of options granted, how fair value was determined including the model and inputs, and a reconciliation of outstanding options from opening to closing. Auditors will test that the note ties to the schedule and that the narrative is consistent with the plan rules. Drafting this from scratch each year invites inconsistency and omissions.
The second prompt treats the disclosure as a structured drafting task with an explicit success brief. Note the emphasis on what the output should not sound like — this is what keeps the model from producing generic boilerplate that fails review. Feed it the prior year note, the current schedule, and the plan rules, and it will produce a draft that mirrors your house style while updating the numbers and reflecting any plan changes during the year.
First, read these files completely before responding:
[prior_year_ifrs2_note.md] — last year’s published note, which sets our house style and structure
[current_period_schedule.md] — the reconciled expense schedule by tranche for the current year
[plan_rules.md] — plan terms, any modifications or new grants during the year, and vesting conditions
Here is a reference for what I want to achieve:
[Upload the prior year note plus the auditor’s review comments as markdown]
Here’s what makes this reference work:
– Opens with a plain description of the arrangement and its terms before any numbers
– Presents the fair value inputs in a compact table with the valuation model named explicitly
– Includes the full reconciliation of outstanding options: opening, granted, forfeited, exercised, expired, closing
– Uses precise, neutral language and avoids promotional or vague phrasing
– Every number is traceable to the schedule and the narrative flags any modification during the year
Here’s what I need for my version / SUCCESS BRIEF:
Type of output + length: A complete draft note in markdown, approximately 500 to 700 words including tables
Recipient’s reaction: The auditor should read it and have no follow-up questions on completeness or consistency with the schedule
Does NOT sound like: Generic IFRS boilerplate copied from a template, or a note that omits the fair value input table
Success means: The note passes first-round auditor review with only minor wording comments and all figures tie to the schedule
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.
A practical tip: run both prompts in the same conversation so the model carries the schedule context into the note-drafting step, and keep your policy memo updated as your first context file — it is the single document that most improves output quality. Start with the roll-forward schedule for your largest plan, verify it against last period’s audited numbers, and only then move to the disclosure draft. Once the workflow is proven, extend it to your other arrangements and keep the prompts as standing templates for each reporting cycle.
Published on 15 November 2026 on growwithgpt.com
