Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $249.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Auto-Attendance & Workday Processor
A build-to-order ERPNext app that turns raw Employee Checkin records into fully processed Attendance per employee, applying your shift rules, grace periods, and late-in / early-out / half-day logic automatically. ECOSIRE designs, builds, installs, and supports it for your HR operations team.
$249.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
`Weekly Working Hours` DocType bound per employee (or via role/grade template) declaring expected hours and working days for accurate per-day baselines
`Process Workday` batch engine that reads a date range of `Employee Checkin` records and generates one processed record per employee-day
IN/OUT punch pairing that computes actual worked time, break/overtime deltas, and total hours from raw biometric log_type events
Configurable grace periods for check-in and check-out, evaluated against each employee's assigned `Shift Type` window
Rule-driven late-in, early-out, and half-day detection with the triggering threshold and reason persisted on the record for audit
`Attendance Regularization` implemented as a Frappe Workflow with states, role-based transitions, and manager approval
Scheduler Event driving nightly/hourly background processing via `frappe.enqueue` so large employee counts don't block the request
Doc events wired in `hooks.py` (`on_submit`/`validate`) to keep derived attendance and workday data consistent automatically
Whitelisted server methods and full Frappe REST API endpoints so biometric middleware can push punches and trigger processing headlessly
Idempotent, re-runnable processing that upserts rather than duplicating `Attendance` when a date range is reprocessed
Writes back native ERPNext `Attendance` (Present/Absent/Half Day/On Leave) so downstream Payroll and Salary Slip logic consumes it unchanged
Leave-aware processing that respects approved `Leave Application` and holiday lists so leave days aren't flagged as absent
Permissions enforced through role profiles (HR Manager, line manager, employee) so each role sees and edits only what policy allows
Optional client script buttons for on-demand single-employee or single-day reprocessing directly from the desk UI
Reporting-ready output (query report / dashboard fields) for exceptions like chronic lateness, missing punches, and unprocessed days
Bu Ürün Hakkında
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.
Neden Auto-Attendance & Workday Processor
`Weekly Working Hours` DocType bound per employee (or via role/grade template) declaring expected hours and working days for accurate per-day baselines
`Process Workday` batch engine that reads a date range of `Employee Checkin` records and generates one processed record per employee-day
IN/OUT punch pairing that computes actual worked time, break/overtime deltas, and total hours from raw biometric log_type events
Configurable grace periods for check-in and check-out, evaluated against each employee's assigned `Shift Type` window
Rule-driven late-in, early-out, and half-day detection with the triggering threshold and reason persisted on the record for audit
`Attendance Regularization` implemented as a Frappe Workflow with states, role-based transitions, and manager approval
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 2-4 weeks from confirmed scope, and the git repository is handed over to you at the end so the code is yours to keep and extend.
Ne elde edeceksin
- Installable source code for your version of the app, built against your ERPNext v15 or v16 bench
- Installation and configuration on your environment, including shift rules, grace periods, and scheduler setup
- Technical documentation covering DocTypes, hooks, whitelisted methods, scheduler events, and the REST API surface
- User guide plus a live training session for your HR operations team
- UAT on a staging bench with a documented rollback plan before touching production
- Attendance regularization workflow configured to your approval hierarchy and role profiles
- Git repository handover so the code is yours to keep, audit, and extend
- Post-go-live support window for defect fixes and configuration adjustments
Bu kimin için
HR Operations Lead
Owns the monthly attendance-to-payroll cycle and is tired of exporting checkins to spreadsheets and hand-fixing Attendance records. Needs the workday to post itself against a defensible, auditable policy so Salary Slips are right the first time.
ERPNext / Frappe System Administrator
Runs the bench and integrations. Wants a clean Frappe app with real DocTypes, hooks, and whitelisted methods it can call from the biometric middleware, on v15/v16, without brittle spreadsheet workarounds or unmanaged customizations.
People/HR Manager
Sets attendance policy — grace windows, late and half-day rules — and approves regularizations. Needs configurable thresholds and a role-based approval workflow rather than one-size-fits-all native behavior.
Finance / Payroll Controller
Consumes attendance for payroll and needs the numbers to be traceable. Wants every late-in, early-out, and half-day flag to carry the reason and threshold that produced it, so payroll deductions and disputes are backed by evidence.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Auto-Attendance & Workday Processor uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
Auto-Attendance & Workday Processor yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
Auto-Attendance & Workday Processor Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Per-employee weekly working-hours model | Dedicated `Weekly Working Hours` DocType per employee/template | Possible but you design and maintain the schema | Usually fixed to Shift Type only | |
| Late-in / early-out / half-day detection | Rule-driven with reason and threshold stored per record | Whatever you code and document yourself | Basic flags, limited configurability | |
| Batch workday generation | `Process Workday` engine over any date range, idempotent re-runs | You build and test the batch job | Often single-shift, limited range handling | |
| Regularization workflow | Frappe Workflow with role-based approval transitions | Build states and permissions from scratch | May offer a basic request form | |
| Automation & scheduling | Scheduler Event + enqueued background jobs, doc events in `hooks.py` | You wire hooks and scheduler yourself | Sometimes scheduled, varies by app | |
| API / integration surface | Whitelisted methods + REST API for middleware-driven processing | You expose and secure your own endpoints | Limited or undocumented endpoints | |
| Fit to your policy | Built to your grace, half-day, and payroll rules | Fully custom but at your cost and risk | Adapt your policy to the app's assumptions | |
| Ownership & support | Git repo handover + post-go-live support window | You own everything including all maintenance | Vendor-locked, upgrades on their schedule |
Auto-Attendance & Workday Processor hakkında Sıkça Sorulan Sorular
+Is this a ready-made app I can download and install today?
No. It is build-to-order. ECOSIRE designs, builds, installs, and supports it around your specific shift patterns and attendance policy — it is not an existing Frappe Cloud Marketplace download, and there is no instant download. We start from a scoping call, confirm scope, then build against your ERPNext version.
+How long does delivery take?
Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on how many shift patterns, grace rules, and integrations (for example biometric middleware) are involved. We agree the scope and timeline in writing after the initial scoping call before any build starts.
+Which ERPNext / Frappe versions are supported?
We build and test against Frappe/ERPNext v15 and v16. We target your specific version and confirm the target bench during scoping, then run UAT on a staging bench matching that version before go-live.
+How does it integrate with our biometric or checkin devices?
The engine reads native `Employee Checkin` records, so any middleware that already pushes punches into ERPNext works. It also exposes whitelisted methods and standard Frappe REST API endpoints, so your device middleware or a scheduled job can push punches and trigger workday processing headlessly, without the desk UI.
+Does it work with native ERPNext Payroll?
Yes. The processor writes back to the native `Attendance` DocType with standard statuses (Present, Absent, Half Day, On Leave) and respects approved `Leave Application` records and holiday lists. Your existing Payroll and Salary Slip logic consumes that output unchanged — we sit in front of payroll, not on top of it.
+What about support and updates after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because we hand over the git repository, the code is yours to keep and extend. Longer-term maintenance, new policy rules, or version upgrades (for example a future v16 point release) can be scoped as a separate support retainer.
+Can employees correct their own attendance?
Yes. We build an Attendance Regularization workflow as a Frappe Workflow with defined states and role-based transitions. Employees raise a correction request, managers approve or reject it, and permissions are enforced through role profiles so each role only sees and edits what your policy allows.
Teklif isteyin
Auto-Attendance & Workday Processor
A build-to-order ERPNext app that turns raw Employee Checkin records into fully processed Attendance per employee, applying your shift rules, grace periods, and late-in / early-out / half-day logic automatically. ECOSIRE designs, builds, installs, and supports it for your HR operations team.
- `Weekly Working Hours` DocType bound per employee (or via role/grade template) declaring expected hours and working days for accurate per-day baselines
- `Process Workday` batch engine that reads a date range of `Employee Checkin` records and generates one processed record per employee-day
- IN/OUT punch pairing that computes actual worked time, break/overtime deltas, and total hours from raw biometric log_type events
- Configurable grace periods for check-in and check-out, evaluated against each employee's assigned `Shift Type` window