On this page
01
Start with reconciliation-ready records
Reconciliation is only as good as the record. Every usage record Cloptima keeps is built to line up against a provider invoice later.
- Provider, model, and token counts (input/output, plus image/audio units where reported)
- Pricing source and the rate applied at the time of the call
- Owning team, app, environment, and customer/workflow attribution
- Billing period and request identifiers for line-item matching
02
Expect timing differences
Provider bills, gateway logs, and telemetry streams arrive at different times. Reconciliation should make timing and pricing assumptions explicit rather than hiding deltas.
03
Account for credits and discounts
Credits, commitments, negotiated rates, and platform fees change the cost finance cares about. Track these adjustments separately from raw estimated usage.
04
Match provider-reported cost in Cloptima
Cloptima brings metered usage, provider-reported cost, allocation, and cloud ownership context into one bill-matching view, surfacing variance and unmapped spend instead of a single blended number.