E-invoicing in Germany 2027: impact on Revenue Cloud
From 1 January 2027, German companies with more than €800,000 turnover in 2026 must send domestic business customers e-invoices, and from 1 January 2028 the duty applies to every domestic B2B invoice. An e-invoice is a structured file under EN 16931, such as XRechnung or ZUGFeRD; a PDF by email no longer counts. If your invoices come from SAP, this is an SAP project. If they come from Revenue Cloud Billing, you need a plan: Salesforce documents invoice PDFs, and I found no native EN 16931 output in its documentation as of October 2026. Ask Salesforce in writing and choose a route before the first invoice leaves Salesforce.
What does the German e-invoicing duty require?
The rules come from the German VAT Act and letters from the Federal Ministry of Finance. The IHK Köln1 and the IHK Stuttgart2 summarise them. The timeline for domestic B2B invoices:
- Every domestic business must be able to receive e-invoices. Paper and, with consent, PDF are still allowed for sending.
- Companies with more than €800,000 turnover in 2026 must issue e-invoices. Smaller companies may still send other invoices. EDI invoices remain allowed with the recipient's consent in 2027.
- E-invoices for all domestic B2B invoices.
An e-invoice is an invoice “issued, transmitted and received in a structured electronic format” that follows EU directive 2014/55/EU and therefore the European standard EN 16931. According to the IHK Stuttgart, the ministry accepts XRechnung and ZUGFeRD from version 2.0.1, among others. A PDF invoice sent by email has counted as an “other invoice” since 2025.
Exceptions include invoices to consumers, small invoices up to €250, tickets and certain tax-exempt transactions. The law does not prescribe the channel: email, an interface or a portal download are all allowed. This is a summary for planning, not tax advice. Your tax advisor should confirm the details, including the letter of October 2026.
Almost every domestic invoice of a manufacturer is affected
Every invoice to a business customer resident in Germany: machines, spare parts, service visits, maintenance contracts and subscriptions. For a machine builder with German dealers and end customers, that is most of the domestic volume. Invoices to customers abroad fall outside the German duty, but other countries have their own rules.
The €800,000 threshold applies per company. A group with several German entities checks each one, which also tells you which legal entities in Salesforce Billing are affected in 2027 and which only in 2028. For a typical machine builder the answer is simple: above the threshold, so the duty starts on 1 January 2027.
What does Revenue Cloud Billing deliver today?
Revenue Cloud Billing creates invoices from billing schedules. Salesforce Help and the Winter ’27 developer documentation file it under Revenue Management, the newer name of the product family, earlier called Revenue Lifecycle Management. According to Trailhead3, you generate a batch of invoice PDFs from an invoice run with “Generate Invoice Documents”, or a single PDF with Flow, Apex or OmniScript, and send posted invoices by email to the bill-to contact. The InvoiceDocument object4 “tracks and displays the status of documents generated for invoices”. The product page5 names “Invoicing Engine & Document Production”.
None of these sources mentions EN 16931, XRechnung, ZUGFeRD or Peppol, and I found no other Salesforce documentation for native e-invoice output as of October 2026. A community post on UnofficialSF6 from October 2025 describes e-invoicing with Revenue Cloud as an extension: a posted invoice publishes a platform event, middleware such as MuleSoft maps the data to a format like UBL or Factur-X/ZUGFeRD, and an external provider delivers it, for example through Peppol. That is one author’s approach, not product documentation.
SAP, an e-invoicing service or a partner app
I see three routes, and the right one depends on where your invoices come from today.
| Route | How it works | When it fits |
|---|---|---|
| Invoice from SAP | Revenue Cloud sends billing data to SAP, and SAP issues the e-invoice | SAP already produces e-invoices and the recurring volume is small |
| E-invoicing service | Billing posts the invoice, middleware maps it to XRechnung or ZUGFeRD, a service validates and delivers it | Billing invoices recurring revenue, and you want one channel for all invoices |
| Partner app | An app in the org creates the structured file from the invoice | An app covers your formats and you accept another vendor in the org |
Invoice from SAP keeps one invoicing system for compliance. SAP offers e-invoicing for Germany in SAP Document and Reporting Compliance7, including XRechnung by email and via Peppol. Ask your SAP team whether it is already licensed and set up. The price: every amendment in Revenue Cloud has to reach SAP before the next invoice run. The trade-offs are in Revenue Cloud Billing or SAP.
An e-invoicing service keeps Billing as the invoicing system. I would choose a service that also handles SAP’s invoices, so customers receive every invoice through the same channel and the same validation. The integration is a normal integration project with an owner, monitoring and error handling, the kind of work I describe under Salesforce integration.
A partner app keeps the logic inside the org, but adds another vendor to every Salesforce release. Check which formats and versions it supports, how it validates, how it handles credit memos and who fixes it when a release breaks something.
Worked example: remote monitoring subscriptions from mid-2027
A machine builder with €60 million turnover invoices machines and spare parts from SAP, which already issues e-invoices. From mid-2027 it plans to invoice remote monitoring subscriptions from Revenue Cloud Billing.
The duty already applies when the first Billing invoice goes out, so there is no transition period for the new process. I would not start Billing invoices with PDFs and fix the format later. Either the subscription invoices run through SAP in the first year, or Billing is connected to the e-invoicing service that SAP’s invoices already use. Which of the two depends on how often subscriptions change, as described in who owns what in quote to cash.
Threshold and invoice source per company
- Threshold per legal entity. Which German companies issue invoices, and is each one subject to the duty from 2027 or 2028?
- Invoice source per revenue type. Which invoices leave Salesforce, which leave SAP.
- Format and channel per customer. XRechnung or ZUGFeRD, email, Peppol or portal, agreed with the main customers.
- Field mapping. Map every mandatory EN 16931 field to a Salesforce field, with your e-invoicing provider or tax advisor.
- Validation and errors. Validate before sending, and name who fixes a rejected invoice.
- Credit memos. Clarify with your tax advisor how credit memos and corrections are issued.
- Archiving. Clarify where the structured file is archived.
- Statement from Salesforce. Written, with the date you received it.
Points 1 and 2 decide whether Billing has to issue e-invoices at all and from when. You need the other points before go-live, and you can start point 8 today. The cost side of invoicing from Salesforce is in Revenue Cloud Billing costs, and the masterclass chapter billing and usage-based pricing puts e-invoicing into the whole quote-to-cash process.
Sources7
- 1IHK Köln (opens in a new tab)ihk.de
- 2IHK Stuttgart (opens in a new tab)ihk.de
- 3Trailhead (opens in a new tab)trailhead.salesforce.com
- 4InvoiceDocument object (opens in a new tab)developer.salesforce.com
- 5product page (opens in a new tab)salesforce.com
- 6UnofficialSF (opens in a new tab)unofficialsf.com
- 7SAP Document and Reporting Compliance (opens in a new tab)blogs.sap.com
Frequently asked questions
When does e-invoicing become mandatory in Germany?
Receiving e-invoices has been mandatory for all domestic businesses since 1 January 2025. Issuing them is mandatory from 1 January 2027 for companies with more than €800,000 turnover in the previous year, and from 1 January 2028 for all domestic B2B invoices.
Is a PDF invoice an e-invoice?
No. Under the German rules an e-invoice is issued, transmitted and received in a structured electronic format that follows EN 16931. A PDF sent by email counts as an other electronic invoice, which is only allowed during the transition period.
Can Revenue Cloud Billing create XRechnung or ZUGFeRD invoices?
I found no Salesforce documentation for native EN 16931, XRechnung or ZUGFeRD output from Revenue Cloud Billing as of October 2026. Salesforce documents invoice PDFs. Ask Salesforce in writing and plan an e-invoicing service or SAP as the route.
Does the German e-invoicing duty apply to export invoices?
The German duty covers domestic B2B transactions between businesses resident in Germany. Invoices to customers abroad fall outside it, but other countries have their own rules, which your tax advisor should check.