Direct answer
For California private skilled nursing employers, direct deposit and payroll cards can be used only on a voluntary, employee-choice basis; they cannot be mandatory, and final pay needs separate handling. ePeople helps operators organize the proof inside the workflow, but the controlling rules come from California DLSE guidance and federal Regulation E.
Key takeaways
- A California private SNF may use direct deposit only if the employee voluntarily authorizes deposit into an account of the employee's choice.
- A payroll card is not automatically unlawful in California, but the program should stay optional, specifically authorized, and designed so employees can access full wages without a discounting problem.
- An employer cannot require an employee to open an account with a particular institution as a condition of employment under federal Regulation E.
- At separation, an employee's prior direct-deposit setup does not automatically carry final wages; the employer must still satisfy California final-pay timing rules and any final-pay deposit must be voluntarily authorized.
- The safest proof set is the signed election, the available alternatives, card or account disclosures, wage-statement delivery proof, payroll records, and timestamped final-pay evidence.
What is the basic California rule for paying SNF employees by direct deposit?
For a California private skilled nursing employer, direct deposit works only through the Labor Code section 213(d) path reflected in DLSE guidance: the wages go into an account at a bank, savings and loan, or credit union of the employee's choice, and the employee must voluntarily authorize the deposit. That means payroll convenience is not enough by itself. If the file does not show a real employee election, the workflow is weak before any final-pay issue even starts.
Can a California SNF require direct deposit or force a payroll card?
No operator should build its process around a mandatory employer-selected account. California's direct-deposit rule is framed around the employee's choice and voluntary authorization, and federal Regulation E separately bars an employer or other person from requiring a worker to establish an account with a particular institution as a condition of employment. In practice, a skilled nursing facility should offer a real alternative and preserve proof that the employee made the selection rather than being routed into the employer's preferred setup by default.
Are payroll cards legal for California private skilled nursing employers?
Yes, but only in a narrower way than many payroll teams assume. DLSE's payroll-card opinion does not treat every payroll card as unlawful, and it does not give blanket approval to every vendor model either. The opinion treats the reviewed programs as another way to receive wages by direct deposit because participation was optional and the employee voluntarily and specifically authorized it. That makes payroll cards a facts-and-proof question, not a simple yes-or-no checkbox.
What features make a payroll-card program risky under California wage-payment rules?
The biggest California risk is discounting wages in practice. DLSE's approval analysis relied on a program design that gave employees immediate and free access to wages in full on payday, including at least one free transaction per pay period. If an employee has to pay a fee just to reach the wages, or can reach only part of the money without cost, the program starts colliding with California's rule that wages must be payable in cash on demand without discount. A skilled nursing operator should therefore review the actual fee schedule, access network, withdrawal rules, and timing of funds availability rather than relying on a vendor sales summary.
California private SNF payroll-method control table
| Workflow step | Rule to meet | Proof to retain | Common failure mode |
|---|---|---|---|
| Onboarding election | Employee chooses the payment method voluntarily | Signed or electronic authorization, date, version of form, and alternative options shown | One default form steers everyone into direct deposit or a card |
| Account or card setup | Direct deposit goes to an account of the employee's choice; payroll card enrollment stays optional | Account-change request, specific card authorization, disclosure packet | HR treats orientation completion as consent |
| Recurring payroll | Employees can receive wages without an unlawful discounting problem | Vendor fee schedule, access instructions, proof of fee-free full-wage access | Card fees or withdrawal limits prevent full access on payday |
| Wage statements and records | Payment method does not replace itemized wage statements or payroll records | Pay-stub delivery proof, payroll registers, employee record retention | Team assumes paperless pay means section 226 duties are finished |
| Offboarding final pay | Prior direct deposit does not automatically carry final wages at separation | Final-pay election if used, time of discharge or quit, payment timestamp | Termination processed through normal payroll cycle without checking final-pay rules |
What changes when an employee quits or is terminated?
This is where otherwise clean payroll setups often fail. DLSE says direct deposits previously authorized by the employee are immediately terminated when the employee quits or is discharged unless the employee has voluntarily authorized that deposit for final wages and the employer still complies with California's final-pay rules. So a routine recurring-pay authorization is not enough for separation pay. Payroll and HR need an offboarding checkpoint that asks a separate question: can final wages lawfully go this way, on this timeline, with this proof?
Why does final pay create more exposure than ordinary payroll?
Because the payment-method mistake can turn into a timing violation. If a facility sends final wages through the ordinary payroll process without confirming the employee's final-pay authorization and the required California timing, the issue is not just paperwork. DLSE explains that employees may pursue wage claims, and waiting-time penalties can be measured at the employee's daily rate of pay for up to 30 days when final wages are not timely paid, subject to the good-faith-dispute limits. In other words, the wrong delivery workflow can become a penalty problem fast.
What proof should payroll and HR keep in the employee file?
The safest file is built to answer four questions later: Did the employee have a real choice? What exactly did the employee authorize? Could the employee access the wages in full without an unlawful fee barrier? What happened at separation? A California private SNF should keep the election form, any later change form, the card or account disclosure packet used at enrollment, proof of wage-statement delivery, payroll records, and timestamped final-pay documentation. If a payroll card is offered, retain the fee schedule and access instructions that were in effect when the employee enrolled, not just the current vendor webpage.
- Initial payment-method election and any revised election
- Evidence that another lawful payment path was available
- Specific payroll-card authorization if a card program is used
- Vendor disclosures, fee schedules, and access instructions used at enrollment
- Itemized wage-statement delivery proof
- Payroll registers and underlying payroll records
- Quit or discharge date and time
- Final-pay authorization if final wages were deposited electronically
- Timestamped proof of when final wages were issued
How should a California SNF set up the onboarding forms?
Start with a form that reads like a real choice, not a preselected funnel. Separate the available methods clearly. If direct deposit is offered, identify that the account is the employee's choice and the authorization is voluntary. If a payroll card is offered, use a distinct authorization rather than burying it inside a general onboarding packet. Skilled nursing operators should also keep version control on the form set, because a later dispute often turns on what language the employee actually saw when enrolling.
How should operators audit an existing payroll-card or direct-deposit process?
Audit the workflow in the order an investigator or plaintiff's counsel would test it. First, pull a sample of active files and confirm there is a signed or electronically attributable election. Next, compare the form language to the actual process: does the facility truly offer choice, or does staff tell new hires that only one method is available? Then test the vendor design itself. Can an employee reach full wages on payday without a fee problem? Finally, trace a few recent separations and verify that final-pay handling did not simply inherit the ordinary payroll setup.
- Review onboarding scripts, not just forms
- Check whether the payroll system defaults every new hire into one method
- Confirm who owns the final-pay decision at separation
- Compare the current vendor program to the fee and access assumptions in DLSE's opinion
- Verify that wage statements and payroll records are still complete when pay is paperless
Where do skilled nursing operators usually get this wrong?
The common misses are operational, not theoretical. One is treating payroll cards as automatically approved because a vendor serves healthcare employers. Another is assuming employee use equals employee choice even when the orientation process pushed only one path. A third is forgetting that section 226 wage-statement duties and payroll-record duties continue even when wages are delivered electronically. The last, and usually the costliest, is letting offboarding ride the normal payroll rails instead of stopping for a final-pay review.
How does this connect to other California payroll controls a SNF already manages?
This topic sits inside the same payroll-control cluster as regular paydays, final pay, wage deductions, and personnel and payroll record requests. The point is not to memorize one payment-method rule in isolation. It is to make sure the form, the payroll system, the offboarding process, and the retained proof all tell the same story when a wage claim, audit request, or internal cleanup starts.
How can ePeople help without turning a payroll policy into a legal shortcut?
The useful role for ePeople is workflow discipline, not substitute legal judgment. In a labor-law process, ePeople can be used to surface missing authorizations, route a separation-pay exception before payroll closes, and keep the proof set attached to the employee record rather than scattered across email and a vendor portal. That is especially useful in skilled nursing, where payroll, HR, staffing, and unit-level leaders are often moving too quickly to catch a payment-method exception by memory alone. The policy still needs to track DLSE and federal rules; the operational win is catching the missing step before it becomes a claim.
