What Are Distribution Notices?
A distribution notice is a formal written communication issued by a private fund’s general partner to its limited partners, notifying each LP of an upcoming or completed distribution of cash or securities from the fund. Distribution notices detail the total amount being distributed, each LP’s individual share, the nature of the distribution (return of capital, realized gain, income, or a combination), the method and timing of payment, and any carried interest or management fee offsets applied before the distribution reaches LPs.
Distributions are the moment LPs actually receive returns from their fund investment. They are triggered by liquidity events — a portfolio company sale or IPO, a real estate asset disposition, a loan repayment in a private credit fund, or a dividend recapitalization — and the distribution notice is the formal document that communicates what each LP will receive, and why.
Unlike capital call notices, which flow from LP to fund, distribution notices represent capital flowing from the fund back to LPs. This makes them among the most anticipated investor communications a GP produces — and among the most scrutinized. LPs will reconcile their distribution against their capital account, verify that carried interest has been calculated correctly, and confirm that their return of capital versus realized gain breakdown is accurate for their own tax and accounting purposes.
Distribution notices are governed by the fund’s LPA, which specifies the distribution waterfall:
the exact sequence and priority in which proceeds are allocated among return of capital, preferred return, GP catch-up, and carried interest. The notice must reflect this waterfall precisely — making distribution notice generation one of the most calculation-intensive, legally significant investor reporting processes a fund undertakes.
Why Firms Use Distribution Notices
Distribution notices serve operational, legal, and investor relations purposes across the fund lifecycle:
- LP Contractual Entitlement. The LPA specifies that LPs must receive notice of distributions within a defined period — typically simultaneously with or immediately prior to the wire transfer. Failing to issue a proper distribution notice is a breach of the fund’s governing documents.
- Capital Account Reconciliation. LPs use distribution notices to reconcile their own capital account records. The notice must clearly show how much of the distribution represents return of capital (reducing the LP’s cost basis) versus realized gain — a distinction that matters significantly for the LP’s own accounting and tax reporting.
- Waterfall Transparency. LPs and their auditors expect to see how the distribution waterfall was applied — how much went to return capital, how much satisfied the preferred return, how much was allocated to the GP catch-up, and how much represents carried interest paid to the GP. Transparency in waterfall calculations is a core LP expectation and increasingly an LPA requirement.
- Tax Reporting Support. Distributions of realized gains, income, and return of capital have different tax treatment for LPs. The distribution notice — along with subsequent Schedule K-1s — provides the foundational documentation LPs need to characterize the distribution correctly for their own tax filings.
- Investor Relations. Distributions are the most positive event in the LP-GP relationship. A clear, professionally produced distribution notice reinforces the GP’s credibility and operational competence at the moment LPs are most engaged with their fund investment.
- Audit Documentation. Auditors review distribution notices, supporting waterfall calculations, and bank wire confirmations as part of the annual fund audit. A clean, systematic distribution notice process with a complete audit trail reduces audit friction significantly.
Common KPIs and Calculations
Distribution notices require precise calculations at both the fund level and individual LP level, incorporating waterfall logic, carried interest, and capital account history. Common data points and calculations include:
Fund-Level Distribution Data
- Total Gross Proceeds (sale proceeds, dividend, or loan repayment before fund-level expenses)
- Fund-Level Transaction Costs and Expenses Deducted
- Total Net Distributable Proceeds
- Distribution Date and Payment Method (wire transfer, check, in-kind securities)
- Portfolio Company / Asset Being Realized
- Investment Cost Basis (for gain/loss calculation)
- Realized Gain / Loss on Investment
- Distribution Number / Sequential Identifier
Waterfall Allocation Sequence
- Step 1: Return of LP Capital Contributions (until all contributed capital is returned)
- Step 2: Preferred Return / Hurdle Rate (typically 8% per annum on unreturned capital)
- Step 3: GP Catch-Up (GP receives a disproportionate share until it has received its carry percentage of total profits)
- Step 4: Carried Interest Split (typically 80% LP / 20% GP on remaining profits)
- Clawback Calculation (GP obligation to return excess carry if total carry exceeds LPA entitlement)
- European vs. American Waterfall Distinction (deal-by-deal vs. whole-fund carry)
LP-Level Distribution Data
- LP Pro-Rata Share of Return of Capital
- LP Pro-Rata Share of Preferred Return
- LP Pro-Rata Share of Profits (after carried interest)
- LP Total Distribution Amount
- LP Cumulative Distributions to Date (inception-to-date DPI numerator)
- LP Remaining Unreturned Capital (post-distribution)
- LP Updated Capital Account Balance (post-distribution NAV)
- LP Management Fee Offset Credits Applied
Performance Metrics Updated by Distribution
- DPI (Distributions to Paid-In) — updated at LP and fund level
- TVPI (Total Value to Paid-In) — updated to reflect realized + remaining unrealized
- IRR (updated with distribution date and amount as a cash flow)
- Realized Multiple on Investment (gross MoM on specific portfolio company exit)
Common Filters and Parameters
Distribution notice reports must be parameterizable across multiple fund structures, LP classes, and distribution types. Common parameters include:
- Fund / Entity — Main fund, parallel vehicle, co-investment vehicle, feeder fund
- Distribution Number — Sequential identifier for audit trail and LP reconciliation
- Distribution Date — Date proceeds are wired or paid to LPs
- Portfolio Company / Asset — Investment being realized (for single-asset distributions)
- Distribution Type — Return of capital, realized gain, income, in-kind securities, or combined
- Waterfall Method — European (whole-fund), American (deal-by-deal), or hybrid
- LP Subset — All LPs, specific LP class, co-investment participants only
- Currency — USD, EUR, GBP, or multi-currency for parallel vehicles
- Carry Status — Accrued carry vs. realized carry (cash carry vs. paper carry)
- Clawback Reserve — Whether a GP clawback holdback
Common Reporting Challenges
Producing distribution notices accurately, on time, and in full compliance with LPA waterfall terms is one of the most technically demanding investor reporting processes in fund administration. Common challenges include:
Waterfall Complexity
No two fund waterfall structures are identical. European waterfalls, American waterfalls, hybrid structures, deal-by-deal carry with loss carryforwards, tiered carried interest rates, and LP-specific side letter modifications all create unique calculation complexity. Even experienced fund accountants can introduce errors when applying waterfall logic manually in Excel, particularly for funds with long operating histories and many prior distributions.
Preferred Return Accrual Tracking
The preferred return — typically 8% per annum — accrues on each LP's unreturned capital contributions from the date of each capital call. Calculating the exact preferred return balance at the time of each distribution requires tracking every historical capital call, its date, the amount called, and the running preferred return accrual. This is inherently an inception-to-date calculation that grows in complexity with every additional call and distribution.
Carry and Clawback Sensitivity
Carried interest calculations are among the most scrutinized numbers in any distribution notice. LPs and their advisors will review the carry calculation in detail. Errors — even small ones — create LP complaints, require restatements, and can trigger legal disputes. In clawback situations, the GP must also track cumulative carry received vs. LPA entitlement across the entire fund life, which requires a complete historical record of every prior distribution.
In-Kind Distributions
When a fund distributes securities rather than cash — shares in a public company post-IPO lock-up, for example — the distribution notice must specify the number of shares, the valuation date and per-share price used, and how shares are allocated to each LP. Inkind distributions create additional complexity around custody, broker delivery instructions, and tax lot tracking.
Multi-Asset and Partial Realizations
When a fund partially exits an investment — selling a portion of its stake rather than the full position — the distribution notice must clearly identify the realized portion vs. the remaining holding, and update the LP's capital account accordingly without closing out the investment entirely.
Volume of LP Notices
As with capital call notices, every LP must receive an individualized distribution notice reflecting their specific allocation, their specific capital account history, and their specific wire payment details. For large LP rosters, manual production of individualized notices is slow, error-prone, and unsustainable at scale.
Timing Coordination
Distribution notices must typically be issued simultaneously with or immediately before the wire transfer. This creates tight coordination requirements between the fund accounting team, the fund's bank, and the investor relations team — all of which must be synchronized within a narrow window.
Tax Characterization Accuracy
The breakdown of a distribution into return of capital, longterm capital gain, short-term capital gain, and ordinary income must be accurate, as LPs rely on this characterization for their own tax reporting. Errors discovered after delivery require amended notices and create LP relations problems.
Automation and Scheduling Options
ReportingGuru builds automated distribution notice systems that replace manual waterfall spreadsheets and PDF production with scalable, auditable, systematic workflows.
- Automated Waterfall Calculation Engine. We build SQL Server-based waterfall calculation models that apply your fund’s specific distribution waterfall — European, American, or hybrid — with full support for preferred return accrual tracking, GP catch-up, tiered carry rates, and LPlevel side letter modifications. When a distribution is triggered, the engine calculates every LP’s share automatically from the full capital account history.
- Preferred Return Accrual Tracking. We build inception-to-date preferred return accrual models that track every historical capital call by date and amount, calculate the daily preferred return accrual on unreturned capital, and produce the exact preferred return balance for each LP at the time of each distribution — eliminating the manual spreadsheet calculations that are the most common source of distribution errors.
- Parameterized Notice Generation. Using SSRS or Crystal Reports, we build distribution notice templates that pull directly from the waterfall calculation engine. Each LP’s notice is generated automatically with the correct distribution amount, correct waterfall breakdown, correct capital account update, and correct return of capital vs. gain characterization.
- Batch PDF Generation. For funds with large LP rosters, we build batch generation pipelines that produce all individualized distribution notice PDFs in a single run — each one named, formatted, and ready for delivery.
- Draft and Final Approval Workflow. Draft distribution notices are generated and routed to internal reviewers — CFO, controller, legal counsel — for validation of waterfall calculations and LP amounts before any notice is issued. Final notices are generated only after approval, creating a clean audit trail.
- Automated Email Delivery. Once approved, the system can automatically email each LP’s distribution notice to their designated contacts — with LP-specific subject lines, cover language, and PDF attachments — timed to coordinate with the wire transfer date.
- Investor Portal Publishing. Distribution notices are published directly to the investor portal at the time of issuance, giving LPs immediate access and building a searchable archive of all historical distributions.
- Post-Distribution Capital Account Update. We integrate distribution notice generation with automated capital account update workflows — so that when a distribution is processed, LP capital account balances, DPI metrics, and unfunded commitment records are all updated simultaneously.
Delivery Methods
ReportingGuru delivers distribution notice automation across the platforms your team already uses:
SSRS (SQL Server Reporting Services)
SSRS is the most effective platform for automated distribution notice generation in fund administration environments. We design SSRS report templates that render each LP's notice with accurate distribution amounts, waterfall breakdowns, capital account summaries, and fund branding. SSRS data-driven subscriptions generate all LP notices in a single batch run and can distribute them automatically by email. For fund administrators on SQL Server, SSRS provides the fastest path to a fully automated distribution notice workflow.
Crystal Reports
Many fund administrators generate distribution notices from Crystal Reports templates connected to legacy fund accounting systems. ReportingGuru modernizes Crystal Reports-based distribution notice packages — updating waterfall calculation logic, improving data connectivity, and migrating to SSRS or Power BI where the technology stack supports it.
Power BI
For fund managers who want dashboard visibility into distribution activity — cumulative DPI by fund, LP distribution history, waterfall allocation summaries, and realized return benchmarking — Power BI provides a powerful analytical layer alongside transactional notice generation. Power BI Embedded can surface distribution history and performance metrics directly inside an investor portal.
Excel and Excel Automation
Some fund administrators maintain Excel-based waterfall models as their primary calculation and review tool. We build Excel distribution workbooks driven by live SQL Server data, with automated population of LP allocation schedules and waterfall step outputs — eliminating manual data entry and reducing the risk of formula errors in high-stakes calculations.
Scheduled PDF / Email Delivery
For teams distributing notices by email, we build automated delivery pipelines that generate, name, and send individualized PDFs on demand — with LP-specific distribution lists, delivery logs, and confirmation tracking.
Investor Portal Integration
We integrate distribution notice publishing with leading investor portal platforms — Allvue, Juniper Square, and custom portals — ensuring LPs receive immediate access to current and historical distribution notices through a single, self-service interface.
Frequently Asked Questions
How does ReportingGuru handle the preferred return accrual calculation?
We build an inception-to-date preferred return model in SQL Server that tracks every historical capital call by date, calculates the daily preferred return accrual on each LP’s unreturned contributed capital, and produces the exact preferred return balance at the time of any distribution. This eliminates the manual spreadsheet accrual calculations that are the most common source of distribution notice errors.
Can the system handle both European and American waterfall structures?
Yes. We build waterfall calculation engines that support European (whole-fund) waterfalls, American (dealby-deal) waterfalls, and hybrid structures. The waterfall logic is configured in SQL Server as fund-level parameters — not hard-coded — so different funds in your portfolio can run different waterfall structures from the same system.
How are clawback obligations tracked and reported?
We build cumulative carry tracking models that record every carry payment made across the fund’s history and compare it to the LP’s current entitlement based on total realized proceeds. If cumulative carry exceeds entitlement at any distribution, the system flags a clawback obligation and calculates the GP’s repayment amount per the LPA terms.
Can you handle in-kind security distributions?
Yes. We build in-kind distribution notice templates that specify share quantities, valuation dates, per-share prices, and LP-level share allocations — along with the supporting calculations that determine how shares are allocated across LPs based on their pro-rata interest.
We have LPs with side letter modifications to the standard waterfall. Can these be accommodated?
Yes. LP-specific waterfall modifications — different carry rates, different hurdle rates, management fee discounts, or preferred return structures — are stored as LP-level configuration data in SQL Server and applied automatically during the waterfall calculation for each distribution.
How quickly can distribution notices be generated once the distribution amount is approved?
With an automated system in place, all LP waterfall calculations are run and individualized notice PDFs are generated within minutes of the distribution amount being finalized and approved. Manual processes that previously took one to two days of spreadsheet work are reduced to a review-and-approve workflow.
Can distribution performance metrics — DPI, IRR — be updated automatically when a distribution is processed?
Yes. We build post-distribution automation that updates LP-level and fund-level DPI, TVPI, and IRR calculations simultaneously with the distribution notice generation — so your investor reporting metrics are always current after each liquidity event.