Use when entering a derivative contract, securities lending arrangement, or any transaction where a specific counterparty owes a future obligation — assessing that specific counterparty's ability to actually meet its obligation, distinct from broad market or credit-bubble risk, since a transaction's value is worthless if the counterparty on the other side defaults.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill audit-counterparty-credit-risk --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Audit Counterparty Credit Risk?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-audit-counterparty-credit-risk)More formats (shields.io, HTML) on the badges page.
---
name: audit-counterparty-credit-risk
description: Use when entering a derivative contract, securities lending arrangement, or any transaction where a specific counterparty owes a future obligation — assessing that specific counterparty's ability to actually meet its obligation, distinct from broad market or credit-bubble risk, since a transaction's value is worthless if the counterparty on the other side defaults.
source: Basel III credit valuation adjustment (CVA) framework; International Swaps and Derivatives Association (ISDA) counterparty risk management practice
tags: [finance, investing, counterparty-risk, credit-risk, derivatives, credit-valuation-adjustment, default-risk]
related: [audit-systemic-credit-bubble-risk, audit-balance-sheet-debt-risk, design-concentration-risk-limits]
---
# Audit Counterparty Credit Risk
When entering a derivative contract, securities lending arrangement, or any transaction where a specific counterparty owes a future obligation, assess that specific counterparty's ability to actually meet its obligation — distinct from broad market or systemic credit-bubble risk — since a transaction's economic value is worthless if the specific counterparty on the other side of it defaults before fulfilling its obligation.
## Why This Is Best Practice
**Adopted by:** The Basel III credit valuation adjustment (CVA) framework requires regulated banks to explicitly capitalize against the risk that a derivative counterparty's credit quality deteriorates or defaults before the contract is settled, and the International Swaps and Derivatives Association (ISDA) has developed standard documentation and practices (including collateral and netting agreements) specifically to manage and mitigate counterparty credit risk across the derivatives industry.
**Impact:** A derivative contract or lending arrangement's stated value assumes the counterparty will actually fulfill its obligation — the 2008 financial crisis specifically demonstrated, through the failure or near-failure of several major counterparties, that this assumption can fail even for large, seemingly creditworthy institutions, and positions that appeared economically sound based on market price alone proved to carry substantial, previously under-priced counterparty risk.
**Why best:** Broad market or systemic credit-risk assessment (see `audit-systemic-credit-bubble-risk`) evaluates whether credit markets broadly are mispricing risk, but doesn't substitute for evaluating the specific creditworthiness of the specific counterparty on the other side of a specific transaction — a transaction can be priced fairly relative to broad market conditions while still carrying meaningful risk that this particular counterparty specifically fails to perform.
Sources: Basel Committee on Banking Supervision, credit valuation adjustment (CVA) capital framework; International Swaps and Derivatives Association (ISDA), counterparty risk management and standard documentation practices
## Steps
### Step 1: Identify every transaction creating a specific counterparty exposure
Identify each transaction — derivative contracts, securities lending, repurchase agreements, or any arrangement where a specific counterparty owes a future payment or delivery — that creates counterparty credit exposure distinct from the transaction's underlying market risk.
### Step 2: Assess the specific counterparty's creditworthiness independently
Assess the specific counterparty's creditworthiness directly — credit ratings, credit default swap spreads, balance sheet strength, and other counterparty-specific indicators — rather than assuming the counterparty's creditworthiness based solely on its size, reputation, or the fairness of the transaction's market pricing.
### Step 3: Quantify the potential future exposure to that specific counterparty
Quantify the potential future exposure to the specific counterparty — how much would be owed and at risk if the counterparty defaulted at various points over the life of the transaction — recognizing that this exposure can change over time as market conditions move the transaction's value.
### Step 4: Use collateral, netting, and clearing arrangements to reduce counterparty exposure
Use standard risk-mitigation mechanisms — collateral posting requirements, netting agreements (offsetting multiple transactions with the same counterparty), and central clearing where available — to reduce the actual credit exposure to any single counterparty, rather than bearing the full, unmitigated exposure.
### Step 5: Set and monitor counterparty exposure limits, aggregated across all transactions
Set explicit exposure limits to any single counterparty, aggregated across all transactions with that counterparty (see `design-concentration-risk-limits` for the related aggregate-exposure discipline), and monitor actual exposure against these limits on an ongoing basis as market conditions and the counterparty's creditworthiness change over time.
## Rules
- Assess each specific counterparty's creditworthiness directly and independently, not merely inferred from the counterparty's size, reputation, or the fairness of the transaction's pricing.
- Quantify potential future exposure to a counterparty as market conditions move, not just current exposure at the point of the transaction's initiation.
- Use collateral, netting, and clearing mechanisms to actively reduce counterparty exposure, rather than bearing full unmitigated exposure by default.
- Set and monitor aggregate exposure limits to any single counterparty across all transactions with that counterparty, not per-transaction in isolation.
## Examples
**Counterparty risk properly mitigated through collateral:** An institution enters a derivative contract with a counterparty assessed as creditworthy, and requires ongoing collateral posting as the contract's value moves in the institution's favor — ensuring that even if the counterparty's creditworthiness later deteriorates, the collateral held substantially reduces the institution's actual loss exposure.
**Counterparty risk underestimated due to reliance on reputation alone (illustrative caution):** A different institution transacts with a large, well-known counterparty without independently assessing its specific current creditworthiness, assuming its size and reputation are sufficient assurance. A subsequent, unexpected deterioration in that counterparty's financial condition exposes the institution to losses that closer, independent counterparty-specific assessment might have surfaced earlier.
## Common Mistakes
- **Assuming counterparty creditworthiness based on size or reputation rather than direct, independent assessment** — even large, well-known institutions can experience unexpected credit deterioration, as demonstrated during the 2008 financial crisis.
- **Failing to quantify how potential future exposure to a counterparty changes as market conditions move** — exposure at the point of a transaction's initiation may be small while potential future exposure under adverse market moves is substantial.
- **Neglecting to use available collateral, netting, or clearing mechanisms to reduce exposure** — these mechanisms are standard, available tools for reducing counterparty risk that shouldn't be skipped by default.
- **Setting exposure limits per-transaction rather than aggregated across all transactions with the same counterparty** — aggregate exposure to a single counterparty across many transactions can be substantial even if each individual transaction appears modest.
## When NOT to Use
- For a transaction cleared through a well-capitalized central clearinghouse that has already substantially mitigated bilateral counterparty risk — in this case, the clearinghouse's own risk framework substantially (though not entirely) addresses this concern.
- As a substitute for broad market or systemic credit-risk assessment — counterparty-specific risk and systemic credit-market risk are related but distinct concerns, and a portfolio needs both (see `audit-systemic-credit-bubble-risk`).
- For a transaction with no meaningful future obligation or settlement risk (e.g., an immediately, fully-settled cash transaction) — counterparty credit risk specifically concerns obligations that remain outstanding over time.
> **Finance disclaimer:** This skill encodes professional best practices for educational purposes. It is not financial advice. Consult a licensed financial advisor before making investment decisions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!