Skip to main content

The common model used when syncing HRIS to 7taps

7taps connects to your HRIS through Merge's unified API. Merge organizes HR data into a standard set of objects, called the common model, and we only read the specific objects and fields listed below.

This article covers what data moves and how. For help connecting your HRIS and importing people, see How to import learners from your HRIS.

How the sync works

Once your HRIS is connected, 7taps reads data from four objects: Employee, Employment, Group, and Location. For most HRIS systems, this sync runs automatically every 24 hours.

7taps only reads data. Nothing is written back to your HRIS.

Employee

Field

What it is

first_name

The employee's first name.

last_name

The employee's last name.

preferred_name

The employee's preferred first name.

display_full_name

The employee's full name for display. Includes the preferred first name when one is set.

personal_email

The employee's personal email.

work_email

The employee's work email.

mobile_phone_number

The employee's mobile phone number.

username

The employee's username as it appears in your HRIS.

employee_number

The employee's number as it appears in your HRIS.

employment_status

The employee's current employment status.

start_date

The date the employee started working. If the employee was rehired, this reflects the most recent start date.

termination_date

The employee's termination date.

date_of_birth

The employee's date of birth.

manager

The employee ID of the employee's manager.

home_location

The employee's home address. Links to the Location object below.

work_location

The employee's work address. Links to the Location object below.

groups

The employee's group memberships. Links to the Group object below.

employments

The employee's position record. Links to the Employment object below.

remote_created_at

When the employee record was created in your HRIS.

hire_date

Marked deprecated in Merge's model. Still synced today, but start_date is the more reliable field going forward.

Employment

Employment holds position-level details, separate from the employee record itself.

Field

What it is

employee

The employee holding this position. Links back to the Employee object above.

job_title

The position's title.

effective_date

The position's effective date.

Group

Field

What it is

name

The group's name.

type

The group type, as returned directly by your HRIS.

parent_group

The parent group, for organizations with nested groups.

Location

Field

What it is

name

The location's name.

location_type

Whether this is a WORK or HOME address.

street_1

Street address, line 1.

street_2

Street address, line 2.

city

City.

state

State, or region if outside the US.

zip_code

Zip or postal code.

country

Country.

phone_number

The location's phone number.

What 7taps does not sync

7taps does not sync payroll or compensation data. Pay rate, pay currency, pay frequency, and pay group are all excluded, and objects like Bank Info, Payroll Run, Employee Payroll Run, and Pay Group are not connected at all.

7taps does not sync protected-class or sensitive personal data. Social security number, ethnicity, gender, and marital status are all present in Merge's model but are not pulled into 7taps.

Objects not connected: Bank Info, Benefit, Company, Dependent, Employee Payroll Run, Employer Benefit, Pay Group, Payroll Run, Time Off, Time Off Balance, Timesheet Entry.

Did this answer your question?