Open it at closing.The day is already counted.

Every figure separates the two payment modes where it is shown, not in a later report. Behind the evening read sits the order book: each order under the token the counter called and the order ID it was written against, so both point at the same line, with status and mode narrowed inside the table and six date presets and a custom range over the top. Four actions ride every row — view, edit, cancel and print — and the thing that prints is configured rather than hard-coded: header, tax, footer and paper width live in Settings, and override the companion app.

The other half of the book. Paid cash and paid UPI are held apart from what is still owed, staff expenses sit on their own card because they settle by bank transfer rather than out of the till, and each line carries its category, its quantity and unit, and a GST chip where tax applied — with eight running totals on one strip above the table. Both halves then read against each other over the same window: orders, revenue, average order and the split on one side; entries, total, credit pending and settled on the other. Each leaves as a file.

Three roles — Admin, Staff and Cashier — are set on the account and shown as a chip, with four actions on every row: permissions, password, deactivate and delete. An account that has never been signed into carries a dash rather than an invented last login. The trail behind them is sequential and filterable by module, by action and by user: each entry carries its own ID and timestamp, who acted, where in the app, and what they did to it — and the filtered trail leaves as a CSV that the trail then counts.