HRIS

Independent HRIS selection and implementation assurance

An HRIS or HCM programme touches every employee's record, pay and manager. We select, plan and assure HR system implementations on the client side, with no vendor ties, so the system you buy is the one your HR, payroll and finance teams can actually run.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
0licences or commissions

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

What sits inside an HRIS programme

HRIS, HCM software, HRMS: the labels blur, but the scope decision is the same. The core is the employee record: positions, reporting lines, contracts, pay elements, cost centres and the dates that drive everything else. Around it sit the modules an HR system implementation can switch on, defer or leave to another product.

Payroll, or the payroll integration. The single biggest design decision. Native payroll means one record and one gross to net engine; integration means an interface, a reconciliation and two suppliers to manage. Our payroll implementation page covers the HMRC side.

Absence and time. Holiday accrual rules, sickness recording that feeds statutory sick pay, rotas and timesheets where hours drive pay.

Recruitment and onboarding. Applicant tracking, offers, right to work evidence and the joiner workflow that creates the record payroll will pay.

Performance, learning and compensation. Objectives, reviews, mandatory training and the annual pay review that has to land back in payroll on the right date.

Most mid market buyers do not need all of it on day one. We help you decide which modules earn their place now, which can wait and which stay in a specialist tool, before a vendor demo decides for you. That ordering, more than the brand on the login screen, separates the HR system implementations that settle in from the ones that stall after core HR goes live.

The record at the centre, and the modules around it

The employee record Positions and reporting linesContracts and pay elementsCost centres and key dates Payroll, native or integratedThe single biggest design decisionAbsence and timeAccrual, sickness to SSP, rotasRecruitment and onboardingOffers, right to work, joiner workflowPerformance, learning, payReviews, training, the annual pay review NowLaterSpecialist toolFor each module, decide which before a vendor demo decides for you

The UK market in three tiers

The UK HRIS market sorts itself by headcount, payroll complexity and how much configuration you can live with.

Enterprise suites. Workday HCM, SAP SuccessFactors, Oracle Fusion Cloud HCM and Dayforce. HMRC's list of recognised payroll software includes Workday, Dayforce Payroll, Oracle's Fusion Cloud HCM and SAP Payroll, so UK payroll inside the suite is a real option rather than a roadmap promise. Expect a negotiated subscription and a systems integrator alongside the vendor.

Mid market. MHR's iTrent and People First, Zellis, Sage People, Cezanne HR, HiBob and Personio. Cezanne positions itself for 50 to 3,000 employees, prices by module and monthly headcount and charges no implementation fee. Personio quotes for 10 to 10,000 employees with Core, Core Pro and Core Enterprise plans plus add on apps for recruiting, performance, surveys and compensation. HiBob sells a core platform with modules for compensation, hiring, learning, time and attendance and workforce planning, and lists UK payroll as an option. Zellis, the payroll incumbent, says one in seven UK and Irish employees are paid through it.

Small business. Employment Hero publishes £6 and £9 per employee a month for HR Essentials and HR Engage with a ten user minimum, plus a free payroll tier; CharlieHR prices by team size from £21 a month excluding VAT. Prices checked November 2026.

Our HR software buyer's guide compares the tiers product by product. For a selection the rule is simpler: shortlist within one tier, and make each vendor prove UK payroll, pensions and statutory leave in a scripted demo on your own data.

Who sits in which tier

Enterprise suitesNegotiated subscription plus integratorWorkday HCMSAP SuccessFactorsOracle Fusion HCMDayforceMid marketMHR iTrentZellisSage PeopleCezanne HRHiBobPersonioSmall businessPublished per employee or team pricesEmployment HeroCharlieHR Shortlist within one tier, and make each vendor prove UK payroll, pensions and statutory leave on your own data.

Employee data, UK GDPR and the joins to payroll and finance

An HR system migration moves the most sensitive data a company holds: salaries, sickness, bank details, right to work documents, disciplinary records. Treat it as a data protection exercise as much as a technical one.

The ICO's employment practices guidance on keeping employment records asks the questions your migration plan should answer: the lawful basis for each record, how much you hold, how long you keep it, the extra conditions for special category information such as sickness and occupational health records, how workers get access, how records stay secure and what happens when processing is outsourced. The ICO says the guidance is under review following the Data (Use and Access) Act 2025, so check the current version before you fix your retention rules.

In practice that means a field level mapping from the legacy system, a decision on how much history migrates (three years of absence? every historic salary?), cleansing of duplicate and dormant records before load, and an archive for what you leave behind. Our data migration consultancy runs that discipline.

Then the joins. Payroll needs starters, leavers, pay changes and absence on time and in the right tax month. Finance needs the payroll journal mapped to cost centres and the general ledger, and headcount and cost reports that reconcile to it. Identity needs joiners, movers and leavers to create and remove accounts. Each interface needs an owner, an error queue and a reconciliation, which is the same discipline we apply to ERP integration.

What the migration plan has to answer

QUESTIONS FROM THE ICO EMPLOYMENT RECORDS GUIDANCE Lawful basis foreach recordHow much youholdHow long youkeep itSpecial categorydataHow workers getaccessHow records staysecureOutsourcedprocessing The ICO says the guidance is under review after the Data (Use and Access) Act 2025, so check the current version.

The joins that keep the record true

HR system of record PayrollStarters, leavers, pay changes and absenceFinancePayroll journal to cost centres and the ledgerIdentityJoiners, movers, leavers: accounts made and removed Every interface: an owner, an error queue and a reconciliation

Adoption, then Part A or Part B

HR systems fail quietly. Managers keep approving holiday by email, HR keeps a spreadsheet of the true salaries, payroll re keys changes, and within a year the system of record is not. Adoption is a design input, not a training course at the end: manager self service has to be faster than the old route, approvals have to match how the organisation actually delegates authority, and the HR team's own processes have to change before the software is configured to copy the old ones.

There are two ways to work with us, and clients take either or both.

Part A, independent assurance. We sit on your side of the table alongside your team and the vendor or systems integrator: requirements and scoring, contract and licence review, design authority, data and cut over readiness, test exit and the go live decision.

Part B, delivery. Our own practitioners run the programme or the workstreams you cannot staff: programme management, data migration, integration, payroll parallel runs and change.

Our consultants have led and analysed the decisions that come before, during and after an HR system migration, and the implementations that followed. Our team has spent 19 years delivering major systems programmes on five continents. We hold no reseller, referral or alliance agreement with any HR software vendor and take no commission, so our recommendation is the one we would make with our own money. Fees are shown plainly on our pricing page.

How HR systems fail quietly

Managers approveholiday by emailHR keeps a spreadsheetof true salariesPayroll re keyschanges Within a year, the systemof record is not So adoption is a design input: self service faster than the old route, approvals that match real delegation.

What we have delivered

22m+assets, National Grid separation

Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.

£25msaving at BP Pulse, 39 days early

Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.

£9bnEnergy Bills Support Scheme

Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.

19 yrsfinance systems delivery

Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.

ERP and CRMpre, mid and post migration

A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

What is the difference between an HRIS, an HCM and an HRMS?

In practice they describe the same category of software: a system of record for employees with modules around it. HRIS usually means the core record, absence and reporting; HCM is the term the enterprise vendors use for the full suite including talent, payroll and workforce planning; HRMS is an older label for the same thing. Buy on scope and fit, not on which acronym the vendor prefers.

How long does an HRIS implementation take?

A small business tool can be live in weeks. A mid market HRIS with payroll usually runs for months rather than weeks, because payroll has to cut over at a tax month or at the 6 April tax year start and needs parallel runs first. Enterprise suites take longer again because of integration, multiple countries and the number of design decisions made before configuration starts.

Should payroll be inside the HRIS or run in a separate system?

Inside gives you one employee record, one absence feed into statutory pay and one supplier. Separate lets you keep a payroll specialist or bureau you trust and change the HR system without touching pay. Decide payroll first on its own merits, including who will own compliance each April, and then choose the HR system that fits around that decision.

How do we protect employee data when migrating to a new HR system?

Map every field from the legacy system, decide how much history you actually need under your retention rules, cleanse duplicates and dormant records before loading, and archive what you leave behind. Apply the ICO's employment records guidance on lawful basis, special category data and security, limit who can see migration extracts, and record the processing so you can answer an access request afterwards.

What does independent HRIS selection and implementation assurance cost?

It depends on whether you want Part A assurance alongside your team and the vendor, Part B delivery by our practitioners, or both, and on how many modules, countries and interfaces are in scope. We take no commissions or referral fees from any HR software vendor, so the fee is the whole cost. Our fees are set out plainly on our pricing page.

Choosing or rescuing an HR system?

Tell us where you are: shortlist, contract, mid implementation or struggling after go live. We will say plainly what we would do next.

Book a conversation