InvoiceKit

EN 16931 rules › BR-51

BR-51 — In accordance with card payments security standards an invoice should never include a full card primary account number…

Rule idBR-51
Rule setEN 16931 itself, not a national or network addition
Severityfatal in CII, warning in UBL; the wording below says which applies where
Applies tothe CII and UBL syntaxes
Checked bythe validator on this site and invoicekit.go v0.2.11, the library behind it

The rule as published

In accordance with card payments security standards an invoice should never include a full card primary account number (BT-97). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown.

fatal in CII — a validator enforcing this rule set rejects the invoice.

In accordance with card payments security standards an invoice should never include a full card primary account number (BT-87). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown.

warning in UBL — flagged as non-conforming; a Peppol access point rejects warnings too.

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.

SyntaxSeverityArtefact phaseApplied toFails when
CIIfatalEN16931-model-phase//ram:ApplicableTradeSettlementFinancialCardstring-length(normalize-space(ram:ID)) <= 10
UBLwarningEN16931model_phasecac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberIDstring-length(normalize-space(.))<=10

Data elements it names

See also

· All EN 16931 rules ·