Search articles

    All Gastrokompass articles →

    Details

    Weekend work in hospitality: how is it paid?

    Does weekend work in hospitality automatically pay more or what legal factors matter?

    Weekend work does not automatically create a premium; entitlement depends on collective agreements, the employment contract or internal company rules. Night work and substitute rest days are subject to statutory regulations, so record shifts and actual hours accurately and use Bonzumo for traceability before each payroll run.

    The basic rule for Saturday, Sunday, and public holidays

    Weekend work in hospitality is not automatically paid at a higher rate. Saturday in particular does not trigger a statutory weekend premium on its own. For Sundays and public holidays in Germany, the position is similar: the Working Hours Act sets protective rules for when people may work, but it does not itself create a fixed extra payment. The Federal Labour Court has made that clear as well: Sunday or public-holiday work alone does not generate an additional pay claim unless that claim comes from a collective agreement, an employment contract, or a clear workplace rule, see BAG 5 AZR 431/16. That means I start with the actual basis that applies in my business, not with rumours from the trade.

    So if a server asks me whether a full Saturday evening must automatically be “paid better,” my honest answer is no, not unless we have agreed that in writing or a collective agreement says so. A practical example helps: two team members each work six hours, one on Friday evening and one on Saturday evening. Without a special rule, the hourly pay is initially the same. I look differently at Sundays, public holidays, and late night hours, because those can involve not just pay questions but also statutory compensatory rest. That distinction matters if I want my team to feel the process is fair rather than improvised around whoever shouts loudest after payroll has been prepared.

    When extra money can actually become due

    In practice, higher pay usually comes from three places: first, a collective agreement; second, the individual employment contract; and third, an expressly defined company rule on premiums. So if someone wants to know what their Sunday is worth, the answer is not hidden in what a friend heard at another restaurant. In hospitality, people often repeat lines like “Sunday is always 50 percent extra” or “after 8 p.m. night pay starts automatically.” Those blanket statements are unreliable unless a valid rule actually says so. As the operator, I have to define in writing which days, time windows, and roles trigger which compensation, otherwise payroll turns into a debate about expectations that were never formally agreed.

    A sensible example would be this: I might decide that in our business Sunday work receives a voluntary premium, while Saturdays remain covered by the normal hourly rate. Or I might distinguish between kitchen closing shifts that run until 1 a.m. and café shifts that finish at 6 p.m. The key is not that every role must receive the same premium, but that the logic is consistent and understandable. It becomes unfair when two comparable late shifts are paid differently simply because one supervisor kept handwritten notes more carefully than another. That is why I formulate premium rules so concretely that the start, end, affected duties, and trigger can still be checked months later without relying on anyone’s memory.

    Night work is the point where the law really matters

    Weekend work by itself is one thing; night work has a specific legal framework. In Germany, night time is generally 11 p.m. to 6 a.m., and night work means working more than two hours within that period under section 2 of the Working Hours Act. If someone qualifies as a night worker and there is no collective compensation rule, they are entitled to an appropriate premium or paid time off under section 6 of the Working Hours Act. The Federal Labour Court often uses 25 percent, and 30 percent for permanent night work, as a starting point for the individual case, not as a universal statutory percentage, see BAG 10 AZR 423/14.

    That matters in hospitality because disputes are often not really about the weekend at all, but about the combination of Sunday service and a late finish. Take a hypothetical bar shift on Sunday from 6 p.m. to 12:30 a.m. I do not only ask “was it Sunday?” I also ask how many hours fell into the statutory night period. If the same person works that pattern regularly, the night-work question quickly becomes more important than the weekend label itself. Fairness starts when I stop throwing all “late shifts” into one bucket and instead assess them according to the actual time windows. That is exactly where confusion arises if rota planning, time recording, and later payroll preparation do not line up.

    On Sundays, time off in lieu is often more important than a premium

    For Sunday and public-holiday work in Germany, the key legal issue is often compensatory rest rather than a pay bonus. Anyone employed on a Sunday generally needs a replacement rest day within two weeks; for work on a public holiday that falls on a weekday, the replacement rest day generally has to come within eight weeks under section 11 of the Working Hours Act. That requirement is not a bonus payment but a worker-protection rule. From my side as a restaurateur, that means a supposedly well-paid Sunday is still badly organised if I lose sight of the replacement rest day or promise it informally without ever putting it into the rota.

    I explain that very plainly to the team: Sunday may come with a premium, but it does not have to; the replacement rest day is a separate point that we still have to handle properly. Here is a typical scenario: a chef steps in for two consecutive Sunday brunches because one colleague is ill. If I only look at the wage line, I miss half the issue. I also need to plan the recovery logic in advance. That is why I separate “money,” “time account,” and “compensatory rest” in our internal rules. Once everything is lumped together under the phrase “weekend pay,” people lose track fast. Most of the later conflict is then caused by weak scheduling and weak documentation, not by the law being mysterious.

    How I would calculate a clear example in the business

    Take a deliberately simple hypothetical case. A server earns 14 euros per hour. They work Saturday from 5 p.m. to 11 p.m., Sunday from 10 a.m. to 4 p.m., and once more on Sunday from 6 p.m. to midnight. Saturday produces, without any special agreement, 6 hours × 14 euros = 84 euros. The Sunday brunch also initially produces 84 euros if no Sunday premium has been agreed. For the late Sunday shift, I then check whether more than two hours fell within the statutory night period from 11 p.m. to 6 a.m. If only the final hour falls into that period, that alone does not yet amount automatically to the legally relevant night work in the sense described above. The classification has to follow the actual clock times, not the mood of the weekend.

    If I choose to grant voluntary company premiums, I write them with the same clarity as a calculation sheet. For example: Sundays plus X percent, legally relevant night work plus Y percent, or paid time off instead of money in the situations we have defined. The order matters: first the base wage, then the type of premium, then the applicable time window, then whether the compensation is paid out or granted as time off. One common mistake is mixing up tips, sales intensity, and premiums. A packed shift with good tips does not replace agreed pay. The amount of a tip and the rules for allocating it are a different issue entirely. If I keep those matters separate, I avoid the dangerous story that “late Sundays pay for themselves through the guests anyway.”

    How I organise it fairly with Bonzumo without overpromising

    Bonzumo does not make the legal decision for me on premiums and it does not produce a finished payroll. What it can do is help me keep the decisive groundwork tidy: shift planning, time recording, roles, and the checking of exceptions. I schedule the relevant shifts in the team area, publish the binding version, and have actual working time captured via the time clock. If someone comes in early for mise en place or stays later because the last table lingers over split bills, that actual recorded time becomes the starting point for any fair premium review. The practical organisational side fits with Give your team a clear start to every working shift, because the rota and the real shift no longer live in separate worlds.

    In day-to-day use, that means the shift lead can see who was planned for the Sunday service, then review exceptions afterwards, such as a forgotten clock-out or a finish that runs past midnight. Roles and permissions help me prevent just anyone from changing time data casually. I then use those recorded times as the basis for discussing doubtful cases with the team before passing clean, understandable figures to payroll or the tax office. The tangible benefit is not “automatic premium magic,” but fewer arguments based on memory. On a busy weekend with terrace service, bar closing tasks, and delayed departures, that reliable data trail is often the difference between a fair payslip and three days of chasing people for handwritten corrections.

    The usual points of conflict and the best way through them

    Most disputes do not start because nobody knows the hourly wage. They start because terms get blurred. Was the last half hour still working time, or were two colleagues simply sitting together after locking up? Does prep before opening count? Does a Sunday shift begin according to the rota or according to the actual clock-in? What happens if the shift runs over midnight? My answer is always operational before it is emotional: I define in writing what counts as working time, what counts as the beginning and end of a shift, how breaks are recorded, and who may approve corrections. Without that groundwork, even good intentions collapse into ad hoc case-by-case politics every payroll cycle.

    For overall traceability during a trading day, I also benefit from Bonzumo’s shared data basis across sale, payment, receipt, and close-out, because it helps me understand why a shift ran long even though it does not calculate wages itself. If I need to check why a Sunday shift extended by 40 minutes, it often becomes clear faster whether late till closing, split payments, or one delayed table caused the overrun. That broader operating context is part of Connect the work behind every successful service. For Germany, as of 30 September 2026, the core answer remains simple: weekend work alone does not automatically mean a premium; what matters are the contract, any collective rule, legally relevant night work, and properly organised compensatory rest.

    More insights

    What Does Restaurant Management Software Cost?The real cost is not just a subscription. I break down software, devices, setup, training, upkeep and transition work with a realistic restaurant example.Restaurant POS system pricing: Comparing cost with real operational valueWhen I compare restaurant POS system pricing, I look at total effort, included services, and my business’s workflow. A practical checklist helps me compare offers clearly.Restaurant POS systems: compare what matters in restaurant workHow I evaluate offers by checking order flow, team routines, closing, and maintenance rather than counting features.Is It Okay to Tip Less During High Inflation?Yes. In Germany, tipping remains voluntary. The fair answer is to separate the bill, service quality and tip pressure, then organize payment respectfully.Employee management software: Giving restaurant information the right access boundariesWhen a vacation replacement needs to organize next week, the real question is not who can see everything, but who needs which information to keep service running. I compare employee management software from a restaurant operator’s perspective: planning shifts and absences, reviewing time questions, giving team members access to their own documents, and ending temporary roles as soon as the responsible manager returns. With Bonzumo, I structure roles, schedule status, time review, and document paths around actual tasks.Reuse Existing Tablets and Order-Ticket Printers?Check existing tablets and order-ticket printers individually: models, software, connections and workstation needs must fit your planned BonZumo workflow.Staff deployment planning tool: The practical checks I use before adoptionI do not test a staff deployment planning tool on a quiet day. I test it when someone calls in sick two hours before service and a group booking is due at the same time. In that moment, I need a clear view of tasks, available people, the published shift plan, and the final closing coverage. This is the practical checklist I use when I discuss Bonzumo with my team and decide which access rights, workflows, and review steps we actually need.How can I stand out positively during onboarding?You stand out in onboarding by learning reliably, asking well-timed questions, and following through cleanly—not by trying to look perfect too soon.Restaurant staff training: Practise around a busy serviceFit restaurant staff training into daily service with short learning windows, one clear case per session and a defined place for follow-up questions.When a More Expensive POS System Pays Off for Your RestaurantA more expensive POS system only makes sense once you can measure its value in your own restaurant: with full costs, a clean test, and real time savings.How Many Clicks Simple Admin Tasks Really NeedGood POS software needs as few steps as make sense for simple admin work, but not at the cost of mistakes. What matters is the full path to a checked, saved change.Hospitality training: Identify the real learning needNot every issue needs training right away. Check whether repeated pass questions come from missing knowledge, unclear tasks or missing information.Holiday rota: Checking agreed absences before releasing the weekly planA weekly plan can look complete and still fail the moment a confirmed absence comes back into view. I use the holiday rota as a fixed review step before I switch a rota from draft to published status. This keeps confirmed leave, open holiday requests, replacement cover, and later time questions in one practical workflow instead of turning release day into a scramble.Buying a restaurant POS system: plan the transition before the old workflow slows you downHow I review sales, kitchen, team, and daily close when changing tills so the switch does not surprise us during service.Excel hospitality staff rota: Agreeing the spreadsheet version before a busy weekBefore a packed week, several rota spreadsheets can circulate at once, each with a different holiday note or copied shift pattern. I describe what happens when the Saturday answer is unclear, why last week’s file causes avoidable staffing risk, and how I move from conflicting drafts to one published plan. Bonzumo fits into this as the team framework for shifts, absences, roles, permissions, and a clear draft and published status, without relying on any Excel connection.Managing Food Cost, Costing and Selling Prices TogetherYou keep food cost, recipe costing and selling prices in view together when purchasing units, recipe quantities and selling prices all rely on the same item data.Bar POS system: Organize service, kitchen, and shift handoffs during a rushHow I structure orders and open tasks as a bar operator so the counter stays clear at peak pace.How I Make Payment Guest-Friendly in My RestaurantGuest-friendly payment means short waits, clear totals, fair splits and a finish that guests and staff both understand immediately.Are You Paying for Features You Don’t Use in BonZumo?Not automatically. What matters is which tasks your business actually needs covered and how the scope, included areas, and necessary dependencies are agreed in the offer.POS system with table management: Plan the restaurant flow from guest to closeHow I review reservation, table assignment, order, kitchen, payment, and daily close as one operating sequence.Restaurant POS system: plan the service journey from greeting to closeHow I make typical restaurant workflows visible and build a shared process for service, kitchen, guests, and management.Which Features Are Available Today and What Is Only PlannedFor your decision, only count what can be shown to you in a real workflow today. Everything else should stay clearly separated as planned or still to be checked.How to Use POS System Comparison Guides WellA useful POS comparison guide sorts systems by your real service flow, payment situations, and handoffs, not by a long list of buzzwords.Restaurant inventory management: Organize stock and purchasing in kitchen operationsHow I structure stock movements, deliveries, and team ownership so shortages become visible earlier.Is Hospitality a Profession With a Future?Yes, if a restaurant offers growth, reliable structure, and real responsibility. What makes hospitality a future-proof profession in day-to-day operations.Working time recording: Seeing preparation and closing work clearlyWhen the dining room is empty, work is often still in full motion. From an operator’s perspective, this article shows how I separate sales time from real working time, discuss preparation, polishing, and handover with the team, and review time data in Bonzumo without reducing the conversation to the first booking or the last payment.Can I Open a Small Restaurant Without Much Experience?Yes, but only if you keep the concept deliberately small, learnable, and financially sober from day one.Burnout Prevention in Restaurants: What Really Helps at WorkBurnout prevention in restaurants starts with workable shifts, clear handovers, real breaks, and managers who stay reachable when pressure rises.What Belongs to Professional Restaurant Service?Professional service is more than friendliness: it combines preparation, timing, clarity, advice, calm problem-solving and a clean finish guests can trust.Understanding Labour Costs in a RestaurantRestaurant labour costs are more than hourly pay. Here is how I calculate them clearly, fairly, and in a way that actually helps decisions.Free vs paid POS systems: which is better for restaurants?Free can work at a very simple counter. Once service gets messy, the real comparison is workflow, follow-up work and operating risk, not just monthly fees.Are variable working hours legal in restaurants?Yes, but not without limits. In restaurants, variable hours can be lawful only when contract terms, planning, breaks, rest periods and fair organisation all fit together.Hospitality hygiene training template: Adapt it with expert helpA hygiene training template should match your own stations. Review it with qualified support and keep the source and date clearly documented.Time tracking and shift planning: Using clear differences to improve next week's rotaTwo Saturday services finish late, but they do not mean the same thing. In one case, recurring closing work is taking longer than the rota allows. In another, the shift likely ended on time and the final clock-out is missing. I use time tracking and shift planning together in our Bonzumo setup to compare planned shifts with personal time sessions, check plausibility before any correction, and make calmer decisions for next week’s rota.Pizzeria POS system: Coordinating dine-in, collection and the kitchenA pizzeria can have full tables, phone orders and collections arriving at once. Here is how Bonzumo can help organize the path from order to daily close.POS system for restaurants: stay on top of things with a small teamHow I structure shift start, a full dining room, and closing so our team does not have to search across scattered information.Delivery service POS system: Connecting order intake, kitchen work, and handoffA delivery service depends on reliable handoffs. I show how I organize the order queue, team responsibilities, and daily close as a restaurateur.Restaurant ordering system: Move orders through service without needless loopsHow I make the route from a guest's order to the kitchen reliable and assess a system against real restaurant work.Process-driven POS: Why connecting every step beats feature-hopping in your restaurantA modern POS's real strength is not a single flashy function but the way order-taking, kitchen, payments, tips, fiscalization and accounting flow as one traceable process. This article shows how to set up and run a process-driven system so your team spends less time fixing inconsistencies and more time serving guests.Best restaurant POS system: decide based on your restaurant’s real workThe “best” checkout system depends on the problems our operation actually needs to solve. I compare concrete workflows and confirmed scope, not promises alone.Best POS system for restaurants: Test service, corrections, and close in daily workHow I assess usability and operational fit from the restaurant team's perspective and test it across real shifts.Bar POS system: How I keep the counter under control during a rushA busy bar runs more smoothly when orders, open checks, team handovers and the daily close follow a clear routine. Here is how Bonzumo’s bar POS system can help.Restaurant inventory management system: Aligning stock, purchasing, and kitchen workAn inventory system for hospitality is useful only when data matches reality. I show how I organize stock, deliveries, menu availability, and team routines.

    Next step

    See how the workflow fits your operation.

    Contact