Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
Convert
⌘K
Documentation overview
Understand formats and standards
Compliance Guides
XRechnung Standard
ZUGFeRD Format
PDF/A-3 for ZUGFeRD
CII Cross Industry Invoice
UBL Universal Business Language
DIN EN 16931-1 Standard
PEPPOL Network
Country and regulatory rules
EU E-Invoicing Mandate
EU E-Invoicing
EU e-invoicing in 2026: what to implement (and why)
EU top markets playbook (DE, FR, IT, ES, PL, NL)
PEPPOL in the EU: how exchange actually works
CTC/clearance and portals in the EU: how to build reliable integrations
Country Guides
Germany
France
Italy
Spain
Poland
Netherlands
Belgium
Austria
Denmark
Sweden
Finland
Fix validation and submission issues
Leitweg-ID Validation
Support playbooks
Support
Why invoices need review
PDF readiness
Source data readiness
Attachments and service descriptions
API errors
API automation
Handling schema errors
Review validation help
Support
Missing information
Buyer reference
Payment and IBAN
VAT and reverse charge
Totals and rounding
Prepayments
Line items
ZUGFeRD PDF warnings
Validation playbooks
Observed validation fixes
Due date or terms
Bank transfer IBAN
PDF/A-3 readiness
VATEX exemption reason
Review vs download
Public test invoice fixture library
Valid XRechnung UBL basic invoice
Invalid XRechnung missing payment terms
Factur-X/ZUGFeRD EN 16931 CII XML
XRechnung rounding and IBAN edge case
KoSIT Validator Errors
ERROR
BR-DE-1
BR-DE-2
BR-DE-3
BR-DE-4
BR-DE-5
BR-DE-6
BR-DE-7
BR-DE-8
BR-DE-9
BR-DE-10
BR-DE-11
BR-DE-14
BR-DE-15
BR-DE-16
BR-CO-3
BR-CO-4
BR-CO-9
BR-CO-10
BR-CO-11
BR-CO-13
BR-CO-14
BR-CO-15
BR-CO-16
BR-CO-17
BR-CO-25
BR-CO-26
BR-S-1
BR-S-5
BR-S-8
BR-61
BR-AE-02
BR-AE-10
BR-E-01
BR-E-05
BR-DE-19
BR-05
BR-22
BR-23
BR-24
BR-25
BR-26
BR-47
BR-57
BR-DE-22
BR-DE-30
BR-DE-31
PEPPOL-EN16931-R001
PEPPOL-EN16931-R010
PEPPOL-EN16931-R020
PEPPOL-EN16931-R046
PEPPOL-EN16931-R120
PEPPOL-EN16931-R130
WARNING
BR-DE-17
BR-DE-18
BR-DE-20
BR-DE-21
BR-DE-26
BR-DE-27
BR-DE-28
Look up reference data
Glossary
E
EN 16931
E-reporting
e-Factura RO
EAS (Electronic Address Scheme)
ebInterface
C
CIUS
CII
Code list
Credit note
Contract reference
Chorus Pro
Codice Destinatario
X
XRechnung
XML Schema (XSD)
XML
Z
ZUGFeRD
F
Factur-X
Finvoice
U
UBL
Unit code
P
PEPPOL
PEPPOL BIS
Participant ID
PDF/A-3
Payment means
Purchase order (PO)
PDP (Plateforme de Dématérialisation Partenaire)
A
Access Point
Allowance / charge
S
SMP
SML
Schematron
SDI (Sistema di Interscambio)
Svefaktura
L
Leitweg-ID
K
KoSIT
KSeF
KvK number
V
Validation
VAT ID
ViDA
VeriFactu
ViDA Pillar 1: Digital Reporting Requirements
ViDA Pillar 2: Single VAT Registration
ViDA Pillar 3: Platform Economy
B
Business Term (BT)
Business Group (BG)
BIC
R
Reverse charge
Real-time reporting
Real-time invoice reporting (RTIR)
T
Tax category
TicketBAI
I
IBAN
Invoice type code
Invoice line item
ISO 6523
D
Document reference
D-U-N-S Number
Digipoort
Q
QR code payment
G
GLN (Global Location Number)
O
OVT-tunnus
OIOUBL
N
NemHandel
Code Lists
Currency codes (common)
Country codes (common)
VAT category codes
Payment means type codes
Unit of measure codes (common)
Invoice type codes (common in XRechnung)
XRechnung Fields
Invoice basics
BT-1
BT-2
BT-3
BT-5
BT-6
BT-7
BT-8
BT-10
BT-11
BT-12
BT-14
BT-15
BT-16
BT-17
BT-18
BT-19
BT-21
BT-22
BT-23
BT-24
BT-25
BT-26
Delivery and payment
BT-9
BT-13
BT-20
BT-59
BT-60
BT-61
BT-70
BT-71
BT-72
BT-73
BT-74
BT-75
BT-76
BT-77
BT-78
BT-79
BT-80
BT-81
BT-82
BT-83
BT-84
BT-85
BT-86
BT-87
BT-88
BT-89
BT-90
BT-91
Seller details
BT-27
BT-28
BT-29
BT-30
BT-31
BT-32
BT-33
BT-34
BT-35
BT-36
BT-37
BT-38
BT-39
BT-40
BT-41
BT-42
BT-43
BT-62
BT-63
BT-64
BT-65
BT-66
BT-67
BT-68
BT-69
Buyer details
BT-44
BT-45
BT-46
BT-47
BT-48
BT-49
BT-50
BT-51
BT-52
BT-53
BT-54
BT-55
BT-56
BT-57
BT-58
Discounts and charges
BT-92
BT-93
BT-94
BT-95
BT-96
BT-97
BT-98
BT-99
BT-100
BT-101
BT-102
BT-103
BT-104
BT-105
Taxes and totals
BT-106
BT-107
BT-108
BT-109
BT-110
BT-111
BT-112
BT-113
BT-114
BT-115
BT-116
BT-117
BT-118
BT-119
BT-120
BT-121
BT-122
BT-123
BT-124
BT-125
Line items
BT-126
BT-127
BT-128
BT-129
BT-130
BT-131
BT-132
BT-133
BT-134
BT-135
BT-136
BT-137
BT-138
BT-139
BT-140
BT-141
BT-142
BT-143
BT-144
BT-145
BT-146
BT-147
BT-148
BT-149
BT-150
BT-151
BT-152
BT-153
BT-154
BT-155
BT-156
BT-157
BT-158
BT-159
BT-160
BT-161
BT-162
BT-163
ZUGFeRD Profiles
MINIMUM
BASIC WL
BASIC
EN 16931
EXTENDED
Compare formats and tools
Comparisons
XRechnung vs ZUGFeRD
PDF24 Tools
sevDesk
Integrate and implement
Platform incident help
Support
Temporary unavailable
Missing result
Validation unavailable
Browser errors
Account and rate limits
Credits and subscriptions
Authoritative validation
ERP export validation guides
DATEV
Lexware
SAP Business One
Odoo
Microsoft Dynamics
Trust & Security
Developer API
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-84

Reference

Markdown export

BT-84 Payment account identifier

A unique identifier of the financial payment account, at a payment service provider, to which payment should be made. This identifier typically represents an IBAN for SEPA payments in Germany and is essential for automated payment processing and reconciliation.

Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Quick answer#

A unique identifier of the financial payment account, at a payment service provider, to which payment should be made. This identifier typically represents an IBAN for SEPA payments in Germany and is essential for automated payment processing and reconciliation.

Delivery and payment

Delivery dates, payment means, and the operational context around settlement.

Quick actions

Validate XMLConvert invoice

In plain language#

A unique identifier of the financial payment account, at a payment service provider, to which payment should be made. This identifier typically represents an IBAN for SEPA payments in Germany and is essential for automated payment processing and reconciliation.

A unique identifier of the financial payment account, at a payment service provider, to which payment should be made. This identifier typically represents an IBAN for SEPA payments in Germany and is essential for automated payment processing and reconciliation.

The payment account identifier is important for automated payment processing, enabling straight-through processing in banking systems. When properly formatted as an IBAN, it includes built-in validation through check digits, reducing payment errors and failed transactions. This field works in conjunction with BT-81 (Payment means type code) to specify both the payment method and the destination account. For German SEPA payments, a valid IBAN alone is sufficient for processing, eliminating the need for separate BIC codes in most cases.

What you usually enter here#

IBAN format: Country code (2 letters) + Check digits (2 digits) + Basic Bank Account Number (up to 30 alphanumeric)

Typical valid values include: DE89 3704 0044 0532 0130 00, FR14 2004 1010 0505 0001 3M02 606, GB29 NWBK 6016 1331 9268 19, IT60 X054 2811 1010 0000 0123 456

Conditionally mandatory according to EN 16931-1. Required when Credit transfer (BG-17) information is provided (BR-50) and when Payment means type code (BT-81) indicates SEPA credit transfer, local credit transfer, or non-SEPA international credit transfer (BR-61). Must be a valid IBAN when code 58 (SEPA) is used in BT-81 (BR-DE-19). Compliance with German banking regulations and SEPA standards is mandatory for Euro transactions within the SEPA area.

What goes wrong often#

Avoid values like: DE89370400440532013000, 123456, INVALID

Relevant rule codes: BR-50, BR-61, BR-DE-19, DIN-91379

Examples in context#

The payment account identifier is important for automated payment processing, enabling straight-through processing in banking systems. When properly formatted as an IBAN, it includes built-in validation through check digits, reducing payment errors and failed transactions. This field works in conjunction with BT-81 (Payment means type code) to specify both the payment method and the destination account. For German SEPA payments, a valid IBAN alone is sufficient for processing, eliminating the need for separate BIC codes in most cases.

Conditionally mandatory according to EN 16931-1. Required when Credit transfer (BG-17) information is provided (BR-50) and when Payment means type code (BT-81) indicates SEPA credit transfer, local credit transfer, or non-SEPA international credit transfer (BR-61). Must be a valid IBAN when code 58 (SEPA) is used in BT-81 (BR-DE-19). Compliance with German banking regulations and SEPA standards is mandatory for Euro transactions within the SEPA area.

Valid Examples#

Use these points as the practical checks for this section.

  • DE89 3704 0044 0532 0130 00
  • FR14 2004 1010 0505 0001 3M02 606
  • GB29 NWBK 6016 1331 9268 19
  • IT60 X054 2811 1010 0000 0123 456
  • ES91 2100 0418 4502 0005 1332

Invalid Examples#

Use these points as the practical checks for this section.

  • DE89370400440532013000
  • 123456
  • INVALID

Related Fields#

The payment account identifier is important for automated payment processing, enabling straight-through processing in banking systems. When properly formatted as an IBAN, it includes built-in validation through check digits, reducing payment errors and failed transactions. This field works in conjunction with BT-81 (Payment means type code) to specify both the payment method and the destination account. For German SEPA payments, a valid IBAN alone is sufficient for processing, eliminating the need for separate BIC codes in most cases.

BT-81 Payment means type code
BT-85 Payment account name
BT-86 Payment service provider identifier
BT-89 Mandate reference identifier
BT-90 Bank assigned creditor identifier
BT-91 Debited account identifier

XML mapping and field facts#

Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.

Field ID:

BT-84

Data Type:

identifier

Cardinality:

0..1

Requirement:

Optional

Max Length:

34 characters

Since Version:

Conditional

XML Implementation#

UBL 2.1 Syntax
/Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANID

Validation Rules#

BR-50

BR-50

BR-61

Payment account identifier (BT-84) is required for credit transfer payments

BR-DE-19

BR-DE-19

DIN-91379

DIN-91379

Why the standard cares about this field#

Business Context

The payment account identifier is important for automated payment processing, enabling straight-through processing in banking systems. When properly formatted as an IBAN, it includes built-in validation through check digits, reducing payment errors and failed transactions. This field works in conjunction with BT-81 (Payment means type code) to specify both the payment method and the destination account. For German SEPA payments, a valid IBAN alone is sufficient for processing, eliminating the need for separate BIC codes in most cases.

Legal Requirement

Conditionally mandatory according to EN 16931-1. Required when Credit transfer (BG-17) information is provided (BR-50) and when Payment means type code (BT-81) indicates SEPA credit transfer, local credit transfer, or non-SEPA international credit transfer (BR-61). Must be a valid IBAN when code 58 (SEPA) is used in BT-81 (BR-DE-19). Compliance with German banking regulations and SEPA standards is mandatory for Euro transactions within the SEPA area.

FAQ#

What is the difference between IBAN and BBAN for BT-84?

IBAN (International Bank Account Number) is the preferred format for BT-84, especially for SEPA payments. It includes country code, check digits, and the basic bank account number. BBAN (Basic Bank Account Number) is the national account number format without international standardization. For German XRechnung, IBAN is strongly recommended as it enables automated validation and processing.

When is BT-84 mandatory versus optional?

BT-84 becomes mandatory when: 1) Credit transfer information (BG-17) is provided in the invoice (BR-50), 2) Payment means type code (BT-81) indicates credit transfer methods like 30, 58, or international transfers (BR-61). It remains optional for payment methods like cash (10), cards (48), or online payments (68) that don't require account details.

How do I validate an IBAN for German bank accounts?

German IBANs follow the pattern: DE + 2 check digits + 8-digit bank code (BLZ) + 10-digit account number. Total length is 22 characters. Validation includes: 1) Country code "DE", 2) Valid MOD-97 check digits, 3) Valid German bank code (BLZ), 4) Correct length and format. Many online IBAN validators and banking APIs can verify German IBANs.

Can I use non-SEPA account identifiers in BT-84?

Yes, but with limitations. For international payments outside SEPA, you can use other account formats (like US routing numbers + account numbers). However, for German XRechnung and public sector invoicing, IBAN is strongly preferred. Non-SEPA formats may require additional fields like BIC (BT-86) and may face processing delays or manual intervention.

What happens if I provide an invalid IBAN in BT-84?

Invalid IBANs will cause: 1) XRechnung validation errors during processing, 2) Invoice rejection by receiving systems, 3) Payment processing failures, 4) Manual intervention requirements, 5) Delayed payments and potential penalty charges. Always verify IBAN format and check digits before submitting invoices.

How does BT-84 work with multiple payment methods?

Each payment means group (BG-16) can have its own BT-84 account identifier. This allows invoices to specify different accounts for different payment methods or partial payments. For example, one payment means might specify SEPA transfer to Account A, while another specifies direct debit from Account B. Each account identifier should match its corresponding payment means type code.

Are there security considerations for sharing account identifiers?

IBANs in BT-84 are generally safe to share as they only enable incoming payments, not withdrawals. However, consider: 1) Limiting IBAN exposure to necessary business partners, 2) Using dedicated business accounts for invoicing, 3) Monitoring account activity for unauthorized attempts, 4) Implementing proper access controls for invoice systems, 5) Following data protection regulations for financial information.

How do German banks process SEPA payments with BT-84?

German banks process SEPA payments using BT-84 IBANs through automated systems that: 1) Validate IBAN format and check digits, 2) Route payments through SEPA network infrastructure, 3) Provide same-day or next-day settlement, 4) Generate automatic payment confirmations, 5) Enable straight-through processing without manual intervention. This reduces costs and processing time compared to traditional international transfers.

What is the relationship between BT-84 and BT-85 (Payment account name)?

BT-84 provides the technical account identifier (IBAN), while BT-85 provides the human-readable account holder name. Both work together for complete payment information: BT-84 enables automated processing, while BT-85 helps with manual verification and compliance. For SEPA payments, banks may verify that the account name matches the IBAN holder, adding an extra security layer.

How should I handle IBAN formatting and spacing in BT-84?

IBAN formatting in BT-84 can include spaces for readability (e.g., "DE89 3704 0044 0532 0130 00") or be provided without spaces (e.g., "DE89370400440532013000"). Most systems accept both formats and normalize them during processing. However, ensure consistent formatting within your invoicing system and verify that receiving systems can handle your chosen format.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-83BT-85
On this page
Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Invoice-Converter.com

Helping businesses across Europe convert invoices to XRechnung and other e-invoice formats with validation support. Review edge cases before submission.

20,000+ invoices processed
Fast & Secure
Trusted by hundreds

Features

Convert PDFs & create

  • PDF to XRechnung
  • PDF to UBL
  • PDF to XRechnung (CII)
  • PDF to ZUGFeRD
  • PDF to Factur-X
  • Create XRechnung
  • XRechnung to PDF

View & validate

  • XRechnung/XML Viewer
  • XRechnung Validator

Quick Links

  • Resources
  • Trust & Security Center
  • Developer API Documentation
  • Blog
  • FAQ
  • Pricing
  • Climate Contribution

Legal

  • Imprint
  • Privacy Policy
  • Data Processing Agreement
  • Terms & Conditions
  • Money-Back Guarantee

Get in Touch

contact@invoice-converter.com
Start Converting
© 2026 Invoice-Converter.com.Made with in Europe
GDPR Compliant
German Server