Billing integrity5 min read

When the billing display is wrong

How to investigate a suspicious AWS total without confusing an estimated display, detailed usage records, and a finalized invoice.

Do not turn a strange number into an outage

When a current-period number suddenly looks wrong, the first job is reconciliation. Cost Explorer can revise estimated values while a billing period is open. Before anyone changes infrastructure, establish whether the movement exists in the underlying usage and billing records.

Write down exactly what looked wrong

Capture the metric, filters, dates, grouping, currency, and time you saw the result. Without that record, a later correction can make a real discrepancy impossible to reproduce.

Evidence ruleBilling evidence establishes cost and usage. Configuration and operational evidence add context. Business cause remains an inference until the sources support it.

Check the number from another direction

Compare the daily pattern with matching line items in your billing export. Look for late-arriving data, credits, refunds, and changes in the selected cost metric. Check service health too, but do not treat a status message as a substitute for reconciling your own evidence.

A display problem and an invoice problem are different claims

A display error does not prove the invoice is wrong. A CUR snapshot can also change while the billing period remains open.

Hold weak evidence for review

Kulshan records provenance and billing-integrity status so findings can be held for review when the underlying surface is suspect.

Build a stronger evidence trail

Yuvdeep Singh builds Kulshan and runs AWS cost investigations from Mission, BC. These notes distinguish observation, estimate, and inference.

← Back to Thinking