Skip to main content

Payroll Event Consumer Landscape

Summary​

This page documents confirmed payroll event consumer landscape behavior and explicitly marks incomplete integration boundaries.

Audience​

Payroll and integration developers, QA and support engineers, solution and security architects, and implementation partners.

Reference Content​

ServiceConfirmed Payroll subscriptionsHandling
DocumentPayrollCalculated, PayrollFrozen, PayslipGeneratedUpdates a local Payroll document projection with duplicate/stale handling
NotificationPayrollFrozen, PayslipGeneratedResolves notification intents and performs idempotent dispatch
PlatformPayrollFrozenFoundation receipt audit and processed-event record only
IntegrationNoneIts supported subscription list contains no Payroll event
EmployeeNoneNo Payroll-event subscriber found
AttendanceNoneNo Payroll-event subscriber found
LeaveNoneNo Payroll-event subscriber found
ExpenseNoneUses a synchronous Payroll guard elsewhere; no Payroll-event subscriber found
ReportingNoneNo Payroll-event subscriber found
GatewayNoneNo Payroll-event subscriber found

Subscription proves handling intent, not successful end-to-end delivery.

Source References​

  • microservices/src/document-service/Messaging/DocumentReadModelConsumer.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/platform-service/Messaging/PlatformEventConsumer.cs
  • microservices/src/integration-service/Domain/IntegrationEntities.cs

See Also​

Keywords​

  • Payroll events
  • Payroll Event Consumer Landscape
  • Integration contracts

Revision Information​

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