Cloud Invoice Reconciler

Usually for one of five reasons. AWS Marketplace and upfront purchases come on their own invoices. Tax may be invoiced separately. The export was taken before AWS finalized the month. The comparison uses the amortized view, which spreads commitment fees, while an invoice never does. Or the export is filtered by usage date, while an invoice covers a billing period. This tool checks each one against your file.

Google Cloud bills late-reported usage in the invoice month it is processed, so the export has to be filtered by invoice.month, not by usage date. The invoice total is cost plus credits, with tax as its own lines. The BigQuery query on this page does all three, and a small rounding line is normal.

Billed or unblended cost is what the invoice charges: a Savings Plan fee or an upfront reservation fee lands in the month it is billed. Amortized cost spreads those fees over the usage they cover, which is better for showback but never matches an invoice. This tool reconciles billed cost, and lists the amortized total separately when the export has the columns for it.

One invoice month. For AWS, the Athena query on this page returns a billing period summed by invoice, line item type and day, or load the raw CUR 2.0 files for the month. For Google Cloud, the BigQuery query filtered by invoice month. Any cloud can also use a FOCUS export, CSV or gzipped CSV.

Within a dollar, or within 0.01% of a large invoice, because an export sums many lines that the invoice rounds one by one. A bigger gap is shown as not explained, with the checks that usually find it.

No. The file is read in your browser tab and nothing in it is sent unless you choose "Share for a review". Usage statistics record that a file was loaded, its detected type and a size band, never its name or contents. The /privacy page lists every field.