Skip to content

Reference data management

Hierarchy Datasets

Keep reporting structures understandable as the organisation changes.

A cost centre can move to another department without becoming a different cost centre.

Separate an identifier from its position in a reporting structure and publish hierarchy changes with ownership, versioning and effective dates.

Refrncr helps teams manage reporting and organisational structures as governed hierarchy datasets.

Version 2Effective until 2026-06-01
  • Commercial
    • Sales
      • 4200 Customer Operations
Version 3Effective from 2026-06-01
  • Operations
    • 4200 Customer Operations
Organisation structureOwner: FinancePublished
The identifier stays the same while the reporting structure changes.

Definition

What is a hierarchy dataset?

A hierarchy dataset defines parent-child relationships between business concepts.

It allows reports, planning processes and applications to group values into meaningful structures.

Taxonomies can be entered as a hierarchy too, such as a product classification: Electronics › Computers › Laptops.

  • Organisation structures
  • Regional hierarchies
  • Cost centre trees
  • Product category trees
  • Legal ownership structures

Where it breaks

Why reporting structures become difficult to manage

Reporting structures change.

Departments merge, teams move, organisations reorganise and countries get reassigned.

Without versioning, historical reporting becomes difficult to explain.

  • Different reports use different structures
  • Historical totals are difficult to reproduce
  • Spreadsheet hierarchies drift apart
  • No clear ownership

Many structures

organisation_v5.xlsxreporting_final.xlsxregions_new.xlsxownership_structure.xlsx
Organisation structureVersion 2Owner: FinanceEffective date: 2026-01-01Published
Many structures → One published hierarchy

Stable identity

The same identifier, different structures

A cost centre can appear in multiple hierarchy datasets without changing its identity.

The hierarchy provides context. The identifier remains stable.

Organisation structure
  • Commercial
    • Sales
      • 4200 Customer Operations
Regional structure
  • Europe
    • Netherlands
      • 4200 Customer Operations
One identifier. Multiple reporting structures.

Visible change

What happens when the organisation changes?

Most hierarchy problems begin when a reorganisation changes reporting relationships.

The change should be reviewed, versioned and published instead of replacing the existing structure.

Record changesDraft based on Version 2
4200 Customer Operations
Parent
SalesOperations

Takes effect on 2026-06-01, after review and publication.

Controlled change

Manage hierarchy changes through a controlled process

Structural changes are prepared in a draft, reviewed and released as a complete, immutable hierarchy publication.

PrepareDraft
→
ApproveReview
→
VersionPublishVersion 3Effective from 2026-06-01
→
APIConsume

Effective dating

Publish hierarchy versions with effective dates

A hierarchy is not replaced when a reorganisation happens.

Both versions remain available so reports can use the structure that applied at the time.

Version 2Published
4200 Customer Operations
Parent
Sales
Effective until 2026-06-01
Version 3Published
4200 Customer Operations
Parent
Operations
Effective from 2026-06-01
Reports use the structure that applied on the reporting date.

Clear purpose

One hierarchy, one purpose

Different structures answer different questions.

A reporting hierarchy, regional hierarchy and legal ownership hierarchy should exist as separate hierarchy datasets.

Reporting hierarchyBy departmentCommercial↓Sales
Regional hierarchyBy countryEurope↓Netherlands
Legal hierarchyBy ownershipHolding↓Operating Company
Different questions require different hierarchies.

Examples

Common hierarchy dataset examples

Organisation Structure

Roll up results by department.

Regional Structure

Analyse results by geography.

Cost Centre Hierarchy

Group operational units for reporting.

Product Category Hierarchies

Roll products up from SKU to category and portfolio level.

Legal Entity Structure

Represent ownership relationships.

Support Teams

Group shared operational support functions.

Why refrncr

Why teams use refrncr for hierarchy datasets

  • Stable identifiers
  • Versioned structures
  • Effective dates
  • Controlled publication
  • Review workflows
  • Audit trail
  • One parent per node
  • API access

Start with real data

Start with one reporting structure that changes too often in spreadsheets

Choose a hierarchy currently maintained in spreadsheets, reporting tools or application configuration.

Replace multiple versions with a single published hierarchy dataset and make historical structures available through the API.