Tuling HCM module

Payroll Suite

A full monthly payroll run lifecycle with statutory-ready exports — the most operationally complete module in Tuling HCM.

About this module

Payroll is the module where “mostly working” isn’t good enough — a payroll mistake is a trust problem, not just a bug. Tuling HCM’s payroll suite is built with that in mind: a preview step before anything is locked, optimistic-locking to prevent two people finalizing conflicting changes, and a full sync log so if something ever needs to be traced after the fact, there’s a real record — not a guess.

Capabilities

  • Preview-Then-Finalize Payroll Runs

    Run payroll with a preview step before finalizing — catch errors before they're locked in, not after the payslips are already out.

  • Optimistic-Locking Safety

    Payroll runs use version-based locking, so two people can't finalize conflicting changes to the same run at once — a real safeguard, not an assumption that it won't happen.

  • Statutory-Ready Exports

    PF ECR file, ESI contribution report, and Professional Tax summary generate directly from the finalized run — formatted for filing, not raw data someone has to reformat.

  • Batch Payslip Generation

    Generate and download payslips for the whole institution in one batch, not one employee at a time.

  • Run Retry, Cancel & Sync Logging

    A payroll run can be retried or cancelled cleanly, with a sync log recording exactly what happened — useful when something needs to be traced after the fact.

  • Full & Final Settlement Processing

    Exit settlements — total earnings, total deductions, net settlement — run through their own pending → processed → approved workflow, not folded into a regular payroll run as an afterthought.

  • Mid-Month Dry Run

    HR and management can run a dry run as of any date — calculated only up to that day, with nothing written — and download the result to Excel to check corrections before the real run.

  • One Real Run per Period

    A period can have only one live run, so two people cannot process the same month twice. If a run needs to be redone, HR cancels it and runs again, and the cancelled run keeps its audit trail.

FAQ

Frequently asked questions