Cloud Billing reports and the BigQuery billing export are the two halves of cost visibility on Google Cloud. The built-in Cloud Billing reports give you fast, visual answers in the console, while the BigQuery billing export gives you the raw, queryable detail you need to allocate spend, build chargeback, and catch anomalies. You cannot run a serious FinOps practice on one without the other, and getting the export switched on early is the single most important setup step.
This article links up to our complete guide to Google Cloud cost optimization, the pillar for this cluster. Visibility is the See step of our See, Cut, Lock, Run method: every dollar needs an owner before you can cut anything. The query techniques that keep the export itself cheap are in how to reduce BigQuery storage and query costs.
The export is not retroactive. It only captures data from the moment you enable it, so a billing account without export is silently losing the history you will want later. Enable detailed usage cost export before you need it.
What Cloud Billing reports do well
The Cloud Billing reports page in the console is the fast path. It lets you slice spend by project, service, SKU, location and label, view trends over time, and group costs to see what is driving the bill this month without writing a query. It is ideal for quick investigation, sharing a chart with a stakeholder, and spotting a sudden jump. Its limits are that it is interactive rather than programmatic, retention and granularity are bounded, and you cannot join it to your own business data such as revenue or customer counts.
What the BigQuery billing export adds
Enabling the billing export streams your Cloud Billing data into a BigQuery dataset, where every cost row is queryable with SQL. There are two exports worth enabling: standard usage cost, and detailed usage cost, which adds resource-level granularity so you can see cost down to individual resources. Once it lands in BigQuery you can write recurring queries for chargeback by label, blended versus list rates, credit and CUD attribution, and trend analysis, and you can join cost to your own tables to compute true unit cost such as cost per customer or per transaction. This is the foundation for showback and chargeback.
Want every Google Cloud dollar accounted for?
Our Google Cloud cost audit stands up the billing export, builds the allocation queries, and turns raw cost rows into an owner for every dollar and a list of ranked savings. On the performance model, you pay only from realized savings. No savings, no fee.
Book a GCP cost audit →How to set up the BigQuery billing export
In the Cloud Billing account, open Billing export, choose a BigQuery dataset to receive the data (create one in a dedicated project if you do not have it), and enable both standard and detailed usage cost export. Set the dataset location deliberately, since export queries run against it. Grant the FinOps and finance teams read access to the dataset, and partition or schedule your analysis queries so you are not re-scanning the full export on every run. Within a day or two you will have rows flowing, and from then on every cost is in SQL reach.
Turning the export into action
Raw rows are not the goal; decisions are. Build a small set of standing queries: spend by team label this month versus last, top ten SKUs by growth, untagged and unallocated spend, and CUD and sustained use discount coverage. Feed the untagged total into your governance work, since anything you cannot allocate is spend without an owner, the same problem we tackle in committed use discounts explained when deciding what baseline is safe to commit. Set budgets and alerts on top so the data drives a notification, not just a dashboard nobody opens.
| Question | Use |
|---|---|
| What is driving this month's bill? | Cloud Billing reports (console) |
| Quick chart for a stakeholder | Cloud Billing reports |
| Chargeback by team or product | BigQuery billing export (detailed) |
| Cost per customer / unit cost | Export joined to business tables |
| CUD and credit attribution | BigQuery billing export |
| Untagged / unallocated spend | BigQuery billing export |
Console reports and export behavior reflect Google Cloud as of May 2026; verify current setup steps in the Cloud Billing documentation.
The Google Cloud Cost Optimization Field Guide includes the billing export setup steps and the standing allocation queries we deploy on every engagement. It is the downloadable companion to this guide.
Common questions about Google Cloud billing data
Does the BigQuery billing export cost anything?
Enabling the export itself is free. You pay only for the BigQuery storage the exported data occupies and for the queries you run against it, both of which are small relative to the spend you are analyzing. Keep query cost down with partitioned, scheduled analysis rather than re-scanning the full export each run.
Is the billing export retroactive?
No. The export only captures data from the moment you enable it, so it cannot backfill history from before it was switched on. Enable both standard and detailed usage cost export early, even before you need it, so the history is there when you do.
What is the difference between standard and detailed export?
Standard usage cost export gives you cost broken down by service, SKU and project. Detailed usage cost export adds resource-level granularity, so you can attribute cost to individual resources, which is what you need for accurate chargeback and fine-grained anomaly detection.
The short version
Use Cloud Billing reports for fast, visual answers in the console, and enable the detailed BigQuery billing export to get queryable, resource-level data for chargeback, unit cost and anomaly detection. Turn the export on before you need it, build a small set of standing queries, and drive budgets and alerts from the data. When you want every dollar allocated and the savings ranked, that is what our Google Cloud cost optimization service delivers.