On October 21, 2026, our joint webinar with Axians ICT Austria focused on how electronic invoicing processes can be fully digitalized within an existing IBM i environment – from invoice creation to automated transmission to customers, platforms, and e-invoicing networks.
Herbert Pfeifer from Axians ICT Austria and Klaus Schaffer from EDI Service & E-Invoicing Partners presented two perspectives that are closely connected in practice: Output Management and e-invoicing/EDI. The aim was to provide a clear understanding of electronic invoice formats, SpoolMaster eBilling, different requirements across Europe, and the various transmission methods.
✓ Understand different requirements, transmission methods, and formats across Europe
✓ Automatically transmit invoices to customers, platforms, and e-invoicing networks
✓ Discover the possibilities of SpoolMaster
From IBM i to structured e-invoices
In the first part of the webinar, Herbert Pfeifer introduced SpoolMaster, the Output Management solution for IBM i. In addition to creating and designing physical and electronic documents, SpoolMaster also supports their electronic transmission.
The eBilling module can process various electronic invoice formats, including XRechnung, ZUGFeRD, CII, and UBL. The required data can be retrieved directly from the ERP database, intermediate files, APIs, or existing spool files. One important aspect is that electronic invoice formats come with specifications and ongoing changes. Defined interfaces are designed to reduce this technical complexity and simplify implementation.
The invoice has been created – but how does it reach the recipient?
In the second part, Klaus Schaffer focused on the next steps in the process. Internationally operating companies face different legal requirements, invoice formats, mandatory fields, platforms, and transmission methods. At the same time, these requirements are constantly evolving. Especially when multiple countries are involved, e-invoicing quickly becomes a cross-company transformation project rather than an isolated IT task.
Various transmission methods are available, ranging from AS2/AS4, OFTP2, and SFTP to web services/APIs, Peppol, and connections to national government e-invoicing platforms. The goal of a centralized e-invoicing and EDI solution is to accommodate these different requirements through as few interfaces as possible.
What role does Peppol play?
Another key topic was Peppol. The network enables the standardized exchange of electronic documents via certified Access Points. Following the principle of “Connect once – connect to all,” senders and recipients do not need to be connected to the same provider.
Depending on the national implementation, government authorities may also be involved in the process. This highlights the growing importance of considering reporting
E-invoicing as part of a broader digitalization strategy
One key takeaway from the webinar: E-invoicing is just one part of the potential for process digitalization.
In addition to invoices, EDI also covers orders, delivery notes, master data, and other business documents. Companies that take a holistic approach to their processes – from orders and invoices to remittance advices and future reporting to tax authorities – can unlock significantly greater automation potential than with a standalone e-invoicing solution.
The interaction between IBM i, Output Management, e-invoicing, and EDI demonstrates that existing system landscapes and new regulatory requirements do not have to be mutually exclusive. What matters is connecting existing data and processes with new formats, networks, and communication methods in a meaningful way. This allows companies to turn a regulatory requirement into another step toward more automated and seamless business processes.
Many thanks to Herbert Pfeifer from Axians ICT Austria and Klaus Schaffer from EDI Service & E-Invoicing Partners for sharing their insights, and to all participants for their interest and valuable discussions.
Are you currently dealing with e-invoicing, EDI, or connecting international business partners?
We are always happy to assist you.
Herbert Pfeifer| Axians ICT Austria |
herbert.pfeifer-ext@axians.at | +43 664 88466769
Klaus Schaffer | EDI Service & E-Invoicing Partners Avenum |
klaus.schaffer@avenum.com | +43 1 92 101 – 152
IBM i & e-invoicing: Key facts at a glance
Existing IBM i processes can continue to be used and extended with e-invoicing functions. Invoice data can be retrieved from ERP systems, databases, APIs, intermediate files, or existing output data and prepared for structured electronic invoice formats.
How is invoice data on IBM i converted into electronic invoice formats?
Invoice data can be extracted from existing ERP and IBM i processes and converted into formats such as XRechnung, ZUGFeRD, UBL, or Peppol BIS. The required format depends on the respective country, business partner, and use case.
How are e-invoices automatically transmitted from IBM i to the recipient?
Once the structured invoice data has been created or converted, it is transmitted via the communication method required by the recipient or the respective country. Possible methods include Peppol, APIs, web services, AS2/AS4, SFTP, or government e-invoicing platforms.
What role does Peppol play in e-invoicing from IBM i?
Peppol is a standardized network for the electronic exchange of business documents. Invoice data from IBM i can be transferred to a Peppol Access Point via a suitable e-invoicing connection and then transmitted to the recipient. Peppol is one of several possible transmission methods.