Running payroll and HR alongside SAP Business One in the UK

Payroll is the part of an ERP project that most often surprises UK finance teams. Companies choose SAP Business One for finance, stock, sales and production, then ask late in the day where the people side fits. This page explains how to organise SAP Business One payroll and HR in a UK business, what to expect from the ERP itself, and which decisions to take with your integrator before the design is frozen.

What SAP Business One covers, and where payroll sits

SAP Learning describes the product as covering finance and accounting, sales and purchasing, inventory, production with material requirements planning, customer and supplier relationship management, service management, project management, and reporting and analytics. That is a broad business scope, and it is the right starting point for any conversation about people processes.

Payroll and full human resources management are not named in that description. This matters for your planning: do not assume a ready-made UK payroll module will be switched on. The realistic question is how payroll will be run next to the ERP and how the two exchange information. For a wider view of the product, see our overview of the SAP Business One modules.

SAP also states that the product is sold through a partner network and supported by a large catalogue of sector and country extensions, and that it is available in 50 localisations. Extensions can fill gaps, but each one is a separate product with its own supplier, support terms and upgrade path. Treat any HR or payroll add-on as a component to be evaluated on its own merits.

Split the topic in two: HR data and payroll processing

Most confusion disappears when you separate two jobs.

HR data: the employee as a master record

An ERP naturally holds employees as people who approve orders, own cost centres, are assigned to projects or appear as sales owners. That information is useful in operations: who can sign off a purchase, which engineer is booked on a service call, which salesperson owns an account. Keeping it in the ERP avoids parallel spreadsheets.

Payroll processing: statutory work with its own cycle

Payroll in the UK is a statutory process with its own calendar. It covers gross-to-net calculation, tax codes, National Insurance, statutory pay, workplace pension contributions and the reporting that goes to HMRC. It changes every tax year, which is why most SMEs entrust it to a product whose supplier tracks the rules. Our guide to payroll software and RTI goes into the reporting side in detail.

The three common ways to organise it

None of these is universally right. The choice depends on headcount, pay frequencies, how many pay elements you manage (overtime, shift allowances, commission), and how comfortable your finance team is with maintaining an interface.

Connecting payroll to the ledger

Whatever route you pick, the ledger link needs to be designed deliberately. A sound payroll journal is simple in principle: it carries gross pay, employer costs, deductions, and the liabilities owed to HMRC, pension providers and employees.

Points to settle with your integrator and accountant:

• Account mapping. Which general ledger accounts receive wages, employer National Insurance, pension costs and the liability balances.
• Cost centres and projects. Whether payroll costs are split by department, site or project. This is where an ERP adds real value, especially for contractors and project-based work.
• Timing. When the journal posts relative to the pay date, and how accruals are handled at period end.
• Reversals and corrections. What happens when an off-cycle payment or a correction is made after the journal has posted.
• Reconciliation. A routine control that matches the liabilities in the ledger to what has actually been paid over.

If your general ledger design is still open, read our page on accounting and finance in SAP Business One first, because the payroll journal will land in that structure.

UK points of vigilance

Real Time Information

Employers report pay to HMRC through Real Time Information each time they pay staff. The reporting should come from the payroll product, not be rebuilt in the ERP. Make sure the interface does not create a second source of truth for pay figures. If amounts differ between the payroll output and the ledger, you want to know which one HMRC has already received.

Workplace pensions

Automatic enrolment brings a separate stream of data: eligibility, contributions, provider files. These are normally handled in the payroll product. Your ERP only needs the resulting cost and liability postings, mapped to the right accounts.

Making Tax Digital and the finance calendar

Payroll does not sit inside Making Tax Digital for VAT, but it affects the same ledger from which your returns are prepared. Staff costs, pension liabilities and VAT-exempt items must all land correctly. Our guide to Making Tax Digital with an ERP shows how the pieces fit, and the broader legal requirements for ERP in the UK puts payroll in context with record-keeping duties.

Data protection

Employee data is personal data, and some of it is sensitive. Decide who may see salary information in the ERP, how access is logged, and how leavers are handled. User authorisations in the ERP should be reviewed with the same care as payroll access in the payroll product.

Expenses, leave and the wider HR agenda

Many firms hope the ERP will also carry holidays, expenses, recruitment and performance reviews. A practical way to deal with each:

• Expense claims. These look like purchases and finance postings, so they are often manageable through the finance side with a clear approval rule. Decide how receipts are captured and how claims reach the payroll if reimbursed through pay.
• Leave and absence. Holiday entitlement, sickness and statutory leave interact with payroll calculations. Keep the master record in one place, normally the payroll or HR product, and avoid maintaining the same balance in two systems.
• Recruitment and appraisals. These are human resources processes with little link to operations. A specialist HR tool is usually a better fit than stretching the ERP.
• Time and attendance. Shift-based sectors such as manufacturing or logistics may need clocking data to flow to payroll. Define the format and who validates it.

Ask the integrator to prove each requirement in a demonstration on your own cases, not on a generic company, and write the outcome into the project scope.

Interfaces: who builds and who maintains

An interface is a small product in its own right. Before signing, clarify:

1. Who builds it and who owns the documentation.
2. How errors are reported and who fixes them on pay day.
3. How the interface is tested when the tax year changes or when either product is updated.
4. What happens if the payroll supplier changes later.

The principles are covered in our page on SAP Business One integrations. If your payroll flows need something non-standard, the customisation page explains what bespoke work involves and why it must be kept to what is genuinely needed.

Where payroll fits in the project plan

Payroll should appear in the plan from the start rather than as a late work package. In an implementation it is wise to:

• fix the payroll approach at design stage, with the accountant involved;
• test the journal on real pay data, with a parallel run against the existing process;
• choose a cut-over date that respects the tax year and your pay calendar;
• train the payroll owner and a deputy so that pay does not depend on one person.

Budget and scope go together. Our page on SAP Business One pricing explains what drives cost, and an interface or add-on is one of the items to list explicitly in a quote.

Questions to put to a prospective integrator

When you meet integrators, ask them how they have connected payroll to SAP Business One for UK clients, what they recommend for your size and why, and who maintains the link after go-live. Ask for a written statement of what is in and out of scope for people processes. Our guide to choosing a SAP Business One partner lists further checks, and how our service works explains how we introduce an integrator suited to your project at no charge to you. For UK-specific context, see SAP Business One in the UK.

Summary

SAP Business One gives you a solid operational and financial base, and employee data is a natural part of it. UK payroll, with its Real Time Information reporting and annual rule changes, is usually best run in a dedicated product connected to the ledger through a well-designed journal. Decide the route early, name an owner, test with real data, and keep the interface documented.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.