Knowledge Center

Knowledge Center > What's New > Previous Zuora Releases > 2016 New Features > January 2016 Release Notes

January 2016 Release Notes

Welcome to the Zuora January 2016 Release, R196. This release includes new Zuora features, enhancements, resolved issues, and improvements to the Knowledge Center.

Released Versions

Environment Current Product Version Release Date Current WSDL
Production R196.2 February 4, 2016 74.0
API Sandbox R196.2 February 2, 2016 74.0

See Version Information for more version information.​

Zuora Community Launch

The Zuora Community is here. We are excited to announce our peer-to-peer support environment where you can go to have your questions answered with the help of others. This is the space where our customers and partners can learn, share, and collaborate.

Sign up now and start sharing your unique thoughts, solutions, and ideas with others.

Check out our helpful Community FAQ for more details.

Zuora's RBM Solution

Features and enhancements related to Relationship Business Management solutions.

Subscription​ Management

R196.2 Calculate a Price for Each Usage Record in All Supported Rating Groups

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

This is an enhancement on Giving a Price to Each Usage Record. In the Zuora January 2015 Release, R196, we added the ability to calculate a price for each usage record. This feature was only used to calculate charges based on Rating Group by Billing Period. Now a price can be calculated for each usage record in all supported rating group options. Zuora can calculate charges based on a rating group after calculating charges for each usage record.

To access this feature, navigate to Settings > Z-Billing Settings > Billing Rules, set the Round and determine a price for usage records individually when rating usage charges? billing rule to Yes.

New REST Method Request Fields for Subscription Invoices

The REST subscription methods were updated to include new request fields that provide more flexibility in managing invoices when subscriptions are created or updated. You can now use REST methods to complete the following invoice tasks:

  • Apply a credit balance to an invoice
  • Invoice a subscription separately from other subscriptions
  • Create an invoice independently of automatic payment collection
  • Collect automatic payments

Two of the new fields, invoice and collect, replace the field invoiceCollect which is now available only for backward compatibility.

The invoiceCollect, invoice, and collect fields are in Zuora REST API version control. To use the invoice and collect fields in the REST methods, you must set the zuora-version parameter to 196.0 in the request header. See Zuora REST API Versions for more information.

The following table lists the new request fields.

Request Fields REST Methods Description
applyCreditBalance Create Subscription
Update Subscription
Renew Subscription
Cancel Subscription
Create Account
Applies a credit balance to an invoice.
invoiceSeparately Create Subscription
Update Subscription
Create Account
Get Subscriptions by Key
Get Subscriptions by Account
Preview Subscriptions

Separates a single subscription charge from other subscription charges and invoices the charge separately.

invoice Create Subscription
Update Subscription
Renew Subscription
Cancel Subscription
Create Account

Generates an invoice for a subscription.

 

collect Create Subscription
Update Subscription
Renew Subscription
Cancel Subscription
Create Account
Collects an automatic payment for a subscription. 

Update Subscription REST Method Now Supports More Pricing-related Fields

Before this release, you could only override the chargeOverrides quantity field in the Update Subscription method. Now you can override more fields related to pricing when making a PUT Subscription call to add or update products in a subscription.

See Update subscription for a list of updateable fields added to chargeOverrides and chargeUpdateDetails for the Update Subscription method.

Subscription Term as a Billing Period and List Price Based on a Month Are Now GA

Subscription Term as a billing period and List Price based on a month are now generally available. 

  • Subscription Term: Sets up a recurring charge using the subscription term as the billing period.
  • List Price: Sets up a list price on a product rate plan charge based on a month or a billing period.

See Recurring Charge for Different Initial and Renewal Terms for more information on using these new options.

New Subscription Creation Notifications

Before this release, we provided a notification callout that triggers when a new subscription is made active. With this release, we are adding two options to trigger a notification for a new subscription that is created but is not yet active. We are supporting notifications for subscriptions in Pending Activation and Pending Acceptance status. These new options are available to all customers.

See Supported Event Types for more information.

Create Remove Product Amendments before Future-dated Removals

You can now create a Remove Product amendment even if there is already a future-dated Remove Product amendment on the subscription. You no longer need to revert the future-dated amendment before creating your new amendment. Currently available only through the Zuora SOAP API and REST API.

See Remove a Product on Subscription with Future-dated Removes for more information.

Price Change Options for Renewed Subscriptions Available from Data Source

PriceChangeOption and PriceIncreasePercentage fields are now available from the Product Rate Plan Charge object for all related data sources. These two fields record the automatic price change when a subscription is renewed.

Weekly Billing

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

New Options to Bill Subscribers Weekly

Now you can bill subscribers weekly or every few weeks in addition to the currently available billing periods, such as monthly increments, quarterly, annually, and so on.

To bill weekly, define the following options:

  • Billing Period. Bill the charges weekly or every few weeks.
  • Billing Day. A specific day of the week that your billing period starts.
  • List Price Base. List price of a recurring charge based on a week.

Weekly billing options are available from the Zuora UI, SOAP API, REST API, and data sources.

In the SOAP API, REST API, and data sources, the WeeklyBillCycleDay field is newly added to specify which day of the week your billing period starts.

Field REST API SOAP API Data Source

WeeklyBillCycleDay 

Create subscription
Preview subscription

ProductRatePlanCharge
RatePlanCharge

Rate Plan Charge
Product Rate Plan Charge

To set weekly billing options, new values are added to the existing fields on REST API methods and SOAP API objects.

Field REST API SOAP API

BillCycleType

Create subscription
Preview subscription

ProductRatePlanCharge
RatePlanCharge

BillingPeriod

Get Catalog
Get subscriptions by account
Get subscriptions by key
Create subscription
Preview subscription

ProductRatePlanCharge
RatePlanCharge

ListPriceBase

Get Catalog
Get subscriptions by account
Get subscriptions by key
Create subscription
Preview subscription

ProductRatePlanCharge
RatePlanCharge

billingDay

Get Catalog
Get subscriptions by account
Get subscriptions by key

 

Before using this feature in the Zuora UI and APIs, you must enable it in Settings > Z-Billing Settings > Define Billing Periods. New options are available in the following sections:

New Billing Settings for Prorating a Partial Week

You can prorate recurring or usage charges for partial weeks through the Zuora UI. Navigate to Settings > Z-Billing Settings > Billing Rules. The following billing rules are now available:

  • Prorate recurring charges for partial week (with weekly based billing periods)? Choose whether to bill recurring charges for any periods less than a week.
  • Prorate usage charges for partial week (with weekly based billing periods)? Choose whether to bill all usage charges that occur within a prorated week.

See Define Billing Rules for more information.

Flexible Usage Rating

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

Previously you could only rate usage records based on billing periods. You could not rate usage records in groups. Now you can group usage records by a rating group option within a billing period. Zuora calculates the charge amount for each rating group. The total amount billed in a billing period is the sum of the rated amounts of all the groups. 
Zuora provides the following rating group options:

  • By Billing Period. The rating is based on all the usages in a billing period.
  • By Usage Start Date. The rating is based on all the usages on the same usage start date.
  • By Usage Record. The rating is based on each usage record.
  • By Usage Upload. The rating is based on all the usages in an uploaded usage file (.xls or .csv).

You can only specify a rating group option with the per unit, volume pricing, or tiered pricing charge models. For other charge models, usages are rated based on billing period by default. For detailed information, see Usage Rating by Group.

In the Zuora UI, select a rating group option from the Rate Group list when you perform the following operations:

  • Create or edit a product rate plan charge
  • Create a new subscription or edit a subscription in Draft status
  • Create an Add Product amendment

See Create Product Rate Plan Charges for more information.

In the SOAP API and REST API, the RatingGroup field is newly added to support this feature.

Field REST API SOAP API Data Source

RatingGroup

Get subscriptions by account
Get subscriptions by key
Create subscription
Preview subscription
Update subscription
Get Catalog

ProductRatePlanCharge
RatePlanCharge

Rate Plan Charge
Product Rate Plan Charge

Giving a Price to Each Usage Record 

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

Previously Zuora could only give you a price for usage records based on each charge ID. Now Zuora can give you a price for each usage record by setting the Round and determine a price for usage records individually when rating usage charges? billing rule to Yes. The rounding rule is also applied for each usage record.

You can view the rated amount for each usage record using the Processed Usage data source, which is newly-added in this release. The rated amount for each usage record is also displayed on the invoice PDFs. Currently this enhancement is only supported for the per unit, volume pricing, and tiered pricing charge models when the usage rating is based on a billing period.

To access this feature, navigate to Settings > Z-Billing Settings > Billing Rules. The Rate usage records individually when calculating usage charges? billing rule is renamed to Round and determine a price for usage records individually when rating usage charges?

See Define Billing Rules for more information.

Billing and Payments

Display More Taxation Information on Invoices

You can use the following new merge fields to display additional taxation information on invoices:

  • Account.CompanyCode — Unique code that identifies a company account in Avalara
  • Account.VATID — Customer’s Value Added Tax (VAT) ID
  • Account.TaxExemptEffectiveDate — Date when the the customer's tax exemption starts
  • Account.TaxExemptExpirationDate — Date when the customer's tax exemption ends

See Merge Fields for Invoices for more information about the merge fields.

Greater Precision When Splitting Invoices

You can now split invoices with more precision. Previously you could only split invoices by specifying the split percentages in integers. Now you can specify the split percentages in decimal numbers of up to nine decimal places. For example, you might split an invoice into three parts by using split percentages of 33.3%, 33.3%, and 33.4%.

Splitting an invoice is in Limited Availability. If you already have split invoice enabled, the decimal precision enhancement is available automatically. Submit a request at Zuora Global Support only if you wish to have access to split invoice feature.

See Splitting Invoices for more information.

Enhanced Invoice Sequencing

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

We have made the following invoice sequencing enhancements to help you with auditing and compliance:

  • Invoice numbers, such as INV00000001, are now generated in a fully sequential order with no gaps in the sequence. Previously, certain scenarios, such as a failed subscription process, might cause invoice numbers to be skipped.
  • Now when you split an invoice, the original invoice remains in Zuora in “cancelled” status. Previously the original invoice would be deleted, causing a gap in your invoice numbering.

See Splitting an Invoice for more information.

Finance

Accounting Periods Can Now be Set to Pending Close

You can now set accounting periods to Pending Close as an intermediate phase before closing them. While an accounting period is set to Pending Close, only users with the Manage Close Process Z-Finance permission can create, update, or delete transactions that fall within the period. You no longer need to worry about extra transactions entering the accounting period that you’re closing during the close process.

Available to all Z-Finance users.

See Accounting Periods for more information.

Upcoming Changes to Accounting Codes

We will soon be making the following changes to accounting codes in Zuora:

  • You will only be able to specify accounting codes that already exist in your chart of accounts. For example, if you update the accounting code on a product rate plan charge by specifying a non-existent accounting code, an error is returned.
  • Accounting codes will require unique names, regardless of the accounting code type. For example, if you have a Sales Revenue accounting code called “Revenue,” you cannot have another accounting code also called “Revenue,” even if it is of a different type, such as Deferred Revenue. Only newly-created accounting codes will be affected. Existing accounting codes with duplicate names will not be affected.

Please ensure that your Zuora integration complies with these upcoming changes.

Zuora for Salesforce Release (Q4 2015)

Zuora for Salesforce Quotes Q4 2015 Release Notes and Zuora 360 Q2 2015 Release Notes

Synchronize Charge End Date of Product Charges and Subscription Rate Plan Charges

Starting in the November 2015 release, you can specify Charge End Dates in Zuora ​for new Subscriptions and New Product Amendments. Now the same functionality is available in Zuora for Salesforce. The Charge End Dates of Product Rate Plan Charges and Rate Plan Charges in Zuora are synchronized to the corresponding objects in Zuora for Salesforce. The following fields were added to the custom fields in Zuora for Salesforce to support the feature:

  • Product Rate Plan Charge.Up To How Many Periods
  • Product Rate Plan Charge.Up To Periods Type
  • Product Rate Plan Charge.End Date Condition
  • Subscription Product & Charge.Up To How Many Periods
  • Subscription Product & Charge.Up To Periods Type
  • Subscription Product & Charge.End Date Condition
  • Subscription Product & Charge.Specific End Date

See Sync Field Reference for the mapping of the RatePlanCharge and ProductRatePlanCharge object fields in Zuora to the corresponding fields in Zuora 360.

Manage and Extend

Features, enhancements, and release announcements for Zuora admin, Zuora integrations, and general information about Zuora APIs.

Integrations

Z-Suite Integrations Release

Z-Suite Integrations Release Notes January 27, 2016, v528 – Production Release.

APIs​

SOAP API

Current WSDL version: 74

See Zuora WSDL for information on how to check your version and download the latest version.

SOAP API Change History

See Zuora SOAP API Version History for a summary of updates made to the SOAP API in recent Zuora releases.

Date Field Changes as of WSDL 69

Please read this important note before using WSDL version 69 or later.

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.

Maintenance Release 196.1

This release includes internal fixes.

  • API Sandbox release, January 27, 2016
  • Production release, January 27, 2016

Maintenance Release 196.2

This release includes internal fixes and an enhancement, Calculate a Price for Each Usage Record in All Supported Rating Groups.

  • API Sandbox release, February 2, 2016
Last modified
21:46, 8 Aug 2016

Tags

Classifications

(not set)