2026.Q1 release
Learn about new features, changes, fixes, and deprecations delivered in a product release and release updates for Zuora Billing, CPQ, Payments, Platform, Revenue, and Zephr.
Zuora publishes release notes in advance of delivery to sandbox environments to allow additional time to review and test new and changed features before they are released to production environments. These release notes are subject to changes and additions after publishing. Any changes or additions that occur after the initial publish for a particular release version are noted with a date in the Updated column in each release note table.
Customer-impacting changes delivered after the initial major release, as part of minor or patch releases during the quarter, are also added to the release notes. The minor and patch release notes are listed in order starting from the most recent release version at the top of each table. The specific minor or patch release version is noted in the Updated column. An empty Updated column indicates that the release note applies to the major release and was not added or changed after the initial publish date.
AI in Zuora
Lists release notes for features that apply AI in Zuora in 2026.Q1 product release.
AI and Automation (Beta)
We are expanding Zuora AI capabilities with several new features available in beta with the 2026.Q1 release. These features are currently available in sandbox environments only and require enablement via a support ticket. Customers may need to join a waitlist depending on feature availability.
Additional AI-powered features will be added throughout the quarter as we continue to expand AI capabilities across the Zuora platform.
|
Feature |
Description |
Updated |
|---|---|---|
|
Zuora MCP server |
The Zuora Model Context Protocol (MCP) server enables AI assistants like Claude to interact directly with your Zuora environment. This integration allows natural-language queries and actions across your subscription data, billing operations, and reporting. Learn more and access the MCP server at npmjs.com/package/zuora-mcp. | |
|
Billing Operations agents |
AI-powered agents assist with common billing operations tasks, helping teams to automate routine workflows and accelerate resolution of billing inquiries. These agents understand subscription context and can guide users through complex billing scenarios. | |
|
Narrative summaries |
AI-generated narrative summaries provide clear, natural language descriptions of subscription data, billing documents, and key metrics. These summaries make it easier to understand complex subscription states and communicate insights across your organization. |
To learn where and how AI is currently used in Zuora products, see Use of AI in Zuora.
Billing
Presents release notes and resolved issues for Zuora Billing in 2025.Q4 product release.
New and changed features
| Feature | Description | Updated |
|---|---|---|
|
Orders and Subscriptions |
We have enhanced the following GET subscription REST API end points to include the ramp information of a subscription:
| |
|
Orders and Subscriptions |
You can now track, log, and report changes of the following business objects in Audit Trail:
| |
|
Orders and Subscriptions |
You can now view the negotiated price table for usage charges directly within the order or subscription UI. | |
|
Orders and Subscriptions |
We have enhanced the Orders API to support hard bundles. When subscribing to a new hard bundle, optional charges can be added on demand now. These charges can be removed as needed during amendments. Note:
This feature is in the Early Adopter phase. If you want to have access to the feature, submit a request at Zuora Global Support | |
|
Invoicing and Tax |
We are pleased to announce that E-Invoicing with PEPPOL Extract is now Generally Available (GA). The PEPPOL Extract feature allows you to build a custom e-invoicing integration by exporting invoice data from Zuora in PEPPOL-compliant XML format. It is one of two e-invoicing options offered by Zuora, alongside integrations with certified e-invoicing partners. With PEPPOL Extract, Zuora supports the export of billing documents in PEPPOL BIS 3.0 format, enabling you to consume standardized XML files and integrate seamlessly with your own third-party systems. This standardized approach reduces implementation effort by minimizing manual field mapping between Zuora and external vendor platforms. | |
|
Invoicing and Tax |
The Sovos E-Invoicing integration now supports Poland, helping you comply with the Krajowy System e-Faktur (KSeF) clearance e-invoicing requirements. Zuora provides prebuilt e-invoice templates and response field mappings aligned with KSeF specifications, reducing setup effort and minimizing the need for custom configuration. Currently, these templates support invoices only. Support for credit memos and debit memos will be added in a future release. | Added: January 12, 2026 |
|
Invoicing and Tax |
We have enhanced the E-Invoice experience by adding a Re-Sync option for invoices in a Failed status. Previously, only the Re-Generate action was available, which limited flexibility when addressing failures. In some cases, Sovos may automatically correct the failure on their end, allowing Zuora to successfully re-sync the document without requiring a full regeneration. With this enhancement, you can now choose whether to re-sync or regenerate based on the specific failure scenario, improving efficiency, reducing unnecessary invoice regenerations, and providing greater control directly within the UI. | |
|
Invoicing and Tax |
The Resync E-Invoice Status function has been enhanced to give you more control over how e-invoice notifications are retrieved and processed. When resyncing for Sovos, you will now be prompted to choose whether to refresh only the latest unacknowledged notifications (default) or to perform a full re-sync that reprocesses all notifications from the beginning—useful when incremental requests return incomplete results, such as after recreating notifications in Sovos. This enhancement improves reliability when deriving the latest e-invoice status. Note: The mode selection is available only for Sovos; Avalara continues to resync without user prompts.
| |
|
Invoicing and Tax |
Zuora now supports resyncing Avalara E-Invoice statuses when polling times out, preventing invoices from being incorrectly marked as failed. Instead of forcing a re-submission, which can cause document already exists errors, timed-out invoices now move to a new RetrieveTimeOut status with clearer error messages. You can safely trigger Resync E-Invoice status from the UI or API whenever the status is RetrieveTimeOut or Processing. The system will then continue polling until the invoice reaches Success, Failed, or ApprovedByTaxAuthority. This enhancement provides smoother handling of delayed tax authority responses and avoids unnecessary resubmissions. | |
|
Invoicing and Tax |
The Configurable Invoice Grouping feature provides greater flexibility and control over how subscriptions, rate plan charges, and Order Line Items (OLIs) are grouped on invoices and credit memos. With this capability, you can define custom invoice grouping rules using standard or custom fields, enabling invoice structures that better align with your business, operational, and reporting requirements. You can also configure a default invoice grouping that is automatically applied across all accounts. Grouping logic can be driven by standard or custom fields from objects such as Subscription, Rate Plan Charge, and Order Line Item, ensuring consistent, predictable invoice generation throughout your billing processes. | |
|
Invoicing and Tax |
Invoice Schedules and Invoice Schedule Items now fully support the Multi-Org feature. With this enhancement, the organizationLabel field is available across the REST API, Data Sources, and Data Query for tenants with Multi-Org enabled. When a new Invoice Schedule is created, it automatically inherits the organization of the related account, ensuring accurate alignment and improved reporting in Multi-Org environments. Historical Invoice Schedule records created prior to this enhancement do not contain an organization value and remain accessible to all users; customers can update these records as needed by running a data-labeling migration using the Data Labeling Job API. | |
|
Invoicing and Tax |
The Split Invoice feature has been enhanced with a new Split invoice status. This replaces the previous behavior of deleting or canceling the original invoice after it is split. With this enhancement, the original invoice is retained as a non-payable, zero-value record for reporting and audit purposes, while the newly created split invoices reference and reuse its related data. Invoices in Split status are read-only for standard invoice actions; you cannot post, cancel, or reverse them. However, you can still edit custom fields and notes on invoices in Split status. When canceling split invoices, they are treated as a single group. Canceling any split invoice will automatically cancel all related invoices, including the original invoice. | |
|
Invoicing and Tax |
Bill Run Advanced Filters now support dynamic date variables, allowing date-based filter conditions to be evaluated at runtime for both scheduled and ad hoc bill runs. With this enhancement, you can reference the following built-in date variables in bill run filters:
These variables can be compared against any standard or custom date-type field using supported comparison operators, including:
This capability enables more flexible and automated billing scenarios. For example, selecting subscriptions or charges based on when they are ready to be billed, with dates dynamically determined at the time the bill run executes. As a result, bill run filters are more accurate, adaptable, and easier to maintain as business needs change. Note: This functionality is currently available through the API only.
| |
|
Invoicing and Tax |
Zuora has improved tax calculation consistency to prevent unnecessary zero-amount credit memos from being generated during invoice creation. Previously, differences between how redistribution (unrounded tax) and grouping (rounded tax) handled tax amounts could cause zero totals to be incorrectly pushed into credit memos. With this enhancement, invoices and credit memos are now generated more accurately, eliminating unwanted zero-amount credit memos. As a result, your billing documents are cleaner, more predictable, and better aligned with your billing rules. | |
|
Invoicing and Tax |
We have improved the bill run retry experience by extending support for advanced filters during retries. Previously, only error-based filters were applied when retrying a bill run. With this enhancement, any advanced filters used in the original bill runsuch as subscription or charge filters are now automatically carried over to the retried bill run for better consistency and control. When a bill run is retried, Zuora will continue to use the failed account list from the original bill run. The account filter will appear empty in the UI for reference, while the retry correctly targets only the accounts that failed previously. This update ensures greater transparency by displaying both the advanced filters and the retried failed accounts in the UI, giving you a clearer and more accurate view of how your bill run is being retried. | |
|
Invoicing and Tax |
Zuora now supports the Anrok Sales Tax Connector in the Tax Engine. Anrok is a global tax engine designed for SaaS and e-commerce businesses that automates real-time sales tax and VAT calculations to help maintain compliance across multiple jurisdictions. The connector is built on the Global Tax Hub, supports both Simple Mode and Advanced Mode, and follows the same configuration experience as other Global Tax Hub tax engines. With the Anrok Tax Engine, you can:
| |
|
Invoicing and Tax |
Zuora now provides a configurable Tax Void Call Handling option in the Tax Engine UI, allowing you to control how tax void calls are handled during transaction processing. The option is available in a new General Settings section, located after Basic Information, and is always available regardless of whether the tax engine is configured in Simple Mode or Advanced Mode. For new tax engine instances, the default value is Enabled. The supported options are:
The General Settings section is available for tax engines using the new Tax Engine UI, including Vertex Advantage Tax V2, ONESOURCE Indirect Tax Determination V2, and Anrok. For Avalara Direct Integration, this option is not configurable and is always set to Enabled. | |
|
Invoicing and Tax |
Zuora Billing now supports a new Use On-Demand or On-Premise Deployment toggle in the Setup New Tax Engine screen ( ). When enabled, you can configure custom API URLs for tax-related calls. Enabling this option exposes a Tax Calculation URL field, which Zuora applies to tax preview, tax void, and related API calls. When disabled, Zuora uses the vendor’s standard API URLs. | |
|
Product Catalog |
Zuora now provides a Pricing Waterfall view for Dynamic Pricing, allowing you to view the step-by-step breakdown of how a final price is derived. The waterfall shows each pricing layer applied such as the base price, dynamic price (such as segment-based, attribute-based, or negotiated pricing), formula-based adjustments, and discounts, when defined and when qualification criteria are met to fetch the price. This feature increases transparency, helps you troubleshoot and validate pricing behavior, and provides a consistent framework for understanding and optimizing complex Dynamic Pricing configurations. | |
|
Product Catalog |
You can now create hard bundled product offerings by combining multiple products, their component rate plans, and selected charges into a single bundle. The bundle includes the charges, features, and entitlements from its component rate plans, while allowing you to update pricing at the charge level for charges included in the bundle. With this new enhancement, you can:
| |
|
Usage and Rating |
You can view Dynamic Usage Charges (DUCs) directly on the account UI to improve visibility into usage-based billing. From the new Fields Mappings for Dynamic Usage Charges settings page under Billing Settings, you can use a single configuration to map usage record custom fields to Dynamic Usage Charge custom fields so that key attributes flow consistently from usage to DUCs when they are generated. The same configuration also controls the DUC generation rule: DUCs are grouped and created by the same account, the same product rate plan charge, and the same mapped field values, so that different mapped values result in multiple DUCs. | |
|
Usage and Rating |
Zuora is introducing a new capability in our Consumption Billing solution: Flexible Commitment. You can create a minimum spend agreement at the account and product level while supporting modern recurring and usage models. With Flexible Commitment, you can:
This feature is in the Early Adopter phase. If you want to have access to the feature, submit a request at Zuora Global Support. |
Billing 2026.Q1 fixes
There are currently no fixes reported for Zuora Billing in 2026.Q1.
CPQ
Lists release notes and resolved issues for Zuora CPQ in 2026.Q1 product release.
New and changed features
There are currently no new or changed features reported for CPQ in the 2026.Q1 release.
CPQ 2026.Q1 fixes
There are currently no fixes reported for CPQ in the 2026.Q1 release.
Payments
Lists release notes and resolved issues for Zuora Payments in 2026.Q1 product release.
New and changed features
| Feature | Description | Updated |
|---|---|---|
|
Payments |
Zuora Payments now supports network tokens for customer‑initiated (CIT) card transactions submitted through HPF/HPM 2.0 and card‑storing APIs for the WorldPay 1.4 and Stripe v2 gateway integrations. For CIT flows, Zuora generates and sends a one‑time cryptogram together with the network token to the gateway, in line with card‑network and Cybersource VAS API requirements. | |
|
Payments |
Zuora Payments now handles UnionPay 3DS enrollment‑check errors from the FatZebra gateway more gracefully, allowing the system to proceed to payment or validation instead of failing the transaction when this specific 3DS check returns an error. | |
|
Payments |
Zuora has added Organization ID as a payment condition in Gateway Routing to support multi‑org customers that segment traffic by organization within a single tenant. This change is important if your organization requires to route transactions based on Account.OrganizationId | |
Payments | Zuora has extended consent management for bank transfer payment methods (ACH, SEPA, PAD, and phase‑2 BACS) by standardizing how mandate consent is stored and managed across payment types. This work aligns bank transfer mandates with the same Stored Credential Profile (SCP) framework used for cards and wallets. | |
Finance | The financial period end management process has been enhanced to provide greater visibility during the period close. This can be enabled as a tenant level setting with additional setup required. As a part of the setup, you can set the effective starting date for the enhanced experience. |
Payments 2026.Q1 fixes
There are currently no fixes reported for Zuora Payments in 2026.Q1.
Platform
Lists release notes and resolved issues for Zuora Platform in 2026.Q1 product release.
New and changed features
| Feature | Description | Updated |
|---|---|---|
|
Data Loader |
Data Loader now supports a feature template compatible with the SOAP API feature object. | |
Data Loader | The Single Action - Create Subscription With New Account in Data Loader now supports the Communication Profile ID and Batch fields for both import and update operations. | This feature was rolled back to 2025.Q4.1.2 release. |
|
Events and Notifications |
The former tenant-level callout setting "Confirm success by parsing response content" has now been moved to the callout-template level. This enhancement provides more granular control and greater flexibility in managing callout notification retires. For existing callout templates, your previous tenant-level setting is used as the default value. | |
|
Events and Notifications |
The following events and their corresponding default email templates are now available for the Mediation feature: Event Store Query Status Changed Meter Session Periodic Status Update Meter Session Status Change
These events help you better monitor and automate your mediation workflows. | |
|
Events and Notifications |
A new Callout Template column is now available in the Callout History table in the Zuora UI. This enhancement makes it easier to identify and access the callout template associated with each callout notification history. | |
Integration Hub | Zuora now supports sub‑partitioning within child object mappings in Integration Hub, allowing you to divide a single child mapping into multiple nested partitions using the same partitioning concepts previously introduced for SAP mappings. | |
Integration Hub | Zuora has migrated the Salesforce CPQ connector from the legacy Tray.io backend to the new Integration Hub framework, improving scalability and enabling stronger governance for connector configuration. | |
Integration Hub | Integration Hub now supports source data filters that let you control whether a record is eligible to be synced at all, so you can restrict synchronization to only the data that matters for your Zuora use cases. For example, you can configure the Salesforce connector so that only Accounts or Contacts tied to orders are synced to Zuora, instead of syncing every CRM record such as general sales contacts. | |
Mediation | The new Manage Connections UI lets you create, activate, and reuse HTTP connections for the HTTP Processor. This removes the need to raise Zuora Support tickets to add URLs for new connections. | |
Mediation | A new AI-powered code editor has been introduced in Mediation processors that lets you generate and refine JavaScript or Python code using natural-language prompts. The code editor can make improvements to speed up building and troubleshooting custom transformations. This feature is in the Early Adopter phase. If you want to have access to the feature, submit a request at Zuora Global Support. The AI code editor is in an initial phase and can provide incorrect results in some cases. Please check the output before using it in your setup. | |
Mediation | New mediation business events are now available in the Events and Notifications framework. These include Meter Session Status Change, periodic meter status updates, and Event Store query status events. You can configure e-mail, callout, or in-app notifications to be triggered when a meter session’s status changes, at scheduled intervals of a meter run, or when Event Store queries succeed or fail. | |
Mediation | You can now query events within an event store using SQL-style asynchronous APIs to validate ingestion, troubleshoot usage issues, and perform any reconciliation. The API supports ad-hoc queries on event stores with pagination and metadata, designed for debugging and QA rather than bulk analytics. | |
Zuora Protect | GDPR controls in OneID are enhanced to support centralized, organization-level management of PII data across Zuora applications. Organization Admins can manage GDPR and PII settings centrally in OneID, choose whether to retain or anonymize PII across OneID and connected Zuora applications, and automatically anonymize PII when a user is deactivated by enabling the User Deactivation PII Policy under Admin Settings in OneID. | |
|
Zuora REST API |
The following response headers related to concurrency limits are now included in all Object Query HTTP responses:
Object Query and Quickstart API requests use a dedicated Object Query concurrency limit type. By default, each tenant has a concurrency limit of 80 for this limit type, calculated independently from other request types, such as Default and High-volume transactions. This enhancement makes it easier to monitor and manage Object Query API usage and avoid concurrency-related request failures. | |
|
Zuora Reporting |
Zuora Reporting now supports Megastore‑backed data sources that allow application teams to build high‑performance analytical datasets for large‑scale reporting. This capability enables application teams to register new data sources in Megastore, define data cubesfor their datasets, and reuse the existing SQL DAG infrastructurein Zuora Analytics to transform raw transactional data into optimized analytical structures for reporting. | |
Zuora Connectors for Warehouses | Delta Lake is a new addition to our existing set of 16 data warehouse connectors. It allows you to seamlessly connect and integrate your Zuora data into a Delta Lake–based destination through a simple, one-time setup. This connector is currently available as an Early Access paid add-on and supports 12-hour and 24-hour latency options. At this time, it supports Zuora Billing objects. | |
Zuora Connectors for Data Warehouses | We've enhanced the Status tab in the Integration Hub UI for all Zuora Data Warehouse connectors to provide improved visibility into connector health and data transfers. You can now monitor daily sync status, view detailed activity logs, including synced objects, transferred rows, and latest update timestamps, and track transfer progress in real time. In the event of partial failures, failed objects and error details are clearly identified, making troubleshooting faster and easier. |
Platform 2026.Q1 fixes
There are currently no fixes reported for Zuora Platform in 2026.Q1.
Revenue
Presents release notes and resolved issues for Zuora Revenue in 2026.Q1 product release.
New and changed features
| Feature | Description | Updated |
|---|---|---|
Manual journal entries enhancement | Zuora Revenue now allows creation of manual journal entries at the Revenue Contract (RC) level without requiring linkage to any transaction line within the contract. |
|
Revenue 2026.Q1 fixes
For the list of resolved issues, see in the Support Center. Additional logon information may be required to access the Zendesk portal.
Zephr
Presents release notes and resolved issues for Zephr in 2026.Q1 product release.
New and changed features
| Feature | Description | Updated |
|---|---|---|
AI Paywall | The AI Paywall decision node in Zephr’s Rules Builder is now configured per site, rather than as a single global configuration. Each Site can define its own AI Paywall node, allowing you to tailor AI-driven paywall behavior to individual brands, regions, or properties within your Zephr environment. | |
Features | Zephr’s Rules Builder now supports AI-powered queries, enabling you to create and refine rules more efficiently. This enhancement reduces manual effort and accelerates the development of complex logic within Zephr. | |
Features and Component | When saving a new version of a Feature or Component, Zephr can now use AI to summarize the changes from the previous version into a concise description (up to ~250 characters). Zephr also now uses AI to generate feature descriptions, helping you quickly articulate the purpose and benefits of new features and improving clarity for end users. |
Zephr 2025.Q4 fixes
There are currently no fixes reported for Zephr in 2026.Q1.
API
Lists updates on REST API, Quickstart API, and SOAP API in 2026.Q1 product release.
REST API
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.
Quickstart API
Zuora offers two sets of APIs for Billing, Payments, and Platform: the v1 API (the REST API) and the Quickstart API.
Zuora's v1 API provides complete coverage to our Zuora Billing, Payments, and Platform features. Zuora's Quickstart API represents a simplified programmatic experience and a subset of coverage for common e-commerce use cases. While often erroneously referred to as the v2 API, the Quickstart API is NOT a replacement for the v1 API and is no longer recommended for new integrations. See Quickstart API Reference.
Developers who need to access the full breadth of Zuora Billing, Payments, and Platform functionalities should use the v1 API, or our v3 SDKs (v1 for C# SDK) that are built on the v1 API.
SOAP API
Current WSDL version: 154
For more information, see SOAP API.
SOAP API change history
For a summary of updates made to the SOAP API in recent Zuora releases, see Zuora SOAP API Version History.