[19.0][MIG] l10n_fr_siret

[alexis-via]

Implementation proposal following #711 that adopt the new native datamodel : SIRET is now stored on the field "company_registry" of res.partner.

[legalsylvain]

Thanks for the ping Alexis. I'm asking if we can define siret / siren and nic fields, computed readonly, and stored, with exactly the same function as you wrote.

Pro :

• possibility to make SQL, request, etc.
• lesss useless computation. (those fields are very stable, so no need to recompute at each use).
• possibility to display it in views.

Cons :

Don't see, but maybe !

[legalsylvain]

Are you sure about this test ?
I'm asking if some people design "holding" with parent in odoo. if yes, company_registry could be totally different between childs... not sure thought.

[alexis-via]

In my interpretation of how partners should be organised in Odoo for companies, I consider that 1 parent partner = 1 legal entity (1 personne morale) i.e. a SIREN for a french company (or a VAT number). I think it's a mistake to use the parent / child relationship to consider a holding company which owns other companies created as children companies ; because, in the accounting, only parent companies are considered on journal items, so you end up in accounting to consider that the debt is only on the holding company although some invoices were for some children companies.
But I'm not sure what is the exact vision of Odoo SA on parent/child relations for companies.
This is particulaly important for the e-invoicing reform : when we used to send invoices by email or by post, the most important parameter was the destination email (or postal) address to which the invoice was sent ; but, with the e-invoicing reform, the most important parameter in SIREN or VAT number.