Most HR teams on ERPNext hit the same wall: attendance never posts itself the way the policy actually reads. Native ERPNext gives you Employee Checkin, Shift Type, and the built-in "Process Attendance" run — but that stock pipeline is coarse. It marks Present/Absent/Half Day off a single shift assignment, has one grace window, and has no real concept of per-employee weekly working-hours contracts, per-day expected hours, or a defensible late-in/early-out policy. So HR ends up exporting checkins to spreadsheets, hand-computing worked hours, and manually overriding Attendance records every payroll cycle — which is slow, error-prone, and impossible to audit.

The Auto-Attendance & Workday Processor is a proper Frappe app (its own module, DocTypes, and hooks.py) that we build to your exact policy and install onto your ERPNext v15/v16 bench. At its core is a Weekly Working Hours model bound per employee (or per role/grade template) that declares expected hours and working days, and a batch Process Workday engine that reads a date range of Employee Checkin rows, pairs IN/OUT punches per employee, computes actual worked and break time, and writes back a clean Attendance (or an intermediate Workday DocType) for every employee-day. The engine applies configurable grace periods, then flags late-in, early-out, and half-day per your thresholds — with the reasoning stored on the record so nothing is a black box at payroll time.

Technically it runs as controller logic plus whitelisted server methods invoked from a Scheduler Event (nightly or hourly enqueued background job) and on-demand from a button-driven client script. Doc events in hooks.py (for example on_submit of Employee Checkin, or validate on the Workday record) keep derived data consistent, and everything is exposed over the standard Frappe REST API and whitelisted methods so your biometric middleware or a scheduled sync can push punches and trigger processing without touching the desk UI. An Attendance Regularization workflow (a Frappe Workflow with states and role-based transitions) lets employees raise corrections and managers approve them, with permissions enforced through role profiles so HR, line managers, and staff each see only what they should.

Because this is build-to-order, nothing is fabricated or pre-packaged as a marketplace download. We start from a short scoping call, confirm your shift patterns, grace rules, half-day/late definitions, and payroll hand-off, then build the app against your version of ERPNext. You get the installable source, a UAT pass on a staging bench with a rollback plan, install and configuration on your environment, documentation, a training session for your HR ops team, and a post-go-live support window. Typical delivery is one working week from confirmed scope, and the git repository is handed over to you at the end so the code is yours to keep and extend.