What should IT check before you buy an HR and payroll system?

Matthew Woolley
By Matthew Woolley
Illustration of an HRIS demo with a checklist of questions to ask a vendor.

Review six things before you sign off. Where the data is stored and who can reach it. How people sign in. What independent security evidence the vendor can show you. How the system connects to finance and your other systems. Who can see pay and personal records. And how you get all your data out if you leave.

As of Nov 14, 2026 · 8 min read

That list comes first because HR has usually picked the shortlist on features by the time IT is asked. Features are HR's call. Your call is whether the system can hold your employees' pay, banking details and personal records safely, and whether you can leave without a fight.

Get written answers, not sales-call answers. A vendor who can't put one of these in writing has given you an answer anyway. The sign-off worksheet near the end lists each item so you can record the answer and who confirmed it.

HR will usually be running the demo in parallel, so pair this list with the HRIS demo questions and the wider guide to choosing HR software.

Where is the data stored?

Ask for the hosting region by name, not "Canada" in general. Ask which cloud provider it runs on, which data centres hold your live data, and where the backups go. Backups are where "Canadian data" claims most often quietly fall apart.

Then ask who else touches it. Support staff, subcontractors and reporting tools can all sit outside the region the sales deck talked about.

Why this matters legally is worth a short, careful note. The federal privacy law, the Personal Information Protection and Electronic Documents Act (PIPEDA), covers private-sector organizations handling personal information in the course of commercial activity. Alberta, British Columbia and Quebec have their own private-sector laws, and PIPEDA still applies where information crosses provincial or national borders (Office of the Privacy Commissioner of Canada). Which law applies to a municipality, a First Nation or a non-profit depends on your sector and province, so confirm it with your privacy officer or counsel. This is not legal advice.

One principle in PIPEDA's schedule is the same in practice for most employers. If you send personal information to an outside processor, you stay answerable for it, and you are expected to use contracts or other means to keep protection comparable (PIPEDA, Schedule 1, clause 4.1.3). A vendor is a processor. So the contract is your control, and IT should read it.

Employers also have a records duty that bears on hosting. The Canada Revenue Agency (CRA) says you must keep records at your place of business or residence in Canada unless it gives written permission to keep them elsewhere, and records kept outside Canada but accessed from Canada are not considered kept in Canada (CRA, where to keep your records). Ask your finance and legal teams how that applies to payroll records before you accept a hosting answer.

How do people sign in (single sign-on and multi-factor authentication)?

Single sign-on (SSO) lets people use the login they already have, through your identity provider such as Microsoft Entra ID (formerly Azure AD), Okta or OneLogin. Multi-factor authentication (MFA) asks for a second proof, such as an app prompt, on top of the password.

Here's where I'd press. Ask which SSO standard the vendor supports. SAML 2.0 is the common one. Ask whether SSO is included or a paid extra, and whether it covers the mobile app as well as the browser.

Then ask about MFA separately, because the answer is often "it depends." Some vendors build MFA into their own login. Others rely on your identity provider to enforce it once SSO is on. Either can be fine, but you need to know which one you're buying, because it decides who owns the policy.

Also ask what happens to a departed employee. Can HR deactivate the account in one place, and does that cut off the mobile app too? Offboarding is where HR systems and IT directories drift apart.

What security evidence should you ask for?

Ask for evidence, not adjectives. "Bank-grade security" is an adjective.

The useful request is an independent report. A SOC 2 report (SOC stands for System and Organization Controls) comes from a certified public accountant's examination of a service provider's controls relevant to security, availability, processing integrity, confidentiality or privacy (AICPA). Ask who the report covers, which period, and whether you can read it under a non-disclosure agreement.

Read the scope line first. A vendor that runs on a big cloud provider can truthfully say the cloud provider holds SOC 2 reports. That covers the cloud provider's data centres and infrastructure. It doesn't cover the vendor's own application, its login, its staff access or how it ships code. Ask the vendor for its own evidence for those layers, or an honest statement that it has none yet.

Beyond the report, I'd ask for six things in writing.

  • Encryption at rest and in transit, with the versions named.
  • The date and scope of the last independent penetration test, and whether you can run your own.
  • Audit logging. What gets recorded on a change to a pay record, and for how long.
  • Backup and recovery. How often, where stored, and the recovery target.
  • How staff reach production systems, and whether that access uses MFA.
  • A breach process. How fast you'd be told, and by whom.

On that last item, PIPEDA has its own breach-reporting duties for organizations it covers. Have counsel confirm yours, and make sure the vendor's contract lets you meet them.

How does it connect to finance and other systems?

This is where marketing language does the most damage, so be literal. Ask for a list of every connection, and for each one ask whether it is a live connection between systems or a file you export and import.

Neither answer is automatically wrong. File-based connections are simple to audit, and finance often prefers to review a journal file before it posts. Live connections save steps and add more things that can break or be misconfigured. What matters is that you know which you're getting before the project plan assumes the other.

Check the specifics that cost real time later. How does pay data reach the general ledger? How do time clocks or badge readers feed hours in? Who handles benefits carrier files? Does the directory sync users, or does someone create accounts by hand? If a connection needs a developer interface (an API, short for application programming interface), ask whether it exists today, what it covers and whether it costs extra. "On the roadmap" is a real answer. Treat it as a no.

Who can see pay and personal data?

Pay, banking details, social insurance numbers and medical or leave notes are about the most sensitive records you hold. PIPEDA's safeguards principle says more sensitive information should get a higher level of protection (PIPEDA, Schedule 1, clause 4.7.2).

So check the permission model against your real org chart. Can you separate HR administrators from payroll administrators? Can a manager see their own team and nothing else? Can you restrict a single sensitive field, such as banking details, without locking a whole screen? Who at the vendor can see your records, and is that access logged?

Ask for a demonstration with your own roles, not the vendor's default admin, and have a manager role and an employee role sign in so you can see what each can open. Record which permissions are configured by default and which your team has to set. Most permission problems appear the first time someone who isn't a full administrator logs in.

How do you get your data out if you leave?

Ask this before you sign, while the contract is still open. Can you export everything, in an open format such as CSV or Excel, and does it cost anything? Does the export include history (past pay runs, year-end slips, audit logs, documents) or only current records? How long does the vendor keep your data after you leave, and how does it prove deletion?

Also ask about retention inside the system. If your policy says delete certain records after a set period, find out whether the system can do that automatically or whether someone has to do it by hand. Don't assume.

Mobile and device questions

Employees will use their own phones, and managers will approve things from them. So check the mobile app the way you'd check any app on your devices.

Does it run on iOS and Android, and does it support your mobile device management policy? Does it sign in through your SSO? What data does it keep on the phone? If it clocks people in, does it use location, and is that on by default or a setting you control? Who can switch it off, and what happens to access when a phone is lost?

IT checklist before sign-off

Use this worksheet in the vendor meeting. Record the written answer, the date and who confirmed it beside each row.

IT sign-off worksheet for an HR and payroll system
AreaWhat to get in writing
HostingHosting region, data centres and backup location named in writing.
ContractContract covers processor duties, breach notice timing and what happens to data at exit.
Sign-inSSO standard supported, and SSO covers browser and mobile.
MFA ownershipClear whether MFA is the vendor's login or your identity provider.
OffboardingAccount deactivation cuts off web and mobile access.
Independent reportReport seen under a non-disclosure agreement, with scope and period read, not only the cover letter.
Penetration testDate and scope of the last test provided.
Audit logLog covers changes to pay and personal records.
ConnectionsEvery connection listed as live or file-based, and what exists today versus later.
PermissionsRoles checked against your real org chart, including field-level restrictions.
ExitFull export in an open format, cost stated, history included.
MobileMobile app checked against your device policy.

What I'd say about Workzoom

I work at Workzoom, so weigh this section accordingly. I'd rather keep it short than put anything here our security team hasn't confirmed to you in writing. Integrations today are file-based. Accounting systems take a general ledger journal file, and reporting tools take an Excel export. We publish pricing at $4 per employee per month per suite. Implementation, data migration, configuration and training are included. There is no free trial, so IT gets a walkthrough on the real platform instead. Payroll runs in Canada, the United States and the Bahamas. Details are on the Payroll page.

If your IT team wants to run this checklist against us, book a walkthrough and bring the list. If we can't back an answer in writing, we'll say so.

How useful was this page?

Questions about IT checks for HR and payroll software

Ask for the hosting region by name, the cloud provider, which data centres hold live data and where backups go. Then ask who else touches the data, since support staff, subcontractors and reporting tools can sit outside the region the sales deck described.
Only for the layers the cloud provider runs. A vendor can truthfully say its host holds SOC 2 reports and still have nothing independent behind how its own product is built, who on its staff can log in, or how changes reach production. Treat the host's report as one input, and ask what stands behind the rest.
Single sign-on lets people use the login they already have through your identity provider. Multi-factor authentication adds a second proof, such as an app prompt, on top of the password. Some vendors build MFA into their own login and others rely on your identity provider, so confirm which you are buying.
Whether you can export everything in an open format such as CSV or Excel, whether it costs anything, whether the export includes history such as past pay runs, year-end slips, audit logs and documents, and how long the vendor keeps your data and proves deletion.

Our clients

The teams that run their people on Workzoom.

See customer stories

Workzoom handles HR, payroll, workforce, and talent on one employee record. Book a Walkthrough.

Matthew Woolley
Matthew Woolley
Account Executive
Matthew leads marketing and sales operations at Workzoom, where he works with employers across Canada, the US, and the Caribbean on HR, payroll, and workforce management. He writes about the systems and strategies that help mid-market organizations choose and run their HR systems.

Get started

Built around your org. See it run live.

Explore your suite options, pricing and fit in a 15 to 60 minute working session. For organizations with 50 or more employees. See our minimums.

Loading available times.

01 / 01

Better work, in your inbox.

Fresh ideas for HR and payroll. Every week.

Better work, in your inbox.

Practical ideas for HR, payroll and workforce teams.