Ripple now supports Payers that use AWS Billing Transfer — AWS's feature for transferring billing ownership to a different Payer.

MSPs proceeding with Billing Transfer migrations for AWS Partner Program incentive eligibility can continue using Ripple seamlessly throughout the transition.

Where to configure A Billing Transfer toggle and start month input have been added to the Payer Settings screen.

New fields:

CUR references during the transition month

For periods spanning the Billing Transfer transition month, Ripple references both the old and new Payer CURs simultaneously, ensuring:

This ensures invoice accuracy immediately after the transition while correctly visualising usage in the new environment.

Cancelling a Billing Transfer

Billing Transfer can also be cancelled from within Ripple (on a monthly basis).

AWS Billing Transfer takes effect from the start of the month. Access to both old and new CURs must be maintained until the previous month's CUR is finalised — typically around the 5th to 10th of the following month.

A new CUR must be created on the new Payer side for the transferred accounts. Historical data remains on the old Payer. If you need historical data reflected on the new Payer, a Backfill request to AWS Support is required.

Even with Billing Transfer enabled, processing will work correctly as long as the input information is accessible from Alphaus — standard CUR format is fully supported.

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