HR Records Reconciliation: Make Your Employee Lists Agree

The problem this kills

Somewhere in your company, the same employee exists in four different systems — your HRIS, payroll, IT/access management, and the badge system — and those four systems quietly disagree. Someone was terminated in the HRIS three weeks ago but is still active in payroll, so they're getting paid. Someone left months ago but their email login and building badge still work, a ghost account waiting to be misused. A name change went into one system and not the others. A promotion updated a title here but not there. Nobody set out to let this happen; it's just what happens when four systems are updated by four different people on four different days.

The painful part is that you usually find out too late — during an audit, after a fraud, when a "terminated" employee shows up on a payroll register, or when security asks why a departed contractor still has VPN access. The clues are sitting in plain sight: you have the employee list from each system. They just need to be lined up, key by key, field by field, so the disagreements jump out. You do not need to be a developer to build the thing that lines them up.

What you'll build

A simple internal web tool for HR ops, payroll, and IT. You import an employee export from each system — HRIS, payroll, IT/access, badges, whatever you have — and tell it the common key (an employee ID or email). The tool lines every person up across the systems and compares the fields you care about: status, name, title, department, manager, start/end dates. Then it shows you every discrepancy, sorted by risk: people missing from a system, fields that mismatch, and the highest-risk of all — status conflicts like active-in-payroll-but-terminated-in-HRIS. HR reviews each one, decides which source is right and what action to take, and only then does the tool produce a correction worklist CSV for each system owner. No system is auto-updated; HR stays in charge of every fix.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — which systems you're reconciling, what each export actually looks like, your real column names, how employee IDs and emails are formatted across systems, your typical and peak headcount, and your rules for which source "wins" for each field. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the per-system CSV imports, the keying and matching engine, the discrepancy categorizer, the HR review-and-resolve screen, the human approval gate, and the per-system correction worklist exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real HR function needs: login so only your team can use it, row-level security so people only see their own organization's records, a complete audit trail of every resolution and override (who decided, what they chose, when, and why), a hard human-approval gate so nothing is written to a correction worklist until a person decides, and duplicate guards so the same export can't be imported and processed twice. The whole tool exists to make a careful human decision easy — the AI surfaces the disagreement, a person makes the call. That matters more here than almost anywhere: a wrong "fix" to an employee record is a payroll error or a wrongful access change.

Who it's for

HR ops leads, payroll managers, and IT/access owners who keep discovering — too late — that their employee lists don't match. If you can export a list of people from each of your systems and say which field should win when they disagree, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be reconciling your real employee lists this weekend.