Unusual pay changes
Large period-to-period differences on the same employee ID are listed for review.
Payroll validation
Upload a payroll register and a comparison file — prior period, HR list, or attendance extract. The engine checks the files. It does not calculate net pay, file taxes, or submit a payroll.
Payroll mistakes are expensive and easy to miss in a 400-row register. Unusual pay changes, duplicate employee IDs, joiners and leavers, and attendance inconsistencies should be reviewed before the file is sent to the payroll processor.
How it works
Step 1
Current payroll export plus a comparison file.
Step 2
Employee ID, status, pay elements you want checked.
Step 3
Compare periods and list unusual changes and inconsistencies.
Step 4
Duplicates, missing people, joiners, leavers, and surprises.
Step 5
Share the finding list. The source register is not rewritten.
What this workflow is designed to do with uploaded files.
Large period-to-period differences on the same employee ID are listed for review.
Repeated IDs or overlapping rows are flagged.
People on the comparison file who are absent from the current register stay visible.
New IDs and IDs that disappeared versus the prior file are grouped.
When both files include hours or attendance, mismatches are listed.
Status or department changes that you mapped can appear as review points.
The core job is file versus file — not live payroll processing.
Compare February and March registers. EMP-1042 is new (joiner). EMP-0881 is absent (leaver). EMP-1109 base pay changed more than the usual pattern in the file. Those findings are review points. They are not a new payroll.
Sample preview
Synthetic employee IDs only. Not a real payroll file.
| Reference | Counterparty | Amount | Status | Note |
|---|---|---|---|---|
| EMP-1042 | New joiner | — | Joiner | Present in March, not in February |
| EMP-0881 | Leaver | — | Leaver | Present in February, not in March |
| EMP-1109 | Pay change | — | Unusual change | Base pay differs from prior period |
| EMP-0770 | Duplicate ID | — | Duplicate | Same employee ID on two rows |
Validation is a control before processing. Privacy matters: keep real payroll files inside your tenant. Examples on this page use synthetic IDs only. AuditExport does not claim to be a payroll engine.
Continue with the workflows that usually sit next to this one.
No. AuditExport validates payroll data. It does not run payroll, calculate tax, or submit filings.
No. Marketing previews use synthetic IDs such as EMP-1042. Your uploaded files stay in your tenant.
No. Deterministic checks produce findings. AI does not alter payroll values.
Upload a register and a comparison file. Review findings before the file is processed elsewhere.