A limit breach alert tells your finance team the moment a currency exposure, hedge ratio or counterparty position moves beyond a boundary your policy has set. It only works if three things are decided in advance: the limit itself, the warning level that fires before the limit is hit, and the named person who must act. This guide covers all three for a UK business with currency exposure, plus what to do when an alert fires and how to stop the same breach recurring.
TL;DR
- A limit breach alert is a rule-based notification that fires when a monitored FX measure crosses a threshold set in your FX policy.
- Use two levels: an early warning below the limit (for example at 80%) and a breach alert at the limit. Each level needs an owner and a deadline.
- When an alert fires, confirm the data, identify the cause, decide on a response and record the decision, with senior sign-off for anything extreme.
- Review limits at least once a year and whenever your exposure changes materially.
- Alerts that nobody owns are noise. Write the escalation path into the policy before you switch anything on.
Table of Contents
- What a limit breach alert actually monitors
- Start with the policy, not the software
- Choosing thresholds: warning, breach and hard stop
- Configuring alerts: frequency, channel and ownership
- What to do when an alert fires
- Preventing repeat breaches
- A worked example
- Our perspective
- How Corphedge supports limit monitoring
- FAQ
- Sources
What a limit breach alert actually monitors
In treasury, "limit breach alert" means something different from the data-security notices that dominate the search results for similar words. Here the "breach" is a breach of a risk limit: a number you agreed internally, or with a bank, that your exposure must not exceed.
The common limit types in a corporate FX setting are:
- Net open position per currency. The unhedged amount you hold in, say, EUR, USD or SEK after netting receivables and payables.
- Hedge ratio bands. For example, 60% to 80% of forecast exposure hedged for the next six months.
- Value at Risk (VaR). The maximum loss you accept over a set horizon at a chosen confidence level.
- Counterparty and settlement limits. The maximum you are exposed to a single bank or settlement channel.
- Budget rate tolerance. How far the market may move against the rate in your budget before you must review.
The mechanics are well established in trading venues. As an example, CME Group's documentation explains that authorized Spot FX users can set email alerts when a chosen percentage, from 50% to 100%, of net open position and product limits has been reached. A corporate treasury version follows the same logic: a percentage-of-limit trigger that warns before the hard stop.
For a deeper look at the exposures themselves, our overview of FX risk types, exposures and mitigation strategies is a good companion.
Start with the policy, not the software
An alert can only be as good as the limit behind it. If your limits are vague, every alert becomes an argument about whether it counts.
HM Treasury's guidance for public bodies is a useful model even for private companies. It requires bodies with material FX risk to hold an FX policy document that sets out objectives, accountabilities, the FX risks and the process for identifying them. Translate that into four lines your alert rules can use:
- Objective. Protect budget margin, protect cash flow, or both.
- Limits. A number for each measure above, in a currency and over a horizon.
- Authority. Who may approve a trade, and who may approve an exception to a limit.
- Escalation. Who is told, in what order and within what time.
The size of the limits should reflect your business, not a template. A manufacturer importing components at a thin margin will set tighter bands than a services firm with a wide buffer. A practical way to find the number is to work back from margin: ask what rate move would take an order or a contract below the minimum margin you accept, and set the limit comfortably inside that point.
If you do not yet have a policy that a board or committee has approved, building one is the first job. Our guide to the FX risk committee mandate, members and meeting pack shows who should own limit approval and exceptions.
Choosing thresholds: warning, breach and hard stop
A single threshold gives you one chance to react, usually when it is already too late. Three tiers work better.
| Tier | Typical trigger | Who is told | Expected response |
|---|---|---|---|
| Early warning | 70% to 80% of the limit | Treasury analyst, treasury manager | Review forecast, prepare hedge options |
| Breach | 100% of the limit | Treasury manager, finance director | Hedge, reduce exposure or request a documented exception |
| Hard stop | Defined multiple of the limit, or a loss trigger | CFO, risk committee | Senior decision on action, possible suspension of new exposure |
The percentages are illustrative starting points, not a standard. Calibrate them to how fast your exposures move and how long it takes you to execute. If a hedge takes a day to approve and place, an alert at 95% of the limit is useless in a volatile week.
Alert on more than the level
A level alert tells you where you are. These tell you where you are heading:
- Speed. Exposure grew by more than a set amount in one day or one week.
- Forecast change. A large sales or purchasing forecast revision that shifts your hedge ratio.
- Market move. A currency pair moving through your budget rate or a stop-level you defined.
- Data staleness. Exposure data has not refreshed. A silent feed is also a risk.
Our article on four steps to set FX alerts that trigger real treasury action goes through the design of these rules in more detail.
Configuring alerts: frequency, channel and ownership
Three configuration choices decide whether an alert helps or gets ignored.
Monitoring frequency. Match it to the pace of your decisions. A business with monthly hedging cycles may be fine with daily checks of net open position, while a company with frequent multi-currency payments benefits from continuous monitoring and intraday alerts. Whatever you choose, state it in the policy so that nobody assumes someone else is watching.
Channel. Email is the minimum and gives you a record. Pair it with an in-platform notification and, for the hard-stop tier only, a phone or messaging escalation. Reserving the loudest channel for the rarest event keeps people responsive.
Ownership. Every alert needs a primary owner and a deputy, named by role rather than by person, so holidays and departures do not break the chain. Add a time limit, for example acknowledgment within two working hours for a breach.
A simple ownership matrix prevents confusion:
| Alert | Primary owner | Deputy | Acknowledge within |
|---|---|---|---|
| Early warning | Treasury analyst | Treasury manager | One working day |
| Limit breach | Treasury manager | Finance director | Two working hours |
| Hard stop | Finance director | CFO | Same hour |
Segregation of duties matters here too. The person who receives and clears an alert should not be the only person who can also approve the trade that cures it. Small teams can use compensating controls such as a second approver and a daily exception review, as described in our guide to fixing FX segregation of duties.
What to do when an alert fires
A calm, repeatable sequence beats improvisation. This one fits on a single page.
- Confirm the data. Check that the exposure figure is current and that the rate source and position feed are correct. A false alert caused by stale data still needs logging, and the data fix needs an owner.
- Find the cause. Was it a market move, a new order, a forecast change, a late payment or an unbooked hedge? The cause decides the cure.
- Choose the response. Options include placing a hedge, reducing or rescheduling the exposure, adjusting pricing, or requesting a formal exception with an expiry date.
- Get the right approval. Use the authority table in your policy. Exceptions without a named approver are policy failures in their own right.
- Record it. Log the alert time, the cause, the decision, the approver and the time to resolution.
- Report it. Include breaches in the regular pack for the finance director or risk committee.
For settlement and payment exposures, international supervisory guidance points the same way. The Basel Committee's guidance on settlement risk in FX transactions recommends a prompt review by credit management personnel when unplanned excesses occur, so that corrective action can be initiated. The same document notes that in extreme cases banks may suspend or cancel payment instructions, but only after careful review and a decision by senior management. Your own hard-stop tier should follow that principle: drastic action is possible, but it is a senior decision, not an analyst's reflex.
Preventing repeat breaches
A breach that happens twice is a design problem. After each one, ask whether the limit, the alert or the process needs to change.
- Review limits on a schedule. HM Treasury's guidance says bodies must review their FX strategy annually and whenever FX risk changes materially. A sensible private-sector habit is the same: an annual review plus a trigger review after a new market entry, a large contract or a change in funding.
- Look for patterns. If the same currency breaches at quarter end, the issue is probably forecasting or payment timing, not hedging.
- Test the escalation path. Once or twice a year, run a drill: send a test alert and check who answers and how quickly.
- Keep the evidence. A clean log of alerts, decisions and approvals is what auditors, lenders and boards want to see. See our explainer on currency risk reporting for finance teams for what a useful pack contains.
- Tune, do not mute. If an early warning fires constantly and nobody acts, move the level or fix the underlying exposure. Never just switch it off.
A worked example
Imagine a UK distributor buying in euros and selling in sterling. Its policy sets a maximum unhedged EUR position of €2,000,000 over the next six months, with an early warning at 80%.
A large new purchase order lifts the unhedged position to €1,650,000, which is 82.5% of the limit. The early-warning alert reaches the treasury analyst, who checks the data, confirms the new order and prepares two hedge options for the treasury manager. The next day another order takes the position to €2,050,000. The breach alert goes to the treasury manager and finance director, a forward contract is approved within the policy authority, and the position falls back inside the limit. The log records cause, decision, approver and time taken, and the forecast owner is asked to share large orders earlier. That last step is what prevents a repeat.
The figures are illustrative, but the pattern is the point: warn early, decide fast, record everything and fix the cause.
Our perspective
Most limit breaches we see discussed are not market surprises. They are information problems: the exposure was visible somewhere, but not to the right person at the right time.
That is why we built Corphedge around live exposure tracking, Value at Risk analysis, portfolio reporting and automated notifications in one place. Our aim is that a finance team sees a position drifting toward its limit while there is still time to choose a calm response, rather than learning about it in a month-end report.
We also believe small and mid-sized companies should not need an institutional treasury budget to work this way. Enterprise-grade analytics and 24/7 access are what we are designed to offer, with operational expert advice available when you want a second opinion on thresholds and escalation.
Start with the policy, define two or three tiers, name the owners, and let the software do the watching.
Bartas
How Corphedge supports limit monitoring
The Corphedge platform brings currency position tracking, hedging strategy simulation, VaR analysis, live market data and automated notifications together, so your thresholds and the exposure they watch sit in the same view. If you want help translating policy into alert rules, our operational expert advice and Risk Safari Tours are built for that conversation. Teams that prefer to build in-house knowledge first can take our FX hedging course for €220 (one-off). We are also expanding to Poland and Sweden, so groups with subsidiaries there can plan for coverage across those markets.
If you are choosing software, our FX risk software RFP questions cover the policy and cost points to put in front of any provider.
FAQ
What is a limit breach alert in FX risk management?
It is an automatic notification that fires when a monitored measure, such as net open position, hedge ratio or VaR, reaches or crosses a limit in your FX policy. Good setups warn before the limit is reached and again at the limit. Each alert is tied to an owner and a response deadline.
At what percentage should an early warning fire?
There is no universal figure. Many teams start between 70% and 80% of the limit and adjust according to how quickly exposure changes and how long a hedge takes to execute. Trading-venue tools show the principle: CME's Spot FX alerts, for example, let users choose any level from 50% to 100% of a limit.
Who should receive the alerts?
Send early warnings to the people who can prepare a response, usually the treasury analyst and manager. Send breaches to the finance director as well, and hard-stop events to the CFO or risk committee. Name recipients by role and give each a deputy.
How often should we review our FX limits?
At least once a year, and whenever your exposure changes materially, for instance after entering a new market or signing a large contract. HM Treasury's FX guidance sets the same annual and event-driven rhythm for the bodies it covers.
Sources
- CME Group: FX Spot+ Thresholds and Alerts
- HM Treasury: Guidance for the Management of Foreign Exchange Exposure (2023)
- Basel Committee: Supervisory guidance for managing settlement risk in foreign exchange transactions (2000)