November 2013 - New Features

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2013 New Features > November 2013 - New Features

November 2013 - New Features


Welcome to the Zuora November 2013 Release (R170, R170.1, 170.2, 170.3). This release includes new features, enhancements, and resolved issues.

Released Versions

Environment Current product version Release date Current WSDL
Production 170.3 December 4, 2013 52.0
API Sandbox 170.3 December 3, 2013 52.0

See Version Information for more version information.

Zuora Highlights

Extended field length on Customer Name:  We now allow up to 255 characters on the customer name for tighter match-up's between Zuora and Zuora for Salesforce.
New invoice views:  We've given you the option of displaying charges on invoices either at the rate plan or subscription level.
New Deferred Revenue option on Z-Finance rule: You can now select another Deferred Revenue accounting code on the Recognize upon invoicing revenue rule.
REST API continues to grow: We keep 'em coming – this release we've added new response parameters for rate plans and rate plan charges on various REST API calls. 
SOAP APIs: Now you can override Revenue Recognition Triggers and Revenue Revenue Codes through SOAP APIs on active subscriptions or when a product is in draft. 

Zuora for Salesforce Titanium Release (Q4 2013) Highlights

Z-Force rebranded to Zuora for SalesforceZ-Force has a new name – Zuora for Salesforce. Same great product – with a new name.  
Re-architected with new reusable components: Leverage our new reusable components in order to build and configure pages quicker than ever before. We've developed reusable components so that you can take our out-of-the-box functionalities and quickly tailor them to meet your business needs.   
New configurable Quote Wizard: Our new admin-friendly Quote Wizard lets you easily implement a quoting flow that works for you.  By leveraging's point-and-click user interface, admins can quickly add pages, re-order them, show progress bars, and label buttons directly through the UI. Wizardry without the spells, gimmicks, and no developer code.  
New configurable product selector: Our new Product Selector provides a fast and easy way to add or modify product rate plan charges while creating or editing a quote. It supports inline editing and filtering, custom tiered pricing, and flexible discount management.  
Extended and improved custom field support: You can add and configure custom fields at the quote-level and charge-level to display on the pages in quote processing flow or to sync to Z-Billing.   
New quote metrics: We have new subscription metrics and now they are calculated in real-time!  These metrics are configurable too – you can choose whether the metrics are calculated for a specified number of billing periods or through the end of a subscription term.   

See Zuora for Salesforce Quotes Q4 2013 Release Notes and Zuora 360 Q4 2013 Release Notes for details.

New Zuora Features and Enhancements


Longer names allowed for customer Account objects

The maximum length of the Name field of the customer Account object has been increased from 50 to 255 characters allowing you to enter longer customer names. This enhancement not only provides greater naming flexibility, but also provides greater compatibility with Zuora CPQ.

This enhancement applies to all areas of the Zuora application that require the customer's account name to be specified. Examples include the add new account on the Customer Accounts page, and creating an Account through SOAP or REST APIs.

New billing setting to allow the proration of a partial period

This feature is in controlled release. Contact Zuora Global Support to learn more about enabling it for your tenant.  

We have introduced a new Z-Billing setting Prorate recurring charges for partial period that works in a similar way to the existing Prorate recurring charges for partial month setting.

To illustrate the difference between the two settings, suppose one of your customers subscribes to a quarterly plan on January 1st and then cancels on January 15th:

  1. With only Prorate recurring charges for partial month set to No, proration would not occur for the remainder of January, but would still occur for the months of February and March.
  2. With the new setting Prorate recurring charges for partial period set to No, proration would not occur for the entire quarterly period, which includes February and March.

Disabling Prorate recurring charges for partial period is useful in a variety of situations, for instance when selling physical goods that are dispatched at the start of a billing period.

If this feature is enabled for your tenant, go to Settings > Z-Billing Settings > Billing Rules to set this new option. 

See Define Billing Rules for more information.

Enhanced subscription summarization on invoices

Until now, it was only possible to generate invoices that displayed charges at the individual charge level. With this release you have the additional option to display charges at either the rate plan or subscription level, summing individual charges up to the subscription or rate plan level on the invoice. Each charge is still held separately in the system however, so using this new feature in your invoice templates does not affect any revenue recognition processes.

To implement either of these new views in your invoices you must modify your current invoice template.

See Configuring the Subscription or Rate Plan Summary Table for information on how to modify your template.

Instructions and a sample template are also available from Zuora. Navigate to Settings > Z-Billing Settings > Manage Invoice Rules and Templates.


New Payment Method Updater Interface for users enrolled in Litle & Co. Updater 

This feature is in controlled release. Contact Zuora Global Support to learn more about enabling it for your tenant.  

Merchants using the Litle & Co. Updater for the Zuora Payment Method Updater now have their username and password loaded automatically from their Litle & Co. Payment Gateway system configuration. Now only the name and merchant ID will need to be inputted when configuring the Litle & Co. Updater. The benefit of this change is enhanced security and improved usability. 

See Configure the Litle & Co. Updater for more information.


New option to select another accounting code for deferred revenue 

For Z-Finance, we've changed the user experience for selecting accounting codes on the Recognize upon invoicing revenue rule.

In previous releases, when selecting Recognize upon invoicing as a revenue rule, you could only select an accounting code for Recognized Revenue. Deferred Revenue was not displayed, but set by default to the same accounting code as Recognized Revenue.

With this release, you can now manage all revenue through the same deferral process. When selecting Recognize upon invoicing as a revenue rule, you can select another accounting code for Deferred Revenue. The new Advanced: define a different Deferred Revenue accounting code check box gives you the option to display Deferred Revenue and select another accounting code. If you clear this check box, the Deferred Revenue defaults back to the accounting code selected on Recognized Revenue.

The Recognize daily over time revenue rule remains unchanged.

The SOAP API request remains unchanged when specifying an accounting code (AccountingCodeRecognizedRevenueAccount, or DeferredRevenueAccount) through the create() or update() calls on the ProductRatePlanCharge object. We've improved the exception handling to display an error message when the DeferredRevenueAccount does not match the AccountingCode.

See Assign Accounting Codes for more information this enhancement to the user interface and see ProductRatePlanCharge for more usage information on the SOAP API accounting code fields.


Z-Force branding changes in the Zuora user Interface

Z-Force has a new name – Zuora for Salesforce. As a result, we updated the Zuora user interface and navigation to maintain continuity between these two solutions.

Look for the following changes in the Zuora user interface:

Where? Was Now Is
Top Settings Menu Settings > Z-Force Settings Settings > Z-Commerce Settings
Left Navigation Menu Z-Force  Z-Commerce
Left Navigation Menu Z-Force > Data Synchronization Z-Commerce > 360 Sync
Left Navigation Z-Checkout

Z-Commerce > Checkout

Note New Location: Checkout has moved under Z-Commerce

Left Navigation > Data Synchronization Sync Zuora for Salesforce - 360 Sync

Zuora APIs


WSDL Version

For Release 170, the WSDL version is 52.0. See The Zuora WSDL for information about downloading the current version.

SOAP API can now override Revenue Recognition Code & Revenue Recognition Trigger in subscriptions

Previously, it was not possible to change the Revenue Recognition Trigger or Revenue Recognition Code of a product in a draft or active subscription via the SOAP API. With this new release, it is now possible to override these values when:

  • Creating a new draft subscription with a subscribe() call
  • Updating a draft subscription with a RatePlanCharge update() call
  • Updating active subscriptions with amend() call via either an Update or New Product Amendment.

This enhancement makes it easy to update many thousands of existing active subscriptions e.g. to make all existing subscriptions compatible with an external Revenue Recognition engine.

The two new optional fields have been exposed in the SOAP object RatePlanCharge, and are defined as follows:

RevRecCode: Takes a valid revenue recognition code

RevRecTriggerCondition: Takes one of the following values:

  • ContractEffectiveDate
  • ServiceActivationDate
  • CustomerAcceptanceDate

You must be on WSDL version 52.0 or higher to use this SOAP feature. See The Zuora WSDL for information about downloading the current version.


New Rate Plans and RatePlanCharges response parameters extend REST APIs

To make it easier to reference related objects when handling responses from our REST APIs, we've added a number of additional response parameters. The new parameters are shown in bold:

REST API New Response Parameters

GET account summary

RatePlans container has new response parameters:

  • Subscriptions container
    • RatePlans​​ container ​(within the Subscriptions container)
      • productId
      • productRatepPlanId
GET subscription by key RatePlans container and RatePlanCharges container have new response parameters:
  • RatePlans ​container
    • productId
    • productRatePlanId
    • RatePlanCharges container (within the RatePlan container)
      • productRatePlanChargeId
GET subscriptions by account

Subscriptions > RatePlans container and RatePlanCharges container have new response parameters:

  • Subscriptions container
    • RatePlans​​ container ​(within the Subscriptions container)
      • productId
      • productRatepPlanId
      • RatePlanCharges container (within the RatePlan container)
        • productRatePlanChargeId
GET catalog products

Products container has a new response parameter:

  • Products container
    • Id

Enhanced support for dates in REST calls that create subscriptions

It is now possible to set and retrieve values for termStartDate, serviceActivationDate (SA) and customerAcceptanceDate (CA) when creating subscriptions through REST API calls. This enhanced functionality makes it easier to implement more flexible subscription options, such as offering free trials.

The following REST APIs have new request parameters:

REST API Required? New Parameters

POST create account


  • Subscription container
    • termStartDate
    • serviceActivationDate
    • customerAcceptanceDate
POST create subscription


  • termStartDate
  • serviceActivationDate
  • customerAcceptanceDate
POST preview subscription


  • termStartDate
  • serviceActivationDate
  • customerAcceptanceDate

If one or more of these request parameters are not specified, then default values are set using the values in other fields, including the Contract Effective date (CE). 

  serviceActivationDate (SA) specified serviceActivationDate (SA) NOT specified

customerAcceptanceDate (CA)


SA uses value in the request call

CA uses value in the request call

CA uses value in the request call

SA uses CE as default

customerAcceptanceDate (CA)

NOT specified

SA uses value in the request call

CA uses SA as default

SA and CA use CE as default

The following REST APIs have had new fields added to their response, which are always returned:

REST API New Fields
GET subscriptions by account
  • Subscriptions container
    • serviceActivationDate
    • customerAcceptanceDate

Note: termStartDate is also always returned

GET subscriptions by key
  • serviceActivationDate
  • customerAcceptanceDate

Note: termStartDate is also always returned

Added more JSON response field codes for improved support on REST API objects

We've added more response field codes on several REST API object fields. Some of these fields are new with this release and have been assigned a code, while other fields already existed but didn't have an associated code, which this release has rectified. The following table lists the new field codes for each object: 

Code Request Resource Field
10016 POST v1/accounts invoiceCollect
10017 POST v1/accounts invoiceTargetDate
10018 POST v1/accounts autoPay
10408 POST v1/accounts subscription.serviceActivationDate
10409 POST v1/accounts subscription.customerAcceptanceDate
10410 POST v1/accounts subscription.termStartDate
10411 POST v1/accounts subscription.customFieldsData
15009 PUT v1/accounts/{account-key} autoPay
30011 POST v1/subscriptions serviceActivationDate
30012 POST v1/subscriptions customerAcceptanceDate
30013 POST v1/subscriptions termStartDate
30014 POST v1/subscriptions customFieldsData
31008 POST v1/subscriptions/preview serviceActivationDate
31009 POST v1/subscriptions/preview customerAcceptanceDate
31010 POST v1/subscriptions/preview termStartDate
35012 PUT v1/subscriptions/{subscription-key} customFieldsData

See Responses and Errors page for more information.

Zuora Knowledge Center

The following improvements were made to Knowledge Center articles for this release:

Maintenance Release R170.1

This maintenance release includes internal fixes.

  • Production release, November 15, 2013
  • API Sandbox release, November 15, 2013

Maintenance Release R170.2

This maintenance release includes internal fixes.

  • Production release, November 27, 2013
  • API Sandbox release, November 26, 2013

Maintenance Release R170.3

This maintenance release includes internal fixes.

  • Production release, December 4, 2013
  • API Sandbox release, December 3, 2013
Last modified


This page has no custom tags.


(not set)