Zuora Release 2024.06.R11

Invoicing and Tax

►Enhancement on Billing Schedule 2

E-Invoicing with Sovos is now generally available.

The Zuora E-Invoicing feature provides the extensibility and configurability to empower you to build country- and customer-specific integrations with Sovos E-Invoice solution including:

• Create e-invoice file templates to streamline integration for new countries.
• Customize standard e-invoice file templates to meet specific customer requirements.

We now support India, Italy, and Saudi Arabia as pre-integrated countries. Our E-Invoicing framework allows you to integrate with any new country by yourself. If you want to integrate with Sovos in these countries, contact us. 

Note: The E-Invoicing feature provides the following capabilities:
E-invoicing with Sovos
E-invoicing with Avalara E-invoicing with PEPPOL

E-invoicing with Avalara and E-invoicing with PEPPOL are still in the Early Adopter phase. We are actively soliciting feedback from a small set of early adopters before releasing it as generally available. If you want to join this early adopter program, submit a request at Zuora Global Support.

►Support E-invoicing with Avalara

We now support our E-Invoicing integration with Avalara E-Invoicing and Live Reporting.

You can now configure Avalara as a service provider. For Avalara, we support countries that are part of the Peppol network and a few countries that are not part of Peppol but follow the country-specific invoice clearance process. We provide the following support to countries pre-integrated and not pre-integrated with us:

• Pre-integrated countries: We provide default invoice, credit memo, and debit memo e-invoice file templates to pre-integrated countries, including Australia and Mexico. 
• Countries not pre-integrated: We provide Peppol and Clearance processes for these countries, and you can select one of the processes. 

For more information, see E-invoicing with Avalara.

 

►E-Invoicing enhancements for countries not pre-integrated 

We enhanced business region configurations for countries that are not pre-integrated. After configuring a service provider, you can now select one of the following E-invoicing processes corresponding to the service provider in the Business Region section.

• Sovos
  • Clearance Only
  • Clearance with Cancellation
• Avalara:
  • Clearance
  • PEPPOL Network

►Index file control when exporting bulk PDF files

A new field, persistIndexFile, has been added to the Export bulk PDF files API request payload to control the generation of the index file. By default, the persistIndexFile field is set to true.

• When set to true, the index file is generated and included in the zip file.
• When set to false, the index file is not generated and consequently not included in the zip file.

This feature provides flexibility in managing document generation processes, facilitating efficient handling of high volumes of requests while ensuring scalability, performance, and ease of use.

Note: This functionality is accessible via API only. We recommended that you establish a workflow for bulk exporting PDF files and subsequently transfer them using FTP to the print vendor, which streamlines the document generation and distribution process.

Payments

►New countries supported for Ebanx credit card transactions

We have now improved the Ebanx payment gateway integration to support credit card transactions in additional countries. Previously, our support included Brazil and Mexico. As of this update, we now also support the following countries:

• Chile
• Colombia
• Costa Rica
• Dominican Republic
• El Salvador
• Guatemala
• Nigeria
• Panama
• Paraguay
• Peru
• South Africa
• Uruguay

For more information, see Overview of Ebanx payment gateway integration.

►End of Support of Collections Window, Notes, Advanced Payment Manager, Payment Plans, and Statement Generator features

During the end of support period beginning on June 3, 2024, features will still be accessible in all Zuora environments, but no further product development. Any critical defects, bug fixes or security issues will be evaluated and fixed at Zuora’s discretion. For more information, see Product and feature end of support plan.

• All customers using Advanced Payment Manager feature must transition to using the Payment Profiles functionality across the Zuora ecosystem and associated business processes by January 31, 2025.
• All customers using Payment Plans feature must transition to using the Payment Schedules functionality and APIs across the Zuora ecosystem and associated business processed by January 31, 2025.
• All customers using Statement Generator feature must transition to using the Account Summary Statement functionality and APIs across the Zuora ecosystem and associated business processes by January 31, 2025.

Events and Notifications

►PATCH HTTP method available for callout notifications 

The PATCH HTTP method is now available for callout notifications.

For more information about all supported HTTP methods and callout notification configurations, see Configure callout notifications.

►Enhancements on Manage Regions settings page 

We have implemented the following enhancements to the Manage Regions settings page:

• Rename the page to "Manage Countries, Regions and States" from "Manage Regions" for a better understanding.
• Relocate the page to the Administration Settings page from Billing Settings. We make this change because managing countries and subregions applies not only to Billing but also to Payments, Platform, and other products.

Rest API

►API Reference

For the detailed API documentation, see API Reference.

For a summary of REST API updates and documentation updates in the Zuora API Reference, see API Changelog. 

►New Zuora v1 API versioning scheme

The Zuora v1 API uses API versions to control backward-incompatible changes, such as deprecating a field on an object or replacing a parameter in a request. To use the version-controlled parameters or get version-controlled fields, you can specify the zuora-version request header to the version you want to use.

If no version is specified in the request header, by default, Zuora will use the minimum version (186.0) of the v1 API. All requests will use your tenant API settings, unless you override the API version.

Previously, all API versions were numbered, for example, 196.0. With this release, we are introducing a date-based versioning scheme. The latest available version is 2024-05-20. 

You can visit Zuora’s UI to use a new administration setting called API Versioning to upgrade your tenant to the latest API version. You can see the current API version for your tenant and the latest API version. As a precaution, we recommend you use the zuora-version request header to test the latest API version before committing to an upgrade. 

We recommend that you upgrade to the latest API version to take advantage of the latest Zuora capabilities. 

Before upgrading to the latest version, you should review and incorporate any backward-incompatible changes that might affect your integration. For a list of backward-incompatible changes, see API versions.

Quickstart API

►API Reference

From 2022.09.R1, the Quickstart API is available to you if you have the Orders (or Order Harmonization) and Invoice Settlement features enabled in your tenant. The QuickstartAPI allows new integrators to swiftly integrate with Zuora, and it supports essential business use cases.

For the detailed Quickstart API documentation, see Quickstart API Reference.

For a summary of REST API updates and documentation updates in the Quickstart API Reference, see Quickstart API Changelog. 

►SOAP API Details

Current WSDL version: 145

For information about how to check your version and download the latest version. see Zuora WSDL.

SOAP API change history

For a summary of updates made to the SOAP API in recent Zuora releases, see Zuora SOAP API Version History.