Payroll

Decide whether payroll is a service line

Payroll is not bookkeeping with a pay run attached. It has its own deadlines, its own regulator, its own liability when it is wrong, and a client who notices within the hour when it is late. Firms that drift into payroll one client at a time end up with a dozen clients on three tools and one person who knows all of them. Firms that decide it is a service line choose one tool, one rhythm and one price structure, and staff it.

The alternative is a decided referral: a payroll provider or bureau the firm trusts, with the firm keeping the ledger and the advisory relationship. That is a legitimate stack decision and it belongs in writing.

What to look for

Compliance in your jurisdiction first: real-time reporting to the tax authority, the pension or superannuation scheme handled inside the tool, leave and award or contract rules where they apply, and year-end filings produced without a spreadsheet. A tool built for one country's rules is a liability in another.

Then the bureau view: every client's pay run in one place, with status, approvals and exceptions, and a way for the client to approve hours and see payslips without emailing the firm. Employee self-service for payslips and leave requests removes the most common client email. Integration with the ledger should post the journal coded and split, and with the practice system so the pay run is a job with a deadline.

Finally, timesheets and rostering: many small clients need them, and a payroll tool that imports approved hours cleanly is worth more than one with a prettier payslip.

Running the rhythm

Payroll as a service works on a calendar. Hours in by a cut-off, run prepared, client approves, payment files out, filings lodged, all on the same weekday every cycle. The tool should enforce the cut-off with a reminder and show at a glance which clients have not approved. Firms that run it well batch the runs by pay frequency and keep one person accountable per batch.

The failure mode is the firm becoming the client's HR department: fielding employee questions, adjudicating leave disputes, chasing hours. Employee self-service and a clear engagement letter are the two defences.

Pricing and how firms recover it

Vendors price per employee per month, per pay run, or with a base amount plus a per-employee rate; bureau plans add a per-client element. The model shapes the service: per-employee pricing maps onto a per-employee fee to the client, per-run pricing onto a per-run fee. The directory records what vendors publish; it does not say what a firm should charge for payroll, and nothing here is fee advice. Firms describe pricing payroll per employee per cycle with a minimum, and keeping the tool cost inside it.

Year end and the changeover

Year end is when payroll tools are judged: the reconciliation between what was reported through the year and what the year-end filing says, the corrections, the finalisation. A tool that reconciles as it goes makes year end an afternoon; one that does not makes it a week. Ask to see the year-end process, not the pay run.

Changing payroll tools mid-year is the hardest migration in a small firm's stack, because the year-to-date figures have to move with the employees. Firms change at the start of a tax year or not at all.

What to avoid

Running payroll on a tool chosen for its ledger rather than its payroll. Taking payroll clients one at a time without a decision on the service line. Any tool without real-time reporting and the pension or superannuation scheme built in for your country. Mid-year migrations. And pricing payroll as an add-on to bookkeeping: it is its own engagement with its own liability.