PowerOffice Go integration
Reference General Setup
For configuring this integration, please complete the Simployer HRM Integration – General Setup Guide. This guide covers the initial steps for setting up integrations in Simployer and ensures that you have configured the necessary base settings for successful data sync.
Overview:
With this integration you will connect Simployer 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 Simployer to PowerOffice Go
Available in: Norway
PowerOffice Go requirements
You need to have access to the following valid credentials:
PowerOffice Client Key
You can find the Client Key in your PowerOffice account by following these steps:
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 2ab06c32-a351-4928-828c-fe97a35064d5 to select the Simployer integration
7. Copy the field: Klientnøkkel. This is very important as you will need it later.
8. Click OK
Employee data
Overview
Employee data is synchronized from Simployer to PowerOfficeGo. This means that if data is updated in PowerOfficeGo on "data fields" and then the sync from Simployer is done the data in PowerOffice Go will be overwritten.
When the sync is executed it will compare the data in Simployer 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.
Note:
1. The matching key for an employment is Employment Start Date + Profession Code. If either changes, PowerOffice will create a new employment record instead of updating the existing one.
2. NationalId and Gender are by default hidden in Poweroffice and they would not get updated on their own.
Few Hardcoded values:
- Employment type: Ordinary
- Working hours arrangement: NonShift
- Hours per week: 37.5
Data fields
Simployer field | PowerOffice Go field | Mapping conditions and details |
Work section |
|
|
Employee.employeeNumber | Number | Required |
Employee.employeeNumber | ExternalNumber | This is the correlation ID used for Simployer-PowerOffice object |
Employee.userId | ExternalImportReference |
|
Employee.workEmail | EmailAddress |
|
Employee.title* | JobTitle | Missing in mapping. |
Employee.active | !IsArchived | When an employee is off-boarded, Simployer 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 Simployer) |
| 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 Simployer and PowerOffice for each employment. |
Employment.EmploymentType | EmploymentForm | permanent_employment = Permanent |
Employment.Notes | ProfessionCode | 7 digit occupational code is mandatory. Accepted format: a 7-digit code on its own (e.g. 3120105) OR 7 digits followed by a description (e.g. 3120105 - Computer Engineer) |
| 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 Simployer 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 Simployer payoutPeriod is “ANNUAL” or “MONTHLY” we use “AnnualSalary”, and in case of monthly salary it will be calculated to annual. If Simployer payoutPeriod is “HOURLY” we use “Hou |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article