For Corporate Treasury & Exporter/Importer CFOs

The hedge you can defend is the one you wrote down before you knew the outcome.

CycleHedge resolves three cycles into one position on how much of the book is covered: your own exposure cycle, the structural cycle of the pair, and the interest rate differential that prices your forward points. Every call carries the timestamp of the moment it was issued, before anyone knew whether it was right. Every override is logged beside it. The framework is in advanced validation, and we publish no performance figure for it.

Built for importers, exporters, and corporates with foreign-currency volumes over $10 million a year.

Book a CycleHedge ConversationSee the proof

Somebody on the oversight committee – the board, the audit committee, the risk management committee – is going to ask the question differently this quarter, but the wording changes and the question does not.

“Walk us through your FX risk management framework.”

The honest answer, for most treasuries, is that there is no framework. There is a policy, a single rule inherited years ago. There is a bank email, which is a view.

There is a spreadsheet, which is a record of the hundred-percent forward cover that always gets placed because you got badly burnt when you were open and the market moved against you – and now don't want to be at risk.

Or the opposite– a hundred-percent Spot policy – for exactly the same reason (you got badly burnt when you took cover and the market moved in your favour, creating a huge forex loss), and for this reason you don't want to be at risk.

Or you have tried both, and they have both worked for a while, until they didn't– so now you sit on the fence, taking fifty-percent cover upfront and leaving fifty-percent uncovered, thinking this is the best you can do, but knowing there must be a better way.

That is the specific moment the page you are reading was built around.

Bring your company's exposure. See the framework. Decide with evidence.

Book a CycleHedge Conversation

You are trying to solve it as a prediction problem. But what you have is an FX risk management problem – and governance is what will expose that.

Every tool you have bought for your treasury was built to help you predict currencies better – bank advisory desks, Bloomberg terminals, treasury management platforms, macro research subscriptions. Your entire vendor stack sits on one side of a divide most treasurers have never had named out loud.

The divide is this.

A prediction system is evaluated by whether its forecast came true.

An FX risk management system is evaluated by whether its methodology is sound. That evaluation is what your risk, audit, and board committees are there to do.

For context on why we are the ones drawing this distinction: the analyst team behind CycleHedge publishes a twenty-one-year prediction record – 9,690 scored forecasts, of which 8,756 are on the Rand pairs at 72.3 percent average accuracy, all auditable. We hold the prediction credentials. What two decades of running them has made clear is that prediction credentials are not the document the committee is asking for.

The committee reviewing your hedging program – whether it sits as the board, the audit committee, or a standalone risk committee – is not running an accuracy check on your banker's six-month FX call. They are asking whether the process that produced your hedge placements was systematic, documented, and defensible in the same way a prudent-person review would defend any other fiduciary decision. Their job is the evaluation. Your job is to give them a methodology worth evaluating.

That is a different kind of question. And it is the one the industry has never built a product for.

Which is why your tools have improved every year and your anxiety before board meetings has not.

Why information alone is not enough.

Even when the information is correct, even when the timing is right, the decision still lands on a human. And the human is part of the crowd. The human is second-guessing. The human is the one whose name will be on the hedge placement if it moves against them.

Over twenty-one years I have fielded phone calls from clients who had the forecast in front of them, published, timestamped, unambiguous, asking whether they should act now or wait until tomorrow. They had the information. They had the timing. What they did not have was protection from their own emotions at the moment of decision.

Our published forecasts still carry a subjective layer. They tell you where the cycle is and where the market is likely to go. What you do with that, and when, is still your call.

CycleHedge removes that layer. The signal tells you what to do and when to do it. The committee reviews the log. The CFO defends the system, not the call.

I have had this conversation with more than one CFO operating at scale. Their point, in their own words, is that they need something to defend to the growers, boards, and committees they answer to. A documented system gives them a fall-back when things do not go to plan; a personal judgement call does not. Accountability sits with them either way, but one version gives them an audit trail to stand on, and the other leaves them standing alone.

The Indefensible Blank

The problem is not the question. The problem is what sits behind it.

If you have sat through the question, you know the problem is not the answer. The problem is that there is nothing systematic behind the answer.

You have spreadsheets. You have a bank email. You have a policy that says “always hedge fifty percent rolling, unless the CFO decides otherwise.” None of that is a framework. It is policy, opinion, and post-hoc narrative. It works in the room until somebody competent asks a second question.

And the second question, “what would have changed your reasoning?”, is the one that ends mandates.

Not because the hedge lost money. Boards do not fire treasurers for FX losses. They fire treasurers who cannot explain the process that produced the loss.

The stake is not the exchange rate. The stake is the methodology you can present when the market moves against you.

Five patterns that do not survive the audit.

Every treasury I have looked at runs one of these patterns. The first three are structured policies, each with a trauma behind it. The last two are what the treasury falls back to when the structured policy has already failed somebody in the room.

The Hundred-Percent Cover.

A policy of always hedging the full exposure, rolling – put in place by somebody who got badly burnt when the book was open and the market moved against them. It locks in a bad rate every time the cycle is moving in your favour, and it locks out the upside when the cycle turns. The decision was made once, under duress, by someone who is probably no longer in the seat. It cannot be defended as methodology because it was never methodology; it was a scar.

The Hundred-Percent Spot.

A policy of never hedging – take the Spot at the moment of receipt. Put in place by somebody who got badly burnt when cover was taken and the market moved in the company's favour, creating a forex loss on the hedge. The reaction is the mirror of the first. The consequence is the mirror of the first: full exposure to the adverse side of every cycle. Same trauma, opposite reaction, same absence of system.

The Fifty-Fifty Fence.

After trying both – and finding that both worked, until they didn't– the treasury sits on the fence. Fifty-percent cover rolling, fifty-percent uncovered, on the theory that it splits the difference. It does not split the difference; it guarantees mediocre outcomes across every cycle. When the board asks “why fifty?” the only honest answer is “because we tried everything else.” That is not methodology. That is exhaustion.

On top of all three of these policies – and often instead of them, once the structured policy has stopped being defensible – sits the less structured approach. When the policy is no longer carrying the argument in the room, the treasury falls back to something that at least feels like a judgement. It is not a methodology either. It is just a different kind of not-methodology.

The Judgement Call.

Someone senior “reads the market” and times the cover. When it works, nobody asks. When it does not, the board wants to know why the company locked in at the worst rate of the quarter. There is no defensible answer if the decision was based on feel.

The Bank's View.

Your relationship manager has a call. You know, privately, that the bank earns the spread whether the call is right or wrong. You also know, because every treasurer who has been in the seat for more than five years knows, that consensus bank FX forecasts have been documented to lose to a coin flip at most horizons (Meese & Rogoff, 1983; confirmed in subsequent studies). You quote the bank anyway because it is the only narrative available.

All five share one structural failure. The decision has no system behind it. There is nothing to audit. Nothing to defend. Nothing to show the committee beyond “this is what we did, and we thought it was the right call at the time.”

That is not a system. That is the absence of one.

Yet you know there must be a better way. After two decades watching every variant of these five patterns fail the same audit question, we set out to build what was missing – a documented timing discipline tailored to your exposure, your currency pair, and the phase of the cycle your book actually runs on.

Your exposure pattern, the pair’s structure and the rate differential resolve into one number: how much of the book is covered.

Three kinds of cycle run through every corporate FX book, and no vendor has ever connected them into a single timing discipline. CycleHedge reads all three and converts them into a hedge signal at each decision point.

1

The operational cycle.

The rhythm your book runs on – your financial year (or your season, if you are in agriculture) and the exposure windows inside it: receivables, creditor payments, the forward horizon you actually hedge to. The point at which exposure gets realised, and the decision window in which you can act on it.

2

The market-structural cycle.

Currency pairs move in measurable, recurring patterns. Not random. Not perfectly periodic. Cyclical in the specific sense that the phase of the cycle is identifiable in real time from the data, and can be recorded and reasoned about at the moment the decision is made rather than reconstructed afterwards. Point forecasts lose to a coin flip at most horizons. A position-sizing decision taken against phase-of-cycle is a different kind of decision, because it is probabilistic rather than directional, and it is judged across the sequence rather than on a single call.

3

The rate-structural cycle.

The rate differential between the two currencies in any pair sets the forward-point curve. Where the higher-rate currency is the one you pay (you import priced in it), holding forward costs you every day you hold. Where the higher-rate currency is the one you receive (you export priced in it), holding forward pays you. The differential determines who benefits from timing, and how much timing is worth in your reporting currency per year. The economics are universal; the magnitude varies by pair – most pronounced on emerging-market pairs like USD/MXN and USD/ZAR, measurable on USD/CAD, EUR/USD, and the G10 majors.

Rates and signals. Spot, forward and execution rate with the signal overlay – the call at each review point: when the forward is worth taking, and when the future spot is.

CycleHedge integrates the three into a HEDGE / WAIT / STOPPED decision on the cover ratio of your book, at the frequency your own exposure runs on. It is built so that every decision is timestamped, every decision logs its inputs, and the committee can read the ledger by week, by pair, by period – the call stops being yours alone to defend.

The oversight committee – board, audit, or risk – does not need to trust your judgement. They can read the ledger.

This is the documented discipline, built on your cyclesthat the prediction tools never delivered – repeatable every exposure period, systematized every week, defensible every time the committee asks.

The Audit Trail

Every call the mechanism makes is written down – every signal, the cover it set, and the market rate weeks later, each one timestamped before the outcome was known. The audit trail is how the committee reviews what the mechanism did – and it is the deliverable the whole system is built around.

The decision ledger. One row per exposure week – the signal, the cover it set, and the market’s spot at maturity, knowable only weeks after the call is made. Every decision timestamped when issued, every override logged. This is the document the committee reads.
Book a CycleHedge Conversation

Each decision carries the date it was taken, not the date it was explained.

One row per exposure week: the signal, the cover it set, the inputs the signal read, and the market's rate at maturity – a number knowable only weeks after the call was made. The row is written when the decision is taken, not when the outcome is known.

That ordering is the whole point. A hedging decision defended after the fact is a narrative. A hedging decision timestamped before the fact is evidence. The first one collapses under the second question from the committee. The second one does not.

Overrides are logged the same way. When the treasury departs from the signal, the ledger records the signal, the override, and the reason given at the time. That lets the committee review two things it has never been able to separate: how the method behaved, and how the people around it behaved.

What the ledger cannot do yet is show you a cleared performance record. CycleHedge is in advanced validation. Until the methodology clears its own internal gates, we publish no performance or savings figure for it.

Where the committee structure came from.

Before the productised rebuild, the same three-cycle discipline ran as a human-in-the-loop advisory engagement with the largest citrus exporter in the Sundays River Valley, from 2017 through 2019, across USD/ZAR, EUR/ZAR and GBP/ZAR on a rolling ten-week forward exposure window.

What matters here is not the outcome but the shape. The engagement was structured around a Risk Management Committee: every decision went through committee review, every weekly signal was documented, and every quarter was reviewed against a stated benchmark. That structure was not bolted on afterwards – it was the reason the arrangement held together, and it is the structure CycleHedge is being built to run without a human in the middle of it.

The analyst team's pedigree, not the CycleHedge proof.

The cycle-timing discipline underneath CycleHedge is the same one underneath the published Dynamic Outcomes forecast record: twenty-one years and 9,690 scored forecasts, of which 8,756 are on the Rand pairs at 72.3 percent average accuracy, all published, all auditable. The forecast record is the pedigree of the analyst team. It is not the CycleHedge proof.

CycleHedge does not require directional accuracy on any single forecast to work. It requires consistent phase-of-cycle identification, which is what the validation work measures. The public forecasts and CycleHedge answer different questions. The forecasts tell you where currency pairs are likely to go. CycleHedge tells you what to do and when to do it.

The methodology was originally built on USD/ZAR – the pair with the longest clean backtest horizon, the deepest rate differential, and the most pronounced cycle amplitude. The same three-cycle discipline was appliedto EUR/ZAR and GBP/ZAR in the 2017–2019 advisory engagement above. Expansion to the international pairs – EUR/USD, USD/CAD, and USD/MXN – is in progress, with each pair earning its own verified backtest before any engagement is quoted on it. The principle does not depend on which currency sits on which side of the pair. It depends on whether the book has forward-hedgeable exposure and a committee that audits the decision.

You do not need to take any of this on trust. Bring your pair, your exposure direction and your decision window, and we will walk you through the method and the record it produces – including what it does not yet answer. You leave knowing which of those two you are dealing with.

Book a CycleHedge Conversation
The Cost of Not Having It

Two treasuries running the same book across the same cycles – on different systems.

Consider two treasuries that started this year with the same book, the same currency exposure, the same quarterly board rhythm.

The first continues the approach it has always used. Fifty-fifty cover rolling, with occasional overrides when the banker's view is confident enough. Over the years ahead, across currency cycles that will include at least one COVID-scale dislocation and at least one rate-differential-driven currency repricing, the treasury will produce results that, looking at the data rather than the narrative, average out to roughly what a coin flip would have produced. The cost to the firm – timing value quietly left on the table – is never booked anywhere, which is exactly why it never gets argued about.

The second treasury runs a documented method built on its own cycles. Same markets, same volatility, the same cycles of currency strength and weakness – different system. Every board meeting, the treasurer walks in with a stated methodology, a signal log, and a record of what was decided and why, written down each week before anyone knew how it would turn out. The market moves against a position? Fine – the framework explains the position, and the board sees a process, not guesswork.

The difference between the two treasuries is not, in the end, a number on a slide. It is whether there is anything to read when somebody asks – and that is the methodology gap sitting underneath every board conversation.

The question is not which treasury got the better rate this quarter. The question is which one can explain how it got there.

Book a CycleHedge Conversation
Who This Is For

Corporate treasury teams who answer to the board and need a documented methodology.

Corporate treasuries and CFOs running annual FX exposure at the mid-market-to-enterprise scale, with board or audit-committee oversight of hedging decisions, who need documented, defensible timing methodology – not another prediction tool.

Currency pairs

  • USD/ZAR – the primary development pair: the longest clean data horizon, the deepest rate differential and the most pronounced cycle amplitude.
  • EUR/ZAR, GBP/ZAR – the other two pairs carried in the 2017–2019 advisory engagement.
  • EUR/USD, USD/CAD, USD/MXN – expansion pairs; each earns its own verified backtest before any engagement is quoted on it.

Scale coverage

The methodology is notional-agnostic – it reads the cycle, not the size of the book. Execution considerations at larger notionals – forward-curve liquidity, placement sizing relative to dealer appetite – are worked through against your counterparty stack in the conversation.

Where CycleHedge fits

Bank-agnostic – your existing counterparties execute and your existing treasury platforms run. CycleHedge is the timing-and-governance layer, and it is built to replace the judgement call, not the bank relationship.

Where it is not a fit

Treasuries that prefer a static, never-review hedging policy; companies where board and audit oversight is informal; books where the timing value does not clear the cost of implementation.

In Practice

How it is designed to land in your week.

Your signal frequency is set from your own invoicing and decision rhythm, not from a product default. For a book that runs weekly, that means Monday morning – the signal drop lands by email before European markets open: pair, direction, phase read, execution window, trigger level. Same format every time, same format every year.

Your treasury analyst (or you) executes through your existing bank counterparties, and the audit log is written alongside the decision rather than reconstructed at month-end. Export into your TMS and a board-ready pack are part of the designed delivery.

Onboarding is scoped at two to four weeks, including one cycle of parallel-signal review before anything is relied on. When the signal disagrees with judgement, your internal override protocol logs both the signal and the override with a signed-off reason.

The system makes the call. The record survives the audit.

Engagement

You are paying for the framework and the record it produces, not for a share of your spread.

We are not on the other side of your hedge, so nothing we earn depends on which way you cover. Annual engagement, scaled to book size and quoted on application. Structured as a retainer, not per-transaction.

Bank-agnostic. No commission. No spread participation. We are not on the other side of your hedge, and we do not earn more when you place one. Commercial terms are discussed once we both know whether there is a fit.

The Crossroads

You are a decisionaway from the answer.

You are not a year away from answering the question your oversight committee is going to ask – you are a decision away, and right now you are standing between two paths.

One path continues the policy you inherited: the fifty-percent rolling cover that came from nobody remembering who chose it, the bank email, the spreadsheet, the post-hoc narrative you have rewritten so many times you no longer hear yourself doing it.

The other path is the framework you can hand to the committee – board, audit, or risk – the same way you hand them the annual audit file. A signal log on your pair, your direction, your decision window. A mechanism that reads the three cycles and places the cover where the method says the cover belongs, with every decision timestamped and every decision auditable.

I have watched every variant of the five patterns fail the same question, through years that nearly broke every treasury in the room. What I could never hand a treasurer was a method that writes down its own reasoning before the market answers back. That is the thing we have been building.

Bring your pair, your exposure direction and your decision window. We will walk you through the method, the record it produces, and the parts that are still in validation. You will leave knowing whether this belongs in your treasury or not. No commitment to anything beyond the meeting itself.

The data decides.

Book a CycleHedge Conversation
James Paynter

James Paynter

Principal, Dynamic Outcomes

Twenty-one-year published currency-cycle track record

Direct line for reference discussions: james@dynamicoutcomes.io

CycleHedge is a hedge-timing decision-support framework, not financial advice. It is in advanced validation and is not represented as a cleared or production-validated performance product; no CycleHedge performance or savings figure is published. All hedging decisions remain the responsibility of the organisation taking them. The forecast record cited on this page is the published record of the Dynamic Outcomes analyst team and is not a measure of CycleHedge performance: Dynamic Outcomes (DBA Dynamic Forex Solutions) – 21 years of published FX forecasts – 9,690 scored forecasts, of which 8,756 are Rand-pair forecasts at 72.3% average accuracy and 934 are global forecasts at 57.3% average accuracy. Past performance does not guarantee future results.