How to evaluate restaurant POS cash rounding

A restaurant POS should apply your chosen rounding rule only to eligible cash payments and leave the card amount unchanged. Before buying or changing a setup, ask the vendor to demonstrate that behavior on the payment screen, receipt and report. Then check refunds, split payments and the devices your staff actually use.

Do not assume that a POS with cash payments also has the rounding controls you need. The useful buying question is whether the system can apply your rule consistently, show staff the amount due and preserve a clear record of the adjustment.

Define the rule before comparing systems

Start with a written rule for your restaurant. Identify which payments qualify, the rounding increment and how the system should handle an amount that falls between two increments. Decide whether the adjustment applies to the final payment amount or somewhere earlier in the transaction. For this evaluation, the goal is to keep the original sale amount visible and adjust the eligible cash amount at tender.

Also decide what should happen when a guest pays by card, uses more than one tender, or receives a refund. A split payment needs particular care: ask whether the rule applies to the cash portion, the remaining balance or neither. Write down the result you expect before the demonstration so the vendor is not choosing the rule for you.

The cashier needs a clear answer at the point of payment: the original amount, any rounding adjustment and the cash amount to collect. A manager needs enough detail later to explain the difference between the recorded sale and cash received. Check both needs when reviewing a restaurant POS system.

Your operating rule must fit the requirements that apply to your business. Ask a qualified adviser about any legal or tax treatment before adopting it. The vendor should explain what its settings do; the vendor demonstration alone does not settle whether your chosen rule is appropriate.

Ask vendors to show the complete workflow

Give each vendor the same requirements sheet and ask for a demonstration from order total through payment record. Include a cash payment, the identical amount paid by card, amounts on both sides of a rounding boundary, a split tender and a refund. Ask the demonstrator to use the roles and devices that would handle those transactions at your restaurant.

Watch for the point at which rounding appears. Can the cashier see the adjustment before collecting cash? Is it a separate line, and does the receipt make the final amount understandable to the guest? If the screen shows only a rounded total, ask how a manager can identify the original amount and the adjustment afterward.

For card, check the amount presented for payment and the recorded card amount. Neither should be changed by a cash-only rule. For reports, ask where the original sale, adjustment and tender are shown, and whether the figures can be traced to the individual transaction. You are looking for a usable explanation of the difference, not just a drawer total that happens to balance.

Then move beyond the standard payment. Can an employee reverse or refund a cash sale using the same record? What happens if the refund is partial or uses a different tender? Can a manager correct a mistaken tender choice without losing the adjustment history? If a function is unavailable, record that fact and decide whether a documented manual process would be workable.

Toast lists restaurant POS, hardware, online ordering, payments, kitchen display systems and integrations. Square offers restaurant point of sale and related payment and order tools. Fleksa offers restaurant POS connected with direct ordering, reservations and related tools. For each, ask specifically how cash rounding works rather than assuming it from the broader product description.

Ask whether the desired behavior depends on a particular plan, processor, device or configuration. Confirm who can change the setting and whether the rule is shared across terminals. If you use more than one kind of POS hardware, include each relevant device in the demonstration. Get dependencies, implementation work and any recurring or exception charges in a written quote.

Use a cents-based cash and card worksheet

The following is a hypothetical acceptance example. Assume the restaurant has chosen to round an eligible final cash amount to the nearest five cents, up or down, while card payments remain at the original amount. These figures describe payment amounts, not POS operating costs. Fixed costs, variable costs such as processing fees, and exception costs such as corrections or support are excluded.

Use the expected results in the table as a script. The adjustment is the difference between the original amount and the amount collected; it is not an extra sale. The receipt or transaction record should make that difference understandable under the restaurant's chosen rule.

For the first row, the cashier should see $12.97 as the original amount, a two-cent downward adjustment and $12.95 due in cash. The receipt should communicate the same result. A manager should be able to find the transaction and understand why cash collected is two cents below the original amount.

Run the same $12.97 sale as card. The expected card amount is $12.97, with no cash-rounding adjustment. If the card amount changes, or the record cannot distinguish the cash adjustment from the original sale, the system has not met this example's acceptance criteria.

The $12.98 cash case checks the other direction: a two-cent increase produces $13.00 due. The final row checks that an amount already on a five-cent increment stays unchanged. Add the boundary amounts that matter to your actual rule, including any tie case if your chosen increment permits one. Do not infer boundary behavior from a single successful transaction.

Keep expected results separate from observed results. During an authorized demonstration or test, note the device, staff role, setting, screen, receipt and report result for each row. Mark a result as not demonstrated if the vendor cannot show it. A verbal assurance is useful context, but it does not replace seeing the workflow your team would use.

Check exceptions without creating real transactions

Before a live service pilot, use a vendor-provided simulation or other authorized practice environment. Confirm that the exercise will not create a real card charge, send a guest message or dispatch a courier. Use simulated tenders and records; do not enter a real customer's payment details.

Test a full refund against the original cash transaction. Ask the vendor to show the original sale, its adjustment and the proposed refund amount together. If your rule calls for returning the amount actually collected, the first worksheet row would suggest $12.95 back in cash. Confirm how the system records that refund and whether your adviser agrees with the intended treatment. Do not assume every POS calculates it that way.

Partial refunds need their own decision. Ask how the system associates a partial refund with the original rounding adjustment and what happens if several partial refunds eventually cover the sale. For split payments, ask for a demonstration using your written rule and verify that any card portion remains unchanged. If the product cannot support the desired result, document a fallback or exclude it from your shortlist.

A live service pilot is different from practice. If you proceed, authorize its scope, train the staff involved and monitor actual transactions under your normal controls. Do not treat a simulation as proof of live behavior, or use live guest transactions merely to complete a practice checklist.

Choose an owner, fallback and acceptance standard

Assign a manager to own the rounding setting and the requirements sheet. That person should approve changes, check who has permission to make them and keep the current rule available to staff. The cashier should know what amount to collect and whom to call if the screen does not match the expected result.

Set a fallback before launch. For example, staff can pause the affected transaction and ask a manager for help rather than inventing an adjustment or changing the card amount. The manager should record the issue and follow the restaurant's approved correction process. Ask the vendor how to preserve an audit trail when a tender is selected incorrectly.

Accept the setup only when the agreed cash cases show the right adjustment, the equivalent card cases remain unchanged, and the receipt and report explain the result. Add your refund, split-tender, device and role requirements to that standard. An unresolved exception is a decision to make, not a passing result.

Compare written quotes separately from the cents worksheet. Include the fixed charges, variable charges and likely exception costs each quote identifies, and ask vendors to clarify exclusions. A quoted processing fee alone is not the all-in cost of operating the system. Ask about contract terms and get qualified advice where contract, legal or tax treatment needs interpretation. For broader cost questions, see payments, processing cost, cash close and POS reports.

Bring the worksheet and your exception rules to a Fleksa POS demo. Ask the team to show each relevant payment state, receipt and report, and to identify any setup or dependency needed to meet your acceptance criteria.

Frequently asked questions

Does cash rounding change the card price?

Under a cash-only rule, it should not. Check the card payment screen and transaction record using the same original amount as a cash test.

Should a cash refund use the rounded amount?

Decide the intended refund rule for your restaurant and ask the vendor to demonstrate full and partial refunds. Consult a qualified adviser about the appropriate treatment.

Is a balanced cash drawer enough to verify rounding?

No. A balanced drawer does not by itself show whether each adjustment was correct. Check the original amount, rounding line, tender and transaction record as well.