Redirected Entity Workflow

1. An existing supplier in POC, US705134, has Tax ID 12-3123213 on their profile.
2. A business requestor either:
   1. Doesn't realize the entity they’re searching for (US705134) already exists in Graphite, or...
   2. Believes US705134 is not the entity they’re looking for...

And creates an NSJ to connect to the same supplier but under a different/similar name.

3. The supplier contact listed in the second NSJ receives the invitation to join Graphite. If they’re a particularly savvy supplier contact who has already been onboarded into Graphite, they may push back on the business requestor and say that they are already onboarded.

If the supplier contact listed in the second NSJ was not the original supplier contact who onboarded US705134, or if the supplier contact simply begins filling out the Graphite questionnaire a second time without pushing back on the business requestor, they begin filling out the Graphite questionnaire.

4. They get to the point where they need to enter their Tax ID. They do so, not knowing this Tax ID is already associated with an existing Graphite profile (US705134).

5. When the supplier fills out this page and clicks “Next,” the following page appears.

6. If the supplier contact recognizes that the entity listed is their own organization, they can click “Transfer invitation to this company.” If the listed entity is not their organization, they can contact support or check to make sure they didn’t mistype their Tax ID.
7. If the supplier selects the Transfer field, they will see this screen next. 

8. If they click Confirm, it takes them here:

Then, they are taken here if they click “OK.”

9. At this point, the supplier contact (in this case, SpendTest User) can close the window.
10. Now, we go back to US705134 and see that there are two tasks:

11. The first task — Connection Redirected — brings you to this screen if you select it:

The purpose of this task is to notify the customer that this redirection occurred. No action is required to close the task; it’s just an FYI so you can check whether the redirection should have happened the way it did.

If you do not want SpendTest User to be merged with SpendTest, send support or your CSM a message asking to unmerge them, and we can do so as requested. Then, the supplier contact (in this case, SpendTest User) can be asked to onboard without merging with NL Letour, whether by using a different Tax ID (if applicable) or by setting up a branch.

12. The next task — Finish Required Questions — brings you to this screen and prompts you to answer questions in the NetSuite record that were created upon the merging of SpendTest User company and SpendTest.

13. You’ll also notice that a second ERP record was created upon the merging of SpendTest User company and SpendTest. It works this way because Graphite assumes (if you look back at #2 above) that the business requestor has a reason for making the second NSJ for SpendTest.

For other customers, that reason is compelling enough that the creation of a second ERP row was required as part of the config build.  Then, on the rare occasion that these redirects happen incorrectly, the customer can simply delete the extra row.