# BT-81 Payment means type code The means, expressed as code, for how a payment is expected to be or has been settled. This field specifies the payment method using standardized UN/CEFACT codes (UNCL4461) to ensure consistent payment processing across different systems and jurisdictions. ## Quick answer The means, expressed as code, for how a payment is expected to be or has been settled. This field specifies the payment method using standardized UN/CEFACT codes (UNCL4461) to ensure consistent payment processing across different systems and jurisdictions. > **Delivery and payment**: Delivery dates, payment means, and the operational context around settlement. ## In plain language The means, expressed as code, for how a payment is expected to be or has been settled. This field specifies the payment method using standardized UN/CEFACT codes (UNCL4461) to ensure consistent payment processing across different systems and jurisdictions. The means, expressed as code, for how a payment is expected to be or has been settled. This field specifies the payment method using standardized UN/CEFACT codes (UNCL4461) to ensure consistent payment processing across different systems and jurisdictions. The payment means type code is essential for automated payment processing, enabling systems to understand how payments should be executed. It determines whether additional payment details like bank account information (BT-84) or card details are required. This standardization facilitates straight-through processing in banking systems and reduces manual intervention in payment workflows. ## What you usually enter here Three-digit numeric code from UN/CEFACT code list UNCL4461 Typical valid values include: 30, 58, 59, 49 Optional according to EN 16931-1, but highly recommended for automated payment processing. When provided, it must use valid codes from UN/CEFACT code list UNCL4461. German banking regulations and SEPA requirements may influence the choice of payment method codes. ## What goes wrong often Avoid values like: 001, BANK, TRANSFER, CC Relevant rule codes: BR-49, PEPPOL-EN16931-CL007 ## Examples in context The payment means type code is essential for automated payment processing, enabling systems to understand how payments should be executed. It determines whether additional payment details like bank account information (BT-84) or card details are required. This standardization facilitates straight-through processing in banking systems and reduces manual intervention in payment workflows. Optional according to EN 16931-1, but highly recommended for automated payment processing. When provided, it must use valid codes from UN/CEFACT code list UNCL4461. German banking regulations and SEPA requirements may influence the choice of payment method codes. ## Valid Examples - 30 - 58 - 59 - 49 - 48 - 10 - 68 - 69 - 70 ## Invalid Examples - 001 - BANK - TRANSFER - CC - SEPA - 999 ## Related Fields The payment means type code is essential for automated payment processing, enabling systems to understand how payments should be executed. It determines whether additional payment details like bank account information (BT-84) or card details are required. This standardization facilitates straight-through processing in banking systems and reduces manual intervention in payment workflows. - [BT-82 Payment means text](/resources/xrechnung/bt-82-payment-means-text) - [BT-83 Remittance information](/resources/xrechnung/bt-83-remittance-information) - [BT-84 Payment account identifier](/resources/xrechnung/bt-84-payment-account-identifier) - [BT-85 Payment account name](/resources/xrechnung/bt-85-payment-account-name) - [BT-86 Payment service provider identifier](/resources/xrechnung/bt-86-payment-service-provider-identifier) - [BT-87 Payment card primary account number](/resources/xrechnung/bt-87-payment-card-primary-account-number) - [BT-88 Payment card holder name](/resources/xrechnung/bt-88-payment-card-holder-name) - [BT-89 Mandate reference identifier](/resources/xrechnung/bt-89-mandate-reference-identifier) - [BT-90 Bank assigned creditor identifier](/resources/xrechnung/bt-90-bank-assigned-creditor-identifier) - [BT-91 Debited account identifier](/resources/xrechnung/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-81 ### Data Type: code ### Cardinality: 0..1 ### Requirement: Optional ### Max Length: 3 characters ### Since Version: Optional ## XML Implementation ### UBL 2.1 Syntax ``` /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode ``` ### CII (UN/CEFACT) Syntax ``` /CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode ``` ## Validation Rules ### BR-49 BR-49 ### PEPPOL-EN16931-CL007 PEPPOL-EN16931-CL007 ## Why the standard cares about this field ### Business Context The payment means type code is essential for automated payment processing, enabling systems to understand how payments should be executed. It determines whether additional payment details like bank account information (BT-84) or card details are required. This standardization facilitates straight-through processing in banking systems and reduces manual intervention in payment workflows. ### Legal Requirement Optional according to EN 16931-1, but highly recommended for automated payment processing. When provided, it must use valid codes from UN/CEFACT code list UNCL4461. German banking regulations and SEPA requirements may influence the choice of payment method codes. ## FAQ ### What are the most common payment means type codes in Germany? The most common codes in German business are: 30 (Credit transfer/Bank transfer), 58 (SEPA credit transfer), 59 (SEPA direct debit), 49 (Direct debit), and 48 (Bank card/EC card). SEPA codes (58, 59) are preferred for Euro transactions within the SEPA area. ### When should I use code 30 versus code 58? Use code 58 (SEPA credit transfer) for Euro payments within the SEPA area, as it offers faster processing and lower costs. Use code 30 (Credit transfer) for international payments outside SEPA or non-Euro currencies. Code 58 typically requires only IBAN, while code 30 may require both IBAN and BIC. ### Do I need to provide bank account details when using payment means codes? It depends on the payment means code. Codes requiring account information include: 30, 58 (need IBAN, possibly BIC), 49, 59 (need account for direct debit). Codes like 10 (cash), 48 (card), 68 (online payment) typically don't require account details. Check the related fields BT-84 through BT-91 for specific account information requirements. ### What is the difference between codes 49 and 59 for direct debit? Code 49 (Direct debit) is for general direct debit transactions, including non-SEPA debits that may require BIC. Code 59 (SEPA direct debit) is specifically for Euro direct debits within the SEPA area, typically requiring only IBAN and offering standardized processing times and lower costs. ### Can I use multiple payment means codes in one invoice? Yes, XRechnung supports multiple payment means per invoice (cardinality allows multiple payment instruction groups). Each payment means can have its own code, account details, and amount allocation. This is useful for partial payments, multi-currency invoices, or offering payment alternatives. ### How do German public authorities handle different payment means codes? German public authorities typically prefer SEPA payment methods (codes 58 for credit transfer, 59 for direct debit) for efficient processing. Many authorities have automated systems that can process these codes for faster payment reconciliation. Some may restrict payment methods for security or administrative reasons - check specific authority requirements. ### What happens if I use an invalid payment means code? Invalid payment means codes will cause validation errors during XRechnung processing. The invoice may be rejected by the receiving system. Always use codes from the official UN/CEFACT UNCL4461 code list. Common mistakes include using descriptive text instead of numeric codes or using outdated codes. ### Are there special considerations for B2B versus B2G payments? B2G (Business-to-Government) payments often have stricter requirements and may prefer specific codes like 58 (SEPA credit transfer) for transparency and audit trails. B2B payments have more flexibility and may use various codes including 48 (cards), 68 (online payments), or 70 (mobile payments) depending on business relationships and agreements. ### How does the payment means code affect settlement timing? Different payment codes have varying settlement times: SEPA transfers (58) typically settle within 1 business day, direct debits (59) follow SEPA timelines, credit cards (48, 54) may settle within 1-3 days, while cash (10) settles immediately. Understanding these timings helps with cash flow planning and payment term setting. ### Can I specify payment terms along with payment means codes? Yes, payment means codes (BT-81) work together with payment terms (BT-20) and payment due date (BT-9). The payment means code specifies HOW to pay, while payment terms specify WHEN to pay and any conditions. For example, you can specify code 58 (SEPA transfer) with "Net 30 days" payment terms. ## Official sources and tools - [KoSIT Validator](https://erechnungsvalidator.service-bw.de/) - [Invoice Converter](/pdf-to-xrechnung) - [XRechnung Standard](https://xeinkauf.de/xrechnung/) - [Test Suite](https://github.com/itplr-kosit/xrechnung-testsuite)