FX forward points: why the forward rate is not a forecast of where spot will go

Forward points are the adjustment added to or subtracted from the spot exchange rate to produce a forward rate for a future settlement date. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What FX forward points means in practice

Forward points are the adjustment added to or subtracted from the spot exchange rate to produce a forward rate for a future settlement date. This matters operationally because an internal plan can still fail when the external bank, lender or counterparty applies the governing rule.

They mainly reflect the interest-rate relationship between the two currencies for the relevant tenor and should not be treated as the bank's directional forecast for the future spot rate. That wording should be translated into a short internal test showing the trigger, deadline, decision owner and evidence required for the business to proceed.

How FX forward points works from start to finish

Start by assembling spot rate, forward rate, tenor, currencies, quoted points, settlement date, notional, credit spread or other bank pricing elements and the underlying commercial exposure. These fields define the actual transaction and reveal whether a missing approval, timing condition or data point can stop the process before cash moves.

Next, identify the last safe decision point rather than only the formal deadline. A rejected file, missing consent or data query can consume hours or days, and a business that plans to the final cut-off has no recovery margin. For FX forward points, the specific checkpoint is this: Compare forward pricing on a like-for-like date and notional basis, record the commercial exposure being hedged and separate hedge policy from a speculative view on future spot.

The data and evidence that matter

Evidence should show both the decision and the external outcome. For FX forward points, retaining only an approval email is weak if the important fact is a bank status, lender consent, value date or counterparty confirmation that arrived later.

An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For FX forward points, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. In this workflow, the supporting record should cover spot rate, forward rate, tenor, currencies, quoted points, settlement date, notional, credit spread or other bank pricing elements and the underlying commercial exposure.

Where the process can fail

A manager may reject a hedge because the forward rate looks 'worse' than spot without recognising that the points reflect the economic cost or benefit of carrying the two currencies over time. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Automation introduces a different failure mode. A system can process an incorrect instruction consistently and at scale, so validation should occur before transmission and exception reporting should be independent of the originating process.

Worked example: test the mechanics

GBP/USD spot is 1.3000 and a six-month forward is 1.2850. The 150-point difference does not by itself mean the bank predicts sterling will fall to 1.2850; treasury should analyse the forward points and the underlying six-month cash-flow certainty rather than reading the forward rate as a forecast.

This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.

Governance and controls for FX forward points

Compare forward pricing on a like-for-like date and notional basis, record the commercial exposure being hedged and separate hedge policy from a speculative view on future spot. The procedure should identify the primary owner, reviewer and escalation contact so an absence does not suspend a material payment or funding decision.

Exception data should feed back into process design. Repeated repairs, late approvals or unexplained differences are evidence that the operating model needs attention, not just isolated mistakes.

Contingency planning should be proportional to the amount and time sensitivity. Treasury should know the alternate approver, payment route, funding source or bank contact before a live FX forward points issue becomes urgent.

Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and FX forward points is safest when the difference is explicit before the transaction proceeds. The reason for that discipline is concrete: A manager may reject a hedge because the forward rate looks 'worse' than spot without recognising that the points reflect the economic cost or benefit of carrying the two currencies over time.

A useful challenge question is whether the transaction would still be safe if a manager may reject a hedge because the forward rate looks 'worse' than spot without recognising that the points reflect the economic cost or benefit of carrying the two currencies over time. Where that answer is uncertain, compare forward pricing on a like-for-like date and notional basis, record the commercial exposure being hedged and separate hedge policy from a speculative view on future spot.