Skip to main content

Expense Submission

Summary​

There is no separate submit command or Submitted status. Creating a valid claim persists it immediately as Pending and records creation evidence.

Audience​

Claimants and Expense operations.

Confirmed behavior​

When workflow delegation is enabled, creation then attempts to start an approval workflow. A successful start links the Pending claim; production workflow-start failure does not silently leave an unrouted claim. When delegation is off, the claim remains ordinary Pending for local decision handling.

Draft saving, later submission, withdrawal, resubmission, and submission-time receipt enforcement are Not implemented.

Source References​

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

See Also​

Keywords​

  • Expense submission

Revision Information​

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