Unresolved exceptions become deductions
Every out-of-zone check-in or missing mark left open is a query waiting to happen. Closed within the week they are administrative; closed on payroll day they are a conversation about someone’s pay.
Face-verified hours, approved leave, and overtime — exported cleanly into your payroll each month. And when you want payroll itself inside the platform, the Full HRMS plan adds the complete engine: components, gratuity, and WPS file generation.
Exports on Growth · Full payroll engine on Full HRMS · WPS / SIF ready
Most school payroll disputes trace back to the same source: an attendance register nobody fully trusts. Hours reconstructed from a punch machine, leave approved on WhatsApp, overtime nobody recorded. CampusTrack fixes the feed: every hour is face-verified and geofenced, every leave day carries its approval trail, and month-end exports arrive in the shape your payroll system or bank WPS gateway expects. Schools that want to go further move to the Full HRMS plan — a complete payroll engine with salary components, GPSSA and gratuity calculation, and WPS / SIF bank file generation.
Illustrative interface — verified hours, leave, and overtime in payroll-ready exports.
Every hour in the export is backed by a face-verified, geofenced check-in with a full audit trail — the register finance can defend.
Hours, overtime, leave, and absences export in formats your payroll system or bank WPS gateway accepts — on schedule, without spreadsheet surgery.
Only approved leave and recorded overtime reach the export — the approval chains upstream keep month-end disputes out of payroll.
Salary components, templates, and pay profiles; GPSSA and gratuity (Article 51) calculation; WPS / SIF bank file generation; GL journal patterns for ERPNext, Zoho Books, and Tally.
Offboarding workflows calculate end-of-service on the actual verified record — service dates, leave balances, and final settlements in one place.
Extended audit retention and a DPO toolkit on the Full HRMS plan — the paper trail regulators and auditors expect from an employer of record.
Payroll problems are almost never payroll problems. They are attendance and leave problems that went unresolved and arrived at the end of the month.
Every out-of-zone check-in or missing mark left open is a query waiting to happen. Closed within the week they are administrative; closed on payroll day they are a conversation about someone’s pay.
A payroll period rarely matches the calendar month exactly, and the days at the boundary are where hours get counted twice or not at all. Aligning periods explicitly removes an entire category of error.
Whether a specific absence was paid, unpaid or authorised determines the deduction. Categorised at the point of approval, it is settled; reconstructed at month end, it is contested.
Someone starting on the 12th or leaving on the 20th needs their period calculated from actual days. This is where manual payroll most reliably produces the wrong number.
Hours beyond contract have to be identified consistently rather than decided per person per month, or the same situation gets treated differently twice and both people find out.
The point of payroll readiness is that the export needs no manual correction. If a file always needs a spreadsheet pass before it can be used, the upstream data is the actual problem.
A 20-minute walkthrough from check-in to WPS export — with your payroll cycle, not a demo script.