February 2012 New Features

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

February 2012 New Features


Zuora is pleased to provide you with a summary of our February 2012 release, including new features and resolved issues.

New Features

This release includes the following new features and enhancements.

Zuora Billing and Payments

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

On-Demand Usage Rating

We have added support for on-demand usage rating for usage charges that use a per-unit or tiered charge model. This feature supports flexible usage rating schedules by allowing multiple rating opportunities in a billing period. 

  • Support for flexible rating schedules: Zuora's usage rating schedule has traditionally been tied to predefined billing period on the usage charge, allowing usage to be rated and billed only at the end of the charge's billing period. You now have the option to use on-demand rating for usage charges. This allows you to rate and generate invoices whenever the usage data is uploaded, without having to wait until the end of billing period. This feature gives you added flexibility in managing your billing operations. 
  • Multiple rating opportunities in a billing period: Without on-demand rating, all usage records are processed at the end of a billing period, and any usage records submitted after usage has been rated and billed will not be processed. With on-demand usage rating, you can rate and bill for usage charges as frequently as needed during the open billing period for the usage charge. For example, to bill for monthly usage in January, the bill run target date should be between January 1 and January 31. You can upload usage throughout January and the usage will be picked up in the subsequent billing run as long as the January billing period remains open. A billing period is closed once the subsequent billing period has been invoiced. In this example, the billing period for January is closed once the bill run target date of February 1st and later is used.

When creating a per-unit usage rate plan in the Zuora application, use the Usage Records Rating Option and select On Demand to use on-demand usage rating. You can also use the UsageRecordRatingOption field of the RatePlanCharge object to set this value when using the Z-Commerce API to create a rate plan charge. 

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

Mandates for Existing Customers

In this release, we have added a feature that allows you to identify new and existing mandates. This makes it easier to migrate existing customers to Zuora. If you have any existing UK or Netherlands direct debit customers that will be migrated to Zuora, you will need to specify (on the payment method) whether the customer has an existing mandate in place and if any payment transactions have already been processed against that mandate. You can do this by selecting either "TRUE" or "FALSE" for the payment method attribute called "Existing Mandate." 

See Obtaining and Processing Mandates for more information.

Data Sources: Expanded Availability of the DefaultPaymentMethod Object

In this release, we have exposed the DefaultPaymentMethod source object to all objects that are related to the Account data source object

The DefaultPaymentMethod object is now available to the PaymentInvoice Payment, and Refund Invoice Payment data source objects.  

Zuora Commerce

The following features have been added to Zuora Commerce.


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

On-Demand Sync

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

In this release, we have added the ability to request on-demand sync as needed for specified billing accounts or products. You can use a set of Global Apex APIs under both trigger and non-trigger context to perform the sync.

See On-Demand Sync for more information about configuring and using this feature. 

Support for Charge-Level Custom Fields

We have added a new GlobalCustomFieldDefinition Apex class for use with Z-Force Global Methods and Components. Use this class to store a set of custom field names, for Z-Force Quotes objects that support custom fields. The custom field sets stored in this global API are available as static resources in the current request context.    

See Global Components for more information about the new GlobalCustomFieldDefinition Apex class, and Sending Custom Fields to Z-Billing for more information about and examples of using the new class with custom fields.

Z-Payments Page

Zuora is pleased to announce the general availability of the Z-Payments Page feature. Z-Payments Page is a hosted iframe that can be embedded in a website to allow you to create payment methods.

The Z-Payments Page feature provides the following benefits:

  • PCI-compliant payment method capture
  • Greater page flow control
  • Highly configurable user interface
  • Reduces the creation of accounts with invalid payment methods
  • Greater error handling
  • A platform to accept future payment methods that require user interaction (for example, PayPal and 3D-Secure) 

Z-Payments Page is a premium service offered by Zuora. Please contact Zuora Global Support or your Account Executive for details on purchasing Z-Payments Page. See the Z-Payments Page User Guide for information about configuring and using this feature.

Integrating Z-Payments Pages with Salesforce VisualForce and Salesforce Sites

Zuora also offers the ability to embed a Z-Payments Page into a Salesforce VisualForce page or Salesforce Sites page. You can use this feature to allow a sales representative to submit an order, including payment information, in a PCI-compliant way.

See Implementing Z-Payments Page with Salesforce.com for more information about configuring and using Z-Payments Page with Salesforce.com. 

Zuora API

The following features have been added to the Zuora API. 

WSDL Version 38.0

The Zuora WSDL has been updated to version 38.0. See The Zuora WSDL for information about downloading the latest version. 

New UsageRecordRatingOption Field for RatePlanCharge

To support the on-demand usage rating feature (see "On-Demand Usage Rating," above, for more information), we have added the UsageRecordRatingOption field to the RatePlanCharge object. 

See RatePlanCharge for a detailed description of this field.

Resolved Issues

The following issues were resolved in this release.

Billing and Payments

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

Import Usage for New Charges with Subscription ID and Charge ID Failed when Creating a New Product Amendment

In previous releases, importing usage against a charge created via a New Product Amendment would not complete successfully. 

We have fixed this issue in this release. 

InvalidChargeSegmentStateException Error Returned when Subscription is Renewed

In previous releases, an auto-renew subscription failure would occur when the Trigger Date was after the Term End Date. 

We have fixed this issue in this release. 

Owner Transfer Returns Error ZX-048328

You can now create a new Subscription with a different Invoice Owner. 

Missing Display Field for Tier with Overage Pricing Charge When Creating Update Product Amendment 

You can now set the Overage Calculation Option, Option for Unused Included Unites, and Price Increase Percentage on an Update Product Amendment.


The following issues were resolved in Z-Force. 

Contacts List in the New Quote Page Limited to a 1000-Item List

In previous releases of Z-Force Quotes, the Bill to Contact and Sold to Contact fields were drop-down lists that had a limit of 1000 contacts. 

In this release, on the New Quote page the Bill to Contact and Sold to Contact fields are displayed as lookup fields. These fields do not have the 1000-item limits.   

Effective Price and Total Do Not Populate Correctly on Quotes when List Price is 0

In previous releases, when creating a quote in Salesforce.com the effective price and total for each charge do not populate correctly if the price is 0:

  • If an effective price was entered, the total was set to 0.
  • If a total was entered, the effective price was set to 0.  

In this release, when list price is 0 the effective price and the total for each charge are computed correctly, and the discount field is disabled for that charge. 

Zuora API

The following issues were resolved in the Zuora API. 

Taxable Rate Plan Charges Must Have a Tax Code 

Previously, a product rate plan charge could be created that was set as taxable, but without a corresponding tax code. 

We have fixed this issue In this release. If you use the Zuora API to create a product rate plan code and set Taxable to true, you must also specify a value for TaxCode. If you do not specify a tax code, Zuora will return an error. 

Error on update() Requiring Custom Field Value

In previous releases, Zuora required that you supplied values for account-required custom fields on every Update API call.

We have fixed this issue in this release. 

Last modified


This page has no custom tags.


(not set)