Separate the legal question from the operating question
A Minnesota proposal introduced in May 2026 would require retail establishments to accept cash and lists August 1, 2026 as a proposed effective date. A bill's text is not proof that it became law, so operators should check its current status and verify requirements with official state guidance or qualified counsel before changing a checkout rule.
The operational question is more immediate. Can a cashier explain the available payment methods? Does a receipt show what was tendered and what change was due? Can a manager reconcile a drawer without relying on memory? Those basics matter whether a location accepts cash, cards, or both. Start with the store's written policy, then check that the register workflow, staff training, and closeout routine all describe the same thing.
Map the transaction from greeting to close
Walk one ordinary sale through the whole shift. Note where the cashier selects a tender type, where a mixed tender is recorded, what appears on the receipt, and how a void or correction is documented. Compare that sequence with the end-of-shift count. If a supervisor needs to translate between a register report and a handwritten note, record the gap rather than assuming the team will remember the workaround.
Keep the customer-facing explanation short and neutral. Post the accepted methods where they can be seen before checkout, and make exceptions easy for staff to escalate. If a rule varies by location, put the location-specific instruction in the shift guide. The retail workflow overview can help frame questions about catalog, checkout, returns, and reporting as one connected operating journey.
Make rounding and refunds auditable
Cash rounding is a separate policy decision from accepting cash. When a jurisdiction permits or requires a particular approach, the point-of-sale configuration should apply it consistently and show the result clearly on the receipt. Do not ask employees to improvise rounding at the till. Keep the approved rule, its effective date, and the person responsible for updates in a place managers can find.
Refunds deserve the same care. Document whether a refund returns to the original payment method, what proof is required, and how an exception is approved. A return should link back to the original sale whenever the system allows it. For a broader procurement checklist, use the POS buyer's guide to test how any system records tenders, refunds, corrections, and end-of-day totals.
A short readiness checklist
Before changing a policy, test it with a manager and a new cashier. Ask both people to describe the same sale, issue the receipt, explain a refund, and complete the drawer count. Differences reveal training or configuration problems before a busy shift does. Review the script after a policy change and again after the first week of use; staff questions are useful evidence about where the instructions are unclear.
Keep the review modest and repeatable: one transaction, one receipt, one refund, one closeout. Record what worked, what confused the team, and which owner will fix each gap. When you evaluate a platform, ask for this workflow using your own examples rather than relying on a feature list. Start with the Freedom POS FAQ for what is publicly documented, and use the pricing overview to understand the factors that can shape a POS budget.
- Verify local cash rules with an authoritative source.
- Align written policy, register steps, receipt language, and drawer close.
- Keep a named owner and review date for each location-specific rule.