3 More Terrible Reasons NOT to Use e-Procurement

Over on Procurement.World, the procurement dynamo gives us 3 Terrible Reasons NOT to Use e-Procurement, which, sadly, are still used by many organizations in the bottom 40% to 60%, to fight the implementation and adoption of e-Procurement systems.

If the reasons given in the procurement dynamo‘s post were the only reasons, that would be bad enough. But these are just a few of the reasons that Procurement organizations don’t use e-Procurement. In this post we are going to discuss other reasons, and, in particular, reasons that are a bit more believable — which are the worst kind of reasons.

1. Our Processes are Not Supported in the New System

While it’s true that the processes used by organizations that are still operating like it’s the last century are not supported out of the box, modern procurement platforms come with adjustable workflows that can be tailored to support just about any process the organization needs, good or bad. This may have been an excuse with first generation systems with fixed rules and workflows, but it’s not an excuse anymore.

2. The system won’t work with our current ERP or AP system

Most organizations require that all POs get in the ERP, all invoices in the AP, and all goods receipts in the inventory system. Because no recommended e-Procurement system will integrate with these systems out of the box, anyone against the implementation of such a system will insist it won’t work. And, again, wile this may have been an excuse with first generation systems that were almost impossible to integrate with anything, it’s not an excuse anymore when most e-Procurement vendors realize that their systems have to integrate with other systems and have published data models, open APIs, and middleware that enables the easy integration with such systems.

3. We don’t need Supply Management System X, we need Supply Management System Y.

Sometimes, knowing that a system they don’t want is inevitable, an opposing employee will suggest that a system is needed, but the system under consideration is not the right one and a totally different system is needed. For example, you are looking at a P2P and they will insist that a S2C is needed, or vice versa. Or they will insist that the ERP needs an upgrade. Or so on. But it will all be a distraction.

Systems will always be opposed, but when they are needed, they need to get implemented. The key is to select the right one. But with proper homework (and many posts on this blog will tell you how to do it), the right one can be selected.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>