Consolidated invoicing, centralized settlement, purchasing groups: Many companies work with more complex invoicing models where a simple individual invoice is insufficient. GOpus® eInvoice supports SAP SD invoice lists – and offers precisely the flexibility that practical applications require.
The challenge: E-invoicing meets complex billing structures
While the switch to e-invoices for simple individual invoices has been well implemented in many cases, practical experience quickly reveals that the truly challenging cases lie elsewhere.
Anyone with Collective billing, Central regulation or Purchasing associations Anyone who works with this system is familiar with the scenario: In the SAP system, several individual invoices are grouped together via an SD invoice list and processed jointly. In addition, there are often specific conditions at the invoice list level that must be correctly taken into account.
This is precisely where a gap has existed: Standard approaches to e-invoice generation are often not designed for this scenario. The result is manual rework, workarounds, or simply a lack of solutions. GOpus® eInvoice closes this gap.
The solution: Two paths – one platform
GOpus® eInvoice builds directly on the existing SAP SD invoice list and now enables two practical variants of e-invoice generation:
- Individual e-invoice per invoice from the invoice list
Each invoice that is part of the SAP SD invoice list is converted separately into an e-invoice. The recipient thus receives a separate electronic invoice document for each underlying SD invoice – in the desired format. This approach is particularly suitable when the individual invoices are sent to different recipients or when the recipient requires document-specific tracking. A single e-invoice from the entire invoice list
2. Alternatively, all invoices from an SAP SD invoice list can be... a single, consolidated e-invoice The relevant invoice data is collected, processed, and output as a single electronic document. This model is suitable when a central invoice is submitted to a regulator, association, or central payer – and the recipient expects a consolidated overview.
Conditions from the invoice list are correctly displayed.
One particularly important aspect: GOpus® eInvoice also takes into account Conditions that are at the invoice list level are stored in the system – and not on the individual SD invoice. This includes, for example... Del credere deductions or del credere conditions, These conditions play a central role in many central settlement and purchasing group scenarios. They are correctly incorporated into the generated e-invoice – regardless of whether it is a single or consolidated e-invoice. This ensures that the electronic document fully and accurately reflects the actual billing situation.
Flexible in format choice – seamlessly integrated into SAP
GOpus® eInvoice generates e-invoices from SAP SD invoice lists in all common and supported e-invoice formats – including XRechnung, ZUGFeRD, and other nationally and internationally relevant formats. This means companies are not tied to a specific format but can respond flexibly to the requirements of their customers and business partners.
The solution is fully integrated into existing SAP processes. No external systems, data exports, or manual steps are required. Anyone using SAP SD for their invoicing can implement GOpus® eInvoice directly on their existing processes and data.
What this means in practice
The benefits for companies can be summarized in a few key points:
- Flexibility in mapping billing scenarios: Whether it's an individual invoice for each item or a consolidated overall document – the decision lies with the user, not the system.
- Support for complex SAP SD processes: Collective billing, central settlement and purchasing associations are supported in a practical way and without workarounds.
- Correct consideration of invoice list conditions: Credit risks and similar conditions are processed automatically and correctly.
- Format freedom: E-invoices are created in the desired format – adapted to the requirements of the respective recipient.
- No system breaks: The solution works natively in the SAP environment and requires no additional infrastructure.
Conclusion: E-invoicing is also suitable for complex cases.
The mandatory use of e-invoicing makes no exceptions for complex billing models. This makes it all the more important that the solution used can keep pace with the realities of your own processes. GOpus® eInvoice, with its support for SAP SD invoice lists, demonstrates that a practical e-invoicing solution must also function where it is not trivial. Not only for standard cases, but also for the special cases that frequently occur in daily business and have often required explanation until now.
Do you use SAP SD invoice lists and want to know how GOpus® eInvoice integrates them into your e-invoicing process? Contact us – we will gladly show you how the solution works specifically in your environment.
Further information about GOpus® eInvoice can be found on our website.
English 
German