Expense Claim Events
Summary
Expense claim creation, deletion, and general updates are not event-producing transitions. Only approval, rejection, and paid outcomes raise domain events.
Claim lifecycle findings
| Claim operation | Domain event | Integration event |
|---|---|---|
| Create pending claim | Not implemented | Not implemented |
| Approve claim | ExpenseApprovedDomainEvent | ExpenseApprovedEvent |
| Reject claim | ExpenseRejectedDomainEvent | ExpenseRejectedEvent |
| Mark approved claim paid | ExpensePaidDomainEvent | ExpensePaidEvent |
| Delete pending claim | Not implemented | Not implemented |
| Add or remove receipt reference | Not implemented | Not implemented |
Audit and timeline records for creation, deletion, workflow activity, and receipts are persistence evidence. They are not event contracts and are not broker-published.
Requires confirmation
Whether claim creation, amendment, or deletion should become integration boundaries requires confirmation.
Source References
microservices/src/expense-service/Domain/Expense/ExpenseClaim.csmicroservices/src/expense-service/Domain/Expense/ExpenseDomainEvents.csmicroservices/src/expense-service/Application/Commands/ExpenseClaimCommands.cs
Related Articles
See Also
Keywords
- Expense events
- Expense Claim Events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly