PEPPOL-EN16931-R020 in your own invoice? Upload the file and find every error in seconds.
What does PEPPOL-EN16931-R020 mean?
As with the buyer address (BT-49), Peppol also requires an electronic address for the seller (BT-34). It identifies the sender on the network unambiguously.
Common causes of PEPPOL-EN16931-R020
- The element URIUniversalCommunication/ram:URIID on the seller is missing.
- No schemeID is set.
How to fix PEPPOL-EN16931-R020
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-34 along this XPath:
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID - Apply the fix. Add BT-34 in 'ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID' with a matching schemeID attribute, for example schemeID='EM' for an email address.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R020 is no longer reported.
Concrete fix
Add BT-34 in 'ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID' with a matching schemeID attribute, for example schemeID='EM' for an email address.
XPath
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIIDFrequent questions about PEPPOL-EN16931-R020
Does BT-34 differ from the VAT identifier?
Yes. BT-34 is the electronic delivery and identification address on the Peppol network, not the Seller VAT identifier (BT-31).
Related error codes
Check PEPPOL-EN16931-R020 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.