Skip to content

Controlling — Cost Center & Allocation Key Registry

Controlling needs stable cost-center hierarchies and allocation keys. Start from the Cost Centers common entity; add allocation keys as a sibling entity.

Why this is needed

  • Month-end breaks when teams use different allocation spreadsheets.
  • Reorgs need effective-dated hierarchies.
  • Fabric models should consume approved dimensions.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Close uses only approved keys/centers.
historyEnabled true History explains restatements after reorg.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: allocation_key
displayName: Allocation key
domain: Finance
description: Allocation key
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: key_code
uniqueConstraints:
  - name: uq_allocation_key_0
    columns: [key_code, version_label]
columns:
  - name: key_code
    dataType: string
    nullable: false
    maxLength: 32
  - name: version_label
    dataType: string
    nullable: false
    maxLength: 32
  - name: name
    dataType: string
    nullable: false
    maxLength: 128
  - name: driver_description
    dataType: string
    nullable: false
    maxLength: 512
  - name: status
    dataType: string
    nullable: false
    maxLength: 16
  - name: effective_from
    dataType: date
    nullable: false

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

key_code version_label name driver_description status effective_from
AK_HC 2026-Q1 Headcount split FTE by cost center approved 2026-01-01
AK_REV 2026-Q1 Revenue split Recognized revenue by market approved 2026-01-01

Benefits for the company

  • One approved allocation version for all close reports.
  • Warehouse consumption keeps Power BI aligned.
  • Natural land-and-expand for Controlling sponsors.