Broken-date FX forwards: hedge the actual cash date instead of forcing everything into standard tenors

A broken-date FX forward is a forward contract with a maturity date that does not fall on a standard monthly or market tenor date. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What this means in practice

A broken-date FX forward is a forward contract with a maturity date that does not fall on a standard monthly or market tenor date. The finance team therefore needs a clear trigger, responsible owner and evidence standard before the concept can be relied on in a live transaction.

The forward rate is priced for the exact value date, allowing treasury to match a known commercial cash flow more closely than a standard one-, three- or six-month maturity. A concise checklist is useful only if it points to the authoritative source and does not turn a nuanced rule into an oversimplified yes-or-no box.

How the process works

The operating sequence should start with the trigger, move through validation and approval, and end only when the external result is confirmed. For this topic, the critical mechanics are: The forward rate is priced for the exact value date, allowing treasury to match a known commercial cash flow more closely than a standard one-, three- or six-month maturity.

Planning should work backwards from the required result rather than from the internal submission date. A correct instruction can still fail operationally if the company misses a notice period, scheme window, bank cut-off or response deadline.

The data and evidence that matter

A reproducible record includes underlying invoice or forecast, currency pair, notional, exact settlement date, spot reference, forward rate, points, counterparty and any expected timing uncertainty. This is stronger than a generic note saying the item was checked because it shows which condition was checked and against what source.

Where several systems participate, one transaction reference should connect the source record, approval, transmitted instruction and final response. Without that link, exception handling becomes an exercise in searching inboxes and spreadsheets after the deadline has already passed.

Where the process can fail

Using a standard tenor can create a gap in which the company must fund the currency early or roll the hedge if the commercial payment date is later. The exposure usually becomes more expensive to fix as the company gets closer to payment, settlement, testing or maturity.

Fragmented ownership can hide the problem. One team sees the contract, another sees the bank message and a third posts the accounting entry; without a named case owner, each can believe someone else has resolved the exception.

Worked example: test the mechanics

A euro supplier invoice is due in 47 days. A one-month forward matures too early and a two-month forward matures too late. A broken-date forward for the contractual payment date can reduce the need for an extra swap or rollover, provided the underlying cash date is sufficiently reliable.

The figures are illustrative, not universal terms. In a live case the company should replace every amount, date and threshold with the current bank, scheme or contractual evidence, then rerun the decision before cash is committed.

Governance and control design

Match hedge maturity to the most credible cash-flow date and document how timing uncertainty will be handled if the commercial payment moves. Management should see unresolved exceptions before the deadline, not only after they appear as failed payments, covenant breaches or reconciliation differences.

The control owner should track hedged cash flows with maturity mismatch, rollovers caused by timing changes and realised cost of hedge extensions. A stable headline volume can otherwise hide growing concentration, ageing or dependence on manual repair.

Periodic review should challenge controls that never produce exceptions. A zero-exception process may be excellent, but it may also mean the rule is not actually being tested or the data is too coarse to reveal problems.

Ownership should also survive absence and staff turnover. The procedure should say who acts, who reviews, where evidence is stored and what happens if the normal owner cannot complete the step. For broken-date fx forwards, undocumented expert knowledge is itself an operational dependency. The practical stop condition is linked to this risk: Using a standard tenor can create a gap in which the company must fund the currency early or roll the hedge if the commercial payment date is later. That scenario should be explicitly ruled out or escalated before the item is released.

A quarterly or event-driven control review should compare the documented procedure with what staff really do. Where the live workflow has diverged, the business should either update the policy deliberately or restore the intended control rather than allowing an undocumented middle ground. The operating response should follow this rule: Match hedge maturity to the most credible cash-flow date and document how timing uncertainty will be handled if the commercial payment moves. A reviewer should be able to see proof of that step in the retained transaction record.

The final operational safeguard is a tested fallback. The company should know which parts of underlying invoice or forecast, currency pair, notional, exact settlement date, spot reference, forward rate, points, counterparty and any expected timing uncertainty are required to execute safely if the preferred system, approver or communication channel is unavailable, and where a trusted copy can be obtained.