Amendments to Notices Under the ISDA 2002 Master Agreement—and Aligning English Law and New York Law CSAs for Illegality and Force Majeure (2025 TRW Guide)

Who should read this: Bangladesh-origin banks, NBFIs, corporates, funds, and treasury centers that trade OTC derivatives with EU/UK/US dealers and use the ISDA 2002 Master Agreement (the “2002 Agreement”), particularly where English law and New York law Credit Support Annexes (CSAs) co-exist across portfolios.

What changed—and why it matters now: In response to pandemic-era disruptions and the more recent surge in sanctions-related operational friction, ISDA has published optional amendments (the “Amendments”) that let parties (i) add email as a permitted method for delivering Section 5 (Events of Default/Termination Events) and Section 6 (Early Termination/Close-out) notices; (ii) replace the vague “close of business” concept with an objective Notice Delivery Cut-off; and (iii) harmonize how English law CSAs are treated with New York law CSAs for Illegality and Force Majeure—especially around Waiting Periods, termination rights, and Close-out Amount mechanics.

This article decodes the legal changes into board-ready policy, negotiation points, and day-to-day operational playbooks that Tahmidur Remura Wahid (TRW) Law Firm implements for clients across Dhaka, London, and Dubai. Where helpful, we link to internal TRW resources only, such as Regulatory (Bangladesh Bank) and Secured Lending & Syndication for adjacent governance and credit topics.

1) The Business Problem the Amendments Solve

Two perennial sources of litigation risk under the 2002 Agreement are (A) notices and (B) collateral performance under stress:

• Notices (Sections 5/6): Pre-Amendments, email was not a standard, permitted method for default/termination notices under Section 12(a). COVID-19 lockdowns and outbound courier failures exposed that physical service can become impossible right when speed and certainty matter most. Ad hoc multi-channel service (courier + fax + email “for convenience”) clogged cases with arguments over effectiveness and timing.
• Collateral (Illegality / Force Majeure): The 2002 Agreement historically drew a line between payments/deliveries under a Transaction and payments/deliveries under a Credit Support Document. New York law CSAs (security interest) were treated as Credit Support Documents (no Waiting Period if due and blocked), but the English law CSA (title-transfer) was treated as a Transaction—creating different outcomes when Illegality/Force Majeure struck collateral flows. In a world of daily collateralization, that asymmetry was commercially awkward.

What the Amendments do:

1. They let parties switch on email service for Sections 5/6 and specify how email is deemed effective.
2. They replace “close of business” with a concrete Notice Delivery Cut-off Time at a defined Notice Delivery Location.
3. They align the treatment of English law CSAs with New York law CSAs in Illegality/Force Majeure contexts, so collateral failures can trigger termination without a Waiting Period when due—and are ignored for third-party quote purposes in Close-out Amount calculations.

Why 2025 is the moment:
Sanctions perimeter shifts, intermittent office closures, evolving communications policies, and cross-border KYC/IT controls mean even sophisticated counterparties can miss a delivery window or face blocked wires. The Amendments install objective rules for service and collateral consequences, reducing litigation-grade ambiguity.

2) Section 12(a) Notices—Email Joins the Canon (With Guardrails)

2.1 What the 2002 Agreement used to say

Section 12(a) listed permitted methods for notices. By default, email was not permitted for Section 5/6 notices (though parties sometimes customized this in the Schedule or a Confirmation). Many relationships never updated Section 12(a), so email-only notices risked being invalid.

2.2 What the Amendments introduce

Parties may now opt in to a standardized change so that email is a permitted method of delivering notices and other communications under Sections 5 and 6. The Amendments also add detail to how effectiveness is proved and when an email notice is deemed effective.

Core mechanics:

• Effectiveness standard: An email is effective when it is relayed to the recipient’s email infrastructure—a critical shift from vague “sent/received” language.
• Evidence of relay: The sender can rely on data captured by the sender’s infrastructure (e.g., relay logs), whether or not it includes data from the recipient’s systems. This is illustrative, not exhaustive; any reliable evidence of relay can suffice.

Why this matters in disputes:
Defaulting parties often argue “we never got it” or “it was after hours”. By defining relay to the recipient’s infrastructure as the touchpoint, the Amendments push the focus to objective delivery artifacts rather than subjective inbox anecdotes.

2.3 TRW drafting guidance for Schedules

• Designated addresses: Insert specific email addresses (and monitored group mailboxes) in Part 4(a) (Address for Notices). Avoid personal addresses where possible; use role-based mailboxes with redundant monitoring and forwarding rules.
• Two-channel practice: For critical events, we still recommend dual-track service (email + courier/hand delivery if practicable). Redundancy buys certainty.
• Security posture: If clients operate allow-lists / DLP / auto-quarantine, set reciprocal whitelisting early. MTA (mail transfer agent) relay logs and SPF/DKIM configurations can become your evidence ledger.
• Time-stamping: Require servers to maintain UTC and local-time stamps (Dhaka/London/Dubai), and train ops to save relays on issuance.

3) From “Close of Business” to a Clear “Notice Delivery Cut-off”

3.1 The problem with “close of business”

The 2002 Agreement deemed after-hours notices effective the next Local Business Day—but never defined “close of business.” Courts have observed that modern financial institutions work well past 17:00, making fixed-hour assumptions fragile. Outcomes were fact-sensitive, expensive to litigate, and sometimes counterintuitive.

3.2 The solution: a Notice Delivery Cut-off

The Amendments create a “Notice Delivery Cut-off” construct with two new defined items in the Schedule:

• Notice Delivery Cut-off Time (default: 17:00 in the recipient’s Notice Delivery Location, unless parties agree otherwise); and
• Notice Delivery Location (the city/region/country that anchors the time test).

This replaces the open-textured “close of business” with a clear timestamp. If a notice is relayed before the Cut-off Time in the recipient’s Location, it’s effective that day; otherwise, next Local Business Day.

3.3 TRW calibration tips

• Choose realistic cut-offs: For Dhaka-facing teams receiving London notices, consider a Cut-off that respects treasury staffing and bank wire windows (e.g., 18:00 recipient local time, not a rote 17:00).
• Holidays and time shifts: Lock in that Cut-off is measured in the Notice Delivery Location, not the sender’s. Maintain a holiday/early-closing calendar in your SOPs.
• Multiple hubs: If your Schedule lists different addresses for different purposes, each address should carry a Location and Cut-off to avoid forum shopping disputes.

4) Practical Service Playbook (Treasury, Legal, Middle Office)

1. Pre-position email: Confirm DNS, SPF, DKIM, DMARC health for outbound legal notices; generate relay proofs.
2. Template the subject line: e.g., “ISDA 2002 – Section 5/6 Notice – [Counterparty] – [Agreement Date]” to avoid “lost in noise” disputes.
3. Use PDF + text body: Attach the notice on letterhead (PDF) and mirror the operative language in the email body.
4. Log the relay artifact: Save the MTA relay record, time-stamped in UTC and recipient local time.
5. Second channel if feasible: Courier/hand delivery to the Part 4(a) address; keep the airway bill/time-stamp.
6. Internal bridge call: Treasury-Legal-MO huddle to confirm time-effectiveness, especially where termination timing matters (race conditions).

These operational touches are the difference between winning and arguing about notice validity under pressure.

5) Aligning English Law and New York Law CSAs for Illegality/Force Majeure

5.1 The pre-Amendments asymmetry

• Transactions vs Credit Support Documents (CSDs): Under Section 5(b)(i) (Illegality) and 5(b)(ii) (Force Majeure Event), Transactions require the Waiting Period to expire before termination. But CSD obligations already due can trigger immediate termination—no Waiting Period.
• New York law CSAs (security interest) are typically treated as Credit Support Documents (the “CSD limb”).
• English law CSAs (title-transfer) have historically been treated as Transactions, meaning Waiting Period logic applied—diluting immediate relief when collateral couldn’t be delivered due to Illegality/Force Majeure.

5.2 What the Amendments do

ISDA’s Amendments harmonize treatment by re-characterizing the English law CSA to be treated, in these contexts, as if it were a Credit Support Document. The practical consequences:

1. No Waiting Period if an obligation under the English law CSA is already due and performance is prevented by Illegality/Force Majeure—immediate termination right becomes available (for the Non-Affected Party).
2. Termination rights coordination: An Affected Party can designate an Early Termination Date only after the Non-Affected Party has designated an Early Termination Date for less than all Affected Transactions—mirroring the CSD logic.
3. Close-out quotes (Section 6(e)(ii)(3)(A), mid-market events): Third-party quotations for Close-out Amount must not take into account any existing Credit Support Document—and the harmonized English law CSA now falls under that ignore rule for quotes, just like the New York law CSA.

Commercial rationale: Daily collateralization is the credit heartbeat of uncleared derivatives. If collateral stops flowing because it’s illegal or physically impossible to deliver, the immediate termination option should not depend on CSA legal architecture (title-transfer vs security interest). The Amendments modernize the 2002 Agreement to that market reality.

5.3 TRW negotiation and drafting notes

• Opt-in clarity: Confirm in the Schedule that the parties adopt the alignment language. Avoid split-book ambiguity where only some relationships implement it.
• Define “due”: Ensure your CSA procedures make crystal clear when a collateral delivery becomes due (call time, valuation time, threshold/MTA tests, settlement cut-offs) to anchor the no-Waiting-Period trigger.
• Sanctions touchpoints: Illegality can stem from sanctions. Draft your sanctions reps and carve-outs to avoid accidental breaches while preserving the right to terminate when truly blocked.

6) Close-Out Amount, Quotes, and the “Ignore the CSD” Rule

Under the 2002 Agreement, mid-market quotation mechanics direct that independent quotes should not consider existing Credit Support Documents. The Amendments extend that treatment to English law CSAs in Illegality/Force Majeure scenarios by aligning them to the CSD limb.

Why that matters:
When collateral deliveries are frozen by Illegality/Force Majeure, you do not want quote providers to assume the economic cushion of a CSA that, in fact, cannot perform. The ignore rule produces cleaner, market-realistic Close-out Amounts and fewer valuation dogfights.

7) Interplay With Your Treasury, Custodians, and Banks (Bangladesh-First View)

• Bangladesh Bank overlays: Collateral funding and cross-border cashflows must respect FX permissions, documentary trails, and banking channels. Tie your ISDA procedures into the governance described in Regulatory (Bangladesh Bank).
• Cut-offs vs wire windows: Choose Notice Delivery Cut-off Times that pair with USD/EUR/GBP settlement cut-offs reachable from Dhaka (often via Dubai/London routes).
• Custodian KYC: If your IM/VM infrastructure involves offshore custodians, ensure sanctions screening and message routing don’t choke in a stress event; add playbooks for blocked payments.

8) Litigation-Proofing Your Notices and Collateral SOPs

Notices (Sections 5/6):

• Maintain a Notices Register with counterparty email addresses, Locations, Cut-offs, and backup channels.
• Adopt two-channel practice for terminations where practicable (email + courier).
• Keep relay artifacts centrally in WORM-style (write-once) repositories for evidential integrity.

Collateral (Illegality/Force Majeure):

• Document when a call is due, including valuation timestamps, threshold/MTA tests, and settlement conventions.
• Maintain incident logs for blocked wires and sanctions holds; these records will ground Impossibility/Illegality narratives if litigated.
• Train teams on the harmonized CSA treatment so they know when immediate termination can be exercised.

9) Drafting Checklist for Your Schedule (TRW “Green-lines”)

1. Section 12(a) email enablement:

• Add email as a permitted method for Sections 5/6.
• Insert recipient addresses (role-based) and monitoring rules.
• Reference relay to recipient infrastructure as the effectiveness point and the evidence standard.

1. Notice Delivery Cut-off block:

• Define Notice Delivery Cut-off Time (e.g., 18:00 recipient local time).
• Define Notice Delivery Location for each party (city/region/country).
• Clarify Local Business Day references where multiple locations appear.

1. CSA alignment for Illegality/Force Majeure:

• State that the English law CSA is treated as if a Credit Support Document for purposes of Sections 5(b)(i), 5(b)(ii), 6(b)(iv)(2)(A), and 6(e)(ii)(3)(A).
• Update definitions/cross-references to capture “due and prevented” moments.

1. Sanctions overlay:

• Calibrate representations and Termination Events to avoid shutting down legitimate trade, but preserve termination where Illegality or sanctions truly bite.

1. Operational annex:

• Append a Notices & Collateral Procedures memo (valuation times, tolerated delays, escalation contacts, calendar sources).

10) Implementation Program (8–10 Weeks Typical)

Phase 1 – Diagnostic (Weeks 1–2)

• Inventory 2002 Agreements and Schedules; map CSAs (English vs NY law).
• Identify current notice channels, addresses, Locations, and implicit “close of business” assumptions.
• Stress-test Illegality/Force Majeure against your sanctions footprint and wire paths.

Phase 2 – Drafting & Negotiation (Weeks 3–6)

• Prepare a standardized Schedule rider with the email enablement, Cut-off, and CSA alignment blocks.
• Prioritize counterparties by volume/volatility; negotiate in parallel where possible.

Phase 3 – Ops Hardening (Weeks 6–8)

• Update Notices Register and distribution lists.
• Implement relay-logging and WORM retention.
• Train Treasury/Legal/MO on timelines and evidence capture.

Phase 4 – Drill & Review (Weeks 8–10)

• Conduct a table-top exercise simulating (a) sanctions-blocked collateral and (b) competing termination notices around the Cut-off.
• Fix gaps; roll changes to the broader book.

For transaction-adjacent governance with lenders, see Secured Lending & Syndication—alignment here smooths credit committee sign-offs on your derivatives posture.

11) “What-If” Scenarios (With TRW Responses)

Scenario A: Sanctions block a EUR cash VM payment due today under an English law CSA.

• Pre-Amendments: Waiting Period arguments could delay termination because the CSA was treated like a Transaction.
• With Amendments: Treat English law CSA like a CSD—no Waiting Period if payment was due and is prevented by Illegality/Force Majeure.
• TRW response: Document due-time, block reason, and evidence; move to termination if strategy dictates.

Scenario B: You email a Section 6 close-out notice at 17:10 in the recipient’s Location; the Cut-off is 17:00.

• Effectiveness: Deemed delivered next Local Business Day.
• TRW response: Consider issuing a fresh notice before the next day’s Cut-off and hand-deliver if speed is mission-critical.

Scenario C: You and your counterparty both race to designate an Early Termination Date.

• Old regime: “Close of business” ambiguity fueled costly arguments.
• With Amendments: Timing is anchored to Cut-off and relay proof.
• TRW response: Produce relay artifacts, apply Cut-off rule, and stabilize the valuation window.

Scenario D: Close-out Amount quotations arrive; the quote provider considered collateral economics.

• With Amendments: Quotes should ignore any CSD, including the aligned English law CSA.
• TRW response: Reject contaminated quotes; demand clean, mid-market quotations per Section 6(e)(ii)(3)(A).

12) Frequently Asked Questions (2025)

Q1: Do we have to adopt all Amendments or can we pick and choose?
You can opt in selectively by bilateral agreement. TRW typically recommends adopting all three (email, Cut-off, CSA alignment) for coherence.

Q2: If we already allow email in our Schedule, do we still need this?
Likely yes. The Amendments add precision (e.g., relay effectiveness, evidence standards, Cut-off) that ad hoc clauses often lack.

Q3: Can we set different Cut-off Times for legal notices vs collateral notices?
Yes—if you draft clearly. Most clients favor one clean rule to reduce mistakes.

Q4: What if our counterparty wants 17:00 London but our ops close at 16:30 Dhaka?
Tie Cut-off to the recipient’s Location, not the sender’s; otherwise you are time-boxed by someone else’s clock.

Q5: Will courts honor sender-side relay logs as evidence?
They are expressly contemplated as acceptable evidence, though not exclusive. TRW layers additional proofs (e.g., delivery receipts, parallel channels) for belt-and-suspenders strength.

Q6: How does this interact with our GMRA/GMSLA?
While separate documents, the conceptual move toward objective cut-offs is consistent. Many clients harmonize notice mechanics across all master agreements to avoid operator errors.

13) Governance, Risk & Compliance (GRC) Actions for Boards

• Policy update: Amend the Derivatives Use Policy to reflect email notices, Cut-off Times, and CSA alignment; specify authorized signatories and mailboxes.
• Records management: Adopt WORM archiving for notice relays and collateral due-time evidence.
• Training cadence: Quarterly refreshers for Treasury, Legal, MO; table-top exercises on race notices and sanctions-blocked collateral.
• Dashboarding: Maintain a Notices & CSA dashboard: counterparties, addresses, Locations, Cut-offs, last tests, and incidents.

14) TRW’s Cross-Border Execution Model

• Dhaka: Integrates the Amendments with Bangladesh Bank compliance, board approvals, and lender communications.
• London: English-law drafting, ISDA negotiations, and quote challenges under Section 6(e).
• Dubai: Time-zone bridge, ensuring notices/collateral operations meet Cut-off and wire windows across currencies.

Our objective: the legal text, treasury ledger, and courtroom narrative all match—no daylight between what the contract says, what your teams do, and how you prove it.

15) Structured Summary Table (Quick Reference)

Topic	Old Position	Amendment	Why It Matters	TRW Action
Email for Sections 5/6 notices	Usually not permitted absent bespoke Schedule	Permitted if parties opt in; effectiveness when relayed to recipient infrastructure; sender-side evidence allowed	Removes pandemic/sanctions service bottlenecks; reduces “we never got it” disputes	Add email in Schedule; designate role-based mailboxes; implement relay logging & dual-channel practice
“Close of business” timing	Undefined; highly fact-dependent; litigation magnet	Replaced with Notice Delivery Cut-off Time in a specified Location (default 17:00 unless agreed otherwise)	Creates objective timing; stabilizes “who went first” races	Set realistic Cut-off per recipient ops; anchor to recipient Location; maintain holiday calendars
English law CSA in Illegality/Force Majeure	Treated like a Transaction → Waiting Period hurdles	Aligned to CSD treatment: no Waiting Period if due and prevented; quotes ignore the CSA	Daily collateral is critical; immediate termination shouldn’t depend on CSA architecture	Opt-in alignment; define “due” precisely; build sanctions/blocked-payment playbooks
Close-out Amount quotes	Quotes may be distorted if they assume collateral performance	Quotes must not consider any CSD (aligned English law CSA included)	Cleaner mid-market valuations; fewer quote fights	Train FO/MO to reject contaminated quotes; keep clean quote procedures
Ops evidence	Patchwork (emails, couriers, call logs)	Relay proofs, WORM archiving, dual-channel service encouraged	Evidence wins disputes	SOPs for log capture, UTC + local time stamps; table-top drills

16) Conclusion

The ISDA Amendments modernize three fault lines that the last decade exposed: how we give critical notices, when those notices legally “land,” and what happens when collateral can’t move because the law—or a Force Majeure—says it cannot. By embracing email with provable relay, replacing “close of business” with an objective Cut-off, and harmonizing the English law CSA with the New York law approach for Illegality/Force Majeure, market participants get certainty and speed exactly where disputes used to fester.

For Bangladesh-origin institutions, this is not just a drafting clean-up—it is a resilience upgrade. It ensures your Dhaka treasury, London legal posture, and Dubai settlement rails are synchronized to one unambiguous rulebook. TRW will inventory your agreements, implement the Schedule rider, harden your operations, and drill your teams—so that when the next stress window opens, your notices stick, your timing holds, and your collateral strategy is enforceable.

For adjacent governance and credit alignment, see our internal guides on Regulatory (Bangladesh Bank) and Secured Lending & Syndication.

Contact TRW Law Firm

Tahmidur Remura Wahid (TRW) Law Firm
Dhaka: House 410, Road 29, Mohakhali DOHS
Dubai: Rolex Building, L-12 Sheikh Zayed Road
London (UK): 330 High Holborn, London WC1V 7QH, United Kingdom

Call Us: +8801708000660 / +8801847220062 / +8801708080817
Email: info@trfirm.com | info@trwbd.com | info@tahmidur.com

Prepared by TRW’s Derivatives & Structured Products team, integrating English-law documentation with Bangladesh-first treasury operations and cross-border settlement realities.