Reviewed October 16, 2026. This guide explains payroll records; examples are fictional and are not individual tax or legal advice.
A paystub describes an individual payment. A payroll register typically summarizes a payroll run across employees. Comparing them is an employer control: it helps detect missing statements, wrong versions, and amounts that do not agree before an unexplained difference becomes harder to trace.
Compare records from the same run
Start with the pay date, period covered, run identifier, and processing status. A preview register and a finalized paystub may legitimately differ if changes were made between versions. Mark whether the run is regular payroll, an off-cycle payment, a correction, or a reissue.
The Department of Labor’s recordkeeping guidance identifies wage, hours, deduction, payment-date, and pay-period information employers must retain for covered workers. It does not prescribe this particular reconciliation worksheet. The workflow below is a practical review method, not a substitute for the applicable recordkeeping requirements.
Match each employee before totaling the run
Use an internal employee identifier and payment reference in a protected working file. Match the correct statement to the corresponding register row. Confirm gross cash earnings, applicable taxable-wage columns, employee taxes, deductions, reimbursements, and net payment using the same definitions on both reports.
Do not expect every report’s “gross” column to mean exactly the same thing. A register may separate taxable noncash benefits or reimbursements while a statement groups them differently. Write down the mapping once and use it consistently rather than forcing unlike totals to agree.
A simple control-total example
Imagine three finalized statements with net payments of $720, $845, and $935. The net-pay control total is $2,500. If the matching register also reports $2,500, that specific total agrees. It does not prove that hours, tax calculations, employee allocation, or payment delivery are correct.
If the bank funding amount is larger, identify employer taxes, payroll-service charges, or other separately funded items before treating the difference as an error. Conversely, a matching withdrawal does not prove each employee received the correct payment. Trace payment status and exceptions separately.
A worked gross-to-net reconciliation
Use one row per employee and payment reference. This simplified example has no reimbursements or noncash benefits; “deductions” combines employee taxes and other employee deductions. These are fictional control amounts, not calculated tax estimates.
| Employee | Gross pay | Deductions | Net pay |
|---|---|---|---|
| A | $1,000 | $280 | $720 |
| B | $1,100 | $255 | $845 |
| C | $1,200 | $265 | $935 |
| Total | $3,300 | $800 | $2,500 |
First match every row to its register entry: $1,000 − $280 = $720, $1,100 − $255 = $845, and $1,200 − $265 = $935. Then check the control totals: $3,300 − $800 = $2,500. Compare each tax and deduction category separately where the reports provide that detail.
Why a matching grand total can hide an error
A register showing $770 for A, $795 for B and $935 for C still totals $2,500. A has $50 too much and B has $50 too little. The run total passes, but the employee-level comparison fails. Resolve the source records before approving the run; do not move amounts between employees merely to make a total agree.
Trace the payment after the payroll records agree
Match the net-pay obligation to the payment method and reference. Split deposits may need multiple transactions to equal one statement’s net pay. A rejected deposit, uncashed check, void or reissue needs its own status review. Reissuing a payment is not automatically a second set of earned wages; verify the payroll system’s void and YTD treatment.
For each exception, record the employee reference, pay date, expected amount, reported amount, difference, source evidence, owner, resolution and reviewer. Keep this worksheet in a restricted location. Follow the pay stub correction process when a statement or payroll entry needs correction.
Keep an exception log
- Missing statement: confirm whether the employee was paid in another run.
- Different gross amount: compare approved hours, rates, and earning codes.
- Different net amount: inspect deduction and reimbursement mappings.
- Duplicate payment reference: establish whether it is a void, reissue, or actual duplicate.
- Year-to-date difference: check the prior balance and any correction history.
Give each exception an owner, explanation, and resolution date. Do not overwrite a mismatched value merely to make a spreadsheet balance. Keep the evidence supporting the correction.
Close the review without losing the audit trail
Save the finalized register, issued statements, approvals, and payment confirmation in the appropriate restricted records system. Retain superseded versions with clear labels when needed for the correction history. Follow applicable retention rules; this workflow does not establish a universal retention period.
For a small business, even a brief independent second review can catch a wrong employee or pay period. If only one person runs payroll, a consistent written checklist and documented follow-up are still more useful than checking the bank total alone.
Sources and further reading
For the fields on a single statement, see the annotated pay stub example.
Related paystub guides
- Check an individual paystub for accuracy
- Organize employer payroll records
- Preserve a correction history
Prepare a paystub from accurate payroll records
When you have verified the payroll figures, open the PayStubPro generator to format your document. Basic pay stubs cost $1 each. W-2 and 1099 forms cost $9.99 each. A generated document does not prove payment or guarantee acceptance. Explore the paystub guide and payroll resource library for related help.