Appearance
Vendors and Categories
| Backlog field | Value |
|---|---|
| Story ID | AP-PUR-009 |
| Epic | Purchase |
| Story type | Master data / configuration |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | AppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available |
| Last source review | 2026-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
- Only authorized users can view or execute the feature's actions.
- Required business data, active dependencies, tenant/branch scope, and current document state are validated.
- Invalid requests return actionable validation errors without applying a partial change.
- Search, list, view, print, and export operations use the same authorized business scope.
- Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
- 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.