Friday, and the week is over
The hours are
already in
the building.
Every punch, every break and every tip landed as it happened, at the stand, on the phone your team already carries. Payroll prep is not data entry. It is the last step of something that already finished.
Step one
The punches are already hours.
Time on the clock, less the breaks nobody was paid for. A break a manager marked paid stays in, because the person was on the clock for it.
Two sites in one week
Each hour is priced where it was worked.
Not at the rate on the employee record. A raise that took effect on Wednesday is paid from Wednesday, on the hours after it and not the ones before.
The part that gets paid wrong
Overtime is owed at neither rate.
It is owed at the regular rate: everything earned that week, over every hour worked in it. Reach for the higher site and you overpay. Reach for the record and you underpay.
What you file
One row, and nobody assembled it.
The same figures the export writes, so what you read on the screen is what leaves in the file.
29 CFR 778.108–115. One of those is an overpayment and one is an underpayment, and both of them are somebody's money.
Illustrative hours and rates · every rate here is operator-set
Tips
A tip's split is decided
when the tip is collected.
Present means clocked in at that stand and not on an unpaid break. Who shared it, and how many ways, is written onto the payment itself - so a clock-out corrected three weeks later never moves money between people who have already been paid.
Illustrative amounts
Before anything leaves
Seven checks, and the week has to pass them.
The same test runs on the screen and again on the server when you approve, because a verdict a browser reached on its own is only advice.
Four of them are hard
An unfinished week is not a cheap mistake.
Somebody mid-shift has hours that are not final yet. A timecard nobody approved is a number nobody has stood behind.
Clear them
The week closes, and it locks.
Approving freezes the period and writes the run out line by line, so what you filed on Friday still reads the same in November.
Or go anyway
Override it, in writing.
Nothing here refuses to let you run payroll. It refuses to let you do it silently.
Two problems, counted apart, because the fix is different: somebody has to clock out, and somebody else has to approve.
Stamped on the pay period with who approved it and which checks they went past.
Illustrative period · the checks are the product's own
The handoff
One file, in the shape
your provider already reads.
Two shapes: ADP RUN's own Pay Data Entry layout, or a vendor-neutral CSV that anything else will import.
Our overtime premium and tip totals are optional columns, off by default: your provider's engine is usually the authority on both.
Employee IDs held for ADP · Gusto · Paychex · QuickBooks · Rippling
The argument
This is not a payroll feature.
It is a vendor you stop paying.
Scheduling, a time clock and payroll prep were three subscriptions with two exports between them. Your payroll provider stays exactly where it is. What goes is the box in the middle whose only job was holding hours.
Seen enough of this one?
Pick the part you
actually care about.
The same operation, seen from five sides.
Thirty minutes
Bring a real week.
We will run it through.
Your locations, your rates, your people. We will take one week you have already paid and show you the file it would have produced.