Skip to main content

Expense Tenant and Claimant Context Troubleshooting

Summary​

Claims are missing, creation reports invalid claimant/context, or the visible list does not match the intended employee.

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​

Claims are missing, creation reports invalid claimant/context, or the visible list does not match the intended employee.

Scope​

Tenant resolution, ESS claimant forwarding, domain claimant requirements, and tenant query filters.

Likely causes​

  • Tenant context missing or inconsistent
  • Claimant user/labor mapping unavailable
  • ESS gateway forwarded an incomplete identity category
  • Wrong route used for intended scope
  • Compatibility and native identity shapes differ

Safe diagnostic steps​

  • Confirm the correct tenant portal and supported route
  • Confirm the user has an employee mapping through approved identity support surfaces
  • Compare ESS list behavior with the intended claimant scope
  • Check Expense result category and tenant-filtered evidence
  • Do not place employee identifiers in public tickets

Safe resolution​

Correct the authoritative identity/tenant mapping through its owner, then retry the supported read/create flow. Do not alter claim rows.

Validation​

The scoped list and new claim resolve to the expected tenant/claimant through supported APIs.

Evidence to collect​

Tenant category, mapping-present/absent result, route, action, timestamp, and correlation evidence.

Escalation​

Identity/employee mapping owner, gateway owner for ESS forwarding, then Expense owner.

Requires confirmation​

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

Source References​

  • microservices/src/expense-service/Infrastructure/Persistence.cs
  • microservices/src/gateway-api/EssEndpoints.cs
  • microservices/src/expense-service/Application/Commands/ExpenseClaimCommands.cs

See Also​

Keywords​

  • Expense troubleshooting
  • Tenant and Claimant Context

Revision Information​

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