Technology ownership can move. Accountability cannot.
AI Team Moving to Service Provider
Technology ownership can move. Accountability cannot.
The service provider can operate the runtime. The service provider cannot own BP's accountability. BP remains accountable for business outcomes, financial controls, regulatory compliance, and enterprise risk.
Platform capability proof: every accountability boundary is tied to source lineage, evidence pack, replay trail, policy authority, collaboration handoff, action permissions, observability, value impact, and learning ownership.
Executive Positioning
Traditional outsourcing transfers activities. AI-enabled operating models transfer execution. The objective is not to outsource decisions; it is to create a governed decision-execution model where humans, agents, and service providers operate within clearly defined accountability boundaries.
What BP Owns
| Area | Examples | Boundary |
|---|---|---|
| Enterprise Policies | journal approvals, SoD, payment thresholds, treasury controls, credit exposure, financial reporting | Agents cannot change policies; only authorized governance teams can. |
| Data Ownership | SAP ECC, S/4HANA, CFIN, Databricks, UDP, OneData, master data, financial records | Service providers may access governed data; ownership never transfers. |
| Controls Ownership | SOX, internal controls, financial controls, compliance controls, audit requirements | BP defines evidence, testing, and approvals. |
| Risk Ownership | financial, operational, regulatory, cyber, model risk | Agents may identify risk; agents do not own risk. |
| Governance Ownership | AI, model, risk, control, audit governance | All governance decisions remain under BP authority. |
What Service Provider Owns
| Service Provider Owns | Responsibility |
|---|---|
| Agent Implementation | build, configure, deploy, enhance, maintain |
| Runtime Operations | agent runtime, orchestration, event processing, observability, incident management, support |
| Monitoring | runtime health, agent health, policy violations, failures, performance, model quality |
| Continuous Optimization | automation rates, cycle times, exception handling, model quality, process performance inside governance boundaries |
Joint Ownership Areas
| Joint Area | BP | Service Provider | Joint Outcome |
|---|---|---|---|
| Productivity | Own targets | Operate improvements | cycle time, touchless processing, automation rates |
| Quality | Own control standard | Improve execution quality | error reduction, control effectiveness, policy compliance |
| Financial Outcomes | Own financial result | Support value delivery | working capital, close acceleration, spend reduction, leakage prevention |
| Change Management | Own process, communications, role redesign | Support training and adoption | training, adoption, KPI management |
Three Layer Accountability Model
| Layer | Owner | Examples |
|---|---|---|
| Layer 1 - Decision Authority | BP | approve payment, journal, credit extension, accounting treatment |
| Layer 2 - Decision Recommendation | Shared | risk scoring, anomaly detection, forecast recommendations, close recommendations |
| Layer 3 - Decision Execution | Service Provider | process invoices, gather evidence, reconcile, create journal drafts, monitor controls |
Operating Model Explorer
| Capability | Activity | BP | Service Provider | Agent |
|---|---|---|---|---|
| Duplicate Invoice Prevention | Define policy | Accountable | Consulted | None |
| Duplicate Invoice Prevention | Configure rule | Consulted | Responsible | Assisted |
| Duplicate Invoice Prevention | Detect duplicate | Informed | Responsible | Execute |
| Duplicate Invoice Prevention | Approve payment release | Accountable | Support | Recommend |
| Journal Intelligence | Accounting policy | Accountable | Consulted | None |
| Journal Intelligence | Journal creation | Informed | Responsible | Execute |
| Journal Intelligence | Risk scoring | Consulted | Responsible | Execute |
| Journal Intelligence | Approval | Accountable | Support | Recommend |
RACI Explorer
| Capability | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Invoice Processing | Service Provider | BP Controller | Procurement | Leadership |
| Journal Review | Service Provider | BP Finance | Audit | Leadership |
| Treasury Forecast | Service Provider | BP Treasury | FP&A | CFO |
| Close Intelligence | Service Provider | BP Controller | Audit | CFO |
Runtime Accountability Panel
- Who: human, agent, service provider
- Under which policy: policy ID and version
- Why: business rationale
- Evidence used: source systems, documents, data points
- Approval authority: required approver and actual approver
- Outcome: approved, rejected, escalated
Payment Release Decision Walkthrough
- Agent: AP Validation Agent
- Service Provider: Service Provider AP Operations
- Bp Owner: AP Control Manager
- Policy: AP-PAY-017
- Evidence: SAP invoice, PO, Goods receipt
- Decision: Recommend release
- Final Authority: BP approver
Strategic Message for BP
The goal is not to replace accountability with AI. Humans remain accountable, policies remain authoritative, controls remain enforceable, agents accelerate execution, service providers operate the runtime, and BP retains governance and ownership. bp Sphere becomes the enterprise accountability fabric.