ZenotiHelp

Debt Recovery β€” Membership Reinstate Gate and Org Validation

ZTZenoti Docs Team Updated September 5, 2026 5 min readGuide

When a staff member attempts to reinstate a cancelled membership, Zenoti checks for any existing debt-recovery claim on that membership before allowing the action to proceed. Separately, when a batch of membership IDs is submitted for debt-recovery processing, Zenoti validates that every ID belongs to the specified organization before any records are created or cancelled. This article explains both behaviors and the steps for performing a reinstatement when a debt-recovery claim exists.

Audience: Front desk staff and administrators who manage cancelled memberships and handle debt-recovery collections.


On this page


Before you begin

  • The guest must have a cancelled membership before reinstatement is applicable.

  • You need the following permissions:

    Permission: Cancel (under Memberships) β€” Required to cancel memberships. Admin path: Configuration > Security > Security roles > [your role] > Marketing Manager > Memberships > Cancel

    Permission: Reinstate (under Memberships) β€” Required to reinstate cancelled memberships. Admin path: Configuration > Security > Security roles > [your role] > Marketing Manager > Memberships > Reinstate

  • To reinstate a membership while a debt-recovery claim is active, the Allow Reinstate While In Collections organization-level setting must be enabled. If it is not enabled, the reinstatement action is blocked. Contact your administrator to review this setting.


Steps

Reinstate a membership when a debt-recovery claim exists

When a staff member attempts to reinstate a cancelled membership, Zenoti first checks whether any non-voided debt-recovery claim exists for that membership, regardless of the claim's current status β€” Active, Released, or Resolved.

Note: A voided claim does not trigger this check. Only non-voided claims cause the evaluation below.

If a non-voided claim is found, Zenoti evaluates the Allow Reinstate While In Collections organization-level setting:

  • If the setting is enabled, reinstatement is permitted and can proceed.
  • If the setting is disabled, reinstatement is blocked. The staff member must resolve the collections situation before the membership can be reinstated.

To reinstate a cancelled membership from the guest profile:

  1. Open the guest's profile page.

  2. Select the Memberships tab.

  3. Locate the cancelled membership and select it to open the membership details.

  4. From the actions available on the membership, select Cancel > Proceed to Cancel is not applicable here β€” instead, look for the reinstatement action. Select the option to reinstate the membership.

    Note: The reinstatement dialog accepts three independent date parameters. Review and confirm each:

    • New expiration date β€” Defaults to the membership's original expiration date.
    • Next scheduled collection date β€” The date on which the next recurring payment will be collected.
    • Annual-fee payment date β€” Applicable only where an annual fee is configured on the membership.
  5. Confirm the reinstatement dates and select Save.

If the reinstatement is blocked because the Allow Reinstate While In Collections setting is disabled, an error is displayed. No partial update is made. Contact your administrator to determine the appropriate next step.

Understand org validation during batch debt-recovery processing

When a batch of membership IDs is submitted for debt-recovery claim creation or cancellation, Zenoti validates that all submitted membership IDs belong to the specified organization before processing any records in the batch.

The validation checks whether the sale center of each membership resolves to the organization specified in the batch request.

  • Memberships whose sale center does resolve to the organization are included in processing.
  • Memberships whose sale center does not resolve to the organization are flagged as not belonging and are excluded from processing.

Important: The batch operation is all-or-nothing at the validation stage only if every record fails. If some records pass and others fail, the valid records proceed and the invalid records are excluded. No partial records are created for flagged memberships.

This validation protects against accidental cross-organization claim creation during bulk operations. Staff performing bulk debt-recovery tasks should confirm that all membership IDs in a submitted batch belong to the same organization before submission.


Tips

  • Check claim status before escalating. If reinstatement is blocked, confirm whether the existing claim is Active, Released, or Resolved. Even a Released or Resolved claim that has not been voided will trigger the evaluation of the Allow Reinstate While In Collections setting.
  • Voiding a claim clears the gate. If the debt-recovery claim is no longer relevant and is voided, the reinstatement gate no longer applies. Coordinate with your collections team to void outdated claims.
  • Verify org alignment before batch submission. When submitting a batch of membership IDs for debt-recovery processing, cross-reference each membership's sale center against the target organization. Mismatched IDs are silently excluded β€” they do not cause the entire batch to fail, but they also do not generate claims.
  • Annual-fee date is only shown when applicable. The annual-fee payment date field appears in the reinstatement dialog only when the membership has an annual fee configured. If you do not see this field, the membership does not have an annual fee component.

Troubleshooting

The reinstate action is blocked even though the membership is cancelled

Symptom: A staff member with the Reinstate permission sees an error when attempting to reinstate a cancelled membership.

Cause: A non-voided debt-recovery claim exists for the membership, and the Allow Reinstate While In Collections organization-level setting is disabled.

Resolution:

  1. Confirm that a debt-recovery claim exists for the membership by contacting your collections administrator.
  2. Determine whether the claim should be voided (if it is no longer valid) or whether reinstatement should genuinely be blocked.
  3. If reinstatement should be permitted despite the active claim, ask an administrator to enable the Allow Reinstate While In Collections setting at the organization level.
  4. If the claim should be voided first, coordinate with the collections team to void it, then reattempt the reinstatement.

Some memberships in a debt-recovery batch were not processed

Symptom: After submitting a batch of membership IDs for debt-recovery claim creation or cancellation, fewer records were processed than expected.

Cause: One or more membership IDs in the batch have a sale center that does not resolve to the specified organization. These memberships fail org validation and are excluded from the batch.

Resolution:

  1. Review the list of submitted membership IDs.
  2. For each excluded membership, verify that its sale center belongs to the organization used in the batch request.
  3. If a membership belongs to a different organization, resubmit it as part of a batch for the correct organization.
  4. If the sale center assignment appears incorrect, contact your Zenoti administrator to review the membership's center configuration.

The reinstatement dialog does not show an annual-fee date field

Symptom: When reinstating a membership, only two date fields appear in the dialog instead of three.

Cause: The membership does not have an annual fee configured. The annual-fee payment date field appears only when an annual fee is associated with the membership.

Resolution: No action is required. Confirm the expiration date and next scheduled collection date, then complete the reinstatement. If you believe the membership should have an annual fee, review the membership configuration in Master data > Memberships.


Was this article helpful?
Your feedback helps us improve our documentation.