SAP Connect 2026: The Autonomous Suite Meets the Rest of Your Stack

What happened

SAP Connect runs October 5–7 at the Las Vegas Convention Center, organized as five events under one roof: Customer Experience Connect, Finance Connect, Spend Connect, Success Connect (HR) and Supply Chain Connect (SAP). Those five tracks line up with the five domains of the SAP Autonomous Suite that SAP announced at Sapphire in May: Finance, Spend, Supply Chain, HCM and CX. The suite has more than 200 agents and 50 assistants, running on the new SAP Business AI Platform with its context, build and governance layers (SAP News). SAP also announced the SAP AI Agent Hub, built on SAP LeanIX and generally available in Q3 2026, to govern both SAP and third-party agents. For many line-of-business leaders, Connect is the first chance to see the Autonomous Suite one domain at a time.

Why platforms are implemented vertically but work runs horizontally

SAP Connect has five tracks, and the Autonomous Suite has five domains. Most organizations implemented SAP the same way, one domain at a time, each with its own program, budget and owners. That approach built strong finance, spend and supply chain systems.

The work runs across those domains:

• Procure-to-Pay moves through Spend, Finance and Supply Chain.
• Hire-to-Retire connects HCM to payroll accounting, cost centers and IT access.

When an autonomous finance agent processes a supplier invoice exception, it needs to know who holds approval authority. That answer may be defined in an HCM system, and it may not be SAP's. Autonomous domains deliver the most when the handoffs between them are designed as carefully as the domains themselves.

What it means for operators

The context layer is where the value is realized. SAP's own framing puts context first: the knowledge graph maps processes and roughly 7 million data fields, and Business Data Cloud extends that map to non-SAP data (SAP News; SAPinsider). What only the organization can supply are its own definitions: who owns each decision, what authority applies, and how exceptions are resolved.

Governance now spans vendors. The AI Agent Hub is designed to manage SAP and third-party agents together, and SAP supports the A2A and MCP protocols for working across vendors. Organizations that also run Workday will have its Agent System of Record as well. They benefit from deciding early how the two relate: which one is the authority for agent identity, ownership and permissions, and how each informs the other.

Tacit knowledge becomes an asset. SAP's new Company Memory layer, built on SAP Signavio, is designed to capture knowledge from policies, processes and communications. As we argue in AI in the Enterprise, the judgment behind exceptions has rarely been written down. Writing it down is what gives that layer something to work with.

Where the value is realized

Three steps help an organization get the most from the Autonomous Suite and from every platform around it:

1. Choose one process that crosses tracks. The exception path in Procure-to-Pay is a strong candidate. Measure its cycle time and its human touchpoints today, so the gain from agents can be shown in days and dollars.
2. Assign each system its authority. For example:
   • SAP for financial and process state
   • the HCM system, whether SAP SuccessFactors or Workday, for people, positions and roles
   • one registry as the record for agent identity, with the others connected to it
3. Write four answers for every decision an agent will take: who owns it, what authority applies, which data is authoritative, and when a person steps in. Those answers are the context that SAP's knowledge graph and Company Memory are designed to hold.

Done once, this groundwork serves every domain SAP automates next. Each track at SAP Connect can then build on the others rather than starting over. As Where ERP Returns Are Actually Decided explains, much of the return is set by design choices like these, well before anyone measures it.