What does PEPPOL-EN16931-R010 mean?
On the Peppol network, the invoice is delivered by the recipient's electronic address (BT-49) - much like an email address for invoices. Without it the invoice cannot be routed.
Common causes of PEPPOL-EN16931-R010
- The element URIUniversalCommunication/ram:URIID on the buyer is missing.
- No schemeID (for example 'EM', '9958') is set.
How to fix PEPPOL-EN16931-R010
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-49 along this XPath:
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID - Apply the fix. Add BT-49 in 'ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID' with a matching schemeID attribute, for example schemeID='EM' for an email address or '9958' for a Leitweg-ID.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R010 is no longer reported.
Add BT-49 in 'ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID' with a matching schemeID attribute, for example schemeID='EM' for an email address or '9958' for a Leitweg-ID.
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIIDFrequent questions about PEPPOL-EN16931-R010
What is an electronic address?
Related error codes
Check PEPPOL-EN16931-R010 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.