Skip to content
English
  • There are no suggestions because the search field is empty.

Time Entry - ADP Data Target Requirements

Time Entry - ADP Data Target Requirement

DataBlend supports the standard API calls to create a Time Entry leveraging the ADP SDK. In addition, custom fields can be added for data that is unique to your business practices.

Your query can include additional fields that are not listed below for informational purposes, they will not disrupt the data sent to ADP.

DataBlend Query Field Example 

ADP Object (API)

Required

Notes

1920339 associateoid Yes This can be retrieved from the Workers collector.
01/01/2025 entrydate Yes This will be the date the time applies to. Be mindful of multiple time entries for the same Worker on the same day across the same combinations of coding.
1 eventid No  
1234 workassignmentid Yes  
hoursentry entrytypecode Yes  
regular entrycode Yes  
PT8H0M timeduration Yes Be mindful of source data that may represent minutes as .5 hours for 30 minutes. ADP requires PT0H30M in this field for that value.
01/01/2025   startperiod   No If you are putting in the time duration for the amount of hours and minutes per day, you do not need to populate this field.
12/31/2025   endperiod   No If you are putting in the time duration for the amount of hours and minutes per day, you do not need to populate this field.
add changecode  Yes  
DEPT001 allocation.1 Optional The use of these custom fields will vary customer to customer. ADP can be configured to require these fields be populated on each time entry. There can be multipe custom fields in use and the next value would be allocation.2, etc. 

More questions about API requirements? Please visit the ADP API site https://developers.adp.com/guides/api-guides

Best Practices

  • Compare your incoming time data against the existing time entry to identify net change de-dupe the data you are sending to ADP.
  • Confirm the configuration settings within ADP for entering time prior to using the API. This can be accomplished by manually entering in a time entry to confirm requirements. You are then able to collect that data via the API to confirm the field and value IDs assigned to that data.