Gusto vs Rippling When Technicians Work Across States

Start with a simple list: for every field technician and consultant, which states did they physically perform work in over the last quarter, not just which state they live in. Remote-first companies often track home state carefully and stop there, missing that a technician who spent two weeks on-site at a client in a neighboring state may have created a withholding obligation in that state too. This list is the foundation for everything else, and it needs to be built from actual site visits or travel logs, not assumptions.

Once you know which states matter, you need an ongoing way to capture it, not a one-time audit. Some firms tag timesheet entries with a work-state field; others rely on expense reports tied to travel. Rippling's timesheet and expense modules can tag entries by state directly, feeding that into payroll's withholding logic. Gusto can also run multi-state payroll, but the state-tagging on individual timesheet entries is a step your ops team is more likely to handle outside the platform, in whatever scheduling or dispatch tool you already use for field technicians.

A handful of neighboring states have reciprocity agreements that simplify withholding for employees who live in one and work in the other, and some states carve out exceptions for a small number of working days before nonresident withholding applies at all. The exact thresholds and which states participate vary and change, so confirm the current rules for your specific states with your CPA rather than relying on a platform's default settings alone. What you want from either platform is a clear state-by-state withholding table you can check against that advice, not a black box.

Per diem paid under an accountable plan, meaning the employee substantiates the business expense and returns any excess, generally is not taxable wages and should not be lumped into a technician's regular pay run. Running it through payroll as a flat add-on instead of tracking it as a true reimbursement risks treating nontaxable expense money as taxable income, which creates both overwithholding for the employee and a paperwork headache if it is ever questioned. Keep travel reimbursement in your expense system, not your payroll system, and make sure the two only meet on the pay stub as a clearly labeled non-wage line.

Before retiring your current platform, run a full cycle on the new one in parallel and compare technician by technician. Check that every state where someone worked on-site during that period has the right withholding applied, that per diem paid under an accountable plan is not showing up as taxable wages, and that any 1099 field subcontractors are correctly excluded from the W-2 payroll run entirely. A parallel run catches setup mistakes while you still have the old system as a safety net.

Compare these items technician by technician in the parallel cycle:

• Every state where someone worked on-site during the period has the right withholding applied.
• Per diem paid under an accountable plan is not showing up as taxable wages.
• Any 1099 field subcontractors are correctly excluded from the W-2 payroll run.
• Reciprocity and short-stay treatment matches what the relevant state agencies or your CPA confirmed.

Getting multi-state withholding right once, during a migration, is a different problem from keeping it right as your dispatch schedule changes every week. Assign someone the recurring job of reviewing which states technicians worked in over the prior pay period and flagging any new state before it becomes a compliance gap, rather than treating the mapping exercise in step one as a task you finish once and file away. Firms that skip this step tend to be fine for a quarter or two, then discover a technician has been working regularly in an unregistered state for months once a state notice arrives asking why no withholding was ever filed.

It also helps to loop your dispatch or scheduling software into the same process, since that system usually already knows where a technician was assigned each day, well before payroll runs. If dispatch and payroll never talk to each other, the state-mapping list in step one goes stale the moment your first new client contract lands in a state you have not worked in before.