From the journal

Weekend on-chain FX conversion and settlement risk for corporate treasury

Treasury should release an onward USD payment from a weekend conversion only after two conditions are evidenced. Both currency obligations must have reached the final settlement event defined by the governing agreements. The dollars must also be available in the account funding the onward payment, with a confirmed route that can meet its deadline. Once the EUR payment order can no longer be recalled or cancelled, hold onward release against unconfirmed USD proceeds and count the full sold-currency amount within the approved settlement-risk limit.

17 min read

Treasury should release an onward USD payment from a weekend conversion only after two conditions are evidenced. Both currency obligations must have reached the final settlement event defined by the governing agreements. The dollars must also be available in the account funding the onward payment, with a confirmed route that can meet its deadline. Once the EUR payment order can no longer be recalled or cancelled, hold onward release against unconfirmed USD proceeds and count the full sold-currency amount within the approved settlement-risk limit. This proposed control follows the exposure window in the FX Global Code, Principle 50, December 2024, p. 48.

This analysis concerns a corporate treasury selling EUR for USD outside office hours to fund a Monday obligation. In this example, the bilateral spot foreign exchange (FX) contract is governed by English law. Actual bank accounts, platform participation and payment-system legs require their own applicable terms and laws.

The BMW transaction and the published product

J.P. Morgan reported BMW's automated EUR-to-USD transaction on 9 December 2025. Its announcement describes balance checks, conditional auto-deposits, conversion and transfers between Blockchain Deposit Accounts (BDAs) in Frankfurt and New York. BMW's German and US treasury teams set the conditions in advance. The bank reports completion outside traditional settlement windows without manual intervention. The weekend purchase considered here is the treasury decision to be tested against that kind of workflow.

As at 18 November 2026, the bank publishes an offering for eligible institutional clients and reports customer execution. Its 29 June 2026 currency expansion added five Asia-Pacific currencies alongside EUR, GBP and USD. The specific Global Payments API onboarding guide still describes EUR/USD access for New York and Frankfurt BDAs, with client eligibility and signed documentation requirements. Product coverage and access through a particular interface must therefore be checked separately.

The bank's on-chain FX page describes continuous availability and simultaneous currency exchange. The bank's 14 July 2026 explanation describes BDA-to-BDA conversion, with J.P. Morgan providing the rate and executing the trade. Its footnote makes extended same-day settlement subject to booking location, funding location, currency and Account Terms; availability is not guaranteed.

Funding and withdrawal have a separate qualification. The Digital Payments API overview, introductory tips, states that movement between legacy demand deposit accounts and BDAs has a Saturday maintenance window of 3–6 p.m. Eastern Standard Time. It separately describes on-network payments as available continuously. Treasury must obtain the operative time-zone convention, maintenance notices, quote hours and liquidity limits for its EUR/USD accounts before relying on a weekend rule.

The contract determines what completes the exchange

A trade becomes binding when the parties' objectively communicated words or conduct establish an intention to create legal relations and agreement on the essential terms. Under the English-law relationship of this example, the automated acceptance event can therefore create a binding exchange obligation before either currency has been paid. The confirmation should record the accepted rate, two amounts, counterparty, value date and settlement accounts. RTS Flexible Systems Ltd v Molkerei Alois Müller GmbH & Co KG [2010] UKSC 14, paragraph 45, supplies the general formation test.

An ordinary bank balance is a claim against the account bank. The bank's mandate defines its authority to act on payment instructions. Those principles make the identity of each account debtor and the terms authorising automated debits material to the analysis. Philipp v Barclays Bank UK PLC [2023] UKSC 25, paragraphs 26–31.

The signed documents must identify when the EUR obligation and USD obligation are discharged. Read the FX master, confirmation, account agreement and platform rules together, applying their incorporation and priority provisions. An English court determines their objective meaning in the context of the whole contract. Wood v Capita Insurance Services Ltd [2017] UKSC 24, paragraphs 10–13.

If the agreed delivery destination is treasury's USD account at Bank A, a final credit there can complete the FX purchase. A later transfer to Bank B then has its own performance conditions. If the confirmation instead makes final credit at Bank B the dealer's delivery obligation, an intermediate credit at Bank A leaves that obligation outstanding. Counsel should resolve this point before the automated instruction is enabled.

Bank A and Bank B must be mapped to legal entities. J.P. Morgan's API availability guidance identifies New York BDA booking for JPMorgan Chase Bank, N.A. and Frankfurt booking for J.P. Morgan SE clients. A Frankfurt-to-New York movement can therefore involve distinct banks within one group. The actual FX counterparty and governing laws must come from the executed documents. The bank's website terms, Enforceability and Governing Law, apply New York law to website use; the contractual analysis here uses the English-law FX agreement of this example.

The two-currency timeline

Operations should maintain the following event map for each conversion. The records below are proposed evidence requirements. Their legal meaning must be agreed with the bank and linked to one trade identifier. A later confirmation may evidence an earlier binding acceptance; the dealing terms should resolve that sequence.

  • Rule fires. Preserve the mandate, rule version, balance type and trigger time. EUR leg: EUR may remain available or be reserved. USD leg and availability: The rule identifies a USD shortfall. Source of finality and remaining exposure: The instruction mandate supplies authority. A trigger alone records no currency settlement.
  • Funding and executable quote. Preserve linked-account funding records, quote ID, rate, amounts and expiry. EUR leg: Confirm usable EUR in the account that will fund the sale. USD leg and availability: A quoted USD amount is a proposed receipt. Source of finality and remaining exposure: Funding follows the account terms. Quote terms determine commitment; liquidity and price risk remain.
  • Trade accepted. Preserve the binding acceptance record and confirmation, including value date and calendars. EUR leg: Treasury owes the agreed EUR amount. USD leg and availability: The dealer owes the agreed USD amount at the specified destination. Source of finality and remaining exposure: The dealing agreement creates the trade. An accepted, unfunded deal can expose treasury to replacement cost if it fails.
  • EUR payment becomes irrevocable before confirmed final USD receipt. Preserve the payment order and its cancellation deadline. EUR leg: The payment order can no longer be recalled or cancelled. USD leg and availability: Final receipt is pending or unconfirmed. Source of finality and remaining exposure: Under the proposed control, measure the full sold-currency exposure from this point until USD settlement is confirmed final, following Code Principle 50.
  • Paired entries reach their legally final event. Preserve both leg IDs, account statements and the linked settlement record. EUR leg: The EUR obligation is discharged under the agreed rule. USD leg and availability: Final USD credit discharges the purchase obligation if this is the agreed destination. Source of finality and remaining exposure: The FX/account rules must make finality of either leg conditional on finality of the other for payment versus payment (PvP). If final receipt of the second currency is uncertain, the party that has finally paid the first bears principal exposure.
  • Available funds are released. Preserve a current available-balance record and any holds. EUR leg: The sold EUR is no longer treasury's available balance. USD leg and availability: USD is usable within the account's permitted payment functions. Source of finality and remaining exposure: Account terms govern use. Final FX settlement can coexist with an availability restriction and continuing deposit-bank exposure.
  • Withdrawal or redemption is completed where the route requires it. Preserve the instruction and receiving-account credit. EUR leg: No further EUR exchange occurs. USD leg and availability: USD moves to the account needed for payout. Source of finality and remaining exposure: BDA withdrawal follows account terms. Any inserted deposit token needs its own issuer and redemption terms. Outage or redemption delay can leave proceeds unavailable for the next step.
  • Outward transfer is accepted and processed. Preserve payment ID, rail, full status and timestamps. EUR leg: The original EUR leg remains a separate record. USD leg and availability: USD may be debited while the receiving bank is still processing. Source of finality and remaining exposure: Payment-service and rail rules govern this leg. Correspondent, liquidity and processing exposure require separate monitoring.
  • Receiving account is credited and funds become available. Preserve the recipient-bank record and availability evidence. EUR leg: No new EUR settlement occurs. USD leg and availability: The intended recipient can use the dollars. Source of finality and remaining exposure: The receiving account's terms and applicable payment rules govern this event. The original FX destination determines whether it also completes an outstanding FX delivery obligation.

For supported accounts, the bank's BDA Balances resource, Response balance types, distinguishes Interim_booked from Interim_available. Its balance API documentation also requires attention to account time zones and published geographic scope. Retain the account, currency, balance type and as-of time; an old balance can be accurate for its timestamp and unusable for a new release decision.

Payment status also needs its complete meaning. In the bank's Global Payments 2 status table, completion substatuses distinguish internal processing, dispatch to clearing and application to the recipient. The bank should map the relevant method's status to the contractual event treasury needs to prove.

Testing payment versus payment across the route

Payment versus payment requires each currency's final settlement to occur if and only if the other's does. The legal test therefore reaches both directions: EUR cannot settle finally while USD remains conditional, and USD cannot settle finally while EUR remains conditional. The mechanism and rules must maintain that condition during normal processing, failures and timeouts. The Committee on Payments and Market Infrastructures (CPMI) explains that the arrangement needs a clear legal basis and rules defining finality. Its report is an operational and policy reference. The applicable law and incorporated rules supply the legal effect. CPMI, Facilitating increased adoption of payment versus payment, March 2023, sections 1 and 3.2.2, pp. 6 and 14.

  • Two accounts at the same legal bank. Condition to establish: The account and FX terms make the linked final entries discharge both obligations; the settlement records satisfy those terms. Exposure that can remain: Deposit-bank and availability risk survive a completed exchange. CPMI also recognises on-us arrangements supported by certain settlement within preauthorised credit lines; their protection must be established from the actual arrangement.
  • Accounts at different booking banks. Condition to establish: Identify each account debtor, the FX obligor and the enforceable linkage across their rules. Confirm the relevant insolvency treatment. Exposure that can remain: Treasury can lose the paid-away EUR principal if the USD obligation remains unpaid. The reverse exposure can fall on the party that finally provides USD first.
  • Bridge or correspondent route. Condition to establish: Identify where reservations become irrevocable delivery and which rules make both final deliveries conditional. Test failure during release, retry and timeout. Exposure that can remain: A lock can leave liquidity tied up. Sequential final payments expose the first payer until the other currency finally settles.
  • Completed FX followed by another-bank payout. Condition to establish: Confirm whether the FX delivery destination has already received final credit. Test the outward route separately. Exposure that can remain: The residual exposure concerns the deposit, payment chain and timing. It remains FX principal exposure only while the agreed FX receipt is outstanding.

The on-us distinction follows CPMI section 2.1, p. 7. It prevents both an automatic finding of principal exposure and an automatic finding of PvP from the bank's identity alone.

For a bridge, counsel should test the finality rules of every connected system. The Bank of England's Meridian FX APAC Policy Report, 13 November 2026, section 4(c), explains the need to establish irrevocability in each system and the agreed cross-border outcome. That report concerns an experiment and policy analysis. It provides a useful test for a proposed connection; an actual deployment needs its own rules and evidence.

Statutory protection requires the identified system and leg

As at 18 November 2026, the operative UK regime remains the Financial Markets and Insolvency (Settlement Finality) Regulations 1999, SI 1999/2979, as amended. Their protection addresses defined transfer orders and specified insolvency proceedings. Regulations 3–4 address designation; regulation 13 defines the relevant scope; regulation 14 protects specified system settlement and default arrangements against insolvency interference. A treasury customer must identify its legal capacity and the transfer order covered by the system's rules.

The rules must specify entry into the system and the point after which an order cannot be revoked. Schedule paragraph 5 also addresses coordination between interoperable systems. Regulation 20 limits protection for orders entered after an insolvency event, subject to its stated exceptions. Counsel should record the entry, irrevocability and settlement times separately and apply the relevant insolvency-event test.

The Bank of England's designation list, updated 30 October 2026, includes Continuous Linked Settlement (CLS), operated by CLS Bank International. Its published list contains no entry under the Kinexys name. A claim to statutory protection for a Kinexys route should identify the precise designated system, order, participant and applicable rules. Treasury should record that protection only after counsel verifies those elements.

CLS provides a documented comparison. Its Rules dated 21 July 2025 select English law in rule 1.6.1. Rules 4.3.4 and 4.4.3 distinguish entry from irrevocability; rules 5.2.2 and 5.3 address paired postings and their final legal effect. Rule 5.3 states the member relationships covered, including conditions for discharge of the underlying transaction. A corporate customer using a member needs the customer-to-member terms to establish its own delivery rights. The treasury route considered here requires its own settlement arrangements.

The December 2024 FX Global Code provides a separate benchmark. Principle 35 favours settlement methods that eliminate settlement risk where practicable. Principle 50 addresses exposure measurement and limits. The Code itself imposes no legal or regulatory obligations; a contractual commitment can give an incorporated provision contractual effect. Its principles should inform the operating design, while the signed documents define the parties' obligations.

For the separate euro central-bank-money and securities analysis, see legal finality in Pontes and tokenised securities. This EUR/USD analysis concerns two commercial-bank currency legs.

The weekend release rule

The treasury director should approve a route-specific release rule before activating automatic conversion. Operations should release against purchased USD only when the agreed FX finality record, a current available balance and a viable outward route are all present. The dealer's executable quote and funding capacity must be available at the intended time. An agreement to deliver on Monday must be treated according to that value date, even if the rate was booked on Saturday.

  • Both legs are contractually final; USD is available at the payout account; the onward route can meet the deadline. Weekend decision: Release within the approved payment authority and limits. Retain the evidence for all three conditions. Responsible party: Treasury operations, under the director's approved rule.
  • Final USD credit exists at the agreed FX destination, but withdrawal or onward processing is unavailable. Weekend decision: Recognise the completed FX purchase within its documented boundary. Use separately available USD or committed liquidity for the Monday payment. Responsible party: Treasury liquidity team and payment operations.
  • The EUR payment order can no longer be recalled or cancelled; final USD receipt is absent or unconfirmed. Weekend decision: Stop further automatic exposure and hold release against those proceeds. Escalate to the dealer and settlement-risk owner. Responsible party: Operations and the counterparty-risk owner.
  • The debit is a revocable reservation, or the quote/trade is pending. Weekend decision: Establish whether a trade exists and whether either leg has become irrevocable. Avoid duplicate execution while resolving the status. Responsible party: FX dealer and operations.
  • The quote, liquidity, terms or downstream evidence is insufficient. Weekend decision: Use a pre-agreed earlier execution window or an approved alternative funding route. Responsible party: Treasury director with bank service owners.

A route using Fedwire illustrates why the outward test matters. The Federal Reserve's operating schedule, as at 18 November 2026, gives business-day operation from 9 p.m. Eastern Time on the preceding calendar day until 7 p.m. It observes weekends and listed holidays; a normal Monday business day opens on Sunday evening. The 9 October 2025 expansion announcement schedules additional operating days no earlier than 2028. Ordinary customer transfers have a 6:45 p.m. Eastern Time cut-off under that schedule. The sending bank and receiving bank can impose earlier customer cut-offs. Other payout methods require their own schedules.

The proposed default limit for automatic principal exposure is zero. Once the legal and operational conditions are established, the risk owner can approve a positive limit for an expressly accepted sequential route. Before each irreversible EUR payment order, cap additional principal exposure at the lower of the unused counterparty settlement limit and unallocated replacement USD liquidity available before the Monday deadline. Calculate unused limit capacity after existing unsettled trades, and replacement liquidity after existing contingency allocations and other committed funding needs. Permit no additional exposure when either amount is exhausted. Use a consistent reporting currency, include unresolved settlement states and aggregate repeated triggers. The amount must come from treasury's approved credit appetite and funding arrangements. The Code's Principle 50 supplies the exposure discipline; this cap and release design are proposed treasury controls.

Set the fallback execution deadline by working backwards from the external beneficiary-bank deadline through the actual withdrawal, payment and contingency windows. If that timetable cannot tolerate a weekend interruption, execute and position USD during the last confirmed window. A repayment claim after a failed trade cannot finance Monday's payment until it produces usable funds. The related European Economic Area card-programme prefunding analysis addresses the same need to identify available fiat before enabling onward use.

Five clauses to obtain before automatic conversion

1 Parties, authority and document priority

Legal and bank counsel should identify the FX dealer, each account bank, booking branch, account holder and any settlement agent. Specify governing law and forum for each relationship, the documents incorporated and their order of priority. Attach the authority for creating and changing balance rules, approving accounts and initiating debits. Require authenticated instructions and a controlled emergency stop. The agreed powers must cover the actual automated acts before activation.

2 Quote, acceptance, value date and funding

The FX dealing lead should obtain a clause identifying an executable quote, its expiry, acceptance event, amounts, rate, fees and permitted slippage. Define the value date, business-day calendars and time zones, including weekend treatment. State whether the bank must quote, has discretion to decline, or can queue the trade. Record the funding source, any committed credit and applicable liquidity or transaction limits. Require a confirmation and a unique reference linking the two currency obligations.

3 Linked final settlement and permissible corrections

Counsel and the bank's settlement owner should define the event that discharges each currency obligation and the designated receiving accounts. To rely on PvP, make final settlement of either currency conditional on final settlement of the other. Specify the effect of reservations, provisional credits, split processing and interruptions. Limit contractual cancellation or reversal rights to identified circumstances, and distinguish a new corrective payment from reversal of an unsettled entry. Preserve mandatory legal powers. Test the clause against the actual system rules and the relevant insolvency laws.

4 Available proceeds, withdrawal and outward delivery

Treasury operations should obtain a precise definition of available USD and the evidence for it. Identify withdrawal rights, holds, account restrictions, maintenance, quote and service windows, and the withdrawal or redemption process used. Specify the outward payment method, destination, customer cut-offs, bank responsibilities and the point at which the receiving account must be credited. State whether external receipt is part of FX delivery or a separate service. Any guaranteed deadline or liquidity commitment must be express.

5 Failed settlement, insolvency and dispute evidence

Legal and counterparty risk should agree who funds a missing leg, when failure must be reported and when trading stops. Specify recovery, interest or compensation, termination, close-out valuation and any netting rights. Match those provisions to the actual bank entities and mandatory insolvency or resolution rules. Require access to quote, acceptance, paired posting, balance, withdrawal and payout records, with timestamps and status definitions. Set retention, reconciliation and dispute procedures. If a status is uncertain, allocate investigation and retry authority so that a second execution cannot create an unintended additional trade.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.