Total sales
The number of fiscal receipts issued in the interval and the total revenue collected in MDL. It is the first line the manager sees at Close — if the figure „looks right”, the details below confirm it.
🍽️ For restaurant · cafe · bar
What does a shift-close report contain?
An immutable snapshot per day × POS — fiscal receipts, total revenue, then aggregation across seven receipt subtypes (sales, e-commerce, production consumed, losses, transfers, goods receipts, transformations) plus a top list of items with losses. The manager reads it in four grouping modes, switchable in one click. The snapshot stays available at any time, and at month-end a roll-up runs across all closed shifts.
📸 Immutable snapshot · frozen at Close, archived for audit
🔀 4 grouping modes · document · product · user · losses
🚦 Non-blocking · does not wait for „clean” orders or the register's Z-report
🗓️ Monthly roll-up · reads the snapshots directly, without rescanning
What is actually written into the snapshot
The report aggregates the day's finalised activity into a compact accounting form. It is not a long list of receipts — it is a synthetic view that the owner can read in 2 minutes.
Production consumed
Aggregated cost + quantity for the finalised production receipts (dishes that came out of the kitchen and were consumed through sales). The basis for margin and for recipe yield.
Aggregated losses
Total cost and quantity of losses recorded during the day (dropped, burnt, expired, tasting) plus a top item list with the most loss events, ordered by descending quantity.
Transfers, goods receipts, transformations
Aggregated rows, quantity, cost for each stock receipt subtype: new inflows from suppliers, transfers between warehouses / units, transformations (raw material into semi-finished goods).
Honest note: the breakdown by payment method (cash / card / transfer), by menu category (pizza / pasta), the net vs. inclusive TVA calculation, the estimated number of customers and the average check are not in the standard snapshot — v1 focuses on aggregation by receipt subtype. These views are ⚙️ available on request, prioritised by the actual impact for you.
The 4 grouping modes — one click, a different reading
The data is read in four views, switchable without regenerating the report. The selected mode stays chosen when another shift is opened — the manager who works „by product” does not have to switch every time.
By document type
Answers „how much came in, how much went out, how much was produced, how much was lost”. The natural accounting view, with one line per receipt subtype. Good for the end-of-day report forwarded to the owner.
By product
Answers „what actually moved” — quantity, cost, revenue, losses, per item. The operational view for the stock manager: what turned over, what stagnated, what was wasted.
By user
Answers „who issued the shift's documents and how much each represents”. The basis for team productivity analysis without exposing financial reports to the waiters — the view stays with the manager.
Losses
Items with losses, ordered by quantity. The manager immediately sees where the most waste occurred in the day and can ask for the reason, without opening receipts one by one.
Each mode shows the essential columns by default and keeps the rest hidden (margin, margin percentage, share of revenue, average price, average cost, cost per row). Column visibility can be enabled from the table settings, per user, and is remembered next time. Tables have search, sorting and pagination, and product codes are clickable through to the item's file.
How a shift is closed — and what „non-blocking” means
The shift manager taps Close shift, chooses the day (today by default) and the POS (all by default). The system scans the day's activity filtered on finalised stages and persists the snapshot in an immutable archive folder. The result appears inline and remains available at any time.
Non-blocking by design
The button does not check the state of orders, production receipts or the cash register's Z-report, and never refuses the operation. Orders still open, receipts in preparation, receipts without Z — stay outside the snapshot, but do not stop the manager from closing.
Snapshot frozen at Close
The saved blob is the accounting truth of reference at the moment of issuance. If a receipt from that day is amended later, the saved journal does not auto-refresh — to reflect the new reality, Close shift is run again for the same day + POS.
Repeated closes = parallel folders
Each run creates a new folder with its own identifier, with no auto-deduplication. The most recent snapshot is considered current, the previous ones stay in the archive for the audit trail. Recommendation: a single Close per day × POS.
Interval from the last close
The report covers the interval between the previous close and the current moment, not the calendar day. In a venue with two shifts, the second close starts where the first left off — no sale is counted twice.
A real scenario — the venue with two shifts per day
A bistro with a day shift and an evening shift closes twice. Here is how the system behaves, step by step — and why no duplicates appear.
08:00 — the bistro opens. The day waiters start serving.
16:00 — the day manager runs Close. Snapshot generated for the interval 00:00 → 16:00: fiscal receipts, revenue, production, losses. It is archived. The evening waiters come on shift.
16:00 → 24:00 — activity continues normally. New orders, new fiscal receipts. The morning snapshot is not touched — it is frozen.
23:45 — the evening manager runs Close. Snapshot generated for the interval 16:00 → 23:45, not 00:00 → 23:45. The morning shift's receipts do not reappear.
When the Close is run for all POS terminals at once (e.g. a general close at 22:00), each POS restarts from its own last close. If the terrace already closed at 14:00, it contributes to the general close only with sales made after 14:00, while the dining room, which has not closed, contributes the entire day. No sale lost, no double counting — regardless of the order in which the Closes are done.
What happens after Close
The snapshot enters two operational flows: the historical list Past closed shifts for reopening at any time, and Month-end for the end-of-month roll-up.
Past closed shifts — the historical list
Every shift ever closed appears in a table: the date, the close time, the POS, the number of receipts, the revenue and who closed. Hidden but available from the table settings: the interval covered, the cost, the margin, the number of rows, the document types, the losses. From each row the report is reopened exactly as it was generated — the system rehydrates the saved snapshot, it does not recalculate.
Month-end — monthly roll-up
The end-of-month card aggregates all shifts closed within a month (or only those of a chosen POS). It does not rescan the receipts — it reads the snapshots persisted at Close directly, so it is fast and consistent with what the manager saw on that day. The output keeps the same structure (subtypes, top losses merged by item) plus meta: number of shifts, list of dates, start / end interval.
Deleting a closed shift is a separate right from the right to close shifts — the reason: the shift report is the source of the monthly aggregation, and a deleted shift changes the monthly total and cannot be reproduced identically. The button only appears where this right is granted explicitly.
A HoReCa shift ≠ the cash register's Z-report
Closing a HoReCa shift is a managerial snapshot per day × POS. It does not issue the cash register's Z-report, does not wait for the Z, does not check it. The Z remains the daily physical operation of the MCR device, completely independent.
In practice: the shift manager runs the HoReCa Close after the cashier has run the physical Z of the day — but the button in the ERP does not wait and does not block. The two flows close separately, each under the responsibility of its own role. The day's housekeeping stays entirely with the shift manager.
Who sees the report
Access is configured conservatively via roles — we handle the setup at onboarding, zero technical work on your side.
Shift manager
The standard role that closes the shift, sees the full report, switches between the 4 grouping modes, opens historical shifts and runs the monthly roll-up. It can be limited per POS — a terrace manager sees and acts only on the terrace.
Administrator
Sees everything, can grant the separate right to delete closed shifts (used rarely, only for rectifications with accounting impact). We prefer this right to stay with the account bearing accounting responsibility, not with the day-to-day operational manager.
Waiter · Cashier · Cook
Have no access to Close shift and do not see financial reports by default. The waiter sees their own history for the current day; the cook sees their kitchen display; the cashier sees their cash operations. Reports stay with the manager, by design.
Frequently asked questions
Can I export the report to CSV or Excel for the accountant?
Yes — the tabular data exports to CSV, XLS and XLSX directly from the UI (the report table or from Past closed shifts on reopen). PDF, JSON for integrations and XML for the SNC journal are custom developments (⚙️ available on request, priced after discovery). Automated sending by email / Telegram at shift close — likewise, a scheduled job that can be added.
Is the SNC accounting journal generated automatically (accounts 611 / 711 / etc.)?
No, not by default. The current snapshot is aggregated by receipt subtype, without a per-line split across Moldovan accounting accounts. Generating the SNC journal + the export to accounting software (1C, SAGA, BAS, InfoCont, WizCount) is a ⚙️ development on request, sized according to your firm's specific accounting flow.
Can I compare the current day with yesterday or with the same day last week?
⚙️ In the works. Comparison views (day-over-day delta, weekly trending, ranking) are a custom development, enabled after validating the key metrics with your manager. As a starting point, the Month-end monthly roll-up exists — useful for the month's volume, without deltas or charts.
I have 3 venues — can I see a consolidated report across the group?
Yes, at the monthly level. The Month-end card can run across all POS terminals in the chain or on just one chosen. Dedicated regional-manager views (per-location comparison vs. chain average, ranking, cross-location per-product-category) are custom developments, sized together with you based on the number of locations and the metrics that matter.
What happens to orders still open when I close the shift?
They stay open and outside the snapshot. The system filters on finalised stages (delivered / ready / stock updated). Unfinished orders continue normally the next day (or in the next shift); when they are finalised, they will enter the snapshot of the corresponding shift. Nothing is lost, nothing is blocked.
I ran Close twice by mistake — how do I delete the duplicate?
The most recent snapshot is considered current. The duplicate stays in the archive for the audit trail. Deleting a closed shift is done from the UI, but requires separate authorisation (usually reserved for the administrator or the account with accounting responsibility) — the reason is that the shift report feeds the monthly aggregation, and a deletion changes the monthly total.
Want a POS + HoReCa system with a professional shift report?
The shift-close report with 4 grouping modes + monthly roll-up is part of Package Extra HoReCa (not part of Micro / Start, which are aimed at simple retail). Role configuration and access to Close we handle at onboarding — no technical work on your side. Package comparison + current pricing → see the pricing page.
Book a conversation
We will show you what the shift report looks like on a demo venue and discuss which metrics matter for you. CSV, XLS and XLSX export for the accountant is included in the package. For anything ⚙️ on request (PDF, SNC journal, custom integrations, day-over-day comparison, consolidated multi-location report), we price after discovery.
SGAPPS LABS SRL · Chișinău, Moldova · Continuously in production since 2018 · POS · ERP · MEV fiscal register · Android fleet