Outsourcing payroll: process, switch and data migration

Quick answer. Outsourcing payroll means entrusting payslip production and the DSN filing to a firm or a software. The switch succeeds if you pick a good moment (start of year or quarter), if the data migration is accurate and if the scope is clear. The employer remains liable for its obligations.

You still run payroll in-house and every month-end is turning into a risk zone: a wrongly entered rate, a late DSN, a faulty cumulative figure. Outsourcing payroll can relieve your HR or accounting team, but a poorly prepared switch moves the problem rather than solving it. This article sets out the concrete process to hand payroll over cleanly, succeed at the data migration and choose between a firm and a software, without losing control of your data or your compliance.

Outsourcing payroll means entrusting a provider, an accounting firm or a SaaS software vendor, with producing payslips, filing social declarations and, sometimes, part of the administrative management of staff. The pivot of the whole system is the DSN (declaration sociale nominative, the mandatory monthly social declaration): it transmits payroll data to social bodies. Accurate payroll produces an accurate DSN; faulty payroll spreads the error.

Scope varies from one provider to another. Some only produce the payslip from the variable items you enter. Others handle the declaration, leave tracking, final settlements, even leave management. Before any choice, set in writing who does what: who collects the variable items, who enters them, who validates before filing. This split of roles avoids blind spots where no one feels responsible.

The legal point that changes everything#

Outsourcing delegates execution, not liability. The employer remains legally liable for its social and reporting obligations, even when a third party produces the payslips and files the DSN. Liability does not transfer to the provider. In practice, if a contribution is wrong or a declaration is late, it is the company that social bodies question. This reality justifies a demanding choice of provider and a maintained internal control, rather than blind delegation.

Our payroll and HR service is built around this very principle: the firm executes and controls, but the employer keeps visibility over what is declared in its name.

There is no single answer. A firm brings advice and carries part of the control: it interprets the collective agreement, secures the calculations and alerts you. A SaaS software, such as Silae or PayFit, industrialises production and gives autonomy, but leaves more data entry and decisions on your side. The trade-off depends on your size, the complexity of your situation (agreements, variable items, multiple populations) and your need for support.

In practice, many SMEs combine the two: the software produces, the firm supervises and advises. To compare market tools, our analysis of Lucca, PayFit and Silae for SME payroll details the positioning differences. And if payroll fits into a broader steering need, an outsourced CFO can connect payroll, cash flow and reporting.

A payroll switch is not a simple file transfer. It is prepared like a mini-project, with a schedule and controls. Here is the procedure we recommend.

1. Define the scope and the need. List what you delegate (payslips, DSN, leave, final settlements) and set in writing who enters variable items and who validates each month.
2. Choose a firm or a software. Decide based on your size, the complexity of your agreement and your need for advice.
3. Choose the right moment. Aim for the start of a calendar year or quarter, after a clean payroll close, to limit the cumulatives to migrate.
4. Gather data and history. Collect contracts, the applicable collective agreement, contribution rates, variable items, payroll cumulatives, leave accrued and taken, balances and prior DSN filings.
5. Configure then check the migration. Have the agreement, rates and cumulatives configured, then check payslip by payslip the accuracy of the migrated cumulatives.
6. Run a parallel payroll if possible. Compare the first month produced by the new tool with your previous reference and fix any gap before the DSN.
7. Secure reversibility and compliance. Verify retrieval of your data and configuration, and the GDPR framing of payroll data.

The right moment to switch#

The best moment to switch is the start of a calendar year or, failing that, the start of a quarter, just after a clean payroll close. The reason is mechanical: at the start of the year, annual cumulatives restart from zero or are the simplest to reconstruct. A mid-period switch forces you to migrate partial cumulatives accurate to the euro, which multiplies the sources of error.

Data migration is where outsourcing succeeds or fails. It means transferring into the new tool or to the new provider all the past data that conditions an accurate payslip. Annual cumulatives must be migrated exactly, otherwise payslips and the DSN will be wrong from the very first month.

The critical data to migrate include, in particular, the cumulative social security ceiling, the basis of the general contribution reduction, the cumulative taxable net and the withholding tax. To this are added leave accrued and taken, balances and prior DSN filings. An error on a cumulative is not always visible immediately: it may only surface at year-end, on the taxable net reported to the administration or on a contribution adjustment.

For the record, the basis of the general reduction is subject to regulatory changes that we follow closely; our article on the single degressive general reduction in 2026 explains why this parameter deserves particular attention at migration time.

Data migration checklist#

• Current-year payroll cumulatives migrated identically
• Cumulative social security ceiling checked per employee
• Basis of the general contribution reduction controlled
• Cumulative taxable net consistent with prior payslips
• Withholding tax: rate and cumulative migrated
• Leave accrued and taken, balances aligned
• Applicable collective agreement configured
• Prior DSN filings available and archived

In switch cases, the most frequent sticking point is not the choice of tool but the quality of the data handed over. A company often arrives with incomplete history: cumulatives reconstructed from memory, a collective agreement no longer entirely certain, leave balances that do not add up. Our reading is simple: the value of outsourcing is built before the first payslip, in the rigour of the preparation, not in the provider's sales promise.

We systematically favour a switch at the start of the year and, when the calendar forces a mid-year switch, a payroll produced in parallel for the first month. This cross-check costs a little time but immediately reveals a cumulative gap, before it contaminates the DSN.

The risk most often overlooked is reversibility. At signing time, few directors ask how they would retrieve their data and configuration if they had to change provider. Yet payroll is a living asset: if you cannot cleanly extract your cumulatives and your history, you are locked into your tool, and the next switch will be painful. Check this point before signing, not the day you want to leave.

The second underestimated risk is legal. Because the provider produces the payslips, people assume it carries the risk. That is false: the employer remains liable. Outsourcing payroll does not exempt you from setting up a minimum of internal control over what is declared in your name.

A common case in SMEs: a company of around fifteen employees decides to outsource in September, under the pressure of a departure in the HR team. The switch is rushed, the year's cumulatives are migrated approximately. Everything seems to work until year-end: the cumulative taxable net declared does not match the payslips, and an adjustment becomes necessary. The problem did not come from the tool but from a data migration done too fast, without payslip-by-payslip control.

The lesson is not to avoid outsourcing, but never to treat the migration as a formality. When urgency forces a mid-year switch, the parallel payroll over one month and the per-employee check of cumulatives are the two safeguards that save year-end.

• Confidentiality and GDPR. Payroll data is sensitive. Frame its processing, hosting and access contractually.
• Reversibility. Require the ability to retrieve your data and configuration if you change provider.
• Clear scope. Write down who enters variable items and who validates payroll before the DSN is filed.
• Migration quality. Validate the switch only after checking cumulatives, ideally via a payroll produced in parallel.
• Maintained liability. Keep internal control: the employer remains liable for its social and reporting obligations.

As a firm registered with the Ordre des experts-comptables d'Île-de-France, we support these switches keeping this thread: delegate execution without ever losing control of compliance.