Skip to main content

Expense Operational Checklist

Summary​

Use this non-destructive checklist for readiness reviews and incidents.

Audience​

Operators, support, developers, QA, architects, and release owners.

Reference Content​

  • Confirm route ownership and intended UI/API surface.
  • Confirm service process health, then check deeper dependency evidence separately.
  • Confirm migration status through approved deployment evidence.
  • Confirm tenant context and claimant mapping category without exposing identities.
  • Check claim lifecycle state and workflow-managed status.
  • Check receipt reference and Document ownership separately.
  • Check outbox Pending/Failed/Processed distribution without reading payload content.
  • Check Payroll and Notification consumption separately from publication.
  • Use smoke/parity/cutover evidence only in approved environments.
  • Stop and escalate on parity/invariant failure.
  • Do not directly edit data, replay broker messages, or use undocumented recovery commands.
  • Record validation and owner sign-off.

Requires confirmation​

Checklist ownership, production evidence locations, sign-off roles, and release cadence require confirmation.

Source References​

  • microservices/src/expense-service/Program.cs
  • microservices/src/expense-service/Messaging/OutboxRelayHostedService.cs
  • microservices/scripts/smoke-expense.ps1
  • microservices/docs/expense-cutover-runbook.md

See Also​

Keywords​

  • Expense operations
  • Operational Checklist

Revision Information​

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