Skip to main content

Expense Audit and Timeline Storage

Summary​

Audit and timeline are separate tenant-scoped evidence stores. Both use their own primary identity and logical entity type/identifier rather than a foreign key to ExpenseClaim. Composite tenant/time indexes support recent evidence reads.

Audience​

Backend developers, database reviewers, QA, architects, DevOps, support, and implementation teams.

Confirmed persistence​

Audit and timeline are separate tenant-scoped evidence stores. Both use their own primary identity and logical entity type/identifier rather than a foreign key to ExpenseClaim. Composite tenant/time indexes support recent evidence reads.

Application commands add evidence to the same tracked context as supported claim mutations. Evidence is not documented as immutable, append-only at database permission level, or a compliance ledger. Retention, archival, correction, masking, and access governance require confirmation.

Requires confirmation​

Production migration governance, retention, archival, masking, performance targets, concurrency roadmap, operational-store access, and rollback ownership remain unconfirmed unless narrowed above.

Source References​

  • microservices/src/expense-service/Infrastructure/ExpenseDbContext.cs
  • microservices/src/expense-service/Infrastructure/Persistence.cs

See Also​

Keywords​

  • Expense database
  • Audit and Timeline Storage

Revision Information​

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