Using a payroll bureau: keep control of the bank payment even when payroll is outsourced

A payroll bureau can calculate wages, prepare Real Time Information submissions and sometimes arrange payments, but outsourcing payroll does not outsource the employer's legal responsibility. The business should know who controls the payroll file, who releases money from the bank, and how each payroll run is checked before employees and HMRC are paid.

The employer remains legally responsible for PAYE tasks

GOV.UK says an employer can pay a payroll provider such as a bureau or accountant to run payroll, but the employer remains legally responsible for completing PAYE tasks. That includes the accuracy of information supplied, required reporting and the obligations created by payroll calculations.

Treat the bureau as a service provider, not as a transfer of accountability. Assign one internal owner who receives the payroll summary, checks unusual movements and confirms that employee starters, leavers, bonuses and deductions match the company's instructions. A bureau can process incorrect information perfectly if the employer supplied the wrong input.

Decide whether the bureau prepares payments or actually controls money

Some payroll providers only calculate payroll and send the employer a payment file. Others can support Bacs submission or make HMRC payments on the employer's behalf. Document the exact boundary. The company should know whether the bureau can create a file, upload a file, approve a file or debit the company account directly.

Where practical, keep final banking approval with named company users. The payroll bureau can prepare the numbers while a finance director or authorised manager releases the payment. That preserves segregation between payroll calculation and cash movement. If the bureau has payment authority, set contractual limits and require reports showing every amount and beneficiary released.

Reconcile the payroll file before it reaches the bank

Compare the net-pay file with the payroll summary before approval. The employee count, total net pay, largest individual payments, new bank accounts and one-off bonuses should all be reviewed. A total that moved from £180,000 last month to £245,000 this month needs explanation even if the bureau says the file generated successfully.

Use exception reporting rather than trying to reread hundreds of ordinary employees. Flag new starters, changed bank details, duplicate accounts, payments above a set threshold and employees receiving unusually different net pay. This catches both payroll errors and bank-detail fraud before the payment file becomes irreversible.

Keep HMRC payments visible even if the bureau calculates them

The bureau may tell the employer the PAYE, National Insurance, student-loan, Apprenticeship Levy or CIS amount due, but finance should reconcile that amount to payroll reports and the HMRC account. The monthly liability should not be treated as an unexplained number supplied by an external processor.

If the bureau makes the HMRC payment, retain the reference, payment confirmation and date. If the company pays HMRC itself, keep the Accounts Office reference under company control and verify the period where extra reference digits are needed. Outsourcing calculation should not weaken the tax-payment audit trail.

Control employee bank-detail changes independently

Employee bank details are sensitive payment instructions. Require changes through a trusted HR or payroll process, not by informal email to the bureau. Where possible, have the employer verify the change and then instruct the bureau, rather than allowing the bureau to accept unverified requests directly from employees.

Keep a change log showing who requested the amendment, who approved it and which payroll first used the new account. For material payrolls, compare changed bank details against the prior month before release. A compromised employee mailbox should not be enough to redirect salary without another check.

Reconcile payroll after payment, not only before it

After payday, match the bank debit or Bacs report to the approved payroll total and investigate rejected credits. A payment file can be accurate overall while one employee payment fails because of invalid account data. That employee still needs paying, and the replacement payment should not create a duplicate when the original item is retried.

Keep the payroll report, bureau invoice, RTI confirmation, HMRC liability, payment file and bank settlement together. The employer should be able to trace the entire cycle from gross pay to employee receipt and tax payment even if most calculations happened outside the company.

A useful monthly control is a payroll sign-off sheet with six numbers: employee count, gross pay, net pay, employer taxes, pension funding and the total bank file. Compare each with the prior month and explain large movements before approval. If headcount increased by two but net payroll rose 28 percent, the reviewer should see the bonuses, back pay or correction that created the difference.

Also define an emergency process for payday failures. The company should know who can obtain the rejected-payment report, who verifies corrected employee bank details and who approves replacement Faster Payments. Replacements should reference the failed payroll item so finance can prove that the employee received one salary payment, not an original Bacs credit plus an accidental duplicate.