SAP Pay executes supplier payments inside Cloud ERP through Tereina

SAP has entered the payments business. On 6 October the company announced SAP Pay, a service that executes and reconciles supplier payments directly inside SAP Cloud ERP rather than handing them off to bank portals, payment files or middleware. The service is operated by Tereina, a payment provider SAP describes as a regulated, wholly owned subsidiary founded in April 2026, according to a detailed analysis on dev.to.

For most SAP customers the payment flow has long ended the same way: an invoice is approved in SAP, and the money moves elsewhere — a bank portal, a file transfer, a middleware box, then a reconciliation job the next morning. SAP Pay removes that handoff. Once an invoice is approved, the service can execute the payment and automatically match it back to the originating invoice or purchase order.

What the service covers

According to SAP, SAP Pay supports traditional rails including ACH, EFT, wire, check and real-time payments, alongside stablecoin payments in USDC through a native integration with Circle. SAP claims intelligent routing selects the rail across more than 40 currencies and 89 global corridors without requiring per-country bank setup. Bank communication runs through SAP Multi-Bank Connectivity, which SAP says the new service complements rather than replaces.

SAP also states that OFAC and KYC/AML screening applies to every transaction, that no payment moves without customer approval, and that payments follow existing SAP workflows.

Pricing is a subscription tied to transaction volume, sold in blocks of 1,200 transactions per year on one- to three-year contracts with automatic renewal; prices are on request. Data centers are listed in US East and Frankfurt. SAP's announcement says the service is generally available now in the United States and the United Kingdom.

Where the sources disagree

The dev.to write-up flags three gaps in the public material.

Ownership: SAP calls Tereina a wholly owned subsidiary, but Reuters describes it as a payments company in which SAP holds a stake, and reports that Tereina's CEO declined to disclose the size of that stake.

Geography: SAP's news release says the service is generally available in the US and UK, while the pricing page says it may only be used for transactions by customers or affiliates domiciled in the United States or the European Union unless the documentation provides otherwise.

Savings: Reuters reports that Tereina claims a 25% cut in payment costs. That figure is a vendor claim, not a measured result, and customers have no public model or references behind it yet.

Agents are next

SAP's own page indicates the finance agents that support teams through Joule will soon be able to trigger and execute payments as well, collapsing decision and execution into a single step. Reuters quotes Tereina's CEO saying SAP previously left payments to customers' own connected providers, and likens SAP Pay to Apple Pay — a payment option built into the platform customers already use.

What finance teams should ask

When approval directly triggers execution, the approval step becomes the control. The dev.to analysis stresses classic separation-of-duties questions — who can create a vendor, change its bank details and approve its invoice — which matter more when nothing sits between approval and money leaving the building. Vendor bank-detail changes in particular become higher risk, since payment fraud that starts with a swapped account travels faster through a direct flow.

Teams should also confirm which entity and licence covers the service in each country, obtain the funds flow in writing (who holds funds between instruction and settlement, and what happens if the provider fails), settle treasury and audit policy for stablecoin settlement before the first USDC payment, and negotiate an exit route back to direct bank connections into the contract.

Why it matters

SAP Pay relocates a critical piece of finance infrastructure — the movement of money itself — from external systems into the ERP. Layers that other vendors sell today, such as separate banking platforms, file transfers, third-party middleware and post-payment reconciliation, get folded into a single flow run by a provider SAP owns, or partly owns. Fewer intermediaries means fewer opportunities for manual review to catch an error, and fewer independent checkpoints in the payment path. With Joule agents scheduled to trigger payments next, the combination of ERP, AI agents and payments from one vendor is convenient, and concentrates operational and counterparty risk in a single place.