Explains what the feature is or what its benefits are to the user or customer.
This release includes the following new features and enhancements.
The following features have been added to Z-Billing.
Zuora's notifications feature allows you to automate communications with your customers, using email and callout notifications. Before you can create and use notifications, you must specify a default email address.
If you have not configured a default email address, Zuora now prompts you to enter that information when you add a new email template or add or edit a notification. A dialog appears that prompts you to enter a tenant email address, which will be used as the default value for the From and Reply-to fields in the default email templates.
To change the default email address, navigate to Settings > Administration Settings, then select Manage Tenant Profile.
See Set Up Profiles, Notifications and Email Templates for more information about using notifications and email templates.
We have added a new notification, Invoice Posted Within a Bill Run of Auto-Post and Auto-Email. Use this to send a notification when invoices are posted within a bill run and the bill run is configured to use the auto-post and auto-email options. This feature supports existing email notification behavior from within a bill run.
See Set Up Profiles, Notifications and Email Templates for more information about using notifications.
With the Enterprise Billing functionality introduced in the August, 2011 release, you can assign different customer accounts as the owner of the invoice and the owner of the usage. In this release, we have added the ability to include the account number associated with usage records in the Usage Detail section of a Word or PDF invoice file.
In this release, we have added the option to disable usage-based pricing. You can disable this option if your organization does not use usage-based charges. This hides the Usage Charges column in rate plans, customizing the Zuora interface for your organization's requirements.
You can configure this option in the Enable Charge Types / Models page (Settings > Z-Billing Settings > Enable Charge Types / Models).
We continue to release more data sources that allow you to customize the fields you would like to extract. You can also use data sources to combine key objects into a single dataset that can be accessed via the Zuora interface or via APIs.
In this release, we have added the Product data source. Use this data source to export Payment data, including amount, dates, and status. Each row represents a single payment. This data source also includes data on the account and payment methods associated with the payment.
To use the new data source, navigate to Z-Billing > Reports, then select the Data Sources tab.
The following features have been added to Z-Payments.
Merchant e-Solutions is a leading Payment Processor and Merchant Acquirer. This integration has been in Controlled Release for several months with pilot customers. The Controlled Release has successfully concluded and we are making this integration generally available for all customers.
See Setting Up Payment Gateways for more information about configuring payment gateways in Zuora.
Moneris is a leading Payment Processor for Canadian and United States merchants. This integration has been in Controlled Release for several months with pilot customers. The Controlled Release has successfully concluded and we are making this integration generally available for all customers.
See Setting Up Payment Gateways for more information about configuring payment gateways in Zuora.
The following features have been added to Z-Force.
This release provides the building blocks required to customize Z-Force Quotes, in the form of Global Apex Methods and Global VisualForce Components. Using the Global Methods and Components, Force.com developers can extend and tailor Z-Force Quotes for their highly-advanced and custom business needs and flows. The effort required for customization has now been reduced dramatically with these reusable plug-and-play methods and components.
See the Z-Force Global Methods and Components Developer's Guide for more information.
In this release, custom fields defined on Zuora objects will be synced automatically to Salesforce if a corresponding field (with the same API name) has been created in Salesforce. This applies to all the objects in the Product Catalog sync as well as the Accounts and Related Objects sync.
See Syncing Zuora Custom Fields for more information.
Z-Force Quotes now has the ability to include discount charges when creating subscriptions in Zuora with the existing “Send to Z-Billing” functionality. All types of discount charges are supported for new subscriptions, amendments, and renewals. In this release, Z-Force Quotes will not perform any calculations based on discount charges.
Users now have the ability to create multiple quote templates for new subscriptions, amendments, and renewals. A new configuration screen allows users to map multiple quote templates for each of the three types, as well as specify a default template for each.
See Configure the Quote Templates for more information.
In addition to the PDF format, users now have the ability to generate quote documents in MS Word format. This allows you to modify the generated document.
See Generating a Quote File for more information.
A new Z-Force Quotes configuration option allows the admin to create subscriptions using the Opportunity Name, Quote Name or an auto-generated number. This feature also enables users to create multiple quotes or subscriptions under the same opportunity.
Z-Force now fully supports the Chrome browser.
Z-Force now has the capability to use the Salesforce user’s locale to format dates in the quote template.
The fields Subscription Term End Date, Rate Plan Charge Effective End Date and Zuora ID for BillingAccount, Subscription, SubscriptionCharge and Invoice are now synced from Zuora to Salesforce in Z-Force 360.
Included Units are now displayed on the Quote page when you select an Overage Pricing Model charge. You can also edit Included Units when creating a new quote.
This feature is not currently supported for amendments or renewals.
A new configuration option provides the admin the ability to enable this feature, which computes and displays a "blended" price for Tiered Rate Plan Charges.
This feature is disabled by default.
A new configuration option allows the administrator to hide the Service Activation and Customer Acceptance Dates on the New Quote screen.
The following features have been added to Z-Suite.
In this release, you are no longer required to enter an email address to create a new the Z-Suite integration.
We have added multiple field to Zuora to allow you to specify more information about your customers. Use the NetSuite Customer Type field in the Account detail to specify whether a customer is a Company or an Individual and map that information to NetSuite.
Use the Sync to NetSuite field on customer accounts in Zuora to specify whether the account should be synced.
If you set this to "Yes" (or leave the field empty), the account and all related transactions will sync to NetSuite. If you set this to "No," any changes that you make to the account and related transactions will not be synced to NetSuite.
Zuora will automatically populate the Transaction Number field on the payment object when NetSuite payments are synced to Zuora. Because NetSuite does not use payment numbers, Zuora will create the value as the customer name concatenated with the payment date.
This field will not be populated when the payment originates in Zuora.
We added a new field to the subscription rate plan that allow you to include the NetSuite project in the subscription. This allows you to create variable revenue recognition using the project code.
Use the NetSuite Revenue Recognition Template Type to specify whether you are using a Standard or Variable template. This is used in conjunction with Projects in NetSuite to allow the revenue recognition of individual invoice items to be tied to project progress or completion.
During the sync, if an invoice item’s charge is configured with NetSuite Revenue Recognition Template Type set to "Variable," the InvoiceItem and any of its TaxationItems will be mapped with a Project reference and the revenue recognition template reference (the Zuora charge’s revenue recognition template must match a NetSuite template of type Variable). In this case, the sync will not map revenue recognition dates.
We added a new field in the product detail page and rate plan detail page to define the NetSuite item type to create. This allows you to select an item type other than "non-inventory" for Zuora Product and Zuora Rate Plan objects. Please note that this item type selection is already available on Zuora Charge.
Use the NetSuite Item Type fields to specify whether a product or product rate plan applies to a Non-inventory, Inventory, or Service type of item.
In previous releases, Zuora has allowed flexible mapping of the Subsidiary, Department, Class, and Location in NetSuite. In this release, we added advanced mapping rules.
You have the ability to enter default Subsidiary, Department, Class, and Location values for Z-Suite.
In addition, you can also enter Subsidiary, Department, Class, and Location values on both the Zuora Charge and the Zuora Account.
In Z-Suite, you can also select whether to use the Subsidiary, Department, Class, and Location value from the Zuora Charge or the Zuora Account when synchronizing Customer Accounts and Transactions (Invoices, Payments, Refunds, Adjustments).
The following features have been added to the Z-Commerce API.
We have added the BcdSettingOption field to the Account object. The object is of type string, and can take the values AutoSet or ManualSet. The default value is ManualSet.
When the value is set to AutoSet, you cannot set the billing cycle day (BCD). The BCD value will be populated automatically by Zuora.
See Account for more information.
Processed usage records are always associated with a chargeable event item and an invoice item in an invoice.
In this release, we have added the ability to query by Invoice ID and Invoice Number when querying the Usage object.
SELECT [usage FIELD] FROM Usage WHERE InvoiceNumber= AND [other condition] SELECT [usage FIELD] FROM Usage WHERE InvoiceId= AND [other condition] SELECT [usage FIELD] FROM Usage WHERE InvoiceId= AND InvoiceNumber= AND [other condition] SELECT [usage FIELD] FROM Usage WHERE InvoiceId= OR InvoiceNumber= AND [other condition]
The following issues were resolved in this release.
The following issues were fixed in Z-Billing.
Previously, a user could switch between defining notifications for Z-Billing and for Z-Payments, without saving any changes.
In this release, a user cannot switch between Z-Billing and Z-Payments while editing notifications.
Previously, a user could edit the Related Event field when editing email templates which are currently being referenced by notifications.
In this release, users cannot update the event category of email templates if the template is referenced by a notification.
Previously, if a notification was configured with the Callout option enabled and the Email option disabled, Zuora would send an email notification.
In this release, Zuora will no longer send an email notification when the Email option is disabled.
Previously, you could not have Auto-set as the only active billing cycle day (BCD) option.
In this release, we have removed that restriction.
Previously, the billing run delete operation was a synchronous operation.
In this release, we have changed the delete operation function to be asynchronous. We have also changed the operation to process one invoice per transaction.