[18.0][ADD] contract_line_defer: Avoid invoicing line until activated

[tobiaszehntner]

Defer Contract Lines to avoid invoicing while start date unknown

Enable to defer contract line's invoicing. If a contract line start date is not known, it can be deferred. It will not be invoiced until manually activated.

• Based on [18.0][IMP] contract: hook for line is invoiceable #1341
• contract_line_defer: module to defer contract lines
• product_contract_line_defer: bridge module for product_contract
• contract_line_defer_successor: bridge module for contract_line_successor

[acsonefho]

Only minor stuff!
Really good job 💪

[bosd]

@tobiaszehntner Can you please fix the tests?

[tobiaszehntner]

@tobiaszehntner Can you please fix the tests?

rebased branch which fixed the tests. Added extra tests for improving coverage.

[bosd]

LGTM

[bosd]

@gurneyalex Can you please merge?

[qgroulard]

LGTM (code review)

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[victor-champonnois]

Functional test OK. Thank you for the great readme.

Just two non-blocking comments :

• I note that the module contract_service_dates is not affected by the defered field. It could be nice to have a glue module at some point.
• Also, the field "Next Period Start" is still filled and visible even the line is deferred. This could generate confusion.

[tobiaszehntner]

• I note that the module contract_service_dates is not affected by the defered field. It could be nice to have a glue module at some point.
• Also, the field "Next Period Start" is still filled and visible even the line is deferred. This could generate confusion.

@victor-champonnois Thanks! I fixed the next period start (now False if deferred) and added a point to the readme/Roadmap regarding contract_service_dates module.

[rousseldenis]

@tobiaszehntner Contract line date_start and date_end are computed. Don't use onchanges.

[tobiaszehntner]

fixed for date_start and left for date_end as it's not computed on the contract mixin

[tobiaszehntner]

@rousseldenis hah that doesn't actually work. The onchange was for the single purpose when the user de-selects is_deferred in the view. but if I move it to the view it triggers on any contract.line that has is_deferred False. I reverted to onchange

2026-09-22 09:36:11,339 337 ERROR odoo odoo.addons.contract_sale_generation.tests.test_contract_sale: FAIL: TestContractSale.test_contract
Traceback (most recent call last):
  File "/__w/contract/contract/contract_sale_generation/tests/test_contract_sale.py", line 25, in test_contract
    self.assertEqual(self.contract_line.recurring_next_date, recurring_next_date)
AssertionError: datetime.date(2026, 10, 22) != datetime.date(2020, 2, 15)
 
2026-09-22 09:36:11,492 337 ERROR odoo odoo.addons.contract_sale_generation.tests.test_contract_sale: FAIL: TestContractSale.test_contract_autoconfirm
Traceback (most recent call last):
  File "/__w/contract/contract/contract_sale_generation/tests/test_contract_sale.py", line 40, in test_contract_autoconfirm
    self.assertEqual(self.contract_line.recurring_next_date, recurring_next_date)
AssertionError: datetime.date(2026, 10, 22) != datetime.date(2020, 2, 15)