Savings Plan Analysis from AWS CUR

Hello,

I found this accepted re:Post answer on a similar ask: AWS CUR re:Post.

If needed, our Billing & Accounts team can also be reached, here: go.aws/support-center.

- Elle G.

Hello, let me help explain this common confusion with Savings Plans reporting:

1. Main Reason for Discrepancy: The Savings Plans Coverage Report and CUR calculate covered spend differently:

   • Coverage Report: Shows the theoretical maximum coverage based on your Savings Plan commitment and eligible usage
   • CUR: Shows the actual applied savings and usage at a more granular level

2. Key Differences:

   • Coverage Report aggregates data at a higher level and might include:
     • Partial hour coverage
     • Instance size flexibility calculations
     • Regional benefit calculations for regional SPs
   • CUR shows the actual transaction-level data with:
     • Exact usage records
     • Actual savings applied
     • More granular timing

3. Source of Truth:

   • For financial/billing reconciliation: Use the CUR
   • For Savings Plan optimization and coverage analysis: Use the Coverage Report

4. Additional Verification: To cross-validate, you might want to:

   • Check if you're including all relevant line item types in CUR
   • Verify the time periods match exactly
   • Ensure you're accounting for any timezone differences

The discrepancy you're seeing is generally expected behavior due to these fundamental differences in how these reports calculate and present the data.

I hope this is helpful. If yes, would love your acceptance/upvote. Thank you!