We are pleased to provide you with a summary of our August, 2011 release.
This release includes the following new features and enhancements.
The following features have been added to Z-Billing.
In this release, Zuora has added the Enterprise Billing feature set. This includes the Customer Hierarchy features, which help manage the customer account parent-child relationship for the vendor. This includes the following functionality:
Aggregate the Usage Billing of Child Accounts
In this release, Zuora added the ability to track the usage of child accounts. This applies to accounts configured to use the customer hierarchy feature.
This feature collects the usage records from child accounts and applies them to the parent account. The parent account must contain a subscription with a matching unit of measure (UOM). All of the usage records are rated and billed from the parent account.
If the account in the example contains more than one subscription with a matching UOM, the usage records will be rated in all the subscriptions as if the usage records were uploaded against the parent account.
By default, this permission is disabled. To use this feature, navigate to Z-Billing > Settings > Define Billing Rules, and enable the Include usage from child accounts when billing? setting.
In this release, Zuora has added the ability to invoice subscriptions to different accounts. With this feature, you can configure a subscription in an account to be rated and billed by a billing run initiated from a different account. This is typically used to create a hierarchical billing situation for larger companies with many departments, divisions, and/or subsidiaries
Previously, a subscription could have a single owner account. After creating the subscription, you could use an owner transfer amendment to change the subscription owner account. With this release, a subscription has an owner account and an invoice owner account. You can now use an owner transfer amendment to change subscription owner account, the invoice owner account, or both.
The subscription owner and the invoice owner accounts must use the same currency settings.
Each subscription now includes an Invoice Owner field. You can use this to assign the invoice responsibility of a subscription to a customer account that is not the owner of the subscription.
All existing subscriptions will use the Customer Name as the default invoice owner.
The feature is controlled by a tenant-level permission. The permission is disabled by default. If permission is disabled, the owner and invoice owner will be set to the same account when you create a subscription. If this permission is enabled, you can specify different accounts for the owner and invoice owner when creating a subscription. Contact Zuora Global Support to use this feature.
The following changes have been made to the Zuora application user interface:
The following changes have been made to the Z-Commerce API:
You can use these fields with the subscribe(), amend(), and query() API calls. You must have the Owner Transfer Amendment permission to be able to edit and change these fields.
See Subscriptions for more information.
In this release, we have added the following permissions to the Z-Billing Standard User role:
These permissions are enabled by default.
If a user attempts to create an account, contact, or payment method without the required permission, they will receive a "Permission required" error if they are using the Zuora user interface, or a "NO_PERMISSION" exception if they are using the Z-Commerce API.
This is a Controlled Release feature. Contact Zuora Global Support for information about using this feature.
Zuora has added the ability to export a secure version of encrypted data source fields. In this release, Zuora has added the ability to view and export the AchAccountNumber field of any PaymentMethod data source object.
To be able to use this feature, you must sign a security contract with Zuora and store your public key in the Zuora System. Zuora decrypts the fields and exports them to a file. We then encrypt the file using your public key, insuring that the fields are never available in plain text format.
To use this feature:
If you exported encrypted fields without specifying the "encryption" option (Encrypt Export or setting Encrypted to "true"), the encrypted fields are masked (replaced with "******").
If you delete the record, the exported file will be removed, but the export record is kept to track all encrypted export history. In the Export history, a lock icon in the File type indicates an encrypted record.
If this feature is not enabled for your tenant, you can use the API to set Encrypted to "true," but the API will return an error message.
The encrypted fields are never selectable in a Z-Commerce API query() operation. If you attempt to select an encrypted field, you will receive an "invalid field" error.
See Data Sources for more information about using Zuora data sources.
The following features have been added to Z-Payments.
In this release, we have added the ability to cancel electronic refunds. Currently, this functionality is supported only for the Chase Paymentech Spectrum gateway.
You can cancel processed refunds that have the status "Marked for Submission." You cannot cancel refunds that have been settled by the payment gateway.
We have added a Cancel option for processed electronic refunds, located in the Refund detail page.
You can also use the Z-Commerce API to cancel electronic refunds. To cancel a refund, you must pass the refund ID and the refund status.
The following is an example of a SOAP message that sets the status of an electronic refund to "Canceled:"
<soapenv:Body> <ns1:update xmlns:ns1="http://api.zuora.com/"> <ns1:zObjects xmlns:ns2="http://object.api.zuora.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:Refund"> <ns2:Id>4028923930fdf8a30130fdfc27a30068</ns2:Id> <ns2:Status>Canceled</ns2:Status> </ns1:zObjects> </ns1:update> </soapenv:Body>
This feature is controlled by a new permission, Cancel Electronic Refund, located in the Refund category. This permission is enabled by default for all tenants who have the Refund permission.
See Refunds for more information about refunds in Zuora.
The following issues were resolved in this release.
The following issues were fixed in Z-Billing:
Previously, Zuora did not return the bill cycle day (BCD) correctly for subscription rate plan charges. Performing a query such as select Id, BillCycleDay from RatePlanCharge would return values only if RatePlanCharge was configured to use "specific day of month."
In this release, querying the BCD from RatePlanCharge will work correctly for all BCD values.
This issue has been fixed in this release.
Note: This is a Controlled Release feature. Contact Zuora Global Support for information about using this feature.
In this release, we have improved the way in which the Usage data source connects to RatePlan and RatePlanCharge. You will now be able to use the following fields:
The following issue was fixed in Z-Suite.
Previously, the CRM ID was mapped incorrectly between Zuora and NetSuite.
In this release, the mapping has been fixed, and the field is passed properly.
The following issue was fixed in the Z-Commerce API.
Previously, when using the Zuora Object Query Language (ZOQL), results would not be sorted if you did not specify either ascending (ASC) or descending (DESC) in the order by clause.
In this release, the ZOQL sorts results in ascending order if you do not specify ASC or DESC in the order by clause.
For example, the following two statements will return results in ascending order:
select * from Account order by ID" = "select * from Account order by ID asc select * from Account order by ID" = "select * from Account