Skip to main content

Expense Receipts

Summary​

Expense stores receipt metadata and Document Service references; receipt bytes remain in Document Service.

Audience​

Claimants, Expense operations, support, and QA.

Relationship​

Upload requires a non-empty file name and decodable, non-empty content. A Document outage fails safely except for an explicitly enabled development-only metadata fallback. Deleting a receipt removes only the Expense reference; stored content remains. Receipt-required-by-category/status rules, claimant-only attachment control, retention, and business deletion policy Require confirmation.

Source References​

  • microservices/src/expense-service/Application/Commands/ReceiptCommands.cs
  • microservices/src/expense-service/Domain/Expense/ExpenseClaim.cs

See Also​

Keywords​

  • Expense receipts

Revision Information​

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