EN 16931 rules › BR-55
BR-55 — Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25)
| Rule id | BR-55 |
|---|---|
| Rule set | EN 16931 itself, not a national or network addition |
| Severity | fatal in CII and UBL — a validator enforcing this rule set rejects the invoice |
| Applies to | the CII and UBL syntaxes |
| Checked by | the validator on this site and invoicekit.go v0.2.11, the library behind it |
The rule as published
Each Preceding Invoice reference (BG-3) shall contain a Preceding Invoice reference (BT-25).
fatal in CII and UBL — a validator enforcing this rule set rejects the invoice.
What runs for it
Straight from the artefacts the engine embeds: the node the assertion selects and the test it applies there. A failing invoice is reported with the message above.
| Syntax | Severity | Artefact phase | Applied to | Fails when |
|---|---|---|---|---|
| CII | fatal | EN16931-model-phase | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument | normalize-space(ram:IssuerAssignedID) != '' |
| UBL | fatal | EN16931model_phase | cac:BillingReference | exists(cac:InvoiceDocumentReference/cbc:ID) |
Data elements it names
- BG-3 Preceding Invoice reference (cited by 1 rule)
- BT-25 Preceding Invoice reference (cited by 1 rule)
See also
- Every EN 16931 rule id — the same list as a filterable table, with the assertions as CSV and JSON.
- What XRechnung and Peppol BIS add — rule sets that run these ids plus their own.
- The data elements — every BT and BG with the rules that name it.