PEPPOL-EN16931-R004

fatalPeppol BIS Billing 3.0profileCIIUBL

Specification identifier MUST have the value 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.

Why it fails

The specification identifier (BT-24) is not the Peppol BIS Billing 3.0 customisation ID, so the receiver will not apply the Peppol rules.

How to fix it

Set BT-24 to exactly urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0 (the plain urn:cen.eu:en16931:2017 is not enough for Peppol).

What the validator checks

CII — context rsm:ExchangedDocumentContext

starts-with(normalize-space(ram:GuidelineSpecifiedDocumentContextParameter/ram:ID/text()), 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0')

UBL — context ubl-creditnote:CreditNote | ubl-invoice:Invoice

starts-with(normalize-space(cbc:CustomizationID/text()), 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0')

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-R001
• PEPPOL-EN16931-R002
• PEPPOL-EN16931-R003
• 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.