Gusto is the payroll platform we run for most of our MSP clients, and for good reason. It handles multi-state employees cleanly, it plays well with contractor payments, and its reporting is straightforward enough that you are not stuck exporting spreadsheets to make sense of your own payroll. But the setup has a few decisions in it that are easy to get wrong if you rush through them, and fixing a payroll mistake after the fact is a lot more painful than getting it right on day one.
Here is the setup in the order we actually walk clients through it.
1. Company Setup and Work Locations
Start with your legal business details - EIN, entity type, and business address - exactly as they appear on your IRS documents. Then set up work locations for every state you have employees physically working in, not just where your business is registered. This matters more for MSPs than most industries, because field technicians and remote support staff are often scattered across several states.
Each work location triggers its own state tax registration requirements inside Gusto. Skip a location and you risk misfiling state withholding and unemployment tax for that employee - the exact kind of issue that shows up as a penalty notice six months later.
Remote-first MSPs, take note: if you hired someone who works from home in a state where you have no other presence, that home address is a work location. Gusto will walk you through the state registration, but you have to add the location first for it to prompt you.
2. Pay Schedules
Most MSPs run either biweekly or semimonthly payroll. Biweekly is simpler to administer and matches how a lot of technicians think about their hours, but it means occasional three-paycheck months that can catch a cash flow forecast off guard if you are not planning for it. Semimonthly keeps things aligned to the calendar month, which is easier to reconcile against MRR billing cycles.
You can run multiple pay schedules in Gusto if you have, for example, salaried admin staff on semimonthly and hourly field techs on biweekly. Just be intentional about it - mixing schedules without a reason adds unnecessary reconciliation work for whoever is doing your bookkeeping.
3. Employees vs. Contractors
This is the step that causes the most long-term trouble if it is rushed. Gusto supports both W-2 employees and 1099 contractors, and it is tempting to default a field technician to contractor status because it is simpler and cheaper up front. The IRS has a specific test for this, and MSPs get flagged on it more than almost any other service industry because of how field technicians are scheduled, supervised, and equipped.
- Do you control when and how the work is done, not just the end result?
- Do you provide tools, a company vehicle, or a uniform?
- Is the person working exclusively or primarily for you?
- Is the role core to your ongoing service delivery, not a one-off project?
Answering yes to most of these means the role is very likely an employee under IRS rules, regardless of what the paperwork says. Set it up correctly in Gusto from day one.
4. Benefits and Deductions
If you offer health insurance, retirement matching, or other benefits, set these up before running your first payroll rather than adding them retroactively. Gusto integrates directly with several benefits providers, which keeps deduction amounts synced automatically instead of relying on someone manually updating a number every pay period.
Common Deductions to Configure Up Front
- Health insurance premiums (pre-tax where applicable)
- 401(k) or SIMPLE IRA contributions and any employer match
- HSA or FSA contributions
- Garnishments, if applicable, entered exactly per the court order
5. Running Your First Payroll
Before you submit the first real payroll run, run it as a preview and check every line against what you expect - gross pay, tax withholding, deductions, and net pay per employee. This is the single easiest place to catch a setup error before it becomes a corrected paycheck and an awkward conversation with your team.
Gusto's approval deadlines matter here too. Direct deposit typically requires payroll to be submitted a few business days before payday, longer for a company's very first run while banking verification completes. Build that lead time into your calendar so payday is never a scramble.
6. Reporting That Actually Feeds Your Books
The last step, and the one most guides skip, is making sure Gusto's output actually flows into your accounting system correctly. Payroll journal entries need to hit the right accounts - gross wages, employer tax expense, and any benefit liabilities - separated in a way that matches your chart of accounts, especially if you are tracking labor cost by service line the way most well-run MSPs do.
If your bookkeeper is manually re-keying payroll totals every pay period instead of syncing Gusto directly to QuickBooks Online, that is both a time sink and a place errors creep in. A proper integration keeps your labor costs accurate in real time, which matters if you are tracking utilization and cost-per-ticket the way we recommend.
Want This Set Up for You?
We are a Gusto Payroll Partner and we handle full-service payroll setup and processing for MSPs - work locations, employee versus contractor classification, and reporting that flows straight into your books correctly.
See Payroll Services