A sound FX counterparty limit program combines binding, multi-metric limits (covering principal risk, replacement cost, and potential future exposure) with real-time monitoring, payment-versus-payment settlement controls, and formal governance for approvals and exceptions. Stress testing, dynamic credit tools, and clear communication across FX prime brokerage chains round out the program. Platforms like CorpHedge give treasury and risk teams a practical way to operationalize these controls without building everything in-house.
TL;DR:
- Set limits by counterparty, product, tenor, and legal or economic group, combining replacement cost, potential future exposure, and net open position.
- Use near real time exposure feeds and pretrade blocks, but establish named override authority and a logged exception process before automating enforcement.
- PvP settlement and bilateral netting reduce principal exposure; assign lower limits to flows outside PvP and measure exposure using actual payment cutoff times.
- Review limits quarterly and after downgrades, settlement incidents, or concentration spikes, then use stress and reverse stress tests to expose hidden concentrations.
- For prime brokerage, feed compressed trades into monitoring promptly and reconcile net open positions across prime broker and dealer records on a fixed cadence.
Table of Contents
- What a modern counterparty limit framework must cover
- Measuring exposure: PFE, replacement cost, and net open position
- Building real-time monitoring and pre-trade controls
- Settlement risk: PvP, netting, and payment shaping
- Governance: approving limits and handling exceptions
- Why stress testing validates your limit levels
- FX prime brokerage and trade compression complications
- Putting this into practice with CorpHedge
- Prioritizing automation against governance maturity
- See how CorpHedge supports your limit program
- FAQ
- Sources
What a modern counterparty limit framework must cover
A limit framework earns its keep only when it maps to the actual risks a counterparty can generate. That means covering principal risk (the full notional at stake if a counterparty fails before settlement), replacement cost (the mark-to-market loss of replacing a defaulted trade), and potential future exposure, which captures how that mark-to-market could move before maturity. Limits also need to reflect product type, tenor, and how trades are grouped: by legal entity, and by economic group where a parent guarantees several subsidiaries.
The objectives behind this scope are straightforward. Limits protect liquidity by preventing an outsized concentration from forcing an unplanned funding scramble, align counterparty exposure with the capital a firm is willing to hold against it, and let the business keep trading within a defined, pre-approved appetite rather than negotiating risk tolerance deal by deal.
A workable policy checklist includes:
- Documented limit levels by counterparty, product, and tenor bucket.
- A defined review cadence tied to calendar dates and trigger events.
- A written exception process with pre-approved temporary thresholds.
- Clear reporting lines showing who sees breaches and how fast.
The Basel Committee's consolidated guidance on counterparty credit risk calls for exactly this kind of structure: comprehensive due diligence, a mix of complementary metrics, and governance strong enough to make limits mean something when markets move fast.
Measuring exposure: PFE, replacement cost, and net open position
Potential future exposure (PFE) estimates the worst plausible mark-to-market loss on a trade or portfolio at a future point, using a stressed confidence interval rather than today's price. It matters more than current exposure alone because an FX forward or swap that looks flat today can move deep into the money well before maturity, and a limit built only on current replacement cost misses that trajectory entirely.
Replacement cost measures what it would cost to re-execute a defaulted trade at current market rates; tracking it by maturity bucket shows where exposure clusters as deals approach settlement. Net open position (NOP) aggregates long and short currency exposure across a book and is the metric prime brokers watch most closely, since it determines margin calls and credit usage across a prime brokerage relationship.
A practical metric mix combines:
- Current replacement cost for immediate loss-given-default.
- PFE for forward-looking tail risk.
- NOP for prime-brokered and netted flows.
Supervisory guidance now expects forward-looking measures as standard practice: Basel-aligned supervisory guidance states that limits should be based on peak exposure measures like PFE, with systems supporting near-real-time intraday monitoring so trades can be checked before execution rather than reconciled after the fact. Running PFE models well requires solid data governance: consistent market data feeds, documented model assumptions, and periodic back-testing against realized outcomes. Our guide on VaR-based FX risk limits walks through how these metrics translate into daily alerting.
Building real-time monitoring and pre-trade controls
Static, end-of-day exposure reports cannot catch a limit breach building intraday across dozens of trades. Real-time or near-real-time monitoring closes that gap, giving risk and trading desks a live view of exposure against limits as flows settle and new trades are booked.
Pre-trade checks, sometimes called speed humps or throttles, stop a trade from executing once a counterparty is approaching its ceiling, rather than flagging the breach after settlement risk has already been taken on. Paired with automated alerting and a documented escalation workflow, this creates an audit trail that shows exactly who approved what and when, which matters as much to internal governance as to external examiners.
Practical controls include:
- Intraday dashboards showing exposure against limits by counterparty.
- Automated pre-trade blocks once usage crosses a defined threshold.
- Escalation rules naming who gets alerted and within what time frame.
Pro Tip: Automated blocks only work if someone owns the override process; build the exception workflow before you build the alert.
Automation reduces the manual reconciliation burden that otherwise eats into a risk team's day, but it shifts the real work to governance: deciding who can override an automated block and how that decision gets logged. Our piece on monitoring cross-currency transactions covers the reconciliation side of this in more depth.
Settlement risk: PvP, netting, and payment shaping
Principal risk exists for the window between when a firm irrevocably pays out one currency and when it confirms receipt of the other, and that window is longer than most teams assume once unilateral payment cancellation deadlines are factored in. Settlement mechanics, not just credit quality, determine how long that exposure actually lasts.
Payment-versus-payment (PvP) settlement and bilateral netting arrangements cut principal exposure substantially by linking the two legs of a trade so neither pays without the other receiving. Counterparties that settle outside PvP arrangements warrant lower limits to reflect the longer exposure window.
Operational controls worth building:
- Daily monitoring of failed or delayed trades before they compound into bigger exposures.
- Documented exposure-duration estimates based on actual payment cutoff times.
- Limit sizing that explicitly discounts PvP-eligible flows against non-PvP flows.
Supervisory guidance on FX settlement risk calls for binding settlement exposure limits and independent oversight of the settlement process, not just credit limits set once and left unchecked.
Governance: approving limits and handling exceptions
Clear ownership keeps a limit framework from becoming a paper exercise. Credit risk sets the overall appetite, treasury and FX desks operate trades within approved limits, and operations teams enforce those limits at the point of settlement.
A workable governance process looks like this:
- Credit risk proposes initial limits based on counterparty financials, product mix, and tenor.
- A credit committee approves limits and any pre-authorized temporary exception bands.
- Limits are reviewed on a fixed cadence (commonly quarterly) and immediately after trigger events such as a credit downgrade, a concentration spike, or a settlement incident.
- A breach triggers immediate notification, a documented root-cause review, and a remediation plan before any further trading with that counterparty resumes.
This structure gives exceptions a defined path instead of an ad hoc phone call, which matters most in volatile weeks when the temptation to wave through a trade is highest.
Why stress testing validates your limit levels
A limit that looks comfortable under normal volatility can look reckless under stress, which is why stress testing has to run alongside day-to-day monitoring rather than as an annual exercise. Useful scenarios include a sudden market shock in a major currency pair, a counterparty default combined with a margin-call spiral, and a liquidity squeeze that forces simultaneous unwinds across several relationships.
Reverse stress tests work the other direction, starting from "what combination of events would breach this limit or exhaust our capital buffer" and working backward to identify hidden concentration.
Key uses of stress output:
- Recalibrating limits where a scenario reveals excess headroom or dangerous concentration.
- Building contingency plans for counterparties most exposed in a shock.
- Feeding results into board and senior management reporting on a defined schedule.
The ECB's macroprudential analysis of counterparty credit risk shows that exposures concentrate quickly and interact with liquidity risk, reinforcing why granular, counterparty-level stress data matters more than aggregate figures. Our guide on FX stress scenarios for treasury teams walks through building these scenarios in practice.
FX prime brokerage and trade compression complications
FX prime brokerage and designation notice structures let a client trade with multiple executing dealers under one prime broker's credit line, but trade compression, run periodically to reduce gross notional, can change reported net open position in ways that are not always communicated promptly.
Practical mitigations:
- Include compressed trades in monitoring feeds as soon as compression runs, not at the next scheduled reconciliation.
- Document how designation notices are treated in your own limit calculations.
- Reconcile NOP across prime broker and executing dealer ledgers on a fixed, frequent cadence.
GFMA/GFXD industry recommendations point to this exact gap, noting that a consistent market practice for treating compressed trades under FXPB limits is still lacking and that timely communication of NOP changes is essential to close it.
Putting this into practice with CorpHedge
A workable path runs from live exposure feeds, to VaR overlays that size the risk, to intraday alerts that flag a breach before it settles, to a logged exception workflow an auditor can follow. Our VaR-based hedging overlays are built around that same chain.
A pragmatic rollout checklist:
- Connect live position and market data feeds first.
- Calibrate exposure models against your actual counterparty mix.
- Align monitoring thresholds with your existing governance sign-off levels.
- Pilot on your largest counterparty relationships before scaling across the book.
Prioritizing automation against governance maturity
Automation only pays off once governance can keep up with it: a smaller corporate treasury is usually better served building exposure visibility and settlement controls first, then layering automated pre-trade blocks once the team trusts the data feeding them, as explained in detail by practical risk-management rules and trade-level controls. This kind of platform-based approach is spreading across mid-sized corporate treasuries in Europe. Start with the metric mix, prove it against a quarter of real data, then automate.
— Bartas
See how CorpHedge supports your limit program
We built CorpHedge around the same metric mix and real-time monitoring this framework calls for: live exposure tracking, VaR overlays, and intraday alerts that catch a limit approaching before it's breached. If you manage FX exposure across multiple counterparties, our use-cases page shows how teams put these controls into daily practice.
FAQ
What are single counterparty credit limits?
A single counterparty credit limit caps the total exposure one entity can have to a single trading partner, combining metrics like replacement cost and potential future exposure rather than relying on notional alone. It exists to prevent one relationship from creating outsized loss if that counterparty defaults.
Who counts as a counterparty in FX trading?
A counterparty is any entity on the other side of a trade, including banks, prime brokers, corporates, and non-bank liquidity providers. Each carries a distinct credit profile, so limits typically differ by counterparty type, with banks and prime brokers often warranting different treatment than corporate trading partners due to differences in regulatory oversight and settlement practices.
What is an example of counterparty risk in FX?
Counterparty risk materializes when one party to a forward or swap fails before the trade settles, leaving the other side needing to replace the position at a worse market rate. This replacement cost, along with any unsettled principal, is exactly what replacement-cost and PFE limits are designed to cap. For a broader view of related exposures, see our overview of FX risk types and mitigation strategies.
What does FX counterparty exposure mean?
FX counterparty exposure is the potential loss a firm faces if a trading partner defaults before a transaction settles, covering both current mark-to-market value and projected future movement. It is typically tracked through a combination of current replacement cost, potential future exposure, and net open position, as detailed above.
How often should FX counterparty limits be reviewed?
Most frameworks set a fixed review cadence, commonly quarterly, alongside immediate reviews triggered by events like a credit downgrade, a settlement failure, or a sudden concentration spike. Combining scheduled and event-driven reviews keeps limits aligned with current risk rather than stale assumptions.
Sources
- Supervisory letter (Basel-related guidance)
- Basel Committee consolidated guidance on CCR (BCBS D588)
- GFMA GFXD publications and recommendations (2026)
- ECB macroprudential bulletin — system-wide implications of counterparty credit risk