Review CUD sharing and billing-account scope

Why this is worth a look

Resource-based CUD sharing is only available for Compute Engine commitments purchased for hardware resources. When the Cloud Billing account scope is Billing account, eligible resource usage across linked projects can consume commitments purchased in any project on that account. Commitment-level attribution then controls how fees and credits are applied in billing reports. Spend-based CUDs are different: they are pooled at the Cloud Billing account level and always use proportional attribution, so they do not have separate CUD sharing settings. Use this review when you need to compare project costs without mixing up account scope and per-commitment attribution.

Use the Google Cloud console and billing reports to record account scope, commitment attribution, and project allocation without changing settings. The checklist is read-only, uses the selected billing account and a named reporting period, and has no external query columns.

Assumptions
[ ] The selected Cloud Billing account is the account under review.
[ ] The report period is recorded before comparing project costs.
[ ] You have permission to view the billing account, commitments, and billing reports.
[ ] The review covers Compute Engine resource-based commitments purchased for hardware resources.

1. Review account scope
[ ] Open the billing account's Committed use discounts (CUDs) page.
[ ] Select the target Cloud Billing account.
[ ] Open CUD scope & settings.
[ ] Record the Resource-based CUDs scope: Project or Billing account.

2. Review each relevant commitment
[ ] For each relevant resource-based commitment, open View Analysis, then Configure Attribution.
[ ] Record that commitment's attribution: proportional or prioritized.
[ ] Treat attribution as applicable only when CUD sharing is enabled.

3. Review eligibility boundaries
[ ] List the projects linked to the selected Cloud Billing account.
[ ] Identify projects with eligible resource usage and active resource-based commitments.

4. Review reported allocation
[ ] In billing reports, group by Project and filter by the relevant SKU.
[ ] Review the displayed commitment fees and credits for each project.
[ ] Record the selected report period, billing account, projects, commitments, scope, and commitment-level attribution.
[ ] If the scope changed recently, record the change and its documented effective timing: 12:00 AM US and Canadian Pacific Time the following day when enabling Billing account scope, or within a few moments when changing to Project scope.

How to confirm it

1. 01

   Open the billing account view

   Open the billing account's Committed use discounts (CUDs) page in the Google Cloud console and select the Cloud Billing account under review. This identifies the account whose commitments and scope you are evaluating.

2. 02

   Record account-level scope

   Open CUD scope & settings and record whether Resource-based CUDs use Project or Billing account scope. Project scope keeps a commitment within its purchasing project. Billing account scope applies resource-based CUDs across projects linked to the account.

3. 03

   Inspect each commitment's attribution

   For each relevant resource-based commitment, use View Analysis, then Configure Attribution. Record whether that commitment uses proportional or prioritized attribution. Keep this record separate from the account-level scope, and note that attribution applies when CUD sharing is enabled.

4. 04

   Check project boundaries and reports

   List projects linked to the billing account and identify eligible resource usage and active resource-based commitments. In billing reports, group by Project and filter by the relevant SKU for a named period, then review the displayed commitment fees and credits for each project before comparing project allocation.

5. 05

   Check scope-change timing

   For a recent scope change, record when it was made and compare it with the documented effective timing. Enabling Billing account scope takes effect at 12:00 AM US and Canadian Pacific Time the following day. Changing to Project scope takes effect within a few moments.

Primary sources