Folio

AIF Compliance Tracking Software: 8 Tests to Run in a Demo

Cover: AIF Compliance Tracking Software: 8 Tests to Run in a Demo

Test AIF compliance tracking software by loading one fund's compliance year with planted traps and running eight pass-or-fail tests, one per trap. Make four of them critical, so a failure on any one blocks signing until the vendor fixes it and the fix passes a re-run. In our view, a clean demo calendar shows the screens; a planted date shows whether the tool counts days the way SEBI, India's securities regulator, counts them.

This applies when a SEBI-registered Category I or II alternative investment fund (AIF) is replacing a spreadsheet or inbox with a tracking tool. The rules quoted are the AIF Regulations as amended up to 15 October 2026 and the Master Circular as last updated on 5 November 2026.

Summary

  • Load one illustrative fund with eight planted traps, and write down each right answer before the demo.
  • Score each test pass or fail, never on a 1 to 5 scale.
  • Treat four tests as critical: dates follow the rule, dates run from the real trigger, nothing is marked done without evidence, and history is never overwritten.
  • Pick on critical failures, not on score: in the example below, the tool scoring 7 of 8 sets a reply 8 days late and loses.
  • Ask for the vendor's SOC 2 report (an auditor's report on its controls) and read which criteria it covers, which period, and which exceptions it lists.

What must AIF compliance tracking software make visible?

AIF compliance tracking software must show, for every obligation, five things: the rule and its source, the due date worked out from that rule, one owner, the status, and the evidence that it was done. Under regulation 20(5) of the SEBI (Alternative Investment Funds) Regulations, 2012, the manager is responsible for every decision of the fund complying with the regulations, the placement memorandum (PPM, the fund's offer document) and investor agreements.

FieldWhat the tool must showCommon error
Rule and sourceThe obligation and its Regulation or Master Circular paragraph"Annual filing" with no source
Due dateThe date worked out from the rule and its triggerA rounded month-end, such as "end of September"
OwnerOne internal role per lineA team name, or an outside adviser
StatusOpen, done or late, with the date it changed"Done" ticked with nothing attached
EvidenceThe filed copy, acknowledgment or approval, with who added it and whenProof left in an email thread

What it is not

  • Not a filing tool. Activity Reports are filed on SEBI's intermediary portal; the tracker records the due date and the acknowledgment.
  • Not the PPM audit. An internal or external auditor or a legal professional still audits compliance with the PPM each year (Master Circular para 21.3.1).
  • Not legal advice. A tracker applies the rules you load. Whether a rule applies to your fund is for your compliance officer or counsel.

If valuation reports and net asset value (NAV) approvals sit in email threads, the evidence column above stays empty when the PPM auditor asks. For AIF managers and their teams, Folio's fund compliance module is where Folio keeps NAV records. See fund compliance in Folio.

How do you build a demo fund with planted traps?

A demo fund is one illustrative fund you load into every tool on the shortlist, with its rules, owners and a year of events, and each trap's right answer written down first. The traps below use one fund. Fund A is a Category II AIF set up as a trust with a sponsor, and its year ends 31 March 2027. It has raised money from investors. It is not a fund only for accredited investors, and not a large value fund (a fund where each investor is an accredited investor investing at least ₹25 crore, Reg. 2(1)(pa)). Every date comes from SEBI's Master Circular for AIFs (MC) or the Regulations (Reg.).

TrapWhat to plantCorrect outputTest
Day countsAnnual report to investors within 180 days of year end (Reg. 22(g)); Quarterly Activity Report within 15 calendar days of each quarter end, except March (MC 21.1.2)Annual report due 27 September 2027, not 30 September; no March 2027 quarter line; June 2027 quarter due 15 July 20271
Trigger datesCompliance test report reaches the trustee 28 April 2027; trustee comments arrive 20 May 2027 (MC 21.2.3); valuer's report dated 18 October 2027 for a 30 September valuation (MC 11.3.1, 11.3.2)Comments due 28 May 2027; reply due 4 June 2027; NAV upload due 17 November 20272
No proofMark the June quarter report done with no file attachedThe tool refuses to close the line3
Moved dateSomeone moves the 4 June 2027 reply date to 11 June 2027Both dates kept, with who changed it, when and why4
Large value fundRe-run Fund A with every investor an accredited investor investing ₹30 crore (MC 21.2.5, 21.3.8(c), 21.4.4)No PPM audit, trustee comment or reply lines; compliance test report prepared, not submitted; PPM changes due 30 April 2027 go straight to SEBI, not via a merchant banker5
SEBI letterA SEBI inquiry letter arrives on 9 August 2027 (Reg. 22(c))A disclosure line dated 9 August 2027, with an owner and a field for the date investors were told6
LeaverOn 1 June 2027, remove the user who owns the June quarter report and the replyBoth lines flagged for a new owner on 1 June 20277
Auditor requestAsk for every line for the PPM auditorOne spreadsheet with each line's rule, owner, dates and evidence links8

What are the eight tests for AIF compliance tracking software?

The eight tests for AIF compliance tracking software are: dates follow the rule, dates run from the real trigger, no evidence means not done, history is kept, applicability follows fund type, events become dated lines, every line has one owner, and everything exports. Tests 1 to 4 are critical, our suggested default.

#TestPasses ifCritical
1Dates follow the ruleThe annual report shows 27 September 2027; no March quarter line; the June quarter shows 15 July 2027Yes
2Dates run from the real triggerComments due 28 May 2027, reply due 4 June 2027, NAV upload due 17 November 2027Yes
3No evidence, no doneA line cannot close without a file, and the file shows who added it and whenYes
4History is keptThe original 4 June 2027 date, the new date, who, when and why are all visibleYes
5Applicability follows fund typeLarge value fund re-run: no PPM audit, comment or reply lines; compliance test report prepared, not submitted; direct filing routeNo
6Events become dated linesThe 9 August 2027 letter creates a dated line with an owner and a disclosure-date fieldNo
7Every line has one ownerEach line names one internal role; removing a user flags both lines for a new ownerNo
8Everything exportsEvery line, with its rule, owner, dates and evidence links, exports to a spreadsheet in one stepNo

Test 4 matters at audit time. Regulation 27 asks the manager or sponsor to keep the fund's core records for five years after the fund winds up. In our view, an overwritten date cannot show an auditor what the fund knew and when.

Rules change too. SEBI's circular reviewing the accredited investor framework, issued on 5 November 2026, also updated the Master Circular. Ask the vendor who updates the rule library when SEBI changes a rule, and check that past lines keep the version of the rule that applied then.

Worked example: a reply 8 days late

An illustrative fund runs the eight tests on two shortlisted tools.

ToolTests passedFailedCritical failures
Tool A7 of 8Test 2: reply due 12 June 2027, 8 days late1
Tool B6 of 8Tests 6 and 80

Tool A counts the manager's 15 days from the trustee's comment deadline, 28 May 2027, not from the day the comments arrived, 20 May 2027. It shows the reply due on 12 June 2027, 8 days after the real deadline of 4 June 2027. Counted by score, Tool A wins, 7 to 6. Under the critical-test rule, Tool A cannot be signed until it counts every date from its real trigger and passes test 2 on a re-run.

The fund picks Tool B. Its order says tests 6 and 8 must pass a re-run before the June 2027 quarter report, due 15 July 2027. Until both pass, the fund logs events in the old spreadsheet, with one owner.

In our view, a missing export costs an afternoon per audit; a late reply date breaks a SEBI timeline. For AIF managers and their teams, Folio's fund compliance module is where Folio keeps NAV records. How fund compliance works in Folio.

What should you ask about security?

Get each vendor's SOC 2 report and read which criteria it covers, which period, and which exceptions it lists. The AICPA's SOC 2 guide, listed on its SOC suite page, names five areas: security, availability, processing integrity, confidentiality and privacy. Then ask:

  • Who at the vendor can see your SEBI letters and investor data?
  • Is every change to a rule, date, owner or file in an audit log, and for how long?

When should you not buy AIF compliance software yet?

Hold off on AIF compliance software while your fund's calendar still fits in a spreadsheet that a second person checks, or while nobody owns the rules you would load.

SituationWhat to do instead
One scheme, one compliance officer, no missed dates last yearKeep the spreadsheet; add a second reviewer and the eight tests as a checklist
No one has listed which obligations apply to your fundList them first, with sources; a tool will only track the list you give it
Your administrator or counsel already runs the calendarRun the eight tests on their system before adding another tool
You also need portfolio demat records trackedAsk whether the tool holds them; see how AIFs standardise demat compliance

Under MC 11.6.1, any investment an AIF makes on or after 1 July 2025 must be held in demat (electronic) form, so what SEBI's demat rules require is a line on the tracker, not a separate project. For the wider work of running a fund's operations, the tracker is one record among several; the AIF operational checklist covers the rest.

Choose on the traps, not the sales demo. Load Fund A, run the eight tests and let the critical ones decide. For AIF managers and their teams, Folio's fund compliance module is where Folio keeps NAV records. Run the tests, then visit Folio's fund compliance page.

FAQ

How much history should we load for the demo?

Our suggestion: the current financial year plus last year's annual items still open, such as the PPM audit findings due 30 September. A tool tested only on future dates never shows how it handles a late line.

Who should own the tracker?

Our suggested default: the compliance officer owns the tracker and its monthly review; each line keeps its own owner. The manager stays responsible for compliance under regulation 20(5), so the manager signs off the open lines each month.

What if the manager runs more than one fund or scheme?

Load a second scheme of a different type, such as a large value fund, and run test 5 on both. In our view, each scheme should keep its own lines, and one view should show every line due in the next 60 days across all of them.

How long should the tracker keep evidence?

Our suggested default: as long as the Regulation 27 records, five years after the fund winds up. Check that the contract lets you export the evidence before you leave.

What should the tracker do when a deadline falls on a weekend or holiday?

Show both dates: the rule's date and the working date. The Quarterly Activity Report for the December 2027 quarter is due 15 January 2028, a Saturday. Our suggested default is to file by the last working day before it, so the tracker should show 14 January 2028 as the working date.

About Folio

Folio is Incentiv's fund platform for private market investors: VC funds, family offices and their LPs. It covers deal flow, portfolio, LP and fund management. Its fund compliance module is where NAV records live. Explore fund compliance in Folio.

This post is general information, not legal advice. Check every obligation against the current SEBI texts and your fund documents. Tool results in the example are illustrative.