## TL;DR
Compare like with like: the console's estimate is invoice-like (includes tax, applies credits at month end), while Cost Explorer defaults to unblended pre-tax costs without credits. In Cost Explorer, include credits, refunds, and tax, and match the month-to-date range. The gap is almost always the tax and credit lines, not missing spend.

## The error
```text
Estimated charges in the billing console are higher than Cost Explorer
```

## Fix it
1. In Cost Explorer, set the same month-to-date range the console estimate covers, and switch the view to include credits, refunds, and tax.
   Expected: the Cost Explorer total moves toward the console number.
2. Open the Bills page and read the tax line and the credit/refund lines separately.
   Expected: those lines account for most of the remaining gap.
3. Check the account scope: confirm Cost Explorer is not filtered to a subset of linked accounts while the console shows the payer total.
   Expected: both views cover the same accounts.
4. If a gap remains, note that the console estimate is provisional and Cost Explorer trails by up to a day; recheck after the next daily refresh.
   Expected: the numbers converge or the leftover is a named line item.

## Use this when
- Finance quotes the console estimate and engineering quotes Cost Explorer and they disagree
- Month-end reconciliation shows a jump the dashboards did not predict
- An agent's savings report uses one source and the invoice uses the other

## Not for this skill when
- The numbers differ because of different date ranges (align the range first; that is not a real discrepancy)
- The console shows charges for a service nobody recognizes (that is an unknown-spend investigation, different skill)
- You are comparing against the final invoiced PDF (the invoice is the source of truth; estimates are provisional by design)

## Variant phrasings
- AWS estimated charges vs Cost Explorer difference
- billing dashboard higher than cost explorer
- why is my AWS bill higher than cost explorer shows
- cost explorer unblended vs estimated charges

## Why it happens
The Billing console's headline estimate is built to resemble the coming invoice: tax included, credits netted at month end, amortized reservation fees. Cost Explorer defaults to the opposite view: unblended, pre-tax, credits hidden unless enabled. Both are correct; they answer different questions, so comparing them raw always shows a gap.

## Edge cases
- Credits often apply only at invoice finalization, so mid-month comparisons always show credits as a gap
- Provisional billing data can be revised; a mid-month "saving" can shrink on the final invoice
- Consolidated billing: make sure linked-account filtering matches between the two views
- Cost Explorer data lags up to 24 hours; never reconcile against today's partial data

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_D0PAueVnqK42jAGBXf06OQ