ZAB Revenue Configuration – ZoneBilling Knowledge Base

The ZAB Revenue Configuration record defines how ZAB Charges should be organized and staged for the purpose of creating Revenue Arrangements and Elements.

This configuration record will ultimately define:

How to summarize ZAB Charges into Revenue Details which ultimately become Revenue Elements.
Where applicable, how to segregate ZAB Charges to support multiple Revenue Arrangements

There is no limit to the number of Revenue Configuration records that can exist in the system, but in most situations there will be one record that covers standard operating procedures and possibly one or a few more for handling exceptional situations.

Name

The Name of the ZAB Revenue Configuration should clearly indicate the type of revenue profile it represents.
e.g., "Default Revenue Configuration".

Default Approval Status

The Default Approval Status field determines the status set on the Revenue Order upon creation.

Approved - Select this when there is an upstream validation that permits Revenue Orders to be approved immediately when Update Revenue Details is run.
- Revenue Arrangements and Elements will be created when Update Revenue Arrangements is run.
Pending Approval - Select this when additional controls are needed to review and approve Revenue Orders before creating Revenue Arrangements and Elements.
- No Arrangements or Elements will be created until the status is changed to Approved.
- See Approve Revenue Order Suitelet for more information.

Revenue Order Source

The Revenue Order Source determines how to manage Revenue Details created after a Subscription has a Revenue Order assigned. Choose whether the newly created Revenue Details are placed on the existing Revenue Order or if new Revenue Order(s) are created.

This field is critical for the correct end result for revenue where contract modifications (e.g., amendment, expansions, etc) may occur. When designing and testing a revenue configuration, be sure to include scenarios that test for net new business as well as any expected modifications a Subscription could have.

Inherit from Subscription (Recommended)
- Newly created Revenue Details are placed on the Subscription’s existing Revenue Order.
Arrangement Subgroup ID
- Allows configuration to direct some Revenue Details to a different Revenue Arrangement than the original.
  
  If the legacy configuration option of 'Batch' or null is used, review this article for additional information.

An example of each option is described below to show the expected result. All examples assumes no Merge/Split profile is being used.

Inherit from Subscription
Arrangement Subgroup ID

Inherit from Subscription

The example below shows the expected behavior where Revenue Order Source = Inherit from Subscription on a new Subscription through a modification (a revenue impacting change to the Subscription). This assumes an Arrangement Subgroup ID is not being used.

A new Subscription is created with a Revenue Configuration where Revenue Order Source = Inherit from Subscription.
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).
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 Inherit from Subscription can be demonstrated.
In this example, a new Subscription Item is added, but the result would be the same for any contract modification that occurs (ie, upsell, downsell, etc).
When Update Revenue Details is run again, the same Revenue Order is updated.
In this example, an existing Revenue Detail was updated rather than a new one getting created. This is due to the Revenue Configuration Field Mappings. If the field mappings had been configured in a way to create a new Revenue Detail, we'd still expect to see the new Revenue Detail on the existing Revenue Order, not a new one, when Inherit from Subscription is selected.
When Update Revenue Arrangements & Plans is run again, the same Revenue Arrangement is updated, with some updates to the existing Revenue Element.

In this example, an existing Revenue Element was updated rather than created. If a new Revenue Detail had been created, we'd expect to see a new Revenue Element, but still on the same Revenue Arrangement when Inherit from Subscription is selected.

Only some native NetSuite fields on a Revenue Element can be updated with new information. Custom fields can only be set during Revenue Element Creation. See this article for more information about data flow during create vs update.

Summary of Inherit from Subscription (with no Arrangement Subgroup ID)

One Subscription with Revenue Arrangement
- All Revenue Elements will be created and added to the existing Revenue Arrangement.

Arrangement Subgroup ID

The example below shows the expected behavior where a new Subscription has Revenue Order Source = Inherit from Subscription AND mapping to the Arrangement Subgroup ID field on the Revenue Detail.

A new Subscription is created with a Revenue Configuration where the Revenue Order Source = Inherit from Subscription and Arrangement Subgroup ID has a Charge Field Definition linked from a custom field named "Opp Type".
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).
When Update Revenue Arrangements & Plans is run, we see a Revenue Arrangement created for each unique Arrangement Subgroup ID, and with a Revenue Element for each Revenue Detail.

Regardless of when the Charges were created, we'd expect to see a Revenue Arrangement created for each unique Arrangement Subgroup ID.

Summary of Inherit from Subscription with no Arrangement Subgroup ID

One Subscription with one or more Revenue Arrangements
- A Revenue Arrangement will be created for each Arrangement Subgroup ID that may exist on a Subscriptions.