An agent can be owned by platform, requested by marketing, approved by legal, and paid from a central provider account. When the invoice arrives, every team can say the charge belongs somewhere else.

The solution is a small ownership model that follows the task. One person does not need to own every part.

Shared infrastructure needs clear task ownership before it needs a chargeback formula.

Name the five roles#

Role	Responsibility
Service owner	Keeps the agent, tool connection, and default limits working
Task owner	Defines the business request and accepts the result
Budget owner	Decides whether the work fits the team’s plan
Approver	Makes a required content, risk, or spend decision
Finance reviewer	Reconciles charges and challenges unexplained amounts

The same person may hold several roles for a small process. The roles should still be named so a change in staffing does not erase accountability.

Follow one task across teams#

Imagine a product launch:

Marketing opens a request for six campaign assets.
A shared agent reads product notes.
Legal approves a claim.
Platform pays the provider invoice.
Finance closes the month.

The service owner did not define the campaign. Legal did not choose the model path. Finance did not decide whether the assets were useful. The task owner connects those decisions and should be responsible for the accepted outcome.

Use a responsibility table#

Decision	Service owner	Task owner	Budget owner	Approver	Finance
Agent can access the tool	Responsible	Consulted	Informed	Consulted	Informed
Request starts	Consulted	Responsible	Accountable	Informed	Informed
Spend crosses a threshold	Consulted	Consulted	Accountable	Informed	Consulted
Public claim is accepted	Informed	Responsible	Informed	Accountable	Informed
Charge is reconciled	Responsible for evidence	Consulted	Informed	Informed	Accountable
Access is removed	Accountable	Informed	Informed	Informed	Consulted

Keep the table with the process brief or service definition. A spreadsheet that nobody updates is weaker than a short field in the request.

Decide where the budget lives#

Choose one of three models:

Model	Works when	Risk
Team budget	Each request maps cleanly to one team	Shared work can become unattributed
Central budget	A platform or operations group provides a common service	Teams may request without seeing cost
Hybrid	Central service covers base access and teams fund task usage	Requires a stable allocation rule

Use the model that matches the decision. Do not create a detailed chargeback process before the team can reliably join a charge to a task.

Set a fallback for shared work#

When a task crosses teams, require:

one primary task owner;
one budget code or campaign ID;
a service owner;
the approval class;
the split rule if multiple budgets truly share the work;
the person who closes missing evidence.

If two teams benefit equally, split the agreed unit cost. Do not split an unexplained charge simply because both teams have a budget.

The spend reconciliation guide gives states for matched, pending, disputed, and missing charges. Use those states before deciding how to allocate a shared amount.

Review ownership when the process changes#

Ownership should be rechecked when:

a new team begins using the agent;
the agent gains a new tool connection;
the task starts producing public content;
the provider or pricing model changes;
an approval requirement is added;
a team stops accepting the output;
a shared budget crosses its threshold.

Do not assume the service owner becomes the budget owner when the process expands. The business owner still decides whether the work is worth continuing.

Give the budget owner an action#

A budget limit needs a next step:

ask for approval;
pause new tasks;
route simple work to a lower-cost path;
close requests with no owner;
move the work to the correct team;
investigate missing provider evidence.

The budget variance guide shows how to classify a variance before cutting work. Ownership is what lets someone take the action.

Report the shared work plainly#

A monthly summary should show:

spend by service and task owner;
shared or unallocated amount;
accepted and published outcomes;
approvals and exceptions;
missing cost evidence;
the decisions due before the next period.

Finance does not need every prompt to ask whether the charge belongs to the right team. It needs stable IDs, owners, and a visible path for unresolved work.

Deixic can show spend by agent, current activity, approvals, connected tools, and missing evidence in one place. Use the product view to support ownership decisions, while budgets, allocations, and financial close remain in the systems that own them.