GCP Costs in the platform Cost History or History Invoice report do not align with the GCP Billing Console

Products

• CloudHealth

Issue/Introduction

There are a few reasons that GCP costs may not line up as you would expect.  This documentation goes through 3 common scenarios:

Resolution

1) For GCP costs, CloudHealth data is based on the BigQuery Billing Export.  A BigQuery Billing Export will only include data from the date that the export was created.  

Be aware that your BigQuery dataset only reflects Google Cloud billing data incurred from the date you set up Cloud Billing export, and after.  That is, Google Cloud billing data is not added retroactively, so you won't see Cloud Billing data from before you enable export.

 

2) Cost History will not match History Invoice for GCP due to the data source.

Data will be different between the two reports:

3) The platform assigns Enterprise Support charges (and potentially other costs) to specific projects, while GCP leaves them as generic costs not associated to any project. 

This will lead to discrepancies when looking as certain categorizations between projects.  GCP will not assign these charges to specific resources but CloudHealth may evenly disburse them based on overall utilization of cost/usage across your infrastructure.  Always line up overall total costs first to confirm that all data was captured and it is indeed a categorization issue.