Running payroll from timecards at a med-spa chain with about 50 studios: a hire at $25 to $30 an hour to catch the mistakes first

For the executive who decides

• The customer acts
• The machine acts
• A person decides
• Nothing runs

An illustration built from the employers' postings: the times are examples, and the minutes are estimates.

1The job

Running payroll from timecards: before each payroll run, collecting every timecard, checking it against the schedule and the pay rules, getting the mistakes fixed with the employee and the manager, then running payroll from the fixed hours. The worked example is a med-spa chain with about 50 studios in 11 states and 201 to 500 employees, paid twice a month or every two weeks. Its staff earn commissions and bonuses on top of hourly pay. Four employers posted this job in the last two months: the med-spa chain; a property manager running weekly payroll for several properties, hiring through an HR firm; a real-estate group with several divisions; and a building contractor in Canada with field crews.

2The number today

The med-spa chain is hiring a person, at $25 to $30 an hour, to Collect, review, and audit timekeeping data, PTO, and schedule adjustments prior to each payroll run, resolving discrepancies with managers and studio teams before processing. The property manager pays $30 to $40 an hour for the same work: "Review and verify employee timecards to ensure hours worked, overtime, PTO, and other payroll-related information are accurate and complete."

That is $52,000 to $62,400 a year for the chain's whole role. US median pay for payroll and timekeeping clerks is $28.01 an hour, inside that range. The timecard part alone is about 200 hours a year, about a tenth of the role: about $5,600 a year, or about $1.16 a timecard.

The bigger cost is the mistakes that get through. A 2022 survey of US payroll teams found one payroll in five has errors, at about $291 each, and timecard errors the most common. Scaled to this chain, that is about 229 errors a year and about $50,000 a year to put right. In California, where the chain is based, a missed break is owed as an extra hour of pay at the regular rate (hourly pay with commissions and bonuses folded in), and penalties start at $100 per pay period for each employee affected.

Estimate. The 200 hours assumes 201 employees, 24 runs a year, 1 minute to read a timecard, 1 in 10 with a problem, and 15 minutes to fix each. The $50,000 scales the 2022 survey to 201 employees. The chain's own count of problem timecards, timed for one pay period, replaces both.

3The verdict

Hand over the chasing. Keep the pay.

• Hand to the machine: reading every punch against the schedule and the bookings each evening; texting the employee the same day about an open shift, a missing break or an odd punch; drafting the fix with the employee's reply attached; and handing the manager and the payroll person one list before cutoff.
• Keep with a person: approving any change to hours (the studio manager); every break premium, overtime change and commission in the regular rate (the payroll person); any reply that does not match the schedule; and running payroll.
• Not yet: approving clean timecards on its own, until two pay periods of its flags have been checked against what the payroll person finds; texting anyone about pay amounts; and off-cycle corrections.

What the payroll person is for now: deciding what each person is owed. The machine does the reading and the chasing. The pay stays with a person.

4The bill

Under $10 a month in usage, plus 20 euros a month for the software that runs the steps, on top of the payroll software the chain already runs. That software's own time module flags open shifts and missed breaks and sends approved hours to payroll; the build adds the texting and the drafted fixes. Then the build, the upkeep, and the texting number's own fees.

If the chain does not yet pay for the time module, its price is on request; the payroll software starts at $8 an employee a month, so at least about $1,600 a month for 201 people. A standalone time clock priced per person is about $1,000 to $1,300 a month; one priced per studio is $1,500 to $6,000 a month for 50 studios. A person doing it is what the four employers chose: $25 to $30 an hour, about $4,300 to $5,200 a month for the whole role.

Checking: for the first two pay periods, the payroll person reads every drafted fix before approving it, and checks two studios' timecards by hand against the machine's list. The check time is not known until it is counted.

Estimate. The usage assumes 20 to 60 problem timecards a run and two runs a month. The $1,600 uses the software's starting price as a floor for the module.

5Owner and off switch

The person who signs off each payroll run owns it (at the chain, the Payroll Specialist the coordinator reports to), because the pay is theirs to answer for. The off switch: turn off the evening workflow. Texts stop, and the payroll person reads the timecards and chases managers as they do today; the payroll software's own flags stay on. It takes under a minute. Try it once in the first pay period.

6The brief to hand your builder

The job: each evening of the pay period, check every timecard against the schedule and the state's pay rules, text the employee about any open shift, missing break or odd punch, draft the fix with their reply, and hold it for the manager and the payroll person.

Today: one payroll person reads about 201 timecards from 50 studios before every run and chases studio managers for fixes, about 200 hours a year (estimate). Mistakes that get through come back as corrections and off-cycle runs.

Done when: for two weeks, covering one full pay period, every open shift and missing break is texted to the employee the evening it happens; no hours or pay change without a person's approval; every drafted premium uses the regular rate with commissions; the payroll person's time on timecards is under half of what it was in the baseline pay period; and no timecard causes a correction after the run.

It may never, on its own: change a punch, approve a timecard, add or waive a premium, round a punch, assume a break was taken, block anyone from clocking in, or text anyone about pay amounts.

You get from us: two past pay periods of timecards with the fixes we made; the schedule and booking export for the same weeks; the pay rules for each state we run in (breaks, overtime, premiums); the list of studio managers; and the employees' consent to work texts.

We own: the payroll software, the time records, the texting number, the employees' phone numbers and the billing.

We get back: before each cutoff, a list for each studio of every flag, the employee's reply, the drafted fix and who approved it.

Ask whoever sets it up	A good answer	A bad answer
Does it ever round a punch or take off a meal break on its own?	Never. It records the real punches and flags a missing break for a person	"It deducts the 30 minutes automatically to save you time"
What happens when the employee does not reply, or the reply does not match the schedule?	It goes to the manager with both facts. Nothing changes until a person approves	"It goes with the schedule"
How does it work out a missed-break premium?	At the regular rate, commissions and bonuses included, drafted for the payroll person to approve	"At their hourly rate"

For the operator who builds and runs it Paid layer

7The working set

• Trigger: every evening at 9:00 pm during the pay period, and once more two days before cutoff.
• Steps: pull the day's punches from the payroll software's time module; pull the schedule and the booked appointments; check each timecard with plain rules (open shift; shift over 5 hours with no 30-minute meal break, for California; daily or weekly overtime; a punch more than 15 minutes from the schedule or the last booking); text the employee one short question; read the reply with the model and draft the corrected punch, with the reply attached; draft any break premium at the regular rate for the period, commissions and bonuses included; hold every draft; write approved edits back with a note; log each step.
• Data: one record per timecard: employee, studio, state, pay period, punches, scheduled shift, last booking, flags, text sent, reply, drafted edit, drafted premium, approver, approved at, and status (clean, flagged, approved, edited, rejected).
• Review step: studio managers clear their flags by the day before cutoff. The payroll person approves every premium and overtime change, and checks two studios a run by hand against the machine's list.
• Alerts: a text with no reply after a day (goes to the manager); a timecard not approved the day before cutoff; a drafted premium; an edit written without an approval (must be zero); and the wrong-but-green count, timecards that caused a correction or an off-cycle run after payroll ran.
• If it breaks: what you see: no texts going out, a studio with no flags at all, or edits missing at cutoff. Check first: the connection to the time module is still authorized; the studio's schedule export is still syncing; the employee is on the text consent list. Safe fix: turn off the workflow; the payroll person reads the timecards by hand, with the time module's own flags.
• Cost per timecard: about $0.01 to $0.02 in usage if built (texting about $0.05 and the model about $0.01 for each problem timecard, 20 to 60 a run), plus the workflow plan, over about 402 timecards a month. If the time module must be bought: at least about $4 a timecard (201 x $8 over 402 timecards).
• Baseline, before switch-on: one pay period of: timecards with a problem, minutes the payroll person spends on each (time it, do not ask), how long managers take to answer, break premiums paid, and corrections or off-cycle runs caused by timecards after payroll ran.

Estimate. The costs assume 201 employees, two runs a month and 20 to 60 problem timecards a run. The baseline pay period replaces all three.

Tools by name: Rippling Time & Attendance (price on request; Rippling starts at $8 an employee a month plus a base fee), already the chain's preferred payroll software; Deputy Core ($6.50 a user a month, with timesheet auto-approval) or Homebase ($30 to $120 a location a month) as standalone time clocks; built: n8n (Starter, 20 euros a month annual), Claude Sonnet 5.5 ($2 per million tokens in, $10 out), Twilio SMS ($0.0083 a segment plus carrier fees), the time module's API.