Payday is a promise. Your people did the work, and on a specific morning, the money needs to be in their account. When it is not, nothing else you do that day matters. The employee standing at your desk does not care that 340 other deposits landed fine. Their rent check is bouncing, and payroll is the reason.
Most direct deposit failures are preventable. They trace back to a handful of causes: account information entered wrong at setup, a bank change processed without verification, a returned deposit nobody caught in time, or a fraudster who emailed HR pretending to be an employee. Every one of those has a straightforward defense, and ADP gives you the tools to build them.
This post covers the full life of an employee's pay delivery: getting direct deposit set up cleanly, using prenotes wisely, handling split deposits, offering pay cards so unbanked employees are not stuck waiting on paper checks, protecting yourself from bank-change fraud, recovering when a deposit comes back, and getting final checks right when someone leaves. None of it is glamorous. All of it is the difference between payday being a non-event and payday being a crisis.
Almost every direct deposit failure starts at setup. A transposed digit in an account number, a routing number from a closed branch, a savings account entered as checking. The deposit file goes out clean from your side; it just goes to the wrong place.
The strongest defense is making employees enter their own banking details through self-service instead of handing paper forms to someone who retypes them. Self-service entry removes the transcription step, which is where most digit errors are born. When employees enter their own information, they are also looking at their own checkbook or banking app, not deciphering someone's handwriting.
When you do have to key banking details manually, work from a voided check or a bank-issued direct deposit form rather than numbers read over the phone. Read the routing and account number back. And build a habit of confirming the account type, because checking-versus-savings mismatches cause a surprising share of returns.
One more setup discipline: watch your first-payment expectations. If a new hire's banking details arrive after your payroll cutoff, that first check may need to be paper or pay card. Tell them that during onboarding, not on payday. Most "my deposit is missing" calls from new hires are really "nobody told me the first check works differently" calls.
A prenote is a zero-dollar test transaction sent to an employee's bank account before real money moves. At a general level, it verifies the routing and account numbers can actually receive a deposit. If the prenote bounces, you find out with zero dollars at stake instead of a full paycheck.
Prenotes come with a trade-off: they take time to clear, which usually means the employee's first check or two arrives as a paper check or pay card while the test runs. Some employers skip prenoting to get people on direct deposit immediately, accepting the risk that a bad account number surfaces as a returned live deposit instead of a returned test.
There is no single right answer, but there is a right way to decide: make it a policy, not an accident. Know whether your ADP setup prenotes new accounts, know how long the window runs, and make sure onboarding communication matches reality. The worst version is the accidental one, where nobody remembers what the setting is and every new hire's first payday is a surprise, including to you.
Employees increasingly want their pay split across accounts: a fixed amount to savings, the remainder to checking, maybe a slice to a joint account. ADP supports multiple accounts per employee with fixed amounts, percentages, and a remainder account that catches whatever is left.
Splits are a great benefit, and they add failure modes worth knowing. The classic one is the missing remainder: an employee sets $200 to savings and $1,800 to checking, then gets a raise, and the extra money has no home unless a remainder account is defined. Always ensure one account is set to catch the balance. The second classic is the stale split: an employee closes their savings account, forgets the $200 split exists, and that slice starts bouncing while the rest of the check lands fine, which makes for confusing troubleshooting.
Encourage employees to review their deposit setup whenever they change banks, and check split configurations when returns come in. If only part of a paycheck bounced, a split is almost always the reason.
Some portion of the workforce has no bank account, and in industries like hospitality, retail, and light industrial, it can be a meaningful portion. Paper checks are the default answer, and they are a bad one: employees pay check-cashing fees, checks get lost, and you carry the cost and headache of printing, distributing, and escheating stale checks.
Pay cards solve most of that. At a general level, a pay card is a reloadable card that receives wages electronically, giving an unbanked employee the reliability of direct deposit without a bank account. Funds land on payday, replacement is possible if the card is lost, and there is no check to cash.
Two cautions. First, pay card rules vary by state, including requirements around employee consent, fee disclosure, and the employee's ability to access full wages without cost. Pay cards generally must be an option employees choose, not a requirement you impose. Confirm your state's rules with your advisor before rolling out. Second, do the rollout as communication, not just configuration: explain fees, show employees how to check balances, and make opting in easy. A pay card program nobody understands is a pile of plastic in a drawer.
Here is the scam, because every payroll team needs to recognize it. Someone emails HR or payroll from an address that looks like an employee's, often a plausible personal Gmail: "Hi, I changed banks. Can you update my direct deposit before this payroll? New account below." The writing is polite and unremarkable. The account belongs to a criminal. If you make the change, the employee's next paycheck disappears into an account that is emptied within hours, and recovery is rare.
This is one of the most common payroll frauds in the country, and the defense is procedural, not technical. Adopt a hard rule: no direct deposit change is ever processed from an email request alone. Either the employee makes the change themselves through self-service with their own login, or you verify the request by contacting the employee through a known channel, meaning a phone number already on file or a face-to-face conversation. Never verify by replying to the requesting email; you would be asking the fraudster to confirm their own scam.
Then add friction where it protects people: alert employees whenever banking details change on their record, and consider holding a change made shortly before payday for extra verification. A one-payday delay on a suspicious change is a minor inconvenience. A stolen paycheck is a disaster, and depending on the circumstances, it may be your organization making the employee whole.
Even with clean setup, deposits come back. Accounts get closed, banks merge and retire routing numbers, and typos slip through. A returned deposit means the money left you and came back, and an employee is now unpaid.
Speed is everything. Make sure someone owns monitoring for returns every cycle, because a return nobody sees for three days is three days an employee goes without pay. When a return lands, contact the employee the same day, get corrected banking details through your verified process, and get money moving again, whether that is a corrected deposit, a pay card load, or a same-day check depending on what your setup supports and how urgent the situation is.
Then close the loop: fix the underlying record so next payday does not repeat the bounce, and log the cause. If returns cluster around manual entry or a particular onboarding path, that pattern is telling you where to tighten setup.
When employment ends, pay delivery gets stricter. Many states regulate final-pay timing, and the deadlines can be short, sometimes the same day for involuntary terminations in certain states. Direct deposit timing does not always fit those windows, which is why some terminations require a live check handed over or delivered rather than a normal deposit cycle.
Build a final-check checklist that includes delivery method and deadline by state, whether the employee's direct deposit remains appropriate for the final payment, and what happens to any pay card balance. Also decide in advance how you handle deposits that would land after a termination date, so nobody is improvising reversals. Final pay is a moment when a departing employee is most likely to call a lawyer or a state agency if something is wrong, so this is the paycheck to get exactly right, on time, every time. Confirm your state's specifics with your advisor; the rules vary widely.
A client with roughly 150 employees processed a direct deposit change from an email that appeared to come from a warehouse supervisor. The email arrived two days before payroll cutoff, used the supervisor's real name, and asked to route pay to a new account. The coordinator, moving fast on a busy day, made the change.
On payday, the real supervisor reported no deposit. The money, about $2,400 net, had landed in a fraudster's account and was withdrawn within hours. The bank recovery attempt failed. The client paid the supervisor again out of pocket, so the incident cost roughly $2,400 plus about 15 hours of staff time on bank calls, a police report, and cleanup.
The fix cost nothing: a written rule that banking changes happen only through employee self-service or a callback to the phone number on file, plus automatic alerts to employees when banking details change. In the following year, the client turned away four similar phishing attempts. Four paychecks saved by one procedure.
It depends on your state. Some states allow mandatory direct deposit with conditions; others require employee consent or an alternative like a pay card or paper check. Set your policy against your state list, and confirm with your advisor before making anything mandatory.
Plan around your payroll cutoff and any prenote window. Details entered after cutoff generally wait for the next cycle, and a prenote adds a test period. Tell new hires their first check may arrive differently, and you will prevent most payday confusion.
Freeze further changes to that record, verify with the employee by phone, and if money already moved, contact your bank and ADP service resources immediately to attempt recovery, then file the appropriate fraud reports. Hours matter far more than days.
Reliable pay delivery is a system, not luck. Employees own their banking details through self-service. Prenote behavior is a documented policy, and onboarding sets first-check expectations honestly. Every split configuration has a remainder account. Unbanked employees have a pay card option that was explained, not just offered. Banking changes require verification through a known channel, no exceptions, even for executives, especially for executives. Someone owns return monitoring every cycle, and final checks follow a state-aware checklist. When that is all true, payday goes back to being quiet.
If payday at your company is not quiet, Ignite HCM can get you there. We are former ADP service professionals who work exclusively with ADP clients, and we have configured, cleaned up, and fraud-proofed pay delivery for companies of every size. No tickets, no hold queues — a dedicated consultant who knows your setup and answers when you call. Your people need to get paid. We make that happen.
Want every payday to land without drama? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not legal or tax advice; confirm state-specific requirements with your licensed advisor.