Freeze the period and source documents
Download the final provider invoice, provider usage export, and WordPress operational export for the same UTC billing period. Record account, project, model, currency, retrieval time, and invoice number. A screenshot of a current dashboard is not an adequate month-end source because later adjustments can change it.
Treat the invoice as authoritative for the payable amount. The local $1,842 estimate is still valuable for control decisions, but it uses configured rates and supported paths rather than every billing adjustment. Reconciliation explains that role difference instead of forcing equality.
Build the bridge from estimate to invoice
Begin at $1,842 and add $121 of direct calls outside the WordPress path, $44 from a rate-table lag, and $24 from tax or rounding to reach $2,031. Each line needs a source and owner. If the arithmetic does not reach the invoice, add an investigation line rather than an 'other' plug with no explanation.
Keep usage variance separate from price variance. First reconcile request and token quantities by provider, model, and path. Then apply the verified rate and adjustments. Combining both in one percentage makes it impossible to know whether engineering or finance owns the difference.
| Bridge line | Amount | Evidence | Owner |
|---|---|---|---|
| Local operational estimate | $1,842 | frozen WordPress export and rate config | site operations |
| Direct calls outside coverage | +$121 | provider project/key attribution | application owner |
| Rate-table lag | +$44 | old/new rate and affected usage | configuration owner |
| Tax/rounding/adjustment | +$24 | invoice line | finance |
| Provider invoice | $2,031 | final invoice | accounts payable |
Assign every call to a coverage state
Classify usage as supported and observed by WordPress, supported but not locally estimated, direct or external call, or unresolved. Record provider request IDs or aggregate project evidence. Do not describe a path as protected merely because it shares the same provider account.
Where caching or discounts affect billed usage, retain the provider's own adjustment line and calculation basis. A local estimator should not imitate a discount it cannot verify in real time; it should disclose the limitation and reconcile later.
Investigate the residual with thresholds
Set both an absolute and percentage threshold for opening an investigation, but never discard an unknown source solely because it is small. A small new direct-call path can become next month's large exposure. Prioritize unexplained API keys, models, and projects before rounding differences.
Document timing differences, currency conversion, credits, taxes, and provider adjustments as separate categories. The jurisdiction-specific accounting treatment belongs to finance; the article does not prescribe tax treatment from a software estimate.
Close at zero unexplained variance
Zero unexplained variance does not mean the two original totals match. It means their difference is fully represented by evidenced bridge lines or an assigned open investigation with amount, owner, due date, and next check. The workbook should recalculate when any line changes.
Archive the invoice, exports, rate sources, bridge, approvals, and investigation outcomes according to the organization's retention rules. The commercial disclosure is the relevant next page for seller, plan, payment, and renewal facts; it should not be used as evidence for a provider's invoice line.
Use the invoice reconciliation workbook from “Reconcile operational AI estimates with the provider invoice at month end” on a real first installation. Download AI Cost Circuit Breaker for free, begin in Monitoring, and move to enforcement only after the expected signals and rollback are verified.