We are pleased to provide you with a summary of our September, 2010 release.
Key actions can now be easily launched from the Customer Accounts page, including the ability to Process Payments, Adjust Invoice Charges, Create Invoice Adjustments, or Refund a Payment. To launch these features, navigate to Customer Accounts > more.
To make it easier to manage multiple logins and instances of Zuora, we’ve added an indicator in the upper right section of the UI that indicates the user that is currently logged into Z-Billing.
We have streamlined our Adjustment functionality as part of our broader rollout of Payment Operations features to allow simpler reporting and integration, improve usability and ensure consistency with other transactions in the system.
Major changes include:
A new field has been added, "Impact Amount," which shows the amount that has impacted the invoice. For a Credit type, the impact amount will be negative and Charge Type, the impact amount will be positive. All existing adjustments will be migrated to this new format at the time of release. The Adjustments will be associated to the same invoices for the same amounts, so this migration will be seamless.
To create an invoice item adjustment, select an invoice, then select more > Adjust Invoice Items.
We now support the ability to create electronic refunds for the PayPal payment method directly from Z-Payments. To create a refund, go to a PayPal payment and click Create Refund.
As mentioned in the Z-Payments section, we are replacing our Adjustment and InvoiceAdjustment objects with a single, overhauled InvoiceAdjustment object. This structure will simplify the creation and querying of InvoiceAdjustments and better reflect the new data model. PLEASE NOTE: Unlike the other API changes in this release, this change affects all versions of the API. For more information on this API, please refer to the API documentation.
You may now create InvoiceAdjustments via the API. For more information on this API, please refer to the API documentation
Ability to auto-generate Subscription Names
As of the latest API version, subscription name (also known as subscription number) will no longer be a required field when creating a subscription. Subscriptions created without a subscription name will now auto-generate the subscription name (this functionality is now consistent with the behavior of our user interface) For more information on this API, please refer to the API documentation
We have added a “Last Segment” field to the RatePlanCharge object to make it easier to determine the latest version of the subscription. This makes common use cases such as displaying the latest subscription to end-customers easier to implement. For more information on this API, please refer to the API documentation.