The pitch is seductive: one system, one data model, HR and Finance finally speaking the same language. That unification drives the platform's real value. It is also the source of its hardest problems.
Put HR, Finance and IT on one shared foundation and you lose the ability to paper over the places those functions have quietly disagreed for years. The platform does not create cross-functional conflict. It exposes it, and hands you a deadline to resolve it.
1The foundation data model is the real negotiating table
At the center sits a model that forces a conversation most organizations have never had: how does HR's view of the organization reconcile with Finance's view of it?
HR thinks in
Supervisory hierarchies, positions, jobs, worker records. The organization as a structure of people and reporting lines.
Finance thinks in
Cost centres, ledgers, worktags, allocations. The organization as a structure of money and accountability for it.
2Competing calendars are a constraint, not a footnote
HR runs on open enrollment and performance cycles. Finance runs on the close, quarter end and year end. Neither pauses for your project, and they rarely align with each other.
3One record, many masters
An employee, a worker and a resource are increasingly the same object seen through different lenses. When one change to a worker ripples simultaneously into payroll, budget and security, data ownership stops being a policy debate and becomes an operational necessity.
What usually happens
The position versus job management call gets made inside the HCM workstream, in isolation, because it looks like an HR decision.
What it actually is
A decision that defines how headcount, budget and vacancy are modelled for the whole organization.
4Security does not respect your org chart
A manager in HR and a cost centre manager in Finance are often different people with different rights over overlapping data. The security model handles that nuance well, but only if the people designing the roles are looking across both functions at the same time.
Designed in silos, security becomes the place cross-functional assumptions go to collide, usually loudly, during user acceptance testing. By then the roles are built, the test scripts are written, and the fix touches both.
5Reporting is where the disagreement finally shows
Two functions can run happily on their own definitions until a single report has to satisfy both. Then headcount means two things, and the number on the page is wrong for somebody.
| The term | What HR means | What Finance means |
|---|---|---|
| Headcount | Active workers, including those on leave | Funded positions, whether or not anyone is in them |
| Manager | The supervisory relationship in the hierarchy | Whoever approves the spend against the cost centre |
| Department | The supervisory organization | The cost centre carrying the budget |
| Start date | The date employment begins | The date cost begins accruing, which may differ |
| Vacancy | A position with no incumbent | Budget available and unspent |
Agree the definitions before the reports are built, and write them down where both functions can see them. Every one of these disagreements is cheap to settle in design and expensive to settle in a board pack.