Appearance
Payment Methods
| Backlog field | Value |
|---|---|
| Story ID | AP-FIN-005 |
| Epic | Finance |
| 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 finance administrators, I want to configure cash, bank, card, and other payment methods so that users capture settlement details consistently.
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
Localized name/code, payment place, method type, currency/availability, and active state are required.
Optional or conditional
Bank constraints, cheque behavior, commission account/rate, VAT tax/account, and references are conditional.
Action behavior
Save changes future payment entry and commission/tax calculation; posted payments retain their snapshot.
Blocking rule or downstream effect
Cash cannot be used with Bank place; cheque methods require cheque data at transaction time.