Skip to main content

Expense Receipt Reference Storage

Summary​

Receipt references are child entities keyed independently and linked to ExpenseClaim by a configured foreign key. Claim deletion cascades to local receipt-reference rows. A tenant/claim composite index and the relationship index support claim receipt access.

Audience​

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

Confirmed persistence​

Receipt references are child entities keyed independently and linked to ExpenseClaim by a configured foreign key. Claim deletion cascades to local receipt-reference rows. A tenant/claim composite index and the relationship index support claim receipt access.

Expense stores descriptive and integrity metadata plus external document/storage identifiers; it does not store receipt bytes. Removing a reference does not invoke Document deletion. Cross-service referential integrity, content retention, orphan cleanup, and masking 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/Application/Commands/ReceiptCommands.cs

See Also​

Keywords​

  • Expense database
  • Receipt Reference Storage

Revision Information​

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