Direct Deposit

Three employees didn't get paid on Friday. The payroll run didn't fail; their direct deposit information was wrong in the system. One had a closed account, one had a transposed routing number, and one simply hadn't submitted banking details yet. Payroll processed correctly. The payment failed downstream. Direct deposit is the electronic transfer of net pay from an employer's bank account directly to an employee's bank account through the Automated Clearing House (ACH) network. It is the dominant payroll disbursement method in the United States, used by more than 93% of employers. The appeal is simple: funds are available on payday without physical checks, manual distribution, or lost envelopes. But direct deposit guarantees only that a payment instruction was submitted, not that the payment arrives. If the banking data is wrong, the routing number is invalid, the account is closed, or the employee hasn't provided banking information at all, the instruction fails after the payroll run completes. The gap between a successful payroll run and a successful payment is where most direct deposit problems sit, and where payroll teams lose payday.

How direct deposit works

When a payroll run completes, the payroll platform produces an ACH file: a batch of payment instructions specifying the originating account, the receiving account (employee bank routing and account numbers), the payment amount, and the effective date. That file goes to the employer's bank, which acts as the Originating Depository Financial Institution (ODFI). The ODFI sends the file through the ACH network to each employee's Receiving Depository Financial Institution (RDFI). Under standard ACH timing, the file is typically submitted two banking days before payday so funds settle on the effective date. Same-day ACH is available for an additional fee and allows same-day settlement for files submitted by the RDFI's cutoff window, typically early afternoon. Problems show up at the RDFI stage. If an account is closed, the RDFI returns the item, usually within two banking days, with a return code giving the reason. If the routing number is wrong or the account doesn't exist, the return comes back faster. The employer then has a returned ACH item: the payroll run succeeded, but the employee has no funds. Most payroll platforms notify payroll administrators of ACH returns within 24 to 48 hours of the effective date, but by then the employee's payday has passed. Prenote verification catches bad banking data before a live payroll: a zero-dollar test transaction is sent to the employee's account at least one payroll cycle before the first live payment to confirm that the account is active and the routing and account numbers are correct. Skipping prenote for new employees or direct deposit changes is the most common cause of preventable payday failures.

Where it gets complicated

The damage from a returned ACH item is out of proportion to the effort it takes to prevent one. When an item returns, payroll teams have several things to do at once: notify the affected employee, issue a replacement payment (often a paper check or a live payroll correction run), reconcile the returned funds back to the employer's bank account, and fix the banking data so the error doesn't repeat next cycle. If the return comes back the day after payday, the employee has been without pay for at least 24 hours and, depending on the replacement method, may wait several more days. Paper checks take time to print, sign, and deliver. Same-day ACH corrections are possible but need correct banking data already on file. The impact on the employee is significant: late pay causes knock-on problems in their personal finances, and in some states late payroll carries employer penalties. The structural problem is that most payroll teams don't learn about a returned item until it has already failed. Prenote moves that failure to a zero-dollar test transaction that costs nothing to fail. But prenote only works if it is enforced, and many payroll platforms let administrators bypass it for speed, particularly during high-volume onboarding. That bypass is where the Friday payday crisis starts.

How platforms handle it

In a typical payroll platform, the employee submits banking information through a self-service portal, or the payroll administrator enters it manually. Better platforms require prenote verification by default and keep the employee on paper check or manual payment until the prenote clears. When an ACH item returns, the platform receives a return file from the ODFI, marks the employee's payment as returned, and alerts the payroll administrator, usually by email or a dashboard flag. The alert includes the return reason code (R02 for closed account, R03 for no account found, R04 for invalid account number, R10 for customer advises not authorized, among others). The administrator then has to decide whether to resubmit after correcting the banking data, issue a paper check, or run an off-cycle payroll. Platforms that build returns into the payroll workflow, prompting the administrator to update banking information before the next cycle instead of just flagging the error, noticeably reduce repeat failures. The weakest implementations simply log the return and leave resolution to the administrator, which sets up the same employee to miss the next payroll too.

Questions to ask about your direct deposit setup

• Does your payroll platform enforce prenote verification for all new direct deposit setups, or can administrators bypass it?
• What is your process when an ACH return comes in on payday? Who is notified, and what is the fastest replacement payment path?
• How are employees set up for direct deposit during high-volume hiring periods? Is there a quality check on banking data before the first payroll cycle?
• Do you have a policy requiring employees without banking information on file to be contacted before the payroll cutoff date?
• Are returned ACH items reconciled against the employer bank account on the same day they are received, or does that reconciliation lag?
• If you use same-day ACH for corrections, what is your bank's submission cutoff window, and who is responsible for initiating the correction file?

Where direct deposit programs fail in practice

The most common failure is not running prenote verification on new bank accounts before the first live payroll. It often gets skipped because the employee was hired close to a payroll cutoff, the administrator wanted to avoid issuing a paper check for one cycle, or the platform allowed the bypass without friction. The result is a predictable returned item on the first payroll. The second most common failure is having no defined process for handling returned ACH items on payday itself. When a return comes in at 9 a.m. on Friday and the payroll team learns about it from an automated email, the clock starts on an employee who has no pay. If the resolution path (who decides whether to issue a check vs. resubmit, who prints and signs the check, who notifies the employee) isn't defined before an incident, the fix is slower and messier than it needs to be. A third failure is not auditing direct deposit records periodically. Employees close old accounts and forget to update payroll. The payment then returns on the first payroll after the account closes, which can be months after the change, and an annual prompt for employees to confirm their banking information is current prevents it entirely. To estimate what fewer correction cycles are worth, try the payroll software savings calculator.

What controls the timing

The pay date is not the send date. Payroll files are submitted to the bank ahead of the pay date, and the funds post on the settlement date the file specifies. That is why the same employer can pay everyone on the same day and employees at different banks see the money at different hours. Missing the bank's submission cut-off, not the payroll run, is what delays a pay date.

Comparing payroll platforms

Payroll platforms separate on filing coverage: which jurisdictions the vendor files in itself, and which ones it hands back to you. Once direct deposit is settled as a requirement, read the Payroll Software category guide for how the market splits, then weigh the Gusto profile against the Rippling profile on that requirement rather than on the feature list. No head-to-head comparison is published in this category yet, so the profiles listed in the Payroll Software guide are the place to compare. Before you book demos, put your own numbers through the payroll savings calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

Related terms

Gross Pay vs Net Pay, Overtime Calculation, and Pay Period come up in the same workflow as direct deposit, and the rest of the payroll platforms cluster is indexed in the finance operations glossary.