3.3 Billing Accounts, Project Linking & Billing Exports
Key Takeaways
- A billing account can be linked to many projects, but a project can be linked to only one billing account at a time.
- Self-serve billing accounts are postpay via card/ACH; invoiced accounts accrue costs and receive one monthly invoice paid by check or bank transfer.
- Only a Billing Account Administrator can contact Cloud Billing Support; Billing Account User plus a project-level role (or Project Billing Manager) is what actually links a new project.
- Billing export to BigQuery is configured only in the Cloud Billing console, never via gcloud, and offers Standard usage cost, Detailed usage cost (resource-level), and Pricing data tables.
- Choosing a multi-region BigQuery dataset back-fills billing export data retroactively to the start of the prior month; a single-region dataset only captures data from the day export was enabled.
Billing Accounts, Project Linking & Billing Exports
Quick Answer: A Cloud Billing account is the payment container that pays for one or more Google Cloud projects. The ACE exam guide's Section 1.2 names three specific skills here — creating billing accounts, linking projects to a billing account, and setting up billing exports — and each has concrete rules the exam tests directly (one project ↔ one billing account; billing exports are console-only, not gcloud).
Why This Matters on the Exam
Billing questions on the ACE exam are rarely about pricing math — they're about structure and process: who can link what to what, which role does which job, and where a given billing task is actually performed. Getting the cardinality rule (many projects to one billing account, but one billing account per project) and the console-vs-CLI distinction wrong is one of the most common practice-test mistakes.
Two Billing Account Types
| Type | How you pay | Typical use |
|---|---|---|
| Self-serve (online) | Postpay via credit/debit card or ACH direct debit, charged automatically each billing cycle | Individuals, startups, most new accounts |
| Invoiced | Costs accrue, then one monthly invoice is issued; paid by check or bank transfer | Larger enterprises with an approved agreement, typically requiring minimum spend |
Every new user can start a Free Trial billing account preloaded with $300 in Welcome credit valid for 90 days — no usage is charged against a real payment method until the trial is explicitly upgraded to a paid self-serve account.
The Cardinality Rule (Frequently Tested)
- One billing account can be linked to many projects — this is how organizations centralize payment while keeping engineering isolation between projects.
- One project can be linked to only one billing account at a time. Unlinking and relinking is possible, but a project never pays from two accounts simultaneously.
- If a billing account is closed, suspended, or unlinked from a project, running resources (like Compute Engine VMs) are stopped, not deleted — you cannot create new resources or new projects tied to that account until billing is resolved, but existing data isn't destroyed.
Billing IAM Roles
| Role | What it can do |
|---|---|
| Billing Account Administrator | Full owner of the billing account: manage payment instruments, configure exports, view costs, link/unlink projects, manage other users' access. Only Administrators can contact Cloud Billing Support. The account creator is an Administrator by default. |
| Billing Account User | Grants the ability to attach a new project to this billing account, but must be paired with a project-level role (like Project Billing Manager or Owner) to actually complete the link. |
| Billing Account Costs Manager | Cost governance and budget visibility without payment-instrument or account-management access. |
| Billing Account Viewer | Read-only visibility into cost and transaction data. |
| Project Billing Manager | Granted at the project level; lets someone link/unlink that specific project's billing without granting any other project resource permissions. The built-in Project Owner role is a superset of this. |
To link a new project to a billing account, a user typically needs either Billing Account User (on the account) or Project Billing Manager (on the project) — the exam has directly tested this "either/or" framing.
Billing Exports to BigQuery
Cost data export is configured entirely in the Cloud Billing console (Billing → Billing export) — there is no gcloud command for setting this up, which is a deliberate ACE distractor (a common wrong option is gcloud billing export bigquery or similar, which does not exist). Three tables can be produced:
| Export type | BigQuery table name pattern | Granularity |
|---|---|---|
| Standard usage cost | gcp_billing_export_v1_<BILLING_ACCOUNT_ID> | Aggregated by service/SKU — good for monthly reporting |
| Detailed usage cost | gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID> | Everything in Standard, plus resource-level identifiers (e.g., a specific VM or disk) — needed for per-resource chargeback |
| Pricing data | cloud_pricing_export | List pricing/SKU rates, independent of your actual usage |
A subtlety worth remembering: if the destination BigQuery dataset is in a multi-region location (US or EU), Cloud Billing back-fills data retroactively from the start of the previous month. If the dataset is in a single supported region, data is only available starting from the day export was enabled — nothing is back-filled. Choosing the dataset location has a real, testable consequence.
Exam Scenario
A finance team wants to build a chargeback report that shows the exact daily cost of each individual Compute Engine VM and Persistent Disk, broken down by resource, not just by service. The correct configuration is the Detailed usage cost export to BigQuery (not Standard, which only aggregates to the service/SKU level) — configured through the Cloud Billing console, since no CLI path exists for enabling export.
Common Traps
- Assuming a project can be linked to more than one billing account "for redundancy" — it cannot; only one at a time.
- Trying to script billing export setup with
gcloud— export configuration lives only in the console/API, not the CLI surface tested elsewhere in ACE. - Confusing Billing Account User (an account-level grant) with Project Billing Manager (a project-level grant) — they solve the same linking problem from two different scopes.
- Picking Standard usage export when a scenario explicitly asks for per-resource cost detail — that requires Detailed usage cost export.
How many Cloud Billing accounts can a single Google Cloud project be actively linked to at one time?
A financial analyst asks for a report showing the daily cost of every individual Persistent Disk and VM by resource ID, not just aggregated by service. Which billing export should be configured?
Which IAM role is required to contact Google Cloud Billing Support directly about a payment issue?