Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

Since

  • September 15, 2026
  • 4 replies
  • 0 views

Originally posted by Hong Zhao on February 9, 2026 at 5:24 PM.

 

  1. Since EmployeeNumber can be explicitly provided in the API request, independent of any internal employee-number–generation logic, is it acceptable for us to supply our own employee number in the request?
  2. Additionally, if we use a 15-digit employee number, could this cause any issues in Dayforce? Do you know of any other clients who are using employee numbers of this length? example: { "EmployeeNumber": "260209101712627" }

 

Thanks,

Hong

 

    4 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Saad Butt on Feb 11, 2026, 10:53 AM.

     

    Thanks Aravin. Just curious, I've noticed we can assign duplicate employee numbers this way. Doesn't this cause database integrity issues i.e. is the employee number not a database id?

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Aravindan Balasubramanian on Feb 11, 2026, 10:13 AM.

     

    Answer for the 1st. Yes, it is acceptable to send your own employee number, the standard practice is to keep employee number same as the EmployeeXrefcode.

     

    Answer for 2nd, You should be okay with 15.The max length for this field is 40. Best practice: Is to confirm with the Dayforce Implementation Team involved in the particular project to confirm downstream impacts as every customer is different (Integration with other systems, Exports etc.)

     

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Aravindan Balasubramanian on Feb 11, 2026, 11:03 AM.

     

    EmployeeXrefcode/ReferenceCode is how we maintain Data Integrity and it is unique.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Saad Butt on Feb 11, 2026, 12:10 PM.

     

    Thanks!