Skip to content

BT-81: Payment Means Type Code

Code indicating the method of payment from UNTDID 4461 (e.g. 58 for SEPA credit transfer).

BT-81Mandatory (1..1)EN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
1..1(Mandatory)

Mandatory (1..1) coded from UNTDID 4461

Data Type
Code (UNTDID 4461)

Semantic data format according to European Standard EN 16931-1

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

What does BT-81 mean?

The payment means code (BT-81) informs financial systems how funds will be settled according to UNTDID 4461. In Europe, 58 (SEPA credit transfer) and 59 (SEPA direct debit) are standard.

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cac:PaymentMeans>
  <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
  <cac:PayeeFinancialAccount>
    <cbc:ID>DE89370400440532013000</cbc:ID>
  </cac:PayeeFinancialAccount>
</cac:PaymentMeans>

Codelist Values: UNTDID 4461 Payment Means Codes

CodeMeaningDescription & Usage
58SEPA credit transferStandard bank transfer in the SEPA zone.
30Credit transferGeneral bank account credit transfer.
59SEPA direct debitDirect debit by seller with SEPA mandate.
48Bank cardPayment by payment card.
10In cashSettlement with physical cash.
97Clearing between partnersOffsetting mutual obligations.

Business Rules & Schematron Checks

BR-49

An invoice shall have a Payment means type code (BT-81).

BR-50

If payment means is credit transfer, a Payment account identifier (BT-84) shall be provided.

Check BT-81 in your invoice

Use the XML paths above to locate BT-81. 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-81 and review your invoice details before sending.