# BR-51: Full card number (BT-87) on the invoice

Source: https://veriport.io/einvoice-rules/br-51 (published 2026-11-17)

The payment card number, BT-87, may show at most the first six and the last four digits, as the PCI Security Standards Council requires (`cac:CardAccount/cbc:PrimaryAccountNumberID` in UBL, `ram:ApplicableTradeSettlementFinancialCard/ram:ID` in CII). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** warning (UBL), error (CII)
- **Business terms:** BT-87, BT-97
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-51 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-51]-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.
```

```text
[BR-51]-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.
```

## What it checks

The payment card number, BT-87, may show at most the first six and the last four digits, as the PCI Security Standards Council requires (`cac:CardAccount/cbc:PrimaryAccountNumberID` in UBL, `ram:ApplicableTradeSettlementFinancialCard/ram:ID` in CII). The CII file tests a maximum of ten characters; the UBL file reports it as a warning, the CII file as fatal.

## Why invoices fail it

The full card number is copied from the payment record into the invoice.

## How to fix it

Write only the last four digits (or the first six and the last four) of the card number.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-51.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-51** | warning | `/ubl:Invoice/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID` | 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. |

```diff
  …
      <cbc:PaymentMeansCode>48</cbc:PaymentMeansCode>
      <cac:CardAccount>
-       <cbc:PrimaryAccountNumberID>4111111111111111</cbc:PrimaryAccountNumberID>
+       <cbc:PrimaryAccountNumberID>4242</cbc:PrimaryAccountNumberID>
        <cbc:NetworkID>VISA</cbc:NetworkID>
      </cac:CardAccount>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID
test:    string-length(normalize-space(.))<=10
```

```xpath
context: //ram:ApplicableTradeSettlementFinancialCard
test:    string-length(normalize-space(ram:ID)) <= 10
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-49: Payment means type code (BT-81) missing](https://veriport.io/einvoice-rules/br-49)
- [BR-50: Payment account (BT-84) for a credit transfer](https://veriport.io/einvoice-rules/br-50)
- [BR-52: Supporting document reference (BT-122) missing](https://veriport.io/einvoice-rules/br-52)
- [BR-53: VAT total in accounting currency (BT-111)](https://veriport.io/einvoice-rules/br-53)
- [BR-CO-05: Allowance reason code and text agree](https://veriport.io/einvoice-rules/br-co-05)
- [BR-CO-21: Document allowance without a reason](https://veriport.io/einvoice-rules/br-co-21)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
