Payroll in most not-for-profits runs on an honest assumption: that someone else has already checked it. A coordinator approves the timesheets because they know who worked the late shift, and the system calculates the pay it has been configured to calculate. A provider or bookkeeper processes the run, lodges the report and files the records, and the board sees a single line in the monthly report. Everyone in that chain is doing their job, and between them nobody is testing whether the rules underneath the calculation are right. Payroll oversight is the name for the job that nobody has been given.
Where the gap in payroll oversight sits
The gap sits in the handover between the steps, which is why no single person sees it. Each step is reviewed on its own terms, and the terms are different in every case.
A manager approving a timesheet is checking whether those hours were worked. They are not checking whether the overtime rate attached to those hours matches the award, or whether an allowance has been coded to the right pay item. They usually don’t have the information to do that, and it was never part of what they were asked to approve.
So the approval travels down the chain carrying a quality assurance it never claimed to give. The next person reasonably treats it as settled.
Each part of the payroll chain checks something different
The payroll system calculates exactly what it has been configured to calculate. If an overtime rule was set up three years ago and the setup was slightly wrong, the system applies that rule faithfully every fortnight without complaint. Software does not flag a rule it was told to follow.
The person processing the run works with what the system produces. If the gross figures look similar to last fortnight and the bank file balances, the run is finished. Processing accurately and questioning the setup underneath are two separate pieces of work, and a provider does the second one only when it is in scope.
By the time payroll reaches the board, it is a single figure compared to budget or to the same month last year. However, a rule applied consistently and incorrectly since it was set up produces a line that looks perfectly stable. Consistency hides configuration errors instead of revealing them.
The useful question for a board, then, is whether anyone in the chain has been given the job of asking whether the rule itself is correct.
Why payroll oversight matters to a not-for-profit board
The obligations attached to payroll sit with the organisation as the employer, and they do not move because a system or a provider did the work. If a rate has been applied incorrectly, responsibility for putting it right normally sits with the organisation, however the error arose.
There is a reporting dimension too. Single Touch Payroll sends payroll information to the ATO with each pay run instead of once a year, so an error in the underlying setup is reported again and again before anyone has a reason to look at it.
Superannuation now moves on a similar rhythm. Payday Super commenced on 1 July 2026, and employers generally pay super at the same time as salary and wages. Contributions are generally required to reach the employee’s fund within seven business days of payday, subject to the relevant rules and exceptions.
Then there is the funding side, which not-for-profit leaders feel more sharply than most employers. Salary costs are acquitted against grants, so if wage costs have been understated across a funded program, the acquittal built on those figures carries the same error forward. Correcting it later means revisiting work that has already gone to a funder.
None of this is cause for alarm. The errors we see are usually small, and they are usually old. Small and old is exactly what no part of the current process is built to catch.
What payroll oversight looks like in practice
There is a difference between a provider who processes payroll and one who reviews it. Both can be competent, and only one of them is looking for the thing nobody has asked about.
When we took over a client’s payroll function, we identified that overtime may not have been configured correctly in the client’s timekeeping or payroll system. That was one engagement and we would not present it as a typical result. It does show the shape of the problem, because the pay runs had been processing without incident and the issue sat in the setup.
We work across platforms including Deputy, Tanda and Employment Hero, and the quality of the output still depends heavily on how each system has been configured. A well-regarded system configured loosely produces clean-looking numbers that are wrong the same way every fortnight.
Testing the rule itself
Work one entitlement out independently. Take a specific employee in a specific period, calculate what they should have been paid without looking at the system, then compare the two figures.
If they agree, the rule behind that payment is probably sound. If they disagree, you have something to investigate before it compounds across more staff and more periods.
Ask what has changed since the last review. Awards are updated, roles get reclassified, and pay items created for a one-off situation keep running long afterwards. A review that starts from what has changed will find more than one that starts from a blank page.
Reviewing timesheet data in volume
We have used AI to review exported timesheet data and flag potential payroll issues that would otherwise have required a significant manual review. It is a tool experienced accountants use and verify, so people still check the findings and decide what action is required. Large volumes of timesheet data show patterns that a sample of three payslips never will.
Treat an anomaly as a question. An employee whose pay moves when nothing about their roster changed, an allowance that appears for some staff in a role and not others, a leave balance that behaves oddly: most of these are explainable, and some are the visible edge of a setup problem.
We have found situations where previous providers may have processed information without sufficiently questioning whether the underlying setup or calculations were correct. That is no reflection on anyone’s diligence. Processing and reviewing are different engagements, and if nobody has asked for the second one, it doesn’t happen.
Questions a board can ask about payroll oversight
You do not need payroll expertise to improve payroll oversight. You need a few questions that reveal whether anyone holds the review job, and then you listen for whether the answer describes a process or an assumption. These sit comfortably on a finance or audit committee agenda once a year.
Questions about who owns the review
If the answer is a role, or if two people each think it is the other, you have found the gap. This is a different question from who processes the payroll.
A date is a good answer. “It has been running fine” is not an answer at all, because a stable incorrect rule produces exactly that impression.
This question resolves most of the others, and the scope is written down somewhere you can read.
Questions about what happens when something looks odd
You want to hear that someone investigates it and records what they found. If odd items are corrected silently each fortnight, the cause is still sitting there.
Awards change, and someone needs to own the job of checking whether a change applies to your staff. That person is rarely the one entering timesheets.
Asking before you need the answer is far easier than asking afterwards. The reply tells you whether anyone has thought about correction, records and advice.
A board that asks these and minutes the answers has materially better payroll oversight than one that reviews the monthly total alone.
A payroll oversight review you can run this year
If those questions surface a gap, the fix does not have to be a project. A proportionate review is within reach for most organisations, and it is easiest while the pay runs are routine.
Start with your highest-risk pay items. Overtime, penalty rates, allowances and leave entitlements are where configuration errors concentrate, because each one depends on conditions being read correctly. Ordinary hours at a standard rate rarely go wrong.
Pick a handful of real employees across different roles. Calculate one period for each by hand and compare it with what the system produced. This is the most useful hour you can spend, because it tests the rule and the arithmetic separately.
Check how pay items map through to reporting. A pay item coded to the wrong category will process normally while reporting incorrectly, so the payroll looks fine inside the organisation and the information going to the ATO does not match what happened.
Write down what you checked and what you found. Even a one-page note gives the next review a starting point, and it gives the board evidence that oversight exists. If you are taking over payroll from a previous provider or a departing staff member, that is the natural moment to do this properly, because you will be opening the setup anyway.
Where specialist advice comes in
Payroll obligations can depend on individual circumstances, including the award or agreement that applies to your staff. Where a review raises something specific about entitlements, specialist industrial relations advice may be required, and it is better to ask early than to correct the same thing twice.
For employer obligations such as withholding, reporting and super, the Australian Taxation Office publishes current guidance. That is a more reliable reference point than the way something has always been done in your organisation.
Frequently asked questions about payroll oversight
Once a year as a baseline, plus any time something structural changes: a new award, a new pay item, a new system or a change of provider. Processing happens every fortnight, but reviewing the rules underneath is a separate exercise with its own schedule.
Both, in different ways. Management runs payroll, and the board satisfies itself that review controls exist by asking who holds the job and when it was last done.
Yes. A system applies the rules it was configured with, so an incorrect rule produces a successful run with the wrong result every time.
Have the calculation checked independently before you correct anything, so you know the size and the period involved. Depending on what is found, specialist advice on entitlements may be required.
Knowing who holds the review job
If you take one action from this, make it the first question: who, by name, is responsible for checking that your payroll rules are correct? Ask it at your next finance meeting and put the answer in the minutes. Much of the risk in payroll sits in the assumption that the answer is obvious, and finding out costs you a conversation.
Hopscotch Accounting supports not-for-profit organisations around the country with the finance work behind the mission, including bookkeeping and payroll. We process pay runs, and we also ask whether the rules underneath them are right, because a successful lodgement only tells you the report was accepted.
If nobody has been given the review job yet, we can help you set one up and show your board what it found. Start a conversation.
Liability limited by a Scheme approved under Professional Standards Legislation.
