Payroll

Valet payroll software that pays runners from the work they already logged

Every check-in, retrieval, and shift your team logs in ValeKit is already the raw material for payroll. The module being built on top of it will calculate hours, overtime, shift differentials, and tip-pool splits from real app activity, not a second punch clock and not a Sunday-night spreadsheet. The goal is a pay run you review, approve, and export in minutes.

Runner payroll is rolling out to ValeKit accounts. Talk to us about early access.

What is valet payroll software?

Valet payroll software turns the hours a valet team logs on shift into pay: it counts regular and overtime hours, applies the pay rate for the location each shift was worked at, splits pooled tips, and produces a per-period summary a finance team can review, approve, and export.

Hours that come from the work, not a time clock

Runners will clock in and out in the same app they use to check cars in, and the module is designed to reconcile those punches against real activity, first check-in to last retrieval, so a forgotten clock-out does not become a payroll argument. Punches carry location and time, and because the app is offline-first today, hours logged in a dead-zone garage will sync when signal returns.

Overtime, differentials, and per-site rates, automatically

You will set daily, weekly, and seventh-day overtime with state presets, night, weekend, and holiday differentials, and different rates per location for runners who move between client sites in a week. The module is designed to apply the right rule to each hour and show labour cost next to the revenue those hours produced.

Tip pools runners can actually trust

Digital tips are captured at payment in ValeKit today, with no cash-drawer guesswork. Payroll is where they will flow into a pool you split by hours, by shift, or evenly, with every runner able to see exactly how their share was calculated.

Payments: where tips are captured today

Pay-period reports your finance team can close on

Per-runner and per-location summaries for any period, with an edit history on every adjustment and an approval step before export. The design goal is a clean file for your payroll system plus the audit trail that answers the question every finance team eventually asks: why did this number change?

Built for distributed valet teams

Runners reassigned across five client sites in a week should not take five spreadsheets to pay. Hours, rates, and tips from every location will roll into one pay run. Role-based access is already location-scoped in ValeKit today, so each location manager stays scoped to their own team when payroll arrives.

Everything included

What the payroll module is being built to cover. Digital tip capture is live in ValeKit today; the rest arrives with the module as it rolls out.

Time & Hours

Activity-reconciled hours
Clock in and out
Location and time stamp
Offline capture with sync
Breaks

Pay Rules

Daily, weekly, 7th-day OT
Night, weekend, holiday differentials
Per-location rates
State presets
Labour cost against revenue

Tips

Digital capture (live today)
Pool by hours, shift, or even
Per-runner transparency
Distribution reporting

Reporting & Export

Pay-period summaries
Per-runner and per-location
Edit history and audit trail
Approval workflow
CSV payroll export

FAQ

Where do the hours come from?
From the app itself. Runners will clock in and out in ValeKit, and those punches are designed to reconcile against real activity, the check-ins and retrievals already recorded against each ticket. Offline punches will sync when signal returns, so no hours are lost. This is part of the payroll module now rolling out.
How are overtime and differentials calculated?
You will configure the rules once, daily, weekly, and seventh-day overtime with state presets, plus night, weekend, and holiday differentials, and the module will apply the right rate to each hour and flag shifts approaching overtime. Rules configuration ships with the payroll module as it rolls out.
How do tip pools work, and can runners see their share?
Digital tips are captured at payment today and attributed to the ticket and the valet who handled it. Payroll is the layer that will pool them and split by hours, shift, or evenly, with each runner able to see the calculation behind their allocation.
Can it export to our payroll system?
Approved periods are designed to export as a CSV compatible with common payroll systems, with per-location breakdowns. Export arrives with the module.
How does payroll work for runners across multiple sites?
Hours, per-site rates, and tips from every location will roll into a single pay run per runner. Roles in ValeKit are already scoped per location today, so a manager sees only their own site's team when the module lands.
Is runner payroll available now?
Not yet. It is rolling out. Digital tipping is already part of ValeKit, and the ticket activity the hours will be built from is already recorded on every check-in and retrieval. Talk to us about early access to the full payroll module.

Payroll that closes itself.