Skip to main content

Expense Limits and Validation

Summary

Confirmed validation protects basic value and lifecycle integrity; no financial policy ceilings are implemented.

Audience

Claimants, operations, and QA.

Reference Content

AreaConfirmed validation
Tenant/claimantTenant and at least one claimant identity are required
AmountMust be greater than zero
CurrencyNormalized three-character code; current creation uses the domain default
CategoryNormalized free form with a maximum length
RejectionPending only; non-blank reason required
Approval/PaidPending-only approval; Approved-only Paid transition
ReceiptFile name and non-empty decodable content required

Maximum amount, category budgets, receipt thresholds, date windows, duplicate detection, and currency conversion are Not implemented.

Source References

  • microservices/src/expense-service/Domain/Common/ValueObjects.cs
  • microservices/src/expense-service/Application/Commands/ReceiptCommands.cs

See Also

Keywords

  • Expense validation

Revision Information

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