Lessons Learned in Implementing Dispute Resolution in an ERP System

Description: The issue of better managing the resolution of disputes in Order-to-Cash is one that is continually addressed by a large number of companies, with a whole range of results. While the major ERP system providers (SAP, Oracle, etc.) have developed improved capabilities to handle dispute resolution, the implementation of this module can be very challenging. During this Peercast, our feature company will share their recent experiences in implementing the SAP Dispute Resolution module and what lessons they learned in carrying out that complex project.

Peercast Poll Results

Poll Title: Dispute Resolution Solutions in Order-to-Cash

Background: The issue of better managing the resolution of disputes in Order-to-Cash is one that is continually addressed by a large number of companies, with a whole range of results. While the major ERP system providers (SAP, Oracle, etc.) have developed improved capabilities to handle dispute resolution, the implementation of this module can be very challenging. This poll looks at the primary technologies used by companies to resolve disputes and the focus that they plan to place on improving this process in the next one to three years.

Poll Question: What best describes the primary technology / tools being utilized at your company for resolving disputes in Order-to-Cash?


Vote Now
  Handled within the ERP system 37%
  Bolt-on to ERP system - internally developed 11%
  Bolt-on to ERP system - external software 0%
  Separate system outside ERP - internally developed 11%
  Separate system outside ERP - external software 16%
  Primarily a manual process using standard tools such as Excel 21%
  Other (please comment) 5%

Poll Question: Looking forward 1-3 years, what priority do you expect to place on improving the dispute management process at your company?


Vote Now
  This will be a very high priority for us 37%
  This will be a moderate priority for us 47%
  This will be a low priority for us - we are happy with our current status 5%
  This will be a low priority for us - we have more important issues to address 11%