September 2015 Release Notes

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2015 New Features > September 2015 Release Notes

September 2015 Release Notes

Welcome to the Zuora September 2015 Release, R192. This release includes new Zuora features, enhancements, and improvements to the Knowledge Center.

Released Versions

Environment Current Product Version Release Date Current WSDL
Production R192.3 September 30, 2015 70.0
API Sandbox R192.3 September 30, 2015 70.0

See Version Information for more version information.

GA Highlights by Zuora Keys

  • PRICE: New Payment Term Options | Price Change on Renewals | Rate Plan Charge Effective Dates Available through REST API
  • BILL: Option to Auto-Post Invoices After Bill Runs Complete is GA
  • COLLECT: Payment Method Updater is GA
  • ACCOUNT: Accounting Code Objects Available in All Transaction Data Sources | Define Segments Using Transaction Objects | Configure Segmentation for Individual Transaction Types | Easily Make Changes to Your GL Segmentation Rule
  • NURTURE: New Date Type on Custom Fields | Custom Field Support on Amendments | New Notifications Based on Various Subscription Dates | Formatting for Japanese User Locale

Z-Suite Integrations Release

Z-Suite Integrations Release Notes v482, Release September 24, 2015

Features and Enhancements

Billing and Subscription​

Billing in Arrears

This feature is in Limited Availability. If you want to have access to the feature, submit a request at Zuora Global Support

Another step in billing flexibility. You can now bill subscribers in arrears—that is, bill subscribers for services that have already been rendered. You may want to bill in arrears for a few reasons:

  • Drive product adoption. Start using the product for free today. Pay for it later.
  • European businesses commonly charge customers in arrears.
  • Combine recurring and usage fees from a service period on a single invoice.

You can choose Billing in Arrears options for Billing Timing on a charge. Available from the Zuora UI, SOAP API, and REST API. Billing Timing options are also available as a data source export.

See Billing Timing for more information.

New Payment Terms

To provide more flexibility in defining payment terms, Zuora offers two payment term solutions:

  • Net Payment Term. This solution is the fixed payment term that was available before this release. The payment interval before the due date is a fixed number of days that you determine. The default payment term is Due Upon Receipt, which means the due date is the day the invoice is received.
  • Prox Payment Term. This solution lets you define the day of the month for the invoice to be sent, the payment interval before the due date (in months), and the day of the month on which the due date occurs.

For more information, see Define Payment Terms.

Custom Fields Supported on the Amendment Object

The Amendment object supports custom fields on the Zuora UI and SOAP API. You can define custom fields on the Amendment object from Settings > Z-Billing Settings.

See the following articles for more information:

New Notification for Subscription Dates

Z-Billing Subscription notification has a new event called Key Date(s). You can now configure notifications to be sent out on a per subscription basis for specific subscription dates. When the subscription date arrives, the notification is sent.

The subscription dates for which you can configure notifications include:

  • Contract effective date
  • Service activation date
  • Customer acceptance date
  • Term start date
  • Term end date
  • Subscription start date
  • Subscription end date

This feature is available for email and callout notifications. You can create multiple notifications, each with a different event trigger date in the same profile. You can configure the same notification across different communication profiles.

Navigation: Settings > Z-Billing Settings > Setup Profiles, Notifications and Email Templates. Define a Z-Billing notification and click add new notification. Select Key Date(s) as the event category and select one of the new subscription date parameters.

See the following articles for more information:

Price Change Options on Subscription Renewal

Price change options for percentage discount charges are now available when you renew a subscription. You can change the price you charge your customers when they renew their subscriptions.

See Define Default Subscription Settings for more information.

Rate Plan Charge Information Available on REST Get Subscription

Zuora now returns information on rate plan charge effective dates as part of get subscription calls in the REST API. Now it is possible for you to see when rate plan charges will be in effect.

Plus we support for more fields on Get Subscription requests:




See the following more information on these fields:

Billing Rule to Auto-Post Invoices After Bill Runs Complete is GA

You can set options to auto-post invoices when bill runs complete. You can also choose to auto-email invoices as part of the automated bill run workflow.

Navigate to Settings > Z-Billing Settings > Billing Rules. The following billing rule options are now available to everyone:

  • Support Bill Run to Auto-Post? Choose Yes to enable the Auto Post Invoices Upon Completion of Bill Run option and Email Invoices after Auto-Post is Complete option when creating a bill run from the Zuora UI.
  • Default Bill Run to Auto-Post? This rule option is displayed only after choosing Yes on Support Bill Run to Auto-Post? Choose Yes to set the Bill Run to Auto-Post by default when creating a bill run.

See the following for more information:

Three Enhancements for Avalara Integrations

This feature is in Limited Availability. If you want to have access to the feature, submit a request at Zuora Global Support

Multiple Origin Addresses in Avalara

Zuora now supports multiple origin address and company codes for tenants with Avalara enabled. Taxes can be calculated based on origin and sold-to addresses in Avalara. With multiple origin addresses and company codes, you can establish relationships between origin and sold-to addresses for your tax calculations.

See Configure Your Tenant Profile and Permissions for more information.

VAT ID Passed to Avalara

Tenants with Avalara enabled can now pass their Value Added Tax ID to Avalara. You can use Avalara to calculate taxes according to European Union tax rules.

See Create a Customer Account for more information.

TaxCompanyCode Field

The TaxCompanyCode field is available in the SOAP API Account object. Use this field to calculate taxes based on origin and sold-to addresses in Avalara.

See the SOAP API Account object reference for more information.


New Quotes File Generation Service Required for New Quote Templates

Starting in this release, you will no longer have the option to choose the old quote file generation service when creating a new quote template. By default, the new service will be used for new templates.

Any existing templates will continue to use the old service until the December 2015 release in which all existing quote templates will be migrated to use the new service.

If you have a special circumstance that requires you to use the old service with new templates, submit a request at Zuora Global Support.

See Quote Template Settings for customizing and uploading a quote template.

Support Date Type Custom Fields in Product Catalog and 360 Sync

Now the Date type custom fields are supported in Zuora. You can use the Manual or Real-time sync to update the Date type custom fields in Zuora CPQ with the value set in Zuora.

See Date Type Custom Fields for the Date type custom fields support in Zuora.

See Synchronize Zuora Custom Fields for creating and synchronizing custom fields from Zuora to Zuora 360.

Payment Pages 2.0 Generally Available in Zuora Quotes

With the General Availability of Payment Pages 2.0 in Zuora, now Payment Pages 2.0 Settings in Zuora Config is available to all orgs in Zuora Quotes.

See Payment Pages 2.0 Settings for setting up and using Payment Pages in Zuora Quotes.


Accounting Code Objects Available in All Transaction Data Sources

All transaction data sources now include accounting code objects. In this release we have added accounting code objects to the following data sources:

Available to all Z-Finance users.

Define Segments Using Transaction Objects

Previously you could only configure segments using fields on customer-related objects, such as Account, and product-related objects, such as Product Rate Plan. Now you can also configure segments using fields on transaction-related objects, such as Invoice Item and Payment. This new feature is useful when segmentation information is stored at the transaction level.

Available to all Z-Finance users.

See Fields Supported by Segments for a full list of supported fields.

Configure Segmentation for Individual Transaction Types

Now you can specify how you want to segment individual transaction types in your GL segmentation rule. For example, you might want to segment all transactions by Subsidiary, and further segment Payment transactions by their Payment Method Type.

When configuring a GL segmentation rule, select the Advanced: override default rule for specific transaction types checkbox, select a transaction type, and then configure segments specifically for that transaction type.

Available to all Z-Finance users.

See GL Segmentation Rules for more information about configuring segmentation for individual transaction types.

Making Changes to Your GL Segmentation Rule is Easy

Previously if you wanted to make changes to your GL segmentation rule, you first had to delete all journal runs and summary journal entries that used the rule. Now you can simply deactivate the rule and then create and activate a new rule. Only one rule can be active at a time, and the active rule is used automatically when you perform journal runs.

Available to all Z-Finance users.

See GL Segmentation Rules for more information about making changes to your GL segmentation rule.


Payment Method Updater Availability

Before this release, the Payment Method Updater was in controlled release, but now this service is available for any Zuora customers who have signed up with CyberSource Account Updater, Vantiv, or WorldPay Account Updater Service. This service enables merchants to automatically incorporate changes made to a customer's Visa or MasterCard data, including expiration date, new card number, account closure, and brand migration.

See Payment Method Updater for more information.


Date Type Custom Fields

We now support the Date type of custom fields in Zuora and Zuora CPQ. You can create custom fields of the Date type, validate dates, or filter using date comparisons on custom fields.

After you configure a Date custom field, the Date field will appear in the Zuora UI with a date picker, in the APIs with the "yyyy-mm-dd" format, and in data sources as fields and filters.

See the following articles for creating new custom fields in Zuora:

Japanese User Locale Formats

The following locale formats apply to the Zuora UI when the user locale is set to Japanese:

  • Display Name fields on the Zuora UI as Last Name, First Name
  • Display Address fields on the Zuora UI as Country, Postal Code, State/Province, City, Address1, Address2

See Manage User Profile for more information.

Zuora APIs


Please read this important note before using WSDL version 69 or later. The current WSDL is version 70.

In WSDL 68 and earlier, 56 Zuora SOAP API date fields are treated as dateTime fields. As of WSDL 69, Zuora will treat these fields as date only fields. These fields are no longer compatible with dateTime values. Date and dateTime values in WSDL 69 are now the same as date and dateTime values in the Zuora application.

Before downloading and using WSDL 69, check to see if your SOAP integration passes or receives dateTime values to or from any of these fields.

The AQuA API is also affected by these date field changes. If you use the AQuA API, you must review the date field changes and take the appropriate action.

See Date Field Changes in the WSDL for more information.

Export ZOQL

Date and time functions support targeted simplification of timestamp date/time fields and values. Export ZOQL now supports: DATE(), YEAR(), MONTH(), WEEK(), and QUARTER() to interpret any date/time (timestamp) field or value into the desired functional element.

See Export ZOQL Date and Datetime for more information.

Knowledge Center

Customer-requested Improvements to Articles

We have updated the following Knowledge Center articles based on customer-reported feedback:

  • ProductRatePlanCharge (SOAP Object): Updated the RecognizedRevenueAccount description to indicate when this field is required on create:
    • Required when the Allow Blank Accounting Code setting is No.
    • Optional when the Allow Blank Accounting Code setting is Yes.
  • How do I trouble shoot callouts configured for authentication? Updated this article with clearer instructions on how to validate the user name and password using curl commands.
  • API Object Relationships: Added Refund objects to the relationship diagram.
  • Catalog (REST API): Clarified the PricingSummary field description and updated JSON response examples.
  • Previewing a subscription: The ProductRatePlanChargeID is not a valid response for previewing a subscription through the SOAP call. Corrected the response code sample by removing the line:
  • AmendOption (SOAP API Complex Object): Clarified rules on the ProcessPayments field when AutoPay is set to .

Maintenance Release 192.3

This release includes internal fixes.

  • API Sandbox release, September 30, 2015
  • Production release, September 30, 2015

Maintenance Release 192.2

This release includes internal fixes.

  • API Sandbox release, September 29, 2015
  • Production release, September 29, 2015

Maintenance Release 192.1

This release includes internal fixes.

  • API Sandbox release, September 22, 2015
  • Production release, September 23, 2015
Last modified



(not set)