What did the IASB change about derecognition of a financial liability?

The Amendments to the Classification and Measurement of Financial Instruments confirm that a financial liability is derecognised on the settlement date, the date the obligation is discharged, cancelled, or expires. They also add an accounting policy election: a company may treat a financial liability paid in cash through an electronic payment system as discharged before the settlement date, but only when it has no practical ability to withdraw, stop, or cancel the payment instruction, no practical ability to access the cash, and settlement risk on that system is insignificant. The changes are effective for annual reporting periods beginning on or after 1 January 2026, with earlier application permitted.

Does the early derecognition election apply to every payment?

No. The election is only for financial liabilities settled in cash through an electronic payment system, and only when all three conditions are met. A company that elects it for one settlement through a given system must apply it to all settlements made through that same system, so the choice is by payment system rather than by transaction. A manual wire or a cheque, or a rail where the payment can still be recalled, falls back to derecognition on the settlement date.

How do the amendments treat a loan with an ESG-linked interest rate?

A financial asset whose interest rate changes on a contingent event that is not itself a basic lending risk, such as a borrower achieving a contractually specified reduction in carbon emissions, can still have contractual cash flows that are solely payments of principal and interest. That holds only when, in every contractually possible scenario, the cash flows would not be significantly different from those on an identical instrument without the contingent feature. A rate indexed to a variable that is not a basic lending risk or cost, such as a carbon price index, does not meet the test and would push the asset to fair value.

What new disclosures do the amendments to IFRS 7 require?

For financial assets and financial liabilities measured at amortised cost or fair value through other comprehensive income whose cash flows can change on a contingent event that does not relate directly to basic lending risks and costs, IFRS 7 now asks for a qualitative description of the nature of the contingent event, quantitative information about the possible changes to the cash flows such as a range, and the gross carrying amount of the financial assets and the amortised cost of the financial liabilities subject to those terms. There are also added disclosures for equity instruments designated at fair value through other comprehensive income.

When are the amendments effective and how are they applied?

The amendments are effective for annual reporting periods beginning on or after 1 January 2026, and earlier application is permitted. A company may early apply all the amendments together, or only the amendments to the classification of financial assets. The amendments are applied retrospectively in accordance with IAS 8, though a company is not required to restate prior periods and can instead recognise the effect as an adjustment to opening balances at the date of initial application.

Digital

Finance

Team

Why The Date Matters What Changed The Payment As DataPublished September 4, 2026

A payment can leave the books the moment you can no longer stop it.

The IASB gave IFRS 9 a clearer answer to a question every finance team meets: on what day does a paid liability leave the books. A financial liability is derecognised on the settlement date, and a new election lets a payable paid through an electronic payment system be discharged before then, once the company can no longer stop it, can no longer reach the cash, and settlement risk is slight. The same package cleans up how a loan with a contingent or carbon-linked rate is classified. It all takes effect for periods beginning on or after 1 January 2026.

Article signals

Audience: Controllers, financial reporting and technical accounting teams, treasury and accounts payable leads, and the finance systems people who own the payment run, the cash ledger, and the loan and receivable records under IFRS
Trigger: The IASB issued Amendments to the Classification and Measurement of Financial Instruments (Amendments to IFRS 9 and IFRS 7) in May 2024, effective for annual reporting periods beginning on or after 1 January 2026, with earlier application permitted
Published: September 4, 2026
Scope: Any company reporting under IFRS that settles payables in cash through electronic payment systems, and any holder of loans or receivables with contingent, ESG-linked, or non-recourse terms
The shift: A financial liability is derecognised on the settlement date, and a new accounting policy election lets a payable be treated as discharged before settlement when it is paid through an electronic payment system and three conditions are all met. The classification test for financial assets is clarified for contingent features, including a rate tied to a carbon emissions target
The artefact to build: A derecognition record per electronic payment: the payment system, the instruction status, the three election conditions checked as a set, and the date the liability and the cash leave the books, with a separate register of financial assets carrying contingent, ESG-linked, or non-recourse terms and the disclosures they now require

The day a payment leaves the books is now a rule, not a habit.

For a long time, the exact day a paid supplier invoice left the ledger was a matter of local practice. Some teams cleared the liability when the payment run was approved, some when the file went to the bank, some when the cash was reported as gone. IFRS 9 did not spell out a single answer for a liability settled by an electronic transfer, and that gap showed up as small, persistent differences between companies that were doing the same thing. The post-implementation review of IFRS 9 surfaced this, and in May 2024 the IASB issued the Amendments to the Classification and Measurement of Financial Instruments to close it.

The core of it is plain. A financial liability is derecognised on the settlement date, the date the obligation is discharged, cancelled, or expires. On top of that, the amendments add an accounting policy election for the common case of paying in cash through an electronic payment system. A company may treat the liability as discharged before the settlement date, but only once it has initiated an instruction that leaves it with no practical ability to withdraw, stop, or cancel the payment, no practical ability to access the cash, and settlement risk on that system that is insignificant. In other words, the liability can come off the books at the moment the company can no longer stop the money leaving.

The second half of the package is about the other side of the balance sheet. IFRS 9 decides whether a loan or receivable is held at amortised cost by asking whether its contractual cash flows are solely payments of principal and interest. Sustainability-linked lending made that question harder, because a rate that steps up or down when a borrower hits a carbon target is now common. The amendments clarify how to read those terms: a contingent feature whose trigger is not a basic lending risk can still pass the test, as long as the cash flows in every possible scenario would not be significantly different from a plain version of the same loan. A rate tied to something that is not a lending risk at all, such as a carbon price index, does not.

Read as a systems problem, all of this is welcome. It replaces a judgement re-argued each period with attributes a finance team can hold: the status of a payment instruction, the electronic payment system it runs on, and the contractual terms on a financial asset. Get those onto the record and the accounting reads from the payment and the contract rather than from memory. The rest of this piece walks through what the amendments say, then gets concrete about the record worth building before the 2026 effective date arrives.

What the amendments say, point by point.

The changes are narrow in scope and specific in wording. The table below sets out the ones that reach everyday finance, where each sits in IFRS 9 or IFRS 7, what it asks of the accounting, and what it should produce in the data a finance team owns.

The IFRS 9 and IFRS 7 amendments that reach everyday finance, with the paragraph behind each and what it should produce in a finance team's data. The paragraphs were read directly from the amendment text issued in May 2024.
What the amendment changes	Where it sits	What it asks of the accounting	What it produces in your data
Set the derecognition date for a payable	IFRS 9, B3.1.2A	A financial liability is derecognised on the settlement date, the date the obligation is discharged, cancelled, or expires, unless the company takes the electronic payment election below. The date the money actually settles is the date the liability leaves the books.	The settlement date held on the liability, so derecognition is tied to a real event rather than to when a payment file was cut or approved.
Elect to derecognise before settlement	IFRS 9, B3.3.8	For a payable settled in cash through an electronic payment system, the company may elect to treat the liability as discharged before the settlement date, but only when it has initiated an instruction that leaves it with no practical ability to withdraw, stop, or cancel the payment, no practical ability to access the cash, and settlement risk on that system is insignificant.	The three conditions captured as a set against each payment, so the earlier derecognition rests on a checked status rather than a habit.
Judge settlement risk once, per system	IFRS 9, B3.3.9	Settlement risk is insignificant when completing the instruction follows a standard administrative process and the gap between the conditions being met and the cash reaching the counterparty is short. It is not insignificant when completion still depends on the company being able to deliver the cash on the settlement date.	The electronic payment system recorded per payment, with the risk assessment made once for the system rather than argued again on each invoice.
Apply the election by system, not by payment	IFRS 9, B3.3.10	A company that elects the early derecognition option for one settlement through an electronic payment system applies it to all settlements made through that same system. The choice is by system, so the same rail is treated consistently.	The election held as an attribute of the payment system, so every payment on that rail follows one policy rather than a case by case call.
Read a contingent rate against the SPPI test	IFRS 9, B4.1.10A	A loan whose rate moves with a contingent event that is not itself a basic lending risk, such as a borrower hitting a contractually set carbon emissions reduction, can still be solely payments of principal and interest, but only when the cash flows in every possible scenario would not be significantly different from an identical loan without that feature.	The contingent term captured on the financial asset, with the scenario test recorded, so amortised cost classification is evidenced rather than asserted.
Disclose the contingent and ESG-linked terms	IFRS 7, 20B to 20D	For financial assets and liabilities at amortised cost or fair value through other comprehensive income whose cash flows can change on a contingent event unrelated to basic lending risks, disclose a description of the event, the range of possible changes to the cash flows, and the gross carrying amount subject to those terms.	A register of instruments carrying these terms, so the disclosure is a query over tagged records rather than a year-end hunt through contracts.

The IFRS 9 and IFRS 7 amendments that reach everyday finance, with the paragraph behind each and what it should produce in a finance team's data. The paragraphs were read directly from the amendment text issued in May 2024.

The through-line of the first four rows is the derecognition date. The default is the settlement date. The election shifts it earlier, to the moment the three conditions are met, and only for cash paid through an electronic payment system. The conditions are cumulative, which is the point worth holding on to: it is not enough that a payment feels final, the company has to be unable to stop it, unable to reach the cash, and running on a system whose settlement risk is slight. And the choice is made once for a whole system, not weighed payment by payment.

The last two rows are for companies that hold financial assets, especially lenders and any business carrying sustainability-linked loans or receivables. The classification test did not change in principle, but the amendments make the assessment of contingent and ESG-linked features far more concrete, and they add disclosures so a reader can see which instruments carry terms that could move the cash flows. Both halves point the same way: turn a term buried in a contract into an attribute you can assess, evidence, and disclose.

The payment, read as a governed record.

A worked example makes it concrete. Take a single supplier payment settled in cash through an electronic payment system. The payable stays open until the derecognition test is met. The payment instruction carries the system it runs on and the three conditions: whether the company can still withdraw, stop, or cancel it, whether it can still reach the cash, and whether settlement risk on that system is insignificant. The election is recorded as a policy that applies to every settlement on that system. When all three conditions are met, the liability and the cash come off on that day, with the instruction status kept as the evidence.

Here is that logic expressed as a record. Each payment carries its system, its instruction status against the three conditions, the election that governs it, and the date the liability and cash leave the books. A held list at the end names the payments the election does not reach, a rail where the payment can still be recalled, or a manual wire that is not an electronic payment system at all, because those fall back to settlement-date derecognition.

A derecognition record for a single electronic payment

# Derecognition record for a single electronic payment
# Figures and names are placeholders for shape, not real values.

payable:
  reference: "AP-2026-058124"
  supplier: "Kestrel Components Ltd"
  amount: 1875000
  currency: GBP
  ledger_status: open              # open until the derecognition test is met

payment_instruction:
  system: electronic_credit_scheme # the electronic payment system used
  initiated_on: 2026-01-14
  can_withdraw_stop_cancel: false  # B3.3.8(a): no practical ability to stop
  can_access_the_cash: false       # B3.3.8(b): cash no longer reachable
  settlement_risk: insignificant   # B3.3.8(c): standard process, short gap
  settlement_date: 2026-01-16

policy:
  election_applied: derecognise_before_settlement   # B3.3.8
  applies_to: all_settlements_on_this_system         # B3.3.10
  system_risk_assessed_on: 2026-01-02                # judged once, per system

derecognition:
  basis: election_before_settlement  # vs settlement_date without the election
  liability_removed_on: 2026-01-14   # the day all three conditions were met
  cash_removed_on: 2026-01-14
  evidence: instruction_status_snapshot

held:                                # payments the election does not reach
  - reference: "AP-2026-058140"
    system: recallable_transfer
    reason: sender_can_still_recall          # B3.3.8(a) not met
    treatment: derecognise_on_settlement_date
  - reference: "AP-2026-058151"
    system: manual_wire
    reason: not_an_electronic_payment_system # election out of scope
    treatment: derecognise_on_settlement_date

The held list is what keeps it honest. Holding the three conditions as a set means the earlier date rests on a checked status rather than on how quick the rail feels. Recording the electronic payment system, and judging its settlement risk once, keeps the scope of the election clear and stops it drifting onto a manual instruction. Keeping the election at the system level is what the standard requires, and it removes the temptation to treat two payments on the same rail differently. None of this is elaborate. It is ordinary payment discipline pointed at a question the amendments have finally answered.

A payable settled through an electronic payment system passes one combined test of three conditions: no ability to withdraw, stop, or cancel the instruction, no ability to access the cash, and insignificant settlement risk. If all three are met and the election is taken, the liability and the cash are derecognised before the settlement date. Otherwise, and where the rail is not an electronic payment system, the liability is derecognised on the settlement date. The election, once taken for a system, applies to every settlement on it.

An implementation checklist.

1.Set the derecognition date for a payable on purpose. The default under the amendments is the settlement date, the day the obligation is discharged, cancelled, or expires. Decide, and write down, whether you also take the election to derecognise a payable before settlement when it is paid through an electronic payment system, so the date a liability leaves the ledger is a policy rather than an accident of when a file was cut.
2.Make the three election conditions one check the payment has to pass. The election is available only when you have no practical ability to withdraw, stop, or cancel the instruction, no practical ability to access the cash, and settlement risk on the system is insignificant. Hold those three as a set captured against the payment, so early derecognition rests on a checked status rather than an assumption about how the rail behaves.
3.Record the electronic payment system on every payment, and assess its settlement risk once. Whether the gap between the conditions being met and the cash arriving is short, and whether completion follows a standard administrative process, is a property of the system, not of the invoice. Assess it once per system and store the result, so a payment inherits a judgement already made rather than reopening it each time.
4.Hold the election at the system level, because the standard requires it. If you elect early derecognition for one settlement through a system, you apply it to all settlements through that same system. Keep the election as an attribute of the rail so the policy is consistent by design, and a mix of early and settlement-date treatment on one system cannot creep in.
5.Tag financial assets that carry contingent, ESG-linked, or non-recourse terms, and record the scenario test. A rate that steps by a fixed amount if a borrower hits a carbon target can still be solely payments of principal and interest, while a rate indexed to a carbon price index is not. Capture the term on the asset and record the assessment that the cash flows would not be significantly different from an identical instrument without the feature, so the classification is evidenced.
6.Build the IFRS 7 disclosure as a query over tagged records. The disclosure asks for the nature of the contingent event, the range of possible changes to the cash flows, and the gross carrying amount subject to those terms. If the terms are tagged on the instruments as they are booked, the disclosure population is a query at close rather than a search through contracts in the last week of the year.
7.Run one completeness check before you rely on the new treatment. Any electronic payment derecognised before settlement where a condition was not actually met, and any contingent asset held at amortised cost without the scenario test recorded, is the exception list. It is far better found in a query than in an audit question, and while it has entries the policy is not yet safe to lean on.

Failure modes, framed so you can avoid them.

Derecognising a payable when the payment file is cut rather than when it settles or the election conditions are met. The amendments tie derecognition of a financial liability to the settlement date, or to the day all three election conditions are met, not to the day an approval was clicked. A liability removed too early leaves the cash and the obligation out of step with the accounting.
Taking the early election on a rail you can still recall. The first condition is that you have no practical ability to withdraw, stop, or cancel the instruction. On a system where a payment can be pulled back before it settles, that condition is not met, so the payable stays on the books until the settlement date whatever the timing feels like.
Applying the election to some payments on a system but not others. The standard requires that if you elect early derecognition for one settlement through a system, you apply it to every settlement through that same system. A mix of treatments on one rail is not a judgement call, it is an inconsistency the amendment specifically closes.
Treating the election as available for a manual wire or a cheque. The relief is for financial liabilities settled in cash through an electronic payment system. A manual instruction outside such a system, or a cheque that clears on its own timetable, falls back to settlement-date derecognition, and reaching for the election there is a misread of its scope.
Assuming any loan with an ESG-linked rate fails the classification test. A contingent feature whose event is not a basic lending risk, such as a carbon emissions target, does not by itself break solely payments of principal and interest. Where a fixed basis-point step is small enough that cash flows in every scenario are not significantly different from a plain loan, the asset can still sit at amortised cost.
Concluding that an ESG-linked rate always passes, without the scenario test. The mirror mistake. A rate indexed to a variable that is not a basic lending risk or cost, such as a carbon price index, gives cash flows that are not solely principal and interest. The feature has to be assessed, and the assessment recorded, rather than waved through because it is common in the market.
Leaving the new disclosure to a year-end scramble. The IFRS 7 additions ask for the nature of the contingent event, the range of possible cash flow changes, and the gross carrying amount subject to those terms. Tagging instruments as they are booked turns that into a query, while discovering the population at the year-end close turns it into a manual search under time pressure.
Retrofitting the policy by hand across a whole system at transition. The amendments are applied retrospectively, but the derecognition and election treatment is a policy set once and carried by the payment system. Reworking it payment by payment invites the very inconsistency the by-system rule was written to prevent.

What this asks of the data model.

The settlement date is a recorded event on the liability, not a memo. Derecognition of a financial liability is tied to the day the obligation is discharged, cancelled, or expires, so the settlement date belongs on the record and drives when the liability and the cash leave the books.
The three election conditions are a set, held together. No practical ability to withdraw, stop, or cancel the instruction, no practical ability to access the cash, and insignificant settlement risk are one combined test, and holding them as a set against each payment is what lets early derecognition rest on a checked status.
The electronic payment system is an attribute with its own risk assessment. Whether settlement risk on a rail is insignificant is a property of the system, judged once and stored, so a payment inherits that judgement rather than reopening it and so the scope of the election is clear.
The election lives at the system level for consistency. Because electing early derecognition for one settlement commits the company to it for all settlements through the same system, the election is an attribute of the rail, which keeps the policy consistent by construction.
Contingent and ESG-linked terms are governed fields on the financial asset. A rate that moves with a carbon target, or any contingent feature whose event is not a basic lending risk, is captured on the instrument together with the scenario test, so the classification into amortised cost or fair value is evidenced rather than argued each period.
Non-recourse and contractually linked features are flagged so the look-through is deliberate. Where a claim is limited to the cash flows of specified assets, or where tranches rank against a pool, the amendments ask for a look-through, and a flag on the instrument is what makes that assessment a step rather than a surprise.
The disclosure population is a query, not a search. Tagging the contingent, ESG-linked, and non-recourse terms as instruments are booked means the IFRS 7 disclosure of the event, the range of possible cash flow changes, and the gross carrying amount reads off tagged records at close.
Completeness reduces to one exception list. Any early derecognition where a condition was not met, and any contingent asset at amortised cost without a recorded scenario test, is a gap, and it can be run as a query before the treatment is relied on rather than surfacing in review.

The evidence to keep.

The written derecognition policy, stating that financial liabilities are derecognised on the settlement date and whether the electronic payment election is taken, so a reader can see the treatment was chosen rather than defaulted.
The per-payment condition snapshots for any liability derecognised before settlement, showing that the instruction could not be withdrawn, stopped, or cancelled, that the cash was no longer reachable, and that settlement risk was insignificant.
The per-system settlement risk assessment, showing that each electronic payment system was judged once against the standard administrative process and short delivery test, with who assessed it and when.
The derecognition register for electronic payments, showing the system, the basis, and the date the liability and the cash left the books, so the timing rests on evidence rather than on the day a file was cut.
The register of financial assets carrying contingent, ESG-linked, or non-recourse terms, with the scenario test recorded for each, evidencing why the asset sits at amortised cost or at fair value.
The IFRS 7 disclosure population, showing the instruments subject to the new disclosures, the nature of each contingent event, the range of possible cash flow changes, and the gross carrying amounts, drawn from the tagged records.
The completeness exception report, ideally empty, listing any early derecognition where a condition was not met and any contingent asset at amortised cost without a scenario test, so the two conditions were checked before the treatment was relied on.
The transition working, showing the amendments applied retrospectively and any adjustment to opening balances, so the first period under the amendments is traceable to the policy rather than to a payment by payment rework.

Questions worth asking in your own review.

Is our derecognition date for a payable set to the settlement date, and have we decided in writing whether we take the election to derecognise before settlement on an electronic payment system?
For any payable we derecognise before settlement, can we show that we could not withdraw, stop, or cancel the instruction, could not access the cash, and judged settlement risk on that system to be insignificant?
Have we assessed settlement risk once for each electronic payment system, and stored that assessment, rather than reopening it on every payment?
Do we apply the early derecognition election to every settlement through a given system, or has a mix of treatments crept onto one rail?
For loans or receivables with a contingent or ESG-linked rate, have we run and recorded the scenario test that decides whether they are still solely payments of principal and interest?
Can we produce the IFRS 7 disclosure, the nature of the event, the range of possible cash flow changes, and the gross carrying amount, as a query over tagged instruments rather than a search through contracts?
Have we flagged non-recourse and contractually linked instruments so the required look-through is a deliberate step at classification?
Could we run, today, a completeness list of any early derecognition missing a condition and any contingent asset at amortised cost without a recorded scenario test?

What this adds up to.

These amendments are a quiet, useful tidy-up. For accounts payable and the cash ledger, the win is a clear derecognition date: the settlement date by default, or the day you can no longer stop an electronic payment if you take the election. That removes an old ambiguity and lets the ledger match the moment the money truly leaves. For lenders and anyone holding sustainability-linked assets, the win is a concrete way to classify a contingent or carbon-linked rate, with disclosures that make the terms visible instead of buried.

The build that makes it work is small and durable. Decide the derecognition policy on purpose. Capture the three election conditions as one status against each payment. Record the electronic payment system and judge its settlement risk once. Hold the election at the system level. Tag contingent, ESG-linked, and non-recourse terms on your financial assets and record the scenario test. Do that, and both the derecognition date and the classification read off governed fields rather than a note reconstructed at close.

If there is one place to start before the 2026 effective date, run the completeness query against your own records: any electronic payment you would derecognise early where a condition was not actually met, and any contingent asset held at amortised cost without a recorded scenario test. For a small finance function that list is short and the work is an afternoon. For a group paying many suppliers across many rails and holding a book of linked loans, it is the work, and it is far better found now, while there is time to set the policy and tag the terms, than raised as a question in the first audit under the amendments.

Sources.

The effective date of annual reporting periods beginning on or after 1 January 2026 and the permission for earlier application, the derecognition of a financial liability on the settlement date, the election to derecognise before settlement on an electronic payment system and its three conditions, the by-system consistency rule, the clarified assessment of contingent and ESG-linked features and the carbon-target example, the non-recourse clarification, and the new IFRS 7 disclosures come from the amendment text issued by the IFRS Foundation in May 2024, which was read directly for this article rather than through a summary, with the announcement and scope corroborated by the IASB news release and by the EY, BDO, PwC, and Deloitte practitioner analyses cited above. No embedded posts from X appear here, because no public post on these amendments could be verified as current, relevant, and authentic at the time of writing, and an unverified embed is worse than none. Nothing here is accounting, audit, or legal advice for a specific company. The figures and names in the worked example and the record are placeholders for shape rather than real values, and how a given company applies these amendments depends on its own facts, its payment systems, and its instruments.