Hire to Retire Process: Steps, Owners, Controls

2026-09-25 · Tommaso Maria Ricci

Only 20% of employees worldwide were engaged at work in 2025, according to Gallup's State of the Global Workplace report. Gallup puts the cost of that disengagement at roughly $10 trillion in lost productivity, about 9% of global GDP. Most of that loss is not caused by bad people. It is caused by a hire to retire process that nobody owns end to end, where recruiting, onboarding, payroll, performance and exits are run by different teams on different systems with different definitions of who an employee even is.

Hire to retire, often shortened to H2R, is the name finance and operations people give to the full employee lifecycle seen as one business process. It sits next to order to cash, procure to pay and record to report as one of the core cycles every company runs, whether it names them or not.

The difference is that H2R deals with people, so companies tend to treat it as an HR topic rather than a process. That is exactly why it breaks. Offer letters that do not match payroll setup. Laptops that arrive a week after the start date. Access that stays open for months after someone leaves. Headcount numbers that differ between HR, finance and the org chart.

This guide lays out the hire to retire process the way I map it with operating teams: the stages, who owns each one, the controls that keep it clean, the metrics that show whether it works, and a 90-day plan to fix it without buying a new platform first.

What the hire to retire process actually covers

The hire to retire process covers every event in the relationship between a company and an employee, from the moment a role is approved to the moment the last payment and document after departure are issued. The name is a little misleading. Most employees do not retire from the company that hired them. They resign, get promoted, transfer or are let go. "Hire to exit" would be more precise, but H2R is the term the market uses.

It helps to think of H2R the way you would think of any end-to-end process: a chain of handoffs where each step creates data the next step depends on. Recruiting creates a candidate record. The offer creates compensation data. Onboarding creates the employee record, system access and equipment assignments. Payroll turns that data into money. Every later change, from a raise to a relocation, flows through the same chain. The exit reverses all of it.

Why finance cares as much as HR

People costs are the largest operating expense in most service businesses and one of the largest in any company. Every error in the H2R chain ends up somewhere in the financial statements: a salary booked to the wrong cost center, a bonus accrued twice, a severance payment not provisioned, a contractor who should have been an employee.

That is why the process shows up in audit scopes and why it connects directly to the close. If you already run a structured record to report process, payroll and people accruals are among the entries that break it most often, and the root cause usually sits upstream in H2R.

Hire to retire versus HR operations

HR operations is a department. Hire to retire is a process that crosses at least five departments: the hiring manager's team, HR, IT, finance and legal, sometimes facilities and security as well. The distinction matters because the failures happen in the handoffs between departments, not inside any single one.

The eight stages of hire to retire, with owners

These are the stages I use to map H2R in mid-sized companies. Some organizations merge or split them, but the sequence holds everywhere.

Stage 1: Workforce planning and requisition

What happens: A role is identified, justified against the budget and approved. The output is an approved requisition with a job level, a salary range, a cost center and a start date target.

Owner: The hiring manager proposes, finance approves against the headcount plan, HR validates level and range.

What breaks: Roles opened outside the budget. Salary ranges that do not match the level. Requisitions approved by email with no record, so nobody can later reconcile headcount to plan.

Stage 2: Recruiting and selection

What happens: The role is posted, candidates are sourced, screened, interviewed and assessed. The output is a selected candidate and a documented decision.

Owner: Talent acquisition runs the process, the hiring manager makes the decision.

What breaks: Interview panels with no scoring criteria. Candidate data spread across inboxes. Slow feedback loops that lose good candidates to faster competitors. Many companies are now adding automation here; the options and the risks are covered in the guide to AI for recruitment.

Stage 3: Offer and pre-boarding

What happens: The offer is approved, issued and accepted. Background checks, right-to-work verification and contract signature follow. The output is a signed contract and a complete new hire data set.

Owner: HR owns the offer and the contract, legal owns templates and exceptions, finance approves anything outside the approved range.

What breaks: Offers that promise terms payroll cannot execute. Contract data retyped into the HR system with errors. Missing documents discovered after the start date, when fixing them is awkward and sometimes non-compliant.

Stage 4: Onboarding and provisioning

What happens: The employee record is created, payroll is set up, equipment and system access are provisioned, and the new hire is introduced to the role, the team and the rules. The output is a productive employee with the right access and nothing more.

Owner: HR coordinates, IT provisions, the hiring manager owns the first 90 days of integration.

What breaks: This is the stage most companies get wrong. A Gallup analysis on onboarding found that only 12% of employees strongly agreed their organization did a great job onboarding new employees. The figure is from 2018, but nothing I see in operating companies suggests it has improved much. Day one without a laptop, week two without the right access, month two without a clear objective.

Stage 5: Payroll and compensation

What happens: Hours, salaries, allowances, deductions and benefits are calculated, approved and paid. The output is correct pay, correct withholding and correct accounting entries.

Owner: Payroll, which sits in HR or finance depending on the company, with finance owning the accounting and the controls.

What breaks: Master data changes that arrive after the payroll cutoff. Retroactive adjustments done by hand. Differences between the payroll register and the general ledger that nobody explains. The detailed controls are laid out in the guide to the payroll process.

Stage 6: Time, absence and scheduling

What happens: Working time, leave, sickness and schedules are recorded and approved. The output is clean time data that feeds payroll and capacity planning.

Owner: Line managers approve, HR owns policies, operations owns scheduling.

What breaks: Leave balances that do not match reality. Overtime approved after the fact. Absence patterns nobody reviews until they become a cost problem. Two related guides go deeper: workforce scheduling and employee absence management.

Stage 7: Performance, development and internal mobility

What happens: Objectives are set, performance is reviewed, pay changes and promotions are decided, training is delivered, and people move between roles, teams or locations. The output is a set of documented decisions that flow back into compensation and the org structure.

Owner: Line managers run the conversations, HR owns the calendar and the calibration, finance owns the merit budget.

What breaks: Pay changes approved in a review meeting and never entered in payroll. Transfers that change the manager but not the cost center. Promotions that change the title but not system access.

Stage 8: Offboarding and exit

What happens: Resignation or termination is recorded, final pay is calculated, equipment is returned, access is revoked, knowledge is transferred and legal documents are issued. The output is a closed employee record with no open liabilities and no open access.

Owner: HR coordinates, IT revokes access, finance settles final pay and accruals, the line manager owns handover.

What breaks: Access that stays active for weeks. Final pay that ignores unused leave or commissions. Company equipment that never comes back. Exit interviews that nobody reads.

Hire to retire process steps and owners in one view

Here is the full chain in one table. Use it as the starting map for your own process, then adapt the owners to your structure.

|---|---|---|---|

The single most important column is the one most companies leave blank: the accountable owner of the whole chain. Without one, each department optimizes its own stage and the handoffs rot.

Who should own hire to retire end to end

In a small company the founder or the operations lead owns H2R by default. Somewhere between 50 and 200 employees that stops working, and the process fragments.

There are three workable models.

HR-led. The head of HR or people operations owns the full process, with finance and IT as service providers for their stages. This works when HR has strong operational capacity and systems literacy. It fails when HR is staffed only for employee relations and culture work.

Finance-led. The CFO or controller owns the process as part of the finance operating model, with HR owning policy and people decisions. This is common in companies where payroll sits in finance and headcount cost control is the main driver. It fails when finance treats people events as transactions and ignores experience.

Shared services. A central operations or shared services team owns the transactional backbone of H2R across HR, payroll and finance, while HR business partners own the people side. This is the most scalable model and the most common in larger organizations.

Whatever the model, write down three things: who owns the end-to-end process, who owns the employee master data, and who decides when two departments disagree about a handoff. Most H2R problems I see trace back to one of those three being undefined.

Controls that keep hire to retire clean

Controls in H2R protect against three risks: paying people incorrectly, giving people access they should not have, and making commitments the company has not approved. These are the controls I would put in place first.

Preventive controls

Approved requisition before posting. No role goes to market without an approved requisition linked to the headcount plan.
Offer within approved range. Any offer outside the range requires documented approval from finance and the budget owner.
Single source of employee master data. One system, one record per employee, one team that can change core fields.
Segregation of duties. The person who creates or changes an employee record is not the person who approves payroll.
Role-based access provisioning. Access is granted from a role template, not copied from a colleague.
Payroll change cutoff. A fixed date after which changes move to the next cycle, with a documented exception route.

Detective controls

Payroll register to ledger reconciliation every cycle, with explained differences.
Headcount reconciliation between HR system, payroll and finance plan every month.
Joiner, mover and leaver access review every month: every leaver's access revoked, every mover's access adjusted.
Ghost employee check: people paid who do not appear in the active employee list or have no manager.
Unusual pay review: large variances from the previous period, retroactive payments, manual adjustments.

The one control that fails most

In my experience the control that fails most often is leaver access. The HR system knows the person has left. Payroll knows. The identity system does not, because nobody told it, or because the ticket was raised and not closed. Automating that single handoff often delivers more risk reduction than an entire new HR platform.

Self-assessment: how mature is your hire to retire process

Answer yes or no. Count the no answers.

Is there one named person accountable for the hire to retire process end to end?
Does every open role have an approved requisition linked to the headcount plan?
Is employee master data maintained in one system that all others read from?
Does a new hire have equipment and system access ready on day one, every time?
Do payroll changes follow a fixed cutoff with a documented exception route?
Is the payroll register reconciled to the general ledger every cycle?
Do HR, payroll and finance report the same headcount number each month?
Are pay changes from reviews entered before their effective date?
Is leaver access revoked on the last working day, with evidence?
Do you measure time to productivity, early attrition and offboarding completion?

0 to 2 no answers. Your process is solid. Focus on measurement and incremental automation.

3 to 5 no answers. You have specific broken handoffs, usually onboarding, payroll changes and leaver access. Fix those first with process and ownership, not new software.

6 to 10 no answers. H2R is run by people remembering things. That works until it does not. You need an owner, a map and a master data rule before anything else.

If your score lands in the high range and you are not sure where to start, a short outside review can save months of trial and error. You can ask for one through the consultation request on the site, with a few lines on headcount, systems and the handoff that hurts most.

Systems: what you actually need

Hire to retire does not require a single platform. It requires that the platforms you use agree on who the employee is.

The typical stack has five components:

Applicant tracking system for requisitions, candidates and offers.
Core HR system (HRIS) holding the employee master record, org structure and job data.
Payroll engine, internal or outsourced, calculating pay and producing accounting entries.
Identity and access management provisioning and revoking system access.
ERP or accounting system receiving payroll journals, accruals and cost allocations.

Many vendors sell suites that cover several of these. Suites reduce integration work, but they rarely remove the need for clean ownership and cutoffs. I have seen companies on a single suite with worse H2R than companies on five separate tools, because the suite gave everyone the illusion that the process was handled.

Integration rules that matter more than the tools

The core HR record is the source of truth. Every other system reads employee data from it. Nobody creates employees directly in payroll or identity systems.

Events drive downstream actions. A hire, a transfer or an exit in the core HR system triggers the corresponding action in payroll, identity and finance automatically, or at minimum generates a tracked task.

Effective dates are respected. A change effective on the first of the month is entered before the first of the month, not discovered after payroll has run.

Where AI and automation help in hire to retire

The most useful automation in H2R is not glamorous. It removes manual handoffs.

Works today: joiner, mover, leaver automation. Events in the HR system trigger provisioning and deprovisioning across systems. This is mature technology and the highest-value automation in most companies.

Works today: document intake. Extracting data from contracts, IDs and forms into the HR record, with human review of low-confidence fields.

Works today: employee service. Answering routine questions on leave, pay slips and policies through a well-scoped assistant connected to real policy documents, with a clear route to a human.

Works with good data: attrition signals. Flagging teams or roles with rising early attrition or absence. Useful as a prompt for managers, dangerous as an automated decision about individuals.

Needs caution: automated screening and decisions. Using AI to rank candidates or decide on people outcomes raises fairness and legal issues, and in the European Union the AI Act classifies many employment uses as high risk. Keep humans accountable for decisions about people.

A broader view of where AI fits in people processes is in the guide on AI for HR professionals.

Metrics that show whether hire to retire works

Measure the process, not just the department. These are the metrics I would put on one page.

| Metric | What it tells you | Frequency |

|---|---|---|

| Time to fill | Speed of recruiting | Monthly |

| Offer acceptance rate | Competitiveness of offers | Monthly |

| Day-one readiness | Share of hires with equipment and access on day one | Monthly |

| Time to productivity | How fast new hires reach expected output | Quarterly |

| Early attrition | Share of hires leaving within 12 months | Quarterly |

| Payroll accuracy | Share of payments requiring correction | Every cycle |

| Headcount variance | Difference between HR, payroll and finance numbers | Monthly |

| Leaver access closure | Share of leavers with all access revoked on last day | Monthly |

Early attrition deserves special attention. Gallup has estimated that replacing an employee can cost from one-half to two times their annual salary, and that 52% of employees who left voluntarily said their manager or organization could have done something to prevent it. Those figures date from 2019, so treat them as order of magnitude. The direction is what matters: most turnover costs are created in the first stages of H2R, long before anyone resigns.

What a working hire to retire process changes

In service businesses, people are the capacity. When I worked with a medical center that increased its capacity by 20%, and with a hotel whose revenue grew from 9 to 10 million, the growth came from different levers in each case. What both had in common is that growth puts pressure on the people chain: more roles to fill, more people to onboard, more schedules and more pay changes to process correctly.

That is the practical reason to fix H2R before growth, not after. If onboarding takes two weeks, every new hire costs two weeks of capacity you already pay for. In seasonal businesses such as hospitality, dozens of joiners arrive in a few weeks and leave together at the end of the season, so a slow start and a sloppy exit are paid for twice a year. None of that requires a new HR platform to fix. It requires someone to own the chain.

Hire to retire for contractors and contingent workers

Most H2R maps cover employees only. Many companies now have a meaningful share of their workforce on other arrangements: freelancers, agency staff, consultants, interns, employees of outsourcing partners working on site. They get laptops, system access and badges. They produce work and cost money. Very often they sit outside the process entirely.

That creates three problems.

Access risk. Contingent workers are the group most likely to keep access after they leave, because no HR event marks their exit. The contract ends in procurement, the identity system never hears about it.

Cost visibility. Contractor spend usually runs through accounts payable, not payroll. Finance sees invoices, HR sees nothing, and the true cost of a team is invisible to both. If this sounds familiar, the purchasing side of the problem is covered in the guide to the source to pay process.

Classification risk. In most jurisdictions, a person who works like an employee must be treated as one, whatever the contract says. Long-running contractors with fixed hours, a manager and company equipment are a legal exposure.

The practical fix is simple to describe and tedious to execute: every person with system access gets a record in the core HR system, with a worker type, an owner, an end date and a cost center. Contingent workers do not need the full H2R flow, but they need the joiner and leaver steps.

Compliance and records in hire to retire

Every stage of H2R creates records the company must keep, protect and eventually delete. The exact rules depend on the country, but the categories are the same everywhere.

Right to work and identity. In the United States, employers must complete Form I-9 for every new hire, with the employer section finished within three business days of the start date. Most other countries have their own equivalent. The control is the same: no start without verified documents.

Employment contracts and changes. The signed contract and every later change to pay, role or hours must be retrievable. Disputes almost always turn on what was agreed and when.

Pay and tax records. Payroll registers, tax filings and benefit records follow statutory retention periods that often run for several years after the employee leaves.

Personal data. In the European Union, the GDPR requires that personal data be kept no longer than necessary for its purpose. That means H2R needs a deletion rule as well as a retention rule: candidate data for people you did not hire, for example, should not live forever in the recruiting system.

A simple way to manage this is a records map: for each stage, list the documents created, the system that stores them, the owner, the retention period and the deletion method. It takes a few days to build and it answers most audit and data protection questions in advance.

How hire to retire connects to the other end-to-end processes

Hire to retire rarely breaks on its own. It breaks at the points where it touches the other core cycles.

Record to report. Payroll journals, bonus and holiday accruals, severance provisions and people cost allocations all land in the close. A late payroll change becomes a late journal, which becomes a late close.

Procure to pay. Recruiting agencies, contractors, training providers, equipment and benefits are all purchased. If H2R and purchasing do not share data, the company cannot see the full cost of a hire.

Order to cash. In service businesses, people are the product. Billable hours, utilization and project staffing link H2R directly to revenue. A consultant who joins two weeks late is two weeks of revenue the plan assumed. The revenue side of that chain is covered in the guide to the order to cash process.

When you map H2R, mark every point where data leaves the process and enters another one. Those are the handoffs to test first.

A worked example: tracing one leaver

The fastest way to find out how well your H2R process works is to pick one recent leaver and trace them through every system. Here is what I usually check.

Core HR record. Is the termination recorded, with the correct last day and reason?
Payroll. Was the final pay calculated with unused leave, commissions, deductions and any severance? Was it reviewed by a second person?
Accounting. Were accruals for the leaver reversed and any severance provision booked in the right period?
Identity and access. Were email, business applications, remote access and shared accounts disabled on the last day? Is there evidence?
Equipment. Were laptop, phone, badge and any other assets returned and logged?
Knowledge. Did files, customer relationships and open tasks move to a named person?
Documents. Were the legally required exit documents issued on time?

If the answer to all seven is yes, with evidence, your offboarding works. In most companies I have reviewed, at least two of the seven fail on the first trace, and access is almost always one of them.

Seven mistakes I see repeatedly

1. Treating H2R as an HR project. It is a cross-functional process. If finance and IT are not in the room, the handoffs that break will stay broken.

2. Buying a suite before mapping the process. Software configures what you tell it. If you do not know your stages, owners and cutoffs, you will automate the confusion.

3. Allowing multiple employee masters. Every time a system holds its own version of the employee, the numbers drift apart and nobody knows which is right.

4. Ignoring movers. Companies design joiner and leaver flows and forget transfers and promotions, which change cost centers, managers, access and pay all at once.

5. Letting offboarding be an afterthought. The exit is the stage with the highest risk per event: access, final pay, data, equipment and legal documents.

6. Measuring only time to fill. Speed of hiring is visible and easy. Early attrition and time to productivity tell you whether the hires worked.

7. Automating people decisions before people processes. The most valuable automation is in handoffs, not in judgments about candidates or employees.

A 30, 60 and 90 day plan

Days 1 to 30: map and assign

Name one accountable owner for the hire to retire process.
Map the eight stages with the actual owners, systems and handoffs, not the ones in the policy.
Pick the last ten joiners, movers and leavers and trace each one through every system.
Answer the ten self-assessment questions with HR, payroll, finance and IT together.
Decide which system holds the employee master record, and write it down.

Days 31 to 60: fix the handoffs

Build a day-one checklist for joiners covering contract, payroll setup, equipment and access.
Set a payroll change cutoff and an exception route, and communicate it to all managers.
Create role-based access templates for the ten most common roles.
Automate or ticket the leaver access revocation so it happens on the last day.
Start the monthly headcount reconciliation between HR, payroll and finance.

Days 61 to 90: measure and extend

Publish the eight metrics on one page and review them monthly.
Add the mover flow: transfers and promotions with cost center, manager, access and pay changes.
Review the first month of reconciliations and fix the recurring causes of difference.
Decide which automation delivers the most value next, based on the errors you actually found.

If halfway through this plan you find that the ownership questions are harder than the system questions, that is normal, and it is where an outside view usually saves the most time. You can request a conversation through the consultation form on the site, describing headcount, systems and the stage that causes the most rework.

FAQ

What are the hire to retire process steps and owners?

The hire to retire process usually has eight stages: workforce planning and requisition, recruiting, offer and pre-boarding, onboarding and provisioning, payroll and compensation, time and absence, performance and internal mobility, and offboarding. Finance and hiring managers own planning, talent acquisition owns recruiting, HR owns offers and onboarding with IT, payroll owns pay with finance, line managers own time approvals and reviews, and HR, IT and finance share offboarding. One person should be accountable for the whole chain.

What does hire to retire mean?

Hire to retire, or H2R, is the end-to-end business process that covers the full employee lifecycle, from the approval of a new role to the final payment and documents after an employee leaves. It groups recruiting, onboarding, payroll, time management, performance, internal moves and offboarding into one process with shared data and handoffs, in the same way order to cash or procure to pay group the steps of a commercial or purchasing cycle.

Who should own the hire to retire process?

One named person should be accountable for the process end to end. In practice this is the head of HR or people operations, the CFO or controller, or a shared services leader, depending on where payroll sits and how strong each function is operationally. Whatever the model, the company also needs a clear owner of employee master data and a rule for resolving disagreements between departments at the handoffs.

What are the key controls in hire to retire?

The core preventive controls are an approved requisition before hiring, offers within approved ranges, a single employee master record, segregation of duties between data changes and payroll approval, role-based access provisioning and a fixed payroll change cutoff. The core detective controls are a payroll register to ledger reconciliation each cycle, a monthly headcount reconciliation, a monthly access review for joiners, movers and leavers, and checks for ghost employees and unusual pay.

What metrics should I track for hire to retire?

Track metrics across the whole chain rather than one department: time to fill, offer acceptance rate, day-one readiness, time to productivity, early attrition within twelve months, payroll accuracy, headcount variance between systems and leaver access closure on the last day. Early attrition and time to productivity are the most revealing, because they show whether hiring and onboarding actually worked.

Do I need new software to fix hire to retire?

Usually not first. Most hire to retire problems come from missing ownership, multiple employee records and broken handoffs between HR, payroll, IT and finance. Name an owner, define the master record, set a payroll cutoff and automate leaver access before evaluating new platforms. Once the process is clear, software choices become much easier and the implementation is far less risky.

How long does it take to improve a hire to retire process?

A focused effort usually shows results within 90 days. The first month goes to naming an owner, mapping the eight stages and tracing recent joiners, movers and leavers through every system. The second month fixes the most painful handoffs, typically day-one readiness, the payroll change cutoff and leaver access. The third month adds metrics and the mover flow. Larger system changes, such as replacing an HR platform, take longer and work better once the process is already clear.