Setup Considerations: pay groups

What this achieves

A pay group decides who is paid together, and every group you create is a separate payroll run to prepare, review, approve, and finalise each period. Choosing the smallest set of groups that your entities and calendars actually require keeps the monthly workload down.

What forces a separate pay group

Three things make a shared group impossible. Everything else is a preference.

Option	Description
A different legal entity	A pay group belongs to one entity. Two entities always mean two groups.
A different pay frequency	Monthly, bi-weekly, and weekly cannot share a group, because the group carries one calendar.
A different currency	Currency comes from the entity, so a different currency already means a different entity, and therefore a different group.

Example: HC Corp UK Ltd pays monthly salaried staff and weekly warehouse staff. The frequency differs, so that is two groups even though the entity is the same. HC Corp Inc. is a different entity, so it is a third group regardless of its calendar — and the group’s other two entities bring the same requirement again, which is why a four-country business runs more payroll cycles than it first expects.

What does not require a separate group

Departments do not. Grades do not. Neither do different allowances, because an eligibility rule can grant an allowance to some members of a group and not others.

Splitting a group by department is the most common unnecessary split, and it doubles the number of runs without changing a single payslip.

Example: HC Corp UK Ltd does not need one group for Engineering and one for Sales. Both are monthly, both are in the same entity, and a London travel allowance reaches only the people it should through a rule rather than through a separate group.

Decision: how many runs you want to process

Each group is a run per period, and each run carries the same lifecycle — inputs, calculation, review, approval, finalisation — including the requirement that a second admin approves it.

Example: if HC Corp UK Ltd ran four monthly groups where one would do, Priya Raman prepares four runs a month and Daniel Okonkwo approves four, for the same set of payslips.

Decision: pay day

The pay day is set per group, so groups can pay on different days. Decide it against your own cut-off rather than the other way round: everything feeding the run — approved leave, attendance, one-off inputs — has to be in before you calculate.

Example: a monthly group paid near the end of the month leaves Priya Raman little room between the leave cut-off and the pay date. Moving the pay day, or moving the cut-off, is a decision to make before the first run rather than during it.

Decision: retiring a group

Groups carry an active switch. Retire a group by deactivating it rather than deleting it, so the runs it has already produced keep their context.

What is expensive to change later

Decision	Cost of changing later
Legal entity	High. The entity determines currency and statutory treatment, and runs already finalised under the group stay as they were.
Pay frequency	High. It changes the period boundaries, so it is a mid-year change to how people are paid rather than a setting.
Splitting one group into two	Medium. New groups apply going forward, and prior periods keep the old grouping, so period-on-period comparison spans two shapes.
Pay day	Low to medium. It moves a date, but it moves everyone in the group and it moves your cut-off with it.
Group name	Low.

What happens next

Once groups exist, confirm that each one’s entity has a statutory profile covering the period you are about to pay. A run needs both: the group tells it who and when, and the entity’s statutory profile tells it what to deduct.