What it means
Each of these four parties holds its registered name and company registration number in a single cac:PartyLegalEntity, for example the seller name (BT-27) and the seller's company registration number (BT-30), or the buyer name (BT-44) and the buyer's (BT-47). The check counts the blocks for each party and allows at most one.
Why it matters
The recipient's software reads the registered name and company registration number from this one block. With two blocks it cannot tell which one belongs to the party, so the invoice is rejected.
How to fix it
In your invoicing software, check the company details of the seller and the buyer for doubled entries, then export again. If you build the XML yourself, merge the registration name, the company ID and the legal form into a single cac:PartyLegalEntity for each party.
The rule as published
PartyLegalEntity shall occur maximum once within a Party. 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 |
| 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 |
Check your file
Drop your e-invoice to see whether UBL-SR-57 still fails, and which other rules do.
Related rules
- UBL-SR-58 A bank branch must have exactly one bank identifier
- UBL-SR-59 A bank account must have exactly one account identifier
- UBL-SR-56 An invoice can have only one tender or lot reference
- UBL-SR-55 An invoice can have only one direct debit mandate
- UBL-SR-54 An invoice can have only one payment card account
- UBL-SR-53 Tax scheme entries need both a scheme code and a number