Completed runs, HMRC outcomes, corrections and recovery as payroll software metrics

Payroll metrics should show whether a defined customer outcome was completed accurately and recoverably. Logins, files generated and buttons clicked are activity measures. They can help diagnosis, but they do not prove that employees, HMRC or pension providers received the intended result.

Completed payroll rate

Define the start and end of a payroll transaction. A defensible end may require approved calculation, employee payment output, HMRC response, pension exchange, employee documents and reconciliation. State which components apply.

The GOV.UK Service Manual's completion-rate guidance emphasises defined start and end points and a denominator containing failed or partial starts. Its government-service definition is not automatically a commercial payroll standard, but the measurement discipline is useful.

HMRC reporting outcomes

Count prepared, approved, transmitted, acknowledged, rejected, corrected and unresolved reports separately. HMRC's FPS guidance explains reporting and correction around payday. A transmitted file should not be labelled accepted without the relevant response evidence.

Measure rejection rate, time to resolution and repeat cause. Segment by tax year, product build, employer type and submission route where sample size allows.

Correction rate

Use a numerator of payrolls or employee records requiring defined correction and a denominator of eligible completed units. Classify cause: customer input, operator action, product calculation, configuration, integration, official response or unknown.

HMRC's correction guidance shows that different errors need different treatment. Track customer outcome repair, not only defect closure.

Pension exchange and reconciliation

Count files or connections created, sent, accepted, rejected and reconciled. Record contribution differences and time open. The Pensions Regulator's software task list demonstrates why calculation alone is incomplete.

Support and recovery

Measure authenticated contacts, payroll-critical cases, first response, meaningful update, workaround, technical restoration and final resolution. For incidents, add affected payrolls, duplicate actions prevented, data recovery and correction time.

Cost and customer health

Track cost per completed payroll, implementation effort, support minutes, gross margin, renewal and expansion by cohort. Keep trials and imported employees out of paying-customer measures unless definitions expressly include them.

Data quality and reporting lag

Attach a freshness marker to every metric. Payroll approval may appear instantly, while an official acknowledgement, pension response or resolved support case arrives later. A daily view should therefore show the latest complete period as well as provisional activity. Otherwise a recent cohort can look worse simply because its outcomes have not matured.

Check missing identifiers, duplicate events, reversed status changes and totals that disagree with the underlying employer records. Reconcile a sample back to restricted source evidence. If a supplier cannot determine whether an absent response means pending, failed or unrecorded, report the state as unknown instead of assigning success.

A compact metric record

For a completed payroll rate, the record could state: eligible employer-pay-period workflows as the denominator; workflows reaching every supported end state as the numerator; England-based employers in the chosen service tier as the population; and seven days after pay date as the observation cut-off. The definition should also explain how reversals, re-runs and employers with no employees are treated.

Set an investigation trigger from operational risk and capacity, not an attractive industry number. One threshold may warn the service desk, while a stricter sustained threshold prompts product or incident review. Record the rationale and review it after material workflow changes.

Publish metric name, purpose, formula, unit, source systems, exclusions, owner and change history. The Service Manual's performance-data introduction recommends using measures to improve the service. Remove a metric that cannot guide a decision, and never change the denominator merely to improve the chart.