A recurring theme across clients and industries when implementing Oracle Fusion for Procure to Pay is the disconnet between expectations and reality for reducing time spent on match exceptions. While Oracle continues to bring improvements, many consultants and clients don’t have a good grasp of the end to end picture, configuration requirements and options which impact their results. Additionally, this is an area where transformation of business processes and culture will pay off in spades alongside of technical solutions that enable teams to communicate and collaborate to resolve the true root causes instead of simply fighting fires.
I have taken hundreds of hours of conversations, configurations, testing and change management insights and boiled them down into this article. If you are struggling with match exceptions today, or if you have never heard the words “match” and “exception” in the same sentence, if you are in the Oracle Supply Chain space, then this article is for you.