# UBL-SR-44

Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.

- Country: EU
- Syntax: UBL
- Severity: fatal
- Statement language: en
- Last verified: 2026-10-18

## Official statement

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

Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/UBL-SR-44/

Peppol BIS Billing 3.0, May 2026 release, EN 16931 model bound to UBL

Severity note: fatal, from the Flag column of the Peppol BIS Billing 3.0 UBL rules index retrieved 2026-10-18.

## Plain-language reading

An invoice may have only one distinct payment identifier. The statement has no period and says may. It does not say shall. It is 102 characters. The flag is fatal. The context is the same string as BR-CO-18. The published test does not wrap the count in parentheses. It counts distinct PaymentID values and writes = and <= with a space on each side.

## What to change

Use one payment identifier, even when several payment means share it.

## Illustration

Illustration of the condition in the official statement. Not an example published by the source.

**Fails the stated condition.** The invoice has two different payment identifiers.

**Passes the stated condition.** The invoice has one payment identifier, or none, including when several payment means repeat it.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
/ubl:Invoice | /cn:CreditNote
```

```
count(//cbc:PaymentID[not(preceding::cbc:PaymentID/. = .)]) <= 1
```

[All rule notes](https://einvoicegoblin.com/rules/index.md) · [JSON](https://einvoicegoblin.com/rules/UBL-SR-44.json) · [HTML](https://einvoicegoblin.com/rules/UBL-SR-44/) · [llms.txt](https://einvoicegoblin.com/llms.txt) · [Invoice page](https://einvoicegoblin.com/) · [Privacy](https://einvoicegoblin.com/privacy.html)