When to workflow within SAP FSCM Dispute Management

9 February 2011

Mark Chalfen

Mark Chalfen

Former SAP S/4HANA Global Lead

Having worked on a few implementations of SAP FSCM Dispute Management it is clear that there is no simple standard solution when deciding what decisions in the dispute cycle should use workflow. The benefits of workflow are clear – "you are pro-active rather than re-active to a dispute”.

However as the saying goes “you can take a horse to water, but you can’t make it drink”; you can send e-mails to processors or approvers but you cannot make them open the dispute and action it. Further to this, the reporting within ECC is non existent, so if you want to report on disputes, you will need to activate some BI reports.

Workflow or BI reports?

Now BI reports can be sent to business users to notify them of disputes they need view and action, and in a way this is doing the same type of job as the workflow – notifying the business user they need to action the dispute. With a typical SAP FSCM implementation, the reporting requirements will come right at the end of the project, they maybe defined in the scoping and Blueprint, but the true look at feel to them will only come late in realisation. Where clients want formal control around their processes workflow is usually recommended as an option, and with mature SAP ERP clients, they will have some experience of this is other business processes. Within scoping and blueprinting, the formal dispute cycle is debated and agreed, and the process will normally include workflow where formal controls are required within the process. Sometimes the business decisions that are made early on within the implementation will be done without the knowledge of what could be achieved via BI reporting and so workflows get designed and agreed to mitigate the risk of lack of control around the approval and sign off processes of a dispute.

Dispute phases within the cycle

The dispute cycle, can be made very complicated, with many new system statuses added, new fields included to record information that is deemed critical. However all dispute cycles can be broken down into a number of basic phases.

  1. Creation and logging
  2. Approval or rejection of dispute
  3. Resolution of dispute - credit note creation
  4. Closure of dispute

When should workflow be used?

Workflow is not normally used to create and log a dispute. There are a number of different ways to create disputes within SAP FSCM, some are automated from receipt of payment, and others could be as a result of customer contact made within SAP Collections Management. The key area for workflow is the approval phase. A normal process would have a dispute being sent to an “approver”. This could be derived from the customer number or the reason code or manually entered. The approvers “task” is to review the details in the dispute and approve or reject. If they have sufficient authority the resolution phase could start, or if they don’t a new approver maybe required to authorise a high value credit note. The resolution phase, is normally either raising a credit note and attaching that to the dispute, or contacting the customer to inform them that the dispute has been resolved and no credit is due, (this could be the case where a Purchase Order Number is missing on a customer invoice). The business users required in the resolution phase will normally be frequent users such as credit collections clerks. Finally the closure of the dispute, is normally an automated process when the dispute has a value of zero, this normally occurs when a credit is raised and assigned to the dispute, or the customer pays in full the invoice that was in dispute.


The key area to focus on utilising workflow is the approval phase of the dispute. By creating good reporting and sensible dispute statuses the other phases should be achievable by either automated processes or frequent business users reviewing reports to identify the disputes that need further processing. Further to this, some clients like to provide the frequent dispute users a worklist similar to the Collections Worklist, to identify the disputes that they need to process.

View comments


Blog post currently doesn't have any comments.

About the author

Mark Chalfen

Former SAP S/4HANA Global Lead

Mark tells it straight - as an ex-boxer, what else would you expect?  Both his knowledge and experience of SAP products allow him to cut to the chase dispelling myths and hearsay.

As a result of working closely with various SAP Finance Product Management teams on product development, Mark understands these products inside out. This depth of understanding has led to him become a ‘thought leader’ in his field; after all, it is not often SAP consultants have helped shape and develop the very product they are selling.

Having such a strong relationship with SAP alongside being an SAP Mentor and Moderator means that Mark has an extensive network within SAP. For clients, this relationship proves to be a huge advantage and leads to configuration issues being resolved rapidly.

Mark has worked on short proof of concepts through to year-long multi-million pound global roll-outs. However, no matter how large or small the project, the true value Mark brings to his work is in the guidance he provides to senior stakeholders. In essence, he assists them to implement more effective processes and drive better behaviours within their finance teams.

Helping organisations transform their business with SAP S/4HANA is Mark’s current focus. The benefits of S/4HANA are numerous, including the simplification of tasks, embedded analytics and improved user engagement. Whilst the eventual move from SAP Business Suite into S/4HANA is inevitable, the journey to it is not always clear. Mark’s ability to understand an organisation’s needs coupled with his deep understanding of S/4HANA provides clarity and eases their transition.

Bluefin and SAP S/4HANA - welcome to the one horse race

We use cookies to provide you with the best browsing experience. By continuing to use this site you agree to our use of cookies.