We’ve configured webhooks in UKG Pro 2023.1 to receive notifications when employees make benefits enrollment changes. The webhook works perfectly for primary enrollments (employee enrolls in medical, dental, vision), but it’s not triggering when employees add dependents to existing coverage.
Our downstream systems (insurance carrier integrations, payroll deduction updates) rely on these webhook events for real-time synchronization. When a dependent is added, we need to update carrier files immediately to ensure coverage is active. Currently, we’re discovering missing dependents during our nightly batch reconciliation, which creates a data mismatch and delays coverage activation by 24 hours.
The webhook configuration shows “benefits.enrollment.updated” as the event type we’re subscribed to. Is there a separate event type specifically for dependent changes, or should dependent additions trigger the same enrollment.updated event? We need proper system reconciliation between UKG Pro and our carrier integrations.
Another approach is to subscribe to the more general “employee.updated” event and then filter for benefits-related changes in your webhook handler. This event fires for any employee record modification, including dependent additions. The downside is you’ll receive a lot of noise (address changes, phone updates, etc.), so your handler needs robust filtering logic. But it ensures you don’t miss dependent changes while waiting for UKG to add more specific event types.
From my experience, dependent additions are treated differently than enrollment changes in the benefits module. The system might be classifying dependent adds as demographic updates rather than enrollment events. Have you checked if there’s a “benefits.dependent.updated” or “employee.demographic.changed” event that could capture these changes? Also, verify that your webhook endpoint is configured to receive all benefits-related events, not just enrollment-specific ones.
The issue is that UKG Pro 2023.1 treats dependent additions as a separate transaction from enrollment updates. They don’t automatically trigger the enrollment.updated webhook. You might need to implement a polling mechanism to check for dependent changes periodically, or use the benefits API to query dependent information after receiving an enrollment.updated event. It’s not ideal, but it’s a workaround until UKG improves the webhook event granularity.