Weekly, fortnightly and monthly runs for one client

How a payroll bureau handles a client that pays some staff weekly or fortnightly and others monthly: run frequencies, input cut-offs and approvals.

By Achekam · 11 October 2026 · 4 min read · For Accountants & audit firms in South Africa, Nigeria, Kenya

A restaurant group pays its kitchen and floor staff every Friday, its supervisors every second week and its managers and office staff at month end. A building contractor does much the same with site labour and its office. For the client this is normal. For the bureau it means one employer with several payrolls running at different speeds, each with its own inputs, its own approvals and its own payday.

Mixed frequencies are where bureau routines tend to break. A monthly rhythm gets applied to a weekly payroll, inputs for Friday arrive on Monday, or the month-end declaration is prepared while a weekly run is still sitting unapproved. This article sets out how to keep the different cycles apart without losing sight of the employer as a whole.

Why clients mix frequencies

Clients rarely mix frequencies by accident. Weekly pay suits staff paid by the hour or the shift, whose hours change every week and who often cannot wait a month for wages. Fortnightly pay is a compromise some employers reach with supervisors or seasonal staff. Monthly pay suits salaried staff whose pay is the same each month apart from occasional extras.

Hourly and weekly-paid workers are also often the ones paid closest to a legal minimum. For South African clients, the Department of Employment and Labour's national minimum wage flyer sets out the hourly minimum from 1 March 2026 with daily, weekly and monthly worked examples, which makes it a useful check when converting an hourly rate into a weekly wage. Nigerian and Kenyan clients have their own minimum wage rules, and the bureau should hold the client's confirmation of which applies.

Understanding why a client pays each group the way it does helps the bureau design the right routine for each group, rather than forcing everything into one monthly calendar.

Choosing the frequency for each run

In Achekam, pay runs can be monthly, fortnightly or weekly. Each client is set up as an employer under South African, Nigerian or Kenyan rules, chosen when the employer is created, and the frequency is then a choice made for each run.

For a South African employer, each run works out gross pay, PAYE, UIF and SDL per employee, whatever its frequency, and can be recalculated as often as needed until it is approved.

Before the client's first live period, run one cycle of each frequency in parallel with the client's old payroll, and check two things for each: that every run contains exactly the people it should, and that nobody appears in two runs for the same days. Mixed-frequency payrolls fail most often at the edges, when someone is promoted from weekly to monthly pay and is briefly in both groups or in neither.

Inputs for every period

Each period has its own variable inputs: overtime, commission, allowances, reimbursements and unpaid leave. A weekly run needs a weekly set of inputs, and a client used to sending one spreadsheet at month end will not produce them unprompted.

Agree a separate cut-off for each frequency and put them in writing:

Fill in the actual days with the client. The point of the table is that each group has its own row, its own deadline and its own owner at the client. How to collect those inputs reliably is the subject of collecting variable pay inputs from clients.

Approval for every run

Every run, weekly or monthly, is approved by someone other than the person who prepared it. Nobody can approve a run that pays themselves, and an approved run is never recalculated.

A monthly client needs an approver once a month. A weekly client needs one every week, including the week the usual approver is on leave. Before taking on a weekly payroll, check the bureau's own staffing: at least two people who can prepare and approve for that client, with cover arranged for holidays. A weekly payroll that cannot be approved on Thursday is a late payday on Friday.

Inputs freeze when each run is approved

On approval, a run's variable inputs are frozen. For a monthly payroll that rarely causes trouble. For a weekly one it happens every week, and late information is routine: a supervisor sends in Saturday's overtime after Thursday's approval, or a timesheet turns up a day late.

The bureau needs a standing rule for this, agreed with the client: anything that arrives after a run is approved goes into the next run of the same frequency, never into a reopened one. Tell the client's supervisors, so they know that late overtime is paid a week late, not lost.

Keeping the month together

Each frequency runs on its own calendar, but statutory declarations do not. For South African employers, Achekam prepares the monthly EMP201 figures and PDF from approved runs, and a person files them on SARS eFiling and records the reference. A weekly run left unapproved at month end will therefore be missing from the month's figures.

Make the month-end checklist for a mixed client start with one question: are all of this month's weekly and fortnightly runs approved? Only then prepare the monthly declaration. Nigerian and Kenyan schedules are likewise prepared from approved runs, so the same check applies.

For how separate clients sit side by side in one firm, each with its own settings, see running clients' payroll as separate employers.

Draw the client's year on one page before the first run: every weekly, fortnightly and monthly payday, every input cut-off and every approval day. Gaps in cover and clashes with public holidays show up on paper long before they show up as late wages.

General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.