NewsMarch 10, 20269 min read

Dolibarr 23: What You Need to Know

Overview of Dolibarr 23: enriched analytical accounting, task categories, shipment signing, web portal improvements and extended REST APIs.

Dolibarr 23: a major release driven by community needs

Dolibarr 23 was released on February 28, 2026, followed by minor corrective releases including 23.0.2 in early April. This major release does not revolutionize the interface but focuses its effort where users and integrators needed it most: analytical accounting, project management, web portal, shipments and a significantly extended REST API. The spirit of this version is to consolidate existing building blocks and fill in functional gaps reported by the community, rather than to add flashy new modules.

Version 23.0 released on February 28, 2026 by the Dolibarr team
PHP 7.2 is now the minimum supported version
Ongoing fixes and stabilization through 23.0.x releases
Release driven by community-expressed needs
Update recommended after testing on a staging environment

Accounting: analytical axes, reconciliation and ISTEA export

The accounting module gets several major improvements in Dolibarr 23. Accounting by payment type is now supported, greatly simplifying journal entry allocation when you handle several payment methods. Reconciliation on general accounting accounts enables a finer matching mechanism, equivalent to bank reconciliation but available on any account in your chart of accounts. Analytical axes are extended to more documents, offering more consistent profitability tracking across orders, invoices and entries. Finally, a new ISTEA export mode joins the existing standard exports.

Accounting by payment type and improved discount handling
Reconciliation on general accounting accounts (equivalent of bank matching)
Analytical axes available on more commercial documents
New ISTEA accounting export mode
New funnel widget for sales opportunity tracking

Projects and tasks: categories, auto-references and consolidated views

Dolibarr 23 starts phase 1 of the project task overhaul with the arrival of task categories. This is a long-standing community request: classify tasks by business type and filter views accordingly. The project list gains a new parent project column to better visualize hierarchies, and the project overview can now hide paid orders to focus on what remains to be done. On the API side, tasks can be created with an automatically generated reference.

Task categories — phase 1 of 3 (progressive rollout)
Parent project column in the project list
Project overview: option to hide already-paid orders
Automatic task reference generation via API
More complete time tracking through new REST endpoints

Shipments and proposals: signing, messaging and agenda

Shipments finally gain features that were long missing: built-in signing (on par with quotes), standalone creation without a source order, and transfer number tracking. Orders and shipments receive new messaging and agenda tabs to consolidate the history of exchanges and related events. Commercial proposals also benefit, with the added possibility of specifying a shipping address distinct from the billing address.

Shipment signing (same ergonomics as for quotes)
Standalone shipment creation without a source order
New messaging and agenda tabs on orders and shipments
Shipping address distinct from billing address on proposals
Transfer number tracking on shipments

Web portal, members and communication

The WebPortal module continues to mature with several useful improvements: navigation through shared folders, public donation pages with CAPTCHA support, and finer card and field management. On the member management side, a free numbering module appears for those who do not want to use the standard sequence, and a merge feature finally allows consolidating duplicate members. Synchronization between third-parties and members gains more control. Agenda events can now send SMS reminders.

Web portal: folder navigation and donation pages with CAPTCHA
Free numbering module for members
Duplicate member merge feature
SMS reminders on agenda events
Contact tab on product and service records

REST API: many new endpoints

This is probably the most appreciated part for integrators. The Dolibarr 23 REST API gains many endpoints that were sorely missing to industrialize integrations: product lots, holidays and leaves, member statistics, VAT lists and payments, stock movements, email templates, time tracking on projects and tasks, and contact management on several modules. The stock module also gains movement endpoints that let you automate adjustments from an external tool or mobile app. Developers will also note the introduction of the TRIGGER_PREFIX property to ensure uniqueness of trigger keys per business object.

New APIs: product lots, leaves, member stats, VAT
Stock movement and email template endpoints
Contact management exposed via API across several modules
Project and task time tracking accessible via API
TRIGGER_PREFIX property for unique trigger keys (developers)

Security, data policy and technical cleanup

Security progresses with a new admin page to configure HTTP security headers (CSP, X-Frame-Options, HSTS, etc.) directly from the interface, without touching the web server configuration file. The datapolicy module, very useful for GDPR compliance, reaches stable status with mature anonymization features. On the technical side, Dolibarr 23 does some cleanup: some deprecated functions and properties are definitively removed, notably the `run_trigger()` method which must be replaced by `runTrigger()`, and the `timepicker.js` library is removed in favor of more modern components. Third-party module integrators should therefore test their modules on Dolibarr 23 before any production deployment.

HTTP security headers configuration page in admin
Datapolicy module promoted to stable for GDPR anonymization
Deprecated methods removed: run_trigger(), img_pdf(), etc.
timepicker.js library removed from core
Incoterms 2025 integrated natively

How to update to Dolibarr 23

Updating to Dolibarr 23 follows the usual best practices, with a few points of attention specific to this release. First, make sure your environment supports at least PHP 7.2 (most modern hosting already runs PHP 8.1 or 8.2, which is preferable). Fully back up your database and file tree before any operation. It is essential to test the upgrade on a staging environment, especially if you use third-party modules, because some deprecated functions have been removed in this release and some modules may require an update. Once acceptance is validated, schedule the production switch outside business hours. If you have doubts or your instance is critical, our Dolicraft team is here to secure the migration and verify the compatibility of your ecosystem.