Data Health & Freshness

Accurate, timely billing data is critical for budgets, anomaly detection, chargebacks, and optimization. This guide explains how to think about data health in Cloudaware FinOps, what latency to expect, and how to troubleshoot common issues.

Key Concepts

When evaluating data health, consider:

• Freshness – how recently Cloudaware received billing data for each provider and scope (billing account, subscription, project, etc.).

• Completeness – whether there are missing days, partial months, or gaps for specific accounts or services.

• Finalization – when providers finish posting all adjustments, credits, and discounts (for example, enterprise discounts or commitment amortization) for a given period.

Cloudaware continuously pulls new billing data as exports are updated, but each provider has its own cadence and behavior for backfilling or adjusting historical costs.

Expected Latency and Provider Behavior

In practice you can expect:

• AWS

  • CUR/Data Exports are typically updated daily.

  • Some charges and enterprise discounts (for example, Enterprise Discount Program and certain RI/SP adjustments) may be posted days or weeks after the end of a month.

  • It is normal for the previous month to “settle” partway through the following month.

• Azure

  • MCA/EA exports are usually updated daily, with occasional reprocessing of historical periods.

  • Credits and adjustments can appear after the initial export is generated.

• Google Cloud

  • Billing Export to BigQuery generally updates multiple times per day.

  • Late‑arriving adjustments may update prior days in the export.

Because Cloudaware reads the provider billing exports as‑is, any missing discounts or late adjustments in the cloud console will also be missing from Cloudaware until the provider publishes them.

Monitoring Data Health

Use a combination of Billing Integrations and FinOps views:

• Billing verification

  • Use Verification to check last successful import times, file sizes, and status per source.

  • Investigate any sources that have not updated within the expected window for that provider.

• Dashboards and reports

  • Build simple daily cost trend dashboards (for example, using Dashboards & Reporting) to spot gaps or spikes across providers, accounts, or projects.

  • Compare totals with cloud billing consoles for a recent period to confirm that data is broadly aligned (small timing differences are expected).

• Operational checks

  • Incorporate data freshness checks into your FinOps or platform operations reviews (for example, weekly cost review or monthly close).

Common Issues and How to Troubleshoot

No new data for a provider

• Confirm that the relevant billing export still exists and is writing data (for example, CUR to S3, Azure export to Blob, GCP Billing Export to BigQuery).

• Verify that Cloudaware still has access to the storage location or APIs (credentials, roles, service principals).

• Check Troubleshooting for provider‑specific error patterns and resolutions.

Missing or partial days

• Inspect the raw export (for example, S3 bucket, Blob container, BigQuery dataset) to see whether the provider produced data for the missing dates.

• If files/rows are missing in the export itself, this must be addressed in the cloud billing configuration or with the provider.

• If exports look complete but Cloudaware does not show corresponding data, contact Cloudaware Support with the affected billing account, time range, and example records.

Month‑end differences and late discounts

• Expect some differences between preliminary month‑end numbers and the final values once providers finish posting all adjustments and discounts.

• For AWS in particular, enterprise and commitment‑related discounts may appear only after the provider updates the CUR/exports. Cloudaware will reflect these changes on the next ingestion run.

Best Practices

• Establish clear expectations with stakeholders about typical data latency for each provider.

• Use separate views or reports for “current, still changing” periods versus “closed, finalized” periods.

• Regularly review billing integration status and data freshness before major activities such as cost reviews, budget updates, or executive reporting.

If you continue to see unexplained gaps after following these steps, collect integration IDs, provider billing account identifiers, and recent errors from Billing Integrations, then reach out to Cloudaware Support at support@cloudaware.com for further investigation.