Odoo Changelog — 2025-09-30

Tuesday, September 30, 2025

2 changes · 18.0

New Features(2)

New functionality added to Odoo

[ADD] l10n_tr_nilvera_einvoice_extended: Adding nilvera einvoice exte…

Core18.0l10n_tr_nilvera_einvoicel10n_tr_nilvera_einvoice_extendedHIGH

Adds support for key Turkish e-invoice scenarios including withholding VAT, tax-exempt invoices, export invoices, and public sector invoices. This helps Turkish businesses meet local legal requirements and improves the invoice data sent through Nilvera, including required tax office details.

Original PR description

[ADD] l10n_tr_nilvera_einvoice_extended: Adding Nilvera E-Invoice Extension  
[ADD] l10n_tr_nilvera_einvoice_extended: Adding Tax Offices

---

### Description of the issue/feature this PR addresses:

We do not support Withholding VAT (KDV Tevkifatı), Exemption Invoices, and Export Invoices (İhracat Faturaları) with our current e-invoicing solution in Türkiye. Those invoice types are legally important and required for both domestic and international sales for businesses. In addition, the inclusion of the Tax office in our current XML we send to Nilvera, both for `<cac:AccountingSupplierParty>` and `<cac:AccountingCustomerParty>`, is required by law.

This PR adds an extension module for Nilvera E-Invoicing. The purpose of this module is to extend the existing E-Invoicing functionality to support additional invoice types and scenarios to be compliant with the TR legal requirements.

---

### Invoice Scenario:

**Basic**  
Invoice Type:
- Sales  
- Withholding  
- Tax Exempt  
- Registered for Export  

**Export**  
Invoice Type:
- Tax Exempt  

**Public**  
Invoice Type:
- Sales  
- Withholding  
- Tax Exempt  
- Registered for Export  

---

### Current behavior before PR:

We don't support a scenario-based system to comply with TR legal requirements.

---

### Desired behavior after PR is merged:

We support a scenario-based system to comply with TR legal requirements.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#Turkey#e-invoicing#Nilvera#compliance

[ADD] l10n_bn: add district names and codes

PR #228664

Core18.0baseMEDIUM

This update adds standard Brunei district names and codes so customer and partner addresses can use consistent location data. It also aligns Brunei address and currency formatting with official postal guidance, reducing manual setup and improving local accuracy.

Original PR description

Added district names and codes based on government postal website, https://www.post.gov.bn/Documents/Buku%20Poskod%20Edisi%20ke%202%20(Kemaskini%2026122018).pdf

Description of the issue/feature this PR addresses:
Currently, the Brunei localisation does not include district names and codes, which requires users or system integrator to enter the district names manually before starting to use the system.

Current behavior before PR:
Partner addresses in Brunei cannot be assigned to a standardised district.
District codes are missing from the localisation data.

Desired behavior after PR is merged:
Brunei district names and their respective codes are available in the localisation module.



---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#localization#brunei#addresses#districts#currency

[ADD] l10n_tr_nilvera_einvoice_extended: Adding Nilvera E-Invoice Extension [ADD] l10n_tr_nilvera_einvoice_extended: Adding Tax Offices --- ### Description of the issue/feature this PR addresses: We do not support Withholding VAT (KDV Tevkifatı), Exemption Invoices, and Export Invoices (İhracat Faturaları) with our current e-invoicing solution in Türkiye. Those invoice types are legally important and required for both domestic and international sales for businesses. In addition, the inclusion of the Tax office in our current XML we send to Nilvera, both for `<cac:AccountingSupplierParty>` and `<cac:AccountingCustomerParty>`, is required by law. This PR adds an extension module for Nilvera E-Invoicing. The purpose of this module is to extend the existing E-Invoicing functionality to support additional invoice types and scenarios to be compliant with the TR legal requirements. --- ### Invoice Scenario: **Basic** Invoice Type: - Sales - Withholding - Tax Exempt - Registered for Export **Export** Invoice Type: - Tax Exempt **Public** Invoice Type: - Sales - Withholding - Tax Exempt - Registered for Export --- ### Current behavior before PR: We don't support a scenario-based system to comply with TR legal requirements. --- ### Desired behavior after PR is merged: We support a scenario-based system to comply with TR legal requirements. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Added district names and codes based on government postal website, https://www.post.gov.bn/Documents/Buku%20Poskod%20Edisi%20ke%202%20(Kemaskini%2026122018).pdf Description of the issue/feature this PR addresses: Currently, the Brunei localisation does not include district names and codes, which requires users or system integrator to enter the district names manually before starting to use the system. Current behavior before PR: Partner addresses in Brunei cannot be assigned to a standardised district. District codes are missing from the localisation data. Desired behavior after PR is merged: Brunei district names and their respective codes are available in the localisation module. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr