The dataset is not linked to a billing account" - BigQuery export agent blind

TL;DR

The BigQuery dataset exists but no billing account exports into it, so the agent's queries return nothing. In the Cloud Console, open Billing Export settings for the billing account and link it to the dataset (or create the export fresh). The dataset is just a container; the billing account linkage is what fills it.

Error

"The dataset is not linked to a billing account"  -  BigQuery export agent blind

Steps

1. Confirm the state: the dataset exists in BigQuery but has no billing tables. Expected: the dataset is empty of billing data.
2. Open the billing account's Billing Export settings in the Cloud Console. Expected: the export shows as not configured or linked elsewhere.
3. Enable standard (or detailed) usage cost export to the dataset. Expected: the linkage saves successfully.
4. Wait for the first export files to land (up to a day for the initial backfill window). Expected: billing tables appear in the dataset.
5. Point the agent at the tables and verify queries return data. Expected: the agent's billing queries work.

When to use

• BigQuery billing queries fail because the dataset is not linked.
• A new dataset was created but export was never enabled.
• The agent was pointed at the wrong dataset.

When not to use

• The dataset is linked but queries get permission denied (an IAM problem).
• Export is linked but data is stale (a pipeline-delay problem).
• The billing account itself is suspended.

Tool compatibility

Google Cloud Billing export to BigQuery (current 2026 releases).

Variant phrasings

bigquery billing tables missing

Check the billing account's export linkage, not just the dataset.

export dataset empty in bigquery

The linkage was never completed. Enable it on the billing account.

agent queries return no billing data

Verify the export linkage before debugging the queries.

Why it happens

Billing export is configured on the billing account side, not the dataset side: creating the dataset is only half the setup. It is easy to create the container, point the agent at it, and never complete the linkage, leaving the agent querying an empty dataset. The error message is precise about the missing piece, which makes this a configuration completion task.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstESRZHM2Xdx0qYHHiChWuw