Overview
You grant Cloud Capital the permissions to move billing for the projects you choose, and Cloud Capital handles the rest: it takes responsibility for the Google Cloud invoices of those projects, pays Google for that usage, and invoices you with the discount in your agreement. You keep your Google Cloud organization, projects, IAM, and workloads. This is how cashback works for Google Cloud. Billing moves project by project, by changing the Cloud Billing account linked to each project. The steps are the same whether Cloud Capital bills you in the US or the UK. Your Cloud Capital contact confirms the payer account for your agreement. This page explains how that works with Cloud Capital, what changes, what stays the same, and how to complete the move.How GCP billing with Cloud Capital works
At a high level:- You and Cloud Capital sign the order form and agree which projects move.
- Cloud Capital arranges a payer billing account for your company and tells you the account name and ID when it is ready to use.
- You grant Cloud Capital permission to link those projects to that billing account, and Cloud Capital links them for you — including projects you create later. If you’d rather link the projects yourself in the Google Cloud console, that’s available too; your Cloud Capital contact confirms which path you are on.
- From then on, Google bills later usage on those projects to the Cloud Capital payer account. Cloud Capital pays Google and invoices you.
- The project’s billing account changes. The project, its resources, and its place in your organization stay put.
- Workloads keep running. Google Cloud documents that switching a project’s Cloud Billing account should not interrupt service.
- For the console steps, see How to change the project’s billing account. The roles that can do it are in Permissions required to change the billing account.
What changes versus what stays the same
1. Billing and payments
What changes- Usage incurred on a moved project after the change is invoiced by Cloud Capital, with the discount in your agreement. You pay Cloud Capital for that usage from the change onward.
- Charges already incurred stay on the previous billing account, including charges Google can take up to two days to report. In Google’s example, a project moved on May 15 is billed to the old account through May 15 and to the new account from May 16. Settle those earlier charges on the previous billing account.
- Charges that are not tied to a project, such as a support plan on the old billing account, stay on that account. Cloud Capital reviews them with you before the move.
- Payment terms, currency, and payment method are the ones in your Cloud Capital order form. Customers billed directly by Cloud Capital also complete Compliance Onboarding so the credit review and payment method are in place.
- Linking a project to a new billing account leaves the project in your organization.
- Projects you leave unchanged stay on their current billing account and are absent from the Cloud Capital invoice.
- Invoices already issued for usage before the change stay with the previous billing account.
2. Infrastructure, security and access
What changes- The Google admin email you give Cloud Capital receives Billing Account Administrator on the new payer billing account, so that admin can link projects to it. The role applies to that payer account.
- If Cloud Capital will link the projects, you grant a separate identity two roles on your organization:
roles/billing.projectManager(link projects to the payer account) androles/browser(find the projects). That identity cannot change resources or read your data. The grants are in Integrate GCP Data, and the access model is in Security.
- Cloud Capital does not become an owner or administrator of your organization, folders, or projects.
- Cost data is read by a different, read-only identity, and only after you connect the integration. Permission to read cost data is separate from permission to change billing. See Integrate GCP Data.
- Your IAM policies, organization policies, and VPC Service Controls stay as you set them.
3. Commitments, subscriptions, and marketplace
Review this section with your Cloud Capital contact before any project changes billing. Several Google Cloud purchases stay on the billing account or need their own move. Spend-based committed use discounts. These are purchased on a Cloud Billing account and apply to eligible usage in the projects that account pays for. Moving a project leaves the commitment, and its fee, on the previous account, and the moved project is no longer covered. Tell Cloud Capital about every active spend-based commitment, including Compute flexible commitments, Flexible Savings Plans, and service-specific commitments such as BigQuery, Cloud SQL, and Spanner. The full list is in Google’s CUD documentation. Cloud Capital reviews each one with you and agrees how coverage continues before the projects move. The commitment does not move on its own. Resource-based committed use discounts. These are Compute Engine commitments purchased in a project. They stay with that project. After the billing change, their discounts apply on the Cloud Capital payer account starting at midnight US and Canadian Pacific Standard Time (UTC−8). If the payer account’s CUD sharing differs from your current account, a discount that covered other projects may cover only the moved project, or the reverse. Prioritized attribution may need an update. Google documents how a billing change affects resource-based CUDs. Reservations. Include reservations in the same review. A billing-account change can affect them. Google Cloud Marketplace. A project with Marketplace purchases cannot move until those purchases are moved. Google requires that move first so the project is not disabled and does not lose data. Tell Cloud Capital about Marketplace purchases before the billing change. The steps are in Change which Cloud Billing account you’re using for an active order. Other subscriptions. Changing the billing account does not move subscriptions such as Security Operations or Looker. Products with their own billing setup, including Cloud Armor Enterprise Annual and Gemini API in AI Studio prepay, can change behavior when the billing account changes. List them with your Cloud Capital contact so they are handled first. Maps Platform, Firebase, and AI Studio. The destination billing account has to support every product the project pays for. A project that also pays for Maps Platform needs a billing account that supports both Google Cloud and Maps Platform. Cloud Capital confirms this on the payer account before you start.Onboarding flow with Cloud Capital
1
Prepare
You and Cloud Capital agree which projects move, and review commitments, reservations, Marketplace purchases, support, and any private pricing. You name the Google admin email that should administer the new payer billing account, and you sign the order form.To have cost history from before the move in Cloud Capital, connect your current billing export with Integrate GCP Data. Google writes export rows from the day an export is enabled, so an export that is already running is the one that carries history.
2
Payer billing account
Cloud Capital arranges the payer billing account and confirms when it is ready, including the account name and billing account ID to select. The named Google admin is granted Billing Account Administrator on that account. Leave every project’s billing as it is until you have that confirmation.
3
Link the projects
Use the path your Cloud Capital contact specifies.Cloud Capital links the projects. This is the default path. When Cloud Capital has enabled this for your organization, open the GCP integration in the Cloud Capital app under integrations and turn on Let Cloud Capital change project billing. An Organization Administrator grants
roles/billing.projectManager and roles/browser on your organization to the principal shown there. Folder-level grants are supported; projects outside the granted folders stay where they are. If Domain Restricted Sharing rejects the grant, an Organization Policy Administrator allow-lists Cloud Capital’s customer ID. The setup page shows that ID and the commands. Cloud Capital then moves the eligible projects and confirms when it is done.While those grants remain, Cloud Capital also links projects you create later, and projects later pointed at another billing account, to the payer account.You link the projects yourself. If you’d rather not grant Cloud Capital those permissions, you can link the projects directly instead. In the Google Cloud console, open Billing → Account management for your current billing account. On each project row, open the actions menu, select Change billing, choose the payer account Cloud Capital named, read the warnings, and select Set account. Repeat for every project that should move.You need permission to unlink the project from the current billing account and to link it to the payer account. The predefined roles that cover this are Project Owner on the project (or Project Billing Manager, Project Browser, and Service Usage Viewer together), and Billing Account Administrator on both billing accounts (or Billing Account User and Billing Account Viewer together). Billing Account Administrator on your own organization does not extend to the Cloud Capital payer account; the admin email Cloud Capital nominated is granted that role on the payer account directly.If Change billing is missing, one of those roles is missing. If a lock icon appears beside the project, unlock the billing link before changing it. Google may ask you to sign in again; changing a billing link is a sensitive action. The console path is in How to change the project’s billing account. The full permission table is in Permissions required to change the billing account.4
Go live
Tell your Cloud Capital contact when you have linked the projects, or wait for confirmation when Cloud Capital linked them. Later usage on those projects is on your Cloud Capital invoice. Usage from before the change stays on the previous billing account. You do not create a billing export on the payer account. Cloud Capital reads usage billed there.
5
Operate
You keep running Google Cloud as before. A new project is on the Cloud Capital invoice when you link it to the payer account at creation, or when the grants above are in place. Invoices, currency, and the discount follow your agreement.
Common questions
Will I lose control of my Google Cloud organization or projects?
Will I lose control of my Google Cloud organization or projects?
- You keep your Google Cloud organization, projects, IAM, and infrastructure.
- The identity that changes billing can link projects to the payer account. It cannot change resources or read data.
- You can point projects back at a billing account you control with the same Change billing action. Revoke the roles that let Cloud Capital change billing first if you granted them. While they remain, Cloud Capital keeps projects on the payer account.
- A reversal has the same commitment and Marketplace constraints as the original move. Plan it with Cloud Capital so a commitment is not left on an account that no longer pays for the usage.
What can Cloud Capital actually access?
What can Cloud Capital actually access?
- The grants that let Cloud Capital change billing allow Cloud Capital to find projects and change which billing account pays for them.
- Cost and usage data is read by a separate identity, and only if you connect Integrate GCP Data.
- Neither identity reads application data, workloads, or logs.
- You can remove either set of grants at any time. Removing them stops further reads or further moves. A project that is already on the payer account stays there until its billing account is changed. See Security.
What happens to my existing discounts and commitments?
What happens to my existing discounts and commitments?
- The cashback discount is the discount in your Cloud Capital agreement, applied to usage Cloud Capital bills.
- Existing commitments keep their term. Spend-based commitments stay on the billing account that holds them until that coverage is moved. Resource-based commitments stay on the project.
- Cloud Capital reviews private pricing, Marketplace purchases, and support with you before the move, because they can change what the discount covers. Your order form states your rate and any exclusions.
Who's the seller of record, and how does invoicing work?
Who's the seller of record, and how does invoicing work?
- Cloud Capital is the seller of record for usage on the moved projects from the change onward.
- Invoicing, currency, and tax treatment are set in onboarding and in the order form.
- Charges from before the change, and charges that were never on the moved projects, remain on the previous billing account.
What happens to my cost history and reporting?
What happens to my cost history and reporting?
- The billing change leaves cost history already in Cloud Capital, and in a billing export you own, in place.
- Google does not backfill a newly enabled export. History from before the move comes from an export that was already running, connected as in Integrate GCP Data.
- After the move, usage on the payer account continues in Cloud Capital. You do not configure a second export for that account.
- You can remove the read-only integration and leave billing where it is. You can also move billing back and keep the history Cloud Capital already stored.
Does my relationship with Google Cloud or my support plan change?
Does my relationship with Google Cloud or my support plan change?
- You keep your organization and your projects, and you keep using the Google Cloud console to run them.
- You remain responsible for the environment. Cloud Capital handles billing, payment, and the contracted discount for the projects that moved.
- A support plan purchased on the previous billing account stays on that account. Tell Cloud Capital if you rely on it, so support is arranged before the move.
Summary
Moving Google Cloud billing under Cloud Capital’s management lets you:- Keep your organization, projects, IAM, and workloads
- Move payment for the projects you choose to Cloud Capital, and receive the cashback discount in your agreement
- See that spend in forecasting and cost insights once the GCP integration is connected
- Move projects back to a billing account you control, after revoking any grants that let Cloud Capital change billing
Onboarding via AWS Billing Transfer
The same commercial model on AWS, using AWS Billing Transfer.
Integrate GCP Data
Read-only cost access, and the optional grants that let Cloud Capital link projects.
Security
What the forecasting identity and the identity that changes billing can each do.
Compliance Onboarding
Credit review and payment method when Cloud Capital bills you directly.

