How to Handle Payroll for Multiple Pay Frequencies

Many small businesses have a workforce mix that doesn't fit neatly into a single pay schedule. Your office staff might expect monthly pay on the 28th. Your warehouse team expects weekly pay on Friday. Your casual workers want fortnightly. Managing payroll for multiple pay frequencies is absolutely doable — most businesses do it — but it requires a bit more setup and attention than a single schedule.

This guide walks you through how to handle payroll when you have more than one pay frequency, from initial setup through tax calculations to reconciliation.

Why businesses use multiple pay frequencies

You don't choose multiple pay frequencies to make life complicated. You choose them because they match how your workforce actually works:

Industry norms are real. Construction, hospitality, and retail workers expect weekly pay — it's how their industry works. Salaried office staff expect monthly. You can fight this, but you'll just churn through people.
Cash flow matters differently. An hourly worker living week-to-week needs weekly pay. A salaried manager with a mortgage prefers monthly.
Contracts lock you in. You may have inherited employment contracts that specify different pay frequencies. You can't unilaterally change them without consent.
It's the practical choice. A mix of full-time, part-time, and casual workers often naturally splits into different frequency groups.

One thing to note: there's no legal requirement to pay everyone the same way. But each frequency creates a separate payroll run, which means separate deadlines, separate tax filings, and more admin work. The upside is you can pay people how they expect to be paid.

Setting up multiple pay frequencies

The first step is to be deliberate about who pays when. Don't let this drift.

Start by creating pay groups — employees grouped by pay frequency:

Monthly: Usually salaried staff, paid on a fixed day each month (often the 28th to avoid month-length confusion)
Weekly: Usually hourly or shift-based staff, paid every Friday (or whichever day suits you)
Fortnightly: Every two weeks, popular in logistics and manual work
Four-weekly: Every four weeks. Important note — this creates 13 pay periods per year, not 12, which affects tax calculations

Your payroll software should let you create multiple schedules within a single employer account. Each schedule gets its own pay dates, processing deadlines, and filing windows.

Set up a payroll calendar for the whole year. Put it somewhere accessible — shared drive, Slack, printed on the wall. It should show every pay date and every filing deadline for every group. Managers need to know when data is due. You need to know when you're filing taxes. Missing a deadline once is annoying; missing it twice means you're not organized.

When you process your first payroll run, make sure each employee is assigned to exactly one pay group. Not two. One. If you accidentally run someone through two schedules, their tax gets calculated twice, which is a nightmare to fix.

Tax calculations across different pay frequencies

This is where it gets interesting. Tax in the UK is calculated per pay period, and the per-period thresholds depend on how many periods you have.

The standard Personal Allowance is around £12,570 per year (as of April 2026 — check the current year's HMRC guidance). Your payroll software divides this by the number of pay periods:

Monthly pay: £12,570 ÷ 12 = ~£1,047 tax-free per month
Weekly pay: £12,570 ÷ 52 = ~£242 tax-free per week
Fortnightly: £12,570 ÷ 26 = ~£483 tax-free per fortnight

The same principle applies to National Insurance thresholds. A weekly-paid employee will have smaller deductions per paycheck than a monthly-paid employee earning the same annual salary, but they'll have 52 paychecks instead of 12. Over the full year, total deductions should be roughly the same.

What's important to understand: your payroll software handles this math automatically, but cumulative calculations make it real. The system looks at everything earned since April (start of the UK tax year) and calculates how much tax should have been deducted by now. If someone earned a bonus one week that pushed them over a threshold, their tax will jump that week, then level out again. This looks odd on a payslip but is perfectly normal.

Pensions, reporting, and payroll automation

If you're using a workplace pension under auto-enrolment rules, contributions get calculated and submitted for each pay period. This means weekly payroll = weekly pension submissions; monthly payroll = monthly pension submissions. Check with your pension provider about their submission schedule — some are fine with multiple frequencies, others prefer consolidation into monthly submissions.

HMRC filings multiply with pay frequencies. HMRC's Real Time Information (RTI) rules require a Full Payment Submission on or before each payday. If you have weekly and monthly payrolls running on different dates, you're filing a submission every week for the weekly group and every month for the monthly group.

Here's an example: if your weekly team is paid every Friday and your salaried team is paid on the 28th, you're filing with HMRC on Fridays (52 times a year) and on the 28th (12 times a year). That's 64 tax filings instead of 12.

This is why automation matters. Modern payroll platforms submit RTI filings automatically after each pay run. You don't have to remember. You don't have to open a portal. The filing just happens.

Reconciliation and tracking across pay groups

The more pay groups you have, the more important monthly reconciliation becomes. You need to track total gross pay across all groups, total tax and National Insurance due, total pension contributions, and net payments going to employees on different dates.

Here's the easiest approach: at the end of each calendar month, run a report that totals all payroll activity from all pay groups. Compare total gross pay against budget, verify total tax withheld matches your HMRC liability, check that employee deductions are correct, and confirm net paid matches your bank statements.

When your payroll system integrates with your accounting software — like with Relentify — these reconciliations become automatic. Each pay run creates accounting entries regardless of which pay group it is, so your P&L and balance sheet stay accurate without manual work. If you're manually moving numbers between systems, you're vulnerable to typos and timing mismatches.

When an employee changes pay groups, process their final pay in the old group up to the transition date, add them to the new group starting from the new pay date, and make sure year-to-date cumulative figures (gross, tax, NI) transfer correctly. No gap, no overlap. Your software should handle the data transfer, but verify it. If cumulative figures don't move across correctly, the new group will recalculate tax from day one of the new period, which will either over-deduct or under-deduct for the rest of the year.

Common pitfalls to avoid

Missing weekly filing deadlines: Weekly payroll means weekly filing obligations. If you're used to monthly payroll, it's easy to miss the weekly rhythm. Set up automated submissions to avoid this.

Incorrect period calculations: A four-weekly payroll has 13 periods, not 12. Using 12 periods will result in incorrect tax calculations and under/overpayment throughout the year.

Inconsistent data collection: Weekly payroll requires weekly timesheet data. If your managers are used to submitting data monthly, they need to adjust their schedule to meet the weekly processing deadline. Use time recording tools to make this automatic.

Not reconciling across frequencies: It's tempting to treat each pay group independently, but your tax liability is combined. Reconcile all groups together each month.

Frequently Asked Questions

Q: Can I pay the same employee in two different pay groups? A: No. An employee belongs to one pay group with one pay frequency. If you need to pay someone at different frequencies (say, salary monthly plus a bonus weekly), the bonus still goes through their main pay group when that group is processed. Don't create two separate payroll runs for one person.

Q: What if I miss a filing deadline for one pay group? A: HMRC treats each filing independently. A missed deadline for the weekly group incurs a penalty even if the monthly group was on time. This is why automation is worth the investment — one piece of forgotten manual work can cost you.

Q: Does four-weekly payroll really have 13 periods instead of 12? A: Yes. 4 weeks × 13 = 52 weeks. Your software will handle this, but if you ever calculate things manually or check year-end numbers, remember it's 13 periods. Using 12 will throw your tax calculations out by roughly 8%.

Q: Do I need to file with HMRC 52 times a year if I have weekly payroll? A: Yes, but your software does it automatically. You don't manually file anything — that's the whole point of RTI automation.

Q: Can my pension provider insist on monthly submissions even though I have weekly pay? A: Some do. Check their requirements when you set up auto-enrolment. If they only accept monthly, you'd typically submit weekly contributions monthly, which they then allocate backward to the correct weeks.

Q: What if an employee moves between pay groups mid-year? A: Your year-to-date figures (gross, tax, NI) must transfer when they move. Your payroll software should handle this, but verify the transfer before processing the first payroll in the new group. An error here will cause incorrect tax calculations for the rest of the year.

Q: Is there a maximum number of pay frequencies I can use? A: Technically no, but practically yes. Most businesses use two or three (weekly and monthly, or weekly, fortnightly, and monthly). If you're thinking of five or more, you've probably got a process problem that's been solved by adding complexity rather than fixing the root cause.

The bottom line

Multiple pay frequencies add admin work, but that work is finite and, with the right tools, highly automated. Set up your pay groups clearly, put deadlines in a shared calendar, use payroll software that handles multiple schedules natively, and reconcile monthly.

The alternative — forcing all employees onto a single pay frequency — often doesn't work. You'll either frustrate staff, break contracts, or find it impossible to hire and keep people in roles where the industry norm is different.

Choose the frequencies that match your workforce. Build the systems to manage them efficiently. Then get on with running your business.