PowerOffice GO integration
Connect Huma to PowerOffice GO to keep employee profiles and employment details in sync
Table of contents
- Introduction
- Roles and access
- Set up the integration
- Sync employees
- Employee data
- Position data
- Absence data
- Salary data
- Change integration settings
- Error log
- FAQ
Introduction
The PowerOffice GO integration keeps employee information in Huma and PowerOffice GO in sync. You manage employees and positions in Huma, and Huma sends the changes to PowerOffice GO.
This is what the integration supports, and which way the data goes:
| Data | Huma → PowerOffice GO | PowerOffice GO → Huma | When |
|---|---|---|---|
| Employee data | ✅ Automatic | ✅ Manual only | Huma changes are sent in real time. PowerOffice GO changes are brought in when you click «Sync users». |
| New employees | ✅ Automatic, if enabled | ✅ Manual only | When an employee is added in Huma, or during «Sync users» |
| Positions (employment details) | ✅ Automatic | ❌ | When a position is created, changed or deleted in Huma |
| Absence | ❌ | ❌ | Not supported |
| Salary | ❌ | ❌ | Not supported |
⚠️ Historical data is not transferred. Only positions created or changed after the integration is active are sent to PowerOffice GO.
💡 Need more than one connection, for example one per company? See Multiple connections.
Roles and access
| Access | Role |
|---|---|
| Set up and manage the integration in Huma | System role with full access to Organization |
| Create the client key in PowerOffice GO | Access to create extensions and generate a client key |
💡 Not sure which roles you need in PowerOffice GO? Contact your PowerOffice system administrator or PowerOffice support.
Set up the integration
Before you start
- You have a system role with full access to Organization in Huma.
- You, or a colleague, can log in to PowerOffice GO and create an extension.
- Employees who exist in both systems have the same email address in Huma and PowerOffice GO. Huma matches employees by email only.
- Employee IDs in Huma are numbers. PowerOffice GO only accepts numeric employee numbers.
Step 1: Create a client key in PowerOffice GO
- Log in to PowerOffice GO.
- Open the menu and select «Settings».
- Under «System», open «Extensions».
- Click «Add extension».
- Select «Huma» in the dropdown.
- Copy the «Client Key» and save the extension.
💡 You need access to create extensions in PowerOffice GO. If you don't have it, contact your PowerOffice system administrator. For more about client keys, extensions and the API, see PowerOffice's own help pages.

Step 2: Connect Huma to PowerOffice GO
- In Huma, go to «Integrations» and select «PowerOffice GO».
- Read the «Overview» and «Details» tabs.
- Click «Set up» in the top right corner.
- Give the connection a name.
- Choose who should be part of this connection: everyone, or a specific team, location or company.
- Click «Save».
- Paste the «Client Key» from PowerOffice GO.
- Confirm that you have the legal authority to accept the terms on behalf of your organization.
- Click «Continue».


Step 3: Choose what to sync
PowerOffice GO has one setting. You can change it later. See Change integration settings.
| Setting | When it's on | When it's off |
|---|---|---|
| Users: Create in PowerOffice GO when added in Huma | New employees in Huma are created in PowerOffice GO automatically. This also applies to employees added through other integrations, such as Teamtailor. | New employees are only created in PowerOffice GO when you click «Sync users». |
💡 Employment details are always sent. There is no setting for them.

Step 4: Sync users to activate the integration
After setup, the integration page says «This integration has been set up, but is not active». Nothing is sent until you sync users. See Sync employees.
Sync employees
«Sync users» compares the employees in Huma and PowerOffice GO. You decide what to update and which employees to create. The first sync also activates the integration.
How to sync users
- Go to the PowerOffice GO integration in Huma and click «Sync users».
- Matching users are employees with the same email in both systems.
- Click «View users» to see fields with different or missing values.
- For each case, choose to update Huma with the value from PowerOffice GO, update PowerOffice GO with the value from Huma, or leave it.
- Click «Next».
- Non-matching users are employees that exist in only one system.
- Choose whether to create all of them, only the ones you select, or none.
- Choose the direction: PowerOffice GO → Huma, or Huma → PowerOffice GO.
- Click «Sync users».
The status changes to «Connected and active». You'll get an email with the result.
💡 Before you sync, decide which system has the most up-to-date information. Your choices here overwrite data.
⚠️ Users missing required fields are not synced until the missing values are added.


When to sync users
Changes in Huma are sent to PowerOffice GO automatically. Click «Sync users» when:
- You have just set up the integration and want to activate it.
- You have changed a supported field in PowerOffice GO and want it in Huma.
- You have added employees in PowerOffice GO that should be created in Huma.
- You have added employees in Huma and «Users: Create in PowerOffice GO when added in Huma» is off.
New employees created from Huma
- Employment details: The start date, end date and job title from the employee's positions in Huma are sent when the employee is created.
- Bank account: The account is set as both salary account and expense account.
- Already exists in PowerOffice GO: If an employee with the same email already exists, Huma doesn't create a new one when the employee is added in Huma.
When an employee leaves
Deactivated in Huma:
- The employee is not deactivated in PowerOffice GO.
- The employee is locked for updates from the integration.
Deleted in Huma:
- The employee is not deleted in PowerOffice GO.
- The next «Sync users» suggests creating them in Huma again.
- The employee can't be synced if they were changed in PowerOffice GO after they were deleted in Huma.
💡 To register the end of employment in PowerOffice GO, set the contract end date on the employee's last position in Huma. See Position data.
Employee data
Changes in Huma are sent automatically. Changes in PowerOffice GO are brought in with «Sync users».
| Huma field | Field in PowerOffice GO | Required | Notes |
|---|---|---|---|
| Email address | ✅ | Used to match employees. Must be unique in Huma. When you change the email in Huma, the new address is sent to PowerOffice GO. API name: emailAddress |
|
| First name | First name | API name: firstName |
|
| Last name | Last name | API name: lastName |
|
| Phone number | Phone | Must be unique in Huma. API name: phoneNumber |
|
| Date of birth | Date of birth | API name: dateOfBirth |
|
| Employee ID | Employee number | Must be unique in Huma, and must be a number. All employees in PowerOffice GO have an employee number. If the employee ID is different in the two systems, it shows as a difference when you sync users. API name: code |
|
| Bank account | Salary account (Lønnskonto) | Norwegian accounts and international accounts (IBAN + BIC) are supported. See How bank accounts are handled. Make sure the salary account in PowerOffice GO is correct, as this is the field brought into Huma. API name: payrollBankAccountCode |
|
| Gender | Gender | Only male and female are supported. If the gender is unspecified in PowerOffice GO, it stays unchanged in Huma. A custom gender in Huma is unspecified in PowerOffice GO. API name: gender |
|
| Address | Mail address | API name: mailAddress |
|
| Identifications | National identity number | Only Norwegian national identity numbers. API name: socialSecurityNumber |

How bank accounts are handled
- New employee: The account is set as both salary account and expense account.
- Changed account: The new account is added to the employee's list of bank accounts in PowerOffice GO and set as the salary account. The old salary account is kept in the list, but set to inactive.
- Expense account: If the salary account and expense account were the same (or both empty), both are changed to the new account. If they were different, only the salary account is changed.
- Deleted account: If you delete the bank account in Huma, the salary account is cleared in PowerOffice GO.
Position data
Positions go one way: from Huma to PowerOffice GO. PowerOffice GO doesn't store positions like Huma does. Instead, Huma sends three employment details, based on all the employee's positions in Huma.
| Huma field | Field in PowerOffice GO | Required | Notes |
|---|---|---|---|
| Contract start date | Start date | Uses the contract start date of the employee's first position in Huma. API name: startDate |
|
| Contract end date | End date | Uses the contract end date of the employee's last position in Huma. API name: endDate |
|
| Job title | Job title | Uses the job title of the employee's current primary position. API name: jobTitle |
When employment details are updated
Every time a position is created, changed or deleted in Huma, Huma works out the start date, end date and job title again and sends any changes. There is no setting for this. Other position fields, such as percentage and contract type, are not sent.
⚠️ Before Huma updates the employment details, it checks that the email address in PowerOffice GO still matches the employee in Huma. If it doesn't, nothing is sent and the error is logged.
Absence data
Absence is not supported in the PowerOffice GO integration. Register absence in PowerOffice GO.
Salary data
Salary is not supported in the PowerOffice GO integration. Register salary in PowerOffice GO.
Change integration settings
- Go to the PowerOffice GO integration in Huma.
- Click ··· in the top right corner.
- Select an option:
- «Edit connection settings» to change the setting or paste a new client key.
- «Edit connection details» to change the name or who is part of the connection.
The setting is explained in Step 3: Choose what to sync.
Disconnect or remove
- Disconnect: Stops syncing but keeps your configuration.
- Remove: Stops syncing and deletes all stored configuration.
Error log
Where to find the error log
- Go to the PowerOffice GO integration in Huma.
- Open the «Error log» tab.
Errors are grouped by day. Each entry shows a message, the time, the employee it applies to and a level:
| Level | Meaning |
|---|---|
| 🔴 Error | Something was not sent to PowerOffice GO. You need to act. |
| 🟡 Warning | Something needs your attention. |
| 🔵 Info | For your information. No action needed. |
Integration status
| Status on the integration page | What to do |
|---|---|
| This integration has been set up, but is not active | Click «Sync users» to activate it. |
| Connected and active | Everything is running. |
Common errors
| Problem | What it means | How to fix |
|---|---|---|
| Employee ID is not accepted | PowerOffice GO only accepts numeric employee numbers. | Change the employee ID in Huma to a number, then sync again. |
| Email mismatch when trying to update | The email address in PowerOffice GO no longer matches the employee in Huma. | Make the email address the same in both systems, then click «Sync users». |
| The connection to PowerOffice GO stops working | The client key no longer works, for example because the extension was removed in PowerOffice GO. | Create a new client key in PowerOffice GO and paste it in «Edit connection settings». |
| Wrong bank account in Huma | Huma reads the salary account in PowerOffice GO. | Correct the salary account in PowerOffice GO, then click «Sync users». |
FAQ
Why are changes I make in PowerOffice GO not showing in Huma?
Changes only go automatically from Huma to PowerOffice GO. To bring changes from PowerOffice GO into Huma, click «Sync users».
Can I sync absence or salary with PowerOffice GO?
No. The PowerOffice GO integration supports employee data and employment details only. Register absence and salary in PowerOffice GO.
What happens to the old bank account when I change it in Huma?
Huma adds the new account in PowerOffice GO and sets it as the salary account. The old account is kept, but set to inactive. The expense account is only changed if it was the same as the salary account.
Why is the gender not updated?
PowerOffice GO only supports male and female. A custom gender in Huma is sent as unspecified, and an unspecified gender in PowerOffice GO doesn't change Huma.
Can historical positions be transferred?
No. Only positions created or changed after the integration is active are sent.
Why wasn't an employee created in PowerOffice GO?
The most common reasons are that «Users: Create in PowerOffice GO when added in Huma» is off, that an employee with the same email already exists in PowerOffice GO, or that the employee ID in Huma isn't a number. Check the error log, then click «Sync users».
Can I have more than one PowerOffice GO connection?
Yes. You can, for example, set up one connection per company. See Multiple connections.