Skip to main content

Expense Database Ownership and Boundaries

Summary​

Expense owns claim state, receipt metadata/references, audit, timeline, outbox intent, and processed-event evidence. Money, category, and claimant are claim-owned values, not independently owned records.

Audience​

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

Confirmed persistence​

Expense owns claim state, receipt metadata/references, audit, timeline, outbox intent, and processed-event evidence. Money, category, and claimant are claim-owned values, not independently owned records.

Document Service owns receipt binary content. Employee/Identity own claimant master data. Workflow owns workflow instances. Payroll owns reimbursement projections/calculation. Notification owns delivery. These are identifier or integration relationships; Expense persistence has no cross-service foreign keys.

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/Domain/Expense/ExpenseClaim.cs

See Also​

Keywords​

  • Expense database
  • Ownership and Boundaries

Revision Information​

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