If "Can we fix that quickly?" is a normal sentence for you, then your pre-payroll is not running on a process. It's running on people who have to correct it every month.
And that's exactly why it consumes so much energy. Not because the payroll run is difficult. The social secretariat handles that.
The misery is almost always beforehand: in what you still need to collect, check, correct, and make "correct".
Monday, 4:48 PM.
Sofie (HR/payroll) is already in closing mode. Not because she enjoys it, but because it has to be done. The input to the social secretariat needs to go out. Preferably today.
Then a message pings in from planning. "Uh… that team from Friday. Someone has been swapped. And Jan was on standby.Can we fix that quickly?"
Sofie sighs. Not dramatically. Just… professionally tired. She opens the file that officially isn't called "the file", but everyone calls it that. An Excel with tabs like "DEF", "NEW2", "corrections_jan" and somewhere a column that is only understood by those who built it.
She knows what's coming next. Always the same ritual.
- first compare hours with registrations
- then reconstruct allowances ("was it that shift or the other one?")
- then check mobility ("which site, which distance, which agreement, who was the driver, who was the passenger?")
- then: "okay, just export it… hoping for the best"
And meanwhile the clock is ticking. Not because the payroll run is difficult. That payroll run usually goes well for the social secretariat.
The stress arises in the step before. Pre-payroll.
Honestly: this is not payroll. This is damage control.
Many organizations call this "payroll". But actually, it is monthly damage control before the payroll run. You can see it from one signal. If "Can we fix that quickly?" is a normal sentence, then your process is not designed to be correct. It is designed to just make it.
Do you recognize this? Do the "Sofie-check"
Read this as a mirror, not as a checklist. Sofie recognizes all of this. Maybe you do too.
- The last week of the month there is always "something else".
- Exceptions (standby, relocations, overtime, allowances) are no longer an exception for you, but routine.
- Corrections are done manually "because otherwise it won't be done on time".
- There is at least one Excel that is critical for the closing.
- Discussions rarely revolve around money, but around evidence: "why did someone get this and someone else did not?"
- Rules partly live in minds: "We do it this way."
- If one key person is absent, the closing suddenly becomes exciting.
- The export to the social secretariat is sometimes: "it will probably be about right, we'll see."
If you often think "yes" here, then you have no calculation problem. You have a flow problem.
What is really going wrong
Pre-payroll is a chain. Registrations, exceptions, interpretation, controls, export.
If controls only happen at the end, you get something everyone knows. Small deviations pile up… until at the end you don't "process", but save what can be saved. That's why month-end closing often feels like firefighting.
Not because HR or payroll is "inefficient". Just because they become too efficient at solving the same misery. Month after month.
How do you break that cycle?
Stop treating pre-payroll like a rescue operation. Make it a process that works without putting out fires.
- All calculation rules are in the system, not in heads.
- Deviations come up on day 3, not on day 28.
- "Why did I get this?" is one click, not a treasure hunt.
- The social secretariat gets input, not question marks.
Then "can we fix this quickly?" dies out. Finally.
From raw registrations to payroll-ready input
VIRO does not run payroll and is not a social secretariat. VIRO is a pre-payroll engine: it automatically converts raw performances (hours, allowances, mobility, reimbursements) into payroll-ready input for the social secretariat, in accordance with collective labor agreements and company rules, with an audit trail.
Or in Sofie language: "Less searching. Less correcting. Less discussion."