Operations, software, and how companies actually work
There is a version of procurement software that exists in vendor demonstrations and a version that exists in production environments. The distance between them is where most of the actual work happens, and almost all of it comes down to data.
Before you automate anything, you need to understand what is actually happening, not what the process documentation says is happening. The gap between those two things is where all the interesting problems live.
ERP projects fail for reasons that have nothing to do with the software. Scope creep that starts before kickoff, the gap between what users need and what systems can do, and a change management problem that most implementation guides describe but almost none explain honestly.