# UBL-SR-44

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

Checked against Peppol BIS Billing 3.0 2026.5

Canonical: https://einvoicecheck.eu/rules/ubl-sr-44

## Official rule text

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

## Why did my invoice fail UBL-SR-44?

The Payment ID (BT-83, 'Remittance information') identifies a payment so the buyer's remittance can be matched by the seller. An invoice may carry only one unique PaymentID value, but that same value may legitimately be repeated across multiple cac:PaymentMeans blocks. This keeps the remittance reference unambiguous while still allowing several payment method options.

## Common causes

- Two or more cac:PaymentMeans elements carry different cbc:PaymentID values instead of the same one.
- A generation template writes a distinct remittance reference per payment channel (e.g. one per IBAN).
- Merging data from multiple source records produced conflicting PaymentID strings.

## How do I fix it?

```
Use one consistent value everywhere, e.g. put the same <cbc:PaymentID>REF-2026-001</cbc:PaymentID> inside every cac:PaymentMeans block.
```
