Welcome to Zuora Product Documentation

Explore our rich library of product information

Application of Holds

Learn how holds are applied manually, in batches, and automatically during Data Collection, including precedence rules and evaluation differences for RC, line-level, and POB-level holds.

Holds can be applied manually, in batches, or automatically through system routines. Understanding how the system routes these applications is critical for predictable hold management.

Manual application

You can apply holds directly from the Workbench. Manually applied holds always take precedence over system-automated holds, meaning the automated system will never override, remove, or re-evaluate a hold that a user has manually placed.

Manually applying a hold impacts automated processing in two key ways:

  • Coexistence, not override: Manual precedence does not mean a manual hold replaces all auto-holds. A manually applied hold and an automatically applied hold (for different hold definitions) can independently coexist on the same contract/transactions.

  • Line-level exclusions: Manually applying a line-level hold excludes that transaction line from automated line-level criteria hold processing during Data Collection.

Automatic application

During the Data Collection process, the system automatically evaluates and applies holds based on your configured business rules. How the system evaluates these rules depends entirely on the hold level:

  • RC and Line-Level Holds: Processed using standard hold criteria. If a transaction matches the criteria groups defined in the hold setup, the system auto-applies the hold. For Revenue Holds, the system inherently filters out and skips fully recognized lines.

  • POB-Level Holds: Processed using Advanced Rules. The standard hold criteria explicitly ignore POB-level holds. To automatically apply a POB hold, you must link it to a POB template condition rather than using standard criteria groups.

For configuration instructions, refer to Set up holds.