{"id":1070,"date":"2019-12-19T10:32:45","date_gmt":"2019-12-19T10:32:45","guid":{"rendered":"http:\/\/sydecon.de\/?p=1070"},"modified":"2019-12-19T10:32:45","modified_gmt":"2019-12-19T10:32:45","slug":"third-party-due-diligence-tpdd-as-a-shared-service","status":"publish","type":"post","link":"https:\/\/sydecon.de\/en\/third-party-due-diligence-tpdd-as-a-shared-service\/","title":{"rendered":"Third-Party Due Diligence (TPDD) as a Shared Service"},"content":{"rendered":"<p>Talking about Shared Services always means talking about the simplification of processes. So, let\u2019s do that with our Third-Party Due Diligence (TPDD) topic now.<\/p>\n<p>Like established last week, summarizing available customer information prevents possible fraud or product abuse and allows you to identify between credible and non-credible customers. How exactly do you accomplish that?<\/p>\n<p>Let\u2019s suppose once again, that a prospective customer approaches a local headquarter with a certain request. But he already tried that over another channel of your company and got dismissed. Without Shared Services the local manager of said different channel would have to contact every other local headquarter individually and tell them via phone or e-mail to not sell to that certain customer. Of course, that is neither practical nor practiced in any way.<\/p>\n<p>On the other hand, a local manager of a different branch office has no way of knowing who they are dealing with. He is sitting in a vacuum between all the available information floating around but can\u2019t access it because he doesn\u2019t know where to start. He will therefore run additional credit reports to verify the liquidity of the prospective customer. Now that is neither efficient nor cost-saving for the overall company. Which means that by not using available customer information in an optimized way, economic statistics will suffer. In the end this is threatening to all who are involved.<\/p>\n<p>The solution is to create a standardized workflow that enables the local manager who initially dismissed the prospective customer to share his information without the need for individual contacting. This can for example be the initialization of a command chain that leads to the available information being automatically distributed via the cloud. An adequate supporting IT system can help with that. With the right programming the first local manager can enter information that is retrievable with a few mouse clicks by all other local managers. Instead of sitting in a vacuum, they now know exactly what to do with available data. This simplifies customer contact and builds additional trust between company and customers.<\/p>\n<p><a href=\"https:\/\/www.youtube.com\/watch?v=jHTLoP4SYoY\">See here our first YouTube-video with a more detailed explanation on Shared Services in general!<\/a> Don\u2019t forget to subscribe and leave a like, we thank you very much!<\/p>\n<p>Next week we\u2019re going to take a Christmas break. We wish you happy holidays and hope you\u2019ll rejoin the blog next year! Stay tuned \u2026<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Talking about Shared Services always means talking about the simplification of processes. So, let\u2019s do that with our Third-Party Due Diligence (TPDD) topic now. Like established last week, summarizing available customer information prevents possible fraud or product abuse and allows you to identify between credible and non-credible customers. How exactly do you accomplish that? Let\u2019s [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":898,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"link","meta":{"footnotes":""},"categories":[8,9,115],"tags":[79,74,21,61,52,78,77],"class_list":["post-1070","post","type-post","status-publish","format-link","has-post-thumbnail","hentry","category-featured-en","category-mdm-enterprise-workflow-en","category-sydecon-timeline-en","tag-customer-risk","tag-due-diligence","tag-shared-service","tag-shared-service-management","tag-ssc","tag-third-party","tag-tpdd","post_format-post-format-link"],"_links":{"self":[{"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/posts\/1070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/comments?post=1070"}],"version-history":[{"count":0,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/posts\/1070\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/media\/898"}],"wp:attachment":[{"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/media?parent=1070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/categories?post=1070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sydecon.de\/en\/wp-json\/wp\/v2\/tags?post=1070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}