How payroll works in restaurants

1. What actually gets calculated at the end of the month

Restaurant payroll does not start with the rota alone. It starts with actual worked time, then turns that into a clear pay statement with base pay, any premiums, deductions, and special cases separated properly. In Germany, when wages are paid, the employer generally has to provide a pay statement in text form showing the pay period and the composition of the pay, including supplements and deductions, under Section 108 of the Trade Regulation Act. If nothing has changed since the last proper statement, an identical new one may not be required. That legal rule matters because payroll is not just a bank transfer; it is an explanation of how the amount was built.

In restaurants, the sensitive part is rarely the bare total of hours. It is the mix of early setup, closing work, real breaks, covering for a colleague, late-night portions of a shift, tip handling, and occasional corrections. A typical example would be a server planned from 4:00 p.m. to 11:40 p.m., who actually starts mise en place at 3:42 p.m. and stays until 12:05 a.m. because a large group leaves late. Those deviations decide whether payroll feels fair. That is why I treat payroll as a controlled process from the beginning of the shift, not as an office task that magically gets solved at month-end. If I only reconstruct it four weeks later, I create avoidable disputes and repeated correction rounds.

2. Which data I need first before anyone calculates pay

Before any payroll software can calculate anything, I need a reliable base record for each employee: employment type, agreed hourly or monthly wage, area of responsibility, possibly a working time account, and the actual recorded times. In Bonzumo, the practical help is the combination of shift planning, time recording, working time accounts, and roles with permissions. The rota shows what was planned; the time clock records the start and end of personal sessions; exceptions can be reviewed instead of guessed from memory. That is far more useful than loose chat messages when somebody switches between bar, floor, and closing duties. You can also get a good overview in staff scheduling and time tracking.

The order matters. First record, then review, then approve, and then make the approved data available to the tax adviser or payroll office or hand it over directly. I therefore do not let every shift lead rewrite hours freely. I assign rights according to responsibility. For example, a newly promoted supervisor may flag a missing clock-out, but should not silently overwrite an employee’s monthly total. Bonzumo supports that separation through distinct roles and action permissions. For me, that is not mistrust of the team. It protects everyone involved. If a question comes up later, I can check the specific exception instead of staring at a corrected total with no clear reason behind it.

3. How I turn shifts into payable hours

Turning restaurant shifts into payable hours is detailed work. I distinguish between the planned shift, the clocked presence, and the paid working time. A common situation is this: someone clocks in punctually at 10:55 a.m., works the lunch rush normally, but takes a longer real break than planned because business drops sharply between 2:30 and 4:00 p.m. For payroll, I do not simply use the rota; I use the actual time after checking it against our rules. I apply the same logic to closing work. If a cook is still cooling stock, cleaning down, and documenting handover after the last order, paid time does not end when the last guest leaves the dining room. Otherwise I would wrongly treat only visible guest service as work.

This is exactly where Bonzumo helps with preparation, but not with the legal payroll calculation itself. The time clock, exception handling, and working time accounts give me a clean data basis; wage tax, social insurance, and the formal pay run remain separate professional processes. I use that structure very practically. On the next day, the responsible person reviews open anomalies, such as a forgotten clock-out crossing midnight or a shift that looks unusually short. Only after that do approved time records go into payroll. In daily operations, this is much fairer than broad month-end corrections, because a Tuesday evening from three days ago can still be checked concretely instead of appearing later as an unexplained difference of 1.75 hours.

4. Premiums, tips, and other items people often mix together

Many payroll conflicts start because people understandably put everything into one mental bucket: wages, premiums, tips, reimbursements, holiday pay, maybe an advance. For payroll, I separate these items strictly. If premiums exist under the contract or company rules, they need to appear as their own pay components. Tips are a different matter. Genuine voluntary employee tips paid by third parties can be tax-free under Section 3 No. 51 of the Income Tax Act. That does not mean every amount connected to the till is automatically normal taxable wages, and it also does not mean the POS system decides what a fair internal distribution rule should be. I set that rule separately and explain it in writing.

A simple restaurant example makes the distinction clearer. A table pays 100 euros of sales plus 8 euros in tip. For the cash process, sales and tip must remain separate amounts. Bonzumo supports exactly that in the payment flow, so I can later see what was revenue and what was entered as tip. That practical separation helps when I reconcile the day and when staff ask how a number appeared. But it still does not answer who is entitled to that tip internally, whether there is a tip pool, or how the pool is shared. That is an organizational decision I make as operator. For the payment side itself, a clean process matters most, and that is the same principle behind a clear payment experience: record correctly first, assign fairly afterward.

5. Which deductions usually appear on a restaurant payslip

When employees look at their first payslip, the biggest surprise is often not the number of hours but the deductions. I explain early that wage tax and social insurance are not the same thing. Wage tax is a tax deduction on taxable pay. Social insurance is a separate block of deductions. In Germany, as of 30 September 2026, ordinary social-insurance employment generally includes pension insurance at 18.6% and unemployment insurance at 2.6%, usually split equally between employer and employee. Statutory health insurance has a general rate of 14.6% plus the individual insurer’s supplementary contribution; the published 2026 average supplementary rate of 2.9% is not a uniform rate for every fund. Those figures come from the German Pension Insurance values for 2026 and the Federal Ministry of Health overview.

There is also long-term care insurance at generally 3.6%. The childless surcharge, child-related reductions, and a different basic split in Saxony can change the employee share, as explained by the German Pension Insurance guidance on contribution rates. That is why I avoid promising a net wage too casually. Two servers with the same gross pay can still receive different net amounts because of their health insurer, insurance status, or personal tax characteristics. Minijobs follow their own logic as well; for 2026, the average monthly earnings limit is 603 euros according to the Minijob Centre. In practice, I therefore separate time review inside the restaurant from the specialist net-pay calculation done in the payroll process.

6. How I organize the month so payroll does not turn into a recurring argument

Payroll works best in my restaurant when every week contains a small review point instead of the whole month ending in one large drama. I want open time issues clarified within a few days: a missing clock-out, the wrong shift selected by mistake, a shift swap without a note, or a break that happened differently from the plan. Take this example: someone spontaneously stays another 45 minutes to polish glasses and complete the cash handover because the later colleague calls in sick. If that extra work is documented immediately, it becomes a normal payroll record. If it is not, it becomes a memory dispute. In restaurants, closeness to the actual event is worth a great deal because four weeks later almost nobody remembers why one Thursday ran 50 minutes longer than usual.

Fairness also means employees understand when a change is professionally justified and when it is not. I do not cut time simply because sales were weak that day. On the other hand, an early clock-in is not paid automatically if the actual work started later. What matters is documented working time and the rules of the business, not who argues louder. Bonzumo supports that indirectly through traceable time data, working time accounts, and permission structures. The real fairness still comes from the process I enforce: timely review, clear responsibility, visible rules, and one payroll logic applied to everyone. That creates calmer conversations because I can point to a checked shift record instead of relying on personal recollection from a busy Saturday.

7. What I hand over, what I check myself, and where the limits are

At month-end, I do not hand over a loose spreadsheet of hours. I hand over a checked package: approved times, understandable exceptions, clearly marked special pay components, and, where relevant, notes on minijob status, health insurance, or employment category from personnel administration. That lets the tax adviser or payroll office continue the formal payroll process on a clean basis. This is where I draw a very deliberate line between preparation and payroll itself. Bonzumo can structure my team and time data, but it does not replace a full wage tax or social insurance payroll calculation. Being explicit about that limit is not a weakness. It prevents false expectations and reduces mistakes in sensitive reporting topics where specialist payroll responsibility still matters.

For employees, I put it simply: your payslip comes from correctly recorded and reviewed time, clearly separated pay components, and the legal deductions that apply in your case. If something looks wrong, we first look at the concrete shift history, not just at the final number. Guests feel the effect indirectly as well, because a fair personnel process leads to calmer service, more reliable handovers, and fewer internal disputes during the shift. The most important lesson for me as an operator is that good restaurant payroll does not begin in a tax office program. It begins inside the restaurant itself, with honest time recording, clear roles, and the discipline to solve small uncertainties immediately instead of carrying them for four weeks.