Expense UI Validation and Error Messages
Summary
Client checks are minimal; domain and command validation remain authoritative.
Audience
Frontend/backend developers, QA, support, and product owners.
Reference Content
| Area | Confirmed client behavior | Server behavior |
|---|---|---|
| ESS create | Category required and amount greater than zero | Validates tenant, claimant, category, amount, currency, and date |
| Compatibility create | Employee and amount greater than zero | Uses native create validation |
| Reject | Modal collects decision input | Rejection reason required |
| Invalid lifecycle | No complete client state machine | Conflict returned by command |
| Workflow-managed decision | No task integration in Expense screen | Direct decision rejected |
| Delete | Pending presentation only | Pending and self-ownership checks |
| API failure | Toast/helper or inline page error | Structured result categories |
The source-defined ESS success message follows submission. Compatibility actions show source-defined success notifications and extracted API errors. Exact downstream text can vary by route and result.
Requires confirmation
Unified error taxonomy, field-level messages, localization, retry affordances, and accessible error focus require confirmation.
Source References
UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsxUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsxmicroservices/src/expense-service/Application/Commands/ExpenseClaimCommands.csmicroservices/src/expense-service/Domain/Expense/ExpenseClaim.cs
Related Articles
See Also
Keywords
- Expense UI
- Validation and Errors
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly