enova365 integration with PeopleForce: HR and payroll

Capabilities

What changes in day-to-day work

Data originates where the process is happening anyway (in the preboarding form, in a request, at a salary change) and reaches the HR and payroll system without retyping.

Hiring without an intermediate spreadsheet

A new hire's details are collected by the preboarding form, not by a file that someone later enters into enova365 by hand. In the employee profile, we add fields that mirror the employee record required for hiring, along with dictionaries of NFZ branches, ZUS branches, tax offices and occupation codes.

Leave and remote work requests

Only approved requests reach enova365; rejected ones never leave PeopleForce. The remaining allowance is confirmed by enova365, so corrections your HR team makes there show up in PeopleForce too.

Payslips and PIT-11 forms in the employee's folder

Payslips and PIT-11 forms from enova365 land in a designated folder in the employee profile; employees see it once an administrator shares the folder with them. The files can be password-protected. Instead of emails, employees get one place with all the payslips and PIT forms sent to them.

Offboarding run from one place

The termination is recorded in PeopleForce, and data on the ended contract reaches enova365 along with the rest of the employee record. HR formalities (deregistration from ZUS and the employment certificate) stay with enova365 and the payroll team. In PeopleForce, the process kicks off: equipment return, exit survey and exit interview.

How it works

What syncs, and in which direction

Each type of data has one home system: employee data is changed in PeopleForce, while entitlements, payroll and payroll documents are kept by enova365. Changes are made in one place, and the other system stays in step. The exchange runs regularly; we agree the schedule and how much history to bring over during implementation.

What moves	Direction	When	Data
Employee record Basic, address, insurance and tax details	PeopleForce enova365	recurring	PESEL, addresses, NFZ and ZUS branch, tax office, NIP
Contracts Employment, mandate (umowa zlecenie), specific-task (umowa o dzieło) and B2B	PeopleForce enova365	recurring	contract type, period, salary, working time (FTE), position, department
Pay supplements Bonuses, commissions, other components	PeopleForce enova365	recurring	component name, amount, validity period
Leave and remote work requests Once approved	PeopleForce enova365	recurring	request type, dates, employee
Bank account numbers	PeopleForce enova365	recurring	account number, bank, currency
Documents Electronically signed contracts and addenda	PeopleForce enova365	recurring	document file linked to the employee
Leave entitlements The employee's current balance	enova365 PeopleForce	recurring	current-year entitlement plus carry-over from last year
Pay supplements and deductions Currently assigned components	enova365 PeopleForce	on demand	the employee's supplements and deductions
Contract history Brought over at the start	enova365 PeopleForce	one-off	contract history in the employee profile
Absences from enova365 Including sick leave	enova365 PeopleForce	on demand	dates and number of days used
Payslips and PIT-11 forms Ready-to-use documents, optionally password-protected	enova365 PeopleForce	on demand	PDF files in the employee's folder

On the first run, the integration links each employee in PeopleForce to their record in enova365, so nobody is duplicated. Any record it can't link is flagged for your team to confirm.

All PeopleForce integrations

A catalogue of ready-made connections, plus an API for building your own integrations

See integrations

Setup

Two stages to launch

First a one-off import, then regular exchange. A dedicated Customer Success Manager guides you through both.

Stage 1

Initial import

We connect enova365 to your PeopleForce account and bring over your employee data. During setup we match your leave types, contract types, pay components and departments with their counterparts in enova365 — once, with your team.

Stage 2

Regular exchange

From then on, data flows in the directions shown above, on the schedule agreed at setup. Day-to-day work stays in PeopleForce and the familiar enova365 interface.

Conditions for running the integration

What you need, who sets it up, and how the launch works.

The integration runs through an add-on on the enova365 side

The connection runs through a certified add-on on the enova365 side, built and maintained by our authorised partner and kept up to date with new enova365 versions. The enova365 Gold or Platinum package is required. Technical requirements are shared during onboarding.

The PeopleForce team enables the integration

Requires the ERP Connector add-on. Our team and the partner set it up with you, and your account manager is your single point of contact, from launch to updates.

Start on a test database, then production

The standard is to launch the integration on a copy of the production database: there we check that the data and entitlements match, and only then do we switch the exchange to the production environment. Before launch, we also write down the exchange scope for your company.