Register Closure β Invoice Source Filtering
When your center uses external checkout systems, public APIs, or online sales channels, open invoices created by those sources can trigger unnecessary alerts or blocks when front desk staff close the register. Invoice source filtering lets administrators specify which invoice sources are included in the open-invoice check at register closure, so that invoices from excluded sources do not block or alert staff β even if those invoices remain open.
Audience: Administrators who configure register closure behavior for centers that process invoices through multiple channels.
On this page
- Before you begin
- Steps
- How source filtering works with existing invoice-type filters
- Tips
- Troubleshooting
- Related articles
Before you begin
- You must have access to organization or center-level register closure settings.
- The Register closure behavior when invoices are open setting must be set to Alert the front-desk staff or Block the front-desk staff from closing the register before invoice source options are presented. If neither option is selected, no open-invoice check runs at closure and source filtering has no effect.
- Confirm which invoice sources your center uses (for example, external API integrations, online booking flows) before making changes. Excluding a source means open invoices from that source will never block or alert at register closure.
Permission: You need administrator access to the register closure configuration settings. Admin path: Security Roles > [your role] > Permissions tab > Administrator section > Cash Management
Steps
Configure invoice source filtering for register closure
Navigate to Configuration > Appointments > Notifications and alerts > Employee alerts.
Locate the Register closure behavior when invoices are open setting and confirm that Alert the front-desk staff or Block the front-desk staff from closing the register is selected. Invoice source options are only visible under the selected option.
Under Include open invoices from external sources, review the list of selectable invoice sources.
Select each invoice source that you want to include in the open-invoice check. Sources you leave unselected are excluded from the check.
- External API integrations β Invoices created through external API calls. Deselect this source if your center uses third-party systems that generate invoices independently of the front desk.
- Online booking flows β Invoices originating from online sales channels or the Webstore. Deselect this source if online-initiated invoices should not block register closure.
Note: The exact source options displayed depend on which invoice sources are active for your organization. Only sources relevant to your center's configuration appear in the list.
Save your changes.
Important: After saving, test the configuration by leaving a sample open invoice from an excluded source and then attempting to close the register. Confirm that no block or alert appears for that invoice before rolling out the change to all staff.
How source filtering works with existing invoice-type filters
Invoice source filtering operates in addition to any invoice-type filters already configured under the Register closure behavior when invoices are open setting. The two filters work together:
The following table summarizes how the two filter types interact:
| Filter type | What it controls | Effect when an invoice matches |
|---|---|---|
| Invoice-type filter | Which types of invoices (for example, service invoices, product-only invoices) are included in the open-invoice check | Invoices of excluded types do not block or alert |
| Invoice source filter | Which originating sources (for example, external API, online booking) are included in the open-invoice check | Invoices from excluded sources do not block or alert |
An open invoice must match both an included type and an included source to trigger a block or alert at register closure. If either filter excludes the invoice, it is ignored during the closure check.
Worked example: A center processes walk-in services through the front desk POS and also receives orders through an external API integration. The administrator enables the Block/Alert setting, includes service invoices in the invoice-type filter, but excludes the external API source from the invoice source filter. At register closure, open service invoices created at the front desk trigger an alert. Open invoices created by the external API β even if they are service invoices β do not trigger an alert or block, because the source filter excludes them.
Tips
- Audit your invoice sources before configuring. Review which channels generate invoices for your center (front desk POS, online booking, external integrations) and decide deliberately which sources should be included in the closure check. Excluding a source is permanent for that closure session β staff will not see any alert for open invoices from that source.
- Use source filtering for high-volume API integrations. If your center receives a large number of invoices from an external system that are settled outside Zenoti, excluding that source prevents unnecessary closure delays for front desk staff without affecting financial accuracy.
- Combine source and type filters for precise control. Source filtering and invoice-type filtering are independent controls. Use both together to define exactly which open invoices matter at register closure for your center's workflow.
- Communicate changes to front desk staff. When you exclude a source, front desk staff will no longer see alerts for open invoices from that source. Make sure staff understand which invoice sources are excluded so they do not assume all open invoices are accounted for at closure.
- Verify the setting after each change. After updating source filter selections, perform a test closure with a known open invoice from each excluded source to confirm the expected behavior before the next business day.
Troubleshooting
Front desk staff are still being blocked by invoices from a source I excluded.
- Confirm that you saved the source filter configuration after making your selections. Unsaved changes do not take effect.
- Verify that the invoice in question was actually created by the excluded source. Check the invoice's Source: field to confirm its origin.
- Confirm that the invoice-type filter is not independently including the invoice. Both filters must allow the invoice to pass for it to be excluded from the closure check.
The invoice source options are not visible in the register closure settings.
- Confirm that Alert the front-desk staff or Block the front-desk staff from closing the register is selected under Register closure behavior when invoices are open. Source filter options only appear under the selected option.
- Confirm that your organization has active invoice sources beyond the standard front desk POS. If no external or online sources are configured, the source filter options may not be displayed.
An excluded source's invoices are still appearing in the blocking invoices list at closure.
- Check whether the invoice was created through a combination of sources (for example, an invoice initiated online but modified at the front desk). Invoices that pass through multiple sources may be attributed to the front desk source rather than the originating external source.
- Contact your administrator to verify that the source filter configuration has been applied at the correct center level and that the setting is active for the current business day.