Treasuries and Banks

Backlog field	Value
Story ID	AP-FIN-009
Epic	Finance
Story type	Business workflow
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 maintain cash treasuries and bank accounts so that receipts, payments, and transfers use valid controlled accounts.

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

Treasury/bank identity, currency, owning GL account, branch scope, and active state are required.

Optional or conditional

Address/contact, bank metadata, opening/reference fields, and method restrictions are optional.

Action behavior

Master-data Save creates no cash movement; transactions change balances through posted payment/fund-transfer records.

Blocking rule or downstream effect

Deletion/account changes are blocked by transactions or balance history; deactivate for future selection.