Payroll must derive the PF wage base from configured eligible components and produce a filing-ready supported output after review.
India statutory payroll output
Connect payroll computation with the PF ECR output your team actually submits.
Configure PF-eligible components, review employee and employer contribution values and prepare the supported PF ECR 2.0 output as part of the payroll close.
Representative operating scenario Current boundaries stated clearly
Payroll control roomIllustrative interaction
1Initiate2Compute3Review4Approve5Finalise
Readiness check
Owner and history remain visible482Employees
31Inputs pending
DraftRun status
Calculation in progress
Owner and history remain visible468Computed
14Exceptions
6m 18sIllustrative run
Variance and output review
Run remains reversible before finalisation94%Ready
11Variance flags
AvailableRollback
Authorised review
Owner and history remain visible471Approved
11Held
2Approvers
Payslips and outputs
Owner and history remain visible471Payslips
5Bank files
4Statutory outputs
Who this page is for
For Indian payroll teams evaluating whether the HRMS can produce usable statutory outputs—not only payslip calculations.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
PF logic is separated from salary component configuration.
02
The team validates totals but not employee-level contribution values.
03
Filing files are prepared manually after payroll finalisation.
04
Unsupported claims about statutory coverage create implementation risk.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Configure eligible components
Use the salary component catalogue and approved PF eligibility flags.
Compute and review
Inspect employee and employer values within the reversible payroll run.
Validate exceptions
Resolve missing identifiers or unusual values before finalisation.
Prepare the supported output
Generate the documented PF ECR 2.0 file after authorised payroll approval.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Payroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
ExploreCompliance & Audit Logs
Use role and data scopes, operational audit, security events, sensitive-data access records, effective dates and controlled exports to make important actions easier to reconstruct.
ExploreCore HR
Centralise employee records, organisation structures, dated lifecycle changes and policy scope so downstream attendance, leave, payroll, performance and access decisions use the same governed foundation.
ExplorePolicy Configuration
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
Does duoHR describe PF ECR 2.0 output?
Yes. The consolidated payroll material lists PF ECR 2.0 as a supported output.
Does duoHR generate Form 16?
No. Form 16 generation is explicitly listed as outside the documented current scope.
Should statutory values be reverified before launch?
Yes. Statutory configuration, rates and filing behaviour require current payroll and legal validation before customer commitment.
India statutory payroll output
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.