Custom benefit enrollment fields not saving values after employee submission

HCM ADP Workforce Now
, , , , , , , ,
1

We’ve added custom fields to our benefits enrollment module to capture additional dependent information (SSN verification status, healthcare provider preferences). The fields display correctly during enrollment, but values aren’t persisting after employees submit their selections.

The custom field mapping appears correct in the configuration panel, and we’re using the standard enrollment workflow. When checking the API payload structure during submission, I notice the custom fields are present but seem to be ignored:

{
  "enrollmentId": "ENR-2024-001",
  "customFields": [
    {"fieldId": "CF_SSN_VERIFY", "value": "pending"}
  ]
}

Payroll integration is affected because these fields drive eligibility calculations. Has anyone encountered similar issues with custom benefit fields in ADP 2022.2? Is there a specific API endpoint or workflow configuration step we’re missing?

2

Since payroll eligibility is affected, verify that your custom fields are included in the benefits-to-payroll data bridge configuration. Even if enrollment saves the values, they won’t flow to payroll calculations unless explicitly mapped in the integration settings. Navigate to Integration Hub > Payroll Bridge > Field Mapping and add your custom field IDs to the benefits data export profile. Without this, payroll sees the enrollment as complete but misses the custom attributes needed for eligibility rules.

3

Looking at your symptoms, this is a multi-layer configuration gap. I’ve debugged this exact scenario three times. Here’s the complete fix:

1. Custom Field Mapping (Core Issue) Your fields need proper schema registration. Go to Benefits Admin > Configuration > Custom Fields and verify:

  • Field Type matches data structure (text/select/date)
  • Persistence Layer is set to ‘Benefits Transaction Store’ not ‘UI Cache’
  • Mapping Target includes both ‘Enrollment Record’ AND ‘Employee Benefit Profile’

2. Enrollment Workflow Configuration The workflow must explicitly handle custom fields:

  • Edit your enrollment workflow template
  • Add ‘Custom Field Commit’ action after ‘Standard Enrollment Save’
  • Configure action to target your field IDs: CF_SSN_VERIFY, CF_PROVIDER_PREF
  • Set commit timing to ‘Immediate’ not ‘Batch’

3. API Payload Structure (Your Code Needs Update) Your JSON is missing critical metadata. Use this structure:

{
  "enrollmentId": "ENR-2024-001",
  "enrollmentType": "benefits",
  "customFieldData": {
    "fields": [
      {
        "fieldId": "CF_SSN_VERIFY",
        "fieldType": "select",
        "value": "pending",
        "persistenceLayer": "transaction",
        "validationRules": "benefits_standard"
      }
    ],
    "commitStrategy": "immediate"
  }
}

The key differences:

  • Use ‘customFieldData’ wrapper with ‘fields’ array
  • Include persistenceLayer specification
  • Add commitStrategy to force immediate save

4. Payroll Integration Bridge For eligibility calculations to work:

  • Integration Hub > Benefits-Payroll Connector
  • Add custom fields to ‘Eligibility Data Export Profile’
  • Map CF_SSN_VERIFY to payroll eligibility field PE_VERIFY_STATUS
  • Enable ‘Real-time Sync’ for these fields

5. Verification Steps After configuration:

  • Test enrollment with API logging enabled
  • Check database table BENEFITS_CUSTOM_FIELDS for persisted values
  • Verify payroll eligibility calculations receive custom field data
  • Monitor enrollment audit logs for field commit confirmations

Common Gotcha: If you’re on 2022.2 base version (pre-2022.2.3), there’s a known bug where custom fields in benefits enrollment require a specific API header: ‘X-ADP-Custom-Fields-Enabled: true’. This was fixed in 2022.2.3 but remains necessary in earlier builds.

This addresses all three focus areas: proper field mapping configuration, complete enrollment workflow setup, and correct API payload structure with persistence specifications. The solution ensures custom fields flow correctly from enrollment through to payroll eligibility calculations.

4

I’ve seen this before. Check if your custom fields are properly registered in the Benefits Admin metadata repository. The enrollment workflow configuration needs explicit field binding, not just UI display mapping. Go to System Configuration > Benefits > Custom Field Registry and verify each field has both ‘Enrollment Capture’ and ‘Data Persistence’ flags enabled. Without proper registration, fields show up in the UI but the backend ignores them during save operations.

5

Are you using the Benefits Enrollment API v2 or v3? Version 2 had known limitations with custom field handling that were fixed in later patches. If you’re on 2022.2 without the latest service pack, custom fields in enrollment payloads may fail silently. Check your API version in the request headers and consider upgrading to at least 2022.2.5 where custom field persistence was significantly improved. The field mapping configuration alone won’t help if the API version doesn’t support it properly.

6

We had this exact issue last year. The problem was our custom fields weren’t mapped to the correct enrollment event trigger. Check your workflow configuration - specifically the ‘Post-Enrollment Actions’ section. Custom fields need to be explicitly included in the data commit phase, otherwise they’re treated as UI-only metadata. Also, make sure your payroll integration mapping references these custom field IDs in the eligibility calculation rules.

7

The API payload structure looks incomplete. For custom fields in benefits enrollment, you need to include the field type and validation schema. Try this format instead:

{
  "customFields": [{
    "fieldId": "CF_SSN_VERIFY",
    "fieldType": "select",
    "value": "pending",
    "validationSchema": "benefits_v2"
  }]
}

Also verify the endpoint you’re hitting supports custom field persistence. Some older enrollment APIs in 2022.2 don’t handle custom attributes correctly.