Skip to main content

BT-125 Attached Document

The binary content of a supporting document embedded directly in the invoice.

Quick answer

Taxes and totals

VAT treatment, tax breakdowns, and document totals that validators check closely.

Quick actions

In plain language

Embeds evidence directly in the invoice package when the receiver needs the document with the invoice.

What you usually enter here

Base64 encoded binary object with a valid MIME code and unique filename

Typical valid values include: Base64-encoded PDF attachment

Embedded supporting documents must use allowed MIME codes, and XRechnung requires attachment filenames to be unique.

Where the field sits

Attachments
UBL 2.1 Syntax
  1. Invoice
  2. cac:AdditionalDocumentReference[not(cbc:DocumentTypeCode="130")]
  3. cac:Attachment
  4. cbc:EmbeddedDocumentBinaryObjectBT-125
CII (UN/CEFACT) Syntax
  1. rsm:CrossIndustryInvoice
  2. rsm:SupplyChainTradeTransaction
  3. ram:ApplicableHeaderTradeAgreement
  4. ram:AdditionalReferencedDocument[ram:TypeCode="916"]
  5. ram:AttachmentBinaryObjectBT-125
BT-125 belongs to the Attachments part of the invoice. UBL 2.1 Syntax: Invoice › cac:AdditionalDocumentReference[not(cbc:DocumentTypeCode="130")] › cac:Attachment › cbc:EmbeddedDocumentBinaryObject. CII (UN/CEFACT) Syntax: rsm:CrossIndustryInvoice › rsm:SupplyChainTradeTransaction › ram:ApplicableHeaderTradeAgreement › ram:AdditionalReferencedDocument[ram:TypeCode="916"] › ram:AttachmentBinaryObject.

What goes wrong often

Avoid values like: Raw file path, Plain text without binary encoding

Relevant rule codes: BR-CL-24, BR-DE-22

Valid Examples

  • Base64-encoded PDF attachment

Invalid Examples

  • Raw file path
  • Plain text without binary encoding

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-125

Data Type:

binary

Cardinality:

0..1

Requirement:

Optional

XML Implementation

UBL 2.1 Syntax
/Invoice/cac:AdditionalDocumentReference[not(cbc:DocumentTypeCode="130")]/cac:Attachment/cbc:EmbeddedDocumentBinaryObject
CII (UN/CEFACT) Syntax
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument[ram:TypeCode="916"]/ram:AttachmentBinaryObject

Validation Rules

BR-CL-24

BR-CL-24

BR-DE-22

BR-DE-22

Next step

Check whether your XRechnung sets BT-125 correctly

Upload the XML file to the free validator. It applies the KoSIT rules for XRechnung 3.0 and names each finding with its rule ID, for this field for example BR-DE-22, BR-CL-24. Creating a new invoice instead? The converter checks the invoice against the same rules and shows the findings before download.

Free, no account needed. XML file up to 2 MB.

Official sources and tools