The run your auditor signs.
Old regime, new regime — computed together
Every projection computes both regimes from one fact set: slabs by age band, rebate and marginal relief, surcharge, cess, rounding. The recommendation and the deduction come from the same math, and employees on the dearer regime are flagged.
The quarterly return falls out of the run
Salary TDS returns computed straight from posted payroll, an e-return file in the standard layout, and a numbered Form 16 certificate register that stamps back onto the ledger.
Recovered automatically, accounted properly
Disbursements raise real receivables; installments recover inside the run and auto-close at zero; an audit-grade loan register keeps opening + disbursed − repaid = closing.
Two regimes. One fact set. The math decides.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Payroll |
|---|---|
| Statutory employee master — PAN, PF, ESI | Native |
| Salary structures with formula components | Native |
| Pay runs across ten states' rules | Native |
| Safe recalculation and reruns | Native |
| PF, ESI, PT and LWF rules kept current | Native |
| Dual-regime income-tax engine | Native |
| Employee tax declarations | Native |
| TDS returns and Form 16 | Native |
| Loans and advances against payslips | Native |
| Single-batch disbursement | Native |
| Full & final settlement | Native |
| GL posting from the run itself | Native |
Everything in Payroll.
The questions evaluators ask.
Which statutory components are supported?
The Indian set, kept current: PF, ESI, professional tax across ten states' rules, LWF, and income tax with a dual-regime engine that works out old and new regime side by side for every employee, every month. Challans for PF, ESI and tax produce straight from the run, and TDS returns and Form 16 generate from the runs themselves — what was deducted is what gets filed.
How does attendance reach payroll?
Without a file transfer. Attendance captured in xMatix — including field attendance with selfie and geofence verification — lives on the same data model the pay run reads, so the run consumes the recorded facts directly. When an input turns out wrong, recalculation is safe: fix it and rerun, with no orphaned figures and no manual patching of what was already paid.
Can expense claims be filed from the field?
Yes — snap the receipt at the taxi stand and the claim line starts itself. Each line knows its type and its rules, GST details ride along so input credit is captured instead of lost, and the policy engine checks every line as it is entered — the over-limit portion is disallowed automatically, with no awkward email later. Duplicates are checked against the claimant's whole history, not just the current claim. Explore xMatix Expense Management.
How are approvals routed?
By your policy, on the platform. Claims route through the approvals you configure, and the moment one clears it is booked — approved means posted to the GL, with no rekeying and no month-end pile. Payments then batch: approved claims collect into one reimbursement run and net pay disburses as a single authorized batch, each with the trail intact.
