Overview
With this integration you will connect Alexis HR to your 24Seven office account via API and can then do the following:
Scheduled 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
Available in: Norway
24Seven Office requirements
You need to have access to the following valid credentials.
Access token: this can be found in here in your 24Seven Office account
Navigate to 24Seven Office Lønn
Click on Innstillinger
Select Diverse innstillinger
Select API, e-post, integrasjoner
Select Administer integrasjoner
Adding the integration
The integration is activated from Settings → Integrations → Add Integration (in the "Integrate with payroll system" section).
In the API Integrations section, select 24Seven Office
Click Next to start the configuration wizard
Enter all the details needed for the connection
Settings
You can choose how the integration sync for employees is executed. The options available are as follows:
Manual sync
The data is manually synced to 24Seven Office by the user
This can be valuable if you have the scheduled sync turned off and want to control when data is synced to 24Seven Office. Either during the implementation phase or during times when an update is not wanted due to process and payroll timing
Manual syncs can be performed even when a scheduled sync is configured. This may be necessary if there have been a significant number of changes in Alexis HR after a scheduled sync has been executed
Scheduled sync
The sync runs on a schedule that you can define
Options include the day(s) of the week and the time of day for the sync to be executed
Note: when a scheduled sync is enabled, it is queued and executed shortly after 06:00 CET the following day.
Scope
Scopes allow more granular filters that determine which employees are included in the employee sync
This is especially useful if you require a specific set of employees to be excluded from the export to 24Seven Office
Scopes follow the same scope behavior as seen in other Alexis HR features
Employee data
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 or have a default value, see the table below for more information.
Data fields
Alexis field | 24Seven Office field | Mapping conditions |
Work |
|
|
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 | Defaulted to “25” |
| Employee.internationalID.type | Defaulted to “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 the bank account country is not Norway, the bank account number is retrieved from the IBAN field. |
BIC | Employee.bic |
|
Clearing number | Employee.clearingno |
|
Employment |
|
|
Start date | Employment.startdate |
|
End date | Employment.endDate |
|
Employment type | Employment.employment_form | If the type contains “temporary” then it is mapped to “midlertidig”.
Otherwise, it is mapped to “fast”. |
Employment rate | Employment.employment_rate |
|
Employment.note | Employment.profession_code | The profession code is retrieved from the Employment.note (before the colon) and mapped to profession_code.
For example, if the note is: 0111101:7
|
Employment.note | Employment.enddate_reason | The enddate_reason is retrieved from the Employment.note (after the colon) and mapped to the enddate_reason.
1: arbeidsforholdetSkulleAldriVaertRapportert 2: arbeidsgiverHarSagtOppArbeidstaker” 3: arbeidstakerHarSagtOppSelv” 4: byttetLoenssystemEllerRegnskapsfoerer” 5: andringIOrganisasjonsstrukturEllerByttetJobbInternt 6: kontraktEngasjementEllerVikariatErUtloept |
n/a | Employment.working_times | Defaulted to “ikkeSkift” |
n/a | Employment.employment_type | Defaulted to “ordinaertArbeidsforhold” |
Compensation |
|
|
Compensation.effectiveDate | Employee.salary_valid_from | Where Compensation.effectiveDate is the most recent among compensation objects for this employee |
Compensation.payoutPeriod | Employee.salary_type | Where Compensation.effectiveDate is the most recent among compensation objects for this employee |
Compensation.amount | Employee.salary | Where Compensation.effectiveDate is the most recent among compensation objects for this employee |
Absence data
Absence data is synchronized from Alexis HR to 24Seven Office. This means that if data is updated in 24SevenOffice on "data fields" and then the sync from Alexis HR is done the data in 24Seven Office will be overwritten.
When the sync is executed, it will compare the data in Alexis for the "data fields" to see if there is a difference between the values for those fields in 24Seven Office. If there is no change, the user will not be updated. If there is a change present, the data will be updated.
Some fields are currently hardcoded, see below for more information.
Alexis field | 24Seven Office field | 24Seven Office field |
Self-certified sick leave | Global leave type | 01 - Sykmelding |
Care of sick child | Global leave type | 02 - Sykt barn |
Self certified sick leave | Global leave type | 03 - Egenmelding |
Vacation | Global leave type | 04 - Ferie |
Off duty | Global leave type | 05 - Permittering |
Parental leave | Global leave type | 06 - Foreldrepenger |
Military service | 07 | 07 - Militærtjeneste |
Educational leave statutory | 10 | 10 - Utdanningspermisjon - lovfestet |
Educational leave non statutory | 11 | 11 - Utdanningspermisjon - ikke lovfestet |
Other leaves statutory | 12 | 12 - Andre permisjoner - lovfestet |
Other leaves non statutory | 13 | 13 - Andre permisjoner - ikke lovfestet |
Palliative care benefit | 14 | 14 - Pleiepenger livets siste faser |
Care benefit sick child | 15 | 15 - Pleiepenger sykt barn |
Childcare sickness days | 16 | 16 - Omsorgspenger (sykt barn dager) |
Training benefit | 17 | 17 - Opplæringspenger |
Pregnancy benefit | 18 | 18 - Svangerskapspenger |
Maternity leave parental benefit | 19 | 19 - Svangerskapspermisjon (foreldrepenger) |
Care leave | 20 | 20 - Omsorgspermisjon |
Other absences | 21 | 21 - Annet fravær |