PEPPOL-EN16931-P0112Type code 326, 384 or 389 outside Germany
Also in:NederlandsFrançaisDeutsch
What it means
Peppol only allows three invoice type codes between specific parties: 326 (partial invoice) and 389 (self-billed invoice) when seller and buyer are both German, and 384 (corrected invoice) when both are German or both are Slovak. Everyone else sends a normal invoice (380) and corrects mistakes with a credit note.
Official message
Rejects the invoice (fatal)[PEPPOL-EN16931-P0112]-Invoice type codes 326 and 389 are only allowed when both buyer and seller are German organizations. Invoice type code 384 is only allowed when both buyer and seller are German organizations or both are Slovak organizations.Peppol BIS Billing 3.0 3.0.22, OpenPeppol, released 4 November 2026 · Read the rule at the source
Text compared with the published file on 17 November 2026.
Direct fix
Use <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>. To correct an invoice outside Germany, send a credit note (381) that refers to it in cac:BillingReference, then a new invoice with 380.
Typical causes
- The software codes a re-issued invoice as 384 “corrected invoice” after a mistake was found.
- Self-billing between Belgian or Dutch companies is exported with type code 389.
- Instalment and partial invoices get 326 by default, as German software does.
How to fix it
- Use 380 for the invoice, also for a partial or instalment invoice.
- To correct an invoice, send a credit note (381) that cancels it and a new invoice (380).
- For self-billing outside Germany, ask your Peppol provider how it is supported; 389 is refused.
Before and after
A real invoice from our sample library, cut down to the lines that matter. The first version fails PEPPOL-EN16931-P0112; the second passes.
The broken invoice is coded 384 (corrected invoice) between two Belgian companies.
<cbc:InvoiceTypeCode>384</cbc:InvoiceTypeCode><cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>It’s one of our sample files, so checking it doesn’t count towards your free validations.
Check your invoice for PEPPOL-EN16931-P0112
Open the free validator with PEPPOL-EN16931-P0112 already explained: paste or upload your XML and the finding, if any, is highlighted with its exact line.
Check my invoice3 free validations a month without an account. Invoice contents are never stored.
Where validators check it
For developers and software suppliers: the test exactly as the official Schematron runs it. The validator applies it to every element that matches the context and reports the rule wherever the test comes out false.
- Runs on (context)
cbc:InvoiceTypeCode- Test
not(normalize-space(.) = '326' or normalize-space(.) = '384' or normalize-space(.) = '389') or ($supplierCountryIsDE and $customerCountryIsDE) or (normalize-space(.) = '384' and $supplierCountry = 'SK' and $customerCountry = 'SK')- Values it uses
$supplierCountryIsDE = (upper-case(normalize-space(/*/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode)) = 'DE')$customerCountryIsDE = (upper-case(normalize-space(/*/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode)) = 'DE')$supplierCountry = if (/*/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2)) then upper-case(normalize-space(/*/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2))) else if (/*/cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2)) then upper-case(normalize-space(/*/cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2))) else if (/*/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode) then upper-case(normalize-space(/*/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode)) else 'XX'$customerCountry = if (/*/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2)) then upper-case(normalize-space(/*/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID = 'VAT']/substring(cbc:CompanyID, 1, 2))) else if (/*/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode) then upper-case(normalize-space(/*/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCode)) else 'XX'
Copied from PEPPOL-EN16931-UBL.sch, Peppol BIS Billing 3.0 3.0.22. Text compared with the published file on 17 November 2026.
What the rule says (technical)
Invoice type codes 326 and 389 are only allowed when both buyer and seller are German organizations. Invoice type code 384 is only allowed when both buyer and seller are German organizations or both are Slovak organizations.
Use 380 for an invoice; correct a wrong invoice with a credit note (381) and a new invoice instead of 384, unless both parties are German (or Slovak for 384).
More errors with a worked fix
Related rules
- BR-04Invoice type is missingSame field: BT-3
- BR-DE-17Document type is unusual for XRechnungSame field: BT-3
- BR-CL-01Choose a recognised document typeSame field: BT-3
- PEPPOL-EN16931-P0100Invoice type is not allowed in PeppolSame field: BT-3
- PEPPOL-EN16931-P0101Credit note type is not allowed in PeppolSame field: BT-3
- BR-NL-7Invoice type code isn't allowed in SI-UBL 2.0Same field: BT-3
- BR-NL-8Credit note sent as an invoice (or the other way round)Same field: BT-3
- BR-NL-9Corrected invoice doesn't say which invoice it correctsSame field: BT-3