Skip to main content
Invoice-Converter.comInvoice-Converter
BlogPricing
Convert InvoiceConvert
Convert
⌘K
Documentation overview
Understand formats and standards
Compliance Guides
XRechnung Standard
ZUGFeRD Format
PDF/A-3 for ZUGFeRD
CII Cross Industry Invoice
UBL Universal Business Language
DIN EN 16931-1 Standard
PEPPOL Network
Country and regulatory rules
EU E-Invoicing Mandate
EU E-Invoicing
EU e-invoicing in 2026: what to implement (and why)
EU top markets playbook (DE, FR, IT, ES, PL, NL)
PEPPOL in the EU: how exchange actually works
CTC/clearance and portals in the EU: how to build reliable integrations
Country Guides
Germany
France
Italy
Spain
Poland
Netherlands
Belgium
Austria
Denmark
Sweden
Finland
Fix validation and submission issues
Leitweg-ID Validation
Support playbooks
Support
Why invoices need review
API errors
API automation
Handling schema errors
Review validation help
Support
Missing information
Buyer reference
Payment and IBAN
VAT and reverse charge
Totals and rounding
Prepayments
Line items
ZUGFeRD PDF warnings
Validation playbooks
Observed validation fixes
Due date or terms
Bank transfer IBAN
PDF/A-3 readiness
VATEX exemption reason
Review vs download
Public test invoice fixture library
Valid XRechnung UBL basic invoice
Invalid XRechnung missing payment terms
Factur-X/ZUGFeRD EN 16931 CII XML
XRechnung rounding and IBAN edge case
KoSIT Validator Errors
ERROR
BR-DE-1
BR-DE-2
BR-DE-3
BR-DE-4
BR-DE-5
BR-DE-6
BR-DE-7
BR-DE-8
BR-DE-9
BR-DE-10
BR-DE-11
BR-DE-12
BR-DE-13
BR-DE-14
BR-DE-15
BR-DE-16
BR-DE-17
BR-DE-18
BR-DE-19
BR-DE-20
BR-DE-21
BR-CO-3
BR-CO-4
BR-CO-9
BR-CO-10
BR-CO-11
BR-CO-13
BR-CO-14
BR-CO-15
BR-CO-16
BR-CO-17
BR-CO-25
BR-CO-26
BR-S-1
BR-S-5
BR-S-8
BR-61
BR-AE-02
BR-AE-10
BR-E-01
BR-E-05
BR-05
BR-22
BR-23
BR-24
BR-25
BR-26
BR-47
BR-57
BR-DE-22
BR-DE-30
BR-DE-31
PEPPOL-EN16931-R001
PEPPOL-EN16931-R010
PEPPOL-EN16931-R020
PEPPOL-EN16931-R046
PEPPOL-EN16931-R120
PEPPOL-EN16931-R130
WARNING
BR-DE-26
BR-DE-27
BR-DE-28
Look up reference data
Glossary
E
EN 16931
E-reporting
e-Factura RO
EAS (Electronic Address Scheme)
ebInterface
C
CIUS
CII
Code list
Credit note
Contract reference
Chorus Pro
Codice Destinatario
X
XRechnung
XML Schema (XSD)
XML
Z
ZUGFeRD
F
Factur-X
Finvoice
U
UBL
Unit code
P
PEPPOL
PEPPOL BIS
Participant ID
PDF/A-3
Payment means
Purchase order (PO)
PDP (Plateforme de Dématérialisation Partenaire)
A
Access Point
Allowance / charge
S
SMP
SML
Schematron
SDI (Sistema di Interscambio)
Svefaktura
L
Leitweg-ID
K
KoSIT
KSeF
KvK number
V
Validation
VAT ID
ViDA
VeriFactu
ViDA Pillar 1: Digital Reporting Requirements
ViDA Pillar 2: Single VAT Registration
ViDA Pillar 3: Platform Economy
B
Business Term (BT)
Business Group (BG)
BIC
R
Reverse charge
Real-time reporting
Real-time invoice reporting (RTIR)
T
Tax category
TicketBAI
I
IBAN
Invoice type code
Invoice line item
ISO 6523
D
Document reference
D-U-N-S Number
Digipoort
Q
QR code payment
G
GLN (Global Location Number)
O
OVT-tunnus
OIOUBL
N
NemHandel
Code Lists
Currency codes (common)
Country codes (common)
VAT category codes
Payment means type codes
Unit of measure codes (common)
Invoice type codes (common in XRechnung)
XRechnung Fields
Invoice basics
BT-1
BT-2
BT-3
BT-5
BT-6
BT-7
BT-8
BT-10
BT-11
BT-12
BT-14
BT-15
BT-16
BT-17
BT-18
BT-19
BT-21
BT-22
BT-23
BT-24
BT-25
BT-26
Delivery and payment
BT-9
BT-13
BT-20
BT-59
BT-60
BT-61
BT-70
BT-71
BT-72
BT-73
BT-74
BT-75
BT-76
BT-77
BT-78
BT-79
BT-80
BT-81
BT-82
BT-83
BT-84
BT-85
BT-86
BT-87
BT-88
BT-89
BT-90
BT-91
Seller details
BT-27
BT-28
BT-29
BT-30
BT-31
BT-32
BT-33
BT-34
BT-35
BT-36
BT-37
BT-38
BT-39
BT-40
BT-41
BT-42
BT-43
BT-62
BT-63
BT-64
BT-65
BT-66
BT-67
BT-68
BT-69
Buyer details
BT-44
BT-45
BT-46
BT-47
BT-48
BT-49
BT-50
BT-51
BT-52
BT-53
BT-54
BT-55
BT-56
BT-57
BT-58
Discounts and charges
BT-92
BT-93
BT-94
BT-95
BT-96
BT-97
BT-98
BT-99
BT-100
BT-101
BT-102
BT-103
BT-104
BT-105
Taxes and totals
BT-106
BT-107
BT-108
BT-109
BT-110
BT-111
BT-112
BT-113
BT-114
BT-115
BT-116
BT-117
BT-118
BT-119
BT-120
BT-121
BT-122
BT-123
BT-124
BT-125
Line items
BT-126
BT-127
BT-128
BT-129
BT-130
BT-131
BT-132
BT-133
BT-134
BT-135
BT-136
BT-137
BT-138
BT-139
BT-140
BT-141
BT-142
BT-143
BT-144
BT-145
BT-146
BT-147
BT-148
BT-149
BT-150
BT-151
BT-152
BT-153
BT-154
BT-155
BT-156
BT-157
BT-158
BT-159
BT-160
BT-161
BT-162
BT-163
BT-164
BT-165
BT-185
BT-186
ZUGFeRD Profiles
MINIMUM
BASIC WL
BASIC
EN 16931
EXTENDED
Compare formats and tools
Comparisons
PDF24 Tools
sevDesk
Integrate and implement
Platform incident help
Support
Temporary unavailable
Missing result
Validation unavailable
Browser errors
Account and rate limits
Credits and subscriptions
Authoritative validation
ERP export validation guides
DATEV
Lexware
SAP Business One
Odoo
Microsoft Dynamics
Trust & Security
Developer API
  1. E-Invoicing Resources
  2. XRechnung Fields
  3. BT-20

Reference

Markdown export

BT-20 Payment Terms

Textual description of the payment terms and conditions. This field provides detailed information about when and how payment should be made, including discounts, penalties, and specific instructions.

Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial sources and tools

Quick answer#

Textual description of the payment terms and conditions. This field provides detailed information about when and how payment should be made, including discounts, penalties, and specific instructions.

Delivery and payment

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

Quick actions

Validate XMLConvert invoice

In plain language#

Textual description of the payment terms and conditions. This field provides detailed information about when and how payment should be made, including discounts, penalties, and specific instructions.

Textual description of the payment terms and conditions. This field provides detailed information about when and how payment should be made, including discounts, penalties, and specific instructions.

Critical for contract compliance, payment processing automation, and establishing clear expectations between trading partners. Helps prevent payment disputes and enables automated payment processing.

What you usually enter here#

Free text with payment instructions and conditions

Typical valid values include: Payment due within 30 days of invoice date, Zahlung innerhalb von 14 Tagen mit 2% Skonto, netto 30 Tage, Net 30 days, 2% discount if paid within 10 days, Zahlung bei Lieferung (Cash on Delivery)

Optional but recommended for commercial transactions to establish legally binding payment conditions and support dispute resolution processes

What goes wrong often#

Avoid values like: , Payment, See contract, As agreed

Relevant rule codes: BR-CO-25

Examples in context#

Critical for contract compliance, payment processing automation, and establishing clear expectations between trading partners. Helps prevent payment disputes and enables automated payment processing.

Optional but recommended for commercial transactions to establish legally binding payment conditions and support dispute resolution processes

Valid Examples#

Use these points as the practical checks for this section.

  • Payment due within 30 days of invoice date
  • Zahlung innerhalb von 14 Tagen mit 2% Skonto, netto 30 Tage
  • Net 30 days, 2% discount if paid within 10 days
  • Zahlung bei Lieferung (Cash on Delivery)
  • Payment by bank transfer within 60 days

Invalid Examples#

Use these points as the practical checks for this section.

  • Payment
  • See contract
  • As agreed

Related Fields#

Critical for contract compliance, payment processing automation, and establishing clear expectations between trading partners. Helps prevent payment disputes and enables automated payment processing.

BT-9 Payment Due Date
BT-81 Payment means type code
BT-82 Payment means text

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

Data Type:

text

Cardinality:

0..1

Requirement:

Optional

Max Length:

500 characters

Since Version:

Optional

XML Implementation#

UBL 2.1 Syntax
/Invoice/cac:PaymentTerms/cbc:Note
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:Description

Validation Rules#

BR-CO-25

BR-CO-25

Why the standard cares about this field#

Business Context

Critical for contract compliance, payment processing automation, and establishing clear expectations between trading partners. Helps prevent payment disputes and enables automated payment processing.

Legal Requirement

Optional but recommended for commercial transactions to establish legally binding payment conditions and support dispute resolution processes

FAQ#

What should be included in payment terms?

Payment terms should include payment deadline, accepted payment methods, early payment discounts, late payment penalties, and any special conditions or instructions.

Can payment terms override the payment due date?

Payment terms provide context and details, but the payment due date (BT-9) takes precedence for automated processing. Both fields should be consistent.

Are early payment discounts common in German business?

Yes, early payment discounts (Skonto) are very common in German business, typically 2-3% for payment within 8-14 days. This should be clearly stated in payment terms.

How do payment terms affect cash flow management?

Clear payment terms enable better cash flow forecasting, reduce payment delays, and allow for strategic use of early payment discounts to improve working capital.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-19BT-21
On this page
Quick answerIn plain languageWhat you usually enter hereWhat goes wrong oftenExamples in contextValid ExamplesInvalid ExamplesRelated FieldsXML mapping and field factsXML ImplementationValidation RulesWhy the standard cares about this fieldFAQOfficial 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.

20,000+ invoices processed
Fast & Secure
Trusted by hundreds

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
  • FAQ
  • Pricing
  • Climate Contribution

Legal

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

Get in Touch

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