---
title: "Guide: Explain the gap in your AI bill"
canonical_url: "https://tokenobserve.com/guides/reconcile-ai-provider-spend"
published: 2026-10-15
last_updated: 2026-10-15
---

# Guide: Explain the gap in your AI bill

The question: Why does our AI bill differ from our token estimate?

## The answer, in one paragraph

Compare the gateway estimate with the provider report first, then compare the provider report with the invoice. Use the same account, currency and completed UTC period for each comparison. Record each explanation with its source instead of adding the three totals.

## Facts

- First check: Gateway estimate to provider-reported cost
- Second check: Provider-reported cost to final invoice
- Keep alongside each amount: Account, source, currency, UTC period and collection status
- Worked example: Synthetic USD amounts; not a customer result

## The limit

A review workflow: The worksheet does not connect an account, import a bill or automatically reconcile a product ledger.

### Make the two figures comparable

Select one account and a completed UTC period. Keep currencies separate. Retain the exact source export, its collection time and coverage status. Compare the whole period rather than one displayed page of a report.

A gateway sees routed traffic. A provider account can include direct calls, console use and other workloads. Partial collection, missing usage chunks, stale price assumptions and cache categories can each create a difference. Team attribution still needs your own supporting records.

### Follow a synthetic USD 70 difference

For the same example account and month, the gateway estimate is USD 1,180, the provider report is USD 1,200 and the invoice is USD 1,250. The first difference is USD 20. An example USD 15 direct job and USD 5 pricing correction explain it: 1,180 + 15 + 5 = 1,200.

The second difference is USD 50. In this synthetic invoice, USD 60 tax less USD 10 credit explains it: 1,200 + 60 − 10 = 1,250. Tax, credits and timing depend on the actual provider and agreement; these amounts are invented solely to show the arithmetic.

The three source totals remain separate. Adding them would count overlapping API usage several times. A zero residual is useful only when the explanations have source evidence; it is not proof that every charge is known.

### Leave a record another person can check

Download the worksheet and keep one row for each bridge. Enter the currency, account label, UTC period, first and second source totals, signed adjustments, source reference and reviewer. Add your own formula in a spreadsheet if desired: second source minus first source minus explained adjustments is the unresolved residual.

Token Observe displays provider reports, imported invoice evidence and gateway estimates as distinct sources. The new cloud portal has no invoice CSV upload or automatic synchronization of existing imports. This guide is a manual review procedure, not a claim of automated invoice reconciliation or financial period close.

## Resources

- Download the reconciliation worksheet CSV: https://tokenobserve.com/downloads/ai-spend-reconciliation.csv
- Check estimates and one difference in your browser: https://tokenobserve.com/tools/ai-spend-estimator
- Connect OpenAI billing: https://tokenobserve.com/guides/connect-openai-billing
- Connect Anthropic billing: https://tokenobserve.com/guides/connect-anthropic-billing

## The capabilities behind this

- https://tokenobserve.com/platform/estate-spend
- https://tokenobserve.com/platform/spend-controls

## Questions and answers

Q: Does a missing source mean zero spend?
A: No. Record it as unknown and identify who can supply the evidence. A subtotal of known sources is not the whole estate’s spend.

Q: Can the worksheet combine GBP, EUR and USD?
A: It retains the currency on every row. Compare only rows in the same currency and period; there is no exchange-rate conversion or blended total.