Orders and Subscriptions

Zuora now calculates the auto-renewal order date using the tenant's configured time zone at the time the renewal is triggered, instead of the UTC term start date for auto-renewed subscriptions. This ensures the order date matches the tenant's local calendar date for the auto-renewal event.

2026.Q1.2.1

Added: April 7, 2026

Invoicing and Tax

Zuora has enhanced how Configurable Tax Apps populate Account VAT ID and Account Company Code during tax calculation.

With this update, when SoldTo or ShipTo is specified on Subscriptions, Order Line Items (OLIs), or Standalone invoice with a different owner account, the system now sources tax-related fields from the specified SoldTo or ShipTo owner account. This ensures that accurate tax exemption and company information is sent to your tax vendor.

2026.Q1.2.0

Invoicing and Tax

Zoura has strengthened Multi-Org access controls to ensure that split invoices adhere to organization-level visibility rules.

You can now access split invoices and split invoice items only if they belong to organizations within your assigned org structure. Multi-Org security restrictions are consistently enforced across relevant API endpoints, ensuring proper data isolation and alignment with your organization’s access policies.

This enhancement improves data security and ensures consistent Multi-Org behavior across invoice-related objects.

See Split invoices overview.

2026.Q1.1.0

Invoicing and Tax

You can now view the PDF generation status directly on the Invoice Detail page in the Zuora UI, providing clear visibility into invoice PDF readiness without relying on API calls. The status indicates whether PDF generation is N/A (disabled or not applicable), Pending (accepted but not started), Processing, Generated, or Failed.

When PDF generation fails, the UI surfaces the error code and error message to support faster troubleshooting. This enhancement reduces uncertainty and manual effort, allowing you to confidently confirm PDF availability directly from the UI.

See Invoice details view.

2026.Q1.0.0 planned 2nd sandbox update

Added: January 27, 2026

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. These templates support all document types including invoice, credit memo, debit memo.

See Country-specific configurations in Sovos for Poland.

2026.Q1.0.0 planned 2nd sandbox update

Added: January 27, 2026

Orders and Subscriptions

We have enhanced the following GET subscription REST API end points to include the ramp information of a subscription:

• Retrieve a subscription by key

• Retrieve a subscription by key and version

• List subscriptions by account key

Orders and Subscriptions

You can now track, log, and report changes of the following business objects in Audit Trail:

• Fulfillment Item

• Rate Plan

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.

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.

See E-invoicing with PEPPOL Extract.

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.

See E-Invoice statuses.

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.

See E-Invoice statuses.

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.

See E-Invoice statuses.

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.

See Configurable Invoice Grouping.

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 and Data Sources 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.

See Split invoices overview.

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:

• {{BillRunDate}}
• {{TargetDate}}
• {{InvoiceDate}}
• {{Today}}

These variables can be compared against any standard or custom date-type field using supported comparison operators, including:

=, <>, <, >, <=, and >=.

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.

See Custom filter creation through Bill Run Advanced Filter.

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.

See Custom filter creation through Bill Run Advanced Filter.

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:

• Set up, modify, and manage tax configurations directly in Zuora, providing a streamlined onboarding and configuration experience.

• Maintain security and flexibility through default field mappings provided by Zuora, with the ability to customize mappings based on business needs.

• Monitor and maintain tax configurations using System Health, helping ensure stability and accuracy in your tax setup.

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:

• Enabled (default) - Allows the call to proceed and either processes tax or returns an error.

• Pass Through - Allows the call to proceed without processing tax.

• Block - Prevents the call from proceeding and returns an error.

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 (Settings > Billing > Setup Tax Engine and Tax Dates ).

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:

• Select multiple component Plans to form a new bundle.

• Automatically apply the bundle’s Effective Date, set to the earliest expiring date among selected Plans.

• Inherit each component charge into the bundle using the default naming pattern: Bundle Plan Name + Original Charge Name.

• Override prices (percentage or fixed amount).

• Update default quantities.

• Include or exclude charges.

• Remove charges.

• Add new charges.

• Include or exclude charges from specific component Plans.

  Note:

  This feature is in the Early Availability phase. If you want to have access to the feature, submit a request at Zuora Global Support.

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:

• Set a postpaid minimum spend.

• Apply the commitment across accounts and products.

• Configure the commitment schedule and amount by month, quarter, year, or custom date ranges.

• Charge customers a true-up invoice if their consumption falls short of the committed amount to enforce a baseline revenue.

This feature is in the Early Adopter phase. If you want to have access to the feature, submit a request at Zuora Global Support.

Order to Revenue

Improved handling of regenerated transactions:

We have improved how Zuora identifies and processes regenerated transactions to ensure the most recently updated transaction is always used, reducing inconsistent results during data collection.

Order to Revenue

Order to Revenue now supports booking-based revenue recognition for Calculated Charges.

2026.Q1.0.2

Order to Revenue

The hard bundles feature is supported in Order to revenue.

2026.Q1.0.1

Added: February 9, 2026

CPQ X

Salesforce users can now suspend and resume subscriptions in Quote Studio by initiating these actions from the Billing Account Selector page and configuring suspension and resumption dates eliminating the need to navigate to Zuora Billing. For more information, see Suspend and Resume subscriptions in Quote Studio.

10.57

CPQ X

Added a new toggle Show Removed Products in Quote Studio, that allows you to control the visibility of removed products in amendment and renewal quotes. For more information, see Removed products.

10.57

CPQ X

Enhanced the Quote Studio Display Scale Settings to support Quote Order Line Item fields. You can now configure display scale for Effective Price, List Price, and Discount under the Order Line Item section.

10.57

CPQ X

Enhanced the subscription selection flow for amendment and renewal quotes by optimizing the prepaid balance data handling. The prepaid balance indicator has been removed from the selection page, and prepaid data is now retrieved only for relevant subscriptions instead of all subscriptions under an account. This reduces data fetching and improves performance, especially for accounts with a large number of subscriptions.

10.57

CPQ X

Improved the performance of saving quotes in Quote Studio for Single Subscription Quoting (SSQ) with a large number of products. Previously, the full quote payload was sent from the client to the server in a single request. It is now processed in batches, similar to Multi Subscription Quoting (MSQ), reducing the size of each request.

10.57

CPQ X

To prevent conflict, the Back button is disabled when the custom components from the sidebar are open.

10.57

CPQ X

Enhanced the Single Subscription Quoting flow to use the Async Orders API for order and subscription creation when quotes contain more than 50 order actions. Previously, only the preview call used async processing. Now the submit (Send to Zuora) flow now also uses async processing for large quotes, improving reliability and preventing timeouts.

You can track async processing status directly on the quote using the following fields:

• SSQ Async Job Id (zqu__SSQ_AsyncJobId__c)
• SSQ Async Job Status (zqu__SSQ_AsyncJobStatus__c)
• SSQ Async Job Error (zqu__SSQ_AsyncJobError__c)

10.57

CPQ X

• This feature requires Ship To Contact support in the connected Zuora tenant. An error is displayed if the tenant does not support this functionality.
• The ShipToContact__c field is now available to be added to the following Quote object field sets:
  • zqu__CPQX_SelectBillingAccount_Quote_Info
  • zqu__CPQX_Subscription_Billing
  • zqu__CPQX_Subscription_Owner

10.57

CPQ X

In Quote Studio, product and rate plan search now supports multiple search terms and exact phrase matching, making it easier to find products when you only remember parts of the name or SKU.

Previously, the entire search input was treated as a single string. For example, entering recurring flat would only match names containing the exact phrase "recurring flat". Now, each word is treated as a separate term, and all terms must match (AND logic) across any searchable field.

For details about search behavior and examples, see Configure information on Quote Studio page.

10.57

CPQ X

You can now search for products and rate plans in Quote Studio using numbers that include commas, with the search correctly interpreting comma-separated number formats and returning the appropriate matching results. For example, 100,000 or 1,00,000.

10.57

CPQ X

The global zqu.zQuoteUtil.sendToZBilling method now returns the Zuora subscription ID in zBillingResult.zSubscriptionId when the subscription is created via synchronous Orders processing scenarios with 50 or fewer order actions. For sample code, see Sample code 2.

10.57

CPQ X

Added ramp-specific alignment options for Quote Start Date (QSD) and Term Start Date (TSD) updates in Quote Studio:

• Realign Initial and Future actions aligned to Interval Start Dates to the New Interval Start Dates, Shifting non-aligned actions by the days the TSD changed

• Realign Initial and Future actions aligned to Interval Start Dates to the New Interval Start Dates, Shifting non-aligned actions by the days the QSD changed

• Realign Initial and Future actions at Interval Start Dates to New Interval Start Dates, Shifting non-aligned actions by days between previous and new Interval Start Dates

These options are available in Zuora Config > Quote Studio Settings > Default Settings.

The global method zqu.zQuoteUtilHelper.updateQuoteStartDate has been enhanced to support the new alignment types:

• SYNC_RAMP_QSD_DELTA

• SYNC_RAMP_QSD_INTERVAL_DELTA

For more information, see:

• Default settings
• zQuoteUtil class

10.55

CPQ X

The Ramp Interval Metrics panel in Quote Studio now supports five new fields that aggregate billing totals directly from Charge Segment metrics, providing more accurate interval-based billing visibility for New, Amendment, and Renewal ramp quotes.

To make these fields visible in Quote Studio, administrators must enable Charge Segment Metrics, add the new fields to the Interval Metrics field sets, and update permission sets as needed.

• Ramp Interval Subtotal: Gross total contract billing (Gross TCB) aggregated from Charge Segment metrics within the ramp interval.

• Ramp Interval Total: Net total contract billing (Net TCB) aggregated from Charge Segment metrics within the ramp interval.

• Ramp Interval Discount: The discount amount for the interval, calculated as the difference between the gross subtotal and net total.

• Ramp Interval Delta Subtotal: The gross billing change for the interval, aggregated from Charge Segment delta metrics.

• Ramp Interval Delta Total: The net billing change for the interval, aggregated from Charge Segment delta metrics.

For more information, see:

• Quote Ramp Interval (zqu__QuoteRampInterval__c)
• Quote and Charge Metrics
• Charge Segment
• Charge Segment behavior
• Quote Studio admin settings configuration

10.55

CPQ X

Quote Studio now supports Charge Segment (period-aligned) metrics for New Subscription ramp quotes. Previously, Charge Segment metrics were available only for Amendment and Renewal quote.

With this enhancement, New Subscription ramp quotes now provide more accurate interval-level metric visibility within the charge table.

Previously, for ramp quotes using In Advance billing or misaligned billing intervals, invoice-based metrics could appear primarily in the first ramp interval. Charge Segment (period-aligned) metrics now distribute subtotals and interval metrics based on ramp interval start and end dates, providing a more accurate view of revenue across the ramp schedule.

For more information, see:

• Quote Studio admin settings configuration
• Charge Segment metrics in Quote Studio UI
• Quote and Charge Metrics
• Field set reference

10.55

CPQ X

Enhanced the Dynamic Pricing modal in Quote Studio to display rate card adjustments in addition to the list price.

A new Adjustment row has been added to the Dynamic Pricing table, allowing you to view any adjustment defined in the catalog rate card.

10.55

CPQ X

You can now create Pending subscriptions together with Order Line Items (OLIs) from Quote Studio and send them to Zuora Billing.

Previously, when a quote contained a Pending subscription along with one or more OLIs, only the OLIs were created in the resulting order. The subscription and its related order actions were not created in Zuora Billing.

10.55

CPQ X

Zuora CPQ now supports Hard Bundles with Charge Optionality, allowing sales representatives to select or deselect predefined charges during quoting. This enhancement formalizes a commonly used bundling approach and provides greater flexibility when configuring bundled offerings. For more information, see Hard Bundle in Quote Studio.

10.54

CPQ X

We have added a new custom setting that allows customers to skip execution of the Zuora CPQ managed package triggers on the following Salesforce objects:

• Quote

• Product2

• Contact

This setting allows you to control Zuora CPQ trigger execution and bypass CPQ processing when Zuora CP functionality is not required. For more information, see Configure skipping of Zuora CPQ managed package triggers.

10.54

Payments

Zuora's Checkout.com gateway integration now supports enhanced Level 2 and Level 3 data submission, including Visa Commercial Enhanced Data Program (CEDP) fields, so that B2B merchants can send richer invoice-level information with card payments and qualify for reduced interchange fees when acquirer and scheme requirements are met.

For tenants using Checkout.com, Zuora now populates the CEDP and other L2/L3 fields expected by Checkout.com on eligible transactions, and merchants can work with Checkout.com to validate payloads and confirm end‑to‑end CEDP eligibility for their portfolios.

2026.Q1.2.1

Payments

Zuora's Braintree v2 gateway integration now supports Visa's Commercial Enhanced Data Program (CEDP) for Level 2 and Level 3 transaction data, allowing B2B merchants to send invoice-level details such as line items and tax with card payments so they can qualify for lower interchange fees when CEDP requirements are met.

2026.Q1.2.1

Payments

Zuora has upgraded the BlueSnap Payment Gateway integration's Web SDK used in hosted payment experiences to a newer supported version aligning with BlueSnap's recommendations, ensuring access to current fixes, improvements, and safer future updates. If you enforce a Content Security Policy, you must add .cardinalcommerce.com and .cardinaltrusted.com as allowed sources so the updated SDK can load 3-D Secure components correctly.

2026.Q1.2.0

Payments

Zuora has updated the Chase payment gateway integration (Orbital) to calculate and submit Level 2 and Level 3 card data in accordance with Visa's Commercial Enhanced Data Program (CEDP) rules for Visa transactions. When Level 2/3 data is enabled, the following actions are performed:

• Applies Visa CEDP formulas to item, tax, discount, partial/negative line item, and rounding calculations.
• Dynamically sends only the required Level 2/3 fields per card network (Visa, Mastercard, Amex).
• Automatically retries eligible transactions with Level 1 data if Level 2/3 submission fails.

This ensures that eligible Chase transactions can continue to qualify for Visa CEDP interchange benefits. Contact Zuora Global Support to enable this feature on your sandbox and production environments.

2026.Q1.1.2

Payments

Zuora has enhanced the CyberSource payment gateway integration (CyberSource Payment API v2.0) to calculate and submit Level 2 and Level 3 card data in compliance with Visa's Commercial Enhanced Data Program (CEDP) requirements for Visa transactions.

When Level 2/Level 3 data is enabled, Zuora performs the following actions:

• Applies Visa CEDP calculation rules to item amounts, taxes, discounts, and rounding adjustments.
• Dynamically includes only the required Level 2/3 data fields based on the card network.

These enhancements help ensure that eligible transactions continue to qualify for Visa CEDP interchange benefits.

To enable this feature in your sandbox or production environment, please contact Zuora Global Support.

2026.Q1.1.2

Payments

For tenants using the EBANX gateway with UPI Mandate, Zuora now automatically closes the corresponding UPI payment method when EBANX reports the mandate as revoked or expired. This enhancement prevents new payments or payment runs from being initiated using that payment method and helps keep the mandate status synchronized between EBANX and Zuora.

No additional configuration is required. Merchants can also use the Zuora API to manually close a UPI payment method and reactivate it later if needed.

2026.Q1.1.2

Payments

Zuora now supports Consent Management as part of the Bank Account Verification (BAV) flow.

This enhancement enables customers to capture and manage user consent when performing bank account verification, improving compliance and auditability for ACH and other bank-based payment methods.

2026.Q1.1.1

Payments

Zuora now supports network token lifecycle management for Worldpay network tokens through Worldpay's Customer Event Service (CES). Payment methods are automatically updated when tokens are provisioned, modified, or deleted, ensuring stored credentials remain in sync without manual updates.

2026.Q1.1.0

Cash Application

Zuora has added support to specify a custom effective date when transferring payments. This aligns transfer behavior with the existing Apply/Unapply operations. It removes the previous restriction that relied on the system-calculated maximum of today and historical payment dates.

2026.Q1.1.0

Added: Apr 07, 2026

Payments

Opayo Direct gateway integration now supports Zero Value Authorization (ZVA) with tokenization. Any new payment method can be validated by ZVA which is then stored as a token in Zuora. Zuora then uses this stored token for all future Opayo Direct transactions.

2026.Q1.0.0

Added: Jan 27, 2026

Payments

Payment Profile fields associated with the Subscription object are now available for querying via Data Source Exports (DSE), AqUa, and the Node SDK.

The following fields are now supported:

• Payment Method ID
• Payment Gateway ID

This enhancement enables easier access to key payment profile data for reporting, analytics, and integrations.

2026.Q1.0.0

Added: Jan 20, 2026

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.

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.

For more information, see Create and Manage Payment Gateway Routing Rules.

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. For more information, see Manage User Consent on Payment Forms.

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.

Mediation

You can now create and manage connections to external Kafka clusters directly in the managed connection flow within Mediation. The Kafka connection type lets you define bootstrap servers, choose the Kafka security protocol and authentication mechanism, configure TLS/SSL truststores and optional keystores, and validate cluster and topic connectivity before activating the connection.

This reduces manual setup and speeds up onboarding for Mediation meters that integrate with external Kafka.

2026.Q1.2.2

Mediation

You can now create and manage connections to Snowflake directly in the managed connection flow within Mediation. The Snowflake connection type lets you define the Snowflake account URL, authentication method, and required connection properties, and then validate connectivity by running a test query before activating the connection. This reduces manual setup and speeds up onboarding for Mediation meters that ingest data from or write data to Snowflake.

2026.Q1.2.1

Zuora SDK

We have released the following version for each of the Zuora client libraries:

• Java: 3.16.0

• Node.js: 3.16.0

• Python: 3.16.0

• C#: 1.8.0

See Changelog for Zuora client libraries.

2026.Q1.2.0

Added: April 2, 2026

Custom Logic

You can now define custom rules to automatically update the following revenue-related fields on the Rate Plan Charge (also known as Subscription Rate Plan Charge) object using the Custom Logic feature:

• ExcludeItemBillingFromRevenueAccounting

• ExcludeItemBookingFromRevenueAccounting

• IsAllocationEligible

• IsUnbilled

• RevenueAmortizationMethod

• RevenueRecognitionTiming

Previously, these fields could not be modified through Custom Logic.

This enhancement gives you greater flexibility to automate and streamline your quote-to-revenue process.

See Rate Plan Charge fields supported by Custom Logic.

2026.Q1.2.0

Mediation

Zuora Mediation now sends only valid pricing attributes to Catalog Dynamic Pricing, passing blank string attributes as-is and dropping blank non-string attributes to avoid errors with partially populated payloads. Mediation also no longer requires all configured Dynamic Pricing attributes to be present, allowing Catalog to use partial attribute sets and fall back to base or default pricing when some attributes are missing.

2026.Q1.2.0

Added: April 2, 2026

Mediation

Python is supported as a basic feature during new provisioning in Zuora Mediation and is available within the code editors of the Advanced Transformer, Advanced Aggregator, and Advanced Accumulator processors. You can now write and run Python scripts directly for standard use cases without submitting a support ticket.

2026.Q1.2.0

Mediation

AWS S3 connections are now available in the managed connection flow within Mediation, and you can use either a Zuora-managed S3 bucket or your own external S3 bucket. Both options are supported out of the box, so you do not need to submit a support ticket to set them up.

This enhancement makes it easier to configure and reuse S3 connections for your meters, while helping you verify that the connection is correctly configured before you start using it in meter flows.

2026.Q1.2.0

Mediation

You can now view a 7‑day history of data prefetch executions directly from the Data Prefetch modal. A new View history action opens a table listing each prefetch run with processor, status, trigger type (manual or automatic), start and completion times, source data timestamp, and any user‑friendly error message or code. You can filter by date, status, and trigger type and use pagination to quickly audit prefetch activity, confirm when data was last refreshed, and troubleshoot enrichment issues for both product/account‑based and Data Query–based prefetch jobs.

See View prefetch history.

2026.Q1.1.1

Mediation

Usage custom fields on the Usage element mapping screen in Zuora Mediation are now sorted alphanumerically (A–Z), making it easier to locate related fields, reduce mapping errors, and work efficiently when you have large numbers of custom fields.

2026.Q1.1.1

Zuora SDK

We have released the following version for each of the Zuora client libraries:

• Java: 3.15.0

• Node.js: 3.15.0

• Python: 3.15.0

• C#: 1.7.0

See Changelog for Zuora client libraries.

2026.Q1.1.0

Added: March 10, 2026

Mediation

You can now override meter source settings at runtime when running meters through the Mediation APIs, without creating new meter versions.

For S3 sources, you can point the same meter to different S3 paths or connections for each run, switch between streaming and batch mode using an incremental flag, and configure batch settings such as monitor interval, retention time, and batch size. Invalid or unsafe overrides are automatically rejected with clear error messages.

For Snowflake sources, you can override the database, schema, table, or SELECT query per run and pass query parameters securely at runtime. The API enforces SQL safety by allowing only single SELECT statements and blocking DDL, multi-statement queries, and disallowed keywords.

For Event Store sources, you can specify a date range (up to a one-year window) or provide an ad hoc SELECT query per run, with the same SQL safety validations.

For uploaded file (LOCAL_FS) sources, you can reference different uploaded file IDs across NORMAL and DEBUG runs while reusing the same meter definition.

Existing meters and UI workflows continue to work as before, and these enhancements are available only through the Mediation APIs.

See Run a specific version of a meter.

2026.Q1.1.0

Data Loader

A new Order Action template has been added to the data dictionary, allowing you to update fields such as change reason and custom fields using the Order Action ID. For more information, see Order Action.

2026.Q1.1.0

Added: March 5, 2026

Integration Hub

You can now monitor Integration Hub connector jobs directly from System Health. A new Integration Hub view shows recent connector executions, including connector name, job type, status, start/end time, duration, and environment, helping you quickly identify failing jobs and start troubleshooting.

Integration Hub also now publishes a standard job-status event to Events and Notifications. You can use this event to:

• Send email notifications when connector jobs complete or fail.
• Trigger callout notifications to external monitoring or ticketing tools, including key details such as connector name, job type, execution ID, status, timings, and error summary.

For setup details, see Monitor Integration Hub connector jobs in System Health.

2026.Q1.0.0

Added: March 05, 2026

Custom Logic

To ensure object parity across custom logic types, the following objects are now supported in each type:

• Decision table and decision tree:

  • Rate Plan Charge (also known as Subscription Rate Plan Charge)

• Function:

  • Order line Item

  • Rate Plan

See Objects and fields supported by Custom Logic.

2026.Q1.0.1

Zuora SDK

We have released the following version for each of the Zuora client libraries:

• Java: 3.14.0

• Node.js: 3.14.0

• Python: 3.14.0

• C#: 1.6.0

See Changelog for Zuora client libraries.

2026.Q1.0.0

Added: January 26, 2026

Custom Logic

When you create or update the following objects in the Zuora UI, error messages triggered by associated custom logic are now enhanced to include the result messages defined in each custom logic, along with a hyperlink to the custom logic list view page:

• Account

• Contact

• Subscription

• Rate Plan Charge (Subscription Rate Plan Charge)

• Invoice

• Credit Memo

• Debit Memo

• Payment

2026.Q1.0.0

Added: January 16, 2026

Data Loader

Data Loader now supports Feature templates compatible with the SOAP API feature object. For more information, see Data Loader dictionary.

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.

See Create a callout template and Callout response codes.

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

• 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.

See Standard events for Zuora Platform and Mediation overview.

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.

See View notification histories.

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 to a 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

You can now configure a Max concurrency limit for the HTTP operator to control how many outbound HTTP calls are executed in parallel per Mediation account (MAX). This advanced setting lets you throttle traffic to downstream services, reduce the risk of breaching external rate limits, and tune throughput for high‑volume flows. When you leave this field at its default value, existing mediation flows continue to behave as before, with no change required. The minimum value that can be set is 1 and the maximum limit is 100.

See Configure a HTTP processor.

2026.Q1.0.3

Mediation

You can now configure the HTTP Operator to skip actual HTTP requests when a mediation flow runs in Test Mode under the operator’s Advanced Configuration. When this option is turned on, the operator does not send external HTTP requests and instead returns a mock response, allowing you to run safe, faster tests without impacting downstream systems.

See Configure a HTTP processor.

2026.Q1.0.3

Mediation

You can now monitor the status of data prefetch while a meter is running, by clicking the Prefetch button. However, the options for manual fetch actions, such as Fetch Again, will remain inactive and not available during the meter run.

2026.Q1.0.1

Added: February 11, 2026

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.

See Manage connections in meters.

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.

See Notifications in Mediation.

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.

See Submit an event store query and Retrieve the results for an event store query.

Mediation

We've introduced a new Empty Sink operator for Mediation that acts as a terminal sink, consuming events and cleanly stopping further processing for that branch without producing output or errors. This is especially useful when using the HTTP operator or similar processors, allowing flows to complete without persisting data to an event store or S3 space. You can use Empty Sink to support scenarios like data validation, enforcing business rules, or debugging by intentionally terminating execution at specific points in your flow.

See Empty Sink.

Added: January 27, 2026

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:

• Concurrency-Limit-Type

• Concurrency-Limit-Limit

• Concurrency-Limit-Remaining

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.

See Concurrent request limits and Object Queries.

Zuora Reporting

A new reporting landing page is now available in the Zuora New Experience to help you more easily discover and navigate reporting capabilities across Zuora. The enhanced landing page improves access to reporting features and supports more efficient reporting workflows.

Zuora is gradually rolling out this update. The classic reporting view will continue to be available for a limited time through a toggle option.

Added: January 14, 2026

Zuora Reporting

Chart visualizations are now available for Summary Reports, making it easier to analyze and understand your data at a glance. You can add configurable charts to summary reports, and charts update dynamically as you modify chart definitions, such as X-axis, Y-axis, or metric selections.

Each chart can display up to two metrics, enabling easier comparisons, and the overall experience is consistent with common business intelligence (BI) tools. In this initial release, the following chart types are supported: Column and Grouped Column, Bar and Grouped Bar, Line and Area, Pie and Donut, as well as Stacked Bar and Stacked Column charts.

Added: January 14, 2026

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.

Deprecation of legacy Revenue sync

Zuora will deprecate Legacy Revenue Sync on February 15, 2027. After this date, Legacy Revenue Sync will no longer be available or supported. If you are still using Legacy Revenue Sync, contact your Zuora account team as soon as possible to plan your migration to Order to Revenue (OTR).

Added: March, 02 2026

Order to Revenue

Improved handling of regenerated subscription data:

Enhanced the subscription data processing in the OTR flow so that Zuora Revenue always uses the most recent data for a subscription, helping ensure accurate and up-to-date revenue results even when updates come from multiple sources.

2026.Q1.1.0

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.

CM-C details inclusion in the Accounting detail report

We've enhanced the Accounting Detail report to improve visibility into credit memo activity and make billing-to-revenue reconciliation more accurate. With this update, you can now identify whether credit memos were system-generated or manually created in billing, and view detailed credit memo references directly within revenue schedules.

The following columns have been added to the Accounting Detail report layout:

• System-Generated Billings: Identifies if the credit memo was system-generated (displayed as "Y" or "System") or manual (displayed as "N" or "Manual").
• Associated Credit Memo Type: Displays the category of the credit memo (e.g., CM or CM-C).
• Credit Memo Number: The unique reference number for the credit memo.
• Credit Memo Line Number: The specific line item sequence within the credit memo.
• Credit Memo Line ID: The unique system identifier for the specific transaction line.

Added: Jan 14th, 2026

OneID

Zephr now integrates with Zuora OneID, allowing you to access all your Zephr tenants using the same unified OneID account used across Zuora applications. This provides a seamless single sign-on (SSO) experience, centralized role and access management, reduced credential maintenance, and a stronger overall security and compliance posture.

Ask your CSE to find out more about the process of migrating your Zephr Admin users to One ID.

2026.Q1.2.0

Billing

Zephr now supports introductory offers with a zero-charge first billing period while still capturing and storing customer payment details for use with Zuora Billing. This enables you to present offers such as “£0 for the first month, then £9.99 per month”, where no subscription charge is taken at sign-up, but the customer’s payment method is validated and securely stored.

After the introductory period, recurring charges automatically begin through Zuora Billing (for example, as merchant-initiated transactions from the second month onward), provided the customer does not cancel.

2026.Q1.2.0

Export

A new asynchronous export capability improves the performance of exporting large user datasets. When enabled, export jobs run in the background and the exported CSV file is uploaded to Amazon S3. After the export completes, a presigned download URL is generated for secure file download.

Email notifications for export success or failure are sent only for exports initiated from the Admin Console.

This feature is controlled by the feature.asyncUserExport.enabled feature flag:

• Enabled - Exports run asynchronously and files are stored in S3.

• Disabled - The existing synchronous export process is used.

See Asynchronous user exports.

2026.Q1.0.3

Features

Zephr now includes stricter validation when saving Feature and Redirect rules. When this option is enabled, the system checks rules for nodes that are not connected to the main rule flow, as well as nodes that may be missing required configuration.

If unconnected nodes are found, administrators are prompted to confirm whether they should be removed before saving. If nodes with missing configuration are detected, administrators are notified and can choose whether to address these issues before proceeding with the save.

This behaviour is controlled by the tenant-level configuration flag console.rules.strictValidation.

2026.Q1.0.3

Features

Zephr now automatically saves in-progress rule edits in the browser, helping prevent loss of work if you navigate away, close a tab, get logged out or encounter a browser issue. Unsaved changes can be restored when you return to the same rule draft or version.

Updated on 13 Feb, 2026

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.

See Get started with Rules Builder.

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.

See Get started with Rules Builder.