Skip to main content
BizzFieldHRMS

INTEGRATED PAYROLL

Every Pay Component. One Connected Pay Run.

Salary setup, overtime, incentives, claims, loans, revisions, payslips and exit settlements all feed the same draft-to-paid pay run in BizzField HRMS — nothing is re-keyed, and nothing is reconciled in a side spreadsheet.

  • 13

    Payroll Capabilities Covered

  • 4

    Audited Pay-Run Stages

  • 5

    Statutory Deductions Automated

  • 2

    Approval Tiers On Every Claim

TRUSTED BY LEADING ORGANIZATIONS

Advait logo
Aminov Healthcare logo
Antrep Healthcare logo
Ashok Nutririch logo
Black Magnum logo
Fitfire logo
Hyderabad Crop Science logo
Indmac logo
J. Mitra logo
Macintel logo
Meravee logo
Navrang logo
Neyah logo
phL logo
RAA logo
Sita Vatika logo
Sunveat Kenya logo
Sushima logo
SW Healthcare logo
Teeming URN logo

HOW IT FITS TOGETHER

Four Stages. Every One Feeds The Pay Run.

Every payroll capability belongs to one of four stages. Pick a feature to jump straight to what it does.

  1. Stage 01

    Define Pay

    The fixed-pay foundation, and how it changes.

  2. Stage 02

    Capture Cycle Inputs

    Amounts that change from month to month.

  3. Stage 03

    Run & Verify

    The monthly pay run and the checks around it.

  4. Stage 04

    Pay Out & Settle

    What employees receive, every cycle and at exit.

BUILT INTO EVERY FEATURE

What Every Payroll Feature Shares

These rules apply to every capability on this page, so the sections below only cover what each feature does differently.

Configured Once, Reused Every Cycle

Components, structures, incentive rules, shift patterns and claim policies are set up once and reused. Nothing is rebuilt at month-end.

One Pay Run, No Side Spreadsheets

Overtime, incentives, claims, EMIs, arrears and settlements arrive as line items in the same pay run instead of separate trackers reconciled by hand.

Approved Before It Is Paid

Pay runs, revisions, incentives, claims and loans route through built-in approvals, and every step is written to an audit trail.

Statutory Deductions, Calculated

Components carry statutory tags, so PF, ESI, Professional Tax, TDS and LWF compute on every run through the Statutory Compliance Engine.

STAGE 01 · DEFINE PAY

Set Pay Up Once. Change It On The Record.

The components and structures every pay run reads from, and the controlled way they change over time.

Salary Components

The shared master of every earning, deduction and statutory item your payroll uses.

Basic, HRA, special allowance, conveyance, PF, ESI and Professional Tax are each defined a single time. Every salary structure draws from this master, so a component behaves identically wherever it appears.

  • Taxability, calculation formula and statutory linkage set per component
  • Statutory eligibility tags — basic wages for PF, gross pay under ₹21,000 for ESI
  • No component redefined per structure, so breakups never drift apart

Salary Structures

Reusable CTC templates that turn components into each employee's pay breakup.

Components are grouped into grade or band templates with set percentage splits and caps, then assigned to employees at onboarding or promotion. A pay run reads each employee's assigned structure to compute gross-to-net and employer contributions without formula lookups.

  • Grade and band templates, from associate levels to leadership
  • Per-employee overrides and bespoke packages for specialist roles
  • Guardrails for the 50% basic-wage rule, PF wage ceiling and ESI eligibility

Good to knowChanges carry effective dates. Paid runs stay locked to the structure that applied in their cycle.

Salary Revisions

Appraisals, promotions and corrections, approved and kept as compensation history.

A revision is proposed against the employee's current structure with an effective date and routed for approval before it applies. It then updates the same CTC breakup payroll reads from, while earlier figures stay on record instead of being overwritten.

  • Proposed against the existing structure, not re-entered from scratch
  • Built-in approval workflow in place of email threads
  • Complete compensation history for every employee

Good to knowA revision dated in the past is settled automatically through Retro Pay.

Retro Pay

Arrears for pay changes that take effect in cycles already paid.

When a revision or correction is back-dated, Retro Pay maps it to every cycle it affects, works out the difference cycle by cycle and adds the net arrears to the next pay run — no manual back-dated recalculation.

  • Every affected cycle identified, not just the current one
  • Difference computed per cycle rather than estimated as a lump sum
  • Net arrears paid as their own line item in the next run

Good to knowRetro within one entity is on the Growth plan. Adjustments spanning entities or states are Enterprise.

STAGE 02 · CAPTURE CYCLE INPUTS

Everything That Changes Month To Month.

Variable amounts are recorded where they happen and reach the pay run already approved.

Shifts & Overtime

Shift patterns and overtime hours converted into pay without a side log.

Shift patterns are maintained centrally in a shift master rather than per team. Overtime is recorded against each employee's assigned shift as hours are logged, so there is no overtime register to reconcile before payroll.

  • One shift master in place of team-level trackers
  • Overtime recorded automatically against the assigned shift
  • Approved hours flow in from Attendance & Shift Tracking

Good to knowShift or overtime corrections for a closed cycle are settled through Retro Pay.

Variable Pay & Incentives

Commissions, bonuses and incentive plans run as rules, not monthly spreadsheets.

An incentive plan's rules are defined once. Each cycle, qualifying transactions are captured against those rules and routed for approval on schedule, and the approved amounts are paid alongside fixed salary.

  • Sales commissions, quarterly bonuses, referral and leadership incentives
  • Qualifying transactions captured automatically every cycle
  • Approvals follow the cycle without a manual trigger

Good to knowRecurring or one-off variable components can also sit inside a salary structure.

Reimbursements

Employee expense claims settled through payroll after a two-tier approval.

Employees submit claims against a defined reimbursement policy. Each claim is approved first by the reporting manager, then by finance, and the approved amount is paid with the next pay run instead of through a separate reconciliation.

  • Claims raised against defined reimbursement policies
  • Manager approval first, finance approval second
  • Receipts uploaded from the employee self-service app

Employee Loans

Loans to employees, recovered automatically through payroll EMIs.

A loan is issued with its terms recorded against the employee. The EMI schedule tracks against payroll on its own, and each instalment is deducted in the relevant pay run until the balance is cleared.

  • Loan requests pass the same two-tier approval as claims
  • EMI schedule tracked automatically, not in a hand-updated sheet
  • Deductions continue each cycle until the loan is repaid

Good to knowIf the employee leaves, the outstanding balance is recovered in Full & Final Settlement.

STAGE 03 · RUN & VERIFY

Draft To Paid. Checked Before Approval.

The pay run brings every input together, flags what looks wrong and records who approved what.

Automated Pay Runs

The monthly payroll cycle, moved from draft to paid through four audited stages.

  1. 1Draft
  2. 2Submit
  3. 3Approve
  4. 4Pay

A draft is built automatically from attendance, leave, salary structures and every approved cycle input. Finance reviews it — statutory deductions included — before approval, and payslips generate the moment the run is marked paid.

  • Approved hours and leave without pay pulled in from Attendance & Shift Tracking and Leave Management
  • Submitted runs held in a reviewable state — nothing is final until approved
  • PF, ESI, PT and TDS ready to file once the run is paid

Automated Variance Checks

A pre-approval scan that surfaces unusual pay before any money moves.

Every draft run is compared with the previous cycle. Sharp pay movements, duplicate expense or leave submissions and timesheet conflicts are flagged for HR, so reviewers investigate the exceptions instead of re-checking every line.

  • Each employee's draft pay compared with the prior month
  • Pay movement above 20% flagged for review
  • Duplicate claims and leave submissions detected

Good to knowFlags are resolved from a single HR queue while the run is still in draft.

STAGE 04 · PAY OUT & SETTLE

Payslips On Time. Exits Settled From The Record.

What employees receive at the end of every cycle, and at the end of their tenure.

Payslips & Self-Service

Downloadable payslips for every employee the moment a run is paid.

A payslip is generated for each employee as soon as the pay run moves to paid, with no separate processing step. Employees open and download current and past payslips through self-service instead of raising a request with HR.

  • Every figure traces back to the same run and statutory configuration
  • Tax deduction follows the regime locked in IT & TDS Declarations
  • Available on the web and in the employee self-service mobile app

Leave Encashment

Unused leave converted to pay, calculated from the live leave balance.

Employees request encashment of unused leave against their recorded balance. The amount is worked out from the live balance in Leave Management, not a figure someone checked by hand.

  • Self-service requests against the employee's own balance
  • Encashable balance carried into the exit settlement automatically
  • Check the maths with the Leave Encashment Calculator

Full & Final Settlement

The exit payroll — dues, recoveries and encashment computed from records already on file.

Recording an employee's exit triggers the settlement. Final salary, leave encashment, notice-period recovery and any outstanding loan balance are computed against the same salary structure used every cycle, reviewed like a regular run, then paid out to close the record.

  • Triggered by the recorded exit, not a manual exit sheet
  • Leave encashment pulled from the live balance
  • Notice-period shortfall and open loan balances recovered

From the people who run it

Sales leaders, not testimonials.

Navrang Spices, Ashok Masale logoFMCG
“Earlier, our field reporting was inconsistent and difficult to verify. With BizzField, we now have complete visibility on ground activities and our team accountability has improved drastically.”
↓ 75%reporting errors within 30 days
AGAchal GuptaDirector · Navrang Spices, Ashok Masale

FAQ

Integrated Payroll — Questions We Get Asked

Plans, pay-run stages and the questions that come up once payroll runs inside the HRMS.

It is the payroll layer of BizzField HRMS. Salary setup, monthly inputs, the pay run, payslips and exit settlements work as one system, with attendance and leave flowing in from Core HR — so payroll is never reconciled against a separate tool.

Every capability on this page is included in the Growth plan. The Starter plan covers employee lifecycle, attendance, leave and timesheets but no payroll, and multi-entity and multi-state payroll, cross-entity retro adjustments and custom approval workflows are part of Enterprise. Pricing is custom — quoted for your headcount and the modules you use.

Draft, submit, approve and pay. The draft is built from attendance, leave, salary structures and approved cycle inputs; variance checks flag anomalies before approval; and payslips generate the moment the run is paid. Each step is recorded in an audit trail.

They are calculated automatically on every run from the statutory tags on each salary component, at current rates. Form 24Q exports directly from the same reconciled payroll data instead of being rebuilt each quarter.

No. Structure changes and salary revisions carry effective dates, and paid runs stay locked to the structure that applied in their cycle. If a change is back-dated, Retro Pay computes the arrears and adds them to the next run.

No. Rules are defined once as a plan. Qualifying transactions and approvals then flow each cycle, and approved amounts are paid with fixed salary.

Through self-service. A payslip is generated for every employee the moment a run is paid, and current and past payslips can be downloaded without contacting HR.

The outstanding balance is recovered in the Full & Final Settlement, alongside final salary, leave encashment and any notice-period recovery.

See Integrated Payroll Run End To End

Walk through a full cycle on BizzField HRMS — from salary structures and cycle inputs to a draft-to-paid pay run and a final settlement.