Outsourced EmploymentPowered by StealthAgents

Practical guide

Run a monthly roster reconciliation between the ATS and payroll

A monthly control that finds employees, pay rates, and status changes that disagree between the applicant system and payroll.

Published

Practical guide illustration for Run a monthly roster reconciliation between the ATS and payroll
Table of contents

Choose the fields that must match

The applicant tracking system and payroll serve different purposes, so not every field needs to match. Choose the small set that affects pay, access, reporting, or legal obligations. Legal name, employee identifier, job code, pay rate, start date, manager, and employment status usually belong on the list. Add any field that triggers a payment or a compliance report.

Define the master source for each field before comparing anything. The applicant system may own the candidate record, payroll may own the pay setup, and a separate HR system may own the job and manager. Write the owner next to each field so a mismatch has a destination. Without that rule, the reconciliation becomes an argument about which screen is correct.

Decide which differences are tolerated and which are true exceptions. A preferred name, a formatting difference in a phone number, or a middle initial may not affect pay. A missing employee identifier or a different pay rate does affect it. Publish the tolerance rule so the reviewer does not spend time on harmless noise.

Document the field list in the reconciliation file so the reviewer does not reinvent it each month. Include the owner and the tolerance rule next to each field. A short legend is enough. The legend should be updated when a system changes. Store it with the report rather than in a separate policy folder.

Export both rosters on the same date

Freeze both exports at the same time and record the query used for each one. A roster pulled on Monday and a payroll file pulled on Wednesday will show changes that are not errors. Save the raw exports with the reconciliation and note the extraction date. The working file should be reproducible by another reviewer.

Match records with the employee identifier when both systems share one. If they do not, use a composite key such as legal name plus start date and location, and review near matches by hand. Never match by name alone because duplicates and name changes are common. Record every manual match and the reason for it.

Limit access to the exports because they contain personal and pay data. Use the approved storage location rather than a personal drive or a chat attachment. Remove the working copies when the review is complete and keep only the approved report. The reconciliation should not create a second uncontrolled roster.

Save the query text with the exports so the next analyst can reproduce the same population. A screenshot of a report is not a substitute for the query. If the system does not expose the query, record the filters and the date. The reconciliation should be repeatable. Add the name of the person who ran each export.

Work the exceptions in a fixed order

Start with people who are active in payroll but missing from the applicant system, or active in the applicant system but missing from payroll. Those gaps can mean an unrecorded hire, a missed termination, or an access risk. Resolve them before comparing less urgent fields. A missing person is more important than a formatting difference.

Then compare pay rate, job code, manager, start date, and status. Route each discrepancy to the field owner with the evidence attached. Do not let the reviewer edit both systems at once, because that makes it impossible to tell which change fixed the record. Record the decision, the corrected value, and the date.

Verify the correction in the downstream system before closing the item. A change that appears in the review file but never reaches payroll is still open. Check the audit log if the update is not visible. Close the item only when the owner confirms the receiving system has the same value.

Set a target date for each exception and review the aging list at the end of the week. An item that stays open across two cycles should be escalated to the field owner's manager. Record the escalation and the reason. A monthly control that leaves items open for months is not a control. Report the age of open items in the monthly summary.

Close the month with a short report

Report the number of records compared, the number of exceptions by field, the age of each open item, and the owner responsible. Include repeat exceptions from the previous month so the team can see whether a fix worked. A one-page report is enough if the counts and owners are clear. Attach it to the payroll close record.

Use the repeat pattern to repair the root cause. A recurring start-date mismatch may point to a delayed handoff from recruiting. A recurring pay-rate mismatch may point to an offer template that shows only an annual figure. Add a control at the point where the error enters rather than hiring another reviewer.

Review the field list each quarter and remove fields that no longer affect pay or compliance. Add fields when a new system, location, or benefit changes the risk. Keep the report with the payroll records for the required retention period. The goal is a roster that can be trusted without a monthly rescue.

Send the report to the payroll owner and the operations lead, not to a broad distribution list. The report contains personal data and should have a named audience. Ask each owner to confirm the corrections assigned to them. Keep the acknowledgment with the report. Review the distribution list when a role changes.

Sources

References supplied with this guide.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
Internal Revenue Service, Publication 15irs.govPrimary reference supplied with this article.
U.S. Small Business Administration, Manage your businesssba.govPrimary reference supplied with this article.