Rexel is a wholesaler and distributor of electrical products and services, operating in the residential, commercial, and industrial markets. With an invoice volume of approximately 1 million documents, scalability was not a nice-to-have but a prerequisite. Furthermore, Rexel operates in a legacy environment with many typical exceptions: from advance invoices to mandatory purchase orders and generic customer and GLN numbers.
Sector
Wholesale
Invoice volume
1 million
ERP environment
Legacy ERP
Regions
Belgium & Luxembourg
Nymus products
Nymus Connect
Hear firsthand how the implementation process went and what concrete results it yielded for the finance team.
Rexel operates within a complex and extensive landscape, with numerous exceptions in the ERP system (AS400) that are specific to the way Rexel invoices. Examples include advance invoices, mandatory purchase orders that must be sent to customers, and generic customer and GLE numbers.
With a volume of nearly one million documents per year, scalability was therefore crucial—not only in an ideal scenario, but just as much during periods when large numbers of documents are sent at once. And just as important: the exceptions to the standard workflow had to remain accurate in every single case, even at those volumes.
Kimberly Van Impe, Process and Quality Manager at Rexel: It wasn’t just a technical setup that had to be taken into account, but above all the exceptions, which really had to be just right for Rexel.
Rexel was looking for a partner that looked beyond the technology. A partner with a view of the big picture, one that could contribute ideas on digitization, Peppol, and scalability. Rexel found that partner in Nymus.
Specifically, Rexel delivers data, XML, and PDF documents to Nymus via (S)FTP. Nymus handles the conversion to the correct format: for Peppol transmission, this means converting to UBL. Where necessary, Nymus also converts invoices to a format that can be sent via email or, if necessary, by mail.
Nymus thus acts as the layer that translates the complexity of the AS400 landscape and customer-specific exceptions into accurate, ready-to-send invoices, regardless of the channel.
Nymus’s role at Rexel extends beyond its own outgoing and incoming invoicing. Through Isabora, Rexel provides its own customers with an invoicing package, which they can use to send and receive invoices. Nymus also acts as a Peppol Access Point for Isabora, ensuring that Rexel’s customers’ invoicing complies with legal requirements.
In addition, Nymus also handles invoicing for Rexel’s Luxembourg entity, also via Peppol for both sending and receiving.
Rexel is now successfully invoicing via the Peppol network, both in Belgium and in Luxembourg. And this applies in both directions: for both sending and receiving invoices. The complexity of the AS400 landscape and customer-specific exceptions (advance invoices, mandatory purchase orders, generic customer and GLN numbers) are no longer an obstacle: Nymus consistently translates these specific characteristics into accurate, ready-to-send Peppol messages, regardless of volume or entity.
A solution has also been provided for Isabora, the invoicing package that Rexel offers to its own customers: Nymus acts as a Peppol Access Point so that Rexel’s customers can issue legally compliant invoices via Isabora, without Rexel itself having to deal with the complexity of Peppol. In this way, Nymus not only handles Rexel’s own invoicing but also that of the broader customer network that invoices via Isabora.
If a substantive issue does arise with an XML invoice, Kimberly says it’s resolved fairly quickly. Nymus always ensures that the customer receives their invoice as soon as possible.
Find out exactly what Nymus can do for your organization. Not a generic demo, but a conversation about your specific situation.
Solutions
Learn more
Hoe ga je om met complexe e-invoicing scenario’s? Dat lees je in deze whitepaper. Vul het formulier in en krijg direct toegang tot de whitepaper.
