| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2910 |
| Technical Name |
l10n_kh_caminvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2910 |
| Technical Name |
l10n_kh_caminvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Cambodia CamInvoice
GDT CamInvoice UBL 2.1 e-invoicing for Odoo — clearance UUID & verification QR on every customer invoice
Connect Odoo to the Cambodia General Department of Taxation (GDT) CamInvoice clearance system. Customer invoices and credit notes are transformed into an OASIS UBL 2.1 document, submitted with your own credentials, and the returned document UUID, verification code and QR code are stored on the move — ready for the 2026–27 large-taxpayer B2B mandate.
UBL 2.1 generation
Standard 10% VAT, zero-rated export, exempt and out-of-scope tax categories (UNCL5305 S/Z/E/O), per-line items, allowances and credit-note referencing. Optional bilingual Khmer/English trade names are emitted on the document.
GDT clearance + QR
OAuth client-credentials or access-token authentication, document submission, status polling and download over the CamInvoice REST API. The clearance UUID and verification code are captured and a verification QR is rendered to a PNG for the printed invoice.
Real GDT VAT-TIN validation
Structural validator accepting both the bare serial and the
L001-902020845 certificate display form, with
enterprise-class (Large / Medium / Small / Estimated) detection and an
advisory Luhn check during onboarding.
CamInvoice business rules
A Cambodia rule set layered on the engine's EN 16931-style core: seller / buyer TIN, valid tax categories, KHR / USD currency and credit-note referencing — validated before submission with a clear, itemised report.
Bring-your-own-key (BYOK)
Your CamInvoice client id / secret (or access token) and TIN are stored only on your own database and are transmitted solely to the GDT CamInvoice endpoint you configure. Sandbox and production endpoints are editable; requests retry with exponential backoff and every call is logged for audit and support.
Built on the e-Invoice Core Engine
This connector reuses the shared e-Invoice Core Engine for the UBL 2.1 builder, validation framework, BYOK REST transport and the e-Invoicing document model. An onboarding wizard, a connection model, an optional batch-submission scheduled action and full transport logging are included. Compatible with Odoo 18 and Odoo 19.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module