Skip to content

BT-86: Payment Service Provider Identifier (BIC)

The Business Identifier Code (BIC) of the financial institution.

BT-86Optional (0..1)EN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
0..1(Optional)

Optional in SEPA, recommended for cross-border transactions

Data Type
BIC (8 or 11 characters)

Semantic data format according to European Standard EN 16931-1

XML Syntax Mappings
UBL 2.1(XRechnung / Peppol BIS)
Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID
UN/CEFACT CII D16B(ZUGFeRD 2.3 / Factur-X)
rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeeSpecifiedCreditorFinancialInstitution/ram:BICID

What does BT-86 mean?

BT-86 provides the BIC/SWIFT code of the payee bank. While IBAN-only applies within SEPA, BIC remains valuable for international payment execution.

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cac:FinancialInstitutionBranch>
  <cbc:ID>DBEUDDFXXXX</cbc:ID>
</cac:FinancialInstitutionBranch>

Check BT-86 in your invoice

Use the XML paths above to locate BT-86. A snippet illustrates this field; it is not a complete invoice. After correcting a value in the source application, export and check the entire file again.

Official specifications and rule sets

Requirements depend on the invoice profile and version. Consult the matching specification for mandatory fields, code lists and rules; Peppol-specific requirements do not automatically apply to every ZUGFeRD invoice.

Create compliant E-Invoices easily

Create XRechnung and ZUGFeRD invoices in Billance and check the exported file locally. Use this guide to understand BT-86 and review your invoice details before sending.