DECCANPRO — RESTAURANT SPLIT-PAYMENT REHEARSAL
Companion: https://deccanpro.com/guides/restaurant-split-payment-checklist/
Use fictional records in a supplier-approved test environment, outside live service.
Do not collect real payments or enter customer, bank or card details here.

SESSION
Restaurant / date / cashier / observer:
Installed version / device / enabled payment methods:
Who explains unsupported steps and approves the service procedure:

1. WRITE THE REQUEST BEFORE CHOOSING A WORKFLOW
Requested outcome (choose one for each independent run):
[ ] One bill, different payment methods
[ ] Equal amounts paid by two guests
[ ] Separate itemised bills for different dishes
Supported procedure demonstrated / limitation to record:
Start a fresh training order for each branch below. Never add the branches together.

2. COMMON FICTIONAL ORDER
Two meals at Rs.200 each = Rs.400.
Two coffees at Rs.50 each = Rs.100.
Item subtotal = Rs.500; total preparation = two meals and two coffees.
These practice figures exclude taxes, discounts and other adjustments.
For a configured bill, record the actual final payable amount and recalculate
the shares before saving. Do not change live tax settings for this exercise.

BRANCH A — ONE BILL, TWO METHODS
Expected allocation: Rs.200 cash + Rs.300 enabled digital method = Rs.500.
Practice cash tendered: Rs.500; expected change: Rs.300.
The cash share remains Rs.200, not Rs.500.
Observed final payable / cash share / digital share:
Observed tendered / change / where these are recorded:
Saved bill reference / payment-method breakdown checked after reopening:
Merchant-side confirmation procedure demonstrated with test evidence:

BRANCH B — TWO EQUAL SHARES
Expected shares: Rs.250 + Rs.250 = Rs.500.
Guest A's method / amount / test receipt reference:
Guest B's method / amount / test receipt reference:
How staff distinguish the two receipts in the demonstrated process:
Saved record reference / observed total received:
If both use the same method, a Rs.500 method total alone does not prove
that both separate receipts were confirmed. Record the evidence actually shown.

BRANCH C — SEPARATE ITEMISED BILLS, IF SUPPORTED
Requested bill 1: two meals, subtotal Rs.400.
Requested bill 2: two coffees, subtotal Rs.100.
Original order reference / resulting bill references:
Observed bill 1 items and quantities / subtotal / final payable:
Observed bill 2 items and quantities / subtotal / final payable:
Across both: exactly two meals and two coffees? yes / no / unresolved
Original record's final state explained? yes / no / unresolved
If unavailable, write the limitation and agreed alternative. Two payment
entries on one unchanged bill do not demonstrate separate itemised bills.

3. KITCHEN OBSERVER — CHECK EACH BRANCH
The payment request does not order more food.
Preparation instruction before the billing change:
Any new print or screen instruction after the change:
What the extra output means / who explained it:
Could staff mistake it for fresh preparation? yes / no / unresolved
Do not re-enter dishes as new orders merely to obtain another receipt.

4. MISMATCH REHEARSAL — SEPARATE TEST RECORD
Rs.200 + Rs.250 = Rs.450: Rs.50 short of the Rs.500 practice bill.
Rs.200 + Rs.350 = Rs.550: Rs.50 above the Rs.500 practice bill.
Observed response to each mismatch / allowed next step:
How an unresolved or pending payment is handed over:
Responsible staff member / reference / next check:
Return to the correct allocation before completing a successful test.

5. RESULT AND RETEST
Branch / expected result / observed result / evidence reference:
Outcome: demonstrated / unsupported / failed / not tested
Issue / owner / agreed correction:
Fresh retest reference / result / reviewer / date:
Do not mark an untested branch as passed because another branch worked.

This worksheet is a demonstration record, not proof of automatic payment
verification, invoice splitting, kitchen suppression or bank reconciliation.
No sign-up is needed. Keep completed business records private.