Skip to content

Fatal

UBL-SR-44: An invoice can have only one payment reference

In short

Fatal: fails the selected checks.

UBL-SR-44 limits the payment reference (cbc:PaymentID) to one distinct value. Use the same value wherever you repeat it.

On this page

What it means

The payment reference (BT-83) is the text the buyer should quote when paying. The main test allows at most one distinct cbc:PaymentID value anywhere in the invoice or credit note. You may repeat that value in several payment means blocks (cac:PaymentMeans).

Why it matters

The rule limits payment references to one value for the document.

How to fix it

Check the payment details in your invoicing software, especially if you list more than one way to pay. Make sure one payment reference is used everywhere. If you build the XML yourself, give every cbc:PaymentID the same value, or keep it in one block only.

Once the file is corrected, check it again for free: Validate an invoice against EN 16931

Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice

The rule as published

An Invoice may only have one unique PaymentID, but the PaymentID may be used for multiple PaymentMeans

Where this rule applies

Rule set Version
EN 16931 (UBL) 1.3.17
EN 16931 (UBL credit note) 1.3.17
XRechnung 3.0 (UBL) 3.0.2
XRechnung 3.0 (UBL credit note) 3.0.2
Peppol BIS Billing 3.0 (invoice) 2026.5
Peppol BIS Billing 3.0 (credit note) 2026.5
SI-UBL 2.0 / NLCIUS (invoice) 2.0.3.13
SI-UBL 2.0 / NLCIUS (credit note) 2.0.3.13
France CTC (UBL invoice) 1.4.0-04
France CTC (UBL credit note) 1.4.0-04
CIUS-RO UBL Invoice 1.0.9 1.0.9
CIUS-RO UBL Credit Note 1.0.9 1.0.9
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether UBL-SR-44 still fails, and which other rules do.

Updated 8 November 2026