Pay Group

What a pay group is

A pay group, also called a payroll group, is a set of employees whose wages are calculated together in a single payroll run, because they share one pay cycle, one cutoff date and one set of calculation rules.

A pay group is an operational unit, not an organisational one. It does not describe who reports to whom in the structure; it describes whose pay is calculated when, and alongside whom. A single organisation may have one pay group, or it may have five.

The four things that put employees in the same pay group

• The cycle: monthly, twice a month or weekly. An employee on a different cycle needs a different group.
• The cutoff date: the day on which attendance, overtime and absence close for that run. Employees who share a cycle but have different cutoff dates form two groups, not one.
• The paying entity: the legal entity or the account the wages are paid from. A different paying entity forces a separate group, because the bank file is different.
• The shared calculation rules: what is calculated by the hour and what by the month, and what is taken from attendance and what is not.

Nothing outside these four is a reason to split a group. A difference in department, branch or grade does not call for a second group, because all of these are data held on the employee record and used to sort reports after the calculation.

How the cutoff date defines a pay group

Take a monthly group with a cutoff on the 25th, and a month that ends on the 30th. This month’s run covers attendance from the 26th of last month to the 25th of this month. An employee who worked 6 hours of overtime on the 27th will not see those hours in this month’s run; they appear in the following one.

This delay does not accumulate. In this example each run carries five days from the previous month and leaves five for the next, so the days coming in match the days going out, and the account stays level over the year. The balance fails at two edges: an employee’s first month, when there is no earlier run to carry anything forward for them, and the last month of someone whose service has ended, when there is no later run to pick up what remains. Those two edges are the only cases that need a calculation outside the cycle.

What the cutoff affects needs to be kept apart from what it does not. A fixed monthly wage is untouched by the cutoff date, because it is paid for the whole month. What moves with the cutoff is whatever depends on attendance: overtime, absence and anything else taken from the time record. Dividing a wage in proportion to part of a period is the subject of pro rata salary.

How many pay groups an organisation needs

Every pay group carries a fixed cost in every cycle: a review before approval, a reconciliation after it, and a bank file of its own. So count the runs in a year:

• One monthly group: 12 runs a year.
• Three monthly groups: 36 runs.
• Three monthly groups plus a weekly group for one category of workers: 36 plus 52, or 88 runs.

If review and reconciliation take 6 hours per run, the total comes to 72 hours in the first case and 528 hours in the third. Adding one weekly group to three monthly ones took the number of runs to more than seven times the first case.

The lesson of this calculation is that a weekly group costs more than four times as much as a monthly one, not because each of its runs is heavier but because it recurs. Where faster pay for one category is the organisation’s choice, the organisation pays for that choice in the number of cycles, not in the volume of work. For some wage types a weekly payment is a legal minimum rather than a choice, and that is a question for the payment date rules, not for the design of pay groups.

The figures in this calculation, and in the examples throughout the definition, are hypothetical. They are there to show the calculation, and they are neither a benchmark nor taken from any source. In the sources we reviewed we found no published reference for an appropriate number of pay groups, and the calculation above counts a cost; it does not recommend a number.

Moving an employee between two pay groups

A transfer between two groups with different cutoff dates can cause a calculation error. Take group A with a cutoff on the 25th and group B with a cutoff on the 20th, and a transfer that takes effect on the first of the month:

• From A to B: the last run in A covered attendance up to the 25th of the previous month, and the first run in B starts from the 21st of that month. Days 21 to 25, which is 5 days, are counted twice.
• From B to A: the last run in B ended on the 20th, and the first run in A starts from the 26th. The same five days are not counted at all.

Both cases are calculation errors, not differences of opinion: the first pays for some days twice, and the second drops days that were worked. For that reason, every transfer between two groups records the day on which the first group stops covering attendance and the day from which the second group starts, and the two are matched before approval. Double counting shows up as an overpayment to be corrected later, a subject with its own rules and limits, covered in our guide to wage deductions. Correcting it after the event can be harder than preventing the overlap in the first place.

Why a weekly pay group produces unequal months

A year has 52 full weeks and 12 months. If every month had four weekly runs, the total would be 48, leaving 4. So in a year of 52 weekly runs, four months contain five runs, and eight contain four.

The effect on reporting is direct: the group’s cost in a month with five runs is 25% higher than in a month with four, because 5 divided by 4 is 1.25. No one’s wage has changed, and no employee has been added.

Taking this rise as a rise in labour cost is a mistake, and a decision based on it in a particular month rests on the number of weeks. Weekly groups are therefore compared by number of runs rather than by month, or the figure is adjusted to a single weekly basis before it goes into a table beside a monthly group.

The review window between cutoff and payment

A group with a cutoff on the 25th and a payment date on the 30th leaves 5 days between them. Everything happens in those days: extracting attendance, dealing with any gaps in it, calculating pay, reviewing and approving the run, and sending the bank file.

Moving the cutoff closer to the payment date to get more recent data narrows the window by the same amount. An organisation that moved its cutoff from the 25th to the 28th gained three days of attendance and lost three days of review, leaving two days out of five. This is a direct trade, and there is no way to gain on both sides.

The pressure on the review window grows with the number of groups, because their windows overlap: three monthly groups with close cutoffs have their reviews fall on neighbouring days for the same team. That is why cutoff dates are spaced apart at the design stage, not because close dates are forbidden, but because the team’s time cannot be divided.

When wages must be paid is a legal question with its own sources, covered in our guide to wage payment dates and the final settlement. The definition of a pay group settles nothing on that question.

How a pay group differs from a payroll run, payroll accounting and a salary structure

• A payroll run is the event: the run in which wages are calculated and approved. The pay group is the set of people included in that event. The run recurs, while the pay group persists from one run to the next.
• Payroll accounting deals with how the cost of wages is recorded in the books and how it is allocated, while a pay group deals with whose pay is calculated alongside whose. The cost of one group may be spread across several cost centres, and the cost of two groups may sit in a single cost centre.
• A salary structure decides how much an employee is entitled to, while a pay group decides when that pay is calculated and in which batch. Two grades in one structure may fall into two different pay groups, and the reverse also holds.

What undermines a pay group

• Creating a group for a single case. An employee with a special arrangement is given a group of their own, which adds a full cycle, with its review and reconciliation, for the sake of one line.
• Mirroring the organisation chart. A group for each department produces as many runs as there are departments, with nothing gained in return, because reports are sorted by department after the calculation, not before it.
• Changing the cutoff date partway through the year. The change produces one month that is longer or shorter than the rest, and the monthly comparison then shows a rise or fall in cost that has no source in the work.
• Mixing two cycles in one group. A category paid weekly and a category paid monthly in the same group forces whoever runs payroll to make a manual exception on every run, and a manual exception repeated run after run is a point at which errors can enter.
• Leaving employees whose service has ended in the group. Membership carries over between runs, so anyone not removed in time is picked up by the next month’s run and gets a line that has to be corrected after approval.
• Assigning no owner to the group definition. When adding a group needs no written decision, groups can multiply over the years until nobody knows why one of them exists.

Before a new pay group is created

Ask one question: which of the four things that define a pay group differs? If the difference lies in the cycle, the cutoff date, the paying entity or a calculation rule, the group is needed. If the difference lies in anything else, what is needed is a field held on the employee record, not a group that has to be run every month.

Then write down two things for each group and review them once a year: its cutoff date, and who joins it and who leaves it. Where a group has no written cutoff date, its days are counted by habit, and habit changes with whoever runs payroll. That is how differences with no known cause come in.

This is an explanation of the concept, not legal advice.

Related terms

• Payroll Accounting
• Payroll Statement
• Wage Protection System (WPS)
• End-of-Service Benefits (EOSB)