Expense Claim Approval and Rejection API
Summary
| Method | Path | Preconditions | Outcome |
Audience
API consumers, backend and frontend developers, QA, architects, implementation partners, and support.
Reference Content
| Method | Path | Preconditions | Outcome |
|---|---|---|---|
| POST | /expense/claims/{claimId}/approve | Claim is Pending and not workflow-managed | Approved claim |
| POST | /expense/claims/{claimId}/reject | Claim is Pending, not workflow-managed, and reason is present | Rejected claim |
Approval comment/remarks are optional. Rejection reason is required. Already-decided or otherwise invalid lifecycle operations return conflicts/validation outcomes. Workflow-managed claims reject direct decisions.
The native approval operation does not apply the compatibility Payroll frozen-period guard in the reviewed source. Approval authority and operation-level authorization Require confirmation.
Source References
microservices/src/expense-service/Api/ExpenseEndpoints.csmicroservices/src/expense-service/Application/Commands/ExpenseClaimCommands.cs
Related Articles
See Also
Keywords
- Expense API
- Approval and Rejection
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly