Common Bill Ingestion Default Format

To upload bills via Common Bill Ingestion (CBI), the bills must first be structured in the CBI Default CSV format. The following table defines the CSV format and indicates what fields map to which Cloud Cost Optimization dimensions:

Common Bill Ingestion Default CSV Format

CSV Column

Dimension

Required?

Meaning

CloudVendorAccountID

Cloud Vendor Account

No

A unique ID for an account (may be used in Cloud Cost Optimization to assign costs to Billing Centers).

CloudVendorAccountName

Cloud Vendor Account Name

No

A human-readable name for the account.

Category

Category

No

The category this usage record belongs in (for example, Compute, Storage, or Network). Set to whatever categories make sense.

For a full list of pubic cloud example categories, see Cloud Cost Optimization-Generated Cost Dimension: Category.

InstanceType

Instance Type

No

An identifier for common hardware configurations for VMs running a customer workload. For example, m4.xlarge (AWS), D2 v3 (Azure), or n1-standard-4 (Google Cloud Platform).

LineItemType

Line Item Type

No

Indicates the type of information the line item is for, such as Usage, Tax, Fee, or Credit.

Region

Region

No

The physical region where a resource was consumed.

ResourceGroup

Resource Group

No

A unique identifier which can group resources together (if applicable).

ResourceType

Resource Type

No

A loosely-defined concept; depends on the application, but generally indicates the type of resource consumed within a service. For AWS, it is product/productFamily column in the HCUR bill. For Azure, it is a combination of MeterCategory and MeterSubCategory fields. For Google Cloud Platform, it is the sku.description field of the BigQuery billing dataset.

ResourceID

Resource ID

No

The ID of a specific cloud resource. For AWS, it might be a bucket name or instance ID. Equivalent for other clouds.

Service

Service

No

The name of the high-level service consumed. For example, AmazonS3 (AWS), Microsoft.Compute (Azure), or Compute Engine (Google Cloud Platform).

UsageType

Usage Type

No

A loosely-defined concept; depends on the cloud, but generally indicates information about the kind of usage incurred. For AWS, it is lineItem/usageType (for example, DiscountedUsage). For Azure, it is MeterName (for example, Standard Transactions).

Tags

-

No

Can be used for defining custom dimensions. For example, consider the following:

"{""environment"": ""Test"", ""department"": ""Sales"", ""cpu-count"": ""24""}"

UsageAmount

Usage Amount

Yes

The amount of usage generated in this record in the units specified in UsageUnit (set to 0 if not needed).

UsageUnit

Usage Unit

Yes

The units that the Usage Amount metric is reported in.

Cost

Cost

Yes

The total cost generated in this record in the currency specified by currency.

CurrencyCode

-

No

The three-letter identifier of the currency for cost (for example, USD, CAD, GBP, EUR).

UsageStartTime

-

Yes

A UTC time in the RFC3339 format time (for example, 2006-01-02T15:04:05Z) representing when the usage started.

Note:If a cost record spans a period longer than a day, you will need to break it down into multiple records.

InvoiceYearMonth

-

Yes

The month this usage was billed/invoiced, for example, 202003.

InvoiceID

Invoice ID

No

The identifier for the invoice that this cost/usage was billed under, if any. Helpful for reconciliation of billing data with an invoice.

The first step toward structuring your data in the CBI Default CSV format is to determine the mapping of native bill fields to the CBI Default CSV fields. When determining your mapping from native fields to CBI Default CSV fields, it may be helpful to refer to the Bill-based dimension documentation for similar mappings from existing public clouds.

For more information about bill-based data dimensions in Cloud Cost Optimization reporting, see Cloud Provider Bill-Based Cost Dimensions.