
From the point of sale to the payroll file, with the tips shared by rules you can read.
Four restaurants in El Paso, each on its own fourteen-day period. Payroll for a restaurant is punches and tips in the point of sale, plus the shares and sheets the managers keep outside it. The application brings both into each restaurant’s period, computes hours, overtime, pay and the tip pools by rules the owner can read, and produces the payroll file. No model computes a paycheck: the one step an agent carries is reading a photo of a sheet.
The work, every day
Every period, every restaurant, every tip.
Each restaurant closes its own period. The punches and the tips are in the point of sale; the chef’s share, the attendance and the host and bar tips are kept by the managers outside it.
How long does it take to get from the point of sale to a payroll file?
Which punches nobody closed this period, and who fixes them?
Can the owner read the rule that split last night’s tips?
- Bring in the punches and the tipsTime in and out, the rate, the unpaid break, card and declared tips.
- Add what the point of sale does not knowThe chef tip share per station and day, the chef attendance, the host and bar tips.
- Fix the punches nobody closedA missing clock-out lands at the restaurant’s cutoff and is marked for a fix.
- Compute pay and the poolsHours, overtime, pay and each tip pool.
- Produce the payroll fileOne per restaurant and period.
How it flows
Rules where the step needs rules.
The arithmetic is rules: no model computes a paycheck. The one step an agent carries is reading a photo of a sheet a manager uploads.
Payroll
How long does it take to get from the point of sale to a payroll file with the tips shared right?
Punches and tips of the period come in
Adds the chef share, attendance and the host and bar tips
Reads a photo of the attendance or tip sheet into the period
Hours, overtime, pay and the tip pools are computed
One per restaurant and period
What you get
The uploads, the payroll grid and the rules.
The walkthrough shows this desk on a read-only sample of your own data before you sign anything.
The period’s files from the point of sale, the checkout reports and the sheet photos, each loaded into its restaurant and period.
Each employee’s hours, overtime, pay and tips for the period, with every missing clock-out marked for the owner to fix.
Every pool, share and threshold as a rule the owner can read, not a formula hidden in a spreadsheet.
The real screens
The period, as the owner closes it.
The customer's data is blurred. The screens are the application as its people use it.
The receipts
What runs, and what it took.
No outcome number is published for the restaurants. These are the facts of what runs.
Restaurants, each on its own fourteen-day period and with its own payroll file.The application’s own description, read on November 17, 2026.
Periods each restaurant keeps ready ahead, created by a daily task.The application’s own description, read on November 17, 2026.
Pages, record types and agents in the application.Counted in the application’s repository on November 17, 2026.
Book a walkthrough
Bring one process.
Leave with a working screen.
Bring your aging report, your worst ticket or the spreadsheet everybody is afraid of. The walkthrough shows the desk on a sample of it on the same call.
