| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3762 |
| Technical Name |
l10n_kh_caminvoice_credit_note |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
Cambodia CamInvoice Credit Notes
GDT CamInvoice UBL 2.1 CreditNote flows for Odoo — UNCL5189 reason codes, original-document UUID referencing & multi-invoice credit allocation
Extends the Cambodia CamInvoice connector with everything a GDT
credit note (UBL CreditNote, document type 381)
requires beyond a plain invoice. A credit note adjusts a previously
cleared invoice — a return, a post-sale discount, a price or
quantity correction, or a cancellation — and the General Department
of Taxation reconciles the output-VAT reversal against the original
cleared document.
Odoo 18 Odoo 19 UBL 2.1 UNCL5189 BYOK
UNCL5189 reason codes
A curated CamInvoice credit-note reason catalogue — return of goods, defective goods, post-sale discount, price / quantity / tax corrections, duplicate and order cancellation — each classified by its VAT effect and emitted as a UBL DiscrepancyResponse (ResponseCode + Description) on the credit note.
Original-document referencing
The credit note carries the original invoice number, issue date and, where the original was already cleared, its GDT clearance UUID. Return and cancellation reasons require the UUID; a back-fill job completes it once the original clears.
Multi-invoice credit allocation
A return frequently spans several cleared invoices. A deterministic largest-remaining-first allocation engine splits the credit into one single-original credit note per referenced invoice, never over-crediting any original's remaining balance, with an exact two-decimal residual sweep so the parts sum precisely to the requested credit.
Credit-note validation
A kh_caminvoice_cn rule set layered on the base Cambodia
rules: document type, valid reason code, original reference and UUID, and
an over-crediting guard — run before submission so the GDT does not
reject the document.
Built on the e-Invoice Core Engine
Built on the base l10n_kh_caminvoice connector and the shared e-Invoice Core Engine (UBL 2.1 builder, validation framework, BYOK REST transport). No engine or base functionality is duplicated — this module adds the reason catalogue, the enriched UBL credit-note generator, the credit-note validation profile and the credit-allocation engine. Clearance reuses the base connector's bring-your-own-key transport: your CamInvoice credentials and TIN are stored only on your own database and are transmitted solely to the CamInvoice endpoint you configure.
Feature summary
- UNCL5189 adjustment reason codes with VAT-effect classification.
- UBL 2.1 CreditNote generation with DiscrepancyResponse and BillingReference (number, date, original cleared UUID).
- Positive credit magnitudes and S/Z/E/O tax-category bucketing.
- Largest-remaining-first multi-invoice credit allocation wizard.
kh_caminvoice_cnbusiness-rule validation profile.- Original-UUID back-fill scheduled action.
- BYOK clearance via the base connector — Odoo 18 & 19.
Disclosure: this is a bring-your-own-key (BYOK) module. We are not an e-invoicing integrator, operator or clearance agent — the clearance relationship is strictly between you and the General Department of Taxation (GDT). Credit notes are transmitted only to the CamInvoice endpoint configured on the base connector, authenticated with your own credentials; no data is sent anywhere else. Product support is provided and the purchase is refundable per the marketplace policy.
Screenshots
Caminvoice Credit Note Retur
Generated Caminvoice Credit
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3762 |
| Technical Name |
l10n_kh_caminvoice_credit_note |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
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