Register → Session control uses the Banknote icon, and Close Register uses the Lock icon. Closing requires pos.register_open permission and is a one-time financial operation on the currently selected register session. Blank counted fields are parsed as zero, signed values are accepted by the input sanitizer, and a mismatch warning can be overridden, so accuracy depends on a deliberate independent count and documented approval—not merely reaching the closed state.

Before you beginSet the intended date range, timezone, locations, registers, statuses, and saved-view filters before reading totals.

Step by step

  1. Before opening the close dialog, confirm the active business, location, register, OPEN badge, opening time, and effective user. The Close Register control appears only with pos.register_open permission. Stop if another register or user context is selected.
  2. Finish or deliberately resolve active selling work first. Review Receipt Activity across Completed, Saved, Incomplete, Layaways, Layaway Payments, Account Balance Open, Account Paid, Layaway Completed, Returns, Exchanges, and Voided. Open any unusual bucket or receipt rather than assuming its amount belongs in tender.
  3. Review Cash drawer movements. Drawer cash shown above the page is opening float plus manual pay-ins minus pay-outs and intentionally excludes customer Cash tenders. Confirm every safe drop, payout, or pay-in against the physical log and note. Never add a movement simply to force the close to balance.
  4. Review Payments Collected and expand each payment type to inspect contributing receipts. It includes supported payments collected on existing layaways. Review A/R/customer-account payments separately because the session screen keeps them outside register tender balancing by design.
  5. Resolve uncertain integrated-card results before closing. Check the sale payment row, terminal/processor transaction, and CentriPay evidence; do not resend, manually duplicate, void, or close over an unknown result simply because the terminal stopped responding.
  6. Add or edit Session Notes while the session is open when working context is useful. These lines are local component state, not independently saved journal entries. When Close Register opens, nonblank lines are joined with line breaks and copied into Closing Note; reopening the dialog copies the current Session Notes again.
  7. Choose Close Register beside the Lock icon. The dialog explicitly says to scroll. Review the entire Payments Collected list, Totals, Cash summary, and Closing Note before using the fixed footer action. On mobile, payment rows are cards in a separately scrollable area; on desktop, they appear in a table.
  8. When the dialog opens, counted values are reset. Every non-cash tender whose expected amount is within half a cent of zero starts as checked with 0.00. Cash always starts blank, even at zero. Every other tender starts blank and unchecked. Do not mistake a blank field for “not applicable”—the close operation parses it as zero.
  9. Verify one tender at a time using physical cash, processor/batch evidence, check log, external financing/gateway record, or the business’s approved source. Enter the actual Counted amount. The text field strips nonnumeric characters except a leading minus and decimal points; signed values can therefore be entered, but use a negative count only when the tender evidence truly requires it.
  10. Use the check box only after independent evidence proves Counted equals Expected. Checking fills the expected amount to two decimals. Unchecking clears the field. Manually editing a nonzero tender does not mark its checkbox; the checkbox is a convenience indicator, not an additional persisted approval record.
  11. Read Totals. Expected is the sum of all displayed payment-type expectations. Counted is the sum of parsed counted fields. Difference is Counted minus Expected. Values within $0.005 are treated as matched; because displayed money is two decimals, verify the actual source rather than relying on rounding edge cases.
  12. Review the Cash summary separately. Drawer base is opening float plus pay-ins minus pay-outs. Cash tenders collected comes from eligible session sale payments. Expected drawer cash is those two values added together. Cash difference is the Cash counted value minus expected drawer cash, rounded to two decimals.
  13. Do not force the overall tender Total to explain the physical drawer. Overall totals include every payment type, while the Cash summary isolates the drawer. A Balanced overall label means entered counts matched expected tender within tolerance; it does not prove processor settlement, deposit timing, bank receipt, inventory, or accounting sync.
  14. Review Closing Note. Replace or extend the copied Session Notes with a concise durable explanation of every approved over/short, processor uncertainty, missing check, safe drop, tender exception, or follow-up owner. The UI does not require a nonblank note before closing, even with a mismatch, so management policy must enforce the explanation.
  15. Choose Close Register once. The handler compares every displayed payment type. If all are within half a cent, it immediately submits the close. If any differ, Count Mismatch Detected lists their names, says management will be notified, and asks whether to continue. No separate notification record is visibly created by this component; the durable evidence is the saved close and note.
  16. Choose Go Back to recount or correct. Use Close Anyway only when the real mismatch is understood, authorized, and fully documented. Close Anyway submits the same count set. A blank missing count is zero and can therefore produce or conceal a mismatch when Expected is also zero—review each field before overriding.
  17. Wait for Register closed. The close operation stores closed user/time, every tender count in cash_counted, Cash as closing float and total, expected drawer cash, cash difference, and closing note. It clears the active-session cache, refreshes register/session/report/sale data, closes the dialog, and clears its local count and note state.
  18. The successful toast summarizes either all tenders matched, the number of payment types needing review, or both the Cash difference and mismatch count. This message is not the final report. Remain on Session Control and review Last Report, then choose View in Reports for the durable Register Reports record.
  19. After a successful close, CentriPOS starts a background processor-reconciliation refresh for the closed session. Failure is logged to the browser console and does not reopen or roll back the session. CentriPay batches and deposits can settle later, so Closed is not equivalent to deposit-reconciled or ready for QuickBooks.
  20. Audit the closed report: exact report/session number, location/register, opener/closer, open/close timestamps, receipt activity, expected and counted tender, variance, opening float, movements, notes, processor/deposit status, and accounting state. Trace any discrepancy through sale/payment → register session → closure tender → processor transaction/deposit → QuickBooks sync evidence.
  21. No close-dialog screenshot is published. The real Amelia Grant Harbor & Hearth image is the safe closed Session Control opening screen, not an active-session closeout. It remains attached to the broader session-control guide; using it here would falsely depict the close workflow.

Screen and contract reference

Control or areaWhat it means
Banknote iconExact Register navigation icon for Session control.
Lock iconExact action icon beside Close Register on an open session.
pos.register_openPermission required for the Open Register and Close Register controls.
Receipt ActivitySession-attached receipts grouped by operational lifecycle; review exceptions before tender counts.
Drawer baseOpening float + manual pay-ins − manual pay-outs; excludes customer Cash tenders.
Payments CollectedEligible session tender totals, including supported payments on existing layaways.
A/R paymentsCustomer-account collections displayed separately and excluded from register tender balancing.
Session NotesUnsaved local working lines copied into Closing Note whenever the close dialog opens.
Payments Collected close listEvery displayed tender with Expected, checkbox, and Counted value.
Zero expected non-cashAutomatically initializes checked at 0.00 when within half a cent of zero.
Cash initializationAlways blank and manual, even when Expected is zero.
Expected tenderSystem-calculated eligible amount for that payment type in the exact session.
Counted tenderParsed actual value entered or copied with the checkbox; blank becomes zero.
Verification checkboxConvenience control that copies Expected to Counted; it is not separate persisted approval evidence.
Signed currency inputKeeps a leading minus and numeric decimal content; verify any negative count carefully.
Half-cent toleranceA tender is mismatched only when absolute Counted − Expected exceeds 0.005.
Totals Expected / CountedSums across every displayed tender type.
Overall DifferenceTotal Counted − total Expected across displayed tenders.
BalancedEntered tender totals match within tolerance; not proof of settlement, deposit, inventory, or accounting reconciliation.
Cash tenders collectedEligible Cash payment amount derived from session sales.
Expected drawer cashDrawer base + Cash tenders collected.
Cash differenceCounted Cash − expected drawer cash, rounded to two decimals.
Closing NoteDurable closeout context stored on the register session; currently not required by the UI.
Count Mismatch DetectedLists tender names outside tolerance before allowing an override.
Go BackReturns to the close dialog without submitting so counts and note can be corrected.
Close AnywaySubmits the mismatched count set; use only with approved, documented evidence.
Register closedClose RPC succeeded and the active session was cleared/refetched.
Background processor refreshPost-close reconciliation attempt that cannot roll back a successful close when it later fails.
Register reportDurable session record containing lifecycle, receipts, expected/counted tender, cash movements, variance, notes, processor evidence, and accounting state.
Screenshot boundaryThe verified Harbor & Hearth capture shows the closed opening screen only, so it is not reused as a close-dialog image.

Expected result

The session closes once with the submitted counts and notes, the calculated variance is recorded, and later sales cannot attach to that closed session.

Troubleshooting

  • Check the date range, timezone, locations, registers, statuses, and saved-view filters first.
  • Refresh after the underlying transaction has finished posting.
  • Open the source sale, payment, movement, or closure when a total needs transaction-level proof.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.