Auto-detect historical CUR changes and refetch

Currently, Cloudability’s one-month lookback window for AWS CUR changes creates a "data drift" between the cloud provider's billing truth and the FinOps platform. AWS frequently applies retroactive adjustments—such as EDP credits, refund corrections, BMods, or Savings Plan/Reserved Instance (RI) backdated adjustments—that can fall outside the 30-day window.

Without this feature, FinOps teams must manually request "backfills," leading to inaccurate reporting, audit risks (GL mismatch), and manual overhead (by both customer and IBM in identifying and fixing data discrepancies).

Who Would Benefit
FinOps Practitioners - Saves hours of manual reconciliation and support ticket management
Finance/Accounting - Ensure the "source of truth" for cloud spend is accurate for long-term budgeting and tax reporting
Executive Leadership - Provides confidence in ROI calculations and long-term spend trend analysis (e.g., 3Y CAGR)

How It Should Work
Automated Manifest Monitoring: Cloudability should continuously monitor the AWS CUR S3 bucket manifest files.
Change Detection: If a manifest file is updated for any month within the last 36 months (covers up to 3 year commitments), the system should flag that month for re-ingestion.
Configurable Lookback: Provide an administrative setting where users can define the maximum lookback window (e.g., 12, 24, or 36 months) to balance data processing needs.
Differential Processing: Ideally, the system should identify the specific changes to minimize processing overhead, but at a minimum, it should trigger a full re-ingestion of the affected month’s data.
Status Notification: Provide a "Data Integrity" dashboard or log showing when historical months were last updated due to detected CUR changes.