Treat a proposal differently from an effective rule
A cash-rounding measure appeared in the U.S. Congressional Record in August 2026, bringing renewed attention to what should happen when exact change is unavailable. A proposal is not automatically a rule in force. Before changing software or staff instructions, verify whether a measure passed, when it takes effect, which transactions it covers, and whether state or local requirements add detail. Keep the source and date with your internal policy note.
The distinction matters because a register rule can touch tax treatment, refunds, drawer reconciliation, and receipt explanations. A rounding setting should never be enabled just because a news headline mentioned it. Have the appropriate finance or legal reviewer translate the applicable rule into plain steps, then ask the POS provider what the software can represent and what remains a manual process.
Design the rule before changing the terminal
Write down the exact scenario first: cash tender only or every payment type, how the final amount is calculated, what happens to tax, and how the receipt presents the adjustment. Include examples at amounts immediately above and below each rounding boundary. A reviewer should be able to calculate the expected result without access to the register.
Then test the workflow in a non-live environment if one is available. Use a normal sale, a partial cash tender, a void, a return, and a correction. Verify the sales report and drawer total agree with the approved examples. The pricing and cost factors page is a reminder to include configuration and training work in implementation planning, not just hardware.
Make the customer explanation and receipt agree
A policy is easier to trust when the receipt explains what happened in ordinary language. Avoid labels that make a rounding adjustment look like a fee or discount if it is neither. Make sure the display, receipt, posted notice, and cashier explanation use consistent terms. If the system cannot show a required detail, pause rollout and ask the vendor what workaround is supported and auditable.
Coach staff on a single explanation and on how to call a supervisor when a transaction falls outside the tested examples. Do not expect each employee to infer the rule from the total. The retail solution overview outlines the kinds of checkout and reporting questions a retailer should ask; use it as a prompt, not as proof that a specific configuration is available.
Close the loop with reconciliation
At close, compare the cash drawer, recorded tenders, rounding adjustments, and any refunds or voids. Reconcile a sample transaction from the receipt to the register report and the accounting export. A small unexplained difference can turn into a recurring problem if teams use different versions of the policy or if a configuration change is not recorded.
Keep a change log with the rule source, approval, configuration date, test evidence, staff communication, and the next review date. For a system evaluation, include these examples in your POS buying checklist and ask vendors to demonstrate each case. The Freedom POS FAQ states the current public product information; confirm any implementation-specific detail directly before relying on it.
- Confirm the rule is effective and applies to your location.
- Test cash, mixed tender, refunds, voids, and receipts before rollout.
- Record who approved the configuration and when it should be reviewed.