Expense Event Consumer Landscape

Summary

Payroll and Notification are the only confirmed consumer services for Expense contracts. No Workflow, Document, Platform, Reporting, Integration, or Employee subscription to an Expense event was found.

Confirmed consumers

Consumer	Subscribed Expense types	Consumer-owned result
Payroll	ExpenseApproved, ExpenseRejected, ExpensePaid	Maintains an approved-expense projection used during calculation
Notification	ExpenseApproved, ExpenseRejected, ExpensePaid	Resolves notification intent, recipient, template variables, and channels

Both consumers use manual acknowledgement. Processing failures are negatively acknowledged and requeued. Both maintain consumer-side idempotency by event identity.

Expense is not a consumer: it registers no subscription and has no message-handling hosted service.

Not implemented

Expense subscriptions in Workflow, Document, Platform, Reporting, Integration, or Employee are Not implemented.

Requires confirmation

Consumer service ownership, subscription monitoring, delivery objectives, and future reporting consumers require confirmation.

Source References

• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/notification-service/Application/NotificationDispatcher.cs

Related Articles

• Expense events documentation
• Expense technical documentation
• Expense database documentation

See Also

• Expense API documentation
• Expense module

Keywords

• Expense events
• Consumer Landscape
• Integration contracts

Revision Information

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