Skip to content

Warning

UBL-CR-455: Payment terms must not carry a reference event code

In short

Warning: worth checking.

UBL-CR-455 warns that your UBL invoice or credit note includes a reference event code (cbc:ReferenceEventCode) within the payment terms. Remove that code from the XML and recheck the file.

On this page

What it means

This rule checks that cac:PaymentTerms contains no cbc:ReferenceEventCode element. It does not check the due date (BT-9) or how your software calculates it.

Why it matters

EN 16931 does not use a structured reference event code within UBL payment terms. Payment conditions can instead be described in the payment terms text (BT-20).

How to fix it

Remove cbc:ReferenceEventCode from cac:PaymentTerms in the XML export. If the payment period's starting point needs explaining, state it in cbc:Note (BT-20). Do not remove the date calculation from your software just to omit this code. Recheck the file.

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

A UBL invoice should not include the PaymentTerms ReferenceEventCode

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-CR-455 still fails, and which other rules do.

Updated 6 November 2026