Odoo Changelog — 2026-06-26

Friday, June 26, 2026

2 changes · 18.0

Improvements(2)

Enhancements to existing features

[IMP] l10n_at: New 4.9% tax

Core18.0l10n_atl10n_eu_ossMedium

This update prepares the Austrian localization for a VAT change effective July 1, 2026, reducing the rate from 10% to 4.9% for certain food categories. It also adjusts the related chart of accounts and tax return mapping so accounting and reporting stay correct.

Original PR description

From first of July 2026, the VAT will change from 10% to 4.9% for some food categories. 
Adapt the taxes, the CoA and the tax return accordingly.

task-6273259


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

Forward-Port-Of: odoo/odoo#268278

#VAT#Austria#localization#tax#accounting#reporting

[IMP] l10n_pl_edi: Fetch bills even if there is an error

PR #270511

Core18.0l10n_pl_ediaccountMedium

This change makes KSeF bill retrieval more resilient when one bill causes an error, so the whole import process does not get blocked. It also helps users keep track of bills that need manual follow-up and improves handling of edge cases between companies and date limits.

Original PR description

### Commit 1: We fetch and store bills if we're able to parse and store them correctly. but in case we make a mistake 1. The cron gets stuck trying to fetch the problematic bill. 2. Users have no…

### Commit 1:

We fetch and store bills if we're able to parse and store them correctly. but in case we make a mistake

1. The cron gets stuck trying to fetch the problematic bill.
2. Users have no clue that there is a bill on KSeF that they have to fetch manually.

---

1. Save the bill on a savepoint, to make sure one problematic bill doesn't affect others
2. Create all bills as draft first so that users have a reference to fallback to in case the have to do manual fetching.

---

task-6310321

---

### Commit 2:

Issues:

1. For a db with company_1 and company_2, when company_1 sends an invoice to company_2 via KSeF (out_invoice with a ksef number),
company_2 in the same database can't fetch the corresponding bill because there is a move with the same KSeF number.
2. The date difference between `from` and `to` in the `dateRange` must not exceed 3 months as explained in the documentation
https://api.ksef.mf.gov.pl/docs/v2/index.html#tag/Pobieranie-faktur/paths/~1invoices~1query~1metadata/post

Fixes:

1. Change the unique constraint and the domain to allow same KSeF number per different companies.
2. Minimize the `to` parameter with `from` + 2 months.
3. Increase the TIMEOUT to 30 seconds as 10 seconds is too small.

task-6260645

---

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

From first of July 2026, the VAT will change from 10% to 4.9% for some food categories. Adapt the taxes, the CoA and the tax return accordingly. task-6273259 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#268278

### Commit 1: We fetch and store bills if we're able to parse and store them correctly. but in case we make a mistake 1. The cron gets stuck trying to fetch the problematic bill. 2. Users have no clue that there is a bill on KSeF that they have to fetch manually. --- 1. Save the bill on a savepoint, to make sure one problematic bill doesn't affect others 2. Create all bills as draft first so that users have a reference to fallback to in case the have to do manual fetching. --- task-6310321 --- ### Commit 2: Issues: 1. For a db with company_1 and company_2, when company_1 sends an invoice to company_2 via KSeF (out_invoice with a ksef number), company_2 in the same database can't fetch the corresponding bill because there is a move with the same KSeF number. 2. The date difference between `from` and `to` in the `dateRange` must not exceed 3 months as explained in the documentation https://api.ksef.mf.gov.pl/docs/v2/index.html#tag/Pobieranie-faktur/paths/~1invoices~1query~1metadata/post Fixes: 1. Change the unique constraint and the domain to allow same KSeF number per different companies. 2. Minimize the `to` parameter with `from` + 2 months. 3. Increase the TIMEOUT to 30 seconds as 10 seconds is too small. task-6260645 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr