SAP Pay and Joule Work: your ERP now pays the invoice itself

At SAP Connect 2026, SAP put two things on the table: SAP Pay, which executes and reconciles payments inside the invoice workflow of SAP Cloud ERP, and the start of the customer rollout for Joule Work, its AI workspace that coordinates agents across finance, HR, and procurement. Put those together and the path from "invoice approved" to "money gone" gets very short. The approval step is now the control that matters.

What actually happened

Per SAP's October 6 announcement:

• Joule Work customer rollout begins. SAP says it is already live with 110,000 of its own employees and reports 20% productivity gains across finance, HR, and procurement. That is SAP measuring SAP, so treat it as a vendor claim.
• SAP Pay launches. It is embedded in SAP Cloud ERP and pays and reconciles from inside the invoice flow. It is powered by Tereina, an SAP company.
• New Joule Assistants. Named examples include a sourcing assistant piloted at Novartis, an accounts receivable assistant at Nestlé, and a billing assistant at PwC.

SAPinsider's write-up adds the plumbing: SAP Pay launches in the US and UK, supports ACH, wire, and check, offers stablecoin-based settlement for cross-border payments, and needs the SAP Multi-Bank Connectivity add-on. Card payments are not on the list. Per SiliconANGLE, SAP's main way to charge for this is consumption-based AI units, with agent inference drawing them down.

Why it matters for your business

Most of our clients do not run SAP. The pattern still reaches you, because QuickBooks, NetSuite, and Bill.com are moving the same way: the system that approves the invoice now also sends the money, and an AI assistant prepares the approval.

That is a good thing for a small AP team. It is also a new fraud surface. A fake vendor or a changed bank account used to need a person to type it into the bank portal. When pay runs inside the ERP, a bad record moves money on approval. So before you turn on any "approve and pay" feature, on any platform:

1. Lock vendor bank changes. A change needs a callback to a known phone number and a second approver. No exceptions for "urgent."
2. Split prepare from approve. The AI can match the PO and draft the payment. A named human releases it, with a dollar threshold for a second signature.
3. Read the meter. Consumption-priced AI bills by use. Ask for the unit rate per invoice before the pilot, not after the first month.

Sources: SAP News, SAPinsider, SiliconANGLE.