Start by defining the engagement

“Handling payroll” can mean very different things. One bookkeeper may prepare calculations and records while the client pays employees and files taxes through another provider. Another may act through an authorized reporting arrangement. Put the scope in writing before the first pay period.

The IRS distinguishes several third-party payroll arrangements and emphasizes that employers generally remain responsible for federal employment-tax obligations when payroll duties are outsourced. Do not let an informal workflow blur that responsibility.

Build one intake checklist for every client

  • Legal employer name and EIN.
  • Primary contact and payroll approver.
  • Work locations and states.
  • Employee roster and classification.
  • Pay frequency, workweek, pay dates, and period dates.
  • Current rates, salary basis, withholding setup, and deductions.
  • Who moves money, who makes tax deposits, and who files returns.
  • Where final records and approval evidence will be stored.

Create a cutoff for payroll changes

Small-client payroll becomes chaotic when every change arrives through a different text message. Set a clear cutoff for time, bonuses, deductions, new hires, terminations, and rate changes. Late

changes should be explicitly accepted into the run or deferred—not silently mixed into the workflow.

Prepare and review the run

Work from the same pay-period definition across all employees. Review gross pay, taxes, deductions, net pay, and YTD continuity before the client relies on the results. Where the engagement allows, use a second-person or client approval step for exceptions and unusual changes.

Produce a handoff that can stand on its own

A useful handoff should tell the next reviewer what happened without forcing them to rebuild the payroll calculation. At minimum, include the employer and pay-period context, employee-level totals, run totals, and enough detail to reconcile the accounting records.

LeoFolio’s Bookkeeper Handoff is designed around that need. A completed Pay Run can produce a PDF handoff and structured CSV alongside the payroll register, funds summary, and employee statements.

Reconcile after the client completes the downstream steps

After wages and taxes are actually paid, reconcile the completed payroll record to the client’s bank activity, payroll liabilities, and general ledger. A prepared payroll record is not proof that the employer completed payment or filing obligations.

Preserve the client boundary

Use consistent client folders, avoid mixing employees from different employers in the same working file, and keep sensitive payroll data under access controls appropriate to the engagement. Browser-local or local-file workflows can reduce unnecessary centralized access, but they also make backup discipline important.

Quick FAQ

Can a bookkeeper prepare payroll without being the tax filer?

Yes, depending on the engagement. Payroll preparation, review, money movement, tax deposits, and return filing can be separate responsibilities. The scope should make those boundaries explicit.

Who is ultimately responsible for payroll taxes?

Under common payroll service arrangements, the employer generally remains responsible for federal employment-tax obligations. Different legal arrangements can shift or share responsibility, so identify the actual arrangement rather than assuming.

What makes a payroll workflow “bookkeeper ready”?

Consistent inputs, a documented review step, a complete employer-level register, structured handoff data, clear responsibility boundaries, and records that can be reconciled to the books without reconstructing the run from scratch.

LeoFolio pathway

Working with recurring small-business clients? Explore LeoFolio for Bookkeepers and the Pay Run workflow for reviewed payroll records and structured handoff files.

Source notes for editorial verification

Related LeoFolio resources
For Bookkeepers · Workspace · U.S. Payroll · Methodology
Explore Payroll →