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
PDF readiness
Source data readiness
Attachments and service descriptions
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-14
BR-DE-15
BR-DE-16
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-DE-19
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-17
BR-DE-18
BR-DE-20
BR-DE-21
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
ZUGFeRD Profiles
MINIMUM
BASIC WL
BASIC
EN 16931
EXTENDED
Compare formats and tools
Comparisons
XRechnung vs ZUGFeRD
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-113

Reference

Markdown export

BT-113 Paid Amount

The sum of amounts which have been paid in advance for goods and services covered by the Invoice. This amount is deducted from the Invoice total amount with VAT (BT-112) to calculate the Amount due for payment (BT-115).

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#

The sum of amounts which have been paid in advance for goods and services covered by the Invoice. This amount is deducted from the Invoice total amount with VAT (BT-112) to calculate the Amount due for payment (BT-115).

Taxes and totals

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

Quick actions

Validate XMLConvert invoice

In plain language#

The sum of amounts which have been paid in advance for goods and services covered by the Invoice. This amount is deducted from the Invoice total amount with VAT (BT-112) to calculate the Amount due for payment (BT-115).

The sum of amounts which have been paid in advance for goods and services covered by the Invoice. This amount is deducted from the Invoice total amount with VAT (BT-112) to calculate the Amount due for payment (BT-115).

Used when advance payments, deposits, or partial payments have been made before the invoice date. Common in German business practice for construction contracts, large orders, or service agreements where partial payment is required upfront.

What you usually enter here#

Decimal number with up to 2 decimal places, non-negative

Typical valid values include: 500.00, 1190.00, 0.00, 999999.99

Optional according to EN 16931-1. Must be in the same currency as BT-5 (Invoice currency code). When provided, affects the calculation of BT-115: BT-115 = BT-112 - BT-113 + BT-114.

What goes wrong often#

Avoid values like: -500.00, 500,00, 5.00.00, advance

Relevant rule codes: BR-CO-16, BR-DEC-16

Examples in context#

Used when advance payments, deposits, or partial payments have been made before the invoice date. Common in German business practice for construction contracts, large orders, or service agreements where partial payment is required upfront.

Optional according to EN 16931-1. Must be in the same currency as BT-5 (Invoice currency code). When provided, affects the calculation of BT-115: BT-115 = BT-112 - BT-113 + BT-114.

Valid Examples#

Use these points as the practical checks for this section.

  • 500.00
  • 1190.00
  • 0.00
  • 999999.99

Invalid Examples#

Use these points as the practical checks for this section.

  • -500.00
  • 500,00
  • 5.00.00
  • advance

Related Fields#

Used when advance payments, deposits, or partial payments have been made before the invoice date. Common in German business practice for construction contracts, large orders, or service agreements where partial payment is required upfront.

BT-112 Invoice Total Amount With VAT
BT-115 Amount Due for Payment
BT-114 Rounding Amount
BT-5 Invoice Currency Code

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

Data Type:

amount

Cardinality:

0..1

Requirement:

Optional

Since Version:

Optional in all XRechnung versions

XML Implementation#

UBL 2.1 Syntax
/Invoice/cac:LegalMonetaryTotal/cbc:PrepaidAmount
CII (UN/CEFACT) Syntax
/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:TotalPrepaidAmount

Validation Rules#

BR-CO-16

BR-CO-16

BR-DEC-16

BR-DEC-16

Why the standard cares about this field#

Business Context

Used when advance payments, deposits, or partial payments have been made before the invoice date. Common in German business practice for construction contracts, large orders, or service agreements where partial payment is required upfront.

Legal Requirement

Optional according to EN 16931-1. Must be in the same currency as BT-5 (Invoice currency code). When provided, affects the calculation of BT-115: BT-115 = BT-112 - BT-113 + BT-114.

FAQ#

When should BT-113 be used?

BT-113 should be used when advance payments, deposits, or partial payments have been made before invoicing. This includes down payments for orders, security deposits, or installment payments for services or goods.

How does BT-113 affect the amount due for payment?

BT-113 reduces the amount due for payment. The formula is: BT-115 (Amount due) = BT-112 (Invoice total with VAT) - BT-113 (Paid amount) + BT-114 (Rounding amount). If BT-113 equals BT-112, the amount due becomes zero.

What currency should be used for BT-113?

BT-113 must be expressed in the same currency as specified in BT-5 (Invoice currency code). The currency cannot differ from the invoice currency.

Can BT-113 exceed the invoice total amount?

While technically possible, BT-113 should not normally exceed BT-112 (Invoice total with VAT). If it does, BT-115 (Amount due) becomes negative, indicating the customer has overpaid and may be entitled to a refund.

How are advance payments documented in German business practice?

In German business practice, advance payments are typically documented through separate advance payment invoices (Abschlagsrechnungen) or payment confirmations. These documents should be referenced when using BT-113, and the VAT treatment must comply with German tax regulations.

What validation rules apply to BT-113?

BT-113 must follow BR-DEC-16 (maximum 2 decimal places) and BR-CO-16 (proper calculation with BT-115). The amount must be mathematically consistent with the payment calculation formula.

Official sources and tools#

KoSIT Validator
Invoice Converter
XRechnung Standard
Test Suite
BT-112BT-114
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

Helping businesses across Europe convert invoices to XRechnung and other e-invoice formats with validation support. Review edge cases before submission.

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