Circle and Tereina announced a partnership on October 7th, planning to integrate USDC and EURC into an enterprise workflow centered around SAP. Tereina is a company supported by SAP; the focus of their discussion is on making digital currencies more accessible in corporate payment and fund management processes, rather than declaring that stablecoins have been widely adopted by businesses worldwide. The press release mentions background figures such as "the SAP ecosystem handling 84% of global business transactions," which refer to the commercial coverage of SAP software, not the proportion of stablecoin transactions. Presenting these figures alongside the adoption rate of stablecoins would create an impression that is far from reality.
Only after integrating with the business system can we discuss changing the payment method.
There is a significant difference between corporate payments and personal transfers. When a company pays its suppliers, there are typically steps such as purchase orders, invoices, budget approval, and verification of the recipient's information before proceeding to payment, reconciliation, taxation, and auditing. Funds can be transferred quickly on the blockchain, but these steps cannot be automatically completed. The value proposition of the collaboration between Circle and Tereina is precisely to try to make stablecoins not just remain in independent wallets, but to be initiated, recorded, and verified within existing corporate processes. If employees still need to manually copy data from ERP to the trading platform, any potential increase in efficiency may be offset by new operational risks.
According to the announcements from both parties, the relevant capabilities are connected to the SAP Pay ecosystem, and there are plans to advance joint proof-of-concept projects in the coming months. It is important to distinguish between three states: products that are available for exploration, certain components that can be integrated, and full-scale production with large enterprises. The purpose of the proof-of-concept is to identify obstacles in actual transactions, such as how to complete identity and sanctions screening, how to manage accounts of various entities, how to comply with payment rules in different jurisdictions, and how to reflect stablecoin balances in financial systems. Describing the planned pilot as "all SAP customers have already settled using USDC" is not only inaccurate but can also mislead companies about the implementation timeline.
USDC and EURC correspond to US dollars and euros respectively, which theoretically provide new options in multi-currency fund allocation. However, what enterprises really care about is not the number of token symbols, but whether the payments reach the designated legal entities, whether qualified vouchers can be generated, who bears the exchange and handling fees, and whether abnormal transactions can be intercepted or remedied. Cross-border payments also face the issue of whether the recipient is willing to hold stablecoins. If suppliers ultimately only accept the local currency in their bank accounts, chain transfers will still rely on conversion and local payment channels afterward, so the overall cost and speed of the entire blockchain system must be calculated end-to-end.
For financial officers, whether a new payment tool can be adopted by a company often depends on internal controls. Who has the authority to create payment recipients, who approves transfers, who can adjust limits, who manages private keys or custodial accounts, and how the permissions of departing employees are revoked—these aspects may not seem like highlights at a press conference, but they determine whether the system is actually usable. Once stablecoin transfers are initiated, the methods for correcting errors may differ from those of traditional bank payments; therefore, separation of permissions, address whitelists, and pre-verification procedures are often more valuable than just a few minutes faster processing time for individual transactions. New settlement processes must be integrated into the existing chain of responsibilities, rather than bypassing it.
In the next phase, it will depend on whether auditable evidence can be preserved.
The cooperation announcement itself proves that the two companies share a common product direction, but it does not prove that they have already achieved scaled revenue. The most convincing evidence in the future will come from pilots with clear industries, specific types of enterprises, and verifiable metrics: by how much has the payment completion time been reduced, what is the failure rate, how much has the manual reconciliation work been decreased, and how do the overall costs compare to traditional channels? Providing just one on-chain hash or a demonstration interface is not sufficient to indicate the success of the entire process; enterprises are more concerned with whether the financial statements, audits, and supplier experience can all be closed-looped together.
The entry of stablecoins into ERP may also change the competitive landscape among service providers. Banks and traditional payment companies will not withdraw just because a new channel appears on the blockchain; instead, they may continue to play a role in compliance, cash management, and local settlement. Circle possesses the issuance and payment networks, while Tereina understands the SAP processes. Banks, as well as custodian and exchange partners, undertake other key aspects. Whether a solution that can be continuously used by enterprises can be formed ultimately depends on whether these parties can clearly divide the work and jointly ensure the quality of service, rather than one party claiming to solve all problems on its own.
As of now, the most reliable conclusion is that Circle and Tereina have announced a partnership, and they are advancing integration and proof-of-concept efforts surrounding companies related to USDC, EURC, and SAP. There is no evidence to suggest that the majority of commercial transactions in the SAP ecosystem have shifted to stablecoins. The reason to pay attention to this development is that business scenarios have finally moved the discussion from "transfers completed in seconds" to whether "invoices, approvals, settlements, and reconciliations can be integrated." What is worth tracking next is not the largest market figures mentioned in the partnership announcements, but rather actual customer cases, the volume of real payments, failure and error correction mechanisms, and how all parties can demonstrate that these processes are robust enough.
For enterprises preparing to pilot, a more cautious starting point is to choose payment scenarios with stable transaction relationships and controllable amounts and frequencies. First, establish a baseline for the time and costs of traditional channels, and then record the differences in the process for stablecoins on a case-by-case basis. This way, even if the pilot does not yield the expected benefits, it will be possible to determine whether the bottleneck lies in on-chain settlement, exchange, bank account entry, or internal approval processes. Without a baseline, a pilot project may only result in a demonstration that shows technical feasibility, but it will not provide answers as to whether it is worth investing in system modifications.
