End of Day posting

End of Day is the step that turns the day's completed sales into standard Business Central documents. In Bitta Retail POS you pick a date, read a preview, and confirm; the run then creates one consolidated document per group of sales, so the day's trading lands in Posted Sales Invoices and Posted Sales Credit Memos instead of a separate ledger. You can run it by hand or let a recurring job queue entry run it every day.

Prerequisites

• The BAA POS - Admin or BAA POS - Full permission set. End of Day checks write permission on the Posted Daily Sales archive before it creates anything. Without it, the run stops with "End-of-day posting is an administrator task ... Nothing has been posted." See POS user permissions.
• POS customers and POS items mapped to Business Central customers and items.
• The drawer shifts for the business date closed and counted. See Shifts and Z reports.

Close the shifts first

Before anything is written, End of Day looks for every open drawer shift with a business date on or before the posting date, whether or not the shift has sales. The EOD Open Shift Policy field on POS Setup, in the Daily Operations FastTab, decides what happens next:

EOD Open Shift Policy	What End of Day does
Block (default)	Stops with "End of Day cannot continue because N open drawer shift(s) for this business date have not been closed and counted. Close the shifts and try again. Nothing has been posted."
Warn	Puts a WARNING line at the top of the preview and defaults the confirmation to No. Scheduled and other unattended runs treat Warn as Block.
Allow	Continues without a message.

The message lists up to five shifts as Shift / Store / Terminal and counts the rest. If the set of open shifts changes after you confirm a Warn preview, the run stops and asks you to confirm again.

Run End of Day

1. Search for POS End Of Day in Tell Me (it also answers to EOD, Daily Posting, Consolidate and Day Close). You can also choose End of Day in the Shifts and Cash menu of the Bitta Retail POS Admin role center, or End of Day Posting on the POS Sales list.
2. Set the two options, then choose OK:
   • Posting Date: select the date for which released, unposted POS sales will be processed into consolidated Business Central documents. It defaults to the work date.
   • Create Sales Orders (Not Posted): specifies the document mode for this run. Disabled creates and posts consolidated Sales Invoices. Enabled creates consolidated Sales Orders without posting them. Return groups always post as Sales Credit Memos. The switch starts with the Create Sales Orders by Default value from POS Setup, and changing it here affects this run only.

3. Read the preview. It is built before anything is written and lists the sales and consolidation groups in scope, the document type, return groups, stores and terminals, sales skipped for having no customer, and groups that will not post, with the reason. Choose Yes to run. Choosing No returns you to the dialog with nothing written. When no sale is in scope, no preview appears (unless the Warn policy found open shifts); a message says there is nothing to post and no documents were created.

4. Read the result. A full success reads "End of day completed successfully: posted N consolidated Sales Invoice(s) covering M POS sale(s)" (or "created N consolidated Sales Order(s) (not yet posted)" in order mode). If any group failed or any sale was skipped, a summary starting "End of day finished with issues" lists each failed group by customer, store and terminal with the reason.

Fix the issues the summary names, then run End of Day again for the same date. Groups that already posted do not post again. Only one run can process a posting date at a time; a second run stops with "End of Day run N is already processing" that date.

What a run includes

A run takes the sales dated on the Posting Date that are Released and not yet posted; open, cancelled and already posted sales are never touched. Released sales without a customer are skipped and counted in the result. This is rare: a sale cannot be released without a customer, and new register sales default to the store's or POS Setup's Cash Customer No. Each consolidation group becomes one document, as described on Consolidated posting, and the run ends by posting pending settlement payments.

Schedule a daily run

1. Open POS Setup and expand the Daily Operations FastTab.
2. Turn on Enable Daily Consolidation, which schedules one recurring, noninteractive End of Day run for the company. Set Daily Consolidation Time, the company-local time when the run starts, and Daily Operations Time Zone ID, which sets both the scheduled time and the End of Day posting date and follows daylight-saving changes. The time zone is required while the schedule is on.
3. Check Schedule Status. Saving a change to these three fields requests a schedule update automatically; Synchronize Daily Operations Schedule applies it immediately and shows "The daily operations schedule is synchronized with POS Setup."

The job queue entry is named BAA POS Daily End of Day. It recurs every day, retries up to 3 attempts with a 300-second delay, and uses the Create Sales Orders by Default mode. A scheduled run processes the company-local date on which it runs, and it applies the same open-shift policy, with Warn treated as Block.

Review the run history

Open POS Daily Operations Runs from Tell Me or with Daily Operations Runs on POS Setup. Every attempt has a row; manual runs show Interactive Run selected. Status is Running, Succeeded, Completed With Issues, Skipped, Failed or Interrupted, and Action Required says what to do next. Job Queue Entries, Job Queue Log Entries and Settlement Entries open the related records.

To reconcile the day before and after a run, use the POS Daily Reconciliation report. All day-close reports are listed in All POS reports.

What's next

See how the run builds its documents: Consolidated posting.