Tereina and Circle bring stablecoins into ERP workflows

A supplier invoice, its approval and the payment could sit within one workflow. On 7 October 2026, Tereina and Circle announced USDC and EURC integration, beginning with SAP Cloud ERP. Eligible customers can access it through SAP Pay, with customer proof-of-value programmes planned.

Put the stablecoin beside the obligation

The most interesting feature is where the payment option appears. Treasury can start with an existing business transaction rather than a separate crypto interface. That potentially changes who participates in the decision: accounting, procurement and ERP process owners become involved alongside the payment team.

The announcement positions USDC for dollar workflows and EURC for euro activity. Currency selection is therefore connected to the company's obligation. If a supplier needs to receive euros, the invoice currency and receipt terms should determine the economics of the route, rather than the prominence of a particular digital asset.

Where operating work might disappear

Consider a recurring payment to an overseas contractor. Some of the delay may occur before transmission: staff verify details, match an approval to a document and collect accounting evidence. An integration that reduces that manual work can demonstrate value even with a relatively small payment sample.

A meaningful demonstration therefore begins with the invoice and ends with a closed payable. It should show how the transfer identifier connects to the document, who approves the instruction and what happens to a partial refund. These are evaluation criteria, not additional features claimed for the announced product.

There is a clear limit to the proposition. Execution speed cannot compensate for unclear records. If staff must reconstruct a balance manually from several systems, new technology may increase the workload. When the whole history remains accessible within the working process, digital settlement can become a manageable everyday operation.

That is the substantive question for this partnership: how naturally will the new payment rail fit into the finance team's decisions, execution and daily accounting?

What treasury and ERP teams should check

Before joining a pilot, it is worth documenting the existing process as carefully as the new one will be documented. The comparison then becomes fair: not an old bank against new technology, but specific steps, timing and manual effort for the same type of payment.

• Which suppliers are willing to accept digital dollars or euros, and how they convert the funds back to fiat.
• Who approves such transactions, and whether that chain matches current payment-approval rules.
• How the transaction is recorded: exchange rate, fees, expense recognition date, closure of the payable.
• Which internal-control and audit requirements apply to holding and transferring digital assets.
• What happens after an error in payment details, a partial refund or a dispute with the supplier.
• Which pilot metrics define success: time from approval to closure, number of manual corrections, route cost.

Risks and limitations

The legal treatment of stablecoin settlement varies by jurisdiction and may depend on the status of both payer and recipient. That is a question for the company's legal and compliance functions, not only for the payments team. Operational risk deserves separate review: wallet access, segregation of duties and error recovery need the same formal procedures as bank payments. Without them, time saved on settlement can easily be lost again in reconciliation and exception handling.