What a Restaurant's Tip and Service-Charge System Must Get Right in Washington

In Washington there is no tip credit, so the system that moves money to your staff has a different job than it would in most states. It has to pay every hour at the full local minimum in cash, then put tips and service charges on top — and it has to tell the difference between the two, because a distributed service charge is wages and a tip is not.

For a Seattle restaurant group, a tip-and-service-charge system has to get four things right: pay the full Seattle minimum as a cash wage, keep every tip with employees and out of managers' hands, route the disclosed share of any automatic service charge to the staff who served, and treat the service charge you distribute as wages that raise the overtime rate. Then it has to pay all of it by the regular payday.

Most of that can be configured in a modern POS and payroll stack. The rest — who counts as a supervisor, how the pool is split, what the menu discloses — stays a management decision no software should make for you. This guide separates the two.

See how a restaurant group can route finance exceptions to a person for review.

A tip and a service charge are not the same money

A tip is money a customer chooses to leave; a mandatory charge you add to the bill is not. The U.S. Department of Labor is explicit that "a compulsory charge for service ... is not considered a tip" (DOL Fact Sheet #15). That one distinction drives almost everything your system does downstream.

Tips belong to the employee. Under the Fair Labor Standards Act an employer may not keep any portion of employees' tips for any purpose, and managers and supervisors may not receive tips from a pool — they may keep only tips for service they personally and solely provide. A mandatory service charge is different: once you hand it out, it is wages, which means it counts toward overtime pay in a way tips never do. A system that files both into the same bucket will underpay overtime or misreport tips, quietly, every pay period.

What Washington and Seattle require

Start with the wage floor. Washington does not allow a tip credit: the Minimum Wage Act requires employers to pay "all tips and gratuities" and "all service charges" to employees, and says those amounts "are in addition to, and may not count towards" the minimum wage (RCW 49.46.020). In Seattle the floor is higher than the state's: the Office of Labor Standards set the 2026 citywide minimum wage at $21.30 an hour, up from $20.76 in 2025 (Seattle Office of Labor Standards). Some nearby cities set their own, higher minimums, so confirm the rate for the city where each person actually works.

Service charges carry a disclosure duty. If you add an automatic service charge, RCW 49.46.160 requires you to disclose the percentage that goes to the employees serving the customer "in an itemized receipt and in any menu provided to the customer." The statute defines those employees as "nonmanagerial, nonsupervisory workers" — servers, bussers, bartenders, barbacks, banquet staff and porters. Whatever you do not clearly itemize as the house's share is owed to the staff who served. And all of it — tips and each person's service-charge share — must be paid out by the regular payday for that period.

A worked example: one server, one week

The figures below are a worked illustration with stated assumptions, not a report of any real restaurant's results. Say Maya works at a Seattle restaurant that pays the $21.30 city minimum and runs a tip pool for the front of house.

No tip credit. On a four-hour dinner shift, Maya earns 4 × $21.30 = $85.20 in cash wages no matter how good the tips are. Her credit-card tips flow into the pool and are distributed to eligible, nonmanagerial staff; the restaurant keeps none of it, and the shift manager is not in the pool.

The overtime trap. Now take a full week. Maya works 45 hours, all at $21.30, and the restaurant distributes $120 to her from banquet service charges plus $380 in tips. The $380 in tips stays out of her overtime math. The $120 in service charges does not — it is wages. Her regular rate is (45 × $21.30 + $120) ÷ 45 = $1,078.50 ÷ 45 = $23.97 an hour, so the half-time premium on her 5 overtime hours is 0.5 × $23.97 × 5 = $59.92. A system that mistook the service charge for a tip would compute the premium on $21.30 and pay $53.25 — short by $6.67 that week, and by real money across a year and a roster.

What the system has to do, and what still needs a person

This requirements map is our recommended operating method, not legal advice or a guaranteed outcome. A POS-to-payroll setup that stays compliant in Washington has to:

None of that decides the judgment calls. A person — not the software — still has to classify who is a manager or supervisor by actual job duties, so the pool and the service-charge split exclude the right people; set and disclose the pool's allocation formula before the shift; write the service-charge percentage onto the menu and receipt and keep it current; and own the exceptions — a reopened check, a missing POS export, a banquet billed outside the normal flow — by routing them to a named person instead of letting them vanish. The system enforces the policy; it does not write it.

Where this fits the rest of your stack

Which POS you run shapes how cleanly tip and service-charge data is captured in the first place; our comparison of Toast and Square for restaurants looks at that upstream choice. The pattern here — automate the mechanical distribution, route the exceptions to a person, keep an audit trail — is the same one a restaurant group uses to centralize the rest of its finance operations.