Skip to main content

Audit and Timeline Storage

Summary​

Persistence and coverage boundaries for Payroll audit and timeline evidence.

Audience​

Payroll developers, QA and support engineers, solution and security architects, and implementation partners.

Reference Content​

The sections below describe the confirmed logical storage contract and its implementation boundaries.

Purpose​

Distinguish PayrollAuditLog from PayrollTimeline and state their coverage limits.

Ownership​

Payroll owns both evidence records. Audit represents operation evidence; timeline represents ordered employee/run lifecycle entries.

Lifecycle​

Selected native commands stage both records with business writes. Reports/exports, compatibility operations, inbound projections, and backfill may write audit only, sometimes in a separate save.

Persisted fields​

Audit retains tenant, target type/identity, action, actor, structured details, and occurrence time. Timeline retains tenant, optional employee/run references, entry type, detail, actor, and occurrence time.

Relationships​

Entity, employee, and run references are scalar evidence fields; no foreign keys are configured.

Constraints​

Required bounded classification/actor fields are configured. Neither record has a business uniqueness constraint.

Indexes​

Audit uses tenant/occurrence time. Timeline uses tenant/employee/occurrence time. No separate run-oriented timeline index is configured.

Tenant behavior​

Both types have global filters. Explicit tenant predicates are present in filter-bypassing evidence queries.

Audit behavior​

These records are the audit behavior. Coverage is selective and does not provide automatic entity change capture.

Integration usage​

Inbound projection and backfill workflows add audit records. Timeline is primarily used by Payroll lifecycle operations.

Known limitations​

No immutability control, retention policy, cryptographic integrity, or database-wide audit interceptor is confirmed.

Requires confirmation​

  • Evidence retention and access-control policy.
  • Whether every state-changing compatibility operation must create audit/timeline entries.

Source References​

  • microservices/src/payroll-service/Infrastructure/PayrollDbContext.cs
  • microservices/src/payroll-service/Domain/PayrollEntities.cs
  • microservices/src/payroll-service/Infrastructure/Migrations/PayrollDbContextModelSnapshot.cs
  • microservices/src/payroll-service/Application/PayrollCalculationService.cs
  • microservices/src/payroll-service/Application/PayrollOutputsService.cs
  • microservices/src/payroll-service/Backfill/BackfillAudit.cs

See Also​

Keywords​

  • Payroll database
  • Audit and Timeline Storage
  • Payroll persistence

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly