Compliance

Rules that carry a date and cite the Act.

Statutory computation, applicability decided per entity, filing tracked with its evidence, and inbound notices followed to a resolution.

Versioned and effective-dated, so history stays true.

EPF, EPS, EDLI, ESIC, Professional Tax and TDS are computed from rules that carry an effective date and a citation. When a rate changes, a period that already ran recomputes the way it was run at the time.

A compliance run produces line items, not a single figure, so a number can be traced to the employee and the rule that produced it.

  • Applicability is decided, not assumed

    Which statutes apply to which entity is computed from the entity's own facts, and the reasoning is visible.

  • Filing is human-assisted, deliberately

    The workflow tracks what is due and holds the evidence. It does not fabricate government file formats it cannot guarantee.

  • Notices are tracked inbound

    A government notice is an object with an owner and a deadline, not an email in somebody's inbox.

  • Evidence without duplication

    Bundles are assembled by checksum over documents already held, rather than by making second copies.

Nothing due No filing falls in the next 30 days.
Not applicable PF applies above 20 employees.
Incomplete Compliance run left unfinished for this period.
Past due A statutory filing is past its date.

Uncertainty

“Nothing due” is a finding. A blank is not.

An empty compliance calendar can mean there is nothing to file, or that nothing was checked. Those are opposite situations and the product distinguishes them.

Where a statute does not apply, the reason is stated, not left as a silent gap that looks like an oversight at audit time.

Look at a compliance run.

The demo carries computed statutory line items with their citations.