Export Billing Data to a File

To access a detailed breakdown of your charges, you can export your daily usage and cost estimates automatically to a CSV or JSON file stored in a Google Cloud Storage bucket you specify. You can then access the data via the Cloud Storage API, CLI tool, or Google Cloud Platform Console.

Usage data is labeled with the project number and resource type. You use ACLs on your Cloud Storage bucket to control who can access this data.

Important: Regular file export to CSV and JSON captures a smaller dataset than export to BigQuery. For example, the exported billing data does not include any invoice-level charges such as taxes accrued or adjustment memos. If you need to reconcile your exported data to your invoices, you should use export to BigQuery. For more information about export to BigQuery and the data it captures, see Export Billing Data to BigQuery.

How to enable billing export to a file

To enable billing export:

1. If you haven't already created a bucket in Cloud Storage, you need to create one. For instructions, see Creating Storage Buckets.
2. Then to enable billing export, go to the Google Cloud Platform Console.
3. Open the console left side menu () and select Billing.
4. If you have more than one billing account, select Go to linked billing account to manage the current project's billing. To locate a different billing account, select Manage billing accounts.
5. Click Billing export.
6. Select File export.
7. For Bucket name, specify name of the Cloud Storage bucket into which billing reports will be exported. The Google Service Account is granted write access to this bucket.
8. For Report prefix, specify a prefix for the Cloud Storage object name for the exported reports. The year, month, and day is appended to the prefix.
9. For Format, select CSV or JSON.
10. Click Enable billing export.

Contents of the exported billing file

The following table describes the contents of the exported billing JSON or CSV file. JSON metric names are listed first; CSV metric names are shown in parentheses under the JSON metric names.

Note: Exported billing data does not include invoice-level charges such as tax accrued or adjustment memos issued to a billing account.

Metric	Metric Properties
accountId (Account ID)	Metric Type: string Description: The billing account ID Example: 00D11E-FFCCD9-B44BAE
lineItemId (Line Item)	Metric Type: string Description: The URI of the specified resource Example: com.google.cloud/services/compute-engine/ForwardingRuleChargeBase
startTime (Start Time)	Metric Type: dateTime Description: The start time of the measured time period Example: 2015-04-29T00:00:00-07:00 Note 1: The date will not necessarily match the partition date, which is an internal processing date. Note 2: This metric might include late-reported usage not included in your bill and, as a result, might not map directly to your bill.
endTime (End Time)	Metric Type: dateTime Description: The end time of the measured time period Example: 2015-04-30T00:00:00-07:00 Note 1: The date will not necessarily match the partition date, which is an internal processing date. Note 2: This metric might include late-reported usage not included in your bill and, as a result, might not map directly to your bill.
projectNumber (Project Number)	Metric Type: integer Description: The project number Example: 333809197194
projectId (Project ID)	Metric Type: string Description: The ID of the project Example: my-app-project
projectName (Project Name)	Metric Type: string Description: The name of the project Example: My first app project
projectLabels (Project Labels)	Metric Type: string Description: Project labels, returned as key value pairs. For example, if you created labels called cost-center and geo and the project values for those labels were apacand my-cost-center, the metrics returned would be: JSON: {"geo":"apac","cost-center":"my-cost-center"} CSV: geo:apac;cost-center:my-cost-center For more information about labels, see the Google Cloud Platform Blog, Using labels to organize Google Cloud Platform resources.
Measurements
measurementId (Measurement)	Metric Type: string Description: URI of the specified resource Example: com.google.cloud/services/compute-engine/ForwardingRuleChargeBase
sum (Measurement Total Consumption)	Metric Type: integer Description: The calculated time period Example: 86400
unit (Measurement Units)	Metric Type: string Description: The time period units of measurement Example: seconds
Credits
Note: Credit columns appear only when there are credits on a billing line item. If multiple credits apply to a line item, then each of the credit fields listed below is included for each credit that applies.
creditId (Credit)	Metric Type: string Description: The credit ID Example: 008F74-21254F-7E5A81::3WDRCXQ9AHU4FK-81
amount (Credit Amount)	Metric Type: decimal Description: The calculated credit amount Example: -0.000024
currency (Credit Currency)	Metric Type: string Description: The currency code Example: USD
Cost
amount (Cost)	Metric Type: decimal Description: The calculated cost Example: 0.59904
currency (Currency)	Metric Type: string Description: The currency code Example: USD

Warning:

• Using Cloud Storage to store usage reports will incur minimal fees. For more information, see Cloud Storage Pricing.
• Be sure to give a unique set of names for the bucket and the prefix for each of your billing accounts. If you specify the same bucket name and prefix for multiple billing accounts, the file will be created only for one of those projects.

Related topics

• Export billing data to BigQuery
• View your cost and payment history
• Create, modify, or close your billing account