When one table bill becomes several payments
Four guests are sharing a table. Two want to pay for their own meals, one offers to cover the shared bottle and the fourth needs an invoice for work. A single order has turned into several payment decisions. A split bill works only when each person understands what they are paying and what remains afterward. Bonzumo offers both item-based splitting and equal shares. Choose between them according to the conversation at the table, rather than a default selection on the register.
During a busy shift, the connection to the original table matters. Servers should not have to write new totals on paper and later match them to several payments. The current transaction needs to serve as a shared point of reference. Before the first part is charged, clarify the ordered items, shared dishes and document requests. After every confirmed payment, read the remaining amount. This simple sequence is easier to teach than a collection of improvised rules for different group sizes.
Item splits and equal shares answer different requests
With an item split, the team chooses the products a person is paying for. That works when guests can identify their orders. A bottle for everyone, a shared dessert or a starter for two needs a deliberate agreement, though. Selecting the individual mains while leaving a shared item until the end only moves the problem. With equal shares, the agreed total is divided by the chosen number of people. That is often simpler for a group that does not want to settle every item separately.
The same table can produce very different results depending on the chosen method. Let the guests decide before the first transaction. Ask about shared items explicitly and say the amount aloud before payment. Bonzumo keeps the chosen division in the payment context. For an introduction, use typical cases from your venue: a lunch table with separate drinks, a group sharing a bottle and a business meal with one invoice request. Colleagues learn the decision behind the screen, not just the sequence of controls.
After each part, the balance matters most
Once the first person has paid, the original table total is no longer the most useful answer to what remains. The team needs to know which items or shares are settled, which payment was confirmed and what is still due. If the server is called away, another colleague should be able to take over. Saying that two guests have already paid does not give enough information. A specific remaining balance and the status of each partial payment do.
This distinction is especially important with cards. A terminal request that has started must not be treated as a confirmed part payment. If its response is uncertain, check that part first. Only then should the next guest pay or the same part be attempted again. This protects guests against duplicate charges and keeps the balance explainable. In training, deliberately discuss an interrupted card attempt: who checks it, what is recorded and what does the waiting table hear?
Ask for each person's tip choice
A group does not have one shared tip preference unless it has agreed one. One person rounds up, another chooses a percentage and a third pays without a tip. Bonzumo supports different tip entries within the payment flow. With each part, the server needs to see whether the displayed amount is the sale alone or already includes a voluntary extra amount. Opening the next part must not silently carry over the previous guest's choice.
Consider three people paying equal shares. The first uses a card and adds a tip; the second pays cash without one. The amount remaining for the third is that guest's agreed share plus any tip they personally choose. The receipt, confirmed transaction and later tip information need to tell the same story. Your internal rules for distributing tips are a separate business decision. A bill-splitting screen cannot replace an explicit team arrangement or advice on the accounting treatment of tips.
Collect invoice requests before starting
Split payments soon raise a document question. Who needs only a receipt, who needs an invoice with recipient details, and which items belong on that invoice? Ask before splitting begins. Otherwise, after three payments, colleagues may need to reconstruct which guest took which part. Bonzumo includes an invoice dialogue with editable recipient fields and a manual entry route. The precise document and delivery options should be checked for the venue's configuration.
A business invoice makes a useful practice case. Ask a colleague to clarify the request at the table, select the related items and enter the details in the intended flow. Another colleague should then be able to explain which payment belongs with which document. That matters more than fast typing. Confirm mandatory tax details and exceptions with your adviser for your business; the operational assignment of sale, payer and document should already be clear to the team.
Carry the split through handover and closing
A divided table bill may involve cash, a card, a voucher and several tip decisions. At the end of the day, managers and accountants need more than the original table total. They need to understand the confirmed payment steps that make it up and whether a part remains open. Bonzumo connects payment and closing contexts. The reports, exports and device connections available to your business must be agreed specifically. It starts with selecting the correct payment method at the point of sale.
If a shift changes before everyone has paid, hand the table over clearly. Do not close it as a precaution simply because several guests have left. Keep the remaining amount and any unresolved payment visible, and tell the next server about pending document requests. A demo with a group that has paid only half the bill tests this directly. When everyone involved can explain the same current state, later questions at the table and during closing become easier to resolve.
Test a realistic split bill in a Bonzumo demo
Bring a sample bill that resembles one from your restaurant, without real guest information. Include several drinks, different meals and at least one shared item. Ask first for an item split, then run a separate exercise with equal shares. Add different payment methods and tip wishes. After each transaction, ask what remains due. This turns a feature labelled split bill into a service routine that everyone can explain.
Finally, have another person take over without describing the conversation that preceded the handover. They should use the transaction to explain what has been paid, what still needs checking and which invoice is pending. This is the benefit of connecting checkout and payment. It reduces manual calculation, but just as importantly it helps the team continue an agreed decision under pressure without guessing at the table.