User Guide

Cost Reconciliation

Re-check archived months against the cloud and flag any that drifted — so chargeback and trend reports stay accurate long after the month closes.

Why closed months drift#

A closed month feels final, but the cloud keeps adjusting it — often for weeks:

  • ✓Late-arriving usage that metered after the month ended
  • ✓Credits and refunds applied retroactively
  • ✓Reservation and savings-plan true-ups
  • ✓Tax and currency restatements

CCO archives a month once and then trusts it — which keeps the app fast, but means a later restatement can leave a stale total behind. For an MSP invoicing a client off that month, a drifted number is a mis-billed number.

What reconciliation does#

Reconciliation re-fetches each archived month's total from the cloud, compares it to what CCO has stored, and records any material drift:

  • ✓Material drift is a change past a threshold — a percentage of the archived total or an absolute floor, so rounding noise never raises a flag
  • ✓Drift is recorded per month with the archived value, the current cloud value, and the delta
  • ✓You review the drift and apply the correction — re-archiving the month with the up-to-date number — or dismiss it
Paced and throttle-safe
Re-checking years of history could hammer the rate-limited cost APIs. Reconciliation reuses the same paced, self-healing background walker as the history backfill — it trickles through the work without tripping provider rate limits.

When it runs#

  • ✓Weekly — a light sweep of the most recent closed months, where almost all drift lands
  • ✓On demand — trigger a deeper check to whatever depth you choose
  • ✓Alerts — a cost-drift notification tells you which months moved and by how much, with a full drift history you can audit
Note
Reconciliation is available for Azure today; AWS and GCP are on the roadmap. It's alert-and-review by default — corrections are applied on your say-so, not silently.

Where to find it#

Reconciliation lives on the cloud account in Settings → Cloud Accounts, alongside history backfill. Run a check, watch its progress, and review the drift list — each row offers “apply corrected total” or “ignore.”

Tip
Backfill fills a missing month; reconciliation keeps an existing month honest as the cloud restates it. Use backfill to load history, reconciliation to keep it accurate.