Skip to main content

Ripple – Differences Between Aggregated Results and AWS Charges

Understanding the Difference Between Amounts Shown on AWS and Ripple Invoices

Alphaus Support Team avatar
Written by Alphaus Support Team
Updated this week

This article explains why the usage fees aggregated in Ripple may differ from the amounts shown in AWS.

The difference resulting from the calculation logic is typically around a few SGD / MYR.

When converting to a different currency (eg. SGD / MYR):

  1. An exchange rate is multiplied to each service.

  2. After converting each service to a different currency, the total value is aggregated.

Calculation formula:

SUM(Each Service (USD) × Exchange Rate) = Total Amount

*The SUM value is processed according to the decimal rounding settings under Ripple's Invoice Settings.

Additionally, while Ripple's invoices only display up to two decimal places, the data actually holds up to ten decimal places, the same as CUR.

*However, when comparing the sum of each service amount in USD multiplied by the exchange rate, a slight difference of a few SGD / MYR may occur. To verify the exact difference, you can check the CSV file downloadable from Ripple.

When calculating support fees and discounts:

The calculation is performed in the same way as when converting to SGD / MYR, using the following steps:

  1. The discount rate is multiplied by each service.

  2. After calculating the discount amount for each service, the total value is aggregated.

Calculation formula:

SUM(Each Service (USD) × Discount Rate) = Total Discount Amount

The above is a summary of the main reasons for the amount discrepancy that occurs on Ripple.

Due to AWS specifications, the rounding process for exchange rates differs depending on the service. Since Ripple performs a uniform calculation, a slight difference will occur.

If, after applying the above formulas, you still see differences or notice that the discrepancy seems larger than expected, please feel free to contact us via the chat in the bottom-right corner.

Did this answer your question?