Stablecoins in Corporate Treasury: What Changes and What Does Not

Stablecoins are being tested in both consumer payments and treasury. The results vary by corridor, issuer, wallet, off-ramp and local regulation. It is too early to declare one rail the universal winner for consumers or for corporates.

Treasury is a distinct question. A corporate may value an always-available on-chain transfer between approved wallets, even where it would not ask a consumer to hold a token. But an on-chain transfer is not automatically final payment in local law, bank money at the destination, or a completed supplier payment. It still has to be redeemed, reported, reconciled and controlled.

This guide sets out where a controlled pilot may be useful, what it does not solve, and the questions a treasury team should answer before moving funds.

What changes in treasury

Three structural changes when stablecoins enter the treasury stack:

1. A 24/7 transfer rail. A public-chain transfer can be submitted and confirmed outside banking hours. That does not by itself establish when the receiving party can use bank funds, when an issuer will redeem, or when a transfer is legally final. BIS notes that ledger state and legal finality can diverge, and that finality needs a clear legal basis.

2. A different cross-border path. A token transfer can avoid sending that leg through a correspondent-banking message chain. It does not remove the need for a regulated issuer, wallet/custody controls, sanctions screening, local conversion, beneficiary due diligence or an account that can receive local funds. Costs and timing move from the transfer leg into issuance, gas, custody, FX, off-ramp and exception handling.

3. Conditional workflows are possible, not automatic. Smart contracts can constrain how a token moves, but a treasury team still needs to decide who controls keys, validates the triggering evidence, resolves disputes and reverses operational mistakes. Do not treat programmable transfer logic as a substitute for a contract, custody policy or approval control.

What does not change: the accounting, the audit, the tax, the regulator reporting, the FX-policy compliance, the fraud risk profile, the operational discipline. The treasurer's job is the same job; some of the tools are different.

Four use cases worth testing carefully

1. Cross-border supplier and intercompany settlement

This can be a reasonable pilot where both entities can lawfully hold and redeem the selected token, the currency exposure is understood, and each side has approved custody and accounting controls. Traditional rails vary widely by bank, corridor and cut-off; compare the full process rather than assume a fixed delay or fee.

The on-chain leg may complete quickly. The end-to-end transfer is complete only when the receiving entity has the funds or token it is entitled to use, the transfer has the required approvals, and both ledgers reconcile. Direct redemption terms also matter. For example, Circle says USDC redemption is subject to eligibility, account requirements, applicable law and fees.

When to consider it. Start only where both entities, the issuer, custodian and off-ramp are permitted for the relevant jurisdictions and where the existing bank route has a specific problem the new route can test.

What the treasurer ships. A stablecoin-enabled corridor for a bounded approved intercompany flow; a clear policy on eligible currencies, corridors and amounts; accounting/reporting integration; and an audit trail.

2. Liquidity management between regional treasury hubs

A corporate operating from London, Singapore, Dubai, and New York runs intra-day liquidity across the four hubs. Traditional intra-day liquidity is constrained by correspondent-banking cut-off times and by minimum-balance constraints in each location.

An approved wallet-to-wallet transfer can support an intraday liquidity process. It does not create usable local-currency liquidity in every location: that depends on redemption access, local banking cut-offs, FX conversion, limits and legal restrictions.

When to consider it. Related entities can reduce commercial counterparty uncertainty, but issuer exposure, custodian exposure, key compromise, chain outages, local regulatory requirements and FX exposure remain.

What the treasurer ships. A stablecoin-treasury wallet structure at each hub; intra-day rebalancing logic; FX-policy compliance on each leg.

3. Payouts to non-bank counterparties

For a counterparty without a suitable bank route, a stablecoin payout can be worth evaluating where the recipient actively wants it and has a lawful, reliable off-ramp. It is not evidence that a token payout is faster or cheaper in a particular market.

The recipient receives a token to a wallet and still needs a safe way to custody it, understand its value and convert it when necessary. The sender should not describe that conversion as frictionless unless the actual recipient journey has been tested.

When to consider it. Confirm that the recipient has chosen this method and can use a licensed or otherwise appropriate local off-ramp. Compare the full recipient experience, fees and support burden with the bank and wallet alternatives available in that market.

What the treasurer ships. A payout process with approved issuer, custody and off-ramp arrangements; counterparty onboarding and KYC; corridor-specific partner controls; and jurisdictional tax/reporting treatment.

4. FX hedging with deeper liquidity pools

Some firms may test token-based FX or liquidity venues for a specific pair. That is an execution and counterparty decision, not a general stablecoin-treasury benefit.

How to assess it. Compare executable quotes, depth, settlement path, market-access permissions, counterparty risk, controls and the cost of converting the result into required bank funds. A quoted on-chain spread alone is not a treasury cost.

What the treasurer ships. A regulated stablecoin-FX execution capability; per-pair execution policy; counterparty risk management; reconciliation with the traditional treasury reporting.

Four claims that need more evidence

1. "Stablecoin payroll for the whole company"

The deck shows the corporate paying every employee in stablecoin, with the employee converting to local fiat. In practice, employment law, payroll tax, wage-protection rules, employee choice and off-ramp access vary by jurisdiction. Treat this as a local payroll design question, not a generic treasury rollout.

It may fit a defined contractor or cross-border cohort, but only after the employment, tax, recipient-choice and conversion paths have been assessed locally.

2. "Stablecoin replaces all working capital"

The deck shows the corporate's working capital living in stablecoin rather than in bank deposits. A stablecoin is a claim governed by its issuer terms, reserve design, eligibility and applicable law; it is not the same thing as a commercial-bank deposit or central-bank money. Circle's USDC terms, for example, make redemption conditional on eligibility and account requirements. Keep operating balances, reserve exposure and redemption concentration distinct in treasury policy.

3. "Stablecoin for all cross-border, all the time"

The deck shows the corporate doing every cross-border payment via stablecoin. The reality: many counterparties cannot or will not accept stablecoin; many corridors do not have mature regulated infrastructure; many use cases (large bank-to-bank corporate flows, treaty-network FX, regulated commodity payments) work fine on traditional rails. Stablecoin earns its keep on specific corridors / amounts / counterparties, not as a default for all.

4. "DeFi treasury yield optimisation"

The deck shows treasury cash earning DeFi yields by being deployed into stablecoin lending and liquidity pools. This introduces protocol, custody, liquidity, legal, accounting and tax risks that are separate from a payment-rail pilot. A treasury team should evaluate any such exposure under its own investment policy and risk limits, not bundle it into a settlement decision.

Regulation is jurisdiction-specific

There is no single settled global framework for corporate stablecoin use. The FSB's recommendations seek more consistent oversight, while BIS notes divergent policy approaches and cautions that benefits may not outweigh drawbacks in every cross-border setting.

EU (MiCA). MiCA defines electronic-money tokens and asset-referenced tokens and sets issuer and service-provider rules. Whether a proposed treasury flow is available depends on the token, entity, service provider, country and use case.

US. Issuer, money-transmission, sanctions, securities, banking and state-law questions can apply to different parts of a flow. Do not reduce this to “stablecoins are permitted”; obtain advice for the issuer, custodian, redemption and business activity involved.

UAE, Singapore, UK and other hubs. These jurisdictions have distinct regulator, licensing and product rules. A corporate should confirm the exact entity, token, counterparty and activity with local counsel and regulated providers rather than transfer an approval from one jurisdiction to another.

The practical rule is to create a corridor-by-corridor legal and operational matrix. It should cover issuer and redemption rights, custody, wallet controls, transfer screening, local FX and payment rules, reporting, tax and off-ramp availability.

A decision horizon, not a five-year forecast

No credible source supports a universal timetable or share of treasury volume moving to stablecoins. A more useful horizon is operational:

Now. Establish whether the token, issuer, custody model and corridor are lawful and usable for the corporate entities involved. Map redemption and off-ramp paths before moving a production amount.

Pilot. Test one bounded use case with limits, dual controls, accounting entries, sanctions/transaction monitoring, incident handling and a bank-rail fallback. Measure the complete time and cost from funding to usable funds, not just block confirmation.

Scale or stop. Expand only if the pilot meets pre-agreed risk, control, liquidity and economic criteria. Keep the bank route where it remains more reliable or where stablecoin redemption and local conversion introduce a new concentration.

What does not change. Treasury still owns liquidity, counterparty exposure, FX, accounting, tax, sanctions, audit evidence and business continuity. Tokenising a transfer does not transfer those responsibilities to a protocol.

What a senior treasury PM ships

A working set of deliverables over the next 24 months for a senior treasury PM exploring stablecoins:

1. Policy framework. Which currencies, corridors, amounts, counterparties, use cases. Signed by CFO + CRO + GC.
2. Counterparty assessment. Which stablecoin issuers, which regulated off-ramp partners, which custody / wallet providers. Standard counterparty due diligence applied.
3. Initial corridor pilot. One bounded intercompany or supplier flow, with a duration and reporting cadence set by the approvals and control criteria.
4. Accounting and reporting integration. Stablecoin holdings and movements integrated into the existing treasury management system.
5. Audit-evidence pipeline. Every movement audit-trailed; tax and regulatory reporting integrated.
6. Policy renewal cycle. Review frequency set by the risk policy and triggered by material issuer, regulatory, custody or corridor changes.

Set the pilot timetable only after the legal, provider, custody, accounting and integration dependencies are known. A short technical demonstration is not evidence that the full operating model is ready.

The senior PM tell

One useful treasury question is: “What is your stablecoin policy, and what evidence would cause you to expand, pause or exit it?”

An operating answer names the permitted entities and corridors, issuer and redemption arrangements, custody and approval model, limits, screening, reconciliation, incident playbook, bank-rail fallback and review cadence. It also identifies the evidence required before expansion: completed redemptions, reconciled accounting, exception rates, controls testing and legal sign-off.

FAQ

Is the stablecoin treasury thesis dependent on a specific issuer (USDC, USDT)? Yes. The issuer, reserve assets, redemption eligibility, legal claim, chain, token contract, custodian and local off-ramp materially change the risk and operating model. Assess each arrangement separately.

What about depeg risk? A loss of price stability, inability to redeem, or disruption at an issuer, custodian, chain or off-ramp can be material. Stress-test those scenarios, set concentration limits and retain a bank-rail fallback rather than assuming token diversification removes the risk.

How do stablecoin operations interact with traditional banking relationships? The treasurer should normally retain the bank routes needed for funding, redemption, payroll, tax and local payments. Stablecoin use is an additional path until a specific business process has proved otherwise under the corporate's controls.

Is there a difference between stablecoins and CBDCs for treasury? Conceptually yes: stablecoins are privately issued claims, while CBDCs are central-bank liabilities. Their legal basis, access model, privacy, settlement and liquidity arrangements differ. Assess any CBDC use case on its own terms rather than assuming it behaves like a stablecoin.

What about Bitcoin treasury (MicroStrategy-style)? This is a separate balance-sheet allocation decision. Stablecoin use, by contrast, may be a payment-rail or operating-liquidity decision. The two should not be conflated.

Is this hype or substance? Both risks and useful applications exist. The discipline is to test a named corridor and operating problem, then keep or reject the rail using evidence from the complete process rather than a market narrative.

Sources

• BIS CPMI: considerations for stablecoin arrangements in cross-border payments
• Financial Stability Board: global stablecoin recommendations
• Circle: USDC terms and redemption conditions
• Circle: reserve transparency and attestations
• ESMA: MiCA token categories and issuer requirements

---

If this resonated, also read Stablecoin Payments 2026: What Actually Shipped, Crypto On-Ramps: A Product Guide, and Crypto Off-Ramps in Emerging Markets.