Most platforms that call themselves LP onboarding software solve the form-filling layer: a portal where a limited partner uploads a subscription agreement, e-signs, and confirms wire details. That part is largely solved. What stays broken is the compliance work that sits underneath every commitment — identifying the natural persons behind each investing entity, screening them, evidencing where their money came from, rating their risk, and assembling a file an auditor or regulator will accept. That work is still done by hand, in spreadsheets and email threads, by a fund administrator or an in-house compliance officer reading documents one investor at a time.
LP onboarding software has to solve that second layer, or it just moves the bottleneck. A clean e-signature flow does nothing for the analyst who still has to open a passport scan, find the beneficial owners of a Cayman feeder, run each of them through a sanctions and PEP screen, chase a source-of-wealth narrative, decide a risk rating, and write it all down somewhere defensible. Tarth is built for that layer. It is an AI KYC and AML agent that takes each natural person attached to a commitment and does the screening, the source-of-wealth assessment, the risk scoring, and the file assembly — with a citation behind every conclusion.
This page is the canonical reference for what LP onboarding software should do on the compliance side, why it breaks during a close, and how Tarth handles it. If you onboard for a specific firm type, the private equity, venture capital, and fund administrator pages go deeper on each workflow.
What LP onboarding software actually has to solve
An LP commitment is not one person signing a form. It is a chain of legal entities — a family trust, a holding company, a fund-of-funds, a pension mandate, a sovereign vehicle — with natural persons at the end of it who are the real subjects of due diligence. The compliance obligation attaches to those people: the beneficial owners above a disclosure threshold, the directors and authorised signatories, the persons exercising control. LP onboarding software earns its name only if it can take that chain apart and do real work on each person at the end of it.
That work is well defined and it does not change much between funds:
- Identity verification for each natural person — a government ID checked for authenticity, matched to the person, and tied to a verified address.
- Sanctions screening against the lists that apply to the fund’s domicile and the LP’s nationality, with name-matching that survives transliteration and aliases.
- PEP screening to flag politically exposed persons and their close associates, with a defensible reason recorded for every hit dismissed or escalated.
- Adverse-media screening for material negative news, filtered so that a common name does not bury a real signal under noise.
- Source-of-wealth and source-of-funds assessment — not a checkbox, but a reasoned narrative supported by documents that explains how this person accumulated the wealth they are now committing.
- Risk rating that combines all of the above into a score the fund can stand behind, with the inputs visible.
- An audit-ready file that holds the evidence, the screening results, the rationale, and the timestamps together, so a regulator, an auditor, or a depositary can reconstruct the decision later.
Software that stops at document collection leaves every one of these to a human. The volume problem is in the people, not the paperwork.
Why fund onboarding breaks during a close window
Onboarding looks manageable when commitments trickle in one a week. It breaks at a close, when twenty or forty LPs all need to be cleared inside the same narrow window because the fund wants their capital counted in the same closing.
The reason is structural. Each LP brings a chain of entities, and each chain resolves to several natural persons. A single institutional commitment can mean six or eight people to identify and screen. Multiply that across a closing and the compliance team is suddenly holding a few hundred individual screenings, each of which — done properly — means opening documents, running screens, reading hits, and writing a rationale. Outsourced KYC providers add days of turnaround and back-and-forth that the close calendar cannot absorb. Spreadsheets do not scale past the first dozen. The work compresses into the exact week it can least afford to, and either the close slips or the file quality does.
LP onboarding software is supposed to absorb that surge. To actually do it, the screening has to be fast per person and the output has to be consistent regardless of who or how many. That is the design point Tarth is built around.
How Tarth handles LP onboarding end-to-end
Tarth works at the level of the natural person — the unit that the compliance obligation actually attaches to. For each individual behind a commitment, the agent runs the full screening sequence and produces a reasoned, cited result rather than a raw hit list.
- Per-person deep screening. Tarth takes each natural person — an individual LP, a beneficial owner of an investing entity, an authorised signatory — and runs identity verification, sanctions, PEP, and adverse-media screening as one sequence, typically in around ten minutes per person. Every match is reasoned through, not just surfaced.
- Source-of-wealth assessment. The agent reads the documents an investor provides and builds a source-of-wealth narrative against them, flagging where the evidence is thin rather than silently passing it. This is where most manual onboarding is weakest and slowest.
- A risk rating per subject. Tarth produces a customer risk assessment for each person, with the contributing factors visible, so the rating is something the fund can explain rather than a black-box number.
- Citation-backed conclusions. Every screening decision carries the source behind it. A dismissed PEP hit, a cleared sanctions match, a risk score — each links to what it was based on, so the reasoning survives an audit instead of living in someone’s memory.
- An audit-ready file as the output. The result is a structured customer assessment file per subject: identity evidence, screening results, source-of-wealth narrative, risk rating, and rationale, assembled and timestamped. That file is the deliverable, not a by-product. See the anatomy of an audit-ready onboarding file for what goes into it.
- Verification you control. Tarth supports bring-your-own-key and selectable identity verification, so a fund can align onboarding with the identity providers its policy names. Broader screening-vendor and threshold configuration is on the roadmap.
Honest scope note: Tarth 1.0 does deep per-natural-person screening — one person, one file, at a time. Entity-level KYB (verifying the investing company itself), batch or close-mode bulk processing of a full LP register in one pass, cross-fund deduplication so a repeat investor is not re-screened from scratch, and automated ownership-graph tracing through a chain of entities are all on our near-term roadmap, not shipped today. We would rather tell you that than imply a capability that isn’t there yet. For a fund whose hardest problem is doing real, defensible due diligence on each person fast, Tarth solves that now; for one whose hardest problem is bulk-processing a register of entities overnight, the batch and KYB work is what’s coming next.
Fund administrators, GPs, and legal counsel: three different workflows
LP onboarding is run by different people depending on the fund, and the software has to serve each without forcing them into one mould.
A fund administrator runs onboarding at volume, on behalf of many funds at once. Their constraint is throughput and consistency: the same standard applied across every fund they service, with a file that the GP and the auditor will both accept. Per-person screening that produces an identical, cited file every time is what makes that defensible at scale — and the coming batch close-mode is aimed squarely at this workflow. The fund administrator page covers this in detail.
A GP or in-house compliance team owns the relationship and the regulatory exposure. They care that the rating is defensible, that the source-of-wealth work is real, and that they can answer a regulator without reconstructing the file from email. Citation-backed decisions and a structured file are what let them stand behind the onboarding rather than just attest to it.
Legal counsel in fund formation often sits in the CDD chain as well, and needs the onboarding evidence to be clean enough to rely on — particularly source-of-wealth, which is where formation counsel carries real exposure. The same per-person file serves them without a separate process.
Spreadsheets vs. outsourced providers vs. Tarth
| Spreadsheets and manual review | Outsourced KYC provider | Tarth | |
|---|---|---|---|
| Per-person screening | Analyst opens each document, runs each screen by hand | Provider runs screens, returns results to interpret | AI agent runs identity, sanctions, PEP, and adverse media as one cited sequence per person |
| Source of wealth | Written by hand, quality varies by analyst | Often out of scope or charged extra | Agent builds a narrative against the documents and flags thin evidence |
| Turnaround at a close | Compresses into the close week; close slips or quality drops | Days of turnaround plus back-and-forth | Around ten minutes per person, consistent regardless of volume |
| Auditability | Rationale lives in cells, email, and memory | A report you file, not always a reasoned trail | Structured, citation-backed file per subject with timestamps |
| Vendor choice | Whatever the analyst uses | Provider’s fixed stack | Bring-your-own-key with selectable identity verification; broader vendor config on the roadmap |
| Bulk / entity-level KYB | Manual, every time | Sometimes offered | Per-person today; batch close-mode and entity KYB coming next |
Most LP onboarding tools clear the paperwork. The work that actually slows a close is the screening underneath it — and that’s the part Tarth does.
Frequently asked questions
What is LP onboarding software?
LP onboarding software is the system a fund uses to bring a limited partner from commitment to closed. At minimum it handles subscription documents, e-signature, and investor data capture. The harder and more valuable layer is compliance: verifying the identity of each natural person behind the commitment, screening them for sanctions, PEP status, and adverse media, assessing their source of wealth, rating their risk, and assembling an audit-ready file. Tarth focuses on that compliance layer — it is an AI KYC and AML agent that screens each person and produces a cited file, rather than a subscription-document portal.
How is LP onboarding software different from a subscription-document portal?
A subscription-document portal moves the paperwork — forms, signatures, wire details. LP onboarding software in the fuller sense also does the due diligence that sits underneath: who the beneficial owners are, whether they screen clean, where their wealth came from, and how they rate for risk. The two are complementary. A fund can keep its document portal and use Tarth for the screening and file-assembly work that the portal does not touch.
Does Tarth verify the investing entity itself, or just the people behind it?
Today Tarth does deep screening on each natural person — individual LPs, beneficial owners, and authorised signatories — and produces a risk-rated, citation-backed file per person. Entity-level KYB, where the investing company itself is verified and its ownership chain is traced automatically, is on our near-term roadmap rather than shipped in version 1.0. We flag this honestly so funds can match Tarth to what they need now.
Can Tarth handle a full close where many LPs arrive at once?
Tarth screens each person fast — roughly ten minutes per natural person — and the output is consistent no matter how many it runs. That throughput is what helps a close. Batch or close-mode bulk processing, where an entire LP register is pushed through in a single pass, and cross-fund deduplication for repeat investors, are coming next rather than available today. For now Tarth does each subject deeply and quickly; the bulk orchestration layer is on the roadmap.
Why does the audit-ready file matter so much?
Because the question a regulator, auditor, or depositary asks is not “did you onboard them” but “show me why you cleared them.” A file that holds the evidence, the screening results, the source-of-wealth reasoning, the risk rating, and the timestamps together — with a citation behind each conclusion — is what answers that question without a scramble. Tarth produces that file as its primary output. See the anatomy of an audit-ready onboarding file.
Which jurisdictions does Tarth support for LP onboarding?
Tarth is built for cross-jurisdictional fund work, with particular depth in the Gulf and offshore-fund domiciles where its parent operates. The Cayman and ADGM jurisdiction pages set out the specific KYC, AML, and beneficial-ownership requirements Tarth aligns to, citing the relevant regulator sources. Tarth supports bring-your-own-key and selectable identity verification so onboarding aligns with the providers a fund’s policy names.