PEPPOL-EN16931-P0100 — E-Invoice Validation Rule & Fix

Fixture ID: peppolBadTypeCode · XPath: /ubl:Invoice/cbc:InvoiceTypeCode

1. Why This Rule Triggers (Diagnostic Message)

The invoice type code (BT-3) is "325", which billing process 01 does not admit. Peppol's rules are scoped by business process — the ProfileID this library emits is urn:fdc:peppol.eu:2017:poacc:billing:01:1.0, "billing", and each process declares which UNTDID 1001 codes make sense inside it. The permitted set here is 71, 80, 82, 84, 102, 218, 219, 326, 331, 380, 382, 383, 384, 386, 388, 393, 395, 553, 575, 623, 780, 817, 870, 875, 876 and 877. Note that this is a *different* narrowing from BR-CL-01, which admits a wider list, and from XRechnung's BR-DE-17, which admits a narrower one — three lists, three ids, and passing one says nothing about the others. This is a Peppol BIS Billing 3.0 profile rule: it applies because profile is "peppol-bis-3". It does not apply to the en16931, xrechnung-ubl or xrechnung-cii profiles, whose validators will accept the same document.

2. How to Fix PEPPOL-EN16931-P0100

Use "380" for a commercial invoice, "384" for a corrected invoice, "386" for a prepayment invoice, "875"/"876"/"877" for the construction-industry partial invoices. A credit note is a separate document in UBL and is governed by PEPPOL-EN16931-P0101, not this rule.

3. Valid Code / Payload Example

"invoiceTypeCode": "380"