managing-cross-border-settlement-risk

Evaluates settlement risk in cross-border transactions with time zone analysis, CLS participation, and Herstatt risk mitigation. Use when managing settlement risk, analyzing CLS eligibility, or evaluating cross-currency settlement.

11 stars

Best use case

managing-cross-border-settlement-risk is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Evaluates settlement risk in cross-border transactions with time zone analysis, CLS participation, and Herstatt risk mitigation. Use when managing settlement risk, analyzing CLS eligibility, or evaluating cross-currency settlement.

Teams using managing-cross-border-settlement-risk should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/managing-cross-border-settlement-risk/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/capital/managing-cross-border-settlement-risk/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/managing-cross-border-settlement-risk/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How managing-cross-border-settlement-risk Compares

Feature / Agentmanaging-cross-border-settlement-riskStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Evaluates settlement risk in cross-border transactions with time zone analysis, CLS participation, and Herstatt risk mitigation. Use when managing settlement risk, analyzing CLS eligibility, or evaluating cross-currency settlement.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Managing Cross Border Settlement Risk

## When To Use

- Assessing settlement exposure on cross-currency or cross-border FX, fixed-income, or equity transactions
- Evaluating whether a currency pair is eligible for CLS (Continuous Linked Settlement) or requires bilateral netting
- Quantifying Herstatt risk (principal risk) when payment legs settle in non-overlapping time zones
- Reviewing correspondent banking chains for settlement lag, failed-trade rates, or liquidity gaps
- Preparing management reports on aggregate settlement exposure across desks, entities, or jurisdictions

## Inputs To Gather

- **Transaction details**: currency pair, notional amount, value date, settlement method (gross/net), and product type (spot FX, NDF, cross-currency swap, securities DVP)
- **Counterparty profile**: CLS membership status (settlement member, third-party, non-participant), SWIFT BIC, nostro/vostro account structure
- **Time zone data**: local payment system operating hours for each currency leg (e.g., BOJ-NET, TARGET2, Fedwire, CHAPS, HKICL) [VERIFY hours against current RTGS schedules]
- **Netting agreements**: ISDA master agreement status, bilateral netting opinion availability per jurisdiction [VERIFY enforceability in each jurisdiction]
- **Historical fail data**: counterparty-level and currency-level settlement fail rates over trailing 30/90 days
- **Credit and liquidity limits**: intraday credit lines, pre-funding requirements, and liquidity buffers at each nostro bank

## Workflow

1. **Map settlement legs to time zones**
   - For each transaction, identify the payment system and cut-off time for each currency leg
   - Calculate the gap (in hours) between the earliest irrevocable pay-away and the latest expected receipt
   - Flag any leg where the gap exceeds the same-day settlement window (principal-at-risk period)

2. **Classify CLS eligibility**
   - Determine if both currencies are CLS-eligible (currently 18 currencies) [VERIFY current CLS currency list]
   - Confirm both counterparties can access CLS (direct member, third-party, or non-participant)
   - For CLS-eligible pairs: confirm PVP (payment-versus-payment) settlement and note residual liquidity risk (funding deadlines in CLS schedule)
   - For non-CLS pairs: proceed to bilateral risk mitigation steps

3. **Quantify Herstatt / principal risk**
   - Calculate gross principal at risk: full notional of the pay leg during the unhedged window
   - Apply netting: if enforceable bilateral netting agreement exists, reduce to net exposure per counterparty per value date
   - Stress-test: model exposure if counterparty defaults at the point of maximum pay-away (worst-case time zone gap)
   - Compare net exposure against counterparty credit limits and flag breaches

4. **Evaluate correspondent banking chain**
   - Map the nostro/vostro path for each currency leg (number of intermediary banks, expected processing times)
   - Identify single points of failure (sole correspondent in an emerging-market currency)
   - Review historical settlement fail rates by correspondent and currency; flag any above threshold (e.g., >2% fail rate)

5. **Assess mitigation tools**
   - **CLS PVP**: eliminates principal risk; residual risk is liquidity (funding shortfall)
   - **Bilateral netting with close-out**: reduces gross to net; requires enforceable netting opinion [VERIFY jurisdiction-specific enforceability]
   - **Pre-funding / collateralization**: for non-CLS currencies, evaluate margin or escrow arrangements
   - **Staggered settlement**: sequence payment instructions to reduce the window of unilateral exposure
   - **Same-day affirmation / matching**: confirm trade details on T+0 to reduce fails from mismatches

6. **Compile exposure dashboard**
   - Aggregate settlement exposure by currency, counterparty, time zone gap bucket, and CLS vs. non-CLS
   - Highlight top-5 counterparty exposures and any limit breaches
   - Trend failed-trade rates and escalate persistent outliers

## Output

Produce a **Cross-Border Settlement Risk Report** containing:

- **Executive summary**: total gross and net settlement exposure, CLS coverage ratio, number and value of limit breaches
- **Time zone overlap matrix**: grid showing payment system hours and gap windows for each active currency pair
- **CLS eligibility table**: currency pair, CLS status, counterparty access method, residual risk type
- **Herstatt risk heat map**: counterparty × currency pair, ranked by net principal-at-risk during peak gap window
- **Correspondent chain assessment**: per-currency path diagram with fail rates and identified single points of failure
- **Mitigation recommendations**: prioritized list of actions (onboard to CLS, execute netting agreement, pre-fund, change correspondent) with estimated exposure reduction
- **Monitoring triggers**: thresholds for re-escalation (e.g., fail rate >X%, net exposure >$Y per counterparty)

## Quality Checks

- Confirm all payment system cut-off times are sourced from current RTGS operator publications, not stale references [VERIFY]
- Validate that netting benefit calculations only apply where a jurisdiction-specific legal opinion confirms close-out netting enforceability
- Cross-check CLS-eligible currency list against the latest CLS Group publications [VERIFY]
- Ensure gross-to-net calculations match the bilateral netting sets actually documented under ISDA
- Verify that exposure figures reconcile to front-office trade capture (no missing legs or duplicate bookings)
- Confirm that emerging-market currencies without CLS access are flagged with explicit mitigation steps, not left as accepted risk without sign-off
- Mark any assumed correspondent processing times or credit limits with [VERIFY] if not confirmed by operations

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.