Connect each chargeto the work behind it.
Reconcile model usage, cloud resources and service work using an agreed basis. Keep discrepancies and approvals visible before deciding what to change.
Discuss your scopeReconcile before optimizing
More usage is not necessarily waste, and a lower bill is not proof of better outcomes. Connect accounts, projects, environments and billing items instead of judging only the total.
Collect
Billing lines, usage and inventory, with period, currency and units.
Allocate
Map to projects, accounts and owners; keep unallocated costs separate.
Investigate
Compare usage, rates and items; first check time zones, caching and duplicates.
Approve changes
Present the proposed change, impact and rollback to the customer budget or system owner.
Monthly reconciliation
Reconcile bills and usage, record explained and open items, then agree settlement evidence.
How a discrepancy reaches resolution
Illustrative example · not customer data
Application totals differ from the cloud bill. Preserve both exports and record the account, project, billing date and discrepancy. Do not alter charges yet.
Normalize the time zone and separate standard input, cached input and output. This example finds cross-day records and mixed cache categories; request counts are not tokens.
Attach the mapping and reconciliation note. Finance confirms allocation; the technical owner confirms measurement. Keep unexplained items open rather than claiming savings.
| Record field | Example entry | Reviewer |
|---|---|---|
| Allocation | Support assistant / staging | Customer project owner |
| Measurement | Billing export ↔ usage export ↔ project tags | Customer technical owner |
| Status | Basis explained; allocation pending | Customer finance / procurement |
Bring to the first discussion
Bring redacted bills, usage exports, inventory, allocation rules and a budget owner. Define accounts, regions, currency and review period. Do not share keys or full customer data.
Reviewable deliverables
A billing-item dictionary, allocation map, discrepancy and approval log, monthly reconciliation and change recommendations with assumptions.
Scope boundary
No fixed savings promise or substitute for a financial audit. Resource changes, budget changes and billing disputes require the appropriate approval and an agreed scope.
Agree inputs and acceptance criteria before scheduling resources and effort.
Discuss your scope