SAP Sapphire Madrid 2026: Why autonomous enterprise needs finance orchestration

Roger Federer was, predictably, one of the standout moments at SAP Sapphire Madrid 2026. I'll admit I was sceptical about how a tennis legend would land in a room full of enterprise software conversations, but his reflections on pressure, resilience, versatility, and strategic thinking hit harder than I expected — especially in a business context where execution matters as much as ambition. SAP framed the whole event around "The Beginning of Better," and the sessions I attended kept circling back to Joule, AI strategy, live demos, and the harder work of turning AI momentum into measurable outcomes.

The message I heard repeatedly, whether from SAP leadership on stage or partners I spoke with between sessions, was the same: enterprise AI will not create value simply because it exists inside the technology stack. It needs clean data, governed processes, connected applications, and teams that know where automation should act.

That is where finance orchestration becomes critical — and it's the through-line I want to pull on in this piece.

By finance orchestration, I mean connecting spend, expenses, accounts payable, approvals, controls, and ERP data into one coordinated workflow. Instead of adding another layer of tools, you build a finance operating model where people, systems, and AI can act on the same trusted information.

SAP's autonomous enterprise vision raises the bar for finance

The central announcement from SAP Sapphire 2026 was SAP's move toward the Autonomous Enterprise. SAP described this as a model where humans and AI work together across mission-critical workflows, supported by SAP Business AI Platform, SAP Autonomous Suite, and Joule Work.

SAP is moving beyond embedded AI assistants and toward AI that can help execute business processes. SAP announced more than 50 domain-specific Joule Assistants across finance, supply chain, procurement, HCM, and customer experience, orchestrating more than 200 specialised agents.

That matters because finance teams are no longer being asked only to report on what happened. They are being asked to help the business act faster, with better controls and stronger context.

Gartner expects 40% of enterprise applications to include task-specific AI agents by the end of 2026, up from less than 5% in 2025. McKinsey also reports that finance teams are already using AI to improve forecasting, working capital monitoring, reporting cycles, and cost-saving visibility.

The opportunity is real. But so is the risk of disconnected automation.

AI readiness now starts with data quality

One of the strongest themes at Sapphire was that AI is only as useful as the business context behind it.

SAP positioned SAP Business Data Cloud as the data foundation for the Autonomous Enterprise. It described the platform as a business data fabric that anchors universal business context for applications and agents. SAP also highlighted SAP HANA Cloud, Reltio, and SAP Master Data Governance as ways to unify, cleanse, govern, and contextualise enterprise data.

For finance teams, this is an important reminder. Poor spend data does not become strategic simply because AI can read it. Fragmented expense processes, inconsistent supplier records, delayed AP visibility, and manual reconciliation all reduce the quality of AI-driven decisions.

A practical example: if a procurement agent is assessing supplier risk, it needs trusted information on supplier history, invoice status, policy compliance, payment behaviour, and purchase context. If that data is split across cards, spreadsheets, inboxes, AP tools, and ERP customisations, the agent's output becomes less reliable.

Payhawk's role in this environment is to help finance teams structure spend data earlier in the workflow. By capturing spend, expense, AP, and approval data before it reaches the ERP, finance can provide cleaner inputs into SAP-led transformation programmes.

Clean core is now an AI readiness issue

SAP's clean core message has often been framed as a technical architecture priority. At Sapphire 2026, it became much more closely tied to AI readiness.

SAP introduced agent-led transformation tooling that it says can reduce ERP migration effort by more than 35% by automating system analysis, code remediation, configuration, and testing. That signals a clear direction: organisations with complex customisations and fragmented processes will find it harder to adopt SAP's AI roadmap at speed.

For system integrators, this creates a practical client conversation.

Clean core is not only about reducing technical debt. It is about helping clients standardise the right processes, connect the right applications, and avoid recreating legacy complexity in the cloud.

This is where spend management should be part of the S/4HANA transformation discussion early. Finance teams need expense, card, invoice, approval, and supplier workflows that complement the ERP instead of creating parallel process layers.

Our experience tells us that implementation partners look for reliable technology, deep ERP integrations, strong partner and customer experiences, and solutions that protect their client relationships. In other words, a spend management partner must not only work technically. It must also protect the SI's reputation during and after implementation.

AI value will be won at the problem level

The most compelling AI examples from Sapphire were not abstract platform demonstrations. They were problem-led.

SAP highlighted examples such as reducing downtime in offshore wind turbines, improving process execution, and using agents to support end-to-end finance activities such as journal entries, reconciliation, and error resolution.

That is the right direction. Enterprise AI becomes useful when it is designed around specific business problems.

For finance, these problems are familiar:

• Employees submit expenses late or with missing information.
• Finance teams chase receipts, approvals, and coding corrections.
• AP teams manage invoices through shared inboxes and manual checks.
• Month-end close depends on reconciliation work that happens too late.
• Leaders lack real-time visibility into committed and actual spend.

A generic AI layer will not fix these problems on its own. Finance teams need structured workflows, policy controls, ERP integration, and real-time spend data before automation can safely accelerate decisions.

That is the difference between finance automation and finance orchestration. Automation completes a task. Orchestration connects the full process, from spend request to approval, payment, accounting, and reporting.

What this means for SAP system integrators

For SAP SIs and consulting partners, Sapphire 2026 creates a strong opportunity to reposition spend management as part of enterprise AI readiness.

Clients will need help answering three questions:

1. Is our finance data ready for AI?

You can help clients assess whether spend, expense, invoice, and supplier data is clean, complete, and available in real time.

The outcome: finance leaders gain better visibility before data reaches the ERP.

2. Are our workflows ready for autonomous execution?

You can map which finance processes should stay human-led, which should be automated, and which could later support agent-led execution.

The outcome: clients avoid automating broken processes.

3. Are complementary apps strengthening the SAP core?

You can evaluate whether finance tools integrate deeply with SAP, support clean core principles, and reduce manual work without adding unnecessary complexity.

The outcome: clients get a finance stack that supports transformation instead of slowing it down.

Why Payhawk fits the SAP transformation conversation

With Payhawk's native SAP S/4HANA integration, finance teams can manage spend in Payhawk while keeping SAP updated with approved transactions, attachments, and accounting context. This supports cleaner posting, stronger audit trails, and better visibility before month-end.

When spend data is fragmented, finance loses control and AI has weaker context. When spend workflows are orchestrated, finance can support faster decisions with stronger governance.

For SAP-focused partners, Payhawk can support three client outcomes:

• Control: Finance teams can apply policies, approvals, and visibility closer to the point of spend.
• Efficiency: Teams can reduce manual work across expense management, AP, reconciliation, and ERP data preparation.
• ERP value: Clients can get more from SAP by connecting it to cleaner, more structured finance workflows.

This matters because SIs are not simply recommending software. They are protecting client trust. The right finance technology should improve the client experience, strengthen implementation outcomes, and support a longer-term advisory relationship.

The takeaway: AI needs execution-ready finance

SAP Sapphire Madrid 2026 made one thing clear: the next phase of enterprise AI will be judged by execution.

The autonomous enterprise will not be built on disconnected pilots or generic automation. It will depend on clean data, governed processes, trusted integrations, and clearly defined business problems.

For finance leaders, that means preparing spend, expense, AP, and approval workflows for a more agentic future.

For SAP system integrators, it means helping clients build finance architectures that are not only cloud-ready, but AI-ready.

And for Payhawk, it reinforces a clear position: finance orchestration is not a side conversation in SAP transformation. It is part of the foundation that makes autonomous enterprise execution possible.

If you are an SI or consulting partner helping clients prepare for this next phase, explore the Payhawk Partner Program or book a personalised demo to see how we work alongside you to deliver execution-ready finance.