PEPPOL-EN16931-R080:Too many project references
Fix: Review your Invoice XML structure and correct the issue described by this rule. Check relevant cbc: and cac: elements per EN 16931 (PEPPOL-EN16931-R080).
The invoice has more than one project reference at the document level. Peppol allows only a single project reference per invoice. If your invoice relates to multiple projects, use only the primary one at the document level.
Engine Classification
Financial or legal field · Modification blocked by policy
What is PEPPOL-EN16931-R080?
PEPPOL-EN16931-R080 is a fatal validation rule defined in the EN 16931 specification. It validates the XPath: cac:ProjectReference — Peppol rule PEPPOL-EN16931-R080. Only one ProjectReference element is allowed at document level. element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: XPath: cac:ProjectReference — Peppol rule PEPPOL-EN16931-R080. Only one ProjectReference element is allowed at document level.
Why This Error Matters
Invoice will be rejected by PEPPOL validation. Document level supports only one project reference.
PEPPOL-EN16931-R080 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Multiple project references prevent the receiver from routing the invoice to the correct project or cost center. The invoice will be rejected by Peppol validation.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: PEPPOL-EN16931-R080
- ·Specification: EN 16931
How to Fix It
Review the project references
Your invoice has multiple ProjectReference elements. Check which one is the primary project for this invoice.
Keep one reference
Remove the extra ProjectReference elements, keeping only the primary one.
Move to line level
If items belong to different projects, consider using line-level references instead of document-level.
Before / After
<Invoice> <!-- Issue: Only one project reference is allowed on document level. --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
XPath: cac:ProjectReference — Peppol rule PEPPOL-EN16931-R080. Only one ProjectReference element is allowed at document level.Common Causes
- ·ERP exports both project and sub-project references
- ·Multiple project IDs added during manual editing
- ·Template includes placeholder project references
Seeing this in production? The API handles PEPPOL-EN16931-R080 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The invoice has more than one project reference at the document level. Peppol allows only a single project reference per invoice. If your invoice relates to multiple projects, use only the primary one at the document level.
Review your Invoice XML structure and correct the issue described by this rule. Check relevant cbc: and cac: elements per EN 16931 (PEPPOL-EN16931-R080). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, PEPPOL-EN16931-R080 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of PEPPOL-EN16931-R080 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
PEPPOL-EN16931-R080 is commonly seen in exports from All invoicing software. These packages sometimes generate invoices that need adjustment.
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for PEPPOL-EN16931-R080
Detect PEPPOL-EN16931-R080 before submission
This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.