This article provides a summary of new features, enhancements, and resolved issues in the Zuora RevPro application.
If you are using ASC 605, when an approval rule is applied to an arrangement, the revenue can be released and you can review the waterfall and accounting entries before they are posted. The accounting entries cannot be posted to GL if the approval is pending. However, when using ASC 606, you cannot release or defer the revenue when an approval is in the Approval Pending status.
In this release, RevPro introduces a new Release Revenue checkbox in the Edit Approval Rule page. If you select this checkbox, RevPro will not restrict you from releasing revenues. This enhancement resolves the discrepancy between the adoption of ASC 605 and ASC 606 in RevPro.
Change Password Feature Redesign
In this release, Zuora RevPro enhances the Change Password feature. The following behavioral changes are made when you are editing a user after navigating to Setups > Security > Users in the RevPro UI:
- If you are logged in as a Sysadmin user, you can view and change the password for all existing users. While changing the password for a user in the Change Password tab, you must enter your account password in the Admin Password field before entering the new password. Previously, RevPro did not validate the admin password.
- If you are logged in as a user of another role, you can only view and change the password of your account. The Change Password tab is not available when you edit the security information of other users.
Fields for Lines Copied from Another are Available for Editing
Now, RevPro has enhanced the Copy Line feature, which allows you to edit the following fields for a line created by copying another line, irrespective of their Editable flag settings:
- Sales Order Number
- Sales Order Line Number
- Order Quantity
- Extended List Price
- Extended Sell Price
- Unit List Price
- Unit Sell Price
- Sales Order Date
If you do not specify the Unit List Price or the Unit Sell Price, RevPro will derive the value for both fields based on Ordered Qty, Ext List Price, and Ext Sell Price.
Previously, when you copied a line from another in a POB, you could not edit these fields in the new line if their Editable flags in the Labels page were set to No.
VC and Cost Operation Sequence Reordering
RevPro enhances the Variable Consideration (VC) and the Cost user interface in the Policies section in this release. The options under the operation menu in the Variable Consideration and Cost page are reordered to align with the sequence of the actions you need to take: Manage Fields, Manage Formulas, Manage Types, Manage Rules, and Download Template. This change improves the logicality and usability of the Cost and VC user interface.
Viewing Cost Options After POB is Consumed
After a POB is consumed, you cannot edit this POB until you create a new version. However, previously, RevPro did not even allow you to view all options in this POB after the POB consumption. From Release 18.104.22.168, RevPro gives you the visibility of all the options on a cost in the Cost treatment tab of a POB, which will help you understand the cost and corresponding operations.
Support for Incremental Reporting Summarization
Previously, incrementally running the reporting summarization job was not supported in RevPro. In this release, RevPro improves the summarization program to support the incremental reporting summarization. When you run an incremental summarization, RevPro will go through the revenue contracts to be processed and determine the ones that have been changed since the last time the summarization was successfully completed using the
Forecasting Dates Customization
If you provided both the end date and the duration of a Sales Order when doing the forecasting, RevPro would ignore the duration and takes only the end date into account in the past. Now, RevPro supports the customization of forecasting dates before the forecasting is triggered. With this feature, you have the capability to generate the forecast based on the customized dates and a line can have a different start date and end date. This enhancement introduces the stage handler before and after the forecasting process to achieve the desired results through custom extensions.
Support for Cancellation of Standalone Invoice Containing Positive or Negative Values
Previously, the cancellation of standalone invoices that contain positive or negative values was not supported. This issue is resolved now. From this release, RevPro starts to support the cancellation of the standalone invoices that contain positive or negative values. When the standalone invoice is cancelled, the corresponding sales order created by the system is also cancelled. Hence, the total line value becomes zero. The same logic can be leveraged for the standalone credit memo if it is brought into the system as a negative invoice.
Validation Process Master Enhanced with Multiple Holds
The RC Validation Process Master is further enhanced in this quarter, which allows you to identify the following issues in an RC when it is created. If an exception is identified after running this program, RevPro will apply the transfer hold on the RC and stop the problematic RC from the transfer posting. This program helps you identify and solve problems at an early stage.
- Mismatch between the total transaction price and the revenue amount in deferred and released bucket
- Incorrect sign between the positive charge and the revenue amount in deferred and released bucket and vice versa
- For a positive charge line, total billed revenue in deferred and released is negative
- Incorrect Release percent for a charge
- Mismatch between the total billings amount and Initial Accounting entries
- Release percent for contractual revenue and allocation revenue not matching (limited to retrospective)
- Duplicate Billing Lines
- Duplicate SO Lines
- Incorrect flagging of release holds
Nine different seeded holds are introduced accordingly. When a revenue contract has one of these issues, the Validation Process Master program applies a hold. For the next run of validation process master, all the revenue contracts that have the hold are applied along with other revenue contracts that have the accounting changes from the previous run.
Validation Process Master Program Enhanced for Multi-Org
Previously, when you ran the RevPro3.0 RC Validation Process Master program, it did not allow you to specify a particular Org ID and run a specific organization instead of executing all the organizations associated with the current role. In order to give you more flexibility on program scheduling, in this release, RevPro makes the following improvements:
- RevPro includes the Org ID parameter in the RevPro3.0 RC Validation Process Master program. Org ID is a mandatory parameter if you are a Multi-Org user. For Single-Org instances, you do not need to specify this parameter manually because RevPro can pass the corresponding Org ID for you.
- Specific to Multi-Org instances, RevPro creates a new RevPro3.0 RC Validation Process Master for Multi-Org program that does not require the Org ID parameter. This program executes across all the organizations associated with the current role.
Adding Filters to Layout
If you needed to apply a filter to a layout, you must create a new layout and then associate the filter with it. Associating the filter to an existing custom layout was not supported. Now, you have the capability to add a filter to the custom layout that you defined earlier. A new Assign Filters tab is added to the Edit Layout page, where you can manage the relationship between the filters and the layout.
New Waterfall Type
You could not use the billed revenue to filter revenue contract lines and generate the Waterfall prior to this release. Now, a new Billed Revenue option is added to the Waterfall Type field in the Waterfall tab of the Revenue Contract Detail page. It enables you to filter RC lines based on the Billed Revenue Waterfall type and then generate the corresponding Waterfall.
SFC Amount Available to be Split at Different Levels
Previously, if the SO LINE ID in an SFC Upload was not populated, RevPro would split the SFC amount across all the lines in the Revenue Contract. If the SO LINE ID was present, the entire amount would be allocated to the line. Now, RevPro enhances the VC Upload process and supports splitting the SFC amount at different levels. You can set the value in the Level of SFC Allocation field in an SFC Upload to indicate if an amount is split at the RC, POB, or Transaction level. For instance, when the Level Of SFC Allocation is set to POB, the amount is allocated within the lines of a POB irrespective of whether this POB has a single line or multiple lines.
Support for Handling Prorated Lines
RevPro did not support prorated lines in the past. It could lead to the following issues:
- The CM-C could not be referenced back to the invoice being cancelled, which could cause the unnecessary accumulation of accounting schedules and lead to the performance issue in RevPro.
- The incorrect calculation of Per Unit Price and could impact the overall allocations in RevPro if SSP is price based.
In order to meet the requirements of integrating with the Zuora Central, RevPro provides you with the capability of handling prorated lines now. The following changes are made in this release:
- RevPro introduces a new PRATE transaction type which will have a separate treatment of prorated lines which interfaced to RevPro.
RevPro introduces a new tenant-level Allow Overstate Order profile option that indicates when to true up the following data points on a subscription order through billing:
- Ext List Price
- Order Quantity
- Billed Quantity
When this option is set to Yes, RevPro increases the quantity and the Extended List Price on a subscription order if the invoice quantity and the Extended List Price is greater than the subscription order.
Additional Attributes Available for Cost Reports
Prior to this release, if you were using the cost accounting feature in RevPro, you could not view the additional information through attributes on the cost reports because only 10 attributes were allowed in the report. Now, additional attribute columns, from Atr11 through to Atr60, are added to the cost object. If additional information is made available through SO upload, RevPro will copy the attribute information to the cost object. Alternatively, you can upload it through the transaction CST that is specific to the cost processing. Cost reports can provide additional information associated with various cost types.
Approvals Skipping Transaction Owner
Previously, as a user who has the approval authority on the capital for an organization, you upload a transaction for approval but RevPro would mistakenly skip you and forward this approval to another user based on the approval rule. RevPro resolves this issue in 22.214.171.124. You will be the first one to approve transactions in the same scenario.
Unbalanced Entries in Schedules
Suppose you collected several sales orders, some of which have their CV Eligible flags set as Y. Then you collected another SO of the zero dollar value and the CV Eligible flag set as Y. When you ran the transfer accounting schedule, open the next period, and cancel the SO collection for the $0 SO, it would lead to unbalanced entries in the schedules. This issue is resolved in 126.96.36.199 and (Cr-Dr) is netting to zero for Adjustments now.
Amount of Allocation Entries Created Higher than CV Amount
Previously, in some prospective scenarios, when the revenue was released in the revision period, the allocation revenue would be created more than that of the carve amount for the line. RevPro resolves this issue in this release. Now, when you create allocation schedules, the allocation revenue schedules equal the amount of carve amount.
Cannot Map Account Type to Income Statement Account
In some cases, when you attempted to map an account type to a particular Income Statement account in the Cost type tab of the Manage Cost Types page, RevPro prompted the 1 record(s) have been saved successfully message, but the mapping disappeared after you save the change. This issue is resolved in this release and this mapping can be saved successfully.
"No Allocation" Contract Mod Rule Incorrectly Triggers Retrospective
Any new POB within SSP Range should trigger the No Allocation allocation treatment based on the Contract Mod Rules. However, the No Allocation Contract Mod Rule was incorrectly triggering Retrospective. RevPro resolves this issue in this release.
Incorrect Status upon Submitting Approval Manual JE
Previously, when you submitted a Manual JE with no Approval Rule Criteria defined or did not satisfy the Approval Rule Criteria for approval, its status would be incorrectly changed to Approval Canceled and it could not be processed further. Now, RevPro fixes this issue. The status is now corrected to Approval rule not defined after submission in the same scenario.
Excessive Release Revenue
If a contract modification existed, excessive revenue would be released on the POBs with release events. For example, if 30% of the revenue was released, then RevPro would automatically release an additional 30% or the remaining 70%. This issue is resolved in 188.8.131.52 and the revenue is released correctly now.
GL and Manual JE Interface Setup Issue
While updating the fields in GL mapping or Manual JE mapping in the Interface Setup page, you might encounter the issue that RevPro threw an error after saving the fields. For example, if a Source SQL contained special characters that the system could not recognize, RevPro would throw a validation error. In this release, this issue is fixed. You can now save the expressions with special characters in the GL and Manual JE Interface setup successfully.
Waterfall Tab in RC Details Displaying Incorrect Account Number
In some cases, you might find that the Waterfall tab in the Revenue Contract Details page was displaying the contractual revenue GL account number for the Adjustment Revenue Waterfall lines. It should display the account number where the actual adjustment revenue was booked. This issue is resolved in 184.108.40.206. The Waterfall page displays the correct account numbers now.
Credit Memo Referencing SO Not Working
Previously, when you created an SO line with multiple partial invoices, the value of SO got bumped up. After you created multiple credit memos that referenced to the SO, you might find that only the value of the first invoice was knocked off and the others went into the Unreleased Revenue. RevPro resolves this issue in this release.
SO Lines with Full CM Not Participating in Allocation
Previously, RevPro considered the SO lines that had full credit memos with the CM type as a return. RevPro marked the Return flag for such SO lines as Y and these SO line were not participating in allocation. This was incorrect because even full CM can be treated as a price change. SO lines may have the list price, based on which SSP is calculated, and the list price must participate in the allocation even if the allocatable price is 0. Now, RevPro fixes this issue. The SO lines that have full CM will participate in the allocation and the Return Flag will be set to N.
Uploads Running into Oracle Internal Error
You could encounter the issue where all the indicator in the head table were updated as Null because all transaction uploads ended up in the Oracle internal error. This issue is fixed in this release. All the indicator in the head table remains intact and no error occurs in the transaction upload.
Netting Picks up Account Type Impairments
During the Netting process, RevPro used to wrongly include the account type impairment schedules. In this release, this issue is resolved. The account type impairment schedules are not picked up in Netting anymore.
Data Collection Error
Under certain circumstances, transactions could get stuck in Staging with the Oracle Internal error: See the Log for More info error. This issue was caused by out-dated POB IDs which no longer exist in the system. RevPro resolves this issue now and the POB IDs in schedules are updated to the latest.
RC with Impairment Mistakenly Displayed in Initial Status
Previously, an RC with impairment was mistakenly displayed in the Initial status in the Revenue Contract Details page, even after the collections triggering the Contract Impairment happened in different accounting periods. In this release, this issue is resolved and the RC is correctly displayed.
Credit Memo Cancellation Not Displayed in Billing
If you uploaded a credit memo and canceled this credit memo afterwards, you could not see this canceled credit memo line in the Billings tab of this revenue contract. Only INV and CM lines were displayed. Now, RevPro adds a Cancel Flag column in the Billings tab in the Revenue Contract Detail page, which indicates if this transaction has been canceled. Hence, this issue no longer exists.
Validation Issues When Creating New Hold
Previously, you could run into the following issues when creating a new hold:
- If you set the Hold Type to Revenue Hold or Approval, and did not select the Release Event field, you would get the Release Event is required error message. This error message is inaccurate because only either the Release Event or the Allow Manual Apply and Allow Manual Release is mandatory.
- If you set the Hold Type to Transfer Hold, even if you had given the values to all the required fields, you still could not save the hold until you have specified the Schedule Type field.
In this release, RevPro resolves this issue by improving the UI. When creating a new hold:
- If you set the Hold Type to Revenue Hold or Approval, and did not select the Release Event or Allow Manual Apply and Allow Manual Release, you will get the Release Event or Allow Manual Apply and Allow Manual Release should be mandatory error message.
- If you set the Hold Type to Transfer Hold, Schedule Type is explicitly marked as a required field.
Cannot Access RC Workbench after Collecting SO with CST Lines
When you were collecting an SO with zero dollar and the CST lines for this SO which had a cost, the data would be successfully collected but an error message was displayed in the UI when you attempted to open this RC in the RC Workbench afterwards. RevPro fixes this issue in 220.127.116.11. The RC Workbench works fine in the same situation now.
OnHold Accounting Report Not Displaying RCs on Hold
RC on hold means the RC that has the current unposted schedules belonging to an old delinked RC. Previously, the report generating query missed the current RC from the RC_LINE_G field. Hence, OnHold Accounting Report did not display the RCs on hold. RevPro resolves this issue in this release. You can see the on-hold RCs in this report from now on.
Net List Price and Net Selling Price not calculated correctly
Previously, if SO and Invoice lines were released upon booking and you collected RORD or CM-R for these lines in the same or another batch, you might find that the net List Price and the net Selling Price were not calculated correctly. This issue is resolved in this release and the net List Price and net Selling Price are correctly updated in the same scenario.
Missing Schedule Id in RPRO_RC_SCHD_DEL_G Table
If you deferred a zero dollar line and then delinked this line from the RC, RevPro would delete the entry from
RPRO_RC_SCHD_G but did not insert an entry in the
RPRO_RC_SCHD_DEL_G table. This issue is resolved in RevPro 18.104.22.168. the Schedule ID can be found in the
RPRO_RC_SCHD_DEL_G table after you defer a $0 line and delink the line from the RC.
Zero-Dollar Revenue Release Issue
If a subscription has only one sales order with the zero-dollar selling price, when you updated the selling price to a non-zero value, the revenue for the $0 SO line or the PORD line could not be released. RevPro fixes this issue in this release. Now, the revenue can be released correctly.
VC New Amount Not Updated After Uploading VC Actuals
When you tried to upload VC Actuals with all the relevant data, the VC new amount (
NEW_AMT) column was not updated with the amount in the
RPRO_LN_VC_EVENT_G table. This issue is resolved in this release. Now, the new amount field is updated with the value provided in the uploaded file.
Reversals Not Created for Negative Updated SO
Previously, if you collected a negative SO line with the upon booking release event and a negative invoice with the amount less than the SO amount, when you updated the SO to the invoiced amount, the reversal would not be not created. This issue is fixed in RevPro 22.214.171.124. In the same case, the reversals will happen correctly.
Role Enabled Column Incorrectly Stamped in User Assignment Report
Even if a user role was not enabled in the Role Assignment tab in the Editing User page, the Role Enabled column in the User Assignment Report was still stamped as Yes. RevPro resolves this issue in 126.96.36.199. The Role Enabled column of a user is now stamped in accordance with the user setting.
Waterfall Displayed Revenue of Entire Period Although Revenue Start Date Was Not Beginning of Period
Suppose you created an RC in MAR-18 Period and then added a new POB in APR-18 with 21-APR-2018 as the revenue Start Date. Prior to this release, the waterfall was incorrect because it displayed the revenue for the entire month of APR-18 even if the start date was just 21-APR-2018. This issue is resolved in this release. Now, the revenue is scheduled correctly for the remaining 10 days in APR-18 in the same case.
Start Date Field Issue When Scheduling Jobs in the New RevPro UI
Previously, you might find the following issues while scheduling jobs in the new RevPro UI:
- The timestamp was not displayed in the Start Date field while scheduling a new job.
- The date populated in the Start Date field conflicts with the database date when working in different time zones. The new RevPro UI would pick up the system date in contrary to the old RevPro UI.
Now, RevPro fixes these issues. When you are scheduling a new job in the new RevPro UI, it displays the date with the timestamp in the Start Date field, and the populated date is the database date instead of the system date.
Bundle Split Caused Rounding Issue between INV and CM-C
You might encounter the issue where the bundle split caused rounding issues between INV and CM-C. This issue led to the data collection issue and the collected data went wrong for CM-C. This issue is resolved in this release and hence, the rounding issue no longer exists.
Cannot Edit Input Value Labels in Event Upload Template
In some cases, you could not edit the values in the Input Value Label column for the standard fields in an Event Upload Template. This issue is resolved in RevPro 188.8.131.52. Now, you can edit the values of the Input Label Value column in the Field Mapping tab in the Edit Event Template page when applicable.
Immediate Cost Released Ratably upon SO Update Although Release Method was Upon Booking
Previously, the cost was released ratably upon SO update although you have set the release method as upon booking and the ratable method as immediate using open period in the POB setup. Particularly, this issue happened to the Catch-Up Cost. RevPro fixes this issue in this release. The cost is released based on the setting in the POB setup now.
Adjustment Revenue Not Reflected in Accounting and Waterfall after Cost Upload
Prior to 184.108.40.206, you might encounter the issue that after you uploaded a non-standard cost, the transaction lines displayed the Carve Adjustments at the RC Workbench, but the Accounting and Waterfall were not displaying the Adjustment Revenue. This issue is resolved now. After collecting CST lines, the Allocation entries are reflected correctly in the Accounting and Waterfall.
Overstated and Understated Revenue Recognition Issues upon Full Billing
Suppose you collected several SO or INV lines with a revenue duration and the Extended Selling Price was under $1. The release event was Upon Billing and the contract ratable profile was disabled. In this case, you were likely to run into the overstated or understated issue where the revenue is released more or less than 100%. This issue is resolved in this release. The recognized amount is populated correctly.
POB Expiry Date Not Updated
Suppose you created a POB with Expiry details where the Expiry Date is based on the Ship Date. When you collected the SO with a Ship Date, the Expiry Date (
EXP_DATE) was populated the same as the Ship Date. However, when you updated the SO line to a different Ship Date,
EXP_DATE remained the same as the previous value instead of being updated based on the latest Ship Date in the
RPRO_RC_POB_G table. You could not recognize the revenue due to this issue previously. Now, this issue is resolved. The
EXP_DATE can be correctly updated in the
Event Not Processed Correctly
In the scenario where you created a POB based on an amount-based event, collected an SO and multiple invoices with the overstated amount for the same line in one batch, and set the release event to Upon Booking, when you uploaded the event data and run the event process program, the event was not processed but the overstated invoices were released by the system. This issue is fixed in this release. The revenue on the overstated invoices is released only based on the event uploaded. This behavior is only applicable to the Amount and Quantity based events.
Revenue Automatically Re-Released on Deferral
Previously, if you collected an SO line where the release event was set as Immediate Upon Start Date, the revenue for this line was automatically re-released at 100% when you were trying to defer the line. This issue is resolved in 220.127.116.11. The revenue is deferred correctly now.
Period Close Job Run into Error
You could run into the issue where the period close jobs were stuck in the Pending status after submitting jobs. The No Period Status Found for Org_ID, this job cannot be submitted error message was displayed during the period close process. It was because for each time you ran a Period Close job, you needed to click the value of the Org Id field to get the default value populated. In this release, this issue is resolved. As an alternative, the org name is automatically populated by default in the Org Id field after submitting a job.
Allocatable Amount Exists When ESP and SSP are Zero
For an RC with the Enable Contractual Prospective set to Y, if you collected SO, INV, and CM-C, and brought the SO cancellation with the Cancel Flag set as Y, when you posted this RC, moved it to the next period, and then increase the selling price of the SO, the
REC_AMT became zero, but the allocatable amount was calculated. RevPro fixes this issue in this release. In the same case, the allocatable amount, extended selling price, and recognized amount are correctly calculated.
VC Expiry Program Completes in Error When System has Invalid Data
Previously, you might run into the issue that the VC Expiry program was completed in error and it did not update the VC expiry amount. This happened because some outdated data with a VC ID existed in the VC base table. In this release, this issue is resolved. The VC Expiry program now expires VC only for valid records.