Count Payments, Denominations and Close a Register

Read Payment Tally

Payment Tally is built from the register's saved sales. Expected is what Posnic recorded. Counted is what the cashier verifies. Difference is counted minus expected.

How Posnic Calculates Expected Cash

The close repository recomputes Cash from the saved register session. For split payments it adds only the Cash slice; for a normal sale it adds the amount only when the saved payment mode is Cash.

Count Each Payment Method

1. Open Manage -> Cash Register while the session is open.
2. Read the register name and open date.
3. For Cash, count the physical drawer cash.
4. For card, QR, UPI, wallet or bank labels, compare with the external terminal/provider report.
5. Enter Counted amount for each payment type.
6. Watch Difference after each counted value changes.
7. Write and save a Payment Note for any mismatch or unusual event. Keep separate evidence because the current printed Register Summary omits this note.
8. Do not close until manager-required checks are complete.

Interpret Difference Correctly

Use Payment Summary

Payment Summary gives the session totals: Payment Received, Refunds and Net Receipts. Use it as the high-level check before the physical count.

• Payment Received should match the payment methods expected for the session.
• Refunds should be reviewed against return/refund approvals.
• Net Receipts should make sense for the shift volume.
• If totals look wrong, inspect Sales History before closing.
• External settlement evidence still lives outside Posnic for many payment providers.

Count Denominations

The Denomination card uses note/coin buttons from shop settings or currency defaults. It helps the cashier explain the physical cash total.

1. Scroll to Denomination.
2. Click each cash value button for every note or coin counted.
3. Watch Total update.
4. Use Save when first entering denomination data.
5. Use Update Denomination when revising saved denomination data.
6. Delete denomination only when the count was entered for the wrong session or owner policy allows a reset.
7. Compare the denomination total with the Cash counted amount.
8. When Total Sales is zero, Posnic disables denomination access even if an opening float exists; enter the Cash counted amount directly and retain outside count evidence if needed.

Close the Register

Close Register immediately finalizes the open session and starts the printable Register Summary. There is no confirmation dialog in the current screen, so finish every check before selecting it.

• Normal users can close only their own user/device session. Backend override roles are manager, admin and super_admin.
• The close stores who performed it and emits a register_close audit event.
• The saved close figures are Expected, Counted and Over/Short. Later report viewing should use those stored values rather than recomputing today's screen.
• The printable summary includes branch, user, register, open/close times, payment tally, payment totals, sales totals, Opening Float, Cash In and Cash Out.
• The printable summary currently omits Payment Note, denomination breakdown and the explicit label Over/Short; retain those separately when required.

1. Stop sales on this physical drawer and confirm the branch, register name, open date and signed-in user.
2. Save Counted for every payment row and investigate each non-zero Difference.
3. Save the Payment Note and denomination breakdown where used.
4. Review Payment Received, Refunds, Net Receipts, Total Sales, transaction count, Opening Float, Cash In and Cash Out.
5. Select Close Register once. Posnic closes immediately; it does not ask for confirmation.
6. When the print window opens, print or save the Register Summary according to owner policy.
7. Verify the register now shows Closed and review its saved session in Register Reports.

Do Not Blind Close

The current close API requires only the active cash-register session ID. Posnic therefore allows a session to close without a saved Cash counted value. In that case it preserves Expected but stores Counted and Over/Short as blank rather than proving reconciliation.

• A successful Close message does not prove the drawer was counted.
• Always click each Counted value and save the verified number before Close Register.
• If Counted is intentionally zero, save zero and explain why according to policy.
• Review Register Reports after close and escalate any session with missing Counted or Over/Short evidence.

Common Differences