The E-invoicing obligation It's here – since January 1, 2025, all companies must be able to receive e-invoices, and from 2027 onwards, they must also be able to send them. This checklist shows you step by step how to integrate your SAP system with GOpus® eInvoice Get ready for e-invoicing.
Timetable for mandatory e-invoicing: The obligation to receive deliveries has been in effect since January 1, 2025. The obligation to ship deliveries applies from January 1, 2027 (for revenues > €800,000) or January 1, 2028 (for all companies). All deadlines in detail →
The 10-step checklist
How many invoices do you send/receive? Which SAP modules do you use (FI, SD, MM, RE/FX)? Which formats and channels do your business partners use? This inventory forms the basis for implementation.
GOpus® helps: Free initial analysis of your SAP invoicing processes
GOpus® eInvoice runs on SAP ERP (ECC 6.0) and S/4HANA Likewise. Check your SAP version and release level – GOpus® supports all current releases.
GOpus® helps: Compatibility check of your SAP system
What formats do you need? ZUGFeRD vs. XRechnung – or both? Do you have international customers who Peppol or expect Factur-X?
GOpus® helps: Format consulting based on your customer base
The SAP add-on is installed in your system via transport requests – without modification to the SAP standard, without external middleware.
GOpus® helps: Remote installation by certified SAP consultants
Define for each debtor and creditor: Which format? Which delivery channel (email, Peppol, ZRE, ePost)? The mapping can be adjusted at any time.
GOpus® helps: Initial mapping based on customer master data
Define input channels (email, Peppol, portal), define processing profiles, and set up automatic validation and assignment.
GOpus® helps: Configure the processing profiles according to your processes
Set up format conversion, validation, and delivery channels for outgoing invoices. Activate archiving and delivery logging.
GOpus® helps: End-to-end configuration of the output workflow
Create test calculations and use them E-Invoice Validator Check. Conduct test mailings to selected business partners. Test incoming invoice processing with sample invoices.
GOpus® helps: Provision of test invoices and validation support
Introduce accounting and bookkeeping into the new process. The good news: Since GOpus® eInvoice uses existing SAP transactions, training efforts are minimal.
GOpus® helps: User training (remote or on-site)
Go-live with full operation. Monitoring of the first invoice runs, fine-tuning of processing profiles, ensuring compliance.
GOpus® helps: Go-live support and hypercare phase (2 weeks)
Avoid common mistakes
Many companies only set up receiving invoices and forget about sending them. From 2027, you will also be required to send e-invoices. send can.
ZUGFeRD MINIMUM and BASIC requirements are met not The obligation to issue e-invoices. Only COMFORT, EXTENDED and XRECHNUNG are compliant.
Sending e-invoices without validation is risky: Missing mandatory fields or incorrect tax rates lead to rejection and jeopardize the input tax deduction.
Solutions outside of SAP create media breaks: export, conversion, import. With GOpus® eInvoice, everything remains natively within SAP.
Should we go through the checklist together?
Our SAP experts will work through this checklist with you – tailored to your SAP system, your processes and your business partners.
Request a free initial consultationFrequently Asked Questions
How long will the entire implementation take?
Do I have to implement all 10 steps at once?
What are the implementation costs?
Can GOpus® implement the checklist for me?
What if I miss the deadlines?
Further information
- GOpus® eInvoice – The SAP solution for e-invoicing
- E-invoicing obligation 2025: Deadlines, formats & checklist
- Invoice receipt: Receiving e-invoices in SAP
- Outgoing invoices: Sending e-invoices from SAP
- ZUGFeRD vs. XRechnung: Which format is suitable?
- Peppol: Send e-invoices internationally
- GOpus® eInvoice: S/4HANA vs. ERP
- Free e-invoice validator
English 
German