Invoice type not permitted in the Peppol network
The invoice type code (BT-3) is not permitted for invoices in the Peppol network.
What to do now
Who has to fix this?
The issuer of the invoice has to fix this. If the invoice is sent through a Peppol access point, the access point will otherwise reject it before delivery.
Where this rule comes from
This rule comes from the Peppol rule set BIS Billing 3.0, which goes beyond EN 16931. It is checked as soon as an invoice is sent as Peppol BIS Billing 3.0 through the Peppol network.
- Rule ID
- PEPPOL-EN16931-P0100
- Rule set
- Peppol BIS Billing 3.0
- Checked for
- Peppol BIS and profiles based on it
- Consequence of a violation
- The invoice is considered non-compliant with the standard and is automatically rejected by many recipients.
Does PEPPOL-EN16931-P0100 occur in your invoice?
Upload the XRechnung or the ZUGFeRD/Factur-X PDF – the validator shows every violation with the same explanation as here. Free, no login, nothing stored.
Validate your invoice nowGeneral information, not tax or legal advice. As of October 2026. Validation rules: CEN/TC 434 (EN 16931, EUPL 1.2), KoSIT (XRechnung, Apache 2.0), FNFE-MPE/FeRD (Factur-X/ZUGFeRD, Apache 2.0), OpenPeppol AISBL (Peppol BIS), ANAF (CIUS-RO). Explanations: Billvox. Licence notices