PEPPOL-EN16931-R080 in your own invoice? Upload the file and find every error in seconds.
What does PEPPOL-EN16931-R080 mean?
Peppol allows exactly one project reference at document level so the invoice can be assigned to a single project.
Common causes of PEPPOL-EN16931-R080
- Several SpecifiedProcuringProject elements at header level.
How to fix PEPPOL-EN16931-R080
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-11 along this XPath:
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SpecifiedProcuringProject/ram:ID - Apply the fix. Reduce the project references to exactly one 'ram:SpecifiedProcuringProject' (BT-11) at header level.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R080 is no longer reported.
Concrete fix
Reduce the project references to exactly one 'ram:SpecifiedProcuringProject' (BT-11) at header level.
XPath
//rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SpecifiedProcuringProject/ram:IDRelated error codes
Check PEPPOL-EN16931-R080 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.