Revenue Orders are high-level 'container records' for Revenue Details that have gone through the Update Revenue Details process. Revenue Details contain Charge data that has been shaped by Revenue Configuration Map specifics (summarization of one or many Charges). This information is passed over to ARM where the Revenue Arrangement, a 'container record' for Revenue Elements, will contain the details of the revenue to be recognized.
One or more Revenue Orders will be associated with a Subscription after running Update Revenue Details (as long as that Subscription is assigned a Revenue Configuration).
- If the Revenue Configuration Revenue Order Source is ‘Inherit from Subscription’, there will be one Revenue Order per Subscription.
- If the Revenue Order Source is ‘Batch’ or ‘null’, a new Revenue Order will be generated each time one or more Subscription Items are added to the Subscription following the initiation of the Update Revenue Details process. The previous Revenue Order will be left intact.
How revenue records relate to each other
As Charges bill and ZoneBilling processes revenue, five related record types work together to keep your billing data and NetSuite's Advanced Revenue Management (ARM) module in sync:
| ZoneBilling record | Think of it as... | NetSuite ARM equivalent |
|---|---|---|
| Revenue Order | The container for a subscription's revenue processing. ZoneBilling can create multiple Revenue Arrangements from a single Revenue Order | Revenue Arrangement |
| Revenue Detail | One recognizable slice of revenue, grouped per your Revenue Configuration | Revenue Element |
| Revenue Recognition Event (ARM record used by ZoneBilling) | A point-in-time value on a Revenue Detail (e.g., initial forecast, or an actual billed amount) | Revenue Recognition Event |
| ZAB Revenue Link | The connection between a billed Charge and the Revenue Detail it belongs to | — (internal to ZoneBilling) |
| ZAB Transaction Revenue Link | The connection between a specific billed transaction line and the Revenue Detail, used to tell ARM which invoices are related to each revenue element / arrangement | — (internal to ZoneBilling) |
For more on how these records are created and kept in sync, see Update Revenue Details Overview and What's Changing in ZoneBilling Revenue Billing Events.
Fields on the Revenue Order record:
- Subscription: The Subscription associated with the Revenue Order. A Revenue Order cannot be tied to multiple Subscriptions.
- Subsidiary: This field is populated by the Subsidiary assigned to the Subscription.
- Customer: This field is populated by the Customer assigned to the Subscription.
- Approval Status: Depending on the Revenue Configuration assigned to your Subscription, approval may be required for Revenue Orders. If the status is Pending Approval, no ZoneBilling Revenue information will be passed to ARM. Approval can be accomplished by manual toggling Approval Status on the Revenue Order or using the Approve Revenue Orders suitelet (Transactions > Zone Advanced Billing > Approve Revenue Orders).
- Date: This field is populated by the Start Date assigned to the Subscription.
- Currency: This field is populated with the Currency assigned to the Subscription.
- Exchange Rate: The exchange rate will be set based on the 'Revenue Date' on the Revenue Detail (this field will be populated with the corresponding exchange rate between the Subsidiary’s base currency and the Revenue Order currency for the relevant accounting book). A Revenue Date may be set on the Revenue Detail via the Revenue Configuration. If no Revenue Date is present on the Revenue Detail, the Revenue Order Date will be used for currency exchange rates.
- Department: This field is populated by the Department assigned to the Subscription.
- Location: This field is populated by the Location assigned to the Subscription.
- Class: This field is populated by the Class assigned to the Subscription.
- ID: This is a unique ID assigned by the system for identification purposes.
- Date Last Detail Sync: This is the timestamp of the last time the Update Revenue Details function was performed on the Subscription where there was relevant information to re-sync.
- Line Unique Key Version: This field determines the version used for Line Unique Key on the Revenue Details. It should not be changed unless advised by Zone & Co Product personnel.