October 2012 New Features

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2012 New Features > October 2012 New Features

October 2012 New Features


We are pleased to provide you with a summary of our October, 2012 release (R157), including new features and resolved issues.

New features

This release includes the following new features and enhancements.

Zuora Billing

The following features have been added to Z-Billing and Z-Payments.

Ability to split invoices to support flexible payment schedules

In this release, we have added the ability to split a draft invoice into multiple invoices. You can create multiple invoices, with each defined as a percentage of the original invoice, and configure the invoice date and payment terms for each one. 

Splitting an invoice lets a customer spread out payments for a single invoice across multiple invoices. For example, a customer has an invoice that totals $100,000. You agree to let the customer make four payments spread across multiple billing periods on the invoice. You can split that invoice into four separate invoices, each for a specific percentage of the original amount. These percentages can be any amount that you want to set, as long as the collection of split invoices total 100% of the original invoice. In our example, you could set the first split invoice to 40% ($40,000), then each successive split invoice to 30% ($30,000), 20% ($20,000), and 10% ($10,000).

 This is a controlled release feature. Contact Zuora Global Support to learn more about enabling this feature. 

See Splitting Invoices for more information about using this feature. 

Inclusive tax support for discount charges

In this release, we have added support to calculate tax on discount charges when using the inclusive tax mode. No action is required on your part to take advantage of this enhancement. If your base product charge is specified as being taxable with inclusive tax, then any discount applied to that charge will automatically now have a portion of the discount carved out as tax.

See Using the Tax Modes for more web-based UI information on inclusive tax (a new enhancement from our September release). See the TaxMode field in the ProductRatePlanCharge object for more API information on inclusive tax.  

Price update from product catalog pricing on subscription renewal

In this release, new uplift options are available. Uplift is the term for a price change on subscription renewal. As such, uplift options are available for termed subscriptions, but not evergreen subscriptions.

In the past, Zuora allowed you to uplift prices upon renewal by a fixed percentage, for example, to take account for inflation.

In this release, Zuora is providing the ability to change subscriber pricing to whatever the current charge pricing is in the product catalog at the time of renewal. This allows you, for example, to make pricing strategy changes that can then automatically be reflected in subscriptions as they renew.

When you set an automatic uplift on a product rate plan charge, you have the following options:

  • No Change is a new option that keeps the charge price the same upon subscription renewal.
  • Percentage Increase changes the price by a percentage that you specify. This option has been available prior to this release.
  • Use Latest Product Catalog Pricing is a new option that applies the current price of that charge in the product catalog to the subscription renewal.

See Automated Price Change (Uplift) for Renewed Subscriptions for more information about this feature. 

On-demand rating for tiered usage charges

In this release, you can now use Zuora's on-demand usage rating capability with tiered usage charges.  Prior to this release, on-demand usage rating was supported for per unit usage charges only.

See On-Demand Usage Rating for more information about using this feature. 

Zuora Finance

The following features have been added to Zuora Finance.


We have made the following improvements to Z-Finance for this release.

Deferred revenue report

In this release, we have added a deferred revenue report. This report is billing-based only, and includes invoice items, invoice item adjustments, daily revenue recognition, and monthly accounting periods. 

See Revenue recognition reports for more information.

Configurable revenue recognition rule and general ledger accounts on product rate plan charges

We have added general ledger (GL) accounts (deferred revenue accounting code, recognized revenue accounting code) and revenue recognition rule names to the product rate plan charge information.

If you are using Z-Finance, you will see additional fields when viewing product rate plan charge objects in the Zuora UI.

See Map accounting codes for more information about using this feature.

In the Zuora API, we have added three fields to the ProductRatePlanCharge object and data source: DeferredRevenueAccount,RecognizedRevenueAccount, and RevenueRecognitionRuleName. See the ProductRatePlanCharge object for information about using these fields. 

Accounting Close Aging Balance summary

In last month's release, we added Accounting Close Aging Balances to Z-Finance. In this release, we have added a summary section that displays this information in the Summary tab of the Accounting Period summary page. You can select a currency to see the aging balance sum for each aging bucket and the total aging balance. 

See Run a trial balance for more information about using the Accouting Close Aging Balance information. 

Zuora API

The following features have been added to the Zuora API. 

WSDL version

The Zuora WSDL has been updated to version 43.0. See WSDL and API Versions for information about downloading the latest version. 

Product catalog price update on renewal in the API

The fields, PriceIncreaseOption and PriceIncreasePercentage have been removed and replaced with PriceChangeOption and PriceChangePercentage in the objects ProductRatePlanCharge and RatePlanCharge. These fields remain optional.

The ProductRatePlanCharge object has a new field, UseTenantDefaultForPriceChange.


Applies an automatic price change when a termed subscription is renewed.

Type: string (enum)
Character limit
Version notes: WSDL 43.0+
System generated for this object: no
Allowable values

  • NoChange (default)
  • SpecificPercentageValue
  • UseLatestProductCatalogPricing

Specifies the percentage to increase or decrease the price of a termed subscription's renewal. Use this field if you set the PriceChangeOption value to SpecificPercentageValue.

Type: decimal
Character limit: 16 {99999999999999.99}
Version notes: WSDL 43.0+
System generated for this object: no
Allowable values: a decimal value between -100 and 100


Applies the tenant-level percentage uplift value for an automatic price change to a termed subscription's renewal. You set the tenant uplift value in the web-based UI: Z-Billing > Define Default Subscription Settings

Operations: Create, Query, Update, Delete, Filter
Type: boolean
Character limit: 5
Version notes: WSDL 43.0+
System generated for this object: no
Allowable valuestruefalse

Ability to find the specific base charge associated with a discount

In this release, you can now use the Zuora API to find the specific invoice item on an invoice with which a discount charge is associated. This is useful, for example, if you are using the Zuora API to create your own invoices and want to display any applicable discount right next to the charge it is discounting.

For discount charge invoice items, you can now use the new field, InvoiceItem.AppliedToInvoiceItemId to navigate to the base charge invoice item being discounted. This field is read-only and is only populated for discount charges.

Create InvoiceItemAdjustments for discounts and negative line items via API

In this release, you can reduce the size of a discount on an invoice as long as the invoice total moves towards 0. In other words, you can achieve this by adjusting the discount / negative line item by a positive amount, as long as you also adjust another invoice item by an equal or greater negative amount at the same time. This API behavior is consistent with what is already supported in the Zuora UI.

To use this capability, you pass in multiple invoice item adjustments through the create() call. You must also use the CallOptions container in your create() call's SOAP header, and set its useSingleTransaction field value to true

Previous to this release, the CallOptions container was not part of the create() call. 

New call and objects for splitting invoices

In this release, you can split invoices in the API using the existing create() call, the new execute() call, and the new objects, InvoiceSplit and InvoiceItemSplit.

You start by creating an InvoiceSplit object, then create an InvoiceItemSplit object for each split invoice, then execute the InvoiceSplit object.


Contains the individual split invoices that together formed the original invoice.

You can use this object with the following calls:


The individual split invoices that together formed the original invoice.

You can use this object with the following calls:


Creates split invoices from the InvoiceSplit and InvoiceItemSplit objects.

Resolved issues

The following issues were resolved in this release.

Zuora Billing

The following issues were fixed in Z-Billing and Z-Payments.

DE9822: Invoice balance fractions are not consistent with tenant currency fractions

For some currencies, invoice balances displayed an invalid number of decimal places. 

We have fixed this issue in this release. 

DE9910: Error with the CyberSource gateway

In some cases, payments submitted to the CyberSource gateway would return a "Payment failed due to a processing error" error message. 

We have fixed this issue in this release. 

DE10073: Error with the PayPal gateway

In some cases, payments submitted to the PayPal gateway would return a "Failed to connect to host Input Server" error message. 

We have fixed this issue in this release.

DE10139: Subscription Rate Plan Charge custom field is being set to null

Applying an Update a Product and Renewal amendment could set the Subscription Rate Plan Charge custom field to null.

We have fixed this issue in this release.

US7379: New limits for contacts and payment methods for accounts

To resolve a potential memory issue, we have added a limt to the number of contacts and payment methods that you can add to an account. You can now add a maximum of 100 contacts and/or payment methods to an account.

Patch 157.1

The R157.1 release (October 24, 2012) includes internal operational fixes, including fixes for browser issues and maintenance fixes to Z-Force.

Last modified


This page has no custom tags.


(not set)