This module was written to extend the functionality of CRM leads to support setting the VAT identification number ().
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds a TIN/VAT field to CRM leads and opportunities, and keeps it in sync with the linked customer's VAT number.
This module adds a Tax Identification Number (TIN/VAT) field directly on CRM leads and opportunities, right next to the customer field on the lead form.
- The VAT shown on the lead is automatically filled from the linked customer (or its commercial parent company) when one is set.
- If you type or change the VAT on the lead, Odoo shows a small warning icon meaning that saving will also update the VAT on the customer record.
- When a lead is converted into a customer, the VAT entered on the lead is carried over to the new customer record.
- When a customer is linked to a lead, its existing VAT is copied back onto the lead.
The module works on the crm.lead model and only touches the CRM lead form view. No new menus, reports or scheduled actions are added. The VAT field is stored, so it remains available for filtering and reporting like other lead fields.
Depends on
Models and fields (1)
- crm.lead · extends an existing modelvat (TIN), partner_vat_update (Partner VAT will Update)
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/crm.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0To use this module, you need to:
- Go to CRM \> Leads.
- Open a lead.
- You will see the new field.
- If you change vat in partner, it change in lead.
- If you change vat in lead, a warning will show informing you that if you save, vat change in partner.
No verified information in OCA: Installation, Configuration.
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.