Agents need more than business process knowledge. They need to understand how your company actually works
SAP’s sponsored argument is that enterprise agents fail when they know the generic process but not a company’s messy, changing reality. The useful part is not the agent intelligence claim; it is the context, policy, reconciliation, and audit layer that makes execution safe enough to matter.
Transcript
Edmund The sharpest line in this SAP piece is basically: knowing procure-to-pay is useless if your agent does not know your weird version of procure-to-pay.
Geffen Yeah. A model can recite revenue recognition rules, but it cannot infer which contract override, posting history, and approval path apply to one transaction.
Edmund And that sounds obvious until you notice how much agent marketing skips it. Everyone says, “the agent handles finance,” as though finance were a single clean API.
Geffen Right.
Edmund SAP’s actual argument is better than the headline. The agent needs business objects, their relationships, and the controls around actions. Customer, supplier, contract, invoice, order. Then approvals, access rights, compliance rules, and an audit record.
Geffen Mm-hm.
Edmund Which is very much our boring-camp thing. The model can be wrong about a suggestion. It cannot be allowed to quietly be wrong about a payment.
Geffen Exactly. The article calls the endpoint governed execution. That is a sensible sequence: report an approval, recommend a payment, prepare it for a human, then execute and reconcile under policy.
Edmund Okay, that phrase is doing a lot of work, though. “Governed execution” can mean real guardrails, or it can mean a button that still routes everything through three people and saves no time.
Geffen Fair. And this is sponsored content from SAP, so the proof points need a little distance. PwC supposedly took a complex billing task from thirty-five minutes to five. Promising, but we do not get the error distribution or the operational setup.
Edmund Sure.
Geffen The technical reasoning still holds. Their IBM example is mundane and important: one system says IBM, another says International Business Machines, another says IBM Inc. More raw access does not solve entity resolution.
Edmund No way an LLM should be adjudicating that from vibes. You need a trusted entity profile, plus rules for which source wins when records disagree.
Geffen Yeah. SAP Reltio calls that dynamic survivorship, weighing source trust, recency, and aggregation. That is the load-bearing bit, not the assistant’s cheerful prose.
Edmund And Signavio finding four hundred versions of a supposedly single procure-to-pay process is the part I believe instantly. Every enterprise has one process in the slide deck and several hundred processes in the scar tissue.
Geffen Okay, that’s good.
Edmund It is also why I’m more optimistic than you are here. If the context layer is real, it makes the product legible. A person can see what the agent knows, what it may touch, and where it has to stop.
Geffen I am not actually gloomy on this one, Edmund. Fixed workflows for regulated steps, explicit thresholds for review, and monitored process drift are all mechanisms. That is a much stronger story than “our agent understands your business.”
Edmund Right, and the logistics example shows the product shape. A stock exception is not just finding another warehouse. It includes commitments, expiration rules, transportation, and approval authority. One-click is plausible only after all that context is already maintained.
Geffen Hm.
Edmund The weak point is crossing vendor boundaries. SAP says Joule can use Agent2Agent to interact outside SAP, including Microsoft Teams. But agents talking is the easy part. The hard part is carrying the policy, identity, and meaning with the work.
Geffen That is round whatever of our old receipts argument. A cross-system agent needs proof of what it was authorized to do, which records it relied on, and who approved the handoff. Otherwise A2A is just lateral movement with nicer nouns.
Edmund You were waiting all episode to say lateral movement.
Geffen I was trying to be normal for once. It did not take.
Edmund My one public call: sixty-five to thirty-five SAP publishes concrete cross-vendor A2A documentation for Joule by January first. They cannot sell this workflow story with integration staying foggy. Anyway, that was unusually sensible enterprise AI, Geffen. I cannot believe we found it.