Overview
With this integration you will connect Alexis HR to your PowerOffice Go 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 PowerOffice Go
Available in: Norway
Alexis requirements
You will need to generate an Access Token in your Alexis account in order to set up the integration with PowerOffice Go.
Please follow the instructions below:
If you are an Owner you can generate the Access token in Settings -> Access tokens
NB You can select whether the Access token should allow for API access to the Public API and/or the Provisioning API
Select Public for your PowerOffice Go integration
Enter a name for the Access Token eg. "PowerOffice Go"
Optionally add a description
Click Save to show the Access Token
Copy the Access Token and save it somewhere safe. You will need this later.
NB The token created will only be visible once, so make sure to keep it safe! The access token will be tied to the user who created it, so if the user that created the token has its permission changed or if it's removed the token will become invalid.
PowerOffice Go requirements
You need to have access to the following valid credentials.
PowerOffice Application Key
PowerOffice Client Key
PowerOffice Subscription Key
You can find the Application Key, Client Key and Subscription Key in your PowerOffice account by following these instructions:
Log in to your PowerOffice Go account and navigate to “Meny”
Select “Innstillinger”
Click on “Utvidelser”
4. Click “Legg til utvidelse”
5. Choose “Egendefinert” in the dropdown
6. Fill in “Applikasjonsnøkkel” with the Access Token you created in your Alexis account from the last section
7. Copy the field: Klientnøkkel. This is very important as you will need it later.
8. Click OK
Set up in Simployer
The integration is activated from Settings → Integrations → Select payroll system → Add integration
In the API Integrations section, select PowerOffice Go
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 PowerOffice Go by the user
This can be valuable if you have the scheduled sync turned off and want to control when data is synced to PowerOffice Go. 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 : 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 PowerOffice Go.
The scope selection follows the standard scope selection that exists in Alexis HR.
Employee data
Overview
Employee data is synchronized from Alexis HR to PowerOffice Go. This means that if data is updated in PowerOffice Go on "data fields" and then the sync from Alexis HR is done the data in PowerOffice Go 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 PowerOffice Go. 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.
Data fields
Alexis field | PowerOffice Go field | Mapping conditions and details |
Work section |
|
|
Employee.employeeNumber | Number | Required |
Employee.employeeNumber | ExternalNumber | This is the correlation ID used for Alexis-PowerOffice object. |
Employee.userId | ExternalImportReference |
|
Employee.workEmail | EmailAddress |
|
Employee.title* | JobTitle | Missing in mapping. |
Employee.active | !IsArchived | When an employee is off-boarded, Alexis will archive the user, thus we need to negate the active flag. |
Employee.hireDate | HireDate |
|
Employee.startDate | StartDate | If multiple employments exist, the start date from the oldest object is used. |
Employee.endDate | EndDate | If multiple employments exist, the end date from main employment or the most recent employment is used. |
Financial section |
|
|
Employee.bankAccount.number | ContactBankAccount.BankAccountNumber |
|
Employee.bankAccount.bankname | ContactBankAccount.BankCode |
|
Employee.bankAccount.bic | ContactBankAccount.BicSwift |
|
Employee.bankAccount.country | ContactBankAccount.CountryCode |
|
Personal section |
|
|
Person.firstName | FirstName |
|
Person.lastName | LastName |
|
Person.NationalIdList[0].NationalId | NationalIdNumber | NationalId is per default hidden in PowerOffice Go API, therefore it will only be synced upon creation, and it will NOT be updated or removed in PowerOffice Go if updated in Simployer. |
Person.Birthdate | DateOfBirth |
|
Person.Gender | Gender | Gender is per default hidden in PowerOffice Go API, therefore it will only be synced upon creation, and it will NOT be updated or removed in PowerOffice Go if updated in Simployer. |
Person.NationalIdList[0].Country | InternationalIdCountryCode |
|
Person.PhoneNumber | PhoneNumber |
|
Person.email | EmailAddress | Mapped only if workEmail is empty |
Person.Address.street1 | MailAddress.AddressLine1 |
|
Person.Address.street2 | MailAddress.AddressLine2 |
|
Person.Address.city | MailAddress.City |
|
Person.Address.postalCode | MailAddress.ZipCode |
|
Person.Address.Country | MailAddress.CountryCode | ISO-3166 Alpha-2 |
Employment (for each employment in Alexis) |
| HireDate, StartDate and EndDate is also set on the Employee (see above). |
Employment.StartDate | StartDate |
|
Employment.EndDate | EndDate |
|
| EndDateReason | Defaulted to “EmployeeHasResigned” |
| FullTimeHoursPerWeek | Defaulted to 37.5 |
Employee.MainEmploymentId | isDefault |
|
EmploymentId | ReportingId | This is the correlation key between Alexis and PowerOffice for each employment. |
Employment.EmploymentType | EmploymentForm | permanent_employment = Permanent |
Employment.Notes | ProfessionCode |
|
| EnterpriseId | Get default Enterprise from PowerOffice. Currently the integration will only sync with the default Enterprise in PowerOffice. |
| WorkingHoursArrangement | Defaulted to “NonShift” |
Compensation section |
| In PowerOffice compensations (salaries) are tied to an employment, but in Alexis it per employee. Therefore we only put the salaries on the default employment, if there are multiple. Any changes made on compensations will ONLY reflect on default employment as of now. |
Compensation.effectiveDate | FromDate |
|
Compensation.payoutPeriod | RemunerationType | ANNUAL = FixedWage MONTHLY = FixedWage HOURLY = HourlyWage |
Compensation.amount | AnnualSalary / HourlyRate | If Alexis payoutPeriod is “ANNUAL” or “MONTHLY” we use “AnnualSalary”, and in case of monthly salary it will be calculated to annual. If Alexis payoutPeriod is “HOURLY” we use “HourlyRate“. |