We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is standard format expected by Odoo base_vat. See https://github.com/odoo/odoo/blob/12.0/addons/base_vat/models/res_partner.py#L39
base_vat
RUT validation is out of the box from Odoo, and does not need to be in l10n_cl_toponym.
l10n_cl_toponym
For better UX, a l10n_cl_rut computed field could be added, to display the RUT in a 12.345.678-9 format.
l10n_cl_rut
12.345.678-9
This has impact in electronic documents communication, and I have particular concerns related to the Xerox integration.
The text was updated successfully, but these errors were encountered:
Ping @max3903 @nelsonramirezs @rto-odoo
Sorry, something went wrong.
No branches or pull requests
This is standard format expected by Odoo
base_vat
. See https://github.com/odoo/odoo/blob/12.0/addons/base_vat/models/res_partner.py#L39RUT validation is out of the box from Odoo, and does not need to be in
l10n_cl_toponym
.For better UX, a
l10n_cl_rut
computed field could be added, to display the RUT in a12.345.678-9
format.This has impact in electronic documents communication, and I have particular concerns related to the Xerox integration.
The text was updated successfully, but these errors were encountered: