Skip to main content

Methodology · exact number

How one exact total is built

This page explains how CloudJaeger combines cloud, SaaS and AI spend, which amounts it deducts, which possible overlaps remain in the total, how it compares totals with invoices, and what is not proven yet.

How it is built

  • CloudJaeger's monthly total combines cloud bills, direct SaaS bills and AI usage after the deductions listed below; unproven marketplace overlaps remain in the total.

  • Cloud bills come from each provider's own billing data: AWS Cost Explorer or your Cost and Usage Report, Azure Cost Management, and the Google Cloud billing export.

  • Demo accounts that do not exist are left out of every figure.

  • A bill row in another currency that could not be converted is never added to a dollar total, and the page says how many there are.

  • Amounts are kept in millionths of a dollar, so every total is exact to the cent.

Deductions and possible overlaps

  • An AWS member account connected beside its payer account is counted in the payer's consolidated bill on every day that bill holds.

  • Days that only the member account's own bill holds, such as days before the payer account was connected, are counted from the member's bill.

  • When an AWS member account is connected beside its payer, every page, report and export that adds up your connected accounts' bill counts each of the member's days once.

  • A second connection to the same account is counted once.

  • A vendor-name match between cloud marketplace and direct SaaS charges leaves both amounts in the total; overlap is not measured, and the smaller amount is reported separately as possibly counted twice.

  • AI usage that a cloud bill or the vendor's invoice already charges, such as Amazon Bedrock on your AWS bill or an OpenAI invoice, is kept as detail at $0.

  • Every amount removed is listed with both of its sources and its amount, on the Data trust page and in a CSV file.

  • Each month, what CloudJaeger counts plus everything removed must equal every source to the cent, and the page says when it does not.

Matched to an invoice

  • You enter each invoice's number, currency, total and tax from the invoice itself, and CloudJaeger shows its own total for the same cloud and month beside it.

  • When no invoice figure has been entered, the difference is shown as unknown, never as zero.

  • An invoice in euros is compared in euros, using the amounts the provider billed before any conversion to dollars.

  • The difference is split into rounding, because CloudJaeger keeps fractions of a cent, and what is left after rounding.

  • CloudJaeger's total is broken down into usage, tax, credits, refunds, support, marketplace purchases, discounts, and commitments and fees.

  • Azure's cost data is before tax, so the tax on an Azure invoice shows as a difference in tax.

  • Every conversion to dollars names its rate, where the rate came from and its dates, and a fallback rate is called a fallback.

  • Days the provider revised after the first import are counted, and their net change is shown.

  • The export follows the FOCUS 1.4 invoice columns, and it is not certified as FOCUS conformant.

Not proven yet

  • Coming: invoice totals read from AWS, Azure and Google directly, so they do not have to be typed in.

  • Coming: Azure and Google totals checked against their real invoices.

  • Coming: an AWS payer account's Cost Explorer bill split by member account.

  • Coming: a FOCUS conformance check, once the FOCUS 1.4 validator is available.

  • Coming: SaaS bills in a vendor's own currency exported in that currency; today they are exported in dollars.

How every other figure is computed is on /methodology, and what each module can prove today is on /evidence.