Before you approve payroll, answer one question: can every material change in this run be traced to an approved source?

A payroll register can look reasonable and still be wrong. A terminated employee may still be active. A new hire may be missing. A salary change may have started in HR but not reached payroll. A benefit election may have changed without the deduction following it. A bank-account update may be legitimate but unsupported.

That is why pre-payroll reconciliation should end in a decision, not a completed checklist.

Use three outcomes:

RELEASE: the proposed run matches approved source data, and all material exceptions are resolved.

HOLD: one or more material exceptions remain unexplained, unsupported, or unapproved.

RELEASE WITH DOCUMENTED EXCEPTION: an authorized reviewer accepts a defined exception that does not prevent the run from proceeding, with an owner and follow-up date recorded.

This guide focuses only on the controls you run before payroll is approved and funds move. Deposit verification, tax notices, provider migrations, and year-end reconciliation are different jobs and should be handled separately.

1. Freeze the payroll run before you reconcile it

Do not reconcile against moving data.

Start by recording the control details for the proposed run:

The source-data cutoff matters because payroll inputs change continuously. If an employee's compensation, status, bank details, benefits, or time record changes after reconciliation, that change needs to be treated as a new exception or the reconciliation needs to be refreshed.

A good control answers: what exact version of the source data did we approve against?

2. Decide which source owns each payroll field

Payroll reconciliation becomes unreliable when the team cannot answer where the approved value is supposed to come from.

ADP describes payroll reconciliation as comparing payroll records against source data across areas such as HR, time and attendance, benefits, employee status, deductions, tax withholdings, and net pay. It also recommends reviewing the payroll register before approval and investigating material variances. ADP's payroll reconciliation guidance is useful here as operating practice, not as a universal rule for every company.

Build a simple source-of-truth map before you compare numbers:

Do not assume one system must be authoritative for every field. A startup may use one system for HR, another for time, another for benefits, and a payroll provider for calculation. The important control is that each field has a named approved source and a named owner.

3. Run an employee-change diff before reviewing totals

The fastest way to miss a payroll error is to start with company-level totals.

Start with the people who changed.

Compare the current pay-period population against the prior run and the approved source records. At minimum, review:

New hires

Confirm:

• the employee exists in payroll;
• the correct legal entity is paying them;
• start date is correct;
• salary or hourly rate matches the approved record;
• work location is current;
• bank instructions were provided through the approved process; and
• benefit and deduction treatment matches the company's process and effective dates.

Terminations

Confirm:

• the employee is not being paid beyond the authorized period;
• termination effective date matches the approved record;
• final compensation inputs are complete;
• benefit and deduction handling is consistent with the relevant instructions; and
• the employee has not accidentally remained active in a downstream payroll population.

Final-pay rules vary by jurisdiction. Route timing or pay-entitlement questions to the payroll provider or qualified legal/payroll owner.

Compensation changes

Match each new salary, hourly rate, bonus, commission, or one-time payment to an approved record and effective date.

An email saying "please bump Alex to $120k" may be evidence of intent, but your process should define who is allowed to authorize the change and where the approved value is recorded.

Time and leave

For hourly or time-dependent payrolls, compare approved hours, leave, and other time-based inputs against the proposed run.

Do not correct a suspicious result by editing payroll until you know which source record is wrong.

Benefits and deductions

Compare current deductions against approved elections, changes, terminations, and other applicable source records. Look for:

• new deductions;
• stopped deductions;
• unexpected amount changes;
• employees deducted despite ineligibility;
• eligible employees with no expected deduction; and
• one-time corrections.

Bank-account changes

Treat bank changes as both a payroll and fraud-control event.

Confirm the employee change came through the approved process. A bank change arriving through an unusual channel immediately before payroll cutoff is a reason to stop and authenticate it, not a reason to rush.

4. Review the payroll register and explain the variances

After the employee-change diff, review the proposed payroll register.

ADP recommends reviewing items such as total employees, hours, gross pay, deductions, taxes, net pay, and funding before payroll approval. Its reconciliation guide provides a useful starting structure.

You are looking for two types of exception:

1. Source mismatch: payroll does not match the approved source.
2. Unexpected result: payroll may match the inputs, but the resulting amount is unusual enough to require explanation.

Does the employee population make sense?

Compare:

• current employee count versus prior payroll;
• new hires expected this run;
• terminations expected this run;
• employees on leave;
• employees with zero or negative pay; and
• any unexpected reactivated or omitted workers.

Does gross pay make sense?

Compare current gross pay with the prior run and explain material movements using:

• headcount changes;
• salary or rate changes;
• hours;
• bonuses;
• commissions;
• retroactive pay;
• leave;
• reimbursements where processed through payroll; and
• other one-time earnings.

Do not create a universal percentage variance threshold. A 25% increase caused by an approved bonus may be fine. A 2% increase caused by an unknown employee may not be.

Do the deductions make sense?

Look for large movements, unexpected new deductions, missing deductions, and employee-level differences.

Does withholding look unusual?

For federal withholding, compare payroll against the employee's effective Form W-4 or other currently applicable IRS withholding instruction.

IRS Publication 15 explains, among other things, that a replacement Form W-4 generally must be put into effect no later than the first payroll period ending on or after 30 days from receipt, though employers may choose to apply it earlier. It also explains that an IRS lock-in letter can control withholding. Publication 15-T contains the federal income-tax withholding methods.

That is why the source-of-truth map should say effective Form W-4 or applicable IRS withholding instruction, not simply "latest W-4."

Do not turn pre-payroll review into an independent tax calculation unless that is actually part of the team's qualified role. Investigate unexpected changes and route the issue to the correct owner.

Does the funding requirement make sense?

Compare the proposed funding amount with:

• net employee pay;
• known employer taxes and provider withdrawals where applicable;
• benefit or other payroll-related funding items; and
• the prior run, adjusted for known changes.

An unexplained funding movement is an exception even when individual employee rows appear reasonable.

5. Record exceptions instead of "checking the box"

The purpose of reconciliation is not to make every row green. It is to make every material difference explainable.

Use an exception register with these fields:

The most important column is not "status." It is evidence.

A comment such as "HR confirmed" is weaker than a link to the actual approved change record. "Provider says okay" is weaker than a reviewed register, approval, or employee election that supports the result.

6. Define your HOLD conditions before the deadline

Do not decide what is serious only when payroll is five minutes from cutoff.

A startup's exact thresholds will vary, but these conditions should normally trigger a hold until someone with authority resolves them:

• an employee appears or disappears without an approved source change;
• a salary, hourly rate, bonus, commission, or one-time payment lacks approval;
• a material time or leave difference is unresolved;
• a bank-account change cannot be authenticated through the approved process;
• an unexplained zero or negative net-pay result exists;
• a material benefit or deduction does not match the approved election;
• a large variance from the prior run has no explanation;
• withholding changed unexpectedly and the applicable source record cannot be confirmed;
• the funding requirement does not reconcile to the reviewed payroll outputs; or
• the reviewer and final approver cannot identify who owns an unresolved consequential exception.

Not every open item has to stop payroll. Some exceptions may legitimately be accepted for later correction. That is not permission to knowingly run incorrect employee pay or ignore a legal or tax requirement. The decision should be recorded by an authorized reviewer, with technical or jurisdiction-specific questions routed to the appropriate payroll, tax, or legal owner rather than waived because the cutoff is close.

7. Use a real release gate

At the end of the review, the approver should be able to answer each of these questions:

Population

• Are all expected employees present?
• Are all unexpected employees explained?
• Are new hires and terminations reflected according to approved effective dates?

Compensation and time

• Are salary/rate changes supported?
• Are time, leave, and one-time payments complete and approved?
• Are material variances explained?

Deductions and withholding

• Do benefit and voluntary deductions match approved elections?
• Are unusual tax-withholding changes supported or routed for review?
• Are zero or negative pay results understood?

Control and evidence

• Does every material exception have an owner?
• Is the evidence linked or stored somewhere another reviewer can inspect?
• Is the run based on a frozen source-data cutoff?
• Has someone other than the preparer reviewed consequential exceptions when staffing permits?

Funding

• Does the funding requirement reconcile to the reviewed run?
• Is the funding owner prepared for the release?

Then record one outcome:

RELEASE
No unresolved material exception prevents approval.

HOLD
At least one unresolved material exception means the run should not be released yet.

RELEASE WITH DOCUMENTED EXCEPTION
An authorized reviewer accepts a specific unresolved item, with its effect, owner, evidence, and follow-up date recorded.

The point is not bureaucratic sign-off. It is to prevent a deadline from silently becoming the decision-maker.

8. Preserve the evidence after payroll is approved

A good pre-payroll reconciliation creates a useful record of what was reviewed and approved.

Keep the reviewed register, source snapshot, exception log, and approval record according to your company's retention policy and applicable requirements. For federal employment-tax records, the IRS says employers should generally keep relevant records for at least four years after filing the fourth-quarter return for the year. The IRS lists records such as wage payments, employee data, Forms W-4, deposits, returns, benefits, and reimbursements. See IRS employment-tax recordkeeping guidance.

That federal rule is not the only retention requirement that may apply. State employment rules, benefit-plan records, company policy, litigation holds, and other requirements can create different or longer obligations.

9. Keep pre-payroll reconciliation narrow

This checklist is deliberately limited to the period before payroll approval.

Do not turn it into a catch-all payroll compliance process.

After the run:

• use Chore's payroll tax deadlines guide for deposit and filing timing context;
• use the Form 941 and Form 940 year-end checklist for quarterly/year-end reconciliation; and
• use the W-2 filing guide for annual employee-data and wage-statement preparation.

Those are different control points. Pre-payroll reconciliation answers only this question:

Does the proposed run match the approved inputs closely enough that an authorized person can release it?

Use the control sheet on your next pay run

The easiest way to make this repeatable is to keep the review in one record rather than in Slack messages, payroll comments, and memory.

The accompanying Pre-Payroll Reconciliation Control Sheet includes six sections:

1. Run Control
2. Source-of-Truth Map
3. Employee Change Diff
4. Register & Variance Review
5. Exception Register
6. Approval Gate

Use it on one real payroll, then adjust the fields and hold rules to match your systems, jurisdictions, and approval structure.

If the exercise shows that no one internally owns source mapping, exception follow-up, or independent approval, that is an operating-design problem, not merely a payroll-software problem. Use the control sheet to define the exact support you need, then evaluate Chore or another provider against its current, verified scope rather than assuming the software or provider owns the control by default.