A GP's Guide to the New ILPA Reporting Standards

In 2025, the Institutional Limited Partners Association (ILPA) completed a comprehensive overhaul of its quarterly reporting standards, releasing three updated templates: a revised Reporting Template covering fees, expenses, and carried interest; a new Performance Template standardizing how GPs calculate and present fund returns; and an updated Capital Call & Distribution Template establishing new requirements for capital activity notices. Together, they set a new baseline for investor reporting — one that requires more granular, structured data and seamless reconciliation across all investor communications, and necessitates a strategic review of current fund operations.

The three-template overhaul follows the same logic as the SEC's push several years ago to standardize investment returns calculations across funds, reduce inconsistency, lock down the flexibility that prior templates allowed, and bring greater alignment across all frameworks. The updated Reporting Template replaces the 2016 version and addresses fee, expense, and carried interest disclosure. The new Performance Template introduces standardized return calculation methodologies. And the updated Capital Call & Distribution Template, released in September 2025, replaces the 2011 version and aligns capital activity reporting with the broader suite.

The core principle running across all three is that capital activity notices, quarterly reports, and capital account statements must reconcile perfectly, requiring that all investor communications originate from a single, structured data source. For institutional GPs, this is not optional. It is the new baseline that LPs will expect, and firms that cannot produce the updated templates at scale will face friction with existing investors and credibility issues during fundraising.

The 2025 update moves beyond high-level summaries to require detailed, transaction-level data that many GPs do not currently produce. PDFs and manually assembled reports are no longer sufficient. Every capital call and distribution notice must now be accompanied by structured, machine-readable data.

Itemized transaction data

• Requirement: Detailed breakdowns of capital activity, including specific capital call types—classified according to a standardized taxonomy, not firm-defined categories.
• Impact: Fund administrators and managers must adopt granular transaction recording processes aligned to ILPA's prescribed taxonomy. This leaves little room for the interpretive flexibility that prior templates allowed. In practice, remapping to a standardized taxonomy is more involved than it sounds—it typically requires firms to audit every transaction type currently in use, reconcile them against ILPA's definitions, and update coding logic across their accounting and reporting systems. For firms running on legacy infrastructure or custom-built workflows, this process can take months and often surfaces inconsistencies that have accumulated quietly over multiple fund cycles.

Transaction classification

• Requirement: Each transaction must be classified as occurring "inside" or "outside" the fund structure.
• Impact: This classification directly affects how capital flows are categorized and reported to LPs, and it's one of the more operationally complex elements of the new template. Many existing accounting processes were not designed to consistently capture this distinction, potentially requiring updates to transaction coding, capital event tracking, and reporting logic. Firms that have historically treated this as a footnote will need to revisit how transactions are coded at the source.

Standardized LP commitment reconciliation

• Requirement: A standardized format for reconciling each LP's unfunded commitment, aligned across the updated ILPA Reporting Templates.
• Impact: In practice, many finance teams currently generate capital call notices, investor statements, and performance reports from separate spreadsheets or disconnected systems. The new ILPA standard assumes these outputs will reconcile automatically, which means firms will need tighter integration between their accounting records and investor reporting workflows. For many GPs, achieving this level of consistency will require either significant process changes or investment in purpose-built technology.

Cross-report reconciliation

• Requirement: Capital call notices, distribution notices, quarterly reports, capital account statements, and ILPA templates must reconcile perfectly with one another.
• Impact: This is a meaningful operational lift. Firms that manage reporting across multiple systems or rely on manual aggregation will face the greatest exposure. A discrepancy in any one report has downstream implications for all the others, making data integrity and workflow integration more critical than ever.

Alignment across ILPA reporting templates

• Requirement: Definitions, classifications, and data formats must be consistent across the full suite of ILPA templates, not just within individual reports.
• Impact: GPs can no longer treat each template in isolation. Terminology and transaction classifications used in the ILPA Reporting Template must align with how the same data appears in capital account statements and quarterly reports. Inconsistencies that were previously tolerated will become compliance gaps.

LP data integration

• Requirement: Reporting must be delivered in structured formats that LPs can ingest directly into their own reporting systems.
• Impact: The shift to machine-readable outputs isn't just a formatting preference; it reflects how institutional LPs now expect to receive and process data. Firms still delivering PDFs or unstructured exports will face increasing friction with sophisticated investors and may find themselves at a disadvantage in fundraising conversations where operational credibility matters.

Fee and reporting template revisions

• Requirement: Updates to the ILPA Reporting Template with new definitions and stricter fee and expense reporting standards.
• Impact: The fee template changes are more specific than the headline suggests. Gross-to-net management fee reconciliations must now account for offsets, waivers, and rebates. Carried interest reporting must consolidate accrued, earned, and paid carry into a single reconciliation. Internal chargebacks must be clearly separated from third-party costs. And unlike prior versions of the template, ILPA has eliminated customization entirely—there is no longer flexibility to adapt the template to a firm's existing reporting conventions. Every GP is now working from the same structure, which means firms that built fee reporting around their own definitions will need to remap, not just reformat.

The message is clear: firms that rely on manual processes or loosely structured data will struggle to comply at scale. This update isn't just a reporting change; it's a signal that GPs who haven't modernized their data infrastructure need to move now.

• Shift to dynamic data flows: Firms must transition from static PDFs and manually assembled reports to structured, machine-readable data formats.
• Operational overhaul: Manual processes and loosely structured data systems will no longer suffice; investment in technology and process automation is required.

Compliance challenges: Firms that fail to adapt to these changes risk non-compliance, especially at scale.

Most compliance conversations start with the reporting templates. They should start with the general ledger.

A fund's chart of accounts is the foundation for all LP reporting. When that foundation is configured to support ILPA's new line-item classifications from the outset—separating internal chargebacks from third-party costs, reconciling management fee offsets and waivers, and consolidating accrued, earned, and paid carried interest into a single reconciliation—the path to compliance is straightforward. Issues tend to arise when these structural decisions weren't made with this level of granularity in mind, and the gap only becomes visible when new reporting standards arrive.

GPs are well-served by assessing whether their accounting systems can support more granular expense categorization, consistent treatment of internal versus external costs, accurate mapping to ILPA-defined line items, and repeatable reporting across multiple funds with different vintages and strategies. For firms that built their infrastructure around simpler reporting expectations, this is the right moment to identify where the setup may need to evolve—before that gap shows up in a reporting cycle.

Some GPs may look to add more headcount to their finance teams. But layering more people and spreadsheets onto existing processes, without structuring the underlying data and connecting systems, creates effort without leverage and won't scale sustainably to meet the new requirements.

Dorota Kowalski, Senior Director, Fund Administration, warns that for GPs moving from the 2016 framework, the real friction point is often overlooked. “Your legacy expense categories simply weren't built for this new architecture. Historically, internal costs for accounting, compliance, and fund admin were grouped for operational ease, but they don't map cleanly to the new ILPA requirements.

“While you can use a transition line item to roll forward historical data, all new activity must hit the ground running under the new structure. This isn't a 'fix it later' situation—if your GL isn't reconfigured to support this distinction before the first reporting period, you’re setting yourself up for a crisis, patching the holes with manual workarounds and inconsistent data. You might end up technically compliant, but you’ll be left with a reporting process that’s dangerously fragile."

The transition window is open, but firms must act with intention to meet the required deadlines.

• For funds using the ILPA Performance Template: The new CC&D Template applies to funds launching on or after Q1 2026. The first delivery of reports under this new standard is required by Q1 2027.
• For all other funds: The implementation date is Q1 2027.

While legacy funds are technically exempt, LPs are already beginning to request this level of detailed reporting across their portfolios. Proactive adoption is a strategic advantage.

Firms that wait until the 2027 deadline will find themselves at a significant operational disadvantage. To prepare effectively, GPs should take the following steps now:

Audit current workflows

GPs should audit their existing capital call and distribution processes. Compare them against the new transaction type taxonomy required by ILPA to identify gaps in how transactions are currently coded, classified, and reported across systems.

Clarify obligations on historical data

One of the most common questions GPs are asking right now is: do we need to restate historical reporting? The short answer is no. The new templates apply to reporting periods going forward, not retroactively. However, firms should still evaluate whether historical data can be produced in the new structured formats if LPs request it. The GPs best positioned for those conversations will be the ones who have already mapped their legacy data to the new taxonomy, even if formal restatement isn't required. If a fund has significant legacy reporting gaps, now is the time to understand the scope of the work before an LP asks.

Engage with LPs early

GPs should initiate conversations with their LPs before the next fundraise. Proactively sharing the timeline and approach to ILPA compliance reinforces operational credibility and removes a potential friction point from future fundraising conversations.

Assess the technology stack

GPs should evaluate whether their current systems can produce the required structured, itemized, and reconciled data at scale. Manual assembly from spreadsheets or disconnected systems will not be sustainable under the new standard, and the cross-report reconciliation requirement raises the stakes of data fragmentation to levels higher than ever. If reporting workflows touch multiple platforms, the question isn't just whether each tool works, but whether they work together.

For many finance teams, understanding the new requirements is straightforward. The harder problem is mapping out current processes and identifying how fragmented those may be.

A common scenario: a team attempts to reconcile a capital call notice against the corresponding quarterly report and finds a discrepancy. Tracing it back reveals the issue originated six months earlier: a transaction was coded differently across two systems by two different people, neither of whom had visibility into the other's workflow. Under the old templates, that kind of inconsistency could be absorbed or explained away. Under the new standard, it becomes a compliance gap.

The coordination overhead alone is significant. Capital call notices, distribution notices, investor statements, and performance reports are often owned by different people, produced in different tools, and reviewed on different timelines. Without a single data source, bringing them into alignment—and keeping them there at scale—requires introducing a layer of manual QA before every LP delivery, which is not sustainable as LP bases grow and reporting cadences tighten.

This is the operational reality the 2027 deadline is forcing firms to confront. The earlier that work begins, the less disruptive it will be.

The firms that meet the new standard won't do it by adding a reporting layer on top of a broken data foundation. They'll do it by operating from a single system where transaction classifications, fee categorizations, and LP reconciliations are right from the start—not corrected after the fact.

Juniper Square is built around that principle. Because all capital activity, investor reporting, and fund accounting flow from a single unified data foundation, the cross-report reconciliation ILPA now requires isn't a separate workflow—it's a structural outcome of how the platform works.

• A single system for all activities: Juniper Square eliminates reconciliation challenges by consolidating all investor communications into a single, unified data foundation. The platform ensures consistency across every document, from capital calls to quarterly statements.
• ILPA-compliant templates, out of the box: The platform already generates ILPA-compliant capital call, distribution, and contribution notices.
• Structured data, not manual assembly: The transaction-level detail required by the new template—such as capital call types and unfunded commitment reconciliations—flows directly from the platform. This replaces time-consuming manual data gathering and reduces the risk of error.
• Scale without adding headcount: By automating document generation and reporting, Juniper Square allows firms to manage growing LP bases and more granular requirements without a proportional increase in operational staff. Reporting that once took days for a team can be completed in hours by a single person.

Firms that will struggle don’t lack good intentions; they underestimate how much of their current reporting relies on manual coordination and tribal knowledge rather than on clean, integrated systems. The firms best positioned to meet the new ILPA standard are those operating on an infrastructure where structured, audit-ready data already exists. Juniper Square provides this operational advantage. 

The ILPA reporting updates are more than a compliance exercise; they represent a new operational reality for the private markets. The expectation for transparent, accurate, and standardized data is now permanent. By taking decisive action to audit workflows, engage partners, and adopt the right technology, GPs can not only meet the new requirements but also enhance operational efficiency and strengthen investor trust. A unified platform that connects software, data, and services provides the stable foundation needed to navigate these changes with confidence and scale for the future.