Yes, staff can accept a prepaid voucher without counting the sale twice, but the POS and accounting setup have to distinguish the original voucher payment from the later meal sale. Ask the vendor to show both transactions and their reports before you sign or change your setup.
The key question is where the voucher value goes at each step. A guest pays for a voucher first; later, staff apply it to a check. If both events appear as ordinary food sales, your reports may overstate sales. If redemption is recorded only as a discount, you may also lose track of the prepaid balance.
Define the voucher journey before comparing systems
Start with a real service situation. A guest presents a voucher at the counter or table. The employee needs to identify it, see whether it can be used and apply the right amount. Before the guest leaves, the employee also needs a clear answer about any remaining check balance or unused voucher value.
Write down your rules for each step:
- Identifier: Will staff enter a code, scan a barcode or look up another identifier? What happens if it is damaged or entered incorrectly?
- Expiry: What policy applies to your vouchers, and what should the screen show when a voucher is past its stated date? Ask a qualified adviser about the applicable rules before setting the policy.
- Partial use: Can a guest spend less than the voucher value and use the balance later? If not, what happens to the unused amount?
- Payment remainder: Can staff apply a voucher and then take another payment method for the rest of the check?
- Accounting treatment: How will the initial payment, outstanding value and redemption reach your accounting records without duplicating sales?
Also identify who may issue, redeem, void or adjust a voucher. A cashier may need to redeem one, while a manager handles a disputed balance. Decide whether guests can use vouchers across locations or ordering channels, if those matter to your business. Do not assume a voucher accepted at a counter will work online.
Your accountant can help decide how to treat voucher payments, outstanding balances, expiration and redemption for your business. The POS must then produce enough detail to support that treatment. Ask your adviser about contract, legal and tax questions as well; a vendor demonstration is not a substitute for that advice.
Ask vendors to show the full workflow
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 a restaurant POS system connected with direct ordering, reservations and related tools. Ask each vendor to demonstrate your voucher requirements rather than assuming that a general POS feature list covers them.
Start at issuance. Ask the vendor to show what staff enter, what the guest receives and where the outstanding value appears. Then move to redemption on each device and at each location where your team would actually accept vouchers. Include the employee role that will handle the transaction, not just a manager account.
For each step, ask what happens when the system cannot complete it. Can staff see a reason for rejection? Can a manager correct an entry? What happens if the connection drops? Do not assume offline redemption is available or that an offline balance is current. Agree on a fallback that prevents staff from guessing whether value remains.
Compare the reports as carefully as the payment screen. Request a sample showing the original voucher payment, the meal sale, the voucher amount applied and any remaining voucher value. Ask how those figures appear in the end-of-day close and any accounting export. Your POS cost and reporting review can also cover how payment records reach the cash close.
Record whether each requirement is included in the quoted setup, needs another plan or processor, requires manual work, or is unavailable. Ask for setup charges and ongoing charges in writing. Compare the full quoted operating cost, not just the payment-processing fee: fixed charges, variable charges and charges for exceptions or support can matter too. If a quote leaves one out, ask whether it is included or not applicable.
Use a voucher redemption and accounting question sheet
The following is a hypothetical practice case, not a claim about any particular POS. A guest buys a $30 voucher and later uses all of it toward a $48 meal check. The guest pays the remaining $18 by another method. The restaurant receives $30 at issuance and $18 at the meal, for $48 total. The meal sale is $48; the $30 redemption is part of its payment, not a second $30 meal sale.
The example excludes tax, tips, payment-processing fees, fixed software charges and exception charges. It illustrates transaction amounts, not an all-in operating cost. Your accounting treatment may differ, so have your accountant review the reports and entries.
Use the table to record the expected result before a demonstration. Add the vendor's actual result and any follow-up in your own copy after an authorized test.
| Step | Expected result | Question for the vendor |
|---|---|---|
| Issue $30 voucher | $30 received; voucher shows $30 available. | Where are the payment and outstanding value recorded? |
| Open $48 meal check | Check shows $48 before applying the voucher. | Which screen and report show the meal amount? |
| Apply $30 voucher | $30 applied; $18 remains due; voucher balance is $0. | Is redemption shown as a payment or another transaction type, and how does the report avoid another $30 sale? |
| Pay $18 remainder | Check is closed with $30 voucher value and $18 other payment. | Do the receipt and close report show both payment components? |
| Review records | Meal sales show $48, not $78; voucher is no longer outstanding. | Can the accounting export or report support the agreed entries? |
The table checks two different things: what the employee sees during service and what the business can reconcile afterward. A correct-looking receipt alone is not enough if the sales report or export counts the voucher payment again. Conversely, a report that totals correctly is not enough if a cashier cannot tell whether the voucher was accepted.
Run through the case in a vendor demonstration or authorized practice environment. Confirm beforehand that the simulation cannot create a real payment, send a guest message or dispatch a courier. Use a practice voucher and a test check, and ask how the environment keeps those records separate from live reporting. Do not enter a real card for practice.
After the basic case, change one condition at a time. Ask to see a voucher used for less than its value, a check larger than the remaining value, an expired voucher under your policy and a repeated attempt to use an exhausted voucher. For partial use, the acceptance criterion should state the exact remaining balance and whether it can be redeemed later. If your policy does not allow partial use, ask the vendor to show the message and staff action instead.
Set the operating rule and resolve exceptions
Turn the question sheet into an operating rule before launch. Name the person who owns the voucher balance report, the person who can approve corrections and the manager who handles a guest dispute. Write down where staff find the procedure and what they should say when a code cannot be accepted.
For example, a practical fallback might be to pause redemption and call a manager to check the voucher record. The manager should record the issue and decide the next step under the restaurant's policy. Avoid telling staff to apply an ordinary discount as a routine substitute: that can hide the difference between a discount and prepaid value unless your accountant and vendor have agreed on a documented process.
Set acceptance criteria that someone can verify. For the hypothetical full-redemption case, the check should show $30 applied, $18 still due before the second payment, and $0 voucher value remaining afterward. The meal sales report should show $48 rather than $78, with the original voucher payment identifiable separately. If a screen, receipt or report cannot show the required result, record that gap and decide whether an approved manual reconciliation is workable.
Ask about reversals and mistakes as well. If staff apply a voucher to the wrong check and void the payment, does the balance return? Who can perform the correction, and is there an audit record? What happens when a voucher is issued or redeemed at another location? Ask the vendor to demonstrate the cases your restaurant actually expects to encounter.
Finally, confirm the devices, user permissions, processor requirements and support response included in the quote. Review POS hardware needs alongside the workflow, especially if scanning is part of your process. A live service pilot, if you choose one, comes after the simulated checks and needs an approved procedure for real transactions, staff escalation and reconciliation. It is different from practice: real guests and payments may be involved.
Next step: Prepare your voucher rules and acceptance criteria, then request a Fleksa POS demo using the worksheet. Ask the team to show the screens and reports for your scenario and note any open questions before deciding.
Frequently asked questions
Is redeeming a voucher the same as making a new sale?
Redemption applies prepaid value to a later check. The meal may be a sale, but the voucher amount applied should not create an additional meal sale. Confirm the reporting and accounting treatment with your vendor and accountant.
What if the voucher is worth more than the check?
Decide whether your policy permits partial use. If it does, ask the vendor to show the remaining balance and how the guest can use it later. If it does not, agree on the staff action and guest message before accepting vouchers.
What should staff do if a voucher cannot be validated?
Follow a written fallback, such as pausing redemption and asking a manager to check the record. Do not assume the voucher is valid or replace it with a discount without an approved process.
