Account Maturity Date Default
This addon defines as due date of the journal item the date of the journal entry (only if you have not defined one) only affecting receivable and payable accounts.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically fills in the due date of receivable and payable journal items with the journal entry date when no due date has been set, so you no longer have to type it manually.
This module changes how Odoo handles the due date (maturity date) on accounting entries. When a journal item is created on a receivable or payable account and no due date is entered, Odoo now copies the date of the journal entry into the due date field.
The same rule applies when an existing journal entry's date is changed: any receivable or payable line that still has no due date is updated to match the new entry date. Lines that already have a due date are left untouched, so any date you entered yourself is never overwritten.
- Works on customer and vendor balances only (receivable and payable accounts).
- No new menus, screens or reports are added; the behaviour happens silently in the background.
- Affects
account.moveandaccount.move.line, the models behind journal entries and their lines.
This is useful for businesses that do not use payment terms and simply want the invoice date to act as the due date, keeping ageing reports and payment follow-up consistent without extra data entry.
Depends on
Models and fields (2)
- account.move · extends an existing model
- account.move.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.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.