---
path: /blog/corporate-treasury/
title: Stablecoins for Corporate Treasury
description: "A practical guide to stablecoin treasury operations: intercompany funding, liquidity controls, payment approvals, and reconciliation with existing finance systems."
image: /og/2026-q4/og_2026-q4_blog_corporate-treasury_title-image_v02.jpg
date: 2025-12-18
updatedDate: 2026-10-26
author: Tempo Team
label: Stablecoins
timeToRead: 10
heroTitle: Stablecoins for corporate treasury
faq:
  - question: Do I have to hold and manage stablecoins?
    answer: No. You can use stablecoins purely as a settlement rail without holding balances directly. Third parties can manage the stablecoins outside your organization, while your existing bank relationships remain central to day-to-day operations. Over time, you may choose to hold stablecoins directly and expand into other onchain assets such as tokenized treasuries.
  - question: Will my bank support this?
    answer: Bank and provider support varies by entity, currency, market, and payment direction. Confirm the sending and receiving accounts, supported assets, delivery rail, fees, and return process for the specific flow before funding it.
  - question: Who do I need to integrate with?
    answer: There are two common approaches. In a buy model, a provider supplies agreed parts of the payment stack. Establish its responsibilities for custody, wallets, connectivity, reporting, and fiat delivery. In a build model, you integrate those components directly. The right choice depends on your internal resources and required control. View Tempo's infrastructure partners to evaluate available components.
  - question: What about regulatory and audit concerns?
    answer: Establish the requirements for each entity, asset, counterparty, and jurisdiction before launch. Preserve approval records, provider evidence, confirmed transfers, and the accounting treatment used by your organization. Onchain records support that evidence trail; they do not establish that the entire workflow satisfies its obligations.
  - question: What are the risk considerations?
    answer: "The primary risks associated with stablecoin-based treasury flows fall into three categories: Counterparty and liquidity risk. Assess issuer exposure, redemption access, custody arrangements, and available conversion liquidity. Operational risk. Test signing controls, fee funding, delivery checks, reconciliation, and recovery after a failed or uncertain submission. Eligibility and jurisdiction risk. Confirm the requirements for the specific entities and flow. An intercompany transfer still needs this review."
  - question: How does this integrate with our ERP/TMS?
    answer: "Use an available connector or build an integration that maps verified payment records into your ERP or TMS. A typical flow looks like this: Payment instruction originates in ERP/TMS Instruction routes to a stablecoin infrastructure provider Settlement occurs onchain and delivery is verified Confirmation and settlement data flows back to TMS Accounting entries are generated automatically Preserve the network, transaction hash, and transfer log index so each transfer is recorded once. Your integration supplies the ERP or TMS mapping. See payment reconciliation for an example covering receivables, payables, and exceptions."
locale: en
canonical: https://tempo.xyz/blog/corporate-treasury/
---

# Stablecoins for Corporate Treasury

_Stablecoins add an onchain settlement rail to corporate treasury. Teams can move funds between supported accounts around the clock while retaining separate controls for custody, liquidity, fiat conversion, and bank delivery. To evaluate a treasury workflow, [contact Tempo](/contact/)._

Stablecoins and tokenized deposits are gaining traction in corporate treasury operations.

If your company operates globally, you're familiar with the constraints: money moves slowly across borders. A payment to a subsidiary might take days to clear. Cash collected in one region sits idle over the weekend while banks are closed. Exchange rates shift, fees accumulate, and your finance team operates on stale data.

Stablecoins add visibility into onchain balances and let teams transfer value between supported accounts outside banking hours. A treasury system still needs to combine those balances with bank, custodian, and payment-provider records.

## How stablecoins simplify corporate treasury management

Stablecoins address a common problem: cash sitting idle offshore while waiting for correspondent banks to settle payments, particularly over weekends or through slower local payment rails.

They enable 24/7 onchain transfers of dollar-denominated value. Converting into another currency or delivering funds to a bank account depends on the chosen providers, liquidity, and supported markets.

Large multinational companies are already [using stablecoins](https://techcrunch.com/2025/01/31/stablecoins-are-finding-product-market-fit-in-emerging-markets/) to move dollars between subsidiaries and offshore offices, improving cash efficiency and reducing settlement risk.

One in four CFOs [expect](https://ctmfile.com/story/corporate-treasurys-2025-crypto-turning-point-ignited-by-stablecoins) their treasury departments to engage with cryptocurrencies within two years. The practical questions: How do stablecoins fit into existing treasury operations? And how do they align with cost, risk, and resilience frameworks?

## The cost of settlement delays

For companies operating across multiple jurisdictions, correspondent banking can be complex. Treasury teams manage dozens of banking relationships, currencies, and cut-off times across time zones. This creates three problems:

- **Higher borrowing costs.** From trapped cash that cannot be deployed efficiently.
- **Suboptimal hedging.** Based on incomplete or delayed data.
- **Excess bank fees.** For accounts holding idle liquidity.

Despite access to real-time data elsewhere in the organization, treasury teams often rely on end-of-day reports from disconnected systems.

Some banks now offer tokenization services for instant fund movement between entities, but only within their own network. Stablecoins are used across banks and function more like cash.

## Stablecoins add a 24/7 settlement rail

Stablecoins can improve settlement speed and visibility between supported accounts. Treasury teams still need to establish which entities, assets, providers, and jurisdictions are eligible for their flow.

### Faster settlement unlocks working capital

Tempo provides near-instant onchain settlement with no re-orgs. Confirmed balances can inform cash positioning sooner, while provider holds, conversion, redemption, and bank delivery determine when funds can be used elsewhere.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_1.png)

### Onchain settlement simplifies reconciliation

For onchain transactions, payment and settlement occur as a single event. This creates a transparent audit trail and enables automated reconciliation, replacing manual processes.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_2.png)

### Available in underserved markets

Correspondent banking works well for G20 currencies. Stablecoins add the most value for businesses operating in currencies with limited banking infrastructure.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_3.png)

## How stablecoins fit into treasury operations

### Intercompany settlements

Stablecoins enable real-time settlement between parent companies and subsidiaries, or between subsidiaries. Instead of initiating SWIFT transfers, treasury teams move stablecoins between entities and settle against bank accounts on their own schedule.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_6.png)

### Cash positioning & forecasting

Stablecoins provide real-time visibility into global cash positions. Treasury teams can see liquidity across all entities regardless of time zone or banking hours, replacing end-of-day reports with current data for forecasting and liquidity management.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_4.png)

### International payouts

Stablecoins can change the settlement leg of an international payout. Recipients can receive a supported stablecoin directly, or a provider can convert it to local currency and deliver it through local rails. FX conversion, recipient eligibility, fees, and bank timing remain part of the latter flow.

![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_5.png)

## Current limitations

Stablecoins complement bank accounts rather than replace them. Key considerations:

- **Limited non-USD liquidity.** Stablecoins are predominantly dollar-denominated. EUR, GBP, and other major currency liquidity remains limited.
- **Off-ramping constraints.** Off-ramping to bank accounts is not available in all markets, though coverage is expanding.
- **Custody complexity.** Treasury teams must choose between self-custody and institutional custody, with implications for multi-signature controls, insurance, and internal governance.
- **Limited systems integrations.** Some blockchains require custom integration with treasury systems. Provider and network selection can simplify this.
- **Operational risk varies.** Assess issuer exposure, redemption access, custody, liquidity, and network dependencies separately. Reserve composition alone does not establish the risk of the complete treasury flow.

## Define the treasury operating model

Before moving funds, document where balances sit, who can authorize transfers, and how each entity records its position. These are recommended treasury controls to implement through your existing systems and chosen providers.

|Decision|Record before the pilot|
|-|-|
|Account ownership|Legal entity, network, token contract, account address, and custodian or wallet provider.|
|Signing and approvals|Who proposes, approves, and submits a payment; applicable limits and recovery procedures.|
|Liquidity|Required operating balance, payment and fee funding, redemption access, and bank-delivery dependencies.|
|Reconciliation|Business reference, confirmed transfer, internal ledger entry, and unresolved exceptions.|
|Recovery|How to investigate an unknown status, pause new submissions, and reconcile in-flight payments.|

For example, a parent company could pilot funding a subsidiary's approved account. Record the intercompany purpose and amount, validate the destination, obtain approvals, and submit the payment. The receiving entity verifies the delivered asset and amount before updating its ledger. If it needs local bank funds, that delivery is a separate stage to track.

Tempo's [account-model guide](/developers/docs/accounts/integration) distinguishes account ownership from signing authority. Its [sending guide](/developers/docs/guide/payments/send-a-payment) explains delivery verification, and [payment references](/developers/docs/guide/payments/transfer-memos) connect transfers to internal records. A platform API or wallet login does not replace the required payment authorization.

Keep operating liquidity separate from any investment allocation. Evaluate access, withdrawal terms, asset and provider exposure, and liquidity requirements before allocating funds.

## Reconciliation & operational risk considerations

Beyond speed and cost, treasury teams must evaluate how new settlement rails affect reconciliation processes and operational risk:

### Automated GL reconciliation

Fast settlement has limited value if finance cannot match it to the general ledger. [Tempo's TIP-20 memos](/developers/docs/guide/payments/transfer-memos) carry a 32-byte payment reference. Store detailed accounting and counterparty data offchain, then map the reference to your ERP or TMS record. The integration performs that mapping and posting; settlement alone does not create an accounting entry.

### Managing operational risk

Adding operational risk to working capital flows is not acceptable. Instead, start with a contained use case that delivers clear value (such as moving working capital in non-G20 currencies over weekends), then expand to other operations like short-term instrument allocation.

### Controls & auditability

Faster rails can weaken traditional approval and audit controls if implemented poorly. The mitigation is to enforce policy at the transaction layer, using programmable approvals and role-based permissions, so each movement of funds is pre-approved, attributable, and auditable end-to-end.

For multinational companies, stablecoins can deliver value now. The right provider, network, and implementation depend on your specific requirements.

## Key questions to answer

Before engaging providers, answer these questions:

- **What problem are you solving?** Identify your highest-value use case: reducing FX costs, accelerating intercompany transfers, or improving cash visibility in specific regions.
- **Which asset fits the flow?** Verify the exact token representation, issuer, contract, redemption terms, and provider support. Tempo's [stablecoin registry](/developers/docs/partners/stablecoins) identifies supported assets; ticker similarity does not establish compatibility across networks.
- **Manage internally or via third party?** Wallet setup, custody, and liquidity provider integration can be complex, so many companies outsource to infrastructure providers like Bridge, BVNK, or ZeroHash. Some, like Ant Group, build in-house.

By answering these questions, you'll be ready to define the value more clearly and begin to meet providers.

## Getting started

### Immediate actions

Faster, global treasury operations are within reach, but getting there requires a methodical approach that fits your organization:

- **Assess pain points.** Identify where cash is trapped, which corridors have the highest fees, and where settlement delays create the most friction.
- **Build a business case.** Map current costs against projected savings using your actual transaction data.
- **Talk to peers.** Other CFOs in your industry are evaluating stablecoins. Learn from their experience.
- **Engage infrastructure providers.** Request demos. Understand custody models, compliance tooling, and integration requirements.

### Work with Tempo

Our enterprise team can help you navigate the prospect of integrating stablecoins into your corporate treasury operations:

- Analyze your treasury operations to identify high-value use cases
- Model the business case with your transaction data
- Review integration requirements for your tech stack
- Design a pilot program tailored to your operational needs
- Connect you with companies that have implemented stablecoin treasury operations

Please [get in touch](https://tempo.xyz/contact) with us if you'd like to explore this use case with our financial services consulting and product teams.

## Frequently asked questions

### Do I have to hold and manage stablecoins?

No. You can use stablecoins purely as a settlement rail without holding balances directly. Third parties can manage the stablecoins outside your organization, while your existing bank relationships remain central to day-to-day operations. Over time, you may choose to hold stablecoins directly and expand into other onchain assets such as tokenized treasuries.

### Will my bank support this?

Bank and provider support varies by entity, currency, market, and payment direction. Confirm the sending and receiving accounts, supported assets, delivery rail, fees, and return process for the specific flow before funding it.

### Who do I need to integrate with?

There are two common approaches. In a buy model, a provider supplies agreed parts of the payment stack. Establish its responsibilities for custody, wallets, connectivity, reporting, and fiat delivery. In a build model, you integrate those components directly. The right choice depends on your internal resources and required control. View Tempo's [infrastructure partners](/partners/) to evaluate available components.

### What about regulatory and audit concerns?

Establish the requirements for each entity, asset, counterparty, and jurisdiction before launch. Preserve approval records, provider evidence, confirmed transfers, and the accounting treatment used by your organization. Onchain records support that evidence trail; they do not establish that the entire workflow satisfies its obligations.

### What are the risk considerations?

The primary risks associated with stablecoin-based treasury flows fall into three categories:

- **Counterparty and liquidity risk.** Assess issuer exposure, redemption access, custody arrangements, and available conversion liquidity.
- **Operational risk.** Test signing controls, fee funding, delivery checks, reconciliation, and recovery after a failed or uncertain submission.
- **Eligibility and jurisdiction risk.** Confirm the requirements for the specific entities and flow. An intercompany transfer still needs this review.

### How does this integrate with our ERP/TMS?

Use an available connector or build an integration that maps verified payment records into your ERP or TMS. A typical flow looks like this:

- Payment instruction originates in ERP/TMS
- Instruction routes to a stablecoin infrastructure provider
- Settlement occurs onchain and delivery is verified
- Confirmation and settlement data flows back to TMS
- Accounting entries are generated automatically

Preserve the network, transaction hash, and transfer log index so each transfer is recorded once. Your integration supplies the ERP or TMS mapping. See [payment reconciliation](/learn/payment-reconciliation/) for an example covering receivables, payables, and exceptions.

---

## Site links

- [Tempo home](/)
- [Privacy policy](/privacy-policy/)
- [LinkedIn](https://www.linkedin.com/company/tempo)
- [X](https://x.com/tempo)
- [YouTube](https://www.youtube.com/@tempo)

### Products

- [Earn](/earn/)
- [Routes](/routes/)
- [Zones](/zones/)

### Solutions

- [Agentic payments](/solutions/agentic-payments/)
- [Credit](/solutions/credit/)
- [Cross-border payments](/solutions/cross-border-payments/)
- [Institutional settlement](/solutions/institutional-settlement/)
- [Stablecoin accounts](/solutions/stablecoin-accounts/)
- [Tokenized deposits](/solutions/tokenized-deposits/)

### Developers

- [Documentation](/developers)
- [Tempo Explorer](https://explore.tempo.xyz/)
- [Tempo API](/developers/docs/api/)
- [Performance](/developers/performance)
- [Status](https://status.tempo.xyz/)
- [GitHub](https://github.com/tempoxyz)

### Resources

- [Blog](/blog/)
- [Customers](/customer-stories/)
- [Learn](/learn/)
- [OUSD](/ousd/)
- [Partners](/partners/)
- [Reports](/reports/)
- [Stablecoin Advisory](/stablecoin-advisory/)

### Company

- [About](/about/)
- [Careers](/careers/)
- [Brand kit](/brand/)
- [FAQ](/faq/)