Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
ConvertConvert Invoice
⌘K
Documentation overview
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-60

Reference

BT-60 Payee identifier

General identifier of the payee, for example a network or registry identifier.

Quick answer

Delivery and payment

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

In plain language

General identifier of the payee, for example a network or registry identifier.

General identifier of the payee, for example a network or registry identifier.

This helps the buyer identify the payment recipient precisely when the seller and payee are not the same entity.

What you usually enter here

Structured payee identifier

Typical valid values include: 9930:DE445566778

Optional according to EN 16931-1.

What goes wrong often

Avoid values like: payee

Examples in context

This helps the buyer identify the payment recipient precisely when the seller and payee are not the same entity.

Optional according to EN 16931-1.

Valid Examples

  • 9930:DE445566778

Invalid Examples

  • payee

Related Fields

This helps the buyer identify the payment recipient precisely when the seller and payee are not the same entity.

BT-59 Payee name
BT-61 Payee legal registration 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-60

Data Type:

identifier

Cardinality:

0..1

Requirement:

Optional

Max Length:

50 characters

Since Version:

Optional

XML Implementation

UBL 2.1 Syntax
/Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:ID

Why the standard cares about this field

Business Context

This helps the buyer identify the payment recipient precisely when the seller and payee are not the same entity.

Legal Requirement

Optional according to EN 16931-1.

Official sources and tools

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
Previous page
BT-59
Next page
BT-61
On this page
Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationWhy the standard cares about this fieldOfficial sources and tools

Invoice-Converter.com

Empowering businesses across Europe to effortlessly comply with XRechnung regulations. Join hundreds who've automated their invoice conversion process.

Start Converting

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
  • About
  • Pricing
  • Free trial
  • Climate Contribution

Legal

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

Get in Touch

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