Reader question: A non-deliverable forward references two currencies, but at maturity the parties do not exchange both principal amounts. How can one fixing rate turn the entire FX contract into a single cash payment?
The answer is a cash-difference settlement algorithm. At trade date, the parties agree a forward rate, notional amount, settlement currency, valuation or fixing date and settlement date. Near maturity, a specified reference source provides the settlement rate. The algorithm compares the contracted FX economics with the economics implied by that fixing and converts the difference into one payment in the settlement currency.
The mathematics is compact. The operational difficulty is not. Quote direction, reference-rate source, fixing time, business-day calendar, disruption fallbacks and contract documentation all matter. A formula can be algebraically correct and still pay the wrong side if the currencies are inverted.
What this page owns — and what it does not
This page owns:
NDF terms + fixing source → settlement rate → single cash settlement amount.
It does not replace deliverable FX-swap and cross-currency pricing, CLS payment-versus-payment settlement, or financial date engines. An NDF deliberately avoids physical exchange of one currency pair’s two notionals.
This is public derivative mathematics, not a currency forecast, hedging recommendation or personalized financial advice.
Why NDFs exist
Some currencies are subject to capital controls, onshore/offshore market segmentation or other restrictions that make ordinary offshore delivery difficult or undesirable.
An NDF reproduces the economic effect of a forward-rate agreement without requiring both currency principals to be delivered.
ISDA’s public legal guidance describes the distinction clearly: a deliverable FX forward exchanges two currencies on the settlement date, while an NDF instead creates one cash settlement payment reflecting the difference between the contracted rate and a later spot or fixing rate.
The five essential contract inputs
A simplified NDF needs at least:
- Notional amount — the reference principal;
- Forward rate — the agreed contract rate at trade date;
- Settlement currency — the currency in which the final difference is paid;
- Valuation/Fixing date — when the settlement rate is observed;
- Settlement date — when the net cash amount is paid.
It also needs a settlement-rate option or other agreed source for the fixing and a rule for what happens if that source is unavailable.
The ISDA settlement-currency formula
ISDA’s public FX smart-contract guidance reproduces the 1998 FX Definitions formula for one common quote orientation:
Settlement Currency Amount = Notional Amount × [1 − (Forward Rate / Settlement Rate)].
The formula assumes the rates are quoted in the convention defined by the confirmation: the amount of Reference Currency per one unit of Settlement Currency.
This qualifier is not cosmetic. Changing the quote direction changes the algebra.
A worked example
Suppose:
- settlement currency = USD;
- reference currency = INR;
- notional = USD 1,000,000 under the stated formula convention;
- agreed forward rate = INR 84 per USD;
- settlement rate = INR 86 per USD.
Then:
Settlement Amount = 1,000,000 × [1 − 84/86].
≈ USD 23,255.81.
The sign tells us which party owes the cash amount under the transaction’s bought/sold-currency orientation. A production implementation must never infer payer direction from the magnitude alone.
Why the same economic trade can have a different-looking formula
FX rates can be quoted as:
local currency per USD
or:
USD per local currency.
These are reciprocals. If the formula is copied while the quote convention is inverted, the settlement amount is wrong.
This is one of the highest-value diagnostics in FX software: write the unit beside every rate.
Unit analysis exposes quote mistakes
Suppose:
Settlement Rate = 86 INR/USD.
The reciprocal is:
1/86 USD/INR.
An algorithm expecting INR/USD cannot safely accept USD/INR without explicit conversion.
If the system stores a floating number 86.0000 but not the currency-order metadata, it has lost part of the financial object.
The fixing date comes before the settlement date
An NDF generally observes the reference FX rate on a valuation or fixing date before the cash settlement date.
This separates two events:
- Fixing: determine the settlement rate;
- Settlement: pay the resulting cash difference.
If software uses the settlement-date spot rate when the contract specifies an earlier valuation date, it has changed the economics of the derivative.
The reference source is contractual data
The settlement rate may come from a central-bank rate, industry fixing, screen page or another source named by the confirmation and applicable definitions.
ISDA’s 1998 FX Definitions use the concept of a Settlement Rate Option. The settlement rate can be the specified rate or, where the documentation provides, a spot rate determined under the agreed mechanism.
The right source is therefore not “whatever FX rate is easiest to download.”
A reference rate can differ from tradable spot
A benchmark fixing may be calculated at a specified time or through an official methodology. It need not equal the price at which a participant could execute a large spot trade at that moment.
This can create fixing basis between the contract settlement value and executable market value.
A bank can therefore hedge the broad FX direction correctly and still experience a residual difference between the hedge rate and the contractual fixing.
NDF cash settlement removes principal exchange, not market risk
Because an NDF pays only a net difference, the parties do not exchange the full two-currency principals at maturity.
This removes the need to deliver the restricted or non-deliverable currency under the contract.
But until fixing, the mark-to-market value still changes with the FX forward curve, spot expectations, interest rates and basis conditions.
Pre-fixing valuation is a different algorithm
Before the fixing rate is known, the NDF has uncertain future settlement value.
A valuation engine can estimate that value from:
- current spot or offshore reference rates;
- forward points or NDF forward curve;
- discount factors;
- remaining time to fixing;
- counterparty and collateral terms.
After fixing, the exchange-rate uncertainty in the settlement amount largely disappears, leaving a known receivable/payable to be discounted or settled.
This page owns the fixing-to-cash transformation, not the full pre-fixing pricing model.
Clearing changes counterparty mechanics, not the basic fixing idea
LCH ForexClear and CME clear NDFs. A cleared NDF is novated to the CCP, which calculates margin and handles fixing and settlement under its rules.
LCH states that ForexClear undertakes the fixing and settlement of NDFs on maturity and uses its protected payments infrastructure for cash settlement.
The presence of a CCP changes counterparty exposure, margin and default management. It does not turn the NDF into a deliverable two-principal FX trade.
Disruption events are part of the algorithm
What if the contractual fixing source is not published?
What if a market closes unexpectedly?
What if capital controls change?
ISDA and EMTA documentation includes disruption events and fallback procedures for emerging-market FX transactions. These provisions determine whether the calculation agent uses an alternative rate, postpones fixing, applies another method or follows another agreed fallback.
A robust implementation therefore has an explicit state:
normal fixing unavailable → evaluate disruption event → apply documented fallback.
The 2026 FX Definitions are published but not yet the market implementation standard
ISDA and EMTA published revised 2026 FX Definitions on 3 March 2026. ISDA states that they are scheduled for implementation on 22 November 2027, when they will replace the 1998 FX and Currency Option Definitions as the market standard.
As of August 2026, systems therefore need to distinguish documentation written under the existing 1998 framework from future transactions that will migrate to the 2026 definitions.
This is a strong example of why financial algorithms need effective-date versioning.
The 2026 Definitions consolidate NDF market practice
ISDA states that the new definitions incorporate EMTA template terms and market practices for non-deliverable FX transactions and update disruption/fallback provisions.
An implementation should not silently apply future definitions to legacy trades. The governing confirmation and definition version remain part of the transaction state.
Counterexample: correct arithmetic, wrong quote direction
Suppose the contract rate is stored as 84 INR/USD but the settlement rate feed supplies 0.01163 USD/INR.
Both numbers describe the same market convention inversely. Substituting them into one formula without inversion creates nonsense.
This is a dimensional error, not a forecasting error.
Counterexample: current spot is not necessarily the contractual settlement rate
If the confirmation specifies a central-bank fixing at a particular time, using a dealer spot quote from five minutes later is wrong even if it looks more “market-like.”
The derivative pays according to its contract, not according to the programmer’s preferred price source.
Counterexample: zero cash settlement does not mean the trade had no economic purpose
If the settlement rate exactly equals the forward rate, the final NDF cash amount can be zero.
The contract still provided a hedge against FX movements during its life. A zero terminal cash amount merely means the fixing landed on the contracted rate.
Counterexample: an NDF does not eliminate settlement risk entirely
The contract avoids exchange of two principals, so principal FX settlement risk is structurally smaller than a gross bilateral deliverable exchange.
But one cash payment still has to settle. The parties or CCP can face counterparty, payment, liquidity and operational risk on that net amount.
Inputs and outputs
An NDF settlement engine can require:
- currency pair and quote convention;
- reference currency;
- settlement currency;
- notional amount and its currency;
- agreed forward rate;
- valuation/fixing date and time;
- settlement date;
- settlement-rate option/source;
- business-day calendars;
- governing FX definitions version;
- disruption-event and fallback terms;
- clearing status where applicable.
Outputs can include:
- observed settlement rate;
- reference-source timestamp;
- calculated settlement-currency amount;
- payer and receiver;
- normal/disrupted fixing status;
- fallback method used;
- settlement instruction and reconciliation identifiers.
Evidence polarity: what supports confidence?
Evidence for confidence includes a contract rate and fixing rate expressed in the same units, a fixing source that matches the confirmation, independent recomputation of the settlement amount, correct payer direction, consistent calendar treatment and explicit documentation-version traceability.
Evidence against confidence includes reciprocal-rate mistakes, using an intraday market rate instead of the contractual fixing, missing fixing timestamps, settlement amounts that change when the rate is displayed with the inverse quote convention, or fallback logic that cannot identify the governing contractual provision.
Weak links in implementation
Quote-direction loss. The system stores only the number, not USD/INR versus INR/USD.
Notional-currency ambiguity. The formula is applied to a notional expressed in the wrong currency.
Fixing-time mismatch. A correct source is sampled at the wrong timestamp.
calendar drift. Valuation or settlement dates are adjusted under the wrong business-day calendar.
fallback overreach. An alternative rate is used before the contractual disruption condition is satisfied.
rounding error. The fixing is rounded before settlement arithmetic when the contract requires more precision.
version drift. A 2027 definition change is applied to a 2026 legacy confirmation.
payer-sign inversion. Magnitude is correct but payment direction is reversed.
Diagnostics: how to test the engine
- par test: forward rate equals settlement rate → cash settlement should be zero.
- reciprocal test: convert both contract and fixing rates to the inverse quote and confirm the economic payment is unchanged after using the correct inverse formula.
- sign test: move fixing above and below forward rate and verify payer direction.
- source test: replace the contractual fixing with a nearby dealer rate and require a mismatch warning.
- holiday test: move fixing date across local-market holidays and verify the contract’s calendar convention.
- disruption test: remove the primary rate source and activate the documented fallback path.
- precision test: compare full-precision and rounded fixing inputs.
- clearing test: a cleared trade must map to CCP settlement and margin records without changing contract economics.
- version test: run otherwise identical trades under the applicable 1998 and future 2026-definition configurations and expose any rule differences explicitly.
- independent calculation test: use a second implementation of the settlement formula.
What would falsify confidence?
Confidence should be withdrawn if the engine cannot reproduce a confirmed NDF settlement; if reciprocal quote conversion changes the economics; if the fixing source or definition version is unknown; if disruption fallbacks are undocumented; or if the payer direction cannot be derived deterministically from the trade orientation.
Alternatives and limits
A deliverable FX forward exchanges both principals and is appropriate where currencies can be delivered. An NDF is useful where the contract is intended to settle only the cash difference. FX swaps, options and cross-currency swaps solve different exposure profiles.
No NDF settlement formula forecasts the future fixing. It only converts the realised contractual fixing into the agreed payment.
How this connects to the surrounding knowledge estate
FX forward and swap mathematics explains forward-rate formation. CLS PvP settlement handles two-principal deliverable FX settlement for eligible trades. Date engines determine fixing and settlement dates. NDF settlement owns the distinct transformation from contractual fixing to one cash payment.
Verification and update triggers
Preserve currency pair, quote convention, notional currency, forward rate, fixing source, fixing time, settlement date, definitions version, fallback matrix and clearing status. Revalidate after benchmark methodology changes, central-bank fixing changes, FX-definition updates, local-market holidays, clearing-rule changes or any settlement dispute.
Primary and high-quality references
- ISDA, 1998 FX and Currency Option Definitions.
- ISDA, Legal Guidelines for Smart Derivatives Contracts: Foreign Exchange Derivatives, including the public NDF settlement formula.
- ISDA and EMTA, 2026 FX Definitions announcement, including the 22 November 2027 implementation date.
- ISDA, Additional Provisions to the 1998 FX and Currency Option Definitions, including cash-settled and disruption documentation.
- LCH ForexClear, What We Clear, describing cleared NDF fixing and settlement.
Educational boundary: This article explains public NDF settlement mathematics. It does not forecast exchange rates, recommend an NDF or provide personalized financial advice.