For a mid-sized company with 300 to 2,000 employees, payroll outsourcing promises something simple: hand off payslip production to a specialist, receive the final files, and focus on everything else. The operational reality is considerably more complex.
Between your ERP and your outsourced payroll provider, there is a bidirectional data flow that must be automated, reliable, and fully auditable. Without this integration, you have not outsourced your payroll. You have created a new data silo.
This guide is aimed at CHROs and CFOs at mid-market companies (200 to 2,000 employees) who are outsourcing payroll or preparing to do so, and at CIOs who must architect the connection between the ERP and the payroll provider.
Why Payroll Outsourcing Creates ERP Integration Challenges
The Typical Flow Schema: Hub-and-Spoke
When a company outsources its payroll, it does not transfer its entire HR system to the provider. It delegates payslip calculation and statutory payroll filings (social security declarations, pension contributions, tax authority submissions). Everything else — contract management, absence tracking, training plans, performance reviews — remains in the internal HRIS or in the ERP’s HR module.
The data flow follows a hub-and-spoke model:
- The ERP (or internal HRIS) is the HR master record: permanent data — contracts, job grades, pay rates, bank account details
- At the end of each period, the HR team exports variable payroll elements (VPEs): overtime, bonuses, absences, time-off taken
- The provider receives these VPEs, integrates them into its calculation engine, produces payslips and statutory filings
- The provider returns payslips (PDF), analytical data files, and journal entries formatted for the ERP
- The ERP integrates these entries into general and cost-centre accounting
This schema is straightforward in theory. In practice, each step generates errors the moment it is handled manually or only partially automated.
The Risks Without Automation
VPE errors. An Excel file emailed to the provider can contain missing rows, duplicate entries, or hours logged in the wrong column. These errors translate directly into incorrect payslips.
Calendar misalignment. If the VPE export arrives two days late, payslips are produced behind schedule and statutory filings miss their deadlines. Late-filing penalties apply as soon as the legal submission window closes — typically the 5th business day of the following month in most European jurisdictions.
Master data drift. If an employee’s job grade changes in the ERP but that update is not forwarded to the provider before payroll close, the payslip is wrong.
Non-conforming journal entries. The provider generates a payroll file structured according to its own chart of accounts. If the company has updated cost centres in the ERP without notifying the provider, analytical allocations are incorrect.
The 5 Critical Flows to Automate
Automating the ERP/provider interface concentrates on five flows. Each has specific format, frequency, and traceability requirements.
1. Sending Variable Payroll Elements
VPEs are the most sensitive flow because they are variable by nature and consolidated from multiple sources: time-tracking or workforce management systems, expense tools, and management decisions (bonuses, ad-hoc increases).
The standard exchange format in automated interfaces is a structured flat file (CSV or XML) whose schema is agreed contractually with the provider. Each row corresponds to one employee (identified by a unique staff ID), each column to a coded payroll element.
2. Payslip and Analytical Data Returns
The provider returns two categories of files. Individual payslips in PDF (or PDF/A for archival compliance). And an analytical file, which breaks down personnel costs by entity, department, profit centre, or project code according to the cost allocation axes defined in the ERP.
This analytical file is critical for management control. Without it, the CFO cannot reconcile HR costs with budget reporting.
3. Automated Journal Entries
The payroll accounting entry records salary costs (gross pay, employer contributions) and accrued social liabilities (social security payables, pension and insurance providers). It must be imported into the ERP in a format compatible with the local chart of accounts.
Import formats vary by ERP: Cegid XRP Flex expects an OFX file or an API import; SAP S/4HANA accepts an IDoc or a CSV file with mapped GL codes; Sage X3 uses its own journal import format. The mapping must be defined during initial setup and documented for every future update.
4. Payment Flows
The provider can generate the SEPA credit transfer file for net salaries (PAIN.001.001.03 format) and direct debit notices for social contribution payments. This flow is optional: some companies manage payroll payments internally through their ERP treasury module; others delegate entirely to the provider. This choice has implications for banking access rights and approval workflows.
5. Workforce Reporting
Mandatory HR reporting obligations — workforce composition by category, payroll mass, management ratios, gender pay gap data — increasingly apply across EU jurisdictions, not just France. These indicators must be produced by the provider in a format that can be consolidated on the ERP or BI side. The EU Pay Transparency Directive (2023/970) is already adding new reporting requirements that intersect directly with payroll data exports.
Integration Modes: REST API, SFTP, Webhooks
Three technical architectures coexist in the market, with very different maturity levels and implementation costs.
Flat File Integration via SFTP
This is the most widespread mode, particularly among mid-tier providers and in companies whose ERP is more than ten years old. The principle: the ERP deposits VPEs in a secure SFTP directory at a fixed date, the provider retrieves them, processes them, and deposits the output files in return.
Advantages: straightforward to implement, no dependency on a third-party API, compatible with all ERPs.
Limitations: asynchronous (no real-time confirmation that the file was processed), no immediate feedback on format errors, risk of de-synchronisation if a file arrives corrupted or late.
REST API
The most modern providers offer a documented REST API that lets the ERP push VPEs synchronously and receive a structured confirmation. ADP makes its ADP Marketplace platform available, listing certified connectors for major ERPs (SAP, Oracle HCM, Workday) and standardised APIs documented in its developer portal. Payfit offers a REST API covering absence submission, payroll element import, and payslip retrieval.
API integration gives real-time visibility over exchange status and simplifies error handling. It assumes the ERP has a connector or integration module capable of calling REST endpoints.
Webhooks
A webhook is a notification pushed by the provider to the ERP when an event occurs — for example: payslip validated, statutory filing submitted, error detected on a VPE. This mode complements REST API integration and allows the ERP to trigger automated actions without repeated polling.
Payfit implements webhooks on key payroll cycle events. This makes it possible to automatically trigger the journal import as soon as payroll is closed, without waiting for a scheduled batch job.
iPaaS Middleware
For companies running multiple integrations (ERP + HRIS + payroll provider + treasury), an integration middleware (Boomi, Workato, Make, n8n) centralises the orchestration of all flows on one platform. The HR team defines a visual workflow: “when VPEs are validated in the HRIS, send them automatically to the provider and notify the management controller.”
This approach reduces dependency on custom development and simplifies maintenance when a vendor updates its API. The cost of an iPaaS middleware typically ranges from €500 to €3,000 per month depending on flow volume and vendor, weighed against the human cost of manual interfaces.
Main Provider Compatibility with Leading ERPs
ADP (Decidium, ADP iHCM, ADP Next Gen)
ADP is one of the world’s largest payroll and HR services groups, with more than 1.1 million business clients in over 140 countries (ADP Investor Relations). Its ADP Marketplace lists certified connectors for SAP HCM, Oracle HCM Cloud, Workday, and Microsoft Dynamics 365. The SAP connector enables bidirectional synchronisation of employee data and payroll elements without custom development.
In continental Europe, ADP offers Decidium (BPO payroll for mid-market and large enterprises) and ADP iHCM for companies wanting a cloud HRIS integrated with outsourced payroll management. The level of ERP integration varies by plan: native integration with SAP and Oracle is documented and supported; integration with mid-market ERPs (Sage X3, Cegid XRP Flex) typically goes through custom development or middleware.
Cegedim SRH
Cegedim SRH is one of the leading European references for payroll BPO serving mid-market and enterprise clients. The Cegedim Group subsidiary combines deep expertise in multi-country employment law and statutory reporting obligations. It has developed partnerships with the main ERP vendors present in Europe to facilitate data exchange.
The Cegedim SRH / Cegid XRP Flex connector is the most thoroughly documented, as both entities belong to the Cegid Group. Integrations also exist with SAP S/4HANA and Microsoft Dynamics 365 Finance, typically through standard exchange formats (CSV/XML SFTP) or API connectors available as an option.
Cegedim SRH is particularly well-suited to companies with multiple legal entities and multiple collective agreements — a common configuration in European groups with several operating subsidiaries.
Silae
Silae is the reference payroll engine for accounting firms in France and increasingly across southern Europe. It is used by accounting practices to manage payroll for their clients in a BPO model. The Silae approach differs: the accounting firm remains the interface between the company and the payroll engine. The company accesses its payslips and workforce reporting via a client portal; exchanges with the ERP go through open APIs or structured exports.
Silae offers native integrations with Cegid (via the partner programme), Sage, Pennylane, and Odoo. For other ERPs, integration goes through webhooks or scheduled CSV exports from the client portal. This model suits SMEs with 20 to 200 employees whose payroll is managed by an outsourced accounting firm; it is less suited to mid-market companies that want to keep HR management in-house.
Payfit
Payfit, founded in 2015, serves 22,000 business clients and reached €80 million ARR in 2026 (ZeroBullshit). Since summer 2026, Payfit has pivoted toward a managed service model: a team of payroll experts produces payslips on behalf of clients, reducing the error risk from variable element entry.
Payfit’s REST API covers absence submission, variable element imports, payslip retrieval, and webhooks on payroll events. On the ERP integration side, Payfit offers native connectors with leading accounting tools (Pennylane, QuickBooks) and standard exports toward Sage and Cegid. Integration with SAP or Oracle goes through the REST API and development on the ERP side.
Payfit operates in France, the UK, Spain, and Germany. It is well suited to companies with 50 to 500 employees and relatively standard payroll requirements. Organisations with complex collective agreements, multiple entities, or internationally mobile employees will find its capabilities limited.
Nibelis
Nibelis is a French HR software vendor that combines HRIS with an integrated payroll BPO offering in a unified platform. Its differentiator is combining the HRIS software and the payslip production service, which simplifies the architecture for mid-market companies that do not yet have an existing HRIS to preserve. Integration with Microsoft Dynamics 365 Finance is documented; exchanges with Sage X3 are supported via API or SFTP flows.
Governance and Mistakes to Avoid
Define a Shared Master Record Before Any Connection
The first pitfall in ERP/provider integration projects is the absence of a shared reference framework. Employee ID, entity codes, analytical codes, payroll element labels — each reference must be aligned between the ERP and the provider before the first automated exchange. An employee who carries the code EMP-1234 in the ERP and 034521 at the provider will generate errors from the first VPE file.
This mapping work is the least visible part of an outsourcing project, but the most critical for long-term reliability.
Version Your Interface Configuration
Every change to collective agreements, contribution rates, or analytical codes creates a new version of the interface configuration. Without versioning, an update on the provider side can break the ERP integration without anyone noticing until the next payroll close.
Best practice is to treat interface configurations like code: versioned, documented, and tested in a staging environment before going live.
Contractualise Interface SLAs
The contract with the provider must include SLAs specifically covering interface quality: payslip delivery timelines, format and completeness of the analytical file, VPE error turnaround time, API availability at month-end. Without SLAs, payroll can be delayed without any contractual recourse.
Don’t Go Live in Q4
Starting an ERP/provider integration project in Q4 is risky. It is the period of year-end statutory closes, account closures, and annual reporting. A new integration flow that fails in November or December has an immediate impact on cash flow and employee trust. Prefer a January or July go-live, with a parallel run period (manual fallback) of at least two payroll cycles.
When to Add an Intermediate HRIS
If your ERP does not have an HR module capable of structuring VPEs (time management, absence tracking, expense management), an intermediate HRIS may be necessary between the ERP and the provider. Tools such as Lucca or Factorial collect HR data, consolidate it, and transmit it to the provider in the correct format, while feeding the ERP with journal entries and analytical data.
This three-layer architecture (ERP / HRIS / payroll provider) adds complexity, but it is often the only viable option for a mid-market company whose ERP has no native HR module built for its markets.
Further Reading
Three complementary guides to build your HR IT architecture:
- Our complete guide on choosing between integrated HRIS and a dedicated ERP module — decision criteria, vendor comparison, costs
- Our comparison of Lucca, Factorial, Payfit and Sage Payroll Cloud in 2026 — to identify the intermediate HRIS best suited to your configuration
- Our guide on payroll cost management and workforce planning in ERP — to connect payroll data to your management control budget axes
