A restaurant POS should let staff identify how a guest paid, but a recorded tender does not always mean the POS processed the money. Cash goes into a drawer. A card payment may run through an integrated processor or a separate terminal. An external voucher may need to be redeemed with its issuer. Those are different money flows, even if each appears as a payment on a check.
Before choosing a system, list every tender you accept, identify who moves or holds the funds, and trace each selection from checkout to the close report. Ask vendors to demonstrate the setup with your devices and ordering channels. If staff cannot select and reconcile a tender accurately, agree on a safe process before accepting it.
Inventory tenders and follow the money
Start with actual payment methods, not the buttons shown in a vendor demo. Walk through the dining room, counter, pickup operation and any other place a guest can pay. Include occasional tenders, such as a paper voucher, that may be easy to forget during setup.
- Cash: The employee receives physical money; the POS records the amount. Decide which drawer or person holds it and who counts it at close.
- Integrated card: A payment processor handles the transaction. Ask how the POS receives the result and where the restaurant can find settlement records.
- Separate card terminal: The terminal and its processor handle the transaction. Ask whether staff must also record the payment manually in the POS and how they match the two records.
- External voucher: An outside issuer may handle redemption or reimbursement. Find out what staff must check, what evidence to retain and where reimbursement appears.
- Other accepted methods: List each one by name. Ask who processes it, whether the POS can label it separately and what record proves it was accepted.
Do not treat a POS sales total, a payment-processing fee and a deposit as interchangeable. Sales describe transactions recorded for the period. A processor report may show card activity and fees, while deposits show money sent to the restaurant. Timing and adjustments can make these records differ. Ask the provider how to trace an individual transaction between them.
Also check where each method is accepted. A tender offered at the counter may not be appropriate for a direct online order. A device may have its own payment flow, and an external voucher may require a separate redemption step. The POS hardware and restaurant integrations you plan to use are part of this decision, not an afterthought.
Test the checkout choices before accepting a tender
Use a vendor demo or a clearly isolated practice environment. Confirm with the vendor that simulated transactions cannot charge a card, send a guest message or dispatch a courier. Do not use a real customer's details. If the vendor cannot demonstrate a method safely, ask for a walkthrough of the setup and sample records instead.
For each tender, have the person who would normally take payment navigate from an unpaid check to the final screen. Ask the vendor to show which choices are visible, what each button means and which steps happen outside the POS. Repeat the walkthrough on each relevant device and channel rather than assuming the choices match.
Hypothetical example: A restaurant accepts cash, integrated cards and an external meal voucher at its counter. It also wants to accept cards for direct online orders. In a simulation, a cashier enters a fictional $24 meal and chooses cash. The POS records $24 as cash; the practice transaction does not put money in a drawer. The cashier then enters a separate fictional $24 meal and selects the voucher. The POS may record that selection, but the restaurant still needs to establish how the issuer validates and reimburses the voucher. Neither practice entry proves that funds moved.
Next, ask for an unsupported method. If the restaurant wants to accept a voucher the system cannot identify separately, can a manager add a clearly named tender? If not, can the vendor offer a reliable alternative that preserves a distinct record? A generic button is not a good substitute if it leaves the close owner unable to tell which issuer owes the restaurant money.
Then simulate a staff selection error. Ask what happens if a cashier chooses cash when the guest intended to use a card. Can the employee return to the selection screen before completing the check? If the entry is completed, who can correct it, and does the record show what changed? This is a setup and permissions question: agree on the intended workflow before service, rather than relying on staff to improvise.
Ask about restrictions as well. Can a tender be limited to certain devices, locations or roles? Can its display name be changed without changing historical reports? Where the answer is no, decide whether training and a documented close procedure are enough, or whether the limitation makes that tender unsuitable for your operation.
Compare the receipt, shift report and close report
A clear checkout button is only the start. For each simulated transaction, request the receipt, the employee or shift report, and the restaurant's end-of-day close report. Read the tender name on each. A cashier may recognize a button called “Meal voucher,” while the close report groups it under “Other.” That grouping can make reimbursement harder to check.
Trace the same fictional check through the records. Does the receipt identify the tender accurately? Can the shift lead see it in the appropriate employee or drawer totals? Does the close report separate it from cash and card? Ask whether the report can be filtered or exported in a form the person reconciling it can use.
For integrated card payments, ask the vendor to show how a POS transaction is matched to a processor transaction and, later, to a deposit. For a separate terminal, ask which reference appears on both records, if any. For a voucher, identify the issuer's redemption record and the person responsible for checking reimbursement. A POS entry alone does not establish that an outside issuer has paid.
Pay attention to timing. The shift report and the processor's settlement period may use different cutoffs. A deposit can also cover a different period from a restaurant's close. Ask how the close owner should document those differences rather than forcing the totals to match by changing a tender label.
When comparing quotes, keep the processor's quoted fees separate from the broader operating cost of the payment setup. Ask about fixed charges, transaction-based charges and exception charges, such as those associated with a dispute, as well as any separate terminal or service costs. A quote for processing alone is not an all-in operating cost. The restaurant POS cost guide offers a broader framework for reviewing payments and reporting costs.
Build a tender matrix and assign controls
Use one row per tender and payment flow. The sample below continues the hypothetical counter operation; it is a requirements sheet, not a claim that any particular POS supports these settings. The permissions and locations column records the intended control. The final column names the close owner and the question to resolve with the vendor or voucher issuer.
| Tender and money flow | Permissions and locations | Receipt and report label | Owner and open question |
|---|---|---|---|
| Cash: staff receive and hold funds | Cashiers at counter; manager approves completed-entry changes | Cash on receipt, shift and close | Shift lead counts drawer. Can changes be restricted and reviewed? |
| Integrated card: processor handles funds | Counter and direct online ordering; confirm device access | Card, separately visible from cash | Close manager matches processor activity. What reference links the records? |
| External voucher: issuer handles redemption and reimbursement | Counter only; trained cashier accepts it | Named voucher, not a generic cash label | Close manager checks issuer records. Can this tender have a distinct label and report total? |
| Unsupported method: no approved money flow yet | Do not offer until setup and procedure are agreed | No substitute label approved | Owner resolves with vendor. Can it be represented accurately at every relevant location? |
Review the matrix with both the person who trains cashiers and the person who closes the books. They may need different controls: a short, unmistakable button name at checkout and a more detailed breakdown in reporting. Document who can create or rename a tender, who can make a completed-entry change and who reviews those changes.
Then compare vendors against the same requirements. Toast lists restaurant POS, hardware, online ordering, payments, KDS and integrations. Square offers restaurant point of sale and related payment and order tools. Fleksa offers a restaurant POS connected with direct ordering, reservations and related tools. Ask each provider to demonstrate your tender flows rather than treating those general product descriptions as proof of a specific configuration.
Request written answers for any unresolved items, including supported devices, processor choice, contract terms and the cost of the proposed setup. If a provider cannot give a separate label or a usable reconciliation record for a tender, decide whether an agreed manual process is practical. If no one can reliably identify what was accepted and who owes the funds, do not introduce that tender until the gap is resolved.
For your next step, bring the matrix, your devices, ordering channels and fictional scenarios to a restaurant POS system demo. Ask the provider to show checkout and the resulting records for each row, then assign an owner and a decision to every open question.
Frequently asked questions
Does recording a card payment mean the POS processed it?
Not necessarily. A POS may record a payment handled by a separate terminal. Ask which system processes the transaction and how its record matches the POS entry.
Should every voucher have its own tender label?
A distinct label is useful when different issuers require separate redemption or reimbursement checks. Ask whether the label also appears separately on the receipt and close report.
Who should be allowed to change a payment type?
Set permissions around your staffing and close process. At minimum, decide who can change a completed entry, who reviews the change and whether the report preserves a clear record of it.
