When should a payment be skipped?

A payment can be skipped when it is not relevant for accounts receivable processing. Common examples include:

1. Internal bank transfers - Transfers between company-owned bank accounts

2. Sweep transactions - Automated cash movement between bank accounts

3. Test transactions - Transactions created for validation or testing

4. Non-AR receipts - Receipts that should not be matched to customer invoices

5. Specific receiving bank accounts - Payments received into accounts that should not be processed in Zuora

6. Specific currencies - Transactions in currencies that should not be processed for an account

7. High-value or low-value exclusions - Transactions above or below a configured threshold

What fields can be used to skip payments?

Zuora can skip payments based on the following fields from the bank statement transaction:

• Description — Payment narration or transaction description.

  Supported conditions: Contains, Exact Match, Starts With, Ends With.

• Amount — Payment transaction amount.

  Supported conditions: Equal To, Greater Than or Equal To, Less Than or Equal To, Between.

• Currency — Payment currency.

  Supported condition: Exact Match

• Receiving Bank Account Number — Bank account number into which the payment was received.

  Supported conditions: Exact Match, Starts With, Ends With.

• Payment Mode — Payment method such as ACH, Wire, BACS, etc.

  Supported condition: Exact Match.

• Reference Number — Payment reference number from the bank statement.

  Supported conditions: Contains, Exact Match, Starts With, Ends With.

• Bank Transaction ID — Unique transaction identifier from the bank.

  Supported conditions: Exact Match, Starts With.

Supported skip conditions

Zuora supports the following conditions for identifying payments to skip:

• Exact Match — Skips the payment when the field exactly matches the configured value.

  Example: Currency equals USD.

• Contains — Skips the payment when the field contains the configured value.

  Example: Description contains sweep.

• Starts With — Skips the payment when the field starts with the configured value.

  Example: Reference number starts with TEST-.

• Ends With — Skips the payment when the field ends with the configured value.

  Example: Bank account number ends with 1234.

• Greater Than or Equal To — Skips the payment when the amount is greater than or equal to the configured value.

  Example: Amount is greater than or equal to 50000.

• Less Than or Equal To — Skips the payment when the amount is less than or equal to the configured value.

  Example: Amount is less than or equal to 10.

• Between — Skips the payment when the amount falls within a configured range.

  Example: Amount is between 100 and 500.

String-based checks are case-insensitive.

How multiple rules and values are handled?

When two or more rules are active at the same time, Zuora applies them using AND logic. This means the payment will be skipped only when all active rules match the bank statement transaction.

Example:

• Rule 1: Description contains sweep

• Rule 2: Currency equals USD

Result: The payment will be skipped only if the description contains sweep and the currency is USD. If only one of the rules matches, the payment will not be skipped.

What happens when a payment is skipped?

When a transaction matches a skip rule, they are excluded from the normal payment creation flow.

1. Zuora creates an unprocessed payment record.

2. The skip rule is evaluated.

3. If the rule matches, the transaction is marked as Skipped.

4. A payment record is not created.

5. The skipped transaction does not proceed to cash application or ERP posting.

What happens when no skip rule matches?

If no active skip rule matches the transaction, Zuora continues processing the transaction as usual. The payment is created and becomes available for matching, application, and posting based on the configured cash application workflow.