Applicant Tracking System vs HRIS vs Payroll: What Each Does and Where They Hand Off

An applicant tracking system vs HRIS vs payroll comes down to timing: an applicant tracking system manages people before they are hired, an HRIS holds the employee record after they join, and payroll pays them. The handoff happens at the accepted offer, when candidate details become an employee.

Three systems, three different questions

People mix these up because vendors blur the lines and bundle them. The simplest way to separate them is by the question each answers. An applicant tracking system answers: who is applying, who is good, and who should we hire. A human resources information system, usually called an HRIS, answers: who works here, in what role, on what terms, and what is their history with us. Payroll answers: how much do we owe each person this period, what is deducted, and what must we pay to authorities. The first deals with strangers who might join. The second deals with employees. The third deals with money and legal filings. They share a person's name and contact details, but their rules, risks and users differ. A recruiter lives in the first, a people manager in the second, and a finance or payroll specialist in the third. This guide explains each, where they hand off, and how a small business can decide what to buy and in what order. For more on the first category see /applicant-tracking-system and /recruitment-software. We do not state other vendors' features or prices as fact, so check current details before you buy.

What an applicant tracking system does

An applicant tracking system, often shortened to ATS, covers the hiring process up to a signed offer. It collects applications, reads or stores CVs, helps you compare candidates against the job, schedules interviews, gathers structured feedback, records decisions and manages the offer. It also holds the communication with candidates, including those you do not hire. Its data is about candidates, and its retention rules are about how long you may keep information on people who never became staff. It is used heavily during open roles and lightly in between. A good one makes hiring faster and fairer, and keeps a record that explains decisions. It is not designed to manage leave, store contracts for the long term, or run pay. If a tool does everything, ask which part it does best, and whether the rest is thin. Our guide at /blog/ats-vs-crm-for-recruiting-which-do-you-need covers a related confusion, between an ATS and a customer relationship tool used for talent pools.

What an HRIS does

An HRIS is the system of record for employees. Typical contents include personal and contact details, job title, department, manager, start date, contract terms, pay grade, working pattern, leave balances, time off requests, documents such as signed contracts, performance reviews, training records and the history of changes. Some include onboarding checklists, an organisation chart and self-service for staff to update their own details. Because it holds sensitive, long-lived data, it needs strong access control and clear retention rules, which differ by country. Many HRIS products also offer extra modules, such as performance, learning or recruiting, and the depth varies widely, so check what a given product includes now. A small business with five staff can run on a shared spreadsheet and a folder of contracts for a while. The pressure to adopt an HRIS usually comes from leave tracking, compliance paperwork, growth past ten or twenty people, or an audit. An HRIS does not read CVs or compare candidates in depth, and it does not usually calculate net pay and tax by itself.

What payroll does

Payroll turns hours, salary, bonuses and benefits into payments and filings. It calculates gross pay, deductions, employer contributions and net pay, pays staff, produces payslips and reports to tax and social security authorities. These rules are specific to each country and often to each region, change regularly, and carry penalties for errors. For that reason, many small businesses use an accountant or a payroll provider rather than doing it themselves. Payroll needs a precise, trusted record of who is employed, their pay and their bank details, and any mistake becomes a payment error. Some HRIS products include payroll, some connect to a separate provider, and some leave it entirely to you. Whichever you choose, the rule is the same: payroll should receive clean, approved data from the employee record, not retype it from an email. Rules differ by country, so check local law and talk to a qualified adviser about your obligations. Nothing in this guide is tax or legal advice.

Where they hand off

The key handoff is the accepted offer. Before it, you hold candidate data. After it, you hold employee data. At that moment you need to carry across only what is needed: name, contact details, role, start date, agreed pay and any right-to-work or reference confirmations your law requires. Everything else about the candidate, such as the CVs of other applicants and your interview notes, should follow your retention rules and usually should not enter the employee record. A second handoff is from the HRIS to payroll: new starters, changes in pay, leavers and unpaid leave. A third is back to the ATS: the fact that a role is filled, which closes the job and the other candidates. The risk at each handoff is retyping, which creates errors, and over-copying, which spreads sensitive data. Where systems connect, check what data moves and in which direction. Where they do not, define a short checklist and one person responsible. The offer terms feed the next step, and /offer-letter-template gives a starting text.

A decision table

Use this table to match your situation to the system you need first. The thresholds are examples to adapt.

For most small businesses, payroll comes first because it is a legal duty, then a way to hire well, then an employee record. The order can change if hiring is your main problem.

A worked example with example numbers

An example business has 14 staff and plans to hire six people next year. These figures are examples. It pays staff through an accountant, keeps contracts in a shared drive, and tracks leave in a spreadsheet. Hiring is the strain: each role takes about ten hours of the manager's time and CVs sit in an inbox. The owner considers a bundled suite that promises hiring, HR and payroll. Instead she splits the problem. Step one: an applicant tracker for the six hires, to cut the hours and keep a decision record. Step two: a written handoff checklist for the accepted offer, listing the exact details the accountant needs and the documents to file, with one named owner. Step three: review the leave spreadsheet at month nine, and move to an HRIS only if errors continue. Six hires times five saved hours is thirty hours, an example figure that justifies the first step. The suite would have solved all three problems badly and mostly in months she did not need them. Matching the system to the pain, and defining the handoff, gave her most of the value at a fraction of the effort.

Common mistakes

Buying a suite for the one module you need, and paying for the rest. Assuming an ATS can double as an employee record, so candidate notes live on in places they should not. Copying the whole candidate file into the HRIS at hire, including data you have no reason to keep. Retyping pay details from an offer email into payroll, which is how errors start. Keeping rejected candidates forever because there is no deletion setting. Forgetting that leavers need a handoff too, from the HRIS to payroll and to your access list. Ignoring country rules on retention, right-to-work checks and employment records. Choosing on price and discovering that integrations cost extra or do not exist. Not naming an owner for each handoff, so every step relies on someone remembering. Each mistake is cheap to avoid with a written checklist and a clear view of which system holds which data. Rules differ by country, so check local law, and ask your accountant what payroll needs from you.

A handoff checklist you can copy

Write the handoff once and use it for every hire. Before the offer is final: confirm the agreed pay, start date, job title and manager, and have an approver sign off. On acceptance: record the date and what was accepted, and mark the candidate hired so the job can close. Within two days: send the employee record the legal name, contact details, role, start date and pay, and give payroll or your accountant the details they need, such as bank details collected securely, plus any tax forms your country requires. Collect right-to-work or identity documents only as your law requires, and store them in the employee record, not in candidate notes. Close out the other applicants with a message, and set the deletion date for their data. Name one person responsible for each line and tick them off. Rules on checks and records differ by country, so check local law. Finally, keep a one-page map of your systems: what each holds, who can open it, who owns it, and how data moves between them. A map like this takes twenty minutes to draw and saves hours when a new person joins, an auditor asks, or one tool is replaced. Review the map once a year, and whenever you add a tool, because forgotten connections are where records quietly go out of date.

Where Rezumz fits

Rezumz is on the hiring side of the line. It covers the work from opening a role to a signed offer: the job and requirements, an apply page, CVs scored against the job with evidence quoted, interview scheduling and scorecards, a debrief and decision record, an offer letter with approval and a typed-name acceptance, and a hire package. That package is one file with the profile, offer, scores, interview feedback, notes, emails sent and status history, and a webhook subscribed to candidate.hired receives the same data, which is a practical handoff point to other systems. Rezumz does not run payroll or act as a deep HRIS, and it has no direct connection with job sites. It suits small and mid-size hiring teams; Team is for 4 or more recruiters. Prices: a free plan with 2 free candidate analyses, $29 a month, $199 a year, a limited $499 lifetime plan, and Team at $79 a month or $699 a year for up to 10 teammates. See /pricing or /demo.

Who this advice is not for

If you are a large organisation with thousands of staff, several countries and a dedicated HR systems team, you likely need an enterprise suite chosen by a formal process, and this simple ordering does not apply. If you have no employees yet and are hiring your first person, you need a payroll route and an employment contract before any software. If you use a professional employer organisation or an agency that employs people on your behalf, some of these systems are theirs, not yours. And if your hiring volume is very low, a tracker may not pay back at all. Whatever your size, write down the handoff at the accepted offer, name its owner, and check local law on candidate and employee records. The fewer systems you run, the fewer handoffs you have to get right, so add one only when a specific pain justifies it.