Skip to main content

Expense Document Dependency Operations

Summary​

Document Service owns receipt content. Expense stores reference metadata only and uses synchronous HTTP for store/download.

For an upload issue, distinguish Document storage failure from Expense reference-save failure. For download, distinguish missing local reference, metadata-only reference, and missing downstream content. Removal deletes only the Expense reference and deliberately retains stored content.

Safe reconciliation compares approved service responses and reference metadata; it must not inspect or copy receipt content into tickets.

Requires confirmation​

Orphan detection, content retention/deletion, receipt-access governance, metadata repair ownership, and service objectives require confirmation.

Source References​

  • microservices/src/expense-service/Application/Commands/ReceiptCommands.cs
  • microservices/src/expense-service/Infrastructure/DocumentReceiptGateway.cs
  • microservices/src/expense-service/Infrastructure/DocumentServiceClient.cs

See Also​

Keywords​

  • Expense operations
  • Document Dependency

Revision Information​

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