Register Closure Report Delivery Conditions
The register closure report is emailed to users at the end of each business day. Before Zenoti delivers the report to any user, it evaluates five conditions simultaneously. If any single condition is not met, the report is suppressed for that user β other eligible users are unaffected.
This article explains each condition, why it matters, and how to diagnose non-delivery without opening a support ticket.
On this page
Before you begin
- You need administrator-level access to view and modify user profiles and notification settings in Zenoti.
- Familiarity with how your organization has configured register closure settings is helpful before attempting to diagnose delivery issues.
Permission: Access to user profile settings and transactional email configuration typically requires the Administrator or Owner security role.
How delivery works
When a register is closed, Zenoti generates a register closure report and evaluates each user who might receive it. The evaluation runs all five conditions as a single gate β all five must be true at the same time. A user who fails even one condition does not receive the report for that day. Users who pass all five conditions receive the report normally.
This per-user evaluation means that delivery failures are isolated. If one user's email address is missing, only that user is affected β other eligible users still receive their reports.
Delivery conditions
The following five conditions must all be true for a user to receive the register closure report.
Condition 1 β Closure report toggle is enabled for the user
The user's profile must have the register closure report toggle switched on. If this toggle is off, the user is excluded from report delivery regardless of all other settings.
To check this setting, navigate to the user's profile and confirm the closure report option is enabled.
Condition 2 β Transactional email is enabled for the user
The user must be opted in to receive transactional emails. If a user has opted out of transactional email at the profile level, the register closure report is treated as suppressed for that user.
This is a per-user communication preference. Enabling it at the organization or center level does not override a user-level opt-out.
Condition 3 β The user has an email address on record
Zenoti requires a non-empty email address on the user's profile before it can deliver the report. A user with no email address on file is automatically excluded from delivery.
To resolve this, add a valid email address to the user's profile.
Condition 4 β The email address is in a deliverable state
Even when an email address is present, it must also be in a deliverable state. An email address can be marked undeliverable if a previous message to that address bounced or was flagged as invalid.
If a user has a valid-looking email address but still does not receive the report, check whether the address is in a non-deliverable state. Correcting the address or clearing the undeliverable flag restores eligibility.
Condition 5 β The user's last working date has not passed
Zenoti checks whether the user is still active based on their last working date. If a user's last working date is set to a date in the past β for example, because they have left the organization β they are excluded from report delivery for any day after that date.
Users with no last working date configured are treated as active and pass this condition automatically.
To restore delivery for a user whose last working date was incorrectly set, update the date on their profile.
Diagnose non-delivery
If a user reports that they are not receiving the register closure report, work through each condition in order.
- Open the user's profile and confirm the closure report toggle is enabled.
- Confirm the user is opted in to transactional email.
- Confirm a non-empty email address is on file for the user.
- Confirm the email address is in a deliverable state β look for any bounce or invalid-address flags on the profile.
- Confirm the user's last working date is either not set or is set to a future date.
If all five conditions are satisfied and the user still does not receive the report, verify that the register was closed correctly for the day in question, since report delivery depends on a successful register closure event.
Note: Delivery failures for one user do not affect other users. If some users receive the report and others do not, the issue is specific to the users who are missing it β check each of the five conditions for those users individually.