What configuration debt looks like in a mature Unit4 system
Configuration drift, undocumented architecture and control gaps build up quietly across HR, payroll and finance workflow. Where they appear, why they survive and what they cost at upgrade.
Insights
Unit4 HR and payroll insights
Eight pieces on Unit4 HR and payroll, published September 2026 and grouped by the decision they serve. All are by Mircea Rogojan-Rush, who founded and runs Bear Consulting Services.
01 / Awareness
Naming the problem
For the reader who feels the problem but cannot yet describe it to a leadership team.
Why Unit4 payroll defects survive go-live
A passing script shows the system accepted an entry. The payment can still be wrong. Finding those defects takes parallel runs, regression validation and triage by payroll impact.
02 / Diagnosis
Establishing what is wrong with a Unit4 system
For the in-house Unit4 team that suspects the configuration and wants evidence before it escalates.
Twelve checks you can run on your own Unit4 HR and payroll configuration
Twelve checks across the six areas a Unit4 X-Ray assesses, from resource and position master file control to workflow routing, absence balances, role security and reporting. None requires opening Unit4 Business World.
Absence, work schedules and entitlement: where Unit4 drifts
Absence codes and categories, balance configuration, holiday calculation and open absence errors that carry between periods: where entitlement and sickness figures stop reconciling. Half-pay and nil-pay transfer usually shows it first.
03 / Selection
Choosing the size of the work
For the budget holder sizing an engagement and the sponsor about to commit to an upgrade.
Sizing the work: Unit4 review, diagnostic or remediation programme
An independent system review, a strategic diagnostic and a remediation programme answer different questions and produce different documents. The distinction matters before procurement starts.
What to ask before a Unit4 cloud upgrade or web client migration
Client-to-client mapping, landing page configuration, script coverage module by module, data cleanse before cutover, and how the upgrade lands against year end and statutory patches. Questions to ask while the upgrade can still be shaped.
04 / Delivery
Running the change
For the test or delivery manager planning the release.
Release assurance for a Unit4 payroll upgrade: scripts, parallel runs and defect triage
Release assurance is four artefacts: a reusable master script library, a parallel run against the legacy calculation, a defect queue ordered by payroll impact and a completion pack a project board can read.
05 / Assurance
Proving it before you sign
For the project board member or senior responsible owner whose name goes on the go-live decision.
Go or no-go: the evidence a project board should require before a Unit4 payroll cutover
A board should sign against quantified residual risk, defect discovery and fix rates, a test completion evidence pack and a cutover runbook.
06 / Engage
Contact
To discuss what a piece raises in your Unit4 system, book a 30-minute call.
The call covers what to look at first and which of the six services fits.
Bring the article and the question it left you with.