We are pleased to provide you with a summary of our July, 2011 release.
This release includes the following new features and enhancements.
The following features have been added to Z-Billing.
Zuora has always provided the ability to increase the price of a subscription charge using an amendments. With this feature, you can set all of your subscriptions to automatically apply a percentage uplift (for example, a 3% uplift for inflationary costs) to all charges within the subscription upon renewal. For added flexibility and control, you can choose to apply uplift fees only to certain products or to specific subscription charges.
You can use the automated price change with Recurring Charges and Usage Charges. Because One-Time Charges do not renew, you cannot use them with the automated price change feature. You can use the automated price change feature with all charge models except for the Discount charge model.
We have also added new fields in the Z-Commerce API to support this feature:
See Automated Price Change (Uplift) for Renewed Subscriptions for detailed information about this feature.
Zuora has expanded support for usage custom fields to the invoice templates. You can now display usage custom fields on invoices, providing customers with more clarity and transparency into the usage they are billed for. A variety of custom fields are available to help you customize your application and to aid with integration and reporting.
To configure your invoice PDF template, navigate to Settings > Z-Billing Settings > Manage Invoice Rules and Templates. To display custom fields on your invoice PDF template, enter the custom field API name in the appropriate place on the Invoice PDF template.
See Manage Invoice Rules and Templates for more information about configuring invoice templates.
The following features have been added to Z-Payments.
Payments which have been canceled, voided, or errored can now be deleted, which allows you open up an invoice and subscription for editing. This is a specialized feature that is controlled by user permissions to allow only designated users to delete invalid payments as part of a data migration migration process.
For example, you can delete a payment created by an incorrect invoice, correct the invoice, then start a new billing run.
You can use both the user interface and API calls to delete payments. You can use the delete() operation with the Z-Commerce API Payment object.
You can delete a payment if the following requirements are true:
If you delete an Error payment directly, Zuora will not update the summary of the payment run.
See Deleting Payments for more information.
Zuora has enhanced its credit balance feature to support non-referenced electronic refunds in addition to external non-referenced refunds. Non-referenced electronic refunds (for the Verifi and Chase Paymentech Orbital Payment gateways) can be created to issue a credit to a customer electronically without referencing an existing payment in Zuora. The ability to issue refunds is controlled through user permissions under your Administration settings.
This feature is available only if you have enabled the Credit Balance feature; you must create a credit balance to be able to create a refund.
For example, you could create a refund for the following case:
To enable this feature:
We have added the
PaymentMethodId field to the Refund object to support electronic credit balance refund.
See Canceling and Refunding Credit Balances for more information.
In this release, we have added support for the following fields to be used with the Merchant e-Solutions (MES) Payment Gateway:
|Zuora Field||MES Field||Description||Required?||Length||Format||Notes|
|Invoice number||invoice_number||The invoice number||Yes, for preferred interchange||17||A/N||Defined by Visa as 0-9, a-z, A-Z, or spaces. No special characters allowed.|
|Total tax on Zuora invoice||tax_amount||Sales/local tax amount||Yes, for preferred interchange||12||Decimal required|
|Sold to contact postal code||ship_to_zip||Ship to zip code or postal code||Yes, for preferred interchange for Level III processing||5 or 9||A/N||This field is used only when implementing Level III processing.|
The MES Payment Gateway is in Controlled Release. Contact Zuora Global Support for more information.
The following features have been added to Z-Suite.
Our pilot customers have had success using Z-Suite product for some time, so we have made the following integrations available as part of the Z-Suite product:
There is a new option for Customer Account Number Mapping. This allows you to either map the Zuora Account.name to the NetSuite Customer ID or the NetSuite Company Name/First + Last Name (depending on the customer type) to the Zuora Account Number.
See Configuring Sync Preferences for more information.
The following issues were resolved in this release.
The following error affected multiple Zuora applications.
To prevent export errors, data returned by queries is now limited to 20,000 fields. Zuora will alert you if the query result is greater than this return limit.
The following error affected Z-Billing.
When creating a bill run or viewing information about an existing bill run, the Selected Customer Accounts includes the Bill To and Sold To columns. Previously, the values in these columns were links which opened a pop-up dialog that allowed you to edit the customer's Bill To or Sold To information.
To reduce confusion and make this table easier to use, we changed the behavior of these columns, and the text values for Bill To and Sold To are no longer links to open an edit dialog.