Is PEPPOL-EN16931-R100 a critical error?

Yes, PEPPOL-EN16931-R100 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted.

Can PEPPOL-EN16931-R100 be automatically fixed?

Yes, PEPPOL-EN16931-R100 can be automatically corrected. The fix is applied without modifying financial fields.

Error codes · EN 16931

PEPPOL-EN16931-R100In your invoicing software

Only one invoiced object is allowed pr line

This is the rejection, word for word: „[PEPPOL-EN16931-R100] Only one invoiced object identifier is allowed per invoice line. Each line can reference at most one object (contract, order, etc.).“

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doInvoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (PEPPOL-EN16931-R100).

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<Invoice>
  <!-- Issue: Only one invoiced object is allowed per line. -->
</Invoice>

After

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with PEPPOL-EN16931-R100.

What the finding looks likeExample

FindingStructure invalid · PEPPOL-EN16931-R100

Location//cac:InvoiceLine/cac:DocumentReference

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check