Blog Product

Variance between two pay runs

5 min read

Every pay run differs from the one before it. Most of the differences have a cause someone already knows about: a hire, a leaver, a pay rise dated this period. A few do not, and those are the ones worth a look before approval. Here is how to sort the two, line by line, and why the run total is the wrong place to start.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes how to read variance in a pre-run review; it states no statutory figure and sets no threshold.

What variance compares

In TriblockHR’s pre-run review, variance compares this run against the previous run, before approval. For each employee, it shows how their line has moved.

The previous run is the right baseline most months. Pay is meant to be stable, so last period is the best guide to this one, and a movement is a departure from it.

In some months the previous run is a poor baseline, and knowing which months saves time:

  • The first run after an off-cycle run. If last month had a separate off-cycle run for a bonus or a correction, this month’s regular run is better compared with last month’s regular run than with the off-cycle.
  • The month after a large hire. If twenty people started last month part-way through the period, many of their lines will rise this month simply because this is their first full period.
  • A month with an unusual week. A public-holiday week or a seasonal peak in the previous period makes this period look low by comparison.

In those months the movements are still worth reading. They just have an explanation waiting.

Movements with a known cause

Take an invented payroll lead, Jerome Pinder, reviewing the monthly run at a fictional hotel, Seagrape Resort, with about 300 staff. Most of the movements he sees have a cause already on the record, and many are explained by a flag before he opens anyone’s file.

  • A hire. A new line with nothing to compare against. The information flag hired in period explains it.
  • A leaver. A line that is a final pay. Terminated in period explains it.
  • A suspension, or an employee moving on or off probation or a contract. The matching information flags explain the change.
  • A pay rise dated this period. A line up by a step, matching a promotion on the employee’s dated record.
  • A long week. More hours than usual. The warning regular hours exceeded points to it; the approved timesheet confirms it.
  • A category change. Deductions moved. The warning tax category changed in period points to it.
  • Time off. A line down because uninsured time off replaced pay, which its own warning flags.

Each of those is ordinary. Jerome confirms the cause, notes it and moves on. The flags exist so that he does not have to investigate them from scratch.

Movements that deserve a look

What is left after the ordinary movements are explained is a short list of lines that moved with no cause on the record. Those deserve a look before approval:

  • An allowance that doubled. No promotion, no new allowance agreed, but the figure is twice last month’s. Often a bulk import applied twice.
  • A rate on the wrong record. One employee’s line rose by exactly the amount another’s was meant to. A payroll that succeeds and is wrong follows one such error from entry to discovery.
  • A timesheet counted in two periods. Hours that appear this month and last.
  • A line that did not move when it should have. A promotion on the record dated this period, with no change in pay. The absence of movement is a movement too.

Jerome does not need a percentage to tell him which lines these are. A movement deserves a look when nothing on the record explains it, whatever its size. A small unexplained movement can be a large error in waiting; a large explained one is just a promotion.

Employee level

A run total is a poor guide. Two errors can cancel in it.

At Seagrape this month, one chef’s overtime was keyed twice, adding a few hundred dollars to his line. A housekeeper’s allowance was accidentally removed, taking a similar amount off hers. The run total is almost exactly what Jerome expected from the month’s hires and leavers. Read at the total, nothing is wrong. Read at employee level, two people are about to be paid incorrectly in opposite directions.

So variance is read line by line. The total is a summary to glance at after the lines have been read.

Recording the explanation

When Jerome explains a movement, he records why: the hire, the dated promotion, the approved timesheet. That serves two people.

The approver, who may not be Jerome, can see that each movement has been looked at and what the cause was. Approval is staged, with recall and cancel, and a line-level audit trail on the run.

And next month’s reviewer, or an auditor in six months, can see that this month’s movement was understood at the time. The audit feed shows who changed what on the records behind the movement. The note shows who looked at the movement and what they concluded.

A run with every movement explained is not guaranteed to be right. It is a run in which nothing moved without someone knowing why, and that is the best a review before approval can offer. The checks worth running before you approve places variance in the wider review.

Questions

What does pay run variance compare?

This run against the previous run, before approval, employee by employee.

Which movements are usually ordinary?

Hires, leavers, suspensions, probation and contract changes, dated pay rises, long weeks and category changes, most of them explained by a flag.

Why not just check the run total?

Two errors in opposite directions can cancel in the total. Variance is read line by line.

Is there a threshold for a movement worth checking?

A movement deserves a look when nothing on the record explains it, whatever its size.

Read every movement before approval, and know why each line changed.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas