Onboarding

Verifying Payroll Bank Changes During Onboarding

A control routine for direct deposit setup and changes that reduces fraud risk without slowing a new hire's first paycheck.

By OnboardingEmployees editorial team | | 3 min read

Verifying Payroll Bank Changes During Onboarding
On this page
  1. Separate setup from a later change
  2. Use the payroll system's secure entry
  3. Verify a change through a second channel
  4. Watch for urgency and unusual requests
  5. Protect the first paycheck
  6. Record the approval trail
  7. Train the payroll backup
  8. A payroll diversion example
  9. Review changes monthly
  10. Sources
  11. Related reading

Published October 27, 2026.

Separate setup from a later change

A new hire setting up direct deposit for the first time is different from an existing employee changing an account. The first can follow the standard onboarding path. A later change should trigger a stronger verification because it is a common fraud target.

Use the payroll system's secure entry

Let the employee enter the account and routing numbers directly in the payroll portal. Do not collect them in an email, a spreadsheet, or a chat. The portal should mask the account after entry and show only the last four digits in routine reports.

Verify a change through a second channel

If an employee asks to change banking details, contact them through a known phone number or in person, not through the email that made the request. Record the date, the method, and the person who confirmed. A reply to the same email thread is not independent verification.

Watch for urgency and unusual requests

A message that pressures payroll to rush a change before a pay run deserves a pause. So does a request to split deposits across several new accounts or to send funds to a third party. Treat the pattern as a reason to verify, not as proof of fraud.

Protect the first paycheck

Confirm that the direct deposit is active before the first pay run. If it is not, tell the employee how the first payment will be delivered. A missing first paycheck damages trust more than a one-cycle delay in a voluntary change.

Record the approval trail

Keep the employee's request, the verification note, the approver, and the effective date. Do not store full account numbers in the case note. If a dispute arises, the trail shows that the change followed the procedure.

Train the payroll backup

The person who covers payroll should know the verification rule and where to find the approved phone number. A backup who approves a change because the employee sounds convincing defeats the control. Include the rule in the payroll continuity guide.

A payroll diversion example

An employee emails payroll from a personal account asking to change direct deposit before the next run. The payroll specialist calls the number on file, reaches the employee, and learns the request was not theirs. The change is refused, the message is preserved, and the incident is reported under the security policy.

Review changes monthly

Count bank changes, verification methods, and exceptions. A cluster of changes shortly before payday may be legitimate or may be a pattern worth investigating. Share the aggregate with finance and security without exposing employee banking data.

  • Setup versus change
  • Secure entry
  • Independent verification
  • First paycheck check
  • Approval trail
  • Monthly review

Sources

  1. IRS Publication 15
  2. NIST SP 800-63B digital identity guidance
  3. CISA Secure Our World
  4. FTC data security guidance

Continue building the workflow

Related support: virtual assistant role brief, virtual assistant onboarding checklist. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.