Skip to main content

Zuora Revenue 37.009.00.00 Release Notes

Zuora

Zuora Revenue 37.009.00.00 Release Notes

This article provides a summary of new features, enhancements, and resolved issues that have been delivered after version Zuora Revenue 37.008.00.00 was released.

New features and enhancements

The following new features and enhancements are available in this release. 

UI enhancements to Revenue Workbench

The Revenue Contract Detail page in Revenue Workbench is being continuously enhanced to improve user experience. The following enhancements are delivered in this release:

  • In the Contracts/Orders tab, when you are viewing the line details or charge details, the Line Details or Charge Details dialog has a drop-down option for you to switch the current view. Previously, this option did not work. This usability issue has been resolved now.

  • To take any action either on the contract level or on the line level (transaction, POB, and charge) in the Contracts/Orders tab, the hamburger icon was previously used to display the applicable actions. From this release, the hamburger icon to display the action menu on the contract level is changed to three vertical dots icon-rc-action.png . The icon to display the action menu on the line level is changed to three horizontal dots and the line-level icons are available in the column called Actions (as shown in the following graphic). This column is fixed to the right side of the UI when you are scrolling left and right to view the line details. 

    new-workbench.png

  • The layout of all tabs on the Revenue Contract Detail page is optimized to better utilize the UI space. When the header section is collapsed, more records can be displayed based on the available UI space on the screen.

  • The design of the Impairment window is updated. The editable columns, Impairment Type and Comment, are moved and fixed to the left side of the window when you are scrolling to see the line details. The Cancel button is provided as well as the Save button to cancel or save your changes to the table. The icon for managing the table layout is changed to icon-manage-layout.png.

    impairment-window.png

  • (37.009.01.00 or later) The following enhancements are made to the waterfall data presentation in Revenue Workbench. The enhancement of a toggle switch is specific to the Waterfall tab, and others are also applicable to the Line Detail window when you are viewing the waterfall data for a specific line from the Contracts/Orders tab.

    • In the Waterfall tab, a toggle switch is added to switch the display between the table view and graph view, with the table view as the default display. 

    • In both the Waterfall tab and waterfall view of the Line Detail window, the previous icon for hiding and displaying the filter option has been removed, which can enable the user to always see the criteria that are applied to generate the Waterfall reports. Besides, the Manage Layout icon has been changed to icon-manage-layout.png to be consistent across the UI.

  • (37.009.01.00 or later) The Release Hold window and the Apply Hold window are enhanced:

    • In the Release Holds window, the editable fields, Release Reason and Release Comments, are moved to the front side of the table so that you can easily view them. The Release button is now enabled only when the release reason and release comments are provided.

    • In the Apply Hold window, the save icon is replaced with a Save button. The Save and Cancel buttons are made to look more visually clear, which aligns with the Release Holds window.

Universal UI enhancement

In the new UI of Zuora Revenue, all the mandatory fields are indicated by a vertical green bar. To align with universal conventions, the UI is refreshed to use the red asterisk (*) to indicate the mandatory fields in the UI.

ELP calculation change for Billing - Revenue Integration Edit section

This enhancement is applicable only if you use Billing - Revenue Integration.

To ensure data consistency for CCV calculation in Billing - Revenue Integration environments, we no longer use the latest unit list price in the product catalog to calculate the extended list price (ELP). Instead, we will take a snapshot of the unit list price on a rate plan charge at the time when the rate plan charge is created and then use the snapshot to calculate ELP. 

Data migration will occur in all tenants to take a snapshot of the current unit list price for existing rate plan charges. The limitation is that, for existing rate plan charges, the unit list price in the product catalog at the time of data migration will be used, which might not be the same as the unit list price upon rate plan charge creation.

Enhancements to Close Process dashboard

From this release, several enhancements are delivered for the Close Process dashboard. In the existing Data Validation tab, the following items are added:

  • A validation item called Impairment Accounting Exception is added to show validation errors caused by contract impairment. When a revenue contract is canceled for a partial term (reduced term), there might be unposted adjustment revenue pertaining to the canceled future term. In this case, the system will rely on the Impairment Type flag to determine how to handle the impairment amount of adjustment revenue. If the Impairment Type flag is not defined appropriately, it will be reported as a contract impairment exception. Click Summary to see the number of affected transaction lines, unreleased adjustments, and error messages. Click Details to get more information about the transaction lines, such as contract ID, sales order number, extended sell price, etc. You can also take appropriate action to fix the impairment exception from there.
  • Another validation item called Journal Entries is introduced to indicate the status of journal entries in various stages of completion. Click Summary to see the breakdown of the numbers of journal entries in different statuses. Click Details to go to the Manual Journals page to review the pending journals and take appropriate action.

In addition, to ensure the completeness of data collected into Zuora Revenue in terms of booking and billing, the Bookings & Billings tab is introduced to provide the breakdown of bookings data and billings data by data source and transaction type as shown in the following graphic.

bookings-billings-tab.png

Enhancements to Revenue Reports

In this release, multiple enhancements are delivered for Revenue reports.

Exchange rate support for some reports

We offer support on exchange rate conversion for a few identified reports. From now on, you can upload the exchange rate by using File Upload functionality with other relevant details. The uploaded exchange rate will be used in the following reports:

  • Revenue Insight

  • Waterfall Report

  • RC Rollforward Report

  • Unsatisfied POB Balances

  • Revenue Summary

  • Billing RollForward Report

Enhancement to PSAT/CSAT Line Level Report

Revenue from the PSAT (priorly satisfied) and CSAT (currently satisfied) POBs should be able to be identified by Contractual Revenue, VC Revenue, and Adjustment Revenue. Previously, net revenue and adjustment revenue were combined into a single column in the PSAT/CSAT Line Level Report, so you could not distinguish between net revenue and adjustment revenue. From this release, individual columns for splitting the three types of revenue are introduced to this report. You can configure the report by adding individual columns for all the revenue types.

Revenue Waterfall (Beta)

A newer and improved version of the Revenue Waterfall component is available in the Revenue Analytics feature. The Revenue Waterfall improvement feature is in the Beta phase only for selected Beta program customers.

New survey widget to collect user feedback

From this release, a new survey widget is introduced to Zuora Revenue UI to collect the Net Promoter Score (NPS) feedback. The new survey widget will be displayed for randomly selected users after the user logs in to Zuora Revenue. Use this new survey widget to provide feedback without navigating away from the current UI page.

This survey widget will be deployed to Production environments by the end of April on top of the existing patch.

Exclude non-revenue data from Zuora Billing

This enhancement is applicable only if you use Billing - Revenue Integration.

In Billing - Revenue Integration environments, some subscriptions, order line items, or invoices are created in Zuora Billing only to fulfill business scenarios. However, they might not be subject to revenue recognition in Zuora Revenue. To exclude these transactions from flowing into Zuora Revenue, you had to manually either create filters for Revenue Sync jobs or use custom attributes to enable filtering for Data Collection jobs in Zuora Revenue.

From now on, this manual work can be avoided by the introduction of the Exclusion flag for Billing - Revenue Integration. In Zuora Billing, you have the option to specify whether the related object data is to be synced to Zuora Revenue. During the data sync process between Zuora Billing and Zuora Revenue, this type of data can be automatically excluded.

After the newly introduced fields are appropriately set in Zuora Billing for charges or order line items, the Revenue Sync process can automatically examine the field value and then skip the corresponding charges or order line items if the value is set to True. For more information about the new fields in Zuora Billing, see New fields for Zuora Billing objects.

  • For the Exclusion flag set in Zuora Billing to be consumed by Zuora Revenue, make sure the following features are enabled for your tenants of Zuora Billing. These features are automatically enabled for new customers of Zuora Billing.
    • Order Line Item
    • Order Delta Metrics
    • Unified Invoicing
  • If you have previously enabled Billing - Revenue Integration and have your own customizations to exclude the Billing transaction data, some migration procedure might be required. Detailed instructions will be provided separately to the customer who does require data migration.

Role-based control for tabs on Close Process dashboard

There are multiple tabs on the Close Process Dashboard. Previously, the role-based access control is applied only to the entire dashboard. However, there might be the need of having different users or roles to be able to access different tabs instead of the entire dashboard. In this release, the role-based access control can be applied at the tab level for the Close Process dashboard. As a system administrator, when you navigate to Setups > Security > Roles to manage the privileges for a user role, you can assign different access levels for the tabs as shown in the following graphic. For general information about the role-based access control in  Zuora Revenue, see Manage user access.

access-control-tabs.png

New profile for Data Augmentation

In this release, a profile called DA_BACKWARD_COMPATIBILITY is introduced to provide backward compatibility for data augmentation. This profile determines whether to ignore the batch criteria when the system is applying data augmentation rules to the lines on Staging tables.

  • When this profile is set to Yes, the batch criteria will be used to identify the lines that are eligible for the data augmentation rules. Then, data augmentation is performed only on the identified lines in Staging tables.
  • When this profile is set to No, data augmentation will be performed on all the lines in Staging tables.

New profile for ramp deal processing

During ramp deal processing in Zuora Revenue, there is validation against the per unit per day rate (for Volume average pricing method) and the per day rate (for Term average pricing method) within the ramp deal group. The rate must be the same for all the lines within the same group. Otherwise, the validation fails and a hold is applied to the whole revenue contract. As the revenue user, you must review the revenue contract and release the hold as appropriate. 

However, during the calculation of the line-level rate, the rounding operation might cause minor differences among the line-level rates within the same group. In this scenario, revenue holds might not be necessary. It causes extra effort to review each revenue hold and manually release them one by one.

To better support this scenario where the system is expected to ignore the minor differences among line-level rates and not to apply revenue hold, a profile called RAMP_HOLD_THRESHOLD is introduced. If the difference does not exceed the specified value for this profile, the system will ignore the difference, and validation against the line-level rate within the same group will pass. The default value of this profile is 0.

For more information about ramp deal processing, see Ramp deals in Zuora Revenue.

Enhancement to VC accounting

Previously, the variable consideration (VC) accounting was wrong for VC actuals and the VC Liability was not appropriately accounted for. From this release, net accounting for VC actuals is updated for more accurate accounting as follows.

Ratable method of POB template VC accounting
Immediate
  • Dr./Cr. VC Contra Revenue
  • Cr./Dr. VC Liability
Ratable or not Immediate

Accrual accounting is available.

  • Dr./Cr. Contract Liability
  • Cr./Dr. VC Liability
  • Dr./Cr. VC Contra Revenue
  • Cr./Dr. Contract Liability

Enhancement to Unified Invoicing support (37.009.01.00 or later)

This enhancement is applicable only if you use Billing - Revenue Integration. 

As an enhancement to better support the Unified Invoicing feature in Zuora Billing, standalone invoice items created for Order Line Item (OLI) can be consumed by Zuora Revenue from this release. After the standalone invoice item is created for OLI, it will be synced and automatically transformed into invoice transaction lines by Zuora Revenue. A sales order line will be created to associate with the invoice line. 

Only the initial phase of OLI booking and its respective billings can be supported. Any update or cancellation on the OLI will not be synced to Zuora Revenue.

For more information, see Unified Invoicing in Zuora Revenue.

Bulk update or delete transaction data on Staging (37.009.01.01 or later)

Previously, when any transaction line is stopped on Staging due to data validation errors. You have to go to the Data Interface > Inbound Integration page and correct the problematic data by editing the transaction line one by one. There is no way to do a bulk update.

From this release, to facilitate the process of updating transaction data in the Staging table, a new UI page called Manage Inbound is introduced for bulk updating or deleting transaction lines in the Staging table. For more information, see Manage transaction data on Staging.

Enhancement to the new MJE feature (37.009.01.01 or later)

In version 37.008.00.00, a new UI page was delivered to Sandbox environments for manually entering or uploading journal entries along with enhanced journal approval capabilities. These new features will be delivered to Sandbox and Production environments in version 37.009.01.01. The capability of updating the reversal period for posted journal entries is also delivered as an enhancement. After the journal entries are posted, you can use the page to update the reversal period. Then, the journal reversal entry will be created in the reversal period.

For more information about the new UI page, see MJE upload.

Issues resolved in this release

Refer to Resolved_issues_in_37.009.00.00_37.009.01.00_37.009.02.00.xlsx to get a list of issues that have been resolved in this release. The allocation-related issues are listed in the following table. 

When the release notes are first published, not all resolved issues are included in the attached spreadsheet. The attached spreadsheet will be continuously updated on a bi-weekly basis for the subsequent sandbox releases until the next quarterly release. 

Engineering tracking ID Support tracking ID Fixed version Summary
ZR-10595 328380, 330586 37.008.02.00 Mismatch in Ext SSP and Price point in two instances
ZR-11888 N/A 37.008.01.00 Copy Line - Ret Qty is included in EXT FV PRC calculation for copied lines
ZR-13004 344796 37.008.05.00 Posted pct not updated correctly for the updated SO with 0$.

Documentation updates

The following documentation is updated or published for this release: