REPORTING & CONTROL
Attendance Integration
Derive loss-of-pay and overtime from attendance and leave data, read from BizzField HRMS or imported, instead of a monthly export and re-key.
IN SHORT
What is attendance integration?
Attendance Integration
Derive loss-of-pay and overtime from attendance and leave data, read from BizzField HRMS or imported, instead of a monthly export and re-key.
Reporting & Control
Cycle status, cost analytics, an audit log of changes and approvals, retained history and the attendance feed behind loss-of-pay.
THE PROBLEM
What goes wrong without attendance integration
These are the problems payroll teams run into when this is handled on spreadsheets and email.
Attendance is exported to Excel and re-imported into payroll each month.
Loss of pay is calculated by hand and disputed by employees after the payslip.
A late attendance correction does not reach the register, so the run is rebuilt.
Overtime arrives separately from the attendance it came from.
HOW IT WORKS
Attendance Integration inside a BizzField pay run
BizzField runs payroll in five steps: lock attendance, draft the register, review variance, approve, release. Here is how this capability works inside that cycle.
Direct feed
Payroll reads attendance and leave from BizzField HRMS or imported data, not a re-keyed sheet.
Derived loss of pay
Unpaid days are computed from the records instead of entered manually.
Cycle attendance lock
Attendance is frozen for the cycle, and unlocking is an explicit, logged action.
BUILT FOR INDIA
Indian statutory rules, built into the cycle
PF, ESI, professional tax and TDS are calculated inside the pay run, and state rules follow the employee's work location.
PF wage ceiling
Employee and employer provident fund computed on basic wages, respecting the statutory monthly ceiling.
ESI eligibility
Applied to employees within the gross wage limit of ₹21,000 a month, with contribution-period rules handled across the cycle.
State-wise PT
Professional tax slabs resolved by work location rather than by registered head office.
TDS & Form 24Q
Projected annual tax spread across remaining months, with quarterly Form 24Q output.
QUESTIONS
Attendance Integration — Questions We Get Asked
Payroll is a standalone product. It can consume attendance from BizzField HRMS or from imported attendance data, and it does not require HRMS to run.
The cycle must be explicitly unlocked, which is recorded. The register is then recalculated rather than patched, so payslips and the bank file stay consistent.
Yes. Separate legal entities can be run from a single console. Each entity keeps its own PF and ESI registration, its own approval chain and its own bank file.
FILES FROM THE APPROVED PAY RUN
Bank Files And Statutory Returns, Built From The Approved Register
What is paid, what is deducted and what is reported come from the same approved register, so the files are not rebuilt in Excel after the run.
BANK TRANSFER
Bank Salary Files
Key Capabilities
- Output formatted to the bank's own upload specification
- Formats for HDFC, ICICI and SBI
- A separate file per bank when employees bank with different banks
- Released amounts kept against the cycle for matching to the bank statement
The bank-format salary file is generated from the approved register, so the amount credited and the amount on the payslip come from the same source.
See Bank Transfer SupportSTATUTORY & ACCOUNTING
Statutory Return Files And Accounting Export
Key Capabilities
- PF ECR file produced from the pay run
- ESI contribution return
- Form 24Q assembled from the quarter's cycles, not re-keyed
- General Ledger export for Tally Prime and Zoho Books
The PF electronic challan-cum-return, the ESI return and quarterly Form 24Q are produced from the same figures payroll deducted. Submission stays with your finance or compliance team. Payroll can also export General Ledger data for Tally Prime and Zoho Books.
See Government ReportsCONTROL & AUDIT TRAIL
Approval Controls And A Named Audit Trail
A pay cycle is released through maker-checker approval, and every edit, override, approval, rejection and reversal is recorded against a named user and timestamp.
SEGREGATION OF DUTIES
Maker-Checker Release
Key Capabilities
- Preparer and approver are distinct roles
- Sending a cycle back to draft requires a reason that stays with the cycle
- Entities that need finance and leadership sign-off can add approval levels
The person who prepared the cycle is not the person who releases it, and both actions are recorded against named users.
See Approval WorkflowAUDIT TRAIL
Named Audit Log
Key Capabilities
- Every action attributed to a user, not a shared account
- Logs kept against the cycle they belong to
- A closed period can be reconstructed from its own log
Edits, overrides, approvals and reversals are written to the audit log against a named user and timestamp, so a closed cycle can be explained from its own record.
See Payroll Audit LogsKEEP EXPLORING
Related Pages
Other payroll capabilities teams usually evaluate alongside this one.
Payroll Dashboard
See the cycle's current step, headcount, gross and net totals, flagged variances and statutory dues on one screen, before the month closes.
ExplorePayroll Analytics
Break payroll cost down by department, entity, location and cycle, and see which joiners, exits, revisions or variable pay moved it.
ExplorePayroll Audit Logs
Edits, overrides, approvals and reversals recorded with the user and the time, so a closed cycle can be explained to an auditor.
ExplorePayroll History
Closed cycles kept as released, so an old payslip or register can be reproduced and a rate change applies forward, not to past periods.
ExploreSee attendance integration on your own payroll data
Book a walkthrough with our Kanpur-based payroll team and run a sample cycle on your own salary structure.