Guide
How to compare two HR employee exports
A step-by-step guide to comparing two HR employee exports so HR can review new, removed, and changed records before reporting.
Short answer
Use a stable employee identifier first, then compare who is new, removed, or changed across the two files. The review should look at status changes, manager changes, department or location changes, newly populated termination dates, and unexpected changes to fields used in reporting.
Why this matters
- A month-over-month export comparison is often the fastest way to spot reporting drift.
- Not every changed row matters equally; HR needs to distinguish operational follow-up from data review.
- Recurring reporting becomes easier when the same comparison workflow can be reused each cycle.
What HR should check
- Stable employee ID and whether the same person appears once or multiple times.
- New employees, removed employees, and rows present only in one file.
- Status, manager, department, location, employment type, and date fields that changed.
- Whether the differences reflect real movement, data cleanup, or a broken export assumption.
Review checklist at a glance
| Comparison area | Why it matters | What to review first |
|---|---|---|
| Stable employee ID | It keeps the same person anchored across both files. | Match on one stable identifier before looking at names or changed fields. |
| New, removed, and changed rows | These are the three buckets that explain most run-to-run movement. | Separate true adds/removals from rows that only changed values. |
| Manager, department, location, status | These fields often create follow-up work as well as reporting drift. | Focus first on changes that affect counts, ownership, or downstream review. |
| Unexpected differences | Some movement reflects cleanup or broken export assumptions, not real workforce change. | Ask whether the change reflects a business event, a source correction, or a mapping issue. |
Common mistakes
- Comparing only totals without checking changed rows.
- Matching on display name instead of a stable employee ID.
- Treating every changed field as equally urgent.
How KYBN helps
- KYBN separates follow-up action rows from broader comparison summaries so the output is easier to interpret.
- The comparison workflow can preserve run-to-run context without keeping every raw file forever.
- Changed rows can be reviewed alongside the same snapshot and reporting setup used for the main outputs.
Quick questions
Should HR compare totals only?
No. Totals are a starting point, but changed rows explain why the total moved and whether the movement is real, operational, or caused by data issues.
Can display name be used for comparison?
Only as a secondary reference. The main comparison should use a stable employee identifier so renamed or duplicated names do not distort the review.
Related resources
Try the workflow
If this is the kind of HR reporting problem your team is dealing with, start with a sample workspace or review sample outputs before using a real employee file.