Stablecoin Treasury Management: A Guide for Corporate Finance Teams

Stablecoin treasury management is the practice of holding, moving and accounting for fiat-pegged tokens such as USDC and USDT as part of a company's cash and liquidity operations, alongside its bank accounts. For corporate treasuries, the token works like a digital dollar that travels over a blockchain, whereas a bank transfer travels over a bank network.

It lets finance teams settle payments and move cash between entities outside banking cut-off times, with a live onchain record of every balance. That is why instant settlement and 24/7 liquidity are the two benefits treasurers cite most. The trade-off is that your balance sits with a token issuer, so policy, custody and accounting decisions come before the first payment.

You get the benefits, use cases with worked examples, the risks including compliance and accounting, a step-by-step rollout, allocation examples and the route for paying suppliers in India.

Stablecoin treasury management comes down to seven points:

• What changes - Transfers settle onchain in seconds to minutes on any day, and one balance can serve every entity, instead of waiting on bank cut-off times and prefunding.
• Where it fits - The strongest uses are cross-border payables, intercompany transfers, contractor payouts and a small yield sleeve, each with a worked example.
• Three risks decide go or no-go - Issuer and peg exposure, custody and key control, and the accounting treatment, which you settle with your auditors before the first balance.
• Rules are still moving - The GENIUS Act takes effect no later than 18 January 2027 with its rules not final as of 9 October 2026, and the FASB cash-equivalent proposal is open for comment until 19 November 2026.
• Start with a pilot - Run 90 days with a capped balance and an exit gate written before launch, so the decision to scale rests on measured results.
• Size the balance by need - Allocation follows your payables volume and bank access, and a startup and an enterprise land on different splits.
• India is a separate leg - If you pay Indian suppliers, the stablecoin converts outside India, INR is paid to the recipient's bank account, and a Foreign Inward Remittance Advice (FIRA) or eFIRA records the payment.

Stablecoins for corporate treasuries change when money moves, where liquidity sits, how cash is pooled and what each payment costs. Each change helps most where banks are closed, where entities sit in different time zones or where a payment crosses several banks before it arrives.

None of the four gains is automatic. Each one holds only while your treasury policy, custody set-up and accounting treatment keep pace with it, so pair every benefit with the control that protects it before you move real balances onchain.

Instant settlement that ignores banking cut-off times and weekends

Instant settlement means a transfer is final onchain within seconds to minutes on any day of the week, instead of waiting for a bank's cut-off time. Finality depends on the chain: Ethereum finalises in about 13 minutes, while Solana takes about 13 seconds.

A wire is fast on many routes, but it still stops at cut-off times, weekends and holidays, and the last bank in the chain decides when the beneficiary sees funds. For a closer look at the two paths, read stablecoin vs SWIFT.

Enterprise liquidity with stablecoins across entities and time zones

Enterprise liquidity with stablecoins means a parent can fund any subsidiary from one onchain dollar balance at any hour, without prefunding a local bank account in each country first.

A bank-account network ties cash to each country's banking hours and currency, so groups park idle cash in many places. One onchain balance reduces that trapped cash and gives treasurers a single view.

The limit is the edge: each entity still needs a way to turn the stablecoin into local currency. Treasury software vendors are adding support too, and Kyriba announced USDC support with Circle in April 2026 for intercompany payments.

Consolidated cash and programmable payment flows in one balance

Consolidated cash replaces many fragmented local balances with a parent wallet and sub-wallets that show the group position in real time. Programmable flows add rules on top: a smart contract or payment API can run recurring payroll, release escrow when a condition is met or sweep surplus cash back to the parent.

An illustrative rule: any subsidiary wallet above USD 50,000 sweeps to the parent at 18:00 UTC. Pair every rule with approval controls, because the cash still sits with an issuer.

Reduced FX and intermediary drag when you convert only at the edges

A payment over SWIFT or an ACH transfer passes from your bank through one or more banks in a correspondent banking chain to the beneficiary's bank, and each hop can add a fee and an FX spread. A stablecoin makes it one onchain transfer, converted to local currency only where it is received.

That reduced FX and intermediary drag is not free: on-ramp and off-ramp fees and spreads remain, but they sit at the two edges, where you can compare them. Network fees vary by chain and change with congestion, so compare them per chain.

Teams running stablecoin treasury management start with the workflows where bank cut-off times and prefunding hurt most. Four workflows come up most: supplier payables, intercompany transfers, payroll and contractor payouts, and idle cash. Each example is an illustrative scenario with round numbers.

Swap in your own volumes to check whether a workflow would clear your policy limits before it goes live. If a workflow needs a balance larger than your pilot cap, or a chain outside your whitelist, it waits for the next policy review rather than going live early.

Cross-border payables paid to suppliers outside banking hours

Cross-border payables are the clearest fit, because supplier due dates ignore weekends.

Illustrative worked example. A US company owes USD 120,000 to a supplier in Vietnam, due on a Sunday. By wire, it must send before Friday's cut-off or the money lands on Monday or Tuesday.

With stablecoins, accounts payable approves on Sunday, treasury sends 120,000 USDC on a low-fee chain, the supplier's off-ramp partner converts it to VND, and the payable clears on its due date. The supplier's wallet address is verified by a call-back before the first payment, then whitelisted.

Intercompany liquidity transfers and intraday rebalancing across subsidiaries

Intercompany liquidity transfers move cash between group entities without a prefunded account in each country. Intraday rebalancing means correcting a subsidiary's shortfall within the same day.

Illustrative worked example. A parent holds a USD 2 million onchain float. Its Singapore subsidiary needs USD 400,000 at 09:00 Singapore time to pay a vendor. The parent sends 400,000 USDC at once, without waiting for US banking hours, and the subsidiary converts it locally. Any surplus sweeps back the next day.

Global payroll and contractor payouts, plus team spend and expenses

Payroll and contractor payouts suit stablecoins when workers are spread across many countries and accept them. Worker classification and tax withholding do not change with the payment method.

Illustrative worked example. A company pays 50 contractors in 12 countries, USD 3,000 each on average, so USD 150,000 a month. Finance approves the payroll file once, a script sends the batch, and each contractor converts at their own off-ramp. Team spend and expense management on stablecoin-linked cards is a different product category and sits outside treasury.

Yield on idle balances, kept inside treasury policy

Yield on idle balances has two separate answers. Issuer-paid interest is barred: the GENIUS Act stops permitted issuers from paying holders interest solely for holding, using or retaining a payment stablecoin. Other yield is a different matter, covered in yield-bearing stablecoins.

Illustrative worked example. A treasury has USD 3.5 million idle for 60 days. It can leave the cash at the bank on the bank's terms, or place part in an approved tokenized fund if policy and investor status allow. Either way, the amount sits in a separate yield tier, away from the operating float.

Holding a stablecoin means holding a claim on an issuer, a position on a chain and keys you control. Each can fail, so stablecoin treasury management needs a control for each. Issuer, custody, compliance, accounting and reconciliation risks come first, and written risk limits tie them together.

Each one decides whether a pilot can start, so settle them with your auditors, your provider and your counsel before the first balance arrives.

Issuer exposure and peg risk, and how de-pegging happens

Issuer and peg exposure start from one fact: a stablecoin is only as good as the reserves and the redemption route behind it. De-pegging happens when holders doubt either.

In March 2023, Circle said USD 3.3 billion of USDC reserves, about 8% of the total, were stuck at Silicon Valley Bank. At its trough USDC traded at about 86 cents. It recovered after the backstop announcement on 12 March and returned to its peg once redemptions resumed on 13 March. Because it happened over a weekend, treasuries could not reach their banks for about two days.

Circle publishes monthly third-party assurance of USDC reserves under American Institute of Certified Public Accountants (AICPA) standards, and Tether publishes periodic attestations, so read the latest before you approve an issuer. Both issuers can freeze addresses, so price that operational risk in.

Custody, key management and operational controls for treasury wallets

Custody decides who can move the money. Your options differ in where the keys live and who enforces the rules:

• Multi-signature wallet - An onchain wallet needing M of N separate keys to sign, for example two of three. Approvals are visible onchain, and each signer holds a whole key.
• MPC custody - Multi-party computation splits one key into shares held by different parties or devices, so the key is never whole. It looks like one ordinary address, and the provider enforces your approval policy.
• RBAC controls - Role-based access control means initiators cannot approve their own payments, each role has limits, new addresses wait out a cooling period and every action is logged.
• Smart-contract and bridge risk - This applies only when funds touch DeFi or bridged tokens, and staying on issuer-native chains avoids most of it.

Compliance duties under the GENIUS Act, MiCA and sanctions screening

Stablecoin treasury compliance for a corporate holder runs mostly through your own AML and sanctions programme and your providers, because the new rules mainly bind issuers.

Three areas matter most:

• US GENIUS Act - Public Law 119-27 takes effect no later than 18 January 2027, and its rules are not final. It requires permitted issuers to hold reserves of at least 1:1 and publish monthly reserve reports.
• EU MiCA - The Markets in Crypto-Assets Regulation (MiCA, often written MiCAR) has applied to e-money tokens (EMT) since 30 June 2024, and the transition for crypto-asset service providers ended on 1 July 2026.
• Sanctions, AML and KYC - Screen counterparties and wallet addresses for sanctions, and run AML and KYC checks through your provider.

For the full rules by region, see stablecoin compliance.

Stablecoin accounting treatment under US GAAP and IFRS for corporate balances

Stablecoin corporate accounting starts with a classification question, and the answer is not automatic under US GAAP or IFRS.

Under US GAAP, ASU 2023-08 (Subtopic 350-60) applies fair value only to a crypto asset that meets all six criteria:

• Intangible - The asset meets the definition of an intangible asset.
• No enforceable rights - Criterion (b): it gives the holder no enforceable rights to or claims on underlying goods, services or other assets.
• Distributed ledger - It is created or sits on a blockchain or similar ledger.
• Cryptography - It is secured through cryptography.
• Fungible - Each unit is interchangeable with another.
• Not self-issued - It is not created or issued by you or a related party.

The ASU never names stablecoins, but a fiat-backed coin with a redemption claim generally fails the enforceable-rights test, so it usually sits outside fair-value crypto accounting. It applies to fiscal years beginning after 15 December 2024, so confirm the reading with your auditors.

The FASB has proposed changes that add guidance and disclosure but leave the definition alone.

Under IFRS, the June 2019 IFRIC agenda decision treats crypto-assets with no issuer contract as intangible assets (IAS 38) or inventory (IAS 2). A stablecoin with a redemption right is a different analysis, a financial asset (IAS 32, IFRS 9) rather than an intangible, so the answer turns on that right. Tax is a separate question for your tax adviser.

Reconciling onchain flows with ERP and corporate treasury systems

Reconciliation complexity is the friction treasury teams meet first. A wallet address is not a bank account, so balances never arrive in a bank statement. Each payment is a transaction hash plus a network fee paid in a different asset, timestamps are UTC block times against your period cut-off, and each chain is its own ledger.

Fixes are practical: map the invoice ID to the transaction hash in your payment tool, export onchain activity to the general ledger daily, and use TMS (treasury management system) connectors to your ERP. Compare tools by category: a TMS, an ERP and a wallet or custody platform.

How businesses manage treasury risk when using stablecoins

Businesses manage treasury risk when using stablecoins through written limits, each with a named owner. The figures here are illustrative:

• Issuer cap - No single issuer above 60% of the onchain tier, so one reserve failure cannot take the whole balance.
• Chain whitelist - Approved chains only, because each chain adds its own fees, finality and technical risk.
• De-peg trigger - A price below USD 0.995 for a set time pauses payments and converts to bank cash, with one named person holding the authority to pause.
• Fiat buffer - A minimum of operating cash kept in banks for payroll, taxes and bank-only suppliers.
• Approvers - A named initiator and approver for every payment, with dual approval above a threshold.
• Quarterly review - A scheduled policy check that also fires on a new regulation, an issuer attestation change or a volume jump.

Six steps take you from a policy on paper to a scaled programme, with a gate in the middle where you can stop:

1. Set objectives and write the policy.
2. Choose stablecoins, chains and custody.
3. Agree compliance and accounting with auditors.
4. Connect wallets to your ERP.
5. Run a 90-day pilot with a gate.
6. Scale entity by entity.

1. Set your objectives and write a treasury policy with hard limits

Pick the use cases you will allow, such as supplier payables or intercompany transfers, and name an owner, normally the CFO or treasurer. Write your risk limits into a treasury policy that covers:

• Approved issuers and chains - Only the coins and networks your team has reviewed.
• Custody and approvals - The custody model, signing roles and approval matrix.
• De-peg playbook - A named pause authority and a tested route back to bank cash.

2. Choose stablecoins, chains and a custody model for your treasury

Select each coin on reserve composition and attestation cadence, redemption rights, regulatory status, liquidity on your chain, freeze policy and network fees. Run a reserve attestation check before approval: read the issuer's latest attestation and reserve mix yourself.

Then choose chains, such as Ethereum, Base or Solana, from the Layer 1 and Layer 2 options, and a custody model, either a custodian, MPC or a multi-signature wallet. Keep the list short, because every extra chain adds a ledger.

3. Set compliance checks and the accounting treatment with your auditors

Agree the classification with your auditors before the first balance arrives. Bring the cash-equivalent policy question and the open FASB proposal, which takes comments until 19 November 2026. Then put three controls in place:

• Screening - KYB and AML checks on counterparties, and sanctions screening on each new address.
• Audit logs - A record of who initiated, approved and sent every payment.
• Accounting memo - A written classification that your auditors have reviewed.

4. Connect wallets to your ERP and treasury reporting

Link your wallets or custodian to your ERP and TMS so that balances, payments and fees land in the ledger without copying. Settle three things first:

• Invoice mapping - Each payment carries its invoice ID and transaction hash.
• Daily export - Onchain activity lands in the general ledger every day.
• Audit trail - A blockchain explorer link sits in each entry.

Report balances by issuer and chain, so your policy limits are measured against real balances.

5. Run a 90-day pilot with a clear go or no-go gate

Cap the pilot balance, for example at USD 100,000 to 250,000 (illustrative), and pick one route, such as a single supplier corridor. Track these measures against your wire baseline:

• Speed - End-to-end time from initiation to the supplier's local-currency credit.
• Cost per payment - Network, on-ramp, off-ramp and FX spread against wire fees and spread.
• Reconciliation breaks - Breaks per 100 payments and the hours needed to close them.
• Policy breaches - Limit or approval exceptions, with a target of zero.

Write the exit gate before launch. A go decision needs reconciliation breaks under your threshold, no unresolved policy breaches, better cost and time than the baseline, and sign-off from your auditors on the accounting memo.

6. Scale across entities and review the policy every quarter

Add entities one at a time, and let each new entity inherit the policy and its limits. Stablecoin treasury operations should run on the same approvals, reports and reconciliation in every entity.

Review the policy every quarter and whenever a trigger fires:

• Regulation - The GENIUS Act effective date or a final FASB standard.
• Issuer change - A change in an issuer's attestation.
• Volume - A jump in stablecoin payments.

Stablecoin treasury optimization is a sizing decision: how much stays in banks, how much earns yield and how much works as an onchain float. Both examples are illustrative and are not recommendations. Discuss any range with your auditors and bankers. Three questions drive the split:

• How much stays in banks? - Enough for payroll, taxes and bank-only suppliers.
• How much earns yield? - Only cash you will not need inside the policy horizon.
• How much works onchain? - A float sized to your stablecoin payables.

Example of a USD 10 million treasury split into buffer, yield and onchain float

In this illustrative example, a company with USD 10 million divides it three ways.

The split is illustrative, so read it as a template. The 50% onchain share is deliberately high, and your own number should follow the payables you will pay in stablecoins.

Re-run the split whenever your payables mix, banking access or regulation changes. Once the GENIUS Act's final rules land, for example, revisit your issuer shortlist and the share you hold with each issuer.

Keep the yield tier in regulated funds, away from DeFi lending, and keep it separate from the float so a fund restriction never blocks a payment.

Illustrative sizing example. Size the float from payables. If you expect USD 400,000 of supplier payments in stablecoins each week, a float of two weeks, USD 800,000, covers them with a cushion, and the rest of the onchain budget is a ceiling.

• Below one week of payables - Top up from the bank buffer or the yield tier, whichever your policy names first.
• Above four weeks - Sweep the surplus back to the tier it came from.

How the split changes for a startup versus an enterprise

Three drivers move the split: monthly burn, the share of vendors and customers abroad, and the banking access you have. The ranges are illustrative.

• Monthly burn - More months of cash needed in banks means a lower onchain share.
• Cross-border share - More vendors or customers abroad justifies a larger float.
• Bank access - Thin banking relationships push the float up, within your limits.

A startup cannot afford a de-peg that wipes out its runway, so it keeps a high floor. An enterprise holds a smaller onchain share but spreads it across issuers and chains, with the limits from your treasury policy applied tier by tier.

Illustrative worked example

• Startup, USD 2 million - USD 1.3 million (65%) stays in banks, there is no yield tier and USD 700,000 (35%) sits onchain for overseas contractors.
• Enterprise, USD 100 million - USD 80 million (80%) stays in banks, USD 12 million (12%) sits in an approved yield tier and USD 8 million (8%) sits onchain.

Illustrative quarterly review. At the quarterly review, a company finds its float held three weeks of payables, but one issuer now holds 70% of the onchain tier against a 60% cap. Treasury moves part of that balance to a second issuer, sweeps the surplus above four weeks back to the bank buffer, and records both moves in the policy log.

If you pay suppliers, teams or group entities in India, the stablecoin has to become INR before it reaches their bank account. Your treasury policy still applies on this leg: the same issuer cap, whitelist and approvals govern the stablecoin you send, whatever currency the supplier finally receives.

Before the first payment, tell your supplier which coin you will send and which bank account receives the INR, so both sides match the invoice, and whitelist the recipient and screen the counterparty for sanctions.

From stablecoin balance to INR in an Indian bank account

We help global businesses that hold USDC or USDT pay Indian recipients. You send USDC or USDT against an invoice, we convert it outside India, and INR reaches your Indian recipient's bank account.

Every payout comes with an eFIRA issued by an AD Category I bank. The service covers invoice-backed B2B payments only, and we are not an exchange or a route from INR into stablecoins. See our stablecoin payments for the product.

A recurring supplier invoice makes a good first corridor. Start there, measure speed, cost and reconciliation breaks against your wire, and widen to more suppliers once the numbers hold.

The rules for receiving these payments are covered in India off-ramp compliance.

Here is how one payment moves:

1. You link each payment to an invoice from your Indian supplier.
2. You send USDC or USDT for that invoice from your treasury wallet.
3. We convert the stablecoin outside India.
4. INR is paid into the recipient's Indian bank account.
5. An AD Category I bank issues an eFIRA for the payout.

Foreign Inward Remittance Advice (FIRA) and eFIRA for invoice-backed payments

A Foreign Inward Remittance Advice (FIRA) is the bank-issued document recording that money came into India from abroad, and eFIRA is its electronic form. For invoice-backed payments it ties the money received to the invoice.

Attach the FIRA or eFIRA to the payable in your ERP, so the audit trail runs from invoice to onchain transfer to INR credit.

Keep each FIRA or eFIRA with the invoice and the transaction record, because auditors ask for that trio later. It carries:

• Parties - The sender and recipient details.
• Amounts - The foreign currency amount and the INR credited.
• Purpose code - The code, set as per Reserve Bank of India (RBI) guidelines, that classifies why the money came in.

Before you pay, have three things ready:

• The invoice - It should match the amount and describe the goods or services being paid for.
• Recipient details - The legal name and bank account should match the invoice.
• The purpose code - Confirm it fits the invoice, so the FIRA or eFIRA states the payment correctly.

Decide the policy first: which issuers, which chains, who approves and where the limits sit. Then run a capped 90-day pilot, and watch two dates while you do: the GENIUS Act effective date and the FASB comment deadline.

To start this week:

1. Name the owner and the first use case, such as one supplier route.
2. Draft the treasury policy with issuer, chain and de-peg limits.
3. Book time with your auditors on the classification.
4. Set the pilot cap and write the go or no-go gate.

Share the policy with your auditors, banks and counsel before the pilot starts. Treasury management with stablecoins works best when each step is measured against the gate. If your suppliers include Indian businesses, add that leg after the first corridor runs cleanly.