May 2015 Release Notes

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

May 2015 Release Notes

Welcome to the Zuora May 2015 Release, R188. R188.1, R188.2, R188.3, R188.4. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

Highlights by Zuora Keys

Summary of generally available features and enhancements by Zuora Keys:

  • BILL: Assign subscription invoice owner through REST API
  • COLLECT: Specify gateway used for the payment through APIs | Configure payment runs to ignore closed payment methods | IP Payments gateway supports non-referenced refunds
  • ACCOUNT: Key account balance metrics from AR aging report | Accounting rule helps stop over-recognition of revenue
  • NURTURE: Callout Notification on Stateful AQuA queries​

​Released Versions

Environment Current Product Version Release Date Current WSDL
Production R188.3 June 3, 2015 67.0
API Sandbox R188.4 June 9, 2015 67.0

See Version Information for more version information.

Zuora for Salesforce Release (Q1 2015)

Zuora for Salesforce Quotes Q1 2015 Release Notes and Zuora 360 Q4 2014 Release Notes (note that Zuora 360 release remains Q4 2014)

Z-Suite Integrations Release

Z-Suite Integrations Release Notes
Release May 27, 2015, v329

Features and Enhancements


Assign a Subscription Invoice Owner when Creating Subscriptions Using REST API

You can now assign a subscription invoice owner when creating subscriptions. You can also get information about your subscriptions using an invoice owner account key.

Assign a subscription invoice owner when you create subscriptions with an invoice owner account key. Use the following Zuora REST API resources:

Use an invoice owner account key to get detailed information about subscriptions. Use the following Zuora REST API resources:

Flexible Subscriptions with Base Prices and Full Term Pricing

Two new enhancements give you more flexibility when offering subscriptions to your customers:

  • List Price Base. Define list price of a recurring charge based on a month or on a billing period. This monthly base price can be multiplied by the number of months in your billing period.
  • Subscription Term as the Billing Period. Define the billing period as a subscription term. For subscriptions with variable term lengths, you can bill and collect payments up front for the entire term. On renewal, you can bill and collect payment up front for the renewal term too. This ability applies to any term length.

These enhancements are supported through the Zuora application, REST API resources, and SOAP API calls.

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

See the following for more information:


OAuth Credentials for Authenticating into Salesforce Using Connected Apps

Zuora offers an OAuth option for authenticating into Salesforce through Salesforce Connected Apps. Previously, you could only authenticate into Salesforce with Salesforce login credentials and a security token.

The OAuth option gives you a more secure method for connecting to Salesforce:

  • Tokens only are used instead of a Salesforce login or password that is stored in Zuora

  • Salesforce integrations can be controlled centrally from Salesforce, instead of from Zuora, the sending application

Salesforce Connected Apps is deployed with Zuora 360 and requires the installed Zuora 360 Package, version 2.102 or higher. Salesforce Connected Apps is not deployed with Zuora Quotes. If OAuth authentication is used in Zuora Quotes, the Zuora 360 Package, version 2.102 and higher, must be installed on the same Salesforce Org as Zuora Quotes.

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

See Set up Credentials to Connect to Salesforce for more information on how to use OAuth credentials to connect to Salesforce.

Lifespan of Orphan Payment Methods Extended from 120 Hours to 240 Hours

Zuora will delete orphan payments that are not tied to a Zuora account after 240 hours.

See Link Payment Methods from Hosted Payment Method Pages to Accounts for more information.


Key AR Aging Account Balances at a Glance

In the Zuora March Release, R186, we introduced a new AR Account Aging report that lets you see the Invoice Balance, Credit Balance, and Account Balance for each of your customers. You can now view totals for these key account balances directly from the Zuora application – making AR reconciliation easier than ever.

See Accounts Receivable Aging Summary for more information.

More Control Over How You Recognize Revenue

We have introduced the following accounting rule that helps you prevent the over-recognition of revenue:

Allow a Revenue Schedule to have negative amount in Open-Ended Accounting Period

By default, this rule is set to Yes. To prevent the over-recognition of revenue, navigate to Z-Finance Settings > Configure Accounting Rules and change this rule to No.

See Configure Accounting Rules for more information.


Changes in Closed Payment Methods

Zuora is changing the way closed payment are handled. You can now configure your payment run to ignore closed payment methods.

Litle Gateway Name Change    

The Litle gateway name has been changed to Vantiv gateway.

See Vantiv Payment Gateway for more information.

IP Payments Gateway Support for Non-referenced Refund

The IP Payments gateway now supports non-referenced refunds.

See IP Payments Gateway for more information.

New Gateway Field for Payment SOAP API and Invoice and Collect REST API

We have added a new gateway field to the following APIs that enables you to specify the gateway used for the payment:

  • Payment SOAP API: Gateway field
  • Invoice and Collect REST API: paymentGateway field

See Invoice and collect and Payment for more information.

Zuora APIs


Callout Notification Support for AQuA Stateful Queries

You can configure a callout notification to be sent after a stateful AQuA job is complete, using the Zuora notification framework. This feature is in Settings > Z-Billing Settings > Setup Profiles, Notifications, and Email Templates.

See Callout Notification for Completed AQuA Jobs for more information.


For Release 188, the WSDL version is 67.0. See Zuora WSDL for information about downloading the current version.​

Knowledge Center

Customer-requested Improvements to Articles

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

  • Amendment object:
    • Corrected fields descriptions for Amendment.DestinationAccountId and Amendment.DestinationInvoiceOwnerId. These fields do no support query.
    • Clarified Status field values regarding Active versus Completed.
  • Send Custom Fields to Z-Billing. Updated incorrect references in the Quote Type Options column for:
    • Quote object, removed Amendment Renewals and Cancelations
    • Account object, removed N/A and added New Subscriptions
  • File Segmentation. Added note that file segmentation is only supported in stateful mode and only for the initial load.

These customer-requested improvements were made real-time and are not release specific. This list of updated articles represent changes since the last release.

Maintenance Release 188.1

This maintenance release include internal fixes.

  • Production release, May 18, 2015
  • API Sandbox release, May 17, 2015

Maintenance Release 188.2

This maintenance release includes the following features, enhancements, resolved issues, and internal fixes.

  • Production release, May 27, 2015
  • API Sandbox release, May 26, 2015

Features and Enhancements


New Confirmation Dialog Option for Payment Pages 2.0 – Required for SEPA Compliance

We've added a Confirmation Dialog option to the Commerce Payment Pages 2.0 workflow. This option is turned on by default for the SEPA Bank Transfer payment method. When your customers select to pay with SEPA Direct Debit as a payment type, they must confirm the mandate information on this Confirmation Dialog page before payments can be processed.

Key features include:

  • All you need to capture SEPA information in a compliant manner. The required display information includes Creditor Identifier and the customer's IBAN.
  • Look and feel is customizable. You control the styling and placement of content within the dialog.
  • Content can be localized into any language, include legal terms, labels, and dates.

As always, Payment Pages 2.0 is available in Salesforce through Zuora for Salesforce and is mobile-compatible.

See Configure SEPA Type Payment Pages 2.0 for configuring your SEPA Payment Page with the Confirmation Dialog.

New Advanced Digital Signature for Payment Pages 2.0

If your business requires additional security to protect sensitive information, now you have the option to use the advanced digital signature in the callback response for Payment Pages 2.0. The advanced signature provides the following functionality in addition to what the basic signature offers:

  • Encrypts the payment method ID returned from Zuora.
  • Allows you to validate additional information in the signature.

See Validate the Digital Signature for Payment Pages 2.0 for information about the digital signatures in Payment Pages 2.0.

Resolved Issue


Time Component Not Present in the DateTime Field 

The time component in the DateTime field was not displaying in the AQuA generated CSV file. Both the date and time are now displayed in AQuA generated CSV files.  This issue was resolved on AQuA API version 1.2.

Maintenance Release 188.3

This maintenance release include internal fixes.

  • Production release, June 3, 2015
  • API Sandbox release, June 3, 2015

Maintenance Release 188.3

This maintenance release include internal fixes.

  • API Sandbox release, June 9, 2015
Last modified


This page has no custom tags.


(not set)