Weekly, Fortnightly, Monthly
Pay frequency multiplies everything: the runs, the chasing, the filings, the chances to get it wrong. It is also not entirely yours to choose.
Written downif the person who does this is away
Pay frequency multiplies the whole of payroll. Weekly pay means fifty-two gathering cycles, fifty-two runs and fifty-two chances for something to be wrong, against twelve.
The deadline in “Weekly, Fortnightly, Monthly” becomes more workable when collection and approval happen before the final payroll cut-off. Organisations considering timesheet reminder for timesheet reminder can make that timing visible without assuming that activity data alone explains whether a payroll step is complete.
It is also not purely an administrative choice: it is in contracts, it is what people have arranged their lives around, and in some trades it is simply the expectation.
As a separate reference point for “Weekly, Fortnightly, Monthly”, see ADP payroll resources. Current legal, tax and employment requirements should still be confirmed for the organisation’s location.
What frequency actually multiplies
Not the arithmetic, which is the same. The chasing, the cut-offs, the approvals, the payment runs, the filings and the opportunities for a missed change.
| Frequency | Cycles a year | The particular difficulty |
|---|---|---|
| Weekly | 52 | Four months contain five runs |
| Fortnightly | 26 | Deadlines drift; two months contain three |
| Monthly | 12 | Longest wait when something is wrong |
A weekly payroll of ten people is considerably more work than a monthly payroll of forty.
Why weekly persists
Because it suits the people being paid. For anybody on a lower wage or with irregular hours, weekly pay is the difference between managing and not, and a business that moves them to monthly has made their life harder to make its own easier.
That is a real cost and belongs in the decision.
Why monthly is easier to run
One cycle, one set of deadlines, one filing rhythm, and enough time between runs that a correction can be made calmly.
For salaried staff whose pay rarely changes, there is very little argument for anything else.
Fortnightly, and why it is the worst of both
Twenty-six cycles, deadlines that drift across the month, and two months a year with three pay dates — which catches out the cash forecast of every business that has not planned for it.
It persists mostly by inheritance.
Running two frequencies
Common and workable: weekly for hourly staff, monthly for salaried. It doubles the calendar and halves the confusion, because each group has one consistent arrangement.
The cost is that the person running payroll never gets a clear week.
The month with an extra date
Weekly and fortnightly payrolls produce months with one more run than usual, and the money leaves in a month when the business expected the usual number.
Knowing which months those are, a year ahead, is the whole of managing it.
What is actually in the contract
Pay frequency is usually a contractual term, and changing it is a change to terms rather than an administrative decision.
What that requires — notice, agreement, consultation — differs by jurisdiction and by the contract, and is a question for somebody qualified where you are.
The transition problem
Moving people from weekly to monthly leaves them with a gap: the last weekly payment, then a wait of up to a month.
Businesses that do this without a transitional arrangement cause genuine hardship and considerable resentment, and the saving is never worth it.
What a transition looks like when done properly
Notice well ahead, an explanation of exactly which dates change, and a bridging arrangement for the gap — an advance, a part payment, or a phased move.
That costs money and is the price of making the change at all.
The cash side
Monthly pay holds the money longer and makes the outflow lumpier. Weekly pay smooths the outflow and makes the business's cash position more visible week to week.
Neither is obviously better; it depends on how the business's money comes in.
What to look at before changing anything
Who is actually asking. A frequency change that suits the person running payroll and nobody else is a change made for the convenience of the smallest group affected.
The arrangement most small businesses end up with
Monthly for everybody, weekly retained only where the work is hourly and the people need it.
That is usually right, and the thing that makes it right is the second half of the sentence rather than the first.
Changes to avoid making together
Change frequency and pay date together, change it mid-year, or change it without writing to everybody affected with the specific dates.
What the frequency does to errors
More cycles means more opportunities for an input to be missed, and it also means each error is smaller and found faster. A weekly payroll produces more mistakes and corrects them within days; a monthly one produces fewer and lives with each for a month.
Neither is obviously safer. What matters is that the controls scale: a comparison performed monthly is twenty minutes, and the same discipline weekly is a different proposition entirely.
The ninety-second version for weekly runs
For a weekly payroll the full comparison is not realistic every time. The workable substitute is three figures — headcount, total, and anybody who moved by more than a quarter — checked each week, with the full comparison done monthly.
That combination keeps a control in place without asking somebody to spend twenty minutes fifty-two times.
Two frequencies and one calendar
Where a business runs both, the two sets of dates have to sit on the same calendar or they will collide: a weekly cut-off landing in the monthly keying day, or a bank holiday moving one and not the other.
The collisions are the entire management problem, and they are visible only when both are on one view.
The one fact worth carrying
Frequency is multiplication. Before changing anything else about how payroll runs, it is worth knowing which number everything is being multiplied by.