Ceridian Dayforce
Ceridian Dayforce is a complete HRIS solution that helps organizations transform every core area of HCM including Continuous payroll, workforce management, benefits, talent management, and more.
DataLakeHouse.io provides the best data synchronization process from Ceridian into your Data Warehouse or Data Lake Storage so that you can integrate your other financial and operational sources for an enterprise view of your organization.
DataLakeHouse.io securely connects to your Ceridian Dayforce system. Using the form in the DataLakeHouse.io portal please complete the following steps:
- Enter a Name or Alias for this connection, in the 'Name/Alias' field, that is unique from other connectors.
- Enter in the 'Target Schema Prefix' field, a name that will be unique in your cloud warehouse destination database where you wish to replicate the data.
- Enter the 'Company Id' for this Ceridian Dayforce company information you are retrieving.
- Company IDs differ from your employee number and user name, which are specific to each individual user. Your Company ID is found in your initial Ceridian Welcome email or your HR/Ceridian Administrator will be able to provide your Company ID, which is unique to your organization
- The value of Company ID may be in the format of mycompanyname and will be unique to each of your Ceridian environments
- Ceridian has the following environments:
- Production
- Config
- Train
- Test / Stage
- Enter the 'User' for this Ceridian Dayforce company api integration
- It's a best practice to create a service account in your Ceridian Dayforce environment that has access to all API entities. You can control access to the individual entities and columns within DataLakeHouse.io that you want replicated into your Target Connection.
- Enable all entities (and relevant child nodes) under RESTful Services > Human Resources in the Web Services Field-Level Access tab of System Admin > Roles
- Enter the 'Password' credential for this Ceridian Dayforce company api integration
- Select the 'Environment' of Ceridian Dayforce - once the Connection is saved this cannot be changed. Create a new Source Connector if a different Environment is desired.
- Train = https://train.dayforcehcm.com/api/
- Test / Stage = https://stage.dayforcehcm.com/api/
- Config = https://config.dayforcehcm.com/api/
- Production = https://dayforcehcm.com/api/
- Click the Authorize Your Account button which will save the connection.
If any issues occur with the Ceridian.com authorization, simply return to the sources page in DataLakeHouse.io, edit this source and click the 'Authorize Your Account' or 'Re-Authorize Your Account' button. If any issues persist please contact our support team via the DataLakeHouse Support Portal.
If your Dayforce implementation needs to first connect to a non-Production environment, use one of the non-production options from the Environment dropdown. It is recommended that you create multiple connectors in this case as you cannot and should not mix environments in the same replication process. Thus, create one Ceridian Dayforce source connection and select the non-production environment option. Complete any synchronization testing to your target connection. When ready, create a new Ceridian Dayforce source connection and select the Production environment option, create a new Sync Bridge, etc. You can later disable any Sync Bridges that you were using the non-production connector to prevent any charges from that non-production source replication. Remember, utilization charges apply for any production or non-production environments.
It is rare that Ceridian Dayforce provides your company with an environment that is not one of the following:
- Production
- Config
- Train
- Test / Stage
However, if you do have a special environment, you will need to contact DataLakeHouse.io support or your DLH.io account manager in order to have the option to connect to a non-standard Dayforce environment.
The following Ceridian Dayforce entities are replicated to Snowflake. Ceridian makes changes to their API on a quarterly basis and we are notified in advance in order to incorporate these changes in a timely manner. These are the table names you will see in Snowflake and click to view a detailed description of each table and column:
- CERTIFICATION
- CONTACT_INFORMATION_TYPE
- COURSE
- DEDUCTION_DEFINITIONS
- DEPARTMENT
- DOCUMENT
- EARNING_DEFINITIONS
- EMPLOYEE
- EMPLOYEE_ADDRESS
- EMPLOYEE_AUS_SUPERANNUATION
- EMPLOYEE_AUS_SUPERANNUATION_RULE
- EMPLOYEE_BADGE
- EMPLOYEE_CAN_FEDERAL_TAX
- EMPLOYEE_CAN_PROVINCE_TAX
- EMPLOYEE_CAN_TAX_STATUS
- EMPLOYEE_CERTIFICATION
- EMPLOYEE_CLOCK_DEVICE_GROUP
- EMPLOYEE_COMPENSATION
- EMPLOYEE_CONFIDENTIAL_IDENTIFICATION
- EMPLOYEE_CONTACT
- EMPLOYEE_COURSE
- EMPLOYEE_DEFAULT_LABOR
- EMPLOYEE_DIRECT_DEPOSIT
- EMPLOYEE_DOCUMENT_MANAGEMENT_SECURITY_GROUP
- EMPLOYEE_EMERGENCY_CONTACT
- EMPLOYEE_EMPLOYMENT_AGREEMENT
- EMPLOYEE_EMPLOYMENT_STATUS
- EMPLOYEE_EMPLOYMENT_TYPE
- EMPLOYEE_ETHNICITY
- EMPLOYEE_HEALTH_WELLNESS
- EMPLOYEE_HR_INCIDENT
- EMPLOYEE_LOCATION
- EMPLOYEE_MANAGER
- EMPLOYEE_MARITAL_STATUS
- EMPLOYEE_ONBOARDING_POLICY
- EMPLOYEE_ORG_UNIT_INFORMATION
- EMPLOYEE_PAYROLL_TAX
- EMPLOYEE_PAYROLL_TAX_PARAMETER
- EMPLOYEE_PAY_ADJUSTMENT
- EMPLOYEE_PAY_GRADE_RATE
- EMPLOYEE_PAY_SUMMARY
- EMPLOYEE_PERFORMANCE_RATING
- EMPLOYEE_PROPERTY
- EMPLOYEE_PUNCH
- EMPLOYEE_PUNCH_TRANSFERS
- EMPLOYEE_RAW_PUNCH
- EMPLOYEE_RAW_PUNCH_EXTRA_DATA
- EMPLOYEE_RAW_PUNCH_LABOR_METRICS
- EMPLOYEE_ROLE
- EMPLOYEE_SKILL
- EMPLOYEE_SSO_ACCOUNT
- EMPLOYEE_TRAINING_PROGRAM
- EMPLOYEE_UNION_MEMBERSHIP
- EMPLOYEE_USER_PAY_ADJUST_CODE_GROUP
- EMPLOYEE_US_FEDERAL_TAX
- EMPLOYEE_US_STATE_TAX
- EMPLOYEE_US_TAX_STATUS
- EMPLOYEE_VETERANS_STATUS
- EMPLOYEE_WORK_ASSIGNMENT
- EMPLOYEE_WORK_ASSIGNMENT_MANAGER
- EMPLOYEE_WORK_CONTRACT
- EMPLOYMENT_STATUS
- EMPLOYMENT_STATUS_REASON
- HIGHLY_COMPENSATED_EMPLOYEE
- JOB
- LABOR_METRIC_CODE
- LABOR_METRIC_TYPE
- LOCATION_ADDRESS
- LOCATION_ADDRESS
- ORG_UNIT
- ORG_UNIT_CHILD
- ORG_UNIT_LEGAL_ENTITIES
- ORG_UNIT_PARENTS
- PAYEE
- PAYROLL_ELECTION
- PAY_CLASS
- PAY_GROUP
- PAY_GROUP_CALENDAR
- PAY_TYPE
- POLICY_ASSOCIATION
- POSITION
- PROJECT
- TRAINING_PROGRAM
For Employee Pay Summary, the last 10 days worth of records are always replicated in order to capture manual changes that may have occurred within Ceridian. For example, an employee submits a timesheet on a Friday and their manager makes a manually adjustment within Ceridian the following Tuesday prior to the pay period closing. The Ceridian API end point does not have a last updated date so we need to replicate the last 10 days of Pay Summary records.
The Ceridian Employee Pay Summary endpoint does not contain a last updated timestamp so DataLakeHouse is unable to determine a more graceful way of replicating the last changed Pay Summary record. Thus, this is why DataLakeHouse.io will always replicate the last 10 days worth of Pay Summary records to your Target Connection.
If you don't see your custom entities per your Dayforce configuration above don't worry. DataLakeHouse.io retrieves custom entities as well if they are accessible. After the first sync bridge synchronization to your target warehouse, if you do not see any anticipated custom schemas please contact our support team.
It's not uncommon for the credentials used for connecting to Ceridian Dayforce to not have all the necessary permissions to replicate all of the desired Entities. Within DataLakeHouse, when you check Logs & Monitoring, Monitoring, Filter errors/failures only you will see an entry below which indicates that the "Current users doe not have access to..." This message is generated by the Ceridian Dayforce API and is passed to DataLakeHouse.
The following are how to address common permission issues from within Ceridian Dayforce:
- Projects Entity
- You must enable Projects (and relevant child nodes) under RESTful Services > Human Resources in the Web Services Field-Level Access tab of System Admin > Roles.
- In addition to field-level access, you must enable Can Read for Projects under the Authorizations tab of System Admin > Roles.
- Your user role must have Projects enabled in the Features tab of System Admin > Roles.
- EmployeePayAdjustment Entity
- You must enable EmployeePayAdjustment (and relevant child nodes) under RESTful Services > Workforce Management in the Web Services Field-Level Access tab of System Admin > Roles.
- Enabled the Can Read 'Pay Adjustments' for the role in System Admin > Roles > Authorizations.
The Ceridian API only allows thirty (7) days worth of data to be loaded for certain entities (Employee Punches). In order to rectify this situation please follow these steps:
- Open your Ceridian Source Connector, click the Options tab and select a date for the Historical Load Start Date. This date should represent when data was first entered into your Ceridian environment. Next, go to the list of your Sync Bridges, click the Actions drop down for the desired bridge, click Mark Status as IDLE. Click Actions...Re-sync All History.
2. Another reason you may not be seeing all of the Employee Punch data is that you have manual punches in Ceridian. In order to replicate these manual punch es, go into Ceridian and
- You must enable EmployeePunch (and relevant child nodes) under RESTful Services > Workforce Management > EmployeePunch in the Web Services Field-Level Access tab of System Admin > Roles
When subscribing to the Enterprise Analytics Plan, you have access to the pre-built Ceridian Dayforce Analytics data model.
