Custom Pivoton Kentro integration development
Kentro is Pivoton's back-office software for the staffing industry, with contract management, payroll, invoicing, time registration and the Kentro Konnekt portal for flexible workers and clients. Pivoton is part of zvoove and connects Kentro to RecruitNow's ATS Cockpit and to tools such as Planbition and ID-check. If you work with a different ATS, your clients record hours in their own system, or you want your figures in an overview of your own, the standard integrations fall short. Appfront builds the integration between Kentro and those systems.
What is a Pivoton Kentro integration?
A Pivoton Kentro integration lets your back office exchange data with the systems around it. In Kentro you record contracts, run payroll under the correct collective labour agreement (cao) using Kentro's payroll engine, invoice clients and process hours, with Kentro Analytics for insight into margins and performance. In Kentro Konnekt, flexible workers record hours and retrieve their payslips, and clients approve hours. The integration ensures that data coming from outside, such as a placement from the ATS or hours from the client's system, arrives in Kentro automatically, and that what Kentro produces ends up in the right systems.
According to its own website, Pivoton connects Kentro to RecruitNow's ATS Cockpit, with Kentro taking over from the candidate's placement, and to tools such as Planbition, ID-check and StiPP. Pivoton mentions APIs for external tools and, in the Enterprise bundle, full integration options. A custom integration covers what is not on that list: a different ATS, a client who records hours in their own time registration or supplier portal, an accounting package for the journal entries, or an overview that puts back-office figures alongside recruitment figures.
We build custom because every staffing organisation works differently. Whether you provide temp staffing, secondments or freelancer placements, which systems you and your clients use, how often you run payroll and which side is the source for which data all determine how the integration works. We have not found public API documentation for Kentro. Which integration options exist for your environment and bundle is something we look at in the first step, together with you and Pivoton.
Placement passed on
From your ATS into Kentro.
Hours in
From the client, without retyping.
Overview
Your figures in one place.
How we build your Pivoton Kentro integration
We start with your organisation: which Kentro bundle you use, which ATS and other systems run alongside it, how hours and placements currently come in and what is still done by hand. Then we build the first integration, usually the flow that costs the most manual work, such as placements from the ATS or hours from a large client. You run a few payrolls with it. Other flows and reporting follow once that works well. After that, we maintain the integration when Kentro, the cao or your other systems change.
Bundle, systems, manual work.
The biggest time saving first.
More flows and reporting.
Go-live, monitoring, and maintenance when things change.
What a Pivoton Kentro integration actually does
The components below come up in almost every integration with Kentro. Which ones you need depends on your market and on the systems you and your clients use.
Placements
From your ATS into Kentro.
Hours
Straight in from the client.
Contracts
Data kept in sync.
Invoices
To the accounting system.
Double entry
Detected and blocked.
Reporting
Back office alongside recruitment.
Who we build a Pivoton Kentro integration for
The integration is aimed at flex organisations that work with Kentro and also have systems that don't talk to it out of the box. The more flex workers and clients you have, the more it pays off.
Temporary staffing agencies
From placement to payroll.
Secondment agencies
Contracts and hours.
Payroll organisations
Many clients, many hours.
Freelancer intermediaries
Hours and invoices.
Technology and integrations
This page is about integrations with Pivoton's Kentro. If you work with a different back office, see our page on the Easyflex integration; for the Cockpit ATS and the front office, see our page on the RecruitNow integration; for a different ATS, our page on the Carerix integration; and if you want custom software for your agency, our page on custom staffing agency software. You can read about our approach on building software.
Why Appfront for your Pivoton Kentro integration?
A placement that has to be retyped in the back office, hours copied over from a client portal, or a payslip that is wrong because a contract differs between two systems: all of this costs a staffing organisation time and the trust of its flex workers. That is what we build around: data that flows through automatically, a clear source for every data item, and an integration that shows you when something went wrong.
Less retyping
Data passes through automatically.
Reliable
One source per data item.
Visible
Errors in the log.
Security and privacy in a Pivoton Kentro integration
The integration processes flex workers' personal data, such as contracts, hours and pay information, and therefore falls under the GDPR. It sends only the fields the other system needs, works with dedicated accounts that have exactly the permissions required, and records every exchange with a timestamp and its content.
The integration runs in a European data centre, using encrypted connections. Keys and passwords are stored securely and are not visible to staff. We agree with you in advance who in your organisation may see which data from the integration.
Frequently asked questions about a Pivoton Kentro integration
Questions asked by owners, back office staff and application managers at staffing organisations before they get started.
A connection between Pivoton's Kentro and another system you use, such as your ATS, a client's timesheet system, your accounting software or a custom report. Placements, hours and invoices then flow back and forth automatically, without retyping.
Back office software from Pivoton for the staffing industry, with contract management, payroll in line with collective labour agreements, invoicing, timesheets, Kentro Analytics and the Kentro Konnekt portal. Kentro comes in the Essential, Elevate and Enterprise bundles. Pivoton is part of zvoove.
Yes. According to Pivoton, there is an integration with RecruitNow's Cockpit ATS, as well as integrations with Planbition, ID-check and StiPP, among others. A custom integration is for a different ATS, or for systems and flows not covered by those.
Pivoton mentions APIs for external tools and full integration options in the Enterprise bundle. We have not found any public API documentation. We will work out which integration options are available for your environment in the first step, together with you and Pivoton.
This is one of the most requested flows. If the client approves hours in Kentro Konnekt, they are already in Kentro. If a client tracks hours in its own system or portal, we build the integration that retrieves them, checks them and enters them in Kentro.
The integration retries, and puts an exchange that keeps failing into an error list with the reason. You can see which placement, flex worker or client is affected and, after correcting it, send it again before payroll starts.
For staffing organisations with many flex workers and clients, an ATS other than Cockpit, clients with their own timesheet system, or a custom overview of recruitment and back office. If you only use Pivoton's standard integrations, configuration is often enough.
Want Kentro to work with your other systems?
Tell us how you use Kentro and which systems you and your clients use alongside it. We will show you how an integration can take over the manual work.