> For the complete documentation index, see [llms.txt](https://developer.usemultiplier.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.usemultiplier.com/integrations/hibob-payroll-hub.md). # Hibob Payroll Hub HiBob Payroll Hub is a standardized way for HR data in HiBob to flow directly into payroll providers, rather than manually exporting and re-entering employee information. {% embed url="" %} ### **How it works** Once the integration is set up, employee data entered and maintained in HiBob flows automatically into Multiplier.\ \ **This includes:**
* Personal and contact details * Compensation information * Start dates and employment details * Organisational structure (department, manager) \ Multiplier uses this data to onboard employees and process payroll. ### Connect Hibob Payroll Hub with Multiplier 1. Click on the install icon on Hibob 2. When authorize window appear click on "Authorize" button

3. After successful authorization, you should be able to see the "Installation Request Received" page with an activation code, which will be used on the Multiplier side to complete the integration setup.

4. Copy the activation code from the previous screen. Log in to Multiplier, choose the HiBob Payroll Hub option when HiBob platform is selected, click Connect, and use the same activation code to establish the connection.

### Mapping field requirements 1. Go back to Multiplier integrations. 2. Click on review button inside Direct Employees card.

3. Map at least one entity in order to enable data sync.

4. When entity is fully mapped you be able to enable data sync and integration is completely configured and ready to receive real time events from Hibob Payroll Hub.

### Defining Payroll Cycles in Hibob Payroll Hub 1. Once everything properly configured. 2. Go in to Hibob and navigate to Payroll Cycles where you will define employees, pay frequency and payout days. 3. Click on the button "Add pay cycle".

4. Define name for payroll cycle.

5. Select employees you want to have in the cycle based on worksite (country of work).

6. Add payroll configuration, this needs to be aligned with Multiplier payroll configuration in order to run payroll successfully.

7. Select report fields by default they all should be marked since they are defined by GP requirements.

8. Activate configuration so its ready for vendor.

### Exporting data to Multiplier 1. After the configuration is activated you should be able to see under Payroll Cycles all configured cycles such as Monthly, Bi-Weekly etc. Depending on what company has configured in Multiplier platform.

2. As part of configured cycle you will have 3 options: 1. New Hires 2. Changes 3. Leavers 3. All three should be exported by selecting records available in the report in order to send all data to Multiplier.

4. After the export is done you should be able to see "Report successfully exported" together with "Synced" status on employee level.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.usemultiplier.com/integrations/hibob-payroll-hub.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.