Account credit control attach invoices
This module enhances the Odoo Credit Control process by allowing users to automatically attach detailed customer invoice reports to each credit control summary. When printing or sending a credit control summary (reminder) to a customer, the selected invoice report is merged into the same PDF document, providing a complete overview of outstanding credits and the underlying invoices in a single file.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you choose an invoice report that is automatically merged into the credit control summary PDF, so customers receive the reminder and the underlying invoices in one document.
This module extends the credit control process so that the credit control summary sent to a customer can include the actual invoices in the same PDF file.
- In Settings, under the credit control section, a new field "Report to attach to credit control summary" lets you pick which invoice report (limited to reports for
account.move) should be attached. - The setting is stored per company on
res.companyand is editable fromres.config.settings. - When the credit control summary report is generated (the reports
account_credit_control.report_credit_control_summaryandaccount_credit_control.credit_control_summary), the module automatically renders the selected invoice report for every invoice linked to the credit control lines of the communication, then merges all PDFs into a single file. - The merge is done in memory by extending
ir.actions.report; if no report is configured, the standard behaviour is kept unchanged. - This applies both when printing and when sending the summary, since it hooks into the PDF rendering of the report.
It touches the credit control communication data through credit.control.communication and its credit_control_line_ids.invoice_id links, and adds a configuration field on res.company and res.config.settings.
Depends on
Models and fields (3)
- res.company · extends an existing modelcredit_control_report_to_attach_id (Report to attach to credit control summary)
- ir.actions.report · extends an existing model
- res.config.settings · extends an existing modelcredit_control_report_to_attach_id
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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/credit-control.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0Configuration Steps
- Dependencies: Ensure that the
account_credit_controlmodule is installed and configured in your Odoo database. - Module Installation: Install this module (
account_credit_control_attach_invoice) via the Apps menu. - Configure Report to Attach:
- Go to the Accounting\Invoicing app.
- Open the Configuration settings.
- In the Credit Control section, locate the "Report to attach" field.
- Select the invoice report you want to merge with credit control summaries (e.g., Customer Invoice, Invoice with Payments, etc.).
- Save your settings.
Usage
Source · Odoo 18.0- Create or select a Credit Control Run from the Credit Control Run menu in the Accounting\Invoicing app.
- Use the Compute Credit Lines button to generate credit control lines for overdue invoices.
- Review the generated credit control lines. Each line represents an invoice or receivable to follow up.
- When ready to communicate with customers, print or send the Credit Control Summary report from the run.
- The system will automatically merge the selected invoice report (as configured) into the credit control summary PDF for each customer, so recipients receive both the summary and detailed invoices in one document.
- Download, print, or send the combined report as needed.
No verified information in OCA: Installation.
Installation 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.