Outsourced EmploymentPowered by StealthAgents

Practical guide

Verify direct deposit changes before the next pay run

A verification path for bank detail changes that confirms the request, the account, and the approval before payroll sends money to a new destination.

Published

Practical guide illustration for Verify direct deposit changes before the next pay run
Table of contents

Treat every bank change as a high-risk request

Classify a bank detail change separately from an address or a phone update. The destination of the money is different from a contact detail because a mistake is hard to reverse after the pay date. The request should follow a stricter path even when it arrives from a familiar email address. Familiarity is not verification.

Record the request date, the employee, the last four digits of the old account, and the new account reference. Do not copy the full account number into the request log. The masked values are enough to identify the change and compare it with the system. The full number belongs only in the payroll platform.

Ask the employee to confirm the change through a channel that was already on file. A reply to the request itself is not independent because the requester controls that channel. A phone call to a known number or an in-person confirmation is stronger. Record the channel and the person who confirmed.

Set a rule for changes that arrive close to the pay date. A late change may need to wait for the next run unless there is a documented hardship exception. Write the rule before the situation occurs. A consistent rule protects both the employee and the payroll team.

Confirm the account without exposing it

Ask the employee to provide the new account details through the approved secure channel rather than in an email body. A secure form or the payroll portal reduces the chance that the number is copied incorrectly. The employee should be able to review the number before submitting. The channel should produce a receipt.

Use a second confirmation method for the account, such as a call back to the employee or a comparison with a voided check. A single entry can contain a transposed digit that passes every other check. The second method should not rely on the same message thread. Record which method was used.

Check the account type and the routing details against the form the employee submitted. A savings account and a checking account may have different handling. A routing number that belongs to a different institution is a warning sign. Record the check and the person who performed it.

Do not send a test deposit unless the payroll provider supports it and the employee expects it. A test deposit can confuse the pay schedule and create a second reconciliation. If a test is used, record the amount and the date. The employee should know when to confirm it.

Separate the request from the approval

Name the person who may approve a bank change and a backup for that person. The approver should be able to compare the request with the employee record and the confirmation. A manager who can approve hours may not be the right approver for bank details. The route should be specific to the risk.

Record the approval with the date, the scope, and the confirmation reference. An approval that does not name the account or the effective date is too broad. The approver should confirm that the request matches the employee and the confirmed channel. A check mark without those details is not evidence.

Require a second reviewer for a change that follows a recent personal data update. A fraud attempt often changes an address or a phone number before changing the bank account. The second review should look at the sequence, not only the final request. Record the sequence in the case note.

Tell the employee when the change is approved and when it will take effect. A confirmation message gives the employee a chance to object before the pay run. It also creates a record that the change was expected. The message should not include the full account number.

Record the system update and the pay run check

Record the payroll system update with the user, the date, and a receipt. The update should match the approved account and the effective date. A change entered in the wrong employee record is a serious error that a receipt alone will not catch. Compare the employee identifier before saving.

Check the pay run preview for the affected employee before the run is released. The preview should show the new account and the expected amount. A change that was approved but not applied will appear in the preview. Record the check and the person who performed it.

Compare the bank file or the payment instruction with the approved change. A payroll system can hold the right account while the bank file uses an old one. The comparison should be part of the pre-run checklist. Record the result and any exception.

Ask the employee to confirm the first payment to the new account. A confirmation closes the loop and catches a problem before the next cycle. Record the date and the method. If the payment failed, the record should show the correction path and the person who handled it.

Handle a suspected fraudulent request

Stop the change when the request looks inconsistent with the employee record or the confirmation channel. Do not confront the requester through the same channel. Contact the employee using the number on file and record the attempt. The payroll team should not try to resolve a suspected fraud alone.

Preserve the original message, the headers, and the request details in a restricted location. A forwarded summary may lose the information needed for an investigation. Record who accessed the case and when. The evidence should be kept according to the organization's retention policy.

Notify the payroll provider and the bank contact if money may have been sent to the wrong account. A fast notification may improve the chance of recovery. Record the time of the notification and the reference number. The employee should be told what happened and what to expect.

Keep the path usable for legitimate changes

A verification path that takes a week will push employees to ask for exceptions. Set a service target for a complete request and publish it in the employee guidance. The target should include the time needed for the independent confirmation. A clear expectation reduces pressure on the payroll team.

Give employees a way to confirm a change before the pay date without exposing their account number. A portal status or a short confirmation message is enough. The employee should know whether the change is pending, approved, or applied. A status that never updates erodes trust in the process.

Review the volume of bank changes and the reasons for late requests each quarter. A spike may indicate a payroll date change or a communication problem. A cluster of late requests from one department may indicate a manager who is not sharing the guidance. Use the pattern to improve the communication.

Sources

References supplied with this guide.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
U.S. Department of Labor, Employment Law Guidedol.govPrimary reference supplied with this article.
Internal Revenue Service, Understanding employment taxesirs.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Cybersecurity Framework 2.0nist.govPrimary reference supplied with this article.