E-Invoicing in Germany – A Guide
With the E-Invoicing Ordinance 2020 (E-Rechnungsverordnung), electronic invoices became mandatory for exchanging invoices with public sector clients. In the domestic B2B sector, e-invoicing is introduced in stages from 2025 to 2028, see When are e-invoices mandatory in B2B?.
This guide summarizes important information that is particularly relevant for German companies getting started with e-invoicing:
Basic information
Preliminary considerations
Prerequisites
Setup and use
Frequently asked questions
Information on E-Invoicing
- What is an e-invoice?
-
An electronic invoice is an invoice in the form of a structured, machine-readable file. Unlike a paper invoice or an invoice in PDF format, an e-invoice is created, transmitted, received and processed purely electronically.
In Europe, the use of the XML data format is mandatory for e-invoices. Based on the European standard for electronic invoicing EN16931, each EU member state can develop its own specification.
To ensure the legal certainty of electronic invoices, EN16931 must fully contain all information required by the German VAT Act (Umsatzsteuergesetz). Here you find a mapping table that shows in which EN16931 data field each mandatory information is implemented. In addition, E-Invoice Data Mapping shows which e-invoice fields JustOn Billing & Invoice Management populates with which data by default.
- Which e-invoice formats apply in Germany?
-
In Germany, the E-Invoicing Ordinance defines the invoice formats XRechnung and ZUGFeRD as the standard for electronic invoicing. The standards serve to unify invoice formats and increase security in the exchange of invoice data.
All e-invoice formats structure the invoice content using Business Groups and Business Terms, which are defined by the European standard EN16931. A Business Group is a categorization, for example, "Buyer", "Seller", "Invoice line". A Business Term is an individual parameter within the categorizations, for example, "IBAN" (of the seller), "Quantity" (of an invoice line).
- When are e-invoices mandatory in B2B?
-
For domestic B2B transactions, the German VAT Act introduces the e-invoice obligation in stages:
As of Applies to Obligation 2025-01-01 all businesses Receive e-invoices. Sending paper invoices or, with the recipient's consent, other formats like PDF is still allowed. 2027-01-01 businesses with a total turnover of more than EUR 800,000 in 2026 Send e-invoices 2027-01-01 businesses with a total turnover of up to EUR 800,000 in 2026 Paper invoices or, with the recipient's consent, other formats like PDF are still allowed until 2027-12-31 2028-01-01 all businesses Send e-invoices Invoices exchanged via EDI that do not yet meet the e-invoice requirements remain allowed until 2027-12-31.
An invoice for a service performed in 2026 that is transmitted only in 2027 must generally be an e-invoice, irrespective of the turnover – the EUR 800,000 threshold applies only to services performed in 2027.
This information does not constitute legally effective tax advice. For details, see the application letters of the German Federal Ministry of Finance (BMF) or contact your tax consultant.
Preliminary Considerations for Getting Started With E-Invoicing
Introducing e-invoicing requires careful planning. Before you start, take the following preliminary considerations into account:
(1) Identifying Recipient Group
First, analyze to whom you will send e-invoices:
- B2G – Public sector clients in Germany
-
If you invoice public sector clients in Germany (federal government, federal states, municipalities), e-invoices have been mandatory since the E-Invoicing Ordinance 2020.
- Required format: XRechnung (according to ERechV § 4, exceptions are possible)
- Specific feature: recipients must provide a Leitweg-ID as buyer reference
- Distribution channel: for the federal government Peppol, email or upload to the central invoice receipt platform OZG-RE, in the federal states partly their own portals (see Frequently Asked Questions)
- B2B – Business customers in Germany
-
In domestic B2B transactions, businesses must be able to receive e-invoices since January 2025. Sending e-invoices becomes mandatory in 2027 or 2028, depending on your turnover, see When are e-invoices mandatory in B2B?.
- Possible formats: XRechnung or ZUGFeRD
- Specific feature: the buyer reference must be agreed with the business partner (for example, VAT ID, customer number, order number)
- Distribution channel: email or another agreed exchange procedure
- EU and international
-
Different requirements apply to cross-border invoices within the EU and worldwide.
- Required format: depending on the country – Peppol BIS Billing UBL is recognized throughout Europe
- Specific feature: some EU countries have developed their own e-invoice formats
- Distribution channel: Peppol network for Europe-wide exchange
- Special recipients with specific requirements
-
Some countries, industries or organizations require specific e-invoice formats or transmission channels.
- Required format: as specified by the recipient (possibly country-specific or industry-specific formats via Avalara ELR)
- Specific feature: requirements must be clarified in advance
- Distribution channel: as specified and available (portal, Peppol, Avalara ELR)
(2) Selecting Suitable Formats
Based on your recipient group, select the required e-invoice formats:
| Recipient type | Recommended format |
|---|---|
| German authorities (B2G) | XRechnung UBL |
| German companies (B2B) | XRechnung UBL, ZUGFeRD |
| EU countries | Peppol BIS Billing UBL |
| International recipients | Avalara ELR formats |
Using the formats
JustOn Billing & Invoice Management can create e-invoices in the formats XRechnung UBL, Peppol BIS Billing UBL and ZUGFeRD. For special country-specific or industry-specific formats (mainly outside Germany), the Avalara ELR integration is available. For more information, see E-Invoice Formats.
Note that German law and EU law generally do not oblige senders of e-invoices in the B2B sector to comply with specific format requests of the recipients. Instead, they define standard formats and permit bilateral agreements on the formats to be used, which, however, must generally comply with EN16931.
(3) Defining Workflow
Determine how e-invoices are to be created and sent:
- Workflow 1: Creation + email distribution
-
The e-invoice XML file is created automatically on invoice finalization and sent as an email attachment.
- Suitable for: B2B customers who accept e-invoices by email, and federal public sector clients (email to the OZG-RE)
- Advantages: simple setup, familiar distribution channel
- Configuration: set the e-invoice format on the account, configure email attachments (see Email Attachments)
- Workflow 2: Creation + portal upload
-
The e-invoice is created, downloaded manually and uploaded to a portal.
- Suitable for: authorities requiring a platform, key accounts with their own portals
- Advantages: meets portal requirements, full control
- Configuration: set the e-invoice format on the account
- Workflow 3: Creation + Peppol distribution
-
The e-invoice is transmitted directly to the recipient via the Peppol network.
- Suitable for: EU-wide invoice exchange, recipients in the Peppol network, federal public sector clients (Peppol to the OZG-RE)
- Advantages: secure, standardized transmission, usable throughout Europe
- Precondition: registration as Peppol participant required (contact us)
- Workflow 4: Creation and distribution via Avalara ELR
-
JustOn Billing & Invoice Management prepares the invoice data, Avalara ELR handles the creation and distribution of country-specific or industry-specific e-invoices.
- Suitable for: international invoicing with country-specific or industry-specific requirements (mainly outside Germany)
- Advantages: compliance certainty for many countries, automatic format updates
- Precondition: Avalara ELR contract and integration required
Combinations possible
You can use different workflows in parallel – for example, email distribution for German B2B customers and Peppol for recipients in the EU.
Prerequisites for Creating E-Invoices
Technical prerequisites
-
Software version
To avoid problems with incompatible data and to meet the current requirements for e-invoices, creating and sending e-invoices always requires the latest version of JustOn Billing & Invoice Management.
-
API access
Creating and sending e-invoices requires access to the Salesforce API and therefore at least the Salesforce Enterprise Edition.
All users who create or send e-invoices must be enabled to use the Salesforce API via their profile or a permission set.
-
Heroku platform
JustOn Billing & Invoice Management, which is integrated in Salesforce, serves as the "user interface" for managing electronic invoices and controls the data management. Essential parts of the business logic for creating electronic invoices, however, run on the Heroku-based platform. The dedicated app JustOn Platform integrates the Salesforce and Heroku components.
Therefore, you must enable access to the JustOn Platform app for all relevant user profiles.
- Buyer reference
-
The buyer reference is mandatory information that allows the unique identification of the invoice recipient.
In business with German authorities (B2G scenarios), the buyer reference usually contains the Leitweg-ID.
In B2B scenarios, you must agree on a buyer reference with your business partner. Possible values are, for example, customer number, VAT ID, order number, or combinations like "company name-contract number-order number". Contact your customers to define the buyer references.
Also consider where to maintain the buyer references in Salesforce. We recommend a dedicated field on the account.
- Recipient and sender addresses
-
Every e-invoice needs an e-invoice recipient and an e-invoice sender. This means that companies sending or receiving electronic invoices must have a unique electronic invoice address, which is encoded by a specific address identifier. In general, electronic invoice addresses are subject to the electronic addressing system defined by the European Union, see E-Invoice Address and Scheme.
-
E-invoice recipient address
We recommend using the buyer's VAT ID as the recipient address and maintaining this value in a dedicated field on the account.
Since not every company has applied for a VAT ID and must specify it accordingly, you can alternatively use an email address of the invoice recipient. Some companies have set up a dedicated email address for receiving e-invoices.
-
E-invoice recipient scheme
For electronic invoice addresses, you must specify the corresponding scheme identifier according to the Electronic Address Scheme. We recommend maintaining this value in a dedicated field on the account.
Frequently used identifiers are
Scheme code E-invoice address 9930 German VAT ID 0204 Leitweg-ID EM Email address -
E-invoice sender address and e-invoice sender scheme
We recommend using your VAT ID as the sender address and entering this value in the field
E-Invoice Sender Addressin your business entity. The corresponding scheme code9930must be set accordingly in the fieldE-Invoice Sender Scheme Idin your business entity.Even if you use another sender address for e-invoices, it must comply with the specifications of the Electronic Address Scheme.
-
- Quantity units and unit codes
-
Each invoice line item in an e-invoice must specify a quantity unit, which is defined as the custom setting Quantity Units (see Unit and Unit Code). For the quantity unit, you must also specify a code to ensure a standardized specification. The code must be listed in the UNECE Recommendation No. 20 "Codes for Units of Measure Used in International Trade" or in the UNECE Recommendation No. 21 "Codes for Passengers, Types of Cargo, Packages and Packaging Materials", see UNECE Code List Recommendations.
If you have not used quantity units so far and have no new specific requirements, we recommend defining the unit
Piecewith the unit codeH87.A Configurator package for common quantity units and unit codes is available.
- Business entity
-
In the custom setting Business Entity for your company, the following fields must be filled:
CompanyTax IDCityPostalCodeCountry CodePhoneEmail SenderIBANE-Invoice Sender AddressE-Invoice Sender Scheme Id
- Tax rules
-
Each invoice line item in an e-invoice must specify a tax rate, which is defined via the custom setting Tax Rules (see Tax Rate).
The tax rule must define the tax rate, the business entity and the VAT category code. This code serves to categorize the VAT regulations and is mandatory for electronic invoices. The code must be listed in the code list 5305 of the United Nations Trade Data Interchange Directory (UNTDID), see Duty or tax or fee category code (Subset of UNCL5305).
A Configurator package for the standard tax rules in Germany is available, which includes the VAT category codes.
If your tax rules in JustOn Billing & Invoice Management do not yet include the VAT category code, you can easily add it for the common tax rules. We are happy to support you with this.
Using E-Invoicing Feature
- Setup
-
The steps required to configure your JustOn Billing & Invoice Management instance to support electronic invoicing can differ depending on the use case. In general, however, the setup comprises the following tasks:
To send XRechnung or ZUGFeRD e-invoices by email, follow the E-Invoicing Quickstart, which covers all of these tasks.
-
Setting up software feature
This includes at least the API access and the platform access for the users involved.
-
Preparing source data
See Prerequisites for Creating E-Invoices and Required Fields.
-
- Creation
-
As soon as a format is set in the field
E-Invoice Formaton the invoice (currentlyXRechnung UBL,Peppol BIS Billing UBLor an Avalara ELR country mandate, see E-Invoice Formats), JustOn Billing & Invoice Management automatically creates the corresponding e-invoice XML file on finalization.We recommend setting the e-invoice format manually in a dedicated field (
ON_EInvoiceFormat) on the account if your customer has actively requested an e-invoice.After completing the configuration, use the e-invoicing feature for newly created invoices. This ensures from the start that the invoice record contains all information relevant for creating an e-invoice.
- Validation
- JustOn Billing & Invoice Management automatically validates created e-invoices. This checks whether certain mandatory values are specified.
- Validation report
-
In case of warnings or errors during the e-invoice creation, JustOn Billing & Invoice Management attaches a validation report to the invoice record. This HTML file usually points to data quality problems, like missing fields, wrong data formats, and so on.
Review the validation report to detect possible data quality problems. Use this information to correct the invoice data. As a reference, use Required Fields and E-Invoice Data Mapping. When all relevant fields are filled, create the e-invoice again by clicking Create E-Invoice.
If errors persist, contact us via the support portal.
- Distribution
-
The simplest and immediately available option is the email distribution: the e-invoice XML file is attached to the invoice email, just like you know it from invoices as PDF files.
There are several configuration options to have either both the e-invoice XML file and the PDF file, or only the PDF file, or only the e-invoice attached to the email. We recommend creating the corresponding field
ON_EmailFileTypeson the account. You can have users fill this field or set it automatically via a formula following a specific logic.Of course, you can also download the e-invoice and upload it to portals. For distribution to federal public sector clients, Peppol, email and upload are available, see Frequently Asked Questions.
In addition, you can transmit e-invoices via the Peppol network or Avalara ELR. Using these services, however, requires separate contractual agreements and causes additional costs. Contact us.
- Additional information in e-invoice
-
Your customers may request additional information in the electronic invoice. In this case, you may need to create and fill the corresponding fields.
In such cases, contact us via our support portal. We check this requirement and, if applicable, plan it into our product development.
Frequently Asked Questions
What is XRechnung?

XRechnung is the name of an e-invoice standard valid in Germany. It complies with the European standard EN16931 and is based on a pure XML data model. This makes the invoice fully machine-readable, but it does not contain a human-readable image of the invoice data.
XRechnung files can be created in the UBL and CII syntaxes. These differ and are not directly interchangeable, but can be converted into each other using appropriate tools.
JustOn Billing & Invoice Management creates e-invoices in XRechnung format in UBL syntax. It always supports the current XRechnung version.
What is ZUGFeRD?

ZUGFeRD is a hybrid format. Unlike other supported e-invoice formats (XRechnung UBL or Peppol BIS Billing UBL), ZUGFeRD combines the human-readable PDF format with the machine-readable XML format. The XML file is embedded in the PDF.
What is Peppol?

Peppol is a Europe-wide network for exchanging electronic documents – including e-invoices. Common specifications and standards ensure the interoperability between senders and recipients throughout Europe.
Peppol BIS Billing UBL is another standardized file format for exchanging electronic invoices in Europe.
If you want to use Peppol, you must be registered as a participant in the network. Contact us.
Do I need a Leitweg-ID?
The Leitweg-ID (see ZFB | eRechnung) is one possible value that can be specified as the buyer reference. In general, the buyer reference is a mandatory unique identifier for the recipient of the e-invoice, which can also be the Leitweg-ID.
In B2G scenarios in Germany (invoice exchange with public bodies), the Leitweg-ID is the most common identifier for recipients. It is not mandatory, though – federal states or municipalities can also specify other identifiers. Invoice senders, for their part, do not need a Leitweg-ID.
In the B2B sector, the Leitweg-ID is not required for addressing. Invoice senders and invoice recipients can agree on any other type of identification that is permitted according to the Electronic Address Scheme – for example, VAT ID, customer number or order number.
How do I send e-invoices to public sector clients?
The federal administration receives e-invoices via its central invoice receipt platform OZG-RE. Regardless of the transmission channel, you must register with the OZG-RE as an invoice issuer. The registration is free of charge.
For the e-invoice itself, the following applies:
- Use the format
XRechnung UBL. - Specify the Leitweg-ID of your client as the buyer reference. If the Leitweg-ID is missing in the e-invoice, the OZG-RE rejects it. You find the Leitweg-ID in your contract documents, or you ask your client for it.
The OZG-RE accepts e-invoices via the following transmission channels, which you can serve with JustOn Billing & Invoice Management:
- Peppol
-
In the field
E-Invoice Distribution Channel, set the valuePeppol, and send the e-invoice via Send E-Invoice, see Sending E-Invoices.E-Invoice Recipient Address: the Leitweg-ID of your client, with the value0204in the fieldE-Invoice Recipient Scheme Id- E-invoice sender address: your VAT ID with the address scheme
9930(or your Global Location Number with the address scheme0088)
For distribution via Peppol, you must be registered as a Peppol participant. For details, see Enabling E-Invoice Action.
-
After the registration, the OZG-RE provides you with an individual recipient email address that identifies you as the invoice issuer. In the field
E-Invoice Distribution Channel, set the valueEmail, and send the invoice email to this address.The OZG-RE processes an email only if it meets the following rules – otherwise, it discards the email including all attachments:
- The email contains exactly one e-invoice.
- The email contains no further attachments without structured data – not even the invoice PDF.
To have only the e-invoice XML file attached, set the field
Email File TypestoE-Invoice, see Email Attachments. The subject and text of the email are ignored.The OZG-RE asks not to use no-reply sender addresses. Specify a sender address that can receive replies, and check whether your outgoing emails use
noreply@salesforce.com, see How to removenoreply@salesforce.comfrom sender address?. - Upload
- Download the e-invoice XML file from the invoice record, and upload it manually to the OZG-RE.
For more information, see Übertragungskanäle (transmission channels) on the website of the federal administration.
The federal states implement e-invoicing under their own responsibility. Some operate their own invoice portals, and their requirements – including the assignment of Leitweg-IDs – differ. If you invoice a state or municipal authority, ask your client for the expected transmission channel, see Umsetzung der E-Rechnung in den Bundesländern (implementation of e-invoicing in the federal states).