Skip to main content

Expense Business Rules

Summary​

This catalog separates enforced rules from authorization and policy gaps.

Audience​

All Expense participants and reviewers.

Reference Content​

  • Creation requires tenant, claimant, valid amount/category, and produces Pending; there is no edit or separate submit.
  • Pending alone can be approved, rejected, workflow-linked, or deleted. Rejection requires a reason.
  • Workflow-managed Pending claims cannot be decided by the direct decision commands.
  • Approved alone can be marked Paid; Paid does not execute payment.
  • Compatibility approval is blocked for a Payroll-frozen claim month.
  • Receipt content is stored through Document Service; reference deletion retains stored content.
  • Creation, workflow activity, decisions, Paid, deletion, and receipt mutations create evidence.
  • Delete-own-Pending is the only explicit claimant ownership rule. Create/read/approve/reject/mark-paid authorization Requires confirmation.
  • Manager approval, claim items, cancellation, policy limits, receipt mandates, payment reconciliation, and reporting workflows are Not implemented.

Source References​

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

See Also​

Keywords​

  • Expense business rules

Revision Information​

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