Reviewed October 16, 2026. Examples are fictional and illustrate record review, not individual tax or legal advice.
A bank transaction shows money arriving in one account. A paystub explains a payroll payment. When the two numbers differ, start by identifying which transactions belong to the same payroll run before assuming an earnings error.
Start with the exact payment
Find the payment date, pay-period dates, employer, and statement version. Avoid comparing a current paystub with last period’s deposit or a pending bank transaction. If payroll issued a replacement, ask which statement and payment are final.
Add all destinations
A split deposit can send a fixed amount to savings and the remainder to checking. In a fictional example, net pay of $1,250 is distributed as $200 to savings and $1,050 to checking. Comparing only checking creates an apparent $200 shortfall even though the two deposits reconcile. Use the payroll allocation confirmation, not a guess based on past behavior.
Keep reimbursements and reversals separate
An expense reimbursement may arrive separately from wages. A corrected payroll may also involve a reversal and replacement. List each transaction with its date, amount, and purpose; do not add every employer-labelled bank entry together without checking the payroll record.
Use a simple reconciliation
Write down the statement’s net pay, each matching deposit, and any remaining difference. If deposits total $1,200 against $1,250 net pay, the unresolved difference is $50. That arithmetic identifies the question; it does not prove the cause. Ask payroll whether there was an allocation, return, replacement, or separate payment.
Document the difference before requesting a correction
For the $1,250 example, use three lines in your working note: statement net pay $1,250; confirmed matching payments $1,200; unresolved balance $50. Record the pay date, payment reference, destination labels and whether each transaction is pending, posted, returned or replaced. Mask full account numbers.
What if the deposit is pending or returned?
A pending entry is not the same as a completed payment. Ask payroll for the payment status and reference, and ask the bank about the specific transaction when needed. Do not assume a universal arrival time or create a replacement statement to imply that a payment succeeded.
What if a reimbursement arrived separately?
If the $1,250 wage payment is accompanied by a separate $75 expense reimbursement, the bank may show $1,325 across the relevant transactions. Reconcile the $1,250 to the wage statement and the $75 to its reimbursement record; do not change net wages to $1,325 merely to match the combined deposits.
What if the statement itself shows zero net?
Use the zero-net-pay review guide to establish whether cash was expected. For a payroll entry or statement error, follow the correction process. For an employer-wide review, compare the statements and payment records with the payroll register.
What to send payroll
Provide the pay period, payment date, expected net amount, and the relevant transaction amounts. Mask unrelated bank activity and full account numbers. Ask for the disbursement breakdown and an explanation of any remaining difference. Preserve the original statement while the issue is investigated.
Do not rewrite the stub to match the bank
Changing a PDF does not fix a failed payment. If the underlying payroll is wrong, use the employer’s correction process and retain both versions. If payroll is correct but delivery failed, the payment needs to be resolved separately.
Sources and related guidance
The practical workflow above should be used with the rules that apply to the employee and payroll arrangement.
Continue your payroll review
State paystub requirements · All payroll guides · Free payroll tools
Prepare a paystub from verified payroll records
Use the PayStubPro generator to format accurate payroll information. Basic pay stubs cost $1 each. W-2 and 1099 forms cost $9.99 each. A generated document does not establish that wages were paid or guarantee compliance or acceptance.
