Knowledge Center

Knowledge Center > What's New > Previous Zuora Releases > 2013 New Features > May 2013 - New Features

May 2013 - New Features

Table of contents
  1. Overview
    1. Highlights
    2. New features
    3. Zuora Billing and Payments
        1. New admin settings control whether a user role can edit settings for Z-Billing, Z-Payments, and Z-Finance
        2. Invoice Templates now support Subscription Owner Account Name for Invoice items
        3. Reason Codes added for invoice adjustments, invoice item adjustments, and credit balance adjustments
        4. Payment Method status can now be edited (Active/Closed)
        5. Multi-currency support added for Merchant eSolutions and Verifi payment gateways
      1. Zuora now supports non-referenced (credit balance) refunds for Litle payment gateway
        1. Secondary reference ID now supported in Qvalent QuickGateway, providing easier refund reconciliation
    4. Zuora Commerce
        1. Quote Templates offer new formats and content
        2. Quote PDF generation is now faster
    5. Zuora APIs
      1. REST API
        1. REST write privileges controlled by API Write Access setting
      2. SOAP API
        1. WSDL Version
        2. Zuora now returns payment gateway Response and Reason Code for subscribe() and amend()
  2. Resolved issues
    1. Billing and Payments
        1. Scrolling problem with IE8 in Z-Billing customer account Notes field
        2. Bill run errors when charges had very long names
        3. Activating DRAFT amendments on cancelled subscriptions
        4. Cancellation of a bill run successfully cancelled the run but did not update the status
        5. Tax Rate file uploads rejected tax-code names of more than 32 characters
    2. Zuora APIs
      1. REST API
        1. Unable to create a new account in REST with an HPM credit card payment method ID
        2. When creating a new account in REST, the paymentTerm field should be optional
        3. REST responses did not return nextPage field even when more data was available
  3. R164.1
    1. SOAP API now supports optional InvoiceTargetDate field when creating a new subscription
  4. R164.2
    1. Problem with Quote PDF if contact information not included in quote template
  1. Overview
    1. Highlights
    2. New features
    3. Zuora Billing and Payments
        1. New admin settings control whether a user role can edit settings for Z-Billing, Z-Payments, and Z-Finance
        2. Invoice Templates now support Subscription Owner Account Name for Invoice items
        3. Reason Codes added for invoice adjustments, invoice item adjustments, and credit balance adjustments
        4. Payment Method status can now be edited (Active/Closed)
        5. Multi-currency support added for Merchant eSolutions and Verifi payment gateways
      1. Zuora now supports non-referenced (credit balance) refunds for Litle payment gateway
        1. Secondary reference ID now supported in Qvalent QuickGateway, providing easier refund reconciliation
    4. Zuora Commerce
        1. Quote Templates offer new formats and content
        2. Quote PDF generation is now faster
    5. Zuora APIs
      1. REST API
        1. REST write privileges controlled by API Write Access setting
      2. SOAP API
        1. WSDL Version
        2. Zuora now returns payment gateway Response and Reason Code for subscribe() and amend()
  2. Resolved issues
    1. Billing and Payments
        1. Scrolling problem with IE8 in Z-Billing customer account Notes field
        2. Bill run errors when charges had very long names
        3. Activating DRAFT amendments on cancelled subscriptions
        4. Cancellation of a bill run successfully cancelled the run but did not update the status
        5. Tax Rate file uploads rejected tax-code names of more than 32 characters
    2. Zuora APIs
      1. REST API
        1. Unable to create a new account in REST with an HPM credit card payment method ID
        2. When creating a new account in REST, the paymentTerm field should be optional
        3. REST responses did not return nextPage field even when more data was available
  3. R164.1
    1. SOAP API now supports optional InvoiceTargetDate field when creating a new subscription
  4. R164.2
    1. Problem with Quote PDF if contact information not included in quote template

Overview

We are pleased to provide you with a summary of our May 2013 release (R164), including new features and resolved issues.

Highlights

In May we continue giving our customers more information and greater control. Here are some of the highlights:

✓ Quotes:  New format options for dates, numbers, and zero-balance items, support for custom objects, and faster quote generation

✓ Billing & Payment: Payment-method status now editable, subscription-owner account name added to invoice templates, and reason codes added to invoice adjustments, invoice item adjustments, and credit balance adjustments

✓ Payment gateways: Non-referenced credit refunds for Litle, multi-currency support for Verifi and Merchant eSolutions, and easier refund reconciliation for Qvalent - plus gateway Response and Reason Codes returned by our SOAP API subscribe() and amend() calls 

Please read on for more information about these and other changes.

New features

This release includes the following new features and enhancements.

Zuora Billing and Payments

New admin settings control whether a user role can edit settings for Z-Billing, Z-Payments, and Z-Finance

Admins can now control whether a user role can access the settings menus for Z-Billing, Z-Payments, and Z-Finance. This feature is accessed via Settings > Administration Settings > Manage User Roles, and is individually set for each role under each product in the dropdown list there. Users who lack this new privilege for a product, such as Z-Billing, can still see the product listed on the Settings menu, but selecting it returns a message such as "You do not have permission to view or modify Zuora Z-Billing Settings. Contact your company's Zuora administrator to obtain permission." Since this permission was enabled for all user roles in the past, it is still enabled for all existing roles with this release, but must be manually enabled for new roles you create in the future.

For more on this, see Managing User Roles.

Invoice Templates now support Subscription Owner Account Name for Invoice items

Invoices can now display the Subscription Owner Account Name for Invoice Items. This will help you present more informative, attractive invoices in certain invoice ownership and partner scenarios. You can download the new invoice template and instructions at Settings > Z-Billing Settings > Manage Invoice Rules and Templates

Reason Codes added for invoice adjustments, invoice item adjustments, and credit balance adjustments

Users can now configure and use reason codes for invoice adjustments, invoice item adjustments, and credit balance adjustments. Some possible reasons might include early cancellation, customer satisfaction, or delinquent payment issues. You'll recall that we started supporting reason codes for refunds back in January. This type of information provides insight into payment exceptions, cash flow, and your customer relationships.  By default, Standard Users have the Change Reason Codes permission, accessible via Settings > Administration Settings > Manage User Roles.

Payment Method status can now be edited (Active/Closed)

In this release, Zuora expands your control of payment methods by allowing you to edit the Payment Method status in the UI and SOAP API. All payment methods are Active when created, but you can now change them to Closed, or back to Active again, as needed - for instance, when a customer asks you to retry a card, or stop using a card, or as part of your workflow for Auto-pay.

Multi-currency support added for Merchant eSolutions and Verifi payment gateways

We're delighted to report that Zuora has added support for multiple currencies in Merchant eSolutions and Verifi. This means that all of our pre-integrated payment gateways now support multiple currencies - good news for our growing customer base of global companies!

Zuora now supports non-referenced (credit balance) refunds for Litle payment gateway

Zuora continues to roll out support for non-referenced (credit balance) refunds for additional pre-integrated gateways. In this release, we support credit balance refunds for the Litle gateway, allowing customers to take full advantage of Zuora’s credit balance functionality. Users no longer have to leave the Zuora application to issue a credit balance refund in the gateway, then map the refund in Zuora;  this two-step manual process is now done in one step without leaving Zuora.

For more information, see Canceling and Refunding Credit Balances.

Secondary reference ID now supported in Qvalent QuickGateway, providing easier refund reconciliation

For Qvalent QuickGateway, the secondary reference ID field is now supported for refunds as well as payments, making it easier to reconcile payment and refund transactions.

Zuora Commerce

Quote Templates offer new formats and content

This month we continue our ongoing enhancements to Quote Templates with three new display features:

  1. Your quote templates can specify date and numeric formats, including numeric precision, percentage, and currency symbols.
  2. Also, you can now opt to hide $0 line items
  3. And Quote Templates now support custom Salesforce objects.

You'll find more information in the revised instructions, which you can download at Z-Force > Quote Templates.

Quote PDF generation is now faster

WIth this release, Z-Force users will be pleased to notice faster generation of Quote PDFs due to an optimized, more efficient workflow.

Zuora APIs

REST API

REST write privileges controlled by API Write Access setting

When we introduced our REST API in April, permissioning was simple: if the tenant had REST API access, then all user roles were automatically granted full access to the REST API. However, in this release we've added a layer of control. If REST is enabled for the tenant, all users automatically have read access (i.e., the GET calls), but write access in REST now depends on the API Write Access setting in the user role. This allows administrators to restrict the ability of user roles to create, update, or delete data via the REST API.

For more on this, see Managing User Roles and Creating an API User.

 The REST API is in controlled release. Contact Zuora Global Support to learn more about enabling it for your tenant.

SOAP API

WSDL Version

The WSDL version for Release 164 is 47.0. As of Release 164.1, described at the bottom of this page, the WSDL version is 47.1.

See The Zuora WSDL for information about downloading the latest version.

Zuora now returns payment gateway Response and Reason Code for subscribe() and amend()

The SOAP subscribe() and amend() calls now return Response and Reason Code from the payment gateways. The new fields are defined in WSDL 47.0. This additional information gives a boost to our customers who are increasingly automating their payment-collection processes.

Resolved issues

The following issues were resolved in this release.

Billing and Payments

Scrolling problem with IE8 in Z-Billing customer account Notes field

An incompatibility with Internet Explorer version 8 prevented users from scrolling inside the Notes field when editing a customer account.

We have fixed this issue in this release.

Bill run errors when charges had very long names

Bill runs were failing when subscription charges had names that approached the documented maximum length.

We have fixed this issue in this release.

Activating DRAFT amendments on cancelled subscriptions

In some real-world workflows, an amendment to a subscription was created with DRAFT status, the subscription itself was subsequently cancelled, and then the workflow attempted to activate the amendment on the (cancelled) subscription.  The system did not check subscription status to prevent this operation.

We have fixed this issue in this release.

Cancellation of a bill run successfully cancelled the run but did not update the status

Recently, when customers cancelled a bill run in progress, the bill run was successfully cancelled but the bill run status was "Completed".

We have fixed this issue in this release.

Tax Rate file uploads rejected tax-code names of more than 32 characters

When uploading a Tax Rate CSV file, users got an error message if a tax code name was longer than 32 characters, even though the file template allows tax code names of up to 64 characters.

We have fixed this issue in this release; the system now accepts tax code names of up to 64 characters.

Zuora APIs

REST API

Unable to create a new account in REST with an HPM credit card payment method ID

When creating a new account with the REST API, you must either provide credit card information or an HPM credit-card payment method ID. However, a bug caused the system to return an error if an hpmCreditCardPaymentMethodId was specified.

We have fixed this issue in this release.

When creating a new account in REST, the paymentTerm field should be optional

The paymentTerm field should be optional when creating a new account, but was actually required in the initial release of the REST API.

We have fixed this issue in this release; the field is optional.

REST responses did not return nextPage field even when more data was available

In our initial release, REST responses did not include the nextPage field (a URL for requesting the next page of the response), even when more data was available.

We have fixed this issue in this release.

R164.1

The R164.1 release (May 21, 2013) includes the following enhancement:

SOAP API now supports optional InvoiceTargetDate field when creating a new subscription

When creating a subscription with the Zuora SOAP API, you have the option of immediately invoicing (for all subscriptions or just the new one) and collecting payment. This release allows you to specify the invoice target date. One possible use case is to invoice at subscription time for a service that begins in the future.

For details, see the description of SubscribeOptions under SubscribeRequest. You must install WSDL 47.1 or higher to use this feature.

R164.2

The R164.2 release (May 30, 2013) resolves the following issue:

Problem with Quote PDF if contact information not included in quote template

In release 164, if a quote template did not directly reference an account's contact information (BillTo or SoldTo), the resulting quote PDF contained fieldnames (e.g., "<<SAccount.Name>>") instead of Account data (e.g., "Acme Corporation").

This issue is resolved in R164.2.

Last modified

Tags

This page has no custom tags.

Classifications

(not set)