Contract Service Dates
This module adds Service Start Date and Service End Date fields to contract lines, allowing you to track the actual service period independently from the billing dates.
Table of contents
Use Cases / Context
Contract lines in the base contract module carry a single start date and end date that drive the recurring invoicing schedule. There is no dedicated field to record the period during which the service is actually delivered, which is often distinct from the billing period. This module fills that gap.
Usage
On a contract line form, a new Service Dates group is displayed in the Recurrence tab, below the contract line start and end dates:
Service Start Date: start of the service period. Populated automatically from the contract line start date and kept in sync with it unless manually overridden.
Service End Date: end of the service period. Populated automatically from the contract line end date and kept in sync with it unless manually overridden.
Once a service date is set to a value different from its corresponding contract line date, it is considered decoupled and will no longer be updated automatically when the contract line date changes.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Benoit Aimont benoit.aimont@acsone.eu (https://www.acsone.eu/)
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/contract project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-contract-service-dates 18.0.1.0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_contract_service_dates-18.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_contract_service_dates-18.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_contract_service_dates-18.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_contract_service_dates-18.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 26.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d17246dc594234ad46df44133a14c8085055f6225f11f60121f884cc53d7e12f
|
|
BLAKE2b-256 checksum How to use checksums |
852c229b2b5c269dc05ff932e9f5749f8ed9c932cdda9196491568d6ca83f351
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-contract-service-dates 18.0.1.0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
