opportunity / idea_filter — YES, but only as an exception layer, not as legal-compliance software or a full tip-payout system. The hypothesis is supported: restaurant and hospitality tip workflows now combine POS tips, declared cash tips, credit-card tips, pooled tips, tip-outs, automatic gratuities, service charges, role eligibility, hours worked, shift review, and payroll exports. The sharp wedge is a payroll-close exception queue that says: “these tips/pay codes reconcile; these do not; here is the evidence and proposed adjustment before payroll is finalized.”
Build a POS/payroll-adjacent exception queue for restaurants, bars, cafés, salons, and hospitality bookkeepers that reconciles tip pools, tip-outs, service charges, auto-gratuities, cash tips, shift-role rules, and payroll exports before pay runs create employee disputes.
Best first ICP: restaurant payroll/bookkeeping providers and fractional controllers serving 10-100 tipped-workforce clients. They see the same messy close process repeatedly, can justify a workflow tool if it saves review time, and can bring multiple locations under one buyer relationship.
Second ICP: independent restaurants, bars, cafés, salons, and multi-location hospitality groups using Toast, Square, 7shifts, Homebase, Gusto, ADP, or a POS/payroll patchwork without a clean tip-reconciliation control room.
Good-fit operators have:
Bad-fit operators are single-location, low-tip-volume shops where each employee keeps their own tips and payroll is already clean through one integrated POS/payroll product.
The strongest buyer vocabulary is not abstract “compliance”; it is operational reconciliation language:
Those phrases point to a practical close workflow: compare the POS/tip-manager/payroll views, identify the reason for the variance, collect the evidence, and either fix configuration/data before payroll or produce a documented adjustment.
1. Toast has an entire support page for tip reporting discrepancies. Toast’s “Get Help With Tip Discrepancies in Reporting” page tells operators to identify which reports they are comparing, such as Payroll Export vs. Labor Summary or Sales Summary. It lists concrete symptoms: Payroll Export tip totals do not match other reports; tips on the Payroll Export are lower than what the employee took home; the Payroll Export shows zero tips for an employee who worked a tipped shift; auto-gratuity from a large party is not on shift review; and there is a “specific dollar discrepancy you can’t reconcile.” That is almost a product requirements document for an exception queue.
2. The failure modes are operational, not just legal. Toast attributes discrepancies to open shift reviews, employees not clocking in or being auto-clocked out, tips added or adjusted after shift review closed, report timing, voided transactions, and account-level configuration. These are exactly the types of exceptions a queue can detect and route before payroll, without trying to be a legal-advice engine.
3. Toast’s non-Tips-Manager workflow validates the messy handoff. Toast’s “Pool Tips and Tipping Out” article describes restaurants using negative declared cash tips for ad-hoc redistribution, percentage tip-outs by sales category, pooled-tip reports, and online order tip distribution. It explicitly says the tip-out action is a manager workflow and that when negative declared cash tips are involved, the manager reports a net tip number per employee to payroll. That is a reconciliation chokepoint: human action, cash movement, payroll reporting, and potential employee misunderstanding all meet in one place.
4. Toast Payroll’s tip processing page confirms multiple pay-code paths. Toast says tips, service charges, and mandatory gratuities look similar on a check but are taxed and reported differently. It describes payout settings for non-cash tips and gratuities/service charges; whether employees receive them on paycheck/direct deposit; whether employees must declare cash tips in shift review; and whether declared cash tips appear under Tips Paid or Tips Owed. The page also says there are three ways to move tips from POS to Payroll: Toast Tips Manager for pooled tip-outs, direct sync for each employee’s own tips with no pooling, and manual entry. That complexity creates room for mismatches even inside a single vendor ecosystem.
5. Service charges and auto-gratuities are a repeated source of confusion. Toast’s service-charge page says the key setting is “Assign to check owner (Gratuity?)”: if yes, the charge becomes mandatory gratuity / auto-gratuity; if no, it is an employer-kept service charge. Toast’s discrepancy page separately says auto-gratuity from a large party is a service charge, not a tip, and may not appear under tip earning codes. That supports a product feature that classifies charges, shows where they should appear, and explains why they do or do not hit payroll.
6. Square validates role/hour-based tip allocation in another mainstream POS. Square’s tip pooling support says tip pooling can equally divide credit-card tips across tip-eligible team members clocked in at the time of transaction, include Order partner tips, pool by hours worked, and allocate tips by job with percentage amounts that must add up to 100%. This confirms the same reconciliation dimensions outside Toast: clocked-in status, tip eligibility, job/role, transaction timing, and percentage totals.
7. 7shifts validates payroll-export demand and time-savings claims. Search-result snippets from 7shifts support say its Tip Pooling combines custom tip rules with POS or 7punches data to automatically calculate tip distribution. Its integration settings page says 7shifts can include tip data in payroll sync or as a new column in a CSV payroll export. Its Toast POS tip-pooling page claims operators can save up to 8 hours per week managing the tip pool with custom rules, automatic calculations, comprehensive reports, and payroll export options. Even if a new tool does not replace 7shifts, this validates willingness to pay for tip workflow automation.
8. Payroll and accounting guidance confirms the tip/service-charge distinction. Horizon Payroll says tips and service charges can look similar on a guest receipt but are handled differently for payroll and tax reporting; it gives an example of a server with cash tips, credit-card tips recorded in the POS, and a required tip-out where payroll needs a clear method for recording total tips received and distribution rules. Baker Tilly says managers/supervisors/owners cannot participate in tip pools, allocation should be based on hours worked, a point system, or another reasonable/equitable method, and employees should be notified how the tip pool is administered. These sources validate that evidence and policy documentation matter, but the product should stay focused on workflow and audit evidence rather than giving legal advice.
9. Competitors already sell adjacent automation. Gratuity Solutions markets an end-to-end platform from POS ingestion to calculation, validation, payout, payroll export, reporting, and audit, with credit-card tips, cash tips, service charges, online-order gratuities, to-go tips, and driver tips. Agendrix markets tip pooling by role, hours worked, points, or percentages and says distributed amounts sync directly to payroll. TipHaus, Fourth, 7shifts, and Square all validate a paid category around tip pooling / payout / payroll export. The opportunity is not that no one automates tips; it is that many SMBs still need a lightweight exceptions-and-evidence layer across tools.
10. Regulatory basics make the workflow high-stakes, but not compliance-only. The U.S. Department of Labor’s FLSA tip guidance says employers may not keep employees’ tips, managers/supervisors generally may not participate in tip pools, and employers using mandatory tip pools must maintain payroll or other records of tipped employees and amounts reported. That raises the cost of sloppy records, but the strongest wedge remains operational: prevent payroll mismatches and employee disputes before they become legal or morale problems.
Build a CSV/API-first exception queue, not a full payout rail.
1. Import POS/tip data: employee, role/job, clock-in/out, service period, check/order IDs, sales category, card tips, cash tips declared, online-order tips, service charges, auto-gratuities, voids/refunds, and late adjustments.
2. Import payroll export or payroll preview: employee, pay period, earning code, Tips Paid, Tips Owed, gratuity/service-charge wage codes, cash tips, and net tip allocation.
3. Import policy/rule table: eligible roles, excluded managers/supervisors, tip-pool method, pool interval, points/percentages, tip-out rates, location, event/banquet rules, cash-tip declaration policy, and service-charge handling.
4. Match expected allocations to payroll-ready amounts by employee, shift, role, pay period, and location.
5. Flag exceptions:
6. Give each exception a status: clean, needs manager review, needs payroll adjustment, waiting on employee declaration, configuration issue, policy exception approved, or unresolved.
7. Export payroll-ready adjustments and a dispute/audit packet: source rows, policy rule applied, manager approval, employee-facing explanation, and proposed earning-code correction.
8. Start with Toast/Square CSV templates plus generic Gusto/ADP payroll exports; defer write-back integrations until the exception logic proves value.
A credible demo: “Imported 146 shifts and $18,420 of tips/service charges; 129 clean; 9 open shift reviews; 3 auto-gratuities mapped to tip code; 2 employees auto-clocked out; 2 negative cash tip-outs need approval; 1 manager role included in pool; payroll adjustment CSV ready.”
Toast Tips Manager / Toast Payroll. Strong incumbent when the restaurant is fully inside Toast and configured correctly. But Toast’s own support content shows discrepancies still happen and operators must compare reports, inspect shift review, and gather details before support.
Square tip pooling. Handles tip pooling for eligible team members clocked in at transaction time and role/hour distributions. A focused exception queue would not replace Square; it would reconcile Square output against payroll/export rules and document why exceptions occurred.
7shifts Tip Pooling / Tip Management. Strong adjacent competitor with custom rules, POS/time data, payroll sync, and CSV payroll export. The wedge against 7shifts is cross-stack exception handling for bookkeepers managing many clients, especially when POS, scheduling, and payroll are not all standardized.
Gratuity Solutions, TipHaus, Fourth, Agendrix, Instant, Kickfin. These validate the category but may be heavier enterprise/payout/payroll workflow products. A new product should avoid “complete tip automation” and sell the narrower unresolved-exception queue.
Payroll providers and restaurant accountants. Many will solve this as a service with spreadsheets, exports, and checklists. They are both competitor and channel; the product must make their review faster rather than threaten to replace their judgment.
Spreadsheets and manager memory. The true incumbent is a spreadsheet plus a manager explaining tip-outs after the fact. The product wins if it creates a repeatable, employee-facing evidence trail without asking restaurants to rip out POS/payroll tools.
What might be wrong or overstated:
A focused tip/payroll exception queue is a practical SMB ops wedge with recurring pain, visible admin burden, and a believable service-provider distribution path, but integrations and incumbent absorption are real constraints.