We are working on an API with vendor and are having an issue with EmployeeManager.

Originally replied by Eddie Heinzelman on Jun 18, 2026, 2:59 PM.

and what is EmploymentStatusGroupXrefcode? That's not outlined in the Employment Status segment so is it "Employee" or is it "Active" or something else?

If it's not required, that's ok. Just not familiar with this element.

Originally replied by Frank Ruffolo on Jun 18, 2026, 3:03 PM.

But all Statuses, whether custom status or not roll up into an EmploymentStatusGroupXrefcode of either Active, Inactive or Terminated.

Originally replied by Frank Ruffolo on Jun 18, 2026, 3:02 PM.

It shouldn't be required as part of the Manager POST

Originally replied by Eddie Heinzelman on Jun 18, 2026, 3:05 PM.

Appreciate the help!!

Originally replied by Eddie Heinzelman on Jul 2, 2026, 1:29 PM.

@Frank Ruffolo​  as follow up: This worked. The manager now comes over. There is an interesting issue in Dayforce though: The manager comes over seemingly fine with the employee in pre-start status, but when the status changes to Active, the manager record end dates. There are a ton of fields in the EmployeeWorkAssignmentManager but when I do a GET on this, I only get the following results (for an active employee that shows correctly) - so now, the question is do we need to send all of these fields? OR is this some other function where because we are applying the manager on a pre-start that Dayforce would terminate the manager record regardless?

There are no errors in what we are bringing over - just the Start Date, the Managerxrefcode - we are not bringing in the Location and Position currently. Do we have to in order to keep the record from end dating?

{

  "Data": [

    {

      "EffectiveStart": "2025-09-18T00:00:00",

      "EmploymentStatusGroupXRefCode": "ACTIVE",

      "ManagerXRefCode": "0030382",

      "ManagerName": "ManagerName Redacted 0030382",

      "ActiveEmployeePosition": {

        "XRefCode": "OPERATIONS_STORE_MANAGER_H",

        "ShortName": "Operations - Store Manager (H)"

      },

      "ActiveEmployeeLocation": {

        "XRefCode": "02800",

        "ShortName": "02800"

      },

      "LastModifiedTimestamp": "2026-06-02T08:31:53.143"

    }

  ]

}

Originally replied by Frank Ruffolo on Jul 3, 2026, 9:14 AM.

Hey @Ted Fifield​  can you comment on the Manager being end dated after the employees moves from Pre-Start to Active? Is that expected?

Originally replied by Ted Fifield on Jul 7, 2026, 5:16 PM.

@Eddie Heinzelman​ @Frank Ruffolo​ - The Manager Recalc logic will automatically end-date the EmployeeWorkAssignmentManager record associated with the Employee when the corresponding EmployeeWorkAssignment ends. In this case, the employee's Pre-Start EWA record is end-dated when the employee transitions from Pre-Start status to Active status following their onboarding period.

A new Primary EWA record will begin on the same EffectiveStart date as the Active EmployeeEmploymentStatus. The employee should then have a new manager assignment based on the client's configuration:

• Automatically inherited from the manager assigned to the Job record (Derived By Job)
• Automatically inherited from the manager assigned to the Location record (Derived By Org)
• Manual assignment of a new manager (RESTful, Import, UI, Forms, etc.)

If I'm interpreting correctly, this client is manually assigning managers to their employees. In that case, I would recommend creating a new manager assignment that aligns with the Effective Dates of the employee's Primary EWA record once they become Active in the system.