From the desk:Investor Relations (For Syndicators)

K-1 season starts in six weeks and 340 LPs still live in spreadsheets

We took on a sponsor client in July whose entire investor record lives in spreadsheets plus a shared drive. 340 unique LPs, 11 deal entities, three of them from 2018 and 2019 vintages that are still holding.

What the data actually looks like after two weeks of cleanup:

62 of the LPs invest through trusts or LLCs, and 19 of those have the investing entity name spelled differently across subscription docs, distribution records, and the tax package
8 LPs appear twice under married and maiden names
4 subscription agreements are missing signature pages entirely on the 2019 entity
ACH detail exists in a separate spreadsheet the sponsor's bookkeeper maintains and it does not reconcile to the investor list on 11 rows

Platform quote is $6,200 implementation plus $1.15 per investor per month, so call it $4,700 a year in subscription on current count. Sponsor is fine with the money. The question is timing.

Option A is cut over November 1, so the year-end statement and the K-1 delivery both go out through the new portal and LPs get one clean experience. That means my team does data validation and tax package coordination in the same six weeks.

Option B is cut over February 1 after K-1s land, run the old spreadsheets through one more distribution cycle, and eat a year where LPs get statements from one system and tax docs from another.

I have a two-person team plus me. Quarter-end already runs long. I lean toward B and my client leans toward A because he's told his LPs a portal is coming.

What would you check before choosing? Genuinely unsure which failure is worse here, a rough cutover or a broken promise that slips a quarter.

Answer

0tonyv88SO4CPRO6

B, and it isn't close from where I sit. I've done three of these on the property management side and the thing that burns you is never the interface, it's money and tax IDs.

Your 11 unreconciled ACH rows are the whole answer. If you cut over November 1 and one distribution lands in the wrong account or one 1099 or K-1 goes out under a mismatched tax ID, you have spent your client's investor trust to save four months. Investors forgive a delayed portal. They do not forgive a payment that went somewhere else, and they tell each other about it.

What I'd do in your six weeks instead of a migration:

Get every one of the 62 entity investors to confirm the legal name and tax ID in writing, on a one-page form, signed. Not an email reply, a form. That gives your client a clean record and it gives you cover if the historic docs are wrong. The 19 mismatches are probably 15 typos and 4 real problems where the money went in under one entity and the docs name another, and those 4 need the sponsor's attorney and accountant, not you.

Run the December distribution and the K-1s on the system that already works, however ugly it is. Then load the cleaned data in January, run January and April in parallel with the spreadsheets, and invite LPs in May once you've seen two clean cycles.

On the broken promise, that's a communication problem you can solve for free. Have the sponsor tell LPs the portal arrives in Q2 and that the delay is so their tax documents and banking detail get verified first. Investors read that as care. I've never seen anyone complain about that sentence.

3 replies

-1sonia_alvarez Get yoursPRO6

Two things from the LP seat, since I've been on the receiving end of one of these.

A sponsor I'm in switched portals mid-year and I ended up with two logins, a statement in each, and numbers that disagreed by about $1,900 on my capital account because the old system had been netting a fee the new one itemized. Nobody could tell me which was right for five weeks. That was the moment I stopped assuming they knew where my money was. So trellis is right about parallel running, and I'd add: reconcile every capital account balance to the penny across both systems before an LP ever sees the new one.

Second, ask the platform now, in writing, what happens to the data if the sponsor leaves. Export format, whether historic statements come with it, whether documents come as a zip or you have to click 340 times. You're the one who'd have to rebuild it.

2nicole_adeyemiPassivePRO5

Different angle. Why are you migrating the 2018 and 2019 entities at all?

Those are holds that will exit on their own schedule. The LPs in them already have years of statements in whatever format they've been getting. Leave them where they are, run them to exit on the spreadsheets, and put the newer entities and everything going forward on the portal. You cut the migration scope by three entities and probably most of your name mismatches, since old vintages are where the sloppy paperwork lives.

And the four missing signature pages are a bigger deal than either of your options. An investor whose subscription agreement isn't fully executed is a problem sitting there whether or not there's a portal, and that one is for the sponsor's securities counsel this month, not for your cutover plan. I'd put that in writing to the client today so it's clearly not sitting on your desk.