BirdDogHR has partnered with Core HR to provide customers with an integrated solution. This document is intended to provide a list of fields and how they are mapped between the two systems.
Employee Data Mapped from BirdDogHR Onboarding to Core HR
BirdDogHR | Core HR | Required | Format | Notes |
---|---|---|---|---|
Social Security Number | SSN / Employee ID [key] | Y | xxxxxxxxx | 9 characters – no dashes necessary |
First Name | First Name | Y | Text | Up to 30 characters |
Middle Name | Middle Name | Text | Up to 30 characters | |
Last Name | Last Name | Y | Text | Up to 30 characters |
Suffix | Suffix | Text | Up to 30 characters | |
Address Line 1 | Street 1 | Y | Alphanumeric Text | Up to 50 characters |
Address Line 2 | Street 2 | Alphanumeric Text | Up to 50 characters | |
Employee City | City | Y | Text | Up to 30 characters |
State | State | Y | System Defined | 2 characters |
Zip Code | Zip | Y | Numeric Text | Up to 15 characters |
Home Phone Number | Home Phone | Text | Up to 20 characters | |
Mobile Phone Number | Mobile Phone | Text | Up to 20 characters | |
Employee Email Address | Home Email | Text | Up to 20 characters | |
Work Phone | Text | |||
Date of Birth | Birth Date | Y | MM/DD/YYYY | |
Birth Location | Text | |||
Gender | Gender | Y | System Defined (M, F, U) | Limited to 1-character, blank values will pass “U” |
Marital Status | Marital Status | Y | System Defined (Single, Married) | Blanks will pass over “undefined” |
Tobacco User | System Defined (True/False) | |||
Handicapped | System Defined (True/False) | |||
Employee ID | Numeric Text | |||
Hours Worked | Numeric Text | |||
Work Email | Text | |||
Employee Status | Y | System Defined | BDHR will send over “undefined” | |
Department | Client Defined | |||
Location | Facility 1 Name | Client Defined | ||
Facility 2 Name | Client Defined | |||
Job Code | Job Code | Client Defined | Up to 50 characters | |
Employment Type | Employee Type | Client Defined | ||
Start Date | Hire Date | Y | MM/DD/YYYY | Blank values will pass “undefined” |
Original Hire Date | MM/DD/YYYY | |||
Alternate Service Date 1 | MM/DD/YYYY | |||
Alternate Service Date 2 | MM/DD/YYYY | |||
Benefit Eligibility Date | MM/DD/YYYY | |||
Benefit Status | Y | System Defined | BDHR will send over “undefined” | |
Retirement Date | MM/DD/YYYY | |||
Termination Date | MM/DD/YYYY | |||
Termination Reason | Client Defined |
BirdDogHR | Core HR | Required | Format | Notes |
---|---|---|---|---|
Job Title | Title | Text | Up to 150 characters | |
Pay Schedule | Client Defined | |||
Race Ethnicity | EEOC Ethnicity | Client Defined | Up to 75 characters | |
EEOC Occupation | Client Defined | |||
EEOC Workers Compensation | Client Defined | |||
User Defined Field 1 | Text | |||
User Defined Field 2 | Text | |||
User Defined Field 3 | Text | |||
User Defined Field 4 | Text | |||
User Defined Field 5 | Text | |||
User Defined Field Lookup 01 | Client Defined | |||
User Defined Field Lookup 02 | Client Defined | |||
User Defined Field Lookup 03 | Client Defined | |||
User Defined Field Lookup 04 | Client Defined | |||
User Defined Field Lookup 05 | Client Defined | |||
User Defined Field Lookup 06 | Client Defined | |||
User Defined Field Lookup 07 | Client Defined | |||
Custom Field with mapping ID = “UDF1” | User Defined Field Lookup 08 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF2” | User Defined Field Lookup 09 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF3” | User Defined Field Lookup 10 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF4” | User Defined Field Lookup 11 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF5” | User Defined Field Lookup 12 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF6” | User Defined Field Lookup 13 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
Custom Field with mapping ID = “UDF7” | User Defined Field Lookup 14 | Client Defined | If blank, or doesn’t exist, BDHR can leave blank | |
User Defined Field Lookup 15 | Client Defined | |||
ACA Employee Status | System Defined (Full Time, Part Time, Seasonal, Variable) | |||
Additional Household Income | Text | |||
Country | Country | System Defined (United States of America) | Up to 150 characters | |
Country populated from Address, not passport | ||||
EEO Class | System Defined (1.1, 1.2, 2, 3, 4, 5, 6, 7, 8, 9) | |||
Work Phone Extension | Text | |||
Payroll Hours Worked | Text | |||
Payroll Auto Pay | Text | |||
Pay Rate Type | Pay Type Salary | System Defined (Hourly, Salary) | 3 characters | |
Payroll Frequency | Client Defined |
Important Notes:
- Data will be pushed from Core HR to BirdDogHR on a nightly basis.
- Once an employee is created through the integration, the system will only update any changes to the employee record from Core HR. This allows customers to assign users to Job Codes, Locations, etc. in BirdDogHR and the system will retain those assignments.
- All fields listed will be populate upon create. Fields that will be impacted upon update are noted.
Employee Data Mapped from Core HR to BirdDogHR LMS/Performance
From Core HR | To BirdDogHR | On Update | Required | Notes |
Username | No | Yes | ||
Active Status | Yes | Yes | ||
Last Name | Yes | Yes | ||
First Name | Yes | Yes | ||
Middle Initial | Yes | No | Truncated to the first letter | |
Display Name | Yes | No | ||
Employee ID | Yes | Yes | ||
Yes | Yes | |||
Home Phone | Yes | No | ||
Mobile Phone | Yes | No | ||
Job Code | No | Yes | Default Value | |
Job Title | Yes | No | ||
Manager | No | Yes | If not available in Core HR, will default to “ToBe Assigned” | |
Location | No | Yes | Default Value | |
Is Manager | No | Yes | TRUE/FALSE | |
Gender | Yes | No | ||
Hire Date | No | Yes | ||
Last Promotion Date | Yes | No | ||
Last Raise Date | Yes | No | ||
Termination Date | Yes | No |
Important Notes:
- Data will be pushed from Core HR to BirdDogHR on a nightly basis.
- Upon creation of BDHR Talent instance, BDHR Implementation Specialist will create a User with the following information:
- Username: ToBeAssigned@HRIS.com
- First Name: ToBe
- Last Name: Assigned
- Display Name: ToBe
- Email: ToBeAssigned@HRIS.com
- Employee ID: ToBeAssigned
- Supervisor: System Administrator
- Job Code: ToBeAssigned (1)
- Location: ToBeAssigned (1)
- Hire Date: 12/31/2050
(1) Creating a new Job Code and Location is not necessary; Job Code and Location for “ToBe Assigned” can also use an existing Job Code and/or Location.
Stress the importance of ensuring that options available in IHR’s User Defined Fields match available options in BDHR
User Defined 06 = Job Code