Enterprise Treasury Management Systems (TMS), platforms like Kyriba, GTreasury, and FIS, are foundational software for global corporate finance. They have earned their position by solving genuinely complex problems: aggregating cash across hundreds of bank accounts, forecasting liquidity, managing FX exposure, and automating SWIFT-based payment workflows at scale.
As regulated stablecoins (USDC, EURC) mature into viable B2B settlement instruments, many of these TMS providers are extending their platforms to include digital asset visibility, allowing treasury teams to view stablecoin balances alongside traditional fiat positions. This is a natural and welcome evolution.
The question facing IT architects and CFOs today is not whether a TMS can display a USDC balance, but whether displaying a balance is the same as executing a stablecoin payment, reconciling gas fees, and writing the transaction back into the ERP General Ledger — all without requiring the AP team to change how they work.
What TMS Platforms Do Well
Established TMS platforms provide essential capabilities that DeSuite does not attempt to replicate:
- Multi-Bank Cash Aggregation: Consolidating balances from hundreds of global bank accounts via SWIFT MT940, BAI2, and host-to-host connectivity, giving treasurers a unified view of fiat liquidity across entities and geographies.
- Cash Flow Forecasting: Ingesting historical ERP and banking data to model multi-currency working capital requirements, seasonal patterns, and funding gaps.
- FX Hedging & Debt Management: Managing derivative portfolios, investment yields, and hedging positions — workflows that require deep integration with trading desks and capital markets.
- Digital Asset Visibility (Emerging): Several TMS vendors now offer dashboard connectivity to custody providers such as Fireblocks, enabling treasury teams to see USDC or BTC balances alongside their traditional bank positions. This is a valuable step toward a consolidated liquidity view.
The Gap: Visibility vs. Execution
Showing a stablecoin balance on a dashboard is fundamentally different from settling an invoice in stablecoins. This is where the architectural distinction matters.
The Workflow Question
In a typical TMS-based stablecoin workflow, a treasury analyst sees the USDC balance in the TMS dashboard, then switches to a separate custody interface (or API) to initiate the actual on-chain transfer. Once settlement confirms, someone must manually record the transaction (including the gas fee, the exchange rate at the moment of execution, and the blockchain transaction hash) back into the ERP. The AP clerk's existing Oracle Payables workflow is not involved.
This works. But it introduces a second system of record, requires manual reconciliation steps, and means the General Ledger is updated after the fact rather than atomically at the point of settlement.
The ERP-Native Approach
DeSuite eliminates this gap by embedding the stablecoin execution layer directly inside Oracle Fusion Cloud ERP. The AP clerk triggers a stablecoin payment from the same Oracle Payables workbench they already use for SWIFT or ACH. No new interface, no workflow change, no retraining. DeSuite handles the cryptographic signing via Zero-Possession MPC, executes the on-chain settlement, and writes the transaction hash, gas fee split, and exchange rate back into the General Ledger in real time using its proprietary Atomic Split™ protocol.
The result: Oracle remains the single system of record. The AP team's process does not change. The auditor sees one ledger, not two.
Comparative Architecture
| Capability | DeSuite Orchestrator | Established TMS (e.g., Kyriba) |
|---|---|---|
| Primary Strength | Real-time stablecoin settlement + ERP sync | Multi-bank fiat cash aggregation + forecasting |
| Stablecoin Visibility | Yes - via Oracle GL (single system of record) | Yes - via custody provider dashboard integrations |
| Stablecoin Execution | Native - triggered from Oracle Payables workflow | Requires external custody interface or API bridge |
| AP Workflow Impact | Zero. AP clerk uses existing Oracle payment workbench | Requires separate system for on-chain initiation |
| Gas Fee Reconciliation | Automatic real-time split via Atomic Split™ protocol | Manual post-transaction adjustment |
| Settlement Latency | T+0 (seconds) | T+1 to T+3 (via clearing networks) |
| GL Writeback | Atomic, at point of settlement confirmation | Post-facto, via bank statement reconciliation |
Conclusion: Complementary, Not Competitive
For enterprises managing complex global cash positions, FX hedging, and multi-bank connectivity, established TMS platforms remain indispensable. They are purpose-built for fiat treasury operations and continue to evolve their digital asset visibility capabilities.
DeSuite addresses a different layer of the stack: the execution of stablecoin B2B payments natively inside the ERP, with zero AP workflow disruption and real-time, audit-ready General Ledger reconciliation. For organizations running Oracle Fusion Cloud, the two can coexist — one managing your global cash position, the other settling your invoices on-chain without your AP team ever leaving Oracle.