STATUTORY FILING SUMMARIES
PF, ESI, PT, TDS And LWF, Summarized Each Cycle.
Totaling PF, ESI, PT, TDS and LWF by hand leaves doubts at filing time. BizzField HRMS summarizes each cycle's liabilities and reconciles them against payroll.
OVERVIEW
One Summary Instead Of Five Deduction Records
PF, ESI, PT, TDS and LWF are deducted employee by employee, but finance needs one total per cycle that it can trust to match payroll.
PF, ESI, PT, TDS And LWF Together
Each cycle's liabilities are rolled up from the pay run into a summary, instead of five deduction records totaled by hand.
Reconciled Against Payroll
The summary is checked against what was actually deducted, so finance has a figure to work from before filing.
SUMMARY SNAPSHOT
This Cycle's Liabilities, At A Glance
A sample view of what a running BizzField statutory filing summary looks like — illustrative data.
Liability Mix This Cycle
Recent Reconciliations
HOW IT WORKS
How Statutory Filing Summaries Work
From each pay run's deductions to a reconciled summary, every cycle.
Step 01
Liabilities Calculated As Payroll Runs
Source calculation
PF, ESI, PT, TDS and LWF are calculated inside each pay run by the Statutory Compliance Engine, with PT and LWF following each employee's work location. The summary has one source to work from.- Liabilities calculated as part of each payroll run
Step 02
Summarized Automatically Each Cycle
Automatic summarization
At the end of each cycle, individual liability figures roll up into a summary automatically, so nobody totals deductions across every employee by hand.- Liability figures rolled up into a summary automatically each cycle
Step 03
Reconciled Against What Was Actually Deducted
Reconciliation
The summary reconciles against what was actually deducted in payroll, so a difference between what should have been withheld and what was withheld is visible before filing, not at it.- Reconciles against what payroll actually deducted
Step 04
Available Alongside Cost Reports And Dashboards
Reporting consistency
The same figures are available in Payroll & Cost Reports and visible on Real-Time Dashboards, so finance sees one number rather than three slightly different ones.- Same figures available across reports and dashboards
WHO USES THIS
Where Liabilities Are Hardest To Total
Employers with staff in several states, or regular audits, have the most liabilities to total and explain.
Manufacturing
Shift-based pay and overtime across plants, where statutory deductions vary by work location.
Logistics & Transportation
Field staff and multi-state operations, where PT and LWF follow each employee's work location.
BFSI
Strict access control, audit trails and incentive-heavy pay, where deductions must be explainable at audit.
FAQ
Statutory Filing Summaries — Questions We Get Asked
PF, ESI, PT, TDS and LWF liabilities, summarized and reconciled each cycle, so finance has one number to work from rather than five separate deduction records to total by hand.
It's part of the Growth plan, bundled with the rest of the statutory compliance suite — the Statutory Compliance Engine, Form 24Q Export, and IT & TDS Declarations.
Automatically. The summary reconciles against what was actually deducted in that cycle's payroll runs, so a mismatch is visible before filing instead of at filing time.
Yes. Statutory Filing Summaries, Payroll & Cost Reports, and Real-Time Dashboards all draw from the same reconciled data, so the liability figure is consistent wherever you look at it.
PF, ESI, Professional Tax, TDS and LWF. PT and LWF follow each employee's work location, so a multi-state team gets the right state's rule without manual lookups.
The summary totals each cycle's liabilities across PF, ESI, PT, TDS and LWF. Form 24Q is the quarterly TDS return, built from the TDS already deducted in payroll and covered under Statutory Compliance.
AT A GLANCE
Five Liabilities, Every Cycle
AUTOMATED CHECKS
Variance Checks Before Payroll Is Approved
Before a pay run is approved, BizzField compares the draft with the previous cycle and flags what looks wrong, so reviewers examine the exceptions instead of every line.
PRE-APPROVAL SCAN
Automated Variance Checks
Key Capabilities
- Each employee's draft pay compared with the prior month
- Pay movement above 20% flagged for review
- Duplicate leave and expense submissions detected
- Flags resolved from one HR queue before approval
Every draft run is compared with the previous cycle. Sharp pay movements, duplicate expense or leave submissions and timesheet conflicts are flagged for HR, who resolve each flag from a single queue while the run is still a draft.
See Automated Variance ChecksSECURITY & PRIVACY
Role-Scoped Access And Privacy By Design
Access is enforced on the server from the reporting hierarchy, and data handling is designed around the principles of India's DPDPA. The security page sets out what is and is not certified.
DATA PRIVACY
DPDPA-Informed Data Handling
Key Capabilities
- Consent logging for employee data
- Data export for the employee
- Deletion rights supported
Data handling is designed around the principles of India's Digital Personal Data Protection Act. That describes how data is handled; it is not a certification.
ACCESS CONTROL
Server-Scoped Access And Encrypted Storage
Key Capabilities
- Server-side role-based access, not just interface-level visibility
- Manager visibility limited to their reporting hierarchy
- AES-256 encryption at rest for employee records, bank details and document files
Role flags are not left to the front end. Access is scoped on the server, so a manager retrieves records only within their own reporting tree.
See HRMS SecurityROLLOUT TIMELINE
Getting Started with BizzField Statutory Filing Summaries
A structured path from configuration to pilot testing and full launch, guided by our onboarding team.
Step 01
Employee Data Import & Hierarchy Setup
Model your reporting hierarchy, upload employee records securely, and map custom document types to BizzField's structure.- Upload employee master data from a CSV file
- Map reporting lines & org hierarchy
- Configure custom document categories
Step 02
Policy & Rule Configuration
Configure multi-level approvals, custom shift templates, statutory compliance ceilings, and salary revision workflows.- Set leave types, accruals & sandwich rules
- Define shift rosters & overtime rules
- Configure state-wise PT/LWF compliance
Step 03
Parallel Run & Validation
Verify payroll calculations, shift check-ins, and approval chains alongside your existing setup before fully cutting over.- Run a parallel payroll draft for one month
- Compare attendance records with your current process
- Confirm role-scoped access for all managers
Step 04
Full Launch & Team Training
Release employee self-service credentials, activate mobile check-in, and turn on pay run approvals and notifications.- Distribute self-service app credentials to all employees
- Publish payslips to employee self-service on pay date
- Switch on approval and leave notifications
KEEP EXPLORING
Related Pages
Other HRMS capabilities teams usually evaluate alongside this one.
Timesheets
Weekly timesheets lock after submission; a manager opens a time-limited window for corrections.
ExploreRole-Based Access Control
Managers see only their own team's records; access is enforced server-side from the org hierarchy.
ExploreAutomated Pay Runs
Draft from approved attendance and leave, then submit, approve and pay, with an audit trail at every step.
ExploreFlexible Salary Structures
Earnings, deductions and statutory components set once and applied per employee, not rebuilt in Excel.
ExploreSee Statutory Filing Summaries In Action
Walk through how PF, ESI, PT, TDS and LWF liabilities are summarized each cycle and reconciled against what payroll deducted.