Tool Documents

HR and Payroll

HR systems hold the most sensitive personal data most organisations process, about people who cannot decline to be in the database, and they are frequently bought with less scrutiny than a project tool.

Reviewed August 9, 2026. Legal points summarise published provisions; employment and payroll rules are jurisdiction-specific. For a related operational perspective, Monitask also publishes a reference on workforce optimization software.

What makes it different

The data is special. Contracts, salaries, bank details, addresses, sickness records, performance notes, and in some cases health or union information — categories that carry additional protection under data protection law.

The subjects cannot opt out. An employee cannot decline to be in the payroll system, which is why consent is a weak basis in employment and why the balancing exercise matters.

For broader context, see Microsoft 365.

Payroll is jurisdictional. Tax tables, social contributions, statutory filings and reporting formats differ per country and change annually. A product excellent in one jurisdiction may not operate in another at all.

And the retention obligations are statutory, running years past employment, which makes the export question sharper than usual.

What varies structurally

Whether payroll is native or partnered. Many HR platforms hand payroll to a local partner per country, which means a second contract, a second processor and a second export.

Whether it is the system of record. An HR platform that feeds identity, access and payroll is load-bearing infrastructure; one that holds leave requests is not.

Document handling. Contracts and signed documents, and whether they come out with the export or only their filenames.

And access granularity. Who can see salary, who can see performance notes, who can see sickness records — this is a data protection control, not a convenience feature, and it is frequently gated at a higher tier.

What to check in this category specifically

Which jurisdictions are supported for payroll, by name, and who operates each — the vendor or a partner.

Access controls at field level, tested in the trial with a non-admin account.

Retention configuration, and whether it can differ for leavers.

Per-individual retrieval and deletion, because employees exercise data subject rights and the tool must be able to answer.

Document export, with actual files.

And the subprocessor list, read properly. HR platforms integrate background checking, benefits, learning and analytics providers, and each sees a slice of employee data.

The consultation dimension

In several jurisdictions, introducing an HR system with monitoring or evaluation functions requires works council involvement — Germany under §87 BetrVG, the Netherlands under Article 27 WOR, with equivalents elsewhere.

Performance and analytics modules are the trigger, more often than the core record-keeping.

Which is an argument for buying narrowly: a system that holds contracts and leave is a different consultation from one that scores performance, and the second capability frequently arrives as an included module nobody asked for.

The short version