This is the story of an ABA practice owner who went looking for something most vendors quietly refuse to own: help staying on the right side of labor law. We've kept them anonymous, but what they found when they started asking will surprise a lot of owners — and the exposure it points to is bigger than most realize.
The discovery: the buck stops with the owner — even when payroll is outsourced
The owner assumed, reasonably, that their payroll provider had labor-law compliance covered. So they asked. Then they asked another. The answer, in different words each time, was the same: payroll services process pay — they do not take responsibility for whether the practice is complying with wage-and-hour and other labor laws. That responsibility stays with the employer.
Once you understand how payroll services work, it makes sense. They calculate pay from the hours you give them — so a paycheck is only ever as accurate as the hours you hand over, and getting those right is your responsibility, legally. The provider that runs the paychecks is not the party on the hook if the underlying hours, overtime, or recordkeeping are wrong. The owner is — and under wage-and-hour law, owners and managers can be held personally liable, with penalties, back pay, and liquidated damages that can double what was owed.
And once the math goes wrong, it goes wrong in a way that's wildly out of proportion to the original mistake. Wage-and-hour exposure rarely arrives as one tidy bill. It stacks: underpaid hours or miscalculated overtime become back pay, which the law can double as liquidated damages; penalties frequently attach per employee, per pay period; and because the lookback can reach back years, a single small error gets multiplied across the whole roster and across every pay period in that window — a tiny mistake quietly compounding into a very large number; one underpaid tech can become a class or collective action that sweeps in everyone; and in most wage suits the employer also pays the other side's attorneys' fees on top of its own. None of it requires bad intent — just records that can't back you up.
"One wage-and-hour lawsuit can put your own lawyer's kids through college — never mind the other side's lawyers, who you end up paying too." — Practice owner
(The exact penalties, damages, and lookback periods vary by state and situation — those are questions for your own counsel. The point isn't a specific number; it's that the downside is asymmetric, and the one thing standing between you and it is the quality of your records.)
Why an ABA workforce is exactly where this gets messy
Wage-and-hour rules (the federal FLSA, plus often stricter state laws) turn on one unglamorous thing: an accurate record of hours worked. And an ABA practice is built out of precisely the staffing pattern that makes that hard:
- Hourly, part-time, high-turnover techs whose schedules shift constantly — small discrepancies, multiplied across a big roster, add up fast.
- Mobile, multi-site work. Techs move between homes, clinics, and schools. Travel time between client sites in a workday can be compensable — and it's one of the most commonly missed pieces of an hourly worker's time.
- Overtime that hides across locations and roles. A tech picking up hours at two sites, or a part-timer who quietly crosses 40 in a week, can trigger overtime the practice never saw coming — because nobody was watching the total in real time.
- Meal and rest breaks — the exposure owners forget. It's not just hours and overtime. Many states require breaks at set intervals and penalize missed, shortened, or interrupted ones — sometimes a full hour of premium pay for each break missed. ABA work makes this especially fraught: a tech can't walk away from a client mid-session, so breaks get skipped or worked through routinely. With no record of when breaks were taken or properly waived, the practice can't show they were handled right — and "we're sure they took their breaks" is no more a record than the hours are.
- Recordkeeping obligations. The law expects you to keep accurate time records and be able to produce them. "We think the hours were about right" is not a record.
(To be clear: the specifics — what's compensable travel, how overtime is calculated, what your state requires — are legal questions for your own counsel. The point here is only that all of it rests on accurate, defensible records of who worked when.)
How one of these actually unfolds — and where it's decided
Most owners have never seen one play out, which is part of why the risk stays abstract. It usually begins undramatically — a letter from an attorney requesting the time and pay records for a former employee. From those records, or the gaps in them, a claim gets built; and because the staffing pattern is identical across the team, it's often filed not just for that person but on behalf of others who don't yet know their names are on it. That's a class or collective action. From there it usually heads to mediation, not a courtroom, where each side brings an expert whose whole job is to evaluate records — how complete and contemporaneous they are, and what they imply about hours, overtime, and breaks across the roster. That assessment frames the negotiation, and the settlement number tracks, more than anything else, the strength of your records.
There's no dramatic trial here, no verdict, no finding of bad intent — it's largely a documentation exercise with a price attached, and the price is set by how defensible your records are.
What they tried first
Spreadsheets and trust. Hours were tracked loosely and reconstructed at pay periods, which made it impossible to answer the questions that actually matter: were hours captured accurately at the source, was overtime visible before it became a paycheck surprise, could the practice produce clean, complete records if a regulator or an ex-employee ever asked. The honest answer was "not really" — which, for a liability the owner personally carries, is a precarious place to sit.
How Wilma helped: fix the foundation, not the paperwork
The owner chose Wilma specifically because she strengthens the thing labor-law compliance actually rests on — accurate records and real visibility — at the source:
- Accurate time and hours captured where the work happens. Hours are recorded as sessions happen, by the mobile staff doing the work, rather than reconstructed from memory at the pay period. The record starts sound instead of being patched together later.
- Visibility before it becomes a problem. Hours and overtime are visible to leadership in real time — so a tech quietly approaching overtime across sites is something you can see and manage this week, not a surprise (and a liability) you discover after the checks have run.
- Clean records that hand off — and hold up. Wilma keeps the underlying documentation and exports clean numbers to your payroll provider (she tracks and exports to the major payroll platforms; she doesn't replace running payroll). The hours you hand off stop being reconstructed from memory and start being accurate at the source, and you have records you could actually produce if you ever had to.
"I called everyone I could. Payroll companies don't take responsibility for labor law — that's still on me as the owner. I wanted software built to actually help me carry that." — Practice owner
An important boundary — what Wilma is and isn't here
Let's be precise about this. Wilma gives you accurate records and visibility — the foundation compliance is built on. She does not provide legal advice, she does not run your payroll, and she does not assume your legal obligations. Labor-law responsibility stays with you as the employer, and you should work with qualified counsel on your specific obligations — compensable travel time, overtime calculation, your state's rules. What Wilma changes is whether you're doing all of that on solid records or flying blind. Whether the question is unpaid overtime or a missed-break premium, the answer comes from the same place — a record of what actually happened, not what everyone remembers. Good records and clear visibility are the difference between managing compliance on purpose and hoping the numbers were right.
The results
- Time and hours captured as work happens, by the people doing it — not reconstructed at pay periods
- Overtime and hours visible to leadership early enough to actually manage, not discover
- Clean, exportable records that hand off to payroll — and stand up if a regulator or ex-employee ever asks
- The owner carrying a personal liability on real records instead of trust and a spreadsheet
The names are hidden. The pattern isn't: many owners assume their payroll vendor owns labor-law compliance. It doesn't — that responsibility, and the personal exposure, stay with the employer. The records compliance depends on are yours to keep, and worth keeping well. It's the same lesson as owning your billing: the parts you can't outsource are exactly the parts worth getting right.
Frequently asked questions
Doesn't my payroll provider handle labor-law compliance?
This is the surprise that started this story. The owner called around and got the same answer every time: payroll services process pay — they do not take responsibility for whether you're complying with wage-and-hour and other labor laws. That responsibility stays with the employer, even when payroll is outsourced.
What labor-law risk am I actually exposed to?
In a practice full of part-time, hourly, often-mobile staff, the underlying records — who worked when, for how long, overtime, and meal/rest breaks — are where things get messy. It isn't only unpaid hours: many states penalize missed or interrupted breaks, sometimes a full hour of premium pay for each one, and breaks are routinely skipped when a tech can't leave a client mid-session. If hours and breaks are reconstructed loosely at pay periods, you can't confidently answer basic questions or produce clean records if you ever have to. The party on the hook for that is you, not the payroll vendor.
How expensive can a wage-and-hour mistake actually get?
Out of all proportion to the original error — which is exactly why owners underestimate it. Back pay can be doubled as liquidated damages, penalties often attach per employee per pay period, lookback periods run multiple years, one underpaid employee can become a class or collective action covering the whole roster, and in most wage suits the employer pays the other side's attorneys' fees too. As one owner put it, just one of these lawsuits can "put your own lawyer's kids through college — and you pay the other side's lawyers too." Exact figures vary by state and situation (a question for your counsel), but the downside is asymmetric, and accurate records are what keep you out of it.
What does Wilma do that my payroll service doesn't?
Wilma strengthens the foundation compliance rests on: accurate time and hours captured as work happens (not reconstructed later), overtime and hours visible to leadership early enough to manage, and clean, exportable records that hand off to your payroll provider and stand up if questions arise.
Does Wilma run payroll?
No — and that's deliberate. Wilma does time/hours tracking and exports to your existing payroll system (the major platforms). She owns the accurate records and visibility; your payroll provider still runs the actual payroll.
Is Wilma giving me legal advice on labor law?
No. Wilma gives you accurate records and visibility — the foundation compliance is built on — but she doesn't provide legal advice or assume your obligations. Labor-law responsibility stays with you as the employer, and you should work with qualified counsel on your specifics. What changes is whether you're flying blind.
How does better time tracking actually reduce my risk?
Compliance depends on records. When hours are captured as work happens and overtime is visible before it compounds, you're managing wage-and-hour exposure on purpose instead of hoping the numbers were right. Good records and clear visibility are the difference between defensible and "we think so."