Skip to content

[ADD] automatic_invoice: Implemented automated invoice sending by email #918

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: 18.0
Choose a base branch
from

Conversation

dhbr-odoo
Copy link

This PR introduces a new feature to automate the sending of customer invoices via email. The system is managed through a new section in the Accounting settings, allowing administrators to enable the functionality and configure a specific delay period in days. A daily cron job has been implemented to handle the automation, which identifies and processes all posted, unpaid customer invoices with an invoice date that has passed the configured delay. To prevent duplicate communications, a new boolean field, 'is_auto_email_sent', has been added to the invoice model to track which invoices have already been sent by this process.

Task ID :- 5020819

This commit introduces a new feature to automate the sending of customer invoices via email. The system is managed through a new section in the Accounting settings, allowing administrators to enable the functionality and configure a specific delay period in days. A daily cron job has been implemented to handle the automation, which identifies and processes all posted, unpaid customer invoices with an invoice date that has passed the configured delay. To prevent duplicate communications, a new boolean field, 'is_auto_email_sent', has been added to the invoice model to track which invoices have already been sent by this process.

Task ID :- 5020819
@robodoo
Copy link

robodoo commented Aug 17, 2025

Pull request status dashboard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants