Workday to AD User Provisioning : Unable to receive StatusTerminationDate and ContractEndDate

StatusTerminationDate and ContractEndDate are retrieved only if the underlying Workday XPATH expressions match the Workday Web Services (WWS) API version configured in the provisioning app and if the corresponding data set is included in the Get_Workers response.

For a WWS API version 40+ URL, the following must be in place:

1. Ensure XPATHs are updated for v30+ schemas
   • The Workday inbound provisioning app ships with default XPATHs for v21.1. When a higher WWS version (such as v40.0) is specified in the Workday URL, the default v21.1 XPATHs can fail to resolve attributes.
   • Resolution requires updating the XPATH API expressions under Attribute Mapping → Advanced Options → Edit attribute list for Workday to the v30+ values documented in the Workday attribute reference.
   • For StatusTerminationDate on v30+ the documented XPATH is:
     • wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Status_Data/wd:Termination_Date/text()
   • If this XPATH is already configured but the provisioning app still does not retrieve the attribute, verify that the XPATH list as a whole has been updated to the v30+ set and not left in the v21.1 default state while using a v40 URL.
2. Verify the correct Workday entities are requested
   • The Get_Workers API returns data based on the XPATH patterns present in the mapping. For status-related attributes (including StatusTerminationDate), the provisioning service relies on Employment Data:
     • wd:Worker_Data/wd:Employment_Data
   • Ensure mappings include XPATH patterns that pull Employment_Data and Worker_Status_Data so that the Response_Group flags are set correctly and the status data is returned.
3. Address version mismatch issues
   • If attributes like StatusTerminationDate are not being retrieved while using a v40 URL, this is a known symptom of XPATH definitions not aligned with the WWS version.
   • Two supported options:
     • Option 1: Remove the explicit WWS version from the Workday URL so the app uses the default v21.1 API and the shipped v21.1 XPATHs.
     • Option 2: Keep the v40 URL and manually update all XPATH API expressions to the v30+ equivalents as documented in the Workday attribute reference.
4. ContractEndDate specifics
   • ContractEndDate is not part of the default attribute list and must be added as a custom XPATH.
   • For custom attributes on v30+ (and higher), the guidance is to:
     • Add the attribute under Edit attribute list for Workday.
     • Use a v30+ compatible XPATH and test it against the tenant following the instructions in the “Managing your configuration” section.
   • If multiple candidate XPATHs have been tried and none return data, validate in Workday that:
     • The corresponding contract-related entities are included in the Get_Workers response for the worker(s) being tested.
     • The XPATH is aligned with the actual structure for the tenant’s WWS version (using the same approach as for other custom attributes like Universal ID or Management Level ID, which are explicitly documented for v30+).
5. Troubleshooting approach
   • Confirm that the provisioning app is not in a mixed state (v40 URL with v21.1 XPATHs). If it is, either:
     • Switch back to a versionless URL (default v21.1), or
     • Fully adopt the v30+ XPATH set and retest.
   • After updating XPATHs or adding ContractEndDate:
     • Save the attribute list and mappings.
     • Clear the current state and restart a full sync so the new attributes are requested and evaluated.

Following these steps ensures StatusTerminationDate is retrieved via the documented v30+ XPATH and that ContractEndDate is implemented as a tested custom XPATH compatible with the WWS v40+ endpoint.

References:

• Workday attribute reference for Microsoft Entra ID
• How Microsoft Entra provisioning integrates with Workday
• Configure Workday for automatic user provisioning with Microsoft Entra ID
• Troubleshoot HR attribute retrieval issues