Moving your payroll
Change payroll provider without betting a month on it.
We run alongside your current provider for two months. You compare every line before anything depends on us.
Why a payroll move keeps being put off.
- A wrong first payroll lands on every employee in the same week.
- Nobody wants to own the month it goes wrong.
- The data sits across HR, finance and the current provider.
- Every year, the move is pushed to the next one.
- Testing a new provider sounds like running payroll twice.
We run ours alongside, and you compare.
Nothing depends on us until the numbers match.
You compare both payrolls line by line, twice, before we go live.
- Your current provider
- Global Kinect
Start
Data captured
Your payroll data is captured by CSV.
Month one
Side by side
Matched
We run alongside your current provider. You compare line by line.
Month two
Side by side, again
Matched
You compare both outputs a second time.
Month three
Live
We go live on payroll.
You do not have to trust our calculation. You check it against the one you already trust.
Who does what
You
From you
- One named contact who can confirm decisions.
- Input data by the agreed cut-off.
- Sign-off on each parallel run.
Global Kinect
From us
- Mapping the data.
- Running both parallel months.
- Explaining every difference.
One sample file is enough to scope the move.
Send us a sample output file from your current provider, and we scope the move from it.
Questions about the move
How long does it take to move payroll to a new provider?
With Global Kinect, payroll goes live in month three. Your initial payroll data is captured by CSV. For two months we run your payroll alongside your current provider, and you compare both outputs line by line. Nothing depends on us until the numbers match. This timeline covers payroll only. The rest of the platform does not go live with it.