The hard part of attendance was never exporting a sheet. It is the **definitions**: the system's idea of overtime is not the company's, and the pay period is rarely the calendar month. Here is how the line actually runs.
Attendance systems count every minute beyond the schedule as overtime, while the company usually only pays the part that went through approval. Someone has to filter the difference row by row, leave a trace of it, and do it again next month.
As soon as the period is not a calendar month — say the 26th to the 25th — the export has to be done twice and stitched together. Get the stitch wrong and every overtime and absence figure is wrong, in a way that is hard to spot.
Late arrivals, missing punches and short hours have to reach the right department lead. Done by hand you either miss a department or send the whole company's list to every lead — and the second is worse than the first.
Period boundaries are configuration, not a hardcoded calendar month. A period that crosses months is fetched in two passes and rejoined per person, so nobody has to remember that this month needs two exports.
Only approved hours land in the overtime column, and leave categories map to the names your company already uses rather than a tool's defaults.
Column names and order follow your existing template, so whoever runs payroll can use it directly instead of reformatting it first.
The rules are configurable — how many consecutive late arrivals, how many missing punches, what hour threshold — and leads are resolved from the directory rather than pinned in config, so a reassignment is picked up next month.
Daily reminders, the Monday roll-up and the fixed month-end run each have their own timing. Nobody has to watch the calendar.
Fetching and calculation run on the machine with the desktop app installed. Only the model call you chose leaves the network, and what leaves is the task description, not the roster. Enterprise deployments can route that call through your own gateway.
Rules are configuration, not code. The common shapes — approved-only, banded conversion, holiday multipliers — are parameters. A genuinely unusual formula is calibrated once at delivery and applied every month after that.
That is the default. Distribution is split by department and leads come from the directory; the complete company list goes to HR only.
It applies from the next run. No reinstall, no waiting for a release.