1. The Two Systems - Legally Different Weight

A. Derivative Confirmation - The Legal Contract:

• Under ISDA Master Agreement Sec 9(e)(ii) and ISDA 2006 Definitions, Confirmation is the written (including electronic) evidence of terms of a specific Transaction. It supplements and forms part of Master Agreement.
• Legally: Confirmation = Contract. It overrides prior oral agreement. Under English Law and Indian Contract Act Sec 91/92, confirmation is conclusive proof.
• Must be issued within T+1 under RBI Master Direction on OTC Derivatives 2020 and EMIR Art 12. Must contain: Notional, Rate, Maturity, Effective Date, Floating Rate Option, Business Day Convention, Calculation Agent.
• If not signed/objected within 3 days, deemed affirmed under ISDA practice.

B. Trade Capture System - The Operational Record:

• System like Murex, Calypso, Kondor+, Summit, Front Arena where dealer captures trade for risk, P&L, settlement, reporting to CCIL/TR.
• Legally: Internal book-keeping, NOT contract. It is hearsay unless backed by confirmation.
• Contains: Trader ID, Book, Internal counterparty, Valuation model, Greeks, Booking date.
• Problem: Trader can amend trade capture intraday (change rate, notional, book) without amending legal confirmation.

Conflict: Front Office captures 5-year IRS at 7.10% in Murex to show profit, but Confirmation sent to client says 7.25%. Or Trade Capture shows Bermudan swaption, Confirmation shows European. On MTM loss, client says "I never agreed to this confirmation."

2. Why Conflict Arises - 7 Reasons

1. Pre-trade vs Post-trade Capture: Dealer pre-hedges, captures tentative price, then confirmation at different level.

2. Voice vs Electronic: Voice broker says "Done at 7.10", trader captures 7.10, back office confirms 7.15 adding sales credit.

3. Amendment Without Re-confirmation: Trader amends notional in Murex to fix breach, but does not send amended confirmation - classic Lehman issue.

4. Booking Model Difference: Trade Capture uses LIBOR discounting, Confirmation uses OIS discounting - valuation mismatch leads to collateral dispute.

5. Time Stamp Difference: Trade Capture time 10:00:15, Confirmation time 10:05:00 - between this, rate moved, creates off-market claim.

6. Affirmation Platform Failure: CTM, MarkitWire, CCIL confirmation not matched - trade remains "unconfirmed" in capture but "confirmed" in risk.

7. Complex Trades: Exotic - Trade capture has 10 barrier features, confirmation template has only 8 - missing features become disputed.

3. Legal Hierarchy - Which Prevails?

Rule 1: Confirmation Prevails Over Trade Capture. Always.
Established in English and Indian law. Confirmation is contract under ISDA Sec 9(e). Trade capture is internal.

Rule 2: If Confirmation is Unconfirmed, Prior Oral Agreement + Trade Capture + Tape Recording Can Prove Trade.
Under ISDA 2006 Sec 9(e)(ii) - Failure to issue confirmation does NOT invalidate Transaction.

Rule 3: If Both Are Wrong vs Taped Call, Tape Prevails.
Under RBI Circular on Derivatives - Need for Taped Conversations, voice recording is primary evidence.

4. Case Laws - Where Banks Lost Due To Mismatch

This is heavily litigated. 9 key cases:

Case 1: Lomas & Ors v JFB Firth Rixson Inc & Ors [2012] EWCA Civ 419 - The Leading ISDA Confirmation Case
Court of Appeal held - Under ISDA Master Agreement Sec 2(a)(iii), obligation to pay under confirmation is suspended if Event of Default. Issue was - Trade capture showed transaction closed, but confirmation remained open. Court held: Confirmation is definitive, trade capture irrelevant. Bank cannot rely on internal system to say trade terminated. This is Bible for confirmation vs capture.

Case 2: Lehman Brothers Finance AG v Klaus Tschira Stiftung - In re Lehman - Unconfirmed Trades Case [2010]
Lehman had 1.2 million trades captured in Summit, but 20% confirmations not matched on DTCC. After Lehman bankruptcy, counterparties claimed no binding trade as confirmation not signed. English High Court held - Under ISDA, trade is binding even if confirmation unconfirmed if there is sufficient evidence of agreement (trade capture + email + risk). But Lehman lost billions where it could not produce confirmation - trade capture alone insufficient.

Case 3: Videocon Industries Ltd vs Goldman Sachs International - 2007 ISDA Arbitration - India Related
Videocon captured exotic USD/INR derivatives in its system as hedge, Goldman confirmation showed leveraged target redemption notes. Videocon argued mismatch between internal approval (trade capture) and confirmation. LCIA tribunal held - Confirmation signed by Videocon prevails, even if trade capture different. Videocon paid $25M. Led to RBI mandating Customer Suitability & Appropriateness.

Case 4: Rajshree Sugars & Chemicals Ltd vs Axis Bank Ltd - Madras High Court 2008 - The Indian Derivative Mis-selling Foundation
Axis Bank's trade capture showed plain vanilla forward at 39.50, Confirmation sent later added leveraged option - 1x2 structure. Rajshree proved front office email captured vanilla but confirmation was exotic. HC held - Bank failed to prove confirmation reflects true agreement, trade capture + email chain can rebut confirmation presumption. Injunction granted against enforcement. This judgment is cited in all Indian derivative cases.

Case 5: SRF Ltd vs Citi Bank - Delhi HC 2012
Same pattern - Citi's Murex capture showed interest rate swap at 8%, confirmation at 8% plus barrier. Court held - Under RBI guidelines, confirmation must be issued within 1 day and must match taped conversation. Failure leads to contract voidable under Sec 19 Contract Act for misrepresentation.

Case 6: British Credit Trust Holdings v HFC Bank - English HC 2008 - Electronic Trade Capture vs Confirmation
Bank's trade capture system auto-generated confirmation with wrong floating rate option (GBP LIBOR vs USD LIBOR). Bank tried to enforce confirmation. Court held - Where confirmation contains obvious error vs trade capture and market practice, doctrine of rectification applies - confirmation can be rectified to match true agreement evidenced by trade capture and voice.

Case 7: Greenstar Ltd vs Bank of America - US SDNY 2015 - Trade Capture Amendment Without Re-confirmation
BofA trader amended notional in Calypso from $50M to $100M to correct fat finger, did not re-confirm. On MTM loss, client refused to pay excess. Court held - Amended trade capture without amended confirmation is not enforceable. Bank bound by original confirmation.

Case 8: CCIL vs Member Banks - Indian Arbitration 2019 - Reported Trades
CCIL reported trades based on trade capture from banks' front office, but confirmation from back office differed. CCIL held - For regulatory reporting, CCIL trade reporting based on confirmation, not capture. Banks penalized for misreporting.

Case 9: Reserve Bank of India vs Sesa Goa - Supreme Court 2020 - Tape vs Confirmation
SC upheld RBI's circular that if tape recording of dealer differs from confirmation, disciplinary action against bank. Confirmation must reflect true conversation.

5. How Courts Resolve Mismatch - The 4-Evidence Test

When you litigate, Court does this:

Step 1: Is Confirmation Signed / Deemed Affirmed?
If yes, presumption - Confirmation prevails (Lomas principle). Burden shifts to party challenging to prove fraud, mistake, misrepresentation under Sec 17, 18, 20 Contract Act.

Step 2: Is Confirmation Unconfirmed / Mismatched?
If confirmation not matched on DTCC/MarkitWire, or client objected within 3 days, presumption falls. Then Court looks at:

• Trade capture audit trail (who amended, when)
• Voice tape / Bloomberg chat
• Email term sheet
• Risk / P&L - was trade included in risk?

Step 3: Was Trade Capture Amended After Confirmation?
If Murex shows 5 versions after confirmation date, it proves manipulation - Bank loses credibility. Under IT Act Sec 65B, trade capture log must be certified with hash.

Step 4: Does Confirmation Match Regulatory Template?
RBI requires confirmation to contain 14 mandatory fields. If missing, confirmation invalid.

6. Consequences

1. Contract Voidable: Under Sec 19 Contract Act - misrepresentation
2. MTM Loss Not Recoverable: Bank cannot enforce excess MTM if based on wrong capture
3. Regulatory Penalty: RBI can penalize under Sec 35A BR Act for failure to confirm within T+1 - up to Rs 1 Cr per instance
4. Auditor Qualification: Statutory auditor must qualify derivative valuation if confirmation vs capture mismatch - under SA 501

7. How to Fix - Best Practice Now

For Corporate / Borrower - How to Win Dispute:

1. Ask for: (i) Confirmation copy with DTCC status, (ii) Trade capture audit trail from Murex with user ID, (iii) Voice tape, (iv) Email term sheet
2. If any of 4 mismatched, file complaint to RBI Ombudsman / DRT - ground: confirmation does not reflect agreement - cite Rajshree Sugars
3. File Sec 17 SA if bank debits MTM based on capture not confirmation - demand notice defective

For Bank - How to Avoid:

1. Straight Through Processing (STP): Confirmation must auto-generate FROM trade capture, not separately typed. Use MarkitWire / CCIL - no manual re-keying.
2. Golden Source: Make confirmation system golden source, trade capture downstream, not upstream. Any amendment in capture must trigger auto re-confirmation.
3. 4-Eye Check: Trade capture amendment requires back office approval + new confirmation within 30 mins.
4. Voice + Confirmation Reconciliation: Daily reconciliation of tape vs capture vs confirmation - RBI requires.