Upload K-1 to Specific Existing Investment

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

Upload K-1 to an individual investment rather than an instance

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.

K-1 presentation changes from year to year for certain funds, and as a firm we prefer to upload a K-1 straight to an investment instead of using the bulk drag and drop feature. A more versatile upload feature with the API would allow Canoe/Arch users to map out their K-1s to K1x K-1s and automatically send data from the document collection platform to K1x without the risk of creating new investments that previously existed in the instance, but now misconfigured without relevant tags, rollover comments, activity numbers, and investment classifications and adding to the K-1 upload count for billing purposes

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.

Firms with stringent data controls and workflows who still want a no-touch K-1 process

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.

User runs an upload to K-1 GUID command. If additional endpoints are added, my workflow would be that a K-1 hits my document collection platform which I've configured to have K1x IDs in, checks on that K-1's status, if the status is "No Data" then the K-1 is uploaded and the investment is tagged "Uploaded to K1x" in the document system, if the status is Ready for Review because the fund posted a document twice, I don't upload so that I don't end up erasing everything.