K1N Tiering: Match by EIN

Describe your idea. The more information you provide, the clearer picture of your idea we will have.

1. Tiering suggestion instead of matching name and address (I might not clearly understand what is matched)

   1. For tiering when setting up entities in a group

2. When setting it up I believe I had something different between the GP address in the fund and in the actual GP entity

3. Is it possible to have the system check the EIN and not anything else?

4. 1. 1. 1. Multiple entities should not be sharing the same EIN – this would prevent issues like I had in one Project where there was a missing comma in a name or address (at least that’s what I think the issue was, I may be mistaken here)

How will this idea help you and potentially others? Understanding how things are done today, where the pain is, and how the idea is beneficial puts us in your shoes.

Doesn't make sense to match on variable information. Should match on static information like EIN/SSN

Who will benefit from this idea? Whether it's specific roles of users, users of a specific product, or certain departments/markets, this helps us know who to talk to when we need more information.

Everyone

How do you envision this idea being implemented at K1x? You're the expert and understanding how you see this working helps kickstart the idea.

Match on EIN/SSN