Before you begin

Confirm the following before creating a Revenue workflow:

• Your tenant has Zuora Revenue enabled.

• Your tenant is on the 2026.Q3.0.1 release or a later release that includes Revenue support in Workflow.

• You have access to Extension Studio and Workflow.

• The Revenue configuration required by the task is complete. For example, a task that applies a hold requires an applicable Revenue hold definition, and a task that releases or defers revenue requires the target performance obligation to support the operation.

• You understand the accounting impact of the Revenue operation you are automating. Test workflows in a non-production tenant before enabling them in production.

Workflow entitlement and licensing

Workflow entitlements and licensing for Zuora Revenue follow the same rules as those for Zuora Billing.

For customers that use both Zuora Billing and Zuora Revenue, the entitlement is 15 active workflows in total across Billing and Revenue. This entitlement is shared between the two products. It is not 15 active workflows for Billing plus 15 active workflows for Revenue.

Supported customer configurations

Workflow is supported for both OTR customers and Revenue-only customers. Workflow is not supported in the following tenant configurations:

• One Billing tenant connected to multiple Revenue tenants.

• A multi-entity Billing tenant connected to one Revenue tenant.

Recommended workflow controls

• Add a validation step to confirm that the source and target belong to the expected tenant, entity, book, and accounting context.

• Add a failure branch that captures the Revenue error, identifiers, and workflow run ID. Do not continue to downstream mutation tasks after a failed Link/Delink operation.

• Add comments where the task exposes them so the reason for the realignment is retained in the operational history.

• Remember that a manual delink makes the RC ineligible for systematic grouping rules thereafter.

Important considerations

• Revenue tasks automate supported Revenue operations; they do not make every action available in the Revenue UI available as a Workflow task.

• Eligibility rules configured in Revenue still apply. A task can fail or be unavailable when the target contract, POB, line, hold, book, or accounting state does not support the requested action.

• A successful Workflow task does not replace Revenue approvals, accounting controls, or period-close procedures.

• Use comments, approval steps, and notifications for operations that change revenue recognition, holds, allocations, or accounting data.

• Review task output and run history after each production rollout. Use the task payload and Revenue identifiers to troubleshoot failures.