Managing Investor Compliance Requests

---
name: managing-investor-compliance-requests
language: en
description: Coordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support. Use when responding to compliance requests, managing FOIA inquiries, or supporting LP audit processes.
tags:
  - management
  - investor-relations-and-lp-reporting
  - compliance
  - regulatory
metadata:
  author: casemark
  practice_areas:
    - Investor Relations
    - LP Reporting
    - Fund Administration
  document_types:
    - Management Report
  skill_modes:
    - Management
    - Coordination
---
# Managing Investor Compliance Requests

Coordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support.

## When To Use

- An institutional LP (pension fund, sovereign wealth fund, endowment, insurance company) submits a compliance questionnaire, regulatory data request, or audit inquiry
- A public pension LP triggers a FOIA or public records request that may expose fund-level data
- An LP's external auditor requests confirmations, fee schedules, capital account statements, or valuation backup
- A regulatory filing deadline (e.g., Form PF data, Schedule of Investments, ILPA reporting) requires coordinated data collection from the GP side
- An LP requests updated KYC/AML documentation, beneficial ownership disclosures, or sanctions certifications from the fund

## Inputs To Gather

- **Request document**: The actual compliance questionnaire, audit confirmation letter, FOIA notice, or regulatory data template from the LP or their agent
- **LP profile**: Investor type (public pension, ERISA plan, insurance company, endowment), jurisdiction, and any side letter provisions governing reporting obligations
- **Prior responses**: Previous compliance submissions to this LP to ensure consistency and flag any changed positions
- **Fund documents**: LPA, side letters, PPM, and subscription agreements that define information rights and confidentiality carve-outs
- **Data sources**: Fund administrator records, audited financials, portfolio company data, fee and expense reports, capital account statements
- **Internal contacts**: Investment team members, CFO/controller, legal counsel, compliance officer, and fund administrator contacts needed to compile responses
- **Timeline**: Response deadline, any interim acknowledgment requirements, and internal review/approval workflow lead times

## Workflow

1. **Classify the request**
   - Determine request type: compliance questionnaire, FOIA/public records, audit confirmation, regulatory filing support, or KYC/AML update
   - Identify the requesting party (LP directly, LP's auditor, LP's regulatory body, or third-party consultant)
   - Check side letter provisions for any enhanced reporting obligations or confidentiality restrictions specific to this LP
   - Flag if the request touches FOIA-sensitive data (track record, fee terms, carried interest) that may require confidential treatment claims [VERIFY: state-specific FOIA exemption procedures vary]

2. **Scope and assign**
   - Map each data element requested to an internal owner (fund admin, controller, legal, investment team)
   - Identify items that can be fulfilled from existing reports vs. items requiring new data pulls or calculations
   - Set internal deadlines with buffer ahead of the LP's deadline (typically 5-7 business days early for review cycles)
   - Flag any items that require legal review before disclosure (e.g., pending litigation, regulatory inquiries, MNPI considerations)

3. **Compile response package**
   - Gather data from each assigned owner; cross-check figures against audited financials and prior submissions for consistency
   - For compliance questionnaires: answer each question directly, cite supporting documents, and note any qualifications or scope limitations
   - For FOIA requests: prepare redaction recommendations for trade secrets, proprietary terms, and competitive information; draft confidential treatment request if applicable [VERIFY: specific FOIA exemptions and procedures by state]
   - For audit confirmations: reconcile requested balances to fund records, note any timing differences, obtain controller sign-off
   - For KYC/AML updates: compile current entity documents, beneficial ownership certifications, OFAC/sanctions representations, and any Form W-8/W-9 updates

4. **Internal review and approval**
   - Route completed response through compliance officer for regulatory accuracy
   - Legal review for any items involving confidentiality, privilege, or disclosure risk
   - Senior management sign-off where required by fund policy or side letter terms
   - Confirm all attachments, exhibits, and supporting schedules are included and properly labeled

5. **Submit and document**
   - Deliver response via the LP's specified channel (portal upload, encrypted email, secure file transfer)
   - Confirm receipt with the requesting party
   - Archive the complete request-response package in the investor compliance file with date stamps
   - Log the request in the LP compliance tracker for trend analysis and future reference

## Output

- **Response package**: Completed questionnaire, confirmation letter, or data submission formatted per LP/auditor specifications
- **FOIA treatment memo** (if applicable): Redaction log and confidential treatment request with cited exemptions
- **Internal tracking update**: Entry in compliance request log capturing request date, type, responding parties, submission date, and any open follow-up items
- **Escalation notes**: Any unresolved items, disputed data points, or legal concerns flagged during the process

## Quality Checks

- All figures reconcile to audited financials or fund administrator records; no unsupported estimates
- Response is consistent with prior submissions to the same LP — discrepancies are explained with a change narrative
- Confidentiality provisions in side letters and LPA have been respected; no over-disclosure of co-investor or portfolio company data
- FOIA redaction requests cite specific statutory exemptions, not generic objections [VERIFY: exemption language varies by jurisdiction]
- Deadlines met or extension formally requested before expiration
- Response reviewed by at least two internal parties (data owner + compliance/legal) before submission
- KYC/AML certifications are current (not expired) and match the fund's registered entity information