Current status BETA
Note: this is an add-on to the core-packages and needs to be activated and purchased separately.
Time Off data - coming soon!
Overview
With this integration you will connect Alexis HR to your 24Seven Office account through API and can then do the following:
Scheduled and/or manual sync of employee data such as personal information, employment data, compensation data and more from Alexis HR to 24Seven Office.
Sync time off data such as sickness, parental leave and vacations to 24Seven Office for the period that you choose. You have full control over what absences are exported for what employees and for what period.
Requirements
The following requirements is needed to for the integration.
24Seven Office
You need to have access to the following valid credentials
Access token
Created from 24Seven Office Lønn → Innstillinger → Diverse innstillinger → API, e-post, integrasjoner → Administer integrasjoner
Alexis HR
Valid Access token for Public API
At-least one Access token for Public API needs to be created that will be used to connect the two systems. If you have not created an access token you need to do that from Settings - Access tokens
Configuration
The integration is activated from Settings → Integrations → Integrate with payroll system → Add Integration
Select 24Seven Office.
Click Next to start the configuration wizard.
Enter all the detail needed for the connection
Settings
You can choose how the integration sync for employees is done. Options are as follows
Manual sync : The data is synced to 24Seven Office with manual interaction.
This can be valuable if you have the scheduled sync turned off and want to control when data is updated in 24Seven Office. Either during implementation phase or during times when an update is not wanted due to process reason.
Manual sync can be performed even when there is a scheduled sync. This could be if there are a lot of changes done in Alexis HR after the scheduled sync has run.
Scheduled sync.
The sync runs at a schedule that you decide. Options are what day(s) of week the sync should start to run.
Note : Currently the sync is queued and it starts shortly after 06:00 CET.
Scope
The edit scope settings allows for more granularity on what employee will be part of the automatic or manually triggered employee export. This is useful if you know that not all of the employees should be exported to 24Seven Office.
The scope selection follows the standard scope selection that exists in Alexis HR.
Employee data
Overview
Employee data is synchronized from Alexis HR to 24Seven Office. This means that if data is updated in 24Seven Office on "integration data fields" and then the sync from Alexis HR is done the data in 24Seven Office will be overwritten.
When the sync runs it will compare the data in Alexis for the "integration data fields" to see if there is a difference vs the data for those fields in 24Seven Office. If no change then the user will not be updated. If there is a change the data will be updated.
Some fields are currently hardcoded, see below for more information.
What employees are exported?
Integration Data fields
Alexis field | 24SevenOffice field | Mapping conditions |
Work Section |
|
|
Employee number | Employee.empId |
|
Work email | Employee.email | If workEmail is empty, privateEmail is used |
Personal |
|
|
First name | Employee.firstname |
|
Last name | Employee.lastname |
|
Employee.ssn | Employee.personnr |
|
| Employee.vacation_days | Hardcoded as “25” |
| Employee.internationalID.type | Hardcoded as “socialSecurityNumber” |
Employee.ssn | Employee.internationalID.ID |
|
Nationality | Employee.internationalID.countryCode |
|
Home address - Street name | Employee.postaddress |
|
Home address - City | Employee.city |
|
Home address - Zip code | Employee.zipcode |
|
Home address - Country | Employee.countryCode |
|
Financial |
|
|
Bank account | Employee.account | If Bank account country is not Norway number is taken from IBAN field. |
BIC | Employee.bic |
|
Clearing number | Employee.clearingno |
|
Employment |
|
|
Start date | Employment.startdate |
|
End date | Employment.endDate |
|
Employment type | Employment.employment_form | if type contains “temporary” then mapped as “midlertidig”. Otherwise it is mapped as “fast”. |
Employment rate | Employment.employment_rate |
|
Employment.note | Employment.profession_code | Number from the employment note (before the colon) is mapped to the profession code.
Example : If note = 0111101:7 , then 0111101 is sent as profession code |
Employment.note | Employment.enddate_reason | Number from the employment note (AFTER the colon) is mapped to the enddate reason.
1→ arbeidsforholdetSkulleAldriVaertRapportert 2→ arbeidsgiverHarSagtOppArbeidstaker” 3→ arbeidstakerHarSagtOppSelv” 4→ byttetLoenssystemEllerRegnskapsfoerer” 5→ andringIOrganisasjonsstrukturEllerByttetJobbInternt 6→ kontraktEngasjementEllerVikariatErUtloept |
n/a | Employment.working_times | hardcoded as “ikkeSkift” |
n/a | Employment.employment_type | hardcoded as “ordinaertArbeidsforhold” |
Compensation |
|
|
Compensation.effectiveDate | Employee.salary_valid_from | Where Compensation.effectiveDate is the most recent among compensations for this employee |
Compensation.payoutPeriod | Employee.salary_type | Where Compensation.effectiveDate is the most recent among compensations for this employee |
Compensation.amount | Employee.salary | Where Compensation.effectiveDate is the most recent among compensations for this employee |
Time Off data
Time off data is handled from Manage Time → Export time off.
Coming soon!