Invoicing and Tax

The Sovos E-Invoicing integration no longer requires TLS certificates, making setup faster and easier. You can now choose between TLS or Sovos’s token-based authentication, with certificates remaining optional.

You can manage multiple service providers with or without certificates, update them as needed, and use the new Test Connection button to quickly validate credentials.

To migrate, notify Sovos to update your configuration and then create a new non-TLS service provider in Zuora. This update streamlines onboarding, reduces errors, and improves efficiency.

Invoicing and Tax

We’ve introduced a new billing rule called Rating Detail Generation Timing in both the API and UI. This setting gives you control over when rating details—the full breakdown of charge calculations and billing information—are generated.

You can choose to generate rating details after the invoice is created (the default option, which speeds up invoice processing by delaying rating detail generation), or generate them together with the invoice (the recommended option, if you want them displayed on the invoice PDF).

This enhancement provides greater flexibility in balancing invoice performance and presentation.

Invoicing and Tax

The Sovos E-Invoice integration has been expanded to support Mexico and Brazil, ensuring compliance with local clearance e-invoice requirements.

Zuora now provides pre-built e-invoice templates and response field mappings for both countries, simplifying setup and reducing the need for custom configurations.

This update also introduces cancellation support, allowing you to correct billing documents even after approval by the tax authority. For Mexico, all four SAT-defined cancellation reasons are supported, and cancellations can be triggered through both the UI and API.

Invoicing and Tax

We’ve enhanced the system to let you update the invoice date for all draft invoices—whether created manually or through bill runs—directly in the UI. This ensures consistent behavior across the UI and API, making it easier to correct invoice dates before finalizing.

Invoicing and Tax

We've improved Zuora's PDF generation process to make it more reliable and reduce failures. PDFs will now generate successfully even if related data is updated during processing. If those updates are relevant to the document, you can simply re-generate the PDF to include the latest information.

As a best practice, we recommend re-generating PDFs whenever you update invoice-related data that should appear on the document. This ensures your PDFs always display the most accurate and up-to-date details.

Invoicing and Tax

We’ve enhanced invoice generation for commitment billing to improve accuracy and reliability. Invoices now correctly handle commitments, usage, and overage charges without splitting, and true-ups are generated or adjusted only when needed. Negative true-ups are grouped into credit memos following existing rules, and a new bill run option lets you decide whether to include commitment true-ups.

These updates reduce manual corrections and deliver more predictable billing outcomes.

Invoicing and Tax

We’ve enhanced Zuora’s E-Invoice Cancellation feature to give you more flexibility when replacing canceled invoices.

This update simplifies cancellation workflows by removing unnecessary constraints and enabling debit memos as valid replacement documents.

Customers now have more flexibility to stay compliant with local e-invoicing requirements while using the billing processes that best fit their business.

Invoicing and Tax

We’ve enhanced the REST API to support single account billing preview runs.

With this enhancement, customers can easily run previews for a single account, improving performance and usability.

This makes it simpler to validate billing data and invoices for high-volume or complex accounts before finalizing them.

Invoicing and Tax

Zuora now supports using Advanced Custom Fields (created via Object Manager) in the Tax Engine Mapping Formula. Fields from the Account and Sold-To Contact objects can be referenced to create flexible rules, such as routing U.S. transactions to Avalara and non-U.S. transactions to Zuora Tax.

This enhancement streamlines configuration, supports unified product catalogs, and ensures accurate tax processing across regions.

Invoicing and Tax

The State, County, City, and TaxRegion fields on the Contact object now support up to 100 characters, expanded from the previous 40-character limit. This update resolves issues where longer regional names were being truncated.

The enhancement applies across both UI and API when creating or updating contacts, accounts, invoices, and tax engine companies. It also extends to Z-Tax imports, which can now process and store records with longer field values.

By supporting extended field lengths, Zuora ensures more accurate, complete, and consistent customer data across reporting, invoicing, integrations, and tax connectors.

Invoicing and Tax

Zuora now supports the Invoice Group Number (IGN) field in the Invoice data source within Reporting. Previously, this field was only available through Data Source Exports and Data Query.

With this enhancement, you can easily include the Invoice Group Number in reports based on the Invoice object, giving you greater flexibility to track and group invoices directly in Zuora Reporting.

Invoicing and Tax

We’ve optimized the performance of the FilterByRef function in HTML templates when working with standalone custom objects. A standalone custom object is one that isn’t linked to standard Zuora objects like invoices or payments. For example, you might use a standalone object to store Daily Exchange Rates. This optimization enables faster PDF generation.

Note that the improvement does not apply to non-filterable fields or to custom objects that are related to standard business objects.

The optimization does not apply to non-filterable fields or to custom objects related to standard business objects.

Order to Revenue

We've added support for additional fields for 'bill to' and 'sold to' contact information under invoice item and rate plan charge objects within Order to Revenue.

Order to Revenue

Previously, Order to Revenue supported the calculated charge model as a billing-based revenue recognition method. Now, the rate plan charge calculated using the charge model, will function as a standalone billing transaction.

Order to Revenue

You can now map an invoice number to Revenue when creating memo items, as long as the memo originates from the invoice in the field mapping.

Order to Revenue

If a subscription or rate plan charge is deleted, but its associated invoice items or memo items are not, these remaining billing items will now be treated as standalone billing transactions.

Order to Revenue

OTR now handles delete orders/amendments. Booking transactions will set the charge status (Revenue subscription status) to 'void' when synced to Revenue for deleted sales order lines.

Order to Revenue

We have enabled revenue standard fields mapping for FV_ELIGIBLE_FLAG.