Skip to content

Chart of Accounts ​

Backlog fieldValue
Story IDAP-ACC-002
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 accounting administrators, I want to maintain account sections, types, levels, and the chart hierarchy so that transactions post to a controlled financial structure.

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 ​

Account code/name, type, nature, level/parent, currency behavior, and posting/detail classification are required.

Optional or conditional ​

Descriptions, tags, cost-center requirements, and alternate-language detail are optional or policy-driven.

Action behavior ​

Add/Edit changes account master data only; Delete is blocked by children, settings, master-data fallback, journals, or balances.

Blocking rule or downstream effect ​

Only active leaf/posting accounts may be selected for transaction lines.

Internal Documentation — Microtec