---
title: "HiBob integration: Pensions"
slug: "hibob-integration-pensions"
updated: 2026-10-22T15:30:03Z
published: 2026-10-22T15:30:03Z
canonical: "help.cintra.co.uk/hibob-integration-pensions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.cintra.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# HiBob integration: Pensions

Pension contributions come from the custom **Pension** section in HiBob through the main sync. Each pension record in HiBob becomes a pension contribution in payroll. For the fields in the Pension section, see [HiBob integration: Required fields in HiBob](/payroll/docs/hibob-integration-required-fields-in-hibob).

The **Scheme Contribution Name** in HiBob must match a pension scheme part name in payroll exactly.

## Default contributions

| If | Then |
| --- | --- |
| **Use Default Employee Contribution** or **Use Default Employer Contribution** is set to **Yes** | The default contribution set up in payroll is used, even if a different value is entered in HiBob. |
| A default field is set to **Yes**, but payroll has no default contribution | An error appears in the CintraHR log. Set up the default contribution in payroll, or enter the actual contribution in HiBob. See [Setting up pension scheme contributions](/iq/docs/how-do-i-set-up-pension-scheme-contributions). |
| You don't use the default fields in HiBob | The values in **Employee Contribution** and **Employer Contribution** are always used. We recommend making both fields mandatory in HiBob. |

## Changing a pension contribution

To change an employee's contribution, end-date their current pension record in HiBob, then add a new record that starts after it.

HiBob lets you have more than one pension record with overlapping dates, but payroll can't. If two records for the same scheme contribution overlap, both are rejected and nothing is added to payroll. Make sure only one record is active for each scheme contribution at a time.

The end date on a HiBob pension record ends that contribution in payroll. It doesn't end the employee's membership of the pension scheme.

## Correcting the scheme contribution name

If you chose the wrong **Scheme Contribution Name** for an employee, delete the pension record in HiBob and add a new one. If you edit the name on the existing record, an error appears in the CintraHR log.

## Deleting a pension record

Deleting a pension record in HiBob deletes the matching pension contribution in payroll, including any contribution set up when your payroll was onboarded. The employee's pension membership isn't deleted.

## Leavers and opt-outs

The integration doesn't record when an employee leaves the pension scheme or opts out. Your payroll user needs to enter the membership end date in payroll and check whether the employee is due a refund. See [Pension membership](/payroll/docs/pension-membership).

## Auto-enrolment and re-enrolment

Data only flows from HiBob to payroll. If payroll enrols an employee through its auto-enrolment assessment, HiBob isn't updated.

1. Run the auto-enrolment assessment in payroll to check whether anyone is due to be enrolled. See [Running auto enrolment assessments](/iq/docs/how-do-i-run-auto-enrolment-assessments).
2. For each employee who's due, add a pension record in HiBob.
3. Run the sync again.

Do the same when re-enrolment is due. Anyone payroll flags for re-enrolment needs to be put back into the pension scheme in HiBob.

## Existing pensions at go-live

Pension contributions set up in payroll when your payroll was onboarded are matched with HiBob automatically, even though the effective dates are different. Pension membership start and end dates in payroll aren't changed. See [HiBob integration: Matching existing records at go-live](/payroll/docs/hibob-integration-matching-existing-records-at-go-live).