Attendance, Leave and Payroll Without the Spreadsheet
Shifts, a working calendar per site, leave that knows the holiday list, and a payroll run that refuses rather than quietly paying everybody zero.
Payroll is the process where a small error is a personal event for somebody. It deserves more care than a spreadsheet formula that one person understands.
The working calendar is per site
A company with an office in one state and a site in another does not share a calendar. Weekly offs, shift timings and the holiday list all hang off the location — because the payroll divisor counts the days that site was open. Get it wrong and loss of pay is calculated against a month nobody worked.
Leave knows the calendar
A leave application spanning a weekly off and two holidays should not consume five days of entitlement. QuantX Ops counts only working days for the applicant's own site.
Payroll refuses rather than pretending
This is the part worth dwelling on. Payroll with no salary components configured, or with no per-person breakup entered, could technically "run" — computing a gross of zero for everybody, producing no payslips, and reporting success.
That is far worse than failing. So QuantX Ops checks its prerequisites and refuses, naming what is missing and linking to the screen that fixes it. A module that declines to transact is protecting you; one that completes silently is not.
And it posts to the ledger
A payroll run writes its journal like every other document: gross to the expense heads, deductions to their liability accounts, net to payable. Nobody types it up afterwards.