This article provides an overview of how to prepare your Personio account for a3innuva Nómina, and how to set up the a3Innuva Nómina integration.
Note
To use the a3innuva Nómina integration, a legal entity must exist in Spain. To find out more about legal entities, refer to our Help center article on creating legal entities.
To learn how to use the integration to sync your Personio data with a3innuva Nómina, visit our article on using the a3innuva-Nómina integration.
Overview
What is a3Innuva Nómina?
A3innuva Nómina is an HRM solution provided by Wolters & Kluwer. Nómina is their dedicated payroll functionality. The a3innuva Nómina integration allows you to sync the following data from Personio:
- Employee data (personal data, employment data, national insurance data)
- Contract, contribution, and tariff data
- Company agreements
- Compensations
- Absences
Once you order the integration for free of charge through the Personio Marketplace, our Customer Operations team will set up the account for you. This includes making sure that the attributes supported by the integration are correctly set up in your Personio Account.
Step 1: Set up the a3innuva integration
Request the a3innuva Nómina integration and fill in values for the new integration
Request the a3innuva Nómina integration and have your account set up
Before transferring data between Personio and a3innuva Nómina, your account requires compatible attributes to successfully transfer data between Personio and a3Innuva Nómina. To book the a3innuva Nómina integration directily in Personio via the Marketplace, follow these steps:
- Go to the Marketplace in the navigation bar.
- Search for a3innuva Nómina.
- Click Book integration.
Once you request the integration via our Marketplace, our Customer Operations Team will perform an attribute mapping session to link existing attributes or create new attributes to be transferred to a3innuva Nómina. The missing attributes will be created in the new section of all employee profiles: Payroll-Spain-A3.
After completing the attribute setup, the Customer Operations Team will enable the integration for your account. However, you still need to complete the next steps to be able to use the integration.
Select a value for each attributes
Select attribute values for all relevant employees in the Payroll-Spain-A3 section. You can also select an attribute value for several employees at once via the employee list and also via
When applicable, validation rules for selected attributes apply to ensure the data is transferred successfully from Personio to the a3innuva Nómina integration. The validations and the error messages allow you to identify incorrectly formatted attribute values in the employee profile or in Payroll > a3innuva Nómina. You can then correct them, before you transfer this information to a3innuva Nómina.
Note
If you are rehiring former employees, you can use the rehire feature, transferring all employee data from the inactive employee profile to the new one. For detailed guidance, refer to our Helpcenter article on rehiring former employees. Once you select the option Copy all other attributes from the previous profile, Personio automatically copies the custom attribute values and sets the attribute Consider in Spanish Payroll in the old profile to No. This adjustment allows you to reuse the same Employee code (a3innuva Nómina) without duplication errors. We recommend your payroll or a3 admin reviews the new profile to confirm whether the previous employee code should be reused.
Defined attributes
Here is the full list of all the relevant attributes:
Name (Personio) | Name (a3innuva Nómina) | Additional Context |
Include in Spanish payroll | This attribute defines if an employee should be included in the sync with a3innuva-Nómina. | |
Employee code (a3innuva Nómina) | Identificación > Código | This is a unique six-digit employee identifier in a3innuva Nómina. This value links an employee in Personio to an employee profile in a3innuva Nómina. |
Legal entity | Identificación > Empresa | - |
Office | Identificación > Centro de Trabajo | |
Type of document | Identificación | |
Document number | Identificación | |
First name | Identificación > Nombre | |
Last name |
Identificación > Primer apellido & Segundo apellido |
The Personio last name is split according to Spanish standards to be transferred to Primer apellido and Segundo apellido. |
Gender | Identificación > Sexo | - |
Social security number (NAF) | Identificación > NASS (or NAF) | |
Type of person | Identificación > Tipo de persona | Personio will send Trabajador for all employees. Refer to the Special cases section for more information. |
Nationality | Identificación > Nacionalidad | - |
Birthplace | Identificación > Lugar de nacimiento | |
Hire date | Contractuales > Fecha Alta | |
Name of the collective agreement | Convenio > Código convenio/pacto | This open text field must match what is in a3innuva Nómina. Refer to the Special cases section for more information. |
Category name of the collective agreement |
Convenio > Categoría OR Convenio > Grupos/Niveles |
This open text field must match the description of the Categoría or Grupos/Niveles in a3innuva Nómina. Refer to the Special cases section for more information. |
Job position collective agreement |
Convenio > Puesto de trabajo |
This open text field must match the name of the Puesto de trabajo in a3innuva Nómina. |
Contribution group |
Convenio > Grupo de Tarifa |
Only contribution groups from the Tipo de Régimen: Régimen General are supported. |
Type of payment |
Convenio > Tipo de Cobro |
- |
Tipo de Régimen |
Convenio > Tipo de Régimen |
Personio will send Régimen General for all employees. Refer to the Special cases section for more information. |
Type of contribution |
Contratación > Cotización > Tipo |
- |
Termination date Note |
|
This attribute is filled in during the usual termination flow in Personio. |
Termination reason Note |
Contractuales > Fechas > Motivo baja |
This attribute maps the list of termination reasons in a3innuva Nómina and is mandatory in case of termination. Refer to the Special cases section for more information. |
Birthday |
Identificación > Fecha nacimiento |
- |
Contract Type |
Contratación |
|
CNO Occupation Code |
Contratación > Listado contrato |
Personio is considered the source of truth for this attribute - if there is no value for an employee, the value in a3innuva Nómina is overridden. |
Personal phone |
Identificación > Telefono |
-
|
Personal email |
Identificación > Email personal |
|
Corporate phone |
Localización > Móvil de empresa |
|
|
Localización > Email profesional |
|
Employee IBAN |
Formas de Cobro |
Through the sync all necessary bank data is automatically filled in (account number, check digits, bank entity, etc) |
Employee BIC |
Formas de Cobro |
- |
Probation period |
Contratación > Contractuales > Período de prueba |
We currently only support months as probation period. Custom probation periods in Personio are not supported and are not transferred if set. |
Address (country) |
Identificación > Domicilio |
The “Localidad” field is inferred from the Municipality + postal code. |
Address (street) |
Identificación > Domicilio |
|
Address (house number) |
Identificación > Domicilio |
|
Address (type) |
Identificación > Domicilio |
|
Address (stair) |
Identificación > Domicilio |
|
Address (floor) |
Identificación > Domicilio |
|
Address (gate) |
Identificación > Domicilio |
|
Address (postal code) |
Identificación > Domicilio |
|
Address (municipality) |
Identificación > Domicilio |
Accepts both, the municipality name and municipality code. A list of all codes and names is linked to the product andalso available as an attachment in this article. |
Company bank account type |
Formas de Cobro > Banko de Pago |
This information is retrieved from the Legal Entity the employee is assigned. If the Legal Entity has a an IBAN value, it will be transferred via the sync. |
Special cases
- Consider in Spanish Payroll and Employee Code (a3innuva Nómina)
These two attributes determine if an employee is included in the sync.
▶ Consider in Spanish Payroll: You need to select the value Yes for all employees whose data should be transferred with the integration, and the value No for those whose data should not.
▶ Employee Code (a3innuva Nómina): You need to input the code that you will find in a3innuva Nómina.
- Termination reason
In addition to the usual termination flow, terminating an employee using the a3innuva Nómina integration requires filling in the Termination reason attribute located in Employee profile > Personal Info tab > Payroll-Spain-A3.
- Name of collective agreement
What is input in Personio has to match exactly what is in a3innuva Nómina. Refer to the screenshot for guidance.
- Category name of the collective agreement
In a3innuva Nómina you can find different categories and groups or levels determined by the collective agreement. Personio can identify these different categories, but requires a description of what is in a3innuva Nómina. In the case of Grupos/Niveles, you need to use the description without the hierarchy numbers to label the different groups.
Note
Ensure that the value in Personio matches the category collective agreement descriptions in a3innuva Nómina.
- Tipo de Régimen
Tipo Régimen is a field we always send as Régimen General from Personio. This value is overridden for all employees included in the transfer. The Régimen General needs to be selected for the a3innuva Nómina company.
- Employee code (a3innuva Nómina) and legal entity
Changing these attributes after the creation of an employee in a3innuva Nómina will lead to the creation of a new employee.
- Type of person
Personio will send Trabajador for all employees. Since this attribute is not editable, it is not shown in the Personio file.
Step 2: Authorize & configure the integration
Authorize the integration
You need to authorize the integration to make sure that your Personio account is linked to the correct a3innuva Nómina account. To authorize the integration, follow these steps:
- Ensure that you have the necessary access rights both in Personio (edit rights to both the Payroll area and Payroll Configurations) and in Wolters & Kluwer (Admin rights to your a3innuva Nómina account).
- In your Personio account, go to Payroll > a3innuva.
- Open the Manage tab.
- In the general settings, select the legal entity you want to complete the authorization for. Each legal entity can be authorized to one a3innuva-Nómina organization.
- Click Connect a3innuva Nómina to be redirected to Wolter & Kluwers.
- Grant permissions for the authorization to take place. If you are not logged in, you will need to log in and select the correct organization to connect.
- You will be redirected back to Personio. The Personio a3innuva Nómina authorization page now shows all the details regarding the completed authorization.
Map legal entities and offices to companies and workplaces
Finally, you need to map legal entities and offices in Personio to companies and workplaces in a3innuva Nómina to make sure that data is transferred correctly. To do so, follow these steps:
- In your Personio account, go to Payroll > a3innuva.
- Open the Manage tab.
- Select a legal entity in the dropdown and assign it to a corresponding company in a3innuva Nómina ("empresa").
- Select an existing office in Personio and assign it a corresponding workplace in a3innuva Nómina ("centros de trabajo").
- Click Save to complete the configuration. You can only save the page after you have mapped at least one company and one workplace.
Configure compensations
The Personio-a3innuva Nómina integration supports the transfer of compensation data for the following types:
- transfer of recurring compensations for the current month
- transfer of one time compensations for the current month
- Transfer of theoretical annual gross salary (base salary)
Note
The theoretical annual gross salary is an informative concept within a3Innuva. To ensure accurate payroll calculations, manually transfer this data to the Salary Concepts tab for each employee. This step is crucial for maintaining correct payroll processing
The transfer of the following compensation types are not supported:
- hourly wages
- recurring compensations with non-monthly frequency
- bonuses
- historical recurring compensations
- historical one time compensations
- future (not current month) recurring compensations
- future (not current month) one time compensations
You can find more information on what compensation data can be maintained in Personio in our Help Center article Salary Components in Personio.
To map the compensation types you wish to transfer from Personio to a3innuva Nómina, follow the next steps:
- Go to the Payroll section in the navigation bar and select a3innuva.
- Click Manage and go to the Compensation mapping tab.
- Select which compensations you want to transfer to a3innuva Nómina.
- Click Save.
Important to note
- Changes made directly in a3innuva Nómina won’t be reflected in Personio. We recommend entering information in Personio and using the sync feature to a3innuva Nómina to ensure both systems remain accurate.
- The base salary is always transferred and does not need to be mapped in the manage tab.
- Only compensations that are mapped in Personio, will be transferred to a3innuva Nómina.
- Recurring compensations that do not follow a monthly interval are not transferred. If you wish to transfer those, we recommend adding the compensation as a one time compensation.
Configure absences
The Personio-a3innuva Nómina integration supports the transfer of absences. All absence types that are stored in the Personio Settings > Absences can be transferred to a3innuva Nómina and have to be mapped to one of the Personio categories. Refer to our article on syncing absences to a3innuva Nómina to learn how to setup and use this feature.
Step 3: Complete the setup and start your transfer
Complete setup and payroll data transfer
You have now successfully set up the a3innuva Nómina integration. To learn how to use the integration to sync your Personio data with a3innuva Nómina, visit our article on using the a3innuva Nómina integration and synching Personio absences to a3innuva Nómina.