Foreign Exchange

How banks price, book, hedge, fund and settle currency transactions, with worked examples and controls for operations, risk, finance and technology teams. The architectures and examples are illustrative; contracts, currency rules and local market procedures govern implementation.

How to read this chapter

Foreign exchange is not simply the conversion of one currency into another. In a bank, FX is the meeting point of market price, customer need, currency liquidity, nostro funding, settlement risk, payment processing, regulatory screening, confirmations, reconciliation, accounting, P&L, risk limits and operational cut-offs. A customer may only see a rate on a screen, but behind that rate the bank has to quote, book, hedge, settle, fund, reconcile and report two currency legs correctly. If one leg fails, the bank may face funding cost, principal risk, market loss, customer complaint, compliance investigation or operational break.

Read this chapter as a banking flow. A corporate may need USD to pay an invoice while holding EUR. A fund manager may need USD to settle a US securities purchase. A bank treasury desk may have surplus EUR but need short-term USD liquidity. A retail customer may send an international payment where the debit currency differs from the beneficiary currency. A markets desk may quote spot, forward or swap prices. An operations team may have to settle currencies across time zones and correspondent accounts. A risk team may monitor open FX positions. A finance team may revalue positions. A technology team may connect channel, pricing, trade capture, payment engine, confirmation platform, nostro reconciliation and reporting. FX is therefore both a markets topic and a payments topic.

The most practical mindset is this: Deliverable FX creates two currency obligations. One currency is delivered, another is received, and both have value dates, settlement calendars, accounts, cut-offs and risks. An NDF instead settles a calculated difference in one currency, and an option may expire without an exchange of principal. The rate is only one part of the story. The full banking story includes who quoted, who accepted, what product was booked, what value date applies, which accounts move, whether the trade is confirmed, whether settlement is protected, whether sanctions or payment repair affects the flow, whether the nostro has enough cash, whether the risk position is within limits and whether the customer receives the right explanation.

The BIS Triennial Central Bank Survey is the most comprehensive global source on FX and OTC derivatives market size and structure. BIS reported that global FX trading reached $9.6 trillion per day in April 2025, with the US dollar on one side of 89 percent of all FX trades according to its 30 September 2025 press release (BIS 2025 survey release). That scale matters. FX is not a side desk. It is one of the largest markets in the world and one of the daily operating systems of international banking.

Learning objectives

By the end of this chapter, you should be able to explain spot FX, forwards, swaps, non-deliverable forwards and basic options in banking language. You should understand how FX connects to cross-border payments, securities settlement, treasury liquidity, nostro funding and client pricing. You should be able to explain settlement risk, payment-versus-payment, CLS, cut-off times, confirmation matching, failed settlement, reconciliation, accounting, rate governance and payment-linked exceptions. You should also be able to design BA, developer and testing scenarios for FX flows across channels, pricing, trade systems, payment engines, risk, finance and operations.

1. Why FX is more than currency conversion

A customer sees FX as a conversion. A bank sees a chain of obligations. If a corporate buys USD against EUR, the bank must agree a rate, capture the trade, update the risk position, confirm the deal, debit or receive EUR, deliver or receive USD, manage cut-off times, fund the relevant nostro, reconcile the cash movements, account for the transaction and report it correctly. If the trade is linked to a payment, securities purchase, loan drawdown, invoice settlement or treasury hedge, the FX trade becomes one leg of a bigger process. If the bigger process fails, the FX leg may need cancellation, amendment, rollover or unwind.

The FX market is also the currency language of international banking. Cross-border payments move through correspondent accounts. Securities bought in a foreign market require local currency funding. Treasury invests and borrows across currencies. Markets desks provide prices to clients. Risk monitors open positions and stress loss. Finance translates foreign-currency results into reporting currency. Operations ensures settlement instructions are right. Compliance screens counterparties and payment messages. A currency mismatch may begin as a normal customer request and become a liquidity or settlement problem if the operational design is weak.

For business analysts, the most important point is that FX creates two sides. If the bank sells USD and buys EUR, both legs matter. If USD is paid but EUR is not received, the bank has settlement exposure. If the value date is wrong, cash arrives on the wrong day. If the customer payment is stopped by sanctions screening after the FX trade is booked, the bank needs clear rules for what happens next. If the customer receives a guaranteed rate for a payment but the payment is repaired two days later, the product must define whether the rate still stands.

The FX desk also needs to understand purpose. A customer trade, a treasury funding swap, a hedging forward, a speculative trading position and an operational conversion for a payment may all use currency exchange, but they are not the same business. They carry different pricing, documentation, limits, settlement treatment, reporting and conduct requirements. Strong banks classify FX activity by purpose and control it accordingly.

2. Currency pairs, quotation and direction

FX is quoted as a currency pair. EUR/USD, GBP/USD, USD/JPY and USD/INR are examples. The first currency is the base currency and the second is the quote currency under standard market convention. If EUR/USD is 1.1000, one euro is worth 1.1000 US dollars. If the rate rises, the euro has strengthened against the dollar in that pair. If USD/JPY is 150.00, one US dollar is worth 150 Japanese yen. Direction matters because many operational and customer disputes begin with confusion about which currency the bank bought or sold.

Banks often speak in terms of buying and selling from their own perspective. If the bank buys EUR/USD, it buys EUR and sells USD. If a customer buys USD against EUR, the customer sells EUR and buys USD. The bank’s side is the opposite of the customer’s side. Trade capture systems must be unambiguous: bought currency, bought amount, sold currency, sold amount, rate, value date and counterparty. A screen that shows only one amount and one rate without clear direction can create serious booking mistakes.

Some currency pairs are quoted with many decimal places. A pip is a common unit of price movement, though pip size varies by currency pair. For many pairs, one pip is 0.0001. For yen pairs, one pip is often 0.01. Banks also use points, spreads, margin and all-in rates. A customer may receive an all-in rate that includes market rate plus customer margin. Internally, the bank may store market mid, bid, offer, client spread, trader spread, sales margin and final executed rate separately. This matters for transparency, P&L and conduct.

Currency pair convention also affects system design. The bank may need to support direct pairs, indirect pairs and cross rates. If a direct market quote is unavailable or illiquid, the bank may calculate a cross rate through a common currency such as USD. Cross-rate calculation must handle precision, rounding, market direction, spreads and cut-off windows correctly.

Worked direction and spread example

Assume a firm EUR/USD quote of 1.1000 / 1.1002, in USD per EUR, from the dealer's perspective. The dealer buys EUR at the bid and sells EUR at the offer. A corporate selling EUR 1,000,000 to buy USD receives USD 1,100,000 at the bid, before any separate fee. Buying EUR 1,000,000 costs USD 1,100,200 at the offer. A quoted client margin must be applied in the correct direction: reducing the EUR/USD bid to 1.0990 gives that EUR seller USD 1,099,000, rather than increasing its receipt. The difference against the dealer bid is USD 1,000, before hedge costs and expenses, not automatically net profit.

Inverting a two-way quote reverses the sides: USD/EUR bid = 1 / 1.1002 and offer = 1 / 1.1000. A system that takes reciprocals without reversing sides can produce an inverted spread. For a mid-only arithmetic illustration, EUR/USD 1.1000 and USD/JPY 150.00 imply EUR/JPY 165.00 JPY per EUR: the USD units cancel. Executable cross prices require consistent bid/offer sides, timestamps and liquidity, not multiplication of unrelated mids. CME explains base and quote currency conventions.

Store the currency units with the rate. Decimal precision for the rate, money precision for each currency, and the final rounding rule are different choices. Retain unrounded calculation inputs and round only at the contractually specified step; independently recalculate both amounts before accepting a manual repair.

3. Quote-to-settlement operating algorithm

A practical FX operating sequence starts before the customer sees a rate. First, the channel captures customer intent: currencies, amount, account, purpose, product, value date and payment linkage where relevant. Second, the system checks eligibility: customer status, account permissions, product access, currency availability, cut-off, sanctions or compliance pre-checks where applicable, credit limit for forward products and treasury availability. Third, the pricing engine builds a quote from market source, spread policy, customer tier, trade size, product type and validity window. Fourth, the customer or dealer accepts the quote. Fifth, the trade is booked with clear bought and sold currency direction. Sixth, risk and position systems update. Seventh, confirmation or advice is generated. Eighth, settlement instructions are prepared. Ninth, the payment or cash movement settles through CLS, correspondent accounts, internal accounts or local systems. Tenth, nostro reconciliation and accounting prove the cash and P&L.

This sequence matters because many FX defects are handoff defects. A quote may be correct but expire before acceptance. A trade may book but fail settlement because its standard settlement instructions (SSIs) are wrong. A payment may pass validation but fail sanctions screening after FX booking. A forward may be sold before credit limit is approved. A customer may accept a rate in the channel but the trade capture message may be duplicated during retry. A settlement may complete in one currency but fail in the other. A good bank designs status, ownership and recovery for each step.

The operating algorithm should produce traceability. A user should be able to move from customer instruction to quote request, quote response, accepted rate, trade ID, payment ID, confirmation, settlement instruction, nostro entry, accounting entry, P&L and customer statement. In payment-linked FX, references such as payment ID, UETR where relevant, customer reference, trade reference and reconciliation reference should remain connected. If a complaint arrives, the bank should explain the flow without manual archaeology.

For BA and developers, the practical requirement is not “perform FX conversion.” It is “control the quote-to-settlement lifecycle.” Build quote expiry, idempotency, duplicate prevention, product eligibility, market closed handling, settlement status, payment status linkage, accounting status, reconciliation status, exception owner and audit evidence.

Front, middle and back office responsibilities

These responsibilities can sit in different organisations. The control is independent challenge and a traceable hand-off, not a mandatory department name. Confirmation, risk updates and settlement preparation can run in parallel after execution. A settlement gate is separate from economic booking: a hold cannot erase a legally agreed trade.

The diagram separates trade events from payment evidence. A network acknowledgement proves receipt or validation at a messaging layer; it does not by itself prove irrevocable cash settlement. A UETR identifies a supported payment journey and must not be manufactured as the identifier for every FX trade.

4. Spot FX

Spot FX is the exchange of one currency for another on the standard spot value date for the currency pair. Many major pairs settle on T+2, but conventions differ. Some same-day or next-day flows exist depending on product and market. Obtain the currency-pair convention from the venue or approved reference-data source, rather than assuming a bank-wide spot tenor. Holidays matter because both currencies need valid settlement days. If one currency’s market is closed, the value date may move. A spot trade is therefore not simply “today plus two.” It is a value-date calculation across currency calendars.

Spot FX is used for customer conversions, cross-border payments, treasury funding, trade settlement, travel money, card settlement, securities purchases and operating needs. The product may appear simple, but operational timing is strict. A trade booked late may miss the payment cut-off. A trade booked for a currency with a local holiday may settle later than expected. A trade linked to a payment may need the payment to pass screening and repair before FX settlement. A trade linked to securities settlement may need currency cash before the securities settlement deadline.

Spot pricing depends on market bid and offer, trade size, liquidity, currency pair, client relationship, spread policy and market volatility. A bank may quote a tighter spread to an institutional client and a wider spread to a retail or SME channel depending on policy, cost and product design. Conduct risk appears when pricing is not transparent or when a customer is led to believe a rate is guaranteed when it is not. Systems must record quote time, expiry time, accepted rate, margin and user acceptance.

From a risk perspective, spot trades create open positions until hedged or offset. If the bank buys USD from one customer and sells USD to another, positions may offset. If customer flow creates imbalance, the bank may hedge in the interbank market. Real-time risk updates are important because exchange rates can move quickly. A small operational delay between customer booking and market hedge can create P&L exposure if volumes are large.

5. FX forwards

An FX forward locks an exchange rate for a future value date. A corporate expecting to pay USD in three months may buy USD forward against EUR today. This protects against adverse currency movement. If USD strengthens by the payment date, the corporate has already locked a rate. If USD weakens, the corporate may regret the forward economically, but the hedge served its purpose: certainty. A forward is not a prediction product by default. It is a risk-management product.

The forward rate is linked to spot and interest-rate differentials between the two currencies, adjusted for market basis and funding conditions. Learners often think a forward rate is the bank’s forecast of future spot. That is usually wrong. In covered-interest-rate logic, forward points reflect the relative cost of money in the two currencies. If one currency has a higher interest rate than the other, the forward points adjust so that arbitrage is controlled. In real markets, cross-currency basis, credit, liquidity, balance sheet and demand can influence pricing.

For banks, forwards create several responsibilities. The trade must be documented and confirmed. Credit exposure must be measured because the counterparty may owe money at maturity depending on market movement. Collateral may be required under agreements for professional counterparties. The position must be revalued. The settlement date must be tracked. If the underlying commercial payment changes, the customer may ask to amend, extend, pre-deliver or cancel the forward. Product rules must define how that is handled and how costs are calculated.

For business analysts, forward lifecycle scenarios are critical. Test new forward booking, maturity settlement, early drawdown, extension, cancellation, partial utilisation, rate reset if product allows, credit limit breach, collateral call, payment linkage failure, customer cancellation and accounting revaluation. A forward is operationally alive until maturity or termination. Treating it like a one-time conversion is a design mistake.

Forward points with explicit units

For an illustrative 90-day EUR/USD forward, assume spot S = 1.1000 USD per EUR, simple USD rate 5%, simple EUR rate 3%, and ACT/360 for both interest periods from the spot value date to forward value date. Ignore bid/offer, basis, collateral and fees. Covered-interest parity gives:

F = S × (1 + rUSD × 90/360) / (1 + rEUR × 90/360)

F = 1.1000 × 1.0125 / 1.0075 = 1.105459057 USD per EUR

Forward points are F minus S = 0.005459057, or about 54.59 pips when one pip is 0.0001. A corporate buying USD 1,000,000 pays about EUR 904,601.57 at that forward, before rounding and charges. This is an outright rate derived under stated assumptions, not a forecast of the future spot price. The numerator is the quote-currency interest factor; swapping it with the base-currency factor reverses the points. BIS explains covered-interest parity and why actual markets can exhibit a cross-currency basis.

In production, use actual curve discount factors and each leg's conventions, including the starting value date, rather than assuming both currencies use the same day count. A 90-calendar-day period is not necessarily a contractual three-month tenor. A hedge termination is a new valuation and settlement event: any cancellation gain or charge depends on replacement economics, remaining tenor and contractual terms.

6. Non-deliverable forwards and restricted currencies

A non-deliverable forward, or NDF, is a forward contract where the two parties do not exchange the restricted or non-deliverable currency at maturity. Instead, they settle the net difference in a freely deliverable settlement currency, often USD, based on an agreed fixing rate. NDFs are used for currencies where local market restrictions, capital controls or settlement limitations make physical delivery difficult or impossible for offshore participants.

NDFs are important because they show that FX is not always two simple cash legs moving through nostros. The bank still takes currency risk, but settlement is usually net cash settlement in the settlement currency. The contract must define notional, reference currency, settlement currency, fixing source, fixing date, maturity, settlement date and calculation method. If the fixing source is unavailable or disputed, fallback rules matter.

Restricted currencies create additional operational and compliance requirements. Some currencies require local documentation, purpose codes, central-bank reporting, tax checks, local settlement accounts or regulatory approval. Some cannot be freely converted offshore. Some have different onshore and offshore markets. A bank should not offer a currency product simply because a rate can be displayed. It must know whether it can legally and operationally settle, report and support the currency.

For BA work, NDF and restricted-currency requirements should include fixing source, fixing calendar, settlement currency, local regulatory fields, permitted customer types, country restrictions, documentation checklist, cancellation rules, settlement method, accounting treatment and customer explanation. A normal spot/forward design is not enough for restricted currencies.

A cash-settled NDF example

This is an explicitly defined teaching contract, not a claim that all NDF confirmations use one formula. The client economically buys USD 1,000,000 and sells local currency at K = 80.00 local units per USD. The local-currency equivalent is 80,000,000. The agreed fixing is R = 82.00 local units per USD; settlement is in USD, two valid business days after the fixing under the example's calendar. Define the USD amount payable to the USD buyer as:

USD notional × (R - K) / R = 1,000,000 × 2/82 = USD 24,390.24

The buyer receives USD because the local currency weakened. Equivalently, USD 1,000,000 minus 80,000,000 / 82 produces the same result. At R = 78.00 the amount is negative, so the buyer pays USD 25,641.03. Neither party delivers 80,000,000 local-currency principal. Reverse quotation, a local-currency-defined notional or different contractual settlement terms require a correspondingly different calculation. Test both signs, a zero result, fixing precision and rounding; do not reuse a deliverable-forward payment template.

Operations records the authenticated fixing, rate source, publication time, contractual fallback decision and resulting cash obligation. A correction must preserve the original fixing and reissue affected calculations and reports through controlled versions. NDF clearing, when used, adds a CCP and margin lifecycle; it is distinct from PvP for a deliverable exchange. CME's cleared OTC FX service provides an example of clearing for NDFs.

7. FX swaps

An FX swap combines two linked currency exchanges: a near leg and a far leg. The near leg exchanges currencies on an earlier value date, and the far leg reverses the exchange on a later value date. Economically, FX swaps are major funding tools. A bank with surplus EUR and short USD can use an FX swap to receive USD now and deliver it back later, while delivering EUR now and receiving EUR later. The product changes currency liquidity over time without creating the same long-term outright FX exposure as a simple spot position left open.

FX swaps are used heavily by bank treasury, money-market desks, institutional investors, corporates and dealers. They help manage currency funding, roll short-term exposures, hedge settlement needs, cover securities purchases and balance nostro positions. They also influence cross-currency basis and short-term funding markets. During stress, FX swap markets can become expensive or less available, especially for currencies where dollar funding demand is high. A bank should not assume that currency transformation will always be cheap and unlimited.

Operationally, FX swaps are more complex than a spot trade because both legs must be captured, confirmed, valued, settled and reconciled. The near leg and far leg may have different cash-flow directions. The far-leg rate is derived from spot and swap points. Systems must ensure the two legs stay linked. If the near leg settles and the far leg is wrong, the bank has a future problem. If one leg is amended, the relationship to the other leg must remain clear.

For liquidity management, FX swaps are powerful but not free. They rely on counterparty limits, market access, collateral or credit support where applicable, settlement arrangements and value-date calendars. A treasury desk may use swaps to convert one currency into another, but liquidity risk should stress what happens if swap capacity shrinks or basis widens. In a real stress, the bank may be liquid in one currency and short in another, and the swap market may be the bridge. If the bridge is narrow, management needs to know early.

Funding swap cash ladder

Suppose a bank needs USD for one month and has EUR cash. In an illustrative linked swap it delivers EUR 10 million and receives USD 11 million on the near date at 1.1000. On the far date, it receives EUR 10 million and delivers USD 11.02 million at 1.1020. The far amount is EUR notional multiplied by the far rate. The bank must fund the full USD 11.02 million maturity obligation, not only the USD 20,000 difference. That difference is not a standalone interest expense: it also reflects the EUR funding opportunity and the two-currency pricing structure. Record both obligations in the currency ladders and prevent rollover from quietly concealing a concentration of maturities.

An FX swap has two exchanges. A cross-currency interest-rate swap can also have periodic interest, principal exchanges and resettable notionals according to terms; it is not interchangeable with a short FX funding swap. See the derivatives chapter for the longer collateral and interest lifecycle.

8. FX options in banking language

FX options give the buyer a right, not an obligation, to exchange currencies under agreed terms. A vanilla call option gives the right to buy a currency. A put option gives the right to sell a currency. In FX, options are often described by the currency being bought or sold, strike, expiry, notional, premium and settlement terms. Options can be used by corporates to hedge while preserving upside, by investors to express views, and by banks to manage or intermediate risk.

The key difference from forwards is optionality. A forward creates an obligation to exchange at maturity. An option gives choice to the buyer. That choice has value, so the buyer pays a premium. Option value depends on spot rate, strike, time to expiry, interest-rate differentials, volatility and other factors. Volatility is central. Higher expected volatility usually increases option premium because the right to choose becomes more valuable when the exchange rate can move more.

Operational teams do not need to become option-pricing quants, but they must understand lifecycle. Premium must be paid. Confirmation must capture strike, expiry, exercise style, settlement method, barrier or exotic features if any, and cut-off for exercise. At expiry, the option may be exercised, expire worthless, or automatically exercise depending on terms. A deliverable exercise creates agreed currency exchanges; a cash-settled exercise creates the contractual net amount instead. A EUR call/USD put describes both sides of the same vanilla option, so the strike must carry the quotation units and the exercise must identify both amounts. Exotic options add more complexity and should be controlled through product approval.

Conduct and suitability are important. Options can protect customers, but they can also be misunderstood. A zero-cost collar, participating forward, accumulator or barrier structure may look attractive but embed conditions. Customer-facing teams should explain outcomes under different market movements. A product sold as protection can create surprise if the customer does not understand obligation, leverage or barrier features.

9. FX and cross-border payments

FX and payments are tightly connected. A customer may initiate a cross-border payment in one currency while funding the account in another. The bank may convert before sending, after receiving, during repair or through treasury depending on product design. That design affects customer transparency, pricing, cut-off, rate hold, cancellation, charges, reconciliation and beneficiary value. Payment professionals must understand FX because many payment complaints are really FX timing, rate or settlement questions.

Consider an outward payment where a customer holds EUR and wants to send USD. The bank may debit EUR, convert to USD and send USD through a correspondent or clearing channel. If the payment passes immediately, the FX and payment move together. If sanctions screening holds the payment, the bank must decide whether the FX trade remains valid, is cancelled, or is held pending release. If the beneficiary bank rejects the payment, the return may arrive in USD while the customer expects EUR credit. The bank needs return FX rules. If the original rate is not available, who bears the difference? Product terms must answer.

Incoming payments can also involve FX. A bank may receive USD for a customer whose account is in EUR. The bank may auto-convert, hold a foreign-currency balance, ask for customer instruction or reject depending on product. If the incoming payment lacks clear remittance, account or currency instruction, repair may delay conversion. If rates move during repair, customer expectation must be managed. Reconciliation must link incoming currency, conversion trade, customer credit and charges.

In ISO 20022 payment environments, currency fields, instructed amount, interbank settlement amount, equivalent amount, charges, exchange rate and settlement date can carry important FX meaning depending on message type and scheme. Payment engines and FX engines must agree on what amount is converted, what rate applies, when the rate is locked and what happens on return, recall, repair or investigation. This is exactly where banking BA skill becomes valuable.

10. Payment-linked FX exception rules

Payment-linked FX needs explicit exception rules because payment status and FX status can separate. A payment may be screened, held, repaired, rejected, returned, recalled, cancelled or delayed after the FX quote is accepted. The bank must define what happens to the FX position in each case. Without rules, operations teams improvise under pressure and customers receive inconsistent answers.

The main exception cases are common. If FX booking fails before payment release, the payment may be held or routed to manual pricing. If FX books successfully but payment screening holds the payment, the bank may keep the FX, hedge exposure, cancel according to policy or wait for compliance decision. Quote expiry governs whether an unaccepted quote can be accepted; it does not by itself cancel an executed contract. If payment release is delayed after acceptance, product terms must specify the rate-hold and amendment process, including any required fresh customer consent. If the beneficiary bank returns funds in the foreign currency, the bank must decide whether to credit the foreign currency account, reconvert to debit currency, use original rate, use current rate or apply a product-specific refund rule.

Charges complicate the picture. Correspondent charges may be deducted from the foreign-currency leg. Some payment products show fees separately; others embed margin in the rate. A return may come back net of charges. Customer service needs the audit trail to explain why the returned amount differs from the original debit. This is not only finance logic. It is customer trust logic.

A robust design links FX trade status and payment status. The system should show quote accepted, FX booked, payment pending screening, payment released, settlement pending, settlement completed, returned, refunded and reconciled. It should prevent duplicate FX booking during payment retry and prevent payment release when the linked FX state is invalid. This control prevents a retry or delayed response from creating a second conversion for the same accepted instruction.

11. Nostro liquidity and currency funding

A nostro account is an account a bank holds with another bank in a foreign currency or foreign location. FX settlement and cross-border payments often move through nostro accounts. A bank may sell EUR and buy USD, but the practical question is whether USD is available in the correct nostro account by the settlement cut-off. A profitable FX trade can still create operational pressure if the nostro is unfunded or if incoming funds arrive late.

Treasury and operations must manage nostro balances carefully. Too little balance can create overdrafts, failed payments or urgent funding trades. Too much balance can trap liquidity and reduce income. The right balance depends on currency, flow pattern, correspondent limits, payment cut-offs, intraday volatility, customer behaviour, scheme rules and market access. High-value currencies may require more active monitoring. Exotic or restricted currencies may require special funding arrangements.

Nostro reconciliation is a core control. The bank must match expected cash movements to actual account entries. Breaks may arise from failed trades, late payments, charges, value-date differences, correspondent fees, returns, rejected payments, repaired instructions, wrong SSIs or manual postings. An aged nostro break is not harmless. It may hide a missing receipt, duplicate payment, wrong customer credit or settlement failure.

For real-time payments and extended operating hours, nostro management becomes even harder. Customer channels may continue when wholesale FX markets are less liquid or closed. Weekend flows, holiday mismatches and time-zone gaps matter. A bank offering 24/7 international payment features must decide how it prices, funds and controls currency conversion outside normal market hours. That is a product design question and a treasury question.

12. Settlement risk, PvP and CLS

FX settlement risk is the risk that one party pays the currency it sold but does not receive the currency it bought. This is sometimes called Herstatt risk, after the 1974 failure of Bankhaus Herstatt, where time-zone settlement created losses for counterparties. The risk remains important because currencies settle in different systems, jurisdictions and time zones. BIS has repeatedly highlighted FX settlement risk as a financial stability concern. In a December 2022 BIS Quarterly Review article, BIS explained that FX settlement risk arises when one party fails to deliver the currency owed and noted that payment-versus-payment mechanisms help mitigate it (BIS settlement-risk analysis).

Payment-versus-payment, or PvP, means final transfer of one currency occurs if and only if final transfer of the other currency occurs. This eliminates principal settlement risk for eligible trades in the PvP arrangement. CLSSettlement is the best-known PvP service for many major currencies and participants. BIS noted in its 2026 analysis of 2025 FX settlement data that CLS provides a PvP service that eliminates FX settlement risk for covered settlement (BIS 2026 settlement study). That does not mean all FX settlement risk has disappeared. Not every currency, counterparty, trade type, value date or operational circumstance is covered.

Banks need settlement-risk controls even when they use PvP where possible. They must identify which trades settle through PvP, which settle bilaterally, which are netted, which are intragroup, which use correspondent accounts and which have timing controls. They must measure exposure by counterparty and value date. They must monitor failed settlements and unmatched confirmations. They must know when a payment has become final. They must also understand cut-off times because settlement risk can increase when one leg is released before the other is secure.

For business analysts, CLS integration requires trade eligibility rules, matching status, settlement method, pay-in schedule, currency funding, exception workflow, fail handling, reconciliation and reporting. Testing should include eligible trade, ineligible currency, unmatched trade, failed pay-in, late instruction, amended SSI, split settlement and fallback process. PvP is a control, but controls need systems and people to operate them.

PvP, netting and clearing solve different problems

The BIS's June 2026 settlement study distinguishes PvP from a CCP. PvP removes principal risk for obligations actually settled through the protected mechanism. It does not remove replacement-cost exposure before settlement, the need to fund pay-ins, or a liquidity shortfall if an expected currency receipt is delayed. Payment netting reduces gross obligations when legally enforceable but does not itself link the final transfers. CLSNet is a netting calculation service; it is distinct from CLSSettlement's PvP service. CLS describes both services.

For an illustrative bilateral trade, Bank A buys EUR 10 million and owes USD 11 million to Bank B. If A's USD payment becomes irrevocable before its EUR receipt is final, it is exposed to the principal owed by B during that interval. A SWIFT confirmation or payment message cannot close that exposure. Operations must establish the earliest cancellation deadline for the sold currency and when the bought currency receipt is known to be final, then measure exposure across that interval, not just a nominal payment timestamp.

For a CLS route, check eligible currencies, product and value date, participant access, instruction matching, settlement window and funding readiness. A bank may participate through a settlement member rather than directly. Net funding obligations and internal gross trade settlement records are different objects; retain the mapping between them. If a trade is late or ineligible, send it to an owned exception. Moving it to bilateral settlement needs approved settlement-risk limits and authenticated SSIs; it must not be an automatic unrecorded fallback.

13. FX Global Code and conduct

The FX Global Code is a set of good-practice principles for wholesale FX. The GFXC page identifies the December 2024 edition. The Code does not create legal or regulatory obligations and supplements applicable local law; its principles are useful for conduct and operational design. It covers areas such as ethics, governance, execution, information sharing, risk management, compliance, confirmation and settlement.

Conduct matters because FX markets depend on trust. Clients need fair execution, transparent pricing, appropriate information handling and clear communication. Banks need controls over mark-ups, last look where applicable, order handling, benchmark execution, confidential information, conflicts of interest and trade surveillance. A dealer who misuses client information can damage the bank. A pricing engine that applies unexplained margins can create complaints. A sales process that does not explain product risk can create conduct issues.

For retail and SME customers, transparency is especially important. The customer should understand the rate, charges, timing and whether the rate is guaranteed. For corporates, the bank should explain hedging product outcomes, including what happens if the underlying exposure changes. For institutional clients, execution policy, platform behaviour, order handling and disclosures matter. Conduct is not soft decoration. It is a core control area.

Business analysts should include conduct fields in requirements: quote source, quote time, accepted rate, customer spread, all-in rate, expiry, user consent, product disclosure, amendment history, cancellation reason, complaint reference and exception approval. In FX, a clean audit trail can protect both the customer and the bank.

14. Rate governance, pricing and margins

FX pricing begins with the market rate. The bank observes bid and offer prices from liquidity providers, interbank markets, electronic platforms or internal pricing engines. The mid-rate is a reference between bid and offer. The bank then applies spread based on product, client segment, trade size, currency pair, volatility, liquidity, channel, risk, operational cost and commercial policy. The final customer rate may be called the all-in rate. The difference between market reference and client rate contributes to revenue but must be governed.

Rate governance is the missing discipline behind many FX complaints. The bank should define rate source, market data hierarchy, quote freshness, spread policy, margin approval, manual override rules, stale-rate handling, market-closed logic, weekend or holiday pricing, quote expiry and audit trail. If the customer asks “how did you get this rate,” the bank should not answer with guesswork. It should retrieve the market reference, spread, quote timestamp, expiry and acceptance evidence.

Pricing is not the same for every flow. A large institutional EUR/USD trade may receive a tight spread. A small retail exotic-currency transfer may have a wider spread because liquidity, processing cost and risk differ. A guaranteed rate held for several minutes carries market risk for the bank. A weekend quote may need wider protection because live wholesale market liquidity is limited. A forward price includes forward points. An option price includes premium and volatility. The pricing engine must know product behaviour.

Testing pricing requires scenarios: normal quote, stale quote, rate expired, market closed, high volatility spread widening, customer tier change, manual dealer override, margin approval, cancellation, refund, payment return and complaint investigation. A good FX system can explain how the final rate was produced. A poor one only stores the final number.

15. FX positions and market risk

An FX position is the bank’s net exposure to currency movement. If the bank buys USD and sells EUR, it is long USD and short EUR from that trade. If another trade offsets it, the net exposure reduces. Banks manage positions by currency, desk, book, legal entity and sometimes product. Open positions create P&L when exchange rates move. Market risk limits control how much exposure can be carried.

FX market risk includes spot risk, forward risk, curve risk, basis risk, volatility risk for options and correlation risk for portfolios. A simple spot position is sensitive to exchange-rate movement. A forward position also reflects interest-rate differentials and basis. An option position is sensitive to spot, volatility, time decay, rates and other Greeks. A cross-currency portfolio can be exposed to several currencies and correlations. Stress testing should include sharp devaluation, appreciation, liquidity gap, pegged-currency break, capital-control event and market closure.

Banks may hedge client flow. If a customer buys USD against EUR, the bank sells USD and buys EUR in that client trade. To offset this exposure, the bank buys USD and sells EUR in the interbank market. Selling more USD would increase the short USD position. A pre-existing inventory position may change how much the desk needs to hedge. Some banks warehouse limited risk within appetite. Others pass through quickly. The business model depends on desk mandate, scale, technology, risk appetite and liquidity. A payment conversion business may prefer near-immediate hedge. A trading desk may manage inventory actively. Treasury swaps may hedge currency funding rather than customer rate risk.

Market risk systems should update positions quickly because FX moves continuously across global trading hours. End-of-day revaluation is not enough for active desks. Limits should consider intraday exposure, stop-loss, stress, option Greeks and currency concentration. Finance should reconcile P&L with risk and trade data. A position mismatch between systems is not a reporting annoyance. It may mean the bank is carrying unknown risk.

16. Credit and counterparty risk in FX

FX creates counterparty risk because the counterparty may fail before or at settlement. For spot trades, risk exists from trade date until settlement and can include settlement exposure. For forwards and swaps, exposure can last longer because market value changes over time. If the contract moves in the bank’s favour, the counterparty owes economic value. If the counterparty defaults, the bank may need to replace the trade at current market rates.

Credit exposure measurement can include current exposure and potential future exposure. Collateral agreements may reduce exposure for professional counterparties. Netting agreements may reduce exposure across trades. Settlement limits control principal risk by value date and currency. Wrong-way risk can appear if a counterparty is vulnerable to the same currency move that makes the FX contract valuable to the bank.

For corporate clients, credit approval may be needed before forwards, swaps or options are allowed. A customer may not pay premium, collateral or settlement amount when due. Pre-settlement risk and settlement risk must be controlled. Product onboarding should define permitted products, tenor, notional limits, collateral requirements and documentation.

For systems, counterparty risk requires legal entity mapping, netting set, agreement type, collateral status, maturity, mark-to-market, exposure calculation, limit utilisation and breach workflow. A trade booked under the wrong counterparty or branch can consume the wrong limit. A missing legal agreement can overstate netting benefits. Data quality is credit risk control.

17. Liquidity risk and treasury FX swaps

FX liquidity risk has several forms. The first is market liquidity: can the bank trade the currency pair in size without unacceptable price impact? The second is funding liquidity: does the bank have the required currency cash on the value date? The third is settlement liquidity: can the bank deliver funds through the correct account and system before cut-off? The fourth is transformation liquidity: can the bank use swaps or other tools to convert surplus currency into needed currency during stress?

A bank may have strong group liquidity but weak liquidity in a specific currency. For example, it may have surplus EUR but need USD. An FX swap can bridge the gap, but only if the market is open, counterparties have limits and the cost is acceptable. During dollar funding stress, FX swap basis can widen, making USD liquidity expensive. A treasury team should therefore run currency-specific liquidity ladders and not rely only on consolidated liquidity.

FX swap maturities need ladder management. A bank that rolls short FX swaps continuously may create rollover risk. If markets become stressed, the swap may be more expensive or unavailable. If the bank funds long-term USD assets through overnight or one-week FX swaps, it has created a currency maturity mismatch. Treasury should report swap maturity concentration, currency, counterparty and stress roll assumptions.

Risk reports should show currency ladder, expected inflows, expected outflows, unsettled FX trades, nostro balances, swap maturities, failed settlements, large client flows, cut-off exposures and stress assumptions. FX liquidity is one of the places where markets and payments truly merge.

18. FX and securities settlement

Securities settlement and FX are tightly connected when an investor buys securities denominated in a currency different from its funding currency. If a European investor buys US securities, USD may be needed by the securities settlement date. The US move to T+1 for covered broker-dealer securities transactions from 28 May 2024 compressed the timeline for arranging FX funding (SEC implementation statement). This is not a universal rule for every debt security: SEC FAQs identify government securities and other exemptions. ESMA’s July 2026 preparation statement identifies 11 October 2027 as the scheduled EU transition, still a future date for learners using this chapter in October 2026. Product scope and infrastructure calendars must be checked separately. See ESMA’s T+1 preparation statement.

Shorter securities settlement cycles affect FX because allocation, confirmation, funding and settlement must happen faster. A fund manager cannot wait too long to book the currency trade. The custodian must know settlement instructions. The FX trade must match value date. If the FX leg is late, the securities trade may fail or the account may go overdraft. If the securities trade fails, the FX trade may still settle, leaving unwanted currency cash. Exception processes must handle both sides.

Time zones make this harder. A trade executed late in one region may need currency funding before another region opens. Holidays create mismatch. Some currencies have local cut-offs earlier than global trading hours. A bank providing custody, securities execution and FX must coordinate product design. It should not promise frictionless T+1 cross-border settlement unless the FX funding workflow supports it.

Testing should include a US securities purchase requiring USD FX from EUR, late allocation, unmatched FX confirmation, failed securities settlement, FX settled but securities failed, securities settled but FX late, account overdraft, holiday mismatch and client cancellation. This is where securities operations and FX operations must work as one process.

19. Trade capture and confirmation

FX trade capture must record the economic and operational terms. For spot and forwards, key fields include trade date, value date, currency pair, bought currency, bought amount, sold currency, sold amount, rate, counterparty, product type, book, trader, channel, settlement instructions, confirmation method and status. For swaps, both legs must be captured with near and far value dates and linked economics. For options, strike, expiry, premium, exercise style and settlement method are essential. For NDFs, fixing source, fixing date, settlement currency and cash-settlement calculation are essential.

Confirmation reduces dispute risk. The confirmation should match counterparty, currency amounts, rate, value date, settlement instructions and product terms. Unmatched confirmations should be investigated quickly because value dates can be near. A trade that is economically agreed but not confirmed can still settle incorrectly. Confirmation platforms, SWIFT messages, electronic matching or bilateral processes may be used depending on counterparty and product.

Standard settlement instructions, or SSIs, are critical. Wrong SSIs can send money to the wrong account or cause failure. SSI changes should have strong controls, including maker-checker approval, counterparty authentication and audit trail. Fraud risk is real because payment instruction changes can be exploited. FX operations should not accept casual email changes without proper validation.

For technology, confirmation status should feed settlement readiness. A high-value trade that is unmatched near cut-off should trigger escalation. A stale SSI should block or warn. A value-date mismatch should not proceed silently. Trade capture is not only front-office convenience. It is the beginning of settlement control.

20. Settlement, reconciliation and breaks

FX settlement moves currency cash. Depending on settlement method, this may occur through CLS, correspondent accounts, central-bank systems, local clearing systems or internal accounts. Settlement status should show whether each deliverable leg is pending, released, settled, failed, repaired or cancelled. For spot, deliverable forwards and each exchange in a swap, systems must track both legs independently and together. NDF cash settlement and option premiums need their own obligation records. A single-leg failure can create exposure.

Reconciliation compares expected settlement cash with actual account entries. Nostro reconciliation is especially important. Breaks may arise from wrong amount, wrong value date, charges, correspondent fees, failed settlement, duplicate payment, return, amendment, sanctions hold, cut-off miss or incorrect reference. A break should have reason, owner, age, amount, currency, counterparty, trade reference and resolution action.

Aged breaks create risk. A small break may hide a larger process issue. A high-value break can affect customer funds, P&L, liquidity and reporting. Operations should classify breaks by risk and age. Treasury should see material breaks that affect cash availability. Finance should see breaks that affect accounting. Compliance should see breaks linked to screening or sanctions. Reconciliation is therefore a bank-wide control, not only an operations task.

For testing, include successful settlement, one-leg failure, late receipt, overpayment, underpayment, wrong account, returned payment, correspondent charge, cancelled trade, amended trade, CLS settlement, non-CLS settlement and month-end open break. A robust FX platform should make breaks visible and actionable.

21. FX accounting and revaluation

FX accounting depends on product, accounting standard, business model and bank policy. Spot trades may create realised gains or losses. Forwards, swaps and options are revalued as market rates move. Foreign-currency monetary assets and liabilities are translated into the entity’s functional currency under the applicable framework. Translation into a different presentation currency is a separate financial-statement process. Hedge accounting may apply where strict documentation and effectiveness requirements are met. This chapter does not replace accounting standards, but learners should understand that FX trades create valuation and reporting consequences beyond settlement.

Daily revaluation marks open FX positions to market. If the bank is long USD and USD strengthens, the position may gain value in reporting currency. If USD weakens, it may lose. Forwards include forward curve effects. Options include volatility and time value. Revaluation feeds P&L, risk, collateral, client statements and management reporting. A mismatch between front-office valuation and finance valuation can create breaks.

Accounting events need clean data: trade date, value date, rate, currency, amount, product, counterparty, book, valuation source, realised/unrealised split, settlement status and hedge designation where relevant. Manual adjustments should be controlled. Month-end revaluation is especially sensitive because financial statements rely on it.

For payments-linked FX, accounting must also connect customer debit, currency conversion, charges, beneficiary payment, return and refund. If a payment returns in foreign currency after the original conversion, the accounting flow can become complex. Product rules should define whether the customer receives original currency, return currency or reconverted amount, and how FX difference is handled.

A balanced translation example

Distinguish transaction currency, functional currency and presentation currency. IAS 21 governs foreign-currency translation under IFRS; derivative recognition and hedge accounting also involve IFRS 9. The accounting policy, not the dealer's label, decides the treatment.

Assume a EUR-functional-currency bank has a USD 110,000 monetary receivable initially equivalent to EUR 100,000 at EUR/USD 1.1000. At reporting date EUR/USD is 1.0000, with no credit loss, interest or other changes. The USD receipt is now worth EUR 110,000. The illustrative translation entry is debit receivable EUR 10,000, credit FX gain EUR 10,000. Receipt then debits USD cash with EUR carrying equivalent 110,000 and credits receivable EUR 110,000. Debits equal credits in the functional-currency ledger; USD and EUR must never be added as if they were the same unit.

This is a receivable translation example, not a complete forward or option journal. A derivative's fair value is the value of its remaining contractual economics under the approved model, not its gross notional. Reconcile trade population, valuations, cash settlements and ledger movements independently. An economically hedged position can still have accounting timing differences without qualifying hedge designation. See the finance course for the accounting framework.

22. Sanctions, AML and compliance touchpoints

FX trades and FX-linked payments must respect sanctions, AML, KYC and regulatory requirements. A pure interbank FX trade may focus on counterparty and market conduct, while a customer payment with FX includes payment screening, beneficiary information, originator information, sanctions lists, purpose codes where relevant and transaction monitoring. Compliance holds can affect FX lifecycle because the currency trade may be booked while the payment is stopped.

This creates design questions. If screening stops a payment after FX is booked, does the bank cancel the FX trade automatically, hold it, hedge it separately, or escalate manually? If a payment is released after the original rate expires, is a new rate used? If a payment is rejected due to compliance, how is the customer refunded? If the refund currency differs from debit currency, who bears exchange movement? These rules must be defined before incidents occur.

AML monitoring may also identify unusual FX patterns: rapid in-and-out conversions, circular flows, high-risk corridors, inconsistent customer profile, structured amounts or sudden activity in high-risk currencies. Transaction monitoring and FX systems should share relevant data where legally and operationally appropriate. A siloed FX engine can miss compliance context.

For BA work, compliance requirements should not be vague. Capture screening points, hold statuses, release authority, cancellation rules, customer notification, audit trail, rate handling, refund handling and reporting. Compliance is not outside FX. It is one of the gates in the FX journey.

23. Customer transparency and disputes

Many FX disputes come from misunderstanding. The customer may not know whether the rate was indicative or firm, whether fees were separate or embedded, whether the rate expired, whether the beneficiary amount was guaranteed, whether correspondent charges apply, whether a return will use the same rate, or why the final amount differs. A good bank reduces disputes through clear product design and language.

Retail customers need simple explanations: you are paying this currency, the beneficiary receives that currency, this rate applies, these charges apply, the rate is valid until this time, settlement may depend on cut-off and intermediary banks. SME and corporate customers may need more detail: value date, payment route, forward contract terms, cancellation cost, hedge relationship, settlement instruction and documentation. Institutional clients need execution quality, confirmations, margining and market conduct transparency.

Dispute handling requires traceability. The bank should retrieve quote time, accepted rate, user consent, channel, payment instruction, screening status, settlement status, correspondent charges, return details and communication history. Without traceability, customer service becomes guesswork. FX customer experience is built on audit trail.

A human explanation can be accurate without being complicated. Instead of saying “market movement caused differential settlement,” say: “The original conversion was booked at one rate, but the payment was returned later. The currency had moved by then, so reconversion produced a different amount according to the product rule.” Clear language protects trust.

24. FX data model essentials

A bank-grade FX data model should capture product type, trade date, value date, currency pair, bought currency, bought amount, sold currency, sold amount, market rate, client rate, spread, quote time, expiry time, counterparty, customer, channel, book, trader, legal entity, settlement method, settlement account, SSI, confirmation status, settlement status, payment linkage, risk status, revaluation price, P&L, accounting status and regulatory reporting fields. For forwards and swaps, maturity and leg linkage are essential. For options, strike, expiry, premium and exercise data are essential. For NDFs, fixing and settlement currency fields are essential.

The data model must distinguish economic trade status from settlement status. A trade may be booked but unconfirmed. Confirmed but unsettled. Settled on one leg but not the other. Cancelled economically but pending operational reversal. Linked to a payment that is on hold. Matured but unreconciled. These statuses affect risk, liquidity, customer service and accounting differently.

Identifiers matter. Trade reference, payment reference, UETR where relevant, customer reference, confirmation reference, settlement reference and reconciliation reference should be traceable. A payment-linked FX conversion should allow the bank to trace from customer instruction to FX quote to trade booking to payment execution to nostro entry to customer statement. Without references, investigations become slow.

For developers, field precision matters. Currency decimals differ. Rounding rules differ. Some currencies have zero decimals. Value dates depend on calendars. Cut-offs depend on currency and channel. Rates require precision. Spreads may be stored in pips, basis points or percentage terms. A small technical assumption can become a financial defect.

Reporting is a separate lifecycle

Before building a reporting feed, determine the reporting legal entity, jurisdiction, product classification, counterparty and applicable regime. Spot, deliverable forward, NDF and option treatment can differ; payment reporting, derivatives reporting and market-transaction reporting are separate obligations. Do not infer a derivatives-reporting requirement merely from an exchange-rate field in a payment. For example, MiFIR Article 26 contains an instrument-scope test, distinct from settlement status.

For each applicable report, link the executed trade to the submitted version, regulatory identifiers where required, validation result, regulator/repository acknowledgement, rejection reason and correction. An accepted upload is not evidence that the reported economics are correct. Reconcile eligible trade counts and notionals to accepted reports, including cancellations, amendments and lifecycle events. A false duplicate rejection after retry should not lead to suppressing the real correction.

25. Architecture for FX platforms

An illustrative FX architecture has customer channels, pricing engine, quote service, order management, trade capture, risk engine, confirmation platform, settlement engine, payment engine, nostro reconciliation, accounting, market data, limits, customer master, SSI database, compliance screening and reporting. The architecture may be integrated or fragmented, but the flow must be controlled.

The channel requests a quote. The pricing engine returns a rate with validity window. The customer accepts. The order becomes a trade. The trade updates risk. The settlement engine prepares currency payment instructions. The payment engine executes where needed. Confirmation is sent or matched. Nostro reconciliation confirms cash. Accounting posts entries. Reporting stores evidence. If any step fails, the exception should be visible.

Low-latency institutional FX platforms have different needs from retail payment conversion platforms, but both need control. Institutional trading emphasises price speed, liquidity provider connectivity, algorithmic execution, order handling, last look policy where applicable, pre-trade limits and post-trade reporting. Retail and SME channels emphasise transparent rate display, customer consent, payment linkage, cut-off logic, cancellation, refund and support. Treasury FX swaps emphasise funding ladder, value dates, counterparty limits and liquidity reporting.

Architecture should support idempotency and event traceability. Duplicate messages, retries, partial failures and delayed responses are common in distributed banking systems. The platform should not book duplicate trades because a channel retried. It should not settle a cancelled conversion. It should not lose linkage between FX trade and payment. Strong architecture accepts that failure happens and designs controlled recovery.

26. Testing scenarios for FX

A strong FX test pack should begin with simple spot conversion. The customer requests a quote, receives a rate, accepts within validity, the trade books, payment executes, settlement completes, nostro reconciles and customer statement shows correct amounts. Then the tester should attack the flow. What if the quote expires before acceptance? What if the market rate changes? What if the customer cancels? What if the payment fails screening? What if the beneficiary bank returns the payment? What if the value date is a holiday? What if the nostro is short? What if the SSI is wrong?

Forward tests should include maturity, early drawdown, extension, cancellation, partial cancellation, customer credit limit breach, revaluation, collateral call where applicable, accounting and payment linkage. Swap tests should include near-leg settlement, far-leg settlement, leg mismatch, rollover, amendment, cancellation and liquidity ladder update. Option tests should include premium payment, expiry, exercise, automatic exercise, expiry worthless, barrier event where applicable and settlement. NDF tests should include fixing source, fixing date, missing fixing, settlement currency, cash-settlement calculation and cancellation.

Operational tests should include unmatched confirmation, late confirmation, manual amendment, settlement fail, one-leg fail, CLS eligible trade, non-CLS trade, cut-off breach, correspondent charge, duplicate booking, repair after rejection, rate dispute and reconciliation break. Risk tests should include limit breach, open position update, P&L revaluation, stress loss and missing market data. Compliance tests should include sanctions hold, release, rejection, refund and audit trail.

The best FX testing does not ask only whether the system calculated a rate. It asks whether the bank can run the full day safely: quote, book, hedge, settle, reconcile, explain and report.

27. Practitioner scenarios

Scenario 1: Payment passes, FX fails

A customer submits a cross-border payment requiring conversion. The payment instruction is valid, but the FX booking fails due to pricing engine outage. The bank must decide whether to hold the payment, use fallback pricing, route to dealer intervention or reject. The customer experience depends on clear product rules. If the payment is sent without proper FX booking, the bank may create an open position or wrong customer debit. If the payment is held too long, the customer may miss a deadline. The control is fallback design with approval and audit trail.

Scenario 2: FX booked, payment held

A customer accepts a USD conversion for a payment, but the payment is held by sanctions screening. The FX trade is now booked while the payment is not released. If market rates move, the bank may have exposure. If the payment is later rejected, the bank must reverse or settle the FX according to product terms. The control is linkage between payment status and FX lifecycle. Compliance should not be bypassed, but treasury and operations must know the cash and risk effect of the hold.

Scenario 3: Securities trade needs urgent FX

A fund buys US securities settling T+1 and needs USD. Allocation arrives late. The FX trade is booked close to cut-off. Confirmation is delayed. If USD does not arrive, the securities trade may fail or the account may overdraft. The control is early FX funding workflow, clear cut-offs, automated allocation and exception escalation. T+1 settlement makes this scenario more common and less forgiving.

Scenario 4: Nostro shortfall

A bank expects USD inflows from several trades but some arrive late. Outgoing USD payments are due. The nostro account approaches overdraft. Treasury must source USD through swap, borrowing, internal transfer or correspondent credit. Operations must manage payment queues. Reconciliation must identify which inflows failed. The lesson is that FX liquidity is not theoretical. It is visible in accounts and cut-offs.

Scenario 5: Forward hedge no longer matches exposure

A corporate hedged a USD payable using a forward. The supplier invoice is cancelled. The corporate asks the bank to cancel the forward. The bank must value the cancellation using current market rates and explain gain or cost. If the customer expected free cancellation, dispute may arise. The control is upfront explanation: a forward is a contract, not a reservation.

Scenario 6: Currency holiday missed

A trade is booked with an invalid value date because one currency has a holiday. Settlement fails or rolls unexpectedly. The customer sees delay. Treasury sees funding mismatch. Operations sees repair workload. The control is accurate holiday calendars and validation at quote and trade capture stage. Calendar quality is not a back-office nicety in FX.

Scenario 7: Wrong direction booked

A dealer intended to buy USD and sell EUR but booked the reverse. The position report now shows wrong exposure. If not caught quickly, the bank may hedge in the wrong direction. The control is clear bought/sold currency display, confirmation matching, trader review and P&L reasonableness checks. FX direction mistakes are simple, expensive and avoidable.

Scenario 8: Client rate dispute

A customer claims the bank used the wrong rate. The bank must retrieve quote timestamp, market source, spread, rate displayed, customer acceptance, expiry and final trade. If audit trail is weak, the complaint becomes hard to resolve. The control is transparent rate capture and customer consent evidence. In FX, explainability is part of customer protection.

Scenario 9: NDF fixing issue

A corporate books an NDF for a restricted currency. On fixing date, the expected rate source is unavailable or delayed. The bank cannot simply invent a rate. It must apply contractual fallback, escalate, evidence the rate used and explain settlement. The lesson is that fixing governance is central to NDF control.

28. Source references

• BIS - Triennial Central Bank Survey 2025 - BIS source for the 2025 global FX and OTC derivatives survey, with final turnover and settlement data releases.

• BIS press release - Global FX trading hits $9.6 trillion per day - BIS 30 September 2025 press release summarising preliminary 2025 survey findings.

• BIS - FX settlement risk: an unsettled issue - BIS article explaining FX settlement risk and the role of netting and PvP.

• BIS - Uncovering FX settlement risk: new measures from the 2025 BIS Triennial Survey - BIS 2026 article discussing FX settlement methods and PvP.

• Global Foreign Exchange Committee - FX Global Code - Official GFXC source for the FX Global Code and global good-practice principles.

• SEC - T+1 settlement cycle implementation - Official SEC statement confirming the US move to T+1 from 28 May 2024.

• ESMA - Shortening the settlement cycle to T+1 in the EU - Official ESMA page on the EU T+1 programme and transition programme. See also the July 2026 preparation statement for the scheduled 11 October 2027 date.

• CLSSettlement and related services - PvP scope and distinction from payment netting.

• BIS - Covered-interest parity and the cross-currency basis - Economic pricing relationship, not a live curve source.

• IAS 21 - Functional currency and translation framework.

• ESMA - T+1 preparations, July 2026 - Scheduled EU transition and readiness programme.

Final takeaways

Foreign exchange is one of the most practical markets in banking because it touches both money and movement. A bank can quote a good rate and still fail the customer if settlement, payment linkage, nostro funding, confirmation or reconciliation breaks. A bank can have strong liquidity in one currency and still be short in another. A bank can book a hedge and still create operational risk if product rules, value dates and payment status are unclear. FX is therefore not only a trader’s topic. It is a treasury, payments, operations, risk, finance, compliance and technology topic.

The learner should leave this chapter with a working instinct. When you see an FX trade, ask what currencies move, when they move, where they move, who confirms them, how they settle, whether PvP applies, which nostro is used, what happens if a payment is held, what happens if one leg fails, how the rate was built, how the customer sees it, how risk is hedged and how reconciliation proves the cash. That is foreign exchange inside a bank.

End of Foreign Exchange enhanced practitioner chapter.