At Conrad Benelux, e-invoicing did not begin with a straight upward line, but with a process that got stuck. The team had wanted to send e-invoices since 2018, but couldn't get it operational with a previous supplier. After about two years it still wasn't possible to generate the right file. The switch to eConnect changed that. First with manual sending via the platform, then with a technical connection between SAP, SFTP and the Procurement Service Bus. This gave Conrad Benelux a working process that not only brought peace of mind internally, but also became a blueprint for sister organisations in Sweden and later Denmark.
The trigger was recognisable to many organisations. Governments started actively receiving e-invoices and suppliers were expected to follow. At Conrad too, the topic suddenly became concrete. Peppol and Mercurius were known, but not yet high on the agenda. When the obligation around government receipt became more visible, that changed.
Internally the goal was clear: set up e-invoicing properly and not let the process depend on manual actions. In practice, however, the process with a previous supplier was slow. Kelly Soijo, Head of Quality & Process Management and later also Head of Operational Customer Care, described that process as too complex. Despite efforts over a period of about two years, no working output came from the system. Generating the right file simply didn't work.
The switch started pragmatically. During the search for an alternative, Conrad came across eConnect. Because it initially involved a limited number of invoices, the team could start quickly with manual sending via the platform. The threshold stayed low, creating an account was quick, and the first invoices could be sent immediately.
After that, the focus shifted to automation. The goal was clear: stop relying on manual work and establish a robust chain that fits into the daily process. Together with the technical teams, the setup was worked out step by step:
- In SAP, it is recorded that an invoice must be sent via Peppol.
- SAP then generates the correct file and places it on an SFTP server.
- The PSB checks every 15 minutes whether an e-invoice is ready.
- As soon as a file is ready, the sending is executed.
The first result was reliability. Where the previous process had not produced working output after a long period, the new setup did. Conrad could not only send e-invoices, but also incorporate the process into regular operations.
The second result was automation with control. The combination of SAP, SFTP and the PSB created a predictable rhythm. The periodic check every 15 minutes ensures continuity without manual steps per invoice.
The third result was knowledge building. As Conrad Benelux realised the connection, the team built experience that proved directly applicable outside the Netherlands. Within the group, Sweden and Denmark were at that time facing similar challenges with a national supplier. By sharing the knowledge from the Netherlands and comparing approaches, a concrete alternative emerged.
"At eConnect I just had a good feeling. They are flexible and really think along with us." Kelly Soijo, Conrad
- Start small if that is faster, but from day one design a route to automation.
- Let technical teams work directly with each other — this prevents delays from intermediate layers.
- See e-invoicing as a process improvement across departments, not as a separate IT project.
Want to know how this works in your situation? Schedule an introductory meeting and discuss how eConnect makes your e-invoicing process achievable.