Stablecoins as a Treasury Payment Option: When They Make Sense and When They Don’t

Author: 

Biswajyoti (BJ) Upadhyay: Strategic Senior Advisor & Chairman of Global Transaction Banking Committee; Financial Executive Club (FinEx Club) Research Centre

Valuable review and insights have been provided by Byron Gardiner, Chairman of Global Treasury Committee

Research Analyst: Zhao JiaYi Emilia

1. The treasury problem in plain terms

Stablecoins are advertised as a more affordable and quicker method for transferring funds. That's just the beginning for a corporate treasurer. The treasury question is, what happens between the time the customer pays in a token and the time the value is used by the supplier, business unit, tax authority, lender or bank account. Once the payment rail is there it turns into an accounting, liquidity, custody, cyber, sanctions, FX and board-risk issue.

There are practical questions that need answers before a stablecoin option is ready for the treasury. Will the company retain or exchange the token as soon as possible to fiat? What is the opportunity cost of the instrument that the corporate might not receive any return on? What is the risk that a token may not represent $1 or one unit of local currency, and what is the risk that it will be issued by a non-legitimate entity? What are the risks behind the claims of one token equaling one dollar, or one unit of local currency, and the risk that the token may be issued by an illegitimate issuer? What markets and products to deploy first and what to report, bank, legal or control before it is deployed?

The answer is not simply “use stablecoins” or “do not use stablecoins.” The goal is a rules-based approach to operation. Collections, cross-border settlement, customer convenience and settlement outside banking hours can make sense of the use of Stablecoins. They can be harmful when they are not properly controlled by the wallet, the conversion to fiat is carried out on an ad hoc basis, without specifying what the funds are intended for, or without keeping an eye on whether they are used to circumvent foreign exchange policies or local monetary laws.

2. Stablecoins are a payment rail, not a source of cash

This distinction matters because treasury is responsible for liquidity discipline, not technological enthusiasm. The bank relationship and account mandate, statement process, credit policy, legal documentation and, if applicable, deposit protection support a bank deposit. A stablecoin has another stack: the issuer, reserve assets, blockchain, wallet/custodian, redemption process, market maker/exchange, off-ramp bank, and the legal regime of each jurisdiction in which the stablecoin is received or paid.

The company is not simply taking in “digital dollars” in its business activities. It is dependent on a private/regulatory network. This also relates directly to TCMAG Principal XI settlement finality and singleness of money: the company shall have an understanding of when settlement is final, what money form has actually been received, and whether the money form is bank cash for the relevant business purpose.

Stablecoins should also be integrated in the larger instrument class of tokens tokens that serve as cash. Stablecoins exist as a private money backed by an asset. Programmable rail bank money - tokenised bank deposits. The Tokenised money market fund units are more akin to reserve-cash or investment instruments, as opposed to operating payment balances. In a realistic treasury policy, the two-bucket approach is recommended: operating cash for short-term settlement and reserve cash for liquidity preservation and investment and liquidity-ratio management. Stablecoins are generally not in the reserve-cash bucket, but in the operating-cash bucket, unless the board approves a specific purpose.

One of the safe assumptions is that stablecoins can be accepted or utilized for payment execution, but they can't be infinite treasury reserves. In a normal situation, the transfer of tokens to fiat should be scheduled on the day they are to be converted or the next business day, with a documented working capital need for a small float of assets. This will help maintain a well-structured balance sheet, reduce issuer and de-peg risks, and provide ease in audit evidence.

It also guards against a frequent management mistake. A token that resembles money is not treasury money until it is received by the company, screened, matched it with the receivable, recorded its fiat value, confirmed acceptance of the token by policy, and either converted it into bank cash or had it accepted as operating float on purpose.

This is particularly true in today's geopolitical climate. But as trade routes shift, regulations on FX become stricter, sanctions grow, and supply chains try to find new ways to bypass banks' cut-off times, it's no wonder that stablecoins appear promising. That advantage doesn't count unless it is specific, legal, measurable and under the control of the treasury. Stablecoins are not intended for use as shadow FX market, bank deposits or to evade local monetary rules. They are not geopolitical workarounds or insured deposits or central bank money.

3. Decision 1: hold or convert to fiat

The initial operating decision will be whether tokens will be kept or converted. The selection impacts on accounting, audit evidence, internal control, liquidity threat, reporting to tax, reporting to management, etc. It will be recorded in advance of receiving any token.

The principle seems to be that exceptions do not exist and should be drafted as narrowly as possible. If there is an approved outbound stablecoin payment in the same token within a specific window of short duration, and if the payment is not a fiat one, then the customer receipts must be converted into fiat. Any float that is operating should be capped by token, wallet, counterparty, jurisdiction, and legal entity and ageing bucket. Anything outside those limits should auto-escalate.

Treasury decision	When it makes sense	Accounting and audit implications	Control implications
Immediate conversion to fiat	Best default for most corporates, especially where stablecoins are accepted for customer convenience but expenses, payroll and debt service remain fiat-based.	Record the receipt at the transaction-date fiat value, then record conversion proceeds, fees and any small gain or loss. Audit evidence should include the invoice, blockchain transaction hash, custodian or exchange statement, conversion confirmation and bank statement.	Lowest balance-sheet exposure. Requires approved off-ramp, automated reconciliation, clear timing rule such as T+0 or T+1, and exception reporting where conversion fails or is delayed.
Short-term operating float	Suitable where the company also pays suppliers, platforms or distributors in the same stablecoin and can match inflows with outflows quickly.	Balance remains on the books until used or converted. The auditor will expect valuation policy, ownership proof, wallet access evidence, cut-off testing and ageing reports. Classification should be agreed with finance before launch.	Requires maximum balance limits, ageing limits, dual approval, wallet whitelisting, daily reconciliation, de-peg monitoring and treasury committee oversight.
Strategic holding	Rarely appropriate for normal corporate treasury unless the firm has a regulated digital-asset business model or a specific board-approved liquidity strategy.	Creates more complex financial reporting, valuation, impairment or fair-value questions, tax issues and disclosure pressure. It also increases scrutiny of whether treasury is taking investment risk.	Highest control burden. Requires board risk appetite, market risk limits, issuer and reserve due diligence, custody due diligence, stress testing and documented exit procedures.

Treasury must not solve the accounting question after the event. Before launch, finance, audit, legal and treasury should agree how tokens will be initially measured, how period-end balances will be classified, how conversion fees and gains or losses will be recorded, and what evidence is needed for period-end cut-off. This is consistent with TCMAG Principle III on unambiguous accounting treatment.

IAS 7 and any local accounting guidance should be considered before the settlement architecture is fixed. In some circumstances, regulated stablecoins, tokenised deposits or similar instruments may be analysed as cash or cash equivalents, but that conclusion should not be assumed merely because a token tracks a fiat currency. The practical rule is sequencing: agree the accounting and audit treatment first; build the settlement flow second.

The audit issue is evidence. A blockchain record proves a technical transfer, not commercial substance, ownership, customer identity, compliance clearance or correct valuation. The audit file should contain the invoice and customer record, approved wallet address, wallet screening evidence, blockchain transaction, custodian statement, conversion record and bank credit. Without that chain, treasury may have a token transfer but not reliable evidence of a clean receivable settlement.

Internal control should therefore reflect bank-grade payment discipline. No single employee should be able to set up a wallet, change a settlement address, approve a counterparty or release a payment. Addresses should be whitelisted, address changes should require dual approval, and high-value transactions should require multi-person approval. The treasury policy should specify who can approve exceptions and how those exceptions are reported.

4. Decision 2: the yield problem

The simplest but often overlooked issue is yield. Corporate treasuries do not normally want idle assets that produce nothing. Cash can earn bank interest, reduce overdraft usage, support liquidity ratios, or be invested in approved money-market instruments. A stablecoin balance usually does not provide those benefits to the corporate holder. The income generated by the issuer’s reserve assets typically accrues to the issuer or reserve manager, not the company holding the token.

That makes opportunity cost central. Stablecoins may reduce payment fees, accelerate collections, improve settlement certainty or free trapped working capital, but the calculation must include foregone interest on fiat deposits and approved investments. The relevant treasury measure is not transaction cost alone. It is payment saving plus working-capital saving, minus conversion cost, compliance cost, custody cost, technology cost, operational risk and foregone yield.

Where applicable law or product terms prohibit issuer-paid yield to holders, the opportunity cost becomes structural rather than merely a market convention. Treasury should therefore assume that a held stablecoin balance is zero-yield unless legal, tax, accounting and board policy explicitly approve a different product or arrangement. That assumption should be reflected in the monthly benefit case.

Stablecoins should therefore be treated mainly as intraday or very short-dated settlement balances. A small buffer may be sensible where there are predictable outbound payments in the same token, but surplus tokens should be converted to fiat or moved into approved interest-bearing instruments. If a business unit says a token is “as good as dollars,” treasury should ask whether it can be converted into bank dollars quickly, with minimal spread, minimal friction and clear reporting. If not, it is not the same as cash.

The yield issue is also a governance issue. Commercial teams may focus on adoption and receipt speed; treasury must protect liquidity discipline. A monthly cost-benefit report should show payment-fee savings, days-sales-outstanding improvement, conversion spreads, failed or delayed payments, custody fees, technology costs and interest foregone on token balances. Without that reporting, management may overstate the commercial gain and understate the treasury cost.

5. Decision 3: the risk stack

Stablecoin risk is not one risk. It is a stack of risks that can fail at different points in the payment lifecycle. A stablecoin may be technically transferable but legally prohibited, temporarily below par, linked to a sanctioned address, trapped in an exchange, impossible to redeem quickly, or misreported in the ledger. Treasury’s job is to prevent those failures from becoming liquidity, compliance or financial-reporting failures.

Risk area	What can go wrong	Treasurer’s operating response	Reporting signal
Issuer, reserve and de-peg risk	The token may trade below par, redemption may slow, reserves may be questioned, or market liquidity may disappear in stress.	Use only approved stablecoins; set de-peg stop-loss thresholds; maintain multiple off-ramp options; require issuer and reserve due diligence; suspend acceptance automatically if price or redemption conditions breach policy.	Token price versus par, redemption delays, market depth, concentration by issuer, exceptions to conversion timing.
Cybersecurity and custody risk	Private keys can be stolen, wallet addresses can be spoofed, employees can be socially engineered, or custodians can suffer outages.	Prefer regulated custodians or bank-grade custody; enforce multi-factor access, multi-signature approval, address whitelisting, hardware security controls, access reviews and incident response drills.	Open access exceptions, attempted address changes, failed approvals, wallet balance by custody provider, cyber incidents and unresolved alerts.
Compliance and sanctions risk	A wallet may be linked to illicit activity; a payment may breach sanctions, AML, travel-rule or licensing requirements.	Screen counterparties and wallet addresses before acceptance and payment; retain screening evidence; block unverified wallets; escalate hits to compliance; map allowed use cases by jurisdiction.	Number of screened transactions, blocked payments, unresolved hits, countries and counterparties outside policy.
FX and restricted-market risk	Stablecoins can become an unofficial USD rail in markets with FX controls, creating arbitrage, repatriation and regulatory risk.	Do not use stablecoins to bypass FX rules. Obtain local legal sign-off, price and report consistently, limit or ban usage in restricted markets, and document central-bank or tax reporting obligations.	Stablecoin volume by restricted market, gap between official and implied FX rate, unrepatriated value, local regulatory exceptions.
Operational and reporting risk	Transactions may be misbooked, duplicated, delayed, valued incorrectly or omitted from cash forecasting.	Integrate wallets with ERP and treasury management systems; reconcile daily; assign token-specific accounts; require end-to-end evidence from invoice to bank statement.	Unreconciled items, ageing of token balances, valuation differences, manual journals, failed ERP matches.

The area of cybersecurity requires special focus. Traditional banking payment controls are part of the account mandates and bank portals. Sending to an incorrect address could result in a stablecoin transaction becoming irreversible. Address poisoning, fake wallet addresses or wallet compromise are avenues for a normal payment to be lost. Unless the company can support it with the technical ability, insurance, segregation of duties and board authorisation, treasury needs to be careful not to use self-custody.

This is no exception for compliance with the law. A company can be a borderless network, but it is not a borderless legal entity. It also has tax registrations, banking connections, licensing restrictions and reporting requirements. Technically valid payment could be commercially unacceptable if it could impact bank relationships, breaches licence conditions or cause sanctions or AML exposure. Jurisdictions should be categorized as permitted, restricted or prohibited and use cases should be categorized as permitted, pilot-only or banned.

FX-restricted markets require a more nuanced frame than “stablecoins are a USD rail.” A high adoption rate could be a sign of low payment capabilities, exchange rate volatility, dollars, settlement speed, or the introduction of local-currency stablecoins in Nigeria. A key policy issue for a sovereign or a regulator is to either limit or regulate or get involved via safer local-currency digital rails. The policy question for corporate treasury is much more focused: Don't operate a shadow FX desk.

The policy shall include the requirement for local-law approval, clear pricing rules, conversion shall be required on an immediate basis if legal and operationally feasible and strict escalation shall be implemented if the transaction is deemed to be being made to exploit an FX spread. While customer pain points might be alleviated through the acceptance of Stablecoins, there is also the possibility of implicit USD exposure, tax uncertainty, capital-control risks and banking-risk consequences.

Privacy of transactions should be viewed not as a technical matter but as a treasury control one. If privacy is not built in from the ground up, it may be possible to infer counterparties, wallet relationships, when transactions happen, volumes, and settlement patterns and behaviour, even when the payment value is not sensitive. The issue at hand isn't whether the blockchain is public or private in general. The issue is how far can go the transparency of the business, how far can go the transparency of the wallet, how far can go the access control, how far can go the approved infrastructure and how far can go the screening and audit.

A good treasury model should be chain independent. If multiple approved payment networks can deliver the same payment goal, the company shouldn't rely on a single one, a single issuer, or a single technical payment route. Chain agnosticism provides greater flexibility for treasury in terms of cost, speed, liquidity, and resilience, and mitigates the risk of a single failure due to policy changes or congestion causing a disruption in the payment process.

The same goes for stablecoins. Treasury should be able to approve multiple stablecoins within a single system of controls, not create a system of controls around a single token. Support for multiple stablecoins simultaneously gives the company the flexibility to adjust to liquidity fluctuations, jurisdictional variations, issuer concentration risk, market access concerns and more — without altering the core control model. The idea is not to maximise choice of tokens. The objective is to maintain the continuity of operation whilst maintaining consistent timing and reporting of screening, reconciliation and conversion activities.

Where used, privacy tools should be subject to policy and legal, compliance and information security review. They must not undermine the effectiveness of sanctions screening, audit documentation, counterparty checks or record keeping. It's not a standard of hidden transactions, but selective disclosure; not a standard of uncontrolled opacity, but controlled access; not a standard of fragment operating practice, but flexible network choice.

6. Decision 4: adoption order

The adoption of stablecoins shouldn't start with the most complicated B2B movements. The best place to start is where the benefit is seen, transactions are not too large and terms can be easily enforced. The usual first test is usually a B2C, e-commerce or distributor collection, rather than the settlement of large supplier payments, long credit terms or documentary B2B settlement. The objective is to demonstrate wallet control, failed payment processing, refunds, customer validation, accounting entries, and conversion time and reconciliation before introducing the business to higher quantities of larger invoices or strategic supplier partnerships.

The order of adoption should also take into account the readiness of jurisdictional control. It is important to remember that Singapore, Hong Kong and mainland China are not an “Asia” block. The typical control ranking is Singapore first, Hong Kong second, and mainland China is a legally protected, regulator cleared structure. This ranking is not a market ranking, however, it is a control ranking.

Stablecoin regimes are evolving rapidly, so it is important that the stablecoin's regulatory status be verified right before the launch. The jurisdiction playbook ought to monitor such developments as Singapore's regime for digital-token service providers, Hong Kong's stablecoin licensing regime, mainland China's restrictions on public chains and specific EU MiCA treatment of stablecoins. The big takeaway is that the label of being “approved stablecoin” is not a worldwide one. The same token that might be acceptable in one jurisdiction may be unacceptable in another.

Adoption tier	Best initial use case	Why it is operationally sensible	Treasury guardrail
Tier 1: Singapore pilot	Limited B2C, e-commerce, distributor collections or controlled cross-border settlement.	Strongest fit for a controlled pilot because banking, custody, compliance and digital-payment infrastructure are easier to align.	Keep balances small, convert by rule, use approved custodians, produce daily reconciliation and monthly treasury committee reporting.
Tier 2: Hong Kong controlled expansion	Selective customer collections or regional treasury testing after Singapore controls prove stable.	Useful as a regional hub, but the treasurer should assume higher legal and licensing review before scale.	Proceed only after legal sign-off, bank confirmation, jurisdiction-specific compliance workflow and board-approved risk limits.
Tier 3: Mainland China restriction	Do not launch public-chain stablecoin receipts or payments as a normal treasury flow.	Operational, legal and banking uncertainty can outweigh payment benefits for ordinary corporate treasury.	Use conventional bank channels, approved RMB or cross-border payment structures, and regulator-cleared alternatives only.
FX-restricted markets such as Nigeria	Highly limited, exception-based use were legally approved and commercially necessary.	Stablecoins may solve customer pain points but can also create parallel-FX, sanctions, tax, and regulatory problems.	No use to bypass FX controls; require local counsel, pricing discipline, transaction caps, immediate conversion where allowed, and enhanced reporting.

Pilot, prove and scale is the order of learning. Treasury has a safer way to isolate wallet controls, customer validation, refunds, accounting, conversion windows and exception management from high-value supplier and credit-term complexity with B2C before B2B. Once the company has demonstrated the above, then it can start to think about higher value B2B flows.

7.The operating model a treasurer should build

The stability of a stablecoin programme needs more than a cryptocurrency wallet. It requires a common operating model, that's owned by treasury, finance, legal, tax, compliance, IT security and the business. Treasury needs to be leading as it has the advantage of liquidity discipline, cash forecasting, bank relationships and payment risk.

Operating layer	What the treasurer should define	Why it matters
Policy	Approved stablecoins, approved jurisdictions, approved wallets, permitted use cases, conversion rule, maximum balances, ageing limits, exception process, board reporting, and a clear statement that stablecoins are private payment instruments rather than public money or bank cash.	Prevents business teams from treating stablecoins as an informal workaround, cash substitute, or geopolitical shortcut.
Counterparties	Approved exchanges, custodians, banks, liquidity providers, market makers, payment processors and stablecoin issuers.	Reduces issuer, redemption, custody and off-ramp risk.
Transaction process	Invoice wording, customer wallet verification, payment reference, exchange-rate timestamp, screening, confirmation, booking and conversion.	Connects commercial activity to treasury control and audit evidence.
Controls	Segregation of duties, dual approval, address whitelisting, multi-signature release, access review, daily reconciliation and incident escalation.	Turns irreversible blockchain payments into a controlled corporate process.
Reporting	Daily balances, token ageing, fiat equivalent, conversion timing, exceptions, de-peg alerts, fees, yield opportunity cost and jurisdictional exposure.	Allows management to see stablecoins as part of liquidity risk, not a technology footnote.

The most significant policy line is the conversion rule. Any tokens received and not matched to an approved outbound stablecoin transaction during the approved operating-float window should be converted to fiat the same day or next business day, as per a good policy. Never accept, allow or approve tokens listed on unapproved token lists, wallets, jurisdictions, counterparties, float or ageing limits.

The company should clarify where the stablecoins are integrated into the system design. A weak model is based on screenshots and manual spreadsheets. A better model relates bank reconciliation to treasury management system, as well as payment processor or custodian to ERP. Customer invoice, blockchain transaction, wallet credit, conversion order and bank receipt should be connected to one another by a unique reference for each transaction. Three-way reconciliation and exception detection are now realistic controls – not features to be wished for.

Customer and vendor terms need to be updated. The company should clarify when payment is considered made, which stablecoins it accepts, who takes on the burden of network and conversion fees, what happens if the token de-pegs before the payment time expires, how the process is handled for a token refund and whether it will refuse tokens from unverified or high-risk wallets. Without these terms, treasury will have to deal with contractual issues that could have been addressed commercially.

8. Reporting: how stablecoins should appear in treasury and finance

Reporting on the implementation of stablecoins should be designed before go-live. Stablecoins need to be classified in a distinct liquidity and operational-risk group. They don't go away from risk reporting because they're associated with a fiat currency. Balances should be reported by token, legal entity, wallet, custodian, country and counterparty/ageing bucket at a minimum.

Useful dashboard has four elements, how much, how long, how fast can it be converted and what are the exceptions? A recent small fully screened token balance is an operating item with tested off ramps. A large balance, old balance, unscreened balance, de-pegged token or trapped restricted-market position is a risk to the treasury.

Report item	Frequency	Minimum content	Management question answered
Daily stablecoin balance report	Daily	Balances by token, wallet, custodian, legal entity, country, fiat equivalent, price versus peg and ageing.	Are we holding more token exposure than policy allows?
Conversion and liquidity report	Daily or weekly	Receipts, conversions, spreads, fees, failed conversions, settlement delays and bank credits.	Is the stablecoin rail delivering real liquidity or only apparent settlement?
Compliance exception report	Weekly and monthly	Blocked wallets, screening hits, high-risk jurisdictions, unresolved alerts and transactions awaiting compliance approval.	Are we accepting compliance risk faster than we can control it?
Yield opportunity-cost report	Monthly	Average balances, days held, estimated interest foregone, payment fees saved and net treasury benefit.	Does the payment benefit justify holding a non-yielding asset?
Board or treasury committee summary	Monthly or quarterly	Policy breaches, limits, jurisdiction exposure, cyber incidents, de-peg events, concentration by issuer and proposed expansion.	Should the programme be continued, capped, expanded or paused?

The distinction between receipt and cash realisation should be made when reporting. A stablecoin receipt can be used to pay a customer receivable without requiring the company to use bank cash for payroll, suppliers, taxes or debt service. If not converted or if there is no approved balance as operating float, the cash forecast should be separated into stablecoins and bank cash. This is particularly the case when bank cash buffers are used as a measure of borrowing capacity and of liquidity covenants or working-capital targets, rather than digital-asset balances.

This discipline is taught by a simple journal entry logic. Once the token is received, note the agreed fiat amount and only clear the receivable once the commercial and compliance conditions are fulfilled. Identify bank cash at conversion, record fees and difference in value. If it is a token to pay a payable, then record the transaction according to the approved fiat value at the time of payment. The accounting classification must be negotiated with the auditor but all the movements of the tokens should have a commercial transaction, a moment of valuation and a chain of evidence.

9. Practical implementation roadmap

A full implementation presents unnecessary implementation risk. A controlled pilot with a limited use case, with boundaries and measurable success criteria is a better option. The roadmap shouldn't start with designing a new technology. It should start with an economic baseline – the company must be able to establish whether the stablecoins are affecting the treasury's outcomes in a positive or a negative way, without a baseline.

Phase	Treasury actions	Success test
0-30 days: design	Define permitted use case, select token shortlist, obtain legal and tax review, choose custody and off-ramp partners, draft accounting policy, set limits, confirm that tokens will not be treated as public money or bank cash, and design the reporting dashboard.	Board or treasury committee approves policy; finance and audit agree treatment; no launch without documented controls.
30-60 days: pilot	Run low-value transactions in one permitted jurisdiction, reconcile daily, convert by rule, test address whitelisting, test blocked-wallet workflow and document every exception.	Transactions can be traced from invoice to wallet to conversion to bank statement without manual gaps.
60-90 days: reporting and stress test	Produce management reports, simulate de-peg, custodian outage, delayed conversion and compliance hit; review whether yield foregone is justified by payment benefit.	Treasury can prove that the programme remains within limits under stress.
90+ days: scale or pause	Expand only to approved use cases and jurisdictions; keep B2B for later; update contracts and ERP integration; review counterparty concentration and bank relationship impact.	Expansion occurs because controls worked, not because the technology was available.

Transaction count alone is not success. If reconciliation occurs late, the conversion spread is not consistent, controls only rely on a single employee or balances are not tested for yield opportunity cost, then that commercial pilot is not successful in the treasury. More successful indicators would be zero un-reconciled account balances, zero unauthorised wallets, conversion within the set time frame, zero policy violations, clear customer terms, zero un-resolved compliance alerts and positive net treasury value after costs and foregone yield.

10. Final judgement

When the stablecoins are integrated into the treasury control framework, they can be a valuable payment alternative for the companies' treasury. They should normally be reported as collections/cash movements, converted to fiat if they default, and be small and justified operating floats that should be reported separately from bank cash. The decision is NOT a crypto decision. It's a payment, liquidity, compliance, accounting, cyber and reporting choice.

The operating model should be structured around the TCMAG principles, not solely from a first principles approach. The new model is naturally compatible with Multi-Bank Architecture (Principle II), Unambiguous Accounting Treatment (Principle III), ERP Integration (Principle IV), Security (Principle V), Preservation of Control Frameworks (Principle X), Settlement Finality and Singleness of Money (Principle XI), and Operational Resilience and Liability (Principle XII). That's a signal that it's based on the baseline expectations of the corporate treasury community.

Multi-layered implementation: conversion first, liquidity management, accounting and audit evidence pre-agreed, wallet and custody security enhanced, screening for jurisdictions and counterparties, reporting yield opportunity costs, token-by-jurisdiction approval, and cautious approach to rollout, starting with lower-risk collections to more complex B2B flows. Treasury's role is not to impede innovation. To make sure that innovation does not supplant fundamental business discipline.

Every token needs to have a purpose, every wallet an owner, every transaction has an audit trail, every balance has a limit, every jurisdiction has a rule and every payment option has a reporting location, or a stablecoin programme should launch. That's where stablecoins go from the experimental phase into the realm of treasury-grade infrastructure.