---
title: "Use case: Find out what AI costs this business, line by line"
canonical_url: "https://tokenobserve.com/use-cases/what-ai-actually-costs"
published: 2026-09-07
last_updated: 2026-10-21
---

# Use case: Find out what AI costs this business, line by line

Put a vendor, a tool, a team and a named owner on every AI subscription and API account, then map the charge lines out of your finance export onto an import template with ten required columns and two optional columns. Token Observe's import path needs no billing credential or vendor console login.

## The stated limit

What an import cannot find: A subscription that is on no invoice you give it

## Finance owns the total. Nobody owns the shape.

The card statement gives you a total and it is right: money moved. What it does not hold is which team, which tool and who decided, so the second question in the meeting is the one that lands. The usual answer is a spreadsheet that was accurate the week it was made.

## The steps, in this order

1. Register what you know about. One entry per vendor and tool, with a team and an owner email, in one of three states: approved, prohibited or unknown.
2. Map the export onto the template. Ten required columns: external id, vendor, tool, team, kind, currency, amount, charge date and the two service-period dates. Owner email and subscription id are optional.
3. Import it, and read what it refuses. The dashboard previews the parsed lines first. Unrecognised columns are refused, bounded at 1,000 lines, and rolled back whole.
4. Read billed and metered apart. Billed reports per currency, subscription and API in separate columns. Vendors you have not imported are unknown, not nothing.

### A bill and an estimate are never added together.

An invoice is money that has already moved; a metered estimate is a calculation over observed traffic. Adding them produces the single figure an executive asks for and a number that reconciles against nothing. That is how a spend tool loses its credibility over arithmetic.

- Billed: What an invoice line says, per currency, with its charge date and service period. Retained without proration.
- Metered: What gateway traffic is calculated to have cost, against price rows you hold. Never folded into the billed figure.
- Unknown: A source nobody connected. Reported as unknown rather than zero: those look identical on a chart and mean opposite things.
- Never produced: A blended total, or a converted multi-currency one. No exchange rate is applied anywhere.

### The same export imported twice adds nothing.

Identity is team, source and external id together, so an identical reimport contributes no spend. A reimport reusing an identity with different data is a conflict rather than an update and the whole import rolls back. Corrections are separately identified credit lines, which keeps the ledger append-only.

## What this still does not solve

- An import finds what the invoice lists. A personal card, a free tier or a vendor you have not exported stays unknown until another source finds it.
- The cloud pilot connects supported provider billing reporting sources. Their reported costs stay separate from gateway estimates calculated against configured price rows; missing or partial evidence is unknown, not zero.
- It does not reduce the bill. Nothing here routes, caches or downgrades a model to save money, and no percentage saving is claimed anywhere.
- The register records the current decision. It is not an attestation that earlier use was permitted, and it cannot cancel a subscription.

## Questions and answers

Q: Does this connect to our finance system or our vendor billing accounts?
A: Cloud billing uses the provider's required reporting credentials. The separate invoice-import path needs no billing credential: map the charge lines out of the export finance already produces onto the import template with ten required columns and two optional columns, as CSV in the dashboard or JSON over the API, so there is no billing connector to authorise and no vendor admin credential in the path. An import then finds what the invoice lists, and nothing else.

Q: Why will it not give us one total for AI?
A: Because the two things it holds are different measurements. Add a £120 subscription to £340 of estimated tokens and £460 appears nowhere else in your business: not on the vendor invoice, and not in the gateway.

Q: Can we trust a low number, or a screen with nothing on it?
A: Only as far as your coverage. A source nobody connected reads as unknown, never zero, and the estate report's completeness flag is hard-coded false with its reasons beside it. Detail rows cap at 1,000 and any truncation is stated in the report.