NextHr — Leave, expense reports & performance reviews

Balances · Approvals · Team calendar · Mileage scale · Weighted goals

In many companies, leave lives in a spreadsheet, expense claims live in an envelope, and the yearly review lives in a Word file nobody can find again. NextHr brings all three into Dolibarr, next to the rest of the business, with the calculation rules written once instead of redone by hand every month.

What the module brings

1. Leave types that match your own agreement

• Monthly accrual per type: 2.08 days a month for 25 days of paid leave, 0.92 for working time reduction, zero for sick leave.
• Yearly cap: once it is reached the module refuses the request instead of letting the counter drift.
• Carry-over capped, unlimited or forbidden, with a computed expiry date: carried days do not linger forever.
• Mandatory justification on the types that need one: a sick leave without a reason is refused as it is typed.
• Weekends counted or not, type by type.
• One colour per type, used everywhere: lists, cards and calendar.

2. Requests counted in working days, not in calendar days

• Saturdays and Sundays are skipped, unless the type says otherwise.
• Recorded public holidays are skipped too: a week holding a bank holiday costs four days, not five.
• Half days at both ends of the period. A half day on a Saturday removes nothing: that day is not worked anyway.
• A one-day request with a half day is worth half a day. It sounds obvious; it is exactly the kind of detail that costs a day of pay when it is wrong.
• Overlap control: the same period cannot be booked twice.
• Balance control before saving, with an option to allow a negative balance when your agreement does.

3. Approvals that leave a trace

• Full route: draft → submitted → approved, with a reasoned refusal and a cancellation.
• The reason for a refusal is mandatory. A refusal without an explanation is not a decision, it is a problem that comes back.
• A dedicated queue for the manager, showing each employee's remaining balance next to the request — in red when the request goes beyond it.
• Bulk approval: tick, approve.
• Days are held as soon as the request is submitted, not at the approval: nobody can spend the same days twice while you think it over.
• Every decision is written into the Dolibarr agenda.

4. The team calendar

• One row per employee, one column per day of the month.
• Each absence takes the colour of its type; requests still pending are shown in a faded tone.
• Weekends shaded, public holidays in pale red, today outlined.
• This is the screen you look at before approving a long weekend: you see at once who is already away.

5. Expense reports with a real mileage scale

• The scale lives in the database, per year, per fiscal power and per distance bracket. It is updated every January without touching the code.
• The French car scale imports in one click: 3 to 7 CV, three brackets each, fixed part included.
• A mileage line is always priced by the scale: the employee types the distance and the power, never the amount.
• A distance no bracket covers is refused, not silently reimbursed at nothing.
• For every other expense the employee types the amount shown on the receipt; the module works out the amount before tax and the VAT.
• Cap per line and mandatory receipt set per type: a 40 € meal against a 25 € cap is refused as it is typed, not three weeks later.
• An accounting code carried by the type, ready for an export.
• Route up to the payment: draft → submitted → approved → reimbursed, with the reimbursement date.

6. Yearly reviews that stop getting lost

• Campaigns: one review per employee, progress visible at a glance.
• Four steps: planned → self-assessment → manager assessment → completed.
• The employee writes their comment, the manager writes theirs. Both see both.
• Weighted goals with a target, a percentage of achievement and a rating. The overall rating is the weighted average — and a goal without a weight is ignored, not counted as a zero.
• The overall rating is spelled out: insufficient, needs improvement, meets expectations, above expectations, excellent.

7. Balances under control

• One table, every employee × every type, editable in place.
• Acquired, carried over, adjustment, taken, remaining: the remaining figure is never stored, it is always recomputed. A stored derived value always ends up lying.
• A "recompute the accrual" button applies the monthly accrual of each type to the months already elapsed, for everybody.
• Year closing: acquired, remaining, carry-over within the cap, lost days and expiry date, computed and written onto the next year.

What you gain

• No more leave spreadsheet. Working days, public holidays and half days are computed by code that is written once, tested, and does not slip.
• Fewer round trips. A short balance, a missing receipt or an exceeded cap are told to the employee as they type.
• A fair mileage scale. It lives in the database, year by year: the January update is an administrator's job, not a developer's.
• Traceable decisions. Every approval and every reasoned refusal goes to the agenda.
• Reviews you can use. Weighted goals and a computed rating beat a general impression.

Installation

1. Unzip the archive into htdocs/custom/.
2. Home > Setup > Modules, enable NextHr.
3. Grant the permissions in Users & Groups.

The activation creates the tables, five leave types, six expense types, the mileage scale of the year and the public holidays of the current and the next year. It is idempotent: running it again creates no duplicate.

Permissions

Nine permissions draw a clear line between what an employee sees and what a manager decides: reading and filing one's own records, reading everybody's, approving leave, approving and paying expenses, running the reviews, managing the balances, configuring the module.

Technical facts

• Dolibarr 16.0 and later — developed and validated on 21.0.2.
• PHP 7.4 and later — validated on 8.2.
• MySQL / MariaDB.
• Multi-company: an entity column on every table that carries an object.
• Five languages shipped: French, English, German, Italian, Spanish — 278 keys, identical across the five files.
• 11 tables, 14 classes, 21 screens.
• 139 unit tests, 280 assertions, all green.
• The screens work without JavaScript.
• No external dependency, no outgoing network call.
• GPL v3 — the code is readable and modifiable.

What the package holds

• The installable module (ZIP).
• The training manual in French (PDF).
• The technical documentation, the migration guide and the compatibility matrix.
• The full report of the tests that were run.
• 17 real screenshots.

NextHr 1.0.0 — published by NEXT GESTION — www.nextgestion.com — GPL v3 or later.

Demo of the NextHR module
Login : demo
Password : demo