SEBI AIF Category I, II & III Reporting: A Fund Operations Guide

Most AIF reporting pain is misdiagnosed. Fund teams describe it as a compliance burden, when what they actually have is a data-architecture problem: the same underlying facts get assembled three or four separate times, by hand, into three or four different formats.

This guide covers what a SEBI-registered AIF reports, how the three categories genuinely differ, and — the part that matters operationally — how to structure your data once so every report becomes a view rather than a project.

A note on scope: this is an operations guide, not legal advice. SEBI's AIF Regulations and the circulars issued under them are amended regularly, and thresholds and formats change. Confirm current requirements against SEBI's own publications or with your compliance counsel before relying on any specific obligation described here.

The three categories, and what actually separates them

The categories are defined by investment strategy, and the regulatory treatment follows from how much the regulator wants to encourage or constrain that strategy.

Category I

Funds investing in sectors the government and regulators consider socially or economically desirable — venture capital, SME funds, social venture funds, infrastructure funds. These receive the most favourable treatment, because the policy intent is to channel capital toward them. Borrowing is restricted to short-term operational requirements rather than investment leverage.

Category II

The residual category, and where most private credit and private equity funds in India sit. Category II covers funds that are neither Category I nor Category III — typically private equity, debt funds and funds of funds. Like Category I, leverage is limited to meeting day-to-day operational needs, not to amplifying returns. If you run an Indian private credit fund, this is almost certainly your category.

Category III

Funds employing diverse or complex trading strategies, including leverage through listed or unlisted derivatives — hedge funds and long-short funds. Because these can take on genuine investment leverage, Category III attracts the most intensive reporting, including more frequent submissions and leverage-specific disclosure.

The recurring obligations, in operational terms

Periodic reporting to SEBI

AIFs file periodic activity reports covering fund size, commitments drawn, investments made and portfolio composition. Frequency and format depend on category, and are prescribed through SEBI circulars rather than sitting statically in the regulations — which is precisely why hard-coding a report template is a mistake. Build the data model to be format-agnostic and treat the template as configuration.

PPM compliance and the annual audit of terms

The Private Placement Memorandum is not a marketing document once issued — it is a commitment. SEBI requires AIFs to have compliance with PPM terms audited annually, with findings reported to investors and to the regulator.

Operationally this is where funds get caught out, because it audits things nobody tracked contemporaneously: whether investment restrictions were observed, whether fees were charged as disclosed, whether the stated strategy was actually followed. If the answers have to be reconstructed at year end, the audit becomes an archaeology exercise. Tracking PPM constraints as live, enforced limits — rather than as a document — is the single highest-leverage change most funds can make.

Valuation

AIFs must value portfolio investments on a defined basis and cadence, with independent valuation requirements for certain categories and asset types. For private credit specifically, valuation and credit monitoring should share inputs: a position where covenants are under pressure and the borrower's GST filings have gone irregular is not obviously worth carrying at par. Funds that keep valuation and portfolio monitoring in separate systems tend to discover this mismatch only at audit.

Investor reporting

Investors receive periodic reports on portfolio performance, fees and expenses, and — for Category III especially — risk and leverage. Alongside the regulatory obligation sits the commercial reality: sophisticated LPs increasingly expect performance data at a granularity and frequency that goes well beyond the regulatory minimum.

Why the same numbers get built four times

Here is the pattern that produces most AIF reporting cost. The same underlying facts — what was invested, what it is worth, what it earned, who owns what share — are assembled independently for:

• the SEBI periodic report, in SEBI's format
• the LP quarterly report, in the fund's own format
• the annual audited financial statements, in accounting format
• the internal IC and board pack, in whatever the CIO prefers

Each is built from a different spreadsheet, by a different person, at a different time — which guarantees they will disagree. Reconciling four versions of the same truth is where fund operations teams lose their quarters, and it is also where restatement risk originates.

The fix: one deal record, many views

The architectural principle is straightforward and rarely implemented: every reportable fact should have exactly one authoritative source, and every report should be a projection of it.

• Deal-level record as the single source. Commitment, drawdown, instrument terms, security, covenants, valuation history and cash flows all attached to the deal — not scattered across an accounting system, a spreadsheet and someone's inbox.
• Investor allocations computed, not maintained. LP-level shares derived from commitment and drawdown records rather than kept in a parallel capital-account spreadsheet.
• Performance metrics from cash flows. IRR, MOIC and TVPI calculated from the actual cash flow record. If your IRR lives in a spreadsheet that someone updates, it will eventually disagree with your accounts.
• Report templates as configuration. When SEBI revises a format, you change a template — not a data pipeline.
• PPM limits as enforced constraints. Concentration and strategy restrictions checked at approval, so the annual PPM audit reads a log rather than reconstructing history.

Where Indian private credit AIFs specifically struggle

Beyond the generic reporting architecture, Indian private credit funds face three problems that offshore-designed systems do not anticipate.

Borrower data does not arrive in reporting-pack form. Indian mid-market borrowers generate monthly GST filings, bureau records and Account Aggregator banking data rather than tidy quarterly submissions. That is an advantage for monitoring — see our guide on covenant monitoring beyond quarterly PDFs — but only if your system can ingest it.

Security and enforcement mechanics are India-specific. Security creation and perfection, security trustee arrangements, and the enforcement routes available — SARFAESI, the DRT, arbitration, the IBC before the NCLT — all carry documentation and tracking requirements that generic fund software treats as free-text fields.

Co-lending and NBFC structures blur the boundary. Many Indian private credit strategies involve an NBFC alongside the fund, which means the same underlying borrower can appear in both an AIF reporting perimeter and an RBI-regulated lending perimeter, with different classification rules applying to each. Keeping those consistent is genuine operational work.

A practical operations checklist

1. Confirm your category and its current obligations against SEBI's latest circulars, not against a summary written two years ago.
2. Map every recurring report to its data source. Where two reports draw the same fact from different places, you have found a reconciliation cost.
3. Make the deal record authoritative. One place for terms, security, covenants, valuations and cash flows.
4. Derive IRR, MOIC and TVPI from cash flows rather than maintaining them.
5. Convert PPM restrictions into enforced limits checked at investment approval and logged.
6. Connect valuation to credit monitoring so deteriorating positions cannot quietly stay at par.
7. Keep report formats as templates, so a SEBI format revision is a configuration change.
8. Log IC decisions immutably — who voted, when, on which memo version, with what conditions. This is what an audit actually wants to see.

The takeaway

AIF reporting feels like a compliance problem and behaves like an engineering problem. Funds that treat each report as a separate deliverable spend every quarter rebuilding and reconciling the same numbers, and carry restatement risk while doing it. Funds that build one authoritative deal record and project it into each required format find that regulatory reporting, LP reporting and the annual audit all become substantially cheaper at the same time — because they stop being four different jobs.