
Counterparty Risk
- 384 installs
- 161 repo stars
- Updated July 18, 2026
- joellewis/finance_skills
counterparty-risk is a Claude Code finance skill that evaluates counterparty credit, settlement, and default exposure for developers integrating trades, lending, vendor contracts, or treasury relationships who need pre-t
About
counterparty-risk is a Claude Code skill from the finance_skills collection for assessing credit, settlement, and default exposure before entering trades, lending arrangements, vendor contracts, or treasury relationships. It helps developers building fintech integrations, treasury dashboards, or automated settlement flows understand whether a counterparty's failure could cascade into platform liability. The skill structures due diligence questions and exposure limits rather than executing transactions. Developers reach for counterparty-risk when wiring new broker APIs, DeFi protocols, B2B lending features, or vendor payment rails where counterparty insolvency or settlement failure would affect end users or firm capital.
- Credit and default exposure framing
- Settlement and collateral risk checks
- Pre-trade and pre-contract due diligence
- Exposure limit and concentration guidance
- Finance-specific risk vocabulary
Counterparty Risk by the numbers
- 384 all-time installs (skills.sh)
- +15 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #288 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/joellewis/finance_skills --skill counterparty-riskAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 384 |
|---|---|
| repo stars | ★ 161 |
| Last updated | July 18, 2026 |
| Repository | joellewis/finance_skills ↗ |
How do you assess counterparty risk before trading?
Evaluate counterparty credit, settlement, and default exposure before trades, lending, vendor contracts, or treasury relationships.
Who is it for?
Developers building fintech integrations or treasury tools who must gate new counterparties before automated settlement or credit exposure.
Skip if: Teams needing market risk models, portfolio optimization, or retail suitability questionnaires should use market or compliance skills instead.
When should I use this skill?
User asks to evaluate counterparty credit, settlement risk, or default exposure before a trade, loan, or vendor contract.
What you get
Counterparty risk assessment, exposure limits, and settlement failure mitigation checklist for trades, lending, or treasury relationships.
- counterparty risk assessment
- exposure limit checklist
Files
Counterparty Risk
Workflow A: Assessing a New Counterparty
1. Identify the legal entity and verify netting enforceability. Map the exact legal entity (not the corporate group), its jurisdiction, and entity type. Confirm close-out netting enforceability via ISDA netting opinions for that jurisdiction and entity-type combination before counting any netting benefit — where enforceability is uncertain, risk and capital must be measured gross. Apply the sovereign ceiling for counterparties in jurisdictions with material sovereign risk. 2. Assess credit quality from three angles. External ratings are a baseline but a lagging indicator — they typically reprice after the market has. Internal scoring: for banks, focus on CET1 (strong banks hold >12%), leverage ratio (well-capitalized banks target 5%+), LCR/NSFR (minimum 100%), and NPL trend; for corporates, debt/EBITDA, interest coverage (below 2x signals stress), free cash flow, and Altman Z-score, plus qualitative factors (management, franchise, regulatory standing). Market-implied: CDS spreads react fastest — annual PD ≈ CDS_spread / (1 − recovery); a 200bp spread at 40% recovery implies roughly 3.3% annual default probability. 3. Determine the trading channel: cleared vs. bilateral. Standardized interest rate swaps in major currencies and index CDS must clear under Dodd-Frank Title VII / EMIR (end-user hedging exemptions exist). Non-mandated products stay bilateral under the uncleared margin rules: zero VM threshold, IM threshold up to $50 million per counterparty group, and IM held segregated at a third-party custodian with no rehypothecation. Client clearing adds clearing-member risk: evaluate portability provisions and maintain a backup clearing member. 4. Negotiate documentation. ISDA Master Agreement (the 2002 version uses the Close-out Amount methodology; many legacy relationships remain on the 1992 version's Market Quotation/Loss — know which governs each relationship), Schedule elections (governing law, Specified Entities, cross-default thresholds, additional termination events such as NAV triggers), and CSA terms: threshold, minimum transfer amount, independent amount/IM, eligible collateral and haircuts, valuation frequency (daily is standard), and dispute resolution. Link the CSA threshold to ratings so it steps down — ideally to zero — on downgrade. 5. Set the credit limit. Tier by credit quality, with sub-limits by product and tenor (long-dated exposure is more uncertain) and a settlement limit separate from the pre-settlement limit. Apply explicit add-ons or reduced limits for wrong-way risk, where exposure and counterparty credit quality are positively correlated (general WWR: PD correlated with market factors; specific WWR: structural, e.g., a put written on the counterparty's own stock). 6. Stand up measurement and monitoring. Compute current exposure CE = max(V, 0); PFE at 95-97.5% confidence via Monte Carlo (simulate risk-factor paths, revalue the netting set at each time step, take the percentile of max(value, 0)); EE/EPE as the capital basis; EAD = 1.4 × (RC + PFE add-on) under SA-CCR; CVA = LGD × Σ EE_i × PD_i × DF_i. Aggregate across all desks, products, and legal entities facing the counterparty — a trade missing from the counterparty risk system is unmeasured exposure. Wire pre-deal limit checks into order flow, monitor post-trade for market-driven breaches, alert at ~80% utilization, and hard-block at 100%. Review cadence: annual full review for top-tier names, semi-annual for lower tiers, monthly (or more) for the watch list.
Workflow B: Responding to a Credit-Deterioration Event
Early-warning thresholds that should put a counterparty on the watch list before any downgrade: sustained CDS widening (e.g., 50bp over 30 days, or absolute spread above 300bp), stock price decline >30% over 60 days, negative rating outlook, covenant breaches, regulatory enforcement actions, accounting restatements, or significant client withdrawals.
1. Confirm and classify the trigger. Initiate a formal credit review: temporary setback (a bad quarter, a one-time loss) or structural deterioration (capital erosion, rising NPLs, franchise decline)? Review the latest financials, disclosures, and analyst coverage. 2. Enforce CSA downgrade provisions. Check for ratings-linked threshold step-downs and additional termination events; call any collateral the CSA now permits (a threshold stepping to zero converts the prior threshold amount into an immediate collateral call). 3. Reduce the credit limit. Convene the credit committee and re-tier the counterparty. If current exposure now exceeds the reduced limit, document the breach and a dated remediation plan. 4. Reduce exposure. In rough order of cost: let maturing trades roll off without replacement; execute offsetting trades; novate trades to other counterparties (requires consent); unwind by agreement with a close-out payment. Prioritize long-dated, high-PFE trades for novation or unwind; short-dated trades maturing within weeks rarely justify early-termination costs. 5. Restrict new trading. Hold on exposure-increasing trades; require credit-officer approval for any new trade, which must be flat or exposure-reducing. 6. Escalate monitoring to daily — exposure, CDS, collateral disputes, news — and explicitly stress wrong-way risk by jointly shocking the exposure drivers and the counterparty's default (e.g., a European bank counterparty and euro depreciation that inflates FX-forward exposure simultaneously). 7. Pre-position for default. Pre-calculate close-out amounts and collateral adequacy, identify replacement counterparties for critical hedges, and confirm which agreement version and close-out methodology governs. 8. Document everything — committee decisions, limit rationale, the reduction plan, and communications — as evidence of prudent risk management for internal audit and examiners.
Workflow C: Default Close-Out Playbook
Maintain this playbook pre-built for every watch-list counterparty: pre-drafted Event of Default and termination notices, pre-identified valuation sources (dealer panels, pricing services, internal marks), pre-computed exposure and collateral figures, and a contact tree (legal, credit, trading, operations). Close-out must execute in days, not weeks — every day of delay is unhedged market risk on the terminated portfolio.
1. Confirm the Event of Default under the governing Master Agreement (failure to pay, credit support default, cross-default above the threshold, bankruptcy, merger without assumption). Distinguish from Termination Events (illegality, force majeure, tax events, ATEs), which may permit termination of only the affected transactions. 2. Deliver the default notice using the pre-drafted form, observing the agreement's notice mechanics and grace periods. 3. Designate the Early Termination Date (same day or a future date, as the agreement permits). 4. Value the terminated transactions using commercially reasonable procedures — 2002 ISDA Close-out Amount (flexible but more subjective) or 1992 Market Quotation/Loss — drawing on the pre-identified valuation sources. Document quotes and marks contemporaneously; valuation disputes are the most litigated part of close-outs. 5. Net to a single Early Termination Amount. The single-agreement provision defeats cherry-picking by the bankruptcy estate: all transactions terminate together and net to one claim, including unpaid amounts. This is where the netting-enforceability verification from Workflow A pays off. 6. Apply collateral held under the CSA against the net amount. Expect exposure drift over the margin period of risk (regulatory MPOR ~10 business days bilateral, ~5 days cleared) between the last margin collection and final close-out — this is the exposure IM was sized to cover. 7. Re-hedge the terminated portfolio immediately. The close-out crystallizes the claim, but the market risk of the vanished trades is live until replaced. 8. For cleared trades, the CCP runs default management instead. The default waterfall applies resources in order: (1) the defaulter's initial margin, (2) the defaulter's default fund contribution, (3) the CCP's own capital (skin-in-the-game), (4) non-defaulting members' default fund contributions, (5) capped supplemental assessments, (6) recovery tools (variation margin gains haircutting, partial tear-up). CCPs size resources to the Cover 1 / Cover 2 standard — the default of the largest one or two members under extreme but plausible conditions. Clients of a defaulted clearing member should trigger porting of positions and margin to a backup member within one to two days.
Core Reference
Exposure measures (one line each). Current exposure: CE = max(V, 0), where V is the net mark-to-market of the netting set. PFE: the high-percentile (95-97.5%) simulated exposure profile over time — rising with horizon, then rolling off as trades mature. EE/EPE: average exposure at a date / time-averaged EE, the basis for regulatory capital under SA-CCR and IMM. EAD (SA-CCR): 1.4 × (RC + PFE add-on). CVA: the market value of counterparty credit risk, a separate Basel III capital charge that raises the cost of bilateral OTC trades. Wrong-way risk: standard PFE models assume exposure-default independence — add joint stress scenarios where they correlate.
Netting. Payment netting reduces settlement flows; close-out netting is the credit-risk tool. Netting benefit = gross exposure − net exposure; netting ratio = net/gross (a ratio of 0.3 means netting cut exposure 70%). CCP multilateral netting nets across all clearing members and can exceed any bilateral result.
Collateral. VM covers current exposure (daily exchange, typically title transfer and reusable); IM covers close-out-period exposure (posted at inception, segregated, no rehypothecation under the uncleared margin rules). ISDA SIMM (sensitivity-based, recalibrated annually) generally produces lower IM than the regulatory schedule because it recognizes hedging and diversification. Typical haircuts: cash 0%; Treasuries 0.5-4% by maturity; investment-grade corporates 5-10%; equities 15-25%; plus ~8% FX haircut for non-domestic-currency collateral. Valuation disputes are routine — transfer the undisputed amount while escalating per the CSA.
CCP margin methodology. CCPs compute IM with historical-simulation VaR or Expected Shortfall at 99%+ confidence over the MPOR (typically 5 days for cleared swaps, 2 days for listed futures), plus concentration, liquidity, and wrong-way add-ons; VM is exchanged daily or intraday. Clearing concentrates risk in the CCP itself — CCPs are designated SIFMUs with heightened supervision, and members should assess each CCP's default waterfall adequacy.
Settlement risk. Settlement risk mechanics — DVP, PvP/CLS, Herstatt risk — are owned by the settlement-clearing skill (trading-operations); the counterparty-risk implication is that settlement limits must be set separately from pre-settlement limits because the exposure is full notional, not mark-to-market.
Key Metrics and Formulas
| Metric | Expression | Use Case |
|---|---|---|
| Current Exposure | max(V, 0) | Point-in-time counterparty exposure |
| EAD (SA-CCR) | 1.4 * (RC + PFE_addon) | Regulatory capital calculation |
| Netting Ratio | Net_exposure / Gross_exposure | Netting effectiveness measurement |
| Implied PD from CDS | CDS_spread / (1 - Recovery_rate) | Market-implied default probability |
| Collateralized Exposure | max(V - C_adjusted, 0) | Exposure net of haircut-adjusted collateral |
| Uncollateralized Exposure | max(V - Threshold, 0) - Collateral_held | Residual exposure above CSA threshold |
| Limit Utilization | Current_exposure / Credit_limit | Credit limit monitoring |
| CVA | LGD sum(EE_i PD_i * DF_i) | Credit valuation adjustment |
where V = portfolio MTM, C_adjusted = collateral after haircuts, LGD = loss given default (1 - Recovery), EE_i = expected exposure at time i, PD_i = default probability in period i, DF_i = discount factor.
Worked Examples
Two worked examples are in references/examples.md — load for an end-to-end scenario: (1) setting up a counterparty credit limit framework with tiering, sub-limits, and governance, (2) designing collateral management for bilateral OTC trades under the uncleared margin rules.
Common Pitfalls
- Relying solely on credit ratings as the primary indicator of counterparty creditworthiness — ratings are lagging indicators that often reflect deterioration only after the market has repriced the risk; CDS spreads and equity-implied metrics provide more timely signals
- Failing to verify netting enforceability in each counterparty's jurisdiction before counting netting benefits in exposure calculations — unenforced netting provides no risk reduction and regulators require gross exposure treatment where enforceability is uncertain
- Neglecting wrong-way risk in exposure measurement — standard PFE models assume independence between exposure and default probability, which can dramatically underestimate risk when the two are positively correlated
- Setting counterparty credit limits at inception but failing to reduce them when credit quality deteriorates — limits must be dynamic, with formal processes for downward revision triggered by early warning indicators
- Using a single aggregate credit limit without sub-limits by product type and tenor — a counterparty with a $200 million limit concentrated entirely in 30-year interest rate swaps presents fundamentally different risk than one with the same limit spread across short-dated FX forwards
- Treating the CSA threshold as a static parameter without linking it to the counterparty's credit rating — thresholds should step down (or reduce to zero) upon rating downgrade to ensure additional collateral is posted as credit quality weakens
- Failing to calculate and maintain pre-computed close-out amounts for counterparties on the watch list — if a counterparty defaults, the firm needs to act within hours, not days, to terminate and hedge
- Ignoring settlement risk for currencies not covered by CLS — the full notional of the first-delivered leg is exposed during the time-zone gap (mechanics in settlement-clearing)
- Assuming that central clearing eliminates counterparty risk entirely — clearing reduces but does not eliminate risk; the firm still faces clearing member default risk (for client clearers) and CCP tail risk, and must contribute to the default fund
- Permitting rehypothecation of initial margin received for uncleared derivatives — this violates uncleared margin rules and, even where not prohibited, introduces a chain of credit risk that defeats the purpose of initial margin
- Not stress testing the collateral portfolio for scenarios where collateral values decline simultaneously with exposure increases — a concentrated collateral portfolio of corporate bonds may lose value in the same market stress that increases derivative exposure
- Maintaining ISDA documentation with outdated Schedules that reference superseded regulations or contain stale credit thresholds, creating legal uncertainty about close-out mechanics and collateral obligations during a default event
Cross-References
- settlement-clearing (trading-operations): Owns settlement risk mechanics — DVP/PvP, CLS, Herstatt risk, and fail management; clearing and settlement infrastructure are the structural mitigants for counterparty exposure.
- margin-operations (trading-operations): Owns Reg T and FINRA Rule 4210 brokerage margin; margin call workflows are the operational implementation of the collateral concepts in this skill.
- trade-execution (trading-operations): Pre-deal credit limit checks must be integrated into the trade execution workflow to prevent trades that would breach counterparty exposure limits.
- order-lifecycle (trading-operations): Counterparty selection and credit validation are pre-execution steps in the order lifecycle.
- operational-risk (trading-operations): Counterparty default events require documented escalation, remediation, and loss attribution processes.
- forward-risk (wealth-management): PFE calculation shares Monte Carlo risk-factor simulation techniques and infrastructure with forward-looking portfolio risk analysis.
- fixed-income-corporate (wealth-management): Credit analysis of corporate bond issuers uses many of the same financial metrics and rating frameworks applied to counterparty credit assessment.
Counterparty Risk — Worked Examples
Example 1: Setting Up a Counterparty Credit Limit Framework
Scenario: A mid-size institutional trading desk is establishing a counterparty credit limit framework for its OTC derivatives business. The desk trades interest rate swaps, FX forwards, and equity options with approximately 40 counterparties including major global banks, regional banks, and several large corporate end-users. The desk needs a structured framework for setting, monitoring, and enforcing counterparty credit limits.
Design Considerations:
The framework begins with counterparty tiering based on credit quality. The desk categorizes counterparties into four tiers:
- Tier 1 (AA- or higher): Major global banks with strong capital positions and diversified revenue. Maximum aggregate limit of $500 million per counterparty. These counterparties have deep liquidity, robust ISDA documentation, and active CSAs with daily margining.
- Tier 2 (A- to A+): Large regional banks and well-capitalized financial institutions. Maximum aggregate limit of $200 million per counterparty. These counterparties have standard ISDA documentation and CSAs, though some may have higher thresholds or less frequent margining.
- Tier 3 (BBB- to BBB+): Investment-grade corporates and smaller financial institutions. Maximum aggregate limit of $50 million per counterparty. These counterparties may have limited ISDA documentation and may not post collateral, requiring stricter exposure limits.
- Tier 4 (below BBB- or unrated): Sub-investment-grade or unrated counterparties. Maximum aggregate limit of $10 million per counterparty. Trading is restricted to short-dated, fully collateralized transactions where possible.
Within each tier, individual counterparty limits are set based on specific credit analysis. The credit analyst evaluates the counterparty's financial statements (focusing on capital adequacy ratios for banks, leverage and interest coverage for corporates), market indicators (CDS spreads, equity volatility), qualitative factors (management, business model, regulatory standing), and the expected trading relationship (product types, tenors, netting potential).
Limits are sub-allocated by product type and tenor. For a Tier 1 counterparty with a $500 million aggregate limit, the sub-allocation might be: interest rate swaps up to $300 million (with sub-limits of $200 million for tenors under 5 years and $100 million for tenors 5-30 years), FX forwards up to $150 million (all tenors under 1 year), and equity options up to $100 million. These sub-limits need not sum to the aggregate limit — the aggregate limit caps total exposure regardless of product mix.
Settlement limits are set separately from pre-settlement limits. A counterparty may have a pre-settlement limit of $200 million (covering mark-to-market exposure on outstanding trades) and a settlement limit of $50 million (covering the notional amount at risk during the settlement window). Settlement limits are particularly important for FX transactions where Herstatt risk is present and CLS is not used.
Analysis:
The pre-deal limit check process integrates with the trading system. Before any new trade is executed, the system calculates the incremental exposure the trade would add to the counterparty's current exposure (using a pre-deal PFE add-on based on the trade's notional, product type, and tenor) and checks whether the resulting total would exceed the limit. If the limit would be breached, the trade is blocked and routed to the credit officer for review.
Limit utilization is monitored continuously. The exposure management system recalculates counterparty exposure as market prices change, not just when new trades are booked. A counterparty whose exposure was at 60% of limit in the morning could reach 90% by afternoon if market movements cause the portfolio's mark-to-market value to increase significantly. The system generates tiered alerts: amber at 80% utilization, red at 95%, and hard block at 100%.
The credit committee reviews the entire limit framework quarterly, with ad hoc reviews triggered by material credit events. Annual reviews include a comprehensive reassessment of each counterparty's creditworthiness, a review of limit utilization patterns (counterparties whose limits are consistently underutilized may have limits reduced to free up aggregate capacity), and stress testing of the limit framework under adverse scenarios (what would happen to exposure and limit utilization if interest rates moved 200bp, FX rates moved 10%, or equity markets dropped 30%).
Governance and reporting are integral to the framework. The credit risk management function produces a daily counterparty exposure report showing each counterparty's current exposure, PFE, collateral held, net exposure, limit, and utilization percentage. A weekly summary report aggregates exposure by tier, product type, and geography, highlighting concentration risks (e.g., if 60% of total exposure is concentrated in three Tier 1 banks, the firm has significant concentration risk even if each counterparty is individually well-rated). A monthly report to senior management and the risk committee includes trend analysis, limit breach history, watch list updates, and any material changes to the credit environment. These reports form part of the firm's risk governance framework and are subject to internal audit review.
The framework should also address the treatment of wrong-way risk within the limit structure. For counterparties where the desk has identified potential wrong-way risk, the credit limit should be set more conservatively, and the PFE calculation should incorporate stress scenarios that capture the correlation between exposure and counterparty credit quality. For example, if the desk holds commodity derivatives with an energy company, and the energy company's creditworthiness deteriorates when commodity prices fall (which is precisely when the derivatives may have high positive value to the desk), the standard PFE model may understate the true risk. Explicit wrong-way risk add-ons or dedicated wrong-way risk limits can address this gap.
Example 2: Designing Collateral Management for Bilateral OTC Trades
Scenario: An asset management firm is establishing bilateral OTC derivative trading capability for the first time. The firm will trade interest rate swaps and FX options to hedge portfolio exposures. The firm needs to design collateral management processes that comply with uncleared margin rules and efficiently manage collateral across multiple counterparty relationships.
Design Considerations:
The firm must first determine its regulatory obligations. Under the BCBS-IOSCO uncleared margin rules (implemented in the US via CFTC and prudential regulator rules, and in the EU via EMIR margin RTS), the firm must exchange both initial margin (IM) and variation margin (VM) for uncleared OTC derivatives if its aggregate average notional amount (AANA) exceeds the applicable threshold. Variation margin requirements apply to virtually all financial counterparties. Initial margin requirements apply in phased implementation based on AANA thresholds, with the final phase covering entities with AANA above $8 billion (US) or EUR 8 billion (EU).
The CSA negotiation with each counterparty must address several critical terms:
Threshold and minimum transfer amount: Under the uncleared margin rules, the VM threshold must be zero (no uncollateralized exposure is permitted for entities in scope). The MTA can be set up to $500,000 for VM. For IM, the threshold can be up to $50 million per counterparty group. The firm should negotiate these terms within regulatory constraints, balancing credit protection against operational burden.
Eligible collateral and haircuts: The firm specifies which collateral types it will accept and post. A typical schedule includes cash in major currencies (USD, EUR, GBP, JPY) with zero haircut, US Treasuries and equivalent sovereign bonds with haircuts of 0.5% to 4% depending on maturity, and investment-grade corporate bonds with haircuts of 5% to 10%. The firm should establish whether it will accept equities (higher haircut, more volatile) and set concentration limits (no more than a specified percentage of collateral in any single issuer for non-sovereign securities).
Segregation requirements: Under the uncleared margin rules, IM must be held in a segregated account at a third-party custodian. The IM cannot be rehypothecated, commingled with the receiving party's assets, or used for any purpose other than satisfying the margin obligation. VM does not have the same segregation requirement and can be held directly by the receiving party. The firm must establish custodial relationships with one or more third-party custodians (such as BNY Mellon, State Street, or JPMorgan as custody banks) to hold segregated IM.
The daily margining process follows a defined workflow. Each business day: the firm's risk system calculates the current mark-to-market value of the portfolio with each counterparty; the system calculates the required VM call (the change in net exposure since the last margin exchange) and the required IM (using either the ISDA SIMM model or a schedule-based approach); the collateral management team issues margin calls to counterparties where the firm is owed additional collateral, and responds to margin calls from counterparties where the firm owes collateral; collateral is transferred by the agreed settlement deadline (typically T+1 for cash, T+2 for securities); and the firm's records are updated to reflect the new collateral balances.
Analysis:
Dispute resolution is a critical operational consideration. If the firm and a counterparty disagree on the portfolio valuation (and therefore the margin call amount), the CSA dispute resolution provisions apply. The standard approach is: the parties exchange their respective valuations; if the difference exceeds a tolerance (typically $1-5 million), the parties engage in good faith negotiation; the undisputed amount is transferred while the dispute is resolved; escalation to senior management or a third-party valuation agent if the dispute is not resolved within a defined timeframe. The firm should track dispute frequency and magnitude by counterparty — persistent disputes may indicate valuation model differences that need to be reconciled.
ISDA SIMM (Standard Initial Margin Model) is the industry-standard model for calculating IM on uncleared derivatives. SIMM uses a sensitivity-based approach: the firm calculates the sensitivities of each trade to defined risk factors (delta, vega, curvature), and SIMM applies calibrated risk weights and correlations to compute the IM requirement. SIMM is recalibrated annually by ISDA using recent market data. Using SIMM rather than the regulatory schedule-based approach typically results in lower IM requirements because SIMM recognizes portfolio diversification and hedging benefits.
Collateral optimization is an ongoing operational challenge. The firm holds a pool of eligible collateral assets and must decide which assets to post to each counterparty. Cash is the cheapest to post (no haircut, immediate settlement) but has the highest opportunity cost (the firm forgoes the return on cash). Government securities are nearly as efficient (low haircut) but require settlement infrastructure and incur a small haircut cost. The firm should implement a collateral allocation algorithm that minimizes the total cost of collateral across all counterparty relationships, considering haircuts, opportunity costs, settlement timing, and any counterparty-specific collateral preferences.
The firm should also prepare for stressed collateral scenarios. During market stress, the value of non-cash collateral may decline (increasing the amount of collateral needed to meet margin requirements), margin calls may increase sharply (as portfolio MTM values swing), and counterparties may reject previously acceptable collateral types. The firm should maintain a buffer of high-quality liquid assets (cash and short-dated government securities) above minimum margin requirements to absorb margin call increases without needing to liquidate portfolio positions.
Operational infrastructure is a significant consideration for a firm establishing bilateral OTC capability for the first time. The firm needs: a collateral management system that tracks collateral balances by counterparty, calculates margin calls, and manages substitution requests; connectivity to custodian banks for collateral transfers (SWIFT messaging, custodian portals); legal documentation (CSAs negotiated and executed with each counterparty); accounting processes for recording collateral received and posted, including treatment of interest on cash collateral (typically paid at the federal funds rate or a negotiated rate); and trained personnel to manage the daily margin call process, respond to disputes, and coordinate collateral movements across counterparties and custodians. The operational cost of collateral management is non-trivial — firms should budget for systems, custody fees, and dedicated operations staff before entering bilateral OTC markets.
Related skills
FAQ
What risks does counterparty-risk evaluate?
counterparty-risk evaluates credit quality, settlement reliability, and default exposure for trades, lending, vendor contracts, and treasury relationships. Outputs include exposure limits and mitigation checklists before live integration.
When should developers run counterparty-risk checks?
counterparty-risk runs before activating new broker APIs, lending features, vendor payment rails, or treasury connections. The skill gates automated flows until counterparty failure modes are understood and bounded.