When configure for sequence prefix/suffix, this module add option range_end_ in addition to range_. to use the ending of the range instead of the current date, e.g. %(range_end_year)s instead of %(year)s.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a new placeholder for sequence prefixes and suffixes that uses the end date of a date range instead of the current date, e.g. %(range_end_year)s. Useful for numbering documents based on the closing period of a range.
This module extends the sequence configuration in Odoo. When you set up a sequence with date ranges (for example, yearly or monthly numbering), you can now use the special placeholder range_end_ in the prefix or suffix. This placeholder will be replaced by the end date of the range, not the current date.
For example, if you have a sequence with a range from January 1 to December 31, 2024, and you use %(range_end_year)s in the prefix, the generated number will include '2024' (the year of the range end) instead of the current year. This is helpful when you want document numbers to reflect the period they belong to, even if the document is created after the period ends.
The module adds a note in the sequence form view (under the date range settings) explaining how to use range_end_. It works with all standard date parts: year, month, day, etc. The change applies to the ir.sequence model and its date range sub-model, and it only activates when range_end_ is present in the prefix or suffix; otherwise, the standard behavior is unchanged.
Models and fields (1)
- ir.sequence · extends an existing model
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/server-ux.
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.