Skip to main content

Expense Paid State Troubleshooting

Summary​

Cannot find a Mark Paid action, native action conflicts, or Paid is mistaken for payment execution.

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​

Cannot find a Mark Paid action, native action conflicts, or Paid is mistaken for payment execution.

Scope​

Native Paid command and downstream projection/notification outcome; no confirmed Paid UI.

Likely causes​

  • No Paid UI is implemented
  • Claim is not Approved
  • Claim is already Paid
  • Authority is not defined
  • External payment execution/reconciliation is outside Expense

Safe diagnostic steps​

  • Confirm whether the request expects status recording or actual payment execution
  • Read current claim status through supported API
  • Confirm the native action and authority are approved for the operator
  • If already processed, inspect event/projection evidence rather than repeating

Safe resolution​

Use only an approved native integration to mark an Approved claim Paid. Do not use Expense to execute, reverse, or reconcile a payment.

Validation​

Claim status is Paid, one Paid outbox intent exists, and downstream evidence is checked separately.

Evidence to collect​

Previous/current status, action result, timestamp, event identity/correlation evidence, and projection/notification outcome without financial values.

Escalation​

Expense and Finance/product owners; Payroll/Notification owners for downstream gaps.

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/Application/Commands/ExpenseClaimCommands.cs
  • microservices/src/expense-service/Api/ExpenseEndpoints.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs

See Also​

Keywords​

  • Expense troubleshooting
  • Paid State

Revision Information​

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