Managing Foreign-Currency Balances

Managing Foreign-Currency Balances

Managing Foreign-Currency Balances: A Practical Framework for International Merchants Imagine opening the treasury dashboard on Monday morning and seeing balances in twelve currencies. EUR has been building for months. GBP rises and falls with refund activity. A small balance in NOK has barely moved. Another local currency accumulated because the payment provider stopped automatically converting it. And somewhere in the organization, somebody asks the most useful question in multi-currency treasury: Why is each balance there? For some currencies, there is a good answer. EUR revenue may fund EUR suppliers. GBP may be needed for customer refunds. A regional operation may need local currency for payroll or taxes. For others, there is no answer. The money accumulated because nobody established a conversion rule. That distinction matters. A merchant should not retain a foreign currency merely because its bank or payment provider makes it possible. The better question is whether retaining that currency serves a measurable operating purpose. This leads to a simple treasury principle: Every foreign-currency balance needs a job. That job may be funding expenses, supporting refunds, matching suppliers, preserving short-term liquidity, or complying with a market-specific funds-management requirement. If a currency does not have such a job, holding it is usually not an FX strategy. It is an unmanaged currency position.

The objective of business FX risk management is generally to control financial exposure rather than generate trading profits. U.S. International Trade Administration guidance makes the same distinction and identifies matching foreign-currency receipts with foreign-currency expenditures as a natural hedge. (Trade.gov) 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.

First, understand where the balance sits A merchant receiving foreign-currency revenue might see something resembling: Customer pays EUR → payment is authorized and captured → clearing and settlement occur → merchant becomes entitled to a settlement amount → EUR appears in a provider balance or merchant account → merchant retains EUR, spends EUR, or converts EUR → funds may later move into a bank or centralized treasury account The details vary considerably by provider and operating model. The important treasury question is what happens after the currency becomes available to the merchant. That requires distinguishing several things that frequently get grouped together. A settlement balance is not automatically working capital A balance displayed by a PSP may contain funds that are available for payout, subject to settlement schedules, reserved against obligations, or offset against fees, refunds, or chargebacks. The fact that an amount appears in a dashboard does not necessarily mean treasury should treat every unit as freely deployable cash. A provider balance is not necessarily a bank balance Merchants should understand the legal and regulatory nature of every institution holding material cash.

The UK provides a useful illustration. The FCA requires relevant payment and e-money firms to safeguard qualifying customer funds under specific rules, but safeguarding is structurally different from holding a traditional bank deposit. The UK Financial Services Compensation Scheme separately explains that ordinary deposit protection does not apply directly to money held with e-money or payment-services firms in the same way it applies to eligible bank deposits. (FCA) The rules differ by jurisdiction and institution, so the practical question is not simply: “Where does the dashboard show my EUR?” It is: “Who legally holds or owes this balance, under what regime, and how quickly can I move it?”

The five legitimate jobs for a foreign-currency balance A practical multi-currency treasury policy starts by separating balances according to what they actually finance. 1. Refund and chargeback funding A merchant may receive GBP from UK customers and continue to incur GBP-denominated refunds after the original sales period. Immediately converting every pound into another currency can create an avoidable cycle: GBP revenue → convert GBP into treasury currency → customer requests refund → acquire GBP again or have the provider perform another conversion → issue refund Keeping a measured GBP refund reserve can eliminate part of that repeated currency movement. The relevant number is not total GBP revenue. It is forecast GBP refund need. If normal refund requirements are £40,000 over a defined period, retaining £300,000 simply because £300,000 is available is not refund management. It is excess currency exposure.

2. Supplier and operating-cost matching Suppose an international merchant receives €800,000 of EUR-denominated revenue each month and pays approximately €350,000 in recurring EUR expenses. Those expenses could include: * European suppliers * contractors * warehousing * software * local operating costs * payroll, where applicable * taxes or statutory obligations, where appropriate Converting all €800,000 into another currency and subsequently buying €350,000 to cover EUR obligations introduces currency conversion that may not be economically necessary. Matching EUR receipts against EUR expenses is a natural hedge. The U.S. Trade Finance Guide explicitly describes natural hedging as matching foreign-currency receipts with expenditures in the same currency. (Trade.gov) That is fundamentally different from maintaining a directional view that EUR will appreciate. The merchant is holding EUR because it needs EUR. That is the evidence anchor for the entire policy.

3. Short-term operating liquidity A currency may also be retained because the business needs reliable access to it between settlement and its next payment cycle. For example, treasury might determine that a subsidiary requires approximately 20 business days of local-currency operating expenses. The target balance should therefore be based on expected cash use: Target operating balance = forecast currency outflows × chosen liquidity buffer The buffer should reflect: * settlement predictability * payment frequency * refund variability * banking cutoffs * provider payout schedules * transfer lead times * access to alternative liquidity A liquidity reserve has a defined purpose and horizon. An indefinite balance does not.

4. Planned same-currency obligations Some currencies may not be required daily but are required predictably. Perhaps a merchant: * pays a quarterly supplier invoice in CHF * remits a recurring software or licensing payment in USD * pays annual insurance in EUR * expects a known tax payment in a local currency Converting currency that will predictably be needed again can create additional transactions without reducing the underlying business requirement. That does not mean the merchant should automatically retain an entire quarter's worth of revenue. Instead, treasury can set accumulation thresholds tied to the future obligation.

5. Restricted or specialist-handling balances Some currency positions cannot be managed through a generic “retain or convert” rule. Country-specific foreign-exchange administration, convertibility, documentation, permitted payment purpose, bank requirements, account type, or transfer restrictions may matter. Mainland China is a useful example of why this category needs to exist rather than being improvised. China’s State Administration of Foreign Exchange maintains a substantial foreign-exchange administration framework covering, among other areas, current-account activity, capital-account activity, bank FX business and foreign-exchange accounts. SAFE's catalog published in 2025 listed 174 major regulations in force as of June 30, 2025. That does not mean every commercial RMB transaction is restricted in the same way; it means the applicable flow must be classified and checked rather than treated like an unrestricted treasury transfer. (Safe) This is the fifth policy category: Restricted handling. Its operating rule is not “hold forever.” It is: Do not establish an ordinary conversion or transfer policy until the entity, account, transaction type, documentation and applicable FX rules have been verified.

Accounting standards also recognize that exchangeability itself can become a material issue. Amendments to IAS 21 effective for annual periods beginning on or after January 1, 2025 address circumstances in which one currency cannot be exchanged into another and how that lack of exchangeability should be assessed and reported. (IFRS)

Holding a currency is not the same as hedging it This distinction prevents a great deal of bad treasury logic. Suppose a USD-functional-currency merchant receives €500,000. It has three choices: 1. Convert the EUR. 2. Keep the EUR because it has €500,000 of upcoming EUR expenses. 3. Keep the EUR because it believes EUR will rise against USD. Only the second choice is directly tied to operating architecture. The third introduces a directional currency position. A natural hedge occurs when business inflows and outflows offset one another. A formal financial hedge may involve forwards, options, swaps or other financial instruments and requires a different level of treasury expertise, governance, accounting and risk management. A merchant can therefore hold a currency without being hedged. And it can hedge an exposure without maintaining a large cash balance. This article concerns operating balances and natural matching—not speculative FX positions or the design of derivative hedging programs.

FX cost and FX exposure are different things This is the second major distinction. FX cost FX cost arises when currency is converted. It can include: * exchange-rate spread * explicit conversion fee * bank fee * provider markup * intermediary costs associated with the transfer FX exposure FX exposure exists while the economic value of a foreign-currency position can change relative to the merchant's relevant functional or treasury currency. IAS 21 defines functional currency as the currency of the primary economic environment in which an entity operates and treats other currencies as foreign currencies for the entity. (IFRS) Imagine a merchant that saves $8,000 in conversion costs by retaining a currency for six months. If the merchant has no corresponding obligations in that currency, the economic value of that balance may move during those six months. The merchant avoided one cost. It did not eliminate risk. This is why the statement “holding currencies avoids FX costs” is incomplete. A better formulation is: Holding a currency can reduce unnecessary conversion when future same-currency use exists. Otherwise, it may merely postpone conversion while creating currency exposure and operating complexity.

The Foreign-Currency Balance Policy Every currency should be assigned one—and only one—primary operating policy. 1. Operational retain Use when the currency regularly funds: * refunds * suppliers * payroll * taxes * recurring operating expenses * other predictable same-currency obligations The target balance should be based on forecast cash requirements, not revenue volume. Example A merchant earns substantial EUR revenue and consistently pays EUR suppliers. Policy: Retain enough EUR to cover the approved operating horizon, then convert or transfer excess amounts.

2. Threshold retain Use when the merchant needs some currency, but not continuously. The balance is allowed to accumulate between a minimum and maximum threshold. When the upper threshold is exceeded, excess funds are converted or transferred. Example GBP is needed primarily for refunds. Treasury could maintain: * Minimum: expected short-term refund requirement * Target: refund requirement plus an approved buffer * Maximum: target plus tolerance * Excess: convert or transfer This prevents every refund from triggering a new FX transaction without allowing GBP to accumulate indefinitely.

3. Periodic convert Use when: * the merchant has little recurring operational demand * transaction volume is meaningful enough that transaction-by-transaction conversion is undesirable * treasury wants predictable conversion and reconciliation cycles Possible policies include: * weekly conversion * twice-monthly conversion * monthly conversion * conversion aligned to treasury close The schedule should be based on operating need and risk appetite—not an attempt to time the FX market.

4. Immediate convert Use when the merchant has no meaningful recurring need for the currency. This is often appropriate for a small, low-volume currency that would otherwise create: * immaterial balances * additional reconciliation * more accounts * extra forecasting * currency exposure * operational exceptions For example, if a merchant receives a small amount of a currency each month but has no suppliers, refunds, payroll, taxes or other obligations denominated in it, retaining the balance merely fragments treasury. Subject to provider functionality and conversion economics, an automatic conversion rule may be more rational.

5. Restricted handling Use when: * conversion is subject to market-specific rules * transferability is uncertain * documentation is required * account structure matters * funds may not be freely movable for the intended purpose * provider or banking access imposes specific constraints This category should trigger specialist review. Do not use ordinary treasury thresholds until the merchant has verified: * legal entity * account ownership * balance location * transaction purpose * currency * conversion mechanism * transfer route * documentation * regulatory requirements * bank and provider rules

The policy table every treasury team should maintain For each retained currency, record: Field Question it answers Currency What are we holding? Purpose Why does this balance exist? Policy Operational retain, threshold retain, periodic convert, immediate convert or restricted handling? Holding location Provider, bank, subsidiary account or central treasury? Legal owner Which entity controls the funds? Target balance How much should normally be retained? Minimum balance At what point could operations become underfunded? Maximum balance At what point has cash become excessive? Conversion trigger Amount, date, forecast or exception? Destination Where do converted or excess funds go? Owner Who can approve the rule or an exception? Review cadence Daily, weekly, monthly or quarterly? The most important field is Purpose. If treasury cannot complete that cell in one sentence, the balance deserves review.

A hypothetical merchant policy Consider an international digital merchant with five relevant currency situations. Currency situation Policy Why EUR revenue and recurring EUR suppliers Operational retain Same-currency expenses create a natural match GBP used mainly for customer refunds Threshold retain Maintain refund liquidity; convert excess Small low-volume currency with no operating use Immediate convert Avoid idle fragmented balances Higher-volatility operating currency needed only for short-term refunds Short-period threshold / periodic convert Preserve necessary operating liquidity while limiting unneeded open exposure Currency or market subject to material FX-administration requirements Restricted handling Confirm banking, regulatory and transfer requirements first Notice what the table does not ask: “Which currency is likely to appreciate?” That is not the operating question this framework is designed to answer.

Volatility should shorten the justification horizon A currency balance held for tomorrow's refunds has a stronger operational justification than the same balance held with no expected use for nine months. As holding periods increase, treasury should ask harder questions: * What obligation will consume this balance? * When will that obligation occur? * How certain is the forecast? * What happens if the currency moves materially before then? * Can the balance be converted when required? * Does the provider or bank impose withdrawal limitations? * Is the position concentrated with one counterparty? For a more volatile currency with only limited operational use, that analysis may justify maintaining a smaller buffer and converting excess balances more frequently. That is a risk-control decision, not a forecast that the currency will weaken.

Centralize rules even when balances remain local International merchants frequently need accounts, providers and currencies spread across several markets. That does not mean every regional team should establish its own treasury logic. Central treasury can define: * approved currencies * allowed purposes * target methodologies * maximum holdings * conversion authority * counterparty limits * reporting standards * exception procedures while local finance teams continue handling legitimate operating needs. Centralization is particularly useful when it enables exposures to be viewed together rather than as isolated balances. BIS research and analysis has documented how corporate treasury centralization and internal netting can reduce the need to manage gross FX positions individually. (Bank for International Settlements) The objective is not to move every unit of cash into one country. It is to create one policy language for deciding why cash remains decentralized.

Provider risk and banking risk belong in the currency policy Foreign-currency management is not only about exchange rates. Suppose €2 million is sitting with one PSP and another €2 million is held in a regulated bank account. The currency may be identical. The counterparty structure may not be. Treasury should therefore track: * amount held with each PSP * amount held with each bank * legal entity holding or entitled to the funds * whether the balance is a bank deposit, safeguarded payment balance or another arrangement * withdrawal conditions * settlement and payout timing * applicable regulatory regime * concentration * operational dependency on the provider A foreign-currency dashboard that shows currency exposure but ignores where the cash sits is incomplete.

Settlement currency and treasury currency do not have to be identical Another common mistake is assuming every retained settlement currency must eventually become the merchant's functional currency immediately. That is not necessarily true. If EUR revenue will finance EUR costs, converting it immediately into USD simply because USD is the parent company's reporting or treasury currency may create a round trip. Conversely, accepting customer payments in EUR does not mean maintaining a permanent EUR balance makes sense. These are separate decisions: Presentment: What currency does the customer see and pay? Settlement: What currency does the payment provider make available? Balance management: How much of that currency should the merchant retain? Treasury destination: In which currency and account does the merchant ultimately need excess liquidity? Keeping these decisions separate prevents payment configuration from accidentally determining treasury policy.

How to measure whether a foreign-currency policy is working A balance policy should be measurable. 1. Balance by currency Report separately by: * currency * legal entity * provider * bank * country * availability status Do not rely only on group-level totals.

2. Days of operating need Days of operating need = usable currency balance ÷ forecast average daily eligible currency outflows If €450,000 is available and forecast eligible EUR outflows are €15,000 per day: €450,000 ÷ €15,000 = 30 days Treasury can then compare actual days held with the approved target.

3. Supplier matching ratio One practical version is: Supplier matching ratio = same-currency supplier payments funded from retained same-currency cash ÷ total eligible supplier payments in that currency × 100 A low ratio may indicate that treasury is holding a currency without actually using it to offset obligations.

4. Refund-funding coverage Refund-funding coverage = immediately available retained balance ÷ forecast refunds for the defined refund horizon Track this by currency rather than globally.

5. FX conversion volume Track: * currency sold * destination currency * amount * date * provider or bank * reason * reference rate * actual rate * explicit fees This makes repeated conversion visible.

6. Effective FX cost A useful internal calculation is: Effective FX cost % = (reference-rate value − actual net converted value) ÷ reference-rate value × 100 The reference rate and timestamp should be defined consistently. This captures more than an advertised FX fee.

7. Idle cash Define idle cash as: Available currency balance above the approved maximum that has no identified near-term operating use. This is one of the most important metrics in the policy. Idle foreign currency creates both opportunity cost and currency exposure.

8. Currency concentration One useful measure is: Largest non-functional-currency balance ÷ total foreign-currency balances × 100 Also track concentration by provider and banking counterparty.

9. Reconciliation-exception rate Records requiring manual investigation ÷ settlement and balance records reviewed × 100 An additional currency is not free merely because FX conversion is avoided. It may create additional: * account statements * settlement records * journal entries * bank reconciliations * FX remeasurement * operational exceptions

10. Provider exposure Track both: Balance held with provider and Provider-held balance ÷ total available cash × 100 The same analysis can be performed by bank.

A practical review cadence Daily Automate alerts for: * balances above maximum * balances below minimum * failed transfers * unexpected conversion * restricted-currency exceptions * provider concentration Weekly Treasury reviews: * major balance movements * forecast refund needs * supplier matching * conversion requirements * unusual accumulation Monthly Finance and treasury review: * effective FX cost * idle balances * policy exceptions * days of operating need * reconciliation burden * forecast accuracy Quarterly Review whether each currency still deserves its existing policy. Ask again: Why is this balance here? A currency that was operationally important six months ago may no longer be.

What would disprove the case for retaining a currency? Good treasury policy should be falsifiable. A retained-currency strategy deserves reconsideration when: * same-currency expenses do not actually materialize * refund balances remain materially above required levels * the supposed FX savings are smaller than operating and reconciliation costs * currency repeatedly sits above its maximum * the merchant must eventually convert nearly all of the balance anyway * funds cannot be moved when treasury needs them * provider concentration becomes excessive * the balance creates accounting or reconciliation problems disproportionate to its value The hypothesis is: Retaining this currency improves the merchant's operating economics or liquidity because the merchant has future use for it. If the data repeatedly shows otherwise, convert or redesign the policy.

Those public materials support a conversation about settlement and payout currency architecture. They do not, by themselves, establish that every merchant can: * indefinitely hold every supported currency * convert every balance on demand * use every currency for every payment method * settle every currency to every country * use arbitrary bank-account destinations * avoid regulatory restrictions

That qualification actually strengthens the article. The merchant question is not: “How many currencies does my PSP support?” It is: “Which supported currencies should become part of my treasury architecture?”

Final treasury recommendation A multi-currency balance sheet is not automatically a sign of sophisticated international treasury. Sometimes it is simply the residue of dozens of payment decisions that were never connected to a cash-management policy. Start with the currencies already sitting in your merchant accounts, payment providers and bank accounts. Then make every balance defend its existence. For every currency, define: 1. Purpose 2. Target balance 3. Minimum balance 4. Maximum balance 5. Conversion trigger 6. Destination 7. Owner 8. Review cadence Then assign one policy: * Operational retain * Threshold retain * Periodic convert * Immediate convert * Restricted handling The principle is deliberately simple: Retain currency because the business needs the currency. Not because it might rise. Not because converting feels expensive. Not because the provider offers a wallet for it. And not because nobody ever established a conversion rule. A foreign-currency balance is most useful when it is part of the merchant's operating architecture—not a passive bet sitting inside it.

Short operational FAQ Should merchants convert foreign-currency revenue immediately? Not necessarily. If the merchant has predictable expenses, refunds or other obligations in that currency, retaining an appropriate operating balance may avoid unnecessary conversion. If there is no recurring use, immediate or periodic conversion may be more appropriate. Does holding foreign currency eliminate FX costs? No. It may avoid or defer a specific conversion. The merchant can still have currency exposure while holding the balance, and conversion may eventually be required. Is holding foreign currency the same as hedging? No. Retaining foreign currency is a cash-management decision. A natural hedge occurs when foreign-currency revenues offset expenses in the same currency. Formal hedging typically involves a separate treasury and financial-instrument strategy. U.S. government trade guidance similarly distinguishes natural matching from formal FX instruments. (Trade.gov) How much currency should a merchant retain for refunds? Base the target on expected refunds during a defined period plus an approved liquidity buffer. Do not base it simply on gross revenue or the maximum balance available. Should a merchant keep money with a PSP or move it to a bank?

That depends on operational requirements, settlement arrangements and the legal nature of the balance. Merchants should compare counterparty risk, access, regulatory treatment, transfer timing and concentration rather than assuming a provider balance and bank deposit are equivalent. The UK regulatory example illustrates why the distinction matters. (FCA)

Original article asset: Foreign-Currency Balance Policy Dashboard Dashboard concept Headline: Every Currency Needs a Job Five columns or policy lanes: OPERATIONAL RETAIN Use it. Keep it. * suppliers * payroll * taxes * recurring expenses THRESHOLD RETAIN Keep enough. Convert excess. * refunds * variable expenses * liquidity buffers PERIODIC CONVERT Consolidate on schedule. * limited operational use * meaningful recurring inflow * controlled treasury cycle IMMEDIATE CONVERT No job? Don't accumulate it. * low volume * no local costs * no recurring refunds RESTRICTED HANDLING Verify before moving. * country FX rules * convertibility * documentation * account restrictions Footer: Purpose → Target → Min → Max → Trigger → Destination → Owner → Review Supporting flow Settlement currency ↓ Does the merchant have a defined future use? Yes → Match against obligations → Set operating/threshold balance No → Define periodic/immediate conversion Restrictions apply or are uncertain → Specialist review Image alt text “Foreign-currency balance policy dashboard showing five merchant treasury policies: operational retain, threshold retain, periodic convert, immediate convert and restricted handling, with rules for target balances and conversion triggers.”

I treated the uploaded editorial brief as the controlling specification and kept this article tightly focused on what happens after a merchant has chosen to retain foreign currencies, rather than re-covering settlement-currency selection or cross-border settlement mechanics. Editorial interpretation The merchant decision this article owns: For every currency the merchant receives or retains, decide whether to keep it, how much to keep, when to convert it, where to move it, and who owns that decision. The movement of money this article explains: Settlement balance → retained foreign-currency balance → same-currency operational use or FX conversion → merchant bank/treasury destination. Unique evidence anchor: A foreign-currency balance should exist because the merchant has a future use for that currency—not simply because the provider allows it to be held. Editorial position: Merchants should retain foreign-currency balances only when those balances serve a defined operating, refund, liquidity, or treasury purpose, or materially reduce repeated conversion. Common assumption challenged: “Holding currencies avoids FX costs.” It may avoid a conversion today. It does not automatically eliminate FX exposure, operating complexity, counterparty exposure, or a conversion that will still have to occur later. Most important distinction: Avoiding conversion is not the same as avoiding currency risk. Selected format: Treasury policy framework. Structural rationale:

The article begins with the balance itself rather than the payment transaction. Each currency is then assigned a business purpose and operating rule. That keeps the article centered on treasury architecture instead of drifting into the mechanics owned by the cluster’s settlement articles. How this differs from adjacent articles: * Multi-Currency Settlement Explained owns how currencies reach settlement. * How to Choose Settlement Currencies owns which currencies a merchant should request. * Repatriating Revenue From Foreign Markets owns moving foreign earnings toward a home or treasury structure. * Foreign-Exchange Controls by Country owns jurisdiction-specific restrictions. This article owns what treasury should do once the currency is sitting on the balance sheet. SEO metadata SEO title: Managing Foreign-Currency Balances: A Treasury Framework for Merchants H1: Managing Foreign-Currency Balances: A Practical Framework for International Merchants Meta description: Learn when merchants should retain, convert or consolidate foreign-currency balances using a practical framework for refunds, suppliers, liquidity and FX. URL slug: /managing-foreign-currency-balances Article excerpt: Holding multiple currencies can reduce unnecessary conversion—but only when each balance has a defined business purpose. This framework helps international merchants decide which currencies to retain, how much to keep, when to convert them and which balances require specialist handling. Primary keyword:

managing foreign currency balances Secondary keywords: * foreign currency balance management * multi currency treasury * ecommerce currency balances * merchant FX management * international payment balances * settle and hold foreign currency * currency treasury strategy * manage multi currency revenue Related entities/concepts: * foreign exchange * treasury management * multi-currency settlement * functional currency * settlement currency * payout currency * natural hedge * liquidity * refunds * supplier payments * currency conversion * FX controls * working capital * reconciliation

Internal-link recommendations 1. How to Choose Settlement Currencies Recommended anchor: choose the right settlement currencies Best placement: Section explaining why settlement currency and treasury currency do not have to be identical.

2. Multi-Currency Settlement Explained Recommended anchor: how multi-currency settlement works Best placement: Near the early settlement-balance flow.

3. Repatriating Revenue From Foreign Markets Recommended anchor: repatriating revenue to centralized treasury Best placement: Centralization section.

4. Foreign-Exchange Controls by Country Recommended anchor: country-specific foreign-exchange controls Best placement: Restricted-handling section.

Authoritative source recommendations IFRS Foundation — IAS 21 Use for: * functional currency * foreign currency * accounting treatment of FX * lack of exchangeability IAS 21 defines functional currency around the entity's primary economic environment and now includes specific requirements relating to lack of exchangeability. (IFRS) U.S. International Trade Administration — Trade Finance Guide Use for: * FX-risk framing * natural hedging * matching receipts with expenditures * distinction between operating FX management and profit-seeking The guide explicitly identifies natural hedging through matched foreign-currency receipts and expenditures and states that FX-risk management is aimed at limiting financial loss rather than seeking profit. (Trade.gov) UK Financial Conduct Authority Use for: * provider-held funds * safeguarding * payment/e-money institution treatment The FCA's safeguarding guidance was updated May 7, 2026 and explains requirements applying to qualifying payment and e-money institutions. (FCA) UK Financial Services Compensation Scheme Use as a concrete illustration of: * bank deposit versus payment/e-money balance * counterparty classification Current FSCS materials distinguish eligible protected bank deposits from money held directly with e-money or payment-services firms. (FSCS) State Administration of Foreign Exchange — China Use for: * restricted-handling example * current-account versus capital-account controls * account administration * regulatory verification

SAFE's latest English-language catalog located for this review covers rules effective through June 30, 2025. Country-specific claims should be refreshed immediately before publication. (Safe) International Monetary Fund — AREAER Use primarily as: * global screening source * cross-country taxonomy * starting point for identifying restrictions The IMF's AREAER covers exchange arrangements, restrictions on international payments and transfers, capital controls and related currency arrangements. Country-level publishing claims should still be checked against the relevant current central bank or regulator. (IMF) Bank for International Settlements Useful supporting research for: * corporate FX exposures * natural offsets * treasury centralization * internal netting Recent BIS research finds that many non-financial companies offset foreign-currency exposures using income, assets or other business exposures in the same currencies. (Bank for International Settlements)

Structured-data recommendation Use: * Article * BreadcrumbList Google's current documentation continues to support Article structured data and BreadcrumbList markup. (Google for Developers)

Proposed author and reviewers Proposed author:

Primary expert reviewer: Treasury or Finance leader. Supporting reviewers: * Payment Operations * Reconciliation/Finance Operations

* Legal/Compliance or regional specialist for restricted-market examples Do not publish invented names or credentials. Recommended byline enhancement: Include an actual 2–4 sentence treasury observation from the reviewer, such as a lesson involving idle balances, refund funding, reconciliation or currency matching.

Treasury measurement plan The post-publication operational framework should encourage merchants to maintain a monthly dashboard containing: 1. Currency balance 2. Holding institution 3. Legal entity 4. Days of operating need 5. Target/min/max variance 6. Refund-funding coverage 7. Supplier matching ratio 8. FX conversion volume 9. Effective FX cost 10. Idle cash 11. Currency concentration 12. Provider/bank concentration 13. Reconciliation-exception rate 14. Policy exceptions Primary metric for this article Idle foreign-currency balance above approved operational need That is more aligned with the thesis than using FX savings alone.

Financial fact-check items before publication Verify: * Accounting language involving functional currency with Finance/Accounting. * Whether “working capital” is being used consistently with internal finance terminology. * Formula methodology for effective FX cost.

* Whether chargebacks are generally debited in original transaction currency under the relevant products. * Whether any example could be interpreted as formal treasury advice. * Treatment of reserves versus available balances.

Banking fact-check items

* What institution legally holds merchant funds? * Which entity owes settlement to the merchant? * Does the merchant have a bank balance, PSP ledger balance, safeguarded balance or another claim? * Can merchants choose when to withdraw? * Which account types can receive settlement? * Must payout account currency match settlement currency? * Does account location matter? * Are virtual accounts relevant? * Are intermediary banks involved? * Are there payout or correspondent-bank fees? * What happens during provider or bank failure? * How are balances treated if a merchant account is suspended or closed?

Currency fact-check items Verify: * Currencies merchants can present to customers. * Currencies merchants can actually settle. * Currencies merchants can receive as payouts. * Currencies merchants can retain rather than automatically convert. * Whether on-demand FX exists. * Whether automated conversion thresholds exist. * Whether currency-specific minimum payout levels exist. * Applicable FX pricing/spreads. * Currency-specific settlement frequency. * Refund currency behavior. * Chargeback currency behavior. * Whether balances can be moved between merchant legal entities. * Whether the merchant can nominate multiple same-currency bank accounts.

Country-specific fact-check items For any market used as a restricted-handling example, verify immediately before publication: 1. Relevant merchant entity 2. Residence status 3. Currency 4. Account type 5. Payment purpose 6. Transaction classification 7. Conversion rules 8. Outbound-transfer requirements 9. Bank documentation 10. Current central-bank/regulator guidance 11. Effective date 12. Relevant exemptions China specifically Do not publish: “CNY cannot be freely transferred.” Instead verify the specific transaction and explain the applicable SAFE regime. China's framework distinguishes multiple transaction and account categories, so a generalized statement would be too broad. (Safe)

Regulatory, legal, tax and treasury fact-check items Confirm whether any retained-balance strategy affects: * local payment-services regulation * safeguarding * permitted account ownership * foreign-exchange reporting * current-account or capital-account classification * withholding * tax payment requirements * intercompany transfer treatment * permanent-establishment analysis * transfer pricing * sanctions screening * treasury licensing * local cash-pooling rules The article should explain questions to investigate, not recommend a corporate or tax structure.

Amber-flag claims

RED/AMBER — Merchant-controlled currency holding

A displayed “available balance” is not sufficient evidence of merchant-controlled multi-currency treasury functionality. AMBER — Restricted currency terminology Avoid labeling an entire national currency “restricted” without defining the relevant convertibility or transfer limitation. AMBER — Natural hedge Safe to explain conceptually, but avoid claiming a natural hedge eliminates all FX risk. AMBER — FX savings Never publish a percentage saving without: * currency pair * amount * reference rate * timestamp * actual rate * explicit fee * comparison structure

1. Can merchants maintain independent balances by settlement currency? 2. Which currencies can be retained? 3. Which are automatically converted? 4. Can merchants initiate conversion manually? 5. Can merchants establish automated conversion rules? 6. Are there minimum or maximum balances? 7. Can different currencies settle into separate bank accounts? 8. Can the same currency settle to multiple accounts? 9. Can balances be used directly to fund refunds? 10. Are refunds deducted from future settlement? 11. Can currency balances be transferred between merchant entities? 12. Which payout currencies are currently supported? 13. What bank-account denomination rules apply? 14. How is FX priced? 15. What reporting supports currency-level reconciliation? 16. What happens to currency balances when processing stops? 17. Which currencies/countries require special treasury treatment? 18. Are merchant balances safeguarded, bank-held or structured differently by product/entity/jurisdiction?

Provider-specific verification requirements For any PSP, acquiring partner or bank evaluated by a merchant, verify: * balance legal structure * supported holding currencies * settlement currency * payout currency * bank-account requirements * conversion timing * withdrawal timing * spread and explicit fees * minimum payout * reserves * negative balances * refund funding * chargeback funding * transfer limits * cross-border availability * local regulatory restrictions * failure/safeguarding regime * reconciliation files and APIs This can become a downloadable Foreign-Currency Provider Audit Checklist later.

Cluster sameness-audit fields Title: Managing Foreign-Currency Balances: A Practical Framework for International Merchants First two sentences: “Imagine opening the treasury dashboard on Monday morning and seeing balances in twelve currencies. EUR has been building for months.” Opening device: Twelve-currency treasury dashboard and the question “Why is each balance there?” Primary format: Treasury policy framework. Unique evidence anchor: A balance exists because the merchant has a future use for that currency. Editorial position: Retain currencies only for defined operational purposes or demonstrable reduction of repeated conversion. Merchant decision: Retain, threshold, periodically convert, immediately convert or apply restricted handling. Main country example: Mainland China solely as an illustration of specialist FX-regulatory handling. Original framework: The Foreign-Currency Balance Policy. Primary metric: Idle foreign-currency balance above approved operating need. Conclusion: Every currency must defend its existence with a purpose and operating rule. CTA: Map every settlement currency to a defined operating purpose, then verify whether the merchant's payment and banking providers can support the required settlement, holding, conversion and payout structure. FAQ: Short operational FAQ centered on conversion, holding, hedging, refunds and provider versus bank balances. Supporting asset: Five-lane currency-policy dashboard. Distinctive cluster role: Post-settlement treasury management.

Recommended CTA for the published article International payment infrastructure should not determine treasury policy by accident. Map the currencies your business collects, the currencies it actually needs, and the balances currently sitting across payment providers and bank accounts. Then define which currencies should be retained, converted or treated separately.

Every currency should have a job. The strongest part of this version is that it gives Article 10 a very clean piece of intellectual territory: settlement produces balances; treasury decides whether those balances deserve to continue existing. That should keep it from cannibalizing the settlement-currency and repatriation articles while giving you a strong original visual and framework.