Expense Notification Dependency Operations

Summary

Notification consumes the three Expense lifecycle events and owns intent resolution, idempotency, message creation, and delivery.

A Processed Expense outbox row proves broker publication, not Notification consumption or channel delivery. Investigate Notification consumer evidence, processed-event identity, resolver outcome, message state, and delivery attempts through approved support surfaces.

Ordinary Expense mapping does not establish claimant email enrichment, so email delivery must not be assumed.

Requires confirmation

Recipient enrichment, channel guarantees, template ownership, delivery escalation, and cross-service correlation procedures require confirmation.

Source References

• microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/notification-service/Application/NotificationDispatcher.cs
• microservices/scripts/smoke-expense.ps1

Related Articles

• Expense operations documentation
• Expense troubleshooting
• Expense technical documentation

See Also

• Expense events
• Expense module

Keywords

• Expense operations
• Notification Dependency

Revision Information

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