Workplace Rights
A Payroll Change Request Looks Suspicious: Verify It Before Updating Direct Deposit
Use independent payroll and security routes to verify an unexpected direct-deposit change notice. A completed fictional notice review and incident packet separate the message claim, actual payroll record, account exposure, and payment checks still pending.
Treat an unexpected payroll bank-change request or notification as something to verify through an independent route. Do not follow its link, reply with financial details, or use its phone number to check whether it is genuine. Open the employer’s established payroll route separately and contact payroll or security through details you already trust. The message’s authenticity, the account’s exposure, and the payment destination each need their own evidence.
This LandOffer.ai guide uses a fictional employee incident packet and public primary sources checked October 27, 2026. No email was opened in an account, attachment inspected, link visited, credentials entered, payroll setting changed, or report sent. The completed examples are authored coordination records, not a real security investigation. Your employer’s reporting and incident-response process supplies the actual owners and controls.

Separate a suspicious message from an actual payroll change
A message can claim that your direct deposit changed even when nothing changed. It can also be a genuine alert about an unauthorized change. Alternatively, someone may impersonate an employee and ask payroll to redirect wages. Preserve the message and leave its proposed action unused while you check the real payroll record through an independent route.
Washington University’s documented direct-deposit notification scam describes false change notices intended to collect credentials or banking details. Its guidance directs university users to its own reporting button and established services. The article also states that WashU employees change their information themselves through Workday. That is an employer-specific example, not a rule that every payroll department everywhere lacks authority to make changes.
The FBI’s 2018 payroll-diversion alert describes stolen payroll credentials being used to redirect deposits and suppress alerts. This helps explain why “I did not receive another notice” is weak reassurance. It does not establish that a particular reader’s mailbox or payroll account was compromised. Keeping those possibilities distinct helps security investigate exposure while payroll checks the actual payment instructions.
If you administer payroll, leave an unverified request unapproved and use the employer’s established identity-verification and change-authorization process. An employee reporting a suspicious notice should not be asked to authorize a new destination merely to cancel an alleged change. Do not invent a substitute bank account as an emergency workaround or assume you personally have the authority to pause an entire payroll run.
Verify using a route the message did not provide
Use an established company application launcher, a previously validated bookmark, or the employer’s independently confirmed HRIS address. If you do not know that route, ask the help desk through a known directory entry. Avoid treating the top search advertisement as a trusted login destination simply because its title matches the payroll provider.
The FBI’s April 24, 2025 warning specifically describes fraudulent search advertisements impersonating employee self-service websites. It recommends known bookmarks or directly entering the authentic address. It also warns that a fraudulent page can capture multifactor tokens. Having MFA enabled does not make it safe to enter a code into a page reached from a suspicious notice.
Contact payroll using an established directory number or an existing internal case channel. A reply in the same email thread, an incoming caller’s claimed role, or a number pasted into the message does not create independence. If someone calls claiming to be support and asks for a password or one-time code, stop and reconnect through the verified channel. Do not share a login code to prove your identity to an unsolicited caller.
When you reach the genuine payroll record, review the current masked destination, any change history made available to you, and effective dates. Record the time and what the page actually shows. A matching current destination does not necessarily expose every pending instruction, completed payment, hidden account change, or email rule. Payroll and security may need records that employees cannot see.
The FTC’s phishing guidance similarly advises contacting a known company using a number or website you know is real rather than details in the message. Use the visible warning signs to decide to report and verify; do not turn spelling checks, a familiar logo, or the presence of HTTPS into a verdict that the message is safe.
Completed notice review: an alarming claim, an unchanged destination
All names, dates, observations, and case references below are fictional. Analyst Marin receives a notice at 9:12 a.m. Pacific on October 27. Its display name is “Payroll Operations,” and it claims her direct deposit now ends in 2910. Marin’s own expected destination ends in 7142; both endings are invented labels, not account information supplied by a reader.
The message says to open a document and confirm her employee login within twenty minutes to prevent a payroll hold. Marin has not requested a change. She does not open the document, click the link, reply, or approve a sign-in prompt. Her completed review records the claim separately from its verification:
| Item in the authored notice | What it establishes | Completed verification decision |
|---|---|---|
| Payroll display name and familiar formatting | The message presents itself as payroll | Identity remains unverified; use the known directory route |
| Claimed destination ending 2910 | The sender asserts a change | Do not accept this as a real payroll entry |
| Twenty-minute deadline and threatened hold | The sender is applying pressure | Report promptly without using the supplied action route |
| Document button requesting employee login | The sender wants an interaction | Leave it unopened; send the original through the approved reporting mechanism |
| Marin did not initiate a change | A relevant employee statement | Tell payroll explicitly; ask about current and pending changes |
At 9:20, Marin uses her previously validated company launcher to reach the genuine payroll portal. Its current masked destination still ends in 7142. She records that observation without changing anything. She cannot see an administrator’s pending-change queue and labels that part unknown. Her report does not say that the unchanged screen proves the email account is safe or guarantees the next payment’s destination.
At 9:27, a payroll representative reached through the existing staff directory confirms, within the story, that no current or pending direct-deposit change is recorded for Marin at that time. Payroll assigns case P-27 and accepts responsibility for checking the relevant upcoming run. Marin records that confirmation as of 9:27, with the upcoming-run check still assigned to payroll.
Marin’s finished decision is to leave the destination unchanged and continue the security report. This is a complete administrative outcome for the immediate request: no change is authorized, the claimed new account is unsupported by the independently checked record, and the suspicious message remains under investigation. It is not a claim of recovered money, blocked attackers, or a fully examined account.

Give security and payroll one factual incident packet
The two teams need related facts but own different questions. Security handles the suspicious communication and potential account exposure. Payroll checks destination instructions, effective dates, and payment-run status. A ticket acknowledged by one team does not show that the other has completed its part. Put the payroll case reference in the security report and the security reference in the payroll record, using the approved private channels.
Marin’s second completed asset is the following report prepared at 9:16 and supplemented after the independent checks. It is an authored private incident record; no message or file is actually sent.
| Report field | Completed example entry |
|---|---|
| Subject and receipt | Unexpected direct-deposit change notice; received October 27, 9:12 a.m. Pacific |
| Employee’s statement | I did not request or authorize a bank-destination change |
| Message claim | New destination ending 2910; document login demanded within twenty minutes |
| Interaction and exposure | No link clicked, attachment opened, reply sent, password entered, or MFA prompt approved |
| Preserved evidence | Original message submitted using the employer’s approved reporting workflow; original metadata retained for security review |
| Independent payroll observation | Genuine portal reached through existing company launcher at 9:20; current destination ends 7142; pending queue not visible to employee |
| Payroll confirmation | Directory callback at 9:27; P-27 reports no current or pending change as of that check; upcoming-run review owned by payroll |
| Security reference | S-44 acknowledged at 9:35; message analysis and relevant account review pending |
| Requested next update | Ask payroll and security to state their findings and remaining actions by 11:00, or provide a revised update time |
The update time is a coordination request in this example, not a universal incident-response guarantee. The packet includes masked endings to distinguish the claim from the known record, without distributing full routing or account numbers. If a team needs sensitive evidence, supply it only through its designated private process. Do not forward the suspicious message to coworkers as an interactive warning or ask someone else to test its button.
In the fictional 10:10 security update, S-44 classifies the notice as phishing based on its review of the original message. That finding belongs to the story; this article has not performed that analysis. The update also says relevant account review remains pending. Marin records “message classified; account review open” rather than converting a phishing classification into proof that no account was accessed.
Payroll’s upcoming-run review is also unfinished. The report therefore retains two named owners and two unresolved checkpoints. Marin has finished the immediate verification and reporting work while leaving final account scope and payment-run findings open. The closeout keeps those remaining checks visible instead of labeling the entire incident resolved.
If you already interacted, change the response branch
The no-interaction case above should not be reused unchanged if someone entered credentials, downloaded a file, approved a prompt, or saw an unfamiliar destination in the real payroll portal. Tell the responsible team exactly which interaction occurred and when. “I clicked but entered nothing” differs from “I entered my password and a code.” If you are uncertain whether a submission completed, say so rather than assuming it failed.
Use the organization’s verified incident route promptly and follow its account-recovery instructions through the genuine service. A password reset alone should not be treated as a complete investigation: security may need to assess sessions, access methods, or message rules, and payroll must independently check bank instructions and payment exposure. Do not reopen the suspicious page to determine whether it still works or to retrieve an apparent confirmation number.
USAID OIG’s June 14, 2024 advisory recommends independent telephone verification and warns against links, attachments, and phone numbers supplied by unsolicited account-change messages. Its agency reporting route is specific to that organization. A private-sector employee should use the employer’s actual security and payroll contacts rather than send personnel information to an unrelated agency mailbox.
If an actual unauthorized payment or financial-account change is identified, contact the relevant payroll organization and financial institution through verified channels promptly. The FBI’s 2025 notice discusses requesting a recall or reversal and reporting fraud to IC3; those are requests for assistance, not guarantees that a payment can be stopped or funds recovered. Record who owns that request and what status has actually been confirmed.
Close the verification, account, and payment questions separately
A useful closeout distinguishes the notice’s authenticity, whether credentials or a device were exposed, whether payroll instructions changed, and whether a payment was released or received. Some questions may close sooner than others. Keep the original timestamps and case references when adding later findings so an old “unchanged” observation is not mistaken for a permanent state.
If the request turns out to be legitimate, resume only through the normal authorized change process. Independent verification does not authorize skipping required identity checks, approvals, or effective-date rules. If it is malicious, follow security’s preservation and removal instructions after the report; do not keep an actionable copy circulating in a team channel.
Return to LandOffer.ai for more current-work guides. For this situation, the next action is concrete: leave the message’s proposed route unused, reach payroll and security independently, and record the message’s claim, any interaction, each team’s confirmed findings, and the owner of every remaining check.


