Insights
6 min readNov 2, 2026

What KYC documents does an incoming LP need to provide in a transfer?

An incoming limited partner (LP) will usually be asked for identification and information about its legal status and how the acquisition will be funded. An entity investor may also need to explain its ownership and control structure. The precise know-your-customer (KYC) requirements vary widely between funds, depending on the applicable regulations, jurisdictions and investor circumstances.

Most of the time lost in KYC goes on chasing. A request goes out, part of the pack comes back, and someone works out what is still missing. The next request starts another round of correspondence. Across several investors and transactions, the fund's team can spend considerable time keeping those exchanges moving.

What KYC documents does an incoming LP need to provide?

The fund's team or the service provider handling KYC should confirm the checklist. The documents below are common examples; a fund may require different evidence, certification or more recent copies.

Investor typeDocuments and information that may be requested
IndividualA passport or national identity card, proof of residential address, and information or evidence about the source of funds or wealth
EntityFormation and governing documents, an ownership chart, information about relevant owners and controlling persons, and evidence of signing authority. Supporting identity documents and information about how the acquisition is funded may also be required

The onboarding pack may also include tax forms, such as the appropriate Form W-8 or W-9, and Common Reporting Standard (CRS) self-certifications. These help the fund establish the investor's tax status and meet its reporting and, where relevant, withholding obligations.

The checklist needs to be specific enough for the investor to act on it. Asking for proof of address without saying how recent it must be, or requesting identification without explaining the certification requirements, leaves room for another exchange when the documents arrive.

Why does KYC take so long on an LP transfer?

Consider an investor that supplies an ownership chart but leaves out supporting documents for one of the entities in the chain. The reviewer identifies the gap and sends a request. The investor passes it to the person who holds the documents. When the response comes back, someone has to check it and establish whether the file is now complete.

Much of that time is spent waiting for a response, with several people having to pick up the file along the way. An unsigned form or an out-of-date document can set off the same sequence.

The person managing the transfer also has to keep track of what has happened. A response may arrive in a different email thread, or a document may be uploaded without anyone recording whether it has been accepted. Before sending the next chaser, someone has to reconcile the correspondence with the checklist. Otherwise, the investor may be asked again for something it has already provided.

This is the work between reviews: finding the latest response, checking what remains outstanding and making sure the next action happens. It absorbs time on both sides of the transaction and can continue after the transfer documents have been agreed. Our guide to the LP transfer process explains how KYC fits alongside the other closing requirements.

Why are investors asked for the same KYC documents again?

Some repeat requests have a straightforward explanation. A different fund or administrator may apply different requirements. A document accepted for an earlier investment may need updating or further supporting evidence for the current review.

Other requests come from an incomplete record. The investor's lawyer has emailed a certificate, identification has gone into a portal and an ownership chart is sitting in another thread. The person following up may have only part of the picture.

The LP has to spend time on every request, including those caused by documents already sitting in the fund team's correspondence. Someone on the investor's side must find the earlier submission, check whether anything has changed and explain what has already been provided.

Repeated unexplained requests can make a well-run fund look disorganised. The frustration can reach the manager even when an adviser or administrator is doing the chasing. At a primary closing, this may be one of the LP's first experiences of working with the fund; on a transfer, it adds friction to an acquisition or exit.

When does KYC need to be refreshed?

KYC can require further attention during the life of an investment. A fund may ask an existing investor to confirm that its information remains accurate or provide updated evidence, including following a change in ownership or control. The timing and scope of a KYC refresh depend on the applicable rules, the investor and the fund's procedures.

A delayed transfer can create the same problem before closing. An identity document may expire, or proof of address may fall outside the period accepted by the reviewer. A delay elsewhere in the transaction can therefore create new KYC work on a file that appeared complete.

A useful refresh starts with the existing file. The team needs to establish what is still usable, what has changed and what must be obtained again. Without that comparison, it can end up repeating much of the original collection exercise.

How can a fund spend less time chasing KYC?

A clear initial checklist helps the investor assemble the right documents. After that, the fund needs a reliable record of each request, the response and the review decision. An uploaded document should be distinguishable from an item that has been accepted.

Follow-ups should reflect that record. Before asking the investor for anything further, check what has arrived and bring the remaining questions together. The timing should also reflect the expected closing date: a file with several weeks to run needs a different follow-up schedule from one holding up an imminent closing.

How can Sam help manage KYC?

In LP Transfers on Navys, each KYC request keeps its response, supporting documents and follow-up questions together. The fund's team can see what is awaiting a response, in progress or approved. The incoming LP's KYC documents are not visible to the outgoing LP's team.

Sam, our AI associate for fund operations, already updates KYC status in the Intelligent Fundraising Tracker from correspondence copied to it. Each change links to its source email. Sam tracks KYC status for each leg of a portfolio sale on the same basis.

Sam also handles the follow-up work. Sam checks submissions against the fund's requirements and flags missing documents or information for human attention. The fund decides which messages Sam is authorised to send.

For example, Sam can chase every few days early in the process and more frequently as closing approaches. As replies arrive, Sam checks what they resolve and updates the outstanding items. If a document needs refreshing or a response leaves a question unanswered, Sam brings it to the reviewer's attention. Each chaser reflects what is still needed, taking account of the LP's earlier replies.

The person responsible for KYC decides whether the file is satisfactory. Sam keeps the requests, responses and next actions in order, so the reviewer has the current file without having to piece it together from an inbox.

The True Cost of LP Transfers examines the costs of the wider process. Request a demo to see how Navys manages KYC within a transfer.