How to Allocate One Employee Across Multiple Departments or Entities
How to Allocate One Employee Across Multiple Departments or Entities
August 25, 2026
One person, three cost centers, and the $20K that moves when the split changes.
Welcome back to Bridging the Deficit, your go-to resource for financial planning insights, the kind you can actually use, not just theory.
This week: the employee who belongs to three places at once. Keep reading, as there is one of them in every finance org.
The split is typed into a cell as 50/30/20, and it is wrong in a way that never shows up on the consolidated P&L. Total company cost stays exactly right. The error lives entirely in the department columns your managers are measured on. Here is where it comes from and roughly what it costs, per person, per change.
The Controller who runs Finance and half of Operations. The plant manager covering two facilities. The grants administrator paid out of four funding sources. The shared-services CFO invoiced across every entity in the group.
You put them in the model at 50/30/20 and move on. That number is doing more work than it can hold.
Because a split is not one decision. It is four. Your spreadsheet only asks you for one of them.
In this issue:
- The four decisions your split actually makes
- Run it on one person
- Where the grid stops holding
- Recognize your shape
- Pull the list
The Four Decisions Your Split Actually Makes
1. What is the basis?
Percentage of time. Percentage of salary. FTE fraction. Actual hours logged. These produce different numbers and they do not reconcile to each other. A 0.5 FTE who works 60% of their hours in Operations is one person with two defensible splits.
Pick a basis, write it down, and apply it the same way to every person who splits. If half your allocations are time-based and half are FTE-based, your department rollup does not tie and nobody will be able to tell you why.
2. Which cost layers follow the basis, and which don't?
This is the one that quietly breaks the number.
Wage-driven layers follow the split cleanly, because they are a percentage of a base that is already being divided. FICA and Medicare at 7.65%. Workers' comp and disability, priced by role class. Bonus, when it is a percentage tier.
Fixed-dollar-per-head layers do not follow anything. Health premium, retirement match, life and AD&D, equipment and phone stipends. These are one number attached to one human being. Splitting them 50/30/20 is a choice you are making, not math the model is doing for you. And if one of those three destinations is a separate legal entity, you have just moved premium onto a set of books that does not carry the plan.
3. Is the split inside one entity or across several?
Inside one entity, a split is a cost center tag. The dollars stay put and you are only deciding which department wears them.
Across entities, it is a transaction. One entity employs the person and runs the payroll. The others are being charged. That creates an intercompany payable and receivable that has to eliminate on consolidation, and it has to eliminate the same way every month or your close gets longer.
Your workbook treats these two situations identically. They are not.
4. When does the split change?
Almost never on January 1. Someone moves off a project in March. A grant closes in July. A new site opens in September and the regional director picks it up.
A percentage typed into a cell has no effective date. It runs the full year, every year, until someone remembers to change it. That is where the money goes.
Run It On One Person
Take a Controller at $145,000 base, splitting 50% Operations, 30% Finance, 20% to a shared-services entity. Run this alongside someone real from your own model.
Build the loaded cost before you split anything.
Start with the $145,000. Add the 10% bonus tier and wages are $159,500. FICA and Medicare at 7.65% of that is $12,202. Workers' comp and disability, priced at roughly 1.2% for this role class, adds $1,914. Everything to this point is wage-driven, and it totals $173,616.
Then the layers that are not percentages of anything. Health premium at $18,600. Retirement match at 4% of base, $5,800. Life and AD&D, $480. That is $24,880 of fixed dollars attached to one human being, and it does not know what a department is.
Loaded cost: $198,496. That is 37% on top of base, and an eighth of the total sitting in layers that have no natural home.
Now apply the split.
Operations takes $99,248. Finance takes $59,549. Shared services takes $39,699.
Look at that third number. You just charged the shared-services entity $4,976 of health, retirement match and life cover for an employee who is not on its payroll and not on its benefit plan. Someone has to book that as an intercompany charge, and if the elimination is done by hand it will not look the same twice.
Now move the effective date.
Say the split shifts to 30/50/20 on July 1 when a project wraps.
Your budget says Operations carries $99,248 for the year. Actual is six months at 50% and six at 30%. That is $49,624 plus $29,774, or $79,398.
Operations is overstated by $19,850. Finance is understated by $19,849.
$19,850 · One employee · One mid-year change
Total company cost is exactly right, which is why nothing flags. Nothing in your variance report is designed to catch a number that nets to zero.
One employee. One mid-year change. Twenty thousand dollars sitting in the wrong department.
Now count how many people in your org split. If it is twelve, and half of them change at some point in the year, you are carrying roughly $240,000 of departmental margin in the wrong column, and no line item anywhere says so.
If you want to see what this looks like when the split is a field with an effective date instead of a formula, the personnel module walkthrough covers allocations in about three minutes.
👉 See our Personnel Module in Action
Where the Grid Stops Holding
Twelve split employees. Seven cost layers each, four that follow the basis and three that do not. Two or three destinations per person. Effective dates landing on different months.
That is roughly 250 rows to maintain for twelve people, and every one of them has to be updated by hand when a split changes, in the right month, across the budget version and the projection and last year's actuals if you want the comparison to mean anything.
It holds until the person who built it takes two weeks off.
The structural fix is the same one that applies everywhere in personnel budgeting: allocate the position, not the person, and let the split carry a start date and an end date. Then a mid-year change is one edit that flows through every layer, both entities and every report that touches them, instead of forty.
Recognize Your Shape
Three flavors of split, and the same trap under all of them:
Shared-services split
One person, several departments, one legal entity. Your problem is the fixed-dollar layers and the effective date. No intercompany, but your department margins are wrong in both directions at once.
Cross-entity split
One employer of record, several entities being charged. Everything above, plus an intercompany payable and receivable that has to eliminate cleanly every month. Common in group structures, franchise operators, and anyone running a management company.
Fund or grant-funded split
Effort allocated across funding sources, each with its own allowable cost rules and its own reporting calendar. The split is not just a budgeting decision here, it is a compliance one, and the budget version and the projection often have to follow different rules.
Whichever you are, the workbook is the same trap. The exit is a system that treats an allocation as a rule with a date on it rather than a number typed into a cell.
Pull the List
Every employee in your model whose cost lands in more than one department, entity or fund. It is usually shorter than people expect and always longer than the one or two you had in mind.
For each one, two questions. What happens to the fixed-dollar benefit layers. And when did the split last change.
If you cannot answer the second one from the model itself, without asking the person who maintains it, the effective date is not in your budget. It is in somebody's memory. That is the gap, and it is worth about twenty thousand dollars per person, per change.
Take the next step
Bring your split list to a 30-minute discovery call.
We will walk through how allocations, fixed-dollar fringe and intercompany charge-outs are handled when the system owns the rule instead of the formula.
4 to 6 week implementation · Finance-owned, no IT project · Onshore FP&A support
About Centage
Centage delivers the complete FP&A platform—budgeting, forecasting, reporting, and scenario planning—designed to free finance teams from spreadsheet chaos.
For organizations where strategic finance matters, Centage replaces manual processes with automated workflows, real-time collaboration, and seamless integrations—so finance leaders can stop maintaining spreadsheets and start driving decisions.