Ripple & Wave – AWS Billing Notes and Considerations

This guide walks you through key considerations when operating Ripple, including how billing amounts are finalised, how Ripple and Wave interact, and important notes on support charges and discounts.

AWS CUR updates occur at random intervals. Pay-as-you-go charges are finalised when the AWS PDF invoice is issued, but in rare cases, CUR updates may occur even after billing has been confirmed.

Notes You can verify whether billing amounts have been confirmed in CUR by checking the Invoice ID in Ripple's billing confirmation notification.

AWS: Pay-as-you-go (Usage) costs for the previous month are typically finalised around the 4th of each month.

Items under Adjusting Entries — including Fee, Credit, Refund, Discount, and Marketplace — are confirmed in CUR as each item is finalised by AWS and are reflected in Ripple's Adjusting Entries in real time. While the timing of each item varies, all amounts are generally finalised by around the 15th of each month.

Azure: Previous month costs are typically finalised around the 9th of each month, including subscription charges and software licence fees.

GCP: Amounts tend to be finalised around the 5th of each month. However, if discounts or special contract arrangements apply, cost reflection may be delayed.

Wave reflects daily CUR data in real time, updated approximately three times per day. This daily data is refreshed continuously and may include updates to past usage charges. Wave automatically reflects daily data from the 1st of each month, but final amounts are only confirmed after Ripple's monthly aggregation is complete.

Since CUR updates occur frequently, Wave's daily data should be treated as a reference figure. Final amounts are confirmed in both Ripple and Wave after Ripple's monthly aggregation is complete.

Wave reflects the latest available CUR data on a daily basis. When the billing confirmation button is clicked in Ripple, Wave also recalculates based on the final data at that point — ensuring that the amounts displayed in Wave match the amounts billed in Ripple.

Due to the nature of AWS CUR, charges are not officially finalised until the billing confirmation of the following month. In rare cases, this can result in duplicate cost entries in Wave.

Notes Example: If an EC2 instance listed under Region A is updated in CUR to Region B, Wave may temporarily show costs for both Region A and Region B for the same instance, resulting in a duplicate entry.

If you notice any discrepancies in the amounts displayed in Ripple or Wave, please contact Alphaus and we will investigate.

If you make changes to the AWS accounts, tags, Azure subscriptions, or Google Cloud projects linked to a Billing Group, you will need to run aggregation to reflect those changes.

Wave updates daily usage charges based on the Billing Group settings at the time of the most recent aggregation. To reflect any changes to Billing Group settings in Wave, aggregation must be run again.

AWS support charges are calculated based on AWS usage charges. Since Ripple's calculation process may affect the AWS usage amount, support charges must be calculated accordingly.

AWS support charges are classified as follows depending on the contract type:

All of the above AWS charges are calculated based on Unblended usage.

To calculate support charges based on True Unblended costs, use the invoice settings in the Billing Group configuration. Since support charges in the Billing Group are calculated according to the Unblended or True Unblended setting in the Billing Group, it is generally recommended to use the Billing Group invoice settings for support charge calculation — except when passing through AWS charges directly.

Important Notes Billing both the support charges calculated in the Billing Group settings and the support charges billed by AWS will result in double-billing. Please ensure only one source is used.

Depending on your contract with AWS, certain services such as Marketplace may not be eligible for discounts. We recommend reviewing your AWS contract before configuring billing settings.

The Service Discount & Markup → feature allows you to adjust discount amounts applied per service. For Marketplace charges, individual configuration in Ripple is required — please contact the Alphaus support team if needed.

If any errors occur during the process or if you have any questions, please reach out to us: