Cloud Billing release notes

New filter and group-by option available in Cloud Billing Reports

In Billing Reports, Cloud Billing has added the Originating products filter and Group by to provide additional options that let you analyze and understand your costs. Originating products are Google Cloud products that cause usage in another product. For example, Gemini Enterprise is an originating product when it causes usage in the Gemini Enterprise app.

To help you track and analyze your AI spend, the Originating products dimension is used in the following ways:

• You can use the Originating products filter and group by option to configure your Cloud Billing report to track and analyze your Gemini Enterprise subscription and consumption costs.

• The Originating products dimension supports a new preset report for quick report configuration, called Gemini Enterprise costs by SKU.

• When you are viewing your costs in the Gemini Enterprise console, on the Gemini Enterprise > Usage & Spending page, the Originating products dimension supports the functionality of the costs displayed on the Gemini Enterprise Billing tab.

For more information, see the following resources:

• Learn how to view Gemini Enterprise costs in Cloud Billing reports
• Learn more about analyzing billing data and cost trends with Reports
• Learn how to view Gemini Enterprise costs in the Gemini Enterprise console

Spend cap budgets are now available for a limited set of services (Preview)

Available in Preview for eligible services, you can now configure a spend cap budget to automatically pause usage when your spend exceeds the budget amount you set.

Spend caps are a cost control mechanism. A spend cap is enforced when usage costs exceed your budget target amount. When enforced, any new request to the eligible services, within the specified project, are paused and no further usage costs are accrued until you manually lift the spend cap.

Spend caps typically use estimated costs to trigger the alerts and caps, enforcing a cap much faster than the actual costs are processed and appear on billing reports. Even though faster than reports, the enforcement of spend caps isn't instant and any cost overages are billed as normal.

For more information about spend cap budgets, see:

• How spend cap budgets work to help you control spend
• Configure a spend cap budget
• Lift an enforced spend cap
• Limitations of spend cap budgets

Early signals for AI workloads

For AI workloads (such as Gemini API and Vertex AI), you can now view early anomalies. Early anomalies use near real-time cost estimates to provide daily, service-level insights before finalized billing occurs. You can view these alerts on the By service (Early signals) tab on the Anomalies dashboard in the Google Cloud console. User-configured thresholds do not apply to early anomalies.

For more information, see View early anomalies for AI workloads.

Payments documents for invoiced billing accounts available on Payment status page

For Cloud Billing accounts that are paid by invoice, access to your payments documents, such as invoices and credit memos, is now available in the Cloud Billing console in the Payment status page.

The Payment status page replaces the Invoices page. Self-service (online) Cloud Billing accounts will continue to access Payments documents on the Invoices page.

The Payment status page provides a real-time and customizable view of your financial standing with your Cloud Billing account. The Payment status page is based on the Google payments Statement of account page, with your payments documents filtered by the Google payments account that is linked to the Cloud Billing account that you are viewing.

For more information about payments documents, see:

• Get a Cloud Billing document such as an invoice, statement, or receipt
• View your cost and payment history
• Google payments Statement of account

Resource-based CUD recommendations available for Compute Engine GPUs, Local SSD disks, and OS licenses

Resource-based committed use discount (CUD) recommendations are generally available (GA) for GPUs, Local SSD disks, and premium operating system (OS) licenses.

CUD recommendations provide insight into any additional commitments that you can purchase to optimize the costs of the resources that you run. You can use these recommendations and purchase commitments for resource usage that isn't covered by commitments and is being charged at list prices. Google Cloud analyzes your compute instance spending trends with and without a commitment and generates CUD recommendations on a monthly basis.

For more information about how CUD recommendations are generated, what resource types are supported, and how to use recommendations to purchase commitments, see Get recommendations for committed use discounts (CUDs).

CUD dashboard redesign available (preview)

The redesigned CUD dashboard is available in the Billing section of the Google Cloud console. It provides a consolidated view of all your resource-based and spend-based CUDs in a single place. The new design improves usability and scalability, helping you find information faster.

For more information, see View your commitments.

New filters and group-by options available in Cloud Billing Reports

Cloud Billing has added two filters to the Billing Reports page to help you analyze and understand your costs:

• Products: Google Cloud Products consist of a group of SKUs (potentially from more than one Google Cloud Service) that work together and are sold as a single service, sometimes referred to as a logical product family or a subscription service. Examples include Gemini Enterprise and Firebase App Hosting.

• Originating services: An Originating service is a Google Cloud service that causes usage in another service. For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine. In this use case, when you are viewing the Compute Engine usage and costs, GKE is an originating service when it causes usage in Compute Engine.

You can also Group by the new filters, to summarize your costs by the dimension you select.

• Product: When you group by Product, the Report shows your costs and savings summarized by Product.
• Originating service > Service: When you group by Originating service > Service, the Report shows your costs and savings summarized by Originating service. In the report table, you can expand each row for an Originating service to see your costs summarized by each Service that is associated with the Originating service.

Learn more about analyzing billing data and cost trends with Reports.

Learn how to view Gemini Enterprise costs in Cloud Billing reports.

Multi-project access to Cloud Billing cost views available in Preview

In Cloud Billing accounts, multi-project access to usage costs lets project owners, solution owners, developers, and other non-billing admins see cost data for all of their authorized projects in a single view in the Cloud Billing console.

The multi-project view uses a combination of Cloud Billing account permissions and Google Cloud project permissions that let Cloud Billing administrators and organization administrators jointly control access to project-level cost data.

Using project-scoped Cloud Billing account permissions, Cloud Billing administrators can control which solution owners can view aggregated cost data in the Cloud Billing console.

• Learn more about cost management for project owners.
• Learn how to set up multi-project access to costs views.

FOCUS billing data export to BigQuery available in Preview

Cloud Billing data export to BigQuery now offers a FOCUS billing data export available in Preview. The FinOps Open Cost and Usage Specification (FOCUS) is an open specification that defines clear requirements for technology billing data generators to produce consistent cost and usage datasets. The Google Cloud billing data export using the FOCUS specifications includes FOCUS columns up to FOCUS version 1.2.

For more information about the FOCUS billing data export to BigQuery, refer to the following documentation:

• Set up FOCUS Cloud Billing data export to BigQuery
• Structure of the FOCUS data export
• FOCUS conformance report
• Query examples for FOCUS use cases

CUD Analysis is Generally Available

CUD Analysis has reached general availability (GA). This tool supports the new spend-based CUD model and provides a unified interface for customers to examine both spend-based and resource-based CUDs. It offers a consolidated view of Compute resources including the benefits of both resource-based and spend-based CUDs.

You can use this tool to do the following:

• Understand savings: Understand the financial impact of your commitments.
• Track key metrics: Track how effectively your commitments are being used.
• Download data: Download a CSV file of your daily usage for offline analysis and reporting.

For more information, see Analyze the effectiveness of your CUDs.

The AI Cost Summary Agent is now available in Preview

You can now use the AI Cost Summary Agent to analyze your AI costs and gain critical insights into your AI-related spend. The agent analyzes spending related to Gemini usage, including Gemini API and Vertex AI.

This feature is available as a widget on the Billing Overview page for your Cloud Billing account.

For more information, see Analyze your AI spend with the AI Cost Summary Agent.

GKE workload recommenders now available in the FinOps hub

You can now view recommendations for right-sizing overprovisioned workloads and optimizing underprovisioned workloads for Google Kubernetes Engine (GKE) clusters directly in the FinOps hub.

For more information, see Optimize workload resource utilization.

Scenario modeling for CUD recommendations is generally available

Scenario modeling for committed use discount (CUD) recommendations is now generally available (GA). You can simulate scenarios for both spend-based and resource-based CUDs, and customize recommendations to purchase a commitment that maximizes your savings.

For more information, see Simulate scenarios for CUDs savings.

Billing account permissions now streamline access to Google payments profiles and payments accounts

We've launched a billing IAM permissions update that simplifies and streamlines Cloud Billing account access to the associated Google payments profiles and accounts, for users who have the billing.accounts.updatePaymentInfo permission on their Cloud Billing account.

Prior to this update: While working in the Cloud Billing console, to access and edit the associated Google payments profile and account information, all Cloud Billing account users needed two sets of permissions:

• Identity and Access Management (IAM) permissions on the Cloud Billing account to access and manage the billing account.
• Edit or Admin access permissions on the associated Google payments profile in order to add and edit payment methods, make a manual payment, and update payments profile info such as the business name, address, tax info, and payments account settings.

After this permissions update: Cloud Billing account users with the billing.accounts.updatePaymentInfo permission on the billing account can access and edit Google payments profile and account information directly from the Cloud Billing console, without needing additional permissions on the payments profile itself. This includes users with the Billing Account Administrator role (roles/billing.admin) and those granted this permission via a custom role.

Note that this permissions update applies only to Cloud Billing accounts associated with an Organization (or Business) Google payments profile type. You can verify your account type on the Payment settings page in the Cloud Billing console.

With the billing.accounts.updatePaymentInfo permission on the billing account, users can do the following:

• View payments history and documents related to the associated Google payments profile.
• Add and edit payment methods on a self-serve (online) billing account.
• Make a manual payment to a self-serve (online) billing account.
• Update payments profile info such as the business name, address, tax info, and payments account settings.

Billing account users with the billing.accounts.updatePaymentInfo permission won't have the Manage users or Admin with all permissions level of access on the Google payments profile. To fully manage a payments profile and gain Manage users and Admin permissions, billing account users still require additional Google payments user permissions granted on the associated payments profile.

CUD recommendations support more machine types

Resource-based CUD recommendations for cores and RAM now support additional machine series. For a complete list, see Resource-based CUDs supported by recommendations.

You can access these recommendations using the FinOps hub user interface, programmatically using the Recommender API, or when you export recommendations to BigQuery.

View granular cost data from Pub/Sub snapshot, subscription, and topic usage in Cloud Billing exports to BigQuery

You can now view granular Pub/Sub cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed snapshot, subscription, and topic usage.

Review the schema of the Detailed cost data export.

Anomaly Detection is generally available

View and manage cost spikes that deviate from your typical spend patterns using the Anomalies dashboard, which is generally available. Each anomaly includes a detailed root cause analysis that identifies the top services, regions, and SKUs that contributed to the spike.

With this launch, we've added the following features to Anomaly Detection:

• Auto-generated anomaly thresholds that update daily based on your usage patterns.
• Deviation percentage as a new threshold for you to configure for your anomalies.
• Email alerts automatically set up for Billing administrators to help you proactively manage your costs.

Learn more about using Anomaly detection to manage costs.

Personalized saved reports are available in cost Reports.

For customers who have enabled Gemini Cloud Assist in Cloud Billing, your custom saved reports that you open frequently now appear in the reports carousel, for quick access. Previously, the reports carousel only provided access to Google-created preset reports.

For more information, see the following topics in the Reports dcoumentation:

• Save and share report views
• Use preset reports for quick configuration

Spend-based committed use discount (CUD) metadata export to BigQuery (public preview)

You can now access spend-based CUD metadata programmatically through a BigQuery export. This data provides a comprehensive, daily snapshot of spend-based CUDs, which you can join with other billing data exports for improved CUD reporting and management.

Learn more about the CUD metadata export.

Tags data for regional Secret Manager secret usage is available in both the Standard usage cost export and the Detailed usage cost export.

Tags for Global secrets have been available since August 8, 2024. With this update, you can now tag Regional secrets as well.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see about tags and query examples with tags.

New fields added to Cloud Billing data exports to BigQuery

To prepare for expanding the spend-based committed use discounts (CUD)s program, we added new data fields to the schema for Cloud Billing standard and detailed data exports to BigQuery. These new fields add more information about the prices charged for your Google Cloud usage and consumption models.

To learn more, see Billing data and SKU updates for spend-based CUDs.

New, enhanced forecasting model for increased accuracy in cost reports

Cloud Billing forecasts now better account for seasonality trends, data irregularities, and missing data, using an enhanced forecasting model that leverages AI to factor in various scenarios, such as the following:

• Intelligent handling of transient effects caused by known business events - for example, a new workload migration causing a usage spike.
• Deeper understanding of seasonality - for example, various recurring patterns, such as daily, weekly and monthly cycles in your cloud spend; or for retailers, increases in usage during holiday seasons.
• Adapting to trends to remain relevant in changing environments - for example, new AI spend.

These enhancements, powered by our new machine learning engine, translate to increased forecasting accuracy. By capturing complex trends, multiple seasonalities, and handling data anomalies more intelligently, you'll see a marked improvement in the precision of your cost forecasts.

For more information about the forecasted costs in reports, see View you forecasted costs.

Find and eliminate waste using FinOps hub 2.0 with Gemini Cloud Assist (preview)

FinOps hub 2.0 adds a new dashboard, Utilization insights, designed to help you quickly identify and reduce cloud waste to get the most value from Google Cloud. You can do the following with FinOps hub's Utilization insights dashboard:

• Assess estimated costs from underutilized resources (for example, idle, overprovisioned, underprovisioned and suboptimal configurations).
• Use the visual Waste map to find the top waste drivers by projects and waste category, helping you focus your optimization efforts.
• Leverage data-driven recommendations to optimize key services (Compute Engine, Kubernetes Engine (GKE), Cloud SQL, and Cloud Run) and App Hub applications.

Use Gemini Cloud Assist in FinOps hub to save time and simplify collaboration. If you have enabled Gemini Cloud Assist in Billing, Gemini generates summaries of top wasted usage insights and drafts email reports of utilization insights that you can share with your engineering teams for quicker remediation.

For more information about the FinOps hub Utilization insights dashboard, see:

• Review utilization and wasted usage insights

For more information about Gemini Cloud Assist features in FinOps hub, see:

• Gemini Cloud Assist in Cloud Billing
• Set up Gemini Cloud Assist in Cloud Billing

App Hub applications are now integrated with billing reports and the FinOps hub, to let you analyze costs by application. This integration provides detailed cost analysis for your specific applications, so FinOps and DevOps can see the cost of their applications and get recommendations on how to optimize their cloud efficiency.

• In cost Reports, you can configure your report to Group by Application, or filter on Applications.
• In the Cost table report, you can filter on Applications.
• In the Cost breakdown report, you can filter on Applications.
• In the FinOps hub Utilization insights dashboard, you can view insights by App Hub Application, to see the estimated costs of potentially wasted usage, and find recommendations to reduce waste and optimize your costs.

Cloud Billing supports Dark theme in the Google Cloud console (in preview)

Dark theme is now available in the Billing section of the Google Cloud console (preview). To enable the Dark theme, in the Google Cloud console, click Settings > Preferences > Appearance. Choose Dark theme and click Save.

Improved consistency in resource-based committed use discount (CUD) string names across experiences.

We have improved consistency by standardizing CUD string names across the various experiences. This update helps provide a seamless experience in resource-based CUD purchase flows, recommendations, analysis, and the FinOps hub.

Google Cloud Marketplace now uses the agency model for marketplace services for UK, FR, and DE customers.

As part of this change, customers will receive separate invoices for Google Cloud and third-party vendor transactions in the Cloud Marketplace.

For more information, see Split invoicing for agency model transactions and Marketplace Agency Account Migration FAQ.

Tags data for BigTable instances is available in both the Standard usage cost export and the Detailed usage cost export.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see more about tags and query examples with tags.

Simulate scenarios in FinOps hub to maximize your savings from resource-based CUDs

In the FinOps hub, we added support for resource-based CUD recommendations as a starting point to simulate various usage scenarios, and customize the recommendation to purchase a CUD that maximizes your savings.

Learn about simulating scenarios for resource-based CUDs.

View and manage unexpected costs with Anomaly Detection (in preview)

You can now view and manage cost spikes that deviate from your historical spend patterns using the Anomalies dashboard (preview). Each anomaly comes with a detailed root cause analysis that identifies the top services, regions, and SKUs that contributed to the spike.

Learn more about using Anomaly Detection to manage costs.

Avoid charges for underutilized Compute Engine reservations in the FinOps hub

You can now get recommendations to modify or delete your underutilized, on-demand reservations for Compute Engine resources when you haven't consumed your specified threshold of resources for at least 7 days.

Learn about reservation recommendations
View and apply underutilized reservation recommendations

Use Gemini AI assistant to find or create Billing Reports (preview)

Gemini Cloud Assist in Cloud Billing Reports provides FinOps-focused AI assistance to create the cost reports you need to analyze your cost trends and to summarize key insights from the cost reports.

Gemini Cloud Assist in Cloud Billing Reports helps you to:

• Use saved reports: Quickly access existing reports to analyze your spending.
• Create new reports: Configure custom reports with AI assistance to get the exact data you need.
• Summarize reports: Get AI-powered summaries of your reports to quickly understand key cost trends and insights.

Enable the Gemini for Google Cloud API in a project to turn on Gemini Cloud Assist in Cloud Billing Reports.

For more information about Gemini Cloud Assist features in Cloud Billing Reports, see:

• Gemini Cloud Assist in Cloud Billing
• Set up Gemini Cloud Assist in Cloud Billing
• Analyze billing data and cost trends with Reports

The Carbon footprint dashboard in the FinOps hub now includes market-based emissions data (preview)

Scope 2 market-based emissions data (preview) for the Carbon footprint dashboard are now available in the FinOps hub. The market-based emissions metric represents purchased electricity, incorporating Google's annual renewable energy purchases. You can use the data in the Carbon footprint dashboard to optimize your cloud spend and reduce your carbon impact.

• To learn more about the methodology and the difference between location-based and market-based emission metrics, see the carbon footprint documentation.

• Learn more about the FinOps hub.

Tags data for Secret Manager secret usage is available in both the Standard usage cost export and the Detailed usage cost export.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see about tags and query examples with tags.

View granular cost data from Secret Manager secret usage in Cloud Billing exports to BigQuery

You can now view granular Secret Manager secret cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed log bucket usage.

Review the schema of the Detailed cost data export.

Track credits for your spend-based milestone credit programs (contract pricing)

If you have a custom pricing contract, you might be enrolled in spend-based milestone credit programs, where you earn promotional credits for spending specific amounts on Google Cloud.

In the Google Cloud console, you can now track the promotional credits for your spend-based milestone programs. The promotional credits that you receive act as a payment method, and are automatically applied to your costs.

Learn about tracking spend-based milestone credits.

You can now view granular AlloyDB for PostgreSQL usage in the Cloud Billing Detailed export to BigQuery

You can now view granular AlloyDB for PostgreSQL cluster, instance, and backup data in the Google Cloud Billing detailed export. Use the resource.global_name and resource.name fields in the export to view and filter your detailed AlloyDB cluster, instance, and backup usage.

Review the schema of the Detailed cost data export.

Tags data for AlloyDB for PostgreSQL cluster, instance, and backup usage is available in both the Standard usage cost export and the Detailed usage cost export.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see about tags and query examples with tags.

Simulate scenarios in FinOps hub to maximize your savings from spend-based CUDs

In the FinOps hub, you can now use a spend-based CUD recommendation as a starting point to simulate various usage scenarios, and customize the recommendation to purchase a CUD that maximizes your savings.

Learn about simulating scenarios for spend-based CUDs.

View your Carbon Footprint in the FinOps hub

In the FinOps hub, you can now view the estimated greenhouse gas emissions for your Google Cloud usage by visiting the Carbon Footprint dashboard.

Learn about Carbon Footprint data.

Avoid getting charged for idle Compute Engine reservations in the FinOps hub

You can now get recommendations to modify or delete your idle, on-demand reservations for Compute Engine resources when you haven't consumed any resources for at least 7 days.

Learn about idle reservation recommendations.

You can now view granular cost data for more Google Cloud services

• You can now view granular Cloud Logging log bucket cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your detailed log bucket usage.
• You can now view granular Managed Microsoft Active Directory cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed domain usage.
• You can now view granular Dataproc Metastore cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed service usage.
• You can now view granular Cloud Deploy cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed delivery pipeline usage.
• You can now view granular Cloud Data Fusion cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed instance usage.

Review the schema of the Detailed cost data export.

The Cost Estimation API is deprecated

To get estimates for your planned Google Cloud workloads, use the Google Cloud pricing calculator.

Generate a SQL query to BigQuery from your Cloud Billing Reports (in preview)

In the cloud console, on the Billing Reports page, you use the report settings and filters to refine the data returned to your report. If you have enabled Cloud Billing data export to BigQuery, you can analyze your exported billing data using SQL queries. In Billing Reports, you can now click a button to generate a SQL query in BigQuery that is configured to use the equivalent Billing Report settings and filters to query your exported billing data. When run against your exported billing data, the generated query returns the equivalent results in BigQuery as the results in the Billing Report.

• Learn more about Billing Reports
• Learn more about Billing data export to BigQuery
• Learn more about generating a SQL query from a billing report

Commitment recommendations in the FinOps hub now include a Recommended quantity column, so you can see more information about recommendations at a glance.

Learn more about using the FinOps hub to optimize your costs.

Download committed use discount data as a CSV file

You can now download data about all your committed use discounts (CUD) as a flat comma-separated value (CSV) file. The CSV file includes the subscription ID for each commitment, which you can use join your CUDs data to your usage data in the BigQuery export.

Learn about downloading your CUDs data.

The Cloud Billing FinOps hub is now Generally Available

Use the FinOps hub to monitor and share your current savings, explore recommended opportunities to optimize costs, and plan your optimization goals. The FinOps hub dashboard generates recommendations based on historical usage, including recent usage and current commitments, and helps you gauge how well you're using Google Cloud tools to monitor and save costs.

Learn about using FinOps hub.

You can now view granular Memorystore for Redis usage in the Cloud Billing Detailed export to BigQuery

You can now view granular Memorystore for Redis cost data in the Google Cloud Billing detailed export. Use the resource.global_name and resource.name fields in the export to view and filter your detailed Memorystore for Redis usage.

Review the schema of the Detailed cost data export.

You can now view granular Bigtable usage in the Cloud Billing Detailed export to BigQuery

You can now view granular Bigtable instance cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your detailed Bigtable instance usage.

Review the schema of the Detailed cost data export.

Tags data for Google Cloud Storage buckets is available in both the Standard usage cost export and the Detailed usage cost export.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see more about tags and query examples with tags.

Create your first budget with one click

You can now create your first budget and receive budget alerts in one step using the Create a budget alert panel on the Billing Overview page. The tool shows you recommended budget amounts based on your usage patterns, and you will receive alerts when your actual spend reaches 50%, 75%, 100%, and 150% of your selected budget. You can later edit these settings in the Manage budgets and alerts section.

Learn more about budgets.

Between February 13, 2024 and February 22, 2024, some SKU IDs for your support subscriptions have changed. Use the following table to check whether you're affected by this change. If you have reports or BigQuery queries that depend on these IDs, edit them to use the new SKU IDs.

Learn about reports that you can use to analyze your costs.

US-based billing accounts only: In August 2023, Google Cloud Marketplace transitioned to the Agency model for marketplace services for US partners and US customers. As part of this change, the remittance information has changed on your Google Cloud invoices and in the Google Cloud console.

As part of this change, you can see the following information in your Cloud Billing tools:

• In the Cost Table report, use the Seller Name and Transaction type columns.
• In the Standard data export to BigQuery, use the seller_name and transaction_type columns.

View granular cost data from Cloud Storage usage in Cloud Billing exports to BigQuery

You can now view granular Cloud Storage bucket-level cost data in the Cloud Billing Detailed cost export. Use the resource.global_name field in the export to view and filter your detailed Cloud Storage bucket usage.

Review the schema of the Detailed cost data export.

Recommendations for Compute Engine Flexible committed use discounts are now Generally Available

Flexible CUDs add flexibility to your spending capabilities by eliminating the need to restrict your commitments to a single project, region, or machine series. Flexible CUDs recommendations in the FinOps Hub help you optimize costs by analyzing your spending trends and existing commitments to suggest purchase amounts for Flexible CUDs.

• Learn more about Flexible CUDs
• Learn more about the FinOps Hub

Subscription IDs for your committed use discounts are now available in the Detailed cost data export

You can now view a subscription ID associated with your resource-based and spend based Committed Use Discount (CUD) fees. This enables you to connect CUD fees to the corresponding CUD (subscription instance) to improve traceability of costs and savings calculations. Use the subscription.instance_id column in the Detailed cost data export to see your subscription ID.

• Learn about exporting your billing data to BigQuery
• View the schema of the Detailed cost data export

Control access to single-project budgets

If you are a billing account-level user and are creating a budget for a single project, you can now prevent project users such as Project Owners and Project Editors from making changes to the budget. This prevents inadvertent changes to budgets that you might be tracking at the Cloud Billing account level.

Learn more about creating Google Cloud budgets.

Budgets for project users is now Generally Available

Project users such as Project Owners, Project Editors, and Project Viewers in Google Cloud can now create budgets and stay on top of their cloud costs, without needing additional permissions to access Cloud Billing accounts. Budgets for project users enables project users to take ownership of their costs, plan for the spend in the projects that they own, and proactively manage cost exceptions.

You can now assign custom roles to users who can create, modify and delete single-project budgets for the projects they have access to.

Project users can use the Google Cloud console or the Cloud Billing Budget API to manage budgets for projects.

• Take a 10-minute tutorial to get started with budgets for project users
• View the documentation to learn more about Google Cloud budgets

View granular cost data from Dataflow usage in Cloud Billing exports to BigQuery

You can now view granular Dataflow cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your detailed Dataflow usage.

Review the schema of the Detailed cost data export.

View granular cost data from BigQuery usage in Cloud Billing exports to BigQuery

View granular cost data from BigQuery in Cloud Billing exports to BigQuery You can now view granular BigQuery cost data in the Google Cloud Billing detailed export. Use the resource.name or resource.global_name field in the export to view and filter your BigQuery Dataset and Jobs costs.

Review the schema of the Detailed cost data export.

You can now monitor and share your current savings, explore new recommended opportunities to optimize costs, and plan your optimization goals with the new FinOps Hub (Preview). The FinOps Hub dashboard generates recommendations based on historical usage metrics, including recent usage and current commitments, and helps you gauge how well you're using Google Cloud tools to monitor and save costs.

Learn more about the FinOps Hub.

Budgets for project users now available (in preview)

Now project users in Google Cloud can create budgets and stay on top of their cloud spend, without needing additional permissions to access Cloud Billing accounts. Budgets for project users enables engineers to take ownership of their costs, plan for the spend in the projects that they own, and proactively manage cost exceptions.

Project Owners, Project Editors, and Project Viewers can view budgets that are scoped to individual projects. Project Owners and Editors can also create, modify and delete single-project budgets for the projects they have access to.

A new email notification option is available for budgets scoped to a single project: Email alerts to project owners. All other notification options are also available for single-project budgets.

Project users can use the Google Cloud console or the Cloud Billing Budget API to manage budgets for projects.

• Take a 10-minute tutorial to get started with budgets for project users
• View the documentation to learn more about Google Cloud budgets

We added a new BigQuery example that helps you join your Price and Detailed Cost Data exports, so that you can compare your costs with detailed information from your Pricing BigQuery export.

View the example query to join prices and costs.

Cloud Billing Pricing API now available in preview

You can now get list prices, as well as account-specific custom prices and discounts for Google Cloud stock keeping units (SKUs) with the Pricing API (preview). You can also use the Pricing API to get additional information about Google Cloud services, such as service-to-SKU mappings, information about SKU groups, SKU group to SKUs mapping, and geo and product taxonomy information.

• Learn about using the API, with example API requests
• Get detailed information in the the API reference

List Prices now available in cost data exports

You can now view the list prices associated with all line items charged to your account in Google Cloud Billing standard and detailed export. Use the cost_at_list column to view list prices.

Review the schema of the Detailed cost data export
Review the schema of the Standard cost data export

View granular cost data from Firestore and Datastore usage in Cloud Billing exports to BigQuery

You can now view granular Firestore and Datastore cost data in the Google Cloud Billing detailed export as part of your overall App Engine usage. For your detailed Firestore and Datastore usage, the service.name column contains App Engine. Use the resource.name or resource.global_name fields in the export to view and filter your detailed Firestore and Datastore usage.

Review the schema of the Detailed cost data export.

Use folders and organizations in budgets: When you set up budgets for your Cloud Billing account, you can set the budget's scope to one or more folders or organizations that are linked to your account, in addition to the current options for specific projects and labels.

When you create a budget that applies to a folder or organization, the budget also covers future projects that you create in the folder or organization.

Learn about creating and modifying budgets for your Cloud Billing account.

Cloud Billing Reports and Cost Breakdown report now support CSV downloads

For Cloud Billing Reports and Cost Breakdown reports, we have added the ability to download the data in the report table to a comma-separated values (CSV) file. With this update, the Download CSV feature is now available on most reports in the Cloud Billing console, including: Cost Table, Pricing Table, Reports, Cost Breakdown, and the Committed Use Discounts (CUDs) dashboard.

View granular cost data from Cloud Spanner usage in Cloud Billing exports to BigQuery

You can now view granular Cloud Spanner cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your detailed Cloud Spanner usage.

Review the schema of the Detailed cost data export.

View granular cost data from App Engine usage in Cloud Billing exports to BigQuery

You can now view granular App Engine cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your detailed App Engine usage. Note that Firestore, App Engine Flex, and Datastore costs are not included in the granular App Engine instance costs.

Review the schema of the Detailed cost data export.

Starting from March 15, 2023, in your Billing BigQuery exports and all Cloud Billing reports in the Google Cloud console, the service description for Cloud Monitoring (formerly Stackdriver) has changed from Stackdriver Monitoring to Cloud Monitoring.

If you have BigQuery queries or visualizations that filter data based on the Cloud Monitoring service description, you must update those queries.

• Learn about the structure of the Cloud Billing data tables in BigQuery.
• Read the announcement for Cloud Operations Suite (February 2020)

Committed Use Discounts: View your usage data at an hourly granularity in the CUD Analysis dashboard

You can now analyze the effectiveness of your spend-based or resource-based committed use discounts at an hourly granularity. Previously, you could only analyze your CUDs at the daily level.

Access your usage data at an hourly granularity in the CUD Analysis dashboard.

View your Cloud SQL costs in Billing export to BigQuery

You can now view your granular Cloud SQL instance cost data in the Cloud Billing Detailed cost export. Use the resource.global_name field in the export to view and filter your Cloud SQL instance data.

Preview: Get estimated costs in the Google Cloud console

You can now estimate the cost of Compute Engine and Cloud Storage workloads in the Google Cloud console. The Cost Estimation tool provides estimates that also include any custom contract prices on your Cloud Billing account. These cost estimates can help you make more informed business decisions.

Learn about estimating costs in the Google Cloud console.

View expiring commitments and automatically renew resource-based commitments with the Committed use discount dashboard

In the Committed use discount dashboard, you can now see subscription expiration notifications for commitments that are expiring within the next 30 days. In the dashboard's auto renewal column, you can automatically renew your resource-based commitments.

For more information about viewing the Commitment dashboard, see Committed use discount overview.

View granular cost data from Cloud Run instances in Cloud Billing exports to BigQuery

You can now view granular Cloud Run cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your Cloud Run instances.

Review the schema of the Detailed cost data export.

View granular cost data from Cloud Function instances in Cloud Billing exports to BigQuery

You can now view granular Cloud Function cost data in the Google Cloud Billing detailed export. Use the resource.global_name field in the export to view and filter your Cloud Function instances.

Review the schema of the Detailed cost data export.

Dataset configuration requirements have changed for Cloud Billing export to BigQuery

When exporting detailed usage cost data to BigQuery, when you select or create a BigQuery dataset to be used for your BigQuery tables, you can now use any supported location when configuring your dataset. Prior to this update, when you enabled the export of detailed usage cost data to BigQuery, your BigQuery dataset was limited to using a multi-region location.

Data availability tip: The dataset location you select can influence whether the previous month's billing data is added to the dataset retroactively:

• When you enable the detailed usage cost data export for the first time, if you select a dataset configured to use a multi-region location, Cloud Billing data will be available retroactively from the start of the previous month.
• If you enable the detailed usage cost data export and select a dataset that is configured to use a region location, your Cloud Billing data will be available starting from the date when you enabled the export, and after. That is, Google Cloud billing data is not added retroactively for non-multi-region dataset locations, so you won't see Cloud Billing data from before you enable export.
• For more details, see Data availability

For more information, review the schema of the Cloud Billing detailed cost export to BigQuery.

Generally available: View your Google Kubernetes Engine (GKE) costs in Cloud Billing reports and cost data export to BigQuery

You can view your GKE costs by cluster, namespace, and pod labels in the Detailed cost export, and the built-in reports in the Google Cloud console.

Cloud Billing export to BigQuery

In the Detailed cost export to BigQuery, you can use the labels.key column to filter the data by these label keys:

• goog-k8s-cluster-name: Filter your GKE resources by cluster.
• k8s-namespace: Filter your GKE resources by namespace.
• k8s-label: View all your GKE resources.

Cloud Billing reports

In the Cloud Billing report, Cost breakdown report, and Cost Table report, you can use the Label selector to filter and group your data by cluster or namespace, using one of these label keys:

• goog-k8s-cluster-name: Filter or group your GKE resources by cluster.
• k8s-namespace: Filter or group your GKE resources by namespace.

To start viewing and analyzing your GKE cost data, see these pages:

• Enable cost allocation for your GKE clusters
• Enable the Detailed cost data export
• Review the schema of the Detailed cost data export
• View your Cloud Billing reports

Tags data now available in cost data export in BigQuery

Tags are attached to resources and support inheritance, centralized management, nomenclature standardization, and policy engine integration. For Cloud Billing, Tags help map costs across your organization. In cost reporting, you can query on Tags to perform Cost Management tasks like chargebacks, audits, and other cost allocations.

Tags data is available in both the Standard usage cost export and the Detailed usage cost export.

To learn more about Tags, see Tags overview. To learn about using Tags in your cost data exported to BigQuery, see more about tags and query examples with tags.

Non-USD accounts can now view more cost information with the Commitment Analysis Dashboard

Customers with non-USD billing accounts now have additional information (including local currency cost data) available to them within the committed use discount dashboard and have been granted access to the Commitments Analysis Dashboard.

View all on-demand spend applicable for committed use discounts (CUDs)

You can now view all CUD-eligible usage without any active commitments within the Commitment Analysis Dashboard for further cost optimization opportunities.

You can now estimate the cost of your workloads using the Cost Estimation API (Preview). The Cost Estimation API provides customer-specific estimates that include all your discounts, such as those negotiated as part of a contract and those based on committed usage. These cost estimates can help you make more informed business decisions.

• For information on using the API, and example API requests, see Get cost estimates for your Google Cloud workloads.

• For detailed information on the API request and response formats, see the API overview.

Secure the link between a project and its billing account

In the Cloud Billing Console, you can now lock the link between a project and its Cloud Billing account, in order to prevent accidental changes to the billing state, such as disabling billing or moving the project to a different billing account. You can also unlock this protected state if you want to unlink a project from a Cloud Billing account.

Google Cloud projects contain all the resources required for a system to operate. To pay for the usage of the Cloud resources (such as Compute Engine or Storage), each project must be linked to an active Cloud Billing account. If you unlink the project from a billing account, you disable billing on that project. When billing is disabled on a project, all resources contained within the project will shut down, which can cause outages to your normal business operation.

To prevent unintentional outages due to billing issues, lock your valuable projects to their linked billing account. Locking creates a two-step process to change the billing state of a project, improving billing reliability and reducing accidental outages due to billing issues.

Learn how to secure the link between a project and a Cloud Billing account.

Preview: View your Google Kubernetes Engine (GKE) costs in Cloud Billing reports and cost data export to BigQuery

You can view your GKE costs by cluster, namespace, and pod labels in the Detailed cost export, and the built-in reports in the Google Cloud console.

Cloud Billing export to BigQuery

In the Detailed cost export to BigQuery, you can use the labels.key column to filter the data by these label keys:

• goog-k8s-cluster-name: Filter your GKE resources by cluster.
• k8s-namespace: Filter your GKE resources by namespace.
• k8s-label: View all your GKE resources.

Cloud Billing reports

In the Cloud Billing report, Cost breakdown report, and Cost Table report, you can use the Label selector to filter and group your data by cluster or namespace, using one of these label keys:

• goog-k8s-cluster-name: Filter or group your GKE resources by cluster.
• k8s-namespace: Filter or group your GKE resources by namespace.

To start viewing and analyzing your GKE cost data, see these pages:

• Enable cost allocation for your GKE clusters
• Enable the Detailed cost data export
• Review the schema of the Detailed cost data export
• View your Cloud Billing reports

We've added new features to view your billing information and cost estimates in the Google Cloud Console mobile app. You can view your cost trends and forecasts, the costs for your top project, and how much you're spending on your top Google Cloud services.

To see your billing data in the app, select the Billing tab in the navigation bar, then select Overview.

Get the Google Cloud Console app for iOS or Android.

Attribution for your committed use discounts (CUDs) now appears at the same time as eligible usage.

Previously, the subscription fees and credits associated with your CUDs would appear in billing reports and BigQuery usage cost exports after the corresponding eligible resource usage. This could result in apparent spikes in cost if you viewed your billing data before the attribution process completed.

With this release, subscription fees and credits appear at the same time as eligible usage, meaning that your net costs are always accurate whenever you view your billing data.

Learn about how your CUD fees and credits are attributed across your resources.

Cost table report now supports updated filters, project ancestry, and report sharing

In the Cloud Billing Console Cost table report, we've updated the report's filters and invoice month selector to function similarly to the Cloud Billing Reports page and Cost breakdown page, added project ancestry functionality, and enabled report sharing.

Updated filters: You use the cost table report to access the details of your invoices and statements. The report's filters and other settings allow you to configure the report views when you are analyzing the usage and cost data. You can also download the cost table data to CSV for offline analysis. When you download the report to CSV, the data that downloads is limited by any filters that you have set and includes only the columns that you have selected to view.

Project ancestry: A new table column has been added to display project ancestry data. Starting with the January 2022 invoice month:

• Historical project metadata is available with the addition of Project hierarchy data.
• Usage and cost data that was grouped by Project is now grouped by Project hierarchy.
• You can now filter on Folders & Organizations, components of a project's ancestry, to analyze costs by project hierarchy.
• The values in the project hierarchy column are displayed only when you are viewing a flat table view or when you are viewing a nested table view grouped by Project > Service > SKU.
• The report returns a row for each distinct combination of Organization > Folder > Project, and the table includes columns for Project, Project ID, Project number, and Project hierarchy. The values listed in the Project hierarchy column show Organization name > Folder name.

Report sharing: Along with the updated report filters, the cost table report now supports URL bookmarking and sharing. As you configure your cost table report by setting the invoice month, table view cost grouping options, and report filters, the cost table URL updates to include your selections. You can save your report settings by bookmarking the URL. You can share the cost table report by copying the URL.

For more details about the cost table report and using the updated features and functionality, see the documentation.

Cost analysis by project ancestry, including folder-level costs, now available in BigQuery Export and Reports

Viewing your costs by project ancestry helps you do things like analyze costs by folder or organization. For example, if you use folders in an organization to represent cost centers (such as DevOps or Finance), you can effectively configure your report or query to group all costs by those cost centers.

Billing Reports

In the Cloud Billing Console Reports page, you can now Group by Project hierarchy and filter on Folders & Organizations, to analyze costs by project ancestry (such as folders or organizations).

• Group costs by project ancestry – In the Reports page, when you group by Project hierarchy, the report returns a row for each unique combination of Organization > Folder > Project, and the table includes columns for Project, Project ID, Project number, and Project hierarchy. The values listed in the Project hierarchy column show Organization name > Folder name.

• Filter costs by project ancestor(s) – In the Reports page, when you filter by Folders & Organizations, the report returns costs for all projects that are associated with any of the selected folders/organizations in their project ancestry.

In the Cloud Billing Console Cost breakdown report, you can now filter on Folders & Organizations, to analyze costs by project ancestry (such as folders or organizations).

• Filter costs by project ancestor(s) – In the Cost breakdown report, when you filter by Folders & Organizations, the report returns costs and credits aggregated for all projects that are associated with any of the selected folders/organizations in their project ancestry.

To learn more about organizations, folders, and project hierarchy, see Billing reports: Analyzing your costs by project hierarchy.

Cloud Billing data export to BigQuery

In the Cloud Billing usage cost data that exports to BigQuery, you can now see resource hierarchy metadata that describes a project's ancestry, including:

• project.ancestors.resource_name – An identifier containing the resource hierarchy type and ID (for example, folders/234)
• project.ancestors.display_name – A name that you create for the resource (for example, DevOps)

The project.ancestors metadata is available in both the Standard usage cost export and Detailed usage cost export. To help make resource hierarchy levels easier to identify in the BigQuery data tables, the ancestor data includes the resource display name (a human-readable name that you create) and the relative resource hierarchy names (immutable ID numbers representing each project/folder/organization).

For more details about project.ancestry_numbers and project.ancestors, see

• Understand the Cloud Billing data tables in BigQuery
• Query examples to use resource hierarchy filters to review project ancestry

Report filters now support the display of IDs in addition to names in the filter panels.

In the Cloud Billing Console, when you are viewing the options displayed in the filter panels for Subaccounts, Projects, Services, and SKUs, you can now see both the option name and the option ID (for example, project name and project ID). The ID displays below each option name. Previously, only the name was displayed when viewing the list of options in a filter panel. View an example of the Services filter panel, before and after the update.

With the addition of the ID, you can do the following:

• Within a filter panel, search by name or by ID (for example: "BigQuery" or "services/24E6-581D-38E5").
• More easily match a filter option to an invoice line item. For example, instead of searching for the "Active Storage" SKU, you can search for SKU ID "services/24E6-581D-38E5/skus/947D-3B46-7781".
• You can use partial values when searching within a filter panel, and you will get back all matching results. For example, you can type to filter on "storage" or "24e6" or "7781".

Learn more about using filters in Cloud Billing Reports and the Cost breakdown report.

Starting in February 2022, if you have committed use discounts (CUDs), Google Cloud Billing calculates the attribution for your fees and credits every hour, to help you track costs faster and more accurately.

Learn about how your CUD fees and credits are attributed across your resources.

Starting on February 1, 2022, Google Cloud usage by customers in Bahrain is subject to 10% VAT.

Learn about taxes applied in your country.

Prioritized attribution for your resource-based committed use discounts (CUDs) is now Generally Available.

You can now specify how your credits and, where appropriate, the subscription fees from your resource-based committed use discounts are distributed among your Google Cloud projects.

Learn about how you can allocate your commitments.

Recommendations for spend-based committed use discounts (CUDs) are now Generally Available.

You can use these recommendations to optimize your project costs by analyzing your spending trends and signing up for committed use discounts. Recommendations are supported for Cloud Billing accounts billed in US Dollars (USD).

Learn about commitment recommendations.

Cost breakdown report now supports new filters and report sharing

In the Cloud Billing Console Cost breakdown report, you can now select the costs you want to analyze using the Time range and other report filters, such as projects, services, and SKUs.

For detailed insights behind the results of your cost breakdown report, view the Reports page. The cost breakdown report is linked to the Cloud Billing Reports page; the link uses the same time range and report filters you configure on your cost breakdown report. When you open the Reports page from your cost breakdown report, the report opens displaying the same totals as the cost breakdown report.

Along with the new report filters, the cost breakdown report now supports URL bookmarking and sharing. As you configure your cost breakdown report by setting the time range and other filters, the cost breakdown URL updates to include your selections. You can save your report settings by bookmarking the URL. You can share the cost breakdown report by copying the URL.

For more details about the cost breakdown report and using the new report filters and sharing feature, see the documentation.

Cloud Billing Budgets & alerts now support configurable budget time periods, beyond monthly budgets

In the Cloud Billing Console Budgets & alerts settings, you can now specify the time period of your budgets. Using the Time range settings now available to budgets in the Cloud Console, you can configure the budget's time range to a calendar period or a custom date range, allowing you to create budgets to monitor spend for time frames beyond the default calendar month, such as a quarter, a year, or a custom date range that you specify.

With this update, you can create, view, and manage all budgets (monthly and non-monthly) in the Budgets & alerts page in the Cloud Console or by using the Cloud Billing Budget API.

For more information on budgets and alerts, see Create, edit, or delete budgets and budget alerts.

The detailed usage cost data export to BigQuery is now generally available (GA).

The detailed export includes all of the data fields from the standard usage cost data export, along with additional fields that provide resource-level cost data. The resource-level cost data available in the detailed export is limited to Compute Engine resources, such as virtual machines or SSDs that generate service usage.

In your BigQuery dataset, the detailed usage cost data is exported to a table named gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID>.

The following are the newly available fields:

• resource (Struct) - The fields that describe the structure and value of information relevant to service resources (like a virtual machine or a SSD) that generate service usage.
• resource.global_name (String) - A globally unique service identifier for the resource that generated relevant usage.
• resource.name (String) - A service-specific identifier for the resource that generated relevant usage. This can be input generated by the user. Note, the first full day of data with this field is August 11, 2021.

The daily cost detail data export to BigQuery is now the standard usage cost data export.

To understand the differences between the standard and detailed usage cost data exports to BigQuery, see the documentation.

Proportional attribution for spend-based committed use discounts is now generally available (GA).

Proportional attribution applies the subscription fees from your committed use discounts to the projects in your Cloud Billing account, directly in proportion to the amount of eligible credit consumed by each project. Any subscription fees that are not attributed to a project are charged at the Cloud Billing account level.

Starting from August 2021, all spend-based commitments you purchase for any of your Cloud Billing accounts use proportional attribution by default. If you purchased spend-based commitments before then, you can request that they be converted from account to proportional attribution.

To understand proportional attribution for your spend-based commitments and how to enable it, see the documentation.

(Customers in India only) We have updated information about Google's tax compliance in India, for tax deducted at source (TDS). Learn about Google Cloud India TDS certificates.

(Customers in India only) Starting on July 1, 2021, the first page of your invoice shows a Unified Payment Interface (UPI) QR code. You can pay your invoice by scanning the QR code with any UPI-enabled application.

Summary bar now available in the Cost Table report

To provide additional flexibility when analyzing your data in the cost table report, we've added the summary bar as another analysis tool.

When you select a subset of rows in your cost table, a floating summary bar opens and shows you the total gross costs, credits, the percentage of savings, and the total net costs, summarized for the selected rows. The summary bar is available for both the nested and flat table views.

For more information about using the summary bar on the Cost table report, see View and download the cost details of your invoice or statement.

Committed use discounts for Google Kubernetes Engine (GKE) are now Generally Available to purchase for workloads running on GKE Autopilot.

They provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. The spend-based committed use discounts apply to all GKE Autopilot Pod workload CPU, memory, and ephemeral storage usage in the region in which you have committed. This gives you low, predictable costs, without the need to make any manual changes or updates yourself. This flexibility saves you time and helps you to save more by achieving high utilization rates across your commitments.

GKE Autopilot Mode commitments do not apply to the cluster management fee or to GKE Standard mode compute nodes.

See the documentation for more details.

Committed use discounts are now available for public preview to purchase for Cloud Run. They provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. The spend-based committed use discounts apply to all aggregated Cloud Run CPU, memory, and request usage in a region, giving you low, predictable costs when your code is running in one of the supported container ecosystems.

Cloud Run commitments do not apply to networking changes.

See the documentation for more details.

Cloud Billing Reports now show the target budget amount when you open the report from a budget

In the Cloud Billing Console, Billing Budgets are linked to the Billing Reports page. If you open the Reports page from a Budget, the budget's scopes are used to set the report's filters and the report opens displaying the costs tracked by the budget. Additionally, the budget's target amount appears in the report chart as a red, dashed line, helping you to visualize the budget amount in the report while you are analyzing the specific, budget-related costs. You can open the cost report from the list of budgets, or from a budget's cost trend chart.

For more details about how budgets and cost reports are linked, see Viewing a budget in your report.

Budget API now supports configurable budget time periods, beyond monthly budgets

Using the Cloud Billing Budget API to manage your budgets, you can now specify the time period of the budget. Prior to this update, you could only configure a budget to monitor costs incurred during a calendar month. Using the usage_period filter that is available in the Cloud Billing Budget API, you can configure the budget time period to a CalendarPeriod or a CustomPeriod, allowing you to create budgets to monitor time frames beyond the default calendar month, such as a quarter, a year, or a custom date range that you specify.

At this time, budgets configured with a non-monthly time period can only be viewed and managed using the Cloud Billing Budget API. Non-monthly budgets are not yet visible in the Budgets page in the Cloud Console.

For more information on using the Cloud Billing Budget API, see Get started with the Cloud Billing Budget API.

Effective April 1, 2021, for customers in India: Due to new Reserve Bank of India (RBI) regulations, your bank might begin declining automatic card charges for recurring payments for your Google Cloud usage.

To avoid interruptions in service, if your automatic payments are being declined, we recommend that you make a manual payment for your usage.

List cost and Unrounded cost columns now available in the Cost Table report

We've added two columns of data to the Cost table report: List cost and Unrounded cost.

• List cost: The List cost column is available for Cloud Billing accounts associated with a negotiated pricing contract, and represents the monthly cost of your cloud usage calculated using list prices. If your account has negotiated, custom pricing, you can compare List cost amounts to Cost amounts to determine how much you are saving with your negotiated prices.
• Unrounded cost: The Unrounded cost column contains the calculated cost of the usage to a precision of up to six decimal places. Unrounded costs can be helpful when analyzing your cost details and understanding the source of any discrepancies due to rounding.

For more information on the Cost table report, see View and download the cost details of your invoice or statement.