One Employee, Three Departments: Time Rules, Supervisors, and Pay Rates

Most payroll systems assume a person has one job. One department, one supervisor, one set of time rules, one rate. Plenty of workplaces do not run that way.

A front desk attendant picks up shifts in childcare. A maintenance tech gets pulled to a different line for two days. A server bartends on Fridays. None of that is unusual, and none of it is complicated in real life. It gets complicated the moment somebody has to turn it into a paycheck.

Here is what actually breaks when you have employees in multiple departments, based on what HR and payroll teams describe when they go looking for something better.

Last updated: September 2026

Three departments, three supervisors, and a system that allows two

An HR director at a YMCA described the version of this that costs the most time. One employee works in three departments. Three different directors need to see that person’s time card and schedule, because each of them owns part of the week.

Her platform allowed two. For a long stretch, the answer she kept getting was that two was the limit.

So the workaround became manual. Every time staff get shared between departments, she goes into the back end and moves the department, then moves the job position, then checks back with each director to confirm they can actually see the schedule now. Her words for what happens when a manager says they are borrowing somebody: she dreads it.

That is not a reporting inconvenience. A supervisor who cannot see a time card cannot approve it, which means the approval either does not happen or happens blind.

The rules change by department, and they change mid-week

Departments rarely run on identical policies. One takes a 30 minute lunch. Another takes an hour. The time system applies an automatic deduction based on where the employee sits.

An HR manager at an animal welfare nonprofit hit the obvious problem: an employee transfers, and the lunch rule cannot be changed in the middle of a pay period. Her team manually deducts the extra 30 minutes for the affected days, every affected day, by hand.

There is a second-order version of this that is easier to miss. When that employee moved, the schedule from the old department followed them and corrupted the time card on the new team. Nobody set out to build that. It is just what happens when a schedule is attached to a person instead of to a position.

The job code is carrying more weight than anyone realizes

In a plant, the department code is not an org-chart label. It is an accounting input.

A metal powder manufacturer runs five departments, and the number is built into the employee ID. Production staff mostly stay put, so their default code is right most of the time. Maintenance is the exception, because a maintenance tech works wherever the repair is. Which system they were on determines which code their hours belong to, and those hours feed inventory costing at fiscal year end.

So the production manager keeps a paper timesheet for every one of his people. Not because he wants paper. Because he is the only one who knows where each person actually worked that day, and the default will quietly be wrong if nobody corrects it.

Hospitality and club operations hit the same thing from a different angle. An HR manager at a country club described food and beverage staff carrying roughly ten separate clock-in codes each, with one set as the default so PTO pulls from the right place. Server, bartender, host, cart attendant. Same person, different rate, different department, depending on the shift.

What it actually costs

The country club HR manager did the arithmetic out loud, which is worth repeating because the number surprised her too.

Every department head prints every time card and cross-references it against whatever scheduling system that department uses. About two hours per person, per payroll. There are fifteen department heads. There are twenty-six payrolls a year.

That is roughly 780 hours a year spent confirming that hours landed in the right place. Before anyone has run payroll.

She was not describing a broken team. Her managers check. She triple-checks after them, scanning for anything above twelve or fifteen hours, which is how she caught a 92 hour punch in a single pay period. The checking is the job. That is the problem.

What to check before you commit to a system

• How many supervisors can see one employee’s time card? If the answer is a fixed number, find out what that number is before you sign, not after a director calls you
• Can an employee hold several positions at once, each with its own rate and department, without being duplicated as two records?
• Can a break or lunch rule change mid pay period when someone transfers, or does that become a manual adjustment?
• Is the schedule attached to the position or to the person? This is what decides whether a transfer corrupts the new team’s time card
• Can a manager reassign hours to a different job code after the fact, without an admin doing it for them?
• Does the department split carry through to the general ledger and to job or inventory costing, or does it stop at the time card?

The fix is structural, not procedural

Every workaround above is somebody compensating by hand for a system that models one person as one job. More checking does not solve that. It just moves the cost onto whoever is doing the checking, which is usually one person who already has a full plate.

When time and attendance lets one employee hold multiple positions, each with its own rate, department and approver, the manual department-shuffling stops being necessary. The hours arrive coded correctly, the right supervisor sees them, and payroll and tax carries the split through to the general ledger instead of stopping at the time card. Keeping HR on the same record is what stops a reorganization from rebuilding the spreadsheet six months later.

For context on the underlying wage and hour rules when someone works two roles at different rates, the Department of Labor’s guidance on overtime pay under the FLSA covers how the regular rate is calculated. Employees working multiple positions at different rates in the same workweek generally require a weighted average, which we walk through with a worked example in how to calculate blended overtime rates for dual-role employees. Getting the department coding right at entry is what makes that calculation possible in the first place.

Frequently Asked Questions

This guide reflects publicly available regulatory guidance and product information as of 2026. Wage and hour rules vary by state and by role. Feature availability may vary by plan. Contact Netchex for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page