Negative Interest Under the 1995 ISDA Credit Support Annex (Transfer – English law): What the High Court Decided—and How TRW Re-Papers Your Risk in 2025
Audience: Bangladesh-origin banks, NBFIs, corporates, and funds that (i) hedge FX/rates/commodities with EU/UK dealers, (ii) still have legacy 1995 ISDA Credit Support Annex (Transfer – English law) relationships in their book, or (iii) run back-to-back structures where old and new collateral frameworks co-exist.
Core holding (plain English): The High Court of England and Wales held that the 1995 English law title-transfer CSA does not require a Transferor that has posted cash collateral to pay or account for negative interest to the Transferee. In other words, under the standard 1995 English law CSA, there is no contractual obligation to make a reverse-direction payment when the applicable interest rate on cash collateral drops below zero. If parties want negative-interest economics, they must draft for it (e.g., in Paragraph 11) or adhere to ISDA’s 2014 Collateral Agreement Negative Interest Protocol (which many legacy pairs did not do).
1) Why this decision still matters in 2025
You might think negative rates were a “2015–2021” phenomenon—but rate regimes can and do pivot. More importantly, many treasuries still carry legacy 1995 CSAs for long-dated transactions, amortizing infra hedges, or older back-to-backs. During a renewed stress episode (or even a short negative-print window), the treatment of collateral interest can move real P\&L and close-out math. The High Court ruling places a bright marker: no negative-interest obligation under the standard form unless parties expressly contracted for it.
Why Bangladesh-origin institutions care:
Mixed estates: It’s common to have a 1995 CSA on one leg and a 2016 VM CSA (or a bespoke modern annex) on another. Asymmetry creates basis risk if negative-rate conditions return.
Back-to-backs with clients/suppliers: If your upstream (street) leg recognizes negative interest but the downstream (client/intra-group) leg doesn’t, your treasury becomes the shock absorber.
Close-out disputes: During termination events, counterparties will scrutinize every cash-flow convention. Clear drafting—and clear evidence trails—win the day.
2) The facts, simplified
The State and Deutsche Bank traded multiple derivatives under an ISDA Master Agreement with a 1995 ISDA CSA (Transfer – English law).
At the relevant time, Deutsche Bank had posted cash collateral to the State (the State had net credit exposure).
The applicable interest rate on that cash collateral turned negative for a period.
The relationship did not incorporate the 2014 ISDA Collateral Agreement Negative Interest Protocol.
The State’s claim: Not by invoking the explicit interest-payment clause Paragraph 5(c)(ii) (which concerns positive interest), but by a structural route: arguing that the definition of “Credit Support Balance” implicitly accounts for negative interest. Because Credit Support Balance includes any Interest Amount “not transferred” pursuant to 5(c)(i) or (ii), the State argued that negative accruals reduce the Credit Support Balance and thus force additional collateral posting.
3) The High Court’s analysis (business-friendly summary)
Textual spine: While “Interest Amount” could mathematically be negative, Paragraph 5(c)(ii)—the clause that pays interest—does not require paying negative interest.
No “two-machinery” rationale: The State’s theory would mean positive interest is handled in 5(c)(ii) but negative interest is smuggled in via the Credit Support Balance definition. The Court found no credible commercial rationale for this asymmetry. If parties wanted to deal with negative interest, the “obvious course” was to put it in 5(c)(ii) or otherwise spell it out.
Result: The Agreement does not oblige the Transferor to pay or account for negative interest under the 1995 English law title-transfer CSA.
Commercial translation: The 1995 form was drafted in a positive-rate paradigm. It contains a working engine for paying positive interest on posted cash; it never installed the reverse flow. Courts will not retrofit that engine by implication through a definition designed for counting amounts, not creating new payables.
4) How this sits with the Protocol and newer CSAs
2014 ISDA Collateral Agreement Negative Interest Protocol: A voluntary, standardized way to amend certain collateral agreements to recognize negative interest. If both parties adhered, your interest mechanics may already allow negative cashflows. If not, the default 1995 position stands.
2016 ISDA VM CSA (English law): Designed in the post-crisis era, it aligns daily VM, eligible collateral, haircuts, and interest mechanics with modern risk-mitigation regimes. Many 2016 forms speak clearly about interest treatment (including floors). A 2016 VM CSA won’t automatically cure what an old 1995 CSA says (or doesn’t say) on other relationships.
Bottom line:Do not assume your book is harmonized. Inventory your annexes and read the actual words.
5) Treasury math: where negative-interest ambiguity bites
Even a brief negative-rate window can ripple through:
Collateral posting size: Under the State’s theory (rejected), negative accruals would reduce Credit Support Balance and increase daily calls. The Court avoided that spiral by holding no negative-interest obligation exists absent drafting.
Close-out determinations: Termination amounts can be sensitive to collateral economics (e.g., whether a collateral account notionally accrues below zero).
6) What TRW recommends you do—now
6.1 Audit and classify your estate
List every CSA by counterparty, date, and type (1995 English law Transfer; 1994/1995 New York law security interest; 2016 VM CSA; bespoke).
Mark Protocol adherence (2014 Negative Interest) for both parties; attach the actual adherence records.
Flag interest clauses: Does the text (i) impose a zero floor, (ii) allow negative interest, or (iii) stay silent?
6.2 Decide your “house position”
Option A—Zero floor (no negative interest): Adopt or confirm a zero floor under legacy 1995 CSAs; avoid P\&L leakage if rates re-dip.
Option B—Allow negative interest (symmetry): If your pricing depends on full symmetry, draft it in (Paragraph 11); align benchmark, day-count, and cut-offs with your ops.
6.3 Repaper precisely (Paragraph 11)
If you want to move from silence to clarity, Paragraph 11 is the correct place for bespoke elections and overrides. Keep it tight:
Define where interest accrues (collateral currency vs exposure currency benchmarks).
State the floor (zero or negative allowed) and direction (who pays whom).
Set day-count, rounding, and payment frequency.
Reflect time-zone cut-offs and valuation timestamps that Treasury can actually run (Dhaka–Dubai–London choreography).
6.4 Align your notices mechanics (separate but critical)
A negative-rate episode often overlaps with market stress. If you are terminating or disputing calls, your notices must stick. Consider adopting the ISDA notices amendments (email enablement, Notice Delivery Cut-off). This reduces “we never got it” fights and timing ambiguity during close-outs.
7) Drafting tactics (that win in audit and in court)
Say the quiet parts out loud: If negative interest is not intended, state a zero floor expressly. If you do intend it, say so and wire the plumbing (who pays; when; how calculated).
Separate VM and IM logic:IM (if you are in scope) is segregated; interest conventions can differ. Don’t let IM language contaminate VM clauses.
Currency-aware drafting: If you post USD against EUR exposure, decide whether interest follows the collateral currency or a specified benchmark; paper FX haircut logic to avoid “double-charging” for currency risk.
Operational annex: Add a margin/interest procedures memo (valuation times, tolerance bands, escalation). In disputes, good SOPs become good evidence.
Back-to-backs: If only one side permits negative interest, install an internal transfer pricing or adjustment mechanism so Treasury isn’t unhedged.
8) Bangladesh-first operational reality
FX & banking channels: Cross-border collateral flows must track Bangladesh Bank requirements and documentary evidence. Map VM interest inflows/outflows to permitted accounts; pre-clear with your banks.
Time-zones and cut-offs: Align valuation and payment cut-offs with Dhaka-Dubai-London banking windows. A clause that assumes New York evenings won’t help your Dhaka desk settle next-day VM.
Board governance: Update your Derivatives Use Policy to state the firm’s negative-interest stance by annex type; require quarterly collateral P\&L reporting.
Q1. Does the decision mean negative interest is never payable under a 1995 English law CSA? No—it means the standard form doesn’t require it. Parties can contract for it (e.g., in Paragraph 11) or both adhere to the 2014 Protocol.
Q2. Our upstream 2016 VM CSA recognizes negative interest, but our legacy 1995 downstream annex is silent. Is that a problem? Potentially. You may experience P\&L mismatch in a negative-rate window. Consider a downstream rider (either zero floor or symmetry), or a transfer pricing mechanism.
Q3. Can a court imply a term for symmetry because positive interest exists? The High Court’s reasoning cuts against implication. If you want symmetry, write it in. Courts respect ISDA’s careful drafting culture.
Q4. Should we simply adhere to the 2014 Protocol? It’s a clean path if both parties agree—but confirm it fits your treasury policy, benchmarks, and day-count. Some prefer a tailored Paragraph 11 rider for precision.
Q5. We have dozens of counterparties. Where do we start? Start with material exposures and long tenors. TRW will produce a CSA inventory, flag negative-interest status, and propose a two-page rider for fast bilateral execution.
Amend Derivatives Use Policy; brief the board and lenders; publish an internal one-pager on negative interest.
11) Sample policy language (illustrative only)
Interest on Cash Collateral (VM). Except as otherwise agreed in the applicable Credit Support Annex, any Interest Amount in respect of Cash Collateral shall not accrue below zero; for the avoidance of doubt, no obligation to pay or account for negative interest shall arise. Where the parties expressly elect to recognize negative interest, Interest Amount may accrue below zero and shall be payable by the party specified in Paragraph 11, calculated by reference to the agreed benchmark and day-count convention.
(TRW will tailor the operative drafting directly in Paragraph 11 of your 1995 CSA or prepare a short-form rider.)
12) Common pitfalls we fix before they bite
Assuming Protocol coverage—many books never adhered (or only one party did).
Relying on generic confirmations—they often don’t amend CSA interest mechanics.
Day-count and rounding drift—small numbers, big audit findings.
Currency mismatch leakage—posting USD against EUR exposure without clear FX haircut and interest currency rules.
Back-to-back blind spots—street vs client annexes not aligned; Treasury eats the basis risk.
No evidence trail—when disputes hit, you need journals, timestamps, and SOPs.
13) Structured summary table (print-friendly)
Topic
What the Court held
Why it matters
What to do now
TRW deliverable
1995 CSA (English law) & negative interest
No obligation to pay/account for negative interest under standard form
Avoids surprise collateral calls and P\&L shifts in negative-rate windows
Decide house stance: zero floor or allow negatives
Two-variant Paragraph 11 rider
“Credit Support Balance” argument
Cannot be used to smuggle in negative interest
Prevents creeping obligations via definitions
Keep interest obligations in 5(c)(ii)/Paragraph 11
Red-lined annex with clean definitions
Protocol (2014)
Enables negative-interest recognition if both adhered
Many pairs never adhered; don’t assume
Check adherence lists; remediate gaps
CSA inventory with adherence flags
Mixed estates (1995 vs 2016 VM)
Asymmetry creates basis/P\&L risk
Back-to-backs vulnerable
Harmonize with riders or internal transfer pricing
Back-to-back mapping memo
Ops & governance
Evidence and clarity win
Audits and close-outs hinge on records
Update SOPs, day-count, cut-offs, journals
SOP pack + table-top drill plan
14) Conclusion: decide your economics—and write them down
The High Court’s judgment confirms what seasoned documentation lawyers long suspected: the 1995 English law title-transfer CSA never hard-wired negative interest. That clarity is an opportunity. In 2025, you can either (i) lock in a zero floor (the simplest path for many Bangladesh-origin treasuries) or (ii) elect symmetry with precision drafting where your pricing demands it. What you should not do is leave the question to interpretation. Markets move; paperwork lasts.
TRW will (a) map your CSAs, (b) draft the Paragraph 11 rider that fits your treasury’s reality, (c) align upstream/downstream books, and (d) harden your SOPs so the legal text, daily ledger, and courtroom story are perfectly aligned.
For adjacent governance and credit alignment, see:
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
Prepared by TRW’s Derivatives & Structured Products team. This article is for general information only and does not constitute legal advice; we tailor advice to the specifics of your documentation stack and regulatory posture.
Harvey AI Alternatives in Bangladesh: A TRW Law Firm Guide to Choosing the Right Legal AI for Research, Contracts, and Review
Harvey AI is one of the better-known new entrants in legal AI—strong in research, drafting support, clause discovery, and summarization. But no single platform is a perfect fit for every team, practice, or budget. If you’re evaluating Harvey AI alternatives, you’re likely balancing six practical questions:
Will it meaningfully reduce review time and drafting cycles?
Can it plug into our existing workflows (DMS/ECM, CRM, e-signature, SSO, MDM, SIEM)?
Does it protect client confidentiality and comply with data-residency and bar-ethics requirements?
Does it support playbooks, templates, and firm-style consistency?
Is pricing aligned with utilization (and defensible to clients)?
Can we deploy quickly without burdening lawyers and IT?
This guide breaks down what Harvey AI does well, why some firms look elsewhere, and how five notable alternatives—Aline, CoCounsel, Spellbook, Everlaw, and Luminance—stack up across contract work, litigation support, and research. We conclude with TRW Law Firm’s procurement checklist, an implementation roadmap, and a comparison table you can lift into your internal memo.
Looking for structured help on implementation, policies, and vendor selection? Our technology, privacy, and commercial teams advise on AI procurement, contractual risk allocation, and internal governance for Bangladesh-headquartered and cross-border practices. Explore our Corporate & Commercial and Innovation & Legal Tech Tools pages for related services and resources.
What Is Harvey AI?
Harvey AI is a newer legal AI platform designed to accelerate legal research, legal document review, and contract analysis. In practical terms, it ingests large volumes of legal text and returns direct, cited answers; drafts and redlines clauses; and summarizes documents and case files to support faster decision-making.
Core Capabilities (Typical Deployments)
AI-assisted legal research with cited sources and targeted reasoning.
Document and clause review to highlight risks, exceptions, and deviations from standards.
Contract analysis to speed negotiation and align language with playbooks.
Drafting support for agreements, letters, and motion-adjacent documents.
Summarization of case files, agreements, and correspondence.
Natural-language Q\&A on legal topics, to orient a matter team quickly.
While Harvey AI is gaining traction, many firms—especially those with complex cross-department workflows—consider alternatives that better match their contract lifecycle scope, litigation scale, integration footprint, or price-to-usage expectations.
Why Consider an Alternative to Harvey AI?
Different practices value different things. From our work advising in-house teams and law firms, these are the most common reasons to explore substitutes or complements:
Deeper contract-lifecycle coverage: From pre-signature drafting and negotiation to repository analytics and renewal tracking—some platforms offer an end-to-end approach out of the box.
Tighter workflow integrations: Smoother connectivity with DMS (iManage/NetDocuments/SharePoint), CLM, CRM, SSO/IdP, e-signature, and ticketing tools reduces adoption friction.
Playbooks + firm style enforcement: Legal ops often prioritize configurable playbooks, clause libraries, fallback logic, and formatting enforcement.
Cost alignment: Solo practitioners or boutique teams may prefer pricing that scales with matter volume and user roles.
Specialized features: Litigation analytics, deposition prep, timeline building, or advanced repository mining may be must-haves for specific practice groups.
Data control & ethics: Some buyers require explicit commitments—no model training on client data, regional hosting, SOC 2/ISO 27001, and granular audit trails to meet confidentiality and professional-responsibility duties.
Related reading from TRW: see Regulatory Compliance & Bangladesh Bank for governance frameworks that matter when your AI stack touches regulated financial clients.
The 5 Best Harvey AI Alternatives (and When They Win)
1) Aline — Full-Cycle Contract Work, From Draft to Signature to Insights
Where it shines: A comprehensive contract lifecycle approach that goes beyond point solutions. If your pain spans drafting, third-party review, negotiation, approvals, signature, and repository analytics, Aline’s “single lane” experience removes tool-switching and preserves metadata end-to-end.
Standout Features
Aline AI for drafting, redlining, and querying agreements with context awareness.
AI Playbooks that operationalize your templates and fallbacks for consistent review.
AI Repository to centralize agreements, surface risk, and trigger renewal/obligation alerts.
AlineSign built-in e-signatures (unlimited) that stay within the contract workspace.
Cross-functional workflows for Sales, Legal, and Ops, with approval paths and audit trails.
AI Reports to extract terms at scale and answer portfolio-level questions.
Why teams pick it
Collapses multiple tools into one governed environment.
Reduces review time—especially for third-party paper—by standardizing playbooks.
Improves findability and obligation tracking post-signature.
Watch-outs
Best fit when your primary use case is contracts rather than litigation analytics.
Implementation is smooth, but you’ll get the best ROI if you invest in playbooks early.
2) CoCounsel (Thomson Reuters) — Research, Review, and Task Acceleration
Where it shines: A trusted ecosystem for firms already embedded in Westlaw/Practical Law. CoCounsel accelerates research, contract review, document summarization, and deposition prep, with attention to cited support and manageable outputs for human validation.
Standout Features
Contract review for risk flags, missing terms, and negotiation points.
Case law research with citations to underpin arguments quickly.
Long-document summarization for discovery and diligence sets.
Deposition prep via transcript parsing and question structuring.
Why teams pick it
Reduced research latency; fast triage of heavy files.
Strong fit for firms that want acceleration without departing from established research stacks.
Watch-outs
More assistant-style breadth than deep CLM lifecycle.
Value increases with the broader Thomson Reuters toolchain.
3) Spellbook — Microsoft Word-Native Drafting and Review
Where it shines: Lawyers who live in MS Word and want AI inline. Spellbook augments drafting with real-time clause suggestions, risk flags, and contextual Q\&A without leaving the document.
Standout Features
Inline review that flags issues and proposes alternatives in real time.
On-demand drafting of clauses/sections tailored to the active document.
Due-diligence acceleration by highlighting key terms across sets.
Minimal learning curve due to Word-native experience.
Why teams pick it
Keeps velocity high for deal teams working directly in Word.
Ideal as a low-friction “assist” layer even when a CLM exists elsewhere.
Watch-outs
Not a full CLM; repository, obligations, and e-signature are typically separate.
Governance depends on your M365 configuration and document policies.
4) Everlaw — Litigation & Investigations at Scale
Where it shines:Discovery-heavy matters and investigations where speed to insight is crucial. Everlaw consolidates document review, search/filtering, timeline building, and case prep features in one interface geared to large datasets—but also approachable for small teams.
Standout Features
Review workflows with efficient coding, batching, and collaboration.
Advanced search to locate needles in massive haystacks.
Case building tools for chronology, themes, and exhibits.
Multi-user collaboration and granular workspace management.
Why teams pick it
Shortens time from ingestion to actionable insights.
Useful across antitrust, investigations, and complex civil disputes.
Watch-outs
Purpose-built for litigation; not a contracts platform.
Cost and value scale best with litigation intensity.
Where it shines:Due diligence, post-merger harmonization, and ongoing compliance monitoring where teams need anomaly detection and fast variance analysis against playbooks or templates.
Standout Features
Outlier and risk detection across large contract sets.
Compliance monitoring for term drift and change notifications.
Document comparison for template adherence and version deltas.
Data extraction for reporting and analytics.
Why teams pick it
Efficient for large-scale review programs.
Clear visual dashboards shorten the “so what” path.
Watch-outs
Edge cases and nuanced drafting still need domain experts.
Consider how it coexists with your DMS/CLM to avoid duplication.
How to Choose: A Practical Buyer’s Checklist
When TRW runs legal-tech selections for clients (or for our own cross-border practice), we apply a layered assessment to avoid “demo bias” and ensure adoption:
Governance & Risk
Data handling: At-rest/in-transit encryption, key management, audit logs.
Confidentiality: No training on client data; configurable retention and deletion.
See also our Project Finance and Restructuring & Insolvency service pages for broader risk and governance approaches that often intersect with legal-tech procurement.
TRW’s View: When Each Tool Is the Better Fit
Choose Aline if your core goal is contract velocity + governance in one lane—drafting to signature to repository insights—with strong playbooks and built-in e-signatures.
Choose CoCounsel if you want accelerated research and review within a BigLaw-friendly ecosystem and leverage of the Thomson Reuters stack.
Choose Spellbook if your partners and associates live in Word and want inline intelligence without moving files or screens.
Choose Everlaw if you need litigation-grade discovery and investigation tooling to tame volume and move from ingestion to strategy quickly.
Choose Luminance for portfolio-level contract analytics, anomaly detection, and compliance tracking across thousands of agreements.
Many TRW clients ultimately adopt a hybrid: e.g., Aline for contracts + Everlaw for discovery, or Spellbook for drafting assistance with a separate CLM. The key is drawing a clear system-of-record map so documents, signatures, and audit trails are never fragmented.
Implementation Roadmap (90 Days)
Phase 1 — Baseline & Guardrails (Weeks 0–2)
Confirm data policies, privilege, and no-training commitments.
Map identities (SSO/SCIM), roles, and DLP rules.
Draft AI usage policy (matter types allowed, review expectations, logging).
Define KPIs: cycle time, review time saved, deviation-from-playbook rate.
Weekly cadence with pilot users; capture objections and wins.
Phase 3 — Scale (Weeks 8–12)
Expand to additional matter types and business units.
Formalize training (15-minute micro-modules; “golden path” checklists).
Integrate alerts (renewals, unusual clauses) into matter intake or ticketing.
Phase 4 — Institutionalize (Post-90 Days)
Quarterly playbook refresh; add analytics to partner dashboards.
Vendor roadmap review; negotiate SLAs, uptime credits, and security attestations.
Annual red-team exercise on prompt injection, data exfiltration, and misuse.
FAQs About Harvey AI Alternatives
Who are Harvey AI’s competitors? Platforms commonly evaluated alongside Harvey AI include Aline, CoCounsel, Spellbook, Everlaw, Luminance, and data-driven litigation platforms like Lex Machina. Each emphasizes a different mix of contract, research, or litigation features.
Who competes with Harvey? Broadly, any tool that accelerates research, drafting, contract review, or litigation prep. Your “closest” competitor set depends on whether your top pain is contracts, discovery, or research.
How much does Harvey AI cost per month? Public list pricing is uncommon for enterprise legal AI. Costs vary by user count, feature tiers, data/security add-ons, and support level. We advise piloting with 2–3 use cases and negotiating commercials around tangible KPIs.
Does Harvey AI use OpenAI? Harvey AI is widely understood to leverage large-language-model technology in its stack. For procurement, focus on concrete data-handling commitments (no model training on your inputs by default, retention controls, and auditable logs).
Why might law firms choose advanced legal AI tools? To compress drafting and review cycles, cut error rates, and surface insights (judge/court trends, clause risks, fallback positions) that sharpen strategy and improve client value.
Aline Brings the Complete Package for Contract Work
If your legal team’s bottleneck is contracts from first draft to final signature and beyond, Aline stands out for combining AI drafting, playbook-driven review, approvals, e-signature, and a searchable repository. Rather than shuttling documents across four tools, you keep momentum, context, and auditability in one governed space—an advantage for in-house departments, fast-moving deal teams, and law firms that must standardize quality at scale.
How TRW Law Firm Helps
As a Bangladesh-origin international law firm with London and Dubai presence, Tahmidur Remura Wahid (TRW) advises on:
AI Procurement & Contracting: Vendor due diligence, DPAs, audit rights, SLAs, limitation of liability, IP and output ownership, indemnities, and termination rights.
Privacy, Data & Professional Responsibility: Confidentiality safeguards, privilege preservation, cross-border transfers, and local hosting considerations for regulated clients.
Implementation & Change: Playbook design, intake forms, approval logic, and “golden path” training to increase adoption and measurable ROI.
Ongoing Governance: Quarterly playbook refresh, model-risk checkups, and incident/exception handling.
Comparison Table: Harvey AI vs. Leading Alternatives
Criterion
Harvey AI
Aline
CoCounsel (TR)
Spellbook
Everlaw
Luminance
Primary Strength
Research + drafting + review
Full CLM lifecycle
Research + review + summarization
Word-native drafting/review
Litigation discovery & case prep
High-volume contract analytics
Drafting Assist
Yes
Yes (playbook-aware)
Yes
Yes (inline in Word)
Limited (litigation-oriented)
Limited (analytics-focused)
Contract Review
Strong
Strong with playbooks
Strong
Strong (inline flags)
N/A (not core)
Strong (outliers/risks)
Repository & Obligations
Basic-to-moderate
Advanced (AI repository)
Moderate
Minimal
N/A
Strong extraction/monitoring
E-Signature
Via integrations
Built-in (AlineSign)
Via integrations
Via integrations
Via integrations
Via integrations
Litigation/Discovery
Limited
Limited
Moderate (summaries)
Limited
Best-in-class
Limited
Integrations
Varies
CRM/DMS/IdP +
Strong in TR stack
M365-native
eDiscovery ecosystem
DMS/CLM coexistence
Governance & Logs
Enterprise-grade
Enterprise-grade
Enterprise-grade
M365-governed
Enterprise-grade
Enterprise-grade
Best For
Balanced research + review
Contract velocity + governance
Research-heavy teams
Word-centric drafters
Discovery-heavy matters
Portfolio compliance & due diligence
Quick Fit Matrix (Use Cases → Tools)
We need one governed lane for contracts (draft→sign→renew). → Aline
We want faster research with citations and contract triage. → CoCounsel
We live inside Word and want real-time help. → Spellbook
We’re drowning in discovery and need speed to insight. → Everlaw
We’re harmonizing thousands of legacy contracts post-deal. → Luminance
Closing Takeaways
Start with your top two use cases. If contracts dominate, prioritize CLM depth (playbooks, repository, e-signature). If litigation drives revenue, optimize for discovery speed.
Design your pilot like a mini-case study. Define KPIs before the kickoff and negotiate commercials around realized savings and cycle-time improvements.
Treat AI as a governance program, not just a tool. Policies, playbooks, and training will drive more ROI than model specs alone.
A hybrid stack may be optimal. Many TRW clients pair a contract-centric system with a litigation platform and a Word-native assistant for maximum coverage.
Contact TRW Law Fir
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
Book a scoping call with TRW’s cross-border tech team
If you’d like, we can tailor this guide to your exact tech stack (DMS, CLM, SSO), run a vendor RFP, and draft contractual protections (DPA, audit rights, SLAs, IP ownership, and indemnities) that reflect your risk profile and client commitments.
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:
They let parties switch on email service for Sections 5/6 and specify how email is deemed effective.
They replace “close of business” with a concrete Notice Delivery Cut-off Time at a defined Notice Delivery Location.
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)
Pre-position email: Confirm DNS, SPF, DKIM, DMARC health for outbound legal notices; generate relay proofs.
Template the subject line: e.g., “ISDA 2002 – Section 5/6 Notice – [Counterparty] – [Agreement Date]” to avoid “lost in noise” disputes.
Use PDF + text body: Attach the notice on letterhead (PDF) and mirror the operative language in the email body.
Log the relay artifact: Save the MTA relay record, time-stamped in UTC and recipient local time.
Second channel if feasible: Courier/hand delivery to the Part 4(a) address; keep the airway bill/time-stamp.
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:
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).
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.
Close-out quotes (Section 6(e)(ii)(3)(A), mid-market events): Third-party quotations for Close-out Amountmust 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”)
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.
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.
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.
Sanctions overlay:
Calibrate representations and Termination Events to avoid shutting down legitimate trade, but preserve termination where Illegality or sanctions truly bite.
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.
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
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.
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
Negative Interest Under the ISDA 1995 Credit Support Annex: What the (2019) Court of Appeal Decision Means for 2025—and How TRW Structures Your CSAs
Audience: Bangladesh-origin banks, NBFIs, corporates, and funds that enter into OTC derivatives (FX, rates, commodities) with EU/UK counterparties and continue to hold or renegotiate legacy ISDA 1995 English law Credit Support Annex (CSA) frameworks. Core message: The English Court of Appeal (2019) confirmed that the standard form ISDA 1995 CSA does not oblige a Transferor of cash collateral to pay “negative” interest. That holding still matters in 2025 for legacy books, back-to-back hedges, and close-out valuations—especially where treasury teams confront rate-regime pivots, cross-currency funding, and mixed documentation (1995 CSA on some lines; 2016 VM CSA on others). This article explains the decision, dissects its reasoning, and translates it into practical drafting and operational playbooks that TRW implements for clients in Dhaka, London, and Dubai.
1) The Business Problem That “Negative Interest” Exposes
Cash collateral posted under a CSA accrues interest. In “normal” rate environments, interest is positive, and the contract typically spells out who pays whom. But when benchmark rates dive below zero, a conceptual tension arises: should the receiver of cash collateral (Transferee) pay interest to the poster (Transferor)? Or does the contract contemplate only positive interest flowing in the opposite direction?
Why this matters in 2025, even after rate normalization in many economies:
Legacy contracts: Thousands of relationships still run under ISDA 1995 CSAs (some amended piecemeal), especially for long-dated infra hedges and back-to-back structures.
Volatility is cyclical: Rate regimes can slip below zero again under stress. “We’ll never see negatives again” is not a legal position.
Pricing & disputes: If your CSA is silent (or asymmetric) on negative interest, P\&L transfers, margin calculations, and close-out amounts can shift materially during a rate shock.
Cross-border books: Bangladesh-origin treasuries hedging in USD/EUR/GBP with EU/UK dealers need clarity so ops, audit, and lenders can trust the collateral engine across cycles.
2) A Quick Refresher: What the ISDA 1995 English Law CSA Does
The 1995 English law CSA is a title-transfer collateral annex. In the vanilla setup:
The Transferor posts cash (or securities) to the Transferee when exposure calls arise.
The Transferee typically owes the Transferorpositive interest on posted cash at a defined benchmark ± a spread (the Price Differential / Interest Amount concept).
Collateral is re-transferred when exposure drops or upon termination, subject to netting and thresholds.
Crucial limitation: The 1995 form was drafted with a positive-rate paradigm. It contains a detailed mechanism for paying positive interest on cash collateral but is silent on the reverse flow that would operationalize negative interest.
3) The 2019 Court of Appeal Decision—Plainly Stated
In 2019, the English Court of Appeal confirmed that the standard ISDA 1995 CSA does not provide for payment of “negative” interest by a Transferor of cash collateral. The Court reached the same end result as the High Court but criticized the lower court for being “too simplistic” in how it got there. The appellate court’s three pillars:
Textual anchor in paragraph 5(c)(ii) The clause that deals expressly with positive interest is the “obvious place” one would expect to see negative interest if intended. It isn’t there. That asymmetry strongly indicates no obligation to pay negative interest arises under the standard form.
User’s Guide and background materials The court treated the ISDA User’s Guide (1999) and surrounding best-practice commentary as background showing the market did not contemplate negative interest payments under the 1995 CSA. Even post-contract materials (near contemporaneous best-practice notes) were considered relevant to understanding market thinking.
Contract read as a whole / business common sense Taking the CSA in its entirety, there is nothing signalling that negative interest was meant to be paid. If rates later turned negative, that was an unforeseen market development—not a gap for the court to fill by implying reciprocal negative interest obligations.
Bottom line: Under the standard 1995 CSA, no contractual obligation arises to pay negative interest on cash collateral from the Transferor to the Transferee.
4) Why the Decision Still Matters in 2025
Even though many relationships migrated to the 2016 ISDA VM CSA (which better reflects modern margin regimes), you may still have:
Legacy hedges under a 1995 CSA (possibly with bespoke amendments).
Back-to-backs where one leg uses a 1995 CSA (e.g., an old project finance hedge) and the other uses a modern VM CSA.
Mixed portfolios where operational teams rely on shared procedures across different annex types.
For any book where the 1995 CSA remains relevant, the 2019 decision offers litigation-grade clarity: unless you amended the annex or adopted a specific protocol, negative interest is not contractually owed by the Transferor.
5) What the Courts Actually Valued in the Reasoning
Understanding the legal method helps you draft stronger positions:
Location matters: When a contract has a specific clause for interest (paragraph 5(c)(ii)), courts expect both sides of the coin (positive and negative) to be spelled out there if intended. Silence where you’d expect text is meaningful.
Market documentation context: English courts give respectful weight to industry standardization, especially for ISDA forms shaped by thousands of practitioners.
Common sense over mechanical symmetry: The court refused to force “symmetry” just because positive interest exists; it looked at intended economics and document design, not math for math’s sake.
6) Practical Implications for Bangladesh-Origin Parties
A) If you hold a 1995 CSA (unamended):
No negative interest payable by the Transferor on posted cash, absent bespoke drafting to the contrary.
Dispute avoidance: Ensure your ops and counterparty teams align on this; memorialize it in a side letter or portfolio memo so staff turnover doesn’t resurrect old misunderstandings in a future rate shock.
Pricing awareness: Dealers may factor the asymmetry into pricing, especially if they perceive one-way economics when rates dive. Understand the spread trade-off if they push you to modernize.
B) If you face a dealer asking to “turn on” negative interest under a 1995 CSA:
Resist “implied term” arguments. The appellate decision is strong authority that implied reciprocity isn’t there.
Consider bargaining: You can negotiate commercial give-and-take (e.g., adjustments to Minimum Transfer Amounts, eligibility, or haircuts) if you agree to negative interest prospectively—but put it in writing with precise drafting.
C) If you are migrating to a 2016 VM CSA:
Treat the 1995 annex’s negative-interest position as legacy risk and design the cutover explicitly.
Train treasury on which annex governs which trades, especially during transition periods when both annexes sit side-by-side.
D) If you run back-to-backs (intragroup or client-to-street):
Mismatches between a 1995 annex on one leg and a 2016 VM CSA on the other can generate P\&L noise in stress scenarios. TRW maps the cash-flow stack, sets internal transfer pricing, and—if needed—re-papers the vulnerable leg.
7) The 2014 ISDA Collateral Agreement Negative Interest Protocol—What It Did (and Didn’t)
The 2014 Protocol was ISDA’s pragmatic answer to market uncertainty. It gave counterparties a standardised way to amend interest provisions in certain collateral agreements so that negative interest could be recognized contractually.
But note:
Protocol adherence is voluntary and relationship-specific. If you didn’t adhere (or your counterparty didn’t), your 1995 CSA may remain unamended.
Even where adhered, operational clauses (valuation times, netting sequences, rounding, floor logic) still need to be understood by treasury and middle office.
TRW’s position: Don’t assume your CSA reflects the Protocol. We audit the signed adherence list, the Annex inventory, and any bespoke amendments your teams made across years of renewals.
8) The 2016 ISDA VM CSA: Designed for Modern Margin, Not for Guesswork
The 2016 VM CSA (English law) modernised the daily variation margin framework and sits comfortably with post-crisis risk mitigation regimes. Among the benefits:
Cleaner alignment of daily VM calculations, collateral eligibility, and haircuts.
Improved scaffolding for interest mechanics, reducing ambiguity across rate regimes.
Operational clarity for call windows, settlement cut-offs, and dispute processes, which matter for Dhaka–Dubai–London time-zone choreography.
However: If you run a mixed estate (some 1995 CSAs; some 2016 VM CSAs), you still need policy and process differentiation. The 2019 decision remains relevant for any pocket where the 1995 form persists.
9) Drafting Tactics TRW Uses in 2025
When we (re)paper your CSA stack, we focus on clarity, symmetry where intended, and operational truth:
Define interest economics expressly
If negative interest is intended, draft it plainly: who pays whom, at which benchmark ± spread, with what floor.
If not intended, state a zero floor explicitly to eliminate interpretive drift.
Disaggregate VM vs IM
VM interest mechanics can differ from segregated IM (where interest often belongs to posted collateral owner, subject to custodian/platform terms).
Keep IM economics and ops (segregation, reuse bans, control agreements) out of VM clauses to avoid cross-contamination.
Currency-aware haircuts and floors
If VM posts occur in USD against EUR exposures (or vice versa), fix FX haircut logic; decide if interest rates follow the collateral currency, exposure currency, or a specified benchmark.
Rounding, MTA, and day-count conventions
These “small” terms drive real cashflows. Align day-count to the benchmark used for interest; ensure Minimum Transfer Amounts prevent noise but don’t cause cliff-edge calls.
Dispute mechanics
Name the valuation agent(s) and data sources; set a tolerance; provide escalation and interest on adjustments to avoid relationship damage during volatility spikes.
10) Operational Reality for Bangladesh Treasuries
A) Time-zone choreography Daily calls often reference London close; settlements must clear through correspondent banks before cut-offs. We map Dhaka banking windows against Dubai and London to stop settlement fails.
B) Liquidity staging Posting VM in USD/EUR/GBP while revenues accrue in BDT requires offshore pools and standing lines. TRW’s Dubai/London teams help set funding rails that comply with Bangladesh Bank rules and avoid “daylight” liquidity gaps.
C) Board-level governance Update the Derivatives Use Policy: state whether negative interest can arise (and under which annexes), define authorized signatories, and require quarterly reporting on collateral P\&L.
Scenario 1: Rates lurch negative in one currency for six months. You run a 1995 CSA (unamended).
Effect: No negative interest obligation from you (as Transferor) under the standard form.
Action: Communicate position early; issue a relationship note to counterparties; monitor for pricing pushback.
Scenario 2: Back-to-back hedging with a client: upstream 2016 VM CSA (negative interest allowed), downstream 1995 CSA (silent).
Effect: Possible P\&L mismatch in a negative-rate window.
Action: Insert inter-affiliate adjustment or transition downstream annex to a modern form; until then, set internal accrual to cushion basis risk.
Scenario 3: Counterparty proposes a quick side letter “recognizing negative interest going forward.”
Effect: Might be fine, but watch for spill-overs (e.g., changes to benchmark fallback, floors, FX haircuts) hidden in drafts.
Action: TRW redlines to confine the change to exactly what’s intended; consider a pricing concession in your favour.
Scenario 4: Close-out during a negative-rate month.
Effect: Annex asymmetries can feed into the Close-out Amount calculus.
Action: Keep valuation statements, interest journals, and call logs clean and time-stamped; ensure the determination method under your ISDA Master is aligned with your records.
12) FAQs (2025)
Q1: Does the 2019 appellate decision mean negative interest is never payable under any CSA? No. It means the standard 1995 English law CSA doesn’t create that obligation. Parties can draft it in (or adhere to a protocol). Many 2016 VM CSAs articulate interest mechanics that handle zero floors or negatives explicitly.
Q2: If my 1995 CSA is silent, can a court imply a term for symmetry? The appellate court’s reasoning strongly disfavors implication where the text and market materials don’t support it. If you want symmetry, write it in.
Q3: We are an NFC- (non-financial counterparty below clearing thresholds) hedging with a UK dealer. Does any of this change? Your margin obligations, trading lines, and collateral economics still depend on the annex you actually signed. NFC status doesn’t override the contract.
Q4: If we adopt a 2016 VM CSA now, should we also retrospectively “fix” old trades under the 1995 CSA? Typically you don’t rewrite historic VM interest for closed periods. You can set a cutover date for interest mechanics and leave history as-is, unless there’s a bilateral commercial reason to restate.
Q5: What’s the simplest way to neutralize the risk without a full repaper? A short bilateral amendment that (i) floors interest at zero or (ii) defines negative-interest flows cleanly, with aligned benchmark/day-count and FX choices. Keep it tight; avoid accidental scope creep.
13) TRW’s 10-Point Playbook for 1995 CSA Estates
Inventory every annex by type, governing law, and counterparty; flag any 2014 Protocol adherence.
Classify annexes by interest mechanic (positive-only vs explicit negative treatment).
Map product and tenor to annex type; prioritize high-volatility or long-dated pockets.
Stress test interest flows under sample negative-rate paths (USD, EUR, GBP).
Identify mismatches in back-to-back hedges; propose internal transfer pricing or repaper where basis risk bites.
Draft a standardized zero-floor or negative-interest rider (two variants) for quick bilateral adoption.
Set ops SOPs: valuation times, call windows, escalation contacts; codify interest journals and audit trails.
Board policy: update the Derivatives Use Policy to state the official position on negative interest by annex type.
Train treasury/legal/middle office; run a table-top drill simulating a 6-week negative-rate episode.
Review annually (or on rate regime alerts); keep a live CSA dashboard.
14) Bangladesh, London, Dubai—Why TRW’s Tri-Hub Model Works
Dhaka: Local regulatory fit, Bangladesh Bank interfaces, board approvals, lender communications, and audit readiness.
London: English-law drafting, ISDA negotiation at dealer desks, and real-time handling of UK/EU market shifts.
Dubai:Liquidity staging in USD/EUR with time-zone overlap; custodian onboarding; contingency routes if London cut-offs collide with Dhaka banking hours.
Our multi-hub practice ensures the legal text and the daily plumbing (calls, interest booking, reconciliations) are consistent—so your documentation isn’t elegant on paper but brittle in operations.
“Rahman Power & Textiles Ltd.” maintained a legacy 1995 CSA with a European dealer for project-linked USD swaps. During a eurozone mini-shock, front-office feared negative EUR depo might reopen an old debate about negative interest on cash VM.
TRW actions:
Confirmed no negative interest obligation under the 1995 CSA; prepared a relationship note memorializing shared understanding with the dealer.
Proposed a concise zero-floor rider for prospectively clearer drafting (accepted without pricing change due to long-term relationship).
Updated SOPs and interest journals; ran a table-top drill. Outcome: The six-week episode passed with no disputes; auditors praised the documented policy and ledger clarity.
17) Board-Ready Checklist
[ ] Inventory annex types (1995 vs 2016 VM; English vs NY law) and protocol adherence.
[ ] Decide: maintain zero floor or adopt explicit negative-interest language prospectively.
[ ] Align benchmark, day-count, rounding, MTA with operations.
[ ] Update Derivatives Use Policy and lender communications.
[ ] Drill a negative-rate scenario across Dhaka–Dubai–London teams.
[ ] Install a CSA dashboard for oversight and incident logs.
The 2019 appellate ruling provided a durable, commercially sensible answer for a standard document drafted in a different era: under the ISDA 1995 English law CSA, negative interest is not payable by the Transferor of cash collateral—unless the parties say so. In 2025, the right approach is not to litigate metaphysics but to decide your economics and write them down—with interest floors, currencies, day-counts, and dispute mechanics tailored to your treasury’s reality.
TRW will map your annex inventory, design crisp riders, negotiate them in London, stage liquidity and operations in Dubai, and embed governance in Dhaka—so your collateral engine works the same on paper, in ledgers, and in court.
For further internal reading that complements this topic, see:
Time zones, cut-offs, day-counts drive real cashflows
Reduces disputes; avoids settlement fails
Dhaka–Dubai–London choreography; ledger codes
Governance
Policies must declare the house view
Audit and lender comfort
Update Derivatives Use Policy; quarterly dashboard
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
Send us your CSA inventory (even a simple list of counterparties and annex dates). We’ll return a one-page gap memo flagging where you stand on negative interest, and a draft zero-floor or negative-interest rider tailored to your treasury and documentation stack.
ISDA Master Agreement With EMIR-Compliant Credit Support Annex (CSA): A Practical Guide for Bangladesh-Origin Banks and Corporates
Executive Summary. For Bangladesh-origin banks, non-bank financial institutions (NBFIs), corporates, and investment funds that trade OTC derivatives with EU/UK counterparties, the ISDA Master Agreement and an EMIR-compliant Credit Support Annex (CSA) are no longer “nice to have”—they are mission-critical legal instruments. EMIR’s risk-mitigation regime requires daily Variation Margin (VM) for uncleared OTC derivatives and, above defined exposure thresholds, Initial Margin (IM) with strict segregation and no rehypothecation. These obligations fundamentally shape how Bangladeshi parties negotiate credit terms, collateral schedules, eligibility criteria, documentation workflows, custodian setups, and operational controls.
This guide explains (i) what “EMIR-ready” documentation looks like in practice, (ii) how the ISDA 2016 VM CSA and IM documentation suite are adapted for Bangladesh-linked counterparties, and (iii) how TRW Law Firm helps clients negotiate the commercial levers—Minimum Transfer Amounts (MTA), Thresholds, haircuts, eligible collateral, dispute resolution, custodial models, and governing-law choices—while aligning with local banking rules, FX controls, and treasury realities. We also map the Dubai and London contexts given TRW’s cross-border footprint and typical trading flows with EU/UK dealers.
1) Why EMIR Matters to Bangladesh-Origin Parties
Although EMIR is an EU regulation, it “travels” contractually through your EU/UK dealers and investment banks. If your counterparty is in the EU (or UK with EMIR-onshored rules), they must apply the uncleared margin regime to your trades unless a specific exemption applies. That means you, as a Bangladesh-linked corporate or bank, will likely sign ISDA Master documentation with EMIR-compliant credit support terms.
Key implications:
Daily VM on uncleared trades at market value, exchanged in cash or approved collateral with prescribed haircuts and currency guidelines. (EUR-Lex)
IM for groups above the AANA (Average Aggregate Notional Amount) thresholds; IM must be segregated with an independent custodian and cannot be rehypothecated—raising operational and banking-arrangement complexity. (eba.europa.eu)
A cap on Minimum Transfer Amounts—the combined MTA for IM and VM must not exceed EUR 500,000 (or equivalent) across the relationship (you can split per margin type, but the sum cannot exceed the cap). (EUR-Lex)
Classification (FC, NFC+, NFC- under EMIR Refit) determines scope for clearing and certain risk mitigation techniques; many real-economy corporates in Bangladesh that hedge FX or rates with EU dealers are NFCs, with NFC+ triggering wider duties. (esma.europa.eu)
Phase-in has ended: the IM regime is now in a “steady state”; Phase 6 went live in September 2022, leaving documentation and model validation (SIMM or schedule) work as an ongoing compliance discipline. (tractionfintech.com)
Bottom line: If you face EU/UK dealers, your ISDA and CSA terms will be shaped by EMIR—even if your treasury sits in Dhaka or Chattogram, and your underlying commercial exposure arises from Bangladesh trade, supply chain, or project finance activity.
2) The Building Blocks: ISDA Master + Schedule + CSA
A robust OTC derivatives legal stack for cross-border trading generally includes:
ISDA Master Agreement (1992 or 2002 version) Establishes the overarching contractual architecture (single agreement, netting, events of default, termination, tax provisions). It is typically governed by English law or New York law, depending on your trading relationships and product set.
ISDA Schedule Tailors the Master’s boilerplate to your credit and operational reality, adding credit support terms, tax gross-up carve-outs, set-off, governing law, cross-default thresholds, additional termination events, and sanctions representations.
Credit Support Annex / Deed
2016 ISDA Credit Support Annex for Variation Margin (VM) (English law, title-transfer) or the New York law VM CSA—to implement daily VM exchange. (isda.org)
ISDA documentation suite for IM (commonly Credit Support Deed (CSD) or custodian triparty agreements), where required by EMIR, to implement two-way IM, segregation, eligibility schedules, and dispute resolution mechanics. (handbook.fca.org.uk)
Why 2016 VM CSA matters: The 2016 form modernized collateral terms for the uncleared VM regime, replacing the legacy 1994/1995 forms many banks once used, and standardised daily cash/eligible collateral flows and haircuts for EMIR/US rulesets. (isda.org)
3) Variation Margin (VM): The Daily “P\&L” Settler
Trigger & mechanics. VM covers current exposure—the day-to-day change in the mark-to-market of your uncleared trades. It is usually called daily, subject to thresholds, MTA, and rounding amounts, then settled same-day or T+1 in agreed collateral currencies/instruments.
Choices Bangladesh-origin parties negotiate:
Eligible collateral: Cash in major currencies is standard; high-quality government bonds may be permitted with haircuts. Parties often prefer cash for operational simplicity, FX manageability, and clean title transfer under the VM CSA. (isda.org)
Haircuts & FX: Haircuts reflect collateral type and potential currency mismatch (collateral vs exposure currency). Agreeing collateral currency sets that align with your treasury (e.g., USD, EUR, GBP) reduces basis risk and ops friction. (EUR-Lex)
Threshold and MTA: Under EMIR, your combined MTA (IM + VM) must not exceed EUR 500,000 (or equivalent). Many dealers push for low or zero thresholds for VM (pure exposure settlement), with MTA set within the cap to limit micro-movements. (Legislation.gov.uk)
Interest on cash collateral: Define interest rate or pricing spread for cash posted/received (e.g., ESTR, SOFR, or a commercial rate). This can have tangible P\&L effects over time.
TRW practice note. Where your functional currency is BDT but your trading currency and collateral currencies are USD/EUR/GBP, we design VM terms that minimize FX slippage. For example: VM in USD with defined FX cut-off windows and operational settlement cut-offs that account for Bangladesh banking hours, correspondent banking routes, and holiday calendars.
4) Initial Margin (IM): Segregation, Custodians, and the AANA Gate
Who is in scope? If your group exceeds the AANA threshold (currently steady-state €8bn), you and your counterparty must calculate and exchange IM bilaterally. IM is two-way, independent of daily P\&L, and calibrated to potential future exposure over a 10-day margin period (or as per the RTS/product), often via ISDA SIMM or schedule. (eba.europa.eu)
Segregation and reuse ban. Under EMIR, IM must be segregated and cannot be rehypothecated by the collecting party. The go-to solutions are:
Third-party (tri-party) custodians with control agreements;
Bilateral custody arrangements with no right of reuse; and
Operational playbooks for calls, substitutions, interest, and disputes. (handbook.fca.org.uk)
Documentation. Expect a separate IM Credit Support Deed/Annex (English or NY law) and a custody control agreement. The 2016 VM CSA is not sufficient for IM: VM can be title-transfer, but IM must be held segregated. (handbook.fca.org.uk)
Bangladesh-specific pinch-points TRW navigates:
Custodian footprint: Selecting global custodians that accept Bangladesh-origin entities, handle KYC, and support your chosen governing law.
Funding IM: IM is a liquidity drain. We model the cost of collateral (cash vs government bonds) and how it interacts with your working capital, trade cycles, and FX availability.
Operational daylight: Call windows aligned to Dhaka time (UTC+6), avoiding missed settlements due to time-zone mismatches with London or continental Europe.
5) Minimum Transfer Amount (MTA) and Thresholds—Commercial Levers That Matter
The MTA is the smallest incremental margin movement you must make. Under EMIR, the sum of the IM-MTA and VM-MTA cannot exceed EUR 500,000 (or equivalent) across the relationship (you may split between IM and VM, but the aggregate cap still applies). (EUR-Lex)
Negotiation strategy:
Avoid micro-movements that clog operations (e.g., set VM-MTA at a pragmatic level), but do not breach the 500k combined cap.
Use product mapping (FX, rates, commodities) to set differentiated MTAs or rounding only if operationally justified and the total cap is respected.
Thresholds for VM are typically set to zero by EU dealers; where non-zero thresholds are floated, be mindful of credit charges or pricing give-ups you may pay elsewhere.
6) Eligible Collateral, Haircuts, and Concentration Limits
Eligible collateral lists tend to include cash in major currencies and high-quality sovereign paper (subject to haircuts). Many corporates prefer cash to simplify valuation, interest, and substitution.
Haircuts account for market and FX risk—for example, posting USD cash against EUR exposures may carry FX mismatch layers that need careful CSA drafting to avoid hidden volatility. Large dealers also push concentration limits (no over-reliance on one issuer or currency) to manage wrong-way risk. (EUR-Lex)
TRW tip: Where treasury prefers USD as the collateral currency, we draft the FX haircut treatment and substitution rights with precision, including calendar cut-offs and valuation time definitions that match Dhaka, Dubai, and London banking days.
7) Dispute Resolution, Valuation, and Interest Mechanics
Daily valuation and call disputes are central to a smooth VM/IM regime:
Define valuation agent(s), pricing sources, and timing (e.g., London close) with clarity.
Build a dispute workflow: thresholds for tolerances, escalation contacts on both sides, and a timely interest adjustment mechanism on resolved disputes.
Specify interest on cash collateral (the “Interest Amount” or “Price Differential”)—a non-trivial P\&L item over a year.
Operational documentation often includes margin procedures and playbooks: which email addresses, margin platforms (e.g., Acadia), and cut-off times apply. TRW ensures your operations, treasury, and legal teams are aligned on the same parameters reflected in the signed CSA suite.
8) Governing Law, Netting, and Close-Out—Choosing the Right Spine
For international derivatives, most Bangladesh-linked parties adopt English law ISDA architecture when trading with EU/UK dealers (or New York law for US-facing portfolios). The critical points are:
Netting enforceability: The backbone of credit mitigation—your Schedule should include netting confirmations and cross-default tolerances that work with your Bangladesh credit agreements and group treasury.
Close-out methodology:Market Quotation vs Loss, updates around Determination mechanics, and links to hedging policy.
Sanctions & representations: Ensure you can comply with EU/UK/US sanctions undertakings without cutting across legitimate Bangladesh trade (e.g., permitted commodity imports).
TRW aligns your ISDA terms with your secured lending, trade finance, and bank regulatory profiles in Bangladesh—important where your lenders (or Bangladesh Bank policies) scrutinize derivatives positions alongside loan covenants and FX exposure.
9) EMIR Classifications (FC, NFC+, NFC-) and What They Mean for You
Under EMIR Refit, financial counterparties (FCs) and non-financial counterparties (NFCs) face different duties. NFC+ status (i.e., NFCs that exceed clearing thresholds) attracts more obligations (e.g., clearing certain products, timely confirmations, portfolio reconciliation, dispute resolution, margining, reporting via counterparties or TRs). NFC- face lighter obligations but still must meet VM on uncleared trades where applicable with EU dealers. (esma.europa.eu)
Action point: Proactively assess your AANA and clearing thresholds during budgeting cycles. Avoid inadvertent “step-ups” in duty by breaching thresholds without having documentation, custodians, and operations ready.
10) The Dubai and London Contexts—Why They Matter to Bangladesh Parties
London remains a global hub for FX and rates derivatives; many Bangladesh-origin hedgers (importers/exporters, EPC contractors, fuel buyers, airlines, telcos) face UK-regulated dealers applying onshored EMIR rules. Dubai offers proximity and banking relationships that facilitate custody, multi-currency cash management, and regional trading hours aligned with Dhaka.
TRW, with teams spanning Dhaka, London, and Dubai, designs tri-jurisdiction operating models for:
Custody selection: Global custodians accessible from Dhaka with KYC familiarity.
Cash pooling: USD/EUR liquidity management between Bangladesh and offshore accounts to fund VM/IM without destabilizing onshore working capital.
Time-zone choreography: Margin call windows that avoid settlement failures.
11) Cross-Border Compliance With Bangladesh Realities
Even though EMIR is foreign law, Bangladesh-linked players must balance:
Bangladesh Bank FX controls, trade documentation, and banking channels for cross-border collateral movements;
Board approvals and treasury policies for derivatives usage;
Audit and disclosure requirements; and
Counterparty risk and sanctions compliance in procurement and supply chains.
TRW drafts ISDA + CSA in a way that fits your local obligations and evidence needs (board minutes, policy annexes, internal approvals), and we map operational steps to your relationship banks.
For background reading on secured financing and regulatory alignment (all internal to TRW’s site), see:
Collateral currency set: Prefer USD/EUR/GBP aligned to exposure; state valuation times and cut-offs that work from Dhaka.
Haircuts & FX: Cap FX haircut add-ons where pricing already reflects cross-currency risk.
MTA: Set a pragmatic MTA (e.g., 100k–250k equivalent) to avoid operational friction while observing the EU-mandated aggregate 500k cap for IM+VM MTA. (Legislation.gov.uk)
Interest on cash collateral: Negotiate an objective benchmark (e.g., SOFR for USD) with a small spread where justified.
B) IM Terms (if in scope)
Custodian choice: Select a tri-party that accepts Bangladesh corporates; negotiate fee schedules and turnaround times.
Concentration limits: Avoid overly tight caps that force constant collateral substitutions.
SIMM vs schedule: If SIMM, ensure your model access (vendor or in-house) is ready; if schedule-based, test conservatism on your portfolio.
Disputes: Low thresholds with fast escalation to avoid stand-offs that could freeze your trading lines.
C) Schedule & Master
Governing law: English law typically harmonizes best with EU/UK dealers; ensure Bangladesh-law interfaces (e.g., security, set-off) are mapped.
Sanctions reps: Calibrate to avoid catching legitimate trade; include materiality qualifiers where appropriate.
Tax: Confirm withholding positions and any gross-up carve-outs consistent with your finance structures.
13) Operating Your CSA: People, Process, and Platforms
People. Nominate named contacts for calls, disputes, and settlements in treasury, legal, and middle office. Maintain a holiday calendar matrix across Dhaka, Dubai, London, and dealer centers.
Process. Adopt standard operating procedures: daily MTM check, exposure aggregation, call verification, confirmation, settlement booking, and ledger reconciliation. Record interest accrual on cash collateral and substitution protocols for securities.
Platforms. Your counterparties may require using margin messaging utilities. Ensure your KYC and onboarding with a tri-party custodian are complete well before AANA thresholds are met.
14) Common Pitfalls—and How TRW Helps You Avoid Them
MTA breaches. Parties sometimes split IM-MTA and VM-MTA without tracking the aggregate cap—which must not exceed EUR 500k equivalent. TRW stress-tests the drafts to ensure compliance. (EUR-Lex)
Underestimating IM plumbing. IM is not just numbers; it’s legal + operational (custodian contracts, wiring, substitutions). TRW builds the end-to-end checklist, including internal approvals and policy updates.
FX leakage in VM. Posting EUR collateral for USD exposures (or vice versa) can embed FX volatility into collateral P\&L. We align CSA currency sets with your hedge book.
Unclear valuation/disputes. Vague pricing sources or window timings cause avoidable disputes. We set objective sources, intraday snapshots, and escalation triggers.
Sanctions representations too broad. Over-broad reps can force unnecessary trade stops. We calibrate language and materiality to reflect legitimate Bangladesh trade.
Threshold creep to “buy” pricing. Some counterparties trade economic price for higher thresholds that later strain liquidity during stress. TRW models “all-in” economics (spread + collateral burden).
15) Case Study (Hypothetical, Bangladesh-Origin Corporate)
The scenario. A Dhaka-headquartered conglomerate (“Rahman Textiles & Power”) hedges USD/BDT FX and USD interest rates with EU and UK dealers to manage purchase and project finance exposures. Rapid growth means they approach the AANA line for IM.
TRW’s solution.
Documentation: English law ISDA 2002 + 2016 VM CSA, pre-negotiated IM Deed and tri-party control with a global custodian.
Collateral strategy: USD cash for VM; IM in USD cash + select sovereigns with concentration limits.
Ops: Dhaka treasury runs daily margin; Dubai office provides global banking rails; London counsel handles model validation and custodian negotiations.
Result: No settlement fails across the first volatile quarter; pricing sustained; audit satisfies board policy and lenders.
(Names are generic.)
16) Frequently Asked Questions (FAQs)
Q1. Do Bangladesh corporates always need IM? Not automatically. IM applies when both parties’ AANA exceed the threshold (steady-state €8bn). Smaller hedgers may face VM only. Your EU/UK counterparty will still require VM, daily. (eba.europa.eu)
Q2. Can we set separate MTAs for VM and IM? Yes—but their sum cannot exceed EUR 500,000 equivalent under EMIR. Plan your split to match operational capacity without breaching the cap. (EUR-Lex)
Q3. Must IM be held at a third-party custodian? Yes, IM must be segregated and cannot be rehypothecated. This entails a custody control agreement, KYC, and funding workflows. (handbook.fca.org.uk)
Q4. Can VM be by title transfer of cash? Yes. The 2016 VM CSA (English law) commonly uses title transfer of cash for operational simplicity. (isda.org)
Q5. What if our treasury prefers USD but exposure is in EUR? Define eligible collateral and FX haircut rules carefully. Sometimes it’s worth posting in the exposure currency to reduce FX noise; other times USD liquidity wins—your CSA should reflect the strategy.
Q6. How do EMIR classifications affect us? Your NFC+/NFC- status influences clearing and some techniques. Even NFC- can face VM with EU dealers. Re-assess classifications regularly. (esma.europa.eu)
17) Implementation Roadmap With TRW
Phase 1 — Diagnostic (2–4 weeks, depending on complexity)
[ ] Train Treasury/Legal/Ops; dry-run settlement and substitution.
20) Conclusion
An ISDA Master Agreement with an EMIR-compliant CSA is not merely legal paperwork—it is a credit, liquidity, and operational engine that supports competitive pricing and stable market access for Bangladesh-origin hedgers. Getting the VM and IM architecture right—from MTA caps to segregation mechanics—protects your balance sheet and preserves access to EU/UK liquidity during market stress.
TRW Law Firm structures, negotiates, and operationalises this end-to-end: from Dhaka board approvals and Bangladesh Bank considerations to English-law drafting, custodian onboarding, and training. If your business hedges FX, interest rates, or commodities with EU/UK dealers—or plans to—we will set you up to trade confidently, compliantly, and efficiently.
Structured Summary Table (for quick reference)
Topic
What It Means
Your Decision Points
TRW’s Role
ISDA Master (1992/2002)
Core contract: netting, EoD, tax, termination
Choose governing law (often English); align with local facilities
Currency set, FX haircut rules, concentration limits
Treasury-aligned drafting and FX-risk minimisation (EUR-Lex)
Valuation & Disputes
Daily MTM; fast dispute workflows
Sources, timing, escalation
Build procedures and playbooks; train teams
Bangladesh Interfaces
FX controls, board approvals, audit
Policy updates; evidence trail
Local regulatory fit and lender comfort letters
London & Dubai Hooks
Dealer access; liquidity rails
Time-zone choreography; custody
Orchestrate multi-hub operations for resilience
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
