Skip to content

Vendors and Categories

Backlog fieldValue
Story IDAP-PUR-009
EpicPurchase
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 purchasing users, I want to maintain vendors, contacts, tax data, categories, and commercial defaults so that purchase documents use valid supplier information.

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

Vendor/category localized identity and active state are required; vendor legal/tax/accounting and currency data are required by enabled workflows.

Optional or conditional

Contacts, addresses, payment term, credit, purchase/return/discount accounts, and category inheritance are conditional.

Action behavior

Vendor accounts override category accounts; missing Payable blocks invoice/payment posting.

Blocking rule or downstream effect

Deactivate prevents new selection; referenced records/history remain.

Internal Documentation — Microtec