Skip to main content

Expense Claim Creation Troubleshooting

Summary​

Submit does nothing, client validation appears, API creation fails, or the new claim is not visible.

Audience​

  • Employees, managers, HR administrators, support engineers, developers, QA engineers, DevOps engineers, and solution architects, as applicable to the symptom.

Cause​

Use the verified possibilities in Likely causes; do not infer an environment-specific cause without evidence.

Resolution​

Use Safe resolution, then complete Validation. Stop and escalate if the required action exceeds approved access.

Symptoms​

Submit does nothing, client validation appears, API creation fails, or the new claim is not visible.

Scope​

ESS and compatibility forms, gateway/native creation, domain validation, persistence, and optional workflow start.

Likely causes​

  • Category or positive amount missing
  • Claimant or tenant context missing
  • Domain validation failure
  • Expense Service or persistence unavailable
  • Workflow start policy affects completion
  • List refresh or route scope differs

Safe diagnostic steps​

  • Record which form was used
  • Check source-defined client validation
  • Confirm tenant/claimant context category
  • Check API result category and Expense logs/traces
  • Check whether a claim was created before repeating submission
  • If workflow-enabled, inspect workflow-start evidence separately

Safe resolution​

Correct form/context input and submit once. If outcome is uncertain, read the claim list before retrying to avoid duplicates. Escalate service/dependency failures.

Validation​

A single Pending claim appears in the intended scoped list; workflow linkage exists only when expected.

Evidence to collect​

Surface, form validation category, result category, timestamp, correlation evidence, resulting status, and workflow-start evidence.

Escalation​

Frontend/gateway for form transport, Expense owner for validation/state, Workflow owner for start issues.

Requires confirmation​

Any corrective action beyond the supported resolution, incident ownership, response objectives, and production evidence locations require confirmation.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • microservices/src/expense-service/Application/Commands/ExpenseClaimCommands.cs

See Also​

Keywords​

  • Expense troubleshooting
  • Claim Creation

Revision Information​

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