What Changes the Day Your Bureau Stops Running Payroll
When an accountant or payroll bureau runs your payroll, they carry more than the calculation. They hold the filing credentials, keep the year-to-date history, and catch mistakes before the bank file goes out. Taking payroll in-house moves all three jobs to you. Most first-time buyers treat payroll software implementation as a software purchase. It's really a controls project, and the software is the easy part.
Moving payroll in-house often makes sense somewhere between 15 and 50 employees, though it varies by country and pay complexity. Below that, bureau fees are small and the risk of an error can outweigh the savings. Above it, charges for changes, off-cycle runs and reports add up, and HR wants direct control over the data. As rough 2026 market ranges that vary by contract and country, small-business payroll software costs about $4 to $15 per employee per month plus a base fee of $0 to $150. Bureaus often land at $8 to $25 per employee per month once extras are counted. Confirm both with vendors in your country.
Plan for roughly 30 calendar days from contract signature to your first live run. If your jurisdiction allows it, pick a go-live date at the start of a tax year or quarter, which keeps the opening balances you must load small. The timeline below is the backbone of this checklist.
| Days | Workstream | Done when |
|---|---|---|
| 1–7 | Contract, access, statutory registrations | You can log in to every tax and social security portal yourself |
| 8–15 | Payroll data migration and opening balances | Year-to-date totals in the new system match the bureau's final reports |
| 16–25 | Parallel payroll run and variance review | Two cycles (or one cycle plus a test) reconcile within tolerance |
| 26–30 | Approval controls, bank setup, cutover | Maker-checker approval is live and the bureau has confirmed its final filing |
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Days 1–7: Registrations, Credentials and the Bureau Handover Letter
Start with access, not software configuration. Plenty of companies discover in week three that their tax portal account sits under the bureau's agent login, or that nobody internal knows the social security employer number. On Day 1, send your bureau a written handover request covering every registration number, the portal credential arrangements, and the last date they'll file on your behalf.
Registrations differ by country. Examples of what has to move or be set up:
- UK: the employer PAYE reference and Accounts Office reference, your own Government Gateway access so the software can make Real Time Information submissions, and pension auto-enrolment access with your provider.
- India: PF establishment code, ESIC code, state Professional Tax registrations where you have staff, and the TAN for TDS on salaries.
- UAE and Saudi Arabia: Wage Protection System enrollment through your bank or exchange house in the UAE; Mudad and GOSI registration in Saudi Arabia.
- Australia and Canada: Single Touch Payroll-enabled software linked to your ATO account in Australia; a CRA payroll program account for remittances in Canada.
- Latin America: IMSS employer registration and CFDI payroll stamping in Mexico; eSocial event submission in Brazil.
- US: federal and state withholding accounts, plus state unemployment accounts for each state where you employ people.
In the same week, sign the software contract and check three things. Does the vendor actually file in your jurisdiction, or only calculate? Is the implementation fee fixed? Typical 2026 ranges run from $0 for self-serve tools to roughly $1,000–$5,000 for guided onboarding. And can you export all payroll history if you leave? A vendor that can't hand over a full export in a standard format is a red flag. For single-country teams, local or regional tools such as Xero Payroll, Sage, Zoho Payroll, Employment Hero, Keka or greytHR are common choices, depending on where you operate. With staff in several countries, look at platforms like Rippling or Deel, or a payroll aggregator that works with in-country partners.
Day 7 checkpoint: an internal person can log in to every statutory portal without the bureau's help. If not, push the go-live date back now. That costs far less than a missed filing.
Days 8–15: Payroll Data Migration and Opening Balances
Payroll data migration is where most first-time errors start. You aren't just copying a staff list. You're rebuilding each employee's tax position for the year to date so the new software calculates cumulative tax, contribution caps and annual returns correctly.
Ask the bureau for these reports as of the last pay date they process: an employee master file, a year-to-date payroll summary per employee, a statutory contributions report, the last three payslips per employee, and leave balances. Load the data in the order below and check each category before moving on.
| Data category | Why it matters | Common error |
|---|---|---|
| Employee master data (IDs, tax codes or regimes, bank details) | Drives every calculation and payment | Outdated tax code or bank account copied over |
| Year-to-date gross, taxable pay and tax withheld | Cumulative tax and year-end returns | Loading net instead of taxable figures |
| Year-to-date social security and pension contributions | Annual ceilings and caps | Missing employer-side contributions |
| Recurring deductions (loans, court orders, benefits) | Ongoing obligations to third parties | Arrears balances left behind |
| Leave and gratuity or end-of-service accruals | Payouts on exit, often legally required | Accruals reset to zero |
A hypothetical example: say a 40-person company in India goes live in October. If PF and TDS year-to-date figures from April through September aren't loaded, the software may spread annual tax across the remaining six months as if the year started in October. Some people get under-withheld, others over-withheld. The test is simple: run the new system's year-to-date report and compare it line by line with the bureau's. Totals should match exactly, not roughly.
Data-protection rules apply to this transfer. The GDPR in Europe and the UK, India's DPDP Act and similar laws elsewhere expect you to move salary and bank data securely and to know who handled it. Use the vendor's encrypted import tool rather than emailing spreadsheets, and delete working copies afterward.
Days 16–25: Running a Parallel Payroll Without Fooling Yourself
In a parallel payroll run, the bureau processes the real payroll while you run the same period in the new system and compare results. It's your best protection against a bad first live run. Plenty of companies skip it because it feels like doing the work twice. Don't.
If your pay cycle allows, run at least one full parallel cycle; two is better. On a monthly cycle with a tight timeline, run one live parallel plus a test run of a past period whose results you already know. Compare at the employee level, not just total cost:
- Gross pay by earning type (basic, overtime, allowances, commission).
- Employee tax and social security deductions.
- Employer contributions and levies.
- Net pay per employee.
- Statutory filing totals the new system would submit.
Set a tolerance before you start. A workable rule: investigate any net pay difference above the equivalent of $1 per employee, and explain every difference, including small ones. Rounding differences are fine. Unexplained ones aren't. Typical causes include wrong pro-rating for mid-month joiners, an allowance taxable in one system and exempt in the other, and overtime multipliers set per policy instead of per contract.
Say the parallel run shows 3 of 40 employees off by $12–$40 in net pay (a hypothetical case). Don't patch those three. Find the rule behind the error, fix it, and rerun the whole group, because the same rule will hit other employees next month. If variances remain unexplained by Day 25, pay the bureau for one more cycle. That extension typically costs a few hundred dollars, usually less than fixing a statutory filing error.
Days 26–30: Approval Controls, Bank Setup and the Cutover Call
The bureau was your second pair of eyes. Once it's gone, build that check into your own process. At minimum, use maker-checker approval: one person prepares the payroll and a different person approves it before any payment or filing goes out. In a 20-person company, that's often the HR or office manager preparing and the owner or finance lead approving. Configure the software's roles to enforce it, so the person who edits salaries or bank details can't also release payment.
Your checklist for the last five days:
- Approval roles set up, with at least two approvers so payroll doesn't stall when someone is on leave.
- Bank details change control: any change to an employee's bank account gets a call-back check and a second approval. This is a common payroll fraud route.
- Bank file or payment integration tested with a small-value or zero-value file where your bank supports it.
- Pre-run variance report flagging any employee whose net pay moved more than 10% from last period.
- Filing calendar covering each statutory deadline, with an owner and a backup owner.
- Written confirmation from the bureau of the last period it filed and paid, so nothing is submitted twice or missed.
Before go-live, have an accountant or payroll advisor licensed in your jurisdiction review the setup. A one-off review typically costs far less than a year of bureau fees, and it catches local quirks no vendor checklist covers.
The cutover rule: go live on Day 30 only if every statutory portal is under your control, opening balances match to the cent, and the last parallel run has no unexplained variance. If any of the three fails, pay the bureau for one more cycle and fix the gap first.