How applicability is decided
A deterministic, versioned rules engine decides which statutory obligations apply from your company profile — never an LLM. Every verdict comes with the reason and the rule version.
Applicability is the heart of ComplianceStack, and it is decided by a deterministic rules engine— never by an LLM. Given your company profile, the engine evaluates each statutory rule and returns a clear verdict: applies, doesn't apply, or needs-input — with the reason.
Rules are versioned data, not code
Each obligation (a GST return, a TDS payment, an ROC filing) is stored as a declarative rule with conditions, a frequency, and a due-date formula. When the law changes by notification, we update the rule and bump its version — we never hardcode a threshold or date into the product. That makes every verdict auditable: you can see which rule version produced it.
What the engine reads
- Entity type — private limited, LLP, partnership or proprietorship decides the ROC/MCA obligations.
- GST registration — drives GSTR-1 / GSTR-3B and annual return obligations.
- Turnover — thresholds for GST, audit, and TDS applicability.
- Headcount — triggers PF (20+) and ESI eligibility, plus professional tax.
- State — professional tax and shops-and-establishment vary by state.
Why deterministic matters
Compliance is not a place for confident guesses. A deterministic engine gives the same answer every time, can be tested against the statute, and shows its working. The AI layer sits on top to explain a verdict in plain English — it never overrides it.