SAP autonomous enterprise: What it is, how it works and what it needs

At SAP Connect on October 6, 2026, SAP announced that the autonomous enterprise is moving into everyday work, starting with the customer rollout of Joule Work. SAP first presented the concept at Sapphire in May, and most of the coverage since has been about the agents themselves: how many there are and which business functions they cover.

Much less has been written about what those agents work with. An agent that matches invoices or creates sales orders relies on data in SAP, and a lot of that data starts out as a document someone sent in.

Gartner predicts that through 2026, organizations will abandon 60% of AI projects that lack AI-ready data. For SAP customers, the documents behind their transactions are one of the first places to look.

Key takeaways

• SAP delivers the autonomous enterprise through the SAP Business AI Platform, the SAP Autonomous Suite and Joule Work
• Your company decides, process by process, how much an agent may do without human approval
• Nearly every task SAP's agents take on starts with a document, from supplier invoices to employment contracts
• Agents can only use documents that are captured as SAP data, linked to the right business object and governed
• Invoice, order and HR processes already run in SAP with people handling only the exceptions

What is the SAP autonomous enterprise?

The SAP autonomous enterprise is SAP's operating model for AI, announced at SAP Sapphire 2026, in which AI agents built into SAP applications run business processes from start to finish. Each company decides which steps an agent may complete on its own and which still need a person's approval.

SAP describes it as a cycle in which the system senses what happens in the business, reasons about it and then acts. For companies that have used SAP for decades to record transactions, the change is that SAP now prepares and carries out many of those transactions as well.

What SAP announced: the building blocks

SAP delivers the autonomous enterprise through three products that build on each other. A data and AI platform gives agents their context, a suite of business applications puts the agents to work, and Joule Work gives employees a new way to direct them.

SAP Business AI Platform

The SAP Business AI Platform unifies SAP BTP, SAP Business Data Cloud and SAP Business AI in one governed environment.

At its center sits the SAP Knowledge Graph, a map of your business objects and how they relate to each other. That map tells an agent that a purchase order belongs to a particular supplier and plant before it changes anything.

SAP Autonomous Suite and Joule agents

The SAP Autonomous Suite covers SAP's business applications, from finance to customer engagement, with agents added so they run processes themselves. SAP's Sapphire announcement lists more than 50 domain-specific Joule assistants, each orchestrating a subset of over 200 specialized agents. SAP's own example is an Autonomous Close Assistant that compresses the financial close from weeks to days.

Joule Work

Joule Work changes how employees use SAP. A user describes the outcome they need in plain language, and Joule puts together the workflows and agents to get there.

Here is what each of the three changes for the people who use SAP.

Assistants, agents and autonomy: who decides what

The difference between an assistant and an agent comes down to who completes the task. With an assistant, an employee still does the work, with AI drafting or suggesting along the way. With an agent, the AI completes the task, such as matching an invoice, and a person steps in when something falls outside the rules.

That is what separates autonomous AI agents in the enterprise from the chatbots and copilots most companies have tried so far.

How far an agent goes is up to you. SAP lets customers set the level of autonomy for each process, so one company might have an agent prepare the payment run for approval while another lets it release payments within agreed limits. Those limits are best agreed with the owner of each process before the first agent goes live.

What an autonomous enterprise looks like in each business function

Each business area SAP targets gets its own agents. Line up what those agents handle with the documents behind each task, and nearly every task starts with something a supplier, customer or employee sent in.

Finance and procurement are a sensible first step, because supplier invoices and contracts arrive there in large volumes.

Why documents decide how autonomous your SAP processes get

The SAP Knowledge Graph gives agents a detailed view of what is already in SAP. It has no view of an invoice that is still waiting to be entered, or of a contract stored in a file share with no link to the supplier record. Whether a document is usable for an agent comes down to three things.

The document has to become SAP data

Until an invoice or customer order is turned into structured data in SAP, an agent has nothing to work with. If that step depends on someone typing in the data, every automated step after it waits for that person.

Capturing the data automatically where documents first arrive, whether that is a shared inbox, a portal or an EDI channel, removes the wait.

It has to be linked to the right business object

An agent approving an invoice has to see the purchase order and goods receipt that belong to it. That only works when every document is attached to the right SAP object, the way an invoice is linked to its purchase order and its accounting document.

SAP provides certified interfaces for these links: ArchiveLink for on-premises S/4HANA and ECC, and CMIS for the SAP BTP Document Management Service in the cloud. A document stored this way opens straight from the SAP transaction it belongs to.

Permissions and audit trails have to carry through to the AI

Once agents act on documents, auditors and process owners will want to know which document a decision was based on and who could see it.

The rules that already protect your documents from the wrong people have to apply to AI as well. An agent or assistant should only see what the user it acts for is allowed to see, and every document it uses keeps its retention period and access history.

Autonomous document processes you can run in SAP today

Companies don't need SAP's agents to run document-heavy processes in which software handles the routine cases and people only see the exceptions. Many already work this way in finance, sales and HR, and the groundwork they have laid is what agents will build on.

Supplier invoices that post themselves

Invoices go into one intake, whether they arrive by email or on paper. AI extracts the data, checks for duplicates and runs a three-way match against the SAP purchase order and goods receipt. Invoices that match post automatically, and only exceptions reach a person.

Each invoice is archived with a link to its purchase order and accounting document, along with a full audit trail. Eli Lilly automates more than 600,000 invoices a year in its SAP workflow across nearly 100 countries, and reached ROI within 18 months.

Customer orders created in SAP within seconds

Customer orders arrive by email or EDI, each in the customer's own format. The order data is checked against SAP master data, and rules decide which orders SAP creates automatically. A clean order lands in SAP in under 10 seconds.

At i-PRO Americas, staff used to key orders into SAP by hand. About 70% of new orders are now handled largely automatically, and the team sends most order confirmations on the day the order arrives.

Personnel files that build themselves from SuccessFactors

In HR, an event in SAP SuccessFactors creates and fills the employee's personnel file, which stays in sync with Employee Central. When a candidate accepts an offer, the employment contract is generated from a template and signed electronically.

HR no longer assembles these files by hand. Any agent that later handles an employee change finds every document it needs in one place.

Keep the core clean while your archive becomes a source of context

SAP's move toward agents makes clean core more pressing. Agents work from SAP's standard processes and data models, so the more custom code sits in S/4HANA, the less reliably they work. A clean core means extending S/4HANA through standard, certified interfaces and leaving the core itself unmodified.

Document automation is held to the same standard. Purchase-to-pay automation from Doxis is certified by SAP for clean core with RISE with SAP, so invoice automation extends SAP without custom code in the core.

The archive needs the same attention. Many companies keep years of SAP documents in a content repository that is slow to search and costly to run. Techniker Krankenkasse, Germany's largest health insurer, migrated its legacy SAP archive and now accesses documents ten times faster. With an archive that fast, old contracts and correspondence become context a process can draw on.

Is your SAP system ready? A document readiness checklist

Before you hand a process to an agent, check how its documents are handled now. If every item below is in place, an agent has what it needs, and you can show auditors what it based its decisions on.

• Incoming documents are captured automatically at the point of entry
• Every document is linked to the right SAP business object
• Metadata like supplier, document type and date is complete and consistent
• Access rights in the archive match the roles in SAP
• Retention periods and legal holds apply to documents and SAP data alike
• Every view, change and approval is recorded in an audit trail
• Your archive connects to SAP through certified interfaces

Where several items are still open, start with supplier invoices or customer orders. Delays there show up quickly in missed payment terms and late deliveries.

Give SAP's agents documents they can trust with Doxis

Doxis covers the document side of SAP's autonomous enterprise. Your documents enter SAP as validated data and stay linked to the right business object for as long as you keep them, so your teams only handle the exceptions. As SAP rolls out more agents, they will work from documents you already trust.

Doxis brings document capture and archiving together on one platform with SAP-certified integrations. An agent then gets the extracted data and the original document from the same governed source.

• Automate supplier invoices with three-way matching and automatic posting in SAP
• Create customer orders in SAP automatically, whatever format they arrive in
• Keep every document linked to its SAP business object through ArchiveLink or CMIS
• Build HR files directly from SAP SuccessFactors events
• Extend S/4HANA with clean-core certified invoice automation for RISE with SAP
• Give teams and AI assistants permission-based access to the full document history

Doxis is a Leader in the Gartner® Magic Quadrant™ for Document Management 2026.

Explore our SAP solutions or request a free demo below.

FAQs on SAP autonomous enterprise