Payroll runs on time. The reports lodge. Nobody complains.
For most not-for-profit leaders, that is the extent of the visibility they have over payroll, and it feels like enough.
But a clean pay run tells you the system did what it was told. It does not tell you whether payroll system configuration reflects the rules that actually apply to your staff.
That distinction is worth understanding, because it decides whether a small setup error stays small.
A system applies the rules it was given, every time
Payroll and timekeeping systems are rule-followers. Someone configures the pay items, the award interpretation, the overtime thresholds and the leave accruals, and the system applies those settings to every pay run afterwards.
It does not second-guess them.
If a rule was entered correctly, the system will reproduce that correctness reliably for years. That is the value of automation.
If a rule was entered incorrectly, the system reproduces the error just as reliably. Every fortnight. Without an error message.
This is the part that catches organisations out. A configuration mistake does not look like a mistake. It looks like a normal pay run, because the software has no way of knowing what the correct answer should have been.
So the absence of problems is not evidence of a correct setup. It may only be evidence that nobody has checked.
Why the error compounds rather than surfaces
A manual error usually announces itself. Someone keys the wrong figure, an employee queries their pay, and the issue is fixed in that period.
A configuration error behaves differently, because it is systematic. The same rule applies to the same group of staff every time they are paid.
As a result, the exposure grows with each pay cycle rather than staying contained. By the time someone asks the question, the period under review may cover many pay runs and several employees.
The cost of finding it late is not just the underlying amount. It is the reconstruction work, the conversations with staff, and the board reporting that follows.
Where payroll system configuration commonly goes unexamined
Configuration is usually done once, often at implementation, sometimes by a previous provider or a staff member who has since moved on.
After that, it tends to be inherited rather than reviewed.
When Hopscotch took over a client’s payroll function, it identified that overtime may not have been configured correctly in the client’s timekeeping or payroll system. That is one specific engagement, not a typical finding, but it illustrates the pattern: the issue sat in the setup, not in the processing.
Overtime is a common place for this to happen, because the calculation depends on inputs the system has to be told about.
When overtime starts. A system needs to know the threshold that applies to the relevant staff, and thresholds can differ between roles, agreements and arrangements.
How hours are grouped. Daily, weekly and averaging arrangements produce different results from the same raw timesheet data.
Which rate applies. Rates can vary by day, time of day and the applicable industrial instrument.
How the timekeeping system talks to payroll. Hours may be exported, rounded or categorised on the way through, and the payroll system applies its own rules to whatever it receives.
Any one of those can be set up in a way that looks reasonable and still produces the wrong figure.
The setup question sits underneath the processing question
There is a difference between asking “was this pay run processed correctly?” and asking “is the underlying setup correct?”.
The first question compares the output to the configuration. The second compares the configuration to the obligations that apply to your organisation.
Both matter, but only the second one catches a systematic error.
Hopscotch has found situations where previous providers may have processed information without sufficiently questioning whether the underlying setup or calculations were correct. Processing accurately against an incorrect rule still produces an incorrect result.
That is not a criticism of anyone’s diligence. It reflects how payroll work is usually scoped: the job is to run the pay, and the setup is treated as settled.
For a not-for-profit leader, the practical implication is simple. Someone needs to own the setup question, and it should be explicit rather than assumed.
What not-for-profit leaders should check
You do not need to become a payroll expert to ask useful questions. You need to know which questions reveal whether anyone has looked.
Start with the people involved.
Who configured the payroll system, and when? If the answer is “it came across with the last provider” or “the previous finance manager set it up”, the setup has not been independently examined.
Who is responsible for the setup now? Processing and configuration are different responsibilities, and they are often assumed to sit with whoever runs the pay.
When was the configuration last reviewed against the applicable award or agreement? A review that happened at implementation may predate changes in staffing, roles or arrangements.
Then look at the mechanics.
How do hours move from the timekeeping system into payroll? Ask what happens to the data in transit: rounding, rules applied at each end, and which system is treated as the source of truth.
Has anyone tested a calculation by hand? Taking one employee, one pay period, and working the figures manually is a blunt check, and it is often the fastest way to confirm the system is doing what you think.
What happens when an employee’s circumstances change? New roles, changed hours and different classifications may need configuration changes rather than just a data entry change.
Warning signs worth following up
Some signals suggest the setup deserves attention sooner rather than later.
- payroll queries from staff that get resolved individually but keep recurring
- a payroll system inherited at handover with no documentation of how it was configured
- manual adjustments made each period to make the output look right
- staff working patterns that have changed without a corresponding review of pay rules
- nobody in the organisation able to explain how a particular rate is calculated.
None of these prove an error exists. Each one means the answer is currently unknown, which is a different position from knowing the setup is sound.
How a review actually works
Reviewing payroll system configuration is detailed work, and it is mostly about comparison rather than discovery.
Establish what the rules should be. This means the applicable industrial instrument, employment arrangements and organisational policies, confirmed rather than assumed.
Map what the system is currently doing. Pay items, categories, thresholds, rates and the integration between timekeeping and payroll are documented as they are, not as they were intended to be.
Compare the two and test the gaps. Where the configuration and the rules do not obviously line up, calculations are worked through against real pay data.
Decide what action is required. Some findings are configuration fixes. Others may need specialist industrial relations or legal input before anything is changed.
That last step matters. Payroll obligations can depend on individual circumstances, and the right response to a finding is not always obvious from the accounting side alone.
Where technology helps with the checking
Reviewing a year of timesheet data by hand is slow, which is one reason these reviews get deferred.
Hopscotch has used AI to review exported timesheet data and flag potential payroll issues that would otherwise have required a significant manual review. It has also used AI to process financial reports and rapidly prepare calculations such as accrued wages, reducing manual spreadsheet work.
The tool narrows where to look. People still verify the findings and decide what action is required.
Hopscotch works across platforms including Deputy, Tanda and Employment Hero. The quality of the output still depends heavily on how each system has been configured, which is the same point in a different form: better software does not remove the need to check the rules it was given.
What this means for your board
Boards generally want to know that payroll obligations are being met, and they are usually shown outputs: costs, reports lodged, no outstanding issues.
Outputs answer the processing question. They do not answer the setup question.
A short, honest position on configuration is more useful to a board than a clean report with nothing behind it. When was the setup last reviewed, by whom, and what did they look at.
If the answer is that it has never been reviewed, that is worth recording as a known gap rather than leaving it unstated. It also helps to be clear about where responsibility for payroll decisions sits, which is a separate question from who processes the pay and one that matters when committee members and volunteers are involved in payroll.
For organisations with limited internal finance capacity, that clarity is often the most practical form of risk management available.
Where to get specialist input
Accounting and payroll expertise can tell you what your system is doing and whether the numbers reconcile.
Determining what an award or enterprise agreement requires in a particular situation can be a different question, and complex cases may need specialist industrial relations or legal advice.
The Fair Work Ombudsman publishes general guidance on pay, awards and employment conditions at fairwork.gov.au, which is a reasonable starting point for understanding what applies before you commission any change.
Where a potential underpayment or overpayment is identified, obtaining advice before acting is generally sensible, because the appropriate remedy depends on the circumstances.
Frequently asked questions about payroll system configuration
Generally, after any material change: a new award or agreement, a change in staffing arrangements, a system migration, or a change of payroll provider. A periodic review is also sensible even when nothing obvious has changed.
No. A clean pay run shows the system applied its configuration without error. If the configuration itself is wrong, the output will be consistently wrong and still look normal.
Generally, the employer. Responsibility may be delegated to internal staff or an external provider, but the obligation to pay correctly sits with the organisation, so the arrangement should be documented.
Possibly, in part. Many systems include award interpretation features, but they still rely on being set up with the correct classifications, thresholds and rates for your staff.
Stop and establish the facts before changing anything. Confirm what the rules require, quantify the effect across affected pay periods, and seek specialist industrial relations or legal advice where the position is unclear.
Not automatically. A new provider generally inherits the existing setup, so the configuration needs to be examined deliberately as part of the transition rather than assumed to be sound.
Sometimes, depending on scope. Processing payroll and reviewing whether the underlying setup is correct are different pieces of work, so it is worth confirming which one your current arrangement covers.
Payroll you do not have to take on trust
The goal is not a perfect payroll system. It is knowing, with reasonable confidence, that the rules your system applies are the rules that should apply.
That confidence comes from someone having looked, recently, and being able to explain what they checked.
Hopscotch Accounting works with not-for-profit organisations across Australia on the financial operations that run in the background, including bookkeeping and payroll, reporting and the systems underneath them. Our role is to ask the questions about setup that automated processing does not ask itself, and to tell you plainly what we find.
If you have inherited a payroll system and nobody in the organisation can say when its configuration was last examined, that is a reasonable place for us to begin. Start a conversation.
Liability limited by a Scheme approved under Professional Standards Legislation.
