Compliance coverage with method and boundaries.
1nHR treats statutory rulesets like product infrastructure: source, date, jurisdiction, simulation, approval status, and payroll-run evidence.
Coverage map
Labour codes
Transition matrices and jurisdictional readiness are tracked with explicit status.
EPF and ECR
UAN source trails and contribution context stay attached to payroll evidence.
ESI, PT, and LWF
State effective dates and dual wage tracking stay visible during calculation.
Minimum wage and POSH
Zone, skill, VDA, restricted boundaries, and policy evidence are handled separately.
Rulesets are treated like product infrastructure.
The compliance surface focuses on method and governance instead of pretending statutory detail is static marketing copy.
Source
Official notification URL, jurisdiction, identifier, capture date, and verification date are retained.
Model
Rules are translated into effective-dated calculations with explicit review and approval states.
Simulate
Representative payroll cases are tested before activation so changes can be reviewed safely.
Release
Approved rulesets are version locked to payroll runs, liabilities, payslips, and audit exports.
Coverage is published with boundaries.
Compliance automation is evidence support for HR and finance teams. It does not replace fact-specific legal advice.
Payroll ruleset evidence
Payroll runs retain the exact ruleset version, source snapshot, inputs, and intermediate values used for calculation.
State and jurisdiction handling
Professional Tax, Labour Welfare Fund, minimum wage, and Shops and Establishments rules use effective dates.
Statutory payroll scope
Income tax, salary TDS, EPF, EPS, EDLI, ESI, gratuity, bonus, maternity benefits, and related payroll duties.
Governance boundaries
Restricted areas such as POSH, contract labour, OSH, and labour code transitions carry visible coverage status.