Payment Terms

Backlog field	Value
Story ID	AP-FIN-008
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 credit controllers, I want to define payment schedules and due-date rules so that receivables and payables follow agreed terms.

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

Localized identity and one or more valid term lines are required.

Optional or conditional

Default flag, description, fixed-day rules, and percentages/amounts depend on term type.

Action behavior

Lines must create a complete non-duplicated due schedule; percentages must total 100 where percentage-based.

Blocking rule or downstream effect

Changing a term affects future invoices only, not existing invoice balances.