Account Holder Inactivity Tracking Settings
Configure how long an account holder's wallet must remain inactive before it becomes eligible for scheduled closure, and how far in advance Zenoti sends a pre-closure notification.
Note: For conceptual background on the inactivity-based wallet closure pipeline, see Zenoti Wallet Inactive Account Closure Policy.
Audience: Organization administrators who manage tips payout configuration.
On this page
Before you begin
Your organization must have tips payout enabled. See Get started with Same-Day Tip Payouts.
You need the following permission:
Permission: Configure Payment Settings — Required to view and update inactivity tracking settings. Admin path: Configuration > Security > Security roles — open the role, then enable Configure Payment Settings under the Payments group.
Steps
Review the default inactivity thresholds
Before changing any values, understand what the defaults mean for your organization:
| Setting | Default value | What it controls |
|---|---|---|
| Inactivity waiting days | 60 days | The number of consecutive days of zero balance and no transaction activity after which a wallet becomes eligible for scheduled closure. |
| Notification waiting period days | 30 days | How many days before the closure action a pre-closure notification is sent to the wallet holder. |
Under default settings, the pre-closure notification is sent after 30 days of inactivity — that is, 30 days before the 60-day inactivity threshold is reached.
Important: If you change either value, the configured value takes precedence over the defaults described above. Review the interaction between the two settings before saving changes. See How the two settings interact below.
Update the inactivity tracking settings
Note: Inactivity tracking settings are configured by Zenoti on request. Contact your Zenoti representative to update these values for your organization.
When you submit a configuration request, provide the following:
Inactivity waiting days — The number of consecutive days of zero balance and no transaction activity that must elapse before a wallet becomes eligible for scheduled closure.
- Default: 60
- Minimum recommended value: greater than the Notification waiting period days value, so that the notification is sent before closure is triggered.
Notification waiting period days — The number of days before the scheduled closure action that a pre-closure notification is sent to the wallet holder.
- Default: 30
- This value must be less than Inactivity waiting days to ensure the notification is sent while the wallet is still open.
Worked example: Your organization sets Inactivity waiting days to 90 and Notification waiting period days to 45. A wallet with no balance and no transactions for 45 consecutive days receives a pre-closure notification. If the wallet remains inactive for a further 45 days (90 days total), it becomes eligible for scheduled closure.
How the two settings interact
The two settings work together to define the full inactivity timeline for a wallet:
- A wallet enters the inactivity tracking pipeline when it reaches zero balance and records no transaction activity.
- After Notification waiting period days of continuous inactivity, Zenoti sends a pre-closure notification to the wallet holder.
- After Inactivity waiting days of continuous inactivity, the wallet becomes eligible for scheduled closure.
The gap between the notification and the closure action equals:
Inactivity waiting days − Notification waiting period days = days the wallet holder has to act after receiving the notification.
Under default settings (60 − 30 = 30), the wallet holder has 30 days after receiving the notification before the wallet is eligible for closure.
Important: If Notification waiting period days is set equal to or greater than Inactivity waiting days, the notification would be sent at or after the closure threshold — meaning the wallet holder receives no advance warning. Always keep Notification waiting period days strictly less than Inactivity waiting days.
Tips
- Use the default values unless you have a specific business reason to change them. The 60-day inactivity threshold and 30-day notification lead time are designed to balance timely closure of dormant wallets with adequate notice to wallet holders.
- Coordinate changes with your Zenoti representative before a payout cycle. Changes to inactivity thresholds apply prospectively. Wallets already in the inactivity pipeline are evaluated against the settings active at the time of each scheduled closure run.
- Communicate threshold changes to affected employees. If you reduce the inactivity waiting period, employees with low-activity wallets may receive earlier-than-expected closure notifications. Notify your team before the change takes effect.
Troubleshooting
A wallet holder received a pre-closure notification sooner than expected.
The notification timing is determined by the Notification waiting period days setting. If the value was recently reduced, wallets that had already accumulated inactivity days may cross the new threshold sooner than under the previous setting. Verify the current configured value with your Zenoti representative and confirm when the change was applied.
A wallet was closed before the wallet holder received a notification.
This can occur if Notification waiting period days is set equal to or greater than Inactivity waiting days, which causes the notification to be triggered at or after the closure threshold. Contact your Zenoti representative to review and correct the configuration so that Notification waiting period days is strictly less than Inactivity waiting days.
The inactivity threshold does not appear to have changed after a configuration update.
Inactivity tracking settings are applied at the next scheduled closure run after the update is saved. If a closure run has not yet executed since the change, wallets will still reflect the previous threshold. Allow one full payout cycle to pass and then re-evaluate. If the issue persists, contact Zenoti support.