|
|
|
|
|
by jl6
598 days ago
|
|
> It is set to re-implement an "out of the box" version of the solution after customizations in the first effort disrupted its bank reconciliation system. Root cause. When you buy from an ERP vendor, you are not just buying software, you are buying a logical model of an idealized corporation. If that model doesn't reflect your actual organization, you can try to customize the software, but beyond some threshold of mismatch, it's easier to change your accounting & control & governance processes to match the software. SAP and Oracle are no different in this respect. |
|
But almost none of the banks actually work like that, apart form some small insignificant shops which can't afford such customization. Each has some unique stuff that makes it better than most competition in that area. Behemoths of banking world run their pretty unique things, workflows, specific jurisdiction reporting etc. so each of them have more or less massive customization on top of basic common stuff.
I guess it goes without saying almost constant flow of changes, either from business or regulators keeps hefty IT teams busy to maintain that customization and ensure things keep working. Also logically the complexity has only one direction to go, and so it goes, slowly but surely.
I am not even sure if business properly realizes all this, maybe they do or maybe they are kept in continuous cloud of bullshit from IT managers who of course want to preserve their jobs and importance (headcount, impact) within corporation. Anyway the prospect of migration to something else is something they (rightly) detest and want to avoid if possible, since costs and duration are massive, potential issues tremendous and backbreaking, and there is absolutely no guarantee of success.