Dispensary POS Reconciliation and Day-Close Controls: What Cannabis Operators Should Track

Start with register open and close discipline

A reliable day-close workflow starts before the first sale. Operators should know which register opened, who opened it, what starting cash was counted, and which store or facility details applies.

At close, the system should make it easy to compare expected cash, counted cash, card or other tender totals, refunds, voids, discounts, and receipt totals without forcing managers to rebuild the day from disconnected reports.

• Capture register open, starting drawer, closing drawer, owner, store, and timestamp.
• Review cash drawer counts against expected totals.
• Separate payment type breakdowns from tax, fee, discount, and receipt review.

Review receipts, voids, returns, and discounts

A clean sales total is not enough. Day-close controls should show receipts, voids, returns, discounts, overrides, and manual exceptions with user, role, reason, and approval details. These events can affect inventory, margin, cash, and compliance-sensitive records.

• Tie returns and voids back to the original receipt and inventory record where possible.
• Require reason details for discounts, overrides, and manager-reviewed exceptions.
• Keep receipt, inventory, and finance handoff records aligned.

Connect sales reconciliation to inventory

Cannabis retail reconciliation should connect what sold to the package and item records that were available at the time of sale. If POS records and inventory records drift apart, store managers may close the day while inventory exceptions remain unresolved.

• Review sold, returned, reserved, held, and adjusted inventory separately.
• Flag package or item exceptions before managers finalize the close.
• Use the same operating record for POS, inventory, and margin review.

Use manager approval for exceptions

Multi-store operators need repeatable controls for exceptions such as cash variance, unusual discounts, repeated voids, return spikes, or unresolved receipt mismatches. Approval thresholds help teams separate normal day-close work from issues that need manager review.

• Route cash variance, void, discount, and return exceptions to an owner.
• Use role-based approval for sensitive day-close adjustments.
• Keep audit trail detail visible after the close is completed.

Review compliance-sensitive queues before close

If a retail workflow creates compliance-sensitive events, operators should review queue status, failures, retries, approvals, and unresolved exceptions before assuming the day is done. The goal is operational readiness and clean handoffs, not unsupported compliance promises.