---
title: "German E-Invoicing: Mandate, Formats, BT Numbers | Billance"
description: "E-invoicing explained: the legal definition under German VAT law, 2025–2028 deadlines, XRechnung vs. ZUGFeRD and key EN 16931 business terms, plus free tools."
url: "https://billance.de/en/e-invoicing-basics"
language: "en"
---

E-invoicing knowledge

# E-invoicing: basics, formats and mandatory fields

Last updated: 31 October 2026

An e-invoice is a structured data record a computer can read without anyone retyping it. A PDF sent by email does not qualify. This page explains the legal definition, the deadlines through 2028, the difference between XRechnung and ZUGFeRD, and how an invoice is built from business terms. You can use it as a reference or to plan the switch in your business.

[Start for free](https://billance.de/en/pricing) [Download Billance](https://billance.de/en/download)

## At a glance

- Legal basis

  § 14 UStG, EN 16931

- Receiving required

  since 1 Jan 2025

- Common formats

  XRechnung, ZUGFeRD

- Retention

  generally 8 years

## What is an e-invoice?

An e-invoice is issued, transmitted and received in a structured electronic format that enables electronic processing. In practice this means formats that follow the European standard EN 16931. Other agreed formats are permitted as long as they allow the mandatory VAT details to be extracted correctly and completely.

The difference is who the invoice is readable by. A conventional PDF is made for the human eye: a computer sees only text at image positions and has to guess the amounts through character recognition, or someone retypes them. A genuine e-invoice, by contrast, is an XML data model in which every piece of information sits in a defined field, its business term. The recipient system therefore finds the invoice number, the VAT rate and the amount due in exactly the same place as in every other e-invoice, and can check and post them without a break in the media chain.

For you as the issuer, little changes. You enter the same information as before, and your software also produces the structured file from it.

### Other invoices and e-invoices compared

Until the end of 2024, any invoice sent electronically counted as an electronic invoice, a plain PDF included. Since 1 January 2025 German VAT law distinguishes between the structured e-invoice and the "other invoice", which covers paper, image files, and the familiar PDF.

| Aspect | Other invoice | E-invoice per EN 16931 |
| - | - | - |
| Format | Paper, image and text files such as `.pdf`, `.jpg` or `.docx` | XML structure such as XRechnung, or a hybrid PDF such as ZUGFeRD |
| Machine processing | No, requires character recognition or manual entry | Yes, the data fields are read directly |
| Legal classification | Permitted during the transitional rules and in the statutory exceptions | Receiving mandatory since 2025, issuing phased in |
| Recipient consent | Paper needs none, a plain PDF does | Not required for mandatory domestic B2B transactions |
| Retention | Analogue or manually digitised | Keep the structured original electronically and unaltered |

### Why now? The European context (ViDA)

E-invoicing is part of a larger change. Under the EU initiative "VAT in the Digital Age" (ViDA), a union-wide digital reporting system for cross-border B2B transactions is to be in place by 2030. Structured invoice data is the technical prerequisite. If you produce it correctly today, what remains later is mostly the transmission channel.

## The German e-invoicing mandate: deadlines and who is covered

The German [B2B e-invoicing mandate](https://billance.de/en/e-invoicing-mandate) covers taxable transactions between domestic entrepreneurs. What matters is the VAT obligation to issue an invoice, the domestic establishment of both parties, and the statutory exceptions. It does not apply to sales to consumers.

Keep the receiving side and the issuing side strictly apart: you have had to be able to receive e-invoices since 1 January 2025, without exception and regardless of your size. Issuing your own e-invoices is governed by transitional rules that depend on your previous-year revenue.

1. from 1 Jan 2025

   ### Everyone must be able to receive

   Every domestic business must be able to accept e-invoices. Formally, an email inbox is enough according to the ministry FAQ; in practice you also need a way to read the XML file, check it and file it traceably.

2. until 31 Dec 2026

   ### General transitional period for issuing

   Issuers may still send paper invoices. A simple electronic format such as a PDF requires the recipient to agree.

3. from 1 Jan 2027

   ### Issuing required above 800,000 euros previous-year revenue

   Businesses with more than 800,000 euros of revenue in the previous year must issue e-invoices for the covered domestic B2B transactions. Below that threshold the transitional rule runs one year longer.

4. from 1 Jan 2028

   ### E-invoicing becomes the default

   The extended deadline for smaller issuers ends too. From then on only the statutory exceptions remain, such as small-value invoices and supplies by small businesses.

| Period | Receiving (B2B) | Issuing (B2B) | Transitional rules and exceptions |
| - | - | - | - |
| from 1 Jan 2025 | Mandatory for all domestic B2B recipients. | Until the end of 2026 the general transitional rule applies: paper, or a simple electronic format with the recipient’s consent. | Paper needs no consent, a plain PDF does. The statutory exceptions remain in place. |
| from 1 Jan 2027 | Mandatory for all. | Generally mandatory above 800,000 euros previous-year revenue. | Up to and including 800,000 euros previous-year revenue the transitional rule runs until the end of 2027. Certain EDI procedures may continue until then. |
| from 1 Jan 2028 | Mandatory for all. | Generally mandatory for the covered domestic B2B transactions. | The statutory exceptions continue to apply, among them supplies by small businesses, small-value invoices up to 250 euros gross, transport tickets and certain VAT-exempt transactions. |

### Special case B2G: invoices to public authorities

Invoices to public bodies are additionally governed by federal or state rules, which predate the B2B mandate. At federal level XRechnung, or an equivalently admissible standard, is generally required, and submission runs through the federal invoice receipt platform. Always follow the buyer’s instructions on the routing identifier, the format and the transmission channel.

## Standards and formats: EN 16931, XRechnung, ZUGFeRD and Peppol

The European standard EN 16931 defines the semantic data model of an electronic invoice: which pieces of information exist, what they are called, and how they relate to each other. It does not prescribe a file format, which is why several formats satisfy the same standard while looking quite different.

- ### EN 16931: the European standard

  Describes the semantic core model with its business terms and business rules. Profiles and national rules may add further requirements on top.

- ### XRechnung: the pure XML format

  The German application specification (CIUS) of the standard, issued in UBL or CII syntax. It carries no visual rendering and is the standard for dealings with public administration.

- ### ZUGFeRD / Factur-X: the hybrid format

  Combines a visible PDF/A-3 file with an embedded XML invoice. The recipient sees a familiar invoice while their software reads the structured data. In B2B this is usually the most convenient route.

- ### Peppol BIS Billing and EDI

  Peppol is less a format than a transmission network with its own profile based on the standard. Classic EDI procedures may continue under certain conditions and once aligned with EN 16931.

| Format | Type | Human readable | Typical use |
| - | - | - | - |
| XRechnung | Pure XML (UBL or CII) | No, only through software or a viewer | Public administration (B2G), federal and state authorities |
| ZUGFeRD from 2.0.1 (suitable profiles) | Hybrid: PDF/A-3 with embedded XML | Yes, in any PDF reader | B2B, retail, services, freelancers |
| Peppol BIS Billing | XML over the Peppol network | No, only through software | Cross-border B2B and B2G exchange |

Which format fits a given transaction depends mainly on what your recipient requires. The detailed comparison lives on the ZUGFeRD and XRechnung page.

## BT numbers: how an e-invoice is built

So that a recipient system can process an invoice without asking questions, every piece of information is assigned to a defined field. EN 16931 calls these fields business terms (BT) and collects them into business groups (BG). Business rules (BR) then specify which fields must appear together and how the totals add up.

That is why error messages from validation portals look like "BR-DE-15" or "BT-10 is missing". The BR number names the rule that was broken, the BT number the field.

| BT number | Name | Required | Meaning |
| - | - | - | - |
| General invoice information | | | |
| [BT-1](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-1-invoice-number) | Invoice number | Yes | Unique identifier of the invoice |
| [BT-2](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-2-invoice-issue-date) | Invoice issue date | Yes | Date the invoice was issued |
| [BT-3](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-3-invoice-type-code) | Invoice type code | Yes | e.g. 380 (commercial invoice), 381 (credit note) |
| [BT-5](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-5-invoice-currency-code) | Invoice currency code | Yes | ISO code, usually EUR |
| [BT-9](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-9-payment-due-date) | Payment due date | Conditional (often relevant) | When payment is due |
| [BT-10](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-10-buyer-reference-leitweg-id) | Buyer reference / Leitweg-ID | Conditional; required in XRechnung | Lets the recipient route the invoice automatically, especially in public administration |
| [BT-13](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-13-purchase-order-reference) | Purchase order reference | Conditional | Order or contract identifier |
| [BT-24](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-24-specification-identifier-customization-id) | Specification identifier | Yes | Identifier of the standard or profile applied |
| Seller (invoice issuer) | | | |
| [BT-27](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-27-seller-name) | Seller name | Yes | Official company name of the issuer |
| [BT-31](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-31-seller-vat-identifier) / [BT-32](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-32-seller-tax-registration-identifier) | Seller VAT / tax identifier | Yes | VAT identification number or tax registration identifier |
| [BT-34](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-34-seller-electronic-address) | Seller electronic address | Conditional | Electronic address with a scheme identifier, such as an email address or a network endpoint |
| [BT-35](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-35-seller-address-street) ff. | Seller postal address | Yes | Street, postcode, city, country |
| [BT-40](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-40-seller-country-code) | Seller country code | Yes | ISO 3166-1 alpha-2 country code, e.g. DE |
| [BT-43](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-43-seller-contact-email) | Seller contact email | Conditional; required in XRechnung | Email address of the contact person |
| Buyer (invoice recipient) | | | |
| [BT-44](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-44-buyer-name) | Buyer name | Yes | Official company name of the recipient |
| [BT-48](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-48-buyer-vat-identifier) | Buyer VAT identifier | Conditional | VAT identification number |
| [BT-49](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-49-buyer-electronic-address) | Buyer electronic address | Conditional | Electronic address with a scheme identifier, such as an email address or a network endpoint |
| BT-50 ff. | Buyer postal address | Yes | Complete address |
| [BT-55](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-55-buyer-country-code) | Buyer country code | Yes | ISO 3166-1 alpha-2 country code, e.g. DE |
| Delivery & invoicing period | | | |
| [BT-72](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-72-actual-delivery-date) | Actual delivery date | Conditional | Date goods were delivered or the service was rendered |
| [BT-73](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-73-invoicing-period-start-date) / BT-74 | Invoicing period start / end | Conditional | Start and end of the invoicing period at document level |
| Payment information | | | |
| [BT-81](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-81-payment-means-type-code) | Payment means type code | Conditional | Code of the payment method, e.g. credit transfer or SEPA direct debit |
| [BT-83](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-83-remittance-information-payment-reference) | Remittance information | Conditional (often relevant) | Payment reference used to match an incoming payment |
| [BT-84](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-84-payment-account-iban) | Payment account / IBAN | Conditional (for credit transfer) | Bank account of the issuer |
| [BT-86](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-86-bic-financial-institution) | BIC | Conditional | Identifier of the payment service provider |
| Document totals & VAT | | | |
| [BT-106](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-106-sum-of-invoice-line-net-amount) | Sum of line net amounts | Yes | Total of all line net amounts |
| [BT-109](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-109-invoice-total-amount-without-vat) | Invoice total without VAT | Yes | Net total after allowances and charges |
| [BT-110](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-110-invoice-total-vat-amount) | Invoice total VAT amount | Conditional | Total VAT in the invoice currency |
| [BT-112](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-112-invoice-total-amount-with-vat-gross) | Invoice total with VAT | Yes | Gross total including VAT |
| [BT-114](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-114-rounding-amount) | Rounding amount | Conditional | Rounding correction applied to the amount due |
| [BT-115](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-115-amount-due-for-payment) | Amount due for payment | Yes | Gross total less prepaid amounts plus rounding |
| [BT-118](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-118-vat-category-code-breakdown) | VAT category code | Yes | Category in the VAT breakdown, e.g. S, Z, E, AE or K |
| Invoice lines | | | |
| [BT-126](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-126-invoice-line-identifier) | Invoice line identifier | Yes | Unique identifier within the invoice |
| [BT-129](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-129-invoiced-quantity) | Invoiced quantity | Yes | Quantity of goods or services invoiced |
| [BT-130](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-130-invoiced-quantity-unit-code) | Unit of measure code | Yes | Code per UN/ECE Recommendation 20/21, e.g. C62, HUR or DAY |
| [BT-131](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-131-invoice-line-net-amount) | Invoice line net amount | Yes (per line) | Net amount of the individual invoice line |
| [BT-146](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-146-item-net-price) | Item net price | Yes | Net price relative to the price base quantity |
| [BT-151](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-151-invoiced-item-vat-category-code) / [BT-152](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-152-invoiced-item-vat-rate) | VAT category & rate | Conditional | VAT treatment of the invoice line |
| [BT-153](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-153-item-name) | Item name | Yes | Name of the goods or service |
| [BT-154](https://billance.de/en/e-invoicing-basics/bt-numbers/bt-154-item-description) | Item description | Conditional | Additional description of the goods or service |
| BT-157 | Item standard identifier / GTIN | Conditional | Item identifier from a registered scheme, such as a GTIN |

[Browse the BT number index](https://billance.de/en/e-invoicing-basics/bt-numbers)

### Further fields that appear depending on the case

- ### BT-20: payment terms

  Payment terms in plain text, early-payment discounts and deviating arrangements.

- ### BT-42 / BT-43: seller contact

  Telephone number and email address of the contact person; XRechnung requires BT-43.

- ### BT-92 / BT-107: document level allowances

  A single document-level allowance and the sum of all allowances.

- ### BT-116 ff.: VAT breakdown

  Taxable base, rate and amount per VAT category. This is the most common source of errors on invoices with mixed rates.

- ### BT-134 / BT-135: line invoicing period

  Relevant for recurring services such as maintenance, rent or subscriptions.

- ### BT-7 / BT-72: tax point and delivery date

  A deviating VAT point in time and the actual delivery date.

This overview is a selection from the semantic core model, not a complete list. How binding a field is depends on the invoice type, the profile in use and the national specification. XRechnung makes more fields mandatory than the bare standard does.

## What the change delivers in day-to-day work

Structured invoice data simplifies processing. How much depends on your current workflow and on how well the systems involved are connected. The points below describe where the difference usually appears.

- ### Less data entry

  Electronic delivery saves paper, printing and postage; above all it removes the retyping of incoming invoices. How much time that saves depends on the process you have today.

- ### Direct data import

  Compatible systems read the invoice data directly. That reduces manual entry and follow-up questions; reviewing and approving the invoice remains your job.

- ### Fewer transcription errors

  Structured data and formal validation catch transposed digits and missing mandatory fields before the invoice leaves the building.

- ### Traceable filing

  E-invoices can be organised digitally and compactly. Billance supports you with local storage, an archive and backups; proper retention and process documentation remain part of your own operations.

- ### Faster incoming payments

  An invoice that lands directly in the recipient’s approval flow is paid earlier on average than one that has to be captured first, which directly helps your liquidity.

- ### Groundwork for ViDA

  Producing standard-compliant invoice data today gives you the basis for the European reporting duties that are coming.

## Creating an e-invoice: the workflow in four steps

With the right software, the path to an e-invoice barely differs from writing an invoice the way you always have. What is new is mainly steps two and three, validation and format.

1. ### Enter the invoice data

   Fill in the usual details: seller and buyer including VAT identifiers, line items, prices and tax rates. For public buyers, the routing identifier they give you goes into the buyer reference (BT-10).

2. ### Validate formally against EN 16931

   Billance checks in the background whether the mandatory fields are filled and whether the tax and total calculations add up. Formal checks do not replace the professional and tax review.

3. ### Choose a format and generate it

   For public authorities you produce an XRechnung as XML; for business customers a ZUGFeRD hybrid PDF is usually the better fit. Existing PDF invoices can be converted into an e-invoice format.

4. ### Send and retain

   Email is the most common route. Afterwards keep the structured original unaltered and file it traceably in your invoice management.

## Check, read and unpack e-invoices right away

You do not need to install anything to work with an e-invoice. The three tools below run entirely in your browser: your invoice file is never sent to a server, there is no account and no limit.

- [View an e-invoice Open an XRechnung XML or a ZUGFeRD PDF and read parties, line items, taxes and totals in a clear layout.](https://billance.de/en/view-e-invoice)
- [Validate an e-invoice A validation report covering XML schema, EN 16931, XRechnung and Peppol, with findings that point at BT and BR numbers.](https://billance.de/en/validate-e-invoice)
- [Extract XML from an e-invoice Inspect and download the embedded invoice XML from one or many ZUGFeRD or Factur-X PDF files.](https://billance.de/en/extract-xml-from-e-invoice)

## Frequently asked questions about e-invoicing

The questions that come up most often in practice, from the PDF question to retention.

### Is a plain PDF still acceptable as an e-invoice?

Since 2025 a plain PDF is an "other invoice", not a structured e-invoice. It remains permissible during the transitional periods and in the statutory exceptions, for example for supplies by small businesses. There is therefore no blanket PDF ban from 2028 either. A ZUGFeRD PDF with suitable structured XML, on the other hand, can be an e-invoice.

### What is the difference between XRechnung and ZUGFeRD?

XRechnung is a pure XML file with no visual rendering and is the standard for dealings with public authorities. ZUGFeRD combines a readable PDF with embedded XML data and is widespread in B2B because the recipient can open the invoice as usual. Both rest on EN 16931; which format fits is dictated by the recipient.

### Does the mandate apply to small businesses under § 19 UStG?

Small businesses have had to be able to receive e-invoices since 2025, without exception. For their supplies exempt under § 19 (1) UStG they may, under § 34a UStDV, continue to issue other invoices even after the general transitional periods. Voluntary e-invoices remain possible, and separate B2G requirements may apply alongside.

### Do I need a Leitweg-ID for B2B invoices?

You do not need an official routing identifier in purely B2B exchange. The corresponding field is the buyer reference BT-10, and a format such as XRechnung may still require it. In that case you enter the reference your recipient specifies. BT-24 is something else: the identifier of the specification in use.

### How must e-invoices be archived?

Invoices generally have to be retained for eight years. For an e-invoice, at least the structured part must be preserved electronically, intact and in its original form; a printout alone is not enough. For ZUGFeRD, keeping the complete PDF/XML file is advisable. Proper filing and process documentation are part of your own operations.

### Do I have to consent to receiving an e-invoice?

No consent from the recipient is required for mandatory domestic B2B e-invoices. During the transitional periods a paper invoice may be issued without consent, whereas another electronic invoice such as a plain PDF does require it.

### Can e-invoices simply be sent by email?

Yes, email is the simplest and most common transmission route. Alternatively, e-invoices can be provided through download portals, web uploads or transmission networks such as Peppol. In B2G the buyer specifies the route.

### What happens if I issue an invoice in the wrong format?

Where an e-invoice is required, you should correct an invoice issued in the wrong format. What follows for the recipient’s input VAT deduction depends on the individual case and the evidence available; an automatic, final loss cannot be inferred. Clarify such cases with your tax adviser.

### Does the mandate apply to invoices abroad?

The German B2B mandate presupposes that both the supplier and the recipient are established in Germany. Invoices to or from abroad are not covered by it, but must comply with the relevant national or European rules, and the same principle is spreading there too.

### Which formats does Billance produce?

Billance creates XRechnung as CII or UBL XML, EN16931 CII XML, and ZUGFeRD hybrid PDFs in the EN16931/Comfort, XRechnung and Extended profiles. Formal checks accompany creation. A UBL export alone guarantees neither acceptance by every recipient nor transmission over the Peppol network.

## Sources and further reading

The statements on this page rest on the publicly available publications below. In case of doubt, the original text governs.

- [E-invoicing: questions and answers on the B2B rollout](https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html) (German Federal Ministry of Finance)
- [German VAT Act § 14: issuing invoices](https://www.gesetze-im-internet.de/ustg_1980/__14.html) (Federal Office of Justice, Gesetze im Internet)
- [XRechnung: standard, specification and validator configuration](https://xeinkauf.de/xrechnung/) (KoSIT (German coordination office for IT standards))
- [ZUGFeRD and Factur-X: format specification and profiles](https://www.ferd-net.de/standards/zugferd) (FeRD (Forum elektronische Rechnung Deutschland))
- [EN 16931: semantic data model of the electronic invoice](https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467108661/European+Standard+and+Specifications) (European Commission, Digital Building Blocks)
- [VAT in the Digital Age (ViDA)](https://taxation-customs.ec.europa.eu/taxation/vat/vat-digital-age-vida_en) (European Commission)

This article reflects publicly available information as of the date shown and is not tax or legal advice. What governs are the statutory rules, the letters issued by the German Federal Ministry of Finance and the requirements of your invoice recipient.

## Read on

### Step by step in the help centre

The help articles walk through the same workflow as step-by-step instructions, including all fields, buttons and special cases.

- [BT Numbers: What Do They Mean?](https://billance.de/en/help/help-center/bt-numbers-en-16931-explained)
- [Required Data for an E-Invoice](https://billance.de/en/help/help-center/mandatory-e-invoice-fields-en-16931)
- [Leitweg ID / Buyer Reference](https://billance.de/en/help/help-center/leitweg-id-and-buyer-reference)
- [Validate E-Invoices](https://billance.de/en/help/help-center/validate-e-invoices-and-fix-errors)

### Try it right away

- [Create e-invoices](https://billance.de/en/features/create-e-invoices)
- [Validation](https://billance.de/en/features/validation)
- [Convert invoices](https://billance.de/en/features/convert-invoices)

### Related guides

[ZUGFeRD & XRechnung](https://billance.de/en/zugferd-and-xrechnung) [E-invoicing mandate](https://billance.de/en/e-invoicing-mandate) [Features](https://billance.de/en/features)

## Ready for e‑invoices?

Start with Billance and create your first e-invoices in just a few minutes.

[Start for free](https://billance.de/en/pricing) [Download software](https://billance.de/en/download)
