My accountCartFree DemoRequest a quote
Back to blog
News6 min readBy

Dolibarr 24.0.2 and 24.0.3: two maintenance releases published on November 11

Dolibarr 24.0.2 and 24.0.3 were released on 11 November 2026. What these fixes contain, what they change for an SME and how to plan the update.

Workshop bench with a wrench, gears and a paper checklist suggesting software fixes

Two releases on the same day, 24.0.2 then 24.0.3

The Dolibarr project published two maintenance releases of the 24 branch on 11 November 2026: 24.0.2 and 24.0.3. They follow 24.0.1 of 7 September, which we covered in our article on the first maintenance release of Dolibarr 24. These are maintenance releases: the release notes list only FIX lines, with no new feature announced. For an SME, the message is simple. If your instance runs 24.0.0 or 24.0.1, the right target is 24.0.3, which carries on the series of fixes. The 24.0.2 notes list more than two hundred of them, and the 24.0.3 notes list even more. You do not have to read them all. You need to spot the ones that touch your daily use: invoicing, stock, leave, expense reports, manufacturing, API. The following sections group them by area.

Access controls and API: what matters for security

Several fixes in 24.0.2 concern access rights. The notes mention missing checks on the payment pages for supplier invoices, VAT and salaries, a missing authorisation on an ajax call for email templates, an authorisation bypass on the leave API, and ownership checks added on several API endpoints (contracts, interventions, categories, bills of materials). One fix also addresses a risk of forced outgoing requests when importing external calendars. 24.0.3 continues: a per-object access check on documents and images, which was not running in 24.0, is restored, and read-only users can no longer edit an expense report. The sources give no CVE identifier for these points, so we will say no more about them. If your teams, such as sales reps or outside contractors, use the API or sensitive pages, these fixes are a reason not to postpone the update. Our guide to securing Dolibarr in production covers the other good practices.

Invoicing, accounting and payments

On the financial side, the fixes are numerous and concrete. 24.0.2 prevents the deletion, through the API, of a supplier invoice that is already paid, or of a paid VAT return that left an orphan bank line. It also fixes the next date of recurring invoices being shifted when the server time zone is ahead of UTC, and the sales journal keeping only the last deposit consumed. 24.0.3 fixes an invoice due date moved forward by one day at the switch to daylight saving time, an invoice paid in its own currency staying partially paid because of a one-cent difference, and the sales journal crashing when an invoice uses up a deposit. Closing an accounting period no longer risks writing the opening entries into the period being closed. Finally, the EPC code (the QR code for SEPA transfers) is no longer generated for a zero amount on a settled invoice. If you are preparing your year-end, read our closing checklist again after the update.

Stock, receipts, shipments and manufacturing

Workshops and warehouses are particularly affected by 24.0.3. A manufacturing order can no longer be consumed or produced while it is a draft, already produced or cancelled. An order with consumed or produced lines can no longer be set back to draft. Cancelling or deleting a line no longer doubles a negative consumption. On receipts, deletion no longer returns stock for lines that never had a movement, and the expiry and sell-by dates of lots entered on the record are no longer lost or swapped. For inventories, answering No to saving or cancelling no longer carries the action out, and barcode scanning no longer adds lines without a lot that blocked data entry. The same serial number can no longer appear twice in a stock transfer or on two lines of a shipment. If you work with lots, also read our article on multi-warehouse stock.

Leave, expense reports and other modules

Leave management gets a batch of fixes in 24.0.3. The monthly credit never ran if the last update date was empty. Cancelling an approved leave that had not yet been debited refunded one day too many. Bulk validation could debit the balance twice. Half-days were counted as full days. For expense reports, a report paid in several instalments never moved to the paid status, and a validated report line could be deleted. Calendars no longer shift recurring events by one hour at the clock change. Whit Monday (Lundi de Pentecôte) is corrected for France, Belgium and Austria. TakePOS keeps the decimals of a free amount when the comma is the separator. These points have a direct effect on payroll and the till: check the leave balances of a few employees after the update.

  • Compare the leave balance of two or three employees before and after the update.
  • Test an expense report settled in several payments.
  • Check a TakePOS cash-up with a decimal free amount.

Planning the update without surprises

A maintenance release usually deploys without any change in behaviour, but it touches tables, permissions and PDFs. Proceed in order. First, back up the database and the documents folder. Then test on a copy, with your modules and your customised PDF templates. The 24.0.3 notes mention a migration of API tokens when the table prefix is not llx_: if that is your case, check your integrations afterwards. Then go live outside invoicing hours. If the 24 branch is too recent for you, 23.0.4 remains the last release of the 23 branch, published on 20 August. If you have no technical team, the DolicraftUpgrade module automates the backup, the preliminary checks and the rollback.

  • Back up the database and the documents folder.
  • Restore this backup on a test copy.
  • Check your third-party modules and PDF templates on the copy.
  • Check the integrations that use the API after the switch.

Next step: move to 24.0.3

Note the version shown under Home, then Setup, then System. If you run 24.0.0 or 24.0.1, aim for 24.0.3: it follows 24.0.2 and stays on the same branch. The full notes are published for 24.0.2 and 24.0.3. Go through them with the person in charge of each business area concerned: accounting, logistics, HR. If you prefer to delegate, our team can handle the backup, the testing and the switch as part of maintenance. To set an update date or ask about a specific fix, contact us.

Need help with Dolibarr?

Our team of Dolibarr experts is available to support you in your projects: implementation, migration, custom module development and training.