SAP Pay In-Depth: How Embedded Payments in ERP Are Reshaping Financial Controls

SAP has long operated with a default boundary: invoices are approved inside the system, but money moves outside it. Bank portals, payment files, middleware, next-day reconciliation—these constitute the "last mile" that finance teams know well. SAP Pay attempts to pull that stretch of the journey inside Cloud ERP. The significance here isn't that there's one more payment button; it's that the buffer zone between approval and funds outflow is being redesigned.

What SAP Pay Confirms

According to SAP's official product page and press release, SAP Pay is a B2B payment solution embedded in SAP Cloud ERP: once an invoice is approved, the system executes payment directly and automatically reconciles it to the original invoice or purchase order. The operator, Tereina, is described by SAP as a regulated payment service provider and a wholly owned SAP subsidiary.

Payment rails cover ACH, EFT, wire transfer, check, and real-time payments, with native integration of Circle's USDC stablecoin payments. SAP says smart routing can select rails across more than 40 currencies and 89 global corridors, eliminating the need for per-country bank connections. Bank communication runs through SAP Multi-Bank Connectivity, and SAP explicitly states that SAP Pay does not replace it. On compliance, every transaction undergoes OFAC and KYC/AML screening. Pricing is a volume-tiered subscription, with each tier at 1,200 transactions per year, contract terms of 1 to 3 years, auto-renewal, and specific pricing available on request. Data center options are US East and Frankfurt. SAP's press release states it is generally available in the US and UK.

Multi-Bank Connectivity is SAP's bank communication network service for enterprise customers, used to securely transmit payment instructions, bank statements, and cash management messages (such as SWIFT MT/ISO 20022 formats) between ERP and multiple banks. It is essentially a "pipe" responsible for connectivity and message transformation, but it does not hold funds, execute clearing, or perform payment compliance screening. SAP Pay layers payment execution, sanctions and KYC/AML screening, and reconciliation write-back on top of it. Understanding this layering is critical: SAP explicitly states that SAP Pay does not replace Multi-Bank Connectivity, meaning enterprises can retain their existing bank connection contracts and integrations—which also forms the technical basis for later reverting from SAP Pay to a self-built payment path.

Why This Is a Bigger Move

Reuters quotes the Tereina CEO as saying SAP previously "stopped before payment, letting customers connect to payment service providers themselves." SAP's own page lists the costs of the old approach—standalone banking platforms, file transfers, third-party middleware, post-payment reconciliation. These are precisely the layers other vendors sell, and SAP now chooses to fold them into ERP.

More telling is a statement on the product page: the Joule AI agent supporting finance teams "will soon also trigger and execute payments, closing the loop from decision to execution within a single process." This means the manual gate between approval and payment may in the future involve agent participation. For financial control systems, this is where rules need to be designed in advance.

Joule is the generative AI assistant SAP embeds in its cloud products, executing queries and actions across SAP applications through natural language interaction. The "agent" mentioned refers to an AI agent with a degree of autonomous action capability, able to proactively initiate process steps within authorized scope rather than merely answering questions. The industry typically manages such capabilities using an "autonomy ladder": from read-only queries, to drafting recommendations, to execution after human confirmation, to fully automated execution. Where payment release authority sits on that ladder determines the maximum loss when the agent errs. Finance teams should define amount thresholds, supplier whitelists, exception escalation paths, and human review triggers before the agent goes live, and retain complete audit logs of agent actions.

Three Discrepancies Between Official Statements and Reuters Reporting

First, ownership structure. SAP calls Tereina a wholly owned subsidiary, while Reuters describes it as a payment company in which SAP "holds a stake," with the CEO declining to disclose the ownership percentage. This directly affects judgments about the operator's control and where risk resides; written confirmation of the legal structure should be required.

Second, availability regions. The press release says generally available in the US and UK, but the pricing page states the service may only be used for transactions of customers and affiliates located in the US or EU unless documentation states otherwise. Where it can actually be used needs to be confirmed with SAP.

Third, savings claims. Reuters reports that Tereina claims a 25% reduction in payment costs—a claim, not a result. Request the calculation model and customer references with similar payment structures.

Seven Questions Finance, Treasury, and Audit Should Ask

1. "Approval" Now Means "Payment"

When approval directly triggers execution, the approval step itself is the control point. Who can approve? Can the same person create a supplier, modify bank information, and approve an invoice? Separation-of-duties issues get amplified when there's no buffer between approval and funds outflow.

2. Supplier Bank Change Risk Rises

Payment fraud often starts with a change of bank account. With approval wired directly to execution, an erroneous bank information change travels faster. Callback confirmation on master data and dual-approval rules need to be treated with the same seriousness as payment rules.

3. Whose License Covers What

A regulated payment provider holds specific licenses in specific regions. Ask clearly: which entity, which license, which country. Public materials currently point to the US and UK, while the pricing page points to the US and EU.

4. Where Do Funds Stop, and for How Long

Require a written explanation of the funds flow: which accounts are involved, at what points in time, who holds funds between instruction and settlement, and how issues with the service provider are handled.

5. Stablecoin Settlement

SAP describes cross-border settlement with Circle's USDC as completing in minutes rather than days. This is a valuable option, but accounting treatment, treasury policy, and audit issues are independent of the technology itself. Auditors will want to see the policy before your first payment.

USDC is a USD-pegged stablecoin issued by Circle, backed 1:1 by reserves including cash and short-term US Treasuries, with Circle publishing regular reserve audit reports. In cross-border B2B scenarios, stablecoins enable near-real-time on-chain transfers, bypassing correspondent banking chains and batch clearing windows—hence SAP positioning it as a "minutes rather than days" settlement option. But for corporate finance, the key questions aren't about technical speed but about accounting and compliance: whether stablecoins should be classified on the books as cash equivalents or other assets, at what exchange rate and fair value they are measured, who is responsible for on-chain address ownership and private key management, and how AML and sanctions screening cover on-chain counterparties. These policies need to be confirmed with auditors before the first payment.

6. Agents and Payments

SAP says agents will soon trigger and execute payments. Borrow the autonomy ladder concept for agent permissions: agents can draft and recommend payments, but payment release should come much later than recommendation. Set the rules now.

7. How to Exit

After stopping SAP Pay, how do you return to your own bank without launching a new project? SAP says it is complementary to Multi-Bank Connectivity, which hints at a fallback path. Require it to be written into the contract.

Control Matrix for the New Process

Supplier creation or bank information changes are owned by the master data team, with controls of dual approval plus callback confirmation, and evidence in the change log. Invoice approval is owned by AP approvers, with controls of approval limits, matching rules, and prohibition of self-approval, and evidence in the workflow log. Payment execution is owned by SAP Pay and your payment settings, with controls of sanctions screening, routing rules, and release limits, and evidence in the service provider's execution log. Payment reconciliation is owned by AP and treasury, with controls of exception queues and timing checks, and evidence in reconciliation reports. If any row has no owner today, fill that gap before turning on automation.

Comparison with Existing Options

Direct bank connectivity: you handle formats, bank onboarding, and testing yourself—maximum control, maximum effort. SAP Multi-Bank Connectivity: a secure enterprise-to-bank network that SAP says SAP Pay uses rather than replaces. Third-party payment providers or treasury platforms: independent contracts, independent screening and reconciliation interfaces. SAP Pay: embedded in ERP, priced by transaction blocks, with execution, screening, and reconciliation in one process, run by an operator SAP wholly or partially owns.

The real differences aren't in the feature list but in who holds the contract, who performs screening, where reconciliation happens, and how you exit.

A 30-Day Pilot Approach

Select a single legal entity and a group of low-risk suppliers in a supported country; start with domestic payments only, testing cross-border and stablecoins separately; measure approval-to-settlement time, exception counts, reconciliation effort, and per-transaction cost against a baseline; verify the control matrix item by item with real evidence; define upfront what the pilot must prove before scaling.

Final Assessment

Fewer steps is good. But fewer steps also means fewer people, documents, or delays that can stop an error. Zoom out: ERP, AI agents, and now payments all come from the same vendor. That's convenient, and it's concentration risk. Enjoy the convenience while preparing for the concentration.

One-line Summary

SAP Pay brings payment execution and reconciliation into Cloud ERP, where approval equals payment—reshaping financial controls.

Paragraph Summary

SAP Pay is a B2B payment solution embedded in SAP Cloud ERP that executes payments directly after invoice approval and automatically reconciles them, covering ACH, wire transfers, checks, real-time payments, and Circle's USDC stablecoin rails, operated by Tereina, which SAP describes as wholly owned. The article argues its real significance lies in the redesign of the buffer between approval and funds outflow, not in adding a payment button. It also reveals three discrepancies between official statements and Reuters reporting on ownership structure, availability regions, and savings claims, and raises questions across seven dimensions: separation of duties, supplier bank changes, license coverage, funds flow, stablecoin accounting, AI agent payment authority, and exit paths. It concludes with a control matrix and a 30-day pilot approach, reminding enterprises to prepare for vendor concentration risk while enjoying the convenience.