Zuora Release 2022.12.R2

New REST API operation for signing up customers and creating subscriptions

A new REST API operation called "Sign up" is now available. You can use this operation to implement the standard requirements for signing up customers, such as validating the uniqueness of an account and limiting the number of subscriptions per account. Also, you can use this operation to create a subscription, generate an invoice, and collect payment for a new or existing customer. Details are as follows:

• For a new customer, you can perform the following tasks in one call with a higher performance than using the Create an order operation. Note that you can skip creating a payment method and still get the subscription and invoice successfully created.
  • Create an account
  • Create a payment method
  • Create a subscription
  • Generate an invoice
  • Collect payment
• For an existing customer, you can use an account identification field of an external system to specify the account.
• You can make asynchronous requests when using the "Sign up" operation.

Support for late usage processing

Under certain circumstances, you might need to deal with late usages that are not billed in time. Through the Late Usage feature, you can upload usage records to Zuora Billing even after the accounting periods are closed. You do not need to make changes to the closed accounting periods. Previously, the late usage records could be uploaded but would not be processed by Zuora.

After a late usage record is uploaded, Zuora will recalculate the total amount of the billed service period, to which the usage record is added. The amount of the late usage records is the remaining amount of the updated total amount deducting the existing total amount that has already been billed. 

The late usage will be listed as unbilled usage of the current unbilled service period and will be billed in the next billing cycle. Each record is listed as an item for the invoice generated by the bill run.

For more information, see Late Usage.

New REST API operations available for deleting invoices and retrieving operation jobs

The following REST API operations are now available:

• Delete an invoice
• Retrieve an operation job

You can use the "Delete an invoice" operation to delete any invoice that is no longer needed, and then use the "Retrieve an operation job" operation to retrieve the information about the invoice deletion operation job.

Whether to delete an invoice synchronously or asynchronously depends on the number of invoice items contained in the invoice. By default, if an invoice contains less than 100 items, the invoice is deleted synchronously. Otherwise, the invoice is deleted asynchronously. If you want to change the threshold, submit a request at Zuora Global Support.

 Back to Table of Contents

Support for passing billing and payment information to Braintree

On the Braintree gateway integration, when creating Credit Card payment methods through Payment Pages and processing payments with 3D Secure 2.0 enabled, we now support passing the following information to the Braintree gateway. You must submit a request to Zuora Global Support to enable this feature.

For more information about these fields and the corresponding fields in Zuora Payment Pages, see the following articles:

• Braintree Developer Docs
• Credit Card fields in Zuora Payment Page form

 Back to Table of Contents

Enhancement to Audit Trail (production only)

By the end of December 2022, we will perform an upgrade on Audit Trail for all production tenants.

After this upgrade, you can use three new fields, including year, month, and day, in the following Audit Trail tables:

• auditloginevent
• auditobjectchangeevent
• auditsettingchangeevent

For example, you can use the following query to retrieve login history records in October 2022:

SELECT * FROM auditloginevent WHERE year = 2022 and month = 10

In addition, the version field is removed from the auditloginevent table.

Note that the entirety of Audit Trail history in your production tenants will be retained after this upgrade.

For more information, see Data model of Audit Trail.

 Back to Table of Contents