How to Choose Settlement Currencies

How to Choose Settlement Currencies for an International Payments Business Two merchants each generate €10 million from European customers. The first merchant employs people in Europe, pays European suppliers, issues refunds in euros, and has recurring tax and operating obligations denominated in EUR. The second merchant sells to the same customers but operates almost entirely from the United States. Its payroll, cloud infrastructure, debt service, and most supplier contracts are denominated in USD. Their sales mix is identical. Their settlement-currency strategy probably should not be. For the first merchant, converting every euro into dollars would mean selling a currency the business expects to need again. It could then have to buy euros later to fund refunds, suppliers, payroll, or other obligations. For the second merchant, retaining a large EUR balance could accomplish very little. If nearly every foreseeable use of the cash is in dollars, holding euros creates another balance to reconcile, monitor, and eventually convert. That leads to the central principle of settlement-currency strategy: The best settlement currency is not necessarily the currency with the most revenue. It is the currency the business has a reason to use after settlement. For many international merchants, the right strategy is therefore neither “convert everything to the home currency” nor “retain every currency customers use.” It is to give each settlement currency a job.

Revenue currency is only the starting point A customer paying €100 does not, by itself, answer what treasury should do with the €100. Several different currency concepts can sit between the sale and the merchant's eventual use of the cash. Transaction or presentment currency is the currency in which the customer is charged. Settlement currency is the currency in which the payment provider or acquiring arrangement makes settled funds available to the merchant under the applicable setup. Payout currency is the currency ultimately transferred to a merchant bank account. Depending on the provider and operating model, settlement and payout currency may or may not be identical. Functional currency is an accounting concept rather than simply a payments configuration. Under IAS 21, functional currency reflects the primary economic environment in which an entity operates. The standard looks at factors including the currencies influencing sales prices and operating costs, financing, and the currency in which operating receipts are normally retained. (IFRS) These concepts may point toward the same currency. They do not have to. A European subsidiary may have EUR as its functional currency while accepting customers in EUR, GBP, USD, SEK, and PLN. A global merchant with USD as its functional currency may still have good operational reasons to retain EUR or GBP. That is why functional currency should inform settlement strategy without automatically determining it. The more useful question is:

What will happen to this currency after the payment provider makes it available?

Give every retained currency a job A settlement currency has a strong case for retention when the merchant can connect incoming funds to foreseeable outgoing obligations. There are several recurring uses. Refunds and chargebacks A merchant may sell in a currency today and need funds in that currency tomorrow when customers request refunds or when other payment adjustments occur. Suppose a retailer converts every incoming pound into dollars but routinely needs GBP to finance refunds. Depending on how the provider funds those refunds, treasury may be creating a round trip: GBP revenue → USD conversion → GBP purchased later for obligations If the merchant instead keeps an appropriately sized GBP operating balance, some of that unnecessary conversion can potentially be avoided. That does not mean retaining all GBP indefinitely. It means forecasting the amount that has an operational purpose. Suppliers Supplier currency can be more important than customer currency. A travel business may receive revenue in many currencies while paying hotels, airlines, property operators, or other suppliers in only a smaller subset. If €5 million of EUR receipts will soon finance €4 million of EUR-denominated obligations, converting all €5 million to another currency and subsequently buying euros again would create additional FX activity without changing the underlying economics of the business.

The merchant has what treasury teams commonly describe as a natural hedge: cash inflows and operating outflows in the same currency offset part of one another. That is different from a financial hedge, in which the company uses instruments such as forwards, options, or other contracts to manage currency exposure. Those strategies require separate treasury, accounting, risk, and potentially regulatory analysis. Payroll and operating expenses Payroll, rent, logistics, advertising, contractors, customer support, infrastructure, and other operating costs can create recurring local-currency requirements. Predictability matters. A stable €1 million monthly payroll requirement creates a clearer reason to retain euros than an uncertain possibility that the company may incur some euro expenses at some point. The goal is not to accumulate foreign currency simply because the company can. It is to establish an operating balance connected to expected cash uses. Taxes and government obligations Tax payments and other statutory obligations may also create local-currency needs. The exact requirements, permissible payment routes, entity responsibilities, and bank-account arrangements are jurisdiction-specific and should be confirmed with qualified tax, legal, banking, and finance advisers. Settlement strategy should not assume that a tax obligation exists merely because customers are located in a particular country. Debt and recurring contractual obligations Financing can change the answer again.

A company earning primarily EUR but servicing material USD-denominated debt may have a fundamentally different currency requirement from another company with identical sales but EUR financing. The same applies to recurring software, licensing, content, manufacturing, or inventory contracts. Cash use—not sales volume alone—determines the value of retaining a currency.

Count FX conversion events, not just exchange rates Merchants commonly evaluate FX by asking: “What rate are we getting?” That matters, but the number and location of conversions matter too. Consider two structures. Structure A EUR customer revenue → EUR settlement → EUR payroll and supplier payments Structure B EUR customer revenue → automatic EUR-to-USD conversion → USD treasury balance → USD-to-EUR conversion → EUR payroll and supplier payments Structure B creates an additional economic question even before comparing individual rates: why did the merchant convert away from a currency it already knew it would need? This is where a settlement-currency strategy can reduce unnecessary FX activity. But “fewer conversions” should not become another absolute rule. Maintaining another currency may introduce account costs, balance-management requirements, liquidity constraints, provider fees, or additional reconciliation work that exceeds the conversion cost being avoided. Treasury should therefore measure the full economics. Measure effective FX cost A useful starting measure is: Effective FX cost = (reference-rate value − actual value obtained after conversion and relevant conversion costs) ÷ reference-rate value × 100 The reference rate needs a documented source and timestamp. It should not be mistaken for an executable market price. The European Central Bank, for example, explicitly publishes its euro reference rates for information purposes rather than as transaction rates. (European Central Bank)

The analysis should separately identify, where applicable: * FX spread * explicit conversion fee * provider fee * bank conversion charge * payout fee * intermediary-bank charge Otherwise, treasury may believe it has negotiated a low “FX fee” while still paying materially more through another part of the conversion or funds-transfer process.

FX cost and currency risk are different problems A currency can be inexpensive to retain and still create risk. Conversely, converting immediately can reduce one exposure while creating another. Suppose a US-headquartered retailer receives GBP today but will owe a British logistics provider GBP 30 days from now. Keeping enough GBP to cover that obligation reduces the need to purchase GBP later. The business is matching an asset with a liability or expected cash outflow. Keeping significantly more GBP than operational forecasts justify because management expects sterling to rise is a different decision. The first is operating liquidity management. The second begins to resemble a currency position. Settlement strategy should focus on the first. The distinction also explains why currency holding is not automatically currency speculation. A merchant needs working balances. Refunds occur. Suppliers need to be paid. Payroll dates do not always align with settlement dates. The right question is whether each balance can be traced to a documented liquidity, refund, operating, or treasury requirement. Natural hedge versus financial hedge The same discipline applies to hedging terminology. A natural hedge can arise because commercial inflows and outflows occur in the same currency. A financial hedge involves a separate financial instrument or contract.

Settlement-currency selection can improve the first. It should not be presented as a replacement for a properly governed corporate hedging program where one is required.

Convertibility can override the economic answer Imagine a currency scores extremely well on operating usefulness. The merchant has revenue in it. It has suppliers in it. It has local expenses in it. That still does not mean treasury should treat the currency exactly like EUR or USD. The merchant also has to determine whether the funds can be held, converted, transferred, and ultimately used for the intended purpose under the applicable banking and regulatory framework. This is more precise than asking whether a currency is simply “convertible.” IAS 21's updated exchangeability guidance illustrates why purpose matters: exchangeability is assessed at a particular date and for a specified purpose, and different availability or exchange arrangements can apply to different uses. (IFRS) For payments operations, the broader legal and treasury analysis may include questions such as whether: * the merchant can maintain the required balance or account; * the intended currency conversion is permitted; * documentation is required; * transfers require a specified underlying purpose; * foreign-currency access is limited; * the receiving account is eligible; * cross-border movement is restricted; * limits differ between current-account and capital-account activity.

The IMF's AREAER is designed to track exchange arrangements, restrictions on international payments, capital controls, and related measures across member countries, underscoring why this is a jurisdiction-specific question rather than a simple currency attribute. (IMF) A treasury model should therefore contain a fourth classification in addition to “keep” and “convert”: Restricted or specialist handling. That designation does not necessarily mean the currency cannot be exchanged. It means the merchant should not automate its treasury treatment until the applicable rules and operating route have been verified.

Currency support is not the same as currency usefulness A PSP may technically support transactions in a currency. That alone does not tell a merchant whether retaining that currency is useful—or even whether the same provider configuration supports settlement, balance retention, and payout in it. Before incorporating a currency into treasury policy, map four distinct questions: Can customers pay in it? → Can the merchant settle in it? → Can it be paid out without another conversion? → Can the merchant's approved bank account receive and use it? One “yes” does not establish the next. This is particularly important when providers use terms such as multi-currency, local settlement, or supported currencies. The merchant needs the exact functionality behind the label. A settlement currency without a usable destination is not much of a treasury strategy.

Every additional currency has an operational carrying cost There is a hidden assumption behind “settle in every currency”: that adding another currency is free once the payment system supports it. It is not. Each additional retained currency can add another combination of: * provider balance * bank account or sub-account * general-ledger treatment * balance forecast * refund reserve * conversion rule * reconciliation workflow * approval process * cash concentration decision * regulatory check * reporting requirement The marginal workload may be tiny for a sophisticated treasury operation with automated systems. It may be substantial for a finance team currently reconciling settlements manually. That makes operational complexity an economic variable, not merely an inconvenience. A currency producing modest revenue, few refunds, no local obligations, and significant reconciliation work has a weak case for retention. A currency producing moderate revenue but covering payroll, refunds, and suppliers every month may have a strong one.

The Settlement Currency Decision Matrix A merchant can turn these principles into a repeatable governance process. Score each prospective settlement currency across 13 factors from 0 to 2. This is a decision aid, not a universal financial formula; treasury should adjust weights to the business model. Factor 0 1 2 Revenue volume Immateral Meaningful Material enough to justify dedicated handling Refund requirements Minimal Periodic High/predictable Supplier expenses None Some Material recurring obligations Payroll None Limited Material recurring payroll Taxes None identified Periodic Material recurring requirement Debt None Limited Material debt service Other recurring obligations Minimal Moderate Material FX cost avoided by retention Little Moderate Material/repeated conversions potentially avoided Volatility Low concern for policy horizon Moderate Material Convertibility / regulatory friction No material constraint identified Requires additional process Material restriction or specialist review Liquidity / practical FX access Strong Moderate Limited/uncertain Banking access Straightforward Conditional Material obstacle Operational complexity Marginal Manageable High The first eight factors primarily test purpose. The final five test risk and friction. Revenue volume belongs in the matrix because scale can justify the infrastructure required to maintain a currency. It should not receive veto power over the rest of the matrix. Classification 1: Retain

Retain a currency when it has substantial, predictable future uses and the merchant can hold and use it without disproportionate banking, regulatory, liquidity, or operational friction. Treasury should still define a target balance rather than allowing funds to accumulate indefinitely. Classification 2: Periodically convert Use periodic conversion when the merchant has real obligations in the currency but revenue routinely exceeds those obligations. For example: monthly EUR receipts: €5m forecast EUR requirements: €3m Treasury might retain the amount required for its approved operating buffer and periodically convert the surplus, rather than choosing between 100% retention and 100% conversion. Classification 3: Immediately convert Immediate or systematic conversion becomes more compelling when a currency has little predictable future use, the business ultimately needs another currency, and conversion is economically and operationally straightforward. This is the likely default for the long tail of currencies that generate revenue but no meaningful matching obligations. Classification 4: Restricted or specialist handling This category overrides the normal scoring model when currency controls, banking restrictions, permitted-purpose rules, liquidity constraints, sanctions considerations, or other regulatory issues materially affect what the merchant can do with the funds. Do not apply an automated sweep rule until the actual route has been verified.

Five merchants, five different answers These examples are hypothetical. They illustrate the framework rather than country- or provider-specific recommendations. 1. European SaaS merchant A SaaS company generates substantial EUR revenue. It also has: * EUR payroll * European contractors * office costs * VAT or other tax obligations where applicable * EUR refunds Its functional currency may or may not be EUR depending on the relevant accounting facts; under IAS 21, functional currency considers the entity's broader primary economic environment rather than simply its customer mix. (IFRS) Likely settlement posture: retain sufficient EUR for forecast EUR uses plus an approved liquidity buffer, then periodically convert surplus. The reason is not that European customers paid in euros. It is that the company knows where many of those euros are going next.

2. Travel marketplace Consider a marketplace collecting EUR, GBP, and USD from travelers while having material supplier or seller obligations in EUR and GBP. Subject to the marketplace's actual regulated payments and payout structure, keeping appropriate EUR and GBP balances may reduce repeated conversion when those same currencies are needed for refunds or eligible beneficiary obligations. Likely settlement posture: retain currencies that correspond to predictable payout and refund needs; convert structural surpluses. But buyer collection and seller payout are separate payment flows. The ability to calculate what a seller is owed does not by itself establish that the platform may legally hold, transfer, or convert seller funds. Marketplace regulatory, safeguarding, AML/KYC, licensing, and payout questions require separate analysis.

3. Asian digital-goods merchant Imagine a Singapore-based digital-goods company selling heavily in Japan and South Korea. Customers pay in JPY and KRW. The company's payroll is primarily SGD, while cloud infrastructure and licensing contracts are primarily USD. JPY and KRW may be important sales currencies without becoming major treasury currencies. If there are no meaningful JPY or KRW operating obligations beyond refunds, treasury might maintain appropriately sized refund balances where its provider arrangement supports them and convert the remaining proceeds into currencies with actual uses. Likely posture: SGD and USD may justify retention; JPY and KRW may fall into periodic or systematic conversion depending on refund requirements, costs, provider configuration, and banking access. The example illustrates why payment localization and treasury localization are different decisions.

4. Global retailer A retailer earns EUR, GBP, CAD, AUD, and USD. It pays local payroll, logistics, rent, refunds, and taxes in several markets, while a large percentage of inventory procurement is denominated in USD. “All USD” ignores the value of local operating balances. “Keep everything” ignores the cost of idle cash and operational complexity. A stronger policy might establish a currency-specific operating buffer: forecast refunds + operating expenses + known obligations + liquidity reserve Amounts above that threshold can then be considered for periodic concentration. Likely posture: retain several core operating currencies; periodically sweep excess balances; convert long-tail currencies that have no recurring purpose.

5. Merchant operating in a more tightly controlled FX environment China illustrates why a currency can require a separate governance category rather than a simplistic “convertible/not convertible” label. China's State Administration of Foreign Exchange updated its current catalog of major FX regulations on August 5, 2026; the catalog covers 168 regulations in force as of June 30, 2026 across areas including current-account and capital-account FX administration, financial-institution FX business, exchange markets, and related controls. (Safe) Suppose a merchant has CNY revenue and meaningful CNY payroll, supplier, and tax obligations. Those local uses may make retaining some CNY economically rational. That does not answer how surplus funds can subsequently be converted or moved to a USD treasury location. The merchant must verify the current rules applicable to its particular entity, transaction purpose, documentation, bank, payment structure, and transfer route. Likely posture: treat CNY used for legitimate local operating obligations separately from surplus funds that may need cross-border movement; classify the latter as specialist handling until the current route is confirmed. This is exactly why “foreign-exchange controls” should not be reduced to a currency-risk score.

How to know whether the strategy is working A settlement-currency strategy should create measurable improvements rather than more balances. The following dashboard is more useful than simply counting how many currencies the company can settle. Metric Suggested definition What it reveals Revenue/expense matching ratio Same-currency payment revenue used for eligible same-currency obligations ÷ payment revenue settled in that currency Whether retained currencies are actually being used Effective FX cost Difference between documented reference-rate value and actual converted value after relevant conversion costs ÷ reference-rate value Real conversion economics Average holding period Weighted average time between funds becoming available and their conversion or operational use Whether balances are purposeful or simply accumulating Currency balance Available balance by currency, provider, and bank, separated from reserves/restricted funds Liquidity and concentration Conversion frequency FX conversions per currency per reporting period Whether treasury is repeatedly converting back and forth Idle balance Funds above the approved operating/liquidity requirement for longer than the policy threshold Unproductive currency accumulation Refund-funding coverage Immediately usable same-currency funds ÷ forecast refunds for the policy period Whether settlement strategy supports refunds Reconciliation workload Manual settlement exceptions or staff hours by currency Operational cost of multi-currency complexity

The revenue/expense matching ratio deserves particular attention. A currency producing $50 million equivalent in annual sales but almost no same-currency obligations can be less useful to treasury than one producing $10 million with $8 million of matching expenses. Sales volume measures importance at checkout. The matching ratio measures usefulness after checkout.

Test the strategy before redesigning treasury around it Merchants do not have to turn the entire currency architecture upside down at once. A finance team can model the previous 60 or 90 days of transaction and expense data under two scenarios: Current strategy: existing automatic conversions and balances. Proposed strategy: retain selected currencies to forecast obligations and convert excess using defined thresholds. Then compare: * number of conversion events; * effective FX cost; * balances required; * refund funding; * average holding period; * idle cash; * reconciliation exceptions; * treasury workload. A limited live pilot can follow where provider and banking arrangements permit. The thesis behind multi-currency retention should also be falsifiable. If keeping an additional currency does not reduce unnecessary conversion or improve operational matching—and instead creates persistent idle cash, additional reconciliation work, or unusable balances—then that currency probably has not earned a place in the settlement portfolio.

A practical settlement-currency policy A merchant does not need a sophisticated formula for every transaction. It needs explicit rules. For each currency, treasury should be able to answer: 1. Why are we keeping it? Refunds? Suppliers? Payroll? Taxes? Debt? Another documented obligation? 2. How much do we need? Define a forecast horizon and liquidity buffer. 3. Where can it be held? Provider balance? Bank account? Which legal entity controls it? 4. What happens to excess funds? Threshold conversion? Weekly sweep? Monthly concentration? 5. What would force a different treatment? FX-control changes? Bank restrictions? provider changes? worsening liquidity? material volatility? reconciliation cost? If there is no good answer to the first question, the default should generally move toward conversion rather than indefinite retention—assuming conversion and transfer are legally available, operationally supported, and economically sensible.

The final rule: every retained currency needs a job There is no universal best settlement currency. There is a better question: What does the business need this money to do next? If EUR revenue will fund EUR payroll, refunds, taxes, and suppliers, there is a strong operational case for keeping an appropriate amount of EUR. If EUR revenue will ultimately fund almost entirely USD obligations, there may be little reason to accumulate euros beyond short-term requirements. If a currency cannot be freely used, transferred, or converted for the intended purpose, the decision moves out of ordinary treasury optimization and into specialist regulatory, banking, and financial review. The resulting strategy is usually selective: Retain currencies with predictable jobs. Periodically convert currencies whose inflows exceed those jobs. Convert currencies with no meaningful future use. Escalate currencies whose movement or convertibility is constrained. That is the distinction between supporting many settlement currencies and having an actual settlement-currency strategy. This article provides general information and does not constitute legal, regulatory, tax, accounting, investment, or treasury advice. Merchants should confirm applicable obligations and financial arrangements with qualified advisers, banking partners, payment providers, and relevant authorities.

Treasury decision FAQ Should settlement currency always match the currency the customer pays in? No. Customer currency indicates the denomination of the payment. Settlement strategy should also consider future refunds, suppliers, payroll, taxes, debt, operating expenses, FX economics, convertibility, banking access, and treasury requirements. Should we always settle in our functional currency? No. Functional currency and settlement currency answer different questions. IAS 21 determines functional currency based on the entity's primary economic environment; a merchant can still have legitimate reasons to retain operating balances in other currencies. (IFRS) How many settlement currencies should an international merchant maintain? There is no useful universal number. Maintain currencies whose expected financial or operating value justifies their additional banking, balance-management, and reconciliation requirements. When does immediate conversion make sense? It becomes more compelling when the merchant has little foreseeable use for the currency, can convert it efficiently and lawfully, and would otherwise create an idle foreign-currency balance. Is retaining foreign currency a hedge? Matching predictable same-currency revenue with same-currency expenses can create a natural operational hedge. That is different from taking a speculative currency position or implementing a derivatives-based financial hedging program. How should refunds affect settlement-currency selection?

Model them as a forecast liability or funding requirement. If refunds repeatedly require treasury to repurchase a currency it automatically converted earlier, the current settlement policy deserves review. What if the PSP supports a currency but our bank does not? Treat settlement support and bank-account usability as separate requirements. Confirm settlement currency, payout currency, beneficiary account denomination, location, eligibility, fees, and conversion behavior before retaining the currency. What changes in a market with FX controls? The normal cost-and-matching framework becomes secondary to the actual legal and banking route. Verify the permitted purpose, documentation, conversion route, transfer rules, account structure, payment-provider arrangement, and current regulation before implementing an automated treasury policy. The IMF's AREAER is useful for identifying areas requiring investigation, but country-specific decisions should be checked against current national authorities and banking partners. (IMF)

Original practical asset: Settlement Currency Decision Matrix

Horizontal axis: Future Currency Use → Low to High Vertical axis: Currency / Operational Constraint → Low to High

Low future use High future use Low constraints 3 — Convert \nNo clear reason to retain 1 — Retain \nMatch revenue with future obligations Moderate constraints / excess balances 3 — Convert or consolidate 2 — Periodically Convert \nKeep operating buffer; sweep excess High regulatory / banking constraints 4 — Specialist Handling 4 — Specialist Handling \nOperational usefulness does not override restrictions Visual callouts Around the chart, use six “future use” signals: Refunds · Suppliers · Payroll · Taxes · Debt · Operating Costs. On the constraint side: FX Cost · Volatility · Convertibility · Liquidity · Banking Access · Operational Complexity. Suggested headline: DON'T SETTLE BY SALES VOLUME. SETTLE BY WHAT THE MONEY NEEDS TO DO NEXT. Image alt text: “Settlement Currency Decision Matrix showing when international merchants should retain, periodically convert, immediately convert, or use specialist handling for payment settlement currencies.”

Treasury measurement plan The most revealing dashboard pairing is: Primary KPI — Revenue/expense matching ratio How much settled revenue actually finds a same-currency operational use? Economic KPI — Effective FX cost What does each necessary conversion really cost versus a consistently timestamped reference value? Liquidity guardrail — Idle foreign-currency balance How much cash is being held without an approved near-term purpose? Operational guardrail — Reconciliation workload How much incremental work does each additional currency create? A treasury review should segment these by currency + merchant entity + PSP/acquirer + settlement account + payout bank account, rather than relying on one blended global number.

I’ve treated the uploaded brief as the controlling editorial document: this piece owns the settlement-currency decision, is organized around what happens after settlement, and challenges the idea that every customer currency deserves to become a treasury currency. Editorial interpretation Element Decision Merchant decision owned Which currencies should the merchant retain, periodically convert, immediately convert, or treat as specialist/restricted Unique evidence anchor The currency producing the most sales is not necessarily the currency treasury should keep Editorial position Retain currencies that have a predictable future use. Convert currencies that do not, subject to FX economics, banking access, and regulatory constraints Assumption challenged “Settle in every currency customers use” Most important distinction Revenue currency tells you where money came from. Settlement strategy should reflect where the money needs to go next. Format Treasury decision framework Structural rationale Work backward from refunds, payroll, suppliers, tax, debt, and treasury needs rather than forward from customer currencies Primary metric Revenue/expense matching ratio, supported by effective FX cost Original asset The Settlement Currency Decision Matrix Scope boundary Currency selection, not a full explanation of multi-currency settlement mechanics, cross-border settlement mechanics, repatriation law, or ongoing balance management Proposed architecture 1. €10 million in sales, two different treasury answers

2. Revenue currency is only the starting point 3. Give every retained currency a job 4. Count FX conversion events, not just exchange rates 5. Separate FX cost from currency risk 6. Treat convertibility and banking access as constraints 7. Account for the operational cost of each additional currency 8. The Settlement Currency Decision Matrix 9. Five merchant scenarios 10. Measure whether the strategy is actually working 11. Final recommendation 12. Treasury decision FAQ

SEO metadata SEO title: How to Choose Settlement Currencies for Global Payments H1: How to Choose Settlement Currencies for an International Payments Business Meta description: Choose settlement currencies based on refunds, suppliers, payroll, FX cost, liquidity, volatility, convertibility, banking access, and treasury needs. URL slug: /how-to-choose-settlement-currencies Article excerpt: The currency generating the most sales is not necessarily the currency a merchant should keep. This framework shows how to choose settlement currencies based on what happens to the money next—from refunds and payroll to suppliers, FX, liquidity, and treasury concentration. Primary keyword: how to choose settlement currencies Secondary keywords: best settlement currency; payment settlement currency strategy; multi currency treasury payments; choose payout currency; foreign currency settlement; international merchant currency strategy; settle payments in local currency; PSP settlement currency Related entities/concepts: settlement currency, payout currency, functional currency, treasury management, foreign exchange, natural hedge, FX spread, currency conversion, convertibility, liquidity, foreign-exchange controls, reconciliation Structured data recommendation: Article plus FAQPage markup if the FAQ is published visibly on-page and remains compliant with current search-engine structured-data requirements.

Internal-linking plan The four strongest contextual links are: Anchor/context Destination Placement how multi-currency settlement works Multi-Currency Settlement Explained First distinction between transaction, settlement, and payout currencies managing foreign-currency balances Managing Foreign-Currency Balances Operational carrying-cost / balance-policy section foreign-exchange controls by country Foreign-Exchange Controls by Country Convertibility section repatriating revenue from foreign markets Repatriating Revenue From Foreign Markets Restricted-currency scenario / cross-border surplus discussion This keeps the article from cannibalizing those topics: the reader receives enough context to make the currency-selection decision, then moves to the specialist article for mechanics or implementation.

Authoritative source recommendations For publication, I would build the evidence layer primarily around four non-competitive sources. IFRS Foundation — IAS 21: Use for the formal distinction around functional currency and for the updated exchangeability concept. IAS 21 ties functional currency to the primary economic environment and explicitly considers sales, costs, financing, and retained operating receipts. (IFRS) European Central Bank: Use to explain why an independent reference rate must be timestamped and should not be conflated with a merchant's transactable FX price; ECB states its reference rates are published for information purposes. (European Central Bank) International Monetary Fund — AREAER: Use as the global reference layer for identifying exchange restrictions, international-payment restrictions, capital controls, and related country-level issues requiring investigation. (IMF) State Administration of Foreign Exchange, China: Use only for the China specialist-handling example. SAFE updated its major-regulations catalog on August 5, 2026, covering rules in force through June 30, 2026. (Safe)

Before publishing product-specific copy, verify internally:

2. Settlement currencies available by merchant entity, market, MID/acquiring route, and payment method. 3. Which currencies may actually be maintained without automatic conversion. 4. Payout currencies currently supported. 5. Required bank-account denomination and eligible beneficiary jurisdictions. 6. Whether a merchant can direct different currencies to different accounts. 7. Where automatic FX occurs and whether merchants can control its timing. 8. Current FX pricing methodology, spreads, and explicit conversion charges. 9. How refunds and chargebacks are funded when the original currency is no longer held. 10. Whether minimum balances or payout thresholds vary by currency. 11. Reconciliation data supplied for multi-currency settlements. 12. Which currencies or countries require specialist settlement arrangements. Once confirmed, the article can add a modest CTA such as:

The last sentence should only be published after internal product/legal approval.

Publication fact-check sheet Area Verify before publication Financial Functional-currency treatment with finance/accounting reviewer; natural-hedge terminology; effective-FX-cost methodology; whether all cost components can be obtained consistently Banking Account denomination requirements; beneficiary-entity requirements; multi-currency account eligibility; inbound-transfer restrictions; intermediary fees Currency Settlement versus payout support; actual convertibility for intended purpose; liquidity; FX source; conversion timing Country Any jurisdiction explicitly described as controlled/restricted; current central-bank rules; documentation and transfer purpose; applicability to merchant's entity and flow Regulatory/legal Marketplace seller-fund handling; cross-border transfer permissions; sanctions; payment-services requirements Tax Do not infer tax payment, withholding, repatriation, or entity obligations from payment activity alone Treasury Operating-buffer methodology; concentration rules; excess-balance thresholds; separation of natural hedging from derivatives strategy Amber-flag claims The following require particular care in final editorial review: * “Currency X is restricted.” * “Currency X is freely convertible.” * “Holding local currency reduces FX costs.” * “Automatic conversion is cheaper.” * “Settlement in local currency avoids FX.” * “The merchant needs a local bank account.” * “The merchant can repatriate the balance.” * “The PSP supports settlement in Currency X.”

* Any exact FX spread, transfer time, or fee. * Any marketplace statement implying the platform may hold or move seller funds. For these claims, the applicable jurisdiction, merchant entity, provider configuration, transaction purpose, account, currency, and effective date should be identifiable.

Proposed human accountability

Primary reviewer: Named treasury lead. Secondary reviewers: Finance analyst and payment-operations specialist. Conditional reviewer: Regional legal/compliance or tax specialist for any country-specific example retained in the published copy. Last reviewed: Add the actual final-review date rather than treating the article's drafting date as equivalent to expert review.

Cluster sameness-audit fields Field Article 5 / this draft Title How to Choose Settlement Currencies for an International Payments Business First-two-sentence device Two merchants each generate €10m in European sales but have different expense structures Opening device Matched-revenue counterexample Primary format Treasury decision framework Evidence anchor Future cash use beats revenue volume as the selection principle Editorial position Keep currencies with predictable jobs; convert those without them Merchant decision Retain vs periodically convert vs immediately convert vs specialist treatment Main country example China, narrowly used to illustrate specialist FX-control review Original framework Settlement Currency Decision Matrix Primary metric Revenue/expense matching ratio Secondary metric Effective FX cost Conclusion Every retained currency should have a job CTA Map actual settlement → FX → payout → bank-account behavior before implementation FAQ type Treasury decision FAQ I would not claim the full ten-article sameness audit is complete yet: the materials retrieved here give me the cluster briefs and ownership rules, but not a clean set of all ten final publication drafts side-by-side. For this article, however, the differentiation is strong: it does not explain how multi-currency settlement works; it answers which currencies are worth retaining once that capability exists.