From 2027 onwards, all companies in Germany must be able to send e-invoices in the B2B sector – the E-invoicing obligation This also applies to outgoing invoices. GOpus® eInvoice automates the entire process: from the SAP invoice to its conversion into the appropriate format. E-invoice format until dispatch to the recipient.
The challenge: Sending e-invoices from SAP
Creating invoices in SAP is the easy part. The real challenge begins afterward: What format does the recipient expect? Which channel should be used to deliver the invoice? And how do you ensure that every e-invoice complies with the EN 16931 standard?
Each recipient expects a different format: ZUGFeRD, XRechnung, Peppol, Factur-X
Without automation, every invoice has to be manually formatted correctly.
Email, Peppol, ZRE portal, ePost – each channel has its own requirements.
Incorrect e-invoices are rejected by the recipient – payment delays.
Invoice generation with GOpus® eInvoice: 5 steps
GOpus® eInvoice integrates directly into the SAP invoicing process. From document creation to dispatch, everything runs automatically – without media breaks or manual intervention.
The invoice is created in SAP as usual – in FI, SD, MM or RE/FX. The process remains unchanged for the user.
GOpus® eInvoice uses the recipient mapping to recognize the desired format and automatically converts the SAP document – into ZUGFeRD, XRechnung, Factur-X or Peppol BIS 3.0.
Before being sent, each e-invoice is automatically validated against the EN 16931 standard. Missing mandatory fields, invalid tax rates, or formatting errors are detected and reported.
The invoice will be delivered via the specified shipping channel: by email, via the Peppol network, the ZRE/OZG portal (B2G) or via ePost.
Every e-invoice sent is archived in compliance with GoBD regulations. A complete transmission log documents the time, format, channel, and validation status.
Recipient mapping: The right format for every customer
Not every business partner expects the same format. GOpus® eInvoice solves this problem through the... Receiver mapping: For each customer, SAP stores which e-invoice format and which shipping channel is used – fully configurable, without SAP development.
| Receiver type | format | channel |
|---|---|---|
| B2B customers (Germany) | ZUGFeRD EXTENDED or XRechnung | |
| Public sector clients (B2G) | XRechnung | ZRE / OZG Portal |
| International customers (EU) | Peppol BIS 3.0 | Peppol network |
| French customers | Factur-X | Email / Chorus Pro |
| Customers without e-invoicing | PDF (classic) | Email / ePost |
Before and after: Comparison of outgoing invoices
| criterion | Without GOpus® | With GOpus® eInvoice |
|---|---|---|
| Format conversion | Manual / external tool | Automatically per receiver |
| Validation | None / subsequently | EN 16931, before shipping |
| Shipping channels | Single / manual | Email, Peppol, ZRE, ePost |
| Archiving | Manual / uncertain | GoBD-compliant, automatically |
| Receiver mapping | Unavailable | Configurable per debtor |
| SAP integration | Export → external tool | Native in SAP, no media break |
Supported shipping channels
Delivery as an email attachment – ZUGFeRD PDF or XRechnung XML. The email address is taken from the SAP customer master data.
🌐 Peppol Network
Direct shipping via the Peppol network to national and international recipients – automatic delivery to the registered Peppol ID.
🏛 ZRE / OZG Portal
XRechnungen to public sector clients via the Central Invoice Receipt Platform (ZRE) or country-specific OZG portals.
💬 ePost / Print channel
For recipients who do not yet accept e-invoices: automatic fallback to print or ePost – from the same workflow.
Ready for automated invoice delivery?
Our SAP experts will show you in a live demonstration how GOpus® eInvoice automates the invoice output in your SAP system – from document to dispatch.
Request a live demonstration
English 
German