PEPPOL-EN16931-R001

fatalPeppol BIS Billing 3.0profileCIIUBL

Business process MUST be provided.

Why it fails

The business process identifier (BT-23) is missing. Peppol routes on it, so an invoice without it cannot be delivered even though it is valid EN 16931.

How to fix it

Add BT-23 (UBL cbc:ProfileID) with the value urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 for a normal invoice-only process. This is the field most often missing when a working EN 16931 file first meets Peppol.

What the validator checks

CII — context —

ram:BusinessProcessSpecifiedDocumentContextParameter/ram:ID

UBL — context —

cbc:ProfileID

Related rules

Part of PEPPOL-EN16931 — Peppol BIS Billing 3.0.

• PEPPOL-EN16931-CL001
• PEPPOL-EN16931-CL002
• PEPPOL-EN16931-CL003
• PEPPOL-EN16931-CL006
• PEPPOL-EN16931-CL007
• PEPPOL-EN16931-CL008
• PEPPOL-EN16931-F001
• PEPPOL-EN16931-P0100
• PEPPOL-EN16931-P0101
• PEPPOL-EN16931-P0104
• PEPPOL-EN16931-P0105
• PEPPOL-EN16931-P0106
• PEPPOL-EN16931-P0107
• PEPPOL-EN16931-P0108
• PEPPOL-EN16931-P0109
• PEPPOL-EN16931-P0110
• PEPPOL-EN16931-P0111
• PEPPOL-EN16931-P0112
• PEPPOL-EN16931-R002
• PEPPOL-EN16931-R003
• PEPPOL-EN16931-R004
• PEPPOL-EN16931-R005
• PEPPOL-EN16931-R006
• PEPPOL-EN16931-R007

Validate an invoice against this rule →

This is a Peppol BIS Billing 3.0 rule: an invoice can be perfectly valid EN 16931 and still be rejected by it.