PEPPOL-EN16931-R006

fatalPeppol BIS Billing 3.0profileCII

Only one invoiced object is allowed on document level

Why it fails

More than one invoiced object reference (BT-18) at document level.

How to fix it

Keep one, or move the extra references onto the relevant invoice lines (BT-128).

What the validator checks

CII — context ram:ApplicableHeaderTradeAgreement

count(ram:AdditionalReferencedDocument[ram:TypeCode='130']) <=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-R007

Check your own invoice against PEPPOL-EN16931-R006

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