GOpus® eInvoice: S/4HANA & ERP

E-invoicing in both SAP worlds – today and after migration

Whether SAP ERP (ECC 6.0) or SAP S/4HANA – the E-invoicing obligation This applies to both systems. Many companies are in the middle of or planning an S/4HANA migration. GOpus® eInvoice It works identically on both platforms – and guides you seamlessly through the transition.

The starting point: Two SAP worlds, one obligation

SAP has extended mainstream support for ECC 6.0 until 2027 (extended maintenance until 2030). At the same time, more and more companies are migrating to S/4HANA. But no matter where you stand: e-invoicing requirements won't wait for your migration. You need a solution that... now works – and even after migration.

CURRENT

SAP ERP (ECC 6.0)

  • Classic SAP architecture
  • Proven transactions (VF01, MIRO, FB60)
  • Maintenance until 2027/2030
  • GOpus® eInvoice: Fully supported
FUTURE

SAP S/4HANA

  • New database (HANA) & UI (Fiori)
  • Simplified Data Model (ACDOCA)
  • SAP's strategic platform
  • GOpus® eInvoice: Fully supported

Functional comparison: GOpus® eInvoice on ERP vs. S/4HANA

function SAP ERP SAP S/4HANA
Outgoing invoice
Invoice receipt
ZUGFeRD / XRechnung
Peppol network
Receiver mapping
EN-16931 validation
SAP modules (FI, SD, MM, RE/FX)
SAP Fiori Integration
Migration: Configuration transferable ✓ Receiver mapping and profiles are transferred 1:1

Key message: GOpus® eInvoice offers the same functionality on SAP ERP and S/4HANA. Only the SAP Fiori integration is exclusive to S/4HANA. All configurations (recipient mapping, processing profiles, format rules) are transferred 1:1 during migration.

E-invoicing on SAP ERP: Here's how it works

GOpus® eInvoice is installed as a native SAP add-on and utilizes the existing SAP ERP infrastructure. Outgoing invoice and Invoice receipt They run via proven SAP transactions – users work in their familiar environment.

Output via SAP print program

GOpus® integrates into the SAP output process (message control). The e-invoice format is automatically generated during invoice output.

Input via processing profile

Incoming e-invoices are automatically validated and fed to the SAP transactions MIRO (MM) or FB60 (FI) via configurable profiles.

No ABAP customizing required

The entire configuration is done via customizing tables – without Z-development, without modifications to the SAP standard.

E-invoicing on SAP S/4HANA: Additional benefits

With S/4HANA, you benefit from additional possibilities offered by the new data model and the Fiori interface:

SAP Fiori Dashboard

Modern dashboard for an overview of all incoming and outgoing e-invoices – status tracking, error analysis and real-time evaluations.

Simplified data model

The new Universal Journal (ACDOCA) enables faster evaluations and a more direct assignment of e-invoice data to accounting documents.

Output Management 2.0

GOpus® eInvoice uses modern output management on S/4HANA – more flexible than classic message control and with native cloud support.

Migration: From ERP to S/4HANA with GOpus®

One of the biggest advantages of GOpus® eInvoice: Migration to S/4HANA requires no new implementation the e-invoicing solution. Your existing configuration will be retained:

Receiver mapping

All customer/vendor mappings (format + channel) will be migrated automatically.

Processing profiles

Profiles for invoice receipt (assignment rules, validation, workflow) are retained.

Format definitions

All configured format rules (ZUGFeRD profiles, XRechnung versions, country-specific formats) are adopted.

Peppol configuration

Peppol IDs, access point connection and network configuration remain unchanged.

Setting up e-invoicing in your SAP system?

Whether SAP ERP or S/4HANA – our experts will implement GOpus® eInvoice precisely for your system and support you during the migration.

Schedule a consultation

Frequently Asked Questions

Do I have to wait for the S/4HANA migration to receive e-invoices?
No. GOpus® eInvoice runs entirely on SAP ERP (ECC 6.0). You can E-invoicing obligation Implement immediately and later seamlessly migrate the solution to S/4HANA.
Will anything change for users during the migration?
The e-invoicing process remains unchanged for users. S/4HANA also offers a Fiori dashboard that provides a clearer overview of all e-invoices – but the existing processes remain the same.
Does GOpus® eInvoice also work in the SAP S/4HANA Cloud?
GOpus® eInvoice is available for SAP S/4HANA on-premise and private cloud. Specific integration paths apply to the public cloud edition – contact us for a personalized consultation.
How long will the implementation take?
Implementation on SAP ERP and S/4HANA On-Premise typically takes 2 to 4 weeks – depending on the number of modules, formats, and distribution channels. GOpus® accompanies you from analysis to go-live.
Does GOpus® also support SAP Business One or SAP Business ByDesign?
GOpus® eInvoice is specifically designed for SAP ERP (ECC 6.0) and SAP S/4HANA. For SAP Business One or ByDesign, we recommend contacting us directly – we would be happy to advise you on alternatives.
en_GBEnglish