How Do We Chargeback Agentforce Flex Credits to Business Units When Digital Wallet Reports at the Org Level?

An org invoice is not a chargeback. Digital Wallet tells you what the company burned. It does not tell Finance which business unit owes which share.

That gap is where the Proof Gap opens on consumption AI. The pilot case was built as one org number. The second BU joins the same cohort. Month-end arrives as one Digital Wallet total. Every leader has a story. Nobody has a tagged share.

This page is the RevOps chargeback model. It is not the kill-switch control plane, not the forecast-and-close checklist, and not a price list. Every product claim below carries the URL that published it. Your order form beats any blog math, including ours.

The buyer question, stated cleanly

Director of RevOps, revenue finance partner, Salesforce admin, VP Sales Ops at 100+ headcount:

How do we chargeback Agentforce Flex Credit consumption to business units when Digital Wallet only reports at the org level?

Useful answer: treat Digital Wallet as the org burn total. Build BU attribution yourself with tags on actions or sessions before scale, allocate the month-end wallet total by tagged share, and name the people who own the table and the journal entry.

What Digital Wallet actually gives you

Salesforce positions Digital Wallet as near real-time consumption insight across Flex Credits and Agentforce, with alerts so teams can see burn as it happens. Source: Salesforce Digital Wallet.

That is org-level visibility. It is a billing and monitoring surface for the org's consumption pool, not a finished chargeback ledger that posts cost centers into your GL.

The same product page markets custom business tagging so teams can categorize consumption by environments, agents, or features and automate internal chargebacks. Treat that as a product claim and a tagging hook, not as proof that BU invoices appear without an internal allocation owner. Source: Salesforce Digital Wallet.

What Salesforce itself says about billing truth and business context

Salesforce's 18 August 2026 post on the Agentforce usage data model, by Chetan Dandekar, states that Digital Wallet is the source of truth for billing and that token-based views are directional for analysis. If a usage report and the invoice disagree, the invoice is the record. The same post states Digital Wallet does not block execution when credits run out and overages bill at contracted rates. Source: Salesforce.

That post also shows how to join usage to business context such as country, brand, or cost center through Agent Session attributes and related DMOs. That is an analytics path you build. It is not an automatic BU chargeback. Source: Salesforce.

Published list math on that same post: standard pricing of $500 per 100,000 Flex Credits ($0.005 per credit), with agent actions described at 20 Flex Credits per action. Confirm your rate card and contracted rate on the order form before any allocation hits a budget slide. Source: Salesforce. Rate card PDF when needed: Flex Credits Rate Card.

Demand evidence the question is real

• Trailblazer Community Agentforce Pricing thread: operators debate how Flex Credits are bought, shared, and governed when the meter is org-wide. Trailblazer Community
• CalculateForce Flex Credits complete guide: allocation and planning framing for teams that have to explain credit burn across use cases. CalculateForce
• Reddit r/salesforce: Digital Wallet discussed as lacking hard caps, which leaves spend control and attribution to internal process. Reddit

Cite those as demand evidence. They do not replace your order form or your allocation table.

Why org-only visibility creates a Proof Gap

Three mechanics compound.

1. One invoice, many sponsors. Finance sees one Digital Wallet total. Each BU reports the pilot as a success against a share nobody measured.
2. Untagged cohorts cannot be reallocated later. If actions and sessions never carried a cost center, month-end math becomes politics.
3. The second BU scales first. Shared cohorts without chargeback tags turn every overage argument into a narrative fight instead of a tagged share.

That is the Proof Gap on the cost side. Spend was real. Attribution by owner was not.

The RevOps chargeback model

Five items. None of them require a purchase.

1. Tag before scale. Require a BU or cost-center tag on every Agentforce action cohort or Agent Session before a use case goes live. Use Digital Wallet custom tags and session-level business attributes so the join exists when burn happens, not after.
2. Keep Digital Wallet as the org total. Week by week, one named RevOps owner reads the wallet burn to date. That number is the numerator for allocation. Do not invent a second billing truth.
3. Allocate by tagged share at month-end. Compute each BU's share of tagged consumption, apply that share to the Digital Wallet period total and to the arrears invoice when it lands, and publish the allocation table the same day Finance needs it.
4. Name Finance on the journal entry. RevOps owns the allocation table. Finance owns the journal entry that charges cost centers. If either role is vacant, you have a dashboard, not chargeback.
5. Hold the decision rule. Do not put a second BU on the same cohort until tags are mandatory and both owners are named. Untagged shared burn is how org invoices become un-auditable.

Dry-run it once on last month's wallet total before the next BU joins. If you cannot produce a share table in one working session, the tags are not ready.

What this is not

This is not an anti-Agentforce page. Org-level Digital Wallet visibility is more than most consumption vendors ship. Chargeback is the layer you still owe yourselves.

This is not the kill-switch page. Alerts versus enforcement lives at Does Digital Wallet Stop Agentforce When Credits Run Out.

This is not the Flex Credits forecast-and-close model. Burn modeling, arrears invoicing, and the close checklist live at How Do You Forecast Agentforce Flex Credits When Overages Bill in Arrears.

This is not SKU identity. Which meter prompts hit lives at Which Agentforce SKU Are We On.

This is not audit-rights contracting. Parallel counts and order-form clauses live at Who Audits the Meter.

This is not a price list. The $500 per 100,000 Flex Credits figure above is Salesforce's published standard from the usage data model post. Confirm your contracted rate on the order form.

Related: Digital Wallet no kill switch · Flex Credits forecast and close · Agentforce SKU identity · Who audits the agent meter · Proof Gap · AI pricing and contracts topic · Agentforce and Data 360 share one credit pool