What does PEPPOL-EN16931-R003 mean?
Peppol requires at least one assignment reference so the invoice recipient can route the invoice to the right case automatically. In Germany this matches the duty to give the Leitweg-ID on B2G invoices (see BR-DE-15).
Common causes of PEPPOL-EN16931-R003
- Neither BuyerReference (BT-10) nor a purchase order reference (BT-13) is set.
- The Leitweg-ID was not carried over into BT-10.
How to fix PEPPOL-EN16931-R003
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-10 along this XPath:
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerReference - Apply the fix. Give the buyer reference (BT-10) in 'ram:ApplicableHeaderTradeAgreement/ram:BuyerReference' - in Germany this is the Leitweg-ID for public authorities. A purchase order reference (BT-13) in 'ram:BuyerOrderReferencedDocument/ram:IssuerAssignedID' is enough as an alternative.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R003 is no longer reported.
Give the buyer reference (BT-10) in 'ram:ApplicableHeaderTradeAgreement/ram:BuyerReference' - in Germany this is the Leitweg-ID for public authorities. A purchase order reference (BT-13) in 'ram:BuyerOrderReferencedDocument/ram:IssuerAssignedID' is enough as an alternative.
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerReferenceFrequent questions about PEPPOL-EN16931-R003
Does the order number replace the Leitweg-ID?
Related error codes
Check PEPPOL-EN16931-R003 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.