UBL-SR-43:Scheme identifier shall only be used for invoiced object (document type code with value 130 or 50)
Fix: Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). S Upload your invoice to fix this automatically.
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). Scheme identifiers are only valid for these document types.
Engine Classification
Remove schemeID attribute from AdditionalDocumentReference/ID when DocumentTypeCode is not 130 or 50
Confidence: 85% · Applied automatically in pipeline
What is UBL-SR-43?
UBL-SR-43 is a fatal validation rule defined in the EN16931 specification. It validates the @schemeID element under ID in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: //cac:AdditionalDocumentReference/cbc:ID/@schemeID
Why This Error Matters
Invoice will be rejected. The schemeID attribute on document references is only meaningful for invoiced objects and catalogue references.
UBL-SR-43 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Fails EN 16931 business rule validation
- ·Error returned: UBL-SR-43
- ·Specification: EN16931
How to Fix It
Find the disallowed attribute
Check @schemeID at //cac:AdditionalDocumentReference/cbc:ID/@schemeID. This attribute is not permitted in the target profile.
Remove the attribute
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). S
Re-validate your invoice
Upload the corrected invoice to confirm UBL-SR-43 is resolved.
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <@schemeID></@schemeID>
<!-- Corrected --> <@schemeID>VALID_VALUE</@schemeID>
Technical Reference
//cac:AdditionalDocumentReference/cbc:ID/@schemeIDCommon Causes
- ·Generic document reference template adds schemeID to all references
- ·ERP export includes schemeID attribute on all document references
- ·Copy-paste from invoiced object reference to other reference types
- ·XML generation library adds schemeID by default
- ·Conversion from other format incorrectly mapped schemeID
Seeing this in production? The API handles UBL-SR-43 automatically. See the fix response →
Frequently Asked Questions
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). Scheme identifiers are only valid for these document types.
Your invoice uses a scheme identifier (schemeID attribute) on AdditionalDocumentReference/ID but the DocumentTypeCode is not 130 (invoiced object identifier) or 50 (price/sales catalogue reference). S You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-SR-43 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-SR-43 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for UBL-SR-43
Auto-fix UBL-SR-43 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.