One restaurant bill. Two payment methods. One clear record.

Start with the final amount due

Complete the agreed order changes and review the final bill before entering payments. Use the final payable amount shown by the demonstrated workflow, including the business settings you have approved. Do not copy an earlier item subtotal into the payment screen.

For a training bill with a final amount of ₹650, agree to allocate ₹200 to cash and ₹450 to the demonstrated digital method. These are fictional practice amounts, not a menu price or a tax calculation. Keep the exercise in a demo environment so it does not create a real sale or charge.

Check the allocation before saving

Ask the cashier to open the multiple-payment workflow and enter the two amounts. Check the selected methods as well as the numbers: ₹200 cash plus ₹450 digital equals ₹650. An amount entered against the wrong method can leave the bill total correct while making the cashier’s breakdown incorrect.

Deliberately try ₹200 plus ₹400 in the demonstration and inspect how the remaining ₹50 is shown or handled. Then try ₹200 plus ₹500 and ask how the excess is handled. Return to the correct allocation before completing the practice transaction. Have the supplier explain validation and any partial-payment procedure instead of assuming either mismatch is a fully paid bill.

Separate cash received from the cash share

If the cash share is ₹200 and the guest hands over ₹500, the change is ₹300. The amount allocated to the bill is still ₹200. Ask the demonstrator to show where the amount tendered and change belong in the supported workflow; do not put ₹500 into the cash share simply because that note was received.

Have a second staff member read the allocation aloud and check the change calculation. In the practice example, the saved payment shares should remain ₹200 and ₹450, matching the ₹650 bill. Repeat using the rounding and denomination routine your restaurant actually follows.

Treat payment confirmation as a separate check

Recording a digital payment method in a POS is not, by itself, evidence of confirmation from the payment provider. Demonstrate the merchant-side confirmation process for your actual setup and agree who checks it. This guide does not claim automatic UPI verification, a bank integration or automatic settlement.

If a payment is pending or disputed, identify the bill and responsible cashier before anyone attempts another collection. Follow the payment provider’s guidance and the restaurant’s agreed procedure. Keep unresolved items visible in the shift handover so the next person does not mistake a recorded intention to pay for a completed receipt.

Reopen the saved bill and review the shift

After saving the correct practice allocation, reopen the transaction through the demonstrated lookup. Verify its bill reference, final amount and available payment breakdown. Ask which report the cashier should use to review payments by method; report labels and available views should be demonstrated for your installation.

For this sample alone, the cash share contributes ₹200 and the digital share ₹450. It does not contribute ₹650 to each method. In a real shift, compare like-for-like records for the same period and account for opening cash, change, refunds and other cash movements through your approved process. Do not treat a payment-method report as a complete bank reconciliation.

Ask which kind of split the guest means

“Split the bill” can describe several different requests. Before choosing a button, ask whether the guest wants to change how one bill is paid, divide the amount between people, or receive separate itemised bills. Record the requested outcome first. A demonstration of one route does not prove the other routes are supported.

Use the same meal to test different requests

Build a fictional training order containing two meals at Rs.200 each and two coffees at Rs.50 each: an item subtotal of Rs.500. This example deliberately excludes taxes, discounts and other adjustments; use the actual final payable amount when demonstrating a configured bill. In the first branch, allocate Rs.200 to cash and Rs.300 to the enabled digital method. That describes payment methods, not which guest ate which dish.

Restart from a fresh training order for the second branch. Two guests want equal shares: Rs.250 each. Agree how those shares will be received and recorded in the supported workflow. If both guests use the same digital method, ask how staff identify and check both receipts. Do not assume that a single Rs.500 payment-method total proves two separate receipts were confirmed, or that the POS stores a separate payer identity.

In a third independent branch, one guest wants both meals and the other wants both coffees. The requested item subtotals are now Rs.400 and Rs.100, rather than Rs.250 each. If separate itemised bills are required, ask for that exact demonstration. Across the resulting records there must still be two meals and two coffees, with no omitted or duplicated item. If the installed version cannot provide the requested bill split, record the limitation and agree the service procedure before accepting that requirement.

Check that a billing change did not order the food twice

The guests have changed who pays; they have not ordered another meal. During the separate-bill rehearsal, have the kitchen observer check for any new preparation instruction. If the demonstrated workflow produces another print, staff must be able to identify its purpose and avoid treating it as fresh food to cook. Follow the supported correction or billing procedure instead of re-entering dishes as new orders merely to obtain another receipt.

Finish by recording the original training reference, any resulting bill references, item quantities and payment evidence. Compare those records with the requested branch: one bill with two methods, equal payment shares, or separate itemised bills. Keep each branch independent so that earlier test payments do not contaminate the next result. This exercise checks the proposed workflow; it does not claim automatic invoice splitting, kitchen suppression or per-person payment tracking.

Record what each branch actually proves

Use the free split-payment rehearsal worksheet linked below with a cashier and a kitchen observer. Start a fresh training order for each request, then record the saved references and observed output. The worksheet separates payment allocation, equal shares and itemised bills so that success in one branch cannot accidentally sign off all three.

Mark each branch as demonstrated, unsupported, failed or not tested. A limitation is a useful result: agree the restaurant’s service procedure before launch. For a failed check, record an owner and a fresh retest reference. Keep customer and payment credentials out of the worksheet; fictional test receipts and training references are enough.

Prepare your Chennai demonstration

For a Chennai demonstration, bring a sample order and tell us which payment methods your cashier needs to record. Test corrections, saved records and the handover procedure with the staff who will use them. DeccanPro’s software plan is ₹6,000 per year with unlimited use and no setup fees or hidden software charges; discuss payment-provider and equipment requirements separately.