The Revenue Order Source determines how to manage Revenue Details created after a Subscription has a Revenue Order assigned.
If the Revenue Order Source is 'Batch' or is null, New Revenue Details are placed on new Revenue Orders, if a Revenue Order already exists on the Subscription.
The example below shows the expected behavior where Revenue Order Source = Batch on a Subscription undergoing a modification (a revenue impacting change to the Subscription). This example assumes there is no Merge/Split profile being used.
This is a legacy configuration option and should not be used for newly created Revenue Configurations. This is here to understand the expected behavior for any configurations where it already exists.
- A new Subscription is created with a Revenue Configuration where the Revenue Order Source = Batch.
- When Update Revenue Details is run the first time, a single Revenue Order is created with Revenue Details (as defined by the Revenue Configuration Field Mappings).
This represents a single Batch. - When Update Revenue Arrangements & Plans (native NetSuite ARM process) are run the first time, a single Revenue Arrangement is created with a Revenue Element for each Revenue Detail.
- At this point, when a modification occurs the impact of using Batch can be demonstrated.
In this example, a new Subscription Item is added, but the expected result would be the same for any contract modification that occurs (ie, upsell, downsell, etc) where we would expect newly created Revenue Details and a new Revenue Order.
- When Update Revenue Details is run again, a new Revenue Order is created with the new Revenue Detail(s).
This represents a new Batch. - When Update Revenue Arrangements & Plans is run again, a new Revenue Arrangement is created with the Revenue Element for each Revenue Detail.
Summary of Batch
- One Subscription with multiple Revenue Orders and Revenue Arrangements
- One Revenue Arrangement per batch of newly created Revenue Details