Answer capsule: A manual ATS-to-HRIS handoff turned a $103K salary into $130K on a new hire’s file at a mid-market manufacturer. The error cost $27K in overpayment, and the employee quit after HR corrected it. The fix is not a stricter checklist — it’s removing the manual re-entry step entirely. Automating the ATS-to-HRIS handoff with Make.com closes the exact gap that created this failure, and it costs nothing close to what one bad data entry already cost this company.

The Challenge: One Manual Handoff, One New Hire’s Trust

David runs HR for a mid-market manufacturer. His team hires steadily — production staff, shift supervisors, the occasional engineer — and every hire follows the same path: offer accepted in the applicant tracking system (ATS), then someone on his team keys that candidate’s data into the HRIS by hand. Name, start date, department, salary. Line by line, copy from one screen, paste into another.

This is the exact handoff we cover in Automating Employee Onboarding the Right Way, and it’s the single most common failure point we see in manufacturing and mid-market HR teams. Manual re-entry between systems isn’t a training problem. It’s a structural one — anywhere a human retypes data that already exists somewhere else, the error rate isn’t zero, it’s just unmeasured until it costs you.

For David’s team, the cost showed up on one new hire’s very first paycheck.

What Went Wrong: A Single Keystroke, A $27K Bill

The new hire’s approved salary in the ATS was $103K. When David’s team transferred that number into the HRIS by hand, it became $130K. A transposition — three keystrokes reversed, no different from a typo in an email. Nobody caught it. Not the HR coordinator entering the data, not payroll processing the first cycle, not anyone reviewing the file until well after paychecks had already gone out at the wrong rate.

By the time the error surfaced, the company had overpaid the employee by $27K. HR corrected the salary to the accurate $103K. That’s the right move — you can’t leave a wrong number on the books. But the correction landed on the employee as a pay cut, with no warning and no context about how the number got there in the first place. The employee quit shortly after.

This is the part of the story that matters most, and it’s covered in more depth in 9 Employee Onboarding Tasks You Should Never Do Manually in 2026: the damage from a manual data error rarely stops at the dollar figure. David’s team didn’t just eat a $27K accounting problem. They lost a new hire in the first weeks of employment, burned the time spent recruiting and onboarding that person, and had to restart the search. The $103K-to-$130K transposition is the headline number. The quit is the real cost.

Why This Keeps Happening: The Manual Data Entry Gap

David’s team isn’t careless. This is what manual data entry does at scale. Every new hire’s file requires the same fields transferred by hand — salary, title, department, start date, manager, benefits eligibility — and every one of those fields is a chance for a transposition, a dropped digit, or a copy-paste from the wrong row. According to SHRM, onboarding data errors are one of the most common and most preventable causes of new-hire dissatisfaction in the first 90 days, and salary or pay discrepancies sit at the top of that list.

The signs are usually visible before the failure happens. If your team is retyping ATS fields into your HRIS, cross-checking numbers in a spreadsheet, or catching errors after the fact instead of before, you’re carrying the same exposure David’s team carried. We walk through exactly what those warning signs look like in 7 Signs Your Onboarding Process Is Costing You New Hires.

The deeper issue is that manual re-entry treats a data transfer problem like a discipline problem. No amount of “double-check your work” instruction fixes a process where a human has to accurately retype a five-or-six-digit number, correctly, every single time, with zero system checking it against the source. Eventually the process fails. It’s not a matter of if.

The Automated Fix: Removing the Re-Entry Step Entirely

The fix here isn’t a better spreadsheet or a second reviewer. It’s removing the manual re-entry step from the process, using Make.com to connect the ATS directly to the HRIS.

Here’s how the automated version of David’s process runs. When a candidate’s status changes to “Hired” in the ATS, a Make.com scenario triggers automatically. It pulls the candidate’s approved data — salary, title, start date, department — directly from the ATS record, the same record that was already approved during the hiring decision. That data maps into the corresponding fields in the HRIS through a direct field-to-field connection. No human retypes the salary. No human retypes anything. The number that lands in the HRIS is the exact number that was approved, because it’s the same number, moved automatically instead of copied by hand.

This is the automation-first-then-AI thesis we build every scenario around. Automation handles the structured, repeatable transfer: fields moving from one system to another in a fixed, predictable pattern. That’s not a job for AI judgment — it’s a job for a reliable, rules-based connection that behaves identically the 500th time as the first. AI has a role in onboarding, but it belongs on top of a clean automated structure, handling unstructured tasks like summarizing a candidate’s background or drafting a personalized welcome note. Salary transfer isn’t unstructured. It’s a lookup and a match, and that’s exactly what automation is built to do without error.

We cover the specific mechanics of this handoff — which fields to map first, how to handle exceptions, what to automate versus what still needs a human decision — in How to Automate New Hire Paperwork (Without Losing the Personal Touch).

Adoption-by-Design: Why This Fix Sticks

The reason this kind of fix works long-term is that it doesn’t ask David’s team to learn a new system or change how they work. The ATS and HRIS David’s team already uses stay exactly the same. The only thing that changes is what happens between them — instead of a person bridging the two systems with a keyboard, Make.com bridges them invisibly. Nobody on the HR team has to remember a new step, follow a new checklist, or get retrained. The work just gets easier, and the error that used to slip through has nowhere left to slip.

Results and Prevention: What Changes With the Handoff Automated

The table below shows the same ATS-to-HRIS handoff David’s team ran manually, compared to the automated version built to prevent the exact failure that cost $27K.

The prevention case here is straightforward. Once the ATS-to-HRIS handoff runs on a direct, automated connection, there’s no step where a human retypes a salary figure, which means there’s no step where $103K can silently become $130K. The $27K overpayment David’s team absorbed wasn’t a one-time bad break. It was the predictable outcome of a process with a gap in it, and the gap is what got fixed.

Research from McKinsey on process automation consistently finds that structured data transfers — the kind with a fixed, repeatable format like ATS-to-HRIS fields — are where automation delivers the most reliable error reduction, because the task has no ambiguity for a system to get wrong. That’s precisely the category David’s failure falls into.

Lessons: What Every HR Team Should Take From This

David’s case is a manufacturing HR story, but the lesson isn’t specific to manufacturing. Any HR team moving candidate data from an ATS into an HRIS by hand is one transposition away from the same outcome: a wrong number, a hard correction, and a new hire who walks. The fix isn’t more careful people. It’s a system that doesn’t need a human to retype a number that’s already correct somewhere else.

David’s manufacturer isn’t the only company we’ve helped fix this exact category of gap. Nick, a recruiter at a small staffing firm, faced a different version of the same manual-data problem before automating his intake process — that story is in Nick’s onboarding automation case study. And Sarah, an HR Director at a regional healthcare system, hit her own breaking point with manual onboarding tasks before automating her team’s workflow, covered in Sarah’s onboarding automation case study. A company-wide version of this fix, including the ROI math on a larger scale, is in the TalentEdge onboarding automation case study.

Harvard Business Review has reported repeatedly that the first 90 days of employment set the tone for retention, and a preventable pay error in that window does outsized damage relative to its dollar size. David’s $27K mistake wasn’t really a $27K problem. It was a lost hire, a restarted search, and a dent in trust that a clean process would never have created.

Expert Take

The number that sticks with people in David’s story is $27K. That’s the wrong number to fixate on. The real number is one — one manual keystroke, repeated across every new hire, with no system checking it against the source. Fix that one step and the $27K problem doesn’t come back, because it was never really about the money. It was about a process that depended on a human getting a five-digit number right every single time, with nothing backing them up. Automate the handoff, and the backup exists by design.

FAQ: Automating the ATS-to-HRIS Handoff

What exactly went wrong in David’s case?

A new hire’s approved salary of $103K was manually entered into the HRIS as $130K. The error wasn’t caught until after paychecks reflected the wrong rate, resulting in a $27K overpayment that had to be corrected.

Why did the employee quit after the correction?

The correction from $130K back to $103K landed as an unexplained pay cut. Manual errors like this don’t just cost money — they cost trust, and in this case, the new hire.

Is this a manufacturing-specific problem?

No. Any HR team transferring candidate data from an ATS to an HRIS by hand carries this same exposure, regardless of industry.

What’s the actual fix?

Removing the manual re-entry step. A Make.com scenario pulls approved data directly from the ATS record and maps it into the HRIS automatically, so no human retypes the salary figure.

Does this mean AI replaces the HR team here?

No. Automation handles the structured field transfer. AI has a place in onboarding for unstructured work like drafting welcome messages, but the salary handoff itself is a rules-based task best handled by automation, not judgment.

For a full build-out of this cluster’s foundation, start with Automating Employee Onboarding the Right Way.