How to Run Payroll for a Small Business

Payroll feels like it should be simple — pay people what they're owed, on time. It's the accumulation of small details that makes it error-prone: a missed deduction, a misclassified contractor, a pay date that slips a day and triggers a bank complaint. None of these are hard problems individually. They're just easy to get wrong when they all live in someone's head instead of a process.

Here's the actual sequence, in order.

1. Classify everyone correctly first

Before any numbers, decide who's an employee and who's a contractor. This isn't a formality — it determines what you're legally required to withhold, whether benefits apply, and how disputes get resolved later. Misclassification is one of the most common (and expensive) small-business payroll mistakes, and it's cheapest to fix before the first payment, not after twelve months of them.

2. Set gross pay and pay structure

For salaried staff, this is straightforward — an annual figure divided by your pay frequency. For hourly or commission-based roles, you need a reliable way to capture hours or sales before payroll runs, not reconstructed afterward from memory. Whatever tracks attendance and whatever calculates payroll should be looking at the same numbers — a second spreadsheet that gets updated "later" is where discrepancies start.

3. Calculate deductions

Tax withholding, loan or advance repayments, any benefit contributions — each needs to come out correctly, every single run, without being re-derived by hand each month. This is the single biggest source of payroll errors in small teams: someone remembers to deduct a loan repayment in month one, forgets in month three, and now there's a reconciliation problem nobody notices until the loan should have been paid off and hasn't been.

4. Pick a pay schedule and hold it

Weekly, biweekly, monthly — the specific choice matters less than consistency. A payday that moves around erodes trust fast, especially for employees living paycheck to paycheck. If a public holiday or weekend falls on payday, decide your rule (pay before vs. after) once, and apply it every time rather than deciding fresh each occurrence.

5. Run it, review it, then pay

Generate the run, but don't treat generation as the finish line. Scan for the obvious red flags before money moves: a salary that's 10x what it should be from a typo, a deduction that's missing entirely, a new hire who isn't in the run at all. A five-minute review catches the expensive mistakes before they're expensive.

6. Keep records — actual records, not memory

Every run should leave a permanent trail: what was paid, what was withheld, and why. This matters for tax purposes, for resolving a "you underpaid me" conversation six months later with facts instead of recollection, and for the day an employee leaves and you need their exact payment history without reconstructing it from bank statements.

Where this actually breaks in practice

Almost never at the math. It breaks at the handoffs — attendance data that doesn't reach payroll automatically, a loan repayment tracked in a different file than the one payroll reads from, a leaver who keeps showing up in the run three months after they left because nobody had a real way to mark them inactive. Those are process gaps, not arithmetic mistakes, and they're exactly what payroll software is meant to close: attendance, loans and leaver status feeding directly into the run instead of being separately maintained and hoped to stay in sync.

If you're currently doing this in a spreadsheet and it still works, that's a legitimate place to be — plenty of small teams run payroll manually for years without incident. The moment it stops working is usually specific: the person who understood the spreadsheet is out sick on payday, or a new hire needs an answer nobody has time to give. That's the point worth automating, not before.