Accounting software comparisons
Dolibarr alternative: shared hosting philosophy, different scope
Dolibarr is a PHP business-management suite; PHP Ledger is a development preview centered on bookkeeping and source-linked reports.
Key takeaways
Compare the business modules you need before deciding that a smaller application will be easier to operate.
- Dolibarr documents contacts, orders, invoices, stock and accounting in a modular PHP application.
- Its double-entry accounting deserves a workflow test, not dismissal based on how the project evolved.
- PHP Ledger has a bounded AR/AP starter, optional Purchasing and Inventory, and manual tax configuration; it does not replace the breadth of an ERP/CRM suite.
- Both self-hosting approaches still require an accountable operator and a tested recovery procedure.
What kind of alternative is PHP Ledger?
It is a narrower accounting evaluation, not a substitute for the entire Dolibarr business suite.
The Dolibarr repository, checked on 16 September 2026, describes a PHP ERP and CRM covering contacts, suppliers, invoices, orders, stock and accounting. Its GPL-3.0-or-later licensing and published source make it a relevant option for businesses evaluating self-hosting. The appropriate comparison is not whether both products contain an accounts screen. It is whether the required operational record can reach that screen with the right source evidence.
Consider a small wholesaler using contacts, quotes, customer orders and invoices together. Moving only accounting into another application may require an integration, extra entry and a reconciliation process. None of those disappears because the destination has fewer modules. A different business may have no order-management requirement and may reasonably prefer a smaller scope. The choice follows the work, not a general rule that ERP is either necessary or excessive for every small business.
How does Dolibarr present double-entry accounting?
Its official documentation describes a dedicated accounting process with account assignment and ledger preparation.
The Dolibarr double-entry overview, checked on 16 September 2026, explains its accounting module and the preparation of accounting records from business documents. This is a concrete capability to test. We do not claim that a separate preparation step makes the result unreliable, and we have not audited an installed Dolibarr database. Ask your bookkeeper to demonstrate a source document, its account assignment, posting and export in the chosen version.
In PHP Ledger, supported posted sources reach a central double-entry posting service. The current preview includes receipts, expenses and general journals, with linked financial reports. Its new foundations do not supply complete customer invoicing or supplier billing. That makes it unsuitable as a replacement where those are everyday requirements, irrespective of whether its posting model appeals to a developer.
| Area | Dolibarr | PHP Ledger preview |
|---|---|---|
| Business scope | ERP and CRM modules | Core AR/AP, optional Purchasing/Inventory and bounded cash POS |
| Language | PHP | PHP 8.2 or newer |
| Licence | GPL-3.0-or-later; check bundled components | AGPL-3.0-or-later; check bundled components |
| Invoices and bills | Documented business functions to evaluate | Starter documents, payments, credits and ageing |
| Database compatibility | Use the exact release prerequisites | MySQL 8.4 is the validated profile |
| Country tax readiness | Check the selected country modules | Manual tax engine; no country rules or e-invoicing client |
Will both run on the same hosting account?
Possibly, but a shared PHP language does not establish matching database, extension or security requirements.
Read the Dolibarr prerequisites, checked on 16 September 2026, for the selected release. Then ask the hosting operator to confirm the actual versions and access available on your plan. A provider's general PHP support page does not prove that your subscription permits the required document root, command execution or backup access. Record the difference between what the panel can offer and what your account can actually use.
For PHP Ledger, the requirements page is the acceptance checklist. Its MySQL 8.4 profile is narrower than the phrase PHP and MySQL hosting may suggest. MariaDB and earlier MySQL releases are not certified alternatives. The project-owned core has no licence-key or licensing-server requirement. This article has not audited Dolibarr's installed outbound traffic, optional modules or update services; check those directly if network isolation is a requirement.
Where PHP Ledger loses
Dolibarr provides a broader documented business toolset, while the preview omits several processes many teams already need.
PHP Ledger is the wrong choice if replacing Dolibarr would mean losing customer invoicing, supplier records, stock operations or another required module. A business with a working Dolibarr configuration should first ask whether its problem can be solved through configuration, training or a supported update. Product replacement has a cost in historical access, procedures and staff familiarity. A narrower application can be easier to inspect while still being a worse operational fit.
PHP Ledger also cannot claim comparable maturity or jurisdiction coverage. Passing technical checks establishes bounded behavior of tested cases; it is not a general accountant endorsement. The preview is useful when a small core is the intended subject of evaluation and missing modules are acceptable. It should not be chosen on an assumption that future modules will arrive before a planned go-live.
Which demonstration should an implementer provide?
Ask for a complete transaction and a recoverable error using your required modules and roles.
- Enter a synthetic customer transaction and trace its accounting result.
- Use a second role to review it and confirm that permissions match responsibilities.
- Introduce a deliberate account or amount error and show the supported correction.
- Compare the original and corrected reports, including a closed-period attempt.
- Restore an isolated backup and reproduce the same evidence.
If the application prepares accounting in a separate step, include that step in the demonstration and assign responsibility for completing it. If exports feed another accountant's system, test the actual exchange file rather than a screenshot. Record rejected cases and manual work. A fair comparison reports these costs alongside the convenience of connected modules.
How do you avoid losing context during cutover?
Keep the link between business documents, detailed schedules and opening account balances.
- Module boundary
- The point where one business function passes a record or responsibility to another.
- Reconciliation
- A documented comparison of two records that should agree, with differences investigated rather than hidden.
Business module → reviewed accounting record → report → retained evidence
Keep old quotations, orders and invoices accessible where they remain relevant. Agree how partly completed work will finish. Reconcile bank and control-account balances at one cutoff date. A supplier total cannot replace a list of bills that still need payment, and an inventory value cannot replace quantities and valuation evidence. PHP Ledger's opening support documents serve cutover review. The starter's separate reviewed conversion maps supported balances into shared open items or stock without reposting the opening journal.
Questions and recommendation
Evaluate Dolibarr first when its connected modules are needed; use the preview only for a deliberately smaller scope.
Is Dolibarr only a CRM with accounting added?
Its official materials document a double-entry accounting module. Evaluate the actual accounting process rather than using project history as a substitute for a test.
Is PHP Ledger a direct migration destination?
No automatic full Dolibarr migration is claimed. Required data, mappings, open workflows and reconciliation need an explicit plan.
Read the FrontAccounting comparison for another PHP accounting option, and the ERPNext comparison for a larger ERP approach. The current PHP Ledger release notes describe its usable preview boundary. Primary documentation was checked on 16 September 2026; no installed competitor performance or compliance benchmark is claimed.
