How do I fix UBL-SR-12?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (UBL-SR-12). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is UBL-SR-12 a critical error?

Yes, UBL-SR-12 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can UBL-SR-12 be automatically fixed?

Many instances of UBL-SR-12 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorEN 16931

`UBL-SR-12`:Seller VAT identifier shall occur maximum once

Your invoice contains multiple Seller VAT identifiers (PartyTaxScheme with VAT scheme). EN16931 allows only one VAT identifier per seller.

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Remove duplicate seller VAT identifiers, keeping the first occurrence

Confidence: 90% · Applied automatically in pipeline

What is UBL-SR-12?

UBL-SR-12 is a fatal validation rule defined in the EN 16931 specification. It validates the CompanyID element under PartyTaxScheme[cac:TaxScheme > ID='VAT'] in the UBL invoice XML.

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.

UBL-SR-12 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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
·Error returned: UBL-SR-12
·Specification: EN 16931

Before / After

Failing XML

<Invoice>
  <!-- Issue: Seller VAT identifier shall occur maximum once. -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPath/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID

SpecEN 16931

Operationremove_duplicates

StrategyRemove duplicate seller VAT identifiers, keeping the first occurrence

Common Causes

·ERP system exports multiple references where only one is allowed in EN16931
·Data consolidation merged records that should have been deduplicated
·Template or mapping incorrectly configured to output duplicate elements
·Manual editing introduced extra elements
·Invoice conversion from another format did not merge duplicate entries

Seeing this in production? The API handles UBL-SR-12 automatically. See the fix response →

Handle UBL-SR-12 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

UBL-SR-12:Seller VAT identifier shall occur maximum once