Master Data: How to Avoid Issues with the Requestor’s Process
By Sigrid Kok on Mar 25, 2014
This time of year, those of us in the US are scrambling to get our taxes in by the April 15th deadline. Even if we have someone prepare our taxes for us, we have a lot of preparation to do. The process can take a large amount of time to complete, including finding receipts, W-2’s and lots of other documents. In addition one may have to fill out many forms for the tax consultant. Needless to say this timely process, depending on how organized you are and the complexity of your situation, isn’t a fun chore.
Once you’ve submitted your request, the tax consultant has their own process to complete, taking everything you’ve collected and applying the proper tax year rules to your tax return. Those with state taxes, there are additional documents to complete. Sometimes they have to come back to you for additional information before finally filing your return.
Much like the process of completing a tax return, we often speak to companies who have their Master Data processes very well documented and as optimized as possible, albeit often a manual process. While we can look to automate and optimize that process, we may need to also take into consideration the requestor’s process.
What does a requestor need to do to submit a master data request?
Often they need to interact with external partners, such as customers or vendors for quotes or requests for proposals. They need to collect the partner’s information, often requiring legal documents in order to conduct business with them. The requestor also needs to interact with internal participants in their process to collect data and/or approvals.
The requestor’s process is usually done via emails and paperwork, making it difficult to track has been completed and to identify what is missing.
The requestor’s process can take anywhere from a couple of hours to a few months before they can submit their request to their master data team. And as is often the case, there may be additional or updated data to submit along the way.
Just like the necessary prep work to complete your tax returns, your master data requestor’s process requires a lot of time and can be very complex. Here’s a few contributing factors:
- How many people does the requestor need to interact with, both externally and internally?
- How much data and supporting information do they need to collect?
- How often are requests rejected and/or modified because of incorrect or incomplete information?
These are considerations as to whether you might want to include the requestor’s process in your master data automation and optimization projects.
Winshuttle Foundation provides a suite of products is able to support your master data processes for SAP. In addition, Foundation also supports automating your requestor’s process to ensure you have a smooth flow of complete and correct data. This will greatly increase the speed up the onboarding process and providing complete end-to-end traceability!
Contact email@example.com for more information.
About the author
Sigrid Kok is a Principal Solutions Engineer at Winshuttle, residing in the San Francisco By Area. Prior she has worked for companies like SAP and IBM in their SAP practice. She has been in technical sales for over 20 years, and also has experience in product management and IT.
Questions or comments about this article?
Tweet @Winshuttle to continue the conversation!