Skip to content

PEPPOL-EN16931-R101: Document reference in the line only for the object identifier (type 130)

Official message

[PEPPOL-EN16931-R101] Element Additional referenced document can only be used for Invoice line object.

XRechnung (CII) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[PEPPOL-EN16931-R101] Element Document reference can only be used for Invoice line object

XRechnung (UBL) · Error · Message language: English · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Error The invoice is invalid and may be rejected by the recipient.
Applies to
XRechnung (CII), XRechnung (UBL)

What does this mean?

Element Additional referenced document can only be used for Invoice line object: in an invoice line a document reference may only be used for the invoice line object identifier (BT-128), i.e. with document type 130. The line contains a document reference without this type.
The rule originates from Peppol BIS Billing 3.0 and is applied in the XRechnung validation. CII: ram:SpecifiedLineTradeSettlement/ram:AdditionalReferencedDocument with ram:TypeCode 130. UBL: cac:InvoiceLine/cac:DocumentReference or cac:CreditNoteLine/cac:DocumentReference with cbc:DocumentTypeCode 130.

Typical causes

A delivery note, an order or an attachment was given as document reference in the line.
The type code 130 is missing or another code was used.

How to fix the error

In the line only state the object identifier (BT-128) as document reference with type 130.
Give order lines via the referenced purchase order line reference (BT-132), other documents on document level (e.g. BT-16 despatch advice or BG-24 additional supporting documents).
Generate and validate the invoice again.

In E-Rechnungsfreund

The invoice form always writes entries of a line's tab "Objekt-IDs (BT-128)" (object IDs) in section "Rechnungspositionen (BG-25)" (invoice lines) with type 130. Do not enter other documents there, but on document level in the sections "Referenzen (Bestell-, Vertrags-, Projektnummern)" (references) or "Zusätzliche Dokumente (BG-24) – optional" (additional documents). Generate and validate the invoice again.

Example

Wrong

<ram:SpecifiedLineTradeSettlement>
  ...
  <ram:AdditionalReferencedDocument>
    <ram:IssuerAssignedID>DN-4711</ram:IssuerAssignedID>
    <ram:TypeCode>916</ram:TypeCode>
  </ram:AdditionalReferencedDocument>
  ...
</ram:SpecifiedLineTradeSettlement>

Correct

<ram:SpecifiedLineTradeSettlement>
  ...
  <ram:AdditionalReferencedDocument>
    <ram:IssuerAssignedID>METER-0815</ram:IssuerAssignedID>
    <ram:TypeCode>130</ram:TypeCode>
  </ram:AdditionalReferencedDocument>
  ...
</ram:SpecifiedLineTradeSettlement>
For developers: test expression per syntax

XRechnung (CII) (CII)

Context: ram:IncludedSupplyChainTradeLineItem

(not(ram:SpecifiedLineTradeSettlement/ram:AdditionalReferencedDocument) or (ram:SpecifiedLineTradeSettlement/ram:AdditionalReferencedDocument/ram:TypeCode='130'))

XRechnung (UBL) (UBL)

Context: cac:InvoiceLine | cac:CreditNoteLine

(not(cac:DocumentReference) or (cac:DocumentReference/cbc:DocumentTypeCode='130'))

Related validation rules

Last updated:
Explanation of the validation rule, not legal or tax advice.