Regional spotlight
Formats? Mandates?
We've got you covered!
-
Overview of B2G, B2B and B2C e-invoicing in Germany. -
Key formats, networks and channels you may need to support. -
High-level regulatory and compliance considerations.
e-invoicing in Germany
Germany is introducing mandatory e-invoicing in phases. Starting from 1st of January 2025, all German companies have been required to be able to receive e-invoices. The obligation to send e-invoices will follow gradually: starting 1st of January 2027 for large and medium-sized companies, and from 1st of January 2028 for all companies, regardless of size.
German company account registration
When registering a new German company via the API, the VAT number must be used as the company identifier. At the moment, company registration requires the vendor to have KYC approval from Maventa. Contact Maventa support to get started.
| Identifier | Description | Format | Validation |
|---|---|---|---|
| VAT number | German VAT identifier (Umsatzsteuer-Identifikationsnummer) | DE123456789 |
Structural validation via VIES |
Sending in Germany
Supported delivery channels in Germany
For B2B and B2G, sending in Germany is currently supported in the following priority order: through Maventa’s internal network and through the Peppol network. Email and print delivery are also available as fallback options. Printing is currently handled through the Finnish production facility, with a local German print solution planned (timeline TBD).
For B2C, invoices are delivered via email and print only.
Receiving in Germany
In Germany, companies can receive invoices through different channels. If a company has activated e-invoice receiving, they can receive invoices via Maventa’s internal network. Additionally, if the company is registered with Peppol, Peppol receiving is available.
| Address Type | Description | Example address | Activation Requirement |
|---|---|---|---|
| Peppol address | Official identifier for the Peppol network. Uses the VAT number with scheme 9930. |
9930:de811000000 | Created when the company registers to receive from Peppol |
Scanning
Scanning is available in Germany via the AutoScan solution.
For step-by-step instructions on enabling receiving, registering for Peppol, and setting up scanning, see the invoice receiving integration guide.
Accounts receivable services
Accounts receivable services for Germany are coming at a later date (timeline TBD).
Ropo Reminder & Collection will be available for German companies, offering reminder and debt collection services through Ropo. The service allows you to transfer overdue invoices to Ropo for reminder handling and collection directly through the Maventa API. For more details on how the service works, see the Accounts receivable section in the Integration Guide.
Peppol SMP registration
When a German company registers to receive invoices via Peppol through Maventa, the following document types are registered in the SMP (Service Metadata Publisher). These registrations determine which document formats the company can receive over the Peppol network.
Peppol BIS Billing 3.0
The standard Peppol BIS Billing 3.0 profiles are registered for cross-border invoicing. Peppol BIS must be used when sending invoices to or from Germany across national borders.
Peppol BIS Billing 3.0 — Invoice
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
Peppol BIS Billing 3.0 — Credit Note
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 3.0
In addition to the standard Peppol BIS profiles, German companies are registered with XRechnung profiles for domestic traffic. XRechnung is the German national CIUS (Core Invoice Usage Specification) of EN 16931, required for public sector invoicing in Germany.
XRechnung 3.0 — Invoice (UBL)
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 3.0 — Credit Note (UBL)
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 3.0 — Invoice (CII)
DocumentIdentifier
urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100::CrossIndustryInvoice##urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0::D16B
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 2.3
The previous XRechnung version is also registered to ensure compatibility with senders still using the older version.
XRechnung 2.3 — Invoice (UBL)
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 2.3 — Credit Note (UBL)
DocumentIdentifier
urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3::2.1
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
XRechnung 2.3 — Invoice (CII)
DocumentIdentifier
urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100::CrossIndustryInvoice##urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3::D16B
ProcessIdentifier
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
e-invoicing formats used in Germany
| Format | Standard | Notes |
|---|---|---|
| Peppol BIS Billing 3.0 | EN16931 | Used for Peppol exchanges |
| XRechnung | EN16931 | German national format, used in domestic Peppol traffic |
| ZuGFeRD | EN16931 | Hybrid format (PDF with embedded XML). Support for sending as email attachment planned (timeline TBD) |