PEPPOL-EN16931-R002 in your own invoice? Upload the file and find every error in seconds.
What does PEPPOL-EN16931-R002 mean?
PEPPOL BIS Billing 3.0 deliberately allows only one note at document level to keep machine processing unambiguous. Several header notes would make automatic processing harder.
Common causes of PEPPOL-EN16931-R002
- The invoicing software writes several 'IncludedNote' elements at header level.
- Extra free texts (for example payment terms or closing remarks) were each created as a separate note.
How to fix PEPPOL-EN16931-R002
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-22 along this XPath:
//rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNote/ram:Content - Apply the fix. Merge all header notes into a single 'ram:IncludedNote' (BT-22) or move the extra remarks to line level.
- Validate again. Save the file and validate it again to check that PEPPOL-EN16931-R002 is no longer reported.
Concrete fix
Merge all header notes into a single 'ram:IncludedNote' (BT-22) or move the extra remarks to line level.
XPath
//rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNote/ram:ContentFrequent questions about PEPPOL-EN16931-R002
How do I fit several remarks in?
Merge them into one BT-22 note using line breaks. Remarks that relate to a line belong on the respective invoice line anyway.
Related error codes
Check PEPPOL-EN16931-R002 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.