Evidence, Not 'Filed': The One Habit That Makes Diligence Painless
A task marked 'done' is not the same as a task you can prove. Here's why keeping the filed acknowledgement as evidence — not just ticking a box — is the single habit that makes due diligence fast.
In diligence, "we filed it" is worth nothing without the document that proves it. The single habit that separates a painless diligence from a painful one is treating a compliance task as complete only when the filed acknowledgement is stored as evidence — the challan, the ARN, the FC-GPR acknowledgement, the stamped certificate — not just when someone ticked "done." Here's why that distinction quietly decides how your next round goes.
"Done" and "provable" are different states
Most compliance tracking records intent or action: a task marked complete, a note that the CA filed it. But an investor's lawyer doesn't accept actions — they accept artifacts. A cap table is reconstructed from filed PAS-3 forms; FEMA compliance is verified from FC-GPR and FLA acknowledgements; tax compliance from the actual returns and challans. If the action happened but the proof isn't kept, you're functionally non-compliant for diligence purposes, because you can't demonstrate it.
The gap shows up exactly when it's most expensive: mid-round, when you're asked to produce two years of acknowledgements and discover some live only in the CA's inbox or a since-deleted email.
Why the evidence habit compounds
Three reasons keeping proof as you go beats reconstructing it later:
- Acknowledgements decay. Portal downloads expire, emails get lost, staff and CAs change. The day a filing happens is the easiest day to capture its proof.
- Reconciliation needs the source. When the cap table and the filings must match, you need the filings — not a memory that they were done.
- It signals control. A complete evidence trail tells an investor the team is disciplined, which earns trust on everything harder to verify (the boring data room effect).
What counts as evidence
For each obligation, the proof is the thing the government or counterparty issued back:
- GST/TDS: the filed return + challan / ARN
- ROC (PAS-3, AOC-4, MGT-7): the SRN / filed challan
- FEMA (FC-GPR, FLA): the RBI acknowledgement
- Equity: stamped share certificates, signed SHA/SSA, ESOP grants
- IP: the signed assignment
"Filed" is a claim; these are the proof.
Build the habit into the system, not the person
The reason evidence gets lost is that capturing it depends on someone remembering, every time, across years and staff changes. The fix is to make "not done until evidence is attached" a property of the system. That's the core design choice in ComplianceStack: a task isn't complete until a document is linked (or explicitly waived), the proof lives in a private evidence vault, and your diligence pack assembles from it automatically. Get your free compliance health check.
FAQs
- Why isn't "marking a task done" enough for compliance?
- Because diligence accepts artifacts, not actions. Without the filed acknowledgement stored as proof, you can't demonstrate compliance when an investor or auditor asks — which functionally counts as non-compliant for the deal.
- What counts as compliance evidence?
- The document the authority or counterparty issued back: the filed return and challan/ARN, the ROC SRN, the RBI acknowledgement, stamped share certificates, signed agreements.
- When should I capture the evidence?
- The day the filing happens — acknowledgements and emails decay over time, and reconstructing them later (especially under deal pressure) is slow and sometimes impossible.
This article is general information, not tax, legal or accounting advice. Statutory timelines and thresholds change by notification — confirm applicability and interpretation with your CA, CS, or lawyer before acting.
Know exactly what applies to you
ComplianceStack builds your applicable GST, TDS, PF/ESI, ROC and legal calendar from a short questionnaire — and keeps the evidence in one place. Your first health check is free.
Get your free health check