Colombia - Verification Digit
This module extends the Colombian localization to compute the verification digit (dígito de verificación) of the NIT, as defined in Orden Administrativa 4 of 1989 by the DIAN.
It adds a computed field on the partner form that automatically calculates the check digit from the NIT and displays it next to the identification number with a hyphen separator when the identification type is NIT.
Table of contents
Use Cases / Context
Business Need
In Colombia, every NIT (Número de Identificación Tributaria) issued by the DIAN includes a verification digit (dígito de verificación) computed using a weighted sum algorithm defined in Orden Administrativa 4 of 1989. This digit is required on invoices, tax filings, and legal documents. Odoo does not compute or display this digit natively.
Approach
This module adds a compute_verification_digit function that implements the DIAN algorithm and extends res.partner with a computed field l10n_co_verification_digit that displays the check digit next to the identification number on the partner form, separated by a hyphen (e.g., 900123456 - 8). The verification digit is only shown when the identification type is NIT.
Useful Information
Depends on: l10n_latam_base, l10n_co (Colombian localization)
Works well with: l10n_co_electronic_invoice and any module that displays partner tax identification
Suggested setup: recommended for any Colombian Odoo instance that needs to display or validate the NIT verification digit on partner records and printed documents
Usage
To use this module, you need to:
Go to Contacts > select a partner
Set the country to Colombia
Select NIT as the identification type
Enter the NIT in the identification number field (base number without the verification digit)
The verification digit is computed automatically and displayed next to the number with a hyphen (e.g., 900123456 - 8)
Changelog
18.0.1.0.0 (2026-07-12)
[ADD] Initial release. Compute Colombian NIT verification digit using the DIAN algorithm (Orden Administrativa 4 of 1989). Display the digit next to the identification number on partner form when the identification type is NIT.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Juan Arcos juanparmer@gmail.com
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/l10n-colombia project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-l10n-co-verification-digit 18.0.1.0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_l10n_co_verification_digit-18.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_l10n_co_verification_digit-18.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_l10n_co_verification_digit-18.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_l10n_co_verification_digit-18.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a3a59839d83e636be80eb85c33320f3791bc0955a908dfae0a14b237e405a64
|
|
BLAKE2b-256 checksum How to use checksums |
a17c4769167461b0c8587a241d6986b26d191d04391d1586756cf00ace081afc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-l10n-co-verification-digit 18.0.1.0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
