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
| Area | Confirmed validation |
|---|---|
| Tenant/claimant | Tenant and at least one claimant identity are required |
| Amount | Must be greater than zero |
| Currency | Normalized three-character code; current creation uses the domain default |
| Category | Normalized free form with a maximum length |
| Rejection | Pending only; non-blank reason required |
| Approval/Paid | Pending-only approval; Approved-only Paid transition |
| Receipt | File 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.csmicroservices/src/expense-service/Application/Commands/ReceiptCommands.cs
Related Articles
See Also
Keywords
- Expense validation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly