Lucca integrator: connecting payroll, accounting and the directory without creating duplicates
Take ACME France (a fictitious example). Léa Martin leaves the company on June 30. Her manager enters the departure in Lucca, the date appears and the record switches to "left". In September, the payroll software still shows her employee ID as active, and her email account still opens the shared folders. The information was entered once, in the right place. It simply never arrived anywhere else.
This is the kind of situation that prompts a finance and administration department or an HR manager to look for a Lucca integrator. Proposals can look alike on module configuration and diverge on everything else: connections to payroll, accounting and the directory, data migration, and what happens after go-live. This guide helps you read these proposals and compare them on what matters.
What a Lucca integrator does
The term covers very different services: what you can see, what makes the project, and what remains your responsibility.
Configuring the modules, the visible part
Leave approval workflows, expense categories, the managers' role in approvals, individual reviews: this is the part you see in a demo and test first. It takes good knowledge of the tool, but it can be reworked without touching other systems. If you want to review what an HRIS automates day to day, our article on HRIS tools covers it in detail; that is not the subject here.
Connecting Lucca to everything else, the part that makes the project
An absence approved in Lucca must become a payroll variable. An approved expense report must become an accounting entry, with the right account and the right analytical axis. A new hire must open accounts, a departure must close them. Each of these connections is a flow: data that leaves one system, on a given date, in a given format, for a system with its own rules. This is where re-keying, files sent by email and discrepancies found at closing are hiding.
What it does not do for you
An integrator cannot decide alone which system is authoritative for the employee record, or which leaving date to keep when Lucca and payroll show two. Nor can they guess which employee IDs are duplicates left over from a rehire or a change of entity. These decisions belong to the company. A good provider puts them on the table during scoping; a less good one discovers them during acceptance testing.
Module configuration shows up in the demo; flows show up on payday.
Four flows to scope
Four flows need scoping. Describing them in your request for proposals, even briefly, changes the quality of the answers.
The employee master data and its employee ID
It all starts with one question: where does the authoritative employee record live? In Lucca, in the payroll software, or in a spreadsheet kept by HR? As long as the answer is "a bit of everywhere", each connector copies the discrepancies. The employee ID is the identifier that matches the same person from one system to another: it must be unique, identical everywhere and never reassigned. At ACME France (a fictitious example), an employee rehired after two years has a new ID in payroll and the old one in Lucca: two records, two histories and a manual reconciliation at every closing.
Payroll variables
Absences, leave, overtime, bonuses entered by managers: these items must reach payroll before a closing date, in the format expected by the software or the firm that prepares the payslips. To decide: on what date is the month frozen? What happens to an absence entered after that date? Who corrects it, and in which system? Outsourcing payroll to an accountant does not remove the flow: it only changes its recipient and format.
Expense reports and entries to accounting or the ERP
An approved expense report is only useful to the accounting department if it arrives with the right account, the right VAT rate, the right cost center and an attached supporting document. The same goes for payroll entries when they have to reach 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 connected to the Infor LN ERP, with history migrated, to put an end to double entry (see the Focal case). It is not an HR project, but the logic is the same: data entered once and reused without re-keying wherever it is needed.
Joiners and leavers in the directory
Email, application access, the badge: these accounts do not live in the employee record but in the company directory and in each tool. Lucca can tell the IT department that access needs to be created or deactivated; someone, or a flow, still has to do it. If accounts are created and closed by hand from an HR email, the time between the leaving date and the actual closure depends on someone's memory. Connecting these events to the authoritative employee record is a simple flow to describe: name it explicitly in your request for proposals so it is not missing from the proposal.
The diagram below follows a payroll month and marks the point where data entered late distorts the rest of the month. If your database already contains duplicates, the method for fixing them without recreating everything is detailed in our article on duplicates: it applies to employee records as well as customer records.
Choosing your Lucca integrator
Once the flows are described, five criteria separate the proposals.
- The flows actually covered. Does the proposal name each flow, its direction, its frequency and its format, or does it just say "interface with payroll"?
- Data migration and control. Who matches the employee IDs, who handles duplicates, who approves the migrated file? If the answer is "the client", you need to know before signing.
- Knowledge of your payroll and accounting. Connecting Lucca to a specific payroll package, or to a firm with its own formats, requires knowing the other side of the flow.
- Connector maintenance. A vendor updates its tool, a firm changes software, a chart of accounts moves. Who fixes the flow when it breaks, and how quickly?
- Acceptance testing on a real payroll month. Testing on sample data proves nothing. The only test that counts compares the payslips and entries produced by the new flows with those of a real month.
Behind these criteria, you will meet three provider profiles. The configuration partner knows Lucca in depth and delivers well-configured modules; the connections may remain your job. The payroll specialist masters payslips and collective agreement rules; they handle the payroll flow first, not necessarily accounting or the directory. The flow provider starts from the data: they establish the master data, align the employee IDs and build the connections end to end. The right profile is the one that covers what is stuck at your company. The specific questions to ask each one come out of the questionnaire at the top of this article.
What drives the budget
The cost of an implementation cannot be deduced from the number of modules purchased. It depends on factors that can almost all be assessed before you go out to providers.
- The number of flows. Each connection adds design, development or configuration, testing and maintenance.
- In-house or outsourced payroll. The flow does not have the same recipient, format or contacts.
- The number of entities or sites. Several companies often mean several payroll files, several charts of accounts and differing rules.
- The state of the master data. Duplicates, mismatched employee IDs or headcounts that do not match between Lucca and payroll have to be dealt with before any connector.
- Historical data migration. Migrating this year's leave balances and migrating several years of expense reports are two different jobs.
- Connector maintenance. You plan for it from the start, or you pay for it at the first incident.
The logic is the same as for a broader management project: what moves the bill is data and connections, not the license. Our article on ERP projects develops this reasoning from the ERP side.
How a project unfolds
A well-run project starts by mapping the flows: which data leaves Lucca, for which system, on what date, in what format, and who handles it today. Next comes choosing the authoritative system for each item in the employee record, put in writing so nobody reopens the debate during acceptance testing.
Cleanup follows: reconciling headcounts between Lucca and payroll, aligning employee IDs, dealing with duplicates and orphan records. Module configuration moves forward in parallel. The connectors are then built one by one, on a clean base.
Acceptance testing takes place on a real payroll month, alongside the old way of working: you compare the variables sent, the payslips, the entries and the accounts opened or closed. Go-live only happens once these discrepancies are explained. That leaves maintenance, to be organized from signature: who monitors the flows, who is alerted when one fails, who fixes it.
A connector placed on a database that doesn't match fixes nothing: it just copies the discrepancy faster.
Where to start
Start with a single flow: the one that costs you the most today, in re-keying, payslip corrections or accounts left open. Describe it precisely, check that the employee record feeding it is authoritative, then move on to the next. This description serves as your specifications and makes proposals comparable.
The question of proximity often comes up: do you need a Lucca integrator in Bordeaux, Lille, Lyon, Nantes, Strasbourg or Marseille? It matters less than mastery of your flows. This type of project can be run remotely, with a few on-site workshops for mapping and acceptance testing. The Lucca page in our tools section sums up what the tool covers; for module details, the reference remains the vendor's website, lucca.fr.
turnK makes HR data reliable and connects it to payroll, accounting and the directory: employee master data, employee ID alignment, flows to management systems. If you would like your list of flows reviewed before you go out to providers, talk to a consultant about your project. For connections with an ERP, see also our ERP services and our article on ERP and CRM integration.
the most common questions
A Lucca integrator is a service provider that sets up the tool in your company: module configuration, migration of employee data and, depending on their scope, connections to payroll, accounting and the directory. These connections and the data migration are what proposals should mainly be compared on.
You connect Lucca to payroll by first describing the flow: which variables are sent (absences, leave, bonuses), at what closing date, in what format and to which software or firm. You then need an identical employee ID in both systems, followed by acceptance testing on a real payroll month before go-live.
Approved expense reports must reach accounting or the ERP as entries, with the right account, the right VAT rate, the right analytical axis and the supporting document. The format and frequency of this export are agreed with the accounting department before the provider quotes for them.
No, proximity matters less than mastery of your payroll, accounting and directory flows. A Lucca project can be run remotely, with a few on-site workshops for flow mapping and acceptance testing, whether you are in Lyon, Bordeaux, Lille, Nantes, Strasbourg or Marseille.



