What it means
The check looks at every cac:AdditionalDocumentReference. A reference passes when its cbc:DocumentTypeCode is 130, or when it has neither cbc:DocumentTypeCode nor cbc:ID/@schemeID (cbc:ID/@scheme in UBL.BE and Italian Peppol), as for a supporting document reference (BT-122). The check also allows code 50 in a credit note. For the invoiced object identifier (BT-18), schemeID holds the scheme identifier (BT-18-1).
Why it matters
The rule reserves identifier schemes and document type codes for invoiced object references, rather than ordinary supporting document references.
How to fix it
In your invoicing software, check the document references and attachments you have added. Keep a scheme only on the invoiced object identifier, with type code 130, or type code 50 if the document is a credit note. For other supporting documents, leave the scheme and type code out. If you build the XML yourself, remove schemeID (scheme in UBL.BE and Italian Peppol) from cbc:ID and delete cbc:DocumentTypeCode in the cac:AdditionalDocumentReference elements for those supporting documents.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
Scheme identifier shall only be used for invoiced object (document type code with value 130 or 50) Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether UBL-SR-43 still fails, and which other rules do.
Related rules
- UBL-SR-44 An invoice can have only one payment reference
- UBL-SR-45 Only one due date in the payment means
- UBL-SR-46 The payment means text can only be given once
- UBL-SR-47 All payment means codes on an invoice must be the same
- UBL-SR-48 Every line must have exactly one VAT category
- UBL-SR-49 The VAT point date code can only be given once