What configuration debt looks like in a mature Unit4 system

A defect is something that does not work. Configuration debt is everything that still works, individually, for reasons nobody can now reconstruct.

Every mature Unit4 system carries it. An absence code was created for a scheme that ran for two years and was then withdrawn. The code stayed. A flexi field group was added for one directorate to hold what the standard tabs did not. It is still live, filled in by people never told its purpose. A workflow route was amended to clear an approval during a reorganisation. The amendment outlived the reorganisation by six years. Each made sense on the day.

One test: ask three people who run HR and payroll to describe, without opening the system, how one process runs from manager’s request to payslip. Three partly right answers mean the system has drifted.

Drift collects in four places.

Attributes and attribute values. Position and resource attribute sets, equal opportunities and diversity values, and their linked document types are easy to add and almost never retired. Value lists grow, superseded values stay selectable and reports stop meaning what their readers think.

Flexi fields. Group headers, members and value lists at tab level, with conditional hide and show rules, are the fastest way to capture what the standard screens do not hold. Groups that should have been closed remain active, their members’ value lists never rationalised.

Workflow. Element type routing, approval chains from line manager to cost-centre approver to HR and payroll, and the substitute and proxy configuration behind them are where drift shows in daily work. Staff report ghost tasks, bypassed approvals and routing that silently misses a step. The usual cause is an amendment made for one case and left in place for every case.

Absence configuration. Absence codes, categories and grouping, special leave reasons and the sickness, annual leave and statutory schemes built on them are the most sensitive part of the system, because absence feeds pay. A category grouped wrongly at build surfaces with the first employee whose circumstances cross the boundary.

None is anybody’s fault.

First, configuration is nobody’s job. It belongs to HR as a form, to payroll as an element, to finance as a cost distribution and to IT as a fault. Nobody owns the whole picture.

Second, documentation is the first thing cut under service pressure. The change is made because the pay run is on Thursday. The build note is never written, and the person who knew why moves on.

Third, testing follows the change. A change request is tested against itself and passes. Its interaction with the eleven earlier changes to the same element, code or route is never tested, because nobody holds the list of eleven.

The system behaves correctly for most people most of the time. Drift shows on the exceptions, as manual work nobody has counted yet.

A major-version upgrade or a move to the web client puts every HR and payroll process at risk of silent regression. Proving nothing regressed means knowing what correct behaviour was before the release, process by process. Without it, the programme’s first weeks go on rediscovering the current system at programme rates, against a fixed timetable.

The same gap undermines any strategic decision taken before the system is understood.

Bear Consulting Services reviews a Unit4 system across six areas: configuration drift, defect inventory, control gaps, undocumented architecture, capability deficit and cloud readiness. The review is written for the executive who has to decide, with findings, remediation options and an estimate for the work.

On a major-version Unit4 upgrade in local government, acceptance ran across 16 HR and payroll process areas, from position administration, applicant, starter and induction and probation, through absence, occupational health, leaver and contractual change, to loans, deductions, pensions and court orders.

The master script library was written before execution started, setting out the system’s real behaviour in advance, area by area. The project board accepted the upgrade against that phased, documented library, with dated defect status reports and a recommendation backed by the numbers.

Read the engagement in full on the case studies page.

Three places to go from here.

• Run the free Unit4 health check. Twelve questions across the six areas a Unit4 X-Ray assesses, scored on the page: the Unit4 HR and payroll health check.
• Read the diagnostic brief. The Unit4 X-Ray: a priced, fixed-scope consultancy engagement across the same six areas, reported for the executive who has to decide.
• Read the worked example. The upgrade above is written up in full as an upgrade acceptance programme across 16 HR and payroll process areas.