Skip to content

Transaction Audit Log ​

Backlog fieldValue
Story IDAP-SHR-005
EpicShared Platform
Story typeBusiness workflow
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-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 ​

  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 ​

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.

Internal Documentation — Microtec