Skip to main content

Understand invoices with reports

To get a detailed view of your costs for a specific invoice or during a selected period, you often need to run a Cloud Analytics report.

Allocation: Invoices​

The Invoices allocation is used to analyze invoices issued to the following asset types, each invoice corresponds to an individual allocation rule:

  • Amazon Web Services, Google Cloud: For costs incurred by AWS accounts, Google Cloud billing accounts and Google Cloud projects

    • If you're using custom bucketing, allocations follow the naming convention [{billing_profile_id}] {billing_profile_name} - {bucket_name}.

    • Otherwise, allocation rules follow the naming convention [{billing_profile_id}] {billing_profile_name} - {asset_type}.

  • Looker: Looker invoices appear in the entry named Looker.

For other asset types, only Microsoft Azure billing data is available in Cloud Analytics; it will stay in the Unallocated.

Example​

The example report below uses the Invoices allocations for invoices issued to a fictitious company:

Invoices allocation

  • The company has a Billing profile US123123 – Example.com with custom buckets.

  • The company has three custom buckets with the supported asset types.

You can add more dimensions to further break down the invoice. Below is an example of the invoice issued to assets in the bucket Dev.

Invoices allocation - one bucket

The example below combines all three group allocations for Billing and invoicing for a breakdown of cost categories and savings.

Invoices group allocations

Limitations​

  • If your billing currency is Japanese yen (JPY), each invoice line item is first converted to JPY and then rounded to the nearest 10 yen. The invoice total is the sum of the rounded line items. By contrast, Cloud Analytics reports do not apply rounding, which may result in small discrepancies.
Last updated on