Skip to content

Cost Centers

Backlog fieldValue
Story IDAP-ACC-004
EpicAccounting
Story typeMaster data / configuration
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-07-10

User story

As management accountants, I want to maintain cost-center hierarchy and allocations so that income and expenses can be analyzed by responsibility.

Acceptance criteria

  1. Only authorized users can view or execute the feature's actions.
  2. Required business data, active dependencies, tenant/branch scope, and current document state are validated.
  3. Invalid requests return actionable validation errors without applying a partial change.
  4. Search, list, view, print, and export operations use the same authorized business scope.
  5. Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
  6. Financial or stock effects are applied atomically and no more than once.

Business rules

Required

Code/name, hierarchy position, and active state are required.

Optional or conditional

Description and parent are optional for top-level centers.

Action behavior

Save changes analytical dimensions only; no GL amount is created until a journal line uses the center.

Blocking rule or downstream effect

Deletion is blocked by children, item/asset configuration, or journal allocations.

Internal Documentation — Microtec