Dayforce Integration

the dayforce integration allows you to push hired candidates from ashby directly into dayforce, removing the need for manual data entry after a hire is made once configured, you can send candidate and offer data to dayforce as part of your post hire workflow prerequisites a dayforce administrator account is required to complete configuration on both the ashby and dayforce sides permissions & access foundations legacy plus plus enterprise ❌ ❌ ✅ ✅ this feature is available on plus and enterprise plans only organization admins can set up and configure this integration how the integration works the dayforce integration works as part of your post hire workflow during setup, you select which dayforce fields you want to populate when creating an employee record each field you enable becomes an offer custom field in ashby, which your team fills out when creating an offer once the candidate is hired, you push their data to dayforce directly from the candidate profile ashby sends a combination of data from the candidate profile, values your team enters on the offer form, and a set of hardcoded placeholder values that dayforce requires to create a record but that most organizations prefer not to store in ashby data sent to dayforce the table below shows all fields ashby sends to dayforce, along with their source in ashby and the corresponding dayforce field field ashby data source dayforce field notes first name candidate profile firstname last name candidate profile lastname contacts candidate profile preferred name offer custom field commonname hire date built in start date offer field hiredate pre start date offer decided at date prestartdate start date built in start date offer field startdate salary built in salary offer field active role offer custom field requires a dayforce report to sync dropdown options department offer custom field direct manager offer custom field job offer custom field requires a dayforce report to sync dropdown options onboarding policy offer custom field org unit offer custom field requires a dayforce report to sync dropdown options pay class offer custom field pay group offer custom field pay type offer custom field pre start role offer custom field birth date hardcoded birthdate updated in dayforce after push culture hardcoded updated in dayforce after push gender hardcoded updated in dayforce after push ssn hardcoded socialsecuritynumber sent as 111 11 1111; updated in dayforce after push addresses hardcoded addresses updated in dayforce after push employment statuses partially hardcoded hardcoded values dayforce requires certain fields, including social security number (ssn), gender, birth date, and address, to create an employee record because most organizations prefer not to store sensitive personally identifiable information (pii) in ashby, ashby sends placeholder values for these fields your dayforce admin updates the actual values directly in dayforce after the candidate is pushed for example, ssn is sent as 111 11 1111 your dayforce admin can then update this to the employee's actual ssn in dayforce if your organization wants to store and send actual values for these fields, contact your csm to discuss options note that storing sensitive pii in ashby requires careful consideration of your data security requirements dayforce reports for dropdown fields dayforce does not expose dropdown option lists (such as jobs, org units, or active roles) via its api directly to bring these values into ashby, you create reports in dayforce using reports as a service (ras) each report should have two columns label the display name of the option xref the dayforce internal id for that option once you've created a report in dayforce, paste its name into the corresponding field in the ashby integration settings ashby uses the report to populate the dropdown options for that field ashby also checks that it can access all configured reports when you test your credentials setting up the integration step 1 enter your credentials in ashby, navigate to admin → integrations → dayforce and enter the following credentials provided by your dayforce administrator username password client name base url step 2 test your credentials once you've entered your credentials, select test credentials under the credential validation section ashby runs through all of the endpoints it needs access to and returns a pass/fail result for each this allows your dayforce administrator to confirm that the integration user has been set up with the correct permissions before completing the rest of the configuration if any reports have been configured, ashby also verifies that it can access those reports during the credential test step 3 configure employee fields in the employee fields section, select the dayforce fields you want to send when creating an employee record common fields include job, active role, org unit, pay group, and pay type for each dropdown field you enable, paste the name of the corresponding dayforce ras report into the report field under the reports section so ashby can sync the available options step 4 configure employee properties (optional) if you want to send custom employee properties from dayforce, you can add them in the employee properties section for each property paste the xref code of the property from dayforce enter a title for the property select the field type ; for example, string or number if the property is a dropdown, paste the name of the corresponding dayforce ras report step 5 configure the generated offer custom fields each field you enabled in steps 3 and 4 automatically appears as an offer custom field in ashby you can configure each field to fit your team's workflow required make the field required so it must be filled in before the offer is submitted default value set a default so recruiters don't have to select a value each time hidden if a default value is set, you can hide the field entirely so recruiters never see it this is useful for fields that always have the same value but are needed by dayforce conditions restrict the field to specific offer forms or job types so it only appears when relevant pushing a hired candidate to dayforce once a candidate has accepted their offer, signed any required documents, and been moved to the hired stage, you can push their data to dayforce navigate to the hired candidate's profile click select post hire integrations in the candidate's activities & progress feed check the box for dayforce and click add candidate you should see a success message appear in the bottom left corner of the screen once the push is successful, you can navigate to more in the upper right corner and select view external pushes to review the full data payload that was sent the candidate appears as a new employee record in dayforce your dayforce admin can then update any hardcoded placeholder values, such as ssn, gender, birth date, and address, with the employee's actual information if the push fails, ashby displays an error message in the bottom left, and you can similarly navigate to more and then view external pushes to view the error use this to identify what needs to be corrected before retrying faqs what happens to the hardcoded fields after i push a candidate? ashby sends placeholder values for fields like ssn, gender, birth date, and address — for example, ssn is sent as 111 11 1111 your dayforce admin updates these to the correct values directly in dayforce after the candidate is pushed you can configure some of the placeholder values we send as part of the integration configuration can i push the same candidate to dayforce more than once? \[author note confirm with arjun whether re pushing a candidate is supported and what the expected behavior is] what do i do if the push fails? if the push fails, ashby displays an error message with the data payload that was sent so you can see exactly what ashby attempted to send and what needs to be corrected if you're unable to resolve the error, email integrations\@ashbyhq com with your csm copied will ashby support bidirectional sync with dayforce? the current integration only supports pushing from ashby to dayforce bidirectional sync is not available at this time but may be considered in a future release