Multi-state overtime

Multi-state overtime, split automatically — no rules, no spreadsheets

Multi-state overtime timesheet software for staffing firms and IT consultancies. Tag each day with where the work happened; MTT applies that state's daily and weekly overtime rules and splits Regular, Overtime, and Double-time per state — automatically, every week.

Start 30-day free trial → See a worked example

$5 per active consultant per month. No rule-building. No post-export math.

The problem

Three states a week. Three sets of rules. One paycheck.

An IT consultant on a travelling engagement works Tuesday in California and Thursday in New Jersey. California pays daily overtime after eight hours in a single day. New Jersey doesn't. By Monday, someone in your back office is supposed to know exactly who's owed what — and split it correctly, by hand, before billing closes.

Most don't. The hours land in a spreadsheet as one weekly total, the state-by-state nuance gets flattened, and the consultant is either underpaid or the firm quietly eats the difference. Either way, multi-state overtime turns into a recurring stream of payroll corrections — the kind nobody catches until a consultant does.

The rules aren't optional and they aren't going away. As your people move between client sites, every state they touch brings its own overtime math, and your team is the one expected to reconcile it every single week.

How it works

We tag each day with where the work happened, then apply that state's rules.

Every day on an MTT timesheet carries a state tag — a small pill the consultant sets when a day's work location differs. That tag is the only thing anyone configures.

Behind it sits a resolved-state engine. For each day, MTT applies that state's daily overtime rules; across the week, it applies the federal weekly 40-hour rule. Regular, Overtime, and Double-time are calculated and persisted per state — every week, with no pay-rule builder to set up and no spreadsheet column to maintain.

There is no configuration screen and no rule wizard. The state pills on the timesheet are the entire user-facing surface of multi-state overtime in MTT. Tag the day; the engine does the rest.

Worked example

Multi-state overtime, worked end to end.

One consultant, one week, split across two states — resolved the way MTT resolves it.

→ One consultant, one week

Day	State	Hours	Rule applied
Tue	CA	8h
Wed	CA	10h	→ 2h California daily overtime
Thu	NJ	12h
Fri	NJ	12h

→ Multi-state overtime, calculated automatically

Total: 42h worked (40h Regular + 2h Overtime)

CA Reg 16 / OT 2 / DT 0

NJ Reg 24 / OT 0 / DT 0

OT is attributed to the state where it was earned.

State rules

Every state we encode, every rule we apply.

The states where multi-state overtime actually bites are the daily-overtime states. Those are encoded; everywhere else falls back to the federal weekly rule.

State	Rules applied
CA California	Daily 8 (1.5×), daily 12 (2× double-time), weekly 40
AK Alaska	Daily 8
NV Nevada	Daily 8
CO Colorado	Daily 12
US All other states	Federal weekly 40

These rules track state law as it changes — when a state updates its overtime thresholds, the engine updates with it. You build nothing, maintain nothing, and never own a rule that's quietly gone stale.

Payroll

Straight into payroll, OT already split per state.

The same per-state split shows up as a subtotal block on the in-app timesheet and on the signed PDF — your approver sees Regular, Overtime, and Double-time broken out by state before anything is exported.

The payroll export is an XLSX with one row per consultant per state, each carrying its own Reg / OT / DT figures. Drop it into Paychex, ADP, or whatever provider you run — there's no manual re-split, no reconciliation pass, no post-export math. The multi-state overtime calculation is already done by the time the file leaves MTT.

Paychex ADP Gusto QuickBooks XLSX export

FAQ

Multi-state overtime, common questions.

Does MTT handle California's daily overtime and double-time?

Yes. For any day tagged California, MTT applies time-and-a-half after 8 hours and double-time after 12 hours in a single day, on top of the weekly 40-hour rule. You don't configure any of it — tag the day CA and the engine applies the right rule.

What about a consultant who moves between states mid-week?

That's the normal case, not an edge case. Each day carries its own state tag, so a week split across California, New Jersey, and Texas is resolved day by day. Overtime is calculated per state and attributed to the state where the hours were actually worked.

How is weekly overtime attributed across states?

Each state's daily rules are applied first, then the weekly 40-hour rule. Hours past 40 are attributed to the state where those later hours were worked, while daily overtime — like California's daily-8 — stays tied to the day and state that earned it.

Can I add a custom state rule?

There's no self-serve rule builder, and that's deliberate. MTT ships the daily and weekly overtime rules for every state and keeps them current as state law changes. If your situation needs a rule we don't yet encode, tell us and we'll add it — you never maintain a pay-rule engine yourself.

Which payroll systems does the export work with?

The payroll export is an XLSX with one row per consultant per state, broken into Regular, Overtime, and Double-time. It drops straight into Paychex, ADP, Gusto, QuickBooks, or any provider that ingests a standard spreadsheet — with no post-export math.