Solution Icon

Solutions

Cutting-edge solutions tailored to everyday issues in the modern digital environment.

Services icon

Services

Innovative tools and services designed to address complex challenges today’s digital landscape.

IT FOR What WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

IT FOR HOW WE DO MENU

Aerial view of an industrial facility at sunset

Services

Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.

Ready to clean up your CRM workflow?

Book a CRM Workflow Audit and see where leads, follow-ups, reporting, or disconnected tools can be fixed first.

Integration

ATS Integration: What to Connect Before You Hire

A buyer guide for HR, operations and IT leaders connecting an applicant tracking system to HR, payroll and IT: what data to move, which rules apply and how to test it.

  • Integration
  • Buyer Guide
  • Updated November 2026
Dark cover with the words Connect ATS to HR and Payroll First

ATS integration means your applicant tracking system hands a hired candidate to HR, payroll and IT without anyone retyping the record. The safest way to start is to connect one event, the accepted offer, and send only the fields each system needs. Get that handoff right before you sync anything else.

This guide is for HR leaders, operations managers and IT owners who run an ATS such as iCIMS, Greenhouse or Lever next to a separate HR, payroll or ERP system. It covers what to connect first, which rules shape the design, and how to test it before the first new hire goes through.

What does ATS integration actually connect?

An ATS is built to manage candidates. Your HR system is built to manage employees. The gap between them is the moment a candidate becomes an employee, and that is where most manual work and most errors happen.

A typical integration connects four handoffs:

  • Offer accepted to HR system. Create the employee record with name, contact details, job, department, manager, location and start date.
  • HR system to payroll. Pass pay rate, pay group and tax setup once HR has confirmed them.
  • HR system to IT. Open a ticket or workflow to create accounts and order equipment before day one.
  • Back to the ATS. Mark the requisition filled so recruiters stop sourcing for it.

Not every company needs all four on day one. Most get the biggest return from the first one, because it removes the double entry that causes typos in names, start dates and pay details.

Which candidate data should move, and which should stay?

We start every ATS integration project with a field list, not a connector. For each field, we ask three questions: which system owns it, who needs it next, and when does it stop being needed.

Candidate records hold far more than an employee record needs. Interview notes, scorecards, rejected applications and assessment results usually belong in the ATS only. Copying them into HR or payroll spreads sensitive data into systems with wider access and different retention rules.

A short rule works well: move data forward only when the next team must act on it. The payroll team needs a pay rate. It does not need the interview feedback that led to the offer.

What rules shape how hiring data is stored and shared?

Several U.S. rules affect the design. They do not tell you which software to buy, but they tell you what the systems must keep and how fast data has to move.

  • Record retention. Under the EEOC recordkeeping rule, application forms and other personnel records generally must be kept for one year from when the record was made or the personnel action was taken, and longer if a charge of discrimination is filed. Your ATS and HR system need a retention setting that matches your policy, not a default that deletes or keeps everything forever.
  • New hire reporting. Federal law requires employers to report new hires to their state directory. The required items include the employee's name, address, Social Security number and date of hire, plus the employer's name, address and federal employer ID. States set the deadline. Utah, for example, asks employers to report within 20 days of the first day of work. If your HR system files these reports, the start date coming from the ATS must be right.
  • Access control. Sensitive fields such as Social Security numbers should be collected in the HR or payroll system during onboarding, not passed through the ATS, whenever your vendors allow it.

We are not your legal counsel, so confirm your retention policy and state filing rules with your HR advisor or attorney before you build.

What should you connect first?

We usually recommend this order for a mid-sized company:

  1. Accepted offer creates a pending employee. One trigger, a small set of fields, and a person in HR who reviews and approves the new record.
  2. Approved employee starts IT setup. Accounts and equipment are requested on a fixed number of days before the start date.
  3. Payroll setup follows HR approval. Pay data moves only after HR confirms it, never straight from the offer letter.
  4. Status flows back to the ATS. Filled requisitions close automatically.

If you already use workflow automation for approvals, the HR review in step one can live there. Each step should work on its own before you add the next. If step one is still producing duplicate employees, adding payroll will copy the problem into paychecks.

How do you test the handoff before go-live?

A good test uses real scenarios, not one happy-path record. Before go-live, we run cases like these in a sandbox or test tenant:

  • A candidate whose start date changes after the offer is accepted.
  • A rehire who already has an old employee record.
  • An offer that is rescinded after the record was created.
  • Two candidates with the same name hired in the same week.
  • A manager or department that does not exist yet in the HR system.

For each case, write down what should happen and who gets told when it fails. Silent failures are the real risk. A sync that skips a record without alerting anyone means a new hire shows up with no laptop and no payroll record.

After launch, keep a simple weekly check for the first month: offers accepted in the ATS against pending employees created in HR. The two counts should match.

Should you use a native connector or build a custom integration?

Start by checking what your ATS and HR vendors already offer. Many ATS products publish connectors or open APIs for common HR systems. A native connector is usually the cheapest path when your field list is short and your process is standard.

A custom or middleware integration makes sense when:

  • You need an approval step the native connector cannot add.
  • Your HR, payroll and IT tools come from different vendors with no shared connector.
  • You need clear logs and alerts for every failed record.
  • You plan to add more systems later, such as a CRM or an ERP for job costing.

Either way, ask the vendor who owns the integration when an API changes. Someone has to watch for version updates and fix the mapping, or the sync breaks quietly months later.

Frequently asked questions

What is ATS integration?

It is the connection between your applicant tracking system and the systems that take over after a hire, such as HR, payroll and IT. It moves the hired candidate's details forward so nobody retypes them.

Which data should go from the ATS to the HR system?

Only what HR needs to create the employee: name, contact details, job, department, manager, location and start date. Interview notes and scorecards usually stay in the ATS.

How long does an ATS integration take?

A native connector with a short field list can go live in a few weeks once testing is done. Custom work with approvals, alerts and several target systems takes longer, so scope one handoff first.

Do we need to change our ATS to integrate it?

Usually not. Most modern ATS products offer an API or connectors. The bigger work is agreeing on field ownership, approvals and how failures get reported.

Planning an ATS integration?

We help growing companies connect hiring, HR, payroll and IT systems with clear approvals, logs and alerts, so new hires start with everything ready.

Explore API Integration Services

Sources

BUSINESS SYSTEMS

SOFTWARE

AI

INTEGRATIONS

Build, Improve, or Connect the Systems Your Business Depends On.

Whether you need custom software, CRM, ERP, AI, automation, integrations, or modernization, tell us what you’re trying to improve. We’ll review your requirements and recommend the most practical next step.

300+

Software projects delivered

37+

Enterprise apps built

150+

delivery team members

★★★★★ 4.7 on Google · 20 reviewsU.S.-led since 200721 awards & certifications →
Client results
BMG: cut the time lost on follow-ups by 70% with our CRM.
Utah Dental Association: convention registration streamlined from months to one month.

Tell Us About Your Project

No sales pressure. Tell us what you’re trying to build, improve, integrate, automate, or replace. We’ll review your answers and come back with a clear recommendation within 1 business day.

Prefer to talk now? Call +1 (801) 259-4800 or book a free 30-minute review.

© 2026 Hexagon IT Solutions. All rights reserved.