In previous versions of Odoo, the system did not require a default expense account. We would like to investigate the feasibility of a simple solution of just making this field not-required once again in v14.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Makes the default expense account optional on accounting journals, so users can save a journal without filling in a default account.
This module changes one small thing in Odoo Accounting: the default account field on a journal is no longer mandatory.
- Where it appears: the journal configuration form (Accounting journals), the same screen where you set up a journal's name, type and default accounts.
- What changes: on the fourth occurrence of the default account field in that form, the "required" rule is switched off. In practice, you can now save a journal even when that default account is left empty.
- Business effect: no validation error blocks you when the default account is blank, which is useful for journals where a single default account does not make sense, such as vendor bill journals.
- What it does not do: it adds no new menu, no new screen, no report, no automatic computation, no email and no scheduled action. It only relaxes a form-level requirement.
- Area touched: the
account.journalmodel's form view, inherited from the standard Accounting journal form.
Because the change is only a view attribute, existing journals and accounting entries are not modified; only the data-entry constraint on the journal form is relaxed.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/account-financial-tools.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.