This localization module provides functions that facilitate working with UBL documents with the specific dialect that is used in Netherlands (NLCIUS). For more info on the NLCIUS standard see:
https://www.forumstandaardisatie.nl/open-standaarden/nlcius
Partner identification
According to NLCIUS, a Dutch commercial partner can be identified with:
- Kamer van Koophandel (KvK).
- Organisatie-identificatienummer (OIN).
In case OCA module partner_coc is installed, this module will handle the proper value of KvK. Otherwise if the field KvK is defined in another module, you should extend method _l10n_nl_base_ubl_get_kvk returning your custom KvK field.
In case OCA module l10n_nl_oin is installed, this module will handle the proper value of OIN. Otherwise if the field OIN is defined in another module, you should extend method _l10n_nl_base_ubl_get_oin returning your custom OIN field.
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Adds Dutch identification numbers (KvK and OIN) to UBL electronic documents generated in Odoo, so Dutch partners are correctly identified in the NLCIUS dialect.
This is a technical base module for the Dutch UBL dialect (NLCIUS). It does not add any menu, screen or button of its own; instead it changes how electronic UBL documents are built when they are generated from Odoo.
What it does: - When a UBL document is created, the partner's Dutch identification is looked up and inserted into the document's legal entity section. - If the partner has an OIN (Organisatie-identificatienummer), it is written with scheme code 0190. - Otherwise, if the partner has a KvK (Kamer van Koophandel) number, it is written with scheme code 0106. - The OIN takes priority over the KvK when both are present.
Where the values come from:
- The KvK is read from the field coc_registration_number if that field exists on the partner (for example when the partner_coc module is installed).
- The OIN is read from the field nl_oin if that field exists (for example when the l10n_nl_oin module is installed).
- If neither field exists, no Dutch identification is added, and developers can extend the lookup methods to use their own fields.
It touches the abstract UBL model base.ubl and the partner data used when generating UBL files. No scheduled jobs, emails or user-facing screens are added.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 13.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 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/l10n-netherlands.
terminal Installation and usage
No verified informationInstallation 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.