In one sentence: a payroll run isn't slow because of the calculation — your social secretariat handles that. The time goes to collecting and checking every input at month-end. Keep that data continuously up to date and let a payroll agent show you only the exceptions, and a run wraps up in about five minutes.
How can I automate my payroll?
In Belgium, automating payroll doesn't mean taking over the calculation itself. That stays with your social secretariat (Belgium's outsourced payroll processor). What you do automate is all the work around it. In short, it comes down to four steps:
- Gather your HR data in one place and validate it the moment it arrives: hours, leave, sick days, expenses and contract changes.
- Let a payroll agent prepare the input, freeing you from manually chasing it at month-end, cleanly checked against your policy and your social secretariat's codes.
- Approve only the exceptions. Anything that already matches the rules doesn't need a second look.
- Send the validated input straight to your social secretariat and pull payslips and processed timesheets back into your HRIS.
Payroll automation is one concrete form of agentic HR: HR automation where the software takes organisation through to actual execution of the work. The difference with a regular integration is that an integration moves data, while an agent handles the process end-to-end. We cover that shift more broadly in What is Agentic HR?.
Why does a payroll run take so long today?
The payroll calculation isn't your bottleneck. In Belgium, your social secretariat does that heavy lifting as the payroll engine: NSSO (DmfA) declarations, withholding tax, the right joint committee and every extralegal benefit.
The time goes into what comes before it: preparing the input. And today that happens as a batch. For a whole month, changes pile up across emails, Excel sheets and separate tools: hours, leave, sick days, expenses, new contracts, salary changes. Only at month-end do you bring it all together, check it and re-type it toward the secretariat. Every mistake surfaces at once, right at the busiest moment.
That's why payroll errors are so stubborn. US research by EY found that one in five payroll runs contains an error, with an average of fifteen corrections per period (EY, 2022): treat it as an order of magnitude based on US data. The cause is rarely the payroll engine, but that manual hand-off in front of it.
What is exception-based payroll?
The idea comes from finance, where it's called the "continuous close". You validate data at the moment it's created, keeping everything up to date throughout the month. A timesheet coming in is checked immediately, a leave request updates the balance right away, an approved contract change updates the salary scale.
The result is that by the time the payroll run happens, there's nothing left to collect. The data is already up to date and already checked. What remains isn't the whole payroll, but only the exceptions: cases the agent can't handle with confidence on its own. Think of a timesheet that doesn't add up, an expense outside policy or a shift with a duplicate code. Only those land on your screen, with the context you need, ready to approve.
That's the real tipping point. In classic payroll you review everything to find the handful of errors. In exception-based payroll you review only those errors. In time, that's the difference between a day and a few minutes.
What does the payroll agent actually do?
A payroll agent isn't a chatbot that helps you and isn't a dashboard that shows data. It's software that performs the task and pulls you in only for decisions. It runs continuously, without you needing to babysit it.
The agent validates data at the source: every timesheet, leave day, expense and contract change is checked as it comes in, against your policy and your social secretariat's codes. That keeps the payroll input permanently sharp, and leaves nothing to collect at month-end. Exceptions are set aside and only those are surfaced to you, with enough context to decide in seconds. After your approval, the validated input goes to your social secretariat's payroll engine, and the output (payslips, processed timesheets) flows back into your HRIS.
The contrast with a classic integration or API export is clear. Those move data, but the checking and the decisions stay your manual month-end job. The agent takes the process over and leaves only the exceptions on your plate.
The 4 levels of HR software
Most HR tools can't do this, and that's because they sit at a different level. HR software has spent a long time stuck at organising work. Agentic HR executes it. The distinction is augmentation versus execution: augmentation helps you with a task you still do yourself, execution does the task and lets you approve where it matters.
| Level | Name | Payroll at this level |
|---|---|---|
| 1 | Manual | Timesheets in Excel, changes over email, re-typing toward the secretariat |
| 2 | System of Record | One central HRIS, but you still export and hand over yourself |
| 3 | System of Workflow | Approvals run automatically, but the export stays manual at month-end |
| 4 | System of Execution (agentic) | Data continuously validated, only exceptions to approve, run in minutes |
A System of Record (level 2) is a fine archive. A System of Workflow (level 3) automates the clicks around it. But exception-based payroll only becomes possible at level 4, because that's when the software moves from assistance to actually doing the work itself. Most Belgian SMBs sit at level 2 or 3 today.
That shift is broader than HR. Gartner expects 40% of enterprise apps to feature task-specific agents by the end of 2026, up from less than 5% in 2025 (Gartner, 2025). At the same time Gartner warns that over 40% of agentic projects will be cancelled by end of 2027 due to unclear value or weak governance (Gartner, 2025). Reason enough to judge agentic HR on its concrete execution and demonstrated results.
How Peepel approaches it
Peepel is an agentic HR platform for European companies of 50 to 500+ employees, and sits at level 4. You give an instruction in plain language and the platform runs the workflow from start to finish, with approval where policy requires.
For payroll, that looks like this: because Peepel keeps HR data continuously validated and up to date, there's nothing left to gather at run time. The payroll agent surfaces only the exceptions, which is why a run drops from half a day to about five minutes.
Peepel is ISO 27001-certified, GDPR-compliant and hosted in the EU. Peepel is operational within one day. Peepel delivers the payroll input (worked time, absences, contract and pay changes) to your social secretariat. Salary calculation stays with the secretariat.
So it isn't about being better than your current HRIS — it's about operating at a different level. Peepel prepares the payroll input and only asks you to approve the exceptions. Salary calculation stays with your social secretariat.
What level is your HR at?
Walk through the four questions; your first "yes" gives away your level.
Do your timesheets and changes still live mostly in Excel, folders and mailboxes? Then you're at level 1, Manual. Do you have one central HRIS, but still hand payroll off yourself? That's level 2, System of Record. Do approvals run automatically, but you still export manually at month-end? Level 3, System of Workflow. Is your payroll input continuously validated and do you only see the exceptions at run time? Then you're at level 4, System of Execution.
Most SMBs reading this sit at level 2 or 3.
Ready to turn your payroll run from half a day into five minutes?
Want to see how a payroll agent keeps your data continuously in shape and surfaces only the exceptions? Book a demo or explore the payroll module in Peepel.
Further reading: What is Agentic HR?, HR automation: the complete guide, Automating payroll in a small business and What is Dimona? Declaration, deadlines and fines.
