Integration · SAP BTP + Joule
Gate Joule before it touches
master data or financial postings
A BTP destination + Joule skill wrapper that puts a regulator-grade gate in front of SAP-originated AI calls — so AI changes to vendor master, journal entries, or material master data never bypass your SoD controls or ASIC / APRA obligations.
◐ In design partnership — CFO-office driven
What we’re building together
Adapter shape
- →BTP destination with mTLS — Joule extensions and CAP services call our gate as a standard HTTP destination.
- →Joule skill wrapper — wrap your custom Joule skills with a pre-action gate; refusals show up in the Joule chat with citations.
- →CAP service binding — for teams building bespoke AI in BTP, drop a pre-handler that calls /v1/governance/gate before the LLM.
- →S/4HANA RAP intercept on the roadmap — block AI-driven master-data writes that don’t pass the gate, even in the on-prem core.
Why CFO-office buyers care
- ✓SAP is the system of record for posting + master data. AI mistakes here become auditor findings, not just bad UX.
- ✓Cross-checks SAP’s native SoD with our regulator-mapped citations — a complete “why was this allowed” trail.
- ✓Customer-VPC deploy keeps prompts inside your SAP perimeter — important for PCI / banking secrecy / ATO data.
- ✓One audit table covers SAP-originated AI, Salesforce-originated AI, and Control-M-orchestrated AI — your CFO sees one number, not three.
Looking for one launch customer
One mid-market or enterprise SAP customer in AU/APAC — banking, energy, government, or insurance — running an active Joule pilot or BTP-hosted AI extensions. We co-design the destination shape, you get an early-access deploy + co-author the SAP TechEd story.
BTP destination spec
Co-authored OpenAPI + destination-config templates.
Audit data contract
How decisions surface in your finance ops + GRC tools.
TechEd / SAUG story
Joint case-study slot at the next AU SAP user-group event.