Let’s say a sales resource wants to add a new customer. Internal business rules state that payments made within 30 days of invoicing is standard. The new customer works on a different cycle and requires a 45 day payment cycle. Business rules further state that this type of variation must have CFO approval. So what must happen to get the customer approved?
The sales resource submits the information to Accounting, who sends it to the Accounts Receivables (AR) department. >> AR sees the 45 days to pay request and asks the CFO for approval. >> The CFO contacts the sales department asking for clarification, the sales manager tracks down the sales resource and asks for information to help make a decision. >> The information is given to the sales manager, who pushes it back to the CFO, who makes a decision and gives instructions to the administration department, who then gives instructions to AR. >> AR then notifies the sales resource who contacts the customer. Here’s what this process looks like…are you dizzy yet?
Do you see any place for this process to collapse? Do you see any opportunity for this workflow to digress into ‘workslow’? Also, what about the new customer, what has this felt like to them?
The good news? This mess can be simplified. A workflow engine could trigger off the variation between 30 and 45 days during data entry, send the appropriate notification (even lock the entry until approved), manage notifications and approvals throughout the process even if re-cycling were to be required.
With workflow automation, the process is efficient and effective. Not only does it alleviate your headaches, your customer will see you as well organized, enhancing their desire to do business with you. Hair loss may be reduced as well.
Think about the processes you must manage in your daily routines. Which ones are cumbersome? How would an automated workflow be beneficial?
Brought to you by U-LINC, workflow anytime, anywhere
by Integrity Data, ISV for Microsoft Dynamics