Saturday, October 4, 2025
1 change · saas-18.4
Resolved issues and error corrections
Dutch electronic invoices now include only the Peppol endpoint as the customer identifier, avoiding a duplicate identifier when a customer reference is also set. This prevents NLCIUS validation errors so affected invoices can be sent successfully.
Original PR description
**Steps to reproduce:** - Install Accounting and Contacts - Use a company based in Netherlands - In Contacts, configure the company: * eInvoice format: Netherlands (NLCIUS) * Peppol endpoint:…
**Steps to reproduce:**
- Install Accounting and Contacts
- Use a company based in Netherlands
- In Contacts, configure the company:
* eInvoice format: Netherlands (NLCIUS)
* Peppol endpoint: [anything]
* Reference ("Sales & Purchase" tab): [anything]
- Create a Dutch contact with a peppol endpoint and a reference
- Create an invoice for the Dutch contact
- Confirm the invoice
- Send the invoice
- Check the generated NLCIUS xml
**Issue:**
In the XML there are 2 "<cac:PartyIdentification>" for each party.
One with the peppol endpoint and one with the partner reference.
For "<cac:AccountingCustomerParty>", only one Party Identification is allowed, triggering the following validation error:
[UBL-SR-16] Buyer identifier shall occur maximum once
**Cause:**
By default (UBL 2.0), the partner reference is used as Party Identification.
But in the case of a Dutch partner, the peppol endpoint is also added in BIS3.
**Solution:**
Only use the peppol endpoint for Dutch partners.
opw-5059667
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#226561