Prepare and test your skills

Prepare and test your skills

Establishment of Billing Accounts and Payment Profiles is the setup that connects Google Cloud usage to payment. A Cloud Billing account (opens in a new tab) is the Google Cloud resource that funds usage and tracks costs for projects and organizations. Every Cloud Billing account is connected to a Google payments profile, which holds the payment instruments, billing contacts, and payment history used to pay for usage. A project must be linked to an active billing account, or cost data for its resources will be lost and create discrepancies.
Prerequisites for creating a billing account are an organization identity and the correct Identity and Access Management (IAM) permissions. A company domain establishes identity with Google through Google Workspace or Cloud Identity, which automatically creates an organization resource (opens in a new tab) as the top of the resource hierarchy. Projects and billing accounts created under that domain become child resources of the organization, so IAM access policies and organization policies are inherited down the hierarchy. Once the organization exists and permissions are granted, a new billing account can be created from the Google Cloud console billing page and then linked to one or more projects.
The creator must hold the right roles on the organization before creating billing:
All billing accounts within an organization use a single price sheet to charge service usage.
Google payments profiles and payment settings control how a Cloud Billing account is paid. A Google payments profile is the payments-side record that sits behind a Cloud Billing account in the Google payments center (opens in a new tab). The Cloud Billing account tracks which projects used what resources, while the payments profile owns how those charges are paid, including linked payment accounts and transaction history. Usage costs flow from the project to its linked Cloud Billing account, and payment for those costs flows through the linked Google payments profile.
Each Cloud Billing account also has payments contacts, which are people designated to receive billing information about the payment instrument on file, such as when a credit card needs to be updated. These contacts can be viewed and managed in the Google payments center or in the Google Cloud console. Configuring the payment account, contacts, and payment method happens on the Payment settings and Payment method pages for the billing account.
Account types for different organizational needs define who the billing account fits and how payment is collected. Most customers start with a self-serve account that pays automatically, while larger organizations may use monthly invoicing, and resellers use subaccounts to separate customer charges. The choice depends on organizational scale and payment method.
| Account type | Who it fits | How payment works |
|---|---|---|
| Self-serve account | Individual teams and smaller organizations | Pays automatically with an online payment method, such as a credit card or verified bank account |
| Invoiced billing account | Larger organizations with monthly billing | Receives a monthly invoice and pays by invoice; self-serve customers may request to change to this type if eligible |
| Cloud Billing subaccount | Resellers managing charges for customers | Behaves like a billing account with its own linked projects, exports, and IAM roles, but all usage charges are paid by the reseller's parent billing account and grouped and subtotaled on the invoice |
A subaccount allows access control to be fully separated per customer while keeping payment centralized with the parent account. Split invoicing can place subaccount charges on multiple invoices when it applies.
Exam tip: A parent Cloud Billing account must use invoiced billing to own subaccounts for resellers.
IAM Roles for Billing Administration are the Identity and Access Management (IAM) roles that control who can create and manage Google Cloud billing accounts. A billing account pays for resource usage, and IAM roles separate the ability to create a new account from the ability to manage an existing one. The two central predefined roles are Billing Account Creator (opens in a new tab), which allows creation, and Billing Account Administrator, which allows full management.
Organization requirements for billing setup are an organization resource plus specific IAM roles granted on that organization. The organization resource comes from a Google Workspace or Cloud Identity account, and each Workspace or Cloud Identity account is associated with exactly one organization resource tied to exactly one domain. All projects and billing accounts created under that domain become child resources of the organization resource, so the organization is the trust and management boundary for billing. An Organization Administrator can grant the needed roles by selecting the organization in the IAM page, granting access to a new principal by email, and selecting each role.
To set up resources under the organization, a user typically needs the following roles granted on the organization:
After the roles are granted, the user can create billing accounts that automatically belong to the same organization.
Billing Account Creator and Billing Account Administrator divide billing work by creation versus ongoing management. Billing Account Creator is granted on the organization and allows the holder to create new billing accounts inside that organization. Billing Account Administrator is normally granted on a specific billing account and allows the holder to manage that account's settings, spending controls, and lifecycle. The difference in scope matters because creation happens at the organization level while daily control happens at the billing account level.
A creator can bring a new billing account into existence, but an administrator controls what happens to it afterward, including updates, budget alerts, billing export, closing, and reopening. Most billing actions also require basic read access such as billing.accounts.get, so management roles build on viewing permission. The table below shows when to choose each role:
| Role | Where it is typically granted | Choose when |
|---|---|---|
| Billing Account Creator | Organization | The person needs to create new billing accounts for the organization |
| Billing Account Administrator | Billing account, inherited from organization if granted there | The person needs to manage settings, budgets, export, associations, and close or reopen the account |
| Billing Account Viewer | Billing account | The person needs read-only visibility such as account name, currency, and open or closed state |
Where billing permissions apply determines which hierarchy level controls each billing action and how permissions inherit downward. Most billing permissions belong on the billing account, so roles containing them should be associated with the billing account. Some permissions belong on the project instead, and when an action touches both sides, both permissions are required. Inheritance flows downward, so a role granted on the organization can affect any billing account within that organization.
Linking a project to a billing account shows this two-sided dependency. Data and control flow from the project to the billing account only after both checks pass: the caller needs billing.resourceAssociations.create on the billing account, where billing administrators control access, and resourcemanager.projects.createBillingAssignment on the project, where project owners control access. Some permissions only work at higher levels, so billing.accounts.list granted on an organization can list all billing accounts in that organization but does nothing when granted on a single billing account.
Custom roles for Cloud Billing accounts are organization-level roles that bundle only the permissions a team needs. Custom roles are created on the organization (opens in a new tab) and then can be applied to any billing account in that organization. For example, a Cost Management Administrator custom role could contain only billing.budgets.create, billing.budgets.update, and billing.accounts.updateUsageExportSpec, and when combined with Billing Account Viewer it allows budget and export management without the broader power to delete associations, cancel subscriptions, or close the account.
Exam tip: Create billing custom roles under Organization, not Project, because Project roles cannot be applied to billing accounts.
Project Linking and Account Association is the hierarchy that connects usage in projects to payment in billing accounts. A Google Cloud project (opens in a new tab) is the top-level container for cloud resources and is required to use Google Cloud services. A Cloud Billing account accrues and calculates costs for every project linked to it, and those costs are then routed to a Google payments account to pay the bill.
How billing accounts pay for projects follows a fixed flow from resources to payment. Usage flows from service resources to their parent project, from the project to its linked billing account, and from the billing account to the linked Google payments account for payment. Each billing account operates in a single currency and is connected to a Google payments profile that holds legal, address, and payment information. A project and its resources are paid for by a single billing account at a time, while one billing account can be linked to one or more projects.
A left-to-right process flow showing service resources feeding Google Cloud projects, costs tracked by one Cloud Billing account, and payment made through the linked Google payments profile and account.
Billing is enabled on a project only when the project is linked to a billing account and that account is active and in good standing, meaning it is not closed or suspended. Projects that are not linked to an active billing account cannot use Google Cloud or Google Maps Platform services, even if they only use services that are free.
Exam tip: One billing account can pay for many projects, but each project can be linked to only one billing account at a time.
Linking new projects and changing the linked account connects a project's usage to a specific billing account so that account is charged. How a new project gets linked depends on where the project is created, because different consoles handle billing differently.
| Project-creation platform | Billing account linked? | What happens |
|---|---|---|
| Google Cloud console | Yes | You are prompted to choose a billing account, or the only account is linked automatically; if you have no account, you must create one before using many paid services |
| Firebase console | No | The new project starts unlinked on the no-cost Spark plan with full free services plus limited paid-service quota |
| Google AI Studio console | No | The new project starts unlinked on the Free tier for eligible Gemini API models up to rate limits |
An existing project can be moved to a different billing account when you have access to multiple accounts. The move is done from Account management in Cloud Billing (opens in a new tab):
A locked link must be unlocked first, shown by a padlock icon, and missing permissions will prevent the Change billing option from being selected. Switching accounts should not cause service interruption or downtime, but charges already incurred before the move stay with the former account. Because services can take up to two days to report usage, the old account may still receive charges for up to two days after the change.
Using one account or multiple accounts controls financial oversight and management overhead. The recommendation is one central Cloud Billing account in the organization, because extra accounts add tracking overhead and can behave unexpectedly with committed use discounts (CUDs) and promotional credits. Ownership of a billing account belongs to a single organization for permission inheritance, but payment linkage is flexible and one billing account can pay for projects in a different organization. Reports show one billing account at a time and are not aggregated across accounts.
Multiple billing accounts are needed only for specific separation requirements:
Using separate accounts for departments or for development, test, and production gives each area its own bill and spending view, but increases management work.
A Cloud Billing account tracks which projects used what resources, while a Google payments profile owns how those charges are paid, including linked payment accounts and transaction history. Usage costs flow from the project to its linked Cloud Billing account, and payment for those costs flows through the linked Google payments profile.
Billing Account Creator is granted on the organization and allows the holder to create new billing accounts inside that organization, while Billing Account Administrator is normally granted on a specific billing account and allows the holder to manage that account's settings, spending controls, and lifecycle. Creation happens at the organization level while daily control happens at the billing account level, including updates, budget alerts, billing export, closing, and reopening.
Each Google Cloud project can be linked to only one Cloud Billing account at a time, while one Cloud Billing account can be linked to one or more projects. Billing is enabled on a project only when the project is linked to a billing account that is active and in good standing, meaning it is not closed or suspended.
Charges already incurred before the move stay with the former Cloud Billing account, and the old account may still receive charges for up to two days after the change because services can take up to two days to report usage. Switching accounts should not cause service interruption or downtime.
An enterprise is setting up access control for its Google Cloud financial operations and needs to assign appropriate Identity and Access Management (IAM) roles to two team members:
Following the principle of least privilege, which predefined IAM roles should you assign to these users?
Last updated