PEPPOL-EN16931-R080

fatalPeppol BIS Billing 3.0profileCIIUBL

Only one project reference is allowed on document level

Why it fails

More than one project reference (BT-11) at document level.

How to fix it

Keep one project reference.

What the validator checks

CII — context ram:ApplicableHeaderTradeAgreement

count(ram:AdditionalReferencedDocument[ram:TypeCode='50']) <=1

UBL — context ubl-creditnote:CreditNote

(count(cac:AdditionalDocumentReference[cbc:DocumentTypeCode='50']) <= 1)

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-R004
• PEPPOL-EN16931-R005
• PEPPOL-EN16931-R006

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.