SAP started selling payment execution inside SAP Cloud ERP on October 6, and three outlets that covered it came away with three different stories: a product from a separate company, a feature with a fraud-control bill attached, and a challenge to the bank portal. All three are partly right. What none of them settles is who ends up holding the authorization record when software, not a person at a bank site, releases the money.
What SAP and its partners actually announced
SAP’s own announcement, issued at its SAP Connect event, says the company “is entering the payments market with SAP Pay, powered by Tereina, an SAP company.” The service is embedded in SAP Cloud ERP and, per SAP, executes and reconciles payments within the same workflow when an invoice is due. SAP says the aim is to reduce manual file handling and dependence on external processing while giving customers more control.
The detail comes from the trade press. Payments Dive reported that SAP Pay supports ACH payments, wires and checks, plus stablecoin-based settlement for cross-border transactions, and is generally available in the United States and the United Kingdom. It also reported that a global distributor of networking and wireless broadband solutions already uses the service for supplier and treasury payments. SAP did not name the company.
Advertisement
A day later, Circle and Tereina announced a partnership. In Circle’s release, USDC is the preferred stablecoin for eligible dollar-denominated payment workflows and EURC covers euro activity. The release says the integration is available to SAP customers through SAP Pay. It also says the two companies plan joint proof-of-value programs with customers “over the coming months,” which places stablecoin use at an earlier stage than the card, ACH and wire rails.
Three accounts, three different stories
Reuters: a payments company that happens to live inside SAP
Reuters, in a version carried by KFGO, led with Tereina rather than SAP: “a payments company in which SAP owns a stake” that launched technology letting businesses pay suppliers, employees and affiliates from their SAP software in traditional currencies or stablecoins. Tereina CEO Cedric Bru told Reuters that until now SAP had stopped short of payments and let customers connect their own providers, and declined to disclose the size of SAP’s stake. Reuters added that customers can subscribe to SAP Pay under existing contracts, that Bru compares the offering to Apple Pay, and that Tereina partners with other payment providers rather than competing with them. It also passed along Tereina’s claim of a 25% cut in payment costs, which is the company’s own figure and not an independent measurement.
Reuters’ emphasis is commercial structure: the product is described as Tereina’s, with SAP as a shareholder, and Tereina is described as a partner to existing payment providers.
Payments Dive: a finance-automation feature, with a risk caveat
Payments Dive treated SAP Pay as one item in a wider finance-automation push. It reported the launch alongside new AI assistants for pricing and financial disclosure, with more specialized agents planned for financial close, planning, treasury, billing, tax and receivables management, and early adopter programs for the assistants planned for the first quarter of 2027. David Imbert, head of finance product marketing at SAP, told the outlet: “This will basically give our customers access to a wide variety of payment methods, whether it’s old-fashioned bank transfers or stablecoin transactions”.
The outlet’s own analysis pointed somewhere else. It cited a July white paper from the U.S. Faster Payments Council, which describes ERP systems becoming payment command centers and notes that Oracle and Microsoft Dynamics already integrate payment capabilities. The same paper warns that some instant payments are irrevocable, so companies need stronger fraud controls, authentication frameworks and stop-payment protocols. Payments Dive’s emphasis is therefore the control burden that travels with convenience.
PYMNTS: the bank portal loses the interface
PYMNTS framed the launch as a contest with banks. An ERP, it argued, already knows what a company owes, when it is due, who approved it and how it should be recorded, so a system that can initiate payments moves the bank “one layer down the corporate finance stack.” The outlet put the competitive question as who owns the interface through which the CFO decides what happens to the money. It was explicit that banks keep deposits, credit and regulated payment access, and it noted that J.P. Morgan and ING already sell APIs that let companies initiate payments from ERP and treasury systems, while Oracle’s embedded banking connects Fusion Cloud ERP with participating banks.
PYMNTS also made the most forward-looking claim of the three: that AI could turn the choice of payment rail into a background decision made by the system.
Where the accounts agree, and where they pull apart
They agree on the mechanism. Each describes payment execution and reconciliation happening in the same system that holds the invoice and the approval. Reuters quotes Tereina’s CEO saying SAP had until now stopped short of payments, and PYMNTS notes that Oracle already offers embedded banking and virtual-card programs.
They differ on who the counterparty is. Reuters points to Tereina’s partner posture toward other payment providers. PYMNTS points to banks, though it keeps banks in the picture as infrastructure. Payments Dive points to the customer’s own fraud and approval controls. Those are three readings of one product, and the evidence in the primary documents supports each of them in part.
They also differ on stage. Reuters says businesses can pay in stablecoins as of the launch. Payments Dive says stablecoin settlement covers cross-border transactions. Circle’s release describes an integration available through SAP Pay and, in the same document, customer proof-of-value programs still to come. A reader who takes only the Reuters line could assume a production stablecoin flow. The Circle release supports a more careful reading.
What the coverage adds up to (our read)
This section is our interpretation, not a finding from any of the three outlets.
The common thread is a move of the approval point. Today at many companies the ERP produces a payment file, and someone then carries it to a bank site. SAP Pay, as SAP describes it, collapses that into one workflow. The Faster Payments Council paper is blunt that older ERP designs assumed batch cycles and delayed postings, and that finance teams fill the gap with flat-file uploads, banking portal logins and manual reconciliation. A product that removes those steps can remove a human checkpoint along with a delay.
That is why the three framings are compatible. If the ERP releases payments, the vendor needs a licensed payments partner (Reuters’ point), the bank loses some visibility into the decision (PYMNTS’ point), and the customer inherits the fraud and stop-payment design (Payments Dive’s point). The competitive story and the control story are one story told from two sides.
It also explains why the earlier moves on this site look related. We covered BMO and Mastercard embedding virtual card payments in ERP software, and made the case in an opinion piece that payments firms are moving upstream to where the payment starts. The ERP is the most upstream point there is for business-to-business payments, because it is where the obligation is created.
The gap in all the coverage is evidence. The only adoption data point is one unnamed distributor. The 25% cost reduction is Tereina’s claim. The Circle programs are planned. Nobody has published how many SAP customers will switch on payment execution, how many will keep their own providers, or how often a payment released from inside the ERP will be reversed or disputed. Until those numbers exist, the sources support a change in architecture and show no change in behavior yet.
What it means for the finance leader
For a CFO or treasurer running SAP, the practical questions are narrower than the trade-press framings.
- Provider choice. Reuters reports that customers can subscribe to SAP Pay under existing contracts and that Tereina partners with other providers. Ask whether your current payment providers and banks connect to it, and on what terms.
- Approval design. If payments execute when an invoice is due, check who can change the due date, the payee record or the approval threshold, because those fields now sit one step from the money.
- Irrevocable payments. The Faster Payments Council paper flags stop-payment protocols. Find out which rails in your configuration can be recalled and which cannot.
- Stablecoin scope. Treat the stablecoin option as a pilot decision. Circle’s own release describes proof-of-value work still ahead.
- Evidence of savings. Ask Tereina or SAP for the basis of the 25% payment-cost figure before it goes into a business case.
Source: SAP News Center
