ZenotiHelp

Account freeze candidate tracking

ZTZenoti Docs Team Updated August 16, 2026 8 min readGuide

The tips payout platform automatically identifies employee wallet accounts that may need to be frozen due to inactivity or policy triggers, and tracks each candidate through a retry schedule until the freeze is confirmed or the candidate is cleared. This article explains how to monitor freeze candidates and understand the notification and retry behavior that governs the process.

Audience: Tips payout administrators who manage participant freeze status and investigate why an employee's payout has stopped.


On this page


Before you begin

  • Your organization must have tips payout enabled and at least one center onboarded.

  • Freeze operations apply at either the center level or the employee level — these are independent. Confirm which level you are investigating before taking action.

  • You need the following permissions:

    Permission: Configure Payment Settings — Required to view and manage tips payout participant status. Admin path: Configuration > Security > Security roles, then open the role and enable the permission under the Payments group.

  • Freeze candidate tracking is a background process. You cannot manually add or remove accounts from the candidate list through the Zenoti UI. To freeze or unfreeze a participant directly, see Set up Same-Day Tip Payouts for your business.

How freeze candidate tracking works

When the tips payout platform determines that an employee wallet account may need to be frozen — for example, because the employee has become inactive — it creates an internal freeze candidate record for that account holder. The record carries the information the system needs to attempt the freeze and notify the account holder:

  • The account holder's identity details, including their display name, email address, phone number, and phone code, used for pre-freeze notifications.
  • The external account ID and card holder external ID, used to locate the account with the Banking-as-a-Service provider.
  • The BaaS provider associated with the account.
  • The owner reference (a GUID) that links the candidate record to the correct organizational entity.

The system uses this record to drive the freeze attempt and to track whether a notification has already been sent to the account holder.

Note: Freeze candidate tracking is a center-level and employee-level operation. A center being frozen does not automatically freeze individual employee accounts, and vice versa. Always confirm which level is relevant when investigating a specific participant.

Automated freeze triggers

The most common trigger for freeze candidate creation is employee inactivity. Specifically, when an employee's last working date plus two days has passed relative to the center's local time, the system automatically marks that employee as a freeze candidate. If the employee's last working date is later updated to a future date — for example, because the termination was reversed — the system automatically removes the freeze candidate status and restores the employee to active payout eligibility.

Important: Do not conflate tips payout freeze (which stops electronic disbursement via the platform) with tips allocation at the point of sale. Freezing a participant stops future payout transfers; it does not affect how tips are recorded on invoices. For tips allocation and declared cash tips, see Employee Payroll.

Retry scheduling

Because freeze attempts may not always succeed on the first try — for example, if the BaaS provider is temporarily unavailable — the freeze candidate record includes two scheduling fields that the system uses to manage retries:

Field Description
Last attempted The date and time the system most recently attempted to freeze this account. This field is blank if no attempt has been made yet.
Next attempt scheduled The date and time the system will next attempt the freeze. This field is blank if no further attempts are scheduled.

The system updates both fields automatically after each attempt. You do not need to manually trigger retries.

Note: Retry scheduling is managed entirely by the background processing service. The retry interval is determined by system policy and is not configurable through the Zenoti UI.

Payout status during retry cycles

While a freeze attempt is pending or retrying, the employee's payout status reflects the current state of their account. The following status codes are relevant to freeze candidate scenarios:

Status code Label Meaning
7 Employee Opted Out The employee's account has been successfully frozen. Payouts are stopped for this participant.
3 Wallet Inactive / Not Created The employee does not have an active wallet. Distinct from a frozen account — the wallet was never activated or has been closed.
8 Center Payouts Stopped / Business Paused The center's payouts are stopped. This is a center-level status, not an employee-level freeze.

Important: Status 7 (Employee Opted Out) and Status 3 (Wallet Inactive / Not Created) are distinct conditions. An employee with Status 7 had an active wallet that was frozen. An employee with Status 3 never had an active wallet, or their wallet was closed through a separate process. Do not treat these as interchangeable when investigating a participant.

Pre-freeze notification behavior

Before the system freezes an account, it sends a pre-freeze notification to the account holder using the contact details stored in the freeze candidate record (email address, phone number, and phone code). This notification informs the account holder that their account is scheduled to be frozen.

To prevent the account holder from receiving the same notification multiple times across retry cycles, the system tracks whether a notification has already been sent using an internal flag. Once the notification is dispatched:

  • The flag is set to indicate that the notification has been sent.
  • Subsequent retry attempts do not send the notification again, even if the freeze itself has not yet completed.

This means each account holder receives at most one pre-freeze notification per freeze candidate lifecycle, regardless of how many retry attempts occur.

Note: Employee-facing notifications (such as push notifications in the MyZen app) are managed separately from the pre-freeze notification described here. For viewing tips earnings and notifications on the employee side, see MyZen.

What the notification contains

The pre-freeze notification uses the display name, email address, and phone details from the freeze candidate record at the time the notification is sent. If the account holder's contact details change after the notification is dispatched, the system does not resend the notification with updated details — the flag prevents a second send.

Tip: If you need to verify which contact details were used for a pre-freeze notification, check the employee's profile for the email address and phone number that were on record at the time the freeze candidate was created.

Reports

Freeze candidate activity feeds into the tips payout reporting suite. Use the following reports to monitor participant status and identify accounts affected by freeze operations:

Report What it shows Where to find it
Same-Day Tips Adoption Report Enrollment and payout status per employee, including frozen participants (Status 7) Same-Day Tips Adoption Report
View Same-Day Tip Payouts reports Payout batch results, including status codes for each participant in a given payout cycle View Same-Day Tip Payouts reports

When reviewing these reports, filter for Status 7 (Employee Opted Out) to identify participants whose accounts have been successfully frozen. Use Status 3 (Wallet Inactive / Not Created) to identify participants who were never enrolled or whose wallets were closed separately.

Tips

  • Verify the freeze level before acting. Center-level freeze and employee-level freeze are independent. Freezing a center stops payouts for all participants at that center (Status 8), while freezing an individual employee stops payouts only for that person (Status 7). Confirm which level applies before escalating an issue.
  • Check the retry schedule before contacting support. If a freeze attempt has not completed, the next scheduled attempt date indicates when the system will try again. Allow the retry cycle to complete before assuming the freeze has failed.
  • Use the Adoption Report to audit freeze status at scale. If you need to review freeze status across multiple employees, the Same-Day Tips Adoption Report provides a per-employee view of payout status, including frozen participants. Filter by Status 7 to see all currently frozen accounts.
  • Do not confuse freeze with unenrollment. Freezing a participant stops future payouts but does not remove the employee from the tips payout platform. The employee's historical payout records remain accessible in reports. To fully remove a participant, contact Zenoti support.

Troubleshooting

The employee's payout status shows Status 7 (Employee Opted Out) but the employee is still active.

The automated freeze trigger fires when an employee's last working date plus two days has passed. If the employee's last working date was incorrectly recorded, the system may have created a freeze candidate prematurely. Update the employee's last working date in their profile. If the date is now in the future, the system will automatically remove the freeze candidate status and restore the employee to active payout eligibility on the next processing cycle.

The account holder says they did not receive a pre-freeze notification.

Check the email address and phone number on the employee's profile at the time the freeze candidate was created. The notification is sent once, using the contact details in the freeze candidate record. If the details were incorrect or outdated at the time of dispatch, the notification may have been sent to the wrong address. The system does not resend the notification — contact Zenoti support if the account holder needs to be notified through an alternate channel.

The freeze attempt has been retrying for an extended period without completing.

Retry attempts are managed automatically. If the next scheduled attempt date continues to advance without the freeze completing, this may indicate a persistent issue with the BaaS provider connection for this account. Review the employee's payout status in the View Same-Day Tip Payouts reports for additional status detail, and contact Zenoti support if the issue persists beyond several retry cycles.

The employee shows Status 3 (Wallet Inactive / Not Created) instead of Status 7 (Employee Opted Out).

Status 3 means the employee does not have an active wallet — either it was never created, or it was closed through a separate process. This is distinct from a freeze (Status 7). If you expected the employee to have an active wallet, verify their enrollment status in the Same-Day Tips Adoption Report and confirm they completed the wallet enrollment process.

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