HR wants fewer systems and a better flow of data

Why payroll preparation does not fail because of too few tools, but because of too little alignment between planning, registration, business rules and the payroll service provider.

HR has massively digitalized in recent years. Time registration systems, HR platforms, planning tools, apps, payroll portals, reporting tools, and exports to social secretariats have emerged. On paper, that seems like progress. In practice, many HR teams see something different: more screens, more files, more checks, and more discussions at the end of the month.

That is not a technological detail. That is an operational risk. Every manual step between registration and payroll preparation is a place where hours are misinterpreted, mobility goes wrong, allowances appear too late, or exceptions only become visible when payroll is already under time pressure.

“Payroll preparation rarely fails due to one bad system. It fails because planning, registration, rules, and payroll output do not work as one data stream.”

The market is therefore moving away from isolated tools towards stronger alignment, governance and data flows across systems. In its HR Trends 2026, SD Worx identifies strategic HR and fluid HR as key trends. HR needs to move faster, while also working more transparently and reliably. That will not happen by adding more Excel files between systems. It will only happen when rules, controls and data flows are organised centrally.

Where HR is losing grip today

Situation	What is going wrong	What VIRO changes
Loose exports	HR compares files instead of managing discrepancies.	Registrations are automatically processed and validated.
Excel as a control layer	Rules are in formulas, versions, or individual knowledge.	Business rules are applied centrally and made traceable.
Too late discrepancies	Errors only surface at payroll closing.	Discrepancies become visible earlier in the processing flow.
Unclear payroll components	Hours, mobility, and allowances require interpretation.	Raw data is converted into correct payroll components.

The core question for HR: which system does what?

Many organizations try to solve every problem by adding an extra application. A tool for planning. A tool for time tracking. An HR system for employee data. An ERP for projects. A social secretariat for payroll processing. Each system has its role, but the break usually occurs between those systems.

A payroll service provider processes what it receives. A time registration system records what someone enters or clocks. A planning tool shows what was scheduled. But who translates operational reality into correct, explainable and payroll-ready output? Who decides which hours are normal, which premium applies, which mobility rule counts, which exception should be blocked and which code needs to be sent to the payroll service provider?

This is where it often goes wrong today. Not because HR lacks systems, but because no one centrally monitors the processing logic.

HR does not need an extra tool, but a reliable processing layer.

VIRO starts from a different logic. Not: adding yet another separate system. But: creating an intelligent processing layer between planning, registration systems, ERP and the payroll service provider.

That layer does what Excel is often forced to do today: convert raw registrations into correct payroll components, based on collective labour agreement rules, internal business rules and exception logic. Only this happens automatically, reproducibly and in a controlled way.

That is a fundamental difference. Excel can help detect errors, but Excel is not governance. Excel does not remember why a rule was applied in a certain way. Excel does not structurally warn you when a registration conflicts with the planning. Excel depends on the person managing the file. And as soon as that person is absent, payroll preparation becomes vulnerable.

VIRO removes that vulnerability from the process. The rules no longer sit in separate files or in the head of one experienced payroll employee. They are managed centrally, applied consistently and validated across all registrations.

"Excel is not governance. Once payroll logic is in separate files, it becomes dependent on interpretation instead of control."

From time tracking to payroll output: one data stream without duplicate work.

A strong HR data stream does not start with payroll. It starts much earlier: with master data, planning, and registration. Who was scheduled? On which site? In which team? With which role, skill, or contract type? What hours were actually worked? Was there mobility? Are there night hours, overtime, Saturday hours, waiting times, reimbursements, or exceptions?

If that information is spread across separate systems, HR ends up in interpretation mode at the end of the month. Exports are compared, discrepancies are manually checked, and exceptions are clarified via email, Teams, or Excel. This takes time, but mainly margin. Incorrect hours and wrong allowances lead to corrections, discussions, and loss of trust among employees.

VIRO creates a controlled flow from raw data to payroll output. Registrations from mobile apps, time registration systems or planning are collected. The rule engine applies the correct payroll logic. Deviations are made visible for approval. The output is prepared in the format expected by the payroll service provider or payroll system.

From raw registration to payroll-ready output.

Step	What happens?	Why this matters
1. Data collection	Registrations from the app, planning, time tracking, or ERP come together.	Fewer separate files and less copy-pasting.
2. Apply rules	Collective labor agreement rules, internal agreements, mobility, and exceptions are processed automatically.	Fewer errors and less discussion about interpretation.
3. Identify deviations	Incomplete or deviating data becomes visible before export.	HR corrects earlier, not just at payroll closing.
4. Prepare output	Correct payroll codes and payroll-ready files are created.	Faster processing towards the social secretariat.
5. Keep traceable	The logic remains verifiable and reproducible.	More trust from HR, operations, and employees.

Het resultaat is geen extra administratieve laag. Het resultaat is minder dubbel werk. Minder copy-paste. Minder laattijdige verrassingen. Minder afhankelijkheid van individuele interpretatie. En vooral: meer grip op wat uiteindelijk in de loonverwerking terechtkomt.

Why integrations fail when business rules are not central

Many HR integrations are technically built correctly, but operationally designed incorrectly. Data can flow perfectly from system A to system B and still be wrong for payroll. The reason is simple: integration is not the same as interpretation.

An API can pass on a time registration. But an API does not automatically know whether that hour should result in regular hours, overtime, time off in lieu, a night premium, a mobility allowance, a project cost or a combination of these. That translation depends on the collective labour agreement, contract, location, planning, business rules and exceptions.

When those business rules are spread across different systems, discussions arise. Planning works with one logic. HR checks things in another way. Payroll receives codes without the full context. Finance receives post-calculation data that does not always match what actually happened operationally.

That is why business rules need to be centralised. Not as a document on a shared drive, but as working logic inside the data flow. VIRO does exactly that: it turns rules from a reference document into an active processing engine.

“An API moves data. VIRO ensures that this data is also correctly interpreted according to the operational and payroll reality.”

Strategic HR starts with reliable operational data

HR wants to work more strategically. That is justified. But you cannot build strategic HR on data that first needs to be manually corrected. As long as HR loses time every month on checks, corrections, and exceptions, there is too little room for analysis, workforce planning, cost control, and policy.

Reliable operational data changes that role. When HR can quickly see where overtime is building up, where mobility costs are increasing, where teams structurally deviate from planning or where exceptions are piling up, HR becomes a real sparring partner for operations and finance.

That is the bridge between strategic HR and the workplace. Not abstract, not theoretical, but concrete: fewer payroll errors, less payroll stress, better cost allocation, faster closing, and more transparency for employees.

Fluid HR requires systems that adapt.

Fluid HR often sounds like a buzzword, but the operational reality behind it is easy to recognise. Teams change more quickly. People work across multiple locations. Contract types differ. Shifts, teams, absences and last-minute changes make planning more complex. Employees expect clear communication and correct pay, even when their working day deviates from the plan.

That is where traditional HR processes start to struggle. They are often built for stability, not for movement. As soon as reality deviates, workarounds appear. A planner changes something. A team leader notes something separately. HR corrects it afterwards. Payroll receives an exception. Finance later asks why the project cost does not add up.

VIRO helps absorb that movement without breaking the process. The reality of planning and registration is automatically translated into correct payroll preparation. Not by forcing everything into a rigid standard, but by applying rules flexibly and in a controlled way.

The impact: less noise between HR, operations, and payroll.

The biggest gain from VIRO is not just time savings. The biggest gain is calm and predictability. HR sees deviations earlier. Operations faces fewer questions afterwards. Employees have more trust because hours, mobility and premiums are processed correctly. Payroll receives output that has already been validated.

That reduces the pressure at the end of the month. It reduces discussions about hours and allowances. It prevents errors from only becoming visible when corrections are costly and sensitive. And it makes the entire flow from planning to payroll and post-calculation more reliable.

For companies with complex working time arrangements, mobile employees, multiple sites, shifts, collective labour agreement logic or many exceptions, this is not a luxury. It is margin protection.

Business impact of a central processing layer.

Pain point without VIRO.	Operational consequence.	Impact with VIRO.
Manual corrections.	HR loses time on checks and recalculations.	Faster closing and less payroll stress.
Discussions about hours and mobility.	Employees lose trust in the processing.	More transparency and less dispute.
Scattered exceptions.	Planning, HR, and payroll work with different interpretations.	One central logic for the same reality.
Late errors.	Corrections become expensive, sensitive, and difficult to explain.	Deviations are detected earlier.
Invisible margin leaks.	Project costs, surcharges, and mobility become clear too late.	Better cost allocation and more predictability.

VIRO as the engine between systems.

VIRO does not necessarily replace your HR system, planning tool, ERP or payroll service provider. VIRO makes sure those systems work better together. It takes raw registrations, applies the right rules, validates deviations and delivers payroll-ready output.

Thus, VIRO becomes the engine between operational reality and payroll processing. Not visible as an extra administrative burden, but felt in every month-end closing: fewer errors, less stress, less manual work, and more control.

Whoever says today that HR wants fewer systems is right. But the real question is sharper: which layer ensures that the systems that already exist finally work as one reliable data stream?

“The future of HR is not in more screens, but in a processing layer that allows existing systems to work together reliably.”

Conclusion: the future of HR is not in more screens

HR does not need yet another portal that collects data. HR needs a reliable processing layer that connects planning, registration, rules and payroll output.

That is where VIRO makes the difference. It removes the breaking points from the process, makes business rules centrally applicable and ensures HR no longer has to chase after the facts. From time registration to payroll output. From operational reality to correct payroll preparation. Without Excel as an emergency bridge..

Frequently asked questions

What is VIRO?

VIRO is the pre-payroll processing layer of GO-VIRTUAL. The solution automatically converts raw registrations, hours, mobility, allowances, reimbursements, and exceptions into correct payroll-ready output according to collective labor agreement rules and internal company rules.

Does VIRO replace the social secretariat?

No. VIRO is not a social secretariat and not a payroll package. VIRO ensures that the data sent to the social secretariat is already validated, correctly coded, and ready for processing.

Why is Excel risky in payroll preparation?

Excel makes payroll preparation dependent on manual checks, individual knowledge, and separate files. This increases the risk of errors, late corrections, discussions with employees, and unpredictable month-end closures.

Which systems can VIRO connect?

VIRO can process data from planning, mobile registration, time registration, ERP, and HR systems, and provide output to social secretariats or payroll systems.

For which companies is VIRO relevant?

VIRO is particularly relevant for organizations with complex working hours, shifts, mobility, collective labor agreement rules, multiple locations, project work, or many exceptions in payroll preparation.