Departments, Sites and Cost Centres

Reference data is the set of things a person's record points at: their site, their department, their cost centre, their role.

Why it diverges

It is maintained separately in each system, by different people, at different times.

Finance reorganises cost centres and tells finance systems.

Operations opens a site and tells the scheduling system.

HR renames a department and tells nobody, because to HR it is a label.

Within a year the four lists are four different lists, and nothing warns anyone.

What that costs

Totals do not reconcile, and the difference gets explained as timing rather than investigated.

Reports cannot be compared across systems, so each department uses its own and they disagree in meetings.

Costs land in the wrong place, which finance discovers at period end and corrects manually, every period, forever.

And analysis becomes impossible, because there is no dimension common to all four.

The rule

One master for each dimension, and a stated owner.

Sites and departments usually master in HR; cost centres in finance.

Every other system receives them rather than maintaining its own list.

Where a system cannot receive them, the mapping is documented and owned, which is worse but honest — an undocumented mapping is the actual problem.

Handling change

A department split or a site closure is a change to history as well as to the future.

Decide whether old records move with the reorganisation or stay as they were.

Both are defensible; only one can be true, and the decision determines whether last year's figures still reproduce.

Record the date of every structural change, because a report that spans it will otherwise be wrong in a way nobody can explain.

The check

Compare the lists across systems, quarterly.

Count: entries in each, entries in one and not another, entries with the same name and different codes.

The last category is the dangerous one, because it reconciles by eye and not by machine.

And check what happens to a person whose department no longer exists, which is the case every reorganisation creates and nobody tests.

Record every structural change with its date

The field that makes historical reports reproducible.

A department split, a site closure, a cost centre renumbering.

A report spanning the change will otherwise be wrong in a way nobody can explain, because half the period uses one structure and half the other.

One line per change, kept indefinitely, and it costs nothing until the moment it is the only thing that answers the question.

Turn the boundary into a test

For a concrete product reference, a practical team scenario can help turn this boundary into a test. Verify the current behaviour with representative fields and record what reaches the destination.

Independent reference

For a thematic point of reference, see the International Organization for Standardization. Its current material provides useful context beyond product documentation.