Appearance
Transaction Audit Log
| Backlog field | Value |
|---|---|
| Story ID | AP-SHR-005 |
| Epic | Shared Platform |
| 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 auditors, I want to review transaction history and user actions so that I can trace material changes and posting activity.
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
Authorized audit scope and target/user/date criteria are required as applicable.
Optional or conditional
Action/entity/status filters and export are optional.
Action behavior
Audit reads are side-effect free; material state changes record actor, time, target, and before/after or event detail.
Blocking rule or downstream effect
Audit history is not editable through business APIs.