{"id":5770,"date":"2026-06-04T14:45:32","date_gmt":"2026-06-04T12:45:32","guid":{"rendered":"https:\/\/gopus.de\/?p=5770"},"modified":"2026-06-04T14:49:23","modified_gmt":"2026-06-04T12:49:23","slug":"e-rechnungen-aus-sap-sd-rechnungslisten-einfach-und-flexibel-mit-gopus-einvoice","status":"publish","type":"post","link":"https:\/\/gopus.de\/en\/e-rechnungen-aus-sap-sd-rechnungslisten-einfach-und-flexibel-mit-gopus-einvoice\/","title":{"rendered":"E-invoices from SAP SD invoice lists \u2013 simple and flexible with GOpus\u00ae eInvoice"},"content":{"rendered":"

Consolidated invoicing, centralized settlement, purchasing groups: Many companies work with more complex invoicing models where a simple individual invoice is insufficient. GOpus\u00ae eInvoice supports SAP SD invoice lists \u2013 and offers precisely the flexibility that practical applications require.<\/strong><\/p><\/div>\n\n\n\n

The challenge: E-invoicing meets complex billing structures<\/strong><\/h4><\/div>\n\n\n\n

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.<\/p><\/div>\n\n\n\n

Anyone with Collective billing<\/strong>, Central regulation<\/strong> or Purchasing associations<\/strong> 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.<\/p><\/div>\n\n\n\n

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\u00ae eInvoice closes this gap.<\/strong><\/p><\/div>\n\n\n\n

The solution: Two paths \u2013 one platform<\/strong><\/h4><\/div>\n\n\n\n

GOpus\u00ae eInvoice builds directly on the existing SAP SD invoice list and now enables two practical variants of e-invoice generation:<\/p><\/div>\n\n\n\n

    \n
  1. Individual e-invoice per invoice from the invoice list<\/strong><\/li>\n<\/ol>\n\n\n\n

    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 \u2013 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<\/strong><\/p><\/div>\n\n\n\n

    2. Alternatively, all invoices from an SAP SD invoice list can be... a single, consolidated e-invoice<\/strong> 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 \u2013 and the recipient expects a consolidated overview.<\/p><\/div>\n\n\n\n

    Conditions from the invoice list are correctly displayed.<\/strong><\/h4><\/div>\n\n\n\n

    One particularly important aspect: GOpus\u00ae eInvoice also takes into account Conditions that are at the invoice list level<\/strong> are stored in the system \u2013 and not on the individual SD invoice. This includes, for example... Del credere deductions or del credere conditions<\/strong>, These conditions play a central role in many central settlement and purchasing group scenarios. They are correctly incorporated into the generated e-invoice \u2013 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.<\/p><\/div>\n\n\n\n

    Flexible in format choice \u2013 seamlessly integrated into SAP<\/strong><\/h4><\/div>\n\n\n\n

    GOpus\u00ae eInvoice generates e-invoices from SAP SD invoice lists in all common and supported e-invoice formats<\/strong> \u2013 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.<\/p><\/div>\n\n\n\n

    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\u00ae eInvoice directly on their existing processes and data.<\/p><\/div>\n\n\n\n

    What this means in practice<\/strong><\/h4><\/div>\n\n\n\n

    The benefits for companies can be summarized in a few key points:<\/p>\n\n\n\n