Lucca Integrator: connecting payroll, accounting, and directory without creating duplicates

Let’s take ACME France (fictitious example). Léa Martin leaves the company on June 30th. Her manager enters the departure in Lucca, the date appears, and the record is marked as 'exit'. In September, the payroll software still shows her employee ID as active, and her email account still has access to shared folders. The information was entered once, in the right place. It simply did not go anywhere else.

This kind of situation prompts an administrative and financial management or HR manager to seek a Lucca integrator. Proposals may be similar in module configuration and differ on everything else: connections with payroll, accounting, and directory, data import, and what happens after deployment. This guide helps to read these proposals and compare them on what matters.

What a Lucca integrator does

The term covers very different services: what is visible, what drives the project, and what remains your responsibility.

Configure the modules, the visible part

Leave approval workflows, expense categories for expense reports, managers' role in approval, individual interviews: this is the part shown in demonstrations and tested first. It requires good knowledge of the tool but can be adjusted without touching other systems. If you want to review what an HRIS automates daily, our article on HRIS tools it details it; that’s not the subject here.

Connect Lucca to the rest, the part that drives the project

A validated absence in Lucca must become a payroll variable. An approved expense report must become a accounting entry, with the correct account and the correct analytical axis. An arrival must open accounts, a departure must close them. Each of these links is a flow: data that leaves one system, at a given date, in a given format, towards a system with its own rules. This is where re-entries, files sent by email, and discrepancies discovered at closing are stored.

What it does not do for you

An integrator cannot decide alone which system is authoritative on the employee record, nor which exit date to retain when Lucca and the payroll display two. It also cannot guess which employee IDs are duplicates inherited from rehire or entity change. These decisions belong to the company. A good provider raises them during scoping; a less good one discovers them during testing.

Module configuration is demonstrated; the flows, however, are visible on payroll day.

Four flows to scope

Four flows need to be scoped. Describing them in your consultation, even briefly, improves the quality of responses.

The employee reference data and its employee ID

It all starts with a question: where does the authoritative employee record reside? In Lucca, in the payroll software, or in a spreadsheet maintained by HR? As long as the answer is "everywhere," each connector copies discrepancies. The employee ID is the identifier that allows matching the same person across systems: it must be unique, identical everywhere, and never reassigned. At ACME France (fictitious example), a re-hired employee after two years has a new ID in payroll and the old one in Lucca: two records, two histories, and manual reconciliation at each closing.

Payroll variables

Absences, leave, overtime, bonuses entered by managers: these elements must reach payroll before a closing date, in the format expected by the software or the firm preparing the payslips. To decide: at what date is the month frozen? What happens to an absence entered after this date? Who corrects it, and in which system? An outsourced payroll with an accountant does not eliminate the flow: it only changes the recipient and the format.

Expense reports and entries to accounting or ERP

A validated expense report is only useful to the accounting department if it arrives with the correct account, the correct VAT rate, the correct cost center, and an attached supporting document. The same applies to payroll entries when they need to be integrated into the general ledger or an ERP. The principle is the same as for any business tool connected to a management system: at Focal, the customer service tool was linked to the Infor LN ERP, with historical data transferred, to eliminate double data entry.see the Focal case). It’s not an HR project, but the logic is the same: data entered once, reused without re-entry where it is needed.

New hires and departures in the directory

The messaging, application access, badge: these accounts do not live in the employee record but in the company directory and in each tool. Lucca can notify the IT department to create or deactivate access; someone or a flow must handle this. If accounts are created and closed manually, based on an HR email, the delay between departure date and actual deactivation depends on someone’s memory. Linking these events to the employee record that serves as proof is a simple flow to describe: explicitly name it in the consultation so it is not missing from the process.

The diagram below follows a payroll month and marks where late data entry disrupts the rest of the month. If your database already contains duplicates, the method to correct them without recreating everything is detailed in our article on duplicates : it applies equally to employee records and client records.

Choose your Lucca integrator

Once the flows are described, five criteria differentiate the proposals.

• The flows actually covered. Does the proposal name each flow, its direction, its frequency, and its format, or does it simply say “interface with payroll”?
• Data transfer and control. Who matches the employee IDs, who handles duplicates, who validates the resumed file? If the answer is “the client,” it’s important to know before signing.
• Knowledge of your payroll and accounting. Connecting Lucca to a specific payroll software, or to a firm with its own formats, requires understanding the other side of the flow.
• Connector maintenance. A publisher updates their tool, a firm changes software, a chart of accounts shifts. Who fixes the flow when it breaks, and within what timeframe?
• A test on a real payroll month. Testing with sample data proves nothing. The only meaningful test compares the payslips and entries produced by the new flows to those of a real month.

Behind these criteria, three types of providers are encountered. The configuration partner knows Lucca deeply and delivers well-configured modules; the connections may remain your responsibility. The payroll specialist masters payslips and collective agreements; they handle the payroll flow first, not necessarily accounting or directory. The provider connecting flows starts from the data: they establish the reference, align employee IDs, and build end-to-end links. The right profile is the one that addresses your specific issues. The precise questions to ask each are outlined at the beginning of the article.

What makes up the budget

The cost of implementation is not deducted from the number of modules purchased. It depends on factors that can almost all be assessed before consultation.

• The number of flows. Each connection adds a design, development, or configuration, validation, and maintenance.
• An internalized or outsourced payroll. The flow does not have the same recipient, format, or contacts.
• The number of entities or establishments. Multiple companies often mean multiple payroll files, different chart of accounts, and varying rules.
• The state of the reference system. Duplicates, divergent employee IDs, or workforce discrepancies between Lucca and payroll are addressed primarily through the connector.
• Historical data migration. Retrieving current year leave balances and importing several years of expense reports are two different projects.
• Connector maintenance. It is planned from the start, or it is paid for at the first incident.

The logic is the same as for a broader management project: what affects the invoice are the data and connections, not the license. Our article on ERP projects develops this reasoning on the ERP side.

The project process

A well-managed project begins with mapping flows: which data leaves Lucca, to which system, on what date, in what format, and who handles it today. Then comes the choice of the system that is authoritative for each employee record, documented in writing so no one re-discusses it during validation.

Cleaning follows: reconciling workforce data between Lucca and payroll, aligning employee IDs, handling duplicates and orphan records. Module configuration progresses in parallel. The connectors are then built one by one, on a clean basis.

The process is carried out over a real payroll month, alongside the previous system: variables transmitted, payslips, entries, and open or closed accounts are compared. Deployment only occurs once these discrepancies are explained. Maintenance remains, to be organized from the signing: who monitors the flows, who is notified when one fails, who corrects it. Our article on HR management linked to the information system provides a broader overview of these connections.

A connector placed on a database that does not match does not correct anything: it copies the discrepancy faster.

Where to start

Begin with a single flow: the one that costs you the most today, in re-entries, payslip corrections, or open accounts. Describe it precisely, verify that the employee record feeding it is accurate, then move on to the next. This description serves as a specifications document and makes proposals comparable.

The question of proximity often comes up: should there be a Lucca integrator in Bordeaux, Lille, Lyon, Nantes, Strasbourg, or Marseille? It matters less than mastering your flows. This type of project can be managed remotely, with a few on-site workshops for mapping and testing. The Lucca sheet on our tools page summarizes what the tool covers; for detailed modules, the reference remains the publisher’s website, lucca.fr.

turnK ensures the reliability of HR data and links it to payroll, accounting, and directory: employee reference data, alignment of employee IDs, flows to management systems. If you want your list of flows reviewed before launching the consultation, discuss your project with a consultant. For connections with an ERP, also see our ERP services.