Private Market Onboarding Checklist for LPs, Founders, and SPVs

Overview

This guide gives you a practical private market onboarding checklist you can return to whenever your deal flow, compliance requirements, or tools evolve. The goal is not to create a one-size-fits-all policy. It is to help you standardize the parts of onboarding that should be consistent, and identify the parts that vary by participant type.

In most venture and private market workflows, onboarding touches several related but distinct tasks:

• Identity verification for the individual you are dealing with
• Business identity verification for an entity such as a fund, startup, family office, or SPV
• Authority verification to confirm the signer can act for the entity
• Risk screening including AML screening, sanctions screening, and PEP screening where relevant
• Document verification for formation records, cap table materials, subscription documents, and signed agreements
• Auditability so your team can show what was collected, checked, approved, and when

A useful onboarding process separates these steps instead of blending them into one broad request. That matters because LP onboarding requirements are different from founder onboarding compliance, and both differ from an SPV verification checklist. If you ask for everything from everyone, you slow down legitimate participants. If you ask for too little, you create avoidable risk.

A simple operating principle helps: verify the person, verify the entity, verify the authority, and verify the risk posture. Then document the decision trail.

If you need a broader primer on how KYC, KYB, and AML fit together in fund and platform operations, see KYC vs KYB vs AML: A Practical Guide for Funds and Platforms.

Checklist by scenario

This section breaks the process into three common scenarios. Treat these as baseline checklists you can adapt by jurisdiction, investor type, fund structure, and internal risk tolerance.

1. LP onboarding checklist

Use this for limited partners, including individuals, family offices, trusts, and institutional entities entering a fund or related vehicle.

• Identify the LP type early. Determine whether the LP is an individual, joint account, trust, fund-of-funds, family office, or corporate entity. The document path changes immediately based on this answer.
• Confirm who the actual decision-maker is. The contact managing the subscription may not be the beneficial owner or final approver.
• Collect core identity proofing information. For individuals, gather the information needed for kyc verification and investor verification, using a process that matches your jurisdiction and risk profile.
• Run relevant screening. Apply AML screening, sanctions screening, and PEP screening to the individual or controlling persons as appropriate.
• For entity LPs, perform kyb verification. Confirm legal name, registration details, operating status, and jurisdiction of incorporation.
• Identify beneficial ownership where required. Map controlling persons and beneficial owners, especially for layered structures and closely held entities. This is where ubo verification and beneficial ownership verification often matter most.
• Verify signatory authority. Confirm the person signing the subscription documents is authorized to bind the entity. Board resolutions, delegated authority documents, or equivalent records may be needed.
• Validate accreditation or eligibility if your workflow requires it. If you are handling investor accreditation verification or related eligibility checks, define the evidence standard in advance instead of improvising case by case.
• Review source consistency. Names, addresses, entity names, and registration numbers should match across subscription docs, formation records, and screening outputs.
• Store an audit trail. Preserve the evidence collected, the decision taken, any exceptions approved, and who approved them.

Investor portals often fail not because they lack a form, but because they lack clear branching logic for different investor types. If your process is portal-based, review Digital Identity Verification for Investor Portals: Features, Risks, and Requirements.

2. Founder onboarding compliance checklist

Use this when a founder, executive team, or startup entity is entering your diligence, investment, banking, lending, or platform workflow.

• Verify the founder as an individual. Apply identity verification appropriate to the stage of the relationship. At minimum, confirm you are dealing with a real person and preserve the evidence used.
• Verify the startup as a legal entity. Confirm corporate registration records, jurisdiction, legal name, and current status.
• Check the relationship between person and company. A founder may present themselves as authorized before formal paperwork is complete. Confirm title, role, and authority to provide records or sign agreements.
• Review formation and governance documents. Depending on the transaction, that may include certificates of incorporation, operating agreements, bylaws, board consents, or other authorization records.
• Check cap table support materials. If ownership claims affect the transaction, verify that the cap table, option pool details, and issued securities records are internally consistent.
• Screen for sanctions and risk indicators. Risk screening is not just for investors. Founders and startup entities can also create onboarding risk where names, jurisdictions, or ownership structures raise questions.
• Assess document integrity. Document verification should include basic fraud checks such as mismatched dates, signatures that do not align with authority records, altered PDFs, or unexplained discrepancies between versions.
• Document exceptions. Early-stage companies are often imperfect on paperwork. The key is to separate tolerable incompleteness from unresolved identity or authority risk.
• Escalate red flags instead of working around them. If formation records, cap table claims, or signatory authority do not line up, pause and resolve them before moving forward.

Two related resources can help tighten this workflow: How to Verify Corporate Registration Records Across Major Startup Jurisdictions and How to Verify a Startup Cap Table During Due Diligence.

3. SPV verification checklist

SPVs create a special onboarding challenge because they sit between individuals and funds. They are often simple in concept but messy in practice, especially when timelines are compressed.

• Confirm the SPV structure. Identify the legal form, jurisdiction, manager or GP, and whether the SPV is newly formed or already active.
• Perform business identity verification on the SPV. Validate formation records, registration details, and active status.
• Verify the manager, GP, or controlling entity. The SPV itself may be thinly documented, so the control chain matters.
• Map beneficial ownership and control. Determine who ultimately controls the vehicle and whether any layered entity structure requires additional review.
• Confirm banking and payment alignment. Ensure the account receiving or sending funds matches the legal entity and authorized operating arrangement.
• Verify signer authority. Subscription packets, side letters, and transaction approvals should be signed by a person whose authority can be shown.
• Screen the relevant parties. Depending on your process, that may include the SPV, its manager, control persons, and in some cases look-through participants.
• Check offering and investor communication documents for consistency. Names, legal entities, and economics should align across summary materials, legal docs, and payment instructions.
• Set a refresh rule. SPVs often reappear for follow-ons, warehousing, or side transactions. Decide in advance what expires and what can be reused.

Where authority questions come up, use a structured review process rather than relying on email explanations. A helpful companion is Board Consent, Signatory Authority, and Entity Authorization Checklist.

4. Cross-scenario workflow checklist

No matter who you onboard, the workflow itself should be standardized.

• Define required fields and required evidence by participant type.
• Use consistent naming conventions across forms, CRM, and document storage.
• Separate automated checks from analyst review steps.
• Define escalation paths for mismatches, high-risk screening results, and missing authority documents.
• Record timestamps, reviewer actions, and final decisions.
• Minimize data collection. Privacy-first authentication and gdpr identity verification practices start by not collecting more than you need.
• Design for integration. If data has to move into a CRM, investor portal, or compliance system, build the mapping before launch rather than after exceptions appear.

If you are comparing tools or planning a verification API rollout, start with Verification API Evaluation Checklist for Regulated Onboarding Flows.

What to double-check

Before approving onboarding, pause on these items. They are common sources of avoidable mistakes in venture fund onboarding and private market compliance workflows.

• Name mismatches. Check whether the legal entity name, trade name, and signed name are being treated as if they were the same thing.
• Stale documents. Good onboarding files age quickly. Formation records, authority evidence, and screening results may need refreshes based on your policy and risk level.
• Authority assumptions. A founder, fund manager, or finance lead may appear to be the obvious signer, but your file should show why they are authorized.
• Layered ownership. Do not stop at the first entity in the chain if your process requires beneficial ownership verification or risk review of controlling persons.
• Jurisdiction-specific differences. Entity documents and registry records vary. Your checklist should define what equivalent evidence is acceptable when standard documents do not exist.
• Document quality issues. Missing pages, cropped scans, inconsistent dates, and unsigned attachments are small warnings that often point to larger process gaps.
• Manual overrides. Exceptions are normal, but they should be documented. Untracked overrides are one of the fastest ways to weaken a verification program.

For document collection standards, see Business Identity Verification Documents: What to Collect and When. For evidence preservation, see How to Design an Audit Trail for Identity and Business Verification.

Common mistakes

The biggest onboarding problems in private markets are usually operational, not theoretical. Teams know they need digital identity verification and document review. The trouble is that the process remains informal until scale exposes the gaps.

• Using one checklist for every participant. LPs, founders, and SPVs should not all receive the same request list.
• Confusing KYC with KYB. Verifying a person does not verify the entity they represent, and verifying an entity does not prove the signer has authority.
• Requesting too much too early. Over-collecting data creates friction, privacy risk, and unnecessary review workload.
• Ignoring ownership and control complexity. The more layered the structure, the more important it is to define where your look-through obligations and risk reviews stop.
• Accepting screenshots and summaries in place of source documents. Convenience should not replace evidence for key legal and identity claims.
• Relying on memory for exceptions. If an unusual approval cannot be reconstructed later, it was not handled well enough.
• Building workflows around the current team instead of a durable process. Good onboarding survives role changes, tool changes, and seasonal surges.

A useful habit is to maintain a red-flag list tied to your own workflow. A starting point is Red Flags in Startup Verification: A Due Diligence Warning Signs List.

When to revisit

This checklist is most valuable when it is reviewed before activity increases, not after a deal stalls. Revisit your onboarding standards in these situations:

• Before seasonal planning cycles. If you expect a new fundraise, a heavier diligence period, or more SPV activity, review your required evidence list and approval paths in advance.
• When workflows or tools change. A new portal, CRM, data source, verification api, or document collection flow can quietly introduce gaps.
• When you enter a new jurisdiction or participant segment. International founders, non-US investors, trusts, and layered entities often require adjusted evidence standards.
• When internal ownership changes. If legal, compliance, investor relations, or operations teams shift responsibilities, confirm who owns each approval step.
• After exceptions cluster. If your team keeps making the same manual override, the checklist is probably missing a real scenario.

To turn this into an action plan, do the following:

1. Create three separate intake paths: LP, founder, and SPV.
2. For each path, define required person, entity, authority, and screening checks.
3. Set a refresh rule for time-sensitive items such as screening results and authority evidence.
4. Assign one owner for policy and one owner for workflow operations.
5. Run a file review on your last five onboardings and note where exceptions were handled informally.
6. Update your templates, portal logic, and internal SOPs before the next volume spike.

If you are also reviewing vendors, security posture should be part of the decision. This checklist pairs well with SOC 2 Questions to Ask an Identity Verification Vendor.

The best private market onboarding process is not the one with the most steps. It is the one that consistently proves identity, entity legitimacy, authority, and risk review without collecting unnecessary data or improvising under deadline. That is what makes the checklist worth revisiting: your participants change, your tools change, and your standard should remain clear.