Reference
Markdown exportBT-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 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.
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
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
/Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANIDValidation Rules
BR-50
BR-50
BR-61
Business Process Type Identifier must have a valid URN format
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.