Payroll & statutory compliance
VIBWERA™ runs payroll and its statutory trail inside your books — provident fund, ESI, state professional tax, labour welfare fund, gratuity provision and salary TDS under both regimes — so every payroll run posts to the general ledger the moment it is approved.
An Indian employer does not simply pay salaries. Each pay cycle creates deductions, contributions, challans, returns and records that different authorities expect in different formats, on different dates. VIBWERA is configured for each of them, and every statutory rate, slab, threshold and due date is a setting you control — not a number hard-coded in the product.
Employee and employer contributions computed per employee on the wage definition you configure, with UAN and member details held on the employee master and voluntary PF handled separately.
Output: ECR-ready contribution output for upload, contribution register and employer liability posted to the ledger.
Eligibility tracked per employee against the wage limit you configure, with mid-month joiners, exits and wage revisions handled inside the same run.
Output: Contribution statement per employee and per establishment, plus the employer share posted as expense.
State-wise slabs maintained separately, so a business with branches in more than one state deducts correctly for each work location without a parallel spreadsheet.
Output: State-wise PT deduction register for each return and challan.
Employee and employer LWF applied only to the states and periodicity where it applies, driven by the branch each employee is mapped to.
Output: LWF register by state and contribution period.
Annual tax liability projected from earnings, declared investments and perquisites, spread across remaining pay periods, with old and new regime computed so the employee's election is applied consistently through the year.
Output: Employee tax computation sheet, monthly TDS deduction and quarterly return-ready deduction data.
Gratuity provision accrued on continuous service and leave encashment liability carried in the books rather than surfacing only at exit.
Output: Provision schedules that reconcile to the balance sheet and feed the auditor's working papers.
Exit processing that closes attendance, notice period, recoveries, leave encashment and the final statutory deductions in one settlement.
Output: F&F statement for the employee and the closing entries in the ledger.
Payslips generated for every employee and available in the employee self-service portal or emailed, with registers retained for the statutory record-keeping period.
Output: Payslip PDFs, salary register, and an audit trail of who ran and approved each payroll.
One chain, one system of record. Nothing is re-keyed between attendance, payroll, statutory output and the books.
Shifts, attendance, leave and loss-of-pay captured against each employee and branch.
Earnings, deductions, arrears and reimbursements computed for the period, with maker-checker approval before release.
PF, ESI, PT, LWF and s.192 TDS applied per employee, per state, per establishment.
Payslips published to the employee self-service portal, with declarations and claims collected there too.
Contribution and deduction output produced in the formats your filings and challans need.
Salary cost, employer contributions, provisions and statutory payables posted to the GL by branch and cost centre.
Because payroll and the general ledger are the same system, salary cost, employer contributions and statutory payables are already in the books when the run is approved. There is no monthly journal to key in and nothing to reconcile between two tools.
Employees are mapped to a branch and work state, so professional tax, LWF and establishment-level output follow the right registration — and payroll cost lands on the right cost centre and branch P&L.
Payroll runs sit behind role-based access and maker-checker approval, and every run, revision and reversal is retained in the audit trail for the statutory retention period.
Employees view payslips, submit investment declarations and apply for leave themselves, which removes most of the email traffic that surrounds a pay cycle.
The AI assistant answers payroll questions from your own records — cost by branch, PF liability for a period, who is pending declarations — and cites the transactions behind the answer.
Payroll due dates sit in the same statutory calendar as your GST, TDS and ROC dates, so the whole compliance month is visible in one place.
Payroll data is yours, and moving it in or out is a supported operation rather than a support ticket. VIBWERA runs in three modes, and payroll works the same way in each.
Run attendance, payroll, statutory output and accounting entirely inside VIBWERA on a single ledger — the fastest route to a clean payroll month.
Keep an existing attendance device, biometric system or HR tool and exchange data over authenticated REST APIs and webhooks in both directions.
Import employee masters, attendance and earnings from CSV or Excel and export registers and statutory output the same way, on demand or on a schedule. Imports are validated line by line before anything posts.
Migration in is a managed step at onboarding — employee masters, opening balances, YTD earnings and deductions, and declared investments are loaded and reconciled before your first live run. Egress is equally explicit: you can export your masters, registers, payslip data and ledger at any time in open formats.
Yes. Professional tax slabs are maintained per state and each employee is mapped to a work location and branch, so deductions follow the state where the employee works. Your PT registers come out state-wise, ready for each return.
Yes. VIBWERA is branch-first and supports multiple companies and registrations under one login, with separate establishment-level statutory output and role-based access that can be limited to a company or branch.
Within the normal run. Joining and exit dates drive pro-rating and eligibility, arrears and revisions are computed for the affected periods, and exits go through full-and-final settlement that closes notice period, recoveries, leave encashment and final deductions together.
Both regimes are computed so the employee can see the comparison, and the elected regime is applied for the year with the remaining pay periods re-spread when the election or declarations change.
Onboarding is managed. Employee masters, salary structures, YTD earnings and deductions, statutory identifiers and declarations are imported from CSV or Excel, validated against masters and reconciled to your existing registers before the first live run — usually with one parallel cycle so both outputs can be compared.
You are. VIBWERA is a tool that computes, records and produces the output your filings need, and it is not a substitute for advice from your Chartered Accountant, payroll consultant or advocate. Statutory positions, elections and submissions remain the employer's responsibility.
Rates, slabs, wage limits and thresholds are configurable settings maintained per company and state, so they can be updated for a period without a product change and without restating prior runs.
In India. VIBWERA is a sovereign multi-tenant cloud platform operated by Dynamixe Digital Solutions India Pvt. Ltd. with data hosted in India, tenant-isolated, and retained in line with statutory record-keeping requirements.
Bring one month of real payroll data to a 30-minute demo and we will walk the whole chain — attendance to statutory output to ledger — against your own numbers.
Request a free demo