Check your BigQuery target before enabling billing export
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Avoid a failed save and missing cost history by checking the target dataset before enabling or moving Cloud Billing export. For first-time Standard or Detailed usage-cost exports, choose EU or US when current and previous month data matters.
What you need first
- Tool
- Google Cloud console is Google's web interface for managing resources and billing. Start at Billing export, choose the source Cloud Billing account, then review the BigQuery export tab without saving changes.
- Access
- If you cannot view the target dataset or project, ask an authorized dataset owner and billing administrator to return the read-only results for the named scope. Use the documented configuration roles only when enabling export.
- If you do not use that tool
- Send the dataset owner and billing administrator the project ID, dataset ID, source billing account, and export type. Request each checklist result, unresolved item, and owner before configuration.
Why this is worth a look
An unsupported dataset region causes an Invalid dataset region error and prevents settings from being saved. A supported single region starts usage-cost data at enablement, without earlier data. The target project must have billing enabled and be linked to the same billing account. Pricing export also requires the BigQuery Data Transfer Service API in that project.
Run this check
CHECKLISTUse this checklist in the Google Cloud console or ask authorized colleagues to complete it. Scope one target dataset, its project, and its source billing account. It calculates no costs or usage.
Scope:
- Target project ID:
- Target dataset ID:
- Source Cloud Billing account:
- Export type: Standard usage cost / Detailed usage cost / Pricing data
- Initial enablement, re-enablement, or move:
- Required reporting history:
Read only. Do not create resources, enable APIs, change permissions, or save export settings.
[ ] Open Billing export, choose the source billing account, and review the BigQuery export tab. For an existing export, record the current target separately from the proposed target.
[ ] Ask the dataset owner for the target location. Confirm EU, US, or a supported region in the setup guide. Mark an unconfirmed location unresolved.
[ ] Record whether history meets the need. EU or US gives current and previous month usage-cost data on first enablement. Supported single-region locations and Pricing data do not provide retroactive data.
[ ] Ask the dataset owner whether encryption is Google-managed or CMEK. For CMEK, confirm dataset-level enablement and review the setup guide's encryption limitations.
[ ] Ask the billing administrator to confirm billing is enabled on the target project and that it is linked to the source billing account.
[ ] For Pricing data, confirm the BigQuery Data Transfer Service API is enabled in the target project.
[ ] Ask the configurator to confirm the documented permissions for the selected export type.
[ ] For an existing export, ask the owner to confirm the Google-managed export service account remains on the dataset. If row-level security is used, request confirmation that [email protected] has full-table access.
[ ] Record unresolved items and owners. Do not configure export until requirements and history expectations are resolved.How to confirm it
- 01
Define the target and history need
Record the target project, dataset, source billing account, export type, and whether this is initial enablement, re-enablement, or a move. State the earliest usage date your reports need.
- 02
Choose the dataset location
Choose EU or US for first-time Standard or Detailed usage-cost history covering the current and previous month. Otherwise confirm the location is supported. Dataset location cannot change after creation, so an unsuitable target requires another dataset.
- 03
Resolve dataset and project requirements
Complete the read-only checklist with the dataset owner and billing administrator. Confirm encryption, project billing and linkage, the Pricing API when applicable, service-account continuity, and any row-level security access. Assign every unknown or unmet item.
- 04
Confirm configuration permissions
For usage-cost export, confirm Billing Account Costs Manager or Billing Account Administrator on the billing account and BigQuery User on the target project. For Pricing export, confirm Billing Account Administrator, BigQuery Admin, and resourcemanager.projects.update on the target project.
Before making changes
This review does not enable export and assumes a target dataset already exists. EU or US backfill applies to first enablement, not re-enablement, and may take up to five days before current usage appears. Pricing data is not retroactive. Moving an export does not copy earlier data to the new dataset, so plan how reports will include it. BigQuery storage and query processing can incur usage charges.