1. What It Means

Regulators require a bank to view one counterparty = one exposure, irrespective of where it sits.

Basel LEX Standard para 20: "A bank must aggregate exposures arising in trading book and banking book to calculate total exposure to that counterparty. Netting across books is not permitted."

Basel: "Banks did not always consistently measure, aggregate and control exposures to single counterparties across their books and operations."

Products that must be aggregated:

• Funded: term loan, working capital, overdraft
• Non-funded: LC, BG, SBLC
• Markets: derivatives - Current Exposure + PFE, total return swaps, repos
• Capital markets: bonds held, CP, underwriting commitments
• Prime brokerage / securities lending
• Off-balance sheet special purpose vehicles

Failure modes:

1. System silos - Loan system sees Rs 100cr loan, treasury sees $50m derivative PFE, trade finance sees $30m LC - no common Customer ID.
2. Not aggregating connected counterparties - Holding company, SPVs, family office counted separately.
3. Not aggregating product risk add-ons - Counting loan notional but ignoring derivative add-on.
4. Using net instead of gross - Basel says you cannot net banking and trading book.

Result: Bank thinks exposure is 15% of capital, actual aggregated is 35% > RBI limit 20% single / 25% group.

2. Indian Regulatory Framework

• RBI Large Exposure Framework 2019 (revised): Single counterparty 20% of Tier 1 capital base, group of connected counterparties 25%. RBI uses higher of sanctioned vs outstanding to arrive at exposure.
• RBI Master Directions on Credit Concentration: Banks must aggregate fund based + non-fund + investment + derivatives.
• Penalty example: RBI fined IndusInd Bank Rs 4.5 crore in Oct 2020 for non-compliance with exposure norms and IRAC norms.

In IL&FS, DHFL, Bhushan Steel cases, multiple banks had individual product exposures within limit, but group exposure breached when aggregated across lending + investment in NCDs + guarantees.

3. Case Laws & Enforcement Actions - This is Where Law Developed

Case 1: Archegos Capital Management vs Credit Suisse - The Textbook Failure

Archegos used total return swaps to build $160bn gross exposure on $36bn capital from 6 prime brokers.

"Its prime brokers — Credit Suisse, Nomura, Morgan Stanley, Goldman Sachs, and UBS — each saw only their own slice"
"Each bank saw only its own piece... None saw the aggregate picture."

Key finding: "banks did not combine or 'aggregate' the exposures to see the full picture of Archegos"

Consequences:

• Credit Suisse lost $5.5bn, shuttered prime brokerage, ultimately forced into UBS takeover .
• PRA fined Credit Suisse International £87 million in July 2023 for "significant failures in risk management and governance... in connection with exposures to Archegos" - specifically failure to aggregate swap exposure with margin lending and failure to aggregate across legal entities .
• FINMA report: Credit Suisse cut swap margins from 15-25% to 7.5% because it failed to aggregate .

This is now taught as BCBS example of LEX breach.

Case 2: JPMorgan Chase - London Whale 2012

CIO office held CDS index derivatives + cash bonds + structured notes. Each desk aggregated VaR separately. Synthetic Credit Portfolio not aggregated with banking book hedges. Loss $6.2bn. OCC fined JPM $300m, required remediation to aggregate exposures across products for VaR and stress testing.

Case 3: Citigroup OCC Consent Order $400m (2020)

OCC: Citi had "longstanding deficiencies in enterprise-wide risk management... failure to aggregate exposures across products and businesses leading to inability to identify concentrations." Required to build single counterparty exposure platform.

Case 4: Deutsche Bank Fed Fine $41m (2017) + $186m (2017)

Federal Reserve found Deutsche failed to aggregate Volcker covered fund exposures + trading exposures across US operations, leading to mis-reporting of large exposures.

Case 5: UK Insurance Aggregation - Legal Definition of Aggregation

While not banking, courts define what aggregation means:

AIG Europe Ltd v Woodman [2017] UKSC 18: Supreme Court held aggregation clause "similar acts or omissions in a series of related matters" requires real connection, not mere similarity. This principle is now used by banks to argue whether exposures to two SPVs should be aggregated - need common control / financial interdependence.

Lloyds TSB v Lloyds Bank Group [2003] 4 All ER 43: House of Lords allowed aggregation of thousands of mis-selling claims as single claim under aggregation clause. Shows regulators will force aggregation when there is common source.

4. How Regulators Expect You to Aggregate Correctly

Basel LEX Methodology:

1. Identify counterparty: Legal Entity + all entities under control >50% or economic dependency
2. Measure per product:
   • Loans: outstanding + undrawn committed
   • Derivatives: SA-CCR = RC + PFE multiplier
   • SFT: exposure = securities lent - collateral
3. Aggregate: Total = Σ Banking Book + Σ Trading Book

RBI specific: You must aggregate "unknown exposures" as if related to single counterparty.

Best Practice Controls:

• Single Customer View / CIF with LEI mapping
• Product-agnostic exposure engine (e.g., Murex, Aladdin)
• Daily large exposure breach report with product breakdown
• Connected party declaration and annual verification