Buying stage: diagnosis, finding out what is wrong
Twelve questions show whether a Unit4 HR and payroll configuration still matches its own documentation. None requires opening Unit4 Business World. Two fall in each of the six areas Bear Consulting Services assesses in a Unit4 X-Ray. The weakest pair shows where to look first.
The six areas are configuration drift, defect inventory, control gaps, undocumented architecture, capability deficit and cloud readiness. Each question has three answers: yes, and it is written down; partly, or not recently; no, or not known. None asks for a number that needs clearance before sharing.
Two weak answers in one area mean that area runs on knowledge nobody has written down. A wrong configuration is a different problem, and it is fixed differently.
The two checks
History accumulates in the Unit4 resource master and position master. Resource types and classes, status and date control, position numbering and legacy reconciliation, position relations and attributes: somebody chose each on a particular day. Flexi field groups on the personnel tabs are added for a process that needs them and rarely retired.
Drift begins when nobody holds that list and nothing records the last change. A configuration change should leave a written baseline, an execution record and a post-change validation.
The two checks
Workflow is where faults are easiest to see. Element type routing, approval chains from line manager to cost-centre approver to HR and payroll, substitutes and proxies: change any of these and ghost tasks, bypassed approvals and missed routing follow.
Most teams know their faults. What is missing is one list, with a root cause against each. A workaround keeps the month running at a cost paid again every month.
The two checks
Roles and access across HR, payroll, learning and development, finance and procurement are configured once and inherited: role-based menu access, third-party users, substitutes and proxies, production, test and sandbox. Recertification is the control most often deferred, because nothing visibly breaks.
Without a current matrix, approval limits exist only in the workflow configuration, and at audit nobody can evidence who was permitted to approve what.
The two checks
A system is operable only once somebody has written down how to run it: the monthly payroll playbook, an error catalogue, decision trees and process maps, line-manager guides.
Interfaces around Unit4 include pension scheme submission files, HMRC gateway submissions, BACS output and applicant tracking feeds, each with its own timing and failure behaviour. Alerts and automated tasks belong in the same picture.
The two checks
Browser queries for headcount, absence, casework and payroll extracts, Excelerator templates and the standard report set are the working level of reporting. SQL against the Unit4 schema, for correction work and statutory extracts, is the level above.
Year-end and statutory patches arrive on a fixed calendar. A patch not proved before the live run is corrected in the following period, after the payslips have gone out.
The two checks
Smart client to web client migration means client-to-client mapping, module-by-module test scripts, landing page configuration, data cleanse and defect remediation ahead of cutover. Without the dependency inventory that work cannot be scoped.
Every load or migration needs validation rules, reconciliation checkpoints and rollback criteria agreed before it runs.
One council would have answered no to the undocumented-architecture pair. It ran a payroll with multiple pay entities, including a schools payroll, and carried manual effort nobody had mapped end to end. Bear Consulting ran an independent system review, which mapped the workflows, specified the fixes and sequenced the remediation into a phased roadmap with consultancy estimates, written for an executive audience.
The review and its procedures enabled a move to self-service entry, forecast to save about 9,000 administrative hours a year.
The first call covers the weakest pair and what to do about it.