Reviewed by: Selio Support Team
Last updated: May 13, 2026
Summary
Run Close of Day only after open checks, unpaid or partial payments, fiscal-device actions, invoices, refunds, and reporting exceptions have been reviewed or explicitly assigned for follow-up.
Before you begin
- Finish service or move the location into its final closing window.
- Review open orders, unpaid checks, split-payment balances, refunds, and failed or pending payment attempts.
- Check invoice, fiscal, transaction, and live-sales views before relying on the final daily summary.
- Make sure the closing staff follows the same internal checklist every shift and records unresolved follow-up items.
Steps
- Review open or unresolved orders before starting the close.
- Confirm payments are completed, failed, refunded, or clearly marked for follow-up.
- Check transactions, invoices, fiscal actions, and device confirmations that still need attention.
- Open the Close of Day flow.
- Review the daily summary on screen against the transaction and report context instead of relying on memory.
- Confirm the closing action only after the totals, exceptions, and follow-up notes are understood.
- Verify the success state before leaving the device or handing over to the next manager.
Troubleshooting
- Close of Day is blocked: There may still be open orders, unfinished payments, or unresolved fiscal work.
- Daily totals look unexpected: Review discounts, voids, refunds, split payments, invoices, and transactions before retrying the close.
- The close action looks stuck: Refresh only after confirming there is no pending operational work or device response left to finish.
- You are not sure the day closed successfully: Reopen the result and confirm the final success state and daily records.
- A manager finds an issue after closing: Keep the original close result intact and investigate through transactions, reports, invoices, or fiscal records instead of guessing.
