More subscriptions per account

Address more complicated situations like reseller use cases with up to 80,000 subscriptions per account.

More invoice line items per invoice

Address more complicated scenarios like reseller use cases with up to 20,000 invoice line items per invoice.

Enhanced account batches

You can have up to 200 configurable account batches instead of 50. This provides you with great flexibility to manage your accounts during bill runs. For instance, you can categorize batches by country and channel or arrange your accounts based on billing cycle days and frequencies.

Dedicated shard

For customers who purchase Performance Booster Elite, we offer additional hardware enhancements for your production instance, for new and existing clients as explained below, that provide dedicated query performance and enable segregation from other customers. This provides even faster throughput on Bill Runs, Payment Runs, and improved concurrency on API requests.

Micro-batch bill runs

The Zuora Parallel Processing Engine uses a micro-batching technique to allow parallel generation of invoices, and hence shortening bill run times. Invoices within a bill run are automatically grouped into smaller batches and processed with greater throughput.

Rating:

• This impacts rating of Rate Plan Charges and drafting of Invoices.
• Typically, the majority of processing time is tied to rating and drafting.

Posting currency:

• This impacts the posting of each invoice following the rating step.
• While negligible at smaller volume, posting time becomes material as the volume of transactions processed by each Bill Run increases, especially if it involves integration to a tax engine.

Optional micro-batch payment runs

The Zuora Parallel Processing Engine uses a micro-batching technique to allow parallel generation of payments, that can help shorten payment run times. Payments within a payment run are automatically grouped into smaller batches for greater throughput.

To improve the payment run performance through multi-threading support, the number of concurrent threads enabled must be more than the number of concurrent payment runs configured for your tenant.

This impacts the initial creation of the payment, and impacts payment processing against your payment gateways.

Contact your payment provider to ensure the payment gateway can take advantage of the increased concurrent limit thresholds. For the gateway to provide the required number of concurrences, you must work backwards from your expected payment volumes per day.

Higher API concurrency limits

Increased API concurrency limits allow companies to scale sign-ups and other customer operations per second. This upgrade does not apply to Data Query API operations by default. If you want to enable this upgrade for Data Query, contact your Zuora account representative. The maximum allowed limit is up to 10, subject to evaluation. The actual limit may vary based on your tenant configuration.

Optional higher data query queued queries limits

After reaching the maximum number of simultaneous queries, this feature allows you to achieve an increased queue size. This means that queries can be queued and prioritized for processing, ensuring that none are rejected due to capacity constraints. This upgrade is not enabled for your tenant by default. If you want to enable this upgrade, contact your Zuora account representative.The maximum allowed queue size is up to 50, subject to evaluation. The actual limit may vary based on your tenant configuration.

Optional dedicated workflow workers

Zuora provides always-available resources to support high-priority processing and lower in-queue wait times.