July 2014 - New Features

Knowledge Center > ZZ ARCHIVE > ARCHIVED Zuora Billing Release Notes > 2014 New Features > July 2014 - New Features

July 2014 - New Features


Welcome to the Zuora July 2014 Release (R178, R178.1, R178.2, R178.3, R178.4). This release includes new features, enhancements, resolved issues, and improvements to the Knowledge Center.

Released Versions​

Environment Current Product Version Release Date Current WSDL
Production R178.4 August 3, 2014 58.0
API Sandbox R178.4 August 3, 2014 58.0

See Version Information for more version information.

Highlights by Zuora Keys

  • BILL: New mergefield for usage rate charge detail​ on custom invoices
  • COLLECT:  Override default accounting codes on invoice item adjustments​​ | Edit more ACH payment method ​fields on customer accounts
  • SCALE:  Increased simultaneous callout capacity by 60X

Zuora for Salesforce Release (Q1 2014)

See Zuora for Salesforce Quotes Q1 2014 Release Notes and Zuora 360 Q1 2014 Release Notes for details.

New Zuora Features and Enhancements


New Invoice Mergefield for Usage Charge Rate Detail

A new mergefield is available for use in the Usage Summary table of your custom invoices templates. The new UsageSummary.RateDetail mergefield makes it easier for your customers to see how their usage charges are calculated, especially for the tiered and volume pricing charge models.

You must upgrade your templates to the invoice file generation service to use the UsageSummary.RateDetail mergefield. For instructions on how to upgrade, see Upgrade to New Invoice File Generation Service.

Usage Charges: Tiered Pricing Charge Model

The UsageSummary.RateDetail mergefield displays Tier level, Tier unit range, Units consumed, Price per unit, and the Subtotal for each tier, and then the total charge for all tiers:

Tier 1: 1-100, $0.00 Flat Fee
Tier 2: 101-200, 100 Each(s) x $2.00/Each = $200.00
Tier 3: >=201, 10 Each(s) x $5.00/Each = $50.00
Total = $250.00

Usage Charges: Volume Pricing Charge Model

The UsageSummary.RateDetail mergefield displays Tier level, Tier volume, Units consumed, Price per unit, and the Total charge:

Tier 3: >=101, 150 Each(s) x $10.00/Each = $1500.00

UsageSummary.RateDetail displays usage charges that use the flat fee and per unit pricing charge models in a similar way to the above examples. The overage and tiered with overage pricing charge models are not supported by UsageSummary.RateDetail in this release. 

If you currently use the UsageSummary.ListPrice mergefield to display charges using the tiered or volume pricing charge models, you should consider using UsageSummary.RateDetail instead.

UsageSummary.RateDetail displays more information than UsageSummary.ListPrice, such as the number of units consumed, making it easier for your customers to see how their usage charges are calculated.

See Display Usage Charge Breakdown for more information.


New Override Available for Invoice Item Adjustments Accounting Codes

Deferred and Recognized Revenue accounting codes inherited by Invoice Item Adjustments from the Invoice Item can be now be overridden. You must have Z-Finance to access this feature. If you do not have Z-Finance, you can only override one accounting code.

See Creating Invoice Adjustments and Invoice Item Adjustments for more information.

Allow Editing on More Fields for ACH Payment Method

The Bank Name and Account Holder Name fields under ACH can be edited from the Customer Accounts page.


Increased Callout Capacity

We have increased the simultaneous callout capacity by 60X.

Zuora APIs


WSDL Version

For Release 178, the WSDL version is 58.0. See The Zuora WSDL for information about downloading the current version.​

Resolved Issues

The following issue was resolved for this release.

Unable to Update Amended One-time Charge's Custom Field through SOAP API

The following two-step process failed:

  1. Perform an update product amendment on a one-time rate plan charge, either through the Zuora application or the amend() SOAP API.
  2. Call the update() SOAP API to edit that one-time charge's custom field.

The update() call generated an error. If you edited the custom field through the Zuora application the update() call would succeed, and no error was generated.

Zuora Knowledge Center

Customer-requested Improvements to Articles

We updated the following Knowledge Center articles based on customer-reported feedback:

Maintenance Release 178.1

  • Production release, July 22, 2014
  • API Sandbox release, July 21, 2014

This maintenance release includes internal fixes.

Maintenance Release 178.2

  • Production release, July 28, 2014
  • API Sandbox release, July 28, 2014

This maintenance release includes internal fixes.

Maintenance Release 178.3

  • Production release, July 30, 2014
  • API Sandbox release, July 30, 2014

This maintenance release includes internal fixes.

Maintenance Release 178.4

  • Production release, August 3, 2014
  • API Sandbox release, August 3, 2014

This maintenance release includes the following fix and other internal fixes.

The lifespan of a "standalone" payment method was extended from 72 hours to 120 hours
Starting from this release, orphan payment methods that are not tied to a Zuora account are deleted after 120 hours.
Last modified


This page has no custom tags.


(not set)