PE
PE Suite Interactive BRD
Questionnaire Questions Open prototype ↗
Business Requirement Document · Interactive

PE Suite — PE Engine & PCAP Engine

A navigable BRD for the private-equity fund accounting & investor-reporting platform. Every module and requirement links to the live prototype screen that demonstrates it. Markers show what extends the current draft (extends) and what still needs your input (pending). Produced with the prototype to clarify scope.

2
Engines (PE · PCAP)
16
Business modules
4
User roles (RBAC)
45
Open questions
2
Phases

1Executive Summary

PE Suite is a secure, modular, web-based platform for PE fund data capture, fund accounting workflows, partner capital account reporting, dashboards, reconciliations, approval controls and audit-ready reporting.

ContextSummary
What they have nowAccounting data in MSD 365 (ERP) plus extra data compiled manually in Excel, handed to an external third-party tool that produces the investor reports. Two disparate systems, heavy manual work in between, and dependence on an outside vendor.
What they wantPE Suite — one internal, modular platform replacing the manual middle and the external tool: PE Engine (drawdown, NAV, distribution/waterfall, management fee, close), PCAP Engine (partner capital accounts), investor reporting (ILPA pack + dashboards), with bulk upload, maker-checker approvals, exceptions and a full audit trail. Hosted on EY servers. Phase-1 first proof: drawdown and distribution notices.
Why they want itCut manual, error-prone spreadsheet work; remove dependence on the external tool/vendor; gain auditability & traceability (every figure traces to an approved source); enforce human-in-the-loop control before finalising; standardise investor reporting (ILPA); and own their process and data.

The solution comprises two integrated engines plus an investor-reporting layer:

EnginePurposePrimary outputs
PE EngineCore fund accounting, investor data, capital calls, commitments, expenses, investments, valuation, distribution, waterfall, close and reports.Executive dashboards, capital-call reports, distribution notices, close pack.
PCAP EnginePartner capital account statement generation, fund-level PCAP consolidation, contribution & distribution mapping, NAV mapping, reconciliation, variance and audit packs.Fund-level PCAP, partner statements, reconciliation & variance reports, export pack.

2Business Objectives

IDObjectiveSuccess criteria
BO-01Digitise PE fund data capture and reporting workflows.Users can input/upload structured fund, investor, capital-call, distribution, NAV, valuation and expense data.
BO-02Generate fund-level and partner-level PCAP statements.System generates PCAP from approved source data, ratios, reconciliation and mapped rules.
BO-03Improve auditability and traceability.Every input, upload, adjustment, approval, calculation and export is logged.
BO-04Enable human-in-the-loop controls.Key outputs, exceptions, uploads and report packs require approval before finalisation.
BO-05Support secure deployment flexibility.Hosted internally, migratable to client infrastructure with documented procedures.
BO-06Provide dashboard and reporting capability.Role-based dashboards and downloadable PDF/XLSX reports are available.

3Scope

In scope: user management & RBAC, data capture, bulk upload, the PE Engine, the PCAP Engine, workflow, audit trail and integration-readiness.

Out of scope (initial release)Note
Full ERP integrationInitial release supports file import; live ERP later.
Regulatory filing submissionGenerates reports but does not submit filings.
Payment processingMay capture payment status; does not initiate bank payments.
ForecastingInitial scope is actual data capture, processing, reconciliation and reporting.

4Target Users & Role-Based Access

Four roles with distinct entitlements. See the live role switcher →

RoleKey access
Fund ManagerDashboards, review screens, workflow approvals and final report approvals.
Fund AccountsCreate/update inputs, upload templates, run validations, prepare reports, resolve exceptions.
InvestorView/download own approved statements and permitted reports only.
AdminUser management, configuration, audit-log access and system administration.

5High-Level Process Flow

Onboard → Once per fund: details, terms profile, classes, investors, ratios, opening balances → activate Input → Capture / upload fund, investor, calls, distributions, NAV, valuation, ratios Process → Validate → allocations, waterfall, NAV, PCAP mapping, close logic Approve → Maker-checker across data, calculations, exceptions and reports Output → Notices, statements, reconciliations, dashboards, export/audit pack

Designed for traceability: every output line item traces back to an approved source input. See the pipeline →

5.1Fund Onboarding Process extends

The draft BRD has no onboarding step: fund and investor data arrive only as the Fund Master and Investor Master uploads, and fund terms are assumed separately on each calculation screen (Q1–Q22). This section adds one ordered, gated process that every fund passes through before any engine can use it. See Fund Onboarding →

#StageWhat is capturedChecksOwnerQuestions
1Fund detailsName, legal structure / AIF category, manager, vintage, target and first-close size, term and extensions, investment period, currency, reporting frequency, first close dateMandatory fields completeFund AccountsQ1, Q3, Q4
2Terms profileWaterfall, hurdle, catch-up, carry, fee basis / rates / step-down, offset, GST, call basis and notice period, excused and default rules, recycling, valuation policy, equalisationEach term confirmed or flagged pending; versioned, effective-datedFund Accounts → FMQ2, Q5–Q22, Q40
3Share classesClasses, fee and carry differences, class rights, minimum commitmentΣ class commitments = fund sizeFund AccountsQ1, Q7, Q16
4Investors & commitmentsInvestor, type, class, commitment, close admitted at, KYC status, tax residency, bank details, notice contacts, side lettersKYC verified; bank details verified by a second person; notice contact presentFund Accounts; bank change → FMQ8, Q15, Q41, Q43
5Ratios & opening balancesPartner ratios per class / transaction type (effective-dated); opening capital accounts (0 for a new fund; last external PCAP for a moved fund)Ratios = 100%; opening balances reconcile to sourceFund AccountsQ23, Q25, Q42
6Approval & go-liveMaster data approval (WF-001) and fund activation (WF-007)All blockers passFund ManagerQ44

Go-live rules

CheckTypeEffect if it fails
Fund details complete · class commitments = fund size · all investors KYC verified · ratios = 100% · opening balances approvedBlockerFund cannot be activated
Investor bank details not verifiedWarningDistributions to that investor are blocked
Investor notice contact missingWarningNotices to that investor cannot be issued
Terms pending confirmationWarningCalculations that use the term run as Draft only

Onboarding types & later events

CaseHow it is handled
New fundAll six stages; opening balances = 0.
New fund cloned from an existing oneTerms profile copied from the source fund (e.g. Fund III → Fund IV); only differences are edited and shown as changed.
Fund moved from the external toolOpening capital accounts loaded from the last external PCAP, reconciled line by line, and signed off before go-live (Q42).
Later closeNew investors pay their share of earlier calls plus equalisation interest; existing investors are credited. Ratios re-based with a new effective date; old ratios kept for earlier periods (Q40).
Transfer between investorsCommitment, called and uncalled amounts, and capital account moved from seller to buyer on a dated transfer; buyer must pass investor checks first (Q45).
Term change after go-liveNew terms-profile version with effective date, through override approval (WF-006); earlier periods keep the old version.

6Application Modules

Each module opens its live screen in the prototype. extends = beyond the current BRD draft; grouped by delivery phase.

PE Engine · Phase 1 calc + foundations

PCAP Engine & Reporting Phase 2

Ledger, portfolio, regulatory & controls extends

7Functional Requirements

Representative requirements with acceptance criteria. Use the filter in the top bar to narrow by keyword.

IDRequirementAcceptance

8Data Ingestion — assumed upload files

Manual Excel schedules + MSD 365 extracts. The columns below are what we plan to read — illustrative until the workbook is shared. See Import Center →

FileSourceAssumed columnsFeeds
Fastest way to lock scope: share the actual workbook (recording showed Fund_Master · Investor_Master · DD Notice · Distribution Notice tabs) + one MSD 365 trial-balance extract. Tracked as Q35–Q37.

9Core PCAP Calculation Logic

Configurable, version-controlled rules; each output retains source mapping and calc-run version. See PCAP roll-forward →

Capital commitment = Total commitment (fund) × partner contribution ratio Contribution received = Fund contribution received × ratio Total Distributions (A) = transferred + reinvested + retained + taxes Fair value unrealised (B) = fund FV + deemed contribution, by ratio Accrued returns (C) = fund accrued × ratio Sponsor expenses (D) = sponsor expense × ratio Total Fair Value of Inv. = A + B + C − D

10Workflow & Approvals

Maker-checker; final outputs enabled only after Fund Manager approval. See pipeline →

IDWorkflowApprover
WF-001Master data approvalFund Manager / Admin
WF-002Upload approvalFund Accounts / FM
WF-003Calculation approvalFund Manager
WF-004Exception resolution approvalFM / Controller
WF-005Report approvalFund Manager
WF-006Override approvalFM + Admin
WF-007Fund activation (go-live) extendsFund Manager

11Exception & Control

Rule breaches raise exceptions; material ones block final export. See Exceptions →

ExceptionSystem behaviour
Missing mandatory inputBlock save/upload or mark row invalid
Ratio ≠ 100% tolerance pendingCreate exception; block final calculations
Reconciliation mismatchCreate exception; prevent final export if material
Unapproved source dataExclude from final calculation
Manual override / balancing figureRequire reason, approval and audit trail

12Reporting

IDReportFormat
RPT-001Executive DashboardUI / XLSX / PDF
RPT-002Capital Call SummaryXLSX / PDF
RPT-003Distribution SummaryXLSX / PDF
RPT-004NAV SummaryXLSX / PDF
RPT-005Fund-Level PCAP SummaryXLSX / PDF
RPT-006Partner PCAP StatementXLSX / PDF
RPT-007Variance & ExceptionsXLSX / PDF
RPT-008Audit Trail ReportXLSX / PDF
RPT-009Export PackZIP / PDF / XLSX
ILPA Reporting Pack newXLSX / PDF

13Audit Trail & Non-Functional

Immutable log of every create/update/approve/override/export with before→after values and full lineage. See Audit Trail →

CategoryRequirement
SecuritySecure authentication & authorization; role restrictions enforced.
Data confidentialitySensitive financial data encrypted in transit and at rest.
DeploymentHosted on EY internal servers with documented portability to client infra.
AuditabilityFull traceability from source input to final report.
Data integrityValidation, reconciliation and approval controls; invalid/unapproved data cannot reach final reports.
Export securityDownloads respect RBAC & data entitlements.

14Phasing

Phasing correction. The agreed Excel places PCAP, Investor Reporting and Investment/Capital in Phase 2; Phase 1 is the four PE-Engine calc modules. This corrects the BRD draft (Appendix B had PCAP in Phase 1) and matches the discovery meeting.
PhaseScope
Phase 1RBAC, master data, Fund Onboarding, Import Center, bulk upload, validations, audit trail, Drawdown, NAV, Distribution, Management Fee, Close, export pack.
Phase 2PCAP engine, Partner Statements, reconciliation, Investor Reporting Dashboard (ILPA), Investment/Capital, enhanced dashboards.
Phase 3ERP/Tally connectors, advanced analytics, enhanced investor portal, configurable rules engine.

15Open Questions & Traceability

45 open decisions with assumed defaults, mapped to modules. Answer offline in Excel or in the browser. Open the register →

ObjectiveRelated requirements
BO-01FR-GEN-003, FR-UPL-001…006, FR-MST-001…005, FR-ONB-001…008
BO-02FR-PCAP-001…013
BO-03AUD-001…007
BO-04WF-001…006
BO-06RPT-001…009, FR-PE-001, FR-PCAP-001

16Indicative Data Model

The logical entities behind the modules — what stores what, and how they relate.

EntityStoresKey relationships
Fund MasterFund attributes & reporting setupInvestors, capital calls, distributions, NAV, PCAP
Entity MasterSponsor / fund / entity structureFund master & GL
Investor / Partner MasterInvestor/partner details & statusCommitments, ratios, statements
Partner Ratio TableFund- & transaction-wise allocation ratiosUsed by PCAP calculations
Capital Call TableCapital call detailsInvestors & commitments
Distribution TableDistribution instances & componentsMapping & reconciliation
NAV & Valuation TableNAV, valuation, fair value, carried interest inputsNAV summary & PCAP
Fees & Expenses TableSponsor/fund expenses & fee calculationsPCAP & dashboards
GL / Journal TableAccounting entries & postingsCOA & reports
Upload Batch TableUpload metadata & statusImported records
Calculation Run TableCalculation run metadata & versionOutput reports
Exception TableValidation & reconciliation issuesSource records
Approval TableWorkflow approval historyRecords & reports
Fund Terms ProfileVersioned, effective-dated economic & LPA termsFund master; read by drawdown, fee, distribution, NAV
Side Letter RegisterPer-investor overrides (fees, excusal, MFN)Investor master; terms profile
Investor Onboarding RecordKYC status, tax residency, verified bank details, notice contactsInvestor master; notices; distributions
Audit Log TableImmutable audit eventsAll key entities

17Assumptions Ledger

Every placeholder baked into the prototype, and the question that confirms or replaces it — so nothing stands unexplained. Full detail in the Open Questions register.

#AssumptionResolved by
A1Illustrative ₹ Cr figures, single demo fundA real dataset
A21 fund, 2 classes (A/B) + GPQ1
A3European (whole-fund) waterfallQ2
A4Single currency, no FXQ3
A5Pro-rata calls; excused/default as demoedQ5–Q7, Q9
A6Pro-rata class/investor NAV; IPEV valuationQ10, Q11
A78% hurdle · 100% catch-up · 80/20 carry · single withholdingQ13–Q15
A8Fee 2%→1.5%, step-down Mar 2026, 80% offset, 18% GSTQ18–Q22
A9Partner ratios pro-rata = 100%; §8 verbatim; opening = 0Q23–Q25
A10PCAP, Investor Reporting, Investment = Phase 2 (corrects BRD Appendix B)Excel + meeting; fix in v2
A11Standard ILPA templates; DPI/TVPI shown, IRR pendingQ26, Q28
A12File import (MSD 365 TB, manual schedules, bank/Tally)Q35–Q38
A13Reconciliation tolerances not numerically setQ31
A14Fund onboarding demoed on Fund IV (cloned from Fund III); KYC tracked in PE Suite; bank changes need 2 people; equalisation 8% p.a.Q40–Q45

18About & How to Use This Portal

This one document is the interactive BRD. It is accompanied by two working tools — the prototype and the questionnaire — and nothing else to keep track of.

ISWhat it is

An interactive requirements document that demonstrates the proposed scope, explains each calculation, and captures the client’s answers — a shared reference for scoping. Produced alongside the written BRD to remove ambiguity before build.

NOTWhat it is not

The production system. Data is illustrative; calculations show shape & intent, not real books. Not security-hardened, multi-tenant, or connected to live systems. No AI is used.

The three pieces

PiecePurpose
Interactive BRD this pageThe full requirements — modules, requirements, data ingestion, calc logic, data model, assumptions — each linked to the prototype.
Prototype ↗The clickable app. Every screen has a derivation panel, and Explain mode lets you hover any element to see what it is, how it’s derived and any assumption. Role switcher demonstrates RBAC.
Open Questions register45 decisions with assumed defaults. Answer offline in Excel (Download for Excel — includes section, why, assumed default, related screen) or in the browser; attach evidence.
How to validate, end to end: read a requirement here → click Open in prototype ↗ → turn on Explain and hover the figures → answer the mapped questions in the register. Technology: plain HTML/CSS/JS, self-hosted; an optional backend only adds shared answer storage.