Hands at a back-office workstation sorting an invoice stack beside a receipt spike and card terminal, cool 3pm daylight from the left

Payroll and HR

Payday is coming. Will your records hold?

Gusto keeps pay runs, onboarding paperwork and HR compliance tasks close together for small teams. This guide walks the routine before your first payroll on it.

Close crop of an invoice stack and a clipboard resting on a matte counter in cool daylight
The bench, mid-morning Invoices squared and waiting

Chapters in this guide

Payroll and HR

Pay runs, onboarding and records

Accounting

Ledgers that match the pay summary

CRM and sales

Commission notes the payroll carries

Projects

Onboarding tasks with due dates

Workspace

Where the policy lives for staff

Read the rail, then the chapter. Each band below covers one part of the payroll routine a small team actually runs.

Why payroll becomes the first HR system

Many small firms buy payroll first and discover it holds the employee roster, pay history, and key documents. That makes it the de facto HR file when hiring picks up. Gusto sits in that spot because pay, onboarding, and compliance tasks live near each other.

Keep job titles, pay rates, and start dates exact from day one. Later reports and filings draw from those fields. A wrong start date on one hire surfaces months later in an anniversary raise or a leave accrual, and fixing it means rebuilding a history that was never recorded properly.

This guide explains pay runs, onboarding paperwork, time inputs, and record habits for small teams. It is education, not tax or legal advice — confirm filing duties with your provider and advisors.

What a normal pay run involves

A typical cycle, and the two lanes most teams fall between

The left lane is the routine that keeps a run clean. The right lane is where it usually slips. Read the two columns against each other — the digits sit in the same column so the eye can run down them.

The routine that works

Where it slips

Review hours or salaries against the schedule

Hours arrive after the cutoff the team agreed

Check additions and deductions line by line

A bonus approved verbally and entered from memory

Confirm contractor versus employee treatment

A contractor paid through the employee lane

Approve the run, then pay by the scheduled date

Approval left to one person who is out that week

File pay stubs and summaries with the record

Summaries exported to a folder nobody revisits

Set the cutoff, and set the second pair of eyes

Errors usually come from late hours, wrong rates, or missed contractor versus employee distinctions. None of those are tool problems — they are calendar problems. Write the cutoff down, name who reviews the run, and keep a calendar with pay dates and approval deadlines posted where managers see it.

A two-person review does not slow a six-person payroll down. It catches the one entry the person who typed it will always read as correct. Post the calendar before the next hire, not after the next mistake.

An accountant's desk edge with a laptop turned at an angle and tabular printouts stacked neatly beside it
Two colleagues at a shared back-office bench, one pointing at a screen, cool window daylight across the room
The room the work happens in Two chairs, one screen, one question

Onboarding that avoids first-week gaps

A short checklist beats a long email thread

Collect Form I-9 and W-4 inputs, state new-hire data, direct deposit details, and handbook acknowledgments before the first shift where possible. Store offer letters and policy receipts with the employee record.

Assign training tasks with due dates in Asana or Notion so nothing drifts. New hires notice when day one is organized, and the difference is almost never budget — it is whether anyone wrote the order down.

  1. Before day one

    Offer letter signed and filed

    A signed offer in the employee record means the pay rate and start date already have a source.

  2. Before day one

    Tax and identity forms entered

    Form I-9 and W-4 inputs, state new-hire data, and direct deposit details typed in once, not three times.

  3. Week one

    Handbook receipt acknowledged

    Policy receipts stored beside the roster so the acknowledgment date is never reconstructed from memory.

  4. Week one

    Training tasks with due dates

    Assigned in Asana or Notion so a manager sees what is late without asking the new hire.

Time, leave, and small-team rules

Even a team of six needs the rules written down

Decide how time is submitted, who approves it, and when edits lock. Hourly teams of six still need written rules for overtime, sick leave, holidays, and time-off requests — not because anyone is looking for a loophole, but because the same question gets asked four times otherwise.

Keep leave balances visible to staff to cut back-and-forth. Review state and city rules for your location and any state where remote staff live. Two employees in two states is two sets of withholding rules, and the smaller the team the easier that is to forget.

Write the policy once and link it from your workspace so the answer to "how do I request Friday off" is a link, not a conversation.

What to write down first

  • How time is submitted, and the weekly cutoff.
  • Who approves a time-off request, and who covers.
  • When an edited timesheet locks for the run.
  • Which state's leave rules apply to each person.

Compliance records worth keeping tidy

Tidy files shorten every inquiry

Payroll ties to tax deposits, filings, new-hire reports, and wage records that auditors or agencies may ask for. Keep names, addresses, Social Security inputs, pay rates, hours, and filing confirmations organized by year. When a request arrives, the difference between a day and a week is whether the year was filed together.

Limit access to sensitive fields — the fewer people who can see Social Security inputs, the smaller the exposure. Retain records per applicable retention duties and your advisor's guidance. Gusto holds the electronic trail, but the habit of filing by year is what the team actually owns.

Payroll conversation at a bench, one person seated at a laptop and a colleague standing beside with a folder

Tax deposits and filing confirmations, by year

New-hire reports and wage records

Pay rates, hours and pay stubs, per person

Access limited to the people who file them

A wide view of an industrial back office with exposed ductwork, a server rack and one window at 3pm
Back office, 3pm One window, one hum

Beginner mistakes we see

Four habits that cause most of the cleanup

Another is running payroll from memory instead of a checklist. None of these are failures of software — they are failures of order, and they show up in the same week of every month.

Late hour submissions

A manager approves hours the morning the run is due. Fix with a firm cutoff, posted where the time-submitting team can see it, and a message the day before the cutoff.

Unapproved bonuses

A bonus agreed in a hallway and typed in from memory. Fix with a rate confirmation in writing — even one line in the payroll notes is enough to check against.

Wrong state withholding for remote staff

A remote hire keeps the home-state withholding line for two cycles. Fix by confirming the state on the offer, not on the first pay run.

Missing onboarding forms

A hiring week moves fast and the W-4 lands after the first run. Fix with a pre-run review sheet that lists what is still missing, and reconcile payroll totals to accounting monthly so the ledger matches pay summaries.

How experienced managers judge a payroll tool

They test the steps, not the brochure

Trial the exact steps you will run in your first month, with sample staff, before you commit a live pay cycle to the platform.

  • The onboarding flow — adding a hire and how much typing it takes
  • The pay-run review screen — what you see before you approve
  • Correction handling — what happens when a run needs a fix before deadline
  • Reporting exports — a year-to-date pull that a bookkeeper can read
  • Permission controls — who can see pay rates and Social Security inputs
  • Accounting connection — how the platform posts summaries to the ledger
  • Support — who to call when a run needs fixing before the pay date

Connecting payroll to books and CRM

One owner per system, one tie-out per month

Post payroll summaries to accounting on a consistent schedule and keep gross-to-net detail available. Do not retype net checks line by line if a summary entry is the accepted practice with your bookkeeper — it usually is, and the summary is where the review belongs.

Keep sales commissions visible between CRM notes and payroll inputs. Monthly tie-outs catch drift early. Ask your CPA how they want payroll mapped in the chart of accounts before the first month closes, not after.

For a small team the mapping question is small: wages, taxes, and net pay as their own accounts, with commissions flowing to the sales expense line. The goal is that a monthly review takes an hour, not a day.

Monthly tie-out

Match the pay summary against the ledger entry, commissions against CRM notes, and any correction against the support record. Three minutes of checking beats a quarter-end reconstruction.

Getting started in one week

Five days from decision to first run

A week is enough for a small team if someone owns each day. Keep support contacts and filing calendars in Notion for the team.

  1. Day one

    Gather what the platform needs

    EIN details, state accounts, employee records, pay rates, and pay schedule decisions into one folder before anything is entered.

  2. Day two

    Enter staff and verify deposit data

    Identities, direct deposit details, tax IDs — typed once and checked by a second person before the first live run.

  3. Day three

    Set time and leave rules

    Load balances, decide approval order, and write the cutoff where the team can find it.

  4. Day four

    Run a test review with real hours

    Not a demo entry — last week's actual hours, so the review screen shows what a real cycle will show.

  5. Day five

    Approve the schedule and file the checklist

    Confirm cutoffs and the first pay date in writing with the provider, then keep the checklist where the next hire will need it.

Team-size fit

Choose process weight that matches headcount

Revisit after each hiring wave, not once at the start.

Solo with contractors

Clean contractor records and year-end forms

One owner, separate contractor agreements, and a year-end form habit set up long before January. Payroll is small but the records still have to survive a review.

Five to twenty people

Onboarding checklists managers will follow

Time approvals and leave tracking that survive a busy week. The process is built for the person who is not you — a manager who has never run payroll before.

Multi-state teams

Extra care with withholding and leave rules

Each state adds a withholding line and a leave rule. Confirm the state on the offer, and check the registration is live before the first pay date.

The eight tools this guide covers

A roster, not a pitch

Accounting

QuickBooks Online

The ledger everything else posts to, and the account a bookkeeper is most likely to already know.

Accounting

Xero

Bank feeds and a clean chart of accounts, chosen by owners who like a lighter interface.

Accounting

Sage 50 Accounting

A desktop-era workhorse many established shops still run their books on.

Payroll and HR

Gusto

Pay runs, onboarding and compliance tasks in one place — the subject of this chapter.

CRM and sales

Salesforce Sales Cloud

Where the commission notes live that payroll has to carry into a pay run.

Projects

Asana

Onboarding tasks with due dates, so a new hire's week one has an owner.

Workspace

Notion

Where the leave policy, support contacts and filing calendar live for the team.

Communication

Google Workspace

The email and documents a hiring week actually travels on.

Before you switch providers

What to prepare, and what to confirm

Two answers we get asked most often when a small team is moving payroll for the first time.

What should we prepare before switching payroll providers?

Employee rosters, pay rates, hire dates, tax IDs, state account details, direct deposit data, time-off balances, and year-to-date totals. Confirm cutoffs and first pay dates in writing. Run one parallel review before you move pay entirely.

How do payroll, accounting, and CRM stay in sync?

Keep pay detail in payroll, money movement in accounting, and commission notes in CRM, then connect with vendor-supported integrations and a monthly tie-out. One owner per system helps. Review the sync weekly during the first two months.

On the bench

The chapter you just read sits next to the accounting chapter, and the two are meant to be read together. Payroll tells the story of a month; the ledger is where that story has to reconcile.

Where the guide comes from

Deskberry Digital writes this guide from the bench. Education only — when a filing duty is yours, confirm it with your provider and advisors.

Reach the bench

[email protected]

We keep a few cookies on the bench so your settings stay where you left them. You decide what stays. What we store