SAP Pay — payments move into the ERP

What SAP announced

In October 2026 SAP introduced SAP Pay, a payments service embedded directly in SAP Cloud ERP. Instead of exporting a bank file to a separate processor, the system executes a supplier payment when the invoice is due and reconciles the transaction in the same workflow. SAP positions it as a way to reduce manual bank-file handling, reliance on external payment processing and reconciliation delays.

The service is operated by Tereina, a regulated payment-service provider backed by SAP, whose chief executive is Cedric Bru — the same executive who leads SAP’s working-capital business, Taulia. SAP Pay was unveiled alongside a set of finance AI assistants, with further agents for close, planning, treasury, billing, tax and receivables flagged for early-adopter programmes in the first quarter of 2027.

This piece is not a product review. The executive question is narrower and older than the feature: what does SAP gain, and what does the customer gain, when the payment-execution layer moves inside the ERP — and is this time different from the last time SAP tried to own that layer?

The documented facts

SAP’s own announcement is narrow and clear: in its words, SAP “is entering the payments market with SAP Pay, powered by Tereina, an SAP company,” and “embedded directly in SAP Cloud ERP, SAP Pay executes and reconciles payments within the same workflow.” That core — the service, its operator and the embedded execute-and-reconcile model — is confirmed by SAP’s primary text. The operational specifics below (rails, stablecoins, availability, corridors, cost) are not in SAP’s release; they come from press reporting and are attributed as such.

What it does. SAP Pay executes and reconciles payments inside SAP Cloud ERP, with automated reconciliation, fraud detection and multi-rail routing (the system selects the method for a given transaction). (press: CFO Dive, Payments Dive)
Which rails. Electronic funds transfers — automated clearing house, wires and cheques — plus stablecoin settlement for cross-border transactions. Notably, there is no support for credit-card payments in the announced scope.
Stablecoins. Circle’s USDC is the preferred stablecoin for eligible dollar payments and EURC for euro payments, with Circle’s Arc blockchain as the preferred chain for the initial workflows.
Availability. Generally available in the United States and the United Kingdom, across 89 payment corridors, subscribable under existing SAP contracts. A global networking and broadband distributor is cited as an early user for supplier and treasury payments.
Who runs it. Tereina, CEO Cedric Bru, a small team built over roughly two and a half years — most of it in the last 18 months — using AI coding tools. Tereina’s own claim is a payment-cost reduction of up to 25 per cent; Bru compares the model to Apple Pay.

Two facts remain unresolved and are not stated here as certainty. SAP’s own wording is simply “Tereina, an SAP company”; press reporting goes further and inconsistently — Reuters describes SAP as holding a stake of undisclosed size, while one SAP-guide-derived account calls Tereina a wholly owned subsidiary incorporated in April 2026. And the relationship, if any, between Tereina and Taulia beyond their shared chief executive is not established in any source. Where this briefing needs a label, it uses SAP’s: “an SAP company.”

The part worth the executive’s attention: this is SAP’s third approach to the money layer

The instinct to read SAP Pay as a payments launch misses the more useful pattern. For well over a decade SAP has returned to the same ambition — to own the layer between the enterprise and its money — and has approached it three different ways.

2012 — connect to the banks. SAP launched the Financial Services Network, a cloud corporate-to-bank layer for payments, reconciliation and remittances, co-innovated with tier-one banks and Visa. It targeted a real problem: host-to-host bank connections took months to stand up. The rollout was slower than planned, and the network never became the universal rail SAP described.
2022 — finance the invoice. SAP acquired a majority stake in Taulia, bringing working-capital tools — dynamic discounting, supply-chain finance, receivables — into the portfolio. Taulia kept its brand and its chief executive, Cedric Bru.
2026 — execute the payment. SAP Pay, through Tereina and with Bru again at the helm, does the thing the 2012 network stopped short of: it moves the money itself, from inside the ERP, across traditional rails and stablecoins.

Read in sequence — connect to banks → finance the invoice → execute the payment — SAP Pay is the point where payments come home to the ERP, and the leader of the working-capital business is the one carrying it across the line.

The counter-example: a network that chose not to move money

Not every industry platform reached for the payment layer. Elemica, the neutral business-to-business network founded by chemical majors at the turn of the century, built its position on the transaction and document layer — orders, confirmations, logistics across trading partners — and, on the public record, did not become a payment rail. That is the strategic fork in one picture: own the instructions and stay neutral, or own the execution and take on the money. SAP Pay is a decisive step towards the second; Elemica is the reminder that the first was a deliberate, defensible choice, not a failure to try.

The wider market is moving the same way

SAP is not alone. A July 2026 white paper from the US Faster Payments Council describes ERP systems evolving from financial-management platforms into “payment command centres” as instant payments, treasury and automation move into day-to-day workflows, and it cites Oracle and Microsoft Dynamics as platforms embedding payment capability directly. The wider ecosystem is doing serious work here; sapperment’s contribution is only the executive reading of what it means for an SAP estate.

The same paper makes the risk explicit, and it is the right place to be sober rather than enthusiastic: instant payments are often irrevocable, which raises the bar on fraud controls, authentication and stop-payment protocols. Moving execution inside the ERP concentrates both the convenience and the consequence in one system.

The executive decision

Embedding payment execution is attractive on paper — fewer bank portals, less manual upload, tighter reconciliation, more timely cash and liquidity visibility for the CFO and treasurer. The judgement is whether that convenience is worth consolidating the execution layer, its controls and its vendor dependency inside the ERP. Separate the vendor promise from the management decision with four tests.

1. Control and auditability, not just convenience

The claimed advantage is one workflow for execution, reconciliation, controls and auditability. Test it against irrevocable-payment risk: approval thresholds, segregation of duties, fraud detection, stop-payment and the audit trail have to be stronger inside the ERP than the bank-portal process they replace, not merely faster.

2. The economics, measured not asserted

“Up to 25 per cent lower payment cost” is the provider’s claim. The number that matters is yours: current cost per payment across rails, reconciliation effort removed, float and working-capital effect, against the subscription and the switching cost. No price belongs in the business case before that comparison exists.

3. Rail fit and the missing card rail

Multi-rail routing and stablecoin settlement are genuinely useful for cross-border flows. But the announced scope has no credit-card support, and your payment mix decides how much of the problem SAP Pay actually removes. Map your corridors and methods before assuming coverage.

4. Concentration and reversibility

Owning execution inside the ERP is lock-in by design. Ask what the exit looks like, how the stablecoin dependency (Circle, Arc) is governed, and whether treasury keeps an independent path. The 2012 network is the cautionary case: the ecosystem can decline to converge on a single rail.

Monday-morning questions

What is our fully-loaded cost per payment today, by rail — and what would SAP Pay actually remove?
Which of our payment methods and corridors does the announced scope cover, and which (cards, specific geographies) does it not?
Are our fraud, authentication and stop-payment controls strong enough for irrevocable, in-ERP execution?
Who owns the stablecoin decision, and what is our governance for settlement on a third-party chain?
If we embed execution now, what is the reversibility plan if the economics or the controls disappoint?

Executive takeaway

SAP Pay is best understood not as a new feature but as SAP’s third attempt to own the money layer — connect, finance, now execute — carried by the leader of its working-capital business. For the SAP customer the decision is not whether embedded payments are modern. It is whether the control model, the measured economics, the rail fit and the reversibility are strong enough to turn an embedded convenience into a durable advantage rather than a concentrated dependency.

Frequently asked questions

What is SAP Pay?

SAP Pay is a payments service embedded in SAP Cloud ERP that executes a payment when an invoice is due and reconciles it in the same workflow, across electronic funds transfers and stablecoin settlement. It is operated by Tereina, a payment-service provider backed by SAP.

How is SAP Pay different from earlier SAP payment efforts?

SAP’s 2012 Financial Services Network connected corporates to banks, and its 2022 Taulia acquisition financed invoices. SAP Pay goes further by executing the payment itself from inside the ERP. Whether that embedded model achieves the adoption the network did not is the open question.

Does SAP Pay support stablecoins?

Yes, for cross-border settlement, with Circle’s USDC and EURC as the preferred stablecoins and Circle’s Arc blockchain as the preferred chain for the initial workflows. Traditional rails — ACH, wires and cheques — are also supported; credit cards are not in the announced scope.

Is SAP Pay available everywhere?

No. At announcement it is generally available in the United States and the United Kingdom, across 89 payment corridors, and subscribable under existing SAP contracts.

Call to action

Use this briefing to frame the embedded-payments decision before your next finance-architecture or treasury review. For board-level framing and independent decision support, visit Executive Clarity.

Sources and evidence

SAP SE, “SAP Puts the Autonomous Enterprise to Work,” SAP News Center (press release), 6 October 2026 — SAP’s primary confirmation that it “is entering the payments market with SAP Pay, powered by Tereina, an SAP company,” “embedded directly in SAP Cloud ERP,” executing and reconciling payments “within the same workflow.” Corroborated by SAP’s feature “SAP Showcases the Autonomous Enterprise in Action,” 7 October 2026 (“an embedded payments service that can automatically execute and reconcile supplier payments once an invoice is approved”).
Reuters, “SAP-backed Tereina launches payment service inside SAP’s business software,” 6 October 2026 (development timeline, SAP stake, Bru quotes, cost-reduction claim).
CFO Dive and Payments Dive, “SAP expands into payments as finance automation push deepens,” October 2026 (rails, availability, AI-assistant roster).
Circle, press release on USDC/EURC and the Arc blockchain in SAP Pay, 7 October 2026.
US Faster Payments Council, white paper on ERP as a “payment command centre,” July 2026 (market context, Oracle and Microsoft Dynamics, irrevocable-payment risk).
SAP Financial Services Network coverage, 2012–2014 (Sibos announcement; bank and Visa co-innovators; slow rollout).
SAP acquisition of Taulia, announced January 2022, completed March 2022; Cedric Bru remained chief executive.

Source integrity note

SAP’s primary announcement has been retrieved and archived. It confirms the service (SAP Pay), its operator (“Tereina, an SAP company”) and the embedded execute-and-reconcile model inside SAP Cloud ERP. The operational specifics — payment rails, stablecoin settlement, US/UK availability, the 89-corridor figure, the up-to-25% cost-reduction claim and the Apple Pay comparison — are not in SAP’s own text and are attributed to the press and Circle sources above, not to SAP. Tereina’s precise ownership beyond “an SAP company,” and any formal relationship to Taulia, remain unconfirmed and are flagged as such. No prices are stated; no figure here is an independent sapperment measurement.

SAP Pay: when the payment itself moves into the ERP