Skip to main content

Google Billing Troubleshooting

Use this guide to diagnose common issues with Google Billing integrations in Cloudaware, including BigQuery export delivery, Cloud Storage export delivery, service account access, and report type mismatches.

BigQuery Export Missing or Incomplete​

See also: Google Cloud Billing Export

  • In the Google Cloud console:
    • Open Billing and select the billing account.
    • Go to Billing export → BigQuery export.
    • Confirm that the export is enabled for the correct billing account.
    • Confirm that the correct project and dataset are configured.
  • In BigQuery:
    • Confirm that billing tables exist, such as gcp_billing_export_v1_* or gcp_billing_export_resource_v1_*.
    • Check table metadata or recent rows to confirm the tables are being updated.
  • In Cloudaware:
    • Go to Admin → Google Billing.
    • Confirm that the billing integration is enabled and green.

Cloudaware Service Account Cannot Read BigQuery​

  • In the Google Cloud console → BigQuery:
    • Open the billing export dataset's Permissions.
    • Ensure the Cloudaware service account has BigQuery Data Viewer or an equivalent read-only role on the dataset.
  • In Cloudaware:
    • Go to Admin → Google Billing.
    • Confirm that the billing integration is configured with the correct project, dataset, and table names.
  • If access was changed recently, allow time for Google Cloud IAM propagation before rechecking Cloudaware status.

Legacy Cloud Storage Export Issues​

See also: Billing Export to Cloud Storage (Legacy)

  • In the Google Cloud console:
    • Open Billing → Billing export and confirm File export is configured.
    • Verify that the export targets the expected Cloud Storage bucket and path.
  • In Cloud Storage:
    • Verify that CSV billing files are arriving in the configured bucket.
    • Confirm the Cloudaware service account has Storage Object Viewer or equivalent read-only access on the bucket.
  • In Cloudaware:
    • Go to Admin → Google Billing.
    • Make sure the configured bucket and path match the actual export location.

Instance-Level Cost Views Are Missing​

  • In the Google Cloud console:
    • Confirm that Detailed usage cost is enabled for the billing export.
    • Confirm that detailed export tables, such as gcp_billing_export_resource_v1_*, exist in the dataset.
  • In Cloudaware:
    • Go to Admin → Google Billing.
    • Verify that the Detailed report is added and selected as the Cost Fields Source.
note

Cost data for individual resources becomes available only after Detailed usage cost is enabled. Retrospective resource-level cost data is not available for periods before the detailed export was enabled.

Costs Do Not Match Google Cloud Billing​

Google Cloud and Cloudaware totals can differ when the comparison uses different scope, timing, or report settings.

  • Compare the same billing account, project set, and date range.
  • Use a completed day or month rather than the current partial day.
  • Confirm whether you are comparing standard or detailed export data.
  • Check whether credits, discounts, taxes, adjustments, or late-arriving charges are included in the same way.
  • Verify that labels and project filters are applied consistently.

When to Contact Cloudaware Support​

If you have verified Google Cloud exports, BigQuery or Cloud Storage permissions, and Cloudaware configuration but issues persist:

  • Collect the following before opening a ticket:
    • Cloudaware org name and affected Google Billing integration.
    • Google Cloud billing account and project IDs in scope.
    • BigQuery project, dataset, and table names, or Cloud Storage bucket and path.
    • Screenshots or samples showing:
      • Google Cloud Billing export configuration.
      • BigQuery tables or Cloud Storage objects with recent billing data.
      • Google Billing integration status and any error messages in Cloudaware.
  • Contact Cloudaware Support via your usual channel or support@cloudaware.com and include the collected information for faster triage.