LD Consulting · Demo

Test kit: reconciling hours

Everything you need to try the tool end to end with made-up data (no real data), and check that each correction it proposes matches your own logic.

The problem it solves

Two pieces of software that don't talk to each other: the sales software (hours sold) and the field tracking software (hours worked). Every month, someone exports both, spots the gaps, writes up the list of adjustments to make, and types them back by hand into the field tracking software. That takes 2 to 3 days of work, and only one person knows how. The tool does that work in a few seconds and shows every correction: what changes, from which value to which value, under which rule, and why. Nothing is changed silently. Anything that needs your judgement is marked "to check".

How to test it (5 minutes)

Open the tool and go to the Réconciliation tab.
Drop in suivi-terrain--detail-quotidien--TEST.xlsx and ventes--heures-vendues--TEST.xlsx (and, optionally, paye--conges--TEST.xlsx + referentiel-chantiers--TEST.xlsx).
Click Lancer (Run). The Toutes les corrections (All corrections) table appears.
Compare it with the reference output: regules-attendues--SORTIE-DE-REFERENCE.xlsx. You should find the 8 corrections described below.

The files in the test kit

Field tracking export · Daily detail suivi-terrain--detail-quotidien--TEST.xlsx
The hours actually worked: one row per employee per day (arrival, departure, working time, allowances, meals, job site, sales ledger…). The daily detail is the main input file.
Sales export · hours sold ventes--heures-vendues--TEST.xlsx
What was sold to the client, per job site and ledger. Used to compute the gap between sold and worked.
Payroll export · leave paye--conges--TEST.xlsx
The absences per employee (payroll is the reference). The file is optional. Without it, the Leave adjustment is flagged as pending.
Job site list referentiel-chantiers--TEST.xlsx
The list of known job sites (name and code). Used to spot job sites that aren't on the list.
Client list referentiel-clients--TEST.xlsx
Client code to company name (context only, not needed to run).

The 7 adjustments: the problem, the cost, and the case to test

Adjustment 1

Mileage allowance (MG)

The problem: A day when the truck is used should carry the standard mileage allowance (€10.63). But the allowance can also vary legitimately with distance.

Why it costs money: A wrong allowance means money paid out too high or too low, every month, across dozens of days.

To test: Julien MARTEL, 12/05, truck, MG = €11.40. The tool flags it "to check" without rewriting it (you decide whether the distance justifies it).

Adjustment 2

Meal break (continuous day)

The problem: A continuous day of 6 hours or more with no declared meal break must get half an hour for the meal.

Why it costs money: The meal time owed to the employee is forgotten, so pay is wrong and there is a labour-law risk.

To test: Romain LECLERC, 13/05, 9 hours straight, meal = 0. The tool adds 0.5 h.

Adjustment 3

39-hour contracts

The problem: For employees on a 39-hour contract, overtime counts from 8 hours a day, not 7.5.

Why it costs money: Using the wrong threshold means paying these employees too much (or too little) overtime.

To test: Bastien REYNIER, 14/05, 8.5 h. The tool recalculates overtime at the 8-hour threshold.

Adjustment 4

Leave (payroll and field tracking aligned)

The problem: At month end, the absences recorded in the payroll software are the reference, and field tracking has to match them.

Why it costs money: If field tracking and payroll disagree, the hours and leave balances are wrong on both sides.

To test: Two absences in the payroll export (Thomas GIRARD, Karim SAADI). The tool lists them to be copied into field tracking. (Needs the payroll export. Without it the adjustment is flagged as pending, never silently skipped.)

Adjustment 5

Job sites not on the list

The problem: Every row of hours must belong to a job site on the list.

Why it costs money: Hours on an unknown job site distort the margin analysis, so you can't tell where you make or lose money.

To test: Marc LAVIGNE, 15/05, job site "ZONE NORD (à coder)", not on the list. The tool flags it for reassignment.

Adjustment 6

Wrong sales ledgers

The problem: The sales ledger must match the employee's trade (a pool technician on S5/S6, a landscaper on V1 to V4…).

Why it costs money: A mismatched ledger distorts the analysis by activity, and revenue per trade no longer reads correctly.

To test: Antoine DUCROS (Pool) entered on ledger V2. The tool flags it as inconsistent.

Adjustment 7

Depot time with no report

The problem: Any time spent at the depot must be backed by a job report.

Why it costs money: Depot time with no report is potentially billable time lost, or a data-entry error.

To test: Florent CHABERT, 16/05, activity type "dépôt". The tool flags it so a report gets attached.

Data made up for the demo. No real client data, and every name is fictional. Names, amounts and thresholds can all be configured. The page was delivered in French, and this is a translation. LD Consulting · 2 June 2026.
← Back to demos and case studies