Service charge and tips in one card transaction — why most providers can't do it

Ask most restaurant operators how their service charge works and you'll get one of two answers: "it goes through the till and we distribute it later" or "honestly, I'm not entirely sure." The service charge is often the largest source of pooled revenue on the table — and frequently the most poorly handled.

The EATA position on service charges

Under the Employment (Allocation of Tips) Act 2023, a mandatory service charge must be passed to workers in full with no deductions. An optional service charge — one that customers can remove — has more flexibility, but the allocation must still be fair, documented, and paid on time.

The distinction between a tip and a service charge matters for tronc treatment too. A service charge is not automatically tronc-eligible in the same way a tip is. Whether the NIC exemption applies depends on how the service charge is characterised and how the tronc is structured.

Why taking both in one transaction is hard

Most card terminals process a single payment amount. If a bill is £80 and the customer wants to add a £10 service charge and a £5 tip, most systems require either two transactions (awkward) or a single combined amount with no distinction maintained in the data (problematic for audit and allocation).

Maintaining the distinction at the point of payment — so the service charge routes to the venue's tronc and the tip routes to the named worker — requires the terminal software, the payment split logic, and the tronc engine to be integrated. Most tipping-only providers don't have the payments layer to do this cleanly.

How Tip4 handles it

Tip4 is built on Payment Guru's payments infrastructure, which means the split settlement logic is native rather than bolted on. Service charge and tip are taken in a single customer-facing transaction, distinguished at source, and routed separately — service charge to the venue's tronc, tip to the worker pool — with a full audit trail per transaction.